—

Deploy a second site

Installs a complete second SOGGY — three contracts, 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.

Four signatures, no private key. Each contract is its own transaction — that is the chain's rule, not this page's — plus one to fill the stock whitelist. Roughly 14M gas, about 0.0008 ETH at the ~0.03 gwei this chain has been charging. Everything is signed by your wallet; nothing is typed into a terminal.

▶

Deploy everything

Runs all four steps 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.

pending

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.

Domain this stack is for

Protocol treasury — receives 10% of trading fees

Creator wallet — receives the 25% allocation at launch

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)

WETH

Uniswap V3 factory

Position manager

Swap router

RobinhoodLaunchpad

Fair launches paired against WETH. 1B fixed supply · 25% to the creator wallet at launch · 5% across the 224 airdrop wallets · 70% single-sided liquidity locked forever · trading fees 90% creator / 10% treasury. Fixed by the contract, not by this page.

pending

UniswapStockLaunchpad

The same launch, paired against a whitelisted stock token instead of ETH. Identical split and fees; it keeps its own whitelist, filled in step 4.

pending

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.

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, then committed in one signature. If the whitelist is already full, this step sends nothing and spends no gas.

pending

✓

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.