Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>>and those LN could be responsible for an inordinant amount of volume

Theoretically yes, in practice no.

Routing complexity increases as usage increases without a commensurate increase in channel collateral, because increased usage leads to more channels using up the collateral for one direction of transmissions, which eliminates the transmissibility of one of the two routes in the channel. The network would thus naturally see rising collateral - either in existing channels or in new ones - to maintain routing efficiency, as usage increases.

Beyond that, more individuals joining the LN would naturally lead to more collateral being added to it, as individuals create new channels with new stashes of respective collateral.

For these reasons, low collateral reliably maps to low usage.



>Theoretically yes, in practice no.

...?

1.) I have a direct disincentive to include more collateral than would be absolutely required.

2.) Most of the time LN's only need to go one way.

3.) The only thing your original graph shows is that the price of bitcoin has fallen.

4.) I anecedotely know there has been more use in LN among all my crypto friends and in South/ central America where i have seen increased use in Cafe's and hotels.

5.) The total amount of BTC being used as collateral in LN has grown. (Even though this means absolutely nothing and your graph of 'TVL' Also means nothing when compared is USD).

6.) It's annoying to see someone spitting FUD on BTC/ LN with ETH in their name.


1. My point is about how much collateral is required for a given amount of usage.

2. LN transactions going one way makes the collateral situation worse, by preventing collateral from being replenished by counter-flow transactions.

3. It shows how little value is locked in LN channels relative to value of BTC outstanding.

The rest of your points are either not relevant or have already been addressed.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: