Thank you, Larry, for adding to this.
Would you be able to make the live conversation tomorrow, at 10:30 ET?
1 Like
I want an ip address in my universal profile.
Ehy @friedger, i think that IP address and all the DNS settings are out of scope now. We need first a decentralized DNS, then we can enhance BNS with standard zonefile settings from web2.
what about using the url field to store your ip address? something like https://1.2.3.4 should work as a redirect
1 Like
I agree with Larry’s thoughts here, especially the importance of not being too prescriptive. Standards should evolve from real-world usage and successful products. Developers need the flexibility to extend zonefiles without friction, and while on-chain storage has always been possible, we should aim to keep it minimal and efficient, with support for encrypted off-chain data when needed.
I also really like the idea of a lightweight BNSIP process, separate from SIPs. It gives the community a clear, flexible path to propose and iterate on standards without unnecessary blockers. This kind of community-led approach is exactly what BNS needs to keep moving fast.
BNS has a huge future ahead. With its foundation on Stacks and finality with Bitcoin, it has the potential to become the most widely adopted naming system in crypto. The work we’re doing around zonefiles is essential to unlocking that potential. Great to see this energy in the community right now.
2 Likes
I agree that the zone file could be defined in the structure in CBOR format and compressed. If it does not fit, the legacy DNS will be used, but hopefully, it will be better in the structure proposed.
For the zonefile, we need
The domain name associated
(i.e., ubid.app )
The Owner address
(i.e., owner=SP3K21D44E7W3W70HMMCM5GPY963RTD330D5XM1RJ )
We need several records (1 to 5) of the most basic structure to reference the following web services:
Maybe it could be integrated as the tag “srvs” (services?)
Type of service: (i.e. “did”, “dwn”, “subd”, …)
Uri: (i.e. “https://gaia.blockstack.org/hub/1Gt6wCa6qKe9x7dMA1WH14S6BEAzJxZofp/profile.json”)