## # Transaction

Transactions here refer to operations initiated by externally owned accounts, i.e. accounts managed by humans, not contracts.

### # Trading Information

• 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
• value – amount of BTM to transfer from sender to recipient
• data – optional field to include arbitrary data
• gasLimit – the maximum amount of gas units that can be consumed by the transaction. Units of gas represent computational steps
• maxPriorityFeePerGas - the maximum amount of gas to be included as a tip to the miner
• maxFeePerGas - the maximum amount of gas willing to be paid for the transaction (inclusive of baseFeePerGas and maxPriorityFeePerGas)

### # Example

The transaction object will look a little like this:

{
from: "0xEA674fdDe714fd979de3EdF0F56AA9716B898ec8",
to: "0xac03bb73b6a9e108530aff4df5077c2b3d481e5a",
gasLimit: "21000",
maxFeePerGas: "300",
maxPriorityFeePerGas: "10",
nonce: "0",
value: "10000000000"
}


### # Transaction Type

• On BMC there are a few different types of transactions:
• Regular transactions: a transaction from one wallet to another.
• Contract deployment transactions: a transaction without a 'to' address, where the data field is used for the contract code

### # Transaction Life Cycle

Once the transaction has been submitted the following happens:

1. Once you send a transaction, cryptography generates a transaction hash: 0x97d99bc7729211111a21b12c933c949d4f31684f1d6954ff477d0477538ff017
2. The transaction is then broadcast to the network and included in a pool with lots of other transactions.
3. A miner must pick your transaction and include it in a block in order to verify the transaction and consider it "successful".
• You may end up waiting at this stage if the network is busy and miners aren't able to keep up.
1. Your transaction will receive "confirmations". The number of confirmations is the number of blocks created since the block that included your transaction. The higher the number, the greater the certainty that the network processed and recognized the transaction.
• Recent blocks may get re-organized, giving the impression the transaction was unsuccessful; however, the transaction may still be valid but included in a different block.
• The probability of a re-organization diminishes with every subsequent block mined, i.e. the greater the number of confirmations, the more immutable the transaction is.
Last Updated: 1/13/2022, 4:47:56 PM