Replay Grade v0.1: a request for comments

This page needs no script and no tool to read. Text source: replay-grade-v0.1.md (md5 d83c269ff6ca04e4713755c127457001). The grades of my own claims: the table as a web page, or as text. The scripts that compute them: noter_fiches.py, construire_table.py, test_replay_grade.py (their comments are in French).

Version 0.1, draft of 2026-11-13, revised on 2026-11-14 after a review of the page and of its table (the changes are listed in the last section). Status: request for comments. Nothing here is final, nothing has been sent to anyone, and the criteria below will change if the comments are good.

What this grades

Many projects now publish who can change a smart contract: a key, a multisig, a vote, a delay. Each publication makes claims such as "this contract is controlled by a 3 of 5 multisig" or "the delay is 48 hours". The question here is narrow: what does the page itself let a reader replay? It does not ask whether the claim is true, whether the project is safe, or whether the score is right. A claim can get the best grade and be wrong; a claim can get the worst grade and be right. The grade only says how much work a stranger needs before they can find out.

One grade per claim, never one per product. A page with ten claims has ten grades. There is no ranking between projects and no average.

The four elements

A claim is graded on four elements, each checked on the page where the claim is made:

  1. Command. A complete command or request a reader can paste and run: the tool and its arguments, with the address and the endpoint. A method name alone (eth_getStorageAt) is not a command. A script of a repository counts as a command when the claim names the script and its arguments and the script itself carries the address and the endpoint; the claim then needs the commit the script was run at as its named point of reading, and without it the claim has no named point.
  2. Named point of reading. For chain state, the block number or the slot. The word latest is not a named point. For a web file or an API that has no block, the UTC time of the read, to the minute. For a repository file, a commit hash. For a read of the chain, a time of day is not a named point, whatever the method. A claim whose subject is a commit (the pinned commit is the last one that changed a file) names that commit, which is then also its named point of reading.
  3. Expected result. What the command should print or return, written on the page, so a reader can tell a match from a difference. A value that moves (a timestamp, a live score) is expected to be written as moving, with the field to compare.
  4. Network. For a chain read, the network name and its identifier written on the page: the chain ID for an EVM chain, the genesis hash or the cluster for Solana.

The four grades

A claim that is about no chain (a count of files, a result of a script on a repository) is graded on the same four elements, with the commit as its point of reading and the network element not applicable; it can reach A.

Edge cases

How to apply it in five steps

  1. Copy one claim, with its page and line.
  2. Look for the four elements on that page.
  3. Write the grade and, for each missing element, the one line that would add it.
  4. If you can, run the command and note matches or replay differs, with the time.
  5. Publish the table with the claims you could not grade, typed UNREAD, and the reason.

What I grade first: my own pages

I have graded my own claims first, in public, with the ones that fall to C and D. The table is own-grades-v0.1.md, next to this page, and also as a web page. Summary, read at 09:50Z, on 14 November: the README of the showcase repository at commit a6eb1da and a local copy of the site pages at commit ebec56c:

Three examples from my own pages:

Versioning and comments

This is version 0.1. Any change of a criterion becomes version 0.2 with a dated change list, and old grades keep the version they were given under. I would like comments on five open points: whether a UTC time is an acceptable point of reading for a web file, whether latest should ever count, whether the chain ID should be required when the endpoint address already implies it, whether a claim split in parts should be graded by its weakest part, and whether a script of a repository that carries its own address and endpoint should count as a command. Comments and corrections are welcome by an issue on the showcase repository or by writing to contact@realspap.com. Co-authors are welcome on the criteria; a grade of another project is never published here without that project having been told first and having had seven days to answer.

Changes of 2026-11-14

A review of this page and of its table found points to correct; those about the criteria and the table are applied here, and the grades of the table were computed again.

Back to the dashboard. Not an audit, not investment advice.