Legacy deployments

This page records the retired NFT product and its historical deployment procedures. It does not deploy the new topup contract. Use Deployment for current instructions.

Mainnet is not deployed. This page preserves the earlier testnet rehearsal and proposed mainnet preconditions. Legacy testnet minting was paused at block 140880178 on 5 November 2026; reward claims remain unpaused. Use Addresses for the pause transaction and active payment deployment.

Historical mainnet preconditions

Do not deploy to mainnet until all of these are true:

• Treasury is a Safe 3/5.
• Admin and upgrader are a Safe 3/5.
• Keeper is a separate EOA with limited funds.
• External audit is complete.
• All critical and high findings are fixed and retested.
• four.meme recipient contract and founder fee flow are verified.
• The 100M airdrop allocation is final.
• Monitoring and incident response are active.
• Legal review is complete.

Historical testnet rehearsal

1. Deploy mock USDT, mock oracle, and mock registry.
2. Deploy PassRenderer, AgentPassSingle, and RewardDistributor. Initialize both the inherited pass state and membership version 2 before opening mint.
3. Set the distributor on the pass.
4. Grant KEEPER_ROLE to the keeper and TaxSplitter.
5. Start mint.
6. Set Agent ID handles.
7. Mint twice from the same wallet using BNB and USDT. Verify $5 per mint and aggregate weight.
8. Deposit USDT rewards.
9. Build the airdrop tree and deploy AirdropVesting.
10. Fund the vesting contract.
11. Start the indexer and web app.
12. Test mint, claim, chat, and admin actions.

Completed membership upgrade

On 3 November 2026, the existing chain-97 proxy was upgraded to AgentPassSingle at block 140541776. The original NFT #1 retained its owner, edition 0, 10,000 weight, stored handle, and reward balance. Minting returned to its previous unpaused state.

Both mints used the original holder's wallet. It held NFTs #1, #2, and #3 with aggregate weight 30,000 after the checks. The USDT mint charged 5 mock USDT; the BNB mint charged 8416666666666666 wei at the configured mock oracle price, including the 1% buffer.

The application migration completed at 2026-11-03T08:29:20.224Z after an application-schema backup. It preserved the existing $1.50 grant and five usage records totaling $0.000142. Confirmed-pass synchronization then granted $5 for each new NFT. The verified balance was $11.499858 from $11.50 granted. Repeated synchronization did not duplicate grants.

The contract suite passed 243 tests, and storage validation passed for the upgrade. A local fork rehearsal also verified preservation before the live testnet transaction. These checks do not replace an independent audit. Deployment records are in packages/contracts/deployments/; the new addresses are on Addresses.

Historical mainnet deployment outline

1. Create the treasury Safe and admin Safe.
2. Deploy PassRenderer.
3. Deploy the AgentPassSingle implementation and proxy, then initialize membership.
4. Deploy the RewardDistributor implementation and proxy.
5. Set the distributor on the pass.
6. Deploy TaxSplitter after the token exists.
7. Deploy AirdropVesting after the snapshot.
8. Grant roles to the Safe and keeper.
9. Renounce deployer roles.
10. Verify the contracts on BscScan.
11. Start mint.
12. Publish the addresses.

Role handover

The deploy script grants roles to the admin and keeper, then renounces the deployer roles when the addresses differ.

Check the case-insensitive comparison. A checksummed address and a lowercase address are the same account.

After deployment, verify:

Verification

• Verify the proxy and implementation on BscScan.
• Verify the renderer.
• Verify the distributor, splitter, and vesting contracts.
• Confirm the proxy points to the expected implementation.
• Confirm the distributor points to the pass.
• Confirm the pass points to the distributor and renderer.
• Confirm the tax splitter points to the distributor and router.

Post-deploy checks

• mintOpen() == true
• totalMinted() == 0
• soldOut() == false
• rewardDistributor() is set
• oracle() is the Chainlink feed
• usdt() is BSC USDT
• agentIdRegistry() is the Agent ID registry
• RewardDistributor.solvent() == true
• AirdropVesting.start() is in the future

Upgrade process

For the existing testnet proxy, use packages/contracts/scripts/upgrade-membership.ts. It validates storage, pauses minting, snapshots existing NFTs and holder rewards, deploys the implementation and renderer, calls upgradeToAndCall with initializeMembership, verifies preservation, and restores the previous pause state. It records the transaction in packages/contracts/deployments/.

Stop chat traffic and let in-flight requests finish before applying apps/web/migrations/002-single-membership.sql. Back up the application schema first. Fresh databases need apps/web/supabase.sql before this migration. The migration is replay-safe and preserves existing credit grants and usage. Deploy the matching app build after the database and proxy are ready. The indexer retains its existing proxy address and PassMinted event signature.

The testnet command, run from packages/contracts, is:

The general mainnet process remains:

1. Deploy the new implementation.
2. Validate the storage layout.
3. Propose upgradeToAndCall through the admin Safe.
4. Collect 3 of 5 signatures.
5. Execute.
6. Verify the new implementation and a smoke test.

There is no timelock. Treat every upgrade as a high-risk operation.

Inference API migration

After the membership migration, apply apps/web/migrations/003-inference-api.sql before deploying the inference app build. Back up the app schema first. The migration adds API keys, key audit events, and a nullable api_key_id on requests. It does not rewrite grants or usage and is replay-safe. Fresh databases apply supabase.sql, 002-single-membership.sql, and 003-inference-api.sql in that order.

Use the existing server-only OPENROUTER_API_KEY, OPENROUTER_BASE_URL, DATABASE_URL, SESSION_SECRET, and ADMIN_WALLETS configuration. Configure the host to allow at least 120 seconds for the completions route and disable proxy buffering for SSE. The provider deadline is 90 seconds. Apply infrastructure limits to unauthenticated traffic; application limits apply to admitted inference requests. Smoke-test key creation, models, a completion, streaming, usage settlement, and revocation using the steps in API.

Emergency

• Pause AgentPass to stop minting.
• Pause RewardDistributor to stop deposits and claims.
• Pause TaxSplitter to stop tax distribution.
• Do not pause the airdrop. It has no pause.
• Publish an incident note after the immediate risk is contained.

Testnet addresses

See Addresses.