Skip to main contentA-REX Core

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. Small enough for anyone to implement, open enough for any crop, rule or jurisdiction.

Read the whitepaperRead the specification

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 0MUST

    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 1MUST

    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 2MUST

    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 3SHOULD

    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 interfaces on ERC-1155, released under CC0System 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

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 ERC | Used 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

5interface ids a token answers to be conformant. Nothing else is required.Read the specification
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

Build on A-REX Core

Implement the standardDeploy the reference token or write your own. Compile, test and walk a lot through its life on a local node in minutes.Get started
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

Documentation