TeaVaultV3Port_Beta+LongStrategy_arbitrum

TeaVaultV3Pair_STRK-USDC_Starknet_Jediswap

TeaVaultV3Pair_STRK-ETH_Starknet_Jediswap

TeaVaultV3Pair_USDC-USDT_Starknet_Jediswap

TeaVaultV3Pair_ETH-USDC_Starknet_Jediswap

TeaVaultV3Pair_WBTC-ETH_Starknet_Jediswap

TeaVaultV3Pair_WSTETH-ETH_Starknet_Jediswap

TeaVaultV3Pair_USDC-DAI(new)_Starknet_Jediswap

TeaVaultV3Pair_USDC-gUSDC_Arbitrum_Ramses

TeaVaultV3Pair_SWAY-USDC_Starknet_Jediswap

TeaVaultV3Pair_METH-WETH_Mantle_Cleopatra

TeaVaultV3Pair_USDT-METH_Mantle_Cleopatra

TeaVaultV3Pair_ezETH-WETH_Arbitrum_Ramses

TeaVaultV3Pair_uniETH-WETH_Arbitrum_Ramses

TeaVaultV3Pair_USDT-aUSD_Mantle_Cleopatra

TeaVaultV3Pair_METH-aUSD_Mantle_Cleopatra

TeaVaultV3Pair_WBTC-uniBTC_Optimism_Uniswap

TeaVaultV3Pair_WBTC-tBTC_Arbitrum_Uniswap

TeaVaultV3Pair_ETH-EKUBO_Starknet_Jediswap

All Teahouse Finance codes can be found at https://github.com/TeahouseFinance. Documentation for the assets provided in the table can be found at https://docs.teahouse.finance/teahouse-finance-1/

Teahouse Finance is a multi-strategy DeFi investment platform dedicated to secure and flexible asset management.

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Protocol insolvency

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below. 

__Repeatable Attack Limitations__

In cases of repeatable attacks for smart contract bugs, only the first attack is considered if the smart contracts where the vulnerability exists can be upgraded, paused, or killed. If the attack impacts a smart contract directly holding funds that cannot be upgraded or paused, the amount of funds at risk will be calculated with the first attack being at 100% of the funds that could be stolen and then a reduction of 25% from the amount of the first attack for every 300 blocks the attack needs for subsequent attacks from the first attack, rounded down. For avoidance of doubt, if a second attack would happen at 600 blocks and then a third at 900 blocks, the funds at risk would be counted at 50% and 75% of the reward from the first attack, respectively.

__Restrictions on Security Researcher Eligibility__

Security researchers who fall under any of the following are ineligible for a reward
- On OFACs SDN list 
- Official contributor, both past or present
- Employees and/or individuals closely associated with the project 
- Security auditors who directly or indirectly participated in the audit review

__Previous Audits__

Teahouse Finance has provided these completed audit review reports for reference. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
- [https://vault.teahouse.finance/Teahouse-Finance_audit_report_2023-06-14.pdf](https://vault.teahouse.finance/Teahouse-Finance_audit_report_2023-06-14.pdf)
- https://omniscia.io/reports/teahouse-finance-portfolio-strategy-65ad01e4cd79e50018d6fa75/ 

__Feasibility Limitations__

At Immunefi, we sometimes receive reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. If it’s obviously feasible, then it seems there are no questions about severity or payout amount. But if the bug report is less feasible, or not really feasible at all, suddenly questions arise.

Therefore, Immunefi has developed a set of [feasibility limitation standards ](https://immunefisupport.zendesk.com/hc/en-us/articles/16913132495377-Feasibility-Limitation-Standards)which by default state what a Project should or should not cite when downgrading a bug report’s impact, severity, and/or payout amount. These standards are continuously being developed and updated with the help of the community and encompass fair guidelines where the project clearly commits, and the security researcher can be assured that the project cannot arbitrarily downgrade the program based on theoretical counter measures, such as a [chain rollback. ](https://immunefisupport.zendesk.com/hc/en-us/articles/16913153448721-Chain-Rollbacks)

__Proof of Concept (PoC) Requirements__

A PoC is required for the following severity levels:
- Smart Contract: Critical
- Smart Contract: High

All PoCs submitted must comply with the Immunefi-wide [PoC Guidelines and Rules.](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules) Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

__Reward Payment Terms__

Payouts are handled by the Teahouse Finance team directly and are denominated in USD. However, payments are done in USDC.

Teahouse Finance

Resources & Documentation