The Lightning Network FAQ - page 35.

Rath_

legendary

Activity: 1876

Merit: 3139

Quote from: JustAnOtherLoser on August 09, 2021, 02:47:20 PM

So - Now you can't open a Channel to me? Thats really strange. I just want inbound capacity,
why you so complicated Mr. LN? :')

If I were running LND instead of c-lightning, we would be able to have two channels. Apparentely, it is a c-lightning limitation. As for the inbound liquidity, that's why I am asking you to pay a Lightning invoice in exchange for an on-chain transaction. The moment you pay my invoice, half of the channel balance will be moved to my side. You will be able to receive that much (minus a negligible channel reserve) through me. In other words, you will gain some inbound capacity.

JustAnOtherLoser

jr. member

Activity: 37

Merit: 16

Quote from: Rath_ on August 09, 2021, 05:24:15 AM

.
@JustAnOtherLoser - I have just tried opening a channel and I got an error that we already have one. Sorry for causing the confusion. I have never heard people complain about this.

So - Now you can't open a Channel to me? Thats really strange. I just want inbound capacity,
why you so complicated Mr. LN? :')

Rath_

legendary

Activity: 1876

Merit: 3139

Quote from: ndalliard on August 09, 2021, 04:51:37 AM

according to this issue on github it is not possible - i read it somewhere else too, but can't find the source atm

Thanks for that link. I have no idea how I could have missed it.

@JustAnOtherLoser - I have just tried opening a channel and I got an error that we already have one. Sorry for causing the confusion. I have never heard people complain about this.

As we agreed earlier, I am going to send you an invoice for around half of the total channel balance and refund you via an on-chain transaction. Please, send me your Bitcoin address either here or via PM.

ndalliard

full member

Activity: 154

Merit: 177

Quote from: Rath_ on August 09, 2021, 03:48:12 AM

Quote from: ndalliard on August 09, 2021, 03:41:10 AM

hmm, i thought c-lightning doesn't allow to have more than one channel with one peer - or are you guys trying something different here?

That's exactly what we are trying to do. Why would c-lightning not support it, though? I can't find any information that states so.

according to this issue on github it is not possible - i read it somewhere else too, but can't find the source atm

JustAnOtherLoser

jr. member

Activity: 37

Merit: 16

Opening a Channel worked now!

Rath_

legendary

Activity: 1876

Merit: 3139

Quote from: JustAnOtherLoser on August 08, 2021, 10:06:47 PM

Yeah, sure. Let's test this out!

I have just closed the channel and the closing transaction has been already confirmed.

Quote from: JustAnOtherLoser on August 08, 2021, 11:21:01 PM

or console commands. I always wondered if I could get 0 sats through, but never tried by now.

Even if you managed to sign a feeless transaction, it would be rejected by the majority of the nodes. Unless you gave it directly to a miner willing to help, you would be out of luck.

Quote from: ndalliard on August 09, 2021, 03:41:10 AM

hmm, i thought c-lightning doesn't allow to have more than one channel with one peer - or are you guys trying something different here?

That's exactly what we are trying to do. Why would c-lightning not support it, though? I can't find any information that states so.

ndalliard

full member

Activity: 154

Merit: 177

Quote from: Rath_ on August 08, 2021, 08:32:15 PM

I wonder if you could open a channel to me if I closed my channel. Would you mind if we give it a try? I would close my channel. Then, you would open a 100k-120k satoshi channel to me and I would try opening back a channel with the same value.

Why a 100k-120k channel? In case I am not able to open a channel to you, I could receive ~50k-60k satoshi through your channel and refund you via an on-chain transaction. This way, we would have a perfectly balanced channel even if we fail to open another channel. I am also open to other suggestions.

hmm, i thought c-lightning doesn't allow to have more than one channel with one peer - or are you guys trying something different here? Huh

JustAnOtherLoser

jr. member

Activity: 37

Merit: 16

Quote from: Timelord2067 on August 08, 2021, 10:19:49 PM

