You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To allow creation of Lens publication as well as regular video NFTs. For that we need to implement some kind of NFT metadata templating in the task-runner.
This is to allow minting both regular NFTs for marketplaces but also the Lens publications which have additional fields (including some “dynamic” fields, using the CID of the file exported to IPFS).
We can implement this in a couple of ways, here are some ideas:
A full templating language on the requests, setting fields to something like {{ .output.ipfs.videoFileUrl }}, or
Just a set of pre-defined templates in the code (e.g. right now erc721 or lens_publication). We just specify on the request which template to use. This will give us less flexibility but should be much simpler to implement, so may be preferred.
Defintions of done:
1. Can export to IPFS a metadata corresponding to a Lens publication, following all the spec described here
2. Can also export to IPFS a metadata corresponding to a regular Video NFT without any of the Lens-specific fields
The text was updated successfully, but these errors were encountered:
To allow creation of Lens publication as well as regular video NFTs. For that we need to implement some kind of NFT metadata templating in the
task-runner
.{{ .output.ipfs.videoFileUrl }}
, orerc721
orlens_publication
). We just specify on the request which template to use. This will give us less flexibility but should be much simpler to implement, so may be preferred.https://www.notion.so/livepeer/Lens-Integration-e756c036e6c741de97d8e9ef1c351e84#6394c0df8bdc464f9285aecb458161f3
Defintions of done:
1. Can export to IPFS a metadata corresponding to a Lens publication, following all the spec described here
2. Can also export to IPFS a metadata corresponding to a regular Video NFT without any of the Lens-specific fields
The text was updated successfully, but these errors were encountered: