incubator-resilientdb

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

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.

View-Change algorithm in PBFT was added. Now PBFT-performance in NexRes is resilient to the following Byzantine behaviors and can replace primary and recover via the view-change algorithm. (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.

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

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)

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.

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

Creating a persistent release using Zenodo.

Major Changes

Support of UTXO model and wallet integration: Detailed Documentation

Bugfix

Fix build fail from kv_server
Fix build fail from Ubuntu 22

Major Changes

Added Python SDK that supports UTXO-like transactions such as asset creation, transfer, and multi-party validations.
Added REST CROW endpoints to interface with the on-chain KV service.
Extended KV service range queries.

Major Changes

Support smart contract compiled from Solidity.
Use eEVM as a back-end service to execute the contract functions.

Major Changes

Added Geo-Scale Byzantine Fault-tolerant consensus protocol, referred to as GeoBFT. It is designed for excellent scalability by using a topological-aware grouping of replicas in local clusters, giving rise to parallelization of consensus at the local level and by minimizing communication between clusters.

ResilientDB: Global Scale Resilient Blockchain Fabric, VLDB 2020

NexRes v1.0.1 (2022-10-13)

Changes

Add node manager backend for resilientdb.com to launch Nexres locally.

NexRes v1.0.0 (2022-09-30)

Changes

Release the next generation of RelisientDB referred to as Nexres.
Nexres supports PBFT as the default core protocol and provides a KV-Server as a service.
Nexres also supports LevelDB and RocksDB as the durable storage layer.
Add SDK endpoints.

NexRes v1.0.0-alpha (2022-09-22)

An alpha version of Nexres v1.0.0-alpha

Implemented:

• Release the next generation of RelisientDB referred to as Nexres.
• Nexres supports PBFT as the default core protocol and provides a KV-Server as a service.
• Nexres also supports LevelDB and RocksDB as the durable storage layer

GeoBFT Protocol (v3.0)

Major Changes

• GeoBFT Protocol Added
• Work Queue structure changed

Minor Changes

• Refactoring
• Scripts
• Statistics

Nanomsg Next Generation and Client Improvements (v2.1)

• Updated transport layer to new nanomsg library called NNG.
• Client Memory problem solved.
• Minor fixes for docker script.

Smart Contracts, DB Support and GUI Display (v2.0)

ResilientDB (v1.1)