Open ashishkhuraishy opened 1 year ago
Hey,
This could be due to the fact that your chain has different SignedExtra
defined. This might require a different kind of SignatureOptions
that use something else instead of the normal Tip
that we provide.
Please refer to the example provided here - https://github.com/centrifuge/go-substrate-rpc-client/blob/master/registry/retriever/extrinsic_retriever_live_test.go#L42, and check whether you need the non-default option found there.
You can then adjust the SignatureOptions
on your end and try to submit an extrinsic using that.
I have created an example pallet from the tutorials and i want to interact with that pallet programatically.
using the package i am able to create the call and invoke the submitExtrinsic
The output of the code is throwing an error in the last stage which is not giving out much info on why its happening
but when i used the hex encoded values on the frontend template and invoked
submitExtrinsic
i got (when i used the ext hex value pre-signing)(when using the ext hex value after signing)
the error seems to suggest bad signature and i followed everything from the
*_test.go
files. Any help would be appreciated