Bitcoin Forum

Bitcoin => Armory => Topic started by: Silveravin on November 10, 2015, 08:21:20 PM



Title: Error message while trying to send BTC. How can I fix quickly?
Post by: Silveravin on November 10, 2015, 08:21:20 PM
I have a 93.2 and 11.1. I have re-scanned and increased fee but nothing has worked. Every time I get the error message. I have contacted Armory support but no response. I know my coins are safe but I have to make a payment within 24 hours. What can I do other than try to rebuild my whole database which I just did because it's a new computer.


Title: Re: Error message while trying to send BTC. How can I fix quickly?
Post by: achow101 on November 10, 2015, 08:26:28 PM
Upgrade to Armory 0.93.3, it should fix the problem. Armory 0.93.2 is not compatible with Bitcoin Core 0.11.1 since it can generate High S signatures in transactions, which are now considered non-standard as of Core 0.11.1 and will be rejected by Core 0.11.1.


Title: Re: Error message while trying to send BTC. How can I fix quickly?
Post by: Silveravin on November 11, 2015, 01:00:20 AM
Upgrade to Armory 0.93.3, it should fix the problem. Armory 0.93.2 is not compatible with Bitcoin Core 0.11.1 since it can generate High S signatures in transactions, which are now considered non-standard as of Core 0.11.1 and will be rejected by Core 0.11.1.


Thanks so much bro. 93.3 isn't available for OSX so I downgraded my core to 11.0 and it worked like a charm.


Title: Re: Error message while trying to send BTC. How can I fix quickly?
Post by: achow101 on November 11, 2015, 02:43:49 AM
Upgrade to Armory 0.93.3, it should fix the problem. Armory 0.93.2 is not compatible with Bitcoin Core 0.11.1 since it can generate High S signatures in transactions, which are now considered non-standard as of Core 0.11.1 and will be rejected by Core 0.11.1.


Thanks so much bro. 93.3 isn't available for OSX so I downgraded my core to 11.0 and it worked like a charm.
Someone made an OSX build here: https://bitcointalk.org/index.php?topic=1229596.msg12866810#msg12866810, but since it isn't the official one and you can't check that it actually used the real source code, it may not be safe. It probably is safe, but a warning that it could be backdoored (likely isn't though).