Eclipse

Whitepaper

Eclipse

A bonding-curve launchpad on Robinhood Chain, designed so that "the team can't rug you" is a fact about the contract, not a promise from the team.

Abstract

Most token launchpads ask holders to trust that a team won't drain the liquidity pool, mint more supply, or quietly walk away. Eclipse removes that trust requirement for the failure mode that matters most: every token launched through Eclipse graduates into a liquidity position that is permanently burned — sent to an address no private key controls — the moment it graduates. Nobody, including Eclipse, can pull it afterward. This document describes how that works end to end: the bonding curve that prices a token before it has any liquidity, the fee and anti-snipe mechanics that apply while it's bonding, and the graduation step that locks liquidity for good.

1. The problem

A "rug pull" on a bonding-curve launchpad usually takes one of a few shapes: the deployer holds a large share of supply and dumps it, the liquidity pool created at graduation is owned by a wallet that can withdraw it, or the contract has an admin function that can mint more tokens or redirect funds after launch. Each of these is a trust problem, not a liquidity problem — the mechanism works fine right up until someone with privileged access decides to use it.

2. The approach

Eclipse doesn't ask for trust on this point — it removes the privileged access. The contracts it uses (reused from infrastructure already live on Robinhood Chain, not deployed fresh by Eclipse) have no function that lets anyone withdraw a graduated curve's liquidity, because by the time a curve graduates, that liquidity has already been transferred to a burn address with no owner. The guarantee is structural: it holds regardless of what the Eclipse website does, because it's enforced by the chain, not by Eclipse.

3. Mechanics: the bonding curve

Each launch deploys its own constant-product curve, tokenReserve · quoteReserve = k, seeded with a small phantom quote reserve so the first trade already has a real, non-zero price instead of starting at zero. As buyers trade in, the real quote reserve grows and the token reserve shrinks along the curve, pushing the spot price up monotonically — there's no separate "presale" price distinct from what the curve itself produces.

An ETH-paired launch fixes these constants at the contract level: 1,000,000,000 total supply (800,000,000 sellable on the curve, 200,000,000 reserved for the liquidity position minted at graduation), a 1.05 ETH phantom reserve, and a 4.2 ETH graduation threshold. A stock-quote-paired launch — trading against a tokenized-stock ERC-20 instead of ETH — uses the same formula with a threshold and phantom reserve sized per quote asset at registration time, keeping each asset's implied graduation value in a comparable range to the others already listed.

4. Mechanics: fees and the snipe-tax schedule

A flat 1% fee applies to every buy and sell, on top of which every buy in the first 5 seconds after a token's launch carries a flat 99% extra tax, dropping straight to 0% once that window closes. This exists because a bonding curve without it is trivially snipeable: a bot watching the mempool could buy the entire early, cheap portion of the curve in the same block the token launches, before any human has a chance to. The flat tax makes that unprofitable without blocking genuine early buyers who arrive moments later. A creator may optionally make one exempt "first buy" at the instant of launch — their own stake, at the honest starting price, before the public window opens. Stock-quote launches additionally support an optional 0–5% creator tax, paid to a wallet the creator chooses, on every subsequent trade.

This is a deliberate change from an earlier, now-legacy version of the curve, which instead decayed the tax per second (99% → 24.75% → 3.09% → 0.39% → 0.05% → 0%) rather than holding it flat for the whole window. Neither curve contract has an upgrade path — each deploys its bonding-curve child contract directly from its own bytecode on every launch — so this change only applies going forward, through a new factory deployment (see "Contracts" below); every token already launched through a legacy factory keeps its own already-deployed curve, decaying schedule and all, permanently.

5. Mechanics: graduation

A curve tracks its own state — CREATED → BONDING → GRADUATING → GRADUATED — and once the real quote reserve raised crosses the graduation threshold, the graduation contract mints a Uniswap v4 liquidity position from the accumulated reserves and transfers that position's NFT to a dead address. From that point, the token trades on that Uniswap position like any other graduated pair, and the bonding-curve contract no longer mediates trades for it.

6. Architecture

Eclipse is a static frontend with no backend and no database. It reads chain state directly over RPC (batched through a Multicall3 contract so a page full of tokens costs one round trip, not one per token), discovers every launch by scanning each factory's own TokenLaunched event log, and renders what the chain actually says — there is no cached or Eclipse-controlled copy of any balance, price, or graduation status to drift from the truth on-chain. The one piece of state that is Eclipse's own is cosmetic: an optional token description, stored only in the visiting browser's local storage, never shared or synced anywhere.

7. Two ways to launch

Robinhood Chain's own distinguishing feature is tokenized, on-chain exposure to real-world stocks. Eclipse's stock-quote-paired path leans into that: a launch priced in a registered stock token (NVDA, AAPL, and 30+ others) rather than ETH. An ETH-paired path exists alongside it for creators who'd rather skip the quote-asset approval step and the stock-pairing tradeoffs — simpler, at the cost of the creator-tax, social-link, and first-buy features that only the stock-quote factory supports.

8. Risk disclosures

  • Price volatility. A bonding-curve price moves entirely with buy/sell pressure — there's no floor, and an early or late position can lose most or all of its value before (or instead of) reaching graduation.
  • Graduation is not a quality signal. Crossing the threshold only confirms that much quote-asset volume has traded through the curve; it says nothing about the token, the creator, or whether trading continues afterward.
  • Stock-quote threshold drift. An ETH-paired curve's 4.2 ETH threshold floats in USD terms as ETH's own price moves. A stock-quote curve's threshold is instead a fixed number of that stock's own tokens, set once at registration — it does NOT automatically track that stock's price afterward, so its implied USD value can drift out of step with ETH's over time. Eclipse has a read-only reporting script (not run automatically) to compare the two and suggest a re-registration when they drift too far apart; applying any such change is a separate, owner-signed step, same as deploying a new factory.
  • Contract and infrastructure risk. The factory, curve, and graduation contracts are shared infrastructure Eclipse did not write and has not independently audited (see "Security status" below). RPC node issues can also delay how current the numbers on this site are, even though they're always a live read, never a cached copy.
  • No recourse. Every trade and launch is signed directly by your own wallet against the contract. Nobody — including Eclipse — can reverse a transaction, recover funds sent in error, or stop a token's creator from being anonymous or disappearing after launch.

9. Contracts and network

Verify any of these directly on the block explorer rather than trusting this page — the whole point of the design above is that you shouldn't have to trust Eclipse on anything that's checkable on-chain.

Current — what /create launches through today

Legacy — frozen, pre-2026-10-03 curves (see section 4)

Shared by every generation above

Network

10. Security status

The factory, curve, and graduation contracts Eclipse calls are shared infrastructure already deployed and trading on Robinhood Chain before Eclipse existed — Eclipse did not write or deploy them, and has not commissioned an independent audit of them itself. Treat them, and this product, as experimental. Eclipse does not custody funds at any point: every trade and every launch is signed directly by your own wallet against the contract, never routed through an Eclipse-held account.

11. Disclaimer

This document describes how the product works; it is not investment advice, a prospectus, or a solicitation to buy anything. Tokens launched through Eclipse — including by Eclipse itself, if it ever does — carry full risk of loss. See Terms and Privacy for the legal detail, and Docs for the practical walkthrough of using the product.