c-lightning v0.10.1 has been released. If anyone is interested in opening a dual-funded channel then my offer still stands. Make sure to contact me before opening a channel to me so that I can adjust my funder policy. |
|
|
|
It seems like I need to dig deeper into c-lightning & LND. Thanks for helping me out!
c-lightning is great if you are interested in features like dual-funding or funding multiple channels in a single transaction. LND is much better in terms of available services: ThunderHUB, Zap Wallet, Lightning Loop, Sphinx Chat and so on. I used both of them and so far I have been enjoying c-lightning more. I guess that "Channel reserve" triggered my Question. I send about 150 Sats through another Channel and wondered why I can't receive 1 Sat Invoices after that.
Exactly. The channel reserve is usually 1%-3% of the total channel capacity. In our channel, it is equal to 1200 satoshi so you can receive 58800 satoshi through me despite that you have paid me 60k satoshi. |
|
|
|
When you can, please check your Electrum apps and let me know if this option is ticked or unticked in your settings.
I installed Electrum 4.1.0 and 4.1.5 on Windows Sandbox and both of these version had this option enabled by default. The way it is now, what happens with my change?
The change will be sent back to one of your existing addresses rather than to a new address. Should I tick this option?
Maybe? I always disable it and manually decide what to do with the change. You can use exclamation mark ("!") instead of a specific amount to spend the remaining value of the selected inputs. Example: Input: 0.3 BTC Address #1, 0.1
Address #2, ! "!" means that 0.2 BTC minus the transaction fee will be sent to Address #2. |
|
|
|
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. |
|
|
|
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. |
|
|
|
Yeah, sure. Let's test this out!
I have just closed the channel and the closing transaction has been already confirmed. 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. 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. |
|
|
|
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. 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. 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. 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. |
|
|
|
I only have just now noticed this, it has happened before. What exactly is the second transaction of a random amount of BTC?
The second output of your transaction is change. If you don't spend the whole value of an input then you have to send the remaining part back to yourself, preferably to a new address for privacy reasons. See this Trezor wiki entry. |
|
|
|
970 or 980 series for sure are my main pick.
Watch out for the non-pro version of the 980. It is a DRAM-less drive. Although, you should be fine as long as you are not going to make large file transfers. It will last you a long time anyway. I didn't know that about Adata, but that is probably the reason they are much cheaper than Samsung.
I bought some ADATA NVMe SSD and I returned it on the following day. It was overheating despite using the included metal heat spreader. I bought a different drive from Corsair and it's been working perfectly fine for over 3 years now. |
|
|
|
Edit: Jednak poniższa kampania raczej nie jest dobrym pomysłem. ŹródłoManager: Betking Manager
Nazwa kampanii: Betking.io Signature Campaign | The Best Bitcoin Casino
Ile do zarobienia/tydzień / ilość postów: Full Member - $20 w BTC/tydzień, Sr. Member - $30 w BTC/tydzień, Hero Member/Legendary - $40 w BTC/tydzień
Jakie rangi: 10x Full Member, 15x Sr. Member, 15x Hero Member/Legendary
Dodatkowe informacje: Minimum 20 postów tygodniowo, w tym minimum 8 postów w sekcji Gambling/Gambling Discussion. Lokale nie liczą się. |
|
|
|
My idea was to use this new drive for running a node and for storing some unimportant data, files, videos and music, if drive have larger capacity than 1 TB.
Sounds good. I am already doing it with my 1 TB drive since I have over 400 GB of storage left. Samsung and Adata SSD are my first options if I decide to buy one more SSD.
Buy an SDD from Samsung. 970 Evo series drives are solid. ADATA was one of the first companies to cheat by replacing the controllers. |
|
|
|
So my question: Is it better to buy new HDD with larger capacity or SSD with 1 or 2 TB, and what drives are you using for running your Bitcoin nodes?
1 TB should be good for the next few years. I am running my Bitcoin node with txindex (~34 GB) and blockfilterindex (~6.5 GB) enabled, and its data folder weighs ~425 GB in total. I am also running ElectrumX which takes up around 70 GB. A Lightning Network node takes up a negligible amount of space. By the time you need more storage, 2 TB SSDs should have become more affordable. I am currently using a 1 TB Sandisk Extreme USB SSD and it works well. If I hadn't had it from my old Raspberry Pi build, I would have bought an NVMe SSD. However, buying an SSD is a huge PIA. Less durable QLC SSDs are becoming more and more common. Some manufacturers quietly replace controllers in existing models which significantly degrades their performance or lifetime. You might even buy a DRAM-less SSD which again, hurts the performance. You might find a good deal on some SATA SSD if you are willing to wait. I think it would be a good compromise between an HDD and an NVMe SSD if you are on a budget. |
|
|
|
(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. LND Log:
Are you still running LND v0.12.1? You messaged me that you updated Umbrel but I am not familiar with it. [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. 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. |
|
|
|
@ Rath_: nice catch, eagle eyes. How could that have happened? Was there an automatic RBF when he opened the channel?
No idea. RBF on the opening transaction adds a lot of complexity. That's why it's not available in Electrum. I believe that LND simply performs CPFP if there is a change output. C-lightning uses RBF only if both nodes follow the (experimental) dual-fund/v2 open protocol. AFAIK, that output's script should have another public key (for the other party's wallet) that can spend it without waiting for the set time.
The RSMC output of the commitment transaction can be spent immediately only using a combination of Electrum trampoline's and OP's revocation keys for that particular transaction. Once the timeout has expired, the output can be also spent using OP's private key. I explained it in detail here. |
|
|
|
I have just realised something. Your funding outpoint for some reason contains a different (not valid) transaction ID rather than the actual funding transaction. I guess that you could get that channel to work by modifying it manually! Close Electrum, go to %appdata%\Electrum\wallets and open your wallet file in some text editor. Find the following piece of text: "funding_outpoint": {
"output_index": 0,
"txid": "963e417c937bbd97d4e66ad3127f8168f24a4bf38cdaefc427c96922c2e5795d"
},Replace it with: "funding_outpoint": {
"output_index": 0,
"txid": "13822376273207cb13b598f3a9f5b8cc957fae2041c45c0e190c0716948344cb"
},Save the file and launch Electrum. |
|
|
|
After i ran electrum again few hours later, the channel opening transaction was confirmed.
Are you sure about that? Double click on that channel, copy the funding outpoint and look it up in any block explorer. It looks as if the funding transaction has never been broadcast. Also, if Electrum trampoline knew about this channel, there would be a valid channel id.Edit: Clarification: the short channel ID includes the blockheight at which the transaction was confirmed. So, if the funding transaction has never been broadcast/confirmed, there is no short channel id. |
|
|
|
Szkoda, że wszystkie takie gotowe rozwiązania są robione pod LND, a nie c-lightning. Jak tylko uda Ci się postawić swój własny węzeł, to z chęcią otworzę do Ciebie kanał. wszystko czego potrzebujecie to raspberry pi 4 z 8gb ram, karte sd 16gb i najlepiej dysk twardy 1tb ssd
Raspberry Pi z 4 GB RAM spokojnie wystarczy. Prędzej wydajność CPU będzie wąskim gardłem. Przesiadłem się z RPi 4 GB na zwykły serwer i jestem bardzo zadowolony. Maszyna wirtualna z Bitcoin Core + c-lightning + ElectrumX zużywa zaledwie 700 MB RAMu oraz 1 GB swap. It is nice that it has all these packages installed, but I confess that it's slow as f*ck. Apart from the full node and the electrum server, there's no reason to run anything else. The mempool viewer fails to load the balances of the addresses and goes extremely slow for everything else. I synced the Electrum server and it then allowed me to install the rpc explorer which is even slower.
Myślę, że to całkiem trafny opis. Próbowałem postawić ElectrumX na swojej malince, ale poddałem się po tygodniu. Wstępna synchronizacja (a właściwie przygotowanie bazy danych) była daleka końca po tym czasie. Cały proces zajął nieco ponad 6 dni na moim obecnym serwerze z i5 11 generacji i dysku SATA SSD. |
|
|
|
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. 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. I'll try it later again, promised! Don't close your channel  Take your time and don't worry about it. I will be fine even if you don't open a channel back to me. |
|
|
|
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  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. lncli openchannel 0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5 70000 --sat_per_vbyte 1 |
|
|
|
It's a nice way to earn, do I need to make payments to publish an article for people to read?
There is a "Write New Article" button in the top-right corner. At the moment, you need to pay $0.84 to publish an article. However, if you provide your node's public key, you can withdraw the coins that other people will pay to read your article. Since you are using BlueWallet, you would have to provide the public key of their node. Unfortunately, this would allow every BlueWallet user to pay out your earnings. |
|
|
|
|
Show Posts
