Treehouse Protocol

Description sourced from DeFiLlama's protocol metadata; teams submit their own copy when listing.

DeFiLlama publishes the exact rules used to aggregate on-chain balances into the headline TVL figure shown on this page. The methodology below is the team's own source-of-truth description.

Token balance in vault and strategy contracts

If a contract or vault isn't in this list, its balance does not contribute to the TVL displayed on Mantapex or DeFiLlama.

Treehouse Protocol's governance or utility token carries a market capitalisation of US$1085.8万 based on circulating supply at the latest DeFiLlama snapshot. The token's market cap (US$1085.8万) is small relative to deposits secured by the protocol (US$1.8亿); a mcap/TVL multiple of 0.06× is sometimes read as a discount, though it can also reflect minimal fee accrual to the token.

Market cap and supply figures are sourced from DeFiLlama's price feed (which reconciles CoinGecko, CoinMarketCap, and on-chain DEX prices). Treasury and staking values reflect on-chain balances controlled by the protocol at last sync.

由 DeFiLlama 社区标记的重要事件——协议上线、安全攻击、治理变更和激励计划。

1. Sep 10, 2024
   上线 DeFiLlama

Treehouse Protocol operates in the DOR category of DeFi. It is deployed across 3 chains, including Ethereum, Mantle, Avalanche. The codebase has been independently audited (1 report on file).

Treehouse Protocol operates on 3 networks (Ethereum, Mantle, Avalanche), keeping its surface area narrower than chain-agnostic peers. Roughly 100% of its on-chain value sits on just three networks (Ethereum, Mantle, Avalanche), so a fault on any one of them would affect a large slice of users. Only one audit report is currently listed; users should weigh that against the protocol's TVL before depositing significant amounts. Its token market cap (US$1085.8万) is small relative to TVL (US$1.8亿) — a mcap/TVL ratio of 0.06 is often read as the token being structurally undervalued versus the activity it secures.

Verified external resources for Treehouse Protocol — use these to read the source code, follow governance discussions, or cross-check on-chain data against the original team's channels.