Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
  • Is something wrong?
#43 5 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@robertocarlous is already working on this.

Since Jul 21, 2026.

Assessment

This issue has not been assessed yet.

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)

Dominant language
Python
Stars
4
Forks
7
Avg merge
3d 5h
Merged PRs (30d)
34

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from InfiniteZeroFoundation/DevNet

All issues in InfiniteZeroFoundation/DevNet

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.