From e3bba09bf3db96593b83ef2f205a819874fdc287 Mon Sep 17 00:00:00 2001
From: Matt Witherspoon <32485495+spoonincode@users.noreply.github.com>
Date: Mon, 19 Aug 2024 22:58:24 -0400
Subject: [PATCH] call out log compatiblity explicitly

---
 .../100_migration-guides/04_upgrade-guide-spring-1-0.md        | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/native/07_node-operation/100_migration-guides/04_upgrade-guide-spring-1-0.md b/native/07_node-operation/100_migration-guides/04_upgrade-guide-spring-1-0.md
index e59d718..1c472db 100644
--- a/native/07_node-operation/100_migration-guides/04_upgrade-guide-spring-1-0.md
+++ b/native/07_node-operation/100_migration-guides/04_upgrade-guide-spring-1-0.md
@@ -18,6 +18,9 @@ This upgrade guide covers the steps for upgrading a node to Spring v1 from prior
 
 ## Upgrade Steps
 
+### Log File Compatibility
+The block log, state history logs, and trace logs from prior versions all remain compatible with Spring v1. There is no need to remove these files when performing the upgrade procedure documented below.
+
 ### Upgrade Steps for All Nodes
 To quickly transition from Leap to Spring v1, nodeos must be restarted from a snapshot due to structural changes to the state memory storage. Snapshots from earlier versions of nodeos (including Leap v3 through v5) may be used to start a Spring node.