2026-05-09 –, Sladkovský Stage
Most people hear "preconfirmation" and think the job is done. But there's a big gap between knowing your tx will be included vs knowing exactly what state you'll get. This talk breaks down execution preconfs - what they guarantee, how they work, and why they matter for users who don't want surprises when swapping or bridging.
We work on preconfirmation systems at Puffer Finance, where we're building UniFi - a based rollup with execution preconfirmations. So I've spent a lot of time thinking about the difference between "your transaction will be included" and "your transaction will execute exactly like this."
Here's the thing that keeps bugging me: the ecosystem talks about preconfs like they're all the same. But an inclusion preconf and an execution preconf are very different promises. With inclusion, you know your tx gets in a block - but the final state might surprise you. Price moved? Too bad. With execution preconfs, you get a cryptographic commitment to the exact outcome.
I want to give this talk because I think developers and users deserve to understand what they're actually getting. When someone uses a based rollup with preconfs, are they getting a real guarantee or just a "probably fine"?
The talk will cover:
- Quick refresher on why based rollups need preconfs in the first place (the 12-second problem)
- The difference between inclusion and execution guarantees with concrete examples
- How execution preconfs actually work under the hood (gateways, commitments, slashing)
- What this means for DeFi users doing swaps, bridges, or anything price-sensitive
I'll keep it practical and skip the marketing fluff. Just want people to walk away understanding the tradeoffs.
I've been in crypto for more than 5 years and know the material well from building it daily.
Blockchain engineer at Puffer Finance, working on UniFi and preconfirmation systems. 5+ years writing smart contracts and building DeFi stuff. Hackathon mentor. Hardcore developer who likes getting hands dirty with code.