Developer Council 2025 01 24 - algorandfoundation/technical-adoption-committee GitHub Wiki

Notes for This Meeting

ARCs in Last Call that did not receive complaints and should be finalized by 15/02/2025:

ARC in Last Call that might need some refinement:

ARC-0053: Decentralized, Self-declared, & Verifiable Tokens, Collections, & Metadata

  • Waiting to get a review of the implementation of ARC-40 before moving forward

ARC-0071: Soulbound ASA NFT

Questions were raised regarding Soul Bound ASAs (SBAs) terminology and functionality:

  1. Terminology:

    • The ARC should consistently use the term Soul Bound ASA (SBA) rather than Soul Bound Token for clarity.

  2. Current Types of SBAs:

    • Issued
    • Held/Claimed

  3. Opt-out Mechanism:

    • Currently, both types of SBAs can be opted out of by sending a Close-Out Transaction.
    • While this isn't an issue in itself, it may not fit all use cases.

  4. Consideration:

    • Depending on the user’s or project’s requirements, we might want to offer an alternative approach where the SBA cannot be “removed.”
    • A potential solution involves using another account or application as the Clawback.

Reference Implementation

We need to define the requirements (via gDocs):

  • Stakeholders for Creation: Determine who should create the reference implementation (Authors, Projects, Foundation).
  • Stakeholders for Maintenance: Define who will maintain it (Authors, Projects, Foundation).
  • Stakeholder Categorization: Differentiate between users and wallets (e.g., For the same ARC, users may write, while wallets may read).
  • Mandatory Elements: Define mandatory components (e.g., Python, TypeScript, tests).
  • Status for Implementation: Include statuses? such as Draft, Final, Audited, Deprecated.
  • Prioritization: Decide what should be prioritized, such as Interface ARCs that refer to Applications.

Considerations:

  • The Algorand Foundation aims to expand the AlgoKit templates repository.
    • Should the ARC reference implementation also be included there?
  • We need a CI/CD pipeline for these implementations.

Sharing Information

  1. Developer Portal:

    • The Developer Portal should become the main point of entry for ARCs and their reference implementations.

  2. Can I Use Website:

    • The "Can I Use" website should be appealing.
    • It might be worth considering making it mandatory for a project to be listed in the Algorand ecosystem overview.