Skip to content

fix: use a valid 20-byte signer in the gasless module-sender test #331

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
0xNilesh merged 1 commit into from
Aug 26, 2026
Merged

fix: use a valid 20-byte signer in the gasless module-sender test #331

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion test/integration/uexecutor/gasless_module_sender_test.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -120,8 +120,13 @@ func TestGaslessExecutePayloadWithModuleSender(t *testing.T) {

// The gasless message itself: signer is a relayer, the EVM caller is the
// uexecutor module. This must still succeed after the x/vm change.
// testSigner (execute_payload_test.go) is a valid 20-byte account. The
// literal this test originally carried decoded to 42 bytes, which
// F-2026-18200's signer-length guard rejects in GetAddressPair before
// ExecutePayload does any work - so the test failed on an address that was
// never the thing under test.
_, err = ms.ExecutePayload(ctx, &uexecutortypes.MsgExecutePayload{
Signer: "cosmos1xpurwdecvsenyvpkxvmnge3cv93nyd34xuersef38pjnxen9xfsk2dnz8yek2drrv56qmn2ak9",
Signer: testSigner,
UniversalAccountId: universalAccount,
UniversalPayload: payload,
VerificationData: "0x91987784d56359fa91c3e3e0332f4f0cffedf9c081eb12874a63b41d5b5e5c660dc827947c2ae26e658d0551ad4b2d2aa073d62691429a0ae239d2cc58055bf11c",
Expand Down
Loading