Priority Messages

When Speed Matters

Sometimes you need your message included now:

• Oracle updates

• Trading signals

• Time-sensitive alerts

• Breaking news

• Emergency notifications

Priority Messages guarantee faster inclusion for those who bid.

How It Works

Priority Messages include a fee bid and are sorted by bid amount (highest first) within each lane batch.

Standard Message (SM)	Priority Message (PM)
Free (VDF proof required)	Bid ≥ MinPMBid
FIFO ordering	Highest bid wins
Wait your turn	Deterministic ordering

MinPMBid is 0.001 OBS (= 1e15 wei)

Signed Debit Authorization

Rather than prepaying fees, Priority Messages include a signed debit authorization. The proposer deducts the bid from the sender's balance at inclusion time. This eliminates stuck transactions and enables more predictable fee markets.

Check current competition:

const status = await provider.send("eth_getMessageBufferStatus", []);
console.log("Top bid:", status.topBid); // Highest bid currently in PM buffer

Reserved Space

Priority messages can't crowd out standard messages. Each lane has dedicated space for both types:

Parameter	Value
SM per lane per slot	2 MB
PM per lane per slot	2 MB
Total per lane	4 MB (SM + PM)
Lane count	8
Total SM per slot	16 MB (8 × 2 MB)
Total PM per slot	16 MB (8 × 2 MB)

Even if PM lanes are busy, SM still gets its dedicated space (and vice versa).

Fee Distribution

Priority Message fees are distributed among protocol participants:

• Block Proposer: 30% - Compensated for including lane headers

• Lane Leader: 20% - Compensated for batching, encoding, and distributing data

• Archive Pool: 50% - Funds long-term data storage infrastructure

Current status: PM bids are burned in the current implementation. Fee distribution will be enabled in a future upgrade.