Bitcoin Forum

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.94.1

This is hopefully the one and only bug fix release on top of 0.94

Focusing on the next version from now on.

Copy paste of the changelog for the good measure:

Armory 0.94.1 did NOT compile successfully on my OS X 10.11.4 with Xcode 7.3 command line tools. This is the error:


I followed the OS X build instructions. (I also uninstalled all the Homebrew packages first before installing the ones mentioned in the instructions.)

It seems to me like the compilation is mostly done at that point and some of the final steps fail (I could be wrong). The Armory.app is there, but when I double-click on it nothing happens. Looking at Console.app, this is logged out when the Armory.app is double-clicked:


Any ideas?

Yeah. I goofed and need to generate a PR to fix the build issue. Sorry about that! In the meantime, if you want to paste in the following line at line 62 of osxbuild/build-app.py, you'll be fine. I'll put together a PR after rebasing on my end.

After adding your change, the compilation ran without any errors. But I still can't run Armory.app. When double-clicking on it (even if I copy it to /Applicaitons first), nothing happens, and Console.app logs out "Service exited with abnormal code: 1".

Any ideas?

Don't know about that one. Mine works fine. You may want to do a make clean and start from scratch to be safe.

Make sure 0.94 isn't pointed at a 0.93.x DB folder.

I tried that too (deleting the ~/Library/Application Support/Armory folder). Didn't work. Still getting "Service exited with abnormal code: 1". Any more ideas?

Update: When I go into the Armory.app/Contents/MacOS folder and double-click on the Armory binary there, the Terminal shows up and this error is displayed before the program quits:


Does this give you any clues about how to fix the problem?

You have to install the Twisted Python package.

Thanks, this did the trick. Armory 0.94.1 is now running on my Mac. This is what I did on my OS X El Capitan:
Maybe it would be a good idea to mention this in the OS X build notes. Thanks again!

You asked me not to point it to the older database, so it's starting from scratch now building the database. I presume I must do this. (Thankfully it's much faster due to the new smaller database size.)

