Type Members

1.  class SynchronizerAliasManager extends NamedLogging with SynchronizerAliasResolution
2.  trait SynchronizerAliasResolution extends AutoCloseable
3.  final case class SynchronizerConnectionConfig(synchronizerAlias: SynchronizerAlias, sequencerConnections: SequencerConnections, manualConnect: Boolean = false, synchronizerId: Option[SynchronizerId] = None, priority: Int = 0, initialRetryDelay: Option[NonNegativeFiniteDuration] = None, maxRetryDelay: Option[NonNegativeFiniteDuration] = None, timeTracker: SynchronizerTimeTrackerConfig = SynchronizerTimeTrackerConfig(), initializeFromTrustedSynchronizer: Boolean = false) extends HasVersionedWrapper[SynchronizerConnectionConfig] with PrettyPrinting with Product with Serializable

   The synchronizer connection configuration object

   The synchronizer connection configuration object

   synchronizerAlias

   alias to be used internally to refer to this synchronizer connection

   sequencerConnections

   Configuration for the sequencers. In case of BFT synchronizer - there could be sequencers with multiple connections. Each sequencer can also support high availability, so multiple endpoints could be provided for each individual sequencer.

   manualConnect

   if set to true (default false), the synchronizer is not connected automatically on startup.

   synchronizerId

   if the synchronizer id is known, then it can be passed as an argument. during the handshake, the participant will check that the synchronizer id on the remote port is indeed the one given in the configuration. the synchronizer id can not be faked by a synchronizer. therefore, this additional check can be used to really ensure that you are talking to the right synchronizer.

   priority

   the priority of this synchronizer connection. if there are more than one synchronizer connections, the com.digitalasset.canton.participant.protocol.submission.routing.TransactionRoutingProcessor will pick the synchronizer connection with the highest priority if possible.

   initialRetryDelay

   synchronizer connections are "resilient". i.e. if a connection is lost, the system will keep trying to reconnect to a synchronizer.

   maxRetryDelay

   control the backoff parameter such that the retry interval does not grow above this value

   timeTracker

   the synchronizer time tracker settings. don't change it unless you know what you are doing.

   initializeFromTrustedSynchronizer

   if false will automatically generate a SynchronizerTrustCertificate when connecting to a new synchronizer.

4.  trait SynchronizerHandle extends AutoCloseable

   A context handle serving all necessary information / connectivity utilities for the node to setup a connection to a new synchronizer

5.  trait SynchronizerRegistry extends AutoCloseable

   A registry of synchronizers.

6.  sealed trait SynchronizerRegistryError extends Product with Serializable with ContextualizedCantonError
7.  trait SynchronizerRegistryHelpers extends FlagCloseable with NamedLogging with HasCloseContext