LaconicNetwork/cosmos-sdk
7
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 2 Wiki Activity

fix: do not allow unordered txs to have sequence values set (#24581)

Browse Source 
Co-authored-by: Alex | Interchain Labs <alex@interchainlabs.io>
Co-authored-by: Aaron Craelius <aaronc@users.noreply.github.com>
This commit is contained in:
Tyler
2025-04-28 20:55:05 +00:00
committed by GitHub
co-authored by Alex | Interchain Labs Aaron Craelius
parent a158c24b38
commit f9f3bfb066
21 changed files with 255 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files
api/cosmos/tx/v1beta1/tx.pulsar.go
+4
View File
@@ -8561,6 +8561,10 @@ type TxBody struct {
// Note, when set to true, the existing 'timeout_timestamp' value must
// be set and will be used to correspond to a timestamp in which the transaction is deemed
// valid.
//
// When true, the sequence value MUST be 0, and any transaction with unordered=true and a non-zero sequence value will
// be rejected.
// External services that make assumptions about sequence values may need to be updated because of this.
Unordered bool `protobuf:"varint,4,opt,name=unordered,proto3" json:"unordered,omitempty"`
// timeout_timestamp is the block time after which this transaction will not
// be processed by the chain.