Deep Dive
1. Token Buyback Proposal (November 2025)
Overview: This is a governance proposal, not a code update. It aims to create a sustainable link between protocol revenue and token value by automatically reinvesting fees.
The Treehouse Improvement Proposal (TIP 4) seeks to allocate 50% of all protocol fees generated from its first tAsset, tETH, toward recurring open-market purchases of TREE tokens. These buybacks would be executed weekly via a designated Ethereum wallet, with all purchased tokens held in DAO reserves. The goal is to align token value with protocol growth, reduce circulating supply, and build treasury resilience.
What this means: This is neutral for TREE as it's a proposal, not an implemented feature. If approved, it could create a steady source of buying pressure for the token, potentially making it more scarce over time as the protocol earns more fees. However, its impact depends entirely on community voting and subsequent successful execution.
(Source)
2. DOR Staking Program Launch (April 2026)
Overview: This activation of the Pre-Deposit Vaults represents the launch of a previously designed staking mechanism, not a new code release.
The program allows TREE holders to stake tokens into on-chain vaults backing specific rate forecasters (Panelists) within the Decentralized Offered Rates (DOR) system. Stakers lock their TREE for nine months and earn rewards between 50% and 75% APR, with the actual yield tied to their chosen Panelist's prediction accuracy.
What this means: This is bullish for TREE because it activates a core utility, creating immediate demand for staking. It incentivizes users to lock up their tokens for an extended period, which can reduce selling pressure on the market. The high introductory APRs are designed to bootstrap participation in the protocol's rate-setting system.
(Source)
Conclusion
Recent developments for Treehouse have centered on activating economic utilities like staking and proposing value-accrual mechanisms, rather than publishing new codebase versions. How will developer activity and commit history reflect this focus on protocol maturation?