# \[OriLife × TonFarm] Identifying 180 Million Durians Without Physical Labels Main Govermance Action proposal to submit on gov.tools Mainnet proposal: [click here](https://tempo.vote/governance-action?governanceActionId=2f583d8efb7a01da81df432f561a5a9bb2f5749555cea3e19d5097a9bfb06b52%230) GA Reference: GS-ORILIFE-GA-01 GA Type: Treasury Withdrawal Submitted by: Nguyen Hung Son— DDC Holdings, Dak Lak Epoch: 629 Version: v5.10 final Update: April 24, 2026 Requested Amount: 2,400,000 ADA For Vietnamese: [OriLife GA (Vi)](https://docs.google.com/document/d/1bEbbX_L9Ht36TU6VJIddFO9zoTzt5figanETIRUq9wU/edit?tab=t.1s1ja7ygbmj1) *** ### ABSTRACT OriLife Alliance proposes 2,400,000 ADA from the Cardano Treasury to deploy OriLife across 12,000 hectares of durian in Đắk Lắk Province. This is not a research grant request, but it is a proof of concept works — fruit identification is live at orilife.io/en/demo, VeData batching is verified on Cardano Preprod, and farmers across 46 communes have been onboarded through two harvest seasons. The funding covers production deployment: hardening the PoC into audit, mainnet-ready infrastructure and scaling it across 12,000 hectares before the December 1, 2026 regulatory deadline. This is not a standalone app or a narrow protocol. OriLife is an open infrastructure layer that enables multiple businesses, startups, and developers to build their own applications on top of a shared foundation. In this GA, TonFarm (farm management) and Aladin (mass user experience for web3) are the first two integrated applications — both reading from a single source of truth on Cardano. Any enterprise can integrate via the OriLife SDK. What the Cardano Treasury funds: * 180 million durian fruits identified and traced via blockchain through each fruit's unique biological fingerprint — origin cannot be forged, no physical labels needed. * 24,000 new users (2 per household × 12,000 households) with self-sovereign digital identities on Cardano via PhoenixKey. * 12,000 CIP-68 Dynamic NFTs on Cardano Mainnet — each a permanent digital ledger for a 1-hectare farm. * \~1,000,000–1,200,000 on-chain events/year — real farming activity. Labor contracts and commercial escrow settle as individual Cardano transactions; cultivation logs and Bio-ID updates are batched by VeData (up to 15,000 fruits per transaction) before settlement. Full breakdown: Annex A, Section 6. * \~75,000 ADA permanently locked on-chain at M4 — immediate, verifiable, permanent value for the ecosystem. * First global deployment of Midnight ZK Proof in real agricultural trade. * Publicly released SDK enabling any developer or enterprise to build on OriLife infrastructure. Smart contracts and key recovery tools are MIT-licensed. The integration SDK is publicly documented — third parties build freely; API calls consume MAGIC credits to cover compute costs. Full licensing: Annex B, Section 12. * Consumer data visible in \~5 seconds — Cardano verification confirms within \~60 seconds, automatically. * Opportunity for Cardano to be officially adopted by a government — OriLife is a candidate for the list of 5 national strategic traceability platforms. Why OriLife costs less than alternatives: | Identification solution | Cost per ha per year | | -------------------------------- | -------------------------------------------- | | QR labels (cheapest) | \~$300 ($0.02–$0.04 × 15,000 fruits) | | RFID / NFC tags | $1,500–$8,700 ($0.10–$0.58 × 15,000 fruits) | | OriLife Bio-ID | \~$200 (no physical labels, no consumables) | | — of which: Cardano network fees | \~$10 (paid by users via MAGIC, not this GA) | Source: CropTex field data; QĐ 3763/QĐ-UBND Đắk Lắk 19/12/2019; industry standard label pricing. \*MAGIC is an internal service credit for platform fees — not a tradeable token. See: Sustainability section. The platform serves solely as a neutral infrastructure layer, facilitating the direct exchange of utility credits between users. Total farming operational cost for 1 ha durian: \~$5,000–8,500 USD/year. OriLife traceability = 2–4% of that — the cheapest, most fraud-proof option on the market. Who pays what: All on-chain transaction fees (labor contracts, commercial settlements, VeData anchors, Hydra audit) are paid by users via MAGIC credits — converted from local fiat currency through standard payment gateways. These costs are not part of this GA budget. The GA funds only: building the infrastructure, deploying it across 12,000 ha, and open-sourcing the SDK. Alliance's Financial Commitment: * ADA < $0.25 at disbursement: Alliance self-funds the gap from its own capital. Deployment continues without interruption. * ADA ≥ $0.30 at disbursement: Surplus is used to reimburse Alliance's self-funded expenditures first; any remainder becomes contingency or ecosystem reinvestment. All 2,400,000 ADA locked in a smart contract escrow managed by Intersect. Disbursed per milestone after IOB confirmation. Strategic Alignment: This proposal complies with the Intersect 2026 Budget Framework, contributing directly to the Pillar: Ecosystem Growth & Real-world Adoption of the Cardano 2030 Vision. Why this demand is mandatory, not voluntary: OriLife addresses requirements mandated by 4 legal systems simultaneously — Vietnam's Circular 11/2026/TT-BCT (hard deadline December 1, 2026), China's GACC Orders 248 & 249, EU's EUDR, and US FDA's FSMA 204. Legal deadlines create demand that cannot be eliminated by market forces or competitor products. A YES vote funds infrastructure the market is required to adopt. ### KEY TERMS Readers familiar with Cardano may skip this section. Bio-ID — A biological fingerprint from a durian's skin texture. Unique to each fruit, inseparable from it. Replaces physical QR labels. VeData — OriLife's data validation and batching layer. Checks farm data through 5 filters before sending them to Cardano. Bundles up to 15,000 fruit records into one Cardano transaction — reducing cost by \~19,000×. LampNet — A distributed storage network (about 100 devices in Vietnam in pilot phase) storing farm photos, videos, and logs. Data is encrypted and miraged into hundred shards then distributed on a lot of devices; only the farmer's PhoenixKey can decrypt it. Cardano stores only a 32-byte fingerprint — not the raw data. Farm NFT — A permanent digital ledger for one hectare of farmland on Cardano Mainnet. Updatable (new cultivation logs, harvest records) without changing the NFT's identity. PhoenixKey — A digital identity built on Cardano's DID standard. Farmers register with fingerprint + face scan in \~3 minutes. No seed phrase, no email, no blockchain knowledge needed. One identity works across all OriLife apps. Midnight — A Cardano privacy layer. Enables selective disclosure: customs sees origin data, consumers see cultivation history, nobody sees contract prices or trade partners. MAGIC — An internal service credit for platform fees (storage, compute, Cardano network fees). Farmers pay in VND; MAGIC converts to ADA automatically. Not a tradeable token. IOB: Independent Oversight Board - Three (or more) independent reviewers who verify each milestone before ADA is released from escrow. Funds cannot move without 2-of-3 IOB signatures. eUTXO — Cardano's transaction model. Multiple farm records update simultaneously at a fixed cost — cost does not grow with the number of farms. DID - Decentralized Identifier - A W3C-standard digital identity that belongs to the farmer, not to any company. Cannot be deleted or altered by OriLife, DDC Holdings, or anyone else. *** ###
### MOTIVATION #### Why this project must be funded now — the problem, the urgency, and the team that earned the right to solve it. #### The Problem: A $3.36 Billion Supply Chain Built on Peelable Stickers Vietnam's durian exports to China totaled $3.36 billion USD — over 90% of the country's durian export revenue. The entire traceability system rests on physical QR labels that can be peeled off one fruit and stuck onto another. The 2025 scandal ([source](https://vnexpress.net/gan-2-000-container-sau-rieng-xuat-khau-mac-ket-vi-tam-ngung-xet-nghiem-4955678.html)) proved this conclusively: 17 individuals prosecuted, 55+ plantation codes revoked, 2,000 containers stuck at ports. The root cause is simple — when the identity carrier can be separated from the product, fraud is inevitable. No blockchain can fix this if what you're anchoring on-chain is a detachable sticker. The solution must make the product itself the identity. #### Five Pressures That Cannot Be Delayed Pressure 1 — Officially Assigned Mission: The Đắk Lắk Agricultural Extension Center officially assigned TonFarm the mission to digitize 12,000 ha of durian. OriLife is the mandatory technical infrastructure to complete this mission. Pressure 2 — National Pilot, July 10, 2026 Summary: Decision 5272/QĐ-BNNMT ([source](https://mae.gov.vn/Pages/chitietvanbandh.aspx?ItemID=3451)) pilots Durian Traceability January 1 – June 30, 2026, with national expansion by end of 2026. On April 4, 2026, the first Green Lane shipment was exported — but still uses peelable labels. OriLife solves the weakness the government plan hasn't addressed. Pressure 3 — Nationwide Formalization from July 1, 2026: The Traceability System officially launches for key agricultural products. OriLife needs to be operational to integrate into this wave. Pressure 4 — Hard Legal Deadline December 1, 2026: "Food production establishments must connect to and provide information to the Traceability System from December 1, 2026." — Article 15, Circular 11/2026/TT-BCT ([source](https://vanban.chinhphu.vn/?pageid=27160\&docid=217126)) Pressure 5 — China's GACC Requirements: The 2025 scandal proved the labeling system has failed. GACC continues tightening requirements. Without fraud-proof traceability, Vietnam risks losing its largest export market. #### The Alliance: Earned the Right to Solve This **TonFarm 2024 — The Expensive Lesson** TonFarm is an agricultural digitization project launched by DDC Holdings in 2024 in Đắk Lắk. DDC actually deployed, actually failed in many aspects, and drew lessons that cannot be learned from textbooks. DDC mobilized dozens of employees to manually attach QR codes to durian trees, store data on a single server, and hash each fruit as a separate on-chain transaction. | Weakness | Real-world Impact | | ----------------------------------- | ---------------------------------------------- | | QR labels detachable | Peeled and re-attached — zero anti-fraud | | Data on a single server | Modifiable at any time | | Each fruit = 1 on-chain transaction | 180M fruits = 180M transactions — infeasible | | Farmers dependent on DDC staff | Staff leaves = data stops | | Hash ≠ validation | Proves data unchanged, not that it was correct | Verify:[ TON blockchain NFT collection](https://tonviewer.com/UQAftkW5i-ON2qIPIRub2Z8zZL_KzbvX8jPnF9-6uwnowmcD?section=nfts) Despite failures, DDC built irreplaceable assets: UX validated with farmers aged 50+ over 2 harvest seasons; relationships across 46 communes; standardized onboarding; offline logic with zero data loss. Copyright Certificate No. 4420/2025/QTG confirms this is not a new project. **The Three-Company Alliance** * [DDC Holdings](https://ddcholdings.co/) — Field Operations & Government Relations. Trust relationships with farmers and government agencies across 46 communes that no tech company can replicate quickly. They failed with the old approach and understand exactly why. * [GreenSun Tech](https://www.greensun.tech/en) — R\&D & Core IP. Holds 4 USPTO Provisional Patent Applications directly related to OriLife platform: LampNet, VeData, PhoenixKey, and OriLife. Also deploying 1,000 EV charging stations as a partner with V-Green (VinFast) — providing capacity to operate physical infrastructure at scale. * [Aladin Contract](https://aladin.work/) — Product Development & User Experience. Building Aladin App 2.0 (June 2026): Chat, Work, and Trace modules. Users join Cardano via fingerprint and face — no seed phrase, no technical knowledge required. **The Strategic Decision** The three teams unified in early 2026: migrate the entire infrastructure to Cardano — the only blockchain that simultaneously provides eUTXO batch efficiency, Midnight ZK Proof for trade privacy, and Identus for government-scale DID. #### Verifiable Evidence * OriLife PoC:[ orilife.io/en/demo](https://www.orilife.io/demo) * LampNet:[ lampnet.cloud](https://lampnet.cloud/) - Some attached documents are miraged on LampNet. * VeData on Preprod:[ verified transaction](https://preprod.cardanoscan.io/transaction/a8dd2f28d7b4d4a162d752070d839496e671f608abde9bb95a021cbbe7574dde?tab=utxo) * PhoenixKey: * Source code:[ ](https://github.com/OriLifeTrace) * Field activities: * Legal: 4 USPTO Provisional Patent Applications — see Annex B. The Alliance has self-invested nearly $500,000 USD before submitting this proposal. *** ### RATIONALE How OriLife works, why Cardano is the right chain, what the Treasury gets, and the delivery plan. #### What Does the Cardano Treasury Invest In? 1\. Real-World On-Chain Activity | Metric | Value | Basis | | ----------------- | -------------------------------- | --------------------------- | | Area | 12,000 ha | Extension Center assignment | | Farm households | 12,000 | \~1 ha/household | | PhoenixKey DIDs | 24,000 | 2 persons/household | | Durian trees | 1,200,000 | 100 trees/ha | | Fruits/season | 180,000,000 | 150 fruits/tree | | On-chain activity | \~1,000,000–1,200,000 event/year | See breakdown below | Activity breakdown: | Activity | Est. events/year | Notes | | ----------------------------------- | ---------------- | --------------------------------------- | | VeData batch anchors | \~600,000 | \~Weekly per farm during growing season | | Labor contracts (farmer ↔ worker) | \~300,000 | \~25 engagements/ha/year\* | | Commercial escrow (farmer ↔ trader) | \~60,000 | \~5 tx/ha/year\*\* | | One-time setup: DID, NFT minting | \~100,000 | Spread across M4–M7 | | Path B audit decommits (Hydra) | \~2,190 | Fixed system cost, 6×/day | VeData batch anchors are events batched into \~6,000–7,500 actual L1 transactions. Labor contracts, commercial escrow, and setup events settle as individual L1 transactions. Full reconciliation: Annex A, Section 6. \*Based on field data: 2 permanent workers × 12 monthly payments + 1–2 harvest khoán contracts. Source: CropTex; QĐ 3763/QĐ-UBND Đắk Lắk. \*\*Based on durian trade structure: advance deposit + final settlement per harvest batch, 1–2 batches/year. Adjusted from initial estimate after field review. All fees for these transactions are paid by users via MAGIC credits — not covered by this GA. The 1,200,000 figure is the upper bound planning estimate; actual activity will vary by farm. 2\. ADA Permanently Locked \~75,000+ ADA | Lock Location | ADA | | ------------------------------- | -------- | | minADA in 12,000 Farm NFTs | \~24,000 | | minADA in 24,000 farmer wallets | \~48,000 | | Commercial escrow contracts | \~3,000+ | 3\. Treasury Fee Contribution 20% of every Cardano transaction fee flows to the Treasury automatically via protocol — no additional commitment required from the Alliance. Estimated annual Treasury contribution from OriLife activity: | Activity | Est. tx/year | Avg fee | Total fees | 20% → Treasury | | -------------------------- | ------------- | ----------- | -------------------------- | ------------------------ | | VeData batch (L1 batch tx) | \~6,000–7,500 | \~0.83 ADA | \~5,000–6,000 ADA | \~1,000–1,200 ADA | | Labor contracts | \~300,000 | \~0.30 ADA | \~90,000 ADA | \~18,000 ADA | | Commercial escrow | \~60,000 | \~0.30 ADA | \~18,000 ADA | \~3,600 ADA | | DID + setup | \~100,000 | \~0.30 ADA | \~30,000 ADA | \~6,000 ADA | | Total |


|


