From: Christian Decker <decker.christian@gmail•com>
To: Brian Lockhart <brianlockhart@gmail•com>,
Kulpreet Singh <zapfmann@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Patrick Shirkey <pshirkey@boosthardware•com>
Subject: Re: [bitcoin-dev] Why not archive the backend of Bitcoin blockchain?
Date: Wed, 13 Jun 2018 18:17:20 +0200 [thread overview]
Message-ID: <87h8m68xv3.fsf@gmail.com> (raw)
In-Reply-To: <CAJQ0i9v0T8w4LD13z9AePtgnMdiG7=1pjMFWVXTnCFRVB1bwpw@mail.gmail.com>
Brian Lockhart <brianlockhart@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
next prev parent reply other threads:[~2018-06-13 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 0:56 Segue
2018-05-10 6:48 ` アルム カールヨハン
2018-05-10 7:54 ` ZmnSCPxj
2018-05-10 6:50 ` Jim Posen
2018-05-10 10:52 ` Patrick Shirkey
2018-06-12 8:40 ` Kulpreet Singh
2018-06-13 13:33 ` Christian Decker
2018-06-13 15:32 ` Brian Lockhart
2018-06-13 16:17 ` Christian Decker [this message]
2018-06-14 23:24 ` Brian Lockhart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8m68xv3.fsf@gmail.com \
--to=decker.christian@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=brianlockhart@gmail$(echo .)com \
--cc=pshirkey@boosthardware$(echo .)com \
--cc=zapfmann@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox