PR #437proposed changes toZIP 314

[ZIP 314] Privacy upgrades to the Zcash light client protocol

status → Draftby defuse · updated 2022-04-18zip-0314.rst @ 276b6e54ba · upstream 4699a8d518view on GitHub ↗

Unofficial preview — the proposed text below is rendered from the pull request head and is not part of the canonical ZIP set.

Contents

Terminology

The key words "MUST", "SHOULD", and "MAY" in this document are to be interpreted as described in RFC 2119. [1]

The terms below are to be interpreted as follows:

Light client

A client that is not a full participant in the network of Zcash peers. It can send and receive payments, but does not store or validate a copy of the block chain.

Proxy server

lightwalletd TODO define it properly

Abstract

This proposal suggests changes to the Zcash light client protocol to acheive improved privacy properties, at the cost of increased bandwidth usage.

Motivation

Privacy!

References

Changes

zip-0314.rst +41 −0
@@ -0,0 +1,41 @@ +:: + + ZIP: 314 + Title: Privacy upgrades to the Zcash light client protocol + Owners: Taylor Hornby <taylor@electriccoin.co> + Category: Standards / Ecosystem + Status: Draft + Created: 2020-01-11 + License: MIT + + +Terminology +=========== + +The key words "MUST", "SHOULD", and "MAY" in this document are to be interpreted as +described in RFC 2119. [#RFC2119]_ + +The terms below are to be interpreted as follows: + +Light client + A client that is not a full participant in the network of Zcash peers. It can send and + receive payments, but does not store or validate a copy of the block chain. + +Proxy server + lightwalletd TODO define it properly + +Abstract +======== + +This proposal suggests changes to the Zcash light client protocol to acheive +improved privacy properties, at the cost of increased bandwidth usage. + +Motivation +========== + +Privacy! + +References +========== + +.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels <https://www.rfc-editor.org/rfc/rfc2119.html>`_