Skip to content

Releases: crypto-org-chain/cronos

v1.4.0-rc5

18 Nov 02:13
1c31276
Compare
Choose a tag to compare
v1.4.0-rc5 Pre-release
Pre-release

v1.4.0-rc5 is a consensus breaking version on top of rc4, it reverts an unexpected change introduced in previous testnet upgrade.

CHANGELOGS

Testnet Upgrade Plan

We need a coordinated upgrade to fix testnet, upgrade plan name: v1.4.0-rc5-testnet.

v1.4.0-rc4

15 Nov 01:54
ce797fa
Compare
Choose a tag to compare
v1.4.0-rc4 Pre-release
Pre-release

v1.4.0-rc4 is a non-consensus-breaking upgrade against v1.4.0-rc3, it fixes a few issues we met during testnet upgrade.

CHANGELOGS

IAVL Async Pruning

This version enables async pruning option in iavl v1, it's to fix the hanging issue of pruning nodes we met during testnet upgrade, if you have disabled iavl pruning temporarily during upgrade, you can change it back now.

Fix versiondb corrupted data

NOTE: it's only needed for node operator who actually met this issue, see #1683

  • Stop node, upgrade binary to v1.3.4.
  • Run cronosd changeset fixdata /path/to/node/data/versiondb, takes a few minutes.
  • Start the node with binary v1.3.4.

v1.3.4

13 Nov 03:11
dd3cea2
Compare
Choose a tag to compare
v1.3.4 Pre-release
Pre-release

Include json-rpc bug fixes, and provides a tool to fix versiondb corrupted data.

CHANGELOGS

Fix versiondb corrupted data

  1. Stop node, upgrade binary to v1.3.4.
  2. Run cronosd changeset fixdata /path/to/node/data/versiondb, takes a few minutes.
  3. Start the node with binary v1.3.4.

v1.4.0-rc3

07 Nov 01:00
9469907
Compare
Choose a tag to compare
v1.4.0-rc3 Pre-release
Pre-release

v1.4.0-rc3 is ready for testnet upgrade.

CHANGELOGS

Testnet Upgrade

Upgrade plan name: v1.4.

VersionDB

v1.4 changed the versiondb config, it's recommended for versiondb enabled nodes to add the new config in app.toml in advance, to make sure it's picked up when upgrade actually happens:

[versiondb]
# Enable defines if the versiondb should be enabled.
enable = true

app.toml Changes

Added

# The maximum gas a query coming over rest/grpc may consume.
# If this is set to zero, the query can consume an unbounded amount of gas.
query-gas-limit = "0"

[versiondb]
# Enable defines if the versiondb should be enabled.
enable = true

[telemetry]

# MetricsSink defines the type of metrics sink to use.
metrics-sink = ""

# StatsdAddr defines the address of a statsd server to send metrics to.
# Only utilized if MetricsSink is set to "statsd" or "dogstatsd".
statsd-addr = ""

# DatadogHostname defines the hostname to use when emitting metrics to
# Datadog. Only utilized if MetricsSink is set to "dogstatsd".
datadog-hostname = ""

[evm]
# BlockExecutor set block executor type, "block-stm" for parallel execution, "sequential" for sequential execution.
block-executor = "block-stm"
# BlockSTMWorkers is the number of workers for block-stm execution, 0 means using all available CPUs.
block-stm-workers = 0
# BlockSTMPreEstimate is the flag to enable pre-estimation for block-stm execution.
block-stm-pre-estimate = false

[streaming]
# New config section for the state streaming feature

Removed

# NOTE: irrelevant to iavl v1
iavl-lazy-loading = true

[grpc-web]
# NOTE: gRPC-Web uses the same address as the API server.
address = "localhost:9091"
enable-unsafe-cors = false

[store]
[streamers]
# NOTE: Both `store` and `streamers` sections are removed, replaced by `streaming` section,
# previously versiondb use the `store.streamers` field to enable, now it has it's own section `versiondb`.

config.toml Changes

Added

# The version of the CometBFT binary that created or
# last modified the config file. Do not modify this.
version = "0.38.13"

# Maximum number of requests that can be sent in a batch
# If the value is set to '0' (zero-value), then no maximum batch size will be
# enforced for a JSON-RPC batch request.
max_request_batch_size = 10

[mempool]
# recheck_timeout is the time the application has during the rechecking process
# to return CheckTx responses, once all requests have been sent. Responses that 
# arrive after the timeout expires are discarded. It only applies to 
# non-local ABCI clients and when recheck is enabled.
#
# The ideal value will strongly depend on the application. It could roughly be estimated as the
# average size of the mempool multiplied by the average time it takes the application to validate one
# transaction. We consider that the ABCI application runs in the same location as the CometBFT binary
# so that the recheck duration is not affected by network delays when making requests and receiving responses.
recheck_timeout = "1s"

Removed

block_sync = true

[mempool]
# NOTE: v1 is removed, default to v0
version = "v1"
ttl-duration = "0s"
ttl-num-blocks = 0

v1.4.0-rc2

24 Oct 02:33
6276793
Compare
Choose a tag to compare
v1.4.0-rc2 Pre-release
Pre-release

v1.4.0-rc2 includes bug fixes and benchmark improvements.

CHANGELOGS

v1.4.0-rc1

15 Oct 03:24
e06f87e
Compare
Choose a tag to compare
v1.4.0-rc1 Pre-release
Pre-release

v1.4.0-rc1 includes many bug fixes.

CHANGELOGS

v1.3.3

15 Oct 03:02
62bd406
Compare
Choose a tag to compare
v1.3.3 Pre-release
Pre-release

1.3.3 is a minor release that add cronos-testground support.

$ docker pull ghcr.io/crypto-org-chain/cronos-testground:1.3.3

CHANGELOGS

v1.3.2

24 Sep 12:23
2c977e6
Compare
Choose a tag to compare
v1.3.2 Pre-release
Pre-release

v1.3.2 fixes two json-rpc issues.

CHANGELOGS

v1.4.0-rc0

18 Sep 01:40
e2b0a65
Compare
Choose a tag to compare
v1.4.0-rc0 Pre-release
Pre-release

v1.4.x is a new major breaking version, the main updates:

  • Implement block-stm parallel transaction execution.
  • Upgrade to cosmos-sdk 0.50.x and enable optimistic execution.
  • Upgrade to ibc-go 8.5.x and support unordered ica channel.
  • Implemented cluster benchmarking infrastructure.

CHANGELOGS

Upgrade Plan

It takes a coordinated upgrade from 1.3 to 1.4, the upgrade plan name should be v1.4.

v1.3.1

29 Jul 02:13
3624740
Compare
Choose a tag to compare
v1.3.1 Pre-release
Pre-release

v1.3.1 upgrade rocksdb dependency and tune rocksdb options to reduce ram usage.

For versiondb nodes, please use graceful shutdown to terminate the node before upgrade, otherwise, you need to manually ldb compact --db=... before start up with new binary.