Pick a sort with the sort chips. Each sort answers a different question. No sort is a risk score. The last column follows the sort, and its header names what it shows. Below the table, select 10, 20 (default) or 50 rows for each page, and use Previous and Next to change the page.
| Sort | Question it answers | Weak point |
|---|
| Rollout stage | What reaches mainnet next, and what just reached it? (default) | Only SIMDs with feature gates move by on-chain state. The other SIMDs sort by stage and impact. |
| Discussion | Where is the debate now? | It counts the volume of discussion. A small proposal with a long thread ranks high. |
| Last update | What changed most recently? | Every edit counts, also a typo fix. |
| SIMD number | Which proposals are newest by number? | The number shows nothing about importance. |
Rollout stage. Each SIMD goes into the first group that matches. The groups have a fixed order and no weights. Inside a group, rows sort by impact (high first), then discussion heat, then SIMD number.
Discussion. score = heat + stage + impact + impl, rounded to one decimal. The heat term is the discussion heat.
| Term | Weights |
|---|
| heat | sum over open SIMD PRs of participants × log₂(1 + comments + reviews), halved for every 30 days since the PR's last activity |
| stage | in review / idea / draft 12 · accepted 10 · live 3 · stagnant / withdrawn 0 · +8 while an open PR touches the SIMD |
| impact | high 15 · medium 6 · low 0 (curated in classifications.json) |
| impl | merged implementation PR 4 · any tracked implementation PR 2 · none 0 |
Last update. The date is the last change to the proposal file or the last activity on its SIMD PRs, whichever is later.
Stage. The stage comes from the proposal file's status. One exception: when every gate of a SIMD is active on mainnet, the SIMD counts as live, and the row says “stage from gate”. Files often lag: some SIMDs that are live on mainnet still say Review or Draft.
Feature gates. Keys come from three places: the proposal's feature: list, Agave's feature-set crate (a gate whose description names the SIMD), and Firedancer's feature map (name and implemented flag only). Each key is read on mainnet, testnet and devnet when the page is built. M T D badges: filled = every gate active, outlined = some gates active, orange = queued. Activation dates come from the block time of the activation slot.
Implementation PRs. Every PR in each client repo is listed once; each later run reads only the PRs updated since the last run. A PR counts when its title names a SIMD (“SIMD-0504”, “SIMD504”, “simd 504”). The line under the header shows each repo's status.
Which client implemented it. “impl: Agave ✓ · Firedancer (WIP)” names each client with evidence. Done: a merged PR, Firedancer's feature map marking every gate implemented, or “Implemented” in the proposal file's development: list. In progress: an open PR, a partial feature map, or other text such as “WIP”. Point at a client name to see its evidence.
Freshness. The page is rebuilt every 4 hours. A banner appears when the page or the implementation PR list is more than 9 hours old, or when a cluster did not answer. The change digest covers a rolling 7-day window.