Armory 0.93.3 with BIP62 compliance

[goatpig]

With respect for chain of command, it's been quite a few days now.... Mac users everywhere would be very much appreciated if there was at least one last officially compiled binary update to take care of the high/low-S patch

...Please consider elevating the priority of this request...

No. I will not escalate anything because even though I reviewed the code, I do not build on Macs thus I cannot test the code at all. My review was merely to make sure nothing was fishy with the change.

I informed etotheipi of my opinion on the content of this PR, but I won't press that matter any further because I do not have experience with OSX builds, so I cannot make an informed decision. If I could say "I tested it, it works and I approve of this change", things would be different, but I can't. Development is a lot simpler when people stick to their specialty.

[armedmilitia]

Heya there everyone,
I'm wondering what the system requirements for armory are, both for offline and online? I remember the online version being very resource intensive a while back, but have there been improvements?

Thanks guys!

[philipma1957]

Heya there everyone,
I'm wondering what the system requirements for armory are, both for offline and online? I remember the online version being very resource intensive a while back, but have there been improvements?

Thanks guys!

I would like to know how does this work on windows 10?

[bitsolutions]

Looks like my pull request was merged, hopefully there will be an official release soon.

[etotheipi]

Yes, I just pulled the changes and successfully built 0.93.3 for OSX.

It's now available via secure-downloader, and the link copied here:

Armory 0.93.3 for MacOSX 10.7+ (64bit)

[coinbtm]

Yes, I just pulled the changes and successfully built 0.93.3 for OSX.

It's now available via secure-downloader, and the link copied here:

Armory 0.93.3 for MacOSX 10.7+ (64bit)

Thank you very much as always alan, you are a true gentleman and a scholar!

[Carlton Banks]

Heya there everyone,
I'm wondering what the system requirements for armory are, both for offline and online? I remember the online version being very resource intensive a while back, but have there been improvements?

Thanks guys!

Can't give you official figures from the Armory devs, but my own recommendations for the pre-built 0.93.3 would be....

Online:
2GB RAM minimum
Any Intel/x86 CPU from the past 5-7 years will be good enough, but older/slower means more time sync'ing up to set up the databases.
100GB spare HDD space. High performance/solid state disk recommended.

Offline:
512 MB RAM minimum
Any Intel/x86 CPU from the past 10 years will do it. Almost doesn't matter how underpowered the CPU is, an Atom/Eeee PC could probably deal with it.
Negligible diskspace (a few dozen MB for the installation)


OS wise, I think you're still OK with something as outdated as Windows XP (can anyone confirm this? goatpig?), but I can't help you with the newer Windows versions. I think people have had it working with Windows 8.

For Linux, you need anything with dpkg packaging (Ubuntu, Debian etc), and anything that uses Debian 8 as a base (Ubuntu 15.04+) .

[goatpig]

OS wise, I think you're still OK with something as outdated as Windows XP (can anyone confirm this? goatpig?)

For 0.92.x you can use WinXP.

For 0.93+ you need at least Vista x64.

[Carlton Banks]

OS wise, I think you're still OK with something as outdated as Windows XP (can anyone confirm this? goatpig?)

For 0.92.x you can use WinXP.

For 0.93+ you need at least Vista x64.

0.93.3 corrects any High-S sigs generated offline, no? I'm thinking of the Atom/Netbook owners, Offline Armory could be a great way to re-purpose those devices now. IIRC, 0.92.3 uses the same format for offline transactions...

[goatpig]

0.93.3 corrects any High-S sigs generated offline, no? I'm thinking of the Atom/Netbook owners, Offline Armory could be a great way to re-purpose those devices now. IIRC, 0.92.3 uses the same format for offline transactions...

Yes but 0.93.3 online will fix highS in sigs at broadcast too, so you can sign with an older version as long as you broadcast with 0.93.3

[twebit]

Anybody having problems with connecting to the new Armory? I use custom startup options in the shortcut like this --satoshi-datadir="D:\Bitcoin" --datadir="D:\armoryW" but it won't connect with bitcoin core running and windows 10 firewall allowing connections. Settings in armory are unchecked for "Let armory run Bitcoin/QT in the background"

