u/UnicoreP

I posted a rhetorical question a couple days ago asking whether there is more than one checkpoint.

Today I will ask one more such question.

Is there more than one 42?

So far I counted three of them in my journey.

As many of the checkpoints as of the 42s.

This is perhaps the ultimate question.

Responses are welcome but not required.

Through my journey to find the final place, I thought I encountered more than one checkpoint. Each one is directional and confirmed on the next step. So far I have had three checkpoints. They helped me find the pole, the realm, and the bride. I am thinking there may be one last one that point me to the treasure. Would the last one be “double arcs?”

Possibly.

There are many Easter Eggs along the way - that’s what I heard.

Through my journey to find the final place, I thought I encountered more than one checkpoint. Each one is directional and confirmed on the next step. So far I have had three checkpoints. They helped me find the pole, the realm, and the bride. I am thinking there may be one last one that point me to the treasure. Would the last one be “double arcs?”

Possibly.

There are many Easter Eggs along the way - that’s what I heard.

After publishing my first post-solve piece, “Where Is the Pole,” I thought I was ready to move on. Then a new “receipt” surfaced—credible or not? It’s enough to pull me back in and derail any momentum toward the next step. I still wanted closure, so I spent a couple of hours talking to an AI. What began as a casual discussion turned into an argument, then a genuinely heated debate.

For those who think I’m overly invested: I already had my solve, and most of my time in this phase was simply “warm weather waiting”—digging into the cipher out of curiosity and for fun. Along the way, I’ve posted several pieces (“Paging Decipherers,” “Tucker the Container,” “Devils Tower, the Shape of the Container”). This post is my attempt at a final word—an adios to what increasingly feels like a man-made abyss. The AI conversation, at least, ended constructively. We reached a conclusion I can live with.

⸻

TL;DR
The clock cipher is clever and thematically satisfying once all pieces are known. However, its real-world implementation exposed weaknesses in production coordination, input clarity, and post-launch communication. It delivered a strong “aha” moment for the eventual solvers, but at the cost of broader trust due to ambiguity and reliance on external guidance. The lesson is straightforward: in public treasure hunts, perceived fairness and self-contained solvability matter as much as clever design. While Justin has since provided walkthroughs and detailed explanations, the community’s concerns about process remain valid. The good news is that the main poem hunt stands separate from this side puzzle.

⸻

The Solve

The clock cipher in Beyond the Map’s Edge (BTME) treasure hunt was solved in late March 2026 by Rose and Mooshee (Team Misfits). The method uses six specific clock times visible in the Netflix series. Solvers map each time onto a clock face divided into quadrants by an “X”:

— The hour hand selects a quadrant.
— The minute hand (grouped into ranges) selects a letter within that quadrant

This produces the unordered letters AAGMRY, which anagram to MAGYAR—a nod to Justin’s Hungarian Vizsla, Tucker, and a thematic hint about the treasure container.

The design draws clear inspiration from works like The Eleventh Hour—dense, visual puzzles with layered codes and symbolic structure. Whether direct or indirect, the influence is recognizable in hindsight.

⸻

Design Strengths vs. Execution Weaknesses

Conceptually, the cipher works. It rewards observation, pattern recognition, and thematic thinking—exactly what a side puzzle should do.

Execution is where it faltered.

Two unintended clock times (approximately 4:02 and 5:26) made it into the final Netflix cut. These introduced “noise,” turning a clean six-letter system into a misleading dataset. For nearly a year, solvers chased false paths because the puzzle, as presented, contained more inputs than intended.

Only after Justin explicitly eliminated these times at Seekers Summit did the solution fall quickly. That delay materially changed the puzzle—from reasonably approachable to disproportionately challenging.

⸻

Inconsistencies in Input Treatment

A central issue is how different clock appearances are counted.

Four times (1:33, 3:04, 4:19, 6:06 ± small variation) appear multiple times but are treated as single contributions
Meanwhile, 12:03 (also repeated with minor variation) is treated as two separate inputs, producing the duplicate “A”

From a solver’s perspective, working only with the Netflix footage, there is no clear rule for this distinction. Why do some repeated times collapse into one input while another produces two?

This ambiguity matters. Without prior knowledge of the intended dataset, solvers have no reliable way to determine:

how many letters the cipher should produce
which repetitions matter
or when to stop collecting inputs

