path: root/3d/246fb6bd589aa004c51b9b5f92924942aea1da

Return-Path: <christophera@gmail.com>
Received: from whitealder.osuosl.org (smtp1.osuosl.org [140.211.166.138])
 by lists.linuxfoundation.org (Postfix) with ESMTP id E5C06C07FF;
 Sun, 17 May 2020 09:12:11 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by whitealder.osuosl.org (Postfix) with ESMTP id CE1E188106;
 Sun, 17 May 2020 09:12:11 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from whitealder.osuosl.org ([127.0.0.1])
 by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id MpBoE1bkyxD3; Sun, 17 May 2020 09:12:11 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-vk1-f172.google.com (mail-vk1-f172.google.com
 [209.85.221.172])
 by whitealder.osuosl.org (Postfix) with ESMTPS id C81E8880F6;
 Sun, 17 May 2020 09:12:10 +0000 (UTC)
Received: by mail-vk1-f172.google.com with SMTP id p7so1674665vkf.5;
 Sun, 17 May 2020 02:12:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=lifewithalacrity-com.20150623.gappssmtp.com; s=20150623;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc; bh=hyBgKrvIL4L2gstXRV6lVIuaqnyLIVgIiQd20RwXBi0=;
 b=CgiMpD68y5++EFMqOJzyImbqJziDMoyrbPx0RAg0nYT4B1r1TBKVuMQK+4YB973JD+
 2EMpFjH4V7Q6nqsrUSMEY9edxM6xayqu3pfbI8BBi1HJB6dHvf8l+WyGI2AgJeWHbSnY
 03E5FIU3TfDzWnh3eQJr1r+sYMKHAEXc9BB/xSl7Ovug/wCpDMYL/lQTfoNrMBu0Pjug
 b+sQmLpH7ZMlSetJgAsIa702GIkiPlCfruMEvVgIYPVuGxNt4XcA2m/udVUH24itA0Tx
 F3JwCjlPaika+NdgDgLs8PMV3QoL36RyI6pjXWkyjgSL4IQ8h4VA6Hk32iTc3G2+7V1h
 JQww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=hyBgKrvIL4L2gstXRV6lVIuaqnyLIVgIiQd20RwXBi0=;
 b=BesyZoFdutQK15DhBOvvLmwQJFVgBYxKw3W0Y5ZcVpFTmBlJ+TYZGA7Dk70G7vSq/z
 K1n6aaZgTLVov+eaLKO4IZxRZQNpGIMBJ+7q0xJWp48nbKTa+rCeMK80Sad9NuGZtVqR
 eNBc0C5dvdI5r3PIYGjz3XaYSaAStmF7CXuqEcvyH32VE7fzT3qz9q0S5dvwbLuKU/ED
 QzkmYMIZ1e5Ey5yasUEWqK5xW7KVqkBJio7poyX/70iYaJgvcHwat7N+YNFb1Xolhtb+
 oLeIKKHO+5H7B3QH/36y5VZVPgmnhsp5UvPF8f0JL91u/qxjUAhdtcitUGQIzQuuAS/e
 3mFQ==
X-Gm-Message-State: AOAM53093DwwJ3R0nvi20X0JBgCrdNkrr7Pg8/9tPubYaRa/E40l4pQz
 Wcye3aIOwDVSF3yNxaPCinz6FRBBiPMHgSMVzsI=
X-Google-Smtp-Source: ABdhPJwuXfaUd0rJRN1On4QnxNbQuegYZHySxNjGmkI1R885jXYtpM4q0MFVSxR7IQvIuyBz+xTO2FgHRRquJWXUi/c=
X-Received: by 2002:a1f:1f52:: with SMTP id f79mr7673456vkf.63.1589706729629; 
 Sun, 17 May 2020 02:12:09 -0700 (PDT)
MIME-Version: 1.0
References: <CALZpt+GBPbf+Pgctm5NViNons50aQs1RPQkEo3FW5RM4fL9ztA@mail.gmail.com>
 <202005051300.38836.luke@dashjr.org>
 <CAH5Bsr27rN1SE166ON_q49=MNti0v7Vyn6s6T5R3=LC69K2QdQ@mail.gmail.com>
 <6883e35a-e584-523f-d6f9-cf9ce2cca66d@riseup.net>
 <CALZpt+G8SzeX4U-VBhEZqQ0ApwAs_jKkKe7aeZEQZ5KcJaMjCg@mail.gmail.com>
 <uOUyhfZ-Ti4E4sQn_Cap6Em_pqVc-p2INXoBLIEKsiOWpWKT-WNeqUge902E-HU0wWWWo4onr8UQTNKg5YmVkUWfrlNVJkkMSWYCnoj2WVY=@protonmail.com>
 <45FD4FF1-1E09-4748-8B05-478DEF6C1966@ed.ac.uk>
 <CALeFGL1ZNrXBB31SScgP3BvKsiTDF-DSDj6Wf-QbPJc6E8t3iQ@mail.gmail.com>
