3 ms·

I wonder whether there is any meaningful difference between the effort it would take to implement TACK securely in a way that doesn't involve paying what amount

I wonder whether there is any meaningful difference between the effort it would take to implement TACK securely in a way that doesn't involve paying what amounts to protection money, and the effort required to use a blockchain-based solution. It wouldn't surprise me in the slightest if the blockchain-solution were actually simpler to implement and deploy. Fetching public key fingerprints involves a single HTTP request that returns some JSON. That's about it.

thefreeman 13y ago
Don't we still have to then trust whoever is hosting the server returning the json? I guess you could verify with multiple servers, but that doesn't really guarantee anything and increases the requests. The other option is to a full namecoin client with an up to date chain, correct?
- itistoday2 13y ago
  > Don't we still have to then trust whoever is hosting the server returning the json? It's assumed that you find yourself (or a close friend) trustworthy. DNSChain is designed to be run by individuals, with no powerful deciding authority (like browser vendors) deciding who you should trust (as with CAs today). Today, you trust the least trustworthy of hundreds of organizations that you've never heard of. With this proposal, anyone is free to trust whoever they want, and they can change that instantly without any browser updates or anything along those lines. It's about as trustworthy as you can get.