v22.3.0

* Deprecates the JSON-RPC API

Author: zah

CHANGELOG.md

@@ -1,3 +1,40 @@
+2022-03-07 v22.3.0
+==================
+
+Nimbus `v22.3.0` is a `low-urgency` upgrade that marks the beginning of a more predictable release cadence for Nimbus. Going forward, we'll be publishing a new release at the start of each month, following a feature freeze period with intensified testing and monitoring of the introduced code changes on our dispersed fleet of mainnet validators.
+
+> Please note that the new versioning scheme is tied to the calendar. The number 22 indicates the year of the release (2022), while 3 is the month (March). The last digit is the patch number of the release and it will have a non-zero value only when we ship a hotfix during the month.
+
+### Improvements:
+
+* Nimbus can now run as a service on Windows: use the `--run-as-service` flag
+  https://github.com/status-im/nimbus-eth2/pull/3441
+
+* All command-line options can now be provided in a configuration file: use the `--config-file` flag
+  https://github.com/status-im/nimbus-eth2/pull/3442
+
+* Lower CPU and bandwidth usage thanks to better handling of already seen attestation aggregates
+  https://github.com/status-im/nimbus-eth2/pull/3439
+
+* Reduced memory usage for nodes bootstrapped with [trusted node sync](https://nimbus.guide/trusted-node-sync.html)
+  https://github.com/status-im/nimbus-eth2/pull/3429
+
+### We've fixed:
+
+* Reduced performance on Windows due to the use of a less efficient method for collecting stack traces
+  https://github.com/status-im/nimbus-eth2/pull/3466
+
+* Non spec-compliant URLs in the [Keymanager APIs](https://nimbus.guide/keymanager-api.html) for handling remote keystores
+  https://github.com/status-im/nimbus-eth2/commit/4c01b777736f0d5d6fe38b37a4349741f6944e4c
+
+* Extremely slow [slashing DB import](https://nimbus.guide/migration.html#step-4---import-your-slashing-protection-history) for validators: the import should be pretty fast now
+  https://github.com/status-im/nimbus-eth2/pull/3393
+
+### Deprecated features:
+
+- The [JSON-RPC](https://nimbus.guide/api.html) service (`--rpc` flag) option is now deprecated. It's scheduled for removal in version `v22.6` (i.e June of this year). If you are currently relying on the JSON-RPC API, please consider switching to the official [REST API](https://nimbus.guide/rest-api.html).
+
+
 2022-02-15 v1.7.0
 =================
 

beacon_chain/conf.nim

@@ -322,7 +322,7 @@ type
         name: "status-bar-contents" }: string
 
       rpcEnabled* {.
-        desc: "Enable the JSON-RPC server"
+        desc: "Enable the JSON-RPC server (deprecated)"
         defaultValue: false
         name: "rpc" }: bool
 

beacon_chain/version.nim

@@ -13,8 +13,8 @@ when not defined(nimscript):
   let copyrights* = "Copyright (c) 2019-" & $(now().utc.year) & " Status Research & Development GmbH"
 
 const
-  versionMajor* = 1
-  versionMinor* = 7
+  versionMajor* = 22
+  versionMinor* = 3
   versionBuild* = 0
 
   versionBlob* = "stateofus" # Single word - ends up in the default graffiti

docs/the_nimbus_book/src/api.md

@@ -1,11 +1,12 @@
 # JSON-RPC API
 
+> The Nimbus JSON-RPC API has been deprecated and it’s scheduled for removal in version v22.6 of Nimbus (to be released in June 2022).
+  If you are currently relying on the JSON-RPC API, please consider switching to the [official REST API](./rest-api.md).
+
 The `JSON-RPC API` is a collection of APIs for querying the state of the application at runtime.
 
 The API is based on an early version of the common [beacon APIs](https://github.com/ethereum/beacon-APIs) with the exception that `JSON-RPC` is used instead of [http `REST`](./rest-api.md) (the method names, parameters and results are all the same except for the encoding / access method).
 
-Nimbus also implements the [common REST API](./rest-api.md) - new applications should consider using it instead of JSON RPC.
-
 The `JSON-RPC API` should not be exposed to the public internet.
 
 ## Introduction