That makes the puzzle feel subjective—or worse, post-hoc—until the creator intervenes. That’s where the fairness concern becomes legitimate.

⸻

Anagram Ambiguity

The output AAGMRY is not uniquely solvable in a strict sense. Alternatives include:

— MARGAY (a wildcat)
— GAY RAM (a male homosexual animal)
— GAY ARM (a male homosexual body part, species-neutral)

This isn’t unusual—treasure hunt puzzles often rely on contextual resolution. MAGYAR stands out because it aligns with Justin’s personal and thematic framework. Still, reaching that answer often required external tools and a willingness to consider proper nouns, which adds another layer of soft dependency beyond the cipher itself.

⸻

Broader Concerns: Fairness and Optics

The controversy extends beyond mechanics.

Justin’s presence in private Discords, personal connections with some participants, the disclosure of his childhood puzzle solving book to certain people, and the timing of certain public posts (including the “seven X-words” post shortly before the solve announcement) created optics issues. Even without evidence of favoritism, uneven access to information is enough to erode confidence in a competitive environment.

His probability model—used to justify delaying clarification—argued that a small group of dedicated solvers would eventually succeed anyway. It used inconsistent population estimates and failed to predict the actual timeline. The correct solve only emerged after the dataset was clarified. That undermines the model’s credibility and makes the delay look less like calculated design and more like post-hoc rationalization.

⸻

Overall Assessment

The clock cipher succeeds as a concept and as a thematic Easter egg. But as an implemented puzzle in a public hunt, it falls short of the standard of self-contained solvability.

The key takeaway isn’t that the puzzle was flawed—it’s that its presentation was. In a setting where participants rely entirely on shared public information, even small inconsistencies or hidden assumptions can scale into major trust issues.

The broader hunt continues. This piece, for me, is where this chapter ends.

Edit: Full Disclosure
I also posted two pieces in this topic
In Defense of Justin. 4/29/26
Failure of the Cipher Design 5/3/26

After publishing my first post-solve piece, “Where Is the Pole,” I thought I was ready to move on. Then a new “receipt” surfaced—credible or not? It’s enough to pull me back in and derail any momentum toward the next step. I still wanted closure, so I spent a couple of hours talking to an AI. What began as a casual discussion turned into an argument, then a genuinely heated debate.

For those who think I’m overly invested: I already had my solve, and most of my time in this phase was simply “warm weather waiting”—digging into the cipher out of curiosity and for fun. Along the way, I’ve posted several pieces (“Paging Decipherers,” “Tucker the Container,” “Devils Tower, the Shape of the Container”). This post is my attempt at a final word—an adios to what increasingly feels like a man-made abyss. The AI conversation, at least, ended constructively. We reached a conclusion I can live with.

⸻

TL;DR
The clock cipher is clever and thematically satisfying once all pieces are known. However, its real-world implementation exposed weaknesses in production coordination, input clarity, and post-launch communication. It delivered a strong “aha” moment for the eventual solvers, but at the cost of broader trust due to ambiguity and reliance on external guidance. The lesson is straightforward: in public treasure hunts, perceived fairness and self-contained solvability matter as much as clever design. While Justin has since provided walkthroughs and detailed explanations, the community’s concerns about process remain valid. The good news is that the main poem hunt stands separate from this side puzzle.

⸻

The Solve

The clock cipher in Beyond the Map’s Edge (BTME) treasure hunt was solved in late March 2026 by Rose and Mooshee (Team Misfits). The method uses six specific clock times visible in the Netflix series. Solvers map each time onto a clock face divided into quadrants by an “X”:

— The hour hand selects a quadrant
— The minute hand (grouped into ranges) selects a letter within that quadrant

This produces the unordered letters AAGMRY, which anagram to MAGYAR—a nod to Justin’s Hungarian Vizsla, Tucker, and a thematic hint about the treasure container.

The design draws clear inspiration from works like The Eleventh Hour—dense, visual puzzles with layered codes and symbolic structure. Whether direct or indirect, the influence is recognizable in hindsight.

⸻

Design Strengths vs. Execution Weaknesses

Conceptually, the cipher works. It rewards observation, pattern recognition, and thematic thinking—exactly what a side puzzle should do.

Execution is where it faltered.

