If you don't mind, you can share your node URI either in this thread or here. I am willing to open a channel to other forum members. Someone else might be interested in it too.

It is still in early-stages, but it's feasible between two c-lightning nodes if they both enable it in their config. The official specification has not been finalized yet so I guess that's why it is not available in other implementations. It will also take some extra time for wallets to implement it.

I am currently waiting for DaveF to update his node and we are going to test it out. If you are interested in the results then keep a close eye on The Lightning Network FAQ thread.

Usually, such services are time-limited or will keep their channel open only if you use their channel frequently. Otherwise, there is no incentive for them to keep the channel open, especially if you are running a client which does not route payments.


That's actually a tough question! There's plenty of great wallets out there, but since most of them are designed for mobile devices, they don't really handle inbound channels well. I would have to do some thorough research to answer your question. I have been running a c-lightning node for quite some time now and it's great because I am not limited in any way, but such a setup would be unnecessarily complicated for you. Here's what I would suggest:

1) You can use whichever wallet you want while you friend uses BlueWallet to receive the payment without any extra steps.

2) You can both use Electrum and open a channel to some node (preferably the same one). Your friend can use the built-in swap functionality to exchange his off-chain coins to on-chain coins for a small fee. He will gain incoming capacity in his channel this way and he should be able to receive your payment.


I think the biggest disadvantage is that you can't route payments which should be obvious given that no one keeps Electrum open 24/7. You might also have a hard time getting an inbound channel to work. It won't be a good choice for your plan. You might find some useful information in my "Electrum Lightning Network walkthrough" thread.

Sounds good. However, each channel has to maintain a reserve (1-3% of the channel's total capacity) which is unspendable so both of you would have to have slightly larger channels.


It will be very difficult to have some large node open a channel to your friend. You might be better off using some custodial wallet like BlueWallet. This way, your friend won't have to bother with opening and maintaining his own channel - he will be able to receive your Lightning payment instantly. It won't be a "real" Lightning Network experience since you won't be able to route payments or create your own channels but it is definitely an easy way for beginners like you to get onboard.

W razie gdyby ktoś z Was chciał otworzyć do mnie kanał, to podaję nowe ID oraz adres swojego węzła. Nie zamierzam zmieniać implementacji po raz kolejny, więc w przyszłości nie powinny się one zmienić.


https://1ml.com/node/0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5

2 GB of upload for free accounts and 20 GB for paid users are nowhere near the 67 GB which I would have to send. Thanks for your suggestion, though!

My SSD was connected to the USB 2.0 port for the first 2 days. About 430,000 blocks were processed in the first 24 hours and about 25,000 blocks in another 24 hours.


If it is just for testing, I can share my database with you. I have no idea where to upload it, though.

I finally managed to set up my new server. I don't expect to have to close all of my channels ever again. @jackg, could you update my node's information?

Najnowsza aktualizacja c-lightning wprowadziła eksperymentalne wsparcie dual-funding, które umożliwia zasilenie kanału przez obu jego uczestników. Zamierzam przetestować tę funkcję z dwoma innymi członkami forum jakoś w przyszłym tygodniu. Jeżeli będzie ona działać bezproblemowo, to będzie to duży krok do przodu - balansowanie kanałów od razu po ich otwarciu jest po prostu męczące.

I am not sure what you are driving at. Dual-funding is currently supported only by properly configured up-to-date c-lightning nodes.


Take your time. I am trying to figure out how to use lightning-cli funderupdate which allows you to control the behaviour of your node when some dual-funding compatible node opens a channel to you. I can't find any detailed documentation about it except for a short explanation in the command line.

I have just connected to your node. My new node should be reachable at 0273da0a525390c36857841e208f1d289275c76ebfa7ecfde697c6cbf4f235b4f5@fjpmf23cd2c6sqp7e4wzexa6ixkttl3jabivldakwq733tw634ymjbid.onion:9735 . I am about to fund its wallet and start reopening my channels.

I am aware of that. I am already running a bunch of virtual machines on that server so I would rather not waste any resources, especially RAM.


Sounds good, but an UPS would be an overkill for the amount of BTC that I want to lock up on the LN.


I compiled c-lightning yesterday on my own without specifying the target version, so I guess that I am running a fairly recent version of the master branch. lightning-cli getinfo returns version: v0.10.0-162-g33736b8


Thanks Dave! The mempool is slowly clearing up, so I would appreciate if you could do it in your spare time. By the way, are you going to open any more channels in the near future? I would like to maintain channels with a few forum members but it would nice to improve my node's connectivity this way.

Thanks Carlton for your write-up! I have recently decided to switch from a Raspberry Pi to a normal server. Since LND does not recommend reusing the channel database between different architectures, I had to close all of my channels. I was thinking about using a different implementation this time. You sold me on c-lightning. I am going to miss Zap Wallet, though. Spark Wallet isn't nearly as good.

Would there anyone here be interested in testing out dual-funding once the transaction fees have gone down?

For future reference: the sync up to the 684,456 block height took 6 days and 15 hours. It would have been faster if I had noticed earlier that my external drive was connected to a USB 2.0 port. The database directory weights about 66 GB.

Correct.


Yes, you would have to pay a transaction fee.


Hardly anything can go wrong. As long as you keep your Trezor One untouched, you will still have access to your coins.

I managed to get USB 3 passthrough to work by using a front panel connector and replacing the data cable. The sync ETA has dropped from 13 days to just two and I can see that the VM is now using up to 30% of the assigned CPU power.


I don't think there is a significant performance difference between a SATA and an USB 3.0 SSD. Even if I disassembled my SSD, it would probably have an mSATA connector which my motherboard does not have. I will upgrade to an NVMe SSD at some point, but I wanted to reuse an SSD from my previous Raspberry Pi setup for the time being.

I have just realised that I have plugged in my SSD into an USB 2.0 port It looks like my motherboard has only two USB 3.2 gen 2 ports and I couldn't get passthrough to work for them, so I plugged in my SSD into some random working port. I will report back once I have managed to get it to work. How much time did your sync take?

Hey,

I am running a virtual machine under Proxmox with bitcoind and ElectrumX. It took about 24 hours for the ElectrumX to process about 430,000 blocks. It's been a few more hours and only 15,000 blocks were processed.

ElectrumX dbcache is set to 2000 MB. Bitcoind dbcache is 2048 MB. I assigned 4 cores and 5 GB of RAM to the VM. htop reports that electrumx-server process uses less than 10% of the CPU (11th gen Intel i5). Both bitcoind and ElectrumX use less than 2 GB of RAM in total. They both read/write data from the same external SSD.


I wonder if there is a major bottleneck in my setup or if I misconfigured something.

Thanks for your suggestion. I will probably overhaul this thread at some point. Still, I think that there are plenty of YouTube videos and Medium articles showing such basics. Although, I am not sure how up-to-date they are since I didn't look at any of them in a long time.


Sure, but with Taproot, no one will be able to tell if coins were locked up in a channel (unless that channel ends up being closed uncooperatively). That's a significant privacy enhancement.


You can see his deleted posts here. He was mostly arguing about Lightning not being Bitcoin.

Sounds good. You can also do the dry-run recovery to see if you have written down your seed correctly.


You should read about this Trezor exploit. If you are worried about any physical attacks then you should use a long passphrase.