I can't convince bitcoin core to set a transaction fee to zero, the lowest I can go is one satoshi (it sets it to one thousand per kb, but I'm sure you understand what I'm referring to).

I was just wondering, what bitcoin wallet are you using that allows you to set a zero sat fee paid for transactions?

I never tried by now to be honest! I use a multiple of wallets & software. Most of them just deliver an input field
or console commands. I always wondered if I could get 0 sats through, but never tried by now.
Before LN I never moved any of my coins anyway Tongue

Timelord2067

legendary

Activity: 3696

Merit: 2219

💲🏎️💨🚓

I can't convince bitcoin core to set a transaction fee to zero, the lowest I can go is one satoshi (it sets it to one thousand per kb, but I'm sure you understand what I'm referring to).

I was just wondering, what bitcoin wallet are you using that allows you to set a zero sat fee paid for transactions?

JustAnOtherLoser

jr. member

Activity: 37

Merit: 16

Quote from: Rath_ on August 08, 2021, 08:32:15 PM

I wonder if you could open a channel to me if I closed my channel. Would you mind if we give it a try? I would close my channel. Then, you would open a 100k-120k satoshi channel to me and I would try opening back a channel with the same value.

Yeah, sure. Let's test this out! Just out of curiosity: When the Mempool is really empty, could I set 0 sats per vByte as fee? In theory a miner should not mind, if the block has empty space or will I end up bumping the fee to get my Tx through?

ps.: Thanks for fiddling around with my umbrel problems Tongue

Rath_

legendary

Activity: 1876

Merit: 3139

Quote from: JustAnOtherLoser on August 06, 2021, 04:38:01 PM

My remaining Balance would be about 120k Sats after opening a 70k Channel to you. If I understood correct everything above 100k should be sufficient?

Yes, that would be more than enough.

Quote from: JustAnOtherLoser on August 06, 2021, 04:38:01 PM

Regarding your Log + Time request
My Last Try was at: 23:28 - UTC/GMT +1:00 (06.08.2021)

I couldn't find anything useful in the logs. I have no idea what else could be the cause. Last month, two people managed to open channels to me but they were both running c-lightning and we didn't have any other active channels.

Quote from: JustAnOtherLoser on August 06, 2021, 04:38:01 PM

So maybe I should not hackle with it myself by now? ...Maybe I
should migrate my Umbrel into something less "consumer friendly

I can't guarantee you that it will work once you have migrated. I double-checked LND changelogs and it turns out that your node supports anchor channels without any extra configuration.

Quote from: https://github.com/lightningnetwork/lnd/releases/tag/v0.12.0-beta

lnd will now open the new channel type dubbed "anchor channels" by default if both peers support it.

I wonder if you could open a channel to me if I closed my channel. Would you mind if we give it a try? I would close my channel. Then, you would open a 100k-120k satoshi channel to me and I would try opening back a channel with the same value.

Why a 100k-120k channel? In case I am not able to open a channel to you, I could receive ~50k-60k satoshi through your channel and refund you via an on-chain transaction. This way, we would have a perfectly balanced channel even if we fail to open another channel. I am also open to other suggestions.

JustAnOtherLoser

jr. member

Activity: 37

Merit: 16

Quote

Are you still running LND v0.12.1?

=> "version": "0.12.1-beta commit=v0.12.1-beta"
I don't know why, but thats whats running on my Umbrel.
I'll have to look it up, I guess? Maybe there is a reason?

edit: Reddit => "You have to wait for Umbrel to support it.
Apparently v0.13 had some big changes with how the wallet is
unlocked so i am assuming that is what’s taking them so long."

So maybe I should not hackle with it myself by now? ...Maybe I
should migrate my Umbrel into something less "consumer friendly" Tongue

Quote

It looks like either you won't have enough funds in your wallet to meet the above criteria after opening a channel to me.

My remaining Balance would be about 120k Sats after opening a 70k Channel to you. If I understood correct everything above 100k should be sufficient?

