# \[ARFC\] Core & Base - BTC Correlated Asset Update **URL:** \ **Category:** Governance\ **Created:** [February 4, 2025, 6:34pm UTC](https://governance.aave.com/t/arfc-core-base-btc-correlated-asset-update/20940 "2025-02-04T18:34:59Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![bgdlabs](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/bgdlabs/32/1829_2.png) [@bgdlabs](https://governance.aave.com/u/bgdlabs)\ **Post date:** [March 11, 2025, 3:16pm UTC](https://governance.aave.com/t/arfc-core-base-btc-correlated-asset-update/20940/7 "2025-03-11T15:16:40Z")
A communication involving the listing of LBTC on Aave v3 Base (not affecting Core). > [@\[ARFC\] Onboard rsETH to Arbitrum and Base V3 Instances](https://governance.aave.com/t/arfc-onboard-rseth-to-arbitrum-and-base-v3-instances/20741/9): > > Just after listing, a misconfiguration involving the new eMode including wrsETH and another involving LBTC has been detected, with a race condition between two proposals running in parallel causing the rsETH eMode to have too conservative risk parameters but including on the same eMode both ETH assets (rsETH collateral, wstETH borrowable) and BTC assets (LBTC collateral, cbBTC borrowable). Even if this doesn’t create any immediate risk to the protocol or these assets, this is a highly unexpecte… In what concerns LBTC on Base, there is no type of risk, and the asset will be unfrozen after passing a governance proposal properly segregating the eModes. --- _[View the full topic](https://governance.aave.com/t/arfc-core-base-btc-correlated-asset-update/20940)._