Universal Asset Layer
Launchpads expose different names, APIs, lifecycle states and onchain events. The Universal Asset Layer translates those differences into a versioned NormalizedAssetState understood by the market engine.
Normalized identity
An asset identity includes:
- chain namespace and chain ID;
- canonical contract or asset address;
- symbol and display name;
- launchpad and launch mechanism;
- stable aliases used by supported host sites.
Identity is not inferred from symbol alone. Symbols are neither globally unique nor immutable.
Normalized state
Depending on source availability, a state snapshot can include:
- price, valuation, liquidity and volume;
- launch stage and graduation progress;
- creation and migration timestamps;
- holder or activity measurements;
- source, observation time, finality and freshness;
- a capability set describing which market primitives are currently valid.
Every numeric value carries a unit and observation time. Missing data stays missing; adapters must not turn unavailable values into zero.
Discovery data versus durable market data
Explore can display short-lived launchpad listings from host APIs and cache them locally with a TTL. This keeps broad discovery data out of the durable market database.
An asset becomes durable when it enters a market creation workflow, receives a frozen question or has user positions. The durable record preserves the identity and evidence needed for later audit and settlement.
Source priority
Source selection depends on the field:
- chain state is preferred for onchain facts;
- a launchpad’s API can be authoritative for launch-specific metadata;
- independent market-data providers can supply quoted prices;
- DOM extraction is a compatibility fallback for discovery, not settlement authority.
Adapters must expose data provenance so downstream engines can apply field-specific trust and freshness rules.