P3 push-start: cryptoeconomic mechanism design tracking (staking, slashing, auditing, scoring, rewards, fees/treasury, tokenomics)

Open
  • Is something wrong?
#36 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
28/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python, solidity
Domain
blockchain

Research direction

Read Developer/design/MECHANISM_DESIGN.md §9, then compare the child issues #37–#43 with the sequencing in Developer/ROADMAP.md. Track unresolved decisions and record agreed outcomes in the design document; done when every child design is agreed, discussions are resolved, the child issues are on project board 6, and contract work can start from a frozen spec.

Written by the indexing model from the issue text.

Description

enhancement Umbrella

Why this issue exists

P4 (din-dao #23, din-sdk #20, din-daemon #21, din-indexer #24) is the currently active phase, but P3 — the cryptoeconomic layer — is delayed because finalized designs for its mechanisms do not exist yet: staking, slashing, auditing, scoring, rewards, network fees/treasury, and tokenomics. This is why project board 6 has been nearly empty while board 7 fills up.

The design groundwork now exists in-repo. This issue tracks the design push that unblocks P3: each child issue below must reach an agreed design (open decisions closed, discussion threads resolved) before its contracts/implementation work starts.

Canonical design sources

  • Developer/design/MECHANISM_DESIGN.md — consolidated DevNet 2.0 cryptoeconomic design: role × mechanism matrix, current on-chain state vs gaps, per-mechanism designs, and the §9 consolidated open-decision list.
  • Developer/design/whitepaper-summary.md — summary of the DIN white paper (Abraham Nash, Jun 2026) with a gap/alignment checklist (§8) mapping paper mechanisms to DevNet status.
  • Developer/ROADMAP.md — work packages P3-4.x (slashing), P3-SCR (scoring), P3-5.x (token utility / emission / fees), P3-6.x (testing/audit), P3-DOC2/3/5. Use the WP IDs for scope and sequencing; the week-by-week dates are not binding.

Child issues (one per mechanism)

  • #37 — Staking: DAO-settable floor, per-model stake requirements, concurrent-registration cap, withdrawal queue
  • #38 — Slashing: conditions taxonomy, penalty tiers, slashed-stake destination, dispute resolution (P3-4.1/4.2/4.3)
  • #39 — Scoring: BlockFLow validation (P3-SCR), on-chain median, scenario-driven scoring redesign
  • #40 — Auditing: auditor evaluation mechanism — commit-then-reveal, encrypted test data, deviation accountability
  • #41 — Rewards: per-GI reward engine and pull-payment claim flow
  • #42 — Tokenomics: token utility, emission schedule, supply policy, treasury (P3-5.1/5.2)
  • #43 — Fees & treasury: fee lines, fee-router contract, DIN denomination (P3-5.3)

Decisions under discussion

The consolidated open-decision list is MECHANISM_DESIGN §9. The protocol-shaping ones are open as Discussions for input from @abrahamnash and the team:

  • #44 — Slashing economics: slashed-stake destination, penalty sizing, dispute bonds, delegator semantics
  • #45 — Tokenomics: emission schedule, MAX_SUPPLY, fee denomination, burn policy
  • #46 — White paper ↔ DevNet alignment: delegation, encrypted test sets, resampling, commit-then-reveal, governance

Status update (2026-07-21): most of the above is now resolved — see the updated MECHANISM_DESIGN.md §9 and the corresponding notes on #37, #38, #40, #42, #43. Still open: reward split percentages, per-model stake bounds, dispute bond size/window, and the exact partial-slash fraction / S3 threshold (pending P3-SCR data).

Related backlog (design write-ups exist, not opened as issues yet)

Definition of done

  • Every child issue has an agreed design with its open decisions closed
  • Discussion threads resolved and decisions recorded back into MECHANISM_DESIGN.md
  • Child issues populated on project board 6
  • Contract work can start against a frozen mechanism spec (pre-audit, per P3-6.3b)
Dominant language
Python
Stars
4
Forks
7
Avg merge
4d 12h
Merged PRs (30d)
36

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.