-
Notifications
You must be signed in to change notification settings - Fork 14
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
Ideas for meta 721 protocol #7
Comments
Welcome. thank you for all your great comments on ORC-721 - it's still early (starting with the basics). And thanks for highlighting the dune analytics dashboard. |
Another idea, because now we have Recursive Inscriptions: Why not add a comment to the SVG files (see Recursive Punks example) and avoid complex html+json code of all the Ordinals 721 protocols (https://dune.com/ordinalstats/bitcoin-tokens) |
@TalerOrd a little update on your suggestions:
starting with the d.i.y. (recursive) apes collection - see https://ordinals.com/inscription/610ad953a48ce514ca71933b40228a366ef5edb8f6581ac20dca3098d618c7b2i0 you can now use / list as many inscriptions as you like - incl. mix'n'match 1/1 PNGs or spritesheet PNGs.
note: ordgen / ORC-721 has NO complex html+json code for "on-chain" rendering - the mint inscription is text. you CAN generate "classic" recursive inscriptions in the .SVG format "automagically". for samples see https://ordtest.github.io. |
Thank you for your orc-721! Here are some ideas to so that it becomes the standard 721 protocol:
Other 721 protocols gains more traction, see https://dune.com/ordinalstats/bitcoin-tokens . Reason could be the above points because brc721 and crc721 are more attractive for creators. And more creators means more possibilities to mint, and that means more minters...
The text was updated successfully, but these errors were encountered: