SOGGY Deploy a second site
Installs a complete second SOGGY — five contracts (two launchpad names per pair, plus the router), owned by the wallet you connect here, for a domain like dev2.soggylaunch.fun. Same code, same look, same rules as this site; different contracts, different owner, different treasury. Nothing on this page touches the launchpads the live site already runs on.
Deploy everything
Runs every step back to back. Your wallet asks for each signature in turn. Steps already done are skipped, so this is safe to press after a partial run.
Connect the second site's wallet first. Everything below fills itself in as it goes.
Settings
Chain infrastructure is prefilled and verified on chain — it belongs to the chain, so both sites share it. The domain and the two wallets are yours to choose.
Both default to your connected wallet. They are written into every token this launchpad creates 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)
UniswapRouter
This is a launchpad, not a router. The name is a label the owner chose; the actual swap router is step 3. Tell them apart by address, not by name.
Fair launches paired against WETH. 1B fixed supply · 25% to the creator wallet at launch · 5% split evenly across this site's own 100-wallet airdrop list · 70% single-sided liquidity locked forever · 0.3% pool fee, split 90% creator / 10% treasury. The list is this site's own — not the 224 wallets the first site pays — and both lists are written into their contracts, not into this page.
RobinhoodStockPad
The same launch, paired against a whitelisted stock token instead of ETH. Identical split and fees — 25/5/70, same airdrop list; it keeps its own whitelist, filled in step 4.
UniswapAtomicStockRouter
ETH ⇄ stock-paired token in one signature. It stores the stock launchpad as an immutable, so it is wired to the one deployed in step 2 and has to come after it. The main app trades stocks through SwapRouter02 and does not need this — it is here so the stack is complete.
HoodMarket Uniswap v4
Optional. The ETH venue on Uniswap v4 instead of v3 — same terms as the rest of this stack (25% to the creator at launch, 5% to the same airdrop list, 70% locked, 0.3% pool fee), but the pool lives in the v4 singleton and is identified by a PoolId rather than an address. Nothing above depends on it: skip this and the site is still complete, just without a v4 board.
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, then committed in one signature. If the whitelist is already full, this step sends nothing and spends no gas.
Deployment record
The addresses, as the chain reported them. Download the file and hand it to the tool — nothing is copied by hand, which is where digits get dropped.
Deploy step 1 to begin…
Then, from the repo root:
Show the file, in case the download is blocked
That writes this domain's block into site/launchpad/sites.js. Deploy with cd site && vercel --prod, then point the domain at that deployment with vercel alias set. Until the block exists, the domain would quietly load the first site's contracts — so do not alias it before this step.
Telegram alerts
These two contracts emit the same CoinCreated events as the first site's, so the bot reads them with the adapters it already has — no new code. Add these entries to data/launchpads.json, then git push vps main and update.sh. Every token launched on this domain then alerts exactly like the first site's do.
The bot dedupes by address and reads each pool's fee tier from the chain, so these can be appended to the existing list as they are. After adding them, restart the service or the new launchpads are configured but unwatched.