Protocol

How it all fits together

Updated 30 October 202612 min read

Redacted brings together your browser, the shared Reserve, the nodes that relay your actions, a reference screener and the governance that sets the public rules. This page explains how they fit together and who decides what, and each part has its own page, linked at the end.

The short version

Anyone with a wallet can use Redacted, with no sign-up, KYC or identity checks, and the rules are public and the same for everyone. Every deposit is approved by the node network, and each node chooses what it checks before it approves.

New money waits about two hours before it can be used privately, so a deposit can't be matched to what you do with it a few minutes later. While it waits, the nodes can send back money they decide not to accept, such as coins tied to known hacks or sanctions lists. That money doesn't enter the Reserve and goes back to where it came from.

Only independent nodes decide whether a deposit is sent back, and it only ever goes back to its sender. The core contributors, the DAO and Bōheki (the DAO's safety multisig) can't turn away or send back anyone's money, and no vote or switch can stop an exit to your home or rescue address, or your own money coming back. Bōheki (once, for about 3 days at most) and node votes can pause all new deposits, but a pause applies to everyone at once and never singles anyone out.

The parts

The Redacted system map The entry doors lead into the Reserve of private notes. The Reserve, the Spending accounts and the Rujira products sit on THORChain. Independent nodes relay your actions, approve deposits after their own checks and vote on the safety switches and on an alarm, and Ozone is the reference screener they can use. Token holders and the DAO set the public rules, with an upgrade timelock of at least 3 days and the Bōheki brake, which can pause deposits, start incident mode or raise an alarm once. The Reserve Private notes of all users, held together. Only your proofs can spend yours. Spending accounts Your private accounts, where money acts at once. Rujira products Trade, swap, stake, borrow and more. Entry doors Your public wallet Direct deposit Other chains Via a pay-in account You Your browser Keys, notes and proofs stay here. It sends sealed actions to a random node. Independent nodes Bonded operators Relay your actions Approve deposits after their own checks Release them when the wait is over Vote a deposit back, to its sender only Vote on five safety switches and an alarm Confirm your own returns Ozone The reference screener signs answers about public lists and decides nothing. Emergency exit If no node is active for 7 days, the exit opens by itself. can check addresses Governance Token holders and the DAO They set fees, the wait, bonds and the screening policy, and admit, back or remove nodes. The DAO acts until the relaunch. Upgrade timelock Code upgrades wait at least 3 days, in public. An emergency lane, with more co-signers, can run a scheduled rescue build at once. Bōheki A capped 2-of-3 brake that pauses deposits, starts incident mode or raises an alarm, once, for about 3 days at most. The DAO re-arms it. Relay, approve, release Five safety switches Rules, upgrades, one brake

Your browser holds the keys and proves every action. Nodes carry the proofs to the chain, can check the addresses involved and decide whether a waiting deposit is sent back. Token holders set the wider rules after the token relaunch and the DAO does until then, and the contract applies the same public rules to everyone.

Governance and safety wrap around the Reserve. Token holders (the DAO until the relaunch) set the rules and, once governance switches staking on, can back nodes with stake. Code upgrades wait at least 3 days in the upgrade timelock, in public, and an emergency lane that needs a larger share of the upgrade co-signers can run a scheduled rescue upgrade sooner. The nodes vote on five safety switches and can raise an alarm, and Bōheki is a capped brake that can pause deposits once, for about 3 days at most. None of the switches and brakes touch an exit to your home or rescue address, and every code upgrade waits in public first, so you can withdraw before one runs.

The life of your money

  1. You sign in with one wallet signature, which derives your private account in Redacted's vault in your browser, and Face ID or your fingerprint opens it on your device from then on. Or you keep the account as 25 words in bunker mode. There is no transaction.
  2. You deposit. A node signs an approval after whatever checks it chooses to run, and the deposit then waits about 2 hours, which breaks the timing link to whatever you do next. During the wait, nodes can send it back, only to the address it came from, and you can cancel it. See New money waits briefly.
  3. You use your money privately. It moves from the Reserve to your Spending account, at once when it fits its coin's instant lane and otherwise after the 12-hour queue, and acts from there at once. Your browser proves each action, and a node picked at random carries it. All your actions run from one Spending account, and you can start a new one once a day.
  4. You bring it back. Your own money returns to the Reserve at once, including what came from your Reserve and every gain your positions make in the share you put in. Money someone else sends to your Spending account waits like a deposit, and a mixed return is split, so your part is back at once. Nodes confirm this (see Returns from Spending), and your own money comes back at once even during an incident or a deposit pause.
  5. You withdraw whenever you like. A withdrawal pays at once within its coin's instant lane or otherwise after the 12-hour queue. A payment to a THORChain address you type goes out whole after a short random wait unless you choose Send now. A node can check the destination address first. The proof-free exit to your home or rescue address needs no lane at all.
  6. If every node refuses your exit home, you submit it yourself a day later. If no node is active for 7 days, the emergency exit opens by itself and you can withdraw on your own, from your own wallet. See The emergency exit.

The diagram below shows how returns from Spending work.

Returns from Spending A node traces where the money in a Spending account came from. Your own money comes back to the Reserve at once, including every gain your positions make in the share you put in. Money that someone else sends to the account waits like a deposit, and a mixed return is split so that your part comes back at once and the rest waits. Coins tied to known hacks or sanctions lists, or that cannot be checked, do not enter the Reserve. They stay in the Spending account, and the app offers to send them straight back to their sender. While incident mode or a deposit pause is on, money someone else sent waits, and your own money still comes back at once. Your own money comes back at once What came from your Reserve and every gain your positions make in the share you put in. Money someone else sent waits Coins someone else sends to your Spending account’s address enter the Reserve through the same wait as a deposit. A mixed return is split Your own part is back at once. The rest waits. Known hacks and sanctions lists Coins tied to them, or that cannot be checked, stay in your Spending account. The app offers to send them straight back to their sender. A node checks It traces where the money came from and confirms your own part in a signed statement, public on-chain. A return it cannot confirm waits like a deposit. Spending account Holds your own money, and anything others send to its address. The Reserve Private notes of all users, held together. it stays in the Spending account While incident mode or a deposit pause is on, money someone else sent waits, and your own money still comes back at once.

Who decides what

No single group decides everything. Each has its own powers, and the contract applies the safeguards between them.

Token holders

After the token relaunch, token holders decide who runs nodes. Once governance switches staking on, they stake behind the nodes they choose (see Staking behind a node), and a node needs its bond to be active. Through governance they also set the bond size, remove or slash a node, and open admission to everyone. They decide the fees, the wait, code upgrades (with their public delay) and the screening policy as well. Stake influences which nodes are active without being a direct election, and once admission is open anyone with the bond can run a node.

The Redacted DAO

Until the relaunch, the Redacted DAO holds the token holders' role. It is a 2-of-3 group made up of one core contributor and two independent members.

Nodes

Nodes run the network. They relay actions, approve deposits after whatever checks each node chooses, and send deposits back, which takes at least two nodes, or a third of the active nodes once more than six are active. They also vote on five safety switches, which are the deposit pause, the deposit cap per hour, pausing new private accounts, strict screening and incident mode. The DAO can't override those switches, and fees, bonds and code stay with token holders. The active places rotate every day, with stake deciding who holds them, so no single node is essential (see Node rotation).

Bōheki

Bōheki is a capped, 2-of-3 emergency brake. It can pause deposits, switch on incident mode or raise an alarm, once, for at most about 3 days, and the DAO re-arms it.

Core contributors

Core contributors build the software.

Ozone

Ozone decides nothing. It is the reference screener, built by Redacted's core contributors, and it works only from public data. It is open source. Each node chooses which Ozone instance it trusts, and the node network can decide to use or add other sources. Ozone signs answers about addresses tied to known hacks or sanctions lists and can't move money, and every decision about a deposit stays with the nodes.

You

You hold your keys. Your browser proves every action, and only your proofs can spend your notes.

The contract

The contract applies all of this to everyone, the core contributors included. It checks every proof, accepts a deposit only with a node's approval and holds the funds in the Reserve.

For every decision and its safeguards in one table, see Who controls what.

Brakes and switches

The brakes act on everyone at once, so none of them is a decision about one person, and none of them touches an exit to your home or rescue address or your own money coming back. A node vote needs two thirds of the active nodes, and at least three.

SwitchWhoSafeguards
Deposit pauseA node vote, which holds until two thirds vote otherwise, or Bōheki, once and for at most about 3 daysIt never touches withdrawals or Spending actions, and only the DAO re-arms Bōheki
Deposit cap per hourA node voteThe same safeguards
Incident mode (24-hour wait)A node vote, or BōhekiThe same safeguards, and new money waits 24 hours instead of about 2
Pause new private accountsA node voteIt applies only to creating new private accounts
AlarmA node vote, for a day and twice without the DAO, or Bōheki, once and for a day, the DAO, or the contract's own checksNew deposits pause, the instant lane halves and the queue holds its payouts for at most about 3 days beyond their 12 hours, while exits home and your own money coming back carry on
Strict screeningA node voteIt refuses every fallback, so no deposit approval can rest on a node's backup copy of the lists
Code upgradesToken holders (the DAO until the relaunch)They wait at least 3 days, in public, and need co-signatures from a majority of a published group of co-signers. An emergency lane runs a scheduled rescue upgrade at once only with a larger share of them, and replacing them waits the same notice

The same for everyone

The contract applies these rules to everyone, the core contributors included.

  • Your notes stay yours, because only your proofs can spend them.
  • Your account can always pay its home wallet, and nobody can redirect a payment home (see Your money can always go home).
  • A rejected or cancelled deposit goes back only to the address it came from.
  • Withdrawals stay open. No vote, pause or alarm can stop an exit to your home or rescue address or your own money coming back, and every withdrawal that rests on a proof, home included, passes the lanes, which pay it at once or after the 12-hour queue, in parts when the queue is busy and later only during an alarm. After a break of the proofs or of elliptic-curve signatures, the contract switches into a safe mode for good, and governance can then hold back up to half of each exit, once per coin, and pay it out about 30 days later. If nodes decline a withdrawal, governance can remove them, an exit home goes through without them after a day, and the 7-day emergency exit opens when no node is active at all.
  • Code changes come with at least 3 days' notice, with the emergency lane as the one exception, which needs a larger share of the upgrade co-signers.
  • Every node has the same chance, because the app picks the node that relays your action at random.

Only the nodes can turn a deposit away or send it back. A node turns a deposit away by not approving it, and sending a waiting deposit back takes the votes of at least two nodes, after which it goes back only to the sender. The core contributors, the DAO and Bōheki can do neither. A pause on new deposits, from Bōheki or a node vote, applies to everyone at once and is never a decision about one person.

A code upgrade is the one path that could change these rules, which is why it waits in public and why you can withdraw first.

Go deeper

Reserve and Spending and How privacy works explain the Reserve and what stays private, and the architecture and the relayer cover the pieces in more detail. For screening, the wait, the bond, the brakes and the emergency exit, read How the node network works and Running a node. Compliance, Security and upgrades, Fees and Tokenomics cover screening, the upgrade delay, costs and how the network is paid for.