Last Notes
because @npub1xts…kk5s is actually competent.
while I disagree with them a bunch about nostr + bitcoin (rereading the DB on every frame should be a crime), they still understand most of this better than the average vibeslopper
Since your nsec/npub are actually bitcoin-compatible keys, you can actually send on-chain transactions to npubs.
Ditto and now Amethyst are adding that as a feature. Some people have opinions about that.
I've got lots more pics I COULD share, if only there were some way to chat more privately teehee
Keep the memes coming 😆
@npub1lxk…5xlc has some competition
Some kind of composting worm?
Hodl diddy I like that lmao
They are not only. The problem with decryption is that the signer doesn’t know what kind of event it is decrypting, so a lists app can decrypt DMs.
You could say “let’s send the event to decrypt that is signed”, but the problem there is that the app can:
1. Take the ciphertext from a kind it does not have access to
2. Ask the app to sign an event with that ciphertext and with a kind it has access to
3. Ask it to decrypt that event
The only robust solution is NIP-44 v3
A hundred gets you 3 minutes. These guys are busy.
Didn't know how thicc Yoda was
So we can claim to have sent you “money “, while it is actually the equivalent of throwing in front of someone 10 USD in a country that uses Euros.
Or like those annoying Twitter crypto tipbots
If I had it set up in my studio setting I’d make it look even better 😎❤️🤞🏼
Usually every day too ❤️🤞🏼
i silently celebrated this like it was already a done deal. sounds excellent. my apologies 😅✅✅✅
people are too busy fighting about whether zaps that cost more to send than their value are worth it while ignoring the biggest problem with Nostr right now
“allow decrypting everything” must end just like inputting nsecs into every app
#nevent1q…0fud
so, it sounds like we just need a request to zap protocol, that's a lot like an LN address, and it gives you a different btc address each time cc @npub1xts…kk5s
we really gon let the bitcoin coat-tailers muddle these waters? hehe. maybe. sure. for now.
I know this and count my blessings.
It’s not BS.
Anon zaps / Invoice only: fully private
Private: private to everyone but recipient
Public: visible to anyone
For sender. Recipient detail is always public except for “invoice only”
Okay. That doesn't replace a signer, then. It's just an alternative to storing it as an encrypted nsec in the local storage.
Then it's password-protected behind the Google cloud account, and linked to their email. So, if anyone hacks their Google cloud account, they have the nsec.
Tradeoffs. I can see how that would be less of an initial hurdle, as they are used to storing everything in the Google Cloud or Apple Cloud, rather than exclusively on their machines.
Just wanted to clarify that it entails a possible loss in functionality and security over a real signer. Like the dust-zaps, there is an assumption made that nobody had thought of this, before. We just didn't do it.
all it means is that you may have to scan 1m addresses when restoring from backup
thats it
Satoshi Arepa Tenet Operation.
yes i assumed btc pay did it, so yeah, but this thing you mentiond where none received thats what worries me
I'd loooove to receive an onchain zap 🥹
I love bitcooooiiiiiiin
https://i.nostr.build/O0srF6Rmpqdj6UFR.png
https://i.nostr.build/hIWxU2iaewM8EBoj.gif
What is it, and how so? (Genuinely curious)
Zaps are hoooot
https://i.nostr.build/5m9h6uTzGYFjxGY9.jpg
how do you think BTCPayServer and every system that does onchain receiving works?
(It’s fine)
I recommend using BIP-32 to derive subkeys.
One thing to be aware of is gap limit. If you have 1K addresses that got issued, but none of them received, some wallets will just give up on scanning by when they see 20 addresses without any action
So, back up the index of the last address issued somewhere, just to make your life easier
betta sit up 🌝⚡ we talkin zaps neah!
Data doesn't lie, but it isn't information. Information requires interpretation.
The on chain zaps are going to be stolen by qUanTuM
I had to learn this lesson when I made my short rib curry. There was so much beef fat that it was overpowering all the spices. I had to add like 2-3x more of each spice and a ton of vinegar to make it taste right. But once I got there, it was the best curry I'd ever made.
would it be an attack vector to provide a new address each time (that say someone requests to zap, and new addr is made... hell, even hand out the same one for 24hrs?) lazy web question yeah i know. 😅
I don’t think so, it’s nsec loaded into the app
This is how we scale Bitcoin.
So, they still have granular permissions?
Thank you ser
https://fountain.fm/episode/YtHPO5C4OyHAXaVxlfxi
#nevent1q…n467
Key reuse is also generally discouraged in cryptography as it leads to subtle issues and weakening.
Either you use separate keys for each purpose, or use a root seed to derive keys from with HMAC etc.
I mean.... _really_ private zaps.
Did somebody say ZAPS? Wake up wake up, time to engage on nostr
There is not one, not two, but four nostr merchants on this plate ✅🤘🏼
@npub1jz5…vd4d, @npub1zqd…e6fj , @npub1w56…nsxk, @npub1ekg…qwns
https://image.nostr.build/88cd15711129e9a3fd2fa3473fbfa16781709e59a4c6e3b46cf3bade39528e33.jpg
When the art hoe pussy is so good that’s it’s got you singing The USSR National Anthem 😩.
bro with an A100 powered brain right here. How do you do it? 🙏
Most of those npubs weren't talking to small fry, like me. I didn't notice them coming. I didn't notice them leaving.
Also, a lot of the most-active npubs I was talking to then, I am still talking to now, but not in the public Nostr feeds. So, I can see them, but you can't.
Poverty is The State’s Ultimate Tool of Control.
A person without the means to sustain themselves is unable to fight back.
Then you can say you're using Bitcoin as it was intended to be used.
4) mute those responsible, then 3, then 1, then when it finally gets unbearable, 2.
"I sent you a zap"
"I don't see it?"
"It's on chain."
"What?"