Unlinked, not invisible.
Elypx402 unlinks funding from spending: the wallet that deposits is not the identity that pays vendors. It does not make activity anonymous, and we never describe it that way.
Deposits and withdrawals are still public. Timing, amounts, and network metadata can still correlate activity. We design for real privacy, not a promise we can’t keep.
Where privacy starts and stops
Elypx402 integrates the existing Elysium private rail (ElysiumSwap Private: shielded USDC pools, screening, relayer and ERC-5564 stealth payments). We do not build our own pool, circuit or mixer.
What is public, and what isn’t
Still public
- Deposits and withdrawals
- Timing and amounts, which can still correlate activity
- Network metadata
- That an address has used the private rail
Unlinked by design
- Which deposit funded which payment
- Which vendor an agent paid, from the outside
- How often an agent calls a vendor
An exportable receipt is the other side of this: you can prove a payment to finance or compliance, and reveal only what you choose.
What stays on your device
Private keys, recovery phrases, ZK notes, proofs and payment signatures are generated and held client-side. They never reach our servers.
| Item | Where it lives |
|---|---|
| Recovery phrase | Your device only — shown once |
| Notes, proofs, payment signatures | Your device only — never logged |
| Policy configuration and agent labels | Elypx402 backend |
| Receipt hashes and settlement status | Elypx402 backend — hash and status only, never payloads |
What you are relying on
- The Elysium private rail’s entrypoint is the only upgradeable contract in that stack, controlled by a single MPC-controlled owner.
- Its relayer can be paused.
- Its processor and relayer contracts are disclosed as not yet externally audited as of our most recent check. We re-confirm this before relying on it for real funds, and we don’t round it up to “audited and safe”.