From 48fab3f4fb7d306db2c554b1f6f6ea1b0b4077ca Mon Sep 17 00:00:00 2001
From: brunny <96834997+brunny-eth@users.noreply.github.com>
Date: Tue, 10 Sep 2024 11:21:01 -0400
Subject: [PATCH] Update bounty.md

Updated bounty.md for consistency amongst other repos
---
 .github/ISSUE_TEMPLATE/bounty.md | 20 ++++++--------------
 1 file changed, 6 insertions(+), 14 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/bounty.md b/.github/ISSUE_TEMPLATE/bounty.md
index 61447dc1..f7e2e454 100644
--- a/.github/ISSUE_TEMPLATE/bounty.md
+++ b/.github/ISSUE_TEMPLATE/bounty.md
@@ -1,15 +1,6 @@
----
-name: Bounty
-about: Create a bounty for contributors
-title: ''
-labels: 'Bounty 💰'
-assignees: ''
-
----
-
 **Bounty description**
 
-A clear and concise description of the project; should be accessible to a contributor with minimal context
+A clear and concise description of the project; should be accessible to a contributor with minimal context.
 
 **Implementation requirements**
 
@@ -35,8 +26,9 @@ A list of potentially-useful resources. This list should be less than 5 total re
 
 **Criteria**
 
-Bounties will be rewarded based on the following criteria:
+For timely submissions of bounties that meet the implementation requirements, a bounty of at least $250 will be awarded to the contributor. Additional bounty amounts are available and will be rewarded based on the following criteria:
 
-1. Correctness and security: A thorough review of the implementation should convince our team that they are correct and secure, with all requirements met.
-2. Code clarity and quality: Succinct, easy-to-follow code with appropriate naming conventions. Utilize Rust’s type system for flexibility and security (e.g., compile-time checks where possible), and avoid external crates. Optimizations should be a lower priority than clarity, but can be included behind a feature flag as a bonus.
-3. Documentation quality: Provide comprehensive README’s, Cargo docs, and inline comments where code itself is not self-explanatory. Prioritize clarity and readability.
+1. Completion of any of the bonus features listed above and/or other bonus features that improve the quality of the submission. 
+2. Correctness and security: A thorough review of the implementation should convince our team that they are correct and secure, with all requirements met.
+3. Code clarity and quality: Succinct, easy-to-follow code with appropriate naming conventions. Utilize Rust’s type system for flexibility and security (e.g., compile-time checks where possible), and avoid external crates. Optimizations should be a lower priority than clarity, but can be included behind a feature flag as a bonus.
+4. Documentation quality: Provide comprehensive README’s, Cargo docs, and inline comments where code itself is not self-explanatory. Prioritize clarity and readability.