Closed Riff451 closed 6 months ago
It turned out that the nodejs wrapper does a JSON.parse:
And I think the reqId
in the output of multiSignRequest
was changed because it's a number too big to be contained in a js Number type. The workaround was to update manually the reqId
of the multiSignRequest
output with the original unchanged reqId
. If the request is already of type string the wrapper doesn't do anything and passes the txn as is to libindy.
Should the wrapper take this issue with large numbers into considerations? Thanks.
Hello, I'm receiving the following error when calling the nodejs wrapper
submitRequest
function:If I try to use the
indy-cli
with the same configurations (DID/Verkey, etc.) I can manually multi-sign the transaction and submit successfully the request to the ledger.In my app, which uses the nodejs wrapper, I've double checked the generated signatures and for the same txn I get the same signatures returned from the indy-cli.
The app code does something like this:
where
request.transaction
is the txn json string already signed with my DID.I don't understand what I'm doing wrong. :)
Here's my current environment:
Thanks in advance for any help.