non-mandatory-script-verify-flag when trying to send transaction

[superphil0]

Hey when I am trying to send a transaction from a recovered wallet I get the response from an online tool:
non-mandatory-script-verify-flag (Operation not valid with the current stack size) (code 64)

Can you tell me what I am doing wrong?

[glowang]

What do you mean by "recovered wallet"? It sounds to me that you have already successfully recovered your funds out of the wallet using the WRW?

@superphil0 could you be more specific about 0) which version of WRW were you using 1) what feature of the WRW were you using 2) What type of bitgo wallet were you using (cold/hot user key? cold/hot backup?) 3) What does the stack trace look like in the developer console/netowork?

[superphil0]

0. We tried both BitGoWalletRecoveryWizard.Setup.2.6.5.exe and BitGoWalletRecoveryWizard.Setup.2.5.4.exe
1. When you start the BitGo Wallet Recovery Wizzard: Non-BitGo-Recoveries -> Non-BitGo-Recoveries. Then the options were: Wallet Type = Bitcoin. Environment = Mainnet. Bitcoin Recovery Service = Bitcoin KRS. The other Info is directly from the BitGo Recovery Keycard.
2. I guess hot-wallet. The Recovery Keycard I got when I created the BitGo account back in 2018.
3. Not completely clear what you mean.

As a result from the bitgo wallet recovery I receive a file with a raw transaction which needs to be broadcasted. Until this step there are no errors. However when I try to broadcast the transaction via tools like https://www.blockchain.com/btc/pushtx
or https://live.blockcypher.com/btc/pushtx/

on blockcypher I get the error: Error validating transaction: Rejected script for input 0 referencing xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ( = redacted) at 1..

on blockchain.com I get> Code: -26, Error: non-mandatory-script-verify-flag (Operation not valid with the current stack size)

After some google I found that this indicated an error in the transaction script, but not sure about this. If you want we can also take this to email/call so you can debug easier

[Number16BusShelter]

Today I've tried to restore access to the Bitgo wallet using KeyCard. Raw transaction was created successfully, but when I tried to broadcast it I saw the same error @superphil0 describes: Code: -26, Error: non-mandatory-script-verify-flag
I've tried multiple services, but it didn't help.

I used data from multiple KeyCards and the result was -26 for every generated transaction.

Please, consider resolving the issue, I'm facing troubles transferring funds from account.

If there's any way to bypass this issue let us know in the thread.

[glowang]

Sorry that this hasn't worked for you, we are looking into the issue now.

Just a few more clarifying questions to make sure we are really on the same page:

1. for the box A and box B of your keycard, do they contain xpubs or do they contain a JSON (encrypted prv)? PLEASE do not share with me the actual data itself.
   An example of the JSON:
   {"iv": "asdfasdfadfasdfafasdfa", "v": 0, ... }
2. If you have xpubs for both Box A and Box B of these fields, you must have a cold wallet. Then what did you use to sign the transaction locally? Or were the transactions signed in the WRW itself?

@superphil0 @Number16BusShelter

[Number16BusShelter]

For the Box A I have JSON string. And for B and C its xpub.

The password seems to be correct, as using another one causes error of invalid password.

I was also a little confused with this keys and if what I have is enough for creating signed transaction. But thinking logically about it I should've got some signature error, which I did not.

I'm not completely sure about how this should work and if I have to sign the transaction by myself or if it's done by the wizard. Need some more guidance here and maybe a better documentation on this topic.

[glowang]

@Number16BusShelter I suspect you are missing a signature. Do you have a transaction hex? I can verify for you.

You need at least two out of the three signatures to send the transaction. Your Box A is a Json, which is an encrypted private key that will be decrypted with your password. The private key from Box A will contribute one signature. However, you need one more signature. Since you are doing the transaction without BitGo, you need the private key corresponding to Box B (your backup key) to sign the transaction too.

Are you the backup key holder? if so you need to sign using your backup prv.

[Number16BusShelter]

Here's my transaction hash