Did you follow my instructions and do a make clean, followed by a complete rebuild? Long story short, assembly of the Armory package wasn't completed when you encountered the initial error; it just won't have everything you need, including Twisted, which is included inside the package (i.e., you shouldn't install it using brew).

Again, to be clear, there's no need to install Twisted on OS X; the build script takes care of that and downloads all the required runtime code. There's no need to update the documentation, at least in this regard. (Also, yes, I know the OS X build process is kinda wonky. Sorry. It's what was inherited a couple of years ago. It works but is far from ideal. Armory's former intern, Joseph, came up with a solution that would've been awesome. Alas, unless somebody's willing to spend days, if not weeks, rewriting his code from scratch, it can't be used.)

are these still the official build instructions for ubuntu?

https://github.com/goatpig/BitcoinArmory/blob/master/linuxbuild/Linux_build_notes.md

do i need to delete my current BitcoinArmory directory before building as i am getting this error:

yes. That's what it's telling you, and it means it. The other alternative is to execute the git command from a different directory, i.e. one in which no directory named BitcoinArmory exists. There is probably also a way of indicating to git that you want the target directory to have an alternative name, not sure what that is. Use "man git" or "git --help" for that.



Also, I would consider looking into using the "make install" command subsequent to make itself (perhaps specifically for Python/SWIG projects), as once you've ran make, the built application directory structure ends up in your home directory somewhere. The permissions set on those folders would allow external attackers to discover their existence, so the Armory executable & dependents are better off living in /usr/lib/ (where the Armory installer places them on Linux).

@cypherdoc

If you just want to erase the 0.93.3 location and replace it with 0.94.1:

cd BitcoinArmory (or whatever path gets you to the BitcoinArmory directory)
git checkout master
git pull
make clean && make

Subsequently, you won't need the second line once you're definitively following the master branch.

appears to have failed.  ran thru above steps and seemed ok.  but when launching, i still get 0.93.3:

I think you're probably still using the etotheipi repo. You need to run "git clone git://github.com/goatpig/BitcoinArmory" to access goatpig's fork. Delete or rename the BitcoinArmory directory first (or you could run the git clone command from somewhere that is not your home directory)

yeah, probably.

does that mean i go to your first post and delete the entire BitcoinArmory folder with it's contents?

See above! I strongly suspect that's your issue (git checkout master can only have performed that exact command; etotheipi's master branch is still on 93.3, whereas the goatpig master branch is at 94.1)

does goatpig have 0.94.1 git tagged?:

He does. I suspect there's some minor error in the version string you're supplying, but that's only a guess. I don't make use of that particular git command, so can't help you specifically with it from off the top of my head unfortunately.

so i run make and make clean and even make install but still get this:


thanks for your help on this Carlton.

Ok, so some command line essentials: if you're doing your git clone command afresh, the make clean command isn't needed. make clean is used to purge the old build prior to compiling a new one, so you don't need it for this situation. I think you may have run make, then make clean afterwards. Also, forget about make install for now, it won't solve this problem.

Try this to correct what's happened:

ok, got it.

now how do i delete Armory's copy of the blockchain?

It isn't signed.

Go to the armory data directory and delete everything in the "databases" folder.

You can also delete the /.armory/atisignedannounce directory. Hasn't caused me any problems thus far.

that's not good, is it?

what are these Errors at the bottom?  when the gui client opens, it still says 0.93.3 and isn't updating:

Ubuntu:~/BitcoinArmory$ python ArmoryQt.py
********************************************************************************
Loading Armory Engine:
   Armory Version:       0.94.1
   Armory Build:         x
   PyBtcWallet  Version: 1.35
Detected Operating system: Linux
   OS Variant            : ('Ubuntu', '14.04', 'trusty')
   User home-directory   : /home/x
   Satoshi BTC directory : /home/x/.bitcoin/
   Armory home dir       : /home/x/.armory/
   ArmoryDB directory     : /home/x/.armory/databases
   Armory settings file  : /home/x/.armory/ArmorySettings.txt
   Armory log file       : /home/x/.armory/armorylog.txt
   Do wallet checking    : True
(ERROR) ArmoryQt.py:6996 - Socket already in use.  Sending CLI args to existing proc.
(ERROR) ArmoryQt.py:7000 - Exiting...

It's not necessarily bad though.


It means the the socket that armory uses is in use. This probably means you already have armory open.

yep, had 0.93.3 still open.  sheesh.  all good now.  thks Carlton and KnightDB.

would be comforting if goatpig would git tag his source though...

ok, more trouble:


would that call for a bitcoind -reindex?

edit:  actually, bitcoind seems to be running normally.

hmmmmm, I think that's the C++ runtime making that complaint, but possibly nothing to do with bitcoind. Try erasing the /.armory/databases folder and rebuild the databases folder from the start. If that's unsuccessful, try bitcoind -reindex, but I'm not confident that's the source of your issue.

That part of the code (tx scan) is a multi-threaded high performance wonder, but it took some lengthy debugging in it's original incarnation. It's possible you've done everyone a favour by finding an unknown bug. Keep the log files if you can, goatpig may want to see them.

happened again after outright deletion of /.armory/databases folder, this time at a different blockheight:


running bitcoind -reindex

That's even more curious. I might be wrong about it being an Armory bug then, it's hard to believe that something so deterministic has not yet happened to someone else so far. I'm stumped by this one, if the re-index doesn't work, you will need goatpig, droark or knightDk to help troubleshoot. Limited knowledge of C++ runtime errors over here.

Small install bug...

Armory is 64bit (right?) but wants to install to C:\Program Files (x86) by default, should be C:\Program Files.

That's all!   :)

Also, I just realised...

I uninstalled old v0.93 version, moved AppData\Roaming\Amory, installed latest v0.94.1. When Armory was all synced and db built, I imported my wallet from my old AppData\Roaming\Amory folder.

Now all this worked perfect, but I just realised that Armory never asked for my passphrase for the imported (encrypted) wallet. It just imported it and was good to go.

Is that right?

Yes, that's expected behaviour.

The encryption only encrypts the private keys.  You cannot spend the coins without the password, but you can see them.

Ah I understand now, OK thanks.

bitcoind -reindex worked.

after a variety of issues, i just now finished it, and 0.94.1 is running.

Been running 94.1 for days now.

Thanks so much!  Works great!

crap, it's back!:

How much RAM does your computer have? I think Armory might be using up too much RAM.

hmmm, how much do you recommend?

well, there you go.

doubled my memory and it's working again :)

what clued you in?  that mempool.bin error?

Actually 'std::bad_alloc' did. It's a C++ error when something fails to allocate enough memory (I had to google it though).

Unless you are running a x86 OS or you have low RAM and disabled the swap (or actually managed to fill swap partition), you can't get a bad_alloc for running out of physical RAM. This is all virtual address space, the underlying actual RAM isn't all that relevant.

bad_alloc appears when the OS fails to allocate memory. This is more often the case when a bogus amount of memory is requested (say unserializing a random chunck of 9 bytes as a varInt and allocating that absurd number) than actually exhausting all RAM on the system.

If you suspect it is actually how much memory you have available on your system, you should try and reduce the RAM Armory uses instead of increasing yours:

https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BlockchainScanner.h#L96

Set this value to 2 to cut the memory use in half, then
make clean
make

It's currently tuned to run at around 1GB.

How is the latest Bitcoin Core doing with the latest Armory?  Any major bugs?

First off, thank you for keeping the project going. Very much appreciated!


I got 0.94.1 installed and get right off the bat:


Should I bitcoind -reindex?

Bitcoin Core (0.12) runs fine on its own though.

Yes. This is a deser error, that's unmistakably corrupted block data.

that's interesting b/c i had to increase it from 2GB to 4GB to get it to run again.

You also have to consider what the OS consumes.

And Bitcoin Core. Bitcoin Core consumes quite a bit of memory.

Thanks!

I have done the reindex, and - since the error persisted - removed the blocks, chainstate and database folders of bicoind. Now after everything is fresh I still get:


Lubuntu Trusty, 16 GB RAM, 51 GB free HDD

Any more pointers?

@Newar

are you sure that Armory is using the correct directory for .armory? it's currently in /root/, which implies you installed 0.94 while logged in as the root user? Can you try rebuilding the 0.94 db? (delete .armory/databases) It's possible that whichever erroneous contents in your previous copy of the Bitcoin blockchain also made it's way into the Armory databases, and so the tx scanning stage for Armory is essentially detecting that mismatch.

As Carlton suspects, you are using a fresh copy of the blockchain over a preexisting DB. Delete that DB, let Armory start from scratch.

I've been using Armory for a couple years now. I'm 'techie-light' so please bare with me & apologies if this has already been answered.

System: OS - Ubuntu 15.1 15Gb real memory 15Gb virtual memory

Initially I installed 0.94.1 on top of 0.93.1 using the Git clone + make + make install instructions.

That resulted in the Armory GUI showing a successful Wallet consistency check + successful Bitcoin Engine init; then the GUI turned grey and I got a program not responding message requiring a manual close which left Bitcoind running but no Armory process running. I then uninstalled Armory leaving the settings as was and re-installed.

Result: As above except that, instead of the GUI freezing, it simply disappears.

All looks fine in the log (to me anyway - ie no errors) until the last few lines as follows:
Any pointers much appreciated

You can't use the same DB as 0.93 for 0.94. Point to another folder using the --dbdir command line argument

Thanks gp. I renamed the 93.1 db folder then created a new one with standard name. All purring along fine now. If all remains well, I'll delete the old one in a day or two and get back 60+Gb of space

Another daft question:

How do I get the Armory icon to show on the launcher? - that's using the standard Ubuntu Gnome GUI

At present the launcher shows a grey '?'. Otherwise everything working fine.

I just upgraded 2 of my Armory instances and have had no issues so far. I just love seeing my used space cut in half with the new database setup.

goatpig, would you like a free Silver Wallet for being cool enough to keep Armory going? -> http://silverwallets.com/

That's a kind offer but I'll pass. These things look nice though =)

