As most of CT knows, Flashblocks launched on Base Mainnet 3 days ago. I wanted to share 2 quick learnings after helping build out this feature as one of the engineers:.

Flashblocks FAQs page is live! . Would encourage anyone for flashblocks related questions to check out this page first. If the answer is not there and not other docs, feel free to lmk.

Anyone else feel weird if the current value prop for ETH is also strategic reserve? If that’s the current value prop it feels more like institutional fomo created bubble? Happy to be proven wrong.

why is there like no good TEE development examples out there? Like setting up an application e2e using aws nitro or something.

Frontier day 1 talk notes (Fireside chat with Tomasz and Georgios). How to describe Ethereum.- World computer. Motivation in Crypto.- Always things to build.- Building for world computer, things will last for a long time. Ethereum with stablecoin + RWA.- institutions are asking

Eventually, the mined txs are streamed to RPC nodes/websocket as part of the flashblocks data. Eventually served to the end users. If the txs get tail reorged, they typically go through the block building loop one more time in the following block.

Thus even if you pay a high fee but the tx is large (> 10M gas), it will still have a harder time to get mined. This is due to how the builder allocates gas, it incrementally adds 1/10th of the total block gas limit to every flashblock. More info here:.

The builder picks the txs from the txpool based on 3 factors.- Tx gas limit.- Remaining gas available in the flashblock.- Tx fee. The higher the fee, the higher chance it gets included unless the tx gas limit is over the remaining gas available. (Code: .

So now, the mempool also p2p gossips the txs to the builder. The builder stores those pending txs in its own txpool and every 200ms it picked txs out of the txpool to mine.

As mentioned in my previous tweet, the simple architecture of the flashblocks system. We added a builder component that handles flashblocks block building.

How a transaction gets included on Base previously.1. A tx is submitted and goes into the private mempool.2. Mempool p2p gossip pending txs to the sequencer, stored in sequencer's txpool.3. The sequencer picks txs out of its txpool in each block building loop

What's the lifecycle of a flashblock transaction? (Explainer below).

That's it! We will hopefully provide update on this topic as we improve things in the next coming weeks :).

What's the implication?. If your app relies on block related data (e.g. block_number) from the preconfirmation tx receipt, and a mismatch could break your internal state or logic, you should be cautious about this when integrating. We don't yet guarantee no tail reorgs (or type.

Right now, type 1 accounts for 99% of the reorgs. Type 2 only happens during significant chain instability. Based on our stats, roughly 1 in 250 blocks experience tail flashblocks reorg, and because those are tail flashblocks, the number of impacted transactions are small (~5.

What is a flashblocks reorg?. A flashblocks reorg happens when transactions are preconfirmed in block X, but end up being included in a later block—block X + N. There are currently two types of reorgs:. 1. Tail flashblock reorgs - This is where the last flashblock in block X.

A quick recap of the flashblocks system architecture (very simplified). 1. The sequencer notifies the flashblocks builder to build a new block.2. Builder sends out flashblocks stream to RPC nodes as it builds flashblocks.3. Sequencer requests for a finalized block back.4.

Been getting reached out about flashblocks reorgs on Base this week both internally and externally, wanted to share a quick explainer for anyone else digging into this, hopefully it can serve as a useful reference!.

RT @_jxom: Viem 2.33 introduces initial support for Flashblocks as a first-class citizen! . Try it out in Viem or Wagmi by importing a chai….

Integration guide: Eng blog:

If you’re a user: try out the new instant UX in your favorite app. If your fav app hasn’t integrated—suggest it!. If you’re a dev: check out the docs and start testing with a Flashblock-aware RPC endpoint.