RELEASE AND TERMS 2 MIN READ
Cannabis mainnet release
The canonical release package and deployment requirements.
Cannabis is preparing a production mainnet launch with efficient verified-person claims, zero-knowledge eligibility privacy, and 1% founder vesting over 24 calendar months.
The preparation command checks reviewed dependency pins against finalized and current canonical chain state, then exports unsigned deployment data, constructor arguments, exact dates, allocations, dependency observations, ABI and complete compiler input. It does not load a key or broadcast a transaction. See dependency verification for the source checks, configuration format and evidence limits.
npm run prepare:launch -- --founder YOUR_PUBLIC_ADDRESS --launch YYYY-MM-DDTHH:MM:SSZ --network base --semaphore VERIFIED_SEMAPHORE_ADDRESS --registrar REVIEWED_REGISTRAR_ADDRESS --semaphore-code-hash VERIFIED_RUNTIME_CODE_HASH --dependency-config config/base-dependencies.json --out ../private/launch-review
Ethereum, Base and Arbitrum One are candidate EVM networks. Their actual deployment/version compatibility, cost and operational assumptions must be checked before selecting one. The supplied config/ethereum-dependencies.json and config/base-dependencies.json record observed, source-reproduced dependencies; they do not select the launch network or approve a release. For Ethereum, use --network ethereum with its matching dependency configuration. Another network requires its own reviewed configuration. The unsigned package is a draft until independently reviewed. The tool requires seven days' opening notice and concrete provider/dependency details.
After preparation, use the read-only deployment fee checker against the exact reviewed creation-data hash. It accounts for the selected chain's fee model, including Base's separate L1 and operator fees. The estimate covers one creation transaction; the full release and operating budget includes additional costs.
The constructor creates immutable founder vesting and an append-only enrollment controller. The new token's group is not automatically populated; real eligibility enrollment is a separate release requirement. Claims require at least 128 commitments and one proof per enrolled identity.
Before signing, check chain ID, complete creation-data hash, founder address, dates, Semaphore implementation/verifier, registrar controls and expected fee. After deployment, verify source and constructor values on the explorer, publish canonical addresses, validate the founder allocation, and test real provider enrollment and claims.
Earlier proof-of-work packages are superseded and must not be deployed.