# [ARFC] Sentora Externally Curated Hub & Spoke Framework on Aave V4

- Space: [Aave DAO](https://snapshot.box/s:aavedao.eth.md)
- Author: 0x66a28531E6f390A8CD44aB0C57a0F1aeb7E673FF
- State: Passed
- Voting type: Basic
- Start: 2026-10-02 09:54 UTC
- End: 2026-10-05 09:54 UTC
- Votes: 140
- Discussion: https://governance.aave.com/t/arfc-sentora-externally-curated-hub-spoke-framework-on-aave-v4/25723
- Open in Snapshot: https://snapshot.box/#/s:aavedao.eth/proposal/0x682f73c809e03d25008b9c4898f4e25c047806683f4d1b0d7635ba8ed50276aa

## Results

- For: 360,060.19 voting power, 99.9%
- Against: 0 voting power, 0.0%
- Abstain: 377.93 voting power, 0.1%

## Proposal

**Title:** [ARFC] Sentora Externally Curated Hub & Spoke Framework on Aave V4
**Author:** SentoraHQ
**Date:** 2026-10-01

***
## **Summary**

This ARFC establishes a framework for Sentora to operate Hub and Spoke instances on Aave V4, and authorises the first instance on Ethereum.

Hub and Spoke instances deployed under this framework are externally curated instances, independently managed by Sentora, which holds curation over collateral selection, risk parameters, interest rate curves, and oracles across its markets. Curation of these instances sits outside the risk management mandate of the Aave DAO and its service providers.

The Aave DAO retains smart contract and admin role ownership through the Aave DAO Governance Short Executor, and grants Sentora revocable operational roles. Sentora executes ongoing changes through an optimistic model: risk-reducing actions execute instantly, while risk-increasing updates require a 48-hour onchain timelock, and new Hub deployments and new collateral markets require a 2-week optimistic governance process.

The stablecoin surface is restricted to RLUSD, PYUSD and OUSD, and the Aave DAO receives 50% of instance revenue. No credit lines to or from Aave DAO Hubs are authorised here, and establishing one would require a separate proposal in accordance with the [Aave Risk Framework](https://governance.aave.com/t/arfc-aave-risk-framework/25114/5).

## **Motivation**

Sentora currently operates curated lending market strategies across several isolated venues. That fragments liquidity, duplicates risk operations across incompatible parameter models, and requires separate monitoring and tooling for each venue. Aave V4 is the first architecture that permits consolidation without giving up curation control, because the Hub and Spoke model lets one liquidity domain serve several Spokes with distinct collateral sets and distinct risk configurations.

For the Aave DAO, the deposits involved sit on external venues today, so the instance adds to Aave liquidity and revenue potential, and establishes Aave as a primary venue for RLUSD, PYUSD, and OUSD stablecoin growth.

## **Market Structure**

The diagram below shows the target state of the first instance, a single Liquidity Hub on Ethereum serving as the sole liquidity domain for all Sentora Spokes on that network, isolated from other Aave markets. No credit lines to or from other Aave Hubs are proposed here.

Hub assets are split into two distinct categories: borrowable liquidity and collateral-only assets.

RLUSD, PYUSD, and OUSD serve as the sole borrowable liquidity, each supplied with independent interest rate curves and drawn by the Spokes. All other registered assets function strictly as collateral, configured with a 0% interest rate and a zero draw cap across every Spoke. Consequently, all debt issued by the instance is denominated exclusively in RLUSD, PYUSD, or OUSD.

The deployment launches with three initial Spokes segmented by risk profile, with a fourth planned for later deployment. The **RLUSD Yield Spoke** offers RLUSD borrowing against yield-bearing collateral: initially USDe and Huma PST, with planned expansion to assets like PRIME and mWIN. The **Bluechip Spoke** offers RLUSD borrowing against kBTC. A third spoke, **OUSD Yield**, will have a similar set up to the RLUSD Yield spoke, replacing the corresponding borrowed asset. Lastly **PYUSD Yield**, will launch subsequently to mirror the yield-bearing model with PYUSD debt against a tailored collateral selection. Collateral sets across all Spokes are expected to expand over time, with every new asset onboarding subject to the governance veto process.

## **Instance Management**

Sentora serves as operational manager for the instance, holding authority over risk, growth, and market configuration. Aave DAO maintains smart contract and admin role ownership via the Aave DAO Governance Short Executor to protect ecosystem security and alignment, which does not place the instance within the risk management mandate of Aave DAO service providers.

The instance's assets, risk parameters, interest rate curves, liquidation configurations, and oracles are selected and maintained solely by Sentora. They have not been reviewed against the Aave Risk Framework and are not maintained under it. The Aave DAO's risk service providers carry no mandate to monitor the instance, to produce parameter recommendations for it, or to perform incident response on it, and none is engaged or compensated to do so. Service providers retain the ability to raise objections and to bring matters to governance where they judge that competitive alignment or systemic risk considerations warrant it, at their own discretion and on their own initiative.

Aave V4 natively implements the OpenZeppelin AccessManager across all privileged configurator functions, enabling operational boundaries through granular, account-specific role delays rather than custodial transfers. Sentora owns none of the deployed contracts and acts exclusively through revocable roles granted to the Sentora operational address and a dedicated intermediate Risk Steward contract:

grantRole(SENTORA_RESTRICTIVE_ROLE, sentoraAddress, 0)  // risk-reducing

grantRole(SENTORA_MANAGED_ROLE, sentoraAddress, 172800) // risk-increasing

grantRole(SENTORA_MANAGED_ROLE, sentoraRiskSteward, 0)  // risk-reducing

Emergency risk mitigation is handled via the Restrictive Role, allowing the Sentora operational address to immediately execute functions such as pauseReserve, freezeReserve, haltAsset, haltSpoke, and resetting caps in the calling transaction.

Routine market operations sit inside the Managed Role and follow an optimistic model split into two execution paths based on risk direction:

* **Risk-Reducing Actions (Zero Delay)**: Sentora executes these in the same block via an extended Risk Steward contract. The Steward exposes a restricted, one-way numeric entrypoint covering granular parameter cuts such as reducing collateral factors, tightening collateral risk, or lowering add and draw caps. The Steward verifies that updates move strictly in the risk-reducing direction.

* **Risk-Increasing Actions (48-Hour Delay)**: Any parameter movement that increases risk, such as raising collateral factors or expanding caps, as well as parameters where the risk direction is ambiguous, such as interest rate models and liquidation configurations, cannot pass through the Risk Steward. These changes must be scheduled directly on the AccessManager by the Sentora operational address and await a mandatory 48-hour onchain timelock before execution. Ambiguous functions are classified as risk-increasing.

The 48-hour delay is the constraint on the risk-increasing path. It provides a fixed observation window during which any scheduled change is visible onchain before it takes effect. Increases are not bounded in magnitude and are not subject to cooldowns between updates, so a large parameter change and a small one are delayed identically. The Aave DAO does not hold a mechanism to cancel an individual scheduled operation inside the 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.

Asset listings and new Hub deployments follow an optimistic two-week governance review. Sentora submits its proposal and market analysis to the Aave governance forum, opening a two-week window for review. If any appointed Aave DAO service provider objects within this window, the action immediately pauses and moves to a binding Snapshot vote. Sentora cannot proceed with onchain scheduling or deployment while a Snapshot is pending. The window is an opportunity to object rather than a review commitment. No service provider is scoped or compensated to review these submissions, and the absence of an objection does not indicate that a review was performed.

### **Aave DAO Oversight**

The Aave DAO Governance Short Executor retains structural ownership of the instance, holding the admin roles across all Hub and Spoke contracts, configurators, and the native AccessManager. Core protocol controls are never delegated to Sentora, including smart contract upgrades and role assignments. The Short Executor sits above all operational flows, retaining the right to revoke Sentora's role grants through an onchain governance proposal.

For new Hub deployments or asset additions, the DAO exercises governance control through an optimistic two-week forum review. If any appointed Aave DAO service provider objects within this window, the rollout halts and escalates to a binding Snapshot vote. Sentora cannot proceed with deployment or onchain execution while a Snapshot vote is pending.

Ownership is retained so that the deployment remains inside the Aave V4 codebase and upgrade path, and so that the ability to halt a deployment or listing, or to withdraw Sentora's authority entirely, stays with the Aave DAO and can be exercised at its discretion. Ownership is not an assertion that the Aave DAO or its service providers manage risk on the instance.

## **Aave DAO Alignment**

To preserve alignment with core Aave DAO markets, this framework imposes structural, commercial, and operational bounds.

RLUSD, PYUSD, and OUSD serve as the exclusive borrowable stablecoins across any Sentora Hub, with USDC and USDT permanently excluded to avoid conflicting with existing Aave market liquidity. A minimum reserve factor of 20% applies to every asset on the Hub, which Sentora may raise but never lower.


***
Note: Due to the character count limitations of Snapshot, the remainder of the forum post cannot be shown, and can be found on the governance forum linked below.

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

