Clovis private mainnet is now live.
Clovis brings yield, bridging assets, and borrowing against collateral into a single unified account. Deposit across supported chains, move assets seamlessly between them, and use eligible positions to natively borrow on @base in markets built on @morpho.
Explore Clovis at clovis.network
A wallet signature records what a user authorized. For a cross-chain transaction, the protocol must also check whether the chosen route can support the request.
Route liquidity, limits, and availability can change. For transactions that require Clovis authorization, we check the specific request and issue an attestation the contract can verify.
That makes the check enforceable by the contract, rather than something the user has to assume.
A position may be usable across chains, but each route has its own liquidity, limits, and available actions.
Clovis gives users a connected experience across chains while applying the checks each route requires. Users choose what they want to do from one interface, and Clovis handles the checks behind that request.
A wallet signature records what a user authorized. For a cross-chain transaction, the protocol must also check whether the chosen route can support the request.
Route liquidity, limits, and availability can change. For transactions that require Clovis authorization, we check the specific request and issue an attestation the contract can verify.
That makes the check enforceable by the contract, rather than something the user has to assume.
Clovis deposits earn on one chain and back borrowing on another.
Before enabling a route, we review how it handles assets and positions, test its cross-chain accounting, and set limits on exposure.
We built and tested these checks before opening mainnet. Clovis is working with close partners and invited users to strengthen them further as access expands.
We spent much of the past year building Clovis around security.
That meant testing how positions are accounted for across chains and how we detect and handle delayed messages or failed routes.
Since opening mainnet a little over two weeks ago, we have been working with close partners and invited users on real use cases. We are watching how supported routes behave and using what we learn to further strengthen the system as we prepare to invite more people from the waitlist.
The PHP security team is giving advance notice: Upcoming security release Wed, Oct 21st 2026, 14:00UTC, two critical vulnerabilities, both rated CVSSv4 9.2.
PHP users are encouraged to prepare to update. Earlier release if details become public or active exploit evidence.
5/ Over the past year, we built and validated the vault accounting, cross-chain messaging, and recovery paths behind these connections. We are now opening mainnet to invited users with Earn, Bridge, and Borrow.
Explore Clovis at clovis.network.
4/ Say you have a deposit in a supported Earn vault on Ethereum and want to borrow on Base. An eligible vault position can back that borrowing while the underlying asset remains in its vault. Through Clovis, you manage the Ethereum deposit and the borrowing on Base in one account.
3/ An eligible Earn position can become collateral in a supported lending market on Base built on Morpho. This is composability in practice: a position created through one protocol becomes usable in another, even across chains. Users can keep the vault position and access borrowing on Base.
2/ Clovis connects vaults on Base, Ethereum, BNB Chain, and Sei to one account on the Clovis hub on Base. Supported assets can remain in their source-chain vaults while users manage their positions, collateral, and borrowing through that account while earning yield from across the board.
1/ We started with a problem: a vault deposit on one chain and a lending market on another are not inherently composable or fungible with one another. An individual can hold a position that the market cannot use, and instead requires the user to manually do withdrawals, swaps and bridging. We built Clovis to connect eligible positions across that boundary.
Imagine your bank opening a new branch and asking you to fund a separate account there.
That is how onchain lending often grows. Each new chain starts with its own market and has to attract liquidity from scratch.
Clovis connects supported chains to shared liquidity.
You can have capital across your accounts and still need to top up the one holding your trade.
Keeping spare funds in every venue ties up capital before you know where you will need it. Putting those funds to work elsewhere means you may need to withdraw and transfer them before they can be used.
With Clovis, we want users to keep capital earning while making it easier to access when they need it elsewhere.
We should pay more attention to what happens between deposits.
You find somewhere to earn, somewhere to borrow, somewhere to trade. Then you have to move capital between them when you need it.
That is a big part of what we want to solve with Clovis.