Thank you both. Fixed.

I install new Armory win64 with core 0.12.1 and in generality it work.
But when I tried to close Armory - program froze and don't closed.
In log:

Then I wait more than 10 minutes, kill process and restart Armory.
But sometimes (in previous version) and now start with gray transactions (tab transaction active, but not unabled) and I can't browse transactions, but 14-15pcs visible (in disabled mode).
If I go to Dashboard tab I can't come back (button transaction gray and disabled).
Armory write that offline - loading database headers (long time - more than hour and nothing changed).
Image, that many time I see in Armory (from 19:16 to 20:17):
http://s019.radikal.ru/i615/1604/72/40f9591a435a.jpg
I shoutdown Armory and close OK.

Then I run Armory again - start and close without problem in few minutes. WTF?) Connection to internet stable all time:
I think may be this line do Armory offline and then don't come back: 2016-04-24 19:16 (INFO) -- ArmoryQt.py:5801 - Dashboard switched to auto-BadConnection (but blocks downloading!).

Armory is failing to shutdown bitcoind somehow. Turn off auto management and deal with BitcoinQt manually instead.

In this version I found that for some transactions I have the Invalid TX error message: "The transaction be displayed you requested does not exist in Armory's database. This is unusual..."
I tried to rebuild the database from scratch, delete and import wallet - nothing helped .. The transaction is there, so I suspect in some reason Armory decided to not include the transaction in DB. Would it be considered as a bug? I am going to revert back to v0.93 to see if it has the same issue. Will post about the result.

It is considered a bug, and already reported to some extent. I discovered the same problem with both coinbase outputs and transactions that spend coinbase outs, but too late for goatpig to fix it, sadly. Can you tell us whether the tx's you're experiencing this with are either coinbase or spending coinbase?

Sure, this is related to spending coinbase ...

Ok, that's the same bug me and knightdk found. goatpig knows, so it will likely receive a fix. I don't think it's a problem to continue to use 0.94 with wallets containing coinbase, although I can't say whether spending coinbase will work with 0.94. So you can probably use 0.94 for now, or to put it another way, that's what I've been doing.

Thanks for letting me know that this bug is already known, so waiting for the fix then ...

ok, i deleted the 0.93 db, but now Armory keeps crashing at the exact moment it ends syncing and tries to load the database headers.

any idea?

edit: ok, rescan&rebuild the db seems to do the trick

Hi every one.
Does this mean we can not use 0.93.9 version of Armory anymore or it doesn't make a difference?
Because I have been trying to build the Armory 0.93.3 version and it takes up all my 267GB memory space, I do not know why...:-(

You can still use it, but it is recommended that you use 0.94.1 because it is the latest version that has fixed several bugs.

The databases for 0.93.3 and earlier are much much larger. Use 0.94.1 and the databases will only be a few hundred MB instead of several Gb

thank you :-).

I now have armory the transaction you requested displayed does not exist in database.

My transaction summary is now missing 5 coins... I can't tell if they were stolen or if this is armory. I am switching to bitcoin core.

Armory seems to have a security problem where malware can transfer coins I can discuss thanks

Is there a way to switch back to bitcoin classic? I have 5 wallets

Now 5 coins are missing.. I receive transaction doesn't exist in database error in armory.

I have no way to access my funds and I can't export my wallet so basically this is a bad situation.

I need to check if this is an armory bug or worst case if they have been stolen as I have found a bug that may allow one to do this.

Please do not jump to conclusions and make definitive statements like this without knowing what is actually wrong.

If the transaction(s) was a coinbase transaction, then this is a known bug. We know that there is a problem with Armory when displaying coinbase transactions

If the problem is something else, then can you also provide us with the armory logs?

Lastly, is the five bitcoins missing from your balance or is it just that you cannot see the details of the transaction that sent you those Bitcoins.

I don't know if it's coinbase.. all the sudden I see these transaction subtracting from my account of wallet 2 and then it happens 12 hours later to wallet 1. Non of these transaction are openable. All have error message transaction can't be displayed, does not exist.

Is there a specific log file I can sent?

These transaction shouldn't be there and now I can't really view the details and coin is gone from the interface.. but I've had incorrect totals before that were fixed by this release

That might be a bug. Since the coins are leaving your wallet, then it isn't a coinbase transaction. Try rescanning the wallet. Go to Help > Rescan Databases and then click OK on the dialog box. Then restart Armory.

Go to File > Export Log File and it will instruct you to save the file somewhere. Open up that file and post the contents here. If Bitcointalk tells you that it is too large, post it to pastebin and post the link to that pastebin.

This is what my dashlooks like..

All those negative transactions, I never made them. You can not get transaction info from them.

I deleted all databases and rebuilt.. took me 4 days, same problem... I need to get my wallet into bitcoincore and test there but I don't know how.

http://s32.postimg.org/jeat22kat/armory.jpg

The log is at:

http://s000.tinyupload.com/index.php?file_id=94864565476841356988

How can I revert to check my coins in another program? How can I go armory -> bitcoin core?

Did you rescan the wallet. Not rebuild the database but rescan the databases. There is a difference between the two, and rescanning shouldn't take as long.

Are you able to copy the transaction IDs of those transactions and post them here. If there is a bug then those txids will not match what the transaction supposedly is in your wallet or they may not exist.

I am unable to download your log.

Thanks, I have scanned and rebuilt everything. I did this database from scratch and had the same problem after.

I can not get transactions on them.. I double click and get this entry doesn't exist in armory error message ( exact message is in other posts)

It will show up as invalid ID on bitcoin transaction explorer when opened in application

