# Understanding the "Shared Ledger" Concept

<figure><img src="/files/luN78q5F813Jqa5QIvvD" alt=""><figcaption></figcaption></figure>

### Traditional System = Individual Farm Notebooks

**You record:** "Harvested 5 tons of organic apples on October 15"\
**Distributor records:** "Received organic apples on October 16 (thinks it's 4.8 tons)"\
**Retailer records:** "Organic apples arrived October 18" (has no weight data)\
**Certifier has:** Paper certificate from 6 months ago\
**Consumer knows:** Only what label says

**When there's a dispute or recall:**

* Everyone has different records
* Meeting required to reconcile
* No one knows which version is "true"
* **Trust breaks down**

### Blockchain = Shared Farm Ledger

**October 15, 8:00 AM:** Harvest begins, **IoT scale** records weight → **Blockchain**\
**October 15, 5:00 PM:** 5.0 tons organic apples harvested, **GPS, temp** → **Blockchain**\
**October 16, 6:00 AM:** Distributor receives, **confirms 5.0 tons,** **signs** → **Blockchain**\
**October 18, 7:00 AM:** Retailer receives, **confirms condition, signs** → **Blockchain**\
**Ongoing:** **Temperature sensors** record storage conditions → **Blockchain**\
**Consumer:** **Scans QR code**, sees complete verified history

**When there's a question:**

* **One source of truth**, visible to all
* **Timestamped, signed, tamper-proof**
* No reconciliation needed
* **Trust is built-in**

#### Critical Difference

No one "owns" the ledger. It's not your system or the distributor's system. **It's a shared layer that everyone can see and trust, but no single party controls**.

This is fundamentally different from:

* **Centralized databases** (one company controls everything)
* **Private blockchain** (limited participants, one entity sets rules)
* **Government databases** (subject to political changes)

The power is in the **sharing and verification**, not in centralization.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/the-business-case-for-blockchain-in-agriculture/what-blockchain-actually-does-for-farmers-and-agribusiness/understanding-the-shared-ledger-concept.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.