Topic: armory in ubuntu for newbees (Read 313 times)

As a summary, I want to list a few things I had to take into account when running armory:

- When downloading bitcoin core, use the tgz and not the snap. With the tgz, the blockchain files will be stored in the .bitcoin/blocks directory where armory looks for them.
- Disable bitcoin core pruning.
- Wait for bitcoin core to fully synchronize before launching armory.
- Use a decent computer. Both bitcoin core and armory are demanding. I used a six year old computer with an intel core i3,  6 gigs of ram  and some 450 GB of HD and at some point it was too slow or even freezed.
- Use ubuntu 18.04 instead of the latest release.
- Run bitcoin core with the flag -server. bitcoin-qt -server
- Change the configuration of armory to disable the option "let armory manage bitcoin core".

Thanks goatpig

I did a "rebuild" and now when I click on the "send bitcoin" button, the window to send bitcoins appears as it should be.

Problem solved.

Try to rescan the db.

They way I used to run armory was
1) bitcoin-qt -server
2) armory

Then I realized that there is an option in the configuration for armory to run bitcoin core. And that option was checked. That's why amory complained

  I told armory where my bitcoin binary is and let armory run bitcoin. Now everything runs smoother. Before I was running bitcoin core myself and also telling armory to run bitcoin core and the computer was very sluggish for some reason. Now it's much faster.

But I think I broke something in the process as I cannot send bitcoin now.


So I am thinking about looking into the factory reset options...

Wow, thanks for the whole explanation. I realize how armory has to constantly evolve to adapt to the changes of core. Now I use

It's not much related to the PC's performance. Armory's p2p broadcast code was implemented when Core would push transactions as is once delivered by another peer. Core batches now, so the broadcast detection throws a lot of false negatives. This needs a bit of a technical explanation to make sense:

Early days, before Core was even named Core, the Bitcoin node software did 2 things different: Setting up the JSON-RPC interface required some minor work on the user part, notably adding login and password to a config file. Therefor, Armory could not expect access to the RPC in plug and play setups (95% of users), so it had to rely on something else to broadcast transactions. The RPC returns with an ACK/nACK on broadcasts but if only 5% of users can set it up properly, it was useless to Armory.

Instead etotheipi (the original maintainer) opted to connect to Core through the P2P interface. Armory, still to this day, spoofs a P2P node to your Core instance, for the purpose of pushing transactions and getting new block notifications.

The P2P broadcast interface does not come with an explicit ACK/nACK. It doesn't provide a result at all as a matter of fact, for design reasons. The flow goes like this: advertise the hash of the transaction you want to broadcast to the peer. The peer will then request that transaction by hash. You will return the transaction body to the peer. Broadcast is over. The only way to know if that transaction made it into the peer's mempool is to query that peer for the same transaction. If it returns it to you, it's in. You won't get a reply otherwise.

So basically, Armory sends the transaction to your Core instance and polls it for a few seconds to verify it's been added to the mempool. Eventually core introduced broadcast batching, where it tries to make a better use of the MTU and reduce point of origin timing leaks. Basically your node will now wait some time and try to accumulate a bunch of transactions before announcing them to other peers. This delay also affects entry in the mempool (so that you can't just query the node for specific hashes to know what made it in or not with certainty). As a result, this disrupts the Armory P2P broadcast loop, since the polling may now timeout.

Since then, interfacing with the RPC has become easier so I've added a RPC broadcast fallback when available, which is why you received the message about the RPC.

Ok. Perfect. Now I know what happened. Mine is a very old computer. That may explain the timeout.

Thanks for the explanation

Broadcast timeout doesn't mean the tx didn't make to the mempool, it only means Armory sent the tx to your node but failed to acknowledge delivery in the allotted time (hence the timeout). When that happens, it tries to fallback to the RPC interface to broadcast through that, but since yours isn't set up, you got that message.

I was trying on the main network.

And I didn't add the -server flag when I launched bitcoin-qt. Next time I will.

Thanks again, goatpig.

Did you try on the testnet? You have to run Core with -server to enable the RPC at any rate.

Now I get

Ok. I managed to create some transactions and they have been accepted and confirmed by the network.

The gcc 4.9 version does work. Now armory is scanning the global transaction history.

Well, my first attempt with armory gcc7.2 failed.

I will try with the gcc 4.9 version...

Thanks HCP for your input.


I am using an old computer with some 450 GBytes of HD. Fingers crossed that's enough.  I agree that a larger HD is needed. So far I downloaded 95% of the blockchain and used 75% of the HD. I haven't installed armory yet.

Don't forget you'll need room for the OS and applications etc... go 1TB+ if you can

I have tested it on ubuntu 18.04 LTS and it works OK.

Thanks goatpig

I plan to install armory on a dedicated computer. A laptop that is some 7 years old.

I will install ubuntu 18.04 lts

Your main road block is that Armory currently runs on python2 & pyqt4, and both py2 and Qt4 have been dropped from ubuntu starting version 20. You should read this thread for a decent work around:

https://bitcointalksearch.org/topic/bitcoin-armory-installation-on-mint-2004-5261375

Otherwise, the simplest path forward is to run Armory from within a Ubuntu 19 VM.

Hi everyone!

I want to run armory and I will post here my steps.

So far, I learned four things
- A system with some 400 Gbytes of HD is needed to store the blockchain.
- When downloading bitcoin core, use the tgz and not the snap. With the tgz, the blockchain files will be stored in the .bitcoin/blocks directory where armory looks for them.
- Disable bitcoin core pruning.
- Wait for bitcoin core to fully synchronize before launching armory.