From b076168bf8df3d3afcb102fa7dfa57678363f1c5 Mon Sep 17 00:00:00 2001
From: tersec <tersec@users.noreply.github.com>
Date: Tue, 30 May 2023 08:17:18 +0000
Subject: [PATCH] State explicitly slashingdb import doesn't destroy existing
 information (#4998)

---
 docs/the_nimbus_book/src/migration.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/the_nimbus_book/src/migration.md b/docs/the_nimbus_book/src/migration.md
index 60c4a6438..c20b563f9 100644
--- a/docs/the_nimbus_book/src/migration.md
+++ b/docs/the_nimbus_book/src/migration.md
@@ -187,6 +187,9 @@ build/nimbus_beacon_node slashingdb import path/to/export_dir/slashing-protectio
 
 Replacing `/path/to/export_dir` with the file/directory you specified when you exported your slashing protection history.
 
+!!! tip
+    Additional slashing protection information can be safely added to slashing protection databases.
+
 ### 5. Start the Nimbus validator
 
 Follow the instructions [here](./connect-eth2.md) to start your validator using our pre-built [binaries](./binaries.md).