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

Simulation: model validator gas costs to size ETH network fee for model trainers

未关闭
  • 哪里不对？
#78 5 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
solidity
领域
blockchain, fintech-quant

调研方向

The issue names the P3-5.2 simulation requirement and MECHANISM_DESIGN §5; start by reading those to find the existing validator income model and its assumptions. Model aggregation, evaluation, and worst-case dispute gas across the listed participation variables, using current Optimism gas prices. Report low, mid, and high scenario costs in ETH, the fee floor, sensitivity at 10× and 0.1× participation, and any unprofitable scenario.

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

描述

Context

Discussed with @abrahamnash (Aug 2026). The resolved fee model is:

  • All protocol fees in ETH — DIN is staking/utility only, no fee denomination migration
  • Network fee (model trainer → validators, paid per-GI) must be sized from real gas data, not assumed
  • Current design has no hard numbers; this simulation is the prerequisite for setting the fee

The network fee is essentially gas recovery for validators: model trainers pay it upfront, validators get reimbursed for the on-chain work they do per GI. Getting this wrong in either direction (too low = validators lose money, too high = model owners won't participate) blocks the validator economics from being viable at scale.

Scope

Three scenarios to model, covering the full on-chain surface validators touch per GI:

1. Aggregation submissions
  • T1 sub-batch CID submission gas cost (per aggregator, per batch)
  • T2 combined CID submission gas cost
  • Baseline: aggregation logic is off-chain — only the final CID goes on-chain (per Abraham's design intent)
  • Variables: number of T1 batches, number of aggregators per batch
2. Evaluation submissions (batched vs per-round)
  • Gas cost of a single auditor submitting scores on-chain (setAuditScorenEligibility)
  • Batched final-round evaluation: all submissions in one round vs spread across rounds
  • Variables: number of clients per auditor, number of auditors per batch, pass/fail ratio
3. Dispute scenarios (worst-case)
  • Full dispute chain gas cost: dispute open → bond post → fresh subgroup reassignment → re-evaluation submissions → resolution
  • Disputes are rare by design (random assignment + >50% consensus threshold) — but worst-case must be bounded so it does not make the network fee unworkable
  • Variables: dispute window length, subgroup size

Expected output

  • Gas cost range (low/mid/high participation) for each scenario in ETH at current Optimism gas prices
  • Recommended ETH network fee floor that covers validator gas at target participation level
  • Sensitivity table: what happens to validator economics at 10× and 0.1× participation
  • Flag any scenario where gas costs alone make validator participation unprofitable at the proposed fee floor

Notes

  • Aligns with the existing P3-5.2 simulation requirement (validator income stability at target/10×/0.1× participation) — this scopes the gas input to that model
  • Builds on the mitigations already in the design: aggregation off-chain, evaluations batched to final round, disputes rare — the simulation should validate those mitigations hold under load
  • Reward split (clients/validators/treasury %) is a separate open item and out of scope here — see MECHANISM_DESIGN §5

cc @abrahamnash

主要语言
Python
星标
4
派生
7
平均合并
3 天 4 小时
30 天内合并 PR
34

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

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

InfiniteZeroFoundation/DevNet 的其他 Issue

查看 InfiniteZeroFoundation/DevNet 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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