Cannabis

Grow like nature. Power what’s next.

Cannabis is a production cryptocurrency project built around efficient community participation and privacy-preserving eligibility. Status: preparing mainnet launch. Explore Cannabis.

Money for useful computing. The economic objective is real service demand: people pay in Cannabis for accepted computing work, while providers publish capacity and enforceable redemption terms. Read the compute economy and backing requirements. Service backing becomes operational only when defined provider commitments can actually be redeemed and fulfilled.

The contracts define a fixed supply cap and one-time verified-person community claims with a common public opening. Read the allocation, vesting and service terms before participating.

There is no proof-of-work. The selected architecture uses Ethereum proof-of-stake settlement through an EVM network. Semaphore zero-knowledge proofs omit the claiming identity from the proof, while the recipient wallet and transaction remain public. Enrollment is append-only; the initial claim minimum is configurable and defaults to one genuinely verified member, with claims available after the common opening. The founder can raise the minimum only up to the already enrolled count, preserving existing eligibility. There is no recruitment quota for deployment. A singleton group cannot hide who claimed; small groups provide limited privacy. Cannabis-run synchronized in-person verification must establish one commitment per distinct person; no external identity provider is required.

Put compute to work. The general-purpose client packages arbitrary software through extensible runtime adapters, compares node quotes, plans task graphs and coordinated groups, and reconstructs encrypted output shards on the requester. Python, VM checkpoints and distributed model training are examples of the broader format. Target hardware includes NVIDIA/CUDA, AMD/ROCm, CPU and other accelerators. Job quotes disclose the included service fee and total before payment; see the service terms. Work stays off-chain and does not mint tokens or decide consensus. See the universal client, useful-compute design and escrow payment rules. The protected worker service and mainnet payments still require integration and review.

Customer jobs require encrypted code/data and attested confidential execution. Keys must stay out of worker operators' hands, with no fallback to unprotected hardware. See the confidential-compute requirements. Runtime compatibility alone does not establish private execution; the protected worker and key-release service are release work.

Run the website

Requires Node.js 22.22+ and npm.

npm ci
npm run dev

Open http://127.0.0.1:4200. This serves the public Cannabis website.

Open the worker console

The worker console shows actual local machine activity and admission requirements. Open Start-Cannabis-Worker.cmd on Windows, or run npm run worker:console and visit http://127.0.0.1:4201/. This release does not accept paid jobs or mine tokens.

Verify the contracts

npm test

The suite checks real zero-knowledge proofs, replay and recipient-substitution attacks, enrollment permissions, first-member claims, configurable thresholds, bounded owner increases and current-root checks, fixed supply and founder vesting on isolated ephemeral chains. Compute integration checks also require Python 3.12+ and age 1.3.2 with age-keygen; put them on PATH or set CANNABIS_PYTHON and CANNABIS_AGE to their executable paths. CI installs and verifies these tools. Production releases require independent security and privacy review.

Project material

• Windows guided participant setup
• Token rules and architecture
• Privacy and security design
• Efficient-network approach
• Community claim workflow
• Cannabis ceremonies and witness approval
• Encrypted participant identity and offline proofs
• Complete membership download and chain-state checks
• Mainnet release preparation
• Deployment fee estimates and budget scope
• Launch acceptance criteria
• Participation risks
• Launch review
• Campaign copy
• Ready-to-share graphics
• English narrated films
• General-purpose workload packaging and result reconstruction
• Compute escrow and transparent pricing
• Small jobs, exact fees and reproducible integration checks
• Signed capacity commitments and reservation controls
• Trustee attestation checks and single-use challenges
• Per-job encryption keys and requester recovery
• Requester-approved encrypted key delivery
• Guest-held channels and hardware-evidence integration
• Guest workload decoding and assignment verification

Ethereum mainnet is the selected preparation target. The Cannabis ceremony, witness roster, registrar, independent review and verified deployment remain release work. Canonical addresses and the opening time will be published with the verified release. Cannabis is an independent project, unaffiliated with other cannabis-themed currencies.