NoxSend
Live on SepoliaERC-7984 · Intel TDXZero mock data

Etherscan sees
32 bytes.
Your landlord sees nothing.

Private send for the wallet you already have. Wrap USDC into confidential cUSD (ERC-7984), send with the amount encrypted end-to-end inside Intel TDX via iExec Nox, and reveal it only to whom you choose.

Watch it live on-chain →

MetaMask or Rabby · Ethereum Sepolia · read-only until you act · nothing installed or modified

Private send · preview
to
0x71C7…9f2
amount
0x9f3a··2b1c
Sealed — Etherscan sees a 32-byte handle

Same transaction, two views. The chain — and your landlord — only ever see the handle on the left. The value is decryptable solely by the recipient and anyone you explicitly grant.

Verify every claim yourself — zero mock
Liveon Ethereum Sepolia
0tests passing
0%contract coverage
TDXERC-7984 · Intel TDX
Open /verifyView on GitHub ↗Pitch deck ↗Verified cUSD contract ↗

/verify streams live Sepolia events and a live ACL inspector — zero mock. Every on-chain step has a real proof tx in the README.

The one flow — narrow and deep
1Wrap USDC → cUSD

Deposit the USDC you already hold. Get confidential cUSD 1:1 (ERC-7984), redeemable.

2Private send

The amount is encrypted before it hits the chain — calldata carries only a 32-byte handle.

3Reveal to whom you choose

Recipient decrypts via viewer ACL. Grant an auditor if you say so — no one else can read it.

4Claim-link · unwrap

Wallet-less recipients get a claim link. Redeem cUSD back to USDC, proof-gated.

Why judges can trust it
On real infraNot a stub

Runs against the live Nox Handle Gateway inside Intel TDX on Ethereum Sepolia. Wrap, send, grant, claim and unwrap each land a real proof transaction.

On your walletNothing modified

The MetaMask/Rabby you already have and the USDC you already hold — untouched. Privacy lives inside cUSD, added around them, never inside them.

Honest by designAmount-privacy, stated plainly

Addresses stay public and wrap/unwrap is visible at the boundary. We say so on the page, in the README and in the demo. No overclaiming.

How it works · FAQ
Do I need a new wallet or a new chain?
No. NoxSend uses the MetaMask or Rabby you already have, and the USDC you already hold — neither is modified. It runs on Ethereum Sepolia via the wagmi injected connector.
Is the amount really hidden?
Yes. The amount is encrypted by the Nox Handle Gateway inside Intel TDX before it ever touches the chain — the transaction calldata carries only a 32-byte handle, not the value. Etherscan sees 32 bytes.
Is this a mock or a demo stub?
No. It is live on Ethereum Sepolia against the real Nox Handle Gateway, zero mock data. Wrap, private send, auditor grant, claim-link and unwrap each have a real proof transaction — open /verify to watch events stream live.
Who can see my balance and transfers?
Only you, by default. Decryption is a viewer-gated, EIP-712-signed request to the Nox TEE gateway. The recipient can decrypt via the viewer ACL, and you can grant an auditor with a single addViewer call — no one else can read it.
What's the honest limitation?
Amount-privacy only. Sender and recipient addresses stay public, and wrap/unwrap amounts are visible at the wrapper boundary. Privacy lives inside cUSD. It uses a pinned beta SDK (@iexec-nox/handle) and trusts Intel TDX + iExec gateway liveness.
How does a recipient without a wallet get paid?
Via a claim link — a self-custodial escrow (SendLinkEscrow) funded by a time-bound operator grant that auto-revokes right after funding. If it is never claimed, you can reclaim it after expiry.
Ready when you are

Send a number only the right people can read.

Connect the wallet you already use — read-only until you act. Then watch the amount turn into a 32-byte handle, live on Sepolia.

See live proof →