JoinMarket primary sources
Reviewed: 2026-05-15 UTC
Archived official repository / top-level framing
- https://github.com/JoinMarket-Org/joinmarket-clientserver
- Best single overview source for this pass.
- Used to confirm that the repository is now archived, that JoinMarket frames CoinJoin coordination as an economic problem rather than only a software one, that makers stay available for on-demand joins while takers pay fees, and that the implementation also includes privacy-management features like mixdepths, tumbler automation, and PayJoin support.
Usage guide / wallet and taker workflow
- https://raw.githubusercontent.com/JoinMarket-Org/joinmarket-clientserver/master/docs/USAGE.md
- Best source for the operational wallet model.
- Used to confirm mixdepth-based wallet structure, Bitcoin Core dependence, taker-side wallet tooling, tumbler support, and the practical workflow for creating CoinJoins on demand from the command line.
Yield-generator maker economics
- https://raw.githubusercontent.com/JoinMarket-Org/joinmarket-clientserver/master/docs/YIELDGENERATOR.md
- Best source for the maker-side market design.
- Used to confirm that makers run always-on bots, advertise offers to the trading pit, configure fee and size policies, depend on reliable uptime and meaningful balances, and compete on price plus service quality rather than merely joining a fixed coordinator queue.
Fidelity bonds / sybil-resistance design
- https://raw.githubusercontent.com/JoinMarket-Org/joinmarket-clientserver/master/docs/fidelity-bonds.md
- Best source for the system’s distinctive sybil-defense mechanism.
- Used to confirm that makers can create provable costly identities by locking bitcoin in timelocked outputs, that takers choose bonded makers with higher probability, and that the design explicitly treats the sacrifice of time-value-of-money as the scarce resource that makes sybil attacks expensive.
Architecture notes / daemon-client split
- https://raw.githubusercontent.com/JoinMarket-Org/joinmarket-clientserver/master/docs/architecture-notes.md
- Best source for the project’s internal control-plane decomposition.
- Used to confirm the separation between messaging/server logic and wallet/client logic, the daemon model, and the idea that alternate client code can implement application logic without embedding the full messaging backend.
Orderbook exposure / market surface
- https://raw.githubusercontent.com/JoinMarket-Org/joinmarket-clientserver/master/docs/orderbook.md
- Best source for the visible market-discovery layer.
- Used to confirm the existence of local orderbook tooling, the project’s exposure of maker offers through an orderbook watcher, and the fact that market visibility is part of the protocol surface rather than a single branded hosted coordinator.
Main takeaways from this pass
- JoinMarket is best understood as privacy-liquidity market infrastructure: always-on makers advertise CoinJoin capacity, takers buy that capacity when needed, and fee-setting plus uptime become part of the privacy mechanism itself.
- Fidelity bonds are the project’s key reusable mechanism because they make sybil resistance legible as costly identity formation plus selection weighting rather than only coordinator screening or social reputation.
- The daemon/client split matters because it exposes JoinMarket as a communication and market protocol, not just one wallet application.
- The archived status of the reference repository is a real maturity signal, but it does not reduce the project’s value as a mechanism baseline for CoinJoin markets, maker economics, and privacy-liquidity coordination.