The log is working for me:
http://s000.tinyupload.com/index.php?file_id=94864565476841356988

I am trying to load a wallet into bitcoin core to test now.

Here is the message I get when I click on the transactions now (the withdrawls).. the old transaction work. I think there's something wrong with these transactions.

http://s32.postimg.org/jfz1dkvr9/armory_fix.jpg (http://s32.postimg.org/jfz1dkvr9/armory_fix.jpg)

Some of them work, but I don't know if they refer to the correct transaction.

Are you by chance pruning bitcoin

No, I have not pruned. I don't really know how. I have loaded the bitcoin db, and redid the armory db.

I then reload the bitcoin db and redid the armory db but this takes 4 days to get the data 100% again and same issue.

Just take your private keys and import into core

I don't know how to do that and don't understand the dangers about it.

The wiki warms me of losing coins.

Is there a way to make a wallet.dat?

How does this import related to wallet.dat? Will I do it every time? I need to use bitcoind RPC calls? I don't know how this is working in relation to wallet.dat

I'd like to make 5 wallets and just take them and switch em in bitcoin core to check if it sums the transactions differently.

1) Make sure you have flagged all wallets as yours, or display all wallets in the bottom right combo box.

2) Extent your wallet's address chain.

3) Make sure the top block in Armory matches the top block in Bitcoin Core

4) The missing txid error is unrelated to your issue, it's explained here: https://bitcointalk.org/index.php?topic=1385530.msg14111584#msg14111584

Thanks, I'm getting these type of error messages around the time period:

2016-05-06 18:32 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode

I have done "receive coin" to generate an address on all wallets and then rescan db and restarted.

Armory Current block number: 411478
Bitcoin logs show something like: blocks=411385

I think Armory is OK..

More of the error text:

http://pastebin.com/jGy2iQ72

That's Armory having trouble talking to Core through the RPC. This isn't related to your issue however.


You want an extra 1000, not just one. Go in offline mode, pick expert mode, in the wallet properties dialog, click on the figure next to addresses used, set 1000 in the text box and click compute. Do that for every wallet, then restart Armory in online mode and let it scan. Also, in the wallet properties dialog, make sure all wallets are flagged as yours.

Thanks, I added 1000 to the wallet and restart it, still same problem.

Those log errors look around the time of the "bad" transactions in armory. They start around the time of the problem transaction and they end around the time it's finished (running all day on the 2016-05-06). This is causing some transaction log corruption?

Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:40 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:41 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-05-06 13:42 (ERROR) -- SDM.pyc:883 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 857, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 104, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded

Again, this error is unrelated. I don't know why the JSON-RPC interface is failing but none of it is involved with transaction scanning. Turn off auto bitcoind management to get rid of these messages. With that done, start BitcoinQt manually, then start Armory, and make sure the top blocks match exactly.

What leads you to believe the balance is incorrect? Did it show before? Have you received a payment that never showed up?

I am beleiving these balances are not correct because:

1. I had a number of coins sitting in my wallets and I didn't transfer them
2. Problem transaction start to appear around error messages
3. Transaction do not load up when double clicked (see screen before)
4. Transactions that do load up when double clicked seem to have incorrect transaction references.

I am hoping my coins are still here and this is a transaction issue.

I have above screen shots with some of the display

I tried turning off management, and allowing bitcoin core to load and then allow armory, but the problem is still the same

Block counts are the same in armory and bitcoin core

That's unrelated. That's left over GUI code that I didn't update to reflect the changes in DB structure. Again, I linked to the explanation for the why and how.


Check each addresses on a blockchain explorer, no reason for your coins to have moved at all.


Armory failed to compute the hash for these transactions somehow, that breaks a bunch of a stuff in the scanning process down the road. That's a bug and it shouldn't be happening at all. I would suggest you redownload the blockchain from scratch in another location and rebuild a fresh copy of the DB against that chain, ideally on another machine.

Ok, I redownloaded it.. it took 4 days, and retested. I dont have another machine I can use.

Is there a way I can port a wallet to bitcoin core so I can test there?

Thanks

You have to export the private keys from the Armory wallet and import into a Core wallet. Have you checked the address balance on a blockchain explorer yet?

I'm trying.. I don't know how to tell..

It does really look like a problem with those transactions not being valid

I don't know how to move wallets or restore them

I can't really tell how to do the bitcoin explorer addressing checking..

Is there a way to check the aggregate?

When I double click the withdrawl transactions, it comes up with the error.

"The transaction you requested be displayed does not exist in Armory's database. This is unusual..."

The transaction all seem to say "UNKNOWN INPUT".. I dont know if this helps, I'm trying to find at transaction I can check. The problem is the coins are missing, can't be used..

You need to export your private keys and import into core

I heard that it's dangerous and breaks the wallets.. I've got two.. hoping for a fix or something?

No you'll be fine as long as you don't share the keys. You can't lose anything by importing.

Also, post an address and what it is supposed to have if possible.

What is the latest downloadable build which is running on Win32? Will there be any interaction problems with 0.94.1?

Edit: Using a 32 bit Win system as offline device for signing.

You have 3 possiblities:

1) Export keys to another wallet software.

2) Try to debug Armory yourself.

3) Identify the buggy wallet and send me a watching only copy to reproduce and debug on my own. You lose privacy but I get to fix the issue.


0.92.x had x86 builds and is compatible with later versions. Otherwise you can build 0.94.x in x86, that will run just fine. Not sure about XP though.

Thanks, it's best I sent a watching copy. It effects two wallet so it should be the same issue in both of those wallets. I send to you now.

Will let you know what I found out tomorrow.

i have seen this error message too in my wallet:

"The transaction you requested be displayed does not exist in Armory's database. This is unusual..."[/i]

Looks like it happens under certain (yet to be determined) conditions when the sender address is used as the change address. Will let you know when I figure out the bug and fix it.

new problem:

upon opening Armory 0.94.1, wallet consistency check starts fine but then:

