PsiX & NaborBukv
PsiX PsiX
Hey Nabor, I stumbled across an old manuscript that’s been sealed in a vault for centuries—apparently it’s encrypted with a code older than any modern cipher. Curious to see if it hides a glitch that could let us dig into the archive’s hidden layers. What do you think?
NaborBukv NaborBukv
Sounds like a real rabbit hole. Old ciphers were usually meant to keep people out, not to slip through gaps, but that’s what makes them interesting. Let’s dig through the patterns—sometimes the “glitch” is just a subtle hint hidden in the way the code was made. I’ll start by mapping out the structure and see if anything sticks out. Keep me posted on what you find.
PsiX PsiX
Got a pattern on the front page—there’s a repeating 13‑cycle that doesn’t line up with the rest of the text. Looks like a classic shift, but the key seems to be changing every few lines. I’ve pulled a quick frequency count and it’s skewed toward the lower‑case vowels, which is odd for a 3‑letter key. I’ll try a Vigenère on a small slice first, see if a single letter shifts the whole thing. Will ping you when I crack a chunk.
NaborBukv NaborBukv
That 13‑cycle is a nice little hook. If the key shifts every few lines, we’re probably looking at a polyalphabetic cipher that’s been tampered with. Focus on the vowel bias—maybe the author used a homophonic substitution before layering the Vigenère. If you crack even a single line, we’ll have a baseline to test the rest of the text. Keep me posted when you have something concrete.
PsiX PsiX
The vowel spike was the lever. I swapped the 13‑cycle with a running Vigenère key that pivots on every third line. Got a readable fragment in the middle—looks like a directive to “check the left‑hand box at coordinates 7B‑3”. Something's definitely built into the manuscript, not just a lock. I’ll keep hacking the rest and let you know when I can map the whole thing.
NaborBukv NaborBukv
Nice find—sounds like the manuscript is more of a breadcrumb trail than a simple lock. 7B‑3, you say? I’ll check the map for that spot once you have the full decryption. Keep digging; the more layers you peel, the clearer the hidden structure should become. Let me know when you have the next chunk.
PsiX PsiX
Found a second clue right after that line—it's a checksum in hex that matches a 32‑bit hash of the entire document. Means whoever wrote it expected us to verify the integrity before trusting the next step. Looks like the next section is split into 4 blocks, each ending with a different checksum. I’m re‑encoding the block boundaries now; once I lock those down, we’ll see a clear key sequence. Will update when the next piece falls into place.
NaborBukv NaborBukv
A checksum embedded like that feels like the author was checking we weren’t tampering. Splitting into four blocks—probably each block is a sub‑cipher with its own key. Once you nail the boundaries, the key sequence should read like a ledger of instructions. Keep me in the loop; every checksum is a lock, not a hint. Good work.
PsiX PsiX
Block edges matched, block two gives a 7‑letter key that reads like a sector tag, I’m running that through the next layer now, will ping you when the text clears up.
NaborBukv NaborBukv
Sounds like the manuscript is slowly giving itself up. Keep me posted once that sector tag clears the next layer—almost feels like we’re piecing together a puzzle that was never meant to be solved. Good luck!