|2 years ago|
|.github||2 years ago|
|mappings||2 years ago|
|nix||2 years ago|
|.gitignore||2 years ago|
|API_Terms_of_Use.md||2 years ago|
|README.md||2 years ago|
|Registry_Terms_of_Use.md||2 years ago|
|shell.nix||2 years ago|
This repository provides a means to register off-chain token metadata that can map to on-chain identifiers (typically hashes representing asset IDs, output locking scripts, or token forging policies).
A server exposes the functionality of a key-value store, allowing users and applications to query registry entries through a RESTful API.
While this registry is limited in scope to handle native tokens only, it will also serve to facilitate a discussion and introduce a standard for a metadata distribution system that is currently put forward as a draft CIP.
New submissions to this registry will take the form of a GitHub Pull Request with the addition of one JSON file to the mappings/ folder. Submissions will be subject to automated checking for well-formedness and human vetting before being merged to the registry.
Updating existing entries
Modification of entries in this registry will take the form of a GitHub Pull Request with the modification of one or more JSON files in the mappings/ folder. Submissions will be subject to automated checking for well-formedness and human vetting before being merged to the registry.
Semantic content of registry entries
Each entry contains the following information:
||Required||The base16-encoded policyId + base16-encoded assetName|
||Required||The script that hashes to the policyId|
||Required||A human-readable name for the subject, suitable for use in an interface|
||Required||A human-readable description for the subject, suitable for use in an interface|
||Optional||A human-readable ticker name for the subject, suitable for use in an interface|
||Optional||A HTTPS URL (web page relating to the token)|
||Optional||A PNG image file as a byte string|
||Optional||how many decimals to the token|
For a comprehensive description of all fields and how to generate them, please see offchain-metadata-tools.
Submission well-formedness rules
Submissions to the registry must consist of a single commit, directly off the master branch of the cardano-token-registry repository.
Submissions must add or modify files in the mappings/ folder.
The file name must match the encoded
"subject"key of the entry, all lowercase.
The maximum file size of a single metadata entry is 370KB.
Users and applications can query this registry through an API at
The API documentation and source code for the server implementation is available with the offchain-metadata-tools.
Use of the