Brian Lockhart <brianlockh...@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 _______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
