Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit bfc2a71

Browse files
committed
updated bounty amt
1 parent 7ace168 commit bfc2a71

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/hackers/retesting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,4 +46,4 @@ To participate in the retest:
4646

4747
![retesting-5](./images/retesting_update_4.png)
4848

49-
Upon completion, you'll be awarded with a $100 bounty.
49+
Upon completion, you'll be awarded with a $50 bounty.

docs/programs/retesting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ path: "/programs/retesting.html"
44
id: "programs/retesting"
55
---
66

7-
As programs receive vulnerability reports and work on deploying fixes, they need proof that their vulnerabilities have actually been fixed. Asking hackers to verify whether a vulnerability has been fixed is a good way to secure the protection of your asset’s data. You can elect to invite hackers to retest your vulnerabilities to verify fixes. Each hacker that participates in the retest will receive a $100 bounty upon completion.
7+
As programs receive vulnerability reports and work on deploying fixes, they need proof that their vulnerabilities have actually been fixed. Asking hackers to verify whether a vulnerability has been fixed is a good way to secure the protection of your asset’s data. You can elect to invite hackers to retest your vulnerabilities to verify fixes. Each hacker that participates in the retest will receive a $50 bounty upon completion.
88

99
### How It Works
1010
To have hackers retest a vulnerability:

0 commit comments

Comments
 (0)