Using Armory on the BCH chain - page 7.

justmyname

sr. member

Activity: 389

Merit: 250

Quote from: Holliday on April 22, 2018, 02:17:18 PM

Quote from: alomar on April 22, 2018, 01:58:20 PM

i've heard goatpig is a hard core fundamentalist when it comes to BTC so don't be surprised if you don't get your wish. good luck

I would certainly prefer goatpig work on Bitcoin features and keeping the wallet up to date with the Bitcoin ecosystem, along with bug fixes and general improvements, as opposed to wasting time adding support for every forked shitcoin that someone dreams up. Armory is a Bitcoin wallet, after all.

Besides, one is able to access their forked shitcoins with other methods if so desired.

BCH shitcoin is worth $1,239.39 each. Not much to you maybe. But I can sell them without touching the Bitcoin if I choose. I'll continue to take those shit coins.

I could export the keys somehow and get the coins that way. It might be interesting to learn how to do it.

Holliday

legendary

Activity: 1120

Merit: 1009

Quote from: alomar on April 22, 2018, 01:58:20 PM

i've heard goatpig is a hard core fundamentalist when it comes to BTC so don't be surprised if you don't get your wish. good luck

I would certainly prefer goatpig work on Bitcoin features and keeping the wallet up to date with the Bitcoin ecosystem, along with bug fixes and general improvements, as opposed to wasting time adding support for every forked shitcoin that someone dreams up. Armory is a Bitcoin wallet, after all.

Besides, one is able to access their forked shitcoins with other methods if so desired.

alomar

member

Activity: 178

Merit: 10

Quote from: justmyname on April 22, 2018, 01:19:01 PM

Quote from: alomar on April 21, 2018, 08:21:47 PM

Quote from: justmyname on April 21, 2018, 05:57:43 PM

As one other and Jojo69 suggested I used bitcoin-abc-0.16.1-win64. And it worked just fine.

Maybe not with your operating system.

there is an ABC hard fork coming up May 15 so you might want to get everything done before then.

So their forking BCH also. Interesting.

I moved my BTC and BCH coins off of Armory. Their is only one developer left and we still don't have a BTG signer available. These coins are worth a significant amount of money. Sort of like a stock split or dividend.

Hardware wallets have software to separate the significant coins. You can have many different types coins on them without downloading the blockchain.

you shouldn't necessarily concerned. ABC has made it clear from the beginning that they are planning hard forks q6mo as routine upgrades. i don't necessarily agree with that but i believe their intentions to be good. we'll see. i agree that we should be able to harvest altcoins but i'm sure you'll get some sort of response like code it yourself. i've heard goatpig is a hard core fundamentalist when it comes to BTC so don't be surprised if you don't get your wish. good luck

justmyname

sr. member

Activity: 389

Merit: 250

Quote from: alomar on April 21, 2018, 08:21:47 PM

Quote from: justmyname on April 21, 2018, 05:57:43 PM

As one other and Jojo69 suggested I used bitcoin-abc-0.16.1-win64. And it worked just fine.

Maybe not with your operating system.

there is an ABC hard fork coming up May 15 so you might want to get everything done before then.

So they're forking BCH also. Interesting.

I moved my BTC and BCH coins off of Armory. Their is only one developer left and we still don't have a BTG signer available. These coins are worth a significant amount of money. Sort of like a stock split or dividend.

Hardware wallets have software to separate the significant coins. You can have many different types coins on them without downloading the blockchain.

alomar

member

Activity: 178

Merit: 10

Quote from: justmyname on April 21, 2018, 05:57:43 PM

As one other and Jojo69 suggested I used bitcoin-abc-0.16.1-win64. And it worked just fine.

Maybe not with your operating system.

there is an ABC hard fork coming up May 15 so you might want to get everything done before then.

justmyname

sr. member

Activity: 389

Merit: 250

As one other and Jojo69 suggested I used bitcoin-abc-0.16.1-win64. And it worked just fine.

Maybe not with your operating system.

alomar

member

Activity: 178

Merit: 10

Quote from: goatpig on April 21, 2018, 11:08:49 AM

A few months after the first BCH release, I believe ABC changed magic word and port. This is why Armory cannot work with these nodes. Changing the node port is easy, as there's a command line argument in the DB for this purpose. However, magic words are hardcoded.

You'd have to modify the Armory source to use this other magic word only for the node then build yourself to get it to work with newer ABC versions.

i suspected this was the problem all along.

goatpig

legendary

Activity: 3640

Merit: 1345

Armory Developer

A few months after the first BCH release, I believe ABC changed magic word and port. This is why Armory cannot work with these nodes. Changing the node port is easy, as there's a command line argument in the DB for this purpose. However, magic words are hardcoded.

