Waking Titan/Phase 4

Waking Titan - Phase 4
Active since 2017-05-28
Waking Titan was an ARG which led to the Atlas Rises update for No Man's Sky, and has been dormant untill 18-12-2017.
Type	[[List_of_Investigations#Official|Official]]
Creator	Alice & Smith & Hello Games
Discovered	2017-05-28

Main Page > List of Investigations > Waking Titan > Phase 4

It is unclear whether Phase IV has officially begun, or whether these events are interstitial matter leading to a new phase. For our purposes we refer to these events as "Phase IV" until contrary evidence is presented.

Tenth Glyph

Beginning on December 28th, 2017, typing WHOIS on the Waking Titan website returned the following: #WHATIS1.5. In addition, the 10th glyph was made active, and linked to a Google Drive folder, which contained community-made pictures of the NMS logo in an infinite mirror.

The titles of the photos, when strung together (skipping the 00 (empty) ones), formed the hexadecimal code for moirrr, which was an anagram for mirror. Additionally, the hexadecimal code in the correct order for the word mirror could be found on the bottom of the Myriad website.

Also of note was the background of the tenth glyph, which read:

the background of the tenth glyph

Dear Elizabeth
We have finished processing 10,000 passes as per your requirements. You should
have them in time for the next phase. I really hope you will like the final product.

Kind regards,
Gail

The allusion to 10,000 passes is likely a reference to the Level 4 Atlas passes that were promised to players as part of earlier phases. The identity of "Gail" remained unknown.

Atlas Passes

On January 17th, 2018, the first CSD user received their Atlas Pass. The passes were made from cardstock, with a textured pass printed on it. The front had the text WAKING TITAN printed, and below that the CSD category the user belonged in. On the very bottom, a series of hexadecimals reading 70686f656e6978 could be found, which, after decoding, translated to PHOENIX. On the back, the owner's CSD-ID was written, along with a serial number stating which pass out of 10,000 the user had, and a number at the top.

It is strongly recommended to not cover up the hex underneath your signature, and to share the number above and below your CSD ID if you are in possession of a pass. Preferably with a picture of the front, as shown below. For a list of all the atlas passes currently known of, please refer to this spreadsheet. In the event you receive one of these, please share a picture of the front, and the numbers underneath and above your CSD-ID (censored bit) on the back.

• 

  Atlas Pass front side

• 

  Atlas Pass back side

Status Command Update

On January 20th at 5:44PM UTC, the output of the STATUS command began to update:

Downloading Data...: 19:44
1-                 : 20:16 (32 min)
1-8                : 20:27 (11 min)
1-80               : 20:39 (12 min)
1-800-             : 20:44 (5 min)
1-800-41           : 21:35 (51 min)

1-800-413-01       : 22:14 (39 min)
Xxxxx X            : New Line

1-800-413-011      : 22:15 (1 min)
Xxxxx XX           

1-800-413-0110     : 22:16 (1 min)
Xxxxx XXX

Calling the provided phone number yielded an SSTV transmission (pictured below) which, once decoded, provided meteorological data for various locations.

• 

  SSTV page 1

• 

  SSTV page 2

Players found they were to order the list of locations in the image alphabetically. This yielded a sequence where Index by Precipitation could be read off. Using the ordered text indexed by precipitation (in alma the second index is o) led to the following:

CAFE
BENE
NINETEEN
SAT

Livedrop Memo

The text indicated a new livedrop would be occurring in the same location as the last one had. However, due to the old Cafe Bene closing, the Xxxxx XXX part was added in the STATUS command update to warn players about the new venue, Outro NYC, which opened in the same place as the Cafe Bene had been located. The livedrop was intended to occur at 7PM EST (12:00AM UTC). However, the first player from the community who set out for the drop was involved in a traffic mishap, delaying their arrival. Anticipating missing the drop's time window, the community reached out to request a time extension, and the STATUS command, which had updated frequently throughout the confusion, was updated again to approve the community's request.

STAND BY: CSD CITIZEN NOT DETECTED
WARNING: CSD CITIZEN NOT DETECTED!
IT'S LONELY OUT HERE
TIME EXTENSION REQUESTED?
EXTENTION PROPOSED: 2H30 – AWAITING CSD APPROVAL
EXTENSION APPROVED, BE SAFE

Book case seen on the livedrop livestream is the same as one used in an earlier livedrop.

After the extension was approved, a second player from the community set out to the livedrop location on livestream and met with their A&S contact around 7:30PM EST (12:30AM UTC). During the meeting, the player was handed a memo from a mysterious case disguised as a book, pictured left. After some cryptic conversation, the contact asked if they were "getting enough sleep", stating that being well-rested would be very important. After the meeting, players who had attended the livedrop met in another location and showed off the memo, speculating about it's contents and even discovering the REM Sleep connection to the letters on the memo's back. After the livedrop, the community used the livestream to look over the memo, pictured below. On the back of the memo REMS is written. This clue, in combination with the strange question A&S asked at the rendezvous, led players to the password for the 10th Glyph, REM SLEEP.

• 

  Memo page 1

• 

  Memo page 2

• 

  Memo page 3

Seventh question revealed on the bit.ly form when REMS or REM Sleep is entered for question six

Once the glyph was solved, the STATUS command updated to a bit.ly link to a form. Players discovered that on the sixth question on the form, entering REMS or REM Sleep (case sensitive) caused a seventh question, pictured right, to reveal itself, allowing CSD users to enter their email address to receive "left over materials" from something called Lab 319. Players remained unclear on what exactly Lab 319 was or what it's leftovers were, however signing up seemed integral given the input is only revealed after using the REM Sleep phrase.

Solar Event

On 26 March, 2018 at 05:25 UTC an event occurred. The Myriad site came online featuring indications of a solar event interfering with operations. In addition, the status command on Waking Titan briefly displayed the following:

CODE -3
Unable to restart
.................
ERROR LOG SUMMARY
- Major malfunction
- Protect the monarch
- All tiers 2 and tiers 3 clients must be purged IMMEDIATELY
.................
TO ALL CSD
- Gather maximum EXTERNAL intel
- CSD should take time to regroup and get organized

Ten minutes elapsed before the Status command began to display the following:

CODE -5
System Locked
e b 4 c 1 4 a 9 c 6 2 2 d f 7 1 6 6 f b e 0 d d 8 9 1 5 d b 0 2

The meaning of this hexadecimal string remains undetermined.

Client 3597b

At 1:11 AM, UTC, Myriad-70.com updated, and the updates included the following.

Latest network diagnostic table:
- Network corruption detected
- Situation isolated to Client 3597b
- Process cannot be suspended due to critical conditions
--------------------------
-Beijing: 29.1Tb/s
--------------------------
MAJOR ISSUES:
Client 3597b

Soon after, at 1:30 AM UTC, the Status command updated in the Terminal to say the following.

> status
CODE -5
System Locked
e b 4 c 1 4 a 9 c 6 2 2 d f 7 1 6 6 f b e 0 d d 8 9 1 5 d b 0 2
--------------
Monarch Repository Status: Degraded
Conflict With
- Client 18d1a TRACERT 10.30.74.*
- Client 3597b TRACERT 54.91.155.*
- Client 351h TRACERT 6.128.214.*
- Client 0911a TRACERT 74.1.21.*

With Client 3597b being the "Major Issue" for Myriad-70, an IP trace was conducted, and yielded the following results.

Lookup IP Address Location For IP: 54.91.155
Continent: North America (NA)
Country: United States; IP Location Find In United States (US)
Capital: Washington
State: Virginia
City Location: Ashburn
Postal:	20149
Area: 703
Metro: 511

Approximately 15 minutes later, clients began to disconnect, beginning with Client 0911a, second being Client 18d1a, and the last being Client 351h, who had an additional piece of text added, being ID: 79657321, which was translated as hex into Yes!

Then, at 2:15 AM UTC, the status command was updated again, stating - Client 3597b - UNABLE TO DISCONNECT 54.91.155.209 NAT 52.2.248.*

The finished IP Address gives the same result, and the use for the NAT Number also leads to the same location.

This page is a work in progress, and will be updated as new developments emerge.