> For the complete documentation index, see [llms.txt](https://ga.orilife.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ga.orilife.io/qna/economic.md).
# Economic
**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.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://ga.orilife.io/qna/economic.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.