The Corda community is buzzing. Since Corda’s open source debut in 2016, we’ve had four full releases. Read the release notes to see Corda’s rapid progress and check out what’s next!
Corda has been on a rapid release cadence since its open source launch. Our planning process includes:
- Capturing community feedback and requirements.
- Adding priority information to that based on number of requests.
- Sorting priorities into a release T minus six weeks from current release completion.
- Estimating the work for the requirements with Jira story points.
- Communicating and estimating the delivery date.
Where we’ve been
With the help of our community, Corda has gone through a rapid evolution. Our latest release, Corda 4 is a big deal! Corda 4 includes 1800+ commits, new features, and compatibility with Corda 3.
What’s in Corda?
A critical step in the Corda journey, Corda 1 enables the developer community, clients, and partners to build on Corda with confidence and features significant changes in reaching API stability including:
Flow framework: The Flow framework communications API has been redesigned around session based communication with the introduction of a new FlowSession to encapsulate the counterparty information associated with a flow.
Complete API cleanup: All public interfaces have been thoroughly revised and updated to ensure a productive and intuitive developer experience.
Simplified annotation driven scanning: CorDapp configuration has been made simpler through the removal of explicit configuration items in favor of annotations and classpath scanning.
Java usability: All code has been updated to enable simple access to static API parameters. Developers no longer need to call getter methods, and can reference static API variables directly.
What’s new in Corda 2?
Observer nodes: Adds the facility for transparent forwarding of transactions to some third party observer, such as a regulator. By having that entity simply run an Observer node they can simply recieve a stream of digitally signed, de-duplicated reports that can be used for reporting.
Version bumps: Due to the introduction of new APIs, Corda 2.0 has a platform version of 2. This will be advertised in the network map structures and via the versioning APIs.
What’s new in Corda 3?
Wire stability: Any state generated by a Corda system is now retrievable, understandable, and seen as valid by any subsequently released version. Systems can thus be deployed safe in the knowledge that valuable and important information will always be accessible through upgrade and change.
Network Map Service: The network map service has been completely redesigned to enable increased network scalability and redundancy, reduced runtime operational overhead, support for multiple notaries, and administration of network compatibility zones.
Contract Upgrade: Support for the upgrading of contracts has been significantly extended in this release.
Test API Stability: A great deal of work has been carried out to refine the APIs provided to test CorDapps, making them simpler, more intuitive, and generally easier to use.
What’s new in Corda 4?
Official Docker images: Corda 4 adds an Official Corda Docker Imagefor starting the node. It’s based on Ubuntu and uses the Azul Zulu spin of Java 8.
Signature constraints: A new way to ensure correct CorDapp code is executed to verify transactions for secure and simple upgrades.
Reference states: Transactions can now reference states on ledger without requiring those states to be consumed.
Accounts: Allows business network operators to represent end-users or organizational entities as partitioned accounts on a single node opening up custodian type applications and new use cases as well as lowering barrier to entry for participants in Corda networks