
Venus tagged isolated-pools v4.5.0 on 10 November, merging its hub-spoke pool branch and mainnet spoke deployments. The release changes how liquidity and risk are split across the lending protocol.
In brief
- Venus tagged isolated-pools v4.5.0 on 10 November 2026, merging the hub-spoke pools branch.
- The release includes mainnet spoke deployments and a Bluechip spoke deployment.
- The code went through Sherlock and BailSec audits before the tag.
What happened
Venus, a lending protocol, published version 4.5.0 of its isolated-pools repository on 10 November, according to the release notes.
The tag merges the project's hub-spoke pools branch into the main line.
A hub-spoke design keeps one central hub for shared liquidity and risk, with separate spoke pools for individual markets.
The release also merges a branch for spoke pool mainnet deployments.
A further merge adds a Bluechip spoke deployment.
Why it matters
The structure decides where liquidity sits and how losses in one market reach the rest of the protocol.
Splitting markets into spokes limits what a single pool can affect.
The release notes list two external security reviews before the tag: a Sherlock audit and a BailSec audit.
They also list an internal AI audit and a storage-layout check.
The repository holds the protocol's isolated pools, the contracts behind its separate lending markets.
Venus
XVS is the protocol's token.
What to watch
The release notes do not say which assets the new spokes cover or when deposits open.
The Bluechip spoke deployment is merged in the code but not described in the notes.
Watch for a protocol announcement on spoke markets and their risk parameters.