Network Fee

Overview

Network fees allocate scarce block space and compensate or incentivize validators, miners, sequencers, or other infrastructure. Calculation may depend on transaction size, gas used, compute units, storage, data publication, congestion, and priority bidding. The fee is distinct from a gateway, exchange, bridge, conversion, or withdrawal service fee. On some Layer 2 networks, users pay both local execution and Layer 1 data components. Failed transactions may still consume fees.

Wallets should estimate the complete fee before signing and identify the native asset required for payment. Merchant systems need separate accounting for network and service charges. Fee policies should handle rapid demand changes, replacements, refunds, and insufficient gas without silently reducing the intended recipient amount. A pending quote can change before inclusion, and a transaction that fails at execution may still consume a network fee. Operational systems should store the canonical transaction identifier, inclusion block, execution result, consumed resources, and effective fee reported by the final receipt.

Policies should be tested against low-demand, congested, replaced, reverted, and reorganized transactions. Monitoring should distinguish a pricing error from delayed inclusion or failed execution, since each condition requires a different customer message and recovery action.

Wallet defaults, quoted caps, and minimum protocol charges are different values, so interfaces should label each field and avoid presenting a maximum authorization as the amount ultimately paid. An estimate should identify the fee unit, network, block context, and transaction parameters used to calculate it. Implementation note: Network fees pay for protocol resources and must be distinguished from provider charges, bridge costs, conversion spreads, and recipient amounts.