It's OK.. We all float down here.....

This will allow you to decode those dots into the printer serial number. https://w2.eff.org/Privacy/printers/docucolor/
This is a great way to encode information.  I have never seen it used in a puzzle before.

At this point OP believes we have all the data we need to reach at least the next step.  Pretty sure we will not be receiving anymore clues for a while.  This damn puzzle has consumed my life now for several days.  I am seriously bummed that I am leaving on a cruise tomorrow for 7 days and will  probably miss the next steps.  Although I am now very very tempted to pay a stupid premium for internet access while on the boat.  Hell that is a first world problem if ever there was one.  It also appears the morse code is completely solved based on the OPs last update.  I think the next strategy is in looking at the remaining alpha numeric that are not part of the plaintext address.  I've been looking at all of the standard transpositions and nothing is clicking.  Possibly a base change.  I have converted everything to hex, decimal, reversed it, flipped the hex values, reassembled.. nothing.  Analysis of the remaining alpha numerics  show a pretty random distribution which is usually indicative of a cipher, meaning a plaintext transposition will not work due to the frequency of letters and numbers does not seem to match typical language pattern.

Reasons I use Gimp....
#1 Its Free
#2 Its Free
#3 Its Free

My conversion script had an error..   So that is not correct.

Reposting... because I had an error in the last post...


The following addresses have all received coins from 1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ:

1sosB9wN5ij84GKfo6Xxx8FWyh5fPXVXu
1rEDGrNbuqqtbJU12XiU4hvmfM4XaQVcD
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz

Based on the transaction chain I can only feel comfortable with these above addresses being associated with the OP.

This means the following transactions are associated with OP


1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .001011 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .001011 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .001011 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .023 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .022 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .021 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .02 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .19 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  -  .01799999 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .017 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .016 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .015 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .014 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .013 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .012 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .011 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .01 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .00899999 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .007 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .006 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .004 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .002 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .001 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .023 BTC
1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .001 BTC

1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ  - .05 BTC

1sosB9wN5ij84GKfo6Xxx8FWyh5fPXVXu - .01010011 BTC

1rEDGrNbuqqtbJU12XiU4hvmfM4XaQVcD - .00098765 BTC (public note : (no more clues)

1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ - .06 BTC

1rEDGrNbuqqtbJU12XiU4hvmfM4XaQVcD - .00404 BTC (public Note: http)
1rEDGrNbuqqtbJU12XiU4hvmfM4XaQVcD - .001 BTC (public not: Public Note: 01100011 01100001 01101110 00100000 01101110 01101111 01110100 00100000 01100100 01101111
                                                                                                                        00100000 01101110 01101111 01110100 00100000 01100110 01100110 01110011)
1rEDGrNbuqqtbJU12XiU4hvmfM4XaQVcD - .00057235 BTC

1sosB9wN5ij84GKfo6Xxx8FWyh5fPXVXu - .001 BTC

1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .00404 BTC - 404
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .005 BTC -   5
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .01 BTC -    1
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .01001111 BTC - O
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .0009 BTC -     9
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .00100011 BTC - #
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .01000011 BTC - C
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .01001 BTC -    H
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .01000011 BTC - C
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .01001011  BTC - K
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .01010101  BTC - U
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .01010011  BTC - S
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .01000101 BTC - E
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz   .0101001 BTC - R
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .00404 BTC - 404
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .00100001 BTC - !
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .010001 BTC - D
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .01001111 BTC - O
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .00100001 BTC - B
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .00100001 BTC - B
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .00100001 BTC - B
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .0010001 BTC - D
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .010001 BTC - D
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .01001111 BTC - O
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .0100111 BTC - N
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .01001111 BTC - O
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .010101 BTC - T
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .0010001 BTC - D
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .01001 BTC - H
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .010101 BTC - T
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .010101 BTC - T
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz - .0101 BTC - P

404 5 1 O 9 # CHCK USER 404 ! DOB BBD BO NOT D HTTP

I was looking at this one too.

The 5 and 1are right next to each other in the alphanumeric sequence.  5 might end the 1st section of cipher before the 1 begind the plaintext bitcoin address?  O and the 9 might mean to look at the string of alpha-numerics from O all the way to 9.... curiouser and curiouser

I think the OP is choosing specific addresses to communicate specific pieces of the puzzle.

BoR - not sure what this means (main contributing address)
rEDGrN - specicially hints regarding the red/green dots
1sos - using for larger game course correction or actual translated MORSE code
PBs - So now what can PB mean?

initial thoughts... PB is lead (alchemy), PB is Puzzle Background, PB is parity bits.. yeah.. I am chasing rabbits

I take HTTP with a  .0404 amount to mean, we got something wrong.  What you see when you get a webs address wrong.... Then the following binary comment trying to course correct us... Obviously there is a huge important between can not and do not

"what they do not see" could be the actual guys in the picture... they are looking forward and not seeing what is behind them....  A crypto attack perhaps?

I also had no problems installing dark wallet using the directions on the darkwallet site.

mirth is not a girl... nor am I

pretty sure at this point you are just chasing rabbits

Just a reminder this is out there for translating and manipulating Morse... http://rumkin.com/tools/cipher/morse.php  rumkin has many many other useful tools for these types of puzzles as well.

I have been going off of the idea that the next phase is going to be a redirection to a video, another image, or a random website.  This is what I think the next step is going to be some sort of transposition on the remaining plain text alpha numeric and/or decoding of the dots.  I have been trying to reverse engineer the process in creating the drawing.  thinking about what I would have control over to change that would still allow the drawing to maintain integrity and coherence.  The things I would not have a problem changing would be letters/numbers, and location of dots and possibly an embedded message in the background colors... this is a really fun puzzle.

I am currently going on a theory that the blue dot signifies the start point.  I am basing this on the fact that it is blue like the pyramid eye.  Also, I am suspecting that the yellow triangle in the upper right corner of the pyramid may be relevant.  At this point I am taking a step back and thinking very abstractly about this.

This might help you out....

https://docs.google.com/spreadsheets/d/1EPARfiJ-Fw140N8Jg5QTgJdp10GsgepcHD_-7DWPmKg/edit?usp=sharing

the ! and @ existed in order to create conditional formatting.  The blue filled cells represent the known plaintext public address.  The purple cell is the blue dot on the image.  you can export CSV and use python to get strings.  I have double and triple checked it for accuracy. Its fun to play with.  knock yourself out.  Please don't break it

We should be carefull not to fall down the "raw bit" hole

another thing.. The Yellow dots on row 14 makes me think we should not be approaching these dots from left to right but instead either top/bottom or bottom to top.