How SBI Verification Works
A technical overview of the cryptographic provenance system that authenticates every genetic transfer on Seed Bank International.
The Verification Gap
Cannabis genetics is a multi-billion dollar industry with zero authentication infrastructure. When a buyer purchases seeds labeled “Girl Scout Cookies,” there is no way to verify whether the genetics are genuine. No certificate of origin. No chain of custody. No cryptographic proof.
SBI solves this by generating a unique SHA-256 provenance certificate for every genetic transfer on the platform.
SHA-256: The Cryptographic Foundation
Every certificate is anchored by a SHA-256 hash — the same algorithm that secures Bitcoin transactions and SSL/TLS connections worldwide.
strain: “Grape Stomper”
breeder: “Gage Green”
buyer_id: “usr_9f3a...”
timestamp: 1709164800
7a3f9c2e4b1d8f6e
2a5c9d1b3e7f4a8c
6d2e9f5a1b8c3d7e
4f6a2c8e1d3b5f9a
Deterministic
The same input always produces the same output. A certificate can be re-verified at any time by re-hashing the original data.
Irreversible
You cannot derive the original data from the hash. The certificate proves a transaction occurred without exposing private details.
Avalanche Effect
Changing a single character in the input produces a completely different hash. Even minor tampering is immediately detectable.
Collision Resistant
It is computationally infeasible to find two different inputs that produce the same hash. Each certificate is guaranteed unique.
Certificate Lifecycle
From breeder registration to verifiable certificate in four automated steps.
Registration
A breeder submits strain data — name, lineage, phenotype, generation. The system records the submission with a timestamp and assigns a unique node ID in the genetic registry.
Transaction
When a sale occurs, the platform captures buyer, seller, strain, quantity, and price. This creates the raw inputs for the certificate.
Hash Generation
A SHA-256 hash is computed over the transaction data, producing a unique 64-character hexadecimal fingerprint. Any alteration to the inputs would produce a completely different hash.
Certificate Minting
The hash, metadata, and QR verification link are assembled into a provenance certificate. It is stored in the database and accessible via a permanent URL.
The Trust Problem
“How do you know the data going into the system is accurate?” — This is the fundamental challenge of any verification system. SBI addresses it with a layered trust stack.
Breeder Identity
Breeders undergo identity verification at the Seed and Growth tiers. Verified badges are issued only after manual review. This establishes the human anchor — someone accountable for the genetic claim.
Batch Tracking
Each seed lot is tracked from registration through sale. Batch IDs link individual certificates to specific production runs, creating an audit trail from breeder to buyer.
Community Verification
Buyers leave reviews, grow journals, and photos. Over time, a strain accumulates social proof — phenotype reports, terpene profiles, and yield data that either corroborate or contradict the breeder's claims.
Lab Testing
When available, third-party lab results (cannabinoid profiles, terpene analysis, contaminant screening) can be attached to certificates. This is the highest-confidence layer and the eventual standard.
Certificate Data Model
The provenance_certificates table schema.
| Field | Type | Description |
|---|---|---|
| cert_id | TEXT | Unique certificate identifier (e.g., SBI-7a3f9c2e4b1d) |
| hash | TEXT | SHA-256 hash of the transaction data |
| strain_name | TEXT | Registered strain name |
| breeder_name | TEXT | Verified breeder identity |
| buyer_id | UUID | Buyer account reference |
| lineage_mother | TEXT | Mother strain (if known) |
| lineage_father | TEXT | Father strain (if known) |
| generation | TEXT | Genetic generation (F1, F2, S1, etc.) |
| tier | TEXT | Breeder tier at time of issuance |
| is_valid | BOOLEAN | Whether the certificate is currently valid |
| on_chain_tx | TEXT | Blockchain transaction hash (reserved, nullable) |
| on_chain_network | TEXT | Blockchain network identifier (reserved, nullable) |
| created_at | TIMESTAMPTZ | Certificate issuance timestamp |
| verification_url | TEXT | Public verification URL with QR code |
Blockchain-Ready,
Not Blockchain-Dependent
The certificate schema includes on_chain_tx and on_chain_network fields — currently nullable, reserved for future blockchain anchoring.
This is intentional. Blockchain adds immutability guarantees but introduces wallet friction, gas costs, and onboarding complexity. SBI delivers the core value — cryptographic verification — without requiring users to understand or interact with blockchain technology.
When the economics and UX of on-chain anchoring make sense for our users, the infrastructure is already in place.
SHA-256 Certificate
Server-generated, database-stored, QR-verifiable provenance certificates for every transaction.
IPFS Anchoring
Optional pinning of certificate hashes to IPFS for decentralized availability.
On-Chain Notarization
Batch-anchoring certificate Merkle roots to a public blockchain for immutable timestamping.
Frequently Asked Questions
Every Seed, Verified.
Explore the protocol in action — verify a live certificate, read the platform charter, or start selling with cryptographic provenance.