Developers can query individual namespaces and look up names within them using
the BNS API.
-$ curl https://core.blockstack.org/v1/namespaces/id/names?page=0
[
@@ -369,7 +370,7 @@ the BNS API.
Each page returns a batch of 100 names.
-Get the Cost to Register a Namespace (reference)
+Get the Cost to Register a Namespace (reference).
$ curl https://core.blockstack.org/v1/prices/namespaces/test
{
@@ -380,7 +381,7 @@ the BNS API.
If you want to register a namespace, please see the namespace creation section.
-Getting the Current Consensus Hash (reference)
+Getting the Current Consensus Hash (reference).
$ curl -sL https://core.blockstack.org/v1/blockchains/bitcoin/consensus
{
@@ -400,7 +401,7 @@ transaction.
-
-
Send a NAMESPACE_PREORDER
transaction (live example).
+
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
@@ -408,7 +409,7 @@ a recent consensus hash in the transaction
(see the section on BNS forks for details).
-
-
Send a NAMESPACE_REVEAL
transaction (live example).
+
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
@@ -420,13 +421,13 @@ has the option to collect name registration fees for the first year of the
namespace’s existence by setting a namespace creator address.
-
-
Seed the namespace with NAME_IMPORT
transactions (live example).
+
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.
-
-
Send a NAMESPACE_READY
transaction (live example).
+
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
@@ -450,7 +451,7 @@ create the same namespace, the one that successfully confirms both the
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 section document. It is highly recommended that
+
Developers wanting to create their own namespaces should read the namespace creation section document. It is highly recommended that
developers request individual support before creating their own space, given the large amount of
cryptocurrency at stake.
diff --git a/_site/core/naming/register.html b/_site/core/naming/register.html
index d7907cf4..bc343bbc 100644
--- a/_site/core/naming/register.html
+++ b/_site/core/naming/register.html
@@ -17,9 +17,9 @@
-
+
+{"url":"https://docs.blockstack.org/core/naming/register.html","headline":"Register a name","dateModified":"2018-10-25T11:28:54-07:00","datePublished":"2018-10-25T11:28:54-07:00","author":{"@type":"Person","name":"Blockstack"},"mainEntityOfPage":{"@type":"WebPage","@id":"https://docs.blockstack.org/core/naming/register.html"},"description":"Register a name","@type":"BlogPosting","@context":"http://schema.org"}
@@ -274,13 +274,13 @@
-
diff --git a/_site/core/naming/resolving.html b/_site/core/naming/resolving.html
index 0453a1aa..a9edd62f 100644
--- a/_site/core/naming/resolving.html
+++ b/_site/core/naming/resolving.html
@@ -17,9 +17,9 @@
-
+
+{"url":"https://docs.blockstack.org/core/naming/resolving.html","headline":"Resolve a name","dateModified":"2018-10-25T11:28:54-07:00","datePublished":"2018-10-25T11:28:54-07:00","author":{"@type":"Person","name":"Blockstack"},"mainEntityOfPage":{"@type":"WebPage","@id":"https://docs.blockstack.org/core/naming/resolving.html"},"description":"Resolve a name","@type":"BlogPosting","@context":"http://schema.org"}
@@ -274,13 +274,13 @@
-
+
Edit this page on Github
- w Oct 22, 2018
+ w Oct 25, 2018
diff --git a/_site/core/naming/search.html b/_site/core/naming/search.html
index dc64a88e..e49edb5c 100644
--- a/_site/core/naming/search.html
+++ b/_site/core/naming/search.html
@@ -17,9 +17,9 @@
-
+
+{"url":"https://docs.blockstack.org/core/naming/search.html","headline":"How to build a Profile Search Index","dateModified":"2018-10-25T11:28:54-07:00","datePublished":"2018-10-25T11:28:54-07:00","author":{"@type":"Person","name":"Blockstack"},"mainEntityOfPage":{"@type":"WebPage","@id":"https://docs.blockstack.org/core/naming/search.html"},"description":"How to build a Profile Search Index","@type":"BlogPosting","@context":"http://schema.org"}
@@ -274,13 +274,13 @@
-
+
Edit this page on Github
- w Oct 22, 2018
+ w Oct 25, 2018
diff --git a/_site/core/naming/subdomains.html b/_site/core/naming/subdomains.html
index c616f4fd..8a24bdd4 100644
--- a/_site/core/naming/subdomains.html
+++ b/_site/core/naming/subdomains.html
@@ -17,9 +17,9 @@