Ledgers

Nutrimatic scopes data by ledger — one blockchain or network family.

Supported ledgers

Use these values in the ledgers field of createNutrimaticSdk config.

Display name	Kind	Ledger ID	Alias	Details
Infinite Mainnet	`evm`	`evm:421018`	`infinite-mainnet`	Below

You can also call catalog.listLedgers() at runtime to list available ledgers.

Ledger types

Two types, two roles — do not mix them in examples:

Type	Where	What you pass
`LedgerRef`	`createNutrimaticSdk({ ledgers })` only	Full object: `id`, `kind`, `chainId`, optional `alias`
`LedgerScope`	Method inputs (`ledgers: [...]`)	Ledger ID or alias from your config
`LedgerId`	Method outputs (`Quote.ledger`, `ExecutionHandle.ledger`, …)	Always the canonical `id` — never an alias

type LedgerScope = LedgerId | string  // 'evm:421018' | 'infinite-mainnet'

LedgerScope is for arguments you pass in. Use the ledger id (e.g. evm:421018) or its alias (e.g. infinite-mainnet) inside a ledgers array when filtering method calls. Responses always echo the canonical LedgerId. The SDK resolves kind and chainId automatically — see Filtering with ledgers.

interface LedgerRef {
  readonly id: LedgerId       // e.g. 'evm:421018'
  readonly kind: 'evm' | 'bitcoin' | 'cosmos'
  readonly chainId?: number | string
  readonly alias?: string
}

Config validation rules (unique IDs, unique aliases, no alias/id collision) are in Configuration — Config rules. Type reference: Types — LedgerRef.

Infinite Mainnet (EVM)

Field	Value
Display name	Infinite Mainnet
Kind	`evm`
Chain ID	`421018`
Ledger ID	`evm:421018`
Alias	`infinite-mainnet`
Native instrument symbol	`42`
Service fee (`costs` kind `service`)	Fixed `0.0001` `42` on every write — see Fees and costs

Example instrument ID:

evm:421018:instrument:42

Example venue ID pattern:

evm:421018:amm:v2:0x…

Resource IDs

Most API responses and SDK methods use stable Nutrimatic IDs (not raw contract addresses in user-facing layers). Pass these IDs back into SDK calls as documented per method.

Writes and settlement

Read and write share the same ledger model. Method filters use LedgerScope on input. Signing and execution return the canonical ledger ID on SignRequest, Quote, and ExecutionHandle. Multi-step plans use Path and settlement.track — the integrator does not coordinate bridge steps manually.

→ Write operations · Settlement

Errors Wallet adapter