Corda Accounts Library

In the context of Corda, the Corda Accounts Library allows a Corda node to partition the vault — a collection of state objects — into a number of subsets, where each subset represents an account. In other words, the Corda Accounts Library allows a Corda node operator to split the vault into multiple “logical” sub-vaults. This is advantageous for a couple of reasons:

  1. Node operators can reduce costs by hosting multiple entities, as accounts, on one node.
  2. Node operators can partition the vault on a per-entity basis.

Accounts are created by host nodes, which are just regular Corda nodes. Hosts can create accounts for a range of purposes, such as customer accounts, balance sheets or P&L accounts, employee accounts, and so on.

The Corda Accounts Library takes the form of a .jar file, which can be dropped into the CorDapps directory. It is optional to use - some nodes will support accounts but others will not. This functionality is intentional, as not all nodes will need to support accounts and the optional nature of accounts reduces the learning curve for new CorDapp developers.

You can access the Corda Accounts Library from the public repository .

To learn how to install and use the Corda Accounts Library, check out the readme and docs repo pages.

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.