StakeSteak

StakeSteak is a suite of financial products centered around fUSD, a stable coin on Fantom, including but not limited to interest-bearing assets, liquidity pools, auto-compounding vaults, and loaning/borrowing.

xSTEAK is the current fee distribution contract for long-term StakeSteak project believers. xSTEAK holders receive 10% (reduced from 20%) of all the STEAK harvested from farms. Currently, StakeSteak are sending out fees manually, but are planning on creating off-chain automation that sends fees randomly 2-3 times a day. The randomization of fee distribution is crucial to prevent exploiters from staking the moment before fees are distributed and unstaking immediately afterwards. Eventually, xSTEAK will transition into the timelocked model of veSTEAK. The veSTEAK model will allow stakers to lock their STEAK to boost their farming rewards and vote on pool allocations. This model is forked from Curve’s veCRV.

For more information about StakeSteak, please read the StakeSteak Product Paper.

The bug bounty program covers its smart contracts and website and is focused on the prevention of loss of user funds and the denial of service.

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

All web and app bugs must come with a PoC in order to be accepted. All web and app bug reports without a PoC will be rejected with a request for a PoC.

This bug bounty program has fixed rewards in STEAK. The USD amounts reflected are only estimates. For an up-to-date price of the token, please visit the StakeSteak website.

Critical smart contract vulnerabilities are further capped at 10% of the economic damage, primarily taking into account the funds at risk, as well as some PR considerations and the exploitability of the vulnerability.

Payouts are handled by the StakeSteak team directly and are denominated in USD. Payouts are done in STEAK.

Only web/app vulnerabilities that directly affect the web/app asset listed in this table are accepted within the bug bounty program. All others are out-of-scope.

For additional reference, all smart contracts can be found here: https://github.com/xam-darnold/steak-public-contracts. However, only smart contracts listed in the table are counted as in-scope of the bug bounty program.

We are especially interested in receiving and rewarding vulnerabilities of the following types:

Smart Contracts and Blockchain

• Re-entrancy
• Logic errors
  • including user authentication errors
• Solidity/EVM details not considered
  • including integer over-/under-flow
  • including rounding errors
  • including unhandled exceptions
• Trusting trust/dependency vulnerabilities
  • including composability vulnerabilities
• Oracle failure/manipulation
• Novel governance attacks
• Economic/financial attacks
  • including flash loan attacks
• Congestion and scalability
  • including running out of gas
  • including block stuffing
  • including susceptibility to frontrunning
• Consensus failures
• Cryptography problems
  • Signature malleability
  • Susceptibility to replay attacks
  • Weak randomness
  • Weak encryption
• Susceptibility to block timestamp manipulation
• Missing access controls / unprotected internal or debugging interfaces

Websites and Apps

• Remote Code Execution
• Trusting trust/dependency vulnerabilities
• Vertical Privilege Escalation
• XML External Entities Injection
• SQL Injection
• LFI/RFI
• Horizontal Privilege Escalation
• Stored XSS
• Reflective XSS with impact
• CSRF with impact
• Direct object reference
• Internal SSRF
• Session fixation
• Insecure Deserialization
• DOM XSS
• SSL misconfigurations
• SSL/TLS issues (weak crypto, improper setup)
• URL redirect
• Clickjacking (must be accompanied with PoC)
• Misleading Unicode text (e.g. using right to left override characters)

The following vulnerabilities are excluded from the rewards for this bug bounty program:

• Attacks that the reporter has already exploited themselves, leading to damage
• Attacks requiring access to leaked keys/credentials
• Attacks requiring access to privileged addresses (governance, strategist)

Smart Contracts and Blockchain

• Incorrect data supplied by third party oracles
• Not to exclude oracle manipulation/flash loan attacks
• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Sybil attacks

Websites and Apps

• Theoretical vulnerabilities without any proof or demonstration
• Content spoofing / Text injection issues
• Self-XSS
• Captcha bypass using OCR
• CSRF with no security impact (logout CSRF, change language, etc.)
• Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
• Server-side information disclosure such as IPs, server names, and most stack traces
• Vulnerabilities used to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring unlikely user actions
• URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Attacks requiring privileged access from within the organization
• Feature requests
• Best practices

The following activities are prohibited by bug bounty program:

• Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
• Any testing with pricing oracles or third party smart contracts
• Attempting phishing or other social engineering attacks against our employees and/or customers
• Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
• Any denial of service attacks
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty