Network-wide DNS for node identification and arbitrary payload messaging

[kwvg]

Existing Works

• Polkadot Name System (whitepaper, additional reading)
• Polkadomain (whitepaper, flowchart)

Description

To facilitate the querying of nodes that provide access to invitation-based private chains, the ability to identify libp2p entities (nodes), contracts or non-protocol endpoints is necessary, failing which, would make the process less intuitive, not impossible, just considerably more difficult and prone to human error as developers and users will need to work with identifiers to primitives.

After establishing contact with said chain, assuming that both parties have complete knowledge of expected serialization formats, off-chain communications and exchange of ephemeral data can begin, relying only on the chain for discovery but conducting the actual transfer of information off chain.

Purpose

For the fulfillment of KYC nodes, the establishment of them, bound to an account that controls a libp2p entity needs to be done on-chain, with the ability to distinguish from first-party and (if any) second-party nodes, to avoid attack vectors that rely on domain name similarity and purchase of expired but still hard-coded domains.

This should yield the ability to transfer a subset of "reserved" messages meant for private-public chain bridging (assuming a "store privately, hash publicly" model) that would otherwise be invalid if issued by a public-to-public any-party node.