One thing I keep coming back to with
@aave is how GHO's economics actually work at the protocol level, because the more you look at the mechanic, the more it separates from how most people categorize it
When someone mints $GHO, they borrow it against collateral inside Aave. Standard so far. But there's no depositor on the other side of that trade. Aave isn't matching a lender to a borrower like it does w/ USDC or USDT. It's creating the asset. Which means every basis point of borrow interest on GHO goes straight to the DAO treasury. The full spread, unshared, as 100% protocol-owned revenue on a stablecoin the protocol itself issues
$250M+ in circulation right now and a $13M+ annualized revenue to the DAO from GHO alone per
@Token_Logic
sGHO makes this stickier than it looks on the surface. A 4.25% fixed APR vault, ERC-4626 compliant, w/ yield accruing directly in the share price and full liquidity to withdraw anytime. It functions as a savings rate on Aave's own currency. And because it absorbs idle $GHO into a passive yield position, it compresses sell pressure while keeping supply in the ecosystem. The savings product and the revenue engine are feeding the same balance sheet
I think what most people miss is that these aren't separate products. They're one loop:
Aave mints $GHO → earns interest on all of it → a portion funds the $sGHO savings rate → sGHO creates holding incentive → more GHO stays in circulation longer → supply grows more durably → revenue compounds → Aavenomics 3.0 routes that into automated $AAVE buybacks
Every layer reinforces the one before it without depending on external emissions or mercenary liquidity
GHO is positioned as a core settlement and borrowing asset across the V4 architecture. Each new market Aave deploys becomes another surface where GHO demand can form organically
@aave continues to earn spread on other people’s capital. GHO lets it earn on capital it creates. The savings rate locks that capital in. and V4 turns every new deployment into a distribution channel
As Aave keeps expanding the credit layer, it's interesting to see how much of that growth runs through a surface the protocol actually owns