SAFETY FIRST
Security and privacy
The website is intentionally static. Your node, wallet, and release verification deserve the same simplicity and care.
Software provenance
Install from the project's canonical GitHub repository and confirm you selected the intended tagged release. Compare downloaded binaries against independently authenticated hashes and signatures if these are published. A GitHub signed-commit indicator alone does not authenticate release binaries.
Never share wallet secrets
This site does not request seed phrases, private keys, wallet files, passwords, browser-wallet connections, or personal details. Treat any website asking for those as unsafe.
Do not mix blockchains
BitcoinII (BC2) and Bitcoin (BTC) are distinct networks. Address similarities do not make transactions cross-chain compatible. Be deliberate about which wallet and network are active before sending funds.
Keep node administration isolated
Block or restrict management RPC ports. Update your software carefully and review consensus-critical release notes. Maintain tested backups and avoid storing secret credentials in publicly served directories.
Site privacy
These pages load no third-party fonts, trackers, or client-side libraries, and use no cookies. A small local JavaScript file controls the optional light/dark switch and stores your selected theme in this browser only; no setting is sent to the server. With JavaScript disabled, the site automatically follows your system color preference. The web server may still retain standard request logs, depending on deployment configuration; a static website is not a promise of anonymous access.
Report software issues
Use the project's GitHub issue tracker for non-sensitive reports. Do not publish working exploits, credentials, or private wallet data in public issues.