zookozcash

How's parity-bitcoin's test coverage?

@zallarak: for your information, I loved this proposal, and I hope you, or someone, can do something like this someday. :-) (I'm not part of the Zcash Foundation and I'm...

https://lists.zca.sh/pipermail/zcash-dev/2016-February/000064.html

Here's a new stab at documenting the intended behavior of "Solid Pink Semi-Sparkly" selective transparency, from the perspective of a user: https://lists.zca.sh/pipermail/zcash-dev/2016-February/000067.html (this is prelude: https://lists.zca.sh/pipermail/zcash-dev/2016-February/000066.html)

Here's a use case that I want to support: https://twitter.com/marak/status/706724947239047168 This is a person posting a URL to a public blockchain-viewer site, linking to a specific transaction. I want it...

> However, the proof that I give to the viewing key holder(s) is replayable, i.e. they could pretend to be me. I.e. the proof is only that the payment happened,...

@arielgabizon: a good defense against those sorts of replay/MITM attacks is to include identifiers (e.g. public keys or addresses) of the prover and the verifier into the proof. In this...

This is complementary with https://github.com/zcash/zcash/issues/3677. https://github.com/zcash/zcash/issues/3677 makes it so that it isn't possible to move more ZEC into the first (the Sprout) shielded pool. This gives an incentive to move...

(Disclosure: I'm one of the co-authors of BLAKE2.) My use of BLAKE2 is in the Proof-of-Work in our upcoming cryptocurrency — https://z.cash . However, our current implementation doesn't use openssl...