From 03bd0d2308a312f7c583423ade5713624faf8c47 Mon Sep 17 00:00:00 2001 From: Fredrik Svantes Date: Fri, 22 Mar 2024 11:52:21 +0100 Subject: [PATCH 1/3] Update page-bug-bounty.json --- src/intl/en/page-bug-bounty.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/intl/en/page-bug-bounty.json b/src/intl/en/page-bug-bounty.json index e2a1748a752..88ee2f06d14 100644 --- a/src/intl/en/page-bug-bounty.json +++ b/src/intl/en/page-bug-bounty.json @@ -69,7 +69,7 @@ "page-upgrades-bug-bounty-type-4": "Calculation or parameter inconsistencies", "page-upgrades-bug-bounty-types": "Types of bugs", "page-upgrades-bug-bounty-validity": "In Scope", - "page-upgrades-bug-bounty-validity-desc": "Our bug bounty program spans end-to-end: from soundness of protocols (such as the blockchain consensus model, the wire and p2p protocols, proof of stake, etc.) and protocol/implementation compliance to network security and consensus integrity. Classical client security as well as security of cryptographic primitives are also part of the program. When in doubt, send an email to bounty@ethereum.org and ask us.", + "page-upgrades-bug-bounty-validity-desc": "Our bug bounty program spans end-to-end: from soundness of protocols (such as the blockchain consensus model, the wire and p2p protocols, proof of stake, etc.) and protocol/implementation compliance to network security and consensus integrity. Classical client security as well as security of cryptographic primitives are also part of the program. When in doubt, send an email to bounty@ethereum.org and ask us. You may also submit a disclosure/vulnerability directly to bounty@ethereum.org, in which case we ask that you encrypt the message using our PGP Key", "page-upgrades-bug-bounty-card-critical": "Critical", "page-upgrades-bug-bounty-card-critical-risk": "Submit critical risk bug", "page-upgrades-bug-bounty-card-h2": "Medium", From 10c6ba6ce243a61a28c29ce40567687db7dfc583 Mon Sep 17 00:00:00 2001 From: Fredrik Svantes Date: Fri, 22 Mar 2024 19:14:03 +0100 Subject: [PATCH 2/3] Update src/intl/en/page-bug-bounty.json Co-authored-by: Nico --- src/intl/en/page-bug-bounty.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/intl/en/page-bug-bounty.json b/src/intl/en/page-bug-bounty.json index 88ee2f06d14..6321585dff5 100644 --- a/src/intl/en/page-bug-bounty.json +++ b/src/intl/en/page-bug-bounty.json @@ -69,7 +69,7 @@ "page-upgrades-bug-bounty-type-4": "Calculation or parameter inconsistencies", "page-upgrades-bug-bounty-types": "Types of bugs", "page-upgrades-bug-bounty-validity": "In Scope", - "page-upgrades-bug-bounty-validity-desc": "Our bug bounty program spans end-to-end: from soundness of protocols (such as the blockchain consensus model, the wire and p2p protocols, proof of stake, etc.) and protocol/implementation compliance to network security and consensus integrity. Classical client security as well as security of cryptographic primitives are also part of the program. When in doubt, send an email to bounty@ethereum.org and ask us. You may also submit a disclosure/vulnerability directly to bounty@ethereum.org, in which case we ask that you encrypt the message using our PGP Key", + "page-upgrades-bug-bounty-validity-desc": "Our bug bounty program spans end-to-end: from soundness of protocols (such as the blockchain consensus model, the wire and p2p protocols, proof of stake, etc.) and protocol/implementation compliance to network security and consensus integrity. Classical client security as well as security of cryptographic primitives are also part of the program. When in doubt, send an email to bounty@ethereum.org and ask us. You may also submit a disclosure/vulnerability directly to , in which case we ask that you encrypt the message using our PGP Key", "page-upgrades-bug-bounty-card-critical": "Critical", "page-upgrades-bug-bounty-card-critical-risk": "Submit critical risk bug", "page-upgrades-bug-bounty-card-h2": "Medium", From 893bee62f1241edb24e1cbd990bde90f096c46b8 Mon Sep 17 00:00:00 2001 From: Nico Date: Fri, 22 Mar 2024 16:52:01 -0300 Subject: [PATCH 3/3] Update src/intl/en/page-bug-bounty.json --- src/intl/en/page-bug-bounty.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/intl/en/page-bug-bounty.json b/src/intl/en/page-bug-bounty.json index 6321585dff5..d75a469420e 100644 --- a/src/intl/en/page-bug-bounty.json +++ b/src/intl/en/page-bug-bounty.json @@ -69,7 +69,7 @@ "page-upgrades-bug-bounty-type-4": "Calculation or parameter inconsistencies", "page-upgrades-bug-bounty-types": "Types of bugs", "page-upgrades-bug-bounty-validity": "In Scope", - "page-upgrades-bug-bounty-validity-desc": "Our bug bounty program spans end-to-end: from soundness of protocols (such as the blockchain consensus model, the wire and p2p protocols, proof of stake, etc.) and protocol/implementation compliance to network security and consensus integrity. Classical client security as well as security of cryptographic primitives are also part of the program. When in doubt, send an email to bounty@ethereum.org and ask us. You may also submit a disclosure/vulnerability directly to , in which case we ask that you encrypt the message using our PGP Key", + "page-upgrades-bug-bounty-validity-desc": "Our bug bounty program spans end-to-end: from soundness of protocols (such as the blockchain consensus model, the wire and p2p protocols, proof of stake, etc.) and protocol/implementation compliance to network security and consensus integrity. Classical client security as well as security of cryptographic primitives are also part of the program. When in doubt, send an email to bounty@ethereum.org and ask us. You may also submit a disclosure/vulnerability directly to bounty@ethereum.org, in which case we ask that you encrypt the message using our PGP Key", "page-upgrades-bug-bounty-card-critical": "Critical", "page-upgrades-bug-bounty-card-critical-risk": "Submit critical risk bug", "page-upgrades-bug-bounty-card-h2": "Medium",