Treehouse’s TIP 15 proposal would let its protocol multisig restrict addresses associated with Treehouse (TREE) during theft or exploits involving the token, as TREE’s wider use across networks and venues may increase an incident’s impact.
A flagged address could lose the ability to move TREE or use its token contract across Treehouse-supported networks. The proposal reserves the control for substantiated cases tied to the token, including theft or an exploit. It also provides a way to clear addresses and allows future DAO proposals to change or remove the function.
TIP 15 presents the blacklist as a way to contain illicit transfers and limit harm to holders and connected venues. It says the current contract lacks an address-restriction tool, while TREE’s use across venues, networks and integrations could increase the effects of an incident.
The proposal acknowledges that giving the multisig power over holder addresses raises a centralization concern. It also warns that restrictions could disrupt bridges, liquidity pools or exchange integrations.
A formal Snapshot vote on TIP 15 is underway and is scheduled to close Nov. 4. If approved, the team would complete the design, develop and audit the contract changes, and check compatibility with existing integrations before deployment.
