 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
Love, sidekick.
Later.  |
|
|
|
btw... the solution is.... one small now is tall... so exchange w with W in the 51 character string...
That's fucking stupid. It's unrelated to any of the information given. Why was the shit on the right of the image then? The OP made a typo in the given key and somehow that's supposed to be part of the ARG? I dont even get it... z69JZqlJn862D1ndx7oLVEMmVOlP1zewEeUCrsI7Roahzpeny7P switch(w,W) -> z69JZqlJn862D1ndx7oLVEMmVOlP1zeWEeUCrsI7Roahzpeny7P and then what? shift 6EQUJ5 times? ... 5KZnsvrXDcP7JFD7GCuZvifrbcBtK4kke8nHx6ibktgvPJxs4Lp Where is the palindrome hint? I am confused and go to sleep maybe someone is nice and write a "for dummies" how to solve the last step so I can finish the pdf. You get "6EQUJ5", turn it into integers using the pattern in Crops.jpg. 6EQUJ5 = (decoded) = 6,14,26,30,19,5 You change the w to a W in the string (who the would have thought of that?) z69JZqlJn862D1ndx7oLVEMmVOlP1ze[W]EeUCrsI7Roahzpeny7P You shift the key in Wow.jpg by the numbers sequentially, looping once you run out 5KZnsvrXDcP7JFD7GCuZvifrbcBtK4kAe8nHx6ibktgvPJxs4Lp You then add 0.35% more to your horde of BTC like Gatekeeper did.  |
|
|
|
Yeah that was very anticlimactic...
That's understating it. Somebody added 0.35% more to their pile of BTC. Yay.  |
|
|
|
So what was it? And why does somebody with a million dollars need to play games like this?  I mean come on, they're on the top 100 richest addresses. |
|
|
|
Ok, here's some collected thoughts (yet again). What have we got?
1) 0=0A=10BABYA=36 (0=0 A=10 a=36)
I am 95% certain this is the description of a mapping of [0-10A-Za-z] to numbers starting with 0. It tells you the three starting points of each substring in the list. All other interpretations that I have seen make no sense to me.
This mapping could have two uses: character shifting or transformation.
2) The hidden XMP data.
This seems to cross out all the data on the left. It also crosses out the 51 byte string. Lastly, it appears to highlight the positional codes in the RT. ASCEN section (or possibly cross them out). It even points at the 6 in '36' which seemed noteworthy since 6 shifts is what's needed to turn the z into a 5. OP went to the trouble to hide this XMP data so we should assume that it must somehow hint at the solution.
3) z69JZqlJn862D1ndx7oLVEMmVOlP1zewEeUCrsI7Roahzpeny7P
Most of us have shifted the hell out of this in various straightforward ways. Several of us have used the WOW signal strength as an alphabet cipher key, and at least a couple of us have used series of timecodes over on the right as a cipher key. It either doesn't want to want to turn into a private key address, or we're barking up the wrong tree.
Interestingly enough, it appears to be vigorously crossed out by the XMP. This made me wonder if there is some sort of 3733T instructional message hidden in it, but I wonder that less and less with OP's more recent hints.
4) CHANNEL NUMBER (TWO DIGITS, WRITTEN VERTICALLY)
This was recreated by OP for this image, but was text from the original document. It's possible that OP preserved it as some sort of hint. That said, most instances of "two digits, written vertically" are crossed out by the XMP.
5) Some timecode and other data on the right
This stuff is not crossed out by the XMP, some of it seems to be specifically called out by the XMP, but it's not clear what to do with it. It seems worth calling out because I think it's been largely ignored.
6) Various OP clues
"Final countdown" - Either we're near the end, or it is somehow referring to the time codes that are called out in the XMP.
wow + crops - we need to use something from the Crops puzzle. I am assuming the character map, but could there be more?
6EQUJ5 - This is the Wow signal strength. We must need to use this somehow, but it doesn't work as a key.
No sha or hash needed - any transforms we solve will be relatively straightforward
the prize awaits you
the final palindrome is key: hints at wow being a cypher key?
once small is now tall: all uppercase?
Haha, yes, well about that. Lets list the invalid keys shall we? https://mega.co.nz/#!GVVHwJLT!WDLXR8yQTiJiYeHjXzbm93xiHxgcF_vIhMWToLzjpxI I'm getting nowhere fast. |
|
|
|
I test both, but O looks to be valid.  If the font is the same as the word TWO above it then it's a 0
It's a different font.   Same as Mirth23, I've tried hundreds of mutations of the strings with no result. |
|
|
|
This program, for example transforms the "z69JZ..." string into 5KZnsvrXDcP7JFD7GCuZvifrbcBtK4kAe8nHx6ibktgvPJxs4Lp can you recheck please... is your result ok? cause i get a different result: 5KZnsvrXDcP7JFD7GCuZvifrbcBtK4kAe8nHx6ibktgvPJxs4Lp <-your 5KZnsarXDcPgJFD7GfuZvifEbEBtKLkAe8nSx6ibkygvPJxr4Lp <-my or i have some error in my code, i dont know, cant find it...  Yours is wrong somehow. I can confirm that my code returns the same result as alphabetacanary's. |
|
|
|
The ADDRESS is valid but no wallet should have imported the PRIVATE KEY because it is invalid. |
|
|
|
yes, its compressed: 5KZnsvrXDcP7JFD7GCuZvifrbcBtK4kAe8nHx6ibktgvPJxs4Lp
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. |
|
|
|
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. 0ee3318601b0ed03b4e12f4af8ab756bd0347b6b2bef4fbd1ff2fdd1ce6e93a5 |
|
|
|
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/1MtR9nBGfWBLY23q4dRGRjjzBBiEdxRmC3if 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. |
|
|
|
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/1nchRAYGJofxyrkuhbL1CGYtD5x8Lowi5The 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: 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. It's called base58check because it has a checksum. |
|
|
|
echo -n "5KZns" | openssl dgst -sha256
b2a950ff612a89d7fd2effa6d75acced098d9d141a559029629080c092aedf14
Yep. That's what I came up with. You can't get a sane private key out of it. I think this is right, I don't know why it doesn't give the correct key though. I was just going to post the exact same findings, except that at my end, I got the same key and it does convert to a public key.
It doesn't, it's not valid base58. |
|
|
|
How about a character shift of only 30? Didn't the SETI article indicate that the Wow signal was only a 30 (unknow unit of measure) deviation from the standard background noise at its highest point? May not have anything to do with it, who knows.
Nope. Tadn3KFnHcaWhVH7RbIpziqGzsFtVT8Qi8ygLMmbvI4BTJ8HSbt
Vcfp5MHpJecYjXJ9TdKr1ksI1uHvXVASkA0iNOodxK6DVLAJUdv |
|
|
|
Yeah this is doing my head in, been trying a lot of character shift stuff with no luck...
I noticed that there are the same number of letters in "z69JZqlJn862D1ndx7oLVEMmVOlP1zewEeUCrsI7Roahzpeny7P" as there are numbers in the downward column in Wow.jpg (41 characters).
There's 51 characters in the top string. |
|
|
|
There is one problem with online hashing, at least from personal experience, hashing is done on the ASCII, or on the binary. So I'm not sure if using online tools is good.
In this case the OP used ASCII mode for a all hashes, it messed me up for ages until I realised what was going on. I've pretty much given up at this point. There's no fun in writing endless permutations of python scripts that shuffle letters around, hashes them, tries to decode them as private keys, and fails time and time again. Whatever the puzzle is designed to do is nothing that I can come up with, nor my partner, nor anybody else it seems. @shorena sieht aus als ob du deutsch kannst,ich kann nicht immer genau das was ich meine in english ausdrücken,wär cool wenn man sich mal austauschen könnt und dann das ganze hier in english posted
 Sorry, had to  |
|
|
|
They where clues. I made a summary of them here: https://bitcointalk.org/index.php?topic=661781.msg7552956#msg7552956the only part I missed IIRC was the "SOCLOSE" hint. I believe they all hinted at binary. "SOCLOSE" was meant to make us backtrack, same as the reverse counting. Not sure why OP left some oft the numbers out. Maybe there is a reference with the post numbers where binary was mentioned. I missed all of the blockchain.info transaction comment hints. So many people seem to think that the "notes" on their website are part of Bitcoin due to the way blockchain.info labels them, but they're totally not. Nobody but users of that website can see them. Until I looked back at comments here I don't even know the OP thought the same. |
|
|
|
I guess I am back on the thought that if the 51 char string is not something we can shift into a private key, then it must be some kind of 37337 clue and we're looking for a spoon in a haystack with bitshifts and the like.
We have only 41 characters on the right, and 51 characters above. I can't make heads nor tails of what the aim is even meant to be. Even they were the same length I would be slightly happy, but as it is I can do nothing with them. Not even a clue what is going on in the OPs mind with this one. |
|
|
|
|
