bnswg / initiatives

1 stars 0 forks source link

Enable hierarchal namespaces governed by smart contract #4

Open larrysalibra opened 2 years ago

larrysalibra commented 2 years ago

BNS as it exists today has three types of names:

@MarvinJanssen suggested that instead of the simple pricing and expiration rules of BNSv2, that each namespace could be instead governed by its own smart contract. Namespace smart contracts could have their own rules for how names (or sub-namespaces) in their namespace are governed. It is easy to imagine creative ways that this could be used to unlock new opportunities for our ecosystem and seems like something worth exploring.

friedger commented 2 years ago

Subdomains are stored on-chain in bulk txs. Owners of subdomains have the same on-chain experience as name owners.

Subdomains are subject to price and expiration rules of the owner of the name. Subdomain owners trust the owner of the name to handle name transactions in their name.

markmhendrickson commented 2 years ago

Owners of subdomains have the same on-chain experience as name owners

This is true except (as we discuss briefly yesterday) owners of subdomains can't transfer them to another address unless they get permission top-level name owner somehow?

larrysalibra commented 2 years ago

Subdomains are stored on-chain in bulk txs. Owners of subdomains have the same on-chain experience as name owners.

@friedger Where are subdomains stored on-chain? In the Stacks docs, they say that subdomains are stored off-chain. Is it possible to resolve subdomains with the BNS smart contract?

Screen Shot 2022-02-25 at 20 16 16
friedger commented 2 years ago

@larrysalibra They are stored in attachments of an name-update tx of the registrar's on-chain name.

It is not possible to look them up via BNS smart contract.

friedger commented 1 year ago

Ryder Handles (https://handles.ryder.id) is an implementation of namespaces governed by smart contract: https://github.com/Light-Labs/stacks-name-system