Two unintended clock times (approximately 4:02 and 5:26) made it into the final Netflix cut. These introduced “noise,” turning a clean six-letter system into a misleading dataset. For nearly a year, solvers chased false paths because the puzzle, as presented, contained more inputs than intended.

Only after Justin explicitly eliminated these times at Seekers Summit did the solution fall quickly. That delay materially changed the puzzle—from reasonably approachable to disproportionately challenging.

⸻

Inconsistencies in Input Treatment

A central issue is how different clock appearances are counted.

Four times (1:33, 3:04, 4:19, 6:06 ± small variation) appear multiple times but are treated as single contributions
Meanwhile, 12:03 (also repeated with minor variation) is treated as two separate inputs, producing the duplicate “A”

From a solver’s perspective, working only with the Netflix footage, there is no clear rule for this distinction. Why do some repeated times collapse into one input while another produces two?

This ambiguity matters. Without prior knowledge of the intended dataset, solvers have no reliable way to determine:

how many letters the cipher should produce
which repetitions matter
or when to stop collecting inputs

That makes the puzzle feel subjective—or worse, post-hoc—until the creator intervenes. That’s where the fairness concern becomes legitimate.

⸻

Anagram Ambiguity

The output AAGMRY is not uniquely solvable in a strict sense. Alternatives include:

— MARGAY (a wildcat)
— GAY RAM (a male homosexual animal)
— GAY ARM (a male homosexual body part, species-neutral)

This isn’t unusual—treasure hunt puzzles often rely on contextual resolution. MAGYAR stands out because it aligns with Justin’s personal and thematic framework. Still, reaching that answer often required external tools and a willingness to consider proper nouns, which adds another layer of soft dependency beyond the cipher itself.

⸻

Broader Concerns: Fairness and Optics

The controversy extends beyond mechanics.

Justin’s presence in private Discords, personal connections with some participants, the disclosure of his childhood puzzle solving book to certain people, and the timing of certain public posts (including the “seven X-words” post shortly before the solve announcement) created optics issues. Even without evidence of favoritism, uneven access to information is enough to erode confidence in a competitive environment.

His probability model—used to justify delaying clarification—argued that a small group of dedicated solvers would eventually succeed anyway. It used inconsistent population estimates and failed to predict the actual timeline. The correct solve only emerged after the dataset was clarified. That undermines the model’s credibility and makes the delay look less like calculated design and more like post-hoc rationalization.

⸻

Overall Assessment

The clock cipher succeeds as a concept and as a thematic Easter egg. But as an implemented puzzle in a public hunt, it falls short of the standard of self-contained solvability.

The key takeaway isn’t that the puzzle was flawed—it’s that its presentation was. In a setting where participants rely entirely on shared public information, even small inconsistencies or hidden assumptions can scale into major trust issues.

The broader hunt continues. This piece, for me, is where this chapter ends.
:::

Edit: Full Disclosure
I also posted two pieces in this topic:
In Defense of Justin 4/29/26
Failure of the Cipher Design 5/3/26

As I promised myself to move on from the cipher thing and focus on the solve, I have a question that still not settled from day one and not discussed lately here: Where’s the Pole? Are we all so confident that we don’t need to talk about it?

Too much has been focused on the realm, the bride, her foot of three, and how to return/rotate her face. I think the Pole is critical since the clues are in executive order. If we mistaken the location of the pole, how can we move on to the bride?

My pole is a fishing rod casted in a creek somewhere in Montana but I’m not so sure.

Any thoughts?

After the cipher was solved and the ensuing controversy, I decided to reverse-engineer the puzzle. My goal was to determine whether it could be solved without eliminating the two disputed clock times, thereby avoiding the ambiguity they introduced.

I rewatched the entire GG series, paying close attention to every settings that the background clock appears. After careful observation and analysis, I reached a clear conclusion: the cipher design itself is flawed.

1. The Cipher Solution Is Not Unique
I lack deep expertise in cryptography, so I won’t delve too far into this. However, the existence of two viable solutions—MARGAY and MAGYAR—using the same set of clues strongly suggests a fundamental problem. A well-designed cipher should yield a single, unambiguous solution. The fact that this one does not points to a flaw in the design.

2. The Cipher Clues Are Misplaced
Placing critical cipher clues in a film production over which you have no editorial control was a serious mistake. This aspect is worth examining in detail, as it requires no specialized cipher-solving knowledge.

