Installation - c8ntinuum Docs

Requirements

Item	Value
Node	`>= 20`: the SDK uses the global `fetch`, `crypto.randomUUID` and Web Crypto (Ed25519 for Solana keypairs)
Browsers	any current browser, in a secure context (`https` or `localhost`)
Modules	ESM and CommonJS builds, with type declarations for both
Runtime dependencies	none
Optional peer	`viem >= 2.21.0`, only for the `/evm` entry point

Install

npm install @c8ntinuum/infinity-interop-sdk

pnpm add @c8ntinuum/infinity-interop-sdk

yarn add @c8ntinuum/infinity-interop-sdk

Add viem if you use the /evm adapters (a viem wallet client, or a key your server holds):

npm install viem

Entry points

Import	Use it in	Main exports
`@c8ntinuum/infinity-interop-sdk`	browser and Node	`createInteropClient`, `proxyTransport`, `projectTransport`, `executeQuote`, `vetQuote`, `trackOrder`, refunds, errors, `evmWalletFromEip1193`
`@c8ntinuum/infinity-interop-sdk/server`	Node only	`hubTransport`, `createInteropProxy`, `toNodeListener`, `memoryOwnershipStore`, `verifySubjectScoping`
`@c8ntinuum/infinity-interop-sdk/evm`	browser and Node	`evmWalletFromViem`, `evmWalletFromAccount` (needs `viem`)
`@c8ntinuum/infinity-interop-sdk/solana`	browser and Node	`solanaWalletFromStandard`, `solanaWalletFromKeypair`, `solanaRpc`

Keep /server out of your production browser code, and never ship your secret API key to a browser: a key in a page is a key anyone can use, and the hub’s gateway refuses a key from a browser anyway. A page reaches the hub through your backend (Partner backend) or with your public project id (Browser apps).

The entry points share one build, so an error class thrown by /server is the same class you catch from the root import (instanceof works across them).

First call

A backend sends its secret key with every call; here it reads the catalog:

import { createInteropClient, hubTransport } from "@c8ntinuum/infinity-interop-sdk/server";

const client = createInteropClient({
  transport: hubTransport({
    baseUrl: "https://proxy-api.infinimesh.net", // the hub's origin: the SDK adds /v1
    apiKey: process.env.HUB_API_KEY!, // c8n_sk_…, made for your project in the hub dashboard
  }),
});

const catalog = await client.getCatalog();
console.log(catalog.chains.map((chain) => chain.chainDomain));

There is no sign-in: the key goes in x-api-key on every call. On the routes where the hub requires X-Infinity-Subject, a call that names none of your users goes under the transport’s subject, default unless you set another. Next: the quickstart runs a full bridge, and Testing shows where the test hub’s keys come from.