> For the complete documentation index, see [llms.txt](https://nexchain.gitbook.io/nexchain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nexchain.gitbook.io/nexchain/developer-integration.md).

# Developer Integration

This section outlines the intended developer experience at a conceptual level. Concrete endpoints, addresses, SDK packages, and parameters will be published in dedicated developer documentation as they are finalized.

Because the execution environment is EVM-compatible, the developer workflow is intended to be familiar:

* **Contracts** — written in standard Solidity and deployed using common development frameworks, with little to no Nexchain-specific modification required.
* **Wallets** — standard EVM wallets can connect to the network through its RPC interface.
* **Tooling** — existing libraries for contract interaction, testing, and deployment are expected to work against the network's standard interfaces.

What distinguishes building on Nexchain is access to network-level risk intelligence. The intended model is that applications can query risk signals — for example, scoring a pending transaction or evaluating a counterparty address — and surface those signals to their own users. This turns transaction safety from a feature each team must build independently into a shared network service.

A typical integration flow is conceptually:

1. Connect to the network via its RPC endpoint.
2. Build and submit transactions using standard EVM tooling.
3. Optionally, request a risk assessment for a transaction or address through the risk interface before prompting the user to sign.
4. Surface the returned assessment and its contributing factors in the application's own interface.

*Status: developer SDKs, the risk API, and full integration documentation are planned ahead of mainnet (see Roadmap). The description above reflects intended design, not a finalized, released interface.*