1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
|
Return-Path: <brianlockhart@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 67049CE0
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 14 Jun 2018 23:24:36 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pl0-f51.google.com (mail-pl0-f51.google.com
[209.85.160.51])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 125F45C2
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 14 Jun 2018 23:24:36 +0000 (UTC)
Received: by mail-pl0-f51.google.com with SMTP id a7-v6so4358192plp.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 14 Jun 2018 16:24:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:subject:from:in-reply-to:date:cc
:content-transfer-encoding:message-id:references:to;
bh=gNQc66MxLO5HJ2GuQJP8wYyInZJd8b2T1pbXOBsSoB0=;
b=W7Q6YTTLdsXpLvmVd3JmKPnQrJjZbalcpmN6kUThgU11wt4+F8YAOWgPWuPCSq19My
QQ1f52tztrFRglwBZQn7al8mdX/SAN+WjLff9SEiYAjnBUZLpb9gV3byduAZWkwOTiMr
YXkzY3c1SRxiTOjTZA7Urf6KqpoGqJ6GSSVJ/vT6CtZpjQfZtp/dzDw9s7QFI0Au1dpm
MdQtZrOkzvUibQj1+PVx+6dWJAPsawDr2KwyEVAMBd/NJvrdLPfNR36uWLmg9Rj4ynId
AtB0u3h1y608HRymBEMHG9aCx6krPEBn6zhwz05NMpxO6inhCzjEu9Mz25aT2PLH3Ewk
7vIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc
:content-transfer-encoding:message-id:references:to;
bh=gNQc66MxLO5HJ2GuQJP8wYyInZJd8b2T1pbXOBsSoB0=;
b=mKBOailh3yGOrWu1bGpZLTTtH6C1MYsM6qOJK8Fc9TK0E3u5lXVtPNfZhuRPWSVAxp
veHMDXxcbqvzu0Vna1XPZ6SnN0nPabTvpRTgjO2Gwf4f8znOZNn22mOX7XjYv0CJrgj8
dapI7dhSWwAZwhATlojKXDaHXrL3mtVSQgZT9pTFzpxJNYPvcdzfq03FMYdbp2WAuaPE
+p7X1UnD6FBGbxH4nAfGjzSGUnM6bppTJiYoPps4BH4UrpYT4UqYFjNwhPlzSxl/F464
tVRq588kbK/Nr1mKjIbOrNLRXfd0lYDM9wTHmYYII8huEwzithdqrq/x8ud/BRLsOAZy
B/wA==
X-Gm-Message-State: APt69E0COc5hD9QxWJfyyVmza9KthNg+uekTHGn7aIruFK1IuVwpYvGI
PKZ5pQWZHMtY6PagISSwhGowtAvq
X-Google-Smtp-Source: ADUXVKLXp6TgMq+qGEyci1RMLs7VV7si6dt6znuINfpRxLsezs3qzwdiundSDr3psmY5yvIbl5ylAw==
X-Received: by 2002:a17:902:24e:: with SMTP id
72-v6mr5127512plc.87.1529018675313;
Thu, 14 Jun 2018 16:24:35 -0700 (PDT)
Received: from ?IPv6:2600:380:8050:b98c:1430:42e6:179e:a561?
([2600:380:8050:b98c:1430:42e6:179e:a561])
by smtp.gmail.com with ESMTPSA id
s75-v6sm15911102pfj.125.2018.06.14.16.24.34
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Thu, 14 Jun 2018 16:24:34 -0700 (PDT)
Content-Type: text/plain;
charset=utf-8
Mime-Version: 1.0 (1.0)
From: Brian Lockhart <brianlockhart@gmail.com>
X-Mailer: iPhone Mail (15F79)
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>
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, MIME_QP_LONG_LINE,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 14 Jun 2018 23:26:27 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Why not archive the backend of Bitcoin blockchain?
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2018 23:24:36 -0000
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
|