1.  Sync blocks-OK
2.  Building Database-OK
3.  Scanning Transaction History-GUI shuts down (closes)

any ideas?  Armory is set to manage bitcoind.

Ubuntu 14.04.4 LTS

edit:  was working fine until i added 1000 addresses to one of the wallets.

Do a rebuild & rescan

would that be:

bitcoind -reindex and then bitcoind -rescan?

do both?

running bitcoind -reindex.

is there any indication when it is finished?

No I meant picking Rebuild & Rescan in Armory's Help menu...

what exactly is that command doing?  is it working on just the Armory DB or Bitcoin's DB or both?

Installed 0.94.1 with an alternative folder for the db (--dbdir) and all is well.  If i drop the --dbdir argument it will re-build the new ~120MB db in the default folder and delete de old ~70GB one - correct?

It won't delete the old one; you will have to find it and delete it manually.

worked, thanks.

So even if I don't use --dbdir to choose an alternate db folder Armory 0.94.1 will not use the old directory, e.g.: "databases"?

One question about key-stretching: which algorithm are you using? ROMix? Scrypt?

It will use the default folder lacking any specific CLI arg, i.e ~/.armory/databases


ROMix I believe.

OK, so the recommended procedure when upgrading to 0.94.1 is to manually delete the old databases, right? Otherwise we would have in the same folder the ~70GB db together with the ~120MB one....

May I ask who is in charge of mantaining that part of the code?

Yes.

Goatpig is the only one in charge of maintaining anything in armory as he is the only full time developer of it.

Ok, hope it's going OK. Looking forward to new version. Thanks

Your wallets helped me identify and fix 2 GUI bugs, but nothing in there indicates the balances are off.

Most of the wallets funds were moved in some 15 transactions, all spending coins to a same address. Half of them had change, and the pattern does not suggest someone stealing coins or trying to sweep the wallet, rather deliberate, incremental spending. I invite you to look into that, notably that one recipient address.

Ok, thanks. I did not spend these. The only way is a bug or someone stealing them with a trojan. I didn't spend, the balances are very weird to leave money like that. Thanks

Can you confirm someone has stolen all my coins?

If this is true. This is something connecting to bitcoind while armory is loaded with the RPC configuration in the config file, scanning wallets and transferring out.

Is there anyway to confirm this was stolen? Bitcoin is really not useful. People stealing $2000 just like that? I'm so'posed to run a business like this?

There is a set of transactions moving coins from your wallets but again the pattern does not reflect theft, rather deliberate spending. It would make little sense for a thief to steal your coins the way this was done. Without further investigations, I cannot qualify this spending pattern as theft.

To confirm or infirm this case, you would need to present more information and/or enlist the community into helping with the investigation. You would would have to at least divulge the addresses involved, your spending habits, and whether you know the recipient addresses.

I cannot assert if this is theft with what information I have, and so far I remain skeptical.

It is theft. I don't spend any coins.. I was about to transfer out but I wasn't able to.

I collect small payments into 2 wallets from my business. I never spend and then I was going to exchange it..

Unless this has somehow "spent" into an address which I can still access? This doesn't make any sense to me. What do you need?

Armory was running in the background

I am scanning for malware now, the only thing i can think of is it want bitcoin client and got the wallet address and balances and RPC a transfer.

I agree it doest look like it's theft, but I didn't use them.. so unless it's a bug.. it's definitly thefy

Whatever it was appeared to push all my coins to this wallet:

18mhcZ4tdD2GQquSrMda5TPzgRodAEfYeF


I am hoping it's a bug.. I just spent money and time to lose money.. $2000 is alot of money for me.

It could be someone physically close to you and he did a hasty job of corrupting your wallets

Nope, no one has access to my machines or my office

I'm telling you, if these coins are coin, it's a trojan most likely used RPC while armory was open.

Unless this is another type of attack. Who knows why it was done like this.

I'm still hoping for a bug

Increase your keypool and start private keys importing into bitcoin

I noticed bitcoin-cli can connect while armory is open.. not sure if it is possible to issue commands such as get wallet balance and transfer..

Otherwise, if this is not a bug that has made a mistake in transaction account, I have no idea

Try to export private key in new wallet and check using bitcoin?

I have 2 wallets I need to try this on..

Is there instructions for exporting and importing into a wallet.dat?

I need to do it twice?

http://bitcoin.stackexchange.com/questions/5941/how-do-i-import-a-private-key-into-bitcoin-qt

You need to do it for every armory address

Ok, I will now try to import all 5 wallets into wallet.dat on my bitcoin install and see if that restores the coins

This is 1/3rd of the story at best.

We are talking about 5BTC, split in 2 wallets, ~2.9 BTC in wallet A, ~2.1 BTC in wallet B.

On May 6th, 3 transactions in block #410492 moved coins from wallets A and B to address 18mhcZ4tdD2GQquSrMda5TPzgRodAEfYeF:

- tx 1&2 move all coins from wallet A. All coins in this wallet were split between 2 addresses. The spending tx each sweep one of these addresses.
- tx 3 moves all coins out of out of 1 address from wallet B, about 0.28 BTC.

In all cases, there was no change and all outputs were spent regardless of how small they were (a few were >0.02 BTC). This pattern is indicative of a private key sweep.

However, all transactions came with small fees. All fees were >0.002BTC. Considering one of these tx spends 10 utxos and another one 7, we're far below the proper fee/kB for quick confirmation. The fact that all 3 tx were confirmed within the same block with such low fees is possibly an indicator that they sat in the mempool for some time.

This to me doesn't characterize theft, rather deliberate private key sweeping. You would expect a thief targeting your private keys would be sophisticated enough to pay a 0.01 total fee on 3 tx stealing some 3 BTC just to get included in the next block.

