lukechilds
/
docs
mirror of https://github.com/lukechilds/docs.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
263 Commits
80 Branches
0 Tags
152 MiB
 
 
Tree: 8ee85229c1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '8ee85229c1'
${ noResults }
docs/_core/naming/creationhowto.md

3.4 KiB
Raw Blame History

layout permalink
core /:collection/:path.html

Creating a Namespace

There are four steps to creating a namespace:

  1. Send a NAMESPACE_PREORDER transaction (live example). This is the first step. This registers the salted hash of the namespace with BNS nodes, and burns the requisite amount of cryptocurrency. In addition, it proves to the BNS nodes that user has honored the BNS consensus rules by including a recent consensus hash in the transaction (see the section on BNS forks for details).

  2. Send a NAMESPACE_REVEAL transaction (live example). This is the second step. This reveals the salt and the namespace ID (pairing it with its NAMESPACE_PREORDER), it reveals how long names last in this namespace before they expire or must be renewed, and it sets a price function for the namespace that determines how cheap or expensive names its will be. The price function takes a name in this namespace as input, and outputs the amount of cryptocurrency the name will cost (i.e. by examining how long the name is, and whether or not it has any vowels or non-alphabet characters). The namespace creator has the option to collect name registration fees for the first year of the namespace's existence by setting a namespace creator address.

  3. Seed the namespace with NAME_IMPORT transactions (live example). Once the namespace has been revealed, the user has the option to populate it with a set of names. Each imported name is given both an owner and some off-chain state. This step is optional---namespace creators are not required to import names.

  4. Send a NAMESPACE_READY transaction (live example). This is the final step of the process. It launches the namespace, which makes it available to the public. Once a namespace is ready, anyone can register a name in it if they pay the appropriate amount of cryptocurrency (according to the price funtion revealed in step 2).

The reason for the NAMESPACE_PREORDER/NAMESPACE_REVEAL pairing is to prevent frontrunning. The BNS consensus rules require a NAMESPACE_REVEAL to be paired with a previous NAMESPACE_PREORDER sent within the past 24 hours. If it did not do this, then a malicious actor could watch the blockchain network and race a victim to claim a namespace.

Namespaces are created on a first-come first-serve basis. If two people try to create the same namespace, the one that successfully confirms both the NAMESPACE_PREORDER and NAMESPACE_REVEAL wins. The fee burned in the NAMESPACE_PREORDER is spent either way.

Once the user issues the NAMESPACE_PREORDER and NAMESPACE_REVEAL, they have 1 year before they must send the NAMESPACE_READY transaction. If they do not do this, then the namespace they created disappears (along with all the names they imported).

Developers wanting to create their own namespaces should read the [namespace creation]({{ site.baseurl }}/core/naming/namespaces.html) document. It is highly recommended that developers individula support to create your own namespace, given the large amount of cryptocurrency at stake.