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:17.830 align:start position:0% [Music] 00:00:17.830 --> 00:00:17.840 align:start position:0% 00:00:17.840 --> 00:00:21.830 align:start position:0% welcome<00:00:18.840> back<00:00:19.199> so<00:00:20.100> our<00:00:20.640> next<00:00:20.820> speaker<00:00:21.180> is 00:00:21.830 --> 00:00:21.840 align:start position:0% welcome back so our next speaker is 00:00:21.840 --> 00:00:26.090 align:start position:0% welcome back so our next speaker is Brian<00:00:22.260> Wilkes<00:00:22.980> and<00:00:23.760> he'll<00:00:24.180> be<00:00:24.300> comparing<00:00:25.199> the 00:00:26.090 --> 00:00:26.100 align:start position:0% Brian Wilkes and he'll be comparing the 00:00:26.100 --> 00:00:28.550 align:start position:0% Brian Wilkes and he'll be comparing the performance<00:00:26.640> and<00:00:27.060> security<00:00:27.560> characteristics 00:00:28.550 --> 00:00:28.560 align:start position:0% performance and security characteristics 00:00:28.560 --> 00:00:31.370 align:start position:0% performance and security characteristics of<00:00:29.099> some<00:00:29.400> zero<00:00:29.880> knowledge<00:00:30.180> proofs<00:00:30.660> that<00:00:31.019> are 00:00:31.370 --> 00:00:31.380 align:start position:0% of some zero knowledge proofs that are 00:00:31.380 --> 00:00:33.770 align:start position:0% of some zero knowledge proofs that are commonly<00:00:32.099> deployed<00:00:32.700> in<00:00:33.300> the<00:00:33.420> ethereum 00:00:33.770 --> 00:00:33.780 align:start position:0% commonly deployed in the ethereum 00:00:33.780 --> 00:00:43.389 align:start position:0% commonly deployed in the ethereum ecosystem<00:00:34.320> so<00:00:35.280> Brian 00:00:43.389 --> 00:00:43.399 align:start position:0% 00:00:43.399 --> 00:00:47.510 align:start position:0% hello<00:00:44.399> wow<00:00:45.239> that's<00:00:45.360> loud<00:00:45.660> so 00:00:47.510 --> 00:00:47.520 align:start position:0% hello wow that's loud so 00:00:47.520 --> 00:00:50.090 align:start position:0% hello wow that's loud so who<00:00:48.180> are<00:00:48.480> my<00:00:48.660> data<00:00:49.020> scientists<00:00:49.500> in<00:00:49.860> the<00:00:49.980> room 00:00:50.090 --> 00:00:50.100 align:start position:0% who are my data scientists in the room 00:00:50.100 --> 00:00:51.709 align:start position:0% who are my data scientists in the room raise<00:00:50.700> hands 00:00:51.709 --> 00:00:51.719 align:start position:0% raise hands 00:00:51.719 --> 00:00:56.029 align:start position:0% raise hands very<00:00:52.260> few<00:00:52.879> devs<00:00:53.879> devs<00:00:54.480> out<00:00:54.660> there<00:00:54.920> lots<00:00:55.920> of 00:00:56.029 --> 00:00:56.039 align:start position:0% very few devs devs out there lots of 00:00:56.039 --> 00:00:59.209 align:start position:0% very few devs devs out there lots of devs<00:00:56.460> nice<00:00:56.820> investors<00:00:57.600> d-gens 00:00:59.209 --> 00:00:59.219 align:start position:0% devs nice investors d-gens 00:00:59.219 --> 00:01:01.430 align:start position:0% devs nice investors d-gens yes<00:00:59.760> put<00:01:00.360> it<00:01:00.539> down 00:01:01.430 --> 00:01:01.440 align:start position:0% yes put it down 00:01:01.440 --> 00:01:03.830 align:start position:0% yes put it down um<00:01:01.559> how<00:01:02.100> about<00:01:02.219> expertise 00:01:03.830 --> 00:01:03.840 align:start position:0% um how about expertise 00:01:03.840 --> 00:01:06.109 align:start position:0% um how about expertise um<00:01:03.960> who's<00:01:04.739> a<00:01:05.040> beginner<00:01:05.400> in<00:01:05.580> zero<00:01:05.880> knowledge 00:01:06.109 --> 00:01:06.119 align:start position:0% um who's a beginner in zero knowledge 00:01:06.119 --> 00:01:08.450 align:start position:0% um who's a beginner in zero knowledge just<00:01:06.540> got<00:01:06.900> the<00:01:07.080> basics 00:01:08.450 --> 00:01:08.460 align:start position:0% just got the basics 00:01:08.460 --> 00:01:11.630 align:start position:0% just got the basics cool<00:01:09.540> um<00:01:09.540> who<00:01:10.260> knows<00:01:10.619> what's<00:01:10.740> going<00:01:10.920> on<00:01:11.159> but 00:01:11.630 --> 00:01:11.640 align:start position:0% cool um who knows what's going on but 00:01:11.640 --> 00:01:15.109 align:start position:0% cool um who knows what's going on but has<00:01:12.000> not<00:01:12.180> written<00:01:12.360> a<00:01:12.540> circuit<00:01:12.840> before 00:01:15.109 --> 00:01:15.119 align:start position:0% 00:01:15.119 --> 00:01:18.410 align:start position:0% true<00:01:15.540> ZK<00:01:15.960> expert<00:01:16.380> knows<00:01:17.100> a<00:01:17.220> ton<00:01:17.340> about<00:01:17.520> ZK 00:01:18.410 --> 00:01:18.420 align:start position:0% true ZK expert knows a ton about ZK 00:01:18.420 --> 00:01:21.350 align:start position:0% true ZK expert knows a ton about ZK you<00:01:19.140> perfect<00:01:19.860> all<00:01:20.340> right 00:01:21.350 --> 00:01:21.360 align:start position:0% you perfect all right 00:01:21.360 --> 00:01:23.149 align:start position:0% you perfect all right um well<00:01:22.140> um<00:01:22.200> thanks<00:01:22.380> for<00:01:22.560> having<00:01:22.680> me<00:01:22.860> my<00:01:23.040> name 00:01:23.149 --> 00:01:23.159 align:start position:0% um well um thanks for having me my name 00:01:23.159 --> 00:01:24.230 align:start position:0% um well um thanks for having me my name is<00:01:23.280> Brian 00:01:24.230 --> 00:01:24.240 align:start position:0% is Brian 00:01:24.240 --> 00:01:26.450 align:start position:0% is Brian um<00:01:24.360> I<00:01:24.659> am<00:01:24.900> a<00:01:25.200> grantee<00:01:25.619> with<00:01:25.920> the<00:01:26.040> ethereum 00:01:26.450 --> 00:01:26.460 align:start position:0% um I am a grantee with the ethereum 00:01:26.460 --> 00:01:28.310 align:start position:0% um I am a grantee with the ethereum foundation<00:01:26.880> on<00:01:27.299> privacy<00:01:27.780> scaling 00:01:28.310 --> 00:01:28.320 align:start position:0% foundation on privacy scaling 00:01:28.320 --> 00:01:30.230 align:start position:0% foundation on privacy scaling exploration<00:01:28.799> team<00:01:29.040> so 00:01:30.230 --> 00:01:30.240 align:start position:0% exploration team so 00:01:30.240 --> 00:01:31.670 align:start position:0% exploration team so um<00:01:30.299> today<00:01:30.479> I'm<00:01:30.659> going<00:01:30.780> to<00:01:30.840> be<00:01:30.900> talking<00:01:31.080> about 00:01:31.670 --> 00:01:31.680 align:start position:0% um today I'm going to be talking about 00:01:31.680 --> 00:01:33.649 align:start position:0% um today I'm going to be talking about um ZK<00:01:32.220> proof<00:01:32.820> performance<00:01:33.240> and<00:01:33.420> security 00:01:33.649 --> 00:01:33.659 align:start position:0% um ZK proof performance and security 00:01:33.659 --> 00:01:35.990 align:start position:0% um ZK proof performance and security characteristics<00:01:34.380> so 00:01:35.990 --> 00:01:36.000 align:start position:0% characteristics so 00:01:36.000 --> 00:01:41.990 align:start position:0% characteristics so um<00:01:36.060> so<00:01:36.479> what's<00:01:36.540> in<00:01:36.720> the<00:01:36.840> docket<00:01:37.079> for<00:01:37.200> the<00:01:37.320> day 00:01:41.990 --> 00:01:42.000 align:start position:0% 00:01:42.000 --> 00:01:43.789 align:start position:0% search<00:01:42.720> for<00:01:42.960> me<00:01:43.140> to<00:01:43.200> go<00:01:43.320> over<00:01:43.320> some<00:01:43.500> background 00:01:43.789 --> 00:01:43.799 align:start position:0% search for me to go over some background 00:01:43.799 --> 00:01:45.410 align:start position:0% search for me to go over some background so<00:01:44.220> we'll<00:01:44.400> just<00:01:44.579> give<00:01:44.700> some<00:01:44.880> background<00:01:45.240> on 00:01:45.410 --> 00:01:45.420 align:start position:0% so we'll just give some background on 00:01:45.420 --> 00:01:47.810 align:start position:0% so we'll just give some background on what<00:01:45.600> zkps<00:01:46.079> are<00:01:46.439> I'm<00:01:47.220> try<00:01:47.400> and<00:01:47.460> work<00:01:47.640> through 00:01:47.810 --> 00:01:47.820 align:start position:0% what zkps are I'm try and work through 00:01:47.820 --> 00:01:49.370 align:start position:0% what zkps are I'm try and work through what<00:01:48.060> they<00:01:48.180> actually<00:01:48.360> mean<00:01:48.600> for<00:01:48.900> on-chain 00:01:49.370 --> 00:01:49.380 align:start position:0% what they actually mean for on-chain 00:01:49.380 --> 00:01:51.530 align:start position:0% what they actually mean for on-chain data 00:01:51.530 --> 00:01:51.540 align:start position:0% data 00:01:51.540 --> 00:01:53.030 align:start position:0% data then<00:01:52.020> we're<00:01:52.140> going<00:01:52.320> to<00:01:52.439> look<00:01:52.560> at<00:01:52.740> how<00:01:52.920> to 00:01:53.030 --> 00:01:53.040 align:start position:0% then we're going to look at how to 00:01:53.040 --> 00:01:54.710 align:start position:0% then we're going to look at how to actually<00:01:53.220> find<00:01:53.520> those<00:01:54.180> um<00:01:54.180> zero<00:01:54.540> knowledge 00:01:54.710 --> 00:01:54.720 align:start position:0% actually find those um zero knowledge 00:01:54.720 --> 00:01:57.410 align:start position:0% actually find those um zero knowledge proofs<00:01:55.079> and<00:01:55.200> verifiers<00:01:55.740> on<00:01:56.100> circuits<00:01:56.700> on<00:01:57.299> and 00:01:57.410 --> 00:01:57.420 align:start position:0% proofs and verifiers on circuits on and 00:01:57.420 --> 00:01:59.389 align:start position:0% proofs and verifiers on circuits on and off<00:01:57.540> chain 00:01:59.389 --> 00:01:59.399 align:start position:0% off chain 00:01:59.399 --> 00:02:00.649 align:start position:0% off chain then<00:01:59.820> we'll<00:02:00.000> look<00:02:00.180> at<00:02:00.299> some<00:02:00.420> of<00:02:00.600> the 00:02:00.649 --> 00:02:00.659 align:start position:0% then we'll look at some of the 00:02:00.659 --> 00:02:02.330 align:start position:0% then we'll look at some of the characteristics<00:02:01.200> behind<00:02:01.560> those<00:02:01.799> and<00:02:02.159> what 00:02:02.330 --> 00:02:02.340 align:start position:0% characteristics behind those and what 00:02:02.340 --> 00:02:05.090 align:start position:0% characteristics behind those and what they<00:02:02.460> mean 00:02:05.090 --> 00:02:05.100 align:start position:0% 00:02:05.100 --> 00:02:08.690 align:start position:0% so<00:02:06.140> unfortunately<00:02:07.340> Waldo's<00:02:08.340> not<00:02:08.459> going<00:02:08.580> to<00:02:08.640> be 00:02:08.690 --> 00:02:08.700 align:start position:0% so unfortunately Waldo's not going to be 00:02:08.700 --> 00:02:11.089 align:start position:0% so unfortunately Waldo's not going to be with<00:02:08.819> us<00:02:09.000> today<00:02:09.179> so<00:02:09.539> this<00:02:10.259> is<00:02:10.380> the<00:02:10.739> second<00:02:10.860> best 00:02:11.089 --> 00:02:11.099 align:start position:0% with us today so this is the second best 00:02:11.099 --> 00:02:12.530 align:start position:0% with us today so this is the second best piece<00:02:11.340> of<00:02:11.400> art<00:02:11.520> I've<00:02:11.819> ever<00:02:11.940> done<00:02:12.120> so<00:02:12.300> I<00:02:12.420> hope 00:02:12.530 --> 00:02:12.540 align:start position:0% piece of art I've ever done so I hope 00:02:12.540 --> 00:02:15.290 align:start position:0% piece of art I've ever done so I hope you<00:02:12.660> appreciate<00:02:13.020> it<00:02:13.140> everyone<00:02:13.700> so<00:02:14.700> what<00:02:15.180> are 00:02:15.290 --> 00:02:15.300 align:start position:0% you appreciate it everyone so what are 00:02:15.300 --> 00:02:17.270 align:start position:0% you appreciate it everyone so what are zkps<00:02:15.840> of<00:02:16.140> our<00:02:16.319> high<00:02:16.440> level<00:02:16.560> first<00:02:16.860> we'll<00:02:17.160> go 00:02:17.270 --> 00:02:17.280 align:start position:0% zkps of our high level first we'll go 00:02:17.280 --> 00:02:19.250 align:start position:0% zkps of our high level first we'll go through<00:02:17.400> this<00:02:17.580> quick<00:02:17.760> and<00:02:17.940> then<00:02:18.060> move<00:02:18.180> on<00:02:18.360> but 00:02:19.250 --> 00:02:19.260 align:start position:0% through this quick and then move on but 00:02:19.260 --> 00:02:22.190 align:start position:0% through this quick and then move on but um we<00:02:19.560> have<00:02:19.680> Alice<00:02:20.160> Alice<00:02:20.879> wants<00:02:21.480> a<00:02:21.540> drink 00:02:22.190 --> 00:02:22.200 align:start position:0% um we have Alice Alice wants a drink 00:02:22.200 --> 00:02:25.729 align:start position:0% um we have Alice Alice wants a drink she's<00:02:22.739> a<00:02:22.980> prover<00:02:23.280> we<00:02:24.180> have<00:02:24.300> Bob<00:02:24.660> Bob<00:02:25.260> is<00:02:25.560> the 00:02:25.729 --> 00:02:25.739 align:start position:0% she's a prover we have Bob Bob is the 00:02:25.739 --> 00:02:27.650 align:start position:0% she's a prover we have Bob Bob is the bartender<00:02:26.040> is<00:02:26.280> a<00:02:26.400> verifier 00:02:27.650 --> 00:02:27.660 align:start position:0% bartender is a verifier 00:02:27.660 --> 00:02:29.449 align:start position:0% bartender is a verifier um<00:02:27.720> Alice<00:02:28.260> does<00:02:28.560> not<00:02:28.739> want<00:02:28.860> to<00:02:29.040> give<00:02:29.160> all<00:02:29.400> of 00:02:29.449 --> 00:02:29.459 align:start position:0% um Alice does not want to give all of 00:02:29.459 --> 00:02:31.910 align:start position:0% um Alice does not want to give all of her<00:02:29.640> information<00:02:29.819> to<00:02:30.360> Bob<00:02:30.540> and<00:02:31.319> so<00:02:31.560> therefore 00:02:31.910 --> 00:02:31.920 align:start position:0% her information to Bob and so therefore 00:02:31.920 --> 00:02:35.030 align:start position:0% her information to Bob and so therefore she<00:02:32.700> can<00:02:32.879> put<00:02:33.120> in<00:02:33.360> her<00:02:33.959> birthday 00:02:35.030 --> 00:02:35.040 align:start position:0% she can put in her birthday 00:02:35.040 --> 00:02:37.430 align:start position:0% she can put in her birthday the<00:02:35.459> circuit<00:02:35.760> will<00:02:35.819> output<00:02:36.120> a<00:02:36.239> proof<00:02:36.540> Bob<00:02:37.080> can 00:02:37.430 --> 00:02:37.440 align:start position:0% the circuit will output a proof Bob can 00:02:37.440 --> 00:02:39.229 align:start position:0% the circuit will output a proof Bob can verify<00:02:37.860> that<00:02:38.040> proof<00:02:38.340> is<00:02:38.459> correct<00:02:38.760> that<00:02:38.940> she<00:02:39.120> is 00:02:39.229 --> 00:02:39.239 align:start position:0% verify that proof is correct that she is 00:02:39.239 --> 00:02:41.570 align:start position:0% verify that proof is correct that she is old<00:02:39.360> enough<00:02:39.480> to<00:02:39.720> drink<00:02:39.840> and<00:02:40.739> the<00:02:40.860> cerveza<00:02:41.400> will 00:02:41.570 --> 00:02:41.580 align:start position:0% old enough to drink and the cerveza will 00:02:41.580 --> 00:02:45.710 align:start position:0% old enough to drink and the cerveza will flow<00:02:41.819> so<00:02:43.319> um<00:02:43.379> what's<00:02:44.160> important<00:02:44.580> for<00:02:44.879> this<00:02:45.060> is 00:02:45.710 --> 00:02:45.720 align:start position:0% flow so um what's important for this is 00:02:45.720 --> 00:02:48.050 align:start position:0% flow so um what's important for this is you<00:02:46.200> have 00:02:48.050 --> 00:02:48.060 align:start position:0% you have 00:02:48.060 --> 00:02:49.610 align:start position:0% you have approver 00:02:49.610 --> 00:02:49.620 align:start position:0% approver 00:02:49.620 --> 00:02:52.009 align:start position:0% approver you<00:02:50.099> have<00:02:50.160> inputs<00:02:51.060> you<00:02:51.480> have<00:02:51.599> the<00:02:51.720> circuit 00:02:52.009 --> 00:02:52.019 align:start position:0% you have inputs you have the circuit 00:02:52.019 --> 00:02:53.990 align:start position:0% you have inputs you have the circuit itself<00:02:52.319> you<00:02:53.099> have<00:02:53.220> the<00:02:53.340> proof<00:02:53.580> popping<00:02:53.879> out 00:02:53.990 --> 00:02:54.000 align:start position:0% itself you have the proof popping out 00:02:54.000 --> 00:02:56.210 align:start position:0% itself you have the proof popping out and<00:02:54.360> then<00:02:54.540> Bob<00:02:54.840> decides<00:02:55.379> if<00:02:55.500> it's<00:02:55.680> true<00:02:55.980> or 00:02:56.210 --> 00:02:56.220 align:start position:0% and then Bob decides if it's true or 00:02:56.220 --> 00:02:58.490 align:start position:0% and then Bob decides if it's true or false<00:02:56.519> and<00:02:56.760> then<00:02:56.940> does<00:02:57.660> an<00:02:57.840> action<00:02:58.080> based<00:02:58.440> on 00:02:58.490 --> 00:02:58.500 align:start position:0% false and then does an action based on 00:02:58.500 --> 00:03:02.089 align:start position:0% false and then does an action based on whether<00:02:58.739> that<00:02:59.040> verification<00:03:00.000> is<00:03:00.239> true<00:03:00.420> so 00:03:02.089 --> 00:03:02.099 align:start position:0% whether that verification is true so 00:03:02.099 --> 00:03:03.830 align:start position:0% whether that verification is true so um<00:03:02.160> why<00:03:02.700> do<00:03:02.819> we<00:03:02.940> need<00:03:03.060> zero<00:03:03.360> knowledge<00:03:03.599> proofs 00:03:03.830 --> 00:03:03.840 align:start position:0% um why do we need zero knowledge proofs 00:03:03.840 --> 00:03:06.530 align:start position:0% um why do we need zero knowledge proofs in<00:03:03.959> ethereum<00:03:04.379> so<00:03:05.160> the<00:03:05.580> first<00:03:05.700> thing<00:03:05.940> that<00:03:06.360> we 00:03:06.530 --> 00:03:06.540 align:start position:0% in ethereum so the first thing that we 00:03:06.540 --> 00:03:09.290 align:start position:0% in ethereum so the first thing that we struggle<00:03:06.840> with<00:03:06.959> is<00:03:07.319> scalability<00:03:07.920> so 00:03:09.290 --> 00:03:09.300 align:start position:0% struggle with is scalability so 00:03:09.300 --> 00:03:12.350 align:start position:0% struggle with is scalability so right<00:03:09.900> now<00:03:10.140> we<00:03:10.739> can<00:03:10.860> do<00:03:11.040> about<00:03:11.340> on<00:03:11.879> main<00:03:12.060> chain 00:03:12.350 --> 00:03:12.360 align:start position:0% right now we can do about on main chain 00:03:12.360 --> 00:03:14.630 align:start position:0% right now we can do about on main chain 13<00:03:12.840> transactions<00:03:13.800> per<00:03:13.920> second 00:03:14.630 --> 00:03:14.640 align:start position:0% 13 transactions per second 00:03:14.640 --> 00:03:16.190 align:start position:0% 13 transactions per second um<00:03:14.700> and<00:03:15.180> we<00:03:15.300> really<00:03:15.420> need<00:03:15.599> to<00:03:15.659> get<00:03:15.780> into<00:03:15.959> that 00:03:16.190 --> 00:03:16.200 align:start position:0% um and we really need to get into that 00:03:16.200 --> 00:03:18.470 align:start position:0% um and we really need to get into that 13k<00:03:16.800> transactions<00:03:17.519> per<00:03:17.700> second<00:03:17.879> if<00:03:18.239> not 00:03:18.470 --> 00:03:18.480 align:start position:0% 13k transactions per second if not 00:03:18.480 --> 00:03:20.330 align:start position:0% 13k transactions per second if not significantly<00:03:19.080> higher<00:03:19.379> to<00:03:19.620> get<00:03:19.800> in<00:03:19.860> the<00:03:19.980> Visa 00:03:20.330 --> 00:03:20.340 align:start position:0% significantly higher to get in the Visa 00:03:20.340 --> 00:03:21.830 align:start position:0% significantly higher to get in the Visa range<00:03:20.580> so 00:03:21.830 --> 00:03:21.840 align:start position:0% range so 00:03:21.840 --> 00:03:23.570 align:start position:0% range so um how<00:03:22.500> is<00:03:22.620> your<00:03:22.739> knowledge<00:03:23.040> proofs<00:03:23.280> help<00:03:23.459> us 00:03:23.570 --> 00:03:23.580 align:start position:0% um how is your knowledge proofs help us 00:03:23.580 --> 00:03:25.070 align:start position:0% um how is your knowledge proofs help us that<00:03:23.879> you<00:03:24.060> can<00:03:24.180> separate<00:03:24.480> they<00:03:24.780> can<00:03:24.959> take 00:03:25.070 --> 00:03:25.080 align:start position:0% that you can separate they can take 00:03:25.080 --> 00:03:27.470 align:start position:0% that you can separate they can take fully<00:03:25.560> separate<00:03:25.860> chains 00:03:27.470 --> 00:03:27.480 align:start position:0% fully separate chains 00:03:27.480 --> 00:03:28.970 align:start position:0% fully separate chains um<00:03:27.599> and<00:03:27.840> they<00:03:27.959> can<00:03:28.080> impart<00:03:28.379> the<00:03:28.560> full<00:03:28.680> security 00:03:28.970 --> 00:03:28.980 align:start position:0% um and they can impart the full security 00:03:28.980 --> 00:03:31.430 align:start position:0% um and they can impart the full security of<00:03:29.280> ethereum<00:03:29.700> to<00:03:29.879> those<00:03:30.000> chains 00:03:31.430 --> 00:03:31.440 align:start position:0% of ethereum to those chains 00:03:31.440 --> 00:03:33.949 align:start position:0% of ethereum to those chains so<00:03:31.920> privacy<00:03:32.580> as<00:03:32.819> well<00:03:33.480> um<00:03:33.480> is<00:03:33.780> something 00:03:33.949 --> 00:03:33.959 align:start position:0% so privacy as well um is something 00:03:33.959 --> 00:03:36.589 align:start position:0% so privacy as well um is something that's<00:03:34.200> a<00:03:34.319> hotbed<00:03:34.680> issue<00:03:35.580> to<00:03:36.060> me<00:03:36.239> uh 00:03:36.589 --> 00:03:36.599 align:start position:0% that's a hotbed issue to me uh 00:03:36.599 --> 00:03:38.390 align:start position:0% that's a hotbed issue to me uh ethereum's<00:03:37.260> public<00:03:37.440> if<00:03:37.860> you're<00:03:37.980> a<00:03:38.159> data 00:03:38.390 --> 00:03:38.400 align:start position:0% ethereum's public if you're a data 00:03:38.400 --> 00:03:39.350 align:start position:0% ethereum's public if you're a data scientist 00:03:39.350 --> 00:03:39.360 align:start position:0% scientist 00:03:39.360 --> 00:03:40.970 align:start position:0% scientist um<00:03:39.420> as<00:03:39.659> a<00:03:39.780> few<00:03:39.840> of<00:03:39.959> you<00:03:40.080> are<00:03:40.260> you<00:03:40.560> can<00:03:40.680> go<00:03:40.860> online 00:03:40.970 --> 00:03:40.980 align:start position:0% um as a few of you are you can go online 00:03:40.980 --> 00:03:43.190 align:start position:0% um as a few of you are you can go online or<00:03:41.340> you<00:03:41.519> can<00:03:41.580> go<00:03:41.640> on<00:03:41.760> ethereum<00:03:42.239> and<00:03:42.659> see<00:03:42.840> anyone 00:03:43.190 --> 00:03:43.200 align:start position:0% or you can go on ethereum and see anyone 00:03:43.200 --> 00:03:46.070 align:start position:0% or you can go on ethereum and see anyone ever<00:03:43.500> everyone<00:03:43.799> ever<00:03:44.099> does<00:03:44.760> um<00:03:44.819> so<00:03:45.120> I<00:03:45.780> don't 00:03:46.070 --> 00:03:46.080 align:start position:0% ever everyone ever does um so I don't 00:03:46.080 --> 00:03:47.270 align:start position:0% ever everyone ever does um so I don't want<00:03:46.200> to<00:03:46.319> live<00:03:46.379> in<00:03:46.500> a<00:03:46.620> world<00:03:46.739> where<00:03:47.040> you<00:03:47.159> have 00:03:47.270 --> 00:03:47.280 align:start position:0% want to live in a world where you have 00:03:47.280 --> 00:03:49.670 align:start position:0% want to live in a world where you have scalability<00:03:47.760> and<00:03:48.120> everything<00:03:48.360> sits<00:03:49.140> on<00:03:49.379> that 00:03:49.670 --> 00:03:49.680 align:start position:0% scalability and everything sits on that 00:03:49.680 --> 00:03:51.530 align:start position:0% scalability and everything sits on that platform<00:03:50.040> without<00:03:50.700> having<00:03:51.000> the<00:03:51.239> Privacy 00:03:51.530 --> 00:03:51.540 align:start position:0% platform without having the Privacy 00:03:51.540 --> 00:03:54.050 align:start position:0% platform without having the Privacy behind<00:03:51.959> it<00:03:52.080> so<00:03:52.620> let's<00:03:53.280> talk<00:03:53.459> about<00:03:53.640> on<00:03:53.819> chain 00:03:54.050 --> 00:03:54.060 align:start position:0% behind it so let's talk about on chain 00:03:54.060 --> 00:03:56.750 align:start position:0% behind it so let's talk about on chain so<00:03:54.840> this<00:03:55.379> is<00:03:55.440> what<00:03:55.620> it<00:03:55.680> looks<00:03:55.920> like<00:03:56.040> you<00:03:56.640> have 00:03:56.750 --> 00:03:56.760 align:start position:0% so this is what it looks like you have 00:03:56.760 --> 00:04:00.110 align:start position:0% so this is what it looks like you have your<00:03:56.879> layer<00:03:57.120> 2<00:03:57.239> blockchain<00:03:57.659> here<00:03:58.319> um<00:03:58.319> so<00:03:59.120> uh 00:04:00.110 --> 00:04:00.120 align:start position:0% your layer 2 blockchain here um so uh 00:04:00.120 --> 00:04:02.570 align:start position:0% your layer 2 blockchain here um so uh they<00:04:00.780> have<00:04:00.840> the<00:04:01.019> blocks<00:04:01.319> going<00:04:01.560> you<00:04:02.099> aggregate 00:04:02.570 --> 00:04:02.580 align:start position:0% they have the blocks going you aggregate 00:04:02.580 --> 00:04:04.430 align:start position:0% they have the blocks going you aggregate some<00:04:02.879> of<00:04:02.940> the<00:04:03.120> transactions<00:04:03.720> together 00:04:04.430 --> 00:04:04.440 align:start position:0% some of the transactions together 00:04:04.440 --> 00:04:06.350 align:start position:0% some of the transactions together um<00:04:04.500> and<00:04:04.739> then<00:04:04.920> you<00:04:04.980> batch<00:04:05.220> them<00:04:05.519> into<00:04:05.879> a<00:04:06.060> ZK 00:04:06.350 --> 00:04:06.360 align:start position:0% um and then you batch them into a ZK 00:04:06.360 --> 00:04:08.750 align:start position:0% um and then you batch them into a ZK circuit<00:04:06.840> so<00:04:07.200> you<00:04:07.799> take<00:04:07.920> those<00:04:08.159> transactions 00:04:08.750 --> 00:04:08.760 align:start position:0% circuit so you take those transactions 00:04:08.760 --> 00:04:10.610 align:start position:0% circuit so you take those transactions they<00:04:09.000> go<00:04:09.180> into<00:04:09.239> the<00:04:09.480> circuit<00:04:09.840> the<00:04:10.319> circuit 00:04:10.610 --> 00:04:10.620 align:start position:0% they go into the circuit the circuit 00:04:10.620 --> 00:04:12.949 align:start position:0% they go into the circuit the circuit produces<00:04:10.980> a<00:04:11.159> proof<00:04:11.459> this<00:04:12.120> is<00:04:12.239> all<00:04:12.420> off<00:04:12.720> chain 00:04:12.949 --> 00:04:12.959 align:start position:0% produces a proof this is all off chain 00:04:12.959 --> 00:04:15.890 align:start position:0% produces a proof this is all off chain so<00:04:13.739> then<00:04:13.920> you<00:04:14.280> have<00:04:14.400> your<00:04:14.819> ethereum<00:04:15.720> main 00:04:15.890 --> 00:04:15.900 align:start position:0% so then you have your ethereum main 00:04:15.900 --> 00:04:18.469 align:start position:0% so then you have your ethereum main chain<00:04:16.079> on<00:04:16.739> where<00:04:17.160> things<00:04:17.340> are<00:04:17.519> expensive 00:04:18.469 --> 00:04:18.479 align:start position:0% chain on where things are expensive 00:04:18.479 --> 00:04:19.009 align:start position:0% chain on where things are expensive um 00:04:19.009 --> 00:04:19.019 align:start position:0% um 00:04:19.019 --> 00:04:21.590 align:start position:0% um so<00:04:19.739> you're<00:04:19.979> able<00:04:20.220> to<00:04:20.340> take<00:04:20.519> your<00:04:20.699> proof<00:04:21.060> and 00:04:21.590 --> 00:04:21.600 align:start position:0% so you're able to take your proof and 00:04:21.600 --> 00:04:24.350 align:start position:0% so you're able to take your proof and post<00:04:21.780> that<00:04:22.019> to<00:04:22.260> the<00:04:22.380> verifier<00:04:22.800> smart<00:04:23.100> contract 00:04:24.350 --> 00:04:24.360 align:start position:0% post that to the verifier smart contract 00:04:24.360 --> 00:04:26.330 align:start position:0% post that to the verifier smart contract um and<00:04:24.540> then<00:04:24.780> the<00:04:25.020> layer<00:04:25.320> 2<00:04:25.440> State<00:04:25.860> source<00:04:26.220> of 00:04:26.330 --> 00:04:26.340 align:start position:0% um and then the layer 2 State source of 00:04:26.340 --> 00:04:29.390 align:start position:0% um and then the layer 2 State source of Truth<00:04:26.520> can<00:04:27.120> get<00:04:27.300> updated<00:04:27.600> so<00:04:28.259> that's<00:04:29.160> what 00:04:29.390 --> 00:04:29.400 align:start position:0% Truth can get updated so that's what 00:04:29.400 --> 00:04:31.070 align:start position:0% Truth can get updated so that's what happens<00:04:29.580> with<00:04:30.000> the<00:04:30.240> scalability<00:04:30.660> side<00:04:30.900> of 00:04:31.070 --> 00:04:31.080 align:start position:0% happens with the scalability side of 00:04:31.080 --> 00:04:33.230 align:start position:0% happens with the scalability side of things<00:04:31.199> now<00:04:31.979> let's<00:04:32.100> talk<00:04:32.280> privacy<00:04:33.060> um<00:04:33.060> it's 00:04:33.230 --> 00:04:33.240 align:start position:0% things now let's talk privacy um it's 00:04:33.240 --> 00:04:34.790 align:start position:0% things now let's talk privacy um it's very<00:04:33.479> similar<00:04:33.720> I<00:04:33.960> won't<00:04:34.020> have<00:04:34.199> reveals<00:04:34.620> for 00:04:34.790 --> 00:04:34.800 align:start position:0% very similar I won't have reveals for 00:04:34.800 --> 00:04:36.890 align:start position:0% very similar I won't have reveals for you<00:04:34.860> I'll<00:04:35.040> just<00:04:35.220> go<00:04:35.340> right<00:04:35.520> to<00:04:35.639> it<00:04:35.820> there's<00:04:36.720> a 00:04:36.890 --> 00:04:36.900 align:start position:0% you I'll just go right to it there's a 00:04:36.900 --> 00:04:39.590 align:start position:0% you I'll just go right to it there's a secret<00:04:37.080> there's<00:04:37.860> the<00:04:38.040> ZK<00:04:38.340> circuit<00:04:39.240> um<00:04:39.300> you<00:04:39.419> put 00:04:39.590 --> 00:04:39.600 align:start position:0% secret there's the ZK circuit um you put 00:04:39.600 --> 00:04:41.930 align:start position:0% secret there's the ZK circuit um you put the<00:04:39.720> secret<00:04:39.900> through<00:04:40.199> it<00:04:41.100> produces<00:04:41.520> a<00:04:41.639> proof 00:04:41.930 --> 00:04:41.940 align:start position:0% the secret through it produces a proof 00:04:41.940 --> 00:04:44.689 align:start position:0% the secret through it produces a proof and<00:04:42.479> then<00:04:42.660> that<00:04:42.840> proof<00:04:43.139> goes<00:04:43.500> on<00:04:43.620> chain<00:04:43.919> to<00:04:44.460> the 00:04:44.689 --> 00:04:44.699 align:start position:0% and then that proof goes on chain to the 00:04:44.699 --> 00:04:46.969 align:start position:0% and then that proof goes on chain to the verifier<00:04:45.120> smart<00:04:45.419> contract<00:04:45.840> and<00:04:46.500> funds<00:04:46.860> are 00:04:46.969 --> 00:04:46.979 align:start position:0% verifier smart contract and funds are 00:04:46.979 --> 00:04:49.070 align:start position:0% verifier smart contract and funds are released<00:04:47.340> so<00:04:48.000> that's<00:04:48.180> very<00:04:48.479> similar<00:04:48.780> that's 00:04:49.070 --> 00:04:49.080 align:start position:0% released so that's very similar that's 00:04:49.080 --> 00:04:50.450 align:start position:0% released so that's very similar that's going<00:04:49.259> to<00:04:49.380> be<00:04:49.440> your<00:04:49.740> mixers<00:04:50.040> your<00:04:50.280> channel 00:04:50.450 --> 00:04:50.460 align:start position:0% going to be your mixers your channel 00:04:50.460 --> 00:04:52.189 align:start position:0% going to be your mixers your channel caches<00:04:50.940> different<00:04:51.180> things 00:04:52.189 --> 00:04:52.199 align:start position:0% caches different things 00:04:52.199 --> 00:04:52.909 align:start position:0% caches different things um 00:04:52.909 --> 00:04:52.919 align:start position:0% um 00:04:52.919 --> 00:04:54.590 align:start position:0% um what's<00:04:53.520> important<00:04:53.759> for<00:04:54.060> both<00:04:54.180> of<00:04:54.300> these<00:04:54.479> two 00:04:54.590 --> 00:04:54.600 align:start position:0% what's important for both of these two 00:04:54.600 --> 00:04:56.090 align:start position:0% what's important for both of these two is<00:04:54.960> that<00:04:55.080> you<00:04:55.259> have 00:04:56.090 --> 00:04:56.100 align:start position:0% is that you have 00:04:56.100 --> 00:04:58.129 align:start position:0% is that you have um off<00:04:56.400> chain<00:04:56.639> and<00:04:57.180> on<00:04:57.360> chain<00:04:57.600> and<00:04:57.780> on<00:04:57.960> chain 00:04:58.129 --> 00:04:58.139 align:start position:0% um off chain and on chain and on chain 00:04:58.139 --> 00:05:00.170 align:start position:0% um off chain and on chain and on chain is<00:04:58.380> where<00:04:58.560> the<00:04:58.740> verifier<00:04:59.220> in<00:04:59.520> the<00:04:59.699> proof<00:04:59.940> gets 00:05:00.170 --> 00:05:00.180 align:start position:0% is where the verifier in the proof gets 00:05:00.180 --> 00:05:01.909 align:start position:0% is where the verifier in the proof gets posted<00:05:00.540> I<00:05:01.020> mean<00:05:01.139> off<00:05:01.259> chain<00:05:01.440> is<00:05:01.620> with<00:05:01.740> the 00:05:01.909 --> 00:05:01.919 align:start position:0% posted I mean off chain is with the 00:05:01.919 --> 00:05:03.469 align:start position:0% posted I mean off chain is with the circuit<00:05:02.160> and<00:05:02.280> the<00:05:02.400> proofs<00:05:02.699> are 00:05:03.469 --> 00:05:03.479 align:start position:0% circuit and the proofs are 00:05:03.479 --> 00:05:05.689 align:start position:0% circuit and the proofs are so<00:05:03.960> this<00:05:04.800> is<00:05:04.860> the<00:05:05.040> best<00:05:05.160> piece<00:05:05.400> of<00:05:05.460> artwork 00:05:05.689 --> 00:05:05.699 align:start position:0% so this is the best piece of artwork 00:05:05.699 --> 00:05:07.550 align:start position:0% so this is the best piece of artwork I've<00:05:05.940> ever<00:05:06.120> done<00:05:06.300> so<00:05:06.540> I<00:05:06.720> appreciate<00:05:07.080> it<00:05:07.259> while 00:05:07.550 --> 00:05:07.560 align:start position:0% I've ever done so I appreciate it while 00:05:07.560 --> 00:05:11.510 align:start position:0% I've ever done so I appreciate it while you<00:05:07.740> can<00:05:08.240> so<00:05:09.240> let's<00:05:09.720> find<00:05:10.020> some<00:05:10.560> ZK<00:05:11.040> proofs<00:05:11.400> on 00:05:11.510 --> 00:05:11.520 align:start position:0% you can so let's find some ZK proofs on 00:05:11.520 --> 00:05:14.930 align:start position:0% you can so let's find some ZK proofs on chain<00:05:11.699> and<00:05:11.880> figure<00:05:12.120> out<00:05:12.300> where<00:05:12.600> they're<00:05:12.720> at<00:05:12.900> so 00:05:14.930 --> 00:05:14.940 align:start position:0% chain and figure out where they're at so 00:05:14.940 --> 00:05:16.070 align:start position:0% chain and figure out where they're at so um<00:05:15.120> this<00:05:15.360> is<00:05:15.479> called<00:05:15.540> the<00:05:15.720> search<00:05:15.900> for 00:05:16.070 --> 00:05:16.080 align:start position:0% um this is called the search for 00:05:16.080 --> 00:05:17.810 align:start position:0% um this is called the search for verifiers<00:05:16.620> so<00:05:16.979> why<00:05:17.220> are<00:05:17.340> we<00:05:17.460> searching<00:05:17.699> for 00:05:17.810 --> 00:05:17.820 align:start position:0% verifiers so why are we searching for 00:05:17.820 --> 00:05:20.570 align:start position:0% verifiers so why are we searching for verifiers 00:05:20.570 --> 00:05:20.580 align:start position:0% 00:05:20.580 --> 00:05:22.610 align:start position:0% the<00:05:21.060> important<00:05:21.419> characteristics<00:05:21.960> of<00:05:22.199> a<00:05:22.320> zero 00:05:22.610 --> 00:05:22.620 align:start position:0% the important characteristics of a zero 00:05:22.620 --> 00:05:24.350 align:start position:0% the important characteristics of a zero knowledge<00:05:22.800> proof<00:05:23.160> are<00:05:23.520> in<00:05:23.699> the<00:05:23.820> circuit<00:05:24.120> so 00:05:24.350 --> 00:05:24.360 align:start position:0% knowledge proof are in the circuit so 00:05:24.360 --> 00:05:25.850 align:start position:0% knowledge proof are in the circuit so the<00:05:24.479> circuit<00:05:24.780> is<00:05:24.900> going<00:05:25.020> to<00:05:25.139> generate<00:05:25.860> um 00:05:25.850 --> 00:05:25.860 align:start position:0% the circuit is going to generate um 00:05:25.860 --> 00:05:26.749 align:start position:0% the circuit is going to generate um they're<00:05:26.100> going<00:05:26.280> to<00:05:26.340> have<00:05:26.460> the<00:05:26.639> different 00:05:26.749 --> 00:05:26.759 align:start position:0% they're going to have the different 00:05:26.759 --> 00:05:28.330 align:start position:0% they're going to have the different characteristics<00:05:27.360> that<00:05:27.600> are<00:05:27.720> important<00:05:28.020> to<00:05:28.199> us 00:05:28.330 --> 00:05:28.340 align:start position:0% characteristics that are important to us 00:05:28.340 --> 00:05:32.629 align:start position:0% characteristics that are important to us let's<00:05:29.340> look<00:05:29.580> at<00:05:29.940> a<00:05:30.240> particular<00:05:30.600> DK<00:05:31.259> sync<00:05:32.100> um 00:05:32.629 --> 00:05:32.639 align:start position:0% let's look at a particular DK sync um 00:05:32.639 --> 00:05:35.390 align:start position:0% let's look at a particular DK sync um transaction<00:05:33.360> flow<00:05:33.780> for<00:05:33.960> instance<00:05:34.199> so 00:05:35.390 --> 00:05:35.400 align:start position:0% transaction flow for instance so 00:05:35.400 --> 00:05:37.909 align:start position:0% transaction flow for instance so between<00:05:35.699> September<00:05:36.360> 26th<00:05:37.020> and<00:05:37.320> September<00:05:37.740> or 00:05:37.909 --> 00:05:37.919 align:start position:0% between September 26th and September or 00:05:37.919 --> 00:05:40.730 align:start position:0% between September 26th and September or September<00:05:38.340> 20th<00:05:38.880> and<00:05:39.120> September<00:05:39.479> 26th<00:05:40.080> there 00:05:40.730 --> 00:05:40.740 align:start position:0% September 20th and September 26th there 00:05:40.740 --> 00:05:42.650 align:start position:0% September 20th and September 26th there were<00:05:40.919> two<00:05:41.400> thousand<00:05:41.820> one<00:05:42.240> hundred<00:05:42.600> and 00:05:42.650 --> 00:05:42.660 align:start position:0% were two thousand one hundred and 00:05:42.660 --> 00:05:44.990 align:start position:0% were two thousand one hundred and seventy<00:05:43.080> one<00:05:43.919> two<00:05:44.280> thousand<00:05:44.520> one<00:05:44.639> hundred<00:05:44.940> and 00:05:44.990 --> 00:05:45.000 align:start position:0% seventy one two thousand one hundred and 00:05:45.000 --> 00:05:47.210 align:start position:0% seventy one two thousand one hundred and seventy<00:05:45.300> blocks<00:05:45.600> 265 00:05:47.210 --> 00:05:47.220 align:start position:0% seventy blocks 265 00:05:47.220 --> 00:05:49.550 align:start position:0% seventy blocks 265 000<00:05:47.340> transactions<00:05:48.539> um<00:05:48.660> which<00:05:49.020> were<00:05:49.199> batched 00:05:49.550 --> 00:05:49.560 align:start position:0% 000 transactions um which were batched 00:05:49.560 --> 00:05:53.749 align:start position:0% 000 transactions um which were batched together<00:05:49.680> into<00:05:50.419> 214<00:05:51.560> inputs<00:05:52.560> proofs<00:05:53.220> brought 00:05:53.749 --> 00:05:53.759 align:start position:0% together into 214 inputs proofs brought 00:05:53.759 --> 00:05:56.990 align:start position:0% together into 214 inputs proofs brought on<00:05:53.880> chain<00:05:54.120> so<00:05:54.960> what<00:05:55.620> you<00:05:55.740> want<00:05:55.919> the<00:05:56.220> ZK<00:05:56.639> circuit 00:05:56.990 --> 00:05:57.000 align:start position:0% on chain so what you want the ZK circuit 00:05:57.000 --> 00:05:58.909 align:start position:0% on chain so what you want the ZK circuit did<00:05:57.180> not<00:05:57.300> change<00:05:57.479> but<00:05:57.840> those<00:05:57.960> inputs<00:05:58.500> and<00:05:58.740> the 00:05:58.909 --> 00:05:58.919 align:start position:0% did not change but those inputs and the 00:05:58.919 --> 00:06:00.110 align:start position:0% did not change but those inputs and the proofs<00:05:59.280> did 00:06:00.110 --> 00:06:00.120 align:start position:0% proofs did 00:06:00.120 --> 00:06:03.430 align:start position:0% proofs did um<00:06:00.180> so 00:06:03.430 --> 00:06:03.440 align:start position:0% 00:06:03.440 --> 00:06:06.770 align:start position:0% each<00:06:04.440> circuit<00:06:04.860> has<00:06:05.340> a<00:06:05.639> unique<00:06:06.000> verifier<00:06:06.479> on 00:06:06.770 --> 00:06:06.780 align:start position:0% each circuit has a unique verifier on 00:06:06.780 --> 00:06:08.990 align:start position:0% each circuit has a unique verifier on chain<00:06:07.020> so<00:06:07.560> for<00:06:08.039> each<00:06:08.220> circuit<00:06:08.520> or<00:06:08.699> circuit 00:06:08.990 --> 00:06:09.000 align:start position:0% chain so for each circuit or circuit 00:06:09.000 --> 00:06:10.310 align:start position:0% chain so for each circuit or circuit systems<00:06:09.360> they<00:06:09.539> have<00:06:09.660> their<00:06:09.900> own<00:06:09.960> unique 00:06:10.310 --> 00:06:10.320 align:start position:0% systems they have their own unique 00:06:10.320 --> 00:06:14.150 align:start position:0% systems they have their own unique verifier<00:06:10.740> that's<00:06:10.979> there<00:06:11.699> and<00:06:12.479> the<00:06:13.560> um<00:06:13.560> if<00:06:13.979> you 00:06:14.150 --> 00:06:14.160 align:start position:0% verifier that's there and the um if you 00:06:14.160 --> 00:06:15.710 align:start position:0% verifier that's there and the um if you want<00:06:14.280> to<00:06:14.400> know<00:06:14.580> about<00:06:14.880> circuits<00:06:15.419> and<00:06:15.539> you<00:06:15.660> want 00:06:15.710 --> 00:06:15.720 align:start position:0% want to know about circuits and you want 00:06:15.720 --> 00:06:17.390 align:start position:0% want to know about circuits and you want to<00:06:15.840> use<00:06:15.900> on-chain<00:06:16.320> data<00:06:16.740> you<00:06:17.100> need<00:06:17.220> to<00:06:17.340> go 00:06:17.390 --> 00:06:17.400 align:start position:0% to use on-chain data you need to go 00:06:17.400 --> 00:06:18.710 align:start position:0% to use on-chain data you need to go through<00:06:17.580> the<00:06:17.699> verifier 00:06:18.710 --> 00:06:18.720 align:start position:0% through the verifier 00:06:18.720 --> 00:06:20.870 align:start position:0% through the verifier so<00:06:19.139> going<00:06:19.380> through<00:06:19.560> the<00:06:19.680> verifier 00:06:20.870 --> 00:06:20.880 align:start position:0% so going through the verifier 00:06:20.880 --> 00:06:23.510 align:start position:0% so going through the verifier um<00:06:20.940> you<00:06:21.060> use<00:06:21.240> the<00:06:21.419> L1<00:06:21.780> on<00:06:22.199> chain<00:06:22.440> data<00:06:23.220> um<00:06:23.340> so 00:06:23.510 --> 00:06:23.520 align:start position:0% um you use the L1 on chain data um so 00:06:23.520 --> 00:06:25.010 align:start position:0% um you use the L1 on chain data um so let's<00:06:23.699> talk<00:06:23.880> about<00:06:24.000> how<00:06:24.240> to<00:06:24.300> find<00:06:24.419> verifiers 00:06:25.010 --> 00:06:25.020 align:start position:0% let's talk about how to find verifiers 00:06:25.020 --> 00:06:28.309 align:start position:0% let's talk about how to find verifiers so<00:06:25.800> the<00:06:26.340> first<00:06:26.460> section<00:06:26.699> is<00:06:27.600> um<00:06:27.660> if<00:06:28.139> you<00:06:28.259> guys 00:06:28.309 --> 00:06:28.319 align:start position:0% so the first section is um if you guys 00:06:28.319 --> 00:06:30.469 align:start position:0% so the first section is um if you guys haven't<00:06:28.560> used<00:06:28.860> bigquery<00:06:29.340> on<00:06:29.759> from<00:06:30.000> Google<00:06:30.120> I 00:06:30.469 --> 00:06:30.479 align:start position:0% haven't used bigquery on from Google I 00:06:30.479 --> 00:06:32.450 align:start position:0% haven't used bigquery on from Google I highly<00:06:30.720> recommend<00:06:31.080> it<00:06:31.560> um<00:06:31.620> it's<00:06:31.919> a<00:06:31.979> great<00:06:32.100> tool 00:06:32.450 --> 00:06:32.460 align:start position:0% highly recommend it um it's a great tool 00:06:32.460 --> 00:06:35.090 align:start position:0% highly recommend it um it's a great tool it<00:06:33.300> allows<00:06:33.840> you<00:06:33.900> to<00:06:34.080> search<00:06:34.259> through<00:06:34.560> lots 00:06:35.090 --> 00:06:35.100 align:start position:0% it allows you to search through lots 00:06:35.100 --> 00:06:36.950 align:start position:0% it allows you to search through lots more<00:06:35.160> data<00:06:35.580> than<00:06:35.759> things<00:06:36.000> like<00:06:36.180> Doom<00:06:36.600> do<00:06:36.720> as 00:06:36.950 --> 00:06:36.960 align:start position:0% more data than things like Doom do as 00:06:36.960 --> 00:06:38.930 align:start position:0% more data than things like Doom do as much<00:06:37.139> as<00:06:37.199> I<00:06:37.319> love<00:06:37.440> Dune<00:06:37.860> so 00:06:38.930 --> 00:06:38.940 align:start position:0% much as I love Dune so 00:06:38.940 --> 00:06:40.670 align:start position:0% much as I love Dune so um<00:06:39.000> different<00:06:39.300> queries<00:06:40.080> that<00:06:40.259> time<00:06:40.440> out 00:06:40.670 --> 00:06:40.680 align:start position:0% um different queries that time out 00:06:40.680 --> 00:06:43.309 align:start position:0% um different queries that time out within<00:06:41.160> 30<00:06:41.819> minutes<00:06:42.060> for<00:06:42.300> Dune<00:06:42.660> will<00:06:42.960> go<00:06:43.199> in 00:06:43.309 --> 00:06:43.319 align:start position:0% within 30 minutes for Dune will go in 00:06:43.319 --> 00:06:45.650 align:start position:0% within 30 minutes for Dune will go in about<00:06:43.500> two<00:06:43.800> seconds<00:06:44.039> for<00:06:44.340> bigquery<00:06:44.759> so 00:06:45.650 --> 00:06:45.660 align:start position:0% about two seconds for bigquery so 00:06:45.660 --> 00:06:46.909 align:start position:0% about two seconds for bigquery so um check<00:06:45.960> it<00:06:46.080> out 00:06:46.909 --> 00:06:46.919 align:start position:0% um check it out 00:06:46.919 --> 00:06:49.010 align:start position:0% um check it out um the<00:06:47.340> three<00:06:47.520> tables<00:06:48.000> that<00:06:48.120> I<00:06:48.300> used<00:06:48.780> um<00:06:48.780> for 00:06:49.010 --> 00:06:49.020 align:start position:0% um the three tables that I used um for 00:06:49.020 --> 00:06:52.430 align:start position:0% um the three tables that I used um for this<00:06:49.139> project<00:06:49.319> were<00:06:50.000> contracts<00:06:51.080> traces<00:06:52.080> and 00:06:52.430 --> 00:06:52.440 align:start position:0% this project were contracts traces and 00:06:52.440 --> 00:06:54.650 align:start position:0% this project were contracts traces and transactions 00:06:54.650 --> 00:06:54.660 align:start position:0% transactions 00:06:54.660 --> 00:06:56.870 align:start position:0% transactions since<00:06:55.319> you're<00:06:55.500> almost<00:06:55.800> all<00:06:56.039> devs<00:06:56.400> I<00:06:56.580> won't<00:06:56.699> go 00:06:56.870 --> 00:06:56.880 align:start position:0% since you're almost all devs I won't go 00:06:56.880 --> 00:06:59.390 align:start position:0% since you're almost all devs I won't go over<00:06:57.000> traces<00:06:57.600> versus<00:06:57.780> transactions<00:06:58.500> but 00:06:59.390 --> 00:06:59.400 align:start position:0% over traces versus transactions but 00:06:59.400 --> 00:07:02.510 align:start position:0% over traces versus transactions but start<00:06:59.940> versus<00:07:00.180> end<00:07:00.660> of<00:07:00.840> things<00:07:00.960> so<00:07:01.380> okay 00:07:02.510 --> 00:07:02.520 align:start position:0% start versus end of things so okay 00:07:02.520 --> 00:07:04.370 align:start position:0% start versus end of things so okay um so<00:07:02.940> the<00:07:03.360> first<00:07:03.479> way<00:07:03.780> to<00:07:03.960> try<00:07:04.080> and<00:07:04.199> search 00:07:04.370 --> 00:07:04.380 align:start position:0% um so the first way to try and search 00:07:04.380 --> 00:07:07.430 align:start position:0% um so the first way to try and search through<00:07:04.560> bytecode<00:07:05.520> um<00:07:06.060> is<00:07:06.539> to<00:07:06.780> go<00:07:07.020> for 00:07:07.430 --> 00:07:07.440 align:start position:0% through bytecode um is to go for 00:07:07.440 --> 00:07:09.650 align:start position:0% through bytecode um is to go for constants<00:07:07.860> constants<00:07:08.580> will<00:07:08.940> show<00:07:09.120> up<00:07:09.300> in<00:07:09.419> byte 00:07:09.650 --> 00:07:09.660 align:start position:0% constants constants will show up in byte 00:07:09.660 --> 00:07:12.529 align:start position:0% constants constants will show up in byte code<00:07:09.780> as<00:07:10.199> a<00:07:10.740> big<00:07:10.919> hex<00:07:11.280> so<00:07:11.940> if<00:07:12.060> you<00:07:12.180> can<00:07:12.300> get<00:07:12.419> a 00:07:12.529 --> 00:07:12.539 align:start position:0% code as a big hex so if you can get a 00:07:12.539 --> 00:07:13.969 align:start position:0% code as a big hex so if you can get a big<00:07:12.660> enough<00:07:12.840> number<00:07:13.139> that's<00:07:13.500> unique<00:07:13.860> enough 00:07:13.969 --> 00:07:13.979 align:start position:0% big enough number that's unique enough 00:07:13.979 --> 00:07:16.189 align:start position:0% big enough number that's unique enough for<00:07:14.280> what<00:07:14.400> you're<00:07:14.460> looking<00:07:14.639> for<00:07:14.900> you<00:07:15.900> can<00:07:16.020> take 00:07:16.189 --> 00:07:16.199 align:start position:0% for what you're looking for you can take 00:07:16.199 --> 00:07:18.170 align:start position:0% for what you're looking for you can take that<00:07:16.440> in<00:07:16.800> search<00:07:17.039> with<00:07:17.400> very<00:07:17.580> simple<00:07:17.759> SQL 00:07:18.170 --> 00:07:18.180 align:start position:0% that in search with very simple SQL 00:07:18.180 --> 00:07:19.309 align:start position:0% that in search with very simple SQL queries 00:07:19.309 --> 00:07:19.319 align:start position:0% queries 00:07:19.319 --> 00:07:21.710 align:start position:0% queries um<00:07:19.380> in<00:07:19.560> through<00:07:19.680> the<00:07:19.800> byte<00:07:20.099> code<00:07:20.220> so<00:07:20.639> this<00:07:21.360> is 00:07:21.710 --> 00:07:21.720 align:start position:0% um in through the byte code so this is 00:07:21.720 --> 00:07:24.110 align:start position:0% um in through the byte code so this is both<00:07:22.199> a<00:07:22.440> big<00:07:22.620> and<00:07:22.919> unique<00:07:23.280> value<00:07:23.520> it's<00:07:23.940> the 00:07:24.110 --> 00:07:24.120 align:start position:0% both a big and unique value it's the 00:07:24.120 --> 00:07:25.189 align:start position:0% both a big and unique value it's the finite<00:07:24.419> field 00:07:25.189 --> 00:07:25.199 align:start position:0% finite field 00:07:25.199 --> 00:07:27.469 align:start position:0% finite field um<00:07:25.319> so<00:07:25.740> the<00:07:25.860> finite<00:07:26.160> field<00:07:26.340> is<00:07:26.699> the<00:07:26.940> range<00:07:27.300> at 00:07:27.469 --> 00:07:27.479 align:start position:0% um so the finite field is the range at 00:07:27.479 --> 00:07:28.850 align:start position:0% um so the finite field is the range at which<00:07:27.660> you<00:07:27.780> modulate<00:07:28.139> over<00:07:28.380> when<00:07:28.740> you're 00:07:28.850 --> 00:07:28.860 align:start position:0% which you modulate over when you're 00:07:28.860 --> 00:07:29.589 align:start position:0% which you modulate over when you're doing 00:07:29.589 --> 00:07:29.599 align:start position:0% doing 00:07:29.599 --> 00:07:32.270 align:start position:0% doing different<00:07:30.599> cryptography<00:07:31.560> cryptographic 00:07:32.270 --> 00:07:32.280 align:start position:0% different cryptography cryptographic 00:07:32.280 --> 00:07:35.089 align:start position:0% different cryptography cryptographic things<00:07:32.460> for<00:07:32.940> um<00:07:32.940> knowledge<00:07:33.599> so<00:07:34.020> this<00:07:34.680> is<00:07:34.740> it<00:07:34.919> in 00:07:35.089 --> 00:07:35.099 align:start position:0% things for um knowledge so this is it in 00:07:35.099 --> 00:07:37.850 align:start position:0% things for um knowledge so this is it in HEX<00:07:35.340> form<00:07:35.819> um<00:07:35.819> it's<00:07:36.000> massive<00:07:36.419> so<00:07:36.960> the<00:07:37.740> first 00:07:37.850 --> 00:07:37.860 align:start position:0% HEX form um it's massive so the first 00:07:37.860 --> 00:07:39.890 align:start position:0% HEX form um it's massive so the first way<00:07:38.039> that<00:07:38.220> I<00:07:38.400> look<00:07:38.520> through<00:07:38.699> the<00:07:38.819> data<00:07:39.180> was<00:07:39.419> to 00:07:39.890 --> 00:07:39.900 align:start position:0% way that I look through the data was to 00:07:39.900 --> 00:07:42.129 align:start position:0% way that I look through the data was to search<00:07:40.440> for<00:07:40.740> this<00:07:40.979> finite<00:07:41.340> field 00:07:42.129 --> 00:07:42.139 align:start position:0% search for this finite field 00:07:42.139 --> 00:07:45.469 align:start position:0% search for this finite field unfortunately<00:07:43.139> it<00:07:43.740> didn't<00:07:44.639> exactly<00:07:45.060> give<00:07:45.300> me 00:07:45.469 --> 00:07:45.479 align:start position:0% unfortunately it didn't exactly give me 00:07:45.479 --> 00:07:47.270 align:start position:0% unfortunately it didn't exactly give me all<00:07:45.660> the<00:07:45.840> verifiers<00:07:46.380> so<00:07:46.560> it<00:07:46.680> gave<00:07:46.860> me<00:07:46.979> a<00:07:47.039> lot<00:07:47.160> of 00:07:47.270 --> 00:07:47.280 align:start position:0% all the verifiers so it gave me a lot of 00:07:47.280 --> 00:07:50.749 align:start position:0% all the verifiers so it gave me a lot of different<00:07:47.400> noise<00:07:47.840> there's<00:07:48.840> 558<00:07:49.800> contracts<00:07:50.340> on 00:07:50.749 --> 00:07:50.759 align:start position:0% different noise there's 558 contracts on 00:07:50.759 --> 00:07:53.089 align:start position:0% different noise there's 558 contracts on that<00:07:51.240> have<00:07:51.419> the<00:07:51.539> finite<00:07:51.840> field<00:07:52.020> constant<00:07:53.039> um 00:07:53.089 --> 00:07:53.099 align:start position:0% that have the finite field constant um 00:07:53.099 --> 00:07:54.710 align:start position:0% that have the finite field constant um and<00:07:53.460> after<00:07:53.759> checking<00:07:54.180> every<00:07:54.300> one<00:07:54.539> of<00:07:54.599> them 00:07:54.710 --> 00:07:54.720 align:start position:0% and after checking every one of them 00:07:54.720 --> 00:07:57.170 align:start position:0% and after checking every one of them manually<00:07:55.319> most<00:07:56.160> of<00:07:56.280> them<00:07:56.340> are<00:07:56.460> not<00:07:56.639> verifiers 00:07:57.170 --> 00:07:57.180 align:start position:0% manually most of them are not verifiers 00:07:57.180 --> 00:07:59.570 align:start position:0% manually most of them are not verifiers so<00:07:57.539> I<00:07:58.139> moved<00:07:58.500> on<00:07:58.560> to<00:07:58.860> trying<00:07:59.160> to<00:07:59.280> get<00:07:59.400> into 00:07:59.570 --> 00:07:59.580 align:start position:0% so I moved on to trying to get into 00:07:59.580 --> 00:08:02.749 align:start position:0% so I moved on to trying to get into method<00:08:00.060> IDs<00:08:00.479> so<00:08:00.900> the<00:08:01.620> second<00:08:01.740> tool<00:08:02.280> that<00:08:02.580> I 00:08:02.749 --> 00:08:02.759 align:start position:0% method IDs so the second tool that I 00:08:02.759 --> 00:08:04.189 align:start position:0% method IDs so the second tool that I think<00:08:02.819> is<00:08:03.000> really<00:08:03.180> important<00:08:03.539> and<00:08:03.780> apparently 00:08:04.189 --> 00:08:04.199 align:start position:0% think is really important and apparently 00:08:04.199 --> 00:08:06.589 align:start position:0% think is really important and apparently it's<00:08:04.319> new<00:08:04.560> according<00:08:05.099> to<00:08:05.220> etherscan<00:08:05.880> it<00:08:06.000> is 00:08:06.589 --> 00:08:06.599 align:start position:0% it's new according to etherscan it is 00:08:06.599 --> 00:08:09.890 align:start position:0% it's new according to etherscan it is the<00:08:07.099> transaction<00:08:08.099> decoder<00:08:08.699> so<00:08:09.240> the 00:08:09.890 --> 00:08:09.900 align:start position:0% the transaction decoder so the 00:08:09.900 --> 00:08:11.510 align:start position:0% the transaction decoder so the transaction<00:08:10.199> decoder 00:08:11.510 --> 00:08:11.520 align:start position:0% transaction decoder 00:08:11.520 --> 00:08:13.249 align:start position:0% transaction decoder um what<00:08:11.940> it<00:08:12.060> does<00:08:12.240> if<00:08:12.720> you<00:08:12.780> look<00:08:12.960> through<00:08:13.080> it 00:08:13.249 --> 00:08:13.259 align:start position:0% um what it does if you look through it 00:08:13.259 --> 00:08:14.749 align:start position:0% um what it does if you look through it is<00:08:13.500> if<00:08:13.740> you<00:08:13.919> go<00:08:14.099> through<00:08:14.220> and<00:08:14.400> look<00:08:14.520> at<00:08:14.639> a 00:08:14.749 --> 00:08:14.759 align:start position:0% is if you go through and look at a 00:08:14.759 --> 00:08:16.670 align:start position:0% is if you go through and look at a transaction<00:08:15.120> it<00:08:15.780> will<00:08:15.900> tell<00:08:16.080> you<00:08:16.199> the<00:08:16.380> exact 00:08:16.670 --> 00:08:16.680 align:start position:0% transaction it will tell you the exact 00:08:16.680 --> 00:08:18.589 align:start position:0% transaction it will tell you the exact flow<00:08:17.039> of<00:08:17.160> what<00:08:17.340> happened<00:08:17.580> on<00:08:18.060> through<00:08:18.360> that 00:08:18.589 --> 00:08:18.599 align:start position:0% flow of what happened on through that 00:08:18.599 --> 00:08:21.650 align:start position:0% flow of what happened on through that transaction<00:08:19.080> so<00:08:19.680> looking<00:08:20.340> at<00:08:20.759> this<00:08:21.240> here<00:08:21.419> is 00:08:21.650 --> 00:08:21.660 align:start position:0% transaction so looking at this here is 00:08:21.660 --> 00:08:23.990 align:start position:0% transaction so looking at this here is another<00:08:21.840> ZK<00:08:22.259> sync<00:08:22.620> example 00:08:23.990 --> 00:08:24.000 align:start position:0% another ZK sync example 00:08:24.000 --> 00:08:25.070 align:start position:0% another ZK sync example um 00:08:25.070 --> 00:08:25.080 align:start position:0% um 00:08:25.080 --> 00:08:27.890 align:start position:0% um first<00:08:25.560> it<00:08:26.099> proves<00:08:26.460> the<00:08:26.639> blocks 00:08:27.890 --> 00:08:27.900 align:start position:0% first it proves the blocks 00:08:27.900 --> 00:08:30.890 align:start position:0% first it proves the blocks after<00:08:28.620> going<00:08:28.919> through<00:08:29.099> some<00:08:29.220> proxies<00:08:29.900> and 00:08:30.890 --> 00:08:30.900 align:start position:0% after going through some proxies and 00:08:30.900 --> 00:08:33.769 align:start position:0% after going through some proxies and then<00:08:31.139> in<00:08:31.740> the<00:08:31.860> verifier<00:08:32.279> contract<00:08:32.700> it<00:08:33.240> does<00:08:33.599> it 00:08:33.769 --> 00:08:33.779 align:start position:0% then in the verifier contract it does it 00:08:33.779 --> 00:08:35.810 align:start position:0% then in the verifier contract it does it calls<00:08:34.080> a<00:08:34.200> function<00:08:34.440> called<00:08:34.620> verify<00:08:35.279> aggregate 00:08:35.810 --> 00:08:35.820 align:start position:0% calls a function called verify aggregate 00:08:35.820 --> 00:08:39.949 align:start position:0% calls a function called verify aggregate block<00:08:36.419> proof<00:08:36.959> so<00:08:37.440> after<00:08:38.399> doing<00:08:38.700> some<00:08:39.120> modular 00:08:39.949 --> 00:08:39.959 align:start position:0% block proof so after doing some modular 00:08:39.959 --> 00:08:43.370 align:start position:0% block proof so after doing some modular Edition<00:08:40.620> down<00:08:41.159> below<00:08:41.339> it<00:08:41.959> outputs<00:08:42.959> true<00:08:43.140> and 00:08:43.370 --> 00:08:43.380 align:start position:0% Edition down below it outputs true and 00:08:43.380 --> 00:08:44.870 align:start position:0% Edition down below it outputs true and the<00:08:43.560> state<00:08:43.680> gets<00:08:44.039> updated 00:08:44.870 --> 00:08:44.880 align:start position:0% the state gets updated 00:08:44.880 --> 00:08:48.530 align:start position:0% the state gets updated so<00:08:45.440> method<00:08:46.440> IDs<00:08:46.860> the<00:08:47.580> method<00:08:47.820> IDs<00:08:48.180> are<00:08:48.360> the 00:08:48.530 --> 00:08:48.540 align:start position:0% so method IDs the method IDs are the 00:08:48.540 --> 00:08:50.449 align:start position:0% so method IDs the method IDs are the first<00:08:48.720> 10<00:08:49.019> characters<00:08:49.320> or<00:08:49.740> four<00:08:49.860> bytes<00:08:50.279> that 00:08:50.449 --> 00:08:50.459 align:start position:0% first 10 characters or four bytes that 00:08:50.459 --> 00:08:52.610 align:start position:0% first 10 characters or four bytes that come<00:08:50.640> through<00:08:50.820> with<00:08:51.300> any<00:08:51.480> input<00:08:51.839> or 00:08:52.610 --> 00:08:52.620 align:start position:0% come through with any input or 00:08:52.620 --> 00:08:54.650 align:start position:0% come through with any input or transaction<00:08:53.040> call<00:08:53.279> for<00:08:54.120> traces<00:08:54.540> or 00:08:54.650 --> 00:08:54.660 align:start position:0% transaction call for traces or 00:08:54.660 --> 00:08:56.630 align:start position:0% transaction call for traces or transactions<00:08:55.260> so<00:08:55.680> just<00:08:56.160> going<00:08:56.339> through<00:08:56.519> them 00:08:56.630 --> 00:08:56.640 align:start position:0% transactions so just going through them 00:08:56.640 --> 00:08:57.650 align:start position:0% transactions so just going through them briefly 00:08:57.650 --> 00:08:57.660 align:start position:0% briefly 00:08:57.660 --> 00:08:59.990 align:start position:0% briefly um you<00:08:58.019> can<00:08:58.140> see<00:08:58.380> that<00:08:58.680> this<00:08:59.220> function<00:08:59.519> here 00:08:59.990 --> 00:09:00.000 align:start position:0% um you can see that this function here 00:09:00.000 --> 00:09:02.329 align:start position:0% um you can see that this function here is<00:09:00.300> for<00:09:00.480> startware<00:09:01.320> um<00:09:01.440> and<00:09:01.620> it's<00:09:01.800> a<00:09:01.980> fry 00:09:02.329 --> 00:09:02.339 align:start position:0% is for startware um and it's a fry 00:09:02.339 --> 00:09:04.610 align:start position:0% is for startware um and it's a fry verifier<00:09:02.820> so<00:09:03.240> this<00:09:03.959> is<00:09:04.080> what<00:09:04.320> is<00:09:04.440> actually 00:09:04.610 --> 00:09:04.620 align:start position:0% verifier so this is what is actually 00:09:04.620 --> 00:09:07.310 align:start position:0% verifier so this is what is actually verifying<00:09:05.279> the<00:09:05.519> proofs<00:09:06.360> um<00:09:06.420> so<00:09:06.899> if<00:09:07.140> you<00:09:07.200> want 00:09:07.310 --> 00:09:07.320 align:start position:0% verifying the proofs um so if you want 00:09:07.320 --> 00:09:10.130 align:start position:0% verifying the proofs um so if you want to<00:09:07.440> know<00:09:07.560> what<00:09:07.800> the<00:09:08.100> method<00:09:08.519> ID<00:09:08.700> is<00:09:09.180> for<00:09:09.660> this 00:09:10.130 --> 00:09:10.140 align:start position:0% to know what the method ID is for this 00:09:10.140 --> 00:09:13.130 align:start position:0% to know what the method ID is for this particular<00:09:10.500> function<00:09:10.920> here 00:09:13.130 --> 00:09:13.140 align:start position:0% particular function here 00:09:13.140 --> 00:09:15.590 align:start position:0% particular function here then<00:09:13.800> you<00:09:14.100> take<00:09:14.279> you<00:09:14.580> take<00:09:14.760> out<00:09:14.940> all<00:09:15.240> the<00:09:15.360> chaff 00:09:15.590 --> 00:09:15.600 align:start position:0% then you take you take out all the chaff 00:09:15.600 --> 00:09:18.050 align:start position:0% then you take you take out all the chaff if<00:09:15.899> you<00:09:16.080> will<00:09:16.200> from<00:09:16.440> inside<00:09:16.620> and<00:09:17.580> then<00:09:17.760> you<00:09:17.880> run 00:09:18.050 --> 00:09:18.060 align:start position:0% if you will from inside and then you run 00:09:18.060 --> 00:09:20.630 align:start position:0% if you will from inside and then you run the<00:09:18.180> kcac<00:09:18.660> 256 00:09:20.630 --> 00:09:20.640 align:start position:0% the kcac 256 00:09:20.640 --> 00:09:22.550 align:start position:0% the kcac 256 and<00:09:21.120> you<00:09:21.240> take<00:09:21.420> the<00:09:21.600> first<00:09:21.720> four<00:09:21.959> bytes<00:09:22.380> plus 00:09:22.550 --> 00:09:22.560 align:start position:0% and you take the first four bytes plus 00:09:22.560 --> 00:09:25.009 align:start position:0% and you take the first four bytes plus the<00:09:22.800> indicator<00:09:23.160> that<00:09:23.459> it's<00:09:23.580> hex<00:09:23.880> so<00:09:24.360> that 00:09:25.009 --> 00:09:25.019 align:start position:0% the indicator that it's hex so that 00:09:25.019 --> 00:09:26.710 align:start position:0% the indicator that it's hex so that there<00:09:25.320> the<00:09:25.620> ox 00:09:26.710 --> 00:09:26.720 align:start position:0% there the ox 00:09:26.720 --> 00:09:31.130 align:start position:0% there the ox E85<00:09:27.720> A6<00:09:28.500> a28<00:09:29.459> is<00:09:29.700> the<00:09:29.820> method<00:09:30.120> ID<00:09:30.300> it'll<00:09:30.959> be<00:09:31.019> the 00:09:31.130 --> 00:09:31.140 align:start position:0% E85 A6 a28 is the method ID it'll be the 00:09:31.140 --> 00:09:32.750 align:start position:0% E85 A6 a28 is the method ID it'll be the first<00:09:31.260> 10<00:09:31.440> characters<00:09:31.680> in<00:09:32.040> any<00:09:32.220> call<00:09:32.459> that 00:09:32.750 --> 00:09:32.760 align:start position:0% first 10 characters in any call that 00:09:32.760 --> 00:09:35.150 align:start position:0% first 10 characters in any call that when<00:09:32.940> you<00:09:33.060> look<00:09:33.240> through<00:09:33.420> the<00:09:33.660> data<00:09:33.899> so 00:09:35.150 --> 00:09:35.160 align:start position:0% when you look through the data so 00:09:35.160 --> 00:09:36.949 align:start position:0% when you look through the data so um a<00:09:35.399> great<00:09:35.519> resource<00:09:36.060> again 00:09:36.949 --> 00:09:36.959 align:start position:0% um a great resource again 00:09:36.959 --> 00:09:38.509 align:start position:0% um a great resource again um<00:09:37.019> I'd<00:09:37.200> like<00:09:37.320> to<00:09:37.440> show<00:09:37.560> the<00:09:37.740> resources<00:09:38.160> that<00:09:38.399> I 00:09:38.509 --> 00:09:38.519 align:start position:0% um I'd like to show the resources that I 00:09:38.519 --> 00:09:41.389 align:start position:0% um I'd like to show the resources that I get<00:09:38.700> to<00:09:38.820> use<00:09:39.360> um<00:09:39.420> the<00:09:39.959> four<00:09:40.160> byte.directory<00:09:41.160> is 00:09:41.389 --> 00:09:41.399 align:start position:0% get to use um the four byte.directory is 00:09:41.399 --> 00:09:44.210 align:start position:0% get to use um the four byte.directory is fantastic<00:09:42.180> um<00:09:42.240> you<00:09:42.360> can<00:09:42.540> input<00:09:42.899> any<00:09:43.680> method<00:09:44.100> ID 00:09:44.210 --> 00:09:44.220 align:start position:0% fantastic um you can input any method ID 00:09:44.220 --> 00:09:47.030 align:start position:0% fantastic um you can input any method ID and<00:09:44.820> it<00:09:44.940> will<00:09:45.060> tell<00:09:45.300> you<00:09:45.480> what<00:09:46.080> the<00:09:46.800> um<00:09:46.800> text 00:09:47.030 --> 00:09:47.040 align:start position:0% and it will tell you what the um text 00:09:47.040 --> 00:09:50.329 align:start position:0% and it will tell you what the um text signature<00:09:47.519> for<00:09:47.700> what<00:09:47.820> it<00:09:47.940> should<00:09:48.120> be<00:09:48.240> is<00:09:48.600> so 00:09:50.329 --> 00:09:50.339 align:start position:0% signature for what it should be is so 00:09:50.339 --> 00:09:52.070 align:start position:0% signature for what it should be is so um<00:09:50.399> now<00:09:50.640> what<00:09:50.820> do<00:09:51.000> we<00:09:51.060> find 00:09:52.070 --> 00:09:52.080 align:start position:0% um now what do we find 00:09:52.080 --> 00:09:54.769 align:start position:0% um now what do we find essentially<00:09:52.740> there's<00:09:53.220> about<00:09:53.519> 65<00:09:54.240> confirmed 00:09:54.769 --> 00:09:54.779 align:start position:0% essentially there's about 65 confirmed 00:09:54.779 --> 00:09:56.810 align:start position:0% essentially there's about 65 confirmed verifiers<00:09:55.260> on<00:09:55.440> main<00:09:55.620> chain<00:09:55.860> now<00:09:56.339> there's 00:09:56.810 --> 00:09:56.820 align:start position:0% verifiers on main chain now there's 00:09:56.820 --> 00:09:58.670 align:start position:0% verifiers on main chain now there's probably<00:09:57.000> a<00:09:57.300> few<00:09:57.420> more<00:09:57.540> on<00:09:57.959> maybe<00:09:58.200> 30<00:09:58.440> more 00:09:58.670 --> 00:09:58.680 align:start position:0% probably a few more on maybe 30 more 00:09:58.680 --> 00:10:00.710 align:start position:0% probably a few more on maybe 30 more that<00:09:59.040> are<00:09:59.220> not<00:09:59.459> on<00:09:59.820> verified<00:10:00.180> public 00:10:00.710 --> 00:10:00.720 align:start position:0% that are not on verified public 00:10:00.720 --> 00:10:02.449 align:start position:0% that are not on verified public contracts<00:10:01.320> so 00:10:02.449 --> 00:10:02.459 align:start position:0% contracts so 00:10:02.459 --> 00:10:04.970 align:start position:0% contracts so um in<00:10:02.760> those<00:10:03.000> 65<00:10:03.660> confirmed<00:10:04.140> verifiers<00:10:04.620> have 00:10:04.970 --> 00:10:04.980 align:start position:0% um in those 65 confirmed verifiers have 00:10:04.980 --> 00:10:05.930 align:start position:0% um in those 65 confirmed verifiers have done 00:10:05.930 --> 00:10:05.940 align:start position:0% done 00:10:05.940 --> 00:10:09.230 align:start position:0% done over<00:10:06.600> 600<00:10:07.260> 000<00:10:07.440> verifications 00:10:09.230 --> 00:10:09.240 align:start position:0% over 600 000 verifications 00:10:09.240 --> 00:10:12.410 align:start position:0% over 600 000 verifications so<00:10:10.140> um<00:10:10.140> of<00:10:10.620> those 00:10:12.410 --> 00:10:12.420 align:start position:0% so um of those 00:10:12.420 --> 00:10:15.590 align:start position:0% so um of those there<00:10:12.899> are<00:10:13.019> about<00:10:13.140> 16<00:10:13.560> that<00:10:14.040> are<00:10:14.160> active<00:10:14.700> still 00:10:15.590 --> 00:10:15.600 align:start position:0% there are about 16 that are active still 00:10:15.600 --> 00:10:17.449 align:start position:0% there are about 16 that are active still um that's<00:10:16.080> active<00:10:16.620> according<00:10:17.040> to<00:10:17.160> me<00:10:17.279> and 00:10:17.449 --> 00:10:17.459 align:start position:0% um that's active according to me and 00:10:17.459 --> 00:10:19.730 align:start position:0% um that's active according to me and some<00:10:17.760> of<00:10:17.940> them<00:10:18.060> are<00:10:18.360> very<00:10:18.779> minor<00:10:19.080> projects<00:10:19.500> if 00:10:19.730 --> 00:10:19.740 align:start position:0% some of them are very minor projects if 00:10:19.740 --> 00:10:21.110 align:start position:0% some of them are very minor projects if you're<00:10:19.860> trying<00:10:20.040> to<00:10:20.160> squint<00:10:20.459> it's<00:10:20.760> because<00:10:20.940> I 00:10:21.110 --> 00:10:21.120 align:start position:0% you're trying to squint it's because I 00:10:21.120 --> 00:10:22.490 align:start position:0% you're trying to squint it's because I made<00:10:21.240> it<00:10:21.420> small<00:10:21.540> so<00:10:21.779> you'd<00:10:21.959> have<00:10:22.080> to<00:10:22.140> go<00:10:22.260> on<00:10:22.320> the 00:10:22.490 --> 00:10:22.500 align:start position:0% made it small so you'd have to go on the 00:10:22.500 --> 00:10:25.970 align:start position:0% made it small so you'd have to go on the GitHub<00:10:22.740> at<00:10:22.920> some<00:10:23.040> point<00:10:23.220> so<00:10:23.459> sorry 00:10:25.970 --> 00:10:25.980 align:start position:0% GitHub at some point so sorry 00:10:25.980 --> 00:10:26.810 align:start position:0% GitHub at some point so sorry um 00:10:26.810 --> 00:10:26.820 align:start position:0% um 00:10:26.820 --> 00:10:28.850 align:start position:0% um I<00:10:27.360> was<00:10:27.420> surprised<00:10:27.720> by<00:10:27.839> how<00:10:28.080> few<00:10:28.260> verifiers 00:10:28.850 --> 00:10:28.860 align:start position:0% I was surprised by how few verifiers 00:10:28.860 --> 00:10:31.070 align:start position:0% I was surprised by how few verifiers there<00:10:29.040> are<00:10:29.160> actually<00:10:29.339> on<00:10:29.580> main<00:10:29.760> chain<00:10:30.000> but 00:10:31.070 --> 00:10:31.080 align:start position:0% there are actually on main chain but 00:10:31.080 --> 00:10:32.990 align:start position:0% there are actually on main chain but moving<00:10:31.620> on<00:10:31.680> to<00:10:31.800> the<00:10:31.920> characteristics<00:10:32.399> so 00:10:32.990 --> 00:10:33.000 align:start position:0% moving on to the characteristics so 00:10:33.000 --> 00:10:34.850 align:start position:0% moving on to the characteristics so we'll<00:10:33.420> look<00:10:33.540> at<00:10:33.660> proving<00:10:33.959> systems<00:10:34.740> um<00:10:34.740> so 00:10:34.850 --> 00:10:34.860 align:start position:0% we'll look at proving systems um so 00:10:34.860 --> 00:10:36.410 align:start position:0% we'll look at proving systems um so you're<00:10:35.040> proving<00:10:35.339> systems<00:10:35.700> here<00:10:35.880> that<00:10:36.240> are 00:10:36.410 --> 00:10:36.420 align:start position:0% you're proving systems here that are 00:10:36.420 --> 00:10:38.509 align:start position:0% you're proving systems here that are actually<00:10:36.600> being<00:10:36.839> verified<00:10:37.200> on<00:10:37.500> main<00:10:37.680> chain 00:10:38.509 --> 00:10:38.519 align:start position:0% actually being verified on main chain 00:10:38.519 --> 00:10:40.610 align:start position:0% actually being verified on main chain um<00:10:38.640> you<00:10:38.820> have<00:10:39.000> your<00:10:39.720> your<00:10:39.720> Classics<00:10:40.260> I'm<00:10:40.440> sure 00:10:40.610 --> 00:10:40.620 align:start position:0% um you have your your Classics I'm sure 00:10:40.620 --> 00:10:41.750 align:start position:0% um you have your your Classics I'm sure you<00:10:40.680> guys<00:10:40.800> have<00:10:40.920> all<00:10:41.040> heard<00:10:41.220> of<00:10:41.339> these<00:10:41.519> but 00:10:41.750 --> 00:10:41.760 align:start position:0% you guys have all heard of these but 00:10:41.760 --> 00:10:44.630 align:start position:0% you guys have all heard of these but your<00:10:42.120> growth<00:10:42.480> 16<00:10:42.660> from<00:10:43.080> 2016.<00:10:44.160> um<00:10:44.160> that<00:10:44.399> runs 00:10:44.630 --> 00:10:44.640 align:start position:0% your growth 16 from 2016. um that runs 00:10:44.640 --> 00:10:47.030 align:start position:0% your growth 16 from 2016. um that runs your<00:10:44.760> tornado<00:10:45.060> cash<00:10:45.360> your<00:10:45.959> Hermes<00:10:46.380> your<00:10:46.800> Loop 00:10:47.030 --> 00:10:47.040 align:start position:0% your tornado cash your Hermes your Loop 00:10:47.040 --> 00:10:49.610 align:start position:0% your tornado cash your Hermes your Loop ring<00:10:47.579> um<00:10:47.579> in<00:10:47.880> a<00:10:48.000> bunch<00:10:48.120> other<00:10:48.480> uh<00:10:48.959> different<00:10:49.200> uh 00:10:49.610 --> 00:10:49.620 align:start position:0% ring um in a bunch other uh different uh 00:10:49.620 --> 00:10:52.190 align:start position:0% ring um in a bunch other uh different uh privacy<00:10:50.100> functions<00:10:50.640> you<00:10:51.240> have<00:10:51.420> plonk<00:10:52.140> um 00:10:52.190 --> 00:10:52.200 align:start position:0% privacy functions you have plonk um 00:10:52.200 --> 00:10:54.769 align:start position:0% privacy functions you have plonk um which<00:10:52.440> is<00:10:52.500> asked<00:10:52.860> to<00:10:52.920> connect<00:10:53.160> ZK<00:10:53.880> sync<00:10:54.720> um 00:10:54.769 --> 00:10:54.779 align:start position:0% which is asked to connect ZK sync um 00:10:54.779 --> 00:10:57.110 align:start position:0% which is asked to connect ZK sync um then<00:10:55.260> you<00:10:55.440> have<00:10:55.560> turbo<00:10:56.040> plug<00:10:56.279> which<00:10:56.700> is<00:10:56.880> the 00:10:57.110 --> 00:10:57.120 align:start position:0% then you have turbo plug which is the 00:10:57.120 --> 00:10:59.810 align:start position:0% then you have turbo plug which is the original<00:10:57.180> Aztec<00:10:58.260> um<00:10:58.260> Aztec<00:10:59.220> connect<00:10:59.339> uses 00:10:59.810 --> 00:10:59.820 align:start position:0% original Aztec um Aztec connect uses 00:10:59.820 --> 00:11:01.910 align:start position:0% original Aztec um Aztec connect uses turbo<00:11:00.180> Planck<00:11:00.660> before<00:11:00.839> it<00:11:01.079> gets<00:11:01.260> on<00:11:01.380> chain<00:11:01.560> but 00:11:01.910 --> 00:11:01.920 align:start position:0% turbo Planck before it gets on chain but 00:11:01.920 --> 00:11:03.710 align:start position:0% turbo Planck before it gets on chain but then<00:11:02.040> it<00:11:02.160> uses<00:11:02.459> Planck<00:11:02.940> on<00:11:03.060> chain<00:11:03.300> if<00:11:03.540> that 00:11:03.710 --> 00:11:03.720 align:start position:0% then it uses Planck on chain if that 00:11:03.720 --> 00:11:05.930 align:start position:0% then it uses Planck on chain if that makes<00:11:03.839> any<00:11:04.019> sense<00:11:04.200> then<00:11:05.160> you<00:11:05.339> have<00:11:05.399> Halo<00:11:05.880> 2 00:11:05.930 --> 00:11:05.940 align:start position:0% makes any sense then you have Halo 2 00:11:05.940 --> 00:11:08.690 align:start position:0% makes any sense then you have Halo 2 which<00:11:06.240> is<00:11:06.360> coming<00:11:06.540> out<00:11:06.720> zcash<00:11:07.620> uses<00:11:07.920> it<00:11:08.459> um<00:11:08.459> and 00:11:08.690 --> 00:11:08.700 align:start position:0% which is coming out zcash uses it um and 00:11:08.700 --> 00:11:11.990 align:start position:0% which is coming out zcash uses it um and then<00:11:08.880> also<00:11:09.240> scroll<00:11:09.959> is<00:11:10.320> going<00:11:10.560> to<00:11:10.800> deploy<00:11:11.760> with 00:11:11.990 --> 00:11:12.000 align:start position:0% then also scroll is going to deploy with 00:11:12.000 --> 00:11:14.150 align:start position:0% then also scroll is going to deploy with it<00:11:12.180> most<00:11:13.019> people<00:11:13.200> I<00:11:13.440> talk<00:11:13.560> to<00:11:13.740> are<00:11:13.980> really 00:11:14.150 --> 00:11:14.160 align:start position:0% it most people I talk to are really 00:11:14.160 --> 00:11:16.150 align:start position:0% it most people I talk to are really moving<00:11:14.459> towards<00:11:14.760> that<00:11:14.880> Halo<00:11:15.300> 2 00:11:16.150 --> 00:11:16.160 align:start position:0% moving towards that Halo 2 00:11:16.160 --> 00:11:18.230 align:start position:0% moving towards that Halo 2 move<00:11:17.160> it<00:11:17.399> seems<00:11:17.640> like<00:11:17.700> it's<00:11:17.820> a<00:11:18.000> really<00:11:18.060> good 00:11:18.230 --> 00:11:18.240 align:start position:0% move it seems like it's a really good 00:11:18.240 --> 00:11:20.210 align:start position:0% move it seems like it's a really good proving<00:11:18.600> system<00:11:18.839> so<00:11:19.620> um<00:11:19.680> it's<00:11:19.860> not<00:11:19.980> on<00:11:20.100> main 00:11:20.210 --> 00:11:20.220 align:start position:0% proving system so um it's not on main 00:11:20.220 --> 00:11:22.069 align:start position:0% proving system so um it's not on main chain<00:11:20.459> yet<00:11:20.640> that<00:11:20.880> I've<00:11:21.000> seen<00:11:21.180> so<00:11:21.600> then<00:11:21.899> you 00:11:22.069 --> 00:11:22.079 align:start position:0% chain yet that I've seen so then you 00:11:22.079 --> 00:11:23.930 align:start position:0% chain yet that I've seen so then you have<00:11:22.200> your<00:11:22.260> Starks<00:11:22.740> on<00:11:23.100> and<00:11:23.339> that<00:11:23.519> includes 00:11:23.930 --> 00:11:23.940 align:start position:0% have your Starks on and that includes 00:11:23.940 --> 00:11:25.610 align:start position:0% have your Starks on and that includes all<00:11:24.060> your<00:11:24.180> starboard<00:11:24.600> projects 00:11:25.610 --> 00:11:25.620 align:start position:0% all your starboard projects 00:11:25.620 --> 00:11:29.030 align:start position:0% all your starboard projects so<00:11:26.339> Starks<00:11:27.180> versus<00:11:27.360> snarks 00:11:29.030 --> 00:11:29.040 align:start position:0% so Starks versus snarks 00:11:29.040 --> 00:11:32.030 align:start position:0% so Starks versus snarks snarks<00:11:29.760> the<00:11:30.060> succinct<00:11:31.040> non-interactive 00:11:32.030 --> 00:11:32.040 align:start position:0% snarks the succinct non-interactive 00:11:32.040 --> 00:11:35.269 align:start position:0% snarks the succinct non-interactive argument<00:11:32.519> of<00:11:32.760> knowledge<00:11:33.320> and<00:11:34.320> that<00:11:34.980> then 00:11:35.269 --> 00:11:35.279 align:start position:0% argument of knowledge and that then 00:11:35.279 --> 00:11:37.509 align:start position:0% argument of knowledge and that then there's<00:11:35.519> Starks<00:11:35.940> which<00:11:36.060> are<00:11:36.360> scalable 00:11:37.509 --> 00:11:37.519 align:start position:0% there's Starks which are scalable 00:11:37.519 --> 00:11:40.190 align:start position:0% there's Starks which are scalable transparent<00:11:38.519> arguments<00:11:39.000> of<00:11:39.120> knowledge<00:11:39.420> and 00:11:40.190 --> 00:11:40.200 align:start position:0% transparent arguments of knowledge and 00:11:40.200 --> 00:11:42.490 align:start position:0% transparent arguments of knowledge and the<00:11:40.500> major<00:11:40.620> difference<00:11:40.860> between<00:11:41.160> the<00:11:41.459> two 00:11:42.490 --> 00:11:42.500 align:start position:0% the major difference between the two 00:11:42.500 --> 00:11:45.410 align:start position:0% the major difference between the two there's<00:11:43.500> a<00:11:43.620> bunch<00:11:43.740> of<00:11:43.860> them<00:11:43.980> these<00:11:44.760> are<00:11:44.940> the 00:11:45.410 --> 00:11:45.420 align:start position:0% there's a bunch of them these are the 00:11:45.420 --> 00:11:47.329 align:start position:0% there's a bunch of them these are the base<00:11:45.540> level<00:11:45.779> for<00:11:46.079> what<00:11:46.260> happens<00:11:46.440> but<00:11:46.860> Quantum 00:11:47.329 --> 00:11:47.339 align:start position:0% base level for what happens but Quantum 00:11:47.339 --> 00:11:49.670 align:start position:0% base level for what happens but Quantum Computing<00:11:47.760> is<00:11:48.600> probably<00:11:48.899> going<00:11:49.320> to<00:11:49.440> be<00:11:49.560> able 00:11:49.670 --> 00:11:49.680 align:start position:0% Computing is probably going to be able 00:11:49.680 --> 00:11:52.970 align:start position:0% Computing is probably going to be able to<00:11:49.860> take<00:11:49.980> down<00:11:50.220> snarks<00:11:50.940> or<00:11:51.300> but<00:11:51.779> Starks<00:11:52.680> will 00:11:52.970 --> 00:11:52.980 align:start position:0% to take down snarks or but Starks will 00:11:52.980 --> 00:11:55.610 align:start position:0% to take down snarks or but Starks will probably<00:11:53.100> be<00:11:53.279> resistant<00:11:53.700> to<00:11:53.820> it<00:11:54.000> so<00:11:54.500> what<00:11:55.500> is 00:11:55.610 --> 00:11:55.620 align:start position:0% probably be resistant to it so what is 00:11:55.620 --> 00:11:57.590 align:start position:0% probably be resistant to it so what is quantum<00:11:55.980> Computing<00:11:56.220> when<00:11:56.459> will<00:11:56.640> it<00:11:56.760> come 00:11:57.590 --> 00:11:57.600 align:start position:0% quantum Computing when will it come 00:11:57.600 --> 00:12:00.590 align:start position:0% quantum Computing when will it come I<00:11:58.140> have<00:11:58.260> no<00:11:58.440> idea<00:11:58.740> but<00:11:59.760> um<00:11:59.760> if<00:12:00.060> it<00:12:00.180> does<00:12:00.300> this<00:12:00.480> is 00:12:00.590 --> 00:12:00.600 align:start position:0% I have no idea but um if it does this is 00:12:00.600 --> 00:12:01.730 align:start position:0% I have no idea but um if it does this is what<00:12:00.720> will<00:12:00.839> happen 00:12:01.730 --> 00:12:01.740 align:start position:0% what will happen 00:12:01.740 --> 00:12:04.370 align:start position:0% what will happen so<00:12:02.339> looking<00:12:02.940> at<00:12:03.180> these<00:12:03.480> different 00:12:04.370 --> 00:12:04.380 align:start position:0% so looking at these different 00:12:04.380 --> 00:12:06.170 align:start position:0% so looking at these different um proving<00:12:04.800> systems<00:12:05.160> you<00:12:05.459> have<00:12:05.579> graph<00:12:06.000> 16 00:12:06.170 --> 00:12:06.180 align:start position:0% um proving systems you have graph 16 00:12:06.180 --> 00:12:07.670 align:start position:0% um proving systems you have graph 16 which<00:12:06.660> is<00:12:06.779> in<00:12:06.959> blue 00:12:07.670 --> 00:12:07.680 align:start position:0% which is in blue 00:12:07.680 --> 00:12:09.590 align:start position:0% which is in blue um really<00:12:08.100> taking<00:12:08.339> off<00:12:08.640> that's<00:12:09.240> on<00:12:09.420> the<00:12:09.540> back 00:12:09.590 --> 00:12:09.600 align:start position:0% um really taking off that's on the back 00:12:09.600 --> 00:12:12.949 align:start position:0% um really taking off that's on the back of<00:12:09.779> tornado<00:12:10.079> cache<00:12:10.560> as<00:12:11.100> well<00:12:11.220> as<00:12:11.519> loopering 00:12:12.949 --> 00:12:12.959 align:start position:0% of tornado cache as well as loopering 00:12:12.959 --> 00:12:14.990 align:start position:0% of tornado cache as well as loopering and<00:12:13.260> then<00:12:13.440> you<00:12:13.620> have<00:12:13.800> down<00:12:14.459> below<00:12:14.640> you<00:12:14.880> have 00:12:14.990 --> 00:12:15.000 align:start position:0% and then you have down below you have 00:12:15.000 --> 00:12:17.090 align:start position:0% and then you have down below you have your<00:12:15.300> Stark<00:12:15.899> um<00:12:15.899> fries<00:12:16.560> that<00:12:16.860> are<00:12:16.980> coming 00:12:17.090 --> 00:12:17.100 align:start position:0% your Stark um fries that are coming 00:12:17.100 --> 00:12:19.370 align:start position:0% your Stark um fries that are coming through<00:12:17.339> those<00:12:17.880> are<00:12:18.000> the<00:12:18.060> starkware<00:12:18.480> projects 00:12:19.370 --> 00:12:19.380 align:start position:0% through those are the starkware projects 00:12:19.380 --> 00:12:23.090 align:start position:0% through those are the starkware projects um<00:12:19.440> they<00:12:19.680> have<00:12:19.860> really<00:12:20.040> taken<00:12:20.399> off<00:12:21.019> dydx<00:12:22.100> posts 00:12:23.090 --> 00:12:23.100 align:start position:0% um they have really taken off dydx posts 00:12:23.100 --> 00:12:25.790 align:start position:0% um they have really taken off dydx posts a<00:12:23.339> lot<00:12:23.459> of<00:12:23.579> data<00:12:24.240> to<00:12:24.360> chain<00:12:24.540> often<00:12:25.079> and<00:12:25.620> then 00:12:25.790 --> 00:12:25.800 align:start position:0% a lot of data to chain often and then 00:12:25.800 --> 00:12:28.310 align:start position:0% a lot of data to chain often and then you<00:12:25.920> have<00:12:26.040> your<00:12:26.579> plonks<00:12:27.060> and<00:12:27.480> unknowns<00:12:28.200> are 00:12:28.310 --> 00:12:28.320 align:start position:0% you have your plonks and unknowns are 00:12:28.320 --> 00:12:30.470 align:start position:0% you have your plonks and unknowns are probably<00:12:28.500> blocks<00:12:29.279> um<00:12:29.339> but<00:12:29.579> I<00:12:29.880> didn't<00:12:30.180> wasn't 00:12:30.470 --> 00:12:30.480 align:start position:0% probably blocks um but I didn't wasn't 00:12:30.480 --> 00:12:33.590 align:start position:0% probably blocks um but I didn't wasn't quite<00:12:30.839> confident<00:12:31.440> enough<00:12:31.560> to<00:12:31.800> say<00:12:31.920> that<00:12:32.100> so 00:12:33.590 --> 00:12:33.600 align:start position:0% quite confident enough to say that so 00:12:33.600 --> 00:12:35.870 align:start position:0% quite confident enough to say that so um<00:12:33.660> okay<00:12:33.779> let's<00:12:33.959> talk<00:12:34.079> about<00:12:34.200> trusted<00:12:34.560> setups 00:12:35.870 --> 00:12:35.880 align:start position:0% um okay let's talk about trusted setups 00:12:35.880 --> 00:12:38.690 align:start position:0% um okay let's talk about trusted setups so<00:12:36.540> a<00:12:37.260> trusted<00:12:37.560> setup<00:12:37.860> is<00:12:38.220> where<00:12:38.399> on<00:12:38.640> the 00:12:38.690 --> 00:12:38.700 align:start position:0% so a trusted setup is where on the 00:12:38.700 --> 00:12:40.790 align:start position:0% so a trusted setup is where on the elliptic<00:12:39.060> curve<00:12:39.899> um<00:12:39.899> you<00:12:40.200> should<00:12:40.380> evaluate 00:12:40.790 --> 00:12:40.800 align:start position:0% elliptic curve um you should evaluate 00:12:40.800 --> 00:12:43.970 align:start position:0% elliptic curve um you should evaluate the<00:12:41.100> different<00:12:41.220> ZK<00:12:42.120> proof<00:12:42.480> so<00:12:42.779> it's<00:12:43.019> it's<00:12:43.560> kind 00:12:43.970 --> 00:12:43.980 align:start position:0% the different ZK proof so it's it's kind 00:12:43.980 --> 00:12:46.490 align:start position:0% the different ZK proof so it's it's kind of<00:12:44.100> an<00:12:44.820> agreement<00:12:45.300> and<00:12:45.540> a<00:12:45.720> spot<00:12:45.839> that<00:12:46.500> um 00:12:46.490 --> 00:12:46.500 align:start position:0% of an agreement and a spot that um 00:12:46.500 --> 00:12:48.769 align:start position:0% of an agreement and a spot that um approver<00:12:46.980> and<00:12:47.160> a<00:12:47.220> verifier<00:12:47.579> can<00:12:47.940> done<00:12:48.300> kind<00:12:48.720> of 00:12:48.769 --> 00:12:48.779 align:start position:0% approver and a verifier can done kind of 00:12:48.779 --> 00:12:50.389 align:start position:0% approver and a verifier can done kind of verify<00:12:49.260> through 00:12:50.389 --> 00:12:50.399 align:start position:0% verify through 00:12:50.399 --> 00:12:51.710 align:start position:0% verify through um what<00:12:50.700> that<00:12:50.820> snark's<00:12:51.360> going<00:12:51.420> to<00:12:51.480> look<00:12:51.540> like 00:12:51.710 --> 00:12:51.720 align:start position:0% um what that snark's going to look like 00:12:51.720 --> 00:12:53.569 align:start position:0% um what that snark's going to look like so<00:12:52.139> I'd<00:12:52.740> like<00:12:52.860> to<00:12:53.040> think<00:12:53.160> of<00:12:53.279> it<00:12:53.399> like<00:12:53.459> a 00:12:53.569 --> 00:12:53.579 align:start position:0% so I'd like to think of it like a 00:12:53.579 --> 00:12:55.490 align:start position:0% so I'd like to think of it like a trustful<00:12:53.940> how<00:12:54.600> many<00:12:55.019> people<00:12:55.139> have<00:12:55.260> done<00:12:55.380> trust 00:12:55.490 --> 00:12:55.500 align:start position:0% trustful how many people have done trust 00:12:55.500 --> 00:12:57.829 align:start position:0% trustful how many people have done trust Falls<00:12:55.740> before<00:12:55.980> in<00:12:56.160> their<00:12:56.279> life<00:12:56.880> a<00:12:57.240> couple<00:12:57.480> yeah 00:12:57.829 --> 00:12:57.839 align:start position:0% Falls before in their life a couple yeah 00:12:57.839 --> 00:12:59.389 align:start position:0% Falls before in their life a couple yeah it's<00:12:58.320> scary 00:12:59.389 --> 00:12:59.399 align:start position:0% it's scary 00:12:59.399 --> 00:13:01.730 align:start position:0% it's scary um<00:12:59.459> so<00:12:59.880> you<00:13:00.000> get<00:13:00.180> up<00:13:00.300> there<00:13:00.540> on<00:13:00.959> a<00:13:01.139> big<00:13:01.320> standing 00:13:01.730 --> 00:13:01.740 align:start position:0% um so you get up there on a big standing 00:13:01.740 --> 00:13:04.190 align:start position:0% um so you get up there on a big standing and<00:13:01.920> then<00:13:02.100> you<00:13:02.220> fall<00:13:02.399> backwards<00:13:03.000> and<00:13:03.480> as<00:13:04.019> long 00:13:04.190 --> 00:13:04.200 align:start position:0% and then you fall backwards and as long 00:13:04.200 --> 00:13:06.110 align:start position:0% and then you fall backwards and as long as<00:13:04.320> one<00:13:04.740> strong<00:13:04.980> person<00:13:05.279> below<00:13:05.700> you<00:13:05.760> is<00:13:05.940> there 00:13:06.110 --> 00:13:06.120 align:start position:0% as one strong person below you is there 00:13:06.120 --> 00:13:07.790 align:start position:0% as one strong person below you is there to<00:13:06.300> catch<00:13:06.540> you<00:13:06.600> then<00:13:06.779> you<00:13:06.959> should<00:13:07.019> be<00:13:07.200> good<00:13:07.320> so 00:13:07.790 --> 00:13:07.800 align:start position:0% to catch you then you should be good so 00:13:07.800 --> 00:13:10.310 align:start position:0% to catch you then you should be good so as<00:13:08.160> long<00:13:08.399> as<00:13:08.519> the<00:13:09.180> trusted<00:13:09.779> setup<00:13:10.019> is<00:13:10.079> kind<00:13:10.200> of 00:13:10.310 --> 00:13:10.320 align:start position:0% as long as the trusted setup is kind of 00:13:10.320 --> 00:13:13.190 align:start position:0% as long as the trusted setup is kind of similar<00:13:10.500> if<00:13:10.920> everybody's<00:13:11.519> toxic<00:13:12.240> waste<00:13:12.720> gets 00:13:13.190 --> 00:13:13.200 align:start position:0% similar if everybody's toxic waste gets 00:13:13.200 --> 00:13:14.750 align:start position:0% similar if everybody's toxic waste gets collected<00:13:13.560> together<00:13:13.740> if<00:13:14.220> everyone<00:13:14.399> gives 00:13:14.750 --> 00:13:14.760 align:start position:0% collected together if everyone gives 00:13:14.760 --> 00:13:15.949 align:start position:0% collected together if everyone gives their<00:13:15.000> secret<00:13:15.180> out 00:13:15.949 --> 00:13:15.959 align:start position:0% their secret out 00:13:15.959 --> 00:13:17.210 align:start position:0% their secret out um it<00:13:16.200> doesn't<00:13:16.320> want<00:13:16.500> to<00:13:16.620> catch<00:13:16.800> you<00:13:16.860> or<00:13:17.100> is 00:13:17.210 --> 00:13:17.220 align:start position:0% um it doesn't want to catch you or is 00:13:17.220 --> 00:13:20.030 align:start position:0% um it doesn't want to catch you or is distracted<00:13:17.700> then<00:13:18.600> um<00:13:18.660> the<00:13:18.839> snark<00:13:19.139> can<00:13:19.380> be 00:13:20.030 --> 00:13:20.040 align:start position:0% distracted then um the snark can be 00:13:20.040 --> 00:13:22.370 align:start position:0% distracted then um the snark can be um<00:13:20.100> then<00:13:20.880> the<00:13:21.180> chest<00:13:21.420> is<00:13:21.600> set<00:13:21.720> up 00:13:22.370 --> 00:13:22.380 align:start position:0% um then the chest is set up 00:13:22.380 --> 00:13:25.250 align:start position:0% um then the chest is set up um will<00:13:22.980> not<00:13:23.519> work<00:13:23.820> and<00:13:24.600> someone<00:13:24.899> will<00:13:25.139> be 00:13:25.250 --> 00:13:25.260 align:start position:0% um will not work and someone will be 00:13:25.260 --> 00:13:28.009 align:start position:0% um will not work and someone will be able<00:13:25.380> to<00:13:25.500> write<00:13:25.680> proofs<00:13:26.279> that<00:13:26.519> will<00:13:27.180> um 00:13:28.009 --> 00:13:28.019 align:start position:0% able to write proofs that will um 00:13:28.019 --> 00:13:29.810 align:start position:0% able to write proofs that will um be<00:13:28.620> false<00:13:28.980> positives<00:13:29.279> and<00:13:29.519> they'll<00:13:29.639> be<00:13:29.760> able 00:13:29.810 --> 00:13:29.820 align:start position:0% be false positives and they'll be able 00:13:29.820 --> 00:13:30.949 align:start position:0% be false positives and they'll be able to<00:13:29.940> take<00:13:30.060> money<00:13:30.180> from<00:13:30.360> you<00:13:30.480> if<00:13:30.660> that<00:13:30.779> makes 00:13:30.949 --> 00:13:30.959 align:start position:0% to take money from you if that makes 00:13:30.959 --> 00:13:32.690 align:start position:0% to take money from you if that makes sense<00:13:31.139> so 00:13:32.690 --> 00:13:32.700 align:start position:0% sense so 00:13:32.700 --> 00:13:34.610 align:start position:0% sense so um this<00:13:33.120> requires<00:13:33.600> one<00:13:33.839> honest<00:13:34.200> participant 00:13:34.610 --> 00:13:34.620 align:start position:0% um this requires one honest participant 00:13:34.620 --> 00:13:37.910 align:start position:0% um this requires one honest participant from<00:13:34.920> the<00:13:35.040> mo<00:13:35.160> from<00:13:35.459> the<00:13:35.519> MPC<00:13:36.240> um<00:13:36.300> ceremony 00:13:37.910 --> 00:13:37.920 align:start position:0% from the mo from the MPC um ceremony 00:13:37.920 --> 00:13:40.129 align:start position:0% from the mo from the MPC um ceremony I<00:13:38.399> also<00:13:38.639> like<00:13:38.760> to<00:13:38.880> think<00:13:38.940> of<00:13:39.060> it<00:13:39.180> like<00:13:39.300> Thanos 00:13:40.129 --> 00:13:40.139 align:start position:0% I also like to think of it like Thanos 00:13:40.139 --> 00:13:41.629 align:start position:0% I also like to think of it like Thanos um<00:13:40.260> if<00:13:40.380> you<00:13:40.560> have<00:13:40.620> enough<00:13:40.800> Infinity<00:13:41.040> Stones<00:13:41.459> if 00:13:41.629 --> 00:13:41.639 align:start position:0% um if you have enough Infinity Stones if 00:13:41.639 --> 00:13:42.889 align:start position:0% um if you have enough Infinity Stones if you<00:13:41.700> have<00:13:41.820> them<00:13:41.940> all<00:13:42.060> you<00:13:42.360> can<00:13:42.420> destroy<00:13:42.720> the 00:13:42.889 --> 00:13:42.899 align:start position:0% you have them all you can destroy the 00:13:42.899 --> 00:13:45.350 align:start position:0% you have them all you can destroy the proof<00:13:43.200> and<00:13:43.380> it'll<00:13:43.560> be<00:13:43.740> good<00:13:43.860> so<00:13:44.100> uh<00:13:44.760> it's<00:13:45.060> bad 00:13:45.350 --> 00:13:45.360 align:start position:0% proof and it'll be good so uh it's bad 00:13:45.360 --> 00:13:46.550 align:start position:0% proof and it'll be good so uh it's bad actually 00:13:46.550 --> 00:13:46.560 align:start position:0% actually 00:13:46.560 --> 00:13:49.490 align:start position:0% actually okay<00:13:47.040> so<00:13:47.820> um<00:13:47.880> what<00:13:48.000> are<00:13:48.120> the<00:13:48.240> trusted<00:13:48.540> setups 00:13:49.490 --> 00:13:49.500 align:start position:0% okay so um what are the trusted setups 00:13:49.500 --> 00:13:51.170 align:start position:0% okay so um what are the trusted setups um we<00:13:50.220> have 00:13:51.170 --> 00:13:51.180 align:start position:0% um we have 00:13:51.180 --> 00:13:53.990 align:start position:0% um we have um<00:13:51.240> growth<00:13:52.019> 16<00:13:52.260> over<00:13:52.680> there<00:13:52.860> on<00:13:52.980> the<00:13:53.100> end<00:13:53.579> um<00:13:53.700> it 00:13:53.990 --> 00:13:54.000 align:start position:0% um growth 16 over there on the end um it 00:13:54.000 --> 00:13:56.870 align:start position:0% um growth 16 over there on the end um it has<00:13:54.120> a<00:13:54.720> two-phase<00:13:55.500> trusted<00:13:55.980> setup 00:13:56.870 --> 00:13:56.880 align:start position:0% has a two-phase trusted setup 00:13:56.880 --> 00:13:59.150 align:start position:0% has a two-phase trusted setup um<00:13:56.940> and<00:13:57.180> then<00:13:57.420> the<00:13:58.019> universal<00:13:58.500> setups<00:13:58.920> came<00:13:59.040> in 00:13:59.150 --> 00:13:59.160 align:start position:0% um and then the universal setups came in 00:13:59.160 --> 00:14:01.550 align:start position:0% um and then the universal setups came in and<00:13:59.519> that's<00:13:59.639> Planck<00:14:00.180> and<00:14:00.240> turbo<00:14:00.480> plunk<00:14:00.839> and 00:14:01.550 --> 00:14:01.560 align:start position:0% and that's Planck and turbo plunk and 00:14:01.560 --> 00:14:04.550 align:start position:0% and that's Planck and turbo plunk and that<00:14:01.740> only<00:14:01.980> requires<00:14:02.459> one<00:14:02.820> so<00:14:03.420> whereas<00:14:04.200> Roth 00:14:04.550 --> 00:14:04.560 align:start position:0% that only requires one so whereas Roth 00:14:04.560 --> 00:14:07.730 align:start position:0% that only requires one so whereas Roth 16<00:14:04.800> needs<00:14:05.459> a<00:14:05.880> new<00:14:06.000> ZK<00:14:06.420> circuit<00:14:06.899> or<00:14:07.139> needs<00:14:07.500> a<00:14:07.620> new 00:14:07.730 --> 00:14:07.740 align:start position:0% 16 needs a new ZK circuit or needs a new 00:14:07.740 --> 00:14:10.790 align:start position:0% 16 needs a new ZK circuit or needs a new Pro<00:14:08.459> needs<00:14:08.940> a<00:14:09.000> new<00:14:09.180> entrusted<00:14:09.720> ceremony<00:14:10.079> for 00:14:10.790 --> 00:14:10.800 align:start position:0% Pro needs a new entrusted ceremony for 00:14:10.800 --> 00:14:14.629 align:start position:0% Pro needs a new entrusted ceremony for the<00:14:11.700> um<00:14:11.760> each<00:14:12.060> circuit<00:14:12.720> that<00:14:12.899> it<00:14:12.959> produces 00:14:14.629 --> 00:14:14.639 align:start position:0% the um each circuit that it produces 00:14:14.639 --> 00:14:16.670 align:start position:0% the um each circuit that it produces um<00:14:14.700> Planck<00:14:15.600> and<00:14:15.779> turbo<00:14:15.959> Planck<00:14:16.320> have<00:14:16.500> a 00:14:16.670 --> 00:14:16.680 align:start position:0% um Planck and turbo Planck have a 00:14:16.680 --> 00:14:18.949 align:start position:0% um Planck and turbo Planck have a universal<00:14:17.040> setup<00:14:17.339> and<00:14:17.820> that<00:14:17.940> allows<00:14:18.300> them<00:14:18.480> to 00:14:18.949 --> 00:14:18.959 align:start position:0% universal setup and that allows them to 00:14:18.959 --> 00:14:21.650 align:start position:0% universal setup and that allows them to only<00:14:19.560> have<00:14:19.800> one<00:14:20.160> total<00:14:20.519> ceremony<00:14:20.940> so<00:14:21.480> if 00:14:21.650 --> 00:14:21.660 align:start position:0% only have one total ceremony so if 00:14:21.660 --> 00:14:23.509 align:start position:0% only have one total ceremony so if anyone<00:14:21.959> here<00:14:22.139> wanted<00:14:22.380> to<00:14:22.560> create<00:14:22.680> a<00:14:22.920> plonk<00:14:23.279> you 00:14:23.509 --> 00:14:23.519 align:start position:0% anyone here wanted to create a plonk you 00:14:23.519 --> 00:14:25.069 align:start position:0% anyone here wanted to create a plonk you could<00:14:23.579> use<00:14:23.820> the<00:14:24.120> universal<00:14:24.480> ceremony<00:14:24.839> that's 00:14:25.069 --> 00:14:25.079 align:start position:0% could use the universal ceremony that's 00:14:25.079 --> 00:14:26.329 align:start position:0% could use the universal ceremony that's already<00:14:25.260> been<00:14:25.500> created 00:14:26.329 --> 00:14:26.339 align:start position:0% already been created 00:14:26.339 --> 00:14:27.769 align:start position:0% already been created um and<00:14:26.579> already<00:14:26.760> been<00:14:26.940> done<00:14:27.120> and<00:14:27.540> then<00:14:27.720> you 00:14:27.769 --> 00:14:27.779 align:start position:0% um and already been done and then you 00:14:27.779 --> 00:14:30.050 align:start position:0% um and already been done and then you have<00:14:27.899> Halo<00:14:28.260> 2<00:14:28.440> and<00:14:28.740> Starks<00:14:29.519> um<00:14:29.519> they<00:14:29.760> do<00:14:29.880> not 00:14:30.050 --> 00:14:30.060 align:start position:0% have Halo 2 and Starks um they do not 00:14:30.060 --> 00:14:32.210 align:start position:0% have Halo 2 and Starks um they do not require<00:14:30.240> trusted<00:14:30.839> setups<00:14:31.260> so<00:14:31.560> that's 00:14:32.210 --> 00:14:32.220 align:start position:0% require trusted setups so that's 00:14:32.220 --> 00:14:33.889 align:start position:0% require trusted setups so that's obviously<00:14:32.700> you<00:14:32.880> want<00:14:33.000> the<00:14:33.180> least<00:14:33.300> amount<00:14:33.660> of 00:14:33.889 --> 00:14:33.899 align:start position:0% obviously you want the least amount of 00:14:33.899 --> 00:14:35.629 align:start position:0% obviously you want the least amount of trusted<00:14:34.260> setups<00:14:34.620> as<00:14:34.740> you<00:14:34.860> can 00:14:35.629 --> 00:14:35.639 align:start position:0% trusted setups as you can 00:14:35.639 --> 00:14:37.790 align:start position:0% trusted setups as you can so<00:14:36.120> moving<00:14:36.420> on<00:14:36.540> on<00:14:36.839> the<00:14:37.200> actual<00:14:37.380> projects 00:14:37.790 --> 00:14:37.800 align:start position:0% so moving on on the actual projects 00:14:37.800 --> 00:14:39.470 align:start position:0% so moving on on the actual projects themselves<00:14:38.100> you<00:14:38.760> have 00:14:39.470 --> 00:14:39.480 align:start position:0% themselves you have 00:14:39.480 --> 00:14:42.290 align:start position:0% themselves you have um<00:14:39.540> graph<00:14:40.199> 16s<00:14:40.800> are<00:14:41.100> Loop<00:14:41.459> ring<00:14:41.699> polygon 00:14:42.290 --> 00:14:42.300 align:start position:0% um graph 16s are Loop ring polygon 00:14:42.300 --> 00:14:45.110 align:start position:0% um graph 16s are Loop ring polygon Hermes<00:14:42.680> their<00:14:43.680> withdrawal<00:14:44.160> and<00:14:44.459> then<00:14:44.699> tornado 00:14:45.110 --> 00:14:45.120 align:start position:0% Hermes their withdrawal and then tornado 00:14:45.120 --> 00:14:46.910 align:start position:0% Hermes their withdrawal and then tornado cash<00:14:45.660> um<00:14:45.720> those<00:14:45.839> are<00:14:45.959> the<00:14:46.019> major<00:14:46.199> ones<00:14:46.560> that 00:14:46.910 --> 00:14:46.920 align:start position:0% cash um those are the major ones that 00:14:46.920 --> 00:14:50.030 align:start position:0% cash um those are the major ones that are<00:14:47.100> currently<00:14:47.279> being<00:14:47.459> in<00:14:47.820> operation<00:14:48.199> so<00:14:49.199> the 00:14:50.030 --> 00:14:50.040 align:start position:0% are currently being in operation so the 00:14:50.040 --> 00:14:52.189 align:start position:0% are currently being in operation so the number<00:14:50.220> these<00:14:50.880> are<00:14:50.940> trusted<00:14:51.360> setups<00:14:51.779> they<00:14:52.019> use 00:14:52.189 --> 00:14:52.199 align:start position:0% number these are trusted setups they use 00:14:52.199 --> 00:14:55.370 align:start position:0% number these are trusted setups they use the<00:14:52.380> Perpetual<00:14:52.800> powers<00:14:53.100> of<00:14:53.339> Tau<00:14:54.000> um<00:14:54.120> which<00:14:54.420> is 00:14:55.370 --> 00:14:55.380 align:start position:0% the Perpetual powers of Tau um which is 00:14:55.380 --> 00:14:58.129 align:start position:0% the Perpetual powers of Tau um which is um<00:14:55.440> basically<00:14:55.860> an<00:14:55.980> on-chain<00:14:56.459> on<00:14:57.120> step<00:14:57.420> one<00:14:57.660> for 00:14:58.129 --> 00:14:58.139 align:start position:0% um basically an on-chain on step one for 00:14:58.139 --> 00:15:01.069 align:start position:0% um basically an on-chain on step one for the<00:14:58.440> different<00:14:58.620> uh<00:14:59.459> trusted<00:15:00.360> setups<00:15:00.720> then 00:15:01.069 --> 00:15:01.079 align:start position:0% the different uh trusted setups then 00:15:01.079 --> 00:15:03.650 align:start position:0% the different uh trusted setups then they<00:15:01.560> had<00:15:01.680> a<00:15:01.860> step<00:15:02.040> two<00:15:02.279> that<00:15:02.880> step<00:15:03.180> two<00:15:03.360> these 00:15:03.650 --> 00:15:03.660 align:start position:0% they had a step two that step two these 00:15:03.660 --> 00:15:04.910 align:start position:0% they had a step two that step two these are<00:15:03.779> the<00:15:03.839> number<00:15:03.959> of<00:15:04.139> participants<00:15:04.560> that<00:15:04.800> were 00:15:04.910 --> 00:15:04.920 align:start position:0% are the number of participants that were 00:15:04.920 --> 00:15:07.189 align:start position:0% are the number of participants that were in<00:15:05.040> those<00:15:05.160> ceremonies<00:15:05.639> so<00:15:06.120> if<00:15:06.540> you<00:15:06.660> can<00:15:06.899> get<00:15:07.019> to 00:15:07.189 --> 00:15:07.199 align:start position:0% in those ceremonies so if you can get to 00:15:07.199 --> 00:15:08.990 align:start position:0% in those ceremonies so if you can get to 16<00:15:07.380> people<00:15:07.740> from<00:15:08.040> the<00:15:08.160> loop<00:15:08.399> ring<00:15:08.639> that<00:15:08.760> did<00:15:08.940> it 00:15:08.990 --> 00:15:09.000 align:start position:0% 16 people from the loop ring that did it 00:15:09.000 --> 00:15:11.569 align:start position:0% 16 people from the loop ring that did it if<00:15:09.300> they<00:15:09.420> all<00:15:09.540> compromised<00:15:10.139> then<00:15:10.440> that<00:15:10.680> will 00:15:11.569 --> 00:15:11.579 align:start position:0% if they all compromised then that will 00:15:11.579 --> 00:15:13.610 align:start position:0% if they all compromised then that will not<00:15:11.699> be<00:15:11.880> a<00:15:12.000> valid<00:15:12.240> just<00:15:12.420> the<00:15:12.600> setup<00:15:12.899> and<00:15:13.500> then 00:15:13.610 --> 00:15:13.620 align:start position:0% not be a valid just the setup and then 00:15:13.620 --> 00:15:16.009 align:start position:0% not be a valid just the setup and then those<00:15:13.800> funds<00:15:14.100> will<00:15:14.160> be<00:15:14.339> able<00:15:14.399> to<00:15:14.519> be<00:15:14.639> taken<00:15:14.880> so 00:15:16.009 --> 00:15:16.019 align:start position:0% those funds will be able to be taken so 00:15:16.019 --> 00:15:18.290 align:start position:0% those funds will be able to be taken so um<00:15:16.079> you<00:15:16.380> have<00:15:16.500> 16<00:15:16.980> for<00:15:17.339> Loop<00:15:17.699> ring<00:15:17.940> you<00:15:18.180> have 00:15:18.290 --> 00:15:18.300 align:start position:0% um you have 16 for Loop ring you have 00:15:18.300 --> 00:15:21.050 align:start position:0% um you have 16 for Loop ring you have six<00:15:18.959> participants<00:15:19.560> in<00:15:19.740> the<00:15:19.860> polygon<00:15:20.220> hermesis 00:15:21.050 --> 00:15:21.060 align:start position:0% six participants in the polygon hermesis 00:15:21.060 --> 00:15:23.269 align:start position:0% six participants in the polygon hermesis then<00:15:22.019> um<00:15:22.019> tornado<00:15:22.440> cache<00:15:22.680> had<00:15:22.800> a<00:15:22.920> whopping 00:15:23.269 --> 00:15:23.279 align:start position:0% then um tornado cache had a whopping 00:15:23.279 --> 00:15:26.449 align:start position:0% then um tornado cache had a whopping 1114. 00:15:26.449 --> 00:15:26.459 align:start position:0% 00:15:26.459 --> 00:15:28.550 align:start position:0% um moving<00:15:26.940> on<00:15:27.000> to<00:15:27.180> plaques<00:15:27.839> um<00:15:27.839> so<00:15:28.079> like<00:15:28.380> I 00:15:28.550 --> 00:15:28.560 align:start position:0% um moving on to plaques um so like I 00:15:28.560 --> 00:15:30.590 align:start position:0% um moving on to plaques um so like I said<00:15:28.680> there's<00:15:28.980> you<00:15:29.399> only<00:15:29.519> need<00:15:29.820> one<00:15:30.180> trusted 00:15:30.590 --> 00:15:30.600 align:start position:0% said there's you only need one trusted 00:15:30.600 --> 00:15:32.210 align:start position:0% said there's you only need one trusted setup<00:15:30.899> ceremony<00:15:31.260> to<00:15:31.500> be<00:15:31.620> correct<00:15:31.860> and<00:15:32.100> then 00:15:32.210 --> 00:15:32.220 align:start position:0% setup ceremony to be correct and then 00:15:32.220 --> 00:15:34.069 align:start position:0% setup ceremony to be correct and then anyone<00:15:32.459> can<00:15:32.639> use<00:15:32.760> it<00:15:32.880> so<00:15:33.180> they're<00:15:33.600> all<00:15:33.779> using 00:15:34.069 --> 00:15:34.079 align:start position:0% anyone can use it so they're all using 00:15:34.079 --> 00:15:36.949 align:start position:0% anyone can use it so they're all using the<00:15:34.320> Aztec<00:15:34.800> clock<00:15:34.980> Universal<00:15:35.519> setup<00:15:36.360> um<00:15:36.420> it<00:15:36.779> is 00:15:36.949 --> 00:15:36.959 align:start position:0% the Aztec clock Universal setup um it is 00:15:36.959 --> 00:15:39.110 align:start position:0% the Aztec clock Universal setup um it is all<00:15:37.199> these<00:15:37.620> you<00:15:37.740> can<00:15:37.860> see<00:15:37.980> asset<00:15:38.339> stations<00:15:39.120> um 00:15:39.110 --> 00:15:39.120 align:start position:0% all these you can see asset stations um 00:15:39.120 --> 00:15:40.790 align:start position:0% all these you can see asset stations um on<00:15:39.420> GitHub<00:15:39.720> to<00:15:39.959> see<00:15:40.079> how<00:15:40.199> they<00:15:40.320> worked<00:15:40.560> but 00:15:40.790 --> 00:15:40.800 align:start position:0% on GitHub to see how they worked but 00:15:40.800 --> 00:15:44.449 align:start position:0% on GitHub to see how they worked but they<00:15:41.279> had<00:15:41.519> 176<00:15:42.420> participants<00:15:43.079> on<00:15:43.500> in<00:15:43.800> that<00:15:43.980> so 00:15:44.449 --> 00:15:44.459 align:start position:0% they had 176 participants on in that so 00:15:44.459 --> 00:15:47.329 align:start position:0% they had 176 participants on in that so that's<00:15:44.880> all<00:15:45.120> your<00:15:45.360> your<00:15:45.720> ZK<00:15:46.199> sync<00:15:46.680> your<00:15:46.980> ZK 00:15:47.329 --> 00:15:47.339 align:start position:0% that's all your your ZK sync your ZK 00:15:47.339 --> 00:15:49.850 align:start position:0% that's all your your ZK sync your ZK space<00:15:47.699> as<00:15:48.120> to<00:15:48.360> connect<00:15:48.480> Aztec<00:15:49.199> Tom<00:15:49.380> all<00:15:49.680> the 00:15:49.850 --> 00:15:49.860 align:start position:0% space as to connect Aztec Tom all the 00:15:49.860 --> 00:15:51.530 align:start position:0% space as to connect Aztec Tom all the way down<00:15:50.040> the<00:15:50.160> line<00:15:50.699> but<00:15:51.060> then<00:15:51.180> you<00:15:51.300> have<00:15:51.420> your 00:15:51.530 --> 00:15:51.540 align:start position:0% way down the line but then you have your 00:15:51.540 --> 00:15:52.550 align:start position:0% way down the line but then you have your Starks 00:15:52.550 --> 00:15:52.560 align:start position:0% Starks 00:15:52.560 --> 00:15:54.590 align:start position:0% Starks um<00:15:52.620> which<00:15:53.160> do<00:15:53.519> not<00:15:53.699> have 00:15:54.590 --> 00:15:54.600 align:start position:0% um which do not have 00:15:54.600 --> 00:15:57.110 align:start position:0% um which do not have um any<00:15:54.899> trusted<00:15:55.320> setups 00:15:57.110 --> 00:15:57.120 align:start position:0% um any trusted setups 00:15:57.120 --> 00:15:58.730 align:start position:0% um any trusted setups um<00:15:57.180> we'll<00:15:57.480> start<00:15:57.660> by<00:15:57.779> recursion<00:15:58.260> this<00:15:58.560> is<00:15:58.620> the 00:15:58.730 --> 00:15:58.740 align:start position:0% um we'll start by recursion this is the 00:15:58.740 --> 00:16:00.110 align:start position:0% um we'll start by recursion this is the other<00:15:58.860> major<00:15:59.100> thing<00:15:59.399> that<00:15:59.760> um<00:15:59.760> people<00:15:59.940> are 00:16:00.110 --> 00:16:00.120 align:start position:0% other major thing that um people are 00:16:00.120 --> 00:16:03.230 align:start position:0% other major thing that um people are looking<00:16:00.360> for<00:16:00.540> for<00:16:00.959> performance<00:16:01.500> so<00:16:01.980> as<00:16:02.940> you<00:16:03.060> go 00:16:03.230 --> 00:16:03.240 align:start position:0% looking for for performance so as you go 00:16:03.240 --> 00:16:05.030 align:start position:0% looking for for performance so as you go through<00:16:03.420> performance<00:16:03.839> a<00:16:04.199> recursion<00:16:04.620> is<00:16:04.800> the 00:16:05.030 --> 00:16:05.040 align:start position:0% through performance a recursion is the 00:16:05.040 --> 00:16:06.530 align:start position:0% through performance a recursion is the ability<00:16:05.220> to<00:16:05.459> take<00:16:05.699> you<00:16:06.120> know<00:16:06.240> a<00:16:06.360> big 00:16:06.530 --> 00:16:06.540 align:start position:0% ability to take you know a big 00:16:06.540 --> 00:16:08.329 align:start position:0% ability to take you know a big computation<00:16:06.959> and<00:16:07.320> break<00:16:07.620> it<00:16:07.800> up<00:16:07.920> into<00:16:08.040> a<00:16:08.220> bunch 00:16:08.329 --> 00:16:08.339 align:start position:0% computation and break it up into a bunch 00:16:08.339 --> 00:16:10.189 align:start position:0% computation and break it up into a bunch of<00:16:08.459> little<00:16:08.519> ones<00:16:08.760> into<00:16:09.000> them<00:16:09.540> um<00:16:09.600> together<00:16:09.899> and 00:16:10.189 --> 00:16:10.199 align:start position:0% of little ones into them um together and 00:16:10.199 --> 00:16:12.170 align:start position:0% of little ones into them um together and then<00:16:10.440> recursively<00:16:10.980> proof<00:16:11.399> back<00:16:11.639> to<00:16:11.820> the<00:16:11.880> firm 00:16:12.170 --> 00:16:12.180 align:start position:0% then recursively proof back to the firm 00:16:12.180 --> 00:16:13.970 align:start position:0% then recursively proof back to the firm back<00:16:12.420> to<00:16:12.540> the<00:16:12.660> top<00:16:12.779> so 00:16:13.970 --> 00:16:13.980 align:start position:0% back to the top so 00:16:13.980 --> 00:16:15.910 align:start position:0% back to the top so um<00:16:14.519> what<00:16:15.060> this<00:16:15.120> allows<00:16:15.420> you<00:16:15.420> to<00:16:15.540> do<00:16:15.660> is 00:16:15.910 --> 00:16:15.920 align:start position:0% um what this allows you to do is 00:16:15.920 --> 00:16:18.350 align:start position:0% um what this allows you to do is parallelization<00:16:16.920> of<00:16:17.220> proof<00:16:17.519> generation<00:16:17.880> so 00:16:18.350 --> 00:16:18.360 align:start position:0% parallelization of proof generation so 00:16:18.360 --> 00:16:20.269 align:start position:0% parallelization of proof generation so you<00:16:18.839> can<00:16:18.899> decentralize<00:16:19.440> and<00:16:19.680> have<00:16:19.860> a<00:16:19.980> bunch<00:16:20.160> of 00:16:20.269 --> 00:16:20.279 align:start position:0% you can decentralize and have a bunch of 00:16:20.279 --> 00:16:22.850 align:start position:0% you can decentralize and have a bunch of provers<00:16:20.760> doing<00:16:20.940> this<00:16:21.180> in<00:16:21.420> parallel<00:16:22.199> um 00:16:22.850 --> 00:16:22.860 align:start position:0% provers doing this in parallel um 00:16:22.860 --> 00:16:24.650 align:start position:0% provers doing this in parallel um so<00:16:23.279> get<00:16:23.459> out<00:16:23.579> your<00:16:23.699> Asics<00:16:24.060> because<00:16:24.240> you<00:16:24.480> just 00:16:24.650 --> 00:16:24.660 align:start position:0% so get out your Asics because you just 00:16:24.660 --> 00:16:26.990 align:start position:0% so get out your Asics because you just got<00:16:24.839> rid<00:16:24.959> of<00:16:25.079> them<00:16:25.199> for<00:16:25.380> the<00:16:25.680> merge<00:16:26.040> but<00:16:26.339> uh<00:16:26.880> and 00:16:26.990 --> 00:16:27.000 align:start position:0% got rid of them for the merge but uh and 00:16:27.000 --> 00:16:28.790 align:start position:0% got rid of them for the merge but uh and then<00:16:27.180> it<00:16:27.300> also<00:16:27.480> lets<00:16:27.720> you<00:16:27.720> do<00:16:27.899> proof<00:16:28.139> chaining 00:16:28.790 --> 00:16:28.800 align:start position:0% then it also lets you do proof chaining 00:16:28.800 --> 00:16:30.650 align:start position:0% then it also lets you do proof chaining um<00:16:28.860> so<00:16:29.160> you<00:16:29.639> can<00:16:29.699> have<00:16:29.820> the<00:16:30.000> output<00:16:30.300> of<00:16:30.480> one 00:16:30.650 --> 00:16:30.660 align:start position:0% um so you can have the output of one 00:16:30.660 --> 00:16:34.129 align:start position:0% um so you can have the output of one proof<00:16:31.019> be<00:16:31.260> the<00:16:31.380> input<00:16:31.680> for<00:16:31.800> the<00:16:31.920> next<00:16:32.040> proof 00:16:34.129 --> 00:16:34.139 align:start position:0% proof be the input for the next proof 00:16:34.139 --> 00:16:36.290 align:start position:0% proof be the input for the next proof um so<00:16:34.560> what<00:16:34.860> provides<00:16:35.279> recursion<00:16:35.760> pretty 00:16:36.290 --> 00:16:36.300 align:start position:0% um so what provides recursion pretty 00:16:36.300 --> 00:16:38.090 align:start position:0% um so what provides recursion pretty much<00:16:36.420> everything<00:16:36.660> but<00:16:36.959> graph<00:16:37.199> 16<00:16:37.500> is<00:16:37.920> now 00:16:38.090 --> 00:16:38.100 align:start position:0% much everything but graph 16 is now 00:16:38.100 --> 00:16:39.769 align:start position:0% much everything but graph 16 is now doing<00:16:38.399> recursion<00:16:38.940> and<00:16:39.120> they're<00:16:39.300> doing<00:16:39.420> it<00:16:39.600> in 00:16:39.769 --> 00:16:39.779 align:start position:0% doing recursion and they're doing it in 00:16:39.779 --> 00:16:41.509 align:start position:0% doing recursion and they're doing it in better<00:16:40.079> ways<00:16:40.500> I<00:16:40.680> guess<00:16:40.800> as<00:16:40.980> you<00:16:41.160> move<00:16:41.339> forward 00:16:41.509 --> 00:16:41.519 align:start position:0% better ways I guess as you move forward 00:16:41.519 --> 00:16:42.769 align:start position:0% better ways I guess as you move forward so 00:16:42.769 --> 00:16:42.779 align:start position:0% so 00:16:42.779 --> 00:16:44.569 align:start position:0% so um that<00:16:43.199> was<00:16:43.320> the<00:16:43.680> other<00:16:43.800> the<00:16:44.040> why<00:16:44.399> would 00:16:44.569 --> 00:16:44.579 align:start position:0% um that was the other the why would 00:16:44.579 --> 00:16:46.490 align:start position:0% um that was the other the why would anyone<00:16:44.759> use<00:16:44.940> graph<00:16:45.240> 16<00:16:45.480> if<00:16:46.019> you<00:16:46.259> can't<00:16:46.380> do 00:16:46.490 --> 00:16:46.500 align:start position:0% anyone use graph 16 if you can't do 00:16:46.500 --> 00:16:47.990 align:start position:0% anyone use graph 16 if you can't do recursion<00:16:46.980> and<00:16:47.160> you<00:16:47.279> have<00:16:47.399> a<00:16:47.459> big<00:16:47.579> trusted 00:16:47.990 --> 00:16:48.000 align:start position:0% recursion and you have a big trusted 00:16:48.000 --> 00:16:49.850 align:start position:0% recursion and you have a big trusted setup<00:16:48.300> you<00:16:48.720> it's<00:16:48.899> faster 00:16:49.850 --> 00:16:49.860 align:start position:0% setup you it's faster 00:16:49.860 --> 00:16:51.829 align:start position:0% setup you it's faster um<00:16:49.920> and<00:16:50.040> there's<00:16:50.279> it's<00:16:50.579> cheaper<00:16:50.940> to<00:16:51.060> verify<00:16:51.480> so 00:16:51.829 --> 00:16:51.839 align:start position:0% um and there's it's cheaper to verify so 00:16:51.839 --> 00:16:53.870 align:start position:0% um and there's it's cheaper to verify so it's<00:16:52.320> the<00:16:52.500> OG<00:16:52.800> it's<00:16:53.160> been<00:16:53.339> there<00:16:53.459> for<00:16:53.639> a<00:16:53.759> long 00:16:53.870 --> 00:16:53.880 align:start position:0% it's the OG it's been there for a long 00:16:53.880 --> 00:16:55.850 align:start position:0% it's the OG it's been there for a long time<00:16:54.480> um<00:16:54.540> but<00:16:54.720> people<00:16:54.899> are<00:16:55.079> moving<00:16:55.440> on<00:16:55.560> because 00:16:55.850 --> 00:16:55.860 align:start position:0% time um but people are moving on because 00:16:55.860 --> 00:16:58.249 align:start position:0% time um but people are moving on because of<00:16:56.100> those<00:16:56.220> two<00:16:56.399> problems<00:16:56.820> mostly 00:16:58.249 --> 00:16:58.259 align:start position:0% of those two problems mostly 00:16:58.259 --> 00:17:02.269 align:start position:0% of those two problems mostly so<00:16:58.980> now<00:16:59.940> I<00:17:00.420> guess<00:17:00.600> we<00:17:00.839> can<00:17:00.959> talk<00:17:01.139> about<00:17:01.320> my 00:17:02.269 --> 00:17:02.279 align:start position:0% so now I guess we can talk about my 00:17:02.279 --> 00:17:03.949 align:start position:0% so now I guess we can talk about my favorite<00:17:02.579> topic<00:17:03.180> which<00:17:03.480> is<00:17:03.600> data 00:17:03.949 --> 00:17:03.959 align:start position:0% favorite topic which is data 00:17:03.959 --> 00:17:06.169 align:start position:0% favorite topic which is data availability<00:17:04.260> as<00:17:04.620> a<00:17:04.799> data<00:17:05.040> scientist 00:17:06.169 --> 00:17:06.179 align:start position:0% availability as a data scientist 00:17:06.179 --> 00:17:09.590 align:start position:0% availability as a data scientist um so<00:17:06.780> uh<00:17:07.740> we'll<00:17:08.220> talk<00:17:08.400> this<00:17:09.000> is<00:17:09.120> going<00:17:09.419> to<00:17:09.540> be 00:17:09.590 --> 00:17:09.600 align:start position:0% um so uh we'll talk this is going to be 00:17:09.600 --> 00:17:13.309 align:start position:0% um so uh we'll talk this is going to be about<00:17:09.780> l1s<00:17:10.380> and<00:17:10.439> l2s<00:17:10.919> so<00:17:11.280> for<00:17:12.480> um<00:17:12.600> for<00:17:13.260> the 00:17:13.309 --> 00:17:13.319 align:start position:0% about l1s and l2s so for um for the 00:17:13.319 --> 00:17:15.049 align:start position:0% about l1s and l2s so for um for the purists<00:17:13.799> out<00:17:13.860> there<00:17:13.980> l2s<00:17:14.640> would<00:17:14.819> only<00:17:14.939> be 00:17:15.049 --> 00:17:15.059 align:start position:0% purists out there l2s would only be 00:17:15.059 --> 00:17:17.090 align:start position:0% purists out there l2s would only be Roll-Ups<00:17:15.540> but<00:17:15.720> I'll<00:17:16.020> use<00:17:16.260> both<00:17:16.500> back<00:17:16.919> and 00:17:17.090 --> 00:17:17.100 align:start position:0% Roll-Ups but I'll use both back and 00:17:17.100 --> 00:17:19.970 align:start position:0% Roll-Ups but I'll use both back and forth<00:17:17.339> so<00:17:17.640> Zeke<00:17:18.240> validiums<00:17:18.900> validiums<00:17:19.980> um 00:17:19.970 --> 00:17:19.980 align:start position:0% forth so Zeke validiums validiums um 00:17:19.980 --> 00:17:22.010 align:start position:0% forth so Zeke validiums validiums um they<00:17:20.280> have<00:17:20.400> their<00:17:20.640> state<00:17:20.819> route<00:17:21.059> is<00:17:21.780> on<00:17:21.900> the 00:17:22.010 --> 00:17:22.020 align:start position:0% they have their state route is on the 00:17:22.020 --> 00:17:23.870 align:start position:0% they have their state route is on the bridge<00:17:22.140> contract<00:17:23.160> um<00:17:23.280> and<00:17:23.459> then<00:17:23.640> they<00:17:23.760> have 00:17:23.870 --> 00:17:23.880 align:start position:0% bridge contract um and then they have 00:17:23.880 --> 00:17:25.309 align:start position:0% bridge contract um and then they have their<00:17:24.000> state<00:17:24.120> reconstruction<00:17:24.660> that's<00:17:25.079> off 00:17:25.309 --> 00:17:25.319 align:start position:0% their state reconstruction that's off 00:17:25.319 --> 00:17:27.230 align:start position:0% their state reconstruction that's off chain<00:17:25.559> it<00:17:26.220> goes<00:17:26.520> through<00:17:26.699> a<00:17:26.880> data 00:17:27.230 --> 00:17:27.240 align:start position:0% chain it goes through a data 00:17:27.240 --> 00:17:29.570 align:start position:0% chain it goes through a data availability<00:17:27.540> committee<00:17:28.199> to<00:17:28.500> go<00:17:28.620> on<00:17:28.860> chain<00:17:29.160> to 00:17:29.570 --> 00:17:29.580 align:start position:0% availability committee to go on chain to 00:17:29.580 --> 00:17:31.130 align:start position:0% availability committee to go on chain to be<00:17:29.640> able<00:17:29.760> to<00:17:29.880> make<00:17:30.000> it<00:17:30.120> so<00:17:30.240> you<00:17:30.419> have<00:17:30.600> that<00:17:30.780> data 00:17:31.130 --> 00:17:31.140 align:start position:0% be able to make it so you have that data 00:17:31.140 --> 00:17:32.990 align:start position:0% be able to make it so you have that data but<00:17:31.559> it<00:17:31.740> is<00:17:31.860> permissioned<00:17:32.340> on<00:17:32.580> that<00:17:32.700> side<00:17:32.880> of 00:17:32.990 --> 00:17:33.000 align:start position:0% but it is permissioned on that side of 00:17:33.000 --> 00:17:35.630 align:start position:0% but it is permissioned on that side of things<00:17:33.380> then<00:17:34.380> the<00:17:34.679> alternative 00:17:35.630 --> 00:17:35.640 align:start position:0% things then the alternative 00:17:35.640 --> 00:17:38.029 align:start position:0% things then the alternative which<00:17:36.240> is<00:17:36.360> in<00:17:36.660> supposed<00:17:37.260> to<00:17:37.380> be<00:17:37.500> gold<00:17:37.620> it<00:17:37.860> kind 00:17:38.029 --> 00:17:38.039 align:start position:0% which is in supposed to be gold it kind 00:17:38.039 --> 00:17:39.770 align:start position:0% which is in supposed to be gold it kind of<00:17:38.100> looks<00:17:38.220> like<00:17:38.280> bronze<00:17:38.760> so<00:17:38.820> forget<00:17:39.059> that<00:17:39.780> um 00:17:39.770 --> 00:17:39.780 align:start position:0% of looks like bronze so forget that um 00:17:39.780 --> 00:17:41.810 align:start position:0% of looks like bronze so forget that um is<00:17:40.559> you<00:17:40.799> have<00:17:40.919> your<00:17:41.100> state<00:17:41.280> reconstruction 00:17:41.810 --> 00:17:41.820 align:start position:0% is you have your state reconstruction 00:17:41.820 --> 00:17:43.610 align:start position:0% is you have your state reconstruction and<00:17:42.539> your<00:17:42.660> state<00:17:42.840> route 00:17:43.610 --> 00:17:43.620 align:start position:0% and your state route 00:17:43.620 --> 00:17:45.350 align:start position:0% and your state route um for<00:17:43.860> the<00:17:43.980> ZK<00:17:44.220> Roll-Ups 00:17:45.350 --> 00:17:45.360 align:start position:0% um for the ZK Roll-Ups 00:17:45.360 --> 00:17:47.330 align:start position:0% um for the ZK Roll-Ups um<00:17:45.419> down<00:17:45.660> on<00:17:45.900> the<00:17:45.960> bridge<00:17:46.080> roll<00:17:46.320> up<00:17:46.559> or<00:17:46.860> down<00:17:47.160> on 00:17:47.330 --> 00:17:47.340 align:start position:0% um down on the bridge roll up or down on 00:17:47.340 --> 00:17:49.370 align:start position:0% um down on the bridge roll up or down on the<00:17:47.460> bridge<00:17:47.520> contract<00:17:47.940> so<00:17:48.419> that<00:17:48.960> allows<00:17:49.260> you 00:17:49.370 --> 00:17:49.380 align:start position:0% the bridge contract so that allows you 00:17:49.380 --> 00:17:50.270 align:start position:0% the bridge contract so that allows you to 00:17:50.270 --> 00:17:50.280 align:start position:0% to 00:17:50.280 --> 00:17:52.310 align:start position:0% to um always<00:17:50.580> have<00:17:51.000> that<00:17:51.480> data<00:17:51.840> to<00:17:52.020> be<00:17:52.080> able<00:17:52.200> to 00:17:52.310 --> 00:17:52.320 align:start position:0% um always have that data to be able to 00:17:52.320 --> 00:17:54.049 align:start position:0% um always have that data to be able to generate<00:17:52.620> a<00:17:52.740> proof<00:17:53.280> um<00:17:53.280> in<00:17:53.460> case<00:17:53.700> you<00:17:53.820> need<00:17:53.940> to 00:17:54.049 --> 00:17:54.059 align:start position:0% generate a proof um in case you need to 00:17:54.059 --> 00:17:56.090 align:start position:0% generate a proof um in case you need to escape<00:17:54.179> so 00:17:56.090 --> 00:17:56.100 align:start position:0% escape so 00:17:56.100 --> 00:17:58.430 align:start position:0% escape so um why<00:17:57.059> would<00:17:57.240> you<00:17:57.360> do<00:17:57.480> oblidium<00:17:58.020> over<00:17:58.200> a 00:17:58.430 --> 00:17:58.440 align:start position:0% um why would you do oblidium over a 00:17:58.440 --> 00:18:00.950 align:start position:0% um why would you do oblidium over a roll-up<00:17:58.740> it's<00:17:59.220> many<00:18:00.000> more<00:18:00.240> transactions<00:18:00.840> per 00:18:00.950 --> 00:18:00.960 align:start position:0% roll-up it's many more transactions per 00:18:00.960 --> 00:18:03.169 align:start position:0% roll-up it's many more transactions per second<00:18:01.140> so<00:18:01.679> your<00:18:01.980> imxs<00:18:02.700> and<00:18:02.880> your<00:18:03.000> different 00:18:03.169 --> 00:18:03.179 align:start position:0% second so your imxs and your different 00:18:03.179 --> 00:18:05.570 align:start position:0% second so your imxs and your different Stark<00:18:03.419> X<00:18:03.660> projects<00:18:04.140> are<00:18:04.919> able<00:18:05.160> to<00:18:05.220> be<00:18:05.340> a<00:18:05.460> lot 00:18:05.570 --> 00:18:05.580 align:start position:0% Stark X projects are able to be a lot 00:18:05.580 --> 00:18:09.350 align:start position:0% Stark X projects are able to be a lot cheaper<00:18:06.360> um<00:18:06.360> so<00:18:06.840> moving<00:18:07.620> forward 00:18:09.350 --> 00:18:09.360 align:start position:0% cheaper um so moving forward 00:18:09.360 --> 00:18:11.390 align:start position:0% cheaper um so moving forward um<00:18:09.480> let's<00:18:09.720> look<00:18:10.020> at<00:18:10.320> your<00:18:10.559> validiums<00:18:11.160> that<00:18:11.280> are 00:18:11.390 --> 00:18:11.400 align:start position:0% um let's look at your validiums that are 00:18:11.400 --> 00:18:13.190 align:start position:0% um let's look at your validiums that are currently<00:18:11.700> operating<00:18:12.120> you<00:18:12.539> have<00:18:12.600> Stark<00:18:12.900> X 00:18:13.190 --> 00:18:13.200 align:start position:0% currently operating you have Stark X 00:18:13.200 --> 00:18:15.590 align:start position:0% currently operating you have Stark X which<00:18:13.500> is<00:18:13.620> on<00:18:13.980> immutable<00:18:14.520> X 00:18:15.590 --> 00:18:15.600 align:start position:0% which is on immutable X 00:18:15.600 --> 00:18:18.590 align:start position:0% which is on immutable X um you<00:18:15.840> have<00:18:15.960> rindify<00:18:16.620> so<00:18:17.460> rare<00:18:17.640> Apex<00:18:18.600> um 00:18:18.590 --> 00:18:18.600 align:start position:0% um you have rindify so rare Apex um 00:18:18.600 --> 00:18:20.990 align:start position:0% um you have rindify so rare Apex um other<00:18:18.780> ones<00:18:18.960> that<00:18:19.200> are<00:18:19.320> coming<00:18:19.440> out<00:18:19.620> you<00:18:20.460> have 00:18:20.990 --> 00:18:21.000 align:start position:0% other ones that are coming out you have 00:18:21.000 --> 00:18:22.669 align:start position:0% other ones that are coming out you have um ziki<00:18:21.419> Porter<00:18:21.660> almost<00:18:21.900> coming<00:18:22.200> out<00:18:22.320> from<00:18:22.380> ZK 00:18:22.669 --> 00:18:22.679 align:start position:0% um ziki Porter almost coming out from ZK 00:18:22.679 --> 00:18:23.630 align:start position:0% um ziki Porter almost coming out from ZK sync 00:18:23.630 --> 00:18:23.640 align:start position:0% sync 00:18:23.640 --> 00:18:25.669 align:start position:0% sync um and<00:18:24.299> then<00:18:24.600> your<00:18:24.840> roll<00:18:25.020> ups<00:18:25.380> I'll<00:18:25.500> run 00:18:25.669 --> 00:18:25.679 align:start position:0% um and then your roll ups I'll run 00:18:25.679 --> 00:18:26.630 align:start position:0% um and then your roll ups I'll run through<00:18:25.799> these<00:18:26.039> because<00:18:26.160> you<00:18:26.340> guys<00:18:26.460> probably 00:18:26.630 --> 00:18:26.640 align:start position:0% through these because you guys probably 00:18:26.640 --> 00:18:28.010 align:start position:0% through these because you guys probably all<00:18:26.760> know<00:18:26.940> them<00:18:27.120> but 00:18:28.010 --> 00:18:28.020 align:start position:0% all know them but 00:18:28.020 --> 00:18:29.810 align:start position:0% all know them but um<00:18:28.080> you<00:18:28.320> have<00:18:28.500> to<00:18:28.559> idx 00:18:29.810 --> 00:18:29.820 align:start position:0% um you have to idx 00:18:29.820 --> 00:18:31.310 align:start position:0% um you have to idx Loop<00:18:30.360> ring 00:18:31.310 --> 00:18:31.320 align:start position:0% Loop ring 00:18:31.320 --> 00:18:35.390 align:start position:0% Loop ring ZK<00:18:31.860> sync<00:18:32.220> V1<00:18:32.720> usdk<00:18:33.720> space 00:18:35.390 --> 00:18:35.400 align:start position:0% ZK sync V1 usdk space 00:18:35.400 --> 00:18:37.310 align:start position:0% ZK sync V1 usdk space um<00:18:35.520> starknet 00:18:37.310 --> 00:18:37.320 align:start position:0% um starknet 00:18:37.320 --> 00:18:38.510 align:start position:0% um starknet so 00:18:38.510 --> 00:18:38.520 align:start position:0% so 00:18:38.520 --> 00:18:40.610 align:start position:0% so I'll<00:18:38.820> pause<00:18:39.000> for<00:18:39.179> the<00:18:39.360> camera 00:18:40.610 --> 00:18:40.620 align:start position:0% I'll pause for the camera 00:18:40.620 --> 00:18:42.590 align:start position:0% I'll pause for the camera then<00:18:41.280> moving<00:18:41.700> on<00:18:41.820> there's<00:18:42.179> a<00:18:42.299> couple<00:18:42.419> more 00:18:42.590 --> 00:18:42.600 align:start position:0% then moving on there's a couple more 00:18:42.600 --> 00:18:44.390 align:start position:0% then moving on there's a couple more that<00:18:42.840> are<00:18:43.320> um<00:18:43.380> the<00:18:43.679> newer<00:18:43.919> ones<00:18:44.160> that<00:18:44.280> are 00:18:44.390 --> 00:18:44.400 align:start position:0% that are um the newer ones that are 00:18:44.400 --> 00:18:46.850 align:start position:0% that are um the newer ones that are coming<00:18:44.520> up<00:18:44.700> for<00:18:45.179> Roll-Ups<00:18:45.660> that<00:18:46.020> are<00:18:46.200> exciting 00:18:46.850 --> 00:18:46.860 align:start position:0% coming up for Roll-Ups that are exciting 00:18:46.860 --> 00:18:48.890 align:start position:0% coming up for Roll-Ups that are exciting um<00:18:46.919> you<00:18:47.220> have<00:18:47.400> ZK<00:18:47.640> sync<00:18:48.000> V2 00:18:48.890 --> 00:18:48.900 align:start position:0% um you have ZK sync V2 00:18:48.900 --> 00:18:50.870 align:start position:0% um you have ZK sync V2 um<00:18:49.020> which<00:18:49.320> I<00:18:49.740> think<00:18:49.860> is<00:18:49.980> under<00:18:50.160> 30<00:18:50.400> days<00:18:50.640> now 00:18:50.870 --> 00:18:50.880 align:start position:0% um which I think is under 30 days now 00:18:50.880 --> 00:18:53.150 align:start position:0% um which I think is under 30 days now which<00:18:51.120> is<00:18:51.240> exciting<00:18:51.539> to<00:18:51.720> mainnet 00:18:53.150 --> 00:18:53.160 align:start position:0% which is exciting to mainnet 00:18:53.160 --> 00:18:54.950 align:start position:0% which is exciting to mainnet um<00:18:53.220> you<00:18:53.580> have<00:18:53.880> scroll 00:18:54.950 --> 00:18:54.960 align:start position:0% um you have scroll 00:18:54.960 --> 00:18:57.590 align:start position:0% um you have scroll um<00:18:55.020> which<00:18:55.320> is<00:18:55.500> going<00:18:55.919> for<00:18:56.280> a<00:18:56.700> higher<00:18:57.240> level<00:18:57.360> of 00:18:57.590 --> 00:18:57.600 align:start position:0% um which is going for a higher level of 00:18:57.600 --> 00:18:59.029 align:start position:0% um which is going for a higher level of evm<00:18:58.020> compatibility 00:18:59.029 --> 00:18:59.039 align:start position:0% evm compatibility 00:18:59.039 --> 00:19:02.810 align:start position:0% evm compatibility um<00:18:59.100> and<00:18:59.760> then<00:19:00.000> uh<00:19:00.660> let's<00:19:01.260> see<00:19:01.500> what's<00:19:01.799> next 00:19:02.810 --> 00:19:02.820 align:start position:0% um and then uh let's see what's next 00:19:02.820 --> 00:19:05.150 align:start position:0% um and then uh let's see what's next then<00:19:03.179> you<00:19:03.360> have<00:19:03.480> all<00:19:03.720> of<00:19:03.840> polygons<00:19:04.260> projects 00:19:05.150 --> 00:19:05.160 align:start position:0% then you have all of polygons projects 00:19:05.160 --> 00:19:06.350 align:start position:0% then you have all of polygons projects um which<00:19:05.520> are<00:19:05.640> all<00:19:05.760> exciting<00:19:06.059> in<00:19:06.179> their<00:19:06.299> own 00:19:06.350 --> 00:19:06.360 align:start position:0% um which are all exciting in their own 00:19:06.360 --> 00:19:08.029 align:start position:0% um which are all exciting in their own right<00:19:06.539> so 00:19:08.029 --> 00:19:08.039 align:start position:0% right so 00:19:08.039 --> 00:19:09.529 align:start position:0% right so um let's<00:19:08.460> talk<00:19:08.580> about<00:19:08.760> what<00:19:09.059> it<00:19:09.120> means<00:19:09.299> to<00:19:09.419> be 00:19:09.529 --> 00:19:09.539 align:start position:0% um let's talk about what it means to be 00:19:09.539 --> 00:19:12.470 align:start position:0% um let's talk about what it means to be a<00:19:09.660> roll-up<00:19:09.960> so<00:19:10.380> everyone<00:19:11.100> talks<00:19:12.000> constantly 00:19:12.470 --> 00:19:12.480 align:start position:0% a roll-up so everyone talks constantly 00:19:12.480 --> 00:19:14.990 align:start position:0% a roll-up so everyone talks constantly about<00:19:12.780> how<00:19:13.260> the<00:19:13.679> full<00:19:13.860> security<00:19:14.160> of<00:19:14.520> ethereum 00:19:14.990 --> 00:19:15.000 align:start position:0% about how the full security of ethereum 00:19:15.000 --> 00:19:19.010 align:start position:0% about how the full security of ethereum is<00:19:15.660> being<00:19:15.840> inherited<00:19:16.320> by<00:19:16.500> these<00:19:16.620> Roll-Ups<00:19:17.160> so 00:19:19.010 --> 00:19:19.020 align:start position:0% is being inherited by these Roll-Ups so 00:19:19.020 --> 00:19:20.450 align:start position:0% is being inherited by these Roll-Ups so what<00:19:19.500> does<00:19:19.620> it<00:19:19.740> mean<00:19:19.860> to<00:19:20.039> have<00:19:20.160> the<00:19:20.340> full 00:19:20.450 --> 00:19:20.460 align:start position:0% what does it mean to have the full 00:19:20.460 --> 00:19:23.330 align:start position:0% what does it mean to have the full security<00:19:20.700> of<00:19:21.059> ethereum 00:19:23.330 --> 00:19:23.340 align:start position:0% security of ethereum 00:19:23.340 --> 00:19:25.010 align:start position:0% security of ethereum you<00:19:23.820> need<00:19:23.880> to<00:19:24.000> have<00:19:24.120> the<00:19:24.299> right<00:19:24.480> to<00:19:24.660> be<00:19:24.780> able<00:19:24.900> to 00:19:25.010 --> 00:19:25.020 align:start position:0% you need to have the right to be able to 00:19:25.020 --> 00:19:28.370 align:start position:0% you need to have the right to be able to force<00:19:25.320> exit<00:19:25.620> from<00:19:25.799> that<00:19:25.980> chain<00:19:26.160> so<00:19:27.059> if<00:19:28.020> you 00:19:28.370 --> 00:19:28.380 align:start position:0% force exit from that chain so if you 00:19:28.380 --> 00:19:31.669 align:start position:0% force exit from that chain so if you have<00:19:28.500> on<00:19:28.919> your<00:19:29.160> Layer<00:19:29.580> Two<00:19:29.720> if<00:19:30.720> they<00:19:30.960> have<00:19:31.679> um 00:19:31.669 --> 00:19:31.679 align:start position:0% have on your Layer Two if they have um 00:19:31.679 --> 00:19:34.310 align:start position:0% have on your Layer Two if they have um decide<00:19:32.100> to<00:19:32.220> be<00:19:32.460> against<00:19:33.240> you<00:19:33.539> you<00:19:34.020> need<00:19:34.140> to<00:19:34.260> be 00:19:34.310 --> 00:19:34.320 align:start position:0% decide to be against you you need to be 00:19:34.320 --> 00:19:35.690 align:start position:0% decide to be against you you need to be able<00:19:34.440> to<00:19:34.559> submit<00:19:34.980> your<00:19:35.100> transactions 00:19:35.690 --> 00:19:35.700 align:start position:0% able to submit your transactions 00:19:35.700 --> 00:19:37.850 align:start position:0% able to submit your transactions directly<00:19:36.240> on<00:19:36.539> layer<00:19:36.840> one<00:19:36.960> to<00:19:37.320> the<00:19:37.500> ethereum 00:19:37.850 --> 00:19:37.860 align:start position:0% directly on layer one to the ethereum 00:19:37.860 --> 00:19:39.770 align:start position:0% directly on layer one to the ethereum bridge<00:19:38.039> contract<00:19:38.460> and<00:19:38.700> get<00:19:38.880> your<00:19:39.000> funds<00:19:39.360> so 00:19:39.770 --> 00:19:39.780 align:start position:0% bridge contract and get your funds so 00:19:39.780 --> 00:19:41.870 align:start position:0% bridge contract and get your funds so right<00:19:40.140> now<00:19:40.320> you<00:19:40.620> have<00:19:40.740> your<00:19:40.919> happy<00:19:41.160> user<00:19:41.700> down 00:19:41.870 --> 00:19:41.880 align:start position:0% right now you have your happy user down 00:19:41.880 --> 00:19:42.710 align:start position:0% right now you have your happy user down here 00:19:42.710 --> 00:19:42.720 align:start position:0% here 00:19:42.720 --> 00:19:44.570 align:start position:0% here um that's<00:19:43.320> from<00:19:43.500> Walmart<00:19:43.740> it's<00:19:44.280> kind<00:19:44.460> of 00:19:44.570 --> 00:19:44.580 align:start position:0% um that's from Walmart it's kind of 00:19:44.580 --> 00:19:45.770 align:start position:0% um that's from Walmart it's kind of creepy<00:19:44.880> actually<00:19:45.000> the<00:19:45.240> more<00:19:45.360> you<00:19:45.480> look<00:19:45.600> at<00:19:45.720> it 00:19:45.770 --> 00:19:45.780 align:start position:0% creepy actually the more you look at it 00:19:45.780 --> 00:19:48.830 align:start position:0% creepy actually the more you look at it so<00:19:45.900> don't<00:19:46.080> stare<00:19:46.380> at<00:19:46.440> it<00:19:46.559> too<00:19:46.679> long<00:19:47.220> um<00:19:47.220> but<00:19:48.000> the 00:19:48.830 --> 00:19:48.840 align:start position:0% so don't stare at it too long um but the 00:19:48.840 --> 00:19:51.169 align:start position:0% so don't stare at it too long um but the transaction<00:19:49.260> goes<00:19:49.740> to<00:19:49.860> this<00:19:50.160> uh<00:19:50.520> the<00:19:51.059> happy 00:19:51.169 --> 00:19:51.179 align:start position:0% transaction goes to this uh the happy 00:19:51.179 --> 00:19:54.049 align:start position:0% transaction goes to this uh the happy sequencers<00:19:52.020> here<00:19:52.260> they<00:19:52.980> put<00:19:53.340> the<00:19:53.760> transaction 00:19:54.049 --> 00:19:54.059 align:start position:0% sequencers here they put the transaction 00:19:54.059 --> 00:19:56.330 align:start position:0% sequencers here they put the transaction into<00:19:54.360> the<00:19:54.539> layer<00:19:54.780> two<00:19:54.900> those<00:19:55.679> transactions 00:19:56.330 --> 00:19:56.340 align:start position:0% into the layer two those transactions 00:19:56.340 --> 00:19:59.690 align:start position:0% into the layer two those transactions are<00:19:56.520> batched<00:19:57.000> on<00:19:57.419> into<00:19:57.840> the<00:19:58.020> ZK<00:19:58.320> circuit<00:19:58.799> it 00:19:59.690 --> 00:19:59.700 align:start position:0% are batched on into the ZK circuit it 00:19:59.700 --> 00:20:01.190 align:start position:0% are batched on into the ZK circuit it produces<00:20:00.059> the<00:20:00.240> proof<00:20:00.480> and<00:20:00.720> it<00:20:00.900> goes<00:20:01.080> to<00:20:01.140> the 00:20:01.190 --> 00:20:01.200 align:start position:0% produces the proof and it goes to the 00:20:01.200 --> 00:20:02.990 align:start position:0% produces the proof and it goes to the ethereum<00:20:01.500> bridge<00:20:01.679> contract<00:20:02.100> as<00:20:02.280> as<00:20:02.580> we<00:20:02.760> talked 00:20:02.990 --> 00:20:03.000 align:start position:0% ethereum bridge contract as as we talked 00:20:03.000 --> 00:20:04.850 align:start position:0% ethereum bridge contract as as we talked about<00:20:03.059> before<00:20:03.360> so 00:20:04.850 --> 00:20:04.860 align:start position:0% about before so 00:20:04.860 --> 00:20:07.010 align:start position:0% about before so um this<00:20:05.100> is<00:20:05.160> how<00:20:05.280> it's<00:20:05.460> supposed<00:20:05.640> to<00:20:05.820> function 00:20:07.010 --> 00:20:07.020 align:start position:0% um this is how it's supposed to function 00:20:07.020 --> 00:20:10.850 align:start position:0% um this is how it's supposed to function so<00:20:07.740> let's<00:20:08.280> say<00:20:08.520> that<00:20:09.419> the<00:20:09.900> sequencers<00:20:10.440> become 00:20:10.850 --> 00:20:10.860 align:start position:0% so let's say that the sequencers become 00:20:10.860 --> 00:20:13.490 align:start position:0% so let's say that the sequencers become evil<00:20:11.220> and<00:20:11.460> start<00:20:11.640> smoking<00:20:12.059> cigars 00:20:13.490 --> 00:20:13.500 align:start position:0% evil and start smoking cigars 00:20:13.500 --> 00:20:15.409 align:start position:0% evil and start smoking cigars um you<00:20:13.919> get<00:20:14.100> unhappy 00:20:15.409 --> 00:20:15.419 align:start position:0% um you get unhappy 00:20:15.419 --> 00:20:17.510 align:start position:0% um you get unhappy so<00:20:15.960> your<00:20:16.320> transactions<00:20:16.860> can't<00:20:17.039> make<00:20:17.220> it<00:20:17.400> to 00:20:17.510 --> 00:20:17.520 align:start position:0% so your transactions can't make it to 00:20:17.520 --> 00:20:20.169 align:start position:0% so your transactions can't make it to Layer<00:20:17.760> Two<00:20:17.880> and<00:20:18.120> your<00:20:18.240> funds<00:20:18.539> are<00:20:18.600> frozen<00:20:18.840> so 00:20:20.169 --> 00:20:20.179 align:start position:0% Layer Two and your funds are frozen so 00:20:20.179 --> 00:20:22.669 align:start position:0% Layer Two and your funds are frozen so what<00:20:21.179> do<00:20:21.299> you<00:20:21.480> do 00:20:22.669 --> 00:20:22.679 align:start position:0% what do you do 00:20:22.679 --> 00:20:24.110 align:start position:0% what do you do you take<00:20:23.280> your 00:20:24.110 --> 00:20:24.120 align:start position:0% you take your 00:20:24.120 --> 00:20:26.210 align:start position:0% you take your transaction<00:20:24.720> and<00:20:25.080> you<00:20:25.200> go<00:20:25.320> directly<00:20:25.740> onto 00:20:26.210 --> 00:20:26.220 align:start position:0% transaction and you go directly onto 00:20:26.220 --> 00:20:28.669 align:start position:0% transaction and you go directly onto layer<00:20:26.520> one<00:20:26.640> to<00:20:26.880> the<00:20:27.000> bridge<00:20:27.120> contract<00:20:27.600> so<00:20:28.260> when 00:20:28.669 --> 00:20:28.679 align:start position:0% layer one to the bridge contract so when 00:20:28.679 --> 00:20:30.529 align:start position:0% layer one to the bridge contract so when you<00:20:28.799> take<00:20:28.919> your<00:20:29.100> layer<00:20:29.400> to<00:20:29.640> transaction<00:20:30.179> go 00:20:30.529 --> 00:20:30.539 align:start position:0% you take your layer to transaction go 00:20:30.539 --> 00:20:33.409 align:start position:0% you take your layer to transaction go directly<00:20:30.840> to<00:20:31.020> it<00:20:31.200> then<00:20:31.679> the<00:20:32.220> validators<00:20:32.760> have 00:20:33.409 --> 00:20:33.419 align:start position:0% directly to it then the validators have 00:20:33.419 --> 00:20:35.210 align:start position:0% directly to it then the validators have a<00:20:33.720> certain<00:20:33.840> amount<00:20:34.080> of<00:20:34.260> time<00:20:34.500> to<00:20:34.980> actually 00:20:35.210 --> 00:20:35.220 align:start position:0% a certain amount of time to actually 00:20:35.220 --> 00:20:38.270 align:start position:0% a certain amount of time to actually include<00:20:35.820> your<00:20:36.539> transaction<00:20:37.320> on<00:20:37.860> into<00:20:38.100> the 00:20:38.270 --> 00:20:38.280 align:start position:0% include your transaction on into the 00:20:38.280 --> 00:20:41.090 align:start position:0% include your transaction on into the layer<00:20:38.760> twos<00:20:39.059> so<00:20:39.419> usually<00:20:40.080> it's<00:20:40.260> between<00:20:40.559> 7<00:20:40.860> and 00:20:41.090 --> 00:20:41.100 align:start position:0% layer twos so usually it's between 7 and 00:20:41.100 --> 00:20:44.750 align:start position:0% layer twos so usually it's between 7 and 14<00:20:41.280> days<00:20:41.660> so<00:20:42.919> if<00:20:43.919> they<00:20:44.039> don't<00:20:44.220> do<00:20:44.400> it<00:20:44.460> within 00:20:44.750 --> 00:20:44.760 align:start position:0% 14 days so if they don't do it within 00:20:44.760 --> 00:20:47.150 align:start position:0% 14 days so if they don't do it within that<00:20:44.880> amount<00:20:45.120> of<00:20:45.240> time<00:20:45.419> then<00:20:46.140> Hell<00:20:46.679> Freezes 00:20:47.150 --> 00:20:47.160 align:start position:0% that amount of time then Hell Freezes 00:20:47.160 --> 00:20:51.350 align:start position:0% that amount of time then Hell Freezes Over<00:20:47.340> and<00:20:48.539> um<00:20:48.539> the<00:20:48.960> chain<00:20:49.260> freezes<00:20:49.799> so<00:20:50.400> your 00:20:51.350 --> 00:20:51.360 align:start position:0% Over and um the chain freezes so your 00:20:51.360 --> 00:20:54.049 align:start position:0% Over and um the chain freezes so your layer<00:20:51.780> 2<00:20:51.900> cannot<00:20:52.500> update<00:20:52.860> State<00:20:53.160> on<00:20:53.700> layer<00:20:53.940> one 00:20:54.049 --> 00:20:54.059 align:start position:0% layer 2 cannot update State on layer one 00:20:54.059 --> 00:20:57.409 align:start position:0% layer 2 cannot update State on layer one and<00:20:54.840> the<00:20:55.440> serial<00:20:55.919> knowledge<00:20:56.160> circuit<00:20:56.820> um<00:20:56.880> then 00:20:57.409 --> 00:20:57.419 align:start position:0% and the serial knowledge circuit um then 00:20:57.419 --> 00:21:00.230 align:start position:0% and the serial knowledge circuit um then you<00:20:57.720> as<00:20:58.080> a<00:20:58.320> user<00:20:58.620> can<00:20:58.980> produce<00:20:59.340> a<00:20:59.520> proof<00:20:59.820> from 00:21:00.230 --> 00:21:00.240 align:start position:0% you as a user can produce a proof from 00:21:00.240 --> 00:21:03.590 align:start position:0% you as a user can produce a proof from the<00:21:00.480> circuit<00:21:00.860> then<00:21:01.860> that<00:21:02.400> proof<00:21:02.700> will<00:21:02.880> provide 00:21:03.590 --> 00:21:03.600 align:start position:0% the circuit then that proof will provide 00:21:03.600 --> 00:21:06.710 align:start position:0% the circuit then that proof will provide you<00:21:03.720> the<00:21:03.960> ability<00:21:04.200> to<00:21:04.440> get<00:21:04.559> your<00:21:04.740> funds<00:21:04.980> back 00:21:06.710 --> 00:21:06.720 align:start position:0% you the ability to get your funds back 00:21:06.720 --> 00:21:09.830 align:start position:0% you the ability to get your funds back um<00:21:06.799> so<00:21:07.799> that<00:21:08.280> sounds<00:21:08.460> great<00:21:08.760> but<00:21:09.360> it's<00:21:09.539> also 00:21:09.830 --> 00:21:09.840 align:start position:0% um so that sounds great but it's also 00:21:09.840 --> 00:21:11.750 align:start position:0% um so that sounds great but it's also kind<00:21:10.080> of<00:21:10.200> difficult<00:21:10.440> how<00:21:11.340> does<00:21:11.460> the<00:21:11.640> average 00:21:11.750 --> 00:21:11.760 align:start position:0% kind of difficult how does the average 00:21:11.760 --> 00:21:14.630 align:start position:0% kind of difficult how does the average user<00:21:12.240> especially<00:21:12.720> when<00:21:13.500> these<00:21:13.799> proofs<00:21:14.160> are 00:21:14.630 --> 00:21:14.640 align:start position:0% user especially when these proofs are 00:21:14.640 --> 00:21:15.890 align:start position:0% user especially when these proofs are off<00:21:15.059> chain 00:21:15.890 --> 00:21:15.900 align:start position:0% off chain 00:21:15.900 --> 00:21:18.230 align:start position:0% off chain um<00:21:15.960> in<00:21:16.260> usually<00:21:16.799> sometimes<00:21:17.100> proprietary<00:21:17.700> how 00:21:18.230 --> 00:21:18.240 align:start position:0% um in usually sometimes proprietary how 00:21:18.240 --> 00:21:20.630 align:start position:0% um in usually sometimes proprietary how do<00:21:18.299> you<00:21:18.360> generate<00:21:18.660> that<00:21:18.840> proof<00:21:19.559> um<00:21:19.559> that's<00:21:20.100> one 00:21:20.630 --> 00:21:20.640 align:start position:0% do you generate that proof um that's one 00:21:20.640 --> 00:21:22.669 align:start position:0% do you generate that proof um that's one of<00:21:20.760> there's<00:21:21.120> a<00:21:21.299> few<00:21:21.480> things<00:21:21.720> that<00:21:22.020> you<00:21:22.320> have<00:21:22.500> to 00:21:22.669 --> 00:21:22.679 align:start position:0% of there's a few things that you have to 00:21:22.679 --> 00:21:26.090 align:start position:0% of there's a few things that you have to really<00:21:22.980> do<00:21:23.400> to<00:21:24.059> inherit<00:21:24.600> full<00:21:25.500> ethereum 00:21:26.090 --> 00:21:26.100 align:start position:0% really do to inherit full ethereum 00:21:26.100 --> 00:21:29.930 align:start position:0% really do to inherit full ethereum security<00:21:26.340> so<00:21:27.120> let's<00:21:27.299> go<00:21:27.539> through<00:21:27.660> them 00:21:29.930 --> 00:21:29.940 align:start position:0% 00:21:29.940 --> 00:21:31.909 align:start position:0% to<00:21:30.179> have<00:21:30.419> the<00:21:30.600> available<00:21:30.720> data<00:21:31.260> on<00:21:31.500> layer<00:21:31.799> one 00:21:31.909 --> 00:21:31.919 align:start position:0% to have the available data on layer one 00:21:31.919 --> 00:21:34.310 align:start position:0% to have the available data on layer one so<00:21:32.460> if<00:21:32.940> you<00:21:33.059> don't<00:21:33.240> have<00:21:33.419> that<00:21:33.600> available<00:21:33.780> data 00:21:34.310 --> 00:21:34.320 align:start position:0% so if you don't have that available data 00:21:34.320 --> 00:21:36.049 align:start position:0% so if you don't have that available data then<00:21:34.559> you<00:21:34.799> can't<00:21:35.039> reconstruct<00:21:35.700> the<00:21:35.940> state 00:21:36.049 --> 00:21:36.059 align:start position:0% then you can't reconstruct the state 00:21:36.059 --> 00:21:38.270 align:start position:0% then you can't reconstruct the state proof<00:21:36.480> and<00:21:36.780> therefore<00:21:37.080> you<00:21:37.620> won't<00:21:37.799> be<00:21:37.980> able<00:21:38.159> to 00:21:38.270 --> 00:21:38.280 align:start position:0% proof and therefore you won't be able to 00:21:38.280 --> 00:21:40.730 align:start position:0% proof and therefore you won't be able to properly<00:21:39.179> get<00:21:39.480> your<00:21:39.600> funds<00:21:39.960> back<00:21:40.020> from<00:21:40.260> the<00:21:40.380> L1 00:21:40.730 --> 00:21:40.740 align:start position:0% properly get your funds back from the L1 00:21:40.740 --> 00:21:43.430 align:start position:0% properly get your funds back from the L1 contract 00:21:43.430 --> 00:21:43.440 align:start position:0% 00:21:43.440 --> 00:21:45.230 align:start position:0% um secondly<00:21:43.919> you<00:21:44.340> need<00:21:44.520> to<00:21:44.640> have<00:21:44.760> functional 00:21:45.230 --> 00:21:45.240 align:start position:0% um secondly you need to have functional 00:21:45.240 --> 00:21:48.169 align:start position:0% um secondly you need to have functional and<00:21:45.900> accessible<00:21:46.320> Force<00:21:46.740> exits<00:21:47.220> so 00:21:48.169 --> 00:21:48.179 align:start position:0% and accessible Force exits so 00:21:48.179 --> 00:21:51.110 align:start position:0% and accessible Force exits so those<00:21:49.080> Force<00:21:49.380> exits<00:21:49.799> have<00:21:49.919> to<00:21:50.039> be<00:21:50.220> in<00:21:50.520> code<00:21:50.760> and 00:21:51.110 --> 00:21:51.120 align:start position:0% those Force exits have to be in code and 00:21:51.120 --> 00:21:52.909 align:start position:0% those Force exits have to be in code and they<00:21:51.240> have<00:21:51.419> to<00:21:51.539> be<00:21:51.780> accessible<00:21:52.620> for<00:21:52.799> the 00:21:52.909 --> 00:21:52.919 align:start position:0% they have to be accessible for the 00:21:52.919 --> 00:21:54.409 align:start position:0% they have to be accessible for the average<00:21:53.039> person<00:21:53.400> they<00:21:53.820> need<00:21:53.940> to<00:21:54.059> be<00:21:54.179> able<00:21:54.299> to 00:21:54.409 --> 00:21:54.419 align:start position:0% average person they need to be able to 00:21:54.419 --> 00:21:56.090 align:start position:0% average person they need to be able to generate<00:21:54.780> those<00:21:54.960> proofs<00:21:55.320> they<00:21:55.799> need<00:21:55.919> to<00:21:56.039> be 00:21:56.090 --> 00:21:56.100 align:start position:0% generate those proofs they need to be 00:21:56.100 --> 00:21:59.090 align:start position:0% generate those proofs they need to be able<00:21:56.280> to<00:21:56.400> take<00:21:57.059> that<00:21:57.299> data<00:21:58.020> um<00:21:58.140> and<00:21:58.440> Pull<00:21:58.679> and 00:21:59.090 --> 00:21:59.100 align:start position:0% able to take that data um and Pull and 00:21:59.100 --> 00:22:02.149 align:start position:0% able to take that data um and Pull and directly<00:21:59.640> send<00:22:00.539> it<00:22:00.659> to<00:22:00.840> that<00:22:00.960> L1<00:22:01.260> contract<00:22:02.159> um 00:22:02.149 --> 00:22:02.159 align:start position:0% directly send it to that L1 contract um 00:22:02.159 --> 00:22:04.430 align:start position:0% directly send it to that L1 contract um that<00:22:02.820> for<00:22:03.120> a<00:22:03.299> lot<00:22:03.360> of<00:22:03.480> devs<00:22:03.780> it's<00:22:03.960> not<00:22:04.140> a<00:22:04.260> big 00:22:04.430 --> 00:22:04.440 align:start position:0% that for a lot of devs it's not a big 00:22:04.440 --> 00:22:05.810 align:start position:0% that for a lot of devs it's not a big deal<00:22:04.679> that 00:22:05.810 --> 00:22:05.820 align:start position:0% deal that 00:22:05.820 --> 00:22:07.730 align:start position:0% deal that um there's<00:22:06.419> the<00:22:06.720> the<00:22:06.900> front<00:22:07.200> ends<00:22:07.500> are<00:22:07.559> all 00:22:07.730 --> 00:22:07.740 align:start position:0% um there's the the front ends are all 00:22:07.740 --> 00:22:09.890 align:start position:0% um there's the the front ends are all centralized<00:22:08.280> but<00:22:08.580> we<00:22:09.179> need<00:22:09.240> decentralized 00:22:09.890 --> 00:22:09.900 align:start position:0% centralized but we need decentralized 00:22:09.900 --> 00:22:11.750 align:start position:0% centralized but we need decentralized front<00:22:09.960> ends<00:22:10.260> to<00:22:10.380> allow<00:22:10.559> people<00:22:10.679> to<00:22:10.860> escape 00:22:11.750 --> 00:22:11.760 align:start position:0% front ends to allow people to escape 00:22:11.760 --> 00:22:15.110 align:start position:0% front ends to allow people to escape um<00:22:11.820> in<00:22:12.120> the<00:22:12.240> case<00:22:12.360> of<00:22:12.900> one<00:22:13.440> of<00:22:13.559> the<00:22:13.559> sequencers 00:22:15.110 --> 00:22:15.120 align:start position:0% um in the case of one of the sequencers 00:22:15.120 --> 00:22:18.289 align:start position:0% um in the case of one of the sequencers um going<00:22:15.360> evil<00:22:15.900> so<00:22:16.740> then<00:22:17.039> thirdly<00:22:17.520> you<00:22:18.120> need 00:22:18.289 --> 00:22:18.299 align:start position:0% um going evil so then thirdly you need 00:22:18.299 --> 00:22:21.049 align:start position:0% um going evil so then thirdly you need time<00:22:18.419> delays<00:22:18.900> for<00:22:19.020> the<00:22:19.080> L1<00:22:19.380> contracts<00:22:19.919> so 00:22:21.049 --> 00:22:21.059 align:start position:0% time delays for the L1 contracts so 00:22:21.059 --> 00:22:23.270 align:start position:0% time delays for the L1 contracts so if<00:22:21.419> the<00:22:21.600> layer<00:22:21.840> 1<00:22:21.960> contracts<00:22:22.559> aren't<00:22:22.919> have 00:22:23.270 --> 00:22:23.280 align:start position:0% if the layer 1 contracts aren't have 00:22:23.280 --> 00:22:26.029 align:start position:0% if the layer 1 contracts aren't have time<00:22:23.520> delays<00:22:23.940> or<00:22:24.179> if<00:22:24.419> they're<00:22:24.659> immutable 00:22:26.029 --> 00:22:26.039 align:start position:0% time delays or if they're immutable 00:22:26.039 --> 00:22:27.950 align:start position:0% time delays or if they're immutable um<00:22:26.100> then<00:22:26.340> it<00:22:26.520> gives<00:22:26.940> people<00:22:27.179> the<00:22:27.419> chance<00:22:27.659> to 00:22:27.950 --> 00:22:27.960 align:start position:0% um then it gives people the chance to 00:22:27.960 --> 00:22:30.890 align:start position:0% um then it gives people the chance to actually<00:22:28.140> exit<00:22:28.620> from<00:22:28.860> that<00:22:29.039> later<00:22:29.220> one<00:22:29.460> but<00:22:29.940> if 00:22:30.890 --> 00:22:30.900 align:start position:0% actually exit from that later one but if 00:22:30.900 --> 00:22:33.289 align:start position:0% actually exit from that later one but if they<00:22:31.020> don't<00:22:31.200> have<00:22:31.380> time<00:22:31.620> delays<00:22:32.100> then<00:22:32.640> they 00:22:33.289 --> 00:22:33.299 align:start position:0% they don't have time delays then they 00:22:33.299 --> 00:22:34.909 align:start position:0% they don't have time delays then they can<00:22:33.419> just<00:22:33.539> change<00:22:33.720> the<00:22:34.020> contract<00:22:34.440> and 00:22:34.909 --> 00:22:34.919 align:start position:0% can just change the contract and 00:22:34.919 --> 00:22:36.529 align:start position:0% can just change the contract and everyone's<00:22:35.460> funds<00:22:35.760> will<00:22:35.880> be<00:22:36.000> frozen<00:22:36.120> from 00:22:36.529 --> 00:22:36.539 align:start position:0% everyone's funds will be frozen from 00:22:36.539 --> 00:22:38.090 align:start position:0% everyone's funds will be frozen from there<00:22:36.659> so 00:22:38.090 --> 00:22:38.100 align:start position:0% there so 00:22:38.100 --> 00:22:41.390 align:start position:0% there so um<00:22:38.159> and<00:22:38.520> then<00:22:38.760> late<00:22:39.179> then<00:22:39.659> last<00:22:39.960> is<00:22:40.740> um<00:22:40.740> this<00:22:41.340> is 00:22:41.390 --> 00:22:41.400 align:start position:0% um and then late then last is um this is 00:22:41.400 --> 00:22:43.909 align:start position:0% um and then late then last is um this is a<00:22:41.580> nuanced<00:22:42.000> one<00:22:42.179> but<00:22:42.539> the<00:22:43.200> the<00:22:43.440> amount<00:22:43.799> of 00:22:43.909 --> 00:22:43.919 align:start position:0% a nuanced one but the the amount of 00:22:43.919 --> 00:22:47.270 align:start position:0% a nuanced one but the the amount of money<00:22:44.100> that<00:22:44.400> you<00:22:44.520> can<00:22:44.640> secure<00:22:45.000> from<00:22:45.960> L1<00:22:46.380> is 00:22:47.270 --> 00:22:47.280 align:start position:0% money that you can secure from L1 is 00:22:47.280 --> 00:22:49.130 align:start position:0% money that you can secure from L1 is really<00:22:47.520> based<00:22:48.000> upon<00:22:48.179> the<00:22:48.360> amount<00:22:48.539> of<00:22:48.720> locked 00:22:49.130 --> 00:22:49.140 align:start position:0% really based upon the amount of locked 00:22:49.140 --> 00:22:52.430 align:start position:0% really based upon the amount of locked funds<00:22:49.500> on<00:22:49.799> layer<00:22:50.100> one<00:22:50.220> so<00:22:50.760> if<00:22:51.659> if<00:22:52.080> everyone 00:22:52.430 --> 00:22:52.440 align:start position:0% funds on layer one so if if everyone 00:22:52.440 --> 00:22:55.010 align:start position:0% funds on layer one so if if everyone Force<00:22:52.919> exits<00:22:53.400> then<00:22:53.760> the<00:22:54.179> layer<00:22:54.419> one<00:22:54.539> contract 00:22:55.010 --> 00:22:55.020 align:start position:0% Force exits then the layer one contract 00:22:55.020 --> 00:22:56.510 align:start position:0% Force exits then the layer one contract which<00:22:55.320> is<00:22:55.440> the<00:22:55.620> bridge<00:22:55.740> contract<00:22:56.159> with<00:22:56.340> all 00:22:56.510 --> 00:22:56.520 align:start position:0% which is the bridge contract with all 00:22:56.520 --> 00:22:57.590 align:start position:0% which is the bridge contract with all the<00:22:56.640> assets 00:22:57.590 --> 00:22:57.600 align:start position:0% the assets 00:22:57.600 --> 00:22:59.390 align:start position:0% the assets um<00:22:57.659> they<00:22:57.960> will<00:22:58.140> impart<00:22:58.620> all<00:22:58.799> their<00:22:58.980> assets<00:22:59.220> to 00:22:59.390 --> 00:22:59.400 align:start position:0% um they will impart all their assets to 00:22:59.400 --> 00:23:01.070 align:start position:0% um they will impart all their assets to the<00:22:59.520> people<00:22:59.700> but<00:23:00.240> if<00:23:00.419> there's<00:23:00.539> more<00:23:00.720> total 00:23:01.070 --> 00:23:01.080 align:start position:0% the people but if there's more total 00:23:01.080 --> 00:23:03.590 align:start position:0% the people but if there's more total locked<00:23:01.380> value<00:23:01.559> above<00:23:02.100> on<00:23:02.400> Layer<00:23:02.760> Two<00:23:02.880> then 00:23:03.590 --> 00:23:03.600 align:start position:0% locked value above on Layer Two then 00:23:03.600 --> 00:23:05.750 align:start position:0% locked value above on Layer Two then somebody's<00:23:04.320> going<00:23:04.440> to<00:23:04.559> be<00:23:04.620> out<00:23:04.740> of<00:23:04.860> luck<00:23:05.039> so 00:23:05.750 --> 00:23:05.760 align:start position:0% somebody's going to be out of luck so 00:23:05.760 --> 00:23:09.409 align:start position:0% somebody's going to be out of luck so the<00:23:06.120> best<00:23:06.240> way<00:23:06.539> to<00:23:06.960> think<00:23:07.380> about<00:23:07.500> this<00:23:07.799> is<00:23:08.419> a 00:23:09.409 --> 00:23:09.419 align:start position:0% the best way to think about this is a 00:23:09.419 --> 00:23:11.090 align:start position:0% the best way to think about this is a lot<00:23:09.539> of<00:23:09.720> the<00:23:09.900> l2s<00:23:10.500> are<00:23:10.679> starting<00:23:10.860> to<00:23:10.980> get 00:23:11.090 --> 00:23:11.100 align:start position:0% lot of the l2s are starting to get 00:23:11.100 --> 00:23:13.850 align:start position:0% lot of the l2s are starting to get traction<00:23:11.460> with<00:23:12.059> direct<00:23:12.360> transfers<00:23:13.080> to<00:23:13.320> them 00:23:13.850 --> 00:23:13.860 align:start position:0% traction with direct transfers to them 00:23:13.860 --> 00:23:15.289 align:start position:0% traction with direct transfers to them um<00:23:13.919> they<00:23:14.220> might<00:23:14.400> even<00:23:14.520> have<00:23:14.700> their<00:23:14.880> own<00:23:15.000> state 00:23:15.289 --> 00:23:15.299 align:start position:0% um they might even have their own state 00:23:15.299 --> 00:23:16.789 align:start position:0% um they might even have their own state from<00:23:15.539> different<00:23:15.780> contracts<00:23:16.380> and<00:23:16.559> Native 00:23:16.789 --> 00:23:16.799 align:start position:0% from different contracts and Native 00:23:16.799 --> 00:23:18.529 align:start position:0% from different contracts and Native tokens 00:23:18.529 --> 00:23:18.539 align:start position:0% tokens 00:23:18.539 --> 00:23:21.649 align:start position:0% tokens if<00:23:18.960> you<00:23:19.080> have<00:23:19.260> a<00:23:19.320> native<00:23:19.500> token<00:23:19.919> on<00:23:20.159> an<00:23:20.340> L2<00:23:20.700> and 00:23:21.649 --> 00:23:21.659 align:start position:0% if you have a native token on an L2 and 00:23:21.659 --> 00:23:23.390 align:start position:0% if you have a native token on an L2 and you<00:23:21.840> don't<00:23:22.020> have<00:23:22.200> assets<00:23:22.559> backing<00:23:22.980> it<00:23:23.100> up<00:23:23.220> on 00:23:23.390 --> 00:23:23.400 align:start position:0% you don't have assets backing it up on 00:23:23.400 --> 00:23:26.029 align:start position:0% you don't have assets backing it up on the<00:23:23.520> layer<00:23:23.760> 1<00:23:23.880> Bridge<00:23:24.120> contract<00:23:24.539> then<00:23:25.320> the 00:23:26.029 --> 00:23:26.039 align:start position:0% the layer 1 Bridge contract then the 00:23:26.039 --> 00:23:27.890 align:start position:0% the layer 1 Bridge contract then the ability<00:23:26.400> for<00:23:26.700> you<00:23:26.820> to<00:23:27.000> inherit<00:23:27.480> ethereum 00:23:27.890 --> 00:23:27.900 align:start position:0% ability for you to inherit ethereum 00:23:27.900 --> 00:23:29.630 align:start position:0% ability for you to inherit ethereum security<00:23:28.140> and<00:23:28.440> take<00:23:28.620> your<00:23:28.740> assets<00:23:29.100> off<00:23:29.640> um 00:23:29.630 --> 00:23:29.640 align:start position:0% security and take your assets off um 00:23:29.640 --> 00:23:32.090 align:start position:0% security and take your assets off um isn't<00:23:30.120> there<00:23:30.299> so<00:23:31.200> it's<00:23:31.620> really<00:23:31.740> important 00:23:32.090 --> 00:23:32.100 align:start position:0% isn't there so it's really important 00:23:32.100 --> 00:23:35.029 align:start position:0% isn't there so it's really important that<00:23:32.760> um<00:23:32.760> as<00:23:33.179> we<00:23:33.299> move<00:23:33.539> forward<00:23:33.840> that<00:23:34.500> any 00:23:35.029 --> 00:23:35.039 align:start position:0% that um as we move forward that any 00:23:35.039 --> 00:23:38.630 align:start position:0% that um as we move forward that any state<00:23:35.340> that<00:23:35.760> is<00:23:36.000> native<00:23:36.240> to<00:23:36.480> the<00:23:36.600> L2<00:23:36.960> is<00:23:38.100> um<00:23:38.159> is 00:23:38.630 --> 00:23:38.640 align:start position:0% state that is native to the L2 is um is 00:23:38.640 --> 00:23:42.409 align:start position:0% state that is native to the L2 is um is known<00:23:38.820> as<00:23:39.059> for<00:23:39.299> that<00:23:39.480> risk<00:23:39.840> that<00:23:40.020> it<00:23:40.200> has<00:23:40.380> so 00:23:42.409 --> 00:23:42.419 align:start position:0% known as for that risk that it has so 00:23:42.419 --> 00:23:43.730 align:start position:0% known as for that risk that it has so now 00:23:43.730 --> 00:23:43.740 align:start position:0% now 00:23:43.740 --> 00:23:46.010 align:start position:0% now um<00:23:43.799> let's<00:23:44.520> get<00:23:44.760> in<00:23:44.880> I<00:23:45.480> guess<00:23:45.539> this<00:23:45.720> is<00:23:45.840> the<00:23:45.900> end 00:23:46.010 --> 00:23:46.020 align:start position:0% um let's get in I guess this is the end 00:23:46.020 --> 00:23:47.510 align:start position:0% um let's get in I guess this is the end of<00:23:46.140> my<00:23:46.260> talk<00:23:46.380> so<00:23:46.679> I'm<00:23:46.980> going<00:23:47.159> to<00:23:47.220> try<00:23:47.400> and 00:23:47.510 --> 00:23:47.520 align:start position:0% of my talk so I'm going to try and 00:23:47.520 --> 00:23:48.950 align:start position:0% of my talk so I'm going to try and implore<00:23:47.760> you<00:23:47.940> to<00:23:48.120> get<00:23:48.299> into<00:23:48.419> the<00:23:48.659> data 00:23:48.950 --> 00:23:48.960 align:start position:0% implore you to get into the data 00:23:48.960 --> 00:23:51.289 align:start position:0% implore you to get into the data directly<00:23:49.620> um<00:23:49.620> don't<00:23:50.039> be<00:23:50.159> like<00:23:50.280> Waldo 00:23:51.289 --> 00:23:51.299 align:start position:0% directly um don't be like Waldo 00:23:51.299 --> 00:23:52.909 align:start position:0% directly um don't be like Waldo um<00:23:51.419> and<00:23:51.720> be<00:23:51.900> sad<00:23:52.080> because<00:23:52.320> other<00:23:52.500> people<00:23:52.740> tell 00:23:52.909 --> 00:23:52.919 align:start position:0% um and be sad because other people tell 00:23:52.919 --> 00:23:55.490 align:start position:0% um and be sad because other people tell you<00:23:53.039> what's<00:23:53.220> true<00:23:53.460> and<00:23:53.580> what's<00:23:53.760> not<00:23:54.240> um<00:23:54.240> so<00:23:54.960> we 00:23:55.490 --> 00:23:55.500 align:start position:0% you what's true and what's not um so we 00:23:55.500 --> 00:23:56.390 align:start position:0% you what's true and what's not um so we have 00:23:56.390 --> 00:23:56.400 align:start position:0% have 00:23:56.400 --> 00:23:58.789 align:start position:0% have um I<00:23:56.880> I<00:23:57.179> tell<00:23:57.419> you<00:23:57.480> I<00:23:57.960> I'm<00:23:58.260> very<00:23:58.500> impressed 00:23:58.789 --> 00:23:58.799 align:start position:0% um I I tell you I I'm very impressed 00:23:58.799 --> 00:23:59.930 align:start position:0% um I I tell you I I'm very impressed with<00:23:58.860> these<00:23:59.100> projects<00:23:59.400> I<00:23:59.580> think<00:23:59.700> you<00:23:59.820> guys 00:23:59.930 --> 00:23:59.940 align:start position:0% with these projects I think you guys 00:23:59.940 --> 00:24:01.250 align:start position:0% with these projects I think you guys should<00:24:00.120> all<00:24:00.299> check<00:24:00.480> them<00:24:00.659> out<00:24:00.780> they're<00:24:01.080> all 00:24:01.250 --> 00:24:01.260 align:start position:0% should all check them out they're all 00:24:01.260 --> 00:24:04.490 align:start position:0% should all check them out they're all open<00:24:01.500> you<00:24:01.919> have<00:24:02.100> bigquery<00:24:02.820> you<00:24:03.179> have<00:24:03.360> Dune 00:24:04.490 --> 00:24:04.500 align:start position:0% open you have bigquery you have Dune 00:24:04.500 --> 00:24:06.770 align:start position:0% open you have bigquery you have Dune um the<00:24:05.039> dunes<00:24:05.460> getting<00:24:05.760> better<00:24:05.940> and<00:24:06.120> better 00:24:06.770 --> 00:24:06.780 align:start position:0% um the dunes getting better and better 00:24:06.780 --> 00:24:08.870 align:start position:0% um the dunes getting better and better um<00:24:06.840> and<00:24:07.020> then<00:24:07.260> the<00:24:07.980> bigqueries<00:24:08.580> of<00:24:08.760> public 00:24:08.870 --> 00:24:08.880 align:start position:0% um and then the bigqueries of public 00:24:08.880 --> 00:24:10.970 align:start position:0% um and then the bigqueries of public database<00:24:09.419> that<00:24:09.659> has<00:24:09.900> all<00:24:10.080> the<00:24:10.320> ethereum<00:24:10.679> layer 00:24:10.970 --> 00:24:10.980 align:start position:0% database that has all the ethereum layer 00:24:10.980 --> 00:24:13.250 align:start position:0% database that has all the ethereum layer one<00:24:11.100> posted<00:24:12.000> there<00:24:12.179> they'll<00:24:12.720> give<00:24:12.840> you<00:24:12.960> 300 00:24:13.250 --> 00:24:13.260 align:start position:0% one posted there they'll give you 300 00:24:13.260 --> 00:24:15.710 align:start position:0% one posted there they'll give you 300 credits<00:24:13.919> to<00:24:14.100> go<00:24:14.280> on<00:24:14.580> query<00:24:14.940> through<00:24:15.120> it<00:24:15.600> um<00:24:15.600> and 00:24:15.710 --> 00:24:15.720 align:start position:0% credits to go on query through it um and 00:24:15.720 --> 00:24:17.510 align:start position:0% credits to go on query through it um and you<00:24:15.900> can<00:24:15.960> really<00:24:16.340> differentiate<00:24:17.340> yourself 00:24:17.510 --> 00:24:17.520 align:start position:0% you can really differentiate yourself 00:24:17.520 --> 00:24:20.090 align:start position:0% you can really differentiate yourself especially<00:24:18.059> as<00:24:18.240> a<00:24:18.419> data<00:24:18.720> scientist<00:24:19.559> um 00:24:20.090 --> 00:24:20.100 align:start position:0% especially as a data scientist um 00:24:20.100 --> 00:24:24.169 align:start position:0% especially as a data scientist um you<00:24:20.640> have 00:24:24.169 --> 00:24:24.179 align:start position:0% 00:24:24.179 --> 00:24:25.970 align:start position:0% that<00:24:24.840> the<00:24:24.960> project<00:24:25.500> that<00:24:25.740> I<00:24:25.860> actually 00:24:25.970 --> 00:24:25.980 align:start position:0% that the project that I actually 00:24:25.980 --> 00:24:28.310 align:start position:0% that the project that I actually completed<00:24:26.880> um<00:24:26.940> please<00:24:27.179> check<00:24:27.539> it<00:24:27.720> out<00:24:27.840> on<00:24:28.140> just 00:24:28.310 --> 00:24:28.320 align:start position:0% completed um please check it out on just 00:24:28.320 --> 00:24:30.110 align:start position:0% completed um please check it out on just the<00:24:28.559> QR<00:24:28.740> code<00:24:28.919> for<00:24:29.100> it<00:24:29.220> I'll<00:24:29.580> have<00:24:29.760> it<00:24:29.880> at<00:24:30.000> the 00:24:30.110 --> 00:24:30.120 align:start position:0% the QR code for it I'll have it at the 00:24:30.120 --> 00:24:31.850 align:start position:0% the QR code for it I'll have it at the end<00:24:30.240> too<00:24:30.360> so<00:24:30.600> obviously<00:24:31.200> miss<00:24:31.380> it<00:24:31.500> it's<00:24:31.620> no<00:24:31.679> big 00:24:31.850 --> 00:24:31.860 align:start position:0% end too so obviously miss it it's no big 00:24:31.860 --> 00:24:32.870 align:start position:0% end too so obviously miss it it's no big deal<00:24:32.039> but 00:24:32.870 --> 00:24:32.880 align:start position:0% deal but 00:24:32.880 --> 00:24:34.730 align:start position:0% deal but um<00:24:32.940> please<00:24:33.120> go<00:24:33.419> check<00:24:33.780> out<00:24:33.900> the<00:24:34.140> data<00:24:34.440> tables 00:24:34.730 --> 00:24:34.740 align:start position:0% um please go check out the data tables 00:24:34.740 --> 00:24:37.250 align:start position:0% um please go check out the data tables all<00:24:34.980> the<00:24:35.100> SQL<00:24:35.400> queries<00:24:35.760> on<00:24:36.480> any<00:24:36.900> of<00:24:37.080> the 00:24:37.250 --> 00:24:37.260 align:start position:0% all the SQL queries on any of the 00:24:37.260 --> 00:24:38.270 align:start position:0% all the SQL queries on any of the different<00:24:37.500> things 00:24:38.270 --> 00:24:38.280 align:start position:0% different things 00:24:38.280 --> 00:24:40.190 align:start position:0% different things um please<00:24:39.000> uh<00:24:39.419> feel<00:24:39.659> free<00:24:39.780> to<00:24:39.900> let<00:24:40.020> me<00:24:40.140> know 00:24:40.190 --> 00:24:40.200 align:start position:0% um please uh feel free to let me know 00:24:40.200 --> 00:24:42.830 align:start position:0% um please uh feel free to let me know what<00:24:40.320> I<00:24:40.440> screwed<00:24:40.799> up<00:24:40.860> and<00:24:41.400> it'll<00:24:41.640> be<00:24:41.760> good 00:24:42.830 --> 00:24:42.840 align:start position:0% what I screwed up and it'll be good 00:24:42.840 --> 00:24:45.230 align:start position:0% what I screwed up and it'll be good um<00:24:42.900> and<00:24:43.020> then<00:24:43.200> L2<00:24:43.799> beat<00:24:44.100> is<00:24:44.640> just<00:24:44.760> such<00:24:45.000> a<00:24:45.179> great 00:24:45.230 --> 00:24:45.240 align:start position:0% um and then L2 beat is just such a great 00:24:45.240 --> 00:24:46.909 align:start position:0% um and then L2 beat is just such a great resource<00:24:45.659> I'm<00:24:45.960> sure<00:24:46.260> everyone's<00:24:46.620> heard<00:24:46.799> of 00:24:46.909 --> 00:24:46.919 align:start position:0% resource I'm sure everyone's heard of 00:24:46.919 --> 00:24:48.169 align:start position:0% resource I'm sure everyone's heard of them<00:24:47.039> and<00:24:47.280> I'm<00:24:47.460> sure<00:24:47.700> you've<00:24:47.880> been<00:24:47.940> to<00:24:48.059> their 00:24:48.169 --> 00:24:48.179 align:start position:0% them and I'm sure you've been to their 00:24:48.179 --> 00:24:50.090 align:start position:0% them and I'm sure you've been to their Booth<00:24:48.480> yesterday<00:24:48.659> but 00:24:50.090 --> 00:24:50.100 align:start position:0% Booth yesterday but 00:24:50.100 --> 00:24:52.430 align:start position:0% Booth yesterday but um<00:24:50.159> they<00:24:50.640> categorize<00:24:51.360> all<00:24:51.659> a<00:24:51.900> lot<00:24:51.960> of<00:24:52.080> risks 00:24:52.430 --> 00:24:52.440 align:start position:0% um they categorize all a lot of risks 00:24:52.440 --> 00:24:54.110 align:start position:0% um they categorize all a lot of risks and<00:24:52.679> a<00:24:52.799> lot<00:24:52.919> of<00:24:53.039> specific<00:24:53.400> things<00:24:53.700> happening 00:24:54.110 --> 00:24:54.120 align:start position:0% and a lot of specific things happening 00:24:54.120 --> 00:24:56.330 align:start position:0% and a lot of specific things happening within<00:24:54.600> these<00:24:54.900> different<00:24:55.020> projects<00:24:55.500> and<00:24:56.159> I 00:24:56.330 --> 00:24:56.340 align:start position:0% within these different projects and I 00:24:56.340 --> 00:24:58.250 align:start position:0% within these different projects and I just<00:24:56.520> can't<00:24:56.700> recommend<00:24:57.120> them<00:24:57.299> enough<00:24:57.480> to 00:24:58.250 --> 00:24:58.260 align:start position:0% just can't recommend them enough to 00:24:58.260 --> 00:25:00.169 align:start position:0% just can't recommend them enough to check<00:24:58.380> them<00:24:58.500> out<00:24:59.039> they're<00:24:59.520> doing<00:24:59.700> Bridges<00:25:00.059> now 00:25:00.169 --> 00:25:00.179 align:start position:0% check them out they're doing Bridges now 00:25:00.179 --> 00:25:01.970 align:start position:0% check them out they're doing Bridges now too<00:25:00.360> which<00:25:00.539> is<00:25:00.659> exciting<00:25:01.380> um<00:25:01.440> and<00:25:01.740> then<00:25:01.860> the 00:25:01.970 --> 00:25:01.980 align:start position:0% too which is exciting um and then the 00:25:01.980 --> 00:25:03.830 align:start position:0% too which is exciting um and then the layer<00:25:02.280> twos<00:25:02.760> um<00:25:02.760> I<00:25:03.000> haven't<00:25:03.120> got<00:25:03.299> to<00:25:03.480> the<00:25:03.600> data 00:25:03.830 --> 00:25:03.840 align:start position:0% layer twos um I haven't got to the data 00:25:03.840 --> 00:25:06.590 align:start position:0% layer twos um I haven't got to the data on<00:25:03.960> layer<00:25:04.320> twos<00:25:04.620> so<00:25:05.100> I<00:25:05.760> I<00:25:05.880> it<00:25:06.240> would<00:25:06.360> be<00:25:06.480> really 00:25:06.590 --> 00:25:06.600 align:start position:0% on layer twos so I I it would be really 00:25:06.600 --> 00:25:08.270 align:start position:0% on layer twos so I I it would be really great<00:25:06.840> for<00:25:07.200> everyone<00:25:07.440> to<00:25:07.740> check<00:25:07.919> out<00:25:08.039> the 00:25:08.270 --> 00:25:08.280 align:start position:0% great for everyone to check out the 00:25:08.280 --> 00:25:10.130 align:start position:0% great for everyone to check out the different<00:25:08.520> we're<00:25:08.880> going<00:25:09.179> to<00:25:09.360> a<00:25:09.600> different 00:25:10.130 --> 00:25:10.140 align:start position:0% different we're going to a different 00:25:10.140 --> 00:25:12.409 align:start position:0% different we're going to a different layer<00:25:10.919> modular<00:25:11.340> blockchain<00:25:11.820> where<00:25:12.120> you<00:25:12.240> have 00:25:12.409 --> 00:25:12.419 align:start position:0% layer modular blockchain where you have 00:25:12.419 --> 00:25:14.690 align:start position:0% layer modular blockchain where you have layer<00:25:13.080> ones<00:25:13.380> layer<00:25:13.799> twos<00:25:14.039> and<00:25:14.159> layer<00:25:14.400> threes 00:25:14.690 --> 00:25:14.700 align:start position:0% layer ones layer twos and layer threes 00:25:14.700 --> 00:25:16.730 align:start position:0% layer ones layer twos and layer threes and<00:25:15.240> these<00:25:15.419> layer<00:25:15.720> threes<00:25:16.080> are<00:25:16.380> going<00:25:16.500> to<00:25:16.620> be 00:25:16.730 --> 00:25:16.740 align:start position:0% and these layer threes are going to be 00:25:16.740 --> 00:25:18.710 align:start position:0% and these layer threes are going to be deployed<00:25:17.100> on<00:25:17.400> layer<00:25:17.700> twos<00:25:18.000> in<00:25:18.299> the<00:25:18.480> Privacy 00:25:18.710 --> 00:25:18.720 align:start position:0% deployed on layer twos in the Privacy 00:25:18.720 --> 00:25:21.830 align:start position:0% deployed on layer twos in the Privacy things<00:25:18.960> already<00:25:19.200> are<00:25:19.500> for<00:25:19.860> like<00:25:19.980> semaphore<00:25:20.580> so 00:25:21.830 --> 00:25:21.840 align:start position:0% things already are for like semaphore so 00:25:21.840 --> 00:25:24.890 align:start position:0% things already are for like semaphore so um<00:25:21.900> I<00:25:22.440> highly<00:25:22.919> recommend<00:25:23.280> that<00:25:23.580> I<00:25:24.240> really<00:25:24.720> like 00:25:24.890 --> 00:25:24.900 align:start position:0% um I highly recommend that I really like 00:25:24.900 --> 00:25:26.990 align:start position:0% um I highly recommend that I really like to<00:25:25.020> see<00:25:25.200> somebody<00:25:25.380> on<00:25:25.980> check<00:25:26.220> out<00:25:26.340> layer<00:25:26.700> twos 00:25:26.990 --> 00:25:27.000 align:start position:0% to see somebody on check out layer twos 00:25:27.000 --> 00:25:28.789 align:start position:0% to see somebody on check out layer twos and<00:25:27.419> be<00:25:27.539> able<00:25:27.659> to<00:25:27.779> do<00:25:27.900> the<00:25:28.020> same<00:25:28.140> data<00:25:28.559> type 00:25:28.789 --> 00:25:28.799 align:start position:0% and be able to do the same data type 00:25:28.799 --> 00:25:30.890 align:start position:0% and be able to do the same data type projects<00:25:29.279> for<00:25:29.460> that<00:25:29.640> so 00:25:30.890 --> 00:25:30.900 align:start position:0% projects for that so 00:25:30.900 --> 00:25:32.390 align:start position:0% projects for that so um<00:25:30.960> I<00:25:31.440> have<00:25:31.559> some<00:25:31.679> thank<00:25:31.799> yous<00:25:32.039> I'd<00:25:32.159> like<00:25:32.279> to 00:25:32.390 --> 00:25:32.400 align:start position:0% um I have some thank yous I'd like to 00:25:32.400 --> 00:25:34.130 align:start position:0% um I have some thank yous I'd like to get<00:25:32.580> get<00:25:33.240> ahead<00:25:33.480> of 00:25:34.130 --> 00:25:34.140 align:start position:0% get get ahead of 00:25:34.140 --> 00:25:35.950 align:start position:0% get get ahead of um<00:25:34.200> so<00:25:34.559> I'd<00:25:35.039> like<00:25:35.159> to<00:25:35.279> thank<00:25:35.400> the<00:25:35.520> daily 00:25:35.950 --> 00:25:35.960 align:start position:0% um so I'd like to thank the daily 00:25:35.960 --> 00:25:38.990 align:start position:0% um so I'd like to thank the daily Discord<00:25:36.960> Channel<00:25:37.320> and<00:25:37.860> and<00:25:38.279> podcast<00:25:38.640> for 00:25:38.990 --> 00:25:39.000 align:start position:0% Discord Channel and and podcast for 00:25:39.000 --> 00:25:40.610 align:start position:0% Discord Channel and and podcast for being<00:25:39.240> so<00:25:39.419> great<00:25:40.020> um<00:25:40.020> that's<00:25:40.260> my<00:25:40.500> favorite 00:25:40.610 --> 00:25:40.620 align:start position:0% being so great um that's my favorite 00:25:40.620 --> 00:25:42.350 align:start position:0% being so great um that's my favorite Discord<00:25:41.039> Channel<00:25:41.279> there<00:25:41.460> is<00:25:41.880> um<00:25:41.880> if<00:25:42.120> you<00:25:42.240> need 00:25:42.350 --> 00:25:42.360 align:start position:0% Discord Channel there is um if you need 00:25:42.360 --> 00:25:43.610 align:start position:0% Discord Channel there is um if you need stud<00:25:42.539> to<00:25:42.840> know<00:25:42.960> things<00:25:43.080> there's<00:25:43.320> so<00:25:43.500> many 00:25:43.610 --> 00:25:43.620 align:start position:0% stud to know things there's so many 00:25:43.620 --> 00:25:44.690 align:start position:0% stud to know things there's so many helpful<00:25:43.919> people 00:25:44.690 --> 00:25:44.700 align:start position:0% helpful people 00:25:44.700 --> 00:25:45.950 align:start position:0% helpful people um 00:25:45.950 --> 00:25:45.960 align:start position:0% um 00:25:45.960 --> 00:25:48.230 align:start position:0% um there's<00:25:46.679> the<00:25:46.860> zero<00:25:47.159> knowledge<00:25:47.340> podcast 00:25:48.230 --> 00:25:48.240 align:start position:0% there's the zero knowledge podcast 00:25:48.240 --> 00:25:50.269 align:start position:0% there's the zero knowledge podcast um it's<00:25:48.480> so<00:25:48.720> good<00:25:48.840> for<00:25:49.200> all<00:25:49.500> the<00:25:49.679> new<00:25:49.919> pressing 00:25:50.269 --> 00:25:50.279 align:start position:0% um it's so good for all the new pressing 00:25:50.279 --> 00:25:53.090 align:start position:0% um it's so good for all the new pressing things<00:25:50.460> I<00:25:50.940> highly<00:25:51.240> recommend<00:25:51.539> them<00:25:51.720> as<00:25:51.840> well 00:25:53.090 --> 00:25:53.100 align:start position:0% things I highly recommend them as well 00:25:53.100 --> 00:25:55.970 align:start position:0% things I highly recommend them as well um<00:25:53.159> l2b<00:25:54.000> I'll<00:25:54.240> show<00:25:54.360> them<00:25:54.539> again 00:25:55.970 --> 00:25:55.980 align:start position:0% um l2b I'll show them again 00:25:55.980 --> 00:25:58.130 align:start position:0% um l2b I'll show them again and<00:25:56.340> then<00:25:56.580> on<00:25:56.760> the<00:25:57.000> ethereum<00:25:57.360> on<00:25:57.720> Foundation 00:25:58.130 --> 00:25:58.140 align:start position:0% and then on the ethereum on Foundation 00:25:58.140 --> 00:26:00.409 align:start position:0% and then on the ethereum on Foundation privacy<00:25:58.679> scaling<00:25:59.159> exploration<00:25:59.580> team 00:26:00.409 --> 00:26:00.419 align:start position:0% privacy scaling exploration team 00:26:00.419 --> 00:26:01.730 align:start position:0% privacy scaling exploration team um<00:26:00.480> that's<00:26:00.659> not<00:26:00.840> their<00:26:00.960> symbol<00:26:01.260> but<00:26:01.440> I<00:26:01.620> think 00:26:01.730 --> 00:26:01.740 align:start position:0% um that's not their symbol but I think 00:26:01.740 --> 00:26:03.890 align:start position:0% um that's not their symbol but I think that<00:26:01.919> there's<00:26:02.220> their<00:26:02.520> new<00:26:02.700> logo<00:26:03.000> for<00:26:03.240> Defcon 00:26:03.890 --> 00:26:03.900 align:start position:0% that there's their new logo for Defcon 00:26:03.900 --> 00:26:06.649 align:start position:0% that there's their new logo for Defcon is<00:26:04.140> really<00:26:04.320> cool<00:26:04.500> so<00:26:04.679> I<00:26:04.799> put<00:26:04.919> it<00:26:05.039> up<00:26:05.159> there<00:26:05.659> and 00:26:06.649 --> 00:26:06.659 align:start position:0% is really cool so I put it up there and 00:26:06.659 --> 00:26:08.570 align:start position:0% is really cool so I put it up there and then<00:26:06.840> I'd<00:26:07.320> like<00:26:07.440> to<00:26:07.500> thank<00:26:07.620> Justin<00:26:07.799> Martin<00:26:08.520> um 00:26:08.570 --> 00:26:08.580 align:start position:0% then I'd like to thank Justin Martin um 00:26:08.580 --> 00:26:09.890 align:start position:0% then I'd like to thank Justin Martin um for<00:26:08.820> all<00:26:08.940> of<00:26:09.059> his<00:26:09.179> help<00:26:09.299> and<00:26:09.480> getting<00:26:09.600> me<00:26:09.779> into 00:26:09.890 --> 00:26:09.900 align:start position:0% for all of his help and getting me into 00:26:09.900 --> 00:26:12.710 align:start position:0% for all of his help and getting me into this<00:26:10.500> um<00:26:10.500> and<00:26:11.279> I'd<00:26:11.460> also<00:26:11.760> like<00:26:11.820> to<00:26:12.000> thank<00:26:12.120> Mark 00:26:12.710 --> 00:26:12.720 align:start position:0% this um and I'd also like to thank Mark 00:26:12.720 --> 00:26:14.390 align:start position:0% this um and I'd also like to thank Mark for<00:26:13.080> all<00:26:13.320> your<00:26:13.440> help<00:26:13.620> getting<00:26:14.039> me<00:26:14.279> through 00:26:14.390 --> 00:26:14.400 align:start position:0% for all your help getting me through 00:26:14.400 --> 00:26:16.070 align:start position:0% for all your help getting me through this<00:26:14.580> stuff<00:26:14.700> and<00:26:15.000> really<00:26:15.539> brainstorming 00:26:16.070 --> 00:26:16.080 align:start position:0% this stuff and really brainstorming 00:26:16.080 --> 00:26:17.750 align:start position:0% this stuff and really brainstorming through<00:26:16.260> it<00:26:16.380> all<00:26:16.500> and<00:26:16.799> I'm<00:26:17.220> trying<00:26:17.520> to<00:26:17.640> get 00:26:17.750 --> 00:26:17.760 align:start position:0% through it all and I'm trying to get 00:26:17.760 --> 00:26:19.970 align:start position:0% through it all and I'm trying to get through<00:26:17.880> all<00:26:18.000> those<00:26:18.179> issues<00:26:18.539> so<00:26:18.659> wow<00:26:19.380> so<00:26:19.740> I<00:26:19.860> got 00:26:19.970 --> 00:26:19.980 align:start position:0% through all those issues so wow so I got 00:26:19.980 --> 00:26:24.110 align:start position:0% through all those issues so wow so I got thank<00:26:20.400> you<00:26:20.520> very<00:26:20.640> much 00:26:24.110 --> 00:26:24.120 align:start position:0% 00:26:24.120 --> 00:26:25.510 align:start position:0% uh 00:26:25.510 --> 00:26:25.520 align:start position:0% uh 00:26:25.520 --> 00:26:29.090 align:start position:0% uh I<00:26:26.520> will<00:26:26.640> take<00:26:26.820> quite<00:26:27.000> yes<00:26:27.360> please 00:26:29.090 --> 00:26:29.100 align:start position:0% I will take quite yes please 00:26:29.100 --> 00:26:31.669 align:start position:0% I will take quite yes please I'm<00:26:29.520> sure<00:26:29.640> yeah<00:26:30.000> they'll<00:26:30.299> have<00:26:30.419> a<00:26:30.539> mic<00:26:30.659> for<00:26:30.779> you 00:26:31.669 --> 00:26:31.679 align:start position:0% I'm sure yeah they'll have a mic for you 00:26:31.679 --> 00:26:33.470 align:start position:0% I'm sure yeah they'll have a mic for you unless<00:26:32.220> you're<00:26:32.400> really<00:26:32.580> loud<00:26:32.880> and<00:26:33.179> then<00:26:33.360> you 00:26:33.470 --> 00:26:33.480 align:start position:0% unless you're really loud and then you 00:26:33.480 --> 00:26:39.169 align:start position:0% unless you're really loud and then you can<00:26:33.600> just<00:26:33.659> go<00:26:33.840> for<00:26:33.960> it 00:26:39.169 --> 00:26:39.179 align:start position:0% 00:26:39.179 --> 00:26:40.970 align:start position:0% I<00:26:39.600> was<00:26:39.659> wondering<00:26:39.900> if<00:26:40.080> you<00:26:40.200> comment<00:26:40.500> a<00:26:40.860> little 00:26:40.970 --> 00:26:40.980 align:start position:0% I was wondering if you comment a little 00:26:40.980 --> 00:26:42.830 align:start position:0% I was wondering if you comment a little bit<00:26:41.100> more<00:26:41.279> on<00:26:41.640> the<00:26:41.820> security<00:26:42.000> considerations 00:26:42.830 --> 00:26:42.840 align:start position:0% bit more on the security considerations 00:26:42.840 --> 00:26:45.470 align:start position:0% bit more on the security considerations when<00:26:43.380> dealing<00:26:43.740> with<00:26:43.860> Native<00:26:44.279> assets<00:26:44.640> on<00:26:44.940> l2s 00:26:45.470 --> 00:26:45.480 align:start position:0% when dealing with Native assets on l2s 00:26:45.480 --> 00:26:46.909 align:start position:0% when dealing with Native assets on l2s like<00:26:45.779> I<00:26:45.900> get<00:26:46.020> that<00:26:46.140> you<00:26:46.260> can't<00:26:46.440> withdraw<00:26:46.860> the 00:26:46.909 --> 00:26:46.919 align:start position:0% like I get that you can't withdraw the 00:26:46.919 --> 00:26:49.010 align:start position:0% like I get that you can't withdraw the funds<00:26:47.220> on<00:26:47.340> the<00:26:47.460> other<00:26:47.580> one<00:26:47.760> but<00:26:48.000> can<00:26:48.840> you 00:26:49.010 --> 00:26:49.020 align:start position:0% funds on the other one but can you 00:26:49.020 --> 00:26:51.110 align:start position:0% funds on the other one but can you double<00:26:49.200> spend<00:26:49.620> or<00:26:49.860> can<00:26:50.100> eat<00:26:50.520> out<00:26:50.700> there<00:26:50.940> like 00:26:51.110 --> 00:26:51.120 align:start position:0% double spend or can eat out there like 00:26:51.120 --> 00:26:53.090 align:start position:0% double spend or can eat out there like Forge<00:26:51.600> a<00:26:52.140> balance<00:26:52.440> or<00:26:52.620> things<00:26:52.799> like<00:26:52.980> that 00:26:53.090 --> 00:26:53.100 align:start position:0% Forge a balance or things like that 00:26:53.100 --> 00:26:55.250 align:start position:0% Forge a balance or things like that given<00:26:53.460> the<00:26:53.520> stage<00:26:53.760> rolled<00:26:54.120> up<00:26:54.179> no<00:26:54.659> I<00:26:54.840> you<00:26:55.140> know 00:26:55.250 --> 00:26:55.260 align:start position:0% given the stage rolled up no I you know 00:26:55.260 --> 00:26:57.529 align:start position:0% given the stage rolled up no I you know I<00:26:55.620> I<00:26:55.740> don't<00:26:56.100> think<00:26:56.340> that<00:26:56.580> those<00:26:56.760> are<00:26:56.880> concerns 00:26:57.529 --> 00:26:57.539 align:start position:0% I I don't think that those are concerns 00:26:57.539 --> 00:26:59.330 align:start position:0% I I don't think that those are concerns um to<00:26:57.720> do<00:26:57.840> double<00:26:57.960> spends<00:26:58.380> and<00:26:58.500> things<00:26:58.620> but<00:26:58.919> I 00:26:59.330 --> 00:26:59.340 align:start position:0% um to do double spends and things but I 00:26:59.340 --> 00:27:00.230 align:start position:0% um to do double spends and things but I do<00:26:59.460> think 00:27:00.230 --> 00:27:00.240 align:start position:0% do think 00:27:00.240 --> 00:27:02.450 align:start position:0% do think um<00:27:00.299> because<00:27:00.600> your<00:27:01.140> state<00:27:01.380> is<00:27:01.799> the<00:27:02.279> state 00:27:02.450 --> 00:27:02.460 align:start position:0% um because your state is the state 00:27:02.460 --> 00:27:03.769 align:start position:0% um because your state is the state source<00:27:02.760> of<00:27:02.820> Truth<00:27:03.000> is<00:27:03.179> really<00:27:03.360> sitting<00:27:03.659> on 00:27:03.769 --> 00:27:03.779 align:start position:0% source of Truth is really sitting on 00:27:03.779 --> 00:27:05.630 align:start position:0% source of Truth is really sitting on layer<00:27:04.140> one<00:27:04.260> so 00:27:05.630 --> 00:27:05.640 align:start position:0% layer one so 00:27:05.640 --> 00:27:08.210 align:start position:0% layer one so um<00:27:05.700> you're<00:27:06.179> not<00:27:06.360> going<00:27:06.480> to<00:27:06.600> be<00:27:06.659> able<00:27:06.779> to<00:27:07.140> uh<00:27:07.740> one 00:27:08.210 --> 00:27:08.220 align:start position:0% um you're not going to be able to uh one 00:27:08.220 --> 00:27:09.110 align:start position:0% um you're not going to be able to uh one of<00:27:08.279> the<00:27:08.340> reasons<00:27:08.520> they<00:27:08.640> do<00:27:08.820> some<00:27:08.940> of<00:27:09.059> the 00:27:09.110 --> 00:27:09.120 align:start position:0% of the reasons they do some of the 00:27:09.120 --> 00:27:10.789 align:start position:0% of the reasons they do some of the delays<00:27:09.480> and<00:27:09.600> things<00:27:09.779> I<00:27:10.080> believe<00:27:10.200> is<00:27:10.500> to<00:27:10.620> stop 00:27:10.789 --> 00:27:10.799 align:start position:0% delays and things I believe is to stop 00:27:10.799 --> 00:27:13.970 align:start position:0% delays and things I believe is to stop double<00:27:10.980> spend<00:27:11.279> from<00:27:11.460> happening<00:27:12.240> um<00:27:12.360> but<00:27:13.020> the 00:27:13.970 --> 00:27:13.980 align:start position:0% double spend from happening um but the 00:27:13.980 --> 00:27:15.169 align:start position:0% double spend from happening um but the um<00:27:14.100> and<00:27:14.279> that's<00:27:14.340> why<00:27:14.520> they<00:27:14.640> freeze<00:27:14.940> the<00:27:15.059> state 00:27:15.169 --> 00:27:15.179 align:start position:0% um and that's why they freeze the state 00:27:15.179 --> 00:27:16.730 align:start position:0% um and that's why they freeze the state route<00:27:15.419> on<00:27:15.659> layer<00:27:15.900> once 00:27:16.730 --> 00:27:16.740 align:start position:0% route on layer once 00:27:16.740 --> 00:27:20.029 align:start position:0% route on layer once um<00:27:16.860> but<00:27:17.580> I<00:27:17.880> I<00:27:18.059> don't<00:27:18.419> think<00:27:18.659> that<00:27:19.440> um<00:27:19.440> yeah<00:27:19.740> if 00:27:20.029 --> 00:27:20.039 align:start position:0% um but I I don't think that um yeah if 00:27:20.039 --> 00:27:21.590 align:start position:0% um but I I don't think that um yeah if you<00:27:20.100> understand<00:27:20.279> I<00:27:20.940> won't<00:27:21.000> go<00:27:21.179> back<00:27:21.240> over<00:27:21.360> the 00:27:21.590 --> 00:27:21.600 align:start position:0% you understand I won't go back over the 00:27:21.600 --> 00:27:23.990 align:start position:0% you understand I won't go back over the ideas<00:27:21.720> of<00:27:22.200> but<00:27:22.740> if<00:27:22.919> you<00:27:23.039> have<00:27:23.159> tokens<00:27:23.640> that<00:27:23.880> are 00:27:23.990 --> 00:27:24.000 align:start position:0% ideas of but if you have tokens that are 00:27:24.000 --> 00:27:25.010 align:start position:0% ideas of but if you have tokens that are here 00:27:25.010 --> 00:27:25.020 align:start position:0% here 00:27:25.020 --> 00:27:26.930 align:start position:0% here um<00:27:25.080> and<00:27:25.320> the<00:27:25.559> values<00:27:25.860> more<00:27:26.159> are<00:27:26.400> there<00:27:26.640> than<00:27:26.820> on 00:27:26.930 --> 00:27:26.940 align:start position:0% um and the values more are there than on 00:27:26.940 --> 00:27:28.430 align:start position:0% um and the values more are there than on the<00:27:27.059> bridge<00:27:27.179> contract<00:27:27.539> then<00:27:27.900> you<00:27:28.140> won't<00:27:28.260> be 00:27:28.430 --> 00:27:28.440 align:start position:0% the bridge contract then you won't be 00:27:28.440 --> 00:27:29.750 align:start position:0% the bridge contract then you won't be able<00:27:28.559> to<00:27:28.740> get<00:27:28.860> your<00:27:29.039> money<00:27:29.159> back<00:27:29.279> off<00:27:29.520> of<00:27:29.640> there 00:27:29.750 --> 00:27:29.760 align:start position:0% able to get your money back off of there 00:27:29.760 --> 00:27:31.789 align:start position:0% able to get your money back off of there so<00:27:30.059> if<00:27:30.299> it<00:27:30.539> makes<00:27:30.600> sense 00:27:31.789 --> 00:27:31.799 align:start position:0% so if it makes sense 00:27:31.799 --> 00:27:34.070 align:start position:0% so if it makes sense hello<00:27:32.279> so<00:27:32.700> when<00:27:32.880> you're<00:27:33.059> talking<00:27:33.240> about<00:27:33.480> State 00:27:34.070 --> 00:27:34.080 align:start position:0% hello so when you're talking about State 00:27:34.080 --> 00:27:36.529 align:start position:0% hello so when you're talking about State on<00:27:34.380> layer<00:27:34.799> one<00:27:34.919> have<00:27:35.460> you<00:27:35.580> had<00:27:35.760> any<00:27:36.000> thoughts 00:27:36.529 --> 00:27:36.539 align:start position:0% on layer one have you had any thoughts 00:27:36.539 --> 00:27:41.750 align:start position:0% on layer one have you had any thoughts in<00:27:36.840> regards<00:27:37.200> to<00:27:37.320> uh<00:27:38.220> upcoming<00:27:38.760> State<00:27:39.299> expiry 00:27:41.750 --> 00:27:41.760 align:start position:0% in regards to uh upcoming State expiry 00:27:41.760 --> 00:27:44.690 align:start position:0% in regards to uh upcoming State expiry not<00:27:42.419> yet<00:27:42.659> but<00:27:43.260> I<00:27:43.440> I<00:27:43.620> would<00:27:43.799> love<00:27:43.980> that<00:27:44.159> I'd<00:27:44.520> love 00:27:44.690 --> 00:27:44.700 align:start position:0% not yet but I I would love that I'd love 00:27:44.700 --> 00:27:48.130 align:start position:0% not yet but I I would love that I'd love to<00:27:44.820> hear<00:27:45.000> your<00:27:45.179> thoughts<00:27:45.480> on<00:27:45.600> at<00:27:45.840> some<00:27:46.020> point 00:27:48.130 --> 00:27:48.140 align:start position:0% to hear your thoughts on at some point 00:27:48.140 --> 00:27:50.450 align:start position:0% to hear your thoughts on at some point I'm<00:27:49.140> kind<00:27:49.260> of<00:27:49.380> practical<00:27:49.740> on<00:27:50.039> the<00:27:50.159> side<00:27:50.279> of 00:27:50.450 --> 00:27:50.460 align:start position:0% I'm kind of practical on the side of 00:27:50.460 --> 00:27:51.649 align:start position:0% I'm kind of practical on the side of things<00:27:50.520> as<00:27:50.820> far<00:27:50.940> as<00:27:51.059> what<00:27:51.179> that<00:27:51.360> should<00:27:51.539> look 00:27:51.649 --> 00:27:51.659 align:start position:0% things as far as what that should look 00:27:51.659 --> 00:27:53.210 align:start position:0% things as far as what that should look like<00:27:51.779> and<00:27:52.020> what<00:27:52.140> colorful<00:27:52.559> even<00:27:52.799> yeah<00:27:53.039> please 00:27:53.210 --> 00:27:53.220 align:start position:0% like and what colorful even yeah please 00:27:53.220 --> 00:27:55.250 align:start position:0% like and what colorful even yeah please go<00:27:53.580> ahead<00:27:53.760> sorry 00:27:55.250 --> 00:27:55.260 align:start position:0% go ahead sorry 00:27:55.260 --> 00:27:56.630 align:start position:0% go ahead sorry um<00:27:55.320> yeah<00:27:55.559> I<00:27:55.740> don't<00:27:55.860> have<00:27:55.980> any<00:27:56.220> particular 00:27:56.630 --> 00:27:56.640 align:start position:0% um yeah I don't have any particular 00:27:56.640 --> 00:27:59.630 align:start position:0% um yeah I don't have any particular thoughts<00:27:57.179> just<00:27:57.480> that<00:27:57.840> I<00:27:58.380> think<00:27:58.559> current<00:27:59.100> plans 00:27:59.630 --> 00:27:59.640 align:start position:0% thoughts just that I think current plans 00:27:59.640 --> 00:28:03.590 align:start position:0% thoughts just that I think current plans are<00:27:59.940> to<00:28:00.620> expire<00:28:01.620> estate<00:28:01.860> after<00:28:02.580> a<00:28:03.000> year<00:28:03.299> or<00:28:03.480> so 00:28:03.590 --> 00:28:03.600 align:start position:0% are to expire estate after a year or so 00:28:03.600 --> 00:28:06.230 align:start position:0% are to expire estate after a year or so yeah 00:28:06.230 --> 00:28:06.240 align:start position:0% 00:28:06.240 --> 00:28:07.970 align:start position:0% um<00:28:06.299> you<00:28:06.840> know<00:28:06.900> some<00:28:07.140> other<00:28:07.260> way<00:28:07.500> to<00:28:07.679> get<00:28:07.799> the 00:28:07.970 --> 00:28:07.980 align:start position:0% um you know some other way to get the 00:28:07.980 --> 00:28:10.490 align:start position:0% um you know some other way to get the state<00:28:08.220> I<00:28:08.820> my<00:28:09.360> understanding<00:28:09.779> is<00:28:09.960> there<00:28:10.320> will 00:28:10.490 --> 00:28:10.500 align:start position:0% state I my understanding is there will 00:28:10.500 --> 00:28:11.990 align:start position:0% state I my understanding is there will be<00:28:10.620> I<00:28:10.860> mean<00:28:10.980> zero<00:28:11.400> knowledge<00:28:11.520> proofs<00:28:11.820> that 00:28:11.990 --> 00:28:12.000 align:start position:0% be I mean zero knowledge proofs that 00:28:12.000 --> 00:28:13.190 align:start position:0% be I mean zero knowledge proofs that we'll<00:28:12.059> be<00:28:12.179> able<00:28:12.299> to<00:28:12.419> construct<00:28:12.779> that<00:28:12.960> and 00:28:13.190 --> 00:28:13.200 align:start position:0% we'll be able to construct that and 00:28:13.200 --> 00:28:14.810 align:start position:0% we'll be able to construct that and prove<00:28:13.500> that<00:28:13.559> that's<00:28:13.740> true<00:28:14.460> um<00:28:14.520> but<00:28:14.700> then 00:28:14.810 --> 00:28:14.820 align:start position:0% prove that that's true um but then 00:28:14.820 --> 00:28:16.070 align:start position:0% prove that that's true um but then you'll<00:28:15.000> also<00:28:15.299> have 00:28:16.070 --> 00:28:16.080 align:start position:0% you'll also have 00:28:16.080 --> 00:28:17.750 align:start position:0% you'll also have um<00:28:16.140> so<00:28:16.740> you're<00:28:17.039> kind<00:28:17.159> of<00:28:17.279> using<00:28:17.460> the<00:28:17.580> same 00:28:17.750 --> 00:28:17.760 align:start position:0% um so you're kind of using the same 00:28:17.760 --> 00:28:19.250 align:start position:0% um so you're kind of using the same different<00:28:18.000> different<00:28:18.299> technology<00:28:18.779> but<00:28:19.020> I'm 00:28:19.250 --> 00:28:19.260 align:start position:0% different different technology but I'm 00:28:19.260 --> 00:28:20.149 align:start position:0% different different technology but I'm not<00:28:19.380> going<00:28:19.500> to<00:28:19.559> speak<00:28:19.679> to<00:28:19.740> you<00:28:19.799> about<00:28:19.919> a<00:28:20.039> turn 00:28:20.149 --> 00:28:20.159 align:start position:0% not going to speak to you about a turn 00:28:20.159 --> 00:28:21.590 align:start position:0% not going to speak to you about a turn on<00:28:20.460> what<00:28:20.700> I<00:28:20.820> don't<00:28:20.880> know<00:28:21.000> it's<00:28:21.120> not<00:28:21.240> about<00:28:21.360> it's 00:28:21.590 --> 00:28:21.600 align:start position:0% on what I don't know it's not about it's 00:28:21.600 --> 00:28:23.090 align:start position:0% on what I don't know it's not about it's a<00:28:21.779> great<00:28:21.900> question<00:28:22.080> though 00:28:23.090 --> 00:28:23.100 align:start position:0% a great question though 00:28:23.100 --> 00:28:24.289 align:start position:0% a great question though um<00:28:23.220> I'll<00:28:23.340> definitely<00:28:23.640> I<00:28:23.820> can<00:28:23.880> look<00:28:23.940> into<00:28:24.059> it 00:28:24.289 --> 00:28:24.299 align:start position:0% um I'll definitely I can look into it 00:28:24.299 --> 00:28:27.260 align:start position:0% um I'll definitely I can look into it and<00:28:24.360> get<00:28:24.480> in<00:28:24.600> touch<00:28:24.720> with<00:28:24.840> you<00:28:24.960> about<00:28:25.080> it