<?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" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Glorysunday on Medium]]></title>
        <description><![CDATA[Stories by Glorysunday on Medium]]></description>
        <link>https://medium.com/@glorysunday629?source=rss-fa0f7483919c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*PUzlS8yN18kzrFwRxC6WGw.jpeg</url>
            <title>Stories by Glorysunday on Medium</title>
            <link>https://medium.com/@glorysunday629?source=rss-fa0f7483919c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:54:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@glorysunday629/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[BUDGET KIT: HOW POCKET IS CHANGING THE WAY USERS ACCESS RPC SERVICES.]]></title>
            <link>https://medium.com/@glorysunday629/budget-kit-how-pocket-is-changing-the-way-users-access-rpc-services-a90aa4925e02?source=rss-fa0f7483919c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a90aa4925e02</guid>
            <dc:creator><![CDATA[Glorysunday]]></dc:creator>
            <pubDate>Wed, 18 Nov 2026 10:07:57 GMT</pubDate>
            <atom:updated>2026-11-18T10:07:57.598Z</atom:updated>
            <content:encoded><![CDATA[<p>INTRODUCTION:<br>Providing access to network infrastructure is important, but keeping that infrastructure sustainable also requires a way to support its costs.</p><p>During the November 11 Pocket Network Ecosystem Office Hours, the team shared an update on Budget Kit, a wallet-based system designed to help users purchase network throughput using USDC or POKT.</p><p>The development introduces a more structured approach to RPC access, allowing regular users and applications with higher demands to access services differently.</p><p>1. WHAT IS BUDGET KIT?<br>Budget Kit is a wallet-based payment system developed by Pocket Network. Jorge confirmed during the meeting that its primary development had been completed.</p><p>Instead of depending on traditional email-based accounts, users will be able to connect their wallets and pay for network throughput using USDC or POKT.</p><p>The goal is to make accessing Pocket’s infrastructure more flexible while creating a payment model that supports network costs.</p><p>2. WHAT IS CHANGING?<br>Pocket is introducing three planned access levels:</p><p><strong>Free Public RPC:</strong> Users can continue accessing public RPC, but with stricter rate limits.</p><p><strong>Wallet-Connected Access:</strong> Connecting a wallet provides a more generous free usage allowance.</p><p><strong>Premium Access:</strong> Users who need additional throughput can purchase network capacity.</p><p>Another important change is that WebSocket access will become part of the premium offering.<br>This creates a clearer difference between regular access and services that require higher-volume usage.</p><p><strong>HOW DOES THIS MATTER TO DEVELOPERS AND USERS?</strong><br>The changes give users more control over how they access Pocket’s infrastructure.</p><p>Regular users can continue using free public RPC, while developers running applications that require more throughput will have a paid option.</p><p>It also means that applications consuming more network resources have a way to contribute towards the cost of providing those services.</p><p>This helps Pocket balance accessibility with the resources needed to maintain its infrastructure.</p><p><strong>4. WHY DOES PAYING WITH POKT MATTER?</strong><br>The team also discussed incentives for users who choose to pay with POKT instead of USDC.</p><p>A 20% discount was discussed, with a possible introductory increase to around 50%. However, the final figures are yet to be confirmed.</p><p>More importantly, USDC collected through the public RPC portal is intended to be converted into POKT to replenish application stakes.</p><p>This creates a connection between actual network usage and demand for POKT.</p><p>As more users adopt paid access, this model could help strengthen Pocket’s network economics. However, the actual impact will depend on adoption.</p><p><strong>CONCLUSION:</strong><br>Budget Kit is more than a new payment option. It represents Pocket’s effort to create a better balance between free access and sustainable infrastructure.</p><p>By introducing wallet-based payments, different access levels and premium throughput, Pocket is working towards a system where users can access services according to their needs while contributing to the resources they consume.</p><p><strong>The important change is simple:</strong> Pocket wants to keep RPC accessible while giving high-volume users a clear way to pay for the infrastructure they depend on.</p><p><strong>OFFICE HOURS REFERENCE &amp; SOURCES:</strong><br><strong>Primary source:</strong> November 11 Pocket Network Ecosystem Office Hours.</p><p><strong>Full recording:</strong> https://youtu.be/VmznTpJRg9M⁠�</p><p><strong>Supporting resource:</strong> Official Pocket Network Documentation⁠�</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a90aa4925e02" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OPPORTUNITY BRIEF: MAKING SMART CONTRACT EVENTS EASIER TO USE.]]></title>
            <link>https://medium.com/@glorysunday629/opportunity-brief-making-smart-contract-events-easier-to-use-e8be2ce56271?source=rss-fa0f7483919c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8be2ce56271</guid>
            <dc:creator><![CDATA[Glorysunday]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 16:10:28 GMT</pubDate>
            <atom:updated>2026-11-16T16:12:14.050Z</atom:updated>
            <content:encoded><![CDATA[<p>INTRODUCTION.<br>When someone sends tokens or interacts with a smart contract, the blockchain records what happened through event logs. Developers need this information to track transactions, monitor token transfers and build applications that respond to blockchain activities.<br>But how can developers easily understand and use these records? This is where Pocket Network’s Event Log Decoding service becomes useful.</p><p>1. THE ACTUAL DEVELOPER NEED.<br>DECODING SMART CONTRACT EVENT LOGS.<br>Developers need to extract meaningful information from blockchain event logs. These logs contain technical data that applications must interpret before using it.</p><p>Ethereum’s documentation explains that developers use events to track contract activity, debug applications and build analytics.<br>SOURCE 1: Ethereum – Logging Data from Smart Contracts⁠�</p><p>Etherscan also explains how external applications use event logs to track token transfers, decentralised exchange activity and other blockchain events.<br>SOURCE 2: Etherscan – Understanding Event Logs⁠�</p><p>2. THE EXISTING POCKET SERVICE.<br>Pocket already provides an EVENT LOG DECODING SERVICE in its service directory.<br>It decodes ERC-20 and ERC-721 transfer events from an EVM transaction, returning information such as the sender, receiver and transferred amount.<br>Resource: Pocket Event Log Decoding Service⁠�</p><p>3. HOW POCKET MEETS THIS NEED.<br>Consider a developer building a wallet application that displays token transfers.<br>The developer can submit a transaction hash and chain ID to Pocket’s Event Log Decoding service. Pocket returns decoded transfer information, making it easier for the application to identify who sent the tokens, who received them and the amount transferred.<br>This saves the developer from having to implement that decoding process for supported transfer events.</p><p>CONCLUSION.<br>Developers need understandable blockchain event data to build applications that track and respond to on-chain activities.<br>Ethereum and Etherscan document this practical requirement, while Pocket already provides a service that addresses it.<br>Pocket makes complex smart contract event data easier for developers to use.</p><p>RESEARCH SOURCES:<br>Ethereum Documentation⁠�<br>Etherscan Documentation⁠�</p><p>POCKET RESOURCE:<br>Event Log Decoding Service⁠�</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8be2ce56271" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[YOUR API CAN BECOME A SERVICE ON POCKET NETWORK: A PRACTICAL OPPORTUNITY FOR DEVELOPERS.]]></title>
            <link>https://medium.com/@glorysunday629/your-api-can-become-a-service-on-pocket-network-a-practical-opportunity-for-developers-92225f9aca40?source=rss-fa0f7483919c------2</link>
            <guid isPermaLink="false">https://medium.com/p/92225f9aca40</guid>
            <dc:creator><![CDATA[Glorysunday]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 17:28:52 GMT</pubDate>
            <atom:updated>2026-11-11T17:37:45.473Z</atom:updated>
            <content:encoded><![CDATA[<h3>INTRODUCTION<br>An API does not have to serve only the application that created it. It can become a service that other applications discover and use. Pocket Network provides an open network where developers register services, Suppliers provide infrastructure, and applications pay to access them.</h3><p>1. WHAT CAN BECOME A POCKET SERVICE?<br>Pocket supports more than blockchain RPC. Its documentation describes services such as blockchain data, LLM inference, embeddings, data aggregation and other API-based capabilities.<br>For example, a developer could create a currency conversion API. A budgeting application could use it to retrieve exchange-rate information. Another developer might offer a document tool that extracts text from reports.</p><p>2. HOW DOES A DEVELOPER REGISTER A SERVICE?<br>A developer registers a service on Pocket, creating an on-chain record with a unique service ID. The developer gives it a name and sets its request price in compute units.<br>A service metadata card explains what the API does, the requests it accepts, the responses it returns and what a Supplier needs to operate it. This helps users and infrastructure providers understand the service.<br>Registration does not automatically make an API available. The service still needs a Supplier to provide the infrastructure that handles requests.</p><p>3. WHY ARE SUPPLIERS IMPORTANT?<br>Suppliers are operators that provide infrastructure for Pocket services. They stake on services and run the required backend and RelayMiner, which connects their infrastructure to Pocket.<br>Imagine a developer registers a weather API. A Supplier configures it. When an application requests the weather in a city, a Gateway routes the request to an eligible Supplier. The Supplier processes it and returns a response.</p><p>4. HOW DO APPLICATIONS ACCESS SERVICES?<br>Applications access Pocket services through Gateways. A Gateway receives a request and routes it to Suppliers serving the requested service. This gives application developers a way to access services without managing a separate connection to every Supplier.</p><p>5. HOW CAN SERVICE OWNERS BENEFIT?<br>Applications pay for service usage, while Suppliers earn for providing infrastructure and serving requests. Pocket uses claims and proofs to account for completed work as part of its settlement process.<br>Service owners can receive a share of settled usage under the protocol’s revenue-sharing arrangements. A developer may benefit when applications use their service, even if another Supplier operates the infrastructure.</p><p>6. WHY DOES THIS MATTER FOR AI DEVELOPERS?<br>AI agents often need information and tools beyond the language model itself. An agent might need research, financial information or document analysis to complete a task.<br>Pocket’s Agentic Portal provides a catalogue of services that agents, MCP clients and applications can discover and access. For example, an agent preparing a company summary could use a research service, retrieve financial information and call a document tool to extract details from a report.<br>Not every registered service automatically appears in the portal; it must meet listing and technical requirements. Usage and income are not guaranteed.</p><p>CONCLUSION<br>Pocket Network gives developers a way to bring APIs into an open service ecosystem. Developers register services and describe them for users and Suppliers. Suppliers provide infrastructure, Gateways route requests, and applications or AI agents access the services.<br>The opportunity extends beyond blockchain RPC to data, research, document and AI-related tools. Pocket does not promise automatic traffic or income, and registration alone does not make a service operational. However, it creates a framework where service creators, infrastructure operators and application builders can contribute value.<br>A developer’s API does not have to remain an isolated tool. With Pocket Network, it can become part of a wider service marketplace.</p><p>SOURCES:</p><ul><li><a href="https://docs.pocket.network/services/">Services</a></li><li><a href="https://docs.pocket.network/services/register/">Register a Service</a></li><li><a href="https://docs.pocket.network/services/deploy/">Deploy a Service</a></li><li><a href="https://docs.pocket.network/agent-services/">Agent Services</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92225f9aca40" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Practicality Over Promises: Last Call to Represent ROZOai]]></title>
            <link>https://medium.com/@glorysunday629/practicality-over-promises-last-call-to-represent-rozoai-a73c90a53473?source=rss-fa0f7483919c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a73c90a53473</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[crypto-project]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Glorysunday]]></dc:creator>
            <pubDate>Mon, 05 Jan 2026 16:11:55 GMT</pubDate>
            <atom:updated>2026-01-05T16:11:55.113Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*33CzDZyYnsWqf5Bo1bwYTA.jpeg" /></figure><p>Most crypto projects spend money to hype up something that isn’t real yet. ROZOai does things differently. ROZOai isn’t looking for people who just retweet; ROZOai wants people who understand what ROZOai is building.</p><h3>What problem ROZOai solves</h3><p>Right now, paying with stablecoins is a headache. Different blockchains mean different systems, and a payment can fail if you’re on different chains than the merchant. ROZOai is like a “Visa for stablecoins.” Visa lets you pay without worrying about the bank; ROZOai connects stablecoins across networks. ROZOai uses “Intents.” Tell ROZOai what you want to pay, and the tech does the tricky cross-chain work behind the scenes. The goal is to make the tech invisible so everyday users don’t have to think about it.</p><h3>The Warm-Up event today</h3><p>Deadline: Today, January 5, 2026.<br>ROZOai is giving away 10–100 USDC to Stellar addresses. To qualify, do any two of these four things:<br>1. Social: Share about ROZOai on X.<br>Community: Participate in ROZOai Discord groups.<br>2. Product: Use ROZOai Intents or refer someone who does.<br>3. Content: Share a thoughtful post on Reddit or similar sites.<br>4. Important: This isn’t low-effort spam. A thoughtful Reddit guide can earn more than dozens of casual posts.</p><h3>The longer-term plan</h3><p>ROZOai OG status<br>The warm-up ends today, but the journey continues. ROZOai is opening OG status for the top 1,000 contributors. This isn’t for casual visitors. It’s for people who stick around, learn the tech, and help ROZOai grow in the coming months. OG status comes with social recognition, early access to features, and ongoing rewards. ROZOai wants to reward the people who help build the project, not just ad agencies.<br>How to join before the window closes<br>If you want to support the Stellar ecosystem and real payment infrastructure, here’s what to do:<br>Join the <a href="https://discord.gg/nFSvDTDw">ROZOai Discord</a> now.<br>Pick two ways to contribute (create content, use the tool, or engage with the community).<br>Submit proof in the <a href="https://docs.google.com/forms/d/e/1FAIpQLSe3hTI0jE46O1bAdlrABduTAB14J2UkHtaf0aL5WKt5nVKvyQ/viewform">Ambassador channel</a> before the day ends.<br>ROZOai is building the rails for the future of payments.</p><p>Are you ready to help and to focus on real utility, not hype?<br>Follow <a href="https://x.com/ROZOai">ROZOai</a> on X for more information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a73c90a53473" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>