Paid P2P Tweet Promotion with Off-chain, Zero Knowledge Proofs.
Users can zap followers who retweet one of their tweets the moment a retweet occurs, like a smart contract… useful for users paying other real users to promote their tweets without trust risks.
1. Retweet a tweet, but do not share the plaintext copy.
2. Encrypt the signed retweet with ZKCSP.
3. Send encrypted retweet to original tweeter.
4. Original tweeter routes sats to you to satisfy the ZKCSP condition for decryption.
5. Once the retweeter receives the sats, the original tweeter will be able to decrypt the retweet as plain text.
6. Original tweeter now shares your decrypted retweet with Nostr relays so the retweet can become part of the normal public record.
This model could help users subsidize other users who don’t have the funds to pay… if free relays become less practical to operate. #[0] #[1] #[2] #[3]
One possibility ZKCSP unlocks👇🔓
Working on* a better way to pay relays with decentralized pools. Sorry for the typo :-)
Working a better way to pay relays with pools and Proof of Spacetime without ZKCSP, but ZKCSP might be valuable for paying Nostr relays to perform a variety of computational services in a trust-minimized way… plenty of possibilities.
Worthwhile idea: a bounty for paying Nostr relays with ZKCSP and Lightning.⚡️
ZKCSP is a trust-minimized evolution of ZKCP — which was created by Bitcoin Core Developer Gregory Maxwell.
https://eprint.iacr.org/2017/566
It’s simple: open a lightning channel with a relay, then use ZKCSP to exchanges sats for the delivered data — settles on-chain with 1 transaction when the channel closes.
Users can stream sats as they download data over time… this way relays can’t take sats from users and leave without providing service.
Worthwhile idea: a bounty for paying Nostr relays with ZKCSP and Lightning.⚡️
ZKCSP is a trust-minimized evolution of ZKCP — which was created by Bitcoin Core Developer Gregory Maxwell.
https://eprint.iacr.org/2017/566
It’s simple: open a lightning channel with a relay, then use ZKCSP to exchanges sats for the delivered data — settles on-chain with 1 transaction when the channel closes.
If Bluesky nodes are synchronizing, how does the protocol address the Sybil attack?
“The above is what I meant when writing, “If you can become aware of the miraculousness which I symbolize, you can help save the freedom mankind is so unhappily losing.” For, if one is aware that these know-hows will naturally, yes, automatically, arrange themselves into creative and productive patterns in response to human necessity and demand— that is, in the absence of governmental or any other coercive master-minding—then one will possess an absolutely essential ingredient for freedom: a faith in free people. Freedom is impossible without this faith.” 🔮
“The configuration of creative human energies—millions of tiny know-hows configurating naturally and spontaneously in response to human necessity and desire and in the absence of any human masterminding!”
This essay is an under appreciated relic. 💜
💜🤙
What the inside of a Nostr 2.0 relay looks like..👇
A forest of user data stored as Merkle Trees (Merkle DAGs):
If you want something done right… do it yourself. Nostr2+DIDs+DWN-backups = the real blue sky.
🌳
