How Spark works

Release manifest gate

One versioned manifest supplies every read address and every browser-write and agent release gate. Opening writes requires a deployment newer than the read-only slots already on chain, four nonzero address/runtime-hash pairs, the bounded Spark router, a reviewed source commit, and one block shared by the fork and linkage readback.

The ordered deployment evidence is launchpad, hook, router, setHook, then all five blueprint receipts. The canary evidence is an intent-bound instant pool launch, bounded-router buy, token approval, then bounded-router sell. Every receipt is required; a production boolean alone cannot open writes.

No machine blockers: every gate condition above is satisfied by the checked-in manifest.

$SPARK Lock Rewards and paid Launch Boost

Current state: V2 release candidate; V2 reads and writes closed. No complete schema-3 V2 manifest is checked in, so V2 reads and wallet writes remain closed. Candidate source, local tests, simulations and candidate addresses are not deployment or receipt evidence. The V2 utility rail has a separate release gate from the launchpad and cannot borrow the core deployment's status.

Separately, V1 is a deployed, superseded recovery-only contract with one historical one-SPARK lock position. Spark may verify that position for checkpoint, claim and matured withdrawal only. It offers no new V1 lock, permit, approval, extension, Boost or paid-placement write.

Lock Rewards. Any wallet can lock $SPARK with no deposit fee. The three disclosed terms are 30 days at 1.00×, 90 days at 1.15×, 180 days at 1.25×. Principal is non-transferable while locked, never slashed and fully refundable after unlock. A position activates in the next immutable V2 epoch and earns only across complete epochs. Epoch 0 is a two-hour lock-only window from deployment; epoch 1 is a two-hour fees-and-Boost window; epoch 2 bridges to the first Monday 00:00 UTC strictly after epoch 1 ends; later epochs are Monday-to-Monday weeks. Rewards consist solely of realized Launch Boost fees and may be zero; there is no APY.

Launch Boost. Only the creator recorded by the supported launchpad can fund a launch's position. Its paid-rail score is net refundable principal × the same capped term multiplier. V2 Boost hard-reverts throughout the initial lock-only epoch and opens at the fee epoch exactly two hours after deployment. When an already-eligible locker cohort exists, a ceiling-rounded 1% of the gross deposit is routed to that cohort; when none exists, the fee is waived rather than saved for future lockers. Longer or additional locks recommit the resulting position under the contract's disclosed term rules.

Boosted is a separate, visibly paid and capital-weighted rail. It never changes organic Discover order and is not endorsement, identity verification, vetting or a safety signal. After the one-time reward-source wiring, the utility contracts have no ongoing owner, slashing, pause, upgrade or sweep path.

Machine gate: utility deployment evidence is not published. Read the ranking methodology, terms and public-position privacy notice before considering a lock.

1 · Choose a launch path

Every path mints a fixed supply of 1,000,000,000 tokens with no owner, mint function, pause, blacklist or transfer tax. The creator receives no token allocation. What changes is how the first market and its opening price are formed.

Instant pool. The creator commits ETH and chooses 20–100% of supply as the tradeable float. Those two inputs imply the opening price and an opening FDV between 1× and 5× the committed ETH. The Uniswap v4 pool opens with locked, launchpad-owned liquidity in that same transaction. There is no curve phase and no private window: anyone can swap as soon as the launch transaction lands, so the configured anti-snipe guard is the launch-specific cap and tax while AMM reserves determine execution prices. ETH accepted into the position cannot be withdrawn; any sub-ppm rounding residue is refunded by the launch transaction.

Bonding curve. 80% of supply sells across ten tranches, each priced 70% above the previous one. Buys and sells work while the curve is live, and each pays a 1% curve fee split evenly between creator and protocol. The pool opens only after the last tranche sells out.

Active release capability: instant pool and bonding curve. The launcher also verifies the instant preview against the deployed launchpad before it enables signing.

2 · Curve graduation

When the last tranche sells out the launch graduates in the same transaction. The ETH raised and the remaining 20% of supply become a full-range Uniswap v4 position at exactly the price the curve ended on, with the creator's hook attached and a dynamic fee. The position is owned by the launchpad contract, which has no function to remove liquidity — the liquidity is locked by construction, not by promise. Any supply that did not fit the position is burned by default, or placed as token-only bands if the creator configured them; see section 3. Trading fees earned by these positions can be collected by anyone; the ETH side splits between creator and protocol and the token side is burned.

3 · Creator fees and liquidity placement

