Provider routing

RoutedProvider lets an application use different providers for chain queries, transaction evaluation, and transaction submission while still passing a single provider into Blaze.

import { Blockfrost, Kupmios, Maestro, RoutedProvider } from "@blaze-cardano/query";

const provider = new RoutedProvider({
  defaultProvider: blockfrost,
  queryProvider: blockfrost,
  evaluationProvider: kupmios,
  submissionProvider: maestro,
});

Per-operation overrides are useful when a provider has a better implementation for a specific query.

const provider = new RoutedProvider({
  defaultProvider: blockfrost,
  queryProvider: blockfrost,
  evaluationProvider: kupmios,
  submissionProvider: maestro,
  perOperation: {
    resolveScriptRef: blockfrost,
    getUnspentOutputsWithAsset: maestro,
  },
});

All routed providers must target the same Cardano network. RoutedProvider rejects mixed network IDs and also rejects mismatched known network names, such as routing a cardano-preview default provider to a cardano-preprod submission provider. Providers with an unknown network name can still be used when the network ID matches.

Debug logging

Pass debugLogger to observe provider calls. The logger receives the operation, target provider, params, status, duration, and error when a provider throws.

const provider = new RoutedProvider({
  defaultProvider: blockfrost,
  evaluationProvider: kupmios,
  debugLogger(event) {
    console.debug(event.operation, event.status, event.durationMs);
  },
});

Applications should avoid logging secrets, API keys, signed transactions, or personally identifying data. The debug event exposes the original method parameters so callers can decide what to redact before writing logs.