|
Ouch, do you happen to know which version you are using?
You can cat lib/version.py from the source dir if you don't know. (if that was already in that version)
|
|
|
|
|
Before you do anything else, just to be sure, make a copy of the wallet.
Then try downloading the latest stable release from Flatfly (Windows) or do a pip install from the tarbal from the site (Linux). And see if that helps.
|
|
|
|
A few more things I've got in being tested at bkkcoins/electrum branch, merged-2. Anyone is welcome to test it but please backup your wallet first. - show currency balance in pro mode. not fancy or clickable - remember column widths for receive and history tabs - new sahara theme with browns instead of blues - import addr or key only allows import a watch only address (flag W in list) allows import just key w/o address like most other clients, gets addr from key - multi-select sends - like coin control - expert only allows multi-selections in receive list and context menu to add as inputs for send send page looks same unless selected inputs then a list shows I have tested most of this a fair bit but the multi-select sends I have only test the gui and not got around to testing the actual send trx yet. I'd prefer to use test net rather than risk my wallet but I'll probably do something tomorrow. Going to go watch a movie now...  Will check those out asap  |
|
|
|
I would love to build this. I think it's really necessary since Electrum servers sometime lag behind, which can be quite annoying. This should be right up my alley to see I am a web-developer by day |
|
|
|
I was thinking of a feature that allows you to show a QR containing a signed transaction. Then you could grab your phone with Electrum and snap it and send without ever physically moving anything from offline machine to net-connected machine. Truly an "air-gapped" process. Intriguing, I like how you're thinking .... Amoury (and any off-line wallets that can sign) might be interested in this feature also. All I can say is I'm real glad BkkCoins is taking strong interest in contributing to Electrum and will quickly become an invaluable asset to the "team"... Couldn't agree more. BkkCoins hit me up on irc so I can give you commit access to the main repo. You seem to deliver quality work I've merged your 'merged' branch from two days ago into master now, did a lot of testing and it seems to be stable. I will try to find some time to checkout the merged2 branch. You are developing harder then I can test it  |
|
|
|
I've asked Genjix to look into your pull request a while ago since I wasn't sure I understood the commit to the fullest. He is taking a little time-out since the conference but he should be back soon (I hope ). I will make sure the Spanish translation gets compiled into the next release, which shouldn't be too long |
|
|
|
I've just finished an very, very initial implementation of multiple wallet support into the lite-gui.  There are some limitations at this point: - You will not be able to add new wallets via de GUI. Launch Electrum with -w ~/.electrum/wallet_name.dat to add one for now.
- It will only find wallets inside the default electrum folder. ~/.electrum on Linux/OS X
I will not be merging this into master anytime soon since these features add on the actual wallet files themselves. So if you want to help me test it / code review it please do this by checking out the feature/wallet-experiments branch from Github. Please backup your wallets if you do decide to help out git checkout -b wallets origin/feature/wallet-experiments
Thanks in advance. |
|
|
|
Tested it on a clean Debian 6 system and on OS X 10.7 and it seems to be working. Before I merge it into master though I would appreciate it if there were some other people who could give it a quick run. It required some manual merging and that's always tricky. I previously made master unstable by merging too quickly and I would like to avoid that this time. The fully merged tree can be found on github. Thanks! |
|
|
|
Merged everything, just doing some final testing on a couple of my vm's before I merge everything back into master |
|
|
|
I've merged the offline wallet fix, I've commented on the "remember Gui" pull and I will check out the larger commits tonights and over the weekend. They can't be merged automatically so I want to be sure everything goes according to plan. The commits you have done did fix my config file issues |
|
|
|
I have a working version of Electrum with SOCKS and HTTP proxy support now in my fork. If anyone wants to try it / test it and give feedback I'd welcome that before going for a pull request to merge it in.
I've tested it with SOCKS4 and SOCK5 a fair bit using an ssh tunnel to my server at amazon. This was quite reliable and seemed to have no issues. I tried an HTTP proxy off a free-list and it worked as well but I found it was more inconsistent and once it had an error it usually could not recover except by restarting. This seems to be due to how the polling code is done and it doesn't handle an error condition and recuperate. I tested mostly with TCP mode but a few times with HTTP mode too.
This proxy support uses the Socksipy wrapper available from google code (apparently a fixed version of the old 2006 code). The license on that code is a bit vague. It's not explicitly based off a known entity but seems to say, well, use it but leave the notice intact is all. One drawback of this code is that it doesn't support unicode host urls. I'm not sure if that's very important for proxies as in most cases people probably use localhost anyway.
Does Tor use a SOCKS proxy? Could someone test if this allows Electrum to run over tor then? I don't know anything about that but it would be good if it worked.
To find this for testing goto my fork at bkkcoins/electrum and get the socks-support branch (NOT the master branch which is default).
Ok I ran the codebase and with a clean install it works fine and runs perfect over Socks! There is however a problem. When you are starting from a non-fresh installation on master and you already have a config file the app crashes because the key proxy doesn't exit. Traceback (most recent call last):
File "./electrum", line 119, in <module>
parser.add_option("-p", "--proxy", dest="proxy", default=simple_config["proxy"], help="set proxy [type:]host[:port], where type is socks4,socks5 or http")
AttributeError: SimpleConfig instance has no attribute '__getitem__'
I tried solving this by writing a get_key method for SimpleConfig so that if a key is not found, it just returns nothing. Sadly this did not really solve the problem. Traceback (most recent call last):
File "/usr/local/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 551, in __bootstrap_inner
self.run()
File "/Users/maran/Projects/bitcoin/bkk-electrum/lib/interface.py", line 434, in run
self.start_interface()
File "/Users/maran/Projects/bitcoin/bkk-electrum/lib/interface.py", line 425, in start_interface
self.interface.init_socket()
File "/Users/maran/Projects/bitcoin/bkk-electrum/lib/interface.py", line 263, in init_socket
if self.proxy["mode"] == "none":
TypeError: 'NoneType' object has no attribute '__getitem__'
I'm now not sure how to solve this. Is this an issue with your code specific? An other option to solve this would be to "upgrade" the default_options on each launch. Check if the default have more then the current, merge the default into the config file but don't overwrite existing options. I think this would be the best solution. What do you think? |
|
|
|
I think there are a bunch of things higher priority at the moment for Electrum. But if you supply a pull request I'm sure it will get merged |
|
|
|
Cool! I will give it a try after work tonight |
|
|
|
I would prefer if the master branch was considered stable. Things should be merged only after they have been tested.
I can understand that, that's why we should really about git-flow. bug reports like these are not needed [...]
well... are you sure that's the right approach?
Once we move over to Gitflow this problem is solved since every feature will be in it's own branch, once it's merged into master it should be stable and bug reports make sense. The problem is I merged this feature in master too soon, without proper testing it myself. |
|
|
|
Ah yes, after digging thru the code a bit I saw the new SimpleConfig stuff. I'm using the "gui":"qt" value now and it works. I'll just work on adding a checkbox for this in expert mode settings.
I have SOCKS support working now. I am currently testing it and working out how to do the settings. I've added defaults in SimpleConfig to support this and also added cmdline proxy option.
I could have proxy values in main settings dlg or put them in server connect dlg. Seems like socks works but is limited by not supporting unicode string for url in the socks module. I'm not sure how much unicode DNS lookup is needed but I guess ideally this should only affect proxy and not normal connections.
I'm a bit confused as to whether I'm working from master or 1.0 branch. I guess this only matters when it gets pulled back later?
I would try to work from master, 1.0 is pretty far behind. |
|
|
|
I've already brought up Git flow since I use that for all my day-job related code. It's an awesome system and makes it very easy for all parties to know what to except. Sadly Genjix has been very busy these last few weeks with the conf stuff so I haven't had the time to really discuss it. I will bring it up again once he surfaces |
|
|
|
Sure thing, but please note that master is overall considered unstable. So most of the time bug reports like these are not needed until the release is merged into a stable branch and ready for testing. |
|
|
|
1. A setting that allows starting up in Pro Mode and skipping what I see as the useless small window currently the default.
This is something I'm already working on in master, sorta. If you edit config.json and setup gui: qt it should boot up in pro mode every time. There just isn't a preference window to set it yet, only via editing the config file. 2. SOCKS proxy support so the client can get to the server via an ssh tunnel when at public wifi locations (amongst other uses).
3. Have the current balance in local currency (fiat) on the Pro Mode window (like on the small regular startup window).
4. Have main window remember it's size and location on the desktop.
These would be a very welcome pull requests, preferable in separate commits so it's easier to code review. Thanks for your involvement |
|
|
|
I have a question regarding passwords.
I'm not really sure I understand how this client is supposed to work, but if you use an encrypted wallet shouldn't it ask for the password every time the program is run? Mine goes straight into the application.
I'm running v1.01 on OS X Lion 10.8.1 if that helps
Only when you need a need acess to your private keys. Try sending a payment and it should ask for your password. |
|
|
|
Anybody selling a BTC10[/btc] silver round with gold-plated b? Still considering buying one and not having to pay shipping might just push me over the edge |
|
|
|
|
Show Posts
