Nah, it’s a party not a press conference.
“Bitcoin is a swarm of cybernetic hornets feeding off the goddess of energy growing ever stronger and more powerful. It’s a golden city in the sky that you can journey to.”
*Drops mic*
*Walks out*
Live footage of #[1] traveling with a singlesig wallet.
?cid=6c09b952c52998ed106f2ea96c1f77a78d427adb0ef1518b&ep=v1_internal_gifs_gifId&rid=giphy.gif&ct=g
It’s not a tax, it’s an extra payment. If you set it to 100% you still send your normal payment to the person you want to zap and then you also send that same amount to support Damus.
Why is YouTube underrated?
Imagine selling a cold storage wallet with the entire purpose of storing your funds securely without network access…
and then revealing that said wallet can send your keys over the network.
Check if there’s an update first and then there’s a wallet button in the sidebar above muted and below profile.
Wallet view in the side bar.
Someone please help me. I connected TapZap and I can’t stop.
Who needs documentation when you can spend an hour rediscovering the spec on your own?
https://ny.eater.com/2022/12/13/23494423/pubkey-opening-manhattan-bitcoin-bar
One of the ways I recognize that I have had a good idea is if I can find someone already doing it. You sir, have had a good idea!
Oh well, I guess it’s back to the drawing board. There is still the possibility of pulling a Leibniz I suppose.
I actually came first with the idea, sir, but I’d happily share the royalties as it wasn’t exactly pubkey 🤝
https://open.substack.com/pub/sutor/p/tempus-fugit-memoria-nostrum
I’d be happy to be a co-inventor with you and share the single proceed.
🫂
Lol.
I’ll admit it, it was honestly kind of fun making raw requests to relays and parsing the JSON output in the CLI.
Was about to tell you I figured it out but realized you were a step ahead of me.
Maybe the NIP could be made clearer?
Firefox only recently improved their browser sandboxing. Before there was barely anything protecting you.
Btw Rust solves a lot of stuff like this.
https://www.securityweek.com/chrome-sandbox-escape-vulnerability-earns-researchers-20000/
New nerd bar name idea: The Pubkey
I hereby state that anyone is free to take my brilliant idea with the only restriction that if I stop by your pub I’ll get a free beer.
Those are definitely wallets not users. The receipt event is sent from the pubkey of the LN wallet. What I’m talking about are the tags in the receipt event. In the NIP Appendix E it has this bullet point:
> - tags MUST include the p tag AND optional e tag from the zap request
I think the tags contain the pubkey of the person who requested the invoice. The p tag in the event is the pubkey you’re looking for.
Your browser is literally downloading code from many different computers and executing it. It’s honestly amazing to me that we don’t get hacked more often.
The pubkey of what? I don't have access to the 9734 request because it's not sent on a relay. I may have access to the 9735 receppt with a p tag that refers to me; but I may not since it is sent to the relays specified by the zapper, not the relays that the zappee is actually listening on.
In any case, what I'm looking for is a way to know who sent the zap based on the information in my wallet. In otherwords, I'd like to go to WoS and ask it who sent the zap. Failing that I'd like to decode the invoice that WoS presents with the payment and pull out the pubkey, or some ID, of the sender.
>From: jsm<-DerekRoss at 05/14/23 08:02:40 on wss://relay.damus.io
>---------------
>https://github.com/nostr-protocol/nips/blob/master/57.md
>
>The pubkey?
https://github.com/nostr-protocol/nips/blob/master/57.md#appendix-e-zap-receipt-event
If I understand the NIP correctly the LN publishes a zap receipt. You should be able to see the pubkey of who sent the zap request in the tags, right?
