RFC 57: Safecoin Revised

[dirvine]

@anon23746431

Because the elders of each section need to know the current states, i.e. the number of tokens, of all clients in the section to avoid double spending.

Not quite, but we have recently adopted DBC approach and docs will follow v soon. Bottom line, no wallets, no state and no notion of who received the output Dbcs (who you paid). Each input can be form a different key as well. So you can “self tumble” with this scheme if you wish, but there should be no need.

Only network “state” is the spentBook, which is the minimum state possible in any algorithm AFAIK.

[anon23746431]

Thank @dirvine for your warm feedback. Blockchain using global state uses 1) mixing or 2) zero-knowledge proof using added metadata for anonymity. I’m so excited about how to prevent double spending in DSC. Thanks…