Obtain the integration SDK distribution through your integration access. Confirm the available package source before adding a registry dependency. This documentation does not assume that the package is published to a public registry. The package identifier remains @c8ntinuum/infinity-interop-sdk despite the documentation section’s new name.

Entry points

Use the package manifest for supported runtime and peer dependencies. The EVM adapters require viem. Browser cryptographic operations require a secure context and the required Web Crypto capabilities. Keep the /server entry point out of browser bundles. Keep API keys and server-held wallet keys in server-side secret storage.

Compatibility checks

Check the installed client’s request validation and quote verification against the selected Infinity Hub schema. In particular, verify support for slippage allocations, EIP-3009, Solana wallet plans, and chain-only status responses. Infinity Hub’s acceptance of a request does not establish that an older client can validate its response.

Signing trust

Configure trusted chains, settlers, oracles, proxies, routers, and programs independently of quote responses. Pass this configuration as signingTrust. A missing or invalid trust configuration must prevent signing.