📅 Original date posted:2018-06-13
📝 Original message:Brian Lockhart <brianlockhart at gmail.com> writes:
> In the interest of avoiding running multiple bitcoind full nodes - is there
> a method to allow a Lightning node to point to / access a separate
> already-existing node, vs. requiring it to have its own dedicated local
> instance of bitcoind running?
>
> I.e. if I already have a full bitcoin node running, could I use RPC calls
> or something to tell my Lightning node to use that node, instead of
> spinning up *another* full node? I’m currently minimizing the network
> thrashing by whitelisting my LN bitcoind node to only point to my existing
> full node for updates, but if I could just point my whole LN node at it,
> that’s save on disk storage etc. etc. etc.
Certainly, that's supported by all 3 implementations:
- With c-lightning you can either configure `bitcoin-cli` to connect to
a remote node with the `rpcconnect`, `rpcuser`, and `rpcpassword`
options in the `bitcoin.conf` file (at which point all calls to
`bitcoin-cli` will use that node) or you can use the following
command line options when starting `lightningd`: `--bitcoin-rpcuser`,
`--bitcoin-rpcpassword` and `--bitcoin-rpcconnect`
- lnd allows you to specify the node to connect to using the command
line options `--bitcoind.rpchost`, `--bitcoind.rpcuser`, and
`--bitcoind.rpcpass`.
- Eclair requires you to edit the configuration file [1] before
compiling afaik
Cheers,
Christian
[1] https://github.com/ACINQ/eclair/blob/master/eclair-core/src/main/resources/reference.conf
Christian Decker [ARCHIVE] /
npub1wt…gtuyn
2023-06-07 18:13:01
in reply to nevent1q…eawf
Author Public Key
npub1wtx5qvewc7pd6znlvwktq03mdld05mv3h5dkzfwd3dc30gdmsptsugtuynPublished at
2023-06-07 18:13:01Event JSON
{
"id": "18e28f089e0a638d08676691c6911fd37daa090a410eebd9442de64c52b96a4d",
"pubkey": "72cd40332ec782dd0a7f63acb03e3b6fdafa6d91bd1b6125cd8b7117a1bb8057",
"created_at": 1686161581,
"kind": 1,
"tags": [
[
"e",
"c2331da544243a5990bc730e9a7e309d1e4089ae98deca285d0dbc4110aabe22",
"",
"root"
],
[
"e",
"88dedb9031974eb5e6a0b0f6d8ce8b72191e5331b587f16f448ed56c72239a58",
"",
"reply"
],
[
"p",
"8a07fead3beb25522057ad7db926598e3e87751b90daf5586d522fe249861fa8"
]
],
"content": "📅 Original date posted:2018-06-13\n📝 Original message:Brian Lockhart \u003cbrianlockhart at gmail.com\u003e writes:\n\u003e In the interest of avoiding running multiple bitcoind full nodes - is there\n\u003e a method to allow a Lightning node to point to / access a separate\n\u003e already-existing node, vs. requiring it to have its own dedicated local\n\u003e instance of bitcoind running?\n\u003e\n\u003e I.e. if I already have a full bitcoin node running, could I use RPC calls\n\u003e or something to tell my Lightning node to use that node, instead of\n\u003e spinning up *another* full node? I’m currently minimizing the network\n\u003e thrashing by whitelisting my LN bitcoind node to only point to my existing\n\u003e full node for updates, but if I could just point my whole LN node at it,\n\u003e that’s save on disk storage etc. etc. etc.\n\nCertainly, that's supported by all 3 implementations:\n\n - With c-lightning you can either configure `bitcoin-cli` to connect to\n a remote node with the `rpcconnect`, `rpcuser`, and `rpcpassword`\n options in the `bitcoin.conf` file (at which point all calls to\n `bitcoin-cli` will use that node) or you can use the following\n command line options when starting `lightningd`: `--bitcoin-rpcuser`,\n `--bitcoin-rpcpassword` and `--bitcoin-rpcconnect`\n - lnd allows you to specify the node to connect to using the command\n line options `--bitcoind.rpchost`, `--bitcoind.rpcuser`, and\n `--bitcoind.rpcpass`.\n - Eclair requires you to edit the configuration file [1] before\n compiling afaik\n\nCheers,\nChristian\n\n\n[1] https://github.com/ACINQ/eclair/blob/master/eclair-core/src/main/resources/reference.conf",
"sig": "7bd86f5a471f6908cb0adf1184009e882d4065ea23bfc850c7a3a4172a53c1d81bdae9c4534f9b912b7b434341407ef73374841f9a2feab568b74c7e2988fbf0"
}