Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#283 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@umermjd11 ya está trabajando en esto.

Desde el 26/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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.
Lenguaje dominante
Python
Estrellas
4
Forks
7
Merge medio
3 d 58 min
PR fusionados (30 d)
39

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de InfiniteZeroFoundation/DevNet

Todos los issues de InfiniteZeroFoundation/DevNet

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.