The Lightning Network FAQ - page 55.

d5000

legendary

Activity: 3906

Merit: 6249

Decentralization Maximalist

Quote from: Wind_FURY on October 19, 2020, 06:47:57 AM

Quote

2) It must be clear that transaction costs using LN are much smaller than without it.

I believe it will be obviously clear.

The problem is that if fees continue to be very low, people will continue to think that this will be so forever, and not bother about LN. They could even refuse to open a LN channel because of the fear that opening and closing it could cost them even more fees (which is a fallacy, as for LN you typically pay fees 1 time for many transactions).

Quote from: Wind_FURY on October 20, 2020, 11:21:34 AM

I was expecting Bitstamp to be the first Lightning-capable exchange.

Bitstamp has a LN node (which seems to be even older than Bitfinex's), but as far as I know it doesn't offer deposits/withdrawals.

Quote from: Carlton Banks on October 19, 2020, 08:35:45 AM

It appears that Bitfinex already allow their clients to make LN deposits to their accounts. Quite a big development really, it perhaps got mixed up with the news that Bitfinex were running a public LN node?

Thanks for the info, that's really good news and I wasn't aware of it. It seems also to include withdrawals to LN (which is, imo, at ~~most~~ least equally important than deposits, so people can buy directly LN coins) and seems to have been added already in December 2019. The deposited coins are credited as "LNX" and can be converted for free to Bitcoin. It is true however that there are relatively few news articles about that and most of them focus on Bitfinex' LN node. Since September 2020 also Wumbo channels seems to be supported.

They also seem to want to add Tether deposits/withdrawals via LN. As Tether is an Omni token, this could mean OmniBOLT support.

Wind_FURY

legendary

Activity: 2898

Merit: 1823

Quote from: Carlton Banks on October 19, 2020, 08:35:45 AM

Quote from: Wind_FURY on October 19, 2020, 06:47:57 AM

Quote from: d5000 on October 17, 2020, 01:49:13 PM

For me, there are mainly two conditions for the Lightning Network to really take off:

1) Providers of massively used services must support it.

Yes, the exchanges. Onboarding exchanges must be one of the first priorities.

It appears that Bitfinex already allow their clients to make LN deposits to their accounts. Quite a big development really, it perhaps got mixed up with the news that Bitfinex were running a public LN node? I'm not sure when client account deposits went live tbh

Haha. That makes me wish that Bitfinex was a "model-exchange" that the other exchanges could follow. To be honest, I was expecting Bitstamp to be the first Lightning-capable exchange.

jackg

copper member

Activity: 2856

Merit: 3071

https://bit.ly/387FXHi lightning theory

Quote from: darkv0rt3x on October 19, 2020, 07:11:30 PM

Quote from: jackg on October 19, 2020, 04:49:27 PM

It's the minimum reserve YOU would have to change, try typing to the command line

Code:

clightning /? | grep="reserve"

And see what comes up, replacing clightning with how you'd normally run it and potentially /? with -h or - -help.

I was trying to search through the docs but there was a lot of them on their github.

Well, the output of that is:

Quote

$ lightning-cli help | grep reserve
fundpsbt satoshi feerate startweight [minconf] [reserve] [locktime]
reserveinputs psbt [exclusive]
unreserveinputs psbt
Unreserve utxos (or at least, reduce their reservation)
utxopsbt satoshi feerate startweight utxos [reserve] [reservedok] [locktime]

But in the meantime, I was talking to (what I think is) a dev and he told me this is actually a bug and he started an issue on github.
https://github.com/ElementsProject/lightning/issues/4140

In less than a week, I have already stumbled into 2 bugs. On one hand, this is bad, because a noob user and a new lightning user is coming across with quite a few bugs. On the other hand, it's good because I'm kind of contributing for the enhancement of this Lightning Network implementation.

This dev tried to push me to fix the bug, as it's apparently simple to fix, but I'm too afraid of messing things up, so I'm not going to do anything without supervision.

As far as I understood, every node in the Lightning Network has these 2 settings: channel reserve and dust limit. This said, when one node (A) tries to open a channel to another node (B), node (A) needs to make sure tat it's own channel reserve parameter is equal or greater than its own dust limit. Moreover, it also needs to make sure that its own channel reserve parameter is greater or equal to node (B) dust limit parameter.

