3 ms·

What baby? DNS doesn't have the double spend problem. Why is the blockchain good for this?

• rswail 2mo ago
  An authenticated chain similar to the crts for TLS certificates.
  • josephg 2mo ago
    You don’t need a blockchain to implement a cryptographic chain of trust.
• inigyou 2mo ago
  The double spend problem for domains is the double domain purchase problem. I claim example.com and you also claim it, who wins?
  • josephg 2mo ago
    Whoever buys it first. With a centralised database, this is trivial. Usernames are the same. Who gets @example.bsky.social ? Whoever registers it first. Problem solved.
    • pineapplepizza6 2mo ago
      If you have a central database why do you need atproto?
      • josephg 2mo ago
        To stream dns changes from site owners to dns servers. If you want to change a record, you post the change on atproto. DNS servers everywhere just subscribe to the jetstream. That way anyone can run a fast, local dns server which is kept up to date automatically.
        • deleted 2mo ago
          [deleted]
        • pineapplepizza6 2mo ago
          How fast can I change my DNS records?
          • josephg 2mo ago
            How fast can you post messages to Bluesky?
  • adinisom 2mo ago
    I'd like to see DNS ownership combined with the time range and an owner-unique key so you can go to the website you intended to visit rather than whoever happens to own the domain at the moment.
    • inigyou 2mo ago
      Why would they still have the server but not the domain?
      • adinisom 2mo ago
        Domains cost money to maintain. They can lapse, change, or be sold. Sometimes people make mistakes. So to my way of thinking they're great as a short-term named identifier but not as a long-term stable identifier. Would be nice to have both.
• tancop 2mo ago
  [dead]