Skip to content

2.0.0-dev5

Pre-release
Pre-release
Compare
Choose a tag to compare
released this 26 Oct 11:19
ccf-2.0.0-dev5
3b58d40

Added

  • Receipts now include the endorsed certificate of the node, as well as its node id, for convenience (#2991).
  • get_metrics_v1 API to BaseEndpointRegistry for applications that do not make use of builtins and want to version or customise metrics output.
  • Slow ledger IO operations will now be logged at level FAIL. The threshold over which logging will activate can be adjusted by the --io-logging-threshold CLI argument to cchost (#3067).
  • Snapshot files now include receipt of evidence transaction. Nodes can now join or recover a service from a standalone snapshot file. 2.x nodes can still make use of snapshots created by a 1.x node, as long as the ledger suffix containing the proof of evidence is also specified at start-up (#2998).
  • ccf.historical.getStateRange / ccf.historical.dropCachedStates JavaScript APIs to manually retrieve historical state in endpoints declared as "mode": "readonly" (#3033).
  • Log more detailed errors on early startup (#3116).
  • New split_ledger.py utility to split existing ledger files (#3129).

Changed

  • JavaScript endpoints with "mode": "historical" now expose the historical KV at ccf.historicalState.kv while ccf.kv always refers to the current KV state. Applications relying on the old behaviour should make their code forward-compatible before upgrading to 2.x with const kv = ccf.historicalState.kv || ccf.kv.

Removed

  • Receipts accessible through JavaScript no longer contain the redundant root hash field. Applications should be changed to not rely on this field anymore before upgrading to 2.x.

Fixed

  • Fixed issue with ledger inconsistency when starting a new joiner node without a snapshot but with an existing ledger prefix (#3064).
Assets 7
Loading