Twyne-logo

Twyne

|

Twyne is a modular risk layer that leverages credit-delegation to unlock new levels of capital efficiency in lending markets. Twyne empowers lending market users with the freedom to focus on their individual goals: lenders can re-lend, borrowers can re-borrow, and together they drive the emergence of new markets, ensuring capital flows to where it is needed most.

ETH
Defi
Lending
Solidity
Maximum Bounty
$50,000
Live Since
16 January 2026
Last Updated
21 January 2026
  • PoC Required

Select the category you'd like to explore

Assets in Scope

Name
eWSTETH Intermediate Credit Vault
Added on
21 January 2026
Name
aWSTETH Intermediate Credit Vault
Added on
21 January 2026
Name
eWETH Intermediate Credit Vault
Added on
16 January 2026
Name
Intermediate Vault Factory
Added on
16 January 2026
Name
Leverage Operator
Added on
16 January 2026
Name
Oracle Router
Added on
16 January 2026
Name
Vault Manager
Added on
16 January 2026
Name
Collateral Vault Factory
Added on
16 January 2026

Impacts in Scope

Impacts Body

All vaults deployed using CollateralVaultFactory are considered in scope

Severity
Critical
Title

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

Severity
Critical
Title

Permanent freezing of funds

Severity
Critical
Title

Protocol insolvency

Severity
High
Title

Temporary freezing of funds (for at least 24 hours)

Severity
High
Title

Theft of unclaimed yield

Severity
High
Title

Permanent freezing of unclaimed yield

Out of scope

Default Out of Scope and rules

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