Greetings All,

This version update incorporates a change in the record format to take into
account web3 wallet address variations.

Its proposed that the record format consist of

<wallet family>:<reference or coin name>:<address>

The wallet family is pulled from "Chain Agnostic Namespaces", as is
references.  The Coin Name is referenced from SLIP-044.

Small typographical and syntax changes were also made.

Thanks
Shay

---------- Forwarded message ---------
From: <[email protected]>
Date: Mon, Aug 11, 2025 at 1:44 AM
Subject: New Version Notification for
draft-chins-dnsop-web3-wallet-mapping-03.txt
To: Shay Chin <[email protected]>


A new version of Internet-Draft draft-chins-dnsop-web3-wallet-mapping-03.txt
has been successfully submitted by Shay Chin and posted to the
IETF repository.

Name:     draft-chins-dnsop-web3-wallet-mapping
Revision: 03
Title:    DNS to Web3 Wallet Mapping
Date:     2025-08-11
Group:    Individual Submission
Pages:    8
URL:
https://www.ietf.org/archive/id/draft-chins-dnsop-web3-wallet-mapping-03.txt
Status:
https://datatracker.ietf.org/doc/draft-chins-dnsop-web3-wallet-mapping/
HTML:
https://www.ietf.org/archive/id/draft-chins-dnsop-web3-wallet-mapping-03.html
HTMLized:
https://datatracker.ietf.org/doc/html/draft-chins-dnsop-web3-wallet-mapping
Diff:
https://author-tools.ietf.org/iddiff?url2=draft-chins-dnsop-web3-wallet-mapping-03

Abstract:

   This document proposes an implementation standard for mapping wallets
   to domain names using the new WALLET RRType, allowing for TXT record
   fallback while the WALLET RRType propagates through DNS providers.
   The goal is to provide a secure and scalable and unbiased way to
   associate wallets with domain names, enabling seamless lookup as well
   as suggesting required authentication mechanism.  The proposal relies
   on DNSSEC or security successors to ensure trust and security.



The IETF Secretariat
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to