Bundler Reputation Score Tracker
Free to download on every platform. Comes pre-installed on BotFone, BotPad and BotFlip — with extra free apps included.
About this app
WHAT IT DOES
Bundler Reputation Score Tracker provides comprehensive monitoring and scoring of ERC-4337 bundler reputation, enabling developers and operators to evaluate bundler performance and reliability. It retrieves on-chain EntryPoint contract bytecode via eth_getCode and fetches verified source code and ABI from block explorer APIs. The tool analyzes bundler addresses and staking deposit information, tracks UserOperation submission history and bundler performance metrics, and calculates historical bundler success/failure rates and inclusion times. It generates a reputation score for each bundler based on a weighted combination of success rate (60%), staking deposit (20%), and operation volume (20%). The output includes an overall network health assessment (Good, Warning, or Critical), count of bundlers tracked, average score, a detailed bundler matrix showing each bundler's address, score, success rate, staking deposit, and operation count, and actionable recommendations for selecting reliable bundlers—such as switching to higher-rated bundlers, increasing staking for low-reputation bundlers, or monitoring underperforming bundlers for improvement. This enables AA wallet developers, bundler operators, and dApp developers to make informed decisions about which bundlers to trust and use for submitting UserOperations.
HOW TO USE
Connect your BGWallet to the target EVM chain. Paste the address of the ERC-4337 EntryPoint contract you wish to monitor. Provide a list of bundler addresses (one per line) that you want to track. Optionally supply a GitHub repository URL to pull bundler implementation details and reputation specifications for additional context. The tool fetches the EntryPoint contract's bytecode and state, analyzes bundler history and staking data, and generates a comprehensive reputation report. Review the network health, bundler count, average score, the bundler matrix showing individual scores and performance metrics, and the list of recommendations. Use the results to identify the most reliable bundlers for your AA operations and to detect underperforming bundlers that may need attention.
BUNDLER REPUTATION SCORING AND PERFORMANCE ANALYSIS ENGINE
The real technical mechanism is the bundler reputation scoring and performance analysis engine that combines EntryPoint contract analysis with bundler performance metrics. The tool first analyzes the EntryPoint contract's bytecode to understand the staking and reputation tracking mechanisms—specifically how the EntryPoint tracks bundler deposits and enforces reputation-based throttling or banning. It then aggregates bundler performance data from multiple sources: historical UserOperation submissions, success/failure rates, inclusion times (how quickly operations are included in blocks), and staking deposit amounts. The reputation score is calculated using a weighted formula: success rate contributes 60% of the score, staking deposit contributes 20% (with higher stakes indicating greater commitment), and operation volume contributes 20% (with higher volumes indicating active and reliable bundlers). The score is normalized to a 0-100 scale, with scores above 75 considered high, 50-75 moderate, and below 50 low. The network health assessment is derived from the distribution of scores: Good if the average score is above 75 and no bundlers are below 50, Warning if the average is 50-75 or some bundlers are below 50, and Critical if the average is below 50 or multiple bundlers are underperforming. The tool also identifies bundlers that may be throttled or banned by the EntryPoint based on reputation thresholds. This approach provides developers with a comprehensive, data-driven way to evaluate bundler reliability and make informed decisions about bundler selection, improving the overall reliability and efficiency of AA operations.
WHAT IT CANNOT SEE
This tool cannot generate a complete reputation score without access to EntryPoint bytecode or bundler history. It is limited by your RPC provider's rate limits for data retrieval, which may delay analysis on congested networks. It cannot determine if bundler reputation is correctly calculated without executing reputation logic—the tool relies on available performance data and may not reflect real-time reputation changes. The detection relies on the completeness of the ABI and source code verification; unverified contracts or incomplete verification data will produce incomplete or inaccurate results. Detection is based on bytecode pattern matching and may miss indirect or obfuscated reputation logic, such as reputation logic hidden in libraries or via delegate calls. The tool cannot assess runtime behavior or performance implications of reputation scoring, such as how reputation thresholds affect bundler behavior under different network conditions. It may produce false positives for data that appears similar to reputation data but is used for other purposes. The tool does not execute the contract to validate reputation scores, so it cannot confirm that the scores accurately reflect the EntryPoint's internal reputation tracking. It cannot account for network-specific reputation implementation differences or future upgrades—different chains may have different EntryPoint implementations or modifications to ERC-4337 reputation logic. Bundler reputation scoring may vary across implementations and change over time as standards evolve.
PLEASE NOTE
This tool works exclusively with EVM-compatible chains that support ERC-4337 account abstraction. It requires active internet connectivity to access block explorer APIs and RPC endpoints. Some block explorers may require API keys for high-volume data retrieval. The tool is read-only and does not submit any transactions—it only produces reputation assessments. Bundler reputation is critical to AA security and reliability; always verify reputation scores against actual bundler performance logs and test on testnet before mainnet deployment. Different EntryPoint implementations may have different reputation thresholds and scoring mechanisms.