API: ServiceHub

Within FlowLogic.call, the flow developer has access to the node’s ServiceHub, which provides access to the various services the node provides. The services offered by the ServiceHub are split into the following categories:

  • ServiceHub.networkMapCache

    • Provides information on other nodes on the network (e.g. notaries…)
  • ServiceHub.identityService

    • Allows you to resolve anonymous identities to well-known identities if you have the required certificates
  • ServiceHub.attachments

    • Gives you access to the node’s attachments
  • ServiceHub.validatedTransactions

    • Gives you access to the transactions stored in the node
  • ServiceHub.vaultService

    • Stores the node’s current and historic states
  • ServiceHub.keyManagementService

    • Manages signing transactions and generating fresh public keys
  • ServiceHub.myInfo

    • Other information about the node
  • ServiceHub.clock

    • Provides access to the node’s internal time and date
  • ServiceHub.diagnosticsService

    • Provides diagnostic information about the node, including the node version and currently running apps. Note that this data should be used for diagnostic purposes ONLY
  • ServiceHub.contractUpgradeService

    • Provides functionality for secure contract upgrades

Additional, ServiceHub exposes the following properties:

  • ServiceHub.loadState and ServiceHub.toStateAndRef to resolve a StateRef into a TransactionState or a StateAndRef
  • ServiceHub.signInitialTransaction to sign a TransactionBuilder and convert it into a SignedTransaction
  • ServiceHub.createSignature and ServiceHub.addSignature to create and add signatures to a SignedTransaction

Was this page helpful?

Thanks for your feedback!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Create an issue

Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.