Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#78 コメント 3 件 リアクション 1 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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日 58分
マージ済み PR（30日）
39

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

InfiniteZeroFoundation/DevNet のほかの issue

InfiniteZeroFoundation/DevNet の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。