The Ledger
Osero Proposal Sets 15M USDC Base Vault Rate Limit
A proposal dated Nov. 5 would connect Osero’s Ethereum Mainnet and Base liquidity layers and onboard a Gauntlet-curated USDC vault on Base. The proposed 15 million USDC deposit rate limit would refill over time, and BA Labs recommends reducing it to 5 million USDC if the Ethereum Mainnet vault misses its minimum exposure requirement entering the spell.

Seven changes span Ethereum and Base
Stablewatch’s Nov. 5 proposal sets out seven changes across Ethereum Mainnet and Base. It would connect the Osero Liquidity Layer on the two networks through Circle CCTP and onboard the Osero x Gauntlet USDC Prime Vault (ogUSDCb), a Morpho Vault V2, on Base. Stablewatch writes: “Deploy the Osero Liquidity Layer on Base, with a first allocation to a Gauntlet-curated USDC vault, funded from Ethereum Mainnet through CCTP.”
Source forum.skyeco.com
The November 19 Osero spell makes changes 1–2, while the Osero Base payload it relays, executed by the Osero Executor on Base, makes changes 3–7. Osero deployed the Executor, Receiver and Diamond PAU on Base on November 3; the proposal says those contracts are not configured yet.
Ethereum and Base get reciprocal CCTP settings
On Ethereum Mainnet, the proposal enables the CCTP Facet on the Osero Controller and sets the Osero ALM Proxy on Base as the mint recipient. Fee caps are set at a minimum of zero and a maximum of zero. The proposed limit for USDC sent to CCTP is unlimited, while the domain limit has a maximum amount of 10,000,000 USDC and a slope of 50,000,000 USDC per day.
The Base-side CCTP configuration also sets fee caps at a minimum and maximum of zero, an unlimited CCTP limit, and a domain limit of 10,000,000 USDC with a 50,000,000 USDC-per-day slope.
Base vault gets a 15 million USDC deposit rate limit
The Osero x Gauntlet USDC Prime Vault would have a maximum exchange rate of 2 USDC per whole share. Its initial deposit rate limit would have a maximum amount of 15,000,000 USDC and a slope of 10,000,000 USDC per day. This is a rate limit that refills over time, rather than a fixed total deposit cap; withdrawals can replenish the allowance. The withdrawal rate limit would be unlimited.
BA Labs recommends reducing the Base deposit rate limit to 5,000,000 USDC if the Ethereum Mainnet vault misses its minimum exposure requirement entering the November 19 spell.
The Base payload would grant the CONTROLLER role on the ALM Proxy and ALM Rate Limits contract to the Osero Controller on Base. It would also grant ALLOCATOR_ROLE on Osero AccessControls to the Osero AdministeredAgent. The Osero Relayer Multisig and Core Operator Relayer Multisig are named as actors for that agent, with the Freezer Multisig as revoker.
Audits cover the controller, facets and vault
The proposal lists audits for the Diamond PAU components, including the Controller, AccessControls, ALM Proxy, Rate Limits, Beacon, PAUFactory, CCTP Facet and ERC-4626 Facet. It cites ChainSecurity and Cantina reports for versions 1.12.0 and 1.13.0, and says the v1.12.0 facet audits apply unchanged to v1.13.0.
For the PAUInit library, the proposal lists a ChainSecurity report dated November 2, 2026, and says the Cantina report is still pending. ChainSecurity reported no Critical, High, Medium or Low findings and two Informational findings, both corrected. The proposal also lists ChainSecurity and Cantina/Spearbit audits for Morpho Vault V2 and the Morpho Market V1 Adapter V2.
Base execution follows the Ethereum spell
The proposal says the Sky Core spell is scheduled to register the ERC-4626 Facet on Base and register Osero on the Base PAS on November 19. The Osero spell executes once the Sky Core Executive Vote plots it on the Osero StarGuard and the GSM Pause Delay elapses; it carries out the Ethereum actions and relays the Base payload.
When the message arrives on Base, the Osero Receiver forwards the queue call and the Osero Executor queues the payload. Anyone may call execute(actionsSetId) during the Executor’s seven-day grace period, and the proposal says Osero engineering will call it. Osero engineering must complete post-checks 1–5 before any CCTP transfer; post-check 6 is the first transfer.
Sources
- Original source Sky Ecosystem Forum forum.skyeco.com