I have been studying the Algorand ARC-19 and ARC-69 to see which one will better suit my use case. But I am finding it hard to understand them properly.
Can you help me better understand by providing sequence diagram for the data flow and operations that occur with creating an ASA in ARC-69?
To give a bit of context:
URL fieldis immutableReserve Addressis mutable (If it has not been set to the Zero Address & the Manager Address exists)By using a template,
template-ipfs://{ipfscid:1:raw:reserve:sha2-256}ARC-19 allows client to read/display URL based on the value of theReserve Address. (An IPFS hash can be obtained from theReserve Address.)ARC-69 is a community-based convention used for Digital Media.
URL fieldof the Asset points to a Media file (png, jpeg ...)Note Field, which is accessible during the creation/config of the Asset. (If theManager Addressexist)Note Fieldcan only contain 1024 Bytes)Manager Addressis set, Metadata is mutable.ARC-3 is a general Fungible/Non-Fungible Token convention.
URL fieldof the Asset points to an OFF-CHAIN IPFS file containing the Metadata (JSON based on ERC-1155)URL Fieldof the Asset from a non-Archival Node. (Which is way more convenient than using an Indexer)To have mutability with OFF-CHAIN Data (which is encouraged & matches every case), ARC-19 can be combined with ARC-3.
Url FieldMUST be equal totemplate-ipfs://{ipfscid:1:raw:reserve:sha2-256}#arc3Reserve AddressMUST be setManager AddressMUST be setIf you have more questions about ARC or Algorand in general, I encourage you to join the Discord and the Forum.