Closed wenchaosong closed 1 year ago
This looks more related to how the SSL protection has been setup on the endpoint, not the library itself. Based on this:
WRONG_VERSION_NUMBER
I assume SSL has been set with an old version and should be updated on the gRPC endpoint
ok, but how to set the custom chain id ?
I tried again, success, but the chain id was deadcode in TxSigner.dart file, so you can let it can be configurable
@wenchaosong I'm not understing. Why do you need the chain id while decoding the transaction? It is not used during that process
you are right, no need to set the chain id