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

[mirth23]

If you google all of the capital letters, "CRYPTO JS", it turns out to be a Javascript crypto library.

One of the algorithms implemented by Crypto-JS is called Rabbit: https://code.google.com/p/crypto-js/#Rabbit

Rabbit is defined in RFC4503. I tweeted it earlier and @TR3N47Y responded "Indeed."

I've tried a number of different ciphertext/key combinations and am a bit stymied at the moment.

[frisco]

Umm transcribing 20 and 09 to 0 and 1 leads to 2 different results if you include or not the spaces between the text.
I think that it should be included as doing so gives you a result starting with "0a 54" or "\nT".

But in any case there are too much white spaces, so probably we need to find a way or removing some of them.

If the result is ciphered with rabbit then the output should be more random so it is almost impossible to get so many 0.
If the result is plaint text it can have some bias but still it is too high (almost 4 to 1).
Also you can try inverting 20 and 09 values but the it seems that 20 as 0 gives a more text like result.

Transcription without the spaces between words (hand made)

Code:

10100101 01000000 10000000 01000010 00000010 00000010 00100001 00010101 10010000 10000010 10000101 01001000 00001000 00100000 10001000 10010010 00000010 00000100 00101000 00001000 00000000 00010001 10000100 00001000 00010000 00010100 10010000 01000000 10001000 10011000 00001000 00001000 01000000 10100010 00000010 00010001 01000001 00000001 00001001 00000010 00000100 01000000 10000001 01100010 00000010 00100001 00001100 00000010 11000010 00000100 11000100 01000000 00100000 01000010 00000010 00000010 00001000 00010100 00001000 00001000 01100000 00000000 10000001 00000100 00000100 00001000 00001000 10000000 00100100 00011000 01000001 00000001 00010100 00001001 00010000 00010001 11000000 01001011 00000010 00000100 00000100 00001000 10000100 00000101 00000000 00000100 00010000 00010110 00001100 00100000 00110000 10000100 10000100 00100000 01000000 01000000 

Transcription with the spaces between words (automated)

Code:

00001010 01010100 00001000 00000000 01000010 00000010 00000010 00100001 00000010 11001000 01000001 01000010 10100100 00000100 00010000 01000100 01001000 00000000 00100000 01000010 10000000 10000000 00000000 00100011 00001000 00010000 00100000 00000100 10010000 01000000 10001000 10011000 00001000 00001000 01000000 10100010 00000000 00100001 00010100 00010000 00010000 00010010 00000100 00001000 10000001 00000000 01100010 00000010 00100001 00001100 00000010 11000010 00000100 11000100 01000000 00000010 00000100 00100000 00100000 00100000 00010000 00101000 00010000 00010000 11000000 00000000 01000000 10000010 00000010 00000100 00000100 01000000 00010010 00001100 00100000 10000000 10001010 00000000 00100100 01000000 01000110 00001000 00001001 01100000 01000000 00100000 00100000 01000100 00100000 00101000 00000000 00100000 10000000 10110000 01100001 00000000 10000100 00100100 00100001 00000010 00000010 00010000 

The text ends with 09 and 3 null characters (000000) and in both cases the length is too short, event if it is ciphered that's imposible as it works in blocks of 16 bytes, that's another reason that leads me to think that we should remove some bits.

[Darkstone2]

that we should remove some bits.

Perhaps '347' has something to do with this?

[mirth23]

I'm stuck on getting Crypto-JS to work for our use case. I'm doing things like the following:

Code:

cipher=CryptoJS.enc.Hex.parse(paddinghex); // create a WordArray based on a hex version of the padding
alert(cipher.toString(CryptoJS.enc.Base64)); // check for well-formed Base64
cparms = CryptoJS.format.OpenSSL.parse(cipher.toString(CryptoJS.enc.Base64)); // create CipherParams
cparms.iv = '0000';
cparms.key = 'wombats';
var decrypted=CryptoJS.Rabbit.decrypt(cparms,key,{iv: my_iv});
alert('decrypt: ' + decrypted.toString(CryptoJS.enc.Latin1)); // display output

