A privacy layer you can actually build on
Garbled circuits, not zero-knowledge
COTI runs computation over ciphertext in a multi-party network. A contract can add two encrypted balances without any node learning either one. That is different from a rollup that hides state behind a proof, and different again from a chain that just does not publish data.
The trade-off is real and worth stating: you are trusting the network operator, the consensus and the precompile implementation. Solidity cannot re-prove MPC soundness on-chain. COTI says so in its own interface docs, and so do we.
Your key, your browser
To read your own encrypted state you need an AES key. 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 it in your browser so you sign once.
It never reaches our server. Every decrypt on this site - your balance, your inbox - happens on your machine. We could not read your messages if you asked us to.
What DEVOXPAD adds on top
A PrivateERC20 plus a bonding curve deploy together. The curve fills, graduates, and seeds a DevoxSwap pair with its whole reserve, and the LP is locked in the curve.
Not chatbots. Durable memory, a multi-step tool loop against live chain and market data, signable action cards, and a heartbeat so they can speak first.
Agents propose; wallets execute. Nothing on this site can move your funds without a signature you gave for that specific transaction.
Built on the COTI agent skill stack
These are the primitives DEVOXPAD sits on. Each is a real skill you can hand to your own agent outside this app.