This repository houses public contract source files, contract references, and plain-English breakdowns for Kishu Inu and related project contracts.
The goal is to make it easier for community members to inspect what a contract is, where it is deployed, what controls exist, what public records verify, and what risks or limits should be understood before anyone treats a contract as current or official.
Each contract folder should include, where available:
- Verified source code or recovered source files.
- License or source metadata.
- Contract address and network.
- Block explorer links.
- Known owner/admin/control addresses.
- A plain-English breakdown of important functions.
- Notes about what the contract can and cannot do.
- Safety notes for holders, NFT buyers, and community reviewers.
This repository is an archive and research workspace. It is not, by itself, proof of control over any deployed contract.
- Kishu Inu ETH Token - Original KISHU ERC-20 token on Ethereum Mainnet.
- NFT Collections - NFT collection contracts associated with Kishu-branded project history, including Ethereum and Polygon collections.
Important distinction: most NFT collection contracts in this repository do not directly integrate with the original KISHU ERC-20 token contract. A Kishu-branded NFT collection can use Kishu names, symbols, art, websites, or social claims without requiring, staking, burning, rewarding, or reading the KISHU token contract on-chain.
Always verify deployed contracts directly on the relevant block explorer before connecting a wallet, approving a transaction, or trusting a migration/recovery claim.
This repository will never ask for a seed phrase, private key, recovery phrase, wallet file, remote desktop session, or payment to "verify" a wallet.
Unless a migration, refund, recovery claim, wallet verification flow, or airdrop is documented publicly and verifiable from on-chain records, treat it as suspicious.