Getting electron unstuck from synching.

[Bigpiggy01]

I'm trying to figure out the max possible number of private keys into electron to claim BCC.
I dumped 3 old qt wallets (yes, I know that's an absurd number of addresses) with a fair amount of dust and imported them and have had electron stuck synching for 4 days now. Restarting it seems to kick it briefly but then it freezes again. To be fair some of those wallets are very old with a fairly long history.

I also tried on another box with just the keys from a single wallet and the process is identical

In both cases, I am connected to 10 nodes.

[jackg]

I'm trying to figure out the max possible number of private keys into electron to claim BCC.
I dumped 3 old qt wallets (yes, I know that's an absurd number of addresses) with a fair amount of dust and imported them and have had electron stuck synching for 4 days now. Restarting it seems to kick it briefly but then it freezes again. To be fair some of those wallets are very old with a fairly long history.

I also tried on another box with just the keys from a single wallet and the process is identical

In both cases, I am connected to 10 nodes.

You're probably better off trying it with say 20 private keys just to check there isn't an issue with the server on electrum.
Then take batches of 20-100 private keys until all all your coins have been redeemed.

In your network settings you could try changing the node you're connecting to also and switch to have it connect to a different peer as it can only connect to one at a time.

You might be able to sweep the keys instead which might speed it up but will cost you in transaction fees.

[Bigpiggy01]

I've swapped around several nodes and it doesn't seem to help.

As to batches of 20-100 that'd take ages but these bigger batches completely break exodus and coinomi, so I'm impressed that electron can actually handle some of it. I guess I might actually have to give it a go though 

Sweeping keys might be an option if I can figure out how to control the fees on it as it doesn't seem to be immediately available.

[mocacinno]

I've had the same problem in the past... Importing more than 50 private keys at once wouldn't work. I finally just install core, imported the private keys in a loop with the extra "False" argument to avoid a rescan, then i just restarted core with a forced rescan, and i was able to use the unspent outputs of hundreds of addresses within a couple of hours scanning.

As far as i know, it has nothing to do with the nodes you're connected to, and it's not a new problem, so i guess your best bet would be to use a workaround.

[Bigpiggy01]

Thanks, I'll give that a go with the ABC client. I was trying to avoid having that on any of my machines but c'est la vie.

For btc I'd just dump it all into core and it'll handle it just fine but given the current network fees, my dust can sit comfortably where it is till LN is operational. Archiving stuff back when you could spend coins with over 120 confirmations for free then "forgetting" about it wasn't the world's brightest move 

[jackg]

Thanks, I'll give that a go with the ABC client. I was trying to avoid having that on any of my machines but c'est la vie.

For btc I'd just dump it all into core and it'll handle it just fine but given the current network fees, my dust can sit comfortably where it is till LN is operational. Archiving stuff back when you could spend coins with over 120 confirmations for free then "forgetting" about it wasn't the world's brightest move 

I think that's probably the best option to use the ABC client, try to run it on a VM or a computer without core as it tends to overwrite the blockchain of bitcoin core

[Bigpiggy01]

Thanks, I'll give that a go with the ABC client. I was trying to avoid having that on any of my machines but c'est la vie.

For btc I'd just dump it all into core and it'll handle it just fine but given the current network fees, my dust can sit comfortably where it is till LN is operational. Archiving stuff back when you could spend coins with over 120 confirmations for free then "forgetting" about it wasn't the world's brightest move 

I think that's probably the best option to use the ABC client, try to run it on a VM or a computer without core as it tends to overwrite the blockchain of bitcoin core

YIKES! Thanks for the heads up, I've got a couple of spare boxes so that shouldn't be too big of an issue. Core going down would be.....

[HCP]

You don't need to run it on a different machine, just be careful when running the installer and make sure that you change the "Program Files\Bitcoin" path to something unique like "Program Files\BitcoinABC"... And then when you run it for the first time, set a "custom" data directory and again, change the "Bitcoin" part to "BitcoinABC"

I've had the two wallets running side by side without issue since the fork... But then, I don't just click-click-click through installers since the vast majority of them started including "helper" apps and browser toolbars etc

[Bigpiggy01]

You don't need to run it on a different machine, just be careful when running the installer and make sure that you change the "Program Files\Bitcoin" path to something unique like "Program Files\BitcoinABC"... And then when you run it for the first time, set a "custom" data directory and again, change the "Bitcoin" part to "BitcoinABC"

I've had the two wallets running side by side without issue since the fork... But then, I don't just click-click-click through installers since the vast majority of them started including "helper" apps and browser toolbars etc

Oh well, that's hardly alarming. 

I cut the addresses down to batches of 30 and they synched up within 10min. Still an awful lot of pasting keys