armorylog.txt

1) Install Bitcoin Core 0.15.0.1 and let it sync with the network (will take a week with your computer).

2) Update to Armory 0.96.4 RC1

While I understand your frustration, this is no place for politics, and I don't dab in those on this page either. As far as predictions go, they are basically an exercise in futility.

The nature of the fork is irrelevant. People who feel they need to dissociate should do so. Delaying the issue only builds up venom within the community. Bitcoin and cryptocurrencies by nature implement and purport the right to dissociate. It is expected such foundational precept will be used.

ETC set the precedent that a minority fork can survive. BCH demonstrated that a haphazard and poorly executed fork can also survive, despite how little regard the BCH devs have for the disruption their faulty design choices still inflicts upon users of both chains.

Naturally with B2X, we are set to further explore that rabbit hole that is the derelict of duty the forking party is guilty of by deliberately choosing the more harmful forking parameters. If B2X fails to fork, or does no wreck the havok it is set to, the one after that will.

This is the kind of situation that will get worse before it gets better. At the same time, the magnitude of the disturbance is irrelevant. Bitcoin is built to survive. If it fails, we will have to learn from the attack and improve upon it.


The only way they can guarantee this is by using post fork coinbase rewards. It could be a week before they have such an output for use. I wouldn't trust that claim.

Post your logs.

You can't use Core 0.15.0.1 with 0.96.3. Use 0.96.4 RC1

If there was a way to get rid of the auto github source, I'd like to know. It is still telling when someone grabs these files, tries to build and realize they don't work. Git submodules may be a blessing in disguise for these people, as they obviously did not check signatures on the tarball (there is none).

I've been pushing signed source since 0.96.2:

https://github.com/goatpig/BitcoinArmory/releases/download/v0.96.3.99/armory_0.96.3.99_src.tar.gz

That guy has no idea what he is doing therefor has no business building from a tarball. He should pull the signed tags and build from that. It is evident the github packaged source is useless: even if it carried the proper code (which it doesn't cause of git submodule shenanigans), the auto packaged source tarball IS NOT SIGNED. Github could shove anything they want in there. If he was checking sigs, he would have noticed that immediately.

Any coins you have in an Armory wallet pre fork will be available on both sides of the split post fork. You can spend as usual, knowing that any transaction you perform on one chain will be mirrored on the other chain. As an example, this means that post fork if you move 1 BTC to 3addressblahblah, 1 B2X will be moved to 3addressblahblah on the 2X chain as well.

This is because 2X has no replay protection. There's no sane explanation as to why this is the case, but that's besides the point. If you want to send your coins on one side of the split independently of the other, you will need to taint your coins first. This means you will have to move your coins to an output that only exists on one chain (remember, all your pre fork outputs are valid on both chains).

Tainting requires a set of operations that are time consuming but low risk. I'll have to write a guide about this at some point.

Core 0.15.0.1 does not work with 0.96.3. Use 0.96.4 RC1 or downgrade to Core 0.15

No that would be 0.96.4 RC1

I'm deleting the first post because this looks like obvious sig spamming. Also that guy is recommending blockchain.info, which is garbage. Don't use online services to hold your coins, and if you ever do, don't use bc.info!

You can't use 0.96.3 with Core 0.15.0.1. Use 0.96.4 RC1 or downgrade Core.

You are placing the sentence out of context in 2 instance. The question I was replying to was "can I import my private keys into another wallet to spend coins from". The reply is only those private keys hold coins under the aforementioned scripts types. You missed the context a second time when asking about how to check for script types in Armory. My reply was that this point is moot in anything pre 0.96, as Armory only ever used P2PKH prior to that release.

Your question is simply "can I use an old Armory wallet in the most recent release". The answer is obviously yes.

Mac is fine as long as you have enough technical background to get the package running or building from source. OSX is a bad platform for open source when compared with Linux and Windows. It is acutely worse when it comes to software that relies on old GUI library, like in Armory's case.

What I am recommending here is how I'd do it I had to use Armory on a Mac: build DB from source and run it on host (OSX) and run the client on a guest VM of some Linux distro (ideally Debian based, that's what I dev on).

0.93 is over 3 years old. Update.

As long as you have the private keys, you have the BCH, I don't understand where "lost forever" part is coming from.

If you didn't update to 0.96, you can't have any of these script types. If you did, you have to check on the online machine, through the address tree in the wallet properties dialog.

Link?

Turn off auto bitcoind in File -> Settings.