3 ms·
Do they explain anywhere whether the browser is expected to keep a bunch of multi-gigabyte blockchains on my disk? Or, is it simply that Google, Mozilla and wh
by aasasd 4y ago
Do they explain anywhere whether the browser is expected to keep a bunch of multi-gigabyte blockchains on my disk?
Or, is it simply that Google, Mozilla and whoever else have to serve verification requests for their users?
Or is the whole joke in that none of this is figured out?
- duskwuff 4y agoIf I had to guess, I'd say it's the third one. Given that Mozilla and Google have already publicly objected to this proposal, I don't expect them to implement it. The W3C's word is not the law; no one is obligated to implement every specification they put forth.
- ajvs 4y agoThat's never been a requirement. There exists SPV to verify cryptographic signatures without downloading a blockchain.
- unreal37 4y agoIt's simply a URI standard for crypto signatures. It provides no function except an address to something else. That's why Google is asking for a few "working" integrations to prove the theory. Because someone goes to implement it and figures out the standard is missing something they need critically, they can modify the standard before it becomes a 1.0 standard.