This organization is an independent community archive, rebuild, and public record effort related to Kishu Inu.

This is not an official continuation of the original Kishu Inu project unless the original contract, wallet, account, and deployment authority is publicly transferred or delegated.

• My Work

I do not control the original KISHU token contract, legacy deployer wallets, owner Safe, NFT collection owner wallets, or former team accounts.

This work is an opt-in transparency and rebuild effort for community members, holders, and NFT buyers who want a clearer record of what exists today, what was promised historically, what was actually deployed, and what would need to be rebuilt correctly.

• A public archive of recovered project materials, interfaces, contracts, and deployment notes.
• A research effort to map known contracts, wallets, repositories, domains, NFT collections, and public claims.
• A place to document what can be verified from public records.
• A rebuild workspace for community-owned tools, only where they can be built safely and transparently.

Without control of the original wallets and contracts, this organization cannot safely:

• Change the original KISHU contract.
• Control the KISHU owner Safe.
• Move, repair, or upgrade legacy staking contracts.
• Force a migration.
• Update old NFT contracts or collections.
• Claim to be the official continuation of Kishu Inu.
• Promise that historical losses will be recovered or made whole.

The current Kishu Community recovery work covers the domains, GitHub organization, recovered frontend code, public documentation, and public materials that can be accessed and maintained through the current rebuild.

This rebuild does not control the original KISHU token contract, owner Safe, legacy team wallets, unavailable legacy team accounts, or private messages on legacy social accounts.

The X account @InuKishu is still active through a separate legacy/community account operator. Some public profile assets and limited public posts have been updated where access was available, but private messages to that account are not accessible to the current rebuild maintainer and should not be treated as official support for this recovery effort.

For current public communication, use the homepage, GitHub organization, and Telegram links listed in this README and on kishu.finance.

• Current rebuild GitHub organization: github.com/Kishu-Community
• Current rebuild homepage: kishu.finance
• Original KISHU Ethereum token contract: 0xa2b4c0af19cc16a6cfacce81f192b024d625817d

This organization will never ask for a seed phrase, private key, recovery phrase, wallet file, remote desktop session, or payment to "verify" a wallet.

There is no active token migration, refund, recovery claim, wallet verification, or airdrop from this organization unless it is documented in this GitHub organization and verifiable from public sources.

Public GitHub repositories can be forked or copied by anyone. A fork, clone, issue comment, pull request, website, or repo with similar branding is not part of this rebuild unless it is linked from this organization or the current rebuild homepage.

• Token: Kishu Inu (KISHU)
• Network: Ethereum Mainnet
• Standard: ERC-20
• Contract: 0xa2b4c0af19cc16a6cfacce81f192b024d625817d
• Decimals: 9
• Max total supply: 100,000,000,000,000,000 KISHU

Use Etherscan for live holder counts, transfers, market data, verified contract details, and token tracker information. Mutable market stats are not hardcoded here because they change over time.

• Website rebuild preview: kishu.finance

This deployment is being used to make the website recovery process visible while older public frontend code, recovered assets, and project notes are reviewed.

It should be treated as work in progress until domains, repos, deployment ownership, contracts, and public documentation are fully aligned.

• Original Kishu Inu whitepaper PDF
• Whitepaper archive notes and errata

The original whitepaper PDF is preserved unchanged as a historical artifact. It may contain old domains, older social links, typos, roadmap claims, and product claims from the original project era.

Those historical claims should not be treated as active promises unless a current repo, deployment, contract, and public maintenance record verifies them.

Several original whitepaper ecosystem items are being treated as historical, abandoned, incomplete, or unverified until proven current:

The Kishu Inu Foundation charity work is listed separately because it was part of the historical team/project record. Kishu Crate, Kishuverse, Kishu Kingdom, Kishu Paw Print, and Kishu sWAG are being documented as ecosystem or community project records unless public evidence proves a different control structure.

Supporting recovered repositories:

• Kishu Inu Pay
• Kishu Wallet Connect
• Social media posts and safety references

Recovered repos and redeployments should clearly explain:

• What the old project claimed.
• What the recovered code actually does.
• Which contracts or wallets are involved.
• Who controls those contracts or wallets, if known.
• What is broken, missing, abandoned, or unverifiable.
• What would need to be rebuilt, retired, or replaced.

• No private deals.
• No hidden teams.
• No special access.
• No vague promises.
• No hype without proof.
• No custody of critical systems without public accountability.
• No claims of control that cannot be verified.

Outside help may be accepted through issues, documentation, review, or pull requests, but no one is handed trust by default.

If you want to help, bring useful work, clear evidence, and patience.

The goal is not to rewrite the past.

The goal is to preserve the record, separate facts from claims, and rebuild only what can be rebuilt honestly.

Trust should be earned in public.