From: Brian Lockhart <brianlockhart@gmail•com>
To: Christian Decker <decker.christian@gmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Why not archive the backend of Bitcoin blockchain?
Date: Thu, 14 Jun 2018 16:24:33 -0700 [thread overview]
Message-ID: <C99E9D96-3930-4F2B-B373-524A45370BAD@gmail.com> (raw)
In-Reply-To: <87h8m68xv3.fsf@gmail.com>
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@gmail•com> wrote:
>
> 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
prev parent reply other threads:[~2018-06-14 23:24 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
2018-06-14 23:24 ` Brian Lockhart [this message]
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=C99E9D96-3930-4F2B-B373-524A45370BAD@gmail.com \
--to=brianlockhart@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=decker.christian@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