16 documents
Whitepaper
Rationale, regulation, use cases and the road to standardization, in sixteen chapters.
The whitepaper explains why A-REX Core exists, what it standardizes, how it is built and what it means legally and commercially. Every technical claim points to code or to a test, and every regulatory claim to a dated primary source.
Reading paths
| If you are | Read | Time |
|---|---|---|
| Deciding whether to adopt it | 01 Executive Summary · 03 Problem Statement · 10 Use Cases · 15 Conclusion | 25 min |
| Implementing it | 04 Solution Overview · 05 Technical Specification · 07 Hooks · 11 Implementation Guide · 13 Performance | 90 min |
| Assessing risk and compliance | 06 Core Standard · 08 Security Framework · 09 Regulatory Compliance · 12 Interoperability | 60 min |
| Planning the roadmap | 02 Introduction · 14 Future Developments · 16 Appendices | 30 min |
What each part covers
| Part | Chapters | Content |
|---|---|---|
| Why | 01–03 | the gap in today's token standards, the requirements a batch token must meet |
| What | 04–07 | the four layers, the normative summary, the reasoning behind each field, hooks and extensions |
| How safely | 08–09 | threat model, invariants, access control; food traceability, EUDR, securities and commodities law |
| How to use it | 10–13 | end-to-end use cases, the executed implementation guide, interoperability, measured gas |
| What next | 14–16 | roadmap to a Draft ERC, conclusions, interface reference, glossary and FAQ |
The same text is available as one plain-text file at /llm-full.txt.
Documents
Executive Summary
A-REX Core in one chapter: what the standard is, what it deliberately leaves out, how it is positioned legally, and how it intends to become a de-facto standard before it becomes an official one.
Introduction
Why agricultural batches need a token standard, what exists today, what the regulatory drivers actually are (with dates verified in September 2026), and how A-REX approaches the problem.
Problem Statement
The specific gaps that A-REX Core addresses, stated as engineering and legal problems rather than as market sizes. Where an earlier version of this document quoted figures without a verifiable source, they have been removed.
Solution Overview
Architecture of A-REX Core: three tiers with one direction of dependency, the transfer pipeline, the actors, and how the pieces are deployed.
Technical Specification
Normative summary of A-REX Core: conformance, interfaces, operation semantics, the hook contract, attestations, storage and upgrade rules. The authoritative text is standard/AREX-CORE.md; this chapter restates it for readers of the whitepaper.
Core Standard
The rationale behind each element of A-REX Core: why the batch record has exactly these fields, why lineage is an operation and not a mapping, why enforcement comes from ERC-7943, why codes replace enums, and which lessons shaped the design.
Hooks and Reference Modules
How functionality is added to a conformant token without touching the standard: the hook contract, the reference hooks, the companion extensions, and how to write, test and register your own.
Security Framework
Threat model, invariants, access control, the hook trust boundary, enforcement key management, upgrade safety and audit posture of the A-REX Core reference implementation.
Regulatory Compliance
How A-REX Core maps to the regimes that govern agricultural lots and the tokens that represent them. Dates and legal references were verified in September 2026; where a statement is an inference rather than a verified fact, it is marked. Nothing here is legal advice.
Use Cases
Six scenarios showing how the four interfaces of A-REX Core, plus hooks, cover the situations that a grain elevator, a cooperative, an exporter, a lender and a regulator actually face. Each scenario names the calls involved.
Implementation Guide
From a clean clone to a deployed, hooked, attested batch token, step by step. Every JavaScript block in this chapter is copied from test/standard/ImplementationGuide.test.js and runs in CI; if a block here were wrong, the build would fail.
Interoperability
How an A-REX token fits the existing world: Ethereum token standards, compliance engines, traceability data standards, legal-document registries, identity systems, cross-chain infrastructure and existing farm systems.
Performance Analysis
Measured gas of the reference implementation with zero, one and two hooks; what drives the cost; and deployment guidance.
Future Developments
The roadmap from a frozen alpha interface to a de-facto and then an official standard, and the technical work that accompanies it. Dates are targets, not promises.
Conclusion
What A-REX Core is, what it proved, what it still has to prove, and how to take part.
Appendices
Authoritative sources: contracts/standard/ .sol (CC0) and standard/AREX CORE.md. Interface ids reproduced by npm run interface ids.