Skip to main content
Extended information about the current transaction.

Signature

Members

version

The version of the transaction. It is fixed (currently, 1) in the OS, and should be signed by the account contract. This field allows invalidating old transactions, whenever the meaning of the other transaction fields is changed (in the OS).

Signature

account_contract_address

The account contract from which this transaction originates.

Signature

max_fee

The max_fee field of the transaction.

Signature

signature

The signature of the transaction.

Signature

transaction_hash

The hash of the transaction.

Signature

chain_id

The identifier of the chain. This field can be used to prevent replay of testnet transactions on mainnet.

Signature

nonce

The transaction’s nonce.

Signature

resource_bounds

A span of ResourceBounds structs used for V3 transactions.

Signature

tip

The tip of the transaction.

Signature

paymaster_data

If specified, the paymaster should pay for the execution of the transaction. The data includes the address of the paymaster sponsoring the transaction, followed by extra data to send to the paymaster. Used for V3 transactions.

Signature

nonce_data_availability_mode

The data availability mode for the nonce. Used for V3 transactions.

Signature

fee_data_availability_mode

The data availability mode for the account balance from which fee will be taken. Used for V3 transactions.

Signature

account_deployment_data

If nonempty, will contain the required data for deploying and initializing an account contract: its class hash, address salt and constructor calldata. Used for V3 transactions.

Signature