Sentora has proposed running its own isolated Aave V4 Hub and lending Spokes on Ethereum, an arrangement that would give the firm control over collateral selection, interest-rate curves, liquidation settings and oracles while Aave DAO keeps contract ownership and admin rights. The catch: none of Aave's existing risk service providers would be assigned to monitor, recommend changes, or respond to incidents on Sentora's instance. The proposal is an ARFC, meaning it is still just a discussion document. A Snapshot vote and a formal on-chain Aave Improvement Proposal would follow.
A Hub That Talks to No One Else
The isolation is the point. Sentora's Hub would have no credit lines to or from other Aave DAO Hubs, and its Spokes would draw only from suppliers inside Sentora's Hub. That structure stops Sentora's borrowers from pulling liquidity out of Aave's main markets. It does nothing for lenders inside Sentora's own Hub, who remain exposed to whatever its Spokes do.
Borrowable assets are narrow by design. The instance is limited to RLUSD, PYUSD and OUSD. USDC and USDT are excluded — the two stablecoins that anchor most of Aave's existing activity.
The 48-Hour Delay, and What It Doesn't Cover
Sentora's operational roles come with an unusual split. It can pause or freeze a reserve, halt an asset or Spoke, cut a collateral factor or tighten a cap immediately through a one-way Risk Steward role. Those are all defensive moves.
Anything that adds risk works differently. Rate model changes, liquidation configuration changes and risk increases take effect only after a 48-hour on-chain delay. The facts as published do not specify whether the DAO holds an individual cancellation right over those pending actions. Adding collateral or deploying another Hub requires a two-week forum review, and an objection from any appointed Aave DAO service provider pauses the action for a binding Snapshot vote.
The DAO's Governance Short Executor would retain admin roles over the Hub, Spokes and AccessManager, including contract upgrades and role grants. Sentora's operational roles are revocable through an on-chain governance proposal. Aave DAO can take the keys back. It just isn't budgeting anyone to watch the shop.
Nobody Is Paid to Review Sentora's Submissions
That's the sharpest detail in the filing. No service provider is scoped or compensated to review Sentora's submissions, and the instance is explicitly excluded from providers' monitoring, parameter-recommendation and incident-response mandates. The two-week review window exists, but there is no assigned reviewer. In practice, the objection mechanism depends on a DAO service provider noticing something worth objecting to.
Who Eats the Loss
Sentora's commercial terms give 50% of the instance's protocol revenue to Sentora and 50% to the DAO, covering reserve-factor earnings and protocol liquidation fees. The loss side follows TokenLogic's V4 Umbrella proposal: if a liquidation leaves a debt shortfall, the Spoke reports it to the Hub, which records the deficit against that asset. Suppliers of that Hub asset bear the loss.
A separate Aave V4 Umbrella ARFC proposes deficit offsets and staked coverage for Core WETH, Core USDC and Core USDT. It does not name Sentora's proposed Hub. So the assets listed for backstop coverage are not the assets Sentora wants to lend against.
Sentora CEO Anthony DeMartino argued in a November 2025 essay that risk management needs measurable controls and continuous monitoring. The proposal puts the measurable controls on-chain, behind a 48-hour timer and a one-way kill switch. The continuous monitoring is Sentora's own.
Next up is a Snapshot vote, then an on-chain AIP if the temperature check holds.
