Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

feat(optimism): OP Stack support (Optimism, Unichain-ready) in the chain registry

未关闭
#16 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
42/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
backend, databases

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

chain-integration enhancement help wanted tier-1

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).

主要语言
Python
星标
2
派生
4
平均合并
6 小时 54 分钟
30 天内合并 PR
7

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

QMeshPy/distributed-quantum 的其他 Issue

查看 QMeshPy/distributed-quantum 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。