The Legend of Satoshi Nakamato, FINAL STEP PUBLISHED.... 4.87 BTC GRAND PRIZE!

[sini]

Might be of interest to some:

https://i.gyazo.com/a2ef6b183e635c79652dc72bf6df9d3c.png

could you give some more info?

Outer ring with 'orange' flames. C for Colored. A for 'abnormal'.

[1714948610]

1714948610

[1714948610]

1714948610

[1714948610]

1714948610

[Pan Troglodytes]

- DNA/RNA has 4 symbols ('atcg' or 'aucg'), is read three units (called bases) at a time, and there are 21 proteins (indicated by one letter abbreviations).
- The three drips on the chess piece could indicate a reading frame, which tells you how to chunk the bases. A different start point will lead to different amino acids, so this is important.
- DNA/RNA has stop codons, which indicate when to stop making a protein. These can either be delimiters between words, or be considered by their pigment based names (amber, ochre, opal).

seriously? don't tell me that coin-artist have a Phd in medicine or biochemistry
your post could be a good lecture, but of course not here.

Actually I am on CompNeuro side here. The DNA double helix was my first thought when I saw the picture with inner&outer ring of flames for the first time. I then discarded the idea, not being able to pair flames as DNA bases pair each other in a double helix. But the idea with the reading frame is definitely something that is worth a deeper thought and definitely it was not mentioned before here.

And how whould you actually write such a post for non-biologists so they can understand it? I think the form it has been written is OK too.

Might be of interest to some:

could you give some more info?

Outer ring with 'orange' flames. C for Colored. A for 'abnormal'.

thank you sini for posting that. It is of interest to some

[sini]

There is close to 98 in the outer ring if you include orange flames.

[feedo]

Actually I am on CompNeuro side here. The DNA double helix was my first thought when I saw the picture with inner&outer ring of flames for the first time

Actually i've discovered the DNA stop codons of that FrenchNeuron:
https://imgur.com/a/D5srG

i feel like coin-artist is watching this forum and laughing.

[CompNeuro]

When read according to the drips clockwise, the very start of the decode you get the following word relevant to the painting:
*MPSRI*
Prism.

[Pan Troglodytes]

