Token Metadata Now Stays Fresh

What was broken

Until last week, a token's metadata on /tokens/[address] was frozen at the values set when the token first deployed. Edits made later on-chain — via the SDK, the admin section on the token page, or directly via Basescan — were invisible.

The cause: the Liquid factory emits UpdateMetadata, UpdateImage, and UpdateAdmin events when those values change, but the indexer wasn't subscribed to them. Each token's row in the database stayed at deploy-time values forever.

The fix

Indexer release #21 adds handlers for all three. Edits picked up on the next WebSocket tick, typically within 2–4 seconds of the on-chain confirmation.

We also shipped a /v1/replay-updates admin endpoint to backfill historical edits. Every existing token row has been replayed against the chain, so any metadata that was edited but never indexed is now correct.

What this affects

• Token images updated via the admin section now render across the site
• Token descriptions edited via the SDK propagate to the detail page and the catalog
• Admin transfers are reflected in the contract details table

Token deployers: edit via [ EDIT ] on your token's page (admin-only) — the change goes on-chain and the site picks it up shortly after.