Recover the effective ARC-69 metadata from Algorand asset configuration history

An ASA can evolve its on-chain ARC-69 metadata through configuration transaction notes. Looking only at the original creation note can show an outdated level or description.

Inspect notes for the exact asset ID

Obtain confirmed asset configuration history for the target ID, including its creation. Decode each candidate note from the transport representation to bytes, then parse a UTF-8 JSON object. The example is a metadata payload after decoding. Verify the standard marker and schema.

{
  "standard": "arc69",
  "description": "Season two item",
  "properties": { "level": 2 }
}

Order valid updates by their chain position

If two valid updates occur in the same round, use their intra-round transaction order to choose the later one. A payment note containing identical JSON cannot update an ASA’s ARC-69 metadata. Preserve the winning transaction ID with the decoded payload and treat incomplete indexed history as an unresolved lookup.

Sources