XFollowListPeople, ideas and original work on X

Crypto reading list

Crypto security & investigations

Crypto security starts with several different questions. How did stolen funds move? Which rule in a contract failed? How did someone gain access to an account or device? Choose a question below and read a worked example from the person investigating it.

Selected sources
10

People to read

Open the first material, then continue with the author on X. People appear once, grouped by their main reading use and ordered by handle within each group.

4 of 10 people

Audits & incident response

Understand why code fails, how researchers look for bugs and what teams do when a vulnerability puts funds at risk.

  • @gf_256 Luna Tong (cts) Auditor

    Luna Tong explains how researchers approach contract audits and which kinds of findings deserve attention. As cofounder and CEO of Zellic, she writes from inside the audit industry; her technical guides are most useful to readers who already understand code.

    Start with this Web material · zellic.io

    The Auditooor Grindset

    A technical introduction aimed at experienced vulnerability researchers. Start with the categories of contract problems and the discussion of reports; the career and market claims belong to the article’s 2022 context.

    Published . Material checked .

  • @Mudit__Gupta Mudit Gupta Auditor

    Mudit shows how a vulnerability emerges from a particular combination of contract calls and how an incident response unfolds. Read him when you want the mechanism behind a failure, with code and the people’s decisions kept in the same story.

    Start with this Web material · mudit.blog

    A peek inside the MISO war room

    The 2021 MISO story explains why batching and an otherwise reasonable payment function became dangerous together. The later sections show the coordination needed to address the bug; this is a historical incident account.

    Published . Material checked .

  • @pcaversaccio Auditor

    pcaversaccio organizes examples of EVM failures and builds tools for examining what people sign. His collections help a developer move from the name of a bug class to concrete incidents and the code behind them.

    Start with this Code · github.com

    Reentrancy Attacks

    A maintained collection of reentrancy incidents and references. Choose one familiar protocol and follow its linked explanation; the collection brings together others’ findings as well as the maintainer’s work.

    Material checked .

  • samczsun explains serious contract vulnerabilities and the response when funds are already at risk. His writing connects individual bugs to the incentives and continuing work needed to protect a protocol after launch.

    Start with this Web material · samczsun.com

    Higher Bug Bounties Won’t Stop Hacks

    A readable argument about the limits of tests, audits and bug bounties. Use it to ask how a team continues finding and addressing risk after its initial security checks.

    Published . Material checked .

A few bearings for your reading

These field notes explain the people, language and questions you may meet along the way.

XFollowList field note

Meet ZachXBT through an investigation

See what a transaction link establishes and where an investigator needs additional evidence.

XFollowList field note

Follow a claim back to its source

A practical way to read the conversation around an incident on X.

How this list is selected

We selected people through their own investigations, articles, code and talks. Linked public sources connect names or pseudonyms to X accounts. Material dates describe the linked work; check dates describe checking the material and its authorship through the cited sources. Recent X activity is recorded separately and remains unknown where it was not checked. Read case-specific conclusions alongside the evidence and any later updates.