Settlement happens on-chain and stays verifiable — but the amounts travel sealed. Every payment ships with a notarized .nota receipt, so you can prove delivery without ever exposing the sum. Powered by the cAROUSD confidential rail.
Live on Ethereum mainnet
Not a testnet. Not a simulation. The confidential-payment rail cAROUSD builds on has already settled real payroll live — and the standard behind it was written by the teams defining the category.
First confidential payroll on Ethereum mainnet — executed live by Zama and Bron.
The confidential-token standard, jointly developed by OpenZeppelin, Zama, and Inco.
Institutional backing led by Pantera Capital — the category's first FHE unicorn.
First confidential institutional OTC trade settled on Ethereum — the same rail, validated for capital markets.
Five products on one confidential rail: encrypted settlement, notarized delivery, programmable treasury, compliant identity, and tokenized assets.
Every balance and transfer amount is FHE-encrypted. Only sender and recipient can decrypt their own numbers — yet settlement stays on-chain and auditable to entitled parties.
Explore the railA single signed envelope proves a payment happened — without disclosing the amount. Notarized (EIP-712), anchored on-chain, one per recipient.
See how it worksProgrammable, role-gated disbursement — one Treasury action, many private payouts.
Learn moreA soulbound, revocable membership passport gates every counterparty before funds ever move.
Learn moreTokenized real-world assets settling against sealed stablecoin liquidity, on the same rail.
Learn moreThe .nota envelope confirms a payment landed and was notarized — while the amount stays sealed. Disclosure is opt-in, through the rail's existing regulator flow.
Passing tests across the full contract suite, including encrypted mint / transfer / redeem.
Production Solidity contracts shipped, audited, and hardened.
B2B cross-border flows — the largest payments category by 2030.
B2B stablecoin volume growth over the last 30 months.
No new contracts required — .nota reuses infrastructure already deployed. Verifiable two ways: by signature, no chain needed, or by on-chain anchor, no trust in Xend needed.
confidentialTransfer({ recipients: [ { address: "0x…", amount: { disclosed: false } } ], onChainAnchor: { tokenId: 42 }, signature: { alg: "EIP-712" } }) → ".nota" envelope
Regulatory cooperation is built in, not bolted on. The forced-transfer and disclosure mechanisms exist so privacy and lawful oversight aren't in tension — balances reveal only to an authorized party, on demand.