[the reocurring patterns are as follow:

Actually, on second look, I don't think this is statistically significant.  Out of a sample of 25, you have 16 unique values which is not surprising.  You're bound to get repeats even if you look at random data.  If the sample size was much larger and you still got few values, that would mean something more I think.  But that doesn't mean the thin/thick data can't also be part of the solution.

well I tried to calculate the probabilities analytically but I failed, it turned out to be quite complex

Then I ran a simulation in R, drawing 25-tuples from 64 pool with repeats, and out of a milion runs only 4544 had 16 or less unique values. So call it what you will, it is an anomaly to me - anomaly at worst, but human creation hopefully

[zbyszek2]

If someone is interested in symbols:

https://imgur.com/gallery/F22X4

of course they are very subjective

[feedo]

When read according to the drips clockwise, the very start of the decode you get the following word relevant to the painting:
*MPSRI*
Prism.

How did you read them that way?

[massl]

https://imgur.com/ysbPyGB

k09 = Duckduck it: Aeronautical maps? As overlay?
35 or 38, 76, 15 or 95...() = positions on map (x°/y°)?

"bits in dust" = Some information in small transactions to 1FLAMEN6rq2BqMnkUmsJBqCGWdwgVKcegd (especial those only containing binary 0,1)

[feedo]

https://imgur.com/ysbPyGB

k09 = Duckduck it: Aeronautical maps? As overlay?
35 or 38, 76, 15 or 95...() = positions on map (x°/y°)?

"bits in dust" = Some information in small transactions to 1FLAMEN6rq2BqMnkUmsJBqCGWdwgVKcegd (especial those only containing binary 0,1)

i can't see K09 in the image,
DuckDack it? 

[massl]

i can't see K09 in the image,
DuckDack it?  

Top left corner (if you shrink it even more it becomes more obvious)
Might also say k5, L5 or nothing at all.


https://duckduckgo.com/?q=k09

[feedo]

If someone is interested in symbols:

https://imgur.com/gallery/F22X4

of course they are very subjective

i think that many symbols and characters are embedded in the image that way, but as you said they are very subjective, the rabbit mentioned those eom ea and i agree with you that there is Y, A, 8, S, E but i disagree that there is 4 (i see i or V) or that big O and M (maybe W)
and even if we all see the same characters, the problem is in what order we should arrange them! there are infinite possibilities!

and yes i am interested in symbols or anything other than those fucking trolling flames that i fed up with them, i think that they made those flames to distract our attention from the first step.

[RealOnTheMF]

This thread seems pretty active again, so I figured I'd post some recent findings in hopes we can all solve this thing.

I found a bacon (v2) message within the height bit-stream that when decoded appears to be "thefm auriskeyfile". The message is clearly incomplete/incorrectly decoded. We're not even convinced the message is an intended message or just a massive coincidence. A script to decode this message as-is, is below.

We have a solving team going right now that are all working together to solve this. If anyone's interested in joining, send me a PM. We're trying to round out our skill-base.

If this info helps you solve it, please be kind and tip our team: BTC address: 1Giz1ZV8rgk4UfMoscsjQiTp4cXmdSoxN2

Matlab/Octave code:

Code:

%% 1FLAMEN6 - decode "thefm_auriskeyfile" message
% Written by OnTheMF

tall            = 1; % Tall flame bit-value
tiny            = 0; % Short flame bit-value
ribbon_short    = 0; % Short ribbon bit-value
ribbon_long     = 1; % Long ribbon bit-value

%% Dataset

% Key with ribbons
rbn_l2r = [ ribbon_short, ribbon_long, ribbon_long,...
            ribbon_short, ribbon_long, ribbon_short ];

% Outer top segment
ot_l2r = [ tiny, tiny, tall, tall, tiny, tall, tall, tiny, tiny, tall,...
           tall, tall, tiny, tiny, tall, tall, tiny, tall ];
% Outer right segment
or_t2b = [ tiny, tiny, tall, tall, tall, tall, tiny, tiny, tiny, tall,...
           tiny, tall ];
% Outer bottom segment
ob_r2l = [ tiny, tiny, tall, tall, tall, tall, tall, tiny, tall, tall,...
           tiny, tall, tiny, tiny, tiny, tall ];
% Outer left segment
ol_b2t = [ tiny, tall, tall, tiny, tall, tall, tiny, tall ];
% Inner top segment
it_l2r = [ tiny, tall, tall, tiny, tall, tall, tiny, tall, tall, tiny,...
           tall, tiny, tiny, tiny, tall, tiny, tall, tall, tiny, tall,...
           tall, tiny, tall, tall, tiny, tiny, tall, tall];
% Inner right segment
ir_t2b = [ tall, tall, tiny, tall, tall, tall, tall, tall, tiny, tall,...
           tall, tiny, tall, tall, tiny, tall, tall, tall, tall, tall,...
           tiny, tiny, tall, tiny ];
% Inner bottom segment
ib_r2l = [ tall, tiny, tiny, tiny, tall, tall, tall, tiny, tiny, tiny,...
           tall, tiny, tall, tall, tiny, tall, tall, tall, tall, tall,...
           tiny, tall, tall, tall, tall, tall, tiny, tall, tall, tall,...
           tall, tall, tiny ];
% Inner left segment       
il_b2t = [ tiny, tall, tall, tall, tiny, tiny, tall, tall, tiny, tall,...
           tall, tiny, tall ];

% Reverse our segments for easy manipulation
ot_r2l = fliplr(ot_l2r);
or_b2t = fliplr(or_t2b);
ob_l2r = fliplr(ob_r2l);
ol_t2b = fliplr(ol_b2t);
it_r2l = fliplr(it_l2r);
ir_b2t = fliplr(ir_t2b);
ib_l2r = fliplr(ib_r2l);
il_t2b = fliplr(il_b2t);

%% Decode keyfile message
encrypted_track = [ib_l2r, il_t2b, ir_t2b, it_r2l, ot_r2l, ob_l2r];

% Skip first bit
decrypted_track = vectorxor(encrypted_track(2:end), rbn_l2r);

% Generate indexes for every fifth bit (circular buffer)
message_indices = mod((0:(length(decrypted_track)-1)) * 5, length(decrypted_track)) + 1;

% Get the message bits in the correct order
message_data = decrypted_track(message_indices);

% Decode and display message
decodebacon(message_data)

%% Helper functions
% xor a vector or matrix with a given key vector
function [ret] = vectorxor(x,key)
    % Pre-allocate return variable
    ret = zeros(size(x,1),size(x,2));

    % Generate 1:1 vector for xor function
    copies = ceil(size(x, 2) / length(key));
    xkey = repmat(key, 1, copies);
    xkey = xkey(1:size(x, 2));

    % Iterate through each row of input data
    for i = 1:size(x,1)
        ret(i,:) = xor(x(i,:), xkey);
    end
end

% Decode a Bacon v2 string (base 26) - invalid characters mapped to space
function [ret] = decodebacon(x)
    letters = 'abcdefghijklmnopqrstuvwxyz ';
    
    % Only decode 5-bit sequences
    vals = x(1:end - mod(length(x), 5));
    
    % Convert to base 10 values
    dec = sum(reshape(vals, 5, length(vals) / 5) .* (2 .^ (4:-1:0))')';
    
    % Return corresponding string
    ret = letters(min(dec'+1, length(letters)));
end

[googas]

I think I have figured out what the chess pieces are about. Was that figured out years ago, I didn't see it mentioned here yet..?

[itod]

This thread seems pretty active again, so I figured I'd post some recent findings in hopes we can all solve this thing.

I found a bacon (v2) message within the height bit-stream that when decoded appears to be "thefm auriskeyfile".

This is a  real breakthrough, thanks for sharing this.

Edit: Where did you find the code for bacon? Wrote it yourself?

[itod]

I think I have figured out what the chess pieces are about. Was that figured out years ago, I didn't see it mentioned here yet..?

No, no one has said anything provable about the chess pieces, just theories. Care to say what you think they mean?

[kn0w0n3]

This thread seems pretty active again, so I figured I'd post some recent findings in hopes we can all solve this thing.

I found a bacon (v2) message within the height bit-stream that when decoded appears to be "thefm auriskeyfile". The message is clearly incomplete/incorrectly decoded. We're not even convinced the message is an intended message or just a massive coincidence. A script to decode this message as-is, is below.

We have a solving team going right now that are all working together to solve this. If anyone's interested in joining, send me a PM. We're trying to round out our skill-base.

If this info helps you solve it, please be kind and tip our team: BTC address: 1Giz1ZV8rgk4UfMoscsjQiTp4cXmdSoxN2

Matlab/Octave code:

Code:

%% 1FLAMEN6 - decode "thefm_auriskeyfile" message
% Written by OnTheMF

tall            = 1; % Tall flame bit-value
tiny            = 0; % Short flame bit-value
ribbon_short    = 0; % Short ribbon bit-value
ribbon_long     = 1; % Long ribbon bit-value

%% Dataset

% Key with ribbons
rbn_l2r = [ ribbon_short, ribbon_long, ribbon_long,...
            ribbon_short, ribbon_long, ribbon_short ];

% Outer top segment
ot_l2r = [ tiny, tiny, tall, tall, tiny, tall, tall, tiny, tiny, tall,...
           tall, tall, tiny, tiny, tall, tall, tiny, tall ];
% Outer right segment
or_t2b = [ tiny, tiny, tall, tall, tall, tall, tiny, tiny, tiny, tall,...
           tiny, tall ];
% Outer bottom segment
ob_r2l = [ tiny, tiny, tall, tall, tall, tall, tall, tiny, tall, tall,...
           tiny, tall, tiny, tiny, tiny, tall ];
% Outer left segment
ol_b2t = [ tiny, tall, tall, tiny, tall, tall, tiny, tall ];
% Inner top segment
it_l2r = [ tiny, tall, tall, tiny, tall, tall, tiny, tall, tall, tiny,...
           tall, tiny, tiny, tiny, tall, tiny, tall, tall, tiny, tall,...
           tall, tiny, tall, tall, tiny, tiny, tall, tall];
% Inner right segment
ir_t2b = [ tall, tall, tiny, tall, tall, tall, tall, tall, tiny, tall,...
           tall, tiny, tall, tall, tiny, tall, tall, tall, tall, tall,...
           tiny, tiny, tall, tiny ];
% Inner bottom segment
ib_r2l = [ tall, tiny, tiny, tiny, tall, tall, tall, tiny, tiny, tiny,...
           tall, tiny, tall, tall, tiny, tall, tall, tall, tall, tall,...
           tiny, tall, tall, tall, tall, tall, tiny, tall, tall, tall,...
           tall, tall, tiny ];
% Inner left segment       
il_b2t = [ tiny, tall, tall, tall, tiny, tiny, tall, tall, tiny, tall,...
           tall, tiny, tall ];

% Reverse our segments for easy manipulation
ot_r2l = fliplr(ot_l2r);
or_b2t = fliplr(or_t2b);
ob_l2r = fliplr(ob_r2l);
ol_t2b = fliplr(ol_b2t);
it_r2l = fliplr(it_l2r);
ir_b2t = fliplr(ir_t2b);
ib_l2r = fliplr(ib_r2l);
il_t2b = fliplr(il_b2t);

%% Decode keyfile message
encrypted_track = [ib_l2r, il_t2b, ir_t2b, it_r2l, ot_r2l, ob_l2r];

% Skip first bit
decrypted_track = vectorxor(encrypted_track(2:end), rbn_l2r);

% Generate indexes for every fifth bit (circular buffer)
message_indices = mod((0:(length(decrypted_track)-1)) * 5, length(decrypted_track)) + 1;

% Get the message bits in the correct order
message_data = decrypted_track(message_indices);

% Decode and display message
decodebacon(message_data)

%% Helper functions
% xor a vector or matrix with a given key vector
function [ret] = vectorxor(x,key)
    % Pre-allocate return variable
    ret = zeros(size(x,1),size(x,2));

    % Generate 1:1 vector for xor function
    copies = ceil(size(x, 2) / length(key));
    xkey = repmat(key, 1, copies);
    xkey = xkey(1:size(x, 2));

    % Iterate through each row of input data
    for i = 1:size(x,1)
        ret(i,:) = xor(x(i,:), xkey);
    end
end

% Decode a Bacon v2 string (base 26) - invalid characters mapped to space
function [ret] = decodebacon(x)
    letters = 'abcdefghijklmnopqrstuvwxyz ';
    
    % Only decode 5-bit sequences
    vals = x(1:end - mod(length(x), 5));
    
    % Convert to base 10 values
    dec = sum(reshape(vals, 5, length(vals) / 5) .* (2 .^ (4:-1:0))')';
    
    % Return corresponding string
    ret = letters(min(dec'+1, length(letters)));
end

I'm curious if you know which flames in what order produced that? Should have been 90 flames right.

Guess i'm gonna start trying to xor flame lengths with the ribbon and try to reproduce that.

[crax0r]

Regarding what RealOnTheMF said, the message can be also "THEFMSAURISKEYFILE"

Below are the flame sides aligned in the order that results in the message above.

a = inner top CW
b = inner right CW
c = inner bottom CW
d = inner left CW
e = outer left CW
f = outer bottom CW
g = outer right CW
h = outer top CW

ABCDEFGH same, but read order is CCW (counter clock wise)

In the decoder-stream, only 6 out of 8 sides are used in the following fashion: CDbAHF

Then, start reading every 5th bit from the stream until you get the the end, then start over from the beginning, +4 bits... then from the beginning +3 bits, then +2 and +1

Everything has to be xored by 011010. You can either ignore first bit of C, or last bit of F, total length of this stream must be 131 bits. Make sure xor key aligns like below.

Code:

#     C CCCCCC CCCCCC CCCCCC CCCCCC CCCCCC CCDDDD DDDDDD DDDbbb bbbbbb bbbbbb bbbbbb bbbAAA AAAAAA AAAAAA AAAAAA AAAAAA AHHHHH HHHHHH HHHHHH HFFFFF FFFFFF F FFFF
#011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010
#       T    T     T     T     T     H     H    H     H     H     E     E     E    E     E
#                                                                                              F     F     F     F    F     M     M     M     M     M    S        
#     S     S     S     S     A     A    A     A     A     U     U     U    U     U     R     R     R     R    R   
#                                                                                                                    I     I     I     I     I    S     S     S  
#
#          S     S
#                      K     K    K     K     K     E     E     E    E     E     Y     Y     Y     Y    Y  
#                                                                                                             F     F     F     F     F    I     I     I     I
#         I     L     L    L     L     L     E     E     E    E     E

[RealOnTheMF]

I'm curious if you know which flames in what order produced that? Should have been 90 flames right.

Guess i'm gonna start trying to xor flame lengths with the ribbon and try to reproduce that.

It's given by this line in the code:

Code:

encrypted_track = [ib_l2r, il_t2b, ir_t2b, it_r2l, ot_r2l, ob_l2r];

i = inner
o = outer
l = left
r = right
b = bottom
t = top
r = right

So, ib_l2r means inner bottom left to right.

[RollBit.io]

Really wish I had the knowledge to figure all of this out. Looks so cool