You'd have to modify the Armory source to use this other magic word only for the node then build yourself to get it to work with newer ABC versions.

alomar

member

Activity: 178

Merit: 10

@HCP and @justmyname

this post here suggests the newer versions of ABC won't work with Armory. what versions have you been successful in getting to work with Armory?

https://bitcointalksearch.org/topic/m.35175889

alomar

member

Activity: 178

Merit: 10

Quote from: HCP on April 20, 2018, 04:00:07 AM

Quote from: alomar on April 19, 2018, 10:22:30 AM

i'm launching bitcoind different ways; either directly in CLI with "bitcoind" first, then launching Armory or launching bitcoind via letting Armory do it. either way Node Offline. bitcoind by itself will update when launched alone as assessed by "bitcoin-cli getblockcount". like i said, my other instance of a VM based BTC blockchain works just fine on my other computer that doesn't have another blockchain on the host. so i know this setup runs inside a VM just fine. that setup also does NOT have a bitcoin.conf file. i also read somewhere that bitcoin.conf is not necessary.

It's not strictly necessary to have a bitcoin.conf file... but it's possible that things are not working correctly without the appropriate runtime arguments being passed to the daemon (like "server").

Quote

as an aside, when i start up Armory with either bitcoind started by itself first or by letting Armory control it, the block count at bottom right in Armory shows the updated correct number. it just won't advance beyond that both in the GUI and in the terminal (stuck at "BDM ready!").

That's very similar to the issue I have on Windows 10 when I don't user -server and -listen parameters... it will sync up to whatever block bitcoind has at the time it starts, but doesn't seem to get new blocks Undecided

would you be willing to share the entire contents of your bitcoin.conf? like i said, i tried listing both server=1 and listen=1 as well as dummy rpcuser and rpcpassword parameters without success.

HCP

legendary

Activity: 2086

Merit: 4314

Quote from: alomar on April 19, 2018, 10:22:30 AM

i'm launching bitcoind different ways; either directly in CLI with "bitcoind" first, then launching Armory or launching bitcoind via letting Armory do it. either way Node Offline. bitcoind by itself will update when launched alone as assessed by "bitcoin-cli getblockcount". like i said, my other instance of a VM based BTC blockchain works just fine on my other computer that doesn't have another blockchain on the host. so i know this setup runs inside a VM just fine. that setup also does NOT have a bitcoin.conf file. i also read somewhere that bitcoin.conf is not necessary.

It's not strictly necessary to have a bitcoin.conf file... but it's possible that things are not working correctly without the appropriate runtime arguments being passed to the daemon (like "server").

Quote

as an aside, when i start up Armory with either bitcoind started by itself first or by letting Armory control it, the block count at bottom right in Armory shows the updated correct number. it just won't advance beyond that both in the GUI and in the terminal (stuck at "BDM ready!").

That's very similar to the issue I have on Windows 10 when I don't user -server and -listen parameters... it will sync up to whatever block bitcoind has at the time it starts, but doesn't seem to get new blocks Undecided

alomar

member

Activity: 178

Merit: 10

Quote from: HCP on April 19, 2018, 04:49:53 AM

Quote from: alomar on April 18, 2018, 11:18:56 AM

looking inside .bitcoin, the only differences i see btwn the contents of this BCH blockchain and my currently working BTC blockchain, both inside Ubuntu VM's on different machines, are two additional files inside the BTC blockchain; .cookie and bitcoind.pid. anyone recognize those two and what they are? are they critical to getting this Node Online?

@HCP: there is no bitcoin.conf inside my working .bitcoin directory on my BTC blockchain.

How do you launch the BTC "bitcoind"? Huh

Are you using any commandline parameters?

The .cookie file is used for RPC Authentication... without it, you probably won't be able to connect to bitcoind via RPC. You might want to check some of the commandline options as specified here: https://en.bitcoin.it/wiki/Running_Bitcoin

I would think that, at the very least, -server would be required so that it accepts the RPC commands. It's also possible you're running into some weird behaviour with them in VMs relating to ports and networking...

