Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

P3 fees & treasury: fee lines, fee-router contract, DIN denomination (P3-5.3)

Ouverte
  • Quelque chose ne va pas ?
#43 5 commentaires 0 réactions 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@robertocarlous y travaille déjà.

Depuis le 21/7/2026.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

enhancement

Part of the P3 mechanism-design push (#36).

Summary

Model owners should pay for the network services they consume, with a slice of every flow sustaining a real treasury. Today only ETH registration/manifest fees exist in DINModelRegistry, withdrawable by owner() — no per-GI service fees, no treasury, no routing.

Scope (from MECHANISM_DESIGN §8)

  • Fee lines: model registration fee (open-source vs proprietary tiers, reroute to treasury), manifest update fee, per-GI service fee (one flow with the reward-pool deposit: 95% validator pool / 5% treasury), storage-cost line item (design the routing slot now, hold at 0 until Filecoin migration — RES-1), dispute bond (returned + bounty if upheld, treasury if frivolous)
  • Fee-router contract: single router with DAO-settable basis-point split fractions modelOwner → {validatorPool, treasury, burn, storage} summing to 100%; sane hard bounds only (e.g., treasury cut ≤ 20%). ✅ Resolved (Abraham, 2026-07-21): add a publicGoods slot to the split ({validatorPool, treasury, burn, storage, publicGoods}) now — it doesn't need to be funded immediately, but the slot needs to exist or it never gets built later.
  • Denomination: registration fees are ETH today, staking/rewards are DIN. ✅ Resolved as a split, not "DIN for all protocol fees" as previously recommended here (Abraham, 2026-07-21): on-chain protocol fees (registration, manifest updates, staking, rewards) → DIN; validator network fees (model owner → validator, i.e. the per-GI service fee, storage line item, dispute bond) → stay in ETH — model owners already pay gas in ETH, and requiring DIN just to pay validators adds friction the depositAndMint on-ramp doesn't fully remove. Migration path: DIN params for the protocol-fee lines only, deprecate their ETH variants after one release; the network-fee lines have no ETH-to-DIN migration. The fee router must handle both assets going forward — accepted complexity, not deferred.
  • Burn policy: ✅ Resolved: burn a fraction of both on-chain protocol fees and validator network fees (dual sources), start at 0%, keep the hook — in addition to the slashed-stake burn share (see #38, #42).
  • Dynamic fees: admin/DAO-settable base rate + per-role multipliers; no algorithmic fee logic in 2.0 — parameterize now, automate later

Design sources

MECHANISM_DESIGN §8 · issues/tokenomics.md (fee routing scope) · whitepaper-summary §5 (network fees as validator revenue; quadratic public-goods funding stance)

Roadmap anchors: P3-5.3 (fee mechanism), P3-5.1 (governance hooks), RES-1 (Filecoin storage cost slot)

Langage dominant
Python
Étoiles
4
Forks
7
Merge moyen
3 j 4 h
PR mergées (30 j)
34

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de InfiniteZeroFoundation/DevNet

Toutes les issues de InfiniteZeroFoundation/DevNet

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.