
Airdrop · Ethereum
Treehouse TREE airdrop: docs say 25 November, contract allows a sweep from 4 November
Confirmed Verified Risk 3/5
Deadline in
Step by step
- Go directly to gaiafoundation.xyz, the claim address in the Treehouse docs.
- Select Season 2 and connect the wallet eligible at the snapshot.
- Check your allocation and that the call goes to the airdrop contract published in the docs.
- Sign the claim transaction and pay mainnet gas. Each wallet claims once.
- The docs give until 25 November 2026, 07:00 UTC; the contract allows an owner sweep to its reserve address from 4 November 2026, 09:52:47 UTC.
Our notes
The Treehouse TREE airdrop for Season 2 closes on 25 November 2026 at 07:00 UTC, according to Treehouse’s documentation. The verified airdrop contract on Ethereum carries an earlier date. From 4 November 2026 at 09:52:47 UTC, its owner can send all the TREE still inside it to a reserve address, about three weeks before the documented close.
That is a possibility written into the code, not a scheduled event. Nothing we read says a sweep will happen. Neither the docs nor the Season 2 blog post mention 4 November, and they offer no explanation for the difference. At 08:51 UTC on 2 November the contract still held 16,164,631.66 TREE.
A wallet that has already claimed is out of reach of any sweep. One that has not depends, after 4 November, on the owner leaving the tokens in place until the date the docs give. What to do with TREE once claimed is a separate matter, and we take no view on it.
Season 2 airdrop facts: 23.1 million TREE, one claim per wallet
Treehouse is a fixed-income protocol: it issues tETH, a liquid staking token, and runs DOR, a system of staked rate predictions. TREE is its governance and utility token. This Season 2 airdrop shares out 23.1 million TREE, which the blog post puts at 2.31% of supply. We read a total supply of 1,000,000,000 on chain.
| Item | Season 2 figure |
|---|---|
| Snapshot | 25 April 2026, 02:00 UTC, Ethereum mainnet |
| Claims opened | 29 April 2026, 07:00 UTC |
| Distributed | 23,100,000 TREE across three tracks |
| Vesting | 20% at opening, 80% linear over 180 days |
| Vesting ended | 26 October 2026, 07:00 UTC |
| Claim close (docs) | 25 November 2026, 07:00 UTC |
| Owner can sweep to the reserve (contract) | From 4 November 2026, 09:52:47 UTC |
| Cost | Standard mainnet gas, no deposit |
Vesting finished on 26 October. Before then, an early claim gave up the unvested part, up to 80% on day one: the docs say forgone, the contract says penalty. Claim now and the full allocation arrives. We ran the contract’s own claimableBalance calculation on 1,000 TREE on 2 November: 1,000 claimable, zero penalty.
You get one claim per wallet: Treehouse says it can be made at any point in the window, but only once. The FAQ adds that the TREE goes to the eligible wallet itself and that allocations cannot be merged or redirected. Safe multisigs and hardware wallets can claim. Exchange deposit addresses generally cannot, since nobody can sign from them.

