CGCX is opening registrations for traders, programmers, and UI designers to join our Closed-Beta Testing Bounty Program. Users intending to take part in this program would have to register their interests or intentions through this form.

Successful applicants will receive an email invitation from contact@cgcx.io with access to the Closed-Beta System.

Testing should be done from the UI and functional perspective. To optimise the availability of our services for our users, testers are not allowed to carry out DoS attacks, leverage black hat SEO techniques, spam people or do other similarly questionable or illegal activities. Testers are strongly discouraged to use any vulnerability testing tools that automatically generate significant volumes of traffic.

To qualify for bounty, the security bug must be original and previously unreported.

Non-­qualifying Vulnerabilities: Depending on their impact, some of the reported issues may not qualify. Although we review them on a case ­by ­case basis.

Please note you will qualify for a reward only if you were the first person to alert us to a previously unknown flaw. We will update you on the progress of your report­ when it is accepted, validated, fixed and when the bounty is rewarded.

This is not a competition, but rather an experimental and discretionary rewards program. You should understand that we can cancel the program at any time and the decision as to whether or not to pay a reward has to be entirely at our discretion. Of course, your testing must not violate any law, or disrupt or compromise any data that is not your own.

Identified issues will be rewarded with 4 different tiers of rewards.

Critical : 5000USD worth of CGCX Tokens
High : 2500USD worth of CGCX Tokens
Medium : 1000USD worth of CGCX Tokens
Low: 250USD worth of CGCX Tokens

Low:
Button actions not working,  css or styles not loading in page, error messages are not properly conveyed.

Medium:
Flow affecting user journey, presence of an item that confuse users, unauthenticated page access.

High:
Previously known vulnerable libraries, comma separated value injection, Missing best practices in SSL / TLS configuration, Wallet generation issue, trading issues.

Critical:
Any activity that could lead to the disruption of our service (DoS), Content spoofing and text injection issues.