feat(optimism): OP Stack support (Optimism, Unichain-ready) in the chain registry
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 42/100
Research direction
Start by inspecting the chain registry and the wallet, transfer, and x402 selectors; the issue does not name their files. Check provider support and verify Unichain chain IDs and testnet details from official sources before implementing. Done means Optimism testnet wallet creation, balance, and USDC transfer work, and the registry entry validates and appears in GET /api/v1/chains.
Written by the indexing model from the issue text.
Description
Summary
Add Optimism (testnet) as a supported EVM chain and make the registry ready for other OP Stack chains such as Base and Unichain.
Motivation
Optimism, Base and Unichain share a stack, so one well-tested family profile covers several chains and ENS L2 primary names.
Current state in this repo
- Only Base Sepolia is configured.
Proposal
- Add Optimism testnet to the registry (#2) with stablecoin and explorer data.
- Document OP Stack quirks (L1 data fee, finality) in the adapter notes.
- Add the network to wallet, transfer and x402 selectors.
Acceptance criteria
- Wallet creation, balance and USDC transfer work on the Optimism testnet.
- Registry entry validates and appears in
GET /api/v1/chains.
Out of scope
- Mainnet.
- Optimism-specific governance or retro-funding mechanics (see the quadratic funding issue).
Dependencies
- #2
Verify before implementing
- Wallet provider support for Optimism.
- Unichain chain ids and testnet details from official sources.
Part of ##1. Ground rules for all issues in this roadmap are listed there (testnet-first, no secrets in the repo, chain logic behind the registry, tests and docs with every PR).
- Dominant language
- Python
- Stars
- 2
- Forks
- 4
- Avg merge
- 5h 19m
- Merged PRs (30d)
- 11
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No 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 QMeshPy/distributed-quantum
-
enhancement good first issue helia storage tier-1
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
QMeshPy/distributed-quantum#53 ·
Maintainers usually reply within 1 day
-
chain-integration enhancement payments research-spike tier-2
Difficulty 4/5 3-5 days Newbie friendliness 55/100
QMeshPy/distributed-quantum#78 ·
Maintainers usually reply within 1 day
-
chain-integration enhancement payments research-spike tier-2
Difficulty 3/5 1-2 days Newbie friendliness 66/100
QMeshPy/distributed-quantum#77 ·
Maintainers usually reply within 1 day
-
chain-integration enhancement payments tier-2
Difficulty 5/5 Over a week Newbie friendliness 35/100
QMeshPy/distributed-quantum#76 ·
Maintainers usually reply within 1 day
-
documentation good first issue kubo storage tier-1
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
QMeshPy/distributed-quantum#75 ·
Maintainers usually reply within 1 day
All issues in QMeshPy/distributed-quantum
Similar issues
-
resource-submission validation-passed
Difficulty 1/5 Under an hour Newbie friendliness 88/100
hesreallyhim/awesome-claude-code#3214 · 1 comment ·
Maintainers usually reply within 1 day
-
room-commons replace accepts an empty old string and silently prepends the new text to the pageOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
doobidoo/mcp-memory-service#1650 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ml-explore/mlx-lm#2002 ·
Maintainers usually reply within 2 days