| \~143,000–144,000 ADA/year | \~28,600–28,800 ADA/year | At $0.25/ADA: \~$7,150/year direct Treasury contribution from OriLife's 12,000 ha alone. This is the floor estimate — durian traceability only, Đắk Lắk only. As the open-source SDK expands to coffee (731,900 ha), melon, aquaculture, and global markets, this contribution scales proportionally without any additional Treasury investment. The infrastructure is built once; the returns compound indefinitely. Additionally: \~75,000 ADA permanently locked on-chain at M4 — immediate, verifiable, permanent value for the Cardano ecosystem regardless of future activity. OriLife is not a loan to be repaid. It is infrastructure that generates sustainable Treasury revenue as monetary expansion declines — precisely the kind of real-world adoption the Cardano 2030 Vision requires. 4\. Government-Scale Adoption | Metric | Commitment | | ------------------------------------------- | ---------------------------- | | Active users with DID on Cardano | 24,000 people | | Digital transformation conferences covered | 46 communes × 50,000+ people | | Opportunity to become a government platform | 1 of 5 national platforms | | Midnight ZK Proof in real commerce | Global first | #### Why Cardano Why not another blockchain? Three requirements must be met simultaneously for this use case. No other blockchain provides all three: | Requirement | Why it matters | Only Cardano provides | | --------------------------------------- | ---------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | O(1) batch cost for 180M fruits | Linear cost makes 180M individual records economically infeasible | eUTXO + Merkle Tree — cost unchanged whether 1 or 15,000 fruits update in one tx | | Commercial privacy for export trade | Businesses won't accept blockchain if competitors see contract prices and trade partners | Midnight ZK Proof — selective disclosure per party, production-ready | | Government-scale decentralized identity | Vietnam's regulatory framework requires W3C-standard DID; farmers need biometric login with no seed phrase | PhoenixKey, built on Cardano's DID infrastructure (Identus/Atala PRISM). PhoenixKey adds biometric registration and seedless recovery on top of the Identus standard — the same W3C-compliant DID, usable by a farmer with no technical knowledge. | Ethereum: gas wars make batch economics unpredictable. Solana: no native privacy primitive equivalent to Midnight. Other L1s: no production-ready DID infrastructure. Cardano is the only blockchain where all three primitives exist, are production-tested, and work together. eUTXO — On-chain Cost Doesn't Scale with Volume Each farm holds only 1 Farm NFT (CIP-68 Dynamic). All fruit state updates are aggregated into a single Cardano transaction via Merkle Tree by VeData. Cost is unchanged whether 1 or 15,000 fruits change state in the same batch. Two numbers, two questions — both real: 1. What is the minimum cost to identify 180 million fruits? | Model | Transactions | Cost per fruit | Total | | ----------------------- | -------------- | ----------------- | ------------- | | Legacy (1 fruit = 1 tx) | 180,000,000 tx | \~$0.17/fruit | \~$30,600,000 | | OriLife VeData batch | \~12,000 tx | \~$0.000009/fruit | \~$1,530 | | Reduction | 15,000× | \~19,000× | \~20,000× | VeData's batch technology reduces identification cost from \~$0.17/fruit (legacy, 1 tx per fruit) to \~$0.000009/fruit (OriLife, 15,000 fruits per tx) — a 19,000× reduction, bringing total identification cost for 180 million fruits from \~$30,600,000 down to \~$1,530. Full transaction model and reconciliation of all figures: see Annex A, Section 6. 2. What is the total on-chain footprint of a fully operational ecosystem? \~1,000,000–1,200,000 L1 events/year across all activity types — real farming, labor, and commerce. All Path A transactions settle directly on Cardano Mainnet L1. Path B (Hydra audit decommits, \~2,190 tx/year) adds a cryptographic audit trail at \~2.7 ADA/day total. Technical details: Annex A, Section 10–11. Midnight — Protecting Trade Secrets | Party | Can See | Cannot See | | ---------------------- | ---------------------------------- | -------------------------- | | GACC (Chinese Customs) | Origin, harvest date, GACC code | Contract price, partners | | EU EUDR | GPS plot, deforestation-free proof | All commercial information | | Consumers | Cultivation history, harvest date | All business information | Midnight — Protecting Trade Secrets: Midnight ZK Proof enables selective disclosure — customs sees origin and phytosanitary data, consumers see cultivation history, no one sees contract prices or trade partners. This is a commercial prerequisite for export businesses to accept blockchain. Identus — Built-in Decentralized Identity: One PhoenixKey registration (fingerprint + face, 3 minutes) creates a W3C-standard DID on Cardano Mainnet — works across all OriLife-integrated applications. Farmers never know what blockchain is. #### Why $600,000 Achieves What $50,000,000 Could Not The agricultural traceability space has seen substantial investment over the past decade. The results reveal a consistent pattern: | Platform | Investment | Current Status | Core Limitation | | ----------------------- | ------------------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | | IBM Food Trust | Est. $200M+ | Operational — restructured into FSMA 204 compliance tool (iFoodDS partnership, Sept 2023) | Voluntary adoption; label-dependent; compliance tool, not fraud prevention | | VeChain × Walmart China | Est. $10–50M | Operational | Physical label still detachable — fraud vector structurally unsolved | | SEA2SEE (EU Horizon) | €5.4M over 4 years | Pilot stage — commercial transition pending as of 2026 | No legal liability for non-compliance; voluntary participation | | TE-FOOD | \~$10M (ICO + operations) | Platform operational (400K+ tx/day in Vietnam); TONE token down 99%+ from peak | Label-dependent; economic model relied on token speculation, not sustainable revenue | The pattern is clear: platforms survive, but the root problem remains unsolved. None of these platforms has eliminated food fraud at its source. IBM Food Trust pivoted from a standalone traceability network to a compliance tool — useful, but not a fraud-prevention system. VeChain and TE-FOOD both operate at scale, yet the 2025 Vietnam durian scandal — 17 individuals prosecuted, 55+ plantation codes revoked, 2,000 containers blocked — occurred in a market where TE-FOOD has been operating for years. The label can still be peeled. The fraud vector remains open. The problem was never technological capability. It was structural. All four platforms share the same architectural assumption: a physical data carrier (label, QR code, RFID tag, seal) is attached to the product and carries its identity. When the carrier can be separated from the product, fraud is always possible — regardless of how sophisticated the blockchain behind the label is. OriLife addresses the structural failure, not just the technological symptom: Structural difference 1 — Mandatory adoption via legal liability. Circular 11/2026/TT-BCT creates direct legal consequence for non-compliance by December 1, 2026. IBM Food Trust, VeChain, SEA2SEE, and TE-FOOD all operated under voluntary adoption models — enterprises joined because they wanted to, not because they were legally required to. OriLife is the first deployment in this space where non-adoption carries regulatory penalty. Structural difference 2 — The product is its own identity. Bio-ID uses the durian fruit's biological skin texture as the identity carrier. There is no label to peel, no QR code to transplant. The 2025 Vietnam scandal — which occurred in a market with existing traceability infrastructure — is direct proof that label-based systems cannot solve this problem regardless of investment level. Why OriLife costs less while solving more: The $600,000 GA budget — combined with \~$500,000 in prior self-investment — totals approximately $1.1M USD for full deployment across 12,000 hectares and 180 million fruits. Three factors make this possible: First, engineering depth at local cost structure. The Alliance engineers — across GreenSun Tech, Aladin Contract, and DDC Holdings — are building at a technical level comparable to global blockchain and AI teams, operating within Vietnam's cost structure. Cardano smart contract development, distributed storage architecture, and computer vision fine-tuning are being executed by engineers who have spent years on this specific problem. This is not outsourced development or a demo MVP. Second, AI-assisted development multipliers. The Alliance uses AI tooling systematically across the development pipeline — from dataset labeling (semi-automated via CVAT) to code generation, test automation, and documentation. Internal estimates show 2–3× throughput compared to conventional development processes. The M1 labeling budget reflects this: 50,000 field images at $0.15/image via semi-automated labeling, not $1.50–$3.00/image via fully manual annotation. Third, building on proven primitives, not reinventing infrastructure. OriLife does not build its own blockchain, DID framework, or privacy layer. It deploys on Cardano (eUTXO batch efficiency), Identus (production-ready DID), and Midnight (ZK Proof). IBM Food Trust and VeChain built proprietary infrastructure — significant capital consumed before a single farmer was onboarded. OriLife's engineering effort is integration and application on public goods. Fourth, near-zero identification cost democratizes access at any scale. Every predecessor platform implicitly assumed a minimum viable farm size. IBM Food Trust targets enterprise supply chains. VeChain's Walmart China deployment works with large registered facilities. TE-FOOD's per-product fee of \~35–60 VND is cheap by industrial standards — but still assumes volume to justify onboarding cost and operational complexity. OriLife's Bio-ID identification cost approaches zero per fruit. There is no physical label to purchase, no RFID tag to attach, no per-unit consumable of any kind. The identification happens through the product's own biological surface, captured by a mid-range Android phone the farmer already owns. This changes who can participate in a verified supply chain. A farmer with 3 chickens can provide verified origin. An elderly couple living off a small patch of water spinach harvested daily can attach blockchain-verified provenance to every bunch they bring to market. A subsistence durian grower with half a hectare — too small to be commercially interesting to any enterprise traceability platform — can prove their fruit is authentic, chemical-free, and traceable to a specific tree on a specific farm. No predecessor platform made this economically or operationally possible at that scale. The cost structure of label-based systems creates a floor below which small producers are simply excluded from verified supply chains — and therefore excluded from the premium markets, export channels, and legal compliance frameworks that verified provenance unlocks. OriLife's architecture has no such floor. The same system that traces 180 million fruits across 12,000 hectares traces 150 fruits from a single smallholder at identical cost per fruit. This is not a feature added for social impact — it is a direct consequence of removing the physical data carrier from the equation entirely. For Cardano, this means the 24,000 DIDs created in Đắk Lắk are not a ceiling — they are a proof of concept for a model that scales down as naturally as it scales up. Every small farmer brought into a verified supply chain is a new Cardano user whose economic activity generates real on-chain transactions, not a registration metric. The result: OriLife's cost per hectare digitized is approximately $50 USD. Industry benchmarks for comparable agricultural digitization projects range from $500–$2,000/ha. The efficiency gap is not a sign of low ambition — it is a consequence of structural choices in team composition, AI tooling, and architecture. The Cardano Treasury is not funding a research project. It is funding production deployment of a system that solves the structural problem its predecessors identified but could not fix, has legal demand confirmed by four regulatory frameworks simultaneously, and is operated by a team that invested $500,000 of their own capital before requesting community support. #### Data Flow Farm → LampNet: AI processes on-device, signs with PhoenixKey, sends <1KB package. Image available to consumers within \~5 seconds of upload. LampNet → VeData: 5-layer validation (device origin, image authenticity, GPS boundary, temporal validity, biological plausibility). Bad data is rejected before it ever reaches Cardano. VeData → Cardano: VeData uses two independent pipelines. Path A (user data) sends Farm NFT updates directly to Cardano L1 as batched transactions — \~80–100 farms per transaction, every \~20 seconds — this is what consumers see when verifying a fruit's origin. Path B (audit trail) accumulates cryptographic records off-chain via Hydra and commits a summary to L1 every 4–8 hours — this is the tamper-proof evidence log for regulators. Path A works regardless of Path B's status. Cardano → Parties: Midnight View Keys deliver the right information to the right party. Customs verifies origin. Consumer verifies cultivation history. No one sees trade secrets. Full technical architecture: see Annex A. Transaction model reconciliation: Annex A Section 6. Hydra integration: Annex A Section 10. #### Milestones (Work Packages) Design Principles: * Milestones follow product development: Foundation → Alpha → Beta → Audit → Mainnet → Pilot → SDK → Scale → Sustainability. * Each milestone has Output — Acceptance Criteria — Evidence for IOB. * Tree/fruit targets: 1 ha = 100 trees = 15,000 fruits. * Audit strategy: Reuse Intersect's Escrow template + audit customization (\~$5–15K) + Intersect Community Audit Fund + Bug Bounty post-launch. *** **M0 — Foundation + Mobilization Advance** May Week 1–2 · 360,000 ADA · $90,000 · 15.0% Mobilization Tranche — disbursed immediately upon M0 pass so the Alliance can recruit and begin deployment. Output: Escrow deployed on Preprod; IOB 3 members confirmed + signing keys on-chain; wallet addresses published; Clawback active. Acceptance Criteria: Escrow TxHash verifiable; IOB 3 members signed on-chain; wallets public ≥14 days; automatic Clawback if M1 not submitted within 90 days. Evidence: Escrow TxHash · IOB signatures on-chain · 30-day Spending Plan NOTE: 15% advance protected by automatic 90-day Clawback. Mandatory Spending Report 30 days after disbursement — failure freezes all subsequent milestones. *** **M1 — Alpha: Identify 750,000 Sample Fruits** May–June · 260,000 ADA · $65,000 · 10.8% Fine-tune AI on Đắk Lắk field data: 50 ha = 5,000 trees = 750,000 test fruits. Output: Labeled dataset ≥50,000 field images (4+ varieties, 4+ stages, 5+ lighting); fine-tuned AI model; multi-tenant database; full pipeline Mobile → LampNet → VeData → Preprod. Acceptance Criteria: Precision \~99% on 10,000-tree benchmark. Recall ≥95% at ±45° angle. Latency <1 second on Android 4GB. Temporal consistency after 30 days. Throughput ≥100 units/hour/person. API <500ms p95. Evidence: Benchmark report · Field video ≥10 min · Public DB schema · Load test log. *** **M2 — Beta App: Signing & Offline-First** June–July · 220,000 ADA · $55,000 · 9.2% Production-ready app. Smart contract frozen for audit. Output: OriLife Collector App (Android); Smart Capture via Sensor Fusion; PhoenixKey SDK integrated; offline-first queue + auto-sync; FarmDatum contract frozen hash public. Acceptance Criteria: IOB self-installs and tests <10 min; uncut end-to-end video demo; tampered data auto-rejected; offline sync verified; contract freeze hash public ≥7 days before M3. Evidence: APK link · Demo video · Freeze hash + GitHub commit · Unit test report · Offline sync recording *** **M3 — Audit + Mainnet Launch** July · 180,000 ADA · $45,000 · 7.5% Audit → Fix → Deploy Mainnet. No deployment before audit. Output: Independent audit report; FarmDatum + Escrow on Mainnet; ≥1 Farm NFT (CIP-68); BCT Portal API connection. Acceptance Criteria: Zero unresolved Critical/High; ≥1 Farm NFT on Mainnet; source code public (MIT + Apache 2.0); BCT API pass; demo ≥10,000 updates → 1 tx (public TxHash). Evidence: Audit URL · Mainnet TxHash + Policy ID · GitHub link · BCT screenshot · VeData batch demo *** **M4 — Pilot: 7.5 Million Fruits / 500 Ha** July–August · 280,000 ADA · $70,000 · 11.7% Controlled pilot in 1–2 districts: 500 households = 50,000 trees = 7,500,000 fruits. Output: 500 households onboarded with PhoenixKey DID; 50,000 trees with Bio-ID on Mainnet; harvest module operational August 2026; ≥1 GACC export shipment cleared. Acceptance Criteria: ≥50,000 trees on-chain; ≥1,000 active DIDs; ≥1 GACC shipment with blockchain proof; anti-fraud red-team 100% detection (≥20 scenarios); zero data loss; scan fruit → trace mother tree <2 seconds. Evidence: Dashboard · Customs declaration scan · Fruit scanning video ≥5 min · Anti-fraud log · GPS + field photos *** **M5 — SDK Open Source + Multi-App Integration** August · 200,000 ADA · $50,000 · 8.3% Prove OriLife is open infrastructure: two apps, one source of truth. Output: OriLife Integration SDK + Smart Contracts on GitHub — open-source scope: see Annex B Section 12; Compliance Adapter SDK (GACC + GS1 EPCIS v2.0 + Midnight View Key); TonFarm + Aladin integrated; Bug Bounty launched. Acceptance Criteria: GitHub public with docs; third party installs SDK + calls API <1 hour (video); GACC JSON valid; GS1 EPCIS v2.0 validator pass; multi-app demo: farmer scans on TonFarm → consumer sees on Aladin → customs verifies via orilife.io. Evidence: GitHub org · Multi-app video ≥10 min · GS1 validator screenshot · Developer integration video · Bug Bounty URL *** **M6 — Beta Rollout: 45 Million Fruits / 3,000 Ha** August–September · 260,000 ADA · $65,000 · 10.8% 3,000 households = 300,000 trees = 45,000,000 fruits across 3–5 districts. Output: 3,000 households onboarded; 300,000 tree Bio-IDs on Mainnet; training at 3–5 districts; infrastructure scaled. Acceptance Criteria: ≥300,000 trees on-chain; ≥3,000 active DIDs; ≥3 districts with GPS + photos; uptime ≥99.0%; p99 <20ms; zero security incidents. Evidence: Dashboard · GPS heatmap · Grafana uptime · Load test · Security log *** **M7 — Mass Rollout: 180 Million Fruits / 12,000 Ha** September–October · 280,000 ADA · $70,000 · 11.7% 12,000 households = 1,200,000 trees = 180,000,000 fruits. GA primary target achieved. Output: 12,000 households (24,000 people) with active DID; 1,200,000 trees on Mainnet; 15 districts covered; DR test successful. Acceptance Criteria: ≥1,200,000 trees on-chain; ≥24,000 active DIDs; ≥15 districts; uptime ≥99.5% peak month; DR recovery <15 min; ≥100,000 on-chain tx during M7. Evidence: On-chain metrics · 15-district report · 30-day Grafana · DR test minutes · Explorer tx count *** **M8 — Global Integration + Sustainability** October–November · 360,000 ADA · $90,000 · 15.0% Hand off to the market. Output: ≥5 international enterprises integrated; MAGIC economics live; independent impact report; expansion plan for coffee, melon, shrimp, fish; 2 public AMAs. Acceptance Criteria: ≥5 active B2B contracts; MAGIC ≥1,000 tx/30 days; impact report ≥30 pages public; 2 AMA recordings (≥60 min each); roadmap for 4 new industries; bilingual docs. Evidence: B2B contracts · MAGIC on-chain · Impact report URL · AMA recordings · Roadmap · GitHub docs Surplus after M8: Reimburse Alliance's self-funded expenditures → contingency → reinvest in ecosystem → public report within 14 days. *** #### Budget Overview | # | Milestone | Target | ADA | USD | % | | ----- | -------------------------------------- | ------ | --------- | -------- | ----- | | M0 | Foundation + Mobilization Advance | — | 360,000 | $90,000 | 15.0% | | M1 | Alpha — 750K sample fruits | 750K | 260,000 | $65,000 | 10.8% | | M2 | Beta App + Contract Freeze | — | 220,000 | $55,000 | 9.2% | | M3 | Audit + Mainnet Launch | — | 180,000 | $45,000 | 7.5% | | M4 | Pilot — 7.5M fruits / 500 ha | 7.5M | 280,000 | $70,000 | 11.7% | | M5 | SDK Open + Multi-app | — | 200,000 | $50,000 | 8.3% | | M6 | Beta Rollout — 45M fruits / 3,000 ha | 45M | 260,000 | $65,000 | 10.8% | | M7 | Mass Rollout — 180M fruits / 12,000 ha | 180M | 280,000 | $70,000 | 11.7% | | M8 | Global Integration + Sustainability | — | 360,000 | $90,000 | 15.0% | | Total |


