Skip to main content
After every merge, Burst recomputes the canonical metadata. This determines the final name, ticker, and image for the canonical token.

​
How resolution works

Only graduated and merged variants are considered. Pre-graduation noise does not decide the final result. Each merged variant contributes a weighted signal. That weighting can include:
  • absorbed liquidity,
  • deployer distinctness,
  • and recency.
Burst evaluates ticker, name, and image separately.

​
Name and ticker resolution

Name and ticker

Burst resolves these by dominant merged representation.A challenger replaces the current value only if it:
  • represents a majority of merged variants,
  • exceeds the current value by a clear margin,
  • persists for a short window,
  • and comes from multiple distinct deployers.

Image

Burst uses visual clustering, not exact file matching.Images are grouped by perceptual similarity.A new image wins only if one cluster becomes clearly dominant and stays dominant.Learn more
These rules prevent flickering. They also make spam-driven overrides harder.

​
Canonical metadata update

Once Burst determines a new canonical representation, it generates new metadata. That metadata can then be uploaded to storage and applied to the canonical mint. Token metadata is mutable because Meteora supports Metaplex’s Token Metadata extension for fungible tokens. This allows Burst to update the name, symbol, and image of the canonical token as the identity resolves over time. Metadata authority is held by Burst so updates stay deterministic and consistent.
updateMetadata.ts
await updateMetadata({
  mint: canonicalMint,
  authority: metadataAuthorityPDA,
  name: resolvedName,
  symbol: resolvedSymbol,
  uri: metadataUri,
})