Transactions
Last updated
Last updated
Transactions are cryptographically signed instructions from accounts. An account will initiate a transaction to update the state of the Electroneum network. The simplest transaction is transferring ETN from one account to another.
To help you better understand this page, we recommend you first read Accounts and our Introduction to the Electroneum Smart Chain.
An Electroneum transaction refers to an action initiated by an externally-owned account, in other words an account managed by a human, not a contract. For example, if Bob sends Alice 1 ETN, Bob's account must be debited and Alice's must be credited. This state-changing action takes place within a transaction.
Transactions, which change the state of the EVM, need to be broadcast to the whole network. Any node can broadcast a request for a transaction to be executed on the EVM; after this happens, a validator will execute the transaction and propagate the resulting state change to the rest of the network.
Transactions require a fee and must be included in a validated block. To make this overview simpler we'll cover gas fees and validation elsewhere.
A submitted transaction includes the following information:
from – the address of the sender, that will be signing the transaction. This will be an externally-owned account as contract accounts cannot send transactions.
recipient – the receiving address (if an externally-owned account, the transaction will transfer value. If a contract account, the transaction will execute the contract code)
signature – the identifier of the sender. This is generated when the sender's private key signs the transaction and confirms the sender has authorized this transaction
nonce - a sequentially incrementing counter which indicates the transaction number from the account
value – amount of ETN to transfer from sender to recipient (denominated in WEI, where 1ETN equals 1e+18wei)
input data – optional field to include arbitrary data
gasLimit – the maximum amount of gas units that can be consumed by the transaction. The EVM specifies the units of gas required by each computational step
maxPriorityFeePerGas - the maximum price of the consumed gas to be included as a tip to the validator
maxFeePerGas - the maximum fee per unit of gas willing to be paid for the transaction (inclusive of baseFeePerGas and maxPriorityFeePerGas)
Gas is a reference to the computation required to process the transaction by a validator. Users have to pay a fee for this computation. The gasLimit, and maxPriorityFeePerGas determine the maximum transaction fee paid to the validator.
The transaction object will look a little like this:
But a transaction object needs to be signed using the sender's private key. This proves that the transaction could only have come from the sender and was not sent fraudulently.
An Electroneum client like etn-sc will handle this signing process.
Example JSON-RPC call:
Example response:
the raw is the signed transaction in Recursive Length Prefix (RLP) encoded form
the tx is the signed transaction in JSON form
With the signature hash, the transaction can be cryptographically proven that it came from the sender and submitted to the network.
The vast majority of transactions access a contract from an externally-owned account. Most contracts are written in Solidity and interpret their data field in accordance with the application binary interface (ABI).
The first four bytes specify which function to call, using the hash of the function's name and arguments.
The rest of the calldata is the arguments, encoded as specified in the ABI specs↗.
For example, lets look at this transaction↗. Use Click to see More to see the calldata.
The function selector is 0xa9059cbb. There are several known functions with this signature↗. In this case the contract source code↗ has been uploaded to Etherscan, so we know the function is transfer(address,uint256).
The rest of the data is:
According to the ABI specifications, integer values (such as addresses, which are 20-byte integers) appear in the ABI as 32-byte words, padded with zeros in the front. So we know that the to address is 4f6742badb049791cd9a37ea913f2bac38d01279↗. The value is 0x3b0559f4 = 990206452.
On Electroneum Smart Chain there are a few different types of transactions:
Regular transactions: a transaction from one account to another.
Contract deployment transactions: a transaction without a 'to' address, where the data field is used for the contract code.
Execution of a contract: a transaction that interacts with a deployed smart contract. In this case, 'to' address is the smart contract address.
As mentioned, transactions cost gas to execute. Simple transfer transactions require 21000 units of Gas.
So for Bob to send Alice 1 ETN at a baseFeePerGas of 190 gwei and maxPriorityFeePerGas of 10 gwei, Bob will need to pay the following fee:
Bob's account will be debited -1.0042 ETN (1 ETN for Alice + 0.0042 ETN in gas fees)
Alice's account will be credited +1.0 ETN
The base fee will be burned -0.00399 ETN
Validator keeps the tip +0.000210 ETN
Gas is required for any smart contract interaction too.
Any gas not used in a transaction is refunded to the user account.
Once the transaction has been submitted the following happens:
A transaction hash is cryptographically generated: 0x97d99bc7729211111a21b12c933c949d4f31684f1d6954ff477d0477538ff017
The transaction is then broadcasted to the network and added to a transaction pool consisting of all other pending network transactions.
A validator must pick your transaction and include it in a block in order to verify the transaction and consider it "successful".
On Electroneum, the IBFT consensus mechanism provides 1-block finality for transactions, meaning that once your transaction is added into a block it is considered "final" and can never be changed or reversed.
Ethereum originally had one format for transactions. Each transaction contained a nonce, gas price, gas limit, to address, value, data, v, r, and s. These fields are RLP-encoded, to look something like this:
RLP([nonce, gasPrice, gasLimit, to, value, data, v, r, s])
Ethereum has evolved to support multiple types of transactions to allow for new features such as access lists and EIP-1559↗ to be implemented without affecting legacy transaction formats.
EIP-2718↗ is what allows for this behavior. Transactions are interpreted as:
TransactionType || TransactionPayload
Where the fields are defined as:
TransactionType - a number between 0 and 0x7f, for a total of 128 possible transaction types.
TransactionPayload - an arbitrary byte array defined by the transaction type.
The Electroneum Smart Chain has introduced a new typed transaction in ETNIP-1, called Priority Transactions. This new transaction type follows the EIP-2718 envelope, where:
TransactionType = 0x40.
TransactionPayload = RLP([nonce, gasPrice, gasLimit, to, value, data, v, r, s, priorityV, priorityR, priorityS])
ETNIP-1 transactions are prioritised by the validators.
