141 lines
5.2 KiB
HTML
141 lines
5.2 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<HTML>
|
|
<HEAD>
|
|
<TITLE> [ZcF-general] Dec/Jan update on implementing anonymous payment channels
|
|
</TITLE>
|
|
<LINK REL="Index" HREF="/pipermail/general/2019/index.html" >
|
|
<LINK REL="made" HREF="mailto:general%40lists.zfnd.org?Subject=Re%3A%20%5BZcF-general%5D%20Dec/Jan%20update%20on%20implementing%20anonymous%20payment%0A%20channels&In-Reply-To=%3CCAJVTvHuSEvkOteSk5VoNoWDRkV6mJBAbzm2M-bPKWdR5u1dc5A%40mail.gmail.com%3E">
|
|
<META NAME="robots" CONTENT="index,nofollow">
|
|
<style type="text/css">
|
|
pre {
|
|
white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */
|
|
}
|
|
</style>
|
|
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
|
<LINK REL="Previous" HREF="000043.html">
|
|
<LINK REL="Next" HREF="000045.html">
|
|
</HEAD>
|
|
<BODY BGCOLOR="#ffffff">
|
|
<H1>[ZcF-general] Dec/Jan update on implementing anonymous payment channels</H1>
|
|
<B>J. Ayo Akinyele</B>
|
|
<A HREF="mailto:general%40lists.zfnd.org?Subject=Re%3A%20%5BZcF-general%5D%20Dec/Jan%20update%20on%20implementing%20anonymous%20payment%0A%20channels&In-Reply-To=%3CCAJVTvHuSEvkOteSk5VoNoWDRkV6mJBAbzm2M-bPKWdR5u1dc5A%40mail.gmail.com%3E"
|
|
TITLE="[ZcF-general] Dec/Jan update on implementing anonymous payment channels">ayo at boltlabs.io
|
|
</A><BR>
|
|
<I>Fri Feb 1 17:21:52 EST 2019</I>
|
|
<P><UL>
|
|
<LI>Previous message (by thread): <A HREF="000043.html">[ZcF-general] Update Benedikt Bünz Scholarship Grant
|
|
</A></li>
|
|
<LI>Next message (by thread): <A HREF="000045.html">[ZcF-general] Riemann status update
|
|
</A></li>
|
|
<LI> <B>Messages sorted by:</B>
|
|
<a href="date.html#44">[ date ]</a>
|
|
<a href="thread.html#44">[ thread ]</a>
|
|
<a href="subject.html#44">[ subject ]</a>
|
|
<a href="author.html#44">[ author ]</a>
|
|
</LI>
|
|
</UL>
|
|
<HR>
|
|
<!--beginarticle-->
|
|
<PRE>J. Ayo Akinyele
|
|
|
|
Progress as of January 31, 2019
|
|
|
|
|
|
Dear All,
|
|
|
|
|
|
Over the last few months, we’ve been working on understanding the different
|
|
approaches for implementing Bolt payment channels on top of Zcash and the
|
|
changes necessary in Zcash to support the privacy goals in Bolt. This has
|
|
been joint work with Colleen Swanson, Ian Miers, and Matthew Green.
|
|
|
|
|
|
We have been working on an initial specification on the different
|
|
approaches to implementing Bolt on top of Zcash and setting up the private
|
|
testnet infrastructure for node development on AWS:
|
|
|
|
|
|
*Summary of the initial specification.* It defines three general approaches
|
|
which can be categorized as follows:
|
|
|
|
|
|
(1) *T-addr and Bitcoin-style scripts.* This approach follows the baseline
|
|
solution described in the original Bolt paper. This approach exposes the
|
|
initial and final balances but potentially interoperates with LN. Requires
|
|
a few opcodes to be added to Zcash: OP_CSV (for relative locktime),
|
|
OP_BOLT* (for opening and closing channels) and a way to ensure transaction
|
|
non-malleability for the funding transaction on the channel opening.
|
|
|
|
|
|
(2) *Z-addr & T-addr with Bitcoin-style scripts.* This approach allows us
|
|
to hide the initial/final balance of each party in the channel. Relies on
|
|
multi-sig address with T-addrs, and requires OP_CSV/OP_BOLT* opcodes for
|
|
channel ops. Also may require a way to ensure transaction non-malleability.
|
|
|
|
|
|
(3) *Z-addr and scriptless scripts.* Simplifies the implementation and
|
|
provides maximal privacy. Bolt channel operations will be hidden from the
|
|
network and would not require any special opcodes. That is, the Bolt
|
|
conditions will be encoded in the signatures attached to the funding
|
|
transaction and closing transaction. This approach is currently under
|
|
specified and remains a work-in-progress.
|
|
|
|
|
|
For private multi-hop payments, we are evaluating multiple approaches: (1)
|
|
HTLCs via LN with Bolt used at the first and last hop of the path, (2)
|
|
Increased privacy for hops in the middle using multi-hop locks as described
|
|
here, and (3) Interledger approach via packetized payments. Each approach
|
|
has its pros and cons in terms of possible attacks and risks to end users.
|
|
|
|
|
|
*Private Testnet for Bolt development.* Setting up a public/private testnet
|
|
on AWS for Bolt development. And forked current version of Zcash to
|
|
prototype the necessary changes for Zcash.
|
|
|
|
|
|
Now currently working on the initial proof of concept Bolt node
|
|
implementation (approach #2 in spec) using libbolt that provides direct
|
|
channels on a private testnet. This version will initially implement
|
|
unilateral closing by the customer and provide mutual closing via specified
|
|
channel durations.
|
|
|
|
Best,
|
|
Ayo
|
|
</PRE>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<!--endarticle-->
|
|
<HR>
|
|
<P><UL>
|
|
<!--threads-->
|
|
<LI>Previous message (by thread): <A HREF="000043.html">[ZcF-general] Update Benedikt Bünz Scholarship Grant
|
|
</A></li>
|
|
<LI>Next message (by thread): <A HREF="000045.html">[ZcF-general] Riemann status update
|
|
</A></li>
|
|
<LI> <B>Messages sorted by:</B>
|
|
<a href="date.html#44">[ date ]</a>
|
|
<a href="thread.html#44">[ thread ]</a>
|
|
<a href="subject.html#44">[ subject ]</a>
|
|
<a href="author.html#44">[ author ]</a>
|
|
</LI>
|
|
</UL>
|
|
|
|
<hr>
|
|
<a href="/mailman/listinfo/general">More information about the general
|
|
mailing list</a><br>
|
|
</body></html>
|