Thread

Replies (12)

@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
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
@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!