Pywallet 2.2: manage your wallet [Update required] - page 31.

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

Quote from: Dabs on April 15, 2013, 05:00:33 AM

Regarding the public key only, I was thinking, what if you don't know the private key, or do not wish to add it (so it is never seen by hardware or software.) That's my point for adding it to wallet.dat with bogus encryption. Watching only.

I will test the suggested method, maybe that will work if you know the private key. But then, why bother when you can importprivkey using the QT client directly?

You're absolutely right, I posted that just to check if bitcoin-qt accepts bogus private keys/encryption
If it works you'll only have to give the public key

Dabs

legendary

Activity: 3416

Merit: 1912

The Concierge of Crypto

Regarding the public key only, I was thinking, what if you don't know the private key, or do not wish to add it (so it is never seen by hardware or software.) That's my point for adding it to wallet.dat with bogus encryption. Watching only.

I will test the suggested method, maybe that will work if you know the private key. But then, why bother when you can importprivkey using the QT client directly?

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

Yes it's just an exe file to install
PWI 0.0.3 should install all dependencies BTW

But yeah don't worry I think other people with pywallet already installed will try

dserrano5

legendary

Activity: 1974

Merit: 1029

Quote from: jackjack on April 14, 2013, 04:05:16 PM

I'd like someone to confirm that the new update system works on windows

Code:

'twisted' package is not installed, pywallet web interface can't be launched

Now if installing twisted is a matter of uncompressing some zip file available in the interwebz I can give it a try, but otherwise I don't really want to fight windows. Somebody else e.g. a current pywallet user should have it already installed.

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

Pywallet v2.0 released!

I hope you'll like the changes

I'd like someone to confirm that the new update system works on windows

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

Yeah of course! Grin

And I forgot I coded the update page that way... That's kinda stupid actually
I'll change that to the ajax way...

K1773R

legendary

Activity: 1792

Merit: 1008

/dev/null

Quote from: jackjack on April 12, 2013, 06:51:51 AM

Yup good idea I'll put that soon

Quote from: K1773R on April 12, 2013, 06:44:16 AM

Code:

That would work too right?

Code:

no, otherwise it would refresh the update site and therefore update itself all 5 seconds lol
update site = "/?update=1"

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

Yup good idea I'll put that soon

Quote from: K1773R on April 12, 2013, 06:44:16 AM

Code:

That would work too right?

Code:

K1773R

legendary

Activity: 1792

Merit: 1008

/dev/null

Quote from: dserrano5 on April 12, 2013, 06:37:12 AM

ADSL routers and the like have a piece of javascript or HTML META tag to refresh the page some time after instructing the router to reboot itself. That mechanism would fit nicely here.

Code:

dserrano5

legendary

Activity: 1974

Merit: 1029

ADSL routers and the like have a piece of javascript or HTML META tag to refresh the page some time after instructing the router to reboot itself. That mechanism would fit nicely here.

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

Great, so that works
It's true I should add a little message to say everything happened as expected

dserrano5

legendary

Activity: 1974

Merit: 1029

I got the "out of date" message. Then clicked on it to upgrade and I got the standard Firefox error about being unable to connect. pywallet output is sane so I guess the Firefox message is normal:

Code:

2013-04-12 12:39:36+0200 [HTTPChannel,0,127.0.0.1] 127.0.0.1 - - [12/Apr/2013:10:39:35 +0000] "GET /?update=1 HTTP/1.1" 200 29750 "http://localhost:8989/" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0"
2013-04-12 12:39:36+0200 [twisted.web.server.Site] (Port 8989 Closed)
2013-04-12 12:39:36+0200 [twisted.web.server.Site] Stopping factory 
2013-04-12 12:39:36+0200 [-] Main loop terminated.

Did a ./pywallet.py again and now it reports being up to date.

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

Thanks!

To everybody: I pushed the new version, can you check that pywallet tells you there's an update? and that auto-update works?

dserrano5

legendary

Activity: 1974

Merit: 1029

Thanks for all the insights, and for pywallet of course!

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

Quote from: dserrano5 on April 11, 2013, 09:33:17 AM

