• ARC-78 URI scheme Key Reg
• ARC-79 URI scheme with App NoOp calls
• ARC-65 AVM Run Time Errors

New Standard Proposal for ASA: Why? We need to deprecate ARC-69 to avoid having to rely on indexers (and find an alternative that covers it completely)

Instead of using IPFS/note-field to store metadata, I want to propose the following: We create a basic application (let's say 1001) with a box-storage BoxMap(UInt64, String, key_prefix="") When creating an ASA, we set the URI to something like algorand://?app=1001&box=. We store the ASA's metadata in the box. Now, any dApp can read the metadata information by reading the box information shown in the ASA's URI.

The pros:

• This metadata can be updated if the smart contract allows it
• We do not need to query an indexer to get the information
• We don't rely on IPFS
• It increases the value lock on-chain.

The cons:

• Not backward compatible
• New Uri Scheme to use/define

A Proof of concept is available here: https://github.com/SudoWeezy/asa_box/tree/main/projects

[ARC-65] will be moved to the last call status next week if ARC-56 is also moving forward [ARC-78/79] will be discussed Async A new ARC will be created for clients to have URIs to query

Applications' Data:

• Local
• Global
• Box
• Teal?

ASA information:

• Creator
• Manager
• Reserve
• Clawback
• Freeze
• AssetName
• UnitName
• Total
• Decimals
• DefaultFrozen
• URL
• MetaDataHash

We will take as examples what has been done with ARC 26, 78, 79, and did