Return-Path: <email@esotericnonsense.com>
Received: from silver.osuosl.org (smtp3.osuosl.org [140.211.166.136])
 by lists.linuxfoundation.org (Postfix) with ESMTP id B9470C087F
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 23 Nov 2019 20:07:40 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by silver.osuosl.org (Postfix) with ESMTP id 9E93220368
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 23 Nov 2019 20:07:40 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from silver.osuosl.org ([127.0.0.1])
 by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id bIcCOYCj717A
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 23 Nov 2019 20:07:39 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
 [66.111.4.27])
 by silver.osuosl.org (Postfix) with ESMTPS id 9AEE1200E5
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 23 Nov 2019 20:07:39 +0000 (UTC)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43])
 by mailout.nyi.internal (Postfix) with ESMTP id 92A19227C4
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 23 Nov 2019 15:07:38 -0500 (EST)
Received: from imap35 ([10.202.2.85])
 by compute3.internal (MEProxy); Sat, 23 Nov 2019 15:07:38 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 esotericnonsense.com; h=mime-version:message-id:in-reply-to
 :references:date:from:to:subject:content-type
 :content-transfer-encoding; s=fm1; bh=ebjftCG8ME4vZENNs6lzRb5nGX
 PiJp4mhvCiUC5/3E4=; b=ivXKl1mEq3Ij8XPa6Z+oDIGS7muUxDjWRrYYtofPPz
 ixujbgvWnkXno9J4uMQGwdl9eY1HgrwIHPxoyLYOM3OO1kOswVx5zHRjCZ/xbPz5
 nuwfNAyC/tIMypsiPUxl0gh6Nai0sXSE+5ODBfU7n/bzE1RIniH8WBW2/wpMfs5B
 dfZBf1qiD+Y9p9l2em2e+79ufd5gPG2ccofK7nv4v1GRmDfjFIeEudsS+otPs+Ex
 URTYVSXSNzdYd7iPDf4jj9y2oLtvoqcO0OE2FdEZnu0neYE8+d7h3JJu7MlTt2pJ
 FUuxBQPqJNH5PHZL4MSbk9ur7iBtO8m0EieK6HfBafTA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender
 :x-sasl-enc; s=fm1; bh=ebjftCG8ME4vZENNs6lzRb5nGXPiJp4mhvCiUC5/3
 E4=; b=o4/IHOIKj8AkgeRlZsZTpiuCO+fh20a//XvHxmWKAZrk9t2OXOFuSnHis
 boPHKqEnnEERihzRVHuGcKpy0JeYulFnAr0xTctPhQf/wpGudCvIrE5GFFC7P2ju
 AZzGfC5o4zdDnd0nml+CRRtPQReRoNj/5bJjT58Q0fLA3UHnHq/Qyt7/GzrDavBk
 CI3YGsZ1hZUXDLscISBTn9jlWbzdsTozclFiFP+tuDTn7RqbQCWIJ/9OupOo6z8c
 fB/x04hGrW1zD/paW00Ukao8VckYDQaV8oxi/0YaNq9TLXNsvUEu60C/GVrEph9X
 VRNQyCCp8ggxB1mA1DNCbuO1GdReA==
X-ME-Sender: <xms:ipHZXZ98RQos2AMCB6zERJf36i506Vsdm3C9kX4Lj6omhueackYS1w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudehiedgudeflecutefuodetggdotefrod
 ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh
 necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd
 enucfjughrpefofgggkfgjfhffhffvufgtgfesthhqredtreerjeenucfhrhhomhepfdff
 rghnihgvlhcugfgughgvtghumhgsvgdfuceovghmrghilhesvghsohhtvghrihgtnhhonh
 hsvghnshgvrdgtohhmqeenucffohhmrghinhepthhhvghrvghgihhsthgvrhdrtghordhu
 khdpvghsohhtvghrihgtnhhonhhsvghnshgvrdgtohhmpdhlihhnuhigfhhouhhnuggrth
 hiohhnrdhorhhgpdgvlhgvtghtrhhonhhrvghlohgtrghtihhonhdrtghomhenucfrrghr
 rghmpehmrghilhhfrhhomhepvghmrghilhesvghsohhtvghrihgtnhhonhhsvghnshgvrd
 gtohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:ipHZXUwJ1ClMhJ5gL3OBPysPKDq4hEpo72xXvwUV9RbaRC53gO9Zpg>
 <xmx:ipHZXfccbZpwUv-6KK9Ds0Sw84G3RIv1nksW8NByUH3r3Yc32_lfFg>
 <xmx:ipHZXYlCYZnmek8udsnxbY3336EIwOSEin1e0lPw3FE7TOaWAYTBVA>
 <xmx:ipHZXTMJQmsaY_vyck6hKPucAe_IPdQOX17TvBv2DE8zRwKZYNsRqw>
