From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 67049CE0 for ; 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 ; Thu, 14 Jun 2018 23:24:36 +0000 (UTC) Received: by mail-pl0-f51.google.com with SMTP id a7-v6so4358192plp.3 for ; 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 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: References: <0cc0a7249708ad26a7cbef702370b234.squirrel@boosthardware.com> <87fu1qdd5e.fsf@gmail.com> <87h8m68xv3.fsf@gmail.com> To: Christian Decker 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 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 = wrote: >=20 > Brian Lockhart 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