StaFi announces the rETH Open Beta. Team welcome any Staker or Validator participating in the testing of the rETH product, and for that, they have prepared incentives as well as considerable bounty rewards for any Staker and Validator who finds bugs and vulnerabilities.
After pulling many all-nighters, the StaFi team has finally developed rETH, a solution to the liquidity of ETH2.0 staking, with the help of community contributors. Once accessible, Stakers will be able to Stake freely in the ETH2.0 ecosystem. More importantly, the minimum Staking amount will be lowered to 0.01 ETH instead of the 32 ETH required by ETH. The rETH a user obtains after Staking can circulate, and he or she can virtually enjoy the real decentralized Liquidity Staking.
On the other hand, any validator can deposit 8ETH in the StaFi rETH contract in order to run a node in the ETH 1.0 Deposit contract. This is because a validator’s deposit will be combined with another 24ETH from StaFi users’ funds. The above validator will virtually become an Original Validator of rETH, enjoying staking rewards that are much higher than that of self-operating nodes.
For a detailed introduction to the rETH solution, please check: https://medium.com/stafi/official-release-of-stafi-staking-liquidity-solution-for-ethereum-2-0-8f1557763cfd
The contract of rETH contract will be formally submitted to a third-party auditing agency this week. At the same time, the Open Beta of Bug Bounty will be accessible by the StaFi community. Submission of any Bug you find during the experience will be eligible to win up to $25,000 as reward. When all tests and the audit phase are over, team will officially release rETH.
When you complete the task：
Before starting the task, you need to join the StaFi validator test group: https://t.me/stafi_reth.
When the test is completed:
For any bug, vulnerability, or details that might need optimization, you are welcome to report through the same channel as that of bug submission.
Outside the scope of the bounty program
The bounty will be issued in the form of FIS, and the amount will depend on the severity of the bugs found.
In addition to severity, the bounty amount will be determined (but not limited to) by other factors including:
When you find bug(s), please send a report to: email@example.com. Please attach your name, email, company name (optional), description of the bug(s), your opinion on what is the potential impact of that bug on StaFi rBridge, and how you discovered that bug.