What fits your constraints

What your constraints removed

In the order the controls are listed. A vault removed at one step is not counted again at the next, so the two columns on the right always add up to the drop on that line.

209 vaults meet all of it, holding $3.21bn between them.

The constraint costing you the most

How many more vaults would meet everything else if this one alone were switched off. Computed by re-running the whole screen without it, so nothing is promised that a later constraint would remove anyway.

• Takes deposits+134
• Size+66
• Days watched+56

Why a column is a dash

• Takes deposits: read for 450 of 3,029. we have not called maxDeposit on this vault yet.
• Size: read for 2,680 of 3,029. nothing in this vault has a price we can read, so its size is unknown rather than zero.
• Days watched: read for 2,580 of 3,029. we hold no observation of this vault yet, so there is no span to measure.
• Age: read for 2,342 of 3,029. we hold no creation record for this vault, which is common where it was not found from a factory event.
• Risk score: read for 693 of 3,029. not enough of the inputs are read on this vault to score it.
• Worst fall: read for 116 of 3,029. the series is shorter than a quarter, or the figure is the venue’s own over a window it does not state, and neither is a drawdown.
• Crowding: read for 319 of 3,029. crowding needs a per-vault book, and only Hyperliquid and Drift publish one to us.
• Performance fee: read for 87 of 3,029. the fee has not been read from this contract, which is not the same as it being nothing.
• Withdrawable now: read for 393 of 3,029. this vault does not lend, or its free liquidity has not been read.
• Shares its code: read for 303 of 3,029. this vault is not a proxy, or its implementation slot has not been read.
• Named operator: read for 3,029 of 3,029. never: an operator is either linked or it is not.