| 180M | 2,400,000 | $600,000 | 100% | Financial principles: Alliance self-invested \~$500,000 USD before this GA. Budget anchored at $0.25/ADA. If ADA drops below $0.25, Alliance self-funds the gap — deployment continues. If ADA rises above $0.30, surplus first reimburses Alliance's self-funded expenditures; remainder becomes contingency. Detailed budget per milestone: see Annex C. *** ### PARTICIPANTS Proposer — Field Operations and Government Relations Nguyen Hung Son— Director, Đắk Lắk Office, DDC Holdings. Technology Alliance * DDC Holdings — TonFarm app since 2024, field operations in Đắk Lắk * GreenSun Tech — AI/LampNet/VeData R\&D, intellectual property * Aladin Contract — PhoenixKey, Midnight integration, Compliance SDK Integrated Applications * TonFarm — Farm management (DDC, since 2024) * Aladin — Mass user experience (Aladin Contract) Project Manager — Duc TIGER is the Project Manager of the OriLife platform. Also a dRep and SPO (TIGER) on Cardano. Conflict of Interest Disclosure: * Duc Tiger votes ABSTAIN on this GA and all Withdraw Treasury GAs during the voting period. * All Alliance members receive reasonable compensation from the GA budget, recorded in milestone spending reports. * No token allocation to voters. Institutional Confirmation * Đắk Lắk Farmers' Union (Letter 351-CV/HNDT, December 22, 2025) [https://orilife.io/docs/letter135cvhdnt](https://tonfarm/letter135cvhdnt) * Đắk Lắk Agricultural Extension Center (Cooperation MOU, March 2026) * Presented at digital transformation conferences across 46 communes (50,000+ people) * Candidate for 1 of 5 national strategic traceability platforms *** ### BUDGET MANAGEMENT All 2,400,000 ADA locked in Escrow smart contract managed by Intersect. Disbursed when IOB 2-of-3 sign milestone confirmation. Automatic timeout returns to Treasury — no new vote needed. Independent Oversight Board (IOB) — 3 Members: 1. Intersect MBO representative 2. Independent technical expert (nominated via Intersect Forum) 3. Community dRep (PRAGMA preferred, open candidacy) IOB confirms verifiable outcomes, does not review internal implementation. Treasury Protection Mechanisms: | Scenario | Action | | ---------------------------------------------- | --------------------------------------------------------------------- | | M0 pass → Mobilization Advance | Disburse 15% immediately, with 90-day Clawback | | M0 Spending Report not submitted after 30 days | Freeze all subsequent milestones | | Milestone overdue | Smart contract automatically returns ADA to Treasury | | IOB rejects | No disbursement, 30 days to remediate | | Project stops | All remaining ADA to Treasury within 14 days | | Completed with surplus | Reimburse Alliance self-funded → contingency → ecosystem reinvestment | Detailed Escrow and IOB mechanisms: see Annex D. *** ### RISKS AND MITIGATION | Risk | Likelihood | Mitigation | | --------------------------------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ADA drops below $0.25 | Medium | Alliance self-funds the gap — deployment continues at slower pace | | Farmers don't adopt | Low | Presented to 46 communes, 50,000+ people; Circular 11 creates legal pressure | | AI doesn't hit M1 benchmark | Medium | 21-day grace; contingency for extra iteration | | Smart contract bug | Very low | Reuse Intersect template + audit + Bug Bounty | | Field data fraud | Low | 5-layer VeData validation + random 5% spot checks | | Miss August harvest season | Medium | M4 Pilot covers August; M6/M7 scale after season | | Duc Tiger conflict of interest | Managed | Disclosed proactively. Duc Tiger votes ABSTAIN on this GA and all Treasury Withdrawal GAs during the voting period. Compensation as PM is documented in milestone spending reports. IOB Member 3 (Community dRep) independently verifies field adoption metrics — the area most directly under PM influence. | | IOB member disengages mid-project | Low | Backup candidates identified at M0 via public candidacy process. Intersect MBO replacement protocol (10-day transition) pauses timeout clocks during handover. IOB scope is milestone-gated, not continuous — 7-day review windows per milestone only. | | Mobilization Advance misuse | Very low | 90-day Clawback + 30-day Spending Report + IOB freeze | | MAGIC economics underperforms | Low | Data on LampNet and Cardano remains independently accessible. Users recover assets via PhoenixKey and can purchase ADA directly. Open-source SDK ensures no vendor lock-in. | | GACC does not accept Midnight View Key format | Low | Midnight is a privacy enhancement layer, not a GACC compliance prerequisite. OriLife can export full GACC-required data fields (origin, harvest date, plantation code, phytosanitary) independently of Midnight. If GACC requires format changes, the Compliance Adapter SDK handles this without modifying core infrastructure. M4 pilot shipment will validate GACC acceptance before full rollout — any required adjustments are addressed at M4, not M7. | *** ### SUSTAINABILITY After Treasury funding ends, OriLife sustains itself through three revenue streams: MAGIC Credit Model: All on-chain transaction fees — VeData anchors, labor contracts, commercial settlements, Hydra audit — are paid by users via MAGIC credits. Farmers and enterprises purchase MAGIC with local fiat currency through standard payment gateways (banks, e-wallets). MAGIC automatically converts to ADA for network settlement, covering on-chain fees, LampNet storage, and AI processing. Farmers never need to understand blockchain — they pay in their local currency and get a working system. B2B Compliance SaaS: Export enterprises subscribe for GACC + GS1 EPCIS v2.0 + Midnight View Key services, paid as MAGIC credits converted from fiat. Ecosystem Expansion: The open-source SDK enables any developer or startup to build on OriLife infrastructure. Success in Đắk Lắk durian creates a proven blueprint for Đắk Lắk coffee (731,900 ha, $8.4B EU exports), melon, aquaculture, and global markets. The global traceability market reaches $31.1B by 2033. Long-term commitment: The Alliance commits to completing M0–M8 and open-sourcing the SDK. Post-M8, adoption and activity are driven by the market — enterprises integrating the SDK, farmers using the platform, and developers building new applications. The 20% Treasury fee mechanism ensures that every transaction generated by OriLife and its ecosystem automatically contributes to Cardano's Treasury without requiring any additional commitment from the Alliance. *** ### ### COMMITMENTS I, Nguyễn Hùng Sơn, Director of DDC Holdings' Đắk Lắk Office, confirm: 1. All information in this proposal is truthful and independently verifiable. 2. TonFarm is an application developed by DDC Holdings since 2024. The OriLife Alliance (DDC + GreenSun + Aladin) was formally established in early 2026 with the strategic decision to migrate the entire infrastructure to Cardano. 3. Duc Tiger is the Project Manager, also a dRep and SPO TIGER. Full conflict of interest disclosure: Participants section and Annex D Section 10. 4. All Alliance members receive reasonable compensation from the budget, allocated by role and actual contribution, recorded in milestone spending reports. 5. No token allocation to voters. ADA receiving wallet addresses published ≥14 days before on-chain submission. 6. All undisbursed ADA returns to the Treasury if milestones are not completed. 7. Commitment to organize at least 2 public AMAs. 8. If ADA is below $0.25 at disbursement, the Alliance self-funds the gap — deployment continues. If ADA is above $0.30, surplus first reimburses Alliance's self-funded expenditures; remainder becomes contingency or ecosystem reinvestment. 9. The SDK is open-sourced at M5. Post-M8 adoption is market-driven. The Alliance does not commit to a specific transaction volume target, revenue sharing percentage, or years of post-M8 activity — these outcomes belong to the ecosystem, not the Alliance. Proposer: Nguyen Hung Son— Director, DDC Holdings, Đắk Lắk * Web: * X: Manager: Duc Tiger · dRep · SPO TIGER · Votes ABSTAIN on this GA * dRep: * X: * Telegram: Technology Alliance: * DDC Holdings — Nguyen Hung Son (Director, Đắk Lắk) · TonFarm since 2024 * GreenSun Tech — Nguyen Thi Kim Ngan (CEO) * Aladin Contract — Nguyen Thi Thuy (Deputy Director) Technical, legal, financial, and governance documents stored on LampNet. Open-source code hosted on GitHub. On-chain evidence verifiable on Cardano Explorer.
# Annex A Annex A Technical Architecture & Verified Results Document: GS-ORILIFE-GA-01 · Annex A Version: v6.1 Updated: April 2026 IP Disclaimer: Architecture described at feasibility-evaluation level. Core technologies protected by 4 USPTO PPAs. Open-source components at . ### 1. From TonFarm to OriLife #### Why DDC Failed — and What Was Learned TonFarm (2024) deployed dozens of staff across Dak Lak farms: manually attaching QR codes, photographing trees, recording GPS, uploading to a single server, and hashing each fruit as a separate on-chain transaction. Verifiable on-chain:[ TON blockchain NFT collection](https://tonviewer.com/UQAftkW5i-ON2qIPIRub2Z8zZL_KzbvX8jPnF9-6uwnowmcD?section=nfts). Five failures DDC experienced directly: | Weakness | Real-world consequence | | ----------------------------- | ----------------------------------------------------------------------- | | QR labels detachable | Peeled and re-attached — zero anti-fraud. Exactly the 2025 scandal | | Single server | Anyone with access could modify data; blockchain only anchored the hash | | 1 fruit = 1 tx | 180M fruits = 180M transactions — impossible to scale | | Farmer dependent on DDC staff | Staff leaves = data stops | | Hash ≠ validation | Proves "data unchanged since hashing," not "data was correct" | Despite failures, DDC built irreplaceable assets: UX validated with farmers aged 50+ over 2 harvest seasons; relationships with the Farmers' Union and Extension Center across 46 communes; standardized onboarding; offline queue logic with zero data loss. Copyright Certificate No. 4420/2025/QTG confirms this is not a new project. #### Architecture Comparison | Criterion | Legacy (TonFarm 2024) | OriLife on Cardano | | --------------------- | ------------------------------ | ----------------------------------------- | | Identity carrier | QR label — detachable | Fruit skin texture (Bio-ID) — inseparable | | Data processing | Staff upload to central server | AI on-device → 80 bytes sent | | Raw data storage | 1 modifiable server | LampNet 100+ nodes, encrypted | | Pre-chain validation | None | 5-layer validation before anchoring | | On-chain cost | 1 fruit = 1 tx (linear) | 15,000 fruits = 1 tx — O(1) | | Scale to 180M fruits | 180M tx — infeasible | \~12,000 tx/harvest — $1,530 (Note A) | | Consumer image access | Days (manual) | \~5 seconds (Three-Layer Read Model) | | Commercial privacy | Fully public | Midnight View Keys per party | | User identity | Password, managed by DDC | PhoenixKey — biometric, self-sovereign | Note A: \~12,000 tx = theoretical floor (1 VeData anchor per farm per harvest season). In production, VeData runs weekly → \~600,000 anchor events/year → \~6,000–7,500 actual L1 batch transactions. Full ecosystem: \~1,200,000 L1 events/year across all activity types. See Section 6. #### The Alliance * DDC Holdings — field operations and government relations. Brings institutional trust across 46 communes that no tech company can replicate quickly. * GreenSun Tech — R\&D and core IP. Holds 4 USPTO PPAs directly related to OriLife. Also deploying 1,000 EV charging stations with V-Green (VinFast) — proving capacity to operate physical infrastructure at scale. * Aladin Contract — product development. Building Aladin App 2.0 (June 2026): Chat, Work, and Trace modules. Users join Cardano via fingerprint and face — no seed phrase. Why Cardano: eUTXO enables O(1) batch cost. Midnight enables commercial privacy. Identus enables government-scale DID. No other blockchain simultaneously provides all three. The Alliance has self-invested nearly $500,000 USD before this proposal. ### 2. System Architecture — Four Layers Data flows one direction only: farm → blockchain. Layer 1 — Edge (Farmer's phone): AI processes on-device. Signs data with PhoenixKey hardware key. Sends <1KB package. Works on 2G. Layer 2 — LampNet (Distributed storage and compute): Photos, videos, logs encrypted and distributed across 100+ physical nodes in Vietnam. Available to consumers within seconds of upload — before any blockchain confirmation. Layer 3 — VeData (Validation & aggregation): 5-layer validation. Aggregates thousands of records into one Merkle root. Operates two independent settlement paths (Section 5). Layer 4 — Cardano Mainnet (Immutable evidence): Path A: direct L1 batch updates. Path B: Hydra audit decommits. Anyone can verify; no one can modify. Three physical constraints resolved: | Constraint | Response | | ---------------------------- | ------------------------------------------- | | Rural 2G/3G | AI on-device; <1KB upload | | GPS drift 5–20m under canopy | Local grid coordinates replace absolute GPS | | Android 4GB RAM | Biometric compressed to 80 bytes on-device | ### 3. Collection Layer Smart Capture via Sensor Fusion: Accelerometer + compass integration triggers capture only when device is stable and object is identified. Eliminates blurry images; keeps upload under 1KB. Automatic Harvest Capture: Phone sensors detect cutting motion → auto-capture + timestamp → linked to mother tree on-chain. No farmer action required. Triggers PRIORITY\_HIGH in VeData pipeline — see Section 5 for latency impact. Offline: SQLite local queue, auto-sync on reconnect. Validated over 2 harvest seasons in Dak Lak with zero data loss. ### 4. LampNet — Encrypted Distributed Storage USPTO #64/031,472 About 100+ physical nodes in Vietnam. End-to-end encrypted. Content-addressed via lamp\://CID — accessible globally within seconds of pinning. Only PhoenixKey owner can decrypt. Why not Cardano for raw data: 180M fruits × 10 images × \~500KB ≈ 900TB. Blockchains store proofs, not raw data. LampNet stores data; Cardano stores the 32-byte Merkle root that proves data is authentic. Data sovereignty: Cardano stores only 32-byte hash — no PII, no violation of Vietnam Cybersecurity Law 2018. LampNet nodes prioritized in Vietnam with on-chain Sovereign Data Residency Proof per Decision [1236/QĐ-TTg](https://vanban.chinhphu.vn/?pageid=27160\&docid=211462). Try it:[ lampnet.cloud](https://lampnet.cloud/) ### 5. VeData Mosaic — Validation, Aggregation & Settlement USPTO #64/032,593 · Specification: GS-VEDATA-MOSAIC-SPEC-01 v1.5.0 #### Validation (5 layers) Device origin → image authenticity → GPS vs registered farm boundary → temporal validity → biological plausibility. All 5 must pass. Any failure → data rejected → never reaches Cardano. This is what legacy TonFarm lacked: hashing bad data produces bad hashes. #### Batch Aggregation — O(1) Cost Each Farm NFT stores only a 32-byte Merkle root (Sparse Merkle Tree). Updating 50 of 150 trees recomputes \~700 nodes; the other 100 trees and 15,000 fruits cost zero recomputation. Result: 1 datum update on-chain regardless of how many entities changed. Datum size is permanently bounded at ≤580 bytes — never grows with record count. #### Two-Path Settlement Validated records from LampNet │ ├── PATH A — NFT Datum Updates (direct L1) │ 80–100 Farm NFTs per tx · every 20s or 100 NFTs │ PRIORITY\_HIGH: bypass timeout, submit immediately │ Cost: \~8,900 lovelace per NFT (\~0.0089 ADA) │ └── PATH B — Audit Proof Trail (via Hydra) Accumulate off-chain · Decommit every 4–8 hours Cost: \~450,000 lovelace per decommit (\~0.45 ADA) \= \~2.70 ADA/day fixed for entire system Farm NFTs never enter the Hydra Head. They stay on Cardano L1 at all times, updated only via Path A. Path A functions correctly regardless of Hydra status or version. #### Three-Layer Read Model — Consumer Data Availability Consumers see images within seconds. Blockchain confirmation comes later. These are independent. | Layer | Latency | Basis | UI | | -------------- | ------- | ------------------------- | --------------------- | | 0 — Optimistic | 3–7s | LampNet CID | 🔵 Image available | | 1 — Pending | 15–25s | VeData operator signature | 🟡 Processing | | 2 — Confirmed | 41–61s | Cardano L1 consensus | ✅ Verified on Cardano | End-to-end: Farmer in Dak Lak → Consumer in Ha Noi | Event | Time | | ------------------------------------- | ------------------ | | Farmer triggers harvest capture | T+0s | | Image available on LampNet | T+3–7s → Layer 0 | | VeData validation + SMT root computed | T+15–25s → Layer 1 | | Path A tx confirmed on Cardano | T+41–61s → Layer 2 | | Consumer app auto-updates via push | T+42–62s | For PRIORITY\_HIGH events (harvest, quality inspection): Layer 2 at \~25–35 seconds by bypassing batch timeout. #### SLA Tiers Under normal conditions queue depth stays below 100 NFTs. During peak periods (harvest season), Mosaic signals queue state to consumer apps automatically: | Tier | Queue depth | Confirmation target | Consumer UI | | ---------- | ----------- | ------------------- | --------------------------- | | Normal | <100 | 40–60s | "Verifying..." | | Congested | 100–500 | 2–5 min | "Confirming (\~3 min)" | | Overloaded | >500 | 5–15 min | "Confirming (up to 15 min)" | Images remain visible at Layer 0 regardless of tier — only confirmation latency changes. #### Automated Push — CID Subscription API WebSocket-based. Buyers, export enterprises, customs subscribe to Farm NFT IDs and receive: * cid\_available → image on LampNet * root\_pending → Merkle root queued * datum\_confirmed → TxHash + merkle\_proof\_cid on-chain * datum\_failed → auto-requeue notification No polling. No manual intervention. GACC customs in China receives automatic proof packets at harvest capture in Dak Lak. #### Update Frequency — Why Standard Batch | Strategy | Cadence | Used for | | ------------------ | ------------ | ------------------------------------------ | | A — Standard Batch | 1/hour–1/day | Farm logs, harvest events ← OriLife | | B — Lazy Anchor | >1/minute | IoT sensors, solar panels (not in this GA) | | C — Scheduled | <1/day | Annual audits | Farm updates occur \~weekly per farm — 20-second batch cycles are optimal. Consumer image availability (Layer 0, \~5s) is independent of batch cycle length. Mosaic v1.5.0 introduces Lazy Anchor (Strategy B) for ultra-high-frequency data sources — not used in the current GA, but positioned for future expansion to coffee and aquaculture traceability where sensor integration is planned. #### Fee Calculation — Why 0.0089 ADA Per NFT Single NFT update costs \~0.25–0.42 ADA. Batching 100 NFTs with a reference script (CIP-33): Base fee: 155,381 lovelace Size fee: 44 × \~15,300 bytes = 673,200 lovelace Ref script fee: \~61,440 lovelace (validator \~4KB, Tier 0 ≤25,600 bytes) ───────────────────────────────────────── Total: \~890,021 lovelace for 100 NFTs Per NFT: \~8,900 lovelace (\~0.0089 ADA) — 98% reduction The reference script fee (refScriptFee) is incurred once per batch transaction and does not scale with batch size — making larger batches increasingly efficient per NFT. The Mosaic validator must remain below 25,600 bytes to stay in Tier 0; exceeding this causes non-linear fee growth. ### 6. Cardano — Immutable Evidence #### eUTXO Advantages | Feature | Benefit | | ----------------------- | ----------------------------------------------------------- | | Deterministic execution | VeData pre-computes — no failed transactions, no wasted gas | | Parallelism | 12,000 farms update simultaneously, no UTXO contention | | Native tokens | Farm NFT requires no separate token contract | #### Transaction Model — Three Figures Reconciled 1. \~12,000 tx — Minimum to record 180M fruit Bio-IDs (theoretical floor) | Model | Transactions | Cost/fruit | Total | | ---------------------- | ------------ | ----------- | ------------- | | Legacy: 1 fruit = 1 tx | 180,000,000 | \~$0.17 | \~$30,600,000 | | OriLife VeData batch | \~12,000 | \~$0.000009 | \~$1,530 | | Reduction | 15,000× | \~19,000× | \~20,000× | Legacy cost from TonFarm 2024 TON fees — verifiable at tonviewer.com. 2. \~600,000 events → \~6,000–7,500 L1 tx — VeData actual annual output VeData runs weekly per farm: 12,000 farms × \~50 cycles/year = \~600,000 anchor events. Each L1 batch covers 80–100 farms → \~6,000–7,500 actual L1 transactions from VeData alone. 3. \~1,200,000 events/year — Total ecosystem footprint | Activity | Path | Events/year | Per ha/year | | ----------------------------------- | ------------- | ----------- | ----------- | | VeData batch anchors | A — Direct L1 | \~600,000 | \~50 | | Labor contracts (farmer ↔ worker) | A — Direct L1 | \~300,000 | \~25 | | Commercial escrow (farmer ↔ trader) | A — Direct L1 | \~60,000 | \~17 | | One-time setup (DID, NFT minting) | A — Direct L1 | \~100,000 | \~8 | | Path B audit decommits | B — via Hydra | \~2,190 | fixed | | Total |


| \~1,202,190 | 100/ha/year | Labor contracts and commercial escrow are direct Plutus L1 transactions — they need independent enforceability, not just Merkle inclusion. DID registrations (24,000) are within the \~100,000 setup events. minADA locks (\~75,000 ADA) are created within these setup transactions. All three figures are accurate — they answer different questions. ① is the cost-floor. ② is VeData's actual cadence. ③ is the full ecosystem planning footprint. #### M3 Demo vs M7 Threshold "10,000 updates → 1 tx" (M3 demo) proves VeData batching. "≥100,000 on-chain tx" (M7 requirement) is the cumulative total across all four transaction types over 1–2 months — not a single batch. #### Peak Load — M7 100,000 events ÷ 30 days ÷ 86,400s = \~0.039 events/second. Peak burst \~0.12–0.20/s. Cardano capacity: \~10 tx/s. OriLife peak = <2% of Cardano throughput. No congestion risk. #### ADA Locked | Location | ADA | | ------------------------------- | --------- | | minADA in 12,000 Farm NFTs | \~24,000 | | minADA in 24,000 farmer wallets | \~48,000 | | Commercial escrow | \~3,000+ | | Total | \~75,000+ | Per NFT: coinsPerUTxOByte (4,310) × \~307 bytes ≈ 1.32 ADA × 12,000 = \~15,840 ADA minimum; \~24,000 accounts for optional datum fields. Returned to owners on NFT burn. ### 7. PhoenixKey — One Identity, Many Applications USPTO #64/031,291 Architecture: PhoenixKey is built on Cardano's DID infrastructure (Identus/Atala PRISM standard), extending it with biometric hardware key management and seedless recovery. Identus handles W3C-compliant DID anchoring on Cardano; PhoenixKey adds the farmer-facing layer — fingerprint + face registration, hardware key generation, and app delegation — making the same DID standard usable by a farmer with no technical knowledge. Problem solved: TonFarm and Aladin were separate accounts with separate identities. PhoenixKey creates one DID anchored on Cardano, recognized across all OriLife-integrated apps — one source of truth on-chain. | Capability | Detail | | -------------- | ------------------------------------------------------- | | Registration | Fingerprint + face. No email, phone, or seed phrase | | Hardware key | Lives in secure chip, never leaves device | | App delegation | Apps receive scoped session keys; master key stays safe | | Recovery | Face auth on new device → full wallet recovery | | Key rotation | Swap key → DID unchanged → assets intact | 24,000 farmers will have Cardano DIDs without knowing what blockchain is. Each PhoenixKey registration = 1 L1 transaction, counted within the \~100,000 setup events in Section 6. ### 8. Midnight — Commercial Privacy Cardano is public — anyone can read transactions. Export businesses won't accept blockchain if competitors can see contract prices and partner lists. Midnight generates per-party View Keys: | Party | CAN verify | CANNOT see | | ---------------------- | ------------------------------- | ------------------------------------ | | GACC (Chinese Customs) | Origin, harvest date, GACC code | Contract price, quantities, partners | | EUDR Inspectors | GPS, deforestation-free proof | Commercial data | | Consumers | Cultivation history, region | Business data | View Keys generated automatically on datum\_confirmed event for export shipments. No manual distribution. No other blockchain simultaneously provides traceability transparency AND commercial privacy — this combination is unique to Cardano. ### 9. Multi-Application Architecture Both TonFarm and Aladin read from the same Farm NFT datum and same LampNet CIDs — one source of truth, no sync needed. One durian, four actors, one source of truth: T+0s: Farmer scans harvest on TonFarm → Bio-ID written to LampNet T+3–7s: Consumer in Ha Noi sees images on Aladin Trace (Layer 0) T+41–61s: Cardano confirms → GACC dossier auto-generated → Customs receives View Key via Midnight → Consumer app: "✅ Verified on Cardano" OriLife SDK (MIT, GitHub from M5): Bio-ID registration, origin verification, GACC/GS1 export, Midnight View Key creation, CID subscription. ### 10. Hydra — Path B Audit Settlement GS-VEDATA-MOSAIC-PUBLIC-01 Hydra serves one function: audit proof trail. It has no role in NFT datum updates, consumer image delivery, or consumer verification. Head config: 3 LampNet nodes · Hydra v1.3.0 · Long-lived Head (never closes in normal operation) Why long-lived: 12-hour contestation period makes frequent Open/Close impractical. Head runs indefinitely via incremental deposit/decommit. T=0: Open Head (one-time, \~580,000 lovelace) T=4h: Decommit Merkle root → L1 (\~450,000 lovelace) T=8h: Next decommit → L1 ... (repeat; Head never closes normally) v1.3.0 costs (official benchmarks, 2025-07-28): | Transaction | 3 parties | ADA | | --------------------- | ---------------- | ---- | | Init (one-time) | 580,000 lovelace | 0.58 | | Decommit (every 4–8h) | 450,000 lovelace | 0.45 | | Close (dispute only) | 540,000 lovelace | 0.54 | Daily cost: 450,000 × 6 = 2.70 ADA/day for entire system. Annual: \~985 ADA (\~$246 at $0.25/ADA). FanOut limit (\~37 UTxOs) is not a constraint — Mosaic commits 1 Merkle root UTxO per epoch. Hydra v2.0.0 roadmap: Directly Open Heads (no collectCom). Only HydraSettlementAdapter interface changes — Path A, SMT logic, datum schema, proof generation are entirely unaffected. Path independence (formal property): Path A operates correctly regardless of Hydra Head status, Path B deployment status, or Hydra version. Path B is additive — not a dependency. ### 11. Verified Results Verify:[ orilife.io/en/demo](https://www.orilife.io/demo) Identification: | Metric | Result | Conditions | | ----------------------------- | ------ | ----------------------------- | | Precision | \~99% | \~100 trees, current test set | | Recall | >90% | ±45° angle variation | | Re-identify after 30 days | ✅ Pass | Same fruit | | Distinguish 2 adjacent fruits | ✅ Pass | Field conditions, Dak Lak | M1 commitment: maintain \~99% Precision + raise Recall to ≥95% on 10,000-tree benchmark (4+ varieties, 4+ stages, 5+ lighting conditions). Operations: | Metric | Result | | --------------- | --------------------------- | | Response time | <3 seconds end-to-end | | On-device speed | >30 FPS (mid-range Android) | | Minimum device | Android 4GB RAM | | Data package | <1KB | M1 target: <1 second response. Consumer latency: | Layer | Latency | Event type | | ------------------------ | ----------------- | ---------------- | | Layer 0 — Optimistic | \~3–7s | All uploads | | Layer 1 — Pending | \~15–25s | All uploads | | Layer 2 — Confirmed | \~41–61s | Standard | | Layer 2 — PRIORITY\_HIGH | \~25–35s | Harvest events | | Push notification | <1s after confirm | WebSocket | | Peak load vs Cardano | <2% | \~0.039 events/s | On-chain evidence: * [VeData batch on Preprod](https://preprod.cardanoscan.io/transaction/a8dd2f28d7b4d4a162d752070d839496e671f608abde9bb95a021cbbe7574dde?tab=utxo) * [TonFarm legacy on TON](https://tonviewer.com/UQAftkW5i-ON2qIPIRub2Z8zZL_KzbvX8jPnF9-6uwnowmcD?section=nfts) * [github.com/OriLifeTrace](https://github.com/OriLifeTrace) ### 12. Milestone Technical Mapping Completed before GA: | Component | Status | Verify | | --------------------------------------- | ----------------- | -------------------------- | | TonFarm UX (farmers 50+) | ✅ 2 seasons | tonfarm.co | | AI PoC — fruit identification | ✅ Working | orilife.io/en/demo | | LampNet distributed storage | ✅ Working | lampnet.cloud | | VeData batch → Preprod (Path A) | ✅ Working | Preprod TxHash | | Institutional relationships 46 communes | ✅ Confirmed | Letter 351-CV/HNDT | | PhoenixKey DID concept | ✅ Design complete | Prototype | | Mosaic spec | ✅ Frozen | GS-VEDATA-MOSAIC-PUBLIC-01 | Per milestone: | Milestone | Key components | Status | | --------- | ---------------------------------------------------------------- | -------------------- | | M0 | Escrow + IOB setup | Not deployed | | M1 | AI fine-tuning + pipeline + Three-Layer Read PoC | PoC \~1K trees | | M2 | Mobile app + contract freeze + PRIORITY\_HIGH | TonFarm UX inherited | | M3 | Audit + Mainnet + BCT Portal + Hydra init + CID Subscription API | Preprod tested | | M4 | 500 ha field ops + harvest module + GACC export | Not deployed | | M5 | SDK + Compliance adapter + TonFarm/Aladin integration | In development | | M6 | Scale 3,000 ha + SLA tiers | Not scaled | | M7 | 12,000 ha + DR test + peak load | Not scaled | | M8 | B2B + MAGIC economics + impact report | Plan ready | *** Annex A v6.1 · April 2026 · GS-ORILIFE-GA-01 Open Source: [github.com/OriLifeTrace](http://github.com/OriLifeTrace) · USPTO: #64/030,398 · #64/031,291 · #64/031,472 · #64/032,593 # Annex B ## Legal & Compliance Context ### OriLife Platform: Legal Framework, International Compliance & Intellectual Property Document: Annex B — Legal & Compliance Context Version: v4.1 Updated: April 2026 Reference: GS-ORILIFE-GA-01 Proposer: Nguyen Hung Son— DDC Holdings, Dak Lak Status: Public — Attached to Governance Action Disclaimer: This document is informational, not legal advice. The Proposer is responsible for full compliance with all applicable regulations. ### 1. Overview — Why Legal Context Is OriLife's Advantage OriLife operates at the intersection of five legal systems directly affecting the Dak Lak durian supply chain for global export: Vietnam, China, the European Union, the United States, and Japan. Core Thesis: OriLife is not a voluntary solution. It is a solution mandated by at least 4 legal systems simultaneously — with hard deadlines that cannot be extended. No existing market solution addresses all of these requirements on a unified platform. Significance for dReps: A YES vote means the Cardano community invests in a project that the market is required to adopt — not a startup that can be eliminated by market forces. Legal deadlines create mandatory demand, independent of marketing or voluntary adoption. ### 2. Vietnamese Legal Framework #### 2.1 Decision 1236/QĐ-TTg — National Blockchain Strategy
FieldDetail
Number1236/QĐ-TTg
Sourcehttps://vanban.chinhphu.vn/?pageid=27160&docid=211462
Issuing AuthorityPrime Minister of Vietnam
Year2024
ScopeNational blockchain strategy for 2024–2030
Relevant Content: Assigns the Ministry of Agriculture and Environment to research and apply blockchain in plantation management and agricultural traceability. Priority deployment in 2024–2026 for key products and OCOP products. Significance for OriLife: OriLife is executing a mission assigned by the Vietnamese Government — not experimenting with an idea. This is a critical distinction when evaluating adoption risk. Significance for Cardano: If OriLife is selected as 1 of 5 national strategic platforms, Cardano becomes the blockchain officially used by a government in agriculture — a first-of-its-kind milestone. #### #### 2.2 Resolution 57-NQ/TW — Politburo Directive
FieldDetail
Number57-NQ/TW
Sourcehttps://xaydungchinhsach.chinhphu.vn/toan-van-nghi-quyet-ve-dot-pha-phat-trien-khoa-hoc-cong-nghe-doi-moi-sang-tao-va-chuyen-doi-so-quoc-gia-119241224180048642.htm
AuthorityPolitburo — Central Committee
LevelHighest-level strategic document
Relevant Content: AI and Blockchain are identified as national strategic technologies to be mastered. Agriculture tops the priority list for smart production. Strategic Significance: Resolution 57 creates a political corridor at the highest level. This is not a ministry-level policy that can change with personnel rotation — it is a Politburo directive, stable across multiple terms. #### 2.3 Decision 5272/QĐ-BNNMT — Durian Traceability Pilot
FieldDetail
Number5272/QĐ-BNNMT
Sourcehttps://mae.gov.vn/Pages/chitietvanbandh.aspx?ItemID=3451
Issuing AuthorityMinistry of Agriculture and Environment
Date IssuedDecember 13, 2025
ScopeDurian Traceability Pilot
Pilot PeriodJanuary 1 – June 30, 2026
Summary DateJuly 10, 2026
ExpansionNationwide by end of 2026
Relevant Content: On April 4, 2026, the first shipment was exported via the Green Lane process — but still uses physical labels that can be peeled and re-attached. OriLife solves the weakness that the government's current plan has not yet addressed: biological identification directly on the product, no labels needed. Significance for OriLife: This is an opportunity to demonstrate value superior to the traditional labeling system during the national pilot. If successful, OriLife will be a strong candidate for the nationwide expansion at end of 2026. #### 2.4 Summary of Vietnamese Legal Documents
DocumentAuthorityRelevant ContentImpact on OriLife
Decision 1236/QĐ-TTg (2024)Prime MinisterBlockchain for plantation & OCOP 2024–2026OriLife is the implementation vehicle
Resolution 57-NQ/TWPolitburoAI + Blockchain as strategic tech, Agriculture priority #1Highest political corridor
Decision 5272/QĐ-BNNMT (2025)Ministry of Ag & EnvDurian traceability pilot 01/01–30/6/2026, expand end 2026OriLife solves physical label weakness
Circular 11/2026/TT-BCTMinistry of Industry & TradeMandatory traceability connection from 01/12/2026Hard legal deadline
Food Safety Law 55/2010National AssemblyFood traceability responsibilityLegal foundation
Product Quality Law 78/2025/QH15National AssemblyProduct quality standards revisionLegal basis for pilot decisions
Cybersecurity Law 116/2025/QH15 (effective July 1, 2026)National AssemblyVietnamese user data stored in Vietnam; foreign service providers must establish local presenceLampNet Sovereign Data Residency — compliant with new law effective during all OriLife deployment phases
Decree 13/2023/NĐ-CPGovernmentPersonal data protectionPhoenixKey + end-to-end encryption
*** ### 3. Circular 11/2026/TT-BCT — Deadline December 1, 2026 #### 3.1 Document Information
FieldDetail
Number11/2026/TT-BCT
Sourcehttps://chinhphu.vn/?pageid=27160&docid=217126&classid=0
AuthorityMinistry of Industry and Trade, Vietnam
Date IssuedFebruary 27, 2026
Effective DateApril 16, 2026
Mandatory DeadlineDecember 1, 2026
ScopeAll commercial food production and business establishments
#### 3.2 Directly Relevant Articles Article 3 — Traceability Code: The Circular defines a traceability code as "the final identification code at each stage, encoded in a data carrier." OriLife's Bio-ID is precisely that identification code — but the data carrier is the durian fruit itself (biological skin texture), not a physical label. This approach complies with the Circular's definition while eliminating the possibility of forgery. The Circular also requires a "one step forward — one step back" principle: each stage must link to the previous and next stages. VeData ensures this continuity: Tree Registration → Cultivation Log → Fruit Registration → Harvest → Transfer → Processing → Export. Each step has a cryptographic link to the step before and after, impossible to break. Article 5 — Mandatory Stored Information: | Circular 11 Requirement | OriLife Delivers Via | | -------------------------------------- | -------------------------------------------- | | Name, address, facility code | PhoenixKey DID — decentralized identity | | Product name and images | Bio-ID + raw images on LampNet | | Identification code, traceability code | Farm NFT + Bio-ID on Cardano Mainnet | | Weight, quantity, batch code | FarmDatum batch\_sequence + Merkle Tree | | Location, event timestamp | GPS coordinates + digitally signed timestamp | Article 6 — Record Retention and Provision: The Circular requires minimum 12-month retention and record provision within 24 hours. OriLife exceeds requirements: Cardano Mainnet stores immutably forever (not 12 months). API Gateway responds in seconds (not 24 hours). Article 14 — Cross-agency Connection: The Circular requires the system to connect with domestic and international databases. OriLife's Compliance Adapter SDK exports GS1 EPCIS v2.0 and GACC — standards that Vietnam's Ministry of Public Security, Ministry of Health, Ministry of Agriculture, and Chinese Customs can all read natively. Article 15 — Hard Deadline December 1, 2026: All food production establishments must connect to the Traceability System from December 1, 2026. OriLife's timeline completes M7 (Mass Rollout) by October 2026 — operational for at least 2 months before the deadline. #### 3.3 Consequences of Non-Compliance | Violation | Consequence | | ------------------------------------------ | ------------------------------------------- | | No connection after 01/12/2026 | Product recall ordered | | Failure to provide records within 24 hours | Administrative fines + operations suspended | | Untruthful traceability data | Criminal prosecution | | Export without GACC compliance | Shipment rejected at Chinese port | *** ### 4. Chinese Standards — GACC #### 4.1 Overview The General Administration of Customs of China (GACC) controls all agricultural imports into China. China accounts for >90% of Vietnam's durian export revenue ($3.36 billion USD). Orders 248 & 249 (effective 2022, tightened 2024) govern production facility registration and imported food safety management. #### #### 4.2 Requirements and OriLife Response | GACC Requirement | OriLife Delivers Via | | --------------------------------------- | ------------------------------------ | | Registered plantation code verification | Farm NFT on Cardano | | Packing facility code | PhoenixKey DID of the enterprise | | Certificate of Origin | Merkle Proof on-chain | | Phytosanitary certificate | VeData evidence trail | | Residue control (Cadmium, Auramine O) | Immutable cultivation log on LampNet | #### 4.3 Lessons from the 2025 Scandal The 2025 durian scandal ([source](https://vnexpress.net/gan-2-000-container-sau-rieng-xuat-khau-mac-ket-vi-tam-ngung-xet-nghiem-4955678.html)) — 17 individuals prosecuted, 55+ plantation codes revoked, 2,000 containers stuck — is direct evidence that the current traceability system (QR labels, paperwork) has completely failed. Root Cause: Fraud occurred because the data carrier (label) can be separated from the product. DDC Holdings experienced this firsthand with legacy TonFarm (see Annex A, Section 1). When Bio-ID is the fruit's own skin, there is no way to fake the origin. #### 4.4 Midnight View Key for GACC Export enterprises share a View Key with Chinese Customs:
Chinese Customs with View KeyResult
CAN verifyOrigin, harvest date, GACC code, phytosanitary
CANNOT seeContract price, detailed quantities, buyer identity
CANNOT seeInformation about other shipments from the same company
This is a real-world business requirement — no existing blockchain solution simultaneously provides customs transparency and commercial confidentiality. Midnight on Cardano is the only primitive that solves this. *** ### ### 5. European Union Standards — EUDR & Food Safety #### 5.1 EUDR — EU Deforestation Regulation
FieldDetail
NumberEU 2023/1115
Applicable FromLate 2025 (large enterprises), 2026 (SMEs)
ScopeDeforestation-risk commodities: timber, cattle, cocoa, coffee, palm oil, rubber, soy
Why Relevant: Dak Lak is Vietnam's coffee capital. Coffee export revenue $8.4 billion USD (2024), EU share 46.7%. While the MVP focuses on durian, OriLife SDK can expand to coffee — EUDR creates a massive B2B SaaS market (see M8 in GA). | EUDR Requirement | OriLife Delivers Via | | ----------------------------------------- | ----------------------------------------------- | | Geographic coordinates (polygon) per plot | GPS boundary in FarmDatum | | No deforestation after 31/12/2020 | LampNet Sovereign Data Proof + signed timestamp | | Verifiable due diligence | Immutable audit trail on-chain | | Land use legality | PhoenixKey DID linked to legal records | #### 5.2 EU Food Safety | Requirement | OriLife Response | | -------------------------------- | --------------------------------------------------- | | Farm-to-fork traceability | Full audit trail via VeData | | Record retention ≥12 months | Cardano Mainnet — immutable forever | | Record provision within 24 hours | API Gateway 24/7, response in seconds | | Traceability to batch level | Traceability to individual fruit (Bio-ID per fruit) | *** ### ### 6. United States Standards — FSMA 204 | Field | Detail | | --------- | ------------------------------------------- | | Full Name | Food Safety Modernization Act — Section 204 | | Authority | FDA, United States | | Deadline | January 2026 (large enterprises) | #### Core Requirements Traceability Lot Code (TLC): Each batch must have a unique traceability code throughout all stages. Critical Tracking Events (CTE): Record events: Harvesting, Cooling, Initial Packing, Shipping, Receiving. 24-hour Rule: When FDA requests, complete CTE records must be provided within 24 hours. | FSMA 204 Requirement | OriLife Delivers Via | | --------------------- | ------------------------------------------------- | | Traceability Lot Code | Bio-ID = natural TLC, impossible to forge | | Harvesting CTE | Harvest module — auto-capture at cutting | | Shipping CTE | Compliance Adapter SDK records transfer events | | 24-hour records | Cardano on-chain + realtime API | | Interoperability | GS1 EPCIS v2.0 export compatible with FDA systems | Market Significance: The US is a large untapped durian market, hindered by FSMA barriers. OriLife creates infrastructure for Vietnam to enter the US market. *** ### 7. International Standards — GS1 EPCIS v2.0 & ISO 22005 #### 7.1 GS1 EPCIS v2.0 GS1 EPCIS is the common language for the entire global food supply chain. Used by: Walmart, Carrefour, AEON, Amazon Fresh, and customs agencies in EU/US/Japan/Korea. Version 2.0 (latest, adoption from 2024) adds: | New Feature | Significance for OriLife | | ----------------------- | -------------------------------------------------- | | JSON-LD alongside XML | Native REST API, easy web integration | | W3C EPCIS Ontology | Linked Data for cross-system queries | | Digital Link (QR → URI) | Scan directly to on-chain data | | Blockchain anchoring | Official provision supporting blockchain anchoring | OriLife Compliance Adapter SDK exports GS1 EPCIS v2.0 with blockchain proof verifiable on Cardano Explorer — compatible with GS1's official blockchain anchoring provision. #### 7.2 ISO 22005 — Food Traceability | ISO 22005 Principle | OriLife Mapping | | ----------------------- | -------------------------------------- | | Object identification | Bio-ID as unique biological identifier | | Information recording | VeData audit trail | | Information linkage | Merkle Tree on Cardano | | Traceability capability | Cardano API + Compliance SDK | | System verification | IOB milestone review | ### 8. Japanese Standards — JAS & MRL Japan is a high-potential premium durian market. Quality requirements are extremely stringent — higher than EU and US. Japanese consumers are willing to pay the highest premiums for products with transparent traceability. #### JAS (Japanese Agricultural Standard) | JAS Requirement | OriLife Delivers Via | | ------------------------------- | --------------------------------------- | | Detailed cultivation log | VeData evidence trail with photos/video | | Fertilizer types used | Immutable cultivation log on LampNet | | Pesticides (name, date, dosage) | VeData records, signed at source | | Seed origin | Farm NFT metadata | #### MRL — Maximum Residue Limits Japan's MRL thresholds are significantly lower than Codex Alimentarius (e.g., Chlorpyrifos 50× lower, Cypermethrin 40× lower). Immutable cultivation logs on LampNet help farmers prove they did not use restricted substances — rather than just proving "below threshold." *** ### 9. Consolidated Compliance Matrix #### OriLife Meets 9/9 Standards
MarketStandardCore RequirementOriLifeStatus
VietnamDecision 1236/QĐ-TTgBlockchain for plantations 2024–2026✅Exceeds
VietnamCircular 11/2026/TT-BCTBCT Portal connection from 01/12/2026✅Met (M3)
ChinaGACC (Orders 248/249)Plantation code, phytosanitary, batch✅Met (M4)
EUEUDRGPS polygon, deforestation-free✅Met
EUEU Food SafetyFarm-to-fork, ≥12 months retention✅Exceeds
USFSMA 204Traceability Lot Code, 24h records✅Met
InternationalGS1 EPCIS v2.0ObjectEvent, blockchain anchoring✅Met (M5)
InternationalISO 22005Food traceability system✅Met
JapanJAS + MRLCultivation log, ultra-low residues✅Planned M8 expansion
#### #### Comparison with Existing Solutions | Solution | QĐ 1236 | CT11 | GACC | EUDR | FSMA | GS1 v2.0 | ISO | EU FS | JAS | Total | | ------------------------------------ | ------- | ------- | ------- | ---- | ------- | -------- | ------- | ------- | ------- | ----- | | OriLife | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | 9/9 | | Standard QR labels | ❌ | Partial | Partial | ❌ | ❌ | Partial | ❌ | Partial | ❌ | 0–3/9 | | Blockchain + labels (legacy TonFarm) | ❌ | Partial | Partial | ❌ | Partial | Partial | Partial | Partial | Partial | 1–4/9 | | Blockchain without AI | ❌ | Partial | Partial | ❌ | Partial | Partial | Partial | Partial | Partial | 1–4/9 | Conclusion: No existing market solution simultaneously meets all 9 standards on a unified platform. OriLife achieves 9/9 through a combined architecture of AI vision (label-free Bio-ID) + Cardano eUTXO (batch O(1)) + Midnight (commercial privacy) + VeData (5-layer validation). ### 10. Intellectual Property — Protection Portfolio #### 10.1 Vietnamese Copyright
FieldDetail
Work"Digitizing Agricultural Assets in Vietnam's Central Highlands Using Blockchain Technology"
Certificate No.4420/2025/QTG
Date IssuedJune 2, 2025
AuthorityCopyright Office — Ministry of Culture, Sports and Tourism
Author / OwnerNguyễn Văn Chinh (DDC Holdings)
This copyright confirms DDC has been researching and deploying blockchain in agriculture in Vietnam's Central Highlands since 2024 — the knowledge foundation inherited by OriLife. #### 10.2 USPTO Provisional Patent Applications Four PPAs protect the entire tech stack. PPAs establish a Priority Date — the date GreenSun Tech formally claims ownership. Within 12 months, a Non-Provisional can be filed for full 20-year protection.
InventionUSPTO #Filing DateProtection Scope
OriLife Platform#64/030,398April 6, 2026Label-free biological identification, AI edge, harvest protocol
PhoenixKey#64/031,291April 6, 2026Hardware key management, app delegation, DID recovery
LampNet#64/031,472April 7, 2026Distributed storage, data sovereignty, multi-layer encryption
VeData#64/032,593PendingMulti-tier validation, blockchain batching, trust scoring
Applicant: GreenSun Tech. Filed by: Nguyen Thi Kim Ngan. Significance for Cardano Treasury: Technology with legal IP protection is original IP. If competitors copy the architecture after the PPA filing date, GreenSun Tech has legal recourse. Cardano Treasury is funding technology with legal protection — not a fork or adaptation. ### 11. Cybersecurity Law — Data Sovereignty #### Requirements Cybersecurity Law 116/2025/QH15 (effective July 1, 2026, replacing Cybersecurity Law 24/2018), Article 25.3: Enterprises providing online services in Vietnam must store Vietnamese user data domestically. Foreign enterprises must additionally establish a branch or representative office in Vietnam. Timing advantage: All OriLife deployment milestones (M4–M8: July–November 2026) operate entirely under this new framework — not the expired 2018 law. OriLife is designed for the current legal environment, not a transitional one. OriLife data qualifies as "important": farmer identification (DID, biometric hash), agricultural production data (location, yield), export and supply chain information. #### Two-Layer Solution Layer 1 — Cardano: Stores only Root Hash (32 bytes) — no personal or production information. Does not violate domestic storage requirements as there is no PII on-chain. Layer 2 — LampNet: Actual data (images, video, metadata) stored on LampNet nodes with priority for Vietnam-based nodes. Has an on-chain mechanism to prove storage location (Sovereign Data Residency Proof) — compliant with Decision 1236/QĐ-TTg. LampNet's domestic node priority and Sovereign Data Residency Proof mechanism satisfies both the data localization requirement (Article 25.3) and the traceability requirement (Article 25.2d) of Luật An ninh mạng 116/2025/QH15 — making OriLife fully compliant with the cybersecurity framework in force throughout its entire deployment period. #### Compliance with Decree 13/2023 — Personal Data Protection
RequirementOriLife Response
Consent before collectionOnboarding flow: explicit consent screen
Clear collection purposeUsed only for traceability
Access / deletion rightsPhoenixKey manages permissions; soft delete
Data securityEnd-to-end encryption on LampNet; hardware keys
No overseas transferSovereign Data Residency policy
AI-generated content prohibitionPhoenixKey biometric authentication is not generative — it verifies, not creates. Compliant with Article 7.2g of Cybersecurity Law 116/2025/QH15 prohibiting AI deepfakes
*** ### 12. Open Source and IP Protection Strategy Clear Classification OPEN SOURCE — MIT License (from M5) Published for transparency and user asset sovereignty. Any independent party can verify that user keys, data ownership, and recovery mechanisms work as described — no trust required. * FarmDatum Smart Contract (Aiken) — full source, auditable * PhoenixKey Key Management SDK — key generation, delegation, and recovery flows only; biometric matching core is excluded * Wallet recovery tools — seed phrase derivation, DID resolution * API Gateway Documentation + OpenAPI Spec OPEN FOR INTEGRATION — Restricted License (from M5) Interfaces published to enable third-party applications to build on OriLife infrastructure and participate in the MAGIC economy. SDK calls consume MAGIC credits — expanding the ecosystem without exposing core IP. * OriLife Edge SDK — Bio-ID registration and verification interface (not the underlying algorithm) * Compliance Adapter SDK — GACC + GS1 EPCIS v2.0 export * LampNet Storage SDK — CID pinning and retrieval interface * CID Subscription API — WebSocket push integration PROPRIETARY — Protected by USPTO PPAs Core technology retained as competitive moat. Not open-sourced under any license. * Bio-ID Generation Algorithm — the specific feature extraction method * AI Model Weights — fine-tuned on Đắk Lắk durian field data * VeData Protocol Core — validation logic and trust scoring * LampNet Node Software — distributed storage coordination * PhoenixKey Biometric Core — matching and liveness detection If GreenSun Tech ceases operations: MIT-licensed smart contracts and key recovery tools give the community everything needed to continue operating OriLife and recover user assets. The proprietary core affects performance and accuracy — not basic functionality or data access. Why This Strategy Is Optimal For the Cardano Ecosystem: * Smart contracts and key management are fully auditable — no trust required for user asset security * Integration SDK enables any developer to build on OriLife and participate in the MAGIC economy * This is a public good infrastructure, not a closed silo For GreenSun Tech: * Bio-ID algorithm and AI model weights remain proprietary — the technical moat is intact * Revenue model: B2B SaaS for VeData and LampNet compute, paid via MAGIC credits * USPTO PPAs protect the full stack from copying Common dRep question: "If GreenSun goes bankrupt, what remains?" Answer: Users can recover all assets via MIT-licensed PhoenixKey recovery tools. Developers can continue running OriLife using open smart contracts and integration SDKs. The proprietary core affects accuracy — not access. #### Open Source Governance | Field | Detail | | ------------ | -------------------------------------------- | | Repositories | github.com/OriLifeTrace (Organization) | | License | MIT for SDK · Apache 2.0 for Smart Contracts | | Contribution | Pull Request via GitHub | | Security | Responsible disclosure policy | | Bug Bounty | After Mainnet launch (M3+) | *** ### 13. Legal Mapping to 9 Milestones | Milestone | Related Legal Requirements | Compliance Deliverable | | ------------------ | ------------------------------------------------------- | -------------------------------------------- | | M0 Foundation | Alliance legal contracts, notarized MOU | Public notarized MOU | | M1 Alpha | No specific legal requirements | — | | M2 Beta App | Consent flow (Decree 13/2023) | Onboarding with explicit consent | | M3 Audit + Mainnet | Smart contract audit, BCT Portal API (CT11 Art. 14) | Audit report + BCT API test | | M4 Pilot | GACC pilot export (Orders 248/249), GPS boundary (EUDR) | Customs declaration for pilot batch | | M5 SDK Open | MIT License, GS1 EPCIS v2.0 validation | GitHub public + GS1 validator pass | | M6 Beta Rollout | Sovereign Data Residency (Cybersecurity Law) | LampNet VN nodes active | | M7 Mass Rollout | CT11 deadline readiness (01/12/2026) | System operational ≥2 months before deadline | | M8 Global | FSMA 204, JAS/MRL, EUDR compliance docs | B2B contracts + compliance documentation | *** ### 14. Compliance Declaration #### Vietnamese Law: * Full compliance with Decision 1236/QĐ-TTg and the National Blockchain Action Program * Full compliance with Circular 11/2026/TT-BCT — system operational ≥2 months before the 01/12/2026 deadline * Vietnamese user data stored per Cybersecurity Law — LampNet Sovereign Data Residency. Full compliance with [Cybersecurity Law no 116/2025/QH15](https://vanban.chinhphu.vn/?pageid=27160\&docid=216499) (effective July 1, 2026) — the law in force throughout all OriLife deployment phases M4–M8. * Personal data protection per Decree 13/2023/NĐ-CP #### International Standards: * GS1 EPCIS v2.0 compliance in data export (from M5) * GACC (Orders 248/249) compliance for China export shipments (from M4) * Compatible with FSMA 204 (US FDA) and EUDR (European Union) * Meets ISO 22005 food traceability standards * Meets Japanese JAS and MRL standards #### Intellectual Property: * Core technology is original IP of GreenSun Tech, protected by 4 USPTO PPAs * DDC Holdings copyright No. 4420/2025/QTG * No infringement of any third-party patents or copyrights * Open source components released with clear licensing (MIT + Apache 2.0) #### Cardano Treasury: * All Alliance members participating in the project — including Duc Tiger and Nguyen Hung Son— receive reasonable compensation from the GA budget, allocated by role and actual contribution * Duc Tiger is PM, also dRep/SPO TIGER — publicly disclosed, voting ABSTAIN on this GA and all Withdraw Treasury GAs during the voting period of this GA * No token allocation to voters * No conflicts of interest beyond those already disclosed * All information in the GA dossier is truthful and independently verifiable *** Annex B — Legal & Compliance Context Version: 4.1 · April 2026 Reference: GS-ORILIFE-GA-01 USPTO: #64/030,398 · #64/031,291 · #64/031,472 · #64/032,593

# Annex C ## Detailed Financial Breakdown ### OriLife Platform: Detailed Budget Breakdown Document: Annex C — Detailed Financial Breakdown Version: v4.2 Updated: April 24th, 2026 Reference: GS-ORILIFE-GA-01 Proposer: Nguyen Hung Son— DDC Holdings Status: Public — Attached to Governance Action Total Budget: 2,400,000 ADA = $600,000 USD, Anchor Rate: $0.25 USD/ADA Milestones: 9 (M0–M8) ### Budgeting Principles #### 1. Personnel is the largest expense — and rightly so The current technical team is operating at maximum capacity. To complete 180 million fruits across 12,000 ha before the end of 2026, additional specialized engineers and field operations staff are needed. Vietnamese labor costs are more efficient than international agencies, and the team uses AI-assisted workflows, achieving 2–3× the throughput of conventional processes. #### 2. Mobilization Advance 15% — Hire now, deploy now M0 disburses 360,000 ADA immediately upon GA ratification so the Alliance can recruit additional staff. This advance includes automatic 90-day Clawback if M1 is not submitted, and mandatory 30-day Spending Report. Not "free money" — this is a mobilization fund with legal constraints. #### 3. AI costs are fine-tuning, not training from scratch The AI budget in M1 is for specialized fine-tuning of existing small vision models for the Dak Lak durian problem — not building new models from scratch. GPU resources for fine-tuning are sourced from the LampNet community, not from the GA budget. #### 4. Cost-optimized audit Strategy: Reuse Intersect's battle-tested Escrow template → audit only customization (\~$5–15K instead of $25K+) → apply for Intersect Community Audit Fund in parallel → Bug Bounty post-launch supplement. #### 5. Budget anchored in USD at a conservative rate All actual costs are denominated in USD. The $0.25/ADA rate was chosen below market price to ensure sufficient budget even if ADA corrects. Symmetric commitment: Alliance self-funds if ADA drops, returns/reinvests surplus if ADA rises. #### 6. Every expense has documentation GreenSun Tech commits to providing complete VAT invoices (Vietnamese vendors), invoices/receipts (international vendors), and contracts/SoWs (contractors) as requested by IOB. #### 7. Compensation allocation philosophy All Alliance members participating in the project — including Duc Tiger and Nguyen Hung Son— receive reasonable compensation from the GA budget. Compensation is allocated by role, actual workload, and measurable contribution at each milestone — not as a fixed amount predetermined for the entire project. 8\. Operational fees are user-borne, not GA-funded All on-chain transaction fees generated by platform activity — VeData anchors, labor contracts, commercial escrow, Hydra audit settlements — are paid by users via MAGIC credits converted from local fiat currency. These costs are entirely separate from the 2,400,000 ADA GA budget, which covers only: infrastructure development, 12,000 ha deployment, and SDK open-sourcing. Why individual compensation is not listed as fixed amounts: * ADA price volatility: Actual USD value received depends on the exchange rate at disbursement. Compensation must be adjusted flexibly based on the actual available USD budget. * Multi-role and flexible assignments: In a startup project with 3 companies, individuals often hold multiple roles — engineer doubling as project manager, coordinator doubling as trainer. Compensation reflects total contribution, not a single fixed job title. * Unpredictable field costs: Staff traveling to 15 highland districts face significantly different travel, accommodation, and time costs. Compensation includes offsetting these. * Efficiency measured by milestone: The Alliance commits to paying by results, not by hours. If a milestone is completed early and efficiently, compensation reflects that. 9\. Contingency rates reflect risk type, not milestone size | Risk type | Rate | Milestones | | ------------------------------------------- | ------------ | -------------- | | AI/ML iteration — cannot be pre-modeled | 25% | M1 | | ADA price hedge — pre-positioned | \~52% buffer | M2 | | Field logistics — highland terrain, weather | 12–57% | M4, M6 | | Well-defined scope — known costs | 5–10% | M3, M5, M7, M8 | A higher rate reflects honest uncertainty in that activity type — not lower confidence in the project overall. #### Total Buffer Explained Buffer rates vary by milestone based on the dominant risk type — not as a blanket reserve. M1 — 25% contingency: AI fine-tuning is the highest-uncertainty activity. Reaching Recall ≥95% on a 10,000-tree multi-variety benchmark may require 1 iteration or 5; field conditions introduce variables that cannot be pre-modeled. M2 — 52% buffer: Serves as the primary ADA price hedge. M2 is the last milestone before Mainnet launch. If ADA has depreciated significantly since M0, the Alliance draws on this buffer rather than requesting additional Treasury funds. The buffer is pre-positioned, not speculative. M4 — 57% buffer: Highland pilot deployment carries unpredictable logistics — road conditions, harvest timing, farmer availability across 1–2 districts. Buffer funds emergency team reinforcement if onboarding stalls. M4 is the milestone with the highest real-world friction; underfunding it risks cascading delays to M6 and M7. M5 — 54% buffer: SDK open-sourcing scope depends on the state of the codebase after M3 audit. If audit surfaces architectural changes, the buffer covers re-engineering without delaying M6. M3 and M7 carry tight buffers (5% and 15%) because their scope is well-defined: M3 is audit + Mainnet deployment with known costs; M7 is logistics and infrastructure scale with field-tested data from M4 and M6. All buffers are locked in Intersect's Escrow. Unused portions follow Surplus policy (Annex D, Scenario 6): Alliance reimbursement first, then contingency, then ecosystem reinvestment — public report within 14 days after M8. Transparency commitment: Total personnel costs per milestone are reported in monthly Spending Reports and milestone Completion Reports, with valid documentation (contracts, invoices). IOB has the right to request detail on any line item. *** ### ### Summary by Milestone
#MilestoneADAUSD%
M0Foundation + Mobilization Advance360,000$90,00015.0%
M1Alpha — 750,000 sample fruits260,000$65,00010.8%
M2Beta App + Contract Freeze220,000$55,0009.2%
M3Audit + Mainnet Launch180,000$45,0007.5%
M4Pilot — 7.5 Million fruits / 500 ha280,000$70,00011.7%
M5SDK Open + Multi-app200,000$50,0008.3%
M6Beta Rollout — 45 Million fruits / 3,000 ha260,000$65,00010.8%
M7Mass Rollout — 180 Million fruits / 12,000 ha280,000$70,00011.7%
M8Global Integration + Sustainability360,000$90,00015.0%
Total
2,400,000$600,000100%
Constraint checks: * ✅ M0 = M8 = 15% (symmetric advance ↔ sustainability) * ✅ No milestone > 20% * ✅ Logarithmic scaling: 750K → 7.5M → 45M → 180M fruits *** ### Summary by Category
CategoryUSD%
Additional personnel (full project recruitment)$220,00036.7%
Field operations (DDC Holdings)$105,00017.5%
Technical infrastructure & scaling$72,00012.0%
Security audit + Bug Bounty$20,0003.3%
AI fine-tuning + Data collection & labeling$28,0004.7%
Legal, compliance & registration$25,0004.2%
SDK, integration & documentation$22,0003.7%
B2B integration & international partnerships$20,0003.3%
Impact assessment & reporting (third-party)$15,0002.5%
Community, AMA & communications$12,0002.0%
Consolidated contingency$61,00010.2%
TOTAL$600,000100%
*** ### M0 — Foundation + Mobilization Advance 360,000 ADA · $90,000 · 15.0% · May Week 1–2 Recruit additional staff, establish legal and technical infrastructure, deploy Escrow contract. #### Breakdown 0.1 Personnel — Immediate Recruitment
ItemUnitQtyUnit PriceTotal
Senior AI engineer (6-month contract)person2$3,500/mo × 1 mo advance$7,000
Backend/smart contract engineer (6-month contract)person2$3,000/mo × 1 mo advance$6,000
Mobile engineer (6-month contract)person1$3,000/mo × 1 mo advance$3,000
SDK engineer + Technical writerperson1$2,500/mo × 1 mo advance$2,500
DDC field coordinatorperson2$1,200/mo × 1 mo advance$2,400
DDC field staffperson6$800/mo × 1 mo advance$4,800
Total personnel M0


$25,700
Note: This is the first month's recruitment cost. Subsequent months are covered within M1–M7 respectively. 0.2 Legal & Setup
ItemQtyUnit PriceTotal
Notarized MOU between 3 Alliance companies1$2,000$2,000
Draft new employment contracts (14 positions)14$200$2,800
Additional legal registrations (permits, tax)1$1,500$1,500
Cardano/crypto compliance legal counsel1$3,000$3,000
Total legal M0

$9,300
0.3 Technical Infrastructure Setup
ItemQtyUnit PriceTotal
Escrow smart contract development + Preprod deploy1$5,000$5,000
Dedicated Cardano Preprod node (6 months prepaid)1$200/mo × 6$1,200
Schema Registry (Apicurio) setup1$500$500
CI/CD pipeline + GitHub Actions1$800$800
Additional development devices (test phones)10$150$1,500
Total infrastructure M0

$9,000
0.4 Operations & Communications
ItemQtyUnit PriceTotal
Dak Lak office space (6 months)1$500/mo × 6$3,000
Intersect Forum post + Community call1$500$500
HCM ↔ Dak Lak travel for kickoff4 trips$300$1,200
Total operations M0

$4,700
0.5 Contingency M0 (15%) | Item | Calculation | Total | | ----------- | ------------- | ------ | | Contingency | 15% × $48,700 | $7,305 | M0 risks: Recruitment slower than expected, additional legal fees. M0 Summary | Category | USD | | --------------------------- | ------- | | First-month personnel | $25,700 | | Legal & setup | $9,300 | | Technical infrastructure | $9,000 | | Operations & communications | $4,700 | | Contingency (15%) | $7,305 | | TOTAL M0 | $55,705 | | Budget M0 | $90,000 | | Buffer | $34,295 | Buffer M0 ($34K): For cases requiring additional hires or second-month payroll before M1 disburses. Unused portion rolls to M1. *** ### M1 — Alpha: Identify 750,000 Sample Fruits 260,000 ADA · $65,000 · 10.8% · May–June #### Breakdown 1.1 Personnel (project months 2–3)
ItemUnitQtyUnit PriceTotal
AI engineer (continued from M0)person × month2 × 2$3,500$14,000
Pipeline operations engineerperson × month1 × 2$3,000$6,000
Total personnel M1


$20,000
1.2 Field Data Collection
ItemUnitQtyUnit PriceTotal
DDC field team (reinforced)person × day5 × 10$80$4,000
Field travel (fuel, vehicles)trip30$25$750
Additional equipment (power banks, mounts)set5$50$250
Total collection


$5,000
1.3 Data Labeling
ItemUnitQtyUnit PriceTotal
Semi-automated labeling (CVAT)image50,000$0.15$7,500
Human quality reviewhour150$15$2,250
Labeling platform feesmonth2$200$400
Total labeling


$10,150
1.4 Independent Benchmarking
ItemQtyUnit PriceTotal
Third-party AI benchmarking1$5,000$5,000
A/B testing infrastructure1$500$500
Benchmark report writing3 days$200$600
Total benchmarking

$6,100
1.5 Core Database Infrastructure
ItemQtyUnit PriceTotal
PostgreSQL 16 cluster (3 nodes, 2 months)1$600/mo × 2$1,200
Milvus DiskANN cluster (2 months)1$800/mo × 2$1,600
CDN for OTA model updates1$300$300
Total infrastructure

$3,100
1.6 Contingency M1 (25%) | Item | Calculation | Total | | ----------- | ------------- | ------- | | Contingency | 25% × $44,350 | $11,088 | High contingency (25%) because AI fine-tuning cannot precisely predict the number of iterations needed to reach Recall ≥95%. M1 Summary | Category | USD | | ------------------------ | ------- | | Personnel | $20,000 | | Field data collection | $5,000 | | Data labeling | $10,150 | | Independent benchmarking | $6,100 | | Database infrastructure | $3,100 | | Contingency (25%) | $11,088 | | TOTAL M1 | $55,438 | | Budget M1 | $65,000 | | Buffer | $9,562 | *** ### M2 — Beta App + Contract Freeze 220,000 ADA · $55,000 · 9.2% · June–July #### Breakdown 2.1 Personnel
ItemUnitQtyUnit PriceTotal
Mobile engineer (Android production)person × month1 × 2$3,000$6,000
Aiken smart contract engineerperson × month1 × 2$4,000$8,000
Backend engineer (PhoenixKey integration)person × month1 × 1.5$3,000$4,500
Total personnel M2


$18,500
2.2 Testnet Infrastructure
ItemQtyUnit PriceTotal
Dedicated Cardano Preprod node2 months$200$400
Milvus test cluster2 months$500$1,000
PostgreSQL test2 months$150$300
API Gateway (test environment)2 months$100$200
Total infrastructure

$1,900
2.3 Field Testing — 1,000 Trees
ItemQtyUnit PriceTotal
DDC team (reinforced)5 people × 2 weeks$200$2,000
Travel & logistics15 trips$40$600
4G SIM cards for test devices10$10$100
Total testing

$2,700
2.4 Documentation & Demo | Item | Qty | Unit Price | Total | | ------------------------------ | ----------- | ----------- | ----- | | Demo video production | 2 days | $200 | $400 | | English + Vietnamese subtitles | 6 hours | $50 | $300 | | Total documentation |


|


| $700 | 2.5 Contingency M2 (12%) | Item | Calculation | Total | | ----------- | ------------- | ------ | | Contingency | 12% × $23,800 | $2,856 | M2 Summary | Category | USD | | ---------------------- | ------- | | Personnel | $18,500 | | Testnet infrastructure | $1,900 | | Field testing | $2,700 | | Documentation & demo | $700 | | Contingency (12%) | $2,856 | | TOTAL M2 | $26,656 | | Budget M2 | $55,000 | | Buffer | $28,344 | Large buffer ($28K): Contingency for smart contract redesign before freeze, or PhoenixKey integration complexity beyond expectations. ### M3 — Audit + Mainnet Launch 180,000 ADA · $45,000 · 7.5% · July #### Breakdown 3.1 Security Audit
ItemQtyUnit PriceTotal
Aiken smart contract audit (independent firm)1$15,000$15,000
Post-fix review (if needed)5 hours$300$1,500
Bug Bounty program setup (Immunefi)1$2,000$2,000
Total audit

$18,500
Note: $15K is the reference price for a medium-complexity Aiken audit. If Intersect template reuse succeeds, only customization is audited → reduced to $5–8K. If Intersect Community Audit Fund covers it → potentially free. Savings go to Bug Bounty. 3.2 Personnel | Item | Unit | Qty | Unit Price | Total | | ----------------------------------- | -------------- | ----------- | ----------- | ------- | | Backend engineer (Mainnet + VeData) | person × month | 2 × 1 | $3,000 | $6,000 | | Midnight integration specialist | person × month | 1 × 1 | $4,500 | $4,500 | | Total personnel M3 |


|


|


| $10,500 | 3.3 Production Infrastructure — Mainnet
ItemQtyUnit PriceTotal
Dedicated Cardano Mainnet node (4 months)1$250/mo × 4$1,000
PostgreSQL HA cluster (3 nodes, 4 months)1$600/mo × 4$2,400
Milvus cluster (initial phase, 4 months)1$800/mo × 4$3,200
API Gateway + CDN (4 months)1$300/mo × 4$1,200
Prometheus + Grafana monitoring4 months$100$400
Total infrastructure

$8,200
3.4 BCT Portal Connection (Circular 11) | Item | Qty | Unit Price | Total | | ------------------------------- | ----------- | ----------- | ------ | | API integration with BCT Portal | 5 days | $250 | $1,250 | | BCT technical consultation | 2 sessions | $500 | $1,000 | | Total BCT |


|


| $2,250 | Note: Hydra Head initialization for Path B Audit Settlement (\~0.58 ADA one-time) and VeData Mosaic CID Subscription API deployment are included in infrastructure setup budget. Daily operational cost of Path B: \~2.70 ADA/day — included in infrastructure line item. 3.5 Contingency M3 (8%) | Item | Calculation | Total | | ----------- | ------------ | ------ | | Contingency | 8% × $39,450 | $3,156 | M3 Summary | Category | USD | | ------------------------- | ------- | | Security audit | $18,500 | | Personnel | $10,500 | | Production infrastructure | $8,200 | | BCT Portal connection | $2,250 | | Contingency (8%) | $3,156 | | TOTAL M3 | $42,606 | | Budget M3 | $45,000 | | Buffer | $2,394 | M4 — Pilot: 7.5 Million Fruits / 500 Ha 280,000 ADA · $70,000 · 11.7% · July–August M4 is the first milestone with significant field costs — onboarding 500 farm households in 1–2 districts. #### Breakdown 4.1 DDC Holdings Personnel | Item | Unit | Qty | Unit Price | Total | | --------------------------------------- | -------------- | ----------- | ----------- | ------- | | Field coordinator | person × month | 1 × 2 | $1,200 | $2,400 | | Additional field staff | person × month | 6 × 2 | $800 | $9,600 | | Technical specialist (app + PhoenixKey) | person × month | 1 × 2 | $1,000 | $2,000 | | Total DDC personnel |


|


|


| $14,000 | 4.2 Field Operations — 1–2 Districts | Item | Unit | Qty | Unit Price | Total | | ----------------------------- | ----------- | ------------------ | ----------- | ------ | | Inter-district travel | month | 2 | $800 | $1,600 | | Remote district accommodation | night | 40 | $25 | $1,000 | | Field meals | meal/day | 8 people × 40 days | $8 | $2,560 | | Total logistics |


|


|


| $5,160 | 4.3 Farmer Onboarding — 500 Households
ItemUnitQtyUnit PriceTotal
Printed instruction materialssheet1,000$0.10$100
OriLife color flyerssheet500$0.50$250
Banners for training venuesset10$30$300
Training workshops (10 sessions)session10$100$1,000
4G SIM cards for farmers without dataSIM100$5$500
Total onboarding


$2,150
4.4 GACC Export Pilot
ItemQtyUnit PriceTotal
Pilot shipment inspection fees1$500$500
Pilot shipment logistics1$1,000$1,000
Customs declaration + phytosanitary1$500$500
GACC expert consultation5 hours$200$1,000
Total GACC

$3,000
4.5 Infrastructure Expansion — 7.5M Fruits
ItemQtyUnit PriceTotal
LampNet Mirage storage (~5TB)5TB × 2 months$150/TB$1,500
NVMe SSD expansion (Milvus)1 TB$200$200
PostgreSQL partition expansion2 days DBA$300$600
Total infrastructure

$2,300
4.6 Contingency M4 (12%) | Item | Calculation | Total | | ----------- | ------------- | ------ | | Contingency | 12% × $26,610 | $3,193 | M4 Summary | Category | USD | | ------------------------ | ------- | | DDC personnel | $14,000 | | Field operations | $5,160 | | Farmer onboarding | $2,150 | | GACC pilot | $3,000 | | Infrastructure expansion | $2,300 | | Contingency (12%) | $3,193 | | TOTAL M4 | $29,803 | | Budget M4 | $70,000 | | Buffer | $40,197 | Large buffer ($40K): M4 is the most critical adoption milestone. Buffer allows team reinforcement, additional workshops, or extra support in difficult districts if onboarding is slower than expected. ### M5 — SDK Open Source + Multi-App Integration 200,000 ADA · $50,000 · 8.3% · August #### Breakdown 5.1 Personnel | Item | Unit | Qty | Unit Price | Total | | ----------------------------- | -------------- | ----------- | ----------- | ------ | | SDK engineer (OriLife SDK v1) | person × month | 1 × 1.5 | $3,000 | $4,500 | | Technical writer | person × month | 1 × 1 | $2,000 | $2,000 | | Total personnel M5 |


|


|


| $6,500 | 5.2 Compliance Adapter SDK
ItemQtyUnit PriceTotal
GS1 EPCIS v2.0 implementation8 days$300$2,400
GACC JSON + testing5 days$300$1,500
GS1 membership fee (standards access)1 year$1,500$1,500
Total compliance

$5,400
5.3 Integration Support — TonFarm & Aladin
ItemQtyUnit PriceTotal
TonFarm integration support10 engineer-days$250$2,500
Aladin integration support10 engineer-days$250$2,500
Integration testing (both apps)5 days$200$1,000
Total integration

$6,000
5.4 Open Source Release
ItemQtyUnit PriceTotal
Code cleanup + refactoring5 days$200$1,000
README + Dev guide (Vietnamese + English)3 days$200$600
API docs (OpenAPI/Swagger)3 days$200$600
License legal review1$500$500
CI/CD for SDK2 days$200$400
Total open source

$3,100
5.5 Contingency M5 (10%) | Item | Calculation | Total | | ----------- | ------------- | ------ | | Contingency | 10% × $21,000 | $2,100 | M5 Summary | Category | USD | | ---------------------------- | ------- | | Personnel | $6,500 | | Compliance Adapter | $5,400 | | TonFarm + Aladin integration | $6,000 | | Open source release | $3,100 | | Contingency (10%) | $2,100 | | TOTAL M5 | $23,100 | | Budget M5 | $50,000 | | Buffer | $26,900 |
### M6 — Beta Rollout: 45 Million Fruits / 3,000 Ha 260,000 ADA · $65,000 · 10.8% · August–September #### Breakdown 6.1 Personnel
ItemUnitQtyUnit PriceTotal
AI/backend engineer (maintenance + scale)person × month2 × 2$3,000$12,000
Additional DDC field staffperson × month6 × 2$800$9,600
Total personnel M6


$21,600
6.2 Infrastructure Expansion — 3,000 Ha
ItemQtyUnit PriceTotal
LampNet Mirage storage (10TB, 2 months)10TB × 2$100/TB$2,000
Milvus Query Node expansion (3 nodes, 2 months)3 × 2$400$2,400
New PostgreSQL partitions (VN-LDG, VN-DNG)3 days DBA$300$900
Kafka KRaft cluster (2 months)2$300$600
CDN bandwidth expansion2 months$500$1,000
Total infrastructure

$6,900
6.3 Operations — 3–5 Districts
ItemQtyUnit PriceTotal
Inter-district travel2 months$1,000$2,000
Accommodation50 nights$25$1,250
Onboarding workshops (15 sessions)15$100$1,500
Additional printed materials3,000 sheets$0.15$450
Total operations

$5,200
6.4 Contingency M6 (10%) | Item | Calculation | Total | | ----------- | ------------- | ------ | | Contingency | 10% × $33,700 | $3,370 | M6 Summary | Category | USD | | -------------------------- | ------- | | Personnel | $21,600 | | Infrastructure expansion | $6,900 | | Operations — 3–5 districts | $5,200 | | Contingency (10%) | $3,370 | | TOTAL M6 | $37,070 | | Budget M6 | $65,000 | | Buffer | $27,930 |
### M7 — Mass Rollout: 180 Million Fruits / 12,000 Ha 280,000 ADA · $70,000 · 11.7% · September–October #### Breakdown 7.1 Full Team Personnel
ItemUnitQtyUnit PriceTotal
Backend engineer (maintenance + DR)person × month2 × 2$3,000$12,000
DDC coordinators (province-wide)person × month2 × 2$1,200$4,800
DDC field staff (15 districts)person × month10 × 2$800$16,000
Total personnel M7


$32,800
7.2 Province-wide Operations — 15 Districts
ItemQtyUnit PriceTotal
Province-wide travel2 months$2,000$4,000
Remote district accommodation100 nights$25$2,500
Onboarding workshops (30 sessions)30$100$3,000
Printed materials (12,000 households)15,000 sheets$0.10$1,500
Total operations

$11,000
7.3 Full-Scale Infrastructure
ItemQtyUnit PriceTotal
LampNet Mirage scale (50TB, 2 months)50TB × 2$50/TB$5,000
Milvus full cluster (5 Query Nodes, 2 months)5 × 2$400$4,000
DR infrastructure (backup site)1$2,000$2,000
Total infrastructure

$11,000
7.4 Contingency M7 (8%) | Item | Calculation | Total | | ----------- | ------------ | ------ | | Contingency | 8% × $54,800 | $4,384 | M7 Summary | Category | USD | | ------------------------- | ------- | | Full team personnel | $32,800 | | Operations — 15 districts | $11,000 | | Full-scale infrastructure | $11,000 | | Contingency (8%) | $4,384 | | TOTAL M7 | $59,184 | | Budget M7 | $70,000 | | Buffer | $10,816 |
### M8 — Global Integration + Sustainability 360,000 ADA · $90,000 · 15.0% · October–November #### Breakdown 8.1 Personnel
ItemUnitQtyUnit PriceTotal
Backend engineer (system maintenance)person × month2 × 2$3,000$12,000
SDK engineer (maintenance + B2B support)person × month1 × 2$3,000$6,000
Business development (B2B outreach)person × month1 × 2$2,500$5,000
Total personnel M8


$23,000
8.2 B2B Integration — 5+ Enterprises
ItemQtyUnit PriceTotal
Enterprise meetings (travel)10 trips$250$2,500
Integration support for enterprises40 hours$100$4,000
B2B contract drafting (5 enterprises)5$500$2,500
Demo + workshop for enterprises5 sessions$300$1,500
Total B2B

$10,500
8.3 Impact Assessment — Third Party
ItemQtyUnit PriceTotal
Independent evaluation firm (contract)1$8,000$8,000
Data collection support5 days$200$1,000
Translation + report design1$2,000$2,000
Total impact

$11,000
8.4 Sustainability & MAGIC Economics
ItemQtyUnit PriceTotal
MAGIC token model audit1$3,000$3,000
3-year financial forecast3 days$300$900
B2B SaaS legal setup1$2,000$2,000
Total sustainability

$5,900
8.5 Community & Communications
ItemQtyUnit PriceTotal
2 public AMAs (organization + recording)2$500$1,000
Final report video (Vietnamese + English)1$1,000$1,000
Press releases (Vietnamese + English)2$500$1,000
2027 Roadmap (design + translation)1$1,500$1,500
Total communications

$4,500
8.6 New Industry Expansion (Planning)
ItemQtyUnit PriceTotal
Dak Lak coffee field survey1 week$2,000$2,000
Melon / aquaculture survey1 week$2,000$2,000
PoC image collection for 2 new industries2$1,500$3,000
Total expansion

$7,000
8.7 Contingency M8 (10%) | Item | Calculation | Total | | ----------- | ------------- | ------ | | Contingency | 10% × $61,900 | $6,190 | M8 Summary | Category | USD | | -------------------------- | ------- | | Personnel | $23,000 | | B2B integration | $10,500 | | Impact assessment | $11,000 | | Sustainability & MAGIC | $5,900 | | Community & communications | $4,500 | | New industry expansion | $7,000 | | Contingency (10%) | $6,190 | | TOTAL M8 | $68,090 | | Budget M8 | $90,000 | | Buffer | $21,910 | 9\. LampNet costs are usage fees, not hardware. LampNet is an independently operated distributed storage network. The Alliance pays usage-based storage fees to LampNet node operators — similar to cloud storage billing. No hardware procurement or maintenance is included in this GA budget. *** ### Final Consolidation #### Budget vs Estimated Actual Spending
MilestoneBudgetEstimated ActualBufferBuffer %
M0 — Foundation$90,000$55,705$34,29538%
M1 — Alpha 750K fruits$65,000$55,438$9,56215%
M2 — Beta App$55,000$26,656$28,34452%
M3 — Audit + Mainnet$45,000$42,606$2,3945%
M4 — Pilot 7.5M fruits$70,000$29,803$40,19757%
M5 — SDK Open$50,000$23,100$26,90054%
M6 — Beta 45M fruits$65,000$37,070$27,93043%
M7 — Mass 180M fruits$70,000$59,184$10,81615%
M8 — Global + Sustainability$90,000$68,090$21,91024%
TOTAL$600,000$397,652$202,34834%
#### Total Buffer Explained ($202,348 — 34%) Buffer rates vary by milestone based on the dominant risk type — not as a blanket reserve. M1 — 25% contingency: AI fine-tuning is the highest-uncertainty activity. Reaching Recall ≥95% on a 10,000-tree multi-variety benchmark may require 1 iteration or 5; field conditions introduce variables that cannot be pre-modeled. M2 — 52% buffer: Serves as the primary ADA price hedge. M2 is the last milestone before Mainnet launch. If ADA has depreciated significantly since M0, the Alliance draws on this buffer rather than requesting additional Treasury funds. The buffer is pre-positioned, not speculative. M4 — 57% buffer: Highland pilot deployment carries unpredictable logistics — road conditions, harvest timing, farmer availability across 1–2 districts. Buffer funds emergency team reinforcement if onboarding stalls. M4 is the milestone with the highest real-world friction; underfunding it risks cascading delays to M6 and M7. M5 — 54% buffer: SDK open-sourcing scope depends on the state of the codebase after M3 audit. If audit surfaces architectural changes, the buffer covers re-engineering without delaying M6. M3 and M7 carry tight buffers (5% and 15%) because their scope is well-defined: M3 is audit + Mainnet deployment with known costs; M7 is logistics and infrastructure scale with field-tested data from M4 and M6. All buffers are locked in Intersect's Escrow. Unused portions follow Surplus policy (Annex D, Scenario 6): Alliance reimbursement first, then contingency, then ecosystem reinvestment — public report within 14 days after M8. ### Cost Efficiency Comparison | Metric | OriLife | Market Reference | | --------------------------- | ------------ | ------------------------------- | | Cost / Bio-ID (180M fruits) | $0.003/fruit | $0.10–5.00 (DNA tagging) | | Cost / user onboarded | $25/person | $200–1,000 (typical fintech) | | Cost / ha digitized | $50/ha | $500–2,000 (traditional AgTech) | | % budget on personnel | 36.7% | 30–50% (industry standard) | | % budget on audit | 3.3% | 3–5% (industry standard) | | % contingency | 10.2% | 10–15% (industry standard) | *** ### Financial Policies #### Exchange Rate Commitment Two rules apply at every disbursement. If ADA < $0.25: Alliance self-funds the gap from its own capital — deployment continues without interruption, no scope reduction, no renegotiation. If ADA > $0.30: surplus first reimburses Alliance self-funded expenditures; remainder becomes contingency or ecosystem reinvestment per Scenario 6. These two rules apply at any price point — no tiered scenarios, no ambiguity. ADA Conversion Policy Immediately after receiving from Escrow each milestone: * Convert 30% to USD immediately (pay bills) * Hold 70% ADA, convert gradually 10%/day over 14 days (minimize price impact; demonstrate long-term commitment) Exchanges: Prefer DEX (Minswap, SundaeSwap). No private OTC deals. All conversions logged and reported in monthly reports. #### The Alliance Has Self-Invested Nearly $500,000 USD Before submitting this GA, the Alliance self-invested in: OriLife PoC development, LampNet MVP, PhoenixKey prototype, TonFarm 2024–2025 (DDC Holdings), institutional relationships across 46 communes, 4 USPTO PPA filings, and digital transformation conferences in Dak Lak. This is a conviction signal: the Alliance didn't wait for Treasury to begin — they invested first, delivered results, and are requesting support to scale, not to start. *** Annex C — Detailed Financial Breakdown Version: 4.1 · April 2026 Reference: GS-ORILIFE-GA-01 Proposer: Nguyen Hung Son— DDC Holdings

# Annex D ## Fund Administration & Escrow Mechanism ### OriLife Platform: Fund Administration and Disbursement Mechanism Document: Annex D — Fund Administration & Escrow Mechanism Version: v5.0 Updated: April 2026 Reference: GS-ORILIFE-GA-01 Proposer: Nguyen Hung Son— DDC Holdings, Dak Lak Status: Public — Attached to Governance Action Total Budget: 2,400,000 ADA Milestones: 9 (M0–M8) ### 1. Governance Mechanism Overview #### Four Foundational Principles TRUSTLESS: Smart Contracts replace trust in any individual. ADA moves only when cryptographic signatures from IOB are present. MILESTONE-GATED: No deliverable = no ADA. Each milestone is independent and can be reported at any time. TRANSPARENT: Every spending decision is public. Monthly reporting is mandatory. RECOVERABLE: Unspent ADA on milestone failure → automatically returned to Treasury. No new vote required. #### Why 9 Parallel Milestones Three teams operate independently: GreenSun R\&D, Aladin Dev, DDC Holdings. When a team completes a milestone, IOB reviews and disburses immediately without waiting for other teams. Whichever team finishes first gets paid first — if one milestone is delayed, others continue unaffected. ### 2. Escrow Structure & ADA Flow #### Overall Architecture CARDANO TREASURY (2,400,000 ADA) ↓ After GA ratified (67% DRep + CC approval)
INTERSECT ESCROW SMART CONTRACT Admin: Intersect MBO Logic: Release ONLY when IOB 2-of-3 sign confirmation Fallback: Auto-sweep to Treasury on timeout ├── M0 tranche: 360,000 ADA \[MOBILIZATION ADVANCE] ├── M1 tranche: 260,000 ADA \[LOCKED] ├── M2 tranche: 220,000 ADA \[LOCKED] ├── M3 tranche: 180,000 ADA \[LOCKED] ├── M4 tranche: 280,000 ADA \[LOCKED] ├── M5 tranche: 200,000 ADA \[LOCKED] ├── M6 tranche: 260,000 ADA \[LOCKED] ├── M7 tranche: 280,000 ADA \[LOCKED] └── M8 tranche: 360,000 ADA \[LOCKED] ↓ Per milestone, after IOB approval Nguyen Hung Son— OPERATIONAL WALLET \[addr1: Published ≥14 days before GA submit]
↓ Allocated per internal Alliance agreement ├── GreenSun Tech (R\&D share) ├── Aladin Contract (Dev share) └── DDC Holdings (Field share) #### M0 — Mobilization Advance (Special) M0 differs from all other milestones: disbursed immediately upon GA ratification after preconditions are verified. GA RATIFIED ON-CHAIN ↓ M0 PRECONDITIONS CHECK: * Escrow contract deployed + verified on Preprod * IOB 3 members confirmed + signing keys on-chain * Wallet addresses published ≥14 days * MOU notarized between 3 companies ↓ IOB 2-of-3 sign precondition confirmation MOBILIZATION ADVANCE: 360,000 ADA → Operational Wallet \ ↓ 30 days later MANDATORY SPENDING REPORT: * Employment contracts (scans) * Equipment invoices (scans) * Legal costs (scans) * ADA converted + exchange rate + DEX used ↓ If Spending Report not submitted FREEZE: All M1–M8 locked until remediated
↓ If M1 not submitted within 90 days CLAWBACK: Smart contract recovers unspent portion to Treasury #### Wallet Addresses — Published Before Submit | Role | Publication | | -------------------------- | ------------------------- | | Escrow Contract | ≥14 days before GA submit | | Nguyen Hung SonOperational | ≥14 days before GA submit | | GreenSun Tech | ≥14 days before GA submit | | Aladin Contract | ≥14 days before GA submit | All addresses will be published on [https://pa.orilife.io/cardano-grant ](https://pa.orilife.io/cardano-grant)and Intersect Forum. ### 3. Independent Oversight Board (IOB) #### Three-Member Structure Member 1 — INTERSECT DELEGATE Officially designated by Intersect MBO. No financial relationship with any Alliance partner. Member 2 — TECHNICAL REVIEWER Independent Cardano/AI expert. Nominated via Intersect Forum, community vote. Verifies on-chain deliverables + AI benchmarks. Member 3 — COMMUNITY DREP Reputable dRep — especially from PRAGMA or dReps with technical/agricultural expertise. Open candidacy on Cardano Forum. Verifies field adoption metrics. #### Mandatory Conditions IOB members MUST: * Have no financial relationship with any Alliance member * Not hold LAMP tokens or tokens related to the MagicLamp ecosystem * Review Completion Reports within ≤7 business days * Disclose identity publicly on Intersect Forum and orilife.io Compensation: IOB operates on a voluntary basis. No compensation from the project. #### IOB Member Replacement If a member cannot continue: * Hours 0–48: Public announcement on Intersect Forum * Days 1–7: Intersect MBO nominates replacement * Days 7–10: Community feedback/objection period * Day 10+: New member confirmed and onboarded Timeout clocks pause during transition. ### 4. Milestone Review Process #### Per-Milestone Process (M1–M8) Step 1 — Prepare Completion Report (≤3 days): On-chain evidence, KPIs (target vs actual), video documentation, financial report, third-party verification where applicable. Step 2 — Submit Report (1 day): Post on Intersect Portal, tag 3 IOB members, email Intersect MBO, update orilife.io/cardano-grant. Step 3 — IOB Review (≤7 business days): * Member 1: Process compliance * Member 2: On-chain deliverables + AI benchmarks * Member 3: Field metrics + adoption Step 4 — IOB Decision: * APPROVED: 2-of-3 sign → Release tranche * CONDITIONAL: Supplementary info requested (7-day grace) * REJECTED: Specific reasons → team remediates (30 days) Step 5 — Escrow Release (1–2 days after approval) Total time: ≤14 days from Report submission to ADA received. #### Dispute Resolution * Days 1–3: Team submits Counter-Argument * Days 4–6: IOB responds with detailed rationale * If still disagreed → Escalate to Intersect MBO * Days 7–14: Intersect MBO independent review — decision is FINAL *** ### ### 5. Disbursement Schedule #### Projected Timeline MAY 2026 Week 1: GA ratification → 2,400,000 ADA into Escrow Week 1: M0 preconditions verified → IOB signs → 360,000 ADA MOBILIZATION ADVANCE Week 1–2: M0 Foundation setup M1 begins (GreenSun — AI fine-tuning) M2 begins (Aladin — App build) \[PARALLEL]
JUNE 2026 Week 1: M0 Spending Report (30 days after disbursement) Week 2: M1 Completion Report → IOB Review Week 3: M1 APPROVED → 260,000 ADA released
JULY 2026 Week 1: M2 Completion Report → IOB Review Week 2: M2 APPROVED → 220,000 ADA released M3 begins (Audit + Mainnet) M4 begins (DDC field ops) \[PARALLEL] Week 4: M3 Completion Report → IOB Review Week 5: M3 APPROVED → 180,000 ADA released
AUGUST 2026 🌳 DURIAN HARVEST SEASON — Đắk Lắk M4 Pilot operates during harvest season Week 2: M4 APPROVED → 280,000 ADA released M5 begins (SDK Open)
AUGUST–SEPTEMBER 2026 M5 + M6 \[PARALLEL] M5 APPROVED → 200,000 ADA released M6 execution (3,000 ha scale)
SEPTEMBER 2026 M6 APPROVED → 260,000 ADA released M7 begins (12,000 ha full rollout)
OCTOBER 2026 M7 APPROVED → 280,000 ADA released
OCTOBER–NOVEMBER 2026 M8 execution → M8 APPROVED → 360,000 ADA released ✅ PROJECT COMPLETE
DECEMBER 2026 ⚖️ CIRCULAR 11 DEADLINE (01/12/2026) OriLife operational 2+ months before deadline #### Timeout Thresholds
MilestoneTimeout Sweep
M014 days after ratification
M197 days after M0 disbursement
M2August 8, 2026
M3August 22, 2026
M4September 8, 2026
M5September 22, 2026
M6October 8, 2026
M7November 8, 2026
M8December 8, 2026
Dates converted to Cardano slot numbers at deployment. *** ### ### 6. Pass/Fail Matrix — Per Milestone
MilestoneKey PASS Requirements
M0Escrow deployed + verified; IOB 3 members on-chain; wallets published ≥14 days
M1Precision ≥99%; Recall ≥95% at ±45°; Latency <1s on Android 4GB; Temporal consistency after 30 days; Throughput ≥100 units/hour; API <500ms p95
M2IOB self-installs <10 min; Uncut demo video; Offline sync verified; Contract freeze hash public
M3Zero unresolved Critical/High; ≥1 Farm NFT on Mainnet; Source code public; VeData batch demo
M4≥50,000 trees on-chain; ≥1,000 active DIDs; ≥1 GACC shipment cleared; Anti-fraud 100% detection
M5GitHub public MIT; Third party integrates <1 hour; GS1 v2.0 valid; Multi-app demo complete
M6≥300,000 trees on-chain; ≥3,000 active DIDs; Uptime ≥99.0%; Zero security incidents
M7≥1,200,000 trees on-chain; ≥24,000 active DIDs; DR recovery <15 min; ≥100,000 tx during M7
M8≥5 active B2B contracts; MAGIC ≥1,000 tx/30 days; Impact report ≥30 pages; 2 AMA recordings
*** ### 7. Transparency & Reporting #### Monthly Progress Report — 1st of Each Month Mandatory content: * ON-CHAIN METRICS — Bio-ID count, DID count, transactions, Farm NFT status * FIELD METRICS — Districts covered, workshops held, active farmers * FINANCIAL REPORT — ADA received, USD spent, ADA conversion log * TECHNICAL UPDATES — AI performance, VeData efficiency, uptime * RISKS & BLOCKERS — New risks + mitigation plans #### Reporting Channels | Channel | Frequency | | ---------------------------------- | ------------- | | | Monthly | | Intersect Portal | Monthly | | Cardano Forum | Monthly | | GitHub Release Notes | Per milestone | #### Community AMA Sessions | AMA | Timing | Content | | ------ | ------------------- | -------------------------------- | | AMA #1 | After M4 (August) | Pilot results + Mainnet demo | | AMA #2 | After M8 (November) | Final results + impact + roadmap | *** ### 8. Refund & Surplus Policy #### Scenario 1 — Automatic Timeout Trigger: Completion Report not submitted before deadline. Action: Smart contract automatically sweeps milestone tranche back to Treasury. No vote, no manual action required. #### Scenario 2 — M0 Clawback Trigger: M0 disbursed, but M1 Completion Report not submitted within 90 days. Action: Smart contract recovers all unspent portion of M0 to the Treasury automatically. #### Scenario 3 — M0 Spending Report Failure Trigger: Spending Report not submitted 30 days after M0 disbursement. Action: IOB freezes all M1–M8 until the Spending Report is submitted and approved. #### Scenario 4 — IOB Rejects Milestone Trigger: IOB 2-of-3 vote REJECT. Action: Team has 30 days to remediate. After 30 days if still failing → ADA sweeps to Treasury. #### Scenario 5 — Project Terminates Trigger: Nguyen Hung Son declares inability to continue, or no activity for 45 days. Action: All remaining ADA in Escrow returns to Treasury within 14 days. #### Scenario 6 — Completion with Surplus ADA Trigger: M8 approved, ADA remaining in Escrow or operational wallet. Action in priority order: 1. Reimburse Alliance for self-funded expenditures incurred when ADA was below $0.25 2. Contingency for any outstanding remediation needs 3. Reinvest to expand to coffee, melon, shrimp, and fish 4. Public report within 14 days after M8 #### Why Clawback Doesn't Need a New GA Traditional approach: Discover failure → create clawback GA → vote 1–2 months → proposer may transfer ADA before GA passes. OriLife approach: Smart contract processes automatically on timeout → no vote needed → no window to transfer funds → Treasury receives ADA in 1 transaction. *** ### 9. Financial Risk Management #### ADA Price — Two Simple Rules Rule 1 — ADA below $0.25 at disbursement: Alliance self-funds the gap from its own capital. Deployment continues without interruption. No scope reduction, no VoluntaryRefund, no new negotiation required. The Alliance has already self-invested nearly $500,000 USD before this proposal — this is a demonstrated commitment, not a theoretical one. Rule 2 — ADA above $0.30 at disbursement: Surplus ADA received (relative to the $0.25 baseline) is used first to reimburse Alliance expenditures from any prior self-funded period. Any remainder becomes contingency or ecosystem reinvestment per the Surplus policy above. These two rules replace all price-tiered scenarios. Simplicity is accountability — no ambiguity about what happens at any price point. #### ADA Conversion Policy Immediately after receiving each milestone disbursement: * Convert 30% to USD immediately (pay bills) * Hold 70% ADA, convert gradually 10%/day over 14 days (minimize price impact) Exchanges: Prefer DEX (Minswap, SundaeSwap). No private OTC deals. All conversions logged in monthly reports. *** ### 10. Conflict of Interest Declaration
PartyConflict?Note
Nguyễn Hùng SơnNoNo financial relationship with any DRep/SPO/CC
GreenSun TechNoNo financial relationship with any DRep/SPO/CC
Aladin ContractNoNo financial relationship with any DRep/SPO/CC
DDC HoldingsNoNo financial relationship with any DRep/SPO/CC
Duc TigerYES — DISCLOSEDdRep + SPO (pool TIGER). PM. Receives reasonable compensation from GA budget. Votes ABSTAIN on this GA and all Withdraw Treasury GAs during the voting period.
No LAMP, MAGIC, ADA, or any token is allocated to DReps, SPOs, or CC Members in any form related to voting on this GA. *** ### 11. Emergency Procedures #### Security Incident * Hours 0–2: Activate Incident Response. Pause writes. Notify IOB + Intersect MBO. * Hours 2–24: Assess scope. Public disclosure. * Hours 24–72: Remediation. Security patch. Independent verification. * After 3 days: Post-mortem report (public). #### Force Majeure Recognized events: Natural disaster in Đắk Lắk, contradictory government regulation, Cardano network outage >7 days, epidemic affecting the region. 1. Notify IOB within 48 hours with evidence 2. IOB + Intersect MBO confirm within 7 days 3. If confirmed: Timeout clock PAUSES for up to 60 days 4. After 60 days: Resume or terminate + return ADA *** ### 12. Signatures & Commitments I, Nguyễn Hùng Sơn, Director of DDC Holdings' Đắk Lắk Office, commit to: * ✅ Not spending ADA before receiving from Escrow * ✅ Submitting Spending Report 30 days after M0 disbursement * ✅ Spending strictly within each milestone's scope * ✅ Accurate and timely monthly financial reporting * ✅ Publishing wallet addresses ≥14 days before GA submit * ✅ Public disclosure of all material events within 48 hours * ✅ Organizing 2 public AMAs (after M4 and after M8) * ✅ Accepting auto-sweep mechanism on timeout * ✅ Accepting 90-day Clawback for M0 * ✅ If ADA < $0.25 at disbursement: Alliance self-funds the gap. Deployment continues. * ✅ If ADA > $0.30 at disbursement: Surplus reimburses Alliance self-funded expenditures first; remainder per Scenario 6. * ✅ Reinvesting ecosystem surplus per binding commitment * ✅ Cooperating with IOB and Intersect MBO in all circumstances #### Pre-Submit Checklist ESCROW & WALLETS: * Escrow smart contract deployed and verified on Preprod * All wallet addresses published ≥14 days * 3 IOB members confirmed with public identities * IOB signing keys registered in escrow contract DOCUMENTS (LampNet): * GA main document — final version * Annex A (Technical) — CID * Annex B (Legal & Compliance) — CID * Annex C (Financial) — CID * Annex D (Fund Admin) — this file — CID * Annex E (Community Q\&A) — CID * All legal documents (Circular 11, QĐ 1236, QĐ 5272, Letter 351, MOU, Copyright Certificate, USPTO Receipts) — CIDs ON-CHAIN METADATA: * Compliant with CIP-100 metadata format * LampNet links to all annexes * Wallet addresses accurate COMMUNITY: * Draft posted on Intersect Forum ≥2 weeks for feedback * At least 1 community call presented * Community questions addressed * No unresolved serious objections *** Proposer: Nguyen Hung Son— DDC Holdings, Đắk Lắk Technology Alliance: * DDC Holdings — Nguyen Hung Son(Director, Đắk Lắk) * GreenSun Tech — Nguyen Thi Kim Ngan (CEO) * Aladin Contract — Nguyen Thi Thuy (Deputy Director) Cardano Rep: Duc Tiger (dRep · SPO TIGER) · Receives reasonable compensation · ABSTAIN on this GA and all Withdraw Treasury GAs during voting period *** Annex D v5.0 · April 2026 · GS-ORILIFE-GA-01
# QnA Questions and Answers Document: GS-ORILIFE-GA-01 · Annex E · Version: v1.0 · Update: April 18th, 2026 Purpose: Official responses to community questions received during public review period. Status: Living document — updated as new questions are received. # 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. # Economic Clarifying the boundary between Treasury funding and user-borne costs. **Q: Who pays the on-chain transaction fees — the Alliance, the Treasury, or the farmers?** Users pay — not the Alliance, not the Treasury. Farmers and enterprises pay in local fiat currency (VND) through standard payment gateways (banks, e-wallets). MAGIC credits are automatically converted to ADA for network settlement. The GA budget covers only: building the infrastructure, deploying it across 12,000 ha, and open-sourcing the SDK. *** **Q: What is MAGIC and how does it work for farmers?** MAGIC is an internal service credit used within OriLife and other applications in the MagicLamp ecosystem. Within OriLife specifically, MAGIC functions as compute energy — it is not a tradeable token, has no trading market, and carries no price appreciation story. It is designed explicitly to prevent speculation and focus exclusively on real usage. For Vietnamese farmers, the experience is simple: pay in VND through a familiar payment gateway → MAGIC is credited automatically → MAGIC converts to ADA for on-chain transactions and covers LampNet storage and AI processing in the platform. Farmers never buy cryptocurrency, never manage wallets, and never see seed phrases beyond their PhoenixKey biometric setup. They pay for a traceability service the same way they pay for any other digital service. Note: Questions about MagicLamp ecosystem-wide tokenomics and LAMP token are outside the scope of this GA. This proposal covers OriLife deployment only. MagicLamp ecosystem documentation is available separately. *** **Q: Is \~$10/farm/year in Cardano network fees realistic for Đắk Lắk durian farmers?** Yes — and the context matters. Total farming operational cost for 1 ha durian: \~$5,000–8,500 USD/year (Source: CropTex; QĐ 3763/QĐ-UBND Đắk Lắk 19/12/2019). The \~$10 Cardano network fee = 0.1–0.2% of total farming costs. Total OriLife cost including VeData processing, LampNet storage, and AI = \~$200/ha/year = 2–4% of total farming costs — cheaper than QR labels (\~$300/ha/year) and far cheaper than RFID ($1,500–8,700/ha/year). OriLife is the cheapest traceability option on the market and the only one that cannot be forged. *** **Q: What if the MAGIC economic model fails to operationalize?** Data on LampNet and Cardano remains fully functional and independently accessible regardless of MAGIC's status. Users recover their identity via MIT-licensed PhoenixKey recovery tools on any device. ADA can be purchased directly from any exchange to cover on-chain fees. The open-source SDK ensures no vendor lock-in — any developer or operator can continue running OriLife infrastructure without Alliance involvement. MAGIC is a payment convenience layer, not a foundational dependency. *** **Q: Are VeData, Hydra, and LampNet operational costs covered by this GA?** No. These are user-borne costs paid via MAGIC credits, entirely separate from the 2,400,000 ADA GA budget. The GA funds only: infrastructure development, 12,000 ha deployment, and SDK open-sourcing.
# Transactions Verifying the numbers behind projections. Q: Who pays the on-chain transaction fees — the Alliance, the Treasury, or the farmers? Users pay — not the Alliance, not the Treasury. Farmers and enterprises pay in local fiat currency (VND) through standard payment gateways (banks, e-wallets). MAGIC credits are automatically converted to ADA for network settlement. The GA budget covers only: building the infrastructure, deploying it across 12,000 ha, and open-sourcing the SDK. *** Q: What is MAGIC and how does it work for farmers? MAGIC is an internal service credit used within OriLife and other applications in the MagicLamp ecosystem. Within OriLife specifically, MAGIC functions as compute energy — it is not a tradeable token, has no trading market, and carries no price appreciation story. It is designed explicitly to prevent speculation and focus exclusively on real usage. For farmers, the experience is simple: pay in VND through a familiar payment gateway → MAGIC is credited automatically → MAGIC converts to ADA for on-chain transactions and covers LampNet storage and AI processing in the background. Farmers never buy cryptocurrency, never manage wallets, and never see seed phrases beyond their PhoenixKey biometric setup. They pay for a traceability service the same way they pay for any other digital service. Note: Questions about MagicLamp ecosystem-wide tokenomics and LAMP token are outside the scope of this GA. This proposal covers OriLife deployment only. MagicLamp ecosystem documentation is available separately. *** Q: Is \~$10/farm/year in Cardano network fees realistic for Đắk Lắk durian farmers? Yes — and the context matters. Total farming operational cost for 1 ha durian: \~$5,000–8,500 USD/year (Source: CropTex; QĐ 3763/QĐ-UBND Đắk Lắk 19/12/2019). The \~$10 Cardano network fee = 0.1–0.2% of total farming costs. Total OriLife cost including VeData processing, LampNet storage, and AI = \~$200/ha/year = 2–4% of total farming costs — cheaper than QR labels (\~$300/ha/year) and far cheaper than RFID ($1,500–8,700/ha/year). OriLife is the cheapest traceability option on the market and the only one that cannot be forged. *** Q: What if the MAGIC economic model fails to operationalize? Data on LampNet and Cardano remains fully functional and independently accessible regardless of MAGIC's status. Users recover their identity via MIT-licensed PhoenixKey recovery tools on any device. ADA can be purchased directly from any exchange to cover on-chain fees. The open-source SDK ensures no vendor lock-in — any developer or operator can continue running OriLife infrastructure without Alliance involvement. MAGIC is a payment convenience layer, not a foundational dependency. *** Q: Are VeData, Hydra, and LampNet operational costs covered by this GA? No. These are user-borne costs paid via MAGIC credits, entirely separate from the 2,400,000 ADA GA budget. The GA funds only: infrastructure development, 12,000 ha deployment, and SDK open-sourcing.
# Accountability How the escrow works and what happens if things go wrong Q: What specifically are the \~100 on-chain events per hectare per year? The 100 events/ha/year is a planning estimate reflecting expected average farming activity: * \~50 VeData batch anchors — cultivation logs, Bio-ID updates, harvest events (\~weekly during growing season) * \~25 labor contract engagements — 2 permanent workers × 12 monthly payments + 1–2 harvest khoán contracts per year (Source: CropTex; QĐ 3763/QĐ-UBND Đắk Lắk 19/12/2019) * \~5 commercial escrow transactions — advance deposit + final settlement per harvest batch * \~8 one-time setup events — DID registration, Farm NFT minting, harvest module activation Path B audit decommits (\~2,190/year) are a fixed system cost that does not scale per hectare and is excluded from this formula. Active farms during peak harvest months will generate more; smaller or less active farms will generate fewer. The \~1,200,000 total is the upper bound planning estimate. *** Q: Is "25 labor contracts/ha/year" based on actual Đắk Lắk employment data? Yes, derived from official field data. From QĐ 3763/QĐ-UBND Đắk Lắk (19/12/2019) and CropTex field research: 1 ha durian requires 2 permanent workers year-round at 5–7M VND/person/month. 2 workers × 12 monthly payments = 24 labor payment engagements/year, plus 1–2 harvest khoán contracts per harvest season. Total: \~25–26 individual labor engagements/year. The GA uses 25 as a conservative lower bound. *** Q: Is "5 commercial escrow tx/ha/year" consistent with actual durian trade structure? Yes. Đắk Lắk durian trade typically involves: 1–2 advance deposits from traders before harvest + 1–2 final settlements after delivery + occasional partial payments in multi-batch sales. \~3–5 commercial transactions/ha/year is the realistic estimate. The GA uses \~5 as the planning upper bound. (Source: DDC Holdings field experience across 46 communes; confirmed by trade structure analysis from the 2025 scandal investigation) *** Q: Under a realistic downward scenario (\~700,000 events/year), are milestones still achievable? Yes. M7 requires ≥100,000 on-chain transactions during the M7 period (1–2 months). At 700,000 events/year, 2 months = \~117,000 transactions — M7 passes comfortably. The 700,000 scenario is likely the Year 1 reality as the ecosystem builds up, not a failure scenario. It becomes the baseline from which organic growth occurs as more enterprises integrate the SDK. *** Q: How does the design prevent gaming M7's "≥100,000 on-chain tx" acceptance criterion? Four independent layers: (1) Each transaction costs real MAGIC credits paid by users — generating empty transactions is economically self-defeating. (2) 5-layer VeData validation rejects invalid data before it reaches Cardano; fake records cannot pass biological plausibility checks. (3) IOB Member 3 independently verifies field evidence — GPS photos, district reports, and dashboard data must corroborate on-chain activity. (4) Random 5% spot checks require field inspectors to confirm that on-chain records correspond to physical farms and trees.
# Sustainability What happens when Treasury funding ends. Q: What prevents the Alliance from spending the Mobilization Advance (M0) and disappearing? Three overlapping mechanisms: (1) 90-day Clawback — if M1 is not submitted within 90 days of M0 disbursement, the smart contract automatically recovers all unspent M0 funds to Treasury without any vote or manual action. (2) Mandatory 30-day Spending Report — failure to submit freezes all M1–M8 disbursements until remediated. (3) IOB oversight — 3 independent reviewers with on-chain signing authority; no funds move without 2-of-3 IOB signatures. *** Q: Who are the IOB members and how are they selected? Three independent members with distinct roles: Member 1 — Intersect MBO Delegate: Officially designated by Intersect MBO. No financial relationship with any Alliance partner. Member 2 — Technical Reviewer: Independent Cardano/AI expert. Nominated via Intersect Forum with community vote. Verifies on-chain deliverables and AI benchmarks. Member 3 — Community dRep: Open candidacy on Cardano Forum — preference for PRAGMA or dReps with technical or agricultural expertise. Independently verifies field adoption metrics. All IOB members must publicly disclose identity on Intersect Forum and orilife.io, hold no financial relationship with any Alliance member, and hold no MagicLamp ecosystem tokens. *** Q: What if an IOB member disengages mid-project? Public candidacy process at M0 identifies backup candidates in advance. If a member cannot continue: public announcement within 48 hours, Intersect MBO nominates replacement within 7 days, community feedback period days 7–10, new member confirmed day 10+. Timeout clocks pause during transition. IOB scope is milestone-gated — 7-day review windows per milestone — not continuous commitment, making the role sustainable for volunteers. *** Q: Why are there 9 milestones in only 7 months? Three teams operate independently and in parallel — GreenSun R\&D, Aladin Dev, and DDC Holdings do not wait for each other. When one team completes a milestone, IOB reviews and disburses immediately. M1 (AI fine-tuning) and M2 (App build) run simultaneously from May. M3 (Audit) and M4 (Pilot) run simultaneously from July. M5 (SDK) and M6 (Scale) run simultaneously from August. The timeline is aggressive but the parallel structure is what makes it achievable — and each milestone has an independent timeout that auto-sweeps to Treasury if missed. Full escrow and milestone independence mechanics: Annex D, [Section 1](https://docs.google.com/document/d/1ujuGhROOyxVyyumxr1IhfIvtMTKBx0F14sBs7Ju7eoo/edit?tab=t.e4nu2tm79mv8#heading=h.nf6n4g7o7kv2) *** Q: What happens if ADA price drops significantly during the project? Two simple rules cover every scenario: If ADA < $0.25 at disbursement — Alliance self-funds the gap from its own capital. Deployment continues without interruption, no scope reduction, no renegotiation required. If ADA > $0.30 at disbursement — surplus first reimburses Alliance self-funded expenditures; remainder becomes contingency or ecosystem reinvestment. The Alliance has already self-invested \~$500,000 USD before this GA — the price commitment is demonstrated, not theoretical. *** Q: What does the buffer in each milestone budget cover? Buffer rates vary by the dominant risk type in that milestone, not as a blanket reserve: * M1 — 25% contingency: AI fine-tuning is the highest-uncertainty activity. Reaching Recall ≥95% on a 10,000-tree multi-variety benchmark may require 1 iteration or 5 — field conditions introduce variables that cannot be pre-modeled. * M2 — 52% buffer: Primary ADA price hedge. M2 is the last milestone before Mainnet launch. If ADA has depreciated significantly since M0, the Alliance draws on this buffer rather than requesting additional Treasury funds. * M4 — 57% buffer: Highland pilot deployment carries unpredictable logistics — road conditions, harvest timing, farmer availability across 1–2 districts. Buffer funds emergency team reinforcement if onboarding stalls. * M5 — 54% buffer: SDK open-sourcing scope depends on the state of the codebase after M3 audit. If audit surfaces architectural changes, the buffer covers re-engineering without delaying M6. * M3 and M7 carry tight buffers (5% and 15%) because their scope is well-defined: M3 is audit + Mainnet deployment with known costs; M7 is logistics and infrastructure scale with field-tested cost data from M4 and M6. All buffers are locked in Intersect's Escrow and follow the Surplus policy in Annex D Scenario 6 if unused.
# Alternatives Comparing OriLife against failed predecessors and alternative uses of Treasury funds. **Q: How does OriLife differ structurally from** [**IBM Food Trust, VeChain, TE-FOOD**](https://docs.google.com/document/d/1WUKezM73atod4ipa3XwIENad9ItPvrxoyOq7ztqw7o8/edit?tab=t.0)**,** [**SEA2SEE**](https://docs.google.com/document/d/1BBnH3BqHfI3m4sZSHBbXb5Gmmdn_0RHlchHgahMAc34/edit?tab=t.0) **— from an economic perspective, not technical?** Two structural differences predecessors lacked: First, non-discretionary cost. At \~$200/ha/year, OriLife traceability is 2–4% of total farming operational costs. Non-adoption under Circular 11 means product recall and export loss — farmers aren't choosing OriLife over a competitor, they're choosing it over losing their harvest. That is inelastic demand. Predecessors competed for a premium traceability budget that enterprises could choose not to spend. Second, usage-based revenue without speculation. IBM Food Trust and TE-FOOD required enterprises to be convinced to join — when conviction faded, activity stopped. OriLife's activity is generated by actual farming events: harvests happen, workers get paid, shipments leave. These events occur regardless of whether any party is "motivated" by a platform. Within OriLife, MAGIC functions as compute energy — farmers pay fiat, MAGIC converts automatically to cover on-chain fees and storage. No trading market, no price appreciation thesis, no speculative incentive to hold. *** **Q: How do OriLife's KPIs differ from "1M wallets / 1M tx" metrics claimed by failed predecessors?** The structural difference is what generates the metric, not the metric itself. Failed predecessors reported DIDs and transactions generated by onboarding incentives, grant-funded pilots, or enterprise mandates that expired with the pilot. When the incentive stopped, the metric stopped. OriLife's 24,000 DIDs are generated by farmers registering to comply with a legal obligation. Each DID = a household that must connect to the national traceability system or face product recall. It is a compliance action, not a sign-up. OriLife's 1,200,000 events/year are generated by farming activity that happens regardless of platform: crops grow, workers get paid, shipments leave. The test: remove all Alliance involvement post-M8. Do the events still happen? Yes. Do they still get recorded on Cardano? Yes — because Circular 11 requires it and the open-source SDK is accessible to any operator. *** **Q: "Government partnership and regulatory compliance" were cited by all failed predecessors. Why is OriLife's version structurally more effective?** Predecessors used government partnership as an adoption signal — doors opened, pilots approved, credibility established. When the partnership ended or government priority shifted, adoption stalled. A signal is not a mechanism. Circular 11 is a mechanism. It creates direct legal liability — product recall, administrative fines, criminal prosecution per Article 15 — for non-compliance by December 1, 2026. This converts voluntary demand (elastic, can disappear) into inelastic demand (the cost of not adopting exceeds the cost of adopting). The sustainability depends not on any political relationship continuing, but on the cost gap between compliance and non-compliance — which is structural, not contingent on who is in government. *** **Q: Copyright certificates and USPTO PPAs also existed in failed projects. Why didn't they predict success there, and why should OriLife be different?** They shouldn't predict success — and OriLife doesn't claim they do. Legal protection confirms IP ownership, not market viability. The Alliance holds 4 USPTO PPAs because it built original technology worth protecting, not as evidence of commercial success. The sustainability case rests entirely on inelastic demand from Circular 11. Durian farmers in Đắk Lắk don't choose OriLife because it's better — they use it because the alternative is product recall and export loss. That demand structure is independent of IP paperwork, MOUs, or government branding. *** **Q: Why higher expected value than deploying 2,400,000 ADA into existing Cardano DeFi or developer tooling?** DeFi and developer tooling generate value for existing Cardano users — deeper liquidity, better tools, higher retention. These are real returns, but they circulate within the existing user base. The marginal Treasury fee contribution from an additional DeFi protocol is a function of existing ADA holders transacting more. OriLife brings 24,000 new users who have never touched Cardano, generating \~28,800 ADA/year in Treasury fees from economic activity that would otherwise occur entirely off-chain. These users transact because of legal compliance requirements — not ADA price speculation. The fee-contribution "payback period" is \~83 years at $0.25/ADA — but that framing is wrong. OriLife is infrastructure, not a bond. The 75,000 ADA permanently locked at M4 is immediate verifiable value. SDK expansion to coffee (731,900 ha) and other crops multiplies Treasury contribution without additional Treasury investment. No DeFi protocol offers a comparable path to scaling fee contributions through real-world agricultural adoption. *** **Q: Is Treasury funding "essential" or merely an "accelerant"?** It is the difference between proof-of-concept scale and policy-relevant scale. Without the GA, the Alliance continues self-funding — deploying across approximately 1,500–2,000 hectares. That proves the technology works. It does not meet the 12,000 ha mandate under Circular 11, and it does not satisfy GACC's requirement for consistent traceability coverage across a registered production area. A fragmented deployment — some farms on-chain, others on paper — creates the same audit gap that caused the 2025 scandal. At 2,000 hectares, OriLife is a promising pilot. At 12,000 hectares, it is the infrastructure layer for Vietnam's largest durian export zone, with 24,000 DIDs and \~1,200,000 on-chain events per year — legible to governments, enterprises, and the global blockchain ecosystem. The Treasury is not funding the Alliance's survival. It is funding the scale that makes the difference between a footnote and a first.
# Risks What happens when specific things go wrong. **Q: What if ADA price drops sharply during the project?** Two simple rules cover every scenario. If ADA < $0.25 at disbursement: Alliance self-funds the gap from its own capital — deployment continues without interruption, no scope reduction, no renegotiation required. If ADA > $0.30 at disbursement: surplus first reimburses Alliance self-funded expenditures; remainder becomes contingency or ecosystem reinvestment. The Alliance has already self-invested \~$500,000 USD before this proposal — this is a demonstrated commitment, not a theoretical one. *** **Q: What if key team members leave during the project?** DDC Holdings operates across 46 communes with institutionalized relationships that predate any individual. GreenSun Tech holds 4 USPTO PPAs on core IP — technology assets are legally protected and transferable. Aladin Contract has an engineering team with AI-assisted workflows. The IOB has authority to freeze disbursements if team continuity is compromised, and the auto-sweep mechanism returns ADA to Treasury in any extended inactivity scenario. *** **Q: What if Vietnam's government changes traceability requirements mid-project?** The December 1, 2026 deadline is law — not a policy recommendation. OriLife's open-source Compliance SDK can be updated to match new reporting format requirements without changing the core blockchain infrastructure. On-chain data — Farm NFTs, Bio-IDs, LampNet records — remains valid regardless of how reporting standards evolve. Regulatory format changes are addressed at the Compliance Adapter layer; the underlying architecture is unaffected. *** **Q: What if GACC does not accept Midnight View Key format?** Midnight is an optional privacy layer, not a GACC compliance prerequisite. OriLife exports full GACC-required data fields (origin, harvest date, plantation code, phytosanitary) independently of Midnight. The M4 pilot shipment validates GACC acceptance before full rollout — any required format adjustments are addressed at M4, not M7. The Compliance Adapter SDK handles format changes without modifying core infrastructure. *** **Q: What if the August harvest season is missed during rollout?** M4 Pilot is specifically scheduled to operate during the August 2026 durian harvest season in Đắk Lắk — this is the primary validation window for the harvest module. M6 and M7 scale after the peak season. Missing the August window would delay harvest module validation but not block infrastructure milestones. IOB would assess impact and adjust milestone timing within the existing escrow timeout structure. *** **Q: What if farmers don't adopt the system?** Adoption risk is low for two reasons. First, Circular 11 creates direct legal pressure — non-connected farms risk product recall from December 1, 2026. Second, DDC Holdings has already presented OriLife to 46 communes covering 50,000+ people over two harvest seasons; the UX has been validated with farmers aged 50+ who had no prior smartphone experience. PhoenixKey registration takes \~3 minutes via fingerprint and face scan — no technical knowledge required. The Extension Center's institutional mandate further ensures engagement at the commune leadership level before individual farmer outreach. *** **Q: What if there is a smart contract bug post-Mainnet?** The audit strategy is specifically designed to minimize this risk: reuse Intersect's battle-tested Escrow template (audit only customization), independent security audit before any Mainnet deployment, Bug Bounty program live from M3+, and smart contract frozen at M2 for the full audit period before M3 deployment. Zero unresolved Critical or High severity findings is a hard M3 acceptance criterion — no deployment proceeds until the audit is clean.
# Support Links
DocumentStorage
Annex A — Technical Architecture & Verified Resultshttps://black-worrying-porcupine-242.mypinata.cloud/ipfs/bafybeihwrrqeogkdxirlpacxgh56qa3wesb3kqm7mousuboj3m7q6c6zbu
Annex B — Legal & International Compliancehttps://black-worrying-porcupine-242.mypinata.cloud/ipfs/bafybeigdz6pztrrmzr2v32djrbopsvyjbzubmyrblsyn7dyq5y2sslm2fe
Annex C — Detailed Budget Breakdownhttps://black-worrying-porcupine-242.mypinata.cloud/ipfs/bafybeifn7zpe22kjpqlaczj7tueba7tsmpedudawutlhepr5qwt2pjewiy
Annex D — Escrow & Fund Administrationhttps://black-worrying-porcupine-242.mypinata.cloud/ipfs/bafybeiepwir4a3augtoykvn3z2ly2tkzdmunseww7sz2mgoyjmzez5rlou
Annex E — Community Q&Ahttps://ga.orilife.io/QnA
Forum posthttps://forum.cardano.org/t/request-your-advice-for-ga-orilife-traceability-platform-without-labels/154207
OriLife Whitepaper v5.2https://orilife.io/whitepaper
PhoenixKey Whitepaper v3.0https://phoenixkey.me/whitepaper
VeData Mosaic v1.2https://vedata.io/docs/mosaic
TonFarm legacy on TON blockchainhttps://tonviewer.com/UQAftkW5i-ON2qIPIRub2Z8zZL_KzbvX8jPnF9-6uwnowmcD?section=nfts
Copyright Certificate 4420/2025/QTGhttps://orilife.io/docs/certificate4420
Circular 11/2026/TT-BCThttps://chinhphu.vn/?pageid=27160&docid=217126&classid=0
Decision 1236/QĐ-TTghttps://vanban.chinhphu.vn/?pageid=27160&docid=211462
Decision 5272/QĐ-BNNMT (Durian Pilot)https://mae.gov.vn/Pages/chitietvanbandh.aspx?ItemID=3451
Resolution 57-NQ/TWhttps://tulieuvankien.dangcongsan.vn/he-thong-van-ban/van-ban-cua-dang/nghi-quyet-so-57-nqtw-ngay-22122024-cua-bo-chinh-tri-ve-dot-pha-phat-trien-khoa-hoc-cong-nghe-doi-moi-sang-tao-va-chuyen-11162
Letter 351-CV/HNDThttps://orilife.io/docs/letter135cvhdnt
MOU with Đắk Lắk Extension Centerhttps://tonfarm.co/activity/055fbd2c-cb7e-496d-bcea-51790c3c9d3c
46-Commune Conference Reporthttps://youtu.be/viI7IjKMI2M?si=sdrOr0nHpudf4hzl
USPTO PPA PhoenixKeyhttps://greensun.tech/ppa/phoenixkey
USPTO PPA OriLifehttps://greensun.tech/ppa/orilife
USPTO PPA LampNethttps://greensun.tech/ppa/lampnet
USPTO PPA VeDatahttps://greensun.tech/ppa/vedata
GS1 EPCIS Standard v2.0https://ref.gs1.org/standards/epcis/
GACC Registration Requirementshttp://english.customs.gov.cn/
EU Regulation 2023/1115 (EUDR)https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32023R1115
FDA FSMA Section 204https://www.fda.gov/food/food-safety-modernization-act-fsma/food-traceability-list
ISO 22005:2007https://www.iso.org/standard/36297.html
Cybersecurity Law 2018https://vanban.chinhphu.vn/?pageid=27160&docid=206114
Cybersecurity Law 2025https://vanban.chinhphu.vn/?pageid=27160&docid=216499
Decree 13/2023/NĐ-CPhttps://vanban.chinhphu.vn/?pageid=27160&docid=207759
Global Durian Market Forecast 2025–2035 Analysishttps://docs.google.com/document/d/1zRSTkKyu0IIPCyDX9nAnbck_KzRlcBIQxYkAAkqJ4nU/edit?usp=sharing
Global Coffee Supply Chain 2020-2035 Analysishttps://docs.google.com/document/d/13wAt2f3tb4lFWeEunjuNeUuWxPgPQPvWXvAs1BI_utM/edit?tab=t.0
Global Pepper Supply Chain 2020-2035 Analysishttps://docs.google.com/document/d/1apY9zRWlNkC1QLOK4qv53z0iFK7a8RrfggDKWx2H-Ls/edit?usp=sharing

# Cardano Grant Nguyen Hung Son: addr1q9lay7c9tfs8fd75fdrehr65ra7pe2zlvx6h3suvkgp7gnzcrg8a9484gvutlvjgwjvan63wk4spp8aj7h548h07y5msz2gk72