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
|
Return-Path: <decker.christian@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 47FF9FA7
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 13 Jun 2018 16:17:36 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 06A215C2
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 13 Jun 2018 16:17:33 +0000 (UTC)
Received: by mail-wm0-f43.google.com with SMTP id n5-v6so6483700wmc.5
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 13 Jun 2018 09:17:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=from:to:subject:in-reply-to:references:date:message-id:mime-version
:content-transfer-encoding;
bh=Lov+4lNN8F2xd9kI7NWB7MUM8i6b0Pq/+o8xJB1DvXg=;
b=TRYGWl2em4RRn9rqtNRBLA1/2PZYg8sZOKdICaCrhCKnCIxSjHV1OTP1KMkZekOFhq
wS0eJCTp5CAbHeeYpH2PHVWwp/z4VsQt/0aZiN5GsQgQyHUPzytS+MOigU8yjWQOF9QT
Sa+mwjI00Bu28z1agEYMaQa8r0BuSH9VSfa4U1LKtIy+BPY7aQwngOj1eW6Ms/6g7V/v
QA7g8qw/LuyoHVm0eLyqLDJKFIxMem93/u7h1yG7f0zWVTXSjsT8tauDF2EFsDjQy9VG
VXe0b5vn66OoMBSgpolXRnUHA++U5wvZwa9khBMjqAn8WEnlps7nM+MKGO2iakrEsZ+o
1mhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:from:to:subject:in-reply-to:references:date
:message-id:mime-version:content-transfer-encoding;
bh=Lov+4lNN8F2xd9kI7NWB7MUM8i6b0Pq/+o8xJB1DvXg=;
b=q40M15bnJf2mH4wjm5TxN+SXPyWVGllFjgyyUy6DxHdvpW/jaM9kxCgjjZeC6U7IMU
Z4ShGWWNv/Dla/ON80hXChorexeElsSz8KU58LhZPjLJBpHM/JUA3VdLBVg/JBstYU3g
OkyP+l/0u5+MrOFZClEuAclyIUZF3MjXUQqEDq5kElVkAjSKMUDAqySuzDTA8kK+Ih0d
edMkRYKHAgoSY7PheDsTBiXe46NRz89o8Aq01YfoQVIqclMi4IQqKNcITKlbZCoPFNcZ
lr4l+0c4LYyONLQkx+2O2MslCZD4ugIvFhsncncqsdImIav7UkfvmFoFj46v36Tq+QcQ
YcbA==
X-Gm-Message-State: APt69E1WYZB8HGmHmwCzTCTv8uB48JuMNdDaY6ow7h1iTxESgnSM5EJm
wqwzI++hg+kfX7QdtOQxNII=
X-Google-Smtp-Source: ADUXVKJkK6scPO5yfbnPi1uSg3mmve296ZUu7horXHFbgN5k2f5g8C96PG2IPoaVEP8AKpbRxQ6V6g==
X-Received: by 2002:a1c:7501:: with SMTP id
o1-v6mr4160343wmc.133.1528906652581;
Wed, 13 Jun 2018 09:17:32 -0700 (PDT)
Received: from localhost ([2a02:aa16:1102:5480:e99:3f63:40a2:83e9])
by smtp.gmail.com with ESMTPSA id
s3-v6sm2102761wrp.76.2018.06.13.09.17.30
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Wed, 13 Jun 2018 09:17:30 -0700 (PDT)
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>
In-Reply-To: <CAJQ0i9v0T8w4LD13z9AePtgnMdiG7=1pjMFWVXTnCFRVB1bwpw@mail.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>
Date: Wed, 13 Jun 2018 18:17:20 +0200
Message-ID: <87h8m68xv3.fsf@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
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
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: Wed, 13 Jun 2018 16:17:36 -0000
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?
>
> 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 existing
> 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.
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/resour=
ces/reference.conf
|
