"description":"Preorders a name by telling all BNS nodes the salted hash of the BNS name. It pays the registration fee to the namespace owner's designated address."
"signature":"(name-renewal namespace name stx-to-burn new-owner zonefile-hash)",
"description":"Depending in the namespace rules, a name can expire. For example, names in the .id namespace expire after 2 years. You need to send a name reveal every so often to keep your name.\n\nYou will pay the registration cost of your name to the namespace's designated burn address when you renew it.\nWhen a name expires, it enters a month-long \"grace period\" (5000 blocks). \n\nIt will stop resolving in the grace period, and all of the above operations will cease to be honored by the BNS consensus rules.\nYou may, however, send a NAME_RENEWAL during this grace period to preserve your name.\nIf your name is in a namespace where names do not expire, then you never need to use this transaction."
},
{
"name":"name-revoke",
"input_type":"(buff 20), (buff 48)",
"output_type":"(response bool int)",
"signature":"(name-revoke namespace name)",
"description":"Makes a name unresolvable. The BNS consensus rules stipulate that once a name is revoked, no one can change its public key hash or its zone file hash. The name's zone file hash is set to null to prevent it from resolving. You should only do this if your private key is compromised, or if you want to render your name unusable for whatever reason."
"signature":"(name-transfer namespace name new-owner zonefile-hash)",
"description":"Changes the name's public key hash. You would send one of these transactions if you wanted to:\n* Change your private key\n* Send the name to someone else\n\nWhen transferring a name, you have the option to also clear the name's zone file hash (i.e. set it to null). This is useful for when you send the name to someone else, so the recipient's name does not resolve to your zone file."
},
{
"name":"name-update",
"input_type":"(buff 20), (buff 48), (buff 20)",
"output_type":"(response bool int)",
"signature":"(name-update namespace name zonefile-hash)",
"description":"Changes the name's zone file hash. You would send one of these transactions if you wanted to change the name's zone file contents. For example, you would do this if you want to deploy your own Gaia hub and want other people to read from it."
"description":"Registers the salted hash of the namespace with BNS nodes, and burns the requisite amount of cryptocurrency. Additionally, this step proves to the BNS nodes that user has honored the BNS consensus rules by including a recent consensus hash in the transaction. Returns pre-order's expiration date (in blocks)."
},
{
"name":"namespace-ready",
"input_type":"(buff 20)",
"output_type":"(response bool int)",
"signature":"(namespace-ready namespace)",
"description":"Launches the namespace and makes it available to the public. Once a namespace is launched, anyone can register a name in it if they pay the appropriate amount of cryptocurrency."
"description":"Reveals the salt and the namespace ID (pafter a 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."
"description":"Returns true if the provided namespace is available."
},
{
"name":"can-receive-name",
"input_type":"principal",
"output_type":"(response bool int)",
"signature":"(can-receive-name owner)",
"description":"Returns true if the provided name can be received. That is, if it is not curretly owned, a previous lease is expired, and the name wasn't revoked."
Alexander Graebe
4 years ago
Alexander Graebe