Ethereum developers are proposing a new confirmation mechanism that could reduce transaction confirmation times to roughly 13 seconds. The change targets a key bottleneck in layer-2 (L2) bridging and exchange settlement speed.
The Fast Confirmation Rule (FCR), introduced by Ethereum researcher Julian Ma, replaces traditional block-counting methods with validator attestations to determine transaction safety. Current systems relying on canonical bridges can take up to 13 minutes for full confirmation, while “k-deep” models offer speed but lack formal guarantees. FCR can be deployed without a hard fork, though client updates and API integration are required.
Can Faster Confirmations Improve Ethereum Settlement Efficiency?
The proposal reflects growing pressure to improve Ethereum’s base-layer usability as L2 adoption accelerates. Faster confirmation times could streamline transfers between Ethereum and downstream platforms, particularly for exchanges and cross-chain applications. By comparison, existing bridging systems often introduce delays that limit capital efficiency and trading responsiveness.
But, the approach introduces new assumptions about network conditions. FCR depends on rapid validator message propagation and requires that no entity controls more than 25% of staked Ether. These thresholds fall below Ethereum’s stricter finality guarantees, raising questions about performance during periods of network stress.
supermajority honest is carrying a lot of weight there. 12s confirmation is useful though if the assumptions hold in practice
— serx (@serxzsz) March 18, 2026
Ethereum co-founder Vitalik Buterin said the mechanism can provide a “hard guarantee” that a transaction will not be reverted after a single slot under favorable conditions. However, some community members argue the reliance on probabilistic safety could expose edge cases, particularly in volatile or adversarial scenarios.
A new fast confirmation rule mechanism lets you get a hard guarantee that Ethereum will not revert after one slot (12 seconds)
— vitalik.eth (@VitalikButerin) March 18, 2026
Security assumptions are (i) supermajority honest, (ii) network latency under ~3s. So one step below economic finality, but very strong for many use…
Still, developers are moving toward implementation, with client teams already testing integrations. If adopted, FCR could reshape how exchanges and L2 networks handle confirmations, with early deployments likely to focus on low-risk use cases before broader adoption across the ecosystem.
