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
The description almost match with ENS text record specification https://docs.ens.domains/ensip/5 I think it can almost possible to convert from one format to another
Where do you locate the manifest.json ? Just the root of the project? How do you express if the project has multiple agents? If it’s actually used by https://github.com/operatorlabs/manifest?tab=readme-ov-file#adoption good to mention the actual location of the file so users can actually examine the real use case
The text was updated successfully, but these errors were encountered:
The description almost match with ENS text record specification https://docs.ens.domains/ensip/5 I think it can almost possible to convert from one format to another
I don’t know what the use case for NFT at https://github.com/operatorlabs/manifest?tab=readme-ov-file#nft-collection but maybe it wants to have an ability to include tokenId so that it can point to the specific NFT?
https://github.com/operatorlabs/manifest?tab=readme-ov-file#chains could use https://docs.ens.domains/ensip/9 and https://docs.ens.domains/ensip/11 rather than maintaining own chain directory
Where do you locate the
manifest.json
? Just the root of the project? How do you express if the project has multiple agents? If it’s actually used by https://github.com/operatorlabs/manifest?tab=readme-ov-file#adoption good to mention the actual location of the file so users can actually examine the real use caseThe text was updated successfully, but these errors were encountered: