Avatar
Sjors Provoost
8685ebef665338dd6931e2ccdf3c19d9f0e5a1067c918f22e7081c2558f8faf8
Physicist turned bitcoin developer aka "shadowy super-coder", author of Bitcoin: A Work In Progress

Just updated my BTCPay server to version 1.9.0 which should have improved Zap support. So far they didn't show up for me, though I noticed several random payments in the BTCPay admin panel. Anyone mind testing with 1 sat?

https://blog.btcpayserver.org/btcpay-server-1-9-0/

Still, why use an outdated standard with a known bug for something invented in 2023? It's a trivial fix.

It is a very expensive mistake to forget to count your coinbase sigops, but that's what I think F2Pool forgot. It would explain why they were off by 3 for both blocks. If anyone has their contact details please nag them.

More generally it would be nice to have some client-side algorithm...

AJ Towns and Kalle Woof should know more. There's a #bitcoin-signet IRC channel if they're not on Nostr.

The question is what level of prevention is considered enough. Wasabi does more than Tornado Cash, but banks do WAY more. Yet even the ING director is being criminally prosecuted for not doing enough to prevent money laundering. That's after ING paid a massive settlement.

Also note that Tornado Cash arguably did all it could given the constraints of a smart contract - i.e. nothing. A prosecutor could argue that a wasabi coordinator should not only screen the UTXO's for a round but also perform full KYC on each owner. That's completely unreasonable in my opinion, but my opinion doesn't matter...

Relayers make a percentage of the revenue in the mixer. If that revenue comes from money laundering, then the prosecutor case is relatively simple. (Compared to arguing about tokenomics and how decentralized Metamask client code)

If making money from mixing fees is enough ground for conviction on ETH, then that's potentially bad news for Bitcoin mixers. Though of course there could be other relevant differences.

#[3]​ and I were present at both "pro forma" hearings, in November and February. We recorded an episode after the first hearing. Not much new information came out in the second hearing. Mainly that they just managed to get access to his laptop and that they believe he also operator a relayer (his lawyer denies this).

https://podcast.sprovoost.nl/@nado/episodes/bitcoin-explained-69-the-tornado-cash-trial

Without access to the full dossier it's hard to figure out what exactly went on. But even if all the details were clear, we might still end up with a very bad precedent. Either because the judge has no clue how the system works and will be satisfied with a handwavy reasoning: there was money laundering (A), there was profit (B), therefore A caused B. Even if all profits came from the appreciation of tokens due to degen traders, or just because he bought ETH early, and not a penny from the actual activity in Tornado Cash.

Or it turns out he did run relayer, in which case they'll move on to arrest anyone who makes money from a mixer.

Mmm, maybe I should use TestFlight instead of the App Store version. Both are sufficiently easy (I was self compiling before).

So ... what about permalinks?

Is it easy to self host an archive site, even if just for your own posts?

Switched to the App Store version of Damus. Other than importing my private key, do I need to do anything?