from OP
the prize awaits you
the final palindrome is key
once small is now tall
so change lowercase to uppercase?
only palindrome i can think of is WOW , is there any others?
Topic: ARG Puzzle with 3.5 BTC Private Key Prize, Game Over - page 15. (Read 99512 times)
I suspect you're looking for a code that, when posted, will confirm to OP you've solved the puzzle. OP will then communicate with that person directly to prevent swiping of the private key. Keep it simple.
-snip-
every different place i check says https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3 is a valid bitcoin address and i've tried a few different places.
every different place i check says https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3 is a valid bitcoin address and i've tried a few different places.
Lets just cut this and say: How cares? We need a valid (!) private key (!) that allows you to spend the coin that have been send to 1HXUobwcB19cGDrghuh42HDdJdJvrJUEra
Everything else is irrelevant. Well unless there is another step ahead of us. But this would most likely not go over bitcoin addresses.
every different place i check says https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3 is a valid bitcoin address and i've tried a few different places. End of the day i don't really care, it's an empty address, but everywhere i check says it's valid.
The ADDRESS is valid but no wallet should have imported the PRIVATE KEY because it is invalid.
Focus people!
5KZnsvrXDcP7JFD7GCuZvifrbcBtK4kAe8nHx6ibktgvPJxs4Lp is the string we get from shifting the z69... string by 6EQUJ5 within the base62 alphabet provided by OP
But it is not a valid bitcoin private key because the checksum bytes don't match. Any program that imports it is probably ignoring the checksum and using the 32 bytes after the 0x80 (which is incorrect BTW).
But using the 32 bytes after the first 0x80 (looking at the string in hex) as a private 'raw' key does not yield the correct public address.
So where do we go from here?
1. Maybe someone can find another shift that produces something starting with L for a compressed format?
2. Are there multiple rounds of shifts possibly?
3. Try extra characters at the end of 6EQUJ5?
I believe we just need to find a transformation within the base62 space that yields a valid base 58 address that starts with 5 (uncompressed) or L/K (compressed).
5KZnsvrXDcP7JFD7GCuZvifrbcBtK4kAe8nHx6ibktgvPJxs4Lp is the string we get from shifting the z69... string by 6EQUJ5 within the base62 alphabet provided by OP
But it is not a valid bitcoin private key because the checksum bytes don't match. Any program that imports it is probably ignoring the checksum and using the 32 bytes after the 0x80 (which is incorrect BTW).
But using the 32 bytes after the first 0x80 (looking at the string in hex) as a private 'raw' key does not yield the correct public address.
So where do we go from here?
1. Maybe someone can find another shift that produces something starting with L for a compressed format?
2. Are there multiple rounds of shifts possibly?
3. Try extra characters at the end of 6EQUJ5?
I believe we just need to find a transformation within the base62 space that yields a valid base 58 address that starts with 5 (uncompressed) or L/K (compressed).
Quote from: Gatekeeper link=tohttps://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3pic=661781.msg7705294#msg7705294 date=1404669740
that's still a valid address though isnt it? it's just that no one knows the priv key. That's different, here blockchain is importing a "private key" and giving you what it says is a valid address, if you edit the address it says checksum isn't valid, so that website clearly thinks that an address is valid that the other guys are saying is not, which seems to be a big flaw in blockchain.info.
It's saying https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3 is a valid address, and the guys here are saying it isn't
It's saying https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3 is a valid address, and the guys here are saying it isn't
WIF private key is either valid or not. You can check yourself here, down on the page you have 'WIF checksum checking':
http://gobittest.appspot.com/PrivateKey
5KZnsvrXDcP7JFD7GCuZvifrbcBtK4kAe8nHx6ibktgvPJxs4Lp should have checksum 08FA7CC9 and it has 1E157B43. Key invalid, end of story. Any wallet that imports it has a bug.
every different place i check says https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3 is a valid bitcoin address and i've tried a few different places. End of the day i don't really care, it's an empty address, but everywhere i check says it's valid.
that's still a valid address though isnt it? it's just that no one knows the priv key. That's different, here blockchain is importing a "private key" and giving you what it says is a valid address, if you edit the address it says checksum isn't valid, so that website clearly thinks that an address is valid that the other guys are saying is not, which seems to be a big flaw in blockchain.info.
It's saying https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3 is a valid address, and the guys here are saying it isn't
It's saying https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3 is a valid address, and the guys here are saying it isn't
WIF private key is either valid or not. You can check yourself here, down on the page you have 'WIF checksum checking':
http://gobittest.appspot.com/PrivateKey
5KZnsvrXDcP7JFD7GCuZvifrbcBtK4kAe8nHx6ibktgvPJxs4Lp should have checksum 08FA7CC9 and it has 1E157B43. Key invalid, end of story. Any wallet that imports it has a bug.
yes, its compressed: 5KZnsvrXDcP7JFD7GCuZvifrbcBtK4kAe8nHx6ibktgvPJxs4Lp
but if you import it, then you see transactions made!
but if you import it, then you see transactions made!
Yeah, people turn an empty string into a brain wallet, then send money to it. Not related to the ARG.
L4rK1yDtCWekvXuE6oXD9jCYfFNV2cWRpVuPLBcCU2z8TrisoyY1
Compressed WIP private key for SHA256('')?
if they are not valid addresses then that is a fatal flaw in the blockchain because it's showing as a valid address and you could send coins there
1GatekeeperGatekeeperGatek1zEZ49j
That's 100% valid address meat, but has no private key. You can send coins there too
yes, its compressed: 5KZnsvrXDcP7JFD7GCuZvifrbcBtK4kAe8nHx6ibktgvPJxs4Lp
but if you import it, then you see transactions made!
that's still a valid address though isnt it?
Yep.
That's different, here blockchain is importing a "private key" and giving you what it says is a valid address
Yep.
which seems to be a big flaw in blockchain.info.
Yep.
Code:
0ee3318601b0ed03b4e12f4af8ab756bd0347b6b2bef4fbd1ff2fdd1ce6e93a5
that imports as
https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3
if they are not valid addresses then that is a fatal flaw in the blockchain because it's showing as a valid address and you could send coins there
If you edit the address it comes back as checksum not valid, so it clearly does check the addresses and says that this one is valid. If it's not then blockchain is fucked
eg:
https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC2 is not valid (change 3 to 2 at end)
https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3
if they are not valid addresses then that is a fatal flaw in the blockchain because it's showing as a valid address and you could send coins there
If you edit the address it comes back as checksum not valid, so it clearly does check the addresses and says that this one is valid. If it's not then blockchain is fucked
eg:
https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC2 is not valid (change 3 to 2 at end)
This is not true, there are extremely large number of BTC address that no private key hashes to. If private key (WIF) checksum is wrong, no decent wallet should import it. For instance look at this BTC address:
https://blockchain.info/address/1BitcoinEaterAddressDontSendf59kuE
You can send money to it, but you can never retrieve coins from it. There are thousands of transactions like that in the blockchain.
that's still a valid address though isnt it? it's just that no one knows the priv key. That's different, here blockchain is importing a "private key" and giving you what it says is a valid address, if you edit the address it says checksum isn't valid, so that website clearly thinks that an address is valid that the other guys are saying is not, which seems to be a big flaw in blockchain.info.
It's saying https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3 is a valid address, and the guys here are saying it isn't
L4rK1yDtCWekvXuE6oXD9jCYfFNV2cWRpVuPLBcCU2z8TrisoyY1
Compressed WIP private key for SHA256('')?
if they are not valid addresses then that is a fatal flaw in the blockchain because it's showing as a valid address and you could send coins there
1GatekeeperGatekeeperGatek1zEZ49j
That's 100% valid address meat, but has no private key. You can send coins there too
that imports as
https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3
if they are not valid addresses then that is a fatal flaw in the blockchain because it's showing as a valid address and you could send coins there
If you edit the address it comes back as checksum not valid, so it clearly does check the addresses and says that this one is valid. If it's not then blockchain is fucked
eg:
https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC2 is not valid (change 3 to 2 at end)
https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3
if they are not valid addresses then that is a fatal flaw in the blockchain because it's showing as a valid address and you could send coins there
If you edit the address it comes back as checksum not valid, so it clearly does check the addresses and says that this one is valid. If it's not then blockchain is fucked
eg:
https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC2 is not valid (change 3 to 2 at end)
This is not true, there are extremely large number of BTC address that no private key hashes to. If private key (WIF) checksum is wrong, no decent wallet should import it. For instance look at this BTC address:
https://blockchain.info/address/1BitcoinEaterAddressDontSendf59kuE
You can send money to it, but you can never retrieve coins from it. There are thousands of transactions like that in the blockchain.
L4rK1yDtCWekvXuE6oXD9jCYfFNV2cWRpVuPLBcCU2z8TrisoyY1
this private key have 24 transactions but 0 btc on it!
got to this adress: 1F3sAm6ZtwLAUnj7d38pGFxtP3RVEvtsbV
this private key have 24 transactions but 0 btc on it!
got to this adress: 1F3sAm6ZtwLAUnj7d38pGFxtP3RVEvtsbV
that imports as
https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3
if they are not valid addresses then that is a fatal flaw in the blockchain because it's showing as a valid address and you could send coins there
If you edit the address it comes back as checksum not valid, so it clearly does check the addresses and says that this one is valid. If it's not then blockchain is fucked then
https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3
if they are not valid addresses then that is a fatal flaw in the blockchain because it's showing as a valid address and you could send coins there
If you edit the address it comes back as checksum not valid, so it clearly does check the addresses and says that this one is valid. If it's not then blockchain is fucked then
If you could import that invalid private key to begin with, blockchain.info is not verifying checksums properly. It's invalid, end of story. The address checksum is a different matter, you can have an address but no matching private key.
that imports as
https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3
if they are not valid addresses then that is a fatal flaw in the blockchain because it's showing as a valid address and you could send coins there
If you edit the address it comes back as checksum not valid, so it clearly does check the addresses and says that this one is valid. If it's not then blockchain is fucked
eg:
https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC2 is not valid (change 3 to 2 at end)
https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3
if they are not valid addresses then that is a fatal flaw in the blockchain because it's showing as a valid address and you could send coins there
If you edit the address it comes back as checksum not valid, so it clearly does check the addresses and says that this one is valid. If it's not then blockchain is fucked
eg:
https://blockchain.info/address/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC2 is not valid (change 3 to 2 at end)
5KZnsvrXDcP7JFD7GCuZvifrbcBtK4kAe8nHx6ibktgvPJxs4Lp should be a valid private key. It doesn't include a zero, capital o, capital I or lowercase l.
it is the key for 1nchRAYGJofxyrkuhbL1CGYtD5x8Lowi5 according to blockchain
The checksum doesn't verify though.
blockchain seems to think it does
https://blockchain.info/address/1nchRAYGJofxyrkuhbL1CGYtD5x8Lowi5
The private keys people came up with are wrong. The chance of typing in random characters starting with 5 and getting a valid key are one in 2^32. It's not going to happen to anybody ever. Blockchain.info's wallet is just shit and ignores the checksum by the looks of things.
Prediction:
Code:
016982cea2101f1126034ecb8572e949604054bbb571d4e1b736b10ccee9c9ea
5KZnsvrXDcP7JFD7GCuZvifrbcBtK4kAe8nHx6ibktgvPJxs4Lp should be a valid private key. It doesn't include a zero, capital o, capital I or lowercase l.
it is the key for 1nchRAYGJofxyrkuhbL1CGYtD5x8Lowi5 according to blockchain
The checksum doesn't verify though.
blockchain seems to think it does
https://blockchain.info/address/1nchRAYGJofxyrkuhbL1CGYtD5x8Lowi5
The public address generated from the 32 bytes within the base 58 string we found (after the 0x80 byte) will obviously be valid. But the point is, the private key we find (in base 58 format) is not valid since the checksum bytes aren't correct. So the transformation is a bit off I think.
Again, I think there is either more to the shifting key or the algorithm is a bit off.
5KZnsvrXDcP7JFD7GCuZvifrbcBtK4kAe8nHx6ibktgvPJxs4Lp should be a valid private key. It doesn't include a zero, capital o, capital I or lowercase l.
it is the key for 1nchRAYGJofxyrkuhbL1CGYtD5x8Lowi5 according to blockchain
The checksum doesn't verify though.
blockchain seems to think it does
https://blockchain.info/address/1nchRAYGJofxyrkuhbL1CGYtD5x8Lowi5
5KZnsvrXDcP7JFD7GCuZvifrbcBtK4kAe8nHx6ibktgvPJxs4Lp should be a valid private key. It doesn't include a zero, capital o, capital I or lowercase l.
it is the key for 1nchRAYGJofxyrkuhbL1CGYtD5x8Lowi5 according to blockchain
The checksum doesn't verify though. It's called base58check because it has a checksum.
Jump to: