> For the complete documentation index, see [llms.txt](https://docs.redacted.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redacted.money/protocol/build-on-redacted.md).

# Build on Redacted

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 any connected chain are all becoming an SDK, so that your product can offer what only this foundation makes possible.

For builders it comes down to this. If your users' wallets can sign a message, you will be able to give them a private account, with no THORChain integration on your side, no custody and no keys on your servers. You ship the experience, and the engine provides the privacy.

{% hint style="info" %}
**Coming soon.** The SDK is taking shape alongside the roadmap. One-time receive addresses, money as a link, revenue sharing and integrator settlement arrive with it, and funding from other chains arrives with the node network.
{% endhint %}

## What the engine gives you

* Private accounts from one deterministic signature in any wallet, with sponsored onboarding and no gas token needed, so a full private balance exists right away.
* One-time receive addresses are coming with the SDK, unlimited and forever valid, on any connected chain, all converging invisibly into one balance, so you can give every counterparty their own.
* The whole DeFi suite, privately, with swaps, orderbook, earn, borrow and staking on Rujira, where every action is a sealed proof that the relayer submits and pays for.
* Funding from other chains arrives through a pay-in account with the node network, so native assets enter from their home chains, and direct payouts to any connected chain follow in an upcoming update.
* Money as a link is coming through bearer claims that need no recipient account, because the claim itself onboards the user, funded.
* Client-side everything. Proofs, keys and state live in the user's browser, so your integration is about UX and distribution and the trust model never touches you.

## 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.
* Accounting tools built on selective disclosure, such as tax exports and proof-of-payment receipts that reveal exactly one thing to exactly one party.
* 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.

## What you earn

{% hint style="info" %}
**Coming soon.** Revenue sharing and settlement for integrators arrive with the SDK, and this section describes how they will work.
{% endhint %}

Building on Redacted should pay for the distribution you bring.

* Your users will pay the same Privacy fee they would pay through our own interface, so integrating never makes them worse off and you never have to explain a surcharge for privacy.
* You will earn a share of that fee on the volume you bring, scaled to how much you bring.
* You will be able to add your own margin on top if your product calls for it, within a cap so that nobody can charge punitive rates under a privacy label. How that margin is handled will be agreed as part of your integration.
* Settlement will be periodic, against your API key, with signed receipts for every attributed action. You will reconcile our statement against your own numbers, and a missing receipt will show up as soon as it happens.

Nothing about your integration will be written on-chain. There will be 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 will be 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 independent audits (see [Security and upgrades](/protocol/security.md#audits-and-reviews)), 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, so each new builder makes the ground safer for all of them.

The SDK is taking shape alongside the [roadmap](/project/roadmap.md). Early integrators and builders can reach out through the official channels on [redacted.money](https://redacted.money). See the [Integration guide](/protocol/integration.md) for the technical model as it stands today.