Version 2.1 (#1134)

* bump version to 2.1 * update CHANGELOG * update killswitch for 2.1 * _version_nodeVersion in rosetta network options test * Change kill switch date, mention 1130 in changelog * Remove 1132 from the 2.1 changelog Co-authored-by: Doug Beardsley <[email protected]>
kadena-io · Aug 10, 2020 · 6f29cef · 6f29cef
1 parent 02ca529
commit 6f29cef
Show file tree

Hide file tree

Showing 4 changed files with 54 additions and 4 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,5 +1,55 @@
 # `chainweb-node` Changelog
 
+## 2.1 (2020-08-11)
+
+This version replaces all previous versions. Any prior version will stop working
+on **2020-08-13T00:00:00Z**. Node administrators must upgrade to this version
+before that date.
+
+This version will stop working on **2020-10-15T00:00:00Z**.
+
+*Forks:*
+
+This version includes the fork that adds 10 additional chains to Chainweb
+resulting in 20 chains in total. The fork will occur on
+
+*   Mainnet at block height 852,054, which is expected to happen around
+    2020-08-20 16:55:14 UTC.
+
+The mining API of chainweb-node will start serving work items for the new chains
+starting at above block heights for the respective network. The mempool and pact
+service APIs will accept requests already some time before the transition. POW
+difficulties will re-adjust within a few hours after the transition. During that
+time block rates may be slightly higher or lower than usual.
+
+*Possibly Breaking Changes:*
+
+*   Fix the database location and layout when a custom location is configured.
+    (#1128)
+
+    This only affects users who configured custom database locations.
+
+    This is a potentially breaking change. The chainweb node tries hard to
+    adjust the database location by itself without user intervention. If you
+    have tooling that depends on a custom database location, you may want check
+    the logs at first start up and double check that everything works as expected.
+
+*   Deprecate the use of the node-id configuration. (#1128)
+
+    This only affects users who configured the node-id either on the command line or
+    in the configuration files.
+
+    Any node-id settings are now ignored. In particular the database locations
+    doesn't include the node-id any more and just defaults to `0/rocksDb` and
+    `0/sqlitedb`.
+
+*Other Changes*:
+
+*   Fix a bug where Chainweb node would fail to start when it stopped after
+    the last block that pact evaluated got orphaned. (#1123)
+*   Improve failure response for invalid solved work. (#1126)
+*   Fix mainnet coin v2 upgrade for new chains. (#1130)
+
 ## 2.0 (2020-07-11)
 
 This version replaces all previous versions. Any prior version will stop working

diff --git a/chainweb.cabal b/chainweb.cabal
@@ -1,7 +1,7 @@
 cabal-version: 2.4
 
 name:         chainweb
-version:      2.0
+version:      2.1
 synopsis:     A Proof-of-Work Parallel-Chain Architecture for Massive Throughput
 description:  A Proof-of-Work Parallel-Chain Architecture for Massive Throughput.
 homepage:     https://github.com/kadena-io/chainweb

diff --git a/node/ChainwebNode.hs b/node/ChainwebNode.hs
@@ -493,10 +493,10 @@ pkgInfoScopes =
 -- -------------------------------------------------------------------------- --
 -- main
 
--- KILLSWITCH for version 2.0
+-- KILLSWITCH for version 2.1
 --
 killSwitchDate :: Maybe String
-killSwitchDate = Just "2020-08-13T00:00:00Z"
+killSwitchDate = Just "2020-10-15T00:00:00Z"
 
 mainInfo :: ProgramInfo ChainwebNodeConfiguration
 mainInfo = programInfoValidate

diff --git a/test/Chainweb/Test/Rosetta/RestAPI.hs b/test/Chainweb/Test/Rosetta/RestAPI.hs
@@ -389,7 +389,7 @@ genesisId = BlockId 0 "rdfJIktp_WL0oMr8Wr6lH49YkERAJ9MlFp0RPLMXPDE"
 rosettaVersion :: RosettaNodeVersion
 rosettaVersion = RosettaNodeVersion
     { _version_rosettaVersion = "1.3.1"
-    , _version_nodeVersion = "2.0"
+    , _version_nodeVersion = "2.1"
     , _version_middlewareVersion = Nothing
     , _version_metadata = Just $ HM.fromList
       [ "node-api-version" A..= ("0.0" :: Text)