Human/operator checklist before the first public/shared Base Sepolia deployment.
This file should contain only items that need human custody, external accounts, funds, dashboard access, or product judgment. LLM-executable deployment steps belong in workflow/deployment.md.
- Run
node scripts/generate-wallets.mjs; save the printed secret block in your password manager. - Fund only
DEPLOYER_ADDRESSindeployments/operator-addresses.envwith Base Sepolia ETH from a faucet. The Coinbase Developer Platform faucet's0.1 ETHdaily allowance should be plenty for testnet deployment plus many transactions. (See https://docs.base.org/base-chain/network-information/network-faucets for faucets.) (I ended up using Alchemy's faucet.)
Create/get credentials and put them in .env.secrets:
- GitHub repo connected/pushed for Render Blueprint deploys.
- Render account ready.
- RPC provider URLs, especially
BASE_SEPOLIA_RPC_URLand preferablyMAINNET_RPC_URL. -
ENS_OWNER_PRIVATE_KEY(should be the private key forcommonality.eth; confirm that it has enough mainnet ETH for ~9 ENS transactions: one to createtestnet.commonality.ethplus sub-subdomains, then one per UI subdomain to set contenthashes) -
OPENROUTER_API_KEY. -
VITE_WALLETCONNECT_PROJECT_ID. -
PINATA_JWT. -
X_API_BEARER_TOKENfor the US-politics beat-agent rehearsal. - Privy app (embedded-wallet provider, ratified). Create a dev app and put
VITE_PRIVY_APP_ID(and optionallyVITE_PRIVY_CLIENT_ID) in theuienv. Unblocks the whole embedded-wallet cluster in TODO.md (contribution sequencing, the Privy+Pimlico spike, sponsored gas, refund verification). Step-by-step: workflow/privy-pimlico-setup.md. - Pimlico API key (EIP-4337 bundler + paymaster infra, ratified). Create an account, get an API key, and put the bundler/paymaster URLs in
.env.secrets. Same guide: workflow/privy-pimlico-setup.md. - Coinbase Onramp (CDP) Secret API key — mints the fiat→USDC on-ramp session for the walletless donor flow. This is the same Secret API key already created for the
spikes/coinbase-onramp/harness; reuse it (no new key needed) by copying it into.env.secretsasCOINBASE_CDP_API_KEY_ID/COINBASE_CDP_API_KEY_SECRET, plus a Base mainnetBASE_RPC_URL. Guide: workflow/privy-pimlico-setup.md.
- Go to the Render dashboard and create a new Blueprint deployment, pointing it at your GitHub repo
- Copy required
sync: falsevalues into Render. (Run node scripts/generate-render-secrets.mjs to generate the .env blocks.) - Put
commonality.workson Cloudflare DNS, or otherwise make Cloudflare able to serve Worker routes for the zone. Friend/operator instructions: workflow/commonality-works-setup.md. - Deploy the Cloudflare service gateway from cloudflare-service-gateway/ and verify
https://services.testnet.commonality.works/*routes. - Configure DNSLink UI records for
commonality.worksusing Cloudflare automation, workflow/commonality-works-setup.md, or the transitional workflow/hostinger-dns-setup.md instructions if DNS is still on Hostinger.
Once these are done, ask an LLM to follow the testnet procedure in workflow/deployment.md.