Corda 5 Developer Preview 2 is now available.

Key concepts

Learn about the concepts and features that power Corda, so you can make the best of it. These articles provide an overview suitable for beginners and non-developers. The topics build on each other, so you should read them in order.

First, you’ll learn about the Corda ecosystem, and how people and businesses in it represent themselves and find each other.

Next, you’ll learn how nodes share and store information.

  • The ledger is the record of transactions on Corda.
  • Flows let nodes communicate with each other.
  • States represent shared facts on the ledger.
  • Vaults are where nodes store on-ledger shared facts.

Then, learn how nodes can exchange assets on Corda.

  • Smart contracts digitize agreements between nodes.
  • You can bring off-ledger data into a smart contract using oracles .
  • Transactions update the ledger.
  • The ledger is only updated if the nodes reach consensus .
  • Notaries assure uniqueness consensus—meaning they prevent double-spends.
  • You can use Merkle trees to add additional security to transactions that use oracles and non-validating notaries.
  • Time windows let you validate that a transaction happened before, after, or during a specific time.

After you’re familiar with the key concepts of Corda, see them in action by running a sample CorDapp .

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.