Hi guys,

Is there any foreseeable problems with usage of Armory 0.96.5 and the incoming Taproot soft-fork?

Thx

This usually works for me.

1. In Armory:   Help -> Rebuild and Rescan databases

2. Close Armory.

3. Open Windows Task Manager, make sure any Armory process is not lingering.  (ArmoryDB.exe tends to stay stuck)  Kill those.

4. Re-open Armory.  Wait for it to complete scan and rebuild.

If you still end up in an Offline state, repeat step 2 to 4 (close armory, kill ArmoryDB, re-open armory).   I usually get armory back online after 1-2 tries. 

You can also try to open bitcoin core directly when armory is closed (between step 3 & 4), wait for it to sync and close it properly.


That said, it should not happen if you closed Armory correctly.  I end up in this state only if windows crashed or decided to reboot for an update without prior notice...

I also wish we can see an update to Armory sooner or later.  I've been sticking with this wallet since I started dealing BTC in early 2013.   It would be nice to continue using it on the long term.

Thx for your input guys.   I'll experiment with the different avenues. 

If I want to deal with armoryd, that would mean I need to run a full bitcoind node on the server right?  If so I would rather avoid it. 

Hello,

I would like to implement some payment system, where I would generate a unique address for each transaction/user.   My website runs on php 7.3.

I found some examples using bitwasp library.  But am unsure what would be the best approach to implement this.

- Should I provide a wallet private key to bitwasp to generate my addresses?   This example seems to take a private key fromWif ? (i dont know what this is)
https://github.com/Bit-Wasp/bitcoin-php/blob/9e535f04665ba22ba2b8b63f371ec50d2e7eabb8/examples/addresstypes.script.php#L16-18

 Then I guess the generated addresses would show up in Armory

- Is it possible to provide bitwasp with only my wallet public key to generate new addresses ? I would rather not leave my private key in some php file or in my database (even if it is secured).

- Should I generate a unique private key with bitwasp, use it to generate my addresses and then import it in Armory ?

- Should I generate a new private key and address for each new transaction and then import it in Armory ?

Some help on this would be appreciated.

Thx
Eric

Thanks a lot Claymore for this new release. I've been waiting hoping for it to be the magical hashing booster grail

Unfortunately, after trying all sorts of -h -dmem combination, I can't get higher rates that what sgminer is already giving.  Most of my rigs run 580 polaris cards.

I'll try again on your future releases. Keep up the good work

Of all my cards the XFX and PowerColor are the worst.  So no I would not recommend.   If I had to buy again I would stick with Sapphire and MSI in that order.

For the other question, to mine XMR/Cryptonote currency you don't need that much energy so a single 8 PIN connector is usually enough.

This does work on RX 5xx (mining XMR at least)  You just need to find the right settings to optimize your cards.

I also hope Claymore is gonna update this miner.   Having only RX 580 cards I'm having difficulty obtaining the same hashrates with gateless as it doesnt have any polaris aimed kernel.   I'm sure those cards can do much better.

Been running this driver for last 4 days.  Works like a charm.

1- At time of driver change,  had an extra 7% average boost on hashing speed.   Didn't have any change in power consumption like some are claiming (tested at the wall).

2- I'm almost entirely working with RX580 and some 570.  So I can't claim it works well for the 4xx series.

3- Last DAG epoch did NOT change anything on hashing speed.

Overall I'm really glad this fix has been provided here. 7% gain is huge not to mention it would have been worst on each epoch.  Unless a new official AMD driver is released and provide another increase in overall MH, I will probably stay with those for a while.

This does appear to work fine.    I dunno if AMD is gonna release an official driver with this fix or not, but in the mean time it looks like a viable solution.

I tried on 2 rigs, both with rx580.       Speed went back up from ~28.4 to my initial 30.55MH per card.

1- Make sure you update to claymore 9.8
2- OC and voltage control DO work with BETA version of MSI AB. (link in above post, msi afterburner 4.4.0 BETA 15 )
3- Make sure you apply atikmdag-patcher before system restart

Will deploy to my other rigs soon

Thank you.   

I do.

How I start ArmoryDB


Nginx configs


How I start ArmoryQt.exe

Exactly.

Linux running bitcoind and ArmoryDB.  With nginx configured for fastcgi_pass.

Windows 10 running only armory client.

Both on same subset. 10.10.10.0/24

ArmoryDB is working fine, with all provided paths.      Running armory client locally (same linux instance) or from another linux instance is working nicely.    Only from Windows client I get this error.

I'm getting the same error when trying to run Armory on Windows 10 x64, providing remote IP and PORT to a nginx setup of an ArmoryDB.

ArmoryQt.exe --armorydb-ip=10.10.10.26 --armorydb-port=9002



Running the same command on Linux is working fine.

Any clue what could be causing this?   

Thx