I can usually get this to work but I'm at a loss here.
edit: I tried the checkmark Let armory run Bitcoin/QT in the background too and specified the directories.
Thanks

[goatpig]

Look at the end of armorylog.txt, should have some clue.

[twebit]

Look at the end of armorylog.txt, should have some clue.

Looked and it says "2015-11-14 13:41 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss"

I've also tried copying all data to my OS's default data directories and checking let armory start bitcoind/qt but it doesn't start bitcoind/qt
Everything works when loading linux mint from live cd with the same parameters so I'm assuming something to do with win10.

Any other tips?
Thanks

[goatpig]

I would need more than just the last line. Either give me more here or post your log file in a support ticket.

[twebit]

I would need more than just the last line. Either give me more here or post your log file in a support ticket.

2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1076 - C++ block utilities loaded successfully
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1186 -
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1187 -
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1188 -
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1189 - ************************************************************
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1190 - Invoked: C:\Program Files\Armory\ArmoryQt.exe --satoshi-datadir=F:\Bitcoin --datadir=D:\armoryW
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1191 - ************************************************************
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1192 - Loading Armory Engine:
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1193 -    Armory Version        : 0.93.3
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1194 -    Armory Build:         : e59e10d38c
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1195 -    PyBtcWallet  Version  : 1.35
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1196 - Detected Operating system: Windows
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1197 -    OS Variant            : 8-6.2.9200--Multiprocessor Free
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1198 -    User home-directory   : C:\Users\twebit\AppData\Roaming
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1199 -    Satoshi BTC directory : F:\Bitcoin
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1200 -    Armory home dir       : D:\armoryW
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1201 - Detected System Specs    :
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1202 -    Total Available RAM   : 15.98 GB
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1203 -    CPU ID string         : Intel64 Family 6 Model 42 Stepping 7, GenuineIntel
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1204 -    Number of CPU cores   : 8 cores
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1205 -    System is 64-bit      : True
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1206 -    Preferred Encoding    : cp1252
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1207 -    Machine Arch          : amd64
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1208 -    Available HDD (ARM)   : 151 GB
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1209 -    Available HDD (BTC)   : 242 GB
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1210 -
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1211 - Network Name: Main Network
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1212 - Satoshi Port: 8333
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1213 - Do wlt check: True
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1214 - Named options/arguments to armoryengine.py:
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     nettimeout      : 2
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     rescan          : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     ignoreAllZC     : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     enableSupernode : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     disableModules  : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     port            : None
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     interport       : 8223
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     skipStatsReport : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     forceWalletCheck: False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     rebuild         : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     datadir         : D:\armoryW
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     clearMempool    : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     offline         : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     coverageOutputDir: None
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     armoryDBDir     : DEFAULT
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     satoshiPort     : DEFAULT
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     useTorSettings  : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     netlog          : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     keypool         : 100
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     coverageInclude : None
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     forceOnline     : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     skipAnnounceCheck: False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     redownload      : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     multisigFile    : DEFAULT
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     disableTorrent  : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     testAnnounceCode: False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     mtdebug         : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     logDisable      : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     settingsPath    : D:\armoryW\ArmorySettings.txt
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     verbosity       : None
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     doDebug         : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     enableDetSign   : True
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     testnet         : False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     rpcport         : DEFAULT
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     satoshiHome     : F:\Bitcoin
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     satoshiRpcport  : DEFAULT
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     logFile         : D:\armoryW\ArmoryQt.exe.log.txt
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1216 -     disableConfPermis: False
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1217 - Other arguments:
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1220 - ************************************************************
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:1620 - C++ block utilities loaded successfully
2015-11-14 13:50 (INFO) -- BDM.pyc:418 - Using the asynchronous/multi-threaded BlockDataManager.
2015-11-14 13:50 (INFO) -- BDM.pyc:419 - Blockchain operations will happen in the background. 
2015-11-14 13:50 (INFO) -- BDM.pyc:420 - Devs: check TheBDM.getState() before asking for data.
2015-11-14 13:50 (INFO) -- BDM.pyc:421 - Registering addresses during rescans will queue them for
2015-11-14 13:50 (INFO) -- BDM.pyc:422 - inclusion after the current scan is completed.
2015-11-14 13:50 (INFO) -- ArmoryUtils.pyc:3531 - Using settings file: D:\armoryW\ArmorySettings.txt
2015-11-14 13:50 (INFO) -- announcefetch.pyc:95 - Reading files in fetcher directory:
2015-11-14 13:50 (INFO) -- announcefetch.pyc:104 -    announce         : 96f5d5f4253bac5528333c4fef3afd5fa0e931816bfd4c4c8b43d85cee002bb9
2015-11-14 13:50 (INFO) -- announcefetch.pyc:104 -    bootstrap        : b62c08932668ce162d51226135940724e90f4c71704ac936f74cc153b34cc251
2015-11-14 13:50 (INFO) -- announcefetch.pyc:104 -    changelog        : 1c01304b876de3e75672c8b13d9a00157556b86612afac1c88ffc40a8d7dfb90
2015-11-14 13:50 (INFO) -- announcefetch.pyc:104 -    downloads        : 28efee8047ee0a2c26ac9f785d93566fb5a45c20a794da6f972aa48db50ec35a
2015-11-14 13:50 (INFO) -- announcefetch.pyc:104 -    notify           : 87fa1adcd555be83a71b4f5935a6d4f85178ccbf5043531fdd71432b57d127ca
2015-11-14 13:50 (INFO) -- announcefetch.pyc:271 - Fetching: https://bitcoinarmory.com/announce.txt?osvar=8&os=win&ver=0.93.3&id=9b0e52bc
2015-11-14 13:50 (INFO) -- ArmoryQt.py:2736 - loadWalletsAndSettings
2015-11-14 13:50 (INFO) -- ArmoryQt.py:2790 - Loading wallets...
2015-11-14 13:50 (INFO) -- ArmoryQt.py:2849 - Number of wallets read in: 1
2015-11-14 13:50 (INFO) -- ArmoryQt.py:2854 -    Wallet removed for privacy                      "   (Encrypted)
2015-11-14 13:50 (INFO) -- ArmoryQt.py:2863 - Loading Multisig Lockboxes
2015-11-14 13:50 (INFO) -- ArmoryQt.py:2298 - Setting up networking...
2015-11-14 13:50 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible
2015-11-14 13:50 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt?osvar=8&os=win&ver=0.93.3&id=9b0e52bc
2015-11-14 13:50 (INFO) -- announcefetch.pyc:271 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt
2015-11-14 13:50 (INFO) -- ArmoryQt.py:2327 - Internet status: 0
2015-11-14 13:50 (INFO) -- ArmoryQt.py:2525 - loadBlockchainIfNecessary
2015-11-14 13:50 (INFO) -- ArmoryQt.py:2546 - Setting netmode: 0
2015-11-14 13:50 (INFO) -- ArmoryQt.py:1514 - setupUriRegistration
2015-11-14 13:50 (INFO) -- ArmoryQt.py:1632 - URL-register action: AskUser
2015-11-14 13:50 (INFO) -- ArmoryQt.py:664 - Usermode: Expert
2015-11-14 13:50 (INFO) -- ArmoryQt.py:1810 - Changing usermode:
2015-11-14 13:50 (INFO) -- ArmoryQt.py:1811 -    From: Expert
2015-11-14 13:50 (INFO) -- ArmoryQt.py:1819 -      To: Expert
2015-11-14 13:50 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:50 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:50 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:50 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:50 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:50 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:50 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:50 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:50 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:50 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:50 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:50 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:50 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:51 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:51 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:51 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:51 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:51 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:51 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:51 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:51 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:51 (INFO) -- ArmoryQt.py:5962 - Dashboard switched to user-OfflineOnlinePoss
2015-11-14 13:51 (INFO) -- ArmoryQt.py:6763 - BDM is safe for clean shutdown
2015-11-14 13:51 (INFO) -- ArmoryQt.py:6805 - Attempting to close the main window!

