If you rotate/shift using the alphabet, with a single step interval.... I guess you always get the alphabet in each column 

checked the blockchain for transactions and used addresses.

1BhnKiVaDokB9X5GKixZnSGxJXobbQtfQh --> depleted and not used in combination with 1HXUobwcB19cGDrghuh42HDdJdJvrJUEra
but this address got a payment from 1rEDGrNbuqqtbJU12XiU4hvmfM4XaQVcD and forwarded to 1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz

1sosB9wN5ij84GKfo6Xxx8FWyh5fPXVXu  --> depleted
1rEDGrNbuqqtbJU12XiU4hvmfM4XaQVcD --> depleted

1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz --> still hold some value, not enough for binary at the moment.

1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ --> the main(?) bank wallet?

I guess the depleted wallets mean that the red/green and Morse code should be considered completely solved?

We might still get some binary info.... :-)

I just wonder if the 1BhnK address is also a vanity address and what the name should stand for.
It may have been for a hint that became obsolete...

or a WiKi

Just a thought, the last morse code wordt not(?) part of the phrase were STOP WORDS,
But as I understood the morse (dot)code continued.
morse numbers from this point? binary?

Check the source of the payments, this eliminates the transaction fee binary mix/mess-up.
I also pad "0" to make it go to a single Sathosi.
 
Transactions from 1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz

00100011 -> #
00100011 -> #
01001000 -> H
00100011 -> #
00100011 -> #
01010101 -> U
00100011 -> #
01000101 -> E
01010010 -> R

404 --> stands for "Not Found" I Guess

00100001 -> !
01000100 -> D
01001111 -> O
00100001 -> !
00100001 -> !
00100001 -> !

I guess we have to DO something.... :-)

I was wondering if this picture was the only one (and the first?!) available.
Google image search on "Uc6VAnV.JPG" got me a link to an image with another name:

https://lh5.googleusercontent.com/-Filfubk0KZk/U6b7sQAx5OI/AAAAAAAAAbw/wdT0ivbuHRQ/w1494-h996/cryptiCitpyrc.JPG

This link holds an actual name.

Trying to find more images with this name led me to

https://fireden.net/4chan/images.4chan.org/g/src/1403553226437.jpg

This is actually the biggest image (file size) I found.

the search results all seem to have an link to coin_artist.
But I cannot verify of any of these images is actually the first post....

I might be following the ARG rule:
-View source on all pages
Or breaking the rule
-Don't seek what lies behind the Curtain

Check my repo @ https://github.com/kangaderoo/vanitygen
this keyconv should support the -X switch

The Vanitygen updates are fixed to my development env. at the moment.
Build only the new keyconv code.

Have fun.

[1KangaNsFtfsr7vgVhdvfdY8LyRVbm1Mbh]

I checked the source code of the keyconv, it only combines two private keys an generates a new key.
For the address verification it assumes the prefix that is related to bitcoin, for some reason the -X option is not here for various address confirmations.
For combining the private keys it is actually not needed.

So I took your bitcoin adress to the site: http://brainwallet.org/#converter
convert the bitcoin to hex
input = base58, output is hex
replace the 00 prefix (bitcoin) for 1e (equal to 30.. I suppose dogecoin)
copy the result in the input box
input = hex, output is base 58

Inserting this private key in a Dogecoin wallet should give the prefix DLR I guess.....If the hashing is the same..
the generated code:
DLRk2hNcMccjKrPYiDBrbjX6C1j7r1Pnkg
is not 100% equal to the actual code
DLRk2hNcMccjKrPYiDBrbjX6C1j7tgjDpX

Thats because the SHA hash checksum is not calculated in prefix mode to gain time, this effect is only at the end of the address.

Just as been done with (SHA256 and Scrypt) mining software, I've been trying to port the Vanitygen code for CPU to make use of the SIDM functionality.
By running the SHA256 and RMD160 4 times parallel (AVX1) I got a rough speed increase of about 25-30%.
It seems that the actual EC_key generation is the big time consumer.
Any idea how to speed this up?
Is it possible/faster to only calculate only a X-coordinate, hash the compressed key, and try to find a (valid) key-pair after a confirmation
a wanted prefix in the bitcoin address is found? You might run into false positives I guess, but this could be a trade off to faster hashing.....

Code is @ https://github.com/kangaderoo/vanitygen

[1KangaNsFtfsr7vgVhdvfdY8LyRVbm1Mbh]