PGA, the Fast Feed, and transaction submission
Dated changes to transaction ordering, the Fast Feed, and transaction submission on Arbitrum One, with links to the pages that explain each one.
This page lists the changes to how orders, publishes, and accepts transactions, newest first. Each section after the list links to the pages that explain one topic.
What changed
All dates are in UTC.
- 2026-10-28: Offchain Labs announced changes to how
eth_sendRawTransactionandeth_sendRawTransactionSyncrespond. The changes are not live yet. Read the transaction submission notice. - 2026-09-23: became the ordering policy on Arbitrum One.
- 2026-09-23: The first ticket round started at 17:00.
- 2026-09-23: Offchain Labs turned off Timeboost on Arbitrum One. Until PGA became active the same day, the ordered transactions .
- April 2025: Timeboost started on Arbitrum One.
PGA replaces Timeboost on Arbitrum One only. Other Arbitrum chains can still use FCFS ordering.
Transaction ordering
With PGA, you bid for an earlier position in the order: you attach a priority fee to your transaction. The sequencer orders transactions in rounds of 125ms.
The Fast Feed
The Fast Feed is a paid WebSocket stream. It publishes each transaction after the sequencer orders and executes it, before the block reaches the standard . The Fast Feed does not change the order of transactions.
Introduction to the Fast Feed
What the Fast Feed publishes, who it serves, and how access works.
Buy Fast Feed access
Buy a ticket each round from the Tickets contract.
Consume the Fast Feed
Connect to the Fast Feed and read its messages.
The sequencer feed and the feed relay
The sequencer feed is free and publishes each block. A Nitro node reads it to follow the chain. A receives the sequencer feed and passes it on to your own nodes.
Read the sequencer feed
The message format of the sequencer feed.
Run a feed relay
Run a feed relay, and connect nodes to it for reliable feed reads.
Sequencer transaction flow
How the sequencer queues, orders, and publishes transactions.
Transaction submission
After an upcoming change, two RPC methods return sooner. If your code treats an eth_sendRawTransaction response as proof of inclusion, read the notice before the change goes live.
How is this guide?