Cardano

Taiko

Base

Read

<p class="is-style-lead">Base has explained why its mainnet stopped producing blocks twice in two days.&nbsp;</p><div id="cn-block-summary-block_6d13685d72869799bf233c1677c6f3c9" class="cn-block-summary"><div class="cn-block-summary__nav tabs"><span class="tabs__item is-selected">Summary</span></div><div class="cn-block-summary__content"><ul class="wp-block-list"><li>Base’s latest postmortem shows one sequencer bug caused two mainnet halts within two straight days.</li><li>Funds stayed safe, but transaction queues overflowed as Base stopped producing new L2 blocks temporarily.</li><li>The team plans stronger fuzz tests, load tests, monitoring, and recovery tools after the outage.</li></ul></div></div><p>The Coinbase-backed Ethereum layer-2 network said both outages came from the same bug in its sequencer block-building logic.</p><p>The first outage began on June 25 and lasted about 116 minutes. The second began on June 26 and lasted about 20 minutes. Base said funds stayed safe during both incidents.</p><p>You might also like: <a href="https://crypto.news/taiko-sets-four-step-restart-plan-after-june-21-bridge-attack/" rel="noopener noreferrer nofollow"> Taiko sets four-step restart plan after June 21 bridge attack </a></p><h2 class="wp-block-heading" id="strong-sequencer-bug-stopped-block-production-strong"><strong>Sequencer bug stopped block production</strong></h2><p>In its <a href="https://blog.base.dev/postmortem-june-25th-block-production-outage" rel="noopener noreferrer nofollow">official postmortem</a>, Base said an invalid transaction failed during execution, as expected. The issue came after that failure, when stale journal state remained inside the block builder.</p><figure class="wp-block-embed is-type-rich is-provider-x wp-block-embed-x"><div class="wp-block-embed__wrapper"><blockquote class="twitter-tweet"><p>On June 25 and 26, Base mainnet experienced two block production outages, both caused by the same underlying bug in the block builder logic.<br><br>We’ve identified and fixed the root cause, and have communicated the post mortem to OP chains as feedback.<br><br>All funds were safe… <a href="https://t.co/eArnK12AgZ" rel="noopener noreferrer nofollow">pic.twitter.com/eArnK12AgZ</a></p>— Base Build (@buildonbase) <a href="https://x.com/buildonbase/status/2070896671349948442?ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow">June 27, 2026</a></blockquote></div></figure><p>That stale state included accounts and storage slots touched by the failed transaction. When a valid transaction came next, the system used the wrong journal state and charged gas incorrectly.</p><p>This created a block with an invalid state transition. Other nodes could not accept the block, so the chain stopped producing new L2 blocks.</p><blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p>“The integrity of the chain was not compromised and all funds on Base were safe,” Base said.</p></blockquote><p>The team added that block production resumed safely after mitigation.</p><h2 class="wp-block-heading" id="strong-transactions-queued-during-the-halt-strong"><strong>Transactions queued during the halt</strong></h2><p>During the outages, users could not get new transactions included onchain. Base said transactions queued in the mempool while the chain waited for block production to recover.</p><p>The transaction pool later grew beyond what it could store. As a result, new eth_sendRawTransaction requests returned errors during the outage window.</p><p>The halt also affected sequencer and validator progress. Base said these nodes could not move beyond the invalid block until sequencing returned.</p><p>As <a href="https://crypto.news/coinbase-backed-base-returns-after-2-hour-consensus-halt/" rel="noopener noreferrer nofollow">previously reported</a>, Base first flagged unhealthy block production on June 25 before engineers isolated a consensus problem tied to an invalid block.</p><h2 class="wp-block-heading" id="strong-patch-fixed-stale-state-issue-strong"><strong>Patch fixed stale state issue</strong></h2><p>Base said it fixed the main bug by applying a sequencer patch. The patch ensures journal state updates properly during execution after a failed transaction.</p><p>The team also found a second issue during recovery. Base said mitigation took longer because a race condition in the engine reset feature stopped sequencers from catching up after restart.</p><p>That second issue helped explain why the incident returned the next day. Base said the problem affected sequencers, not validator nodes, but it still slowed recovery.</p><p>The <a href="https://status.base.org/" rel="noopener noreferrer nofollow">Base status page</a> showed sequencing resumed on June 25. It also told ecosystem node operators to restart Base nodes if they were still stuck.</p><h2 class="wp-block-heading" id="strong-testing-and-recovery-changes-planned-strong"><strong>Testing and recovery changes planned</strong></h2><p>Base said it will strengthen protocol fuzz testing and load testing. These methods help teams find strange transaction patterns that may expose hidden bugs.</p><p>The team also plans better monitoring and operational checks. It said these changes should help engineers detect similar problems earlier and respond faster.</p><p>Base also wants to add graceful recovery to base-consensus. That change would make it easier for validator nodes to continue syncing after similar failures.</p><p>The outage came during a busy week for the network. Base also moved forward with its <a href="https://crypto.news/base-delays-beryl-upgrade-by-one-day-ahead-of-b20-activation/" rel="noopener noreferrer nofollow">Beryl upgrade</a>, which adds the B20 token standard and cuts the standard Base-to-Ethereum withdrawal period from seven days to five days.</p><p>The incident gives developers and users a clearer view of the weak point. Base has now named the bug, released a patch, and listed the tests it plans to improve.</p><p>Read more: <a href="https://crypto.news/secondfi-keeps-two-week-recovery-plan-after-2-4m-cardano-wallet-exploit/" rel="noopener noreferrer nofollow"> SecondFi keeps two-week recovery plan after $2.4M Cardano wallet exploit </a></p>

Base says same sequencer bug caused June 25 and 26 outages

Table of Contents

crypto.news

Other articles published on Jun 28, 2026

Tether brings $23B gold push into crypto-backed loans

Bitcoin trades near $60,100 as analysts focus on $58,000 support and key resistance at $63,600

San Antonio takes action against $39 million crypto scam losses! What are the new rules?

Bitcoin miners hold strong despite margin pressure

Tether Gold Integrates With Ledn, Targets XAUT-Backed Mortgage Lending in 2026

Pi2Day is here, and 60 million Pioneers are watching for what drops

Join our free newsletter for daily crypto updates!