Deploy

Scripts, environment, and the traps already found.

Scripts

$env:OWNER = "0x…"; $env:TREASURY = "0x…"
forge script script/DeployLaunchpad.s.sol --rpc-url https://rpc.mainnet.chain.robinhood.com --account deployer --sender 0x… --broadcast

$env:LAUNCHPAD = "0x…"; $env:STAR = "0x…"; $env:NAME = "unipcs"; $env:SYMBOL = "UNIPCS"; $env:BUY = "3000000000000000"
forge script script/LaunchToken.s.sol --rpc-url https://rpc.mainnet.chain.robinhood.com --account deployer --sender 0x… --broadcast

Every script reads the result back from the chain and prints that, never the receipt: broadcast receipts on this chain have mislabelled addresses before. Keys never leave the operator's machine; --account uses the local keystore and the password is typed in the terminal.

Pointing the front end

The mainnet launchpad address is baked into web/src/lib/config.ts; NEXT_PUBLIC_LAUNCHPAD overrides it. A push to main deploys on Vercel.

Traps

• forge script on this chain needs --sender next to --account, or it simulates with the default sender and refuses to broadcast.
• PowerShell: $env:X = "…" and ;, never X=… cmd or &&.
• Vercel variables created as "Sensitive" are not injected into the Next build; do not rely on them for NEXT_PUBLIC_* values.
• The RPC and the explorer return 403 to non-browser User-Agents from scripts.