feat(base): mainnet-readiness safeguards, Basenames and portable reputation attestations
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by reading the registry dependency in issue #2 and the shared ENS resolution code referenced by the issue; inspect the current network configuration and worker_pricing reputation storage. Verify the Base Sepolia attestation service deployment and schema registry process before choosing an integration path. Done means mainnet fails fast without the explicit flag and registry entry, wallet and funder lists resolve names with address fallback, and a sample worker attestation can be issued, read back, and revoked on testnet.
由索引模型根据 Issue 内容生成。
描述
Summary
Prepare the Base integration for a future mainnet decision without enabling it, and add two Base-native features: human-readable names and worker reputation attestations.
Motivation
Base is the existing chain. Safeguards and clear configuration reduce the risk of a mainnet mistake; Basenames and attestations make workers and funders easier to identify and trust.
Current state in this repo
- Base Sepolia is the only configured network;
NETWORKdefaults tobase-sepolia. - Worker
reputation_scorelives only in MongoDB (worker_pricing).
Proposal
- Mainnet guard: refuse mainnet unless an explicit env flag and a registry entry (#2) are present; log a startup warning when enabled; add a runbook covering custody, limits and monitoring.
- Basenames: resolve and display primary names for wallets on Base (see the ENS issue for shared resolution code).
- Attestations (optional): publish a worker reputation or fidelity attestation on Base Sepolia using a standard attestation service, signed by the platform, so reputation is portable.
Acceptance criteria
- Starting with a mainnet network configured but the flag unset fails fast with a clear message.
- Wallet and funder lists show a name when one exists and fall back to the address.
- An attestation can be issued, read back and revoked on testnet for a sample worker.
Out of scope
- Actually enabling mainnet.
Dependencies
- #2
Verify before implementing
- Current attestation service deployment on Base Sepolia and its schema registry process.
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
- 平均合并
- 5 小时 19 分钟
- 30 天内合并 PR
- 11
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
QMeshPy/distributed-quantum 的其他 Issue
-
enhancement good first issue helia storage tier-1
难度 2/5 1-3 小时 新手友好度 78/100
QMeshPy/distributed-quantum#53 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments research-spike tier-2
难度 4/5 3-5 天 新手友好度 55/100
QMeshPy/distributed-quantum#78 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments research-spike tier-2
难度 3/5 1-2 天 新手友好度 66/100
QMeshPy/distributed-quantum#77 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments tier-2
难度 5/5 一周以上 新手友好度 35/100
QMeshPy/distributed-quantum#76 ·
维护者通常 1 天内回复
-
documentation good first issue kubo storage tier-1
难度 2/5 1-3 小时 新手友好度 42/100
QMeshPy/distributed-quantum#75 ·
维护者通常 1 天内回复
查看 QMeshPy/distributed-quantum 的全部 Issue
相似的 Issue
-
bug
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 84/100
sergey-miryanov/gcmon#230 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
Azure-Samples/azure-search-openai-demo#3249 ·
维护者通常 1 天内回复
-
[BUG] Failed archive extraction deletes the dataset cache可能已有人在做 @dajiaohuang 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
alibaba/GraphScope#4674 ·