fix(fee-abstraction): correct the Celo Sepolia USDC token and adapter addresses - #2273
Open
GigaHierz wants to merge 1 commit into
Open
fix(fee-abstraction): correct the Celo Sepolia USDC token and adapter addresses#2273GigaHierz wants to merge 1 commit into
GigaHierz wants to merge 1 commit into
Conversation
… addresses Both cells of the Sepolia USDC row on the AI overview and the fee-abstraction guide held the mainnet USDC adapter (as token) and an address with no code on Sepolia (as adapter). Replaced with the pair registered in the Celo Sepolia FeeCurrencyDirectory: token 0x01C5C0122039549AD1493B8220cABEdD739BC44E (USDC, 6 decimals), adapter 0xbf1441Ea57f43f35f713431001f35742c88071c7. Closes #2268 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
The hole, and the fix
The Celo Sepolia USDC row on two guide pages was wrong in both columns:
0x2F25deB3848C207fc8E0c34035B3Ba7fC157602B— the mainnet USDC adapter; no code on Sepolia0x01C5C0122039549AD1493B8220cABEdD739BC44E—symbol()=USDC,decimals()=6on Sepolia0x4822e58de6f5e485eF90df51C41CE01721331dC0— no code on Sepolia (an Alfajores-era address)0xbf1441Ea57f43f35f713431001f35742c88071c7— registered in the SepoliaFeeCurrencyDirectory;adaptedToken()→0x01C5…BC44EFiles:
build-on-celo/build-with-ai/overview.mdx:125andbuild-on-celo/fee-abstraction/using-fee-abstraction.mdx:52. The canonical reference pagetooling/contracts/fee-currencies.mdx:72already had the correct pair; the guides had drifted from it. Explorer links switched tocelo-sepolia.blockscout.com, the explorer the reference page and the network-overview page use for Sepolia.What this does NOT do / residual risk
legacy/protocol/transaction/erc20-transaction-fees.mdx:47, which carries the same stale pair labelled Alfajores — that file is deleted by task: Remove the Legacy tab — migrate still-relevant L1 content to Learn/Operate, delete the rest #2254.Judgement calls
Issues
Closes #2268 — the wrong rows are replaced and every address in them was verified on-chain (below). The OPEN item in the issue (verify the adapter column) is resolved: the old adapter had no code; the new one is the directory's.
Stacking / conflicts
Branched off
main, independent of my other open PRs. No other open PR touches these two lines.Verification evidence
Read straight from the chain on 2026-08-21 (
FeeCurrencyDirectoryresolved via the registry at0x…ce10, thengetCurrencies()andadaptedToken()/symbol()/decimals()on each):Remaining ops steps
Checklist
mainmint broken-linkspasses