Contract state and settled event logs are the primary source for launch configuration, hook behavior, balances and receipts. Explorer or market APIs may enrich discovery, but they must be labelled and cannot override contract truth for a transaction decision.
Every action that can move value should re-read the relevant onchain state immediately before preparing the wallet request. Indexed history is for navigation and aggregates; it is not authorization.
Receipt over animation. A pending toast or wallet approval is not a confirmed transaction.
Spark displays the block used for bounded reads whenever that provenance matters. If a registry cap, failed read or incomplete time window excludes records, the interface says so. Counts and rankings computed from only part of a registry are labelled as partial.
Current Spark profile pages share a 30-second server snapshot of bounded chain reads. That cache controls request fan-out; it does not expand coverage or turn stale values into transaction authorization. Complete lifetime activity and earnings require a reorg-aware indexer; until that exists and is reconciled, Spark does not turn a bounded scan into a lifetime claim.
Price charts are built from settled trades. Empty spans draw no candle and a carried open is explicitly marked. Volume covers the displayed window and venues only. FDV is a live ETH price multiplied by fixed token supply, not a dollar oracle value.
The project-token band is explicitly labelled and reserved for Spark's own token, whose launchpad relation is read at the same pinned block. A zero record opens its separate market view, a matching launch record routes to the launch page, and an unavailable or inconsistent result makes neither claim. Launches remain in one grid and can be ordered by measured volume, FDV, Blockscout-indexed holder addresses or launch block. Unavailable values sort last; Spark does not turn missing data or sponsorship into organic rank.
V2 Launch Boost and Lock Rewards are source-ready candidates, not deployed products. No complete schema-3 V2 manifest is checked in, so Spark keeps V2 reads and wallet writes closed. Local tests, simulations and candidate addresses are not deployment evidence.
If V2 is released, Boosted would be a separate, clearly labelled paid rail. It ranks active positions by net refundable principal multiplied by the disclosed 30-, 90- or 180-day term weight. The server pins one block, verifies the release manifest and contract runtimes, rechecks that the supported launchpad records the same creator and token, and excludes hidden or expired entries. Missing or inconsistent registry coverage makes the rail unavailable and withholds paid rankings; it never changes or falls back into organic Discover ordering.
A V2 Lock Rewards position joins the next immutable epoch and settles only complete epochs. Epoch 0 is two hours of lock-only operation from deployment; epoch 1 is two hours with fees and Boost open; epoch 2 bridges to the first Monday 00:00 UTC strictly after epoch 1 ends; all later epochs are Monday-to-Monday weeks. A Launch Boost fee is ceiling-rounded to 1% only when an already-eligible cohort exists at the pinned state; otherwise the fee is waived rather than reserved for future lockers. Claimable amounts are realized contract balances, not estimates, and they may be zero. There is no APY or guaranteed return.
The superseded V1 contracts and one deployed historical one-SPARK lock are recovery-only. That surface may verify and expose checkpoint, claim and matured withdrawal for the recorded position; it must not expose a new V1 lock, permit, approval, extension, Boost or paid placement.
Paid placement is not endorsement. Boost weight proves only a disclosed lock under the disclosed rules; it does not prove identity, quality, safety or future value.
A Spark profile is canonical to a wallet address. Launches and blueprints are attributed only when the contracts report that address. Display names, bios and avatars are offchain annotations owned through a signed-in wallet session.
“X connected” means the OAuth provider confirmed control of a stable X identity during linking. It does not mean KYC, endorsement, contract verification, audit status or trustworthiness.
Current claimable is a live balance that can change. Creator fees, split credits, blueprint royalties, pot awards and claimed totals are different ledgers and must remain separate. “Lifetime earnings” is reserved for a complete indexed ledger with reorg handling and reconciled claims.
Uncollected pool fees and unreadable balances are not earnings. Unknown renders as a dash with a reason, never as zero.
Open the token's launch page, inspect its hook behavior and source addresses, compare the wallet prompt with the quoted action, and use the linked explorer receipt after confirmation. For the exact protocol mechanics, read the Spark docs before trading or launching.