Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems starting an imported privkeys wallet from python code #8

Closed
XaviP opened this issue Jul 26, 2017 · 3 comments
Closed

Problems starting an imported privkeys wallet from python code #8

XaviP opened this issue Jul 26, 2017 · 3 comments

Comments

@XaviP
Copy link

XaviP commented Jul 26, 2017

We are starting electrumfair wallet from python code like this:

import electrumfair
c = electrumfair.SimpleConfig()
network = electrumfair.Network(c)
network.start()
storage = electrumfair.WalletStorage(wallet_path)
wallet = electrumfair.Wallet(storage)
wallet.start_threads(network)

This is currently working ok with wallet updated from seed, but we are facing problems with an imported privkeys wallet. From gui, the wallet seems ok (all addresses recognized), but when starting the wallet from python code, only 20 addresses from a seed are recognized, no one of the addresses from the imported private keys.

Edit: from console the imported privkeys addresses doesn't appear neither with electrumfair listaddresses

@santiky
Copy link
Collaborator

santiky commented Jul 26, 2017

the "import private keys" is not a way to go due to we need to sweep the funds, and is required we need use the same wallet with the same balance and addresses for user.

I have the wallet updated to 2.7.18 and striped the false addresses created but i was facing another problem creating transactions, i thought related to
spesmilo#2242

I updated to 2.8.3 (branch 2.8.3-fc, ready to test and use, works for me in debian stretch) but it does not solved the error.
Perhaps is related to
spesmilo#2509
fixed in
spesmilo@7ea2cb4
so i am updating to electrum master but some classes were some refactored (blockchain.py) and it is giving problems to run (changes in the serialized header function and so).

@thokon00
Copy link

Is this issue still relevant?

@santiky
Copy link
Collaborator

santiky commented Dec 18, 2017

Not really, can be closed

@santiky santiky closed this as completed Dec 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants