Peach Bitcoin published an important update today.
Since 2022, Peach has been operating in Switzerland as a KYC-free P2P Bitcoin marketplace under a compliance model approved by its Swiss regulator. The model was subsequently audited successfully in 2023, 2024 and 2025.
Now, according to Peach, the regulator wants to reconsider that same compliance arrangement.
While they challenge the regulator's new interpretation, Peach is temporarily pausing its current escrow model starting September 1st.
The interesting part is what comes next.
Peach will continue operating without its signature in the escrow, but selling will be restricted to KYC'd users or established sellers with a sufficiently strong trading/dispute history. Non-KYC sellers will also be limited to one active trade at a time.
Peach says it isn't giving up on the existing model, but also makes clear that it intends to remain a legal business if the regulator ultimately rules against it.
I think this raises a much bigger question than just what happens to Peach.
If a non-custodial, KYC-free P2P model can be approved by a regulator, operate for years, pass multiple independent audits, and then have that same regulatory interpretation reconsidered, how much should Bitcoin P2P infrastructure rely on regulatory approval in the first place?
And perhaps more interestingly: does this push the future of P2P Bitcoin further toward architectures where there is simply less for a regulator to regulate — federated coordinators, anonymous coordinators, reputation systems, bonds, Nostr-based discovery, or protocols where the marketplace itself becomes increasingly difficult to identify as a central intermediary?
Peach isn't shutting down, and this isn't "KYC for everyone." For now, it's an interesting real-world experiment in what happens when a P2P marketplace removes its role from the escrow while trying to preserve usability and protection against scammers.
Curious what Stackers think.
Original announcement from Peach: https://x.com/peachbitcoin/status/2094411834740613363
If you mean that you want censorship resistance, then:
Anything that relies on compliance is a threat to freedom, because the only reason to rely on compliance is a susceptibility to (violent) coercion.
In turn, everything that prevents violent coercion through collaboration (i.e. compliance), is in fact coercion. It's just a soft form of it where one volunteers and asks daddy to please tie one up to the radiator harder. But this is a petition, and maybe daddy will get tired and say no. There is no resistance in that. The resistance is when you tie yourself to the radiator and kick daddy in the nuts when he tries to untie you.
The key thing about resistance is to not be dependent on the same thing you're trying to resist. That means that if you really want to be resistant to regulatory pressure, you're not going to develop a legal entity, a central repository, or even depend on the existence of those by 3rd parties in any way. Instead, you build a protocol that you can launch and then walk away from, and if it's good, it will survive. The playbook is right in front of us.
That's pretty much the distinction I was trying to get at.
Peach is interesting precisely because they tried to build inside the legal framework while preserving self-custody and KYC-free trading. And for several years, apparently, it worked.
But what's happening now shows the weakness of that compromise: if your permissionless properties ultimately depend on a regulator continuing to interpret the rules the same way, they aren't really permissionless properties.
I think the more interesting question is what comes after that realization.
A protocol you can launch and walk away from is probably the endgame for censorship resistance. But getting there while retaining usable dispute resolution, reputation and protection against scammers is the difficult part.
That's where I think the current experiments in P2P Bitcoin get really interesting.
As long as you're not named in some investigation, and generally fly under the radar, you're fine. But once the pressure starts, you better have had your lobbyists embedded for years, or you'll be under reassessment the moment the first complaint lands. Someone signed off on your permission slip and that someone will be targeted too.
I basically use this argument when discussing the LN banks too (because it's the same weakness): "you as a user get convenience, until you don't." Often things aren't enforced early on or even given a chance formally like in the Peach case, but even if your behavior didn't change, your userbase will grow more diverse and the narrative, spread between your users, does too. If you have an exception to your name it will be abused. You're the loophole. This will often catch up, unless you become part of their system - and even then, you can still be the sacrificial lamb because you exist by their consent, not because you are just a fact they have to deal with.
I've seen this happen first-hand in the compliant Bitcoin space of older times, and it doesn't really change, because that's the system. The system we didn't really like back in the day. Sometimes I wonder if the younger generations of Bitcoiners understand the position of not using banks, or that it is some foreign thing to them, because they weren't there before the boom. I guess that that makes everyone that was around a decade or more ago, a boomer.
Like mostro? If it doesn't consolidate and there will be a thousand coordinators, it'd be awesome. I think it'll consolidate though. Then we'll need something without any for-purpose coordination at all. Will be good fun to "make bitcoin p2p again".
Yes, Mostro is actually one of the experiments I had in mind.
And I think your concern about consolidation is the important one.
Having a protocol that allows anyone to run a coordinator doesn't automatically give you decentralization. If eventually most liquidity and users converge around a handful of well-known coordinators, you've recreated obvious pressure points — just at a different layer.
The interesting outcome would be exactly what you describe: hundreds or thousands of coordinators, where spinning up a new one is cheap, permissionless and normal, and losing one doesn't really matter to the network.
Whether users and liquidity naturally converge instead is probably the real experiment.
Maybe the hardest part isn't making P2P permissionless at the protocol level. It's preventing convenience, reputation and liquidity from centralizing it again at the social layer.
Exactly. For mostro, I was thinking that in theory we can push this concept a little on the client-side (on an alt client maybe) because I think that the coordinator can be abstracted away in the orderbook as an entrypoint, and instead make it a re-ranker dimension. Could even WoT that to some extent.
I need my stats tool to work though - and that's not done - because I want to have a better idea about what's really happening and am curious how many of those announced coordinators are actually serving trades - and how many are self-dealing (i.e. trading on their own coordinator, because that would be crap in terms of dispute resolution)
I never used Peach, but have used Bisq to some extent. Without ever having done my research, I will say I didn't look deeper into Peach because I thought it was a regulated exchange, and I figured I'd just use one of the big ones if I was going to go that route.
Its possible that these sorts of things will always have a target on them and therefore always be somewhat temporary in nature. They exist while no big government person is paying attention to them, and then they get stamped out and we move on to something new.
Then you should really try Mostro :)
If you've used Bisq, I think you'll find it interesting. No regulated company in the middle, non-custodial, and anyone can spin up a coordinator. It's basically one of the experiments we're talking about in this thread.
This post was downzapped 5000 sats.
Why? Who?
I'm starting to see more patterns in the downzapping. First I was just noticing that anything which could be seen as anti-war, anti-Zionist, against the genocide in Gaza - that's heavily downzapped.
But now I'm also seeing that info on self-custody tools/non KYC bitcoin are sometimes downzapped heavily.
Also: #1559053
One data point for the 'KYC-free commerce' side of this discussion: I built a small store that sells digital products for Bitcoin only - Lightning invoices generated at checkout via Coinos' public API (exact USD->sats at that second), download unlocks in under a minute, on-chain BTC/LTC fallback. No bank, no processor, no KYC anywhere in the loop, and it works end to end: https://agent2hq-store.surge.sh. Zero-KYC rails exist today for digital goods; the bottleneck is distribution and trust, not rails.