RHR 388: A CHRISTMAS MIRACLE WITH nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqyv8wumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wsqzqpxfzhdwlm3cx9l6wdzyft8w8y9gy607tqgtyfq7tekaxs7lhmxf5dcd8v AND nostr:nprofile1qy0hw...
@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
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
24❤️5🤙2👀1
