a16z-casper VS cep-78-enhanced-nft

chef@jonas:~/Desktop$ git clone https://github.com/jonas089/a16z-casper chef@jonas:~/Desktop$ cd a16z-casper/contract

Casper NFT Visualizer Thanks to the casper-signer and the casper-javascript-sdk, building Dapps on Casper is achievable. To showcase this, I built a “Casper-Sandbox” demo application using React that is open source and can be found here. If you want to install and test the react app follow the setup guide. You will need React and Node.js to run the app. The “Casper-Sandbox” is an open-source NFT visualizer built to demonstrate some of the capabilities of the Casper Blockchain and the CEP-78 Standard. The app is still under development but already supports minting of “digital” NFTs. The readme includes the latest documentation for the project. Metadata The structure of an NFTs metadata is defined by a json schema. Cep-78 supports both standardized and custom json schemes. Standardized schemes are easier to integrate, whilst custom schemes can be individualized to suit a projects needs best. An example for a standardized json schema (CEP78):

Where the “Can’t be Evil” license URI is stored depends on which metadata schema or standard makes the most sense for a project to follow. Most NFT platforms on Casper will likely comply with the CEP-78 metadata standard. As a metadata URI is a link to a server that returns JSON data, it makes the most sense to include the license in the data returned by the backend.