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

On 2016-04-23 19:25, kirkalx wrote:
> 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.

i can see now that we were talking past each other. when you say 
"registry", you clearly have something else in mind than when i do. i do 
not know exactly what, but it sounds like some shared key/value store 
where everybody is free to add entries. when i use the word "registry", 
i mean it like the managed IETF/IANA registries, such as highlighted in 
these examples:

https://tools.ietf.org/html/draft-wilde-registries-01#section-2


---
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-213879721