On 11/26/2016 07:37 PM, bbrewer wrote:
On Nov 19, 2016, at 2:43 PM, juan <juan.g71@gmail.com> wrote:
The whole system depends on a single key?
https://petertodd.org/2016/cypherpunk-desert-bus-zcash-trusted-setup-ceremon...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 11/26/2016 07:37 PM, bbrewer wrote:
On Nov 19, 2016, at 2:43 PM, juan <juan.g71@gmail.com> wrote:
The whole system depends on a single key?
https://petertodd.org/2016/cypherpunk-desert-bus-zcash-trusted-setup-ceremon...
This is a fun read. And such entertaining countermeasures, which were necessary. Great job Peter. What I find interesting is this "Single Point of Failure As of writing, I’m not aware of any efforts to independently audit the deterministic build process used to create the compute node DVDs that every participant in the trusted setup used. This means there’s a massive single point of failure in the whole process that completely undermines the value of the multi-party computation. Until the software and deterministic builds are audited, the entire ceremony is a bunch of crypto hocus pocus that means nothing." "Backdoored Software As mentioned above, the software used by every compute node was identical and thus a single point of failure that could be backdoored; I actually raised this as a issue publicly with Zooko a few weeks prior to the ceremony on Twitter." I agree that if everyone used a pre-supplied image given to them for this crypto witchcraft ceremony then it truly is a concern if that software is unaudited from single centralized source. What exactly was this software image and its source? It would be entertaining to have copy of one of those DVDs or image .iso so it can collectively be audited. Even then how would such DVD be audited fully if it is already pre-compiled? While I like the idea of zcash, it is concerning having central point of failure like this if it is such. I support idea of privacy for crypto currencies. Right now I believe best way to do that is through privacy layers on top of bitcoin. Bitcoin excels in transparency without need to trust central point. -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJYOkmkAAoJEAYDai9lH2mwNSwQAI6bXoRtRVri9UyvXxlWS6RQ w8TAeskbbtUK1jw5AvedPQXpIS3SXhWZ8ZVBroayvH/vEsSNMmTQUwfOcWdMITHc KxFlHci9Zx9hpy+0cL/sMM8ZQscT4AVZuJKmTjjeTuITyeelFYYvAtdTyQwVi5wS 6FbVtrsSEMSOFwSIPMyH9Xv2xuSiY1hGHU1Noj5E4/TCySUA7VgpLc+0Pkw8t4V5 lJR/AFViUWcdM/ZBuGzon6csoVGL88a/T3XHle6x6RJfcbYrkG/GXauzYTDcbopd Lz5FUlWDBV5lPRitGmoslVt4SMm/lIlfRm6BT1Ys9cBHbwisVlFEjNgDC2scvDAz tFmFTH7ikuNMx0lKJ0bBPDN2rQXjpuBfthbRMfVZ260PQJ6LvTABfW/kzON3YNcf EgiSn+QPN98E7tTQfo0pdm0Djs9Ba2DREed+dZt8/Q3LZenfJRnW1JWlVbsoXg7m KPzlmRBSPOwWrvVTtmxqfDu2HX5XsazRdK24ZMRfjhDHSALEOXfpn+HGGSA02+dH cCcewXYWgpPNpQxkUchNadV6rwW8Cjh4UNAmGB1F8EuEjxfNnzmIbJNBIIoYCJJP /XanfsY0B8tSP2Pz5yqhBulUKZilOyOfi3KiGd5P49iWSOtwsS3HEXo1gnL4AXUg PTZ3TZL6Fw6/AypJ1Axb =hcnM -----END PGP SIGNATURE----- -- Cannon PGP Fingerprint: 2BB5 15CD 66E7 4E28 45DC 6494 A5A2 2879 3F06 E832 Email: cannon@cannon-ciota.info NOTICE: ALL EMAIL CORRESPONDENCE NOT SIGNED/ENCRYPTED WITH PGP SHOULD BE CONSIDERED POTENTIALLY FORGED, AND NOT PRIVATE. If this matters to you, use PGP or bitmessage.