Protocol
Build on Redacted
Updated 30 October 20263 min read
The engine behind Redacted is bigger than one interface. Private accounts from a single signature, proofs generated in the browser, gasless relayed execution and funding from other chains ship as an SDK, so your product can offer them too.
If your users' wallets can sign a message, you can give them a private account and let them swap privately from inside your app, with no THORChain integration on your side, no custody and no keys on your servers.
What the engine gives you
- Private accounts from one deterministic signature in any wallet, protected by Face ID or a fingerprint, or kept as 25 words in bunker mode, with sponsored onboarding and no gas token needed, so a full private balance exists right away.
- Private swaps from your app, where your users swap from their private balance, including between coins of different chains, without leaving your product and without a link to their wallet.
- The whole DeFi suite, privately, with swaps, orderbook, earn, borrow and staking on Rujira, where every action is a sealed proof or signature that the relayer submits and pays for.
- Funding from other chains through a pay-in account, so native assets enter from their home chains through fresh pay-in accounts that never touch the user's Spending account.
- Proofs, keys and state live in the user's browser, so your integration is about UX and distribution, and your servers hold nothing of your users'.
What you could build
These are ideas, and they are examples and not limits.
- Payment apps with tips, invoices, payment links, group pots and split-the-bill, where income isn't a public spreadsheet.
- A private checkout button with a one-time address per order, any asset in, private settlement and a receipt.
- Wallet features, such as a private balance tab inside the wallet your users already use.
- Community bots that send claim links and red-envelope drops in Telegram or Discord, where one drop can onboard a whole group chat.
- Payroll and treasury tools for organizations and DAOs that pay contributors without publishing the comp table.
- Execution tooling that slices orders across rotating single-use accounts, so you can trade size without ever showing a seller.
- Agents with private balances, meaning autonomous software that holds, earns and spends without broadcasting its strategy to the chain.
- Your own frontend, with the full experience, your brand and your audience on our engine.
Your users and their fees
Your users pay the same Privacy fee they pay in the Redacted app, so integrating never makes them worse off and you never have to explain a surcharge for privacy. Partner terms for integrators are agreed directly, through the official channels.
Nothing about your integration is written on-chain. There is no partner tag in the transaction and no per-integrator label, nothing that sorts users into groups by the app they came from. Your users are indistinguishable from every other Redacted user, which is what keeps every integration inside one shared anonymity set.
What stays the same
Everything above is interface. The contracts go through security reviews and audits (see Security and upgrades), change only through a public upgrade path and can be verified by anyone, so integrating Redacted never asks your users for new trust. They get the same proofs, the same Reserve and the same math whoever builds the interface. Every integration feeds the same shared anonymity set.
Integrators and builders can reach out through the official channels on redacted.gg. See the Integration guide for the technical model and the roadmap.