task_210726_5 — Platform Tokenomics & Fee Infrastructure (Robbert)

[umeradl]

cc @robertocarlous
Task assigned for Jul 21–27, 2026 (5 working days; deadline Monday, July 27). Full spec: Developer/tasks/task_210726_5.md

The task file has the full specification — exact contract code, function signatures, deployment/wiring order, and test plan. This post is just the summary and assignment notice.

Summary

Issues #37 (staking), #42 (tokenomics), and #43 (fees & treasury) are now design-resolved, and the underlying contract work is genuinely coupled — a new DinTreasury and DinFeeRouter are shared infrastructure both tokenomics and fees need. Combined into one 5-day task rather than three separate ones:

New: DinTreasury.sol — pure holding/spend contract for ETH and ERC20, no split logic, deploys first (no dependencies).

New: DinFeeRouter.sol — owns all fee-split logic. Separate DIN and ETH split configs; the ETH config has no burn bucket at all — structurally, not just by convention, since native ETH can't be burned. Routes DIN protocol fees (burn/treasury/validatorPool/storage/publicGoods) and ETH network fees (treasury/validatorPool/storage/publicGoods, no burn).

DinToken.sol — adds a plain burn(uint256) self-burn function.

DinCoordinator.sol — adds a settable mint cap, a one-way faucet-retirement switch, and reroutes deposited ETH to DinTreasury instead of owner().

DinValidatorStake.sol — converts MIN_STAKE/UNBONDING_PERIOD from constants to owner-settable storage, adds (currently-unenforced) per-model stake bounds storage, and makes jailing real — jailValidator/reactivate — since the Jailed status has existed as dead code until now.

DINModelRegistry.sol — adds a DIN-denominated fee path alongside the existing ETH fees (not replacing them yet), routed through DinFeeRouter.

Scope is platform-contracts only for this task — task-level contract enforcement (DINTaskCoordinator/DINTaskAuditor), DinEmission, delegation, and tombstoning are all explicitly out of scope; see the task file's "Scope boundaries" section for why.

Reference material

• Developer/design/MECHANISM_DESIGN.md §7–§9
• Developer/design/staking-design.md
• Developer/design/tokenomics-design.md
• P3 staking: DAO-settable floor, per-model stake requirements, concurrent-registration cap, withdrawal queue #37, P3 tokenomics: token utility, emission schedule, supply policy, treasury (P3-5.1/5.2) #42, P3 fees & treasury: fee lines, fee-router contract, DIN denomination (P3-5.3) #43 — all updated with the resolved decisions this task implements

If anything in the task spec doesn't feel right, is ambiguous, or needs clarification — comment here and cc @umeradl.

[robertocarlous]

Hi Umer.

I will look into this. Thank you