History – Fee switches and value accrual

Back
v1.4.6 · currentEm dashes become spaced en dashes (VOICE.md); dashes inside quotes kept–
1 block modified
  • Modified – Text at Block 11

    References - Uniswap Labs & Uniswap Foundation —– UNIfication (proposal blog po…tion) - Uniswap governance —– Proposal 93: UNIfication (fin…als/93) - Uniswap Snapshot —– [Temp Check] Activate v4 Prot…add5f4) - Uniswap Snapshot —– [Temp Check] Protocol Fee Exp…) - Uniswap Snapshot space —– full fee-switch voting record…nce.eth) - Aave governance —– [ARFC] Aavenomics implementat…e/21248) - Aave governance —– [ARFC] Buyback Program: Budge…t/24229) - Aave governance —– Restart AAVE buy backs (May 2…/24936) - Jupiter Research —– Increase the Litterbox buybac…llocation-from-50-to-70/40136)

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

    Concept Fee switch —– diverting a share of protocol…easury Landmark case Uniswap —– voted on from 2021, activated…iki/economics/token-valuation)

  • Modified – Text at Block 2

    A fee switch is a governance-c…of someone's existing revenue —– usually liquidity providers —– turning one on is a redistrib…rs before flipping the switch.

  • Modified – Text at Block 3

    What a fee switch actually swi…nterparties who take the risk —– liquidity providers, deposito…lf is usually trivial in code —– a factory owner setting a fee numerator —– and hard in governance, for t… it to stakers, or banking it —– and each choice creates a dif…t constituency inside the DAO.

  • Modified – Text at Block 4

    Four years of votes, no fee: t…ed in production. The pattern —– repeated large-turnout votes …wed by no on-chain activation —– is itself the lesson: a fee s…ch is the more valuable asset —– ownership as “the threat of the fee” —– on the reasoning that actuall…lised revenue over the threat.

  • Modified – Text at Block 5

    UNIfication: what turning it o… and the protocol takes 0.05% —– the LPs pay for it directly. … operations into Uniswap Labs —– deflation on one side, an ong…uance commitment on the other.

  • Modified – Text at Block 6

    The burn is a market, not a tr… and sent to the burn address —– on Arbitrum Orbit chains thro…hed ten chains beyond mainnet —– Arbitrum, Base, OP Mainnet, W…, Celo, BNB Chain and Polygon —– and the same proposal records…antial dissent of the rollout —– 19.3M UNI for against 1.0M ex…itly opposed, from 132 voters.

  • Modified – Text at Block 7

    Where the revenue goes: four r…reates no ongoing entitlement —– the Uniswap route. - Buyback… benefit on committed holders —– the vote-escrow (/wiki/dao-g…exibility, minimum legibility —– holders get nothing until gov…/economics/token-valuation) ).

  • Modified – Text at Block 8

    Aave: what a discretionary buy…m roughly $50M to $30M a year —– about $577K a week, down from $962K —– citing borrow fee revenue rou…en traded far below its highs —– exactly when a confidence-sig…tee is procyclical twice over —– the revenue falls when the ma…gets pulled at the worst time.

  • Modified – Text at Block 9

    Jupiter: the allocation itself…t on does not settle anything —– it converts an operating budg…d a hard one to argue against.

  • Modified – Text at Block 10

    How Caper approaches this A …f the registry's current_main —– the upgrade path (/wiki/gove…older's canonical vote weight —– a function of both their gove… tokens and their vote tokens —– and burns their vote tokens o…ance is the spending question.

  • Modified – Text at Block 11
v1.4.4Em dashes become spaced en dashes (VOICE.md); dashes inside quotes and source titles kept–
1 block modified
  • Modified – Text at Block 5

    UNIfication: what turning it o…the supply itself never moves —– it is still exactly 1,000,000…uance commitment on the other.

v1.4.3Split paragraphs over 150 words at sentence boundaries; wording unchanged.–
2 blocks modified
  • Modified – Text at Block 8

    Aave: what a discretionary buy…ate or condition for resuming.A forum thread opened 18 May …gets pulled at the worst time.

  • Modified – Text at Block 10

    How Caper approaches this A …er and to the $CAPER treasury.The shares are platform-wide r…ance is the spending question.

