Skip to content

Add a one-command setup checker for new contributors (BL-32) #275

Closed as duplicate

Description

@abrahamnash

New contributors often lose time because something on their machine isn't set up yet. We'd like one command that checks everything before work starts.

What it should check (one line each, OK or MISSING → <fix hint>):

  1. Python ≥ 3.12
  2. forge / anvil installed, solc 0.8.28 available
  3. foundry/node_modules present (run npm ci if not)
  4. eth-account and py-multibase import
  5. torch imports in the active environment
  6. .env / .env.<network> exist, the RPC endpoint answers, and resolve_ipfs_config() resolves

Rules: read-only (it reports what's missing and never installs anything), and it exits non-zero if any check fails.

Form: scripts/preflight.sh or a dincli system doctor command, whichever you prefer.

Size: about half a day. Full background is in Developer/BACK_LOG.md, item BL-32.

Activity

  1. ashish04sharma commented on Oct 25, 2026

    @ashish04sharma

    i would love to help you and contribute in that

  2. abrahamnash commented on Oct 25, 2026

    @abrahamnash
    MemberAuthor

    Hi @ashish04sharma, thank you, great to have you! I've assigned this to you.

    To get started:

    • Setup and contribution guides: DEVELOPMENT_SETUP.md and CONTRIBUTING.md
    • Branch: please branch off develop and open your pull request against develop.
    • Background: item BL-32 in Developer/BACK_LOG.md
    • Form: we'd suggest a standalone scripts/preflight.sh, since it still works before dincli is installed, which is exactly when people need it. If you'd rather build dincli system doctor, just say so here first.
    • Rules: read-only (report, never install), one line per check, and a non-zero exit if anything fails.

    If you get stuck or something in the setup docs is unclear, ask here or in our Telegram: https://t.me/+h46VS3AnO384ZGI8. Unclear docs are useful feedback for us too.

    Once your PR is up, a maintainer will review it. Thanks again!

  3. abrahamnash commented on Oct 26, 2026

    @abrahamnash
    MemberAuthor

    Closing as a duplicate of #245, which is already being handled in PR #255. Sorry, I missed that when I opened this one.

    @ashish04sharma thank you for offering to take it on. Would you like to pick another one from the good first issues? https://github.com/InfiniteZeroFoundation/DevNet/issues?q=is%3Aissue%20is%3Aopen%20label%3A%22good%20first%20issue%22

  4. added a commit that references this issue on Oct 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions