Conclusion

What it is

A-REX Core is the smallest set of interfaces that lets an ERC-1155 token id be an agricultural batch: a commodity and a unit, a production and an expiry time, an origin reference, a metadata commitment, a role-controlled lifecycle, and — through transform — a provenance graph that survives splitting, merging and processing. It adopts ERC-7943 for enforcement, defines one ordered hook pipeline with machine-readable rejection codes, and records attestations per batch with trusted issuers per topic. Everything else is outside the standard by design.

What the redesign established

• A standard and a product are different things. Mixing a farm registry, an identity system, enumerations of crops and grades, and a valuation formula into "the standard" was the first design we rejected. None of it survived the question would an independent implementer accept this constraint? The interfaces that did survive fit in six files.
• Lineage is the missing primitive. Traceability regulation and EPCIS are built around transformation events; a token that cannot become another token cannot serve a recall, a mass-balance audit or an FSMA transformation record. transform is now the only way to create a batch from a batch.
• Enforcement is not optional. Liens, warrants, seizures and recalls are ordinary events in agriculture; ERC-7943 gives them a standard shape and a standard audit trail.
• Legal neutrality is the safe position. The token does not decide whether it is a security or a commodity; it makes every classification implementable and keeps personal data off-chain in line with the EDPB's 2026 guidance.
• Reference implementations must be reproducible. Pinned dependencies, a committed lockfile, continuous integration, and a token under the EIP-170 limit are prerequisites for anyone to try the standard.

What it has not yet proved

• That real lots, real transformations and real enforcement actions run on it for months without the interfaces needing to change.
• That independent teams implement hooks and tokens against the interfaces without help from the authors.
• That the reference implementation withstands a third-party audit.

Until those three are true, A-REX is a well-defined proposal with a working implementation — not a standard. The roadmap does not skip that stage, because the standards that are used today (ERC-3643, ERC-7943) did not.

How to take part

• Issuers and platforms: deploy the reference stack on a testnet with your own lots; report what the interfaces could not express.
• Hook authors: write the rule you need (seasonal windows, quotas, custody, documents) against IARexHook and publish it; three independent hooks are an explicit milestone.
• Certifiers, laboratories, registries: become trusted issuers for your topics; attestations are how your work reaches buyers and regulators on-chain.
• Compliance and identity providers: expose your engine as an eligibility hook; ERC-3643 and ERC-7943 tooling adapts in a few lines.
• Counsel and regulators: review the regulatory chapter and the enforcement model; tell us where a jurisdiction needs something the interfaces do not provide.
• Auditors and researchers: the transfer pipeline invariants are small and stated; break them.

The written terms say the specification will be published under CC0 and the code under MIT. Until that publication, the text stays confidential under the early-access terms, and this site withholds it.