I just took a look at the BIPs repo, thinking that maybe I can be slightly helpful by looking the open PRs and maybe trying to find some very small thing that I can be helpful with The first open PR at the moment is a childish attack by two feds on BIP-54

GitHub

Split BIP54 into bundle constituents by JeremyRubin · Pull Request #2175 · bitcoin/bips

This is largely an editorial question for the BIP Editors, although authors of BIP 54 may care... Largely looking for approach ack at this step bef...

I'm getting more bullish on Payjoin When I first read about it, it seemed a little simplistic and I wanted everyone to go straight to the "perfect" solution. But now I'm really warming to it. It increases privacy by a non-negligible amount. And the protocol is simple enough that many wallets will be able to support it. Then, as more wallet developers are used to the idea of doing this basic form of collaborative signing, the developer community will then have the experience necessary to become more ambitious (full coinjoin privacy, with blinded tokens for registering inputs and outputs, ...). And Cashu is moving in that direction:

GitHub

NUT-XX: Payjoin by thesimplekid · Pull Request #376 · cashubtc/nuts

Cashu protocol specifications https://cashubtc.github.io/nuts/ - NUT-XX: Payjoin by thesimplekid · Pull Request #376 · cashubtc/nuts

I'm switching to X this evening, away from Nostr, because I'm getting bored of the repetition - and egotistical attacks - that's on Nostr

On Silent Payments, I'm getting much more optimistic in the last hour or so, since deciding to dig into more detail. Seems like about 150 KB per block (BIP158 filter + 33 bytes per tx) is sufficient in terms of bandwidth. And this table of CPU-only scan times is much better than I expected. There is room for further bandwidth improvements. According to the BIP (352), if you want a couple of weeks a huge fraction of relevant UTXOs are already spent, and so the 150KB can be shrunk further by discarding transactions which no longer have any unspent taproot outputs. It's still not realistic for everybody, especially noobs, to run their own 'sovereign scanner' like this. But it's interesting nonetheless.

GitHub

GitHub - sparrowwallet/frigate: Frigate Electrum Server

Frigate Electrum Server. Contribute to sparrowwallet/frigate development by creating an account on GitHub.

I went for three weeks, but got nerd-sniped into staying for 6 View quoted note →

Use an *ephemeral* Ark server to collaboratively swap UTXOs (e.g. on-chain zaps) to *Lightning*, trustlessly. Receive on Bolt12 for extra privacy and unlinkability Thoughts? I'm assuming we can put a HTLC in the Ark's vUTXOs View quoted note →