Deploy Circulate on Netlify
The package contains the Next.js website, Netlify Functions, metadata upload service, scheduled keeper dispatcher, database migrations, and Solana program source required by the full Circulate architecture.
Mainnet website release
- Create the Netlify site.Connect the repository or upload the package, then allow Netlify to use the included build configuration.
- Add mainnet RPC values.Set the protected server RPC, browser-safe RPC,
mainnet-betacluster, and expected genesis hash. - Configure metadata storage.Add a server-only Pinata JWT with permission to upload the token image and JSON metadata.
- Review the Pump.fun origin.Keep the transaction builder restricted to the approved Pump.fun host.
- Trigger a fresh deployment.Environment changes reach Functions only after a new production build.
- Run a small canary launch.Confirm the wallet is shown as user, fee payer, and creator, then verify the mint and transaction on-chain.
No private launcher key on Netlify
The launcher signs through their browser wallet. Do not upload a launcher seed phrase, mint seed phrase, or personal wallet private key to the deployment.
Reward infrastructure
- Apply the Postgres migrations in numerical order.
- Deploy the exact Reward Router program build and record its mainnet address.
- Configure the program, database, Jupiter, and keeper variables.
- Fund the keeper with enough SOL for expected transaction volume.
- Verify project initialization, fee collection, swap, snapshot, commitment, and payout on a controlled canary.
- Enable monitoring for scheduler delay, transaction failure, vault drift, and incomplete rounds.
Release checklist
| Check | Expected result |
|---|---|
| Health endpoint | Mainnet cluster and required service checks succeed |
| Metadata upload | Image and JSON resolve from their returned IPFS URIs |
| Wallet transaction | Only the expected launcher approval is requested |
| Pump.fun page | Mint, creator, name, ticker, and metadata match the launch form |
| Solana confirmation | Transaction confirms without a program error |
| Monitoring | RPC, metadata, launch, keeper, and database failures produce actionable alerts |