8 ms·
I've read up a bit on blinded signatures, Brands, etc. I have two problems there. First, I would need a reference standard implementation of blinded signature
by fexl 16y ago
I've read up a bit on blinded signatures, Brands, etc. I have two problems there.
First, I would need a reference standard implementation of blinded signatures. I know if I tried to cobble something together myself, some crypto-guru would laugh and point out that my prime factors weren't super-prime in a Zeta field of modulus three or some such thing.
Second, basic blinding still does require a central server. I believe the Brands protocol allows blinded tokens to circulate without contact with the server at every stage, and anyone who attempts a double-spend can be identified cryptographically. But it's complicated and ultimately relies on the technique of going after the bad guy with a baseball bat.
So if I went with blinded tokens on a central server, I'd be right back at the central server problem. Blinding provides un-traceability at the cryptographic protocol layer. With Loom, I figured that anyone that concerned with un-traceability could just use a VPN or Tor.
- eru 16y agoThanks for the write up!
- derefr 16y agoWhat about a peer-to-peer solution? Every participant runs a brand server; to "spend" a token, you contact any random server and tell it that you're doing so. That notice then gets spread to every other server; a server who has received the notice won't allow the same token to be spent again, and a server that isn't "caught up" to the mesh won't be allowed to be authoritative (be a source for spend announcements.) It would basically be like Bittorrent—except the pieces are created after the torrent is, inserted into the "file" (keyspace) one at a time, and the hash mutates with every spend.