> For the complete documentation index, see [llms.txt](https://docs.efficientdex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.efficientdex.com/reference/deployments.md). # Deployments Where Efficient is deployed: Base and Katana, each chain's first Everlong vault, the pending redeployment, and the contracts whose addresses will be published. **Efficient is deployed on Base and Katana, with one Everlong vault on each chain.** Each vault is financed through Morpho Blue. Both chains still run earlier code until a pending redeployment ships. See [Status](#status). ## Chains **Each chain has its own Efficient deployment.** Everlong runs the first pool on each chain as pool operator. The table shows each vault's settings for the redeployment, as the deployment manifests set them. | | Base | Katana | | --------------------------------- | ----------------------------------- | --------------------------------- | | Chain ID | 8453 | 747474 | | Pair | cbBTC against USDC | vbWBTC against vbUSDC | | Share | Everlong cbBTC (`ev.cbBTC`) | Everlong vbWBTC (`ev.vbWBTC`) | | Lending market | Morpho Blue, liquidation LTV 0.86 | Morpho Blue, liquidation LTV 0.86 | | Price feed | Chainlink cbBTC/USD and USDC/USD | Chainlink WBTC/USD and USDC/USD | | Staleness limits | 1 hour for cbBTC, 25 hours for USDC | 25 hours for each | | Sequencer check | Uptime feed, with a 1-hour grace | None: Katana has no uptime feed | | Leverage quote | On from activation | Off | | Deposit allowlist | On | On | | Per-swap cap | 1,000,000 USDC | 250,000 vbUSDC | | Debt and supply caps at the venue | 1,500,000 and 2,000,000 USDC | 750,000 and 250,000 vbUSDC | | Junior deep window | 2 hours | 25 hours | The two vaults share all their other pool settings. These include the Everlong hook's strategy settings, the credit settings and the 10-day governance and upgrade delays. [The Everlong strategy](https://docs.foreverlong.io/everlong/everlong-strategy) lists the hook's settings. [Price feeds and oracles](/how-pools-work/price-feeds-and-oracles.md) and [Tranches](/use-efficient/provide-liquidity/tranches.md) explain the feed and tranche rows. Neither vault caps deposits itself. So a proportional deposit is limited only by what its lending-market legs can take. For these vaults, those limits are: * the debt and supply caps above * the cash the Morpho Blue market has to lend * the borrow-rate ceiling A book with no debt and no supply takes a deposit of any size. The share-sized entry, `mintProRata`, ships closed on both vaults. That's because `mintProRataCap` stays at zero until the pool operator sets it. Both vaults' settings can still change before the redeployment. That includes each vault's [genesis mode](/run-a-pool/configure-a-pool.md#genesis-modes), and Katana's BTC price feed, staleness limits and leverage setting. ## Katana **vbWBTC and vbUSDC are Katana's Vault Bridge versions of WBTC and USDC.** The pool prices them with Chainlink's WBTC/USD and USDC/USD feeds. No feed on Katana tracks either token against the asset it bridges. So the pool prices each token at par with that asset. **In the redeployment, Katana's vault ships with leverage off.** Its feature bit 5, `FEATURE_LEVERAGE`, is clear. So the Everlong hook never arms and quotes no leverage fill. Every swap there fills on the curve. Deposits, borrowing, lending and collateral maintenance run as they do on Base. The hook's leverage rules were modelled on a BTC feed like Base's. But Katana's WBTC/USD feed updates only after a 0.5% move or 24 hours. As pool operator, Everlong can turn leverage on later by setting the bit. ## Status **These docs describe the contracts at commit `92c77ac` of 22 October 2026.** They'll reach both chains in one full redeployment, which hasn't shipped yet. The redeployment replaces every contract, including the factory, the financing router and the price feed. None of those three can be upgraded once deployed. Until the redeployment ships, each chain runs an earlier deployment. Its code differs from these docs in places. Base's pool stack dates from 11 September 2026, and its tranche contracts were redeployed on 21 September 2026. Katana's stack dates from 18 September 2026. [Security and audits](/reference/security-and-audits.md) lists the code each published report reviewed. It also covers how later code reaches pools. ## Contracts on each chain **Each chain has contracts shared by all its pools, and a set for each pool.** [Smart contracts](/reference/smart-contracts.md) covers each contract's role, key calls and events. | Contract | Deployed | | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | | Factory (`FLAMMFactory`), which creates the financing router (`MMRouter`) | Once per chain | | Pool implementation (`FLAMMFront`, which deploys the full `FLAMM`) | Once per chain | | Morpho Blue account deployer (`MorphoAccountDeployer`) | Once per chain | | Price feed (`PriceFeed`) | Once per chain | | Lens (`FLAMMLens`) and Tycho adapter (`FLAMMTychoSwapAdapter`) | Once per chain | | Linked libraries: the pool's, the financing router's, and the Everlong hook's `LeverageLib` and `EverlongOpsLib` | Once per chain, with the code that links them | | Pool (`FLAMMProxy`), its authority contract (`EverlongCore`) and deposit allowlist | Once per pool | | The pool's hooks (`EverlongHook` in an Everlong vault) | Once per pool | | Morpho Blue account (`MorphoBlueAccount`) | Once per pool, loan asset and venue type, in a pool with a Morpho Blue lending market | | DEX aggregator, asset router, `PoolSwapAdapter` and entry market | Once per pool | | Tranche controller and its senior and junior tokens | Once per pool | In the Morpho Blue account row, a loan asset is a token the pool can borrow, such as the other token in its pair. For the two Everlong vaults, that's USDC on Base and vbUSDC on Katana. A pool created later by another pool operator brings its own per-pool contracts. It can also name a different price feed. Not every pool has a lending market, a deposit allowlist, the periphery or tranches. ## Addresses **Contract addresses for both chains will be published here when the redeployment ships.** Addresses differ between chains, because each chain has its own factory. A pool's address follows from its factory, creator, salt and initial settings. Once they're published, [Roles and governance](/run-a-pool/roles-and-governance.md) shows how to confirm that a pool came from a chain's factory, and who controls it. ## Live values **Integrators read a pool's live values onchain, not from this page.** A pool operator can change many of a pool's settings after deployment. The lens's `config(pool)` returns a pool's dials, limits, price band and per-swap cap. The lens's `identity(pool)` returns the factory, financing router, price feed, hooks and roles a pool uses. [Roles and governance](/run-a-pool/roles-and-governance.md) covers who can change each setting, and the notice each change gets.