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
Here is a bash script that generates and unordered transaction and signs it offline. The signed transaction gets 0 timeout_timestamp field.
To reproduce:
install jq tool
make sure that simd is in the path.
which jq >/dev/null || { echo"jq is required but not installed. Exiting."&&exit 1; }
which simd > /dev/null || { echo"simd not in PATH. Exiting."&&exit 1; }
rm -rf zzz
SIMD="simd --home zzz"$SIMD config set client keyring-backend "test" --skip-validate
$SIMD keys add test --no-backup > /dev/null
address=$($SIMD keys show test -a)$SIMD tx bank send $address$address 123stake --unordered --timeout-timestamp $(date +%s) --chain-id test --generate-only | tee unsigned.json | jq .body.timeout_timestamp
$SIMD tx sign unsigned.json --from $address --offline -a 0 -s 0 --chain-id test| jq .body.timeout_timestamp
Output:
"2025-01-23T21:57:22Z"
"0001-01-01T00:00:00Z"
The first line is the timeout_timestamp field from the unsigned transaction.
The second line is the timeout_timestamp field from the signed transaction.
The reason: cosmos-sdk/x/auth/tx/builder.go, function newBuilderFromDecodedTx
When it creates a new tx builder, it doesn't copy TimestampTimeOut field from the decoded tx:
Is there an existing issue for this?
What happened?
Here is a bash script that generates and unordered transaction and signs it offline. The signed transaction gets
0
timeout_timestamp field.To reproduce:
jq
toolsimd
is in the path.Output:
The first line is the
timeout_timestamp
field from the unsigned transaction.The second line is the
timeout_timestamp
field from the signed transaction.The reason: cosmos-sdk/x/auth/tx/builder.go, function
newBuilderFromDecodedTx
When it creates a new tx builder, it doesn't copy
TimestampTimeOut
field from the decoded tx:cosmos-sdk/x/auth/tx/builder.go
Line 65 in 8493d4f
Patch:
Cosmos SDK Version
0.52.x
How to reproduce?
No response
The text was updated successfully, but these errors were encountered: