ECDSA staker rewards: 2021-09-03 -> 2021-09-10

[lukasz-zimnoch]

Overview

Here we publish the distribution of ECDSA staker rewards for interval 2021-09-03 - 2021-09-10.

To see rewards for your operator, please go to the summary file.

On Monday, 2021-09-13 rewards will be allocated to ECDSARewardsDistributor contract (0x5b9E48F8818962699fe38F5989b130ceE691bBb3) and available to be claimed from KEEP Token Dashboard.

Files updated:

• 2021-09-03_2021-09-10.log.txt - contains the full log from the execution of the script generating the allocation.
• 2021-09-03_2021-09-10.summary.txt - contains the summary generated by the same script in human-friendly form.
• cache-keeps.json - it is the cache of on-chain keep information updated weekly during rewards script execution.
• cache-transactions.json - it is the cache of on-chain sortition pool information TX updated weekly during rewards script execution.
• output-merkle-objects.json - Merkle tree used to allocate rewards on-chain.

Everyone can verify the allocation by running the script themselves.

Rewards Explained

Input

• Interval T starts at T_start.
• Interval T ends at T_end.
• All operators who have ever deposited ETH into the bonding contract are taken into account.

Operator Parameters

For each Operator:

• Calculate the amount of KEEP staked at T_end as KEEP_staked.
• Calculate the total amount of ETH bonded at T_start as ETH_bonded.
• Read the amount of ETH unbonded at T_start as ETH_unbonded.
• Calculate the sum of ETH unbonded and withdrawn for the entire interval as ETH_withdrawn.
• Calculate the total ETH under management as ETH_locked = ETH_bonded + ETH_unbonded - ETH_withdrawn.

Requirements

Operator not meeting all requirements listed in this section is not getting any rewards for interval T. Rewards proportional to the operator's reward weight are deallocated and remains in the pool for future intervals.

• If the operator does not have BondedECDSAKeepFactory contract or tBTC sortition pool authorized at T_start, they are not getting any rewards for interval T.

• If the operator does not have a minimum KEEP stake at T_start, they are not getting any rewards for interval T.

• If the operator has more ETH_unbonded than the minimum unbonded value and is not in the sortition pool at T_start, they are not getting any rewards for interval T. In other words, if the operator is eligible to be in the sortition pool, they have to be registered in the sortition pool. Operators who are not registered in the sortition pool because all of their ETH is bonded are still getting rewards because that ETH is still under the system’s management.

• If the operator deauthorized tBTC sortition pool between T_start and T_end, they are not getting any rewards for interval T.

• If the operator ever committed a fraud, they are not getting any rewards for interval T.

• If the operator did not meet the signature SLA between T_start and T_end,they are not getting any rewards for interval T. For less than 20 closed/terminated keeps, no more than one could be terminated with a signature timeout. For 20 or more closed/terminated keeps no more than 5% could be terminated with a signature timeout. Signature SLA does not include not answered courtesy calls.

• If the operator did not meet the key generation SLA between T_start and T_end, they are not getting any rewards for interval T . For less than 10 key generations, one of them can fail. For 10 or more key generations, no more than 10% can fail.

The Formula

Next interval

The next interval ends Friday, 2021-09-17 00:00 GMT.