🔥🔥 Complete GUIDE for Lightning Desktop Nodes

[NotATether]

Adoptium JDK

What is it with all these JDKs published by new projects?

While I get that the Java community is very strong (and that's a great thing!), ever since Oracle locked their own JDK binaries behind a subscription, we have all these companies and open projects making their own installers. Why so many though?

Also it feels like ages since JDK 21 was last released.

[Satofan44]

Adoptium JDK

What is it with all these JDKs published by new projects?

While I get that the Java community is very strong (and that's a great thing!), ever since Oracle locked their own JDK binaries behind a subscription, we have all these companies and open projects making their own installers. Why so many though?

Excellent question. It seems that Eclair previously used and recommended openJDK 11, which reached EOL. After this they updated to JDK21 and transitioned directly to Adoptium. Adoptium is a runtime that is made by the Eclipse Foundation. Here's an overview of JDKs if you are interested in that sort of thing. I am not that into Java, so I couldn't be able to say too much about why there are this many installers these days but indeed there are quite a few.

Also it feels like ages since JDK 21 was last released.

September 2023, but it is an LTS version. Unless they end up having a specific requirement from the newer versions, I assume Eclair will stick to this one until it is EOL as well.

[Satofan44]

Bump! Does nobody have an auto bump bot? That would be a nice feature. 

[Johnlomape]

Bump! Does nobody have an auto bump bot? That would be a nice feature.  

If you are looking for a bot for bumping your thread, maybe you can ask this question on Wall Observe created by Infofront. There is a well established bot their that is active bumping the thread.

I don't know if the forum actually support the idea of using a bot for now but ChartBuddy has been active since 2013 working like a bot.

[Satofan44]

Bump! Does nobody have an auto bump bot? That would be a nice feature.  

If you are looking for a bot for bumping your thread, maybe you can ask this question on Wall Observe created by Infofront. There is a well established bot their that is active bumping the thread.

I don't know if the forum actually support the idea of using a bot for now but ChartBuddy has been active since 2013 working like a bot.

Infofront has not been active since August so this will not work. I am surprised that somebody else like LoyceV does not have a bump bot here. 

[TokenTikas]

If everything is set up correctly, how long does it usually take after running an LND node for the status to change from “synced graph: false” to “synced graph: true”? Who else has faced this kind of issue? I followed a step-by-step tutorial and ran my LND node properly, but it has been more than 30 hours and still “synced graph: true” is not showing.

I honestly can’t figure out where the problem is. Everything seems fine, but what does it mean if this is still happening? If anyone here has experienced a similar issue, please explain your experience. As far as I knew, after running the node for around 24 hours, “synced graph: true” should normally appear.

[Satofan44]

If everything is set up correctly, how long does it usually take after running an LND node for the status to change from “synced graph: false” to “synced graph: true”? Who else has faced this kind of issue? I followed a step-by-step tutorial and ran my LND node properly, but it has been more than 30 hours and still “synced graph: true” is not showing.

I honestly can’t figure out where the problem is. Everything seems fine, but what does it mean if this is still happening? If anyone here has experienced a similar issue, please explain your experience. As far as I knew, after running the node for around 24 hours, “synced graph: true” should normally appear.

Thanks for posting here, it is an opportunity for everyone to learn something. If everything else is correct, it should happen pretty quickly on a system with good hardware. Please run the tests that I asked you to and post the results, here there are again.

Check whether your node is fully synchronized.

Code:

bitcoin-cli getblockchaininfo

Check your peer list.

Code:

lncli listpeers

Find a couple of peers on 1ML and manually connect to them.

Code:

lncli connect node_id@host:port

Then check the list again.

Code:

lncli listpeers

[TokenTikas]

Code:

lncli connect node_id@host:port

I’ve already connected this and even after connecting a “peer,” the result is still not correct. I’ve already connected three peers, but there’s no change in the result at all.

Code:

C:\lnd>lncli connect 3.33.236.230:9735
[lncli] target address expected in format: pubkey@host:port

C:\lnd>lncli connect 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f@3.33.236.230:9735
{
    "status":  "connection to 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f@3.33.236.230:9735 initiated"
}

C:\lnd>lncli connect 035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226@170.75.163.209:9735
{
    "status":  "connection to 035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226@170.75.163.209:9735 initiated"
}

C:\lnd>lncli connect 0242a4ae0c5bef18048fbecf995094b74bfb0f7391418d71ed394784373f41e4f3@3.124.63.44:9735
{
    "status":  "connection to 0242a4ae0c5bef18048fbecf995094b74bfb0f7391418d71ed394784373f41e4f3@3.124.63.44:9735 initiated"
}

Code:

lncli listpeers

I checked lncli listpeers, and there I can see the synced type as “passive,” and everything looks fine. Still, synced_graph: true is not showing up. My PC has been turned on continuously, and I can see that Bitcoin is running properly. So now I can’t really figure out where the problem is coming from.

Code:

C:\lnd>lncli listpeers
{
    "peers":  [
        {
            "pub_key":  "03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f",
            "address":  "3.33.236.230:9735",
            "bytes_sent":  "4429",
            "bytes_recv":  "944815",
            "sat_sent":  "0",
            "sat_recv":  "0",
            "inbound":  false,
            "ping_time":  "-1",
            "sync_type":  "PASSIVE_SYNC",
            "features":  {
                "0":  {
                    "name":  "data-loss-protect",
                    "is_required":  true,
                    "is_known":  true
                },
                "7":  {
                    "name":  "gossip-queries",
                    "is_required":  false,
                    "is_known":  true
                },
                "8":  {
                    "name":  "tlv-onion",
                    "is_required":  true,
                    "is_known":  true
                },
                "11":  {
                    "name":  "unknown",
                    "is_required":  false,
                    "is_known":  false
                },
                "13":  {
                    "name":  "static-remote-key",
                    "is_required":  false,
                    "is_known":  true
                },
                "14":  {
                    "name":  "payment-addr",
                    "is_required":  true,
                    "is_known":  true
                },
                "17":  {
                    "name":  "multi-path-payments",
                    "is_required":  false,
                    "is_known":  true
                },
                "19":  {
                    "name":  "wumbo-channels",
                    "is_required":  false,
                    "is_known":  true
                },
                "23":  {
                    "name":  "anchors-zero-fee-htlc-tx",
                    "is_required":  false,
                    "is_known":  true
                },
                "25":  {
                    "name":  "route-blinding",
                    "is_required":  false,
                    "is_known":  true
                },
                "27":  {
                    "name":  "shutdown-any-segwit",
                    "is_required":  false,
                    "is_known":  true
                },
                "29":  {
                    "name":  "unknown",
                    "is_required":  false,
                    "is_known":  false
                },
                "35":  {
                    "name":  "quiescence",
                    "is_required":  false,
                    "is_known":  true
                },
                "37":  {
                    "name":  "unknown",
                    "is_required":  false,
                    "is_known":  false
                },
                "39":  {
                    "name":  "unknown",
                    "is_required":  false,
                    "is_known":  false
                },
                "43":  {
                    "name":  "unknown",
                    "is_required":  false,
                    "is_known":  false
                },
                "44":  {
                    "name":  "explicit-commitment-type",
                    "is_required":  true,
                    "is_known":  true
                },
                "47":  {
                    "name":  "scid-alias",
                    "is_required":  false,
                    "is_known":  true
                },
                "61":  {
                    "name":  "rbf-coop-close",
                    "is_required":  false,
                    "is_known":  true
                },
                "155":  {
                    "name":  "unknown",
                    "is_required":  false,
                    "is_known":  false
                },
                "561":  {
                    "name":  "unknown",
                    "is_required":  false,
                    "is_known":  false
                },
                "563":  {
                    "name":  "unknown",
                    "is_required":  false,
                    "is_known":  false
                }
            },
            "errors":  [],
            "flap_count":  0,
            "last_flap_ns":  "0",
            "last_ping_payload":  ""
        },
        {
            "pub_key":  "0242a4ae0c5bef18048fbecf995094b74bfb0f7391418d71ed394784373f41e4f3",
            "address":  "3.124.63.44:9735",
            "bytes_sent":  "261",
            "bytes_recv":  "261",
            "sat_sent":  "0",
            "sat_recv":  "0",
            "inbound":  false,
            "ping_time":  "-1",
            "sync_type":  "PASSIVE_SYNC",
            "features":  {
                "0":  {
                    "name":  "data-loss-protect",
                    "is_required":  true,
                    "is_known":  true
                },
                "5":  {
                    "name":  "upfront-shutdown-script",
                    "is_required":  false,
                    "is_known":  true
                },
                "7":  {
                    "name":  "gossip-queries",
                    "is_required":  false,
                    "is_known":  true
                },
                "8":  {
                    "name":  "tlv-onion",
                    "is_required":  true,
                    "is_known":  true
                },
                "12":  {
                    "name":  "static-remote-key",
                    "is_required":  true,
                    "is_known":  true
                },
                "14":  {
                    "name":  "payment-addr",
                    "is_required":  true,
                    "is_known":  true
                },
                "17":  {
                    "name":  "multi-path-payments",
                    "is_required":  false,
                    "is_known":  true
                },
                "23":  {
                    "name":  "anchors-zero-fee-htlc-tx",
                    "is_required":  false,
                    "is_known":  true
                },
                "25":  {
                    "name":  "route-blinding",
                    "is_required":  false,
                    "is_known":  true
                },
                "27":  {
                    "name":  "shutdown-any-segwit",
                    "is_required":  false,
                    "is_known":  true
                },
                "31":  {
                    "name":  "amp",
                    "is_required":  false,
                    "is_known":  true
                },
                "45":  {
                    "name":  "explicit-commitment-type",
                    "is_required":  false,
                    "is_known":  true
                },
                "2023":  {
                    "name":  "script-enforced-lease",
                    "is_required":  false,
                    "is_known":  true
                }
            },
            "errors":  [],
            "flap_count":  0,
            "last_flap_ns":  "0",
            "last_ping_payload":  ""
        }
    ]
}

[Satofan44]

I’ve already connected this and even after connecting a “peer,” the result is still not correct. I’ve already connected three peers, but there’s no change in the result at all.

Code:

C:\lnd>lncli connect 3.33.236.230:9735
[lncli] target address expected in format: pubkey@host:port

C:\lnd>lncli connect 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f@3.33.236.230:9735
{
    "status":  "connection to 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f@3.33.236.230:9735 initiated"
}

This seems to be different from the general case where you need to wait a bit. If you can't connect to peers, there are 2 most likely explanations for this:
1. The peers are actually not reachable, the ones that you are trying to connect to. You can verify this with telnet (don't use ping), on Linux the command is:

Code:

telnet 3.33.236.230:9735

2. Firewall issues preventing you from connecting to that peer, on that port. Check your firewall and see whether you can make connections to the port in question. How to do that will depend a lot on your setup, so I won't leave some more commands here.

This is not applicable for your case yet because 2 of the peers you tried to connect to are shown in your listpeers. I wanted to share that for future reference in case you have intermittent issues.
There is something wrong here. It could be something very specific to your network conditions or an unusual bugged state of the software. Here are some more steps for you to gather information for us.

1. Provide the output of this.

Code:

lncli getinfo

2. Provide the output of this.

Code:

lncli getnetworkinfo

3. Provide the output of this.

Code:

bitcoin-cli getblockchaininfo

4. Please restart LND and Bitcoin Core (start Bitcoin Core before LND), there may be a bugged state in one of them.

5. Try connecting to more peers, look for large nodes. Try 10. See if something changes after a while.

6. If all else fails, it is time to look at logs in detail.

[Satofan44]

Bump