Skip to content

Latest commit

 

History

History
199 lines (132 loc) · 14.5 KB

CHANGELOG.md

File metadata and controls

199 lines (132 loc) · 14.5 KB

Change Log

Apache ResilientDB v1.12.0

Apache ResilientDB v1.12.0 (2026-2-04)

Core

  • Support Securing Consensus from Long-Range Attacks through Collaboration – PoC implementation merged (#215, closes #216). (Junchao Chen)
  • Support LevelDB with recovery data locally (#208). ResilientDB records every operation in the log and redoes the log on startup. Previously, the default memory storage required scanning all logs (not just from the latest checkpoint) to reconstruct state, so startup time grew with log size. This change adds LevelDB as a persistent storage backend: on startup, ResilientDB loads state from the data storage and only replays missing logs, reducing recovery time. (Junchao Chen)
  • Configuration format – Added support in existing config files for license headers.(Junchao Chen)
  • Remove public/private certificate files from source distribution – Dropped committed .pub/.pri cert and key files; replaced with a script to generate keys and certificates at setup time. (#228) (Harish Krishnakumar)

Ecosystem

  • GraphQL server and Python SDK – Resolved compatibility of the GraphQL server with the new config format; fixed a GraphQL bug in the Python SDK. (#228)(Harish Krishnakumar)
  • Deployment of ecosystem projects to Vercel using GitHub Actions – Automated deployment of ecosystem tools (ResLens, Beacon, Nexus, etc.) from the monorepo via GitHub Actions and Vercel. (#228) (Harish Krishnakumar)
  • Automated Document Generation Workflow – Workflow to keep documentation up to date using Pocketflow. (#229) (Bismanpal Anand)
  • ResLens – CPU and memory profiler with flame graphs and real-time metrics; Vercel deployment from monorepo. (Harish Krishnakumar, Bismanpal Anand)
  • Beacon – Documentation site, supplemented by AI-generated and human-verified insights from the codebase. (Harish Krishnakumar)(Bismanpal Anand)
  • Nexus – RAG application supporting chatting with documents ranging from consensus books, papers, and other materials related to PBFT and consensus research at ResilientDB. (Harish Krishnakumar)
  • GraphQ-LLM – MCP server and HTTP API: AI query tutor for ResilientDB GraphQL (RAG over docs, explanations, efficiency metrics). (Harish Krishnakumar)
  • ResilientDB MCP – MCP server for direct ResilientDB operations: GraphQL (asset/blockchain transactions) and HTTP REST key-value (Crow). (Harish Krishnakumar)

Contributors

The following contributors developed and maintained ecosystem components integrated into this repository. Attribution was lost during subtree merges; this section restores it.

Apache ResilientDB v1.11.0 (2025-4-27)

  • Support Combined Runtime for SmartContact and Key-value Service. (Junchao Chen)

Apache ResilientDB v1.10.1 (2024-4-16)

Apache ResilientDB v1.10.0 (2024-4-16)

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 (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

NexRes v1.3.0 (2023-02-22)

Implemented Enhancements:

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:

v2.0 (2020-02-29)

Implemented Enhancements:

Fixed Bugs:

v1.1 (2019-12-05)

Implemented Enhancements:

Fixed Bugs:

  • Docker script fails to run for multiple client #1 (RohanSogani)

v1.0 (2019-11-24)

Launched ResilientDB (Suyash Gupta and Sajjad Rahnama)