Standards

Standards

Nexa's public interoperability surface currently documents ERC-7683 and OIF. Their compatibility levels are intentionally different.

Standard	Published compatibility	Executable through this surface?
ERC-7683	EXECUTABLE_RESOLVER	Yes, through resolver-centric off-chain eth_call resolution.
OIF	DISCOVERY_DESCRIPTION_ONLY	No. The published module describes the mandate surface; execution resolution is unsupported.

ERC-7683

The public ERC-7683 resolver accepts the canonical Nexa execution payload for off-chain resolution. The committed manifest specifies that resolution:

• is a view-only eth_call and creates no transaction by itself;
• produces one execution call targeting the canonical Router function; and
• does not introduce another source-chain execution transaction.

Use the standards manifest, deterministic vectors, resolver vetting evidence, and ERC-7683 example for exact behavior.

OIF

The OIF module is published for discovery and mandate description only. Its compatibility level is DISCOVERY_DESCRIPTION_ONLY, executable is false, and execution resolution is specified as unsupported. Integrators must not present OIF as a Nexa execution path.

Use the standard IDs, standards manifest, deterministic failure/description vectors, and OIF description example.

Canonical standards resources

• Published standards endpoint
• Canonical standards manifest
• Standard IDs and compatibility levels
• Deterministic test vectors
• Solver-facing ABI
• ERC-7683 resolver vetting

Exact standard IDs, addresses, selectors, hashes, and payload encodings should always be read from these canonical machine-readable resources.