Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minutePeepyFalkoniformes’ September 20, 2026, DEV Community post is a call for collaborators on blockchain-chaos, an open-source tool intended to test how EVM applications respond when RPC infrastructure or chain behavior goes wrong. The project describes a proxy that injects faults into RPC traffic and can simulate chain reorganizations with YAML scenarios. The author invites interested developers to make contact through GitHub.
What blockchain-chaos is for
The project is framed around a practical test question: “does my application stay correct when the blockchain and its infrastructure behave badly?” The author describes blockchain-chaos as a proxy between an application and a blockchain, designed to inject faults into RPC clients and help developers exercise edge cases. Its README calls the binary chain-chaos and describes it as reproducible fault-injection testing for EVM blockchain infrastructure.
As an Amazon Associate I earn from qualifying purchases.
Rather than a blockchain network or consumer service, it is a developer testing tool. In the documented model, the application sends requests through the proxy to an upstream RPC endpoint; scenarios alter behavior so a test can examine how the application responds. The author says the aim is to make edge-case testing simpler with Anvil and make runs reproducible through a seed and supplied configuration.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Faults and scenarios described in the README
The GitHub README documents both transport-level failures and behaviors intended to resemble chain or provider problems. These are project documentation claims, not independently tested results.
#1 Best Overall
| Testing area | Documented examples |
|---|---|
| Transport faults | Latency, timeouts, rejected requests, connection drops, and WebSocket disconnections. |
| Chain-aware or response faults | Stale heads, missing logs, malformed responses, and same-height chain reorganization simulation. |
| Scenario control | YAML scenarios, deterministic seeds, and recovery events for reproducible runs. |
| Provider setups | Independent proxies for multiple RPC providers, supporting provider-cluster testing. |
| Run evaluation | Assertion examples named head_monotonic, eventual_recovery, and catches_up, with pass/fail reporting. |
Seeded replay is useful when a failure depends on a particular sequence of disruptions: a team can aim to repeat a scenario rather than rely on an intermittent outage. Multiple provider proxies also let a test exercise applications that depend on more than one RPC provider. The README documents these as intended capabilities; it does not provide comparative benchmarks or independent evidence of reliability or performance.
What the author is asking collaborators to do
The post invites people interested in the project to contact the author through GitHub to be added as collaborators, and welcomes ideas that could help users. The author specifically says they are interested in people who want to code manually rather than use LLMs. They also disclose that Claude Code was used for scaffolding and the README, so prospective contributors can take that preference into account when deciding whether to reach out.
The author says the project is currently maintained and used at their company. Those statements come from the author’s post and have not been independently verified.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRequirements and project status
The README’s installation instructions use Cargo and state that Rust 1.80 or newer is required. It says Anvil, from Foundry, is needed to run integration tests; the proxy itself accepts an upstream RPC URL. The README presents the project under either the MIT or Apache-2.0 license, at the user’s choice.
The README also distinguishes documented features from work still ahead: saved report artifacts, richer application-state assertions, and CI templates are listed as future work. Those should not be mistaken for current documented functionality.
Quick Recap
Best Value
How to assess whether to contribute
- Your work: Consider whether you want to improve fault injection, YAML scenario authoring, chain-reorg simulation, multi-provider testing, assertions, or developer setup. These are areas anchored in the project’s described design rather than a claimed list of open issues.
- Your environment: Expect a Rust 1.80+ setup for installation and Anvil if you plan to run integration tests, according to the README.
- Your collaboration style: The author’s post indicates a preference for manual coding over LLM-assisted coding. Clarify expectations with the author when making contact.
- Your verification: Read the current README and repository activity before relying on a feature or project-status claim; repository contents and the author’s statements can change.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
