Nostr Web Client

Now the real magic would be finding some zero knowledge proof that destroys your ability to spend a token once you've already spent it. Like a one use signature for an NFT transaction. Each time you receive it, you have a verifiable hard cap on the number of transactions you can do with it. Then you wouldn't need a blockchain for double spend prevention.

Josephus 5mo ago

THIS would be one HELL of a basis for a new coin.

nostr:nevent1qqs8r977waatldg0mujcrfy5e362fjkwmud9hqx9aywlnczthey7aegpndmhxue69uhkummn9ekx7mp0y5erqamnwvaz7tmwdaehgu3wd3skuep0y5erqffjxpshvct5v9ez2v3swaehxw309ahx7um5wgh8w6twv5hj2v3sy5erqctkv96xzu39xgc8wumn8ghj7ur4wfcxcetjv4kxz7fwvdhk6te9xgc8wumn8ghj7un9d3shjtnyv9kh2uewd9hj7ffjxpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9u47fasx

Reply to this note

Please Login to reply.

Discussion

~finpel-dorred 5mo ago

So far I haven't been able to think of a solution to the "clone your hard drive" attack.

How does a single instance of data know that it has been copied?

vinney...axkl 5mo ago

It doesn't. hence: proof of work.

A better direction would be thinking of how to irreversibly imbue data with the PoW.

When I thought about that a little, I ended up with: you have to have an entire compute stack that respects PoW-imbued-data and only talks to other computers that do the same. And then I walked away from the idea because I realized it was just Urbit/Plunder/OPFN/doomed again.