Strata is a general-purpose risk-tranching protocol that brings structured yield products to
diverse on-chain and off-chain yield strategies by splitting underlying yield into tokenized Senior and Junior tranches, each tailored to distinct risk–reward profiles.
Since launching its first markets on Ethena USDe and later on Neutrl NUSD, Strata has grown to over $250M in TVL with 13,000+ users participating across both markets. Over the coming months, Strata plans to expand horizontally to additional yield products, including curated lending vaults, managed multi-strategy vaults, exotic delta-neutral strategies, tokenized private credit, high-yield RWAs etc.
For more information about Strata, please visit https://strata.markets
PoC Required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
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
Temporary freezing of funds
Smart contract unable to operate due to lack of token funds
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Contract fails to deliver promised returns, but doesn't lose value
Out of scope
The following will not qualify for bounty:
- UI and frontend bugs not causing financial loss
- Minor issues such as typos, formatting problems, or “best practice” suggestions without security impact
- Social engineering, phishing attempts, or external ecosystem vulnerabilities
- Bugs in third-party dependencies not directly part of Strata’s deployed contracts
- Incorrect data supplied by third party oracles
- Lack of liquidity impacts
- Centralization risk or attacks requiring access to privileged keys
- Impact related to attacks that are already exploited and have damaged the protocol
- Impacts involving centralization risks
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers