Skip to content

ARC-62 - Integrate with ARC-54, ARC-89, and update reference implementation#368

Open
cusma wants to merge 14 commits intoalgorandfoundation:mainfrom
cusma:arc62
Open

ARC-62 - Integrate with ARC-54, ARC-89, and update reference implementation#368
cusma wants to merge 14 commits intoalgorandfoundation:mainfrom
cusma:arc62

Conversation

@cusma
Copy link
Contributor

@cusma cusma commented Jan 21, 2026

This PR does not introduce any breaking change to the standard; the interface is preserved.

We introduce support for ARC-54 (ASA burning address) and ARC-89 (which extends this ARC).

We provide an updated reference implementation for a singleton App that will reduce friction on the adoption.

UPDATE: Based on feedback from the Dev Council meeting, the custom labels have been increased to 4.

@github-actions github-actions bot added the t-arc label Jan 22, 2026
@cusma cusma changed the title ARC-62 - Integrate with ARC-89 and update reference implementation ARC-62 - Integrate with ARC-54, ARC-89, and update reference implementation Jan 23, 2026
@cusma
Copy link
Contributor Author

cusma commented Jan 23, 2026

The reference implementation of the singleton App provides the following "non-circulating" labeled-addresses for an ASA:

  • Reserve (Treasury)
  • Burned (ARC-54)
  • Locked
  • Custom (user-defined meaning)

Should we add some more usual non-circulating labels as:

  • Vested
  • Escrowed
  • Staked
  • Collateralized
  • Frozen / Siezed

Or maybe add just other "custom" addresses (with user-defined meaning)?

@cusma
Copy link
Contributor Author

cusma commented Feb 11, 2026

The reference implementation of the singleton App provides the following "non-circulating" labeled-addresses for an ASA:

  • Reserve (Treasury)
  • Burned (ARC-54)
  • Locked
  • Custom (user-defined meaning)

Should we add some more usual non-circulating labels as:

  • Vested
  • Escrowed
  • Staked
  • Collateralized
  • Frozen / Siezed

Or maybe add just other "custom" addresses (with user-defined meaning)?

Based on feedback from the Dev Council meeting, the custom labels have been increased to 4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant