lightninglabs
diff --git a/‎.gitbook/assets/Screenshot from 2023-11-20 13-18-24.png
106 KB b/‎.gitbook/assets/Screenshot from 2023-11-20 13-18-24.png
106 KB
diff --git a/‎lightning-network-tools/lightning-terminal/liquidity-report.md
+1-1 b/‎lightning-network-tools/lightning-terminal/liquidity-report.md
+1-1
@@ -22,7 +22,7 @@ The “Routable Inbound” graph places your channels into various fee buckets,
 
 
 
-<figure><img src="../../.gitbook/assets/Screenshot from 2023-11-17 21-28-57.png" alt=""><figcaption><p>Sample liquidity report</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/Screenshot from 2023-11-20 13-18-24.png" alt=""><figcaption><p>Sample liquidity report</p></figcaption></figure>
 
 Don’t rely on other participants of the Lightning Network to remotely detect your liquidity needs. Monitor your node’s inbound capacity and fees and actively manage your node’s liquidity. Attempt to free up additional capacity first, for instance through [Lightning Loop](../loop/), and only close channels that can’t be empty otherwise. Maximize your percentage of channels that have inbound capacity, rather than maximize the number of your channels. Keep channels open and allow their cost to be amortized over multiple cycles, rather than closing them after their liquidity has been depleted.
Original file line number	Diff line number	Diff line change
`@@ -22,7 +22,7 @@ The “Routable Inbound” graph places your channels into various fee buckets,`
`22`	`22`
`23`	`23`
`24`	`24`
`25`		`-<figure><img src="../../.gitbook/assets/Screenshot from 2023-11-17 21-28-57.png" alt=""><figcaption><p>Sample liquidity report</p></figcaption></figure>`
	`25`	`+<figure><img src="../../.gitbook/assets/Screenshot from 2023-11-20 13-18-24.png" alt=""><figcaption><p>Sample liquidity report</p></figcaption></figure>`
`26`	`26`
`27`	`27`	Don’t rely on other participants of the Lightning Network to remotely detect your liquidity needs. Monitor your node’s inbound capacity and fees and actively manage your node’s liquidity. Attempt to free up additional capacity first, for instance through [Lightning Loop](../loop/), and only close channels that can’t be empty otherwise. Maximize your percentage of channels that have inbound capacity, rather than maximize the number of your channels. Keep channels open and allow their cost to be amortized over multiple cycles, rather than closing them after their liquidity has been depleted.
`28`	`28`