WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:12.490 align:start position:0% [Music] 00:00:12.490 --> 00:00:12.500 align:start position:0% 00:00:12.500 --> 00:00:15.350 align:start position:0% I<00:00:13.500> wrote<00:00:13.620> the<00:00:13.799> first<00:00:13.920> papers<00:00:14.400> on<00:00:14.700> using<00:00:15.059> zero 00:00:15.350 --> 00:00:15.360 align:start position:0% I wrote the first papers on using zero 00:00:15.360 --> 00:00:17.269 align:start position:0% I wrote the first papers on using zero knowledge<00:00:15.660> proofs<00:00:16.020> and<00:00:16.199> then<00:00:16.320> ZK<00:00:16.619> snarks<00:00:17.160> for 00:00:17.269 --> 00:00:17.279 align:start position:0% knowledge proofs and then ZK snarks for 00:00:17.279 --> 00:00:18.769 align:start position:0% knowledge proofs and then ZK snarks for blockchains<00:00:17.880> this<00:00:18.180> was<00:00:18.300> the<00:00:18.480> work<00:00:18.600> on 00:00:18.769 --> 00:00:18.779 align:start position:0% blockchains this was the work on 00:00:18.779 --> 00:00:21.410 align:start position:0% blockchains this was the work on zerocoin<00:00:19.380> and<00:00:19.500> zero<00:00:19.920> cash<00:00:20.039> this<00:00:21.000> turned<00:00:21.359> into 00:00:21.410 --> 00:00:21.420 align:start position:0% zerocoin and zero cash this turned into 00:00:21.420 --> 00:00:23.990 align:start position:0% zerocoin and zero cash this turned into Z<00:00:21.720> cash<00:00:21.960> and<00:00:22.260> it<00:00:22.380> also<00:00:22.619> happens<00:00:22.800> to<00:00:23.039> be 00:00:23.990 --> 00:00:24.000 align:start position:0% Z cash and it also happens to be 00:00:24.000 --> 00:00:25.970 align:start position:0% Z cash and it also happens to be the<00:00:24.420> protocols<00:00:24.840> that<00:00:25.019> underpin<00:00:25.500> basically 00:00:25.970 --> 00:00:25.980 align:start position:0% the protocols that underpin basically 00:00:25.980 --> 00:00:28.009 align:start position:0% the protocols that underpin basically every<00:00:26.340> second<00:00:26.580> generation<00:00:27.119> privacy<00:00:27.660> coin 00:00:28.009 --> 00:00:28.019 align:start position:0% every second generation privacy coin 00:00:28.019 --> 00:00:30.349 align:start position:0% every second generation privacy coin that's<00:00:28.140> coming<00:00:28.320> online<00:00:28.560> now<00:00:29.580> in<00:00:30.060> other<00:00:30.180> words 00:00:30.349 --> 00:00:30.359 align:start position:0% that's coming online now in other words 00:00:30.359 --> 00:00:32.089 align:start position:0% that's coming online now in other words I've<00:00:30.660> spent<00:00:30.840> about<00:00:31.019> the<00:00:31.320> last<00:00:31.500> 10<00:00:31.859> years 00:00:32.089 --> 00:00:32.099 align:start position:0% I've spent about the last 10 years 00:00:32.099 --> 00:00:34.310 align:start position:0% I've spent about the last 10 years working<00:00:32.579> on<00:00:32.880> zero<00:00:33.239> knowledge<00:00:33.480> proofs<00:00:33.899> for 00:00:34.310 --> 00:00:34.320 align:start position:0% working on zero knowledge proofs for 00:00:34.320 --> 00:00:37.370 align:start position:0% working on zero knowledge proofs for privacy<00:00:34.739> in<00:00:35.040> blockchains<00:00:36.059> and<00:00:36.780> today<00:00:36.960> I'm 00:00:37.370 --> 00:00:37.380 align:start position:0% privacy in blockchains and today I'm 00:00:37.380 --> 00:00:38.750 align:start position:0% privacy in blockchains and today I'm going<00:00:37.559> to<00:00:37.620> give<00:00:37.739> you<00:00:37.860> a<00:00:38.040> talk<00:00:38.219> entitled 00:00:38.750 --> 00:00:38.760 align:start position:0% going to give you a talk entitled 00:00:38.760 --> 00:00:41.090 align:start position:0% going to give you a talk entitled privacy<00:00:39.300> is<00:00:39.540> dead<00:00:39.719> scalability<00:00:40.559> is<00:00:40.739> boring 00:00:41.090 --> 00:00:41.100 align:start position:0% privacy is dead scalability is boring 00:00:41.100 --> 00:00:44.510 align:start position:0% privacy is dead scalability is boring water<00:00:41.520> ZK<00:00:42.000> proofs<00:00:42.360> good<00:00:42.540> for<00:00:42.739> uh<00:00:43.739> so<00:00:44.040> obviously 00:00:44.510 --> 00:00:44.520 align:start position:0% water ZK proofs good for uh so obviously 00:00:44.520 --> 00:00:46.970 align:start position:0% water ZK proofs good for uh so obviously uh<00:00:44.879> privacy<00:00:45.300> and<00:00:45.480> dead<00:00:45.660> is<00:00:45.960> dead<00:00:46.140> is<00:00:46.320> clickbait 00:00:46.970 --> 00:00:46.980 align:start position:0% uh privacy and dead is dead is clickbait 00:00:46.980 --> 00:00:48.889 align:start position:0% uh privacy and dead is dead is clickbait uh<00:00:47.340> apologies<00:00:47.700> if<00:00:47.879> they<00:00:48.059> got<00:00:48.180> you<00:00:48.300> in<00:00:48.420> here<00:00:48.600> for 00:00:48.889 --> 00:00:48.899 align:start position:0% uh apologies if they got you in here for 00:00:48.899 --> 00:00:50.569 align:start position:0% uh apologies if they got you in here for the<00:00:49.140> wrong<00:00:49.320> reasons 00:00:50.569 --> 00:00:50.579 align:start position:0% the wrong reasons 00:00:50.579 --> 00:00:52.310 align:start position:0% the wrong reasons um<00:00:50.700> privacy<00:00:51.180> is<00:00:51.360> really<00:00:51.539> important<00:00:51.899> I<00:00:52.140> spent 00:00:52.310 --> 00:00:52.320 align:start position:0% um privacy is really important I spent 00:00:52.320 --> 00:00:53.869 align:start position:0% um privacy is really important I spent the<00:00:52.500> last<00:00:52.620> 10<00:00:52.800> years<00:00:52.920> of<00:00:53.100> my<00:00:53.219> life<00:00:53.340> working<00:00:53.640> on 00:00:53.869 --> 00:00:53.879 align:start position:0% the last 10 years of my life working on 00:00:53.879 --> 00:00:55.069 align:start position:0% the last 10 years of my life working on this<00:00:54.059> stuff 00:00:55.069 --> 00:00:55.079 align:start position:0% this stuff 00:00:55.079 --> 00:00:56.389 align:start position:0% this stuff but 00:00:56.389 --> 00:00:56.399 align:start position:0% but 00:00:56.399 --> 00:00:58.670 align:start position:0% but we<00:00:57.000> haven't<00:00:57.120> seen<00:00:57.539> a<00:00:57.780> large<00:00:57.899> amount<00:00:58.199> of<00:00:58.320> demand 00:00:58.670 --> 00:00:58.680 align:start position:0% we haven't seen a large amount of demand 00:00:58.680 --> 00:01:01.069 align:start position:0% we haven't seen a large amount of demand for<00:00:59.219> private<00:00:59.640> consumer<00:01:00.059> payments<00:01:00.480> right 00:01:01.069 --> 00:01:01.079 align:start position:0% for private consumer payments right 00:01:01.079 --> 00:01:03.470 align:start position:0% for private consumer payments right Monero<00:01:01.980> launched<00:01:02.340> zcash<00:01:02.940> launched<00:01:03.300> other 00:01:03.470 --> 00:01:03.480 align:start position:0% Monero launched zcash launched other 00:01:03.480 --> 00:01:06.830 align:start position:0% Monero launched zcash launched other things<00:01:03.719> launched<00:01:04.199> they<00:01:04.860> exist<00:01:05.159> they're<00:01:05.519> great 00:01:06.830 --> 00:01:06.840 align:start position:0% things launched they exist they're great 00:01:06.840 --> 00:01:08.990 align:start position:0% things launched they exist they're great they<00:01:07.320> aren't<00:01:07.439> really<00:01:07.560> moving<00:01:07.799> the<00:01:07.979> needle<00:01:08.520> and 00:01:08.990 --> 00:01:09.000 align:start position:0% they aren't really moving the needle and 00:01:09.000 --> 00:01:10.910 align:start position:0% they aren't really moving the needle and so<00:01:09.119> I've<00:01:09.299> found<00:01:09.540> myself<00:01:09.780> wondering<00:01:10.380> as<00:01:10.560> I<00:01:10.740> work 00:01:10.910 --> 00:01:10.920 align:start position:0% so I've found myself wondering as I work 00:01:10.920 --> 00:01:12.469 align:start position:0% so I've found myself wondering as I work as<00:01:11.040> a<00:01:11.220> professor<00:01:11.460> I'm<00:01:11.640> like<00:01:11.820> What's<00:01:12.119> the<00:01:12.360> next 00:01:12.469 --> 00:01:12.479 align:start position:0% as a professor I'm like What's the next 00:01:12.479 --> 00:01:14.510 align:start position:0% as a professor I'm like What's the next thing<00:01:12.659> we<00:01:12.900> do<00:01:13.020> you<00:01:13.560> know<00:01:13.680> what<00:01:13.920> happens<00:01:14.100> if 00:01:14.510 --> 00:01:14.520 align:start position:0% thing we do you know what happens if 00:01:14.520 --> 00:01:16.250 align:start position:0% thing we do you know what happens if demand<00:01:14.880> for<00:01:15.060> this<00:01:15.240> kind<00:01:15.420> of<00:01:15.479> stuff<00:01:15.659> is<00:01:16.020> 10 00:01:16.250 --> 00:01:16.260 align:start position:0% demand for this kind of stuff is 10 00:01:16.260 --> 00:01:19.190 align:start position:0% demand for this kind of stuff is 10 years<00:01:16.500> plus<00:01:17.040> out<00:01:17.400> one<00:01:18.180> of<00:01:18.299> my<00:01:18.360> co-authors<00:01:18.780> Iran 00:01:19.190 --> 00:01:19.200 align:start position:0% years plus out one of my co-authors Iran 00:01:19.200 --> 00:01:20.870 align:start position:0% years plus out one of my co-authors Iran trommer<00:01:19.619> sort<00:01:19.799> of<00:01:19.860> described<00:01:20.220> it<00:01:20.280> as<00:01:20.460> follows 00:01:20.870 --> 00:01:20.880 align:start position:0% trommer sort of described it as follows 00:01:20.880 --> 00:01:23.270 align:start position:0% trommer sort of described it as follows selling<00:01:21.720> privacy<00:01:22.140> for<00:01:22.439> people<00:01:22.680> for 00:01:23.270 --> 00:01:23.280 align:start position:0% selling privacy for people for 00:01:23.280 --> 00:01:25.010 align:start position:0% selling privacy for people for blockchain<00:01:23.640> payments<00:01:24.180> is<00:01:24.659> kind<00:01:24.900> of<00:01:24.960> like 00:01:25.010 --> 00:01:25.020 align:start position:0% blockchain payments is kind of like 00:01:25.020 --> 00:01:27.950 align:start position:0% blockchain payments is kind of like selling<00:01:25.380> seat<00:01:25.500> belts<00:01:25.979> for<00:01:26.100> cars<00:01:26.460> in<00:01:26.580> the<00:01:26.759> 1920s 00:01:27.950 --> 00:01:27.960 align:start position:0% selling seat belts for cars in the 1920s 00:01:27.960 --> 00:01:29.870 align:start position:0% selling seat belts for cars in the 1920s sure<00:01:28.259> we<00:01:28.560> can<00:01:28.680> all<00:01:28.860> kind<00:01:29.100> of<00:01:29.220> figure<00:01:29.400> out<00:01:29.580> that 00:01:29.870 --> 00:01:29.880 align:start position:0% sure we can all kind of figure out that 00:01:29.880 --> 00:01:30.950 align:start position:0% sure we can all kind of figure out that in<00:01:30.000> the<00:01:30.119> future<00:01:30.180> you're<00:01:30.420> going<00:01:30.540> to<00:01:30.600> need<00:01:30.780> it 00:01:30.950 --> 00:01:30.960 align:start position:0% in the future you're going to need it 00:01:30.960 --> 00:01:32.450 align:start position:0% in the future you're going to need it but<00:01:31.320> until<00:01:31.439> you<00:01:31.680> end<00:01:31.799> up<00:01:31.920> with<00:01:32.100> the<00:01:32.220> actual 00:01:32.450 --> 00:01:32.460 align:start position:0% but until you end up with the actual 00:01:32.460 --> 00:01:33.830 align:start position:0% but until you end up with the actual interstate<00:01:32.880> highway<00:01:33.060> system<00:01:33.360> and<00:01:33.600> people 00:01:33.830 --> 00:01:33.840 align:start position:0% interstate highway system and people 00:01:33.840 --> 00:01:36.410 align:start position:0% interstate highway system and people crashing<00:01:34.200> cars<00:01:34.560> at<00:01:34.799> 60<00:01:35.040> miles<00:01:35.340> an<00:01:35.579> hour<00:01:35.700> it's 00:01:36.410 --> 00:01:36.420 align:start position:0% crashing cars at 60 miles an hour it's 00:01:36.420 --> 00:01:37.730 align:start position:0% crashing cars at 60 miles an hour it's kind<00:01:36.600> of<00:01:36.720> hard<00:01:36.900> to<00:01:37.079> sell<00:01:37.200> people<00:01:37.380> in<00:01:37.619> the 00:01:37.730 --> 00:01:37.740 align:start position:0% kind of hard to sell people in the 00:01:37.740 --> 00:01:38.510 align:start position:0% kind of hard to sell people in the future 00:01:38.510 --> 00:01:38.520 align:start position:0% future 00:01:38.520 --> 00:01:42.050 align:start position:0% future so<00:01:39.479> what<00:01:40.200> do<00:01:40.320> we<00:01:40.439> do<00:01:40.619> right 00:01:42.050 --> 00:01:42.060 align:start position:0% so what do we do right 00:01:42.060 --> 00:01:44.510 align:start position:0% so what do we do right second<00:01:42.659> problem<00:01:43.020> is<00:01:43.320> in<00:01:43.619> terms<00:01:43.799> of<00:01:43.920> research 00:01:44.510 --> 00:01:44.520 align:start position:0% second problem is in terms of research 00:01:44.520 --> 00:01:45.830 align:start position:0% second problem is in terms of research right<00:01:44.820> for<00:01:45.060> everybody<00:01:45.180> who<00:01:45.479> likes<00:01:45.659> to<00:01:45.720> get 00:01:45.830 --> 00:01:45.840 align:start position:0% right for everybody who likes to get 00:01:45.840 --> 00:01:47.270 align:start position:0% right for everybody who likes to get excited<00:01:46.140> about<00:01:46.259> new<00:01:46.560> technical<00:01:46.920> stuff<00:01:47.100> and 00:01:47.270 --> 00:01:47.280 align:start position:0% excited about new technical stuff and 00:01:47.280 --> 00:01:48.770 align:start position:0% excited about new technical stuff and new<00:01:47.400> cryptography 00:01:48.770 --> 00:01:48.780 align:start position:0% new cryptography 00:01:48.780 --> 00:01:50.810 align:start position:0% new cryptography there<00:01:49.140> isn't<00:01:49.439> much<00:01:49.619> here<00:01:49.860> anymore<00:01:50.220> the 00:01:50.810 --> 00:01:50.820 align:start position:0% there isn't much here anymore the 00:01:50.820 --> 00:01:52.910 align:start position:0% there isn't much here anymore the techniques<00:01:51.479> to<00:01:51.600> do<00:01:51.780> this<00:01:51.899> are<00:01:52.200> known<00:01:52.500> they're 00:01:52.910 --> 00:01:52.920 align:start position:0% techniques to do this are known they're 00:01:52.920 --> 00:01:54.770 align:start position:0% techniques to do this are known they're done<00:01:53.159> we<00:01:53.520> worked<00:01:53.880> them<00:01:53.939> out<00:01:54.119> and<00:01:54.360> this<00:01:54.540> is<00:01:54.659> now 00:01:54.770 --> 00:01:54.780 align:start position:0% done we worked them out and this is now 00:01:54.780 --> 00:01:56.450 align:start position:0% done we worked them out and this is now a<00:01:55.020> thing<00:01:55.140> to<00:01:55.320> work<00:01:55.500> out<00:01:55.680> in<00:01:56.040> industrial 00:01:56.450 --> 00:01:56.460 align:start position:0% a thing to work out in industrial 00:01:56.460 --> 00:01:58.850 align:start position:0% a thing to work out in industrial applications<00:01:57.000> right<00:01:57.720> the<00:01:58.020> approach<00:01:58.500> for<00:01:58.680> how 00:01:58.850 --> 00:01:58.860 align:start position:0% applications right the approach for how 00:01:58.860 --> 00:02:00.770 align:start position:0% applications right the approach for how you<00:01:58.979> build<00:01:59.159> private<00:01:59.700> payments<00:02:00.060> is<00:02:00.360> that<00:02:00.540> zero 00:02:00.770 --> 00:02:00.780 align:start position:0% you build private payments is that zero 00:02:00.780 --> 00:02:02.450 align:start position:0% you build private payments is that zero knowledge<00:02:01.079> proof<00:02:01.439> plus<00:02:01.860> an<00:02:02.040> accumulator 00:02:02.450 --> 00:02:02.460 align:start position:0% knowledge proof plus an accumulator 00:02:02.460 --> 00:02:06.889 align:start position:0% knowledge proof plus an accumulator typically<00:02:03.360> ZK<00:02:04.079> snark<00:02:04.500> plus<00:02:04.920> a<00:02:05.100> Merkle<00:02:05.460> tree 00:02:06.889 --> 00:02:06.899 align:start position:0% typically ZK snark plus a Merkle tree 00:02:06.899 --> 00:02:08.690 align:start position:0% typically ZK snark plus a Merkle tree this<00:02:07.380> was<00:02:07.500> developed<00:02:07.860> in<00:02:07.979> zero<00:02:08.280> cache<00:02:08.520> and<00:02:08.580> my 00:02:08.690 --> 00:02:08.700 align:start position:0% this was developed in zero cache and my 00:02:08.700 --> 00:02:10.729 align:start position:0% this was developed in zero cache and my PhD<00:02:09.060> thesis<00:02:09.420> it<00:02:09.660> ended<00:02:09.899> up<00:02:09.959> in<00:02:10.080> Z<00:02:10.200> cash<00:02:10.380> it's 00:02:10.729 --> 00:02:10.739 align:start position:0% PhD thesis it ended up in Z cash it's 00:02:10.739 --> 00:02:12.410 align:start position:0% PhD thesis it ended up in Z cash it's now<00:02:10.920> in<00:02:11.099> you<00:02:11.280> know<00:02:11.400> pretty<00:02:11.640> much<00:02:11.760> every<00:02:12.120> single 00:02:12.410 --> 00:02:12.420 align:start position:0% now in you know pretty much every single 00:02:12.420 --> 00:02:13.790 align:start position:0% now in you know pretty much every single other<00:02:12.599> thing<00:02:12.840> that's<00:02:13.020> coming<00:02:13.200> online<00:02:13.440> now 00:02:13.790 --> 00:02:13.800 align:start position:0% other thing that's coming online now 00:02:13.800 --> 00:02:16.490 align:start position:0% other thing that's coming online now Aztec<00:02:14.700> andoma<00:02:15.000> penumbra<00:02:15.540> railgun<00:02:16.080> they<00:02:16.379> all 00:02:16.490 --> 00:02:16.500 align:start position:0% Aztec andoma penumbra railgun they all 00:02:16.500 --> 00:02:17.750 align:start position:0% Aztec andoma penumbra railgun they all have<00:02:16.680> features<00:02:16.980> on<00:02:17.099> top<00:02:17.220> of<00:02:17.340> this<00:02:17.459> they're<00:02:17.640> not 00:02:17.750 --> 00:02:17.760 align:start position:0% have features on top of this they're not 00:02:17.760 --> 00:02:19.610 align:start position:0% have features on top of this they're not clones<00:02:18.120> but<00:02:18.720> that's<00:02:18.900> the<00:02:19.080> base<00:02:19.200> thing<00:02:19.440> for 00:02:19.610 --> 00:02:19.620 align:start position:0% clones but that's the base thing for 00:02:19.620 --> 00:02:21.589 align:start position:0% clones but that's the base thing for privacy<00:02:19.920> for<00:02:20.160> payments 00:02:21.589 --> 00:02:21.599 align:start position:0% privacy for payments 00:02:21.599 --> 00:02:22.369 align:start position:0% privacy for payments um 00:02:22.369 --> 00:02:22.379 align:start position:0% um 00:02:22.379 --> 00:02:24.770 align:start position:0% um and<00:02:22.980> so<00:02:23.160> sure<00:02:23.459> you<00:02:23.760> can<00:02:23.819> build<00:02:23.940> tweaks<00:02:24.420> you<00:02:24.720> can 00:02:24.770 --> 00:02:24.780 align:start position:0% and so sure you can build tweaks you can 00:02:24.780 --> 00:02:26.030 align:start position:0% and so sure you can build tweaks you can change<00:02:24.900> the<00:02:25.140> accumulator<00:02:25.500> you<00:02:25.800> can<00:02:25.920> change 00:02:26.030 --> 00:02:26.040 align:start position:0% change the accumulator you can change 00:02:26.040 --> 00:02:27.410 align:start position:0% change the accumulator you can change the<00:02:26.220> proof<00:02:26.459> systems<00:02:26.819> you<00:02:27.000> can<00:02:27.060> claim<00:02:27.300> it 00:02:27.410 --> 00:02:27.420 align:start position:0% the proof systems you can claim it 00:02:27.420 --> 00:02:29.930 align:start position:0% the proof systems you can claim it something<00:02:27.599> completely<00:02:28.020> new<00:02:28.260> uh 00:02:29.930 --> 00:02:29.940 align:start position:0% something completely new uh 00:02:29.940 --> 00:02:31.369 align:start position:0% something completely new uh you<00:02:30.360> know<00:02:30.420> you<00:02:30.599> can<00:02:30.720> add<00:02:30.840> extra<00:02:31.020> features 00:02:31.369 --> 00:02:31.379 align:start position:0% you know you can add extra features 00:02:31.379 --> 00:02:33.589 align:start position:0% you know you can add extra features that's<00:02:31.620> quite<00:02:31.800> valid<00:02:32.220> but<00:02:32.879> this<00:02:33.300> kind<00:02:33.480> of 00:02:33.589 --> 00:02:33.599 align:start position:0% that's quite valid but this kind of 00:02:33.599 --> 00:02:35.270 align:start position:0% that's quite valid but this kind of feels<00:02:33.900> to<00:02:34.020> me<00:02:34.140> like<00:02:34.379> we're<00:02:34.560> leaving<00:02:34.800> behind 00:02:35.270 --> 00:02:35.280 align:start position:0% feels to me like we're leaving behind 00:02:35.280 --> 00:02:36.890 align:start position:0% feels to me like we're leaving behind the<00:02:35.520> main<00:02:35.640> things<00:02:35.819> that<00:02:36.000> make<00:02:36.120> zero<00:02:36.420> and<00:02:36.660> all 00:02:36.890 --> 00:02:36.900 align:start position:0% the main things that make zero and all 00:02:36.900 --> 00:02:38.809 align:start position:0% the main things that make zero and all it<00:02:37.080> proves<00:02:37.379> really<00:02:37.680> cool<00:02:37.920> because<00:02:38.459> the<00:02:38.700> thing 00:02:38.809 --> 00:02:38.819 align:start position:0% it proves really cool because the thing 00:02:38.819 --> 00:02:40.610 align:start position:0% it proves really cool because the thing to<00:02:38.940> me<00:02:39.060> that's<00:02:39.300> fascinated<00:02:39.780> me<00:02:39.959> since<00:02:40.260> I<00:02:40.500> was 00:02:40.610 --> 00:02:40.620 align:start position:0% to me that's fascinated me since I was 00:02:40.620 --> 00:02:42.830 align:start position:0% to me that's fascinated me since I was 12<00:02:40.980> is<00:02:41.580> the<00:02:41.700> zero<00:02:42.060> knowledge<00:02:42.300> bits<00:02:42.599> that<00:02:42.780> we're 00:02:42.830 --> 00:02:42.840 align:start position:0% 12 is the zero knowledge bits that we're 00:02:42.840 --> 00:02:44.570 align:start position:0% 12 is the zero knowledge bits that we're hiding<00:02:43.200> things<00:02:43.379> and<00:02:43.739> if<00:02:43.920> nobody<00:02:44.160> cares<00:02:44.400> about 00:02:44.570 --> 00:02:44.580 align:start position:0% hiding things and if nobody cares about 00:02:44.580 --> 00:02:47.089 align:start position:0% hiding things and if nobody cares about privacy<00:02:45.239> well<00:02:46.140> we<00:02:46.440> should<00:02:46.560> move<00:02:46.739> to<00:02:46.920> something 00:02:47.089 --> 00:02:47.099 align:start position:0% privacy well we should move to something 00:02:47.099 --> 00:02:49.369 align:start position:0% privacy well we should move to something else<00:02:47.400> as<00:02:47.940> an<00:02:48.120> application 00:02:49.369 --> 00:02:49.379 align:start position:0% else as an application 00:02:49.379 --> 00:02:51.470 align:start position:0% else as an application obviously<00:02:50.099> privacy's<00:02:50.640> not<00:02:50.819> dead<00:02:51.000> everywhere 00:02:51.470 --> 00:02:51.480 align:start position:0% obviously privacy's not dead everywhere 00:02:51.480 --> 00:02:53.030 align:start position:0% obviously privacy's not dead everywhere uh<00:02:52.019> it's<00:02:52.140> definitely<00:02:52.379> not<00:02:52.500> dead<00:02:52.680> everywhere 00:02:53.030 --> 00:02:53.040 align:start position:0% uh it's definitely not dead everywhere 00:02:53.040 --> 00:02:55.190 align:start position:0% uh it's definitely not dead everywhere in<00:02:53.099> cryptocurrency<00:02:53.640> uh<00:02:54.120> so<00:02:54.300> if<00:02:54.480> you're<00:02:54.720> one<00:02:55.019> of 00:02:55.190 --> 00:02:55.200 align:start position:0% in cryptocurrency uh so if you're one of 00:02:55.200 --> 00:02:56.930 align:start position:0% in cryptocurrency uh so if you're one of these<00:02:55.319> second<00:02:55.620> gen<00:02:55.860> privacy<00:02:56.280> coins<00:02:56.519> don't<00:02:56.760> you 00:02:56.930 --> 00:02:56.940 align:start position:0% these second gen privacy coins don't you 00:02:56.940 --> 00:02:58.369 align:start position:0% these second gen privacy coins don't you know<00:02:57.000> kill<00:02:57.180> me<00:02:57.300> for<00:02:57.480> killing<00:02:57.720> your<00:02:57.840> pitch<00:02:58.019> deck 00:02:58.369 --> 00:02:58.379 align:start position:0% know kill me for killing your pitch deck 00:02:58.379 --> 00:03:00.470 align:start position:0% know kill me for killing your pitch deck uh<00:02:59.040> there<00:02:59.340> are<00:02:59.459> other<00:02:59.640> things<00:02:59.940> that<00:03:00.239> are 00:03:00.470 --> 00:03:00.480 align:start position:0% uh there are other things that are 00:03:00.480 --> 00:03:02.750 align:start position:0% uh there are other things that are happening<00:03:00.840> probably<00:03:01.680> we<00:03:01.980> need<00:03:02.099> privacy<00:03:02.519> for 00:03:02.750 --> 00:03:02.760 align:start position:0% happening probably we need privacy for 00:03:02.760 --> 00:03:05.630 align:start position:0% happening probably we need privacy for defy<00:03:03.180> it<00:03:03.540> seems<00:03:03.780> like<00:03:03.840> Traders<00:03:04.200> do<00:03:04.379> need<00:03:04.560> that 00:03:05.630 --> 00:03:05.640 align:start position:0% defy it seems like Traders do need that 00:03:05.640 --> 00:03:07.610 align:start position:0% defy it seems like Traders do need that um<00:03:05.700> you<00:03:06.060> might<00:03:06.239> be<00:03:06.360> able<00:03:06.540> to<00:03:06.660> use<00:03:06.780> ZK<00:03:07.140> proofs<00:03:07.500> to 00:03:07.610 --> 00:03:07.620 align:start position:0% um you might be able to use ZK proofs to 00:03:07.620 --> 00:03:09.530 align:start position:0% um you might be able to use ZK proofs to get<00:03:07.680> out<00:03:07.800> of<00:03:07.920> Mev<00:03:08.340> or<00:03:08.459> front<00:03:08.580> running 00:03:09.530 --> 00:03:09.540 align:start position:0% get out of Mev or front running 00:03:09.540 --> 00:03:11.270 align:start position:0% get out of Mev or front running Jerry's<00:03:10.319> still<00:03:10.379> out<00:03:10.560> on<00:03:10.739> that<00:03:10.860> you<00:03:11.040> can<00:03:11.159> have 00:03:11.270 --> 00:03:11.280 align:start position:0% Jerry's still out on that you can have 00:03:11.280 --> 00:03:12.830 align:start position:0% Jerry's still out on that you can have an<00:03:11.400> interesting<00:03:11.760> argument<00:03:12.060> with<00:03:12.239> Phil<00:03:12.420> Diane 00:03:12.830 --> 00:03:12.840 align:start position:0% an interesting argument with Phil Diane 00:03:12.840 --> 00:03:14.449 align:start position:0% an interesting argument with Phil Diane if<00:03:12.959> you<00:03:13.080> don't<00:03:13.200> believe<00:03:13.319> me 00:03:14.449 --> 00:03:14.459 align:start position:0% if you don't believe me 00:03:14.459 --> 00:03:17.089 align:start position:0% if you don't believe me um<00:03:14.519> but<00:03:15.060> nonetheless<00:03:15.720> the<00:03:16.319> core<00:03:16.500> protocols 00:03:17.089 --> 00:03:17.099 align:start position:0% um but nonetheless the core protocols 00:03:17.099 --> 00:03:18.530 align:start position:0% um but nonetheless the core protocols for<00:03:17.220> doing<00:03:17.400> zero<00:03:17.700> knowledge<00:03:17.940> proofs<00:03:18.300> are 00:03:18.530 --> 00:03:18.540 align:start position:0% for doing zero knowledge proofs are 00:03:18.540 --> 00:03:20.930 align:start position:0% for doing zero knowledge proofs are still<00:03:18.900> like<00:03:19.379> the<00:03:20.040> same<00:03:20.159> as<00:03:20.400> far<00:03:20.519> as<00:03:20.640> private 00:03:20.930 --> 00:03:20.940 align:start position:0% still like the same as far as private 00:03:20.940 --> 00:03:23.509 align:start position:0% still like the same as far as private payments<00:03:21.300> go<00:03:21.420> even<00:03:21.900> for<00:03:22.200> these<00:03:22.379> applications 00:03:23.509 --> 00:03:23.519 align:start position:0% payments go even for these applications 00:03:23.519 --> 00:03:25.729 align:start position:0% payments go even for these applications so<00:03:24.000> from<00:03:24.300> a<00:03:24.480> research<00:03:24.780> perspective<00:03:25.200> there's 00:03:25.729 --> 00:03:25.739 align:start position:0% so from a research perspective there's 00:03:25.739 --> 00:03:27.470 align:start position:0% so from a research perspective there's nothing<00:03:25.980> new<00:03:26.280> here 00:03:27.470 --> 00:03:27.480 align:start position:0% nothing new here 00:03:27.480 --> 00:03:30.290 align:start position:0% nothing new here so<00:03:28.080> what<00:03:28.440> do<00:03:28.620> we<00:03:28.739> do<00:03:28.860> well<00:03:29.459> I<00:03:29.700> hope<00:03:29.879> this<00:03:30.000> isn't 00:03:30.290 --> 00:03:30.300 align:start position:0% so what do we do well I hope this isn't 00:03:30.300 --> 00:03:32.649 align:start position:0% so what do we do well I hope this isn't too<00:03:30.780> offensive<00:03:31.140> to<00:03:31.260> any<00:03:31.319> of<00:03:31.500> you<00:03:31.620> are<00:03:31.800> but<00:03:32.040> uh 00:03:32.649 --> 00:03:32.659 align:start position:0% too offensive to any of you are but uh 00:03:32.659 --> 00:03:34.970 align:start position:0% too offensive to any of you are but uh blockchains<00:03:33.659> are<00:03:33.780> slow 00:03:34.970 --> 00:03:34.980 align:start position:0% blockchains are slow 00:03:34.980 --> 00:03:37.009 align:start position:0% blockchains are slow so<00:03:35.640> that's<00:03:35.819> a<00:03:36.060> whole<00:03:36.180> problem 00:03:37.009 --> 00:03:37.019 align:start position:0% so that's a whole problem 00:03:37.019 --> 00:03:39.410 align:start position:0% so that's a whole problem and<00:03:37.680> well<00:03:37.920> okay<00:03:38.280> zero<00:03:38.760> knowledge<00:03:39.000> proofs<00:03:39.300> are 00:03:39.410 --> 00:03:39.420 align:start position:0% and well okay zero knowledge proofs are 00:03:39.420 --> 00:03:40.850 align:start position:0% and well okay zero knowledge proofs are supposed<00:03:39.599> to<00:03:39.780> be<00:03:39.840> everything<00:03:40.260> a<00:03:40.620> growing 00:03:40.850 --> 00:03:40.860 align:start position:0% supposed to be everything a growing 00:03:40.860 --> 00:03:42.649 align:start position:0% supposed to be everything a growing blockchain<00:03:41.220> needs<00:03:41.640> so<00:03:41.819> a<00:03:42.120> lot<00:03:42.299> of<00:03:42.420> people 00:03:42.649 --> 00:03:42.659 align:start position:0% blockchain needs so a lot of people 00:03:42.659 --> 00:03:45.170 align:start position:0% blockchain needs so a lot of people working<00:03:43.080> on<00:03:43.379> scalability<00:03:43.980> for<00:03:44.640> blockchains 00:03:45.170 --> 00:03:45.180 align:start position:0% working on scalability for blockchains 00:03:45.180 --> 00:03:47.570 align:start position:0% working on scalability for blockchains doing<00:03:45.360> ZK<00:03:45.659> Roll-Ups<00:03:46.200> dkvms<00:03:46.980> right<00:03:47.159> this<00:03:47.340> is<00:03:47.459> a 00:03:47.570 --> 00:03:47.580 align:start position:0% doing ZK Roll-Ups dkvms right this is a 00:03:47.580 --> 00:03:48.949 align:start position:0% doing ZK Roll-Ups dkvms right this is a lot<00:03:47.640> of<00:03:47.760> research<00:03:48.060> it's<00:03:48.299> a<00:03:48.420> lot<00:03:48.540> of<00:03:48.659> funding 00:03:48.949 --> 00:03:48.959 align:start position:0% lot of research it's a lot of funding 00:03:48.959 --> 00:03:50.390 align:start position:0% lot of research it's a lot of funding it's<00:03:49.260> probably<00:03:49.500> several<00:03:49.860> billion<00:03:50.159> dollars 00:03:50.390 --> 00:03:50.400 align:start position:0% it's probably several billion dollars 00:03:50.400 --> 00:03:52.130 align:start position:0% it's probably several billion dollars worth<00:03:50.519> of<00:03:50.760> value<00:03:51.000> from<00:03:51.299> ventral<00:03:51.659> capital<00:03:51.840> for 00:03:52.130 --> 00:03:52.140 align:start position:0% worth of value from ventral capital for 00:03:52.140 --> 00:03:53.930 align:start position:0% worth of value from ventral capital for this<00:03:52.319> and<00:03:53.099> this<00:03:53.340> is<00:03:53.400> where<00:03:53.640> all<00:03:53.819> the 00:03:53.930 --> 00:03:53.940 align:start position:0% this and this is where all the 00:03:53.940 --> 00:03:56.330 align:start position:0% this and this is where all the excitement<00:03:54.360> is<00:03:54.599> right<00:03:54.780> now 00:03:56.330 --> 00:03:56.340 align:start position:0% excitement is right now 00:03:56.340 --> 00:03:58.789 align:start position:0% excitement is right now but<00:03:57.180> if<00:03:57.840> you<00:03:57.959> haven't<00:03:58.019> seen<00:03:58.260> this<00:03:58.440> well<00:03:58.680> you 00:03:58.789 --> 00:03:58.799 align:start position:0% but if you haven't seen this well you 00:03:58.799 --> 00:04:00.470 align:start position:0% but if you haven't seen this well you know<00:03:58.920> how<00:03:59.040> do<00:03:59.159> these<00:03:59.340> things<00:03:59.519> work<00:03:59.760> uh<00:04:00.239> in<00:04:00.360> a 00:04:00.470 --> 00:04:00.480 align:start position:0% know how do these things work uh in a 00:04:00.480 --> 00:04:02.509 align:start position:0% know how do these things work uh in a row<00:04:00.720> up<00:04:00.840> you<00:04:01.080> have<00:04:01.200> a<00:04:01.319> server<00:04:01.620> that<00:04:02.040> is<00:04:02.280> taking 00:04:02.509 --> 00:04:02.519 align:start position:0% row up you have a server that is taking 00:04:02.519 --> 00:04:04.910 align:start position:0% row up you have a server that is taking transactions<00:04:03.180> that<00:04:03.299> users<00:04:03.599> generate<00:04:04.080> users 00:04:04.910 --> 00:04:04.920 align:start position:0% transactions that users generate users 00:04:04.920 --> 00:04:06.770 align:start position:0% transactions that users generate users submit<00:04:05.280> those<00:04:05.400> transactions<00:04:05.940> to<00:04:06.239> the<00:04:06.420> server 00:04:06.770 --> 00:04:06.780 align:start position:0% submit those transactions to the server 00:04:06.780 --> 00:04:08.690 align:start position:0% submit those transactions to the server the<00:04:07.379> server<00:04:07.680> takes<00:04:07.920> them<00:04:08.040> and<00:04:08.220> compresses 00:04:08.690 --> 00:04:08.700 align:start position:0% the server takes them and compresses 00:04:08.700 --> 00:04:10.670 align:start position:0% the server takes them and compresses them<00:04:08.940> down<00:04:09.180> using<00:04:09.840> a<00:04:09.959> zero<00:04:10.260> knowledge<00:04:10.439> proof 00:04:10.670 --> 00:04:10.680 align:start position:0% them down using a zero knowledge proof 00:04:10.680 --> 00:04:11.809 align:start position:0% them down using a zero knowledge proof does<00:04:10.860> anyone<00:04:11.040> know<00:04:11.159> which<00:04:11.280> proof<00:04:11.459> says<00:04:11.700> hey 00:04:11.809 --> 00:04:11.819 align:start position:0% does anyone know which proof says hey 00:04:11.819 --> 00:04:14.089 align:start position:0% does anyone know which proof says hey all<00:04:12.120> these<00:04:12.360> transactions<00:04:12.780> are<00:04:12.959> correct<00:04:13.260> uh 00:04:14.089 --> 00:04:14.099 align:start position:0% all these transactions are correct uh 00:04:14.099 --> 00:04:15.530 align:start position:0% all these transactions are correct uh and<00:04:14.220> then<00:04:14.280> the<00:04:14.459> server<00:04:14.700> generates<00:04:15.060> this<00:04:15.239> proof 00:04:15.530 --> 00:04:15.540 align:start position:0% and then the server generates this proof 00:04:15.540 --> 00:04:17.030 align:start position:0% and then the server generates this proof and<00:04:15.720> sort<00:04:15.959> of<00:04:16.079> throws<00:04:16.380> it<00:04:16.500> over<00:04:16.620> the<00:04:16.739> wall<00:04:16.859> to 00:04:17.030 --> 00:04:17.040 align:start position:0% and sort of throws it over the wall to 00:04:17.040 --> 00:04:18.170 align:start position:0% and sort of throws it over the wall to the<00:04:17.220> blockchain 00:04:18.170 --> 00:04:18.180 align:start position:0% the blockchain 00:04:18.180 --> 00:04:20.750 align:start position:0% the blockchain and<00:04:18.959> so<00:04:19.139> the<00:04:19.260> server<00:04:19.560> is<00:04:19.739> in<00:04:19.919> effect 00:04:20.750 --> 00:04:20.760 align:start position:0% and so the server is in effect 00:04:20.760 --> 00:04:23.390 align:start position:0% and so the server is in effect saving<00:04:21.479> the<00:04:21.600> blockchain<00:04:21.959> work<00:04:22.260> this<00:04:22.860> proof<00:04:23.160> is 00:04:23.390 --> 00:04:23.400 align:start position:0% saving the blockchain work this proof is 00:04:23.400 --> 00:04:25.850 align:start position:0% saving the blockchain work this proof is succinct<00:04:23.880> at<00:04:24.360> least<00:04:24.540> somewhat<00:04:24.900> uh<00:04:25.620> and<00:04:25.740> so 00:04:25.850 --> 00:04:25.860 align:start position:0% succinct at least somewhat uh and so 00:04:25.860 --> 00:04:27.170 align:start position:0% succinct at least somewhat uh and so it's<00:04:26.040> easier<00:04:26.280> for<00:04:26.460> the<00:04:26.580> blockchain<00:04:26.880> to<00:04:27.060> check 00:04:27.170 --> 00:04:27.180 align:start position:0% it's easier for the blockchain to check 00:04:27.180 --> 00:04:28.730 align:start position:0% it's easier for the blockchain to check that<00:04:27.419> than<00:04:27.660> this<00:04:27.840> to<00:04:28.020> check<00:04:28.139> all<00:04:28.259> the<00:04:28.440> proofs 00:04:28.730 --> 00:04:28.740 align:start position:0% that than this to check all the proofs 00:04:28.740 --> 00:04:30.530 align:start position:0% that than this to check all the proofs and<00:04:29.280> so<00:04:29.400> then<00:04:29.520> it<00:04:29.699> doesn't<00:04:29.820> matter<00:04:30.060> if<00:04:30.419> your 00:04:30.530 --> 00:04:30.540 align:start position:0% and so then it doesn't matter if your 00:04:30.540 --> 00:04:31.790 align:start position:0% and so then it doesn't matter if your blockchain<00:04:30.900> is<00:04:31.139> slow<00:04:31.259> and<00:04:31.440> does<00:04:31.620> 10 00:04:31.790 --> 00:04:31.800 align:start position:0% blockchain is slow and does 10 00:04:31.800 --> 00:04:33.770 align:start position:0% blockchain is slow and does 10 transactions<00:04:32.400> per<00:04:32.580> second<00:04:32.759> if<00:04:33.360> each<00:04:33.479> one<00:04:33.660> of 00:04:33.770 --> 00:04:33.780 align:start position:0% transactions per second if each one of 00:04:33.780 --> 00:04:35.150 align:start position:0% transactions per second if each one of those<00:04:33.840> transactions<00:04:34.380> is<00:04:34.560> a<00:04:34.680> zero<00:04:34.919> knowledge 00:04:35.150 --> 00:04:35.160 align:start position:0% those transactions is a zero knowledge 00:04:35.160 --> 00:04:36.950 align:start position:0% those transactions is a zero knowledge proof<00:04:35.460> saying<00:04:35.699> that<00:04:35.759> 10<00:04:36.240> 000<00:04:36.360> transactions 00:04:36.950 --> 00:04:36.960 align:start position:0% proof saying that 10 000 transactions 00:04:36.960 --> 00:04:39.350 align:start position:0% proof saying that 10 000 transactions are<00:04:37.500> correct<00:04:37.800> in<00:04:37.919> payments<00:04:38.400> that's<00:04:39.180> the 00:04:39.350 --> 00:04:39.360 align:start position:0% are correct in payments that's the 00:04:39.360 --> 00:04:41.030 align:start position:0% are correct in payments that's the theory<00:04:39.660> that's<00:04:40.080> the<00:04:40.259> pitch<00:04:40.380> deck<00:04:40.740> everyone's 00:04:41.030 --> 00:04:41.040 align:start position:0% theory that's the pitch deck everyone's 00:04:41.040 --> 00:04:42.290 align:start position:0% theory that's the pitch deck everyone's raising<00:04:41.340> off<00:04:41.520> of 00:04:42.290 --> 00:04:42.300 align:start position:0% raising off of 00:04:42.300 --> 00:04:44.570 align:start position:0% raising off of okay<00:04:42.900> this<00:04:43.680> is<00:04:43.800> great<00:04:43.919> there's<00:04:44.220> really 00:04:44.570 --> 00:04:44.580 align:start position:0% okay this is great there's really 00:04:44.580 --> 00:04:46.010 align:start position:0% okay this is great there's really nothing<00:04:44.820> wrong<00:04:45.060> with<00:04:45.180> here<00:04:45.419> this<00:04:45.600> is<00:04:45.780> a<00:04:45.900> lot<00:04:45.960> of 00:04:46.010 --> 00:04:46.020 align:start position:0% nothing wrong with here this is a lot of 00:04:46.020 --> 00:04:47.330 align:start position:0% nothing wrong with here this is a lot of brilliant<00:04:46.320> work<00:04:46.440> has<00:04:46.620> been<00:04:46.800> done<00:04:46.979> on<00:04:47.100> this<00:04:47.220> I 00:04:47.330 --> 00:04:47.340 align:start position:0% brilliant work has been done on this I 00:04:47.340 --> 00:04:49.670 align:start position:0% brilliant work has been done on this I don't<00:04:47.460> mean<00:04:47.580> to<00:04:47.820> Bly<00:04:48.300> people<00:04:48.479> on<00:04:48.660> it<00:04:49.139> there's 00:04:49.670 --> 00:04:49.680 align:start position:0% don't mean to Bly people on it there's 00:04:49.680 --> 00:04:50.450 align:start position:0% don't mean to Bly people on it there's just 00:04:50.450 --> 00:04:50.460 align:start position:0% just 00:04:50.460 --> 00:04:52.610 align:start position:0% just as<00:04:50.759> a<00:04:50.940> cryptography<00:04:51.419> Professor<00:04:51.900> the<00:04:52.380> thing 00:04:52.610 --> 00:04:52.620 align:start position:0% as a cryptography Professor the thing 00:04:52.620 --> 00:04:55.909 align:start position:0% as a cryptography Professor the thing that<00:04:52.740> kind<00:04:52.919> of<00:04:53.040> bothers<00:04:53.340> me<00:04:53.460> uh<00:04:54.300> Z<00:04:54.600> kpms<00:04:55.199> and<00:04:55.259> ZK 00:04:55.909 --> 00:04:55.919 align:start position:0% that kind of bothers me uh Z kpms and ZK 00:04:55.919 --> 00:04:58.430 align:start position:0% that kind of bothers me uh Z kpms and ZK Roll-Ups<00:04:56.460> aren't<00:04:56.820> zero<00:04:57.240> knowledge 00:04:58.430 --> 00:04:58.440 align:start position:0% Roll-Ups aren't zero knowledge 00:04:58.440 --> 00:05:00.530 align:start position:0% Roll-Ups aren't zero knowledge uh<00:04:59.160> they<00:04:59.580> compress<00:04:59.820> transactions<00:05:00.419> on 00:05:00.530 --> 00:05:00.540 align:start position:0% uh they compress transactions on 00:05:00.540 --> 00:05:02.870 align:start position:0% uh they compress transactions on blockchains<00:05:01.199> you<00:05:02.040> don't<00:05:02.220> need<00:05:02.460> to<00:05:02.639> hide 00:05:02.870 --> 00:05:02.880 align:start position:0% blockchains you don't need to hide 00:05:02.880 --> 00:05:05.090 align:start position:0% blockchains you don't need to hide what's<00:05:03.120> going<00:05:03.300> on<00:05:03.479> to<00:05:03.720> do<00:05:03.900> that<00:05:04.080> you<00:05:04.800> just<00:05:04.919> need 00:05:05.090 --> 00:05:05.100 align:start position:0% what's going on to do that you just need 00:05:05.100 --> 00:05:06.650 align:start position:0% what's going on to do that you just need things<00:05:05.340> that<00:05:05.580> are<00:05:05.699> faster<00:05:05.940> and<00:05:06.180> smaller<00:05:06.479> to 00:05:06.650 --> 00:05:06.660 align:start position:0% things that are faster and smaller to 00:05:06.660 --> 00:05:08.689 align:start position:0% things that are faster and smaller to verify<00:05:06.960> there's<00:05:07.199> no<00:05:07.740> notion<00:05:08.280> that<00:05:08.460> this<00:05:08.580> has 00:05:08.689 --> 00:05:08.699 align:start position:0% verify there's no notion that this has 00:05:08.699 --> 00:05:10.310 align:start position:0% verify there's no notion that this has to<00:05:08.820> hide<00:05:09.000> what's<00:05:09.180> going<00:05:09.419> on 00:05:10.310 --> 00:05:10.320 align:start position:0% to hide what's going on 00:05:10.320 --> 00:05:13.310 align:start position:0% to hide what's going on and<00:05:11.040> in<00:05:11.280> fact<00:05:11.460> they<00:05:12.360> likely<00:05:12.720> aren't<00:05:13.080> going<00:05:13.259> to 00:05:13.310 --> 00:05:13.320 align:start position:0% and in fact they likely aren't going to 00:05:13.320 --> 00:05:15.050 align:start position:0% and in fact they likely aren't going to hide<00:05:13.500> your<00:05:13.680> data<00:05:14.040> and<00:05:14.400> so<00:05:14.580> this<00:05:14.759> is<00:05:14.880> going<00:05:15.000> to 00:05:15.050 --> 00:05:15.060 align:start position:0% hide your data and so this is going to 00:05:15.060 --> 00:05:16.670 align:start position:0% hide your data and so this is going to be<00:05:15.120> surprising<00:05:15.479> to<00:05:15.660> some<00:05:15.780> of<00:05:15.900> you 00:05:16.670 --> 00:05:16.680 align:start position:0% be surprising to some of you 00:05:16.680 --> 00:05:18.530 align:start position:0% be surprising to some of you um<00:05:16.740> of<00:05:16.919> course<00:05:17.040> ZK<00:05:17.340> Roll-Ups<00:05:17.880> usually<00:05:18.120> reveal 00:05:18.530 --> 00:05:18.540 align:start position:0% um of course ZK Roll-Ups usually reveal 00:05:18.540 --> 00:05:19.969 align:start position:0% um of course ZK Roll-Ups usually reveal the<00:05:18.780> miracle<00:05:19.139> hash<00:05:19.320> of<00:05:19.500> the<00:05:19.560> data<00:05:19.800> they're 00:05:19.969 --> 00:05:19.979 align:start position:0% the miracle hash of the data they're 00:05:19.979 --> 00:05:21.830 align:start position:0% the miracle hash of the data they're dealing<00:05:20.340> with<00:05:20.880> that's<00:05:21.360> kind<00:05:21.540> of<00:05:21.660> obvious 00:05:21.830 --> 00:05:21.840 align:start position:0% dealing with that's kind of obvious 00:05:21.840 --> 00:05:23.090 align:start position:0% dealing with that's kind of obvious there's<00:05:22.020> a<00:05:22.199> zero<00:05:22.440> knowledge<00:05:22.620> proof<00:05:22.860> about<00:05:22.979> it 00:05:23.090 --> 00:05:23.100 align:start position:0% there's a zero knowledge proof about it 00:05:23.100 --> 00:05:24.770 align:start position:0% there's a zero knowledge proof about it but<00:05:23.220> they're<00:05:23.340> reviewing<00:05:23.580> the<00:05:23.699> miracle<00:05:24.000> hash 00:05:24.770 --> 00:05:24.780 align:start position:0% but they're reviewing the miracle hash 00:05:24.780 --> 00:05:27.050 align:start position:0% but they're reviewing the miracle hash and<00:05:25.320> that<00:05:25.500> hash<00:05:25.740> actually<00:05:26.400> reveals<00:05:26.820> a<00:05:26.940> bunch 00:05:27.050 --> 00:05:27.060 align:start position:0% and that hash actually reveals a bunch 00:05:27.060 --> 00:05:29.870 align:start position:0% and that hash actually reveals a bunch of<00:05:27.240> data<00:05:27.539> in<00:05:28.020> much<00:05:28.139> the<00:05:28.380> same<00:05:28.560> way<00:05:28.740> that<00:05:29.220> uh<00:05:29.639> say 00:05:29.870 --> 00:05:29.880 align:start position:0% of data in much the same way that uh say 00:05:29.880 --> 00:05:31.550 align:start position:0% of data in much the same way that uh say publishing<00:05:30.360> the<00:05:30.479> hash<00:05:30.660> of<00:05:30.900> your<00:05:31.020> password<00:05:31.199> is 00:05:31.550 --> 00:05:31.560 align:start position:0% publishing the hash of your password is 00:05:31.560 --> 00:05:33.409 align:start position:0% publishing the hash of your password is going<00:05:31.740> to<00:05:31.800> reveal<00:05:32.100> your<00:05:32.460> password<00:05:32.639> people<00:05:33.240> can 00:05:33.409 --> 00:05:33.419 align:start position:0% going to reveal your password people can 00:05:33.419 --> 00:05:35.210 align:start position:0% going to reveal your password people can Brute<00:05:33.660> Force<00:05:33.960> these<00:05:34.259> things 00:05:35.210 --> 00:05:35.220 align:start position:0% Brute Force these things 00:05:35.220 --> 00:05:36.890 align:start position:0% Brute Force these things and<00:05:35.520> it<00:05:35.639> wouldn't<00:05:35.820> matter<00:05:36.120> if<00:05:36.479> you<00:05:36.600> when<00:05:36.780> you 00:05:36.890 --> 00:05:36.900 align:start position:0% and it wouldn't matter if you when you 00:05:36.900 --> 00:05:38.330 align:start position:0% and it wouldn't matter if you when you publish<00:05:37.139> the<00:05:37.320> hash<00:05:37.440> of<00:05:37.680> your<00:05:37.800> passwords<00:05:38.160> that 00:05:38.330 --> 00:05:38.340 align:start position:0% publish the hash of your passwords that 00:05:38.340 --> 00:05:40.490 align:start position:0% publish the hash of your passwords that uses<00:05:38.699> zero<00:05:38.940> knowledge<00:05:39.240> proof<00:05:39.539> that<00:05:39.840> it<00:05:40.199> meets 00:05:40.490 --> 00:05:40.500 align:start position:0% uses zero knowledge proof that it meets 00:05:40.500 --> 00:05:41.990 align:start position:0% uses zero knowledge proof that it meets whatever<00:05:40.620> ridiculous<00:05:41.280> password<00:05:41.460> policy 00:05:41.990 --> 00:05:42.000 align:start position:0% whatever ridiculous password policy 00:05:42.000 --> 00:05:43.790 align:start position:0% whatever ridiculous password policy there<00:05:42.180> is<00:05:42.300> you<00:05:42.600> know<00:05:42.660> three<00:05:43.259> uppercase 00:05:43.790 --> 00:05:43.800 align:start position:0% there is you know three uppercase 00:05:43.800 --> 00:05:45.770 align:start position:0% there is you know three uppercase characters<00:05:44.039> a<00:05:44.460> symbol<00:05:45.000> and<00:05:45.240> hey<00:05:45.419> let's<00:05:45.600> throw 00:05:45.770 --> 00:05:45.780 align:start position:0% characters a symbol and hey let's throw 00:05:45.780 --> 00:05:47.930 align:start position:0% characters a symbol and hey let's throw into<00:05:45.960> my<00:05:46.139> Emojis<00:05:46.440> for<00:05:46.620> good<00:05:46.740> effort 00:05:47.930 --> 00:05:47.940 align:start position:0% into my Emojis for good effort 00:05:47.940 --> 00:05:49.189 align:start position:0% into my Emojis for good effort that's<00:05:48.479> not<00:05:48.660> going<00:05:48.780> to<00:05:48.840> help<00:05:48.900> with<00:05:49.080> the 00:05:49.189 --> 00:05:49.199 align:start position:0% that's not going to help with the 00:05:49.199 --> 00:05:51.170 align:start position:0% that's not going to help with the Privacy<00:05:49.500> problem<00:05:49.680> here<00:05:49.919> and<00:05:50.580> so<00:05:50.759> this<00:05:51.120> is 00:05:51.170 --> 00:05:51.180 align:start position:0% Privacy problem here and so this is 00:05:51.180 --> 00:05:53.749 align:start position:0% Privacy problem here and so this is going<00:05:51.360> to<00:05:51.360> become<00:05:51.660> an<00:05:51.780> issue<00:05:52.500> now<00:05:53.160> maybe<00:05:53.520> it's 00:05:53.749 --> 00:05:53.759 align:start position:0% going to become an issue now maybe it's 00:05:53.759 --> 00:05:55.370 align:start position:0% going to become an issue now maybe it's just<00:05:53.940> in<00:05:54.120> theory<00:05:54.419> maybe<00:05:54.660> it's<00:05:54.840> hard<00:05:55.020> to<00:05:55.139> Brute 00:05:55.370 --> 00:05:55.380 align:start position:0% just in theory maybe it's hard to Brute 00:05:55.380 --> 00:05:58.090 align:start position:0% just in theory maybe it's hard to Brute Force<00:05:55.680> this<00:05:55.860> stuff<00:05:56.180> uh<00:05:57.180> on<00:05:57.479> the<00:05:57.600> other<00:05:57.720> hand 00:05:58.090 --> 00:05:58.100 align:start position:0% Force this stuff uh on the other hand 00:05:58.100 --> 00:06:00.529 align:start position:0% Force this stuff uh on the other hand ethereum<00:05:59.100> just<00:05:59.340> moved<00:05:59.580> to<00:05:59.699> proof<00:06:00.060> of<00:06:00.120> stake<00:06:00.360> so 00:06:00.529 --> 00:06:00.539 align:start position:0% ethereum just moved to proof of stake so 00:06:00.539 --> 00:06:02.270 align:start position:0% ethereum just moved to proof of stake so there<00:06:00.660> were<00:06:00.780> a<00:06:00.900> lot<00:06:00.960> of<00:06:01.020> angry<00:06:01.380> miners<00:06:01.860> which<00:06:02.100> a 00:06:02.270 --> 00:06:02.280 align:start position:0% there were a lot of angry miners which a 00:06:02.280 --> 00:06:04.249 align:start position:0% there were a lot of angry miners which a bunch<00:06:02.460> of<00:06:02.580> hashing<00:06:03.000> Hardware<00:06:03.180> who<00:06:04.020> don't<00:06:04.139> know 00:06:04.249 --> 00:06:04.259 align:start position:0% bunch of hashing Hardware who don't know 00:06:04.259 --> 00:06:05.629 align:start position:0% bunch of hashing Hardware who don't know what<00:06:04.380> to<00:06:04.560> do<00:06:04.620> with<00:06:04.800> it 00:06:05.629 --> 00:06:05.639 align:start position:0% what to do with it 00:06:05.639 --> 00:06:07.490 align:start position:0% what to do with it so<00:06:06.120> if<00:06:06.240> this<00:06:06.419> ends<00:06:06.660> up<00:06:06.660> being<00:06:06.780> an<00:06:06.900> Mev<00:06:07.259> thing 00:06:07.490 --> 00:06:07.500 align:start position:0% so if this ends up being an Mev thing 00:06:07.500 --> 00:06:09.890 align:start position:0% so if this ends up being an Mev thing you<00:06:08.160> might<00:06:08.340> have<00:06:08.460> some<00:06:08.639> problems 00:06:09.890 --> 00:06:09.900 align:start position:0% you might have some problems 00:06:09.900 --> 00:06:10.550 align:start position:0% you might have some problems um 00:06:10.550 --> 00:06:10.560 align:start position:0% um 00:06:10.560 --> 00:06:12.950 align:start position:0% um either<00:06:10.919> way<00:06:11.160> it's<00:06:11.460> not<00:06:11.639> zero<00:06:12.000> knowledge<00:06:12.300> and 00:06:12.950 --> 00:06:12.960 align:start position:0% either way it's not zero knowledge and 00:06:12.960 --> 00:06:14.510 align:start position:0% either way it's not zero knowledge and so<00:06:13.080> in<00:06:13.199> my<00:06:13.380> perspective<00:06:13.740> this<00:06:14.039> is<00:06:14.160> kind<00:06:14.340> of 00:06:14.510 --> 00:06:14.520 align:start position:0% so in my perspective this is kind of 00:06:14.520 --> 00:06:17.150 align:start position:0% so in my perspective this is kind of boring<00:06:15.180> from<00:06:15.720> a<00:06:15.900> ZK<00:06:16.199> standpoint<00:06:16.680> because<00:06:16.919> it 00:06:17.150 --> 00:06:17.160 align:start position:0% boring from a ZK standpoint because it 00:06:17.160 --> 00:06:18.590 align:start position:0% boring from a ZK standpoint because it just<00:06:17.280> isn't<00:06:17.639> using<00:06:17.940> the<00:06:18.060> thing<00:06:18.180> that's<00:06:18.360> cool 00:06:18.590 --> 00:06:18.600 align:start position:0% just isn't using the thing that's cool 00:06:18.600 --> 00:06:19.790 align:start position:0% just isn't using the thing that's cool and<00:06:18.780> fascinating<00:06:19.080> about<00:06:19.199> zero<00:06:19.560> knowledge 00:06:19.790 --> 00:06:19.800 align:start position:0% and fascinating about zero knowledge 00:06:19.800 --> 00:06:22.370 align:start position:0% and fascinating about zero knowledge proofs<00:06:20.220> sure<00:06:20.699> you<00:06:21.060> need<00:06:21.180> faster<00:06:21.419> proofs 00:06:22.370 --> 00:06:22.380 align:start position:0% proofs sure you need faster proofs 00:06:22.380 --> 00:06:24.230 align:start position:0% proofs sure you need faster proofs that's<00:06:22.860> quite<00:06:23.100> nice<00:06:23.280> this<00:06:23.639> will<00:06:23.759> get<00:06:23.940> you<00:06:24.060> all 00:06:24.230 --> 00:06:24.240 align:start position:0% that's quite nice this will get you all 00:06:24.240 --> 00:06:25.730 align:start position:0% that's quite nice this will get you all kinds<00:06:24.479> of<00:06:24.479> cool<00:06:24.720> technology<00:06:25.139> and<00:06:25.319> I'm<00:06:25.440> glad<00:06:25.620> it 00:06:25.730 --> 00:06:25.740 align:start position:0% kinds of cool technology and I'm glad it 00:06:25.740 --> 00:06:27.950 align:start position:0% kinds of cool technology and I'm glad it exists<00:06:26.160> but<00:06:26.940> it's<00:06:27.120> it's<00:06:27.360> skipping<00:06:27.840> the 00:06:27.950 --> 00:06:27.960 align:start position:0% exists but it's it's skipping the 00:06:27.960 --> 00:06:29.990 align:start position:0% exists but it's it's skipping the interesting<00:06:28.319> bits<00:06:28.680> right<00:06:29.280> and<00:06:29.580> so<00:06:29.699> at<00:06:29.819> the<00:06:29.940> end 00:06:29.990 --> 00:06:30.000 align:start position:0% interesting bits right and so at the end 00:06:30.000 --> 00:06:32.150 align:start position:0% interesting bits right and so at the end of<00:06:30.120> the<00:06:30.180> day<00:06:30.300> zkvms<00:06:31.259> are<00:06:31.500> not<00:06:31.620> a<00:06:31.740> significant 00:06:32.150 --> 00:06:32.160 align:start position:0% of the day zkvms are not a significant 00:06:32.160 --> 00:06:34.430 align:start position:0% of the day zkvms are not a significant source<00:06:33.060> of<00:06:33.120> zero<00:06:33.479> knowledge<00:06:33.720> they're<00:06:34.139> sort<00:06:34.319> of 00:06:34.430 --> 00:06:34.440 align:start position:0% source of zero knowledge they're sort of 00:06:34.440 --> 00:06:35.870 align:start position:0% source of zero knowledge they're sort of nutritionally<00:06:34.979> defunct<00:06:35.580> from<00:06:35.759> this 00:06:35.870 --> 00:06:35.880 align:start position:0% nutritionally defunct from this 00:06:35.880 --> 00:06:37.670 align:start position:0% nutritionally defunct from this perspective<00:06:36.479> they<00:06:36.960> don't<00:06:37.080> give<00:06:37.199> us<00:06:37.319> what<00:06:37.500> we 00:06:37.670 --> 00:06:37.680 align:start position:0% perspective they don't give us what we 00:06:37.680 --> 00:06:38.809 align:start position:0% perspective they don't give us what we want 00:06:38.809 --> 00:06:38.819 align:start position:0% want 00:06:38.819 --> 00:06:42.350 align:start position:0% want um<00:06:39.360> and<00:06:40.259> again<00:06:40.919> this<00:06:41.639> is<00:06:41.759> not<00:06:41.880> to<00:06:42.060> say<00:06:42.180> this 00:06:42.350 --> 00:06:42.360 align:start position:0% um and again this is not to say this 00:06:42.360 --> 00:06:44.270 align:start position:0% um and again this is not to say this stuff<00:06:42.479> isn't<00:06:42.780> useful<00:06:43.080> it's<00:06:43.500> driving<00:06:43.740> serious 00:06:44.270 --> 00:06:44.280 align:start position:0% stuff isn't useful it's driving serious 00:06:44.280 --> 00:06:45.950 align:start position:0% stuff isn't useful it's driving serious Innovation<00:06:44.699> and<00:06:44.880> zero<00:06:45.180> knowledge<00:06:45.419> proofs<00:06:45.720> the 00:06:45.950 --> 00:06:45.960 align:start position:0% Innovation and zero knowledge proofs the 00:06:45.960 --> 00:06:49.070 align:start position:0% Innovation and zero knowledge proofs the things<00:06:46.080> I<00:06:46.319> worked<00:06:46.620> on<00:06:46.740> in<00:06:47.160> 2012<00:06:47.819> in<00:06:48.419> 2017<00:06:48.780> when 00:06:49.070 --> 00:06:49.080 align:start position:0% things I worked on in 2012 in 2017 when 00:06:49.080 --> 00:06:50.469 align:start position:0% things I worked on in 2012 in 2017 when we<00:06:49.259> wrote<00:06:49.380> sexy<00:06:49.800> which<00:06:49.979> were<00:06:50.160> like 00:06:50.469 --> 00:06:50.479 align:start position:0% we wrote sexy which were like 00:06:50.479 --> 00:06:53.090 align:start position:0% we wrote sexy which were like implausibly<00:06:51.479> slow<00:06:51.720> at<00:06:51.960> the<00:06:52.139> time<00:06:52.259> are<00:06:52.919> now 00:06:53.090 --> 00:06:53.100 align:start position:0% implausibly slow at the time are now 00:06:53.100 --> 00:06:54.710 align:start position:0% implausibly slow at the time are now practical<00:06:53.520> in<00:06:53.759> part<00:06:54.000> because<00:06:54.180> of<00:06:54.360> the<00:06:54.419> r<00:06:54.539> d 00:06:54.710 --> 00:06:54.720 align:start position:0% practical in part because of the r d 00:06:54.720 --> 00:06:56.090 align:start position:0% practical in part because of the r d that's<00:06:55.020> been<00:06:55.199> funded<00:06:55.500> by<00:06:55.680> the<00:06:55.800> companies 00:06:56.090 --> 00:06:56.100 align:start position:0% that's been funded by the companies 00:06:56.100 --> 00:06:57.710 align:start position:0% that's been funded by the companies doing<00:06:56.340> this 00:06:57.710 --> 00:06:57.720 align:start position:0% doing this 00:06:57.720 --> 00:06:59.510 align:start position:0% doing this and<00:06:58.139> so<00:06:58.199> that's<00:06:58.380> incredibly<00:06:58.860> useful<00:06:59.160> it's<00:06:59.340> a 00:06:59.510 --> 00:06:59.520 align:start position:0% and so that's incredibly useful it's a 00:06:59.520 --> 00:07:00.890 align:start position:0% and so that's incredibly useful it's a bunch<00:06:59.639> of<00:06:59.759> tooling<00:07:00.060> that<00:07:00.180> I<00:07:00.300> as<00:07:00.419> a<00:07:00.600> researcher 00:07:00.890 --> 00:07:00.900 align:start position:0% bunch of tooling that I as a researcher 00:07:00.900 --> 00:07:02.390 align:start position:0% bunch of tooling that I as a researcher can<00:07:01.139> use 00:07:02.390 --> 00:07:02.400 align:start position:0% can use 00:07:02.400 --> 00:07:03.830 align:start position:0% can use um and<00:07:02.880> so<00:07:02.940> I<00:07:03.060> sort<00:07:03.240> of<00:07:03.360> think<00:07:03.479> about<00:07:03.600> this 00:07:03.830 --> 00:07:03.840 align:start position:0% um and so I sort of think about this 00:07:03.840 --> 00:07:05.870 align:start position:0% um and so I sort of think about this like<00:07:04.020> the<00:07:04.199> 1980s<00:07:04.740> and<00:07:04.860> 1990s<00:07:05.400> when<00:07:05.580> people<00:07:05.759> are 00:07:05.870 --> 00:07:05.880 align:start position:0% like the 1980s and 1990s when people are 00:07:05.880 --> 00:07:07.430 align:start position:0% like the 1980s and 1990s when people are building<00:07:06.060> faster<00:07:06.419> computer<00:07:06.720> processors 00:07:07.430 --> 00:07:07.440 align:start position:0% building faster computer processors 00:07:07.440 --> 00:07:09.230 align:start position:0% building faster computer processors these<00:07:08.160> things<00:07:08.280> were<00:07:08.460> tools<00:07:08.759> we<00:07:08.940> could<00:07:09.000> use<00:07:09.120> to 00:07:09.230 --> 00:07:09.240 align:start position:0% these things were tools we could use to 00:07:09.240 --> 00:07:11.390 align:start position:0% these things were tools we could use to do<00:07:09.360> anything<00:07:09.539> we<00:07:09.780> wanted<00:07:09.960> what<00:07:10.860> was<00:07:11.100> driving 00:07:11.390 --> 00:07:11.400 align:start position:0% do anything we wanted what was driving 00:07:11.400 --> 00:07:13.490 align:start position:0% do anything we wanted what was driving people<00:07:11.759> doing<00:07:12.060> them<00:07:12.360> was<00:07:12.660> you<00:07:13.020> know<00:07:13.080> faster 00:07:13.490 --> 00:07:13.500 align:start position:0% people doing them was you know faster 00:07:13.500 --> 00:07:16.189 align:start position:0% people doing them was you know faster spreadsheets<00:07:14.100> for<00:07:14.280> offices<00:07:14.840> uh<00:07:15.840> kind<00:07:16.020> of<00:07:16.080> like 00:07:16.189 --> 00:07:16.199 align:start position:0% spreadsheets for offices uh kind of like 00:07:16.199 --> 00:07:17.629 align:start position:0% spreadsheets for offices uh kind of like what's<00:07:16.440> driving<00:07:16.680> people<00:07:16.979> now<00:07:17.160> is<00:07:17.400> faster 00:07:17.629 --> 00:07:17.639 align:start position:0% what's driving people now is faster 00:07:17.639 --> 00:07:19.749 align:start position:0% what's driving people now is faster spreadsheets<00:07:18.240> on<00:07:18.360> a<00:07:18.479> blockchain 00:07:19.749 --> 00:07:19.759 align:start position:0% spreadsheets on a blockchain 00:07:19.759 --> 00:07:22.550 align:start position:0% spreadsheets on a blockchain uh<00:07:20.759> so<00:07:21.360> you<00:07:21.720> can<00:07:21.840> do<00:07:21.960> this<00:07:22.080> that's<00:07:22.380> great 00:07:22.550 --> 00:07:22.560 align:start position:0% uh so you can do this that's great 00:07:22.560 --> 00:07:23.689 align:start position:0% uh so you can do this that's great there's<00:07:22.740> nothing<00:07:22.919> wrong<00:07:23.160> with<00:07:23.280> it<00:07:23.400> you<00:07:23.580> can 00:07:23.689 --> 00:07:23.699 align:start position:0% there's nothing wrong with it you can 00:07:23.699 --> 00:07:25.129 align:start position:0% there's nothing wrong with it you can also<00:07:23.880> nerd<00:07:24.240> out<00:07:24.360> on<00:07:24.599> exactly<00:07:24.900> what<00:07:25.080> you're 00:07:25.129 --> 00:07:25.139 align:start position:0% also nerd out on exactly what you're 00:07:25.139 --> 00:07:26.150 align:start position:0% also nerd out on exactly what you're going<00:07:25.259> to<00:07:25.319> do<00:07:25.440> for<00:07:25.560> the<00:07:25.680> zero<00:07:25.919> knowledge 00:07:26.150 --> 00:07:26.160 align:start position:0% going to do for the zero knowledge 00:07:26.160 --> 00:07:28.010 align:start position:0% going to do for the zero knowledge proofs<00:07:26.460> and<00:07:26.880> just<00:07:27.060> go<00:07:27.240> I<00:07:27.539> don't<00:07:27.660> care<00:07:27.780> what 00:07:28.010 --> 00:07:28.020 align:start position:0% proofs and just go I don't care what 00:07:28.020 --> 00:07:30.170 align:start position:0% proofs and just go I don't care what anyone's<00:07:28.440> voting<00:07:28.680> on<00:07:28.740> an<00:07:28.860> application<00:07:29.220> that's 00:07:30.170 --> 00:07:30.180 align:start position:0% anyone's voting on an application that's 00:07:30.180 --> 00:07:32.629 align:start position:0% anyone's voting on an application that's also<00:07:30.479> fine<00:07:30.720> but<00:07:31.680> some<00:07:31.979> people<00:07:32.160> should<00:07:32.400> dream 00:07:32.629 --> 00:07:32.639 align:start position:0% also fine but some people should dream 00:07:32.639 --> 00:07:34.330 align:start position:0% also fine but some people should dream bigger<00:07:33.060> right<00:07:33.300> just<00:07:33.599> like<00:07:33.720> we<00:07:33.840> did<00:07:34.020> with 00:07:34.330 --> 00:07:34.340 align:start position:0% bigger right just like we did with 00:07:34.340 --> 00:07:36.469 align:start position:0% bigger right just like we did with microprocessors<00:07:35.340> you<00:07:36.000> know<00:07:36.060> build<00:07:36.240> the 00:07:36.469 --> 00:07:36.479 align:start position:0% microprocessors you know build the 00:07:36.479 --> 00:07:38.089 align:start position:0% microprocessors you know build the internet<00:07:36.599> build<00:07:37.020> the<00:07:37.440> metaverse<00:07:37.919> build 00:07:38.089 --> 00:07:38.099 align:start position:0% internet build the metaverse build 00:07:38.099 --> 00:07:39.170 align:start position:0% internet build the metaverse build something 00:07:39.170 --> 00:07:39.180 align:start position:0% something 00:07:39.180 --> 00:07:40.790 align:start position:0% something I<00:07:39.599> don't<00:07:39.660> know<00:07:39.780> what<00:07:39.960> it<00:07:40.080> is 00:07:40.790 --> 00:07:40.800 align:start position:0% I don't know what it is 00:07:40.800 --> 00:07:42.350 align:start position:0% I don't know what it is but<00:07:41.160> we<00:07:41.340> should<00:07:41.460> be<00:07:41.580> thinking<00:07:41.819> about<00:07:41.940> it<00:07:42.120> like 00:07:42.350 --> 00:07:42.360 align:start position:0% but we should be thinking about it like 00:07:42.360 --> 00:07:43.969 align:start position:0% but we should be thinking about it like and<00:07:42.780> so<00:07:42.900> we<00:07:43.020> need<00:07:43.139> to<00:07:43.259> figure<00:07:43.319> out<00:07:43.500> what<00:07:43.860> the 00:07:43.969 --> 00:07:43.979 align:start position:0% and so we need to figure out what the 00:07:43.979 --> 00:07:45.290 align:start position:0% and so we need to figure out what the combination<00:07:44.340> of<00:07:44.520> ZK<00:07:44.819> proofs<00:07:45.240> plus 00:07:45.290 --> 00:07:45.300 align:start position:0% combination of ZK proofs plus 00:07:45.300 --> 00:07:47.330 align:start position:0% combination of ZK proofs plus blockchains<00:07:45.900> can<00:07:46.080> do<00:07:46.199> that<00:07:46.800> isn't<00:07:47.099> just 00:07:47.330 --> 00:07:47.340 align:start position:0% blockchains can do that isn't just 00:07:47.340 --> 00:07:50.330 align:start position:0% blockchains can do that isn't just faster<00:07:47.699> spreadsheets<00:07:48.240> on<00:07:48.419> a<00:07:48.539> blockchain 00:07:50.330 --> 00:07:50.340 align:start position:0% faster spreadsheets on a blockchain 00:07:50.340 --> 00:07:52.129 align:start position:0% faster spreadsheets on a blockchain um<00:07:50.460> it's<00:07:50.940> going<00:07:51.120> to<00:07:51.180> be<00:07:51.240> part<00:07:51.419> of<00:07:51.539> it<00:07:51.660> but<00:07:52.020> it's 00:07:52.129 --> 00:07:52.139 align:start position:0% um it's going to be part of it but it's 00:07:52.139 --> 00:07:54.050 align:start position:0% um it's going to be part of it but it's not<00:07:52.319> going<00:07:52.380> to<00:07:52.500> be<00:07:52.560> everything 00:07:54.050 --> 00:07:54.060 align:start position:0% not going to be everything 00:07:54.060 --> 00:07:56.330 align:start position:0% not going to be everything so<00:07:54.780> this<00:07:55.020> brings<00:07:55.259> me<00:07:55.380> to<00:07:55.560> the<00:07:55.680> question<00:07:55.919> and 00:07:56.330 --> 00:07:56.340 align:start position:0% so this brings me to the question and 00:07:56.340 --> 00:07:57.589 align:start position:0% so this brings me to the question and this<00:07:56.520> is<00:07:56.580> where<00:07:56.819> the<00:07:57.060> sort<00:07:57.240> of<00:07:57.360> technical 00:07:57.589 --> 00:07:57.599 align:start position:0% this is where the sort of technical 00:07:57.599 --> 00:07:59.270 align:start position:0% this is where the sort of technical content<00:07:57.960> of<00:07:58.020> this<00:07:58.199> Talk<00:07:58.380> Stops<00:07:58.800> this<00:07:59.039> is<00:07:59.099> this 00:07:59.270 --> 00:07:59.280 align:start position:0% content of this Talk Stops this is this 00:07:59.280 --> 00:08:01.909 align:start position:0% content of this Talk Stops this is this sort<00:07:59.520> of<00:07:59.639> theory<00:08:00.479> question<00:08:00.900> what<00:08:01.680> is<00:08:01.800> this 00:08:01.909 --> 00:08:01.919 align:start position:0% sort of theory question what is this 00:08:01.919 --> 00:08:03.890 align:start position:0% sort of theory question what is this stuff<00:08:02.099> good<00:08:02.400> for<00:08:02.639> right<00:08:03.240> what<00:08:03.599> are<00:08:03.720> we<00:08:03.840> going 00:08:03.890 --> 00:08:03.900 align:start position:0% stuff good for right what are we going 00:08:03.900 --> 00:08:05.930 align:start position:0% stuff good for right what are we going to<00:08:04.020> do<00:08:04.080> with<00:08:04.199> the<00:08:04.259> zero<00:08:04.560> knowledge<00:08:04.800> proof<00:08:05.160> and 00:08:05.930 --> 00:08:05.940 align:start position:0% to do with the zero knowledge proof and 00:08:05.940 --> 00:08:07.490 align:start position:0% to do with the zero knowledge proof and if<00:08:06.180> you<00:08:06.360> went<00:08:06.479> and<00:08:06.660> took<00:08:06.840> a<00:08:06.960> cryptography 00:08:07.490 --> 00:08:07.500 align:start position:0% if you went and took a cryptography 00:08:07.500 --> 00:08:09.589 align:start position:0% if you went and took a cryptography class<00:08:07.680> uh<00:08:08.400> probably<00:08:08.639> even<00:08:08.940> if<00:08:09.120> you<00:08:09.240> took<00:08:09.419> my 00:08:09.589 --> 00:08:09.599 align:start position:0% class uh probably even if you took my 00:08:09.599 --> 00:08:10.969 align:start position:0% class uh probably even if you took my cryptography<00:08:10.199> class<00:08:10.319> because<00:08:10.560> I'm<00:08:10.680> lazy 00:08:10.969 --> 00:08:10.979 align:start position:0% cryptography class because I'm lazy 00:08:10.979 --> 00:08:12.589 align:start position:0% cryptography class because I'm lazy about<00:08:11.099> writing<00:08:11.520> slides<00:08:11.819> you<00:08:12.240> would<00:08:12.300> get<00:08:12.479> a 00:08:12.589 --> 00:08:12.599 align:start position:0% about writing slides you would get a 00:08:12.599 --> 00:08:14.089 align:start position:0% about writing slides you would get a definition<00:08:12.720> like<00:08:13.199> this<00:08:13.319> which<00:08:13.500> that<00:08:13.740> is<00:08:13.860> zero 00:08:14.089 --> 00:08:14.099 align:start position:0% definition like this which that is zero 00:08:14.099 --> 00:08:15.409 align:start position:0% definition like this which that is zero knowledge<00:08:14.340> proof<00:08:14.639> is<00:08:15.000> a<00:08:15.120> thing<00:08:15.240> with 00:08:15.409 --> 00:08:15.419 align:start position:0% knowledge proof is a thing with 00:08:15.419 --> 00:08:17.990 align:start position:0% knowledge proof is a thing with correctness<00:08:15.900> soundness<00:08:16.500> and<00:08:16.800> zero<00:08:17.160> knowledge 00:08:17.990 --> 00:08:18.000 align:start position:0% correctness soundness and zero knowledge 00:08:18.000 --> 00:08:19.670 align:start position:0% correctness soundness and zero knowledge and<00:08:18.419> this<00:08:18.539> is<00:08:18.599> a<00:08:18.780> very<00:08:18.900> sort<00:08:19.199> of<00:08:19.319> textbook 00:08:19.670 --> 00:08:19.680 align:start position:0% and this is a very sort of textbook 00:08:19.680 --> 00:08:21.770 align:start position:0% and this is a very sort of textbook academic<00:08:20.160> thing<00:08:20.340> it's<00:08:20.580> very<00:08:20.819> dry<00:08:21.120> it<00:08:21.419> does<00:08:21.599> not 00:08:21.770 --> 00:08:21.780 align:start position:0% academic thing it's very dry it does not 00:08:21.780 --> 00:08:24.110 align:start position:0% academic thing it's very dry it does not relate<00:08:22.199> what<00:08:22.500> these<00:08:22.800> things<00:08:22.860> really<00:08:23.220> do<00:08:23.460> so<00:08:24.000> I 00:08:24.110 --> 00:08:24.120 align:start position:0% relate what these things really do so I 00:08:24.120 --> 00:08:25.249 align:start position:0% relate what these things really do so I think<00:08:24.240> we<00:08:24.419> kind<00:08:24.539> of<00:08:24.660> should<00:08:24.780> start<00:08:24.960> thinking 00:08:25.249 --> 00:08:25.259 align:start position:0% think we kind of should start thinking 00:08:25.259 --> 00:08:27.770 align:start position:0% think we kind of should start thinking about<00:08:25.319> them<00:08:25.560> in<00:08:25.800> different<00:08:25.919> terms<00:08:26.419> uh<00:08:27.419> so<00:08:27.599> in 00:08:27.770 --> 00:08:27.780 align:start position:0% about them in different terms uh so in 00:08:27.780 --> 00:08:29.270 align:start position:0% about them in different terms uh so in deliberately<00:08:28.199> non-standard<00:08:28.919> terminology 00:08:29.270 --> 00:08:29.280 align:start position:0% deliberately non-standard terminology 00:08:29.280 --> 00:08:30.830 align:start position:0% deliberately non-standard terminology what<00:08:29.639> is<00:08:29.759> a<00:08:29.879> zero<00:08:30.120> knowledge<00:08:30.360> proof<00:08:30.660> doing 00:08:30.830 --> 00:08:30.840 align:start position:0% what is a zero knowledge proof doing 00:08:30.840 --> 00:08:32.389 align:start position:0% what is a zero knowledge proof doing well 00:08:32.389 --> 00:08:32.399 align:start position:0% well 00:08:32.399 --> 00:08:34.490 align:start position:0% well in<00:08:32.940> my<00:08:33.060> mind<00:08:33.180> it's<00:08:33.360> three<00:08:33.659> things<00:08:33.839> the<00:08:34.380> first 00:08:34.490 --> 00:08:34.500 align:start position:0% in my mind it's three things the first 00:08:34.500 --> 00:08:37.670 align:start position:0% in my mind it's three things the first one<00:08:34.680> is<00:08:34.860> confidentiality<00:08:35.640> it<00:08:36.120> hides<00:08:36.479> data<00:08:37.260> and 00:08:37.670 --> 00:08:37.680 align:start position:0% one is confidentiality it hides data and 00:08:37.680 --> 00:08:39.290 align:start position:0% one is confidentiality it hides data and so<00:08:37.800> that's<00:08:37.919> how<00:08:38.099> we<00:08:38.219> got<00:08:38.399> Z<00:08:38.700> cash<00:08:38.880> that's<00:08:39.180> how 00:08:39.290 --> 00:08:39.300 align:start position:0% so that's how we got Z cash that's how 00:08:39.300 --> 00:08:40.610 align:start position:0% so that's how we got Z cash that's how we<00:08:39.419> got<00:08:39.479> tornado<00:08:39.779> cash<00:08:40.080> that's<00:08:40.260> how<00:08:40.380> you<00:08:40.500> get 00:08:40.610 --> 00:08:40.620 align:start position:0% we got tornado cash that's how you get 00:08:40.620 --> 00:08:41.930 align:start position:0% we got tornado cash that's how you get Aztec<00:08:40.979> you<00:08:41.099> get<00:08:41.279> everything<00:08:41.399> else<00:08:41.640> we're 00:08:41.930 --> 00:08:41.940 align:start position:0% Aztec you get everything else we're 00:08:41.940 --> 00:08:43.430 align:start position:0% Aztec you get everything else we're trying<00:08:42.180> to<00:08:42.300> hide<00:08:42.539> data<00:08:42.839> to<00:08:42.959> get<00:08:43.080> private 00:08:43.430 --> 00:08:43.440 align:start position:0% trying to hide data to get private 00:08:43.440 --> 00:08:45.230 align:start position:0% trying to hide data to get private payments<00:08:44.099> because<00:08:44.279> blockchains<00:08:45.000> or<00:08:45.060> Twitter 00:08:45.230 --> 00:08:45.240 align:start position:0% payments because blockchains or Twitter 00:08:45.240 --> 00:08:46.670 align:start position:0% payments because blockchains or Twitter for<00:08:45.420> your<00:08:45.540> bank<00:08:45.660> account<00:08:45.839> and<00:08:46.440> that<00:08:46.560> sounds 00:08:46.670 --> 00:08:46.680 align:start position:0% for your bank account and that sounds 00:08:46.680 --> 00:08:48.230 align:start position:0% for your bank account and that sounds like<00:08:46.860> a<00:08:46.920> horrendous<00:08:47.339> idea 00:08:48.230 --> 00:08:48.240 align:start position:0% like a horrendous idea 00:08:48.240 --> 00:08:51.230 align:start position:0% like a horrendous idea okay<00:08:48.720> that's<00:08:49.200> thing<00:08:49.440> one<00:08:49.620> thing<00:08:50.279> two<00:08:50.519> for<00:08:50.880> ZK 00:08:51.230 --> 00:08:51.240 align:start position:0% okay that's thing one thing two for ZK 00:08:51.240 --> 00:08:53.690 align:start position:0% okay that's thing one thing two for ZK snark<00:08:51.600> specifically<00:08:52.080> is<00:08:52.740> compression<00:08:53.339> right 00:08:53.690 --> 00:08:53.700 align:start position:0% snark specifically is compression right 00:08:53.700 --> 00:08:55.070 align:start position:0% snark specifically is compression right they<00:08:53.880> take<00:08:54.060> a<00:08:54.180> bunch<00:08:54.300> of<00:08:54.420> data<00:08:54.660> and<00:08:54.899> it's 00:08:55.070 --> 00:08:55.080 align:start position:0% they take a bunch of data and it's 00:08:55.080 --> 00:08:56.750 align:start position:0% they take a bunch of data and it's easier<00:08:55.380> to<00:08:55.500> verify<00:08:55.800> than<00:08:56.040> doing<00:08:56.220> the<00:08:56.459> linear 00:08:56.750 --> 00:08:56.760 align:start position:0% easier to verify than doing the linear 00:08:56.760 --> 00:08:58.430 align:start position:0% easier to verify than doing the linear paths<00:08:57.180> that<00:08:57.360> the<00:08:57.600> actual<00:08:57.779> verification<00:08:58.200> would 00:08:58.430 --> 00:08:58.440 align:start position:0% paths that the actual verification would 00:08:58.440 --> 00:08:59.870 align:start position:0% paths that the actual verification would do<00:08:58.560> without<00:08:58.740> the<00:08:58.980> proof 00:08:59.870 --> 00:08:59.880 align:start position:0% do without the proof 00:08:59.880 --> 00:09:01.250 align:start position:0% do without the proof that's<00:09:00.420> nice<00:09:00.600> that's<00:09:00.899> how<00:09:01.019> you<00:09:01.140> get 00:09:01.250 --> 00:09:01.260 align:start position:0% that's nice that's how you get 00:09:01.260 --> 00:09:02.750 align:start position:0% that's nice that's how you get scalability<00:09:01.740> right<00:09:02.040> this<00:09:02.160> is<00:09:02.339> what's<00:09:02.519> driving 00:09:02.750 --> 00:09:02.760 align:start position:0% scalability right this is what's driving 00:09:02.760 --> 00:09:05.509 align:start position:0% scalability right this is what's driving people's<00:09:03.300> quests<00:09:03.720> to<00:09:04.019> save<00:09:04.140> money<00:09:04.380> on<00:09:04.620> gas 00:09:05.509 --> 00:09:05.519 align:start position:0% people's quests to save money on gas 00:09:05.519 --> 00:09:07.310 align:start position:0% people's quests to save money on gas for<00:09:06.000> blockchains 00:09:07.310 --> 00:09:07.320 align:start position:0% for blockchains 00:09:07.320 --> 00:09:09.710 align:start position:0% for blockchains but<00:09:07.860> the<00:09:08.040> third<00:09:08.220> point<00:09:08.459> is<00:09:09.240> to<00:09:09.420> provide 00:09:09.710 --> 00:09:09.720 align:start position:0% but the third point is to provide 00:09:09.720 --> 00:09:10.730 align:start position:0% but the third point is to provide something<00:09:09.839> which<00:09:10.080> we<00:09:10.260> can<00:09:10.320> think<00:09:10.440> of<00:09:10.560> as 00:09:10.730 --> 00:09:10.740 align:start position:0% something which we can think of as 00:09:10.740 --> 00:09:12.470 align:start position:0% something which we can think of as credibility<00:09:11.220> right<00:09:11.640> so<00:09:11.820> zero<00:09:12.240> knowledge 00:09:12.470 --> 00:09:12.480 align:start position:0% credibility right so zero knowledge 00:09:12.480 --> 00:09:13.970 align:start position:0% credibility right so zero knowledge proof<00:09:12.779> from<00:09:12.959> the<00:09:13.140> cryptography<00:09:13.620> standpoint 00:09:13.970 --> 00:09:13.980 align:start position:0% proof from the cryptography standpoint 00:09:13.980 --> 00:09:15.530 align:start position:0% proof from the cryptography standpoint is<00:09:14.220> sound<00:09:14.459> it<00:09:14.700> gives<00:09:14.880> you<00:09:15.000> some<00:09:15.120> guarantee 00:09:15.530 --> 00:09:15.540 align:start position:0% is sound it gives you some guarantee 00:09:15.540 --> 00:09:17.269 align:start position:0% is sound it gives you some guarantee that<00:09:15.720> some<00:09:15.899> statement<00:09:16.260> is<00:09:16.380> correct 00:09:17.269 --> 00:09:17.279 align:start position:0% that some statement is correct 00:09:17.279 --> 00:09:18.590 align:start position:0% that some statement is correct it<00:09:17.640> doesn't<00:09:17.820> tell<00:09:18.060> you<00:09:18.120> anything<00:09:18.240> about<00:09:18.420> what 00:09:18.590 --> 00:09:18.600 align:start position:0% it doesn't tell you anything about what 00:09:18.600 --> 00:09:20.210 align:start position:0% it doesn't tell you anything about what you<00:09:18.720> can<00:09:18.779> do<00:09:18.899> with<00:09:19.019> it<00:09:19.140> credibility<00:09:19.800> is<00:09:20.100> this 00:09:20.210 --> 00:09:20.220 align:start position:0% you can do with it credibility is this 00:09:20.220 --> 00:09:21.769 align:start position:0% you can do with it credibility is this point<00:09:20.339> if<00:09:20.459> I<00:09:20.640> give<00:09:20.820> you<00:09:20.940> a<00:09:21.060> piece<00:09:21.300> of<00:09:21.360> data<00:09:21.600> I 00:09:21.769 --> 00:09:21.779 align:start position:0% point if I give you a piece of data I 00:09:21.779 --> 00:09:23.389 align:start position:0% point if I give you a piece of data I can<00:09:21.899> use<00:09:22.080> a<00:09:22.200> zero<00:09:22.500> knowledge<00:09:22.800> proof<00:09:23.100> to<00:09:23.220> show 00:09:23.389 --> 00:09:23.399 align:start position:0% can use a zero knowledge proof to show 00:09:23.399 --> 00:09:24.949 align:start position:0% can use a zero knowledge proof to show to<00:09:23.580> you<00:09:23.700> that<00:09:24.060> it<00:09:24.180> really<00:09:24.300> is<00:09:24.480> the<00:09:24.660> data<00:09:24.839> you're 00:09:24.949 --> 00:09:24.959 align:start position:0% to you that it really is the data you're 00:09:24.959 --> 00:09:26.210 align:start position:0% to you that it really is the data you're supposed<00:09:25.140> to<00:09:25.260> be<00:09:25.320> looking<00:09:25.440> at<00:09:25.620> it<00:09:25.800> really<00:09:25.980> was 00:09:26.210 --> 00:09:26.220 align:start position:0% supposed to be looking at it really was 00:09:26.220 --> 00:09:28.190 align:start position:0% supposed to be looking at it really was computed<00:09:26.700> on<00:09:26.820> correctly 00:09:28.190 --> 00:09:28.200 align:start position:0% computed on correctly 00:09:28.200 --> 00:09:30.530 align:start position:0% computed on correctly um<00:09:28.260> and<00:09:28.800> this<00:09:29.220> actually 00:09:30.530 --> 00:09:30.540 align:start position:0% um and this actually 00:09:30.540 --> 00:09:32.650 align:start position:0% um and this actually Okay<00:09:31.019> so 00:09:32.650 --> 00:09:32.660 align:start position:0% Okay so 00:09:32.660 --> 00:09:35.570 align:start position:0% Okay so uh<00:09:33.660> the<00:09:34.200> idea<00:09:34.500> here<00:09:34.740> comes<00:09:35.100> from<00:09:35.160> a<00:09:35.339> piece<00:09:35.519> of 00:09:35.570 --> 00:09:35.580 align:start position:0% uh the idea here comes from a piece of 00:09:35.580 --> 00:09:36.530 align:start position:0% uh the idea here comes from a piece of research<00:09:35.820> done<00:09:36.000> by<00:09:36.180> some<00:09:36.360> of<00:09:36.420> my 00:09:36.530 --> 00:09:36.540 align:start position:0% research done by some of my 00:09:36.540 --> 00:09:38.329 align:start position:0% research done by some of my collaborators<00:09:37.080> back<00:09:37.320> before<00:09:37.440> I<00:09:37.620> knew<00:09:37.800> them<00:09:38.040> uh 00:09:38.329 --> 00:09:38.339 align:start position:0% collaborators back before I knew them uh 00:09:38.339 --> 00:09:40.610 align:start position:0% collaborators back before I knew them uh called<00:09:38.459> proof<00:09:38.820> carrying<00:09:39.180> data<00:09:39.540> in<00:09:39.720> 2010<00:09:40.260> and 00:09:40.610 --> 00:09:40.620 align:start position:0% called proof carrying data in 2010 and 00:09:40.620 --> 00:09:42.170 align:start position:0% called proof carrying data in 2010 and this<00:09:40.800> was<00:09:40.860> really<00:09:41.040> before<00:09:41.339> blockchains<00:09:42.060> were 00:09:42.170 --> 00:09:42.180 align:start position:0% this was really before blockchains were 00:09:42.180 --> 00:09:44.210 align:start position:0% this was really before blockchains were a<00:09:42.360> major<00:09:42.540> thing<00:09:42.720> at<00:09:42.899> least<00:09:43.019> in<00:09:43.140> Academia<00:09:43.680> and 00:09:44.210 --> 00:09:44.220 align:start position:0% a major thing at least in Academia and 00:09:44.220 --> 00:09:46.130 align:start position:0% a major thing at least in Academia and the<00:09:44.279> idea<00:09:44.519> was<00:09:44.700> you<00:09:44.880> have<00:09:45.060> data 00:09:46.130 --> 00:09:46.140 align:start position:0% the idea was you have data 00:09:46.140 --> 00:09:48.110 align:start position:0% the idea was you have data never<00:09:46.680> mind<00:09:46.860> where<00:09:47.100> again<00:09:47.580> they<00:09:47.880> didn't<00:09:48.000> know 00:09:48.110 --> 00:09:48.120 align:start position:0% never mind where again they didn't know 00:09:48.120 --> 00:09:49.490 align:start position:0% never mind where again they didn't know about<00:09:48.180> blockchains<00:09:48.839> and<00:09:49.019> the<00:09:49.140> data<00:09:49.380> has 00:09:49.490 --> 00:09:49.500 align:start position:0% about blockchains and the data has 00:09:49.500 --> 00:09:50.930 align:start position:0% about blockchains and the data has proofs<00:09:49.860> attached<00:09:50.160> to<00:09:50.279> it<00:09:50.399> that<00:09:50.820> the 00:09:50.930 --> 00:09:50.940 align:start position:0% proofs attached to it that the 00:09:50.940 --> 00:09:52.730 align:start position:0% proofs attached to it that the computations<00:09:51.720> are<00:09:52.080> correct<00:09:52.320> that<00:09:52.500> was<00:09:52.620> done 00:09:52.730 --> 00:09:52.740 align:start position:0% computations are correct that was done 00:09:52.740 --> 00:09:54.470 align:start position:0% computations are correct that was done to<00:09:52.860> produce<00:09:53.100> the<00:09:53.279> data<00:09:53.519> so<00:09:53.820> you<00:09:54.240> have<00:09:54.360> some 00:09:54.470 --> 00:09:54.480 align:start position:0% to produce the data so you have some 00:09:54.480 --> 00:09:56.630 align:start position:0% to produce the data so you have some data<00:09:54.839> proof<00:09:55.500> here<00:09:55.620> says<00:09:55.980> data<00:09:56.399> whatever 00:09:56.630 --> 00:09:56.640 align:start position:0% data proof here says data whatever 00:09:56.640 --> 00:09:58.550 align:start position:0% data proof here says data whatever someone<00:09:57.360> comes<00:09:57.660> along<00:09:57.779> computes<00:09:58.260> a<00:09:58.380> function 00:09:58.550 --> 00:09:58.560 align:start position:0% someone comes along computes a function 00:09:58.560 --> 00:10:00.530 align:start position:0% someone comes along computes a function on<00:09:58.740> the<00:09:58.860> data<00:09:59.100> gives<00:09:59.700> you<00:09:59.820> the<00:09:59.940> output<00:10:00.180> gives 00:10:00.530 --> 00:10:00.540 align:start position:0% on the data gives you the output gives 00:10:00.540 --> 00:10:02.090 align:start position:0% on the data gives you the output gives the<00:10:00.600> proof<00:10:00.839> that<00:10:00.899> that's<00:10:01.080> correct<00:10:01.500> and<00:10:01.980> then 00:10:02.090 --> 00:10:02.100 align:start position:0% the proof that that's correct and then 00:10:02.100 --> 00:10:03.350 align:start position:0% the proof that that's correct and then later<00:10:02.279> somebody<00:10:02.640> else<00:10:02.880> can<00:10:03.120> come<00:10:03.240> along 00:10:03.350 --> 00:10:03.360 align:start position:0% later somebody else can come along 00:10:03.360 --> 00:10:04.670 align:start position:0% later somebody else can come along compute<00:10:03.839> another<00:10:03.899> function<00:10:04.260> on<00:10:04.440> the<00:10:04.560> result 00:10:04.670 --> 00:10:04.680 align:start position:0% compute another function on the result 00:10:04.680 --> 00:10:05.870 align:start position:0% compute another function on the result of<00:10:04.980> that<00:10:05.100> give<00:10:05.339> you<00:10:05.459> a<00:10:05.519> proof<00:10:05.700> that<00:10:05.760> that's 00:10:05.870 --> 00:10:05.880 align:start position:0% of that give you a proof that that's 00:10:05.880 --> 00:10:07.190 align:start position:0% of that give you a proof that that's correct<00:10:06.240> and<00:10:06.420> you<00:10:06.540> can<00:10:06.660> just<00:10:06.779> sort<00:10:06.959> of<00:10:07.080> imagine 00:10:07.190 --> 00:10:07.200 align:start position:0% correct and you can just sort of imagine 00:10:07.200 --> 00:10:08.750 align:start position:0% correct and you can just sort of imagine some<00:10:07.800> kind<00:10:07.980> of<00:10:08.040> state<00:10:08.160> machine<00:10:08.399> going 00:10:08.750 --> 00:10:08.760 align:start position:0% some kind of state machine going 00:10:08.760 --> 00:10:10.730 align:start position:0% some kind of state machine going forwards<00:10:09.180> looks<00:10:10.019> kind<00:10:10.140> of<00:10:10.260> like<00:10:10.440> a<00:10:10.620> smart 00:10:10.730 --> 00:10:10.740 align:start position:0% forwards looks kind of like a smart 00:10:10.740 --> 00:10:12.290 align:start position:0% forwards looks kind of like a smart contract<00:10:11.160> I<00:10:11.339> guess<00:10:11.459> but<00:10:11.640> it<00:10:11.760> involves<00:10:12.060> zero 00:10:12.290 --> 00:10:12.300 align:start position:0% contract I guess but it involves zero 00:10:12.300 --> 00:10:13.670 align:start position:0% contract I guess but it involves zero knowledge<00:10:12.480> proofs<00:10:12.839> and<00:10:13.260> of<00:10:13.380> course<00:10:13.500> because 00:10:13.670 --> 00:10:13.680 align:start position:0% knowledge proofs and of course because 00:10:13.680 --> 00:10:15.050 align:start position:0% knowledge proofs and of course because it<00:10:13.920> involves<00:10:14.220> your<00:10:14.339> knowledge<00:10:14.640> proofs<00:10:14.940> you 00:10:15.050 --> 00:10:15.060 align:start position:0% it involves your knowledge proofs you 00:10:15.060 --> 00:10:16.670 align:start position:0% it involves your knowledge proofs you can<00:10:15.180> also<00:10:15.360> hide<00:10:15.720> anything<00:10:16.019> you<00:10:16.320> want<00:10:16.440> in<00:10:16.560> the 00:10:16.670 --> 00:10:16.680 align:start position:0% can also hide anything you want in the 00:10:16.680 --> 00:10:18.949 align:start position:0% can also hide anything you want in the process<00:10:16.920> of<00:10:17.100> doing<00:10:17.220> this<00:10:17.940> uh<00:10:18.540> so<00:10:18.720> this<00:10:18.839> is 00:10:18.949 --> 00:10:18.959 align:start position:0% process of doing this uh so this is 00:10:18.959 --> 00:10:22.190 align:start position:0% process of doing this uh so this is great<00:10:19.140> it's<00:10:19.320> a<00:10:19.560> nice<00:10:19.620> piece<00:10:19.920> of<00:10:19.980> work<00:10:20.100> but 00:10:22.190 --> 00:10:22.200 align:start position:0% great it's a nice piece of work but 00:10:22.200 --> 00:10:23.509 align:start position:0% great it's a nice piece of work but you<00:10:22.620> know<00:10:22.680> first<00:10:22.860> of<00:10:22.980> all<00:10:23.100> how<00:10:23.220> do<00:10:23.339> you<00:10:23.399> agree 00:10:23.509 --> 00:10:23.519 align:start position:0% you know first of all how do you agree 00:10:23.519 --> 00:10:25.310 align:start position:0% you know first of all how do you agree on<00:10:23.640> what<00:10:23.820> this<00:10:23.940> data<00:10:24.180> is<00:10:24.300> did<00:10:24.600> everyone<00:10:24.779> saw<00:10:25.140> it 00:10:25.310 --> 00:10:25.320 align:start position:0% on what this data is did everyone saw it 00:10:25.320 --> 00:10:27.050 align:start position:0% on what this data is did everyone saw it second<00:10:25.800> of<00:10:25.980> all<00:10:26.100> what<00:10:26.339> is<00:10:26.459> this<00:10:26.519> good<00:10:26.700> for<00:10:26.820> this 00:10:27.050 --> 00:10:27.060 align:start position:0% second of all what is this good for this 00:10:27.060 --> 00:10:28.610 align:start position:0% second of all what is this good for this paper<00:10:27.240> does<00:10:27.480> not<00:10:27.660> answer<00:10:27.779> that<00:10:28.080> question<00:10:28.260> this 00:10:28.610 --> 00:10:28.620 align:start position:0% paper does not answer that question this 00:10:28.620 --> 00:10:30.290 align:start position:0% paper does not answer that question this proposes<00:10:29.040> this<00:10:29.279> academic<00:10:29.640> mechanism<00:10:30.060> so 00:10:30.290 --> 00:10:30.300 align:start position:0% proposes this academic mechanism so 00:10:30.300 --> 00:10:31.970 align:start position:0% proposes this academic mechanism so we're<00:10:30.480> back<00:10:30.600> to<00:10:30.720> the<00:10:30.899> question<00:10:31.019> of<00:10:31.380> what<00:10:31.860> does 00:10:31.970 --> 00:10:31.980 align:start position:0% we're back to the question of what does 00:10:31.980 --> 00:10:34.430 align:start position:0% we're back to the question of what does your<00:10:32.160> knowledge<00:10:32.459> proofs<00:10:32.820> good<00:10:32.940> for<00:10:33.120> and<00:10:33.899> so<00:10:34.140> in 00:10:34.430 --> 00:10:34.440 align:start position:0% your knowledge proofs good for and so in 00:10:34.440 --> 00:10:35.870 align:start position:0% your knowledge proofs good for and so in my<00:10:34.560> mind<00:10:34.680> the<00:10:34.980> thing<00:10:35.100> that<00:10:35.220> a<00:10:35.399> zero<00:10:35.700> knowledge 00:10:35.870 --> 00:10:35.880 align:start position:0% my mind the thing that a zero knowledge 00:10:35.880 --> 00:10:37.490 align:start position:0% my mind the thing that a zero knowledge proof<00:10:36.180> combined<00:10:36.540> with<00:10:36.660> the<00:10:36.839> blockchain<00:10:37.200> and 00:10:37.490 --> 00:10:37.500 align:start position:0% proof combined with the blockchain and 00:10:37.500 --> 00:10:39.410 align:start position:0% proof combined with the blockchain and that<00:10:37.740> combination<00:10:38.279> is<00:10:38.459> crucial<00:10:38.700> gives<00:10:39.120> you<00:10:39.240> is 00:10:39.410 --> 00:10:39.420 align:start position:0% that combination is crucial gives you is 00:10:39.420 --> 00:10:41.750 align:start position:0% that combination is crucial gives you is credibility<00:10:39.839> right<00:10:40.560> that<00:10:41.160> piece<00:10:41.339> of<00:10:41.399> data<00:10:41.640> if 00:10:41.750 --> 00:10:41.760 align:start position:0% credibility right that piece of data if 00:10:41.760 --> 00:10:44.389 align:start position:0% credibility right that piece of data if it's<00:10:41.880> on<00:10:42.000> a<00:10:42.180> blockchain<00:10:42.540> can<00:10:43.200> tell<00:10:43.440> you<00:10:43.620> uh 00:10:44.389 --> 00:10:44.399 align:start position:0% it's on a blockchain can tell you uh 00:10:44.399 --> 00:10:46.250 align:start position:0% it's on a blockchain can tell you uh that<00:10:44.640> everyone<00:10:44.820> agreed<00:10:45.240> on<00:10:45.360> this<00:10:45.540> right<00:10:46.019> this 00:10:46.250 --> 00:10:46.260 align:start position:0% that everyone agreed on this right this 00:10:46.260 --> 00:10:47.569 align:start position:0% that everyone agreed on this right this is<00:10:46.380> what's<00:10:46.500> out<00:10:46.740> there<00:10:46.860> and<00:10:47.040> then<00:10:47.160> I<00:10:47.339> can<00:10:47.459> give 00:10:47.569 --> 00:10:47.579 align:start position:0% is what's out there and then I can give 00:10:47.579 --> 00:10:49.970 align:start position:0% is what's out there and then I can give you<00:10:47.700> a<00:10:47.820> proof<00:10:48.060> that<00:10:48.120> it<00:10:48.300> was<00:10:48.420> correct<00:10:48.779> that<00:10:49.620> you 00:10:49.970 --> 00:10:49.980 align:start position:0% you a proof that it was correct that you 00:10:49.980 --> 00:10:51.410 align:start position:0% you a proof that it was correct that you know<00:10:50.040> I<00:10:50.399> didn't<00:10:50.519> see<00:10:50.760> anything<00:10:50.820> else<00:10:51.120> that<00:10:51.300> I 00:10:51.410 --> 00:10:51.420 align:start position:0% know I didn't see anything else that I 00:10:51.420 --> 00:10:52.610 align:start position:0% know I didn't see anything else that I wasn't<00:10:51.540> supposed<00:10:51.779> to<00:10:51.899> when<00:10:52.079> I<00:10:52.200> was<00:10:52.260> Computing 00:10:52.610 --> 00:10:52.620 align:start position:0% wasn't supposed to when I was Computing 00:10:52.620 --> 00:10:55.970 align:start position:0% wasn't supposed to when I was Computing on<00:10:52.800> it<00:10:52.920> and<00:10:53.640> that<00:10:53.940> you<00:10:54.839> know<00:10:54.959> the<00:10:55.380> operation<00:10:55.740> I 00:10:55.970 --> 00:10:55.980 align:start position:0% on it and that you know the operation I 00:10:55.980 --> 00:10:57.949 align:start position:0% on it and that you know the operation I did<00:10:56.100> was<00:10:56.339> done<00:10:56.519> correctly<00:10:57.120> and<00:10:57.660> then<00:10:57.720> we<00:10:57.839> all 00:10:57.949 --> 00:10:57.959 align:start position:0% did was done correctly and then we all 00:10:57.959 --> 00:10:59.329 align:start position:0% did was done correctly and then we all get<00:10:58.079> a<00:10:58.200> share<00:10:58.380> consensus<00:10:58.920> on<00:10:59.100> this<00:10:59.220> because 00:10:59.329 --> 00:10:59.339 align:start position:0% get a share consensus on this because 00:10:59.339 --> 00:11:01.069 align:start position:0% get a share consensus on this because it's<00:10:59.459> on<00:10:59.640> a<00:10:59.760> blockchain<00:11:00.060> I<00:11:00.360> can't<00:11:00.480> equivocate 00:11:01.069 --> 00:11:01.079 align:start position:0% it's on a blockchain I can't equivocate 00:11:01.079 --> 00:11:02.810 align:start position:0% it's on a blockchain I can't equivocate on<00:11:01.260> what<00:11:01.380> I<00:11:01.500> did<00:11:01.620> I<00:11:02.040> can't<00:11:02.160> double<00:11:02.339> spin 00:11:02.810 --> 00:11:02.820 align:start position:0% on what I did I can't double spin 00:11:02.820 --> 00:11:03.949 align:start position:0% on what I did I can't double spin something<00:11:03.060> if<00:11:03.300> there's<00:11:03.480> something<00:11:03.660> in<00:11:03.779> this 00:11:03.949 --> 00:11:03.959 align:start position:0% something if there's something in this 00:11:03.959 --> 00:11:06.350 align:start position:0% something if there's something in this data<00:11:04.800> you<00:11:05.220> know<00:11:05.339> this<00:11:05.519> is<00:11:05.640> privacy<00:11:05.880> preserving 00:11:06.350 --> 00:11:06.360 align:start position:0% data you know this is privacy preserving 00:11:06.360 --> 00:11:07.550 align:start position:0% data you know this is privacy preserving smart<00:11:06.540> contracts<00:11:06.959> for<00:11:07.079> any<00:11:07.260> of<00:11:07.320> you<00:11:07.380> have 00:11:07.550 --> 00:11:07.560 align:start position:0% smart contracts for any of you have 00:11:07.560 --> 00:11:09.050 align:start position:0% smart contracts for any of you have looked<00:11:07.800> at<00:11:07.860> this<00:11:08.040> stuff 00:11:09.050 --> 00:11:09.060 align:start position:0% looked at this stuff 00:11:09.060 --> 00:11:10.790 align:start position:0% looked at this stuff but<00:11:09.480> at<00:11:09.600> a<00:11:09.779> level<00:11:09.899> of<00:11:10.140> what's<00:11:10.260> the<00:11:10.500> property 00:11:10.790 --> 00:11:10.800 align:start position:0% but at a level of what's the property 00:11:10.800 --> 00:11:12.949 align:start position:0% but at a level of what's the property that<00:11:10.980> a<00:11:11.160> normal<00:11:11.279> person<00:11:11.519> might<00:11:11.880> care<00:11:12.060> about 00:11:12.949 --> 00:11:12.959 align:start position:0% that a normal person might care about 00:11:12.959 --> 00:11:15.110 align:start position:0% that a normal person might care about right<00:11:13.380> so<00:11:13.620> what<00:11:13.800> do<00:11:13.920> we<00:11:14.040> do<00:11:14.160> with<00:11:14.339> this 00:11:15.110 --> 00:11:15.120 align:start position:0% right so what do we do with this 00:11:15.120 --> 00:11:17.090 align:start position:0% right so what do we do with this well<00:11:15.720> in<00:11:16.140> general<00:11:16.260> what<00:11:16.560> is<00:11:16.680> your<00:11:16.800> knowledge 00:11:17.090 --> 00:11:17.100 align:start position:0% well in general what is your knowledge 00:11:17.100 --> 00:11:18.829 align:start position:0% well in general what is your knowledge proof<00:11:17.339> it's<00:11:17.399> good<00:11:17.579> for<00:11:17.700> and<00:11:18.060> in<00:11:18.240> this<00:11:18.420> talk<00:11:18.600> I'm 00:11:18.829 --> 00:11:18.839 align:start position:0% proof it's good for and in this talk I'm 00:11:18.839 --> 00:11:20.870 align:start position:0% proof it's good for and in this talk I'm going<00:11:18.959> to<00:11:19.079> give<00:11:19.140> you<00:11:19.320> some<00:11:19.740> low-level<00:11:20.579> things 00:11:20.870 --> 00:11:20.880 align:start position:0% going to give you some low-level things 00:11:20.880 --> 00:11:22.970 align:start position:0% going to give you some low-level things of<00:11:21.060> like<00:11:21.180> immediate<00:11:21.660> problems<00:11:22.140> some<00:11:22.740> very 00:11:22.970 --> 00:11:22.980 align:start position:0% of like immediate problems some very 00:11:22.980 --> 00:11:25.009 align:start position:0% of like immediate problems some very high<00:11:23.100> level<00:11:23.279> things<00:11:23.640> that<00:11:23.820> are<00:11:24.000> you<00:11:24.360> know<00:11:24.420> what 00:11:25.009 --> 00:11:25.019 align:start position:0% high level things that are you know what 00:11:25.019 --> 00:11:26.449 align:start position:0% high level things that are you know what was<00:11:25.200> on<00:11:25.380> my<00:11:25.500> mind<00:11:25.620> at<00:11:25.740> the<00:11:25.920> time<00:11:25.980> and<00:11:26.160> then<00:11:26.279> back 00:11:26.449 --> 00:11:26.459 align:start position:0% was on my mind at the time and then back 00:11:26.459 --> 00:11:28.490 align:start position:0% was on my mind at the time and then back to<00:11:26.640> some<00:11:26.760> low-level<00:11:27.180> things<00:11:27.360> of<00:11:27.540> identity 00:11:28.490 --> 00:11:28.500 align:start position:0% to some low-level things of identity 00:11:28.500 --> 00:11:30.410 align:start position:0% to some low-level things of identity so<00:11:28.920> the<00:11:29.160> first<00:11:29.279> thing<00:11:29.519> that<00:11:29.760> you<00:11:30.000> really<00:11:30.240> do 00:11:30.410 --> 00:11:30.420 align:start position:0% so the first thing that you really do 00:11:30.420 --> 00:11:32.509 align:start position:0% so the first thing that you really do need<00:11:30.600> zero<00:11:30.959> knowledge<00:11:31.200> proofs<00:11:31.620> for<00:11:31.800> is 00:11:32.509 --> 00:11:32.519 align:start position:0% need zero knowledge proofs for is 00:11:32.519 --> 00:11:35.269 align:start position:0% need zero knowledge proofs for is credible<00:11:33.120> safety<00:11:33.600> for<00:11:33.899> or<00:11:34.200> from<00:11:34.620> depending<00:11:35.160> on 00:11:35.269 --> 00:11:35.279 align:start position:0% credible safety for or from depending on 00:11:35.279 --> 00:11:36.889 align:start position:0% credible safety for or from depending on how<00:11:35.399> cynical<00:11:35.700> you<00:11:35.940> all<00:11:36.060> roll<00:11:36.240> up<00:11:36.420> operators 00:11:36.889 --> 00:11:36.899 align:start position:0% how cynical you all roll up operators 00:11:36.899 --> 00:11:38.930 align:start position:0% how cynical you all roll up operators right<00:11:37.500> the<00:11:37.860> Bitcoin<00:11:38.220> people<00:11:38.399> would<00:11:38.640> call<00:11:38.820> this 00:11:38.930 --> 00:11:38.940 align:start position:0% right the Bitcoin people would call this 00:11:38.940 --> 00:11:41.509 align:start position:0% right the Bitcoin people would call this censorship<00:11:39.420> resistance<00:11:39.959> uh 00:11:41.509 --> 00:11:41.519 align:start position:0% censorship resistance uh 00:11:41.519 --> 00:11:44.810 align:start position:0% censorship resistance uh because<00:11:42.000> if<00:11:42.360> you<00:11:42.480> have<00:11:42.839> a 00:11:44.810 --> 00:11:44.820 align:start position:0% because if you have a 00:11:44.820 --> 00:11:47.150 align:start position:0% because if you have a have<00:11:45.420> a<00:11:45.720> roll-up<00:11:46.140> right<00:11:46.500> the<00:11:46.680> roll-up<00:11:46.980> is 00:11:47.150 --> 00:11:47.160 align:start position:0% have a roll-up right the roll-up is 00:11:47.160 --> 00:11:48.470 align:start position:0% have a roll-up right the roll-up is taking<00:11:47.279> these<00:11:47.579> transactions<00:11:48.060> the<00:11:48.300> service 00:11:48.470 --> 00:11:48.480 align:start position:0% taking these transactions the service 00:11:48.480 --> 00:11:50.269 align:start position:0% taking these transactions the service sitting<00:11:48.899> here<00:11:49.019> it<00:11:49.560> sees<00:11:49.860> everything<00:11:50.040> that's 00:11:50.269 --> 00:11:50.279 align:start position:0% sitting here it sees everything that's 00:11:50.279 --> 00:11:52.370 align:start position:0% sitting here it sees everything that's in<00:11:50.399> those<00:11:50.579> transactions<00:11:51.600> right<00:11:51.959> these<00:11:52.260> are 00:11:52.370 --> 00:11:52.380 align:start position:0% in those transactions right these are 00:11:52.380 --> 00:11:53.990 align:start position:0% in those transactions right these are normal<00:11:52.620> ethereum<00:11:53.160> or<00:11:53.399> Bitcoin<00:11:53.700> or<00:11:53.820> whatever 00:11:53.990 --> 00:11:54.000 align:start position:0% normal ethereum or Bitcoin or whatever 00:11:54.000 --> 00:11:55.790 align:start position:0% normal ethereum or Bitcoin or whatever it<00:11:54.240> is<00:11:54.360> transactions<00:11:54.899> they<00:11:55.320> are<00:11:55.500> completely 00:11:55.790 --> 00:11:55.800 align:start position:0% it is transactions they are completely 00:11:55.800 --> 00:11:57.949 align:start position:0% it is transactions they are completely uh<00:11:56.279> transparent<00:11:56.760> to<00:11:56.880> the<00:11:57.060> server<00:11:57.300> server<00:11:57.779> can 00:11:57.949 --> 00:11:57.959 align:start position:0% uh transparent to the server server can 00:11:57.959 --> 00:11:59.509 align:start position:0% uh transparent to the server server can see<00:11:58.079> what's<00:11:58.200> going<00:11:58.440> on 00:11:59.509 --> 00:11:59.519 align:start position:0% see what's going on 00:11:59.519 --> 00:12:01.009 align:start position:0% see what's going on okay<00:12:00.060> fine<00:12:00.300> why<00:12:00.660> does<00:12:00.779> that<00:12:00.899> matter 00:12:01.009 --> 00:12:01.019 align:start position:0% okay fine why does that matter 00:12:01.019 --> 00:12:02.990 align:start position:0% okay fine why does that matter blockchains<00:12:01.620> are<00:12:01.680> that<00:12:01.800> way<00:12:01.920> anyway<00:12:02.100> the 00:12:02.990 --> 00:12:03.000 align:start position:0% blockchains are that way anyway the 00:12:03.000 --> 00:12:04.430 align:start position:0% blockchains are that way anyway the problem<00:12:03.180> is<00:12:03.360> the<00:12:03.540> server<00:12:03.839> is<00:12:03.959> getting<00:12:04.140> these 00:12:04.430 --> 00:12:04.440 align:start position:0% problem is the server is getting these 00:12:04.440 --> 00:12:05.930 align:start position:0% problem is the server is getting these from<00:12:04.620> a<00:12:04.740> bunch<00:12:04.860> of<00:12:04.980> people<00:12:05.100> and<00:12:05.339> it<00:12:05.519> gets<00:12:05.820> to 00:12:05.930 --> 00:12:05.940 align:start position:0% from a bunch of people and it gets to 00:12:05.940 --> 00:12:07.970 align:start position:0% from a bunch of people and it gets to choose<00:12:06.300> which<00:12:06.660> ones<00:12:06.959> it<00:12:07.140> takes<00:12:07.380> and<00:12:07.800> which 00:12:07.970 --> 00:12:07.980 align:start position:0% choose which ones it takes and which 00:12:07.980 --> 00:12:10.069 align:start position:0% choose which ones it takes and which ones<00:12:08.339> it<00:12:08.579> doesn't 00:12:10.069 --> 00:12:10.079 align:start position:0% ones it doesn't 00:12:10.079 --> 00:12:11.690 align:start position:0% ones it doesn't and<00:12:10.560> the<00:12:10.680> problem<00:12:10.860> is<00:12:11.100> that<00:12:11.279> that's<00:12:11.459> going<00:12:11.640> to 00:12:11.690 --> 00:12:11.700 align:start position:0% and the problem is that that's going to 00:12:11.700 --> 00:12:13.190 align:start position:0% and the problem is that that's going to be<00:12:11.820> obvious<00:12:12.120> to<00:12:12.300> everybody<00:12:12.480> and<00:12:12.899> so<00:12:13.019> the 00:12:13.190 --> 00:12:13.200 align:start position:0% be obvious to everybody and so the 00:12:13.200 --> 00:12:14.930 align:start position:0% be obvious to everybody and so the server<00:12:13.500> is<00:12:13.620> going<00:12:13.740> to<00:12:13.860> be<00:12:13.920> held<00:12:14.399> responsible 00:12:14.930 --> 00:12:14.940 align:start position:0% server is going to be held responsible 00:12:14.940 --> 00:12:17.150 align:start position:0% server is going to be held responsible at<00:12:15.420> some<00:12:15.600> point<00:12:15.720> by<00:12:16.019> somebody<00:12:16.320> for<00:12:16.920> something 00:12:17.150 --> 00:12:17.160 align:start position:0% at some point by somebody for something 00:12:17.160 --> 00:12:19.430 align:start position:0% at some point by somebody for something it<00:12:17.399> failed<00:12:17.700> to<00:12:17.880> exclude 00:12:19.430 --> 00:12:19.440 align:start position:0% it failed to exclude 00:12:19.440 --> 00:12:19.970 align:start position:0% it failed to exclude um 00:12:19.970 --> 00:12:19.980 align:start position:0% um 00:12:19.980 --> 00:12:22.670 align:start position:0% um in<00:12:20.519> other<00:12:20.579> words<00:12:20.760> zkvms<00:12:21.660> and<00:12:21.720> ZK<00:12:22.019> Roll-Ups<00:12:22.500> at 00:12:22.670 --> 00:12:22.680 align:start position:0% in other words zkvms and ZK Roll-Ups at 00:12:22.680 --> 00:12:24.110 align:start position:0% in other words zkvms and ZK Roll-Ups at least<00:12:22.800> if<00:12:22.980> you<00:12:23.100> naively<00:12:23.459> do<00:12:23.579> them<00:12:23.700> in<00:12:23.820> a<00:12:23.940> single 00:12:24.110 --> 00:12:24.120 align:start position:0% least if you naively do them in a single 00:12:24.120 --> 00:12:26.569 align:start position:0% least if you naively do them in a single server<00:12:24.360> model<00:12:24.540> aren't<00:12:25.200> censorship<00:12:25.680> resistant 00:12:26.569 --> 00:12:26.579 align:start position:0% server model aren't censorship resistant 00:12:26.579 --> 00:12:28.430 align:start position:0% server model aren't censorship resistant the<00:12:26.820> consequence<00:12:27.180> of<00:12:27.360> this<00:12:27.540> is<00:12:27.720> you<00:12:28.260> really 00:12:28.430 --> 00:12:28.440 align:start position:0% the consequence of this is you really 00:12:28.440 --> 00:12:31.009 align:start position:0% the consequence of this is you really better<00:12:28.620> not<00:12:28.860> mint<00:12:29.220> any<00:12:29.459> enfps<00:12:30.000> if<00:12:30.360> some<00:12:30.540> meme<00:12:30.720> a 00:12:31.009 --> 00:12:31.019 align:start position:0% better not mint any enfps if some meme a 00:12:31.019 --> 00:12:32.870 align:start position:0% better not mint any enfps if some meme a government<00:12:31.140> doesn't<00:12:31.440> like<00:12:32.220> you<00:12:32.760> probably 00:12:32.870 --> 00:12:32.880 align:start position:0% government doesn't like you probably 00:12:32.880 --> 00:12:34.730 align:start position:0% government doesn't like you probably shouldn't<00:12:33.300> take<00:12:33.540> payments<00:12:34.140> to<00:12:34.320> activists 00:12:34.730 --> 00:12:34.740 align:start position:0% shouldn't take payments to activists 00:12:34.740 --> 00:12:36.470 align:start position:0% shouldn't take payments to activists that<00:12:34.980> the<00:12:35.100> government<00:12:35.279> doesn't<00:12:35.579> like<00:12:35.880> if 00:12:36.470 --> 00:12:36.480 align:start position:0% that the government doesn't like if 00:12:36.480 --> 00:12:38.210 align:start position:0% that the government doesn't like if you're<00:12:36.660> all<00:12:36.779> a<00:12:36.959> roll-up<00:12:37.260> operator<00:12:37.620> sitting<00:12:38.100> in 00:12:38.210 --> 00:12:38.220 align:start position:0% you're all a roll-up operator sitting in 00:12:38.220 --> 00:12:40.730 align:start position:0% you're all a roll-up operator sitting in Texas<00:12:38.399> I<00:12:39.360> probably<00:12:39.540> wouldn't<00:12:39.899> take<00:12:40.380> donations 00:12:40.730 --> 00:12:40.740 align:start position:0% Texas I probably wouldn't take donations 00:12:40.740 --> 00:12:43.009 align:start position:0% Texas I probably wouldn't take donations to<00:12:40.980> an<00:12:41.160> abortion<00:12:41.519> fund<00:12:41.820> right<00:12:42.000> now<00:12:42.180> might<00:12:42.839> get 00:12:43.009 --> 00:12:43.019 align:start position:0% to an abortion fund right now might get 00:12:43.019 --> 00:12:44.569 align:start position:0% to an abortion fund right now might get you<00:12:43.139> in<00:12:43.260> a<00:12:43.380> bit<00:12:43.440> of<00:12:43.560> trouble 00:12:44.569 --> 00:12:44.579 align:start position:0% you in a bit of trouble 00:12:44.579 --> 00:12:47.449 align:start position:0% you in a bit of trouble um<00:12:44.639> because<00:12:44.880> if<00:12:45.120> you<00:12:45.300> do<00:12:45.540> your<00:12:46.139> nice<00:12:46.380> ZK<00:12:46.920> uh 00:12:47.449 --> 00:12:47.459 align:start position:0% um because if you do your nice ZK uh 00:12:47.459 --> 00:12:49.129 align:start position:0% um because if you do your nice ZK uh block<00:12:47.700> compact<00:12:48.240> trying<00:12:48.660> to<00:12:48.899> make<00:12:49.019> things 00:12:49.129 --> 00:12:49.139 align:start position:0% block compact trying to make things 00:12:49.139 --> 00:12:50.810 align:start position:0% block compact trying to make things efficient<00:12:49.560> isn't<00:12:50.220> going<00:12:50.339> to<00:12:50.399> be<00:12:50.519> a<00:12:50.700> block 00:12:50.810 --> 00:12:50.820 align:start position:0% efficient isn't going to be a block 00:12:50.820 --> 00:12:52.850 align:start position:0% efficient isn't going to be a block compactor<00:12:51.480> it's<00:12:52.019> going<00:12:52.200> to<00:12:52.320> be<00:12:52.440> a<00:12:52.740> trash 00:12:52.850 --> 00:12:52.860 align:start position:0% compactor it's going to be a trash 00:12:52.860 --> 00:12:54.650 align:start position:0% compactor it's going to be a trash compactor<00:12:53.519> on<00:12:53.820> fire 00:12:54.650 --> 00:12:54.660 align:start position:0% compactor on fire 00:12:54.660 --> 00:12:56.629 align:start position:0% compactor on fire you're<00:12:55.200> going<00:12:55.380> to<00:12:55.500> just<00:12:55.620> have<00:12:55.800> major<00:12:56.040> problems 00:12:56.629 --> 00:12:56.639 align:start position:0% you're going to just have major problems 00:12:56.639 --> 00:12:59.150 align:start position:0% you're going to just have major problems with<00:12:57.420> transactions<00:12:58.320> you<00:12:58.380> process<00:12:58.680> so<00:12:58.920> this<00:12:59.100> is 00:12:59.150 --> 00:12:59.160 align:start position:0% with transactions you process so this is 00:12:59.160 --> 00:13:01.370 align:start position:0% with transactions you process so this is not<00:12:59.339> safe<00:12:59.579> this<00:12:59.880> is<00:13:00.000> not<00:13:00.120> good<00:13:00.360> and<00:13:00.959> this<00:13:01.139> is<00:13:01.200> a 00:13:01.370 --> 00:13:01.380 align:start position:0% not safe this is not good and this is a 00:13:01.380 --> 00:13:02.449 align:start position:0% not safe this is not good and this is a major<00:13:01.500> problem<00:13:01.740> for<00:13:01.920> all<00:13:02.100> people<00:13:02.220> trying<00:13:02.399> to 00:13:02.449 --> 00:13:02.459 align:start position:0% major problem for all people trying to 00:13:02.459 --> 00:13:04.730 align:start position:0% major problem for all people trying to get<00:13:02.579> blockchains<00:13:03.060> to<00:13:03.180> scale<00:13:03.959> so<00:13:04.380> what<00:13:04.500> do<00:13:04.620> you 00:13:04.730 --> 00:13:04.740 align:start position:0% get blockchains to scale so what do you 00:13:04.740 --> 00:13:07.069 align:start position:0% get blockchains to scale so what do you do<00:13:04.860> about<00:13:05.040> this<00:13:05.339> well<00:13:05.940> you<00:13:06.300> replace<00:13:06.540> the 00:13:07.069 --> 00:13:07.079 align:start position:0% do about this well you replace the 00:13:07.079 --> 00:13:08.990 align:start position:0% do about this well you replace the individual<00:13:07.440> user<00:13:07.860> transactions<00:13:08.339> with<00:13:08.639> zero 00:13:08.990 --> 00:13:09.000 align:start position:0% individual user transactions with zero 00:13:09.000 --> 00:13:10.430 align:start position:0% individual user transactions with zero knowledge<00:13:09.240> proofs<00:13:09.600> so<00:13:10.079> that<00:13:10.260> those 00:13:10.430 --> 00:13:10.440 align:start position:0% knowledge proofs so that those 00:13:10.440 --> 00:13:13.069 align:start position:0% knowledge proofs so that those transactions<00:13:10.980> are<00:13:11.160> now<00:13:11.339> uh<00:13:11.700> opaque 00:13:13.069 --> 00:13:13.079 align:start position:0% transactions are now uh opaque 00:13:13.079 --> 00:13:14.690 align:start position:0% transactions are now uh opaque and<00:13:13.500> as<00:13:13.620> a<00:13:13.740> result<00:13:13.860> the<00:13:14.100> roll-up<00:13:14.399> operator 00:13:14.690 --> 00:13:14.700 align:start position:0% and as a result the roll-up operator 00:13:14.700 --> 00:13:16.970 align:start position:0% and as a result the roll-up operator can't<00:13:15.060> see<00:13:15.300> what's<00:13:15.480> going<00:13:15.720> on<00:13:15.959> and<00:13:16.620> so<00:13:16.800> they 00:13:16.970 --> 00:13:16.980 align:start position:0% can't see what's going on and so they 00:13:16.980 --> 00:13:18.530 align:start position:0% can't see what's going on and so they have<00:13:17.160> they're<00:13:17.399> a<00:13:17.579> dumb<00:13:17.700> pipe<00:13:18.120> and<00:13:18.240> they<00:13:18.420> have 00:13:18.530 --> 00:13:18.540 align:start position:0% have they're a dumb pipe and they have 00:13:18.540 --> 00:13:20.030 align:start position:0% have they're a dumb pipe and they have some<00:13:18.779> limited<00:13:19.200> ability<00:13:19.440> to<00:13:19.560> manipulate 00:13:20.030 --> 00:13:20.040 align:start position:0% some limited ability to manipulate 00:13:20.040 --> 00:13:21.410 align:start position:0% some limited ability to manipulate transaction<00:13:20.399> ordering<00:13:20.880> but<00:13:21.000> again<00:13:21.120> they 00:13:21.410 --> 00:13:21.420 align:start position:0% transaction ordering but again they 00:13:21.420 --> 00:13:23.030 align:start position:0% transaction ordering but again they don't<00:13:21.540> really<00:13:21.660> know<00:13:21.839> what's<00:13:22.019> going<00:13:22.260> on<00:13:22.440> they 00:13:23.030 --> 00:13:23.040 align:start position:0% don't really know what's going on they 00:13:23.040 --> 00:13:25.490 align:start position:0% don't really know what's going on they have<00:13:23.220> a<00:13:23.339> degree<00:13:23.519> of<00:13:23.820> of<00:13:24.120> deniability 00:13:25.490 --> 00:13:25.500 align:start position:0% have a degree of of deniability 00:13:25.500 --> 00:13:27.590 align:start position:0% have a degree of of deniability uh<00:13:26.100> and<00:13:26.279> so<00:13:26.399> this<00:13:26.579> gives<00:13:26.820> you<00:13:26.940> a<00:13:27.300> minimal 00:13:27.590 --> 00:13:27.600 align:start position:0% uh and so this gives you a minimal 00:13:27.600 --> 00:13:28.910 align:start position:0% uh and so this gives you a minimal amount<00:13:27.839> of<00:13:27.959> safety<00:13:28.200> it<00:13:28.380> doesn't<00:13:28.560> solve 00:13:28.910 --> 00:13:28.920 align:start position:0% amount of safety it doesn't solve 00:13:28.920 --> 00:13:30.710 align:start position:0% amount of safety it doesn't solve everything<00:13:29.639> but<00:13:30.060> this<00:13:30.180> is<00:13:30.300> the<00:13:30.420> thing<00:13:30.540> that 00:13:30.710 --> 00:13:30.720 align:start position:0% everything but this is the thing that 00:13:30.720 --> 00:13:31.910 align:start position:0% everything but this is the thing that you<00:13:30.779> need<00:13:30.899> to<00:13:31.019> be<00:13:31.139> building<00:13:31.260> into<00:13:31.440> your<00:13:31.680> ZK 00:13:31.910 --> 00:13:31.920 align:start position:0% you need to be building into your ZK 00:13:31.920 --> 00:13:34.190 align:start position:0% you need to be building into your ZK Roll-Ups<00:13:32.940> um<00:13:32.940> and<00:13:33.120> this<00:13:33.300> is<00:13:33.420> things<00:13:33.779> that 00:13:34.190 --> 00:13:34.200 align:start position:0% Roll-Ups um and this is things that 00:13:34.200 --> 00:13:35.509 align:start position:0% Roll-Ups um and this is things that various<00:13:34.500> people<00:13:34.680> are<00:13:34.920> building<00:13:35.100> I<00:13:35.399> believe 00:13:35.509 --> 00:13:35.519 align:start position:0% various people are building I believe 00:13:35.519 --> 00:13:36.710 align:start position:0% various people are building I believe the<00:13:35.760> original<00:13:35.880> people<00:13:36.180> who<00:13:36.360> came<00:13:36.540> up<00:13:36.660> with 00:13:36.710 --> 00:13:36.720 align:start position:0% the original people who came up with 00:13:36.720 --> 00:13:38.509 align:start position:0% the original people who came up with this<00:13:36.899> idea<00:13:37.200> uh<00:13:37.740> I<00:13:37.920> don't<00:13:38.040> follow<00:13:38.160> these<00:13:38.399> things 00:13:38.509 --> 00:13:38.519 align:start position:0% this idea uh I don't follow these things 00:13:38.519 --> 00:13:40.610 align:start position:0% this idea uh I don't follow these things too<00:13:38.700> closely<00:13:38.880> Aztec<00:13:39.600> currently<00:13:40.139> has<00:13:40.260> this<00:13:40.440> out 00:13:40.610 --> 00:13:40.620 align:start position:0% too closely Aztec currently has this out 00:13:40.620 --> 00:13:41.389 align:start position:0% too closely Aztec currently has this out there 00:13:41.389 --> 00:13:41.399 align:start position:0% there 00:13:41.399 --> 00:13:42.889 align:start position:0% there um Elio<00:13:41.820> company<00:13:42.120> I'm<00:13:42.420> involved<00:13:42.720> with<00:13:42.779> is 00:13:42.889 --> 00:13:42.899 align:start position:0% um Elio company I'm involved with is 00:13:42.899 --> 00:13:44.509 align:start position:0% um Elio company I'm involved with is also<00:13:43.139> building<00:13:43.320> this<00:13:43.560> I'm<00:13:44.040> sure<00:13:44.220> there<00:13:44.399> are 00:13:44.509 --> 00:13:44.519 align:start position:0% also building this I'm sure there are 00:13:44.519 --> 00:13:46.129 align:start position:0% also building this I'm sure there are others<00:13:44.760> but<00:13:44.880> nobody's<00:13:45.300> really<00:13:45.480> broadcasting 00:13:46.129 --> 00:13:46.139 align:start position:0% others but nobody's really broadcasting 00:13:46.139 --> 00:13:47.870 align:start position:0% others but nobody's really broadcasting these<00:13:46.500> features<00:13:46.800> as<00:13:47.040> a<00:13:47.220> thing<00:13:47.339> that<00:13:47.519> goes<00:13:47.760> on 00:13:47.870 --> 00:13:47.880 align:start position:0% these features as a thing that goes on 00:13:47.880 --> 00:13:49.550 align:start position:0% these features as a thing that goes on very<00:13:48.060> well<00:13:48.300> and<00:13:48.959> part<00:13:49.139> of<00:13:49.260> that's<00:13:49.380> because 00:13:49.550 --> 00:13:49.560 align:start position:0% very well and part of that's because 00:13:49.560 --> 00:13:51.710 align:start position:0% very well and part of that's because that's<00:13:49.800> a<00:13:49.980> really<00:13:50.100> bad<00:13:50.339> name<00:13:50.639> right<00:13:51.180> this<00:13:51.420> gets 00:13:51.710 --> 00:13:51.720 align:start position:0% that's a really bad name right this gets 00:13:51.720 --> 00:13:54.110 align:start position:0% that's a really bad name right this gets called<00:13:51.839> a<00:13:52.019> ZK<00:13:52.320> ZK<00:13:52.740> roll-up<00:13:53.220> which<00:13:53.760> is<00:13:53.880> kind<00:13:54.060> of 00:13:54.110 --> 00:13:54.120 align:start position:0% called a ZK ZK roll-up which is kind of 00:13:54.120 --> 00:13:55.730 align:start position:0% called a ZK ZK roll-up which is kind of a<00:13:54.300> mouthful<00:13:54.600> and<00:13:54.779> every<00:13:54.959> time<00:13:55.139> I<00:13:55.260> hear<00:13:55.440> it<00:13:55.560> all 00:13:55.730 --> 00:13:55.740 align:start position:0% a mouthful and every time I hear it all 00:13:55.740 --> 00:13:57.470 align:start position:0% a mouthful and every time I hear it all I<00:13:55.920> can<00:13:56.040> think<00:13:56.100> of<00:13:56.279> is<00:13:56.459> this<00:13:56.700> bad<00:13:56.880> meme<00:13:57.060> from 00:13:57.470 --> 00:13:57.480 align:start position:0% I can think of is this bad meme from 00:13:57.480 --> 00:14:00.290 align:start position:0% I can think of is this bad meme from like<00:13:57.800> not<00:13:58.800> quite<00:13:59.040> the<00:13:59.220> 90s<00:13:59.639> but<00:13:59.880> it's<00:14:00.000> pretty 00:14:00.290 --> 00:14:00.300 align:start position:0% like not quite the 90s but it's pretty 00:14:00.300 --> 00:14:01.730 align:start position:0% like not quite the 90s but it's pretty old 00:14:01.730 --> 00:14:01.740 align:start position:0% old 00:14:01.740 --> 00:14:02.410 align:start position:0% old um 00:14:02.410 --> 00:14:02.420 align:start position:0% um 00:14:02.420 --> 00:14:05.150 align:start position:0% um so<00:14:03.420> you<00:14:04.139> should<00:14:04.260> be<00:14:04.380> doing<00:14:04.500> this<00:14:04.740> and<00:14:04.980> somebody 00:14:05.150 --> 00:14:05.160 align:start position:0% so you should be doing this and somebody 00:14:05.160 --> 00:14:06.530 align:start position:0% so you should be doing this and somebody should<00:14:05.459> please<00:14:05.639> please<00:14:05.880> come<00:14:06.180> up<00:14:06.300> with<00:14:06.420> a 00:14:06.530 --> 00:14:06.540 align:start position:0% should please please come up with a 00:14:06.540 --> 00:14:07.730 align:start position:0% should please please come up with a better<00:14:06.660> name<00:14:06.839> for<00:14:06.959> this<00:14:07.079> that's<00:14:07.200> catchy<00:14:07.560> so 00:14:07.730 --> 00:14:07.740 align:start position:0% better name for this that's catchy so 00:14:07.740 --> 00:14:09.230 align:start position:0% better name for this that's catchy so that<00:14:07.860> people<00:14:07.980> can<00:14:08.160> Market<00:14:08.339> it<00:14:08.940> um<00:14:09.000> because<00:14:09.060> I'm 00:14:09.230 --> 00:14:09.240 align:start position:0% that people can Market it um because I'm 00:14:09.240 --> 00:14:10.670 align:start position:0% that people can Market it um because I'm sure<00:14:09.420> I<00:14:09.600> left<00:14:09.720> off<00:14:09.959> some<00:14:10.139> people<00:14:10.320> who<00:14:10.560> are 00:14:10.670 --> 00:14:10.680 align:start position:0% sure I left off some people who are 00:14:10.680 --> 00:14:11.930 align:start position:0% sure I left off some people who are building<00:14:10.800> this 00:14:11.930 --> 00:14:11.940 align:start position:0% building this 00:14:11.940 --> 00:14:12.530 align:start position:0% building this um 00:14:12.530 --> 00:14:12.540 align:start position:0% um 00:14:12.540 --> 00:14:14.030 align:start position:0% um but<00:14:12.899> this<00:14:13.019> poses<00:14:13.320> an<00:14:13.500> interesting<00:14:13.860> problem 00:14:14.030 --> 00:14:14.040 align:start position:0% but this poses an interesting problem 00:14:14.040 --> 00:14:15.410 align:start position:0% but this poses an interesting problem for<00:14:14.339> those<00:14:14.459> of<00:14:14.579> you<00:14:14.700> who<00:14:14.820> are<00:14:14.880> working<00:14:15.000> on<00:14:15.180> zero 00:14:15.410 --> 00:14:15.420 align:start position:0% for those of you who are working on zero 00:14:15.420 --> 00:14:18.170 align:start position:0% for those of you who are working on zero knowledge<00:14:15.720> proofs<00:14:16.019> because<00:14:16.459> uh<00:14:17.459> these<00:14:17.880> proofs 00:14:18.170 --> 00:14:18.180 align:start position:0% knowledge proofs because uh these proofs 00:14:18.180 --> 00:14:21.650 align:start position:0% knowledge proofs because uh these proofs need<00:14:18.480> to<00:14:18.600> be<00:14:18.860> built<00:14:19.860> on<00:14:20.700> phones 00:14:21.650 --> 00:14:21.660 align:start position:0% need to be built on phones 00:14:21.660 --> 00:14:25.370 align:start position:0% need to be built on phones and<00:14:22.320> that<00:14:22.620> doesn't<00:14:23.000> necessarily<00:14:24.000> work<00:14:24.480> with 00:14:25.370 --> 00:14:25.380 align:start position:0% and that doesn't necessarily work with 00:14:25.380 --> 00:14:27.110 align:start position:0% and that doesn't necessarily work with every<00:14:25.560> ZK<00:14:25.920> proof<00:14:26.279> system<00:14:26.399> that's<00:14:26.760> out<00:14:27.000> there 00:14:27.110 --> 00:14:27.120 align:start position:0% every ZK proof system that's out there 00:14:27.120 --> 00:14:28.370 align:start position:0% every ZK proof system that's out there right<00:14:27.300> I<00:14:27.480> don't<00:14:27.540> know<00:14:27.660> the<00:14:27.839> full<00:14:27.959> breadth<00:14:28.260> of 00:14:28.370 --> 00:14:28.380 align:start position:0% right I don't know the full breadth of 00:14:28.380 --> 00:14:29.750 align:start position:0% right I don't know the full breadth of these<00:14:28.560> things<00:14:28.680> I<00:14:28.920> don't<00:14:28.980> play<00:14:29.160> with<00:14:29.339> most<00:14:29.579> of 00:14:29.750 --> 00:14:29.760 align:start position:0% these things I don't play with most of 00:14:29.760 --> 00:14:31.750 align:start position:0% these things I don't play with most of them<00:14:29.820> most<00:14:30.060> of<00:14:30.240> my<00:14:30.300> stuff's<00:14:30.600> still<00:14:30.720> in<00:14:30.839> graph16 00:14:31.750 --> 00:14:31.760 align:start position:0% them most of my stuff's still in graph16 00:14:31.760 --> 00:14:34.069 align:start position:0% them most of my stuff's still in graph16 but<00:14:32.760> I<00:14:33.180> do<00:14:33.300> know<00:14:33.420> that<00:14:33.600> some<00:14:33.720> of<00:14:33.839> these<00:14:33.959> things 00:14:34.069 --> 00:14:34.079 align:start position:0% but I do know that some of these things 00:14:34.079 --> 00:14:36.050 align:start position:0% but I do know that some of these things are<00:14:34.260> slower<00:14:34.500> than<00:14:34.680> others<00:14:35.040> and<00:14:35.279> are<00:14:35.519> suited<00:14:35.940> to 00:14:36.050 --> 00:14:36.060 align:start position:0% are slower than others and are suited to 00:14:36.060 --> 00:14:38.690 align:start position:0% are slower than others and are suited to other<00:14:36.180> cases<00:14:36.800> and<00:14:37.800> so<00:14:37.920> there's<00:14:38.160> some<00:14:38.399> risk 00:14:38.690 --> 00:14:38.700 align:start position:0% other cases and so there's some risk 00:14:38.700 --> 00:14:39.949 align:start position:0% other cases and so there's some risk factors<00:14:39.000> that<00:14:39.180> you<00:14:39.360> might<00:14:39.420> want<00:14:39.600> to<00:14:39.720> consider 00:14:39.949 --> 00:14:39.959 align:start position:0% factors that you might want to consider 00:14:39.959 --> 00:14:41.509 align:start position:0% factors that you might want to consider if<00:14:40.139> you're<00:14:40.320> looking<00:14:40.440> at<00:14:40.620> ZK<00:14:40.980> Tech<00:14:41.220> and<00:14:41.399> trying 00:14:41.509 --> 00:14:41.519 align:start position:0% if you're looking at ZK Tech and trying 00:14:41.519 --> 00:14:43.970 align:start position:0% if you're looking at ZK Tech and trying to<00:14:41.699> figure<00:14:41.760> out<00:14:41.940> what<00:14:42.060> we<00:14:42.240> should<00:14:42.360> use<00:14:42.920> a<00:14:43.920> lot 00:14:43.970 --> 00:14:43.980 align:start position:0% to figure out what we should use a lot 00:14:43.980 --> 00:14:45.530 align:start position:0% to figure out what we should use a lot of<00:14:44.100> these<00:14:44.279> systems<00:14:44.699> the<00:14:44.880> approvers<00:14:45.420> are 00:14:45.530 --> 00:14:45.540 align:start position:0% of these systems the approvers are 00:14:45.540 --> 00:14:47.750 align:start position:0% of these systems the approvers are architected<00:14:46.079> to<00:14:46.740> running<00:14:46.920> data<00:14:47.339> centers<00:14:47.579> on 00:14:47.750 --> 00:14:47.760 align:start position:0% architected to running data centers on 00:14:47.760 --> 00:14:50.090 align:start position:0% architected to running data centers on Big<00:14:47.880> Iron<00:14:48.060> right<00:14:48.839> this<00:14:49.320> may<00:14:49.500> be<00:14:49.620> fundamental 00:14:50.090 --> 00:14:50.100 align:start position:0% Big Iron right this may be fundamental 00:14:50.100 --> 00:14:51.590 align:start position:0% Big Iron right this may be fundamental to<00:14:50.160> the<00:14:50.279> way<00:14:50.399> the<00:14:50.459> proof<00:14:50.699> system<00:14:50.820> works<00:14:51.240> it<00:14:51.480> may 00:14:51.590 --> 00:14:51.600 align:start position:0% to the way the proof system works it may 00:14:51.600 --> 00:14:53.090 align:start position:0% to the way the proof system works it may just<00:14:51.779> be<00:14:51.959> who<00:14:52.139> your<00:14:52.320> devs<00:14:52.620> were<00:14:52.680> and<00:14:52.860> what<00:14:52.980> they 00:14:53.090 --> 00:14:53.100 align:start position:0% just be who your devs were and what they 00:14:53.100 --> 00:14:55.129 align:start position:0% just be who your devs were and what they knew<00:14:53.220> how<00:14:53.339> to<00:14:53.459> do<00:14:53.579> but<00:14:54.000> either<00:14:54.180> way<00:14:54.420> it's<00:14:55.019> not 00:14:55.129 --> 00:14:55.139 align:start position:0% knew how to do but either way it's not 00:14:55.139 --> 00:14:56.150 align:start position:0% knew how to do but either way it's not clear<00:14:55.320> they're<00:14:55.440> going<00:14:55.620> to<00:14:55.680> run<00:14:55.800> efficiently 00:14:56.150 --> 00:14:56.160 align:start position:0% clear they're going to run efficiently 00:14:56.160 --> 00:14:58.550 align:start position:0% clear they're going to run efficiently on<00:14:56.279> a<00:14:56.399> mobile<00:14:56.519> phone<00:14:56.760> or<00:14:57.000> a<00:14:57.180> laptop 00:14:58.550 --> 00:14:58.560 align:start position:0% on a mobile phone or a laptop 00:14:58.560 --> 00:15:00.530 align:start position:0% on a mobile phone or a laptop um secondly<00:14:59.279> for<00:14:59.519> the<00:14:59.639> proof<00:14:59.940> systems<00:15:00.300> they 00:15:00.530 --> 00:15:00.540 align:start position:0% um secondly for the proof systems they 00:15:00.540 --> 00:15:03.470 align:start position:0% um secondly for the proof systems they may<00:15:00.660> be<00:15:00.779> amortized<00:15:01.620> uh<00:15:02.399> only<00:15:02.820> over<00:15:03.000> lots<00:15:03.420> of 00:15:03.470 --> 00:15:03.480 align:start position:0% may be amortized uh only over lots of 00:15:03.480 --> 00:15:05.269 align:start position:0% may be amortized uh only over lots of transactions<00:15:04.079> right<00:15:04.560> so<00:15:04.800> they're<00:15:04.980> not<00:15:05.100> really 00:15:05.269 --> 00:15:05.279 align:start position:0% transactions right so they're not really 00:15:05.279 --> 00:15:06.650 align:start position:0% transactions right so they're not really efficient<00:15:05.639> unless<00:15:05.940> you<00:15:06.060> put<00:15:06.240> a<00:15:06.420> thousand 00:15:06.650 --> 00:15:06.660 align:start position:0% efficient unless you put a thousand 00:15:06.660 --> 00:15:08.090 align:start position:0% efficient unless you put a thousand transactions<00:15:07.260> into<00:15:07.380> this<00:15:07.560> proof<00:15:07.860> and<00:15:07.920> check 00:15:08.090 --> 00:15:08.100 align:start position:0% transactions into this proof and check 00:15:08.100 --> 00:15:10.250 align:start position:0% transactions into this proof and check them<00:15:08.339> and<00:15:08.699> then<00:15:08.820> you<00:15:08.940> get<00:15:09.120> some<00:15:09.420> amortized 00:15:10.250 --> 00:15:10.260 align:start position:0% them and then you get some amortized 00:15:10.260 --> 00:15:12.290 align:start position:0% them and then you get some amortized savings<00:15:10.560> which<00:15:11.279> is<00:15:11.399> fine<00:15:11.639> for<00:15:11.880> a<00:15:12.000> server 00:15:12.290 --> 00:15:12.300 align:start position:0% savings which is fine for a server 00:15:12.300 --> 00:15:14.030 align:start position:0% savings which is fine for a server compressing<00:15:12.779> transactions<00:15:13.320> to<00:15:13.500> do<00:15:13.620> a<00:15:13.740> roll-up 00:15:14.030 --> 00:15:14.040 align:start position:0% compressing transactions to do a roll-up 00:15:14.040 --> 00:15:16.730 align:start position:0% compressing transactions to do a roll-up but<00:15:14.639> again<00:15:14.820> in<00:15:15.420> these<00:15:15.600> cases<00:15:15.839> you<00:15:16.199> need<00:15:16.320> phones 00:15:16.730 --> 00:15:16.740 align:start position:0% but again in these cases you need phones 00:15:16.740 --> 00:15:18.290 align:start position:0% but again in these cases you need phones to<00:15:16.920> be<00:15:16.980> generating<00:15:17.279> proof<00:15:17.639> so<00:15:17.760> laptops<00:15:18.120> to<00:15:18.180> be 00:15:18.290 --> 00:15:18.300 align:start position:0% to be generating proof so laptops to be 00:15:18.300 --> 00:15:19.490 align:start position:0% to be generating proof so laptops to be generating<00:15:18.540> proof<00:15:18.839> so<00:15:18.959> the<00:15:19.139> server<00:15:19.380> doesn't 00:15:19.490 --> 00:15:19.500 align:start position:0% generating proof so the server doesn't 00:15:19.500 --> 00:15:21.590 align:start position:0% generating proof so the server doesn't see<00:15:19.680> what's<00:15:19.860> going<00:15:20.040> on<00:15:20.220> and<00:15:21.180> that's<00:15:21.360> only 00:15:21.590 --> 00:15:21.600 align:start position:0% see what's going on and that's only 00:15:21.600 --> 00:15:24.829 align:start position:0% see what's going on and that's only going<00:15:22.019> to<00:15:22.079> have<00:15:22.199> one<00:15:22.500> transaction<00:15:22.980> in<00:15:23.220> it<00:15:23.839> and 00:15:24.829 --> 00:15:24.839 align:start position:0% going to have one transaction in it and 00:15:24.839 --> 00:15:26.329 align:start position:0% going to have one transaction in it and lastly<00:15:25.139> the<00:15:25.560> proofs<00:15:25.800> in<00:15:25.980> a<00:15:26.040> lot<00:15:26.160> of<00:15:26.220> these 00:15:26.329 --> 00:15:26.339 align:start position:0% lastly the proofs in a lot of these 00:15:26.339 --> 00:15:27.650 align:start position:0% lastly the proofs in a lot of these things<00:15:26.459> are<00:15:26.639> very<00:15:26.760> large<00:15:26.940> which<00:15:27.300> is<00:15:27.420> going<00:15:27.600> to 00:15:27.650 --> 00:15:27.660 align:start position:0% things are very large which is going to 00:15:27.660 --> 00:15:28.910 align:start position:0% things are very large which is going to cause<00:15:27.779> all<00:15:28.019> kinds<00:15:28.199> of<00:15:28.260> problems<00:15:28.560> for<00:15:28.680> mobile 00:15:28.910 --> 00:15:28.920 align:start position:0% cause all kinds of problems for mobile 00:15:28.920 --> 00:15:31.129 align:start position:0% cause all kinds of problems for mobile data<00:15:29.279> for<00:15:29.459> your<00:15:29.639> gossip<00:15:29.940> protocols<00:15:30.480> for 00:15:31.129 --> 00:15:31.139 align:start position:0% data for your gossip protocols for 00:15:31.139 --> 00:15:32.810 align:start position:0% data for your gossip protocols for transaction<00:15:31.440> distributions<00:15:31.980> this<00:15:32.399> is<00:15:32.459> also<00:15:32.699> a 00:15:32.810 --> 00:15:32.820 align:start position:0% transaction distributions this is also a 00:15:32.820 --> 00:15:33.829 align:start position:0% transaction distributions this is also a warning<00:15:33.120> sign 00:15:33.829 --> 00:15:33.839 align:start position:0% warning sign 00:15:33.839 --> 00:15:35.449 align:start position:0% warning sign and<00:15:34.139> so<00:15:34.260> the<00:15:34.380> way<00:15:34.500> to<00:15:34.680> think<00:15:34.800> about<00:15:34.980> this<00:15:35.220> or<00:15:35.399> at 00:15:35.449 --> 00:15:35.459 align:start position:0% and so the way to think about this or at 00:15:35.459 --> 00:15:36.949 align:start position:0% and so the way to think about this or at least<00:15:35.579> I<00:15:35.760> think<00:15:35.940> about<00:15:36.060> this<00:15:36.300> is<00:15:36.540> you<00:15:36.779> may 00:15:36.949 --> 00:15:36.959 align:start position:0% least I think about this is you may 00:15:36.959 --> 00:15:38.150 align:start position:0% least I think about this is you may remember<00:15:37.079> that<00:15:37.380> there's<00:15:37.560> been<00:15:37.740> this<00:15:37.980> big 00:15:38.150 --> 00:15:38.160 align:start position:0% remember that there's been this big 00:15:38.160 --> 00:15:40.250 align:start position:0% remember that there's been this big problem<00:15:38.399> with<00:15:38.699> Intel<00:15:39.060> and<00:15:39.240> x86<00:15:39.779> for<00:15:40.019> the<00:15:40.139> past 00:15:40.250 --> 00:15:40.260 align:start position:0% problem with Intel and x86 for the past 00:15:40.260 --> 00:15:42.889 align:start position:0% problem with Intel and x86 for the past about<00:15:40.440> 15<00:15:40.800> years<00:15:41.160> where<00:15:41.699> Intel<00:15:42.360> built<00:15:42.720> these 00:15:42.889 --> 00:15:42.899 align:start position:0% about 15 years where Intel built these 00:15:42.899 --> 00:15:45.530 align:start position:0% about 15 years where Intel built these wonderful<00:15:43.320> server<00:15:43.820> chips<00:15:44.820> and<00:15:45.240> then<00:15:45.360> they 00:15:45.530 --> 00:15:45.540 align:start position:0% wonderful server chips and then they 00:15:45.540 --> 00:15:46.850 align:start position:0% wonderful server chips and then they found<00:15:45.660> out<00:15:45.839> the<00:15:46.079> future<00:15:46.199> of<00:15:46.440> the<00:15:46.560> world<00:15:46.680> was 00:15:46.850 --> 00:15:46.860 align:start position:0% found out the future of the world was 00:15:46.860 --> 00:15:48.470 align:start position:0% found out the future of the world was mobile<00:15:47.100> devices<00:15:47.519> and<00:15:47.940> they've<00:15:48.120> been<00:15:48.240> trying 00:15:48.470 --> 00:15:48.480 align:start position:0% mobile devices and they've been trying 00:15:48.480 --> 00:15:49.910 align:start position:0% mobile devices and they've been trying to<00:15:48.660> play<00:15:48.839> catch-up<00:15:49.260> with<00:15:49.500> getting<00:15:49.680> their 00:15:49.910 --> 00:15:49.920 align:start position:0% to play catch-up with getting their 00:15:49.920 --> 00:15:52.490 align:start position:0% to play catch-up with getting their chips<00:15:50.160> to<00:15:50.399> work<00:15:50.519> on<00:15:50.880> mobile<00:15:51.079> and<00:15:52.079> there's<00:15:52.320> some 00:15:52.490 --> 00:15:52.500 align:start position:0% chips to work on mobile and there's some 00:15:52.500 --> 00:15:53.509 align:start position:0% chips to work on mobile and there's some business<00:15:52.680> development<00:15:53.160> things<00:15:53.339> there 00:15:53.509 --> 00:15:53.519 align:start position:0% business development things there 00:15:53.519 --> 00:15:54.650 align:start position:0% business development things there there's<00:15:53.820> some<00:15:54.000> fundamental<00:15:54.360> technical 00:15:54.650 --> 00:15:54.660 align:start position:0% there's some fundamental technical 00:15:54.660 --> 00:15:56.689 align:start position:0% there's some fundamental technical things<00:15:54.839> or<00:15:55.079> some<00:15:55.199> business<00:15:55.500> positioning<00:15:56.279> that 00:15:56.689 --> 00:15:56.699 align:start position:0% things or some business positioning that 00:15:56.699 --> 00:15:59.090 align:start position:0% things or some business positioning that have<00:15:56.880> causing<00:15:57.180> them<00:15:57.300> problems<00:15:57.779> and<00:15:58.440> so<00:15:58.680> we<00:15:58.980> may 00:15:59.090 --> 00:15:59.100 align:start position:0% have causing them problems and so we may 00:15:59.100 --> 00:16:00.650 align:start position:0% have causing them problems and so we may end<00:15:59.220> up<00:15:59.339> in<00:15:59.459> a<00:15:59.579> similar<00:15:59.760> situation<00:16:00.120> with<00:16:00.300> ZK 00:16:00.650 --> 00:16:00.660 align:start position:0% end up in a similar situation with ZK 00:16:00.660 --> 00:16:02.689 align:start position:0% end up in a similar situation with ZK proofs<00:16:01.079> where<00:16:01.320> you<00:16:01.980> can't<00:16:02.100> get<00:16:02.220> these<00:16:02.459> to<00:16:02.579> work 00:16:02.689 --> 00:16:02.699 align:start position:0% proofs where you can't get these to work 00:16:02.699 --> 00:16:04.069 align:start position:0% proofs where you can't get these to work in<00:16:02.880> the<00:16:03.000> right<00:16:03.120> settings<00:16:03.420> you<00:16:03.660> want<00:16:03.839> and<00:16:03.959> then 00:16:04.069 --> 00:16:04.079 align:start position:0% in the right settings you want and then 00:16:04.079 --> 00:16:05.329 align:start position:0% in the right settings you want and then you're<00:16:04.199> gonna<00:16:04.320> have<00:16:04.440> to<00:16:04.500> do<00:16:04.560> a<00:16:04.740> nested<00:16:05.100> ZK 00:16:05.329 --> 00:16:05.339 align:start position:0% you're gonna have to do a nested ZK 00:16:05.339 --> 00:16:07.129 align:start position:0% you're gonna have to do a nested ZK thing<00:16:05.639> you<00:16:05.760> have<00:16:05.880> to<00:16:06.060> add<00:16:06.180> another<00:16:06.360> ZK<00:16:06.720> proof 00:16:07.129 --> 00:16:07.139 align:start position:0% thing you have to add another ZK proof 00:16:07.139 --> 00:16:09.230 align:start position:0% thing you have to add another ZK proof under<00:16:07.440> your<00:16:07.680> ZK<00:16:08.100> proof<00:16:08.519> in<00:16:09.060> a<00:16:09.180> different 00:16:09.230 --> 00:16:09.240 align:start position:0% under your ZK proof in a different 00:16:09.240 --> 00:16:10.910 align:start position:0% under your ZK proof in a different system<00:16:09.540> that's<00:16:10.139> going<00:16:10.320> to<00:16:10.440> drop<00:16:10.440> your<00:16:10.620> costs 00:16:10.910 --> 00:16:10.920 align:start position:0% system that's going to drop your costs 00:16:10.920 --> 00:16:13.370 align:start position:0% system that's going to drop your costs and<00:16:10.980> up<00:16:11.100> your<00:16:11.220> complexity<00:16:12.060> so<00:16:12.779> Food<00:16:13.199> For 00:16:13.370 --> 00:16:13.380 align:start position:0% and up your complexity so Food For 00:16:13.380 --> 00:16:14.449 align:start position:0% and up your complexity so Food For Thought<00:16:13.560> for<00:16:13.800> those<00:16:13.860> of<00:16:13.980> you<00:16:14.100> who<00:16:14.160> are<00:16:14.279> working 00:16:14.449 --> 00:16:14.459 align:start position:0% Thought for those of you who are working 00:16:14.459 --> 00:16:16.069 align:start position:0% Thought for those of you who are working on<00:16:14.639> these<00:16:14.880> things 00:16:16.069 --> 00:16:16.079 align:start position:0% on these things 00:16:16.079 --> 00:16:16.850 align:start position:0% on these things um 00:16:16.850 --> 00:16:16.860 align:start position:0% um 00:16:16.860 --> 00:16:20.210 align:start position:0% um so<00:16:18.000> okay<00:16:18.540> that's<00:16:18.899> the<00:16:19.139> basic<00:16:19.440> like<00:16:19.800> pressing 00:16:20.210 --> 00:16:20.220 align:start position:0% so okay that's the basic like pressing 00:16:20.220 --> 00:16:21.829 align:start position:0% so okay that's the basic like pressing issue<00:16:20.519> today<00:16:20.699> but<00:16:21.000> looking<00:16:21.180> more<00:16:21.540> broadly 00:16:21.829 --> 00:16:21.839 align:start position:0% issue today but looking more broadly 00:16:21.839 --> 00:16:23.569 align:start position:0% issue today but looking more broadly what<00:16:22.079> else<00:16:22.199> can<00:16:22.440> we<00:16:22.560> use<00:16:22.740> as<00:16:23.040> your<00:16:23.279> knowledge 00:16:23.569 --> 00:16:23.579 align:start position:0% what else can we use as your knowledge 00:16:23.579 --> 00:16:25.310 align:start position:0% what else can we use as your knowledge proofs<00:16:23.880> for<00:16:24.060> right<00:16:24.600> if<00:16:24.779> we<00:16:24.899> have<00:16:24.959> this<00:16:25.079> notion 00:16:25.310 --> 00:16:25.320 align:start position:0% proofs for right if we have this notion 00:16:25.320 --> 00:16:27.590 align:start position:0% proofs for right if we have this notion of<00:16:25.380> credibility<00:16:25.740> carrying<00:16:26.339> data<00:16:26.699> right<00:16:27.300> what 00:16:27.590 --> 00:16:27.600 align:start position:0% of credibility carrying data right what 00:16:27.600 --> 00:16:30.170 align:start position:0% of credibility carrying data right what can<00:16:27.779> we<00:16:27.899> use<00:16:28.019> it<00:16:28.199> for<00:16:28.800> and<00:16:29.339> I<00:16:29.760> think<00:16:29.820> you<00:16:30.060> can 00:16:30.170 --> 00:16:30.180 align:start position:0% can we use it for and I think you can 00:16:30.180 --> 00:16:32.629 align:start position:0% can we use it for and I think you can more<00:16:30.420> broadly<00:16:30.720> do<00:16:30.899> this<00:16:31.019> for<00:16:31.260> markets<00:16:31.860> uh<00:16:32.399> like 00:16:32.629 --> 00:16:32.639 align:start position:0% more broadly do this for markets uh like 00:16:32.639 --> 00:16:35.569 align:start position:0% more broadly do this for markets uh like competition<00:16:33.600> uh<00:16:34.139> decentralization<00:16:34.800> uh 00:16:35.569 --> 00:16:35.579 align:start position:0% competition uh decentralization uh 00:16:35.579 --> 00:16:36.889 align:start position:0% competition uh decentralization uh migrating<00:16:35.880> data<00:16:36.240> around<00:16:36.360> is<00:16:36.600> going<00:16:36.779> to<00:16:36.839> be<00:16:36.839> a 00:16:36.889 --> 00:16:36.899 align:start position:0% migrating data around is going to be a 00:16:36.899 --> 00:16:38.329 align:start position:0% migrating data around is going to be a big<00:16:37.019> one<00:16:37.139> and<00:16:37.440> obviously<00:16:37.800> you<00:16:37.920> can<00:16:38.040> also<00:16:38.220> use 00:16:38.329 --> 00:16:38.339 align:start position:0% big one and obviously you can also use 00:16:38.339 --> 00:16:40.150 align:start position:0% big one and obviously you can also use it<00:16:38.459> for<00:16:38.639> like<00:16:38.880> preventing<00:16:39.420> money<00:16:39.600> laundering 00:16:40.150 --> 00:16:40.160 align:start position:0% it for like preventing money laundering 00:16:40.160 --> 00:16:42.170 align:start position:0% it for like preventing money laundering so<00:16:41.160> starting<00:16:41.339> with<00:16:41.579> the<00:16:41.759> last<00:16:41.820> one<00:16:41.940> of<00:16:42.120> those 00:16:42.170 --> 00:16:42.180 align:start position:0% so starting with the last one of those 00:16:42.180 --> 00:16:44.930 align:start position:0% so starting with the last one of those cryptocurrency<00:16:42.899> has<00:16:43.199> a<00:16:43.500> theft<00:16:43.800> problem<00:16:44.160> right 00:16:44.930 --> 00:16:44.940 align:start position:0% cryptocurrency has a theft problem right 00:16:44.940 --> 00:16:47.389 align:start position:0% cryptocurrency has a theft problem right this<00:16:45.480> is<00:16:45.660> uh 00:16:47.389 --> 00:16:47.399 align:start position:0% this is uh 00:16:47.399 --> 00:16:50.090 align:start position:0% this is uh stuff<00:16:47.880> gets<00:16:48.240> stolen<00:16:48.540> now<00:16:49.380> by<00:16:49.620> nation<00:16:49.800> states 00:16:50.090 --> 00:16:50.100 align:start position:0% stuff gets stolen now by nation states 00:16:50.100 --> 00:16:51.470 align:start position:0% stuff gets stolen now by nation states the<00:16:50.339> nation<00:16:50.519> states<00:16:50.759> actually<00:16:51.000> go<00:16:51.180> get<00:16:51.360> in 00:16:51.470 --> 00:16:51.480 align:start position:0% the nation states actually go get in 00:16:51.480 --> 00:16:53.269 align:start position:0% the nation states actually go get in trouble<00:16:51.600> tornado<00:16:52.199> cash<00:16:52.380> got<00:16:52.680> taken<00:16:53.100> down 00:16:53.269 --> 00:16:53.279 align:start position:0% trouble tornado cash got taken down 00:16:53.279 --> 00:16:54.470 align:start position:0% trouble tornado cash got taken down because<00:16:53.519> of<00:16:53.699> this<00:16:53.820> actually<00:16:54.000> the<00:16:54.180> tornado 00:16:54.470 --> 00:16:54.480 align:start position:0% because of this actually the tornado 00:16:54.480 --> 00:16:57.470 align:start position:0% because of this actually the tornado developer<00:16:55.259> is<00:16:55.560> in<00:16:55.860> prison<00:16:56.699> right<00:16:57.000> now<00:16:57.120> in<00:16:57.360> the 00:16:57.470 --> 00:16:57.480 align:start position:0% developer is in prison right now in the 00:16:57.480 --> 00:16:59.389 align:start position:0% developer is in prison right now in the Netherlands<00:16:57.899> because<00:16:58.079> of<00:16:58.259> this<00:16:58.440> which<00:16:59.220> is 00:16:59.389 --> 00:16:59.399 align:start position:0% Netherlands because of this which is 00:16:59.399 --> 00:17:01.370 align:start position:0% Netherlands because of this which is kind<00:16:59.699> of<00:16:59.820> crazy<00:17:00.000> for<00:17:00.480> you<00:17:00.720> know 00:17:01.370 --> 00:17:01.380 align:start position:0% kind of crazy for you know 00:17:01.380 --> 00:17:02.810 align:start position:0% kind of crazy for you know thing<00:17:01.680> that<00:17:01.860> came<00:17:01.980> out<00:17:02.100> of<00:17:02.160> a<00:17:02.279> paper<00:17:02.399> I<00:17:02.579> started 00:17:02.810 --> 00:17:02.820 align:start position:0% thing that came out of a paper I started 00:17:02.820 --> 00:17:04.730 align:start position:0% thing that came out of a paper I started writing<00:17:03.060> 10<00:17:03.180> years<00:17:03.360> ago<00:17:03.660> but<00:17:04.199> this<00:17:04.439> is<00:17:04.559> what's 00:17:04.730 --> 00:17:04.740 align:start position:0% writing 10 years ago but this is what's 00:17:04.740 --> 00:17:05.990 align:start position:0% writing 10 years ago but this is what's going<00:17:04.980> on 00:17:05.990 --> 00:17:06.000 align:start position:0% going on 00:17:06.000 --> 00:17:08.030 align:start position:0% going on um<00:17:06.179> and<00:17:06.720> it<00:17:07.140> would<00:17:07.260> be<00:17:07.380> good<00:17:07.500> if<00:17:07.620> we<00:17:07.740> had<00:17:07.860> some 00:17:08.030 --> 00:17:08.040 align:start position:0% um and it would be good if we had some 00:17:08.040 --> 00:17:09.470 align:start position:0% um and it would be good if we had some way<00:17:08.160> to<00:17:08.339> deal<00:17:08.459> with<00:17:08.699> this 00:17:09.470 --> 00:17:09.480 align:start position:0% way to deal with this 00:17:09.480 --> 00:17:12.289 align:start position:0% way to deal with this so<00:17:09.839> what<00:17:10.020> if<00:17:10.260> you<00:17:10.380> wanted<00:17:10.559> to<00:17:10.799> prove<00:17:11.339> uh<00:17:12.059> to 00:17:12.289 --> 00:17:12.299 align:start position:0% so what if you wanted to prove uh to 00:17:12.299 --> 00:17:13.429 align:start position:0% so what if you wanted to prove uh to somebody<00:17:12.419> when<00:17:12.720> you<00:17:12.780> make<00:17:12.900> a<00:17:13.020> payment<00:17:13.140> the 00:17:13.429 --> 00:17:13.439 align:start position:0% somebody when you make a payment the 00:17:13.439 --> 00:17:15.710 align:start position:0% somebody when you make a payment the money<00:17:13.679> you<00:17:13.860> had<00:17:13.980> wasn't<00:17:14.280> stolen<00:17:14.760> and<00:17:15.540> you 00:17:15.710 --> 00:17:15.720 align:start position:0% money you had wasn't stolen and you 00:17:15.720 --> 00:17:16.669 align:start position:0% money you had wasn't stolen and you wanted<00:17:15.839> to<00:17:16.020> show<00:17:16.079> them<00:17:16.260> that<00:17:16.439> the<00:17:16.559> money 00:17:16.669 --> 00:17:16.679 align:start position:0% wanted to show them that the money 00:17:16.679 --> 00:17:18.110 align:start position:0% wanted to show them that the money wasn't<00:17:16.980> stolen<00:17:17.400> when<00:17:17.579> you<00:17:17.699> got<00:17:17.819> it<00:17:17.939> from 00:17:18.110 --> 00:17:18.120 align:start position:0% wasn't stolen when you got it from 00:17:18.120 --> 00:17:19.970 align:start position:0% wasn't stolen when you got it from somebody<00:17:18.360> and<00:17:19.020> when<00:17:19.199> that<00:17:19.380> person<00:17:19.559> got<00:17:19.799> it 00:17:19.970 --> 00:17:19.980 align:start position:0% somebody and when that person got it 00:17:19.980 --> 00:17:21.650 align:start position:0% somebody and when that person got it from<00:17:20.100> somebody<00:17:20.280> that<00:17:20.760> money<00:17:20.880> wasn't<00:17:21.179> stolen 00:17:21.650 --> 00:17:21.660 align:start position:0% from somebody that money wasn't stolen 00:17:21.660 --> 00:17:24.049 align:start position:0% from somebody that money wasn't stolen then<00:17:21.780> either<00:17:22.140> right<00:17:22.799> add<00:17:23.100> infinitum<00:17:23.760> all<00:17:23.939> the 00:17:24.049 --> 00:17:24.059 align:start position:0% then either right add infinitum all the 00:17:24.059 --> 00:17:25.189 align:start position:0% then either right add infinitum all the way<00:17:24.120> back 00:17:25.189 --> 00:17:25.199 align:start position:0% way back 00:17:25.199 --> 00:17:27.169 align:start position:0% way back this<00:17:25.860> is<00:17:25.980> impossible<00:17:26.400> if<00:17:26.579> you're<00:17:26.760> just<00:17:26.880> asking 00:17:27.169 --> 00:17:27.179 align:start position:0% this is impossible if you're just asking 00:17:27.179 --> 00:17:28.250 align:start position:0% this is impossible if you're just asking questions<00:17:27.360> you<00:17:27.660> can't<00:17:27.780> do<00:17:27.959> this<00:17:28.079> without 00:17:28.250 --> 00:17:28.260 align:start position:0% questions you can't do this without 00:17:28.260 --> 00:17:30.289 align:start position:0% questions you can't do this without cryptography<00:17:28.980> right<00:17:29.100> if<00:17:29.280> you<00:17:29.400> just<00:17:29.520> do<00:17:29.640> kyc<00:17:30.120> or 00:17:30.289 --> 00:17:30.299 align:start position:0% cryptography right if you just do kyc or 00:17:30.299 --> 00:17:32.510 align:start position:0% cryptography right if you just do kyc or whatever<00:17:30.419> you'll<00:17:31.260> stop<00:17:31.380> at<00:17:31.679> just<00:17:31.919> who<00:17:32.100> you<00:17:32.280> are 00:17:32.510 --> 00:17:32.520 align:start position:0% whatever you'll stop at just who you are 00:17:32.520 --> 00:17:34.370 align:start position:0% whatever you'll stop at just who you are who<00:17:32.820> who's<00:17:33.000> giving<00:17:33.299> you<00:17:33.419> the<00:17:33.600> money<00:17:33.720> and<00:17:34.260> you 00:17:34.370 --> 00:17:34.380 align:start position:0% who who's giving you the money and you 00:17:34.380 --> 00:17:35.630 align:start position:0% who who's giving you the money and you won't<00:17:34.500> really<00:17:34.620> get<00:17:34.860> a<00:17:34.919> good<00:17:35.039> notion<00:17:35.400> of<00:17:35.520> what's 00:17:35.630 --> 00:17:35.640 align:start position:0% won't really get a good notion of what's 00:17:35.640 --> 00:17:37.669 align:start position:0% won't really get a good notion of what's going<00:17:35.820> on<00:17:35.940> but<00:17:36.419> ZK<00:17:36.780> proofs<00:17:37.260> compose 00:17:37.669 --> 00:17:37.679 align:start position:0% going on but ZK proofs compose 00:17:37.679 --> 00:17:39.409 align:start position:0% going on but ZK proofs compose recursively<00:17:38.280> right<00:17:38.640> so<00:17:38.880> I<00:17:39.000> actually<00:17:39.120> can 00:17:39.409 --> 00:17:39.419 align:start position:0% recursively right so I actually can 00:17:39.419 --> 00:17:40.850 align:start position:0% recursively right so I actually can build<00:17:39.660> a<00:17:39.780> zero<00:17:40.080> knowledge<00:17:40.260> proof<00:17:40.620> that<00:17:40.679> not 00:17:40.850 --> 00:17:40.860 align:start position:0% build a zero knowledge proof that not 00:17:40.860 --> 00:17:42.650 align:start position:0% build a zero knowledge proof that not only<00:17:40.980> is<00:17:41.220> my<00:17:41.400> money<00:17:41.520> not<00:17:41.760> on<00:17:41.940> a<00:17:42.059> list<00:17:42.179> of<00:17:42.299> stolen 00:17:42.650 --> 00:17:42.660 align:start position:0% only is my money not on a list of stolen 00:17:42.660 --> 00:17:44.330 align:start position:0% only is my money not on a list of stolen money<00:17:42.840> but<00:17:43.200> it<00:17:43.320> wasn't<00:17:43.500> on<00:17:43.679> a<00:17:43.799> list<00:17:43.919> of<00:17:44.039> stolen 00:17:44.330 --> 00:17:44.340 align:start position:0% money but it wasn't on a list of stolen 00:17:44.340 --> 00:17:45.590 align:start position:0% money but it wasn't on a list of stolen money<00:17:44.460> when<00:17:44.640> it<00:17:44.760> was<00:17:44.880> paid<00:17:45.000> to<00:17:45.179> me<00:17:45.299> and<00:17:45.480> that 00:17:45.590 --> 00:17:45.600 align:start position:0% money when it was paid to me and that 00:17:45.600 --> 00:17:46.789 align:start position:0% money when it was paid to me and that wasn't<00:17:45.780> on<00:17:45.960> a<00:17:46.080> list<00:17:46.140> of<00:17:46.260> stolen<00:17:46.500> money<00:17:46.620> before 00:17:46.789 --> 00:17:46.799 align:start position:0% wasn't on a list of stolen money before 00:17:46.799 --> 00:17:48.650 align:start position:0% wasn't on a list of stolen money before that<00:17:47.039> before<00:17:47.280> that<00:17:47.580> all<00:17:48.000> the<00:17:48.240> way<00:17:48.299> back<00:17:48.480> in 00:17:48.650 --> 00:17:48.660 align:start position:0% that before that all the way back in 00:17:48.660 --> 00:17:50.330 align:start position:0% that before that all the way back in time<00:17:48.840> so<00:17:49.440> we<00:17:49.559> can<00:17:49.679> have<00:17:49.860> this<00:17:50.039> sort<00:17:50.220> of 00:17:50.330 --> 00:17:50.340 align:start position:0% time so we can have this sort of 00:17:50.340 --> 00:17:52.070 align:start position:0% time so we can have this sort of credible<00:17:50.700> money<00:17:51.000> where<00:17:51.360> despite<00:17:51.780> the<00:17:51.960> fact 00:17:52.070 --> 00:17:52.080 align:start position:0% credible money where despite the fact 00:17:52.080 --> 00:17:54.289 align:start position:0% credible money where despite the fact that<00:17:52.200> I'm<00:17:52.380> anonymous<00:17:53.340> you<00:17:53.940> actually<00:17:54.059> know 00:17:54.289 --> 00:17:54.299 align:start position:0% that I'm anonymous you actually know 00:17:54.299 --> 00:17:55.789 align:start position:0% that I'm anonymous you actually know that<00:17:54.480> it's<00:17:54.600> not<00:17:54.780> stolen 00:17:55.789 --> 00:17:55.799 align:start position:0% that it's not stolen 00:17:55.799 --> 00:17:57.230 align:start position:0% that it's not stolen all<00:17:56.220> right<00:17:56.220> so<00:17:56.460> that's<00:17:56.580> one<00:17:56.760> thing<00:17:56.940> you<00:17:57.059> could 00:17:57.230 --> 00:17:57.240 align:start position:0% all right so that's one thing you could 00:17:57.240 --> 00:17:59.390 align:start position:0% all right so that's one thing you could build<00:17:57.559> details<00:17:58.559> are<00:17:58.679> somewhat<00:17:58.919> complex<00:17:59.160> by 00:17:59.390 --> 00:17:59.400 align:start position:0% build details are somewhat complex by 00:17:59.400 --> 00:18:01.190 align:start position:0% build details are somewhat complex by the<00:17:59.520> way<00:17:59.580> but<00:17:59.820> it<00:17:59.940> is<00:18:00.059> possible 00:18:01.190 --> 00:18:01.200 align:start position:0% the way but it is possible 00:18:01.200 --> 00:18:02.870 align:start position:0% the way but it is possible um 00:18:02.870 --> 00:18:02.880 align:start position:0% um 00:18:02.880 --> 00:18:05.029 align:start position:0% um right<00:18:03.299> more<00:18:03.720> broadly<00:18:04.080> you<00:18:04.260> can<00:18:04.500> do<00:18:04.559> all<00:18:04.740> kinds 00:18:05.029 --> 00:18:05.039 align:start position:0% right more broadly you can do all kinds 00:18:05.039 --> 00:18:06.230 align:start position:0% right more broadly you can do all kinds of<00:18:05.100> compliance<00:18:05.520> right<00:18:05.700> you<00:18:05.880> want<00:18:05.940> to<00:18:06.059> comply 00:18:06.230 --> 00:18:06.240 align:start position:0% of compliance right you want to comply 00:18:06.240 --> 00:18:08.630 align:start position:0% of compliance right you want to comply with<00:18:06.419> anti-money<00:18:07.080> laundering<00:18:07.440> rules<00:18:07.860> uh 00:18:08.630 --> 00:18:08.640 align:start position:0% with anti-money laundering rules uh 00:18:08.640 --> 00:18:10.070 align:start position:0% with anti-money laundering rules uh currency<00:18:08.940> transaction<00:18:09.299> reports<00:18:09.840> that<00:18:09.960> you're 00:18:10.070 --> 00:18:10.080 align:start position:0% currency transaction reports that you're 00:18:10.080 --> 00:18:11.630 align:start position:0% currency transaction reports that you're sending<00:18:10.440> you're<00:18:10.799> not<00:18:10.919> sending<00:18:11.220> more<00:18:11.340> than<00:18:11.460> ten 00:18:11.630 --> 00:18:11.640 align:start position:0% sending you're not sending more than ten 00:18:11.640 --> 00:18:14.210 align:start position:0% sending you're not sending more than ten thousand<00:18:11.760> dollars<00:18:12.179> uh<00:18:12.900> through<00:18:13.080> a<00:18:13.260> system<00:18:13.380> you 00:18:14.210 --> 00:18:14.220 align:start position:0% thousand dollars uh through a system you 00:18:14.220 --> 00:18:16.430 align:start position:0% thousand dollars uh through a system you can<00:18:14.340> do<00:18:14.460> that<00:18:14.700> right<00:18:15.240> in<00:18:15.840> theory<00:18:16.020> we<00:18:16.200> knew<00:18:16.320> how 00:18:16.430 --> 00:18:16.440 align:start position:0% can do that right in theory we knew how 00:18:16.440 --> 00:18:18.289 align:start position:0% can do that right in theory we knew how to<00:18:16.559> do<00:18:16.679> this<00:18:16.799> in<00:18:16.980> in<00:18:17.100> 2016<00:18:17.520> so<00:18:17.820> the<00:18:17.940> paper<00:18:18.120> I 00:18:18.289 --> 00:18:18.299 align:start position:0% to do this in in 2016 so the paper I 00:18:18.299 --> 00:18:20.390 align:start position:0% to do this in in 2016 so the paper I wrote<00:18:18.419> at<00:18:18.660> Financial<00:18:18.840> cryptography<00:18:19.559> uh<00:18:20.160> but 00:18:20.390 --> 00:18:20.400 align:start position:0% wrote at Financial cryptography uh but 00:18:20.400 --> 00:18:21.409 align:start position:0% wrote at Financial cryptography uh but now<00:18:20.580> there<00:18:20.880> are<00:18:21.000> actually<00:18:21.059> companies 00:18:21.409 --> 00:18:21.419 align:start position:0% now there are actually companies 00:18:21.419 --> 00:18:22.730 align:start position:0% now there are actually companies building<00:18:21.660> this<00:18:21.900> because<00:18:22.020> again<00:18:22.200> we<00:18:22.440> have<00:18:22.559> more 00:18:22.730 --> 00:18:22.740 align:start position:0% building this because again we have more 00:18:22.740 --> 00:18:24.590 align:start position:0% building this because again we have more practical<00:18:23.039> zero<00:18:23.460> knowledge<00:18:23.760> proofs<00:18:24.059> in<00:18:24.419> part 00:18:24.590 --> 00:18:24.600 align:start position:0% practical zero knowledge proofs in part 00:18:24.600 --> 00:18:25.610 align:start position:0% practical zero knowledge proofs in part because<00:18:24.720> of<00:18:24.900> the<00:18:25.020> people<00:18:25.080> working<00:18:25.320> on 00:18:25.610 --> 00:18:25.620 align:start position:0% because of the people working on 00:18:25.620 --> 00:18:26.750 align:start position:0% because of the people working on Roll-Ups 00:18:26.750 --> 00:18:26.760 align:start position:0% Roll-Ups 00:18:26.760 --> 00:18:28.130 align:start position:0% Roll-Ups um<00:18:26.880> you<00:18:27.179> want<00:18:27.360> to<00:18:27.480> show<00:18:27.539> you're<00:18:27.720> not<00:18:27.900> on<00:18:28.020> the 00:18:28.130 --> 00:18:28.140 align:start position:0% um you want to show you're not on the 00:18:28.140 --> 00:18:30.110 align:start position:0% um you want to show you're not on the sanctions<00:18:28.500> list<00:18:28.620> we<00:18:28.919> can<00:18:29.100> do<00:18:29.220> that<00:18:29.400> so<00:18:29.880> this<00:18:30.059> is 00:18:30.110 --> 00:18:30.120 align:start position:0% sanctions list we can do that so this is 00:18:30.120 --> 00:18:31.549 align:start position:0% sanctions list we can do that so this is again<00:18:30.299> you<00:18:30.600> can<00:18:30.720> get<00:18:30.780> credibility<00:18:31.140> for<00:18:31.380> what's 00:18:31.549 --> 00:18:31.559 align:start position:0% again you can get credibility for what's 00:18:31.559 --> 00:18:33.230 align:start position:0% again you can get credibility for what's going<00:18:31.740> on<00:18:31.799> with<00:18:32.039> money 00:18:33.230 --> 00:18:33.240 align:start position:0% going on with money 00:18:33.240 --> 00:18:33.890 align:start position:0% going on with money um 00:18:33.890 --> 00:18:33.900 align:start position:0% um 00:18:33.900 --> 00:18:36.169 align:start position:0% um more<00:18:34.679> broadly<00:18:35.039> though<00:18:35.340> right<00:18:35.520> let's<00:18:35.760> not<00:18:36.000> just 00:18:36.169 --> 00:18:36.179 align:start position:0% more broadly though right let's not just 00:18:36.179 --> 00:18:38.029 align:start position:0% more broadly though right let's not just think<00:18:36.360> about<00:18:36.480> payments<00:18:37.080> what<00:18:37.620> else<00:18:37.740> could<00:18:37.919> you 00:18:38.029 --> 00:18:38.039 align:start position:0% think about payments what else could you 00:18:38.039 --> 00:18:39.830 align:start position:0% think about payments what else could you do<00:18:38.160> what<00:18:38.460> could<00:18:38.640> you<00:18:38.760> possibly<00:18:39.120> want<00:18:39.360> to<00:18:39.480> prove 00:18:39.830 --> 00:18:39.840 align:start position:0% do what could you possibly want to prove 00:18:39.840 --> 00:18:41.210 align:start position:0% do what could you possibly want to prove to<00:18:40.380> somebody 00:18:41.210 --> 00:18:41.220 align:start position:0% to somebody 00:18:41.220 --> 00:18:43.010 align:start position:0% to somebody well<00:18:41.820> we're<00:18:42.360> all<00:18:42.539> trying<00:18:42.780> to<00:18:42.840> build 00:18:43.010 --> 00:18:43.020 align:start position:0% well we're all trying to build 00:18:43.020 --> 00:18:45.230 align:start position:0% well we're all trying to build decentralized<00:18:43.620> ecosystems<00:18:44.340> right<00:18:44.820> there's<00:18:45.120> a 00:18:45.230 --> 00:18:45.240 align:start position:0% decentralized ecosystems right there's a 00:18:45.240 --> 00:18:46.370 align:start position:0% decentralized ecosystems right there's a whole<00:18:45.360> question<00:18:45.600> of<00:18:45.840> whether<00:18:45.960> those<00:18:46.200> are 00:18:46.370 --> 00:18:46.380 align:start position:0% whole question of whether those are 00:18:46.380 --> 00:18:47.570 align:start position:0% whole question of whether those are really<00:18:46.500> going<00:18:46.620> to<00:18:46.679> be<00:18:46.740> on<00:18:46.860> a<00:18:46.980> blockchain<00:18:47.280> or<00:18:47.460> is 00:18:47.570 --> 00:18:47.580 align:start position:0% really going to be on a blockchain or is 00:18:47.580 --> 00:18:49.130 align:start position:0% really going to be on a blockchain or is it<00:18:47.700> going<00:18:47.760> to<00:18:47.820> be<00:18:47.880> some<00:18:48.059> oligopoly<00:18:48.660> of<00:18:48.840> servers 00:18:49.130 --> 00:18:49.140 align:start position:0% it going to be some oligopoly of servers 00:18:49.140 --> 00:18:50.510 align:start position:0% it going to be some oligopoly of servers where<00:18:49.320> people<00:18:49.440> try<00:18:49.679> to<00:18:49.799> move<00:18:49.860> from<00:18:50.039> one<00:18:50.220> server 00:18:50.510 --> 00:18:50.520 align:start position:0% where people try to move from one server 00:18:50.520 --> 00:18:52.610 align:start position:0% where people try to move from one server to<00:18:50.580> another<00:18:50.760> to<00:18:51.059> another<00:18:51.200> migrate<00:18:52.200> their<00:18:52.320> data 00:18:52.610 --> 00:18:52.620 align:start position:0% to another to another migrate their data 00:18:52.620 --> 00:18:54.409 align:start position:0% to another to another migrate their data from<00:18:52.740> one<00:18:52.919> thing<00:18:53.039> to<00:18:53.160> another<00:18:53.340> and<00:18:54.120> in<00:18:54.299> those 00:18:54.409 --> 00:18:54.419 align:start position:0% from one thing to another and in those 00:18:54.419 --> 00:18:55.549 align:start position:0% from one thing to another and in those settings<00:18:54.600> it<00:18:54.960> would<00:18:55.080> probably<00:18:55.200> be<00:18:55.380> pretty 00:18:55.549 --> 00:18:55.559 align:start position:0% settings it would probably be pretty 00:18:55.559 --> 00:18:56.990 align:start position:0% settings it would probably be pretty useful<00:18:55.860> if<00:18:55.980> when<00:18:56.160> you<00:18:56.220> took<00:18:56.400> your<00:18:56.520> data<00:18:56.820> from 00:18:56.990 --> 00:18:57.000 align:start position:0% useful if when you took your data from 00:18:57.000 --> 00:18:59.210 align:start position:0% useful if when you took your data from server<00:18:57.299> a<00:18:57.480> to<00:18:57.660> server<00:18:57.900> B<00:18:58.080> you<00:18:58.799> sort<00:18:58.919> of<00:18:59.039> said 00:18:59.210 --> 00:18:59.220 align:start position:0% server a to server B you sort of said 00:18:59.220 --> 00:19:01.250 align:start position:0% server a to server B you sort of said that<00:19:00.059> here<00:19:00.480> I<00:19:00.660> can<00:19:00.780> prove<00:19:00.900> to<00:19:01.020> you<00:19:01.140> it's 00:19:01.250 --> 00:19:01.260 align:start position:0% that here I can prove to you it's 00:19:01.260 --> 00:19:02.270 align:start position:0% that here I can prove to you it's correct 00:19:02.270 --> 00:19:02.280 align:start position:0% correct 00:19:02.280 --> 00:19:04.250 align:start position:0% correct all<00:19:02.640> right<00:19:02.760> similarly<00:19:03.299> speaking<00:19:03.900> you<00:19:04.140> might 00:19:04.250 --> 00:19:04.260 align:start position:0% all right similarly speaking you might 00:19:04.260 --> 00:19:05.510 align:start position:0% all right similarly speaking you might want<00:19:04.380> to<00:19:04.559> prove<00:19:04.740> that<00:19:04.860> an<00:19:05.039> auction<00:19:05.220> you're 00:19:05.510 --> 00:19:05.520 align:start position:0% want to prove that an auction you're 00:19:05.520 --> 00:19:07.730 align:start position:0% want to prove that an auction you're doing<00:19:05.760> is<00:19:06.299> not<00:19:06.419> tampered<00:19:06.900> with<00:19:07.020> Google 00:19:07.730 --> 00:19:07.740 align:start position:0% doing is not tampered with Google 00:19:07.740 --> 00:19:08.990 align:start position:0% doing is not tampered with Google recently<00:19:08.280> got<00:19:08.400> in<00:19:08.580> trouble<00:19:08.700> because 00:19:08.990 --> 00:19:09.000 align:start position:0% recently got in trouble because 00:19:09.000 --> 00:19:10.490 align:start position:0% recently got in trouble because allegedly<00:19:09.600> according<00:19:09.960> to<00:19:10.020> several<00:19:10.380> States 00:19:10.490 --> 00:19:10.500 align:start position:0% allegedly according to several States 00:19:10.500 --> 00:19:12.950 align:start position:0% allegedly according to several States Attorney<00:19:10.740> General<00:19:11.240> they<00:19:12.240> will<00:19:12.419> manipulating 00:19:12.950 --> 00:19:12.960 align:start position:0% Attorney General they will manipulating 00:19:12.960 --> 00:19:15.049 align:start position:0% Attorney General they will manipulating their<00:19:13.200> ad<00:19:13.320> auctions<00:19:13.860> instead<00:19:14.520> of<00:19:14.580> running<00:19:14.760> a 00:19:15.049 --> 00:19:15.059 align:start position:0% their ad auctions instead of running a 00:19:15.059 --> 00:19:16.190 align:start position:0% their ad auctions instead of running a they<00:19:15.299> said<00:19:15.480> they<00:19:15.600> were<00:19:15.720> running<00:19:15.840> a<00:19:16.020> second 00:19:16.190 --> 00:19:16.200 align:start position:0% they said they were running a second 00:19:16.200 --> 00:19:18.710 align:start position:0% they said they were running a second price<00:19:16.440> sealed<00:19:16.799> bid<00:19:17.039> auction<00:19:17.340> where<00:19:18.299> if<00:19:18.600> you 00:19:18.710 --> 00:19:18.720 align:start position:0% price sealed bid auction where if you 00:19:18.720 --> 00:19:20.270 align:start position:0% price sealed bid auction where if you win<00:19:18.840> you<00:19:19.080> pay<00:19:19.200> with<00:19:19.380> the<00:19:19.559> second<00:19:19.679> price<00:19:19.919> is<00:19:20.100> and 00:19:20.270 --> 00:19:20.280 align:start position:0% win you pay with the second price is and 00:19:20.280 --> 00:19:22.130 align:start position:0% win you pay with the second price is and so<00:19:20.400> you<00:19:20.520> should<00:19:20.640> bid<00:19:20.820> your<00:19:20.940> value<00:19:21.179> and<00:19:21.720> instead 00:19:22.130 --> 00:19:22.140 align:start position:0% so you should bid your value and instead 00:19:22.140 --> 00:19:23.510 align:start position:0% so you should bid your value and instead they<00:19:22.380> were<00:19:22.559> running<00:19:22.740> something<00:19:23.100> that<00:19:23.340> was 00:19:23.510 --> 00:19:23.520 align:start position:0% they were running something that was 00:19:23.520 --> 00:19:25.130 align:start position:0% they were running something that was approximately<00:19:23.940> a<00:19:24.240> first<00:19:24.419> price<00:19:24.660> seal<00:19:24.960> bit 00:19:25.130 --> 00:19:25.140 align:start position:0% approximately a first price seal bit 00:19:25.140 --> 00:19:27.289 align:start position:0% approximately a first price seal bit auction<00:19:25.380> because<00:19:25.620> if<00:19:25.799> you<00:19:25.980> won<00:19:26.160> they<00:19:26.880> lied<00:19:27.179> and 00:19:27.289 --> 00:19:27.299 align:start position:0% auction because if you won they lied and 00:19:27.299 --> 00:19:28.549 align:start position:0% auction because if you won they lied and said<00:19:27.419> there<00:19:27.539> was<00:19:27.660> a<00:19:27.780> bid<00:19:27.840> right<00:19:28.140> right 00:19:28.549 --> 00:19:28.559 align:start position:0% said there was a bid right right 00:19:28.559 --> 00:19:30.590 align:start position:0% said there was a bid right right underwear<00:19:29.160> yours<00:19:29.580> wasn't<00:19:29.760> basically<00:19:30.179> charged 00:19:30.590 --> 00:19:30.600 align:start position:0% underwear yours wasn't basically charged 00:19:30.600 --> 00:19:31.490 align:start position:0% underwear yours wasn't basically charged you 00:19:31.490 --> 00:19:31.500 align:start position:0% you 00:19:31.500 --> 00:19:34.250 align:start position:0% you what<00:19:32.039> you<00:19:32.160> were<00:19:32.280> willing<00:19:32.520> to<00:19:32.640> pay<00:19:32.840> uh<00:19:33.840> and<00:19:34.140> this 00:19:34.250 --> 00:19:34.260 align:start position:0% what you were willing to pay uh and this 00:19:34.260 --> 00:19:36.230 align:start position:0% what you were willing to pay uh and this is<00:19:34.380> a<00:19:34.500> problem<00:19:34.679> with<00:19:35.039> Google<00:19:35.340> you<00:19:35.940> know<00:19:36.059> a 00:19:36.230 --> 00:19:36.240 align:start position:0% is a problem with Google you know a 00:19:36.240 --> 00:19:38.570 align:start position:0% is a problem with Google you know a semi-trusted<00:19:37.140> guy<00:19:37.740> in<00:19:38.039> a<00:19:38.160> legal<00:19:38.340> setting 00:19:38.570 --> 00:19:38.580 align:start position:0% semi-trusted guy in a legal setting 00:19:38.580 --> 00:19:39.890 align:start position:0% semi-trusted guy in a legal setting where<00:19:38.700> there<00:19:38.820> are<00:19:38.940> places<00:19:39.120> to<00:19:39.299> prosecute<00:19:39.720> them 00:19:39.890 --> 00:19:39.900 align:start position:0% where there are places to prosecute them 00:19:39.900 --> 00:19:41.630 align:start position:0% where there are places to prosecute them if<00:19:40.140> you<00:19:40.260> try<00:19:40.380> to<00:19:40.500> run<00:19:40.679> an<00:19:40.860> auction<00:19:41.039> on<00:19:41.400> you<00:19:41.580> know 00:19:41.630 --> 00:19:41.640 align:start position:0% if you try to run an auction on you know 00:19:41.640 --> 00:19:43.970 align:start position:0% if you try to run an auction on you know decentralized<00:19:42.179> wild<00:19:42.480> west<00:19:42.840> of<00:19:43.080> blockchains 00:19:43.970 --> 00:19:43.980 align:start position:0% decentralized wild west of blockchains 00:19:43.980 --> 00:19:45.830 align:start position:0% decentralized wild west of blockchains this<00:19:44.640> is<00:19:44.700> going<00:19:44.880> to<00:19:44.940> come<00:19:45.059> up<00:19:45.179> so<00:19:45.480> you<00:19:45.660> probably 00:19:45.830 --> 00:19:45.840 align:start position:0% this is going to come up so you probably 00:19:45.840 --> 00:19:46.909 align:start position:0% this is going to come up so you probably want<00:19:46.020> to<00:19:46.140> be<00:19:46.200> able<00:19:46.260> to<00:19:46.320> prove<00:19:46.559> your<00:19:46.679> options 00:19:46.909 --> 00:19:46.919 align:start position:0% want to be able to prove your options 00:19:46.919 --> 00:19:48.890 align:start position:0% want to be able to prove your options are<00:19:47.160> correct<00:19:47.419> similarly<00:19:48.419> you<00:19:48.600> might<00:19:48.660> want<00:19:48.780> to 00:19:48.890 --> 00:19:48.900 align:start position:0% are correct similarly you might want to 00:19:48.900 --> 00:19:50.330 align:start position:0% are correct similarly you might want to run<00:19:48.960> a<00:19:49.200> matching<00:19:49.440> rocket<00:19:49.679> for<00:19:49.799> some<00:19:49.980> Rideshare 00:19:50.330 --> 00:19:50.340 align:start position:0% run a matching rocket for some Rideshare 00:19:50.340 --> 00:19:52.010 align:start position:0% run a matching rocket for some Rideshare system<00:19:50.520> like<00:19:50.760> uber<00:19:51.059> you<00:19:51.299> can<00:19:51.419> do<00:19:51.539> this<00:19:51.660> with<00:19:51.840> a 00:19:52.010 --> 00:19:52.020 align:start position:0% system like uber you can do this with a 00:19:52.020 --> 00:19:54.289 align:start position:0% system like uber you can do this with a zero<00:19:52.260> knowledge<00:19:52.500> proof<00:19:52.860> in<00:19:53.400> theory<00:19:53.760> right 00:19:54.289 --> 00:19:54.299 align:start position:0% zero knowledge proof in theory right 00:19:54.299 --> 00:19:55.909 align:start position:0% zero knowledge proof in theory right thinking<00:19:54.780> even<00:19:54.900> more<00:19:55.140> broadly<00:19:55.500> you<00:19:55.799> might 00:19:55.909 --> 00:19:55.919 align:start position:0% thinking even more broadly you might 00:19:55.919 --> 00:19:57.350 align:start position:0% thinking even more broadly you might want<00:19:56.039> to<00:19:56.220> be<00:19:56.280> able<00:19:56.400> to<00:19:56.580> say<00:19:56.700> like<00:19:56.880> hey<00:19:57.059> if<00:19:57.240> we're 00:19:57.350 --> 00:19:57.360 align:start position:0% want to be able to say like hey if we're 00:19:57.360 --> 00:19:58.730 align:start position:0% want to be able to say like hey if we're running<00:19:57.539> a<00:19:57.720> decentralized<00:19:58.140> social<00:19:58.380> media 00:19:58.730 --> 00:19:58.740 align:start position:0% running a decentralized social media 00:19:58.740 --> 00:20:00.650 align:start position:0% running a decentralized social media system<00:19:58.919> I<00:19:59.520> have<00:19:59.640> a<00:19:59.760> news<00:19:59.880> feed<00:20:00.059> I'd<00:20:00.419> like<00:20:00.539> to 00:20:00.650 --> 00:20:00.660 align:start position:0% system I have a news feed I'd like to 00:20:00.660 --> 00:20:01.610 align:start position:0% system I have a news feed I'd like to know<00:20:00.720> that<00:20:00.900> my<00:20:01.080> news<00:20:01.140> feed<00:20:01.320> wasn't 00:20:01.610 --> 00:20:01.620 align:start position:0% know that my news feed wasn't 00:20:01.620 --> 00:20:03.529 align:start position:0% know that my news feed wasn't manipulated<00:20:02.220> that<00:20:02.820> somebody<00:20:03.059> isn't<00:20:03.419> for 00:20:03.529 --> 00:20:03.539 align:start position:0% manipulated that somebody isn't for 00:20:03.539 --> 00:20:05.029 align:start position:0% manipulated that somebody isn't for example<00:20:03.780> feeding<00:20:04.200> the<00:20:04.320> outrageous<00:20:04.799> stuff 00:20:05.029 --> 00:20:05.039 align:start position:0% example feeding the outrageous stuff 00:20:05.039 --> 00:20:07.850 align:start position:0% example feeding the outrageous stuff just<00:20:05.340> because<00:20:05.520> it<00:20:05.760> generates<00:20:06.059> clicks<00:20:06.559> uh<00:20:07.559> oh 00:20:07.850 --> 00:20:07.860 align:start position:0% just because it generates clicks uh oh 00:20:07.860 --> 00:20:10.010 align:start position:0% just because it generates clicks uh oh you<00:20:08.039> know<00:20:08.160> making<00:20:08.760> clickbait<00:20:09.360> titles<00:20:09.660> for<00:20:09.840> you 00:20:10.010 --> 00:20:10.020 align:start position:0% you know making clickbait titles for you 00:20:10.020 --> 00:20:13.669 align:start position:0% you know making clickbait titles for you know<00:20:10.080> ethereum<00:20:10.559> Devcon<00:20:11.160> talks<00:20:11.580> uh<00:20:12.960> you<00:20:13.559> might 00:20:13.669 --> 00:20:13.679 align:start position:0% know ethereum Devcon talks uh you might 00:20:13.679 --> 00:20:15.230 align:start position:0% know ethereum Devcon talks uh you might want<00:20:13.799> zero<00:20:14.160> knowledge<00:20:14.340> proof<00:20:14.580> to<00:20:14.760> do<00:20:14.880> that<00:20:15.000> and 00:20:15.230 --> 00:20:15.240 align:start position:0% want zero knowledge proof to do that and 00:20:15.240 --> 00:20:16.730 align:start position:0% want zero knowledge proof to do that and the<00:20:15.419> thing<00:20:15.480> here<00:20:15.720> is<00:20:15.840> these<00:20:16.200> are<00:20:16.320> all<00:20:16.440> sort<00:20:16.679> of 00:20:16.730 --> 00:20:16.740 align:start position:0% the thing here is these are all sort of 00:20:16.740 --> 00:20:18.350 align:start position:0% the thing here is these are all sort of Pie<00:20:16.980> in<00:20:17.160> the<00:20:17.280> Sky<00:20:17.400> dreams<00:20:17.820> but<00:20:18.059> we're<00:20:18.120> going<00:20:18.240> to 00:20:18.350 --> 00:20:18.360 align:start position:0% Pie in the Sky dreams but we're going to 00:20:18.360 --> 00:20:19.730 align:start position:0% Pie in the Sky dreams but we're going to need<00:20:18.480> to<00:20:18.600> do<00:20:18.720> things<00:20:18.900> like<00:20:19.140> this<00:20:19.260> because<00:20:19.559> if 00:20:19.730 --> 00:20:19.740 align:start position:0% need to do things like this because if 00:20:19.740 --> 00:20:21.110 align:start position:0% need to do things like this because if you're<00:20:19.860> trying<00:20:20.039> to<00:20:20.160> decentralize<00:20:20.640> existing 00:20:21.110 --> 00:20:21.120 align:start position:0% you're trying to decentralize existing 00:20:21.120 --> 00:20:24.049 align:start position:0% you're trying to decentralize existing Services<00:20:21.500> organizations<00:20:22.500> and<00:20:22.799> institutions 00:20:24.049 --> 00:20:24.059 align:start position:0% Services organizations and institutions 00:20:24.059 --> 00:20:26.150 align:start position:0% Services organizations and institutions it's<00:20:24.299> kind<00:20:24.480> of<00:20:24.539> essential<00:20:24.900> because<00:20:25.320> people 00:20:26.150 --> 00:20:26.160 align:start position:0% it's kind of essential because people 00:20:26.160 --> 00:20:28.070 align:start position:0% it's kind of essential because people kind<00:20:26.460> of<00:20:26.580> trust<00:20:26.880> these<00:20:27.240> essential<00:20:27.720> existing 00:20:28.070 --> 00:20:28.080 align:start position:0% kind of trust these essential existing 00:20:28.080 --> 00:20:29.510 align:start position:0% kind of trust these essential existing things<00:20:28.200> for<00:20:28.440> better<00:20:28.620> or<00:20:28.799> worse<00:20:29.039> and<00:20:29.220> so<00:20:29.340> if<00:20:29.400> you 00:20:29.510 --> 00:20:29.520 align:start position:0% things for better or worse and so if you 00:20:29.520 --> 00:20:30.590 align:start position:0% things for better or worse and so if you move<00:20:29.640> to<00:20:29.820> something<00:20:30.000> that's<00:20:30.240> completely 00:20:30.590 --> 00:20:30.600 align:start position:0% move to something that's completely 00:20:30.600 --> 00:20:32.270 align:start position:0% move to something that's completely crazy<00:20:30.780> and<00:20:31.080> new<00:20:31.260> you're<00:20:31.860> going<00:20:32.039> to<00:20:32.039> need<00:20:32.220> to 00:20:32.270 --> 00:20:32.280 align:start position:0% crazy and new you're going to need to 00:20:32.280 --> 00:20:34.190 align:start position:0% crazy and new you're going to need to convince<00:20:32.580> those<00:20:32.880> people<00:20:33.179> to<00:20:33.480> trust<00:20:33.720> your<00:20:34.020> new 00:20:34.190 --> 00:20:34.200 align:start position:0% convince those people to trust your new 00:20:34.200 --> 00:20:35.750 align:start position:0% convince those people to trust your new thing<00:20:34.440> and<00:20:34.919> you<00:20:35.100> can't<00:20:35.220> just<00:20:35.400> publish 00:20:35.750 --> 00:20:35.760 align:start position:0% thing and you can't just publish 00:20:35.760 --> 00:20:36.890 align:start position:0% thing and you can't just publish everything<00:20:35.940> that's<00:20:36.240> not<00:20:36.419> how<00:20:36.660> the<00:20:36.780> world 00:20:36.890 --> 00:20:36.900 align:start position:0% everything that's not how the world 00:20:36.900 --> 00:20:38.330 align:start position:0% everything that's not how the world Works 00:20:38.330 --> 00:20:38.340 align:start position:0% Works 00:20:38.340 --> 00:20:40.850 align:start position:0% Works um<00:20:38.760> so<00:20:39.600> this<00:20:40.080> is<00:20:40.200> sort<00:20:40.380> of<00:20:40.440> hard<00:20:40.620> to<00:20:40.799> think 00:20:40.850 --> 00:20:40.860 align:start position:0% um so this is sort of hard to think 00:20:40.860 --> 00:20:42.950 align:start position:0% um so this is sort of hard to think about<00:20:41.039> as<00:20:41.280> a<00:20:41.460> concrete<00:20:41.820> thing<00:20:41.940> so<00:20:42.360> he<00:20:42.660> was<00:20:42.840> a 00:20:42.950 --> 00:20:42.960 align:start position:0% about as a concrete thing so he was a 00:20:42.960 --> 00:20:45.409 align:start position:0% about as a concrete thing so he was a you<00:20:43.200> know<00:20:43.260> a<00:20:43.500> concrete<00:20:44.160> version<00:20:44.280> of<00:20:44.580> this 00:20:45.409 --> 00:20:45.419 align:start position:0% you know a concrete version of this 00:20:45.419 --> 00:20:47.210 align:start position:0% you know a concrete version of this standard<00:20:46.080> tale<00:20:46.260> about<00:20:46.500> internet<00:20:46.740> gaming 00:20:47.210 --> 00:20:47.220 align:start position:0% standard tale about internet gaming 00:20:47.220 --> 00:20:49.190 align:start position:0% standard tale about internet gaming right<00:20:47.400> there's<00:20:47.700> some<00:20:47.940> awesome<00:20:48.120> game<00:20:48.480> it's<00:20:49.020> an 00:20:49.190 --> 00:20:49.200 align:start position:0% right there's some awesome game it's an 00:20:49.200 --> 00:20:50.510 align:start position:0% right there's some awesome game it's an online<00:20:49.440> game<00:20:49.679> there's<00:20:49.860> a<00:20:49.980> server<00:20:50.220> there's<00:20:50.400> a 00:20:50.510 --> 00:20:50.520 align:start position:0% online game there's a server there's a 00:20:50.520 --> 00:20:51.710 align:start position:0% online game there's a server there's a great<00:20:50.640> Community<00:20:50.760> everybody<00:20:51.179> loves<00:20:51.600> the 00:20:51.710 --> 00:20:51.720 align:start position:0% great Community everybody loves the 00:20:51.720 --> 00:20:53.450 align:start position:0% great Community everybody loves the thing<00:20:52.380> and<00:20:52.679> then<00:20:52.799> it<00:20:52.919> gets<00:20:53.100> a<00:20:53.160> little<00:20:53.280> too 00:20:53.450 --> 00:20:53.460 align:start position:0% thing and then it gets a little too 00:20:53.460 --> 00:20:55.850 align:start position:0% thing and then it gets a little too popular<00:20:53.640> thing<00:20:54.360> goes<00:20:54.660> down<00:20:54.720> the<00:20:54.900> toilet<00:20:55.260> uh 00:20:55.850 --> 00:20:55.860 align:start position:0% popular thing goes down the toilet uh 00:20:55.860 --> 00:20:58.310 align:start position:0% popular thing goes down the toilet uh the<00:20:55.980> devs<00:20:56.280> get<00:20:56.400> greedy<00:20:56.940> or<00:20:57.660> bought<00:20:57.900> by<00:20:58.140> some 00:20:58.310 --> 00:20:58.320 align:start position:0% the devs get greedy or bought by some 00:20:58.320 --> 00:20:59.330 align:start position:0% the devs get greedy or bought by some company 00:20:59.330 --> 00:20:59.340 align:start position:0% company 00:20:59.340 --> 00:21:02.690 align:start position:0% company um<00:20:59.400> blizzard<00:21:00.000> uh<00:21:00.660> and<00:21:01.620> um<00:21:01.740> they<00:21:02.039> somehow<00:21:02.340> ruin 00:21:02.690 --> 00:21:02.700 align:start position:0% um blizzard uh and um they somehow ruin 00:21:02.700 --> 00:21:04.669 align:start position:0% um blizzard uh and um they somehow ruin the<00:21:02.940> game 00:21:04.669 --> 00:21:04.679 align:start position:0% the game 00:21:04.679 --> 00:21:07.010 align:start position:0% the game never<00:21:05.039> mind<00:21:05.280> how<00:21:05.580> uh<00:21:06.299> and<00:21:06.480> so<00:21:06.600> you<00:21:06.840> know<00:21:06.900> in 00:21:07.010 --> 00:21:07.020 align:start position:0% never mind how uh and so you know in 00:21:07.020 --> 00:21:09.110 align:start position:0% never mind how uh and so you know in classic<00:21:07.260> Futurama<00:21:07.799> binder<00:21:08.460> we're<00:21:08.880> going<00:21:09.000> to 00:21:09.110 --> 00:21:09.120 align:start position:0% classic Futurama binder we're going to 00:21:09.120 --> 00:21:10.970 align:start position:0% classic Futurama binder we're going to make<00:21:09.179> our<00:21:09.299> own<00:21:09.480> with<00:21:09.660> better<00:21:09.900> things 00:21:10.970 --> 00:21:10.980 align:start position:0% make our own with better things 00:21:10.980 --> 00:21:12.470 align:start position:0% make our own with better things um<00:21:11.039> what<00:21:11.280> you<00:21:11.460> want<00:21:11.580> to<00:21:11.700> do<00:21:11.760> is<00:21:11.940> like<00:21:12.120> take<00:21:12.299> all 00:21:12.470 --> 00:21:12.480 align:start position:0% um what you want to do is like take all 00:21:12.480 --> 00:21:14.930 align:start position:0% um what you want to do is like take all your<00:21:12.660> data<00:21:13.020> and<00:21:13.740> go<00:21:13.860> to<00:21:13.980> a<00:21:14.160> new<00:21:14.280> server<00:21:14.580> with 00:21:14.930 --> 00:21:14.940 align:start position:0% your data and go to a new server with 00:21:14.940 --> 00:21:17.029 align:start position:0% your data and go to a new server with the<00:21:15.120> same<00:21:15.240> game<00:21:15.539> but<00:21:16.380> your<00:21:16.500> existing<00:21:16.919> game 00:21:17.029 --> 00:21:17.039 align:start position:0% the same game but your existing game 00:21:17.039 --> 00:21:18.049 align:start position:0% the same game but your existing game state 00:21:18.049 --> 00:21:18.059 align:start position:0% state 00:21:18.059 --> 00:21:19.669 align:start position:0% state and<00:21:18.600> you<00:21:18.780> know<00:21:18.900> for<00:21:19.020> this<00:21:19.140> to<00:21:19.320> work<00:21:19.380> the<00:21:19.559> game 00:21:19.669 --> 00:21:19.679 align:start position:0% and you know for this to work the game 00:21:19.679 --> 00:21:21.289 align:start position:0% and you know for this to work the game has<00:21:19.799> to<00:21:19.919> be<00:21:19.980> open<00:21:20.100> source<00:21:20.520> but<00:21:20.640> even<00:21:20.820> if<00:21:21.000> it<00:21:21.120> is 00:21:21.289 --> 00:21:21.299 align:start position:0% has to be open source but even if it is 00:21:21.299 --> 00:21:23.330 align:start position:0% has to be open source but even if it is you're<00:21:22.080> going<00:21:22.200> to<00:21:22.260> run<00:21:22.440> into<00:21:22.620> some<00:21:22.919> problems 00:21:23.330 --> 00:21:23.340 align:start position:0% you're going to run into some problems 00:21:23.340 --> 00:21:25.850 align:start position:0% you're going to run into some problems here<00:21:23.580> right<00:21:24.240> when<00:21:24.600> you<00:21:24.840> take<00:21:25.020> that<00:21:25.260> level<00:21:25.440> 50 00:21:25.850 --> 00:21:25.860 align:start position:0% here right when you take that level 50 00:21:25.860 --> 00:21:28.190 align:start position:0% here right when you take that level 50 sword<00:21:26.280> or<00:21:26.460> whatever<00:21:26.640> it<00:21:26.940> is<00:21:27.059> from<00:21:27.539> server<00:21:27.900> a<00:21:28.020> to 00:21:28.190 --> 00:21:28.200 align:start position:0% sword or whatever it is from server a to 00:21:28.200 --> 00:21:30.529 align:start position:0% sword or whatever it is from server a to server<00:21:28.440> B<00:21:28.620> why<00:21:29.520> is<00:21:29.640> anyone<00:21:29.940> going<00:21:30.179> to<00:21:30.299> believe 00:21:30.529 --> 00:21:30.539 align:start position:0% server B why is anyone going to believe 00:21:30.539 --> 00:21:32.149 align:start position:0% server B why is anyone going to believe that<00:21:31.020> you<00:21:31.200> actually<00:21:31.320> earned<00:21:31.740> that<00:21:31.799> that<00:21:31.980> you 00:21:32.149 --> 00:21:32.159 align:start position:0% that you actually earned that that you 00:21:32.159 --> 00:21:34.730 align:start position:0% that you actually earned that that you didn't<00:21:32.220> just<00:21:32.400> make<00:21:32.520> it<00:21:32.640> up<00:21:32.820> right<00:21:33.600> for<00:21:34.559> the 00:21:34.730 --> 00:21:34.740 align:start position:0% didn't just make it up right for the 00:21:34.740 --> 00:21:36.230 align:start position:0% didn't just make it up right for the server<00:21:35.039> how<00:21:35.580> are<00:21:35.700> we<00:21:35.820> going<00:21:35.940> to<00:21:36.000> know<00:21:36.120> that 00:21:36.230 --> 00:21:36.240 align:start position:0% server how are we going to know that 00:21:36.240 --> 00:21:37.370 align:start position:0% server how are we going to know that they<00:21:36.360> weren't<00:21:36.539> playing<00:21:36.720> funny<00:21:36.900> business<00:21:37.140> I'm 00:21:37.370 --> 00:21:37.380 align:start position:0% they weren't playing funny business I'm 00:21:37.380 --> 00:21:38.750 align:start position:0% they weren't playing funny business I'm secretly<00:21:37.799> running<00:21:37.919> a<00:21:38.100> pay-to-play<00:21:38.520> game 00:21:38.750 --> 00:21:38.760 align:start position:0% secretly running a pay-to-play game 00:21:38.760 --> 00:21:40.070 align:start position:0% secretly running a pay-to-play game right<00:21:39.179> how<00:21:39.360> are<00:21:39.480> you<00:21:39.539> going<00:21:39.600> to<00:21:39.720> know<00:21:39.840> that<00:21:39.960> the 00:21:40.070 --> 00:21:40.080 align:start position:0% right how are you going to know that the 00:21:40.080 --> 00:21:41.390 align:start position:0% right how are you going to know that the economy<00:21:40.440> of<00:21:40.620> that<00:21:40.740> server<00:21:40.919> and<00:21:41.039> the<00:21:41.159> way<00:21:41.280> the 00:21:41.390 --> 00:21:41.400 align:start position:0% economy of that server and the way the 00:21:41.400 --> 00:21:43.430 align:start position:0% economy of that server and the way the items<00:21:41.640> are<00:21:41.700> distributed<00:21:42.120> is<00:21:42.360> correct 00:21:43.430 --> 00:21:43.440 align:start position:0% items are distributed is correct 00:21:43.440 --> 00:21:45.230 align:start position:0% items are distributed is correct right<00:21:43.980> you<00:21:44.340> want<00:21:44.460> to<00:21:44.580> be<00:21:44.700> able<00:21:44.760> to<00:21:44.940> prevent 00:21:45.230 --> 00:21:45.240 align:start position:0% right you want to be able to prevent 00:21:45.240 --> 00:21:47.690 align:start position:0% right you want to be able to prevent these<00:21:45.539> guys<00:21:45.659> from<00:21:45.960> like<00:21:46.260> toileting<00:21:47.220> this<00:21:47.520> game 00:21:47.690 --> 00:21:47.700 align:start position:0% these guys from like toileting this game 00:21:47.700 --> 00:21:48.770 align:start position:0% these guys from like toileting this game you<00:21:47.880> want<00:21:48.000> to<00:21:48.120> be<00:21:48.179> able<00:21:48.240> to<00:21:48.360> move<00:21:48.480> to<00:21:48.600> another 00:21:48.770 --> 00:21:48.780 align:start position:0% you want to be able to move to another 00:21:48.780 --> 00:21:50.570 align:start position:0% you want to be able to move to another server<00:21:49.200> but<00:21:49.559> you<00:21:49.740> need<00:21:49.860> all<00:21:50.039> of<00:21:50.159> your<00:21:50.220> data<00:21:50.520> to 00:21:50.570 --> 00:21:50.580 align:start position:0% server but you need all of your data to 00:21:50.580 --> 00:21:51.950 align:start position:0% server but you need all of your data to be<00:21:50.700> credible<00:21:50.940> when<00:21:51.179> you<00:21:51.299> do<00:21:51.419> this<00:21:51.539> and<00:21:51.659> move<00:21:51.840> it 00:21:51.950 --> 00:21:51.960 align:start position:0% be credible when you do this and move it 00:21:51.960 --> 00:21:53.450 align:start position:0% be credible when you do this and move it around<00:21:52.140> and<00:21:52.679> so<00:21:52.799> the<00:21:52.919> only<00:21:53.039> way<00:21:53.159> you're<00:21:53.280> going 00:21:53.450 --> 00:21:53.460 align:start position:0% around and so the only way you're going 00:21:53.460 --> 00:21:55.430 align:start position:0% around and so the only way you're going to do<00:21:53.580> this<00:21:53.700> is<00:21:54.059> by<00:21:54.419> committing<00:21:55.020> to<00:21:55.140> the<00:21:55.200> data 00:21:55.430 --> 00:21:55.440 align:start position:0% to do this is by committing to the data 00:21:55.440 --> 00:21:56.990 align:start position:0% to do this is by committing to the data on<00:21:55.559> a<00:21:55.679> blockchain<00:21:55.980> and<00:21:56.340> attaching<00:21:56.700> zero 00:21:56.990 --> 00:21:57.000 align:start position:0% on a blockchain and attaching zero 00:21:57.000 --> 00:21:58.850 align:start position:0% on a blockchain and attaching zero knowledge<00:21:57.240> proofs<00:21:57.600> to<00:21:57.659> all<00:21:57.780> this<00:21:57.960> stuff<00:21:58.200> again 00:21:58.850 --> 00:21:58.860 align:start position:0% knowledge proofs to all this stuff again 00:21:58.860 --> 00:22:00.770 align:start position:0% knowledge proofs to all this stuff again Pie<00:21:59.460> in<00:21:59.640> the<00:21:59.760> Sky<00:21:59.880> you<00:22:00.120> can't<00:22:00.240> get<00:22:00.419> this<00:22:00.600> to 00:22:00.770 --> 00:22:00.780 align:start position:0% Pie in the Sky you can't get this to 00:22:00.780 --> 00:22:02.750 align:start position:0% Pie in the Sky you can't get this to scale<00:22:00.960> now<00:22:01.260> but<00:22:01.679> it's<00:22:01.799> an<00:22:01.980> interesting<00:22:02.340> idea 00:22:02.750 --> 00:22:02.760 align:start position:0% scale now but it's an interesting idea 00:22:02.760 --> 00:22:04.970 align:start position:0% scale now but it's an interesting idea uh<00:22:03.539> and<00:22:03.659> this<00:22:03.780> approach<00:22:04.080> is<00:22:04.200> broadly<00:22:04.559> feasible 00:22:04.970 --> 00:22:04.980 align:start position:0% uh and this approach is broadly feasible 00:22:04.980 --> 00:22:07.010 align:start position:0% uh and this approach is broadly feasible to<00:22:05.159> not<00:22:05.280> just<00:22:05.460> gaming<00:22:05.940> you<00:22:06.659> don't<00:22:06.780> need<00:22:06.900> to 00:22:07.010 --> 00:22:07.020 align:start position:0% to not just gaming you don't need to 00:22:07.020 --> 00:22:08.510 align:start position:0% to not just gaming you don't need to just<00:22:07.140> do<00:22:07.320> this<00:22:07.500> about<00:22:07.620> a<00:22:07.860> sword<00:22:08.039> you<00:22:08.280> could<00:22:08.400> do 00:22:08.510 --> 00:22:08.520 align:start position:0% just do this about a sword you could do 00:22:08.520 --> 00:22:10.730 align:start position:0% just do this about a sword you could do this<00:22:08.640> about<00:22:08.820> any<00:22:09.120> number<00:22:09.360> of<00:22:09.539> things<00:22:10.080> right<00:22:10.559> if 00:22:10.730 --> 00:22:10.740 align:start position:0% this about any number of things right if 00:22:10.740 --> 00:22:12.169 align:start position:0% this about any number of things right if you're<00:22:10.860> running<00:22:11.039> a<00:22:11.280> crowdfronting<00:22:11.880> platform 00:22:12.169 --> 00:22:12.179 align:start position:0% you're running a crowdfronting platform 00:22:12.179 --> 00:22:13.669 align:start position:0% you're running a crowdfronting platform that<00:22:12.419> has<00:22:12.600> like<00:22:12.780> Awards<00:22:13.320> something<00:22:13.500> like 00:22:13.669 --> 00:22:13.679 align:start position:0% that has like Awards something like 00:22:13.679 --> 00:22:15.950 align:start position:0% that has like Awards something like patreon<00:22:14.159> patreon<00:22:14.880> goes<00:22:15.120> under<00:22:15.240> you<00:22:15.720> can<00:22:15.840> move 00:22:15.950 --> 00:22:15.960 align:start position:0% patreon patreon goes under you can move 00:22:15.960 --> 00:22:17.450 align:start position:0% patreon patreon goes under you can move to<00:22:16.140> another<00:22:16.320> server<00:22:16.679> and<00:22:16.919> take<00:22:17.039> the<00:22:17.159> awards 00:22:17.450 --> 00:22:17.460 align:start position:0% to another server and take the awards 00:22:17.460 --> 00:22:18.710 align:start position:0% to another server and take the awards you've<00:22:17.640> gotten<00:22:17.880> improve<00:22:18.179> you<00:22:18.299> actually<00:22:18.480> got 00:22:18.710 --> 00:22:18.720 align:start position:0% you've gotten improve you actually got 00:22:18.720 --> 00:22:19.970 align:start position:0% you've gotten improve you actually got them 00:22:19.970 --> 00:22:19.980 align:start position:0% them 00:22:19.980 --> 00:22:20.930 align:start position:0% them um 00:22:20.930 --> 00:22:20.940 align:start position:0% um 00:22:20.940 --> 00:22:23.029 align:start position:0% um so<00:22:21.539> okay<00:22:21.900> well<00:22:22.320> what<00:22:22.500> if<00:22:22.620> we<00:22:22.740> thought<00:22:22.799> even 00:22:23.029 --> 00:22:23.039 align:start position:0% so okay well what if we thought even 00:22:23.039 --> 00:22:24.049 align:start position:0% so okay well what if we thought even bigger 00:22:24.049 --> 00:22:24.059 align:start position:0% bigger 00:22:24.059 --> 00:22:25.250 align:start position:0% bigger um 00:22:25.250 --> 00:22:25.260 align:start position:0% um 00:22:25.260 --> 00:22:27.470 align:start position:0% um recently<00:22:25.740> there<00:22:25.919> was<00:22:26.039> a<00:22:26.159> headline<00:22:26.400> uh<00:22:27.120> that 00:22:27.470 --> 00:22:27.480 align:start position:0% recently there was a headline uh that 00:22:27.480 --> 00:22:29.090 align:start position:0% recently there was a headline uh that the<00:22:27.780> IRS<00:22:28.080> had<00:22:28.260> gotten<00:22:28.500> in<00:22:28.559> trouble<00:22:28.740> for 00:22:29.090 --> 00:22:29.100 align:start position:0% the IRS had gotten in trouble for 00:22:29.100 --> 00:22:31.850 align:start position:0% the IRS had gotten in trouble for manipulating<00:22:29.700> uh<00:22:30.419> their<00:22:30.720> audit<00:22:31.080> process<00:22:31.380> and 00:22:31.850 --> 00:22:31.860 align:start position:0% manipulating uh their audit process and 00:22:31.860 --> 00:22:33.409 align:start position:0% manipulating uh their audit process and under<00:22:31.980> the<00:22:32.220> Trump<00:22:32.340> Administration<00:22:32.880> auditing 00:22:33.409 --> 00:22:33.419 align:start position:0% under the Trump Administration auditing 00:22:33.419 --> 00:22:35.930 align:start position:0% under the Trump Administration auditing senior<00:22:33.840> FBI<00:22:34.200> officials<00:22:34.740> who<00:22:34.980> mysteriously 00:22:35.930 --> 00:22:35.940 align:start position:0% senior FBI officials who mysteriously 00:22:35.940 --> 00:22:37.130 align:start position:0% senior FBI officials who mysteriously had<00:22:36.059> also<00:22:36.299> been<00:22:36.419> investigating<00:22:36.780> the<00:22:36.960> Trump 00:22:37.130 --> 00:22:37.140 align:start position:0% had also been investigating the Trump 00:22:37.140 --> 00:22:38.630 align:start position:0% had also been investigating the Trump Administration<00:22:37.620> so<00:22:37.860> this<00:22:38.039> was<00:22:38.159> regardless 00:22:38.630 --> 00:22:38.640 align:start position:0% Administration so this was regardless 00:22:38.640 --> 00:22:41.450 align:start position:0% Administration so this was regardless than<00:22:39.000> tampering<00:22:39.419> with<00:22:39.539> those<00:22:39.780> other<00:22:40.320> stuff 00:22:41.450 --> 00:22:41.460 align:start position:0% than tampering with those other stuff 00:22:41.460 --> 00:22:44.210 align:start position:0% than tampering with those other stuff um<00:22:41.520> what<00:22:41.820> would<00:22:41.940> it<00:22:42.120> take<00:22:42.299> to<00:22:43.080> make<00:22:43.500> tax<00:22:43.860> audit 00:22:44.210 --> 00:22:44.220 align:start position:0% um what would it take to make tax audit 00:22:44.220 --> 00:22:45.590 align:start position:0% um what would it take to make tax audit processes<00:22:44.580> credible<00:22:45.000> and<00:22:45.120> this<00:22:45.299> is<00:22:45.360> just<00:22:45.480> sort 00:22:45.590 --> 00:22:45.600 align:start position:0% processes credible and this is just sort 00:22:45.600 --> 00:22:47.390 align:start position:0% processes credible and this is just sort of<00:22:45.720> a<00:22:45.840> hypothetical<00:22:46.260> right<00:22:46.740> how<00:22:47.100> would<00:22:47.280> you 00:22:47.390 --> 00:22:47.400 align:start position:0% of a hypothetical right how would you 00:22:47.400 --> 00:22:49.610 align:start position:0% of a hypothetical right how would you know<00:22:47.700> that<00:22:47.880> this<00:22:48.059> is<00:22:48.179> working<00:22:48.360> uh<00:22:49.140> you'd<00:22:49.500> have 00:22:49.610 --> 00:22:49.620 align:start position:0% know that this is working uh you'd have 00:22:49.620 --> 00:22:52.370 align:start position:0% know that this is working uh you'd have to<00:22:49.799> commit<00:22:50.580> to<00:22:51.179> an<00:22:51.539> audit<00:22:51.780> policy<00:22:52.080> in<00:22:52.200> advance 00:22:52.370 --> 00:22:52.380 align:start position:0% to commit to an audit policy in advance 00:22:52.380 --> 00:22:54.049 align:start position:0% to commit to an audit policy in advance you'd<00:22:52.980> have<00:22:53.100> to<00:22:53.159> put<00:22:53.280> up<00:22:53.400> all<00:22:53.700> of<00:22:53.760> the<00:22:53.880> tax 00:22:54.049 --> 00:22:54.059 align:start position:0% you'd have to put up all of the tax 00:22:54.059 --> 00:22:56.570 align:start position:0% you'd have to put up all of the tax returns<00:22:54.539> committed<00:22:55.020> on<00:22:55.320> in<00:22:55.559> some<00:22:55.860> blockchain 00:22:56.570 --> 00:22:56.580 align:start position:0% returns committed on in some blockchain 00:22:56.580 --> 00:22:58.250 align:start position:0% returns committed on in some blockchain and<00:22:56.760> permissioned<00:22:57.120> Ledger<00:22:57.419> and<00:22:58.020> then<00:22:58.140> you 00:22:58.250 --> 00:22:58.260 align:start position:0% and permissioned Ledger and then you 00:22:58.260 --> 00:22:59.630 align:start position:0% and permissioned Ledger and then you have<00:22:58.500> to<00:22:58.559> show<00:22:58.679> that<00:22:58.799> your<00:22:58.919> audit<00:22:59.220> process<00:22:59.460> was 00:22:59.630 --> 00:22:59.640 align:start position:0% have to show that your audit process was 00:22:59.640 --> 00:23:02.029 align:start position:0% have to show that your audit process was applied<00:22:59.940> correctly<00:23:00.360> and<00:23:00.960> the<00:23:01.080> thing<00:23:01.260> is<00:23:01.380> in 00:23:02.029 --> 00:23:02.039 align:start position:0% applied correctly and the thing is in 00:23:02.039 --> 00:23:03.230 align:start position:0% applied correctly and the thing is in the<00:23:02.220> process<00:23:02.400> of<00:23:02.580> doing<00:23:02.700> this<00:23:02.820> you<00:23:03.000> cannot 00:23:03.230 --> 00:23:03.240 align:start position:0% the process of doing this you cannot 00:23:03.240 --> 00:23:05.330 align:start position:0% the process of doing this you cannot reveal<00:23:03.659> any<00:23:03.960> of<00:23:04.140> that<00:23:04.320> data<00:23:04.620> can't<00:23:05.159> tell 00:23:05.330 --> 00:23:05.340 align:start position:0% reveal any of that data can't tell 00:23:05.340 --> 00:23:06.770 align:start position:0% reveal any of that data can't tell people<00:23:05.520> what<00:23:05.760> will<00:23:05.880> get<00:23:06.059> your<00:23:06.179> taxes<00:23:06.480> out<00:23:06.600> of 00:23:06.770 --> 00:23:06.780 align:start position:0% people what will get your taxes out of 00:23:06.780 --> 00:23:08.029 align:start position:0% people what will get your taxes out of it<00:23:06.840> you<00:23:07.020> can't<00:23:07.200> tell<00:23:07.380> people<00:23:07.559> what<00:23:07.860> other 00:23:08.029 --> 00:23:08.039 align:start position:0% it you can't tell people what other 00:23:08.039 --> 00:23:09.890 align:start position:0% it you can't tell people what other people's<00:23:08.340> tax<00:23:08.520> returns<00:23:09.000> are<00:23:09.120> but<00:23:09.539> if<00:23:09.659> you<00:23:09.780> want 00:23:09.890 --> 00:23:09.900 align:start position:0% people's tax returns are but if you want 00:23:09.900 --> 00:23:11.270 align:start position:0% people's tax returns are but if you want everybody<00:23:10.080> to<00:23:10.380> know<00:23:10.559> and<00:23:10.740> trust<00:23:10.980> that<00:23:11.159> when 00:23:11.270 --> 00:23:11.280 align:start position:0% everybody to know and trust that when 00:23:11.280 --> 00:23:13.130 align:start position:0% everybody to know and trust that when they<00:23:11.460> get<00:23:11.580> audited<00:23:11.880> by<00:23:12.059> the<00:23:12.179> IRS<00:23:12.539> or<00:23:13.020> some 00:23:13.130 --> 00:23:13.140 align:start position:0% they get audited by the IRS or some 00:23:13.140 --> 00:23:14.630 align:start position:0% they get audited by the IRS or some other<00:23:13.320> institution<00:23:13.799> that<00:23:14.220> it<00:23:14.400> was<00:23:14.520> actually 00:23:14.630 --> 00:23:14.640 align:start position:0% other institution that it was actually 00:23:14.640 --> 00:23:16.130 align:start position:0% other institution that it was actually done<00:23:14.820> according<00:23:15.120> to<00:23:15.240> a<00:23:15.360> fixed<00:23:15.659> procedure<00:23:15.960> in 00:23:16.130 --> 00:23:16.140 align:start position:0% done according to a fixed procedure in 00:23:16.140 --> 00:23:18.350 align:start position:0% done according to a fixed procedure in the<00:23:16.260> rule<00:23:16.440> of<00:23:16.559> law<00:23:16.740> or<00:23:16.980> whatever<00:23:17.159> it<00:23:17.400> is<00:23:17.520> you're 00:23:18.350 --> 00:23:18.360 align:start position:0% the rule of law or whatever it is you're 00:23:18.360 --> 00:23:20.210 align:start position:0% the rule of law or whatever it is you're going<00:23:18.480> to<00:23:18.600> have<00:23:18.720> to<00:23:18.900> do<00:23:19.080> something<00:23:19.320> and<00:23:20.039> so 00:23:20.210 --> 00:23:20.220 align:start position:0% going to have to do something and so 00:23:20.220 --> 00:23:22.430 align:start position:0% going to have to do something and so maybe<00:23:20.640> again<00:23:21.480> hypothetically<00:23:22.080> if<00:23:22.260> you're<00:23:22.320> at 00:23:22.430 --> 00:23:22.440 align:start position:0% maybe again hypothetically if you're at 00:23:22.440 --> 00:23:23.810 align:start position:0% maybe again hypothetically if you're at a<00:23:22.559> zero<00:23:22.740> knowledge<00:23:22.980> proof<00:23:23.280> on<00:23:23.340> a<00:23:23.520> blockchain 00:23:23.810 --> 00:23:23.820 align:start position:0% a zero knowledge proof on a blockchain 00:23:23.820 --> 00:23:26.029 align:start position:0% a zero knowledge proof on a blockchain you<00:23:24.120> could<00:23:24.240> do<00:23:24.419> this 00:23:26.029 --> 00:23:26.039 align:start position:0% you could do this 00:23:26.039 --> 00:23:28.610 align:start position:0% you could do this um so<00:23:26.760> as<00:23:26.880> I<00:23:27.059> was<00:23:27.120> writing<00:23:27.419> this<00:23:27.539> talk<00:23:27.780> uh<00:23:28.500> I 00:23:28.610 --> 00:23:28.620 align:start position:0% um so as I was writing this talk uh I 00:23:28.620 --> 00:23:30.230 align:start position:0% um so as I was writing this talk uh I kept<00:23:28.860> thinking<00:23:29.100> of<00:23:29.220> this<00:23:29.400> idea<00:23:29.640> that<00:23:30.000> like 00:23:30.230 --> 00:23:30.240 align:start position:0% kept thinking of this idea that like 00:23:30.240 --> 00:23:33.169 align:start position:0% kept thinking of this idea that like verifiability<00:23:30.960> enables<00:23:31.559> uh<00:23:31.860> cooperation<00:23:32.400> so 00:23:33.169 --> 00:23:33.179 align:start position:0% verifiability enables uh cooperation so 00:23:33.179 --> 00:23:34.970 align:start position:0% verifiability enables uh cooperation so during<00:23:33.360> the<00:23:33.539> Cold<00:23:33.659> War<00:23:33.900> the<00:23:34.140> US<00:23:34.260> and<00:23:34.500> the<00:23:34.620> USSR 00:23:34.970 --> 00:23:34.980 align:start position:0% during the Cold War the US and the USSR 00:23:34.980 --> 00:23:37.070 align:start position:0% during the Cold War the US and the USSR wanted<00:23:35.280> to<00:23:35.580> disarm<00:23:36.360> somewhat<00:23:36.720> they<00:23:36.780> wanted<00:23:36.900> to 00:23:37.070 --> 00:23:37.080 align:start position:0% wanted to disarm somewhat they wanted to 00:23:37.080 --> 00:23:38.210 align:start position:0% wanted to disarm somewhat they wanted to have<00:23:37.200> less<00:23:37.320> nukes<00:23:37.679> because<00:23:37.799> they<00:23:37.980> could<00:23:38.100> save 00:23:38.210 --> 00:23:38.220 align:start position:0% have less nukes because they could save 00:23:38.220 --> 00:23:39.590 align:start position:0% have less nukes because they could save money<00:23:38.400> on<00:23:38.640> it<00:23:38.760> and<00:23:38.820> it<00:23:39.059> was<00:23:39.179> better<00:23:39.299> for<00:23:39.480> the 00:23:39.590 --> 00:23:39.600 align:start position:0% money on it and it was better for the 00:23:39.600 --> 00:23:40.490 align:start position:0% money on it and it was better for the planet 00:23:40.490 --> 00:23:40.500 align:start position:0% planet 00:23:40.500 --> 00:23:41.990 align:start position:0% planet um<00:23:40.559> but<00:23:40.740> there<00:23:40.919> was<00:23:41.039> this<00:23:41.159> problem<00:23:41.400> of<00:23:41.640> if<00:23:41.880> you 00:23:41.990 --> 00:23:42.000 align:start position:0% um but there was this problem of if you 00:23:42.000 --> 00:23:43.430 align:start position:0% um but there was this problem of if you the<00:23:42.240> U.S<00:23:42.419> gets<00:23:42.659> rid<00:23:42.780> of<00:23:42.900> their<00:23:42.960> nukes<00:23:43.320> they 00:23:43.430 --> 00:23:43.440 align:start position:0% the U.S gets rid of their nukes they 00:23:43.440 --> 00:23:44.810 align:start position:0% the U.S gets rid of their nukes they want<00:23:43.500> to<00:23:43.620> verify<00:23:43.919> the<00:23:44.159> Russians<00:23:44.460> are<00:23:44.520> also 00:23:44.810 --> 00:23:44.820 align:start position:0% want to verify the Russians are also 00:23:44.820 --> 00:23:46.970 align:start position:0% want to verify the Russians are also getting<00:23:44.880> aware<00:23:45.179> of<00:23:45.299> theirs<00:23:45.720> and<00:23:46.500> that<00:23:46.860> was 00:23:46.970 --> 00:23:46.980 align:start position:0% getting aware of theirs and that was 00:23:46.980 --> 00:23:48.770 align:start position:0% getting aware of theirs and that was kind<00:23:47.220> of<00:23:47.340> hard<00:23:47.580> so<00:23:47.940> one<00:23:48.120> of<00:23:48.240> the<00:23:48.360> limits<00:23:48.659> for 00:23:48.770 --> 00:23:48.780 align:start position:0% kind of hard so one of the limits for 00:23:48.780 --> 00:23:50.630 align:start position:0% kind of hard so one of the limits for arms<00:23:49.080> control<00:23:49.200> treaties<00:23:49.799> was<00:23:50.280> that<00:23:50.400> it<00:23:50.520> was 00:23:50.630 --> 00:23:50.640 align:start position:0% arms control treaties was that it was 00:23:50.640 --> 00:23:52.070 align:start position:0% arms control treaties was that it was hard<00:23:50.820> to<00:23:50.940> verify<00:23:51.240> what<00:23:51.419> was<00:23:51.539> going<00:23:51.720> on<00:23:51.840> and 00:23:52.070 --> 00:23:52.080 align:start position:0% hard to verify what was going on and 00:23:52.080 --> 00:23:53.930 align:start position:0% hard to verify what was going on and what<00:23:52.260> happened<00:23:52.440> was<00:23:52.679> as<00:23:52.980> spy<00:23:53.220> satellites<00:23:53.760> got 00:23:53.930 --> 00:23:53.940 align:start position:0% what happened was as spy satellites got 00:23:53.940 --> 00:23:55.430 align:start position:0% what happened was as spy satellites got better<00:23:54.059> and<00:23:54.360> then<00:23:54.480> spy<00:23:54.780> planes<00:23:55.080> got<00:23:55.260> better 00:23:55.430 --> 00:23:55.440 align:start position:0% better and then spy planes got better 00:23:55.440 --> 00:23:58.010 align:start position:0% better and then spy planes got better and<00:23:55.679> more<00:23:55.860> pervasive<00:23:56.480> the<00:23:57.480> Russians<00:23:57.780> in<00:23:57.900> the 00:23:58.010 --> 00:23:58.020 align:start position:0% and more pervasive the Russians in the 00:23:58.020 --> 00:24:00.110 align:start position:0% and more pervasive the Russians in the uh<00:23:58.260> and<00:23:58.500> the<00:23:58.620> US<00:23:58.799> were<00:23:59.159> capable<00:23:59.460> of<00:23:59.580> verifying 00:24:00.110 --> 00:24:00.120 align:start position:0% uh and the US were capable of verifying 00:24:00.120 --> 00:24:02.029 align:start position:0% uh and the US were capable of verifying that<00:24:00.299> disarmament<00:24:00.840> was<00:24:00.960> happening<00:24:01.380> and<00:24:01.500> so 00:24:02.029 --> 00:24:02.039 align:start position:0% that disarmament was happening and so 00:24:02.039 --> 00:24:04.010 align:start position:0% that disarmament was happening and so they<00:24:02.220> could<00:24:02.340> actually<00:24:02.460> cooperate<00:24:03.120> and<00:24:03.900> there 00:24:04.010 --> 00:24:04.020 align:start position:0% they could actually cooperate and there 00:24:04.020 --> 00:24:05.450 align:start position:0% they could actually cooperate and there actually<00:24:04.200> are<00:24:04.380> now<00:24:04.559> treaties<00:24:05.039> about<00:24:05.220> being 00:24:05.450 --> 00:24:05.460 align:start position:0% actually are now treaties about being 00:24:05.460 --> 00:24:06.950 align:start position:0% actually are now treaties about being able<00:24:05.640> to<00:24:05.760> fly<00:24:05.940> planes<00:24:06.360> over<00:24:06.539> other<00:24:06.720> people's 00:24:06.950 --> 00:24:06.960 align:start position:0% able to fly planes over other people's 00:24:06.960 --> 00:24:08.210 align:start position:0% able to fly planes over other people's territory<00:24:07.320> to<00:24:07.500> verify<00:24:07.740> this<00:24:07.919> stuff<00:24:08.039> it's 00:24:08.210 --> 00:24:08.220 align:start position:0% territory to verify this stuff it's 00:24:08.220 --> 00:24:10.010 align:start position:0% territory to verify this stuff it's called<00:24:08.340> the<00:24:08.460> open<00:24:08.520> spies<00:24:08.940> act<00:24:09.179> it's<00:24:09.840> open 00:24:10.010 --> 00:24:10.020 align:start position:0% called the open spies act it's open 00:24:10.020 --> 00:24:11.930 align:start position:0% called the open spies act it's open Skies<00:24:10.380> act<00:24:10.500> excuse<00:24:10.919> me<00:24:10.980> so<00:24:11.580> technical 00:24:11.930 --> 00:24:11.940 align:start position:0% Skies act excuse me so technical 00:24:11.940 --> 00:24:13.669 align:start position:0% Skies act excuse me so technical advances<00:24:12.419> can<00:24:12.600> enable<00:24:12.840> better<00:24:13.080> verification 00:24:13.669 --> 00:24:13.679 align:start position:0% advances can enable better verification 00:24:13.679 --> 00:24:16.549 align:start position:0% advances can enable better verification and<00:24:14.340> more<00:24:14.520> cooperation<00:24:15.080> uh<00:24:16.080> but<00:24:16.260> of<00:24:16.440> course 00:24:16.549 --> 00:24:16.559 align:start position:0% and more cooperation uh but of course 00:24:16.559 --> 00:24:18.830 align:start position:0% and more cooperation uh but of course spy<00:24:17.460> satellites<00:24:18.059> don't<00:24:18.179> work<00:24:18.360> for<00:24:18.600> this<00:24:18.720> kind 00:24:18.830 --> 00:24:18.840 align:start position:0% spy satellites don't work for this kind 00:24:18.840 --> 00:24:20.750 align:start position:0% spy satellites don't work for this kind of<00:24:18.900> stuff<00:24:19.020> on<00:24:19.260> on<00:24:19.740> the<00:24:19.980> internet<00:24:20.100> we<00:24:20.640> can't 00:24:20.750 --> 00:24:20.760 align:start position:0% of stuff on on the internet we can't 00:24:20.760 --> 00:24:22.190 align:start position:0% of stuff on on the internet we can't just<00:24:20.940> publish<00:24:21.240> everyone's<00:24:21.600> data<00:24:21.900> ever<00:24:22.020> out 00:24:22.190 --> 00:24:22.200 align:start position:0% just publish everyone's data ever out 00:24:22.200 --> 00:24:23.750 align:start position:0% just publish everyone's data ever out there<00:24:22.260> for<00:24:22.440> everyone<00:24:22.500> to<00:24:22.799> see<00:24:22.919> and<00:24:23.100> so<00:24:23.280> to<00:24:23.580> do 00:24:23.750 --> 00:24:23.760 align:start position:0% there for everyone to see and so to do 00:24:23.760 --> 00:24:24.830 align:start position:0% there for everyone to see and so to do this<00:24:23.820> in<00:24:24.000> this<00:24:24.120> case<00:24:24.240> we'd<00:24:24.480> need<00:24:24.600> zero 00:24:24.830 --> 00:24:24.840 align:start position:0% this in this case we'd need zero 00:24:24.840 --> 00:24:26.510 align:start position:0% this in this case we'd need zero knowledge<00:24:25.080> groups 00:24:26.510 --> 00:24:26.520 align:start position:0% knowledge groups 00:24:26.520 --> 00:24:28.730 align:start position:0% knowledge groups um<00:24:26.580> so<00:24:27.539> you<00:24:27.840> know<00:24:27.900> what<00:24:28.080> is<00:24:28.260> your<00:24:28.440> knowledge 00:24:28.730 --> 00:24:28.740 align:start position:0% um so you know what is your knowledge 00:24:28.740 --> 00:24:31.610 align:start position:0% um so you know what is your knowledge proof's<00:24:29.100> good<00:24:29.220> for<00:24:29.820> these<00:24:30.360> three<00:24:30.480> things<00:24:30.780> uh 00:24:31.610 --> 00:24:31.620 align:start position:0% proof's good for these three things uh 00:24:31.620 --> 00:24:33.770 align:start position:0% proof's good for these three things uh on<00:24:31.860> a<00:24:32.039> more 00:24:33.770 --> 00:24:33.780 align:start position:0% on a more 00:24:33.780 --> 00:24:35.390 align:start position:0% on a more you<00:24:34.200> know<00:24:34.260> concrete<00:24:34.679> thing<00:24:34.799> you<00:24:35.039> can<00:24:35.100> also<00:24:35.280> use 00:24:35.390 --> 00:24:35.400 align:start position:0% you know concrete thing you can also use 00:24:35.400 --> 00:24:36.590 align:start position:0% you know concrete thing you can also use them<00:24:35.580> for<00:24:35.700> identity<00:24:36.059> moderation 00:24:36.590 --> 00:24:36.600 align:start position:0% them for identity moderation 00:24:36.600 --> 00:24:38.750 align:start position:0% them for identity moderation decentralization 00:24:38.750 --> 00:24:38.760 align:start position:0% decentralization 00:24:38.760 --> 00:24:39.950 align:start position:0% decentralization um<00:24:38.880> so<00:24:39.000> we<00:24:39.179> need<00:24:39.240> to<00:24:39.360> prove<00:24:39.600> all<00:24:39.720> kinds<00:24:39.900> of 00:24:39.950 --> 00:24:39.960 align:start position:0% um so we need to prove all kinds of 00:24:39.960 --> 00:24:41.810 align:start position:0% um so we need to prove all kinds of things<00:24:40.080> about<00:24:40.200> our<00:24:40.380> identity<00:24:40.740> online<00:24:40.980> uh<00:24:41.640> that 00:24:41.810 --> 00:24:41.820 align:start position:0% things about our identity online uh that 00:24:41.820 --> 00:24:43.250 align:start position:0% things about our identity online uh that we're<00:24:42.000> not<00:24:42.120> North<00:24:42.360> Korean<00:24:42.659> money<00:24:42.780> launderers 00:24:43.250 --> 00:24:43.260 align:start position:0% we're not North Korean money launderers 00:24:43.260 --> 00:24:45.470 align:start position:0% we're not North Korean money launderers for<00:24:43.500> example<00:24:43.679> that<00:24:43.980> were<00:24:44.159> not<00:24:44.280> a<00:24:44.460> bot<00:24:44.700> Elon 00:24:45.470 --> 00:24:45.480 align:start position:0% for example that were not a bot Elon 00:24:45.480 --> 00:24:48.230 align:start position:0% for example that were not a bot Elon Musk<00:24:46.320> um<00:24:46.440> or<00:24:46.740> that<00:24:46.919> we're<00:24:47.100> over<00:24:47.340> 18<00:24:47.520> to<00:24:47.880> view<00:24:48.059> a 00:24:48.230 --> 00:24:48.240 align:start position:0% Musk um or that we're over 18 to view a 00:24:48.240 --> 00:24:49.370 align:start position:0% Musk um or that we're over 18 to view a video 00:24:49.370 --> 00:24:49.380 align:start position:0% video 00:24:49.380 --> 00:24:50.029 align:start position:0% video um 00:24:50.029 --> 00:24:50.039 align:start position:0% um 00:24:50.039 --> 00:24:52.250 align:start position:0% um and<00:24:50.640> so<00:24:50.820> that's<00:24:51.120> time<00:24:51.360> but<00:24:51.659> I<00:24:51.780> have<00:24:51.900> some<00:24:52.080> work 00:24:52.250 --> 00:24:52.260 align:start position:0% and so that's time but I have some work 00:24:52.260 --> 00:24:53.990 align:start position:0% and so that's time but I have some work on<00:24:52.500> this<00:24:52.620> that<00:24:52.919> would<00:24:53.580> kind<00:24:53.760> of<00:24:53.880> be 00:24:53.990 --> 00:24:54.000 align:start position:0% on this that would kind of be 00:24:54.000 --> 00:24:55.250 align:start position:0% on this that would kind of be interesting<00:24:54.360> so 00:24:55.250 --> 00:24:55.260 align:start position:0% interesting so 00:24:55.260 --> 00:24:57.770 align:start position:0% interesting so with<00:24:55.799> that<00:24:55.980> uh 00:24:57.770 --> 00:24:57.780 align:start position:0% with that uh 00:24:57.780 --> 00:25:01.400 align:start position:0% with that uh I<00:24:58.260> guess<00:24:58.380> I<00:24:58.620> will<00:24:58.740> take<00:24:58.980> questions