Community claims

The proposed production rules reserve 99% of Cannabis for up to 990,000 eligible people: one claim of 420 Cannabis per verified person, starting at the common public opening. Production enrollment awaits a reviewed provider and verified deployment.

The selected enrollment direction is non-biometric person verification. We are evaluating social/personhood verification without iris or face scans, with one-person allocation and recovery protections. A provider has not yet been selected; the website does not collect identity documents or biometric information.

The provider integration checker validates BrightID signed eligibility records, binds them to the intended deployment and identity commitment, and maintains an idempotent private intake registry. Provider lifetime uniqueness, recovery and production enrollment still require review; signature verification alone does not authorize membership.

1. Generate and securely back up a private Semaphore identity on your device. The local identity and proof CLI provides encrypted custody and a recovery check. The identity secret must never be sent to the enrollment service, Cannabis, a chat or a public repository.
2. Complete the approved provider's person-verification process. Submit only the identity commitment for group enrollment. The provider must enforce one identity per person and a recovery policy that prevents repeat claims.
3. Retrieve the complete public membership snapshot using the checked whole-group downloader. Generate a Semaphore proof locally with the receiving wallet address as its message and the deployed token's claimScope as its scope. Use the matching pinned Semaphore libraries and reviewed proving artifacts. Do not include the identity commitment or secret in the public claim file.
4. Validate the proof against the canonical deployment and prepare an unsigned transaction:

node scripts/prepare-claim.mjs --rpc HTTPS_RPC_URL --chain-id CHAIN_ID --token VERIFIED_TOKEN_ADDRESS --recipient YOUR_RECEIVING_ADDRESS --code-hash VERIFIED_TOKEN_RUNTIME_HASH --proof proof.json --out claim-transaction.json

5. Review the chain, contract, recipient and decoded claim in your wallet. Simulate again immediately before signing. A relayer can submit the same proof for the same recipient; it cannot redirect the reward. Network fees apply.

The preparation tool reads no wallet key and broadcasts nothing. A group-root update can require regenerating a proof. A failed transaction can still consume gas. The 128-commitment threshold and proof cryptography do not replace trustworthy human verification.

See privacy and security for public-ledger and metadata limits. The enrollment portal, reviewed graphical identity flow, authenticated membership distribution and production relayer remain release work; the current website does not collect identity information or pretend to verify humans.