diff --git a/content/sccp/sccp-308.md b/content/sccp/sccp-308.md
index 411393b68..dc70350e2 100644
--- a/content/sccp/sccp-308.md
+++ b/content/sccp/sccp-308.md
@@ -22,6 +22,8 @@ This SCCP proposes to incorporate a stalenss check on the chainlink node used fo
 
 The chainlink node would have a staleness check incoporated based on the chainlink [heartbeat](https://docs.chain.link/data-feeds/price-feeds/addresses?network=ethereum&page=1&search=snx) of the respective network. The configuration would be 5,400 seconds on ethereum and 2,400 seconds on optimism.
 
+Staleness is measured by fetching the timestamp of the latest chainlink price push and comparing it to the timestamp of the current block. If it exceeds the configured maximum staleness, the oracle would revert when called, otherwise it would return the oracle price and timestamp.
+
 Note that with respect to v3 oracles, restrictions and filters on existing oracles (such as the chainlink oracle), could be performed via configuration changes, further reference can be found [here](https://github.com/Synthetixio/synthetix-v3/tree/main/protocol/oracle-manager).
 
 ## Motivation