Transactions

On the ENI blockchain, transactions are essential for any state update, including Token transfers, Account linking, Smart contract execution. While creating an account does not require a transaction, but linking an account to blockchain operations does.

Transaction Types

Since ENI supports both EVM and Cosmos SDK transactions, there are different transaction types based on the execution environment. The following sections provide an overview of Cosmos and EVM transactions on ENI.

Cosmos Transactions

Cosmos transactions are used for interacting with Cosmos based RPC’s and tooling. They consist of the body, auth info, and signatures

Signing Cosmos Transactions

Cosmos transactions on the ENI blockchain follow the standard Cosmos SDK format. They include various types of messages that can be included in the transaction body.

Using the enid CLI, you can use the --generate-only flag to generate an unsigned transaction in JSON format. The transaction can then be signed and broadcasted to the network.

Assuming you have an unsigned JSON transaction file, you can sign it using the enid tx sign command. The signed transaction will be in JSON format and can be broadcasted to the network.

enid tx sign unsigned_tx.json --chain-id $CHAIN_ID --keyring-backend test --from $SIGNER_ADDRESS

EVM Transactions

The ENI blockchain supports Ethereum Virtual Machine (EVM) transactions, allowing compatibility with Ethereum-based tools and smart contracts. The structure of EVM transactions is different from that of Cosmos transactions.