reinamora137
commented
4 weeks ago how is the 'collection name' stored in the SRC-721R deploy? That's the main part that needs to be added to the indexer so we can drop all the mints into the collection table properly.
Also perhaps identify the SRC721-R deploy so it displays a placeholder image rather than the broken ones. like in this deploy transaction: https://stampchain.io/stamps/dbe23d8623963a433a9c455416c2af1cbb11274d182b5166ffad95582c9a308f.svg
The other item it would be nice to flag them as SRC-721R in the ident field to go along with the other 'sub' protocols ( SRC-721,SRC-20,SRC-101). this will make querying for both collection name and 'recursive' collections easy on the frontend
EDIT: - oh i guess there isn't a differentiation with the SRC721 vs 721R deployment structure it's just the usual json with the collection name there. was confusing looking at it from the deploy image side. will need to update that so it uses a placeholder image as well on the deploy. Have to get this in queue.
https://github.com/DerpHerpenstein/src-721/tree/draft_version_r
TLDR: SRC721 looks like this:
{"p":"src-721","op":"mint","c":"A9286823293586848000","ts":[3,3,3,0,4,2,0]}SRC721R looks like this op return:
STAMP:721|c:A0123456789123456789|op:mintolga data:<script src=/s/A12389842328028445000 id=1234></script>The op return contains the 721 designation, the mint of and the collection reference and the olga data contains the ts reference in the src (the trait is a js file for a generative collection instead of an image file). This way all the same information as the original stc721 is present in the tx for easy indexing.