zkDeal engineering
One bounded room. Seven ways to put it to work.
A numbered seven-part series that turns zkDeal architecture into public-source tutorials you can run today.
VII → I
Explore the articles
Start with what you can run, then work down through settlement, market policy, and the core room model.
- Part 1VII
Run the supplied Docker stack—or customize any role
Start with zkDeal’s published Docker operating planes, inspect a digest-pinned CUDA prover, and learn where customization keeps the proof and settlement boundaries intact.
- Part 2VI
Specialized validity systems and Stage-aligned room profiles
Separate proof systems from settlement models, choose a zkDeal room inside a deployment envelope, and exercise today’s trust-root and fallback boundaries.
- Part 3V
zkDeal vs shared-L2 proof stacks
Compare a finite, policy-bound zkDeal room with shared L2 proof bases, then inspect and test the public room-node execution boundary.
- Part 4IV
Three ways capital returns to Ethereum L1
Compare canonical return paths, separate fast confirmation from L1 release, and run the public escrow, refund, claim, and terminal-exit contract tests.
- Part 5III
Prove the market rule you choose
See how the same signed intents behave under priority ordering, arrival FIFO, and commit-reveal—and why zkDeal proves the selected room rule without claiming universal MEV elimination.
- Part 6II
From a one-checkpoint clear to an eight-hour market
Map one-shot, rolling, and sparse market rooms to concrete DvP, lifecycle, coordinator, and proof-queue tests available in the public zkDeal repositories today.