Very cool.  Thanks for the link.

UPDATE: I think I found the issue...  a tail of the exported log file under /root/.armory/ had

-ERROR - ...DB version mismatch. Use another dbdir!

According to google this seems to be due to having moved past the version 0.95 level from an earlier version.  As per someone else's experience with this I renamed the .../databases folder out of the way and on the next start Armory seems to be making headway.  I don't know if this is documented somewhere, but I didn't happen to see it...perhaps it would be better for the Armory startup to simply rename incompatible db folders out of the way itself and rebuild when necessary instead of having the interface silently failing with no apparent reason...?

Hello all...  I'm creating an offline Ubuntu 16.04 machine with just bitcoin-qt installed.  My intention is to get a running Bitcoin Core client going on the machine and then remove the network interface and never connect it again to any network.  Then I want to generate BTC addresses and private keys on that offline machine just for saving BTC to those addresses.

Question: If on this offline machine I make (for instance) two addresses with their private keys in bitcoin-qt and only use one for funding BTC amounts and the other for funding BCC amounts will there be any problem accessing/spending the BCC at a later time by simply importing the corresponding private BCC key into (for example) a Bitcoin ABC wallet on an online machine.  In a nutshell I guess I'm wondering if the addresses/private keys are compatible across the two networks so a private key and its address can be used without issue with BOTH BTC AND BCC regardless if its created in the first place with a BTC Bitcoin Core or a BCC Bitcoin Core.

I probably did not ask that well, but I hope my point is understood.

As a follow-up to this...if the address/key pairs will work fine on either network, am I correct in assuming that I could import the keys into any offline wallet of BTC or BCC in the future to do offline signing of transactions?

thank you!!!!!

Hi Everyone...  I don't want to keep nagging about this, but I still cannot access my Amory wallet -- not since the segwit thing!  I've done all the steps to build successfully as I've indicated above, but Armory just sits forever on Preparing Databases and Scan Transaction History without making any headway.

It would be most useful to be able to get at my bitcoins...

Please help someone if you've seen this before.

Actually, I think I spoke too soon...  Armory's been sitting with no progress on Preparing Databases and Scan Transaction History progress indicators for over 12 hours!

That can't be right...does anyone know if this is a known issue?  Thx!!

Thanks mate, that did it.
 
(My problem was that I was following the build steps at https://github.com/goatpig/BitcoinArmory/blob/master/linuxbuild/Linux_build_notes.md which seem to be missing pretty much all those other steps...)

It's up and running now.   

I'm running Ubuntu 16.04.  The debs will not install (my GCC version does not match either) and the build steps just simply fail.  I'm probably missing something here...

All this as root:

git clone https://github.com/goatpig/BitcoinArmory.git
cd BitcoinArmory
git checkout v0.96.2
git tag -v v0.96.2
make

On make I get:

make: *** No targets specified and no makefile found.  Stop.

On the git tag command I get:

object 95dc55907f26cf79fdec7f8efa4228f7efd696cc
type commit
tag v0.96.2
tagger goatpig <moothecowlord@gmail.com> 1504047291 +0200

v0.96.2
gpg: Signature made Tue 29 Aug 2017 04:54:51 PM MDT using RSA key ID 4922589A
gpg: Can't check signature: public key not found
error: could not verify the tag 'v0.96.2'

(Previously I tried to add a key in Kleopatra but that didn't seem to help...)

Any ideas?  Can't access my bitcoin since segwit.   

Thanks.  I was on that mining thread yesterday and didn't find it all that illuminating regarding my above post...  I suppose I could have posted there.  Should I cross post or delete and repost?

I hope this is considered "on topic".  I've been mining Eth/Etc/Sia for the past few months.  Currently I'm mining Eth/Sia at around 1.5 Eth/day and 6000 Sia/day.  Sia pretty much pays for the power, so the $20 (CAD) per day with my nine GPUs is doing well enough.

Came across info the other day on Xmr for the first time -- the principles of design intrigue me and if it were reasonably profitable it would potentially be something I would mine a little more seriously.  So yesterday for a simple trial I set up the minergate GUI and also the minergate CLI and found that the performance was fairly poor on the mining rigs, and it was hitting the GPU performance of the Claymore dual mining (naturally enough, that was not unexpected.)  So I've been running it CPU-only on a couple or three boxes off and on for the past 24 hours and I've found the hashrate of around 130 h/s to be very low and probably is not even paying for the additional power consumption on the CPUs.

So my question is general: Is there a way to GPU/CPU mine this coin in a way that is profitable, or at least relatively profitable as compared to Eth and Etc?  What kind of hashrate would I need to do about $15-$20 USD per day?  To achieve that kind of hashrate, what kind of hardware would be recommended and what kind of power consumption would a person be looking at?  I know these are general questions, but I'm curious what miners are doing with this coin -- how they are setting up to make it profitable...?

Thank you so much if anyone can answer or point me in the direction of materials that might answer these questions.

If I wanted to be taken advantage of by an interest-yielding scheme masquerading as PoS-tech I'd just keep fiat in the bank.

No thanks, ETH can have their PoS...  I'll mine ETC.

CoinPool.biz is working for me...  about 42 hours mining at around 230 MH and 17.6 ETC paid.

I could make about 20% more equivalent value mining ETH on my old pool, but for now I want to support ETC cause it's not in bed with the beast.

Hi folks,

FYI, after pointing 230 MH at ETC on the Suprnova pool for 24 hours and then also on the CoinPool pool for 24 hours, I think I prefer this little pool at CoinPool.  That said, we should get a little more hashing to join us to keep things flowing more consistently.  Say about 2-3 GH?  That would be a nice number from my perspective...  Anyway, I should mention that the performance issues I saw with my Claymore minors on Suprnova could have been due to non-optimal config.

To help, this is how I'm configured on CoinPool and SiaMining.  I'm getting expected hash rates from Claymore on both ETC and SIA:


ClaymoreConfig.txt:

; CLAYMORE DUAL MINER SET-UP FOR Eth Classic on CoinPool:
-epool etc.coinpool.biz:7887
-ewal 0x14624e2889B165b2b459D48e3c7BA3dC75bD1E10
-eworker RigName
-epsw x
-esm 0
-allcoins 1
-erate 0
# CLAYMORE DUAL MINER SET-UP FOR SiaCoin on SiaMining:
-mode 0
-dpool http://siamining.com:9980/miner/header?address=d8573b70ee4fc60bff69489d7879f481262ce8cb22ca93cb9aee9fb7cc4ab89d871e9c7d5bfd&worker=RigName
-dcoin sia


ClaymoreMining.bat:

EthDcrMiner64.exe ClaymoreConfig.txt


Watch your temps as Claymore squeezes every last drop of processing out of your GPUs...

Of couse, you'll want to adjust for your own accounts and rig names.

Although you can feel free to test the above and tip me for the help if you want...