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

Error trying to sweep a private key: unsupported operand type(s) for *: 'NoneType' and 'int' #113

Closed
aecole opened this issue Aug 11, 2017 · 9 comments

Comments

@aecole
Copy link

aecole commented Aug 11, 2017

I'm getting this error on OSX with the released binary and the latest development branch. There is nothing in the log when I run electron-cash with the -v switch. Help / pointers appreciated.

@molecular
Copy link

  • is this on 2.9.2?

it's weird there's nothing on the stdout, definitely looks like an exception that should be printed ther. Are you starting from a terminal? Are you getting this error in a popup or where are you getting it?

@fyookball
Copy link
Collaborator

which log?

@aecole
Copy link
Author

aecole commented Aug 12, 2017

Yep, 2.9.2 and it's a popup on screen, can't grab a screenshot right now, but it's in the GUI and not on stdout.

I ran the binary in the usual way - double click in OSX, the development version I ran from the terminal.

@aecole
Copy link
Author

aecole commented Aug 12, 2017

Which log - I'm referring to the Terminal when launched with the -v switch.

@robert-claypool
Copy link

robert-claypool commented Aug 18, 2017

I get this same error in 2.9.2 when trying to sweep a private key in WIF format (51 characters base58, starts with a '5'). Running x86_64 Linux 4.12.6-1-ARCH.

Here are the logs...

[robert@mozart electron-cash]$ python2 electron-cash -v &
[robert@mozart electron-cash]$ [SimpleConfig] electron-cash directory /home/robert/.electron-cash
[Plugins] registering hardware digitalbitbox: ('hardware', 'digitalbitbox', u'Digital Bitbox wallet')
[Plugins] registering hardware keepkey: ('hardware', 'keepkey', u'KeepKey wallet')     
[Plugins] registering hardware ledger: ('hardware', 'ledger', u'Ledger wallet')        
[Plugins] registering hardware trezor: ('hardware', 'trezor', u'TREZOR wallet')        
[Plugins] registering wallet type ('2fa', 'trustedcoin')                               
[profiler] __init__ 0.0017                 
[Network] blockchains [0]                  
[Network] starting network                 
[Network] connecting to bcc.arihanc.com:52002:s as new interface                       
[FxThread] using exchange Kraken           
[WalletStorage] wallet path /home/robert/.electron-cash/wallets/default_wallet         
[WalletStorage] wallet path /home/robert/.electron-cash/wallets/default_wallet         
[WalletStorage] wallet path /home/robert/.electron-cash/wallets/default_wallet         
[35.197.25.235] connected                  
[35.185.209.69] connected                  
[crypto.mldlabs.com] SSL certificate signed by CA                                      
[crypto.mldlabs.com] connected             
[electron.coinucopia.io] connected         
[abc1.hsmiths.com] connected               
[Network] no height for main interface     
[Network] switching to 35.197.25.235:50002:s                                           
[Network] sending subscriptions to 35.197.25.235:50002:s 0 0                           
[jihan.bitcoin-abc.de] connected           
[bcc.arihanc.com] connected                
[Network] relayfee 1000                    
[electroncash.cascharia.com] connected     
[35.158.236.146] failed to connect timed out                                           
[180.235.49.196] failed to connect timed out                                           
[fdkhv2bb7hqel2e7.onion] cannot resolve hostname                                       
[electron.ueo.ch] saving certificate       
[electron.ueo.ch] connected                
[electrum-btc.ddns.net] SSL error retrieving SSL certificate: ('_ssl.c:645: The handshake operation timed out',)
[electrum.epicinet.net] saving certificate 
[electrum.epicinet.net] connected          
[profiler] load_transactions 0.0000        
[profiler] build_reverse_history 0.0000    
[profiler] check_history 0.0000            
[profiler] on_update 0.0001                
[ElectrumWindow/default_wallet] Notifying GUI                                          
[robert@mozart electron-cash]$ [profiler] write 0.0001                                 
[profiler] save_transactions 0.0003        
[profiler] on_update 0.0001                
[profiler] estimated_size 0.0003 

@robert-claypool
Copy link

The error message changes to No inputs found. (Note that inputs need to be confirmed) when I import a WIF compressed version of the private key (52 characters base 58, starts with a 'K' or 'L').

  1. According to blockdozer.com, the address does contain BCC, and I'm positive that the address was holding Bitcoins on August 1, 2017 at 6:12pm UTC.

  2. They were never held by an Electrum wallet, but I thought that doesn't matter? I am trying to import from a bitaddress.org paper wallet.

  3. I tested this on Arch Linux and then on Windows 10. Same result.

  4. I have verified the sha1 hash and gpg sig of the downloads. They are correct.

@robert-claypool
Copy link

Electron Cash connected itself to the wrong freaking blockchain!

Solution: Go to "Tools > Network", then uncheck "Select server automatically", then right-click a BCC server from the list.

@fyookball
Copy link
Collaborator

chain fixes coming in next version

@aecole
Copy link
Author

aecole commented Aug 21, 2017

Juts confirming: my problem has gone away in the latest version

cculianu added a commit that referenced this issue Mar 23, 2019
…113)

* Fix #105 - Remember change addresses shared with others over network

If a client participates in a shuffle (even a failed shuffle or even a
pool that fails), the change address (which is publicly shared with
other peers) is marked as having been "shared with others" and it can
never be used as a shuffled output address (but can continue to be used
as a change address in subsequent shuffles).

This avoids privacy leaking as a client participates in pools
and fixes the issue discussed in #105.

* nit
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

4 participants