v1.4.2The trade fee is gone: the skim now splits 49.5% to the caper's treasury, 50% to the founder and 0.5% to the $CAPER treasury–
1 block modified
  • Modified – Text at Block 10

    How Caper approaches this A …ee switch to vote on, because the fee is onits treasury takes a share of every trade from the first tradone. Every buy and every sell against the bonding curve (/w…/markets/bonding-curve) pays a trade fee, 0.5% in the deployed contract, takenthe skim, at a rate that falls as the curve fills, and 49.5% off the gross andskim is deposited into that caper's own treasury as part ofin XRD, in the same call that releasmoves the tokens from the caper's fixed 100bn inventory. A sell pays no trade fee. The rate is. The rest goes to the founder and to the $CAPER treasury. The shares are platform-wide rather than per-caper, and it isthey are not a parameters anyone sets: trade_fee is written once when the shared logic component is instantiated and no method on that component writes it againhey are constants compiled into the shared logic component, so moving ithem takes a fresh logic component…d and nothing is bought back. Fee revenuThe skim share accumulates in the treasury alongside the proposal and vote fees, and holders reach it two way…ance is the spending question.

v1.4.1Point to Aragon's Ownership Token Framework, which scores control of revenue routing–
1 block modified
  • Modified – Text at Block 7

    Where the revenue goes: four r…whatever the spreadsheet says. Aragon's Ownership Token Framework, launched in February 2026, scores tokens on this question by reading from their contracts who controls revenue routing ( token valuation (/wiki/economics/token-valuation) ).

v1.4.0Sweep #443: a buy releases tokens from the caper's fixed inventory, it does not mint them (core buy_apply takes from inventory_vault)–
1 block modified
  • Modified – Text at Block 10

    How Caper approaches this A …as part of the same call that mintreleases the tokens from the caper's fixed 100bn inventory. A sell pays no trade fee. Th…ance is the spending question.

v1.3.1Remove the $XRD caper and its reference basket, and say a sell pays no trade fee. Both follow the 18 September 2026 redeploy.–
1 block modified
  • Modified – Text at Block 10

    How Caper approaches this A …om the first trade. Every buy and sell against the bonding curve (/w…nding-curve) pays a trade fee —, 0.5% in the deployed contract —, taken off the gross. The buy-side fee is and deposited into that caper's o…ame call that mints the tokens; the sell-side fee goes to the treasury of the root $XRD caper, which is the platform's single sell-fee sink. A sell pays no trade fee. The rate is platform-wide ra…ance is the spending question.

