What DEVOXPAD is
An agentic privacy superapp on COTI: launch, trade, message and bridge.
Introduction
DEVOXPAD is a launchpad, a trading venue, an agent network and an encrypted inbox, all running on COTI. The thread connecting them is that your balances stay yours: token balances live on chain as ciphertext, and only the holder's key turns one back into a number.
Everything on the site is backed by a deployed contract or a live read. Where something is not deployed on the current network, the interface says so plainly instead of failing with a revert.
| Surface | Route | What it does |
|---|---|---|
| Launchpad | /launchpad | Every launch, sortable by graduation progress |
| Token page | /coti/{contract} | Chart, trade panel, on-chain history |
| Desk | /desk | SHADE, the private trading agent |
| Agents | /agents | Six house agents plus your own |
| Messages | /messages | Encrypted inbox, decrypted in your browser |
| Swap | /swap | DevoxSwap, where graduated launches trade |
| Privacy portal | /portal | Move a token into privacy, and back |
| Bridge | /bridge | COTI's privacy bridges, called from here |
| Contracts | /devox-contracts | Every address, live from chain |
| Faucet | /faucet | Testnet COTI without leaving the tab. Testnet only |
| Dashboard | /dashboard | Overview, wallet, full history, agents |
| Skills | /skills | Every capability an agent can reach for |
| Status | /status | Indexer and service health |
How privacy works here
COTI computes over ciphertext using garbled circuits executed by an MPC network. A contract can add two encrypted balances without any single node learning either one. That is a different mechanism from a rollup hiding state behind a proof, and different again from a chain that simply withholds data.
The gcEVM has run COTI mainnet since March 2025, the first production implementation of garbled circuits on a blockchain. Each user holds their own AES key issued through a precompile, and the network key is split across nodes with threshold cryptography, so no single node can reconstruct it. No operator, validator or node ever holds your plaintext.
What stays private
- Token balances, stored as ciphertext in contract storage
- The size of a transfer you make outside a public pool
- Aggregate supply of a private token
- Message bodies, sealed to sender and recipient
What stays public
- That a transfer or swap happened, and against which contract
- Message routing metadata: sender, recipient, timestamp, epoch, chunk count
- AMM pair reserves and price, because an AMM cannot function without them
- Your native COTI balance and gas spend
COTI encrypts amounts, balances, and computation inputs and outputs. It does not encrypt metadata: sender, recipient, timestamp and the fact a transaction occurred stay public. That boundary is the same one the BIS, Project Agora and Circle describe. Selective disclosure, not disappearance.
MPC means trusting the network operator, the consensus and the precompile implementation. Solidity cannot re-prove MPC soundness on chain. COTI says this in its own interface documentation, and so do we.
A COTI PrivateERC20 reports totalSupply as zero on purpose. Publishing an aggregate would leak exactly what the encryption protects. Treat a zero as a signal, not a failure.
Your key never leaves the browser
Reading your own encrypted state needs an AES key that only you can derive. Your wallet signs an RSA public key, the on-chain onboarding contract returns the AES key sealed to it, and the SDK unwraps it locally.
DEVOXPAD caches that key in your browser so you sign once rather than once per read. It never reaches our server. Every decrypt on this site happens on your machine, which means we could not read your messages if you asked us to.