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 47FF9FA7 for ; 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 ; Wed, 13 Jun 2018 16:17:33 +0000 (UTC) Received: by mail-wm0-f43.google.com with SMTP id n5-v6so6483700wmc.5 for ; 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 To: Brian Lockhart , Kulpreet Singh , Bitcoin Protocol Discussion , Patrick Shirkey In-Reply-To: References: <0cc0a7249708ad26a7cbef702370b234.squirrel@boosthardware.com> <87fu1qdd5e.fsf@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 16:17:36 -0000 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? > > 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