MULTILEDGER DOWNLOAD

genesis_url: The url from which to download the genesis transactions to use for connecting to an Indy ledger.genesis_transactions: String of genesis transactions to use for connecting to an Indy ledger.genesis_file: The path to the genesis file to use for connecting to an Indy ledger.

prefer production ledgers over non-production ledgers)ДЇor connecting to ledger, one of the following needs to be specified: This is used by the pool selector algorithm to know which ledger to use for certain interactions (i.e. is_production*: Whether the ledger is a production ledger.id*: The id (or name) of the ledger, can also be used as the pool name if none provided.Example config file:ДЇor each ledger, the required properties are as following: If -genesis-transactions-list is specified, then -genesis-url, -genesis-file, -genesis-transactions should not be specified. aries_cloudagent/config/multi_ledger_config.yml This parameter accepts a string which is the path to the YAML configuration file. You can enable support for multiple ledgers using the -genesis-transactions-list startup parameter. More background information including problem statement, design (algorithm) and more can be found here. If no write ledger is assigned then a ConfigError is raised. Write ledger can be assigned using is_write in the configuration or using any of the -genesis-url, -genesis-file, and -genesis-transactions startup (ACA-Py) arguments. For write requests, dynamic allocation of write_ledger is not supported. For read requests, checking of multiple ledgers in parallel is done dynamically according to logic detailed in Read Requests Ledger Selection. Ability to use multiple Indy ledgers (both IndySdk and IndyVdr) for resolving a DID by the ACA-Py agent.

Multiledger