docs: add release note for network separation safeguard
What the developer wrote
Authored by ziggie
docs: add release note for network separation safeguard
This is in particular important when running with a postgres
backend.
This only works if you run LND with the native sql flag but
people should run it with this flag from 21 on anyways.
What changed, and why it matters
This commit is just a documentation update adding a release note for a safeguard that was already merged via a previous code change (PR #10684). The safeguard prevents LND from accidentally starting up with the wrong Bitcoin network while reusing the same database, which could silently corrupt data. The actual protective code is not in this commit; only the description of it is.
No immediate action is required for this documentation commit. Operators using native SQL backends should ensure they run LND 0.21+ with --db.use-native-sql so the chain_params network safeguard is active. Review the referenced PR #10684 separately if auditing the actual implementation.
Security signals we found
Safeguard against cross-network database reuse
Silent data corruption prevention
Native SQL backend (PostgreSQL/SQLite) scope
Requires --db.use-native-sql flag
Release-note only; no functional code change in this commit
Evidence from the diff
The diff adds a release note entry describing PR #10684, which introduces a network-separation safeguard for native SQL database backends (PostgreSQL and SQLite). On first startup, the active network is written to a new chain_params table; on later restarts, LND compares the stored value against the configured network and aborts if they differ. The commit itself changes only docs/release-notes/release-notes-0.21.0.md and contains no code modifications.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +9 / −1
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index 62982e3..608aada 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -307,7 +307,15 @@
## Database
-* Freeze the [graph SQL migration
+* [Prevent silent data corruption](https://github.com/lightningnetwork/lnd/pull/10684)
+ when reusing the same database across different Bitcoin networks. On first
+ startup the active network is persisted in a new `chain_params` table; on
+ every subsequent restart lnd compares the stored value against the configured
+ network and refuses to start if they differ, printing a clear error message
+ with remediation steps. This safeguard applies to both the PostgreSQL and
+ SQLite native-SQL backends when running with `--db.use-native-sql`.
+
+* Freeze the [graph SQL migration
code](https://github.com/lightningnetwork/lnd/pull/10338) to prevent the
need for maintenance as the sqlc code evolves.
* Prepare the graph DB for handling gossip V2
Why this scored 58/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.