GitHub

Release 0.34.0 · joinmarket-ng/joinmarket-ng

Automatic history import for existing wallets, fee quantization defaults for better privacy, coin control labels, local mempool API support, bug fi...

Automatic history import for existing wallets, fee quantization defaults for better privacy, coin control labels, local mempool API support, bug fixes, and security hardening.

Wasabi coordinator tagging attack explanation and PoC:

Gist

WabiSabi Round ID tagging: a working PoC

WabiSabi Round ID tagging: a working PoC. GitHub Gist: instantly share code, notes, and snippets.

You are fully trusting the coordinator with your privacy when using Whirpool (Samourai). Here are some practical attacks with a PoC.

Gist

Whirlpool blind-signing-key tagging: a working PoC

Whirlpool blind-signing-key tagging: a working PoC - whirlpool_tagging.md

JoinMarket makers with unique enough fees are easily clustereable across mixdepths and don't provide much privacy to takers that choose them. Imagine there is only one maker that charges 0.123% fee. An external observer can identify that maker's equal amount outputs when they are provided as inputs for another coinjoin with the same fee (observable onchain). So I would encourage makers to select one of these quantized fees and disable randomization. This is an opt in change that joinmarket-clientserver and joinmarket-ng makers can apply on their own. The more makers on the same quantized fee, the better anonymity for them and consequently for takers that pick them. More info at

JoinMarket Maker Clustering and Taker Anonymity-Set Reduction

and

GitHub

Taker-side maker fee quantization · Issue #508 · joinmarket-ng/joinmarket-ng

Each maker advertises a per-CJ fee policy (cjfee_a, cjfee_r). Within a single round the realized maker fees are a deterministic function of each po...

JoinMarket makers can be clustered (across mixdepths). Two ways: - Easily if their CJ fee is unique enough and reused between rounds. - Harder by gathering co-spending thought many rounds and waiting for the intersection to be narrow enough. It's easier said than done in practice. Bit it's still something to improve. Here is a more detailed explanation of the problem and possible solutions that could bring JM achieved anonymity to the next level.

Gist

maker_swaps.md

GitHub Gist: instantly share code, notes, and snippets.

Feedback welcome!

Nice podcast. Bitcoin is unstoppable, but you are not. Privacy is what makes you not worth attacking.

If AI is making you "think less", you are using it wrong.

Jam V2 beta (JoinMarket WebUI)

GitHub

Release v2.0.0-beta.0 · joinmarket-webui/jam

"The very things that hold you down are going to lift you up." First beta of Jam Version v2.0.0 is out! This is the first release compatible with t...

TLDR: Big frontend rewrite with many improvements. Using [https://github.com/joinmarket-ng/joinmarket-ng/](https://github.com/joinmarket-ng/joinmarket-ng/) as the backend. A standalone docker image for fearless beta testers is coming next. Any and all feedback is highly appreciated. Please know, that there are still open issues and refactorings needed before the final release.

Stacker News

Jam V2 beta (JoinMarket WebUI) \ stacker news

TLDR: Big frontend rewrite with many improvements. Using https://github.com/joinmarket-ng/joinmarket-ng/ as the backend. A standalone docker image ...

@OCEAN @Luke Dashjr Will OCEAN pool enforce BIP-110 compliance for DATUM miners? And for its stratum? What happens to a DATUM miner that builds its own block templates if it finds a block that includes non compliant transactions? Or even if it doesn't find it, does the hashrate still count? And of the pool enforces BIP-110 even if only for stratum, I guess rewards will come from BIP-110 blocks only. Which means lower profitability (but same would happen in the other side). But additionally means that many block rewarda are at risk of being invalidated (reorg). So what happens to LN instant payouts? Don't these questions deserve an official announcement? Maybe I've missed it but couldn't find any.

Jam v2 (JoinMarket WebUI) beta is out! Adding compatibility for JoinMarket NG as the backend. See

GitHub

Release v2.0.0-beta.0 · joinmarket-webui/jam

"The very things that hold you down are going to lift you up." First beta of Jam Version v2.0.0 is out! This is the first release compatible with t...

And @/dev/fd0 has audited and co-signed up to the latest release of JoinMarket NG:

GitHub

build: add GPG signature for release 0.33.0 · joinmarket-ng/joinmarket-ng@947552b

JoinMarket (Bitcoin CoinJoin) modern implementation - build: add GPG signature for release 0.33.0 · joinmarket-ng/joinmarket-ng@947552b

Huge milestones! Long live JoinMarket.