Unaddressed Metadata Issues In the Ethereum Ecosystem

Dynamic Metadata

As things are, most metadata on Ethereum is stored in the centralized databases of paid services like Google Storage and Trust Wallet, or distributed ones like IPFS, and represented by tokens and applications in the form of addresses saved as uri parameters.

That doesn’t measure up to the security standards of Ethereum. When those services cease to be operational or available, that metadata is gone. For NFTs in particular, that will be tantamount to the complete loss of their value. Metadata must be always on-chain, decentralized, and censorship-resistant.

The Dynamic on-chain Metadata Protocol, natively integrated into the Item standard, allows you to save and regenerate Metadata on-the-fly (and so dynamically) 100% on-chain.

But that's not all.

How Does It Differ From Other On-Chain Metadata?

A year after v1 of the Items protocol first brought fully on-chain data to Ethereum, others in the industry are beginning to follow suit, such as CryptoPunks, and Uniswap with its NFT LPs.

But while this is great, there are some major limitations to their implementations, which are just static, single-purpose verticalizations.

The Dynamic on-chain Metadata protocol differs in that it is the first fully decentralized, fully-fledged protocol for anyone to easily use and manage on-chain metadata for their tokens.

Developers can use it code their metadata engine smart contracts according to their needs. Using an Extension, they can granulate the way their Item Collections are governed via multi-layered permission systems.

Last updated