You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

446 lines
17 KiB

  1. # Upgrading Tendermint Core
  2. This guide provides steps to be followed when you upgrade your applications to
  3. a newer version of Tendermint Core.
  4. ## v0.32.0
  5. This release is compatible with previous blockchains,
  6. however the new ABCI Events mechanism may create some complexity
  7. for nodes wishing to continue operation with v0.32 from a previous version.
  8. There are some minor breaking changes to the RPC.
  9. ### Config Changes
  10. If you have `db_backend` set to `leveldb` in your config file, please change it
  11. to `goleveldb` or `cleveldb`.
  12. ### RPC Changes
  13. The default listen address for the RPC is now `127.0.0.1`. If you want to expose
  14. it publicly, you have to explicitly configure it. Note exposing the RPC to the
  15. public internet may not be safe - endpoints which return a lot of data may
  16. enable resource exhaustion attacks on your node, causing the process to crash.
  17. Any consumers of `/block_results` need to be mindful of the change in all field
  18. names from CamelCase to Snake case, eg. `results.DeliverTx` is now `results.deliver_tx`.
  19. This is a fix, but it's breaking.
  20. ### ABCI Changes
  21. ABCI responses which previously had a `Tags` field now have an `Events` field
  22. instead. The original `Tags` field was simply a list of key-value pairs, where
  23. each key effectively represented some attribute of an event occuring in the
  24. blockchain, like `sender`, `receiver`, or `amount`. However, it was difficult to
  25. represent the occurence of multiple events (for instance, multiple transfers) in a single list.
  26. The new `Events` field contains a list of `Event`, where each `Event` is itself a list
  27. of key-value pairs, allowing for more natural expression of multiple events in
  28. eg. a single DeliverTx or EndBlock. Note each `Event` also includes a `Type`, which is meant to categorize the
  29. event.
  30. For transaction indexing, the index key is
  31. prefixed with the event type: `{eventType}.{attributeKey}`.
  32. If the same event type and attribute key appear multiple times, the values are
  33. appended in a list.
  34. To make queries, include the event type as a prefix. For instance if you
  35. previously queried for `recipient = 'XYZ'`, and after the upgrade you name your event `transfer`,
  36. the new query would be for `transfer.recipient = 'XYZ'`.
  37. Note that transactions indexed on a node before upgrading to v0.32 will still be indexed
  38. using the old scheme. For instance, if a node upgraded at height 100,
  39. transactions before 100 would be queried with `recipient = 'XYZ'` and
  40. transactions after 100 would be queried with `transfer.recipient = 'XYZ'`.
  41. While this presents additional complexity to clients, it avoids the need to
  42. reindex. Of course, you can reset the node and sync from scratch to re-index
  43. entirely using the new scheme.
  44. We illustrate further with a more complete example.
  45. Prior to the update, suppose your `ResponseDeliverTx` look like:
  46. ```go
  47. abci.ResponseDeliverTx{
  48. Tags: []cmn.KVPair{
  49. {Key: []byte("sender"), Value: []byte("foo")},
  50. {Key: []byte("recipient"), Value: []byte("bar")},
  51. {Key: []byte("amount"), Value: []byte("35")},
  52. }
  53. }
  54. ```
  55. The following queries would match this transaction:
  56. ```go
  57. query.MustParse("tm.event = 'Tx' AND sender = 'foo'")
  58. query.MustParse("tm.event = 'Tx' AND recipient = 'bar'")
  59. query.MustParse("tm.event = 'Tx' AND sender = 'foo' AND recipient = 'bar'")
  60. ```
  61. Following the upgrade, your `ResponseDeliverTx` would look something like:
  62. the following `Events`:
  63. ```go
  64. abci.ResponseDeliverTx{
  65. Events: []abci.Event{
  66. {
  67. Type: "transfer",
  68. Attributes: cmn.KVPairs{
  69. {Key: []byte("sender"), Value: []byte("foo")},
  70. {Key: []byte("recipient"), Value: []byte("bar")},
  71. {Key: []byte("amount"), Value: []byte("35")},
  72. },
  73. }
  74. }
  75. ```
  76. Now the following queries would match this transaction:
  77. ```go
  78. query.MustParse("tm.event = 'Tx' AND transfer.sender = 'foo'")
  79. query.MustParse("tm.event = 'Tx' AND transfer.recipient = 'bar'")
  80. query.MustParse("tm.event = 'Tx' AND transfer.sender = 'foo' AND transfer.recipient = 'bar'")
  81. ```
  82. For further documentation on `Events`, see the [docs](https://github.com/tendermint/tendermint/blob/60827f75623b92eff132dc0eff5b49d2025c591e/docs/spec/abci/abci.md#events).
  83. ### Go Applications
  84. The ABCI Application interface changed slightly so the CheckTx and DeliverTx
  85. methods now take Request structs. The contents of these structs are just the raw
  86. tx bytes, which were previously passed in as the argument.
  87. ## v0.31.6
  88. There are no breaking changes in this release except Go API of p2p and
  89. mempool packages. Hovewer, if you're using cleveldb, you'll need to change
  90. the compilation tag:
  91. Use `cleveldb` tag instead of `gcc` to compile Tendermint with CLevelDB or
  92. use `make build_c` / `make install_c` (full instructions can be found at
  93. https://tendermint.com/docs/introduction/install.html#compile-with-cleveldb-support)
  94. ## v0.31.0
  95. This release contains a breaking change to the behaviour of the pubsub system.
  96. It also contains some minor breaking changes in the Go API and ABCI.
  97. There are no changes to the block or p2p protocols, so v0.31.0 should work fine
  98. with blockchains created from the v0.30 series.
  99. ### RPC
  100. The pubsub no longer blocks on publishing. This may cause some WebSocket (WS) clients to stop working as expected.
  101. If your WS client is not consuming events fast enough, Tendermint can terminate the subscription.
  102. In this case, the WS client will receive an error with description:
  103. ```json
  104. {
  105. "jsonrpc": "2.0",
  106. "id": "{ID}#event",
  107. "error": {
  108. "code": -32000,
  109. "msg": "Server error",
  110. "data": "subscription was cancelled (reason: client is not pulling messages fast enough)" // or "subscription was cancelled (reason: Tendermint exited)"
  111. }
  112. }
  113. Additionally, there are now limits on the number of subscribers and
  114. subscriptions that can be active at once. See the new
  115. `rpc.max_subscription_clients` and `rpc.max_subscriptions_per_client` values to
  116. configure this.
  117. ```
  118. ### Applications
  119. Simple rename of `ConsensusParams.BlockSize` to `ConsensusParams.Block`.
  120. The `ConsensusParams.Block.TimeIotaMS` field was also removed. It's configured
  121. in the ConsensusParsm in genesis.
  122. ### Go API
  123. See the [CHANGELOG](CHANGELOG.md). These are relatively straight forward.
  124. ## v0.30.0
  125. This release contains a breaking change to both the block and p2p protocols,
  126. however it may be compatible with blockchains created with v0.29.0 depending on
  127. the chain history. If your blockchain has not included any pieces of evidence,
  128. or no piece of evidence has been included in more than one block,
  129. and if your application has never returned multiple updates
  130. for the same validator in a single block, then v0.30.0 will work fine with
  131. blockchains created with v0.29.0.
  132. The p2p protocol change is to fix the proposer selection algorithm again.
  133. Note that proposer selection is purely a p2p concern right
  134. now since the algorithm is only relevant during real time consensus.
  135. This change is thus compatible with v0.29.0, but
  136. all nodes must be upgraded to avoid disagreements on the proposer.
  137. ### Applications
  138. Applications must ensure they do not return duplicates in
  139. `ResponseEndBlock.ValidatorUpdates`. A pubkey must only appear once per set of
  140. updates. Duplicates will cause irrecoverable failure. If you have a very good
  141. reason why we shouldn't do this, please open an issue.
  142. ## v0.29.0
  143. This release contains some breaking changes to the block and p2p protocols,
  144. and will not be compatible with any previous versions of the software, primarily
  145. due to changes in how various data structures are hashed.
  146. Any implementations of Tendermint blockchain verification, including lite clients,
  147. will need to be updated. For specific details:
  148. - [Merkle tree](./docs/spec/blockchain/encoding.md#merkle-trees)
  149. - [ConsensusParams](./docs/spec/blockchain/state.md#consensusparams)
  150. There was also a small change to field ordering in the vote struct. Any
  151. implementations of an out-of-process validator (like a Key-Management Server)
  152. will need to be updated. For specific details:
  153. - [Vote](https://github.com/tendermint/tendermint/blob/master/docs/spec/consensus/signing.md#votes)
  154. Finally, the proposer selection algorithm continues to evolve. See the
  155. [work-in-progress
  156. specification](https://github.com/tendermint/tendermint/pull/3140).
  157. For everything else, please see the [CHANGELOG](./CHANGELOG.md#v0.29.0).
  158. ## v0.28.0
  159. This release breaks the format for the `priv_validator.json` file
  160. and the protocol used for the external validator process.
  161. It is compatible with v0.27.0 blockchains (neither the BlockProtocol nor the
  162. P2PProtocol have changed).
  163. Please read carefully for details about upgrading.
  164. **Note:** Backup your `config/priv_validator.json`
  165. before proceeding.
  166. ### `priv_validator.json`
  167. The `config/priv_validator.json` is now two files:
  168. `config/priv_validator_key.json` and `data/priv_validator_state.json`.
  169. The former contains the key material, the later contains the details on the last
  170. message signed.
  171. When running v0.28.0 for the first time, it will back up any pre-existing
  172. `priv_validator.json` file and proceed to split it into the two new files.
  173. Upgrading should happen automatically without problem.
  174. To upgrade manually, use the provided `privValUpgrade.go` script, with exact paths for the old
  175. `priv_validator.json` and the locations for the two new files. It's recomended
  176. to use the default paths, of `config/priv_validator_key.json` and
  177. `data/priv_validator_state.json`, respectively:
  178. ```
  179. go run scripts/privValUpgrade.go <old-path> <new-key-path> <new-state-path>
  180. ```
  181. ### External validator signers
  182. The Unix and TCP implementations of the remote signing validator
  183. have been consolidated into a single implementation.
  184. Thus in both cases, the external process is expected to dial
  185. Tendermint. This is different from how Unix sockets used to work, where
  186. Tendermint dialed the external process.
  187. The `PubKeyMsg` was also split into separate `Request` and `Response` types
  188. for consistency with other messages.
  189. Note that the TCP sockets don't yet use a persistent key,
  190. so while they're encrypted, they can't yet be properly authenticated.
  191. See [#3105](https://github.com/tendermint/tendermint/issues/3105).
  192. Note the Unix socket has neither encryption nor authentication, but will
  193. add a shared-secret in [#3099](https://github.com/tendermint/tendermint/issues/3099).
  194. ## v0.27.0
  195. This release contains some breaking changes to the block and p2p protocols,
  196. but does not change any core data structures, so it should be compatible with
  197. existing blockchains from the v0.26 series that only used Ed25519 validator keys.
  198. Blockchains using Secp256k1 for validators will not be compatible. This is due
  199. to the fact that we now enforce which key types validators can use as a
  200. consensus param. The default is Ed25519, and Secp256k1 must be activated
  201. explicitly.
  202. It is recommended to upgrade all nodes at once to avoid incompatibilities at the
  203. peer layer - namely, the heartbeat consensus message has been removed (only
  204. relevant if `create_empty_blocks=false` or `create_empty_blocks_interval > 0`),
  205. and the proposer selection algorithm has changed. Since proposer information is
  206. never included in the blockchain, this change only affects the peer layer.
  207. ### Go API Changes
  208. #### libs/db
  209. The ReverseIterator API has changed the meaning of `start` and `end`.
  210. Before, iteration was from `start` to `end`, where
  211. `start > end`. Now, iteration is from `end` to `start`, where `start < end`.
  212. The iterator also excludes `end`. This change allows a simplified and more
  213. intuitive logic, aligning the semantic meaning of `start` and `end` in the
  214. `Iterator` and `ReverseIterator`.
  215. ### Applications
  216. This release enforces a new consensus parameter, the
  217. ValidatorParams.PubKeyTypes. Applications must ensure that they only return
  218. validator updates with the allowed PubKeyTypes. If a validator update includes a
  219. pubkey type that is not included in the ConsensusParams.Validator.PubKeyTypes,
  220. block execution will fail and the consensus will halt.
  221. By default, only Ed25519 pubkeys may be used for validators. Enabling
  222. Secp256k1 requires explicit modification of the ConsensusParams.
  223. Please update your application accordingly (ie. restrict validators to only be
  224. able to use Ed25519 keys, or explicitly add additional key types to the genesis
  225. file).
  226. ## v0.26.0
  227. This release contains a lot of changes to core data types and protocols. It is not
  228. compatible to the old versions and there is no straight forward way to update
  229. old data to be compatible with the new version.
  230. To reset the state do:
  231. ```
  232. $ tendermint unsafe_reset_all
  233. ```
  234. Here we summarize some other notable changes to be mindful of.
  235. ### Config Changes
  236. All timeouts must be changed from integers to strings with their duration, for
  237. instance `flush_throttle_timeout = 100` would be changed to
  238. `flush_throttle_timeout = "100ms"` and `timeout_propose = 3000` would be changed
  239. to `timeout_propose = "3s"`.
  240. ### RPC Changes
  241. The default behaviour of `/abci_query` has been changed to not return a proof,
  242. and the name of the parameter that controls this has been changed from `trusted`
  243. to `prove`. To get proofs with your queries, ensure you set `prove=true`.
  244. Various version fields like `amino_version`, `p2p_version`, `consensus_version`,
  245. and `rpc_version` have been removed from the `node_info.other` and are
  246. consolidated under the tendermint semantic version (ie. `node_info.version`) and
  247. the new `block` and `p2p` protocol versions under `node_info.protocol_version`.
  248. ### ABCI Changes
  249. Field numbers were bumped in the `Header` and `ResponseInfo` messages to make
  250. room for new `version` fields. It should be straight forward to recompile the
  251. protobuf file for these changes.
  252. #### Proofs
  253. The `ResponseQuery.Proof` field is now structured as a `[]ProofOp` to support
  254. generalized Merkle tree constructions where the leaves of one Merkle tree are
  255. the root of another. If you don't need this functionality, and you used to
  256. return `<proof bytes>` here, you should instead return a single `ProofOp` with
  257. just the `Data` field set:
  258. ```
  259. []ProofOp{
  260. ProofOp{
  261. Data: <proof bytes>,
  262. }
  263. }
  264. ```
  265. For more information, see:
  266. - [ADR-026](https://github.com/tendermint/tendermint/blob/30519e8361c19f4bf320ef4d26288ebc621ad725/docs/architecture/adr-026-general-merkle-proof.md)
  267. - [Relevant ABCI
  268. documentation](https://github.com/tendermint/tendermint/blob/30519e8361c19f4bf320ef4d26288ebc621ad725/docs/spec/abci/apps.md#query-proofs)
  269. - [Description of
  270. keys](https://github.com/tendermint/tendermint/blob/30519e8361c19f4bf320ef4d26288ebc621ad725/crypto/merkle/proof_key_path.go#L14)
  271. ### Go API Changes
  272. #### crypto/merkle
  273. The `merkle.Hasher` interface was removed. Functions which used to take `Hasher`
  274. now simply take `[]byte`. This means that any objects being Merklized should be
  275. serialized before they are passed in.
  276. #### node
  277. The `node.RunForever` function was removed. Signal handling and running forever
  278. should instead be explicitly configured by the caller. See how we do it
  279. [here](https://github.com/tendermint/tendermint/blob/30519e8361c19f4bf320ef4d26288ebc621ad725/cmd/tendermint/commands/run_node.go#L60).
  280. ### Other
  281. All hashes, except for public key addresses, are now 32-bytes.
  282. ## v0.25.0
  283. This release has minimal impact.
  284. If you use GasWanted in ABCI and want to enforce it, set the MaxGas in the genesis file (default is no max).
  285. ## v0.24.0
  286. New 0.24.0 release contains a lot of changes to the state and types. It's not
  287. compatible to the old versions and there is no straight forward way to update
  288. old data to be compatible with the new version.
  289. To reset the state do:
  290. ```
  291. $ tendermint unsafe_reset_all
  292. ```
  293. Here we summarize some other notable changes to be mindful of.
  294. ### Config changes
  295. `p2p.max_num_peers` was removed in favor of `p2p.max_num_inbound_peers` and
  296. `p2p.max_num_outbound_peers`.
  297. ```
  298. # Maximum number of inbound peers
  299. max_num_inbound_peers = 40
  300. # Maximum number of outbound peers to connect to, excluding persistent peers
  301. max_num_outbound_peers = 10
  302. ```
  303. As you can see, the default ratio of inbound/outbound peers is 4/1. The reason
  304. is we want it to be easier for new nodes to connect to the network. You can
  305. tweak these parameters to alter the network topology.
  306. ### RPC Changes
  307. The result of `/commit` used to contain `header` and `commit` fields at the top level. These are now contained under the `signed_header` field.
  308. ### ABCI Changes
  309. The header has been upgraded and contains new fields, but none of the existing
  310. fields were changed, except their order.
  311. The `Validator` type was split into two, one containing an `Address` and one
  312. containing a `PubKey`. When processing `RequestBeginBlock`, use the `Validator`
  313. type, which contains just the `Address`. When returning `ResponseEndBlock`, use
  314. the `ValidatorUpdate` type, which contains just the `PubKey`.
  315. ### Validator Set Updates
  316. Validator set updates returned in ResponseEndBlock for height `H` used to take
  317. effect immediately at height `H+1`. Now they will be delayed one block, to take
  318. effect at height `H+2`. Note this means that the change will be seen by the ABCI
  319. app in the `RequestBeginBlock.LastCommitInfo` at block `H+3`. Apps were already
  320. required to maintain a map from validator addresses to pubkeys since v0.23 (when
  321. pubkeys were removed from RequestBeginBlock), but now they may need to track
  322. multiple validator sets at once to accomodate this delay.
  323. ### Block Size
  324. The `ConsensusParams.BlockSize.MaxTxs` was removed in favour of
  325. `ConsensusParams.BlockSize.MaxBytes`, which is now enforced. This means blocks
  326. are limitted only by byte-size, not by number of transactions.