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:13.330 align:start position:0% [Music] 00:00:13.330 --> 00:00:13.340 align:start position:0% 00:00:13.340 --> 00:00:16.010 align:start position:0% we're<00:00:14.340> here<00:00:14.460> to<00:00:14.639> talk<00:00:14.759> today<00:00:15.000> about<00:00:15.540> our 00:00:16.010 --> 00:00:16.020 align:start position:0% we're here to talk today about our 00:00:16.020 --> 00:00:18.349 align:start position:0% we're here to talk today about our journey<00:00:16.260> from<00:00:16.500> solidity<00:00:16.980> depth<00:00:17.279> to<00:00:17.340> ZK<00:00:17.699> Dev<00:00:17.880> I 00:00:18.349 --> 00:00:18.359 align:start position:0% journey from solidity depth to ZK Dev I 00:00:18.359 --> 00:00:21.950 align:start position:0% journey from solidity depth to ZK Dev I talk<00:00:18.660> about<00:00:18.840> how<00:00:19.560> we<00:00:19.680> went<00:00:19.980> from<00:00:20.520> uh<00:00:21.300> salinity 00:00:21.950 --> 00:00:21.960 align:start position:0% talk about how we went from uh salinity 00:00:21.960 --> 00:00:24.050 align:start position:0% talk about how we went from uh salinity developers<00:00:22.560> it<00:00:23.039> got<00:00:23.340> introduced<00:00:23.699> to<00:00:23.760> zero 00:00:24.050 --> 00:00:24.060 align:start position:0% developers it got introduced to zero 00:00:24.060 --> 00:00:25.310 align:start position:0% developers it got introduced to zero knowledge<00:00:24.240> cryptography<00:00:24.779> and<00:00:24.960> went<00:00:25.080> on<00:00:25.199> to 00:00:25.310 --> 00:00:25.320 align:start position:0% knowledge cryptography and went on to 00:00:25.320 --> 00:00:27.290 align:start position:0% knowledge cryptography and went on to implementing<00:00:25.800> battleships<00:00:26.400> so<00:00:26.580> uh<00:00:26.760> my<00:00:27.180> name 00:00:27.290 --> 00:00:27.300 align:start position:0% implementing battleships so uh my name 00:00:27.300 --> 00:00:29.990 align:start position:0% implementing battleships so uh my name is<00:00:27.359> Ian<00:00:27.720> and<00:00:28.260> I<00:00:28.380> am<00:00:28.439> Jack<00:00:28.680> and<00:00:29.400> yeah<00:00:29.640> like<00:00:29.820> we 00:00:29.990 --> 00:00:30.000 align:start position:0% is Ian and I am Jack and yeah like we 00:00:30.000 --> 00:00:31.609 align:start position:0% is Ian and I am Jack and yeah like we said<00:00:30.119> we're<00:00:30.359> gonna<00:00:30.539> walk<00:00:31.140> you<00:00:31.320> through<00:00:31.439> our 00:00:31.609 --> 00:00:31.619 align:start position:0% said we're gonna walk you through our 00:00:31.619 --> 00:00:33.110 align:start position:0% said we're gonna walk you through our journey<00:00:31.920> and<00:00:32.099> uh<00:00:32.279> how<00:00:32.460> we<00:00:32.579> got<00:00:32.700> to<00:00:32.820> where<00:00:33.000> we 00:00:33.110 --> 00:00:33.120 align:start position:0% journey and uh how we got to where we 00:00:33.120 --> 00:00:34.130 align:start position:0% journey and uh how we got to where we are<00:00:33.239> today 00:00:34.130 --> 00:00:34.140 align:start position:0% are today 00:00:34.140 --> 00:00:35.990 align:start position:0% are today um but<00:00:34.500> first<00:00:34.620> off<00:00:34.800> I<00:00:34.980> want<00:00:35.100> to<00:00:35.219> start<00:00:35.399> by<00:00:35.700> uh 00:00:35.990 --> 00:00:36.000 align:start position:0% um but first off I want to start by uh 00:00:36.000 --> 00:00:38.150 align:start position:0% um but first off I want to start by uh thinking<00:00:36.300> the<00:00:36.420> ethereum<00:00:36.840> foundation 00:00:38.150 --> 00:00:38.160 align:start position:0% thinking the ethereum foundation 00:00:38.160 --> 00:00:39.650 align:start position:0% thinking the ethereum foundation um<00:00:38.219> just<00:00:38.880> over<00:00:39.059> a<00:00:39.180> year<00:00:39.300> ago<00:00:39.540> today 00:00:39.650 --> 00:00:39.660 align:start position:0% um just over a year ago today 00:00:39.660 --> 00:00:41.930 align:start position:0% um just over a year ago today battleships<00:00:40.440> was<00:00:40.559> just<00:00:40.739> an<00:00:40.860> idea<00:00:41.160> and<00:00:41.579> to<00:00:41.760> go 00:00:41.930 --> 00:00:41.940 align:start position:0% battleships was just an idea and to go 00:00:41.940 --> 00:00:44.270 align:start position:0% battleships was just an idea and to go from<00:00:42.180> presenting<00:00:42.719> at<00:00:42.840> Denver<00:00:43.200> uh<00:00:43.739> receiving<00:00:44.100> a 00:00:44.270 --> 00:00:44.280 align:start position:0% from presenting at Denver uh receiving a 00:00:44.280 --> 00:00:46.610 align:start position:0% from presenting at Denver uh receiving a grant<00:00:44.940> from<00:00:45.120> the<00:00:45.180> ethereum<00:00:45.600> foundation<00:00:46.079> up 00:00:46.610 --> 00:00:46.620 align:start position:0% grant from the ethereum foundation up 00:00:46.620 --> 00:00:49.010 align:start position:0% grant from the ethereum foundation up here<00:00:46.800> uh<00:00:47.640> presenting<00:00:47.940> at<00:00:48.000> Devcon<00:00:48.420> today<00:00:48.660> you 00:00:49.010 --> 00:00:49.020 align:start position:0% here uh presenting at Devcon today you 00:00:49.020 --> 00:00:51.110 align:start position:0% here uh presenting at Devcon today you know<00:00:49.140> it's<00:00:49.260> a<00:00:49.440> pretty<00:00:49.559> surreal<00:00:49.980> experience<00:00:50.460> so 00:00:51.110 --> 00:00:51.120 align:start position:0% know it's a pretty surreal experience so 00:00:51.120 --> 00:00:55.189 align:start position:0% know it's a pretty surreal experience so um none<00:00:51.539> of<00:00:51.660> us<00:00:51.719> expected<00:00:52.200> this<00:00:52.379> so<00:00:52.559> thank<00:00:52.739> you 00:00:55.189 --> 00:00:55.199 align:start position:0% 00:00:55.199 --> 00:00:58.490 align:start position:0% so<00:00:55.980> uh<00:00:56.579> before<00:00:57.059> jumping<00:00:57.539> into<00:00:57.600> what<00:00:58.079> uh<00:00:58.260> our 00:00:58.490 --> 00:00:58.500 align:start position:0% so uh before jumping into what uh our 00:00:58.500 --> 00:01:00.170 align:start position:0% so uh before jumping into what uh our journey<00:00:58.680> in<00:00:58.860> ZK<00:00:59.219> first<00:00:59.460> let's<00:00:59.699> start<00:00:59.879> off<00:01:00.000> with 00:01:00.170 --> 00:01:00.180 align:start position:0% journey in ZK first let's start off with 00:01:00.180 --> 00:01:03.290 align:start position:0% journey in ZK first let's start off with a<00:01:00.300> question<00:01:00.420> what<00:01:00.780> is<00:01:00.899> web3 00:01:03.290 --> 00:01:03.300 align:start position:0% a question what is web3 00:01:03.300 --> 00:01:04.850 align:start position:0% a question what is web3 shout<00:01:03.780> it<00:01:03.840> out<00:01:03.960> yeah<00:01:04.140> please<00:01:04.500> raise<00:01:04.680> your 00:01:04.850 --> 00:01:04.860 align:start position:0% shout it out yeah please raise your 00:01:04.860 --> 00:01:07.850 align:start position:0% shout it out yeah please raise your hands 00:01:07.850 --> 00:01:07.860 align:start position:0% 00:01:07.860 --> 00:01:09.950 align:start position:0% uh<00:01:08.520> I<00:01:08.640> think 00:01:09.950 --> 00:01:09.960 align:start position:0% uh I think 00:01:09.960 --> 00:01:12.830 align:start position:0% uh I think decentralized 00:01:12.830 --> 00:01:12.840 align:start position:0% decentralized 00:01:12.840 --> 00:01:15.530 align:start position:0% decentralized all<00:01:13.200> right<00:01:13.320> answers<00:01:13.680> uh<00:01:14.280> I<00:01:15.000> think<00:01:15.119> to<00:01:15.299> really 00:01:15.530 --> 00:01:15.540 align:start position:0% all right answers uh I think to really 00:01:15.540 --> 00:01:16.969 align:start position:0% all right answers uh I think to really get<00:01:15.720> an<00:01:15.840> appreciation<00:01:16.320> for<00:01:16.680> what<00:01:16.799> the 00:01:16.969 --> 00:01:16.979 align:start position:0% get an appreciation for what the 00:01:16.979 --> 00:01:18.890 align:start position:0% get an appreciation for what the definition<00:01:17.100> of<00:01:17.460> what<00:01:17.580> three<00:01:17.760> is<00:01:18.000> so<00:01:18.240> uh<00:01:18.540> it'd 00:01:18.890 --> 00:01:18.900 align:start position:0% definition of what three is so uh it'd 00:01:18.900 --> 00:01:20.630 align:start position:0% definition of what three is so uh it'd be<00:01:18.960> helpful<00:01:19.500> to<00:01:19.680> look<00:01:19.860> at<00:01:19.979> what<00:01:20.280> some<00:01:20.460> of<00:01:20.580> the 00:01:20.630 --> 00:01:20.640 align:start position:0% be helpful to look at what some of the 00:01:20.640 --> 00:01:22.670 align:start position:0% be helpful to look at what some of the tight<00:01:20.820> ends<00:01:21.119> of<00:01:21.240> the<00:01:21.360> industry<00:01:21.720> have<00:01:21.840> said<00:01:22.020> so 00:01:22.670 --> 00:01:22.680 align:start position:0% tight ends of the industry have said so 00:01:22.680 --> 00:01:25.190 align:start position:0% tight ends of the industry have said so Satoshi<00:01:23.340> oh<00:01:23.640> wait<00:01:23.759> that's<00:01:23.880> not<00:01:24.000> Satoshi 00:01:25.190 --> 00:01:25.200 align:start position:0% Satoshi oh wait that's not Satoshi 00:01:25.200 --> 00:01:26.630 align:start position:0% Satoshi oh wait that's not Satoshi I<00:01:25.799> guess 00:01:26.630 --> 00:01:26.640 align:start position:0% I guess 00:01:26.640 --> 00:01:29.330 align:start position:0% I guess okay<00:01:27.119> you<00:01:27.420> know<00:01:27.479> we'll<00:01:27.659> go<00:01:27.780> with<00:01:27.960> that<00:01:28.340> Satoshi 00:01:29.330 --> 00:01:29.340 align:start position:0% okay you know we'll go with that Satoshi 00:01:29.340 --> 00:01:31.249 align:start position:0% okay you know we'll go with that Satoshi and<00:01:29.580> I<00:01:29.700> just<00:01:29.820> want<00:01:29.939> to<00:01:30.060> preface<00:01:30.360> real<00:01:30.540> quick<00:01:30.720> uh 00:01:31.249 --> 00:01:31.259 align:start position:0% and I just want to preface real quick uh 00:01:31.259 --> 00:01:33.230 align:start position:0% and I just want to preface real quick uh blockchain<00:01:31.920> predated<00:01:32.400> what<00:01:32.640> three<00:01:32.820> by<00:01:33.060> about 00:01:33.230 --> 00:01:33.240 align:start position:0% blockchain predated what three by about 00:01:33.240 --> 00:01:35.510 align:start position:0% blockchain predated what three by about five<00:01:33.540> years<00:01:33.840> uh<00:01:34.439> so<00:01:34.680> this<00:01:34.920> is<00:01:34.979> defined<00:01:35.460> in 00:01:35.510 --> 00:01:35.520 align:start position:0% five years uh so this is defined in 00:01:35.520 --> 00:01:37.630 align:start position:0% five years uh so this is defined in satoshi's<00:01:36.180> terms<00:01:36.540> of<00:01:36.659> uh<00:01:36.840> what<00:01:37.079> Bitcoin<00:01:37.439> was 00:01:37.630 --> 00:01:37.640 align:start position:0% satoshi's terms of uh what Bitcoin was 00:01:37.640 --> 00:01:40.910 align:start position:0% satoshi's terms of uh what Bitcoin was uh<00:01:38.640> but<00:01:38.820> he<00:01:39.000> basically<00:01:39.299> said<00:01:39.540> Bitcoin<00:01:40.439> is<00:01:40.680> a 00:01:40.910 --> 00:01:40.920 align:start position:0% uh but he basically said Bitcoin is a 00:01:40.920 --> 00:01:42.350 align:start position:0% uh but he basically said Bitcoin is a purely<00:01:41.159> peer-to-peer<00:01:41.880> version<00:01:42.060> of 00:01:42.350 --> 00:01:42.360 align:start position:0% purely peer-to-peer version of 00:01:42.360 --> 00:01:44.270 align:start position:0% purely peer-to-peer version of electronic<00:01:42.900> cash<00:01:43.079> which<00:01:43.560> would<00:01:43.740> allow<00:01:44.040> online 00:01:44.270 --> 00:01:44.280 align:start position:0% electronic cash which would allow online 00:01:44.280 --> 00:01:46.069 align:start position:0% electronic cash which would allow online payments<00:01:44.820> to<00:01:44.939> be<00:01:45.060> sent<00:01:45.180> directly<00:01:45.600> from<00:01:45.900> one 00:01:46.069 --> 00:01:46.079 align:start position:0% payments to be sent directly from one 00:01:46.079 --> 00:01:48.410 align:start position:0% payments to be sent directly from one party<00:01:46.320> to<00:01:46.740> another<00:01:46.920> without<00:01:47.700> going<00:01:48.060> through<00:01:48.240> a 00:01:48.410 --> 00:01:48.420 align:start position:0% party to another without going through a 00:01:48.420 --> 00:01:51.410 align:start position:0% party to another without going through a financial<00:01:48.600> uh<00:01:49.200> financial<00:01:49.439> institution<00:01:50.420> uh 00:01:51.410 --> 00:01:51.420 align:start position:0% financial uh financial institution uh 00:01:51.420 --> 00:01:53.090 align:start position:0% financial uh financial institution uh next<00:01:51.720> someone<00:01:52.020> we<00:01:52.320> probably<00:01:52.560> all<00:01:52.740> recognize 00:01:53.090 --> 00:01:53.100 align:start position:0% next someone we probably all recognize 00:01:53.100 --> 00:01:55.929 align:start position:0% next someone we probably all recognize here<00:01:53.340> as<00:01:53.579> well<00:01:53.700> uh 00:01:55.929 --> 00:01:55.939 align:start position:0% here as well uh 00:01:55.939 --> 00:01:58.789 align:start position:0% here as well uh vitalik<00:01:56.939> buterin<00:01:57.420> uh<00:01:58.140> in<00:01:58.320> the<00:01:58.439> context<00:01:58.619> of 00:01:58.789 --> 00:01:58.799 align:start position:0% vitalik buterin uh in the context of 00:01:58.799 --> 00:02:00.710 align:start position:0% vitalik buterin uh in the context of ethereum<00:01:59.340> his<00:01:59.759> definition<00:02:00.000> of<00:02:00.299> what<00:02:00.479> three 00:02:00.710 --> 00:02:00.720 align:start position:0% ethereum his definition of what three 00:02:00.720 --> 00:02:03.710 align:start position:0% ethereum his definition of what three was<00:02:01.079> what<00:02:01.500> ethereum<00:02:02.040> intends<00:02:02.939> to<00:02:03.000> provide<00:02:03.360> is 00:02:03.710 --> 00:02:03.720 align:start position:0% was what ethereum intends to provide is 00:02:03.720 --> 00:02:05.870 align:start position:0% was what ethereum intends to provide is a<00:02:03.840> blockchain<00:02:04.259> with<00:02:04.560> a<00:02:04.740> built-in<00:02:05.159> fully 00:02:05.870 --> 00:02:05.880 align:start position:0% a blockchain with a built-in fully 00:02:05.880 --> 00:02:07.370 align:start position:0% a blockchain with a built-in fully fledged<00:02:06.299> terrain<00:02:06.600> complete<00:02:07.020> programming 00:02:07.370 --> 00:02:07.380 align:start position:0% fledged terrain complete programming 00:02:07.380 --> 00:02:08.690 align:start position:0% fledged terrain complete programming language<00:02:07.560> that<00:02:07.979> could<00:02:08.099> be<00:02:08.280> used<00:02:08.399> to<00:02:08.580> create 00:02:08.690 --> 00:02:08.700 align:start position:0% language that could be used to create 00:02:08.700 --> 00:02:10.850 align:start position:0% language that could be used to create contracts<00:02:09.360> that<00:02:09.840> then<00:02:10.020> can<00:02:10.200> be<00:02:10.319> used<00:02:10.500> to 00:02:10.850 --> 00:02:10.860 align:start position:0% contracts that then can be used to 00:02:10.860 --> 00:02:12.470 align:start position:0% contracts that then can be used to encode<00:02:11.160> arbitrary<00:02:11.700> State<00:02:12.000> transition 00:02:12.470 --> 00:02:12.480 align:start position:0% encode arbitrary State transition 00:02:12.480 --> 00:02:14.510 align:start position:0% encode arbitrary State transition functions<00:02:13.020> but<00:02:13.739> none<00:02:13.980> of<00:02:14.099> this<00:02:14.220> would<00:02:14.400> be 00:02:14.510 --> 00:02:14.520 align:start position:0% functions but none of this would be 00:02:14.520 --> 00:02:15.770 align:start position:0% functions but none of this would be possible<00:02:14.819> if<00:02:15.000> it<00:02:15.180> weren't<00:02:15.300> for<00:02:15.420> the<00:02:15.540> work<00:02:15.599> of 00:02:15.770 --> 00:02:15.780 align:start position:0% possible if it weren't for the work of 00:02:15.780 --> 00:02:18.229 align:start position:0% possible if it weren't for the work of Nick<00:02:15.959> Sabo<00:02:16.560> who<00:02:16.739> I<00:02:17.099> coined<00:02:17.760> the<00:02:17.819> term<00:02:17.940> smart 00:02:18.229 --> 00:02:18.239 align:start position:0% Nick Sabo who I coined the term smart 00:02:18.239 --> 00:02:20.570 align:start position:0% Nick Sabo who I coined the term smart contract<00:02:18.720> and<00:02:18.959> came<00:02:19.200> up<00:02:19.260> with<00:02:19.440> idea<00:02:19.860> in<00:02:19.920> 1994 00:02:20.570 --> 00:02:20.580 align:start position:0% contract and came up with idea in 1994 00:02:20.580 --> 00:02:25.210 align:start position:0% contract and came up with idea in 1994 and<00:02:21.300> his<00:02:21.660> uh<00:02:23.040> his<00:02:23.760> idea<00:02:24.120> of<00:02:24.300> what<00:02:24.540> this<00:02:24.780> eco 00:02:25.210 --> 00:02:25.220 align:start position:0% and his uh his idea of what this eco 00:02:25.220 --> 00:02:27.710 align:start position:0% and his uh his idea of what this eco ecosystem<00:02:26.220> representative<00:02:26.879> was<00:02:27.180> the 00:02:27.710 --> 00:02:27.720 align:start position:0% ecosystem representative was the 00:02:27.720 --> 00:02:30.050 align:start position:0% ecosystem representative was the obscurity<00:02:28.140> of<00:02:28.319> a<00:02:28.500> large<00:02:28.620> random<00:02:29.040> number<00:02:29.220> so 00:02:30.050 --> 00:02:30.060 align:start position:0% obscurity of a large random number so 00:02:30.060 --> 00:02:32.750 align:start position:0% obscurity of a large random number so vast<00:02:30.480> that<00:02:30.720> a<00:02:30.900> lucky<00:02:31.020> guess<00:02:31.319> is<00:02:31.560> unlikely<00:02:32.040> if 00:02:32.750 --> 00:02:32.760 align:start position:0% vast that a lucky guess is unlikely if 00:02:32.760 --> 00:02:34.430 align:start position:0% vast that a lucky guess is unlikely if the<00:02:32.940> in<00:02:33.120> if<00:02:33.360> desired<00:02:33.780> the<00:02:33.900> lifetime<00:02:34.200> of<00:02:34.379> the 00:02:34.430 --> 00:02:34.440 align:start position:0% the in if desired the lifetime of the 00:02:34.440 --> 00:02:36.170 align:start position:0% the in if desired the lifetime of the universe<00:02:34.860> and<00:02:35.280> that's<00:02:35.459> the<00:02:35.640> foundation<00:02:35.940> on 00:02:36.170 --> 00:02:36.180 align:start position:0% universe and that's the foundation on 00:02:36.180 --> 00:02:38.690 align:start position:0% universe and that's the foundation on what<00:02:36.480> uh<00:02:37.080> cryptographic<00:02:37.739> Protocols<00:02:38.280> are<00:02:38.520> in 00:02:38.690 --> 00:02:38.700 align:start position:0% what uh cryptographic Protocols are in 00:02:38.700 --> 00:02:40.910 align:start position:0% what uh cryptographic Protocols are in an<00:02:38.940> intern<00:02:39.120> smart<00:02:39.480> contracts<00:02:39.959> are<00:02:40.080> built<00:02:40.379> and 00:02:40.910 --> 00:02:40.920 align:start position:0% an intern smart contracts are built and 00:02:40.920 --> 00:02:43.610 align:start position:0% an intern smart contracts are built and then<00:02:41.040> finally<00:02:41.480> appropriately<00:02:42.480> ending<00:02:43.019> at<00:02:43.319> the 00:02:43.610 --> 00:02:43.620 align:start position:0% then finally appropriately ending at the 00:02:43.620 --> 00:02:45.710 align:start position:0% then finally appropriately ending at the uh<00:02:43.920> founder<00:02:44.459> of<00:02:44.580> the<00:02:44.760> or<00:02:44.940> the<00:02:45.120> corner<00:02:45.540> of<00:02:45.599> the 00:02:45.710 --> 00:02:45.720 align:start position:0% uh founder of the or the corner of the 00:02:45.720 --> 00:02:47.509 align:start position:0% uh founder of the or the corner of the term<00:02:45.780> what<00:02:45.959> three<00:02:46.200> Gavin<00:02:46.620> wood<00:02:46.800> his 00:02:47.509 --> 00:02:47.519 align:start position:0% term what three Gavin wood his 00:02:47.519 --> 00:02:49.130 align:start position:0% term what three Gavin wood his definition<00:02:47.700> was 00:02:49.130 --> 00:02:49.140 align:start position:0% definition was 00:02:49.140 --> 00:02:51.530 align:start position:0% definition was in<00:02:49.800> short<00:02:49.980> we<00:02:50.580> engineer<00:02:50.879> the<00:02:51.060> system<00:02:51.239> to 00:02:51.530 --> 00:02:51.540 align:start position:0% in short we engineer the system to 00:02:51.540 --> 00:02:53.150 align:start position:0% in short we engineer the system to mathematically<00:02:52.080> enforce<00:02:52.560> our<00:02:52.860> prior 00:02:53.150 --> 00:02:53.160 align:start position:0% mathematically enforce our prior 00:02:53.160 --> 00:02:54.949 align:start position:0% mathematically enforce our prior assumptions<00:02:53.700> since<00:02:54.060> no<00:02:54.300> government<00:02:54.540> or 00:02:54.949 --> 00:02:54.959 align:start position:0% assumptions since no government or 00:02:54.959 --> 00:02:58.070 align:start position:0% assumptions since no government or organization<00:02:55.500> can<00:02:55.739> be<00:02:56.040> uh<00:02:56.819> be<00:02:57.060> trusted 00:02:58.070 --> 00:02:58.080 align:start position:0% organization can be uh be trusted 00:02:58.080 --> 00:02:59.809 align:start position:0% organization can be uh be trusted so<00:02:58.560> that<00:02:58.739> leaves<00:02:58.980> us<00:02:59.160> with<00:02:59.459> our<00:02:59.640> own 00:02:59.809 --> 00:02:59.819 align:start position:0% so that leaves us with our own 00:02:59.819 --> 00:03:02.270 align:start position:0% so that leaves us with our own definition<00:03:00.060> what<00:03:01.019> three<00:03:01.260> is<00:03:01.560> sovereignty<00:03:02.040> and 00:03:02.270 --> 00:03:02.280 align:start position:0% definition what three is sovereignty and 00:03:02.280 --> 00:03:04.309 align:start position:0% definition what three is sovereignty and cyberspace<00:03:02.879> and<00:03:03.660> following<00:03:03.959> from<00:03:04.200> that 00:03:04.309 --> 00:03:04.319 align:start position:0% cyberspace and following from that 00:03:04.319 --> 00:03:06.650 align:start position:0% cyberspace and following from that cryptography<00:03:05.099> is<00:03:05.400> the<00:03:05.519> authority<00:03:06.000> uh<00:03:06.480> the 00:03:06.650 --> 00:03:06.660 align:start position:0% cryptography is the authority uh the 00:03:06.660 --> 00:03:09.290 align:start position:0% cryptography is the authority uh the enforcer<00:03:07.080> of<00:03:07.260> the<00:03:07.319> laws<00:03:07.680> in<00:03:08.099> this<00:03:08.280> news<00:03:08.459> uh<00:03:09.120> and 00:03:09.290 --> 00:03:09.300 align:start position:0% enforcer of the laws in this news uh and 00:03:09.300 --> 00:03:12.110 align:start position:0% enforcer of the laws in this news uh and set<00:03:09.480> space 00:03:12.110 --> 00:03:12.120 align:start position:0% 00:03:12.120 --> 00:03:15.290 align:start position:0% so<00:03:12.659> now<00:03:12.959> that<00:03:13.200> we<00:03:13.620> have<00:03:13.920> a<00:03:14.340> definition<00:03:14.700> a 00:03:15.290 --> 00:03:15.300 align:start position:0% so now that we have a definition a 00:03:15.300 --> 00:03:18.530 align:start position:0% so now that we have a definition a little<00:03:15.420> bit<00:03:15.540> of<00:03:15.659> the<00:03:16.080> etymology<00:03:16.440> of<00:03:17.099> web3<00:03:17.640> uh 00:03:18.530 --> 00:03:18.540 align:start position:0% little bit of the etymology of web3 uh 00:03:18.540 --> 00:03:20.210 align:start position:0% little bit of the etymology of web3 uh let's<00:03:18.720> talk<00:03:18.959> about<00:03:19.080> the<00:03:19.500> actual<00:03:19.680> state<00:03:19.920> of 00:03:20.210 --> 00:03:20.220 align:start position:0% let's talk about the actual state of 00:03:20.220 --> 00:03:21.350 align:start position:0% let's talk about the actual state of this<00:03:20.400> industry 00:03:21.350 --> 00:03:21.360 align:start position:0% this industry 00:03:21.360 --> 00:03:22.790 align:start position:0% this industry um<00:03:21.420> and<00:03:21.720> specifically<00:03:22.200> some<00:03:22.319> of<00:03:22.500> the<00:03:22.560> issues 00:03:22.790 --> 00:03:22.800 align:start position:0% um and specifically some of the issues 00:03:22.800 --> 00:03:24.290 align:start position:0% um and specifically some of the issues that<00:03:22.980> are<00:03:23.099> plaguing<00:03:23.459> it 00:03:24.290 --> 00:03:24.300 align:start position:0% that are plaguing it 00:03:24.300 --> 00:03:26.630 align:start position:0% that are plaguing it um<00:03:24.420> personally<00:03:24.900> we<00:03:25.319> see<00:03:25.560> the<00:03:25.920> biggest<00:03:26.040> issue 00:03:26.630 --> 00:03:26.640 align:start position:0% um personally we see the biggest issue 00:03:26.640 --> 00:03:30.050 align:start position:0% um personally we see the biggest issue as<00:03:27.060> being<00:03:27.360> the<00:03:28.440> um<00:03:28.500> almost<00:03:29.220> zealous 00:03:30.050 --> 00:03:30.060 align:start position:0% as being the um almost zealous 00:03:30.060 --> 00:03:32.930 align:start position:0% as being the um almost zealous conviction<00:03:30.480> in<00:03:30.959> tokenization<00:03:31.560> of<00:03:32.099> all<00:03:32.459> assets 00:03:32.930 --> 00:03:32.940 align:start position:0% conviction in tokenization of all assets 00:03:32.940 --> 00:03:34.970 align:start position:0% conviction in tokenization of all assets and<00:03:33.480> uh<00:03:34.080> perhaps<00:03:34.379> this<00:03:34.500> might<00:03:34.680> be<00:03:34.739> a<00:03:34.860> little 00:03:34.970 --> 00:03:34.980 align:start position:0% and uh perhaps this might be a little 00:03:34.980 --> 00:03:37.070 align:start position:0% and uh perhaps this might be a little america-centric<00:03:35.700> but<00:03:36.360> um<00:03:36.420> you<00:03:36.840> know<00:03:36.900> you 00:03:37.070 --> 00:03:37.080 align:start position:0% america-centric but um you know you 00:03:37.080 --> 00:03:38.089 align:start position:0% america-centric but um you know you could<00:03:37.140> just<00:03:37.260> take<00:03:37.379> a<00:03:37.500> look<00:03:37.560> at<00:03:37.680> the<00:03:37.800> housing 00:03:38.089 --> 00:03:38.099 align:start position:0% could just take a look at the housing 00:03:38.099 --> 00:03:39.830 align:start position:0% could just take a look at the housing market<00:03:38.220> as<00:03:38.580> an<00:03:38.700> example<00:03:38.940> of<00:03:39.180> an<00:03:39.420> asset<00:03:39.720> class 00:03:39.830 --> 00:03:39.840 align:start position:0% market as an example of an asset class 00:03:39.840 --> 00:03:41.630 align:start position:0% market as an example of an asset class that<00:03:40.140> maybe<00:03:40.319> you<00:03:40.560> don't<00:03:40.739> want<00:03:41.040> to<00:03:41.280> hyper 00:03:41.630 --> 00:03:41.640 align:start position:0% that maybe you don't want to hyper 00:03:41.640 --> 00:03:44.509 align:start position:0% that maybe you don't want to hyper financialize<00:03:42.360> and<00:03:43.260> what<00:03:43.739> we<00:03:43.980> essentially<00:03:44.280> are 00:03:44.509 --> 00:03:44.519 align:start position:0% financialize and what we essentially are 00:03:44.519 --> 00:03:46.729 align:start position:0% financialize and what we essentially are seeing<00:03:44.819> is<00:03:45.239> that<00:03:45.480> as<00:03:45.780> time<00:03:46.080> has<00:03:46.319> gone<00:03:46.500> on 00:03:46.729 --> 00:03:46.739 align:start position:0% seeing is that as time has gone on 00:03:46.739 --> 00:03:49.130 align:start position:0% seeing is that as time has gone on protocols<00:03:47.700> focused<00:03:48.120> more<00:03:48.299> and<00:03:48.480> more<00:03:48.659> on 00:03:49.130 --> 00:03:49.140 align:start position:0% protocols focused more and more on 00:03:49.140 --> 00:03:51.530 align:start position:0% protocols focused more and more on financial<00:03:49.739> prosperity<00:03:50.400> rather<00:03:50.760> than<00:03:51.000> the 00:03:51.530 --> 00:03:51.540 align:start position:0% financial prosperity rather than the 00:03:51.540 --> 00:03:53.270 align:start position:0% financial prosperity rather than the actual<00:03:51.720> core<00:03:51.959> tenets<00:03:52.379> of<00:03:52.560> what<00:03:52.680> web3<00:03:53.040> is 00:03:53.270 --> 00:03:53.280 align:start position:0% actual core tenets of what web3 is 00:03:53.280 --> 00:03:55.729 align:start position:0% actual core tenets of what web3 is supposed<00:03:53.400> to<00:03:53.580> be<00:03:53.640> as<00:03:53.819> as<00:03:54.060> we<00:03:54.239> just<00:03:54.360> went<00:03:54.540> over 00:03:55.729 --> 00:03:55.739 align:start position:0% supposed to be as as we just went over 00:03:55.739 --> 00:03:58.610 align:start position:0% supposed to be as as we just went over um<00:03:55.799> and<00:03:56.340> beyond<00:03:56.879> that<00:03:57.060> uh<00:03:57.480> I'm<00:03:57.720> sure<00:03:57.959> a<00:03:58.440> lot<00:03:58.500> of 00:03:58.610 --> 00:03:58.620 align:start position:0% um and beyond that uh I'm sure a lot of 00:03:58.620 --> 00:03:59.930 align:start position:0% um and beyond that uh I'm sure a lot of you<00:03:58.739> here<00:03:58.920> have<00:03:59.099> heard<00:03:59.280> a<00:03:59.459> lot<00:03:59.519> of<00:03:59.580> talk<00:03:59.760> about 00:03:59.930 --> 00:03:59.940 align:start position:0% you here have heard a lot of talk about 00:03:59.940 --> 00:04:01.850 align:start position:0% you here have heard a lot of talk about privacy<00:04:00.420> and<00:04:00.540> scalability<00:04:01.080> over<00:04:01.440> the<00:04:01.680> past 00:04:01.850 --> 00:04:01.860 align:start position:0% privacy and scalability over the past 00:04:01.860 --> 00:04:03.470 align:start position:0% privacy and scalability over the past few<00:04:02.340> hours 00:04:03.470 --> 00:04:03.480 align:start position:0% few hours 00:04:03.480 --> 00:04:05.990 align:start position:0% few hours um<00:04:03.540> again<00:04:03.900> from<00:04:04.440> an<00:04:05.099> individual<00:04:05.580> perspective 00:04:05.990 --> 00:04:06.000 align:start position:0% um again from an individual perspective 00:04:06.000 --> 00:04:08.570 align:start position:0% um again from an individual perspective and<00:04:06.420> from<00:04:06.780> an<00:04:06.959> Enterprise<00:04:07.080> perspective<00:04:07.799> uh 00:04:08.570 --> 00:04:08.580 align:start position:0% and from an Enterprise perspective uh 00:04:08.580 --> 00:04:11.089 align:start position:0% and from an Enterprise perspective uh it's<00:04:08.879> unusable<00:04:09.540> a<00:04:09.959> lot<00:04:10.140> of<00:04:10.200> the<00:04:10.260> time<00:04:10.439> so<00:04:10.620> I 00:04:11.089 --> 00:04:11.099 align:start position:0% it's unusable a lot of the time so I 00:04:11.099 --> 00:04:13.190 align:start position:0% it's unusable a lot of the time so I mean<00:04:11.220> if<00:04:11.459> you<00:04:11.640> try<00:04:11.819> to<00:04:11.939> make<00:04:12.420> a<00:04:12.599> swap<00:04:12.900> when 00:04:13.190 --> 00:04:13.200 align:start position:0% mean if you try to make a swap when 00:04:13.200 --> 00:04:14.630 align:start position:0% mean if you try to make a swap when ether<00:04:13.500> was<00:04:13.739> at<00:04:13.860> forty<00:04:14.099> eight<00:04:14.220> hundred<00:04:14.459> dollars 00:04:14.630 --> 00:04:14.640 align:start position:0% ether was at forty eight hundred dollars 00:04:14.640 --> 00:04:17.750 align:start position:0% ether was at forty eight hundred dollars you<00:04:14.819> probably<00:04:15.000> paid<00:04:15.239> 50<00:04:15.480> for<00:04:15.959> a<00:04:16.079> swap<00:04:16.320> that's 00:04:17.750 --> 00:04:17.760 align:start position:0% you probably paid 50 for a swap that's 00:04:17.760 --> 00:04:19.250 align:start position:0% you probably paid 50 for a swap that's hurts 00:04:19.250 --> 00:04:19.260 align:start position:0% hurts 00:04:19.260 --> 00:04:22.730 align:start position:0% hurts um<00:04:19.380> and<00:04:19.859> while<00:04:20.519> some<00:04:20.699> of<00:04:20.820> us<00:04:21.000> have<00:04:21.380> gone<00:04:22.380> ahead 00:04:22.730 --> 00:04:22.740 align:start position:0% um and while some of us have gone ahead 00:04:22.740 --> 00:04:24.950 align:start position:0% um and while some of us have gone ahead with<00:04:22.979> web<00:04:23.460> 3<00:04:23.699> despite<00:04:24.120> privacy<00:04:24.600> concerns 00:04:24.950 --> 00:04:24.960 align:start position:0% with web 3 despite privacy concerns 00:04:24.960 --> 00:04:27.590 align:start position:0% with web 3 despite privacy concerns there<00:04:25.259> are<00:04:25.380> a<00:04:25.500> lot<00:04:25.620> of<00:04:25.800> ways<00:04:26.220> that<00:04:26.600> private 00:04:27.590 --> 00:04:27.600 align:start position:0% there are a lot of ways that private 00:04:27.600 --> 00:04:29.689 align:start position:0% there are a lot of ways that private information<00:04:27.780> can<00:04:28.139> be<00:04:28.199> leaked<00:04:28.620> and<00:04:29.100> then<00:04:29.220> on 00:04:29.689 --> 00:04:29.699 align:start position:0% information can be leaked and then on 00:04:29.699 --> 00:04:31.310 align:start position:0% information can be leaked and then on the<00:04:29.820> front<00:04:30.060> of<00:04:30.240> Enterprises<00:04:30.780> they've<00:04:31.199> just 00:04:31.310 --> 00:04:31.320 align:start position:0% the front of Enterprises they've just 00:04:31.320 --> 00:04:33.110 align:start position:0% the front of Enterprises they've just full-blown<00:04:31.860> written<00:04:32.460> it<00:04:32.580> off<00:04:32.699> for<00:04:32.940> these 00:04:33.110 --> 00:04:33.120 align:start position:0% full-blown written it off for these 00:04:33.120 --> 00:04:35.030 align:start position:0% full-blown written it off for these reasons<00:04:33.419> a<00:04:33.720> 50<00:04:33.960> transaction<00:04:34.560> fee<00:04:34.919> is<00:04:34.919> a 00:04:35.030 --> 00:04:35.040 align:start position:0% reasons a 50 transaction fee is a 00:04:35.040 --> 00:04:37.189 align:start position:0% reasons a 50 transaction fee is a non-starter<00:04:35.580> and<00:04:35.880> the<00:04:36.000> fact<00:04:36.180> that<00:04:36.479> certain 00:04:37.189 --> 00:04:37.199 align:start position:0% non-starter and the fact that certain 00:04:37.199 --> 00:04:38.810 align:start position:0% non-starter and the fact that certain information<00:04:37.500> is<00:04:38.100> public<00:04:38.340> on<00:04:38.639> a<00:04:38.759> public 00:04:38.810 --> 00:04:38.820 align:start position:0% information is public on a public 00:04:38.820 --> 00:04:40.969 align:start position:0% information is public on a public blockchain<00:04:39.300> again<00:04:39.479> is<00:04:39.660> a<00:04:39.780> non-starter<00:04:40.320> so<00:04:40.740> we 00:04:40.969 --> 00:04:40.979 align:start position:0% blockchain again is a non-starter so we 00:04:40.979 --> 00:04:42.830 align:start position:0% blockchain again is a non-starter so we saw<00:04:41.160> the<00:04:41.340> rise<00:04:41.520> of<00:04:41.699> private<00:04:42.060> blockchains<00:04:42.660> and 00:04:42.830 --> 00:04:42.840 align:start position:0% saw the rise of private blockchains and 00:04:42.840 --> 00:04:45.530 align:start position:0% saw the rise of private blockchains and those<00:04:43.020> were<00:04:43.259> also<00:04:43.560> ruled<00:04:43.919> out<00:04:44.040> as<00:04:44.759> uh<00:04:45.180> well 00:04:45.530 --> 00:04:45.540 align:start position:0% those were also ruled out as uh well 00:04:45.540 --> 00:04:47.330 align:start position:0% those were also ruled out as uh well they<00:04:45.840> are<00:04:45.960> private<00:04:46.440> and<00:04:46.560> scalable<00:04:46.979> to<00:04:47.220> the 00:04:47.330 --> 00:04:47.340 align:start position:0% they are private and scalable to the 00:04:47.340 --> 00:04:49.070 align:start position:0% they are private and scalable to the outside<00:04:47.520> you<00:04:48.000> are<00:04:48.120> still<00:04:48.300> sharing<00:04:48.720> critical 00:04:49.070 --> 00:04:49.080 align:start position:0% outside you are still sharing critical 00:04:49.080 --> 00:04:50.749 align:start position:0% outside you are still sharing critical business<00:04:49.380> information<00:04:49.919> with<00:04:50.520> the<00:04:50.699> other 00:04:50.749 --> 00:04:50.759 align:start position:0% business information with the other 00:04:50.759 --> 00:04:52.610 align:start position:0% business information with the other validators<00:04:51.360> who<00:04:51.780> happen<00:04:51.960> to<00:04:52.080> be<00:04:52.199> competitors 00:04:52.610 --> 00:04:52.620 align:start position:0% validators who happen to be competitors 00:04:52.620 --> 00:04:55.010 align:start position:0% validators who happen to be competitors in<00:04:52.860> the<00:04:52.979> industry<00:04:53.280> so<00:04:53.639> what<00:04:54.180> we've<00:04:54.419> seen<00:04:54.600> is 00:04:55.010 --> 00:04:55.020 align:start position:0% in the industry so what we've seen is 00:04:55.020 --> 00:04:58.189 align:start position:0% in the industry so what we've seen is essentially<00:04:55.560> uh<00:04:56.460> at<00:04:56.880> least<00:04:57.000> until<00:04:57.479> uh 00:04:58.189 --> 00:04:58.199 align:start position:0% essentially uh at least until uh 00:04:58.199 --> 00:05:00.050 align:start position:0% essentially uh at least until uh recently<00:04:58.620> the<00:04:58.979> solutions<00:04:59.340> were<00:04:59.699> just<00:04:59.880> not 00:05:00.050 --> 00:05:00.060 align:start position:0% recently the solutions were just not 00:05:00.060 --> 00:05:02.749 align:start position:0% recently the solutions were just not there 00:05:02.749 --> 00:05:02.759 align:start position:0% 00:05:02.759 --> 00:05:05.749 align:start position:0% so<00:05:03.540> uh<00:05:04.020> really<00:05:04.320> we<00:05:04.620> think<00:05:04.800> that<00:05:05.100> uh<00:05:05.400> we<00:05:05.639> can 00:05:05.749 --> 00:05:05.759 align:start position:0% so uh really we think that uh we can 00:05:05.759 --> 00:05:07.490 align:start position:0% so uh really we think that uh we can summarize<00:05:06.060> this<00:05:06.240> issue<00:05:06.540> uh<00:05:06.900> in<00:05:07.020> a<00:05:07.199> single<00:05:07.380> way 00:05:07.490 --> 00:05:07.500 align:start position:0% summarize this issue uh in a single way 00:05:07.500 --> 00:05:10.550 align:start position:0% summarize this issue uh in a single way that<00:05:08.400> that<00:05:08.460> web3<00:05:09.060> which<00:05:09.660> is<00:05:09.840> mostly<00:05:10.320> become 00:05:10.550 --> 00:05:10.560 align:start position:0% that that web3 which is mostly become 00:05:10.560 --> 00:05:14.270 align:start position:0% that that web3 which is mostly become synonymous<00:05:10.979> with<00:05:11.100> D5<00:05:11.400> uh<00:05:12.680> defy<00:05:13.680> decentralized 00:05:14.270 --> 00:05:14.280 align:start position:0% synonymous with D5 uh defy decentralized 00:05:14.280 --> 00:05:17.150 align:start position:0% synonymous with D5 uh defy decentralized Finance<00:05:14.580> has<00:05:14.820> lost<00:05:15.000> the<00:05:15.240> plot<00:05:15.479> of<00:05:15.720> web<00:05:15.960> 3.<00:05:16.500> uh 00:05:17.150 --> 00:05:17.160 align:start position:0% Finance has lost the plot of web 3. uh 00:05:17.160 --> 00:05:19.730 align:start position:0% Finance has lost the plot of web 3. uh cryptocurrency<00:05:17.820> has<00:05:18.600> become<00:05:19.080> this<00:05:19.320> mechanism 00:05:19.730 --> 00:05:19.740 align:start position:0% cryptocurrency has become this mechanism 00:05:19.740 --> 00:05:21.830 align:start position:0% cryptocurrency has become this mechanism for<00:05:20.040> profit<00:05:20.460> generation<00:05:20.820> whereas<00:05:21.300> that's<00:05:21.600> not 00:05:21.830 --> 00:05:21.840 align:start position:0% for profit generation whereas that's not 00:05:21.840 --> 00:05:23.350 align:start position:0% for profit generation whereas that's not really<00:05:22.080> what<00:05:22.259> Bitcoin<00:05:22.680> was<00:05:22.800> supposed<00:05:22.979> to<00:05:23.160> be 00:05:23.350 --> 00:05:23.360 align:start position:0% really what Bitcoin was supposed to be 00:05:23.360 --> 00:05:25.610 align:start position:0% really what Bitcoin was supposed to be Bitcoin<00:05:24.360> well<00:05:24.720> it<00:05:25.080> has<00:05:25.199> appreciated 00:05:25.610 --> 00:05:25.620 align:start position:0% Bitcoin well it has appreciated 00:05:25.620 --> 00:05:27.590 align:start position:0% Bitcoin well it has appreciated considerably<00:05:26.220> from<00:05:26.520> being<00:05:26.820> worthless<00:05:27.180> back 00:05:27.590 --> 00:05:27.600 align:start position:0% considerably from being worthless back 00:05:27.600 --> 00:05:30.050 align:start position:0% considerably from being worthless back in<00:05:27.840> uh<00:05:28.440> 2000<00:05:28.919> 2009 00:05:30.050 --> 00:05:30.060 align:start position:0% in uh 2000 2009 00:05:30.060 --> 00:05:31.370 align:start position:0% in uh 2000 2009 um it 00:05:31.370 --> 00:05:31.380 align:start position:0% um it 00:05:31.380 --> 00:05:33.830 align:start position:0% um it appreciated<00:05:32.160> because<00:05:32.580> of<00:05:33.060> its<00:05:33.600> Financial 00:05:33.830 --> 00:05:33.840 align:start position:0% appreciated because of its Financial 00:05:33.840 --> 00:05:36.409 align:start position:0% appreciated because of its Financial agency<00:05:34.320> and<00:05:34.560> stability<00:05:34.860> relative<00:05:35.340> to<00:05:35.820> Fiat 00:05:36.409 --> 00:05:36.419 align:start position:0% agency and stability relative to Fiat 00:05:36.419 --> 00:05:39.469 align:start position:0% agency and stability relative to Fiat currencies<00:05:36.840> it<00:05:37.139> was<00:05:37.259> designed<00:05:37.740> to<00:05:38.039> be<00:05:38.479> not 00:05:39.469 --> 00:05:39.479 align:start position:0% currencies it was designed to be not 00:05:39.479 --> 00:05:41.450 align:start position:0% currencies it was designed to be not censorable<00:05:39.960> or<00:05:40.259> manipulatable<00:05:40.919> you<00:05:41.280> can 00:05:41.450 --> 00:05:41.460 align:start position:0% censorable or manipulatable you can 00:05:41.460 --> 00:05:43.610 align:start position:0% censorable or manipulatable you can print<00:05:41.580> more<00:05:41.820> than<00:05:42.000> 21<00:05:42.120> million<00:05:42.720> and<00:05:43.320> the<00:05:43.500> fact 00:05:43.610 --> 00:05:43.620 align:start position:0% print more than 21 million and the fact 00:05:43.620 --> 00:05:45.409 align:start position:0% print more than 21 million and the fact that<00:05:43.860> it<00:05:44.039> appreciated<00:05:44.520> in<00:05:44.820> this<00:05:45.000> economic 00:05:45.409 --> 00:05:45.419 align:start position:0% that it appreciated in this economic 00:05:45.419 --> 00:05:47.930 align:start position:0% that it appreciated in this economic condition<00:05:45.600> is<00:05:46.560> a<00:05:46.860> consequence<00:05:47.280> it<00:05:47.520> wasn't 00:05:47.930 --> 00:05:47.940 align:start position:0% condition is a consequence it wasn't 00:05:47.940 --> 00:05:50.810 align:start position:0% condition is a consequence it wasn't explicitly<00:05:48.660> engineered<00:05:49.199> to<00:05:49.380> go<00:05:49.560> up<00:05:49.800> and<00:05:50.699> then 00:05:50.810 --> 00:05:50.820 align:start position:0% explicitly engineered to go up and then 00:05:50.820 --> 00:05:52.790 align:start position:0% explicitly engineered to go up and then we<00:05:51.060> have<00:05:51.240> protocols<00:05:51.960> like 00:05:52.790 --> 00:05:52.800 align:start position:0% we have protocols like 00:05:52.800 --> 00:05:56.330 align:start position:0% we have protocols like Luna<00:05:53.660> where<00:05:54.660> uh<00:05:55.380> you<00:05:55.680> know<00:05:55.740> there<00:05:55.979> wasn't<00:05:56.100> too 00:05:56.330 --> 00:05:56.340 align:start position:0% Luna where uh you know there wasn't too 00:05:56.340 --> 00:05:58.010 align:start position:0% Luna where uh you know there wasn't too much<00:05:56.460> Innovation<00:05:56.880> on<00:05:57.300> the<00:05:57.419> side<00:05:57.600> of<00:05:57.840> the 00:05:58.010 --> 00:05:58.020 align:start position:0% much Innovation on the side of the 00:05:58.020 --> 00:05:59.390 align:start position:0% much Innovation on the side of the decentralization<00:05:58.620> or<00:05:58.860> peer-to-peer 00:05:59.390 --> 00:05:59.400 align:start position:0% decentralization or peer-to-peer 00:05:59.400 --> 00:06:01.129 align:start position:0% decentralization or peer-to-peer networks<00:05:59.699> or<00:05:59.820> cryptography<00:06:00.479> but<00:06:00.840> they<00:06:01.020> did 00:06:01.129 --> 00:06:01.139 align:start position:0% networks or cryptography but they did 00:06:01.139 --> 00:06:03.110 align:start position:0% networks or cryptography but they did present<00:06:01.500> uh<00:06:01.860> you<00:06:01.979> know<00:06:02.100> a<00:06:02.220> novel<00:06:02.460> algorithmic 00:06:03.110 --> 00:06:03.120 align:start position:0% present uh you know a novel algorithmic 00:06:03.120 --> 00:06:05.150 align:start position:0% present uh you know a novel algorithmic stable<00:06:03.419> coin<00:06:03.720> which<00:06:04.080> turned<00:06:04.620> out<00:06:04.680> to<00:06:04.860> be<00:06:04.979> a 00:06:05.150 --> 00:06:05.160 align:start position:0% stable coin which turned out to be a 00:06:05.160 --> 00:06:07.270 align:start position:0% stable coin which turned out to be a financial<00:06:05.280> weapon<00:06:05.759> of<00:06:05.880> mass<00:06:06.000> destruction 00:06:07.270 --> 00:06:07.280 align:start position:0% financial weapon of mass destruction 00:06:07.280 --> 00:06:10.129 align:start position:0% financial weapon of mass destruction a<00:06:08.280> lot<00:06:08.400> of<00:06:08.520> capital<00:06:08.699> was<00:06:09.060> destroyed<00:06:09.419> both<00:06:09.660> for 00:06:10.129 --> 00:06:10.139 align:start position:0% a lot of capital was destroyed both for 00:06:10.139 --> 00:06:12.110 align:start position:0% a lot of capital was destroyed both for retail<00:06:10.560> investors<00:06:11.160> and<00:06:11.520> institutional 00:06:12.110 --> 00:06:12.120 align:start position:0% retail investors and institutional 00:06:12.120 --> 00:06:14.749 align:start position:0% retail investors and institutional investors<00:06:12.600> lost<00:06:13.080> a<00:06:13.320> lot<00:06:13.500> of<00:06:13.680> money<00:06:13.800> and<00:06:14.520> not 00:06:14.749 --> 00:06:14.759 align:start position:0% investors lost a lot of money and not 00:06:14.759 --> 00:06:16.189 align:start position:0% investors lost a lot of money and not only<00:06:14.880> is<00:06:15.060> this<00:06:15.180> bad<00:06:15.360> for<00:06:15.539> the<00:06:15.720> industry<00:06:15.960> just 00:06:16.189 --> 00:06:16.199 align:start position:0% only is this bad for the industry just 00:06:16.199 --> 00:06:18.590 align:start position:0% only is this bad for the industry just because<00:06:16.320> they're<00:06:16.680> resources<00:06:17.280> that<00:06:17.759> um<00:06:18.000> are 00:06:18.590 --> 00:06:18.600 align:start position:0% because they're resources that um are 00:06:18.600 --> 00:06:20.689 align:start position:0% because they're resources that um are suddenly<00:06:19.259> uh<00:06:19.560> taken<00:06:19.860> away<00:06:19.979> it<00:06:20.520> actually 00:06:20.689 --> 00:06:20.699 align:start position:0% suddenly uh taken away it actually 00:06:20.699 --> 00:06:22.309 align:start position:0% suddenly uh taken away it actually causes<00:06:21.120> a<00:06:21.300> recession<00:06:21.600> in<00:06:22.139> uh 00:06:22.309 --> 00:06:22.319 align:start position:0% causes a recession in uh 00:06:22.319 --> 00:06:23.749 align:start position:0% causes a recession in uh decentralization<00:06:22.979> in<00:06:23.220> this<00:06:23.340> industry<00:06:23.580> and 00:06:23.749 --> 00:06:23.759 align:start position:0% decentralization in this industry and 00:06:23.759 --> 00:06:25.550 align:start position:0% decentralization in this industry and this<00:06:23.880> is<00:06:24.000> I<00:06:24.120> think<00:06:24.240> something<00:06:24.539> even<00:06:24.780> vitalik 00:06:25.550 --> 00:06:25.560 align:start position:0% this is I think something even vitalik 00:06:25.560 --> 00:06:28.610 align:start position:0% this is I think something even vitalik has<00:06:25.740> brought<00:06:25.860> up<00:06:25.979> uh<00:06:26.699> as<00:06:27.000> we<00:06:27.419> uh<00:06:27.900> create<00:06:28.139> these 00:06:28.610 --> 00:06:28.620 align:start position:0% has brought up uh as we uh create these 00:06:28.620 --> 00:06:31.670 align:start position:0% has brought up uh as we uh create these insane<00:06:29.039> volatile<00:06:29.580> uh<00:06:30.180> liquidity<00:06:30.720> events<00:06:31.139> uh 00:06:31.670 --> 00:06:31.680 align:start position:0% insane volatile uh liquidity events uh 00:06:31.680 --> 00:06:33.710 align:start position:0% insane volatile uh liquidity events uh governments<00:06:32.220> notice<00:06:32.580> and<00:06:32.880> they<00:06:33.120> decide<00:06:33.419> their 00:06:33.710 --> 00:06:33.720 align:start position:0% governments notice and they decide their 00:06:33.720 --> 00:06:36.230 align:start position:0% governments notice and they decide their mandate<00:06:34.080> is<00:06:34.380> to<00:06:34.740> exert<00:06:35.160> force<00:06:35.520> or<00:06:35.699> exert<00:06:36.060> power 00:06:36.230 --> 00:06:36.240 align:start position:0% mandate is to exert force or exert power 00:06:36.240 --> 00:06:37.490 align:start position:0% mandate is to exert force or exert power over 00:06:37.490 --> 00:06:37.500 align:start position:0% over 00:06:37.500 --> 00:06:40.670 align:start position:0% over um these<00:06:38.160> industries<00:06:38.520> so<00:06:38.880> as<00:06:39.479> we<00:06:39.780> create<00:06:40.199> more 00:06:40.670 --> 00:06:40.680 align:start position:0% um these industries so as we create more 00:06:40.680 --> 00:06:43.129 align:start position:0% um these industries so as we create more of<00:06:40.919> these<00:06:41.340> opportunities<00:06:42.300> for<00:06:42.600> them<00:06:42.720> to 00:06:43.129 --> 00:06:43.139 align:start position:0% of these opportunities for them to 00:06:43.139 --> 00:06:44.809 align:start position:0% of these opportunities for them to notice<00:06:43.680> uh 00:06:44.809 --> 00:06:44.819 align:start position:0% notice uh 00:06:44.819 --> 00:06:48.110 align:start position:0% notice uh we<00:06:45.419> lose<00:06:45.600> decentralization<00:06:46.319> so 00:06:48.110 --> 00:06:48.120 align:start position:0% we lose decentralization so 00:06:48.120 --> 00:06:52.189 align:start position:0% we lose decentralization so uh<00:06:48.840> essentially<00:06:49.259> what<00:06:49.800> we<00:06:50.039> want<00:06:50.280> to<00:06:50.520> say<00:06:50.940> uh<00:06:51.720> or 00:06:52.189 --> 00:06:52.199 align:start position:0% uh essentially what we want to say uh or 00:06:52.199 --> 00:06:55.550 align:start position:0% uh essentially what we want to say uh or we<00:06:52.440> want<00:06:52.680> to<00:06:52.860> see<00:06:53.039> to<00:06:53.460> have<00:06:53.819> web3<00:06:54.240> grow<00:06:54.600> uh<00:06:55.199> to 00:06:55.550 --> 00:06:55.560 align:start position:0% we want to see to have web3 grow uh to 00:06:55.560 --> 00:06:57.409 align:start position:0% we want to see to have web3 grow uh to where<00:06:55.800> I<00:06:56.100> think<00:06:56.220> we<00:06:56.400> all<00:06:56.520> see<00:06:56.759> it<00:06:56.880> being<00:06:57.060> in<00:06:57.300> the 00:06:57.409 --> 00:06:57.419 align:start position:0% where I think we all see it being in the 00:06:57.419 --> 00:06:59.390 align:start position:0% where I think we all see it being in the future<00:06:57.539> is<00:06:58.139> for<00:06:58.380> web3<00:06:58.680> to<00:06:58.919> break<00:06:59.039> out<00:06:59.160> of 00:06:59.390 --> 00:06:59.400 align:start position:0% future is for web3 to break out of 00:06:59.400 --> 00:07:00.650 align:start position:0% future is for web3 to break out of decentralized<00:06:59.940> finance<00:07:00.240> and<00:07:00.360> become 00:07:00.650 --> 00:07:00.660 align:start position:0% decentralized finance and become 00:07:00.660 --> 00:07:03.409 align:start position:0% decentralized finance and become something<00:07:00.900> more<00:07:01.620> than<00:07:01.800> just<00:07:02.160> a<00:07:02.520> monetary<00:07:03.060> tool 00:07:03.409 --> 00:07:03.419 align:start position:0% something more than just a monetary tool 00:07:03.419 --> 00:07:04.909 align:start position:0% something more than just a monetary tool and<00:07:03.840> we<00:07:04.020> kind<00:07:04.139> of<00:07:04.199> see<00:07:04.319> that<00:07:04.500> with<00:07:04.740> like 00:07:04.909 --> 00:07:04.919 align:start position:0% and we kind of see that with like 00:07:04.919 --> 00:07:06.830 align:start position:0% and we kind of see that with like decentralized<00:07:05.400> science<00:07:05.699> decentralized<00:07:06.539> uh 00:07:06.830 --> 00:07:06.840 align:start position:0% decentralized science decentralized uh 00:07:06.840 --> 00:07:10.070 align:start position:0% decentralized science decentralized uh social<00:07:07.080> media<00:07:07.699> some<00:07:08.699> governance<00:07:09.120> tools<00:07:09.539> are 00:07:10.070 --> 00:07:10.080 align:start position:0% social media some governance tools are 00:07:10.080 --> 00:07:12.110 align:start position:0% social media some governance tools are definitely<00:07:10.680> more<00:07:11.280> focused<00:07:11.639> on<00:07:11.819> information 00:07:12.110 --> 00:07:12.120 align:start position:0% definitely more focused on information 00:07:12.120 --> 00:07:14.210 align:start position:0% definitely more focused on information rather<00:07:12.720> than<00:07:12.900> the<00:07:13.080> financial<00:07:13.259> aspect<00:07:13.800> but 00:07:14.210 --> 00:07:14.220 align:start position:0% rather than the financial aspect but 00:07:14.220 --> 00:07:16.070 align:start position:0% rather than the financial aspect but what<00:07:14.699> we<00:07:14.819> really<00:07:14.940> believe<00:07:15.240> is<00:07:15.479> that<00:07:15.720> zero 00:07:16.070 --> 00:07:16.080 align:start position:0% what we really believe is that zero 00:07:16.080 --> 00:07:17.270 align:start position:0% what we really believe is that zero knowledge<00:07:16.319> cryptography<00:07:16.860> is<00:07:16.979> going<00:07:17.100> to<00:07:17.220> cause 00:07:17.270 --> 00:07:17.280 align:start position:0% knowledge cryptography is going to cause 00:07:17.280 --> 00:07:20.150 align:start position:0% knowledge cryptography is going to cause an<00:07:17.520> explosion<00:07:17.880> in<00:07:18.060> these<00:07:18.240> tools<00:07:18.900> so<00:07:20.099> um 00:07:20.150 --> 00:07:20.160 align:start position:0% an explosion in these tools so um 00:07:20.160 --> 00:07:23.629 align:start position:0% an explosion in these tools so um specifically<00:07:20.759> you<00:07:21.300> might<00:07:21.539> if<00:07:21.780> if<00:07:22.080> you're<00:07:23.039> um<00:07:23.039> a 00:07:23.629 --> 00:07:23.639 align:start position:0% specifically you might if if you're um a 00:07:23.639 --> 00:07:25.730 align:start position:0% specifically you might if if you're um a little<00:07:23.699> unfamiliar<00:07:24.240> with<00:07:24.419> zero<00:07:24.780> knowledge<00:07:25.080> uh 00:07:25.730 --> 00:07:25.740 align:start position:0% little unfamiliar with zero knowledge uh 00:07:25.740 --> 00:07:28.850 align:start position:0% little unfamiliar with zero knowledge uh you<00:07:26.220> might<00:07:26.340> think<00:07:26.580> of<00:07:26.940> tornado<00:07:27.419> cash<00:07:27.720> and<00:07:28.380> uh 00:07:28.850 --> 00:07:28.860 align:start position:0% you might think of tornado cash and uh 00:07:28.860 --> 00:07:31.189 align:start position:0% you might think of tornado cash and uh how<00:07:29.220> zero<00:07:29.880> knowledge<00:07:30.120> can<00:07:30.300> be<00:07:30.479> used<00:07:30.660> as<00:07:30.840> a<00:07:30.960> tool 00:07:31.189 --> 00:07:31.199 align:start position:0% how zero knowledge can be used as a tool 00:07:31.199 --> 00:07:32.809 align:start position:0% how zero knowledge can be used as a tool of<00:07:31.259> anonymity<00:07:31.800> or<00:07:32.220> potentially<00:07:32.580> even 00:07:32.809 --> 00:07:32.819 align:start position:0% of anonymity or potentially even 00:07:32.819 --> 00:07:34.550 align:start position:0% of anonymity or potentially even subversion<00:07:33.479> of<00:07:33.599> central<00:07:33.960> Authority<00:07:34.440> or 00:07:34.550 --> 00:07:34.560 align:start position:0% subversion of central Authority or 00:07:34.560 --> 00:07:36.409 align:start position:0% subversion of central Authority or surveillance<00:07:35.039> however<00:07:35.699> it's<00:07:36.180> actually 00:07:36.409 --> 00:07:36.419 align:start position:0% surveillance however it's actually 00:07:36.419 --> 00:07:39.350 align:start position:0% surveillance however it's actually important<00:07:36.900> to<00:07:37.080> note<00:07:37.199> that<00:07:38.039> um<00:07:38.039> at<00:07:38.880> pretty<00:07:39.240> much 00:07:39.350 --> 00:07:39.360 align:start position:0% important to note that um at pretty much 00:07:39.360 --> 00:07:41.150 align:start position:0% important to note that um at pretty much its<00:07:39.720> Inception<00:07:40.139> uh<00:07:40.680> one<00:07:40.860> of<00:07:40.979> the<00:07:41.039> thought 00:07:41.150 --> 00:07:41.160 align:start position:0% its Inception uh one of the thought 00:07:41.160 --> 00:07:44.089 align:start position:0% its Inception uh one of the thought experiments<00:07:41.759> for<00:07:42.720> um<00:07:43.080> justifying<00:07:43.800> the<00:07:43.919> need 00:07:44.089 --> 00:07:44.099 align:start position:0% experiments for um justifying the need 00:07:44.099 --> 00:07:45.950 align:start position:0% experiments for um justifying the need for<00:07:44.280> zero<00:07:44.580> knowledge<00:07:44.819> was<00:07:45.000> denuclearization 00:07:45.950 --> 00:07:45.960 align:start position:0% for zero knowledge was denuclearization 00:07:45.960 --> 00:07:49.129 align:start position:0% for zero knowledge was denuclearization between<00:07:46.680> bitter<00:07:47.340> enemies<00:07:48.120> United<00:07:48.539> States<00:07:48.900> and 00:07:49.129 --> 00:07:49.139 align:start position:0% between bitter enemies United States and 00:07:49.139 --> 00:07:51.589 align:start position:0% between bitter enemies United States and the<00:07:49.319> Soviet<00:07:49.620> Union<00:07:50.160> they<00:07:50.819> needed<00:07:51.060> to<00:07:51.180> prove<00:07:51.479> to 00:07:51.589 --> 00:07:51.599 align:start position:0% the Soviet Union they needed to prove to 00:07:51.599 --> 00:07:53.770 align:start position:0% the Soviet Union they needed to prove to each<00:07:51.780> other<00:07:51.900> that<00:07:52.680> that<00:07:52.800> they<00:07:53.220> were<00:07:53.400> actually 00:07:53.770 --> 00:07:53.780 align:start position:0% each other that that they were actually 00:07:53.780 --> 00:07:56.089 align:start position:0% each other that that they were actually denuclearizing<00:07:54.780> but<00:07:55.560> they<00:07:55.680> didn't<00:07:55.800> want<00:07:55.979> to 00:07:56.089 --> 00:07:56.099 align:start position:0% denuclearizing but they didn't want to 00:07:56.099 --> 00:07:57.529 align:start position:0% denuclearizing but they didn't want to send<00:07:56.340> uh<00:07:56.759> or<00:07:56.940> they<00:07:57.000> didn't<00:07:57.180> want<00:07:57.300> to<00:07:57.360> allow 00:07:57.529 --> 00:07:57.539 align:start position:0% send uh or they didn't want to allow 00:07:57.539 --> 00:07:58.850 align:start position:0% send uh or they didn't want to allow inspectors<00:07:58.020> from<00:07:58.199> each<00:07:58.319> other's<00:07:58.560> countries 00:07:58.850 --> 00:07:58.860 align:start position:0% inspectors from each other's countries 00:07:58.860 --> 00:08:02.029 align:start position:0% inspectors from each other's countries into<00:07:59.099> their<00:07:59.280> nuclear<00:07:59.639> bases<00:08:00.000> so<00:08:00.780> to<00:08:01.380> have<00:08:01.620> uh 00:08:02.029 --> 00:08:02.039 align:start position:0% into their nuclear bases so to have uh 00:08:02.039 --> 00:08:04.070 align:start position:0% into their nuclear bases so to have uh disjointed<00:08:02.580> or<00:08:02.699> adversarial<00:08:03.360> parties<00:08:03.720> that 00:08:04.070 --> 00:08:04.080 align:start position:0% disjointed or adversarial parties that 00:08:04.080 --> 00:08:06.890 align:start position:0% disjointed or adversarial parties that are<00:08:04.319> able<00:08:04.680> to<00:08:04.940> coordinate<00:08:05.940> and<00:08:06.419> prove<00:08:06.780> things 00:08:06.890 --> 00:08:06.900 align:start position:0% are able to coordinate and prove things 00:08:06.900 --> 00:08:08.450 align:start position:0% are able to coordinate and prove things to<00:08:07.139> each<00:08:07.199> other<00:08:07.319> is<00:08:07.620> incredibly<00:08:08.039> valuable 00:08:08.450 --> 00:08:08.460 align:start position:0% to each other is incredibly valuable 00:08:08.460 --> 00:08:10.969 align:start position:0% to each other is incredibly valuable both<00:08:08.699> in<00:08:09.000> the<00:08:09.180> decentralized<00:08:09.660> context<00:08:10.199> uh 00:08:10.969 --> 00:08:10.979 align:start position:0% both in the decentralized context uh 00:08:10.979 --> 00:08:11.930 align:start position:0% both in the decentralized context uh where<00:08:11.099> you<00:08:11.280> know<00:08:11.400> parties<00:08:11.639> are<00:08:11.819> just 00:08:11.930 --> 00:08:11.940 align:start position:0% where you know parties are just 00:08:11.940 --> 00:08:13.790 align:start position:0% where you know parties are just disinterested<00:08:12.539> and<00:08:13.080> perhaps<00:08:13.380> in<00:08:13.620> more 00:08:13.790 --> 00:08:13.800 align:start position:0% disinterested and perhaps in more 00:08:13.800 --> 00:08:15.830 align:start position:0% disinterested and perhaps in more centralized<00:08:14.280> contexts<00:08:14.819> like<00:08:15.180> the 00:08:15.830 --> 00:08:15.840 align:start position:0% centralized contexts like the 00:08:15.840 --> 00:08:17.270 align:start position:0% centralized contexts like the relationship<00:08:16.199> that<00:08:16.440> individuals<00:08:16.919> often<00:08:17.220> have 00:08:17.270 --> 00:08:17.280 align:start position:0% relationship that individuals often have 00:08:17.280 --> 00:08:18.770 align:start position:0% relationship that individuals often have with<00:08:17.520> Central<00:08:17.699> authorities<00:08:18.240> where 00:08:18.770 --> 00:08:18.780 align:start position:0% with Central authorities where 00:08:18.780 --> 00:08:21.050 align:start position:0% with Central authorities where incentives<00:08:19.319> are<00:08:19.500> very<00:08:19.740> much<00:08:19.860> misaligned<00:08:20.460> we 00:08:21.050 --> 00:08:21.060 align:start position:0% incentives are very much misaligned we 00:08:21.060 --> 00:08:23.689 align:start position:0% incentives are very much misaligned we can<00:08:21.180> start<00:08:21.479> to<00:08:21.660> build<00:08:22.139> solutions<00:08:22.680> that<00:08:23.220> kind 00:08:23.689 --> 00:08:23.699 align:start position:0% can start to build solutions that kind 00:08:23.699 --> 00:08:27.290 align:start position:0% can start to build solutions that kind of<00:08:23.819> bridge<00:08:24.060> that<00:08:24.479> Gap<00:08:25.139> so<00:08:25.800> going 00:08:27.290 --> 00:08:27.300 align:start position:0% of bridge that Gap so going 00:08:27.300 --> 00:08:31.070 align:start position:0% of bridge that Gap so going into<00:08:27.840> the<00:08:28.139> specifics<00:08:28.860> again<00:08:29.819> we<00:08:30.180> can<00:08:30.360> uh<00:08:30.720> on 00:08:31.070 --> 00:08:31.080 align:start position:0% into the specifics again we can uh on 00:08:31.080 --> 00:08:33.409 align:start position:0% into the specifics again we can uh on one<00:08:31.199> end<00:08:31.319> we<00:08:31.680> have<00:08:31.740> tornado<00:08:32.219> cash<00:08:32.520> coin<00:08:33.060> mixers 00:08:33.409 --> 00:08:33.419 align:start position:0% one end we have tornado cash coin mixers 00:08:33.419 --> 00:08:35.389 align:start position:0% one end we have tornado cash coin mixers which<00:08:33.779> are<00:08:34.020> alternate<00:08:34.740> tools<00:08:34.919> of<00:08:34.979> anonymity 00:08:35.389 --> 00:08:35.399 align:start position:0% which are alternate tools of anonymity 00:08:35.399 --> 00:08:37.670 align:start position:0% which are alternate tools of anonymity and<00:08:35.940> on<00:08:36.300> the<00:08:36.479> exact<00:08:36.779> opposite<00:08:37.260> end<00:08:37.440> of<00:08:37.620> the 00:08:37.670 --> 00:08:37.680 align:start position:0% and on the exact opposite end of the 00:08:37.680 --> 00:08:40.190 align:start position:0% and on the exact opposite end of the spectrum<00:08:38.039> with<00:08:38.339> very<00:08:38.580> similar<00:08:38.880> code<00:08:39.120> uh<00:08:39.899> we 00:08:40.190 --> 00:08:40.200 align:start position:0% spectrum with very similar code uh we 00:08:40.200 --> 00:08:42.949 align:start position:0% spectrum with very similar code uh we have<00:08:40.440> uh<00:08:40.919> tools<00:08:41.339> of<00:08:41.459> of<00:08:41.760> compliance<00:08:42.360> know<00:08:42.719> your 00:08:42.949 --> 00:08:42.959 align:start position:0% have uh tools of of compliance know your 00:08:42.959 --> 00:08:45.050 align:start position:0% have uh tools of of compliance know your customer<00:08:43.140> anti-money<00:08:43.800> laundering 00:08:45.050 --> 00:08:45.060 align:start position:0% customer anti-money laundering 00:08:45.060 --> 00:08:49.250 align:start position:0% customer anti-money laundering um<00:08:45.180> and<00:08:45.720> uh<00:08:46.200> moving<00:08:46.560> on<00:08:46.680> uh<00:08:47.640> there's<00:08:48.300> also<00:08:48.720> uh 00:08:49.250 --> 00:08:49.260 align:start position:0% um and uh moving on uh there's also uh 00:08:49.260 --> 00:08:50.930 align:start position:0% um and uh moving on uh there's also uh and<00:08:49.380> I'm<00:08:49.620> sure<00:08:49.800> a<00:08:50.040> lot<00:08:50.100> of<00:08:50.160> you<00:08:50.279> have<00:08:50.399> seen<00:08:50.640> uh 00:08:50.930 --> 00:08:50.940 align:start position:0% and I'm sure a lot of you have seen uh 00:08:50.940 --> 00:08:52.310 align:start position:0% and I'm sure a lot of you have seen uh like<00:08:51.120> the<00:08:51.240> temporary<00:08:51.480> Anonymous<00:08:51.899> Zone<00:08:52.140> all 00:08:52.310 --> 00:08:52.320 align:start position:0% like the temporary Anonymous Zone all 00:08:52.320 --> 00:08:53.630 align:start position:0% like the temporary Anonymous Zone all the<00:08:52.440> semaphore<00:08:52.800> stuff 00:08:53.630 --> 00:08:53.640 align:start position:0% the semaphore stuff 00:08:53.640 --> 00:08:56.329 align:start position:0% the semaphore stuff um<00:08:53.700> there's<00:08:54.240> the<00:08:54.720> ability<00:08:54.959> to<00:08:55.260> create<00:08:55.380> an 00:08:56.329 --> 00:08:56.339 align:start position:0% um there's the ability to create an 00:08:56.339 --> 00:08:58.790 align:start position:0% um there's the ability to create an anonymous<00:08:56.760> social<00:08:57.000> media<00:08:57.420> uh<00:08:57.899> programs<00:08:58.560> that 00:08:58.790 --> 00:08:58.800 align:start position:0% anonymous social media uh programs that 00:08:58.800 --> 00:09:01.670 align:start position:0% anonymous social media uh programs that again<00:08:58.980> allow<00:08:59.720> coordination<00:09:00.720> without<00:09:01.200> any 00:09:01.670 --> 00:09:01.680 align:start position:0% again allow coordination without any 00:09:01.680 --> 00:09:04.730 align:start position:0% again allow coordination without any sort<00:09:01.860> of<00:09:01.980> central<00:09:02.100> Authority<00:09:02.600> and<00:09:03.600> uh<00:09:04.140> on<00:09:04.500> a 00:09:04.730 --> 00:09:04.740 align:start position:0% sort of central Authority and uh on a 00:09:04.740 --> 00:09:07.190 align:start position:0% sort of central Authority and uh on a completely<00:09:05.040> unrelated<00:09:05.760> vertical<00:09:06.180> we<00:09:06.959> can 00:09:07.190 --> 00:09:07.200 align:start position:0% completely unrelated vertical we can 00:09:07.200 --> 00:09:09.829 align:start position:0% completely unrelated vertical we can construct<00:09:07.800> iff<00:09:08.220> signals<00:09:08.820> which<00:09:09.060> many<00:09:09.600> of<00:09:09.720> you 00:09:09.829 --> 00:09:09.839 align:start position:0% construct iff signals which many of you 00:09:09.839 --> 00:09:11.150 align:start position:0% construct iff signals which many of you probably<00:09:09.959> know<00:09:10.500> you<00:09:10.500> don't<00:09:10.680> know<00:09:10.860> what<00:09:11.040> those 00:09:11.150 --> 00:09:11.160 align:start position:0% probably know you don't know what those 00:09:11.160 --> 00:09:13.070 align:start position:0% probably know you don't know what those are<00:09:11.339> but<00:09:11.580> essentially<00:09:12.080> identification 00:09:13.070 --> 00:09:13.080 align:start position:0% are but essentially identification 00:09:13.080 --> 00:09:15.050 align:start position:0% are but essentially identification Friend<00:09:13.440> or<00:09:13.680> Foe<00:09:13.980> signals<00:09:14.399> go<00:09:14.519> on<00:09:14.700> combat 00:09:15.050 --> 00:09:15.060 align:start position:0% Friend or Foe signals go on combat 00:09:15.060 --> 00:09:16.970 align:start position:0% Friend or Foe signals go on combat aircraft<00:09:15.420> and<00:09:15.779> uh<00:09:16.380> when<00:09:16.560> they're<00:09:16.680> flying 00:09:16.970 --> 00:09:16.980 align:start position:0% aircraft and uh when they're flying 00:09:16.980 --> 00:09:18.650 align:start position:0% aircraft and uh when they're flying through<00:09:17.040> an<00:09:17.220> airspace<00:09:17.580> you<00:09:18.240> can<00:09:18.360> basically 00:09:18.650 --> 00:09:18.660 align:start position:0% through an airspace you can basically 00:09:18.660 --> 00:09:20.990 align:start position:0% through an airspace you can basically with<00:09:19.440> a<00:09:19.620> zero<00:09:19.980> knowledge<00:09:20.160> iff<00:09:20.519> you<00:09:20.820> would 00:09:20.990 --> 00:09:21.000 align:start position:0% with a zero knowledge iff you would 00:09:21.000 --> 00:09:22.970 align:start position:0% with a zero knowledge iff you would prove<00:09:21.300> that<00:09:21.480> you're<00:09:21.839> allowed<00:09:22.440> to<00:09:22.560> be<00:09:22.680> flying 00:09:22.970 --> 00:09:22.980 align:start position:0% prove that you're allowed to be flying 00:09:22.980 --> 00:09:24.650 align:start position:0% prove that you're allowed to be flying in<00:09:23.100> that<00:09:23.220> airspace<00:09:23.580> without<00:09:24.060> actually 00:09:24.650 --> 00:09:24.660 align:start position:0% in that airspace without actually 00:09:24.660 --> 00:09:27.590 align:start position:0% in that airspace without actually revealing<00:09:25.320> the<00:09:25.560> details<00:09:25.920> of<00:09:26.040> that<00:09:26.160> mission 00:09:27.590 --> 00:09:27.600 align:start position:0% revealing the details of that mission 00:09:27.600 --> 00:09:29.329 align:start position:0% revealing the details of that mission and<00:09:27.959> we<00:09:28.320> can 00:09:29.329 --> 00:09:29.339 align:start position:0% and we can 00:09:29.339 --> 00:09:29.870 align:start position:0% and we can um 00:09:29.870 --> 00:09:29.880 align:start position:0% um 00:09:29.880 --> 00:09:33.170 align:start position:0% um start<00:09:30.480> to<00:09:30.720> fortify<00:09:31.620> uh<00:09:31.860> trustless<00:09:32.820> Computing 00:09:33.170 --> 00:09:33.180 align:start position:0% start to fortify uh trustless Computing 00:09:33.180 --> 00:09:35.870 align:start position:0% start to fortify uh trustless Computing even<00:09:33.300> bulletproof<00:09:33.959> hosting<00:09:34.320> and<00:09:35.279> again<00:09:35.580> on 00:09:35.870 --> 00:09:35.880 align:start position:0% even bulletproof hosting and again on 00:09:35.880 --> 00:09:38.650 align:start position:0% even bulletproof hosting and again on the<00:09:36.240> other<00:09:36.360> side<00:09:36.480> of<00:09:36.720> things<00:09:37.100> we<00:09:38.100> can<00:09:38.279> be 00:09:38.650 --> 00:09:38.660 align:start position:0% the other side of things we can be 00:09:38.660 --> 00:09:41.329 align:start position:0% the other side of things we can be fortifying<00:09:39.660> uh<00:09:40.380> centralized<00:09:40.920> processes 00:09:41.329 --> 00:09:41.339 align:start position:0% fortifying uh centralized processes 00:09:41.339 --> 00:09:44.990 align:start position:0% fortifying uh centralized processes specific<00:09:41.880> Ally<00:09:42.180> let's<00:09:42.420> take<00:09:43.080> IRS<00:09:43.760> there's<00:09:44.760> a 00:09:44.990 --> 00:09:45.000 align:start position:0% specific Ally let's take IRS there's a 00:09:45.000 --> 00:09:46.370 align:start position:0% specific Ally let's take IRS there's a little<00:09:45.060> bit<00:09:45.240> of<00:09:45.360> entropy<00:09:45.779> that<00:09:45.899> goes<00:09:46.080> into<00:09:46.200> the 00:09:46.370 --> 00:09:46.380 align:start position:0% little bit of entropy that goes into the 00:09:46.380 --> 00:09:47.990 align:start position:0% little bit of entropy that goes into the audit<00:09:46.740> lottery<00:09:46.920> so<00:09:47.279> we<00:09:47.580> want<00:09:47.640> to<00:09:47.760> make<00:09:47.880> sure 00:09:47.990 --> 00:09:48.000 align:start position:0% audit lottery so we want to make sure 00:09:48.000 --> 00:09:50.210 align:start position:0% audit lottery so we want to make sure that<00:09:48.180> that<00:09:48.360> is<00:09:48.660> uh<00:09:48.899> that<00:09:49.380> entropy<00:09:49.800> is<00:09:49.920> sampled 00:09:50.210 --> 00:09:50.220 align:start position:0% that that is uh that entropy is sampled 00:09:50.220 --> 00:09:52.430 align:start position:0% that that is uh that entropy is sampled correctly<00:09:50.580> as<00:09:51.120> well<00:09:51.240> all<00:09:51.600> of<00:09:51.720> the<00:09:51.899> parameters 00:09:52.430 --> 00:09:52.440 align:start position:0% correctly as well all of the parameters 00:09:52.440 --> 00:09:54.170 align:start position:0% correctly as well all of the parameters that<00:09:52.680> are<00:09:52.800> used<00:09:52.920> to<00:09:53.220> choose<00:09:53.580> how<00:09:53.820> someone<00:09:53.940> is 00:09:54.170 --> 00:09:54.180 align:start position:0% that are used to choose how someone is 00:09:54.180 --> 00:09:55.550 align:start position:0% that are used to choose how someone is audited<00:09:54.480> we<00:09:54.899> want<00:09:55.019> to<00:09:55.080> make<00:09:55.200> sure<00:09:55.260> that<00:09:55.440> those 00:09:55.550 --> 00:09:55.560 align:start position:0% audited we want to make sure that those 00:09:55.560 --> 00:09:58.490 align:start position:0% audited we want to make sure that those are<00:09:55.740> all<00:09:55.860> correctly<00:09:56.279> chosen<00:09:56.940> uh<00:09:57.480> improved<00:09:57.959> and 00:09:58.490 --> 00:09:58.500 align:start position:0% are all correctly chosen uh improved and 00:09:58.500 --> 00:09:59.690 align:start position:0% are all correctly chosen uh improved and then<00:09:58.680> finally 00:09:59.690 --> 00:09:59.700 align:start position:0% then finally 00:09:59.700 --> 00:10:00.290 align:start position:0% then finally um 00:10:00.290 --> 00:10:00.300 align:start position:0% um 00:10:00.300 --> 00:10:03.110 align:start position:0% um something<00:10:00.779> that<00:10:01.140> is<00:10:01.800> not<00:10:02.160> so<00:10:02.399> new<00:10:02.580> chain<00:10:02.940> link 00:10:03.110 --> 00:10:03.120 align:start position:0% something that is not so new chain link 00:10:03.120 --> 00:10:04.370 align:start position:0% something that is not so new chain link has<00:10:03.360> been<00:10:03.480> working<00:10:03.600> on<00:10:03.720> proof<00:10:03.959> of<00:10:04.019> reserves 00:10:04.370 --> 00:10:04.380 align:start position:0% has been working on proof of reserves 00:10:04.380 --> 00:10:06.050 align:start position:0% has been working on proof of reserves for<00:10:04.500> a<00:10:04.620> while<00:10:04.680> but<00:10:04.860> facility<00:10:05.220> takes<00:10:05.519> the<00:10:05.700> uh 00:10:06.050 --> 00:10:06.060 align:start position:0% for a while but facility takes the uh 00:10:06.060 --> 00:10:08.870 align:start position:0% for a while but facility takes the uh unbanking<00:10:06.600> of<00:10:06.779> Pop 00:10:08.870 --> 00:10:08.880 align:start position:0% unbanking of Pop 00:10:08.880 --> 00:10:11.210 align:start position:0% unbanking of Pop again<00:10:09.660> on<00:10:09.839> the<00:10:09.959> other<00:10:10.019> hand<00:10:10.140> we<00:10:10.320> can<00:10:10.440> have<00:10:10.920> a 00:10:11.210 --> 00:10:11.220 align:start position:0% again on the other hand we can have a 00:10:11.220 --> 00:10:13.970 align:start position:0% again on the other hand we can have a centralized<00:10:11.640> Supply<00:10:11.880> chains<00:10:12.360> so<00:10:12.600> uh<00:10:13.380> take<00:10:13.680> the 00:10:13.970 --> 00:10:13.980 align:start position:0% centralized Supply chains so uh take the 00:10:13.980 --> 00:10:15.949 align:start position:0% centralized Supply chains so uh take the distribution<00:10:14.580> let's<00:10:14.940> say<00:10:15.060> of<00:10:15.240> alcohol<00:10:15.480> when 00:10:15.949 --> 00:10:15.959 align:start position:0% distribution let's say of alcohol when 00:10:15.959 --> 00:10:17.389 align:start position:0% distribution let's say of alcohol when you<00:10:16.080> go<00:10:16.200> to<00:10:16.320> a<00:10:16.500> bar<00:10:16.620> you<00:10:16.800> need<00:10:16.920> to<00:10:17.040> prove<00:10:17.279> that 00:10:17.389 --> 00:10:17.399 align:start position:0% you go to a bar you need to prove that 00:10:17.399 --> 00:10:19.550 align:start position:0% you go to a bar you need to prove that you<00:10:17.580> are<00:10:17.700> of<00:10:17.820> age<00:10:18.000> and<00:10:18.240> the<00:10:18.420> bartender<00:10:18.779> needs 00:10:19.550 --> 00:10:19.560 align:start position:0% you are of age and the bartender needs 00:10:19.560 --> 00:10:22.790 align:start position:0% you are of age and the bartender needs to<00:10:19.800> prove<00:10:20.640> that<00:10:20.940> they<00:10:21.360> are<00:10:21.779> only 00:10:22.790 --> 00:10:22.800 align:start position:0% to prove that they are only 00:10:22.800 --> 00:10:25.730 align:start position:0% to prove that they are only um<00:10:22.860> Distributing<00:10:23.760> uh<00:10:24.300> alcohol<00:10:24.540> to<00:10:25.080> people<00:10:25.500> who 00:10:25.730 --> 00:10:25.740 align:start position:0% um Distributing uh alcohol to people who 00:10:25.740 --> 00:10:29.329 align:start position:0% um Distributing uh alcohol to people who are<00:10:25.860> of<00:10:26.040> age<00:10:26.279> and<00:10:27.120> this<00:10:27.540> takes<00:10:27.779> the<00:10:27.959> form<00:10:28.140> of<00:10:28.680> uh 00:10:29.329 --> 00:10:29.339 align:start position:0% are of age and this takes the form of uh 00:10:29.339 --> 00:10:32.509 align:start position:0% are of age and this takes the form of uh literal<00:10:29.940> cops<00:10:30.420> sending<00:10:30.779> in<00:10:30.899> uh<00:10:31.320> minors<00:10:31.680> to 00:10:32.509 --> 00:10:32.519 align:start position:0% literal cops sending in uh minors to 00:10:32.519 --> 00:10:35.449 align:start position:0% literal cops sending in uh minors to actually<00:10:32.820> test<00:10:33.360> these<00:10:33.660> places<00:10:33.779> and<00:10:34.140> that<00:10:34.320> is<00:10:34.620> a 00:10:35.449 --> 00:10:35.459 align:start position:0% actually test these places and that is a 00:10:35.459 --> 00:10:37.690 align:start position:0% actually test these places and that is a reactive<00:10:35.820> solution<00:10:36.180> that<00:10:36.600> uses<00:10:37.019> resources 00:10:37.690 --> 00:10:37.700 align:start position:0% reactive solution that uses resources 00:10:37.700 --> 00:10:40.670 align:start position:0% reactive solution that uses resources whereas<00:10:38.700> if<00:10:39.300> we<00:10:39.420> were<00:10:39.540> able<00:10:39.720> to<00:10:39.839> have<00:10:40.080> a<00:10:40.260> system 00:10:40.670 --> 00:10:40.680 align:start position:0% whereas if we were able to have a system 00:10:40.680 --> 00:10:42.590 align:start position:0% whereas if we were able to have a system where<00:10:41.040> you<00:10:41.339> can't<00:10:41.399> even<00:10:41.580> get<00:10:41.820> in<00:10:41.940> the<00:10:42.060> door<00:10:42.240> if 00:10:42.590 --> 00:10:42.600 align:start position:0% where you can't even get in the door if 00:10:42.600 --> 00:10:44.410 align:start position:0% where you can't even get in the door if you<00:10:42.720> can't<00:10:42.779> prove<00:10:43.140> you're<00:10:43.260> 21. 00:10:44.410 --> 00:10:44.420 align:start position:0% you can't prove you're 21. 00:10:44.420 --> 00:10:47.569 align:start position:0% you can't prove you're 21. we<00:10:45.420> create<00:10:45.720> a<00:10:46.320> lot<00:10:46.740> more<00:10:46.920> we<00:10:47.160> free<00:10:47.399> up 00:10:47.569 --> 00:10:47.579 align:start position:0% we create a lot more we free up 00:10:47.579 --> 00:10:49.970 align:start position:0% we create a lot more we free up resources<00:10:48.120> for<00:10:48.420> obviously<00:10:49.260> the<00:10:49.560> people<00:10:49.800> who 00:10:49.970 --> 00:10:49.980 align:start position:0% resources for obviously the people who 00:10:49.980 --> 00:10:51.769 align:start position:0% resources for obviously the people who are<00:10:50.100> checking<00:10:50.459> uh<00:10:50.820> the<00:10:51.000> cops<00:10:51.360> and<00:10:51.480> then<00:10:51.660> as 00:10:51.769 --> 00:10:51.779 align:start position:0% are checking uh the cops and then as 00:10:51.779 --> 00:10:54.590 align:start position:0% are checking uh the cops and then as well<00:10:51.959> it<00:10:52.200> makes<00:10:52.440> the<00:10:52.620> lives<00:10:52.920> of<00:10:53.100> both 00:10:54.590 --> 00:10:54.600 align:start position:0% well it makes the lives of both 00:10:54.600 --> 00:10:56.329 align:start position:0% well it makes the lives of both really<00:10:55.200> the<00:10:55.440> distributor<00:10:55.860> a<00:10:56.040> lot<00:10:56.160> easier 00:10:56.329 --> 00:10:56.339 align:start position:0% really the distributor a lot easier 00:10:56.339 --> 00:10:58.610 align:start position:0% really the distributor a lot easier given<00:10:56.760> the<00:10:56.880> compliance<00:10:57.360> is<00:10:57.480> is<00:10:57.720> managed<00:10:58.200> in<00:10:58.500> a 00:10:58.610 --> 00:10:58.620 align:start position:0% given the compliance is is managed in a 00:10:58.620 --> 00:11:01.370 align:start position:0% given the compliance is is managed in a programmatic<00:10:59.100> way<00:10:59.220> and<00:10:59.640> a<00:11:00.060> proof<00:11:00.660> a<00:11:01.019> provably 00:11:01.370 --> 00:11:01.380 align:start position:0% programmatic way and a proof a provably 00:11:01.380 --> 00:11:03.949 align:start position:0% programmatic way and a proof a provably correct<00:11:01.680> way 00:11:03.949 --> 00:11:03.959 align:start position:0% 00:11:03.959 --> 00:11:07.550 align:start position:0% so<00:11:04.620> just<00:11:05.100> to<00:11:05.279> summarize<00:11:05.640> it<00:11:05.880> uh<00:11:06.480> we<00:11:07.019> have<00:11:07.140> uh 00:11:07.550 --> 00:11:07.560 align:start position:0% so just to summarize it uh we have uh 00:11:07.560 --> 00:11:08.810 align:start position:0% so just to summarize it uh we have uh semaphore<00:11:08.100> again 00:11:08.810 --> 00:11:08.820 align:start position:0% semaphore again 00:11:08.820 --> 00:11:11.210 align:start position:0% semaphore again um<00:11:08.880> which<00:11:09.600> is<00:11:10.200> uh<00:11:10.560> something<00:11:10.800> that<00:11:10.980> could<00:11:11.100> be 00:11:11.210 --> 00:11:11.220 align:start position:0% um which is uh something that could be 00:11:11.220 --> 00:11:14.030 align:start position:0% um which is uh something that could be used<00:11:11.399> for<00:11:11.820> anonymous<00:11:12.480> coordination<00:11:12.959> or<00:11:13.620> uh 00:11:14.030 --> 00:11:14.040 align:start position:0% used for anonymous coordination or uh 00:11:14.040 --> 00:11:16.610 align:start position:0% used for anonymous coordination or uh kyc<00:11:14.579> ammo<00:11:15.060> so<00:11:15.660> what<00:11:16.019> you<00:11:16.140> should<00:11:16.320> really<00:11:16.440> be 00:11:16.610 --> 00:11:16.620 align:start position:0% kyc ammo so what you should really be 00:11:16.620 --> 00:11:18.829 align:start position:0% kyc ammo so what you should really be thinking<00:11:16.980> is<00:11:17.279> that<00:11:17.579> zero<00:11:18.000> knowledge<00:11:18.240> is<00:11:18.600> an 00:11:18.829 --> 00:11:18.839 align:start position:0% thinking is that zero knowledge is an 00:11:18.839 --> 00:11:21.290 align:start position:0% thinking is that zero knowledge is an incredibly<00:11:19.140> versatile<00:11:19.620> tool<00:11:20.100> and<00:11:20.640> how<00:11:20.940> it<00:11:21.120> is 00:11:21.290 --> 00:11:21.300 align:start position:0% incredibly versatile tool and how it is 00:11:21.300 --> 00:11:23.509 align:start position:0% incredibly versatile tool and how it is actually<00:11:21.480> molded<00:11:22.019> into<00:11:22.200> whatever<00:11:22.440> product<00:11:22.800> uh 00:11:23.509 --> 00:11:23.519 align:start position:0% actually molded into whatever product uh 00:11:23.519 --> 00:11:27.290 align:start position:0% actually molded into whatever product uh that's<00:11:23.880> up<00:11:24.000> to<00:11:24.180> you<00:11:24.380> so<00:11:25.380> specifically<00:11:26.279> uh<00:11:27.060> if 00:11:27.290 --> 00:11:27.300 align:start position:0% that's up to you so specifically uh if 00:11:27.300 --> 00:11:29.210 align:start position:0% that's up to you so specifically uh if you<00:11:27.540> are<00:11:27.779> kind<00:11:28.200> of<00:11:28.320> intrigued<00:11:28.620> by<00:11:28.740> semaphore 00:11:29.210 --> 00:11:29.220 align:start position:0% you are kind of intrigued by semaphore 00:11:29.220 --> 00:11:30.769 align:start position:0% you are kind of intrigued by semaphore and<00:11:29.339> you<00:11:29.459> think<00:11:29.579> that<00:11:29.640> you<00:11:29.820> have<00:11:30.000> some<00:11:30.540> way<00:11:30.660> to 00:11:30.769 --> 00:11:30.779 align:start position:0% and you think that you have some way to 00:11:30.779 --> 00:11:32.030 align:start position:0% and you think that you have some way to contribute<00:11:31.140> there's<00:11:31.380> actually<00:11:31.620> a<00:11:31.800> grant 00:11:32.030 --> 00:11:32.040 align:start position:0% contribute there's actually a grant 00:11:32.040 --> 00:11:34.009 align:start position:0% contribute there's actually a grant round<00:11:32.160> going<00:11:32.339> on<00:11:32.459> right<00:11:32.519> now 00:11:34.009 --> 00:11:34.019 align:start position:0% round going on right now 00:11:34.019 --> 00:11:36.650 align:start position:0% round going on right now um I<00:11:34.860> it<00:11:35.279> said<00:11:35.459> uh<00:11:35.640> 14th<00:11:36.120> on<00:11:36.180> an<00:11:36.300> earlier<00:11:36.540> thing 00:11:36.650 --> 00:11:36.660 align:start position:0% um I it said uh 14th on an earlier thing 00:11:36.660 --> 00:11:38.329 align:start position:0% um I it said uh 14th on an earlier thing but<00:11:36.839> I'm<00:11:36.959> pretty<00:11:37.140> sure<00:11:37.260> that<00:11:37.680> this<00:11:37.860> link<00:11:38.040> says 00:11:38.329 --> 00:11:38.339 align:start position:0% but I'm pretty sure that this link says 00:11:38.339 --> 00:11:40.970 align:start position:0% but I'm pretty sure that this link says uh<00:11:38.519> the<00:11:38.700> 28th<00:11:39.180> so<00:11:39.420> I<00:11:40.260> would<00:11:40.380> uh<00:11:40.620> highly 00:11:40.970 --> 00:11:40.980 align:start position:0% uh the 28th so I would uh highly 00:11:40.980 --> 00:11:43.130 align:start position:0% uh the 28th so I would uh highly encourage<00:11:41.279> you<00:11:41.399> again<00:11:41.640> if<00:11:42.000> uh<00:11:42.360> this<00:11:43.019> is 00:11:43.130 --> 00:11:43.140 align:start position:0% encourage you again if uh this is 00:11:43.140 --> 00:11:45.710 align:start position:0% encourage you again if uh this is remotely<00:11:43.500> uh<00:11:43.920> interesting<00:11:44.339> uh<00:11:45.120> to<00:11:45.420> look<00:11:45.540> into 00:11:45.710 --> 00:11:45.720 align:start position:0% remotely uh interesting uh to look into 00:11:45.720 --> 00:11:47.750 align:start position:0% remotely uh interesting uh to look into that<00:11:46.019> Grant<00:11:46.380> uh<00:11:46.860> because<00:11:46.980> there's<00:11:47.220> a<00:11:47.459> huge 00:11:47.750 --> 00:11:47.760 align:start position:0% that Grant uh because there's a huge 00:11:47.760 --> 00:11:51.230 align:start position:0% that Grant uh because there's a huge community<00:11:47.880> of<00:11:48.180> like-minded<00:11:48.779> people<00:11:48.959> so 00:11:51.230 --> 00:11:51.240 align:start position:0% community of like-minded people so 00:11:51.240 --> 00:11:53.150 align:start position:0% community of like-minded people so awesome<00:11:51.660> yeah<00:11:52.019> with<00:11:52.320> the<00:11:52.500> background<00:11:52.800> of<00:11:53.040> uh 00:11:53.150 --> 00:11:53.160 align:start position:0% awesome yeah with the background of uh 00:11:53.160 --> 00:11:54.530 align:start position:0% awesome yeah with the background of uh some<00:11:53.399> of<00:11:53.519> the<00:11:53.579> applications<00:11:53.940> of<00:11:54.180> zero 00:11:54.530 --> 00:11:54.540 align:start position:0% some of the applications of zero 00:11:54.540 --> 00:11:56.810 align:start position:0% some of the applications of zero knowledge<00:11:54.779> let's<00:11:54.959> jump<00:11:55.200> into<00:11:55.440> uh<00:11:55.980> the<00:11:56.579> actual 00:11:56.810 --> 00:11:56.820 align:start position:0% knowledge let's jump into uh the actual 00:11:56.820 --> 00:11:58.970 align:start position:0% knowledge let's jump into uh the actual history<00:11:57.060> and<00:11:57.420> how<00:11:57.660> this<00:11:57.779> came<00:11:57.959> into<00:11:58.079> being<00:11:58.380> so 00:11:58.970 --> 00:11:58.980 align:start position:0% history and how this came into being so 00:11:58.980 --> 00:12:01.790 align:start position:0% history and how this came into being so uh<00:11:59.760> no<00:12:00.120> doubt<00:12:00.420> uh<00:12:00.839> zero<00:12:01.260> knowledge<00:12:01.440> has<00:12:01.620> very 00:12:01.790 --> 00:12:01.800 align:start position:0% uh no doubt uh zero knowledge has very 00:12:01.800 --> 00:12:03.530 align:start position:0% uh no doubt uh zero knowledge has very much<00:12:01.920> been<00:12:02.160> much<00:12:02.459> uh<00:12:03.000> somewhat<00:12:03.360> of<00:12:03.420> a 00:12:03.530 --> 00:12:03.540 align:start position:0% much been much uh somewhat of a 00:12:03.540 --> 00:12:05.449 align:start position:0% much been much uh somewhat of a Zeitgeist<00:12:03.959> this<00:12:04.440> past<00:12:04.620> year<00:12:04.800> everyone's 00:12:05.449 --> 00:12:05.459 align:start position:0% Zeitgeist this past year everyone's 00:12:05.459 --> 00:12:06.769 align:start position:0% Zeitgeist this past year everyone's talking<00:12:05.640> about<00:12:05.880> it<00:12:06.120> how<00:12:06.300> it<00:12:06.420> could<00:12:06.540> be<00:12:06.660> used 00:12:06.769 --> 00:12:06.779 align:start position:0% talking about it how it could be used 00:12:06.779 --> 00:12:09.769 align:start position:0% talking about it how it could be used for<00:12:07.019> privacy<00:12:07.380> purposes<00:12:07.860> scalability<00:12:08.540> but<00:12:09.540> uh 00:12:09.769 --> 00:12:09.779 align:start position:0% for privacy purposes scalability but uh 00:12:09.779 --> 00:12:11.329 align:start position:0% for privacy purposes scalability but uh what<00:12:10.200> not<00:12:10.380> many<00:12:10.560> people<00:12:10.740> might<00:12:10.980> know<00:12:11.160> is 00:12:11.329 --> 00:12:11.339 align:start position:0% what not many people might know is 00:12:11.339 --> 00:12:13.910 align:start position:0% what not many people might know is actually<00:12:11.940> uh<00:12:12.779> you<00:12:12.959> can<00:12:13.079> trace<00:12:13.260> this<00:12:13.500> Genesis 00:12:13.910 --> 00:12:13.920 align:start position:0% actually uh you can trace this Genesis 00:12:13.920 --> 00:12:16.550 align:start position:0% actually uh you can trace this Genesis back<00:12:14.220> to<00:12:14.339> 1985<00:12:15.120> uh<00:12:15.779> two<00:12:15.959> years<00:12:16.079> after<00:12:16.320> the 00:12:16.550 --> 00:12:16.560 align:start position:0% back to 1985 uh two years after the 00:12:16.560 --> 00:12:19.730 align:start position:0% back to 1985 uh two years after the founding<00:12:16.860> of<00:12:16.980> tcpip<00:12:17.760> and<00:12:18.720> six<00:12:18.959> years<00:12:19.079> prior<00:12:19.560> to 00:12:19.730 --> 00:12:19.740 align:start position:0% founding of tcpip and six years prior to 00:12:19.740 --> 00:12:22.210 align:start position:0% founding of tcpip and six years prior to the<00:12:20.700> first<00:12:20.820> website<00:12:21.300> on<00:12:21.480> the<00:12:21.540> world<00:12:21.660> wide<00:12:22.019> web 00:12:22.210 --> 00:12:22.220 align:start position:0% the first website on the world wide web 00:12:22.220 --> 00:12:25.069 align:start position:0% the first website on the world wide web uh<00:12:23.220> it<00:12:23.640> was<00:12:23.760> first<00:12:24.000> published<00:12:24.420> in<00:12:24.600> obscure 00:12:25.069 --> 00:12:25.079 align:start position:0% uh it was first published in obscure 00:12:25.079 --> 00:12:27.490 align:start position:0% uh it was first published in obscure paper<00:12:25.260> by<00:12:25.680> goldwasser<00:12:26.339> Macaulay<00:12:26.820> and<00:12:26.940> rakoff 00:12:27.490 --> 00:12:27.500 align:start position:0% paper by goldwasser Macaulay and rakoff 00:12:27.500 --> 00:12:30.769 align:start position:0% paper by goldwasser Macaulay and rakoff and<00:12:28.500> uh<00:12:29.040> really<00:12:29.519> what<00:12:29.820> this<00:12:30.000> paper<00:12:30.240> at<00:12:30.600> first 00:12:30.769 --> 00:12:30.779 align:start position:0% and uh really what this paper at first 00:12:30.779 --> 00:12:32.810 align:start position:0% and uh really what this paper at first introduced<00:12:31.320> the<00:12:31.680> whole<00:12:31.920> entire<00:12:32.279> concept<00:12:32.640> of 00:12:32.810 --> 00:12:32.820 align:start position:0% introduced the whole entire concept of 00:12:32.820 --> 00:12:34.850 align:start position:0% introduced the whole entire concept of zero<00:12:33.120> knowledge<00:12:33.360> cryptography<00:12:34.019> but<00:12:34.320> it'd<00:12:34.740> be 00:12:34.850 --> 00:12:34.860 align:start position:0% zero knowledge cryptography but it'd be 00:12:34.860 --> 00:12:36.350 align:start position:0% zero knowledge cryptography but it'd be about<00:12:34.980> three<00:12:35.279> decades<00:12:35.700> until<00:12:35.880> we<00:12:36.180> actually 00:12:36.350 --> 00:12:36.360 align:start position:0% about three decades until we actually 00:12:36.360 --> 00:12:38.930 align:start position:0% about three decades until we actually saw<00:12:36.839> uh<00:12:37.200> some<00:12:37.560> continue<00:12:37.740> or<00:12:38.279> some<00:12:38.579> additional 00:12:38.930 --> 00:12:38.940 align:start position:0% saw uh some continue or some additional 00:12:38.940 --> 00:12:41.750 align:start position:0% saw uh some continue or some additional work<00:12:39.120> on<00:12:39.360> this<00:12:39.540> uh<00:12:40.019> in<00:12:40.500> 2013<00:12:40.920> we<00:12:41.279> saw<00:12:41.399> the<00:12:41.640> first 00:12:41.750 --> 00:12:41.760 align:start position:0% work on this uh in 2013 we saw the first 00:12:41.760 --> 00:12:43.970 align:start position:0% work on this uh in 2013 we saw the first CK<00:12:42.180> snark<00:12:42.540> implemented<00:12:43.440> through<00:12:43.740> something 00:12:43.970 --> 00:12:43.980 align:start position:0% CK snark implemented through something 00:12:43.980 --> 00:12:45.710 align:start position:0% CK snark implemented through something called<00:12:44.279> Pinocchio 00:12:45.710 --> 00:12:45.720 align:start position:0% called Pinocchio 00:12:45.720 --> 00:12:47.810 align:start position:0% called Pinocchio um we<00:12:45.959> saw<00:12:46.079> the<00:12:46.320> first<00:12:46.440> example<00:12:46.860> of<00:12:47.040> a<00:12:47.160> ZK<00:12:47.459> VM 00:12:47.810 --> 00:12:47.820 align:start position:0% um we saw the first example of a ZK VM 00:12:47.820 --> 00:12:50.690 align:start position:0% um we saw the first example of a ZK VM through<00:12:48.240> a<00:12:48.480> tinyrem<00:12:49.139> uh<00:12:50.040> these<00:12:50.459> weren't 00:12:50.690 --> 00:12:50.700 align:start position:0% through a tinyrem uh these weren't 00:12:50.700 --> 00:12:53.090 align:start position:0% through a tinyrem uh these weren't blockchain<00:12:51.180> uh<00:12:51.839> specific<00:12:52.139> per<00:12:52.380> se<00:12:52.560> but<00:12:52.860> three 00:12:53.090 --> 00:12:53.100 align:start position:0% blockchain uh specific per se but three 00:12:53.100 --> 00:12:55.490 align:start position:0% blockchain uh specific per se but three more<00:12:53.279> years<00:12:53.519> we<00:12:53.940> would<00:12:54.060> begin<00:12:54.300> to<00:12:54.540> realize<00:12:55.019> the 00:12:55.490 --> 00:12:55.500 align:start position:0% more years we would begin to realize the 00:12:55.500 --> 00:12:56.210 align:start position:0% more years we would begin to realize the uh 00:12:56.210 --> 00:12:56.220 align:start position:0% uh 00:12:56.220 --> 00:12:58.310 align:start position:0% uh you<00:12:56.639> know<00:12:56.760> the<00:12:57.000> opportunity<00:12:57.540> that<00:12:57.899> zero 00:12:58.310 --> 00:12:58.320 align:start position:0% you know the opportunity that zero 00:12:58.320 --> 00:12:59.569 align:start position:0% you know the opportunity that zero knowledge<00:12:58.500> cryptography<00:12:59.100> really<00:12:59.339> could 00:12:59.569 --> 00:12:59.579 align:start position:0% knowledge cryptography really could 00:12:59.579 --> 00:13:02.030 align:start position:0% knowledge cryptography really could provide<00:12:59.880> in<00:13:00.120> terms<00:13:00.360> of<00:13:00.420> scaling<00:13:00.899> uh<00:13:01.740> and 00:13:02.030 --> 00:13:02.040 align:start position:0% provide in terms of scaling uh and 00:13:02.040 --> 00:13:04.129 align:start position:0% provide in terms of scaling uh and providing<00:13:02.459> privacy<00:13:02.820> to<00:13:03.060> ethereum<00:13:03.600> and<00:13:04.019> this 00:13:04.129 --> 00:13:04.139 align:start position:0% providing privacy to ethereum and this 00:13:04.139 --> 00:13:06.470 align:start position:0% providing privacy to ethereum and this happened<00:13:04.320> through<00:13:04.680> uh<00:13:05.220> the<00:13:05.880> proving 00:13:06.470 --> 00:13:06.480 align:start position:0% happened through uh the proving 00:13:06.480 --> 00:13:08.449 align:start position:0% happened through uh the proving mechanism<00:13:06.839> called<00:13:07.139> growth<00:13:07.500> 16<00:13:07.800> which<00:13:08.160> was 00:13:08.449 --> 00:13:08.459 align:start position:0% mechanism called growth 16 which was 00:13:08.459 --> 00:13:10.910 align:start position:0% mechanism called growth 16 which was really<00:13:09.000> the<00:13:09.240> first<00:13:09.420> practical<00:13:09.839> CK<00:13:10.320> snark<00:13:10.680> you 00:13:10.910 --> 00:13:10.920 align:start position:0% really the first practical CK snark you 00:13:10.920 --> 00:13:13.370 align:start position:0% really the first practical CK snark you know<00:13:11.040> something<00:13:11.279> that<00:13:11.579> could<00:13:11.760> uh<00:13:12.720> handle 00:13:13.370 --> 00:13:13.380 align:start position:0% know something that could uh handle 00:13:13.380 --> 00:13:15.129 align:start position:0% know something that could uh handle almost<00:13:13.620> any<00:13:14.040> arbitrary 00:13:15.129 --> 00:13:15.139 align:start position:0% almost any arbitrary 00:13:15.139 --> 00:13:18.710 align:start position:0% almost any arbitrary computational<00:13:16.139> uh<00:13:16.860> problem<00:13:17.339> and<00:13:18.000> uh<00:13:18.240> encrypt 00:13:18.710 --> 00:13:18.720 align:start position:0% computational uh problem and uh encrypt 00:13:18.720 --> 00:13:19.790 align:start position:0% computational uh problem and uh encrypt it 00:13:19.790 --> 00:13:19.800 align:start position:0% it 00:13:19.800 --> 00:13:22.910 align:start position:0% it um<00:13:19.860> two<00:13:20.160> years<00:13:20.279> later<00:13:20.579> we<00:13:21.300> would<00:13:21.480> see<00:13:21.839> a<00:13:22.740> golden 00:13:22.910 --> 00:13:22.920 align:start position:0% um two years later we would see a golden 00:13:22.920 --> 00:13:24.829 align:start position:0% um two years later we would see a golden year<00:13:23.160> and<00:13:23.339> zero<00:13:23.579> knowledge<00:13:23.880> cryptography<00:13:24.480> uh 00:13:24.829 --> 00:13:24.839 align:start position:0% year and zero knowledge cryptography uh 00:13:24.839 --> 00:13:26.269 align:start position:0% year and zero knowledge cryptography uh Barry<00:13:25.200> White<00:13:25.320> Hat<00:13:25.620> implemented<00:13:25.980> the<00:13:26.160> first 00:13:26.269 --> 00:13:26.279 align:start position:0% Barry White Hat implemented the first 00:13:26.279 --> 00:13:29.269 align:start position:0% Barry White Hat implemented the first throw<00:13:26.519> up<00:13:26.760> as<00:13:27.360> far<00:13:27.480> as<00:13:27.600> we<00:13:27.720> were<00:13:27.899> able<00:13:28.079> to<00:13:28.200> uh<00:13:28.800> to 00:13:29.269 --> 00:13:29.279 align:start position:0% throw up as far as we were able to uh to 00:13:29.279 --> 00:13:32.750 align:start position:0% throw up as far as we were able to uh to uh<00:13:29.399> ascertain<00:13:29.880> uh<00:13:30.600> circum<00:13:31.380> a<00:13:31.920> language<00:13:32.220> made 00:13:32.750 --> 00:13:32.760 align:start position:0% uh ascertain uh circum a language made 00:13:32.760 --> 00:13:34.790 align:start position:0% uh ascertain uh circum a language made specifically<00:13:33.180> for<00:13:33.360> writing<00:13:33.660> CK<00:13:34.079> circuits<00:13:34.620> uh 00:13:34.790 --> 00:13:34.800 align:start position:0% specifically for writing CK circuits uh 00:13:34.800 --> 00:13:36.470 align:start position:0% specifically for writing CK circuits uh were<00:13:35.100> released<00:13:35.459> by<00:13:35.639> an<00:13:35.820> organization<00:13:36.180> called 00:13:36.470 --> 00:13:36.480 align:start position:0% were released by an organization called 00:13:36.480 --> 00:13:39.650 align:start position:0% were released by an organization called iden3<00:13:37.220> uh<00:13:38.220> the<00:13:38.519> foundation<00:13:38.820> of<00:13:39.000> the<00:13:39.180> zk's 00:13:39.650 --> 00:13:39.660 align:start position:0% iden3 uh the foundation of the zk's 00:13:39.660 --> 00:13:41.990 align:start position:0% iden3 uh the foundation of the zk's historic<00:13:40.019> which<00:13:40.260> is<00:13:40.380> a<00:13:40.680> different 00:13:41.990 --> 00:13:42.000 align:start position:0% historic which is a different 00:13:42.000 --> 00:13:44.150 align:start position:0% historic which is a different um type<00:13:42.420> of<00:13:42.540> zero<00:13:42.839> knowledge<00:13:43.079> proof<00:13:43.500> apart 00:13:44.150 --> 00:13:44.160 align:start position:0% um type of zero knowledge proof apart 00:13:44.160 --> 00:13:46.430 align:start position:0% um type of zero knowledge proof apart from<00:13:44.279> Starks<00:13:44.880> that<00:13:45.180> stands<00:13:45.480> for<00:13:45.600> zero<00:13:46.139> or 00:13:46.430 --> 00:13:46.440 align:start position:0% from Starks that stands for zero or 00:13:46.440 --> 00:13:48.889 align:start position:0% from Starks that stands for zero or sorry<00:13:46.680> uh<00:13:47.100> scalable<00:13:47.760> transparent<00:13:48.480> argument 00:13:48.889 --> 00:13:48.899 align:start position:0% sorry uh scalable transparent argument 00:13:48.899 --> 00:13:50.930 align:start position:0% sorry uh scalable transparent argument of<00:13:49.139> knowledge<00:13:49.500> and<00:13:49.920> uh<00:13:50.100> what<00:13:50.639> it<00:13:50.820> really 00:13:50.930 --> 00:13:50.940 align:start position:0% of knowledge and uh what it really 00:13:50.940 --> 00:13:52.129 align:start position:0% of knowledge and uh what it really provides 00:13:52.129 --> 00:13:52.139 align:start position:0% provides 00:13:52.139 --> 00:13:54.290 align:start position:0% provides um that<00:13:52.740> snark<00:13:53.040> stone<00:13:53.279> is<00:13:53.700> it's<00:13:53.940> Quantum 00:13:54.290 --> 00:13:54.300 align:start position:0% um that snark stone is it's Quantum 00:13:54.300 --> 00:13:56.750 align:start position:0% um that snark stone is it's Quantum resistant<00:13:54.779> and<00:13:55.200> it<00:13:55.320> also<00:13:55.680> removed<00:13:56.040> moves<00:13:56.639> the 00:13:56.750 --> 00:13:56.760 align:start position:0% resistant and it also removed moves the 00:13:56.760 --> 00:13:58.730 align:start position:0% resistant and it also removed moves the need<00:13:56.880> for<00:13:57.240> a<00:13:57.420> trusted<00:13:57.779> setup<00:13:58.079> which<00:13:58.380> up<00:13:58.560> until 00:13:58.730 --> 00:13:58.740 align:start position:0% need for a trusted setup which up until 00:13:58.740 --> 00:14:01.370 align:start position:0% need for a trusted setup which up until this<00:13:59.040> point<00:13:59.220> has<00:13:59.399> been<00:13:59.579> a<00:13:59.820> major<00:14:00.420> complaint<00:14:00.959> of 00:14:01.370 --> 00:14:01.380 align:start position:0% this point has been a major complaint of 00:14:01.380 --> 00:14:03.590 align:start position:0% this point has been a major complaint of implementing<00:14:01.860> zero<00:14:02.160> knowledge<00:14:02.459> proofs<00:14:02.820> fast 00:14:03.590 --> 00:14:03.600 align:start position:0% implementing zero knowledge proofs fast 00:14:03.600 --> 00:14:06.350 align:start position:0% implementing zero knowledge proofs fast forward<00:14:03.779> to<00:14:04.019> 2019<00:14:04.440> and<00:14:05.220> Aztec<00:14:05.760> released<00:14:06.060> a<00:14:06.240> new 00:14:06.350 --> 00:14:06.360 align:start position:0% forward to 2019 and Aztec released a new 00:14:06.360 --> 00:14:08.150 align:start position:0% forward to 2019 and Aztec released a new proving<00:14:06.660> scheme<00:14:06.959> for<00:14:07.079> Stark's<00:14:07.440> called<00:14:07.680> Planck 00:14:08.150 --> 00:14:08.160 align:start position:0% proving scheme for Stark's called Planck 00:14:08.160 --> 00:14:10.370 align:start position:0% proving scheme for Stark's called Planck this<00:14:09.000> didn't<00:14:09.180> totally<00:14:09.540> get<00:14:09.720> rid<00:14:09.839> of<00:14:09.959> the<00:14:10.079> proof 00:14:10.370 --> 00:14:10.380 align:start position:0% this didn't totally get rid of the proof 00:14:10.380 --> 00:14:12.230 align:start position:0% this didn't totally get rid of the proof uh<00:14:10.740> The<00:14:10.980> Trusted<00:14:11.279> setup<00:14:11.579> but<00:14:11.760> what<00:14:11.940> it<00:14:12.120> did 00:14:12.230 --> 00:14:12.240 align:start position:0% uh The Trusted setup but what it did 00:14:12.240 --> 00:14:14.509 align:start position:0% uh The Trusted setup but what it did allow<00:14:12.480> is<00:14:12.660> a<00:14:12.899> universal<00:14:13.260> trusted<00:14:13.740> setup<00:14:14.160> so 00:14:14.509 --> 00:14:14.519 align:start position:0% allow is a universal trusted setup so 00:14:14.519 --> 00:14:17.509 align:start position:0% allow is a universal trusted setup so instead<00:14:15.180> of<00:14:15.300> needing<00:14:15.779> to<00:14:16.139> provide<00:14:16.740> uh<00:14:17.279> perform 00:14:17.509 --> 00:14:17.519 align:start position:0% instead of needing to provide uh perform 00:14:17.519 --> 00:14:19.370 align:start position:0% instead of needing to provide uh perform a<00:14:17.820> lengthy<00:14:18.120> trusted<00:14:18.540> setup<00:14:18.839> for<00:14:18.959> every<00:14:19.139> single 00:14:19.370 --> 00:14:19.380 align:start position:0% a lengthy trusted setup for every single 00:14:19.380 --> 00:14:21.290 align:start position:0% a lengthy trusted setup for every single snark<00:14:19.680> you<00:14:19.920> implement<00:14:20.220> you<00:14:20.820> only<00:14:20.940> have<00:14:21.120> to<00:14:21.180> do 00:14:21.290 --> 00:14:21.300 align:start position:0% snark you implement you only have to do 00:14:21.300 --> 00:14:23.870 align:start position:0% snark you implement you only have to do one<00:14:21.540> that<00:14:21.720> can<00:14:21.899> then<00:14:22.019> be<00:14:22.200> applied<00:14:22.500> to<00:14:22.620> many 00:14:23.870 --> 00:14:23.880 align:start position:0% one that can then be applied to many 00:14:23.880 --> 00:14:26.389 align:start position:0% one that can then be applied to many um<00:14:24.000> a<00:14:24.360> year<00:14:24.480> after<00:14:24.660> that<00:14:24.959> uh<00:14:25.860> starknet 00:14:26.389 --> 00:14:26.399 align:start position:0% um a year after that uh starknet 00:14:26.399 --> 00:14:28.550 align:start position:0% um a year after that uh starknet released<00:14:26.760> their<00:14:27.000> own<00:14:27.120> ZK<00:14:27.480> VM<00:14:27.779> called<00:14:28.019> Stark<00:14:28.320> x 00:14:28.550 --> 00:14:28.560 align:start position:0% released their own ZK VM called Stark x 00:14:28.560 --> 00:14:30.670 align:start position:0% released their own ZK VM called Stark x with<00:14:28.860> its<00:14:29.100> native<00:14:29.279> language<00:14:29.519> called<00:14:29.880> Cairo 00:14:30.670 --> 00:14:30.680 align:start position:0% with its native language called Cairo 00:14:30.680 --> 00:14:33.769 align:start position:0% with its native language called Cairo importantly<00:14:31.680> to<00:14:31.980> us<00:14:32.160> uh<00:14:32.760> Z<00:14:33.000> cash<00:14:33.240> started<00:14:33.660> work 00:14:33.769 --> 00:14:33.779 align:start position:0% importantly to us uh Z cash started work 00:14:33.779 --> 00:14:36.350 align:start position:0% importantly to us uh Z cash started work on<00:14:33.959> the<00:14:34.079> Halo<00:14:34.380> 2<00:14:34.500> proving<00:14:34.980> scheme<00:14:35.339> which<00:14:36.000> is 00:14:36.350 --> 00:14:36.360 align:start position:0% on the Halo 2 proving scheme which is 00:14:36.360 --> 00:14:39.050 align:start position:0% on the Halo 2 proving scheme which is foundational<00:14:36.959> for<00:14:37.440> battleships<00:14:38.160> V2<00:14:38.519> what<00:14:38.880> we 00:14:39.050 --> 00:14:39.060 align:start position:0% foundational for battleships V2 what we 00:14:39.060 --> 00:14:40.550 align:start position:0% foundational for battleships V2 what we want<00:14:39.180> to<00:14:39.360> accomplish<00:14:39.720> here<00:14:39.839> and<00:14:40.139> uh<00:14:40.380> we'll 00:14:40.550 --> 00:14:40.560 align:start position:0% want to accomplish here and uh we'll 00:14:40.560 --> 00:14:42.710 align:start position:0% want to accomplish here and uh we'll talk<00:14:40.680> about<00:14:40.800> that<00:14:41.040> a<00:14:41.220> bit<00:14:41.339> later<00:14:41.579> uh<00:14:42.420> in<00:14:42.600> our 00:14:42.710 --> 00:14:42.720 align:start position:0% talk about that a bit later uh in our 00:14:42.720 --> 00:14:45.410 align:start position:0% talk about that a bit later uh in our presentation<00:14:43.199> a<00:14:43.980> year<00:14:44.160> after<00:14:44.339> that<00:14:44.579> Mina<00:14:45.060> came 00:14:45.410 --> 00:14:45.420 align:start position:0% presentation a year after that Mina came 00:14:45.420 --> 00:14:47.810 align:start position:0% presentation a year after that Mina came along<00:14:45.600> with<00:14:46.019> the<00:14:46.139> idea<00:14:46.440> of<00:14:46.560> snaps<00:14:46.980> zero 00:14:47.810 --> 00:14:47.820 align:start position:0% along with the idea of snaps zero 00:14:47.820 --> 00:14:49.970 align:start position:0% along with the idea of snaps zero knowledge<00:14:48.060> applications<00:14:48.720> or<00:14:49.260> zero<00:14:49.680> knowledge 00:14:49.970 --> 00:14:49.980 align:start position:0% knowledge applications or zero knowledge 00:14:49.980 --> 00:14:52.370 align:start position:0% knowledge applications or zero knowledge steps<00:14:50.399> as<00:14:50.880> well<00:14:51.000> as<00:14:51.180> circum<00:14:51.480> released<00:14:51.899> uh<00:14:52.199> or 00:14:52.370 --> 00:14:52.380 align:start position:0% steps as well as circum released uh or 00:14:52.380 --> 00:14:55.310 align:start position:0% steps as well as circum released uh or item<00:14:52.800> three<00:14:52.980> release<00:14:53.220> circum<00:14:53.699> 2.0<00:14:54.240> uh<00:14:55.019> which 00:14:55.310 --> 00:14:55.320 align:start position:0% item three release circum 2.0 uh which 00:14:55.320 --> 00:14:57.949 align:start position:0% item three release circum 2.0 uh which really<00:14:56.040> with<00:14:56.699> that<00:14:56.880> that's<00:14:57.240> what<00:14:57.540> made<00:14:57.779> it 00:14:57.949 --> 00:14:57.959 align:start position:0% really with that that's what made it 00:14:57.959 --> 00:15:00.290 align:start position:0% really with that that's what made it possible<00:14:58.320> to<00:14:58.980> uh<00:14:59.220> release<00:14:59.579> Battleship<00:15:00.060> speed 00:15:00.290 --> 00:15:00.300 align:start position:0% possible to uh release Battleship speed 00:15:00.300 --> 00:15:02.689 align:start position:0% possible to uh release Battleship speed one<00:15:00.540> and<00:15:00.720> present<00:15:00.959> at<00:15:01.079> East<00:15:01.320> Denver<00:15:01.500> uh<00:15:02.279> back 00:15:02.689 --> 00:15:02.699 align:start position:0% one and present at East Denver uh back 00:15:02.699 --> 00:15:05.569 align:start position:0% one and present at East Denver uh back earlier<00:15:03.180> in<00:15:03.420> 2022<00:15:04.019> then<00:15:04.680> fast<00:15:04.920> forward<00:15:05.100> to<00:15:05.339> a 00:15:05.569 --> 00:15:05.579 align:start position:0% earlier in 2022 then fast forward to a 00:15:05.579 --> 00:15:09.350 align:start position:0% earlier in 2022 then fast forward to a modern<00:15:05.820> day<00:15:06.060> A<00:15:06.779> year<00:15:06.899> later<00:15:07.019> 2022<00:15:07.860> uh<00:15:08.820> plonky 00:15:09.350 --> 00:15:09.360 align:start position:0% modern day A year later 2022 uh plonky 00:15:09.360 --> 00:15:12.050 align:start position:0% modern day A year later 2022 uh plonky two<00:15:09.540> the<00:15:10.139> successor<00:15:10.500> to<00:15:10.680> plunk<00:15:10.980> uh<00:15:11.579> allows 00:15:12.050 --> 00:15:12.060 align:start position:0% two the successor to plunk uh allows 00:15:12.060 --> 00:15:14.269 align:start position:0% two the successor to plunk uh allows proving<00:15:12.480> speeds<00:15:12.899> that<00:15:13.019> are<00:15:13.139> 100<00:15:13.320> times<00:15:13.620> 100 00:15:14.269 --> 00:15:14.279 align:start position:0% proving speeds that are 100 times 100 00:15:14.279 --> 00:15:17.329 align:start position:0% proving speeds that are 100 times 100 times<00:15:14.639> faster<00:15:15.060> uh<00:15:16.019> zke<00:15:16.380> EVMS<00:15:16.980> are<00:15:17.160> beginning 00:15:17.329 --> 00:15:17.339 align:start position:0% times faster uh zke EVMS are beginning 00:15:17.339 --> 00:15:19.730 align:start position:0% times faster uh zke EVMS are beginning to<00:15:17.639> enter<00:15:17.760> the<00:15:18.000> mix<00:15:18.240> uh<00:15:18.779> in<00:15:18.959> the<00:15:19.139> experimental 00:15:19.730 --> 00:15:19.740 align:start position:0% to enter the mix uh in the experimental 00:15:19.740 --> 00:15:22.370 align:start position:0% to enter the mix uh in the experimental stage<00:15:20.519> uh<00:15:20.940> that<00:15:21.180> include<00:15:21.360> polygon<00:15:21.899> Hermes 00:15:22.370 --> 00:15:22.380 align:start position:0% stage uh that include polygon Hermes 00:15:22.380 --> 00:15:25.069 align:start position:0% stage uh that include polygon Hermes scroll<00:15:23.339> which<00:15:23.760> actually<00:15:23.940> implements<00:15:24.540> Halo<00:15:24.899> 2 00:15:25.069 --> 00:15:25.079 align:start position:0% scroll which actually implements Halo 2 00:15:25.079 --> 00:15:28.069 align:start position:0% scroll which actually implements Halo 2 and<00:15:25.920> then<00:15:26.040> uh<00:15:26.279> ZK<00:15:26.639> sync<00:15:27.060> as<00:15:27.180> well<00:15:27.360> and<00:15:27.959> then 00:15:28.069 --> 00:15:28.079 align:start position:0% and then uh ZK sync as well and then 00:15:28.079 --> 00:15:30.350 align:start position:0% and then uh ZK sync as well and then finally<00:15:28.380> uh<00:15:28.800> an<00:15:28.980> interesting<00:15:29.339> uh<00:15:29.880> application 00:15:30.350 --> 00:15:30.360 align:start position:0% finally uh an interesting uh application 00:15:30.360 --> 00:15:32.629 align:start position:0% finally uh an interesting uh application that<00:15:30.600> exists<00:15:30.959> now<00:15:31.139> is<00:15:31.380> zprize<00:15:31.980> which<00:15:32.220> is<00:15:32.399> a 00:15:32.629 --> 00:15:32.639 align:start position:0% that exists now is zprize which is a 00:15:32.639 --> 00:15:35.810 align:start position:0% that exists now is zprize which is a zero<00:15:33.420> knowledge<00:15:33.720> analog<00:15:34.260> of<00:15:34.500> xprize<00:15:35.220> what<00:15:35.639> it 00:15:35.810 --> 00:15:35.820 align:start position:0% zero knowledge analog of xprize what it 00:15:35.820 --> 00:15:37.790 align:start position:0% zero knowledge analog of xprize what it basically<00:15:36.180> aims<00:15:36.540> to<00:15:36.660> do<00:15:36.720> is<00:15:36.959> uh<00:15:37.260> provide<00:15:37.680> a 00:15:37.790 --> 00:15:37.800 align:start position:0% basically aims to do is uh provide a 00:15:37.800 --> 00:15:39.949 align:start position:0% basically aims to do is uh provide a list<00:15:37.980> of<00:15:38.100> bounties<00:15:38.459> so<00:15:38.820> that<00:15:39.480> um<00:15:39.480> those 00:15:39.949 --> 00:15:39.959 align:start position:0% list of bounties so that um those 00:15:39.959 --> 00:15:41.870 align:start position:0% list of bounties so that um those interested<00:15:40.380> in<00:15:40.500> improving<00:15:41.040> the<00:15:41.519> uh 00:15:41.870 --> 00:15:41.880 align:start position:0% interested in improving the uh 00:15:41.880 --> 00:15:44.090 align:start position:0% interested in improving the uh efficiency<00:15:42.660> which<00:15:43.320> with 00:15:44.090 --> 00:15:44.100 align:start position:0% efficiency which with 00:15:44.100 --> 00:15:46.850 align:start position:0% efficiency which with um zero<00:15:44.820> knowledge<00:15:45.120> algorithms<00:15:45.899> compute<00:15:46.440> uh 00:15:46.850 --> 00:15:46.860 align:start position:0% um zero knowledge algorithms compute uh 00:15:46.860 --> 00:15:49.850 align:start position:0% um zero knowledge algorithms compute uh can<00:15:47.220> go<00:15:47.339> and<00:15:47.459> claim<00:15:47.760> these<00:15:48.000> prizes 00:15:49.850 --> 00:15:49.860 align:start position:0% can go and claim these prizes 00:15:49.860 --> 00:15:51.470 align:start position:0% can go and claim these prizes um<00:15:49.920> but<00:15:50.279> yeah<00:15:50.399> no<00:15:50.699> now<00:15:51.000> that<00:15:51.180> we've<00:15:51.300> gone 00:15:51.470 --> 00:15:51.480 align:start position:0% um but yeah no now that we've gone 00:15:51.480 --> 00:15:52.730 align:start position:0% um but yeah no now that we've gone through<00:15:51.600> the<00:15:51.720> lengthy<00:15:52.079> history<00:15:52.260> let's<00:15:52.560> talk 00:15:52.730 --> 00:15:52.740 align:start position:0% through the lengthy history let's talk 00:15:52.740 --> 00:15:54.829 align:start position:0% through the lengthy history let's talk about<00:15:52.860> how<00:15:53.220> you<00:15:53.279> can<00:15:53.459> actually<00:15:53.579> apply<00:15:54.000> ZK<00:15:54.420> to 00:15:54.829 --> 00:15:54.839 align:start position:0% about how you can actually apply ZK to 00:15:54.839 --> 00:15:57.590 align:start position:0% about how you can actually apply ZK to uh<00:15:55.139> the<00:15:55.680> evm<00:15:56.100> and<00:15:56.820> to<00:15:56.940> do<00:15:57.120> this<00:15:57.240> you<00:15:57.480> really 00:15:57.590 --> 00:15:57.600 align:start position:0% uh the evm and to do this you really 00:15:57.600 --> 00:15:59.810 align:start position:0% uh the evm and to do this you really have<00:15:57.779> two<00:15:58.019> options<00:15:58.440> uh<00:15:59.040> you<00:15:59.339> have<00:15:59.459> the<00:15:59.579> option 00:15:59.810 --> 00:15:59.820 align:start position:0% have two options uh you have the option 00:15:59.820 --> 00:16:01.370 align:start position:0% have two options uh you have the option of<00:15:59.940> applying<00:16:00.300> a<00:16:00.420> domain-specific<00:16:01.019> language 00:16:01.370 --> 00:16:01.380 align:start position:0% of applying a domain-specific language 00:16:01.380 --> 00:16:05.449 align:start position:0% of applying a domain-specific language or<00:16:01.860> utilizing<00:16:02.519> a<00:16:03.060> ZK<00:16:03.839> virtual<00:16:04.560> machine 00:16:05.449 --> 00:16:05.459 align:start position:0% or utilizing a ZK virtual machine 00:16:05.459 --> 00:16:07.430 align:start position:0% or utilizing a ZK virtual machine um<00:16:05.519> and<00:16:05.760> both<00:16:06.000> both<00:16:06.360> uh<00:16:06.779> methods<00:16:07.199> have<00:16:07.320> their 00:16:07.430 --> 00:16:07.440 align:start position:0% um and both both uh methods have their 00:16:07.440 --> 00:16:09.110 align:start position:0% um and both both uh methods have their own<00:16:07.560> pros<00:16:07.920> and<00:16:07.980> cons<00:16:08.100> their<00:16:08.399> own<00:16:08.519> trade-offs 00:16:09.110 --> 00:16:09.120 align:start position:0% own pros and cons their own trade-offs 00:16:09.120 --> 00:16:11.389 align:start position:0% own pros and cons their own trade-offs and<00:16:09.240> ultimately<00:16:10.079> when<00:16:10.500> it<00:16:10.680> comes<00:16:10.860> down<00:16:11.040> to<00:16:11.160> is 00:16:11.389 --> 00:16:11.399 align:start position:0% and ultimately when it comes down to is 00:16:11.399 --> 00:16:13.490 align:start position:0% and ultimately when it comes down to is you<00:16:11.699> know<00:16:11.820> what<00:16:12.600> are<00:16:12.779> you<00:16:12.899> trying<00:16:13.079> to<00:16:13.199> achieve 00:16:13.490 --> 00:16:13.500 align:start position:0% you know what are you trying to achieve 00:16:13.500 --> 00:16:15.050 align:start position:0% you know what are you trying to achieve with<00:16:13.680> your<00:16:13.860> application<00:16:14.279> what's<00:16:14.699> the<00:16:14.880> scope 00:16:15.050 --> 00:16:15.060 align:start position:0% with your application what's the scope 00:16:15.060 --> 00:16:17.930 align:start position:0% with your application what's the scope of<00:16:15.240> it<00:16:15.839> um<00:16:15.959> but<00:16:16.620> we'll<00:16:16.800> uh<00:16:17.459> go<00:16:17.639> through<00:16:17.760> the 00:16:17.930 --> 00:16:17.940 align:start position:0% of it um but we'll uh go through the 00:16:17.940 --> 00:16:19.670 align:start position:0% of it um but we'll uh go through the pros<00:16:18.240> and<00:16:18.300> cons<00:16:18.480> right<00:16:18.779> here 00:16:19.670 --> 00:16:19.680 align:start position:0% pros and cons right here 00:16:19.680 --> 00:16:21.769 align:start position:0% pros and cons right here you<00:16:20.100> know<00:16:20.160> this<00:16:20.339> Pointer's<00:16:20.760> tricky 00:16:21.769 --> 00:16:21.779 align:start position:0% you know this Pointer's tricky 00:16:21.779 --> 00:16:25.430 align:start position:0% you know this Pointer's tricky um<00:16:21.839> so<00:16:22.139> when<00:16:23.100> it<00:16:23.220> comes<00:16:23.459> to<00:16:23.639> a<00:16:23.820> DSL<00:16:24.660> scaling 00:16:25.430 --> 00:16:25.440 align:start position:0% um so when it comes to a DSL scaling 00:16:25.440 --> 00:16:26.990 align:start position:0% um so when it comes to a DSL scaling requires<00:16:25.920> expertise 00:16:26.990 --> 00:16:27.000 align:start position:0% requires expertise 00:16:27.000 --> 00:16:29.810 align:start position:0% requires expertise um<00:16:27.060> but<00:16:27.240> whether<00:16:27.480> it's<00:16:27.600> EK<00:16:27.959> evm<00:16:28.800> the<00:16:29.579> entire 00:16:29.810 --> 00:16:29.820 align:start position:0% um but whether it's EK evm the entire 00:16:29.820 --> 00:16:31.910 align:start position:0% um but whether it's EK evm the entire purpose<00:16:30.240> of<00:16:30.540> this<00:16:30.779> uh<00:16:31.019> other<00:16:31.199> network<00:16:31.500> is 00:16:31.910 --> 00:16:31.920 align:start position:0% purpose of this uh other network is 00:16:31.920 --> 00:16:33.470 align:start position:0% purpose of this uh other network is really<00:16:32.100> to<00:16:32.279> allow<00:16:32.579> scalability<00:16:33.120> of<00:16:33.360> your 00:16:33.470 --> 00:16:33.480 align:start position:0% really to allow scalability of your 00:16:33.480 --> 00:16:35.150 align:start position:0% really to allow scalability of your applications 00:16:35.150 --> 00:16:35.160 align:start position:0% applications 00:16:35.160 --> 00:16:37.069 align:start position:0% applications um 00:16:37.069 --> 00:16:37.079 align:start position:0% um 00:16:37.079 --> 00:16:39.790 align:start position:0% um uh 00:16:39.790 --> 00:16:39.800 align:start position:0% uh 00:16:39.800 --> 00:16:42.530 align:start position:0% uh with<00:16:40.800> dsl's<00:16:41.399> computation<00:16:41.940> is<00:16:42.180> verified 00:16:42.530 --> 00:16:42.540 align:start position:0% with dsl's computation is verified 00:16:42.540 --> 00:16:45.829 align:start position:0% with dsl's computation is verified directly<00:16:43.019> on<00:16:43.199> layer<00:16:43.620> one<00:16:43.800> uh<00:16:44.639> but<00:16:44.820> with<00:16:45.000> GK<00:16:45.360> VMS 00:16:45.829 --> 00:16:45.839 align:start position:0% directly on layer one uh but with GK VMS 00:16:45.839 --> 00:16:47.689 align:start position:0% directly on layer one uh but with GK VMS technically<00:16:46.320> they<00:16:46.560> are<00:16:46.680> a<00:16:46.800> layer<00:16:47.100> two<00:16:47.220> so<00:16:47.459> all 00:16:47.689 --> 00:16:47.699 align:start position:0% technically they are a layer two so all 00:16:47.699 --> 00:16:50.389 align:start position:0% technically they are a layer two so all computations<00:16:48.180> take<00:16:48.600> place<00:16:48.839> on<00:16:49.199> uh<00:16:49.500> set<00:16:50.040> Layer 00:16:50.389 --> 00:16:50.399 align:start position:0% computations take place on uh set Layer 00:16:50.399 --> 00:16:51.889 align:start position:0% computations take place on uh set Layer Two 00:16:51.889 --> 00:16:51.899 align:start position:0% Two 00:16:51.899 --> 00:16:54.470 align:start position:0% Two and<00:16:52.440> then<00:16:52.680> consensus<00:16:53.220> for<00:16:53.519> dsls<00:16:54.180> comes<00:16:54.420> from 00:16:54.470 --> 00:16:54.480 align:start position:0% and then consensus for dsls comes from 00:16:54.480 --> 00:16:56.269 align:start position:0% and then consensus for dsls comes from the<00:16:54.720> root<00:16:55.019> ethereum<00:16:55.440> network<00:16:55.680> of<00:16:55.920> your<00:16:56.040> choice 00:16:56.269 --> 00:16:56.279 align:start position:0% the root ethereum network of your choice 00:16:56.279 --> 00:16:58.550 align:start position:0% the root ethereum network of your choice and<00:16:57.000> then<00:16:57.120> again<00:16:57.300> uh<00:16:57.720> touching<00:16:58.139> on<00:16:58.320> the<00:16:58.440> point 00:16:58.550 --> 00:16:58.560 align:start position:0% and then again uh touching on the point 00:16:58.560 --> 00:17:01.970 align:start position:0% and then again uh touching on the point just<00:16:58.800> before<00:16:59.040> uh<00:16:59.820> a<00:17:00.120> layer<00:17:00.360> two<00:17:00.540> or<00:17:00.959> a<00:17:01.199> ckvm 00:17:01.970 --> 00:17:01.980 align:start position:0% just before uh a layer two or a ckvm 00:17:01.980 --> 00:17:04.370 align:start position:0% just before uh a layer two or a ckvm being<00:17:02.160> a<00:17:02.339> layer<00:17:02.579> two<00:17:02.759> you<00:17:03.540> know<00:17:03.660> you're 00:17:04.370 --> 00:17:04.380 align:start position:0% being a layer two you know you're 00:17:04.380 --> 00:17:06.530 align:start position:0% being a layer two you know you're relying<00:17:04.980> on<00:17:05.040> an<00:17:05.220> entirely<00:17:05.640> separate<00:17:06.179> set<00:17:06.360> of 00:17:06.530 --> 00:17:06.540 align:start position:0% relying on an entirely separate set of 00:17:06.540 --> 00:17:09.409 align:start position:0% relying on an entirely separate set of security<00:17:06.780> and<00:17:07.559> uh<00:17:07.740> validators<00:17:08.339> that<00:17:08.880> you 00:17:09.409 --> 00:17:09.419 align:start position:0% security and uh validators that you 00:17:09.419 --> 00:17:12.289 align:start position:0% security and uh validators that you trust<00:17:09.720> will<00:17:10.319> uh<00:17:10.860> put<00:17:11.220> your 00:17:12.289 --> 00:17:12.299 align:start position:0% trust will uh put your 00:17:12.299 --> 00:17:14.090 align:start position:0% trust will uh put your um<00:17:12.360> eventually<00:17:12.839> reached<00:17:13.199> consensus<00:17:13.620> on<00:17:13.799> layer 00:17:14.090 --> 00:17:14.100 align:start position:0% um eventually reached consensus on layer 00:17:14.100 --> 00:17:15.590 align:start position:0% um eventually reached consensus on layer one<00:17:14.160> but<00:17:14.459> ultimately<00:17:14.760> it's<00:17:15.000> up<00:17:15.179> to<00:17:15.360> this 00:17:15.590 --> 00:17:15.600 align:start position:0% one but ultimately it's up to this 00:17:15.600 --> 00:17:18.829 align:start position:0% one but ultimately it's up to this external<00:17:16.079> network 00:17:18.829 --> 00:17:18.839 align:start position:0% 00:17:18.839 --> 00:17:21.409 align:start position:0% and<00:17:19.319> then<00:17:19.439> uh<00:17:19.620> when<00:17:19.799> it<00:17:19.919> comes<00:17:20.100> to<00:17:20.220> dsls<00:17:20.880> uh<00:17:21.240> the 00:17:21.409 --> 00:17:21.419 align:start position:0% and then uh when it comes to dsls uh the 00:17:21.419 --> 00:17:23.030 align:start position:0% and then uh when it comes to dsls uh the software<00:17:21.660> development<00:17:22.140> kits<00:17:22.559> that<00:17:22.799> exist 00:17:23.030 --> 00:17:23.040 align:start position:0% software development kits that exist 00:17:23.040 --> 00:17:25.130 align:start position:0% software development kits that exist right<00:17:23.220> now<00:17:23.400> do<00:17:23.640> their<00:17:23.819> best<00:17:24.000> to<00:17:24.419> abstract<00:17:24.900> away 00:17:25.130 --> 00:17:25.140 align:start position:0% right now do their best to abstract away 00:17:25.140 --> 00:17:27.289 align:start position:0% right now do their best to abstract away complexity<00:17:25.860> but<00:17:26.220> really<00:17:26.699> what<00:17:26.939> ends<00:17:27.240> up 00:17:27.289 --> 00:17:27.299 align:start position:0% complexity but really what ends up 00:17:27.299 --> 00:17:29.150 align:start position:0% complexity but really what ends up happening<00:17:27.660> is<00:17:27.959> uh<00:17:28.260> you<00:17:28.559> kind<00:17:28.679> of<00:17:28.799> have<00:17:28.860> to<00:17:29.040> put 00:17:29.150 --> 00:17:29.160 align:start position:0% happening is uh you kind of have to put 00:17:29.160 --> 00:17:30.830 align:start position:0% happening is uh you kind of have to put on<00:17:29.280> another<00:17:29.460> thinking<00:17:30.059> cap 00:17:30.830 --> 00:17:30.840 align:start position:0% on another thinking cap 00:17:30.840 --> 00:17:32.810 align:start position:0% on another thinking cap um<00:17:30.900> you<00:17:31.200> know<00:17:31.320> for<00:17:31.860> those<00:17:31.980> of<00:17:32.160> us<00:17:32.280> who<00:17:32.520> are<00:17:32.640> used 00:17:32.810 --> 00:17:32.820 align:start position:0% um you know for those of us who are used 00:17:32.820 --> 00:17:35.450 align:start position:0% um you know for those of us who are used to<00:17:33.000> uh<00:17:33.299> developing<00:17:33.900> in<00:17:34.260> standard<00:17:35.100> languages 00:17:35.450 --> 00:17:35.460 align:start position:0% to uh developing in standard languages 00:17:35.460 --> 00:17:37.370 align:start position:0% to uh developing in standard languages you<00:17:35.820> really<00:17:36.120> when<00:17:36.780> writing<00:17:37.140> to<00:17:37.260> your 00:17:37.370 --> 00:17:37.380 align:start position:0% you really when writing to your 00:17:37.380 --> 00:17:38.930 align:start position:0% you really when writing to your knowledge<00:17:37.679> produce<00:17:38.039> can't<00:17:38.400> get<00:17:38.580> away<00:17:38.700> without 00:17:38.930 --> 00:17:38.940 align:start position:0% knowledge produce can't get away without 00:17:38.940 --> 00:17:40.310 align:start position:0% knowledge produce can't get away without learning<00:17:39.299> some<00:17:39.480> of<00:17:39.600> the<00:17:39.720> cryptographic 00:17:40.310 --> 00:17:40.320 align:start position:0% learning some of the cryptographic 00:17:40.320 --> 00:17:42.710 align:start position:0% learning some of the cryptographic principles<00:17:40.799> uh<00:17:41.280> underlying<00:17:41.880> elliptic<00:17:42.360> curves 00:17:42.710 --> 00:17:42.720 align:start position:0% principles uh underlying elliptic curves 00:17:42.720 --> 00:17:46.310 align:start position:0% principles uh underlying elliptic curves uh<00:17:43.559> finite<00:17:44.340> Fields<00:17:44.940> constructing<00:17:45.720> arithmetic 00:17:46.310 --> 00:17:46.320 align:start position:0% uh finite Fields constructing arithmetic 00:17:46.320 --> 00:17:48.230 align:start position:0% uh finite Fields constructing arithmetic circuits<00:17:46.799> so<00:17:47.100> there's<00:17:47.640> definitely<00:17:47.880> a<00:17:48.059> lot<00:17:48.120> of 00:17:48.230 --> 00:17:48.240 align:start position:0% circuits so there's definitely a lot of 00:17:48.240 --> 00:17:49.909 align:start position:0% circuits so there's definitely a lot of overhead<00:17:48.600> and<00:17:48.840> a<00:17:49.020> lot<00:17:49.140> of<00:17:49.200> investment<00:17:49.679> you 00:17:49.909 --> 00:17:49.919 align:start position:0% overhead and a lot of investment you 00:17:49.919 --> 00:17:51.830 align:start position:0% overhead and a lot of investment you have<00:17:50.039> to<00:17:50.100> put<00:17:50.280> in<00:17:50.460> before<00:17:50.760> you<00:17:51.179> can<00:17:51.600> actually 00:17:51.830 --> 00:17:51.840 align:start position:0% have to put in before you can actually 00:17:51.840 --> 00:17:53.690 align:start position:0% have to put in before you can actually get<00:17:52.080> to<00:17:52.140> writing<00:17:52.440> your<00:17:52.559> own<00:17:52.740> program 00:17:53.690 --> 00:17:53.700 align:start position:0% get to writing your own program 00:17:53.700 --> 00:17:56.870 align:start position:0% get to writing your own program um<00:17:53.760> whereas<00:17:54.299> in<00:17:54.419> a<00:17:54.539> VM<00:17:54.840> uh<00:17:55.559> it's<00:17:56.400> specifically 00:17:56.870 --> 00:17:56.880 align:start position:0% um whereas in a VM uh it's specifically 00:17:56.880 --> 00:17:59.810 align:start position:0% um whereas in a VM uh it's specifically abstracting<00:17:57.600> a<00:17:57.780> lot<00:17:57.900> of<00:17:58.020> the<00:17:58.140> ZK<00:17:58.620> uh<00:17:59.460> overhead 00:17:59.810 --> 00:17:59.820 align:start position:0% abstracting a lot of the ZK uh overhead 00:17:59.820 --> 00:18:02.630 align:start position:0% abstracting a lot of the ZK uh overhead away<00:18:00.059> so<00:18:00.480> you<00:18:00.660> can<00:18:00.780> get<00:18:00.960> in<00:18:01.200> with<00:18:02.100> knowledge<00:18:02.520> as 00:18:02.630 --> 00:18:02.640 align:start position:0% away so you can get in with knowledge as 00:18:02.640 --> 00:18:04.070 align:start position:0% away so you can get in with knowledge as a<00:18:02.820> developer<00:18:03.240> and<00:18:03.360> get<00:18:03.600> ahead<00:18:03.780> and<00:18:03.900> running 00:18:04.070 --> 00:18:04.080 align:start position:0% a developer and get ahead and running 00:18:04.080 --> 00:18:05.810 align:start position:0% a developer and get ahead and running your<00:18:04.320> apps<00:18:04.559> like<00:18:04.679> that 00:18:05.810 --> 00:18:05.820 align:start position:0% your apps like that 00:18:05.820 --> 00:18:07.310 align:start position:0% your apps like that um<00:18:05.880> and<00:18:06.240> then<00:18:06.360> finally<00:18:06.660> talking<00:18:07.080> about 00:18:07.310 --> 00:18:07.320 align:start position:0% um and then finally talking about 00:18:07.320 --> 00:18:11.330 align:start position:0% um and then finally talking about portability<00:18:07.980> uh<00:18:08.640> between<00:18:08.880> dsls<00:18:09.660> and<00:18:09.840> VMS<00:18:10.340> uh 00:18:11.330 --> 00:18:11.340 align:start position:0% portability uh between dsls and VMS uh 00:18:11.340 --> 00:18:14.450 align:start position:0% portability uh between dsls and VMS uh what<00:18:12.179> a<00:18:12.480> DSL<00:18:13.140> basically<00:18:13.500> allows<00:18:13.860> you<00:18:13.919> to<00:18:14.100> do<00:18:14.280> is 00:18:14.450 --> 00:18:14.460 align:start position:0% what a DSL basically allows you to do is 00:18:14.460 --> 00:18:17.210 align:start position:0% what a DSL basically allows you to do is it's<00:18:14.700> a<00:18:14.880> way<00:18:15.000> of<00:18:15.120> constructing<00:18:15.900> your<00:18:16.260> uh<00:18:16.440> files 00:18:17.210 --> 00:18:17.220 align:start position:0% it's a way of constructing your uh files 00:18:17.220 --> 00:18:19.070 align:start position:0% it's a way of constructing your uh files for<00:18:17.340> proving<00:18:17.640> and<00:18:17.820> verifying<00:18:18.360> 0<00:18:18.720> your 00:18:19.070 --> 00:18:19.080 align:start position:0% for proving and verifying 0 your 00:18:19.080 --> 00:18:20.690 align:start position:0% for proving and verifying 0 your knowledge<00:18:19.440> proofs<00:18:19.799> then<00:18:20.160> it's<00:18:20.340> up<00:18:20.520> to<00:18:20.640> you 00:18:20.690 --> 00:18:20.700 align:start position:0% knowledge proofs then it's up to you 00:18:20.700 --> 00:18:23.510 align:start position:0% knowledge proofs then it's up to you where<00:18:20.940> you<00:18:21.120> want<00:18:21.240> to<00:18:21.360> deploy<00:18:21.600> them<00:18:21.780> to<00:18:22.080> be<00:18:22.799> it<00:18:23.039> a 00:18:23.510 --> 00:18:23.520 align:start position:0% where you want to deploy them to be it a 00:18:23.520 --> 00:18:26.029 align:start position:0% where you want to deploy them to be it a solidity<00:18:24.299> smart<00:18:24.480> contract<00:18:24.900> on<00:18:25.140> uh 00:18:26.029 --> 00:18:26.039 align:start position:0% solidity smart contract on uh 00:18:26.039 --> 00:18:29.029 align:start position:0% solidity smart contract on uh be<00:18:26.760> root<00:18:27.179> ethereum<00:18:27.600> chain<00:18:27.900> it's<00:18:28.440> really<00:18:28.740> up<00:18:28.919> to 00:18:29.029 --> 00:18:29.039 align:start position:0% be root ethereum chain it's really up to 00:18:29.039 --> 00:18:30.950 align:start position:0% be root ethereum chain it's really up to you<00:18:29.160> where<00:18:29.340> you<00:18:29.460> deploy<00:18:29.760> to<00:18:30.000> but<00:18:30.600> when<00:18:30.780> it 00:18:30.950 --> 00:18:30.960 align:start position:0% you where you deploy to but when it 00:18:30.960 --> 00:18:33.110 align:start position:0% you where you deploy to but when it comes<00:18:31.080> to<00:18:31.200> ZK<00:18:31.500> VMS<00:18:32.039> you<00:18:32.160> face<00:18:32.340> vendor<00:18:32.760> lock<00:18:32.880> and 00:18:33.110 --> 00:18:33.120 align:start position:0% comes to ZK VMS you face vendor lock and 00:18:33.120 --> 00:18:35.150 align:start position:0% comes to ZK VMS you face vendor lock and risk<00:18:33.419> you<00:18:33.720> know<00:18:33.780> you<00:18:34.200> might<00:18:34.320> have<00:18:34.559> a<00:18:34.860> specific 00:18:35.150 --> 00:18:35.160 align:start position:0% risk you know you might have a specific 00:18:35.160 --> 00:18:36.830 align:start position:0% risk you know you might have a specific idea<00:18:35.580> of<00:18:35.760> what<00:18:35.940> chain<00:18:36.120> you<00:18:36.360> want<00:18:36.539> your 00:18:36.830 --> 00:18:36.840 align:start position:0% idea of what chain you want your 00:18:36.840 --> 00:18:39.289 align:start position:0% idea of what chain you want your application<00:18:37.320> to<00:18:37.559> end<00:18:37.679> up<00:18:37.860> on<00:18:38.039> but<00:18:38.400> down<00:18:39.120> the 00:18:39.289 --> 00:18:39.299 align:start position:0% application to end up on but down the 00:18:39.299 --> 00:18:41.990 align:start position:0% application to end up on but down the road<00:18:39.480> uh<00:18:40.320> if<00:18:40.799> you're 00:18:41.990 --> 00:18:42.000 align:start position:0% road uh if you're 00:18:42.000 --> 00:18:43.370 align:start position:0% road uh if you're you<00:18:42.059> know<00:18:42.419> if<00:18:42.539> the<00:18:42.720> scope<00:18:42.900> of<00:18:43.080> your<00:18:43.260> project 00:18:43.370 --> 00:18:43.380 align:start position:0% you know if the scope of your project 00:18:43.380 --> 00:18:45.230 align:start position:0% you know if the scope of your project changes<00:18:43.860> you<00:18:44.100> can<00:18:44.160> end<00:18:44.280> up<00:18:44.460> being<00:18:44.640> locked<00:18:45.120> in 00:18:45.230 --> 00:18:45.240 align:start position:0% changes you can end up being locked in 00:18:45.240 --> 00:18:47.270 align:start position:0% changes you can end up being locked in and<00:18:46.020> um 00:18:47.270 --> 00:18:47.280 align:start position:0% and um 00:18:47.280 --> 00:18:49.570 align:start position:0% and um you<00:18:47.880> know<00:18:48.000> I 00:18:49.570 --> 00:18:49.580 align:start position:0% you know I 00:18:49.580 --> 00:18:53.090 align:start position:0% you know I lose<00:18:50.580> some<00:18:50.820> flexibility<00:18:51.240> that<00:18:51.539> way 00:18:53.090 --> 00:18:53.100 align:start position:0% lose some flexibility that way 00:18:53.100 --> 00:18:55.970 align:start position:0% lose some flexibility that way but<00:18:53.700> we're<00:18:54.000> out<00:18:54.240> we<00:18:54.480> ended<00:18:54.660> up<00:18:54.720> going<00:18:54.960> on<00:18:55.500> is<00:18:55.740> uh 00:18:55.970 --> 00:18:55.980 align:start position:0% but we're out we ended up going on is uh 00:18:55.980 --> 00:18:57.470 align:start position:0% but we're out we ended up going on is uh the<00:18:56.220> DSL<00:18:56.580> route<00:18:56.700> and<00:18:56.940> for<00:18:57.059> that<00:18:57.120> we<00:18:57.299> chose 00:18:57.470 --> 00:18:57.480 align:start position:0% the DSL route and for that we chose 00:18:57.480 --> 00:18:59.870 align:start position:0% the DSL route and for that we chose cercom<00:18:57.960> uh<00:18:58.500> circom<00:18:58.980> was<00:18:59.220> an<00:18:59.340> obvious<00:18:59.580> choice 00:18:59.870 --> 00:18:59.880 align:start position:0% cercom uh circom was an obvious choice 00:18:59.880 --> 00:19:02.990 align:start position:0% cercom uh circom was an obvious choice because<00:19:00.120> it<00:19:00.539> intuitively<00:19:01.200> uh<00:19:02.039> provides<00:19:02.820> a 00:19:02.990 --> 00:19:03.000 align:start position:0% because it intuitively uh provides a 00:19:03.000 --> 00:19:04.789 align:start position:0% because it intuitively uh provides a language<00:19:03.179> that<00:19:03.720> closely<00:19:04.020> mirrors<00:19:04.500> the 00:19:04.789 --> 00:19:04.799 align:start position:0% language that closely mirrors the 00:19:04.799 --> 00:19:06.710 align:start position:0% language that closely mirrors the cryptography<00:19:05.400> you<00:19:05.520> have<00:19:05.700> to<00:19:05.820> learn 00:19:06.710 --> 00:19:06.720 align:start position:0% cryptography you have to learn 00:19:06.720 --> 00:19:08.810 align:start position:0% cryptography you have to learn um<00:19:06.840> so<00:19:07.440> after<00:19:07.740> going<00:19:08.100> through<00:19:08.340> that<00:19:08.520> headache 00:19:08.810 --> 00:19:08.820 align:start position:0% um so after going through that headache 00:19:08.820 --> 00:19:10.430 align:start position:0% um so after going through that headache learning<00:19:09.240> the<00:19:09.299> ins<00:19:09.600> and<00:19:09.660> outs<00:19:09.960> of<00:19:10.200> the 00:19:10.430 --> 00:19:10.440 align:start position:0% learning the ins and outs of the 00:19:10.440 --> 00:19:12.350 align:start position:0% learning the ins and outs of the underlying<00:19:10.919> cryptography<00:19:11.520> you<00:19:12.059> can<00:19:12.179> pretty 00:19:12.350 --> 00:19:12.360 align:start position:0% underlying cryptography you can pretty 00:19:12.360 --> 00:19:13.730 align:start position:0% underlying cryptography you can pretty much<00:19:12.480> write<00:19:12.720> out<00:19:12.960> everything<00:19:13.320> you've<00:19:13.620> been 00:19:13.730 --> 00:19:13.740 align:start position:0% much write out everything you've been 00:19:13.740 --> 00:19:15.110 align:start position:0% much write out everything you've been working<00:19:13.919> on<00:19:14.100> the<00:19:14.280> past<00:19:14.400> weeks<00:19:14.760> or<00:19:14.880> months 00:19:15.110 --> 00:19:15.120 align:start position:0% working on the past weeks or months 00:19:15.120 --> 00:19:18.110 align:start position:0% working on the past weeks or months however<00:19:15.419> long<00:19:15.660> it<00:19:15.840> takes<00:19:16.020> you<00:19:16.200> uh<00:19:17.039> but<00:19:17.340> anyways 00:19:18.110 --> 00:19:18.120 align:start position:0% however long it takes you uh but anyways 00:19:18.120 --> 00:19:21.049 align:start position:0% however long it takes you uh but anyways uh<00:19:18.539> as<00:19:19.380> much<00:19:19.620> as<00:19:19.799> we<00:19:19.919> love<00:19:20.100> story<00:19:20.400> com<00:19:20.640> we<00:19:20.880> found 00:19:21.049 --> 00:19:21.059 align:start position:0% uh as much as we love story com we found 00:19:21.059 --> 00:19:24.169 align:start position:0% uh as much as we love story com we found it<00:19:21.240> difficult<00:19:21.539> to<00:19:22.320> actually<00:19:23.280> go<00:19:23.820> from 00:19:24.169 --> 00:19:24.179 align:start position:0% it difficult to actually go from 00:19:24.179 --> 00:19:26.150 align:start position:0% it difficult to actually go from beginner's<00:19:24.720> EK<00:19:25.020> developer<00:19:25.500> to<00:19:25.740> releasing 00:19:26.150 --> 00:19:26.160 align:start position:0% beginner's EK developer to releasing 00:19:26.160 --> 00:19:28.370 align:start position:0% beginner's EK developer to releasing battle<00:19:26.400> Zips<00:19:26.820> we<00:19:27.179> actually<00:19:27.299> have<00:19:27.840> crafted<00:19:28.260> our 00:19:28.370 --> 00:19:28.380 align:start position:0% battle Zips we actually have crafted our 00:19:28.380 --> 00:19:30.529 align:start position:0% battle Zips we actually have crafted our own<00:19:28.559> good<00:19:28.740> book<00:19:29.039> called<00:19:29.400> uh<00:19:29.640> awesome<00:19:29.880> circum 00:19:30.529 --> 00:19:30.539 align:start position:0% own good book called uh awesome circum 00:19:30.539 --> 00:19:32.210 align:start position:0% own good book called uh awesome circum and<00:19:30.900> uh<00:19:31.080> you<00:19:31.380> can<00:19:31.500> reach<00:19:31.740> it<00:19:31.799> there<00:19:31.980> by 00:19:32.210 --> 00:19:32.220 align:start position:0% and uh you can reach it there by 00:19:32.220 --> 00:19:33.770 align:start position:0% and uh you can reach it there by scanning<00:19:32.580> the<00:19:32.700> QR<00:19:32.940> code<00:19:33.120> or<00:19:33.480> go<00:19:33.660> to 00:19:33.770 --> 00:19:33.780 align:start position:0% scanning the QR code or go to 00:19:33.780 --> 00:19:36.409 align:start position:0% scanning the QR code or go to battleships.com<00:19:34.440> resources<00:19:35.400> but<00:19:35.700> I<00:19:36.000> just 00:19:36.409 --> 00:19:36.419 align:start position:0% battleships.com resources but I just 00:19:36.419 --> 00:19:38.210 align:start position:0% battleships.com resources but I just want<00:19:36.539> to<00:19:36.720> preface<00:19:37.020> that<00:19:37.380> it's<00:19:37.679> not<00:19:37.860> quite<00:19:38.039> done 00:19:38.210 --> 00:19:38.220 align:start position:0% want to preface that it's not quite done 00:19:38.220 --> 00:19:40.130 align:start position:0% want to preface that it's not quite done yet<00:19:38.400> but<00:19:38.700> come<00:19:39.000> this<00:19:39.179> Friday<00:19:39.419> it<00:19:39.840> should<00:19:39.960> be 00:19:40.130 --> 00:19:40.140 align:start position:0% yet but come this Friday it should be 00:19:40.140 --> 00:19:41.810 align:start position:0% yet but come this Friday it should be complete 00:19:41.810 --> 00:19:41.820 align:start position:0% complete 00:19:41.820 --> 00:19:49.250 align:start position:0% complete um but<00:19:42.179> yeah<00:19:42.360> check<00:19:42.600> it<00:19:42.780> out<00:19:42.900> for<00:19:43.080> sure 00:19:49.250 --> 00:19:49.260 align:start position:0% 00:19:49.260 --> 00:19:50.450 align:start position:0% we're<00:19:49.500> gonna<00:19:49.740> get<00:19:49.799> that 00:19:50.450 --> 00:19:50.460 align:start position:0% we're gonna get that 00:19:50.460 --> 00:19:53.029 align:start position:0% we're gonna get that that<00:19:50.520> finish<00:19:50.820> but 00:19:53.029 --> 00:19:53.039 align:start position:0% that finish but 00:19:53.039 --> 00:19:55.850 align:start position:0% that finish but uh<00:19:53.280> basically<00:19:53.700> uh<00:19:54.419> taking<00:19:54.960> the<00:19:55.260> topics<00:19:55.620> that 00:19:55.850 --> 00:19:55.860 align:start position:0% uh basically uh taking the topics that 00:19:55.860 --> 00:19:58.789 align:start position:0% uh basically uh taking the topics that we<00:19:55.980> think<00:19:56.160> are<00:19:56.640> important<00:19:57.360> from<00:19:57.960> uh<00:19:58.500> you<00:19:58.679> know 00:19:58.789 --> 00:19:58.799 align:start position:0% we think are important from uh you know 00:19:58.799 --> 00:20:01.850 align:start position:0% we think are important from uh you know someone<00:19:59.220> who's<00:19:59.520> absolute<00:20:00.059> newbie<00:20:00.480> uh<00:20:01.320> uh<00:20:01.320> to 00:20:01.850 --> 00:20:01.860 align:start position:0% someone who's absolute newbie uh uh to 00:20:01.860 --> 00:20:04.130 align:start position:0% someone who's absolute newbie uh uh to basically<00:20:02.520> be<00:20:02.700> introduced<00:20:03.179> to<00:20:03.360> borderline 00:20:04.130 --> 00:20:04.140 align:start position:0% basically be introduced to borderline 00:20:04.140 --> 00:20:05.390 align:start position:0% basically be introduced to borderline spoon<00:20:04.440> fed 00:20:05.390 --> 00:20:05.400 align:start position:0% spoon fed 00:20:05.400 --> 00:20:06.890 align:start position:0% spoon fed um<00:20:05.520> and<00:20:05.700> there<00:20:05.880> are<00:20:06.000> some<00:20:06.120> that<00:20:06.360> are<00:20:06.539> really 00:20:06.890 --> 00:20:06.900 align:start position:0% um and there are some that are really 00:20:06.900 --> 00:20:08.570 align:start position:0% um and there are some that are really well<00:20:07.080> documented<00:20:07.740> um 00:20:08.570 --> 00:20:08.580 align:start position:0% well documented um 00:20:08.580 --> 00:20:10.730 align:start position:0% well documented um the<00:20:08.820> proving<00:20:09.059> systems<00:20:09.419> Roth<00:20:09.900> 16<00:20:10.080> and<00:20:10.380> Planck 00:20:10.730 --> 00:20:10.740 align:start position:0% the proving systems Roth 16 and Planck 00:20:10.740 --> 00:20:12.049 align:start position:0% the proving systems Roth 16 and Planck and 00:20:12.049 --> 00:20:12.059 align:start position:0% and 00:20:12.059 --> 00:20:14.090 align:start position:0% and oh<00:20:12.240> ceremony<00:20:12.660> that<00:20:12.960> is<00:20:13.140> trusted<00:20:13.559> setup<00:20:13.919> for 00:20:14.090 --> 00:20:14.100 align:start position:0% oh ceremony that is trusted setup for 00:20:14.100 --> 00:20:17.390 align:start position:0% oh ceremony that is trusted setup for grass<00:20:14.460> 16.<00:20:14.820> we<00:20:15.000> don't<00:20:15.120> really<00:20:15.900> need<00:20:16.440> to<00:20:16.860> do<00:20:17.100> a 00:20:17.390 --> 00:20:17.400 align:start position:0% grass 16. we don't really need to do a 00:20:17.400 --> 00:20:19.730 align:start position:0% grass 16. we don't really need to do a lot<00:20:17.940> for<00:20:18.360> that<00:20:18.539> we<00:20:18.840> are<00:20:19.140> really<00:20:19.380> just 00:20:19.730 --> 00:20:19.740 align:start position:0% lot for that we are really just 00:20:19.740 --> 00:20:22.549 align:start position:0% lot for that we are really just aggregating<00:20:20.360> existing<00:20:21.360> documentation<00:20:22.140> and 00:20:22.549 --> 00:20:22.559 align:start position:0% aggregating existing documentation and 00:20:22.559 --> 00:20:25.970 align:start position:0% aggregating existing documentation and putting<00:20:22.860> it<00:20:23.039> in<00:20:23.700> an<00:20:24.059> easy<00:20:24.299> to<00:20:24.480> access<00:20:24.980> format 00:20:25.970 --> 00:20:25.980 align:start position:0% putting it in an easy to access format 00:20:25.980 --> 00:20:29.630 align:start position:0% putting it in an easy to access format on<00:20:26.880> the<00:20:26.940> other<00:20:27.059> hand<00:20:27.299> we<00:20:28.080> have<00:20:28.640> multiplexing 00:20:29.630 --> 00:20:29.640 align:start position:0% on the other hand we have multiplexing 00:20:29.640 --> 00:20:32.450 align:start position:0% on the other hand we have multiplexing in<00:20:30.120> circom<00:20:30.600> this<00:20:30.960> is<00:20:31.080> a<00:20:31.260> little<00:20:31.500> hidden<00:20:32.160> tidbit 00:20:32.450 --> 00:20:32.460 align:start position:0% in circom this is a little hidden tidbit 00:20:32.460 --> 00:20:34.250 align:start position:0% in circom this is a little hidden tidbit that<00:20:32.640> took<00:20:32.820> us<00:20:32.940> a<00:20:33.120> while<00:20:33.240> to<00:20:33.419> figure<00:20:33.600> out<00:20:33.780> if 00:20:34.250 --> 00:20:34.260 align:start position:0% that took us a while to figure out if 00:20:34.260 --> 00:20:36.169 align:start position:0% that took us a while to figure out if you<00:20:34.500> read<00:20:34.679> the<00:20:34.860> circum<00:20:35.280> documentation<00:20:35.820> you 00:20:36.169 --> 00:20:36.179 align:start position:0% you read the circum documentation you 00:20:36.179 --> 00:20:37.909 align:start position:0% you read the circum documentation you will<00:20:36.299> be<00:20:36.419> misled<00:20:36.780> into<00:20:37.140> thinking<00:20:37.559> that<00:20:37.799> you 00:20:37.909 --> 00:20:37.919 align:start position:0% will be misled into thinking that you 00:20:37.919 --> 00:20:41.450 align:start position:0% will be misled into thinking that you can<00:20:38.039> use<00:20:38.160> if<00:20:38.340> statements<00:20:38.760> you 00:20:41.450 --> 00:20:41.460 align:start position:0% 00:20:41.460 --> 00:20:43.010 align:start position:0% you<00:20:41.580> try<00:20:41.820> to<00:20:41.940> use<00:20:42.000> an<00:20:42.179> if<00:20:42.299> statement<00:20:42.660> to 00:20:43.010 --> 00:20:43.020 align:start position:0% you try to use an if statement to 00:20:43.020 --> 00:20:45.650 align:start position:0% you try to use an if statement to compute<00:20:43.500> a<00:20:43.860> condition<00:20:44.240> to<00:20:45.240> select<00:20:45.539> a 00:20:45.650 --> 00:20:45.660 align:start position:0% compute a condition to select a 00:20:45.660 --> 00:20:47.690 align:start position:0% compute a condition to select a conditional<00:20:46.020> statement<00:20:46.320> in<00:20:46.860> circum<00:20:47.280> you<00:20:47.580> will 00:20:47.690 --> 00:20:47.700 align:start position:0% conditional statement in circum you will 00:20:47.700 --> 00:20:49.549 align:start position:0% conditional statement in circum you will get<00:20:47.940> an<00:20:48.299> error<00:20:48.600> called<00:20:48.780> non-quadratic 00:20:49.549 --> 00:20:49.559 align:start position:0% get an error called non-quadratic 00:20:49.559 --> 00:20:52.370 align:start position:0% get an error called non-quadratic constraints<00:20:49.860> not<00:20:50.100> allowed<00:20:50.400> very<00:20:50.940> dreaded<00:20:51.480> and 00:20:52.370 --> 00:20:52.380 align:start position:0% constraints not allowed very dreaded and 00:20:52.380 --> 00:20:54.409 align:start position:0% constraints not allowed very dreaded and to<00:20:52.679> circumvent<00:20:53.100> it<00:20:53.280> essentially<00:20:53.940> you<00:20:54.179> need<00:20:54.299> to 00:20:54.409 --> 00:20:54.419 align:start position:0% to circumvent it essentially you need to 00:20:54.419 --> 00:20:56.150 align:start position:0% to circumvent it essentially you need to do<00:20:54.600> something<00:20:54.840> called<00:20:55.140> signal<00:20:55.559> multiplexing 00:20:56.150 --> 00:20:56.160 align:start position:0% do something called signal multiplexing 00:20:56.160 --> 00:20:58.310 align:start position:0% do something called signal multiplexing which<00:20:56.400> is<00:20:56.520> where<00:20:56.880> in<00:20:57.179> zero<00:20:57.600> knowledge<00:20:57.840> you 00:20:58.310 --> 00:20:58.320 align:start position:0% which is where in zero knowledge you 00:20:58.320 --> 00:21:01.190 align:start position:0% which is where in zero knowledge you cute<00:20:58.980> both<00:20:59.340> cases<00:20:59.880> or<00:21:00.299> let's<00:21:00.539> say<00:21:00.660> you<00:21:00.840> have<00:21:01.020> n 00:21:01.190 --> 00:21:01.200 align:start position:0% cute both cases or let's say you have n 00:21:01.200 --> 00:21:02.870 align:start position:0% cute both cases or let's say you have n different<00:21:01.440> branches<00:21:01.919> of<00:21:02.039> logic<00:21:02.340> you<00:21:02.520> compute 00:21:02.870 --> 00:21:02.880 align:start position:0% different branches of logic you compute 00:21:02.880 --> 00:21:05.270 align:start position:0% different branches of logic you compute all<00:21:03.120> n<00:21:03.240> branches<00:21:03.780> and<00:21:04.500> only<00:21:04.740> once<00:21:05.100> you've 00:21:05.270 --> 00:21:05.280 align:start position:0% all n branches and only once you've 00:21:05.280 --> 00:21:07.250 align:start position:0% all n branches and only once you've computed<00:21:05.640> every<00:21:06.000> single<00:21:06.299> branch<00:21:06.539> in<00:21:06.840> zero 00:21:07.250 --> 00:21:07.260 align:start position:0% computed every single branch in zero 00:21:07.260 --> 00:21:09.350 align:start position:0% computed every single branch in zero knowledge<00:21:07.559> then<00:21:08.280> can<00:21:08.580> you<00:21:08.760> select<00:21:09.120> which 00:21:09.350 --> 00:21:09.360 align:start position:0% knowledge then can you select which 00:21:09.360 --> 00:21:12.409 align:start position:0% knowledge then can you select which branch<00:21:09.660> you<00:21:09.840> want<00:21:10.020> and<00:21:10.860> this<00:21:11.160> is<00:21:11.340> uh<00:21:11.880> this<00:21:12.299> is 00:21:12.409 --> 00:21:12.419 align:start position:0% branch you want and this is uh this is 00:21:12.419 --> 00:21:15.049 align:start position:0% branch you want and this is uh this is an<00:21:13.140> analogy<00:21:13.919> from<00:21:14.220> electrical<00:21:14.760> signal 00:21:15.049 --> 00:21:15.059 align:start position:0% an analogy from electrical signal 00:21:15.059 --> 00:21:16.909 align:start position:0% an analogy from electrical signal processing<00:21:15.419> I<00:21:15.600> believe<00:21:15.720> this<00:21:15.840> is<00:21:15.960> how<00:21:16.260> uh<00:21:16.500> TV 00:21:16.909 --> 00:21:16.919 align:start position:0% processing I believe this is how uh TV 00:21:16.919 --> 00:21:20.270 align:start position:0% processing I believe this is how uh TV channels<00:21:17.220> and<00:21:17.340> cable<00:21:17.580> even<00:21:18.059> works<00:21:18.600> but<00:21:19.320> um<00:21:19.320> the 00:21:20.270 --> 00:21:20.280 align:start position:0% channels and cable even works but um the 00:21:20.280 --> 00:21:22.250 align:start position:0% channels and cable even works but um the point<00:21:20.400> is<00:21:20.580> if<00:21:21.059> you<00:21:21.360> aren't<00:21:21.539> familiar<00:21:22.020> with 00:21:22.250 --> 00:21:22.260 align:start position:0% point is if you aren't familiar with 00:21:22.260 --> 00:21:23.690 align:start position:0% point is if you aren't familiar with this<00:21:22.380> I<00:21:22.620> know<00:21:22.740> I<00:21:22.980> wasn't<00:21:23.100> when<00:21:23.340> I<00:21:23.460> was<00:21:23.520> looking 00:21:23.690 --> 00:21:23.700 align:start position:0% this I know I wasn't when I was looking 00:21:23.700 --> 00:21:25.250 align:start position:0% this I know I wasn't when I was looking through<00:21:23.940> various<00:21:24.240> code<00:21:24.419> bases<00:21:24.840> and<00:21:25.020> looking 00:21:25.250 --> 00:21:25.260 align:start position:0% through various code bases and looking 00:21:25.260 --> 00:21:27.350 align:start position:0% through various code bases and looking at<00:21:25.440> multiplexing<00:21:26.160> and<00:21:26.580> while<00:21:26.760> you<00:21:26.880> see<00:21:27.059> an<00:21:27.240> if 00:21:27.350 --> 00:21:27.360 align:start position:0% at multiplexing and while you see an if 00:21:27.360 --> 00:21:28.909 align:start position:0% at multiplexing and while you see an if statement<00:21:27.720> in<00:21:27.900> the<00:21:28.020> documentation<00:21:28.440> it<00:21:28.679> can<00:21:28.799> be 00:21:28.909 --> 00:21:28.919 align:start position:0% statement in the documentation it can be 00:21:28.919 --> 00:21:30.890 align:start position:0% statement in the documentation it can be very<00:21:29.039> confusing<00:21:29.580> but<00:21:30.299> um<00:21:30.299> so<00:21:30.539> that's<00:21:30.720> an 00:21:30.890 --> 00:21:30.900 align:start position:0% very confusing but um so that's an 00:21:30.900 --> 00:21:32.390 align:start position:0% very confusing but um so that's an example<00:21:31.140> of<00:21:31.260> something<00:21:31.440> we<00:21:31.620> go<00:21:31.799> more<00:21:31.980> in<00:21:32.100> depth 00:21:32.390 --> 00:21:32.400 align:start position:0% example of something we go more in depth 00:21:32.400 --> 00:21:33.710 align:start position:0% example of something we go more in depth on 00:21:33.710 --> 00:21:33.720 align:start position:0% on 00:21:33.720 --> 00:21:35.029 align:start position:0% on um<00:21:33.780> for<00:21:34.020> the<00:21:34.200> sake<00:21:34.320> of<00:21:34.440> time<00:21:34.620> I'm<00:21:34.799> going<00:21:34.980> to 00:21:35.029 --> 00:21:35.039 align:start position:0% um for the sake of time I'm going to 00:21:35.039 --> 00:21:36.529 align:start position:0% um for the sake of time I'm going to speed<00:21:35.280> through<00:21:35.460> a<00:21:35.580> little<00:21:35.700> bit<00:21:35.760> of<00:21:35.880> this<00:21:36.480> um 00:21:36.529 --> 00:21:36.539 align:start position:0% speed through a little bit of this um 00:21:36.539 --> 00:21:39.049 align:start position:0% speed through a little bit of this um but<00:21:36.900> uh<00:21:37.679> we<00:21:38.039> have<00:21:38.159> some<00:21:38.460> stuff<00:21:38.640> that's<00:21:38.880> again 00:21:39.049 --> 00:21:39.059 align:start position:0% but uh we have some stuff that's again 00:21:39.059 --> 00:21:41.149 align:start position:0% but uh we have some stuff that's again more<00:21:39.299> documented<00:21:39.900> uh<00:21:40.320> which<00:21:40.620> is<00:21:40.860> the 00:21:41.149 --> 00:21:41.159 align:start position:0% more documented uh which is the 00:21:41.159 --> 00:21:43.430 align:start position:0% more documented uh which is the arithmetic<00:21:41.760> friendly<00:21:42.120> implementations<00:21:42.900> of 00:21:43.430 --> 00:21:43.440 align:start position:0% arithmetic friendly implementations of 00:21:43.440 --> 00:21:45.110 align:start position:0% arithmetic friendly implementations of uh<00:21:43.679> different<00:21:43.860> hashing<00:21:44.280> algorithms<00:21:44.820> which 00:21:45.110 --> 00:21:45.120 align:start position:0% uh different hashing algorithms which 00:21:45.120 --> 00:21:47.810 align:start position:0% uh different hashing algorithms which then<00:21:45.480> uh<00:21:45.960> underlie<00:21:46.500> the<00:21:46.740> signing<00:21:47.159> algorithms 00:21:47.810 --> 00:21:47.820 align:start position:0% then uh underlie the signing algorithms 00:21:47.820 --> 00:21:52.490 align:start position:0% then uh underlie the signing algorithms so<00:21:48.240> sha3<00:21:48.840> and<00:21:49.919> um<00:21:49.919> uh<00:21:50.880> ecdsa<00:21:51.659> out<00:21:52.200> the<00:21:52.380> window 00:21:52.490 --> 00:21:52.500 align:start position:0% so sha3 and um uh ecdsa out the window 00:21:52.500 --> 00:21:54.950 align:start position:0% so sha3 and um uh ecdsa out the window uh<00:21:53.039> we're<00:21:53.220> now<00:21:53.340> using<00:21:53.640> Poseidon<00:21:54.240> or<00:21:54.419> MIM<00:21:54.600> C<00:21:54.780> at 00:21:54.950 --> 00:21:54.960 align:start position:0% uh we're now using Poseidon or MIM C at 00:21:54.960 --> 00:21:57.230 align:start position:0% uh we're now using Poseidon or MIM C at the<00:21:55.080> very<00:21:55.140> least<00:21:55.260> and<00:21:55.679> uh<00:21:55.980> eddsa<00:21:56.820> which<00:21:57.059> are 00:21:57.230 --> 00:21:57.240 align:start position:0% the very least and uh eddsa which are 00:21:57.240 --> 00:21:58.970 align:start position:0% the very least and uh eddsa which are far<00:21:57.419> more<00:21:57.600> efficient 00:21:58.970 --> 00:21:58.980 align:start position:0% far more efficient 00:21:58.980 --> 00:22:01.310 align:start position:0% far more efficient um<00:21:59.520> we<00:21:59.880> have<00:22:00.000> Merkle<00:22:00.360> trees<00:22:00.659> which<00:22:00.840> I'm<00:22:01.020> sure<00:22:01.200> a 00:22:01.310 --> 00:22:01.320 align:start position:0% um we have Merkle trees which I'm sure a 00:22:01.320 --> 00:22:02.930 align:start position:0% um we have Merkle trees which I'm sure a lot<00:22:01.440> of<00:22:01.500> you<00:22:01.620> are<00:22:01.799> aware<00:22:02.100> of<00:22:02.220> but<00:22:02.400> they<00:22:02.640> are<00:22:02.760> one 00:22:02.930 --> 00:22:02.940 align:start position:0% lot of you are aware of but they are one 00:22:02.940 --> 00:22:04.789 align:start position:0% lot of you are aware of but they are one of<00:22:03.059> the<00:22:03.059> most<00:22:03.240> powerful<00:22:03.539> tools<00:22:04.020> both<00:22:04.559> for 00:22:04.789 --> 00:22:04.799 align:start position:0% of the most powerful tools both for 00:22:04.799 --> 00:22:07.430 align:start position:0% of the most powerful tools both for privacy<00:22:05.220> and<00:22:05.460> scalability<00:22:06.059> we<00:22:06.600> can<00:22:06.720> take<00:22:06.960> a 00:22:07.430 --> 00:22:07.440 align:start position:0% privacy and scalability we can take a 00:22:07.440 --> 00:22:09.590 align:start position:0% privacy and scalability we can take a massive<00:22:07.740> massive<00:22:08.159> data<00:22:08.520> set<00:22:08.640> and<00:22:09.179> compress<00:22:09.419> it 00:22:09.590 --> 00:22:09.600 align:start position:0% massive massive data set and compress it 00:22:09.600 --> 00:22:12.470 align:start position:0% massive massive data set and compress it into<00:22:09.840> a<00:22:10.140> tiny<00:22:10.440> hash<00:22:10.740> and<00:22:11.460> not<00:22:11.820> only<00:22:12.000> is<00:22:12.299> this 00:22:12.470 --> 00:22:12.480 align:start position:0% into a tiny hash and not only is this 00:22:12.480 --> 00:22:15.169 align:start position:0% into a tiny hash and not only is this clearly<00:22:12.900> a<00:22:13.320> method<00:22:13.860> for<00:22:14.039> scaling<00:22:14.460> but<00:22:14.760> we're 00:22:15.169 --> 00:22:15.179 align:start position:0% clearly a method for scaling but we're 00:22:15.179 --> 00:22:17.149 align:start position:0% clearly a method for scaling but we're also<00:22:15.419> taking<00:22:15.600> that<00:22:15.900> data<00:22:16.200> set<00:22:16.320> and<00:22:16.620> obscuring 00:22:17.149 --> 00:22:17.159 align:start position:0% also taking that data set and obscuring 00:22:17.159 --> 00:22:18.470 align:start position:0% also taking that data set and obscuring the<00:22:17.280> data<00:22:17.520> within<00:22:17.760> it<00:22:17.880> while<00:22:18.059> still<00:22:18.299> being 00:22:18.470 --> 00:22:18.480 align:start position:0% the data within it while still being 00:22:18.480 --> 00:22:21.110 align:start position:0% the data within it while still being able<00:22:18.780> to<00:22:18.960> operate<00:22:19.320> on<00:22:19.559> it<00:22:19.679> so<00:22:20.340> this<00:22:20.700> gives<00:22:21.000> us 00:22:21.110 --> 00:22:21.120 align:start position:0% able to operate on it so this gives us 00:22:21.120 --> 00:22:23.330 align:start position:0% able to operate on it so this gives us both<00:22:21.299> privacy<00:22:21.780> and<00:22:21.900> scalability<00:22:22.440> so<00:22:22.799> you<00:22:23.220> will 00:22:23.330 --> 00:22:23.340 align:start position:0% both privacy and scalability so you will 00:22:23.340 --> 00:22:24.710 align:start position:0% both privacy and scalability so you will definitely<00:22:23.580> be<00:22:23.700> working<00:22:23.880> with<00:22:24.059> Merkle<00:22:24.419> trees 00:22:24.710 --> 00:22:24.720 align:start position:0% definitely be working with Merkle trees 00:22:24.720 --> 00:22:26.990 align:start position:0% definitely be working with Merkle trees and<00:22:25.679> then<00:22:25.799> there<00:22:26.039> is<00:22:26.220> first<00:22:26.460> and<00:22:26.640> third<00:22:26.820> party 00:22:26.990 --> 00:22:27.000 align:start position:0% and then there is first and third party 00:22:27.000 --> 00:22:29.330 align:start position:0% and then there is first and third party devtooling<00:22:27.840> the<00:22:28.380> first<00:22:28.500> party<00:22:28.620> devtooling 00:22:29.330 --> 00:22:29.340 align:start position:0% devtooling the first party devtooling 00:22:29.340 --> 00:22:31.029 align:start position:0% devtooling the first party devtooling you<00:22:29.520> literally<00:22:29.760> just<00:22:29.880> have<00:22:30.000> to<00:22:30.120> use 00:22:31.029 --> 00:22:31.039 align:start position:0% you literally just have to use 00:22:31.039 --> 00:22:34.970 align:start position:0% you literally just have to use circum<00:22:32.039> uh<00:22:32.580> relies<00:22:33.059> on<00:22:33.179> snark.js<00:22:33.840> to<00:22:34.320> actually 00:22:34.970 --> 00:22:34.980 align:start position:0% circum uh relies on snark.js to actually 00:22:34.980 --> 00:22:37.789 align:start position:0% circum uh relies on snark.js to actually put<00:22:35.400> proofs<00:22:35.820> in<00:22:36.059> the<00:22:36.179> evm<00:22:36.600> and<00:22:37.559> then<00:22:37.620> there's 00:22:37.789 --> 00:22:37.799 align:start position:0% put proofs in the evm and then there's 00:22:37.799 --> 00:22:39.529 align:start position:0% put proofs in the evm and then there's also<00:22:37.980> circum<00:22:38.400> tester<00:22:38.760> which<00:22:38.940> unless<00:22:39.240> you<00:22:39.360> want 00:22:39.529 --> 00:22:39.539 align:start position:0% also circum tester which unless you want 00:22:39.539 --> 00:22:41.210 align:start position:0% also circum tester which unless you want to<00:22:39.659> spend<00:22:39.840> two<00:22:40.020> hours<00:22:40.200> running<00:22:40.559> tests<00:22:41.039> every 00:22:41.210 --> 00:22:41.220 align:start position:0% to spend two hours running tests every 00:22:41.220 --> 00:22:42.890 align:start position:0% to spend two hours running tests every single<00:22:41.460> time<00:22:41.640> uh<00:22:42.360> you're<00:22:42.539> going<00:22:42.659> to<00:22:42.720> want<00:22:42.840> to 00:22:42.890 --> 00:22:42.900 align:start position:0% single time uh you're going to want to 00:22:42.900 --> 00:22:44.270 align:start position:0% single time uh you're going to want to use<00:22:43.020> something<00:22:43.200> that<00:22:43.380> simulates<00:22:43.799> the<00:22:43.980> logic 00:22:44.270 --> 00:22:44.280 align:start position:0% use something that simulates the logic 00:22:44.280 --> 00:22:45.950 align:start position:0% use something that simulates the logic rather<00:22:44.520> than<00:22:44.700> actually<00:22:44.940> running<00:22:45.480> the<00:22:45.780> entire 00:22:45.950 --> 00:22:45.960 align:start position:0% rather than actually running the entire 00:22:45.960 --> 00:22:47.450 align:start position:0% rather than actually running the entire overhead<00:22:46.380> and<00:22:47.039> then<00:22:47.100> there's<00:22:47.280> also 00:22:47.450 --> 00:22:47.460 align:start position:0% overhead and then there's also 00:22:47.460 --> 00:22:49.850 align:start position:0% overhead and then there's also third-party<00:22:48.000> tooling<00:22:48.360> which<00:22:48.600> is<00:22:49.020> maybe<00:22:49.620> not 00:22:49.850 --> 00:22:49.860 align:start position:0% third-party tooling which is maybe not 00:22:49.860 --> 00:22:52.190 align:start position:0% third-party tooling which is maybe not as<00:22:50.220> required<00:22:50.820> but<00:22:51.120> still<00:22:51.360> is<00:22:51.600> very<00:22:51.900> important 00:22:52.190 --> 00:22:52.200 align:start position:0% as required but still is very important 00:22:52.200 --> 00:22:54.110 align:start position:0% as required but still is very important for<00:22:52.380> having<00:22:52.620> a<00:22:52.799> good<00:22:52.919> time<00:22:53.039> developing<00:22:53.580> so 00:22:54.110 --> 00:22:54.120 align:start position:0% for having a good time developing so 00:22:54.120 --> 00:22:56.029 align:start position:0% for having a good time developing so there<00:22:54.299> is<00:22:54.419> The<00:22:54.600> Shield<00:22:54.720> CLI<00:22:55.320> which<00:22:55.620> was<00:22:55.799> just 00:22:56.029 --> 00:22:56.039 align:start position:0% there is The Shield CLI which was just 00:22:56.039 --> 00:22:58.370 align:start position:0% there is The Shield CLI which was just released<00:22:56.460> I<00:22:56.820> believe<00:22:57.000> two<00:22:57.360> weeks<00:22:57.659> ago<00:22:57.840> they 00:22:58.370 --> 00:22:58.380 align:start position:0% released I believe two weeks ago they 00:22:58.380 --> 00:22:59.990 align:start position:0% released I believe two weeks ago they released<00:22:58.799> their<00:22:59.100> first<00:22:59.280> non-beta<00:22:59.880> version 00:22:59.990 --> 00:23:00.000 align:start position:0% released their first non-beta version 00:23:00.000 --> 00:23:02.450 align:start position:0% released their first non-beta version and<00:23:00.960> you<00:23:01.080> can<00:23:01.200> think<00:23:01.320> of<00:23:01.440> shield<00:23:01.620> as<00:23:01.919> hard<00:23:02.100> hat 00:23:02.450 --> 00:23:02.460 align:start position:0% and you can think of shield as hard hat 00:23:02.460 --> 00:23:05.930 align:start position:0% and you can think of shield as hard hat or<00:23:02.580> maybe<00:23:02.760> truffle<00:23:03.299> for<00:23:04.080> circon<00:23:04.940> essentially 00:23:05.930 --> 00:23:05.940 align:start position:0% or maybe truffle for circon essentially 00:23:05.940 --> 00:23:08.750 align:start position:0% or maybe truffle for circon essentially it<00:23:07.020> um<00:23:07.080> takes<00:23:07.799> you'll<00:23:08.100> see<00:23:08.280> in<00:23:08.580> the<00:23:08.700> battle 00:23:08.750 --> 00:23:08.760 align:start position:0% it um takes you'll see in the battle 00:23:08.760 --> 00:23:10.909 align:start position:0% it um takes you'll see in the battle Zips<00:23:09.179> code<00:23:09.419> base<00:23:09.600> there<00:23:10.440> are<00:23:10.559> a<00:23:10.679> couple<00:23:10.799> of 00:23:10.909 --> 00:23:10.919 align:start position:0% Zips code base there are a couple of 00:23:10.919 --> 00:23:13.310 align:start position:0% Zips code base there are a couple of bash<00:23:11.159> files<00:23:11.640> that<00:23:11.940> handle<00:23:12.360> the<00:23:12.539> generation<00:23:12.960> of 00:23:13.310 --> 00:23:13.320 align:start position:0% bash files that handle the generation of 00:23:13.320 --> 00:23:16.070 align:start position:0% bash files that handle the generation of circuits<00:23:13.919> and<00:23:14.820> this<00:23:15.240> is<00:23:15.360> something<00:23:15.600> that 00:23:16.070 --> 00:23:16.080 align:start position:0% circuits and this is something that 00:23:16.080 --> 00:23:17.870 align:start position:0% circuits and this is something that requires<00:23:16.860> an<00:23:17.039> understanding<00:23:17.460> of<00:23:17.580> what<00:23:17.760> you're 00:23:17.870 --> 00:23:17.880 align:start position:0% requires an understanding of what you're 00:23:17.880 --> 00:23:20.390 align:start position:0% requires an understanding of what you're doing<00:23:18.059> whereas<00:23:19.020> The<00:23:19.260> Shield<00:23:19.380> CLI<00:23:19.980> will<00:23:20.220> just 00:23:20.390 --> 00:23:20.400 align:start position:0% doing whereas The Shield CLI will just 00:23:20.400 --> 00:23:22.730 align:start position:0% doing whereas The Shield CLI will just do<00:23:20.640> this<00:23:20.760> for<00:23:21.000> you<00:23:21.179> so<00:23:21.720> whether<00:23:22.260> you're 00:23:22.730 --> 00:23:22.740 align:start position:0% do this for you so whether you're 00:23:22.740 --> 00:23:24.590 align:start position:0% do this for you so whether you're already<00:23:22.980> experienced<00:23:23.580> with<00:23:23.880> the<00:23:24.000> circums<00:23:24.539> and 00:23:24.590 --> 00:23:24.600 align:start position:0% already experienced with the circums and 00:23:24.600 --> 00:23:27.289 align:start position:0% already experienced with the circums and arc.js<00:23:24.960> and<00:23:25.140> solidity<00:23:25.559> stack<00:23:25.860> or<00:23:26.220> you<00:23:26.520> uh<00:23:27.059> are 00:23:27.289 --> 00:23:27.299 align:start position:0% arc.js and solidity stack or you uh are 00:23:27.299 --> 00:23:29.029 align:start position:0% arc.js and solidity stack or you uh are brand<00:23:27.480> new<00:23:27.659> especially<00:23:28.200> it's<00:23:28.620> going<00:23:28.860> to<00:23:28.919> be 00:23:29.029 --> 00:23:29.039 align:start position:0% brand new especially it's going to be 00:23:29.039 --> 00:23:31.310 align:start position:0% brand new especially it's going to be very<00:23:29.640> helpful<00:23:29.880> for<00:23:30.059> kickstart<00:23:30.419> starting<00:23:30.840> a 00:23:31.310 --> 00:23:31.320 align:start position:0% very helpful for kickstart starting a 00:23:31.320 --> 00:23:33.350 align:start position:0% very helpful for kickstart starting a new<00:23:31.559> repository<00:23:32.100> and<00:23:32.700> then<00:23:32.760> there's<00:23:32.940> also<00:23:33.179> the 00:23:33.350 --> 00:23:33.360 align:start position:0% new repository and then there's also the 00:23:33.360 --> 00:23:35.630 align:start position:0% new repository and then there's also the circumspect<00:23:33.900> static<00:23:34.620> analyzer 00:23:35.630 --> 00:23:35.640 align:start position:0% circumspect static analyzer 00:23:35.640 --> 00:23:38.149 align:start position:0% circumspect static analyzer and<00:23:36.000> this<00:23:36.120> is<00:23:36.240> another<00:23:36.419> thing<00:23:36.659> in<00:23:37.080> circum<00:23:37.559> the 00:23:38.149 --> 00:23:38.159 align:start position:0% and this is another thing in circum the 00:23:38.159 --> 00:23:40.130 align:start position:0% and this is another thing in circum the debugging<00:23:38.580> and<00:23:38.700> error<00:23:39.000> messages<00:23:39.120> leave<00:23:39.780> a 00:23:40.130 --> 00:23:40.140 align:start position:0% debugging and error messages leave a 00:23:40.140 --> 00:23:42.470 align:start position:0% debugging and error messages leave a little<00:23:40.200> bit<00:23:40.320> to<00:23:40.440> be<00:23:40.620> desired<00:23:41.039> so<00:23:41.700> having<00:23:42.059> a 00:23:42.470 --> 00:23:42.480 align:start position:0% little bit to be desired so having a 00:23:42.480 --> 00:23:43.970 align:start position:0% little bit to be desired so having a tool<00:23:42.840> like<00:23:42.960> uh 00:23:43.970 --> 00:23:43.980 align:start position:0% tool like uh 00:23:43.980 --> 00:23:47.149 align:start position:0% tool like uh circumspect<00:23:44.640> to<00:23:45.320> analyze<00:23:46.320> your<00:23:46.500> code<00:23:46.679> point 00:23:47.149 --> 00:23:47.159 align:start position:0% circumspect to analyze your code point 00:23:47.159 --> 00:23:49.730 align:start position:0% circumspect to analyze your code point out<00:23:47.400> areas<00:23:48.059> where<00:23:48.299> perhaps<00:23:48.659> your<00:23:49.020> miscon 00:23:49.730 --> 00:23:49.740 align:start position:0% out areas where perhaps your miscon 00:23:49.740 --> 00:23:51.649 align:start position:0% out areas where perhaps your miscon training<00:23:50.179> misconstraining<00:23:51.179> something<00:23:51.360> or 00:23:51.649 --> 00:23:51.659 align:start position:0% training misconstraining something or 00:23:51.659 --> 00:23:53.390 align:start position:0% training misconstraining something or you're<00:23:51.840> just<00:23:52.020> not<00:23:52.260> correctly<00:23:52.860> writing<00:23:53.280> code 00:23:53.390 --> 00:23:53.400 align:start position:0% you're just not correctly writing code 00:23:53.400 --> 00:23:56.210 align:start position:0% you're just not correctly writing code is<00:23:53.640> is<00:23:53.820> very<00:23:54.120> valuable<00:23:54.600> so<00:23:55.140> again<00:23:55.260> circumspect 00:23:56.210 --> 00:23:56.220 align:start position:0% is is very valuable so again circumspect 00:23:56.220 --> 00:23:59.450 align:start position:0% is is very valuable so again circumspect and<00:23:56.640> shield<00:23:56.940> CLI<00:23:57.539> very<00:23:57.960> important<00:23:58.860> and<00:23:59.340> then 00:23:59.450 --> 00:23:59.460 align:start position:0% and shield CLI very important and then 00:23:59.460 --> 00:24:02.090 align:start position:0% and shield CLI very important and then finally<00:24:00.020> implementations<00:24:01.020> we've<00:24:01.860> done<00:24:01.980> a 00:24:02.090 --> 00:24:02.100 align:start position:0% finally implementations we've done a 00:24:02.100 --> 00:24:03.409 align:start position:0% finally implementations we've done a couple<00:24:02.220> of<00:24:02.280> videos<00:24:02.460> and<00:24:02.820> we've<00:24:03.000> got<00:24:03.120> stuff<00:24:03.299> on 00:24:03.409 --> 00:24:03.419 align:start position:0% couple of videos and we've got stuff on 00:24:03.419 --> 00:24:04.430 align:start position:0% couple of videos and we've got stuff on there<00:24:03.539> so<00:24:03.659> I'm<00:24:03.780> not<00:24:03.900> really<00:24:04.020> going<00:24:04.140> to<00:24:04.260> go<00:24:04.320> into 00:24:04.430 --> 00:24:04.440 align:start position:0% there so I'm not really going to go into 00:24:04.440 --> 00:24:07.190 align:start position:0% there so I'm not really going to go into it<00:24:04.679> but<00:24:05.400> um<00:24:05.460> the<00:24:06.179> actual<00:24:06.419> specifics<00:24:06.840> of<00:24:06.960> using 00:24:07.190 --> 00:24:07.200 align:start position:0% it but um the actual specifics of using 00:24:07.200 --> 00:24:08.810 align:start position:0% it but um the actual specifics of using zircon 00:24:08.810 --> 00:24:08.820 align:start position:0% zircon 00:24:08.820 --> 00:24:10.789 align:start position:0% zircon so<00:24:09.480> now<00:24:09.720> that<00:24:09.900> we've<00:24:10.020> kind<00:24:10.200> of<00:24:10.320> gone<00:24:10.559> through 00:24:10.789 --> 00:24:10.799 align:start position:0% so now that we've kind of gone through 00:24:10.799 --> 00:24:13.970 align:start position:0% so now that we've kind of gone through uh<00:24:11.400> all<00:24:11.580> of<00:24:11.760> uh<00:24:12.360> what<00:24:12.780> that<00:24:13.200> is<00:24:13.440> uh<00:24:13.679> again<00:24:13.799> I 00:24:13.970 --> 00:24:13.980 align:start position:0% uh all of uh what that is uh again I 00:24:13.980 --> 00:24:14.930 align:start position:0% uh all of uh what that is uh again I think<00:24:14.100> there's<00:24:14.220> like<00:24:14.340> one<00:24:14.460> more<00:24:14.580> minute<00:24:14.760> so 00:24:14.930 --> 00:24:14.940 align:start position:0% think there's like one more minute so 00:24:14.940 --> 00:24:16.490 align:start position:0% think there's like one more minute so I'll<00:24:15.059> be<00:24:15.240> quick<00:24:15.360> but 00:24:16.490 --> 00:24:16.500 align:start position:0% I'll be quick but 00:24:16.500 --> 00:24:18.890 align:start position:0% I'll be quick but um we<00:24:17.100> built<00:24:17.400> uh<00:24:17.820> our<00:24:18.000> original<00:24:18.360> version<00:24:18.720> of 00:24:18.890 --> 00:24:18.900 align:start position:0% um we built uh our original version of 00:24:18.900 --> 00:24:21.230 align:start position:0% um we built uh our original version of battle<00:24:18.960> Zips<00:24:19.380> as<00:24:19.799> a<00:24:20.220> purely<00:24:20.580> a<00:24:20.940> privacy 00:24:21.230 --> 00:24:21.240 align:start position:0% battle Zips as a purely a privacy 00:24:21.240 --> 00:24:23.690 align:start position:0% battle Zips as a purely a privacy preservation<00:24:21.780> tool<00:24:22.200> and<00:24:22.919> uh<00:24:23.159> this<00:24:23.340> is<00:24:23.460> mostly 00:24:23.690 --> 00:24:23.700 align:start position:0% preservation tool and uh this is mostly 00:24:23.700 --> 00:24:24.950 align:start position:0% preservation tool and uh this is mostly what<00:24:23.880> we've<00:24:24.120> been<00:24:24.240> speaking<00:24:24.539> to<00:24:24.659> you<00:24:24.780> about 00:24:24.950 --> 00:24:24.960 align:start position:0% what we've been speaking to you about 00:24:24.960 --> 00:24:28.010 align:start position:0% what we've been speaking to you about today<00:24:25.260> uh<00:24:25.679> circum<00:24:26.220> so<00:24:27.000> this<00:24:27.600> essentially 00:24:28.010 --> 00:24:28.020 align:start position:0% today uh circum so this essentially 00:24:28.020 --> 00:24:30.409 align:start position:0% today uh circum so this essentially allowed<00:24:28.320> us<00:24:28.380> to<00:24:28.559> prove<00:24:28.799> uh<00:24:29.039> an<00:24:29.280> adversarial<00:24:29.880> uh 00:24:30.409 --> 00:24:30.419 align:start position:0% allowed us to prove uh an adversarial uh 00:24:30.419 --> 00:24:32.570 align:start position:0% allowed us to prove uh an adversarial uh interaction<00:24:30.960> between<00:24:31.620> two<00:24:31.919> parties<00:24:32.280> where 00:24:32.570 --> 00:24:32.580 align:start position:0% interaction between two parties where 00:24:32.580 --> 00:24:34.430 align:start position:0% interaction between two parties where they<00:24:32.760> could<00:24:32.880> still<00:24:33.059> trust<00:24:33.419> each<00:24:33.600> other<00:24:33.720> uh 00:24:34.430 --> 00:24:34.440 align:start position:0% they could still trust each other uh 00:24:34.440 --> 00:24:35.450 align:start position:0% they could still trust each other uh without<00:24:34.620> revealing<00:24:35.039> all<00:24:35.159> this<00:24:35.340> information 00:24:35.450 --> 00:24:35.460 align:start position:0% without revealing all this information 00:24:35.460 --> 00:24:38.330 align:start position:0% without revealing all this information so<00:24:36.059> it<00:24:36.600> was<00:24:36.780> a<00:24:37.080> great<00:24:37.200> proof<00:24:37.559> of<00:24:37.679> concept<00:24:38.039> for 00:24:38.330 --> 00:24:38.340 align:start position:0% so it was a great proof of concept for 00:24:38.340 --> 00:24:40.190 align:start position:0% so it was a great proof of concept for us<00:24:38.460> to<00:24:38.760> demonstrate 00:24:40.190 --> 00:24:40.200 align:start position:0% us to demonstrate 00:24:40.200 --> 00:24:42.289 align:start position:0% us to demonstrate um<00:24:40.620> private<00:24:41.340> information<00:24:41.520> on<00:24:42.059> a<00:24:42.179> public 00:24:42.289 --> 00:24:42.299 align:start position:0% um private information on a public 00:24:42.299 --> 00:24:44.810 align:start position:0% um private information on a public blockchain<00:24:42.900> but<00:24:43.440> it<00:24:43.559> fell<00:24:43.679> short<00:24:43.919> in<00:24:44.159> a<00:24:44.280> lot<00:24:44.700> of 00:24:44.810 --> 00:24:44.820 align:start position:0% blockchain but it fell short in a lot of 00:24:44.820 --> 00:24:46.850 align:start position:0% blockchain but it fell short in a lot of ways<00:24:45.059> the<00:24:45.480> scalability<00:24:45.960> is<00:24:46.200> pretty<00:24:46.440> trash<00:24:46.620> to 00:24:46.850 --> 00:24:46.860 align:start position:0% ways the scalability is pretty trash to 00:24:46.860 --> 00:24:49.730 align:start position:0% ways the scalability is pretty trash to be<00:24:46.980> honest<00:24:47.280> and<00:24:48.000> um<00:24:48.480> the<00:24:49.080> intermediate<00:24:49.500> state 00:24:49.730 --> 00:24:49.740 align:start position:0% be honest and um the intermediate state 00:24:49.740 --> 00:24:51.950 align:start position:0% be honest and um the intermediate state so<00:24:50.220> you're<00:24:50.580> still<00:24:50.820> hiding<00:24:51.600> the<00:24:51.780> ship 00:24:51.950 --> 00:24:51.960 align:start position:0% so you're still hiding the ship 00:24:51.960 --> 00:24:55.130 align:start position:0% so you're still hiding the ship positions<00:24:52.440> but<00:24:53.100> um<00:24:53.400> hits<00:24:53.880> and<00:24:54.120> misses<00:24:54.480> all<00:24:55.020> the 00:24:55.130 --> 00:24:55.140 align:start position:0% positions but um hits and misses all the 00:24:55.140 --> 00:24:56.990 align:start position:0% positions but um hits and misses all the different<00:24:55.320> turns<00:24:55.740> in<00:24:55.919> a<00:24:56.100> game<00:24:56.220> all<00:24:56.820> that's 00:24:56.990 --> 00:24:57.000 align:start position:0% different turns in a game all that's 00:24:57.000 --> 00:24:59.570 align:start position:0% different turns in a game all that's public<00:24:57.360> so<00:24:58.200> moving<00:24:58.620> on<00:24:58.740> what<00:24:59.159> we're<00:24:59.340> now 00:24:59.570 --> 00:24:59.580 align:start position:0% public so moving on what we're now 00:24:59.580 --> 00:25:01.430 align:start position:0% public so moving on what we're now working<00:24:59.820> on<00:25:00.000> with<00:25:00.360> the<00:25:00.539> assistance<00:25:00.960> of<00:25:01.320> the 00:25:01.430 --> 00:25:01.440 align:start position:0% working on with the assistance of the 00:25:01.440 --> 00:25:03.590 align:start position:0% working on with the assistance of the ethereum<00:25:01.799> foundation<00:25:02.220> through<00:25:02.700> the<00:25:02.880> grant<00:25:03.120> is 00:25:03.590 --> 00:25:03.600 align:start position:0% ethereum foundation through the grant is 00:25:03.600 --> 00:25:06.470 align:start position:0% ethereum foundation through the grant is Battle<00:25:03.840> Zips<00:25:04.200> V2<00:25:04.559> and<00:25:05.039> this<00:25:05.400> is<00:25:05.700> a<00:25:06.059> little<00:25:06.240> more 00:25:06.470 --> 00:25:06.480 align:start position:0% Battle Zips V2 and this is a little more 00:25:06.480 --> 00:25:08.149 align:start position:0% Battle Zips V2 and this is a little more uh<00:25:07.020> exciting<00:25:07.440> and<00:25:07.500> novel<00:25:07.799> we<00:25:07.980> think 00:25:08.149 --> 00:25:08.159 align:start position:0% uh exciting and novel we think 00:25:08.159 --> 00:25:11.630 align:start position:0% uh exciting and novel we think essentially<00:25:09.320> we<00:25:10.320> want<00:25:10.440> to<00:25:10.679> demonstrate<00:25:11.100> using 00:25:11.630 --> 00:25:11.640 align:start position:0% essentially we want to demonstrate using 00:25:11.640 --> 00:25:15.049 align:start position:0% essentially we want to demonstrate using battleships<00:25:12.360> the<00:25:13.320> generation<00:25:13.740> of<00:25:14.280> State<00:25:14.640> in<00:25:14.940> a 00:25:15.049 --> 00:25:15.059 align:start position:0% battleships the generation of State in a 00:25:15.059 --> 00:25:17.270 align:start position:0% battleships the generation of State in a state<00:25:15.240> Channel<00:25:15.419> off<00:25:15.960> chain<00:25:16.260> and<00:25:16.919> then<00:25:17.039> we 00:25:17.270 --> 00:25:17.280 align:start position:0% state Channel off chain and then we 00:25:17.280 --> 00:25:19.850 align:start position:0% state Channel off chain and then we summarize<00:25:17.700> the<00:25:17.940> entire<00:25:18.179> State<00:25:18.419> channel<00:25:18.720> in<00:25:19.679> a 00:25:19.850 --> 00:25:19.860 align:start position:0% summarize the entire State channel in a 00:25:19.860 --> 00:25:21.970 align:start position:0% summarize the entire State channel in a single<00:25:20.039> transaction<00:25:20.400> using<00:25:20.940> zero<00:25:21.299> knowledge 00:25:21.970 --> 00:25:21.980 align:start position:0% single transaction using zero knowledge 00:25:21.980 --> 00:25:25.610 align:start position:0% single transaction using zero knowledge and<00:25:22.980> what<00:25:23.340> this<00:25:23.460> allows<00:25:23.820> us<00:25:23.940> to<00:25:24.059> do<00:25:24.179> is<00:25:24.480> produce 00:25:25.610 --> 00:25:25.620 align:start position:0% and what this allows us to do is produce 00:25:25.620 --> 00:25:28.370 align:start position:0% and what this allows us to do is produce these<00:25:26.580> interesting<00:25:26.940> truths<00:25:27.299> so<00:25:27.419> you<00:25:27.659> get<00:25:28.080> this 00:25:28.370 --> 00:25:28.380 align:start position:0% these interesting truths so you get this 00:25:28.380 --> 00:25:31.310 align:start position:0% these interesting truths so you get this uh<00:25:29.220> almost<00:25:29.580> immutable<00:25:30.179> or<00:25:30.480> indivisible 00:25:31.310 --> 00:25:31.320 align:start position:0% uh almost immutable or indivisible 00:25:31.320 --> 00:25:33.710 align:start position:0% uh almost immutable or indivisible object<00:25:31.679> a<00:25:32.220> battleship<00:25:32.640> game<00:25:33.299> valid 00:25:33.710 --> 00:25:33.720 align:start position:0% object a battleship game valid 00:25:33.720 --> 00:25:35.390 align:start position:0% object a battleship game valid Battleship<00:25:34.020> game<00:25:34.200> occurred<00:25:34.620> between<00:25:34.860> Alice 00:25:35.390 --> 00:25:35.400 align:start position:0% Battleship game occurred between Alice 00:25:35.400 --> 00:25:37.789 align:start position:0% Battleship game occurred between Alice and<00:25:35.520> Bob<00:25:35.640> where<00:25:35.820> Alice<00:25:36.059> was<00:25:36.539> lost<00:25:37.440> we'll<00:25:37.679> talk 00:25:37.789 --> 00:25:37.799 align:start position:0% and Bob where Alice was lost we'll talk 00:25:37.799 --> 00:25:39.289 align:start position:0% and Bob where Alice was lost we'll talk about<00:25:37.919> that<00:25:38.100> in<00:25:38.220> a<00:25:38.340> second<00:25:38.460> but<00:25:39.299> um 00:25:39.289 --> 00:25:39.299 align:start position:0% about that in a second but um 00:25:39.299 --> 00:25:41.450 align:start position:0% about that in a second but um essentially<00:25:40.140> this<00:25:40.320> benefits<00:25:40.740> both<00:25:40.860> privacy 00:25:41.450 --> 00:25:41.460 align:start position:0% essentially this benefits both privacy 00:25:41.460 --> 00:25:43.370 align:start position:0% essentially this benefits both privacy in<00:25:41.760> that<00:25:41.940> you<00:25:42.179> have<00:25:42.419> the<00:25:42.840> intermediate<00:25:43.260> state 00:25:43.370 --> 00:25:43.380 align:start position:0% in that you have the intermediate state 00:25:43.380 --> 00:25:45.950 align:start position:0% in that you have the intermediate state shield<00:25:43.620> and<00:25:43.919> scalability<00:25:44.460> in<00:25:44.700> that<00:25:45.360> um<00:25:45.360> you're 00:25:45.950 --> 00:25:45.960 align:start position:0% shield and scalability in that um you're 00:25:45.960 --> 00:25:48.169 align:start position:0% shield and scalability in that um you're batching<00:25:46.380> all<00:25:46.500> these<00:25:46.679> transactions<00:25:47.220> and<00:25:48.179> um 00:25:48.169 --> 00:25:48.179 align:start position:0% batching all these transactions and um 00:25:48.179 --> 00:25:50.510 align:start position:0% batching all these transactions and um we<00:25:48.840> intend<00:25:49.260> to<00:25:49.380> demonstrate<00:25:49.860> how<00:25:50.100> that<00:25:50.220> can<00:25:50.400> be 00:25:50.510 --> 00:25:50.520 align:start position:0% we intend to demonstrate how that can be 00:25:50.520 --> 00:25:52.909 align:start position:0% we intend to demonstrate how that can be used<00:25:50.760> to<00:25:51.059> drive<00:25:51.840> qualitative<00:25:52.380> insights 00:25:52.909 --> 00:25:52.919 align:start position:0% used to drive qualitative insights 00:25:52.919 --> 00:25:55.250 align:start position:0% used to drive qualitative insights without<00:25:53.159> revealing<00:25:54.059> a<00:25:54.600> ton<00:25:54.720> of<00:25:54.840> like<00:25:55.080> personal 00:25:55.250 --> 00:25:55.260 align:start position:0% without revealing a ton of like personal 00:25:55.260 --> 00:25:59.090 align:start position:0% without revealing a ton of like personal information<00:25:56.059> using<00:25:57.059> ELO<00:25:57.419> scores<00:25:57.740> so<00:25:58.740> I<00:25:58.919> think 00:25:59.090 --> 00:25:59.100 align:start position:0% information using ELO scores so I think 00:25:59.100 --> 00:26:00.529 align:start position:0% information using ELO scores so I think we'll<00:25:59.279> just<00:25:59.400> skip<00:25:59.580> to<00:25:59.760> the<00:25:59.880> next<00:25:59.940> slide<00:26:00.240> but 00:26:00.529 --> 00:26:00.539 align:start position:0% we'll just skip to the next slide but 00:26:00.539 --> 00:26:02.750 align:start position:0% we'll just skip to the next slide but because<00:26:00.779> it's<00:26:01.080> kind<00:26:01.320> of<00:26:01.440> the<00:26:01.559> same<00:26:01.740> thing 00:26:02.750 --> 00:26:02.760 align:start position:0% because it's kind of the same thing 00:26:02.760 --> 00:26:05.930 align:start position:0% because it's kind of the same thing um<00:26:02.880> again<00:26:03.480> uh<00:26:04.200> battle<00:26:04.620> Zips<00:26:04.919> and<00:26:05.159> and<00:26:05.340> Zips<00:26:05.700> is 00:26:05.930 --> 00:26:05.940 align:start position:0% um again uh battle Zips and and Zips is 00:26:05.940 --> 00:26:08.930 align:start position:0% um again uh battle Zips and and Zips is a<00:26:06.179> kind<00:26:06.419> of<00:26:06.539> data<00:26:06.840> structure<00:26:07.159> is<00:26:08.159> uh<00:26:08.640> basically 00:26:08.930 --> 00:26:08.940 align:start position:0% a kind of data structure is uh basically 00:26:08.940 --> 00:26:10.370 align:start position:0% a kind of data structure is uh basically State<00:26:09.179> Channel<00:26:09.360> summary 00:26:10.370 --> 00:26:10.380 align:start position:0% State Channel summary 00:26:10.380 --> 00:26:12.409 align:start position:0% State Channel summary um<00:26:10.440> where<00:26:10.860> we're<00:26:11.220> rolling<00:26:11.640> up<00:26:11.880> all<00:26:12.120> of<00:26:12.299> the 00:26:12.409 --> 00:26:12.419 align:start position:0% um where we're rolling up all of the 00:26:12.419 --> 00:26:14.210 align:start position:0% um where we're rolling up all of the state<00:26:12.600> that<00:26:12.900> we<00:26:13.020> generate<00:26:13.380> in<00:26:13.860> like<00:26:14.039> a 00:26:14.210 --> 00:26:14.220 align:start position:0% state that we generate in like a 00:26:14.220 --> 00:26:17.029 align:start position:0% state that we generate in like a ephemeral<00:26:14.700> Layer<00:26:15.120> Two<00:26:15.500> we<00:26:16.500> collapse<00:26:16.799> it<00:26:16.919> back 00:26:17.029 --> 00:26:17.039 align:start position:0% ephemeral Layer Two we collapse it back 00:26:17.039 --> 00:26:19.130 align:start position:0% ephemeral Layer Two we collapse it back onto<00:26:17.340> layer<00:26:17.580> one<00:26:17.700> as<00:26:18.480> soon<00:26:18.600> as<00:26:18.720> the<00:26:18.900> state 00:26:19.130 --> 00:26:19.140 align:start position:0% onto layer one as soon as the state 00:26:19.140 --> 00:26:21.830 align:start position:0% onto layer one as soon as the state generation<00:26:19.500> is<00:26:19.740> done<00:26:19.919> and<00:26:21.299> um<00:26:21.299> we<00:26:21.720> already 00:26:21.830 --> 00:26:21.840 align:start position:0% generation is done and um we already 00:26:21.840 --> 00:26:23.390 align:start position:0% generation is done and um we already talked<00:26:22.140> about<00:26:22.200> the<00:26:22.380> battleship<00:26:22.799> Battleship 00:26:23.390 --> 00:26:23.400 align:start position:0% talked about the battleship Battleship 00:26:23.400 --> 00:26:25.310 align:start position:0% talked about the battleship Battleship proof<00:26:23.760> but<00:26:23.940> uh<00:26:24.240> there<00:26:24.419> are<00:26:24.539> a<00:26:24.539> couple<00:26:24.659> of<00:26:24.840> more 00:26:25.310 --> 00:26:25.320 align:start position:0% proof but uh there are a couple of more 00:26:25.320 --> 00:26:27.769 align:start position:0% proof but uh there are a couple of more real<00:26:25.559> world<00:26:25.740> examples<00:26:26.279> that<00:26:27.120> um<00:26:27.120> are<00:26:27.419> exciting 00:26:27.769 --> 00:26:27.779 align:start position:0% real world examples that um are exciting 00:26:27.779 --> 00:26:31.789 align:start position:0% real world examples that um are exciting to<00:26:27.900> us<00:26:28.440> take<00:26:29.039> proof<00:26:29.580> of<00:26:29.640> a<00:26:29.760> valid<00:26:30.059> delivery<00:26:30.799> you 00:26:31.789 --> 00:26:31.799 align:start position:0% to us take proof of a valid delivery you 00:26:31.799 --> 00:26:32.690 align:start position:0% to us take proof of a valid delivery you know<00:26:31.860> there's<00:26:32.039> a<00:26:32.159> bunch<00:26:32.279> of<00:26:32.400> different<00:26:32.520> parts 00:26:32.690 --> 00:26:32.700 align:start position:0% know there's a bunch of different parts 00:26:32.700 --> 00:26:34.870 align:start position:0% know there's a bunch of different parts that<00:26:32.940> go<00:26:33.059> into<00:26:33.179> it<00:26:33.360> perhaps<00:26:33.720> there's<00:26:33.960> iot 00:26:34.870 --> 00:26:34.880 align:start position:0% that go into it perhaps there's iot 00:26:34.880 --> 00:26:38.090 align:start position:0% that go into it perhaps there's iot temperature<00:26:35.880> controls<00:26:36.539> or<00:26:36.960> perhaps<00:26:37.440> there's 00:26:38.090 --> 00:26:38.100 align:start position:0% temperature controls or perhaps there's 00:26:38.100 --> 00:26:39.649 align:start position:0% temperature controls or perhaps there's an<00:26:38.340> inertial<00:26:38.700> sensor<00:26:39.059> on<00:26:39.240> something<00:26:39.419> that's 00:26:39.649 --> 00:26:39.659 align:start position:0% an inertial sensor on something that's 00:26:39.659 --> 00:26:41.630 align:start position:0% an inertial sensor on something that's fragile<00:26:40.080> and<00:26:40.200> can't<00:26:40.320> be<00:26:40.500> moving<00:26:40.740> in<00:26:40.860> transit 00:26:41.630 --> 00:26:41.640 align:start position:0% fragile and can't be moving in transit 00:26:41.640 --> 00:26:43.610 align:start position:0% fragile and can't be moving in transit chain<00:26:41.940> of<00:26:42.179> custody<00:26:42.419> whatever<00:26:42.720> you<00:26:43.020> decide<00:26:43.380> is 00:26:43.610 --> 00:26:43.620 align:start position:0% chain of custody whatever you decide is 00:26:43.620 --> 00:26:48.169 align:start position:0% chain of custody whatever you decide is necessary<00:26:44.240> for<00:26:45.240> your<00:26:45.840> supply<00:26:46.559> chain<00:26:47.059> you<00:26:48.059> can 00:26:48.169 --> 00:26:48.179 align:start position:0% necessary for your supply chain you can 00:26:48.179 --> 00:26:50.149 align:start position:0% necessary for your supply chain you can then<00:26:48.360> package<00:26:48.779> that<00:26:48.960> into<00:26:49.200> a<00:26:49.500> single<00:26:49.740> proof<00:26:50.039> of 00:26:50.149 --> 00:26:50.159 align:start position:0% then package that into a single proof of 00:26:50.159 --> 00:26:53.630 align:start position:0% then package that into a single proof of delivery<00:26:50.580> and<00:26:51.419> what<00:26:52.320> that<00:26:52.740> uh<00:26:53.159> the 00:26:53.630 --> 00:26:53.640 align:start position:0% delivery and what that uh the 00:26:53.640 --> 00:26:55.250 align:start position:0% delivery and what that uh the consequence<00:26:53.940> of<00:26:54.120> that<00:26:54.240> is<00:26:54.480> that<00:26:54.720> the 00:26:55.250 --> 00:26:55.260 align:start position:0% consequence of that is that the 00:26:55.260 --> 00:26:57.350 align:start position:0% consequence of that is that the participants<00:26:55.799> in<00:26:56.220> this<00:26:56.340> say<00:26:56.820> the<00:26:56.940> delivery 00:26:57.350 --> 00:26:57.360 align:start position:0% participants in this say the delivery 00:26:57.360 --> 00:26:58.909 align:start position:0% participants in this say the delivery drivers<00:26:57.659> who<00:26:57.840> have<00:26:57.960> no<00:26:58.200> interest<00:26:58.380> in<00:26:58.740> being 00:26:58.909 --> 00:26:58.919 align:start position:0% drivers who have no interest in being 00:26:58.919 --> 00:27:01.130 align:start position:0% drivers who have no interest in being doxed<00:26:59.400> on<00:26:59.520> chain<00:26:59.700> uh<00:27:00.600> don't<00:27:00.779> have<00:27:00.960> to<00:27:01.080> be 00:27:01.130 --> 00:27:01.140 align:start position:0% doxed on chain uh don't have to be 00:27:01.140 --> 00:27:02.690 align:start position:0% doxed on chain uh don't have to be docked<00:27:01.380> on<00:27:01.440> chain<00:27:01.559> you<00:27:01.679> you<00:27:02.100> can<00:27:02.220> start<00:27:02.400> to 00:27:02.690 --> 00:27:02.700 align:start position:0% docked on chain you you can start to 00:27:02.700 --> 00:27:04.789 align:start position:0% docked on chain you you can start to involve<00:27:03.120> them<00:27:03.299> in<00:27:03.539> these<00:27:03.720> economies<00:27:04.140> without 00:27:04.789 --> 00:27:04.799 align:start position:0% involve them in these economies without 00:27:04.799 --> 00:27:07.070 align:start position:0% involve them in these economies without them<00:27:05.340> being<00:27:05.700> exposed<00:27:06.299> to<00:27:06.480> all<00:27:06.720> these<00:27:06.900> negative 00:27:07.070 --> 00:27:07.080 align:start position:0% them being exposed to all these negative 00:27:07.080 --> 00:27:08.810 align:start position:0% them being exposed to all these negative externalities<00:27:07.740> that<00:27:07.980> web3<00:27:08.400> currently 00:27:08.810 --> 00:27:08.820 align:start position:0% externalities that web3 currently 00:27:08.820 --> 00:27:11.810 align:start position:0% externalities that web3 currently exposes<00:27:09.659> us<00:27:09.779> to<00:27:09.960> and<00:27:10.860> again<00:27:11.400> just<00:27:11.640> another 00:27:11.810 --> 00:27:11.820 align:start position:0% exposes us to and again just another 00:27:11.820 --> 00:27:13.970 align:start position:0% exposes us to and again just another example<00:27:12.179> which<00:27:12.480> is<00:27:12.659> a<00:27:13.020> little<00:27:13.320> less<00:27:13.620> novel 00:27:13.970 --> 00:27:13.980 align:start position:0% example which is a little less novel 00:27:13.980 --> 00:27:15.649 align:start position:0% example which is a little less novel obviously<00:27:14.400> there's<00:27:14.640> you<00:27:15.179> know<00:27:15.240> snapshot 00:27:15.649 --> 00:27:15.659 align:start position:0% obviously there's you know snapshot 00:27:15.659 --> 00:27:17.930 align:start position:0% obviously there's you know snapshot which<00:27:15.900> is<00:27:16.020> somewhat<00:27:16.320> centralized<00:27:16.799> but 00:27:17.930 --> 00:27:17.940 align:start position:0% which is somewhat centralized but 00:27:17.940 --> 00:27:18.649 align:start position:0% which is somewhat centralized but um 00:27:18.649 --> 00:27:18.659 align:start position:0% um 00:27:18.659 --> 00:27:21.289 align:start position:0% um essentially<00:27:19.140> we<00:27:19.500> can<00:27:19.620> uh<00:27:20.159> you<00:27:20.340> know<00:27:20.460> take<00:27:21.059> this 00:27:21.289 --> 00:27:21.299 align:start position:0% essentially we can uh you know take this 00:27:21.299 --> 00:27:22.250 align:start position:0% essentially we can uh you know take this entire 00:27:22.250 --> 00:27:22.260 align:start position:0% entire 00:27:22.260 --> 00:27:25.549 align:start position:0% entire um uh<00:27:23.159> voting<00:27:23.640> process<00:27:23.880> off<00:27:24.240> chain<00:27:24.480> I<00:27:25.260> assume 00:27:25.549 --> 00:27:25.559 align:start position:0% um uh voting process off chain I assume 00:27:25.559 --> 00:27:26.750 align:start position:0% um uh voting process off chain I assume it<00:27:25.620> probably<00:27:25.799> looks<00:27:25.980> a<00:27:26.039> lot<00:27:26.100> like<00:27:26.220> Macy<00:27:26.580> too 00:27:26.750 --> 00:27:26.760 align:start position:0% it probably looks a lot like Macy too 00:27:26.760 --> 00:27:30.830 align:start position:0% it probably looks a lot like Macy too actually<00:27:27.000> in<00:27:27.539> in<00:27:28.200> um<00:27:28.620> premise<00:27:29.580> but<00:27:29.820> instead<00:27:30.779> of 00:27:30.830 --> 00:27:30.840 align:start position:0% actually in in um premise but instead of 00:27:30.840 --> 00:27:32.390 align:start position:0% actually in in um premise but instead of it<00:27:31.559> occurring<00:27:31.919> all<00:27:32.100> of<00:27:32.220> the<00:27:32.279> state 00:27:32.390 --> 00:27:32.400 align:start position:0% it occurring all of the state 00:27:32.400 --> 00:27:34.070 align:start position:0% it occurring all of the state accumulating<00:27:32.940> on<00:27:33.120> chain 00:27:34.070 --> 00:27:34.080 align:start position:0% accumulating on chain 00:27:34.080 --> 00:27:37.730 align:start position:0% accumulating on chain um<00:27:34.140> where<00:27:34.679> uh<00:27:35.520> in<00:27:36.059> in<00:27:36.120> Malik<00:27:36.539> style<00:27:36.720> uh<00:27:37.320> it's 00:27:37.730 --> 00:27:37.740 align:start position:0% um where uh in in Malik style uh it's 00:27:37.740 --> 00:27:39.830 align:start position:0% um where uh in in Malik style uh it's it's<00:27:37.919> all<00:27:38.159> even<00:27:38.400> public<00:27:38.820> uh<00:27:39.419> we<00:27:39.720> are 00:27:39.830 --> 00:27:39.840 align:start position:0% it's all even public uh we are 00:27:39.840 --> 00:27:42.110 align:start position:0% it's all even public uh we are accumulating<00:27:40.320> uh<00:27:40.679> the<00:27:40.860> vote<00:27:41.039> off<00:27:41.279> chain<00:27:41.580> and 00:27:42.110 --> 00:27:42.120 align:start position:0% accumulating uh the vote off chain and 00:27:42.120 --> 00:27:44.810 align:start position:0% accumulating uh the vote off chain and then<00:27:42.179> rolling<00:27:42.600> up<00:27:42.779> uh<00:27:43.440> a<00:27:43.620> proof<00:27:43.919> that<00:27:44.220> a<00:27:44.400> vote 00:27:44.810 --> 00:27:44.820 align:start position:0% then rolling up uh a proof that a vote 00:27:44.820 --> 00:27:47.029 align:start position:0% then rolling up uh a proof that a vote occurred<00:27:45.299> on<00:27:45.480> this<00:27:45.779> proposal<00:27:46.200> where<00:27:46.620> 65 00:27:47.029 --> 00:27:47.039 align:start position:0% occurred on this proposal where 65 00:27:47.039 --> 00:27:48.649 align:start position:0% occurred on this proposal where 65 percent<00:27:47.220> of<00:27:47.400> stakeholders<00:27:47.880> approved<00:27:48.240> it<00:27:48.360> or 00:27:48.649 --> 00:27:48.659 align:start position:0% percent of stakeholders approved it or 00:27:48.659 --> 00:27:51.649 align:start position:0% percent of stakeholders approved it or 65<00:27:49.020> of<00:27:49.440> Governors<00:27:49.740> or<00:27:49.919> whatever<00:27:50.220> so<00:27:51.120> uh<00:27:51.480> it 00:27:51.649 --> 00:27:51.659 align:start position:0% 65 of Governors or whatever so uh it 00:27:51.659 --> 00:27:53.330 align:start position:0% 65 of Governors or whatever so uh it creates<00:27:51.900> these<00:27:52.080> kind<00:27:52.200> of<00:27:52.260> indivisible<00:27:52.860> proofs 00:27:53.330 --> 00:27:53.340 align:start position:0% creates these kind of indivisible proofs 00:27:53.340 --> 00:27:55.370 align:start position:0% creates these kind of indivisible proofs that<00:27:53.640> uh<00:27:53.880> can<00:27:54.120> be<00:27:54.240> used<00:27:54.659> for<00:27:54.900> various<00:27:55.140> things 00:27:55.370 --> 00:27:55.380 align:start position:0% that uh can be used for various things 00:27:55.380 --> 00:27:57.950 align:start position:0% that uh can be used for various things so 00:27:57.950 --> 00:27:57.960 align:start position:0% 00:27:57.960 --> 00:27:59.090 align:start position:0% yeah 00:27:59.090 --> 00:27:59.100 align:start position:0% yeah 00:27:59.100 --> 00:28:01.720 align:start position:0% yeah um<00:27:59.220> so<00:27:59.940> if<00:28:00.120> you<00:28:00.299> guys<00:28:00.419> have<00:28:00.840> uh<00:28:01.140> any 00:28:01.720 --> 00:28:01.730 align:start position:0% um so if you guys have uh any 00:28:01.730 --> 00:28:04.029 align:start position:0% um so if you guys have uh any [Applause] 00:28:04.029 --> 00:28:04.039 align:start position:0% [Applause] 00:28:04.039 --> 00:28:06.630 align:start position:0% [Applause] thank<00:28:05.039> you 00:28:06.630 --> 00:28:06.640 align:start position:0% thank you 00:28:06.640 --> 00:28:09.169 align:start position:0% thank you [Applause] 00:28:09.169 --> 00:28:09.179 align:start position:0% [Applause] 00:28:09.179 --> 00:28:11.210 align:start position:0% [Applause] sure<00:28:09.779> yeah<00:28:10.559> um 00:28:11.210 --> 00:28:11.220 align:start position:0% sure yeah um 00:28:11.220 --> 00:28:13.669 align:start position:0% sure yeah um really<00:28:11.760> quick<00:28:11.880> any<00:28:12.179> desire<00:28:12.539> to<00:28:12.900> be<00:28:13.260> working<00:28:13.440> on 00:28:13.669 --> 00:28:13.679 align:start position:0% really quick any desire to be working on 00:28:13.679 --> 00:28:15.110 align:start position:0% really quick any desire to be working on this<00:28:13.799> and<00:28:14.039> you're<00:28:14.159> struggling<00:28:14.580> to<00:28:14.940> get 00:28:15.110 --> 00:28:15.120 align:start position:0% this and you're struggling to get 00:28:15.120 --> 00:28:16.070 align:start position:0% this and you're struggling to get started 00:28:16.070 --> 00:28:16.080 align:start position:0% started 00:28:16.080 --> 00:28:18.950 align:start position:0% started um we<00:28:16.500> have<00:28:16.679> I<00:28:17.039> think<00:28:17.159> in<00:28:17.640> uh<00:28:18.059> the<00:28:18.419> battle<00:28:18.600> Zips 00:28:18.950 --> 00:28:18.960 align:start position:0% um we have I think in uh the battle Zips 00:28:18.960 --> 00:28:20.990 align:start position:0% um we have I think in uh the battle Zips resources<00:28:19.320> we<00:28:19.440> have<00:28:19.559> a<00:28:19.620> link<00:28:19.740> to<00:28:19.860> our<00:28:19.980> Discord 00:28:20.990 --> 00:28:21.000 align:start position:0% resources we have a link to our Discord 00:28:21.000 --> 00:28:22.070 align:start position:0% resources we have a link to our Discord um<00:28:21.059> you<00:28:21.240> can<00:28:21.360> go<00:28:21.480> in<00:28:21.600> there<00:28:21.720> and<00:28:21.840> drop 00:28:22.070 --> 00:28:22.080 align:start position:0% um you can go in there and drop 00:28:22.080 --> 00:28:23.690 align:start position:0% um you can go in there and drop literally<00:28:22.559> any<00:28:22.679> question<00:28:22.980> we'll<00:28:23.340> do<00:28:23.520> our<00:28:23.580> best 00:28:23.690 --> 00:28:23.700 align:start position:0% literally any question we'll do our best 00:28:23.700 --> 00:28:27.830 align:start position:0% literally any question we'll do our best to<00:28:23.820> answer<00:28:24.000> it 00:28:27.830 --> 00:28:27.840 align:start position:0% 00:28:27.840 --> 00:28:33.409 align:start position:0% with<00:28:28.080> the<00:28:28.320> QR 00:28:33.409 --> 00:28:33.419 align:start position:0% 00:28:33.419 --> 00:28:34.970 align:start position:0% yes<00:28:33.600> sir 00:28:34.970 --> 00:28:34.980 align:start position:0% yes sir 00:28:34.980 --> 00:28:36.470 align:start position:0% yes sir um<00:28:35.100> and<00:28:35.340> then<00:28:35.460> are<00:28:35.760> there<00:28:35.940> any<00:28:36.179> questions 00:28:36.470 --> 00:28:36.480 align:start position:0% um and then are there any questions 00:28:36.480 --> 00:28:41.210 align:start position:0% um and then are there any questions maybe<00:28:37.260> have<00:28:37.500> time<00:28:37.679> for<00:28:37.860> like<00:28:38.100> one<00:28:38.460> or<00:28:38.880> two 00:28:41.210 --> 00:28:41.220 align:start position:0% 00:28:41.220 --> 00:28:43.490 align:start position:0% okay<00:28:41.820> if<00:28:42.360> not<00:28:42.539> another<00:28:42.900> huge<00:28:43.200> round<00:28:43.260> of 00:28:43.490 --> 00:28:43.500 align:start position:0% okay if not another huge round of 00:28:43.500 --> 00:28:45.230 align:start position:0% okay if not another huge round of applause<00:28:43.799> for<00:28:43.980> Jack<00:28:44.159> and<00:28:44.340> Ian 00:28:45.230 --> 00:28:45.240 align:start position:0% applause for Jack and Ian 00:28:45.240 --> 00:28:46.120 align:start position:0% applause for Jack and Ian thank<00:28:45.659> you 00:28:46.120 --> 00:28:46.130 align:start position:0% thank you 00:28:46.130 --> 00:28:50.849 align:start position:0% thank you [Applause]