i'm launching bitcoind different ways; either directly in CLI with "bitcoind" first, then launching Armory or launching bitcoind via letting Armory do it. either way Node Offline. bitcoind by itself will update when launched alone as assessed by "bitcoin-cli getblockcount". like i said, my other instance of a VM based BTC blockchain works just fine on my other computer that doesn't have another blockchain on the host. so i know this setup runs inside a VM just fine. that setup also does NOT have a bitcoin.conf file. i also read somewhere that bitcoin.conf is not necessary. this problematic computer does have the BTC blockchain on the host (which i don't run simultaneously of course). i don't see how that could be interfering with BCH client communicating with Armory in the VM however.

as an aside, when i start up Armory with either bitcoind started by itself first or by letting Armory control it, the block count at bottom right in Armory shows the updated correct number. it just won't advance beyond that both in the GUI and in the terminal (stuck at "BDM ready!").

HCP

legendary

Activity: 2086

Merit: 4314

Quote from: alomar on April 18, 2018, 11:18:56 AM

looking inside .bitcoin, the only differences i see btwn the contents of this BCH blockchain and my currently working BTC blockchain, both inside Ubuntu VM's on different machines, are two additional files inside the BTC blockchain; .cookie and bitcoind.pid. anyone recognize those two and what they are? are they critical to getting this Node Online?

@HCP: there is no bitcoin.conf inside my working .bitcoin directory on my BTC blockchain.

How do you launch the BTC "bitcoind"? Huh

Are you using any commandline parameters?

The .cookie file is used for RPC Authentication... without it, you probably won't be able to connect to bitcoind via RPC. You might want to check some of the commandline options as specified here: https://en.bitcoin.it/wiki/Running_Bitcoin

I would think that, at the very least, -server would be required so that it accepts the RPC commands. It's also possible you're running into some weird behaviour with them in VMs relating to ports and networking...

justmyname

sr. member

Activity: 389

Merit: 250

Quote

looking inside .bitcoin, the only differences i see btwn the contents of this BCH blockchain and my currently working BTC blockchain, both inside Ubuntu VM's on different machines, are two additional files inside the BTC blockchain; .cookie and bitcoind.pid. anyone recognize those two and what they are? are they critical to getting this Node Online?

@HCP: there is no bitcoin.conf inside my working .bitcoin directory on my BTC blockchain.

You can google them. I googled them a long time ago. Don't remember what they are. I just wanted to make sure they weren't some type of spyware and found them to be safe...

If you have the old BTC folder and blockchain still on your computer that is likely the reason you're having trouble. You probably have to nuke everything and re-install the ABC wallet. If that doesn't fix it. Nuke and restore Armory.

justmyname

sr. member

Activity: 389

Merit: 250

Quote from: goatpig on December 21, 2017, 05:34:35 PM

Armory is not for altcoins. I provided a BCH signer so that people can get their coins out. I will provide a BTG signer to the same end. I made it pretty clear back in August that if BCH (or any other Bitcoin fork for that matter) was to introduce changes that made it incompatible with Armory, I would not support that stuff.

Bump. BTG signer yet? Grin

alomar

member

Activity: 178

Merit: 10

looking inside .bitcoin, the only differences i see btwn the contents of this BCH blockchain and my currently working BTC blockchain, both inside Ubuntu VM's on different machines, are two additional files inside the BTC blockchain; .cookie and bitcoind.pid. anyone recognize those two and what they are? are they critical to getting this Node Online?

@HCP: there is no bitcoin.conf inside my working .bitcoin directory on my BTC blockchain.

alomar

member

Activity: 178

Merit: 10

Quote from: HCP on April 17, 2018, 01:33:31 AM

Is your bitcoind installation configured to use:

Code:

listen=1
server=1

in the bitcoin.conf file? (or using -server=1 -listen=1 from the commandline?) Huh

In any case, you will probably need to post your logs for people to be able to troubleshoot further.

a bitcoin.conf file is not required. in any case, i did try adding it with those instructions but still Node Offline.

justmyname

sr. member

Activity: 389

Merit: 250

Quote from: alomar on April 17, 2018, 01:14:26 AM

successfully installed 0.96.4 but still get Node Offline error. bitcoind updating blocks just fine.

Somethings wrong with Armory then. As your ABC wallet is working. All I did was uncheck the box that says something like "Allow Armory to run Bitcoin-qt in the background". That fixed the offline node error. But I still had zero balance until I had Armory in the help menu "rescan and rebuild data base". Worst case scenario, you will have to restore your Armory wallets.

Another way to get the offline node error. Is to by accidentally, restore your offline wallet to your online machine with the paper backup. That had me spinning my wheels for a while.

HCP

legendary

Activity: 2086

Merit: 4314

Is your bitcoind installation configured to use:

Code:

listen=1
server=1

in the bitcoin.conf file? (or using -server=1 -listen=1 from the commandline?) Huh

In any case, you will probably need to post your logs for people to be able to troubleshoot further.

alomar

member

Activity: 178

Merit: 10

successfully installed 0.96.4 but still get Node Offline error. bitcoind updating blocks just fine.

Topic: Using Armory on the BCH chain - page 7. (Read 45958 times)