Who qualifies for the Treehouse TREE airdrop
Eligibility was fixed at the snapshot block, so nothing done since then counts. A wallet qualifies through any of three tracks, and they stack with no cap.
- GoNuts Season 2 needs at least 500 Total Nuts at the snapshot. That guarantees 100 TREE, plus a pro-rata share of the Nuts Pool, the part of the 23.1 million left once the other two tracks are funded.
- Governance pays a flat 10,000 TREE to a wallet that voted on at least one proposal in the treehouse.eth Snapshot space during Season 2. If you delegated, the allocation goes to the delegate’s wallet, not yours.
- The Treehouse Squirrel Council NFT pays 10,000 TREE per NFT held at the snapshot block.
Below 500 Nuts, the GoNuts track gives nothing. An NFT moved into a third-party staking contract does not count for your wallet, though non-custodial staking does. The worked example in the docs reaches 39,580 TREE for one wallet active on all three tracks, using a rate per Nut that Treehouse labels illustrative only. The blog post adds that wallets flagged by Sybil filtering were excluded or had their allocations reduced, without disclosing the criteria.
Docs say 25 November, the contract allows a sweep from 4 November
The docs say unclaimed TREE after 25 November is returned to the Treehouse treasury, and the blog gives the same date. The contract sets sweepTime once, at deployment, at 190 days after the block that created it. That block is dated 28 April at 09:52:47 UTC. We read the value ourselves on 2 November through two public RPC nodes: 4 November at 09:52:47 UTC. It cannot be changed.
From that moment, the owner may call sweep(), which transfers the contract’s entire TREE balance to the address stored as rewardReserve, today 0x1d8f...2731. The owner can change that address at any time with setRewardReserve. Nobody else can sweep: a read-only simulation on 2 November was refused as too early for the owner and as unauthorised for an outside address. Nothing fires automatically, and nothing obliges the owner to act or to wait. After a sweep, a claim would fail for lack of tokens unless TREE were sent back.
The claim function has no deadline at all. It checks the tranche, whether the wallet has claimed, the Merkle proof and the start time. So 25 November exists in the docs and the blog, not in the code. Claims could technically keep working after that date while tokens remain and the tranche stays open, although the docs say the window closes. A separate owner function, closeTranche, can erase the Merkle root at any time, and without the root no proof passes.
What we report here is a difference between the docs and the code, and nothing more: the owner may well leave the right unused until 25 November. The contract’s creator is an address Etherscan labels Treehouse: Deployer 1. Its owner today is a Safe-type multisig (0x2226...01f6) that requires five of seven signatures, according to its own getOwners and getThreshold functions. We could not identify the signers.
The reserve is a Safe-type wallet with a single owner, and it held 532,596.86 TREE on 2 November. It may be the treasury the docs mention, but nothing we read says so.
The 16.16 million TREE balance is not a head count. Claimed tokens have left the contract, and so have forfeited amounts. Public nodes would not give us the event logs, so we know neither how many wallets are still waiting nor exactly how much the contract first received. That is why we do not turn the figure into a share of the 23.1 million.
How to claim TREE Season 2, step by step
- Type gaiafoundation.xyz yourself. It is the claim address on the key-information page, and the blog says to go there directly.
- Select Season 2 and connect the wallet that was eligible at the snapshot.
- Check the allocation. Before signing, confirm that your wallet shows a call to
claimon the airdrop contract 0x0bE45e75797155078417d1a0c32c8B8926403c87, the address the docs publish. - Sign the claim transaction and pay standard mainnet gas in ETH.
- Check the TREE balance in your wallet. Staking or delegating is optional and comes after the claim.
The blog sends claimants to Gaia Foundation and lists it among company links. Neither the blog nor the docs say what it is: no legal entity, no jurisdiction, no role. The site refused our automated request, so we have not read any terms it may carry.
Season 1 rules do not apply here
Searches for this airdrop still return Season 1 terms, above all a vested program with a 50% Universal Buff, a staking condition and a 15-month claim window. None of that appears in the Season 2 docs or blog: no such buff, no vested option, no staking requirement. Nuts boosts from quests and badges are a different thing and fed the Season 2 points. The Season 1 Treasury Bonus that the blog mentions was claimable until 27 October, a date now past.
US and China excluded, EU not named
Treehouse’s terms of service (version 2.0, updated 29 August 2025) say the service is not intended for excluded persons or jurisdictions. They name the United States and its territories, the People’s Republic of China and jurisdictions on the FATF high-risk list, then add any place where Treehouse would be prohibited or need a licence. EU countries, France and Italy are not named.
That silence settles nothing, given the catch-all. The terms have no airdrop section and refer to a “TRH Token” rather than TREE, an inconsistency we cannot explain. The docs also carry a MiCAR white paper page with an attachment we did not read, so we say nothing about the issuer or the notifying authority. Our guide to MiCA and US rules has the wider picture.
Risk score: 3 out of 5
Published docs, a contract verified on Etherscan and a claim that takes no deposit pull the score down. Pushing it up: the owner’s sweep right ahead of the documented close, and a claim site tied to a Foundation the docs do not define. TREE is also a volatile token, and DefiLlama shows Treehouse’s total value locked at about $61.7 million on 2 November against $178.2 million on 15 April. A claim asks for gas only, so the danger to a wallet lies mainly in what you sign.
Treehouse’s security page says the team will never send a direct message asking you to claim, and that any DM claiming to be Treehouse support is a scam. Be wary of any request to sign a message that moves tokens or grants unlimited approvals. Our searches on 2 November found no fake TREE claim campaign aimed at Season 2. Our routine for revoking token approvals covers the clean-up if you have signed something odd.

Next dates and what we still do not know
A sweep becomes possible on 4 November at 09:52:47 UTC, and the documented close is 25 November at 07:00 UTC. We do not know whether the owner will sweep, who holds the seven keys, or how Gaia Foundation is constituted. We will update this page if the docs change or a sweep shows up on chain.
Crypto-assets are volatile and you can lose all the money you invest. Nothing published on Coindaro is investment advice.






