YOLOrekt

YOLOrekt is a decentralized short-term prediction market platform built on blockchain. It includes key attributes such as being the most Intuitive, hyper-gamified setup and having Social-Fi elements.

The platform’s core enabling technology provides the ability to settle markets within seconds on the blockchain. As our first offering, users will be able to predict whether the final price of an asset will end up above or below a strike price by placing bids on the outcome.

These are ‘Bid Up’ OR ‘Bid Down’ games, allowing the trader to get a result in just a matter of a few candles. Access to both sides of the market is transparent and straightforward with an intuitive user interface to bid in any available market, making options trading as easy as it can get.

For more information about YOLOrekt, please visit https://www.yolorekt.finance/.

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

All web/app bug reports and all Critical/High severity smart contract bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.

In addition, all bug reports must come with a suggestion for a fix in order to be considered for a reward.

Previously known issues highlighted in the following audit report are considered out of scope:

• http://audit-report.yolorekt.finance.s3.us-east-1.amazonaws.com/YoloRekt+Smart+Contract+Final+Audit+Report_072022.pdf

Payouts are handled by the YOLOrekt team directly and are denominated in USD. However, payouts are done in USDC or USDT, at the discretion of the team.

Smart Contract

All smart contracts of YOLOrekt can be found at https://github.com/YOLOrekt/community-bug-bounty. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

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
• Centralization risks

Websites and Apps

• Theoretical vulnerabilities without any proof or demonstration
• Attacks requiring physical access to the victim device
• Attacks requiring access to the local network of the victim
• Reflected plain text injection ex: url parameters, path, etc.
  • This does not exclude reflected HTML injection with or without javascript
  • This does not exclude persistent plain text injection
• Self-XSS
• Captcha bypass using OCR without impact demonstration
• CSRF with no state modifying security impact (ex: logout CSRF)
• Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
• Server-side non-confidential information disclosure such as IPs, server names, and most stack traces
• Vulnerabilities used only to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Feature requests
• Issues related to the frontend without concrete impact and PoC
• Best practices issues without concrete impact and PoC
• Vulnerabilities primarily caused by browser/plugin defects
• Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
• Any vulnerability exploit requiring browser bugs for exploitation. ex: CSP bypass

The following activities are prohibited by this 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