You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This patch release fixes [GHSA-x5vx-95h7-rv4p](https://github.com/cosmos/cosmos-sdk/security/advisories/GHSA-x5vx-95h7-rv4p).
8
-
It resolves a `x/group` module issue that can halt chain when handling a malicious proposal.
9
-
Only users of the `x/group` module are affected by this issue.
7
+
Announcing Cosmos SDK v0.53
10
8
11
-
We recommended to upgrade to this patch release as soon as possible.
12
-
When upgrading from <= v0.50.11, please use a chain upgrade to ensure that 2/3 of the validator power upgrade to v0.50.12.
9
+
We are pleased to announce the release of Cosmos SDK v0.53! We’re excited to be delivering a new version of the Cosmos SDK that provides key features and updates while minimizing breaking changes so you can focus on what matters most: building.
10
+
11
+
Upgrading to this verison of the Cosmos SDK from any `v0.50.x` release will **require a coordinated chain upgrade**.
12
+
13
+
For more upgrade information, check out our [upgrading guide](https://github.com/cosmos/cosmos-sdk/blob/v0.53.0/UPGRADING.md)
13
14
14
15
## 📝 Changelog
15
16
16
-
Check out the [changelog](https://github.com/cosmos/cosmos-sdk/blob/v0.50.12/CHANGELOG.md) for an exhaustive list of changes, or [compare changes](https://github.com/cosmos/cosmos-sdk/compare/v0.50.11...v0.50.12) from the last release.
17
+
Check out the [changelog](https://github.com/cosmos/cosmos-sdk/blob/v0.53.0/CHANGELOG.md) for an exhaustive list of changes, or [compare changes](https://github.com/cosmos/cosmos-sdk/compare/v0.50.12...v0.53.0) from the last release.
Copy file name to clipboardExpand all lines: UPGRADING.md
+40-24Lines changed: 40 additions & 24 deletions
Original file line number
Diff line number
Diff line change
@@ -25,42 +25,58 @@ To submit an unordered transaction, clients must set the `unordered` flag to
25
25
used as a TTL for the transaction and provides replay protection. Each transaction's `timeout_timestamp` must be
26
26
unique to the account; however, the difference may be as small as a nanosecond. See [ADR-070](https://github.com/cosmos/cosmos-sdk/blob/main/docs/architecture/adr-070-unordered-transactions.md) for more details.
27
27
28
+
Note that unordered transactions require sequence values to be zero, and will **FAIL** if a non-zero sequence value is set.
29
+
Please ensure no sequence value is set when submitting an unordered transaction.
30
+
Services that rely on prior assumptions about sequence values should be updated to handle unordered transactions.
31
+
Services should be aware that when the transaction is unordered, the transaction sequence will always be zero.
32
+
28
33
#### Enabling Unordered Transactions
29
34
30
-
To enable unordered transactions, set the new `UnorderedNonceManager` field in the `x/auth``ante.HandlerOptions`.
35
+
To enable unordered transactions, supply the `WithUnorderedTransactions` option to the `x/auth` keeper:
0 commit comments