I'm not sure about this because in the meantime, this dev stopped talking to me. He's probably afaik and where I live is now time to go to bed. If I can find this dev tomorrow again, I my try to discuss with him, the fix I have in mind, in case my assumption above is true and accurate!

The dust limit is brought over from bitcoin core. I think it rpc's into core but I don't think it takes any of its settings (but I could he wrong on that one)..

I think that's stayed for cross compatibility so core can still broadcast the transactions.

darkv0rt3x

hero member

Activity: 1176

Merit: 647

I rather die on my feet than to live on my knees

Quote from: jackg on October 19, 2020, 04:49:27 PM

It's the minimum reserve YOU would have to change, try typing to the command line

Code:

clightning /? | grep="reserve"

And see what comes up, replacing clightning with how you'd normally run it and potentially /? with -h or - -help.

I was trying to search through the docs but there was a lot of them on their github.

Well, the output of that is:

Quote

$ lightning-cli help | grep reserve
fundpsbt satoshi feerate startweight [minconf] [reserve] [locktime]
reserveinputs psbt [exclusive]
unreserveinputs psbt
Unreserve utxos (or at least, reduce their reservation)
utxopsbt satoshi feerate startweight utxos [reserve] [reservedok] [locktime]

But in the meantime, I was talking to (what I think is) a dev and he told me this is actually a bug and he started an issue on github.
https://github.com/ElementsProject/lightning/issues/4140

In less than a week, I have already stumbled into 2 bugs. On one hand, this is bad, because a noob user and a new lightning user is coming across with quite a few bugs. On the other hand, it's good because I'm kind of contributing for the enhancement of this Lightning Network implementation.

This dev tried to push me to fix the bug, as it's apparently simple to fix, but I'm too afraid of messing things up, so I'm not going to do anything without supervision.

As far as I understood, every node in the Lightning Network has these 2 settings: channel reserve and dust limit. This said, when one node (A) tries to open a channel to another node (B), node (A) needs to make sure tat it's own channel reserve parameter is equal or greater than its own dust limit. Moreover, it also needs to make sure that its own channel reserve parameter is greater or equal to node (B) dust limit parameter.

I'm not sure about this because in the meantime, this dev stopped talking to me. He's probably afaik and where I live is now time to go to bed. If I can find this dev tomorrow again, I my try to discuss with him, the fix I have in mind, in case my assumption above is true and accurate!

jackg

copper member

Activity: 2856

Merit: 3071

https://bit.ly/387FXHi lightning theory

It's the minimum reserve YOU would have to change, try typing to the command line

Code:

clightning /? | grep="reserve"

And see what comes up, replacing clightning with how you'd normally run it and potentially /? with -h or - -help.

I was trying to search through the docs but there was a lot of them on their github.

darkv0rt3x

hero member

Activity: 1176

Merit: 647

I rather die on my feet than to live on my knees

Quote from: jackg on October 19, 2020, 03:30:32 PM

I think you're wanting to change the channel reserve limit to 573 or they can change their dust limit to 546 (that might be easier for them to do and not interfere with the channel)...

We don't have any channel open. I mean, me and Friend B. (My only channel open now is with Friend A).

Do you know what is the setting I should use to set the dust limit to 573 sats?

jackg

copper member

Activity: 2856

Merit: 3071

https://bit.ly/387FXHi lightning theory

I think you're wanting to change the channel reserve limit to 573 or they can change their dust limit to 546 (that might be easier for them to do and not interfere with the channel)...

darkv0rt3x

hero member

Activity: 1176

Merit: 647

I rather die on my feet than to live on my knees

Quote from: Rath_ on October 19, 2020, 04:50:13 AM

Regarding the darkv0rt3x's case - it turned out that he had only an outbound channel to friend B. That channel required both sides to have a 546 satoshi reserve which means that he should have been able to receive about 454 satoshi through that channel since he had sent a 1000 sat payment through friend B. He tried to receive as little as 50 satoshi without success. It seems to be a problem with friend's B node. Any other suggestions are welcome.

Ok, a small update.
My Friend B ended up closing the channel I opened with him and then, some time later (hours later) he tried to open a channel with me of about 30k sats but he got this message:

I've been talking to @Rath_ and he told me I probably have to add some setting to my node to overcome this problem. But he can't help me further now because he's not where he can help me. However he told me I should search something about "dust limit".

Anyone have an idea of what should I be adding to my c-lightning node config file?

Thanks

Carlton Banks

