Some q&a that @marvin.id recently raised:
- How can a namespace owner define the domain registration fee? Was it considered to have the option to delegate the task to a smart contract via a trait? If not, is this worth discussing?
A: Most BNS behavior is preserved as part of the port, including this API. See https://docs.blockstack.org/references/blockstack-cli#namespace_reveal and the
namespace-revealfunction in the BNS contract
- Can the namespace be populated by as many names as required using NAME_IMPORT?
A: In theory, yes. See the name-import function in the BNS contract.
- Are there any plans to create a background service that resolves BNS names? That is to say, installable software that hooks into the system’s DNS chain so that the user’s machine can resolve BNS names like it would any other. (For example, entering “muneeb.stacks” in the browser will trigger a lookup and DNS-compliant response.)
cc @diwaker would be able to comment on questions 3 and 4 above?