Technical
For readers unfamiliar with blockchain or AI — plain language answers to technical questions.
Section 1 — How the Technology Works
For readers unfamiliar with blockchain or AI — plain language answers to technical questions.
Q: How does Bio-ID work if the fruit's skin changes over time — ripening, bruising, storage?
Bio-ID is extracted from the fruit's structural skin texture — the pattern of surface cells, ridges, and morphological features unique to each individual fruit. These features are stable across the growth cycle from green to ripe. The system captures a composite fingerprint from 5–10 angles, providing redundancy against surface variations. The M1 benchmark specifically tests temporal consistency — the same fruit must be re-identified after 30 days — and requires a pass before any further deployment.
Q: Three figures appear across the GA — 12,000 tx, 600,000 events, and 1,200,000 events/year. Are they contradictory?
No. They answer three different questions:
~12,000 tx — What is the minimum number of L1 transactions to record 180M fruit Bio-IDs? One VeData anchor per farm per harvest season, each covering all 15,000 fruits in a single batch. This is the theoretical cost floor used in the efficiency comparison.
~600,000 events → ~6,000–7,500 actual L1 batch transactions — How active is VeData in practice? VeData runs weekly per farm during growing season, anchoring cultivation logs, input records, and harvest events. 12,000 farms × ~50 cycles/year = 600,000 anchor events; each L1 batch covers 80–100 farms.
~1,200,000 events/year — What is the total ecosystem footprint? All four activity categories combined: VeData + labor contracts + commercial escrow + one-time setup.
All three are accurate. They measure different things. Full reconciliation: Annex A, Section 6.
Q: Why is the per-NFT update cost ~0.0089 ADA when Cardano's base fee is ~0.17 ADA?
The ~0.17 ADA base fee applies to simple ADA transfers with no smart contract. VeData batches 100 Farm NFT updates into one Plutus transaction using a reference script — total ~0.83 ADA for 100 NFTs. Per-NFT cost = ~0.0089 ADA, a 98% reduction versus single-NFT updates (~0.25–0.42 ADA each). The comparison is per-NFT, not per-transaction.
Q: Are labor contracts and commercial transactions recorded on-chain directly, or inside the Merkle Root?
Directly on-chain as individual Plutus L1 transactions. Labor contracts and commercial escrow require independent on-chain enforceability — a Merkle proof alone is not sufficient to enforce a payment obligation. VeData's Merkle Root covers cultivation logs and Bio-ID updates only.
Q: Does the 1,200,000 events/year figure include Hydra (L2)?
L1 only. All ~1,200,000 events/year settle on Cardano Mainnet L1. Path B (Hydra audit decommits) adds ~2,190 additional L1 transactions/year — already separated in the activity breakdown table with its own row. Hydra is used only for the audit proof trail, not for NFT datum updates or any user-facing function.
Q: Does the M3 demo "10,000 updates → 1 tx" contradict M7's "≥100,000 on-chain tx"?
No. M3 demonstrates VeData batching capability — 10,000 fruit state changes collapse into 1 Cardano transaction. M7's ≥100,000 threshold is the cumulative total across all four transaction types over 1–2 months of full deployment, not a single batch. See Annex A Section 6 for full reconciliation.
Q: How frequently is the Merkle Root anchored on-chain?
Path A batch trigger fires at 20-second timeout or when 100 NFTs are queued — whichever comes first. For PRIORITY_HIGH events (harvest capture, quality inspection): bypass timeout, submit immediately → Layer 2 confirmed in ~25–35 seconds.
Q: What is the peak transaction load on Cardano during M7?
100,000 events ÷ 30 days ÷ 86,400 seconds = ~0.039 events/second average. Peak burst ~0.12–0.20/s. Cardano capacity: ~10 tx/s. OriLife peak = <2% of Cardano throughput. No congestion risk.
Q: How are the 24,000 DID registrations counted?
They are part of the ~100,000 one-time setup events, spread across M4–M7. The minADA locks (~75,000 ADA) are created within these same setup transactions — not additional transactions.
Q: If LampNet goes down, is farm data lost?
No. LampNet is a distributed network of 100+ physical nodes — data is replicated across multiple nodes, not stored on any single server. Content is addressed by cryptographic hash (CID): if one node is offline, others serve the same content. Cardano stores the 32-byte Merkle root permanently on-chain — even if all LampNet nodes went offline simultaneously, the cryptographic proof of data authenticity remains verifiable forever. Farmers recover their identity and assets via MIT-licensed PhoenixKey recovery tools regardless of LampNet status.
Last updated
Was this helpful?