Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#36 2 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
28/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Pouca atividade
Stack de tecnologia
python, solidity
Domínio
blockchain

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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)
Linguagem predominante
Python
Estrelas
4
Forks
7
Merge médio
3d 5h
PRs com merge (30d)
34

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de InfiniteZeroFoundation/DevNet

Todas as issues de InfiniteZeroFoundation/DevNet

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.