đź“… Original date posted:2018-06-14
đź“ť Original message:Resolved -> RTFM
Worked like a champ, first try. Thanks! Wish I had thought to look into that sooner! My c-lightning node’s resource footprint is even smaller now. Unfairly small.
And now that I’ve unexpectedly regained ~180 GB worth of free SSD space from not having that extra full node, I’m feeling wealthy. Accordingly, I’m off to squander my newfound riches over at satoshis’s place. )
> On Jun 13, 2018, at 9:17 AM, Christian Decker <decker.christian at gmail.com> wrote:
>
> 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
Brian Lockhart [ARCHIVE] /
npub13g…tc8wj
2023-06-07 18:13:01
in reply to nevent1q…wxdr
Author Public Key
npub13grlatfmavj4ygzh447mjfje3clgwagmjrd02krd2gh7yjvxr75q9tc8wjSeen on
wss://relay.nostr.bandPublished at
2023-06-07 18:13:01Event JSON
{
"id": "80d107ddbbb4c426c19cb473879e923794559cfebd8f54b30254812c0287aa97",
"pubkey": "8a07fead3beb25522057ad7db926598e3e87751b90daf5586d522fe249861fa8",
"created_at": 1686161581,
"kind": 1,
"tags": [
[
"e",
"c2331da544243a5990bc730e9a7e309d1e4089ae98deca285d0dbc4110aabe22",
"",
"root"
],
[
"e",
"18e28f089e0a638d08676691c6911fd37daa090a410eebd9442de64c52b96a4d",
"",
"reply"
],
[
"p",
"72cd40332ec782dd0a7f63acb03e3b6fdafa6d91bd1b6125cd8b7117a1bb8057"
]
],
"content": "📅 Original date posted:2018-06-14\n📝 Original message:Resolved -\u003e RTFM\n\nWorked like a champ, first try. Thanks! Wish I had thought to look into that sooner! My c-lightning node’s resource footprint is even smaller now. Unfairly small.\n\nAnd now that I’ve unexpectedly regained ~180 GB worth of free SSD space from not having that extra full node, I’m feeling wealthy. Accordingly, I’m off to squander my newfound riches over at satoshis’s place. )\n\n\n\n\u003e On Jun 13, 2018, at 9:17 AM, Christian Decker \u003cdecker.christian at gmail.com\u003e wrote:\n\u003e \n\u003e Brian Lockhart \u003cbrianlockhart at gmail.com\u003e writes:\n\u003e\u003e In the interest of avoiding running multiple bitcoind full nodes - is there\n\u003e\u003e a method to allow a Lightning node to point to / access a separate\n\u003e\u003e already-existing node, vs. requiring it to have its own dedicated local\n\u003e\u003e instance of bitcoind running?\n\u003e\u003e \n\u003e\u003e I.e. if I already have a full bitcoin node running, could I use RPC calls\n\u003e\u003e or something to tell my Lightning node to use that node, instead of\n\u003e\u003e spinning up *another* full node? I’m currently minimizing the network\n\u003e\u003e thrashing by whitelisting my LN bitcoind node to only point to my existing\n\u003e\u003e full node for updates, but if I could just point my whole LN node at it,\n\u003e\u003e that’s save on disk storage etc. etc. etc.\n\u003e \n\u003e Certainly, that's supported by all 3 implementations:\n\u003e \n\u003e - With c-lightning you can either configure `bitcoin-cli` to connect to\n\u003e a remote node with the `rpcconnect`, `rpcuser`, and `rpcpassword`\n\u003e options in the `bitcoin.conf` file (at which point all calls to\n\u003e `bitcoin-cli` will use that node) or you can use the following\n\u003e command line options when starting `lightningd`: `--bitcoin-rpcuser`,\n\u003e `--bitcoin-rpcpassword` and `--bitcoin-rpcconnect`\n\u003e - lnd allows you to specify the node to connect to using the command\n\u003e line options `--bitcoind.rpchost`, `--bitcoind.rpcuser`, and\n\u003e `--bitcoind.rpcpass`.\n\u003e - Eclair requires you to edit the configuration file [1] before\n\u003e compiling afaik\n\u003e \n\u003e Cheers,\n\u003e Christian\n\u003e \n\u003e \n\u003e [1] https://github.com/ACINQ/eclair/blob/master/eclair-core/src/main/resources/reference.conf",
"sig": "3bd87f00773a6bbbdfcd173d0c28a4161aa5cdd610b91e51c33e3073433dc622431e203be8bdbf4cd23dd2452296d097c7e62f052edf0359206ec0a39dff7757"
}