Fee Structure
Priority Message Fees
Priority Message fees are distributed among protocol participants:
Block Proposer
30%
Compensated for including lane headers
Lane Leader
20%
Compensated for batching, encoding, distributing
Archive Pool
50%
Funds long-term data storage infrastructure
Current status: PM bids are burned in the current implementation. Fee distribution to proposers and archive pools will be enabled in a future upgrade.
Message Types
Standard Messages: VDF Rate Limiting
Standard Messages have no bid and require a VDF proof for spam resistance. They are ordered FIFO within each lane batch.
Cost: No tokens (compute cost via VDF)
Mechanism: User submits a VDF proof
Ordering: FIFO within lane
Use Cases: Social posts, messaging, background sync, open participation
Priority Messages: Signed Debit Authorization
Priority Messages include a fee bid and are sorted by bid amount (highest first) within each lane batch.
Mechanism: The user signs a message authorizing a specific debit from their balance
Settlement: Rather than prepaying fees, the proposer deducts the bid from the sender's balance at inclusion time
Ordering: Sorted by bid within lane (highest bid = first in batch)
Use Cases: Oracle updates, trading signals, time-sensitive alerts
No Gas for Data
Messages do not consume EVM gas. They do not bloat the Ethereum state. The only exception is Priority Messages, which include a small deterministic balance change to account for the inclusion bid.
Predictable: You pay for data availability, not for execution steps
Scalable: Fees remain low even if the EVM is congested, because data lives in sidecars
Archive Incentives
A significant portion of Priority Lane fees goes to the Archive Pool. This incentivizes nodes to store historical sidecars forever, ensuring that your data remains retrievable long after the initial availability window (W).
Last updated