Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

From Makoto of ENS #2

Open
Esk3nder opened this issue Jan 6, 2025 · 0 comments
Open

From Makoto of ENS #2

Esk3nder opened this issue Jan 6, 2025 · 0 comments

Comments

@Esk3nder
Copy link

Esk3nder commented Jan 6, 2025

  1. 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

  2. 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?

  3. 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

  4. 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

@Esk3nder Esk3nder changed the title From Makoto From Makoto of ENS Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant