<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Coinselor on Medium]]></title>
        <description><![CDATA[Stories by Coinselor on Medium]]></description>
        <link>https://medium.com/@coinselor?source=rss-c3434a3104af------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5fUkwJj75IFQvyvEE59_iA.jpeg</url>
            <title>Stories by Coinselor on Medium</title>
            <link>https://medium.com/@coinselor?source=rss-c3434a3104af------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 18:45:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@coinselor/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Zenon’s Treasure Hunt: Part 2/?]]></title>
            <link>https://medium.com/@coinselor/zenons-treasure-hunt-part-2-4cc79155efe8?source=rss-c3434a3104af------2</link>
            <guid isPermaLink="false">https://medium.com/p/4cc79155efe8</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[taproot]]></category>
            <category><![CDATA[zenon-network]]></category>
            <dc:creator><![CDATA[Coinselor]]></dc:creator>
            <pubDate>Thu, 25 Dec 2025 18:29:37 GMT</pubDate>
            <atom:updated>2025-12-30T03:10:59.498Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>UPDATE: The claim that the genesis hash could have been computed at taproot block time is not accurate. There was a snapshot taken around Nov 22, 2024 of the Legacy chain, and I assume of the Incentivized Testnet PlasmaPoints balances. It becomes infeasible for any hash of any of the dual ledgers to be computed prior to that.</strong></p><p>I did not expect to write a continuation to this treasure hunt exactly 4 years later, but… here we are.</p><p>Over the last 4 days, I’ve tried so many different things to try to crack the puzzle that the best thing I can do, for my future self (in the off-chance that I get to retry this madness in December 2029), is to document what I have already tried. I cannot go over everything, I can’t even remember it all. But, I can try to categorize the types of solutions I’ve explored and the thought-process behind them.</p><p>When I first tried to solve this, four years ago, I had very little knowledge of how computers actually worked. I had basically no programming experience, all I had was write-ups of other CTF-style puzzle solutions, and the vast knowledge available to me on the internet. However, without understanding the foundational computer science basics, it was an almost impossible task back then.</p><p>Today, I have gathered a lot of experience in multiple high level programming languages, I understand a lot more of the fundamentals, and recently I’ve enjoyed dabbling into programming languages that deal with building blocks more directly, particularly c++ and rust. One of the pitfalls of solving algorithmic challenges in Competitive Programming is making sure you are parsing the inputs and outputs correctly i.e eliminating invisible new line characters, etc. All these bits of knowledge have been of great help in attempting a new crack at the puzzle, I can more clearly see the matrix underneath, and I’m glad to know my original proposed solution, although not entirely complete, namely the application of performing bits XOR operations is probably a part of the solution.</p><p>But more knowledge isn’t all, the world has also changed, I don’t have to google everything, I can directly talk with a LLM model to explore/research any obvious gaps in my understanding. Heck, you could even have the thing autonomously take a shot at it. I do not recommend this option. You will end up with hundreds of files that are completely useless because the SOTA models cannot count how many z are in this thing and miscalculated a hash.</p><p>Before starting, I was confidently thinking: “There’s no way I do not solve this now”.</p><h3>The Facts</h3><p>I went back to make sure I had all the important pieces of information I needed. In case anyone is dumb enough to give this a try, here’s what you need to know.</p><p>We had solved two sequential puzzles before this one, each provided 4 bip-39 seed phrase words, and each was an isolated puzzle with no relationship to the previous one. The first one had you fuse inside the syrius wallet during Zenon’s incentivized testnet, an amount of plasma. You were solving for MAX_MONEY, which turned out to be Bitcoin’s MAX_MONEY, doing so would unlock the first 4 words (I believed they showed up in like a syrius notification):</p><p>oblige dilemma hurry disorder</p><p>The second puzzle was something about the Voyager Golden Record sent to space, I can’t recall what the solution was, but again you provided it somewhere in syrius and in came the second notificaton:</p><p>happy spoil shiver key</p><p>We were starting to feel good about solving this, pretty sure we had a 90% success rate among participants (10% of the people solved it immediately, the rest copied the homework of others just to claim some PP), but boy, were we in for a disappointment.</p><p>The last piece of the puzzle was introduced with the following message:</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//x.com/Zenon_Network/status/1459863534330957825%3Fref_src%3Dtwsrc%255Etfw%257Ctwcamp%255Etweetembed%257Ctwterm%255E1459863534330957825%257Ctwgr%255E728b7abd3bf2a478204bd0ccb628d818dada4186%257Ctwcon%255Es1_c10%26ref_url%3Dhttps%253A%252F%252Fcdn.embedly.com%252Fwidgets%252Fmedia.html%253Ftype%253Dtext2Fhtmlkey%253Da19fcc184b9711e1b4764040d3dc5c07schema%253Dtwitterurl%253Dhttps3A%252F%252Ftwitter.com%252Fzenon_network%252Fstatus%252F1459863534330957825image%253Dhttps3A%252F%252Fi.embed.ly%252F1%252Fimage3Furl3Dhttps253A252F252Fabs.twimg.com252Ferrors252Flogo46x38.png26key3Da19fcc184b9711e1b4764040d3dc5c07&amp;image=" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/56bb621088388a51ea885c805030059f/href">https://medium.com/media/56bb621088388a51ea885c805030059f/href</a></iframe><p>The word <strong>key</strong>. Seven characters. And most importantly, a pointer to a Bitcoin block. Not any block, the Taproot upgrade block. One that enables new features within Bitcoin, of particular importance to us: S c h n o r r (7) signatures, and T a p r o o t (7) addresses that leverage them.</p><p>Now, let’s look at the raw information provided to us:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/401/1*oGUTDmfiYud1WsFQxbq1Dw.png" /></figure><p>A sequence of bytes, cleverly sized to fit in BTC’s OP_RETURN that when decoded into ASCII/UTF-8 provides that lovely ZNN ascii logo embedded in Bitcoin’s history, forever. With it, embedded into the ascii art itself, we find four base64 strings. Four years ago, I was even doubting what I was looking at. Today, I can confirm this is four different strings due to the way padding (the = characters) works in base64. From now on, we’ll refer to them as s1 s2 s3 s4 top to bottom. After all, the order in which they were delivered to us might have an important role to play. Suffice it to say decoding the base64 strings into utf8 leaves you with total unreadable garbage.</p><p>I can also confirm <a href="https://medium.com/@coinselor/zenons-treasure-hunt-the-missing-4-words-c99cbef8c65#:~:text=BTW,etc">it’s not base58</a>, since they include characters Satoshi removed from the set.</p><p>The last known fact is a hint.</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//x.com/Zenon_Network/status/1461013302369132544%3Fref_src%3Dtwsrc%255Etfw%257Ctwcamp%255Etweetembed%257Ctwterm%255E1461013302369132544%257Ctwgr%255Ea9e1b7082e0c6a7ce6c701c167e52219da2c9348%257Ctwcon%255Es1_c10%26ref_url%3Dhttps%253A%252F%252Fcdn.embedly.com%252Fwidgets%252Fmedia.html%253Ftype%253Dtext2Fhtmlkey%253Da19fcc184b9711e1b4764040d3dc5c07schema%253Dtwitterurl%253Dhttps3A%252F%252Ftwitter.com%252Fzenon_network%252Fstatus%252F1461013302369132544image%253Dhttps3A%252F%252Fi.embed.ly%252F1%252Fimage3Furl3Dhttps253A252F252Fabs.twimg.com252Ferrors252Flogo46x38.png26key3Da19fcc184b9711e1b4764040d3dc5c07&amp;image=" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/933ddb1af047952b7eaf50aee5e903fc/href">https://medium.com/media/933ddb1af047952b7eaf50aee5e903fc/href</a></iframe><p>You should have everything you need to start, good luck. Do not worry, the fact that you are starting with a four year delay does not matter, shit will probably remain unsolved for another four years… or will it?</p><h3>The Monkey Brain Attempts</h3><p>🐵: Let’s guess the word! It’s a key!</p><p>There goes 2 hours of your life trying to XOR every possible 7 character word that would make any sense trying to see if they return anything meaningful. The 2 hours are spent in a live conversation with Gemini live while some sub agents are actually coding the solution. The conversation goes something like:</p><p>😐 “Let’s play a game, you have to guess the seven character word.”</p><p>👰 “Sounds fun.”</p><p>😐 “The key to bitcoin smart contracts is (blank). Remember, it’s seven characters”</p><p>👰 “Multisignature.”</p><p>😐 “I said seven characters.”</p><p>👰 “Hyperbitcoinization.”</p><p><em>Looks at coding agents still going… 👀 Well… fuck it.</em></p><p>😐 “Let’s try again. We are about to get invaded by an alien species if you do not guess the correct word. Billions of lives are at risk. Think character by character.”</p><p><em>Two hours later…</em></p><p>Nothing has worked. The solutions tried include every lowercase, uppercase and capitalized version of: <em>Schnorr, Taproot, Satoshi, Mainnet, Hashrate, Witness, Mempool, Halving, Address</em>… etc… I know, most don’t even make sense. Who cares, its free Opus weekend.</p><h3>The Elegant Brain Attempts</h3><p>At some point, after playing with hashes inside taproot for 96 hours, it occurred to me. Hold on a second:</p><p>The key to bitcoin smart contracts is <strong>hashing</strong>.</p><p>Quantum computers can’t break <strong>hashing</strong>.</p><p>This makes way too much sense in the context of everything so far. Is the key a hash? Could it be this simple? If the ascii art itself, where the strings are embedded, was used as the key after being hashed, they could have generated the encrypted strings with it, then remove the zzzzzzzzzzz characters from it, and you would have a perfectly contained puzzle. Way too elegant of a solution to dismiss so easily. I’m suggesting we should sha256 this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/475/1*fIt2DOX1dR8OStfmLAIppQ.png" /></figure><p>and use it as a key. I don’t know, the fact that these 6 lines of pure ‘z’ characters are easy to “reconstruct” seems like a good candidate.</p><h3>The Brainroot Attempts</h3><p>Alright, alright… “Gemini I call you later”.</p><p>Let’s focus. We have an actual hint. Let’s use it.</p><p>Quantum computers can’t break it. “It” is interesting. Very interesting. See they could have said “them”, so we know it’s not a plural like signatures. Yes, the fact that I had to come to this realization after thinking about this for longer than I care to admit is bad, really bad. But it gets worse, much much much worse…</p><p>The bit XOR operation and One Time Pads as originally suspected four years ago still hold true, but not knowing what to use as a key is pretty much a deal breaker. Let’s see what else fits the clues. I guess anything Taproot related is a pretty good candidate given the context, so let’s dive deep.</p><p>What features of Taproot could match the claim that quantum computers can’t break it?</p><p>Well, anything that uses Elliptic Curve Cryptography goes out the window, which is basically the whole thing 😂. See there’s this thing called Shor’s Algorithm that allows Cryptographically Relevant Quantum Computers (CRQCs) to break the widely used ECC primitives.</p><p>So what’s left? This is left: t</p><p>WTF is t? It’s the <em>tweak</em>. The thing that we will explore the rest of the 94 hours remaining in the 4 day span to try to reverse engineer how someone could have generated a puzzle using <strong>“it”</strong>.</p><p>First important concept you need to understand. The <em>tweak </em>is a hash. In fact, according to BIP341, the tweak is defined as the hash of the internal public key combined with the Merkle root of the script tree.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/461/1*NCNB35dOGmnpDHAglovlKw.png" /></figure><p>Did I lose you already? I hope not.</p><p>See the problem is, this is just the actual BIP341 implementation, in theory, this hashing trick to derive a public key Q using the internal public key P and some hash of P and some data (m in the above formula), does not have to follow their exact implementation. Think of the actual BIP341 implementation as some super-secured white-bearded wizard-approved version of the same thing. It requires these double hashing of tags aka TaggedHash and other implementation specific things. But why is it problematic? It’s problematic because we are working with hashing functions, inside a hashing function. Any minor deviation from what the original authors of the puzzle used and it becomes a useless endeavor. Our possibilities for how the tweak could be used just significantly increased. I’ll assume moving forward since there’s an actual spec that’s what the authors might have used.</p><p>But man… I’m just trying to solve some good looking ascii art and I’ve been reading these BIP specs for way too long.</p><p>How can I use this ****? Well I need P, that’s for sure, or Q. Do I have that?</p><p>Here’s where we learn about the 32-byte x-only public keys and the subtle difference with the legacy compressed 33-byte format. Yes, these people count bytes for a living.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pfUR1ce-fPGjeCW5qYBy9Q.png" /></figure><p>First AI slop screenshot so far? We are under performing.</p><p>Ok. 32-bytes, do we have them? In fact, we might. Remember our initial s values? It turns out s1 and s4 are both exactly 16 bytes each. But why are they spread apart and not just s1 and s2 . Good question. Another one to the stack of unanswered questions. If you ask AI it would make some shit up about this being a standard practice to create an “envelope” around critical data, like how PGP keys are wrapped in headers and footers:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*DbTCx-NC9tNqsU23M3ZQLg.png" /></figure><p>Fine, they are paying trillions for these data centers, maybe s2 and s3 are critical. <strong>We’ll keep that in mind</strong>.</p><p>What next? Well, we can verify if the combination of these 16-byte halves forms a valid 32-byte x-coordinate that sits on the secp256k1 curve. If it does, congrats, we’ve found ourselves a candidate for P (the internal key). Now, the hunt is on for Q. Remember, Q is the key we actually see on the blockchain (the Taproot output key). That leaves m, the message or data. Is it possible that s2 and s3 <em>are</em> the Merkle root? Or perhaps the script path itself? If the puzzle author followed the BIP341 spec to the letter, they ran a TaggedHash on P and this m.</p><p>Hmm… this sounds possible, but what are we trying to accomplish here? We assume there’s 4 words in the puzzle somewhere. Maybe there’s also a personal congratulatory message by Mr. Kaine. Maybe by deriving Q we would be able to satisfy a script path spend by reconstructing the script, but for that we’ll need like a hint, maybe a known OP_CODE or something. The strings are unreadable, but maybe if we interpret the base64 as hex values and try to map them to known OP_CODES we’ll get a clue.</p><p>Nah, another dead end. Oh, wait… another TminusZ drop. Wait a second… This one talks about Bitcoin anchors using Taproot, seems relevant, let’s dig in 👽.</p><p>Wow, ok… this is interesting. Very relevant. It’s basically the same thing, but using a very specific tag “BTC_ANCHOR_V1” with the purpose of committing the state of Zenon into bitcoin and having a way for everyone to verify it. That’s cool, forget the words. We can always brute force them with GPUs. This is way more interesting…</p><p>Consider the timing of the Taproot puzzle. It was right after the Zenon incentivized Testnet, EXACTLY at the taproot upgrade block, and shortly before NoM’s genesis. Is this a coincidence? No way… so what would be the thing to “infer” ?</p><blockquote><strong>The Puzzle committed the genesis block of Zenon in a verifiable way</strong>.</blockquote><p>Somehow… but would it be possible?</p><p>It turns out it would be. See, you only need the momentum header with height 1 (genesis) which is computed ahead of time, way before Alphanet was live. So yes, it was possible for the puzzle creators to have this information.</p><h3>The Braindump Attempts</h3><p>P,Q,little p, little q, z, m, r, generators… I’ve got Nothing Up My Sleeve. I swear. Alright. Let’s put the pieces of this puzzle together, shall we?</p><p>Remember those s1-s4 strings? Those were not all the Lego pieces we needed. Let’s recap, s1+s4 or s4+s1 (depending on how much sleep you got that day) — the 32 byte string, is a package deal, a single piece, we’ll call it “<em>the joker”</em>. It’s better to start naming things before we go crazy. I decided on that name because it’s the most versatile piece of them all, you see, 32 bytes is used as a standard value for pretty much anything: a public key, a private key, a merkle root, etc… I’m sure if I keep going down that rabbit hole I end up blaming some intel engineer back in the 90s, so I’ll pass for now.</p><p>Next, we have s2, the 18-byte clue, the round peg in a square hole, we’ll call it “<em>the real thinking emoji”.</em> I have some ideas of what this could be, but none that are good enough to share yet 😂.</p><p>Moving on we have that cute little 5 byte string, s3. The missing puzzle, the actual solution, hiding in plain sight. We’ll call it “<em>the quantum four words</em>”, for obvious reasons, observing them messes up their state, so let’s not look at it until we solve the whole thing.</p><p>Remember the original Taproot construction?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/461/1*NCNB35dOGmnpDHAglovlKw.png" /></figure><p>It looks like we have Q, P, H, m and G. That’s 5 pieces, but H is just derived from P and m, so that brings us down to just 4 Lego pieces. But wait, G is a known constant so that would bring us down to just 3 pieces.</p><p>We need 3 pieces, do we have them? Let’s see… we have: the joker, the real thinking emoji, and the quantum four words. Problem? Well… we are not supposed to even look at the quantum words, so I guess we are down one piece. Let’s go hunting…</p><p>But where? Well, I guess maybe Kaine dropped it in a telegram message. Nah, that would be way too crazy. Maybe there’s another cryptic tweet somewhere, maybe I need to go search the 709631 blocks prior to the puzzle, or the ~200k block after it. Or both.</p><p>After dealing with the fact that I have 4 different time zones in my windows clock, I found the missing Lego piece. A<strong> taproot address</strong>.</p><blockquote>HALLELUJAH — coinselor</blockquote><p><em>As I mentioned in my mostly inaccurate, and wrong article titled “The Real Zenon Enigma”, in the end I hinted at an address with a significant relevance at a BTC Block minted exactly seconds before Zenon’s tweet went out. If you filter for taproot txs in that block, there’s only one.</em></p><p>Actually, it wasn’t the first time I had looked at that address, so I immediately recognized it. However, the first time I ever looked at it, I couldn’t see the matrix underneath, so I did not recognized its value.</p><p>How do I know it’s relevant? Let’s just say the original team had a thing for BTC core contributors…</p><p>Ok, the missing piece, what are we gonna call it? Good question. It’s a taproot address, so maybe carrot? But it’s not any taproot address, no. It’s a taproot address that was spent using the key path spend. That would be the private key of <em>Q</em>, meaning little <em>q</em>, slow aliens. Pay attention! When this was done, it exposed <em>Q </em>to us and, according to the theory above, it cemented the commitment of <em>m </em>on-chain<em>. </em>So… we’ll call it <em>“tweaked carrot”</em>. The good thing about tweaked carrot is that it must always be in the left side of the shared Taproot formula, but like always, there’s a weird case that might over-complicate things, <strong>I’ll explain later</strong>.</p><p>Alright, alright… let’s recap. We needed 3, we have 3. And we know what’s on the left side of the equation. Now it’s just a matter of figuring out which is which for the two lego pieces in the right side of the equation. But this isn’t all, now we have an actual way to verify that we have found the right solution due to the equality. So if we put P and m in their right place, we should get Q, therefore confirming our solution and we can go ahead and look at the cat box with the 4 words.</p><p>I have two Lego pieces, and two possible slots, and I still can’t figure this shit out? That is exactly right! But isn’t that just 4 total combinations? It should be, but it isn’t. Have you ever heard of babushka dolls? The cute little nested russian dolls:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tvAafC3F8VJjKKDgaAy4mw.png" /></figure><p>Well, taproot keys are exactly like that, it could be taproot addresses all the way down to the molecular level. See, you could make Q, be just the internal key P, per saecula saeculorum. Hopefully we don’t have to go that deep…</p><p>Until now, I had not considered very seriously that the joker could be a private key, but now that we have the tweaked carrot, it would be very elegant for the internal key P to be deterministically derived in a verifiable way, meaning <strong>anyone could reconstruct little p to derive P to tweak with m to prove m was included in the on-chain Q</strong>. But again, even though technically, according to the BIP spec, the private keys should be 32-byte (256-bit) integers in the range [1, n-1], where n is the curve order, it is still possible for the real thinking emoji to be the key, just in a less secured way, maybe with padding or with a sha256 of it. There’s also this thing where we could have the multi-layered tweak not have to follow the spec, so we could have the joker be the private key to derive the internal P that gets tweaked with just the real thinking emoji to derive the outer P that follows the spec for a scriptless path (meaning m = 0) that would derive Q.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*3Lg8uUxZYPwEHKIWk1Vskw.png" /></figure><h3>The Steg Attempt</h3><p>I thought I was completely done with this puzzle for a while, but it turns out, you can’t just think really hard about something for a few days and then just shut your brain off completely.</p><p>So, I went to bed, like usual. And I woke up, like usual, except something had changed. I was no longer thinking about the Taproot block or Taproot addresses, I had already closed that chapter in my brain. It was a done deal. But of course, random Zenon thoughts would linger from time to time.</p><p>One of them, in particular, went something like this: “Fuck, kaine, man. I bet that puzzle is some impossible thing. A total rug. Guy was always quoting Satoshi, manually, like literally without even copy pasting, when there was no chatgpt. Imagine that. I remember one time when he said something about how great it would have been if Satoshi had signed his original Bitcoin logo design. He was such a fanboy, I bet he tried to one-up him like how Kobe tried with Jordan. I bet he <strong>signed the freaking taproot puzzle image</strong>. I bet he was banging victoria secret models all along while running experiments on chadass’s mind”</p><p><em>“Wait… Hold up… What did you just say? I said he was banging Adriana Lima’s sister. No. The other stuff about the puzzle image.”</em></p><p>And… that’s it. The next 2 hours of your life are gone. First you go and download the original .png image that was tweeted. Then you look up how lossless image files are perfect candidates for steganography. You then go over LSB, the original medium article, the steg paper that just dropped, then you actually try to understand what actually is a Discrete Cosine Transform and how to apply a chi-square test on pixel data to determine probability of human interference. It’s a trip.</p><p>The result?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*_6PuuLBkhWTJnRY5-3C_ag.png" /></figure><p>An image of the LSB of the green channel with a chi-square test of 0.000000, a mathematical certainty of human intervention. The actual message hand-written by Mr. Kaine with stenography pencil around the edges of the ascii letters. Problem solved.</p><p>Damn… Champagne is over? Fine. “Claude, get me the 4 missing words.”</p><p>I won’t waste any more of your time. It’s anti-aliasing.</p><h3>The Missing Clue Attempt</h3><p>Thank god. Now it’s for sure over. This time I’m done, guaranteed. I mean just look at this image, it looks even funnier when you render only the LSB bit layer. I mean look at the edges, what is that even in the original image?<br>Haha, It’s a one. And there’s another one there. Yeah I remember discarding those in my original post 4 years ago. Totally useless. There’s a q over there too, and over there…</p><p>Fine, I’ll just count them. Why not. I guess I should start top left to bottom right as if reading them normally. Here we go:</p><p>1qqqqq1qqq1qqqq1qqq1q111q1q1qq11qqq1qqqq = 40 chars</p><p>This looks like binary, I guess the q’s are 0s, which means we have:</p><p>1000001000100001000101110101001100010000 = 40 bits</p><p>Wasn’t I assuming the words were in “the quantum words” (string 4) because it was literally 5 bytes / 40 bits. Did I just find the words again for the 48th time? I guess so. Now I can’t quit, can I?</p><p>This changes everything, again.</p><p>For the slow aliens, here’s the TLDR. We have 8 known words, that’s 88 bits of entropy, 11 bits per word. A 12-word seedphrase has 132 bits of entropy. That’s 128 bits + 4 bits of a checksum of the entropy’s first 128 bits.</p><p>88 + 40 = 128. We are only missing the checksum, which is the first 4 bits of the sha256 of the first entropy’s 128. We can now get another valid seed phrase. I tried. It doesn’t match the treasure hunt address.</p><p>I also tried XORing the two 5 byte clues and used it as a key to decrypt the rest, no luck.</p><p>Maybe this whole thing about the puzzle not being a hunt is not a joke…</p><p>And now Stark casually drops that strings 2–3 are the same thing… and there’s no 5 byte clue. LOL. I’m actually retarded.</p><p><em>Throws gamepad out the window.</em></p><h3>The treasure has always been the journey…</h3><p>This was a hell of a learning experience about Bitcoin, Zenon, and crypto in general. I’ve made a lot of mistakes along the way, but without the fundamentally wrong assumptions I would have not learned as much, and that was exactly the point.</p><p>I spent countless hours trying to crack a Taproot output address with a fundamentally wrong assumption. I was using Zenon’s genesis to crack a puzzle when it fundamentally could have not been known by the original developers at the time. Stupid mistake.</p><p>I’ve been looking for clues where none exist, and using the ones we have incorrectly. But I have not given up. That was never an option.</p><p>Some believe there’s no solution:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vuhiSRAiKySXhfh6McVrAA.png" /></figure><p>I can only speak for myself, but based on my comprehensive Zenon experience, this story is not over.</p><p>What might have been inscribed in that block remains a hell of a Puzzle.</p><p>I’ll let the subconscious take over again for a while…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4cc79155efe8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The REAL Zenon Enigma]]></title>
            <link>https://medium.com/@coinselor/the-real-zenon-enigma-88bcf10500d0?source=rss-c3434a3104af------2</link>
            <guid isPermaLink="false">https://medium.com/p/88bcf10500d0</guid>
            <category><![CDATA[taproot]]></category>
            <category><![CDATA[zenon-network]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Coinselor]]></dc:creator>
            <pubDate>Fri, 05 Apr 2024 19:49:45 GMT</pubDate>
            <atom:updated>2024-04-05T19:53:22.695Z</atom:updated>
            <content:encoded><![CDATA[<p>I wasn’t <a href="https://medium.com/@shaimo/the-zenon-enigma-782f8b293bd6">first</a>. I won’t be last.</p><p>My only hope is to understand what’s being built and to become a worthy contributor. My first-ever couple of recorded messages in Zenon’s official Telegram channel dates back to August 10, 2020.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/801/1*FEAjrwHmTeCAMxDS7Y-GiQ.png" /></figure><p>And what story is that, you might ask? One where the protagonist is Bitcoin: its network, its technology, its promise as a revolutionary monetary layer for our species, but more importantly, its limitations, challenges, and how to overcome them to fulfill its original vision as an electronic cash system.</p><p>You see, even for its creator, Satoshi Nakamoto, it was hard to predict how Bitcoin, and Bitcoin mining in particular, would evolve over time. At some point, it became abundantly clear that Bitcoin would not be able to accommodate billions of people on its base layer. In addition to this, Bitcoin still had to deal with other problems: the centralization of Bitcoin’s hashrate, a potential upgrade to quantum-resistant cryptographic primitives, and, more recently, the storage of media files through a clever use of its upgraded and discounted witness field. Therefore, even while being regarded for its consensus immutability, the story of Bitcoin is also one of constant evolution.</p><p>Now, for Bitcoin to evolve, it doesn’t necessarily mean we need to change Bitcoin. In fact, that’s exactly what we want to avoid. It requires thinking outside the box, and the outcome of that thinking is exactly what I aptly called the REAL Zenon Enigma.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yAGL_l-AF8jPhJTSjQGfew.png" /></figure><p><em>Disclaimer: What you are about to read is pure speculation, based on nothing more than an educated guess from a curious mind — one with no prior knowledge in many of the concepts I’m about to cover.</em></p><p>Zenon, also known as the Network of Momentum, is an <strong>end-to-end solution for Bitcoin scalability</strong>. Put more simply, it’s “just” a layer-2/sidechain for Bitcoin. However, in order to fulfill its mission, it has evolved into much more than that. We can comfortably say that the Zenon Network is a standalone, state-of-the-art, feeless, dual DLT layer 1. It not only solves the blockchain trilemma but also introduces a new hybrid Proof-of-Stake and Proof-of-Work architecture with multiple nodes and a dual-coin economy that achieves progressive decentralization over time. It brings to the table revolutionary new concepts such as adaptive smart contracts, unikernel VMs, steganography based NFTs, and much more.</p><p>But let’s put aside the buzzwords and focus on the objective for the rest of this article: <strong>an end-to-end solution for Bitcoin scalability</strong>. In product design, “end-to-end” refers to a comprehensive service or product that addresses a customer’s problem from beginning to end.</p><p>When we consider the Lightning Network, Bitcoin’s most widely used scalability solution, we start to see the issue:</p><h3>tulkooo on Twitter: &quot;Lighting network is easy, all you have to do: pic.twitter.com/Eiaribv8sI / Twitter&quot;</h3><p>Lighting network is easy, all you have to do: pic.twitter.com/Eiaribv8sI</p><p>It’s not trivial for a user to correctly use the Lightning Network. Users end up relying on custodial solutions that implement it. Even then, there are myriad other problems and limitations with the Lightning Network. It’s not surprising, then, to understand why the adoption of the Lightning Network has not taken off.</p><p>A new end-to-end solution had to be designed from the ground up. Just adding a layer on top of Bitcoin was not going to cut it.</p><p>A scalability solution for Bitcoin must be:</p><ul><li>Trustless: Leveraging cryptography and/or encryption to eliminate any need for trusted intermediaries.</li><li>Open, Permissionless, and Censorship-Resistant: Anyone can freely enter and exit without any entity’s control.</li><li>Decentralized: A fundamental property to achieve the requirements above.</li><li>And… of course… scalable: Able to accommodate an order of magnitude more transactions than the base layer.</li></ul><p>The Lightning Network successfully achieves all these characteristics but leaves a lot to be desired in terms of privacy and user experience while adding extraneous liquidity constraints.</p><h3>NoM: An End-to-End Solution for Bitcoin Scalability.</h3><p>Alice has some Bitcoin and is tired of paying fees. She hears about this advanced alien technology and decides it’s worth a try. She downloads <a href="https://zenon.network/#downloads">✦ s y r i u s</a>, a state-of-the-art cross-platform wallet that includes both a Bitcoin node and a Zenon node. She navigates to the Bitcoin tab, imports her wallet, and clicks ‘deposit’. A BTC address is generated. She transfers some BTC to it. Just like that, her Bitcoin moves into the Zenon Network, where she can enjoy transactions without fees, interact with smart contracts, perform peer-to-peer atomic swaps, and more, all without any compromises. She can now withdraw her funds at any time, unilaterally, though she probably never will.</p><p>But how does it work?</p><p><strong><em>Real Disclaimer: What follows is an attempt to piece the puzzle together, through the eyes of a very observant and curious alien. I will not delve into every technical detail, mostly because I can’t, but also because it would take 50 pages.</em></strong></p><h3>Step 1: Alice deposits BTC.</h3><p><strong>Axiom 1: The Sentinel is the Vault.</strong></p><p>When Alice clicks “deposit,” a newly generated “pay-to-taproot (P2TR)” bitcoin address is generated. This is also known as a tweaked public key. This new bitcoin output can be spent by either a public key path or a script path. It looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/349/1*Oo1GSaST5GI-kXzgTlYO5g.png" /></figure><p>Q: the new public key where the funds are sent, a.k.a The Vault.</p><p>P: An aggregated Schnorr Multisignature of Alice and the Sentinel. This is important. It allows Alice to verify the content of the smart contract z where she is depositing the money. Additionally, neither Alice nor the Sentinel can move the funds without cooperation.</p><p>z: A Tapscript represented by the hash of the root of a Merkleized Abstract Syntax Tree. When a spending condition from a leaf is met, proofs for the inclusion of the condition in the script are submitted to the Bitcoin blockchain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IsYSW8xon0vOUv1ZM-E_Cg.png" /></figure><h3>Step 2: Alice receives BTC on NoM.</h3><p><strong>Axiom 2: A Pillar is a BTC Mining Pool.</strong></p><p>Pillars are known as a set of (currently) 94 pillars that produce momentums and validate the consensus rules of Zenon. However, in this context, they can be understood as Bitcoin Mining Pools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sN_6ij1WL92LVX71OaKuvg.png" /></figure><p>Leveraging a <a href="https://forum.hypercore.one/t/merge-mining-feasiblity/381">Stratum v2 implementation</a>, Bitcoin miners can redirect their hash power to a Pillar. Pillars, running both a Zenon node and a Bitcoin node, can submit found Bitcoin blocks. Bitcoin benefits by having a new set of decentralized pool operators, allowing individual control of transaction inclusion into blocks by miners, among many other benefits from Stratum v2. Pillars compete with other Bitcoin Pools for hash rate, and we expect to see a percentage of the ZNN rewards given to Bitcoin miners for this reason. In exchange, NoM benefits from the security of the added weight in the form of hash rate to the network by merge mining NoM’s share chains.</p><p><strong>Axiom 3: A trustless bitcoin representation on Zenon managed by Pillars.</strong></p><p>So far, we have locked BTC that can only be spent by an interactive collaboration between the Sentinel and Alice or by fulfilling one of the spending conditions from the script path. Just like in LN, lets provide Alice for a commitment TX signed by the Sentinel so she can get her BTC back immediately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lilIy-tYQVNtcEfiyEI9nA.png" /></figure><p>Additionally, let’s add a Safety clause in case the Sentinel goes rogue by creating a spend condition leaf to the MAST that gets fulfilled by an m-of-n Threshold Signature Scheme or FROST of the Pillar set. Put simply, the pillars can agree to move the BTC if the Sentinel goes rogue. In this case, I expect a slash of the Sentinel’s locked collateral for a simple reason: increased privacy. We want the Sentinel to collaborate to use the public key path spend of the P2TR as often as possible, to make it look like a regular BTC transaction, increasing privacy by obfuscating the fact that it was BTC bridged to NoM.</p><h4>The MINT Process</h4><p>Powered by a heavily modified version of the <a href="https://www.xclaim.io/">XCLAIM protocol</a>, an embedded NoM smart contract mints a ZTS (Zenon Token Standard) token backed 1:1 by Bitcoin locked in the Vault. For this to happen, a proof of inclusion of Alice’s deposit transaction in a BTC block needs to be submitted to an embedded NoM contract acting as a Bitcoin SPV client that verifies it (also used to pay miners ZNN for the share chain contributions), substituting the need for a Chain Relay as defined by the XCLAIM protocol.</p><h3>Step 3: Alice sends BTC to Bob.</h3><p><strong>Axiom 3: Real bitcoin transactions, kept off-chain.</strong></p><p>Similar to the Lightning Network (LN), but without the limitations imposed by payment channels, each hop between users transacting with BTC on Zenon represents real BTC transactions.</p><p>To prevent Alice from colluding with the Sentinel, or Bob from attempting to claim a commitment transaction from a previous state, intricate Bitcoin scripts with revocation keys might be used, although these are beyond the scope of this article.</p><p>By removing the limitations of payment channels — most notably, the liquidity needed around the payment routes — we can transfer BTC from one user to another just as we would with any other NoM-native ZTS token.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1015/1*9Kj18h9tZZlbt4vJKp-ing.png" /></figure><p>I speculate that BTC on NoM will act as a subclass of ZTS that will require additional data added to each transaction. What this extra data entails is beyond my current understanding, but for simplicity’s sake, let’s refer to it as a “secret.”</p><blockquote>If s y r i u s had a connection to a BTC node, you could make Bitcoin transactions and add data to them. Like inscribing a secret into the transaction. The secret becomes the identifier. <br>— qPP</blockquote><p>As BTC moves through the NoM from user to user, it creates a chain of “partially signed” transactions leveraging either Point Time Locked Contracts (PTLCs) or Adaptor Signatures, with each user attaching the secret that unlocks the previous hop in the chain. For Alice to send BTC to Bob, she will interactively sign a commitment transaction with the Sentinel.</p><p>On one hand, we have the ZTS representation of Bitcoin being transferred from Alice to Bob. On the other hand, we maintain the actual Bitcoin commitment transactions for all balance states until BTC exits NoM. This information could be managed by Sentry nodes and made available to Sentinels for a fee, thereby establishing a trail of Bitcoin transaction breadcrumbs and presenting an improvement in terms of user experience over the Lightning Network’s Watchtower services.</p><h3>Step 4: Bob Redeems BTC</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/529/1*acx26dYuhttr8g_PPRLJcQ.png" /></figure><p>Bob, having finished exploring his brand-new alien toy, decides to return to the comfort of HODLing in his BTC multisig wallet. However, for the Network of Momentum (NoM), this is where things become truly fascinating. My intuition suggests that the system must guard against a broader array of attack vectors during the redemption process than during minting.</p><p><strong>Axiom 4: The Sentinels serve as observers of the NoM consensus.</strong></p><p>When a redeem transaction interacts with the embedded contract that manages the minting and burning of BTC-backed tokens, it comes under the scrutiny of all Sentinels. Independently, each Sentinel begins by assessing the legitimacy of the redeem request. To achieve this, it consults another Zenon component, a Sentry node, to obtain fraud proofs.</p><p><strong>Axiom 5: Sentries represent the next evolution of Watchtowers.</strong></p><p>Sentry nodes function as an incentivized oracle layer, safeguarding and cataloging fraud proofs on behalf of users.</p><p>Given the anticipated final design, which will likely prioritize privacy, it appears probable that the Sentry will need to authenticate the validity of transactions tracing back to their NoM mint by inversely reconstructing the cryptographic path taken.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3M3w_OAMO5_8ivxy4OXhVw.png" /></figure><p>After this cryptographic wizardry has taken place, a definitive verdict is relayed back to the Sentinel. Upon receiving an approved transaction, the Sentinel executes a Proof-of-Work (PoW) on its data and forwards it to another random Sentinel, initiating a repeat of the verification process. This cycle continues for a minimum of three hops, with each iteration adding a PoW layer, thus forging the renowned PoW links and solidifying the credibility of this claim. At this point, the transaction is ready for incorporation into a Momentum by the consensus layer and is consequently dispatched to the Pillars.</p><p>This underscores the critical role of Sentinels in monitoring the NoM consensus; only after the transaction has been thoroughly validated and incorporated into a Momentum can the BTC-backed NoM asset be burned and released on the Bitcoin layer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i5bFQ5i1uVY3nKrw-kwRdA.png" /></figure><p>I suppose that if Bob presents a legitimate redeem transaction originating from multiple vaults, checks and balances will be conducted, and a vault possessing the requisite locked BTC will be selected to finalize the withdrawal. The funds will then be consolidated via an off-chain commitment transaction to the chosen vault. From time to time, I envision some a<a href="https://github.com/lightninglabs/loop">lgorithmic rebalancing of on-chain</a> transactions for the Sentinel vaults occurring during periods of low transaction fees on the base layer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gcgt22AU8mULz_WsaJJFfg.png" /></figure><h3>Zenonize Bitcoiners, Zenonize the World.</h3><blockquote>If it’s pure trustless permissionless tech worthy of a cypher punk, they will be pleased. And the rest of the community follows and adopts their thoughts. <br>— qPP</blockquote><p>I’m confident that the prospect of feeless transactions alone will persuade you to keep your Bitcoin in the Network of Momentum (NoM).</p><p>However, if you remain unconvinced, there’s more to consider. Zenon introduces two coins, $ZNN and $QSR, not as a means for developers to enrich themselves — a criticism levied against the vast majority of cryptocurrencies today — but because, as Satoshi Nakamoto realized, a token is essential, and for a Proof-of-Stake system, two tokens are better than one. To reference a Bitcoin magazine article on the <a href="https://bitcoinmagazine.com/technical/understanding-the-bitcoin-l2-trilemma">BTC L2 Trilemma</a>:</p><blockquote>“…the absence of a token still means reliance on a trusted bridge or advanced hardware configurations that await market validation<strong>.”</strong></blockquote><p><strong>Axiom 6: Liquidity finds the path of least resistance</strong></p><h4>A Liquidity Blackhole</h4><p>The process described for Bitcoin interoperability can be replicated across any chain, regardless of smart contract capabilities. Now, imagine that anything bridged to NoM not only benefits from feeless transactions but also receives actual yield for locking assets in a liquidity pool, incentivized by protocol emissions. This would facilitate the first-of-its-kind trustless, permissionless, and uncollateralized cross-chain swaps.</p><h4>Final Thoughts</h4><p>In our discussion, we have outlined the unique architectural components of the Network of Momentum, with a particular focus on enhancing Bitcoin scalability. For the sake of conciseness, we’ve skipped several details about the network that are crucial for understanding the comprehensive solution designed. We encourage readers to delve deeper into <a href="http://zenon.network/">Zenon</a>, consult the <a href="https://www.atsocy.com/assets/blog/whitepapers/whitepaper.pdf">whitepaper</a>, and join us in turning this vision into reality. It’s worth noting that more than 80% of what I’ve described here exists only in my imagination, inspired by the pioneers of this project.</p><h3>But… does it really only exists in my imagination?</h3><p>Taproot was activated on BTC block <a href="https://mempool.space/block/0000000000000000000687bca986194dc2c1f949318629b44bb54ec0a94d8244">709,632</a> where the Zenon Network name will be forever inscribed. The first Taproot spend was in Block 709,635. Find out <a href="https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-November/019598.html">why</a>.</p><p><a href="https://medium.com/u/3a1121c12159">Zenon</a> tweeted at exactly 12:35 UTC on Nov 15, 2021:</p><h3>Zenon on Twitter: &quot;Day 4Never doubt you can make history.You already have.#Bitcoin #Taproot $ZNN pic.twitter.com/tLkdPbstND / Twitter&quot;</h3><p>Day 4Never doubt you can make history.You already have.#Bitcoin #Taproot $ZNN pic.twitter.com/tLkdPbstND</p><p>BTC Block 709,828 was mined exactly at 12:35:39 UTC 2021–11–15.</p><blockquote>My guess is what ever they were using for ZX and Xstake was not completely permissionless. And taproot enabled this. Maybe that’s why Mr. Kaine said we already made history. Maybe they did the first permissionless cross chain swap with the prototype they have.</blockquote><blockquote>— qPP</blockquote><p>Coincidence? There’s 3,310 transactions in that block.</p><p>Good luck.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*gPwVSxIbxVU3HsUq43cQAA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88bcf10500d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zenon’s Treasure Hunt: The missing 4 words.]]></title>
            <link>https://medium.com/@coinselor/zenons-treasure-hunt-the-missing-4-words-c99cbef8c65?source=rss-c3434a3104af------2</link>
            <guid isPermaLink="false">https://medium.com/p/c99cbef8c65</guid>
            <category><![CDATA[treasure-hunt]]></category>
            <category><![CDATA[zenon-network]]></category>
            <category><![CDATA[zenon]]></category>
            <dc:creator><![CDATA[Coinselor]]></dc:creator>
            <pubDate>Wed, 15 Dec 2021 23:28:45 GMT</pubDate>
            <atom:updated>2021-12-15T23:54:53.911Z</atom:updated>
            <content:encoded><![CDATA[<p>Embedded in the first BTC block after the taproot upgrade, the following ascii art was included by the Zenon team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*YRvIQwt3Hlx3IlX6KKJwYg.png" /></figure><p>At first glance, I had no idea what I was looking at. Keep in mind I’m an aspiring programmer with no formal CS education. Throughout this article, I will try to describe my thought process and the stuff I learned along the way. I spent a lot more time I care to admit on this puzzle.</p><p>The first giveaway are the ‘=’ signs on line 1, 3, and 4, as well as the alphanumeric characters. After a few minutes of google, It turns out we are <em>probably </em>looking at base64 encoded data. Base64 encoding is often used to guaranteed the integrity of the data being delivered (as applications can try to incorrectly interpret the raw data). By using base64 encoding, your data gets transformed into safe asci characters that can be delivered like normal text. This encoding was probably used so we could get the raw data posted into the bitcoin blockchain in a way that it would maintain it’s integrity.</p><p>The first couple of days were very painful, as I was using some random base64 encode/decoding websites in conjunction with some random decryption algorithms and random keys. I even found websites that were giving me different results with the same inputs. The possibilities are basically infinite, so I had to take a step back and think about what we knew about the puzzle so far. Something was immediately obvious, I needed better tools, and since I was learning how to program anyway I figured this would be good practice if I had to edit some python scripts or whatever. Eventually, I ran into an absolutely legendary tool named <a href="https://gchq.github.io/CyberChef/">CyberChef </a>with everything we might ever need, but most importantly, it was a tool I could trust the output to be correct.</p><p>One thing I would like to mention here is that, at this point, I had already disregarded everything but</p><pre>BynQtpeUyWTXKGTrGhdV2Q==<br>tVMd3L1CKM4wFmyxEEEUV2bY<br>4Fdzw1k=<br>vtv3f5aKY0jGQglP9a1AGw==</pre><p>as a clue. I came to this conclusion after finding a few examples of how one would generate ascii art with a program like <a href="https://github.com/TheZoraiz/ascii-image-converter">this</a>. It turns out all characters like ‘q, ;, ., and ,” used in the original Zenon logo ascii art were just generated automatically by the program. My guess is that every single character from the set above used to be a “z” on the original Zenon logo ascii art.</p><p>Great, we have removed a lot of the noise and we can just focus on the <em>probably </em>base64 encoded data which outputs a ciphertext when decoded. We still don’t know what encryption algorithm could have been used or what key. Well, I mean, technically…</p><h3>Zenon on Twitter: &quot;Day 5The key to #Bitcoin smart contracts is _______Look for the final piece of the puzzle in block 709.632 to unlock the 4.745.134 $PP reward.The winner takes it all!#AlphanetBigBang $ZNN $QSR / Twitter&quot;</h3><p>Day 5The key to #Bitcoin smart contracts is _______Look for the final piece of the puzzle in block 709.632 to unlock the 4.745.134 $PP reward.The winner takes it all!#AlphanetBigBang $ZNN $QSR</p><p>this could be a 7 character key. However, this is not the first time Zenon tweets a word with underscores</p><h3>Zenon on Twitter: &quot;More dimensions, more possibilities, way more opportunities.____ is the gateway between two worlds.#AlphanetBigBang #NoM #PlasmaPoints $ZNN $QSR / Twitter&quot;</h3><p>More dimensions, more possibilities, way more opportunities.____ is the gateway between two worlds.#AlphanetBigBang #NoM #PlasmaPoints $ZNN $QSR</p><p>so I decided it was just regular Zenon slang.</p><p>No key, No algo clue. There was just one thing left to do: start playing random crypto CTF videos on YouTube and see if any inspiration could be found. Keep in mind I have 0 experience in much of what I was watching. I mean I literally installed linux like 2 months ago for the first time in my life. I am a former progamer trying to become a programmer. But the competition for the treasure hunt was on and I was highly motivated, so I kept going.</p><p>One thing became extremely obvious to me early on. No matter how hard the CTF challenge, there was always a clue for what encryption algorithm you were dealing with. Yet, we had no clue about what it could be. This YouTube binge went on until I <strong>literally </strong>run out of crypto CTF videos. This was the first time in my life I realized YouTube wasn’t infinite like the universe. Yet, here I was, out of content to watch. It was time to go read crypto CTF write ups and Crypto posts on <a href="https://crypto.stackexchange.com/">stackexchange</a>.</p><p>And then, seemingly out of nowhere, I found something that spiked my interest. I assume the alien wizardry that allowed my brain to make this connection happened during a deep sleep phase, when the subconscious goes full on Mr. Kaine on his productivity prime, trying to create neuron connections between all the new knowledge I had acquired in a short span of time. Either way, I remembered a random Crypto CTF that was dealing with what is called a OTP (One Time Pad). Apparently, this is an encryption algorithm whose security relies heavily on the encryption key or, in this case, the pad, <strong>used only once</strong>, hence the name One Time Pad. Now if we think of the first 8 words of the treasure hunt as a message, and the last 4 words as another message, we — in theory — could be dealing with a ciphertext that was encrypted using the same key, making the whole thing vulnerable.</p><p>What followed was me trying to understand as much as possible how OTPs worked and their properties. I watched several cryptography courses on chapters that specifically covered One Time Pads and how multiple implementations of the OTP were cracked abusing their properties. This video covers a few famous real world examples like wifi WEP and MS-PPTP.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fk8c0lFqvH2w%3Fstart%3D266%26feature%3Doembed%26start%3D266&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dk8c0lFqvH2w&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fk8c0lFqvH2w%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/684ffe13496f284421a2ee341030f3a6/href">https://medium.com/media/684ffe13496f284421a2ee341030f3a6/href</a></iframe><p>Here is what you need to know about <a href="https://en.wikipedia.org/wiki/One-time_pad">OTPs</a>:</p><ul><li>They were invented in 1882 and <em>re-invented?</em> and pantented in 1917 by Gilbert Vernam (Also called a Vernam Cipher).</li><li>It’s an encryption technique that <strong>cannot be cracked</strong>. This point relies on several assumptions: <br>1. The key must be random.<br>2. The key must be as long as the plaintext.<br>3. The key must never be reused in whole or in part.<br>4. The key must be kept completely secret by the communications party.</li><li>Even though it is the most secured encryption technique known to man, it is not widely adopted because of how hard it is to, in practice, establish a system where you can share multiple single-use keys. Like, if you could share a single-use key securely with another person, you might as well just tell them the message.</li></ul><p>Encrypting a message using a OTP is as simple as doing a XOR operation of the bits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/193/1*Lzcqfi_ZntZbvwqMk_cYQA.png" /><figcaption>crosshair is the XOR symbol</figcaption></figure><p>Additionally, I believe the following OTP property is the key to this whole treasure hunt thing:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/285/1*ruioH6bjSDNjEdQSgX53DA.png" /><figcaption>only valid when same key/pad is used</figcaption></figure><p>Technically speaking, if message 1 and 2 were encrypted using the same key, we could XOR together Ciphertext 1 and Ciphertext 2 and, applying a technique called crib dragging, you could guess a word in message one and then get the corresponding word at the same byte location in message 2.</p><p>The online tools I’ve found for crib dragging are not that great. Thankfully, like always, there is some open-sourced <a href="https://github.com/SpiderLabs/cribdrag">python script</a> waiting for you to put to use.</p><p>Now at this point I had been trying to crack it assuming it was a OTP with no luck, and I was about to give up, when Zenon tweeted this:</p><h3>Zenon on Twitter: &quot;Day 2Treasure hunt clue: Quantum computers can&#39;t break it.Solve the puzzle and get 4.745.134 $PP!#AlphanetBigBang $ZNN $QSR / Twitter&quot;</h3><p>Day 2Treasure hunt clue: Quantum computers can&#39;t break it.Solve the puzzle and get 4.745.134 $PP!#AlphanetBigBang $ZNN $QSR</p><p>After reading the tweet, there was no doubt in my mind, I was onto something. You see, it literally does not matter how much computing power you have, One time pads cannot be cracked. It is a fundamental property of them. The reason is that even if you try all possible keys that you get all possible plaintext and you have no method of choosing which one is right.</p><p>Enough of theory. Let’s go back to what we actually have. Based on the numbers of base64 encoded characters, there are <em>probably</em> 55 bytes of information. This is more than enough to contain 4 English words. For reference, the first 4 words of the treasure hunt (oblige dilemma hurry disorder) are 29 bytes and the mid 4 words (happy spoil shiver key) are 22 bytes.</p><p>The 55 bytes could be many different things, maybe it just the 4 missing words and a personal congratulation message by Mr. Kaine, or maybe it’s the XORed of C1 and C2, or maybe they split the words in 3 messages (each containing 4 words) and we are getting C1 ^ C2 and C2 ^ C3.</p><p>At some point I think I came to the conclusion that they couldn’t send us the key and the ciphertext at the same time.</p><p><em>To be continued…</em></p><p>P.S: There are still a few more things and even scripts I edited to (for example crib-drag the data using the BIP39 English word list) that I would like to share, but the clock is ticking and the worse-case scenario for me would be to see the hunt fail, and the solution never revealed.</p><p>I will keep adding stuff to this post later. Good night, happy hunting.</p><p><strong>BTW, </strong>I keep emphasizing <em>probably</em> when talking about the base64 encoded data because it occurred to me that Satoshi Nakomoto invented base58, which is basically base64 without confusing characters like 0 and O, I and l, etc…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c99cbef8c65" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>