femtos

Elysium · Lifecycle

Token across layers

One token from its Elysium launch to its HyperEVM mirror, HyperCore spot and perps, each link proven or marked inferred.

GET https://api.femtos.xyz/v1/tokens/{token}/lifecycle

Parameters

ParamInExample or values
tokenpath<token>

Example

curl -H "Authorization: Bearer $FEMTOS_KEY" "https://api.femtos.xyz/v1/tokens/<token>/lifecycle"

Key: Authorization: Bearer $FEMTOS_KEY or X-API-KEY. Get a free key, or with no browser through agent onboarding.

Response fields

FieldTypeMeaning
stagestring | nulllast stage reached: launched · registered · enrolled · committed · bridged · listed · perp
stages[]object{stage, reached, exact, basis, at {layer, block, time, tx}, observedAt, source, detail}
addressesobjectelysium · hyperevm · hypercore {index, spot} · perps[]
links[]object{from, to, relation, exact, basis: event | registry | attestation | metadata | name}
conflicts · unavailablestring[]sources that disagree · that could not answer
feesobject | nullexact fees of the pool from its events (Ascend)
tokenpathalso a HyperEVM address, core:<index>, a HyperCore name or perp coin

Related: Lifecycle

  • Lifecycle stage changes WS ascend.lifecycle
    A message when a launched token reaches its next stage: listing desk, HyperEVM mirror, HyperCore spot, perp.
  • Launch timeline GET /v1/launches/{token}/timeline
    The whole life of a launch as ordered events with running state.

More