After a quick look at the wallet file I thought the format didn't change, but yeah, looks like Bitcoin now stores compressed keys.
I left for a while so I don't know much about compressed keys yet, but now you made me look closer at that, everything is clear.
Thanks a lot for the tip, I hope I'll soon post here that everything's fine
Topic: Keys / Addresses (Read 768 times)
Does the pywallet you are using understand compressed keys?
I've encountered a problem, and it's kinda difficult to investigate more as I still have 40000+ blocks to download.
I made a new Bitcoin wallet (with bitcoin 0.8.1, linux). Obviously it has default keys. Let's take the main one.
This is a dump from Joric's pywallet. 1Co8KFDHnwyuCxfyBWPK1ifRjGiR7AeXDC is what Bitcoin software shows.
The thing is, when I use pywallet (Joric's one, which is up-to-date) to import the private key (here as hexsec or sec) into another wallet, the message it returns to me mentions the address 1MUVkGv8TWjvdJ87VMGoNyhG3NLYE87WQT, and not 1Co8KFDHnwyuCxfyBWPK1ifRjGiR7AeXDC.
If I had access I would have transfered 1 mBTC to each address and tried to retrieve both to see what would happened...
So in the mean time, can anyone tell me what I can do to check where is the error? And can someone check to which address the private key 3d423f... corresponds?
Thanks for any help
I made a new Bitcoin wallet (with bitcoin 0.8.1, linux). Obviously it has default keys. Let's take the main one.
Code:
{
"addr": "1Co8KFDHnwyuCxfyBWPK1ifRjGiR7AeXDC",
"hexsec": "3d423fb2f8b7af14e590230d87ec9067cba3ad29261f829c4f2476ade4278aa0",
"label": "",
"privkey": "3081d30201010420543d423fb2f8b7af14e590230d87ec9067cba3ad29261f829c4f2476ade4278aa08185308182020101302c06072a8648ce3d0101022100fffffffffffffffffffffffffffffffffffffffffffffffffffffffefffffc2f300604010004010704210279be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798022100fffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd0364141020101a1240322000302519ca3be493a26d62e96a814388b441bf972f6cf16f07ba49b993f3a12db69",
"pubkey": "0302519ca3be493a26d62e96a814388b441bf972f6cf16f07ba49b993f3a12db69",
"sec": "5JHGMYGpfoD7HK3jSNrKgRry9yRZGEGJEXBk6w3KPfAdjQRyawb"
}
The thing is, when I use pywallet (Joric's one, which is up-to-date) to import the private key (here as hexsec or sec) into another wallet, the message it returns to me mentions the address 1MUVkGv8TWjvdJ87VMGoNyhG3NLYE87WQT, and not 1Co8KFDHnwyuCxfyBWPK1ifRjGiR7AeXDC.
If I had access I would have transfered 1 mBTC to each address and tried to retrieve both to see what would happened...
So in the mean time, can anyone tell me what I can do to check where is the error? And can someone check to which address the private key 3d423f... corresponds?
Thanks for any help
Jump to: