# The Hidden Mechanism

Within the 888 tokens of GlyphVoid, five contain a key.

The keys are not announced. Their token IDs are not published. The only thing stored on-chain is a cryptographic hash of the answer — a keccak256 hash of the five token IDs sorted in ascending order. The hash is immutable. It was set when the contract was deployed and cannot be changed by anyone, including the creator.

The keys reveal themselves through the art.

Every GlyphVoid token has a chance to contain a hidden cipher glyph — rendered at near-invisible opacity on the black canvas. It exists in the SVG source code. You can find it by examining the raw SVG, adjusting image contrast, or writing a script to scan for low-opacity elements.

Not every hidden glyph marks a real key. Decoys exist — faint glyphs scattered across tokens of all rarity tiers. The community must determine which of the many tokens containing hidden glyphs are actually one of the five real keys.

The hidden glyph type used for real keys belongs to a specific glyph family reserved for this purpose. Careful comparative analysis across many pieces will eventually reveal a pattern. This is a community puzzle — it likely cannot be solved by one person examining one piece.

**What the metadata reveals**

The token metadata does not include a trait indicating whether a hidden puzzle glyph is present. The puzzle must be found visually, not by reading trait lists. This is intentional.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://glyphvoiddocs.gitbook.io/undefined/the-puzzle/the-hidden-mechanism.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.