Received: by mailuser.nyi.internal (Postfix, from userid 501)
 id 0853914C0073; Sat, 23 Nov 2019 15:07:37 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-578-g826f590-fmstable-20191119v1
Mime-Version: 1.0
Message-Id: <2efb057a-4838-4fca-a24e-432091a63ea9@www.fastmail.com>
In-Reply-To: <CAO7Y_eX2egYNw+h_jDGTYx1R5sC1zrTOXOHuJU4rY66rWKRwAw@mail.gmail.com>
References: <CABCTTz6A_ahH_3VZ1stBP4uoqTTcwQCQ_X1Xywdi33etssCioA@mail.gmail.com>
 <CAO7Y_eX2egYNw+h_jDGTYx1R5sC1zrTOXOHuJU4rY66rWKRwAw@mail.gmail.com>
Date: Sat, 23 Nov 2019 21:07:17 +0100
From: "Daniel Edgecumbe" <email@esotericnonsense.com>
To: "M.K. Safi via bitcoin-dev" <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Sat, 23 Nov 2019 20:13:31 +0000
Subject: Re: [bitcoin-dev] I want to rebuild the GUI in JavaScript
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: Sat, 23 Nov 2019 20:07:40 -0000

You may find my (incomplete) front-end of interest:

https://bitcoin.electronrelocation.com

The live demo is backed by a -disablewallet node, but it was able to acc=
ept payments and send them via QR codes before I stopped development.

The source is available via AGPLv3.

https://git.esotericnonsense.com/pub/bitcoin-top.git

I am unable to continue development due to time constraints.

Daniel Edgecumbe | esotericnonsense
email@esotericnonsense.com | https://esotericnonsense.com

On Sat, Nov 23, 2019, at 17:49, Oscar Lafarga via bitcoin-dev wrote:
> Hi MK,
>=20
> I very much share your interests and curiosities here and actually=20
> don't have an answer on whether it's been tried before.
>=20
> One of the few things I am imagining is that given the security-focuse=
d=20
> nature of the Bitcoin Core software, any vulnerabilities in the way NP=
M=20
> handles the dependencies of the Electron app would be a very high=20
> priority (see=20
> https://www.theregister.co.uk/2016/03/23/npm_left_pad_chaos/)=20
>=20
> In NodeJS-land, my sense is that there is a "move fast and break=20
> things" mentality that may have seeped into some practices that may be=
=20
> considered standard. I have seen some recent developments over the pas=
t=20
> few years to address these kinds of issues such as npm-audit (as of=20=

> Node v6+) but I would recommend doing some thorough research on this=20=

> front to make sure there is a secure dependency management solution in=
=20
> place for such a GUI.
>=20
> Another comment I'd make is that if we consider the GUI as a layer tha=
t=20
> is separate from the protocol layer, this mailing list may not be the=20=

> best place to fully discuss this. However I think if anyone here who=20=

> has been around longer can contribute info on past attempts at this, i=
t=20
> could be quite productive. This could technically exist as an=20
> independent client, but I guess there's a conversation on whether this=
=20
> new Electron UI would ever replace the Qt UI, but since it doesn't=20
> exist yet it could be far too early for that.=20
>=20
> Thanks,
>=20
>=20
>=20
>=20
>=20
>=20
> On Sat, Nov 23, 2019, 2:17 PM M.K. Safi via bitcoin-dev=20
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
> > I=E2=80=99d like to try to rebuild Bitcoin Core GUI using the JavaSc=
ript Electron framework. My goal is to get a real world understanding of=
 the pros and cons of moving from Qt to Electron.
> >=20
> > Before I start, I=E2=80=98d like to know if this has been tried befo=
re or if there are ongoing efforts in this direction by anyone?
> >=20
> > I spent sometime looking into how to implement this. One approach co=
uld be for Electron to drive the UI by running bitcoind and communicatin=
g with it through RPC. But I don=E2=80=99t know if such implementation c=
an achieve feature-parity with the Qt implementation. Qt has the advanta=
ge of direct access to Bitcoin Core code.
> >=20
> > Anyways, I just wanted to share these ideas before going further wit=
h them, so please let me know if you have any information on the above!
> > --=20
> > Sent from my iPhone
> >  _______________________________________________
> >  bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>