CG: HCP123 ; FH: HCP123 ; Coin: BTC

A fantastic idea! I only just got all my gear setup again after a move and just prior to the government mandated lockdown here! Was looking at setting up WorldCommunityGrid again, but then the notification email for this thread arrived!

Just a heads up... my Razor came in the mail the other day, and I just have not had a chance to open it and/or test it due to trying to get myself and my partner setup with the government mandated lockdown due to Covid-19

Now that things have settled down, rest assured that I will make the effort over the coming days to do a full unboxing and initial impressions (with pics and some very short and likely bad quality video ) etc.

Thanks again to the BitPie crew for the review unit.

Have you tried Mycelium? That appears to have KeepKey support built in... but I've only ever used it with Ledger Nano S and Trezor ONE.

I was talking more about the transaction fees associated with sending BTC... I will admit I haven't looked in a while, but previously fees for transacting via ShapeShift were fairly high (and fixed) in comparison with being able to manually set fees in Electrum.

Things may have changed.

I don't think this is going to be possible and/or feasible from the Electrum console.

I think a better approach might be to see if it is possible to modify the Electrum source code and get it to start generating addresses from an index higher than 0. Possibly closer to the origin value of your order numbers. Perhaps ask on the Electrum GitHub issues page and see if the devs can assist? https://github.com/spesmilo/electrum/issues

The devs are fairly active and might be able to offer some guidance on a workaround.


In future, you'd be better off using the "account" value of the BIP32 derivation path to separate your stores, rather than such large address indexes.

Things that spring to mind:

1. "Gap Limit" issue... if the original accounts were setup using the Chrome App and NOT Ledger Live, it's possible the coins were sent to an address past the gap limit or even a change address (if selected from the drop down menu instead of using "receive" tab)

2. Valid but incorrect seed... there have been instances in the past where users have managed to get seeds confused and use a wallet for a while but have a seed written down that doesn't match that particular wallet. Not likely given OPs claim that this is their only wallet.

