Skip to main content
Burst lets anyone launch tokens freely. That openness creates early competition around the same idea. Multiple tokens can represent the same meme, narrative, or identity. Burst does not try to block that at launch. It resolves fragmentation later, at migration.

​
Core idea

The first token in an identity cluster to migrate becomes the canonical market. It moves into a Meteora DAMM v2 pool. If later tokens from the same identity also migrate, Burst absorbs them into that canonical token. Their value is merged into the canonical Meteora pool. The non-canonical tokens stop being treated as independent primary markets.
Tokens remain mintable.Liquidity is not burned.Burst keeps migration flexible so markets can converge instead of fragment forever.

​
Why Burst does it

Token PVP is useful when the market is still discovering the best version. It becomes harmful once liquidity splits across obvious duplicates. Burst tries to preserve open creation early, then unify the winning market later.

Before migration

Anyone can launch.Variants can compete.Discovery stays open.

After migration

One identity resolves to one canonical market.Liquidity concentrates.Discovery gets cleaner.

​
How identity resolution works

1

Identity clustering

Burst groups related launches into the same identity_id.
2

Canonical market selection

The first migrated token in that cluster becomes canonical.
3

Merge execution

Later migrated variants are absorbed into the canonical market.
4

Metadata recomputation

Burst recalculates the final name, ticker, and image from merged variants only.

​
1. Identity clustering

Clustering happens off-chain. Burst groups launches only when they appear to represent the same underlying idea. Signals can include:
  • normalized ticker similarity,
  • normalized name similarity,
  • image similarity through perceptual hashing,
  • and optional source references such as a tweet or media link.
This is what prevents unrelated tokens from being merged.

​
2. Migration and merge layer

Migration is the decision point. If no canonical market exists yet, the migrating token becomes canonical. If a canonical market already exists, the new token is absorbed into it. The merge is coordinated off-chain. Meteora DAMM v2 stays the execution layer for the unified market. At merge time:
  • value from the new token is converted into canonical exposure,
  • liquidity is routed into the canonical Meteora DAMM v2 pool,
  • and the non-canonical token is removed from primary discovery.
The result is one post-migration market per identity.
mergeIntoCanonical.ts
await mergeIntoCanonical({
  sourceMint: newTokenMint,
  canonicalMint,
  sourceTokenAccount,
  canonicalTokenAccount,
  user: payer.publicKey,
  meteoraPool: canonicalPool,
})
This simplified flow represents the coordinated merge process. It absorbs value from the new token. It converts that value into canonical exposure. It reinforces a single AMM v2 pool.

​
3. Metadata resolution engine

After every merge, Burst recomputes the canonical metadata. Only migrated and merged variants are considered. Pre-migration 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

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.
These rules prevent flickering. They also make spam-driven overrides harder.

​
4. Visual clustering for images

Image resolution is not based on exact byte-for-byte matches. Burst groups similar images into visual clusters. That allows edited or resized versions of the same meme to resolve together. It also lets a newer meme variant replace an older one naturally when it gains clear support. An image update requires:
  • one visual cluster to become clearly dominant,
  • a clear margin over the current image cluster,
  • persistence over time,
  • and support from multiple distinct deployers.

​
5. 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. Metadata authority is controlled by Burst so updates stay deterministic and consistent.
updateMetadata.ts
await updateMetadata({
  mint: canonicalMint,
  authority: metadataAuthorityPDA,
  name: resolvedName,
  symbol: resolvedSymbol,
  uri: metadataUri,
})

​
What never changes

Canonical market rule

The first migrated token in an identity cluster becomes canonical.

Merge rule

Later migrated tokens in that same identity are absorbed into it.
  • Name and ticker resolve from dominant merged representation.
  • Image resolves from the dominant visual cluster.
  • Overrides require dominance, margin, persistence, and multi-deployer support.
  • Only migrated and merged variants are part of the decision set.

​
Practical outcome

Burst keeps token creation open. It still allows early market competition. But after migration, it collapses duplicate markets into one stronger market. That gives traders a cleaner destination. It gives liquidity a single place to compound. And it gives the best representation of an identity room to win without permanent fragmentation.