Ah indeed, the signer and online instance need to be in lockstep.

I guess start it here and link it on whatever forum/subreddit the BTG crowd hangs in.

Top sticky thread.

Do you have an error log for that last part?

Ah, I misread, I thought you were using a shortcut. Now I just realized you are using 0.96.3. Update to RC1.

You'd want to do that on the binaries you built from source.

Yeah, definitely. It's mostly a matter of schedule and effort.


I would rather you put together a bounty for someone to do the work so that I just have to review a PR. I don't need your money, I'd be getting an airdrop as well if I was to implement BTG support.


I'm a solo act and can't afford to support every fork under the sky under the guise of airdropped $$$. The airdrop part is a dangerous enough precedent as it is. Unless these forks demonstrate some form of resilience, I won't be looking at them.

Not to mention that the effort to support BTG is like 3x that of BCH and this falls at a bad time on my schedule too. At any rate, I can't deal with BTG until my new SSD is delivered, as I'm out of free space (too many copies of the blockchain =O)

Like create transactions and broadcast through the command line?

it's --satoshi-datadir. You're missing the dashes.

Do you have a Core installation and the blockchain synced?

Just use the noasm builds. If you're looking to update, you'll need a stronger CPU anyways (seeing you're going online with this machine), blockchain ain't getting smaller! But I digress. Generally, laptop CPUs have much less silicon to save on power, so only mid-high end laptop CPUs will have all the good stuff. Desktop CPUs are different, basically any i3 from 2010 will have all that you need.


You can 'sudo make install' after building from source.

Update Armory.

No, post it on pastebin

Update Armory and delete your database folder.

Post armorylog.txt

It's more than just SSE4, there's also pclmul and AES. Also washed down iteration, such as SSE4.a won't cut it.


What is an "uncompiled" version? The fix to this is to build yourself from source, or use the noasm .deb (https://github.com/goatpig/BitcoinArmory/releases/download/v0.96.3.99/armory_0.96.3.99-gcc4.7-noasm_amd64.deb)


This means you need to delete .lmdb mirror wallets in your Armory datadir.

Put the call in a try block and print the error message. Something like this:


Btw this traceback is for code from master (0.96.3). Have you reproduced the same issue with the testing branch?

It is but I've had other stuff thrown on my lap these past couple days which need my immediate attention. So, no guarantees.

Yes.

It's suggesting your DB is corrupt.