<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>dubdee</title>
        <link>https://paragraph.com/@dubdee</link>
        <description>undefined</description>
        <lastBuildDate>Mon, 20 Apr 2026 15:52:54 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[The Mystery of the Meebits Tattoos: Part I]]></title>
            <link>https://paragraph.com/@dubdee/the-mystery-of-the-meebits-tattoos-part-i</link>
            <guid>OWNQ9ww4OP4X3AEEMm3X</guid>
            <pubDate>Mon, 28 Mar 2022 18:33:45 GMT</pubDate>
            <description><![CDATA[Something is suspicious with the Meebits tattoo attributes, and it could be a clue in a treasure hunt. Instead of hoarding what I’ve learned, I’m publishing what I know while I continue working through the puzzle before it’s solved (at least as far as I know). If you start solving too and want to work together, please reach out!This Meetbit’s tattoo attribute is strangely expressed as “LLFBDBBDBFLL,LLFBDBBDBFLL”History: Not the First Treasure HuntLarva Labs recently released their Protoglyph ...]]></description>
            <content:encoded><![CDATA[<p>Something is suspicious with the Meebits tattoo attributes, and it could be a clue in a treasure hunt. Instead of hoarding what I’ve learned, I’m publishing what I know while I continue working through the puzzle before it’s solved (at least as far as I know). If you start solving too and want to work together, please reach out!</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/ad16fdc1be3850b688bcef28cc434d1d3e109dd4de695adb3019f033f5e62462.png" alt="This Meetbit’s tattoo attribute is strangely expressed as “LLFBDBBDBFLL,LLFBDBBDBFLL”" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">This Meetbit’s tattoo attribute is strangely expressed as “LLFBDBBDBFLL,LLFBDBBDBFLL”</figcaption></figure><h2 id="h-history-not-the-first-treasure-hunt" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">History: Not the First Treasure Hunt</h2><p>Larva Labs recently released their <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://collective.proof.xyz/grails/11">Protoglyph</a> as part of the first Proof Collective Grails event. Hidden at the very top was a row of alternating “L” characters, which seemed to be separate from the generative part of the work. A clever codebreaker noticed this, and ended up decoding the message to read “The secret is in the pig numbers, LL” (read the Twitter thread <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/andrewbadr/status/1503436760239464449?s=20&amp;t=0L3osoYr2oCffWATor0AgQ">here</a>, or listen to the interview <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.proof.xyz/proof-grails-protoglyph-and-the-secret-of-the-pig-numbers-treasure-hunt/">here</a>). Following this clue eventually led the hunters to the private key for a secret wallet containing a Meebit. Treasure hunted ✅.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/d92a5423158a6f7201bab7121cdbe721aa74be605810b0689ae33ba252c8cfd8.png" alt="The top row of the Protoglyph held a hidden clue in the &quot;L&quot; characters." blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">The top row of the Protoglyph held a hidden clue in the &quot;L&quot; characters.</figcaption></figure><p>The story was fun to read, but it also begged the question: could this be the only treasure hunt Larva Labs hid among the Meebits? Kevin Rose hinted recently that he thinks there might be more, and mentioned how strange the tattoo attributes are on the Meebits. That was enough of a spark to make me want to dive in!</p><h2 id="h-understanding-the-tattoo-attribute" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Understanding the Tattoo Attribute</h2><p>The tattoo attributes are indeed suspicious, especially because it seems like there would be far simpler ways to express the tattoos. It’s not that complex, though, once you break it down.</p><p>Each tattoo is on a square grid of either 3 or 4 units across. The height of the tattoo is determined by the number of letters, one for each row. Each row is comprised of one of six patterns, as illustrated here:</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/2fab32e92a3f95576906e3fe6dc4d466aa8600fb0eb3533b0266a0f78949e369.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>You’ll never see a 4-across character mixed with a 3-across character in a tattoo, the columns above are always distinct. Also, if a Meebit has only one tattoo string (like <code>GTZG</code>), it has a single tattoo on its right arm. If it has two strings (like <code>SBLF,SBLF</code>), the tattoo is on both arms and both tattoos are always exactly the same.</p><p>Of course, you can’t look at that graphic and not think about the tattoo patterns translating to <code>1</code>s and <code>0</code>s, especially after that’s how the “L” clue started the Protoglyph hunt. So here’s that:</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/05264ed3c2b1468ea5c632777caacb4855e5dbfa30a9139207369eadc84e50a5.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>There are many questions outstanding, like why are these particular letters chosen to represent these combinations? But let’s pocket this information for now and move on to the next piece, which seems to confirm there is indeed a treasure hunt here.</p><h2 id="h-the-normal-factor-semidirect-product" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">The Normal Factor Semidirect Product</h2><p>If you start browsing or parsing the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://meebits.larvalabs.com/meebits/attributelist?category=Tattoo">Tattoo attribute page on the Meebits site</a>, you might notice something strange. There are four <em>phantom</em> tattoo properties that do not conform to the above pattern, and don’t even seem to exist. Instead of using letters, the properties use <code>⋉</code> and <code>⋊</code> (the unicode names for these are the <em>Left</em> and <em>Right Normal Factor Semidirect Product</em> characters).</p><p>Four of these properties are nestled among the other tattoo properties on the page, but unlike every other link on this page, they lead to 0 search results. The four strange tattoo attributes look like this:</p><pre data-type="codeBlock" text="⋉⋊⋉⋊⋉⋊⋊⋉⋉⋊⋉⋉,⋉⋊⋉⋊⋉⋊⋊⋉⋉⋊⋉⋉
⋉⋊⋉⋉⋊⋊⋉⋉⋉⋊⋉⋉,⋉⋊⋉⋉⋊⋊⋉⋉⋉⋊⋉⋉
⋉⋉⋉⋊⋉⋊⋉⋊⋉⋉⋊⋉,⋉⋉⋉⋊⋉⋊⋉⋊⋉⋉⋊⋉
⋉⋉⋉⋊⋉⋊⋉⋉⋊⋊⋉⋉,⋉⋉⋉⋊⋉⋊⋉⋉⋊⋊⋉⋉
"><code></code></pre><p>That looks a lot like the beginning of the “Pig Numbers” clue, with these left and right characters as <code>0</code>s and <code>1</code>s.</p><p>Indeed, if you take just the first sequence in each set (I discarded the second because it mirrors the first), and try every possible combination of ordering these, then convert ⋉ to 0 and ⋊ to 1, <em>one</em> of the sets will look like this:</p><pre data-type="codeBlock" text="010011000100000101010010010101100100000101001100
"><code></code></pre><p>Each set was originally 12 characters for a total of 48. To convert to text, we’ll put a break in between each set of 8 numbers and see what’s revealed: </p><pre data-type="codeBlock" text="01001100 = L
01000001 = A
01010010 = R
01010110 = V
01000001 = A
01001100 = L
"><code><span class="hljs-attr">01001100</span> = L
<span class="hljs-attr">01000001</span> = A
<span class="hljs-attr">01010010</span> = R
<span class="hljs-attr">01010110</span> = V
<span class="hljs-attr">01000001</span> = A
<span class="hljs-attr">01001100</span> = L
</code></pre><p>Decoding <code>LARVAL</code> (<strong>Larva L</strong>abs) seems to confirm we’re on a path here. How might this lead to a treasure? Does the encoding method of tattoos have anything to do with this mystery? Surely the order of the <code>⋉⋊⋉⋊⋉⋊⋊⋉⋉⋊⋉⋉,⋉⋊⋉⋊⋉⋊⋊⋉⋉⋊⋉⋉</code> tattoos has something to do with the solution, as does their choice to use this particular obscure symbol. Or does it?</p><p>Stay tuned for Part 2 by following <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/dubdee_nft">dubdee</a> on Twitter.</p>]]></content:encoded>
            <author>dubdee@newsletter.paragraph.com (dubdee)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/9e901928a218ff108c8c591fd9ad712013412df30cff7884527da5babd858c20.png" length="0" type="image/png"/>
        </item>
    </channel>
</rss>