[goatpig]

Let's see armorycpplog.txt

[twebit]

Let's see armorycpplog.txt

It only says...

Log file opened at 1447528977: D:\armoryW\armorycpplog.txt

And ArmorySetting.txt is this...

ManageSatoshi                        | False
NotifyMinPriority                    | 2048
MainWalletCols                       | ff0500003c0078005000a502
Wallet_removed for privacy_DNAA_RecvOther      | False
NotifyBlkFinish                      | False
MainGeometry                         | 01d9d0cb000100000000014c000001030000063e000003ee000001540000012200000636000003e 6000000000000
SkipStatsReport                      | False
SendBtcGeometry                      | 01d9d0cb0001000000000204000000f9000005690000032e0000020e0000011b0000055f0000032 4000000000000
LastBlkRecvTime                      | 1447513708.15
LastDirectory                        | D:\armoryW
Agreed_to_EULA                       | True
MonthlyID                            | 1115_9b0e52bc
NotifyBtcIn                          | True
SyncSuccessCount                     | 10
MainLedgerCols                       | ff0d14000000ad004800700096007000000000000000000000000000
DonateAlready                        | False
UseTorSettings                       | False
DNAA_UnlockTimeout                   | False
WltPropAddrCols                      | ff052200bd00d8004000ae00
AlwaysArmoryURI                      | 0
PrefEndian                           | >
NotifyDiscon                         | True
SkipAnnounceCheck                    | False
KeybdOSD                             | False
NotifyIgnore                         |
DNAA_IntroDialog                     | True
SatoshiDatadir                       | F:\Bitcoin
DateFormat                           | 25592d25622d25642025493a254d2570
DNAA_AllBackupWarn                   | False
DonateFreq                           | 20
DisableUpgradeNotify                 | False
ScrambleDefault                      | 0
AdvFeature_UseCt                     | 0
UnlockTimeout                        | 10
Default_Fee                          | 10000
LastFilterState                      | 0
MinimizeOrClose                      | Close
SkipVersionCheck                     | False
User_Mode                            | Expert
Load_Count                           | 52
First_Load_Date                      | 1446854151
Wallet_removed for privacy_DNAA_RemindBackup   | True
NotifyBtcOut                         | True
DNAA_DeleteLevelDB                   | False
SkipOnlineCheck                      | False
MinimizeOnOpen                       | False
FailedLoadCount                      | 0
First_Load                           | False
Wallet_removed for privacy_ChangeBehavior      | NewAddr
Wallet_removed for privacy_LedgerShow          | True
IgnoreAlerts                         |
DisableTorrent                       | True
LastBlkRecv                          | 383544
DonateLastPester                     | 0
DonateDNAA                           | False
NotifyReconn                         | True
SatoshiExe                           | C:\Program Files\Bitcoin
DNAA_DefaultApp                      | True
WltPropGeometry                      | 01d9d0cb00010000000001a700000086000005830000039b000001b1000000a8000005790000039 1000000000000
LastVersionLoad                      | v0.93.3

