wabisabi-primary-sources-2026-05-15

WabiSabi primary sources

Reviewed: 2026-05-15 UTC

Original protocol paper

• https://eprint.iacr.org/2021/206
• https://eprint.iacr.org/2021/206.pdf
  • Best canonical source for the cryptographic mechanism.
  • Used to confirm that WabiSabi is a centrally coordinated CoinJoin protocol with variable amounts, and that its core construction uses keyed-verification anonymous credentials and homomorphic value commitments to improve privacy and flexibility over earlier blind-signature-style approaches.

Protocol repository / top-level framing

• https://github.com/WalletWasabi/WabiSabi
  • Best concise repository-level overview.
  • Used to confirm that WabiSabi is presented as an anonymous credential scheme for centrally coordinated CoinJoin transactions, with separate explainer and generic protocol materials.

Informal explainer

• https://raw.githubusercontent.com/WalletWasabi/WabiSabi/master/explainer.md
  • Best source for intuitive mechanism decomposition.
  • Used to confirm the protocol’s mapping between value commitments, coordinator-issued credentials, zero-knowledge balance checks, and fresh network identities, plus the idea that the coordinator certifies value without learning linkage.

Generic coordinated CoinJoin protocol

• https://raw.githubusercontent.com/WalletWasabi/WabiSabi/master/protocol.md
  • Best source for the round structure and role separation.
  • Used to confirm the distinct Satoshi / Alice / Bob identities, round phases, timeout and blame behavior, fee-policy hooks, and the explicit caveat that transaction structure privacy is not fully solved by the credential layer alone.

Live Wasabi docs / deployed wallet-facing instantiation

• https://docs.wasabiwallet.io/using-wasabi/CoinJoin.html
  • Best source for the current real-world application of WabiSabi.
  • Used to confirm that Wasabi implements WabiSabi through input registration, connection confirmation, credential reissuance, output registration, signing, broadcast, and blame rounds, and that the wallet treats the coordinator as a persistent policy and fee-setting surface.

Main takeaways from this pass

• WabiSabi is worth keeping as a distinct lower-layer entry because it makes coordinator-run variable-amount CoinJoin legible beneath the Wasabi wallet product.
• The protocol’s key reusable mechanism is private value decomposition via anonymous credentials plus homomorphic commitments rather than fixed equal-output pools.
• The coordinator still matters operationally: it controls round policy, fee parameters, timing, and blame handling even if it cannot directly map inputs to outputs or steal funds under the intended design.
• The protocol docs explicitly warn that privacy still depends on higher-layer transaction-structure and wallet-policy choices, which is precisely why WabiSabi should not be flattened into a generic coinjoin label.