Skip to content

Commit eefba73

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 c54a4b3 commit eefba73

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
@@ -307,7 +307,15 @@
307307

308308
## Database
309309

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

0 commit comments

Comments
 (0)