All source, published

BscScan checkmarks: 6 / 6, and all six are also full matches on Sourcify (bytecode plus metadata, checked both ways). If you trust neither, compile it yourself and compare.

Contracts

Three places to check

• Sourcify (third party, recommended): lookup page — full match with sources and metadata
• Source bundle: bnbfarm-contracts.tar.gz (19 KB, every .sol plus foundry.toml and build notes)
• BscScan: ✅ all six verified — click an address in the table to read the source on BscScan

Compile it yourself

# 1. unpack
tar xzf bnbfarm-contracts.tar.gz && cd .

# 2. build (solc 0.8.26, via_ir = true, optimizer runs = 200)
forge build

# 3. compare with on-chain bytecode
cast code 0x94308A3B78C3Aa4f9376cE2093c1F770C74AB2C7 --rpc-url https://bsc-dataseed.binance.org

# 4. or let forge verify it for you
forge verify-contract 0x94308A3B78C3Aa4f9376cE2093c1F770C74AB2C7 \
  src/v2/FarmAnimal.sol:FarmAnimal --verifier sourcify --chain 56 --watch

Why Sourcify's match is worth more than a checkmark

BscScan's checkmark proves the source compiles to the same bytecode. Sourcify's full match additionally compares metadata and constructor arguments. Both is best; if only one, Sourcify carries more information.

Bytecode fingerprints (trust nobody)

The checkmark means one independent party (BscScan) compared it. If you do not trust them either, here is the raw evidence — the keccak256 of the on-chain runtime code, which you can compute yourself:

# compute it yourself and compare
cast keccak $(cast code <address> --rpc-url https://bsc-dataseed.binance.org)

# or from a local build
forge build && cast keccak $(jq -r .deployedBytecode.object out/<file>.sol/<Contract>.json)