As lightning community channels route funds, channel updates require the two channel friends (Alice & Bob) to do a spherical of signing and commerce dedication transactions for essentially the most up-to-date channel stability.
Is that this the first motive that the channel.db file could develop so dramatically?
For every replace, Alice should maintain a full file of all revocation keys from all previous dedication transactions in case Bob broadcasts an invalid previous channel state. If these keys are deleted, Alice might be weak to Bob stealing cash and Alice wouldn’t be capable of create & broadcast the proper penalty transaction to punish Bob.
Database compaction is often run on startup of the node, however what precisely is concerned in that compaction? Are the revocation keys being listed / compressed in some lossless/recoverable trend?
Do different implementations than LND have the identical course of?