The Engineer’s Guide to Blockchain Finality
Summary: Trail of Bits researchers found that two L2 clients, Juno and Pathfinder, either did not check for finality or used block delays to detect whether Ethereum blocks were finalized, and fixes shipped in Juno v0.4.0 and Pathfinder v0.6.2 after disclosure. The post explains that off-chain applications relying on simple block delays can be hit by re-orgs and double-spend attacks, and that finality conditions differ across probabilistic chains like Bitcoin and provable-finality chains like Ethereum PoS.
What's compelling: An attacker who re-orgs a chain after a deposit is indexed keeps the credited funds in a wallet they still control, and the post notes that renting enough hash power to exceed a low-hash-rate chain's capacity is readily available.
Read the original at Trail of Bits Blog ↗