Reports

What mainnet actually looks like.

Periodic measurements of Solana mainnet, taken by asking the cluster directly rather than reading anyone's documentation. Every report carries its date in the title, states its method, publishes its data, and ships the script that produced it.

How these are made

A report goes out when there is a number worth knowing that nobody has published, and it only goes out with the means to check it. That means three things, every time:

  • The date is in the title. These numbers describe one moment on a chain that moves. A figure without its date is a claim about today that was true last spring.
  • The method is written down before the conclusion. How the sample was drawn, what was counted, what was assumed, and — at length — what the result does not support.
  • The data and the script ship with it. Aggregates as CSV under CC BY 4.0, and a dependency-free script you can run against your own endpoint to get your own numbers.

The upgradeability census repeats quarterly. Where a report measures something that changes, the interesting result is rarely the first reading — it is the second one.

Check your own program

VaultLint reads your source, and with --mainnet it also reports who can replace what you have deployed. Free and open source.

Get VaultLint on crates.io