Dextoro is excited to announce its Security Bug Bounty Program, an initiative inviting cybersecurity enthusiasts and ethical hackers to help us fortify our systems. This program isn't just a call to arms for cyber sleuths; it's a testament to our commitment to security and our trust in the collective genius of the community. By identifying and reporting potential vulnerabilities, participants help us stay a step ahead of malicious actors.

Ready to Report a Bug?

If you've identified a potential vulnerability, don't hesitate to let us know. Submit your reporting form here and take your first step in making a significant impact in the world of blockchain security.

Program Overview

DexToro is a decentralized derivatives trading platform offering perpetual futures trading on Optimism. Traders can gain exposure to a variety of on-chain and real-world assets and access advanced functionality through the DexToro Smart Wallet.

For more information about DexToro, please visit https://dextoro.com

Proof of Concept (PoC) Requirements

A PoC, demonstrating the bug's impact, is required for this program.

Known Issue Assurance

DexToro commits to providing Known Issue Assurance to bug submissions through the program. This means that DexToro will either disclose known issues publicly or, at the very least, privately via a self-reported bug submission.

Bug reports covering previously discovered bugs are not eligible for any reward through the bug bounty program. If a bug report covers a known issue, it may be rejected together with proof of the issue being known before escalation of the bug report.

Previous Audits

A list of DexToro’s completed audit reports can be found at: https://docs.dextoro.com/resources/audits

Any unfixed vulnerability mentioned in these reports is not eligible for a reward.

Deployed Smart Contracts

A list of DexToro’s completed audit reports can be found at: https://docs.dextoro.com/resources/deployed-contracts

Feasibility Limitations

The project may be receiving 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. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and, hence, should not be used as reasons for downgrading a bug's severity.

Rewards by Threat Level

Rewards are distributed according to the impact of the vulnerability.

Reward Calculation for Critical Level Reports

Rewards for critical smart contract bug reports will be capped at 10% of funds directly affected up to a maximum of USD 50 000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 5 000 is to be rewarded in order to incentivize security researchers against withholding a bug report.

For critical web/apps bug reports will be rewarded with USD 5 000, only if the impact leads to:

• A loss of funds involving an attack that does not require any user action
• Unauthorized minting of tokens on-chain
• Private key or private key generation leakage leading to unauthorized access to user funds
• All other web/app impacts that would be classified as critical would be rewarded in a range between USD 1 000 and USD 5 000. The rest of the severity levels are paid out according to the Impact in Scope table.

Repeatable Attack Limitations

In cases of repeatable attacks on smart contracts, only the first attack is considered unless the smart contract cannot be upgraded or paused. 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 the 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 25% from the first attack, respectively.

Reward Calculation for High-Level Reports

In the event of temporary freezing, the reward increases at a multiplier of two from the full frozen value for every additional 300 blocks that the funds are temporarily frozen, up until a max cap of the high reward of USD 10 000. This is because as the duration of the freezing lengthens, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature.

Reward Payment Terms

Payouts are handled by the DexToro team directly and are denominated in USD. However, payments are done in USDT and DTORO. DexToro commits to honoring payouts according to the terms set out in this program at the time of report submission, and to treat this program as the agreement and source of truth concerning bug reports and responsible disclosures.

The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.

Program Rules and Guidelines

1. Who Can Participate Anyone with a knack for cybersecurity and a passion for blockchain technology can participate, except for Dextoro employees and their immediate family members. We welcome global perspectives but remind participants to adhere to their local laws.
2. Scope of Vulnerability Hunting Our program primarily focuses on our smart contracts, DEX interface, and APIs. However, vulnerabilities outside these areas, if critical, are also welcomed.
3. Sought-after Vulnerabilities We're particularly vigilant about smart contract flaws, API security breaches, and any exploits that could affect user funds or data privacy.
4. **Reporting Process **Found a bug? Let us know through our secure reporting form. Your report should include a detailed description, potential impact, and a step-by-step guide to reproduce the issue. Clarity and completeness are key!
5. Assessment and Response Every report is a top priority. Our team will assess each submission and respond promptly. We aim to acknowledge reports within 48 hours.
6. Rewards and Recognition Your effort deserves acknowledgment. Rewards will be tier-based, depending on the severity and impact of the bug.
7. Legal and Ethical Compliance We advocate for responsible disclosure. Researchers are expected to maintain confidentiality and avoid data exploitation. Adhering to ethical standards is non-negotiable. Public disclosure of vulnerabilities is a sensitive affair. We encourage researchers to coordinate with us to ensure a responsible disclosure process.

The Security Bug Bounty Program is about building a robust, secure ecosystem where everyone can trade with peace of mind. We're not just searching for bugs; we're seeking guardians of the blockchain realm. Join us in our quest to make Dextoro not just a platform but a fortress.

