Skip to content

Commit 627a27d

Browse files
committed
Update attestation rewards to latest fork
1 parent 3131a03 commit 627a27d

File tree

1 file changed

+10
-2
lines changed
  • src/content/developers/docs/consensus-mechanisms/pos/attestations

1 file changed

+10
-2
lines changed

src/content/developers/docs/consensus-mechanisms/pos/attestations/index.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,9 +50,17 @@ The attestation lifecycle is outlined in the schematic below:
5050

5151
## Rewards {#rewards}
5252

53-
Validators are rewarded for submitting attestations. The attestation reward is dependent on two variables, the `base reward` and the `inclusion delay`. The best case for the inclusion delay is to be equal to 1.
53+
Validators are rewarded for submitting attestations. The attestation reward depends on the participation flags (source, target and head), the base reward and the participation rate.
5454

55-
`attestation reward = 7/8 x base reward x (1/inclusion delay)`
55+
Each of the participation flags can be either true or false, depending on the submitted attestation and its inclusion delay.
56+
57+
The best scenario occurs when all three flags are true, in which case a validator would earn (per correct flag):
58+
59+
`
60+
reward += base reward * flag weight * flag attesting rate / 64
61+
`
62+
63+
The flag attesting rate is measured using the sum of effective balances of all attesting validators for the given flag compared the total active effective balance.
5664

5765
### Base reward {#base-reward}
5866

0 commit comments

Comments
 (0)