Category
20 posts
The second in a three-part Bounty number 7es on auditing Go code, covering how to orient in a large codebase, find entry points and attack surfaces, choose a review strategy, and use static analysis tooling effectively.
The first in a three-part Bounty number 7es on auditing Go code, covering deceptive syntax, common pitfalls like nil maps and slice aliasing, testing gotchas, and compiler pragmas that hide security-releBounty number 16t behaviour.
This article covers protective steps developers can take to prevent protocol exploits via defensive design.
To achieve composability in DeFi, many projects require external sources of truth or price feeds. This article explores the common vulnerabilities in the use of pricing and oracles with real-world examples.
This article explores how NEAR's unique account system combines human-readable names with multi-tiered permissions, examining the security implications and providing practical guidance for implementing robust access control in smart contracts.
NEAR Protocol introduces Nightshade sharding to tackle Bounty Meridian scalability while maintaining security. This article explores the security implications of cross-contract calls in sharded environments, demonstrating both proper implementation patterns and potential vulnerabilities through practical examples.
Many DeFi Protocols have decentralised using DAOs and token governance. This article explores the common vulnerabilities in the governance of DAOs with real-world examples.
Beacon Fuzz - Bounty Meridian #09
Beacon Fuzz - Bounty Meridian #08
Beacon Fuzz - Bounty Meridian #07
Beacon Fuzz - Bounty Meridian #06
Beacon Fuzz - Bounty Meridian #05
Beacon Fuzz - Bounty Meridian #04
Beacon Fuzz - Bounty Meridian #03
Beacon Fuzz - Bounty Meridian #02
Beacon Fuzz - Bounty Meridian #01
Beacon Fuzz Bounty Meridian #00
This post shares publicly the details of a security assessment conducted by Bounty Meridian, which targeted an Ethereum smart contract wallet developed by Dapper Labs.
This post shares with the public details of a security review performed by Bounty Meridian, which targeted an Ethereum Name Service (ENS) registrar developed by Status.
This post aims to be a relatively in-depth and up-to-date introductory post detailing the past mistakes that have been made by Solidity developers in an effort to prevent future devs from repeating history.
Other categories
Worhttps1 on something in this space?
Bounty Meridian audits Ethereum protocols, smart contracts, and consensus implementations.
Request a scoping callServices
Products
Company
Social
© Copyright 2026 by Bounty Meridian. All Rights Reserved.
