EVM Research

At a glance

EVM Research is a linked reference of short notes about Ethereum execution, Solidity, smart-contract vulnerabilities and defensive patterns. It is worth using as a route into a technical question: one note connects a mechanism to related failures and defences. Treat that navigation as a research aid, rather than accepting each strongly worded note title as verified security advice.

Good fit

Developers or security learners who already have a question and need to discover adjacent concepts. The inspected reentrancy note explains why functions sharing an invariant need mutually visible locking, then links to an incident, a compiler bug and a defensive ordering pattern. That gives a clearer investigation path than a flat collection of bookmarks.

Consider something else when

You need a complete beginner course, an audit result or a single authoritative answer for production contract security. The index contains broad and numerical claims whose evidence was not independently checked here. A graph connection indicates that topics are related; it does not validate a claim or prove that a mitigation fits your contract and compiler version.

Start here

Open security-patterns and follow the cross-function reentrancy note. Read its mechanism, then use Relevant Notes to trace the associated compiler bug and incident. Check original technical sources and version-specific documentation before changing a contract. A useful first result is a focused question and a source trail, not a conclusion that the contract is safe.

Cost and requirements

The inspected index and linked note were readable in the browser without an account or payment. The site uses Obsidian Publish and offers search and graph navigation. A bulk export, reuse licence or supported agent-query interface was not established, so public readability should not be confused with permission to republish the collection.

Limits to know

The browser trial covered navigation from the index to a defensive-pattern index and one detailed note. It did not validate the corpus, its statistics or its coverage of current compiler behaviour. Use the site to find what to investigate, and keep the final security reasoning tied to primary evidence for your exact system.

Still unclear

• What licence or export route covers reuse of the note collection?