Signing transactions usually requires a privateKey.
However, using the wrong privateKey
and or the wrong signatureId
(KMS) can cause the following error message:
{ "statusCode":403, "errorCode":"ltc.blockchain.broadcast.error", "message":"Unable to broadcast transaction.", "cause": "mandatory-script-verify-flag-failed (Operation not valid with the current stack size)" }
Good to know
- When KMS is involved, BTC-based chains require using a key-based signature id.
- Mnemonic-based signature id is currently under development.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article