Skip to content

Commit 02ec43f

Browse files
committed
docs: add release not 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.
1 parent 0648c83 commit 02ec43f

1 file changed

Lines changed: 9 additions & 1 deletion

File tree

docs/release-notes/release-notes-0.21.0.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -282,7 +282,15 @@
282282

283283
## Database
284284

285-
* Freeze the [graph SQL migration
285+
* [Prevent silent data corruption](https://github.com/lightningnetwork/lnd/pull/10684)
286+
when reusing the same database across different Bitcoin networks. On first
287+
startup the active network is persisted in a new `chain_params` table; on
288+
every subsequent restart lnd compares the stored value against the configured
289+
network and refuses to start if they differ, printing a clear error message
290+
with remediation steps. This safeguard applies to both the PostgreSQL and
291+
SQLite native-SQL backends when running with `--db.use-native-sql`.
292+
293+
* Freeze the [graph SQL migration
286294
code](https://github.com/lightningnetwork/lnd/pull/10338) to prevent the
287295
need for maintenance as the sqlc code evolves.
288296
* Prepare the graph DB for handling gossip V2

0 commit comments

Comments
 (0)