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

ROADMAP.md: refresh "What is still open for P3" (several items were fixed in October)

Open Beginner friendly
#285 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@umermjd11 is already working on this.

Since Oct 27, 2026.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown, solidity

Research direction

Read the “What is still open for P3” section in Developer/ROADMAP.md and check the linked issues and pull requests named in the issue to confirm their current status and decisions. Update that section to mark the resolved items and include the listed pre-testnet items. Done when the roadmap accurately reflects those statuses and decisions, including the DevNet 3.0 rehearsal deploy to OP Sepolia.

Written by the indexing model from the issue text.

Description

documentation good first issue

The "What is still open for P3" section of Developer/ROADMAP.md (last updated Sep 30) is out of date:

  • Deploy blocker (#201 Part A): resolved. DINTaskCoordinator is now 23,507 B, under EIP-170 (but only 45 B above the CI size gate; see #201).
  • #192 (auditor commit hash not sender-bound): fixed by #212.
  • #180 (dual-role registration): fixed by #235.
  • #193 (per-model S5 recidivism): fixed by #236.

Please also add the current pre-testnet items:

  • #238 (emission schedule can be drained), now marked a testnet blocker
  • #222 (stuck-GI recovery; policy decided)
  • the #224 decisions (kill-switch, rejected-model fee, S6)
  • the data-owner rewards decision (off at launch; stablecoin if ever offered)
  • the DevNet 3.0 rehearsal deploy to OP Sepolia

Funders and new contributors read this section as the project's status, so keeping it current matters.

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.