The static address deposit manager keeps a deposits map[wire.OutPoint]*Deposit that appears to retain every deposit seen by the daemon.
Finalized deposits are removed from activeDeposits, but the broader deposits map is not pruned. On startup, the map is repopulated from Store.AllDeposits, including historical/final deposit rows.
For a reusable static address, this means a long-running or high-volume node could accumulate an unbounded in-memory deposit cache over time. This is especially relevant if the address receives many small deposits, dust, or spam.
This issue is a reminder to evaluate and address the memory-growth concern.
The static address deposit manager keeps a
deposits map[wire.OutPoint]*Depositthat appears to retain every deposit seen by the daemon.Finalized deposits are removed from
activeDeposits, but the broaderdepositsmap is not pruned. On startup, the map is repopulated fromStore.AllDeposits, including historical/final deposit rows.For a reusable static address, this means a long-running or high-volume node could accumulate an unbounded in-memory deposit cache over time. This is especially relevant if the address receives many small deposits, dust, or spam.
This issue is a reminder to evaluate and address the memory-growth concern.