:: Re: [unSYSTEM] An Electrum server u…
Top Page
Delete this message
Reply to this message
Author: Amir Taaki
Date:  
To: unsystem
Subject: Re: [unSYSTEM] An Electrum server using libbitcoin
Monero with Triptych reaches an acceptable level of on-chain privacy,
but still weaker than zk.

Complexity of ZK is overstated, mostly by programmers who have bad math
skills.



On 4/15/21 5:01 PM, Alec Spier wrote:
> excited to hear more about DarkFi. Great respect and love to the
> Polytekniks and all of you pushing forward in this list. Would love to
> hear everyones opinion on this, and especially Amir as I've looked
> around online for your explicit opinion in your Twitter / polytech on
> this topic but came up empty handed; I'm curious what you think of
> the dominant crypotnotes in their risk to compromise in respect to both
> chain integrity and de-anonymization long-term compared to
> zk-snarks/starks (I have heard of code complexity considerations with
> the latter and immediate scaling considerations w the former) and
> furthermore whether you see technical merit to the 'Haven' styled xUSD
> xAsset model of Defi.
>  
> Cheers,
> alec
>  
> *Sent:* Friday, April 09, 2021 at 6:34 AM
> *From:* "Amir Taaki" <amir@???>
> *To:* unsystem@???
> *Subject:* Re: [unSYSTEM] An Electrum server using libbitcoin
> Ivan, this is great timely news as we are just about to announce our
> project DarkFi.
>
> We have developed our own custom ZK tooling to write anonymous financial
> contracts.
>
> This is all part of a new ideological vision we are pioneering which
> combines applies democratic confederalism to the economic sphere through
> agorist concepts.
>
> https://wiki.polytech.barcelona/index.php?title=Narrative/Study
> <https://wiki.polytech.barcelona/index.php?title=Narrative/Study>
>
> More info coming soon on this mailing list.
>
> On 4/9/21 12:23 PM, Ivan J. wrote:
>> 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
> <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
>> _______________________________________________
>> unSYSTEM mailing list: http://unsystem.net <http://unsystem.net>
>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/unsystem
> <https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/unsystem>
>>
> _______________________________________________
> unSYSTEM mailing list: http://unsystem.net <http://unsystem.net>
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/unsystem
> <https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/unsystem>
>
> _______________________________________________
> unSYSTEM mailing list: http://unsystem.net
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/unsystem
>