Transaction Type

Overview

How it works

A transaction type selects the rule set applied to a transaction. In Ethereum, typed envelopes allow different field layouts and fee mechanisms to coexist. Other networks classify transactions by message version, action code, module entry function, or instruction set. The type can affect required fields, signature preimage, fee calculation, replay protection, and node compatibility.

Protocol type should be distinguished from business categorization. A payment processor may label a transaction as deposit, refund, or payout even though all three use the same on-chain type. Conversely, one business payment can involve several protocol types across approval, swap, and settlement steps. Both classifications are useful, but they answer different questions.

Unknown or unsupported types require safe handling. A decoder should not force unfamiliar bytes into a legacy schema, because the same positions may have different meanings. Hardware wallets and signing services must understand type-specific fields before asking for authorization. New types introduced through upgrades may also change replacement or fee-bumping behavior.

Infrastructure should store the native type identifier, protocol version, decoded fields, and original Transaction Envelope. Monitoring and analytics should avoid grouping transactions solely by method name when the envelope changes security or pricing properties. Compatibility testing should cover every type that an application can construct, sign, submit, and reconcile.

Audit and recovery workflows should preserve the native type code, protocol version, decoder used, signing rules, fee model, and receipt interpretation. These records help because a business label such as payout or refund does not identify the consensus format that nodes process. Production safeguards need to fail safely on unknown types and maintain compatibility tests for construction through reconciliation.

What matters in practice

Protocol transaction types change decoding and signing rules. Ethereum, for example, uses transaction envelopes to support different fee fields and capabilities. A decoder must identify the type before interpreting fields; treating new binary data as an older format can misread what the user authorized. Business labels such as 'deposit' or 'refund' are not protocol transaction types. One customer checkout can involve a token approval and a transfer, each with different execution behavior. Wallet prompts should display decoded contract effects rather than only a generic type number.

Related glossary concepts

Transaction; Transaction Envelope; Transaction Body