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

Rename DIN → INZ (token ticker) and dincli → inz (CLI) before public testnet

Open
  • Is something wrong?
#281 1 comment 0 reactions 2 assignees View on GitHub

Maintainers usually reply within 1 day

@abrahamnash is already working on this.

Since Oct 27, 2026.

Assessment

This issue has not been assessed yet.

Description

Why

"DIN" is already used by another project in our space: the Data Intelligence Network (formerly Web3Go), an AI/data blockchain on the OP stack whose DIN token is listed on KuCoin. Sharing the name and ticker risks search confusion, credibility issues, and people buying the wrong token at our fair launch.

Nothing is on mainnet yet and the public testnet hasn't launched, so this is the cheapest moment to change.

Proposal

Today Proposed
Token "DIN Token" / ticker DIN "InfiniteZero" / ticker INZ
CLI dincli inz (keep dincli as a deprecated alias for one release cycle)
Public name "DIN" Lead with InfiniteZero (open question: keep "Decentralized Intelligence Network" as the descriptive protocol name?)

INF was considered and rejected: it's already a listed ticker (Sanctum Infinity), and "inf" means infinity in most programming languages.

Suggested phases

  1. Agree names in this issue.
  2. Token: update the name and symbol in DinToken.sol (__ERC20_init), plus tests and deploy docs, before the public testnet.
  3. CLI: rename the dincli command and package to inz, with dincli kept as an alias that prints a deprecation notice. Update docs.
  4. Docs and READMEs: replace user-facing "DIN" with the new names.
  5. Optional, before mainnet: rename internal contract and module names (DinToken → InzToken, etc.). This is the largest change (DIN appears ~14k times across ~350 files) and is invisible to users, so it can be decided separately.

Before we commit

  • Check inz / inzcli are free on PyPI.
  • Re-check that INZ isn't an actively used ticker.

Thoughts welcome. If agreed, phases 2–4 can be split into separate issues, and some are good contributor tasks.

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.