From: Ivan J. <parazyd@dyne•org>
To: libbitcoin@lists•dyne.org
Cc: unsystem@lists•dyne.org, bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] An Electrum server using libbitcoin
Date: Fri, 09 Apr 2021 12:23:27 +0200 [thread overview]
Message-ID: <20210409122327.GA8443@fq> (raw)
Hi.
I've been working on an Electrum server implementation that uses zmq
and libbitcoin as its backend. I wanted to use the Electrum wallet with
my libbitcoin server and this makes it possible now with (unfinished)
libbitcoin v4.
The code is here: https://github.com/parazyd/obelisk
(Yes, it's named Obelisk because of historical reasons :p)
As the Electrum/ElectrumX protocol is getting some new stuff in
protocol version 1.5, I will keep tracking the protocol and implement
it in Obelisk as it comes.
Eventually, the end-goal is to merge Obelisk into Electrum and simply
use libbitcoin public (or self-hosted) servers directly, without
the need of a boilerplate protocol/server between a client and a
daemon. In current Electrum git, this seems relatively simple to do
(and I personally already have done about 70% of it on my local
code repository), but the problem is that it's a breaking change
and replaces the old protocol, which invalidates all old servers
if/when this change happens. However, I don't doubt that removing
the boilerplate and querying a libbitcoin server directly is a bad
idea at all. I'll see if I can make upstream progress on this once
I get feedback.
In general, regarding Obelisk I'd appreciate some feedback, review,
and a bit of help with certain TODOs in the code. The entire codebase
is around 1000 lines of Python 3 with no external dependecies besides
pyzmq.
Thanks,
Ivan
reply other threads:[~2021-04-09 10:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210409122327.GA8443@fq \
--to=parazyd@dyne$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=libbitcoin@lists$(echo .)dyne.org \
--cc=unsystem@lists$(echo .)dyne.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox