From a86f1f4251b890154721743c1ebf7e8be08bb77e Mon Sep 17 00:00:00 2001 From: Ramana Kumar Date: Tue, 9 Apr 2024 11:47:29 +0100 Subject: [PATCH 1/2] Update fee-distrib-sp.md The section on the penalty system was inaccurate. These changes ensure that the guides describe the current state of the protocol more correctly. --- docs/guides/node/fee-distrib-sp.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/docs/guides/node/fee-distrib-sp.md b/docs/guides/node/fee-distrib-sp.md index d79c5293..e001eb63 100644 --- a/docs/guides/node/fee-distrib-sp.md +++ b/docs/guides/node/fee-distrib-sp.md @@ -102,22 +102,24 @@ Please keep these conditions in mind when deciding whether or not to use the Smo ### The Penalty System -To ensure that node operators don't "cheat" by manually modifying the fee recipient used in their Validator Client, Rocket Pool employs a penalty system. +To ensure that node operators don't "cheat" by manually modifying the fee recipient used in their Validator Client, Rocket Pool has considered employing a penalty system. -The Oracle DAO constantly monitors each block produced by Rocket Pool node operators. -Any block that has a fee recipient other than one of the following addresses is considered to be **invalid**: +In this system, the Oracle DAO would constantly monitor each block produced by Rocket Pool node operators. +Any block that has a fee recipient other than one of the following addresses would be considered **invalid**: - The rETH address - The Smoothing Pool address - The node's fee distributor contract (if opted out of the Smoothing Pool) -A minipool that proposed a block with an **invalid** fee recipient will be issued **a strike**. -On the third strike, the minipool will begin receiving **infractions** - each infraction will dock **10% of its total Beacon Chain balance, including ETH earnings** and send them to the rETH pool stakers upon withdrawing funds from the minipool. +A minipool that proposed a block with an **invalid** fee recipient would be issued **a strike**. +On the third strike, the minipool would begin receiving **infractions** - each infraction would dock **10% of its total Beacon Chain balance, including ETH earnings** and send them to the rETH pool stakers upon withdrawing funds from the minipool. Infractions are at a **minipool** level, not a **node** level. -The Smartnode software is designed to ensure honest users will never get penalized, even if it must take the Validator Client offline to do so. -If this happens, you will stop attesting and will see error messages in your log files about why the Smartnode can't correctly set your fee recipient. +The Smartnode software is designed to ensure honest users would never get penalized under the hypothetical penalty system, even if it must take the Validator Client offline to do so. +If this were to happen, you would stop attesting and see error messages in your log files about why the Smartnode can't correctly set your fee recipient. + +Currently the penalty system does not exist and there are no plans to implement it. Therefore, a node operator is welcome to set their fee recipient to address other than the three listed above to claim all execution layer rewards for the address of their choice (including those that would normally be designated for rETH holders). Be aware, however, that the Smartnode software does not make such a setting of the fee recipient easy to accomplish. ## The Smoothing Pool From 5e54fff44546f90d3faf28ffa91164d3537cf3da Mon Sep 17 00:00:00 2001 From: Ramana Kumar Date: Tue, 9 Apr 2024 12:01:33 +0100 Subject: [PATCH 2/2] Update fee-distrib-sp.md Fix missing word --- docs/guides/node/fee-distrib-sp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/node/fee-distrib-sp.md b/docs/guides/node/fee-distrib-sp.md index e001eb63..a2a1a294 100644 --- a/docs/guides/node/fee-distrib-sp.md +++ b/docs/guides/node/fee-distrib-sp.md @@ -119,7 +119,7 @@ Infractions are at a **minipool** level, not a **node** level. The Smartnode software is designed to ensure honest users would never get penalized under the hypothetical penalty system, even if it must take the Validator Client offline to do so. If this were to happen, you would stop attesting and see error messages in your log files about why the Smartnode can't correctly set your fee recipient. -Currently the penalty system does not exist and there are no plans to implement it. Therefore, a node operator is welcome to set their fee recipient to address other than the three listed above to claim all execution layer rewards for the address of their choice (including those that would normally be designated for rETH holders). Be aware, however, that the Smartnode software does not make such a setting of the fee recipient easy to accomplish. +Currently the penalty system does not exist and there are no plans to implement it. Therefore, a node operator is welcome to set their fee recipient to an address other than the three listed above to claim all execution layer rewards for the address of their choice (including those that would normally be designated for rETH holders). Be aware, however, that the Smartnode software does not make such a setting of the fee recipient easy to accomplish. ## The Smoothing Pool