Clear project scope
Start with the protocol page if you want the high-level explanation before using any public service.
Independent blockchain protocol project
Chipcoin currently exposes a live public testnet with a full node, external miner, browser wallet, snapshot bootstrap path, explorer, and a native on-chain Node Rewards system for verified nodes. Chipcoin's core public claim is that it is building the first native decentralized PoW protocol that also pays verified nodes, not only miners.
Start with the protocol page if you want the high-level explanation before using any public service.
Chipcoin keeps PoW mining, but also pays verified nodes through deterministic on-chain registration, renewal, attestation, and settlement.
Trusted snapshot import reduces bootstrap time for new public-network nodes and recovery paths.
The docs page summarizes the current public services and operational boundaries.
What Chipcoin Is
Chipcoin is a protocol project with a live testnet stack, not a placeholder shell. The public site should describe what is already running and how the visible services fit together.
The current live state includes a full node, external miner, browser wallet, snapshot bootstrap, explorer access, and a native Node Rewards system that is operating on the public testnet.
What Is Live Now
The public site should reflect the real stack that is already live today, especially the reward-node system and the faster node bootstrap path.
High-level explanation of the project, the current testnet scope, and how the visible services fit together.
Read ProtocolPublic explanation of Chipcoin's verified-node reward model, epoch settlement path, and current testnet parameters.
Open Node RewardsA short public paper covering the monetary model, testnet stack, snapshot bootstrap path, and why Chipcoin is not miner-only.
Read WhitepaperSee how the full node, miner, wallet, explorer/API, snapshot bootstrap, and reward-node loop fit together.
Open ArchitectureStart with the wallet overview, then move to the browser wallet instructions when you are ready to install.
Open WalletRequest testnet CHC and then verify the result in the explorer or inside your wallet.
Open FaucetReview the current public services, reward-node flow, snapshot bootstrap path, and setup boundaries in one technical reference page.
Open DocsSee current public node count, latest blocks, and recent settled reward epochs pulled from the live API.
Open Live TestnetChrome and Firefox installation guidance lives on its own page so setup steps stay separate from the wallet overview.
Browser WalletThe explorer is available as an external service for checking addresses, transactions, and test activity.
Open ExplorerGet Started
Read the protocol page first if you want the shortest explanation of the live testnet stack and public services.
Go to ProtocolRead the Node Rewards page if you want the clearest explanation of what makes Chipcoin different from a miner-only PoW model.
Go to Node RewardsUse the brief whitepaper when you want the concise protocol summary before moving into deeper docs.
Read WhitepaperUse the wallet overview if your next step is creating a wallet and preparing an address for faucet testing.
Go to WalletGo straight to the browser wallet page if you already know you want the Chrome or Firefox extension instructions.
Install Browser WalletUse the faucet after you have a valid CHC address and want to test receiving and transaction visibility on testnet.
Go to FaucetUse the explorer after wallet or faucet actions to confirm that the visible public data matches your test flow.
Open ExplorerOpen the docs if you want a more operational view of the current public services, snapshot bootstrap, and reward-node flow.
Go to DocsUse the live testnet page to inspect public node and reward signals before digging into the explorer.
Open Live TestnetCurrent Public Services
Protocol for orientation, Node Rewards for the key protocol novelty, Whitepaper for the short paper, Architecture for component boundaries, Live Testnet for public chain signals, wallet for the user path, browser wallet for install steps, faucet for testnet testing, docs for technical reference, and explorer for external verification.