3 ms·
Capabilities don't solve double spending(or in this case, double sending) token, as they are intentionally transferrable. So you'd need to have a way to bind a
by senko 5y ago
Capabilities don't solve double spending(or in this case, double sending) token, as they are intentionally transferrable.
So you'd need to have a way to bind a capability to a sender, which naturally leads to PK, or treat them as short lived tokens you revoke as soon as you see they've leaked, which is identical to throwaway email addresses we already have.
- emacsen 5y ago> Capabilities don't solve double spending(or in this case, double sending) token, as they are intentionally transferrable. They do if the entity doing the transfer is the issuing entity.