These are set per launch, not on a hook. A hook blueprint is reusable by anyone, so it can only carry rules that hold for every launch; payout addresses and how a raise is placed belong to one launch.

Fees. While a token is on the curve, its 1% curve fee is a fixed even split between creator and protocol; an instant launch has no curve fee because there is no curve. Once either path has a pool, the locked position earns trading fees that anyone can collect. The ETH side splits by a share the creator chose at launch — 50% by default, 80% at most — and the token side is burned. Only that pool-fee share can be divided, across up to four addresses, each credited on chain so a recipient can claim without depending on the creator.

Liquidity. By default the entire raise becomes one full-range position and any supply that did not fit is burned. A creator can instead place up to four bands at chosen price multiples above the graduation price. Bands hold tokens only — they can never draw ETH — so they act as scheduled sell-side depth rather than a second market. A band that would not fit the tick grid is skipped rather than silently shifted, and fee collection pokes every band that was actually created.

4 · The five hook blocks

• Anti-Snipe — for a set number of blocks after the pool opens, buys are capped and pay an extra LP fee. The cap is based on the chosen pool float for an instant launch and the curve allocation after graduation. Exact-output buys are blocked during the window so the cap cannot be routed around.
• Surge Fees— the LP fee scales with how much of the pool's in-range depth a trade consumes, from your base fee up to your ceiling. No oracle involved.
• Auto Burn — a configured share of actual exact-input buy token output goes directly to the dead address. There is no ETH vault, keeper or separate market buy.
• LP Rewards — an ETH-side share of an exact-input buy is donated to in-range liquidity providers inside that swap.
• Nth-buy Pot — an ETH-side share fills a deterministic pot. A public counter advances at most once per pool per block, and the Nth qualifying slot wins. A minimum buy applies. Qualifying swaps must canonically bind a nonzero recipient, the production router supplies that binding automatically, and claimants can redirect payout. A funded pot remains claim-backed for the next scheduled winner; there is no permissionless flush.

Reading the market figures

The volume, trade and change figures on Discover and the token pages are computed from raw chain logs at the moment you load them — Spark runs no indexer and keeps no history. Knowing exactly what each number measures is the point of this section.

• The window is real time, not block count. “24h” is found by bisecting block-header timestamps — no block rate is assumed. The label states what the window actually covered of the launchpad's history: while that history is shorter than the requested span, the label shrinks to match (“3h”). A token younger than the window keeps the full label — its whole life sits inside the window, so its window figures are simply its lifetime figures.
• Volume counts the ETH leg of every trade in the window. On a bonding token that is the launchpad's own CurveBuy/CurveSellrecord. On a graduated token it is the pool leg of each v4 swap — measured after the hook's buy-side cut is taken, so the trader-side total runs slightly higher. Both surfaces sum both venues for a token that graduated mid-window — it traded on the curve that same day, and a pool-only figure would shrink its day.
• Change compares real trades, not candles.The close is the last trade in the window; the open is the newest trade before it, or the pool's graduation price when the whole record shows no earlier trade. A pool with no trades in the window shows no change at all — “0.00%” would assert a market held a price that nobody actually traded.
• A dash is an answer.Every “—” carries its reason in the tooltip: no trades in the window, a chain read that failed, a window that could not be resolved. Nothing is estimated in its place, ever.

What Spark does not claim

• Nothing here is independently audited. The contracts are deployed and were exercised end to end by a canary launch before writes opened. Tests, readable source, and canary receipts are release evidence — they are not an audit, and no third party has reviewed this code.
• The Nth-buy Pot is not random. The public potBuyCountdetermines the next slot, so expect it to be raced. The one-advance-per-block rule stops a single atomic call from manufacturing every remaining slot; it does not make the outcome fair or private.
• No fairness, anti-bot or anti-MEV guarantee. The anti-snipe block caps per-swap size for a window; it does not identify people and cannot stop someone using many wallets.
• Hook fee cuts apply to exact-input buys only.Sells and exact-output buys pay only the LP fee. Auto Burn is an output-token share; LP/pot shares are ETH-side. The guard's size cap and snipe tax are buy-side too.
• Routing is release-pinned. Graduated trades route only through the bounded Spark router pinned in the release manifest by address and runtime hash; it enforces minimum output, deadline, and recipient on-chain.
• Rules are immutable after graduation. A hook cannot be edited or replaced on a live pool. Changing rules means launching a new token.

Current live contracts · Robinhood Chain 4663