unexpected error during channel creation

[McDaan]

Version built: v1.10.4-namada-beta17-rc2

Saw a bunch of errors like this one:

2024-10-07T13:48:47.713769Z  WARN ThreadId(26) send_tx: gas estimation failed, using the default gas limit. Error: Querying error: No response given in the query: Info log: RPC error: Error while processing transaction's fees: Failed masp fee payment, error code: 1 id=housefire-reduce.e51ecf4264fc3
2024-10-07T13:48:47.717780Z ERROR ThreadId(01) failed ConnOpenTry ConnectionSide { chain: BaseChainHandle { chain_id: osmosis-1 }, client_id: 07-tendermint-3287, connection_id: None }: failed during a transaction submission step to chain 'housefire-reduce.e51ecf4264fc3': Namada error: Namada error: Encountered error while broadcasting transaction: server error: {"codespace":"","code":8,"data":"","log":"{INVALID_MSG}: Wrapper transaction exceeds its gas limit","hash":"6A85444CAC64E4D28341B754BA1699A752C8BE393C7C0E78157664E628C517DC"}

And then it ends like this:

ERROR ThreadId(01) failed to open connection after 11 retries
ERROR error after maximum retry of 11 and total delay of 60s: failed to finish connection handshake for Connection { delay_period: 0ns, a_side: ConnectionSide { chain: BaseChainHandle { chain_id: ChainId { id: "housefire-reduce.e51ecf4264fc3", version: 0 }, runtime_sender: Sender { .. } }, client_id: ClientId("07-tendermint-3"), connection_id: Some(ConnectionId("connection-2")) }, b_side: ConnectionSide { chain: BaseChainHandle { chain_id: ChainId { id: "osmosis-1", version: 1 }, runtime_sender: Sender { .. } }, client_id: ClientId("07-tendermint-3287"), connection_id: None } }: failed during a transaction submission step to chain 'housefire-reduce.e51ecf4264fc3': Namada error: Namada error: Encountered error while broadcasting transaction: server error: {"codespace":"","code":8,"data":"","log":"{INVALID_MSG}: Wrapper transaction exceeds its gas limit","hash":"6A85444CAC64E4D28341B754BA1699A752C8BE393C7C0E78157664E628C517DC"}

Tried to raise gas prices from 0.001 to 1, then from 1 to even 1000, to test it out, and the same result. I wonder if this is due a new param that's supposed to be added in the Hermes config? As masp fee payment error seems to be odd.