Merge pull request #228 from ethereum/acolytec3-patch-2

Clarify slot to be used in `OptimisticUpdate` content key
ethereum · Sep 26, 2023 · 1614bd7 · 1614bd7
2 parents 0dceb29 + 3792cd8
commit 1614bd7
Showing 1 changed file with 6 additions and 6 deletions.
diff --git a/beacon-chain/beacon-network.md b/beacon-chain/beacon-network.md
@@ -204,12 +204,12 @@ content_key                          = selector + SSZ.serialize(light_client_opt
 ```
 
 > The `LightClientOptimisticUpdate` objects are ephemeral and only the latest is
-of use to the node. The content key requires the `optimistic_slot` to be
-provided so that this object can be more efficiently gossiped. Nodes should
-decide to reject an `LightClientOptimisticUpdate` in case it is not newer than
-the one they already have.
-For `FindContent` requests, a node should know the current slot as it is time
-based.
+of use to the node. The content key requires the `optimistic_slot` (corresponding to
+the `signature_slot` in the the update) to be provided so that this
+object can be more efficiently gossiped. Nodes should decide to reject an
+`LightClientOptimisticUpdate` in case it is not newer than the one they already have.
+For `FindContent` requests, a node should compute the current slot based on its local clock
+and then use that slot as a starting point for retrieving the most recent update.
 
 #### HistoricalSummaries