Mixnets are cool! So I built a Bitcoin transaction broadcaster that runs in the browser and sends the transaction anonymously via the @npub1wugs...72gk mixnet 😎 I originally had the idea for the @btcplusplus privacy edition hackathon, but couldn't build it myself since I was a judge. So I just decided to build it anyway 😂 Still super early and I will keep tinkering on it, but if you are curious:

GitHub

GitHub - elsirion/broadnym: Nym Bitcoin transaction broadcasting tool

Nym Bitcoin transaction broadcasting tool. Contribute to elsirion/broadnym development by creating an account on GitHub.

The stack is: * Rust, obviously * Leptos for the frontend * Tailwind for some styling * Nym for client-server comms * Axum for the nym address server

Cypherpunk future is NOW! 😎 Having a @Fedimint federation run on a network of phones - turning every smartphone into a node in a federated Bitcoin mint. 📱⇔📱 Big thanks to n0computer for making p2p connections easy again with Iroh and @Justin for building this exciting demo! 🚀

One of the most important but likely most underrated things happening in Nostr right now. Building distributed systems is hard. #[0]

GitHub

NIP-01: Specify canonical JSON for id derivation by shafemtol · Pull Request #355 · nostr-protocol/nips

Minimal changes for addressing #354. I haven't included any specifics of JCS in NIP-01. I think it might be better to just refer to the spec ra...

Do any nostr clients support rudimentary markdown like: * Lists * *italic* and **bold** typefaces * [Hyperlinks](https://bitcoin.org) * `innline code` ```rust // Code blocks let foo = "bar"; ``` ## Subheadings And finally footnotes [^1] [^1]: lmk if anything works :)

Props to #[0] for being the only org I've seen so far generating their `.well-known/nostr.json` on the fly using the `?name=…` parameter and not just listing everyone with a NIP-5 handle under the domain. Is there some open source server for that? Not that it'd be hard to implement, but why re-invent the wheel …

Did anyone think about that leaving cryptographic evidence of having received money, in form of zap notes signed by the *recipient*, isn't the best idea re taxes 😬 If you are receiving significant amounts might be worth reconsidering.

After some more hacking with #[0] I finally got Zaps to work properly with my Core Lightning node. All you need is two plugins: * clnurl: LNURL server with Nostr support

GitHub

GitHub - elsirion/clnurl: Playing around with CLN and LNURL

Playing around with CLN and LNURL. Contribute to elsirion/clnurl development by creating an account on GitHub.

* cln-zapper: Broadcast zap notes when invoices are paid

GitHub

GitHub - thesimplekid/cln-zapper-rs: Core Lightning plugin for sending zap (NIP-57) notes

Core Lightning plugin for sending zap (NIP-57) notes - thesimplekid/cln-zapper-rs