Tag: Blockchain

  • Meet Aditi Polkam: Building, Breaking, and Shipping in Web3

    Meet Aditi Polkam: Building, Breaking, and Shipping in Web3

    A Web2 intern who dabbled in crypto trading during lockdown is now building across the Web3 ecosystem. Her secret? Stop waiting to be ready and start experimenting.

    Aditi Polkam’s entry into Web3 wasn’t through a grand epiphany or a prestigious program. It started with lockdown curiosity about crypto trading and evolved into writing technical content for a Web3 company. What followed was a journey of constant experimentation, countless failures, and the realization that building in public is more valuable than waiting for perfection.

    Her path from technical writer to fullstack developer to hackathon winner shows something important about Web3: there’s no single right way in. While others might obsess over learning every acronym and tool, Aditi focused on one thing at a time, built projects that broke, fixed them, and shipped anyway.

    What sets her apart isn’t just her technical skills. It’s her honest acknowledgment that feeling lost is normal in Web3, and that the overwhelming information overload everyone talks about is real. Instead of pretending otherwise, she leaned into fundamentals, found her community, and kept building even when projects failed.

    At Offline Protocol, she continues to explore new technologies hands-on, but her real contribution might be her philosophy: experimentation is underrated. Most growth doesn’t come from following a perfect roadmap. It comes from trying things, breaking things, and iterating until something works.

    Meet Aditi Polkam: Building, Breaking, and Shipping in Web3

    The Interview: Aditi’s Web3 Journey

    1. Tell us a bit about yourself.

    Aditi: Hey, I’m Aditi. I’m from India and currently working with Offline Protocol while also experimenting with projects across the Web3 space. Most of what I do is about exploring new technologies, trying them hands-on, and figuring out how they can be applied in real-world scenarios. I enjoy building things, contributing to projects, and constantly learning along the way.

    2. What were you doing before Web3?

    Aditi: Before Web3, I was interning at a Web2 startup where I got to work on multiple client projects. It gave me a lot of exposure to how software is built in the real world and what it means to ship things under deadlines. Around that time, I also got the opportunity to write technical content for a Web3 company. That felt like an interesting entry point, so I took it — and that’s how I slowly transitioned from just “observing Web3 from the outside” to actively contributing to it.

    3. How did you first hear about Web3?

    Aditi: I already had some idea about crypto during the lockdown – I was experimenting with trading and exploring the basics of how blockchains worked. But my actual journey into Web3 development started a year later, around 2022. That’s when I realized there’s a huge difference between knowing crypto as a user and actually building things that power this ecosystem.

    4. What was your first step into the space?

    Aditi: My very first step was as a technical writer for a Web3 company. I learned a lot while breaking down complex topics into articles and docs. Later, I switched into a more hands-on role as a fullstack developer at a startup, which gave me the confidence to actually build projects from scratch. And eventually, I started participating in hackathons, contributing to DAOs, and joining communities like Developer DAO – that’s where things really clicked for me.

    5. What was one big challenge you faced early on?

    Aditi: The biggest challenge was honestly the overwhelming amount of information. Everyone in Web3 talks in acronyms, there are hundreds of tools, and things evolve at lightning speed. It was easy to feel lost or feel like I didn’t belong because there was always someone who seemed to know more. There were moments where I wondered if I was even cut out for it.

    6. What helped you push through?

    Aditi: Two things really helped: a strong desire to learn the basics and community support. I knew I couldn’t skip fundamentals, so I made it a point to dig deeper even if it took extra time. At the same time, being part of communities, hosting workshops, and interacting with like-minded builders encouraged me to keep going. The combination of curiosity and peer support kept me motivated.

    7. What are you most proud of so far in your journey?

    Aditi: A few things stand out:

    • Winning hackathons with projects that actually solved problems.
    • The contributions I’ve made to projects that people found useful.
    • Transitioning from being “just curious” to someone who can actually build and ship.

    Those moments of recognition, whether through a prize or just a “this is cool” from someone, are what I look back on with pride.

    8. Any major failure or learning moment?

    Aditi: Plenty. I’ve had projects that didn’t ship on time, experiments that completely broke, and even ideas that never really took off. But every one of those experiences taught me something – whether it was how to plan better, how to debug smarter, or just how to be okay with things not working out the first time. I think failures in Web3 are just learning curves disguised in fancy clothes.

    9. What advice would you give to someone just starting out in Web3?

    Aditi: Don’t aim to “learn everything” at once – it’s impossible. Pick one area that excites you, whether it’s smart contracts, DAOs, or frontends for dApps, and start there. The rest will fall into place as you go. Also, don’t be afraid to build in public and ask questions. Three months from now, you’ll thank yourself for starting small instead of waiting to be “ready.”

    10. Where can people find or follow your work?

    Aditi: I’m most active on Twitter/X (@aditipolkam) and I share my projects and experiments on GitHub. That’s where you’ll see my latest updates, thoughts, and work.

    11. What is that thing/challenge you would like to change in Web3-Crypto industry?

    Aditi: A lot of companies are building technically sound and fancy products, but not something an average internet user would actually want to use. We need to bridge that gap – simplify UX, focus on real-world use cases, and make Web3 products less intimidating for non-crypto people. Until then, mainstream adoption will remain a buzzword.

    12. Do you want us to cover anything that we missed?

    Aditi: Maybe just this: experimentation is underrated. Most of what I’ve learned came from trying things, breaking things, and iterating — not from following a strict path. If you’re in Web3, don’t wait for perfect conditions. Start experimenting – that’s where the real growth happens.


    From lockdown crypto curiosity to building at Offline Protocol, Aditi’s story is a reminder that Web3 careers aren’t built on perfect preparation. They’re built on willingness to experiment, fail, learn, and ship anyway. Her advice to start small and build in public isn’t just motivational talk, it’s exactly how she built her own career.

    Ready to start your Web3 journey? Follow Aditi on X (@aditipolkam) and GitHub to see what happens when you stop waiting and start building.
    Want to build, learn, and grow in the Web3 space alongside like-minded developers? Join the BlockchainHQ community where builders share knowledge, collaborate on projects, and support each other’s growth. Sign up from here: https://blockchainhq.xyz/auth and follow us on X https://x.com/blockchainhqxyz to become part of our invite-only Telegram community where the real conversations happen.

  • From Stanford Campus to Leading Web3 Developer Relations at Celo

    From Stanford Campus to Leading Web3 Developer Relations at Celo

    A Stanford computer science student walks into an entrepreneur event and gets asked for her Twitter handle. Her response? “What’s Twitter?” Fast forward to today, and she’s now leading developer relations at Celo, one of the most important layer two blockchains focused on real world applications.

    Sophia’s rise in Web3 breaks every normal career path you’ve heard about. While most people enter this space through technical skills or investment backgrounds, she found it through pure curiosity and a willingness to explore new communities online.

    What makes her story remarkable is how not knowing about social media became the gateway to discovering an entirely new industry. From joining her first Web3 groups as a Stanford student to now leading developer relations at a major blockchain platform, her journey shows the surprising ways success can happen in this industry.

    At Celo, Sophia isn’t just managing developer relationships. She’s actively helping one of Ethereum’s most important layer two solutions connect with developers around the world. Her work focuses on real-world adoption and building applications that actually matter to people’s daily lives.

    Her story proves that Web3 success often comes from unexpected places and that community involvement can be just as important as technical skills. Through genuine curiosity about how technology impacts society, she built the foundation for a thriving career in one of the most exciting industries today.

    sophia inforgraphics

    The Interview: Sophia’s Web3 Journey

    1. Tell us a bit about yourself.

    Sophia: I’m Sophia. I am originally from the Bay Area, born and raised here, currently living here, and I am currently the developer relations lead at Celo, which is a layer two on Ethereum, and it’s a frontier chain scaling with real-world adoption and real-world apps.

    2. What were you doing before Web3?

    Sophia: I was still in school, so I went to Stanford for my undergrad. I studied computer science and product design, but I was super into different, like, just, like, building things. So I was always tinkering on different projects and different stuff. I even left school to run a startup full-time, and I was, yeah, just really into, like, figuring out what was cutting edge, what could I build, what could I create. I just loved products and creating and building products. And so I did that a lot while I was in school.

    3. How did you first hear about Web3?

    Sophia: I first heard about Web3 a little bit on Twitter. I was at an event for student entrepreneurs and on a panel for student entrepreneurs and they were talking about there’s a lot of people there that are really into Web3 and the intersection of future of tech. And afterwards they were like, Hey, like, can we follow you on Twitter? And I was like, what’s Twitter? And so I got on Twitter. I started following all these folks and everyone is very like Web3 focused. And I just got started getting involved in communities, a few different ones.

    4. What was your first step into the space?

    Sophia: A Web3 familia I think was one of the first ones and SheFi and yeah I just started really getting involved in some of these like web3 like I think web3 ladies was an early one I I did and it was really cool I learned so much this is like 2021 2022 and I was still in school at the time but it was just so cool getting to learn about all of these programs and then the first thing that actually brought me into the space officially was I went to ETH Denver and visited like I was staying at one of the hacker houses and I was just so impressed that like as a student they would take you to conferences and pay for you to your accommodations and you could win hackathon money it was just such a new eye-opening way for me so that’s definitely what got me originally in this space is just like like paying for travel.

    5. What was one big challenge you faced early on?

    Sophia: I would say, when I first was doing all these hackathons, I was really interested in building, but then as I was getting closer to graduating, I really wanted to figure out what job I wanted to do in the space. And so I set up like all these coffee chats. I would do like three coffee chats a day with people in the industry, just kind of talking about the different opportunities. And at the time, like I knew there was something I was so excited about, but I couldn’t exactly put my finger on what it was. And at the time it was like, oh, you can either do DeFi or NFTs or gaming or payments. and I was like, I don’t know, these specific areas I’m not that interested in but there’s like this intersection between Blockchain and society and how you know how cutting-edge tech is influencing the world that I was so excited about I couldn’t put my finger and articulate what exactly it was

    6. What helped you push through?

    Sophia: Eventually I discovered a Gitcoin and Gitcoin definitely led me down a path that I was really excited about.

    7. What are you most proud of so far in your journey?

    Sophia: Something I’m most proud of so far in my journey is joining Celo and getting to lead the developer relations team at Celo. So it was just so cool getting to go a little bit from like Gitcoin, which is a smaller team, and then I then, through Gitcoin, started leading Public Goods Network, which is also a chain, a blockchain. And I was running a lot of that, and it was a lot smaller. And when I then transitioned to Celo, it was like, it was so cool because like the stakes were a lot bigger.

    8. Any major failure or learning moment?

    Sophia: Honestly leading public goods networks that was one of the first OP stack L twos and I got to lead that and I learned how difficult it is to launch a chain… but the chain did shut down so it was also technically a major failure but I’m glad that it did shut down because I think not all chains need to yeah need to exist you don’t need to launch a change just for the sake of launching a chain.

    9. What advice would you give to someone just starting out in Web3?

    Sophia: I would say join a hackathon. I think that’s one of the most tangible ways to get involved in Web3… There’s so many diverse skill sets that are so appreciated in hackathons now from like marketing to coming up with the product idea to designing the thing to communicating what you’re building. There’s so many aspects and a lot of the coding I see is getting done with AI. So it’s like I feel like there’s less of a technical focus right now in hackathons and more of like a creative focus.

    10. Where can people find or follow your work?

    Sophia: And if anyone wants to find me or follow my work, the best place would probably be on X or on Twitter. My username is @sodofi_ or you can find me on Farcaster on: @sophia

    From not knowing what Twitter was to leading developer relations at one of the most important blockchains around, Sophia’s journey shows that Web3 success can come from the most unexpected beginnings. Her focus on community involvement, hackathon participation, and staying curious about how technology and society connect offers a clear path for anyone looking to build a meaningful career in this space. Through her work at Celo, she continues to prove that understanding people and communities is just as valuable as understanding code.

    Want to build, learn, and grow in the Web3 space alongside like-minded developers? Join the BlockchainHQ community where builders share knowledge, collaborate on projects, and support each other’s growth. Sign up from here: https://blockchainhq.xyz/auth and follow us on X https://x.com/blockchainhqxyz to become part of our invite-only Telegram community where the real conversations happen.

  • Gas Optimization Part 4: Solidity Tips for Cheaper Contracts

    Gas Optimization Part 4: Solidity Tips for Cheaper Contracts

    Every line of your smart contract costs something.

    Some lines cost more than others.

    In this part of our gas saving series, we’ll explore how to write smarter Solidity code that keeps your contract lean and efficient.

    Here are six simple and practical ways to reduce gas costs while writing Solidity smart contracts.

    1. Use payable Only When Needed, But Know It Saves Gas

    In Solidity, a function marked payable can actually use slightly less gas than a non-payable one.

    Even if you’re not sending ETH, the EVM skips some internal checks when the function is marked payable.

    See this example:

    function hello() external payable {}    // 21,137 gas

    function hello2() external {}           // 21,161 gas

    That tiny difference may not seem like much, but across thousands of calls, it adds up.

    • Only use payable when your function is actually meant to accept ETH

    2. Use unchecked for Safe Arithmetic When You’re Sure

    Since Solidity 0.8.0, all arithmetic operations automatically check for overflows and underflows. While this makes contracts safer, it also uses extra gas. When you’re certain that overflow won’t occur, you can use the unchecked keyword to skip these safety checks.

    uint256 public myNumber = 0;

    function increment() external {

    unchecked {

    myNumber++;

    }

    }

    Gas used: 24,347 (much cheaper than using safe math)

    Warning: Use unchecked carefully. Only when you’re confident there’s no risk of overflow.

    3. Turn On the Solidity Optimizer

    The Solidity Optimizer is like a smart helper that cleans up and tightens your compiled bytecode.

    It does not change how your contract works, but it removes waste and makes it cheaper to run.

    If you’re using tools like Hardhat or Remix, always enable the Optimizer before deploying to mainnet.

    4. Use uint256 Instead of Smaller Integers (Most of the Time)

    Smaller types like uint8 or uint16 might look more efficient, but they can cost more gas during execution.

    That’s because the EVM automatically converts them to uint256 behind the scenes.

    So, if you’re not tightly packing them in a struct for storage savings, just use uint256.

    Use smaller types only in structs when trying to save storage space.

    5. Understand Storage Costs: Read + Write Costs Almost Same as Write

    Storage operations are expensive. But here’s something surprising:

    Reading a storage variable before writing to it doesn’t cost much more than writing directly.

    Example:

    • Read + Write = 2,100 (read) + 20,100 (write) = 22,200 gas
    • Write only = 22,100 gas

    That means if your code needs to read before writing, it’s okay, you are not losing much.

    Plan your storage usage wisely. Reuse variables and avoid unnecessary writes.

    Reference: https://ethereum.github.io/yellowpaper/paper.pdf

    6. Use < Instead of <= in Comparisons

    When comparing numbers, use < instead of <=.

    Why? Because:

    • < needs just one check
    • <= takes two checks (a comparison and an extra step to flip the result)

    Fewer steps mean lower gas usage.

    Example:

    for (uint i = 0; i < limit; i++) {

    }

    This small change saves gas on every loop iteration and comparison operation.

    Conclusion

    Gas optimization is about understanding how the EVM works and making informed decisions about your code structure. Each of these techniques might seem to save small amounts of gas individually, but combined and applied across a large contract, they can result in significant cost savings.

    Remember: Always test your optimizations thoroughly. Sometimes gas savings come at the cost of code readability or safety. Strike the right balance for your specific use case.

    Key Takeaways:

    1. Use payable functions when appropriate
    2. Apply unchecked carefully for safe arithmetic
    3. Enable the Solidity optimizer
    4. Prefer uint256 for most variables
    5. Understand storage access patterns
    6. Choose efficient comparison operators

    By implementing these strategies, you’ll create contracts that not only work well but also cost less to deploy and interact with, making them more accessible to users and more profitable for developers.

  • Gas Optimization Part 3: The Foundation of Gas in Solidity and Smart Contract Efficiency

    Gas Optimization Part 3: The Foundation of Gas in Solidity and Smart Contract Efficiency

    You just deployed a smart contract, and it’s costing 98 gas to run a function that does nothing. Literally.

    See for yourself, Why?

    Because even doing “nothing” on Ethereum still means something to the Ethereum Virtual Machine (EVM).

    Welcome to Part 3 of our gas optimization series, where we will look at how gas really works behind the scenes and how you can make your Solidity smart contracts use less gas by removing anything that’s not needed.

    The Building Blocks: OPCODEs Are the DNA of Ethereum

    In Solidity, saving on gas is like saving fuel in your car. To do that, you need to know about OPCODEs – the basic commands that tell Ethereum what to do. They’re the ABCs of Ethereum’s language.

    When you write Solidity code, it doesn’t run directly on the Ethereum network. Instead, it gets compiled into a set of OPCODEs that the Ethereum Virtual Machine (EVM) can understand and execute. Think of it like translating English into machine language that computers can process

    What Are OPCODEs?

    OPCODEs are low level instructions that perform specific operations:

    Arithmetic Operations: ADD, SUB, MUL, DIV for mathematical calculations

    Memory Operations: MLOAD, MSTORE for temporary data storage

    Storage Operations: SLOAD, SSTORE for permanent blockchain storage

    Program Flow: JUMP, JUMPI for conditional logic.

    Cryptographic Functions: SHA3, ECRECOVER for security operations

    Contract Interactions: CALL, DELEGATECALL for inter-contract communication

    And here’s the catch:

    Each OPCODE consumes gas, and some cost way more than others.

    Pro Tip:

    You can see the full list of OPCODE gas costs here: ethereum.org/en/developers/docs/evm/opcodes

    The Secret Code: Function Selectors

    Here’s something that might surprise you: when you compile your Solidity code into bytecode, the names of your functions don’t actually show up in the final assembly output. Instead, what ends up on the Ethereum network is something like a secret code called function selectors

    How Function Selectors Work

    Function selectors are created by taking the first four bytes of the hash of the function’s signature. Let’s look at a real example:

    function doNothig() external pure {}

    After compilation, this becomes:

    46aad107

    So when someone sends a transaction to your contract, they don’t send the name doNothig(),they send the selector 0x46aad107.

    That’s how the EVM knows which function to run, without storing long names on-chain.

    Gas Optimization Tips Every Developer Should Know

    1. Keep It Light

    The less code you deploy, the less gas you’ll use during deployment. Think of it as packing light for a flight – every extra byte costs money.

    Code size optimization strategies:

    • Remove unnecessary functions and variables
    • Use libraries for common operations instead of duplicating code
    • Implement proxy patterns for upgradeable contracts
    • Strip out debugging code and comments in production

    Real impact: A 1KB reduction in contract size saves approximately 200,000 gas units during deployment

    2. Choose Wisely: OPCODE Selection

    Certain commands are cheaper than others. Picking the right ones is like choosing a budget airline over a luxury carrier.

    Cost-effective choices:

    • Some instructions (like ADD) cost less than others (like SSTORE).
    • Store fewer variables
    • Avoid unnecessary require checks
    • Minimize state changes

    3. Pack Data Tight: Transaction Data Optimization

    The more data you send in a transaction, the more you spend. Keep your transaction data lean.

    Data packing techniques:

    • Use struct packing to fit multiple variables in single storage slots
    • Compress arrays and use fixed-size arrays when possible
    • Batch multiple operations to reduce transaction overhead
    • Use events instead of storage for data that doesn’t need to be queried on-chain

    4. Minimize Memory Use

    Memory is temporary, but still costs gas.

    Avoid creating new memory variables when not required.

    Use calldata instead of memory for function inputs when possible

    5. Be Smart About Storage

    Storage is the most expensive operation.

    • Only write to storage if you must
    • Use events to log non-critical data instead of storing it
    • Don’t overwrite storage values unless necessary

    Every time you write to SSTORE, you’re paying a premium.

    The Compound Effect

    A little bit of gas saved on every transaction can add up to significant savings over time. If your contract processes 1,000 transactions per day and you save 500 gas per transaction, that’s 500,000 gas units daily – potentially saving hundreds of dollars monthly at current gas prices.

    Understanding OPCODEs and function selectors is just the beginning. In Part 4, we’ll explore advanced Solidity techniques that can dramatically reduce gas consumption

  • Gas Optimization Part 2: Timing Strategies and Batch Processing

    Gas Optimization Part 2: Timing Strategies and Batch Processing

    You’ve learned what gas fees are and how they’re calculated. Now comes the practical part: how to actually save money on every transaction you make. The difference between a novice and an expert Ethereum user often comes down to understanding when and how to execute transactions efficiently.

    Haven’t read Part 1 yet? Check out our introduction to gas fees and how they work to understand the fundamentals before diving into these optimization strategies.

    Let’s explore the proven strategies that can cut your gas costs by 50-90% without compromising transaction security or speed

    Strategy 1: Master the Art of Timing

    Weekends: Saturday and Sunday typically see 20-30% lower gas fees as business activity decreases.

    Off-peak hours: Between 2 AM and 6 AM UTC, when both American and European users are asleep, gas prices often drop significantly.

    Avoid these high-traffic periods:

    • NFT mint launches
    • Major DeFi protocol updates
    • Market crash periods (panic selling drives up demand)
    • Weekday mornings (8-10 AM UTC)

    You can use trackers like:

    Pro tip: Set up gas price alerts on your phone. When prices drop below your target threshold, that’s your window to execute pending transactions.

    Strategy 2: Batch Processing

    Why send 10 separate transactions…

    When you can send one batch?

    Batching reduces overhead, saves time, and lowers gas.

    Let’s explore 3 Ethereum standards that enable powerful batching:

    1) ERC-3005: Batched Meta Transactions – https://eips.ethereum.org/EIPS/eip-3005

    This standard lets users combine multiple actions into one meta transaction.

    Example:

    1. Approve token
    2. Swap on DEX
    3. Send output to wallet

    All in one call, reducing gas and relayer fees.

    Great for:

    1. Wallet apps
    2. Gasless UX
    3. Relayer-backed platforms

    2) ERC-7821: Minimal Batch Executor –  https://eips.ethereum.org/EIPS/eip-7821

    This one’s about delegations and shared execution.

    Think of it like batching multiple on-chain delegations, such as:

    • Voting
    • Staking
    • DAO participation

    With atomic execution, if one part fails, nothing gets through so it keeps safe and predictable.

    Perfect for:

    • DAO tools
    • Governance app
    • Delegation-heavy protocols

    Example scenario: You want to withdraw from a liquidity pool, swap the tokens, and deposit them into a yield farming protocol. ERC-7821 ensures all these operations happen atomically, preventing scenarios where only part of your strategy executes

    3) ERC-4393: Batch Micropayments – https://eips.ethereum.org/EIPS/eip-4393

    When you need to make multiple small payments, ERC-4393 shines. This standard enables multiple tips or payments in a single transaction call.

    Use case: Tipping multiple content creators or making several small purchases. Instead of paying gas fees for each micropayment, you pay once for the entire batch

    Strategy 3: Wait for gas to go down

    Gas prices go up and down every twelve seconds based on how congested Ethereum is. When gas prices are high, waiting just a few minutes before making a transaction could see a significant drop in what you pay.

    Strategy 4: Use Layer 2 Solutions

    Layer 2 solutions like zkSync, Arbitrum, and Optimism reduce gas fees by up to 95%. By bundling a large number of transactions together, these solutions reduce the number of on-chain transactions.

    Popular options:

    • Arbitrum
    • Optimism
    • Base
    • Polygon (PoS)

    Many dApps are now L2-ready. Just bridge your ETH once, and you’re good to go.

    Wrap-up

    Ethereum gas fees aren’t going away, but you can outsmart them with:

    1. Good timing
    2. Layer 2 networks
    3. Batched transactions using ERC-3005, ERC-7821, and ERC-4393
    4. Wait for the gas to go down

    What’s next?

    While timing and batching strategies can dramatically reduce your transaction costs, the next frontier in gas optimization lies in smart contract efficiency. In Part 3, we will explore advanced Solidity techniques that developers use to minimize gas consumption at the code level.

  • Gas Optimization Part 1: Understanding Ethereum Gas Fees

    Gas Optimization Part 1: Understanding Ethereum Gas Fees

    “I paid $62 just to send $100. What?”

    That’s the kind of reaction many new users have after making their first Ethereum transaction during peak congestion.

    No NFTs. No DeFi. Just a simple ETH transfer.

    Yet the gas fee was more than half the value of the transaction.

    And they thought it was a bug.

    But it wasn’t.

    It was Ethereum being busy.

    Welcome to the world of gas fees.

    What Is Gas, Really?

    If you’ve ever driven a car, you already understand gas.

    Think of your Ethereum transaction as a car trip. To drive (process your transaction), you need fuel, and on Ethereum, that fuel is called Gas.

    Just like fuel powers a car, gas powers your transaction on the Ethereum network.

    But there’s a catch: The busier the road, the higher the fuel price.

    So when the Ethereum network is crowded (say, during a hyped NFT mint), gas prices shoot up because everyone’s trying to get their transactions through.

    Why Gas Prices Change

    Back to our highway example:

    If traffic is light, fuel is cheap, and if traffic is jammed, fuel costs more to cut through

    Ethereum works similarly.

    You can pay a higher gas price to get your transaction picked up faster by validators

    Or you can set a lower price and wait.

    Understanding the Components

    Gas Limit

    This is the maximum amount of gas you’re willing to use.

    For simple ETH transfers, it’s usually 21,000.

    Gas Price

    This is how much you’re willing to pay per unit of gas, measured in Gwei.

    Gas Usage:

    This is the actual amount of gas consumed by your transaction. It’s often the same as your gas limit for simple transactions, but complex operations might use less than the limit you set.

    Breaking Down Gas Fees: A Real Example:

    • Gas Limit = 21,000
    • Gas Price = 35.06 Gwei
    • ETH Price = $3,492.21

    Step 1: Calculate Gas Fee in ETH

    21,000 × 35.06 / 1,000,000,000 = 0.000736 ETH

    Step 2: Convert to Dollars

    0.000736 × 3,492.21 = $2.57

    So, the fee for that simple transaction is about $2.57.

    But when the network gets congested, gas prices might 10x,  and that’s how people end up paying $50+ just to send ETH.

    The Game-Changer: EIP-1559

    In August 2021, Ethereum introduced EIP-1559, which revolutionized how gas fees work. Instead of the old auction-style system where users had to guess appropriate gas prices, EIP-1559 brought predictability and efficiency.

    How EIP-1559 Works

    The new system introduces several key components:

    Base Fee: This is a fixed price per unit of gas that the network automatically adjusts based on demand. Here’s the interesting part: this base fee gets burned (destroyed), permanently removing ETH from circulation.

    Max Fee: The maximum amount you’re willing to pay for the transaction. This acts as your safety net.

    Max Priority Fee: The tip you’re willing to give to miners to prioritize your transaction.

    A Real EIP-1559 Example

    Let’s say you’re making a transaction with these parameters:

    Base Fee: 70 Gwei

    Max Fee per Gas: 90 Gwei

    Max Priority Fee per Gas: 15 Gwei

    Here’s what happens:

    1. 70 Gwei gets burned (the base fee is destroyed)
    2. Miners receive 15 Gwei (your full priority fee since Max Fee – Base Fee = 20 Gwei, which is higher than your 15 Gwei priority fee)
    3. You get 5 Gwei refunded (90 – 70 – 15 = 5 Gwei back to your wallet)

    This system eliminates the guesswork. You know exactly what you’ll pay upfront, and any excess gets refunded automatically.

    Looking Ahead

    Gas optimization isn’t just about understanding current fees. It’s about developing strategies to minimize costs while maintaining transaction reliability. In the next part of this series, we’ll dive into practical techniques for optimizing your gas usage, including timing strategies, transaction batching, and smart contract optimization tips.

    The key takeaway? Gas fees might seem complex, but they follow predictable patterns. Once you understand these patterns, you can navigate the Ethereum network like a pro, saving money and avoiding the frustration of failed transactions.

    Remember: every Gwei saved is money back in your pocket. And in the world of DeFi and NFTs, where you might make dozens of transactions per month, those savings add up quickly.

  • They Lost Millions by Clicking ‘Sign’ – Here’s How to Never Make That Mistake

    They Lost Millions by Clicking ‘Sign’ – Here’s How to Never Make That Mistake

    Picture this: You’re the treasurer of a major crypto exchange. Your phone buzzes with a notification – another routine transaction needs approval. You glance at your screen, see familiar addresses, and click “approve” without a second thought. Within minutes, millions of dollars vanish into thin air.

    This isn’t fiction. This exact scenario played out when Bybit, one of the world’s largest cryptocurrency exchanges, fell victim to a sophisticated hack executed by North Korean cybercriminals. The culprit? A signer who didn’t fully verify a transaction, leading to a critical Safe UI vulnerability that drained millions from their multi-signature wallet.

    The harsh reality is that even the most secure wallet setups can crumble with one careless click. But here’s the good news: these disasters are completely preventable when you know what to look for.

    Don’t want to be the next victim?

    Let’s walk through how to verify calldata, use multi-sig safely, and pick the right wallet for your level.

    The Wallet Hierarchy: Choosing Your Guardian

    Before diving into verification techniques, let’s address the elephant in the room: which wallet should you even use?

    Total Beginner with Small Amounts: Start with custodial wallets or keep funds on reputable exchanges. Yes, “not your keys, not your crypto” is true, but losing $100 to exchange risk beats losing $100 to your own mistakes.

    Beginner with Small Money: Browser wallets like MetaMask or Phantom work well. They’re user-friendly and perfect for learning the ropes with amounts you can afford to lose.

    Intermediate Users with Medium Amounts: Hardware wallets like Ledger or Trezor become essential. They keep your private keys offline and away from internet threats.

    Intermediate Users with Large Amounts: Combine multi-signature wallets with hardware wallets. This creates multiple checkpoints that hackers must breach simultaneously.

    Advanced Users with Significant Holdings: Multi-signature wallets with social recovery, or custom solutions. At this level, you’re building Fort Knox for your digital assets.

    For wallet comparisons and security audits, check out walletscrutiny.com – it’s like a Consumer Reports for crypto wallets.

    Hot vs Cold Wallets

    Hot wallets stay connected to the internet (MetaMask, Phantom, and mobile apps). They’re convenient for daily transactions but vulnerable to online attacks.

    Cold wallets remain offline (Ledger, Trezor hardware devices). They’re like keeping cash in a physical safe, much harder to steal remotely.

    Important:

    Even a cold wallet becomes hot if you connect it to a Safe multi-sig UI!

    Always be aware of when you’re online vs offline

    Verifying Simple Transactions: Your First Line of Defense

    When using MetaMask or similar wallets, you’ll sometimes see transaction details that look like gibberish. Don’t panic,  here’s how to decode them:

    Check These Three Things:

    1. Estimated changes – What’s actually moving in and out of your wallet
    2. The “to” address – Where your money is going
    3. Hash data – The first 4 bytes reveal the function being called

    For example, if you see “0xa9059cbb” in your transaction data, you can decode it using Cast (a developer tool):

    cast sig “transfer(address,uint256)”

    This returns the function selector you can compare against your transaction. If they match, you’re calling a transfer function. If they don’t match, stop immediately.

    To verify the specific parameters of a transfer:

    cast calldata-decode “transfer(address,uint256)”

    This shows exactly where your tokens are going and how many.

    Multi-Sig Transactions: Where Things Get Complicated

    Multi-signature wallets require multiple people to approve transactions before they execute. Think of it like a shared bank account where both you and your spouse need to sign checks for large purchases

    Critical Point: A signature request is NOT the same as a transaction request. You’re not sending money yet, you’re just adding your approval to a pending transaction.

    How to Verify a Multi-Sig Transaction

    Step 1: Install the Right Tools Get Cyfrin’s Safe_hashes tool from GitHub

    https://github.com/Cyfrin/safe-tx-hashes?tab=readme-ov-file#curl

    This tool decodes Safe transactions into a human readable format.

    Step 2: Run the Verification Command

    safe_hashes –address –network –nonce

    If no transaction appears, use –untrusted mode in above command

    Step 3: Manual Verification (Advanced) For complete independence from APIs, use Cast:

    cast calldata “approve(address,uint256)”

    Then verify with Safe hashes:

    safe_hashes –address –network –nonce 2 –data –offline –to

    The Golden Rules That Could Save Millions

    Never sign and execute simultaneously. Some wallets try to streamline this process, but convenience is the enemy of security.

    Watch for operation codes. If you see “operation = 1” in your transaction, you’re looking at a DELEGATECALL – essentially giving another contract permission to act with your wallet’s full authority. This is extremely dangerous and should only be used in very specific circumstances.

    Always verify these three elements before any signature:

    • The destination address (where is this going?)
    • The function selector (what action is being performed?)
    • The value or amount (how much is involved?)

    Why This Matters More Than Ever

    The Bybit hack wasn’t an isolated incident. Similar attacks happen regularly because people skip verification steps. The difference between a secure transaction and a devastating hack often comes down to spending 30 seconds to verify what you’re actually signing.

    Remember: in the world of cryptocurrency, there’s no “undo” button. Once a transaction is confirmed on the blockchain, it’s permanent. The few minutes you spend verifying could be the difference between protecting your assets and reading about your loss in tomorrow’s crypto news.

    The tools and techniques outlined here aren’t just for crypto professionals – they’re for anyone who values their digital assets enough to protect them properly. Start with the basics, build good habits, and gradually level up your security practices as your holdings grow.

    TL;DR

    1. Pick the right wallet for your level
    2. Always verify the transaction before signing, especially calldata
    3. Never trust the UI blindly
    4. Use Safe_hashes or Cast for decoding
    5. Multi-sig ≠ automatic safety

    One wrong click can empty your wallet. Take 30 seconds and verify,  your future self will thank you.

  • From First Principles to First dApp: Learn Blockchain Dev in 2025

    From First Principles to First dApp: Learn Blockchain Dev in 2025

    Have you ever used an app and thought… “Why am I giving away all my data just to use this?”

    Or maybe you’ve wondered:

    Why can banks freeze your money without warning? Why are the games you buy online not really yours? Why do the same tech companies control everything we do?

    The answer lies in one word: trust.

    Or rather, the lack of it.

    That’s where blockchain steps in.

    In 2025, blockchain isn’t just about Bitcoin or NFTs anymore. It’s becoming the foundation for a new kind of internet, one that doesn’t ask you to trust companies, platforms, or middlemen blindly.

    But here’s the problem: most people are stuck on the sidelines.

    They hear the buzzwords. They see the headlines.

    But they don’t know where to start.

    This guide fixes that.

    Whether you’re a student, a curious developer, or someone who just wants to build something real, this is your step-by-step path.

    Real skills. Real tools. A mindset that helps you keep going.

    Let’s start with what really matters, and  the why behind it all.

    We’re still early.

    Ethereum co-founder Vitalik Buterin recently said:

    “There are still many unsolved problems in scalability, privacy, user experience… We need more developers focused on these layers.”

    The reality is this: the blockchain ecosystem is not “done.”

    It’s still being built, and it needs builders.

    Whether it’s making DeFi safer, improving wallets, exploring zero-knowledge proofs, or helping people own their digital identity, there is a real, growing need for smart developers who can understand and ship in this space.

    Why Blockchain? Start With First Principles

    Before we talk about coding, let’s talk about why blockchain exists at all. Because if you don’t understand the “why,” you’ll struggle with the “how.”

    Imagine you want to send money to your friend in another country. Right now, you need banks, clearinghouses, and payment processors. Each one takes a cut. Each one adds delay. Each one becomes a potential point of failure.

    What if you could send that money directly? No middlemen. No extra fees. No waiting three business days for “processing.”

    That’s blockchain’s core promise: removing intermediaries from systems that have always needed them.

    But money is just the beginning. What about voting systems where everyone can verify results? Supply chains where you can track products from farm to table? Digital identities that you actually own?

    Public vs Private Blockchain:

    You’ll come across different types of blockchains. They are not all the same.

    Public Blockchains

    These are open to everyone. Anyone can read, write, and build.

    Examples: Ethereum, Solana, Bitcoin

    Private Blockchains

    These are permissioned. Only selected people can participate.

    Examples: Hyperledger, Fabric

    Many people assume private blockchains are more secure because they offer control. But as Sandy Kaul rightly said:

    “The fewer nodes and simpler security models in private chains make them more vulnerable than public chains.”

    Serge from Chainlink added:

    “All private blockchains will eventually have to connect to public blockchains. Their liquidity and relevance will shrink.”

    That’s why most developers today are building on public chains,  it’s where the action is, and where the opportunities are

    Choosing Your Lane: Types of Chains

    Not all blockchains are created equal. Each has different strengths, different communities, and different opportunities.

    • Ethereum is the most widely used and secure. It’s great for learning and building, but can be slow and expensive during high traffic.
    • Solana is super fast and cheap, best for real-time apps and games. It uses a different coding language (Rust) and has fewer validators.
    • Polygon is a faster, cheaper version of Ethereum. It uses the same tools and is ideal for testing or scaling Ethereum apps.
    • Avalanche offers high speed and flexibility, letting you even create your own custom blockchains.
    • Arbitrum and Optimism are “Layer 2” networks built on top of Ethereum to make it faster and cheaper, using the same code.

    Each has strengths. Start with Ethereum to learn the basics, then explore others as you grow.

    Pick a Niche and Stick (For Now)

    You don’t need to learn every chain.

    Pick one and go deep.

    Examples:

    • Ethereum → Use Solidity + Foundry or Hardhat
    • Solana → Use Rust or JavaScript with Anchor
    • Aptos/Sui → Learn Move language
    • Starknet/Polygon zkEVM → Explore ZK circuits

    Choose one based on what excites you.

    DeFi, NFTs, ZK proofs, gaming, DAOs,  pick your playground

    Core Concepts Before Coding

    Before you write your first smart contract, make sure you understand these fundamental concepts:

    Cryptographic Hashing is how blockchain ensures data integrity. Every block contains a hash of the previous block, creating an unbreakable chain.

    Digital Signatures prove that transactions are authorized by the rightful owner of an address.

    Consensus Mechanisms are how the network agrees on what’s true. Proof of Work, Proof of Stake, and other algorithms each have different trade-offs.

    Gas is the fuel that powers blockchain operations. Every computation costs gas, and understanding this is crucial for writing efficient code.

    Smart Contracts are programs that run on the blockchain. They execute automatically when conditions are met.

    These aren’t just academic concepts. They affect every line of code you’ll write. A smart contract that doesn’t consider gas costs might be too expensive to use. A DeFi protocol that doesn’t understand consensus mechanisms might have security vulnerabilities.

    Smart Contract Security Essentials

    Here’s something that might surprise you: smart contract security is still a mess.

    Samczsun, one of the most respected security researchers in the space, noted that “almost every ticket that we got was a smart contract hack.” This isn’t ancient history. This is happening right now.

    What does this mean for you as a developer? Opportunity. The ecosystem desperately needs developers who understand security.

    Learn about common vulnerabilities like reentrancy attacks, integer overflow, and access control issues. Understand how to use tools like OpenZeppelin’s secure contract libraries. Practice writing tests that try to break your code.

    Security isn’t something you add at the end. It’s something you build in from the beginning.

    Gas Optimisation: Write Efficient Code

    Every operation on the blockchain costs gas. Users pay these costs. Write inefficient code, and nobody will want to use your application.

    Learn how to:

    • Pack storage variables
    • Minimize external calls
    • Use view and pure functions

    This isn’t premature optimization. This is fundamental to blockchain development. A function that costs $50 in gas fees won’t get used, no matter how clever the code is.

    And so on.

    Take a course on this and start learning these techniques

    Don’t Just Learn. Ship.

    This is the most important point.

    You will learn more by building one simple dApp than by reading 50 articles.

    Even if it’s small,  a todo list on-chain, a voting contract, or a basic NFT mint page just ship something.

    Break things. Fix them. Ask questions. Improve.

    Where Are the Opportunities? Jobs, Hackathons, Communities

    Blockchain is not just a tech stack. It’s a community.

    To grow fast:

    • Join hackathons: ETHGlobal, DoraHacks, Encode, Devfolio
    • Explore job boards: Web3.career, CryptoJobsList, Remote3
    • Hang out in Discords and Telegrams of your favorite protocols
    • Learn from:: Cyfrin Updraft, Alchemy University, Speedrun Ethereum and more

    The earlier you show up and ship, the faster you’ll stand out.

    Stay in the Game: Learn in Public

    Building in public is a superpower in the blockchain space. Share your learning journey. Tweet about the bugs you’re fixing. Write about the concepts you’re understanding. Stream your coding sessions.

    This isn’t just about personal branding. It’s about accountability. When you commit to learning in public, you’re more likely to stick with it. You get feedback from the community. You build relationships with other developers.

    Balaji Srinivasan, former CTO of Coinbase, talks about blockchain as the infrastructure for future digital societies. He’s working on projects that use blockchain to create new forms of governance and community. This vision shows blockchain development is evolving beyond financial apps into building tools for entire digital civilizations.

    Checklist: What You Should Have Built After 30 Days

    By the end of your first month, aim to have:

    • Fundamentals of Blockchains
    • A wallet setup (Metamask or others)
    • At least one deployed smart contract
    • A frontend that interacts with your contract
    • A GitHub repo or site link to share your project
    • A basic understanding of gas and security

    A note of 5 things you’d do differently next time

    Blockchain Learning Loop: (Read → Code → Break → Fix → Share → Repeat)

    Learning blockchain development isn’t linear. It’s cyclical. Here’s the loop that works:

    Read documentation, tutorials, and other people’s code. Don’t just skim. Really understand what’s happening.

    Code your own version. Start with copy-paste if you need to, but make sure you understand every line.

    Break things on purpose. What happens if you change this parameter? What if you remove this check? Breaking things teaches you how they work.

    Fix the problems you created. This is where real learning happens. When you fix a bug, you understand the system better.

    Share what you learned. Write about it. Talk about it. Teach someone else.

    Repeat with something more complex.

    This loop works because it combines multiple learning styles. You’re reading, writing, experimenting, and teaching. Each reinforces the others.

    Staying Current and Continuous Learning

    Blockchain evolves fast. Stay up to date by:

    • Subscribing to developer newsletters (Week in Ethereum, Starknet Weekly)
    • Watching talks from ETHGlobal, Devconnect, ZK Summit
    • Reading protocol docs regularly
    • Following devs who ship: Austin Griffith, Patrick Collins, 0xfoobar, and others

    Keep your learning tight. Build in the open. And don’t stop.

    Final Thoughts

    You don’t need to be a genius to become a blockchain developer.

    You just need a clear roadmap, a community, and the courage to start.

    There’s never been a better time to build.

    The tools are better. The community is bigger. The problems are real.

    Blockchain isn’t just about finance anymore.

    It’s about rewriting how the internet works,  and you can be part of it.

    Ready to start your journey?

    Check out our Resource Page( https://blockchainhq.xyz/resources ) to find everything from beginner tutorials to advanced guides

    The blockchain ecosystem is waiting for what you’ll build next🫡

  • Rishikesh Kale: The Web3 Native Who Never Looked Back

    Rishikesh Kale: The Web3 Native Who Never Looked Back

    While his college friends were chasing traditional job placements with attractive packages, Rishikesh Kale made a decision that would define his entire career. He chose to stay in Web3, even when the path seemed uncertain and the resources were scarce. Today, as a Developer Advocate at FIL-B, his story proves that sometimes not going all in on a technology you believe in is the bigger risk, a risk that could mean missing out on the opportunity to shape an emerging field.

    Unlike many who transitioned into Web3 from other careers, Rishikesh Kale took a different path. He started with blockchain right after college, making Web3 not just a career choice but his only industry focus. From winning coding competitions with creative dApps to learning at a time when resources were scarce, his journey reflects what it truly means to grow alongside an emerging technology.

    Based in Nagpur, India, Rishikesh has seen Web3 change from a space where people had to learn coding through games like CryptoZombies to today’s world full of tools and chances. His experience gives a special view of building a career in blockchain from scratch, especially for those who choose to go deep instead of just trying it out.

    This talk with Rishikesh shows the mindset needed to do well in Web3’s early days, why patience matters in a space often linked with quick wins, and real advice for newcomers finding their way through today’s opportunities. His story proves the power of not giving up and the rewards that come to those who truly believe in the future of decentralized technology.

    Rishikesh Kale: The Web3 Native Who Never Looked Back

    The Interview: Rishikesh Kale on His Web3 Journey

    1. Tell us a bit about yourself.

    Rishikesh Kale: I’m Rishikesh Kale, and I’m based in Nagpur, India. Currently, I’m working as a Developer Advocate at FIL-B.

    2. What were you doing before Web3?

    Rishikesh Kale: My journey into Web3 began right out of college; it was my first love and has remained so ever since. I didn’t have a prior career outside of this space.

    3. How did you first hear about Web3?

    Rishikesh Kale: I first heard about Blockchain through my brother. After his introduction, I delved deeper by reading various articles and documentation online.

    4. What was your first step into the space?

    Rishikesh Kale: My real entry point was a hackathon during my college days. My friends and I developed a dApp called Vidhira, a social media platform designed for creators and artists. We ended up winning the hackathon and taking first place!

    5. What was one big challenge you faced early on?

    Rishikesh Kale: One of the biggest challenges I faced early on was the limited availability of educational resources. This was back when Ganache and Remix IDE were still relatively new, and there weren’t many videos or beginner-friendly materials. I largely learned Solidity by playing the CryptoZombies game and then continued my learning from there.

    6. What helped you push through?

    Rishikesh Kale: What kept me going was the desire to implement what I was learning and find opportunities. While waiting for internship opportunities, which felt like a long tunnel, I kept building and participating in more hackathons, knowing that the efforts would pay off eventually.

    7. What are you most proud of so far in your journey?

    Rishikesh Kale: I’m most proud of showing up and not turning back. It was tempting to choose a traditional job when my friends were getting attractive campus placements. However, I chose to stick with blockchain and remained patient, and I’m proud of that decision.

    8. Any major failure or learning moment?

    Rishikesh Kale: Every hackathon has been a significant learning moment for me. Instead of just “bounty hunting,” I always tried to build on new protocols. This approach, while challenging in terms of ideation and execution, taught me a tremendous amount and was a great learning process.

    9. What advice would you give to someone just starting out in Web3?

    Rishikesh Kale: If you’re just starting in Web3, patience is key. It’s rare to hit a jackpot early on. There’s a misconception that Web3 is a space where you can earn a lot of money quickly. While it will definitely pay off one day, it’s not necessarily from day one. Focus on having a solid learning and building journey, and opportunities will follow.

    10. Where can people find or follow your work?

    Rishikesh Kale: You can find or follow my work on Twitter/telegram/linkedIn: @callMeRishhh

    Rishikesh Kale’s story reminds us that Web3 isn’t just about quick financial gains or following the latest trends. It’s about building something meaningful, staying patient during uncertain times, and believing in the long-term vision of decentralized technology. His journey from a college student learning Solidity through games to a Developer Advocate at FIL-B shows that consistent effort and genuine curiosity can lead to remarkable opportunities.

    For those considering a similar path, Rishikesh’s experience offers a valuable lesson: the space rewards those who show up consistently, keep building, and resist the temptation to chase shortcuts. In a world where everyone is looking for the next big opportunity, sometimes the biggest opportunity is the one you’re already working on.

    Ready to start your own Web3 journey? Follow Rishikesh’s approach: start building, participate in hackathons, and focus on learning rather than immediate returns. Connect with him on Twitter @callMeRishhh to learn more about his work and get insights into the developer advocate role in Web3.

    Want to build, learn, and grow in the Web3 space alongside like-minded developers? Join the BlockchainHQ community where builders share knowledge, collaborate on projects, and support each other’s growth. Sign up from here: https://blockchainhq.xyz/auth and follow us on X https://x.com/blockchainhqxyz to become part of our invite only Telegram community where the real conversations happen

  • Meet Patrick Collins: Securing Web3, Educating and Onboarding Builders

    Meet Patrick Collins: Securing Web3, Educating and Onboarding Builders

    In the fast-changing world of Web3, some people really stand out. They bring clear ideas, deep knowledge, and a true passion for building a better digital future. Patrick Collins is definitely one of these important people. As a top smart contract engineer, a dedicated teacher, and a key leader at Cyfrin, he’s not just watching new digital technologies grow, he’s actively helping to shape them.

    Patrick’s path into Web3 shows how important it is to be curious, keep going when things are tough, and truly want to make this new area safer and easier for everyone to use. From his early days figuring out how to put information onto the blockchain to his current work leading the way in blockchain security and teaching, his journey offers valuable lessons for both experienced people and those just starting out.

    At Cyfrin, Patrick and his team are working on some of the biggest challenges in Web3 today. They make sure smart contracts are strong and reliable, and they help train the next group of skilled developers and security experts. Their work not only protects big companies in the industry but also helps individuals through thorough, often free, learning programs like Cyfrin Updraft.

    This interview is a special chance to hear directly from Patrick Collins. We’ll talk about his personal story, the important moments that shaped his career, and his honest advice for navigating the exciting but sometimes difficult world of Web3. Get ready to learn from someone who truly believes in the power of decentralized technology and is working hard to make it all happen.

    Meet Patrick Collins: Securing Web3, Educating and Onboarding Builders

    The Interview: Patrick Collins on His Web3 Journey

    1. Tell us a bit about yourself.

    Patrick Collins: I’m Patrick Collins. I’m from MA in the United States. I’m working on making Web3 more secure with security and educational initiatives as a part of Cyfrin.

    2. What were you doing before Web3?

    Patrick Collins: Before Web3, I worked as a software support engineer at an asset manager, and as a Devrel at a stock data company.

    3. How did you first hear about Web3?

    Patrick Collins: I heard about Web3 first when I had heard about Chainlink and how they wanted to “get financial data on chain” which sounded bizarre to me. At the time, crypto was just like “bitcoin” and it didn’t make sense to me to “put data into bitcoin.”

    4. What was your first step into the space?

    Patrick Collins: I went to the ETH Denver hackathon and spent the hackathon learning Solidity.

    5. What was one big challenge you faced early on?

    Patrick Collins: Getting started in general was confusing. I didn’t know who to trust, what was good vs bad Web3, there were so many competing narratives. One in particular was if using “send”, “transfer”, or “call” on moving ETH. Why are there 3 functions?

    6. What helped you push through?

    Patrick Collins: My curiosity more or less. I thought the tech was sooooo cool and I just wanted to learn more.

    7. What are you most proud of so far in your journey?

    Patrick Collins: Cyfrin. Everything we’ve done so far, and everything we are going to do. We not only secure some of the largest companies in the industry, but we onboard some of the best people through our security education, and make the whole industry better in safer ways.

    8. Any major failure or learning moment?

    Patrick Collins: I fail all the time. Get better and move on. One of my favorite learnings was, I had some feedback that my videos were obnoxious and ruining the brand of the product I was promoting. That I needed to be more boring ‘cuz “devs like boring.” So I made two videos of the same content, one “boring” and one ridiculous. To this day, the ridiculous one has performed over 20x better than the boring one.

    9. What advice would you give to someone just starting out in Web3?

    Patrick Collins: Go to Cyfrin Updraft, compete on CodeHawks, and you’ll be set up for success.

    10. Where can people find or follow your work?

    Patrick Collins: X – @PatrickAlphaC and @patrickalphac on YouTube.

    11. Any advice would you like to share with builders and learners?

    Patrick Collins: Understand why you want to do what you do. Write it down. So that when things get hard, you can remember why you’re doing it and push through.

    It’s truly inspiring to see how Patrick Collins started his journey in Web3. His dedication to sharing knowledge through educational resources has helped thousands of individuals kickstart their careers in Web3. Furthermore, his ongoing efforts are adding immense value to the Web3 space by assisting companies in making their products secure and, as always, helping many across the globe with Cyfrin Updraft’s educational initiatives.