Use the Chain Registry

Orchestrate provides the Chain Registry API to register blockchain networks. Orchestrate is compatible with all Ethereum (EVM) based blockchain networks. Each time a new network is registered, Orchestrate automatically starts a transaction listener that processes transactions receipts being mined on the blockchain network.

The Chain Registry will store the following information:

  • uuid: Orchestrate’s unique internal identifier
  • name: user given name of the chain
  • urls: list of JSON-RPC URLs of nodes in the chains
  • listener: Transaction Listener configuration (optional)
    • fromBlock: block from which the Transaction Listener started processing transaction receipts (default latest)
    • backoffDuration: time to wait before trying to fetch a new mined block (for example 1s or 1m, default is 1s)
    • depth: block depth after which the Transaction Listener considers a block final and processes it (default 0)
    • blockPosition: last block processed by the Transaction Listener.
    • externalTxEnabled: whether to listen to external transactions, meaning not crafted by Orchestrate (default False)
  • privateTxManager: to be used for Quorum private transactions (optional)
    • url: transaction manager endpoint
    • type: Tessera


If using Besu private transactions, Orchestrate does not directly communicate with Orion so configuring the private transaction manager is not required.

Use the Chain Registry

Use the Orchestrate Chain Registry API to manipulate the Chain Registry. Use the ‘uuid’ of a chain will be useful for actions like to update, amend, deleting the chain, and so on.