Full lesson

gree

Legal Contracts on Web3

What it does

From the project README:

You can use any normal anchor commands. Either move to the `anchor` directory and run the `anchor` command or prefix the command with `npm run`, eg: `npm run anchor`.

Original

asimnecip/gree

SuperStack fork

Blockchains/gree @ 7ef8c89

Stars

0

Last push (original)

2024-03-27

Languages

TypeScript, Rust, JavaScript, CSS, HTML

Detected stack

AnchorMetaplexweb3.js

Categories

Other

Licence

MIT

Architecture

29 source files. By extension: .tsx ×17, .ts ×7, .js ×4, .rs ×1.

On-chain programs: anchor/programs/gree

✅ Operational, verified 2026-11-02 Tested on 2026-11-02: full log results.json

Build it yourself: step-by-step guide

Every command below was run on 2026-11-02 by tests/run_fork.py against the pinned commit, and the results come from that run. The full output is in the committed log.

1. Prerequisites (versions we tested with)

• Rust: rustc 1.99.1 (58cf8f9c3 2026-10-13)
• Solana CLI (Agave): solana-cli 1.18.17 (src:c027cfc3; feat:4215500110, client:Agave)
• Anchor (via avm): 0.29.0
• Node.js: v24.22.1
• npm: 11.21.1
• pnpm: 10.34.6

cargo install --git https://github.com/coral-xyz/anchor avm --locked
avm install 0.29.0 && avm use 0.29.0
sh -c "$(curl -sSfL https://release.anza.xyz/stable/install)"

2. Clone at the tested commit

git clone https://github.com/Blockchains/gree.git && cd gree
git checkout 7ef8c89e9b317f2f7f664588b1c58aaac7b816dd

3. Configure

No environment file is needed.

4. Install dependencies

5. Build

6. Test

7. Deploy to a local validator

solana-test-validator --reset   # separate terminal
solana config set -ul && solana airdrop 100
anchor deploy --provider.cluster localnet

Proof: program IDs and transactions

• gree: CZzz3hZ7P6KcvHJ6yPpCg2hGstTtcrYw6KGLqvvrd9vK (local validator)

Transaction signatures recorded on the local validator (1 shown). Local ledgers are thrown away after the run, so these work as receipts in the log and can't be looked up on an explorer:

• gree 338dVtyAKZfrQYfZdino…CRQPW6t1

Deploy to devnet (free)

solana config set --url devnet
solana airdrop 2   # or https://faucet.solana.com
anchor deploy --provider.cluster devnet   # native: solana program deploy target/deploy/<name>.so
# point the frontend RPC env var at https://api.devnet.solana.com

Extend it

1. Add an integration test that runs the main flow end to end and asserts every account state change.
2. Add a negative test: call each instruction with the wrong signer or account and check that it fails.
3. Make the frontend read the cluster from an env var, deploy it to GitHub Pages and point it at your devnet program.
4. Wire the build into CI by copying this site's verify-forks workflow.

Key code, explained

Excerpts chosen automatically where the code uses the most Solana concepts, pinned to the fork's commit.

    pub system_program: Program<'info, System>,    pub rent: Sysvar<'info, Rent>,    #[account(        init_if_needed,        payer = signer,        associated_token::mint = mint,        associated_token::authority = signer    )]    pub associated_token_account: Account<'info, TokenAccount>,        /// CHECK:    #[account(        mut,        seeds = [            b"metadata".as_ref(),            token_metadata_program.key().as_ref(),            mint.key().as_ref(),        ],        bump,        seeds::program = token_metadata_program.key()    )]    pub metadata_account: UncheckedAccount<'info>,     /// CHECK:

How to run, build and test

These commands come from the repo's own manifests (package.json scripts, Anchor.toml, Cargo, go.mod, Makefile). Check the README for prerequisites and environment variables.

What you could build from it

• Fork the SuperStack copy and extend it within the Other gaps listed on the idea page.
• Learn the pattern first: Program Derived Addresses (PDAs)
• Learn the pattern first: Cross-Program Invocations (CPIs)