https://github.com/dodoex/contractv2

Smart contracts for DODOEX V2
https://github.com/dodoex/contractv2

blockchain ethereum-contract solidity

Last synced: 28 days ago
JSON representation

Smart contracts for DODOEX V2

• Host: GitHub
• URL: https://github.com/dodoex/contractv2
• Owner: DODOEX
• License: apache-2.0
• Created: 2020-10-22T17:17:44.000Z (over 4 years ago)
• Default Branch: main
• Last Pushed: 2024-08-13T13:58:30.000Z (9 months ago)
• Last Synced: 2025-04-02T11:07:56.638Z (about 1 month ago)
• Topics: blockchain, ethereum-contract, solidity
• Language: Solidity
• Homepage: https://app.dodoex.io/
• Size: 12.9 MB
• Stars: 165
• Watchers: 10
• Forks: 98
• Open Issues: 6
• Metadata Files:
  • Readme: README.md
  • License: LICENSE
  • Audit: audit/PeckShield-Audit-DODOV2-v1.0.pdf

Awesome Lists containing this project

README

        
# DODO V2: Help 1 Trillion People Issue Token

## Audit Report

[Audited by Peckshield](https://github.com/DODOEX/contractV2/blob/main/audit/PeckShield-Audit-DODOV2-v1.0.pdf)

## Bug Bounty 💰

### Rewards

Severity of bugs will be assessed under the [CVSS Risk Rating](https://www.first.org/cvss/calculator/3.0) scale, as follows:

 - Critical (9.0-10.0): Up to $100,000

 - High (7.0-8.9): Up to $10,000

 - Medium (4.0-6.9): Up to $5,000

 - Low (0.1-3.9): Up to $1,000

In addition to assessing severity, rewards will be considered based on the impact of the discovered vulnerability as well as the level of difficulty in discovering such vulnerability.

### Disclosure

Any vulnerability or bug discovered must be reported only to the following email: [email protected]; must not be disclosed publicly; must not be disclosed to any other person, entity or email address prior to disclosure to the [email protected] email; and must not be disclosed in any way other than to the [email protected] email. In addition, disclosure to [email protected] must be made promptly following discovery of the vulnerability. Please include as much information about the vulnerability as possible, including:

 - The conditions on which reproducing the bug is contingent.

 - The steps needed to reproduce the bug or, preferably, a proof of concept.

 - The potential implications of the vulnerability being abused.

 

A detailed report of a vulnerability increases the likelihood of a reward and may increase the reward amount.

Anyone who reports a unique, previously-unreported vulnerability that results in a change to the code or a configuration change and who keeps such vulnerability confidential until it has been resolved by our engineers will be recognized publicly for their contribution, if agreed.

## Contact Us

Send E-mail to [email protected]