This test encompasses two parts, one is user test incentives, and the other is validator test incentives. Only validators need to test Onboard and Offboard operations, and users don’t. Moreover, validators also need to run Seiya testnet nodes first.
Testing time starts: 21:00 on December 3, 2020 (UTC+8)
Testing time ends: 21:00 on December 17, 2020 (UTC+8)
Starting block height: 751876
End block height: 953476
3. User testing tasks & incentives
LiquidityBond: Exchange FIS for rFIS
Transfer: rFIS transfer
LiquidityUnbond: Redeem FIS through rFIS, and execute
liquidityWithdrawUnbond operation after 56 Eras.
Liquidity_withdraw_unbond: Withdraw the redeemed FIS, please confirm whether the exchange rate calculation is correct after withdrawal.
3) When withdrawing the redeemed FIS, it is necessary to calculate whether the amount of FIS obtained is correct by the current exchange rate. Please note that a 10% handling fee will be deducted from the reward.
During the test period, the first 100 participants who complete all of the above tasks will receive 10 FIS (FIS of mainnet) award. Please carefully memorize the account and key, for the incentive will be sent to this account.
When all tasks are completed, please forward the relevant tweet from StaFi’s Twitter account (link) and attach the screenshot of the successful operation of LiquidityBond and LiquidityWithdrawUnbond operations). Moreover, please @ three of your friends and the FIS address to receive the reward.
The first 40 validators who complete all the above tasks during the test period will receive 50 FIS (FIS of mainnet) as reward. Please be sure to memorize the account and keys, for the test incentive will be sent to this account.
Before the test, you need to join the StaFi validator test group: https://t.me/stafi_testnet. When you complete all tasks, please send the screenshot of the LiquidityBond and LiquidityWithdrawUnbond operations and the FIS address used to receive the reward.
For all malfunctions or bugs discovered during the test, please feel free to report to us through the same channel of bug submission(see below).
Critical: Abnormal function, ineffective function, or security breach, etc.;
Moderate: Defects that do not affect the function, non-security issues, such as the room for optimization, performance improvement, etc.;
Low: Unimportant issues, some minor issues that can be modified during updates, such as modifying text or notes.
Outside the scope of the bounty program
Repeated reports on security issues, including security issues that have been confirmed by the StaFi team;
Theoretical security issues without pragmatic application scenarios, or issues that require complex user-interactions.
1 It must be a newly discovered bug(s) that has/have not been reported before
2 The bug(s) found must be related to security issues in StaFi GitHub page code, but not other third-party code;
3 Have not written any codes of StaFi around the bug(s), and have not participated in any process that generated the bug(s) of StaFi in other ways;
4 Public disclosure will make you lose your bounty;
5 The StaFi team reserves the right to make the final decision on eligibility for the event and all rewards.
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:
The accuracy and details of the bug description;
The quality of reproducibility, such as test code, scripts, and detailed instructions.
When you find bug(s), please send a report to: [email protected]. 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.
1. What should I do if I submit a bug but do not hear a reply?
Before publicly publishing the bug(s) you found, we need some time to review and confirm them, and will reply to you as soon as possible. If you haven’t received a reply two weeks after submission, you can send an email to us at: [email protected]