Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#283 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@umermjd11 ci sta già lavorando.

Dal 26/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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.
Lingua principale
Python
Stelle
4
Fork
7
Merge medio
3g 5h
PR unite (30g)
34

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di InfiniteZeroFoundation/DevNet

Tutte le issue di InfiniteZeroFoundation/DevNet

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.