Quote

or my node expects you to support anchor output channels which you probably don't have enabled.

I don't even. Anchor Output Channels? I need to search this up.

Edit: If I understood correctly, Anchor Output Channels are just special Outputs to have a fee bumping feature.
This means my Bitcoin full node should be implementing package relay, which is another feature itself?
Am I getting here somewhere or should I stop digging? Cheesy

Regarding your Log + Time request
My Last Try was at: 23:28 - UTC/GMT +1:00 (06.08.2021)

Hope this helps somehow Embarrassed

Rath_

legendary

Activity: 1876

Merit: 3139

Quote from: JustAnOtherLoser on August 05, 2021, 10:24:34 PM

(sat_per_vbyte did not seem to exist as parameter)

That's weird. You can see here that it's a valid parameter. I even remember using it a few months ago when I was running LND.

Quote from: JustAnOtherLoser on August 05, 2021, 10:24:34 PM

LND Log:

Are you still running LND v0.12.1? You messaged me that you updated Umbrel but I am not familiar with it.

Code:

[WRN] CHFD: Unable to find funding output for shim intent: unable to create witness script, no funding keys

I looked up the above warning and found out something interesting.

Quote from: https://github.com/lightningnetwork/lnd/issues/5599#issuecomment-891641663

This is expected. With the new anchor output channel format you need to keep a reserve in your wallet for when a channel needs to be force closed. The error you get isn't very helpful but this has been fixed in a recently merged PR: #5577

So you need 10k sats per channel (or a maximum of 100k sats in total) as a reserve.

Anchor output channels have been enabled by default since LND v0.13.0. It looks like either you won't have enough funds in your wallet to meet the above criteria after opening a channel to me or my node expects you to support anchor output channels which you probably don't have enabled.

I have just updated my node to the latest master branch and enabled more detailed logs. Let's see if it works now or if we can at least find out something useful.

JustAnOtherLoser

jr. member

Activity: 37

Merit: 16

Quote from: Rath_ on August 02, 2021, 06:41:53 PM

Why don't you try to open the channel using the command line? Here's the right command along with all parameters.

Code:

lncli openchannel 0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5 70000 --sat_per_vbyte 1

So - I used this Code to run your command on my Umbrel Node:

Code:

docker exec -i lnd lncli openchannel 0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5 70000 --sat_per_byte 1

(sat_per_vbyte did not seem to exist as parameter)

It gave me this: [lncli] rpc error: code = Unknown desc = peer disconnected

LND Log:

Code:

