Topic: MtGox adds redeemer for private keys including Casascius Physical Bitcoins (Read 8560 times)

Interesting.  That particular address and public key pair is just the test pair from the wiki here:  https://en.bitcoin.it/wiki/Mini_private_key_format


So, it is not any of my personal addresses or public keys (whew).  But it interesting that it showed up.  My guess is that Mt. Gox may be using that test pair for testing and somehow their testing went astray?

I just got shown bwagner's private key from this post as my Bitcoin receiving address at MtGox. From what seems to be a php var_dump showing me debug.

This is a major WTF.

1GAehh7TsJAHuUAeKZcXf5CnwuGuGgyX2S

imgur proof:

I have confirmed that MtGox now accepts private keys in "sipa format".

Cool. I take it the --info ensures it won't actually import the key. I tested it with no wallet present and it still works the same so that's handy.

pywallet.py --info --importprivkey 5JSnvLmCsFDye4QMbYE1fsyGAPbpr1XjyBuGJpqVfdvuz2kmuo6

will return:
Address (Bitcoin): 13mWJ7RtAoMTB6nYTWouHSc8KLfpUWZskY
Privkey (Bitcoin): 5JSnvLmCsFDye4QMbYE1fsyGAPbpr1XjyBuGJpqVfdvuz2kmuo6
Hexprivkey: 52e417a1818758ebc3e1c595bf0dca0c9f29a0e1087d5b01456f43819cfbd401

This is all just very awesome. Thanks again to Casascius and MagicalTux.

Boom that worked!!! Thanks bud!

MtGox intends to support this format but may have a bug in its implementation.  I was discussing how this format worked with MagicalTux about 16 hours ago and he indicated his initial understanding of the format was incorrect. So this presumably should be supported at some point soon once it is all fixed.

The "sipa format" is the most commonly used private key format in Bitcoin so it will undoubtedly be supported.

If you don't mind telling your private key to Block Explorer, you can use their API:

Example:
Address: 13mWJ7RtAoMTB6nYTWouHSc8KLfpUWZskY
Privkey: 5JSnvLmCsFDye4QMbYE1fsyGAPbpr1XjyBuGJpqVfdvuz2kmuo6

Go to https://blockexplorer.com/q/addresstohash/5JSnvLmCsFDye4QMbYE1fsyGAPbpr1XjyBuGJpqVfdvuz2kmuo6
and the hex that it spits back is 52E417A1818758EBC3E1C595BF0DCA0C9F29A0E1087D5B01456F43819CFBD401

And if I go to Mt. Gox and try to redeem it, it says "Private address added to your virtual wallet with address 13mWJ7RtAoMTB6nYTWouHSc8KLfpUWZskY. There was no coins in there, maybe you did a typo?"

I'm sure that there are ways of doing it with openssl or python or whatnot locally, but as long as you trust the Block Explorer site to not do anything nefarious with your private key before you have a chance to redeem it, it ought to work for you until Mt. Gox supports the import format directly.

Hmm this is frustrating, I don't know how to take a "sipa format" key and turn it into "standard key"

Can anyone help me?  I can just give you my private key with 1btc on it and you can send me a btc if that's easiest. My coin is stuck in purgatory

Please pm if you can help

"Auto sweep" also works.  I added 2 more Bitcoins to one of the addresses I imported via private key.  The amount was then automatically swept from the imported private key account and transferred to yet another new account inside Mt. Gox.

See http://blockexplorer.com/address/13MsUf2Nnowoj8gdZBfBSyBJzVcC1R7hZA

After sending 4 opened coins (2 using mini key and 2 using hex key) and then sending two more Bitcoins by sending them to one of the opened coin accounts using the "auto sweep".  My Mt. Gox account shows:


Very nice new feature!

Wow.  This is huge for Casascius.  Congratulations!

Here is what I have tried so far:

I entered the mini private key S4b3N3oGqDqR5jNuxEvDwf and got the response "Private address added to your virtual wallet with address 1GAehh7TsJAHuUAeKZcXf5CnwuGuGgyX2S. There was no coins in there, maybe you did a typo?"  This is the correct public key address and there are no coins at this address.  So far so good.

I entered the hex private key for the same key 0c28fca386c7a227600b2fe50b7cae11ec86d3bf1fbe471be89827e19d72aa1d and got the response "Your private address could not be redeemed (already redeemed?)".  I guess this is the expected response and it proves that they calculated the same account for this version of the private key.

However, when I enter the WIF 5HueCGU8rMjxEXxiPuD5BDku4MkFqeZyd4dZ1jvhTVqvbTLvyTJ for the same private key it calculated the wrong public key address.  So there appears to be a problem/bug when using the WIF.

I reported this bug to Mt. Gox.

I then used both a real mini private key and a real hex private key to attempt to import Bitcoins from active accounts (opened physical coins).  In both cases it calculated the correct public key address and found that there were Bitcoins in the accounts and promised to import them into Mt. Gox.

The Bitcoins were eventually moved off the accounts for the private keys I entered into Mt. Gox and placed on new accounts withing Mt. Gox.  This proves that they sweep the value off the imported private keys so there is no way to reuse the private key to send Bitcoins out of Mt. Gox.

See http://blockexplorer.com/address/13MsUf2Nnowoj8gdZBfBSyBJzVcC1R7hZA

And http://blockexplorer.com/address/13MT4QvExmajXAYqKQeMXAh9saVTVP6f6a

Both (one from a mini key and one from the hex key) showed up in my Mt. Gox account:  The notation looked like this:

This shows both the notes I put in when I imported the key (first bits of the original public address and the private key type used) and the new public address the Bitcoins were swept into.

I want to send out transactions specifically from the wallet I uploaded to a specified recipient (outside Mt. Gox)

bitaddress.org provides the private key in "Sipa Wallet Import Format" and MtGox is expecting "Standard Format".
I'm working on a new tab for bitaddress called "Wallet Details" it will have one input box for the private key and I will auto-detect the format and display the private key in the various different formats including the "Standard Format" required by MtGox.


THANKS to MtGox for this super cool feature of private key redeeming!! I hope they add an auto-detect for all the different private key formats.

Hmmm okay I tried using bitaddress, generated a new keypair, and sent one coin to the address: 1QGUNoJ799PKGrFuPrXJPRM3ZsHPoHh1rh

I've tried "redeeming" this with MtGox (using the long-ass private key) a couple times now (including yesterday) and nothing is showing up. You can see the 1 btc is still at the address above.

Any help?

Maybe I'm confused but I thought the address was a hash of the key, not a public key. I would expect once you redeem the key at MtGox that key becomes one of the ones attached to your account just like other keys they generate for you.

So any funds sent to that address later would end up in the account. I'm not sure about this. The difference would be that you could potentially spend money from that address without having to withdraw it using the MtGox interface. Or, alternately perhaps they transfer funds into your account and leave the key empty so that such "outside withdrawls" cannot occur.

Great work! I'm handing out some of my casascius coins to friends, and having this feature will make the explanation a lot easier.

Of course it supports it all you have to do is tell Mt Gox to send Bitcoins to the corresponding public key, however since you have imported the private key into your Mt Gox account the coins would just be sent from your Mt Gox account back into your Mt Gox account, unless I am missing something in your question.

You wouldn't want this.  It has non-ideal security implications.  If you want to stay safe, don't re-use private keys once you've typed them into a website.  Use a new one.