Matrix Transaction Spec

Overview

Matrix transactions are regular BNB L1 transactions whose calldata contains a Matrix payload. Any transaction sent to the Matrix Inbox EOA is later read by Matrix-node and executed on Matrix.

Transaction Format

Matrix transactions use the EIP-2718 transaction type 0x46 (70 in base 10) and contain the following fields:

Field	Description
chain_id	Distinguishes the payload as being relevant only to Matrix • Mainnet: 768945 (0xbbbb1 in hex) • Testnet: 768946 (0xbbbb2 in hex)
to	L2 recipient's address (EOA or L2 contract). Blank for contract creations
value	Amount of GAS being transferred in the transaction
gas_limit	The gas limit of the L2 transaction
data	EVM input data (ABI encoded contract call or contract creation code)
mine_boost	Optional appended data that increases payload size to increase GAS mining (see below)

Important: Matrix transactions have no signature field. The "from" address is inferred from the properties of the BNB Chain transaction in which they are delivered.

Serialization Format

Matrix transactions must be serialized in this specific format for Matrix nodes to process them:

0x46 ++ rlp_encode([chain_id, to, value, gas_limit, data, mine_boost])

Fee Model

Matrix uses a simple execution-only fee model on L2. Matrix transactions do not include priority fees, tip fields, or max fee fields. All Matrix executions consume Matrix L2 gas, with the base fee computed by the Matrix protocol.

The user only pays BNB L1 gas for submitting the envelope transaction. No additional fee markets or sequencer fees exist.

Execution on L2 (Derived Transaction Type)

Matrix payloads are executed on L2 as derived transactions, produced directly from BNB L1 calldata. These L2 execution transactions contain the following fields:

• sourceHash — hash linking the L2 execution to the originating L1 envelope

• from — inferred from the L1 transaction signer

• value — amount of WGAS (or other L2 asset) transferred

• gas — L2 gas allocated for execution

• isSystemTransaction — indicates system-level derivation

• data — ABI-encoded Matrix calldata

Matrix does not mint tokens during execution, and the execution hash is computed independently of any L1 value. All state transitions are derived deterministically from BNB L1 ordering.

For detailed field definitions and hashing rules, see Reference → Chain State Derivation.