Despite explicitly setting an iv and key, I get a different result every time I decrypt. At first I thought it was a problem with something randomized, like the iv or salt, but this issue occurs even when I'm explicitly setting the iv as in the example above. As far as I can tell, Rabbit doesn't use a salt. Has anyone been able to get consistent results out of it?

I'm only having trouble when I try to construct my own ciphertext. I can successfully encrypt then decrypt with Rabbit using Crypto-JS using the following because whatever I'm missing is automagically handled in the CipherParams that encrypt() built:

Code:

var msg="this is a friendly message.";
var key="keyword";
var encrypted=CryptoJS.Rabbit.encrypt(msg,key);
var decrypted=CryptoJS.Rabbit.decrypt(encrypted,key);
alert('decrypted: ' + decrypted.toString(CryptoJS.enc.Latin1));

[slaveforanunnak1]

that we should remove some bits.

Perhaps '347' has something to do with this?

I tried fiddling with that..no luck.

[RussHarben]

Maybe we need a break.... a change of pace.

Going back to the Ghostrider / Fantastic Four idea. I, ahem, "found" a copy of issue #347.  I haven't read it all yet...but it's maybe there are some clues inside.

You'll need a CBR reader.

https://www.dropbox.com/s/n702i0j08j6od2m/Fantastic%20Four%20V1%20347.cbr?dl=0

[frisco]

I'm stuck on getting Crypto-JS to work for our use case. I'm doing things like the following:

Code:

cipher=CryptoJS.enc.Hex.parse(paddinghex); // create a WordArray based on a hex version of the padding
alert(cipher.toString(CryptoJS.enc.Base64)); // check for well-formed Base64
cparms = CryptoJS.format.OpenSSL.parse(cipher.toString(CryptoJS.enc.Base64)); // create CipherParams
cparms.iv = '0000';
cparms.key = 'wombats';
var decrypted=CryptoJS.Rabbit.decrypt(cparms,key,{iv: my_iv});
alert('decrypt: ' + decrypted.toString(CryptoJS.enc.Latin1)); // display output

Despite explicitly setting an iv and key, I get a different result every time I decrypt. At first I thought it was a problem with something randomized, like the iv or salt, but this issue occurs even when I'm explicitly setting the iv as in the example above. As far as I can tell, Rabbit doesn't use a salt. Has anyone been able to get consistent results out of it?

I'm only having trouble when I try to construct my own ciphertext. I can successfully encrypt then decrypt with Rabbit using Crypto-JS using the following because whatever I'm missing is automagically handled in the CipherParams that encrypt() built:

Code:

var msg="this is a friendly message.";
var key="keyword";
var encrypted=CryptoJS.Rabbit.encrypt(msg,key);
var decrypted=CryptoJS.Rabbit.decrypt(encrypted,key);
alert('decrypted: ' + decrypted.toString(CryptoJS.enc.Latin1));

The last method can be tested online here: http://uttool.com/encryption/rabbit/default.aspx

I have not tested it but reading the source code of crypto.js if you want to use a custom IV you must use:

Code:

var decrypted=CryptoJS.Rabbit.decrypt(msg,key,{iv: my_iv});

[mirth23]

Despite explicitly setting an iv and key, I get a different result every time I decrypt. At first I thought it was a problem with something randomized, like the iv or salt, but this issue occurs even when I'm explicitly setting the iv as in the example above. As far as I can tell, Rabbit doesn't use a salt. Has anyone been able to get consistent results out of it?

I was incorrect, it turns out there IS a salt for Rabbit ciphertext in this implementation.

[Moneyunmaker]

Satoshi is trying to tell us something 

[Darkstone2]

Rabbit does use a salt (= IV?), and a key. Both of which have to be exactly 16 bytes, otherwise it will insert apparently random data.

Unfortunately my javascipt is pretty rusty. Perhaps later in this ARG i can dust of wabbitemu and code some assembly

[rock_collector]

While some of you are working on the rabbit cipher, I thought I would throw out some (of my wayy too many) random musings and maybe they will jog some thoughts:

