Oddbean new post about login | logout https://m.primal.net/IFPz.jpg You wouldn't relay a nut (Except if you don't know what's happening because it's encrypted and there are tens of thousands of other users sending DMs between each other being the perfect noise level for a few nuts to be sent around on a relay). nostr:note1wrsks4u7laxdmeucjedyw9tq7ltkk2efm848wr63ajkwkz4zwn4sr0w084
👀
https://m.primal.net/IFQY.jpg
Fixed https://m.primal.net/IFQb.png
I was debating between relay and download 😂
https://image.nostr.build/e796c30649ee22e85ded13e7577586e7968a10f95c3aa130b9de63b6605be0bc.jpg nostr:nevent1qqsxw4v7jaaesjva6l7nuumh92yp7pc4khl0egnl5nx9ufrz7j9lsrqpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccrqsqqqqqp9v223w
I dare you @calle 👁️⚡👁️ to do so ⚡️😇🟠
Endless possibilities ⚡🫂 #DeezNuts 🥜 https://m.primal.net/IFUX.jpg
This is blowing my mind. This is pushing things forward ! https://m.primal.net/IAiG.jpg
Soon this could become so seamless and easy that you don't even know you're doing it. https://i.nostr.build/oMLwk.jpg nostr:nevent1qqs8rpffdz6w8xejud5z59tzjp0qutaxag57sw8k6gx65wkgqwk890cpzemhxue69uhhqatjwpkx2un9d3shjtnrdakj7q3q2rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sxpqqqqqqz99pyjm
Yes, everything I'm working on is so that users who don't know what I'm talking about don't need to know but just use it.
I think I'm missing something. What's the difference between Cashu and Sats? Are we talking about something like a stablecoin, with value of a unit = 1USD, or ... I don't get it... Sorry, I've been seeing a lot of talk about how exciting it is, but not enough about WHAT it is. What am I missing? And yes, I've read the FAQ. I'm not seeing an answer there for some reason.
Cashu is NOT sats. A Cashu token (usually called ecash or "nut") is just a token, an IOU, a "voucher". The nice thing about Cashu Protocol is that it creates a standard for some providers (mints) that are Lightning nodes to create ecash pegged 1-to-1 with sats. So if you go to a cashu mint to get some ecash the mint will ask you to pay an invoice of X sats, you pay the LN invoice and the mint returns to you X ecash tokens. The mint promises to let you redeem the tokens 1-to-1with sats. This is how the cashu protocol works
I just watched the @BTCsessions overview on cashu, and I think I get it. It's not sats directly, but it's a token that can be used to make payments within an ecash node that carry the same value. I haven't gotten deep enough to need this myself yet, but I'm glad it exists. Thanks for responding!
So I have to trust mints? What if all mints runs by years by feds passing by honest people waiting to confiscate all satoshis?
You have to trust mints
Wouldn't then the problem that Satoshi Nakamo was trying to solve with Bitcoin, keep existing? “The root problem with conventional currency is all the trust that's required to make it work. The central bank must be trusted not to debase the currency, but the history of fiat currencies is full of breaches of that trust.” - Satoshi Nakamoto
Yes! Stop using DNS, people. nostr:nevent1qqs8rpffdz6w8xejud5z59tzjp0qutaxag57sw8k6gx65wkgqwk890cpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzq5xeflpdskqvdq4swxj59793uvdzqzc9pzatjk3nhmcg2h0js8trqvzqqqqqqy0yxgzc
Wouldn’t you still need dns to connect to the relays?
I am waiting for the moment relays become just pubkeys (still need some IP somewhere, though).
It doesn't seem that complicated to achieve with IP addresses listed in a nip65-like event for relays and pubkey support in nip65 events. I doubt clients would see implementing it as a priority. It would be a fun project to make a PR for it in 20+ clients.
Yep, it's really easy to setup. Then relays just need to accept connections via IP directly. We could start with just wss://<IP> if they want.
I noticed you have talked about it quite a lot. Have you had many objections to the idea?
Not a lot for the relay part. But I started the no DNS pitch with static content (that shouldn't use http addresses as well) and the criticism for that was through the roof.
Ppl are going to hate this, but if you want a censorship resistant means of mapping ip’s to pubkeys or vanity names, I can tell think of a distributed ledger that can handle that…
There's no need to map ips to pubkeys, just pubkeys to ips. And pubkey to IP doesn't need a ledger. There is no need for a globally-synchronized naming structure.
But how do you solve the cold start issue? If all I have is a pubkey, how do I find the corresponding ip?
In a world where people write that data on chain, it becomes trivially easy to find and impossible to censor
Yeah, but chain operations become extremely expensive over time. > If all I have is a pubkey, how do I find the corresponding IP? There are many ways, but you basically would have a boostrap IP that can download NIP-65-like events of other relays. We could even use WoT to ask your friend's client to become the Bootstrap relay. Once you have a list of available options saved locally, you can easily get updated records by just querying a few of them. And if they go offline, you update the list with new ones. As long as you know the IP of a single relay, you can get all the others.
Do you think there’s any future for a decentralized dns-like protocol for unique vanity names?
I am sure brands love this. So, I am sure it will be there in some form.
How will we bootstrap relay connections without using dns
Certain DNS solutions, absolutely. Clourflare, AWS and one other one are bad news. Use AdGuard, Quad9 or NextDNS, and implement ECH. Simple as that.
@flix @lunaticoin esto del ecash me esa molando bastante. La privacidad y la descentralización por bandera. Me encanta NOSTR!
It's ridiculous. It's all in the name of "easy"
