Sentora

Aave governance is reviewing a proposal that would hand Sentora day-to-day control of a new lending instance built on Aave V4’s Hub and Spoke architecture, while Aave DAO keeps ownership of the underlying contracts. The ARFC posted to the Aave governance forum sets borrowing on the instance exclusively in RLUSD, PYUSD and OUSD, and splits protocol revenue 50/50 between Sentora and the Aave DAO.

• Risk-increasing parameter changes by Sentora face a mandatory 48-hour onchain timelock before execution
• New Hub deployments or collateral listings trigger a two-week optimistic governance window subject to Snapshot veto

• 50% share of instance revenue routed to Aave DAO
• 48-hour timelock on risk-increasing parameter changes

The proposal is an ARFC, the first stage in Aave’s three-step process. It still needs to clear a Snapshot vote and then a final AIP with locked parameters before anything deploys onchain.

Three Spokes, One Liquidity Hub

The first instance targets Ethereum mainnet with a single Liquidity Hub feeding three initial Spokes segmented by risk profile. The RLUSD Yield Spoke lets users borrow RLUSD against yield-bearing collateral starting with USDe and Huma PST, with PRIME and mWIN slated for later addition.

The Bluechip Spoke offers RLUSD borrowing against kBTC. An OUSD Yield Spoke mirrors the RLUSD structure, and a fourth, PYUSD Yield, is planned for a later launch.

Rate Curve And Collateral Split

Borrowable assets are RLUSD, PYUSD, and OUSD, each supplied with independent interest rate curves. All other listed collateral, including USDe, PRIME, mWIN, PST and kBTC, carries a flat 0% rate and a zero draw cap, meaning none of it can be borrowed against directly.

That structure keeps all debt issued by the instance denominated only in RLUSD, PYUSD or OUSD.

Who Holds The Keys

Aave DAO retains admin and smart contract ownership through its Governance Short Executor and grants Sentora only revocable roles, built on OpenZeppelin’s AccessManager. Sentora can cut risk instantly through a restricted Risk Steward contract, but any risk-increasing move, such as raising collateral factors or expanding caps, must sit through the 48-hour window on the AccessManager itself.

The document is explicit that the DAO cannot cancel an individual scheduled change once it enters that window.

“The recourse available to the Aave DAO is revocation of Sentora’s role grants through an onchain governance proposal, which removes Sentora’s authority over the instance going forward.”

Aave governance forum, ARFC on the Sentora framework

The document also states plainly that Aave’s risk service providers carry no mandate to monitor the instance or produce parameter recommendations for it, and none is paid to do so. Objections during the two-week listing window are discretionary, not a scheduled review, a distinction the proposal draws out itself.

What The Framework Skips

The proposal does not authorize credit lines between this instance and other Aave DAO Hubs; establishing one would need a separate proposal under the Aave Risk Framework. It also does not state a target launch date, deposit caps, or how much liquidity currently sits on Sentora’s existing isolated venues that this consolidation would migrate.

The CCS read. Externally curated hubs let Aave scale stablecoin lending without stretching its own risk teams, but the 48-hour timelock has no cancellation switch and no size cap. The DAO’s only real lever if Sentora misjudges a parameter is a governance vote to revoke access after the fact, not before.

Watch for Sentora’s ARFC to move to a Snapshot vote; if it passes, the framework proceeds to an AIP with final parameters for onchain approval and execution.