Quote from: Ean on January 14, 2012, 07:19:24 PM

Quote from: dani147624 on January 14, 2012, 12:01:05 PM

Damn it!

Doing the operations was my first idea... I managed to force pywallet to output something in hex, which I beleived, were the numbers:

33 + caea7cc3f8b198101e0f7ffb0eeb2e8c85ce9e72cc628990f30f41183aa6eba58761c239d03ded / 019385 (all in hex)

Doing these operations in gcalctool I ended up with this solution: 80BBC798A19A21A8BCEAA022375B1B73C73EF466CBE5B48D1DB1C195B26CC4603DDC2F897C

However, when this was imported into my wallet.dat, I didn't get the bitcoins (bitcoin was restarted with -rescan). What did I screw up?

The base58-key kontains 5 additional bytes that the hex-version do not. The blue part is the actual key:
80BBC798A19A21A8BCEAA022375B1B73C73EF466CBE5B48D1DB1C195B26CC4603DDC2F897C

Now that I think about it, pywallet probably didn't allow me to import the long key, so I deleted the last 5 bytes... Turns out I should have deleted the first byte and the last 4 bytes instead... Well, anyway, thanks for pointing that out.