<?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"><channel><title><![CDATA[Akin's Blog]]></title><description><![CDATA[Akin's Blog]]></description><link>https://akindats.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Fri, 11 Sep 2026 03:05:13 GMT</lastBuildDate><atom:link href="https://akindats.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Web 5: A Dive into the Future of Decentralized Internet]]></title><description><![CDATA[https://youtu.be/J2znm4f7VUE
 
Introduction:
With each technological disruption, we, as a society, are transforming the way we work, interact, and earn. The more we shift toward the digital economy, the more we expand our potential to create usable a...]]></description><link>https://akindats.hashnode.dev/web-5-a-dive-into-the-future-of-decentralized-internet</link><guid isPermaLink="true">https://akindats.hashnode.dev/web-5-a-dive-into-the-future-of-decentralized-internet</guid><category><![CDATA[Web Development]]></category><category><![CDATA[JavaScript]]></category><category><![CDATA[React]]></category><category><![CDATA[Internet of Things]]></category><category><![CDATA[webdev]]></category><category><![CDATA[Web3]]></category><category><![CDATA[web 5.0 -The true decentralization platform]]></category><category><![CDATA[Web5 and internet]]></category><category><![CDATA[web 5.0 decentralization concept]]></category><category><![CDATA[web5]]></category><category><![CDATA[web 5.0 -The true decetralization platform]]></category><dc:creator><![CDATA[Abdulrasheed Bello]]></dc:creator><pubDate>Mon, 27 Nov 2023 14:52:09 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1701069578998/d3a8ac62-8294-453e-ac03-94a552d956af.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="embed-wrapper"><div class="embed-loading"><div class="loadingRow"></div><div class="loadingRow"></div></div><a class="embed-card" href="https://youtu.be/J2znm4f7VUE">https://youtu.be/J2znm4f7VUE</a></div>
<p> </p>
<h3 id="heading-introduction">Introduction:</h3>
<p>With each technological disruption, we, as a society, are transforming the way we work, interact, and earn. The more we shift toward the digital economy, the more we expand our potential to create usable and accessible products. The internet is undeniably one of the most significant examples of human ingenuity in the modern era. Thriving as a major disruption in and of itself, the Internet has evolved through developmental changes to reach its present version.</p>
<p>Interestingly, while we are still in the early stages of Web3 development, former Twitter CEO Jack Dorsey coined the word Web 5.0. He proposed developing an “ultra-decentralized” internet version. Though it will walk the same path as Web3, Web 5.0 will still be different from its predecessors.</p>
<p>As we ride the ever-changing waves of the internet, a new era is dawning—Web 5. It's not just a tech upgrade; it's a whole new way of thinking. Come with me as we explore the layers of Web 5 and see what it means for how we experience the online world.</p>
<p>Web 5 is like a makeover for the internet. Remember how your phone got smarter? Well, the internet is getting a digital Einstein treatment. When you're on Web 5, everything just falls into place like magic. It's not just a webpage; it's a whole new level of cool. Ready for the upgrade?</p>
<h3 id="heading-web-5-components"><strong>Web 5 Components:</strong></h3>
<p>There are three main pillars of the decentralized web platform, all of which are based on open standards.</p>
<p><img src="https://developer.tbd.website/assets/images/pillars-of-web5-6cff93b9abe64c2254673a4e32b32b61.png" alt class="image--center mx-auto" /></p>
<ol>
<li><p><strong>Decentralized Identifiers (DIDs):</strong></p>
<p> In the regular online world, others usually control our identities. With Web 5, the power is in our hands. Decentralized Identifiers (DIDs) change the game, letting us truly own and manage our online presence.</p>
<p> DIDs aren't just random characters; they follow a standard structure, giving us more control over our digital identities.</p>
<p> <img src="https://developer.tbd.website/assets/images/did-example-3cbace2fb7e64481dc63db9354c1b236.png" alt class="image--center mx-auto" /></p>
</li>
<li><ul>
<li><p>In the traditional online realm, our identities are often in the hands of others. But with Web 5, we hold the reins. Decentralized Identifiers (DIDs) are the game-changers, allowing us to truly own and control our online presence.</p>
<ul>
<li><p>A DID is more than just a string of characters; it's a standardized structure, bringing a new level of autonomy to our digital identities.</p>
</li>
<li><p>Anchoring DIDs on ION, a Layer 2 DID network riding on Bitcoin, ensures a decentralized landscape without the baggage of central authorities.</p>
</li>
<li><p>You know those online IDs you get, and they're not yours? Web 5 changes that game. Now, you get to own and control your online identity with Decentralized Identifiers (DIDs).</p>
</li>
<li><p>DID Documents, akin to digital ID cards, reside as JSON files in decentralized storage systems like IPFS. They encapsulate essential details about a DID subject, including public keys, authentication methods, and service endpoints pointing to the subject’s data locations. It's like the digital dossier for a decentralized identity!</p>
</li>
<li><pre><code class="lang-json">         {
           <span class="hljs-attr">"@context"</span>: <span class="hljs-string">"https://www.w3.org/ns/did/v1"</span>,
           <span class="hljs-attr">"id"</span>: <span class="hljs-string">"did:ion:EiClkZMDxPKqC9c-umQfTkR8"</span>,
           <span class="hljs-attr">"verificationMethod"</span>: [
             {
               <span class="hljs-attr">"id"</span>: <span class="hljs-string">"did:ion:EiClkZMDxPKqC9c-umQfTkR8"</span>,
               <span class="hljs-attr">"type"</span>: <span class="hljs-string">"Secp256k1VerificationKey2018"</span>,
               <span class="hljs-attr">"controller"</span>: <span class="hljs-string">"did:ion:EiClkZMDxPKqC9c-umQfTkR8"</span>
             }
           ],
           <span class="hljs-attr">"authentication"</span>: [<span class="hljs-string">"did:ion:EiClkZMDxPKqC9c-umQfTkR8"</span>]
         }