0100000000010307bc78c2b687483ca9fae61f8ee25b91b0048eb1422dfab55567339f91aa77f0000000002322002063c8079c46aa2671ce7b86c43b9e8c266567dba2478567f874e2d7879cb2b8dcffffffffdd92f3586ac39e774859786383d8891ff9b2b026b2e118bfe1bf5e8b46d8ac510000000023220020adf9dc555d20373ff907ce943534e386a587536d9a486ed98af479eb7b6f7021ffffffff0056ce70a47d3294f0ea87c068c3d9309ae787f8fab0681846567f79d8729deb0100000023220020d1ac5e2895fe5c93e1e80ab8b5a0ff9a3c647805bae76d837ca22a9f7cb800d4ffffffff010892aa000000000017a914306e926c1fff4d06df20bb8ee47b9908263bc94887030047304402206d75ac0747f826b19e031b791bc5d975b716d041956b96c1cc9704d1649a1ef502204aa7a907632850fa118bace656b85c4e15fe3ca54cea2d9ccd84ff4f994cd75d0169522102bb811cd2bc029206b9b93538538b45d82a76989873ba439b6e5f30de594144ed21026efc6e71e7ce3bdef1dfed87d3085e3c3db7b0670d5a7784391c85dec72d71d121025bef17974cdcb2c1e94536d4901a916a3c9145b9eda240765f816f2efac9a4fc53ae03004730440220412b0d999a1f05437fcfacdf11633718cfc13a166e7bd384679f064cee678ac702203e426dda19b4ed91f45a77d4162bc52ffe4e7912dee13f81b3f2add6a094677501695221035b55c38a5d09c24d5c5ea42b8713a841ad571678f368a2cd15a70d6df046e58721039c46ca66b36af155461446fcd13ef97da6cc573317067470ec3ae4942323511f210225f717c2b5df90dd7270b0c4cf2ecadc2e216222b28ff928fa27542a53cd86b753ae0300483045022100f975299be19ea2a3ae279b24e0f56f5307d77e1f6d05177562f3b5204e0128d2022057a87510c7a1f831e772aa6df174433ad243318395e90bec42d0fa7a485bfdb8016952210234f1d7c83dd5cd939cba4f7ff5d8f33efcdd9dae4241645394068561e8f949b121036abe6bf686cd82248b52244c50d2cec186285351d0cf4293903a977bb6af4c852103778c9f40599716bcb92d7afbb7911c7f7e94ab96c9f5f749ea853736323f5c9053ae00000000

Ok, so what should I do if BitGo support closes my tickets on request to restore access to my account? On password charge I'm getting service error. Support team just does not respond on my requests and now I can't restore my funds, even with KeyCard! How can you support me in this situation?

Maybe there are some other ways I can create and sign the transaction? Has Box D anything to do with that?

[mrafshin]

I have the same issue
please help

I have a Tron wallet with bitgo key recovery service and a bitcoin wallet with coin cover recovery service
In both cases, I've got the same error when pushing transaction
this is the error:
https://live.blockcypher.com/btc/pushtx/

Error validating transaction: Rejected script for input 0 referencing a1317256423c699fd3c6c6c9ff43b72af36426fbe016e4c827c7780929d23a3b at 21..

[Gfayuo]

Dear BitGo team, please answer as soon as possible. I came across with the same problem!! I cannot log in to my account, you cannot send e-mail with the password recovery form. Moreover, when I tried to use my Keycard I got an error Code: -26, Error: non-mandatory-script-verify-flag
Please help as soon as possible

[Number16BusShelter]

This thread is active for 24 days, and last update from team member was nearly 2 weeks ago.
Is this issue under any investigation? Are there any updates?

@glowang please response.

If it is a problem of a higher level let head quoter be informed.

[glowang]

Thank you guys for the attention on this issue, we are aware of this and are actively working on resolving it. We appreciate your patience!

For further update and communication, could you please reach out to our support team at support@bitgo.com? They are our dedicated team to help you guys out.

[Gfayuo]

Dear Bitgo team and @glowang,
Your support team at support@bitgo.com do not answer any replies. I'm waiting for your reply for more than a month

[ejym]

Hi @Gfayuo.

Thank you for your patience as we look into this issue! We apologize for the delayed response. At this point in time, our teams are still actively working to resolve this issue for users; however, our client services team is happy to escalate your support case with our technical teams.

Unfortunately, due to the nature of GitHub, I am unable to see your registered name and email address to track the previous ticket that was opened. If you feel comfortable listing your contact information here, I am happy to find and escalate this ticket; however, I recommend you send a new email to support@bitgo.com for security/privacy reasons.

We understand the frustration that you've been facing, and appreciate your patience as our teams collaborate to provide a solution for our users. In the meantime, please do not hesitate to reach out with any further account requests/questions to support@bitgo.com.

Thank you!

[yvettep321]

_thank you _

[mrafshin]

still no reply from support@bitgo.com
omg please help i have to transfer my funds