Resielientdb v1.10.0 (2024-4-16)
Add the prototype of PoE. (Junchao Chen)
- Implement the base version of 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 (2023-11-29)
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 (2023-08-21)
Implemented Enhancements: 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 (2023-08-04)
Implemented Enhancements: For each replica local recovery from durable storage upon system restart was added.(Junchao Chen)
NexRes v1.6.0 (2023-05-30)
Implemented Enhancements: Refactoring and enhancement of the codebase to highlight the entire software stack of ResilientDB consisting of the following layers (Junchao Chen)
- 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 (2023-04-04)
Implemented Enhancements:
- A complete refactoring of the codebase 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 (Junchao Chen).
NexRes v1.4.0 (2023-02-28)
Major Changes
- Support of UTXO model and wallet integration: Detailed Documentation (Junchao Chen)
NexRes v1.3.0 (2023-02-22)
Implemented Enhancements:
- Added Python SDK that supports UTXO-like transactions such as asset creation, transfer, and multi-party validations. (Arindaam Roy, Glenn Chen, and Julieta Duarte)
- Added REST CROW endpoints to interface with the on-chain KV service. (Glenn Chen and Julieta Duarte)
- Extended KV service range queries. (Glenn Chen and Julieta Duarte)
Fixed Bugs:
- Fixed KV service queries on all values retrieving empty placeholder values (Glenn Chen)
NexRes v1.2.0 (2023-01-29)
Implemented Enhancements:
- Support smart contract compiled from Solidity. (Junchao Chen)
- Use eEVM as a back-end service to execute the contract functions. (Junchao Chen)
NexRes v1.1.0 (2023-01-03)
Implemented Enhancements:
- 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. (WayneWang)
ResilientDB: Global Scale Resilient Blockchain Fabric, VLDB 2020
NexRes v1.0.1 (2022-10-13)
Implemented Enhancements:
- Add node manager backend for resilientdb.com to launch NexRes locally. (Vishnu and Junchao Chen)
NexRes v1.0.0 (2022-09-30)
Implemented Enhancements:
- Release the next generation of RelisientDB referred to as NexRes. (Junchao Chen)
- NexRes supports PBFT as the default core protocol and provides a KV-Server as a service. (Junchao Chen)
- NexRes also supports LevelDB and RocksDB as the durable storage layer. (Junchao Chen)
- Add SDK endpoints. (Junchao Chen)
- Add implementation of Dashboard. (Jianxio)
- Add the recovery protocol and checkpoint on PBFT. (Junchao Chen and Vishnu)
NexRes v1.0.0-alpha (2022-09-22)
Implemented Enhancements:
- Release the next generation of RelisientDB, a complete rewrite and re-architecting, referred to as NexRes. (Junchao Chen)
- NexRes supports PBFT as the default core protocol and provides a KV-Server as a service. (Junchao Chen)
- NexRes also supports LevelDB and RocksDB as the durable storage layer. (Glenn Chen, Julieta Duarte, and Junchao Chen)
v3.0 (2021-09-30)
Implemented Enhancements:
- GeoBFT Protocol Added (Sajjad Rahnama)
- Work Queue structure changed (Sajjad Rahnama)
- Refactoring, and added Statistics and Scripts (Sajjad Rahnama)
v2.0 (2020-02-29)
Implemented Enhancements:
- A GUI display for ResilientDB to ease user interaction and analysis. #9 (Sajjad Rahnama and RohanSogani)
- Added support for Smart Contracts with a Banking use case. #7 (Sajjad Rahnama)
- Monitoring results for visualizing graphs using influxdb. #8 (Sajjad Rahnama, Dhruv Krishnan and Priya Holani)
- Added support for SQLite and provided a new representation for in-memory storage. #6 (Sajjad Rahnama)
Fixed Bugs:
- Bug in the Chain Initialization #5 (Sajjad Rahnama)
v1.1 (2019-12-05)
Implemented Enhancements:
- Defined class to represent ledger. 6b0fdc5 (Suyash Gupta)
Fixed Bugs:
- Docker script fails to run for multiple client #1 (RohanSogani)
v1.0 (2019-11-24)
Launched ResilientDB (Suyash Gupta and Sajjad Rahnama)