Skip to main content
Last reconciled 2026-08-06.

​
Live on testnet

The settlement v3 accumulating-pool rail is the product and it works end to end. A full programmatic run per chain — deploy pool and forwarder, pay 1 USDC, sweep, distribute, claim — was RPC-verified on every EVM testnet. The merchant netted 985050 base units of 1000000, which is 98.505%.

​
Not live

contracts/deployments.json has an empty mainnet object. No contract is deployed to any mainnet. This is deliberate — each chain requires explicit human GO.
Mainnet is gated on four external items, none of which are engineering work:
  • Third-party security audit
  • Immunefi bug bounty live
  • MiCA counsel sign-off
  • Explicit per-chain GO from the founder
The keeper wallet is also unfunded on every mainnet, which is a separate launch blocker.

​
Designed, decided, not built

These have locked designs and open Linear issues. They are the current build queue.

​
Explicitly rejected

Recorded so they are not re-proposed. Full reasoning in Gas reimbursement and Clone decisions.
  • Cloning the pool, on either EVM or TRON
  • Claim-gating (requiring gas repayment before a merchant can claim)
  • Merchant-signed sweeps as the default path
  • One-time delegated signing for sweeps
  • Merchant native-gas escrow
  • Deducting the gas reimbursement inside the forwarder at sweep time

​
Blocked on measurement

Three gates block the contract cutover. All are cheap; none are optional.
1

Dynamic Energy Model attribution

Does TRON attribute delegatecall energy to the implementation or the proxy? Decides whether per-customer forwarders can be clones. Irreversible once proxies are deployed.
2

Like-for-like forwarder sweep

Three inconsistent forwarder measurements exist across issues, and one reports a cloned sweep as cheaper than the original, which a proxy cannot do. Re-measure the same logic both ways on one harness.
3

0x41 CREATE2 re-derivation

Must be re-proven on Nile for any new forwarder init code before an address is ever shown as a QR. A prefix or bytecode mismatch strands funds permanently.

​
Production infrastructure

  • Supabase project pocyrcfbpfvthtyvupqk, fully provisioned, all edge functions deployed.
  • Vercel project cryptocheckout-ai (prj_ev4UHfhlyOQmvaZ2eiUCr9fs0Hih), owns the apex and www.
  • Live site reports zero console errors on /, /verify, and the demo widget panel.