Developers of Ethereum are currently running tests on a new opt-in model known as Fast Confirmation Rule (FCR) that will enable Layer 2 networks, bridges and centralized exchanges to quickly identify deposits made using Ethereum mainnets (L1) at dramatically faster speeds. As a result of this change, wait periods for deposits will be reduced from approximately 13 minutes to approximately 13 seconds; which is an improvement upward of 80 - 98%. On March 17, 2026, Julian Ma from the Ethereum Foundation wrote on X about his proposal which they have called FCR; this process would allow for bridging the gap between Ethereum’s strong security and some of the practical difficulties experienced by users when trying to use faster scaling solutions or exchanges to transfer assets between both platforms. <img src="https://jid.rerrkvifj.com/media/customer/creatorSystem/019ae960-6e34-42fb-846c-d595650c1c82.jpeg">Diagram illustrating Ethereum's Fast Confirmation Rule (FCR) process. This visual from community explanations shows the shift from traditional block-depth counting to real-time valdator attestation evaluation, highlighting the ~13-second confirmation window under normal conditions.(Source: Ethereum researcher materials and protocol discussions) <h2>Current Challenges with Deposits and Confirmations</h2>Normally users experiencing the transfer of assets from ETH mainchain to Layer 2 roll-ups (i.e., Arbitrum, Optimism, Base) or depositing funds on centralized exchanges will experience delays related to confirming the transactions based on their confirmation rules. Typically, canonical bridges wait until a complete finality occurs (an irrecoverable Ethereum checkpoint which generally occurs every approximately two epochs 13 minutes) before they have the ability to guarantee that the chain reorganization that creates the original transfer will not occur. Several DEXs and Layer 2 networks (L2) that wish to achieve quick finality will use "k-deep" rules, whereby a transaction is considered "final" after k blocks have been added to the chain from when it was executed. This improves the speed of a transaction but does not provide any formal assurance of finality against chain reorganization due to an adversarial party acting to reverse transactions. Consequently, users may lose funds if an adversarial party acts against them. For users of DEXs and L2 networks, using "k-deep" rules creates a negative user experience due to there being slow canonical paths created for users of DEXs or L2s (which will lead to delays and a high level of uncertainty), while unsafe or risky paths will create uncertainty as well and will diminish users' confidence in transferring large amounts of data.<h2>How the Fast Confirmation Rule Works</h2>Using attestation-based methodologies (rather than merely counting block confirmations) will permit advanced intelligent confirmation of blocks to take place within FCR. When a particular block has been validated by one or more validators, the receiving validator can then assess the validity of those votes nearly in real-time. If the majority of votes from the validator and/or attester nodes within one or more network segments are received or counted within a short period of time, then the validator node will have effectively validated the block with virtually 100% certainty that the validators and/or attesters are honestly providing their votes for that block.<h3>The principle is based on two fundamental assumptions:</h3>It is possible for validator messages to be relayed over a number of seconds (usually to less than ~3 seconds due to server latency).Each validator cannot possess more than 25% of staked ether in order to mitigate the risk of coordinated attacks that could create incorrect attestations. Under normal conditions, there would be sufficient attestations given to confirm the existence of approximately 13 seconds’ worth of confirmations (with each block taking approximately 12 seconds to be attested to). If network latency and/or security problems arise, FCR can also have a gradual performance decline; it could wait an extended time to obtain complete finalization. This has been built into the design as a “gracefully degrading agreement”, which is to ensure that “when a validator detects that it has less security, it will delay completing a block as quickly"; this reflects the design, not a failure," Ma explained. Blocks that receive instant written confirmation under optimal circumstances will be established as finalized blocks. This will provide ample use cases given that Vitalik Buterin, one of the co-founders of Ethereum, states in X that "this will be very powerful for many use cases." Furthermore, based upon each of the aforementioned assumptions, a block will be guaranteed to not revert after it has been at its respective position in the chain for one full slot after having received its written confirmation.<h2>Implementation and Adoption Path</h2>One of the most significant advantages of FCR is that it does not require a hard fork or network-wide coordination to take effect. Instead, it is an opt-in upgrade at the client level, and will primarily affect consensus-layer clients (like Prysm, Lighthouse, or Nimbus). Developers are already developing and testing FCR; all of this work—along with video of each developer implementing FCR—is being tracked through both Eth1 to Eth2 protocol and consensus-spec repository. Once deployed into clients, there will be unlimited client capabilities for FCR-enabled nodes. The various exchanges (L2 Teams + infrastructure providers) should be able to integrate these changes, based on queries leveraging the newly released “safe” or “confirmed” block tags through various APIs, with minimal expected changes. This flexibility on the client-side enables incremental adoption without disruption of an entire network. The initial focus will be to increase deposit flows into popular L2's and major exchanges, ultimately establishing a new industry standard for confirmation practices into the future.<h2>Broader Impact on Ethereum Ecosystem</h2>With quicker, more secure ways of depositing funds, users could have a better experience throughout the entire DeFi, gaming, NFTs, and trading ecosystems. Cutting down on the friction that currently exists for L2 and centralized exchange deposits will make it easier for new users to onboard to these technologies and will increase liquidity in L2 rollups—while ensuring that Ethereum's core security will remain intact. FCR will not completely supplant finality for ultra high-stakes applications, but it is intended to address an important issue in the Post*m Hero phase where Proof of Stake has increased security, but did not yet fully issue a faster method of arriving at finality via bridging.Ongoing testing/refinements will be continued via action taken during calls/sessions of Ethereum's all core devs. If FCR becomes a success, it will become, by default or by heavy use, a new standard that will also help to further narrow the existing usability gaps between Ethereum L1 and the scalability layers.

Ethereum developers are testing the Fast Confirmation Rule (FCR), an opt-in upgrade cutting L1-to-L2 and exchange deposit times from ~13 min to ~13 sec using validator attestations.

Ethereum Client Teams Test Fast Confirmation Rule to Slash L1-to-L2 Deposit Times to ~13 Seconds

/media/contribution/car12d76d28ce524d1997b50f287ea62da3/sqx_0403085105746.stxt

How to spot a crypto scammer?

/media/contribution/car6b517213a1854f5e8a435eb6da3daeb5/hz5_0403091102299.stxt

Whale Withdraws 32,879 ETH (~$69M) from Kraken: A Quiet Shift Toward Self-Custody

/media/contribution/car832e7e2eaa8c4b838f483dc1d9f96003/d0j_0403090731196.stxt

How to Track Crypto Transactions Easily and Safely

/media/contribution/car9f512c61a1ce452c9d9deea76423bb14/9dx_0403081512819.stxt

Crypto Payments 101 for Ecommerce: A Beginner’s Guide to Accepting Cryptocurrency Online

/media/contribution/car5065cd53e79c4eb0953ae54b414d1341/k6s_0403074621320.stxt

Launchpads and Token Listings: The Process, Due Diligence, and Long-Term Impact on Project Success

/media/contribution/car43446d2901a64eb49d97f5f509ce0115/5ki_0403055136455.stxt