From 593c8e2ef2c8694ed42535523b55d13c64822027 Mon Sep 17 00:00:00 2001
From: Jeremy Frank <jeremy@autonomys.xyz>
Date: Fri, 18 Jul 2025 13:49:46 -0600
Subject: [PATCH 1/2] docs: add detailed steps for verifying PoT against parent
 block parameters.

---
 docs/consensus/proof_of_time.md | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/docs/consensus/proof_of_time.md b/docs/consensus/proof_of_time.md
index e1f083d..2299030 100644
--- a/docs/consensus/proof_of_time.md
+++ b/docs/consensus/proof_of_time.md
@@ -7,8 +7,8 @@ keywords:
     - timekeeper
     - randomness
 last_update:
-  date: 04/17/2025
-  author: Teor
+  date: 07/18/2025
+  author: Jeremy Frank
 ---
 import Collapsible from '@site/src/components/Collapsible/Collapsible';
 
@@ -309,7 +309,12 @@ Generate a random number `n` in the range `0..=(diff)` and if `n<sample_size` re
 
 (Extends [Verification](proof_of_archival_storage.md#verification))
 
-When a new block is received, in addition to PoS and consensus log checks, compare the PoT values in the header to the local view of the PoT chain.
-If the proof-of-time included in the block header covers local proofs that have already been verified, the block’s PoT passes validation.
+When a new block is received, in addition to PoS and consensus log checks, validate the PoT relative to the parent block:
+
+1. Retrieve the parent block's PoT parameters and derive the expected PoT input for the current slot.
+2. Verify that the current block's proof-of-time output is valid according to the parent-derived input and parameters.
+3. Compare the PoT values in the header to the local view of the PoT chain.
+
+If the proof-of-time included in the block header covers local proofs that have already been verified, the block's PoT passes validation.
 
 If the proof-of-time is not consistent with local view or the local view is missing some required slots — do necessary verification, including proving.

From 177da87ad6aebf719dca33ed801ee332a616eb75 Mon Sep 17 00:00:00 2001
From: Jeremy Frank <jeremy@autonomys.xyz>
Date: Tue, 22 Jul 2025 14:27:08 -0600
Subject: [PATCH 2/2] docs: clarify proof-of-time validation steps and note
 caching behavior

---
 docs/consensus/proof_of_time.md | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/docs/consensus/proof_of_time.md b/docs/consensus/proof_of_time.md
index 2299030..78f6cb7 100644
--- a/docs/consensus/proof_of_time.md
+++ b/docs/consensus/proof_of_time.md
@@ -7,7 +7,7 @@ keywords:
     - timekeeper
     - randomness
 last_update:
-  date: 07/18/2025
+  date: 07/22/2025
   author: Jeremy Frank
 ---
 import Collapsible from '@site/src/components/Collapsible/Collapsible';
@@ -313,8 +313,6 @@ When a new block is received, in addition to PoS and consensus log checks, valid
 
 1. Retrieve the parent block's PoT parameters and derive the expected PoT input for the current slot.
 2. Verify that the current block's proof-of-time output is valid according to the parent-derived input and parameters.
-3. Compare the PoT values in the header to the local view of the PoT chain.
+3. If the proof-of-time verification passes, the block's PoT is considered valid.
 
-If the proof-of-time included in the block header covers local proofs that have already been verified, the block's PoT passes validation.
-
-If the proof-of-time is not consistent with local view or the local view is missing some required slots — do necessary verification, including proving.
+Some proofs may be cached locally from previous gossip or evaluation, allowing nodes to skip redundant verification for already-validated PoT values.