Beyond Audits: Securing Web3 in the Age of Lazarus - Gracious Igwe
The picture loads from YouTube. The player loads only when you press Play. Turn on captions in the player if you need them.
Gracious Igwe argues that smart contract audits alone do not keep Web3 projects safe. The talk cites 2025 loss figures, says most hacked contracts had been audited, and describes how the Lazarus Group uses fake job applicants, social engineering and supply chain attacks. It then covers operational security for individuals, organisations and protocols, and makes the case for continuous monitoring.
Not by We Them Media Channel: Web3Bridge. Published Sunday 26 October 2025.
Titles are the owner’s. It plays from their channel.
Watch it on YouTube (opens in a new tab)
Transcript
This transcript may contain errors. This video belongs to Web3Bridge. Letters mark each change of speaker.
These are the speakers’ own words. We have not checked their claims.
0:02 A: All right. Hello, everyone. GM, GM, everybody. Yeah, my name is Gracious, and I'm a security analyst and also a security researcher. I'm very pleased and excited to be here, and it's an honor to be standing here speaking to you guys about web security. So, like I said, I'm a security analyst. I work at the Security Alliance, also known as SEAL, and we're a nonprofit crypto-native security collective. Okay, crypto-native security collective dedicated to protecting Web3 protocols through rapid response, collaboration, and shared intelligence. So today I'm going to be speaking about securing Web3 beyond audits, and, um, the title of my topic is Beyond Audits: Securing Web3 in the Age of Lazarus. So my reason for giving this talk is because I do not believe that smart contract audits are sufficient, because despite all the efforts, all the audits, and all the money we've poured into security, um, we're still losing billions to to hacks and attacks. So I'm going to tell you why, in my opinion, I do not think that smart contract audits are enough for this space. So let's get down to business. Uh, yeah, the numbers don't lie. The numbers we are seeing in 2025 are unprecedented. Um, in the first half of 2025, Web3 recorded approximately $3.1 billion in losses to hacks. And, um, what is interesting is that This is, this is already more than all the losses that, that was recorded in the year 2024. And interestingly, 60% of those losses were from the Bybit, um, February 2025 hack, the $1.5 billion Bybit breach. Now let's take a look at the attack vectors. We have control hijacking, which, um, accounted for $1.7 billion in losses, and then phishing attacks, which accounted for $410 million in losses. So together, these figures imply that Web2 attack vectors- Web2 attack vectors are dominating smart contract exploits, right, in the Web3 security space. So the question is not if another attack is going to happen, it's when and how it's going to happen, and if we are prepared to tackle it. Because despite the widespread awareness of this problem, the ecosystem is still fundamentally vulnerable. All right, so let's move on. So that brings us, um, to a critical misconception in the industry, which is that audits equate to comprehensive security. But then the data says, or rather statistics says otherwise, because 92% of hacked smart contracts in 2025 had undergone some form of audits, undermining the belief that an audit badge means a protocol is completely secure. So if audits are supposed to be our safety nets, then why are we still falling through the cracks? Well, the reason is because we've created, um, a sort of- we've created an ecosystem where the appearance of security takes precedence over actual security measures. When you look at current auditing practices, um, they are limited by their narrow focus on code one-time assessments, inconsistent quality, and inability to detect human-driven threats. And that leads us to the question of who audits the auditors, and are there even quality standards, or are there even standards in the space that ensures that we get quality audits and assessments, right, in this space? So moving on, Now, this guy, um, uh, now this guy, Bruce Schneier, he observed that amateurs hack systems but professionals hack people. And I think that this distinction is important in understanding the current Web3 attack landscape. So if you're, if you're active in the Web3 security space, and you're someone that regularly reads audit reports and postmortems, you would notice that recently, um, reports are dominated by, um, human-based or human-layer-based vulnerabilities. But as at 2022 and 2023, reports were dominated by code-based vulnerabilities. So in recent years, attacks are driven by operational failures, and social engineering have become significantly more common within the space. By 2024, high-value attacks succeeded primarily through compromising human and organizational layers rather than technical exploits. So basically, the tech is solid, is, is, is good, but the human factor is what is the actual problem. It's very vulnerable and is susceptible to attacks, and attackers know this. They recognize this. And, um, They recognize this and they're taking advantage of that. So, so Lazarus- how many of us know about the Lazarus Group? Please raise up your hand. Okay, so the Lazarus Group has executed more than 40 attacks resulting in theft exceeding $3 billion in the DeFi space. Their strength extends beyond technical vulnerabilities to understanding human behavior, and they don't just break code. they break trust in the entire system. There's something I refer to as the decentralization illusion. This is- this means that we all know that the tech is decentralized and it's solid, but then the humans operating this tech are centralized and they are vulnerable. And this creates a kind of, um, disconnect and creates an opportunity for attacks and hacks to happen. So how does the Lazarus Group operate? We have insider positioning, uh, they apply for legitimate jobs. Sorry, okay, so they apply for legitimate jobs with fabricated credentials. They work as contractors through consulting firms. They become trusted community members in governance roles. They maintain cover for months and even years. Before attacking. Then we have social engineering, multi-platform campaigns. They impersonate executives, they use deepfake technology for attacks, they create artificial urgency. And then we have supply chain infiltration. They compromise development tools, libraries, and frameworks. They infiltrate communication platforms and community spaces. They target service providers and contribute malicious code to open source projects. And then lastly, we have long-term relationship building. So they create fake LinkedIn profiles, they engage in technical discussions, they offer job collaborations, and they extract organizational intelligence through conversations. Then we have notable incidents, the Running Bridge hack and the Harmony Bridge hack. So, The Running Bridge hack, um, Lazarus created fake developer profiles and they spearphished the employees of the Running Bridge, and then they gained access to validator nodes and drained about $624 million. While for the Harmony Bridge hack, they used deepfake-enabled video calls to gain trust and eventually walked away with $100 million. Now it's interesting to note that neither of these hacks were caused by code bugs. But they were as a result of human and organizational failures. And both of these projects, or rather protocols, had- Both of these protocols had passed multiple security audits, but then they suffered massive breaches. And this reveals a critical gap in traditional security approaches. There's something referred to as the audit blind spot. So you build your project, you get an audit, But then an audit is not going to tell you that your key storage practices are below par. Your audit is not going to tell you that- it's not going to prepare you for a social engineering attack. Your audit is not going to tell you that your employee is a North Korean state actor. So that is referred to as the audit blind spot, which is comprehensive code review but paired with complete operational blind spots. Then the decentralization paradox is also a factor. Um, both protocols promoted decentralization as a security strength, but in practice, it did not eliminate human risk. Rather, it spread it across potential attack vectors. And then lastly, we have the human factor. Lazarus succeeded by exploiting human vulnerabilities rather than breaking code, demonstrating that true operational security must address both technical systems and human behavior. All right, so I've been talking about operational security, operational security. What exactly is operational security? Well, OPSEC involves implementing proactive procedures and practices to protect security assets from attacks. So basically, OPSEC is just like treating the operational and human layer just as important as you treat the technical layer, which is your code and smart contracts. I think it's important to distinguish OPSEC from related security disciplines such as SecOps and AppSec. SecOps, which is security operations, is primarily focused on reactive security measures, including real-time monitoring, threat detection, and incident response protocols. And then AppSec involves designing, building, and maintaining secure code through bug bounties, audits, and- bug bounces again. So SecOps is like reactive, is the thing that you do after you've deployed your projects. So like you do real-time monitoring, threat detection, and incident response. And then AppSec is like proactive, like the ones we all know, which is code audits, writing secure code, and so on and so forth. So most Web3 security resources are focused on the AppSec factor, but then operational security failures cause the majority of losses, highlighting a critical misalignment that needs correction. Then we have the OPSEC framework. The OPSEC framework is basically, um, operational security measures that you can implement. This is not comprehensive, like this is not everything. These are just like the key ones that I selected. So we have key management, which is the secure handling of private keys and signing procedures, endpoint security, securing individual devices and machines, personnel security, education and human factor management, application security, securing applications and interfaces, code management, secure development and deployment of code, and then access control, managing your infrastructure access and permissions to ensure that only authorized personnel have access to your system. So here you can see a real-time monitoring dashboard for web security incidents, and it was built by Chainlight. Name is Lumos. So it, it just sums up everything I'm talking about since 95% of emergency incidents in April 2025 were caused by basic avoidable security lapses. So Web2 attack vectors such as social engineering, key leaks, supply chain compromises accounted for over 3 times the value stolen by smart contract bugs compared to smart contract bugs. And then from January 2023 to date, control hijacking led to $3.31 billion in losses. But then in contrast, smart contract vulnerabilities accounted for just $900 million in losses. And then we have major cases and studies. There's the Bybit hack I talked about earlier. So North Korean hackers evolved from targeting individual protocols to critical infrastructure, and the Bybit incident compromised the safe wallets. SafeWallet platform used by thousands of DeFi users. So what happened was in the Bybit incidents, um, North Korean hackers didn't just- they didn't just target, um, individual protocols, rather they targeted the core Web3 infrastructure, which is the SafeWallet platform. And Bybit, being the biggest users of the SafeWallet platform, were actually the victims of the hack. Then we have Radiance Capital. Um, attackers build credibility over extended periods before striking. The Radiance hack involved a fake security researcher who spent a year establishing trust before deploying malware. So, this was what I talked about earlier where I said your code is not going to tell you whether your employee is a North Korean state actor. In the Radiant Capital hack, a North Korean state actor had sent a file containing malware to the Radiant Capital team. And then when they clicked on the file, it affected their machines, and then they were able to- North Korea was able to steal or drain their funds. And then we have the WazirX hack. Attackers bypassed hardware security, wallet security, By manipulating what users see before signing, and then victims unknowingly authorize malicious transactions while believing they are legitimate. So we have personal OPSEC for developers and users. Effective operational security starts at the personal level. It includes preventing information leakage, sensitive information like travel schedules and role updates. Can provide openings for social engineering attacks. Then secure physical environments, extend security to development spaces and communications channels, and then rigorous key management protects against, protect against social engineering attacks and physical access vulnerabilities. And lastly, we have social media awareness. Attackers build detailed profiles by aggregating information. for multiple online resources. Moving on, we have OPSEC at the organizational level, which includes vetting your hires, like thorough screening process for your team members or your new employees. Then cultural balance, navigating security needs, insider threats, managing risk from compromised team members, infrastructure hardening, strengthening systems against potential vulnerabilities, team protocols, and lastly, secure communication. And then OPSEC at the protocol level. So at the protocol level, OPSEC involves more than just deploying multisig wallets. It requires clear process for governance and treasury protection. So for those of us in governance, these are the measures that you can take to ensure that your operational security is solid. We have multi-signature security. Effective multisig requires geographic distribution, operational independence, and so on and so forth. Governance controls prevent attacks through snapshot-based voting, quorum requirements, and monitoring. We have treasury protection, time locks implementation, incident response, and admin key management. All right, so security as a life cycle. This is like the crux of everything I've been talking about since. Web3 security must be approached as a comprehensive life cycle. This means that you must work towards approaching secure Web3 security as a continuum. That is, as a continuous process. It's not something that you just do once and then you forget about it. You have to continue doing it. at every stage of a project. So we have pre-deployment security, which includes threat modeling, secure development practices, comprehensive testing, upset planning, and incident response. Then we have deployment security, which includes real-time monitoring, anomaly detection, community alerting mechanisms, response team, and continuous threat intelligence. And lastly, we have post-deployment security, security, which includes operational security, systemic improvements, and regular assessments. Then the continuous approach versus point-in-time audits. So the continuous approach is just like continuous approach to security versus just having an audit once and forgetting about it. So the point-in-time audits are like the traditional audit models. And they force teams to react only after something has happened or after an attack has happened. And then it often takes days to, to respond. So like, there's usually a delay after like something has happened. And then in that process, the attacker might escape with the money and the money, not be able to recover it and so on and so forth. But with a continuous security approach in place, It involves constant monitoring, regular expert reviews, and threat detection to catch problems early and respond faster. Then we have for point-in-time audits, they quickly become outdated because security is always evolving. It's not something that is, it's a constant, right? It's always changing. So like protocols update and threats evolve. Leaving systems vulnerable to new risk. Then shared responsibility. The continuous approach brings users into the security loop through bug bounties, making security a collaborative effort. So the mindset shifts. So as well as we try to adopt security, the continuous security approach, We need to change the way we think about security. So instead of thinking, oh, we got audited, we are secure, we don't need to do anything else, you start thinking that, oh, we are continuously securing our system. Instead of just saying, oh, security is just a requirement, then you start saying security is part of how we operate, security is part of our infrastructure, you know. Then audits prevent attacks to continuous vigilance prevents attacks. All right. So key takeaways. Security is not a product, it's a process. Yes. Constant monitoring, continuous vigilance performs points-in-time security checks beyond audits. Audits provide a necessary foundation, but they cannot address all the vulnerabilities. And then human vulnerability. OPSEC is now the primary attack vector. And social engineering compromises attack even the most sophisticated smart contracts. All right. So how you can contribute. For developers and teams, move beyond smart contract audits to include OPSEC assessments. Establish multisig management procedures. Create incident response plans. Implement continuous monitoring. Contribute to open source security tools. For investors, look beyond audit badges to assess OPSEC practices. Evaluate multisig configurations and and key management procedures, and then supports the development of security tools. And then you, as the user, you can report potential security threats to the community, contribute to open source security resources, and verify protocol security claims rather than relying on audit badges. So at the end of the day, security is everyone's responsibility, and we must come together to ensure that we are able to shift security from where it is right now to a more continuous and human-centric security culture in the Web3 space. Okay, questions?
More from this hub
- Web3Bridge Weekly Update Vlog 3
- Web3Bridge Weekly Update Vlog 2 1
- Web3Bridge Weekly Update Vlog 1
- Web3Bridge Experience Uche
- Web3Bridge Experience Vicentia
- Web3Bridge Experience Tosin
- Web3Bridge Student Experience
- Web3Bridge Experience Mitchell
- Web3Bridge Experience Abiodun
- Web3Bridge Live Stream
- Web3 Lagos Conference 2022
- Web3Bridge 3rd anniversary Documentary
- Meet The Students of Web3bridge Cohort 09 - Part I
- Meet The Students of Web3bridge Cohort 09 - Part II
- Cohort 09 Week 01 Students' Report
- Cohort 09 Week 02 Students' Report
- Question & Answer Session With Vitalik Buterin
- Pushing the boundaries of Web3 UX - Richa Joshi
- Implications of the National Policy of Blockchain in Nigeria on the growth of the Web3 ecosystem
- Cohort 09 Week 03 Students' Report
- Cohort 09 Web3bridgers in Class
- Understanding Blockchain For Beginners - Hezekiah Suleman
- Exciting Insights: Students Reflect on Their Week 04 Learnings!
- Taking a Breather: Our Students Stepped Away from Classes for Conference and Workshop Week 05
- The Students Share Their Eviction Test Experience Week 06
- The Students Spent The Whole Week Building Projects Week 07
- An Introduction to Web3 Frontend: Students Sharing Their Experiences Week 08
- The Students Talk About The Dapps They Built Week 09
- Web3bridge Odyssey: Documentary Telling The Story of Web3bridge
- Exploring Foundry: Students Share Their Learning Journey Week 10
- Students Explain Diamond Standard (EIP-2535) | Week 11
- Smart Contract Code Review: The Students Share Their Experience Week 12
- Students Share Their Experience With Smart Contract Security Class Week 13
- Starting & Building a Career in Blockchain - Michael Jerry
- Web3: Community & Protocol - Ayodele Aransiola
- Understanding & Contributing to DAOs - Odebunmi Fiyinfoluwa
- Hacking distribution for web3 startups - Olatinwo Barakat Anuoluwa
- How crypto can regenerate the world - Kevin Owocki
- The Future of Work in a Decentralized World - Emmanuel Tope
- Blockchain for Africa: Why we should care - Amarachi Amaechi
- Web3bridge Cohort X Onsite Arrival Footage
- Meet The Faces of Cohort X: Introducing The Students of Cohort X - Part I
- Meet The Faces of Cohort X: Introducing The Students of Cohort X - Part II
- Meet The Faces of Cohort X: Introducing The Students of Cohort X - Part III
- Centralized vs Decentralized Networks: Insights from The Msg Senders
- Team ZK Shares Their Knowledge Concerning Smart Contract and It's Advantages
- Happy International Women's Day From Web3bridge
- Our Students Share Insight to What Consensus Mechanism is on Blockchain
- Utilizing JSON RPC as a Communication Protocol for Blockchain
- The Life of a Web3bridger in The Cohort: Abigael Irene Nyangasi from kenya
- The Life of a Web3bridger in The Cohort: Mary Gathoni Wangui from kenya
- Team MsgSender Shares Their Insight on Dapps, What They Learned, and Built
- Team Zero Knowledge Shares Their Insight on Dapps, and What They Learned
- Team Alpha.Eth || Solidity
- Exploring Smart Contracts || Cohort X Shares Insight
- Our Students Break Down Multisig Wallet || Cohort X
- Our Students Explain Mainnet Forking: Mirroring The Live Blockchain || Cohort X
- Exploring Smart Contract Interaction || Cohort X
- A Weekly Recap: What Cohort X Learned at Web3Bridge
- Interacting with Web3: Frontend Development in Cohort X
- Project Week: Cohort X Shares Insights and Emotions on Eviction Test
- Watch Our Students Break Down the Diamond Standard in Blockchain || Cohort X
- Starknet Fundamentals
- Cairo Programming Language I
- Cairo Programming Language II
- Writing Cairo Smart Contract on Starknet I
- Writing Cairo Smart Contract on Starknet II
- Testing
- Check out what our ZK masterclass students said about their experiences in the program.
- Starknet Architecture
- Frontend Interaction With Cairo Smart Contract on Starknet
- Quick Review: Understanding Account Abstraction in Blockchain
- Quick Review: EIP-4844 Proto-Danksharding on Ethereum
- Quick Review: Blockchain Layer Two Solutions Explained
- Quick Review: Oracles in Blockchain Technology
- Beyond Web3Bridge: Ayomide Adebara’s Success Story
- Beyond Web3Bridge: Casweeney Ojukwu’s Success Story
- Beyond Web3Bridge: Etim Paul’s Success Story
- Beyond Web3Bridge: Faith Robert’s Success Story
- Beyond Web3Bridge: Emmanuel Glory Praise’s Success Story
- Beyond Web3Bridge: Chinonso Idogwu’s Success Story
- Beyond Web3Bridge: Ginika Chinonso’s Success Story
- Beyond Web3Bridge: Mayowa Obisesan's Success Story
- Beyond Web3Bridge: Mitong Dapal's Success Story
- Beyond Web3Bridge: Musa Abdulkareem's Success Story
- Meet The Faces of Cohort XI: Introducing The Students of Cohort XI - Part I
- Meet The Faces of Cohort XI: Introducing The Students of Cohort XI - Part II
- Meet The Faces of Cohort XI: Introducing The Students of Cohort XI - Part III
- Meet The Faces of Cohort XI: Introducing The Students of Cohort XI - Part IV
- Meet The Faces of Cohort XI: Introducing The Students of Cohort XI - Part V
- Web3 Lagos Conference 2024: Innovation, Networking & Game-Changing Insights - Day 1 & 2 Highlights!
- Web3 Lagos Conference 2024 Recap: Innovation, Hackathons, and Blockchain Breakthroughs!
- Supercharging user onboarding; Building with social logins and smart wallet - Ayomitan Pamilerin
- Web3bridge Journey; A look into the Future - Ayodeji Awosika
- Mental Model for Building Smart Contracts on Bitcoin - Abimbola Adebayo
- Beyond DX; Building World Class Developer Documentation for Web3 - Owanate Amachree
- DAOs and Onchain Governance - Fiyin Odebunmi
- Build In Public; The Web3 Advantage - Kevin Chibuoyim
- Building Scalable Dapps - Israel Rex
- Web3bridge Students (cohort 11) Share What They’ve Learned: What is blockchain?
- Web3bridge Students (cohort 11) Share What They’ve Learned: Understanding Ethereum
- Web3bridge Students (cohort 11) Share What They’ve Learned: Nodes and Clients
- Web3bridge Students (cohort 11) Share What They’ve Learned: Consensus mechanism.
- The Future of Data in Web3 - Ivy Elebesunu
- Empowering Underserved Markets Onchain An Exposition to Real World Assets RWAs - Oluwole Kayode
- Introduction to Blockchain - Hezekiah Suleman
- Real World Assets Fluke or For real - Emmanuel Tope
- Science on the blockchain - Introduction to Decentralized Science - Scott Itepu
- Product Roadmaps and Team Management in a Decentralized World - Adedoyinsolami Adeyeye
- The Role of Social Media in Building Web3 Communities Best Practices and Pitfalls - Amara Achusi
- Working as a writer in Web3; How to build their brand - Toluwalope Ajetunmobi
- A DePIN protocol for unlocking Africa's solar energy potential and solving Energ - Ifeanyi Christwin
- Introduction to Arbitrum - Oluwafemi Samuel
- Web3 UX from a Wallet point of view - John Odey
- How to write content that connects with Target audience - Victor Fawole
- The Role of User Experience in Web3 Adoption - Favour Ohanekwu
- Building a Career in Web3 - Purity Ogheneochuko
- Scroll Technical Workshop - Wisdom Ogwu
- Web3 Documentation Best Practices - Lessons from Rootstock - Wisdom Nwokocha
- Interchain applications Cosmos and the IBC - Peter Anyaogu
- Developers guide to building on Solana - Alex
- Future of Wallet and Custody - Peter Olawuyi
- Field Notes from the Trenches - Ukeme David Eseme
- Web3bridge Students (cohort 11) Share What They’ve Learned: An Account
- Web3bridge Students (cohort 11) Share What They’ve Learned: The EVM
- Web3bridge Students (cohort 11) Share What They’ve Learned: Public and Private Keys
- Web3bridge Students (cohort 11) Share What They’ve Learned: Transaction
- Web3bridge at 5 Full Documentary | Ayodeji Awosika on the Web3 Journey and Growth
- Invariants Testing for Smart Contracts in the World of Medusa - Joshua Adesanya
- Improving web3 User experience through chain abstraction - Collins Enebeli
- The Future of Technical Communication in Web3 - Victoria Adedayo
- CoreDAO workshop
- Build On Bitcoin Leveraging Rootstock - Chekwube Peters
- Building Scalable Web3 Applications - Amani Kanu
- The Future of Social Media for Blockchain Startups - Motolani Omotuyi
- Buidling Decentralized App quickly - KC Pele
- Building the Future Decentralized Computing Infrastructure for Web 3.0 - Uchechukwu Azubuko
- Understanding the Lisk Protocol - Lisk Workshop
- ZK Workshop - PSE team
- From Ancestors to Algorithms Harmonizing Trust Based Cultures - Abidemi Adenle
- DeSci Web3 and the Future of Scientific Collaboration - Daniel Anomfueme
- Exploring Career Paths in Web3 An Introductory Guide for Beginners - Glory Praise
- Building beyond the Hype - Titus Adenugba
- The Future of Digital Trust Leveraging Ceramic for Global Trust System - Kenechukwu Orjiene
- Building a Global Web3 Community - The SuperTeam Case Study
- Meet Push Notification - Push Ambassador
- Introduction to DEXPAY
- Understanding the East African Ecosystem - David Lumala
- Web3bridge Students (cohort 11) Share What They’ve Learned: Building Function Modifiers
- Web3bridge Students (cohort 11) Share What They’ve Learned: EVM Explained
- Web3bridge Students (cohort 11) Share What They’ve Learned: Account
- Web3bridge Students (cohort 11) Share What They’ve Learned: Wallet
- Web3bridge Students (cohort 11) Share What They’ve Learned :Contract structure
- Web3bridge Students (cohort 11) Share What They’ve Learned: Function Visibility
- Web3bridge Students (cohort 11) Share What They’ve Learned: DApps
- Web3bridge Students (cohort 11) Share What They’ve Learned: Deploying a Smart-Contract
- Cohort 11 Student Shares How Our Training Facility Fuels Success: Meet Akinwunmi Akinrimisi.
- OFFICIAL PARTNERSHIP ANNOUNCEMENT
- Cohort XI - Eviction Week
- Web3bridge Students (Cohort XI) Share What They’ve Learned: Interface, Interaction & Mainnet forking
- Web3bridge Students (Cohort XI) Share What They’ve Learned: Multisig Wallet
- Web3bridge Students (Cohort XI) Share What They’ve Learned: NFT Gated Event Contract
- Web3bridge Students (Cohort XI) Share What They’ve Learned: NFT Gated Event Contract
- Web3bridge Students (Cohort XI) Share What They’ve Learned: ABI
- Web3bridge Students (Cohort XI) Share What They’ve Learned: Intro to REACT
- Web3Bridge Journey: A Ugandan Student's Path to Blockchain Excellence
- Web3bridge Students (Cohort XI) Share What They’ve Learned: JSON RPC and Ethereum JSON RPC
- Web3bridge Students (Cohort XI) Share What They’ve Learned: Wallet, Providers and Signers
- Web3bridge Students (Cohort XI) Share What They’ve Learned: Advanced DApps
- Web3bridge Students (Cohort XI) Share What They’ve Learned: IPFS & IPNS
- Web3bridge Students (Cohort XI) Share What They’ve Learned: MetaMask & MetaMask SDK
- Web3bridge Students (Cohort XI) Share What They’ve Learned: Multicall
- Web3bridge Students (Cohort XI) Share What They’ve Learned: Subgraph
- Web3bridge Students (Cohort XI) Share What They’ve Learned: Calls
- Web3bridge Students (Cohort XI) Share What They’ve Learned: Diamond Standard
- Web3bridge Students (Cohort XI) Share What They’ve Learned: EIP 2535 Diamond Standard
- Web3bridge Students (Cohort XI) Share What They’ve Learned: Upgradeable Smart Contract
- Meet The Faces of Cohort XII: Introducing The Students of Cohort XII - Part I
- Meet The Faces of Cohort XII: Introducing The Students of Cohort XII - Part II
- Meet The Faces of Cohort XII: Introducing The Students of Cohort XII - Part III
- Meet The Faces of Cohort XII: Introducing The Students of Cohort XII - Part IV
- Web3bridge Students (Cohort XII) Share What They’ve Learned: Cryptography, Ethereum, and Wallets.
- Web3bridge Students (Cohort XII) Share What They’ve Learned: Solidity, Functions, and Data Locations
- Scroll Meets Web3Bridge: Exclusive Talk with the Founder!
- The Visit!
- Web3bridge Students Share What They’ve Learned: Blockchain, Distributed Ledger & Consensus Mechanism
- Lisk & CVVC Labs Visit Web3Bridge: Power Moves in African Web3
- Alumni Spotlight: Wilfred, Co-Founder of Audioblocks
- Alumni Spotlight: Michael, Co-Founder of Coinsafe
- This Man's Determination Will Leave You Speechless - Alumni Spotlight EP3: Casweeney Ojukwu
- Breaking Into Tech as a Woman - Alumni Spotlight EP4: Glory Praise Emmanuel
- From Machines to Code | Switched Gears into Tech - Alumni Spotlight EP5: Olorunsogo Banwo
- Web3: Get Rich Quick or Game Changer? – Alumni Spotlight EP6: Ayomitan Pamilerin
- Web3 Lagos Conference 4.0 Is Coming! Africa’s Biggest #web3 Event
- Introducing the Web3Bridge Cohort Xiii students
- DeFi Diaries: Building Wealth Community and Resilience in Web3
- The Future of Privacy - Olayinka Oshidipe
- The Future of Payments: From Card Swipes to Stablecoins - Iyanu Faleye
- Blockchain-Enabled AI for Smart Grid Optimization in Africa - Nnamdi Onuigbo
- Introduction to Arbitrum and the Arbitrum Technologies - Olatunji Samuel
- Data-driven Community Building: Metrics that Matter in Web3 - Mfonobong Umondia
- Panel Session VI: How Stablecoins are Powering the New Pan-African Economy.
- From ChatGPT to ChainGPT: Shipping Autonomous Agents on Ethereum - Opeyemi Stephen
- Understanding and building on Polkadot - Bekka
- Panel Session IV: Onchain data or Community-led Models: Which works Better for Today's Market?
- Panel Session II: From Grants to Growth Capital: The Evolving Web3 Playbook For Web3 African Founder
- Designing for Web3: Crafting Useful Products, Beyond DAOs, DeFis, and Wallets - Mercy Kolapo
- Understanding Qubic - Israel Qubic
- Developer Experience Done Right: Proven DX Strategies to Onboard and Retain More Developers - Joshua
- Dexpay Showcase
- Bridging Traditional Fintech with Decentralized Finance - Motunrayo Koyejo
- Composable Yields - Peter Anyaogu
- A Guide to Crypto Data Analytics. Building Your First Dashboard With Dune - Oladayo Oladipupo
- The Vaults Economy: Supercharging Crypto Market Money with ERC-4626 - Olaoluwa Oluwatunmise
- Creating Public Goods: The Missing Link in Your Developer Marketing - John Fawole
- Web3Bridge Turns 6! 🎉
- 6th Anniversary Appreciation
- RWA Tokenization - Ginger Eke-Daniel
- Stop Yapping, Start Building: Real African Contributions to Web3 - Chukwuemeka Uche
- Starknet: Opportunities and how to get started - Faith Roberts
- Stellar and it's Ecosystem - Levai Agbara
- Content Marketing For Onchain Products: A playbook for Builders and Marketers. - Joy Joe
- The State of Onchain UX. Why Crypto Still Feels Broken (How We Fix It) - Nnamdi Ernest
- Inclusive by Design, Compliance by Default. The Blueprint for Web3 Success - Deborah Enyone Oni
- Why Storytelling Matters in Web3 - Gloria Echendu
- Harnessing The Ripple Effects as African Creators - The Content Chef
- Panel Session: Finding the right path to protocol development and growth as a Web3 Developer
- Panel session I: The rise of builder hubs in Nigeria, lessons & opportunity
- The Future of Payments: Spend Crypto like Cash - Amarachi Agwu
- Pathway to Continuous Growth as a Developer || Mayowa Tudonu || Alumni Retreat
- Enterprise Blockchain: What You Should Know and Prepare For || Adebayo Fabamise || Alumni Retreat
- Crypto and Tax in Nigeria: A Practical Guide to the New Rules || Mitong Dapal || Alumni Retreat
- What to Expect from Web3bridge in 2026
- Web3Bridge Cohort XIV Arrival Day Highlight
- Web3Bridge: Not a Shortcut, But a Launchpad
- Meet the new builders of Web3bridge Cohort XIV || PART 1
- Meet the new builders of Web3bridge Cohort XIV || PART 2
- COHORT XIV INTRODUCTION PART 3
- COHORT XIV INTRODUCTION PART 4
- COHORT XIV INTRODUCTION PART 5
- Web3 Lagos Conference 2026 FINALE
- Web3 Lagos Conference 2026
- WAs for African Money Markets and SMEs | Abidemi Ademola @Web3LagosCon
- The Hard Truth: Why Most Nigerian Startups Never Raise Venture Capital | Adeola Adesina
- Why Every Blockchain Needs an Intelligence Layer | Christian Obi @Web3LagosCon
- AI-Powered Infrastructure:Building More with Fewer Servers & Nodes | KC Pele @Web3LagosCon
- Scaling Your Web3 Startup to Mainstream Adoption | Oluwasanmi Timilehin @Web3LagosCon
- Onchain Lending for Productive Assets | Kayode Oluwole @Web3LagosCon
- The Trust Layer for a Trillion Agents: Blockchain, AI & the Next Internet | Ukeme David
- Trust Machines: What Crypto Actually Does for Credit in Africa | Favour Aniogor @Web3LagosCon
- Stablecoins as a Tool for Financial Inclusion | Ajayi Matthew (OnyxFi) @Web3LagosCon
- Tokenization: The Future of Ownership | Solomon Amaechi @Web3LagosCon
- DePIN & Decentralised AI | Panel Session @Web3LagosCon
- The Missing Layer in AI: Incentives, Trust & Accountability | Aishat Suleiman @Web3LagosCon
- Money in Crypto, Life in Fiat | Francis Codex @Web3LagosCon
- Optimizing for AI Agents: Why Founders Must Build for AI, Not Human Eyes | Adugbo Victory
- Decentralization Across Borders | Adetola Ogunsanya @Web3LagosCon
- Stablecoins & the Future of Digital Payments in Africa | Panel Session @Web3LagosCon 5.0
- AI Is Reshaping the Cybersecurity Landscape but How? | Damilola Abiona @Web3LagosCon 5.0
- Scaling Web3 in Africa: Growth Strategies & Adoption | Growth Panel @Web3LagosCon 5.0
- Building Pan-African Payment Rails with Stablecoins | Suleiman Suleiman @Web3LagosCon 5.0
- The Global Builder Pathway: Where Ethereum's Next Applications Come From | Pablo EAG @Web3LagosCon
- Why Every Fintech Is Rebuilding the Same Stablecoin Liquidity Stack | Amadi Chibuotu @Web3LagosCon
- Legal & Compliance in Web3: Navigating Blockchain Regulations | Panel Session @Web3LagosCon
- The Creator Economy with Stablecoins | Ike Orizu @Web3LagosCon 5.0
- Stablecoins Beyond the Hype: Building Africa's Cross-Border Payment Infrastructure | Mercy Emmanuel
- Venture Capital & Startup Funding in Africa | VC/Funding Panel @Web3LagosCon 5.0
Something wrong, or a video you want off this page? Write to wethem.xyz@gmail.com and it is fixed or taken down within 48 hours.
