@ -27,8 +27,8 @@ really stood out to me recently and I want to share it and discuss it with
the wider "actual" privacy coin community.
</p>
<center>
<ahref=""target=_blank>
<imgwidth=80%src="">
<ahref="zcash-issue.png"target=_blank>
<imgwidth=80%src="zcash-issue.png">
</a>
</center>
@ -42,7 +42,12 @@ The above image shows eight possible "privacy policies", where only one of them
</p>
<pre>
I'm concerned about the practical feasibility of implementing a usable full-node wallet with this API. Short of exposing the full range of policies to users via a radio button and expecting users to understand all the nuances, I don't see how I would implement something that won't either be incredibly frustrating (and not localisable, since all the error messages are in English), or that just always passes AllowFullyTransparent. :-/
I'm concerned about the practical feasibility of implementing a usable full-node wallet
with this API. Short of exposing the full range of policies to users via a
radio button and expecting users to understand all the nuances, I don't see
how I would implement something that won't either be incredibly frustrating
(and not localisable, since all the error messages are in English), or that