Currently the methods, such as broadcastTx etc. are hardcoded to use base64 encoding in the rpc package.
|
tx: Base64.encode(assertNotEmpty(params.tx)), |
It would be good to let the encoding to be specified by the caller (defaulting to base64 if none specified). For example, when passing a string directly as the tx param, the base64 is throwing error (obviously). Since the Tendermint itself does not have any restriction on the encoding of Tx params, allowing the user to decide the best encoding would be very helpful.
Currently the methods, such as
broadcastTxetc. are hardcoded to use base64 encoding in the rpc package.iov-core/packages/iov-tendermint-rpc/src/v0-32/requests.ts
Line 52 in 70b6f77
It would be good to let the encoding to be specified by the caller (defaulting to base64 if none specified). For example, when passing a string directly as the tx param, the base64 is throwing error (obviously). Since the Tendermint itself does not have any restriction on the encoding of Tx params, allowing the user to decide the best encoding would be very helpful.