Code Review (Staking / Slashing)
In the WalletD ecosystem, code reviews are integral to maintaining code quality and security. To incentivize thorough reviews and accountability, we incorporate a staking and slashing mechanism.
Staking for Code Reviews
Initiating a Review: When you're ready to have your code reviewed, you'll need to stake a certain amount of WD Tokens. This serves as a commitment to the quality and seriousness of your contribution.
Performing a Review: Reviewers also stake WD Tokens to participate. This ensures that reviewers are incentivized to provide thorough and constructive feedback.
Slashing Conditions
Bugs and Vulnerabilities: If critical bugs or security vulnerabilities are discovered after merging a pull request, a portion of the staked tokens by the contributor and the reviewers may be slashed.
Non-Adherence to Standards: Slashing can occur if the contribution significantly deviates from established coding standards or fails to adhere to the project’s best practices.
Avoiding Slashing
Thorough Testing: Ensure your code is well-tested before submission.
Adherence to Guidelines: Follow all coding and contribution guidelines detailed in the WalletD documentation.
Engagement: Respond constructively to review comments and engage with the WalletD community.
Last updated