{"id":79904,"date":"2023-06-08T10:16:01","date_gmt":"2023-06-08T07:16:01","guid":{"rendered":"https:\/\/forklog.com\/en\/?p=79904"},"modified":"2025-09-11T13:42:13","modified_gmt":"2025-09-11T10:42:13","slug":"arbitrum-bug-caused-a-brief-disruption-to-transactions","status":"publish","type":"post","link":"https:\/\/u1f987.com\/en\/arbitrum-bug-caused-a-brief-disruption-to-transactions\/","title":{"rendered":"Arbitrum bug caused a brief disruption to transactions"},"content":{"rendered":"<p>On June 7, Arbitrum developers promptly fixed a bug in the sequencer mechanism that caused a brief pause in the execution of transaction batches on Ethereum.<\/p>\n<blockquote class=\\\"twitter-tweet\\\" data-lang=\\\"en\\\">\n<p lang=\\\"en\\\" dir=\\\"ltr\\\">Earlier today, there was a disruption in the Sequencer\u2019s batch poster that caused batches not to be posted. <\/p>\n<p>We&#8217;ll be publishing a full post-mortem later today, but let\u2019s take this chance to look at the high-level overview. <\/p>\n<p>??<\/p>\n<p>\u2014 Arbitrum Developers (?,?) (@ArbitrumDevs) <a href=\\\"https:\/\/twitter.com\/ArbitrumDevs\/status\/1666549893001887744?ref_src=twsrc%5Etfw\\\">June 7, 2023<\/a><\/p><\/blockquote>\n<p> <script async src=\\\"https:\/\/platform.twitter.com\/widgets.js\\\" charset=\\\"utf-8\\\"><\/script><\/p>\n<p>How <a href=\"https:\/\/u1f987.com\/en\/news\/what-is-a-layer%e2%80%912-solution-in-blockchain\">layer-2 network<\/a> Arbitrum aggregates transactions into batches and sends them in a single transfer to Ethereum. This helps reduce the load on the main blockchain and lower fees.<\/p>\n<p>The formation and sending of batches is handled by the sequencer, and the bug was found in the on-chain publication code for the bundles.<\/p>\n<blockquote class=\\\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\\\">\n<p>\u201cImpact: a temporary pause to finalise transactions in the network; otherwise the service was not affected,\u201d the team explained.<\/p>\n<\/blockquote>\n<blockquote class=\\\"twitter-tweet\\\" data-conversation=\\\"none\\\" data-lang=\\\"en\\\">\n<p lang=\\\"en\\\" dir=\\\"ltr\\\">So, where is the bug? Well, it was in the batch poster. <\/p>\n<p>When the Sequencer tried to post a batch on-chain, the bug hit and the transaction reverted.<\/p>\n<p>Impact: A temporary pause to finalize transaction ordering on-chain, but otherwise the Sequencer\u2019s service was not disrupted.<\/p>\n<p>\u2014 Arbitrum Developers (?,?) (@ArbitrumDevs) <a href=\\\"https:\/\/twitter.com\/ArbitrumDevs\/status\/1666549896990662669?ref_src=twsrc%5Etfw\\\">June 7, 2023<\/a><\/p><\/blockquote>\n<p> <script async src=\\\"https:\/\/platform.twitter.com\/widgets.js\\\" charset=\\\"utf-8\\\"><\/script><\/p>\n<p>An unexecuted batch transaction caused desynchronisation of the funding mechanism. It consists of two wallets: the sequencer and the \u201cgas fee reimbursement\u201d. The former inherently has a minimal balance and is replenished programmatically by the latter.<\/p>\n<p>Because the transaction was not completed, the sequencer wallet did not receive reimbursement for the spent ~5 ETH and could not send the next batch.<\/p>\n<p>After the bug was fixed, the mechanism is operating normally.<\/p>\n<blockquote class=\\\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\\\">\n<p>\u201cIn summary, there was a bug in the packet handler, due to which it did not publish them to the network for some time. We will publish a detailed analysis soon, and we are glad that the fault-tolerant system worked properly during the incident,\u201d the developers noted.<\/p>\n<\/blockquote>\n<p>For context, in May <a href=\"https:\/\/u1f987.com\/en\/news\/ethereum-network-records-second-disruption-to-transaction-finalisation\">finalisation failure<\/a> occurred on Ethereum.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>On June 7, Arbitrum developers fixed a bug in the sequencer mechanism that caused a brief pause in the execution of transaction batches on Ethereum.<\/p>\n","protected":false},"author":1,"featured_media":79905,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"select":"1","news_style_id":"1","cryptorium_level":"","_short_excerpt_text":"","creation_source":"","_metatest_mainpost_news_update":false,"footnotes":""},"categories":[3],"tags":[1335,1301,1179],"class_list":["post-79904","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news-and-analysis","tag-arbitrum-arb","tag-blockchain-vulnerabilities","tag-layer-2-solutions"],"aioseo_notices":[],"amp_enabled":true,"views":"28","promo_type":"1","layout_type":"1","short_excerpt":"","is_update":"","_links":{"self":[{"href":"https:\/\/u1f987.com\/en\/wp-json\/wp\/v2\/posts\/79904","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/u1f987.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/u1f987.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/u1f987.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/u1f987.com\/en\/wp-json\/wp\/v2\/comments?post=79904"}],"version-history":[{"count":1,"href":"https:\/\/u1f987.com\/en\/wp-json\/wp\/v2\/posts\/79904\/revisions"}],"predecessor-version":[{"id":79906,"href":"https:\/\/u1f987.com\/en\/wp-json\/wp\/v2\/posts\/79904\/revisions\/79906"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/u1f987.com\/en\/wp-json\/wp\/v2\/media\/79905"}],"wp:attachment":[{"href":"https:\/\/u1f987.com\/en\/wp-json\/wp\/v2\/media?parent=79904"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/u1f987.com\/en\/wp-json\/wp\/v2\/categories?post=79904"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/u1f987.com\/en\/wp-json\/wp\/v2\/tags?post=79904"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}