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
- 平均合併
- 6 小時 13 分鐘
- 30 天內合併 PR
- 20
環境準備
- 提供 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 天內回覆
-
documentation good first issue kubo storage tier-1
難度 2/5 1-3 小時 新手友好度 42/100
QMeshPy/distributed-quantum#75 ·
維護者通常 1 天內回覆
-
enhancement kubo storage tier-2
難度 4/5 3-5 天 新手友好度 56/100
QMeshPy/distributed-quantum#74 ·
維護者通常 1 天內回覆
查看 QMeshPy/distributed-quantum 的全部 Issue
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 78/100
conda-forge/conda-forge-bot#7025 ·
維護者通常 1 天內回覆
-
area:ci
難度 1/5 1 小時以內 新手友好度 74/100
catincloud-labs/dagster-dex#149 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 84/100
home-assistant/core#188424 ·
維護者通常 1 天內回覆
-
Review backlog (docs-currency): README 'CI run' link lands on a run whose overall badge is cancelled未關閉agent/reviewer needs-kind needs-triage
難度 2/5 1-3 小時 新手友好度 63/100
projectbluefin/utah#880 · 2 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
redis/memtier_benchmark#850 ·
維護者通常 1 天內回覆