arg, thanks for the summary. Allow me to supplement it with some insane rambling.
There doesn't appear to be anything to open. Therefore we are either looking for a web/onion address of some kind, or we're at the final step: constructing the private bitcoin key.
My guess is that this is the last step. How do we get to a bitcoin key with the large amount of information currently in front of us? Also, how can we do this with simple transformations? We haven't been using excessively complex math to date.
My (somewhat hare-brained) notion is that the OP used oringinal data from the crop circle binary and the Wow code printout to do this. This might sound crazy from a security perspective, but it's also entirely feasible. Some combination of the alien messages could build the raw bytes of our private key, from which we can easily extract the private and public addresses. I got onto this idea because of OP's "wow + crops" hint. So, how could we combine the two data sources?
We have three hints built into the puzzle:
1) 0=0A=10BABYA=36WOWÐS
2) CHANNEL NUMBER, (TWO DIGITS, WRITTEN VERTICALLY).
z69JZqlJn862D1ndx7oLVEMmVOlP1zewEeUCrsI7Roahzpeny7P
3) the XMP data in Wow.JPG
One other possible hint source is the DoD game. There were added word fragments that went unused. Most notably, "Such Wow!", which I'll get to in a bit.
BREAKDOWNS1) 0=0A=10BABYA=36WOWÐS
We didn't actually use most of the hidden morse code to move on to the next step. What could the rest of it mean?
0=0A: starting point is position 10 (0A hex->dec)? It just so happens that the overlaid message from OP ends just before the 10th octet of the binary alien message.
=10BABYA=:
? I have been puzzling over this for a while. It might be an end point to stop reading.
36: Not sure, but there's multiple instances of '36' in Wow.JPG. The first is a bit to the right of the Wow! signal itself. The other ones are all in the seconds column, which happens to be to column that the XMP is drawn alongside - and the XMP stops RIGHT at 36. Combine this with the use of "The Final Countdown" video, and I wonder if the seconds column itself was used as a raw data source.
WOW: we already used this to get to the next step. It could also imply "36 on the WOW file"
Ð: this is not a typo, it really is the Dogecoin symbol in morse code. This leads me to an alternate interpretation for 36WOW - it's "Such Wow!", the Dogecoin meme, like in the DoD game. 36=Such or So?
S: I added this in because one final morse letter is incidentally here before the original binary message resumes. Not sure if it actually means anything.
2a) CHANNEL NUMBER, (TWO DIGITS, WRITTEN VERTICALLY).
This was the original text, but "two digits, written vertically" sounds like a potential hint. Again, it specifically makes me wonder if we're supposed to be the seconds column from the time data. They are pairs of digits, written vertically.
2b) z69JZqlJn862D1ndx7oLVEMmVOlP1zewEeUCrsI7Roahzpeny7P
We've probably all hammered on this a lot. It doesn't transform into a private address. It doesn't rotate into anything useful. It's not clear how we'd use it as a cipher key, and it's not clear what we'd use it on if we did.
As outlined previously, I wonder if there's a message hidden in it. Things that particularly pop out are: 2D 1ndx 7oLVE ... P1ze ... U Crs I7 Roahz peny 7P
It might not include data for the puzzle solution (it's crossed out by the XMP) but I also think it's some sort of hint.
A (FAILED) ATTEMPT0=0A=10BABYA=36WOWÐS
Let's interpret this to mean that we take 10 bytes of data from the crop circle, starting with the tenth (conveniently the first one unhidden by the puzzle data).
00100000 01100010 01100101 01100001 01110010 01100101 01110010 01110011 00100000 01101111
this gives me 20 hex characters: 2062656172657273206f
A private bitcoin key is 64 bytes, so I need another 12 hex. Let's grab a vertical series of timecodes from Wow.JPG, starting with the "36" that the blue dot points to (using the '36' from the morse code message). (Get it, "Final Countdown"?)
36 48 00 12 24 36 >> 2430000c1824
concatenate this with the above: 2062656172657273206f2430000c1824
public key of this is 1PKSpvbMJqFJ4DPuMbNsiGcp35guqwai3g
Nope.
Obviously, I'm not getting correct solutions here, but I wonder if something along these lines will get us there.
tl;dr: I think the real key is to correctly interpret 0=0A=10BABYA=36WOWÐS and z69JZqlJn862D1ndx7oLVEMmVOlP1zewEeUCrsI7Roahzpeny7P .
