Skip to main contentA-REX Foundation

A standard for every harvest

A-REX Core turns agricultural lots into interoperable tokens on the EVM: batch identity, lineage, enforcement and open rules on ERC-1155. The core is sized for any crop, rule, or jurisdiction. The normative text is requested through early access.

Read the whitepaperAbout the standard

How a batch moves through A-REX

Three operations change a batch: issuing it, transferring it and transforming it. Each one passes the same checks inside the token, in a fixed order. If one fails, nothing changes and the token returns the reason.

A-REX Core

On every movement, in this order

  1. 1Token not paused
  2. 2Both accounts enabled
  3. 3Batch active, balance not frozen
  4. 4Rules (hooks), one by one

The first failure stops the movement with a code. When all pass, balances, lineage and events are recorded.

Issue

Issuerproducer, cooperative, warehouse
Records the batchproduct, unit, dates, origin, document
Mints the units
First holder

Transfer

Holder A
Asks to transferReason if refused
Delivers the unitsevent recorded
Holder B

Transform

Processormill, packer, exporter
Input lotse.g. wheat
New lots, parents linkede.g. flour
New batch

Also acting on a batch

  • CertifierRecords an attestation per batch and topic, such as organic or EUDR. Rules can require it.
  • Enforcement roleFreezes amounts or forces a transfer under a court order. A pause does not stop it, and the rules still run.
  • Status roleRetires a batch for good. A retired batch can only be burned.

Anatomy of the standard

Four small layers on Ethereum. Scroll to take the stack apart, one layer at a time.

Scroll to take it apart

  1. EVM

    Ethereum

    Any EVM chain. The standard adds no new primitive: plain contracts and events that wallets, indexers and explorers already read.

    Read more
  2. Layer 0

    Token and enforcement

    ERC-1155 · ERC-165 · IERC7943MultiToken

    Balances and batch transfers from ERC-1155, interface detection from ERC-165, and from ERC-7943: freeze, forced transfer, eligibility and canTransfer.

    Read more
  3. Layer 1

    Batch

    IARexBatch

    The batch record with open codes, a role-only status with a terminal RETIRED, and transform, which keeps the parents of every split, merge or process on chain.

    Read more
  4. Layer 2

    Hooks

    IARexHook · IARexHookManager

    One hook interface, evaluated in order. A hook returns a bytes32 code instead of reverting for policy, so every rejection carries a machine-readable reason.

    Read more
  5. Layer 3

    Attestations

    IARexAttest

    Attestations per batch and topic, from issuers trusted per topic: certifications, inspections, warehouse receipts and due-diligence statements.

    Read more

Start here

WhitepaperWhy agricultural lots need their own token standardSpecificationFour layers on ERC-1155. The normative text is requested through early access.System designComponents, flows and security controls of the referenceDecisionsSixteen design decisions and the options they rejected

What the standard makes possible

Agricultural lots are the largest class of physical assets without an interoperable on-chain form. A-REX Core gives them one, and nothing more, so that every platform can speak it.

Fund a harvest before it exists A batch can be issued before production, so forwards, warrants and crop receivables use the same token as the delivered lot.Answer a recall in one query Splits, merges and processing keep their parents on-chain. Trace any lot back to its origin and forward to every product made from it.Carry the rules with the lot Perishability, seasons, custody and sanctions are hooks that any conformant token can attach, with a machine-readable reason for every refusal.Prove every claim about a lot Certifications, inspections, warehouse receipts and due-diligence statements become attestations from issuers trusted per topic.

How modules plug in

The token keeps an ordered pipeline of hooks; companion extensions read and write attestations beside it. None of them is part of the standard: any conformant token can take them, and anyone can write their own.

Choose a module

Token

Hooks, in order

Registry

Extensions

TokenARexToken

The reference batch token. Every mint, transfer and burn runs through its hooks, in order.

Read about the modules Source

Road to a Draft ERCUsed first, submitted later

The interfaces are submitted only after a production deployment has run real lots for six months and independent implementers have confirmed them.

Request early accessSee the roadmap

Built to be adopted

5interfaces in the core. The identifiers and the normative text are requested through early access.About the standard
0closed lists in the standard. Commodities, units, statuses and topics are open codes.See the design rationale
24.1 KBreference token, under the EIP-170 limit, with 46 tests including seeded invariants.Review the audit package
16architectural decision records, each with its context, options and implications.Browse the decisions

Work with A-REX Core

Request the standardThe repositories are private. Companies that implement A-REX, issue batches, or audit it can request read access.Request early access
Write a hookAdd a rule without touching the token. A hook returns a code; it never reverts for policy and can serve many tokens.Hook development guide
Audit the referenceScope, trust model, invariants, coverage and the open questions, prepared for an independent security review.Audit readiness

Founding members

Join the founding members of the A-REX standard.

Producers, cooperatives, exporters, banks, certifiers and technology teams that adopt A-REX first will be listed here when the standard and its association go public.

  • 01Open seat
  • 02Open seat
  • 03Open seat
  • 04Open seat
  • 05Open seat
  • 06Open seat
  • 07Open seat
  • 08Open seat
  • 09Open seat
  • 10Open seat
  • 11Open seat
  • 12Open seat
Become a founding member

Documentation

A-REX Foundation

The token standard for agricultural batches on the EVM.

Request early access
© 2026 A-REX Foundation. All rights reserved.A-REX Core 2.0.0-alpha.2 · specification and interfaces CC0-1.0 · reference implementation MIT · Built 2026-10-20