Eunice (@Unixfundz) header
Eunice (@Unixfundz) profile picture

Blockchain Developer in a jiffy 🧑‍💻 AI Prompt Engineer Technical Writer

Abuja, Nigeria
Joined January 2021
I genuinely enjoy being a woman. The beauty, the confidence, the little details, the feminine energy… chef’s kiss 😭❤️
2
3
70
Woke up. Chose Solidity. Let's grind 🧠🚀 Building a lottery smart contract while following along with @PatrickAlphaC and the @CyfrinUpdraft course. The learning journey just keeps getting better 💻🔥 #Web3 #WomenInTech #Ethereum #Solidity #Blockchain
3
113
Joining the @shefiorg family as a Season 15 Scholar! Can't wait to grow, learn, and contribute to a community where the future of finance is feminine. Here's to breaking barriers and creating a new future in web3! Thank you @shefiorg! #shefischolar
2
80
From Newbie to Builder I’m beyond excited to share that my project, WEB3 NEWBIE ODYSSEY has been selected for the Blockops Builder’s Program! @BlockopsX What started as my personal journey to understand Web3 is now becoming a creative gateway to help others especially women step into this space with confidence. Here’s to learning, building, and onboarding the next generation of Web3 explorers 🌍✨ Thank you for the opportunity @BlockopsX #Web3 #NFT #Blockchain #WomenInWeb3 #Builders
3
1
7
131
Foundry Series (Part 3) – Core Components 1/ Part 3 of my Foundry Series is here 🛠️ Let’s talk about the 4 core components of Foundry: 👉 Anvil 👉 Forge 👉 Cast 👉 Chisel What they mean, what they do, and why they matter 👇
1
1
58
Day 70-75 of My Blockchain Journey Foundry Series (Part 2) — RPCs: The Invisible Bridge Between Developers and Blockchains When I first started learning blockchain development, I thought tools like Foundry, Hardhat, or even MetaMask somehow had “direct” access to Ethereum. Write some code, run a command, and boom — it’s on the blockchain. But then I discovered something crucial: none of these tools can talk to Ethereum on their own. They all rely on something called an RPC (Remote Procedure Call) — a gateway that connects us, the developers, to the blockchain network. WHAT IS AN RPC? Think of Ethereum as a giant library. It has books (blocks), shelves (chains of blocks), and new books being added every few seconds (new blocks). But here’s the problem: 🔹 The library is too big to carry around. 🔹 You can’t just walk in and grab books without knowing where to look. So instead, you ask a librarian for help. That “librarian” in blockchain is the RPC endpoint. It takes your request (e.g., “what’s the balance of address 0x123?”) and goes into the blockchain to fetch the answer. Or if you want to write, it takes your transaction and puts it into the right place. WHY RPCs MATTER Without RPCs, tools like: • MetaMask (your wallet) Foundry (your development toolkit) • Hardhat (another dev environment) • Dapps (like Uniswap, Aave, etc.) …wouldn’t know how to talk to the blockchain. RPCs are the language bridge. WHO PROVIDES RPCs? Running a blockchain node yourself is possible but very expensive: • You need powerful hardware. • You need lots of storage. • You need constant uptime and syncing. That’s why many developers use Node-as-a-Service providers. These companies run blockchain nodes for us and give us RPC URLs we can connect to. Some popular ones include: 1. Alchemy 2. Infura (MetaMask uses this by default) 3. QuickNode 4. Ankr 5. Chainstack These providers don’t just give access to nodes; many also add features like analytics, dashboards, and debugging tools. Check out my Medium post for the full article: medium.com/@Cheerie/foundry-… #Alchemy #Infura #Web3 #Blockchaindevelopment #Solidity #Ethereum #womenintech #150daysofcode
1
71
Day 48-70 of My Blockchain Journey Just got started with Foundry 🔨 and wow, this framework makes building and testing smart contracts feel like magic. Here’s what I’ve learned so far 👇 1. Foundry is a fast, developer-friendly framework for Ethereum smart contracts. Think of it as your all-in-one toolbox: building, testing, deploying, debugging. The main tools 🛠️ • Forge → write & run tests • Cast → interact with contracts & RPCs • Anvil → spin up a local blockchain • Chisel → debug in a REPL style 2. I also learned how RPCs connect Foundry to real networks. • Local testing = Anvil • Public chains = RPC endpoints (Infura, Alchemy, or your own node) Super excited about how powerful Foundry feels. Next up: diving deeper into testing smart contracts with Forge. Stay tuned. Checkout my Medium post:medium.com/@Cheerie/my-first… #150DaysOfSolidity #Web3 #WomenInTech #FOUNDRY #Ethereum
3
109
Day 44–48 of My Blockchain Journey After weeks of mastering Solidity and smart contract security, I’m diving headfirst into DeFi and it's going to be a 30-Day DeFi Build Sprint For the next 30 days, I’ll be building DeFi protocols from scratch — staking, lending, borrowing — and breaking down everything I learn 👇 #DeFi #Web3 #Solidity #150DaysOfBlockchain 1/ What is DeFi? DeFi = Decentralized Finance. It means building financial tools (lending, savings, exchanges) without banks or middlemen. Everything runs on smart contracts — open, transparent, and permissionless. 2/ In TradFi (Traditional Finance), you need: • A bank account to earn interest • Approval to borrow money • An identity to access services In DeFi, you only need: • A wallet • Internet • Smart contract interaction 3/ Popular DeFi use cases: 💸 Lending & borrowing 🔒 Staking 💱 Decentralized exchanges (DEXs) 🚜 Yield farming 💼 Asset management 💳 Stablecoins 🔗 Synthetics & derivatives And we’ll explore them all during this journey. 4/ DeFi is composable. Think of protocols as LEGO blocks. You can stack them, combine them, remix them — that's how big systems like Yearn, Curve, and Aave were born. This opens doors to permissionless innovation. 5/ But DeFi isn't perfect. It’s full of risks: ⚠️ Smart contract bugs ⚠️ Oracle manipulation ⚠️ Flash loan exploits ⚠️ Rug pulls ⚠️ Impermanent loss ⚠️ Poor protocol design DeFi is powerful but dangerous when misunderstood. 6/ Why I’m doing this: ✅ To build real DeFi tools from scratch ✅ To learn and share the risks and mechanics ✅ To educate other devs who want to enter this space ✅ To become an excellent DeFi developer + writer 7/ The structure for the next 30 days: 🛠 Protocols: • Week 1: Staking • Week 2: Lending • Week 3: Borrowing • Week 4: Multi-contract integrations, audits, UI Topics: • Code walkthroughs • Gas & security optimization • Exploit case studies • Medium articles + GitHub repos 8/ Tools I’ll be using: • Solidity (Foundry for dev & test) • OpenZeppelin contracts • Chainlink (for oracles) • ERC-20 token standards • Sepolia/Fuji for deployment • Hardhat/Remix for quick testing 9/ By the end of this 30-day DeFi sprint, I want to: ✅ Build multiple audited smart contracts ✅ Understand tradeoffs in protocol design ✅ Master flash loan security ✅ Build a reputation as a reliable DeFi builder & educator 10/ You’re invited to join the journey: Whether you’re new to DeFi or already shipping contracts, there’s something here for you. 👉 Learn with me 👉 Ask questions 👉 Let’s grow Web3 together I’ll post daily updates here + full breakdowns on Medium. Let’s build. #Day44 #DeFi #150DaysOfBlockchain #Web3Builder #Ethereum #SmartContracts #Solidity #Web3Community
3
114
🚨 3. Compromised The Setup: An exchange sells DVNFTs at 999 ETH each, priced by an oracle with three trusted reporters. A server response leaks hex strings decoding to private keys for two reporters: 0x188Ea627E3531Db590e6f1D71ED83628d1933088 0xA417D473c40a4d42BAd35f147c21eEa7973539D8 You start with 0.1 ETH, and the exchange holds 9999 ETH. • The Vulnerability: The oracle uses a median of three prices, and controlling two reporters lets you manipulate the median. The leaked keys allow unauthorized postPrice calls, enabling: 1. Setting a low price (1 wei) to buy cheaply. 2. Raising it to 9999 ETH to drain the exchange on sale. 3. Resetting to 999 ETH per challenge rules. • Exploit Mechanics: lookup image for exploit code The attacker drains 9999 ETH, exploiting the oracle’s trust model. • Why It’s Dangerous: This reflects real-world oracle attacks (e.g., flash loan price manipulation). Leaked credentials or compromised nodes can destabilize DeFi systems. • What I Learned: 💡 Oracle Security: Decentralize data sources and rotate keys regularly. 💡 Trust Assumptions: Never assume external inputs are secure. 💡 Defense: Use timelocks, multi-signature updates, or anomaly detection. 🧪 What This Taught Me as a Developer • Attacker Mindset: I now simulate “what could go wrong?” before “what should work?” • Safe Testing: Local environments like DVD let me break things without real-world cost. • Paranoid Design: Every contract must assume the worst—malicious users, flash loans, or leaked data. Quote to Live By: “In Web3, a single unprotected line of code can cost millions. Security isn’t optional—it’s survival.” 👣 What’s Next for Me • Finish All DVD Challenges: I’m hooked—next up are the trickier ones! • Recreate Vulnerabilities: Build my own flawed contracts to deepen understanding. • Secure Rebuilds: Redesign them with defenses like timelocks and checks. • Share Write-Ups: Detailed posts (like this) to help the community. would you read them? 🚨 To Fellow Builders If you’re writing smart contracts and skipping security, you’re building a vault without a lock. A single exploit can erase your work and others’ funds. Start Today: • Damn Vulnerable DeFi: Hands-on exploit practice. • Ethernaut: Puzzle-based security learning. • OpenZeppelin Guidelines: Best practices for secure coding. Let’s build contracts that don’t just function—let’s build ones that can’t be broken. #BlockchainJourney #SmartContractSecurity #DeFi #Solidity #Web3Security #DamnVulnerableDeFi #FlashLoans #Web3 #Ethereum
2
61
🗳️ 2. Selfie The Setup: A lending pool pairs with a governance system where proposals require token ownership at a snapshot. Flash loans let you borrow tokens temporarily. The Vulnerability: The governance checks only the snapshot balance, not ownership duration. An attacker can: 1. Borrow tokens via flash loan. 2. Take the snapshot and queue a malicious proposal (e.g., to drain the pool). 3. Wait out the governance delay. 4. Execute the proposal and steal funds before repaying the loan. • Exploit Mechanics: lookup image for exploit code The attacker controls the pool for one transaction, draining it entirely. • Why It’s Dangerous: This mirrors real-world governance hacks (e.g., bZx), where temporary ownership via flash loans bypasses trust assumptions. • What I Learned: 💡 Time-Weighted Ownership: Use vesting or duration-based voting to filter flash loan votes. 💡 Snapshot Risks: Validate token history, not just current balance. 💡 Defense: Implement timelocks or require minimum holding periods.
1
3
125