allocated to the token launch curve
permanent liquidity for the ecosystem
Every launch sells 16,800,000 tokens along P(s) = p₀ + k·s², opening at 0.1702 sat per token and calibrated so the curve raises exactly 0.1 BTC at graduation. Nothing below is hand-drawn: the chart, the numbers and the slider all run the same equation, and USD values use the live BTC price.
Funds sit in a Taproot (P2TR) output that only moves when the user key and the protocol key sign together. No custodian, no admin override, no single point of failure.
Swaps, launches, fee claims and vault returns each require a fresh wallet signature over a deterministic payload: action, owner, exact amounts, slippage bounds, timestamp, and a single-use 256-bit nonce. Build one below, your browser generates a real nonce with crypto.getRandomValues and hashes the payload with real SHA-256.
When a curve raises 0.1 BTC it closes automatically and becomes a bonded AMM pool: the raised Bitcoin plus the reserved 4,200,000 tokens seed it, and LP ownership is provably burned. No owner key, no admin withdrawal, no unlock schedule.
The seeded pool starts at 10,000,000 sats × 4,200,000 tokens. Type a buy and the constant-product math below computes your fill and the price impact, the same arithmetic the pool settles with.
On public mempools, bots read pending orders and sandwich them. On satcap, swaps settle on an internal pipeline: strict arrival order, enforced slippage floors, atomic reverts with zero fee. Feed the queue below, the engine runs the real constant-product fills in order and rejects anything that breaks its signed bounds.
queue is empty. Orders will process strictly in the order you add them: each fill moves the pool, so a tight floor set before a big order ahead of you can honestly revert.
Charts, holder tables and feeds query database views guarded by PostgreSQL Row-Level Security. Stealth addresses render masked, raw wallets and balances never reach public APIs or WebSocket feeds, and only the verified owner sees their own history through an authenticated session.
Block explorers make strategy tracing trivial. Stealth Mode cuts the link at the database view, so the public tape stays public and your book stays yours.