• Market Cap
    $2,038.963B -3.66%
  • POW Market Cap
    $1,425.480B -6.32%
  • POS Market Cap
    $192.496B 1.89%
  • Masternodes Market Cap
    $5.935B -1.07%

Tezos TZIP-16 standard and developers tool on Tezos network

By RafaƂ - 2020-10-06

After the huge success encountered by the project, developers on Tezos have increasingly been adopting and testing smart contracts based on the token standards FA1.2 (TZIP-7) and FA2 (TZIP-12). Technically speaking, TZIP-16 is a standard for accessing contract metadata in JSON format in on-chain storage or off-chain using IPFS or HTTP(S).

The goal of TZIP-16 is to provide a standardized location and shape of contract metadata, easing the integration, discoverability and querying of Tezos smart contracts for applications, explorers, and wallets. It also enable developers to focus more on product development and less on questions of how to integrate with wallets and external parties such as wallets or other components. To accompany this ease of use for developers, the team has also introduced the future TZComet, a still-in-development editor, validator, and explorer for contract metadata on Tezos. TZComet contains Metadata JSON Validation, URI Validation, and a Michelson PACK Parser. It will confirm whether the metadata/URI of a contract is valid and if a contract can be parsed by Michelson (the Tezos smart contract language).

The advantages of TZIP-16

Many smart contracts need to define metadata that is not included in the contract script, whether corresponding to the contract code itselt or for how it relates to off-chain data. This solution is the key to address this issue as TZIP-16 proposes a method of finding specific metadata about the contract such as provenance information, references to other implementation standards, off-chain views and enables developers to create their own custom extensions. This metadata is described using a JSON format and a URI scheme is used to locate the metadata, whether on-chain (as in contract storage) data or off-chain (as in web-services or IPFS). By adopting this standard, smart contract authors and wallet/indexer implementers can finally agree on both the location and contents of a contract’s metadata itself.

More information regarding TZIP-16 and TZComet can be found at https://tezos.com/