The controversy centered on two extra clock times. Justin has explained that these times were “slipped in” by the editor and that he only noticed them after the series aired. He even built a probability model to weigh the impact of when and how to eliminating them. In my view, this effort, while creative, was unnecessary. The issue was self-inflicted and could have been prevented with better upfront planning about how the clues would appear on screen.

About 4:02
This time should not be treated as a valid clue. Unlike every other clock shown, we never see a full, clear view of it. The hour hand is visible slightly past 4, but the minute hand is absent. Without a complete reading, there is no reliable basis for interpreting it. Because this time is not presented in its entirety like the others, it should never have been considered equivalent. Attempting to “eliminate” it only adds confusion.
I suspect this shot was included simply because the camera was rolling when Justin turned the clock. The editor, aware that clocks were significant, likely thought the movement looked intentional and hence, kept the footage.

About 5:26
This is the core of the problem. The 5:26 time first appears in Episode 2 at the 31:40 mark and reappears in 12 more scenes, totaling about two minutes of screen time. These scenes cover emotionally heavy topics: a death in the Forrest Fenn treasure hunt, Justin’s brother’s suicide, and other sensitive subjects. Cutting or altering them would have damaged the narrative.

Justin clearly knew the content he was discussing at 5:26. To avoid turning such moments into unintended clues, the better approach would have been to either obscure the clock (forcing it stop-running) or ensure the dialogue at those moments was irrelevant to the series so that they wouldn’t make the cut. But asking an actor to behave irrationally just to hide a clock time would have been poor directing.

I tried to salvage this issue by looking for a consistent reason to disqualify 5:26. In 10 of the 13 appearances, the pillow with the X mark imprinted on it lies flat on the couch, unlike all other clock scenes where the pillows stand upright. In the three instances where the pillow is upright, Tucker is sitting on the same couch. However, this distinction doesn’t hold up cleanly: Yes, in any other clock times, the pillow is always upright but Tucker is sometimes present and sometimes absent. It feels like special pleading rather than a solid rule if I say only in this 5:26 instance when Tucker and upright pillow are both present means exclusion. Ultimately, I couldn’t find a convincing, consistent way to exclude 5:26 without introducing new inconsistencies.

I may be mistaken in some of my observations about the cipher’s flaws and clue placement. That said, it seems far simpler and more reliable for Justin to have embedded the clues in his book, where he has complete control over the content. I’m currently working on identifying the six relevant times in the book. I previously attempted a Playfair cipher on the chapter titles and posted “Tucker the Container.” Although my solve was amateurish, it pointed to the correct answer—I was among those who guessed the container right.

I hope this critique of the cipher design makes logical sense. I’d welcome any thoughts or corrections

Since Justin confirmed the cipher has been solved, there were noisy commotions from all corners. Accusations, innuendos, and conspiracies are flying around.

As an average Joe, a first-time treasure hunter, an outsider, and a willful participant, I think I have fair observations of the drama and I can provide a layman’s defense for Justin.

He should have eliminated the two useless clock time sooner

There might be a legitimate reason not to do that earlier. What if the “useless” times are useless only to the cipher but still be part of the treasure clues as so many searchers are believing now. Although the question of time didn’t specify whether they’re meant for solving the cipher, Justin might have been occupied by the cipher since he knew someone was close and needed a push? Without eliminating these times, the cipher would never be solved - even if and when the treasure is found.

He helped the Misfit to solve the cipher

Along with the logic above, once he announced the elimination, it’s a fair game to all cipher crackers. Perhaps he knew, before the summit, that the Misfit group was working on the cipher and on the right path. Instead of secretly helped them, he chose to announce in public. As such, no fraud was committed.

The integrities of him and the hunt are compromised.

By disclosing the elimination in public, not only his integrity was not compromised, in the contrary, was strengthened in retrospect. As Justin said in his announcement: “Solving this cipher does not bring anyone closer to the treasure. Not a step. Not an inch. The answer is a nod to the vessel that is part of the treasure itself — flavor, atmosphere, a wink. It does not point to a location, a region, or a coordinate.” Therefore, the integrity of the hunt is still intact. I didn’t believe Justin would give hint(s) to his inner circle to comprise his hunt. He has his legacy and ongoing treasure hunt creation, in the pipeline, to guard.

There you have it. My common sense defense of Justin.