Good point xD Then instead of "normal" we could go with someone that's willing to do the PoW required to buy P2P and maybe watch a video or read a post about privacy in Bitcoin 101.

I want to open a debate on something practical: how do we make JoinMarket useful for more people? But before that, a framing question: how *should* a normal person use Bitcoin with some privacy? Nothing crazy, not OpSec level. Just "I don't want people I transact with to know what I own." My current answer would be: buy P2P (Bisq or lnp2pbot depending on the person), run the UTXOs through a few JoinMarket rounds (ideally the tumbler) and then either move them to cold storage or open a Lightning channel with the clean outputs. For Lightning on mobile, honestly only Phoenix works well for non-technical people. Everything else is too fragile or slow or kills your battery. This workflow sounds reasonable on paper. In practice it's a mess: you need a full node, you need a computer, Bisq has its own learning curve, and JoinMarket's install alone is challenging. So what's actually worth building? My guess is a light-client mobile wallet with the tumbler baked in: deposit, wait, get clean UTXOs out, ready for cold storage or a LN channel. Simple enough that you don't need to know what's happening underneath. But is that the right call? Is there a better abstraction? I'd love to hear where you think the effort should go.

JoinMarket NG 0.28.0 is out. The most relevant changes are: - Aligned defaults with joinmarket-clientserver - TUI improvements - Tumbler implementation - New directory nodes - Lots of minor bugfixes and performance improvements All details at https://github.com/joinmarket-ng/joinmarket-ng/releases/tag/0.28.0 Additionally, we now have an acknowledgements section in main README: https://github.com/joinmarket-ng/joinmarket-ng#acknowledgements We're looking for more collaborators and co-maintainers!

Bisq vulnerability being exploited, trading halted: https://bisq.community/t/psa-trade-protocol-exploit-discovered-investigations-ongoing/13664

I think the auditability is an important aspect and I like the low barriers that Python offers for people wanting to read it or contribute. That being said, moving parts or everything to Rust is not out of the table, and would be beneficial for a mobile app for example. Meanwhile we're using Python with type hints analyzed statically (mypy) and on runtime (pydantic models). But there are more important things to tackle first. What brings us to integrations like Raspiblitz and Jam. Both are being worked on at the moment and pretty functional! You can track the status at https://github.com/joinmarket-webui/jam/pull/1166 and https://github.com/raspiblitz/raspiblitz/pull/5240

Does anyone have a compilation of all of the OXT research PDF reports? They were only available for subscribers so aren't reachable from archive.org Willing to send some sats for them.

Thanks for a decade of hard work! Long live JoinMarket.

Browserleaks - Check your browser for privacy leaks https://browserleaks.com/ Terrible... Biggest realizations: * JavaScript test: I leak the timezone city (e.g. Region/City, not just UTC+/-XX) * Canvas test: my browser is very unique already.... Uniqueness: 99.99%. Very low anonymity set. * Font fingerprinting: I was not aware of this... The set of fonts that you have available is leaked to websites... If you want to cry a bit more, check [https://amiunique.org/fingerprint](https://amiunique.org/fingerprint) I was also unique there, among their 5M records. https://stacker.news/items/1473271

I like codimd using the reveal-md format. You can self host, and there's also hackmd for a hosted version.

Since there is now joinmarket-ng and joinmarket-rs, it was time to create a repo for JoinMarket Protocol (JMP) Specifications. The idea is to separate the protocol and protocol extensions from the implementations, as done in BIPs, NIPs, NUTS, ... https://github.com/joinmarket-ng/jmp https://gitworkshop.dev//relay.ngit.dev/jmp