> For the complete documentation index, see [llms.txt](https://docs.bracket.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bracket.fi/product/brkteth/brkteth-treasury/asset-selection-criteria.md).

# Asset Selection Criteria

### Asset Selection Criteria

For each asset we choose to accept, we may either accept it unconditionally, or with a maximum caped limit.  For example, for an asset with a limited number of holders and or low circulating supply, we would establish a maximum limit we would be willing to accept within the treasury before pausing further deposits of that asset.

When considering a new LST/LRT to be accepted within our treasury, we look at the following factors.    

**Minimum TVL threshold:**\
LST/LRT protocols must have at least 15,000 ETH staked. For projects that have substantial TVL drops, we will review the asset’s viability.

**DeFi:**\
Protocols must have swap markets with ample liquidity against ETH, wETH, or wstETH on L1 Ethereum.

**Security and Audits:** \
Protocols must have verifiable public audits and responsible key management. All severe/high risk issues must be resolved. Medium risks issues must have been addressed, or adequately explained. 

**Team:**\
Team must be contactable and able to offer support.

**Slashing:**\
Must have rigorous validator selection criteria and remediation practices.\
\
**Staking Rate:**\
Competitive rate.\
\
\
\&#xNAN;*Disclaimer: Bracket reserves the right to update these criteria at any time, without notice.*<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bracket.fi/product/brkteth/brkteth-treasury/asset-selection-criteria.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.