3. Multiple "Accounts" within Ledger... 1st account is currently empty, so Ledger Live might not see if coins were sent to "2nd" accounts. Could test using Electrum and specifying 2nd or subsequent accounts in derivation path (ie. m/49'/0'/1')

4. "Forked" accounts? I know that there were all sorts of crazy things happening when the BCH fork first happened with the "split" accounts in Ledger Chrome App... I'm not sure if Ledger Live still looks for these? Was the device originally configured/setup within Chrome App or Ledger Live?

That's due to the Chrome App being developed by the original KeepKey devs before the company was then sold to ShapeShift. ShapeShift then developed their web portal which kind of pushes users into registering and using ShapeShift and it's fees

However, as an existing Electrum user, you're in a good position to be able to leverage that as a frontend for your KeepKey so you get the benefits of all it has to offer with the added security of a Hardware Wallet.

I'm not sure why we're still going around and around on this

First and foremost, you need to get access to your seed backup and check it. Given the current state of the world, the closed borders, the lack of flight availability etc, I'm not even sure you're going to be able to achieve this in a timely fashion.

As for the device, have you actually emailed ledger yet? The sooner you do that, the sooner you'll get your answers regarding whether or not they'll even replace it, the process involved, shipping timeframes etc.

Asking random people on an internet forum about a specific company's specific processes is not going to yield the results you want. TALK TO THE COMPANY!

Not necessarily... unless you have explicitly installed the appropriate libraries, the Windows build will still complete "OK" (with errors that scroll past) and binaries will be built... but the libsecp256k1 stuff will be missing and you'll get errors when you try to run it... as per this post: https://bitcointalk.org/index.php?topic=5222986.msg53807327#msg53807327

If you have "libsecp256k1-dev" installed in Ubuntu (with apt-get)... and the python library "libsecp256k1" installed (with pip)... then the build-wine process will automatically compile the libsecp256k1-0.dll and roll it into your binary file. You can also find this compiled .dll and then copy it to a Windows machine and put it into your Electrum "source" folder to be able to run from source.

It seems something went wrong with the import into Electrum. If it is "watching-only", then you have not imported the private key, you have imported the public key. So, make sure you are copy/pasting the correct field from the Armory export.


These are my recommended settings when exporting from Armory to import the keys into Electrum:


Note that the "PrivBase58" will most likely start with a "5", it should have no spaces (use the "omit spaces" option as shown) and it should be 51 characters long.


You should be able to import this into Electrum using the "Import Bitcoin Address or private keys" option when creating a wallet:



And simply paste in the private key(s) that match the address(es) that you sent coins to:



This will create an "imported" wallet with the address(es) and you should be able to send:

I just banged it up on mediafire because it was the first (easy) filehosting that came to mind! It would seem it is freaking out about pyinstaller and blocking the file

In the meantime, I've added the same file to zippyshare for you: https://www92.zippyshare.com/v/qdHxapxK/file.html




Yeah, I went to all the effort previously with libsecp256k1... it's been compiled on my ubuntu VM, so is automatically included when building, so all the lightning stuff is working. I managed to open a couple of channels on Testnet and send some coins.




Yeah, I've tested it on Windows 10 running from source as well... so I've put the compiled ibsecp256k1-0.dll on zippyshare too: https://www92.zippyshare.com/v/CucF6mf9/file.html

Let me know if it works ok!

I'm a bit confused by your explanation.

So to clarify, you are saying that if you use the coworkers wallet.dat as the ONLY wallet.dat it works OK? But if you try and use multiwallet functionality then Bitcoin Core crashes?

Or are you saying that it starts ok with "default_wallet" and "co-worker wallet.dat" files in the data directory, but when you try to switch it crashes?

Just checked in after a few weeks "in the wilderness" due to moving from one end of the country to the other... and then a govt enforced coronavirus lockdown... and was like "shit! I hope I wasn't the guy holding it up!".

Thankfully... I was not!

I have compiled and uploaded a snapshot of 4.0.0a0 as at 30th March 2020... It is available here: http://www.mediafire.com/file/50jvn15ysgj8qsd/electrum-3.3.8-1845-g79d57784c-portable.exe

Ignore the filename, it's just a quirk of the build system as discussed earlier in this thread.

As always, Use at your own risk. I accept no responsibility if something goes wrong and you lose coins... TestNet is there for a reason!





Seems my channels got closed while I've been offline due to moving etc

I think you might be searching for the wrong package. The package name is openssl... that is an "L" NOT an "i" or a "1"...

Jaxx supports BIP39 mnemonics does it not?

Simply importing the 12 word backup phrase into Electrum using the "I already have a seed" and "BIP39 seed" options when creating a wallet in Electrum should be enough to clone the Jaxx wallet.

Once you have it in Electrum, it would enable you to send to "bc1" (aka bech32) addresses.

Get your Jaxx Liberty Backup Phrase if you don't already have it: https://support.decentral.ca/hc/en-us/articles/360006407953-How-to-see-your-Backup-Phrase-in-Jaxx-Liberty


In Electrum, select "File -> New/Restore", then enter a new name like "Jaxx_Clone" and click "Next":



Then select "Standard Wallet" and click "Next":



Then select "I already have a seed" and click "Next":



On the next screen, click "Options" and make sure that "BIP39 seed" is checked:



Then enter your Jaxx backup seed and click next, NOTE: it should say 'BIP39 (checksum: ok)':



Make sure you select "Legacy (p2pkh)" and that the derivation path at the bottom says: m/44'/0'/0' (it should say this by default when you click legacy) and then click "next":



Create a password and click next and your wallet will be created with the same addresses as Jaxx Liberty and you should see all your coins/transactions/balance:

Did you check the Bitcoin Core debug.log file to see what the actual error was?

The debug.log file is in the Bitcoin Core data directory (same place as the wallet.dat file). Without the error details from that file, no one will be able to assist

How exactly are you attempting to "switch" wallets?

The easiest method is to shut down Bitcoin Core. Once it is completely closed, then copy/move the current wallet.dat from the Bitcoin data directory. Then copy your "co-workers wallet.dat" into the Bitcoin Core data directory and overwrite the existing wallet.dat or, if necessary, rename it to wallet.dat.

Then restart Bitcoin Core. If it starts up it'll probably want to rescan to get the wallet up to date with current blocks etc. At the end of that process you will have a better idea if the wallet contains anything.

If it doesn't start up, either report what the error message shown is, or you can check the debug.log file for the errors... although chances are if it doesn't start up with the "co-workers wallet.dat" it is most likely not a Bitcoin Core wallet.dat or it is corrupted.

And in case it wasn't already obvious and well known... DO NOT USE BRAINWALLETS!

There have been countless examples of people losing bitcoins from bruteforced brainwallets. No matter how "random" you think your brainwallet phrase is... eg. lines from obscure poems, all the street names you've ever lived on in reverse chronological order etc... it isn't.

They're a "bad idea"™

Stick with properly randomly generated seeds and/or private keys.

NeuroticFish is correct... walletnotify should trigger twice for each transaction... once on initial receipt of (unconfirmed) transaction and once when the transaction gets it's first confirmation.

If you're getting the 1st update, but not the 2nd "in your shop", then most likely your code at the shop end is to blame. You can check that walletnotify itself is working correctly by simply using a simple shell script that just appends to a local text file... check to see that you're getting each transactionID twice.

This example from an old thread should work quite well:

Once you have confirmed that it is indeed triggering twice, you'll just need to try and find out where the break in your chain is... I'd guess in the processing on the server of the "http://myoniondomainname.onion/transactions/btc" call.