# SIP-0093: Disable SOV and BPro as Lending-Pool Collateral **URL:** \ **Category:** Bitocracy\ **Created:** [June 19, 2026, 11:35am UTC](https://forum.sovryn.com/t/sip-0093-disable-sov-and-bpro-as-lending-pool-collateral/3578 "2026-06-19T11:35:39Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![yago](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.sovryn.com/yago/32/124_2.png) [@yago](https://forum.sovryn.com/u/yago)\ **Post date:** [June 19, 2026, 11:35am UTC](https://forum.sovryn.com/t/sip-0093-disable-sov-and-bpro-as-lending-pool-collateral/3578/1 "2026-06-19T11:35:39Z")
* * * ## SIP: ‘0093’ Title: Disable SOV and BPro as Lending-Pool Collateral Author: Edan Yago (@YagoBit) Status: Draft Track: Contract Created: 2026-06-18 # SIP-0093: Disable SOV and BPro as Lending-Pool Collateral ## Summary This SIP disables SOV and BPro as collateral assets for new Sovryn lending-pool borrowing and margin-trading positions. The change applies to both Torque loans and fixed-term margin-trading loan parameters on every lending pool where those collateral assets are currently enabled. The proposal does not remove SOV or BPro from the protocol token allowlist, price feeds, or swap support. Existing positions backed by SOV or BPro remain open and continue to be repayable, collateral-manageable, closeable, rollable where applicable, and liquidatable under the current protocol rules. ## Motivation SOV and BPro are volatile collateral assets. Keeping them available as collateral for new borrowing and margin trading exposes lending pools to collateral drawdown risk while providing limited strategic value for new position creation. Removing them from the list of accepted collateral assets reduces the risk surface of lending pools without forcing existing borrowers or traders into an immediate unwind. The intended outcome is conservative: stop new exposure from being created, while allowing current exposure to resolve naturally through repayment, closure, rollover mechanics, or liquidation. ## Proposed Changes For each enabled lending-pool loan token, call: ```auto disableLoanParams(address[] collateralTokens, bool[] isTorqueLoans) ``` The SIP disables active SOV and BPro collateral loan parameters for both modes: - `isTorqueLoans = true`: Torque borrowing - `isTorqueLoans = false`: margin trading The live-state check at draft time showed the following enabled parameters: | Loan token | SOV Torque | SOV Margin | BPro Torque | BPro Margin | | --- | --- | --- | --- | --- | | iXUSD | Enabled | Enabled | Enabled | Enabled | | iRBTC | Enabled | Enabled | Enabled | Enabled | | iBPRO | Enabled | Enabled | Not enabled | Not enabled | | iDOC | Enabled | Enabled | Enabled | Enabled | | iDLLR | Enabled | Enabled | Enabled | Enabled | | iUSDT | Not enabled | Not enabled | Enabled | Enabled | The RUSDT/iUSDT lending pool is not currently exposed as a borrow market in the Sovryn app UI, but its BPro Torque and margin loan-parameter entries are still active onchain. This SIP disables those active onchain entries as a defensive cleanup action. The proposal builder checks live `loanParamsIds` and protocol loan-param activity before encoding actions. Already-disabled or absent pairs are skipped so the proposal does not include calls that would revert. ## Technical Details Each loan token stores local collateral/mode pointers in `loanParamsIds[keccak256(collateralToken, isTorqueLoan)]`. Calling `disableLoanParams` on the loan token deletes those local pointers and forwards the matching loan-param IDs to the Sovryn protocol, where the corresponding `LoanParams.active` flags are set to `false`. Opening or increasing a borrow or margin trade goes through `LoanOpenings._initializeLoan`, which requires the referenced loan params to be active. Once disabled, SOV and BPro can no longer be used to create new positions or increase existing positions under the disabled loan params. Existing loans store their original `loanParamsId`. Maintenance and closure paths require the loan to be active and the params to exist, but they do not require `LoanParams.active == true`. Therefore, existing positions remain operational: - borrowers can repay or close with deposit; - margin traders can close with swap while token swap support remains enabled; - borrowers can add collateral; - borrowers can withdraw collateral up to the normal max-drawdown limit; - unhealthy positions can be liquidated; - price feeds and swap support remain available for closing and liquidation flows. ## Implementation This SIP is executed through `GovernorAdmin`, because `disableLoanParams(address[],bool[])` on each loan token is gated by `onlyAdmin` and the relevant loan-token `admin()` is the `TimelockAdmin` controlled by `GovernorAdmin`. The expected actions are: ```auto LoanToken_iXUSD.disableLoanParams([SOV, SOV, BPro, BPro], [true, false, true, false]) LoanToken_iRBTC.disableLoanParams([SOV, SOV, BPro, BPro], [true, false, true, false]) LoanToken_iBPRO.disableLoanParams([SOV, SOV], [true, false]) LoanToken_iDOC.disableLoanParams([SOV, SOV, BPro, BPro], [true, false, true, false]) LoanToken_iDLLR.disableLoanParams([SOV, SOV, BPro, BPro], [true, false, true, false]) LoanToken_iUSDT.disableLoanParams([BPro, BPro], [true, false]) ``` Token addresses: - SOV: `0xEFc78fc7d48b64958315949279Ba181c2114ABBd` - BPro: `0x440cd83c160de5c96ddb20246815ea44c7abbca8` Loan-token targets: - iXUSD: `0x8F77ecf69711a4b346f23109c40416BE3dC7f129` - iRBTC: `0xa9DcDC63eaBb8a2b6f39D7fF9429d88340044a7A` - iBPRO: `0x6e2fb26a60da535732f8149b25018c9c0823a715` - iDOC: `0xd8D25f03EBbA94E15Df2eD4d6D38276B595593c1` - iDLLR: `0x077FCB01cAb070a30bC14b44559C96F529eE017F` - iUSDT: `0x849c47f9c259e9d62f289bf1b2729039698d8387` ## Risks ### Risks introduced - **Reduced borrower flexibility.** Users can no longer open new loans or margin trades using SOV or BPro collateral. - **Integrator assumptions.** Frontends, bots, and analytics that assume SOV or BPro are valid collateral options must update their availability checks. ### Risk mitigants - **Existing positions are not forcibly closed.** The change disables loan params for future use but does not delete loan params or close active loans. - **Close and liquidation paths remain available.** SOV and BPro remain supported tokens for swaps and pricing, so margin close and liquidation flows are not blocked by this SIP. - **Reversible for future positions.** Governance can re-enable the collateral assets later by setting up replacement loan params, although this SIP is intended as a risk-reduction measure rather than a temporary pause. ## Validation The implementation includes on-chain/fork validation for the generated proposal arguments: - verify every encoded pair has an active loan-param entry before execution; - verify disabled or absent pairs are skipped; - verify the generated target set matches the mainnet enabled-pair inventory above; - on a mainnet fork, impersonate `TimelockAdmin`, execute the encoded calls, and confirm the local `loanParamsIds` pointers are deleted while protocol loan params become inactive; - confirm SOV and BPro remain supported tokens after the disable calls. ## License Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). ---
**Author:** ![TM1](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.sovryn.com/tm1/32/126_2.png) [@TM1](https://forum.sovryn.com/u/TM1)\ **Post date:** [June 23, 2026, 2:56pm UTC](https://forum.sovryn.com/t/sip-0093-disable-sov-and-bpro-as-lending-pool-collateral/3578/2 "2026-06-23T14:56:47Z")
1. > [@Community Concerns - Public Disclosure #1 - Exchequer RBTC to OKEx](https://forum.sovryn.com/t/community-concerns-public-disclosure-1-exchequer-rbtc-to-okex/3545): > > On Dec 04 2025 09:35:49 AM a [transaction sent 12 BTC](https://rootstock.blockscout.com/tx/0xf09e5dde0ab0ac7bf436613b39d1a2d7e3b2a2d9953826569de9e8c953a7d1d6?tab=index) from [Exchequer](https://rootstock.blockscout.com/address/0x924f5Ad34698fD20C90fe5d5a8A0ABD3b42dC711?tab=index) to [0xD9ECb390a6A32aE651D5C614974C5570c50a5D89](https://rootstock.blockscout.com/address/0xD9ECb390a6A32aE651D5C614974C5570c50a5D89?tab=index) (from here on 0xD9). On Dec 04 2025 21:04:32 PM [0xD9 through pow-peg transferred 12 BTC](https://rootstock.blockscout.com/tx/0x28f7cbc5d4f4f1f74fd064434594479348dc8af5f9e11bf5aac89eac2f4ed82a) to Bitcoin address [1BVZ13Q7C66UUKsUUq3ReaauJsH9JXxQam](https://www.blockchain.com/explorer/addresses/btc/1BVZ13Q7C66UUKsUUq3ReaauJsH9JXxQam) On 07 Dec 2025 07:46:54 [1BVZ transferred 11.99899292 BTC to address bc1qccy9mn9h2ed6sjf7pvx7af6zc7zax0qaegadw5](https://www.blockchain.com/explorer/transactions/btc/45f6e40a5c46687fbcd08f14245f86d6198c406b2a16e7dde768154782d2b173). Address [bc1…adw5](https://www.blockchain.com/explorer/addresses/BTC/bc1qccy9mn9h2ed6sjf7pvx7af6zc7zax0qaegadw5) is tagged as [OKEx wallet](https://bitinfocharts.com/bitcoin/address/bc1qccy9mn9h2ed6sjf7pvx7af6zc7zax0qaegadw5-nodusting) and also shows many [sweep transactions](https://www.blockchain.com/explorer/transactions/btc/377d737f69f99b5a4b9c4f927205f34ab97399d5309ee988e85ea81437831db5) with other addresses tagged as [OKEx wallet](https://bitinfocharts.com/bitcoin/address/bc1quq29mutxkgxmjfdr7ayj3zd9ad0ld5mrhh89l2). This … 1. > [@Community Concerns - Public Disclosure #2 - Founding Member SOV Collateral Loan](https://forum.sovryn.com/t/community-concerns-public-disclosure-2-founding-member-sov-collateral-loan/3546): > > Starting on Feb 17 2026 1:19:47 AM just before the announcement from @yago at 2:10 PM [https://forum.sovryn.com/t/staking-update-temporary-adjustment-to-staking-rewards](https://forum.sovryn.com/t/staking-update-temporary-adjustment-to-staking-rewards) 4 transactions totaling over 7 million SOV borrowed as much RBTC as they could from [sovrynProtocol in the largest SOV collateral loan ever opened in Sovryn’s history](https://rootstock.blockscout.com/advanced-filter?transaction_types=ERC-20%2CERC-721%2CERC-1155%2CERC-404%2Ccontract_creation%2Ccontract_interaction&methods=0x2ea295fa&methods_names=borrow&amount_from=10000&token_contract_address_hashes_to_include=0xEfC78FC7D48B64958315949279bA181C2114abbD&token_contract_symbols_to_include=SOV&to_address_hashes_to_include=0x5a0D867E0D70FCc6ADe25c3f1B89d618b5B4EaA7). The largest loan before this was against just 111,890 SOV. This loan occurred from 4 addresses that have all been tied to a founding member who currently controls al… 1. > [@Community Concerns - Public Disclosure #3 - Exchequer Total Assets Withdrawn](https://forum.sovryn.com/t/community-concerns-public-disclosure-3-exchequer-total-assets-withdrawn/3562): > > In the last [community call](https://www.youtube.com/watch?v=_KhhwgrOFJo) it was stated [Community Concerns #1](https://forum.sovryn.com/t/community-concerns-public-disclosure-1-exchequer-rbtc-to-okex) transfer of 22BTC from Exchequer to OKEx ([Gemini?](https://www.oklink.com/bitcoin/address/bc1qccy9mn9h2ed6sjf7pvx7af6zc7zax0qaegadw5)) was for the movement of FastBTC liquidity. It’s important to look at the assets that were in the Exchquer multisig address just 4 months ago and what’s in there now. Here’s why the movement of Exchequer RBTC cannot solely be from FastBTC or likely at all. Exchequer Token Balances The following balances were accumulated over years and currently are 0 in the [Exchequer multisig wallet](https://rootstock.blockscout.com/address/0x924f5Ad34698fD20C90fe5d5a8A0ABD3b42dC711?tab=tokens) …