<?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 Sikiru Olagoke on Medium]]></title>
        <description><![CDATA[Stories by Sikiru Olagoke on Medium]]></description>
        <link>https://medium.com/@0xdothis?source=rss-690743530ed1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*GQQX6ZuUjdN6Iq0n</url>
            <title>Stories by Sikiru Olagoke on Medium</title>
            <link>https://medium.com/@0xdothis?source=rss-690743530ed1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 17:37:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@0xdothis/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[Demystifying Subgraphs: The Easiest Way to Query Blockchain Data — Part 1]]></title>
            <link>https://blog.blockmagnates.com/demystifying-subgraphs-the-easiest-way-to-query-blockchain-data-part-1-3612e18e5f3c?source=rss-690743530ed1------2</link>
            <guid isPermaLink="false">https://medium.com/p/3612e18e5f3c</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[subgraph]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[beginners-guide]]></category>
            <dc:creator><![CDATA[Sikiru Olagoke]]></dc:creator>
            <pubDate>Mon, 03 Nov 2025 09:44:30 GMT</pubDate>
            <atom:updated>2025-11-03T12:04:52.696Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*RSVTJxx3Nx1VE10AY0ZLcw.png" /></figure><h3>Demystifying Subgraphs: The Easiest Way to Query Blockchain Data — Part 1</h3><h3>Introduction</h3><p>When the topic of data fetching arises, many developers find themselves at a crossroads: <em>what’s the most efficient and reliable method to integrate on-chain data into their frontend applications</em>? While traditional web3 libraries like Viem/Wagmi or Ethers.js offer functionalities such as WatchEvent listeners and “on” event listeners, respectively, these solutions can sometimes fall short for complex data requirements.</p><p>This article series will explore a powerful alternative: Subgraphs. We’ll embark on a practical journey, starting with the fundamental concepts and progressing to advanced features. You’ll learn how to leverage Subgraphs to query on-chain data, with opportunities to code along. Key concepts like one-to-many, many-to-one, and many-to-many relationships will be thoroughly covered. So, buckle up and prepare to demystify Subgraphs!</p><h3>What is Subgraph?</h3><p>A Subgraph is a custom, open API that extracts data from a blockchain, processes it, and stores it so it can be easily queried via GraphQL. Think of it as a bridge that transforms raw blockchain data into an organized, queryable format.</p><p>It serves as a crucial component in the Web3 ecosystem, acting as a custom, open API designed to efficiently interact with blockchain data. Its primary function involves a three-step process: extraction, processing, and storage.</p><ul><li><strong>Extraction</strong>: Subgraphs are built to meticulously extract raw data directly from various blockchains. This raw data, often in a complex and unstructured format, includes transactions, event logs, contract state changes, and other on-chain activities. Without a subgraph, directly querying this data can be cumbersome and resource-intensive, requiring users to iterate through vast amounts of blocks or interact with specific smart contracts individually.</li><li><strong>Processing</strong>: Once extracted, the raw blockchain data undergoes a transformation within the subgraph. This processing involves indexing, filtering, and structuring the data according to predefined schemas. Developers define these schemas using GraphQL’s Schema Definition Language (SDL), specifying the data models and relationships relevant to their application. This step is critical as it converts the raw, often low-level blockchain data into a more human-readable and application-friendly format. For instance, instead of just a transaction hash, a subgraph can process it to show the sender, receiver, amount, and the specific smart contract interaction.</li><li><strong>Storage:</strong> After processing, the organized and structured data is stored in a dedicated database. This persistent storage allows for rapid and efficient querying, unlike directly querying the blockchain, which can be slow and expensive. The database typically holds an indexed version of the blockchain data, making it readily accessible for applications.</li></ul><h3>Why Subgraph?</h3><p>Subgraphs are designed to aggregate application-specific blockchain data, providing frontend developers with quick and efficient access. They expose this data through GraphQL APIs, enabling real-time querying of transaction data associated with your smart contracts. Subgraphs are particularly beneficial for developers building robust frontend interfaces for complex, custom smart contracts.</p><p>For example, imagine needing to query all transactions within a single Uniswap v3 liquidity pool over the last 24 hours. With a Subgraph, Uniswap simply needs to define their data schema, index the relevant event data to create the Subgraph, and then use the generated GraphQL API to perform flexible and efficient queries. This significantly simplifies data retrieval compared to directly interacting with the blockchain for every data point.</p><p>In essence, a Subgraph functions as a vital bridge that seamlessly connects the raw, often opaque world of blockchain data with the organized, queryable demands of modern applications. It transforms the intricate and distributed nature of blockchain information into a structured and easily accessible format, enabling developers to build powerful and performant decentralized applications (dApps) without needing to directly manage complex blockchain interactions. This not only simplifies development but also enhances the user experience by providing fast and reliable access to on-chain data through a familiar and robust query language like GraphQL.</p><h3>Inside a Subgraph</h3><p>A Subgraph is comprised of several key files that define its behavior and the data it indexes:</p><ul><li><strong>subgraph.yaml (Subgraph Manifest):</strong> This file is the heart of your Subgraph. It defines the smart contracts and network your Subgraph will monitor, specifies which events from these contracts to pay attention to, and dictates how event data should be mapped to entities that the Graph Node stores and makes queryable.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/689/1*7P8dmVDavvKHQ4bEikpSQw.png" /><figcaption>subgraph.yaml</figcaption></figure><ul><li><strong>schema.graphql:</strong> This GraphQL schema defines the structure of the data stored by your Subgraph. It outlines the entities (data objects) and their fields, as well as how they can be queried via GraphQL.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/531/1*VB3Ax1i25yUPcJCNLNeB7Q.png" /><figcaption>schema.graphql</figcaption></figure><ul><li><strong>mapping.ts (AssemblyScript Mappings):</strong> This code, written in AssemblyScript, acts as the translator. It takes raw event data emitted by your smart contracts and transforms it into the entities defined in your schema.graphql.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/693/1*nI_eXgwqJxsvQxmYK-a9MQ.png" /><figcaption>this file (formerly known as mapping.ts) is know named after the contract name.</figcaption></figure><h3>Conclusion</h3><p>Subgraphs represent a significant leap forward in democratizing access to blockchain data. By providing a structured, queryable layer over the often-complex on-chain information, they empower developers to build more efficient, robust, and user-friendly decentralized applications. As we’ve explored, Subgraphs simplify data retrieval by handling the intricate processes of extraction, processing, and storage, making it easier to integrate real-time blockchain data into frontend experiences. The combination of a manifest file, a GraphQL schema, and AssemblyScript mappings creates a powerful framework for transforming raw event data into readily consumable entities. Embracing Subgraphs not only streamlines development workflows but also unlocks new possibilities for how we interact with and visualize the vast potential of the blockchain.</p><blockquote>In the coming days/weeks we will explore the practical aspect of subgraph by writing simple smart contracts and querying them in the subgraph playground, after we deploy it to subgraph studio.</blockquote><p>Kindly drop your comment below for any concerns you might have or any follow up questions, you can reach out to me on x (formerly twitter) <a href="https://x.com/0xdothis">0xdothis</a></p><h4>Resources</h4><ul><li><a href="https://thegraph.com/docs/">The Graph Documentation</a></li><li><a href="https://www.alchemy.com/overviews/what-is-a-subgraph">Alchemy Blog — What is a Subgraph?</a></li><li><a href="https://graphql.org/">GraphQL Official Website</a></li><li><a href="https://www.assemblyscript.org/">AssemblyScript Official Website</a></li><li><a href="https://viem.sh/">Viem Documentation</a></li><li><a href="https://docs.ethers.org/v6/">Ethers.js Documentation</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3612e18e5f3c" width="1" height="1" alt=""><hr><p><a href="https://blog.blockmagnates.com/demystifying-subgraphs-the-easiest-way-to-query-blockchain-data-part-1-3612e18e5f3c">Demystifying Subgraphs: The Easiest Way to Query Blockchain Data — Part 1</a> was originally published in <a href="https://blog.blockmagnates.com/">Block Magnates</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to Web3: My third week at web3bridge, what i have learnt so far —  Part 2]]></title>
            <link>https://blog.blockmagnates.com/introduction-to-web3-my-third-week-at-web3bridge-what-i-have-learnt-so-far-part-2-a52611880f84?source=rss-690743530ed1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a52611880f84</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[solidity]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Sikiru Olagoke]]></dc:creator>
            <pubDate>Thu, 07 Aug 2025 10:42:48 GMT</pubDate>
            <atom:updated>2025-08-22T14:19:51.853Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction to Web3: My third week at web3bridge, what i have learnt so far — Part 2</h3><p>This is the second part of an article I posted you can read it here <a href="https://medium.com/@olagokesikiru06/introduction-to-web3-ecosystem-my-3rd-week-at-web3bridge-and-what-i-have-learnt-so-far-6f39a6bbd647">Part 1</a>, Going forward I will be working you through what I learnt at the second part of my week 3. The second part introduces solidity fundamentals, without further ado let’s get into it.</p><h4>Solidity Fundamentals</h4><p>Solidity is a high-level, object-oriented programming language specifically designed for writing smart contracts on various blockchain platforms, most notably Ethereum. It’s a statically-typed language, meaning that variable types must be defined at compile time, and it supports features like inheritance, user-defined types (structs, mappings, enums), and libraries. Key elements of Solidity include contract definitions, state variables, functions, and the constructor, which is executed during contract deployment.</p><h4>Data Types and Variables</h4><p>Solidity, is a statically-typed language for developing smart contracts on the Ethereum blockchain, it requires explicit declaration of data types for all variables. This allows the compiler to ensure correct usage and memory allocation.</p><p>Below are the types we’ve covered so far:</p><h4><strong>Value Types:</strong></h4><p>These types store their data directly in memory and are copied when assigned or passed as function arguments.</p><ul><li>Booleans (bool): Stores true or false.</li><li>Integers (int, uint): Signed (int) and unsigned (uint) integers of various sizes (e.g., uint8, int256).</li><li>Address (address, address payable): Stores 20-byte Ethereum addresses. address payable can receive Ether.</li><li>Enums (enum): User-defined types with a finite set of named values.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a3bd98d8fef1ddf1f13ce2efc8848bdb/href">https://medium.com/media/a3bd98d8fef1ddf1f13ce2efc8848bdb/href</a></iframe><h4><strong>Reference Types:</strong></h4><p>These types store a reference (memory address) to where the actual data is located.</p><ul><li>Strings (string): Dynamically-sized UTF-8 encoded text.</li><li>Arrays: Can be fixed-size (uint[5]) or dynamic-size (uint[]).</li><li>Structs (struct): User-defined complex data types that group multiple variables.</li><li>Mappings (mapping): Key-value pairs, similar to hash tables, where keys map to a value type.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/edf09d93e77ef0b32a7583fc43f980a7/href">https://medium.com/media/edf09d93e77ef0b32a7583fc43f980a7/href</a></iframe><h4>Variables in Solidity:</h4><p>Variables are named storage locations for data within a smart contract. They are declared by specifying their data type and name.</p><h4><strong>State Variables</strong></h4><p>Declared outside of any function, their values are permanently stored in the contract’s storage on the blockchain.</p><h4><strong>Local Variables</strong></h4><p>Declared inside a function, their values are temporary and only exist during the function’s execution.</p><h4><strong>Global Variables</strong></h4><p>Special built-in variables provided by Solidity that offer information about the blockchain, transaction, and execution context (e.g., block.timestamp, msg.sender, msg.value).</p><p>To declare a variable there’s is a convention also known as signature, it’s just a rule to guide developers on proper variable definitions</p><p>[type] [visibility] &lt;variableName&gt;.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/544e2f6187b45d854d2e1cb726864daf/href">https://medium.com/media/544e2f6187b45d854d2e1cb726864daf/href</a></iframe><h4>Function</h4><p>A function is a named block of code within a smart contract that performs a specific task.</p><p>when declaring a function there’s a convention which can also be called function signatures to help developers define a function</p><p>function &lt;name&gt;(dataType arg1) &lt;visibility&gt; &lt;stateMutability&gt; returns (returnType) {}</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/542c6bc03e3907ae44071e01c95f2b65/href">https://medium.com/media/542c6bc03e3907ae44071e01c95f2b65/href</a></iframe><h4><strong>Visibility:</strong></h4><p>Functions have visibility modifiers that control where they can be called from:</p><ul><li><strong>public:</strong> Accessible from anywhere, including external calls and other contracts.</li><li><strong>external:</strong> Accessible only from external calls (other contracts or transactions), not internally within the same contract.</li><li><strong>internal:</strong> Accessible only within the contract and its derived contracts.</li><li><strong>private:</strong> Accessible only within the contract where it is defined, not in derived contracts.</li></ul><h4><strong>State Mutability</strong></h4><p>These modifiers indicate how a function interacts with the blockchain state:</p><ul><li><strong>view</strong>: Declares that the function does not modify the state. It only reads from the state.</li><li><strong>pure</strong>: Declares that the function does not read or modify the state. It operates solely on its input parameters.</li><li><strong>No modifier (default)</strong>: The function can modify the state.</li><li><strong>payable</strong>: The function can receive Ether along with the transaction.</li></ul><h4>Parameters and Return Values</h4><p>Functions can accept input parameters and return output values. The data types of parameters and return values must be explicitly declared.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/aefe68fb29e9d276c7add8fb95ea3eeb/href">https://medium.com/media/aefe68fb29e9d276c7add8fb95ea3eeb/href</a></iframe><h4>Storage and Memory</h4><p>Storage refers to persistent, contract-level storage on the blockchain, where state variables are stored and their values persist across function calls and transactions.</p><p>Memory refers to a temporary storage, where local variable or function argument is stored and discarded after the function execution has ended.</p><h4>Reading a Smart Contract</h4><p>It involves understanding the contract’s code, its state variables, functions, and events, as well as how it interacts with the blockchain.</p><h4>Smart Contract ABI</h4><p>The Smart Contract ABI (Application Binary Interface) in Solidity serves as a crucial interface for interacting with compiled smart contracts on the Ethereum Virtual Machine (EVM). It acts as a standardized specification that defines how external applications or other smart contracts can communicate with a deployed contract.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/132c782c14549775b8dd56d2433b706b/href">https://medium.com/media/132c782c14549775b8dd56d2433b706b/href</a></iframe><h4>Events and Logs</h4><p>Events are declarations within a smart contract that define a structure for logging specific occurrences. They act as signals emitted by the contract to indicate that something significant has happened, such as a transfer of tokens, a change in state, or the completion of an action.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fa185f54ab604dac7bed52e8a54b294c/href">https://medium.com/media/fa185f54ab604dac7bed52e8a54b294c/href</a></iframe><p>Logs are the actual data records created on the blockchain when an event is emitted. They are stored within the transaction receipts and are a low-level feature of the Ethereum Virtual Machine (EVM).</p><p>Each log entry consists of “topics” and “data.” Topics are indexed parameters from the event definition, allowing for efficient filtering and searching. Data contains the non-indexed parameters.</p><p>While smart contracts cannot directly read or access logs, external applications can query and filter them using tools like <a href="http://ethers.js/">ethers.js</a> or by using block explorers like Etherscan.</p><p>Logs provide a historical record of events, enabling transparency, debugging, and the creation of rich user interfaces that display real-time contract activity. They are a fundamental component for building robust and interactive decentralized applications.</p><h4>Factory Contract</h4><p>A factory contract is a smart contract designed to deploy other smart contracts. Think of it as a blueprint or template that allows for the creation of multiple instances of a similar contract, streamlining the deployment process and potentially saving on gas costs.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0a709bafda3742690e1204507e3efc52/href">https://medium.com/media/0a709bafda3742690e1204507e3efc52/href</a></iframe><h3>Conclusion</h3><p>So far in this articles I covered the second half of what i learnt in week 3, which covers data types, variables, functions, events, logs, memory, storage, and factory contract.</p><p>It was an insightful week and I really learnt a lot. Let’s move on to week 4</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a52611880f84" width="1" height="1" alt=""><hr><p><a href="https://blog.blockmagnates.com/introduction-to-web3-my-third-week-at-web3bridge-what-i-have-learnt-so-far-part-2-a52611880f84">Introduction to Web3: My third week at web3bridge, what i have learnt so far —  Part 2</a> was originally published in <a href="https://blog.blockmagnates.com/">Block Magnates</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to Web3 Ecosystem: My 3rd week at web3bridge and what I have learnt so Far — part 1]]></title>
            <link>https://blog.blockmagnates.com/introduction-to-web3-ecosystem-my-3rd-week-at-web3bridge-and-what-i-have-learnt-so-far-6f39a6bbd647?source=rss-690743530ed1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f39a6bbd647</guid>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[ethereum-blockchain]]></category>
            <category><![CDATA[solidity]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Sikiru Olagoke]]></dc:creator>
            <pubDate>Mon, 28 Jul 2025 08:25:33 GMT</pubDate>
            <atom:updated>2025-08-22T14:19:55.153Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6-ElalzIXVl4Fu6-_7h8tw.jpeg" /><figcaption>Welcome to web3bridge</figcaption></figure><p>Been a lover of the web3 ecosystem I was opportune to join the <a href="https://medium.com/u/d27c09952d68">Web3bridge</a> Bootcamp CohortXIII Onsite, my first week was a mixed feeling of if I’m doing the right thing or not but I was able to find my footing.</p><p>The 1st week started with a lot of introduction to the concept of blockchain and how it all came to be.</p><p>Week 2nd covered an in-depth Introduction to ethereum blockchain, ERC and EIP meaning and their importance to the web3 ecosystem at large.</p><p>Further more in my 3rd week we were introduced to Decentralized Application (dApps) Development and Solidity, given us a general overview on what to expect going forward.</p><h3>Introduction to Decentralized Applications (DApps) Development.</h3><p>Decentralized application (DApp) development involves creating software that runs on a decentralized network, typically a blockchain, instead of relying on a central server. This approach offers advantages like enhanced security, transparency, and resistance to censorship compared to traditional applications. DApps leverage blockchain technology and often utilize smart contracts to automate processes and enforce agreements.</p><h4>Development Environment Setup Options.</h4><p>This is the most common setup, where all development tools and resources are installed directly on the developer’s local machine.</p><h4>Components</h4><ul><li>Operating System: Operating systems like Windows, macOS, or Linux are important when developing, as a developer you need to decide on an operating system you’re familiar with and also make sure it supports the required software needed for seamless development.</li><li>Code Editor/IDE: Visual Studio Code, Sublime text, or Cursor are tools that you write your codes in you need to chose them carefully as they will be part of your journey while developing.</li><li>Version Control System: Git, typically used with platforms like GitHub or GitLab are a way of making sure your progress are saved without issues or worry, they can also serve as a portfolio for potential employers.</li><li>Package Managers: npm or yarn amongst others help keep all dependencies in one place for easy access making it easing to replicate the exact same working file system on another operating system.</li><li>Terminal/Shell: Windows Terminal, Zsh, or Bash are hardware device, or a software application that emulates one, used for interacting with a computer system, while working with GUI (Graphical user interface) is easier been able to navigate your way around the terminal is an added advantage.</li></ul><h4>Key Developer Tools</h4><p>when it comes to development it is necessary to identify tool that will be essential for fast code delivery and simplicity. There has always been a debate on which tool is the best, while I haven’t used variety of tools it’s important to take peoples opinion with a little grain of salt, as people can be biased sometimes.</p><p>My Tools includes</p><ul><li>Window Operating System</li><li>VsCode + WSL 2</li></ul><h4>Connecting to a Testnet</h4><p>To connect to a testnet, you typically need to configure your wallet (like MetaMask) with the specific network details, including the network name, RPC URL, chain ID, and optionally a block explorer URL. You may also need to acquire testnet tokens (e.g., LINK or ETH) from a faucet. I use <a href="https://fauceth.dev/">fauceth.dev</a> a community driven faucet dapp to get faucets.</p><h3>Development Environments / Tools</h3><h4>Remix IDE for Development and Testing</h4><p>Remix IDE is an open-source, browser-based Integrated Development Environment (IDE) specifically designed for the development and testing of smart contracts, primarily on the Ethereum blockchain using the Solidity programming language.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VT9bYxwpO8eV9grr7-A5MQ.png" /><figcaption><a href="https://ethereum.github.io/remix-ide/">Remix IDE</a></figcaption></figure><p>Features of Remix IDE includes but are not limited to</p><ul><li>Built in compiler: Compiles Solidity code directly within the IDE, simplifying the compilation process.</li><li>Solidity Editor: Provides a user-friendly interface for writing Solidity code with features like syntax highlighting, auto-completion, and code analysis.</li><li>Deployment options: Allows deployment of smart contracts to various environments, including the Remix VM (a simulated blockchain environment for quick testing), public testnets (like Sepolia or Holesky), and the Ethereum mainnet.</li></ul><h4>The Hardhat Development Environment</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mFghfgzv6bS3iIsBnBpnBQ.png" /><figcaption><a href="http://github.com/NomicFoundation/hardhat?tab=readme-ov-file">Hardha</a>t IDE</figcaption></figure><p>Hardhat is a comprehensive development environment designed for building, testing, and deploying smart contracts on the Ethereum blockchain and other EVM-compatible networks. It streamlines the entire smart contract development workflow by providing a suite of tools and features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*E2hJV1SV_qkkttrBCRBL3w.png" /><figcaption><a href="https://dev.to/rodrigoherrerai/the-complete-hands-on-hardhat-tutorial-3kbd">Hardhat File Structure by </a><a href="https://dev.to/rodrigoherrerai">Rodrigo Herrera Itie</a></figcaption></figure><p>A typical Hardhat project is structured into several key directories and files: /contracts, /scripts, /test, and hardhat.config.js. The /contracts directory holds the Solidity smart contract files. Deployment scripts are stored in /scripts, and unit tests are placed in /test. The hardhat.config.js file is the main configuration file, allowing customization of the development environment.</p><h4>Key features of hardhat includes:</h4><ul><li>Compilation: Hardhat allows developers to compile Solidity smart contracts into bytecode and ABIs, which are necessary for deploying and interacting with contracts.</li><li>Deployment: It facilitates the deployment of compiled smart contracts to various blockchain networks, including local development networks (like Hardhat Network), testnets, and mainnets.</li><li>Testing: Hardhat provides a robust testing framework for smart contracts. It integrates with popular testing libraries like Chai and offers features like Solidity stack traces and automatic error messages for effective debugging.</li><li>Debugging: Hardhat enhances the debugging experience by providing console.log() functionality within Solidity code, similar to JavaScript, allowing developers to print variable values and log messages during execution.</li><li>Hardhat Network: A built-in, local Ethereum network that offers fast transaction processing and features like mainnet forking, enabling developers to test their contracts in a realistic environment without deploying to a public network.</li></ul><h4>Foundry as an Alternative Development Environment</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X5JnJUzf0bkUAxxkB0MZ6g.png" /><figcaption><a href="https://getfoundry.sh/">Foundry IDE</a></figcaption></figure><p>Foundry is a smart contract development toolchain, providing a suite of tools for building and deploying decentralized applications (dApps) on the Ethereum blockchain. It’s designed to simplify the development process, offering features like smart contract compilation, testing, deployment, and interaction with the blockchain, all through a command-line interface.</p><h4>Key Components and Features</h4><ul><li>forge: A core tool for compiling, testing, and deploying smart contracts.</li><li>cast: Enables interaction with the blockchain via RPC, allowing for contract calls, transaction sending, and data retrieval.</li><li>anvil: Provides a local blockchain node for development and testing purposes.</li><li>chisel: A Solidity REPL (Read-Eval-Print Loop) for writing and testing Solidity code directly.</li><li>Fast and Efficient<strong>:</strong> Foundry is known for its speed and efficiency, enabling developers to move from idea to deployment quickly.</li><li>Security Focused: Foundry incorporates tools and frameworks for ensuring smart contract security, including vulnerability scanning.</li><li>Solidity Testing: Foundry allows developers to write unit tests in Solidity, streamlining the testing process.</li><li>Modular and Portable: Foundry is built with Rust and offers a modular design, making it highly portable across different environments.</li><li>Developer Empowerment: Foundry aims to democratize blockchain development by providing a user-friendly environment and powerful tools.</li></ul><h4>The Node Package Manager</h4><p><strong>npm</strong> is a package manager for the JavaScript programming language maintained by npm, Inc., a subsidiary of GitHub. npm is the default package manager for the JavaScript runtime environment <a href="http://node.js/">Node.js</a> and is included as a recommended feature in the <a href="http://node.js/">Node.js</a> installer.</p><p>It consists of a command line client, also called npm, and an online database of public and paid-for private packages, called the npm registry. The registry is accessed via the client, and the available packages can be browsed and searched via the npm website. The package manager and the registry are managed by npm, Inc.</p><h3>Conclusion</h3><p>The first part of the week introduced me to concept about blockchain and web3 ecosystem that I haven’t thought about, it also help cleared a lot of mis-conception by solidifying my foundational knowledge. I will be introducing the second part of this article which delve into Solidity as a programming language for Ethereum.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f39a6bbd647" width="1" height="1" alt=""><hr><p><a href="https://blog.blockmagnates.com/introduction-to-web3-ecosystem-my-3rd-week-at-web3bridge-and-what-i-have-learnt-so-far-6f39a6bbd647">Introduction to Web3 Ecosystem: My 3rd week at web3bridge and what I have learnt so Far — part 1</a> was originally published in <a href="https://blog.blockmagnates.com/">Block Magnates</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding EIP-681 : URL Format for Transaction Requests.]]></title>
            <link>https://0xdothis.medium.com/understanding-eip-681-url-format-for-transaction-requests-cc95295f392e?source=rss-690743530ed1------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc95295f392e</guid>
            <dc:creator><![CDATA[Sikiru Olagoke]]></dc:creator>
            <pubDate>Sat, 19 Jul 2025 21:14:59 GMT</pubDate>
            <atom:updated>2025-07-19T21:16:36.805Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1btyTG7rPQUXIhcL4MXG_g.jpeg" /></figure><h3>Introduction</h3><p>Blockchain transactions are at the heart of cryptocurrencies and decentralized apps (dApps). But sending these transactions smoothly can be tricky. That’s where protocols like EIP-681 come into play. It helps turn complex transaction data into simple URLs. This makes sending crypto easier, safer, and more consistent. When you understand the URL format of EIP-681, it becomes a powerful tool for developers and users alike. This article dives into how these URLs work, what they include, and best ways to use them.</p><h3>The Fundamentals of EIP-681 and Its Role in Blockchain Transactions</h3><h4>What is EIP-681?</h4><p>EIP-681 is an Ethereum Improvement Proposal that was authored by Daniel A. Nagy which has been approved and implemented as ERC-681. It’s a set of rules that standardizes how transaction requests are written in URLs. Instead of copying long transaction data, you encode it in a neat, predictable way. It allows web browsers and wallet apps to interpret transaction details directly. Think of it as a language that helps wallet apps understand exactly what you want to do with a simple link.</p><h4>Why EIP-681 Matters for Developers and Users</h4><p>EIP-681 makes things quick and easy. Instead of copying and pasting complex data, users click a link to start a transaction. Developers can build smarter, more interconnected apps. Users get a smoother experience, with fewer mistakes and better security. EIP-681 helps bridge the gap between web pages and blockchain wallets, making blockchain tech more friendly for everyone.</p><h4>Key Components of EIP-681</h4><ul><li>Protocol prefix (ethereum:): Tells the browser or app it’s an Ethereum URL.</li><li>Address: The wallet or contract involved.</li><li>Function call data: What function on a contract you’re calling (like transferring tokens).</li><li>Parameters: Extra info like amount, gas limits, or chain IDs.</li><li>Optional extensions: Details for tokens or different networks.</li></ul><h3>Structure and Syntax of EIP-681 URL Format</h3><h4>Basic URL Format</h4><p>A typical EIP-681 URL looks like this: ethereum:[function_or_address][@chainId][?parameters]</p><p>Here’s what each part does:</p><ul><li>ethereum: is the starting point.</li><li>The function or address can specify what you want.</li><li>@chainId (optional) tells which network to use.</li><li>?parameters include details like how much ETH or gas to use.</li></ul><p>For example:</p><p>ethereum:0x89205A3A3bDa56Bf4B4dA9E7b8C4C3b9d7a8D3?value=1.5e18</p><p>This URL is set up to send 1.5 ETH to the address above.</p><h3>Address and Function Calls</h3><p>The address part follows the standard Ethereum address format, which is a string starting with 0x. To call a specific function, you encode the function’s signature and parameters. For example, to call a token transfer, you encode the function signature like transfer(address,uint256) and the recipient’s address and amount, all in a code-friendly format.</p><h4>Parameters and Query Strings</h4><p>You can add additional info using query strings:</p><ul><li>value: Amount of ETH (in wei)</li><li>gas: Gas limit for the transaction</li><li>gasPrice: How much you’re willing to pay per gas unit</li><li>token: Contract address for tokens</li><li>Encoding these parameters correctly ensures that the transaction is precise and secure. e.g: ethereum:0xTokenContractAddress?value=1000000000000000000 to send 1 token.</li></ul><h4>Incorporating Chain and Token Details</h4><p>You can tell the URL which Ethereum network to use:</p><ul><li>Mainnet: no chainId, defaults to mainnet.</li><li>Testnets: add @3 for Ropsten, @4 for Rinkeby, see what network the URL targets.</li></ul><p>When dealing with tokens, include the token contract address and specify the transfer with proper data. This makes multi-chain support easier, especially when working with tokens across different networks.</p><h3>Practical Use Cases and Examples of EIP-681 URLs</h3><h4>Sending ETH</h4><p>Say you want to send 0.1 ETH. You can build this URL: ethereum:0xRecipientAddress?value=100000000000000000</p><p>Clicking or sharing this link can trigger your wallet to send the amount no copying pasting needed. It’s perfect for web wallets or quick payment setups.</p><h4>Interacting with Smart Contracts</h4><p>To transfer tokens like an ERC-20, encode the function data: ethereum:0xTokenAddress/transfer?address=0xRecipient&amp;uint256=1000000</p><p>This URL is a simple way to execute smart contract functions directly from a link. Developers can make token transfers as easy as clicking.</p><h4>Token Purchase and DeFi Transactions</h4><p>When buying tokens or working with DeFi platforms, such as Uniswap, URLs can encode complex swaps or deposits. For instance: ethereum:swap?exactInput=0x...&amp;amountIn=1000000000000000000</p><p>This kind of URL helps users interact without navigating deep into dApps.</p><h4>Best Practices for URL Generation</h4><ul><li>Always double-check the address and parameters.</li><li>Encode special characters, like &amp; and ?, properly.</li><li>Use trusted tools for generating URLs to avoid mistakes.</li><li>Limit the amount of information in URLs to prevent security risks.</li></ul><h3>Security Considerations and Limitations</h3><h4>Risks Associated with URL-Based Transactions</h4><p>Sharing URLs can be risky if they’re not secure. Phishers can craft fake URLs resembling real ones to steal funds. Always verify URLs before clicking or sharing. Malicious URLs may look legit but trick users into signing unwanted transactions.</p><h4>Mitigations and Recommendations</h4><ul><li>Use official wallets and trusted apps for generating transaction URLs.</li><li>Validate URLs within your dApps before executing.</li><li>Educate users to recognize genuine links and avoid suspicious ones.</li></ul><h4>Limitations of EIP-681</h4><p>Some wallets or browsers might not fully support all URL features of EIP-681. Complex transactions or multi-step interactions could be hard to encode. This limits certain use cases where extensive data or multi-contract calls are involved.</p><h4>Future Perspectives and Enhancements</h4><p>Discussions are ongoing about improving EIP-681 further. Ideas include better support for multi-chain interactions and deeper integration with other standards like EIP-712. As more wallets support these URLs, expect easier and safer ways to send transactions from web pages or mobile apps.</p><h3>Conclusion</h3><p>EIP-681 plays a key role in making blockchain transactions easier through URLs. It simplifies how we send ETH, interact with smart contracts, or work with tokens. But correct formatting and security practices are vital to avoid issues. As the standard develops, more tools and features will make blockchain technology more user-friendly and safer. Staying informed about these updates ensures you’re always prepared to use decentralized networks confidently.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc95295f392e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My First Week in Web3Bridge: An In-Depth Journey into Blockchain Education and Community Building.]]></title>
            <link>https://0xdothis.medium.com/my-first-week-in-web3bridge-an-in-depth-journey-into-blockchain-education-and-community-building-e6ca5e299193?source=rss-690743530ed1------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6ca5e299193</guid>
            <dc:creator><![CDATA[Sikiru Olagoke]]></dc:creator>
            <pubDate>Sat, 12 Jul 2025 12:14:48 GMT</pubDate>
            <atom:updated>2025-07-12T12:47:44.027Z</atom:updated>
            <content:encoded><![CDATA[<p>Starting my journey into Web3Bridge was an exciting leap into the future of technology. I was eager to learn about blockchain, smart contracts, and the Web3 movement. With blockchain technology growing fast new developers joined the scene every now and then, it’s clear why this kind of education matters. Hands-on experience and community links make learning Web3 real and practical. This week has been packed with new knowledge and opportunities I didn’t expect.</p><h3>Understanding Web3Bridge</h3><h4>What Is Web3Bridge?</h4><p>Web3Bridge is an onsite and online bootcamp designed to teach people about blockchain development, decentralized finance (DeFi), and smart contract creation. It started with a clear goal: <strong><em>To train Web3 developers in Africa</em></strong>, regardless of location or background. The bootcamp offers courses, mentorship, and projects to help students build real skills.</p><h4>The Mission to Bridge the Web3 Skill Gap</h4><p>The founders saw a huge gap worldwide, many people want to work in blockchain development, but they lack proper training. Web3Bridge targets Africa where access to technological education is limited. Its goal is to shut this gap by giving everyone a chance n and grow in the Web3 space.</p><h4>Core Values and Approach</h4><p>Web3Bridge focuses on practical skills through project-based lessons. Mentors guide students step-by-step, helping them implement what they learn. Instead of just theory, the platform emphasizes real-world tasks. Working on projects and collaborating with others helps students become confident developers in the industry.</p><h3>Navigating the First Week: Key Activities and Experiences</h3><h4>From Home</h4><p>It wasn&#39;t an easy experience for me, the venue for the event was in Igbogbo, Ikorodu Lagos, Nigeria. I moved all the way from Niger state and got to Lagos quite late, I got to the facility around 11:50pm, fortunately for me the security was available to welcome me.</p><h4>Orlentation and Onboarding Process</h4><p>My first onboarding was smooth. We were asked to connect to discord and verify our eligibility for the program. There was a ritual that was always performed in every cohort we were asked to introduce ourselves and speak about our experience getting to the facility.</p><h4>My First Week</h4><p>On day one we were welcomed with an assessment from the pre-content material shared with us. Immediately afterwards we covered blockchain basics and setting up a crypto wallet. These sessions were beginner-friendly but packed with info. I learned how blockchain keeps data safe and transparent.</p><h4>Exploring Learning Resources</h4><p>There are tutorials, videos, and reading materials ready to dive into. I started with beginner guides on smart contracts and Ethereum whitepaper. These resources are easy to follow and help demystify complex ideas. They&#39;re perfect for building solid foundations early on. The mentor explained everything that was confusing and even helped with materials for further understanding.</p><h3>Gaining Hands-On Experience</h3><h4>Completing First Assignments</h4><p>My first assignment involved reading and understanding a material provided by the mentor, for every assignment we would take an assessment that’s been recorded, the most tasking assignment so far was to run a client node using either Rust, Geth etc. We’re also asked to write articles and publish it to improve our writing skills. These exercises boosted my confidence and curiosity.</p><h3>Overcoming Challenges and Embracing Opportunities</h3><h4>Common Initial Hurdles</h4><p>Some parts of blockchain are confusing like e.g how nodes agree on data, The Patricia Merkle Tries, and Cryptography Hash Functions. I also faced technical issues with setup and debugging. But these challenges are normal, and Web3Bridge provides guides and support to work through them.</p><h4>Resources and Support Systems</h4><p>Mentors offered invaluable help during tricky moments. I also joined online forums to ask questions outside of official channels. Over time, the hurdles felt smaller, and my</p><p>skills grew.</p><h3>Actionable Tips for Continued Growth</h3><ul><li>Set weekly goals like mastering wallet creation or deploying a contract.</li><li>Keep up with blockchain, news sites like Coin Desk are good starting points.</li><li>Join community events and hackathons they&#39;re perfect for practice and networking.</li></ul><h3>Reflection and Future Outlook</h3><p>This first week taught me that consistent practice makes a difference. Every small task adds up to real skills. The more I engage, the clearer my career path in blockchain becomes. Completing Web3Bridge&#39;s program can unlock jobs in this booming field. For anyone curious about Web3, this is a solid place to start.</p><h3>Concluslon</h3><p>My first week in Web3Bridge was a whirlwind of learning and connecting. The platform&#39;s focus on practical skills and community support makes it the perfect place for newcomers Blockchain isn&#39;t just tech; it&#39;s a new way to solve problems and share value. If you&#39;re ready to embrace the challenge, Web3Bridge is there to guide you. Join the community, start small, and watch your Web3 skills grow. The future belongs to those who learn and build today</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6ca5e299193" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Concerns About Ethereum Adoption in Africa: A Web3 Student’s Perspective]]></title>
            <link>https://0xdothis.medium.com/my-concerns-about-ethereum-adoption-in-africa-a-web3-students-perspective-71b6a25dc5eb?source=rss-690743530ed1------2</link>
            <guid isPermaLink="false">https://medium.com/p/71b6a25dc5eb</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Sikiru Olagoke]]></dc:creator>
            <pubDate>Thu, 10 Jul 2025 21:49:35 GMT</pubDate>
            <atom:updated>2025-07-10T21:49:35.692Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RfPYj6SwbBmzu0yWJxjdfw.jpeg" /></figure><h3>Introduction</h3><p>Blockchain technology, especially Ethereum, sparks a lot of interest across Africa. Many see it as a chance to boost economies, create jobs, and even fight corruption. But, while the idea sounds promising, big hurdles block the way. These challenges aren’t just about technology they’re about infrastructure, costs, and access. From my perspective as a student looking into Web3, I see the real issues that could slow down Ethereum’s growth on the continent. It’s crucial to understand these roadblocks to build smarter solutions.</p><h3>The Current State of Ethereum Adoption in Africa</h3><h4>Overview of Blockchain Development on the Continent</h4><p>Africa is making strides with blockchain projects. Countries like Nigeria have buzzing crypto communities, and Botswana is experimenting with blockchain in agriculture and government services. Several startups are using blockchain to improve supply chains, banking, and even health records. Still, the progress is uneven, and widespread adoption remains a challenge.</p><h4>Adoption Metrics and Trends</h4><p>Compared to other parts of the world, Ethereum usage in Africa is low. Wallet ownership and transactions are growing but still lag behind. For example, only around 10-15% of Africans who own cryptocurrencies use Ethereum regularly. Globally, many countries see much higher numbers close to 48% internet penetration means more people can access and use blockchain-based apps. For Africa, with just 22% internet access, the gap is huge. This makes it tough for Ethereum to reach average users.</p><h3>Challenges to Ethereum Adoption in Africa</h3><h4>High Data Costs and Its Impact</h4><p>Data costs hit hard in many African countries. For example, in Nigeria, the average mobile data costs around 2-3% of daily income, which is quite high. Since blockchain transactions and decentralized apps (dApps) use a lot of data, these prices stop many from trying. If internet costs stay high, many won’t even bother to download wallets or access Ethereum platforms. This creates a big barrier for everyday users.</p><h4>Low Internet Penetration and Digital Divide</h4><p>Just 22% of people have internet in Africa, compared to 48% worldwide. This digital divide means less than a quarter of the population can even log into Ethereum wallets or platforms. Most people still rely on feature phones, not smartphones, making access even harder. If we want Ethereum to grow, we need wider internet access. Without it, many Africans will stay outside the Web3 ecosystem.</p><h4>Infrastructure Limitations</h4><p>Electricity shortages, unreliable power grids, and limited smartphone access hurt Ethereum adoption. A lot of people don’t have consistent electricity, so charging a phone or running a computer for blockchain activities becomes a challenge. Network quality is patchy in rural areas. These issues make it hard to use Ethereum, especially for transactions or smart contracts that need steady online access.</p><h4>Regulatory and Legal Hurdles</h4><p>Regulations are all over the place. Some African countries have banned or heavily restricted cryptocurrencies, while others are still figuring out rules. This uncertainty scares away investors and stops projects from expanding. Without clear regulations, people are hesitant to hold or trade Ethereum. This kind of legal gray area limits growth and innovation.</p><h4>Educational and Awareness Barriers</h4><p>Many Africans don’t know what blockchain or Ethereum really are. Lack of proper education and awareness programs leave people confused or wary. Schools and local initiatives haven’t fully embraced blockchain literacy. If more young people and entrepreneurs understood how Ethereum works, adoption could pick up faster. But right now, knowledge gaps hold back progress.</p><h3>Potential Opportunities and Solutions</h3><h4>Infrastructure Development and Policy Support</h4><p>Building better internet and electricity systems is key. Governments and companies need to work together to upgrade infrastructure. Solar power solutions, for instance, can fix electricity shortages. Flexible policies encouraging crypto innovation will also create a friendlier environment for Ethereum projects.</p><h4>Reducing Data Costs</h4><p>Partnering with telecom providers can make internet cheaper. Initiatives like zero-rated access where data used for blockchain apps isn’t deducted from data plans can help. Promoting lightweight dApps that don’t require much bandwidth is another smart move.</p><h4>Enhancing Education and Awareness</h4><p>Training programs and workshops tailored for students and entrepreneurs boost understanding. Creating local content like tutorials, videos, and courses helps spread knowledge. Building a community of blockchain advocates also encourages more people to explore Ethereum.</p><h4>Innovative Use Cases Suited for Africa</h4><p>Ethereum-powered solutions tailored to African needs will drive adoption. Examples include remittance platforms that cut transaction costs, or agricultural supply chains that track produce from farm to market. These projects are practical and can directly benefit local communities.</p><h4>Leveraging Mobile Technology</h4><p>Most Africans access the internet via mobile phones. Developing mobile-friendly Ethereum apps and wallets ensures more people can participate. Mobile-based staking, token swaps, and payments are perfect for increasing access.</p><h3>Expert Opinions and Real-World Examples</h3><h4>Insights from Blockchain and Crypto Experts</h4><p>Vitalic Buterin, Ethereum’s creator, emphasizes the importance of infrastructure and education to grow adoption globally. Some African entrepreneurs focus on creating simple, mobile-based Ethereum apps that suit local needs. Their insights show that understanding local challenges is key.</p><h3>Successful Case Studies</h3><p>In Kenya, mobile money was a first step to financial inclusion. Now, projects that combine mobile money with Ethereum smart contracts are showing promise. These initiatives prove that with the right approach, infrastructural hurdles can be overcome.</p><h3>Conclusion</h3><p>The road to Ethereum’s widespread adoption in Africa is filled with hurdles. High data costs, poor internet access, and limited infrastructure slow things down. Weak regulations and low awareness add to the challenge. But these barriers are not insurmountable. With targeted efforts from better infrastructure to tailored education the future can be different. Students and young entrepreneurs have a significant role in pushing this change. By understanding the challenges and advocating for inclusive policies, we can help unlock Ethereum’s potential for Africa. For everyone involved policymakers, tech builders, students collaborating is the key. The goal is clear: creating a blockchain ecosystem that works for Africa’s unique needs. The future of Ethereum in Africa depends on our collective actions today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71b6a25dc5eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>