The original marijuana cryptocurrency
Preserving the public history, software, and community legacy of the CANN cryptocurrency project launched in 2014.
This site preserves legacy material for educational and historical reference. It does not represent current development, financial advice, or an active offering.
About the project
CannabisCoin was publicly announced in June 2014 as an open-source, peer-to-peer proof-of-work cryptocurrency using the trade symbol CANN. Its early community described the project as community-run and promoted it for cannabis-related commerce.
This archive distinguishes historical project claims from independently verified facts. It is intentionally built without WordPress, PHP, plugins, or a database so the record can remain portable, secure, and easy to mirror.
Project history
Public launch period
Early announcement threads described CANN as an X11 proof-of-work coin intended for cannabis-community transactions. The main public discussion thread dates to June 23, 2014.
CANNdy campaign
Historical posts promoted cannabis products and strains under the CANNdy name. This was a project marketing claim, not a guaranteed redemption or present-day offer.
Archived web presence
A May 31, 2023 capture preserves the former site’s public appearance and provides a primary visual reference for this reconstruction.
Preservation project
Public records, surviving files, archived imagery, and historical context are being organized into portable HTML, CSS, JavaScript, and verified downloads.
Historical technology
These details are preserved as historical project information. Current network availability and compatibility have not yet been independently verified.
The project was publicly presented as a mineable peer-to-peer cryptocurrency.
Early announcements identified X11 as the hashing algorithm used by CANN.
The CANN ticker appeared throughout the original public website and discussions.
Wallets, explorers, and network services will be clearly labeled by current status.
Software archive
Files will be published only after they are identified, scanned, and accompanied by checksums and clear legacy-software warnings.
These files are preserved exactly as recovered and have not been executed or security-audited. Use an isolated virtual machine, verify the SHA-256 hash, and never reuse production credentials or a valuable wallet.
Desktop wallet
Recovered Windows installer · 9,473,000 bytes
10261272…ada480a
Download legacy EXE
Desktop wallet
Recovered disk image · 16,012,547 bytes
bb4032a0…fb5eea
Download legacy DMG
Mobile wallet
Recovered Android package · 4,636,409 bytes
192f04de…0ba58e
Download legacy APK
Configuration
Sanitized configuration preserving historical seed names without old RPC credentials.
Download config example View all SHA-256 hashesDigital museum
Archived captures showing the project’s visual evolution.
Recovered news, project updates, and community statements.
Verified legacy packages with hashes, dates, and warnings.
04
Recovered coin artwork and CannabisCoin wordmarks preserved from the legacy server.
Wayback snapshots, source repositories, and blockchain records.
Resources
Archive methodology
Primary sources include surviving server files, archived website captures, original public announcement threads, and historical software packages.
Claims made by the original project are labeled as historical claims. Current network, market, download, and explorer status will be dated and linked to third-party sources whenever possible.
Project preservation
This archive requires no login, content-management system, database, server-side runtime, or plugin ecosystem.
FAQ
This website is an archival preservation project. It does not claim that the original network, development team, exchanges, or services are currently active.
Historical software can be obsolete or unsafe. Downloads will not be published until provenance, file hashes, and appropriate warnings are documented.
No. The site is for historical and educational reference only and does not recommend buying, selling, mining, or using any cryptocurrency.
The original theme configuration was lost. A static archive is faster, safer, easier to preserve, and does not depend on a database, plugins, or server-side code.