<?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>Calvin S. Drapeau</title>
        <link>https://paragraph.com/@calvin-s-drapeau</link>
        <description>undefined</description>
        <lastBuildDate>Sun, 17 May 2026 21:00:40 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[Mint Issues — A Resolution]]></title>
            <link>https://paragraph.com/@calvin-s-drapeau/mint-issues-a-resolution</link>
            <guid>8ja8O8P90T1KGJc5t9hc</guid>
            <pubDate>Wed, 30 Mar 2022 05:39:42 GMT</pubDate>
            <description><![CDATA[We heard you. Here’s what’s next…Greetings… First of all, we’d like to thank all of you for joining in the mammoth effort to save so many Seekers yesterday.We know that some of you experienced issues with the mint and we’d like to take the time today to dive into what happened and how we can provide a remedy. One thing will always remain the same — our strength is in our community. We appreciate each and every one of you, and your contributions as a whole. We want to do right by those affecte...]]></description>
            <content:encoded><![CDATA[<h2 id="h-we-heard-you-heres-whats-next" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><strong><em>We heard you. Here’s what’s next…</em></strong></h2><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/948264ab96391a986e277e9163dab417815a3070769dea7b9d51cb3d2eddcd93.jpg" 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>Greetings…</p><p>First of all, we’d like to thank all of you for joining in the mammoth effort to save so many Seekers yesterday.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/722dde83aae0ff089465b439c2f140d8df3f021233ac3d7b8ec67aaa2d690f81.jpg" 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>We know that some of you experienced issues with the mint and we’d like to take the time today to dive into what happened and how we can provide a remedy.</p><p>One thing will always remain the same — <strong>our strength is in our community</strong>. We appreciate each and every one of you, and your contributions as a whole.</p><p>We want to do right by those affected, so we can charge ahead together as we continue to build the foundations for the open metaverse.</p><p>We now know that the issue that occurred during mint affected a subset of addresses in the Sylo Liquidity Program Whitelist, and a subset of addresses in the SYLO Token Holder Whitelist. Node Runners who were affected by the issue in either of those whitelists, were also affected in that they could not mint their free beacon.</p><h2 id="h-heres-how-were-putting-that-right" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><strong>Here’s how we’re putting that right:</strong></h2><h2 id="h-for-whitelisted-sylo-node-operators" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><strong>For Whitelisted Sylo Node operators</strong></h2><p>If you went through the pre-mint process to <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://medium.com/sylo-io/claim-your-seeker-d7782ddc3c5e">‘claim your Seeker’</a>, you will be airdropped a Beacon before they begin to reveal. This will be sent to your whitelisted wallet address, there is nothing more you need to do.</p><h2 id="h-for-whitelisted-sylo-liquidity-mining-participants" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><strong>For Whitelisted Sylo Liquidity Mining participants</strong></h2><p>If you tried to mint your free beacon but it failed, you will be airdropped a Beacon before they begin to reveal. This will be sent to your whitelisted wallet address, there is nothing more you need to do.</p><h2 id="h-for-whitelist-discount-holders-for-the-sylo-token" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><strong>For Whitelist discount holders for the SYLO Token</strong></h2><p>This error meant that people either had to purchase from another wallet (at full price), or were able to purchase, but the discount wasn’t applied. Therefore in response, all whitelisted SYLO holders who attempted to mint their Seekers will be airdropped the discount that they should have received. This will be sent to your whitelisted wallet address, there is nothing more you need to do.</p><p>[Please note — there will be no change in supply — we can’t get them back from the Goblins!]</p><p><strong>Thank you again for your ongoing support.</strong></p>]]></content:encoded>
            <author>calvin-s-drapeau@newsletter.paragraph.com (Calvin S. Drapeau)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/57d23387e8928e4933fc6109e2d4613a3a56b88b7bbdd5b2f8dc27914b5cce39.jpg" length="0" type="image/jpg"/>
        </item>
    </channel>
</rss>