Enable Base mainnet BORO claims #26

Closed

backmeupplz wants to merge 1 commit from bdt-21-boro-mainnet-claims into main

backmeupplz commented

2026-05-25 23:35:34 +00:00

(Migrated from github.com)

Summary

Switch the default claim runtime to Base mainnet BORO env while keeping legacy Base Sepolia testnet mode behind ENABLE_TESTNET_CLAIMS=true.
Generalize the token sender/config labels for chain id 8453, BORO token address, BORO claim sender key, and BORO claim pool raw amount.
Restore the signed Solana holder -> Base recipient claim UI for BORO and update docs/.env examples for production setup.

Validation

bun install --frozen-lockfile
bun run check
bun run test
bun run build
Local BORO config smoke: PORT=43021 NODE_ENV=test ALLOW_IN_MEMORY_CLAIMS=true BASE_MAINNET_RPC_URL=https://mainnet.base.org BASE_MAINNET_BORO_ADDRESS=0x91f11Ad8fa616E95b41C88dFFde95D415F3F9C3c BORO_CLAIM_SENDER_PRIVATE_KEY= BORO_CLAIM_POOL_RAW=900000000000000000000000000 bun --filter @borodutch-tools/backend start; GET /api/claim/config returned enabled=true, chainId=8453, chainName=Base mainnet, tokenSymbol=, missingRuntimeEnv=[].

Deployment / QA handoff

Manual production deployment remains required after review/merge because this environment does not expose Easypanel production claim secrets. Deploy with DATABASE_URL, BASE_MAINNET_RPC_URL, BASE_MAINNET_BORO_ADDRESS, BORO_CLAIM_SENDER_PRIVATE_KEY, BORO_CLAIM_POOL_RAW, and CLAIM_ADMIN_TOKEN; do not include legacy BASE_SEPOLIA_* claim env unless deliberately enabling testnet mode. Verify live /api/claim/config returns enabled=true, chainId=8453, tokenSymbol=, missingRuntimeEnv=[], invalidRuntimeEnv=[], then run a safe canary claim or dry-run/fork simulation.

## Summary - Switch the default claim runtime to Base mainnet BORO env while keeping legacy Base Sepolia testnet mode behind ENABLE_TESTNET_CLAIMS=true. - Generalize the token sender/config labels for chain id 8453, BORO token address, BORO claim sender key, and BORO claim pool raw amount. - Restore the signed Solana holder -> Base recipient claim UI for BORO and update docs/.env examples for production setup. ## Validation - bun install --frozen-lockfile - bun run check - bun run test - bun run build - Local BORO config smoke: PORT=43021 NODE_ENV=test ALLOW_IN_MEMORY_CLAIMS=true BASE_MAINNET_RPC_URL=https://mainnet.base.org BASE_MAINNET_BORO_ADDRESS=0x91f11Ad8fa616E95b41C88dFFde95D415F3F9C3c BORO_CLAIM_SENDER_PRIVATE_KEY=<dummy> BORO_CLAIM_POOL_RAW=900000000000000000000000000 bun --filter @borodutch-tools/backend start; GET /api/claim/config returned enabled=true, chainId=8453, chainName=Base mainnet, tokenSymbol=, missingRuntimeEnv=[]. ## Deployment / QA handoff Manual production deployment remains required after review/merge because this environment does not expose Easypanel production claim secrets. Deploy with DATABASE_URL, BASE_MAINNET_RPC_URL, BASE_MAINNET_BORO_ADDRESS, BORO_CLAIM_SENDER_PRIVATE_KEY, BORO_CLAIM_POOL_RAW, and CLAIM_ADMIN_TOKEN; do not include legacy BASE_SEPOLIA_* claim env unless deliberately enabling testnet mode. Verify live /api/claim/config returns enabled=true, chainId=8453, tokenSymbol=, missingRuntimeEnv=[], invalidRuntimeEnv=[], then run a safe canary claim or dry-run/fork simulation.