Thanks for the input! I'll take a look at it again tonight and see what's what. I've been doing a huge amount of page hopping and I wouldn't like to tackle the git repo for bitcoin nodes to check what functions and what doesn't (it'd be nice if they left a flag on bips but they may already do)...
As an edit, I've just got through fixing any errors I could find in the first 6 lessons, if you spot anything else please let me know - some smaller things are harder to find, and it's normally harder to find more than one source mentioning it.
Topic: Discussion and support on the lightning network lessons (Read 265 times)
The inputs used when signing the channel opening transaction (the first signed transaction passed) use SIGHASH NOIPUT to ensure the funds can be spent from the address without the need for an input transaction being broadcast or signed
• In order to ensure the last Commitment Transaction is pushed to the blockchain, OP_CHECKSEQUENCEVERIFY is a suggested soft fork. Based on what the paper suggests, his information is currently stored in a bitcoin transaction but it isn’t enforced by miners or empool broadcasters and can’t be relied upon.
hey jack
in your lesson fortnight thread, you ought to amend the wording concerning SIGHASH_NOINPUT and OP_CHECKSEQUENCEVERIFY. The current text implies that SIGHASH_NOINPUT is a usable opcode in Bitcoin script, and that OP_CHECKSEQUENCEVERIFY is not usable, whereas the opposite is in fact the truth! OP_CHECKSEQUENCEVERIFY was activated by soft-fork (as BIP68 IIRC) several years ago, maybe 2016, while the precise details of a SIGHASH_NOINPUT opcode (including both it's precise fashion of operating _and_ in turn it's final name) have been subject to debate in the development community for many months, that process has not yet finished (although 1 proposal was accepted as a draft BIP... edit BIP118 authored by Christian Decker)
I think you've just mixed historical documents together with documents that look to future upgrades, should be easy to untangle.
I was just wondering if you could.
My node is on my phone and it's not been unlocked so that's why it's shown as offline. I think that'd be classed as an agreed closure anyway so wouldn't be (exactly) what I'm looking into atm...
I'm on revokable delivery txs atm and I don't think this would use them.
My node is on my phone and it's not been unlocked so that's why it's shown as offline. I think that'd be classed as an agreed closure anyway so wouldn't be (exactly) what I'm looking into atm...
I'm on revokable delivery txs atm and I don't think this would use them.
It probably literally is your private keys or at least a way of transferring them across (potentially a master private).
I didn't realise your post here and was going to ask another question, do you have an option to close the channel I opened with you from your end? Like is it a verbose option or would it just be available via some reverse engineering.
I didn't realise your post here and was going to ask another question, do you have an option to close the channel I opened with you from your end? Like is it a verbose option or would it just be available via some reverse engineering.
I can do lncli closechannel e7568dc5d5f9c540f8f0c014f920da471d6648d8b4abc3447e241e73f9fdc524 0 and that should take care of it.
I see your node as inactive are you having an issue?
I will close it if you want, but if you are not going to be offline for long it would be better if your node sees the close.
-Dave
It probably literally is your private keys or at least a way of transferring them across (potentially a master private).
I didn't realise your post here and was going to ask another question, do you have an option to close the channel I opened with you from your end? Like is it a verbose option or would it just be available via some reverse engineering.
I didn't realise your post here and was going to ask another question, do you have an option to close the channel I opened with you from your end? Like is it a verbose option or would it just be available via some reverse engineering.
This is a bit of a lesson and a bit of just plain security.
There are utilities for for zap wallet / lnd and zeus / lnd to generate a QR code on the machine hosting your node to connect your mobile wallet to it.
These QR codes are the "keys to the kingdom" so to speak, think of them as private keys to a wallet. With them you can spend / open / close channels.
It's easy to forget this and keep a copy of the QR code someplace that might not be safe.
Don't do it.
-Dave
There are utilities for for zap wallet / lnd and zeus / lnd to generate a QR code on the machine hosting your node to connect your mobile wallet to it.
These QR codes are the "keys to the kingdom" so to speak, think of them as private keys to a wallet. With them you can spend / open / close channels.
It's easy to forget this and keep a copy of the QR code someplace that might not be safe.
Don't do it.
-Dave
No, pending open is different then pending closed. It shows up differently.
These are just sitting out there in pending open.
The joy of beta software
I was just looking for a way to make them go away for appearance sake when looking at it.
-Dave
These are just sitting out there in pending open.
The joy of beta software
I was just looking for a way to make them go away for appearance sake when looking at it.
-Dave
I can try closing mine and seeing if it turns to 0ending? If it's just how channels close, maybe it's part of how they're dealt just in case....
Not sure if it is 2 weeks yet on one of them. If not it's close to two weeks on one of them.
I had this issue before on my old node and it was definitely over 2 weeks. Closer to 2 months that they were sitting out there pending.
I really don't want to take it to github, lots of reasons but mostly due to time, and the way people who are "there to help" can get snippy with you when you don't reply in a timely manner because, I don't know you might have to work and sleep now and then.
-Dave
I had this issue before on my old node and it was definitely over 2 weeks. Closer to 2 months that they were sitting out there pending.
I really don't want to take it to github, lots of reasons but mostly due to time, and the way people who are "there to help" can get snippy with you when you don't reply in a timely manner because, I don't know you might have to work and sleep now and then.
-Dave
Ahh will it not show the address? And has it been like that for more than 2 weeks?
I was wondering if it was to do with the 2016 blocks you get to contest a channel's CT (Confirmation Transaction) broadcast to the blockchain.
I was wondering if it was to do with the 2016 blocks you get to contest a channel's CT (Confirmation Transaction) broadcast to the blockchain.
Running lncli pendingchannels I get the following.
"total_limbo_balance": "0",
"pending_open_channels": [
{
"channel": {
"remote_node_pub": "02c00024c38031616f17f60dab1231477b52764e9f981fbecebe57ea518dc8610f",
"channel_point": "932418f98fe63e1f1e2433417f8770b6ae0114f0992adfa2384bfa8bd8868d16:0",
"capacity": "200000",
"local_balance": "0",
"remote_balance": "190950",
"local_chan_reserve_sat": "2000",
"remote_chan_reserve_sat": "2000"
},
"confirmation_height": 0,
"commit_fee": "9050",
"commit_weight": "552",
"fee_per_kw": "12500"
},
{
"channel": {
"remote_node_pub": "0340e22eb2c4c4e1793ee2e7100a695a4ed0899723484efcd00f48b5ccecb6b93f",
"channel_point": "53c3a1e790892da5967a757faa84a4635d9daf7678df5fe7d03a933730bd66e8:0",
"capacity": "110000",
"local_balance": "0",
"remote_balance": "109455",
"local_chan_reserve_sat": "1100",
"remote_chan_reserve_sat": "1100"
},
"confirmation_height": 0,
"commit_fee": "545",
"commit_weight": "552",
"fee_per_kw": "754"
Sometimes there is a 3rd that pops up and goes away. But, those are just sitting there. Nothing I do can remove them. It's just when I run that command or look in the RTL web interface I then have to go and check if they disappeared and someone else is opening a channel or it's just them. Last night was a good example, I had the 2 of them the odd 3rd one that comes and goes and yours.
-Dave
Code:
"total_limbo_balance": "0",
"pending_open_channels": [
{
"channel": {
"remote_node_pub": "02c00024c38031616f17f60dab1231477b52764e9f981fbecebe57ea518dc8610f",
"channel_point": "932418f98fe63e1f1e2433417f8770b6ae0114f0992adfa2384bfa8bd8868d16:0",
"capacity": "200000",
"local_balance": "0",
"remote_balance": "190950",
"local_chan_reserve_sat": "2000",
"remote_chan_reserve_sat": "2000"
},
"confirmation_height": 0,
"commit_fee": "9050",
"commit_weight": "552",
"fee_per_kw": "12500"
},
{
"channel": {
"remote_node_pub": "0340e22eb2c4c4e1793ee2e7100a695a4ed0899723484efcd00f48b5ccecb6b93f",
"channel_point": "53c3a1e790892da5967a757faa84a4635d9daf7678df5fe7d03a933730bd66e8:0",
"capacity": "110000",
"local_balance": "0",
"remote_balance": "109455",
"local_chan_reserve_sat": "1100",
"remote_chan_reserve_sat": "1100"
},
"confirmation_height": 0,
"commit_fee": "545",
"commit_weight": "552",
"fee_per_kw": "754"
Sometimes there is a 3rd that pops up and goes away. But, those are just sitting there. Nothing I do can remove them. It's just when I run that command or look in the RTL web interface I then have to go and check if they disappeared and someone else is opening a channel or it's just them. Last night was a good example, I had the 2 of them the odd 3rd one that comes and goes and yours.
-Dave
Can I get a screenshot? Perhaps it's an issue that needs to be opened on github instead also if its directly linked with the program.
I could probably work out how to get rid of them but if you haven't found it on the gui after a bit of searching it's be a fairly unstable deletion and you're better off waiting for them since you'll sacrifice your channels funds trying to fiddle about with them so much.
I could probably work out how to get rid of them but if you haven't found it on the gui after a bit of searching it's be a fairly unstable deletion and you're better off waiting for them since you'll sacrifice your channels funds trying to fiddle about with them so much.
Gonna put a tokened response here to show I replied.
I'm opening up a channel with you and it should have 0.004 in capacity. I sent a low fee because its 4am here and I need sleep 😂. Sk it should confirm by the time I wake up.
I'm opening up a channel with you and it should have 0.004 in capacity. I sent a low fee because its 4am here and I need sleep 😂. Sk it should confirm by the time I wake up.
Your channel opened.
Still need help on removing the "phantom" channels. As I said for now it's no big deal but I can see it over time becoming an issue.
-Dave
Gonna put a tokened response here to show I replied.
I'm opening up a channel with you and it should have 0.004 in capacity. I sent a low fee because its 4am here and I need sleep 😂. Sk it should confirm by the time I wake up.
I'm opening up a channel with you and it should have 0.004 in capacity. I sent a low fee because its 4am here and I need sleep 😂. Sk it should confirm by the time I wake up.
Trying to figure out a way around this:
https://bitcointalksearch.org/topic/m.53584618
As of now I have2 3 pending open channels. Been that way for a long time.
Trying to find a way to close / remove them from LND.
Not a major issue now, but I can see it becoming one as they build over time.
Thanks,
Dave
Also: https://bitcointalksearch.org/topic/do-we-need-a-separate-sub-board-for-lightning-wallets-nodes-5209227
https://bitcointalksearch.org/topic/m.53584618
As of now I have
Trying to find a way to close / remove them from LND.
Not a major issue now, but I can see it becoming one as they build over time.
Thanks,
Dave
Also: https://bitcointalksearch.org/topic/do-we-need-a-separate-sub-board-for-lightning-wallets-nodes-5209227
Hi, I'm going to be starting to post lessons on the lightning network availabe here: https://bitcointalksearch.org/topic/m.53607838
If you have any question on it or are a bit stuck with anything feel free to ask them here.
If you have any question on it or are a bit stuck with anything feel free to ask them here.
Jump to: