stjet/bns
1
0
Fork 0
mirror of https://github.com/stjet/bns.git synced 2025-12-29 11:19:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

optional max rpc calls after tld crawl for resolver

Browse Source
This commit is contained in:
stjet
2024-11-24 23:48:41 +00:00
parent 327a80c8c8
commit bb7e857b5e
39 changed files with 149 additions and 138 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
bns_protocol.md
View File

@@ -1,4 +1,4 @@
*Version 1.0.0 release-candidate 2*
*Version 1.0.0 release-candidate 3*
Very similar to [Airtune's Banano NFT protocol](https://github.com/Airtune/73-meta-tokens)
@@ -120,7 +120,7 @@ Domain metadata can be anything. However, in order for domain metadata to be eas
A domain name cannot have the `.`, `\u0000`, or `"` characters in it. Domain names are all lowercase.
> Maybe alphanumeric only?
> Currently, it is recommended that registrars only issue lowercase, alphanumeric domain names. Likewise, applications supporting BNS domains may safely assume that domain names will only be lowercase and alphanumeric. This may become required in a later version of the protocol.
# Implementation
@@ -142,7 +142,7 @@ Also, for the convenience of the user (so they can do a Domain Resovler and Doma
Domain owners will need some specialised software to manage domains. Generating/storing Domain Accounts, transferring domains, and setting/changing their resolved address are all simple. Changing domain metadata is a bit more complicated and involves uploading the metadata file to IPFS. The demo client supports converting IPFS Cid v0 into metadata hashes, and then declaring that metadata hash.
As BNS domains can be burned if sent/received improperly, **it is important that TLD and Domain Accounts are not imported into regular wallets** which may do things like auto-receive. As such, it is recommended that BNS wallets (and wallet-like software) generate seeds for TLD and Domain Accounts in a unique (that is, not 64 hex characters) format, so that those seeds cannot be easily imported into regular wallets by uninformed users. Obviously, BNS wallets should also accept that unique seed format. Arbitrarily, because base32 is annoying, the recommended unique seed format is a simple change of the hex characters 0-9 to g-p and A-F to q-v. This will be called the "BNS Seed Format", or the "BSF Hex".
As BNS domains can be burned if sent/received improperly, **it is important that TLD and Domain Accounts are not imported into regular wallets** which may do things like auto-receive. As such, it is recommended that BNS wallets (and wallet-like software) generate seeds for TLD and Domain Accounts in a unique (that is, not 64 hex characters) format, so that those seeds cannot be easily imported into regular wallets by uninformed users. Obviously, BNS wallets should also accept that unique seed format. Arbitrarily, because base32 is annoying, **the recommended unique seed format is a simple change of the hex characters 0-9 to g-p and A-F to q-v. This will be called the "BNS Seed Format", or the "BSF Hex".**
## Non-BNS wallets