Assets in scope

Deployed Contracts | DexToro Documentation

Logo

Including the website and application

DexToro - Decentralized Derivatives Trading with Deep Liquidity

Trading, decentralized · Trade Synthetic Perpetual Futures with low fees, deep liquidity, and up to 50× more Buying Power. No sign-up or KYC is required.

https://dextoro.com/

DexToro

Gain exposure to a variety of assets with up to 50x leverage and deep liquidity

DexToro

Impacts in scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in the scope table.

Smart Contract

Websites and Applications

Out of Scope & Rules

These impacts are out of scope for this bug bounty program.

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 (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
• Impacts relying on attacks involving the de-pegging of an external stablecoin where the attacker does not directly cause the de-pegging 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

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

Websites and Apps

• Theoretical impacts without any proof or demonstration
• Impacts involving attacks requiring physical access to the victim's device
• Impacts involving attacks requiring access to the local network of the victim
• Reflected plain text injection (e.g. url parameters, path, etc.)
  • This does not exclude reflected HTML injection with or without JavaScript
  • This does not exclude persistent plain text injection
• Any impacts involving self-XSS
• Captcha bypass using OCR without impact demonstration
• CSRF with no state modifying security impact (e.g. logout CSRF)
• Impacts related to 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
• Impacts causing only the enumeration or confirmation of the existence of users or tenants
• Impacts caused by vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
• Lack of SSL/TLS best practices
• Impacts that only require DDoS
• UX and UI impacts that do not materially disrupt the use of the platform
• Impacts primarily caused by browser/plugin defects
• Leakage of nonsensitive API keys (e.g., Etherscan, Infura, Alchemy, etc.)
• Any vulnerability exploit requiring browser bugs for exploitation (e.g. CSP bypass)
• SPF/DMARC misconfigured records)
• Missing HTTP Headers without demonstrated impact
• Automated scanner reports without demonstrated impact
• UI/UX best practice recommendations
• Non-future-proof NFT rendering

Prohibited Activities:

• Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
• 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 that are executed against project assets
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty

Ready to Report a Bug?

If you've identified a potential vulnerability, don't hesitate to let us know. Submit your reporting form here and take your first step in making a significant impact in the world of blockchain security.

=======================Internal Protocol=======================

Internal Processing Protocol for Bug Bounty Reportings

This document outlines the internal protocol for processing bug bounty reportings received through our Google Forms submission system and tracking work progress using Trello. The aim is to ensure efficient, accurate, and timely handling of each submission to maintain the integrity of Dextoro's security infrastructure.

1. **Reception of Reports: **Google Forms Submission: All bug reports are submitted via a dedicated Google Form. This form captures essential information, including the reporter's details, a description of the vulnerability, steps to reproduce, and potential impact.
2. **Initial Assessment: **First Review: A designated team member (the "Intake Coordinator") reviews the submission for completeness and relevance. Preliminary Classification: The Intake Coordinator classifies the report based on perceived severity (Low, Medium, High, Critical) and creates a card in Trello.
3. **Trello: **Card Creation: For each valid report, create a new card in the Trello board under the "New Reports" list. Include a summary of the report and a link to the Google Forms response. Assigning Team Members: Assign relevant team members to the Trello card based on the nature of the vulnerability.
4. **Detailed Evaluation: **Technical Assessment: Assigned team members conduct a thorough analysis of the reported vulnerability, updating the Trello card with their findings. Severity Confirmation: Confirm or adjust the initial severity classification based on the technical assessment.
5. **Communication with Reporter: **Update Reporter: Regularly update the reporter on the status of their submission through email, especially after key milestones (e.g., after initial classification, post-technical assessment). Engage in Dialogue: If necessary, communicate with the reporter for additional information or clarification, maintaining a record of these communications on the Trello card.
6. ***Resolution and Closure: ***Resolving the Issue: Upon successful mitigation or resolution of the vulnerability, update the Trello card status to "Done." Final Communication: Inform the reporter of the resolution and discuss any disclosures or acknowledgments, if applicable. Reward Process: Initiate the reward process based on the final severity classification and the quality of the report.
7. Learning and Improvement: Discuss lessons learned or process improvements that can be derived from handling the report as a team. Regularly review and update the internal processing protocol to ensure continuous improvement.

This protocol is designed to ensure a systematic, efficient, and collaborative approach to handling bug bounty reports. By leveraging tools like Google Forms for submission and Trello for tracking, we aim to maintain the highest standards of security and responsiveness in the Bug Bounty Program.

About DexToro

DexToro’s mission is to democratize access to financial opportunity. 

Join the discussion on Discord or follow us on Twitter.

Learn more at DexToro.com