Quote from: jackjack on April 11, 2013, 07:42:05 AM

It's true that you'll lose the transactions but a rescan is rather quick, isn't it?

Ah, I didn't know that a rescan repopulated the wallet with the transactions. I thought the client added each transaction at broadcast time and that was all.

Nope, during a rescan the client reads all the blockchain and repopulate the wallet.
The "issue" is that you lose your unbroadcasted transactions. But it can be used when you made a transaction that won't never be include in a block for example.

dserrano5

legendary

Activity: 1974

Merit: 1029

Quote from: jackjack on April 11, 2013, 07:42:05 AM

It's true that you'll lose the transactions but a rescan is rather quick, isn't it?

Ah, I didn't know that a rescan repopulated the wallet with the transactions. I thought the client added each transaction at broadcast time and that was all.

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

Oh yeah I forgot to test that

I just looked at the code and... erm... before importing a private key in an encrypted wallet I don't check if it's the right one (-> todo list'd)
So it makes things easier to test:

create a dummy encrypted wallet
pywallet.py --importhex --importprivkey 0123456789012345678901234567890123456789012345678901234567890123 --passphrase anything_that_is_not_the_correct_passphrase

That should import the address corresponding to 01234... but with the bad encrypted private key
See what then happens (I can't test right now)

Dabs

legendary

Activity: 3416

Merit: 1912

The Concierge of Crypto

What happened to the import public key? (with a bogus private key; this is for encrypted wallets only.)

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

Quote from: dserrano5 on April 11, 2013, 05:27:11 AM

I had read about that but somehow I got the impression that I would lose the transactions stored in the wallet. I am totally and utterly wrong, no?

It's true that you'll lose the transactions but a rescan is rather quick, isn't it?

Quote from: dserrano5 on April 11, 2013, 05:27:11 AM

Yeah that did it, thank you! The second dump shows an unhandled exception without any additional info:

Yeah it happens sometimes. I didn't look at this matter closely as it doesn't seem serious.

dserrano5

legendary

Activity: 1974

Merit: 1029

Quote from: jackjack on April 11, 2013, 04:56:17 AM

Quote from: dserrano5 on April 11, 2013, 04:29:44 AM

I'd be happy to be able to --dumpwallet into a file, edit that file and then --importdump or something like that.

You can: this then that

I had read about that but somehow I got the impression that I would lose the transactions stored in the wallet. I am totally and utterly wrong, no?

Quote from: jackjack on April 11, 2013, 04:56:17 AM

Line 1782: change 'if type == "key":' to 'if type == "key" or type == "ckey":'
Must do the trick

Yeah that did it, thank you! The second dump shows an unhandled exception without any additional info:

Code:

$ diff -U2 wallet-dump{1,2}
--- wallet-dump1	2013-04-11 12:13:22.029680350 +0200
+++ wallet-dump2	2013-04-11 12:14:42.028662746 +0200
@@ -22,13 +22,4 @@
         }, 
         {
-            "addr": "1BLre3Uv7Xxh5XgYa8NXbS7ZYTXBuyCfiK", 
-            "compressed": true, 
-            "encrypted_privkey": "2d4a14267d220fce36d7c48df789561797743c29cf750ef5a5234faa7ab178ed8ef4e113771bdb9fe3aa4b0c2a94e9e9", 
-            "pubkey": "02e34a2cc7ee8694cd943d58b222a82e181741002151378820216f6e330cee4c31", 
-            "reserve": 1, 
-            "sec": "KxKs8MzyCZ7ufjGsvZNUJtEF9dxuV12geRfM5KCMRofmFXWhbuVr", 
-            "secret": "2100db5080ec709e0e015d669808111de6f5e9c0e8425f126dce4dc1cd8f520601"
-        }, 
-        {
             "addr": "1L7aZRwhW3Kku66mMxi9NH5z6UUymEZ9im", 
             "compressed": false, 
@@ -35882,2 +35873,6 @@
     "version": 80000
 }
+Unhandled exception in thread started by 
+Error in sys.excepthook:
+
+Original exception was:

Topic: Pywallet 2.2: manage your wallet [Update required] - page 31. (Read 208227 times)