EMERGENCY please help for Multibit wallet transaction

[gondel]

Hello all,
I am using using old multibit wallet version 05.14 and want to send a transaction from there. When I try to do it, it is showing seen by 1 peer and is not confirmed.
Then the transacion bounced back saying in blockchain: Transaction rejected by our node. Reason: Non-canonical signature: High S Value
PLEASE HELP! Do you guys know what is the exact reason and what can I do?
I tried downloading the latest wallet, but it is not showing the amount I have.
Any Idea?

Thanks!!!!
Regards,

Gondel

[unamis76]

There's a MultiBit section on the forums.

Transaction with high S value aren't accepted. You have to wait until the transaction is forgotten by the network, and then you can send funds again.

Not sure if you can replace that transaction via CPFP...

[achow101]

You have to keep using Multibit Classic. Multibit HD will not work since you are currently using Multibit classic. Try sending again, hopefully you will not run into that error since the S values are random. Try enough times and eventually you will get a Low S. You should also upgrade to Multibit HD, see instructions here: https://multibit.org/help/hd0.3/how-to-upgrade-from-classic.html

About that error. In the signatures, there is an integer called 'S'. The S can be two different values and still be a valid signature. The Bitcoin protocol made High S values non standard. Since S is random, eventually you will get one with a Low S value.

[Wind_FURY]

You have to keep using Multibit Classic. Multibit HD will not work since you are currently using Multibit classic. Try sending again, hopefully you will not run into that error since the S values are random. Try enough times and eventually you will get a Low S. You should also upgrade to Multibit HD, see instructions here: https://multibit.org/help/hd0.3/how-to-upgrade-from-classic.html

About that error. In the signatures, there is an integer called 'S'. The S can be two different values and still be a valid signature. The Bitcoin protocol made High S values non standard. Since S is random, eventually you will get one with a Low S value.

One of my wallets is still Multibit Classic. Is the "high S error" happening specifically found only in the classic wallet? I have version 0.5.19 that was released on 9/9/2015 if that is of any significance.

[achow101]

You have to keep using Multibit Classic. Multibit HD will not work since you are currently using Multibit classic. Try sending again, hopefully you will not run into that error since the S values are random. Try enough times and eventually you will get a Low S. You should also upgrade to Multibit HD, see instructions here: https://multibit.org/help/hd0.3/how-to-upgrade-from-classic.html

About that error. In the signatures, there is an integer called 'S'. The S can be two different values and still be a valid signature. The Bitcoin protocol made High S values non standard. Since S is random, eventually you will get one with a Low S value.

One of my wallets is still Multibit Classic. Is the "high S error" happening specifically found only in the classic wallet? I have version 0.5.19 that was released on 9/9/2015 if that is of any significance.

AFAIK, Multibit classic never fixed that issue because it was discontinued before Low S enforcement became widely used.

[gondel]

Thank you guys, the transaction just went thru after sometime, I do not know if it is safe to use this wallet anymore...

[smho_16]

Thank you guys, the transaction just went thru after sometime, I do not know if it is safe to use this wallet anymore...

Why gamble, make sure you install Multibit HD, send all your funds from your Multibit Classic to your new wallet. Read about some documentation on how Multibit HD works as it works a lot differently from the Multibit Classic and is also much more secure because its base with BIP32 encryption and it has a seed with which you can recover it from any other PC if such thing is needed.

[Wind_FURY]

Just to update the information and the discussion in this thread. Here is a quoted statement about Multibit Classic and the canonical S value problem.

Just upgrade to the newest release of MultiBit Classic: https://multibit.org/release-info/classic/v0.5.19.html

This was fixed already in 0.5.17 as 0.5.17 upgraded to bitcoinj 0.11.1 and 0.11 included "Generated signatures now use canonical S values."

So to kake everything clear and to inform everyone, Multibit Classic is still very much ok to use. All you have to do is upgrade to the latest version and you will have no problems.