[Bug]: failing tx generation for multisig address with gas=auto

[mircea-c]

Summary of Bug

Trying to generate a transaction with --gas auto for a multisig address fails with the following error

Error: rpc error: code = Unknown desc = rpc error: code = Unknown desc = expected *signing.MultiSignatureData, got, *signing.SingleSignatureData With gas wanted: '0' and gas used: '50955' : unknown request

Version

Tested with multiple v0.45.x minor versions

Steps to Reproduce

Generate a transaction using any multisig address and the command flags from the following example:

gaiad tx distribution withdraw-rewards ${VALOPER} --from ${MULTISIG_ADDR} --generate-only --gas auto

[julienrbrt]

Given that v0.45, will not receive any bug fix. Are you able to reproduce with a v0.46+ chain?

[mircea-c]

Can confirm the bug is still present in 0.46.7

regen tx distribution withdraw-rewards regenvaloper1kl83t6gm2y5lgg5c5h3sz87tt5fg3cmyl2sksd --from regen1kl83t6gm2y5lgg5c5h3sz87tt5fg3cmyrddngu --generate-only --gas auto
Error: rpc error: code = Unknown desc = rpc error: code = Unknown desc = expected *signing.MultiSignatureData, got, *signing.SingleSignatureData With gas wanted: '18446744073709551615' and gas used: '60194' : unknown request

build_tags: '"osusergo,netgo,ledger,static_build"'
commit: c08da230dae102c3051b383e17532e20b238fb71
cosmos_sdk_version: v0.46.7
go: go version go1.20.3 linux/amd64
name: regen
server_name: regen
version: 5.1.0

[alexanderbez]

This is coming from DefaultSigVerificationGasConsumer and most likely due to the fact that the Tx is multi-sig-based. Simulations use a dummy Secp256k1 Pubkey singleton to simulate signature verification cost. So using a multi-sig in the tx won't help you much. I would suggest avoiding signing the tx prior to simulation.

Granted, we should look into this more to maybe do this automatically?

[JulianToledano]

hey guys, I think this could have been solved in #18472