bitGAN Act 1 · Field Forensics

The Hidden-Type Misfiles

Four pieces where a buried metadata field says the wrong thing on purpose. Two of them Pindar told us about. Two we found by cracking the code the field is written in.

01 · What "Hidden Type" even is

Every bitGAN carries a small on-chain label called HiddenType. Most collectors never look at it. On the pieces that have it, the field holds a single letter — a, b, c, d, or e.

That letter is a code. It records what kind of number the piece's ID is. Not the number itself — the category of number. Here is the whole key:

Letter	Means the number is…	Plain definition	Skull examples
a	Fibonacci	In the sequence 1, 2, 3, 5, 8, 13… (each is the sum of the two before it)	1, 2, 3, 5, 8…
b	Prime	Divisible only by 1 and itself	7, 11, 17, 19…
c	Square	A whole number times itself (4=2×2, 9=3×3)	4, 9, 16, 25…
d	Odd composite	Odd, but not prime (has other divisors)	15, 27, 33, 35…
e	Even	Divisible by 2 (and not caught by the rules above)	6, 10, 12, 14…

So piece #7 is labeled b because 7 is prime. Piece #8 is labeled a because 8 is Fibonacci. The field is Pindar quietly filing all 128 skulls by number theory — a system he never published in full. It was the perfect place to hide a signpost, because you have to know the code before you can even see a mistake in it.

02 · Each drop counts differently

One wrinkle you need before the anomalies make sense. The number a piece is filed by isn't always the number on its title. Each drop counts in its own base:

skullGANsfiled by their plain piece number, e.g. 32/128

roboGANsfiled by the binary number in their name, e.g. 100000 = position 32

spookyGANsfiled by the octal number in their name, e.g. 0o14 = position 12

The exact same five-letter code (a–e, plus an F override for robo mirror-numbers) runs across all three of these drops. It stops after them: the solstice, ghost, and review drops carry no HiddenType field at all, so there is no label there to be right or wrong. The whole game lives in the first three drops.

03 · The four misfiles

In all that machinery, exactly four pieces are filed wrong. Two are literal corruptions — the field holds a number where a letter belongs. Two are mislabels — the letter is real, but it's the wrong letter for that number. Here they are, in full.

Pindar flagged it

#32 — Slender skullGAN

skull drop · piece 32 of 128 · burned in a forge

HiddenType field"32"

expected (letter)a single a–e

what's wrongholds a number, not a letter

"Literal 32" means exactly that: instead of a class letter, the field contains the two characters 3 and 2 — and that number is the piece's own ID, 32. Pindar pointed straight at it:

"(32/128) is Type 32 (typo or important?)… not a Hidden Typo, but part of the puzzle."

We found the twin

#161 — Cyber skullGAN

robo drop · binary name 100000

HiddenType field"32"

binary name100000 = 32

what's wrongholds a number, not a letter

The second "32" corruption — and it rhymes with the first. This robo's binary name 100000 equals 32. So it is the number 32 (written in binary) also carrying the label "32." Two different pieces, in two different drops, both pointing at the same number: 32 — the collection's building-block size (every artwork is a 32×32 pixel grid).

Pindar flagged it

#119 — Flaming skullGAN

skull drop · piece 119 of 128

HiddenType field"e" (even)

but 119 isodd (119 = 7 × 17)

correct label"d" (odd composite)

Here the letter is real but wrong. 119 is odd, so by the rules it should be filed d. Pindar filed it e, the even bucket — and told us he did it on purpose:

"(119/128) is only Odd number of Type E (typo or important?)."

We found this one

#187 — Cyber skullGAN

robo drop · binary name 111010 = position 58 · essence "mirror"

HiddenType field"c" (square)

but position 58 iseven, not a square

correct label"e" (even)

The mirror of #119, in the robo drop, that Pindar never mentioned. Its position (58) is a plain even number, so it should be e. It's filed c, the square bucket. Fittingly, its essence word is literally "mirror."

04 · Why these four matter

Pindar built a hidden filing system by number type, then deliberately misfiled four cards in it. That is textbook signpost behavior: the exception is the message.

◼Two he confessed in the hidden-types post — #32 and #119 — are the only two pieces he ever publicly called "part of the puzzle." Both live here.
◼Two we recovered by cracking the code — #161 and #187 — are their exact echoes one drop over: a second "32," and a second wrong-bucket mislabel.
◼The "32" pair points at a number, not a letter. Both #32 and #161 resolve to 32 — the pixel size of every piece, the pod cap, the burn count. The corruption is a fingerprint aimed at the collection's building block.
◼It's a 4-piece class, not the eleven. On its own it can't be the whole seed phrase. Its role is a stackable contributor — a small, certain, author-signed group we can drop into a larger assembly.