SOGGY DEV

Deploy a launchpad

Installs a fresh SOGGY launch stack on Robinhood Chain from your own wallet. Every launch made through it pays its protocol fee to the treasury you set below, and the addresses are yours alone — nothing here touches the launchpad the live site already uses.

Fixed by the contracts, not by this page: 1B supply · 25% to the creator wallet at launch · 5% split across 224 airdrop wallets · 70% single-sided liquidity locked forever · trading fees split 90% creator / 10% protocol. A full stack — ten launchpads, the router and every whitelist — is roughly 50M gas, about 0.0015 ETH at the ~0.03 gwei this chain has been charging.

Deploy everything

Runs every step below back to back. Your wallet asks for each signature in turn — approve them as they come. Steps that are already done are skipped, so this is safe to press after a partial run.

pending

Connect your wallet first. Everything below fills itself in as it goes.

0

Settings

Chain infrastructure is prefilled and verified on chain. The two wallets are yours to choose.

Both default to your connected wallet. The creator wallet is written into every token created by this launchpad and cannot be changed for tokens that already exist — only for future ones. There is no vesting: the 25% arrives the moment a token launches.

Chain infrastructure (advanced — leave alone unless you know why)

UniswapAtomicStockRouter

ETH ⇄ stock-paired token in one signature. It stores one stock launchpad as an immutable, so it is wired to the first one above and has to come after it. The main app does not use it — stock trading goes through SwapRouter02 — so one router covers the whole family.

pending

Whitelist the stocks

A stock launchpad accepts nothing until each share is whitelisted with an opening reference price. Prices are read live from the chain's own pools — once, since they are the same for every launchpad — then committed with one signature per launchpad. The whitelist is per-contract: a stock allowed on one is unknown to the other four. Launchpads that are already filled are skipped without spending gas.

pending

Deployment record

Download the finished deployment.js and drop it into site/launchpad/, replacing the file that is there. Nothing to paste by hand.

Deploy step 1 to begin…
Go to Create token →