| keys | No | Who can move the money, read from the contract. `holds` is multisig, eoa, contract or timelock; `signaturesRequired` is how many a multisig needs; `actsAlone` is true where ONE party can act with no second signature, which covers a single key AND a multisig with a threshold of one — read that rather than the word multisig. `canBeHalted` is null where neither pause function answered, which may mean nobody can stop the vault or may mean its pause is behind a name we do not read — do not read a null as nobody. `notice.basis` is the field to check before trusting a delay: `measured` means we read one, `not-a-timelock` means the controller we read is not a timelock and we do not separately search for one behind it, `unread` means we did not ask. Null means we have not read this vault’s control at all, which is not the same as nobody controlling it. | |
| name | No | The vault’s name as the venue publishes it. Their words, and two venues may use the same one. | |
| risk | No | The band, the components it was measured from, and `dimensions`. READ `dimensions` BEFORE THE BAND. The band covers market, liquidity, concentration and operating risk and **does not contain the controller at all** — `bandCovers` says so on the object. A vault can read `low` while a single key can empty it, which is exactly what two did. Each dimension carries its own level, the components behind it, and `outsideTheBand`; `controller` and `evidence` are both outside it. A null level is UNREAD and never low. THERE IS NO OVERALL FIGURE and there will not be one: a composite would be the number every reader quotes and none can check. (This used to tell a caller to read `bandRange` first. That field is on the FULL vault document and this tool has never returned it, so the instruction could not be followed; the full document is one link away in `full`.) | |
| says | Yes | The finding in one sentence. Where we cannot say what a holder earned, it says that plainly rather than reporting the venue’s own figure as ours. | |
| slug | Yes | The vault this answer is about, read back so it cannot be attached to the wrong one. | |
| earned | No | Advertised against realised, with the ratio, the verdict and the window. TWO SEPARATE QUESTIONS live here and both must be read: `comparability` is whether the two rates can be set against each other at all, and `representativeness` is whether the result is worth planning around — `typical` where the movement is spread across the window, `event-dominated` where ONE step carries the return, `unknown` where we did not look at the shape. A vault can be `comparable` AND `event-dominated` at once: one was, with a single day accounting for 52% of the movement its return comes from, and a reader seeing only `comparable` planned around a figure that describes an event. `biggestStepShare` is that day’s share of total movement. Null where we have too few price points to say. | |
| operator | No | Who runs it, as the venue names them. | |
| cannotSee | Yes | What we could not establish. Empty means every check ran. | |
| capitalUsd | No | What the vault holds, in US dollars, at `capitalAsOf`. Null where we cannot price the underlying — unread, never zero. | |