Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (1.0)
From: Brian Lockhart <brianlockhart@gmail.com>
In-Reply-To: <87h8m68xv3.fsf@gmail.com>
Date: Thu, 14 Jun 2018 16:24:33 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C99E9D96-3930-4F2B-B373-524A45370BAD@gmail.com>
References: <fd403450-cf7f-ce56-79ca-93c77c042289@frankentrikes.com>
	<0cc0a7249708ad26a7cbef702370b234.squirrel@boosthardware.com>
	<CAN8S4uarZ39BqpmZQqqoof6nDXH7eSuH1rT03ABX2x-Gzc9sXg@mail.gmail.com>
	<87fu1qdd5e.fsf@gmail.com>
	<CAJQ0i9v0T8w4LD13z9AePtgnMdiG7=1pjMFWVXTnCFRVB1bwpw@mail.gmail.com>
	<87h8m68xv3.fsf@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?
Precedence: list

Resolved -> RTFM

Worked like a champ, first try. Thanks! Wish I had thought to look into that=
 sooner! My c-lightning node=E2=80=99s resource footprint is even smaller no=
w. Unfairly small.

And now that I=E2=80=99ve unexpectedly regained ~180 GB worth of free SSD sp=
ace from not having that extra full node, I=E2=80=99m feeling wealthy. Accor=
dingly, I=E2=80=99m off to squander my newfound riches over at satoshis=E2=80=
=99s place. )



> On Jun 13, 2018, at 9:17 AM, Christian Decker <decker.christian@gmail.com>=
 wrote:
>=20
> Brian Lockhart <brianlockhart@gmail.com> writes:
>> In the interest of avoiding running multiple bitcoind full nodes - is the=
re
>> 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?
>>=20
>> 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=E2=80=99m currently minimizing the net=
work
>> thrashing by whitelisting my LN bitcoind node to only point to my existin=
g
>> full node for updates, but if I could just point my whole LN node at it,
>> that=E2=80=99s save on disk storage etc. etc. etc.
>=20
> Certainly, that's supported by all 3 implementations:
>=20
> - 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
>=20
> Cheers,
> Christian
>=20
>=20
> [1] https://github.com/ACINQ/eclair/blob/master/eclair-core/src/main/resou=
rces/reference.conf