TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: DNS names used as electronic “title”

1 pointsby throwawaycitiesover 1 year ago
Hi,<p>Attorney here with a question and figure if anyone has seen this concept in the wild a good chance it’s the HN community.<p>It’s an idea that is admittedly inspired somewhat by “tokenization of real-world assets” which is starting to get discussed a lot in legal circles using blockchain tech.<p>They idea is actually very appealing to corporate clients, but I think as the HN crowd knows blockchain also carry’s a lot of stigma. I began to wonder, why not replace blockchain tokens with DNS names as title. DNS names are known, understood, and trusted.<p>It might sound silly and I’m not looking for a “databases already do that” type of answer. Also I know ICANN has some restrictions&#x2F;rules&#x2F;policies that might make such a use case impractical, but my question is has it been done before&#x2F;does someone offer a service using domains as representation of tangible or intangible asset ownership?

2 comments

elliottinventover 1 year ago
I&#x27;m working on a couple of projects that are along these lines:<p>- Domain Verification Protocol [1][2] – proving authority over a domain. This is an application of our broader technology (still in development) where the domain can represent any thing (not just a company, e.g. an asset).<p>- NUM [3][4] a way to store structured data in DNS so that the domain name is the unique key to make a telephone call, GPS locate, make a payment, etc<p>The usual response to concepts for storing anything in DNS is MITM attacks but these can be mitigated. See DNSSEC, DNS over HTTPs, DNS over TLS.<p>Email in my profile, you&#x27;re welcome to reach out to discuss.<p>1. <a href="https:&#x2F;&#x2F;www.domainverification.org" rel="nofollow noreferrer">https:&#x2F;&#x2F;www.domainverification.org</a><p>2. <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=35827952">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=35827952</a><p>3. <a href="https:&#x2F;&#x2F;www.num.uk" rel="nofollow noreferrer">https:&#x2F;&#x2F;www.num.uk</a><p>4. <a href="https:&#x2F;&#x2F;www.numprotocol.com" rel="nofollow noreferrer">https:&#x2F;&#x2F;www.numprotocol.com</a>
nullindividualover 1 year ago
DNS responses are trivially spoofed, intercepted, altered, etc. And that may not even be the fault of your immediate upstream resolver.
评论 #37472967 未加载