Dynamic NFT Rendering
Owl Protocol advocates for client-side rendering where possible.
With all of the Dynamic NFT's data on-chain, and the IPFS-hosted Collection JSON Schema you have all the data you need to recreate any NFT's rendering.
The final piece of the puzzle is a client-side SDK that would allow any dApp, Web3 game or website to integrate and render the NFT, without relying on a back-end server.
How It Works
We maintain backwards compatibility with existing marketplaces with
tokenURI( tokenId )calls
getDNA( tokenId )which returns a metadata JSON compatible with most marketplaces
The marketplace may integrate a client-side SDK to render the NFT in the browser, but as a fallback the NFT may also point to a decentralized network that can render the NFT. Possible solutions to this include IPNS, or a DAO controlled endpoint.
However, any Web3 game, dApp, or website can easily integrate our open-source SDK which intercepts the NFT's on-chain data and translates it into the rendering directly in the game client, mobile, or browser.
Rendering a Dynamic NFT Step-By-Step
We start with a Webapp (dApp), Web3 Game, or NFT Marketplace, that wants to render the Dynamic NFT.
The application calls the standard smart contract’s
tokenURI()method ensuring backwards compatibility.
The dNFT smart contract returns a
tokenURIthat includes the IPFS hash of the Collection's JSON Schema mappings and the actual on-chain data (DNA).
The application can either render the image in-app with the SDK, or call the failover API endpoint if deployed by the creator.
In either case, a metadata.json is produced with the base64 encoded image for rendering, and the list of traits as usual. In more advanced cases where the rendering is 3D, we recommend taking a static 2D snapshot of the 3D model, but you can conceivably also return 3D graphics files, and or an animated MP4/GIF/video which is supported by some marketplaces.
See It In Action
NFT with Hat
NFT with Hat Removed
In this example we are creating a Dynamic PFP (Profile Picture NFT).
- The hat is its own NFT: it can be detached and re-attached to the main NFT.
- When you attach the hat, the PFP will show the hat.
- When you remove the hat, it can be tradeable with other hats or sold.
- The on-chain data, and JSON Schema is all that is required to render the NFT graphics.
- No centralized back-ends, or dependencies on other tools. Our
nft-sdkis the only thing a client/browser needs to render the NFT.