Aave governance is considering a proposal that would create a framework for Sentora to run externally curated Hub and Spoke deployments on Aave V4, while also approving the first such instance on Ethereum. The draft, posted as an ARFC, would give Sentora day-to-day control over market curation while the Aave DAO keeps contract ownership and the ability to revoke Sentora’s authority through governance.

The proposed setup is designed around a single Ethereum liquidity Hub isolated from other Aave markets. Borrowing would be limited to three stablecoins, RLUSD, PYUSD and OUSD, and the Aave DAO would receive 50% of revenue generated by the instance. The proposal also states that no credit lines to or from existing Aave DAO Hubs are included and any such connection would require a separate governance process.

How the structure would work

Under the framework, Sentora would manage collateral listings, risk parameters, interest-rate curves and oracle choices for its own markets. The proposal says these instances would sit outside the risk-management mandate of the Aave DAO and its service providers, even though the DAO would retain admin ownership through the Governance Short Executor.

Aave V4’s native access controls are central to the design. Sentora would not own the deployed contracts, but would act through revocable operational roles. Immediate authority would be limited to risk-reducing actions such as freezing reserves, pausing assets or lowering caps. Changes that increase risk, or where risk direction is treated as unclear, would have to be scheduled onchain and wait 48 hours before execution.

Initial Hub and Spoke design

The first deployment outlined in the ARFC is a single liquidity Hub on Ethereum serving Sentora Spokes on that network only. Hub assets would be split between borrowable liquidity and collateral-only assets. RLUSD, PYUSD and OUSD would be the only borrowable tokens, each with its own rate configuration, while all other listed assets would be collateral-only with a 0% rate and zero draw cap, meaning debt from the instance would be denominated only in those three stablecoins.

The launch configuration includes three initial Spokes, with a fourth planned later. The RLUSD Yield Spoke would allow RLUSD borrowing against yield-bearing collateral, starting with USDe and Huma PST, with PRIME and mWIN named as planned additions. The Bluechip Spoke would support borrowing against kBTC. A third spoke, OUSD Yield, would mirror the RLUSD Yield model but use OUSD as the borrowed asset. A PYUSD Yield spoke is planned for later deployment.

Parameters, limits and oversight

The ARFC sets several structural boundaries meant to align the instance with broader Aave markets. RLUSD, PYUSD and OUSD would be the exclusive borrowable stablecoins across any Sentora Hub, while USDC and USDT would remain excluded. A minimum reserve factor of 20% would apply to every asset, and Sentora could raise that figure but not lower it.

For borrowable assets, the proposed interest-rate curve has a 0.50% base drawn rate, a 90% optimal usage ratio, 3.50% growth before the kink and 12.00% after it, with a 20.00% liquidity fee. Collateral-only assets including USDe, PRIME, mWIN, PST and kBTC would use a flat 0% curve. Oracle sources listed in the post include Chainlink feeds for RLUSD, PYUSD, USDe and BTC, a Chainlink-based construction for PST, and a Midas NAV feed for mWIN. OUSD was listed without a defined oracle in the proposal text.

Governance path and what happens next

New asset listings and any new Hub deployment would not move directly onchain. Instead, Sentora would first post the proposal and market analysis to the governance forum for a two-week optimistic review. If any appointed Aave DAO service provider objects during that period, the process would stop and move to a binding Snapshot vote. The proposal notes that service providers are not specifically tasked or paid to review these submissions, so a lack of objection would not mean a review took place.

The ARFC is the first step in the formal process. If feedback is positive, the next confirmed stage would be a Snapshot vote. If that passes, the proposal would then move to an AIP with final parameters for onchain governance approval.

Source: governance.aave.com