<?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>Base Name Service (BNS)</title>
        <link>https://paragraph.com/@basename</link>
        <description>Web3 naming (.base) for the next billion+ users on BASE | Native Name Service</description>
        <lastBuildDate>Sat, 04 Apr 2026 00:20:50 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>Base Name Service (BNS)</title>
            <url>https://storage.googleapis.com/papyrus_images/a0ab59e05c2ecbb48e09a08a68440d77.jpg</url>
            <link>https://paragraph.com/@basename</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[A New Chapter for Onchain Identity: From BNS to Basenames]]></title>
            <link>https://paragraph.com/@basename/a-new-chapter-for-onchain-identity-from-bns-to-basenames-1</link>
            <guid>vwwMcHmoc1X3FMuadFrs</guid>
            <pubDate>Tue, 20 Aug 2024 20:59:14 GMT</pubDate>
            <description><![CDATA[Read about our journey from ETH Denver 2023, building onchain naming for the next billion+, and the exciting launch of Basenames. Discove...]]></description>
            <content:encoded><![CDATA[<p><em>Read about our journey from ETH Denver 2023, building onchain naming for the next billion+, and the exciting launch of Basenames. Discover what's next for onchain identity!</em></p><div class="relative header-and-anchor"><h3 id="h-the-genesis-eth-denver-2023">The Genesis: ETH Denver 2023</h3></div><p>In February 2023, we found ourselves at ETH Denver, surrounded by some of the brightest minds in the blockchain space. It was there, during a panel discussion led by <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://jessepollak.com/">Jesse Pollak from Coinbase</a> on “Onchain is The Next Online,” that our vision for the Base Name Service (BNS) began to crystallize. Jesse’s words resonated deeply with us—he spoke about launching Base and the potential to create an ecosystem that could bring the next billion users and a million developers onchain. It was a bold idea, but it was exactly the kind of challenge we were ready to take on.</p><div class="relative header-and-anchor"><h3 id="h-building-for-the-future-onchain-naming-for-the-next-billion">Building for the Future: Onchain Naming for the Next Billion+</h3></div><p>Inspired by that discussion, we set out to build something that would make this vision a reality. We wanted to create an onchain naming service that would serve as the foundation for this new onchain ecosystem. BNS was born from that ambition, providing an onchain identity (.base) for the next billion+ users on Base.</p><p>BNS wasn’t just about giving people an easier way to manage their crypto wallets; it was about laying the groundwork for a connected, user-friendly onchain experience. We envisioned a world where everyone—developers, creators, and everyday users—could navigate the onchain ecosystem as easily as they navigate the web today.</p><p>Over the past year, BNS has seen tremendous adoption. Thousands of users and developers across the Base ecosystem have embraced .base names, using them to establish their onchain identities and build connections within the community. It has been an incredible journey, and we are proud of what we’ve accomplished together.</p><div class="relative header-and-anchor"><h3 id="h-from-bns-to-basenames">From BNS to Basenames</h3></div><p>As the new onchain economy continues to evolve, so must we. The introduction of Basenames by the Base team marks a significant step forward in the journey we began with BNS. Basenames offers a unified, seamless onchain identity experience that builds on the foundation we laid, integrating deeply into the Base ecosystem to onboard the next billion users and million developers to onchain.</p><p>As the Base ecosystem transitions from BNS to Basenames, we do so with a sense of accomplishment and excitement for what’s to come. We’re not just winding down BNS; we’re passing the torch to a new system that will carry our vision forward. We’re proud of what we’ve built, and we’re excited to see how Basenames will take it to the next level.</p><div class="relative header-and-anchor"><h3 id="h-whats-next"><strong>What’s Next</strong></h3></div><p>We collaborated closely with the Base team to ensure our existing users receive the best possible benefits. As part of this, we've agreed to provide an exclusive discount to all our users, making it easier to secure your new “.base.eth” names for free on the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.base.org/names"><u>Basenames platform</u></a> by simply connecting the same wallets that contain your BNS names.</p><p><strong>Note:</strong> All discounts will be applied after the Dutch auction period, 36 hours after launch.</p><div class="relative header-and-anchor"><h3 id="h-gratitude"><strong>Gratitude</strong></h3></div><p>As we transition from BNS to Basenames, we want to extend our deepest thanks to everyone who supported us along the way. To our users, partners, the Base team, and supporters—thank you for believing in our vision and helping us bring it to life. Your feedback, enthusiasm, and trust have been invaluable.</p><p>To our incredible team—thank you for your dedication, creativity, and hard work. None of this would have been possible without your passion and commitment to pushing the boundaries of what’s possible in the onchain space.</p><p></p><p>Thank you for being part of our journey. We are excited to see what comes next.</p><p></p><p>Sincerely Yours,</p><p>The BNS Founders<br>Itgel Ganbold (JackJack), Sabit Bazar, and Gabit Bazar</p><p></p>]]></content:encoded>
            <author>basename@newsletter.paragraph.com (Base Name Service)</author>
            <category>web3</category>
            <category>social</category>
            <category>name service</category>
            <category>bns</category>
            <category>basenames</category>
            <category>base name service</category>
            <enclosure url="https://storage.googleapis.com/papyrus_images/c1b11278162247ed03cc4374feb81c60.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[Welcome to Paragraph!]]></title>
            <link>https://paragraph.com/@basename/welcome-to-paragraph</link>
            <guid>4b0AldLUfaGUDine42h7</guid>
            <pubDate>Tue, 05 Dec 2023 17:44:21 GMT</pubDate>
            <description><![CDATA[This post teaches you everything you need to know about getting started with Paragraph.]]></description>
            <content:encoded><![CDATA[<p>Paragraph lets you create and share beautifully crafted posts - just like this one. </p><p>Write anything - from your smallest paragraph to your grandest masterpiece - and publish it online or send it as email newsletters directly to your readers.</p><p>Your Paragraph publication is blazing-fast, SEO optimized, and combines the best parts of both web2 and web3 to help you create content and grow your community better than ever. </p><h2>Getting started</h2><p>What you&apos;re looking at right now is the Paragraph editor. We support markdown, callouts, code, and rich media embeds like Twitter and YouTube.</p><div data-type="twitter" tweetid="1560419350976221185">   <div class="twitter-embed embed">    <div class="twitter-header">        <div style="display:flex">          <a target="_blank" href="https://twitter.com/paragraph_xyz">              <img alt="User Avatar" class="twitter-avatar" src="https://pbs.twimg.com/profile_images/1521582712527548416/VaZi_24t_normal.jpg">            </a>            <div style="margin-left:4px;margin-right:auto;line-height:1.2;">              <a target="_blank" href="https://twitter.com/paragraph_xyz" class="twitter-displayname">paragraph.xyz</a>              <p><a target="_blank" href="https://twitter.com/paragraph_xyz" class="twitter-username">@paragraph_xyz</a></p>                </div>            <a href="https://twitter.com/paragraph_xyz/status/1560419350976221185" target="_blank">              <img alt="Twitter Logo" class="twitter-logo" src="https://paragraph.xyz/editor/twitter/logo.png">            </a>          </div>        </div>          <div class="twitter-body">      On <a class="twitter-content-link" href="https://t.co/BbYULfPfbU" target="_blank">paragraph.xyz</a>, all posts are stored on <a class="twitter-content-link" href="https://twitter.com/ArweaveTeam" target="_blank">@ArweaveTeam</a>. This means they&apos;re immutable, uncensorable, permanent, and composable <img class="twitter-emoji" draggable="false" alt="✨" src="https://twemoji.maxcdn.com/v/14.0.2/72x72/2728.png">                    <a class="twitter-card-link" href="https://t.co/BbYULfPfbU" target="_blank">          <div class="twitter-media twitter-summary-large-image">            <img src="https://pbs.twimg.com/card_img/1721052517503537152/c2qDlBEK?format=jpg&amp;name=800x320_1">            <div class="twitter-summary-card-text">              <span>paragraph.xyz</span>              <h2>Paragraph | all-in-one publishing &amp; newsletter platform</h2>              <p>Create, publish and share web3-native blogs &amp; newsletters.</p>            </div>          </div>        </a>           </div>         <div class="twitter-footer">          <a target="_blank" href="https://twitter.com/paragraph_xyz/status/1560419350976221185" style="margin-right:16px; display:flex;">            <img alt="Like Icon" class="twitter-heart" src="https://paragraph.xyz/editor/twitter/heart.png">            16          </a>          <a target="_blank" href="https://twitter.com/paragraph_xyz/status/1560419350976221185"><p>7:12 PM • Aug 18, 2022</p></a>        </div>      </div>   </div><p>When you publish a post, you&apos;ll have the option of sending it as a newsletter or storing it in the permanent &amp; uncensorable Arweave. </p><h2>Helpful links</h2><p>Here&apos;s a few helpful pointers to customize your publication &amp; get the most out of Paragraph:</p><ul><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://paragraph.xyz/settings/publication/theme">Theming &amp; customization</a>. Change your publication&apos;s font &amp; colors; truly make this space your own.</p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://paragraph.xyz/settings/publication/emails">Set up a welcome email</a>. This is the email your readers receive when they subscribe to your newsletter. </p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://paragraph.xyz/settings/publication/blog">Configure your publication&apos;s settings</a>. Add links to your homepage, set up a custom domain, configure Google Analytics &amp; more. </p></li></ul><h2>Need help or have feedback?</h2><p>We&apos;ve put together some documentation <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://docs.paragraph.xyz">here</a>, but if you still have questions you&apos;d like answered we’d love to hear from you. </p><p>You can reach us via email at <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="mailto:hello@paragraph.xyz">hello@paragraph.xyz</a> or subscribe to our newsletter <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://paragraph.xyz/@blog">here</a>. We&apos;re also pretty active on <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://paragraph.xyz/discord">Discord</a>. </p>]]></content:encoded>
            <author>basename@newsletter.paragraph.com (Base Name Service)</author>
            <category>tutorial</category>
            <enclosure url="https://paragraph.xyz/covers/welcome_to_paragraph_modern.png" length="0" type="image/png"/>
        </item>
    </channel>
</rss>