Vault pool
On this page
Lista’s holder boost follows a 7-day weighted average of the LISTA your vault holds, so a freshly funded vault takes about a week to reach full Tier 1. To close that gap, the protocol keeps a vault pool: vaults it creates and funds with the Tier-1 LISTA ahead of time, so their 7-day ramp is already under way before anyone asks for one.
What you get when you create a vault#
- The pool has stock: you receive the oldest pool vault. Its LISTA is already in place and its 7-day average is already climbing.
- The pool is empty: a fresh vault is created at an address derived from your wallet and funded in the same transaction. Its boost ramps from zero over about 7 days.
- Either way it is one transaction with nothing to approve. The vault starts with no positions; you supply and borrow through it afterwards.
- If you already qualify for Tier 2, a pool vault is topped up from 10,000 to 50,000 LISTA in that same transaction.
- Adding a vault works the same way. An extra vault (see Multiple vaults) also takes the oldest pool vault while there is stock; its Tier-2 top-up depends on the vlLTP that vault’s number needs.
See it before you create#
The Dashboard’s setup guide tells you which vault you are about to get and how far along its boost is:
| The guide says | Meaning |
|---|---|
| You’ll receive vault 0x… | A pool vault (the current head of the pool). |
| Will be created at 0x… | A fresh vault at your own predicted address. |
| Tier 1 boost immediately | The pool vault has held its LISTA for 7 days or more. |
| Tier 1 in ~X | Still ramping. 7 days minus the time since it was funded, measured in chain time. |
| Allocation is currently full | The pool is empty and the treasury can’t fund a fresh vault right now. You can still create and request later. |
- Funded into the pool
- Monday 08:00
- You create your vault
- Thursday 13:00 (3 d 5 h later)
- Ramp time left
- 7 d − 3 d 5 h
- Setup guide shows
- Tier 1 in ~3d 19h
It is fully yours#
Once handed out, a pool vault works exactly like a freshly created one: only you act through it, its LISTA is ring-fenced the same way, and the same withdraw and inactivity rules apply, with your activity clock starting when you receive it. The one difference is its address, which is not derived from your wallet.
Before it is handed out#
An unassigned pool vault is owned by the protocol’s factory contract. Nobody can open positions in it, it can’t be locked, and it is exempt from inactivity reclaim, so its ramp isn’t lost while it waits. Each pool vault is handed out once, to whoever creates or adds a vault next, and never returns to the pool.
Keeping the pool stocked#
Governance refills the pool in batches as vaults are handed out, aiming to hold roughly a week of new vaults. Pool vaults are funded from the same treasury LISTA as every other vault, so the pool is kept small: LISTA waiting in it isn’t boosting anyone yet.
- Every refilled vault starts its own 7-day ramp when it is funded. Right after a busy period, the next vaults handed out may be only partly ramped.
- If the pool runs out, creating or adding a vault simply falls back to a fresh vault. Nothing ever waits on the pool.
- Pool vaults hold no positions and earn nothing while they wait; only their LISTA balance ages.
Check the pool yourself#
The pool is fully on-chain. These read-only calls on the vault factory show its state:
| Call | Returns |
|---|---|
poolRemaining() | How many unassigned vaults are in the pool. |
nextVault() | The vault the next creation receives; the zero address when the pool is empty. |
poolVaults() | Every unassigned pool vault in hand-out order, with the time each was funded. |
pooledAt(vault) | When a pool vault was funded; 0 once it has been handed out. |
The factory address is listed under Contract deployment. The Dashboard’s setup guide reads the same calls to show you which vault you will get.
Retired pool vaults#
Governance can take unassigned vaults out of the pool and return their LISTA to the treasury, for example when the budget changes or before a contract migration. It takes the newest ones first. A retired vault is left inert: it is never handed out and holds nothing. Vaults already handed out are never affected.