Notes for This Meeting

Moving the following ARCs from the Draft Stage to Last Call:

• ARC-0027: Provider Message Schema
• ARC-0053: Decentralized, Self-declared, & Verifiable Tokens, Collections, & Metadata
• ARC-0071: Soulbound ASA NFT
• ARC-0082: Querying blockchain information using a URI format

Change to ARC-0 Rules:

• Since the forum will no longer be a place for discussing technical matters, we will reintroduce the process of vetting ARC ideas through GitHub Issues.

Idea for 2025

Open Issues in the go-algorand Repo

• Some issues remain open in the go-algorand repository, such as:

  • Adding an opCode to receive app call sender
  • Increasing the max application program size

  These issues haven't made progress for the moment. It might be time to consider moving forward with the creation of an Algorand Improvement Proposal (AIP) process for the core protocol.

---

Discussion: Adding an "Idle" Status for ARCs

• We are starting a discussion to add an "Idle" status, it might be added between Final and Deprecated.
  • When to trigger Idle Status:
    • If the ARC has been Final for a long time but has not been used by the community.
    • Examples: ARCs 18, 20, 55...
  • Goal:
    • Remove unused ARCs from the "Final" category and clarify what is in active use.
    • Consider triggering this status when an ARC has been Final for 12 months without adoption.

---

Showing ARC utilization by creating a "Can I Use" like website

• Current Challenge:

  • We had a wallet matrix to display which ARCs are used, but it is not user-friendly or easy to find.

• Proposed Solution:

  • Start building a solution similar to CanIUse, with a dedicated website to display ARC usage in a clear, user-friendly manner.