[twebit]

One other thing I noticed is that while in this offline state if I click on wallet properties I hear a system ding and then the interface is locked and just ding ding everywhere I click on the armory interface till I end task.

[goatpig]

I don't have much to go on here. It definitely fails to either connect or recognize the blockchain data path. You should turn off auto bitcoind, start BitcoinQt manually and look at the peers, see if Armory managed to connect at some point (or check Core's debug.log)

If there is no trace of Armory connecting as a peer in Core's log, it ought to be a Windows firewall/Bit Defender/anti virus rule. If it does connect, then it's a pathing and/or permission issue on the blockchain data folder.

[twebit]

Ah ha! I found it looking in the bitcoin log there's an issue with it accepting connection here's the error that led me to check out the bitcoin.conf
"ERROR: CScriptCheck(): ca0ee950fb4c1092d5b8e91b236db50b541a1eb13f8de26f7334cb7f259b6f6d:0 VerifySignature failed: Non-canonical signature: S value is unnecessarily high"

I switched the bitcoin.conf off and it didn't work so I turned my old p2pool conf on and it connected.

So that's fixed for me but wonder why it would work in linux and not in windows?

Also I'm a billionaire according to my wallet I have 184467440736.77636719 BTC more than there is in existance... When I do a repair wallet it goes away.

Thanks for your help your last comment is what got me thinking about antivirus, firewall then bitcoin log was the hint I needed.