2021-08-06 03:49:54.363 [INF] SWPR: Manual fee rate input of 250 sat/kw is too low, using 253 sat/kw instead
2021-08-06 03:49:54.363 [INF] FNDG: Initiating fundingRequest(local_amt=0.0007 BTC (subtract_fees=false), push_amt=0 mSAT, chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, peer=0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5, dust_limit=0.00000573 BTC, min_confs=1)
2021-08-06 03:49:54.368 [INF] CHFD: Performing funding tx coin selection using 253 sat/kw as fee rate
2021-08-06 03:49:54.381 [WRN] CHFD: Unable to find funding output for shim intent: unable to create witness script, no funding keys
2021-08-06 03:49:54.413 [INF] FNDG: Target commit tx sat/kw for pendingID(692eecce3a37dcabb2be8370b6aaa58a39739f8b6f3f5685ceddfc70b0a4f376): 43178
2021-08-06 03:49:54.413 [INF] FNDG: Starting funding workflow with fjpmf23cd2c6sqp7e4wzexa6ixkttl3jabivldakwq733tw634ymjbid.onion:9735 for pending_id(692eecce3a37dcabb2be8370b6aaa58a39739f8b6f3f5685ceddfc70b0a4f376), committype=tweakless
2021-08-06 03:49:54.888 [INF] PEER: unable to read message from 0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5@fjpmf23cd2c6sqp7e4wzexa6ixkttl3jabivldakwq733tw634ymjbid.onion:9735: unable to parse message of unknown type:
2021-08-06 03:49:55.099 [INF] PEER: unable to read message from 0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5@fjpmf23cd2c6sqp7e4wzexa6ixkttl3jabivldakwq733tw634ymjbid.onion:9735: EOF
2021-08-06 03:49:55.100 [INF] PEER: disconnecting 0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5@fjpmf23cd2c6sqp7e4wzexa6ixkttl3jabivldakwq733tw634ymjbid.onion:9735, reason: read handler closed
2021-08-06 03:49:55.301 [INF] DISC: Removing GossipSyncer for peer=0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5
2021-08-06 03:49:55.301 [INF] DISC: GossipSyncer(02eb2d3580f4122482a0c9af5aa9d5f9a43574487e72ea5297d26d85de9e029f80): applying gossipFilter(start=2021-08-06 03:49:55.301988561 +0000 UTC m=+1017.171503105, end=2157-09-12 10:18:10.301988561 +0000 UTC)
2021-08-06 03:49:55.302 [INF] HSWC: Removing channel link with ChannelID(aabe578dfee04433ce8b3173f2bbe0f839f78bfabdee954ba6944622a736a28d)
2021-08-06 03:49:55.302 [INF] HSWC: ChannelLink(693925:886:1): stopping
2021-08-06 03:49:55.302 [ERR] RPCS: unable to open channel to NodeKey(0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5): peer disconnected
2021-08-06 03:49:55.302 [ERR] RPCS: [/lnrpc.Lightning/OpenChannel]: peer disconnected
2021-08-06 03:49:55.302 [INF] HSWC: ChannelLink(693925:886:1): exited
2021-08-06 03:49:58.663 [INF] SRVR: Established connection to: 0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5@fjpmf23cd2c6sqp7e4wzexa6ixkttl3jabivldakwq733tw634ymjbid.onion:9735
2021-08-06 03:49:58.663 [INF] SRVR: Finalizing connection to 0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5@fjpmf23cd2c6sqp7e4wzexa6ixkttl3jabivldakwq733tw634ymjbid.onion:9735, inbound=false
2021-08-06 03:49:59.557 [INF] PEER: NodeKey(0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5) loading ChannelPoint(8ca236a7224694a64b95eebdfa8bf739f8e0bbf273318bce3344e0fe8d57beaa:1)
2021-08-06 03:49:59.558 [INF] HSWC: Removing channel link with ChannelID(aabe578dfee04433ce8b3173f2bbe0f839f78bfabdee954ba6944622a736a28d)
2021-08-06 03:49:59.558 [INF] HSWC: ChannelLink(693925:886:1): starting
2021-08-06 03:49:59.558 [INF] HSWC: Trimming open circuits for chan_id=693925:886:1, start_htlc_id=0
2021-08-06 03:49:59.559 [INF] HSWC: Adding live link chan_id=aabe578dfee04433ce8b3173f2bbe0f839f78bfabdee954ba6944622a736a28d, short_chan_id=693925:886:1
2021-08-06 03:49:59.559 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(8ca236a7224694a64b95eebdfa8bf739f8e0bbf273318bce3344e0fe8d57beaa:1)
2021-08-06 03:49:59.559 [INF] PEER: Negotiated chan series queries with 0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5
2021-08-06 03:49:59.559 [INF] DISC: Creating new GossipSyncer for peer=0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5
2021-08-06 03:49:59.560 [INF] HSWC: ChannelLink(693925:886:1): HTLC manager started, bandwidth=0 mSAT
2021-08-06 03:49:59.560 [INF] HSWC: ChannelLink(693925:886:1): attempting to re-resynchronize
2021-08-06 03:49:59.875 [INF] HSWC: ChannelLink(693925:886:1): received re-establishment message from remote side
2021-08-06 03:50:00.680 [INF] DISC: GossipSyncer(0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5): applying new update horizon: start=2106-02-07 06:28:15 +0000 UTC, end=2242-03-16 12:56:30 +0000 UTC, backlog_size=0
2021-08-06 03:50:00.681 [INF] DISC: Received new remote channel announcement for 693925:886:1

