You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
serial = base64(128bit random number) [[This random
value is generated by clients. A high entropy
(crypto grade quality) is important.]]
so maybe storing the serial is enough?
👍
The serial (or maybe serial+mind_key_id) should be the unique coin identifier. And i do not see any protocol-side reasons to store anything else in the DSDB [1].
There might be other reasons to store whole coins, e.g. to harden the DSDB against manipulation. But that is a issuer-side implementation/operations question and not relevant to the protocol.
[1] For i minute i was thinking that there might be a very different reason to store whole coins at the DSDB: they could serve as issuer-signed reject reasons in case of double-spending attempts. But in most cases, the double-spend coin will be identical to the originally accepted one; also if we want to sign messages, the signatures needed to be time-stamped - so this would not really work ...
What determines that a coin is unique?
hash of:
The text was updated successfully, but these errors were encountered: