Platform · 09
Interoperability add-ons
Three optional add-ons let a company's lots and certificates be read by tools built for other standards: ERC-3643, the Ethereum Attestation Service and ONCHAINID. They change nothing about how a company works.
Why
Some buyers, banks, registries and verification tools already read records in formats that other standards define. Instead of asking them to learn A-REX, a company can turn on an add-on that presents its own records in their format. Every answer still comes from the company's A-REX records; the add-ons never hold a second version of the truth.
Lots stay lots of goods. A format borrowed from another field does not make a lot a financial product, and no add-on makes anything compliant with any law.
The three add-ons
| Add-on | What it adds |
|---|---|
| ERC-3643 compatibility | each lot can also be read as an ERC-3643 token: who holds how much, and whether a delivery would be allowed. It is a lot rule that never stops an operation |
| Publish certificates to EAS | copies of the company's lot records and certificates on the Ethereum Attestation Service, replaced when the original changes and withdrawn when it is withdrawn |
| Company identity on ONCHAINID | links the company to an ONCHAINID identity, so that identity registries that follow ERC-3643 can read the company check as a claim |
An owner turns them on in Settings ▸ Lot rules, and each change is approved like any other. The lot page's Interoperability tab then shows what each add-on published for that lot. Where an add-on is not available on a company's ledger, the platform says so before anything is sent. Turning an add-on off is approved the same way; copies already published are withdrawn as their originals are.
Each country's profile and each ledger come with defaults; nothing is turned on without the owner's approval.
Status
The add-ons are in alpha and run on test ledgers. Their contracts have not been independently audited, and they are not used on a public production network until they are. Issuing the company-check claim on ONCHAINID needs a company-check issuer that A-REX trusts; that part is not built yet.
Technical detail
- The add-ons ship in release 2.0.0-alpha.5 of the reference implementation: the A-REX core of 2.0.0-alpha.4 unchanged, plus an ERC-3643 adapter that creates one ERC-3643 view per lot, an EAS mirror and a claim issuer. Their design is in the standard's decision records ADR-020 (ERC-3643), ADR-021 (ONCHAINID) and ADR-022 (EAS), all three Proposed.
GET /v1/batches/{key}/interopand the MCP toolarex_interop_statusreport, per lot, the ERC-3643 view, the EAS copies and the identity link.- EAS copies are published and kept in step by a background job when lots and certificates change; when the mirror is turned on, existing lots are copied in pages.
- How these formats map to the standard: Interoperability in the whitepaper.