> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cryptocheckout.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Status

> What is live, what is designed but unbuilt, and what is blocked. Check this before assuming any behaviour exists.

Last reconciled 2026-08-06.

## Live on testnet

The settlement v3 accumulating-pool rail is the product and it works end to end.

| Capability                                         | Where                      |
| -------------------------------------------------- | -------------------------- |
| Connect rail (`deposit()` direct into pool)        | 6 EVM testnets             |
| Deposit rail (forwarder → keeper sweep → pool)     | 6 EVM testnets + TRON Nile |
| Permissionless `distribute()` + pull `claim()`     | All of the above           |
| `0x41` CREATE2 derivation proven on TRON           | Nile, verified 2026-06-19  |
| Chain-agnostic settlement, late-payment monitoring | Shipped                    |
| Merchant dashboard, pool-only                      | Shipped 2026-07-01         |
| Sanctions screening (merchant + opt-in payer)      | Shipped                    |
| Partner referral attribution, five layers          | Shipped                    |

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

<Warning>
  `contracts/deployments.json` has an empty `mainnet` object. **No contract is deployed to any mainnet.** This is deliberate — each chain requires explicit human GO.
</Warning>

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.

| Area                                              | Summary                                                                                                                                              |
| ------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Gas reimbursement](/economics/gas-reimbursement) | Merchant bears deposit-rail sweep gas, recovered in the settlement token inside `distribute()`. Replaces the bps-incentive netting that ships today. |
| Forwarder cloning                                 | EIP-1167 minimal proxy per invoice. 78% gas saving on EVM, 88% on TRON. Confirmed for both chains.                                                   |
| Merchant-paid pool deploy                         | Pool deployment becomes a prerequisite for SDK and iframe access. Removes the keeper's unbounded lazy-deploy exposure.                               |
| TRON connect rail                                 | `MerchantPoolTron.deposit()` direct. TRON is currently deposit-rail only. GO given 2026-08-05.                                                       |
| Merchant cost tolerance                           | A single percentage that becomes a dynamic per-chain minimum, replacing static `rail_minimums`.                                                      |
| Energy rental on TRON                             | 60–80% off every TRON operation, no code or contract change.                                                                                         |

## Explicitly rejected

Recorded so they are not re-proposed. Full reasoning in [Gas reimbursement](/economics/gas-reimbursement) and [Clone decisions](/economics/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.

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## 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.