Einstein Hooks v2First pool is live
Every claim has a link. Or it says pending.
A real pool, NVDA/USDG, is open on Robinhood Chain with about 1 USD in it. Below is what has been proven on mainnet, what has not, and the transaction behind each line.
- 7proven
- 2partly proven
- 2pending
- 0failed
of 11 claims, replayed against mainnet on 2026-11-20
745a56cA016502c3e5571070ac64E3Be9EBd2cc0
- before initialize
- after initialize
- before add liquidity
- after add liquidity
- before remove liquidity
- after remove liquidity
- before swap
- after swap
- before donate
- after donate
- before swap return delta
- after swap return delta
- after add liquidity return delta
- after remove liquidity return delta
The pool
- Pair
- NVDA/USDG
- Created in block
- 114,372,026
- Creation transaction
- 0x440c71e4…ce465b63
- Position
- #7
- Service fee
- 49 USDG, paid at creation
- Swap Lens, exact match
- 0x6b983bd5…b2879435
Claims
A claim is proven only when every one of its checks holds on chain. Partly proven means true but short of the bar. Pending means there is nothing on chain to check yet.
- P1Partly proven
The code is what we say it is
1 of 16 contracts are an exact match on Sourcify, and the other 15 are a match
- P2Proven
Nothing here can be changed later
EIP-1967 slots are zero on all 15 deployed contracts and on the first pool hook.
- P3Proven
The hook has only the permissions we say
The hook 0x745a56cA016502c3e5571070ac64E3Be9EBd2cc0 has low 14 bits 0x2cc0, and the remove-liquidity bits 9, 8 and 0 are off.
- P4Proven
The pool is real and holds liquidity
Pool created and seeded in one transaction at block 114372026; the 49 USDG service fee was paid, and position 7 holds liquidity.
- P5Proven
The calendars were signed post-quantum
Three governance calls succeeded on SafetyControllerV2, and the GOVERNANCE leaf counter is past 3 (leaves 1 to 3 spent on the calendars; later leaves were spent on a pool resume). Roots are queued by the GOVERNANCE role, not REPORTER.
- P6Proven
Session fees apply
A real swap in each session shows the matching fee in the Swap event: CLOSED, OVERNIGHT, PRE, REGULAR, POST.
- P7Pending
The auction works with real orders
The first auction cycle closed on 16 November with no orders in it: the script that places them started after the ten-minute window. The next cycle opens its order window on 23 November at 00:50 UTC. The same auction code ran a full cycle on the Elysium testnet on 7 November (not a mainnet proof): a sell and a buy order, settle in transaction 0xc1fed537d9757417c9a576b7a59b9371efdb19e44c1fbb440fe640d6db849eda, one clearing price of 99 USDG per stock, and an ordinary swap during the window reverted (transaction 0xf72e2336ea9b451c19e31f72aae7e06226021870b677e8a83780c7d94a348e80). Evidence: evidence/deploy/elysium-testnet-tests.json.
- P8Proven
You can always get out
The LP removed part of the position through the PositionManager both during CLOSED and while the pool was paused with both signatures. Neither exit called the hook or needed a post-quantum signature.
- P9Partly proven
- P10Proven
What post-quantum verification costs
The same pause costs 323,735 gas with both signatures on mainnet and 70,433 gas with ECDSA only on a fork of mainnet, about 4.6 times more.
- P11Pending
Anyone can check all of this
The script runs from a clean clone of the public repo against a mainnet RPC, and it reported no failure on 16 November and again on 18 November from a fresh shallow clone at commit 03b2e56: 13 PASS, 2 PARTIAL, 3 PENDING, 0 FAIL. It will print PASS for P2 to P9 once the auction is on chain and the Sourcify and N6 gaps are closed.
What the post-quantum signature costs on mainnet
- AAPL hybrid-signed governance queue622,899 gas
- NVDA hybrid-signed governance queue589,764 gas
- TSLA hybrid-signed governance queue590,742 gas
- hybrid-signed pause (GUARDIAN)323,735 gas
The same pause with ECDSA only costs 70,433 gas, measured on a fork of mainnet, and with both signatures it costs 323,735 gas on mainnet.
What must fail
Each attempt has to revert with the named error, and the reverted transaction stays on chain as the proof. A test that is not proven yet has not been sent to mainnet.
N1Reverted on mainnet
Calendar root signed with ECDSA only
Reverts with
The reverted transactionInvalidPQSignatureN2Reverted on mainnet
Valid ECDSA with a SHRINCS signature from the wrong key
Reverts with
The reverted transactionInvalidPQSignatureN3Reverted on mainnet
Reuse a SHRINCS leaf that was already spent
Reverts with
The reverted transactionLeafOutOfOrderN4Reverted on mainnet
Pause through SafetyControllerV2 with ECDSA only
Reverts with
The reverted transactionInvalidPQSignatureN5Reverted on mainnet
Swap above the per-trade cap
Reverts with
The reverted transactionTradeCapExceededN6Not sent yet
Ordinary swap during the auction window
Reverts with
AuctionActiveNot yet sent on mainnet.
N7Reverted on mainnet
Swap with no valid session for the timestamp
Reverts with
The reverted transactionPolicyBlocked
Next on the clock
Order window opens in
--d--h--m--s
Monday 23 November at 00:50 UTC, for ten minutes, 00:50 to 01:00 UTC
- Opening Bell AuctionThe first cycle, on 16 November, closed with no orders because the script that places them started after the ten-minute window. The next one is the weekend close ending 23 November. A buyer and a seller, from two different wallets, put orders in during the ten minutes before the market opens, and the orders clear at one price.
- Sessions that openRegular, pre, post and overnight swaps need a keeper to activate each session. The keeper for this stack activated the overnight session on 16 November, and the pool swapped in it.
- Pre and regular session swapsThe pool opens its pre session at 09:00 UTC and its regular session at 14:30 UTC on 16 November. A swap is queued for each, and the fee in the Swap event is what counts.
Check it yourself
One script, Node 20 and a public RPC. No keys, no team API. It reads every address and transaction from proof.json and prints a line per claim, and it exits with an error if anything fails.
git clone https://github.com/belldex/bell && cd bell
node scripts/einstein/verify-einstein-pool.mjs --rpc https://rpc.mainnet.chain.robinhood.comP1 PARTIAL The code is what we say it is P2 PASS Nothing here can be changed later P3 PASS The hook has only the permissions we say P4 PASS The pool is real and holds liquidity P5 PASS The calendars were signed post-quantum P6 PASS Session fees apply P7 PENDING The auction works with real orders P8 PASS You can always get out P9 PARTIAL What fails, fails safely P10 PASS What post-quantum verification costs P11 PENDING Anyone can check all of this
Honest limits
- Wallets still sign with ECDSA. Only BELL's own governance and reporting calls use the post-quantum layer.
- No independent cryptographic review has been done.
- A pause and a resume were exercised on mainnet: one GUARDIAN leaf and one GOVERNANCE leaf were spent, and the pool trades again.
- Only one pool uses the Einstein hook, and it is seeded with about 1 USD.
- The five post-quantum contracts are a Sourcify match, not an exact match.