etotheipi (OP)
Legendary
 Offline
Activity: 1428
Merit: 1093
Core Armory Developer
|
 |
October 29, 2015, 04:53:17 PM
Last edit: November 11, 2015, 09:29:24 PM by etotheipi |
|
Armory 0.93.3 with BIP62 ReleasedDownload links below, but as always, please use the secure downloader within Armory under "Help"-->"Update Software" or on the Announcements tab on the main screen.
Implemented low S-value signatures to work with Core 0.11+: Armory now implements all components of BIP62 compliance in its signing code. Also includes a correction path to fix non-compliant signatures when broadcasting transactions signed by older versions of Armory. Thus, offline systems do not need to be updated, as long as the online system is. Critical Bug Fix: "bitcoin:" URI handling of Multisig/P2SH addresses: The code that handles clicking on a "bitcoin:" link outside Armory was improperly handling Multisig/P2SH addresses, and would prefill a valid but incorrect address. Transaction confirmation fix: The number of confirmations was not being calculated properly for fee estimation in some contexts. No more support for Mac/OSX:
Due to the high resource consumption of maintaining the Mac builds and lack of continued support from the Qt team for Qt4/PyQt4, we have no choice but to pull OSX support until we can upgrade Armory to Python3 and Qt5. (OSX support re-added)
Armory 0.93.3 for Windows XP, Vista, 7, 8+ (64-bit) Armory 0.93.3 for MacOSX 10.7+ (64bit) Armory 0.93.3 for Ubuntu 12.04+ (32bit) Armory 0.93.3 for Ubuntu 12.04+ (64bit) Armory 0.93.3 for RaspberryPi (armhf) Armory 0.93.3 Offline Bundle for Ubuntu 12.04 exact (32bit) Armory 0.93.3 Offline Bundle for Ubuntu 12.04 exact (64bit) Armory 0.93.3 Offline Bundle for RaspberryPi (armhf) Armory 0.93.3: Signed hashes of all installers
|
|
|
|
|
|
|
|
|
|
|
|
|
"Bitcoin: the cutting edge of begging technology." -- Giraffe.BTC
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
cypherdoc
Legendary
Offline
Activity: 1764
Merit: 1002
|
|
October 29, 2015, 05:16:50 PM |
|
ty
hope you're okay
|
|
|
|
|
|
pf
|
|
October 29, 2015, 06:25:34 PM |
|
No more support for Mac/OSX:
That's pity. This begs the question: Can I copy my existing 56 GB data for Bitcoin Core and 49 GB data for Armory from my Mac to Linux and continue using it seamlessly? Downloading the whole thing again just because I moved to Linux would be very painful for me. |
|
|
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3668
Merit: 1345
Armory Developer
|
|
October 29, 2015, 06:31:51 PM |
|
That's pity. This begs the question:
Can I copy my existing 56 GB data for Bitcoin Core and 49 GB data for Armory from my Mac to Linux and continue using it seamlessly? Downloading the whole thing again just because I moved to Linux would be very painful for me.
You should be able to. |
|
|
|
bitpop
Legendary
Offline
Activity: 2912
Merit: 1060
|
|
October 29, 2015, 11:02:08 PM |
|
Thank you
|
|
|
|
Plento
Jr. Member
Offline
Activity: 129
Merit: 1
|
|
October 30, 2015, 04:25:32 AM |
|
Fan-freaking-tastic.
Thank you!
|
|
|
|
|
|
picobit
|
|
October 30, 2015, 06:53:56 PM |
|
No more support for Mac/OSX:
That's pity. This begs the question: Can I copy my existing 56 GB data for Bitcoin Core and 49 GB data for Armory from my Mac to Linux and continue using it seamlessly? Downloading the whole thing again just because I moved to Linux would be very painful for me. I am trying to do just that. Copied Bitcoin Core's stuff onto a virtual Linux machine on my Mac, and started bitcoin-qt on the virtual machine yesterday evening. It does not redownload the blockchain, but it does reverify it. Has been running for 11 hours so far, judging from the rate it crunches blocks according to the log file, it will finish within 12-24 hours  I am not going to move Armory's stuff over to the VM, instead I plan on letting it rescan the blockchain. It would probably to that anyway, and it did not use to be too slow. I will report back tomorrow. It is disappointing that Mac support has been dropped, but considering how badly Qt is supported on Mac, it is not surprising. Pulling 0.94 is far worse, since that was going to only store one copy of the blockchain (Bitcoin Core's). Having two blockchain on my laptop is no longer viable, within a few month I need to find an alternative. Getting rid of one of them would have postponed that for a year or so. Edit: spelling. |
|
|
|
|
unamis76
Legendary
Offline
Activity: 1512
Merit: 1005
|
|
October 30, 2015, 07:39:01 PM |
|
Thank you! A great update to one of my favorite clients  And this: Also includes a correction path to fix non-compliant signatures when broadcasting transactions signed by older versions of Armory. Thus, offline systems do not need to be updated, as long as the online system is.
Great! No need to remake my offline environment  |
|
|
|
|
|
picobit
|
|
October 30, 2015, 07:41:32 PM |
|
Great! No need to remake my offline environment Yes, that is really a good thing!  |
|
|
|
|
|
jammers
|
|
October 30, 2015, 07:49:42 PM |
|
Cool. I could download it from this post, but when offered it in armory and trying to download it via there, it's just giving me the error
There was a failure downloading this file: 0
|
|
|
|
bitpop
Legendary
Offline
Activity: 2912
Merit: 1060
|
|
October 30, 2015, 09:01:15 PM |
|
Cool. I could download it from this post, but when offered it in armory and trying to download it via there, it's just giving me the error
There was a failure downloading this file: 0
Both worked for me, maybe the server was down temporarily |
|
|
|
|
bitsolutions
|
|
October 31, 2015, 12:45:09 AM
Last edit: October 31, 2015, 07:04:29 AM by bitsolutions |
|
No more support for Mac/OSX:
Due to the high resource consumption of maintaining the Mac builds and lack of continued support from the Qt team for Qt4/PyQt4, we have no choice but to pull OSX support until we can upgrade Armory to Python3 and Qt5.
Are there any changes that would prevent me from compiling it myself for Mac/OSX? Edit: Got it working and pull requested fixes for Qt. PM me if you want the binary I compiled. |
Mining Software Developer.
|
|
|
|
pf
|
|
October 31, 2015, 07:28:02 AM |
|
No more support for Mac/OSX:
Due to the high resource consumption of maintaining the Mac builds and lack of continued support from the Qt team for Qt4/PyQt4, we have no choice but to pull OSX support until we can upgrade Armory to Python3 and Qt5.
Are there any changes that would prevent me from compiling it myself for Mac/OSX? Edit: Got it working and pull requested fixes for Qt. PM me if you want the binary I compiled. Any chance you can write out the steps I can use to compile it myself for OS X? Thanks. |
|
|
|
|
|
bitsolutions
|
|
October 31, 2015, 07:38:24 AM |
|
No more support for Mac/OSX:
Due to the high resource consumption of maintaining the Mac builds and lack of continued support from the Qt team for Qt4/PyQt4, we have no choice but to pull OSX support until we can upgrade Armory to Python3 and Qt5.
Are there any changes that would prevent me from compiling it myself for Mac/OSX? Edit: Got it working and pull requested fixes for Qt. PM me if you want the binary I compiled. Any chance you can write out the steps I can use to compile it myself for OS X? Thanks. Just follow the instructions here with pull request #315. |
Mining Software Developer.
|
|
|
|
pf
|
|
October 31, 2015, 10:59:08 AM |
|
No more support for Mac/OSX:
Due to the high resource consumption of maintaining the Mac builds and lack of continued support from the Qt team for Qt4/PyQt4, we have no choice but to pull OSX support until we can upgrade Armory to Python3 and Qt5.
Are there any changes that would prevent me from compiling it myself for Mac/OSX? Edit: Got it working and pull requested fixes for Qt. PM me if you want the binary I compiled. Any chance you can write out the steps I can use to compile it myself for OS X? Thanks. Just follow the instructions here with pull request #315. Thanks, I'll try. A few questions: - If it's so easy to make the OS X build, why didn't they just do it?
- Have you tested your OS X compiled Armory 0.93.3 with Bitcoin Core 0.11.1? Is everything working? Are transactions getting broadcast, and so on?
- Let's say I upgrade to Bitcoin Core 0.11.1 and run it, and then run the older Armory 0.93.2. Will anything break? Or will Armory tell me something is wrong right away? Or will Armory just fail to broadcast transactions? What exactly could go wrong?
|
|
|
|
|
unamis76
Legendary
Offline
Activity: 1512
Merit: 1005
|
|
October 31, 2015, 03:58:13 PM |
|
No more support for Mac/OSX:
Due to the high resource consumption of maintaining the Mac builds and lack of continued support from the Qt team for Qt4/PyQt4, we have no choice but to pull OSX support until we can upgrade Armory to Python3 and Qt5.
Are there any changes that would prevent me from compiling it myself for Mac/OSX? Edit: Got it working and pull requested fixes for Qt. PM me if you want the binary I compiled. Any chance you can write out the steps I can use to compile it myself for OS X? Thanks. Just follow the instructions here with pull request #315. Thanks, I'll try. A few questions: - If it's so easy to make the OS X build, why didn't they just do it?
- Have you tested your OS X compiled Armory 0.93.3 with Bitcoin Core 0.11.1? Is everything working? Are transactions getting broadcast, and so on?
- Let's say I upgrade to Bitcoin Core 0.11.1 and run it, and then run the older Armory 0.93.2. Will anything break? Or will Armory tell me something is wrong right away? Or will Armory just fail to broadcast transactions? What exactly could go wrong?
From the OP, I can just guess that they cannot provide Armory on OSX with the same quality standards that they provide on Windows and Linux. As for 0.93.2 + Core 0.11.1, I don't see why would there be any issue. |
|
|
|
|
achow101
Staff
Legendary
Offline
Activity: 3388
Merit: 6581
Just writing some code
|
|
October 31, 2015, 04:26:53 PM |
|
As for 0.93.2 + Core 0.11.1, I don't see why would there be any issue.
The issue is that 0.93.2 and older does not enforce using low s signatures. They sometimes produce high s sigs, which are no longer relayed by core 0.11.1. The fix fixes that issue so that armory only produced low s sigs. |
|
|
|
unamis76
Legendary
Offline
Activity: 1512
Merit: 1005
|
|
October 31, 2015, 05:02:57 PM |
|
As for 0.93.2 + Core 0.11.1, I don't see why would there be any issue.
The issue is that 0.93.2 and older does not enforce using low s signatures. They sometimes produce high s sigs, which are no longer relayed by core 0.11.1. The fix fixes that issue so that armory only produced low s sigs. Thank you for the clarification. |
|
|
|
|
PRab
Member
Offline
Activity: 98
Merit: 10
|
|
October 31, 2015, 05:58:07 PM |
|
As always, thanks for the updated version!
|
|
|
|
|
|
bitsolutions
|
|
October 31, 2015, 07:26:04 PM
Last edit: October 31, 2015, 09:18:24 PM by bitsolutions |
|
Thanks, I'll try. A few questions: - If it's so easy to make the OS X build, why didn't they just do it?
- Have you tested your OS X compiled Armory 0.93.3 with Bitcoin Core 0.11.1? Is everything working? Are transactions getting broadcast, and so on?
- Let's say I upgrade to Bitcoin Core 0.11.1 and run it, and then run the older Armory 0.93.2. Will anything break? Or will Armory tell me something is wrong right away? Or will Armory just fail to broadcast transactions? What exactly could go wrong?
Not sure why they didn't just do it, best guess is they were too busy or didn't have a mac available, it took me a few hours to get working but most of that was just getting familiar with the build system, the changes they made didn't really touch the build system as far as I could tell but they hadn't updated Qt in a while so some links/paths were broken. Seems to work fine with Bitcoin Core 0.11.1. Armory 0.93.2 fails to broadcast transactions with Bitcoin Core 0.11.1. |
Mining Software Developer.
|
|
|
|
