[VPD 1116] : Risk Parameter Update & Asset Off-boarding#706
Merged
Conversation
fred-venus
reviewed
May 14, 2026
|
|
||
| const receipt = await tx.wait(); | ||
| checkGasLimit("propose", receipt.gasUsed); | ||
|
|
Contributor
There was a problem hiding this comment.
i believe similar logic has been added here https://github.com/VenusProtocol/vips/pull/708/changes
…of per-command checks
fred-venus
previously approved these changes
May 14, 2026
Contributor
|
simulation on zksync wont work |
Contributor
Author
The issue was caused by a local ZkSync-node protocol version mismatch. I’ve updated the command and also added the instructions to run the simulations in the README. fixed here : 1a8b847.
|
3 tasks
Contributor
Debugger022
added a commit
that referenced
this pull request
May 15, 2026
- Add vip622Overrides.json hardcoding 20% floors for the 19 markets PR #706 right-sizes but hasn't yet executed on-chain - VIP merges overrides over the script snapshot per address, with a per-market source tag so reviewers can see at a glance which floors came from live state vs the VIP-622 hardcode - Unblocks publishing VIP-701 without waiting for VIP-622 to land
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

VIP-622: May 2026 Risk Parameter Update & Asset Off-boarding
Background
The four active non-BNB Chain Venus deployments (Ethereum, Arbitrum, Base, zkSync) have been in an emergency-paused state since 2026-03-20, following the THE market exploit on 2026-03-15. BNB Core remained operational with parameter-level mitigations across several markets. This proposal specifies the formal off-boarding, parameter restoration, and cap right-sizing across all five Core deployments, and is a prerequisite cleanup pass ahead of unpausing the four chains.
BNB Chain Core Pool
Off-boarding actions
Removing as collateral (CF → 0%, borrow retained where useful)
Already-deprecated assets (CF=0, caps → 0, borrows disabled)
BNB Core caps summary
(Markets not listed are unchanged or unaffected.)
Ethereum Core Pool
Off-boarding actions
Full delist (CF → 0%, caps → 0, borrow disabled)
Removing as collateral (CF → 0%, kept as borrow asset)
Re-enable borrowing
Re-enable borrowing for USDT, WETH, WBTC, USDC, DAI, crvUSD, USDe, tBTC, USDS.
Caps summary
Arbitrum Core Pool
Off-boarding actions
Keep borrows disabled / do not re-enable
Re-enable borrowing
Re-enable borrowing for USD₮0, WBTC, WETH, USDC.
Caps summary
Base Core Pool
Off-boarding actions
Full delist
Keep borrows disabled / do not re-enable (CF retained)
Re-enable borrowing
Re-enable borrowing for cbBTC, USDC, WETH.
Caps summary
zkSync Era Core Pool
Off-boarding actions
Full delist
Keep borrows disabled / do not re-enable (CF retained)
Re-enable borrowing
Re-enable borrowing for WETH, USDT, USDC.e, USDC.
Caps summary
(zkSync caps sit below the standard non-BNB benchmark, reflecting chain-wide liquidity constraints flagged in the off-boarding bullets above.)
Methodology notes
Cap sizing. Active supply and borrow caps are generally set to ~2× the maximum observed supply / borrow over the past 3 months. This is tightened where on-chain liquidity, concentration risk, or liquidator capacity would be stressed. For non-BNB deployments, caps are also bounded around ~$5M notional for stables, 2,100 WETH, and 65 WBTC, conditional on meeting liquidity considerations. Full-offboarded assets have caps set to zero.
Liquidation thresholds. Unchanged across this proposal. CF→0 actions affect new borrow power only and do not trigger liquidations on existing positions.
Disclosure
Allez Labs has not been compensated by any third party for publishing this report.
Source: Venus Community Forum