History – Aave GHO

Back
v1.1.4 · currentHow Caper approaches this rewritten outcome-only (VOICE §4 Caper overlay): no formula, code names or Caper numbers; claims re-read against core and logic at 1059e09.–
1 block modified
  • Modified – Text at Block 7

    How Caper approaches this Cap…t a stablecoin issuer, so the honestuseful contrast is about who holds the parameters and whether a dissenter has an exi way out. On Aave, a borrower or $AAVE holder who dislikes a governance-set GHO rate has no structural recourse beyond selling their position –: the vote binds everyone who s…/foundations/what-is-a-caper) , the treasury is the governed object, and two things differ. First, a A member’'s vote weight (/wiki/governance/voting) is (held × votes) / (vote_supply × circulation) – a product of tokens held andcomes from the tokens they hold together with a soulbound, non-transferable (/wiki/dao-governance/concepts/membership/soulbound-tokens) record of taking part, minted 1 per rankedearned by casting ballots and nothing at all forever by buying, selling or receiving a transfer. Capital is not excluded – held is a multiplicative factor – but it cannot supply the second term:tokens; holdings still count, but a baig bought on the curve mints no record as it buys, so what the formula rules out is assembling governance weight without ever casting a ballot. Second, when you lose a parameter fight you can exit with youag alone can't capture control. And a member who loses a vote can exit any time for their fair share of the treasury (/wiki…than only sell into the market –, so the majority cannot trap youthem in a policy you fought. (Mechanics verified against compute_vote_weight in contracts/common/src/lib.rs and exit in contracts/logic/src/lib.rs; framed at the outcome level, no invented features.)they fought.

v1.1.3Em dashes become spaced en dashes (VOICE.md); dashes inside quotes and source titles kept–
7 blocks modified
  • Modified – Text at Block 1 → Block 1

    Project GHO (Aave) Category D…vernance vote Stablecoin GHO —– USD-pegged, native to the Aav…Governance Maximally governed —– the borrow rate is a fixed va…(https://governance.aave.com/)

  • Modified – Text at Block 2

    GHO is a decentralized, overc… every lever that governs GHO —– the interest rate borrowers p…ich assets can defend the peg —– is a live decision of the Aa…ntals/dao-governance-models) —– the exact opposite of Liquit…nce itself as monetary policy.

  • Modified – Text at Block 3

    The facilitator model GHO is …ernance approves facilitators —– contracts that can trustless…wered, or revoked by proposal.

  • Modified – Text at Block 4

    An interest rate set by vote …w cap toward a 100M threshold —– a guarded, rate-limited deleg…tion of three governed inputs —– the base rate, their stkAAVE …ance, and the per-stkAAVE cap —– a striking contrast to a purely mechanical fee.

  • Modified – Text at Block 5

    The GHO Stability Module and t…ased price-freeze protections —– all governance-configured. If…rameter set the DAO maintains.

  • Modified – Text at Block 6

    Where it sits on the governanc…by making its rules immutable —– no vote can touch the borrow …ts rules maximally responsive —– the DAO can retune the rate, …ctory is a third answer again —– retiring a governance lever once it has served its purpose.

  • Modified – Text at Block 7

    How Caper approaches this Cap…beyond selling their position —– the vote binds everyone who s…/ (vote_supply × circulation) —– a product of tokens held and …sfer. Capital is not excluded —– held is a multiplicative factor —– but it cannot supply the seco…han only sell into the market —– the majority cannot trap you … level, no invented features.)

v1.1.2Split paragraphs over 150 words at sentence boundaries; wording unchanged.–
1 block modified
  • Modified – Text at Block 7

    How Caper approaches this Cap…lling or receiving a transfer.Capital is not excluded — held… level, no invented features.)

v1.1.1Trading no longer mints v: correct the vote-mint claim against VOTE_MINT in contracts/logic/src/lib.rs (ballots only; buys, sells and transfers mint zero) after the 11 Sep 2026 genesis redeploy–
1 block modified
  • Modified – Text at Block 7

    How Caper approaches this Cap…inted 1 per ranked ballot and 0.01 per XRD of gross value on each leg ofnothing at all for buying, selling or receiving a tradensfer. Capital is not excluded and in fact counts twice over, since— held is a multiplicative factor — but it cannot supply the second term: a bag bought on the curve mints its owno record as it buys;, so what the formula rules out is acquiring someone else's record, and a bag that arrived by transfer carries none of its ownssembling governance weight without ever casting a ballot. Second, when you lose a para… level, no invented features.)

v1.1.0Corrects two claims: v is minted by trading as well as voting, and a bought bag does carry weight–
1 block modified
  • Modified – Text at Block 7

    How Caper approaches this Cap…d, non-transferable record of havtaking actually voted, so a large bag alone cannot captpart, minted 1 per ranked ballot and 0.01 per XRD of gross value on each leg of a trade. Capital is not excluded and in fact counts twice over, since a bag bought on the curve the control surface the way it can accumulate stkAAVEmints its own record as it buys; what the formula rules out is acquiring someone else's record, and a bag that arrived by transfer carries none of its own. Second, when you lose a para… level, no invented features.)