legendary

Activity: 3430

Merit: 3071

Quote from: Wind_FURY on October 19, 2020, 06:47:57 AM

Quote from: d5000 on October 17, 2020, 01:49:13 PM

For me, there are mainly two conditions for the Lightning Network to really take off:

1) Providers of massively used services must support it.

Yes, the exchanges. Onboarding exchanges must be one of the first priorities.

It appears that Bitfinex already allow their clients to make LN deposits to their accounts. Quite a big development really, it perhaps got mixed up with the news that Bitfinex were running a public LN node? I'm not sure when client account deposits went live tbh

Wind_FURY

legendary

Activity: 2898

Merit: 1823

Quote from: d5000 on October 17, 2020, 01:49:13 PM

Quote from: Wind_FURY on October 17, 2020, 12:46:46 AM

I admire the optimism, but I don't know how an ordinary user will be expected to be in it long term, unless he/she is incentivized from the level of specialization in maintaining a Lightning node. But I see a debate for altruism to boot-strap the network.

For me, there are mainly two conditions for the Lightning Network to really take off:

1) Providers of massively used services must support it.

Yes, the exchanges. Onboarding exchanges must be one of the first priorities.

Quote

2) It must be clear that transaction costs using LN are much smaller than without it.

I believe it will be obviously clear.

Quote

Condition 1 is a chicken-and-egg problem. If there are many users, there will be many services, and vice versa. Ideally, some service providers could create something like a "beta area", where people can use LN to deposit and withdraw coins at their own risk but keeping the wallets of on-chain and LN activity strictly separated to minimize exposure to threats related to the alpha/beta state of LN software. But as it was discussed some pages ago this will probably only happen on a small scale.

Or Lightning Labs, Blockstream, or another VC-backed company that develops Lightning could hire a person specializing in business development.

Quote

So it is possible that a LN "takeoff" is more likely to come from a new increase of transaction fees due to fuller blocks (condition 2). This would make it again attractive for service providers to jump on the LN boat.

I believe not. It also needs a better UX, needs more exchanges/services providing liquidity for easy routing, and needs their users to become Lightning users.

Rath_

legendary

Activity: 1876

Merit: 3131

Regarding the darkv0rt3x's case - it turned out that he had only an outbound channel to friend B. That channel required both sides to have a 546 satoshi reserve which means that he should have been able to receive about 454 satoshi through that channel since he had sent a 1000 sat payment through friend B. He tried to receive as little as 50 satoshi without success. It seems to be a problem with friend's B node. Any other suggestions are welcome.

PrimeNumber7

copper member

Activity: 1624

Merit: 1899

Amazon Prime Member #7

Quote from: DaveF on October 15, 2020, 07:57:10 AM

Quote from: PrimeNumber7 on October 14, 2020, 11:54:01 PM

Ahh, I see your point. If a person has open channels with insufficient inbound capacity, the customer not understanding their inbound capacity limit may be an issue of insufficient/inadequate documentation that can be read/understood by the 'average' non-technical user, or error messages that are not specific enough.

If you were to send that invoice to a business, the business should (automatically) be able to tell you what is preventing them from paying the invoice, in your case insufficient inbound capacity.

Which leads to more programming / work on the time of the exchange and more places for errors / vulnerabilities to come in.

What I am describing should not add add vulnerabilities, as the amount available for outbound transactions is public information. You should be able to look at an error message, and other information, and be able to determine what the underlying problem that is preventing a transaction from going through. I don't think the technical expertise required to implement what I describe is higher than what an exchange should have. Exchanges and other businesses should have engineers that could implement what I describe; if they don't, there is a risk, even probability that other vulnerabilities will exist and will be exploited.

darkv0rt3x

hero member

Activity: 1176

Merit: 647

I rather die on my feet than to live on my knees

Quote from: Rath_ on October 18, 2020, 01:56:00 PM

Quote from: darkv0rt3x on October 18, 2020, 01:49:54 PM

Can I send you a PM with my friend's node ID and channel ID?

Sure, go ahead. Do you want me to let the other people here know what might be possibly wrong after I have checked it?

Sure, no problem. Just keep the sensitive information closed please. I'll ask permission to my friend to share our channel info too!

Edited;
Well, looks like there's not much to hide, after all. It's all at 1ml.com.

Rath_

legendary

Activity: 1876

Merit: 3131

