Re: [w3c/browser-payment-api] Identifiers or Locators (#150)

Perhaps this is overkill, but part of the registry might run along these sort of lines (inspired by HashCash/Bitcoin-style proof-of-work):

An identifier would be a bit-string in a suitable encoding (e.g. base64).
Valid identifiers would satisfy H(id) < D for a suitable hash function H and difficulty value D.
To register an identifier, a community would have to calculate such an id and publicize it.
Any person could force a particular id to be dropped from the registry by registering id2 such that H(id2) = id, as well as H(id2) < D.

Details of changes in D as computing power improves are left as an exercise :)

If D was low enough then spammers who got off on forcing used identifiers off the registry would have to be well-resourced.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/150#issuecomment-213869468