AlgoKit Lora 2.4.0-beta pulls ASA metadata from an on-chain registry via ARC-89

Where an asset's identity actually lives

An Algorand Standard Asset (ASA) — the layer-1 mechanism that lets anyone issue a token, from a stablecoin to an NFT — carries only the essentials on the ledger: a name, a unit name, a total supply, decimals and a URL. Everything that makes a token legible to a buyer or an application, its image, description and trait data, has never had a dedicated home on-chain. Lora¹, the visual explorer that ships with the AlgoKit² developer toolkit, has spent its life bridging that gap by stitching together whatever metadata standard it could find.

That changed in April. Version 2.4.0-beta.1 of Lora, released April 14, 2026, can read an asset's metadata directly from a registry that lives inside the Algorand ledger itself. The release changelog gives the change one line — 'support arc-89' — but the shift is structural: instead of fetching an asset's description from a file host or a search index, the explorer now reads it out of the chain.

Three generations of off-chain metadata

ASAs were designed with a deliberately minimal parameter set, and the ecosystem had to improvise the rest. The ARC-89 specification³ describes what came before in plain terms: the absence of a native metadata store led the ecosystem to adopt 'less-than-ideal solutions', including 'hacking on the ASA RBAC roles to get asset metadata mutability'.

Each generation solved one problem and created another, and every consumer of asset data — a wallet, a marketplace, an analytics dashboard — inherited the tradeoff. ARC-89, which explicitly supersedes both ARC-19 and ARC-69, is the attempt to end the chain of workarounds by making the chain its own source of truth.

ARC-89: A registry built into the chain

The standard defines a singleton application — one smart contract, deployed once — whose boxes hold one record per asset, keyed by the asset's raw eight-byte ID. A fixed 51-byte header carries reversible and irreversible flags plus a metadata hash that binds the record's contents, and longer content is paginated to respect the protocol's return-size limits. Reads go through algod, the node API, or directly from inside other smart contracts running on the AVM, Algorand's smart-contract virtual machine — so a contract can fetch and verify an asset's metadata in the same transaction that trades it.

The ARC was proposed on September 22, 2025, and is sponsored by the Algorand Foundation. The Testnet registry is live at application 753324084⁴; its creator account has since built 49 test applications and was still fielding application calls as recently as early May 2026. The MainNet deployment is unfinished in both places that matter: the registry's deployment table reads 'TBD', and Lora's network configuration wires Testnet to the live application while leaving MainNet and LocalNet undefined.

What the Lora beta actually changed

Lora — reachable in the browser at lora.algokit.io or through the 'algokit explore' command — is the visual layer of the AlgoKit toolchain, sitting alongside a visual transaction builder, an app-deployment lab and a TestNet faucet. Its repository⁵ is open source, and the ARC-89 work landed through pull request #582, carried by a merge that its author, Patrick Dinh⁶, described as an 'Empty PR to trigger the release'. A follow-up beta, v2.4.0-beta.2, arrived in May.

The data layer itself is compact. A fetchArc89Metadata() function calls the Foundation's asa-metadata-registry-sdk⁷, asks the registry for the asset's box, and returns nothing when the box does not exist — in which case the asset page falls back to whatever ARC-3, ARC-19 or ARC-69 record it can still find, so existing views keep working. The repository also carries a dedicated arc89-migrate module, migration tooling whose internals are not documented in the material reviewed.

That the change stayed contained is a payoff of a design goal Lora set at the start: operational simplicity, running directly on algod and the indexer with no custom backend. A new metadata source is therefore a new call to a node rather than new infrastructure to operate. The live view makes the point vivid — on August 7, the mainnet home page ticked through ten new blocks in 25 seconds.

A standard still waiting for Mainnet

For all the plumbing, adoption is measured in tens. The read library Lora itself uses was downloaded 18 times in the last week and 65 times in the last month. The standard is, for practical purposes, unproven anywhere outside its own sponsor's stack.

The central design feature is also the sharpest tradeoff: 'Once deployed, the ASA Metadata Registry MUST NOT be updated.' A contract that can never be patched cannot be fixed if its logic contains a bug, and it cannot be extended later to carry richer metadata formats — the only remedy would be an entirely new deployment plus a migration of every registered asset. Combined with the blank MainNet row described above, everything a developer can do with ARC-89 today happens on TestNet.

It is also worth being clear about who is demonstrating what. The Foundation that sponsors the ARC also maintains the explorer and publishes the read SDK, so Lora's ARC-89 support is an organization dogfooding its own standard — not independent evidence of demand. The ARC entered a Last Call review with a February 1, 2026 deadline; a snapshot taken months later still lists it as Last Call, leaving the outcome of that review cycle unconfirmed.

What on-chain metadata buys

If the MainNet deployment lands, the difference shows up in the smallest interactions: a wallet rendering an asset's image, a marketplace displaying traits at settlement. Today those lookups depend on a host that might go away. With ARC-89, the same record can be fetched and verified in one round-trip to a node — or inside the very transaction that transfers the asset — and it remains part of chain state as long as the chain does. Adoption is still in the tens of downloads a month, and that is the honest measure of how far the standard has to travel. What Lora's beta demonstrates is that the path works end to end, and it gives the ecosystem a reference implementation to copy when the registry finally reaches MainNet.