-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Nexa's public Mainnet V6 integration repository provides machine-readable discovery, verified solver-facing contract identities, a signed Feed protocol, execution Permit APIs, interoperability material, SDKs, and passive indexing packages.
It is intended for:
- solvers and solver operators;
- aggregators and wallets;
- passive indexers and scanners;
- intent frameworks; and
- SDK and API integrators.
Canonicality: This Wiki is an explanatory navigation layer. The machine-readable artifacts in the public repository and the published Nexa endpoints take precedence over Wiki text.
| Canonical surface | Use |
|---|---|
| Solver discovery | Start an automated solver, wallet, or aggregator integration. |
| On-chain discovery fingerprint | Inspect public selectors, events, identities, and verification references. |
| Standards discovery | Discover the published ERC-7683 and OIF compatibility surface. |
| OpenAPI 3.1 document | Generate or validate HTTP clients against the public API. |
| Public integration manifest | Navigate the committed artifact set. |
For a repository-based start, follow the root README and the machine-readable onboarding record.
Discovery → Signed Feed → Route → Permit → Resolution → Execution
- Resolve the public discovery document and published on-chain identities.
- Fetch the signed Feed and verify its authenticated payload.
- Select a route from verified live terms and retrieve its canonical detail.
- Request the Permit message, sign it in the integrating wallet, and request the execution Permit.
- Resolve or build the canonical Router call.
- Submit the source transaction and observe public fill/status signals.
See Solver Integration for the evidence-linked lifecycle.
| Network | Chain ID |
|---|---|
| Base | 8453 |
| BNB Smart Chain | 56 |
| HyperEVM | 999 |
See the canonical network IDs and public integration bundle for current identifiers and deployment metadata.
Verify each authority layer in order:
- the on-chain Registry and Router establish protocol identity and on-chain state;
- the cryptographically verified Signed Feed is authoritative for current live route terms; and
- a valid Execution Permit is the final execution authority.
The Graph, Substreams, scanners, analytics, and this Wiki are non-authoritative discovery aids. See Indexing and Verification & Security.
- Solver Integration - public API and execution lifecycle
- Networks & Contracts - verified public deployment surface
- SDKs - cross-language contract and implementations
- Standards - ERC-7683 and OIF compatibility boundaries
- Indexing - passive Graph and Substreams projections
- Verification & Security - public evidence and trust boundaries
- Resources - canonical files, endpoints, and examples