Topic: The Legend of Satoshi Nakamato, FINAL STEP PUBLISHED.... 4.87 BTC GRAND PRIZE! - page 32. (Read 108521 times)

please bear in mind that it does not have to be 17 intended matching digits. It as well may be that the intended number is 16 and the last one is coincidental.

Also, I was thinking that the two streams do not necessarliy have to be equal, they may be complementary (in the sense, that 0/1 is switched in the other stream, the substitution of color with 1 or 0 is arbitrary after all - at that point, at least) suggesting the double helix (in line with CompNeuro's way of thinking). Maybe the top left corner is the beginning of the folded two flame high, 76 flame long double sequence.

+ 17 leaves…

I have this luck today that there is my alter ego (regards, clanestutr) paraphrasing the same exact minute what I was saying in my post (which was cool and unexpectedly a little creepy) and then there is this troll copying my post an hour later. I am reporting this one

That's two more troll accounts to ignore....

amazing observation! And the more amazing is the fact that it is so simple and everybody has been staring at those flames for more than 3 years!

interesting read

Another observation re: data.

If you look at the first 17 bits of the inner track top color (l->r) against the first 17 bits of the outer track top color in same direction, they are identical.  I know you'd expect repeats even in random data but 17 bits in a row starting right on the boundary?  Odds are 1 in 131072 that'd happen?

inside colors
"000101010010110110", // outside track top, left to right

outside colors
"0001010100101101110010110000", // inside track top, left to right

They've been able to encode information into bitcoin public addresses (i.e., the snow poem). It's probably not beyond their capabilities to construct an arbitrary bitstream (and keep in mind, we're only talking about just the flame heights here) with enough sophistication to encode something else.


I agree -- I believe this is really just a coincidence. But there must be a methodology for deciphering all these 1s and 0s, and so far, no one appears to have had much luck in getting a foothold on it. It's interesting, and it's worth exploring.

Maybe they got off somewhere in transcribing the pattern ... and then again ... and then again ...

 

my thinking exactly, especially the keyFILE part

EDIT: actually, on the second thought and the second reading, my thinking entirely

guys, I would hate to cool your optimism down, but of course you realize that every second binary digit (5 of them coding every baconian letter) belongs to that crazy 0x1x1x pattern that is constant throughout the flames. It can't imagine the creator choosing letters and wording so carefullty, so that she can convey her intended message but chosen letters would not break the constant pattern.

On the other hand, it makes much sense what RealOnTheMF said, that it is a massive coincidence: doing the exhaustive search of all possible permutations of all subsets of 8 flame segments, accepting CW or CCW order of each segment, skipping every 1 flame or 2 or 3 or 4 or 5 or whatever threshold he chose as the upper limit, applying the 011010 XOR or not, excluding first k flames when applying the XOR (k=0,1,etc.) - what I am thinking that there were so many bit streams tested (milions would be my guess), that he simply stumbled upon the words that made sense. Not entirely made sense, as you can see. Even if the 'colour' is what was really intended, we don't have to do with a key file, but with a key itself, so the message really is more or less senseless.

Whoops. Yeah, missed that first time around.

The more I play around with the XOR patterns and permutations of row order/orientations, the less I think that these words are meaningful. It's a fairly unlikely coincidence, I admit, for "is" "the" & "keyfile" to appear, but those aren't particularly long words, with "keyfile" being the only exception.

But, perhaps more important--why would they use the term "keyfile" (or "key file") at all? The result wouldn't be a file, it would be a private key. I don't see the puzzle creators using a phrase like "keyfile" when "privkey" or even "key" would suffice, especially when "keyfile" is technically innacurate.

Not to mention generating this phrase requires a series convoluted steps:

1. Arrange 6 out of 8 rows in a pattern that doesn't appear anywhere else in the painting (to be fair, it may be undiscovered, but the bishop/knight explanation breaks down, for me. It's almost certainly a queen rather than a bishop, and the knight's movement is precise in a way that doesn't reflect the jumping around necessary for this row order/orientation)

2. XOR with 011010, but only after you skip the first bit entirely.

3. Cycle back to the beginning of the 6 rows and rinse/repeat.

What about the 011 pattern that tracks through all of the rows without deviation? Sure, it's possible to encode words and still have that pattern exist, but it's a hell of a lot harder, and--considering the route you have to take to generate the above phrase, seemingly unnecessary.

There are a lot of possible permutations, even between 6 out of 8 rows (upwards of 20,000). Maybe if "keyfile" made more sense to me, but I say it's just coincidence that these words exist here. Hell, look at how many scholars tried to prove Bacon was Shakespeare because they "found" his signature hidden in the texts. Everywhere. Those had equally convoluted rule-sets / approaches.

LOL, the key file is not in those fucking trolling flames
And the creators could withdraw their btc any moment and no one could track them if they did that
In the end It's crypto currency and no one could track them

theflamesiskeyfile

The symmetries in the ordering seems fairly consistent. Plus the chance you'd find that sequence of those words (and a missing word) is fairly low.


This would explain the high frequency of repeating 6-gram's being consistent with a vigenere cipher (xor). Because you have multiple repeating characters in the message.

I've decoded the dusty inputs to the address. It says "BERCAICAREA" = french "bercail ce area" = fold THIS area (edit: see my correction below).
So, happy folding.

Only few lines of code needed.


(decode bacon cipher online)

EDIT: I have just been corrected, that "bercail" does not mean "to fold":

Read the (interpretations) in this page:
https://en.m.wikipedia.org/wiki/Robert_Chester_(poet)

Interesting -- and that would make sense too. The binary pattern we *have* is:


…and the one that *would* say "thecolouriskeyfile" is:

Differences in bold. Maybe they got off somewhere in transcribing the pattern.

a python (2.7) script for you (not the prettiest but it works):

output:


@RealOnTheMF - I'm impressed!