Replies (19)

@ThomasV is implementing the solution to the "sybil zapping" problem that you mention at 12m45 You can burn sats by leaving them onchain as anyone-can-spend outputs that are CLTV-locked to the future (decades in the future, if you want to help with the security budget). A "notary" collects all the nostr event IDs, and the sats to burn for each one, and makes a single burn transaction on chain with a Merkle hash - in an op_return -to store all the IDs of the nostr events Nostr clients and nostr relays can then verify the transaction and the Merkle proof to see which events have burned sats attached to them There is a Nostr DVM @Notarized Notes of these notarized notes
Benking's avatar
Benking 1 week ago
You two made a real difference in my life🧑
200k by conference day, you got us goood with that one πŸ˜‚β˜ οΈπŸ˜³
Thanks for the clarification. If I understand correctly, OP_CHECKSEQUENCEVERIFY can only go 65,535 blocks (about 15 months) into the future. I still think the far future is better for this πŸ˜€. The main reason to give the burned sats to miners, and not just burn them immediately in an OP_RETURN, is to help with the security budget in the future If the unlocking is too soon, it gives miners the incentive to cheat in the way we discussed a couple of months ago. A short lockup would allow a large mining pool to advertize "pay us 10 sats, and we'll pretend that we burned 12 sats for you". A large mining pool can do this today as there is a good chance that they will also mine the block at which the burned sats become unlocked and therefore they are "fake-burning" sats by paying themselves I chose 12 sats and 10 sats there, based on the rough numbers that large pools control about 20% of hashrate
@ODELL regarding quantum, I completely agree that the fix is to create quantum proof addresses that people can opt into. Is opensats funding any devs working on this stuff?
Sid Shattuck's avatar
Sid Shattuck 1 week ago
@Marty Bent Andor is not just a good star wars show, it's a great show full stop. I was surprised by it. Resonates with bitcoiners. Should be mandatory viewing for collectivists. Only two seasons so not a huge slog. It's a prequel to Rogue One (ends right where the movie begins) and is mostly about the inner workings of the Empire and the origins of the rebels. All the characters are interesting and well developed. Thank me later!
So you're saying that miners would delay the notarization transaction until the height specified in the CLTV, so that they can notarize and redeem in the same block Yes, they could in theory, and that would allow the cheating that we discussed before. But they're not going to delay the notarization transaction for decades, if we're sending it decades into the future The end users of the system (I mean the users of nostr clients who are consuming nostr events and want to see which events have burned sats associated with them) are looking for reliable notaries, i.e. notaries that get the notarizing transactions into blocks within hours or days (not years or decades). The end user's software could easily check that the notarization transaction is mined at least N blocks before whichever height is specified/implied by the CLTV or CSV locks
#7 ⚑ Most Zapped Last Week Nostr’s Value4Value (V4V) model is all about plebs directly rewarding creators for the value they receive, no middlemen fees, no ads, just pure community-driven support using sats via the Bitcoin Lightning Network. Thanks to by @PABLOF7z for providing this data. Here are the Top Zapped/Top Zappers from last week, showcasing creators who received/sent the most engagement: πŸ”₯ Top 3: Most Zapped 1. Name: @Rizful.com (zap tester) Zaps Received: 1041 Sats Earned: 2k 2. Name: @FLASH Zaps Received: 976 Sats Earned: 72k 3. Name: @Gigi Zaps Received: 392 Sats Earned: 53k πŸ”₯ Top 3: Most Zappers 1. Name: @AQSTR Zaps Sent: 1095 Sats Spent: 130k 2. Name: @Benking Zaps Sent: 372 Sats Spent: 1k 3. Name: @Turkey Zaps Sent: 236 Sats Spent: 12k πŸ’° Top 3: Most Sats Received 1. Name: @Fountain Boost Bot Sats Earned: 697k Zaps Received: 369 2. Name: @RABBIT HOLE RECAP Sats Earned: 473k Zaps Received: 42 3. Name: @BitBetBot Sats Earned: 209k Zaps Received: 43 πŸ’° Top 3: Most Sats Sent 1. Name: @Angor Sats Spent: 256k Zaps Sent: 15 2. Name: @BitBetBot Sats Spent: 228k Zaps Sent: 37 3. Name: @BITKARROT Sats Spent: 184k Zaps Sent: 6 Here are the Top Zapped from last week, showcasing notes that received the most engagement: πŸ”₯ Top 3: Most Zapped 1. View quoted note β†’ Zaps Received: 53 Sats Earned: 7k 2. View quoted note β†’ Zaps Received: 44 Sats Earned: 7k 3. View quoted note β†’ Zaps Received: 42 Sats Earned: 22k πŸ”₯ Top 3: Most Sats 1. View quoted note β†’ Sats Earned: 51k Zaps Received: 13 2. View quoted note β†’ Sats Earned: 23k Zaps Received: 10 3. View quoted note β†’ Sats Earned: 22k Zaps Received: 42 #most-zapped_nostr_recap
ThomasV's avatar
ThomasV 2 days ago
It's not about delaying the transaction. If you only rely on CLTV, a spammer can mine a notarization transaction today and pretend that it has been published a long time ago. But you are right, the software could additionally check that the notarization was mined N blocks before the locktime. This introduces an extra parameter, and it feels a bit like misusing CLTV, but it would indeed allow for longer time delays than CSV.
The extreme case of this could be very interesting for game theory, leading to just one notary getting a very large monopoly Imagine a single notary does a deal with all the big mining pools which together control 90% of hashrate That notary could advertise: "give me 10 sats and I'll notarise it as 50 sats". As they control 90% of hashrate, they will on average get 45 sats back from those 50, and hence the real cost to the notary is just 5 sats (on average) compared to the 10 sats that they earn from the creator of the nostr content With CSV, the delay is just about 15 months, and that's short enough that the big notary is happy to wait I think the only solution is to really make sure that today's miners don't see any value from the burning, so either notarizing to an OP_RETURN, or use CLTV to send it very far in the future @c03rad0r , is this the right npub for Espen?: @Espen I think he had the same idea
↑