v1.0.1Source citation: compute_vote_weight is defined in contracts/common/src/lib.rs, not contracts/logic/src/lib.rs–
1 block modified
  • Modified – Text at Block 7

    How Caper approaches this Cap…d against compute_vote_weight in contracts/common/src/lib.rs and exit in contracts/logic/sr… level, no invented features.)

v1.0.0Accuracy: repoint the contract citation from the deleted path contracts/src/caper_dao.rs to contracts/logic/src/lib.rs, where the curve/weight/exit math actually lives after the 2026-07-20 workspace split.–
4 blocks modified
  • Modified – Text at Block 2

    GHO is a decentralized, overc…governance spectrum (/wiki/daos-governance/concepts/fundamentals/dao-gov…ungovernable BOLD (/wiki/daos/organizations/stablecoins/liquity) , and a c…nce itself as monetary policy.

  • Modified – Text at Block 3

    The facilitator model GHO is …s. Where Liquity (/wiki/daos/organizations/stablecoins/liquity) lets any…wered, or revoked by proposal.

  • Modified – Text at Block 6

    Where it sits on the governanc…d Liquity’s BOLD (/wiki/daos/organizations/stablecoins/liquity) are the …ance attack surface (/wiki/daos-governance/concepts/analysis/dao-securit…-vote-escrow turn (/wiki/daos/organizations/lending/pendle-finance) elsew…nce it has served its purpose.

  • Modified – Text at Block 7

    How Caper approaches this Cap…are of the treasury (/wiki/daos-governance/concepts/membership/rage-quit…_weight and exit in contracts/src/caper_daologic/src/lib.rs; framed at the outcome level, no invented features.)

v1.0.0Repoint DAO links to canonical taxonomy paths (2026-07-17 split)–
4 blocks modified
  • Modified – Text at Block 2

    GHO is a decentralized, overc…governance spectrum (/wiki/daos/concepts/fundamentals/dao-governance-models) — the …s ungovernable BOLD (/wiki/dao/ecosystems/organizations/stablecoins/liquity) , and a clean case s…nce itself as monetary policy.

  • Modified – Text at Block 3

    The facilitator model GHO is …ves. Where Liquity (/wiki/dao/ecosystems/organizations/stablecoins/liquity) lets any borrower m…wered, or revoked by proposal.

  • Modified – Text at Block 6

    Where it sits on the governanc…and Liquity’s BOLD (/wiki/dao/ecosystems/organizations/stablecoins/liquity) are the two poles o…ance attack surface (/wiki/daos/concepts/analysis/dao-security-and-governance-at…st-vote-escrow turn (/wiki/dao/ecosystems/organizations/lending/pendle-finance) elsewhere in…nce it has served its purpose.

  • Modified – Text at Block 7

    How Caper approaches this Cap…are of the treasury (/wiki/daos/concepts/membership/rage-quit-and-exit-rights) ra… level, no invented features.)

v1.0.0Create dao/ecosystem/aave-gho — the maximally-governed CDP stablecoin (borrow rate set by Aave governance vote, facilitator mint caps, stkAAVE discount, GSM), framed as the foil to Liquity's ungovernable BOLD. Contract-verified Caper contrast (vote weight (t*v)/(V*T), soulbound vote token, exit with treasury share).–
7 blocks added
  • Added – Text at Block 1 → Block 1

    Project GHO (Aave) Category Decentralized overcollateralized stablecoin · CDP Chain Ethereum + multichain via cross-chain messaging Launched 12 July 2023 (https://www.pymnts.com/cryptocurrency/2023/aave-introduces-gho-stablecoin/) , after an Aave governance vote Stablecoin GHO — USD-pegged, native to the Aave protocol, minted against Aave V3 collateral Governance token AAVE · stkAAVE (staked in the Safety Module) earns a GHO borrow-rate discount Governance Maximally governed — the borrow rate is a fixed value set by Aave governance vote (https://governance.aave.com/) , not a utilization curve; facilitator mint caps, the discount, and GSM assets are all governance parameters Primary sources aave.com/docs (https://aave.com/docs/developers/gho) · governance.aave.com (https://governance.aave.com/)

  • Added – Text at Block 2

    GHO is a decentralized, overcollateralized stablecoin native to the Aave protocol (https://aave.com/docs/developers/gho) : borrowers mint it against collateral supplied to Aave V3, and it holds a US-dollar peg backed by that collateral rather than by fiat reserves. What makes GHO worth cataloguing here is not the peg mechanics but the control surface: nearly every lever that governs GHO — the interest rate borrowers pay, how much any given contract may mint, the discount stakers receive, which assets can defend the peg — is a live decision of the Aave DAO (https://governance.aave.com/) . That places GHO at the maximally-governed pole of the DAO governance spectrum (/wiki/dao/concepts/dao-governance-models) — the exact opposite of Liquity’s ungovernable BOLD (/wiki/dao/ecosystem/liquity) , and a clean case study in treating governance itself as monetary policy.

  • Added – Text at Block 3

    The facilitator model GHO is not minted by a single vault. Instead, Aave governance approves facilitators — contracts that can trustlessly mint and burn GHO (https://aave.com/docs/developers/gho) up to a governance-set bucketCapacity. The original facilitators were the Aave V3 Ethereum Market (where users borrow GHO against supplied collateral) and a FlashMinter; later additions include the GHO Stability Module. Each facilitator’s bucket is a hard, governance-owned ceiling on how much GHO it can bring into existence, so the total supply is bounded by an explicit ledger of votes rather than by market demand alone. This is a deliberately different answer to “who decides how much stablecoin exists?” than an algorithmic issuer gives. Where Liquity (/wiki/dao/ecosystem/liquity) lets any borrower mint against ETH under fixed immutable rules, GHO’s supply is gated by a governance-maintained set of facilitators and caps that can be raised, lowered, or revoked by proposal.

  • Added – Text at Block 4

    An interest rate set by vote The defining feature: GHO’s borrow rate is a fixed number chosen by Aave governance, not a curve that floats with utilization. Holders vote a rate based on the peg and market conditions, and the protocol charges it uniformly. To make routine adjustments without a full multi-day vote each time, governance delegates a bounded lever to GHO Stewards, who can change the borrow rate by at most 500 bps per two-day period, up to a 25% APR ceiling (https://aave.com/docs/developers/gho) , and raise the borrow cap toward a 100M threshold — a guarded, rate-limited delegation rather than open discretion. Layered on top is a staker discount: users who stake AAVE in the Safety Module (stkAAVE) receive a reduction on their GHO borrow rate, applied per staked token up to a per-token GHO cap. The discount rate is itself a governance parameter. The rate a borrower actually pays is therefore a function of three governed inputs — the base rate, their stkAAVE balance, and the per-stkAAVE cap — a striking contrast to a purely mechanical fee.

  • Added – Text at Block 5

    The GHO Stability Module and the governed peg When the peg drifts, GHO does not rely solely on redemption arbitrage. The GHO Stability Module (GSM) lets users swap GHO 1:1 for governance-approved tokens (https://aave.com/docs/developers/gho) (such as major fiat-backed stablecoins), with exposure caps, dynamic fee strategies, and oracle-based price-freeze protections — all governance-configured. If GHO trades above peg, minting and selling into the GSM pushes it down; below peg, buying and burning pulls it up. Because which assets back the GSM and at what caps are votes, the peg backstop is a governance instrument, not a fixed algorithm. Aave has continued to extend this surface: 2025 brought stkGHO, anti-GHO, and a savings variant (sGHO) (https://oakresearch.io/en/analyses/innovations/aave-2025-three-horsemen-of-gho-stkgho-anti-gho-sgho) as governance-shaped ways to hold and stabilize GHO, each adding another parameter set the DAO maintains.

  • Added – Text at Block 6

    Where it sits on the governance spectrum GHO and Liquity’s BOLD (/wiki/dao/ecosystem/liquity) are the two poles of the same design question, and reading them together is the point. Liquity protects a stablecoin by making its rules immutable — no vote can touch the borrow rate or the peg logic, so there is nothing to capture. GHO protects a stablecoin by making its rules maximally responsive — the DAO can retune the rate, the mint caps, and the peg backstop as markets move. Each buys something and pays for it: immutability buys credible neutrality at the cost of adaptability; governance buys adaptability at the cost of a standing governance attack surface (/wiki/dao/concepts/dao-security-and-governance-attacks) and a dependence on votes turning out. The post-vote-escrow turn (/wiki/dao/ecosystem/pendle-finance) elsewhere in this directory is a third answer again — retiring a governance lever once it has served its purpose.

  • Added – Text at Block 7

    How Caper approaches this Caper is a treasury-and-governance protocol, not a stablecoin issuer, so the honest contrast is about who holds the parameters and whether a dissenter has an exit. On Aave, a borrower or AAVE holder who dislikes a governance-set GHO rate has no structural recourse beyond selling their position — the vote binds everyone who stays. In a caper (/wiki/foundations/what-is-a-caper) , the treasury is the governed object, and two things differ. First, a member’s vote weight (/wiki/governance/voting) is (held × votes) / (vote_supply × circulation) — a product of tokens held and a soulbound, non-transferable record of having actually voted, so a large bag alone cannot capture the control surface the way it can accumulate stkAAVE. Second, when you lose a parameter fight you can exit with your share of the treasury (/wiki/dao/concepts/rage-quit-and-exit-rights) rather than only sell into the market — the majority cannot trap you in a policy you fought. (Mechanics verified against compute_vote_weight and exit in contracts/src/caper_dao.rs; framed at the outcome level, no invented features.)