Revault is best understood as a Bitcoin vault architecture with delegated operations, not as a generic custody vendor. The official materials repeatedly emphasize the split between stakeholder-controlled cold ownership and manager-operated spending flows.
The main reusable mechanism is a pre-signed transaction graph around each deposit UTXO: Unvault, Cancel, Emergency, and Unvault Emergency. That is what turns ordinary multisig custody into a policy-enforced delayed-spend system.
The unvault delay is the most important control surface. Revault’s architecture only works because manager-initiated spending must first move through a timelocked intermediate state where cancellation or emergency reactions remain possible.
Watchtowers are not implementation detail fluff; they are core protocol infrastructure. The reviewed materials make clear that automated policy enforcement and emergency deterrence depend on watchtowers seeing and reacting to chain events in time.
Optional co-signing servers add another distinct layer. They act as single-use signing oracles for Spend transactions so managers cannot change the final transaction after policy validation, which is a sharper design move than a generic multisig with server help description would suggest.
The emergency descriptor feature is analytically important because it turns coercion resistance into a live operational mechanism rather than a vague governance promise. But the same materials also surface the cost: blackmail and business-continuity risk if emergency transactions or trigger paths are mishandled.
The trust model is therefore distributed across stakeholder signing devices, watchtowers, optional co-signers, coordinator availability, and descriptor secrecy. That makes Revault a useful comparison point against single-tier multisigs, MPC wallets, and institutional policy engines.
Specific source signals worth retaining
wizardsardine.com/revault/: best concise overview of the architecture’s value proposition — Bitcoin-native high-threshold custody with delegated operations, pre-signed protections, and watchtower-enforced policies.
wizardsardine.com/assets/revault_documentation.pdf: strongest source for the architecture itself, including the role split, transaction set, timelock design, and threat/risk framing.
revault/practical-revault: useful because it preserves the protocol/spec layer separately from implementation branding and shows Revault as an openly published architecture, not only as a product page.
revault/revaultd: important implementation-side signal because it names the coordinator and cosigning-server dependencies directly and clarifies how participants actually interact with the architecture.
Why this entry belongs in the corpus
It adds a clean Bitcoin-native comparison point for delegated custody without smart contracts and without collapsing everything into threshold signatures or generic institutional custody.
It helps separate cold ownership, delegated spend rights, anti-replay control, monitoring, and emergency response into distinct layers.
The durable insight is that Revault turns pre-signed transaction graphs plus monitoring infrastructure into an active-defense custody architecture, which is more analytically useful than filing it under generic multisig wallet.