Author

Topic: Using Armory with a private blockchain (Read 437 times)

hero member
Activity: 503
Merit: 501
March 16, 2017, 07:50:50 PM
#3
Thanks for the quick reply!
staff
Activity: 3374
Merit: 6530
Just writing some code
March 16, 2017, 06:50:21 PM
#2
IIRC Armory does not do anything with checking the validity of the blocks it receives, it assumes that Core did that. Since Armory will only connect to the local Core client, it will accept whatever Core gives it. However, since it does use a p2p connection, it will be checking for the magic bytes, so if you change those in your private blockchain, you will have to change those in Armory as well.
hero member
Activity: 503
Merit: 501
March 16, 2017, 06:23:47 PM
#1
We have a private blockchain using the latest Bitcoin Core Linux client in house and have one node mining all by itself and would like to use Armory wallet for Windows multi-signature wallets on client machines.

If I understand correctly, for client machines we can install the appropriate Windows version of bitcoin core on the clients and as long as the bitcoin client is configured to connect only to the private blockchain that Armory will connect only to the private blockchain.

re: https://www.bitcoinarmory.com/troubleshooting/#how-can-i-change-the-blockchain-database-storage-location-for-armory-and-bitcoin-core

Be aware that Armory connects to Bitcoin Core or bitcoind as a regular peer, not through RPC. As such, the bitcoin.conf requires allowing incoming connections from 127.0.0.1. The following lines are example options in bitcoin.conf:

Is this a correct understanding or have I missed anything?
Jump to: