sending funds from Cosmos testnet to Namada's MASP isn't working as expected

[McDaan]

Every time I try to do this, I got this at Hermes logs:

2023-12-18T21:21:06.972836Z ERROR ThreadId(10) worker.batch{chain=public-testnet-15.0dacadb8d663}:supervisor.handle_batch{chain=public-testnet-15.0dacadb8d663}:supervisor.process_batch{chain=public-testnet-15.0dacadb8d663}:worker.packet.cmd{src_chain=public-testnet-15.0dacadb8d663 src_port=transfer src_channel=channel-0 dst_chain=theta-testnet-001}:relay{odata=0a880e3f ->Destination @0-1899; len=1}:send_messages_and_wait_check_tx{chain=theta-testnet-001 tracking_id=0a880e3f}:send_tx_with_account_sequence_retry{chain=theta-testnet-001 account.sequence=2140}:estimate_gas: failed to simulate tx. propagating error to caller: gRPC call `send_tx_simulate` failed with status: status: Unknown, message: "failed to execute message; message index: 1: acknowledge packet verification failed: failed packet acknowledgement verification for client (07-tendermint-2649): chained membership proof contains nonexistence proof at index 0. If this is unexpected, please ensure that proof was queried from a height that contained the value in store and was queried with the correct key. The key used: /ibc/acks%2Fports%2Ftransfer%2Fchannels%2Fchannel-0%2Fsequences%2F6: invalid proof [cosmos/ibc-go/[email protected]/modules/core/23-commitment/types/merkle.go:255] With gas wanted: '0' and gas used: '427211' ", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "19396293"} 

While trying to dig into incoming transactions to Namada, I found that only transactions involving client updates are able to be fetched:

namadac tx-result --tx-hash ACD19136EB018D53287DC14FF4AA7CA2FDC49FA88DD117F6D03AEED24BF3E59B
Transaction was applied with result: {
  "info": "Transaction is valid. Gas used: 2270; Changed keys: #tnam1qcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqvtr7x4/clients/07-tendermint-24/clientState, #tnam1qcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqvtr7x4/clients/07-tendermint-24/consensusStates/0-19396280, #tnam1qcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqvtr7x4/clients/07-tendermint-24/update_height, #tnam1qcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqvtr7x4/clients/07-tendermint-24/update_timestamp; VPs result:  Accepted: tnam1qcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqvtr7x4;",
  "log": "",
  "height": "1892",
  "hash": "ACD19136EB018D53287DC14FF4AA7CA2FDC49FA88DD117F6D03AEED24BF3E59B",
  "code": "0",
  "gas_used": "2270",
  "initialized_accounts": []
}

And others:

namadac tx-result --tx-hash 4A3C98BF786823A1F63FE5752BE646A95828BC0FF2A802209A48E53B0477280F
The application panicked (crashed).
Message:  no entry found for key
Location: /.../namada/sdk/src/rpc.rs:657

[McDaan]

We can close this since this PR solved it.
#2311

[sug0]

reopening until the pr is merged