v1.3.0Aave section: cite the Snapshot votes behind the March 2026 budget cut and the May 2026 buyback pause, which followed the rsETH bridge exploit; date the absence of an Aavenomics 3.0 proposal–
1 block modified
  • Modified – Text at Block 8

    Aave: what a discretionary buy…gainst $13.5M in January 2025. Then the buybacks stopped altogether The cut passed a Snapshot vote that closed on 15 March 2026 (https://snapshot.box/#/s:aavedao.eth/proposal/0xe1f47bd04001269432d2e74e76b79747e1458e90b0e3b2cdee7be6495d96e056) , about 363,000 $AAVE for and 3,200 against. Then the buybacks stopped altogether, and a security incident stopped them rather than revenue. On 18 April 2026 an exploit of Kelp's LayerZero bridge route for rsETH, Kelp's restaked-ETH token, put unbacked rsETH into Aave V3 markets on several chains. TokenLogic, the service provider running the programme, executed no buyback after 19 April, and its request for final comment formalising the pause (https://governance.aave.com/t/arfc-pause-aave-buybacks/24686) passed on Snapshot on 1 May 2026 (https://snapshot.box/#/s:aavedao.eth/proposal/0x10a2af0110b1ad6f4afd7a3a052b2a119d102cc22949e80e9bbd5132587107c8) , about 617,000 $AAVE for and 4,900 against. It keeps the pause in place until the rsETH position is clearer and names no date or condition for resuming. A forum thread opened 18 Ma…ted, non-discretionary engine. As of 15 September 2026 no proposal to build that engine had been posted to Aave's governance forum (https://governance.aave.com/) , and the August/September 2026 funding update (https://governance.aave.com/t/direct-to-aip-august-september-2026-funding-update/25597) , posted 1 September, provides for GHO runway, operations and a private-credit trial without mentioning buybacks. That arc is the general less…gets pulled at the worst time.

v1.2.0Sweep #419: sell-side trade fee goes to the root $XRD caper's treasury (the sell-fee sink, contracts/logic/src/lib.rs xrd_fee_sink), not $CAPER; Aave restart thread re-read (autoclosed a month after its 25 June last reply, which relayed the Aavenomics 3.0 automated-buyback announcement); Jupiter 50->70% thread dated (no formal vote as of 25 July 2026).–
3 blocks modified
  • Modified – Text at Block 8

    Aave: what a discretionary buy… wanted and least affordable. The thread closed in July without aIts last reply, on 25 June, relayed Stani Kulechov's announcement (https://x.com/StaniKulechov/status/2070089062648623169) that Aavenomics 3.0 would bring “immutable and automated buybacks of AAVE”, and the thread closed automatically a month later with no decision recorded in it; t. The direction governance took insteadAave's founder set was to remove the discretion,…gets pulled at the worst time.

  • Modified – Text at Block 9

    Jupiter: the allocation itself…t the operating budget to 30%. As of the thread's last reply, on 25 July 2026, it had not been put to a formal vote. This is the fee switch's sec…d a hard one to argue against.

  • Modified – Text at Block 10

    How Caper approaches this A …the sell-side fee goes to the $CAPER treasury atof the protocol levelroot $XRD caper, which is the platform's single sell-fee sink. The rate is platform-wide ra…ance is the spending question.

v1.1.2Run #351: name the hyperstructures 'threat of the fee' argument the four-year delay is evidence for, and link the concept pillar UNIfication tested.–
1 block modified
  • Modified – Text at Block 4

    Four years of votes, no fee: t…mainnet in late December 2025. There was also a case for never flipping it, and it is worth naming because the four-year delay is exactly what it predicted. Jacob Horne's hyperstructures (/wiki/dao-governance/concepts/fundamentals/hyperstructures) essay argued that an unexercised fee switch is the more valuable asset — ownership as “the threat of the fee” — on the reasoning that actually charging it “would immediately lead to an incentivized fork.” UNIfication is the largest test that argument has had, and what the record below shows is holders choosing realised revenue over the threat.

v1.1.1Correct the fee/upgrade authority against the deployed contract: CaperMain has no fee, peak or vote-rate setter (all three are written once in init), set_current_main is a one-time bootstrap, and the registry authorises both an operator backstop and a $CAPER UPGRADE path behind one timelock.–
1 block modified
  • Modified – Text at Block 10

    How Caper approaches this A …e protocol level. The rate is a protocol parameter set by the admin key, not a per-DAO governance decision, so nplatform-wide rather than per-caper, and it is not a parameter anyone sets: trade_fee is written once when the shared logic component is instantiated and no method on that component writes it again, so moving it takes a fresh logic component and a move of the registry's current_main — the upgrade path (/wiki/governance/execution) , open to the protocol admin badge behind the registry's timelock or to a settled $CAPER UPGRADE proposal. No individual caper spends a go…ng about whether to charge one, because no individual caper can answer the question. Nothing is burned and nothi…ance is the spending question.

v1.1.0Sweep #207: the UNIfication burn is exact (100,000,000 UNI to 0x…dEaD) and does not reduce supply — the UNI contract has no burn function and totalSupply is still 1,000,000,000. Inbound link to the deepened daos/dexs/uniswap-dao.–
1 block modified
  • Modified – Text at Block 5

    UNIfication: what turning it o…s are used to remove UNI from supplycirculation rather than to fund the DAO, …money. - A retroactive burn. 100 millionExactly 100,000,000 UNI was burnedsent from the treasury as an estimate of what the switch would have destroyed had it been live since launchTimelock to 0x000…dEaD (https://eth.blockscout.com/address/0x000000000000000000000000000000000000dEaD) in the execution transaction, as an estimate of what the switch would have destroyed had it been live since launch. "Burn" is the convention rather than the mechanism: the UNI contract has no burn function, so the supply itself never moves — it is still exactly 1,000,000,000 UNI, with 10.8% of it now parked at an address nobody holds a key to. The on-chain detail is on Uniswap DAO (/wiki/daos/dexs/uniswap-dao) . - Adjacent revenue. Unichai…uance commitment on the other.

v1.0.0Create cornerstone: fee switches and value accrual — the Uniswap 2021–2026 record, UNIfication mechanics and the TokenJar/firepit burn, the four revenue destinations, Aave's discretionary buyback under stress, Jupiter's Litterbox allocation fight, and a contract-verified Caper note.–
11 blocks added
  • Added – Text at Block 1 → Block 1

    Concept Fee switch — diverting a share of protocol revenue from service providers to the DAO and its token Also called Protocol fee, value accrual, revenue switch Who pays Usually liquidity providers or lenders, out of fees they previously kept in full Where the money goes Burn · open-market buyback · distribution to stakers · retained treasury Landmark case Uniswap — voted on from 2021, activated December 2025 by UNIfication (proposal 93) (https://vote.uniswapfoundation.org/proposals/93) Related Liquidity mining (/wiki/economics/liquidity-mining) · DAO tokenomics (/wiki/dao-governance/concepts/treasury/dao-tokenomics) · Token valuation (/wiki/economics/token-valuation)

  • Added – Text at Block 2

    A fee switch is a governance-controlled parameter that takes a slice of the fees a protocol already charges its users and routes it to the protocol itself rather than to the people supplying the service. It is the mirror image of liquidity mining (/wiki/economics/liquidity-mining) : where liquidity mining pays tokens out to rent capital, a fee switch brings revenue in, and the governance question shifts from how much to emit to who receives the income and in what form. Because the fee comes out of someone's existing revenue — usually liquidity providers — turning one on is a redistribution inside the protocol's own economy, not free money, which is why the largest DAOs argued about it for years before flipping the switch.

  • Added – Text at Block 3

    What a fee switch actually switches Most DeFi protocols charge a fee at the point of use: a swap fee on an automated market maker (/wiki/economics/capital-markets) , an interest spread on a lending market, a redemption fee on a stablecoin. In the standard design that fee is paid entirely to the counterparties who take the risk — liquidity providers, depositors, stakers. A fee switch inserts a second recipient: the contract keeps a configurable fraction and sends it somewhere the DAO controls. The switch itself is usually trivial in code — a factory owner setting a fee numerator — and hard in governance, for three reasons that recur in every fee-switch debate: - It is taken from someone. Raising the protocol's cut lowers LP returns, and liquidity is mobile; a protocol that taxes its LPs while a fee-free fork exists invites them to leave. - It changes what the token is. A token that receives a stream of protocol revenue looks materially more like a security in several jurisdictions than one that only votes, which kept counsel cautious and votes non-binding for years. - It forces a distribution question. Once revenue exists, governance must decide between burning it, buying the token back, paying it to stakers, or banking it — and each choice creates a different constituency inside the DAO.

  • Added – Text at Block 4

    Four years of votes, no fee: the Uniswap record Uniswap (/wiki/daos/dexs/uniswap-dao) 's governance record is the clearest primary-source account of how long the question stayed open. The Snapshot space (https://snapshot.box/#/s:uniswapgovernance.eth) shows a fee-switch vote as early as 25 July 2021 (“Turning on the fee switch for V2”, 354 voters), a July 2022 temperature check for ETH/USDC and USDC/USDT pools, a consensus check for a three-pair pilot that closed 9 August 2022 with 2,373 voters, a three-part “Making Protocol Fees Operational” vote on fee options, deployment chain and treasury asset that closed 1 June 2023, and a “V3 Fees: Factory Owner Amendment” vote that closed 9 March 2024 with 50.2M UNI of weight behind it. None of them resulted in a fee being charged in production. The pattern — repeated large-turnout votes in favour of the principle, followed by no on-chain activation — is itself the lesson: a fee switch is not blocked by the vote count but by the legal, competitive and operational questions that sit underneath it. Uniswap only began charging protocol fees on Ethereum mainnet in late December 2025.

  • Added – Text at Block 5

    UNIfication: what turning it on looked like The change arrived as a single bundled proposal, UNIfication (https://blog.uniswap.org/unification) , which passed with 125,342,017 UNI for and 742 against (https://vote.uniswapfoundation.org/proposals/93) and executed on 28 December 2025. It is worth reading as a template, because it shows how much rides alongside the switch: - The fee. On v2, the LP fee drops from 0.30% to 0.25% and the protocol takes 0.05% — the LPs pay for it directly. On v3 the protocol fee is one quarter of the LP fee in smaller pools and one sixth in larger ones, rolled out first across the pools representing most of mainnet LP fees. - The destination is a burn, not a treasury. Fees are used to remove UNI from supply rather than to fund the DAO, sidestepping the question of who spends the money. - A retroactive burn. 100 million UNI was burned from the treasury as an estimate of what the switch would have destroyed had it been live since launch. - Adjacent revenue. Unichain sequencer fees, net of L1 data costs and the 15% share to Optimism, feed the same burn; the proposal put those at roughly $7.5M annualised. - An offsetting spend. The same proposal created a 20M UNI annual growth budget paid quarterly from 1 January 2026, and moved Foundation operations into Uniswap Labs — deflation on one side, an ongoing issuance commitment on the other.

  • Added – Text at Block 6

    The burn is a market, not a transfer The mechanism Uniswap shipped is more interesting than “fees buy tokens.” Fees accumulate on each chain in a TokenJar, and searchers claim those accumulated fees by paying UNI, which is bridged back to Ethereum mainnet and sent to the burn address — on Arbitrum Orbit chains through a releaser contract named ArbitrumOrbitResourceFirepit. The protocol never has to sell the fee assets or hold an inventory: it auctions them to searchers and denominates the price in the token it wants destroyed, which is why the burn works identically on any chain the DEX deploys to. By the July 2026 Robinhood Chain expansion vote (https://snapshot.box/#/s:uniswapgovernance.eth/proposal/0xc5fd6e916655b293c903b060906c994ff1ff1df348336b3b3e22ceecd2d13d7c) , protocol fees had reached ten chains beyond mainnet — Arbitrum, Base, OP Mainnet, Worldchain, X Layer, Soneium, Zora, Celo, BNB Chain and Polygon — and the same proposal records a single-day record of 186,000 UNI burned in June 2026. Uniswap deployed to Robinhood Chain at that chain's 1 July 2026 mainnet debut and crossed $1bn of cumulative swap volume there within ten days. UNIfication also changed the governance of the parameter, not just its value: fee-parameter proposals now skip the RFC stage and go straight to a five-day Snapshot followed by an on-chain vote. A fee switch that is expected to move often needs a fast path, and building one is part of the design. The v4 protocol fee activation (https://snapshot.box/#/s:uniswapgovernance.eth/proposal/0x3fda3c04fa106ad45173011ef4dfa5db2f14cd35c3c3a7a40f067a44cbadd5f4) ran through it in July 2026 and drew the first substantial dissent of the rollout — 19.3M UNI for against 1.0M explicitly opposed, from 132 voters.

  • Added – Text at Block 7

    Where the revenue goes: four routes Once a protocol collects revenue, four destinations dominate practice, and each one distributes benefit differently: - Burn. Revenue buys the governance token and destroys it. The benefit is spread pro-rata across every holder through supply reduction, requires no claim, and creates no ongoing entitlement — the Uniswap route. - Buyback and hold. Revenue buys the token into a treasury or trust rather than destroying it, keeping the tokens available for future use. It is reversible, which is both the feature and the objection. - Distribution to stakers. Revenue is paid to holders who lock or stake, concentrating the benefit on committed holders — the vote-escrow (/wiki/dao-governance/concepts/voting/vote-escrow) logic applied to income rather than emissions, and the version that most resembles a dividend. - Retention. Revenue simply accrues to the treasury (/wiki/dao-governance/concepts/treasury/dao-treasury-management) and is spent by proposal. Maximum flexibility, minimum legibility — holders get nothing until governance decides they do. The choice is not primarily financial. Burning and distributing hand value to holders automatically; retaining hands it to whoever controls the proposal process. A DAO with weak participation (/wiki/dao-governance/concepts/analysis/voter-apathy) that retains revenue is choosing to concentrate power, whatever the spreadsheet says.

  • Added – Text at Block 8

    Aave: what a discretionary buyback does under stress Aave (/wiki/daos/lending/aave-dao) took the buyback route and its governance forum documents, unusually clearly, what happens when revenue falls. The Aavenomics implementation (https://governance.aave.com/t/arfc-aavenomics-implementation-part-one/21248) gave a finance committee a mandate to buy AAVE on the secondary market at $1M per week. In March 2026 the DAO proposed cutting the programme (https://governance.aave.com/t/arfc-buyback-program-budget-adjustment/24229) from roughly $50M to $30M a year — about $577K a week, down from $962K — citing borrow fee revenue roughly 25% off its peak, with January 2026 at $7.95M against $13.5M in January 2025. Then the buybacks stopped altogether. A forum thread opened 18 May 2026 (https://governance.aave.com/t/restart-aave-buy-backs/24936) asked governance to restart them, with contributors noting that the pause landed while the token traded far below its highs — exactly when a confidence-signalling buyback is most wanted and least affordable. The thread closed in July without a decision recorded in it; the direction governance took instead was to remove the discretion, replacing committee-executed purchases with an automated, non-discretionary engine. That arc is the general lesson of discretionary value accrual: a buyback funded from revenue and executed by a committee is procyclical twice over — the revenue falls when the market falls, and the committee's appetite falls with it. Automation is not a yield improvement; it is a governance decision to remove a lever that gets pulled at the worst time.

  • Added – Text at Block 9

    Jupiter: the allocation itself becomes the recurring vote Jupiter (/wiki/daos/dexs/jupiter) routes 50% of protocol fees into buying JUP for its Litterbox Trust, with the other half funding development, operations, incentives and ecosystem growth. Because that split is a governance parameter rather than a constant, it becomes a standing subject of debate: a proposal posted 30 May 2026 (https://discuss.jup.ag/t/increase-the-litterbox-buyback-allocation-from-50-to-70/40136) asks to raise the buyback allocation from 50% to 70% and to burn the purchased tokens outright instead of holding them in trust, which would cut the operating budget to 30%. This is the fee switch's second-order effect and the one DAO treasurers should plan for. Turning it on does not settle anything — it converts an operating budget into a percentage that holders can vote to reduce, and every subsequent bull market makes “burn more, spend less” an easy proposal to write and a hard one to argue against.

  • Added – Text at Block 10

    How Caper approaches this A caper (/wiki/foundations/what-is-a-caper) has no fee switch to vote on, because the fee is on from the first trade. Every buy and sell against the bonding curve (/wiki/markets/bonding-curve) pays a trade fee — 0.5% in the deployed contract — taken off the gross. The buy-side fee is deposited into that caper's own treasury as part of the same call that mints the tokens; the sell-side fee goes to the $CAPER treasury at the protocol level. The rate is a protocol parameter set by the admin key, not a per-DAO governance decision, so no individual caper spends a governance cycle arguing about whether to charge one. Nothing is burned and nothing is bought back. Fee revenue accumulates in the treasury, and holders reach it two ways: a proposal (/wiki/governance/proposals) that spends it, or exit (/wiki/dao-governance/concepts/membership/rage-quit-and-exit-rights) , which pays out a share of the treasury computed from the holder's canonical vote weight — a function of both their governance tokens and their vote tokens — and burns their vote tokens on the way out. That is a deliberately narrower design than the ones above: the accrual question is settled in code, and what remains for governance is the spending question.

  • Added – Text at Block 11

    References - Uniswap Labs & Uniswap Foundation — UNIfication (proposal blog post) (https://blog.uniswap.org/unification) - Uniswap governance — Proposal 93: UNIfication (final tally and execution record) (https://vote.uniswapfoundation.org/proposals/93) - Uniswap Snapshot — [Temp Check] Activate v4 Protocol Fees (July 2026) (https://snapshot.box/#/s:uniswapgovernance.eth/proposal/0x3fda3c04fa106ad45173011ef4dfa5db2f14cd35c3c3a7a40f067a44cbadd5f4) - Uniswap Snapshot — [Temp Check] Protocol Fee Expansion: Robinhood Chain (July 2026, TokenJar and firepit burn path) (https://snapshot.box/#/s:uniswapgovernance.eth/proposal/0xc5fd6e916655b293c903b060906c994ff1ff1df348336b3b3e22ceecd2d13d7c) - Uniswap Snapshot space — full fee-switch voting record, 2021–2026 (https://snapshot.box/#/s:uniswapgovernance.eth) - Aave governance — [ARFC] Aavenomics implementation: Part one (https://governance.aave.com/t/arfc-aavenomics-implementation-part-one/21248) - Aave governance — [ARFC] Buyback Program: Budget Adjustment (March 2026) (https://governance.aave.com/t/arfc-buyback-program-budget-adjustment/24229) - Aave governance — Restart AAVE buy backs (May 2026) (https://governance.aave.com/t/restart-aave-buy-backs/24936) - Jupiter Research — Increase the Litterbox buyback allocation from 50% to 70% (May 2026) (https://discuss.jup.ag/t/increase-the-litterbox-buyback-allocation-from-50-to-70/40136)