That’s literally what it is lmao. I was testing what happens when you sign something with images with amber and chose something from my photo library that wasn’t a family photo and found WhatsApp auto-saved aunt calibre bible quote.
It's not looking ethbros. I've been doing some technical analysis on ETH/BTC. It turns out that maybe ETH and all "utility tokens" have no fundamental value and it just took an unusually long time for the market to begin adjusting them towards zero.
https://m.primal.net/LfZi.png
Oh interesting OK. So this is broadcast and then you send out deletion for it when the draft is no longer needed?
It seems to happen even if I don't close a note though..
Oh no just before the goldenbull run.
nostr:nevent1qqsfqh08sag9f3qgnzwa38ew8hjcv6wllxu4f962q9ya6qdrlg2nqcqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg9e55m4ywa69lx6aptajrv2wcx7fusnnj0epkvx7aruulgwcrgh85psgqqqqqqspn79yl
Thinking about opportunities for FROST and nostr integration.
1. It should be easy to generate a FROST key with a bunch of people on nostr. But this creates a new thing for everyone to back up (the key share).
2. Maybe we can avoid this with the recovery feature of the FROST keygen WIP BIP. Basically you have your share encrypted to a (smallish) encrypted blob in a nostr note so just with your nostr nsec it should be possible to recover it. Maybe there is some way to pay relays to keep a note into the future.
3. Apart from keygen nostr relays might be used to broadcast signature requests to notify people with other keys that there's something to do. Even an encrypted chatroom among share holders.
4. I'm not sure how this fits in with frostsnap. Frostsnaps could have their own npubs for keygen but I don't really want to back them up. So I think you'll be forced to write down your share backup as usual.
5. It would be good if signing was still one round so I guess presharing nonces would be done via nostr too.
I enjoyed participating in this episode. @NVK is great at bringing together the quiet builders and deep thinkers in Bitcoin.
https://fountain.fm/episode/EFkCsswzEAnxNwEcbUjJ
nostr:nevent1qvzqqqpxquqzq3s5ljpy3v3zkl9xe05xufpvfgw6p86ser4dmzwchuny06ss3c8ycyf0jq
Antiwar podcast is the best updates on the worst situations in the world.
https://fountain.fm/episode/02KHCQb6i3CuixwAcH3P
nostr:nevent1qvzqqqpxquqzq5tr72a7rglzg2vhpwxzfse87vtwpxkav6l3e2veen7ja6eg3gulexw2jg
If the attacker has the xpub then it's definitely much easier and it should be possible in one sig. Your aglo looks right. You can also do it in a single address reuse.
https://x.com/LLFOURN/status/1733992948294181299
The reason we thought this attack was notable and worth disclosing is that it doesn't depend whatsoever on the user's behavior or precautions (i.e. not giving out xpubs).
See FAQ: https://darkskippy.com/faq.html
24 words needs twice as many signatures as 12. 24 words with strong passphrase needs twice as many as 24 words without one.
Oh someone's working on FROST nostr already!
nostr:nevent1qqszlav4jw5wxl6mpn7n4w42la42en88ttzh3a4kjmzwy5jqtjtsseqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygqhw9adf5sw9fp9eks2yx2kyjs2ffeufa5htuttzkflepl6gmedtqpsgqqqqqqs46rfr5
Oddbean new post about login | logout
Notes by llfourn | export