Extract the content of that folder. In the terminal, cd to that folder, then type:

No, this stuff only acts as a proxy to interface the python wallets with the new signer. It does not touch private assets. What you want is for 0.97.

Try that for now.

Are you using DB_BARE?

Droark is out of town atm. Wait for him to get back or search the forums.


You can extract your private keys at any moment in time. Stop throwing a tantrum, the only thing this achieves is deterring potential helpers, me included.

For the new wallets, not the legacy stuff.

Will probably just be one for 0.96.3

OSX, figures. There's some inane manipulation you have to perform so that OSX allows you to run the code in the first place. Some sort of newly introduced security feature or what not. Ask the OSX users in here, I wouldn't touch this system with a 10 foot pole.

Your question was akin to: "do you vouch for this code?". No I don't, nor do I want the responsibility. Also, ABC devs went out of their way to obfuscate their changeset. This is like a manufacturer advertising that you shouldn't trust their product. Alright then, I won't.


I do not believe these developers are malevolent. I certainly think they are incompetent. Whether you get screwed intentionally or by negligence, the end result is the same.

These guys are defunct.


You're using a year old piece of software. Update.

https://github.com/goatpig/BitcoinArmory/releases

If you're still having issues, post your logs.

You run your node and DB on the VPS, put it behind a HTTP daemon and point the client at that IP:port. For better security, you can VPN the client in (since the socket layer between client and server is not encrypted atm).

Yes


lol no

1) I sync'ed a BCH node.

Blockchair uses SSL, but I don't know if they have a send API. One thing you need to know if you're going to push through a 3rd party: Armory RBF flags by default, and RBF is disabled on the BCH chain. This doesn't mean RBF flagged transactions are invalid on the BCH chain, but that second RBF won't be broadcasted (first RBF flags potential replacement, second RBF is replacement). However, people have reported 3rd party chain explorers won't broadcast RBF flagged tx on BCH, therefor I suspect they went for the idiot patch and reject anything sequence flagged as a whole (how do they deal with OP_CSV?).

2) Last I checked, you could get first block inclusion with as low as 20 sat/B atm. I expect it's cheaper now

3) Pick all the eligible utxos in the coin control UI (don't bother if you want to move the whole wallet balance), then check the "MAX" box and pick a sat/B fee (force a flat fee).

That's a false positive. Describe the issue and post your dblog as well.

Armory does not use the rev files. Remove whatever amount of files you need to roll back the chain in a state where all your post fork coins are unspent.


https://btcarmory.com/docs/pathing


Using the "trick", you will know how much BCH you have in total, but since you can't use Armory to broadcast (you are not running an actual BCH node), Armory can't track which outputs you've spent on the BCH chain. If you dump in several transaction, you need to keep track of which utxos are still available.

Look for the Bitcoin ABC repo, or the variants of Classic/Unlimited that support BCH.

As for the setup, read the sticky: https://bitcointalk.org/index.php?topic=2070058.0

It can work on these CPUs but you will have to either use Windows or build with that machine on Linux. My builds aren't compatible with stuff that old atm.

How old is your CPU?

Any idea what triggered it? Any hint can help.

Update.