Quote from: darkv0rt3x on October 18, 2020, 01:49:54 PM

Can I send you a PM with my friend's node ID and channel ID?

Sure, go ahead. Do you want me to let the other people here know what might be possibly wrong after I have checked it?

darkv0rt3x

hero member

Activity: 1176

Merit: 647

I rather die on my feet than to live on my knees

Quote from: Rath_ on October 18, 2020, 01:42:49 PM

Quote from: darkv0rt3x on October 18, 2020, 01:23:47 PM

If I show you the channel he opened with me, can you tell if all the conditions are met or not?

I might be able to see the details of your friend's channels on the 1ml.com explorer once you provide me with your channel's id. I don't know if all information will be up-to-date. We can give it a go if you don't mind sharing it here.

Can I send you a PM with my friend's node ID and channel ID?

Rath_

legendary

Activity: 1876

Merit: 3131

Quote from: darkv0rt3x on October 18, 2020, 01:23:47 PM

If I show you the channel he opened with me, can you tell if all the conditions are met or not?

I might be able to see the details of your friend's channels on the 1ml.com explorer once you provide me with your channel's id. I don't know if all information will be up-to-date. We can give it a go if you don't mind sharing it here.

darkv0rt3x

hero member

Activity: 1176

Merit: 647

I rather die on my feet than to live on my knees

Quote from: Rath_ on October 18, 2020, 12:37:26 PM

Quote from: darkv0rt3x on October 18, 2020, 12:32:17 PM

What am I missing and what is that reserved value I know it gets kinda locked when channels are opened?

There is an unspendable channel reserve. You need to spend about 2-3% of the channel's capacity before you will be able to receive anything. Theoretically, you should be able to receive slightly less than 30k sats through friend's B second channel since all funds are on his side of the channel at the moment. There might be some problem with friend's B channels. He might not have enough inbound capacity because of the reserve.

If I show you the channel he opened with me, can you tell if all the conditions are met or not?

Rath_

legendary

Activity: 1876

Merit: 3131

Quote from: darkv0rt3x on October 18, 2020, 12:32:17 PM

What am I missing and what is that reserved value I know it gets kinda locked when channels are opened?

There is an unspendable channel reserve. You need to spend about 2-3% of the channel's capacity before you will be able to receive anything. Theoretically, you should be able to receive slightly less than 30k sats through friend's B second channel since all funds are on his side of the channel at the moment. There might be some problem with friend's B channels. He might not have enough inbound capacity because of the reserve.

darkv0rt3x

hero member

Activity: 1176

Merit: 647

I rather die on my feet than to live on my knees

Hello once more.

As I'm new to the Lightning network, I need some help to clear a few questions I have about opening channels and inbound capacity.

So, the scenario is this:

I have a c-lightning node running on my laptop and I have Spark-Wallet installed and connected to my node.
I have Bluewallet installed in my smartphone.
I have opened 2 channels with 2 friends of mine (friend A and friend B) of 20k sats (for the sake of experimenting)
Then I sent 100 sats to friend A.
After that I sent 1000 sats to my Bluewallet. I know this transaction was routed through friend B node.
Then friend B opened a channel with me with 30k sats.
Now I'm trying to send sats from my Bluewallet to my Spark-Wallet, but no matter the value I choose, I always get an error of inbound capacity not available!

Shouldn't I be able to receive up to 100 sats from friend A node and up to 1k sats through friend B node?

What am I missing and what is that reserved value I know it gets kinda locked when channels are opened?

Timelord2067

legendary

Activity: 3668

Merit: 2218

💲🏎️💨🚓

Quote from: LoyceV on October 17, 2020, 01:57:40 PM

Unless you can use an exchange to buy Lightning Bitcoin directly so they open large channels instead of having users open small channels, but that means you can only use custodial wallets.

Not necessarily, the Eclair wallet provides for buying inbound capacity. I think the Zap wallet has a similar function.

If part of that purchase was (example) you paid for an inbound 0.05 channel and part of that 0.05 was sent to you (say 0.04) your cost might be (random numbers out of my head) say 10% on top of the 0.04 plus the TX fee to open the channel - rounded up to 0.005. In the hypothetical example you might pay (in advance) 0.045 and get a 0.05 channel opened to you with 0.01 inbound plus 0.04 outbound capacity which would no doubt be a healthy start to any new node.

Topic: The Lightning Network FAQ - page 55. (Read 32079 times)