Networks and Environments

The Evo SDK supports four built-in network configurations plus custom addresses for private or development networks.

Built-in networks

For each network, the SDK discovers DAPI endpoints from seed nodes and rotates between them automatically. Failed nodes are temporarily banned so the SDK retries against healthy nodes.

Devnets

Devnets are long-lived shared development networks identified by a short name (e.g. 'paloma'). The trusted context derives the quorum base URL from the name as https://quorums.<name>.networks.dash.org:

const sdk = EvoSDK.devnetTrusted('paloma');
await sdk.connect();

If the public quorums DNS for a devnet isn't deployed yet, override the URL:

const sdk = EvoSDK.devnetTrusted('paloma', {
  quorumUrl: 'https://quorums.staging.example/',
});
await sdk.connect();

For a devnet without any trusted context (no proof verification), supply explicit DAPI addresses:

const sdk = EvoSDK.devnet('paloma', {
  addresses: ['https://10.0.0.5:1443'],
});
await sdk.connect();

Behind the scenes these factories call WasmTrustedContext.prefetchDevnet(name) or prefetchDevnetWithUrl(url); the same shape is available on prefetchMainnetWithUrl / prefetchTestnetWithUrl for staging endpoints (production networks must use https://).

Local development with Docker

When running a local Platform network via dashmate, use the local network:

const sdk = EvoSDK.localTrusted();
await sdk.connect();

This connects to https://127.0.0.1:1443 by default. If your local setup uses different ports, use custom addresses:

const sdk = EvoSDK.withAddresses(
  ['https://127.0.0.1:2443'],
  'local',
);
await sdk.connect();

Custom masternode addresses

For private devnets, specific nodes, or debugging:

const sdk = EvoSDK.withAddresses(
  [
    'https://52.12.176.90:1443',
    'https://34.217.100.50:1443',
  ],
  'testnet',
);
await sdk.connect();

When custom addresses are provided, the SDK does not perform automatic node discovery — it uses only the addresses you supply.

Browser vs Node.js

The SDK works identically in both environments. The underlying WASM module handles platform differences transparently.

Node.js considerations:

• Requires Node.js ≥ 18.18 (for WebAssembly and fetch support)
• ESM-only package — use import, not require
• No additional polyfills needed

Browser considerations:

• Works in any browser with WebAssembly support (all modern browsers)
• The WASM module is loaded asynchronously on first connect() call
• Total bundle size includes the compiled Rust SDK (~2-4 MB gzipped)
• gRPC calls use grpc-web over HTTPS, compatible with standard CORS