# Snapshot 15: Strengthening TREE Token Security Through Risk Controls

- Space: [Treehouse DAO](https://snapshot.box/s:treehousefi.eth.md)
- Author: 0x657910807E63e9E50C96Eb062d795DdA16B9ff1D
- State: Passed
- Voting type: Basic
- Start: 2026-11-01 15:05 UTC
- End: 2026-11-04 15:05 UTC
- Votes: 18
- Discussion: https://governance.treehouse.finance/t/tip-15-strengthening-tree-token-security-through-risk-controls/48
- Open in Snapshot: https://snapshot.box/#/s:treehousefi.eth/proposal/0xc9d7d8645643bdc8243578e231ec758b562b64f8833ab02e03eac162e1a2d96a

## Results

- For: 2,200.49 voting power, 85.7%
- Against: 368.2 voting power, 14.3%
- Abstain: 0 voting power, 0.0%

## Proposal

## Summary

This proposal seeks DAO approval to upgrade the **TREE** token contract to include a **blacklisting function**, allowing specific addresses to be restricted from interacting with and transferring TREE in the event of a security incident.

The function is intended as a risk control for exploit scenarios, such as a hack or theft involving TREE, and would operate under defined access controls. If approved, it will apply to TREE across all supported networks.

**Token Details:**

- Token: Treehouse (TREE)
- Address: 0x77146784315ba81904d654466968e3a7c196d1f3
- Networks:
  - Ethereum (ERC-20)
  - BNB Chain
  - Avalanche
  - Arbitrum
  - Base
  - HyperEVM

## Motivation

As the Treehouse ecosystem grows, TREE is held and used across more venues, networks, and integrations. This increases the potential impact of a security incident involving the token.

A blacklisting function would allow the protocol to respond to a confirmed exploit by restricting the movement of stolen funds, limiting downstream harm to holders and integrated venues.

Implementing this function is expected to:

- Provide a response mechanism for exploit scenarios involving TREE
- Reduce the risk of stolen TREE being sold or laundered through integrated venues
- Strengthen TREE's security posture as its footprint expands across networks and integrations

Because this function introduces a privileged power over holder addresses, this proposal limits its use to confirmed security incidents and places control with the Treehouse protocol multisig.

## Specification

If approved, this proposal will:

- Upgrade the TREE token contract to include a blacklisting function that restricts a specified address from interacting with and transferring TREE
- Apply the blacklisting function to TREE on all supported networks
- Assign control of the function to the Treehouse protocol multisig
- Limit use of the function to confirmed security incidents, such as an exploit involving stolen or fraudulently obtained TREE
- Include a function to remove an address from the blacklist

No existing balances, allocations, or vesting schedules will be changed under this proposal.

The DAO retains authority to revise, restrict, or remove the blacklisting function through future governance proposals.

## Risk Considerations

The upgrade introduces exposure to the following risks:

- Smart contract risk from the contract upgrade
- Centralization risk, as the function grants power to restrict holder addresses
- Integration risk, as blacklist logic may affect bridges, liquidity pools, or exchange integrations if not properly scoped

**Mitigations**

- Use of the function is limited to confirmed security incidents
- Control of the function sits with the Treehouse protocol multisig
- Blacklisted addresses can be removed from the blacklist
- The upgraded contract will be audited before deployment
- DAO authority to revise the function through governance

## Implementation

If approved, the DAO assigns Treehouse Protocol to:

1. Finalize the technical design of the blacklisting function, including access controls
2. Develop the upgraded TREE contract
3. Submit the upgraded contract for security audit
4. Verify compatibility with existing bridges, liquidity pools, and integrations
5. Deploy the upgrade on Ethereum and apply it to TREE on all other supported networks

## Voting Options

- For – Approve the upgrade of the TREE token contract to include a blacklisting function, controlled by the Treehouse protocol multisig and limited to confirmed security incidents
- Against – Reject the proposal
- Abstain – Record sentiment without voting for or against

## Vote Outcomes

**If FOR passes:**
The TREE token contract will be upgraded to include the blacklisting function on all supported networks, with control assigned to the Treehouse protocol multisig.

**If AGAINST passes:**
No changes will be made to the TREE token contract.

**If ABSTAIN:**
No direct effect; recorded for sentiment but not counted toward quorum.

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

