<unnamed>

Public Key

npub1nc0ynppqh37rtulr57xjqpzmfjp58xrd4ey8896ehn9j5flg33fszrz5pa

Profile Code

nprofile1qqsfu8jfssstclp470360rfqq3d5eq6rnpk6ujrnjavmeje2yl5gc5cpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg5waehxw309aex2mrp0yhxgctdw4eju6t0qyxhwumn8ghj7mn0wvhxcmmvzfvv0p

Publishing to

relay.primal.net

relay.damus.io

nos.lol

Last Notes

2025-08-12 13:02:19 UTC

Mixnets are cool! So I built a Bitcoin transaction broadcaster that runs in the browser and sends the transaction anonymously via the @nprofile…hhad mixnet 😎
https://blossom.primal.net/75c4cb12307962c6912bc5a8953c9afddfc03a3730dcd91a9d3deb8c877ea66e.png
I originally had the idea for the @nprofile…5flv 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: https://github.com/elsirion/broadnym
The stack is:
* Rust, obviously
* Leptos for the frontend
* Tailwind for some styling
* Nym for client-server comms
* Axum for the nym address server

2025-07-31 13:51:24 UTC

Cypherpunk future is NOW! 😎
Having a @nprofile…lshg 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 @nprofile…muj4 for building this exciting demo! 🚀
https://blossom.primal.net/b7bb84c4603ef539af4f64b81e076109b1e03837b0062ae9ddcdf6d4cab466a4.jpg

2024-08-29 10:24:48 UTC

- reply

On why I think protocols ought to be designed carefully from the beginning (in particular re scalability) if we want to preserve certain properties like decentralization in the success case:
#note1h2p…qdyy

2023-03-13 06:11:14 UTC

- reply

Do you happen to know why it begins downloading stuff like mad and supposedly runs out of memory eventually (rather quickly on a GBit backed WiFi)?

2023-03-13 06:06:22 UTC

- reply

Idk why, but viewing your profile made Amethyst crash more than once for me 😬 maybe related?

2023-03-12 21:50:13 UTC

One of the most important but likely most underrated things happening in Nostr right now. Building distributed systems is hard. #[0] https://github.com/nostr-protocol/nips/pull/355/files

2023-03-12 21:31:27 UTC

- reply

That could hide unintentional implementation or configuration errors 😬 better to be explicitly about where money goes.

2023-03-12 21:07:20 UTC

- reply

Didn't think about it that way before, but does it mess with #hashtags ?

2023-03-12 16:19:23 UTC

- reply

Having test vectors people can easily test against and maybe a more machine readable spec (e.g. JSON schema) would help with that. My experience with Nostr and LNURL has been one of reverse-engineering and trying to understand the author's intentions so far (human language sucks for specs).
There's only so much time people spend on spec compliance if it works(tm), being compliant should be the easiest path to "it works".

2023-03-12 07:50:27 UTC

- reply

This is so awesome! 🔥
#[1]

2023-03-12 07:48:18 UTC

- reply

Wow, Amethyst supports nearly everything 😲
https://i.imgur.com/K2i6mDY.jpg

2023-03-12 07:45:07 UTC

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 :)

2023-03-11 20:35:50 UTC

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 …

2023-03-11 20:28:42 UTC

- reply

If it ever becomes significant I'll probably turn it off again. Kinda sad, becauseits *is* a lot of fun throwing around sats and seeing others doing so 🥲

2023-03-11 20:01:45 UTC

- reply

Every day I'm amazed how such an under-engineered protocol can work so well in practice and just keeps getting better 🤯
The extensibility and scriptability (you can sign a message with a key? => you can post!) makes it even more exciting!

2023-03-11 19:53:06 UTC

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.

2023-03-11 19:34:58 UTC

- reply

5
(assuming the imaginary post before #[2]'s was also 1)

2023-03-11 15:49:39 UTC

- reply

Do I want to know how it ran before or would that give me nightmares? 😅

2023-03-11 14:19:45 UTC

- reply

Plugins are awesome!
They allow following the Unix philosophy of tools doing one thing and doing it well and then composing these tools to accomplish specific taksks.
#[0]

2023-03-11 14:16:34 UTC

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 https://github.com/elsirion/clnurl
* cln-zapper: Broadcast zap notes when invoices are paid https://github.com/thesimplekid/cln-zapper-rs

2023-03-05 16:55:26 UTC

- reply

The results are in, it takes ~170 lines of #rustlang code and half a day of work if you implement a LNURL server for Core Lightning. Deployment was a ~25 line diff to my nix-bitcoin config.
I think #[1] nerd-sniped me 😅
Added benefit: now I can zap around on nostr like all the cool kids 😁
https://github.com/elsirion/clnurl
#[0]