Feat/liquidity hub centrifuge onboarding - #759
Draft
GitGuru7 wants to merge 2 commits into
Draft
Conversation
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.
Summary
Draft VIP onboarding a Centrifuge yield group into the USDT Liquidity Hub on BNB Chain, wiring
two Centrifuge v3 (ERC-7540) tokenised-fund vaults into it — JTRSY (Janus Henderson Anemoy Treasury
Fund) and JAAA (Janus Henderson Anemoy AAA CLO Fund) — alongside the existing Core, Flux and FRV
groups.
What the VIP does
34 commands across 6 targets, one atomic transaction, order-dependent.
1. ACM grants (28) on the new yield group:
YieldGroupBase+ 10YieldGroupCentrifuge)pauseResource,requestRedeem, both cancellationsclaimDeposit,claimRedeem,claimCancelDeposit,claimCancelRedeemThe Guardian set is containment and wind-down only: no unpause, no claims, no
sweep, no price-guardcontrol, so it can contain but never undo a governance-ordered pause.
2. Resource registration —
addResourcefor the JTRSY and JAAA vaults behind the sharedAdapterCentrifuge. Must precede the queue setters, which reject an unregistered resource.3.
setInnerDepositQueue([JTRSY, JAAA]). The inner withdraw queue is deliberately not set.4.
setPriceGuardper vault against the live Centrifuge Spoke, 5-day staleness window.5.
addYieldGroupon the USDT Hub at 5,000,000 USDT absolute and 2000 bps (20% of TVL)._effectiveCaptakes the lower, so the percentage dimension binds at the current TVL.6.
setOuterWithdrawQueue([Flux, Core, FRV, Centrifuge])— rewritten in full, because the Hubrejects a queue omitting a registered group that holds a balance.
No
acceptOwnership()appears: the CentrifugeBeacon receives governance ownership inside the deploytransaction (OpenZeppelin
Ownableis single-step). The USDC and U Hubs are untouched.The Spoke reports
maxAge == validUntil == type(uint64).maxfor both share classes and_enforcePriceGuardnever reads them, so the 5-day window is sized from observed publication cadenceinstead: NAV is published on business days — 1-day gaps, 3 days over weekends, 4.00 days worst case
over 60 days of samples. That leaves one day of headroom.
Pending before this can be proposed
CENTRIFUGE_YIELD_GROUP— theYieldGroupCentrifugeBeaconProxy for the USDT Hub. Notdeployed;`
ADAPTER_CENTRIFUGE— the stateless per-chain adapter. Not deployed.