This accounts for ~3.2 BTC. If the story ended there, and you claimed 3.2 BTC were stolen, then you would have more evidence supporting your claim than otherwise. The fee analysis alone is not strong enough on its own refute theft. However, you are claiming 5 BTC are missing, and the last ~2 BTC leave your wallet in a different fashion.

---------------

About half a day later, in block #410581, 6 transactions move coins from wallet B.

- 5 tx spend to address 1CDyeeCHcReYhfaeTb37Piwq8ZWqLtHU5o
- 1 tx spends to address 12DaNV3b6iSobe5uMwBELYdMkoLJ1V4eto
- 4 out of 6 addresses return change
- As a result of change, wallet B currently has a balance, albeit rather small. Nonetheless, this balance remains larger than some of the smaller utxos that were redeemed among all these transactions.
- The fee/kB density of these 6 transactions is over 2~3 times superior (guesstimate) that that of the first 3 transactions.

---------------

It is also notable that prior to these 9 transactions, you only spent coins once, from wallet B, in November 2015. This implies, in case you use online wallets, that you rarely if ever typed in your password to decrypt your private keys. The point is moot if your wallets are offline. On the other hand, there is not much to discuss if your wallets are online and unencrypted.

This observation narrows down the possible attack vectors. Since you didn't spend any coins for months prior to the event, this couldn't have been an attack on the recipient address (swapping a payment address for the attacker's), nor an adversary process trying to steal your password/encryption key or decrypted private keys in RAM. This also rules out RNG snafu.

Again this point is moot if you toyed around with your password a few hours before the coins moved. This comment in particular and this post in general should be a reminder that you need to provide as much details as possible if you hope to find out what happened to your coins. Your wallets only speak that much.

The only credible attack vector that remains is that someone has access to your encrypted wallets (physical access to your computer, cloud storage backup, infected machine, etc...) and your passwords (possibly brute forced if they are weak, again need more details here). However, this would contradict the sweeping pattern: why sweep private keys if you crack a wallet? Just spend it all in one go.

Still this doesn't explain why the attacker would sweep all keys from one wallet and only ~15% from the other, nor his spending pattern (you'd expect 1:1 spend address to wallet address, or a single address for all wallets), nor why he deemed useful to return change, nor why he paid low fees to steal >60% of your coins and much higher fees for the remainder, and lastly why he did it 12h apart.

So I guess this is some type of trojan that has been sitting calling bitcoind every 10 minutes or something trying to extract private keys?

I'm trying to port over to bitcoin-qt now to verify. I don't know exactly how it was done. I remember it was a day I visited a litecoin website and installed litecoin.

There is some brief window in time that allows this to be read from bitcoind after unlocked?

Wallets should not have been unlocked with bitcoind at those two times. I don't see how they can have my passphrase. Will update soon.

That address is still growing where coins have been transferred.

What has bitcoind to do with this? Have you imported your private keys into a Core wallet before this event? Armory wallets are entirely separate from the underlying node. Armory never communicates private nor public keys to the Bitcoin node, nor does it need to.

No, I haven't done this exported and imported before

I am still trying to figure out how to export from armory to a format I can use in bitcoin-qt console for function

importprivkey

I tried PrivBase58, PrivHexBE, SHA256(?) format but it would give me the error:

Invalid private key encoding (code -5)

If you are calling Armory a trojan, then you are mistaken. It is not a virus nor is it malware.

When you look at the Address key info, you want to use the "Private Key (base58)" or if you exported the key lists you want "PrivBase58", both are the same. You want to copy that string without spaces in order to import to Bitcoin Core. There is a handy little checkbox when you export the key list to "Omit spaces in key data". The key should start with a "5" (all uncompressed Bitcoin Private keys start with a 5). If it does not, then it is not the importable private key.

I am not calling Armory a trojan, I am talking about a trojan running at the same time as Armory trying to steal bitcoins.

Thanks, I am trying to import now. I am thinking of how this could be possible.

I keep getting Invalid private key encoding (code -5) in bitcoin-qt console

I have no way to verify this is correct in bitcoin core.

I need to export my wallets in core to make sure my coins are stolen.

importprivkey is not working on the armory exports

It just doesn't make sense to me, I need to confirm in bitcore-qt

I'm working to generate payment in coins here.. have about 5..

Then one day armory just shows incorrect balances and the interface starts being buggy..

And so it's now a trojan or something that stole the coins but the interface is buggy so I can't tell

I want to export into bitcoin-qt core to see the balances there before I conclude someone must have trojaned my computer and stole  those from multiple wallets with passphase

But now I can't export to bitcoin-qt with any armory export?

Any ideas?

It works fine for me. You need to make sure that you are not missing any characters and don't have any spaces in the private key.

P.S. You should stop posting consecutive posts like you are doing right now. It is very spammy. Instead, when you have some information to add and no one has responded yet, please edit your last post with that extra info.

