0x962228a9…9255sent to0xbeccb6bb…9bf6·#23,842,385·view on Etherscan
# Migrate DBR Helpers to New TriDBR Pool
# Proposal to Migrate DBR Helpers to New TriDBR Pool
Forum Post: https://forum.inverse.finance/t/migrate-dbr-helpers-to-new-tridbr-pool/627
## TL;DR
* FiRM helper contracts (ALE, PendlePTHelper, DbrHelper) currently route via the old TriDBR pool.
* Liquidity is migrating to the new TriDBR pool, so we’re upgrading helpers to use it.
* This proposal:
* Enables the new helper contracts,
* Executes a one-shot migrator to copy configuration from the old ALE,
* Then disables the legacy helpers.
* No changes to market parameters or user positions, this is purely a routing / infra upgrade.
## Background
To improve the FiRM UX, we use several helper contracts that abstract common flows such as:
* Buying/selling DBR
* Leveraging and deleveraging positions (ALE)
* Interacting with Pendle PT markets
Today, these helpers have hard-coded routing that assumes DBR–DOLA–INV liquidity is in the [old TriDBR](https://etherscan.io/address/0xc7de47b9ca2fc753d6a2f167d8b3e19c6d18b19a) Curve pool. As liquidity is being migrated to the [new TriDBR](https://etherscan.io/address/0x66da369fc5dbba0774da70546bd20f2b242cd34d) pool, the existing helpers would increasingly route through a shallow / deprecated pool, degrading execution and UX. To avoid this, we deploy updated helpers that integrate with the new pool:
## Objective
Update FiRM infra so that:
* All helper flows (ALE, DBR selling, Pendle PT helper flows) use the new TriDBR pool.
* Governance retains ownership/control of the new helper contracts.
* Legacy helpers are cleanly disabled to avoid confusion or mis-routing.
This proposal only:
1. Enables the new ALE contract on the borrow controller,
2. Executes a migration contract that:
* Claims pending gov on the new helpers,
* Copies ALE market configuration from the old ALE,
* Re-approves FiRM markets on the new DbrHelper,
3. Transfers governance back to DAO gov,
4. Disallows the old helpers.
No FiRM market parameters, user escrows, or DBR logic are changed.
## New Contracts:
* ALE: [0x39D167Fe676EFC3be49bE874a37349A5D89f9058](https://etherscan.io/address/0x39d167fe676efc3be49be874a37349a5d89f9058#code)
* PendlePTHelper: [0x719C47071bea36fD2b2287bBe6efa872A594Fb78](https://etherscan.io/address/0x719c47071bea36fd2b2287bbe6efa872a594fb78#code)
* DbrHelper: [0x3363Ad5780316Fd5180Bb9F34297B533fb9cB335](https://etherscan.io/address/0x3363ad5780316fd5180bb9f34297b533fb9cb335#code)
* Migration Contract: [0x043646A09FA89a1d8f48788008E70299BB269855](https://etherscan.io/address/0x043646a09fa89a1d8f48788008e70299bb269855#code)
The Migration contract:
* Reads the current ALE market configuration from the legacy ALE,
* Sets the equivalent markets on the new ALE,
* Calls approveMarket on the new DbrHelper for the same set of markets,
* Handles pending gov for both new ALE and new DbrHelper.
## On-Chain Actions
The governance proposal will perform the following actions:
1. Enable new helpers on the borrow controller
* Allow the new ALE contract to borrow / operate as helpers on FiRM (same permissions as the legacy helpers).
2. Execute the migrator
* Call `migrate()` on the migration contract
* This:
* Claims pending gov on the new ALE and DbrHelper,
* Copies ALE markets from the old ALE to the new ALE,
* Calls `approveMarket` for all relevant FiRM markets on the new DbrHelper,
* Sets pending gov of both contracts back to DAO governance.
3. Accept governance on new helpers
* Governance (GOV) accepts ownership / gov role on:
* ALEV2
* DbrHelper
4. Disable legacy helpers
* Remove / disallow the following legacy helper contracts from the borrow controller:
* Old ALE
* Old Curve Helper