wiki: DIN-Representative page describes the old CLI (dindao) and pre-P3 contracts

[umeradl]

Summary

Found while reviewing PR No. 204 (verification comment). The public wiki's DIN-Representative page describes an older CLI and older contracts. PR No. 204 refreshes the repo-side docs (Documentation/public/roles/dinrep.md); the wiki page needs the same pass once that merges.

What's out of date

Wiki text	Current state
dincli dindao add-slasher, dincli dindao registry approve-model / reject-model / …	The CLI group is dincli dinrep, and the commands are approve-registration-request, reject-registration-request, approve-manifest-update, reject-manifest-update, …
"DIN DAO command reference" → Documentation/public/roles/dindao.md	That file doesn't exist. The page is roles/dinrep.md
"Deploys the platform contracts (DinCoordinator → DinValidatorStake → DinModelRegistry)"	There are seven proxies (adding DinTreasury, DinToken, DinFeeRouter and DinEmission), deployed by foundry/script/DeployPlatform.s.sol and then dincli system import-deployments
"administers … treasury withdrawals"; "Accumulated fees are withdrawable"	DinCoordinator.withdraw() is gone. Faucet and registry ETH go to DinFeeRouter via sweep-fees
"a single transferable admin (set-admin)"	There is no set-admin command. Ownership is transferOwnership on each contract
"Cannot mint DIN at will — minting is bound to depositAndMint()"	DinCoordinator.mintEmission() also mints, via DinEmission, under mintCap. The owner sets dinPerEth, mintCap and retireFaucet
"by design it evolves into the DIN-DAO"	On-chain DIN-DAO governance is deferred to post-mainnet (DD-3)
Kill switch: "downstream contracts check the flag before executing tasks"	The task contracts don't read modelDisabled. Disabling only blocks manifest updates

Fix

Rewrite the page against roles/dinrep.md as merged in PR No. 204. Keep the wiki conventions: links to blob/develop/..., no assignee names or week-level dates.

Related

PR No. 204, issue No. 203.

[umermjd11]

The wiki has been rewritten against develop @ 740a613, which covers every row of this issue. The scope was widened to the whole wiki, and every page now carries a "DevNet 2.0, soon to be launched" banner.

• DIN-Representative page: https://github.com/InfiniteZeroFoundation/DevNet/wiki/DIN-Representative
• Diff: https://github.com/InfiniteZeroFoundation/DevNet/wiki/_compare/41fb474...6a20a3b (commits 4ea2744 content, 6a20a3b banner)

#207 rows (DIN-Representative page):

• dincli dindao … → dincli dinrep … with the current command names (approve-registration-request, reject-registration-request, approve-manifest-update, reject-manifest-update, disable/enable-model, fee setters, both sweep-fees)
• The command-reference link points to roles/dinrep.md
• Platform deploy: seven Transparent proxies via foundry/script/DeployPlatform.s.sol, then dincli system import-deployments
• Fees: no DinCoordinator.withdraw(). Registry and coordinator ETH go to DinFeeRouter via sweep-fees
• No set-admin: ownership is transferOwnership on each contract, and each ProxyAdmin has its own owner
• Minting: depositAndMint() and mintEmission() (via DinEmission), both under mintCap. The owner sets dinPerEth, mintCap and retireFaucet
• DIN-DAO governance deferred to post-mainnet (DD-3)
• Kill switch: the task contracts don't read modelDisabled, so disabling only blocks manifest updates

The other pages were also checked against develop:

• Platform and Task Contracts: 26 GI states, commit-reveal, encrypted test data, rewards 60/20/15/5, disputes, S1–S5.
• Role pages: the current command names.
• DIN CLI: Python ≥3.12, register-wallet, and an install line that works.
• IPFS: gateway fallback and CID verification.
• SDK / Daemon / Indexer: marked in progress on unmerged PRs.
• DIN DAO: marked deferred.

Every blob/develop link and every internal wiki link resolves.

Repo docs that still drift (not changed here; could be a follow-up docs PR):

• ROADMAP.md:19 calls the next deploy "DevNet 3.0".
• din-workflow.md still lists 4 contracts and withdraw.
• setup.md has the broken @main#subdirectory=dist install line.
• Old command names in roles/clients.md, roles/auditors.md, roles/model-owner.md and model-workflow.md: train-lms --submit, create-genesis, and missing reveal steps.

Part F of task_021026_19. Leaving the close to the maintainer.

🤖 Generated with Claude Code

[umeradl]

Done in the wiki: the DIN-Representative page was rewritten in wiki commit 4ea2744, plus the DevNet 2.0 banner in 6a20a3b (diff, revision comment). This was task_021026_19 Part F; there's no repo PR, so closing by hand.

Checked on a fresh clone of the wiki @ 6a20a3b (DIN-Representative.md), row by row:

• dindao → dinrep: no dincli dindao left; 17 dincli dinrep commands, including approve-registration-request, reject-registration-request, approve-manifest-update and reject-manifest-update.
• Command reference: links to roles/dinrep.md; no roles/dindao.md link.
• Platform deploy: seven contracts, each behind a Transparent Proxy (DinTreasury, DinToken, DinFeeRouter, DinCoordinator, DinValidatorStake, DINModelRegistry, DinEmission), via foundry/script/DeployPlatform.s.sol, then dincli system import-deployments.
• Fees: "There is no withdraw()"; ETH is swept to DinFeeRouter with sweep-fees.
• Admin: "There is no single set-admin switch"; ownership is transferOwnership per contract, and each ProxyAdmin has its own owner.
• Minting: depositAndMint() and mintEmission() via DinEmission, under mintCap; the owner sets dinPerEth, mintCap and retireFaucet. Matches DinCoordinator.mintEmission on develop (msg.sender != emissionContract reverts; mintCap check).
• DIN-DAO: deferred to post-mainnet (DD-3).
• Kill switch: "The task contracts don't read this flag", so disabling only blocks manifest update requests and approvals.
• Wiki conventions: all repo links are blob/develop/...; no assignee names or week-level dates.

The task's deliverables are ticked in Developer/tasks/task_021026_19.md by PR No. 217 (merged as a1fcce2). The repo-docs drift found while writing the wiki is listed under follow-ups in Discussion No. 216; it isn't tracked in an issue yet.