fix(circle): scope mainnet Circle to Base only (hold back Arbitrum)#18
Merged
Conversation
…ts gate) NEXT_PUBLIC_ENABLE_CIRCLE_PAYMASTER is a global flag: enabling it activates Circle on every chain present in both CIRCLE_PAYMASTER_ADDRESSES and CIRCLE_GAS_SURCHARGE_BPS. Arbitrum mainnet (42161) was in the surcharge config but only Base mainnet passed the real-device gate (2026-05-30). To keep the first production rollout Base-only (per the staged-rollout runbook), comment out [arbitrum.id] from CIRCLE_GAS_SURCHARGE_BPS so Arbitrum mainnet stays on Pimlico erc20 fallback even with the flag on. Its allowlist address and the Arb/Base testnet surcharge entries are unchanged. Re-enable by passing SMOKE_CHAIN=arbitrum gate then restoring the commented line. Tests + runbook §段階リリース updated to match. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
NEXT_PUBLIC_ENABLE_CIRCLE_PAYMASTERis a global flag.resolveUsdcGaslessProviderreturns'circle'for any chain present in bothCIRCLE_PAYMASTER_ADDRESSESandCIRCLE_GAS_SURCHARGE_BPS. Arbitrum mainnet (42161) was in the surcharge config, so flipping the flag for the Base rollout would have also activated Circle on Arbitrum mainnet — which has not passed the real-device gate (only Base did, 2026-05-30; Arbitrum only on testnet/Arb Sepolia).What
[arbitrum.id]: 1000inCIRCLE_GAS_SURCHARGE_BPSso the global flag activates Base mainnet only; Arbitrum mainnet stays on Pimlico erc20 fallback. Its allowlist address + Arb/Base testnet surcharge entries are unchanged.SMOKE_CHAIN=arbitrumgate → restore the commented line.Test
This makes step B (
NEXT_PUBLIC_ENABLE_CIRCLE_PAYMASTER=1in prod) genuinely Base-only, matching the staged-rollout plan.🤖 Generated with Claude Code