JustAnOtherLoser

jr. member

Activity: 37

Merit: 16

I don't know if this was already asked (probably), buuut:

Are my LN Wallet & Channels on my Node connected to my btc wallet?

I'm asking because I was wondering what a User should do if his private Key
is leaked or compromised in any way to use an alternate BTC wallet on an
Umbrel Node. For it being a hot wallet it would be plausible to switch it out
once in a while, or am I beeing to paranoid?

Maybe it's just a UI thing and LN is capabale of this, but Umbrel isn't?

In short: My attempt would be to transfer the leftover UTXO's to a new
Private Key / BTC Wallet, but use the old LN Wallet & Channels for it.

Rath_

legendary

Activity: 1876

Merit: 3139

Quote from: JustAnOtherLoser on August 02, 2021, 08:18:28 PM

My btc core seemed to be out of sync for about 11 Hours. I'm at 100% by now again.
Could this be a problem?

I checked my logs and I kept getting the following error.

Code:

02fbb789c95ee3cfd4d5313889070720599d4d4b7a9577e2f01a3042b831c65e01-chan#53: Peer transient failure in CHANNELD_NORMAL: channeld WARNING: Bad tx_signatures [redacted]

Since your node was out of sync, it could not verify if the funding transaction had been confirmed while my node kept sending "funding_locked" message. Everything looks good now. It could also be the reason why you were not able to open a channel to me. You should keep your Bitcoin node synced at all times. If someone broadcasts an outdated commitment transaction, you have limited time to publish a penalty transaction.

Quote from: JustAnOtherLoser on August 02, 2021, 08:18:28 PM

I'll try it later again, promised! Don't close your channel Cheesy

Take your time and don't worry about it. I will be fine even if you don't open a channel back to me.

JustAnOtherLoser

jr. member

Activity: 37

Merit: 16

SSH keeps saying I entered the wrong password Roll Eyes

... thats why I use GUI at the moment.
"peer disconnected" Is what I get as Error. I already restarted my Node.

My btc core seemed to be out of sync for about 11 Hours. I'm at 100% by now again.
Could this be a problem? Running Umbrel btw. I'll try it later again, promised! Don't close your channel Cheesy

Rath_

legendary

Activity: 1876

Merit: 3139

Quote from: JustAnOtherLoser on August 02, 2021, 06:21:52 PM

I'm trying to open a Channel to your Node right now with 70k Sats. RTL did load indefinitely.
I get a "502 Bad Gateway"-Error. I'll try it again, maybe it's just a small hick-up? Never had this problem, but I
did not open too many channels by now Tongue

Try restarting RTL. I have never had any problems with it, but I am running c-lightning as the backend. Why don't you try to open the channel using the command line? Here's the right command along with all parameters.

Code:

lncli openchannel 0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5 70000 --sat_per_vbyte 1

JustAnOtherLoser

jr. member

Activity: 37

Merit: 16

Hi,

"You have exceeded the limit of 2 personal messages per day. Buying a Copper membership may increase your limit."

...so I'll write here. I'm trying to open a Channel to your Node right now with 70k Sats. RTL did load indefinitely.
I get a "502 Bad Gateway"-Error. I'll try it again, maybe it's just a small hick-up? Never had this problem, but I
did not open too many channels by now Tongue

Rath_

legendary

Activity: 1876

Merit: 3139

Quote from: DaveF on July 22, 2021, 06:14:26 AM

So they are now beginning to push out their hosted "node in a box" solution.
Don't know how much traction it's going to get but it's another way for people to use lightning so unless it's total garbage I see it as a good thing.

Since all the signing is done on user's device, such node will probably not able to route payments. The only advantage over some mobile wallet I can think of is ability to use advanced features like: dual-funding, multifund, keysend payments.

Topic: The Lightning Network FAQ - page 35. (Read 33677 times)