task: fix the fee abstraction examples (adapter vs token address, decimals, imports)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 86/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
Start with build-on-celo/fee-abstraction/using-fee-abstraction.mdx, then read AGENTS.md section 5 and the referenced Fee currency contracts. Correct the CLI and viem examples, imports, decimals, and address labels; run the examples as specified, note their output in the PR, and verify that mint broken-links is green.
Written by the indexing model from the issue text.
Description
Follow-up from #2257, which added a troubleshooting section to the fee abstraction guide but left the existing examples as they were.
What needs to be done?
Three problems in build-on-celo/fee-abstraction/using-fee-abstraction.mdx, found while checking the page against the fee currency list and the JSON-RPC behaviour on Celo mainnet. AGENTS.md section 5 says every example that stays must run.
- CLI USDC example uses the adapter as the token. The first
celocli transfer:erc20block passes--erc20Address 0x2F25deB3848C207fc8E0c34035B3Ba7fC157602B. That address is the USDC adapter; the USDC token is0xcebA9300f2b948710d2653dD7B07f33A8B32118C(see Fee currency contracts). The text under the block says transfers use the token address. The USD₮ example below it is correct (token in--erc20Address, adapter in--gasCurrency). - viem step 3 mixes decimals and has missing imports.
parseEther("1") - transactionFeetreats USDC as 18 decimals, but USDC has 6; the snippet usesencodeFunctionData,parseEtherandformatEtherwithout importing them; step 1 callshexToBigInton the result ofestimateGas, which viem already returns as a bigint. - Addresses are not labelled. Every address in the examples should carry the network name and, for tokens, the decimals (AGENTS.md section 5), for example
// Celo mainnet (42220), USDC adapter.
Definition of done
- The CLI USDC example uses the token address for
--erc20Addressand the adapter for--gasCurrency, and the command is run once with its output noted in the PR - The viem examples are self-contained (imports shown), use the token's decimals, and are run against Celo Sepolia with the command and output noted in the PR
- Every address in both examples is labelled with network and decimals
-
mint broken-linksgreen
Priority
medium
Size
S — hours
Refs #2257.
- Dominant language
- MDX
- Stars
- 89
- Forks
- 396
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 17
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from celo-org/docs
-
Add BlockVectra to the Celo mainnet RPC providers listPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
chore priority:medium
Difficulty 2/5 Half a day Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
storytold/photocraft#15350 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
docker documentation
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
VincenzoImp/openings-job-search#463 ·
Maintainers usually reply within 1 day
-
source:reader type:content-error
Difficulty 1/5 Under an hour Newbie friendliness 82/100
stephrobert/blog-roadmap#193 ·
-
Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
pandas-dev/pandas#72163 ·
Maintainers usually reply within 2 days