Post the new logs, post dbLog.txt too

That's the one.

Update to 0.96.4 RC1 and try again.

Show me your armorylog.txt

You need to update to 0.96.4 RC1 to be able to use Core 0.15.1. You can broadcast manually, that doesn't matter in the long term.

In Armory, right click the transaction and pick "Bump Fee".

Your notebook should not have private keys on it.

You have to go through this step to preserve the security model of Bitcoin to begin with. I'm not pulling these recommendations out of nowhere.

Or get on their slack and ask them to point you at the changesets. I'm not going there. They didn't bother extending me an invite, I'm not gonna bother getting one.

Yeah so Ima have to get on their slack and ask directly or read their code? Already deterred =D

Do they have documentation on their replay and wipeout protection?

Valuation is abysmal atm. I don't know what has to be done to support BTG, someone would have to point me at their repo/docs. I'm really taking this from the perspective of lowest effort possible atm, as these forks are more likely to ruins users' privacy than to actually net them anything. Not that I am indulging in hand holding, but don't expect me to spend significant time on this currently. Aren't they still in premine anyways?

Post your armorylog.txt for review.

I've been slacking on that, I'll deal with it at some point.

Update:

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

Proper process, wrong key.

Armory does not try to connect to anything but localhost. Only Core creates sockets over the WAN.

It's been a mess, can't be helped. That page belongs to the previous maintainer that shutdown in 2015. They sometimes mirror my release on their page still.


https://btcarmory.com/docs/verify

Not to mention P2PKH is still the default script type for Armory. It requires user intervention to generate a nested address (to my great dismay, I'd rather set compressed key addresses by default or SW for everyone's benefit, but I have to account for backwards compatibility).

Again, handling private keys is for expert users. The software shows you your private keys just fine. Instantiating these keys into the relevant script is the responsibility of the recipient software. If they don't support Armory script types, then you have to fill that gap or I have to do it for you. I won't do it cause that's a waste of my time. Therefor it's on you.

You are somehow trying to fly a chopper with no expertize and complain that the manufacturer should have informed you that starting the engine doesn't automatically take you to your destination. I am not in the business of holding hands. As a matter of fact I'm in no business at all since you got this stuff for free. Now learn about bitcoin transactions or forsake your BTG. I don't care either way.

But please, try and demonstrate how it is my responsibility to deliver this feature on my own time and dime because you can't be fucked to spend the 2 days it takes to learn about crafting raw transactions.