To save space, not all details of a data host will be stored on-chain.
Each data host will serve a JSON metadata blob that conforms to the below spec to provide more information about itself.
This metadata json blob will include a signature calculated from the private key associated with this data host’s public key. This allows clients to validate the metadata is authoritative.
| Field Name |
Max Length |
Description |
| moniker |
64 |
The name of the Data Host being registered. Must be unique. |
| WebsiteURI |
2048 |
A URI for a website that provides details about this Data Host. |
| description |
4096 |
A string that can be used to state anything pertinent to this Data Host. |
| location |
|
Physical geolocation |
Fields
- Location: A string specifying the geographic location of this data host (i.e. “Toronto, Ontario, Canada”)
- DaemonURI: A URI where the underlying blockchain daemon can be reached for direct querying (i.e. rpc://1.2.3.4:8444)
- UnchainedURI: A URI where the Unchained service can be reached for direct querying (i.e. https://2.3.4.5:9000)
- PaymentGateway: A string specifying details of the payment gateway in use by this Data Host
- BackupHost: Optional. Allows a Data Host to specify another Data Host to be used in the event this host is unreachable.
- FreeTierRateLimitByIP: number of requests per minute the data host will serve for free (not chain/service specific)
- PaidTierRateLimitByIP: number of requests per minute the data hose will serve for paid users. This should be chain/service specific
- Custom: arbitrary json values outside the metadata specification
- version: version of the metadata this json file subscribes to