Was it an unsolicited phishing link that encouraged you to install (https://www.reddit.com/r/Bitcoin/comments/4k4nz6/received_a_random_dropbox_share_with_a_bitcoinjs/) litecoin that day?

See also https://bitcointalk.org/index.php?topic=1478385.0;all

Yes, it's confirmed in bitcoin core someone managed to steal all my coins out of all wallets in armory with passphases on the wallets

Armory's key points of differentiation are privacy and the security of cold offline signing +/- multisig lockboxes.

If you're not using an air-gapped cold offline signing process with Armory (especially if running windows), then you're no more secure than just using a wallet on a jailbroken phone.

And he still hasn't provided that level of details. Are the wallets offline or online? How long are the passwords, do they contain easily identifiable tokens? Does he use the password same for each wallet? Has he manipulated his wallets within the week leading to the event and how? What about month? Has he changed encryption on his wallet recently? Does he has cloud storage backups? What password do they use? Does he know of the addresses that received the coins? Has he scanned his online machine for infection? Any logs we can look at?

I've spent enough time on this. Short of some new significant evidence, this is in the hands of the community.

Armory is supposed to be used offline for maximum security. I trust it solely with all my bitcoin.

For you, use trezor in the future.

Question.

Is it possible to see the size of a tx before you send it? Either with direct sending or with the steps of creating an unsigned tx - sign & broadcast it?

I ask this because I made a transaction that had a huge size in kb and so an extremely low fee sats/bit that will take ages to confirm.

So next time I would like to prevent that.

You can look at the raw tx after signing it, in the offline signing/broadcasting dialog.

Thanks. I looked everywhere but didn't decode the Raw Tx  ::)

As of now there is no way to rebroadcast the tx with a higher fee right?

Any plans to implement replace by fee in a next update?

At some point but not in the next update. Doesn't matter for your particular case, the original tx would have to flag RBF to be replaceable anyways. You can always try a child pays for parent to hurry things up, some pools do prioritize those I believe.

I just waited it out. It took about 13 hours for a 3 sats/b tx.

https://bitcoinfees.21.co/

You can choose the sat/b based on how long you wish to wait.  Bitpay in my experience accepts 0-confirmation payments, so you can use the lowest fee setting in mycelium.

It was not the fee that was the problem at first, it was the size of the tx as it was build up from all small inputs into one output. That made it almost 9kb. Normally my tx are between 200 and 800 b and my fee is slightly higher then average/ideal on tradeblock or blocktrail. So that is why my fee was 10 to 20 times lower then normal.

i was having some unknown issues opening 0.94.1 with Ubuntu 14.04.4 LTS in a VM.  once opened, i found one of my watching only wallets missing.  this persisted upon a reboot.  strange.  any ideas about why?

had to make a fresh restore of this watching wallet from the offline wallet and made one tx w/o any problems.  phew.  i noticed in the meantime that all Comments were gone.  is there any way to recover the original file with it's comments?  any problems wanting to do this?

Without fail Armory 0.94.1 crashes when it starts "Loading Database Headers".

I am fully in sync with Bitcoin Core. I did not have this issue with 0.93.3. OS: Windows 10.

Is there a layman's reason for upgrading to 94.1? Will 0.93.3 ever not be able to receive transfers while online?

https://i.imgur.com/0CICjhX.jpg

I appreciate any help regarding resolving this error, thank you very much.

My Windows 10 also barely worked and had permissions issues. I nuked it back to 7.

Try deleting the directory after backing up your wallet. Then import.

Thanks, so far I've tried the following:

• Ran the Armory uninstaller.
• Deleted from the Program Files directory.
• Reinstalled 0.94.1 and changed the name to NewArmory.

I haven't deleted \AppData\Roaming\Armory\databases because I figured I'd have to reimport and all that.

FWIW, I then reinstalled 0.93.3 and everything worked without crashing & I received transfers as normal. So I'm sort of wondering if there's any immediate reason I need to upgrade in the short-term aside from the DB not taking as much space with the new version.

Rename AppData\Roaming\Armory

Thank you, looks like that did the trick, it is now building the database blocks. After it finishes I'll have to reimport my watch-only wallet since it was gone after I renamed the Roaming/Armory and reinstalled the 0.94.1. Hopefully no more crashes.

Yes just reimport. I've seen horrible permissions issues in win 10 for some reason. And admin actions aren't always root. M$ is scum and now they're tricking 7 users into upgrading.

Hi everybody.

I'm trying to build goatpig's Armory fork on Windows 10 x64 but as I'm quite a newbie I can't complete this task. I used this (https://github.com/goatpig/BitcoinArmory/blob/master/windowsbuild/Windows_build_notes.md) as a reference. I installed everything needed, including MVSE 2013. I then got several errors when trying to compile C++ parts, I got rid of some of them but then I got stuck.

Trying to compile "guardian" :

• Success

Trying to compile "cryptopp" :

• Error C4996: 'inet_addr': Use inet_pton() or InetPton() instead or define _WINSOCK_DEPRECATED_NO_WARNINGS to disable deprecated API warnings (socketft.cpp #102) > Solved by adding a line in socketft.h : "#define _WINSOCK_DEPRECATED_NO_WARNINGS"
• Then success.

Trying to compile "LMDB_Win" :

• Error C4146: unary minus operator applied to unsigned type, result still unsigned (mdb.c #6504) > Solved by replacing "sizeof(size_t)" by "INT_MIN" on this line
• Error C2440: 'function': unable to convert 'DWORD (__cdecl *)(void *)' to 'LPTHREAD_START_ROUTINE' (mdb.c #8776) > Still stuck here

Trying to compile "BitcoinArmory_CppTests" :

• Error C4996: 'lseek': The POSIX name for this item is deprecated. Instead, use the ISO C++ conformant name: _lseek. See online help for details. (blockdatamap.cpp #326) > Solved by replacing "lseek" by "_lseek" in blockdatamap.cpp, lines #326 and #327
• Error LNK1104: cannot open file 'LMDB_Win_d.lib' > Still stuck here because of LMBD_Win compilation failure

Trying to compile "BitcoinArmory_SwigDLL" :

• Error LNK1104: cannot open file 'LMDB_Win_d.lib' > Still stuck here because of LMBD_Win compilation failure

Would you mind helping a noob doing this quite difficult task ?
Thanks in advance.

I've run into this issue before. This is what goatpig told me to do:

Thanks for your answer, but it seems that I simply didn't select "Release" (and "x64") before building. I find Visual Studio's GUI to be a bit confusing for newbies.

I managed to build something, now I just have to try it. EDIT : It does work!

@goatpig, Why cannot broadcast offline transaction ? (ubuntu 16.04, bitcoin core 0.12.1)

Tx was broadcasted, something GUI element failed after that.

I just discovered that when I double-click on an outgoing transaction on the main "Transactions" tab to display the Transaction Information (Windows 7), I get:

"The transaction you requested be displayed does not exist in Armory's database. This is unusual..."

Context Menu (right click)>View Details - yields the same result as above.
Context Menu>View on blockchain.info - works (opens the page) but says "Transaction not found"
Context Menu>Change Comment - works
Context Menu>Copy Transaction ID - does not work (no Tranx ID copied onto the clipboard and therefore cannot/nothing to paste)
Context Menu>Open Relevant Wallet - opens Wallet Properties of a totally different wallet

I already did "Rebuild and Rescan Databases", but to no avail. A Linux machine setup of the same wallets have the same issues. Outgoing Incoming transactions on both W7 and Linux machines are fine though.

Any thoughts?

It's a known issue. There's a post somewhere here explaining it.

Oh! Sorry for missing the post. Thanks for the info.

Is a fix slated in the next release?

Yes

Any info why Armory is no longer displayed on Bitcoin.org site as one of the suggested wallets? I am talking about their "Choose your wallet" section.
Armory used to be listed there but it is not anymore.

Something happened?

See: https://github.com/bitcoin-dot-org/bitcoin.org/pull/1235#issuecomment-185676811

I tried to get it reinstated here: https://github.com/bitcoin-dot-org/bitcoin.org/pull/1301 but it hasn't been done yet.

Sorry if this is a stupid question but I just upgraded to 0.94.1 from 0.93.3 (old Website) and had to rescan and rebuild Databases to make the programm pass the Step with reading the Header.

Now it all works :) but I cant find any update function anymore... is it gone or is something at my programm wrong?

Thanks in advance!

Hey mate had the same problem, just click (while loading) at the Top menü >> Help >> Rebuild and Rescan Databases >> close the whole Armory and start it again >> be happy  ;)

Yes, the database format has changed so it is both much faster to rebuild and rescan and much smaller than the original. You should delete the old databases to free up a lot of space (several 10s of GBs). If you delete the databases folder inside the data directory, it will remove the old databases and the new ones, but don't worry, the new ones will be rebuilt very quickly.

No, that is how it is supposed to be. The updater stuff was removed since the announcements server is no longer working, the development has changed leadership, no announcements server is set up that we can use, and we don't want any phone home code. It may be reintroduced later if we decide to.

Thanks for the reply!
Sorry but all this Armory things are pretty new for me. Could you pls tell me which directorys/Files I have to delete? Running Windows 10 x64 Enterprise and had the normal installation (no custom settings/paths).


What is a 'phone home code'?
Oh thats sad. where can I find the latest stable version of Armory? Is it this Link https://btcarmory.com/releases/ ? Or is there any other link for stable versions?

Is there any option to change language?

Thank you very much in advance!

For you, it should be %appdata%/Armory Delete the folder named "databases" and then start Armory.

Phone home code is any code that communicates back to a server controlled by the developers (i.e. it phones home).

That is the link. All releases will be announced there with links to the downloads.

Working on it. It will likely be available in 0.95.1. If you want to help with that, we have a Transifex project open at https://www.transifex.com/bitcoin-armory/public/. You can help translate the project to another language.

Damn.. that gave me 80GB ??? how is this possible? The whole Blockchain is just 70GB. But as long as it works I dont complain about getting back 80GB of my SSD :)


Oh ok but how will the new Update-System work then?


Thanks!


Already started ;)

Don't know yet, it isn't really a priority right now.

Hi guys just send some money with Armory 0.94.1 and got this error.

https://i.imgur.com/16NywHi.png

The Error is "Invalide Tx"
If the money now gone forever??

Ok. This is what happened.

The transfered money is where it should be! and already got over 20 confirmes, but I still cant see the Details or even open the transaction at https://blockchain.info as I cant see any details of the transaction.

Even deleted the DB twice just to make sure the DB is builded correctly.
Now my friend confirmed the money is at his account but the fact of this Errormessage and that I cant see any details of this transaction bugs me quiet a lot :P

Is there any solution for this problem?



Thanks in advance!

That's a known bug and should be fixed in the next version, 0.95.

The money is not lost, as the transaction has confirmed.

Just go to Help > Rescan Balance and follow the directions of the dialog. It will rescan the blockchain for your balance and you should see the Bitcoin there.

So both v0.94.0 and v0.94.1 are not signed?
That way I have to trust that noone manipulated data in the repo circumventing the regular, visibly logged commit infrastructure?
Are/will any releases be signed?
For me, this repo is so much of a target that the risk of unsigned releases is too high for me..

Ente

All releases are signed. All future tags will be signed.

Sounds great!
Just to be clear, a "release" is like a major version, right? Is 0.94.0 a release then, and is it signed already?
I'd like to step up to 0.94, for the much reduced database size..

Ente

A release is any version that has a tag and published binaries. The binaries for 0.94 and 0.94.1 are hashed and those hashes are placed into a file and signed. That has happened with all releases. The tags are also signed, but goatpig didn't do that for 0.94 or 0.94.1. Future releases will have signed tags.

Aah, I see! Thanks for the clarification!

edit: So Armory doesn't like a pruned bitcoin-core? I need the whole blockchain each time Armory starts up?
edit2: Restoring 91 GB bitcoin-core stuff.. *sigh*

Ente

Nope, pruning won't work. It reads the block files directly and it still needs the entire blockchain which a pruned node cannot provide.

I know I'm probably opening a can of worms and that this isn't a priority, but 0.94.1 can't seem to auto manage bitcoind in Windows 10 14931.

I've had similar problem before, and back then it was because of permissions, but this time I've set them before running bitcoind and Armory.

Here's the logfile:


Everything seems to work fine without auto manage

It can't even read bitcoin.conf. Does the file exist?

Check the permissions on the bitcoin.conf file. Make sure that you are allowed to change it's permissions.

Yes, it does. I've formatted my Windows drive, the drive with Bitcoin and Armory files is intact.


I'm checking. Not sure what's up now as I've already set permissions as I did last time. I'll probably take a rest and look at this when I'm fresher, probably something obvious missing... It really sucks messing with file permissions on Windows :D

Thank you for your replies.