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

Data-owner (client) rewards: off at launch; if offered later, paid in a stablecoin, not DIN

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

维护者通常 1 天内回复

@umermjd11 已经在做这个了。

开始于 2026年10月26日。

评估

这个 Issue 还没有评估数据。

描述

enhancement

Decision (Abraham)

  1. No token rewards to data owners (clients) at launch. Many participants are put off by crypto and digital currencies, so taking part as a data owner should not involve tokens by default.
  2. If data-owner rewards are offered later, for example by an enterprise training a model that wants to reward contributors, they will be paid in a stablecoin, not DIN.

Current state (conflicts with the decision)

  • Each GI's reward pool is funded and paid in DIN (DINTaskAuditor.depositRewards and claimReward), and the design docs say the same (Developer/design/tokenomics-design.md: "model owners pre-fund each GI's reward pool in DIN").
  • DINTaskAuditor.rewardSplit defaults to 60% clients / 20% auditors / 15% aggregators / 5% treasury, so every model pays clients unless its owner changes it. The protocol's emission subsidy (DinEmission.fundGI) is split the same way.
  • setRewardSplit (owner-only, per model) already lets a model owner set clientBps to 0, but there is no stablecoin payment path.

Proposal

  1. Default to 0% clients at launch, redistributing that share across auditors, aggregators and treasury. For example, keeping their current ratios gives 50% / 37.5% / 12.5%. Final values to be set in #155.
  2. Design an optional, stablecoin-denominated client reward path for later: who funds it (e.g. the enterprise model owner), which stablecoin, and how it's distributed. Design only for now; no implementation before testnet.
  3. Update the design docs (tokenomics-design.md, MECHANISM_DESIGN.md) to record both decisions.
  4. Review public wording (README, partner introduction, white-paper summary) so nothing promises DIN or token rewards to data owners.
主要语言
Python
星标
4
派生
7
平均合并
3 天 58 分钟
30 天内合并 PR
39

环境准备

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

从这里开始

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

InfiniteZeroFoundation/DevNet 的其他 Issue

查看 InfiniteZeroFoundation/DevNet 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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