mailman-lists-archive/pipermail/general/2019/000075.html

81 lines
4.3 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE> [ZcF-general] March Update
</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%20March%20Update&In-Reply-To=%3Ca8f4cee2-4481-186d-1310-e950b69c7f61%40gmu.edu%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="000074.html">
<LINK REL="Next" HREF="000076.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[ZcF-general] March Update</H1>
<B>Samuel D Gordon</B>
<A HREF="mailto:general%40lists.zfnd.org?Subject=Re%3A%20%5BZcF-general%5D%20March%20Update&In-Reply-To=%3Ca8f4cee2-4481-186d-1310-e950b69c7f61%40gmu.edu%3E"
TITLE="[ZcF-general] March Update">gordon at gmu.edu
</A><BR>
<I>Fri Apr 19 02:13:03 EDT 2019</I>
<P><UL>
<LI>Previous message (by thread): <A HREF="000074.html">[ZcF-general] Open Invitation &#8212; Zcash Protocol Discussion
</A></li>
<LI>Next message (by thread): <A HREF="000076.html">[ZcF-general] March &amp; April Update: implementing anonymous payment channels
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#75">[ date ]</a>
<a href="thread.html#75">[ thread ]</a>
<a href="subject.html#75">[ subject ]</a>
<a href="author.html#75">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>March Update:
We thought about the meaning of our security definition, based in part upon this comment by Ian Miers&lt;<A HREF="https://github.com/ZcashFoundation/GrantProposals-2018Q2/issues/36#issuecomment-393334620">https://github.com/ZcashFoundation/GrantProposals-2018Q2/issues/36#issuecomment-393334620</A>&gt;. Our thinking is that the strength of our system depends almost entirely on the size of the mix-in that we can support. Of course, if my mix-in is small enough that, later, nobody else in my mix-in spends in the same shops that I spend in, the security is greatly reduced. Similarly, if only a few thousand zcash keys are shielding, then even if you use a ZKP to &#8220;mix-in&#8221; the entire set, your anonymity is only as good as the size of your mix-in. And, to take the opposite extreme, if our protocol is efficient enough to support mixing a very large fraction of the entire network, this would be similar to using a ZKP to prove that a large fraction of the network could have made some payment. Our hope is that we can support a large enough mix-in to claim something comparable to other systems.
Unfortunately, though, our initial findings indicate that the amount of noise required might be a deal killer when building a system that simultaneously achieves strong anonymity and cheap payments. We plan to try a few things to move forward:
* We are going to see what we can do to lower the noise, either by changing the protocol, or by changing the noise distribution.
* We&#8217;re going to see whether our \sqrt(n) variant gives something useful. (So far, we don&#8217;t think so though.)
* We&#8217;re going to see if our construction at least allows us to claim some asymptotic improvement over naive mixing alternatives.
* We will estimate the exact noise requirements for small sizes of mix-ins, i.e., n=50, as traditionally estimated in some related work (e.g. Dicemix)
Dov, Foteini, Mayank
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message (by thread): <A HREF="000074.html">[ZcF-general] Open Invitation &#8212; Zcash Protocol Discussion
</A></li>
<LI>Next message (by thread): <A HREF="000076.html">[ZcF-general] March &amp; April Update: implementing anonymous payment channels
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#75">[ date ]</a>
<a href="thread.html#75">[ thread ]</a>
<a href="subject.html#75">[ subject ]</a>
<a href="author.html#75">[ author ]</a>
</LI>
</UL>
<hr>
<a href="/mailman/listinfo/general">More information about the general
mailing list</a><br>
</body></html>