VIP-615 retired the Venus Core Pool on opBNB, Optimism, and Unichain, but the XVS bridge between BSC and those chains stayed open at the same capacity it had during normal operation. This proposal closes that gap. zkSync receives the same outbound closure for a separate reason: Venus no longer maintains an XVS price oracle on that chain, so the USD-denominated cap on outbound transfers can no longer be validated against a current feed. For all four chains a small inbound capacity is preserved so any remaining holders can return their XVS to BSC. Ethereum — the only route that stays open in both directions — is tightened to match current usage; Arbitrum and Base are unchanged.
Background
When the Core Pool on a chain is wound down, the bridge to that chain stops serving any product purpose — no Venus market remains on the destination side to consume or produce XVS. The outbound caps, however, were never reset: Optimism and Unichain each still allowed up to $20,000 in a single transfer and $100,000 per day, and opBNB still allowed $10,000 single / $50,000 daily. All of that capacity now represents exposure without corresponding utility, exploitable if any part of the bridge path were compromised. This proposal sets the outbound caps on these three chains to ****$0 in both the single-transaction and daily dimensions, fully disabling new BSC → destination sends until a future VIP reactivates the route.
The same outbound closure applies to zkSync, but for a different reason. Redstone no longer maintains an XVS price oracle on zkSync, which means the USD-denominated cap on that route can no longer be validated against a current price feed. Rather than leave the route exposed without functioning price-based controls, the outbound caps on zkSync are zeroed as well (from $20,000 single / $100,000 daily) until oracle support is restored.
For all four chains — opBNB, Optimism, Unichain, and zkSync — the inbound side is preserved at a small non-zero level. Holders who still hold XVS on those chains, whether sitting in wallets or stuck mid-flight, need a way to bring those tokens back to BSC. A small inbound cap preserves that exit path without re-opening meaningful outbound capacity.
Ethereum is the only route that remains open in both directions; the change there is a right-sizing, not a closure. The route’s caps were last set in VIP-407 and have not been revisited since, and actual usage has run far below those levels for an extended period. The outbound single-transfer cap is reduced from $100,000 to $30,000 and the outbound daily cap from $1,000,000 to $150,000; the inbound single-transfer cap from $102,000 to $20,000 and the inbound daily cap from $1,020,000 to $50,000. The new limits leave normal user flow unaffected while cutting worst-case single-transfer exposure by roughly 70%. Arbitrum and Base remain at their current limits and are not part of this adjustment.
Details
Each cap stored on the BSC contract XVSProxyOFTSrc (0xf8F46791E3dB29a029Ec6c9d946226f3c613e854) is denominated in USD with 18 decimals. When a transfer is initiated, the contract converts the requested XVS amount to USD via the Venus ResilientOracle and compares the result against the configured cap. Transfers that exceed the single-transaction cap revert immediately; transfers that fit individually but would push the rolling 24-hour total above the daily cap revert as well.
From the perspective of BSC, send limits apply to BSC → destination transfers and receive limits apply to destination → BSC transfers. Each direction has both a single-transaction cap and a daily cap.
Action
This proposal consists of 20 setter calls on the BSC XVSBridgeAdmin (0x70d644877b7b73800E9073BCFCE981eAaB6Dbc21). For each of the five affected destinations (Ethereum, opBNB, zkSync, Optimism, Unichain), four caps are updated:
setMaxSingleTransactionLimit(uint16,uint256)— outbound single-transfer capsetMaxDailyLimit(uint16,uint256)— outbound daily capsetMaxSingleReceiveTransactionLimit(uint16,uint256)— inbound single-transfer capsetMaxDailyReceiveLimit(uint16,uint256)— inbound daily cap
| Destination (LzChainId) | Daily Send | Single Send | Daily Receive | Single Receive |
|---|---|---|---|---|
| Ethereum (101) | $1,000,000 → $150,000 | $100,000 → $30,000 | $1,020,000 → $50,000 | $102,000 → $20,000 |
| opBNB (202) | $50,000 → $0 | $10,000 → $0 | $51,000 → $1,000 | $10,200 → $1,000 |
| Arbitrum (110) | unchanged | unchanged | unchanged | unchanged |
| zkSync (165) | $100,000 → $0 | $20,000 → $0 | $102,000 → $10,000 | $20,400 → $10,000 |
| Optimism (111) | $100,000 → $0 | $20,000 → $0 | $102,000 → $2,000 | $20,400 → $2,000 |
| Base (184) | unchanged | unchanged | unchanged | unchanged |
| Unichain (320) | $100,000 → $0 | $20,000 → $0 | $102,000 → $10,000 | $20,400 → $10,000 |
A concrete example: at an XVS price of $6, the new Ethereum single-transaction send cap of $30,000 means any outbound transfer larger than ~5,000 XVS would be rejected with Single Transaction Limit Exceed. Daily totals work the same way against the 24-hour rolling sum.
Summary
If approved, this proposal will:
- Close outbound XVS bridging from BSC to opBNB, Optimism, and Unichain (consistent with the VIP-615 Core Pool sunset) and to zkSync (no XVS oracle on that chain) by zeroing their send caps
- Preserve a small inbound capacity from all four chains so existing holders can return their XVS to BSC
- Tighten Ethereum caps in both directions to match current usage; leave Arbitrum and Base unchanged
We welcome community feedback on this proposal ahead of submitting it for a VIP vote.