Apache ResilientDB v1.10.0-incubating

Apache ResilientDB v1.10.0-incubation (2024-7-11)

Add the prototype of PoE. (Junchao Chen)

• Implement the base version of the Proof-of-Execution (PoE) Consensus Protocol [EDBT 2011].

Add ResView Data Collection and APIs (Saipranav-Kotamreddy)

• Consensus data such as PBFT messages and states is now collected and stored
• Added APIs to query consensus data and progress of replicas
• Added APIs to trigger faultiness and test view change

NexRes v1.9.0

Support Multi-version Key-Value Interface. (Junchao Chen)

• Get and Set need to provide a version number to fetch the correct version of the data (if exists) or write to the correct version of data (if not overwritten already), respectively.
• Provide interfaces to obtain historical data with a specific version or a range of versions.

NexRes v1.8.0

The view-change recovery protocol was extensively expanded to support the following Byzantine failures through primary/leader replacement and replica recovery. (Dakai Kang)

• Byzantine primary becomes non-responsive, stopping proposing any new Pre-Prepare messages.
• Byzantine primary equivocates, proposing two different client requests to two subsets of replicas.
• Byzantine replicas try to keep some non-faulty replicas in the dark.
• Byzantine new primary becomes non-responsive, refusing to broadcast New-View messages.

NexRes v1.7.0

For each replica local recovery from durable storage upon system restart was added.

NexRes v1.6.0

Refactoring and enhancement of the codebase to highlight the entire software stack of ResilientDB consisting of the following layers

• SDK Layer (C++, Python, Go, Solidity)
• Interface Layer (key-value, smart contract, UTXO)
• ResilientDB Database Connectivity (RDBC) API
• Platform Layer (consensus, chain, network, notary)
• Transaction Layer (execution runtime and in-memory chain state)
• Storage Layer (chain and chain state durability)

NexRes v1.5.0

A complete refactoring of the code base such that (1) the core engine code is now moved to the platform folder, including the formwork architectures and protocols implementations; (2) the API/interface-related code is moved to the service folder, including UTXO, smart contract, and key-value interface; (3) the python SDK code is moved to a different repository here.

ResilientDB Legacy with SGX Acceleration (v3.1)

Creating a persistent release using Zenodo on the legacy codebase of ResilientDB (pre-NexRes).

NexRes v1.4.1

Creating a persistent release using Zenodo.

NexRes v1.4.0

Major Changes

Support of UTXO model and wallet integration: Detailed Documentation

NexRes v1.3.1

Bugfix

Fix build fail from kv_server
Fix build fail from Ubuntu 22