Ideas for meta 721 protocol about generative-orc-721

[TalerOrd]

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)

[geraldb]

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.

[geraldb]

@TalerOrd a little update on your suggestions:

use more than one image incription as source

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.

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

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.