<?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>Pengu #1</title>
        <link>https://paragraph.com/@pengone</link>
        <description>Pudgy Penguin #1</description>
        <lastBuildDate>Sun, 26 Apr 2026 20:14:11 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>Pengu #1</title>
            <url>https://storage.googleapis.com/papyrus_images/ca6664d73c299bb73d5d67dc822e92c053276411b422f78369c74457ff156e5c.png</url>
            <link>https://paragraph.com/@pengone</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Inscribing digital artifacts on Bitcoin & the Penguin Preservation Program]]></title>
            <link>https://paragraph.com/@pengone/inscribing-digital-artifacts-on-bitcoin-the-penguin-preservation-program</link>
            <guid>Vs9DuQoAgICxnOX7HZ4j</guid>
            <pubDate>Fri, 10 Feb 2023 13:49:30 GMT</pubDate>
            <description><![CDATA[Digital Artifact PreservationWith the advent of Ordinals on Bitcoin, it’s now possible to permanently store any “arbitrary” files on Bitcoin. The best use case that comes to mind immediately is penguin pictures on the blockchain. Pudgy Penguins’ (or [insert your NFT here]’s) metadata is locked on IPFS and won’t be moving anytime soon. But what does “soon” mean? 1 year—5 years—20 years? I don’t know about you, but if there’s a nuclear Armageddon, I want my penguin to still be around. And given...]]></description>
            <content:encoded><![CDATA[<h2 id="h-digital-artifact-preservation" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Digital Artifact Preservation</h2><p>With the advent of Ordinals on Bitcoin, it’s now possible to <strong><em>permanently</em></strong> store any “arbitrary” files on Bitcoin.</p><p>The best use case that comes to mind immediately is <em>penguin pictures on the blockchain.</em></p><p><strong>Pudgy Penguins’</strong> (or [insert your NFT here]’s) <strong>metadata is locked on IPFS and won’t be moving anytime soon.</strong></p><p>But what does “soon” mean? 1 year—5 years—20 years? <strong><em>I don’t know about you, but if there’s a nuclear Armageddon, I want my penguin to still be around.</em></strong></p><p>And given that there are tens of thousands of nodes, in various attics, basements and bunkers, spread all across the world and updating separately with every block appended to the blockchain…Bitcoin’s chain seems like the prime candidate to be able to service that possibility.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/b3a8964c67583bcb33968f94fca0eeb57e36a89ded348452d080c95c4bf6ae4d.png" alt="There will be 13,000+ separate nodes backing up every Bitcoin transaction." blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">There will be 13,000+ separate nodes backing up every Bitcoin transaction.</figcaption></figure><h2 id="h-introducing-ordinals" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Introducing Ordinals</h2><p>The Ordinals protocol built on Bitcoin taproot, to put it bluntly, allows you to store NFT-like instances on Bitcoin.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/7cf7fb8b732d61dc0785c52efbc793dc8ef2c51b9e9466a683823889268d6c6a.png" alt="Given the amount of trash being put on the chain, I don&apos;t expect this craze to last, or the &quot;NFTs&quot; to be worth anything. Hence, in my opinion, using the chain as a permanent storage solution while it lasts, is the smartest thing to do." blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Given the amount of trash being put on the chain, I don&apos;t expect this craze to last, or the &quot;NFTs&quot; to be worth anything. Hence, in my opinion, using the chain as a permanent storage solution while it lasts, is the smartest thing to do.</figcaption></figure><p>People are uploading low resolution highly compressed files of their Etherrocks, Apes, Doodles and Punks because it’s far cheaper than uncompressed. But then, what’s the point of backing up a subpar jpeg? <strong>Remember, BTC sucks for high throughput and scalability, and is great for permanence.</strong> If you’re going to use a premium chain, might as well use a premium jpeg, or else you are best off using IPFS, Arweave or even <em>shudders</em> BSV, all of which are significantly cheaper by a factor of 100 times.</p><h2 id="h-the-penguin-preservation-program" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">The Penguin Preservation Program</h2><p>Penguin #1—me—is offering a service for all penguins and later other NFTs, to get inscribed into the Bitcoin network.</p><p>I’ve done the hard work of setting up a node, syncing the 700GB blockchain and indexing every transaction—which takes &gt;96 hours and costs money by the second, by the way—so you don’t have to.</p><p>Not only that, I’ve optimized the best way to compress files without losing quality, so you can get a high quality version of your NFT on the chain without breaking the bank too much.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/ddb82f50a8c2e5c1a7d8aba4e12f118feb606b660620c31f7f248c04c66fefba.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>Notice how this is one of the only times in history where the mempool is clogged without the price moving fast. <strong><em>Hot take: I estimate that the BTC jpeg inscription is unlikely to continue for a long time</em></strong>* as the Bitcoin block space is extremely limited, so either the network’s developers will fork it off, or it will become <strong>prohibitively expensive to append to the blockchain.</strong> This is why I put my own penguin on the blockchain, as it could give it extra value by being there…before they make it impossible to do so.*</p><p>So, I’m offering this service for all penguins.</p><p>Penguins and other NFTs will be able to be added to Bitcoin’s blockchain at a cost of 0.1 ETH per penguin ID. <em>(This is subject to change according to how BTC network fees act.)</em></p><p>The payment? It goes directly to pay for the inscription, and infrastructure costs. There is no <em>profit</em> made from this initiative.</p><p><strong>All excess <em>“profits”</em> go to </strong><code>thePPP.eth</code><strong>, an <em>EOA and possibly later multisig</em>, used exclusively for the advancement of future penguin endeavors.</strong></p><p>Therefore, by participating, you’re putting your penguin on chain forever, and “donating” to a common fund to be used to benefit penguins in important community initiatives.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/435823e44f7c32ecbe3d17b45ba0bc37d480134e7eef8e79f4c99877c2d71a88.png" alt="@ASvanevik&apos;s penguin has been inscribed onchain on Bitcoin forever at the hash: 0ec4cb2c7991db446c47223556455c7e826721ea51326170c0482328379fa1c5i0.  " blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">@ASvanevik&apos;s penguin has been inscribed onchain on Bitcoin forever at the hash: 0ec4cb2c7991db446c47223556455c7e826721ea51326170c0482328379fa1c5i0.</figcaption></figure><p><strong>To summarize:</strong></p><ul><li><p>You are getting your NFT picture inscribed on Bitcoin.</p></li><li><p>This is not a spendable NFT, simply an inscription.</p></li><li><p>The inscription will last as long as the Bitcoin blockchain is alive.</p></li><li><p>There is a strong possibility that it will not be possible to inscribe in the future, hence why there is a rush now.</p></li><li><p><em>Speculative: If your penguin is saved on the Bitcoin blockchain, that adds extra value to the permanence of it. (Think: What if the BTC network gets overloaded with new NFT users and it starts to cost thousands of dollars to inscribe your penguin?)</em></p></li><li><p>All the money raised by this initiative goes only to cover operational costs, “profits” go to <code>thePPP.eth</code> which is a wallet run by #1 and is pledged to be used exclusively for penguin related endeavors.</p></li></ul><p><strong>The only things you’ll need:</strong></p><ul><li><p>Your penguin (or other collection) ID.</p></li><li><p>An Ethereum address, to send payment.</p></li></ul><p><strong>Deals:</strong></p><ul><li><p>First penguin 0.1 ETH, second penguin 0.08 ETH, each penguin from there on 0.06 ETH.</p></li></ul><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/NumberOnePengu"><strong>Send a DM on Twitter to get inscribed.</strong></a><strong> Solidify your NFT on the blockchain forever.</strong></p><p>If there is significant demand, I will create a front-end application so we do not have to deal through DMs!</p><p>Any funds collected from this article also go to <code>thePPP.eth</code>.</p>]]></content:encoded>
            <author>pengone@newsletter.paragraph.com (Pengu #1)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/02cf2878d377de63128fc1e4ab47a2c3e0577c34b96182cb7101a271d89929ea.png" length="0" type="image/png"/>
        </item>
    </channel>
</rss>