P3 dispute: decentralize adjudication — owner-adjudicator trust assumption must be removed before mainnet
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- solidity
- 领域
- blockchain, security
调研方向
Read the S4 slashing taxonomy and adversarial threat model referenced in the issue, then inspect DINTaskCoordinator.resolveDispute and settleRecomputation. Compare the candidate adjudication paths and their dependencies, including #23 for the DAO option. Done means a dispute can be decided without relying solely on the model owner; the issue does not select a design.
由索引模型根据 Issue 内容生成。
描述
Summary
resolveDispute and settleRecomputation in DINTaskCoordinator are onlyOwner. The model owner is therefore both the party who can benefit from suppressing a valid dispute and the sole adjudicator who decides whether to uphold it.
This is called out explicitly in the slashing taxonomy (S4 section) and in the adversarial threat model as a KNOWN GAP: a challenger who opens a valid dispute and posts a bond has no recourse if the owner simply calls settleRecomputation(confirmed=false) — the bond is forfeited and no aggregators are slashed.
Impact
An owner-colluding-aggregator attack is undetectable and uncostly for the owner. Any honest challenger loses their bond. The S4 dispute mechanism provides no protection against a colluding owner.
Candidate paths
- On-chain fraud-proof with model-output verification (not feasible for large tensor models)
- Multi-sig or timelock on
settleRecomputation - DAO committee vote on dispute outcomes (requires #23 DIN-DAO)
- Optimistic challenge-response with a neutral arbitrator contract
Tracking
Surfaced in the adversarial threat-model doc (task_240926_17, PR 1). Blocks full DEFENDED rating for S4.
- 主要语言
- Python
- 星标
- 4
- 派生
- 7
- 平均合并
- 3 天 4 小时
- 30 天内合并 PR
- 34
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
InfiniteZeroFoundation/DevNet 的其他 Issue
-
ROADMAP.md: refresh "What is still open for P3" (several items were fixed in October)可能已有人在做 @umermjd11 于 2 天前认领。 未关闭documentation good first issue
难度 2/5 1-3 小时 新手友好度 74/100
InfiniteZeroFoundation/DevNet#285 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Update the 25 translated organisation READMEs to match the English version可能已有人在做 @mrCabez 今天认领。 未关闭good first issue help wanted
难度 2/5 1-3 小时 新手友好度 76/100
InfiniteZeroFoundation/DevNet#277 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
InfiniteZeroFoundation/DevNet#266 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
InfiniteZeroFoundation/DevNet#299 · 1 条评论 ·
维护者通常 1 天内回复
-
Long run
难度 5/5 一周以上 新手友好度 25/100
InfiniteZeroFoundation/DevNet#298 ·
维护者通常 1 天内回复
查看 InfiniteZeroFoundation/DevNet 的全部 Issue
相似的 Issue
-
changelog investigate
难度 2/5 1-3 小时 新手友好度 67/100
ramnes/notion-sdk-py#433 ·
-
docs pkg:core
难度 1/5 1 小时以内 新手友好度 84/100
pydantic/pydantic-ai#11929 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
intake/intake-esm#789 ·
-
难度 2/5 1-3 小时 新手友好度 82/100
MemMachine/MemMachine#1877 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
openedx/openedx-authz#579 ·
维护者通常 1 天内回复