</code></pre>
</li>
</ul>
</li>
</ul>
</li>
<li><p><strong>Verifiable Credentials:</strong></p>
<p> In the world of Web 5, Verifiable Credentials become the trust foundation for online interactions, changing how we establish trust without blind faith. These cryptographic handshakes let us make and verify claims securely.</p>
<p> Think of it like this: your bank's cryptographically signed credentials become your trust badges in the digital realm. They vouch for you without revealing too much, like having a secure key for a trustworthy digital interaction.</p>
<p> It's a balance of privacy and security, where proving your identity is not just about who you are but also about doing it with a touch of cryptographic sophistication. It adds a layer of confidence to your online dealings, making them not just trustworthy but also well-protected.</p>
<p> For example, Alice needs to prove she has a bank account at Acme Bank. Acme Bank issues a cryptographically signed Verifiable Credential which would be stored in Alice's identity wallet.</p>
<p> <img src="https://developer.tbd.website/assets/images/acme-bank-example-899ee950d69bf65b0c7f3ee320f011c1.png" alt class="image--center mx-auto" /></p>
<ul>
<li><p>The credential contains the issuer as Acme and the subject as Alice, as well as the claims, which are Alice's account number and full name.</p>
<p>  Upon request for proof of banking, Alice presents the Verifiable Credential that's cryptographically signed by both Alice as well as her bank.</p>
<p>  This is an easy, machine-readable way to share credentials across the web. The Verifier does not know or trust Alice, but they do consider Acme trustworthy, and they have essentially vouched for Alice therefore distributing trust.</p>
</li>
<li><p>Trust is the backbone of any online interaction. Web 5 introduces Verifiable Credentials—a cryptographic handshake that allows claims to be made and verified without the need for blind trust.</p>
</li>
<li><p>Imagine proving your credentials without revealing too much. Cryptographically signed credentials, like those from a bank, become your digital badges of trust.</p>
</li>
</ul>
</li>
<li><p><strong>Decentralized Web Nodes (DWNs):</strong></p>
<ul>
<li><p>Centralized servers have long held our data hostage. Enter Decentralized Web Nodes (DWNs), empowering us to reclaim ownership. Think of it as your personal data sanctuary, independent of any single application.</p>
</li>
<li><p>BlueSky, the decentralized Twitter on the horizon, epitomizes this shift, where your tweets and connections are yours to control.</p>
</li>
<li><p>So, imagine you have these decentralized web nodes (DWNs), right? They're like your personal online hubs. Now, the cool part is they can store both stuff everyone can see, like your tweets and connections, and more private things, like DMs. Plus, these nodes aren't stuck on the blockchain—they can chill on your phone, computer, or wherever. You can even duplicate them across your gadgets and clouds, and all your data stays in sync.</p>
</li>
<li><p><img src="https://developer.tbd.website/assets/images/features-graphic-db5f265fd8a7ef7785383590eb6fa33b.png" alt class="image--center mx-auto" /></p>
<p>  So, when it comes to your DWNs, you've got options. You can be your host and keep things decentralized, but we get it—some folks prefer the ease of letting others host their web nodes. Now, here's the nifty part: even if someone else is hosting, you can still keep your private stuff private by encrypting it. Unlike the current scene where cloud hosts can snoop around, you can maintain some privacy. Oh, and your DWNs are linked to your Decentralized Identifiers and all that info is neatly listed in a DID document.</p>
</li>
</ul>
</li>
</ol>
<p>    Check out the serviceEndpoint part of the DID doc—it's like the GPS for your DWNs. It lays down the service endpoints and hands you the URIs to reach those decentralized web nodes. It's like the roadmap to where all the cool stuff is happening in your decentralized world. Nice and straightforward!</p>
<pre><code class="lang-json">    {
      <span class="hljs-attr">"@context"</span>: <span class="hljs-string">"https://www.w3.org/ns/did/v1"</span>,
      <span class="hljs-attr">"id"</span>: <span class="hljs-string">"did:web:example.com:u:alice"</span>,
      <span class="hljs-attr">"service"</span>: [
        {
          <span class="hljs-attr">"id"</span>: <span class="hljs-string">"#dwn"</span>,
          <span class="hljs-attr">"type"</span>: <span class="hljs-string">"DecentralizedWebNode"</span>,
          <span class="hljs-attr">"serviceEndpoint"</span>: {
            <span class="hljs-attr">"nodes"</span>: [<span class="hljs-string">"https://dwn.example.com"</span>, <span class="hljs-string">"00:11:22:33:FF:EE"</span>]
          }
        }
      ],
      <span class="hljs-attr">"verificationMethod"</span>: [
        {
          <span class="hljs-attr">"id"</span>: <span class="hljs-string">"did:web:example.com:u:alice"</span>,
          <span class="hljs-attr">"type"</span>: <span class="hljs-string">"Secp256k1VerificationKey2018"</span>,
          <span class="hljs-attr">"controller"</span>: <span class="hljs-string">"did:web:example.com:u:alice"</span>
        }
      ],
      <span class="hljs-attr">"authentication"</span>: [<span class="hljs-string">"did:web:example.com:u:alice"</span>]
    }


    If an app knows the address of your DWN, it can shoot over a data request. Now, check this out—it's like an app saying, <span class="hljs-string">"Hey, gimme all the stuff in your DWN that matches the SocialMediaPosting schema."</span> It's like ordering exactly what you're in the mood for.

    ```json
        POST https:<span class="hljs-comment">//dwn.example.com/</span>
        BODY {
          <span class="hljs-attr">"requestId"</span>: <span class="hljs-string">"c5784162-84af-4aab-aff5-f1f8438dfc3d"</span>,
          <span class="hljs-attr">"target"</span>: <span class="hljs-string">"did:example:123"</span>,
          <span class="hljs-attr">"messages"</span>: [
            {
              <span class="hljs-attr">"descriptor"</span>: {
                <span class="hljs-attr">"method"</span>: <span class="hljs-string">"CollectionsQuery"</span>,
                <span class="hljs-attr">"schema"</span>: <span class="hljs-string">"https://schema.org/SocialMediaPosting"</span>
              }
            },
            {...}
          ]
        }
</code></pre>
<p>    The cool thing is, that the data inside your DWNs follows a universal standard—it's all in JSON objects. So, any app can easily figure out and handle the data based on its semantic type. Now, here's the deal: if the data's out there for everyone to see, the app gets it automatically.</p>
<p>    But if it's on the down-low, the owner of the node has to give the green light for the app to access that private data. It's like having a bouncer for your digital VIP section!</p>
<p>    In a nutshell, your DWNs are like personal hubs in the decentralized web. They can hold both public and private data, and you have the flexibility to host them yourself or let others do it for convenience. The serviceEndpoint in the DID doc acts like a GPS for your DWNs, guiding applications to where the action is.</p>
<p>    Thanks to a universal standard in JSON objects, any app can understand and process the data based on its type. Public data is fair game for any app, but for the private stuff, it's all about getting the owner's nod. It's like your own little corner of the digital universe with control in your hands!</p>
<p>In the ever-evolving landscape of the internet, Web 5 emerges as a transformative force, reshaping the way we navigate the digital realm. It's not merely a technological upgrade; it represents a paradigm shift in our approach to online interactions.</p>
<p>Web 5 introduces a trio of groundbreaking components, each based on open standards, paving the way for a more user-centric and decentralized internet experience. Decentralized Identifiers (DIDs) grant individuals unprecedented control over their online identities, breaking away from the traditional reliance on external entities.</p>
<p>Verifiable Credentials become the bedrock of trust in Web 5, offering a cryptographic framework for secure and privacy-conscious online interactions. It's a delicate balance between privacy and security, where credentials act as digital trust badges, vouching for individuals without compromising sensitive information.</p>
<p>Decentralized Web Nodes (DWNs) empower users to reclaim ownership of their data, transcending the limitations of centralized servers. Whether hosted independently or by third parties, these nodes offer a seamless and synchronized experience, where public and private data coexist under the user's jurisdiction.</p>
<p>Web 5 is not just an upgrade; it's a holistic makeover for the internet. It's like the digital Einstein treatment, where everything seamlessly falls into place. The components of Web 5, driven by open standards, herald a new era where users wield greater autonomy and control in the online landscape.</p>
<p>As we embark on this journey into Web 5, we witness a convergence of technology and philosophy. It's not just about accessing webpages; it's about a fundamental shift in how we perceive and engage with the online world. Web 5 invites us to explore these layers of innovation, ushering in a future where our digital experiences are truly in our hands. So, are you ready for the upgrade?</p>
<p>How about diving into the practical aspects of Web 5? You can explore real-world applications and use cases that demonstrate how these components—Decentralized Identifiers, Verifiable Credentials, and Decentralized Web Nodes—work together to reshape our digital experience. It could be enlightening to see how these concepts play out in specific industries or scenarios.</p>
<p>Additionally, considering the evolving nature of technology, staying updated on the latest developments in Web 5 could be a fascinating journey. Whether it's emerging technologies, innovative projects, or influential voices in the space, keeping a pulse on the dynamic landscape of Web 5 can provide valuable insights.</p>
<p>And of course, don't hesitate to share your thoughts or questions about Web 5. Engaging in discussions, forums, or even creating content about your perspectives on the future of the internet could be a great way to contribute to the ongoing dialogue around this transformative concept.</p>
]]></content:encoded></item></channel></rss>