In-Reply-To: <CALeFGL1ZNrXBB31SScgP3BvKsiTDF-DSDj6Wf-QbPJc6E8t3iQ@mail.gmail.com>
From: Christopher Allen <ChristopherA@lifewithalacrity.com>
Date: Sun, 17 May 2020 02:11:33 -0700
Message-ID: <CACrqygDiUE7_yb3_MVoaLmOYe0n2wPPVaX1OZEnGBpbyZiJQkQ@mail.gmail.com>
To: Keagan McClelland <keagan.mcclelland@gmail.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000eaac0005a5d470c2"
X-Mailman-Approved-At: Sun, 17 May 2020 11:41:48 +0000
Cc: Orfeas Stefanos Thyfronitis Litos <o.thyfronitis@ed.ac.uk>,
 "lightning-dev\\\\\\\\@lists.linuxfoundation.org"
 <lightning-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Lightning-dev] On the scalability issues of
 onboarding millions of LN mobile clients
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
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: Sun, 17 May 2020 09:12:12 -0000

--000000000000eaac0005a5d470c2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, May 14, 2020 at 8:30 AM Keagan McClelland via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> > It should be therefore a top priority to make the UX of connecting my
> mobile LN client to my home full node extremely easy, so that centralised
> services can't improve much on that step. Especially if I already run a
> full node.
>

There already is an emerging approach for this, called QuickConnect
https://github.com/BlockchainCommons/Bitcoin-Standup/blob/master/Docs/Quick=
-Connect-API.md

It is currently offered by BitcoinStandup (both Mac and Linux),
BTCPayServer, Nodl, MyNode, RaspiBlitz full node tools and hardware, and is
used currently by FullyNoded, FullyNoded2, and a couple of other
experimental apps to allow secure connection via Tor v3 from a remote to
your own personal full node.

We know that QuickConnect needs another major iteration and welcome
contributions to requirements and/or proposals for the next version.

We invite you to share your thoughts here.
https://github.com/BlockchainCommons/Bitcoin-Standup/issues/66

=E2=80=94 Christopher Allen

--000000000000eaac0005a5d470c2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Thu, May 14, 2020 at 8:30 AM Keaga=
n McClelland via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxf=
oundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&=
gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div =
dir=3D"ltr"><div>&gt; It should be therefore a top priority to make the UX =
of connecting my=20
mobile LN client to my home full node extremely easy, so that=20
centralised services can&#39;t improve much on that step. Especially if I=
=20
already run a full node.</div></div></blockquote><div><br></div><div><font =
face=3D"arial, sans-serif">There already is an emerging approach for this, =
called QuickConnect <a href=3D"https://github.com/BlockchainCommons/Bitcoin=
-Standup/blob/master/Docs/Quick-Connect-API.md" target=3D"_blank">https://g=
ithub.com/BlockchainCommons/Bitcoin-Standup/blob/master/Docs/Quick-Connect-=
API.md</a></font></div><div><font face=3D"arial, sans-serif"><br></font></d=
iv><div><font face=3D"arial, sans-serif">It is currently offered by Bitcoin=
Standup (both Mac and Linux), BTCPayServer, Nodl, MyNode, RaspiBlitz full n=
ode tools and hardware, and is used currently by FullyNoded, FullyNoded2, a=
nd a couple of other experimental apps to allow secure connection via Tor v=
3 from a remote to your own personal full node.=C2=A0</font></div><div><fon=
t face=3D"arial, sans-serif"><br></font></div><div><font face=3D"arial, san=
s-serif">We know that QuickConnect needs another major iteration and welcom=
e contributions to requirements and/or proposals for the next version.</fon=
t></div><div><font face=3D"arial, sans-serif"><br></font></div><div><font f=
ace=3D"arial, sans-serif"><span style=3D"color:rgb(36,41,46)">We invite you=
 to share your thoughts here.=C2=A0</span><a href=3D"https://github.com/Blo=
ckchainCommons/Bitcoin-Standup/issues/66" target=3D"_blank">https://github.=
com/BlockchainCommons/Bitcoin-Standup/issues/66</a></font></div><div><br></=
div><div>=E2=80=94 Christopher Allen</div></div></div>

--000000000000eaac0005a5d470c2--