AskBots round-1 findings: Canonical identifiers, fee-currency adapters and remaining explorer cleanup

Open
#2,410 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
markdown
Domain
documentation

Research direction

Start with the listed pages learn/manage/self-custody.mdx and learn/network/overview.mdx, then inspect the networks, tokens, and adapters data and how the overview imports it. Check the feeCurrency table and the scope of llms.txt as described in the findings. Done means the remaining explorer and date wording are cleaned up, identifiers and feeCurrency guidance are consistent, and the llms.txt scope is documented or committed.

Written by the indexing model from the issue text.

Description

AskBots reviewer agents reviewed this project (20 reviews, round 1). Public page: https://askbots.ai/p/k177pcex5yfv9vp2x2699rpbhh8bzwas

Findings

  • Single canonical identifiers JSON + page. Evidence: multiple. Quote: "celo.blockscout.com appears 136 times… canonical reference omits the most-used explorer". Fix: networks/tokens/adapters JSON imported into the network overview; consistent EIP-55 casing.
  • Document feeCurrency adapter vs token for USDC/USDT; fix reversed table headers. Evidence: 2.
  • Finish old-explorer / Alfajores cleanup. Still present: explorer.celo.org link in learn/manage/self-custody.mdx; "September 2025" future-tense wording in learn/network/overview.mdx. Related: #2383, #2263.
  • Commit/document llms.txt scope. Evidence: 1–2.

Dropped: excluding legacy/ and _deprecated/ from the build (those folders are gone); 44787-as-live in the portal page (page no longer exists).


From an AskBots review round on 2026-08-06; Lena will run round 2 after fixes. I re-checked each item against the current repo on 2026-10-22 and dropped ones that are already fixed.

Dominant language
MDX
Stars
89
Forks
396
Avg merge
3d 5h
Merged PRs (30d)
17

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from celo-org/docs

All issues in celo-org/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.