MainStreetChungus's avatar
MainStreetChungus
mainstreetchungus@nostr.report
npub1pvuu...d7a5
https://nostr.report ⚡️Bitcoin ⚡️ | Meme afficianado 🌎👩‍🚀🔫👩‍🚀 | Fiat 💵 Miner ⛏️
WOW 🤯! This article does a great job of sunmarizing the “Other Stuff” in nostr, here are some of the use cases highlighted… With BIP47, a customer can generate a set of addresses to use for payments by creating a dedicated payment code for the merchant. Then, instead of using notification transactions to exchange payment codes between merchants and customers, payment codes could be exchanged via Nostr. With PayJoins, users exchange information about what UTXOs will be used as inputs via any communication channel. PayJoin transactions are complicated to coordinate, as participants have to be online at the same time when using a clearnet domain or Tor Onion endpoints. In Nostr, communication is asynchronous: users fetch information from relays once network connectivity is restored. With LNURL, instead of tediously needing to generate new invoices for each transaction, users are able to receive a static endpoint pointing at a web server to automatically generate new invoices. Instead of using a web server as the endpoint for LNURL, users could use Nostr keys as endpoints for LNURL transactions to conceal their identities. In anonymous-amount credential systems such as Wasabi Wallet’s protocol for CoinJoin coordination, WabiSabi, Nostr keys can function as communication endpoints for the coordination of a CoinJoin transaction. Another use for Nostr in CoinJoins lies in the discovery of coordinators, Nostr can function as an anonymous bulletin board. In NostrMarkets, customers can subscribe to a merchant's public key to fetch products from relays instead of accessing a merchant’s site via a webshop. This increases the censorship resistance of online shops, as merchants are not dependent on seizable websites — rather, a merchant’s shop is hosted with all relays the shop sets up to communicate with. Another way to circumvent the requirement of IP addresses in server client communication is NOSTREST. REST, short for “representational state transfer.” By using Nostr keys without identification headers, both users and server operators do not need to know the IP addresses of their counterparts. With the NOSTREST bridge, projects can easily preserve the privacy of their users. By running an e-cash mint behind Tor using NOSTREST to communicate between server and clients, communication can be facilitated asynchronously, while both server operator and user only learn each other’s public keys, eliminating the risk of identification via IP.
Sorry, I just couldn’t handle the picture width, had to go back to 1.3.0 Build 6 image
#[0]​ thank you for the green screen. Now it’s time for who did it best? What does nostr think? Who did pick it best?
*Sponsored Advertisement If you or someone you know has been injured Shitcoining, call the lawyers at Vitalik & Buterin for a free consultation. image
Anyone using short on their umbrel? I can’t like it zap anyone on it, anyone else have that issue? Actually commenting doesn’t work either, interesting