Add VIP: Data URL Token Metadata

VIPs
1

This VIP proposes an extension to existing token standards (ERC-721/ERC-1155) to enable storing token metadata directly on-chain using data URLs. This approach provides an alternative to external metadata storage solutions like IPFS or centralized CDNs, offering improved data availability and permanence while maintaining compatibility with existing token standards and tools.

VIP PR: Add VIP: Data URL Token Metadata standard by kyleboe · Pull Request #86 · vechain/VIPs · GitHub

1 Like
2

Hey @kyle.vet, this should already be possible with the ERC-721 Metadata Extension (ERC721Metadata), I’m not sure we need a VIP for this

    /// @notice A distinct Uniform Resource Identifier (URI) for a given asset.
    /// @dev Throws if `_tokenId` is not a valid NFT. URIs are defined in RFC
    ///  3986. The URI may point to a JSON file that conforms to the "ERC721
    ///  Metadata JSON Schema".
    function tokenURI(uint256 _tokenId) external view returns (string);
1 Like
3

Thanks for the response!

While it is technically possible without any modification to the ERC721Metadata standard, I believe there is value in making this declaration as a show of intent to support this type functionality across the VeChain ecosystem. Storing data on-chain plays to VeChain’s strengths and further differentiates us from other projects. A VIP such as this enables marketing VeChain as a “fire-and-forget” blockchain for industries who don’t want to bother with the cost of implementing and maintaining an API.

I do acknowledge that it is a relatively small declaration of intent but as I said in the PR, we are currently tightly coupled to other blockchain projects/services in a way that can add cost and complexity when on-boarding more change-adverse clients. In an environment where every line-item on an expense report is an opportunity for a client to walk away, this seems like a net-positive when looking at it from an enterprise perspective.

1 Like