Oddbean new post about | logout
 Yesterday we were playing around with ideas at  @Sovereign Engineering , we needed something to preserve anonymity for blossom users that communicate with DVMs.

📢 Introducing Onion-routing for event publishing

This introduces insane privacy guarantees, someone can publish an event and not even the relay they are publishing from can now it's them, nor their IP address.

Technically this works very similar to Lightning, the sender constructs a route of pubkeys and can bounce around the message through pubkeys willing to route for them.

The sender can include small ecash tokens inside each onion layer to pay for the routing.

No hop in the route until the last one knows what they are routing, who its coming from and the sender very explicitly defines through which relays it should hop.

(for the sake of debugging, I built a traceroute-like view, so the sender can see the event being bounced around the different relays; in real conditions a sender wouldn't use that to preserve privacy)

Think of this like tor, just faster.

https://m.primal.net/LZtF.mp4 

nostr:note1q8rnnu4ss798ue88400r5ytej50uzhx87d775q6jev7hs64tj2ksf2nkh2  
 How do you plan the route? Isn't it always user -> some relay -> other user? 
 👀👀🤯 
 Amazing new piece of #freedomtech just dropped. Hold on to your 🥜

Ping @ODELL discuss this in the usual places please 🌱

nostr:nevent1qqst9efnnsvf64397d0cjc0ft7mtp95vv7hqsmtx0z5nfslrmt5fhlgpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqzyrafsj7hmweg9ur7zmn6apajdg48hxuskujx53rhrux0ttjcqx84yqcyqqqqqqgmzlh29 
 🔥🚀 
 Npubs Tor Routing!?!

🤯

NTR -> NosTR

nostr:nevent1qqst9efnnsvf64397d0cjc0ft7mtp95vv7hqsmtx0z5nfslrmt5fhlgpzpmhxue69uhk2tnwdaejumr0dshsyg86np9a0kajstc8u9h846rmy6320wdepdeydfz8w8cv7kh9sqv02gpsgqqqqqqslja02g 
 Did I already say I love your awesome brain? 
 So cool, been simmering on this problem for a while and exciting to see this solution!! 
 Wow 🤯 
 Can't wait to add this to Whitenoise 
 This is awesome! 
 🤯 
 Do you think this could also support onion routed event reads? 
 no -- we're working on something different for anonymized event reads; this is only for publishing 
 Very cool. Curious if this could be used as a payjoin v2 async communication channel, but would need to be able to have the read side too 
 immediately after demoing this at #SovEng we started whiteboarding the read for this; there's already people working on implementing it -- they will probably have something usable by the end of the week 😀 
 "Like Tor, just faster."
https://m.primal.net/LZtF.mp4
nostr:nevent1qqst9efnnsvf64397d0cjc0ft7mtp95vv7hqsmtx0z5nfslrmt5fhlgpzamhxue69uhkzarvv9ejumn0wd68ytnvv9hxgtczyrafsj7hmweg9ur7zmn6apajdg48hxuskujx53rhrux0ttjcqx84yqcyqqqqqqgq0uq4w 
 Freaking awesome! 
 nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75sprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0y8qdrm is building the foundations of a new internet

nostr:nevent1qqst9efnnsvf64397d0cjc0ft7mtp95vv7hqsmtx0z5nfslrmt5fhlgpzemhxue69uhkvun9v4ehqet9vd5zucmpwdsj7q3ql2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqxpqqqqqqzfxs3at 
 SWEET 
 Who picks the mints in this case? Would relays have a list of accepted mints? 
 Pablo just being Pablo....
nostr:nevent1qqst9efnnsvf64397d0cjc0ft7mtp95vv7hqsmtx0z5nfslrmt5fhlgpz4mhxue69uhkummnw3ezummcw3ezuer9wchsyg86np9a0kajstc8u9h846rmy6320wdepdeydfz8w8cv7kh9sqv02gpsgqqqqqqs69gqrk 
 And this as well
nostr:nevent1qqst9efnnsvf64397d0cjc0ft7mtp95vv7hqsmtx0z5nfslrmt5fhlgpzdmhxue69uhhwmm59e6hg7r09ehkuef0qgs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75srqsqqqqqptpfre6 
 Exactly, future does not require shitcoins printed by custodians using blind sigs:

nostr:note1t3cvfuuajkn02t6se8dx2mldpmg0t8lgy76mp5supk3gftxxkqlqs78xj7