1ExmJbvEVbimN67zUbEdthezBKSwvNzpw7 - (Unspent) 0.00001 BTC
1ACcZsb1xgKLFwWTwjEQw5Va4artxbhVHY - (Unspent) 0.00001 BTC
14r1UWeCGbTuhnEMX9xXkfauZ5MsGQaHAP - (Unspent) 0.00001 BTC
1PENSUMKNPVCjChPzUqF32eA6gSUdMoJMZ - (Unspent) 0.00001 BTC
16PWqtrP3XtEYwVirHEREPopoJG5M8RtKa - (Unspent) 0.00001 BTC

[ https://blockchain.info/address/1PENSUMKNPVCjChPzUqF32eA6gSUdMoJMZ ]

Could "the art we pen here" refer to a comic book? In a twitter conversation last week between @PO347 and @TR3N47Y  https://twitter.com/PO347/status/507740423180521472 , @TR scolds @PO for never reading "BOOKS," so I assume there will be a reference to a book at some point. (I went down a rabbit hole for a while on that one. @PO refers to herself as a "morphodite," which is a comic slang word for hermaphrodite, from To Kill a Mockingbird. Perhaps we'll learn more about that later?)

Anyway, curious about the line from the poem "The hunter and the prey," I simply googled "the hunter and the prey," which led first to the site Fanfiction.net , where fans (we? in "the art we pen"?) write their own extensions to popular cartoon series. "The Hunter and the Prey" is a fan fiction story written to extend "Avatar: The Last Airbender." [ https://www.fanfiction.net/s/2377707/1/The-Hunter-and-The-Prey ]

(related to comic books, at least one poster on the forum noted that there is a Fantastic Four comic book issue #347 that contains the character Ghost Rider)

Just thinking broadly, trying to interpret the poem:

The rabbit has a seCret,                                  
Little sound does she make,       [1]                                        
She keeps it.                                          
                                                        
The snow falls in silence,          (the padding around the poem hides a message)                                    
A sentRy of concealment,          [2]                                        
She Yields it.                                    
                                                          
The hunter and the Prey,          (we are the hunter, the rabbit/answer/next clue/bounty is the prey?)                              
Wounded where she lay,           [3]                                      
She seeks iT.                                                    
                                                      
Enlightened warriOr don the armor    (use Rabbit cipher)                                  
Crafted in her honor                                                    
You'll need it.                                                                  
                                                                
There is hope in the white,       (the padding)                        
Look to the rabbit, the axiom,   (axiom=starting point of reasoning. Look back to key words from the beginning of the puzzle?)                        
Who reveals it.                                                            
                                                          
J.S.  

[1] So, the rabbit has a secret which she keeps, but she's not silent, "little sound does she make" -- so she makes at least a little sound. Otherwise poem would say "NO sound does she make."

[2] The snow falls in silence, meaning the padding surrounding the poem. The snow is the SentRy of concealment. The key is something about the rabbit, because "she" "yields" it.
                                      
[3] Wounded where she lay, (could she be wounded because the code has something misleading in it? I know I said this before but will repeat it anyway: think of "beware the false satoshi" --something is there that messes with the code. I still like the idea of looking for 00000001 (1 satoshi) as a piece that needs to be excised to yield the correct ciphertext. I think there are more than one of them. Which one needs to be discarded?

Here is a list of words from the puzzle so far that might be used as keys somehow:

WR
it would
W@@@LK
347
EAT
Alice
FoLLow
1follow
WR4Bt
CRYPTO
Followthewhiterabbit
the rabbit
8675
CR347OR
PO347
TR3N47Y
Xavi3rM4x7
N3v4Le7
FoLLowThEWhiteRABBIT
bewareThEFALSesatoshi
LostinThEWhiteNoiSE
theartWePENHERE
PENSUM

Any of the addresses:

1FoLLow3pd7y5Wvk2dWYqpH6YdaHTLcYmM
1WTR4BtM61k4NB52Zvdf79k4B7jiiepFC
13pgUbz1Gxj1Sirw3Yr44Vybck7M1yLhEe…
1PENSUMKNPVCjChPzUqF32eA6gSUdMoJMZ
1GoNR15KUWkqTyZfKTDsKeEacjLqJYJW15
1TLSNYAx5P6Yjie3cF97fZh9U4B5UZ7PF (bounty)
1N8NGRSw1qUQH48PKzuGccThBUT1zGv9aH
1EzarhwPwdGPDZ85Kv6Ytw1YBqnuTg5Mmc
1BKKy36wEcszrEZF4uaehMF9GnqcTziYXT (initial sender to bounty)
1LsGQV6DvhR1RuK9KX7GkLiGcQ7CEXrZN8 (sender to bounty on 9/2)
1JwRwGhsXECmgbLf54RNxqAan3si3XQ42g (sender to bounty on 9/5)
12cC4FGZJSD9uBhsFoPpyK2qG7BHZLHVU9 (sender to bounty on 9/5)
1DsxvZfQJp26kU6ertifiRSpXUJJSCWycM (sender to bounty on 9/9)
00010001
00011
00011001


Any others to add to the list?

[mirth23]

Rabbit does use a salt (= IV?), and a key. Both of which have to be exactly 16 bytes, otherwise it will insert apparently random data.

Unfortunately my javascipt is pretty rusty. Perhaps later in this ARG i can dust of wabbitemu and code some assembly

Salt and IV are two different things, and I had to set both explicitly to get consistent output from CryptoJS.Rabbit in some cases.

[juju]

-snip-

bewareThEFALSesatoshi

-snip-

I had a thought earlier probably no correlation:

When did we learn about the "bewareThEFALSesatoshi" - Was this before satoshin@gmx.com was hacked and Theymos created the thread?

Did the creator know about this false Satoshi before hand or was it simply a coincidence?

Edit: Answering my own question, we learned about the false satoshi warning on September 4th. Theymos made the: satoshin@gmx.com is compromised
September 8th

[rock_collector]

So I followed the white rabbit as instructed, and he only went one way.
https://blockchain.info/pt/tx/e45a0385fae71827891c12ce8cf2f768a5afc535373456a1e76a1a4b9429d981

I have been looking at this transaction for quite some time, but I was impressed by the quantity of output addresses with the same huge prefixes.
I don't know how this can be achieved, can someone explain? Are those some kind of deterministic addresses?

I also found a message hidden in the output scripts of this transaction, check every single one of them, convert from HEX to Text:


The rabbit has a seCret,                                   
Little sound does she make,                                               
She keeps it.                                          
                                                         
The snow falls in silence,                                              
A sentRy of concealment,                                                  
She Yields it.                                             
                                                          
The hunter and the Prey,                                        
Wounded where she lay,                                                 
She seeks iT.                                                    
                                                      
Enlightened warriOr don the armor                                             
Crafted in her honor                                                    
You'll need it.                                                                 
                                                                
There is hope in the white,                                 
Look to the rabbit, the axiom,                                  
Who reveals it.                                                            
                                                          
- J.S.                                                         


EDIT:
CRYPTO "upper-cased" on the msg

If extracted directly from each output, it's something like this:

hex

Code:

76a914546865207261626269742068617320612073654388ac76a9147265742c0920092020092009200920202020202088ac76a914092020202020200a4c6974746c6520736f756e6488ac76a91420646f657320736865206d616b652c202009202088ac76a914202009202020202020200920202020202020092088ac76a91420200920202020092020200a536865206b65657088ac76a914732069742e20092009092020092020202009202088ac76a9142020200920092020202009200a0920092020092088ac76a914202020202020092020202020092020202020092088ac76a9142020092020200920200920200a54686520736e6f88ac76a914772066616c6c7320696e2073696c656e63652c2088ac76a914202020202020092020202020200920202020092088ac76a914092020202020202009202020202020200a41207388ac76a914656e745279206f6620636f6e6365616c6d656e7488ac76a9142c2020202020202009202020090920202020092088ac76a914202020202009202020202020092020202020202088ac76a9140a536865205969656c64732069742e200920200988ac76a914202009202020202009202020202020092020200988ac76a9142020200920200a0909202020202020200920202088ac76a914202020200920202020092020202020200920092088ac76a914202009202020202020200a5468652068756e746588ac76a9147220616e642074686520507265792c092020202088ac76a914092020200920092020202020092020202020202088ac76a9140920200a576f756e64656420776865726520736888ac76a91465206c61792c202009202009202020202020092088ac76a914202020202009202020092020202020200920202088ac76a9142020200a536865207365656b732069542e20090988ac76a914202020092020202020202009202020092020202088ac76a914092020202009092020202020200a20200920090988ac76a914202020200920202020202009202009092020200988ac76a914202020092020202020200a456e6c69676874656e88ac76a91465642077617272694f7220646f6e20746865206188ac76a914726d6f722020092020202020200920202020092088ac76a914202020202020092020202020202009202020200a88ac76a9144372616674656420696e2068657220686f6e6f7288ac76a914200920202020202009200920202020202009202088ac76a914202020202009202020200909202020202020200a88ac76a914596f75276c6c206e6565642069742e202020202088ac76a914200920202020202009202020202009202020202088ac76a914202009202020202020092020202020202009202088ac76a914200920202020200a20202020092020092020202088ac76a914200909202020200920202020200920202020202088ac76a91420092020200920092020202020200a546865726588ac76a91420697320686f706520696e20746865207768697488ac76a914652c09202009202020092020202020202009202088ac76a9142009090a4c6f6f6b20746f20746865207261626288ac76a91469742c20746865206178696f6d2c09202020202088ac76a91420200920200920090920202020202009200a576888ac76a9146f2072657665616c732069742e2020202020092088ac76a914202020202020092020202020200920202009202088ac76a914202009202020202020200920092020202020202088ac76a9140a2020202020200920202020200920202020202088ac76a914200920090920202020200909202020200920202088ac76a914202020200a2d204a2e532e09202020200920202088ac76a914200920200920202020092020202009202020202088ac76a914200920202020202020092020200a090a0a00000088ac

text

Code:

v©The rabbit has a seCˆ¬v©ret,	 	  	 	 	      ˆ¬v©	      
Little soundˆ¬v© does she make,  	  ˆ¬v©  	       	       	 ˆ¬v©  	    	   
She keepˆ¬v©s it. 	 		  	    	  ˆ¬v©   	 	    	 
	 	  	 ˆ¬v©      	     	     	 ˆ¬v©  	   	  	  
The snoˆ¬v©w falls in silence, ˆ¬v©      	      	    	 ˆ¬v©	       	       
A sˆ¬v©entRy of concealmentˆ¬v©,       	   		    	 ˆ¬v©     	      	       ˆ¬v©
She Yields it. 	  	ˆ¬v©  	     	      	   	ˆ¬v©   	  
		       	   ˆ¬v©    	    	      	 	 ˆ¬v©  	       
The hunteˆ¬v©r and the Prey,	    ˆ¬v©	   	 	     	       ˆ¬v©	  
Wounded where shˆ¬v©e lay,  	  	      	 ˆ¬v©     	   	      	   ˆ¬v©   
She seeks iT. 		ˆ¬v©   	       	   	    ˆ¬v©	    		      
  	 		ˆ¬v©    	      	  		   	ˆ¬v©   	      
Enlightenˆ¬v©ed warriOr don the aˆ¬v©rmor  	      	    	 ˆ¬v©      	       	    
ˆ¬v©Crafted in her honorˆ¬v© 	      	 	      	  ˆ¬v©     	    		       
ˆ¬v©You'll need it.     ˆ¬v© 	      	     	     ˆ¬v©  	      	       	  ˆ¬v© 	     
    	  	    ˆ¬v© 		    	     	      ˆ¬v© 	   	 	      
Thereˆ¬v© is hope in the whitˆ¬v©e,	  	   	       	  ˆ¬v© 		
Look to the rabbˆ¬v©it, the axiom,	     ˆ¬v©  	  	 		      	 
Whˆ¬v©o reveals it.     	 ˆ¬v©      	      	   	  ˆ¬v©  	       	 	       ˆ¬v©
      	     	      ˆ¬v© 	 		     		    	   ˆ¬v©    
- J.S.	    	   ˆ¬v© 	  	    	    	     ˆ¬v© 	       	   
	

ˆ¬

And so the difference between the two is basically:

hex

Code:

76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac76a91488ac

text

Code:

v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬v©ˆ¬

So 76a91488ac repeats itself for 55 outputs.


Not really sure if the next conversions are correct...

76 -> char 'v'
a9 -> char ®
14 ->? device control 4 ?
88 ->ê
ac -> char for ¹/₄


(...)

New update from Micaman's earlier post.

[micaman]

"These are op-codes that tell the interpreter to put a specific amount of bytes to the stack. "
https://en.bitcoin.it/wiki/Script#Constants

[rock_collector]

hmmm, I feel the rumblings of something about to explode...

[mirth23]

My partner and I are two more steps along. Proof: "I'm_going_to_have_to_put_you_on_the_game_grid"

I'll drop some more hints tomorrow, zzzzz.

[frisco]

My partner and I are two more steps along. Proof: "I'm_going_to_have_to_put_you_on_the_game_grid"

I'll drop some more hints tomorrow, zzzzz.

Following Twitter and after some test it is clear that there is a Base64 encoded cryptogram hidden in the white spaces using:
http://www.darkside.com.au/snow/

Just need to execute it: (I have uploaded original.txt to: http://pastebin.com/JmjWbDuk)
SNOW.EXE -C -p XXXX original.txt

To see random text changing the password, I have tried a lot of them but haven't found the correct one.

[mirth23]

My partner and I are two more steps along. Proof: "I'm_going_to_have_to_put_you_on_the_game_grid"

I'll drop some more hints tomorrow, zzzzz.

Following Twitter and after some test it is clear that there is a Base64 encoded cryptogram hidden in the white spaces using:
http://www.darkside.com.au/snow/

This is correct. Credit to @x1010fox on twitter for finding snow in the first place.

Actual zzzz for me, now.

[mirth23]

Here's how the next two solves worked. I won't spoil keys if people want to play along. Both keys are pretty straightforward if you follow the clues.

1) Apply the http://www.darkside.com.au/snow/ tool to the poem+whitespace you get from running b58decode_check on the poem. Make sure to strip the extra hex '00' characters first. There is a key. This will result in a base64 representation of a Crypto-JS CipherParams object, which you quickly recognize as such if you have been playing with Crypto-JS. I suspect that people who have been trying to play with snow have ended up with some copy-paste errors when trying to create their file, so here's some python code to show one way to do it successfully:

Code:

import base58
codelist = ('18hJpcE7w51A7GpMU4QkVk1h5V6Ryj61XK', '1BRsa17vaULT26ZNViz1d4Fyjhxgfig77k', '1qFZqzT8jEMPiaHap7qwop3UGrsMWetQ6', '13xGwVghnbk7A9ZSVq18Hk5WDgaqnVAwiU', ...)
poem = ''
for c in codelist:
  poem = poem +(str(base58.b58decode_check(c)).translate(None,'\x00'))
f = open("poem.txt", "w")
f.write(poem)
f.close()

Note that you might need to 'pip install base58' if you don't have it already.

I ran snow from the command-line on the output from the above snippet:

Code:

./snow -C -p KEY poem.txt 

2) Apply the Crypto-JS.Rabbit algorithm to the base64 that snow gave. Salt and iv are NOT needed since they are embedded in the base64. A different key is needed; credit to zonkism for finding it first. You can run this locally by making a simple html code on your local host and directing your browser to it, all you need is the following in the page:

Code:

<script src="http://crypto-js.googlecode.com/svn/tags/3.1.2/build/rollups/rabbit.js"></script>
<script>
var cipher=CryptoJS.enc.Base64.parse('RESULT_FROM_SNOW');
var cparms = CryptoJS.format.OpenSSL.parse(cipher.toString(CryptoJS.enc.Base64));
cparms.key = "KEY2";
var decrypted=CryptoJS.Rabbit.decrypt(cparms,cparms.key);
alert('decrypt: ' + decrypted.toString(CryptoJS.enc.Latin1));
</script>

This results in "http://www.whit3r4bbi7.com/"

This is a website asking for a user/login to the area “I'm_going_to_have_to_put_you_on_the_game_grid”!

next steps:
- There's a lot of user/logins in TRON with many possible variants. I've tried a bunch but have come up empty. Still hammering on that a bit.
- There is a @WHIT3R4BBI7 twitter with "Trust no one. #GTIN" in their profile. GTIN appears to refer to a type of barcode. I can't tell if this twitter account is part of the game or not, it's private unlike all of the other ones.

outstanding weird stuff:
- what do the 'x' marks mean in the OP?
- are there more secrets in the nearby blockchain and related transactions?