Invalid TX signature, but chain-id and account sequence are correct

Archived Tendermint
1

At one point, my test chain with one validator crashed. When restarted, it wouldn’t accept any more transactions.

Here are my bash shortcuts just for reference:

function send() {
    launchpayloadcli tx send cosmos1duqsv0rgf6cg9uk4n3hmxmhr3kxa56au5qrj3y $1 1drop --memo "post-crash test tx" --keyring-backend test --home /home/shinichi/source/work/crashed-drop-c34/nodeconfig/faucet_account --node tcp://$NODE:26657 --chain-id drop-c34efbd55083665002d2 -o json
}

function checksend {
    curl http://$LCD:1317/txs/$1
}

function checkaccount {
	curl http://$LCD:1317/auth/accounts/$1
}

function checknode {
	curl http://$LCD:1317/node_info
}

shinichi@asuka:~ checkaccount cosmos1duqsv0rgf6cg9uk4n3hmxmhr3kxa56au5qrj3y
{"height":"8517","result":{"type":"cosmos-sdk/Account","value":{"address":"cosmos1duqsv0rgf6cg9uk4n3hmxmhr3kxa56au5qrj3y","coins":[{"denom":"drop","amount":"7999981594"},{"denom":"evtx","amount":"5977584791"}],"public_key":{"type":"tendermint/PubKeySecp256k1","value":"A/9O/UiMYLOn+w6fb/gOHwnUq+wpOFqaNiEy0aUhOFx4"},"account_number":"3","sequence":"119"}}}

shinichi@asuka:~ checknode
{"node_info":{"protocol_version":{"p2p":"7","block":"10","app":"0"},"id":"ac30facc07db730401cbcf599d9ba0d20da86ef0","listen_addr":"tcp://0.0.0.0:26656","network":"drop-c34efbd55083665002d2","version":"0.33.7","channels":"4020212223303800","moniker":"alice@apeunit.com node drop-c34efbd55083665002d2-0","other":{"tx_index":"on","rpc_address":"tcp://0.0.0.0:26657"}},"application_version":{"name":"","server_name":"\u003cappd\u003e","client_name":"\u003cappcli\u003e","version":"","commit":"","build_tags":"","go":"go version go1.15.5 linux/amd64"}}

And now when I make a transaction, the account sequence and chain-id are the same as you can see, but it still fails with signature verification.

shinichi@asuka:~ send cosmos13xaeejzdx8q0xevv9pqp790j707ytkgshr953u
{"chain_id":"drop-c34efbd55083665002d2","account_number":"3","sequence":"119","fee":{"amount":[],"gas":"200000"},"msgs":[{"type":"cosmos-sdk/MsgSend","value":{"from_address":"cosmos1duqsv0rgf6cg9uk4n3hmxmhr3kxa56au5qrj3y","to_address":"cosmos13xaeejzdx8q0xevv9pqp790j707ytkgshr953u","amount":[{"denom":"drop","amount":"1"}]}}],"memo":"post-crash test tx"}

confirm transaction before signing and broadcasting [y/N]: y
{"height":"0","txhash":"12D15B4999B7C9FB8DA96842EF7D0DD17AF691AE956700CA7F80B780706CA333","code":4,"raw_log":"unauthorized: signature verification failed; verify correct account sequence and chain-id"}

Any ideas why that might be the case?