Five steps from a fresh wallet to a live LayerCover vault.
If you plan to run the vault from a Safe multisig in production, connect the Safe directly when you sign in. It makes the rest of the flow simpler.
Sign in to the curator dashboard with your wallet. Pick the network you want to deploy on. You'll land on the Vaults list, which will be empty if this is your first vault.
Click Deploy. You'll see one form. Fill in:
500 = 5% / year). Adjust if the auto-filled value doesn't match what you want.Below the form, a status banner shows the predicted address for your new vault. It starts amber because the LayerCover team hasn't approved that address yet.
Copy the predicted address and send it to us. Once we approve it, the banner flips green and the Deploy button activates. Refresh isn't required; the page polls every few seconds.
Sign one transaction. In that single transaction:
Tx receipt is parsed; the success card shows the three new addresses (Morpho vault, LayerCover wrapper, gate) with explorer links.
Day-to-day vault management (adapters, caps, timelocks, allocations, sentinels) is done through the Morpho Curator UI. The LayerCover wrapper is transparent to it; everything you'd normally do on a Morpho V2 vault works the same way.
That also includes setting your management fee and performance fee on the underlying Morpho V2 vault from the same interface. These are independent of the senior-to-junior premium rate, which is the only LayerCover-specific lever (see Premium control).
Two small post-launch tasks are worth doing on day one:
lcSEN and lcJUN receipt tokens for each deposit. Transfer the full balance of both to the burn address 0x000000000000000000000000000000000000dEaD. Burning makes the seed permanent: no one can later redeem the tokens and unwind the share-price stabilisation. The LayerCover-side deploy scripts do the deposit-and-burn automatically when you launch through the team; if you launched via the curator app yourself, run it as a follow-up transaction.It's a continuous rate paid by senior lenders to junior lenders, expressed as % per year. At 5%, senior gives up 5% / year of underlying yield in exchange for first-loss protection; junior receives that 5% on top of the underlying yield. See Premium control for the trade-off.
Yes, if you kept it on your side at deploy. The change applies immediately and accrues from the next block; there's no on-chain delay. If you want a delay (e.g. a 7-day announcement window), point the role at a timelock contract you control.
No. The wrapper is permanently bound to the Morpho vault it was launched against. If you ever need to start over, you spin up a fresh wrapper and migrate.