Standard
Implementations
What counts as an implementation of A-REX Core, which implementations are listed, what a conformance claim says, and how an implementation gets listed.
What an implementation is
An implementation is software that others can check against the standard. It takes one of four forms:
- a batch token that implements the interfaces of the standard;
- a hook: a rule contract that implements
IARexHookand can serve many tokens; - an attestation registry: a companion contract that implements
IARexAttestfor an existing token; - a platform that operates tokens for others, on its own implementation or on the reference implementation deployed unchanged.
Wallets, explorers, indexers and other tools that only read A-REX tokens can be listed too, but they have nothing to conform to.
The reference implementation
The reference implementation is arex-contracts, under the MIT licence. It holds the token and its attestation registry (ARexToken and ARexAttestations), example rule contracts and the conformance suite. It shows that the standard can be implemented; it is not the standard, and an implementation does not have to reuse its code. While the repositories are private, it is shared together with the standard through Request early access.
Listed implementations
The list follows ADOPTERS.md in the standard repository, which is the authoritative record. Rows are kept in alphabetical order, and every row is listed on the same terms.
| Organization | Role | Implementation | Chain | Status | Contact |
|---|---|---|---|---|---|
| A-REX Foundation: A-REX Platform | platform | operates tokens for companies with the reference implementation, deployed unchanged from its releases | not on a public network yet | in development | [email protected] |
The A-REX Foundation also maintains the specification and the reference implementation, so A-REX Platform is not an independent implementer: it does not count toward the two-implementer rule that governs changes to the standard. No independent implementer is listed yet.
The roles are issuer, warehouse, lab, platform (operates tokens for others), wallet and indexer. The statuses are planned, in development, pilot (real batches, limited scope), production, conformant (passes the conformance suite, with the report linked) and retired.
What conformance means
Conformance is checked with the conformance suite that ships with the reference implementation. The suite reaches an implementation only through the interfaces of the standard and a small adapter written by its authors, so it tests every implementation the same way. Each test carries the clause it checks: 87 clauses, 74 at MUST level and 13 at SHOULD level. A run ends with one of three verdicts:
| Verdict | Meaning |
|---|---|
CONFORMANT | every MUST clause passes |
CONFORMANT (with skipped MUST clauses) | no MUST clause fails, but some were skipped because the implementation does not offer what they need |
NOT CONFORMANT | at least one MUST clause fails |
Unmet SHOULD clauses are reported and do not change the verdict.
A conformance claim names the version of A-REX Core, the profile, the version or commit of the suite and the date of the run. It is published with the unedited report, the commit or deployed addresses that were tested, the SHOULD clauses that are not met and any intentional deviation, and it must explain every skipped MUST clause. A claim holds for one version of the standard: it is run again after an upgrade and for each new major version.
A report is evidence of how an implementation behaved on the clauses the suite checks. Clauses that cannot be observed on chain, such as the rule that the origin reference holds no personal data, are left to review, so a report does not cover everything the standard requires.
A listing is not an endorsement
A row records what an organization states about its own implementation. It is not an endorsement, a certification or an audit by the A-REX Foundation or by the editors of the standard, and there is no paid certification and no fee. A conformant status rests on the published report linked from the row; the editors can ask for a claim to be corrected or withdrawn when the report does not support it. A row whose contact does not answer for six months, or whose links stop working, may be marked retired after notice.
How to be listed
- Open a pull request that adds one row to
ADOPTERS.mdin the standard repository, with the columns of the table above. While the repository is private, ask for access first on Request early access. - Give a contact that answers. Listed implementers are asked to confirm or object to proposed changes to the standard.
- For the
conformantstatus, link the report of your conformance claim. - To count as an independent implementer, state in the pull request that your organization is not controlled by, and not paid by, the A-REX Foundation or another listed implementer for this work.
Independent implementers carry the two-implementer rule: a minor change is accepted when two of them confirm they can adopt it, and a major change when two of them have implemented it and pass the conformance suite with it. Until two exist, accepted changes are marked provisional.