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:16.090 align:start position:0% [Music] 00:00:16.090 --> 00:00:16.100 align:start position:0% 00:00:16.100 --> 00:00:18.349 align:start position:0% So<00:00:17.100> today<00:00:17.580> we're<00:00:17.820> going<00:00:18.000> to<00:00:18.119> talk<00:00:18.240> about 00:00:18.349 --> 00:00:18.359 align:start position:0% So today we're going to talk about 00:00:18.359 --> 00:00:20.810 align:start position:0% So today we're going to talk about storage<00:00:18.720> proofs<00:00:19.260> I<00:00:19.680> want<00:00:19.800> to<00:00:19.920> introduce<00:00:20.340> this 00:00:20.810 --> 00:00:20.820 align:start position:0% storage proofs I want to introduce this 00:00:20.820 --> 00:00:23.570 align:start position:0% storage proofs I want to introduce this app 00:00:23.570 --> 00:00:23.580 align:start position:0% 00:00:23.580 --> 00:00:24.650 align:start position:0% yes 00:00:24.650 --> 00:00:24.660 align:start position:0% yes 00:00:24.660 --> 00:00:27.109 align:start position:0% yes uh<00:00:25.380> I'm<00:00:25.680> gonna<00:00:25.800> present<00:00:26.279> you<00:00:26.400> storage<00:00:26.640> proofs 00:00:27.109 --> 00:00:27.119 align:start position:0% uh I'm gonna present you storage proofs 00:00:27.119 --> 00:00:29.029 align:start position:0% uh I'm gonna present you storage proofs and<00:00:27.240> explain<00:00:27.480> why<00:00:27.840> they're<00:00:28.140> cool<00:00:28.380> how<00:00:28.680> to<00:00:28.800> work 00:00:29.029 --> 00:00:29.039 align:start position:0% and explain why they're cool how to work 00:00:29.039 --> 00:00:31.250 align:start position:0% and explain why they're cool how to work with<00:00:29.340> them<00:00:29.580> why<00:00:30.119> you<00:00:30.359> need<00:00:30.480> tooling<00:00:30.900> to<00:00:31.080> work 00:00:31.250 --> 00:00:31.260 align:start position:0% with them why you need tooling to work 00:00:31.260 --> 00:00:34.670 align:start position:0% with them why you need tooling to work with<00:00:31.500> them<00:00:32.180> and<00:00:33.180> yeah<00:00:33.540> a<00:00:34.079> bunch<00:00:34.200> of<00:00:34.380> other 00:00:34.670 --> 00:00:34.680 align:start position:0% with them and yeah a bunch of other 00:00:34.680 --> 00:00:37.310 align:start position:0% with them and yeah a bunch of other things<00:00:35.040> why<00:00:35.399> is<00:00:35.520> it<00:00:35.700> even<00:00:35.820> possible<00:00:36.239> all<00:00:37.140> the 00:00:37.310 --> 00:00:37.320 align:start position:0% things why is it even possible all the 00:00:37.320 --> 00:00:40.069 align:start position:0% things why is it even possible all the complexities<00:00:37.739> behind<00:00:38.219> the<00:00:38.399> trade-offs<00:00:39.300> and 00:00:40.069 --> 00:00:40.079 align:start position:0% complexities behind the trade-offs and 00:00:40.079 --> 00:00:42.650 align:start position:0% complexities behind the trade-offs and so<00:00:40.200> on<00:00:40.379> so<00:00:40.620> a<00:00:41.399> few<00:00:41.579> words<00:00:41.700> about<00:00:41.879> storage<00:00:42.180> Crews 00:00:42.650 --> 00:00:42.660 align:start position:0% so on so a few words about storage Crews 00:00:42.660 --> 00:00:44.389 align:start position:0% so on so a few words about storage Crews well<00:00:43.200> I<00:00:43.320> really<00:00:43.500> believe<00:00:43.739> that<00:00:43.920> they<00:00:44.100> are<00:00:44.219> cool 00:00:44.389 --> 00:00:44.399 align:start position:0% well I really believe that they are cool 00:00:44.399 --> 00:00:48.229 align:start position:0% well I really believe that they are cool especially<00:00:45.500> nowadays<00:00:46.500> so<00:00:47.280> my<00:00:47.460> thesis<00:00:47.879> is<00:00:48.120> that 00:00:48.229 --> 00:00:48.239 align:start position:0% especially nowadays so my thesis is that 00:00:48.239 --> 00:00:51.229 align:start position:0% especially nowadays so my thesis is that ethereum<00:00:48.719> is<00:00:48.960> pretty<00:00:49.500> sharded<00:00:49.980> nowadays<00:00:50.520> and 00:00:51.229 --> 00:00:51.239 align:start position:0% ethereum is pretty sharded nowadays and 00:00:51.239 --> 00:00:53.750 align:start position:0% ethereum is pretty sharded nowadays and with<00:00:51.420> storage<00:00:51.660> rules<00:00:52.140> we<00:00:52.440> can<00:00:52.620> essentially 00:00:53.750 --> 00:00:53.760 align:start position:0% with storage rules we can essentially 00:00:53.760 --> 00:00:57.110 align:start position:0% with storage rules we can essentially read<00:00:54.600> the<00:00:55.140> state<00:00:55.320> in<00:00:55.920> a<00:00:56.160> almost<00:00:56.579> synchronous 00:00:57.110 --> 00:00:57.120 align:start position:0% read the state in a almost synchronous 00:00:57.120 --> 00:00:59.569 align:start position:0% read the state in a almost synchronous manner<00:00:57.600> which<00:00:58.079> is<00:00:58.260> a<00:00:58.680> pretty<00:00:58.980> pretty<00:00:59.280> nice 00:00:59.569 --> 00:00:59.579 align:start position:0% manner which is a pretty pretty nice 00:00:59.579 --> 00:01:00.850 align:start position:0% manner which is a pretty pretty nice thing<00:00:59.820> to<00:01:00.059> do 00:01:00.850 --> 00:01:00.860 align:start position:0% thing to do 00:01:00.860 --> 00:01:04.490 align:start position:0% thing to do given<00:01:01.860> the<00:01:02.340> circumstances 00:01:04.490 --> 00:01:04.500 align:start position:0% given the circumstances 00:01:04.500 --> 00:01:07.190 align:start position:0% given the circumstances um<00:01:04.559> yeah<00:01:05.460> and<00:01:05.939> maybe<00:01:06.180> also<00:01:06.780> let<00:01:06.960> me<00:01:07.080> explain 00:01:07.190 --> 00:01:07.200 align:start position:0% um yeah and maybe also let me explain 00:01:07.200 --> 00:01:09.890 align:start position:0% um yeah and maybe also let me explain why<00:01:07.500> is<00:01:07.680> it<00:01:07.799> even<00:01:07.920> possible<00:01:08.340> so<00:01:09.060> story<00:01:09.360> is 00:01:09.890 --> 00:01:09.900 align:start position:0% why is it even possible so story is 00:01:09.900 --> 00:01:11.390 align:start position:0% why is it even possible so story is essentially<00:01:10.200> this<00:01:10.439> idea<00:01:10.680> that<00:01:10.979> the<00:01:11.159> entire 00:01:11.390 --> 00:01:11.400 align:start position:0% essentially this idea that the entire 00:01:11.400 --> 00:01:13.130 align:start position:0% essentially this idea that the entire state<00:01:11.700> is<00:01:12.000> committed<00:01:12.299> in<00:01:12.420> a<00:01:12.600> cryptographic 00:01:13.130 --> 00:01:13.140 align:start position:0% state is committed in a cryptographic 00:01:13.140 --> 00:01:16.070 align:start position:0% state is committed in a cryptographic manner<00:01:14.000> using<00:01:15.000> some<00:01:15.180> data<00:01:15.659> structure<00:01:15.960> like 00:01:16.070 --> 00:01:16.080 align:start position:0% manner using some data structure like 00:01:16.080 --> 00:01:17.929 align:start position:0% manner using some data structure like Miracle<00:01:16.439> trees<00:01:16.680> Marco<00:01:17.159> Patricia<00:01:17.520> trees<00:01:17.820> and 00:01:17.929 --> 00:01:17.939 align:start position:0% Miracle trees Marco Patricia trees and 00:01:17.939 --> 00:01:20.570 align:start position:0% Miracle trees Marco Patricia trees and so<00:01:18.060> on<00:01:18.200> and<00:01:19.200> yeah<00:01:19.320> we<00:01:19.500> can<00:01:19.680> essentially<00:01:20.040> verify 00:01:20.570 --> 00:01:20.580 align:start position:0% so on and yeah we can essentially verify 00:01:20.580 --> 00:01:23.870 align:start position:0% so on and yeah we can essentially verify any<00:01:21.240> specific<00:01:21.720> piece<00:01:22.140> of<00:01:22.259> State<00:01:22.439> at<00:01:23.340> any<00:01:23.640> point 00:01:23.870 --> 00:01:23.880 align:start position:0% any specific piece of State at any point 00:01:23.880 --> 00:01:27.170 align:start position:0% any specific piece of State at any point in<00:01:24.060> time<00:01:24.299> on<00:01:24.900> any<00:01:25.320> domain<00:01:25.979> which<00:01:26.759> is<00:01:26.939> pretty 00:01:27.170 --> 00:01:27.180 align:start position:0% in time on any domain which is pretty 00:01:27.180 --> 00:01:29.090 align:start position:0% in time on any domain which is pretty nice<00:01:27.420> and<00:01:27.659> does<00:01:27.900> introduce<00:01:28.320> additional<00:01:28.740> trust 00:01:29.090 --> 00:01:29.100 align:start position:0% nice and does introduce additional trust 00:01:29.100 --> 00:01:30.710 align:start position:0% nice and does introduce additional trust assumptions<00:01:29.520> you<00:01:30.060> just<00:01:30.240> rely<00:01:30.540> on<00:01:30.659> the 00:01:30.710 --> 00:01:30.720 align:start position:0% assumptions you just rely on the 00:01:30.720 --> 00:01:32.649 align:start position:0% assumptions you just rely on the security<00:01:30.900> of<00:01:31.259> like<00:01:31.380> the<00:01:31.560> base<00:01:31.920> chain 00:01:32.649 --> 00:01:32.659 align:start position:0% security of like the base chain 00:01:32.659 --> 00:01:36.170 align:start position:0% security of like the base chain so<00:01:33.659> yeah<00:01:33.840> that's<00:01:34.200> like<00:01:34.560> storage<00:01:35.040> proofs<00:01:35.579> tldr 00:01:36.170 --> 00:01:36.180 align:start position:0% so yeah that's like storage proofs tldr 00:01:36.180 --> 00:01:37.969 align:start position:0% so yeah that's like storage proofs tldr where<00:01:36.540> they're<00:01:36.780> cool 00:01:37.969 --> 00:01:37.979 align:start position:0% where they're cool 00:01:37.979 --> 00:01:41.929 align:start position:0% where they're cool now<00:01:38.700> a<00:01:39.000> bit<00:01:39.119> of<00:01:39.299> like<00:01:39.479> sponsored<00:01:40.079> section<00:01:40.380> of 00:01:41.929 --> 00:01:41.939 align:start position:0% now a bit of like sponsored section of 00:01:41.939 --> 00:01:44.630 align:start position:0% now a bit of like sponsored section of sponsored<00:01:42.659> section<00:01:43.020> so<00:01:43.439> uh<00:01:43.860> what<00:01:44.220> we're<00:01:44.460> doing 00:01:44.630 --> 00:01:44.640 align:start position:0% sponsored section so uh what we're doing 00:01:44.640 --> 00:01:48.230 align:start position:0% sponsored section so uh what we're doing at<00:01:44.820> harvardus<00:01:45.479> so<00:01:46.259> our<00:01:46.860> like<00:01:47.159> goal<00:01:47.579> is<00:01:47.700> to<00:01:48.000> make 00:01:48.230 --> 00:01:48.240 align:start position:0% at harvardus so our like goal is to make 00:01:48.240 --> 00:01:51.410 align:start position:0% at harvardus so our like goal is to make smart<00:01:49.140> contracts<00:01:49.560> software<00:01:49.979> in<00:01:50.280> a<00:01:50.399> way<00:01:50.520> by 00:01:51.410 --> 00:01:51.420 align:start position:0% smart contracts software in a way by 00:01:51.420 --> 00:01:54.289 align:start position:0% smart contracts software in a way by providing<00:01:52.079> access<00:01:52.380> to<00:01:52.619> historical<00:01:53.100> state 00:01:54.289 --> 00:01:54.299 align:start position:0% providing access to historical state 00:01:54.299 --> 00:01:57.170 align:start position:0% providing access to historical state uh<00:01:54.899> we<00:01:55.140> like<00:01:55.560> I<00:01:55.799> said<00:01:55.920> might<00:01:56.280> as<00:01:56.579> this<00:01:56.820> is<00:01:56.939> that 00:01:57.170 --> 00:01:57.180 align:start position:0% uh we like I said might as this is that 00:01:57.180 --> 00:01:58.969 align:start position:0% uh we like I said might as this is that ethereum<00:01:57.780> is<00:01:57.899> pretty<00:01:58.079> short<00:01:58.320> that<00:01:58.500> nowadays 00:01:58.969 --> 00:01:58.979 align:start position:0% ethereum is pretty short that nowadays 00:01:58.979 --> 00:02:01.310 align:start position:0% ethereum is pretty short that nowadays we<00:01:59.220> want<00:01:59.340> to<00:01:59.520> unchart<00:01:59.880> it<00:02:00.180> by<00:02:00.780> using<00:02:01.140> storage 00:02:01.310 --> 00:02:01.320 align:start position:0% we want to unchart it by using storage 00:02:01.320 --> 00:02:04.429 align:start position:0% we want to unchart it by using storage Crews<00:02:01.920> and<00:02:02.820> we<00:02:03.240> want<00:02:03.360> to<00:02:03.479> enable<00:02:03.720> synchronous 00:02:04.429 --> 00:02:04.439 align:start position:0% Crews and we want to enable synchronous 00:02:04.439 --> 00:02:06.350 align:start position:0% Crews and we want to enable synchronous data<00:02:04.799> reads<00:02:05.100> because<00:02:05.219> today<00:02:05.460> we<00:02:05.759> do<00:02:06.000> not<00:02:06.119> have 00:02:06.350 --> 00:02:06.360 align:start position:0% data reads because today we do not have 00:02:06.360 --> 00:02:08.990 align:start position:0% data reads because today we do not have really<00:02:06.659> nice<00:02:07.320> ways<00:02:07.740> to<00:02:07.860> make<00:02:08.160> synchronous 00:02:08.990 --> 00:02:09.000 align:start position:0% really nice ways to make synchronous 00:02:09.000 --> 00:02:11.029 align:start position:0% really nice ways to make synchronous data<00:02:09.360> access<00:02:09.479> without<00:02:09.780> introducing<00:02:10.500> New 00:02:11.029 --> 00:02:11.039 align:start position:0% data access without introducing New 00:02:11.039 --> 00:02:13.610 align:start position:0% data access without introducing New State<00:02:11.340> uh<00:02:11.640> new<00:02:12.000> trust<00:02:12.239> assumptions<00:02:12.660> so<00:02:13.500> yeah 00:02:13.610 --> 00:02:13.620 align:start position:0% State uh new trust assumptions so yeah 00:02:13.620 --> 00:02:15.589 align:start position:0% State uh new trust assumptions so yeah that's<00:02:13.860> we<00:02:14.099> do<00:02:14.220> and<00:02:14.400> how<00:02:14.580> we<00:02:14.700> achieve<00:02:15.000> that<00:02:15.180> we 00:02:15.589 --> 00:02:15.599 align:start position:0% that's we do and how we achieve that we 00:02:15.599 --> 00:02:17.449 align:start position:0% that's we do and how we achieve that we achieved<00:02:16.020> it<00:02:16.080> by<00:02:16.260> using<00:02:16.800> obviously<00:02:17.220> storage 00:02:17.449 --> 00:02:17.459 align:start position:0% achieved it by using obviously storage 00:02:17.459 --> 00:02:21.770 align:start position:0% achieved it by using obviously storage proofs<00:02:18.000> we<00:02:18.300> use<00:02:18.540> snark<00:02:18.840> Starks<00:02:19.440> and<00:02:19.980> NPC<00:02:20.780> I 00:02:21.770 --> 00:02:21.780 align:start position:0% proofs we use snark Starks and NPC I 00:02:21.780 --> 00:02:23.690 align:start position:0% proofs we use snark Starks and NPC I will<00:02:21.900> get<00:02:22.080> why<00:02:22.680> we<00:02:22.920> even<00:02:23.099> use<00:02:23.280> all<00:02:23.520> this 00:02:23.690 --> 00:02:23.700 align:start position:0% will get why we even use all this 00:02:23.700 --> 00:02:26.030 align:start position:0% will get why we even use all this tooling<00:02:24.120> but<00:02:24.840> first<00:02:25.200> a<00:02:25.500> few<00:02:25.620> words<00:02:25.800> about 00:02:26.030 --> 00:02:26.040 align:start position:0% tooling but first a few words about 00:02:26.040 --> 00:02:28.190 align:start position:0% tooling but first a few words about storage<00:02:26.340> rules<00:02:26.819> what<00:02:27.000> these<00:02:27.300> are<00:02:27.420> and<00:02:27.720> and<00:02:27.959> so 00:02:28.190 --> 00:02:28.200 align:start position:0% storage rules what these are and and so 00:02:28.200 --> 00:02:29.690 align:start position:0% storage rules what these are and and so on 00:02:29.690 --> 00:02:29.700 align:start position:0% on 00:02:29.700 --> 00:02:32.089 align:start position:0% on it's<00:02:30.300> so<00:02:30.480> tricky<00:02:30.840> actually<00:02:31.020> I<00:02:31.379> I<00:02:31.680> need<00:02:31.860> to<00:02:31.980> be 00:02:32.089 --> 00:02:32.099 align:start position:0% it's so tricky actually I I need to be 00:02:32.099 --> 00:02:34.670 align:start position:0% it's so tricky actually I I need to be multitasking<00:02:33.000> okay<00:02:33.599> so<00:02:33.959> uh<00:02:34.260> what<00:02:34.440> we're<00:02:34.560> gonna 00:02:34.670 --> 00:02:34.680 align:start position:0% multitasking okay so uh what we're gonna 00:02:34.680 --> 00:02:37.729 align:start position:0% multitasking okay so uh what we're gonna cover<00:02:34.980> in<00:02:35.520> today's<00:02:35.819> Workshop<00:02:36.360> so<00:02:37.260> all<00:02:37.560> the 00:02:37.729 --> 00:02:37.739 align:start position:0% cover in today's Workshop so all the 00:02:37.739 --> 00:02:39.350 align:start position:0% cover in today's Workshop so all the basics<00:02:38.099> required<00:02:38.700> to<00:02:38.819> like<00:02:39.060> understand 00:02:39.350 --> 00:02:39.360 align:start position:0% basics required to like understand 00:02:39.360 --> 00:02:42.949 align:start position:0% basics required to like understand properly<00:02:40.260> this<00:02:41.040> primitive<00:02:41.519> how<00:02:42.360> to<00:02:42.480> like<00:02:42.660> work 00:02:42.949 --> 00:02:42.959 align:start position:0% properly this primitive how to like work 00:02:42.959 --> 00:02:45.229 align:start position:0% properly this primitive how to like work with<00:02:43.200> it<00:02:43.379> uh<00:02:44.160> how<00:02:44.340> you<00:02:44.459> can<00:02:44.580> generate<00:02:44.940> these 00:02:45.229 --> 00:02:45.239 align:start position:0% with it uh how you can generate these 00:02:45.239 --> 00:02:47.509 align:start position:0% with it uh how you can generate these proofs<00:02:45.480> why<00:02:45.720> they're<00:02:45.959> pretty<00:02:46.260> useful<00:02:46.620> and<00:02:47.280> how 00:02:47.509 --> 00:02:47.519 align:start position:0% proofs why they're pretty useful and how 00:02:47.519 --> 00:02:50.330 align:start position:0% proofs why they're pretty useful and how actually<00:02:47.760> you<00:02:48.180> can<00:02:48.440> access<00:02:49.440> this<00:02:49.860> commitments 00:02:50.330 --> 00:02:50.340 align:start position:0% actually you can access this commitments 00:02:50.340 --> 00:02:52.009 align:start position:0% actually you can access this commitments I'll<00:02:50.459> get<00:02:50.640> later<00:02:50.819> what<00:02:51.239> we<00:02:51.720> call<00:02:51.840> the 00:02:52.009 --> 00:02:52.019 align:start position:0% I'll get later what we call the 00:02:52.019 --> 00:02:55.490 align:start position:0% I'll get later what we call the commitment<00:02:52.459> in<00:02:53.459> a<00:02:53.700> process<00:02:54.360> manner 00:02:55.490 --> 00:02:55.500 align:start position:0% commitment in a process manner 00:02:55.500 --> 00:02:58.309 align:start position:0% commitment in a process manner and<00:02:56.220> how<00:02:56.459> we<00:02:56.580> make<00:02:56.819> smart<00:02:57.060> contracts<00:02:57.660> software 00:02:58.309 --> 00:02:58.319 align:start position:0% and how we make smart contracts software 00:02:58.319 --> 00:03:02.270 align:start position:0% and how we make smart contracts software and<00:02:58.680> enable<00:02:59.180> historical<00:03:00.180> data<00:03:00.840> reads 00:03:02.270 --> 00:03:02.280 align:start position:0% and enable historical data reads 00:03:02.280 --> 00:03:04.190 align:start position:0% and enable historical data reads cool<00:03:02.940> so 00:03:04.190 --> 00:03:04.200 align:start position:0% cool so 00:03:04.200 --> 00:03:06.830 align:start position:0% cool so um 00:03:06.830 --> 00:03:06.840 align:start position:0% 00:03:06.840 --> 00:03:09.949 align:start position:0% it's<00:03:07.379> pretty<00:03:07.620> that's<00:03:08.400> pretty<00:03:08.640> tricky 00:03:09.949 --> 00:03:09.959 align:start position:0% it's pretty that's pretty tricky 00:03:09.959 --> 00:03:12.589 align:start position:0% it's pretty that's pretty tricky so<00:03:10.620> about<00:03:11.159> the<00:03:11.459> background<00:03:11.760> that<00:03:12.180> I<00:03:12.360> want<00:03:12.480> you 00:03:12.589 --> 00:03:12.599 align:start position:0% so about the background that I want you 00:03:12.599 --> 00:03:14.690 align:start position:0% so about the background that I want you to<00:03:12.840> have<00:03:13.019> for<00:03:13.319> this<00:03:13.440> Workshop<00:03:13.860> so<00:03:14.340> we're<00:03:14.519> gonna 00:03:14.690 --> 00:03:14.700 align:start position:0% to have for this Workshop so we're gonna 00:03:14.700 --> 00:03:17.930 align:start position:0% to have for this Workshop so we're gonna like<00:03:15.300> start<00:03:15.599> from<00:03:16.019> the<00:03:16.620> biggest<00:03:16.860> Basics<00:03:17.400> so 00:03:17.930 --> 00:03:17.940 align:start position:0% like start from the biggest Basics so 00:03:17.940 --> 00:03:19.610 align:start position:0% like start from the biggest Basics so what<00:03:18.120> is<00:03:18.239> the<00:03:18.360> hashing<00:03:18.720> function<00:03:19.019> just<00:03:19.319> a<00:03:19.500> very 00:03:19.610 --> 00:03:19.620 align:start position:0% what is the hashing function just a very 00:03:19.620 --> 00:03:21.710 align:start position:0% what is the hashing function just a very quick<00:03:19.800> reminder<00:03:20.099> I<00:03:20.940> hope<00:03:21.060> it<00:03:21.239> will<00:03:21.360> take<00:03:21.480> less 00:03:21.710 --> 00:03:21.720 align:start position:0% quick reminder I hope it will take less 00:03:21.720 --> 00:03:24.110 align:start position:0% quick reminder I hope it will take less than<00:03:21.900> a<00:03:22.080> minute<00:03:22.280> uh<00:03:23.280> like<00:03:23.519> generalized 00:03:24.110 --> 00:03:24.120 align:start position:0% than a minute uh like generalized 00:03:24.120 --> 00:03:26.750 align:start position:0% than a minute uh like generalized blockchain<00:03:24.420> Anatomy<00:03:25.019> how<00:03:25.680> I<00:03:25.860> ethereum<00:03:26.340> header 00:03:26.750 --> 00:03:26.760 align:start position:0% blockchain Anatomy how I ethereum header 00:03:26.760 --> 00:03:29.149 align:start position:0% blockchain Anatomy how I ethereum header looks<00:03:27.300> like<00:03:27.420> why<00:03:27.780> ethereum<00:03:28.200> they're<00:03:28.739> not<00:03:28.980> like 00:03:29.149 --> 00:03:29.159 align:start position:0% looks like why ethereum they're not like 00:03:29.159 --> 00:03:31.790 align:start position:0% looks like why ethereum they're not like pretty<00:03:29.519> on<00:03:30.060> only<00:03:30.420> like<00:03:30.780> ethereum<00:03:31.260> focused 00:03:31.790 --> 00:03:31.800 align:start position:0% pretty on only like ethereum focused 00:03:31.800 --> 00:03:33.770 align:start position:0% pretty on only like ethereum focused however<00:03:32.459> I<00:03:32.879> think<00:03:33.000> that<00:03:33.120> for<00:03:33.300> the<00:03:33.480> sake<00:03:33.659> of 00:03:33.770 --> 00:03:33.780 align:start position:0% however I think that for the sake of 00:03:33.780 --> 00:03:35.210 align:start position:0% however I think that for the sake of this<00:03:33.959> Workshop<00:03:34.260> it's<00:03:34.560> the<00:03:34.800> best<00:03:34.920> to<00:03:35.099> like 00:03:35.210 --> 00:03:35.220 align:start position:0% this Workshop it's the best to like 00:03:35.220 --> 00:03:37.670 align:start position:0% this Workshop it's the best to like present<00:03:35.459> on<00:03:35.640> this<00:03:35.760> concrete<00:03:36.060> example<00:03:36.959> Miracle 00:03:37.670 --> 00:03:37.680 align:start position:0% present on this concrete example Miracle 00:03:37.680 --> 00:03:39.649 align:start position:0% present on this concrete example Miracle trees<00:03:38.040> explain<00:03:38.220> me<00:03:38.519> like<00:03:38.640> on<00:03:38.819> five<00:03:39.060> I<00:03:39.480> will 00:03:39.649 --> 00:03:39.659 align:start position:0% trees explain me like on five I will 00:03:39.659 --> 00:03:41.330 align:start position:0% trees explain me like on five I will just<00:03:39.900> quickly 00:03:41.330 --> 00:03:41.340 align:start position:0% just quickly 00:03:41.340 --> 00:03:44.630 align:start position:0% just quickly explain<00:03:41.819> the<00:03:42.239> idea<00:03:42.540> how<00:03:42.959> it<00:03:43.140> works<00:03:43.500> and<00:03:44.280> what 00:03:44.630 --> 00:03:44.640 align:start position:0% explain the idea how it works and what 00:03:44.640 --> 00:03:46.490 align:start position:0% explain the idea how it works and what is<00:03:44.760> America<00:03:44.940> Patricia<00:03:45.599> tree<00:03:45.780> without<00:03:46.140> really 00:03:46.490 --> 00:03:46.500 align:start position:0% is America Patricia tree without really 00:03:46.500 --> 00:03:48.949 align:start position:0% is America Patricia tree without really going<00:03:46.680> too<00:03:46.860> much<00:03:46.980> into<00:03:47.159> digitals 00:03:48.949 --> 00:03:48.959 align:start position:0% going too much into digitals 00:03:48.959 --> 00:03:53.030 align:start position:0% going too much into digitals um yeah<00:03:49.400> finally<00:03:50.400> no<00:03:51.299> not<00:03:51.599> finally<00:03:51.959> uh<00:03:52.860> the 00:03:53.030 --> 00:03:53.040 align:start position:0% um yeah finally no not finally uh the 00:03:53.040 --> 00:03:55.610 align:start position:0% um yeah finally no not finally uh the anatomy<00:03:53.519> the<00:03:53.760> ethereum<00:03:54.180> state 00:03:55.610 --> 00:03:55.620 align:start position:0% anatomy the ethereum state 00:03:55.620 --> 00:03:57.830 align:start position:0% anatomy the ethereum state it's<00:03:55.799> pretty<00:03:56.159> important<00:03:56.819> to<00:03:57.180> like<00:03:57.360> deal<00:03:57.540> with 00:03:57.830 --> 00:03:57.840 align:start position:0% it's pretty important to like deal with 00:03:57.840 --> 00:04:00.470 align:start position:0% it's pretty important to like deal with this<00:03:58.080> uh<00:03:58.379> with<00:03:59.159> this<00:03:59.280> primitive<00:03:59.700> and<00:04:00.180> finally 00:04:00.470 --> 00:04:00.480 align:start position:0% this uh with this primitive and finally 00:04:00.480 --> 00:04:03.289 align:start position:0% this uh with this primitive and finally how<00:04:00.840> to<00:04:00.959> deal<00:04:01.140> with<00:04:01.319> the<00:04:01.440> storage<00:04:01.620> layout 00:04:03.289 --> 00:04:03.299 align:start position:0% how to deal with the storage layout 00:04:03.299 --> 00:04:06.589 align:start position:0% how to deal with the storage layout cool<00:04:03.959> so<00:04:04.379> touching<00:04:05.159> function<00:04:05.459> essential<00:04:06.420> is 00:04:06.589 --> 00:04:06.599 align:start position:0% cool so touching function essential is 00:04:06.599 --> 00:04:08.270 align:start position:0% cool so touching function essential is this<00:04:06.780> idea 00:04:08.270 --> 00:04:08.280 align:start position:0% this idea 00:04:08.280 --> 00:04:10.429 align:start position:0% this idea essentially<00:04:09.060> it's<00:04:09.239> this<00:04:09.480> idea<00:04:09.780> that<00:04:10.080> I<00:04:10.379> can 00:04:10.429 --> 00:04:10.439 align:start position:0% essentially it's this idea that I can 00:04:10.439 --> 00:04:13.190 align:start position:0% essentially it's this idea that I can have<00:04:10.680> a<00:04:11.159> function<00:04:11.580> that<00:04:11.939> takes<00:04:12.120> some<00:04:12.299> input 00:04:13.190 --> 00:04:13.200 align:start position:0% have a function that takes some input 00:04:13.200 --> 00:04:15.849 align:start position:0% have a function that takes some input of<00:04:13.739> any<00:04:13.920> size<00:04:14.159> and<00:04:14.580> it<00:04:14.760> always<00:04:15.000> always<00:04:15.480> return 00:04:15.849 --> 00:04:15.859 align:start position:0% of any size and it always always return 00:04:15.859 --> 00:04:18.650 align:start position:0% of any size and it always always return an<00:04:16.859> output<00:04:17.160> of<00:04:17.400> a<00:04:17.519> fixed<00:04:17.820> size<00:04:17.940> and<00:04:18.239> now<00:04:18.419> what's 00:04:18.650 --> 00:04:18.660 align:start position:0% an output of a fixed size and now what's 00:04:18.660 --> 00:04:21.949 align:start position:0% an output of a fixed size and now what's also<00:04:19.019> important<00:04:19.400> there<00:04:20.400> is<00:04:20.519> no<00:04:20.940> input<00:04:21.359> there 00:04:21.949 --> 00:04:21.959 align:start position:0% also important there is no input there 00:04:21.959 --> 00:04:23.510 align:start position:0% also important there is no input there are<00:04:22.139> no<00:04:22.199> two<00:04:22.380> inputs<00:04:22.740> that<00:04:22.860> will<00:04:23.040> generate<00:04:23.340> the 00:04:23.510 --> 00:04:23.520 align:start position:0% are no two inputs that will generate the 00:04:23.520 --> 00:04:26.870 align:start position:0% are no two inputs that will generate the same<00:04:23.699> output<00:04:24.060> and<00:04:24.960> you<00:04:25.259> cannot<00:04:25.500> reverse<00:04:25.979> the 00:04:26.870 --> 00:04:26.880 align:start position:0% same output and you cannot reverse the 00:04:26.880 --> 00:04:28.490 align:start position:0% same output and you cannot reverse the hashing<00:04:27.300> function<00:04:27.540> so<00:04:27.720> it<00:04:27.840> means<00:04:28.020> that<00:04:28.139> given 00:04:28.490 --> 00:04:28.500 align:start position:0% hashing function so it means that given 00:04:28.500 --> 00:04:29.870 align:start position:0% hashing function so it means that given the<00:04:28.620> output<00:04:28.860> we<00:04:29.100> don't<00:04:29.280> know<00:04:29.400> what<00:04:29.580> is<00:04:29.759> the 00:04:29.870 --> 00:04:29.880 align:start position:0% the output we don't know what is the 00:04:29.880 --> 00:04:31.730 align:start position:0% the output we don't know what is the input<00:04:30.180> and<00:04:30.660> this<00:04:30.780> is<00:04:30.900> not<00:04:31.080> what<00:04:31.320> we<00:04:31.440> call<00:04:31.560> like 00:04:31.730 --> 00:04:31.740 align:start position:0% input and this is not what we call like 00:04:31.740 --> 00:04:33.830 align:start position:0% input and this is not what we call like Collision<00:04:32.220> resistance<00:04:32.820> pretty<00:04:33.479> useful 00:04:33.830 --> 00:04:33.840 align:start position:0% Collision resistance pretty useful 00:04:33.840 --> 00:04:35.990 align:start position:0% Collision resistance pretty useful primitive<00:04:34.199> like<00:04:34.380> used<00:04:34.560> in<00:04:34.800> blockchains<00:04:35.340> uh<00:04:35.699> I 00:04:35.990 --> 00:04:36.000 align:start position:0% primitive like used in blockchains uh I 00:04:36.000 --> 00:04:37.969 align:start position:0% primitive like used in blockchains uh I will<00:04:36.120> and<00:04:36.540> I<00:04:36.720> think<00:04:36.840> that's<00:04:36.960> pretty<00:04:37.440> much<00:04:37.560> it<00:04:37.740> I 00:04:37.969 --> 00:04:37.979 align:start position:0% will and I think that's pretty much it I 00:04:37.979 --> 00:04:39.409 align:start position:0% will and I think that's pretty much it I assume<00:04:38.220> that<00:04:38.340> everyone<00:04:38.460> is<00:04:38.759> like<00:04:38.880> familiar 00:04:39.409 --> 00:04:39.419 align:start position:0% assume that everyone is like familiar 00:04:39.419 --> 00:04:42.230 align:start position:0% assume that everyone is like familiar with<00:04:39.660> it<00:04:39.780> like<00:04:40.020> yeah<00:04:40.380> okay<00:04:41.340> why<00:04:41.940> is<00:04:42.060> it 00:04:42.230 --> 00:04:42.240 align:start position:0% with it like yeah okay why is it 00:04:42.240 --> 00:04:45.590 align:start position:0% with it like yeah okay why is it important 00:04:45.590 --> 00:04:45.600 align:start position:0% 00:04:45.600 --> 00:04:47.950 align:start position:0% um<00:04:45.660> so<00:04:46.020> generalized<00:04:46.740> blockchain 00:04:47.950 --> 00:04:47.960 align:start position:0% um so generalized blockchain 00:04:47.960 --> 00:04:50.210 align:start position:0% um so generalized blockchain Anatomy<00:04:48.960> so<00:04:49.139> why<00:04:49.380> we<00:04:49.560> call<00:04:49.680> it<00:04:49.860> a<00:04:50.040> chain 00:04:50.210 --> 00:04:50.220 align:start position:0% Anatomy so why we call it a chain 00:04:50.220 --> 00:04:53.090 align:start position:0% Anatomy so why we call it a chain because<00:04:50.639> we<00:04:51.000> have<00:04:51.360> a<00:04:51.660> bunch<00:04:51.960> of<00:04:52.139> blocks<00:04:52.560> mined 00:04:53.090 --> 00:04:53.100 align:start position:0% because we have a bunch of blocks mined 00:04:53.100 --> 00:04:55.490 align:start position:0% because we have a bunch of blocks mined together<00:04:53.220> like<00:04:53.759> linked<00:04:54.479> together<00:04:54.600> because 00:04:55.490 --> 00:04:55.500 align:start position:0% together like linked together because 00:04:55.500 --> 00:04:57.890 align:start position:0% together like linked together because each<00:04:56.220> block<00:04:56.460> contains<00:04:57.060> the<00:04:57.300> reference<00:04:57.720> the 00:04:57.890 --> 00:04:57.900 align:start position:0% each block contains the reference the 00:04:57.900 --> 00:05:00.530 align:start position:0% each block contains the reference the parent<00:04:58.080> hash<00:04:58.639> and<00:04:59.639> the<00:04:59.940> previous<00:05:00.060> header 00:05:00.530 --> 00:05:00.540 align:start position:0% parent hash and the previous header 00:05:00.540 --> 00:05:01.670 align:start position:0% parent hash and the previous header contains<00:05:00.960> the<00:05:01.080> reference<00:05:01.320> of<00:05:01.440> the<00:05:01.560> parent 00:05:01.670 --> 00:05:01.680 align:start position:0% contains the reference of the parent 00:05:01.680 --> 00:05:03.950 align:start position:0% contains the reference of the parent hash<00:05:02.100> which<00:05:02.580> is<00:05:02.699> pretty<00:05:02.880> cool<00:05:03.120> and<00:05:03.300> let<00:05:03.780> me 00:05:03.950 --> 00:05:03.960 align:start position:0% hash which is pretty cool and let me 00:05:03.960 --> 00:05:06.290 align:start position:0% hash which is pretty cool and let me remind<00:05:04.080> what<00:05:04.380> the<00:05:04.620> hash<00:05:05.100> the<00:05:05.520> parent<00:05:05.880> hash<00:05:06.180> or 00:05:06.290 --> 00:05:06.300 align:start position:0% remind what the hash the parent hash or 00:05:06.300 --> 00:05:09.230 align:start position:0% remind what the hash the parent hash or the<00:05:06.419> block<00:05:06.600> hash<00:05:06.960> of<00:05:07.800> uh<00:05:08.280> on<00:05:08.520> ethereum<00:05:08.880> is<00:05:09.120> it's 00:05:09.230 --> 00:05:09.240 align:start position:0% the block hash of uh on ethereum is it's 00:05:09.240 --> 00:05:11.810 align:start position:0% the block hash of uh on ethereum is it's essentially<00:05:09.540> the<00:05:09.720> hash<00:05:09.960> of<00:05:10.139> the<00:05:10.199> header<00:05:10.979> uh 00:05:11.810 --> 00:05:11.820 align:start position:0% essentially the hash of the header uh 00:05:11.820 --> 00:05:13.909 align:start position:0% essentially the hash of the header uh pretty<00:05:12.060> important<00:05:12.479> to<00:05:13.020> deal<00:05:13.259> with<00:05:13.620> this 00:05:13.909 --> 00:05:13.919 align:start position:0% pretty important to deal with this 00:05:13.919 --> 00:05:15.590 align:start position:0% pretty important to deal with this Primitives<00:05:14.460> and<00:05:14.759> make<00:05:14.940> smart<00:05:15.120> contracts 00:05:15.590 --> 00:05:15.600 align:start position:0% Primitives and make smart contracts 00:05:15.600 --> 00:05:17.650 align:start position:0% Primitives and make smart contracts software<00:05:15.960> so<00:05:16.320> accessing<00:05:16.740> six<00:05:16.979> Oracle<00:05:17.400> State 00:05:17.650 --> 00:05:17.660 align:start position:0% software so accessing six Oracle State 00:05:17.660 --> 00:05:21.189 align:start position:0% software so accessing six Oracle State uh<00:05:18.680> just<00:05:19.680> keep<00:05:19.800> that<00:05:20.040> in<00:05:20.160> mind 00:05:21.189 --> 00:05:21.199 align:start position:0% uh just keep that in mind 00:05:21.199 --> 00:05:25.249 align:start position:0% uh just keep that in mind let's<00:05:22.199> get<00:05:22.560> to<00:05:22.740> the<00:05:22.919> next<00:05:23.100> part<00:05:23.400> so 00:05:25.249 --> 00:05:25.259 align:start position:0% let's get to the next part so 00:05:25.259 --> 00:05:28.070 align:start position:0% let's get to the next part so um no 00:05:28.070 --> 00:05:28.080 align:start position:0% 00:05:28.080 --> 00:05:32.210 align:start position:0% ah<00:05:28.800> I<00:05:29.639> think<00:05:29.759> I'm<00:05:30.060> missing<00:05:30.479> one<00:05:31.199> slide 00:05:32.210 --> 00:05:32.220 align:start position:0% ah I think I'm missing one slide 00:05:32.220 --> 00:05:36.290 align:start position:0% ah I think I'm missing one slide no<00:05:32.699> it's<00:05:33.060> the<00:05:33.240> correct<00:05:33.539> one<00:05:34.259> okay<00:05:35.039> so<00:05:35.580> uh<00:05:36.120> this 00:05:36.290 --> 00:05:36.300 align:start position:0% no it's the correct one okay so uh this 00:05:36.300 --> 00:05:38.270 align:start position:0% no it's the correct one okay so uh this is<00:05:36.419> an<00:05:36.479> ethereum<00:05:36.840> block<00:05:37.020> header<00:05:37.440> uh<00:05:37.860> as<00:05:37.979> I<00:05:38.100> said 00:05:38.270 --> 00:05:38.280 align:start position:0% is an ethereum block header uh as I said 00:05:38.280 --> 00:05:40.010 align:start position:0% is an ethereum block header uh as I said we're<00:05:38.520> gonna<00:05:38.639> go<00:05:38.940> through<00:05:39.120> the<00:05:39.360> example<00:05:39.840> of 00:05:40.010 --> 00:05:40.020 align:start position:0% we're gonna go through the example of 00:05:40.020 --> 00:05:43.249 align:start position:0% we're gonna go through the example of ethereum<00:05:40.620> concretely<00:05:41.100> so<00:05:41.940> a<00:05:42.419> bit<00:05:42.600> of<00:05:42.660> anatomy 00:05:43.249 --> 00:05:43.259 align:start position:0% ethereum concretely so a bit of anatomy 00:05:43.259 --> 00:05:45.650 align:start position:0% ethereum concretely so a bit of anatomy so<00:05:43.860> to<00:05:44.160> access<00:05:44.340> State<00:05:44.699> obviously<00:05:45.120> we<00:05:45.300> need<00:05:45.479> the 00:05:45.650 --> 00:05:45.660 align:start position:0% so to access State obviously we need the 00:05:45.660 --> 00:05:47.210 align:start position:0% so to access State obviously we need the state<00:05:45.960> route<00:05:46.199> what<00:05:46.440> is<00:05:46.560> the<00:05:46.620> state<00:05:46.740> route<00:05:47.039> is 00:05:47.210 --> 00:05:47.220 align:start position:0% state route what is the state route is 00:05:47.220 --> 00:05:49.969 align:start position:0% state route what is the state route is the<00:05:47.400> root<00:05:47.699> of<00:05:47.820> the<00:05:47.940> miracle<00:05:48.300> Patricia<00:05:48.780> tree<00:05:49.020> of 00:05:49.969 --> 00:05:49.979 align:start position:0% the root of the miracle Patricia tree of 00:05:49.979 --> 00:05:51.290 align:start position:0% the root of the miracle Patricia tree of the<00:05:50.160> ethereum<00:05:50.520> state 00:05:51.290 --> 00:05:51.300 align:start position:0% the ethereum state 00:05:51.300 --> 00:05:52.909 align:start position:0% the ethereum state we<00:05:51.780> also<00:05:52.139> have<00:05:52.199> the<00:05:52.320> transactions<00:05:52.740> route 00:05:52.909 --> 00:05:52.919 align:start position:0% we also have the transactions route 00:05:52.919 --> 00:05:54.710 align:start position:0% we also have the transactions route which<00:05:53.220> is<00:05:53.280> pretty<00:05:53.400> useful<00:05:53.759> if<00:05:54.000> you<00:05:54.120> want<00:05:54.419> to 00:05:54.710 --> 00:05:54.720 align:start position:0% which is pretty useful if you want to 00:05:54.720 --> 00:05:56.570 align:start position:0% which is pretty useful if you want to access<00:05:55.139> historical<00:05:55.800> transactions<00:05:56.400> like 00:05:56.570 --> 00:05:56.580 align:start position:0% access historical transactions like 00:05:56.580 --> 00:05:59.570 align:start position:0% access historical transactions like their<00:05:56.820> entire<00:05:57.120> body<00:05:57.740> and<00:05:58.740> receive<00:05:59.100> truth<00:05:59.400> so 00:05:59.570 --> 00:05:59.580 align:start position:0% their entire body and receive truth so 00:05:59.580 --> 00:06:02.210 align:start position:0% their entire body and receive truth so it's<00:05:59.759> very<00:05:59.940> useful<00:06:00.240> to<00:06:00.539> access<00:06:00.800> any<00:06:01.800> events 00:06:02.210 --> 00:06:02.220 align:start position:0% it's very useful to access any events 00:06:02.220 --> 00:06:05.270 align:start position:0% it's very useful to access any events logs<00:06:02.940> and<00:06:03.120> and<00:06:03.600> so<00:06:03.840> on<00:06:04.020> and<00:06:04.500> all<00:06:04.740> of<00:06:04.860> these<00:06:05.100> are 00:06:05.270 --> 00:06:05.280 align:start position:0% logs and and so on and all of these are 00:06:05.280 --> 00:06:07.730 align:start position:0% logs and and so on and all of these are like<00:06:05.460> root<00:06:06.000> of<00:06:06.120> the<00:06:06.180> American<00:06:06.300> Patricia<00:06:06.960> tree 00:06:07.730 --> 00:06:07.740 align:start position:0% like root of the American Patricia tree 00:06:07.740 --> 00:06:10.370 align:start position:0% like root of the American Patricia tree America<00:06:08.039> Patricia<00:06:08.699> 3's<00:06:09.120> America<00:06:09.780> 3<00:06:10.139> just 00:06:10.370 --> 00:06:10.380 align:start position:0% America Patricia 3's America 3 just 00:06:10.380 --> 00:06:12.710 align:start position:0% America Patricia 3's America 3 just think<00:06:10.500> of<00:06:10.680> it<00:06:10.860> in<00:06:10.979> that<00:06:11.460> way<00:06:11.639> and<00:06:12.539> most 00:06:12.710 --> 00:06:12.720 align:start position:0% think of it in that way and most 00:06:12.720 --> 00:06:14.930 align:start position:0% think of it in that way and most importantly<00:06:13.199> we<00:06:13.740> have<00:06:13.800> the<00:06:13.919> parent<00:06:14.100> hash<00:06:14.520> and 00:06:14.930 --> 00:06:14.940 align:start position:0% importantly we have the parent hash and 00:06:14.940 --> 00:06:17.090 align:start position:0% importantly we have the parent hash and with<00:06:15.060> the<00:06:15.180> parent<00:06:15.300> hash<00:06:15.720> we<00:06:16.020> can<00:06:16.259> in<00:06:16.560> a<00:06:16.740> way<00:06:16.800> go 00:06:17.090 --> 00:06:17.100 align:start position:0% with the parent hash we can in a way go 00:06:17.100 --> 00:06:21.409 align:start position:0% with the parent hash we can in a way go go<00:06:17.400> backwards<00:06:18.479> I<00:06:19.259> think<00:06:19.440> that's<00:06:19.919> it<00:06:20.759> let's<00:06:21.180> get 00:06:21.409 --> 00:06:21.419 align:start position:0% go backwards I think that's it let's get 00:06:21.419 --> 00:06:23.510 align:start position:0% go backwards I think that's it let's get to<00:06:21.720> Miracle<00:06:22.380> tree<00:06:22.500> so<00:06:22.740> essentially<00:06:23.100> it's<00:06:23.280> this 00:06:23.510 --> 00:06:23.520 align:start position:0% to Miracle tree so essentially it's this 00:06:23.520 --> 00:06:26.330 align:start position:0% to Miracle tree so essentially it's this idea<00:06:23.880> that<00:06:24.539> I<00:06:24.720> can<00:06:24.900> take<00:06:25.500> whatever<00:06:25.740> amount<00:06:26.160> of 00:06:26.330 --> 00:06:26.340 align:start position:0% idea that I can take whatever amount of 00:06:26.340 --> 00:06:28.550 align:start position:0% idea that I can take whatever amount of data<00:06:26.699> and<00:06:27.419> I<00:06:27.600> can<00:06:27.720> commit<00:06:28.199> it<00:06:28.259> in<00:06:28.440> a 00:06:28.550 --> 00:06:28.560 align:start position:0% data and I can commit it in a 00:06:28.560 --> 00:06:31.550 align:start position:0% data and I can commit it in a cryptographic<00:06:29.100> manner<00:06:29.400> by<00:06:30.180> using<00:06:30.660> this<00:06:31.199> data 00:06:31.550 --> 00:06:31.560 align:start position:0% cryptographic manner by using this data 00:06:31.560 --> 00:06:34.010 align:start position:0% cryptographic manner by using this data structure<00:06:31.979> so<00:06:32.759> on<00:06:33.180> the 00:06:34.010 --> 00:06:34.020 align:start position:0% structure so on the 00:06:34.020 --> 00:06:36.650 align:start position:0% structure so on the left<00:06:34.680> side<00:06:34.919> we<00:06:35.460> see<00:06:35.580> a<00:06:35.819> standard<00:06:36.120> Merkle<00:06:36.479> tree 00:06:36.650 --> 00:06:36.660 align:start position:0% left side we see a standard Merkle tree 00:06:36.660 --> 00:06:38.450 align:start position:0% left side we see a standard Merkle tree so<00:06:37.080> essentially<00:06:37.380> all<00:06:37.740> the<00:06:37.860> data<00:06:38.039> goes<00:06:38.280> to<00:06:38.340> the 00:06:38.450 --> 00:06:38.460 align:start position:0% so essentially all the data goes to the 00:06:38.460 --> 00:06:40.430 align:start position:0% so essentially all the data goes to the bottom<00:06:38.699> and<00:06:38.880> we<00:06:39.060> essentially<00:06:39.360> hash<00:06:39.720> it<00:06:39.900> you 00:06:40.430 --> 00:06:40.440 align:start position:0% bottom and we essentially hash it you 00:06:40.440 --> 00:06:41.629 align:start position:0% bottom and we essentially hash it you know<00:06:40.560> what<00:06:40.620> the<00:06:40.800> hashing<00:06:41.039> function<00:06:41.340> is<00:06:41.400> then 00:06:41.629 --> 00:06:41.639 align:start position:0% know what the hashing function is then 00:06:41.639 --> 00:06:42.710 align:start position:0% know what the hashing function is then we<00:06:41.759> combine<00:06:42.000> these<00:06:42.180> two<00:06:42.240> hashes<00:06:42.600> together 00:06:42.710 --> 00:06:42.720 align:start position:0% we combine these two hashes together 00:06:42.720 --> 00:06:44.749 align:start position:0% we combine these two hashes together with<00:06:43.020> hash<00:06:43.199> it<00:06:43.380> and<00:06:43.560> do<00:06:43.740> we<00:06:44.220> keep<00:06:44.400> doing<00:06:44.580> that 00:06:44.749 --> 00:06:44.759 align:start position:0% with hash it and do we keep doing that 00:06:44.759 --> 00:06:47.390 align:start position:0% with hash it and do we keep doing that until<00:06:45.139> we<00:06:46.139> get<00:06:46.259> to<00:06:46.380> essentially<00:06:46.740> one<00:06:46.919> hush<00:06:47.220> and 00:06:47.390 --> 00:06:47.400 align:start position:0% until we get to essentially one hush and 00:06:47.400 --> 00:06:49.430 align:start position:0% until we get to essentially one hush and this<00:06:47.520> is<00:06:47.580> what<00:06:47.699> we<00:06:47.819> call<00:06:47.880> the<00:06:48.060> root<00:06:48.840> mark<00:06:49.199> up 00:06:49.430 --> 00:06:49.440 align:start position:0% this is what we call the root mark up 00:06:49.440 --> 00:06:51.110 align:start position:0% this is what we call the root mark up the<00:06:49.560> Trisha<00:06:49.919> three<00:06:50.100> modified<00:06:50.639> Miracle 00:06:51.110 --> 00:06:51.120 align:start position:0% the Trisha three modified Miracle 00:06:51.120 --> 00:06:53.930 align:start position:0% the Trisha three modified Miracle Patricia<00:06:51.419> 2<00:06:51.600> to<00:06:51.840> be<00:06:51.960> exactly<00:06:52.639> the<00:06:53.639> data 00:06:53.930 --> 00:06:53.940 align:start position:0% Patricia 2 to be exactly the data 00:06:53.940 --> 00:06:56.450 align:start position:0% Patricia 2 to be exactly the data structure<00:06:54.419> that<00:06:54.600> we<00:06:54.720> use<00:06:54.900> in<00:06:55.020> ethereum 00:06:56.450 --> 00:06:56.460 align:start position:0% structure that we use in ethereum 00:06:56.460 --> 00:06:59.689 align:start position:0% structure that we use in ethereum um<00:06:56.520> what<00:06:57.180> you<00:06:57.360> see<00:06:57.479> here<00:06:57.720> I<00:06:58.380> hope<00:06:58.560> you<00:06:58.740> see<00:06:58.919> on 00:06:59.689 --> 00:06:59.699 align:start position:0% um what you see here I hope you see on 00:06:59.699 --> 00:07:01.490 align:start position:0% um what you see here I hope you see on the<00:06:59.819> top<00:06:59.880> we<00:07:00.060> have<00:07:00.180> the<00:07:00.300> state<00:07:00.479> route 00:07:01.490 --> 00:07:01.500 align:start position:0% the top we have the state route 00:07:01.500 --> 00:07:03.469 align:start position:0% the top we have the state route and<00:07:02.039> essentially<00:07:02.460> the<00:07:02.699> state<00:07:02.880> route<00:07:03.120> is<00:07:03.300> the 00:07:03.469 --> 00:07:03.479 align:start position:0% and essentially the state route is the 00:07:03.479 --> 00:07:05.390 align:start position:0% and essentially the state route is the root<00:07:03.900> of<00:07:03.960> this<00:07:04.139> tree<00:07:04.380> and<00:07:04.740> now<00:07:04.860> how<00:07:05.039> it<00:07:05.160> works 00:07:05.390 --> 00:07:05.400 align:start position:0% root of this tree and now how it works 00:07:05.400 --> 00:07:07.249 align:start position:0% root of this tree and now how it works and<00:07:05.520> how<00:07:05.759> you<00:07:05.880> should<00:07:06.000> think<00:07:06.180> of<00:07:06.360> this<00:07:06.600> of<00:07:07.020> this 00:07:07.249 --> 00:07:07.259 align:start position:0% and how you should think of this of this 00:07:07.259 --> 00:07:09.469 align:start position:0% and how you should think of this of this it's<00:07:07.500> a<00:07:07.740> pretty<00:07:07.919> complex<00:07:08.460> data<00:07:08.940> structure<00:07:09.240> I 00:07:09.469 --> 00:07:09.479 align:start position:0% it's a pretty complex data structure I 00:07:09.479 --> 00:07:10.990 align:start position:0% it's a pretty complex data structure I don't<00:07:09.600> want<00:07:09.720> you<00:07:09.840> to<00:07:09.960> bother<00:07:10.199> with<00:07:10.440> it<00:07:10.740> today 00:07:10.990 --> 00:07:11.000 align:start position:0% don't want you to bother with it today 00:07:11.000 --> 00:07:14.749 align:start position:0% don't want you to bother with it today but<00:07:12.000> essentially<00:07:12.680> we<00:07:13.680> have<00:07:13.919> three<00:07:14.220> types<00:07:14.639> of 00:07:14.749 --> 00:07:14.759 align:start position:0% but essentially we have three types of 00:07:14.759 --> 00:07:17.689 align:start position:0% but essentially we have three types of like<00:07:15.120> notes<00:07:15.539> we<00:07:15.840> have<00:07:16.020> Leaf<00:07:16.979> nodes<00:07:17.220> extension 00:07:17.689 --> 00:07:17.699 align:start position:0% like notes we have Leaf nodes extension 00:07:17.699 --> 00:07:21.110 align:start position:0% like notes we have Leaf nodes extension notes<00:07:18.180> and<00:07:18.479> Branch<00:07:18.900> notes<00:07:19.380> so<00:07:20.220> Leaf<00:07:20.819> nodes 00:07:21.110 --> 00:07:21.120 align:start position:0% notes and Branch notes so Leaf nodes 00:07:21.120 --> 00:07:23.270 align:start position:0% notes and Branch notes so Leaf nodes contain<00:07:21.419> data<00:07:21.780> Branch<00:07:22.139> nodes<00:07:22.440> contain<00:07:22.800> data 00:07:23.270 --> 00:07:23.280 align:start position:0% contain data Branch nodes contain data 00:07:23.280 --> 00:07:25.610 align:start position:0% contain data Branch nodes contain data and<00:07:24.000> extension<00:07:24.539> nodes<00:07:24.840> like<00:07:25.199> on<00:07:25.380> the<00:07:25.500> high 00:07:25.610 --> 00:07:25.620 align:start position:0% and extension nodes like on the high 00:07:25.620 --> 00:07:27.290 align:start position:0% and extension nodes like on the high level<00:07:25.800> just<00:07:26.280> help<00:07:26.520> us<00:07:26.699> to<00:07:26.880> like<00:07:27.000> sort<00:07:27.240> of 00:07:27.290 --> 00:07:27.300 align:start position:0% level just help us to like sort of 00:07:27.300 --> 00:07:29.450 align:start position:0% level just help us to like sort of navigate<00:07:27.539> in<00:07:27.960> that<00:07:28.139> tree<00:07:28.319> but<00:07:28.979> to<00:07:29.099> be<00:07:29.220> honest 00:07:29.450 --> 00:07:29.460 align:start position:0% navigate in that tree but to be honest 00:07:29.460 --> 00:07:31.309 align:start position:0% navigate in that tree but to be honest to<00:07:30.120> deal<00:07:30.240> with<00:07:30.419> storage<00:07:30.539> truth<00:07:31.020> you<00:07:31.199> don't 00:07:31.309 --> 00:07:31.319 align:start position:0% to deal with storage truth you don't 00:07:31.319 --> 00:07:33.170 align:start position:0% to deal with storage truth you don't really<00:07:31.440> need<00:07:31.740> to<00:07:31.860> understand<00:07:32.039> this<00:07:32.520> part<00:07:32.699> but 00:07:33.170 --> 00:07:33.180 align:start position:0% really need to understand this part but 00:07:33.180 --> 00:07:35.570 align:start position:0% really need to understand this part but to<00:07:33.419> like<00:07:33.599> build<00:07:34.020> on<00:07:34.500> the<00:07:34.560> low<00:07:34.680> level<00:07:34.919> as<00:07:35.220> we<00:07:35.400> do 00:07:35.570 --> 00:07:35.580 align:start position:0% to like build on the low level as we do 00:07:35.580 --> 00:07:38.089 align:start position:0% to like build on the low level as we do obviously<00:07:36.360> we<00:07:36.479> need<00:07:36.660> to<00:07:36.900> we<00:07:37.680> need<00:07:37.800> to<00:07:37.919> do 00:07:38.089 --> 00:07:38.099 align:start position:0% obviously we need to we need to do 00:07:38.099 --> 00:07:40.490 align:start position:0% obviously we need to we need to do pretty<00:07:38.460> pretty<00:07:39.180> a<00:07:39.479> lot<00:07:39.539> with<00:07:39.660> that<00:07:39.900> with<00:07:40.139> that 00:07:40.490 --> 00:07:40.500 align:start position:0% pretty pretty a lot with that with that 00:07:40.500 --> 00:07:41.210 align:start position:0% pretty pretty a lot with that with that part 00:07:41.210 --> 00:07:41.220 align:start position:0% part 00:07:41.220 --> 00:07:42.469 align:start position:0% part okay 00:07:42.469 --> 00:07:42.479 align:start position:0% okay 00:07:42.479 --> 00:07:45.589 align:start position:0% okay so<00:07:43.020> ethereum<00:07:43.740> State<00:07:43.979> how<00:07:44.880> is<00:07:45.000> it<00:07:45.120> constructed 00:07:45.589 --> 00:07:45.599 align:start position:0% so ethereum State how is it constructed 00:07:45.599 --> 00:07:47.749 align:start position:0% so ethereum State how is it constructed most<00:07:46.380> important<00:07:46.740> takeaway<00:07:47.099> it's<00:07:47.340> a<00:07:47.460> two<00:07:47.580> level 00:07:47.749 --> 00:07:47.759 align:start position:0% most important takeaway it's a two level 00:07:47.759 --> 00:07:49.969 align:start position:0% most important takeaway it's a two level structure<00:07:48.300> so<00:07:49.020> I<00:07:49.199> mentioned<00:07:49.500> that<00:07:49.680> the<00:07:49.800> state 00:07:49.969 --> 00:07:49.979 align:start position:0% structure so I mentioned that the state 00:07:49.979 --> 00:07:51.650 align:start position:0% structure so I mentioned that the state route<00:07:50.220> is<00:07:50.520> a<00:07:50.759> commitment<00:07:51.120> of<00:07:51.300> the<00:07:51.419> entire 00:07:51.650 --> 00:07:51.660 align:start position:0% route is a commitment of the entire 00:07:51.660 --> 00:07:53.510 align:start position:0% route is a commitment of the entire state<00:07:51.900> but<00:07:52.440> it's<00:07:52.620> not<00:07:52.740> really<00:07:52.919> true<00:07:53.220> because 00:07:53.510 --> 00:07:53.520 align:start position:0% state but it's not really true because 00:07:53.520 --> 00:07:55.550 align:start position:0% state but it's not really true because ethereum<00:07:54.360> is<00:07:54.479> a 00:07:55.550 --> 00:07:55.560 align:start position:0% ethereum is a 00:07:55.560 --> 00:07:58.790 align:start position:0% ethereum is a does<00:07:55.919> it<00:07:56.099> okay<00:07:56.639> works<00:07:57.199> it's<00:07:58.199> uh<00:07:58.380> it's<00:07:58.680> account 00:07:58.790 --> 00:07:58.800 align:start position:0% does it okay works it's uh it's account 00:07:58.800 --> 00:07:59.990 align:start position:0% does it okay works it's uh it's account based 00:07:59.990 --> 00:08:00.000 align:start position:0% based 00:08:00.000 --> 00:08:01.610 align:start position:0% based um<00:08:00.120> and<00:08:00.419> essentially<00:08:00.720> the<00:08:00.960> state<00:08:01.080> route<00:08:01.380> is 00:08:01.610 --> 00:08:01.620 align:start position:0% um and essentially the state route is 00:08:01.620 --> 00:08:03.890 align:start position:0% um and essentially the state route is the<00:08:01.979> commitment<00:08:02.819> of<00:08:03.120> all<00:08:03.300> the<00:08:03.479> accounts<00:08:03.840> that 00:08:03.890 --> 00:08:03.900 align:start position:0% the commitment of all the accounts that 00:08:03.900 --> 00:08:06.050 align:start position:0% the commitment of all the accounts that exist<00:08:04.199> on<00:08:04.319> ethereum<00:08:04.740> and<00:08:05.280> what<00:08:05.520> an<00:08:05.699> account<00:08:05.819> is 00:08:06.050 --> 00:08:06.060 align:start position:0% exist on ethereum and what an account is 00:08:06.060 --> 00:08:07.969 align:start position:0% exist on ethereum and what an account is made<00:08:06.240> of<00:08:06.360> it's<00:08:06.599> made<00:08:06.780> of<00:08:06.900> a<00:08:07.020> balance 00:08:07.969 --> 00:08:07.979 align:start position:0% made of it's made of a balance 00:08:07.979 --> 00:08:10.189 align:start position:0% made of it's made of a balance like<00:08:08.520> the<00:08:08.639> if<00:08:08.759> balance<00:08:09.240> it's<00:08:09.720> announced 00:08:10.189 --> 00:08:10.199 align:start position:0% like the if balance it's announced 00:08:10.199 --> 00:08:13.550 align:start position:0% like the if balance it's announced transaction<00:08:11.039> counter<00:08:11.699> storage<00:08:12.419> route<00:08:12.840> the 00:08:13.550 --> 00:08:13.560 align:start position:0% transaction counter storage route the 00:08:13.560 --> 00:08:15.710 align:start position:0% transaction counter storage route the storage<00:08:13.740> route<00:08:14.039> is<00:08:14.520> like<00:08:15.000> the<00:08:15.240> root<00:08:15.479> of 00:08:15.710 --> 00:08:15.720 align:start position:0% storage route is like the root of 00:08:15.720 --> 00:08:17.749 align:start position:0% storage route is like the root of another<00:08:15.840> America<00:08:16.139> Patricia<00:08:16.860> tree<00:08:17.099> and<00:08:17.639> this 00:08:17.749 --> 00:08:17.759 align:start position:0% another America Patricia tree and this 00:08:17.759 --> 00:08:20.330 align:start position:0% another America Patricia tree and this America<00:08:18.000> Patricia<00:08:18.539> tree<00:08:18.840> contains<00:08:19.379> the<00:08:19.620> key 00:08:20.330 --> 00:08:20.340 align:start position:0% America Patricia tree contains the key 00:08:20.340 --> 00:08:23.270 align:start position:0% America Patricia tree contains the key value<00:08:20.639> database<00:08:21.300> that<00:08:21.960> holds<00:08:22.620> like 00:08:23.270 --> 00:08:23.280 align:start position:0% value database that holds like 00:08:23.280 --> 00:08:26.029 align:start position:0% value database that holds like the<00:08:23.819> mapping<00:08:24.300> from<00:08:24.660> storage<00:08:25.080> key<00:08:25.379> to<00:08:25.680> its 00:08:26.029 --> 00:08:26.039 align:start position:0% the mapping from storage key to its 00:08:26.039 --> 00:08:27.589 align:start position:0% the mapping from storage key to its actual<00:08:26.280> value 00:08:27.589 --> 00:08:27.599 align:start position:0% actual value 00:08:27.599 --> 00:08:29.749 align:start position:0% actual value and<00:08:28.139> finally<00:08:28.319> we<00:08:28.500> have<00:08:28.620> the<00:08:28.740> code<00:08:28.860> it's 00:08:29.749 --> 00:08:29.759 align:start position:0% and finally we have the code it's 00:08:29.759 --> 00:08:31.670 align:start position:0% and finally we have the code it's essentially<00:08:30.419> the<00:08:30.599> hash<00:08:30.840> of<00:08:31.020> the<00:08:31.139> of<00:08:31.500> the 00:08:31.670 --> 00:08:31.680 align:start position:0% essentially the hash of the of the 00:08:31.680 --> 00:08:34.909 align:start position:0% essentially the hash of the of the bytecode<00:08:32.580> so<00:08:33.240> main<00:08:33.599> takeaway<00:08:34.020> first<00:08:34.560> we 00:08:34.909 --> 00:08:34.919 align:start position:0% bytecode so main takeaway first we 00:08:34.919 --> 00:08:37.250 align:start position:0% bytecode so main takeaway first we access<00:08:35.099> accounts<00:08:35.760> and<00:08:36.419> once<00:08:36.779> we<00:08:36.959> have<00:08:37.080> the 00:08:37.250 --> 00:08:37.260 align:start position:0% access accounts and once we have the 00:08:37.260 --> 00:08:41.089 align:start position:0% access accounts and once we have the account<00:08:37.380> storage<00:08:37.800> root<00:08:38.219> we<00:08:38.339> can<00:08:38.459> access<00:08:38.580> each 00:08:41.089 --> 00:08:41.099 align:start position:0% 00:08:41.099 --> 00:08:42.709 align:start position:0% okay 00:08:42.709 --> 00:08:42.719 align:start position:0% okay 00:08:42.719 --> 00:08:43.610 align:start position:0% okay um 00:08:43.610 --> 00:08:43.620 align:start position:0% um 00:08:43.620 --> 00:08:46.970 align:start position:0% um cool<00:08:44.099> so<00:08:44.520> to<00:08:44.760> sum<00:08:44.880> it<00:08:45.060> up<00:08:45.440> like<00:08:46.440> the<00:08:46.680> background 00:08:46.970 --> 00:08:46.980 align:start position:0% cool so to sum it up like the background 00:08:46.980 --> 00:08:49.610 align:start position:0% cool so to sum it up like the background so<00:08:47.339> main<00:08:47.580> takeaways<00:08:48.120> given<00:08:48.899> the<00:08:49.200> block<00:08:49.320> stay 00:08:49.610 --> 00:08:49.620 align:start position:0% so main takeaways given the block stay 00:08:49.620 --> 00:08:52.910 align:start position:0% so main takeaways given the block stay true<00:08:49.800> to<00:08:50.100> you<00:08:50.220> can<00:08:50.339> recreate<00:08:51.120> any 00:08:52.910 --> 00:08:52.920 align:start position:0% true to you can recreate any 00:08:52.920 --> 00:08:56.150 align:start position:0% true to you can recreate any any<00:08:53.459> state<00:08:53.760> for<00:08:54.540> this<00:08:54.720> specific<00:08:55.080> block<00:08:55.320> on 00:08:56.150 --> 00:08:56.160 align:start position:0% any state for this specific block on 00:08:56.160 --> 00:08:57.170 align:start position:0% any state for this specific block on this<00:08:56.339> network 00:08:57.170 --> 00:08:57.180 align:start position:0% this network 00:08:57.180 --> 00:09:00.410 align:start position:0% this network and<00:08:57.899> give<00:08:58.140> an<00:08:58.320> initial<00:08:58.680> trusted<00:08:59.220> blockage<00:08:59.700> you 00:09:00.410 --> 00:09:00.420 align:start position:0% and give an initial trusted blockage you 00:09:00.420 --> 00:09:02.150 align:start position:0% and give an initial trusted blockage you can<00:09:00.540> essentially<00:09:00.899> recreate<00:09:01.620> all<00:09:01.920> the 00:09:02.150 --> 00:09:02.160 align:start position:0% can essentially recreate all the 00:09:02.160 --> 00:09:04.670 align:start position:0% can essentially recreate all the previous<00:09:02.459> headers<00:09:03.060> which<00:09:03.839> is<00:09:04.019> pretty<00:09:04.260> pretty 00:09:04.670 --> 00:09:04.680 align:start position:0% previous headers which is pretty pretty 00:09:04.680 --> 00:09:07.490 align:start position:0% previous headers which is pretty pretty cool<00:09:04.980> and<00:09:05.339> important<00:09:05.760> to<00:09:06.000> get<00:09:06.240> the<00:09:06.959> ideas<00:09:07.080> that 00:09:07.490 --> 00:09:07.500 align:start position:0% cool and important to get the ideas that 00:09:07.500 --> 00:09:09.290 align:start position:0% cool and important to get the ideas that I<00:09:07.620> will<00:09:07.740> explain<00:09:07.860> like<00:09:08.100> pretty<00:09:08.339> soon 00:09:09.290 --> 00:09:09.300 align:start position:0% I will explain like pretty soon 00:09:09.300 --> 00:09:12.110 align:start position:0% I will explain like pretty soon okay<00:09:09.779> so<00:09:10.620> as<00:09:10.920> it's<00:09:11.100> gonna<00:09:11.279> be<00:09:11.459> a<00:09:11.580> workshop<00:09:11.880> it's 00:09:12.110 --> 00:09:12.120 align:start position:0% okay so as it's gonna be a workshop it's 00:09:12.120 --> 00:09:15.290 align:start position:0% okay so as it's gonna be a workshop it's a<00:09:12.300> short<00:09:12.420> one<00:09:12.660> so<00:09:13.260> I<00:09:13.620> won't<00:09:13.800> let<00:09:14.399> you<00:09:14.640> code<00:09:14.880> but 00:09:15.290 --> 00:09:15.300 align:start position:0% a short one so I won't let you code but 00:09:15.300 --> 00:09:17.030 align:start position:0% a short one so I won't let you code but I<00:09:15.480> will<00:09:15.660> show<00:09:15.899> you<00:09:16.019> some<00:09:16.260> concrete<00:09:16.620> examples 00:09:17.030 --> 00:09:17.040 align:start position:0% I will show you some concrete examples 00:09:17.040 --> 00:09:19.730 align:start position:0% I will show you some concrete examples so<00:09:17.820> what<00:09:18.120> I<00:09:18.360> want<00:09:18.540> you<00:09:18.720> to<00:09:18.839> like<00:09:19.200> go<00:09:19.560> through 00:09:19.730 --> 00:09:19.740 align:start position:0% so what I want you to like go through 00:09:19.740 --> 00:09:23.150 align:start position:0% so what I want you to like go through with<00:09:20.160> me<00:09:20.399> today<00:09:20.580> is<00:09:21.240> how<00:09:21.540> we<00:09:21.779> can<00:09:22.019> prove<00:09:22.920> the 00:09:23.150 --> 00:09:23.160 align:start position:0% with me today is how we can prove the 00:09:23.160 --> 00:09:25.550 align:start position:0% with me today is how we can prove the ownership<00:09:23.519> of<00:09:23.940> Alliance<00:09:24.420> profile<00:09:24.720> on<00:09:25.260> another 00:09:25.550 --> 00:09:25.560 align:start position:0% ownership of Alliance profile on another 00:09:25.560 --> 00:09:26.630 align:start position:0% ownership of Alliance profile on another chain 00:09:26.630 --> 00:09:26.640 align:start position:0% chain 00:09:26.640 --> 00:09:28.850 align:start position:0% chain so 00:09:28.850 --> 00:09:28.860 align:start position:0% so 00:09:28.860 --> 00:09:30.949 align:start position:0% so a<00:09:29.339> bit<00:09:29.519> of<00:09:29.700> background<00:09:29.940> lens<00:09:30.300> profiles<00:09:30.899> are 00:09:30.949 --> 00:09:30.959 align:start position:0% a bit of background lens profiles are 00:09:30.959 --> 00:09:34.009 align:start position:0% a bit of background lens profiles are represented<00:09:31.440> as<00:09:31.560> nfts<00:09:32.160> and<00:09:33.000> lens<00:09:33.420> is<00:09:33.600> deployed 00:09:34.009 --> 00:09:34.019 align:start position:0% represented as nfts and lens is deployed 00:09:34.019 --> 00:09:38.590 align:start position:0% represented as nfts and lens is deployed on<00:09:34.200> polygon<00:09:34.860> I<00:09:35.580> think<00:09:35.720> that's<00:09:36.720> it<00:09:37.220> how<00:09:38.220> do<00:09:38.339> we 00:09:38.590 --> 00:09:38.600 align:start position:0% on polygon I think that's it how do we 00:09:38.600 --> 00:09:42.050 align:start position:0% on polygon I think that's it how do we get<00:09:39.600> to<00:09:39.779> this<00:09:39.959> so<00:09:40.680> first<00:09:41.040> of<00:09:41.160> all<00:09:41.279> the<00:09:41.880> question 00:09:42.050 --> 00:09:42.060 align:start position:0% get to this so first of all the question 00:09:42.060 --> 00:09:43.730 align:start position:0% get to this so first of all the question that<00:09:42.300> we<00:09:42.480> need<00:09:42.600> to<00:09:42.720> answer<00:09:42.839> to<00:09:43.080> ourselves<00:09:43.560> is 00:09:43.730 --> 00:09:43.740 align:start position:0% that we need to answer to ourselves is 00:09:43.740 --> 00:09:46.490 align:start position:0% that we need to answer to ourselves is how<00:09:44.580> does<00:09:44.760> Polygon<00:09:45.300> commit<00:09:45.600> to<00:09:45.779> ethereum<00:09:46.200> L1 00:09:46.490 --> 00:09:46.500 align:start position:0% how does Polygon commit to ethereum L1 00:09:46.500 --> 00:09:48.769 align:start position:0% how does Polygon commit to ethereum L1 because<00:09:47.160> if<00:09:47.459> we<00:09:47.640> want<00:09:47.820> to<00:09:47.940> like<00:09:48.360> let's<00:09:48.600> say 00:09:48.769 --> 00:09:48.779 align:start position:0% because if we want to like let's say 00:09:48.779 --> 00:09:51.110 align:start position:0% because if we want to like let's say prove<00:09:49.320> the<00:09:49.440> ownership<00:09:49.800> of<00:09:50.100> a<00:09:50.279> lens<00:09:50.459> profile<00:09:50.820> on 00:09:51.110 --> 00:09:51.120 align:start position:0% prove the ownership of a lens profile on 00:09:51.120 --> 00:09:53.329 align:start position:0% prove the ownership of a lens profile on optimize<00:09:51.959> we<00:09:52.200> need<00:09:52.320> to<00:09:52.440> know<00:09:52.560> the<00:09:52.800> state<00:09:53.100> route 00:09:53.329 --> 00:09:53.339 align:start position:0% optimize we need to know the state route 00:09:53.339 --> 00:09:57.590 align:start position:0% optimize we need to know the state route of<00:09:53.959> polygon<00:09:54.959> but<00:09:55.860> there<00:09:56.399> is<00:09:56.580> material<00:09:57.000> one<00:09:57.420> in 00:09:57.590 --> 00:09:57.600 align:start position:0% of polygon but there is material one in 00:09:57.600 --> 00:09:59.750 align:start position:0% of polygon but there is material one in the<00:09:57.720> middle<00:09:57.839> so<00:09:58.200> how<00:09:59.100> do<00:09:59.220> we<00:09:59.339> actually<00:09:59.459> access 00:09:59.750 --> 00:09:59.760 align:start position:0% the middle so how do we actually access 00:09:59.760 --> 00:10:04.250 align:start position:0% the middle so how do we actually access this<00:10:00.060> on<00:10:00.180> HTML<00:10:00.720> one<00:10:00.959> primarily<00:10:02.279> so<00:10:03.060> uh<00:10:03.720> polygon 00:10:04.250 --> 00:10:04.260 align:start position:0% this on HTML one primarily so uh polygon 00:10:04.260 --> 00:10:06.710 align:start position:0% this on HTML one primarily so uh polygon is<00:10:04.440> a<00:10:04.560> commitment<00:10:04.860> commit<00:10:05.459> commit<00:10:05.820> chain 00:10:06.710 --> 00:10:06.720 align:start position:0% is a commitment commit commit chain 00:10:06.720 --> 00:10:09.949 align:start position:0% is a commitment commit commit chain and<00:10:07.320> it<00:10:07.500> commits<00:10:07.920> to<00:10:08.100> to<00:10:08.339> ethereum<00:10:08.820> a<00:10:09.540> bunch<00:10:09.839> of 00:10:09.949 --> 00:10:09.959 align:start position:0% and it commits to to ethereum a bunch of 00:10:09.959 --> 00:10:11.630 align:start position:0% and it commits to to ethereum a bunch of things<00:10:10.140> every 00:10:11.630 --> 00:10:11.640 align:start position:0% things every 00:10:11.640 --> 00:10:14.329 align:start position:0% things every some<00:10:12.180> amount<00:10:12.420> of<00:10:12.600> time<00:10:12.779> and<00:10:13.560> essentially<00:10:13.920> on 00:10:14.329 --> 00:10:14.339 align:start position:0% some amount of time and essentially on 00:10:14.339 --> 00:10:16.790 align:start position:0% some amount of time and essentially on L1<00:10:14.700> we<00:10:15.000> do<00:10:15.180> not<00:10:15.300> validate<00:10:15.839> the<00:10:16.320> entire<00:10:16.500> State 00:10:16.790 --> 00:10:16.800 align:start position:0% L1 we do not validate the entire State 00:10:16.800 --> 00:10:18.470 align:start position:0% L1 we do not validate the entire State transition<00:10:17.160> but<00:10:17.459> we<00:10:17.580> just<00:10:17.760> verify<00:10:18.240> the 00:10:18.470 --> 00:10:18.480 align:start position:0% transition but we just verify the 00:10:18.480 --> 00:10:21.410 align:start position:0% transition but we just verify the consensus<00:10:19.380> of<00:10:19.860> polygon<00:10:20.459> and<00:10:21.060> this 00:10:21.410 --> 00:10:21.420 align:start position:0% consensus of polygon and this 00:10:21.420 --> 00:10:24.350 align:start position:0% consensus of polygon and this checkpoints<00:10:22.320> how<00:10:22.560> they<00:10:22.800> call<00:10:22.980> it<00:10:23.360> essentially 00:10:24.350 --> 00:10:24.360 align:start position:0% checkpoints how they call it essentially 00:10:24.360 --> 00:10:27.949 align:start position:0% checkpoints how they call it essentially contain<00:10:24.959> uh<00:10:25.800> State<00:10:26.580> routes<00:10:27.060> and<00:10:27.540> so<00:10:27.660> I<00:10:27.779> mean 00:10:27.949 --> 00:10:27.959 align:start position:0% contain uh State routes and so I mean 00:10:27.959 --> 00:10:31.070 align:start position:0% contain uh State routes and so I mean not<00:10:28.320> directly<00:10:28.680> but<00:10:28.980> we<00:10:29.220> can<00:10:29.399> access<00:10:30.240> them<00:10:30.600> and 00:10:31.070 --> 00:10:31.080 align:start position:0% not directly but we can access them and 00:10:31.080 --> 00:10:34.430 align:start position:0% not directly but we can access them and let's<00:10:31.500> get<00:10:31.920> to<00:10:32.040> this<00:10:32.399> to<00:10:33.120> this<00:10:33.360> part 00:10:34.430 --> 00:10:34.440 align:start position:0% let's get to this to this part 00:10:34.440 --> 00:10:37.730 align:start position:0% let's get to this to this part so<00:10:35.160> this<00:10:35.459> is<00:10:35.580> taken<00:10:36.060> from<00:10:36.779> polygons 00:10:37.730 --> 00:10:37.740 align:start position:0% so this is taken from polygons 00:10:37.740 --> 00:10:39.350 align:start position:0% so this is taken from polygons documentation 00:10:39.350 --> 00:10:39.360 align:start position:0% documentation 00:10:39.360 --> 00:10:41.630 align:start position:0% documentation and<00:10:39.899> this<00:10:40.080> is<00:10:40.200> how<00:10:40.500> a<00:10:40.680> checkpoint<00:10:41.100> looks<00:10:41.459> like 00:10:41.630 --> 00:10:41.640 align:start position:0% and this is how a checkpoint looks like 00:10:41.640 --> 00:10:44.210 align:start position:0% and this is how a checkpoint looks like so<00:10:42.480> as<00:10:42.720> you<00:10:42.839> can<00:10:42.959> see<00:10:43.080> the<00:10:43.500> checkpoint<00:10:43.860> is<00:10:44.100> made 00:10:44.210 --> 00:10:44.220 align:start position:0% so as you can see the checkpoint is made 00:10:44.220 --> 00:10:46.850 align:start position:0% so as you can see the checkpoint is made of<00:10:44.339> a<00:10:44.459> proposal<00:10:44.940> so<00:10:45.300> who<00:10:45.540> proposed<00:10:45.959> The<00:10:46.079> Block 00:10:46.850 --> 00:10:46.860 align:start position:0% of a proposal so who proposed The Block 00:10:46.860 --> 00:10:49.430 align:start position:0% of a proposal so who proposed The Block start<00:10:47.279> block<00:10:47.579> and<00:10:47.880> block<00:10:48.140> give<00:10:49.140> me<00:10:49.260> a<00:10:49.380> second 00:10:49.430 --> 00:10:49.440 align:start position:0% start block and block give me a second 00:10:49.440 --> 00:10:51.710 align:start position:0% start block and block give me a second I'll<00:10:49.680> get<00:10:49.920> to<00:10:50.100> this<00:10:50.279> and<00:10:50.940> most<00:10:51.120> importantly<00:10:51.480> we 00:10:51.710 --> 00:10:51.720 align:start position:0% I'll get to this and most importantly we 00:10:51.720 --> 00:10:53.750 align:start position:0% I'll get to this and most importantly we have<00:10:51.779> the<00:10:51.899> root<00:10:52.200> question<00:10:52.320> so<00:10:53.100> the<00:10:53.279> root<00:10:53.519> hush 00:10:53.750 --> 00:10:53.760 align:start position:0% have the root question so the root hush 00:10:53.760 --> 00:10:55.670 align:start position:0% have the root question so the root hush is<00:10:53.940> essentially<00:10:54.300> a<00:10:54.720> Merkle<00:10:55.200> tree<00:10:55.320> not<00:10:55.500> America 00:10:55.670 --> 00:10:55.680 align:start position:0% is essentially a Merkle tree not America 00:10:55.680 --> 00:10:58.730 align:start position:0% is essentially a Merkle tree not America Patricia<00:10:56.279> tree<00:10:56.459> that<00:10:57.180> contains<00:10:57.779> all<00:10:58.500> the 00:10:58.730 --> 00:10:58.740 align:start position:0% Patricia tree that contains all the 00:10:58.740 --> 00:11:01.370 align:start position:0% Patricia tree that contains all the headers<00:10:59.160> and<00:10:59.880> which<00:11:00.120> headers<00:11:00.600> the<00:11:00.839> headers<00:11:01.140> in 00:11:01.370 --> 00:11:01.380 align:start position:0% headers and which headers the headers in 00:11:01.380 --> 00:11:04.190 align:start position:0% headers and which headers the headers in the<00:11:01.500> range<00:11:01.740> of<00:11:01.920> start<00:11:02.160> block<00:11:02.399> and<00:11:02.880> and<00:11:03.060> block 00:11:04.190 --> 00:11:04.200 align:start position:0% the range of start block and and block 00:11:04.200 --> 00:11:05.389 align:start position:0% the range of start block and and block cool 00:11:05.389 --> 00:11:05.399 align:start position:0% cool 00:11:05.399 --> 00:11:07.610 align:start position:0% cool so<00:11:06.240> now 00:11:07.610 --> 00:11:07.620 align:start position:0% so now 00:11:07.620 --> 00:11:10.490 align:start position:0% so now if<00:11:08.279> we<00:11:08.399> get<00:11:08.579> back<00:11:08.760> to<00:11:08.940> the<00:11:09.060> previous<00:11:09.240> part<00:11:09.600> we 00:11:10.490 --> 00:11:10.500 align:start position:0% if we get back to the previous part we 00:11:10.500 --> 00:11:12.590 align:start position:0% if we get back to the previous part we can<00:11:10.680> essentially<00:11:11.040> prove<00:11:11.640> with<00:11:12.420> this 00:11:12.590 --> 00:11:12.600 align:start position:0% can essentially prove with this 00:11:12.600 --> 00:11:14.810 align:start position:0% can essentially prove with this commitment<00:11:13.019> that<00:11:13.320> we<00:11:13.500> know<00:11:13.680> the<00:11:13.980> valid<00:11:14.459> state 00:11:14.810 --> 00:11:14.820 align:start position:0% commitment that we know the valid state 00:11:14.820 --> 00:11:17.210 align:start position:0% commitment that we know the valid state route<00:11:15.060> of<00:11:15.420> polygon 00:11:17.210 --> 00:11:17.220 align:start position:0% route of polygon 00:11:17.220 --> 00:11:20.150 align:start position:0% route of polygon the<00:11:17.459> first<00:11:17.640> event<00:11:17.880> block 00:11:20.150 --> 00:11:20.160 align:start position:0% the first event block 00:11:20.160 --> 00:11:22.370 align:start position:0% the first event block okay<00:11:20.640> A<00:11:21.000> bit<00:11:21.120> of<00:11:21.240> Hands-On<00:11:21.600> so<00:11:21.899> we<00:11:22.140> want<00:11:22.260> to 00:11:22.370 --> 00:11:22.380 align:start position:0% okay A bit of Hands-On so we want to 00:11:22.380 --> 00:11:25.250 align:start position:0% okay A bit of Hands-On so we want to prove<00:11:22.860> that<00:11:23.519> I<00:11:23.760> own<00:11:23.940> a<00:11:24.240> lens<00:11:24.480> profile<00:11:24.959> on 00:11:25.250 --> 00:11:25.260 align:start position:0% prove that I own a lens profile on 00:11:25.260 --> 00:11:27.290 align:start position:0% prove that I own a lens profile on polygon<00:11:25.800> forever 00:11:27.290 --> 00:11:27.300 align:start position:0% polygon forever 00:11:27.300 --> 00:11:31.370 align:start position:0% polygon forever so<00:11:27.839> number<00:11:28.620> one<00:11:28.980> we<00:11:29.700> go<00:11:29.940> to<00:11:30.060> the<00:11:30.300> contracts<00:11:30.720> we 00:11:31.370 --> 00:11:31.380 align:start position:0% so number one we go to the contracts we 00:11:31.380 --> 00:11:32.630 align:start position:0% so number one we go to the contracts we see<00:11:31.560> a<00:11:31.740> contract 00:11:32.630 --> 00:11:32.640 align:start position:0% see a contract 00:11:32.640 --> 00:11:34.670 align:start position:0% see a contract we<00:11:33.180> go<00:11:33.360> through<00:11:33.540> it<00:11:33.720> and<00:11:33.959> we<00:11:34.140> see<00:11:34.320> that 00:11:34.670 --> 00:11:34.680 align:start position:0% we go through it and we see that 00:11:34.680 --> 00:11:36.949 align:start position:0% we go through it and we see that essentially<00:11:35.640> there<00:11:35.940> is<00:11:36.060> a<00:11:36.180> bunch<00:11:36.300> of<00:11:36.420> logic<00:11:36.779> on 00:11:36.949 --> 00:11:36.959 align:start position:0% essentially there is a bunch of logic on 00:11:36.959 --> 00:11:39.290 align:start position:0% essentially there is a bunch of logic on top<00:11:37.079> of<00:11:37.320> this<00:11:37.500> erc721 00:11:39.290 --> 00:11:39.300 align:start position:0% top of this erc721 00:11:39.300 --> 00:11:41.990 align:start position:0% top of this erc721 this<00:11:39.959> is<00:11:40.079> like<00:11:40.320> the<00:11:40.620> basic<00:11:40.980> erc71<00:11:41.640> as<00:11:41.820> you<00:11:41.940> can 00:11:41.990 --> 00:11:42.000 align:start position:0% this is like the basic erc71 as you can 00:11:42.000 --> 00:11:44.090 align:start position:0% this is like the basic erc71 as you can see<00:11:42.060> it's<00:11:42.180> an<00:11:42.300> abstract<00:11:42.600> contract<00:11:43.019> and<00:11:43.860> it's 00:11:44.090 --> 00:11:44.100 align:start position:0% see it's an abstract contract and it's 00:11:44.100 --> 00:11:45.650 align:start position:0% see it's an abstract contract and it's slightly<00:11:44.459> modified 00:11:45.650 --> 00:11:45.660 align:start position:0% slightly modified 00:11:45.660 --> 00:11:47.210 align:start position:0% slightly modified instead<00:11:46.260> of<00:11:46.320> having<00:11:46.500> like<00:11:46.740> a<00:11:46.920> standard 00:11:47.210 --> 00:11:47.220 align:start position:0% instead of having like a standard 00:11:47.220 --> 00:11:49.790 align:start position:0% instead of having like a standard mapping<00:11:47.519> from<00:11:47.760> like<00:11:48.060> token<00:11:48.660> ID<00:11:48.839> to<00:11:49.140> its<00:11:49.500> owner 00:11:49.790 --> 00:11:49.800 align:start position:0% mapping from like token ID to its owner 00:11:49.800 --> 00:11:52.250 align:start position:0% mapping from like token ID to its owner we<00:11:50.339> have<00:11:50.459> like<00:11:50.640> token<00:11:51.000> ID<00:11:51.180> to<00:11:51.420> token<00:11:51.899> data 00:11:52.250 --> 00:11:52.260 align:start position:0% we have like token ID to token data 00:11:52.260 --> 00:11:55.069 align:start position:0% we have like token ID to token data token<00:11:52.920> data<00:11:53.220> is<00:11:53.339> uh<00:11:53.519> structuring<00:11:54.060> this<00:11:54.720> struct 00:11:55.069 --> 00:11:55.079 align:start position:0% token data is uh structuring this struct 00:11:55.079 --> 00:11:57.829 align:start position:0% token data is uh structuring this struct is<00:11:55.440> 32<00:11:55.860> bytes<00:11:56.220> in<00:11:56.339> total<00:11:56.640> 20<00:11:57.000> bytes<00:11:57.540> is<00:11:57.660> the 00:11:57.829 --> 00:11:57.839 align:start position:0% is 32 bytes in total 20 bytes is the 00:11:57.839 --> 00:12:00.050 align:start position:0% is 32 bytes in total 20 bytes is the actual<00:11:58.140> owner<00:11:58.500> and<00:11:58.980> the<00:11:59.160> remaining<00:11:59.459> 12<00:11:59.640> bytes 00:12:00.050 --> 00:12:00.060 align:start position:0% actual owner and the remaining 12 bytes 00:12:00.060 --> 00:12:02.630 align:start position:0% actual owner and the remaining 12 bytes represent<00:12:00.420> when<00:12:00.779> the<00:12:01.019> token<00:12:01.320> was<00:12:01.440> minted 00:12:02.630 --> 00:12:02.640 align:start position:0% represent when the token was minted 00:12:02.640 --> 00:12:06.410 align:start position:0% represent when the token was minted okay<00:12:03.060> but<00:12:03.899> how<00:12:04.380> do<00:12:04.500> I<00:12:04.680> actually<00:12:05.060> prove<00:12:06.060> it<00:12:06.180> oh 00:12:06.410 --> 00:12:06.420 align:start position:0% okay but how do I actually prove it oh 00:12:06.420 --> 00:12:08.509 align:start position:0% okay but how do I actually prove it oh and<00:12:06.720> also<00:12:07.019> very<00:12:07.740> important<00:12:08.100> thing<00:12:08.279> when 00:12:08.509 --> 00:12:08.519 align:start position:0% and also very important thing when 00:12:08.519 --> 00:12:10.310 align:start position:0% and also very important thing when dealing<00:12:08.820> with<00:12:08.940> storage<00:12:09.180> layout<00:12:09.660> we<00:12:10.140> have 00:12:10.310 --> 00:12:10.320 align:start position:0% dealing with storage layout we have 00:12:10.320 --> 00:12:11.630 align:start position:0% dealing with storage layout we have something<00:12:10.500> that<00:12:10.800> is<00:12:10.920> called<00:12:11.040> like<00:12:11.220> slot 00:12:11.630 --> 00:12:11.640 align:start position:0% something that is called like slot 00:12:11.640 --> 00:12:15.350 align:start position:0% something that is called like slot indices<00:12:12.000> so<00:12:12.720> each<00:12:12.959> variable<00:12:13.500> has<00:12:14.279> a<00:12:14.640> given 00:12:15.350 --> 00:12:15.360 align:start position:0% indices so each variable has a given 00:12:15.360 --> 00:12:18.769 align:start position:0% indices so each variable has a given slot<00:12:15.779> like<00:12:16.079> in<00:12:16.260> the<00:12:16.500> some<00:12:17.459> sort<00:12:17.640> of<00:12:17.820> meta 00:12:18.769 --> 00:12:18.779 align:start position:0% slot like in the some sort of meta 00:12:18.779 --> 00:12:20.690 align:start position:0% slot like in the some sort of meta layout<00:12:19.079> I<00:12:19.380> call<00:12:19.500> it<00:12:19.680> like<00:12:19.800> that<00:12:20.040> it's<00:12:20.339> probably 00:12:20.690 --> 00:12:20.700 align:start position:0% layout I call it like that it's probably 00:12:20.700 --> 00:12:23.389 align:start position:0% layout I call it like that it's probably the<00:12:21.480> right<00:12:21.540> way<00:12:21.720> anyways 00:12:23.389 --> 00:12:23.399 align:start position:0% the right way anyways 00:12:23.399 --> 00:12:26.690 align:start position:0% the right way anyways this<00:12:24.060> mapping<00:12:24.480> it<00:12:25.380> has<00:12:25.680> like<00:12:25.860> the<00:12:26.040> slot<00:12:26.339> index 00:12:26.690 --> 00:12:26.700 align:start position:0% this mapping it has like the slot index 00:12:26.700 --> 00:12:29.690 align:start position:0% this mapping it has like the slot index too<00:12:27.000> I<00:12:27.839> will<00:12:28.019> get<00:12:28.200> to<00:12:28.500> this<00:12:28.800> part<00:12:29.040> in<00:12:29.459> a<00:12:29.579> second 00:12:29.690 --> 00:12:29.700 align:start position:0% too I will get to this part in a second 00:12:29.700 --> 00:12:32.329 align:start position:0% too I will get to this part in a second why<00:12:30.060> it's<00:12:30.240> two<00:12:30.480> and<00:12:31.440> we<00:12:31.680> have<00:12:31.800> a<00:12:31.920> mapping<00:12:32.220> from 00:12:32.329 --> 00:12:32.339 align:start position:0% why it's two and we have a mapping from 00:12:32.339 --> 00:12:35.690 align:start position:0% why it's two and we have a mapping from token<00:12:32.760> ID<00:12:32.880> so<00:12:33.720> you<00:12:34.019> win<00:12:34.320> to<00:12:34.740> 32<00:12:35.160> bytes<00:12:35.399> of<00:12:35.519> data 00:12:35.690 --> 00:12:35.700 align:start position:0% token ID so you win to 32 bytes of data 00:12:35.700 --> 00:12:37.310 align:start position:0% token ID so you win to 32 bytes of data represents<00:12:36.300> represented<00:12:36.720> as<00:12:36.839> a<00:12:36.899> structure 00:12:37.310 --> 00:12:37.320 align:start position:0% represents represented as a structure 00:12:37.320 --> 00:12:41.170 align:start position:0% represents represented as a structure just<00:12:37.620> think<00:12:37.740> of<00:12:37.920> it<00:12:38.040> as<00:12:38.160> some<00:12:38.459> bytes<00:12:39.620> okay 00:12:41.170 --> 00:12:41.180 align:start position:0% just think of it as some bytes okay 00:12:41.180 --> 00:12:45.170 align:start position:0% just think of it as some bytes okay so<00:12:42.180> uh<00:12:42.839> I<00:12:43.079> guess<00:12:43.200> most<00:12:43.500> of<00:12:43.620> you<00:12:43.740> use<00:12:43.920> hard<00:12:44.100> hot 00:12:45.170 --> 00:12:45.180 align:start position:0% so uh I guess most of you use hard hot 00:12:45.180 --> 00:12:47.329 align:start position:0% so uh I guess most of you use hard hot so<00:12:45.660> I'm<00:12:45.899> gonna<00:12:46.019> present<00:12:46.440> on<00:12:46.680> on<00:12:46.800> hard<00:12:47.100> Hut 00:12:47.329 --> 00:12:47.339 align:start position:0% so I'm gonna present on on hard Hut 00:12:47.339 --> 00:12:49.730 align:start position:0% so I'm gonna present on on hard Hut there<00:12:47.639> is<00:12:47.820> a<00:12:48.000> very<00:12:48.180> very<00:12:48.360> cool<00:12:48.660> tool<00:12:49.079> to<00:12:49.560> deal 00:12:49.730 --> 00:12:49.740 align:start position:0% there is a very very cool tool to deal 00:12:49.740 --> 00:12:50.990 align:start position:0% there is a very very cool tool to deal with<00:12:49.980> storage<00:12:50.220> layouts<00:12:50.700> it's<00:12:50.820> called 00:12:50.990 --> 00:12:51.000 align:start position:0% with storage layouts it's called 00:12:51.000 --> 00:12:53.389 align:start position:0% with storage layouts it's called obviously<00:12:51.420> hard<00:12:51.600> hot<00:12:51.839> storage<00:12:52.139> layout<00:12:52.680> this 00:12:53.389 --> 00:12:53.399 align:start position:0% obviously hard hot storage layout this 00:12:53.399 --> 00:12:55.370 align:start position:0% obviously hard hot storage layout this is<00:12:53.519> how<00:12:53.700> you<00:12:53.940> install<00:12:54.480> it<00:12:54.720> it's<00:12:54.959> literally 00:12:55.370 --> 00:12:55.380 align:start position:0% is how you install it it's literally 00:12:55.380 --> 00:12:57.710 align:start position:0% is how you install it it's literally yarn<00:12:55.860> install<00:12:56.220> hardcode<00:12:57.000> storage<00:12:57.180> layout 00:12:57.710 --> 00:12:57.720 align:start position:0% yarn install hardcode storage layout 00:12:57.720 --> 00:12:59.509 align:start position:0% yarn install hardcode storage layout you'll<00:12:58.079> add<00:12:58.320> one<00:12:58.500> comment<00:12:58.800> to<00:12:59.100> your<00:12:59.220> Hardware 00:12:59.509 --> 00:12:59.519 align:start position:0% you'll add one comment to your Hardware 00:12:59.519 --> 00:13:02.329 align:start position:0% you'll add one comment to your Hardware config<00:13:00.060> you<00:13:00.959> write<00:13:01.320> a<00:13:01.500> new<00:13:01.560> script<00:13:01.800> that 00:13:02.329 --> 00:13:02.339 align:start position:0% config you write a new script that 00:13:02.339 --> 00:13:04.069 align:start position:0% config you write a new script that contains<00:13:02.760> literally<00:13:03.120> eight<00:13:03.480> lines<00:13:03.779> of<00:13:03.899> code 00:13:04.069 --> 00:13:04.079 align:start position:0% contains literally eight lines of code 00:13:04.079 --> 00:13:06.170 align:start position:0% contains literally eight lines of code you<00:13:04.800> run<00:13:04.980> the<00:13:05.220> script<00:13:05.399> and<00:13:05.820> you<00:13:05.880> get<00:13:06.060> this 00:13:06.170 --> 00:13:06.180 align:start position:0% you run the script and you get this 00:13:06.180 --> 00:13:07.490 align:start position:0% you run the script and you get this weird<00:13:06.360> table 00:13:07.490 --> 00:13:07.500 align:start position:0% weird table 00:13:07.500 --> 00:13:09.170 align:start position:0% weird table and<00:13:08.040> what<00:13:08.279> does<00:13:08.459> it<00:13:08.579> what<00:13:08.760> does<00:13:08.940> it<00:13:09.060> really 00:13:09.170 --> 00:13:09.180 align:start position:0% and what does it what does it really 00:13:09.180 --> 00:13:11.269 align:start position:0% and what does it what does it really tell<00:13:09.480> you<00:13:09.600> and<00:13:10.079> oh<00:13:10.260> and<00:13:10.440> by<00:13:10.560> the<00:13:10.680> way<00:13:10.740> why<00:13:11.040> this 00:13:11.269 --> 00:13:11.279 align:start position:0% tell you and oh and by the way why this 00:13:11.279 --> 00:13:13.310 align:start position:0% tell you and oh and by the way why this tool<00:13:11.519> is<00:13:11.639> pretty<00:13:11.760> useful<00:13:12.120> as<00:13:12.779> you<00:13:12.959> see<00:13:13.079> this 00:13:13.310 --> 00:13:13.320 align:start position:0% tool is pretty useful as you see this 00:13:13.320 --> 00:13:16.310 align:start position:0% tool is pretty useful as you see this contract<00:13:13.680> is<00:13:13.860> abstract<00:13:14.420> so<00:13:15.420> some<00:13:16.200> other 00:13:16.310 --> 00:13:16.320 align:start position:0% contract is abstract so some other 00:13:16.320 --> 00:13:17.930 align:start position:0% contract is abstract so some other contracts 00:13:17.930 --> 00:13:17.940 align:start position:0% contracts 00:13:17.940 --> 00:13:19.670 align:start position:0% contracts again<00:13:18.300> does<00:13:18.660> it<00:13:18.839> still 00:13:19.670 --> 00:13:19.680 align:start position:0% again does it still 00:13:19.680 --> 00:13:22.009 align:start position:0% again does it still yeah<00:13:20.579> some<00:13:20.760> countries<00:13:21.120> can<00:13:21.300> inherit<00:13:21.660> from<00:13:21.839> it 00:13:22.009 --> 00:13:22.019 align:start position:0% yeah some countries can inherit from it 00:13:22.019 --> 00:13:23.990 align:start position:0% yeah some countries can inherit from it and<00:13:22.560> obviously<00:13:22.920> while<00:13:23.160> we<00:13:23.339> inherit<00:13:23.760> the 00:13:23.990 --> 00:13:24.000 align:start position:0% and obviously while we inherit the 00:13:24.000 --> 00:13:25.730 align:start position:0% and obviously while we inherit the storage<00:13:24.180> layout<00:13:24.660> I<00:13:24.839> mean<00:13:24.959> this<00:13:25.079> does<00:13:25.380> this<00:13:25.560> in 00:13:25.730 --> 00:13:25.740 align:start position:0% storage layout I mean this does this in 00:13:25.740 --> 00:13:28.310 align:start position:0% storage layout I mean this does this in synthesis<00:13:26.220> can<00:13:26.519> can<00:13:27.000> get<00:13:27.240> more<00:13:27.480> trickier 00:13:28.310 --> 00:13:28.320 align:start position:0% synthesis can can get more trickier 00:13:28.320 --> 00:13:31.009 align:start position:0% synthesis can can get more trickier because<00:13:28.800> it<00:13:29.160> also 00:13:31.009 --> 00:13:31.019 align:start position:0% because it also 00:13:31.019 --> 00:13:34.569 align:start position:0% because it also okay<00:13:31.920> so<00:13:32.459> that's 00:13:34.569 --> 00:13:34.579 align:start position:0% okay so that's 00:13:34.579 --> 00:13:37.310 align:start position:0% okay so that's it's<00:13:35.579> pretty<00:13:35.940> hard<00:13:36.120> to<00:13:36.300> coordinate<00:13:36.779> like<00:13:37.079> one 00:13:37.310 --> 00:13:37.320 align:start position:0% it's pretty hard to coordinate like one 00:13:37.320 --> 00:13:39.710 align:start position:0% it's pretty hard to coordinate like one hand<00:13:37.500> with<00:13:37.740> another<00:13:37.980> hand<00:13:38.339> even<00:13:39.300> though<00:13:39.540> I'm 00:13:39.710 --> 00:13:39.720 align:start position:0% hand with another hand even though I'm 00:13:39.720 --> 00:13:42.949 align:start position:0% hand with another hand even though I'm Italian<00:13:39.899> okay<00:13:40.320> anyways 00:13:42.949 --> 00:13:42.959 align:start position:0% 00:13:42.959 --> 00:13:46.310 align:start position:0% um<00:13:43.019> yeah<00:13:43.920> we<00:13:44.339> know<00:13:44.519> this<00:13:44.820> slot<00:13:45.240> in<00:13:45.720> the<00:13:45.839> in<00:13:46.079> the 00:13:46.310 --> 00:13:46.320 align:start position:0% um yeah we know this slot in the in the 00:13:46.320 --> 00:13:49.550 align:start position:0% um yeah we know this slot in the in the index<00:13:46.800> and<00:13:47.160> that's<00:13:47.279> how<00:13:47.700> we<00:13:47.880> get<00:13:48.180> it<00:13:48.420> we<00:13:49.260> have<00:13:49.440> a 00:13:49.550 --> 00:13:49.560 align:start position:0% index and that's how we get it we have a 00:13:49.560 --> 00:13:51.730 align:start position:0% index and that's how we get it we have a column<00:13:49.920> that<00:13:50.279> is<00:13:50.459> called 00:13:51.730 --> 00:13:51.740 align:start position:0% column that is called 00:13:51.740 --> 00:13:55.250 align:start position:0% column that is called storage<00:13:52.740> slot<00:13:53.399> and<00:13:54.060> as<00:13:54.180> you<00:13:54.360> see<00:13:54.480> underscore 00:13:55.250 --> 00:13:55.260 align:start position:0% storage slot and as you see underscore 00:13:55.260 --> 00:13:57.590 align:start position:0% storage slot and as you see underscore token<00:13:55.740> data<00:13:56.040> is<00:13:56.160> marked<00:13:56.459> as<00:13:56.579> two<00:13:56.820> and<00:13:57.480> that's 00:13:57.590 --> 00:13:57.600 align:start position:0% token data is marked as two and that's 00:13:57.600 --> 00:14:00.350 align:start position:0% token data is marked as two and that's it<00:13:57.839> okay<00:13:58.260> but<00:13:58.740> what<00:13:59.160> do<00:13:59.339> we<00:13:59.459> do<00:13:59.579> with<00:13:59.700> it<00:13:59.880> how<00:14:00.300> do 00:14:00.350 --> 00:14:00.360 align:start position:0% it okay but what do we do with it how do 00:14:00.360 --> 00:14:03.470 align:start position:0% it okay but what do we do with it how do we<00:14:00.480> get<00:14:00.660> this<00:14:01.079> storage<00:14:01.560> key 00:14:03.470 --> 00:14:03.480 align:start position:0% we get this storage key 00:14:03.480 --> 00:14:05.569 align:start position:0% we get this storage key and<00:14:04.019> yeah<00:14:04.200> that's<00:14:04.620> that's<00:14:04.920> it<00:14:05.160> let<00:14:05.339> me<00:14:05.459> check 00:14:05.569 --> 00:14:05.579 align:start position:0% and yeah that's that's it let me check 00:14:05.579 --> 00:14:08.030 align:start position:0% and yeah that's that's it let me check the<00:14:05.760> time<00:14:06.000> okay 00:14:08.030 --> 00:14:08.040 align:start position:0% the time okay 00:14:08.040 --> 00:14:09.350 align:start position:0% the time okay um<00:14:08.100> so 00:14:09.350 --> 00:14:09.360 align:start position:0% um so 00:14:09.360 --> 00:14:11.210 align:start position:0% um so a<00:14:09.839> bit<00:14:09.959> of<00:14:10.079> Hands-On<00:14:10.500> how<00:14:10.800> do<00:14:10.860> we<00:14:10.920> get<00:14:11.040> the 00:14:11.210 --> 00:14:11.220 align:start position:0% a bit of Hands-On how do we get the 00:14:11.220 --> 00:14:14.629 align:start position:0% a bit of Hands-On how do we get the Azure<00:14:11.459> searches<00:14:11.940> it<00:14:12.480> sounds<00:14:12.779> scary<00:14:13.440> and<00:14:14.220> it's 00:14:14.629 --> 00:14:14.639 align:start position:0% Azure searches it sounds scary and it's 00:14:14.639 --> 00:14:16.490 align:start position:0% Azure searches it sounds scary and it's meant<00:14:14.940> to<00:14:15.060> be<00:14:15.180> scary<00:14:15.420> so 00:14:16.490 --> 00:14:16.500 align:start position:0% meant to be scary so 00:14:16.500 --> 00:14:18.769 align:start position:0% meant to be scary so we<00:14:16.920> know<00:14:17.100> the<00:14:17.220> slot<00:14:17.459> index<00:14:17.820> the<00:14:18.180> storage<00:14:18.300> index 00:14:18.769 --> 00:14:18.779 align:start position:0% we know the slot index the storage index 00:14:18.779 --> 00:14:23.290 align:start position:0% we know the slot index the storage index I<00:14:19.440> want<00:14:19.620> to<00:14:19.740> prove<00:14:20.100> that<00:14:20.579> it's<00:14:21.120> like<00:14:21.740> 0x35 00:14:23.290 --> 00:14:23.300 align:start position:0% I want to prove that it's like 0x35 00:14:23.300 --> 00:14:28.129 align:start position:0% I want to prove that it's like 0x35 owns<00:14:24.380> with<00:14:25.380> ID<00:14:25.740> 3594 00:14:28.129 --> 00:14:28.139 align:start position:0% owns with ID 3594 00:14:28.139 --> 00:14:31.009 align:start position:0% owns with ID 3594 how<00:14:28.560> do<00:14:28.680> we<00:14:28.800> get<00:14:28.920> the<00:14:29.160> storage<00:14:29.399> key 00:14:31.009 --> 00:14:31.019 align:start position:0% how do we get the storage key 00:14:31.019 --> 00:14:35.990 align:start position:0% how do we get the storage key we<00:14:31.380> essentially<00:14:31.740> do<00:14:31.980> this<00:14:32.160> operation<00:14:32.519> so<00:14:33.180> we 00:14:35.990 --> 00:14:36.000 align:start position:0% 00:14:36.000 --> 00:14:40.069 align:start position:0% concatenate<00:14:36.959> the<00:14:37.940> slot<00:14:38.940> I<00:14:39.420> mean<00:14:39.540> the<00:14:39.720> key<00:14:39.839> in 00:14:40.069 --> 00:14:40.079 align:start position:0% concatenate the slot I mean the key in 00:14:40.079 --> 00:14:42.650 align:start position:0% concatenate the slot I mean the key in the<00:14:40.199> mapping<00:14:40.560> which<00:14:41.160> is<00:14:41.279> 35.94<00:14:42.240> because<00:14:42.480> this 00:14:42.650 --> 00:14:42.660 align:start position:0% the mapping which is 35.94 because this 00:14:42.660 --> 00:14:44.750 align:start position:0% the mapping which is 35.94 because this is<00:14:42.779> the<00:14:42.899> token<00:14:43.260> ID<00:14:43.380> as<00:14:44.100> you<00:14:44.279> know<00:14:44.399> we<00:14:44.519> have<00:14:44.639> a 00:14:44.750 --> 00:14:44.760 align:start position:0% is the token ID as you know we have a 00:14:44.760 --> 00:14:46.430 align:start position:0% is the token ID as you know we have a mapping<00:14:45.060> from<00:14:45.180> token<00:14:45.480> ID<00:14:45.600> to<00:14:45.779> token<00:14:46.139> data 00:14:46.430 --> 00:14:46.440 align:start position:0% mapping from token ID to token data 00:14:46.440 --> 00:14:48.410 align:start position:0% mapping from token ID to token data token<00:14:46.920> data<00:14:47.220> contains<00:14:47.579> the<00:14:47.699> old 00:14:48.410 --> 00:14:48.420 align:start position:0% token data contains the old 00:14:48.420 --> 00:14:52.069 align:start position:0% token data contains the old okay<00:14:48.959> so<00:14:49.440> we<00:14:50.300> concatenate<00:14:51.300> this<00:14:51.480> with<00:14:51.839> the 00:14:52.069 --> 00:14:52.079 align:start position:0% okay so we concatenate this with the 00:14:52.079 --> 00:14:55.370 align:start position:0% okay so we concatenate this with the storage<00:14:53.120> index<00:14:54.120> we<00:14:54.720> hash<00:14:54.899> it<00:14:55.139> all<00:14:55.260> together 00:14:55.370 --> 00:14:55.380 align:start position:0% storage index we hash it all together 00:14:55.380 --> 00:14:58.730 align:start position:0% storage index we hash it all together this<00:14:55.980> is<00:14:56.100> the<00:14:56.220> storage<00:14:56.399> key<00:14:56.940> that<00:14:57.300> we<00:14:57.480> have<00:14:57.740> if 00:14:58.730 --> 00:14:58.740 align:start position:0% this is the storage key that we have if 00:14:58.740 --> 00:15:00.889 align:start position:0% this is the storage key that we have if you're<00:14:58.860> interested<00:14:59.279> how<00:14:59.639> to<00:14:59.880> deal<00:15:00.540> with<00:15:00.779> it 00:15:00.889 --> 00:15:00.899 align:start position:0% you're interested how to deal with it 00:15:00.899 --> 00:15:05.509 align:start position:0% you're interested how to deal with it for<00:15:01.320> like<00:15:01.500> more<00:15:01.680> complex<00:15:02.100> mappings<00:15:03.060> and<00:15:03.300> like 00:15:05.509 --> 00:15:05.519 align:start position:0% for like more complex mappings and like 00:15:05.519 --> 00:15:07.250 align:start position:0% for like more complex mappings and like layouts 00:15:07.250 --> 00:15:07.260 align:start position:0% layouts 00:15:07.260 --> 00:15:09.230 align:start position:0% layouts track<00:15:07.680> the<00:15:07.860> solidity<00:15:08.279> documentation<00:15:08.880> it's 00:15:09.230 --> 00:15:09.240 align:start position:0% track the solidity documentation it's 00:15:09.240 --> 00:15:11.629 align:start position:0% track the solidity documentation it's explained<00:15:09.779> pretty<00:15:09.899> well<00:15:10.139> so 00:15:11.629 --> 00:15:11.639 align:start position:0% explained pretty well so 00:15:11.639 --> 00:15:14.509 align:start position:0% explained pretty well so now<00:15:12.540> that's<00:15:13.079> to<00:15:13.380> make<00:15:13.560> sure<00:15:13.800> we<00:15:14.040> got<00:15:14.279> the 00:15:14.509 --> 00:15:14.519 align:start position:0% now that's to make sure we got the 00:15:14.519 --> 00:15:17.329 align:start position:0% now that's to make sure we got the proper<00:15:14.940> storage<00:15:15.899> key<00:15:16.260> let's<00:15:16.620> just<00:15:16.920> check<00:15:17.160> it 00:15:17.329 --> 00:15:17.339 align:start position:0% proper storage key let's just check it 00:15:17.339 --> 00:15:19.610 align:start position:0% proper storage key let's just check it how<00:15:17.519> we<00:15:17.639> can<00:15:17.760> check<00:15:17.940> it<00:15:18.120> super<00:15:18.839> easy<00:15:19.079> let's 00:15:19.610 --> 00:15:19.620 align:start position:0% how we can check it super easy let's 00:15:19.620 --> 00:15:21.970 align:start position:0% how we can check it super easy let's just<00:15:19.920> make<00:15:20.100> a<00:15:20.279> one<00:15:20.459> liter<00:15:20.760> PC<00:15:21.060> call 00:15:21.970 --> 00:15:21.980 align:start position:0% just make a one liter PC call 00:15:21.980 --> 00:15:24.949 align:start position:0% just make a one liter PC call to<00:15:22.980> get<00:15:23.100> this<00:15:23.399> storage<00:15:23.760> at<00:15:24.060> some<00:15:24.240> specific<00:15:24.540> key 00:15:24.949 --> 00:15:24.959 align:start position:0% to get this storage at some specific key 00:15:24.959 --> 00:15:29.150 align:start position:0% to get this storage at some specific key is<00:15:25.639> it<00:15:26.639> if<00:15:27.300> get<00:15:27.540> storage<00:15:27.839> at<00:15:28.320> so<00:15:28.920> the 00:15:29.150 --> 00:15:29.160 align:start position:0% is it if get storage at so the 00:15:29.160 --> 00:15:31.370 align:start position:0% is it if get storage at so the parameters<00:15:29.639> we<00:15:30.480> want<00:15:30.600> to<00:15:30.720> access<00:15:30.899> the<00:15:31.199> storage 00:15:31.370 --> 00:15:31.380 align:start position:0% parameters we want to access the storage 00:15:31.380 --> 00:15:35.449 align:start position:0% parameters we want to access the storage of<00:15:31.680> what<00:15:31.920> of<00:15:32.220> the<00:15:32.579> lens<00:15:33.120> Hub<00:15:33.959> lens<00:15:34.860> cap<00:15:35.040> is<00:15:35.279> a 00:15:35.449 --> 00:15:35.459 align:start position:0% of what of the lens Hub lens cap is a 00:15:35.459 --> 00:15:37.310 align:start position:0% of what of the lens Hub lens cap is a contract<00:15:35.639> that's<00:15:35.880> essentially<00:15:36.360> is<00:15:37.139> the 00:15:37.310 --> 00:15:37.320 align:start position:0% contract that's essentially is the 00:15:37.320 --> 00:15:40.009 align:start position:0% contract that's essentially is the representation<00:15:37.800> of<00:15:37.980> these<00:15:38.160> profiles<00:15:38.660> and<00:15:39.660> its 00:15:40.009 --> 00:15:40.019 align:start position:0% representation of these profiles and its 00:15:40.019 --> 00:15:46.569 align:start position:0% representation of these profiles and its address<00:15:40.079> is<00:15:40.820> 0xdd4<00:15:41.820> and<00:15:42.300> so<00:15:42.480> on<00:15:42.720> and<00:15:43.680> this 00:15:46.569 --> 00:15:46.579 align:start position:0% 00:15:46.579 --> 00:15:50.329 align:start position:0% oh<00:15:47.579> is<00:15:48.480> it<00:15:48.600> better<00:15:48.779> oh<00:15:49.079> it's<00:15:49.320> much<00:15:49.500> better 00:15:50.329 --> 00:15:50.339 align:start position:0% oh is it better oh it's much better 00:15:50.339 --> 00:15:55.790 align:start position:0% oh is it better oh it's much better and<00:15:51.000> just<00:15:51.180> slot<00:15:51.600> the<00:15:51.980> the<00:15:52.980> storage<00:15:53.279> key<00:15:54.000> is<00:15:54.800> 0x1 00:15:55.790 --> 00:15:55.800 align:start position:0% and just slot the the storage key is 0x1 00:15:55.800 --> 00:15:57.829 align:start position:0% and just slot the the storage key is 0x1 so<00:15:56.160> essentially<00:15:56.519> that's<00:15:56.760> the<00:15:57.000> hash<00:15:57.180> that<00:15:57.480> we 00:15:57.829 --> 00:15:57.839 align:start position:0% so essentially that's the hash that we 00:15:57.839 --> 00:16:02.990 align:start position:0% so essentially that's the hash that we got<00:15:58.139> and<00:15:58.680> the<00:15:58.860> result<00:15:58.980> is<00:15:59.579> 0x00 00:16:02.990 --> 00:16:03.000 align:start position:0% 00:16:03.000 --> 00:16:05.030 align:start position:0% and<00:16:03.360> we<00:16:03.540> know<00:16:03.660> that<00:16:03.839> it's<00:16:03.959> 32<00:16:04.320> bytes<00:16:04.680> of<00:16:04.740> data 00:16:05.030 --> 00:16:05.040 align:start position:0% and we know that it's 32 bytes of data 00:16:05.040 --> 00:16:08.030 align:start position:0% and we know that it's 32 bytes of data where<00:16:05.279> we<00:16:05.459> have<00:16:05.579> 20<00:16:06.000> and<00:16:06.300> 12.<00:16:06.899> so<00:16:07.139> let's<00:16:07.440> split 00:16:08.030 --> 00:16:08.040 align:start position:0% where we have 20 and 12. so let's split 00:16:08.040 --> 00:16:10.550 align:start position:0% where we have 20 and 12. so let's split it<00:16:08.160> into<00:16:08.339> 12<00:16:08.519> and<00:16:08.760> 20<00:16:08.940> bytes<00:16:09.420> and<00:16:09.959> what<00:16:10.139> we<00:16:10.380> have 00:16:10.550 --> 00:16:10.560 align:start position:0% it into 12 and 20 bytes and what we have 00:16:10.560 --> 00:16:13.009 align:start position:0% it into 12 and 20 bytes and what we have is 00:16:13.009 --> 00:16:13.019 align:start position:0% is 00:16:13.019 --> 00:16:16.370 align:start position:0% is some<00:16:13.740> number<00:16:13.980> like<00:16:14.339> you<00:16:14.519> can<00:16:14.820> see<00:16:15.000> 0x<00:16:15.720> a<00:16:16.139> lot<00:16:16.260> of 00:16:16.370 --> 00:16:16.380 align:start position:0% some number like you can see 0x a lot of 00:16:16.380 --> 00:16:20.509 align:start position:0% some number like you can see 0x a lot of zeros<00:16:16.800> then<00:16:17.160> 62<00:16:17.760> till<00:16:18.480> d<00:16:19.320> and<00:16:19.980> this<00:16:20.220> looks<00:16:20.459> like 00:16:20.509 --> 00:16:20.519 align:start position:0% zeros then 62 till d and this looks like 00:16:20.519 --> 00:16:22.730 align:start position:0% zeros then 62 till d and this looks like a<00:16:20.699> small<00:16:20.820> number<00:16:21.120> so<00:16:21.660> apparently<00:16:22.199> it<00:16:22.440> is<00:16:22.560> a 00:16:22.730 --> 00:16:22.740 align:start position:0% a small number so apparently it is a 00:16:22.740 --> 00:16:25.790 align:start position:0% a small number so apparently it is a timestamp<00:16:23.100> and<00:16:23.639> the<00:16:23.820> second<00:16:23.940> part<00:16:24.240> is<00:16:24.420> like<00:16:24.600> 35 00:16:25.790 --> 00:16:25.800 align:start position:0% timestamp and the second part is like 35 00:16:25.800 --> 00:16:29.210 align:start position:0% timestamp and the second part is like 35 7<00:16:26.699> and<00:16:27.180> it's<00:16:27.360> literally<00:16:27.660> our<00:16:27.959> address<00:16:28.199> so<00:16:28.980> we 00:16:29.210 --> 00:16:29.220 align:start position:0% 7 and it's literally our address so we 00:16:29.220 --> 00:16:32.030 align:start position:0% 7 and it's literally our address so we got<00:16:29.399> it<00:16:29.579> correct<00:16:29.699> we<00:16:30.120> have<00:16:30.360> the<00:16:30.600> proper 00:16:32.030 --> 00:16:32.040 align:start position:0% got it correct we have the proper 00:16:32.040 --> 00:16:36.590 align:start position:0% got it correct we have the proper storage<00:16:32.519> key<00:16:32.880> cool 00:16:36.590 --> 00:16:36.600 align:start position:0% 00:16:36.600 --> 00:16:39.290 align:start position:0% but<00:16:37.259> how<00:16:38.040> do<00:16:38.220> we<00:16:38.339> actually<00:16:38.459> get<00:16:38.880> to<00:16:39.060> storage 00:16:39.290 --> 00:16:39.300 align:start position:0% but how do we actually get to storage 00:16:39.300 --> 00:16:42.590 align:start position:0% but how do we actually get to storage proofs<00:16:39.839> so<00:16:40.680> there<00:16:41.459> are<00:16:41.699> standardized<00:16:42.180> method 00:16:42.590 --> 00:16:42.600 align:start position:0% proofs so there are standardized method 00:16:42.600 --> 00:16:44.930 align:start position:0% proofs so there are standardized method in<00:16:42.959> like<00:16:43.079> the<00:16:43.320> Json<00:16:43.740> or<00:16:43.920> PC<00:16:44.279> standard<00:16:44.699> for 00:16:44.930 --> 00:16:44.940 align:start position:0% in like the Json or PC standard for 00:16:44.940 --> 00:16:47.509 align:start position:0% in like the Json or PC standard for ethereum<00:16:45.420> appliance<00:16:45.899> and<00:16:46.740> this<00:16:47.040> method<00:16:47.279> is 00:16:47.509 --> 00:16:47.519 align:start position:0% ethereum appliance and this method is 00:16:47.519 --> 00:16:49.610 align:start position:0% ethereum appliance and this method is called<00:16:47.639> eth<00:16:47.940> get<00:16:48.300> proof<00:16:48.660> which<00:16:49.139> essentially 00:16:49.610 --> 00:16:49.620 align:start position:0% called eth get proof which essentially 00:16:49.620 --> 00:16:53.749 align:start position:0% called eth get proof which essentially given<00:16:50.360> the<00:16:51.360> contract<00:16:51.839> address<00:16:52.019> so<00:16:52.500> I<00:16:53.459> better 00:16:53.749 --> 00:16:53.759 align:start position:0% given the contract address so I better 00:16:53.759 --> 00:16:55.670 align:start position:0% given the contract address so I better call<00:16:54.120> it<00:16:54.300> account<00:16:54.540> address<00:16:54.899> in<00:16:55.259> this<00:16:55.440> specific 00:16:55.670 --> 00:16:55.680 align:start position:0% call it account address in this specific 00:16:55.680 --> 00:16:58.009 align:start position:0% call it account address in this specific case<00:16:55.980> allows<00:16:56.699> us<00:16:56.820> to<00:16:57.000> generate<00:16:57.360> a<00:16:57.480> state<00:16:57.660> proof 00:16:58.009 --> 00:16:58.019 align:start position:0% case allows us to generate a state proof 00:16:58.019 --> 00:17:01.370 align:start position:0% case allows us to generate a state proof and<00:16:58.980> the<00:16:59.220> last<00:16:59.639> argument<00:17:00.000> I<00:17:00.420> mean<00:17:00.540> the<00:17:01.019> sorry 00:17:01.370 --> 00:17:01.380 align:start position:0% and the last argument I mean the sorry 00:17:01.380 --> 00:17:03.350 align:start position:0% and the last argument I mean the sorry the<00:17:01.620> second<00:17:01.740> argument<00:17:02.160> is<00:17:02.759> an<00:17:02.880> array<00:17:03.180> that 00:17:03.350 --> 00:17:03.360 align:start position:0% the second argument is an array that 00:17:03.360 --> 00:17:06.110 align:start position:0% the second argument is an array that contains<00:17:03.660> all<00:17:03.899> this<00:17:04.079> Storage<00:17:04.640> storage<00:17:05.640> keys 00:17:06.110 --> 00:17:06.120 align:start position:0% contains all this Storage storage keys 00:17:06.120 --> 00:17:08.929 align:start position:0% contains all this Storage storage keys that<00:17:06.480> we<00:17:06.660> want<00:17:06.839> to<00:17:06.959> prove<00:17:07.679> uh<00:17:08.579> there<00:17:08.819> is 00:17:08.929 --> 00:17:08.939 align:start position:0% that we want to prove uh there is 00:17:08.939 --> 00:17:10.510 align:start position:0% that we want to prove uh there is another<00:17:09.059> argument<00:17:09.540> which<00:17:09.780> is 00:17:10.510 --> 00:17:10.520 align:start position:0% another argument which is 00:17:10.520 --> 00:17:12.890 align:start position:0% another argument which is 0x1a<00:17:11.520> it's<00:17:11.880> essentially<00:17:12.299> the<00:17:12.480> block<00:17:12.600> number 00:17:12.890 --> 00:17:12.900 align:start position:0% 0x1a it's essentially the block number 00:17:12.900 --> 00:17:15.650 align:start position:0% 0x1a it's essentially the block number for<00:17:13.319> which<00:17:13.559> we<00:17:13.740> prove<00:17:13.980> the<00:17:14.160> state 00:17:15.650 --> 00:17:15.660 align:start position:0% for which we prove the state 00:17:15.660 --> 00:17:18.470 align:start position:0% for which we prove the state um<00:17:15.720> yeah<00:17:16.079> let's<00:17:16.559> call<00:17:16.799> this<00:17:17.040> method<00:17:17.400> oh<00:17:18.120> by<00:17:18.360> the 00:17:18.470 --> 00:17:18.480 align:start position:0% um yeah let's call this method oh by the 00:17:18.480 --> 00:17:20.210 align:start position:0% um yeah let's call this method oh by the way<00:17:18.600> uh<00:17:18.959> you<00:17:19.140> might<00:17:19.260> have<00:17:19.380> a<00:17:19.500> question<00:17:19.620> how<00:17:19.980> do 00:17:20.210 --> 00:17:20.220 align:start position:0% way uh you might have a question how do 00:17:20.220 --> 00:17:22.789 align:start position:0% way uh you might have a question how do we<00:17:20.339> deal<00:17:20.579> with<00:17:21.000> this<00:17:21.299> method<00:17:21.660> on<00:17:21.900> non-evm 00:17:22.789 --> 00:17:22.799 align:start position:0% we deal with this method on non-evm 00:17:22.799 --> 00:17:26.329 align:start position:0% we deal with this method on non-evm chains<00:17:23.419> because<00:17:24.419> for<00:17:24.780> example<00:17:25.160> on<00:17:26.160> some 00:17:26.329 --> 00:17:26.339 align:start position:0% chains because for example on some 00:17:26.339 --> 00:17:28.069 align:start position:0% chains because for example on some specific<00:17:26.699> Roll-Ups<00:17:27.360> this<00:17:27.540> method<00:17:27.780> is<00:17:27.900> like 00:17:28.069 --> 00:17:28.079 align:start position:0% specific Roll-Ups this method is like 00:17:28.079 --> 00:17:30.650 align:start position:0% specific Roll-Ups this method is like not<00:17:28.199> supported<00:17:28.679> actually<00:17:29.220> it's<00:17:29.460> not<00:17:29.760> a<00:17:30.240> big 00:17:30.650 --> 00:17:30.660 align:start position:0% not supported actually it's not a big 00:17:30.660 --> 00:17:32.390 align:start position:0% not supported actually it's not a big deal<00:17:30.840> because<00:17:31.260> if<00:17:31.559> you<00:17:31.679> think<00:17:31.799> of<00:17:31.919> it<00:17:32.040> we<00:17:32.280> just 00:17:32.390 --> 00:17:32.400 align:start position:0% deal because if you think of it we just 00:17:32.400 --> 00:17:34.669 align:start position:0% deal because if you think of it we just need<00:17:32.640> the<00:17:32.820> database<00:17:33.299> and<00:17:34.020> on<00:17:34.260> top<00:17:34.380> of<00:17:34.500> this 00:17:34.669 --> 00:17:34.679 align:start position:0% need the database and on top of this 00:17:34.679 --> 00:17:36.110 align:start position:0% need the database and on top of this database<00:17:35.039> we<00:17:35.280> can<00:17:35.400> literally<00:17:35.640> build<00:17:35.940> this 00:17:36.110 --> 00:17:36.120 align:start position:0% database we can literally build this 00:17:36.120 --> 00:17:38.630 align:start position:0% database we can literally build this method<00:17:36.720> we<00:17:37.260> just<00:17:37.620> need<00:17:37.799> to<00:17:37.860> know<00:17:38.039> how<00:17:38.340> the 00:17:38.630 --> 00:17:38.640 align:start position:0% method we just need to know how the 00:17:38.640 --> 00:17:41.409 align:start position:0% method we just need to know how the storage<00:17:39.539> is<00:17:39.840> constructed 00:17:41.409 --> 00:17:41.419 align:start position:0% storage is constructed 00:17:41.419 --> 00:17:45.409 align:start position:0% storage is constructed okay<00:17:42.419> this<00:17:43.020> is<00:17:43.080> the<00:17:43.260> proof<00:17:43.559> it<00:17:44.340> looks<00:17:44.580> scary<00:17:44.700> it 00:17:45.409 --> 00:17:45.419 align:start position:0% okay this is the proof it looks scary it 00:17:45.419 --> 00:17:47.750 align:start position:0% okay this is the proof it looks scary it is<00:17:45.539> scary<00:17:45.780> this<00:17:46.740> entire<00:17:47.039> object<00:17:47.400> is<00:17:47.580> four 00:17:47.750 --> 00:17:47.760 align:start position:0% is scary this entire object is four 00:17:47.760 --> 00:17:50.810 align:start position:0% is scary this entire object is four kilobytes<00:17:48.240> of<00:17:48.419> data<00:17:48.780> and<00:17:49.500> now<00:17:49.740> I<00:17:50.340> mentioned 00:17:50.810 --> 00:17:50.820 align:start position:0% kilobytes of data and now I mentioned 00:17:50.820 --> 00:17:53.630 align:start position:0% kilobytes of data and now I mentioned before<00:17:51.179> that<00:17:51.840> the<00:17:52.500> state<00:17:52.980> is<00:17:53.280> like<00:17:53.400> a<00:17:53.520> two 00:17:53.630 --> 00:17:53.640 align:start position:0% before that the state is like a two 00:17:53.640 --> 00:17:55.730 align:start position:0% before that the state is like a two level<00:17:53.820> structure<00:17:54.419> first<00:17:55.020> we<00:17:55.200> have<00:17:55.320> a<00:17:55.440> proof 00:17:55.730 --> 00:17:55.740 align:start position:0% level structure first we have a proof 00:17:55.740 --> 00:17:57.770 align:start position:0% level structure first we have a proof for<00:17:55.860> the<00:17:55.980> account<00:17:56.100> itself<00:17:56.640> and<00:17:57.360> now<00:17:57.480> we<00:17:57.600> have 00:17:57.770 --> 00:17:57.780 align:start position:0% for the account itself and now we have 00:17:57.780 --> 00:18:00.710 align:start position:0% for the account itself and now we have the<00:17:57.960> proof<00:17:58.380> for<00:17:59.280> the<00:17:59.640> storage<00:17:59.820> I<00:18:00.240> mean<00:18:00.360> for<00:18:00.539> the 00:18:00.710 --> 00:18:00.720 align:start position:0% the proof for the storage I mean for the 00:18:00.720 --> 00:18:02.270 align:start position:0% the proof for the storage I mean for the actual<00:18:00.900> storage<00:18:01.140> slot 00:18:02.270 --> 00:18:02.280 align:start position:0% actual storage slot 00:18:02.280 --> 00:18:05.690 align:start position:0% actual storage slot it<00:18:02.760> is<00:18:02.880> scary<00:18:03.059> it's<00:18:03.780> meant<00:18:04.080> to<00:18:04.200> be<00:18:04.320> scary<00:18:04.700> one 00:18:05.690 --> 00:18:05.700 align:start position:0% it is scary it's meant to be scary one 00:18:05.700 --> 00:18:08.950 align:start position:0% it is scary it's meant to be scary one proof<00:18:06.120> is<00:18:06.299> like<00:18:06.539> more<00:18:06.780> or<00:18:06.960> less<00:18:07.020> 600<00:18:07.799> bytes 00:18:08.950 --> 00:18:08.960 align:start position:0% proof is like more or less 600 bytes 00:18:08.960 --> 00:18:11.810 align:start position:0% proof is like more or less 600 bytes 700<00:18:09.960> bytes<00:18:10.380> it<00:18:10.500> really<00:18:10.679> depends<00:18:11.280> like<00:18:11.460> bigger 00:18:11.810 --> 00:18:11.820 align:start position:0% 700 bytes it really depends like bigger 00:18:11.820 --> 00:18:13.669 align:start position:0% 700 bytes it really depends like bigger the<00:18:11.940> storage<00:18:12.120> is<00:18:12.480> than<00:18:12.720> bigger<00:18:13.140> the<00:18:13.260> proof<00:18:13.559> is 00:18:13.669 --> 00:18:13.679 align:start position:0% the storage is than bigger the proof is 00:18:13.679 --> 00:18:15.590 align:start position:0% the storage is than bigger the proof is and<00:18:14.220> also<00:18:14.400> more<00:18:14.520> accounts<00:18:15.000> we<00:18:15.179> have<00:18:15.299> than 00:18:15.590 --> 00:18:15.600 align:start position:0% and also more accounts we have than 00:18:15.600 --> 00:18:17.870 align:start position:0% and also more accounts we have than bigger<00:18:16.080> the<00:18:16.260> account<00:18:16.500> proof<00:18:16.980> is 00:18:17.870 --> 00:18:17.880 align:start position:0% bigger the account proof is 00:18:17.880 --> 00:18:21.470 align:start position:0% bigger the account proof is so<00:18:18.539> that's<00:18:18.780> a<00:18:18.960> lot<00:18:19.020> of<00:18:19.140> cool<00:18:19.260> data<00:18:19.740> if<00:18:20.520> if<00:18:21.240> you 00:18:21.470 --> 00:18:21.480 align:start position:0% so that's a lot of cool data if if you 00:18:21.480 --> 00:18:24.770 align:start position:0% so that's a lot of cool data if if you can<00:18:21.539> imagine<00:18:21.780> you<00:18:22.500> can<00:18:22.679> imagine<00:18:23.179> uh<00:18:24.179> and<00:18:24.600> yeah 00:18:24.770 --> 00:18:24.780 align:start position:0% can imagine you can imagine uh and yeah 00:18:24.780 --> 00:18:26.810 align:start position:0% can imagine you can imagine uh and yeah that's<00:18:25.200> that's<00:18:25.380> pretty<00:18:25.679> bad<00:18:25.980> why<00:18:26.340> because<00:18:26.580> we 00:18:26.810 --> 00:18:26.820 align:start position:0% that's that's pretty bad why because we 00:18:26.820 --> 00:18:28.850 align:start position:0% that's that's pretty bad why because we need<00:18:27.000> to<00:18:27.120> pause<00:18:27.419> this<00:18:27.660> proof<00:18:28.020> on<00:18:28.260> the<00:18:28.380> Chain<00:18:28.559> so 00:18:28.850 --> 00:18:28.860 align:start position:0% need to pause this proof on the Chain so 00:18:28.860 --> 00:18:31.490 align:start position:0% need to pause this proof on the Chain so it's<00:18:29.039> a<00:18:29.280> lot<00:18:29.400> of<00:18:29.520> cool<00:18:29.640> data<00:18:30.120> but<00:18:30.720> okay<00:18:30.960> let's 00:18:31.490 --> 00:18:31.500 align:start position:0% it's a lot of cool data but okay let's 00:18:31.500 --> 00:18:33.529 align:start position:0% it's a lot of cool data but okay let's let's<00:18:31.740> try 00:18:33.529 --> 00:18:33.539 align:start position:0% let's try 00:18:33.539 --> 00:18:36.110 align:start position:0% let's try what's<00:18:33.960> going<00:18:34.260> to<00:18:34.320> be<00:18:34.440> the<00:18:34.559> cost<00:18:34.740> on<00:18:35.039> like<00:18:35.400> an 00:18:36.110 --> 00:18:36.120 align:start position:0% what's going to be the cost on like an 00:18:36.120 --> 00:18:38.990 align:start position:0% what's going to be the cost on like an evm<00:18:36.600> chain<00:18:36.780> that's<00:18:37.559> the<00:18:37.799> cost<00:18:37.919> it's<00:18:38.220> like<00:18:38.400> 600 00:18:38.990 --> 00:18:39.000 align:start position:0% evm chain that's the cost it's like 600 00:18:39.000 --> 00:18:43.250 align:start position:0% evm chain that's the cost it's like 600 K<00:18:39.299> of<00:18:39.539> gas<00:18:39.720> that's<00:18:40.620> a<00:18:40.860> lot<00:18:41.179> that<00:18:42.179> kills<00:18:42.960> almost 00:18:43.250 --> 00:18:43.260 align:start position:0% K of gas that's a lot that kills almost 00:18:43.260 --> 00:18:45.710 align:start position:0% K of gas that's a lot that kills almost every<00:18:43.799> single<00:18:44.280> application<00:18:45.059> that<00:18:45.480> you<00:18:45.539> want 00:18:45.710 --> 00:18:45.720 align:start position:0% every single application that you want 00:18:45.720 --> 00:18:47.870 align:start position:0% every single application that you want to<00:18:45.840> build<00:18:45.960> on<00:18:46.200> top<00:18:46.380> of<00:18:46.500> this<00:18:46.679> nice<00:18:46.799> primitive 00:18:47.870 --> 00:18:47.880 align:start position:0% to build on top of this nice primitive 00:18:47.880 --> 00:18:50.330 align:start position:0% to build on top of this nice primitive so<00:18:48.660> it's<00:18:49.080> pretty<00:18:49.260> bad<00:18:49.500> and<00:18:49.740> why<00:18:49.919> is<00:18:50.039> it<00:18:50.220> that 00:18:50.330 --> 00:18:50.340 align:start position:0% so it's pretty bad and why is it that 00:18:50.340 --> 00:18:53.330 align:start position:0% so it's pretty bad and why is it that bad<00:18:50.660> so<00:18:51.660> I<00:18:52.260> explained<00:18:52.679> on<00:18:52.980> the<00:18:53.100> high<00:18:53.160> level 00:18:53.330 --> 00:18:53.340 align:start position:0% bad so I explained on the high level 00:18:53.340 --> 00:18:55.070 align:start position:0% bad so I explained on the high level what<00:18:53.640> Merkel<00:18:54.000> trees<00:18:54.240> are<00:18:54.360> America<00:18:54.539> Patricia 00:18:55.070 --> 00:18:55.080 align:start position:0% what Merkel trees are America Patricia 00:18:55.080 --> 00:18:57.289 align:start position:0% what Merkel trees are America Patricia trees<00:18:55.679> are<00:18:55.860> on<00:18:56.340> ethereum<00:18:56.760> we<00:18:56.880> use<00:18:57.000> Marco 00:18:57.289 --> 00:18:57.299 align:start position:0% trees are on ethereum we use Marco 00:18:57.299 --> 00:18:59.270 align:start position:0% trees are on ethereum we use Marco Patricia<00:18:57.720> trees<00:18:58.080> and<00:18:58.620> essentially<00:18:58.860> there<00:18:59.100> is 00:18:59.270 --> 00:18:59.280 align:start position:0% Patricia trees and essentially there is 00:18:59.280 --> 00:19:01.250 align:start position:0% Patricia trees and essentially there is a<00:18:59.400> trade-off<00:18:59.760> that<00:19:00.179> when<00:19:00.660> using<00:19:00.960> Miracle 00:19:01.250 --> 00:19:01.260 align:start position:0% a trade-off that when using Miracle 00:19:01.260 --> 00:19:02.870 align:start position:0% a trade-off that when using Miracle Patricia<00:19:01.620> trees<00:19:01.799> the<00:19:01.980> proof<00:19:02.160> is<00:19:02.280> a<00:19:02.520> slightly 00:19:02.870 --> 00:19:02.880 align:start position:0% Patricia trees the proof is a slightly 00:19:02.880 --> 00:19:06.350 align:start position:0% Patricia trees the proof is a slightly bigger<00:19:03.240> it's<00:19:04.020> like<00:19:04.440> harder<00:19:04.980> to<00:19:05.460> decode<00:19:06.240> it 00:19:06.350 --> 00:19:06.360 align:start position:0% bigger it's like harder to decode it 00:19:06.360 --> 00:19:07.909 align:start position:0% bigger it's like harder to decode it because<00:19:06.539> actually<00:19:06.720> we<00:19:07.020> need<00:19:07.140> to<00:19:07.200> do<00:19:07.380> some<00:19:07.679> a 00:19:07.909 --> 00:19:07.919 align:start position:0% because actually we need to do some a 00:19:07.919 --> 00:19:09.890 align:start position:0% because actually we need to do some a bit<00:19:08.039> of<00:19:08.220> decoding<00:19:08.640> there 00:19:09.890 --> 00:19:09.900 align:start position:0% bit of decoding there 00:19:09.900 --> 00:19:12.830 align:start position:0% bit of decoding there um<00:19:09.960> but<00:19:10.620> we<00:19:10.980> need<00:19:11.220> to<00:19:11.340> do<00:19:11.520> less<00:19:11.700> hashing<00:19:12.240> so 00:19:12.830 --> 00:19:12.840 align:start position:0% um but we need to do less hashing so 00:19:12.840 --> 00:19:14.870 align:start position:0% um but we need to do less hashing so this<00:19:13.080> is<00:19:13.140> a<00:19:13.320> trade-off<00:19:13.679> but<00:19:14.160> depending<00:19:14.580> where 00:19:14.870 --> 00:19:14.880 align:start position:0% this is a trade-off but depending where 00:19:14.880 --> 00:19:16.850 align:start position:0% this is a trade-off but depending where we<00:19:15.000> actually<00:19:15.120> verify<00:19:15.600> this<00:19:15.780> proof<00:19:16.080> it<00:19:16.679> might 00:19:16.850 --> 00:19:16.860 align:start position:0% we actually verify this proof it might 00:19:16.860 --> 00:19:19.430 align:start position:0% we actually verify this proof it might be<00:19:16.980> more<00:19:17.100> feasible<00:19:17.460> to<00:19:17.640> verify<00:19:18.059> like<00:19:19.020> prove 00:19:19.430 --> 00:19:19.440 align:start position:0% be more feasible to verify like prove 00:19:19.440 --> 00:19:20.810 align:start position:0% be more feasible to verify like prove that<00:19:19.500> is<00:19:19.620> based<00:19:19.799> on<00:19:19.860> Marco<00:19:20.100> Patricia<00:19:20.400> trees<00:19:20.700> or 00:19:20.810 --> 00:19:20.820 align:start position:0% that is based on Marco Patricia trees or 00:19:20.820 --> 00:19:22.070 align:start position:0% that is based on Marco Patricia trees or Miracle<00:19:21.179> trees 00:19:22.070 --> 00:19:22.080 align:start position:0% Miracle trees 00:19:22.080 --> 00:19:25.250 align:start position:0% Miracle trees okay<00:19:22.880> but<00:19:23.880> there<00:19:24.179> is<00:19:24.360> a<00:19:24.419> solution 00:19:25.250 --> 00:19:25.260 align:start position:0% okay but there is a solution 00:19:25.260 --> 00:19:28.250 align:start position:0% okay but there is a solution and<00:19:25.799> the<00:19:25.919> solution<00:19:26.220> is<00:19:26.460> what<00:19:26.880> if<00:19:27.120> we<00:19:27.299> snarkify 00:19:28.250 --> 00:19:28.260 align:start position:0% and the solution is what if we snarkify 00:19:28.260 --> 00:19:31.010 align:start position:0% and the solution is what if we snarkify such<00:19:28.860> such<00:19:29.160> a<00:19:29.400> proof<00:19:29.700> and<00:19:30.299> we<00:19:30.480> verify<00:19:30.840> this 00:19:31.010 --> 00:19:31.020 align:start position:0% such such a proof and we verify this 00:19:31.020 --> 00:19:33.289 align:start position:0% such such a proof and we verify this truth<00:19:31.320> inside<00:19:31.500> the<00:19:31.679> snark<00:19:32.460> why<00:19:32.880> is<00:19:33.059> it<00:19:33.179> cool 00:19:33.289 --> 00:19:33.299 align:start position:0% truth inside the snark why is it cool 00:19:33.299 --> 00:19:35.690 align:start position:0% truth inside the snark why is it cool because<00:19:33.720> we<00:19:34.620> can<00:19:34.799> like<00:19:34.980> let's<00:19:35.220> say<00:19:35.400> that<00:19:35.580> I'm 00:19:35.690 --> 00:19:35.700 align:start position:0% because we can like let's say that I'm 00:19:35.700 --> 00:19:38.090 align:start position:0% because we can like let's say that I'm gonna<00:19:35.820> verify<00:19:36.360> this<00:19:36.539> proof<00:19:36.840> inside<00:19:37.020> the<00:19:37.320> graph 00:19:38.090 --> 00:19:38.100 align:start position:0% gonna verify this proof inside the graph 00:19:38.100 --> 00:19:41.090 align:start position:0% gonna verify this proof inside the graph crop<00:19:38.520> 16<00:19:38.640> circuit 00:19:41.090 --> 00:19:41.100 align:start position:0% crop 16 circuit 00:19:41.100 --> 00:19:43.010 align:start position:0% crop 16 circuit um<00:19:41.160> and<00:19:41.520> yeah<00:19:41.640> the<00:19:42.059> verification<00:19:42.539> costs<00:19:43.020> more 00:19:43.010 --> 00:19:43.020 align:start position:0% um and yeah the verification costs more 00:19:43.020 --> 00:19:46.370 align:start position:0% um and yeah the verification costs more or<00:19:43.200> less<00:19:43.260> like<00:19:43.880> 210k<00:19:44.880> gas<00:19:45.179> the<00:19:45.780> proof<00:19:46.020> is<00:19:46.140> like 00:19:46.370 --> 00:19:46.380 align:start position:0% or less like 210k gas the proof is like 00:19:46.380 --> 00:19:49.310 align:start position:0% or less like 210k gas the proof is like way<00:19:46.679> less<00:19:46.919> than<00:19:47.220> 600<00:19:47.820> bytes<00:19:48.360> so<00:19:48.780> it's<00:19:48.960> good<00:19:49.140> so 00:19:49.310 --> 00:19:49.320 align:start position:0% way less than 600 bytes so it's good so 00:19:49.320 --> 00:19:50.870 align:start position:0% way less than 600 bytes so it's good so essentially<00:19:49.740> get<00:19:49.980> rid<00:19:50.100> of<00:19:50.280> the<00:19:50.400> cold<00:19:50.520> data 00:19:50.870 --> 00:19:50.880 align:start position:0% essentially get rid of the cold data 00:19:50.880 --> 00:19:53.270 align:start position:0% essentially get rid of the cold data because<00:19:51.000> the<00:19:51.240> proof<00:19:51.480> itself<00:19:51.720> can<00:19:52.020> be<00:19:52.140> the 00:19:53.270 --> 00:19:53.280 align:start position:0% because the proof itself can be the 00:19:53.280 --> 00:19:56.090 align:start position:0% because the proof itself can be the private<00:19:54.000> input<00:19:54.240> to<00:19:54.419> the<00:19:54.600> Circuit 00:19:56.090 --> 00:19:56.100 align:start position:0% private input to the Circuit 00:19:56.100 --> 00:19:58.669 align:start position:0% private input to the Circuit um<00:19:56.160> yeah<00:19:56.580> we<00:19:57.000> can<00:19:57.120> like<00:19:57.299> use<00:19:57.600> multiple<00:19:58.260> proving 00:19:58.669 --> 00:19:58.679 align:start position:0% um yeah we can like use multiple proving 00:19:58.679 --> 00:20:00.650 align:start position:0% um yeah we can like use multiple proving system<00:19:58.860> depending<00:19:59.400> on<00:19:59.640> the<00:19:59.880> on<00:20:00.299> the<00:20:00.419> actual 00:20:00.650 --> 00:20:00.660 align:start position:0% system depending on the on the actual 00:20:00.660 --> 00:20:03.529 align:start position:0% system depending on the on the actual use<00:20:00.900> case<00:20:01.140> and<00:20:01.799> now<00:20:01.980> why<00:20:02.340> is<00:20:02.640> it<00:20:02.820> like<00:20:03.240> very 00:20:03.529 --> 00:20:03.539 align:start position:0% use case and now why is it like very 00:20:03.539 --> 00:20:05.330 align:start position:0% use case and now why is it like very very<00:20:03.660> cool<00:20:03.960> so<00:20:04.200> first<00:20:04.380> of<00:20:04.559> all<00:20:04.620> it<00:20:04.980> removes 00:20:05.330 --> 00:20:05.340 align:start position:0% very cool so first of all it removes 00:20:05.340 --> 00:20:08.990 align:start position:0% very cool so first of all it removes call<00:20:05.520> data<00:20:06.299> second<00:20:07.140> model<00:20:07.440> it<00:20:08.280> allows<00:20:08.640> us<00:20:08.700> to 00:20:08.990 --> 00:20:09.000 align:start position:0% call data second model it allows us to 00:20:09.000 --> 00:20:11.330 align:start position:0% call data second model it allows us to deal<00:20:09.240> with<00:20:09.480> very<00:20:09.840> UNH<00:20:10.320> unfriendly<00:20:10.919> hashing 00:20:11.330 --> 00:20:11.340 align:start position:0% deal with very UNH unfriendly hashing 00:20:11.340 --> 00:20:14.330 align:start position:0% deal with very UNH unfriendly hashing functions<00:20:11.760> or<00:20:12.299> the<00:20:12.480> evm<00:20:12.900> these<00:20:13.740> the<00:20:13.919> ones<00:20:14.160> that 00:20:14.330 --> 00:20:14.340 align:start position:0% functions or the evm these the ones that 00:20:14.340 --> 00:20:16.490 align:start position:0% functions or the evm these the ones that we<00:20:14.820> don't<00:20:14.940> have<00:20:15.120> pre-compiled<00:20:15.780> for<00:20:15.900> like 00:20:16.490 --> 00:20:16.500 align:start position:0% we don't have pre-compiled for like 00:20:16.500 --> 00:20:19.190 align:start position:0% we don't have pre-compiled for like let's<00:20:16.860> say<00:20:17.039> Peterson 00:20:19.190 --> 00:20:19.200 align:start position:0% let's say Peterson 00:20:19.200 --> 00:20:21.590 align:start position:0% let's say Peterson um<00:20:19.400> so<00:20:20.400> it<00:20:20.520> might<00:20:20.700> be<00:20:20.820> like<00:20:21.000> super<00:20:21.179> expensive 00:20:21.590 --> 00:20:21.600 align:start position:0% um so it might be like super expensive 00:20:21.600 --> 00:20:23.210 align:start position:0% um so it might be like super expensive to<00:20:21.780> verify<00:20:22.020> such<00:20:22.260> a<00:20:22.440> proof<00:20:22.679> on<00:20:22.740> the<00:20:22.860> evm 00:20:23.210 --> 00:20:23.220 align:start position:0% to verify such a proof on the evm 00:20:23.220 --> 00:20:24.289 align:start position:0% to verify such a proof on the evm because<00:20:23.400> first<00:20:23.580> of<00:20:23.760> all<00:20:23.760> that's<00:20:23.940> a<00:20:24.120> lot<00:20:24.240> of 00:20:24.289 --> 00:20:24.299 align:start position:0% because first of all that's a lot of 00:20:24.299 --> 00:20:26.270 align:start position:0% because first of all that's a lot of cool<00:20:24.419> data<00:20:24.900> and<00:20:25.320> the<00:20:25.440> hashing<00:20:25.799> function<00:20:26.039> is 00:20:26.270 --> 00:20:26.280 align:start position:0% cool data and the hashing function is 00:20:26.280 --> 00:20:28.490 align:start position:0% cool data and the hashing function is pretty<00:20:26.460> like<00:20:26.580> unfriendly<00:20:27.179> but<00:20:27.840> what<00:20:28.140> if<00:20:28.320> we 00:20:28.490 --> 00:20:28.500 align:start position:0% pretty like unfriendly but what if we 00:20:28.500 --> 00:20:30.169 align:start position:0% pretty like unfriendly but what if we can<00:20:28.679> like<00:20:28.860> do<00:20:29.160> it<00:20:29.280> inside<00:20:29.460> the<00:20:29.700> snark<00:20:29.940> and<00:20:30.120> just 00:20:30.169 --> 00:20:30.179 align:start position:0% can like do it inside the snark and just 00:20:30.179 --> 00:20:33.529 align:start position:0% can like do it inside the snark and just verify<00:20:30.539> a<00:20:30.720> snark<00:20:31.039> and<00:20:32.039> yeah<00:20:32.400> so<00:20:33.059> another 00:20:33.529 --> 00:20:33.539 align:start position:0% verify a snark and yeah so another 00:20:33.539 --> 00:20:36.409 align:start position:0% verify a snark and yeah so another benefit<00:20:34.160> this<00:20:35.160> really<00:20:35.400> really<00:20:35.760> helps<00:20:36.240> in 00:20:36.409 --> 00:20:36.419 align:start position:0% benefit this really really helps in 00:20:36.419 --> 00:20:38.630 align:start position:0% benefit this really really helps in obstructing<00:20:37.020> the<00:20:37.260> way<00:20:37.380> how<00:20:37.919> we<00:20:38.160> verify<00:20:38.520> this 00:20:38.630 --> 00:20:38.640 align:start position:0% obstructing the way how we verify this 00:20:38.640 --> 00:20:40.130 align:start position:0% obstructing the way how we verify this proofs<00:20:39.059> because<00:20:39.360> you<00:20:39.539> don't<00:20:39.720> need<00:20:39.900> to<00:20:40.020> have 00:20:40.130 --> 00:20:40.140 align:start position:0% proofs because you don't need to have 00:20:40.140 --> 00:20:42.950 align:start position:0% proofs because you don't need to have like<00:20:40.380> one<00:20:40.679> generalized<00:20:41.280> verifier<00:20:41.760> for<00:20:42.600> each 00:20:42.950 --> 00:20:42.960 align:start position:0% like one generalized verifier for each 00:20:42.960 --> 00:20:45.490 align:start position:0% like one generalized verifier for each type<00:20:43.380> of<00:20:43.860> of<00:20:44.100> proof 00:20:45.490 --> 00:20:45.500 align:start position:0% type of of proof 00:20:45.500 --> 00:20:47.750 align:start position:0% type of of proof but<00:20:46.500> you<00:20:46.679> can<00:20:46.799> essentially<00:20:47.160> obstruct<00:20:47.520> it 00:20:47.750 --> 00:20:47.760 align:start position:0% but you can essentially obstruct it 00:20:47.760 --> 00:20:50.450 align:start position:0% but you can essentially obstruct it behind<00:20:48.120> behind<00:20:48.780> the<00:20:48.900> behind<00:20:49.320> the<00:20:49.380> snark<00:20:49.679> which 00:20:50.450 --> 00:20:50.460 align:start position:0% behind behind the behind the snark which 00:20:50.460 --> 00:20:53.090 align:start position:0% behind behind the behind the snark which is<00:20:50.580> which<00:20:50.880> is<00:20:51.120> great<00:20:51.299> uh<00:20:52.260> these<00:20:52.559> numbers<00:20:52.679> were 00:20:53.090 --> 00:20:53.100 align:start position:0% is which is great uh these numbers were 00:20:53.100 --> 00:20:56.150 align:start position:0% is which is great uh these numbers were taken<00:20:53.580> from<00:20:53.820> a<00:20:54.179> very<00:20:54.360> nice<00:20:54.660> uh<00:20:55.320> article 00:20:56.150 --> 00:20:56.160 align:start position:0% taken from a very nice uh article 00:20:56.160 --> 00:20:59.930 align:start position:0% taken from a very nice uh article written<00:20:57.059> by<00:20:57.360> a16z<00:20:58.140> like<00:20:58.500> a<00:20:58.679> bunch<00:20:58.919> of<00:20:59.100> uh<00:20:59.640> a<00:20:59.820> few 00:20:59.930 --> 00:20:59.940 align:start position:0% written by a16z like a bunch of uh a few 00:20:59.940 --> 00:21:01.789 align:start position:0% written by a16z like a bunch of uh a few a<00:21:00.059> few<00:21:00.240> months<00:21:00.419> ago 00:21:01.789 --> 00:21:01.799 align:start position:0% a few months ago 00:21:01.799 --> 00:21:04.070 align:start position:0% a few months ago um<00:21:01.919> yeah<00:21:02.520> and<00:21:02.760> I<00:21:02.880> think<00:21:03.059> that's<00:21:03.299> pretty<00:21:03.840> much 00:21:04.070 --> 00:21:04.080 align:start position:0% um yeah and I think that's pretty much 00:21:04.080 --> 00:21:07.669 align:start position:0% um yeah and I think that's pretty much it<00:21:04.380> let's<00:21:04.679> get<00:21:04.980> to<00:21:05.100> the<00:21:05.280> next<00:21:05.520> slide<00:21:05.880> so 00:21:07.669 --> 00:21:07.679 align:start position:0% it let's get to the next slide so 00:21:07.679 --> 00:21:10.370 align:start position:0% it let's get to the next slide so synchronous<00:21:08.460> cross<00:21:08.640> layer<00:21:09.000> State<00:21:09.240> access<00:21:09.539> so 00:21:10.370 --> 00:21:10.380 align:start position:0% synchronous cross layer State access so 00:21:10.380 --> 00:21:12.289 align:start position:0% synchronous cross layer State access so how<00:21:10.559> can<00:21:10.679> actually<00:21:10.919> a<00:21:11.280> control<00:21:11.400> deployed<00:21:12.000> on 00:21:12.289 --> 00:21:12.299 align:start position:0% how can actually a control deployed on 00:21:12.299 --> 00:21:14.570 align:start position:0% how can actually a control deployed on some<00:21:12.780> layer<00:21:13.140> access<00:21:13.500> the<00:21:13.860> state<00:21:14.039> of<00:21:14.280> another 00:21:14.570 --> 00:21:14.580 align:start position:0% some layer access the state of another 00:21:14.580 --> 00:21:17.029 align:start position:0% some layer access the state of another L2<00:21:15.360> or<00:21:15.539> L1 00:21:17.029 --> 00:21:17.039 align:start position:0% L2 or L1 00:21:17.039 --> 00:21:20.029 align:start position:0% L2 or L1 so<00:21:17.760> I<00:21:18.059> mentioned<00:21:18.419> that<00:21:18.720> we<00:21:19.260> always<00:21:19.440> need<00:21:19.860> the 00:21:20.029 --> 00:21:20.039 align:start position:0% so I mentioned that we always need the 00:21:20.039 --> 00:21:22.010 align:start position:0% so I mentioned that we always need the state<00:21:20.220> route<00:21:20.520> but<00:21:20.940> because<00:21:21.240> all<00:21:21.600> of<00:21:21.780> these 00:21:22.010 --> 00:21:22.020 align:start position:0% state route but because all of these 00:21:22.020 --> 00:21:24.350 align:start position:0% state route but because all of these systems<00:21:22.500> have<00:21:22.980> a<00:21:23.280> native<00:21:23.640> messaging<00:21:24.179> system 00:21:24.350 --> 00:21:24.360 align:start position:0% systems have a native messaging system 00:21:24.360 --> 00:21:26.450 align:start position:0% systems have a native messaging system we<00:21:25.080> can<00:21:25.200> send<00:21:25.380> the<00:21:25.559> small<00:21:25.740> commitments<00:21:26.340> like 00:21:26.450 --> 00:21:26.460 align:start position:0% we can send the small commitments like 00:21:26.460 --> 00:21:29.029 align:start position:0% we can send the small commitments like for<00:21:26.640> example<00:21:26.940> the<00:21:27.120> blockage<00:21:27.480> to<00:21:28.320> like<00:21:28.559> L1 00:21:29.029 --> 00:21:29.039 align:start position:0% for example the blockage to like L1 00:21:29.039 --> 00:21:32.270 align:start position:0% for example the blockage to like L1 usually<00:21:30.000> it<00:21:30.360> goes<00:21:30.659> off-road<00:21:31.140> one<00:21:31.380> and<00:21:32.039> and 00:21:32.270 --> 00:21:32.280 align:start position:0% usually it goes off-road one and and 00:21:32.280 --> 00:21:34.070 align:start position:0% usually it goes off-road one and and yeah<00:21:32.460> we<00:21:32.700> can<00:21:32.820> like<00:21:32.940> enroll<00:21:33.299> it<00:21:33.539> or<00:21:33.720> send<00:21:33.900> the 00:21:34.070 --> 00:21:34.080 align:start position:0% yeah we can like enroll it or send the 00:21:34.080 --> 00:21:35.750 align:start position:0% yeah we can like enroll it or send the state<00:21:34.200> through<00:21:34.440> directly<00:21:34.860> and<00:21:35.280> also<00:21:35.460> we<00:21:35.640> don't 00:21:35.750 --> 00:21:35.760 align:start position:0% state through directly and also we don't 00:21:35.760 --> 00:21:37.669 align:start position:0% state through directly and also we don't need<00:21:35.940> to<00:21:36.120> rely<00:21:36.419> on<00:21:36.539> messaging<00:21:36.900> but<00:21:37.140> we<00:21:37.320> can<00:21:37.440> for 00:21:37.669 --> 00:21:37.679 align:start position:0% need to rely on messaging but we can for 00:21:37.679 --> 00:21:40.310 align:start position:0% need to rely on messaging but we can for example<00:21:37.980> uh<00:21:38.820> rely<00:21:39.120> on<00:21:39.240> the<00:21:39.360> fact<00:21:39.539> that<00:21:39.780> polygon 00:21:40.310 --> 00:21:40.320 align:start position:0% example uh rely on the fact that polygon 00:21:40.320 --> 00:21:42.409 align:start position:0% example uh rely on the fact that polygon is<00:21:40.559> like<00:21:40.740> a<00:21:40.919> commit<00:21:41.220> chain<00:21:41.400> and<00:21:41.700> all<00:21:42.179> these 00:21:42.409 --> 00:21:42.419 align:start position:0% is like a commit chain and all these 00:21:42.419 --> 00:21:44.450 align:start position:0% is like a commit chain and all these Roll-Ups<00:21:42.960> like<00:21:43.080> commit<00:21:43.500> from<00:21:43.980> time<00:21:44.100> to<00:21:44.280> time 00:21:44.450 --> 00:21:44.460 align:start position:0% Roll-Ups like commit from time to time 00:21:44.460 --> 00:21:47.930 align:start position:0% Roll-Ups like commit from time to time they're<00:21:44.820> like<00:21:45.200> batches<00:21:46.200> and<00:21:46.860> and<00:21:47.039> so<00:21:47.280> on<00:21:47.460> so 00:21:47.930 --> 00:21:47.940 align:start position:0% they're like batches and and so on so 00:21:47.940 --> 00:21:49.490 align:start position:0% they're like batches and and so on so this<00:21:48.120> is<00:21:48.240> like<00:21:48.419> pretty<00:21:48.600> important<00:21:49.020> and<00:21:49.200> we 00:21:49.490 --> 00:21:49.500 align:start position:0% this is like pretty important and we 00:21:49.500 --> 00:21:51.710 align:start position:0% this is like pretty important and we sort<00:21:49.919> of<00:21:50.039> can<00:21:50.280> get<00:21:50.520> the<00:21:50.760> commitment<00:21:51.179> from 00:21:51.710 --> 00:21:51.720 align:start position:0% sort of can get the commitment from 00:21:51.720 --> 00:21:54.289 align:start position:0% sort of can get the commitment from which<00:21:51.960> we'll<00:21:52.200> recreate<00:21:52.799> the<00:21:52.919> state<00:21:53.299> directly 00:21:54.289 --> 00:21:54.299 align:start position:0% which we'll recreate the state directly 00:21:54.299 --> 00:21:55.970 align:start position:0% which we'll recreate the state directly on<00:21:54.539> on<00:21:54.720> another<00:21:54.960> one<00:21:55.260> and<00:21:55.380> then<00:21:55.500> send<00:21:55.679> it<00:21:55.860> to 00:21:55.970 --> 00:21:55.980 align:start position:0% on on another one and then send it to 00:21:55.980 --> 00:21:58.010 align:start position:0% on on another one and then send it to another 00:21:58.010 --> 00:21:58.020 align:start position:0% another 00:21:58.020 --> 00:22:00.649 align:start position:0% another um so<00:21:58.700> if 00:22:00.649 --> 00:22:00.659 align:start position:0% um so if 00:22:00.659 --> 00:22:03.230 align:start position:0% um so if let's<00:22:01.260> say<00:22:01.440> polygon<00:22:01.919> commits<00:22:02.400> another<00:22:02.640> one<00:22:03.000> I 00:22:03.230 --> 00:22:03.240 align:start position:0% let's say polygon commits another one I 00:22:03.240 --> 00:22:05.029 align:start position:0% let's say polygon commits another one I can<00:22:03.419> send<00:22:03.539> this<00:22:03.780> commitment<00:22:04.200> then<00:22:04.440> to<00:22:04.620> start<00:22:04.740> I 00:22:05.029 --> 00:22:05.039 align:start position:0% can send this commitment then to start I 00:22:05.039 --> 00:22:06.049 align:start position:0% can send this commitment then to start I don't<00:22:05.159> start<00:22:05.280> how<00:22:05.520> to<00:22:05.580> do<00:22:05.700> the<00:22:05.820> actual 00:22:06.049 --> 00:22:06.059 align:start position:0% don't start how to do the actual 00:22:06.059 --> 00:22:07.789 align:start position:0% don't start how to do the actual verification 00:22:07.789 --> 00:22:07.799 align:start position:0% verification 00:22:07.799 --> 00:22:11.330 align:start position:0% verification cool<00:22:08.220> so<00:22:09.000> now<00:22:09.260> how<00:22:10.260> do<00:22:10.440> we<00:22:10.559> actually<00:22:10.799> do<00:22:11.159> that 00:22:11.330 --> 00:22:11.340 align:start position:0% cool so now how do we actually do that 00:22:11.340 --> 00:22:13.430 align:start position:0% cool so now how do we actually do that so<00:22:11.640> let's<00:22:11.820> break<00:22:12.059> the<00:22:12.299> entire<00:22:12.539> flow<00:22:12.960> into<00:22:13.140> like 00:22:13.430 --> 00:22:13.440 align:start position:0% so let's break the entire flow into like 00:22:13.440 --> 00:22:14.750 align:start position:0% so let's break the entire flow into like smallest<00:22:13.860> pieces 00:22:14.750 --> 00:22:14.760 align:start position:0% smallest pieces 00:22:14.760 --> 00:22:16.549 align:start position:0% smallest pieces so<00:22:15.059> the<00:22:15.240> flow<00:22:15.419> is<00:22:15.600> the<00:22:15.720> following<00:22:16.020> we<00:22:16.320> need<00:22:16.440> to 00:22:16.549 --> 00:22:16.559 align:start position:0% so the flow is the following we need to 00:22:16.559 --> 00:22:18.649 align:start position:0% so the flow is the following we need to have<00:22:16.740> access<00:22:16.980> to<00:22:17.280> the<00:22:17.400> commitment<00:22:17.880> which<00:22:18.480> is 00:22:18.649 --> 00:22:18.659 align:start position:0% have access to the commitment which is 00:22:18.659 --> 00:22:21.289 align:start position:0% have access to the commitment which is either<00:22:18.840> a<00:22:19.140> block<00:22:19.260> hush<00:22:19.620> or<00:22:19.740> a<00:22:19.860> state<00:22:19.980> route<00:22:20.299> and 00:22:21.289 --> 00:22:21.299 align:start position:0% either a block hush or a state route and 00:22:21.299 --> 00:22:23.510 align:start position:0% either a block hush or a state route and again<00:22:21.539> we<00:22:21.780> can<00:22:21.960> get<00:22:22.080> it<00:22:22.260> or<00:22:22.559> I<00:22:22.860> either<00:22:23.220> by 00:22:23.510 --> 00:22:23.520 align:start position:0% again we can get it or I either by 00:22:23.520 --> 00:22:25.610 align:start position:0% again we can get it or I either by sending<00:22:23.820> a<00:22:23.940> message<00:22:24.260> relying<00:22:25.260> on<00:22:25.320> the<00:22:25.500> fact 00:22:25.610 --> 00:22:25.620 align:start position:0% sending a message relying on the fact 00:22:25.620 --> 00:22:26.510 align:start position:0% sending a message relying on the fact that 00:22:26.510 --> 00:22:26.520 align:start position:0% that 00:22:26.520 --> 00:22:29.029 align:start position:0% that is<00:22:27.179> this<00:22:27.419> chain<00:22:27.539> commit<00:22:27.960> so<00:22:28.200> in<00:22:28.500> a<00:22:28.620> sense<00:22:28.740> it's 00:22:29.029 --> 00:22:29.039 align:start position:0% is this chain commit so in a sense it's 00:22:29.039 --> 00:22:31.190 align:start position:0% is this chain commit so in a sense it's still<00:22:29.220> a<00:22:29.400> message<00:22:29.580> we<00:22:30.360> can<00:22:30.539> relate<00:22:30.900> in<00:22:31.080> an 00:22:31.190 --> 00:22:31.200 align:start position:0% still a message we can relate in an 00:22:31.200 --> 00:22:33.770 align:start position:0% still a message we can relate in an optimistic<00:22:31.620> manner<00:22:31.980> or<00:22:32.580> we<00:22:32.940> can<00:22:33.059> go<00:22:33.299> even<00:22:33.539> more 00:22:33.770 --> 00:22:33.780 align:start position:0% optimistic manner or we can go even more 00:22:33.780 --> 00:22:36.890 align:start position:0% optimistic manner or we can go even more crazy<00:22:34.020> and<00:22:34.320> verify<00:22:34.679> the<00:22:34.799> entire<00:22:35.039> consensus 00:22:36.890 --> 00:22:36.900 align:start position:0% crazy and verify the entire consensus 00:22:36.900 --> 00:22:39.169 align:start position:0% crazy and verify the entire consensus okay<00:22:37.440> so<00:22:37.799> this<00:22:37.980> is<00:22:38.100> Step<00:22:38.340> number<00:22:38.520> one<00:22:38.760> we<00:22:39.059> need 00:22:39.169 --> 00:22:39.179 align:start position:0% okay so this is Step number one we need 00:22:39.179 --> 00:22:41.810 align:start position:0% okay so this is Step number one we need to<00:22:39.299> get<00:22:39.419> the<00:22:39.600> commitment<00:22:39.900> step<00:22:40.440> number<00:22:40.679> two<00:22:40.980> we 00:22:41.810 --> 00:22:41.820 align:start position:0% to get the commitment step number two we 00:22:41.820 --> 00:22:43.789 align:start position:0% to get the commitment step number two we need<00:22:42.000> to<00:22:42.299> somehow<00:22:42.720> access<00:22:43.020> the<00:22:43.380> state<00:22:43.559> route 00:22:43.789 --> 00:22:43.799 align:start position:0% need to somehow access the state route 00:22:43.799 --> 00:22:45.830 align:start position:0% need to somehow access the state route so<00:22:44.039> the<00:22:44.159> commitments<00:22:44.640> of<00:22:44.760> the<00:22:44.880> state<00:22:45.059> from 00:22:45.830 --> 00:22:45.840 align:start position:0% so the commitments of the state from 00:22:45.840 --> 00:22:47.570 align:start position:0% so the commitments of the state from like<00:22:46.080> a<00:22:46.200> previous<00:22:46.380> block<00:22:46.679> or<00:22:46.919> the<00:22:47.100> actual<00:22:47.340> blog 00:22:47.570 --> 00:22:47.580 align:start position:0% like a previous block or the actual blog 00:22:47.580 --> 00:22:48.649 align:start position:0% like a previous block or the actual blog because<00:22:47.760> keep<00:22:48.059> in<00:22:48.179> mind<00:22:48.299> that<00:22:48.419> these 00:22:48.649 --> 00:22:48.659 align:start position:0% because keep in mind that these 00:22:48.659 --> 00:22:50.870 align:start position:0% because keep in mind that these commitments<00:22:49.140> are<00:22:49.260> only<00:22:49.500> block<00:22:49.799> hashes<00:22:50.280> and<00:22:50.700> we 00:22:50.870 --> 00:22:50.880 align:start position:0% commitments are only block hashes and we 00:22:50.880 --> 00:22:52.669 align:start position:0% commitments are only block hashes and we block<00:22:51.000> hashes<00:22:51.419> we<00:22:51.600> can<00:22:51.720> recreate<00:22:52.140> headers<00:22:52.500> but 00:22:52.669 --> 00:22:52.679 align:start position:0% block hashes we can recreate headers but 00:22:52.679 --> 00:22:55.490 align:start position:0% block hashes we can recreate headers but we<00:22:52.919> cannot<00:22:53.400> access<00:22:53.580> the<00:22:53.880> state 00:22:55.490 --> 00:22:55.500 align:start position:0% we cannot access the state 00:22:55.500 --> 00:22:58.190 align:start position:0% we cannot access the state okay<00:22:55.919> so<00:22:56.460> once<00:22:57.000> we<00:22:57.059> have<00:22:57.179> the<00:22:57.360> state<00:22:57.480> route<00:22:57.780> we 00:22:58.190 --> 00:22:58.200 align:start position:0% okay so once we have the state route we 00:22:58.200 --> 00:23:00.710 align:start position:0% okay so once we have the state route we obviously<00:22:58.500> need<00:22:58.679> to<00:22:58.860> verify<00:22:59.340> this<00:22:59.880> state 00:23:00.710 --> 00:23:00.720 align:start position:0% obviously need to verify this state 00:23:00.720 --> 00:23:04.070 align:start position:0% obviously need to verify this state storage<00:23:01.559> groups<00:23:02.580> okay<00:23:03.120> and<00:23:03.600> there<00:23:03.900> are 00:23:04.070 --> 00:23:04.080 align:start position:0% storage groups okay and there are 00:23:04.080 --> 00:23:06.409 align:start position:0% storage groups okay and there are multiple<00:23:04.620> features<00:23:04.980> to<00:23:05.220> do<00:23:05.340> that<00:23:05.520> all<00:23:06.179> of<00:23:06.299> them 00:23:06.409 --> 00:23:06.419 align:start position:0% multiple features to do that all of them 00:23:06.419 --> 00:23:08.690 align:start position:0% multiple features to do that all of them come<00:23:06.659> with<00:23:06.900> some<00:23:07.080> trade-offs<00:23:07.559> and<00:23:08.039> let's<00:23:08.340> go 00:23:08.690 --> 00:23:08.700 align:start position:0% come with some trade-offs and let's go 00:23:08.700 --> 00:23:11.770 align:start position:0% come with some trade-offs and let's go through<00:23:09.000> all<00:23:09.419> these<00:23:09.600> approaches 00:23:11.770 --> 00:23:11.780 align:start position:0% through all these approaches 00:23:11.780 --> 00:23:17.210 align:start position:0% through all these approaches so<00:23:12.780> approach<00:23:13.440> number<00:23:13.740> one<00:23:14.100> messaging<00:23:15.539> so<00:23:16.440> I 00:23:17.210 --> 00:23:17.220 align:start position:0% so approach number one messaging so I 00:23:17.220 --> 00:23:21.409 align:start position:0% so approach number one messaging so I can<00:23:17.400> send<00:23:17.640> a<00:23:17.940> message<00:23:18.179> from<00:23:18.900> let's<00:23:19.260> say 00:23:21.409 --> 00:23:21.419 align:start position:0% can send a message from let's say 00:23:21.419 --> 00:23:24.049 align:start position:0% can send a message from let's say optimism<00:23:22.340> to 00:23:24.049 --> 00:23:24.059 align:start position:0% optimism to 00:23:24.059 --> 00:23:26.870 align:start position:0% optimism to Eternal<00:23:24.360> one<00:23:24.659> I<00:23:25.320> can<00:23:25.440> get<00:23:25.620> the<00:23:25.799> opco<00:23:26.220> I<00:23:26.520> can<00:23:26.760> get 00:23:26.870 --> 00:23:26.880 align:start position:0% Eternal one I can get the opco I can get 00:23:26.880 --> 00:23:28.490 align:start position:0% Eternal one I can get the opco I can get the<00:23:27.000> blockers<00:23:27.299> by<00:23:27.539> just<00:23:27.780> calling<00:23:28.080> the<00:23:28.260> proper 00:23:28.490 --> 00:23:28.500 align:start position:0% the blockers by just calling the proper 00:23:28.500 --> 00:23:32.149 align:start position:0% the blockers by just calling the proper op<00:23:28.679> code<00:23:29.059> and<00:23:30.059> and<00:23:30.419> I<00:23:30.720> get<00:23:31.020> it<00:23:31.200> take<00:23:31.740> some<00:23:31.919> time 00:23:32.149 --> 00:23:32.159 align:start position:0% op code and and I get it take some time 00:23:32.159 --> 00:23:34.370 align:start position:0% op code and and I get it take some time but<00:23:32.520> still<00:23:32.760> I<00:23:33.059> get<00:23:33.240> it<00:23:33.360> this<00:23:33.960> is<00:23:34.080> approach 00:23:34.370 --> 00:23:34.380 align:start position:0% but still I get it this is approach 00:23:34.380 --> 00:23:36.710 align:start position:0% but still I get it this is approach number<00:23:34.559> one<00:23:34.860> so<00:23:35.520> we<00:23:35.820> rely<00:23:36.179> on<00:23:36.299> the<00:23:36.419> built-in 00:23:36.710 --> 00:23:36.720 align:start position:0% number one so we rely on the built-in 00:23:36.720 --> 00:23:39.230 align:start position:0% number one so we rely on the built-in messaging<00:23:37.140> system<00:23:37.320> which<00:23:38.280> is<00:23:38.460> I<00:23:38.760> think<00:23:38.880> Fair 00:23:39.230 --> 00:23:39.240 align:start position:0% messaging system which is I think Fair 00:23:39.240 --> 00:23:41.330 align:start position:0% messaging system which is I think Fair because<00:23:39.659> the<00:23:40.020> security<00:23:40.200> of<00:23:40.559> it<00:23:40.679> is<00:23:40.860> equal<00:23:41.100> to 00:23:41.330 --> 00:23:41.340 align:start position:0% because the security of it is equal to 00:23:41.340 --> 00:23:43.010 align:start position:0% because the security of it is equal to the<00:23:41.520> security<00:23:41.640> of<00:23:42.000> the<00:23:42.120> roll<00:23:42.240> up<00:23:42.480> and<00:23:42.840> if 00:23:43.010 --> 00:23:43.020 align:start position:0% the security of the roll up and if 00:23:43.020 --> 00:23:44.270 align:start position:0% the security of the roll up and if you're<00:23:43.080> deploying<00:23:43.500> an<00:23:43.559> application<00:23:43.919> of<00:23:44.159> this 00:23:44.270 --> 00:23:44.280 align:start position:0% you're deploying an application of this 00:23:44.280 --> 00:23:48.350 align:start position:0% you're deploying an application of this rollup<00:23:44.700> it's<00:23:45.240> a<00:23:45.360> fair<00:23:45.480> assumption<00:23:46.200> to<00:23:46.559> do<00:23:46.679> so 00:23:48.350 --> 00:23:48.360 align:start position:0% rollup it's a fair assumption to do so 00:23:48.360 --> 00:23:51.529 align:start position:0% rollup it's a fair assumption to do so um<00:23:48.440> yeah<00:23:49.440> it<00:23:50.100> doesn't<00:23:50.340> oh<00:23:51.000> they<00:23:51.240> don't<00:23:51.360> know 00:23:51.529 --> 00:23:51.539 align:start position:0% um yeah it doesn't oh they don't know 00:23:51.539 --> 00:23:53.750 align:start position:0% um yeah it doesn't oh they don't know about<00:23:51.720> the<00:23:51.960> downsides<00:23:52.500> so<00:23:53.039> the<00:23:53.280> message<00:23:53.400> must 00:23:53.750 --> 00:23:53.760 align:start position:0% about the downsides so the message must 00:23:53.760 --> 00:23:55.370 align:start position:0% about the downsides so the message must be<00:23:53.880> delivered<00:23:54.240> so<00:23:54.419> it<00:23:54.600> introduces<00:23:55.140> a 00:23:55.370 --> 00:23:55.380 align:start position:0% be delivered so it introduces a 00:23:55.380 --> 00:23:57.710 align:start position:0% be delivered so it introduces a significant<00:23:55.799> delay<00:23:56.299> especially<00:23:57.299> when 00:23:57.710 --> 00:23:57.720 align:start position:0% significant delay especially when 00:23:57.720 --> 00:23:59.390 align:start position:0% significant delay especially when dealing<00:23:58.140> with<00:23:58.200> the<00:23:58.380> withdrawal<00:23:58.860> period<00:23:59.159> in 00:23:59.390 --> 00:23:59.400 align:start position:0% dealing with the withdrawal period in 00:23:59.400 --> 00:24:02.029 align:start position:0% dealing with the withdrawal period in the<00:23:59.520> in<00:23:59.700> in<00:23:59.880> the<00:24:00.059> middle<00:24:00.240> uh<00:24:01.200> and<00:24:01.440> it<00:24:01.620> requires 00:24:02.029 --> 00:24:02.039 align:start position:0% the in in the middle uh and it requires 00:24:02.039 --> 00:24:04.669 align:start position:0% the in in the middle uh and it requires we<00:24:02.400> it<00:24:03.120> requires<00:24:03.600> interacting<00:24:04.140> with<00:24:04.260> multiple 00:24:04.669 --> 00:24:04.679 align:start position:0% we it requires interacting with multiple 00:24:04.679 --> 00:24:06.110 align:start position:0% we it requires interacting with multiple layers<00:24:05.039> so<00:24:05.220> first<00:24:05.400> you<00:24:05.580> need<00:24:05.760> to<00:24:05.820> send<00:24:05.940> a 00:24:06.110 --> 00:24:06.120 align:start position:0% layers so first you need to send a 00:24:06.120 --> 00:24:07.190 align:start position:0% layers so first you need to send a message<00:24:06.240> and<00:24:06.480> then<00:24:06.600> actually<00:24:06.780> you<00:24:06.960> need<00:24:07.080> to 00:24:07.190 --> 00:24:07.200 align:start position:0% message and then actually you need to 00:24:07.200 --> 00:24:08.330 align:start position:0% message and then actually you need to consume<00:24:07.679> it 00:24:08.330 --> 00:24:08.340 align:start position:0% consume it 00:24:08.340 --> 00:24:09.950 align:start position:0% consume it so<00:24:08.880> it's 00:24:09.950 --> 00:24:09.960 align:start position:0% so it's 00:24:09.960 --> 00:24:12.529 align:start position:0% so it's it's<00:24:10.020> not<00:24:10.620> ideal 00:24:12.529 --> 00:24:12.539 align:start position:0% it's not ideal 00:24:12.539 --> 00:24:15.230 align:start position:0% it's not ideal but<00:24:13.260> the<00:24:13.679> trust<00:24:13.980> assumptions<00:24:14.400> are<00:24:14.760> pretty 00:24:15.230 --> 00:24:15.240 align:start position:0% but the trust assumptions are pretty 00:24:15.240 --> 00:24:17.450 align:start position:0% but the trust assumptions are pretty occasional 00:24:17.450 --> 00:24:17.460 align:start position:0% occasional 00:24:17.460 --> 00:24:20.630 align:start position:0% occasional another<00:24:18.000> approach<00:24:18.539> consensus<00:24:19.320> validation 00:24:20.630 --> 00:24:20.640 align:start position:0% another approach consensus validation 00:24:20.640 --> 00:24:23.270 align:start position:0% another approach consensus validation by<00:24:21.240> the<00:24:21.360> way<00:24:21.419> this<00:24:21.900> like<00:24:22.200> Gremlin<00:24:22.799> is<00:24:23.039> supposed 00:24:23.270 --> 00:24:23.280 align:start position:0% by the way this like Gremlin is supposed 00:24:23.280 --> 00:24:26.029 align:start position:0% by the way this like Gremlin is supposed to<00:24:23.460> verify<00:24:23.880> a<00:24:24.059> bunch<00:24:24.240> of<00:24:24.360> PLS<00:24:24.840> signatures<00:24:25.380> I<00:24:25.740> I 00:24:26.029 --> 00:24:26.039 align:start position:0% to verify a bunch of PLS signatures I I 00:24:26.039 --> 00:24:29.750 align:start position:0% to verify a bunch of PLS signatures I I hope<00:24:26.280> it's<00:24:27.260> self-explanatory<00:24:28.260> uh<00:24:29.220> okay<00:24:29.400> so 00:24:29.750 --> 00:24:29.760 align:start position:0% hope it's self-explanatory uh okay so 00:24:29.760 --> 00:24:32.870 align:start position:0% hope it's self-explanatory uh okay so maybe<00:24:30.240> a<00:24:30.539> few<00:24:30.780> a<00:24:31.140> bit<00:24:31.440> of<00:24:31.620> an<00:24:31.740> intro 00:24:32.870 --> 00:24:32.880 align:start position:0% maybe a few a bit of an intro 00:24:32.880 --> 00:24:35.570 align:start position:0% maybe a few a bit of an intro um<00:24:32.940> right<00:24:33.299> now<00:24:33.480> we<00:24:33.780> have<00:24:34.020> POS<00:24:34.500> as<00:24:35.039> the<00:24:35.280> native 00:24:35.570 --> 00:24:35.580 align:start position:0% um right now we have POS as the native 00:24:35.580 --> 00:24:37.669 align:start position:0% um right now we have POS as the native like<00:24:35.820> consensus<00:24:36.360> algorithm<00:24:36.960> and<00:24:37.320> ethereum 00:24:37.669 --> 00:24:37.679 align:start position:0% like consensus algorithm and ethereum 00:24:37.679 --> 00:24:39.830 align:start position:0% like consensus algorithm and ethereum which<00:24:38.220> is<00:24:38.400> pretty<00:24:38.580> great<00:24:38.940> because<00:24:39.179> verifying 00:24:39.830 --> 00:24:39.840 align:start position:0% which is pretty great because verifying 00:24:39.840 --> 00:24:43.250 align:start position:0% which is pretty great because verifying the<00:24:39.960> consensus<00:24:40.380> is<00:24:40.860> finally<00:24:41.960> doable<00:24:42.960> because 00:24:43.250 --> 00:24:43.260 align:start position:0% the consensus is finally doable because 00:24:43.260 --> 00:24:45.710 align:start position:0% the consensus is finally doable because before<00:24:43.679> like<00:24:44.159> verifying<00:24:44.760> the<00:24:45.240> hashing 00:24:45.710 --> 00:24:45.720 align:start position:0% before like verifying the hashing 00:24:45.720 --> 00:24:47.510 align:start position:0% before like verifying the hashing function<00:24:45.960> eth<00:24:46.320> hash<00:24:46.799> which<00:24:47.039> was<00:24:47.159> used<00:24:47.340> for 00:24:47.510 --> 00:24:47.520 align:start position:0% function eth hash which was used for 00:24:47.520 --> 00:24:50.270 align:start position:0% function eth hash which was used for proof<00:24:47.880> of<00:24:47.940> work<00:24:48.059> was<00:24:48.299> very<00:24:48.539> memory<00:24:48.900> intense<00:24:49.320> so 00:24:50.270 --> 00:24:50.280 align:start position:0% proof of work was very memory intense so 00:24:50.280 --> 00:24:53.690 align:start position:0% proof of work was very memory intense so not<00:24:50.700> possible<00:24:51.059> to<00:24:51.240> do<00:24:51.360> inside<00:24:51.539> the<00:24:51.900> shark 00:24:53.690 --> 00:24:53.700 align:start position:0% not possible to do inside the shark 00:24:53.700 --> 00:24:56.270 align:start position:0% not possible to do inside the shark um on<00:24:54.360> chain<00:24:54.600> directly<00:24:55.140> so<00:24:55.440> it<00:24:55.679> was<00:24:55.860> almost 00:24:56.270 --> 00:24:56.280 align:start position:0% um on chain directly so it was almost 00:24:56.280 --> 00:24:58.190 align:start position:0% um on chain directly so it was almost impossible<00:24:56.760> to<00:24:57.059> do<00:24:57.179> so 00:24:58.190 --> 00:24:58.200 align:start position:0% impossible to do so 00:24:58.200 --> 00:25:00.710 align:start position:0% impossible to do so um<00:24:58.260> so<00:24:58.740> now<00:24:58.919> we<00:24:59.220> also<00:24:59.460> have<00:24:59.640> this<00:25:00.059> fractures 00:25:00.710 --> 00:25:00.720 align:start position:0% um so now we also have this fractures 00:25:00.720 --> 00:25:02.770 align:start position:0% um so now we also have this fractures rule<00:25:01.080> called<00:25:01.140> lmdigos<00:25:01.860> which<00:25:02.400> is 00:25:02.770 --> 00:25:02.780 align:start position:0% rule called lmdigos which is 00:25:02.780 --> 00:25:06.049 align:start position:0% rule called lmdigos which is implementable<00:25:03.780> but<00:25:04.740> doing<00:25:05.400> all<00:25:05.580> of<00:25:05.700> this<00:25:05.820> like 00:25:06.049 --> 00:25:06.059 align:start position:0% implementable but doing all of this like 00:25:06.059 --> 00:25:08.210 align:start position:0% implementable but doing all of this like directly<00:25:06.480> is<00:25:06.720> pretty<00:25:07.020> expensive<00:25:07.559> so<00:25:07.860> we<00:25:08.100> need 00:25:08.210 --> 00:25:08.220 align:start position:0% directly is pretty expensive so we need 00:25:08.220 --> 00:25:09.830 align:start position:0% directly is pretty expensive so we need to<00:25:08.340> ideally<00:25:08.580> wrap<00:25:08.940> inside<00:25:09.120> the<00:25:09.299> snark<00:25:09.539> but 00:25:09.830 --> 00:25:09.840 align:start position:0% to ideally wrap inside the snark but 00:25:09.840 --> 00:25:12.649 align:start position:0% to ideally wrap inside the snark but there<00:25:10.080> is<00:25:10.260> another<00:25:10.740> downside<00:25:11.220> so<00:25:11.640> a<00:25:12.299> few<00:25:12.480> words 00:25:12.649 --> 00:25:12.659 align:start position:0% there is another downside so a few words 00:25:12.659 --> 00:25:14.890 align:start position:0% there is another downside so a few words about<00:25:12.840> the<00:25:13.140> trust<00:25:13.500> assumptions 00:25:14.890 --> 00:25:14.900 align:start position:0% about the trust assumptions 00:25:14.900 --> 00:25:17.390 align:start position:0% about the trust assumptions you<00:25:15.900> well<00:25:16.320> you<00:25:16.559> verify<00:25:16.860> the<00:25:16.980> consensus 00:25:17.390 --> 00:25:17.400 align:start position:0% you well you verify the consensus 00:25:17.400 --> 00:25:19.730 align:start position:0% you well you verify the consensus directly<00:25:17.820> so<00:25:18.240> it's<00:25:18.600> it's<00:25:18.900> fine 00:25:19.730 --> 00:25:19.740 align:start position:0% directly so it's it's fine 00:25:19.740 --> 00:25:22.250 align:start position:0% directly so it's it's fine he<00:25:20.460> do<00:25:21.299> you<00:25:21.480> introduce<00:25:21.720> any<00:25:21.840> trust 00:25:22.250 --> 00:25:22.260 align:start position:0% he do you introduce any trust 00:25:22.260 --> 00:25:24.470 align:start position:0% he do you introduce any trust assumptions<00:25:22.620> not<00:25:23.400> really<00:25:23.580> but<00:25:24.240> the<00:25:24.419> biggest 00:25:24.470 --> 00:25:24.480 align:start position:0% assumptions not really but the biggest 00:25:24.480 --> 00:25:26.330 align:start position:0% assumptions not really but the biggest downside<00:25:24.960> that<00:25:25.260> generating<00:25:25.740> the<00:25:25.980> proof 00:25:26.330 --> 00:25:26.340 align:start position:0% downside that generating the proof 00:25:26.340 --> 00:25:30.110 align:start position:0% downside that generating the proof actually<00:25:26.640> takes<00:25:27.000> some<00:25:27.299> time<00:25:27.799> so<00:25:28.799> to<00:25:29.640> be<00:25:29.820> honest 00:25:30.110 --> 00:25:30.120 align:start position:0% actually takes some time so to be honest 00:25:30.120 --> 00:25:33.529 align:start position:0% actually takes some time so to be honest this<00:25:31.020> approach<00:25:31.380> is<00:25:31.860> feasible<00:25:32.700> but<00:25:33.059> comparing 00:25:33.529 --> 00:25:33.539 align:start position:0% this approach is feasible but comparing 00:25:33.539 --> 00:25:36.289 align:start position:0% this approach is feasible but comparing to<00:25:33.720> messaging<00:25:34.260> like<00:25:35.100> quite<00:25:35.460> often<00:25:35.760> is<00:25:35.940> like 00:25:36.289 --> 00:25:36.299 align:start position:0% to messaging like quite often is like 00:25:36.299 --> 00:25:38.930 align:start position:0% to messaging like quite often is like almost<00:25:36.720> the<00:25:37.020> same<00:25:37.200> and<00:25:37.860> you<00:25:38.039> pay<00:25:38.279> a<00:25:38.700> lot<00:25:38.820> of 00:25:38.930 --> 00:25:38.940 align:start position:0% almost the same and you pay a lot of 00:25:38.940 --> 00:25:41.090 align:start position:0% almost the same and you pay a lot of improving<00:25:39.659> time 00:25:41.090 --> 00:25:41.100 align:start position:0% improving time 00:25:41.100 --> 00:25:43.730 align:start position:0% improving time and<00:25:41.520> requires<00:25:42.000> like<00:25:42.120> having<00:25:42.360> more<00:25:43.020> advanced 00:25:43.730 --> 00:25:43.740 align:start position:0% and requires like having more advanced 00:25:43.740 --> 00:25:47.029 align:start position:0% and requires like having more advanced infrastructure<00:25:44.700> okay<00:25:45.539> last<00:25:46.020> approach<00:25:46.440> that 00:25:47.029 --> 00:25:47.039 align:start position:0% infrastructure okay last approach that 00:25:47.039 --> 00:25:49.909 align:start position:0% infrastructure okay last approach that we<00:25:47.279> actually<00:25:47.520> use<00:25:48.480> is<00:25:49.320> something<00:25:49.559> that<00:25:49.799> we 00:25:49.909 --> 00:25:49.919 align:start position:0% we actually use is something that we 00:25:49.919 --> 00:25:51.830 align:start position:0% we actually use is something that we call<00:25:50.039> like<00:25:50.220> an<00:25:50.400> optimistic<00:25:50.880> relator<00:25:51.299> based<00:25:51.720> on 00:25:51.830 --> 00:25:51.840 align:start position:0% call like an optimistic relator based on 00:25:51.840 --> 00:25:54.649 align:start position:0% call like an optimistic relator based on NPC<00:25:52.559> MPC<00:25:53.520> stands<00:25:53.880> for<00:25:54.000> multi-party 00:25:54.649 --> 00:25:54.659 align:start position:0% NPC MPC stands for multi-party 00:25:54.659 --> 00:25:58.370 align:start position:0% NPC MPC stands for multi-party computation<00:25:55.140> maybe<00:25:55.860> before<00:25:56.220> I<00:25:56.900> explain<00:25:57.900> how 00:25:58.370 --> 00:25:58.380 align:start position:0% computation maybe before I explain how 00:25:58.380 --> 00:26:00.710 align:start position:0% computation maybe before I explain how it<00:25:58.500> works<00:25:58.799> let<00:25:58.919> me<00:25:59.100> explain<00:25:59.220> the<00:25:59.700> the<00:26:00.120> image<00:26:00.539> I 00:26:00.710 --> 00:26:00.720 align:start position:0% it works let me explain the the image I 00:26:00.720 --> 00:26:02.990 align:start position:0% it works let me explain the the image I hope<00:26:00.840> it's<00:26:01.020> self-explanatory<00:26:01.980> so<00:26:02.700> it's<00:26:02.880> an 00:26:02.990 --> 00:26:03.000 align:start position:0% hope it's self-explanatory so it's an 00:26:03.000 --> 00:26:05.029 align:start position:0% hope it's self-explanatory so it's an NPC<00:26:03.419> protocol<00:26:03.779> we<00:26:04.080> have<00:26:04.200> multiple<00:26:04.559> parties 00:26:05.029 --> 00:26:05.039 align:start position:0% NPC protocol we have multiple parties 00:26:05.039 --> 00:26:08.390 align:start position:0% NPC protocol we have multiple parties it's<00:26:05.460> multiple<00:26:05.880> parties<00:26:06.500> attached<00:26:07.500> something 00:26:08.390 --> 00:26:08.400 align:start position:0% it's multiple parties attached something 00:26:08.400 --> 00:26:12.289 align:start position:0% it's multiple parties attached something then<00:26:09.299> we<00:26:09.539> have<00:26:09.720> an<00:26:10.380> observer<00:26:10.980> that<00:26:11.820> can 00:26:12.289 --> 00:26:12.299 align:start position:0% then we have an observer that can 00:26:12.299 --> 00:26:14.570 align:start position:0% then we have an observer that can challenge<00:26:12.600> it<00:26:12.960> and<00:26:13.380> then<00:26:13.500> we<00:26:13.679> have<00:26:13.860> finally 00:26:14.570 --> 00:26:14.580 align:start position:0% challenge it and then we have finally 00:26:14.580 --> 00:26:16.430 align:start position:0% challenge it and then we have finally the<00:26:14.820> commitment<00:26:15.179> given<00:26:15.600> to<00:26:15.720> a<00:26:15.900> specific<00:26:16.140> chain 00:26:16.430 --> 00:26:16.440 align:start position:0% the commitment given to a specific chain 00:26:16.440 --> 00:26:18.289 align:start position:0% the commitment given to a specific chain in<00:26:16.740> this<00:26:16.860> case<00:26:17.039> start<00:26:17.279> net<00:26:17.580> once<00:26:18.240> everything 00:26:18.289 --> 00:26:18.299 align:start position:0% in this case start net once everything 00:26:18.299 --> 00:26:19.490 align:start position:0% in this case start net once everything is<00:26:18.659> fine 00:26:19.490 --> 00:26:19.500 align:start position:0% is fine 00:26:19.500 --> 00:26:23.269 align:start position:0% is fine how<00:26:19.980> does<00:26:20.159> it<00:26:20.279> work<00:26:20.600> so<00:26:21.600> we<00:26:21.960> have<00:26:22.080> a<00:26:22.260> set<00:26:22.440> of 00:26:23.269 --> 00:26:23.279 align:start position:0% how does it work so we have a set of 00:26:23.279 --> 00:26:26.450 align:start position:0% how does it work so we have a set of trusted<00:26:24.120> three<00:26:24.360> layers<00:26:24.980> validators<00:26:25.980> however 00:26:26.450 --> 00:26:26.460 align:start position:0% trusted three layers validators however 00:26:26.460 --> 00:26:28.310 align:start position:0% trusted three layers validators however and<00:26:26.760> they<00:26:26.940> attested<00:26:27.419> a<00:26:27.659> specific<00:26:27.840> commitment 00:26:28.310 --> 00:26:28.320 align:start position:0% and they attested a specific commitment 00:26:28.320 --> 00:26:31.310 align:start position:0% and they attested a specific commitment is<00:26:28.500> valid<00:26:28.919> so<00:26:29.400> how<00:26:29.640> does<00:26:29.820> it<00:26:30.000> work<00:26:30.179> if<00:26:30.900> you<00:26:31.080> want 00:26:31.310 --> 00:26:31.320 align:start position:0% is valid so how does it work if you want 00:26:31.320 --> 00:26:35.090 align:start position:0% is valid so how does it work if you want to<00:26:31.679> get<00:26:32.520> the<00:26:32.820> commitment<00:26:33.600> AKA<00:26:34.320> The<00:26:34.440> Block<00:26:34.740> hash 00:26:35.090 --> 00:26:35.100 align:start position:0% to get the commitment AKA The Block hash 00:26:35.100 --> 00:26:37.549 align:start position:0% to get the commitment AKA The Block hash of<00:26:35.700> block<00:26:35.940> number 00:26:37.549 --> 00:26:37.559 align:start position:0% of block number 00:26:37.559 --> 00:26:40.909 align:start position:0% of block number X<00:26:38.220> upon<00:26:39.000> Stark<00:26:39.299> net<00:26:39.480> then<00:26:40.140> instead<00:26:40.500> of<00:26:40.559> sending 00:26:40.909 --> 00:26:40.919 align:start position:0% X upon Stark net then instead of sending 00:26:40.919 --> 00:26:43.090 align:start position:0% X upon Stark net then instead of sending a<00:26:41.039> message<00:26:41.159> that<00:26:41.460> will<00:26:41.580> be<00:26:41.700> delayed<00:26:42.059> with<00:26:42.360> a 00:26:43.090 --> 00:26:43.100 align:start position:0% a message that will be delayed with a 00:26:43.100 --> 00:26:46.070 align:start position:0% a message that will be delayed with a like<00:26:44.100> slightly<00:26:44.580> delayed<00:26:45.059> we<00:26:45.539> can<00:26:45.720> essentially 00:26:46.070 --> 00:26:46.080 align:start position:0% like slightly delayed we can essentially 00:26:46.080 --> 00:26:48.230 align:start position:0% like slightly delayed we can essentially make<00:26:46.380> an<00:26:46.500> offshine<00:26:46.919> call<00:26:47.100> just<00:26:47.760> get<00:26:48.059> the 00:26:48.230 --> 00:26:48.240 align:start position:0% make an offshine call just get the 00:26:48.240 --> 00:26:49.730 align:start position:0% make an offshine call just get the latest<00:26:48.419> one<00:26:48.720> and<00:26:48.900> essentially<00:26:49.200> relay<00:26:49.559> this 00:26:49.730 --> 00:26:49.740 align:start position:0% latest one and essentially relay this 00:26:49.740 --> 00:26:52.070 align:start position:0% latest one and essentially relay this message<00:26:49.860> directly<00:26:50.400> to<00:26:51.000> start<00:26:51.240> but<00:26:51.720> it<00:26:51.840> comes 00:26:52.070 --> 00:26:52.080 align:start position:0% message directly to start but it comes 00:26:52.080 --> 00:26:54.230 align:start position:0% message directly to start but it comes with<00:26:52.200> a<00:26:52.380> few<00:26:52.559> downsides<00:26:53.159> because<00:26:53.700> while<00:26:54.000> we 00:26:54.230 --> 00:26:54.240 align:start position:0% with a few downsides because while we 00:26:54.240 --> 00:26:57.769 align:start position:0% with a few downsides because while we introduce<00:26:54.600> some<00:26:55.260> trust<00:26:56.039> assumptions<00:26:56.480> uh<00:26:57.480> but 00:26:57.769 --> 00:26:57.779 align:start position:0% introduce some trust assumptions uh but 00:26:57.779 --> 00:26:59.630 align:start position:0% introduce some trust assumptions uh but still<00:26:57.840> it's<00:26:58.020> okay<00:26:58.140> okay<00:26:58.380> how<00:26:58.559> does<00:26:58.799> it<00:26:58.919> work<00:26:59.100> so 00:26:59.630 --> 00:26:59.640 align:start position:0% still it's okay okay how does it work so 00:26:59.640 --> 00:27:00.950 align:start position:0% still it's okay okay how does it work so it<00:26:59.760> works<00:27:00.000> in<00:27:00.120> a<00:27:00.240> way<00:27:00.299> that<00:27:00.480> we<00:27:00.600> have<00:27:00.659> a<00:27:00.840> bunch 00:27:00.950 --> 00:27:00.960 align:start position:0% it works in a way that we have a bunch 00:27:00.960 --> 00:27:02.930 align:start position:0% it works in a way that we have a bunch of<00:27:01.080> off<00:27:01.200> chain<00:27:01.440> actors<00:27:01.799> who<00:27:02.400> essentially<00:27:02.700> make 00:27:02.930 --> 00:27:02.940 align:start position:0% of off chain actors who essentially make 00:27:02.940 --> 00:27:05.330 align:start position:0% of off chain actors who essentially make this<00:27:03.120> calls<00:27:03.480> and<00:27:04.320> it<00:27:04.620> works<00:27:04.980> more<00:27:05.100> or<00:27:05.279> less 00:27:05.330 --> 00:27:05.340 align:start position:0% this calls and it works more or less 00:27:05.340 --> 00:27:08.269 align:start position:0% this calls and it works more or less like<00:27:05.520> a<00:27:05.760> multi-seek<00:27:06.360> but<00:27:07.020> the<00:27:07.260> reason<00:27:07.380> why<00:27:08.100> we 00:27:08.269 --> 00:27:08.279 align:start position:0% like a multi-seek but the reason why we 00:27:08.279 --> 00:27:11.149 align:start position:0% like a multi-seek but the reason why we have<00:27:08.340> NPC<00:27:08.820> is<00:27:09.000> because<00:27:09.240> more<00:27:10.200> validators<00:27:10.919> you 00:27:11.149 --> 00:27:11.159 align:start position:0% have NPC is because more validators you 00:27:11.159 --> 00:27:12.789 align:start position:0% have NPC is because more validators you have<00:27:11.340> than<00:27:11.520> obviously 00:27:12.789 --> 00:27:12.799 align:start position:0% have than obviously 00:27:12.799 --> 00:27:15.409 align:start position:0% have than obviously more<00:27:13.799> Securities<00:27:14.400> but 00:27:15.409 --> 00:27:15.419 align:start position:0% more Securities but 00:27:15.419 --> 00:27:17.330 align:start position:0% more Securities but more<00:27:15.960> validators<00:27:16.500> you<00:27:16.740> have<00:27:16.860> in<00:27:16.980> it<00:27:17.159> like 00:27:17.330 --> 00:27:17.340 align:start position:0% more validators you have in it like 00:27:17.340 --> 00:27:19.730 align:start position:0% more validators you have in it like standard<00:27:17.820> multi-sig<00:27:18.299> approach<00:27:18.720> you<00:27:19.559> have 00:27:19.730 --> 00:27:19.740 align:start position:0% standard multi-sig approach you have 00:27:19.740 --> 00:27:21.710 align:start position:0% standard multi-sig approach you have more<00:27:20.039> signatures<00:27:20.700> so 00:27:21.710 --> 00:27:21.720 align:start position:0% more signatures so 00:27:21.720 --> 00:27:23.930 align:start position:0% more signatures so more<00:27:22.320> in<00:27:22.620> a<00:27:22.799> way<00:27:22.799> decentralized<00:27:23.400> it<00:27:23.580> is<00:27:23.760> then 00:27:23.930 --> 00:27:23.940 align:start position:0% more in a way decentralized it is then 00:27:23.940 --> 00:27:26.149 align:start position:0% more in a way decentralized it is then it's<00:27:24.419> more<00:27:25.020> expensive<00:27:25.500> to<00:27:25.679> verify<00:27:25.980> because 00:27:26.149 --> 00:27:26.159 align:start position:0% it's more expensive to verify because 00:27:26.159 --> 00:27:27.950 align:start position:0% it's more expensive to verify because you<00:27:26.400> need<00:27:26.520> to<00:27:26.640> verify<00:27:26.940> multiple<00:27:27.299> signatures 00:27:27.950 --> 00:27:27.960 align:start position:0% you need to verify multiple signatures 00:27:27.960 --> 00:27:30.590 align:start position:0% you need to verify multiple signatures and<00:27:28.860> you<00:27:29.279> need<00:27:29.400> to<00:27:29.520> like<00:27:29.760> pause<00:27:30.299> the 00:27:30.590 --> 00:27:30.600 align:start position:0% and you need to like pause the 00:27:30.600 --> 00:27:32.750 align:start position:0% and you need to like pause the signatures<00:27:31.080> it's<00:27:31.320> a<00:27:31.500> lot<00:27:31.559> of<00:27:31.679> cool<00:27:31.799> data<00:27:32.279> such 00:27:32.750 --> 00:27:32.760 align:start position:0% signatures it's a lot of cool data such 00:27:32.760 --> 00:27:35.269 align:start position:0% signatures it's a lot of cool data such approach<00:27:33.120> is<00:27:33.299> not<00:27:33.480> feasible<00:27:33.900> on<00:27:34.559> chains 00:27:35.269 --> 00:27:35.279 align:start position:0% approach is not feasible on chains 00:27:35.279 --> 00:27:37.750 align:start position:0% approach is not feasible on chains Oracle<00:27:35.640> data<00:27:35.940> is<00:27:36.000> expensive<00:27:36.419> so<00:27:36.720> at<00:27:37.320> one 00:27:37.750 --> 00:27:37.760 align:start position:0% Oracle data is expensive so at one 00:27:37.760 --> 00:27:41.149 align:start position:0% Oracle data is expensive so at one optimistic<00:27:38.760> rollups<00:27:39.240> and<00:27:39.960> yeah 00:27:41.149 --> 00:27:41.159 align:start position:0% optimistic rollups and yeah 00:27:41.159 --> 00:27:44.029 align:start position:0% optimistic rollups and yeah okay<00:27:41.700> so<00:27:42.000> how<00:27:42.179> does<00:27:42.360> it<00:27:42.480> work<00:27:42.659> uh<00:27:43.260> what<00:27:43.620> is<00:27:43.799> uh 00:27:44.029 --> 00:27:44.039 align:start position:0% okay so how does it work uh what is uh 00:27:44.039 --> 00:27:46.909 align:start position:0% okay so how does it work uh what is uh actually<00:27:44.279> NPC<00:27:44.940> part<00:27:45.120> doing<00:27:45.360> the<00:27:45.600> MPC<00:27:46.080> part<00:27:46.260> is 00:27:46.909 --> 00:27:46.919 align:start position:0% actually NPC part doing the MPC part is 00:27:46.919 --> 00:27:49.310 align:start position:0% actually NPC part doing the MPC part is very<00:27:47.220> simple<00:27:47.400> it's<00:27:47.880> essentially<00:27:48.320> signing 00:27:49.310 --> 00:27:49.320 align:start position:0% very simple it's essentially signing 00:27:49.320 --> 00:27:52.730 align:start position:0% very simple it's essentially signing over<00:27:49.820> like<00:27:50.820> a<00:27:51.000> specific<00:27:51.360> curve<00:27:51.779> some<00:27:52.320> specific 00:27:52.730 --> 00:27:52.740 align:start position:0% over like a specific curve some specific 00:27:52.740 --> 00:27:54.289 align:start position:0% over like a specific curve some specific payload<00:27:53.279> and<00:27:53.400> the<00:27:53.520> payload<00:27:53.880> is<00:27:54.059> the 00:27:54.289 --> 00:27:54.299 align:start position:0% payload and the payload is the 00:27:54.299 --> 00:27:56.990 align:start position:0% payload and the payload is the commitment<00:27:54.720> itself<00:27:55.080> and<00:27:55.919> that's<00:27:56.159> it<00:27:56.340> okay<00:27:56.580> so 00:27:56.990 --> 00:27:57.000 align:start position:0% commitment itself and that's it okay so 00:27:57.000 --> 00:27:59.870 align:start position:0% commitment itself and that's it okay so this<00:27:57.179> is<00:27:57.299> how<00:27:57.659> we<00:27:58.380> actually<00:27:58.559> attest<00:27:59.220> but<00:27:59.640> now 00:27:59.870 --> 00:27:59.880 align:start position:0% this is how we actually attest but now 00:27:59.880 --> 00:28:01.909 align:start position:0% this is how we actually attest but now how<00:28:00.299> why<00:28:00.720> this<00:28:01.080> approach<00:28:01.620> is<00:28:01.740> called 00:28:01.909 --> 00:28:01.919 align:start position:0% how why this approach is called 00:28:01.919 --> 00:28:04.370 align:start position:0% how why this approach is called optimistic<00:28:02.520> and<00:28:02.760> why<00:28:03.000> it's<00:28:03.179> still<00:28:03.360> secure 00:28:04.370 --> 00:28:04.380 align:start position:0% optimistic and why it's still secure 00:28:04.380 --> 00:28:07.669 align:start position:0% optimistic and why it's still secure so<00:28:05.279> first<00:28:05.640> of<00:28:05.820> all<00:28:06.299> we<00:28:06.900> just<00:28:07.020> posted<00:28:07.440> some 00:28:07.669 --> 00:28:07.679 align:start position:0% so first of all we just posted some 00:28:07.679 --> 00:28:09.890 align:start position:0% so first of all we just posted some something<00:28:07.980> on<00:28:08.279> the<00:28:08.460> actual<00:28:08.700> L2<00:28:09.120> and<00:28:09.419> as<00:28:09.659> you 00:28:09.890 --> 00:28:09.900 align:start position:0% something on the actual L2 and as you 00:28:09.900 --> 00:28:12.169 align:start position:0% something on the actual L2 and as you may<00:28:10.020> know<00:28:10.200> we<00:28:10.620> can<00:28:10.799> send<00:28:10.919> messages<00:28:11.220> from<00:28:11.580> L1<00:28:11.940> to 00:28:12.169 --> 00:28:12.179 align:start position:0% may know we can send messages from L1 to 00:28:12.179 --> 00:28:15.769 align:start position:0% may know we can send messages from L1 to L2<00:28:13.020> and<00:28:13.380> such<00:28:13.500> a<00:28:13.740> message<00:28:13.919> can<00:28:14.340> contain<00:28:14.820> like 00:28:15.769 --> 00:28:15.779 align:start position:0% L2 and such a message can contain like 00:28:15.779 --> 00:28:17.330 align:start position:0% L2 and such a message can contain like the<00:28:16.020> proper<00:28:16.380> commitment<00:28:16.740> so<00:28:16.980> essentially 00:28:17.330 --> 00:28:17.340 align:start position:0% the proper commitment so essentially 00:28:17.340 --> 00:28:19.669 align:start position:0% the proper commitment so essentially even<00:28:17.580> if<00:28:17.880> there<00:28:18.059> are<00:28:18.240> a<00:28:18.360> validator<00:28:18.779> set<00:28:19.140> will 00:28:19.669 --> 00:28:19.679 align:start position:0% even if there are a validator set will 00:28:19.679 --> 00:28:22.430 align:start position:0% even if there are a validator set will lie<00:28:20.039> that<00:28:20.760> one<00:28:21.059> will<00:28:21.299> never<00:28:21.480> lie<00:28:21.900> so<00:28:22.080> you<00:28:22.260> can 00:28:22.430 --> 00:28:22.440 align:start position:0% lie that one will never lie so you can 00:28:22.440 --> 00:28:25.130 align:start position:0% lie that one will never lie so you can just<00:28:22.559> challenge<00:28:22.860> such<00:28:23.220> a<00:28:23.400> message<00:28:23.520> and<00:28:24.120> now<00:28:24.360> to 00:28:25.130 --> 00:28:25.140 align:start position:0% just challenge such a message and now to 00:28:25.140 --> 00:28:27.409 align:start position:0% just challenge such a message and now to participate<00:28:25.620> in<00:28:25.799> verifying<00:28:26.520> this<00:28:26.820> validators 00:28:27.409 --> 00:28:27.419 align:start position:0% participate in verifying this validators 00:28:27.419 --> 00:28:29.750 align:start position:0% participate in verifying this validators it's<00:28:27.659> super<00:28:27.840> easy<00:28:28.020> because<00:28:28.260> literally<00:28:28.799> two<00:28:29.220> RP 00:28:29.750 --> 00:28:29.760 align:start position:0% it's super easy because literally two RP 00:28:29.760 --> 00:28:32.090 align:start position:0% it's super easy because literally two RP sequels<00:28:30.240> one<00:28:30.900> call<00:28:31.140> is<00:28:31.500> gonna<00:28:31.679> check<00:28:31.919> the 00:28:32.090 --> 00:28:32.100 align:start position:0% sequels one call is gonna check the 00:28:32.100 --> 00:28:33.710 align:start position:0% sequels one call is gonna check the actual<00:28:32.400> commitment<00:28:32.820> on<00:28:33.120> the<00:28:33.240> actual<00:28:33.480> chain 00:28:33.710 --> 00:28:33.720 align:start position:0% actual commitment on the actual chain 00:28:33.720 --> 00:28:36.769 align:start position:0% actual commitment on the actual chain and<00:28:34.320> the<00:28:34.500> other<00:28:34.620> one<00:28:34.860> checks<00:28:35.400> like<00:28:35.820> what<00:28:36.600> is 00:28:36.769 --> 00:28:36.779 align:start position:0% and the other one checks like what is 00:28:36.779 --> 00:28:40.250 align:start position:0% and the other one checks like what is the<00:28:37.140> claimed<00:28:37.679> Commitment<00:28:38.100> if<00:28:38.760> you<00:28:38.880> disagree 00:28:40.250 --> 00:28:40.260 align:start position:0% the claimed Commitment if you disagree 00:28:40.260 --> 00:28:42.890 align:start position:0% the claimed Commitment if you disagree you<00:28:40.799> just<00:28:41.039> send<00:28:41.279> a<00:28:41.460> message<00:28:41.640> it<00:28:42.059> costs<00:28:42.419> roughly 00:28:42.890 --> 00:28:42.900 align:start position:0% you just send a message it costs roughly 00:28:42.900 --> 00:28:45.710 align:start position:0% you just send a message it costs roughly 60<00:28:43.620> K<00:28:44.039> of<00:28:44.279> gas 00:28:45.710 --> 00:28:45.720 align:start position:0% 60 K of gas 00:28:45.720 --> 00:28:48.710 align:start position:0% 60 K of gas and<00:28:46.200> that's<00:28:46.320> it<00:28:46.559> everyone<00:28:47.100> can<00:28:47.400> do<00:28:47.580> that 00:28:48.710 --> 00:28:48.720 align:start position:0% and that's it everyone can do that 00:28:48.720 --> 00:28:49.430 align:start position:0% and that's it everyone can do that um 00:28:49.430 --> 00:28:49.440 align:start position:0% um 00:28:49.440 --> 00:28:52.130 align:start position:0% um and<00:28:50.100> again<00:28:50.279> the<00:28:50.940> fraud<00:28:51.299> proving<00:28:51.600> window<00:28:51.779> is 00:28:52.130 --> 00:28:52.140 align:start position:0% and again the fraud proving window is 00:28:52.140 --> 00:28:54.769 align:start position:0% and again the fraud proving window is pretty<00:28:52.380> short<00:28:52.559> because<00:28:53.419> it's<00:28:54.419> essentially 00:28:54.769 --> 00:28:54.779 align:start position:0% pretty short because it's essentially 00:28:54.779 --> 00:28:56.570 align:start position:0% pretty short because it's essentially how<00:28:55.020> long<00:28:55.140> it<00:28:55.320> will<00:28:55.440> take<00:28:55.620> to<00:28:55.860> generate<00:28:56.400> like 00:28:56.570 --> 00:28:56.580 align:start position:0% how long it will take to generate like 00:28:56.580 --> 00:28:58.490 align:start position:0% how long it will take to generate like the<00:28:56.760> proof<00:28:57.000> of<00:28:57.059> consensus<00:28:57.539> if<00:28:57.960> it's<00:28:58.080> possible 00:28:58.490 --> 00:28:58.500 align:start position:0% the proof of consensus if it's possible 00:28:58.500 --> 00:29:01.130 align:start position:0% the proof of consensus if it's possible or<00:28:59.400> how<00:28:59.880> long<00:29:00.000> does<00:29:00.179> it<00:29:00.360> take<00:29:00.480> to<00:29:00.600> deliver<00:29:00.779> the 00:29:01.130 --> 00:29:01.140 align:start position:0% or how long does it take to deliver the 00:29:01.140 --> 00:29:03.350 align:start position:0% or how long does it take to deliver the message<00:29:01.320> and<00:29:02.279> what<00:29:02.400> is<00:29:02.640> pretty<00:29:02.820> cool<00:29:03.000> in<00:29:03.179> this 00:29:03.350 --> 00:29:03.360 align:start position:0% message and what is pretty cool in this 00:29:03.360 --> 00:29:05.810 align:start position:0% message and what is pretty cool in this approach<00:29:03.600> it's<00:29:03.960> not<00:29:04.140> gas<00:29:04.440> intensive<00:29:05.039> we 00:29:05.810 --> 00:29:05.820 align:start position:0% approach it's not gas intensive we 00:29:05.820 --> 00:29:09.049 align:start position:0% approach it's not gas intensive we verify<00:29:06.179> just<00:29:06.419> one<00:29:06.600> signature<00:29:07.279> so<00:29:08.279> that's 00:29:09.049 --> 00:29:09.059 align:start position:0% verify just one signature so that's 00:29:09.059 --> 00:29:10.490 align:start position:0% verify just one signature so that's about<00:29:09.299> this<00:29:09.539> approach 00:29:10.490 --> 00:29:10.500 align:start position:0% about this approach 00:29:10.500 --> 00:29:12.890 align:start position:0% about this approach let's<00:29:11.340> make<00:29:11.520> a<00:29:11.640> recap<00:29:11.940> and<00:29:12.299> let's<00:29:12.480> identify 00:29:12.890 --> 00:29:12.900 align:start position:0% let's make a recap and let's identify 00:29:12.900 --> 00:29:14.450 align:start position:0% let's make a recap and let's identify the<00:29:13.080> trade-offs 00:29:14.450 --> 00:29:14.460 align:start position:0% the trade-offs 00:29:14.460 --> 00:29:17.029 align:start position:0% the trade-offs so<00:29:15.059> we<00:29:15.360> have<00:29:15.480> three<00:29:15.779> approaches<00:29:16.320> the<00:29:16.919> first 00:29:17.029 --> 00:29:17.039 align:start position:0% so we have three approaches the first 00:29:17.039 --> 00:29:19.190 align:start position:0% so we have three approaches the first one<00:29:17.220> is<00:29:17.400> messaging<00:29:17.940> the<00:29:18.720> second<00:29:18.840> one<00:29:19.020> is 00:29:19.190 --> 00:29:19.200 align:start position:0% one is messaging the second one is 00:29:19.200 --> 00:29:21.169 align:start position:0% one is messaging the second one is validating<00:29:19.559> the<00:29:19.799> consensus<00:29:20.279> and<00:29:20.940> the<00:29:21.120> third 00:29:21.169 --> 00:29:21.179 align:start position:0% validating the consensus and the third 00:29:21.179 --> 00:29:24.350 align:start position:0% validating the consensus and the third one<00:29:21.419> is<00:29:21.600> having<00:29:22.320> this<00:29:22.559> optimistic<00:29:23.039> layer<00:29:23.520> so<00:29:24.120> I 00:29:24.350 --> 00:29:24.360 align:start position:0% one is having this optimistic layer so I 00:29:24.360 --> 00:29:28.490 align:start position:0% one is having this optimistic layer so I categorize<00:29:24.840> it<00:29:25.080> in<00:29:25.559> four<00:29:26.840> categories<00:29:27.840> the 00:29:28.490 --> 00:29:28.500 align:start position:0% categorize it in four categories the 00:29:28.500 --> 00:29:31.850 align:start position:0% categorize it in four categories the first<00:29:28.679> one<00:29:28.860> is<00:29:29.220> latency<00:29:29.899> the<00:29:30.899> second<00:29:31.140> one<00:29:31.440> is 00:29:31.850 --> 00:29:31.860 align:start position:0% first one is latency the second one is 00:29:31.860 --> 00:29:35.330 align:start position:0% first one is latency the second one is the<00:29:32.399> gas<00:29:32.520> cost<00:29:32.820> the<00:29:33.779> third<00:29:33.960> one<00:29:34.140> is<00:29:34.380> trust<00:29:35.039> and 00:29:35.330 --> 00:29:35.340 align:start position:0% the gas cost the third one is trust and 00:29:35.340 --> 00:29:37.130 align:start position:0% the gas cost the third one is trust and the<00:29:35.460> last<00:29:35.580> one<00:29:35.760> is<00:29:35.940> what<00:29:36.419> is<00:29:36.539> the<00:29:36.659> off-ching 00:29:37.130 --> 00:29:37.140 align:start position:0% the last one is what is the off-ching 00:29:37.140 --> 00:29:39.590 align:start position:0% the last one is what is the off-ching computation<00:29:37.620> overhead<00:29:38.220> why<00:29:38.880> do<00:29:39.059> I<00:29:39.240> even<00:29:39.299> list 00:29:39.590 --> 00:29:39.600 align:start position:0% computation overhead why do I even list 00:29:39.600 --> 00:29:41.810 align:start position:0% computation overhead why do I even list it<00:29:39.779> because<00:29:39.960> if<00:29:40.380> we<00:29:40.500> do<00:29:40.679> some<00:29:40.919> sort<00:29:41.159> of<00:29:41.340> proving 00:29:41.810 --> 00:29:41.820 align:start position:0% it because if we do some sort of proving 00:29:41.820 --> 00:29:43.430 align:start position:0% it because if we do some sort of proving then<00:29:42.120> obviously<00:29:42.539> it<00:29:42.659> takes<00:29:42.840> time<00:29:43.020> because<00:29:43.200> we 00:29:43.430 --> 00:29:43.440 align:start position:0% then obviously it takes time because we 00:29:43.440 --> 00:29:44.930 align:start position:0% then obviously it takes time because we need<00:29:43.559> to<00:29:43.620> generate<00:29:43.919> the<00:29:44.100> proof 00:29:44.930 --> 00:29:44.940 align:start position:0% need to generate the proof 00:29:44.940 --> 00:29:48.710 align:start position:0% need to generate the proof so<00:29:45.539> messaging<00:29:46.140> in<00:29:46.740> terms<00:29:46.919> of<00:29:46.980> latency<00:29:47.460> we<00:29:48.419> are 00:29:48.710 --> 00:29:48.720 align:start position:0% so messaging in terms of latency we are 00:29:48.720 --> 00:29:50.990 align:start position:0% so messaging in terms of latency we are quite<00:29:48.960> sad<00:29:49.260> because<00:29:49.799> well<00:29:50.220> the<00:29:50.460> message<00:29:50.640> needs 00:29:50.990 --> 00:29:51.000 align:start position:0% quite sad because well the message needs 00:29:51.000 --> 00:29:53.210 align:start position:0% quite sad because well the message needs to<00:29:51.059> get<00:29:51.179> delivered<00:29:51.659> so<00:29:52.200> once<00:29:52.919> the<00:29:53.039> message 00:29:53.210 --> 00:29:53.220 align:start position:0% to get delivered so once the message 00:29:53.220 --> 00:29:56.870 align:start position:0% to get delivered so once the message gets<00:29:53.640> delivered<00:29:54.000> to<00:29:54.299> some<00:29:54.899> specific<00:29:55.380> L2<00:29:55.980> L1 00:29:56.870 --> 00:29:56.880 align:start position:0% gets delivered to some specific L2 L1 00:29:56.880 --> 00:29:59.269 align:start position:0% gets delivered to some specific L2 L1 will<00:29:57.480> be<00:29:58.140> able<00:29:58.320> to<00:29:58.440> generate<00:29:58.740> already<00:29:58.980> new 00:29:59.269 --> 00:29:59.279 align:start position:0% will be able to generate already new 00:29:59.279 --> 00:30:00.950 align:start position:0% will be able to generate already new block<00:29:59.460> so<00:29:59.700> we<00:29:59.820> don't<00:29:59.940> have<00:30:00.120> like<00:30:00.360> access<00:30:00.600> to 00:30:00.950 --> 00:30:00.960 align:start position:0% block so we don't have like access to 00:30:00.960 --> 00:30:02.810 align:start position:0% block so we don't have like access to the<00:30:01.200> newest<00:30:01.679> values 00:30:02.810 --> 00:30:02.820 align:start position:0% the newest values 00:30:02.820 --> 00:30:05.510 align:start position:0% the newest values in<00:30:03.120> terms<00:30:03.240> of<00:30:03.360> gas<00:30:03.539> cost<00:30:03.840> it's<00:30:04.740> not<00:30:05.039> bad<00:30:05.220> but 00:30:05.510 --> 00:30:05.520 align:start position:0% in terms of gas cost it's not bad but 00:30:05.520 --> 00:30:07.070 align:start position:0% in terms of gas cost it's not bad but it's<00:30:05.700> not<00:30:05.880> perfect<00:30:06.059> because<00:30:06.480> we<00:30:06.840> need<00:30:06.960> to 00:30:07.070 --> 00:30:07.080 align:start position:0% it's not perfect because we need to 00:30:07.080 --> 00:30:08.630 align:start position:0% it's not perfect because we need to interact<00:30:07.440> with<00:30:07.679> two<00:30:07.860> chains<00:30:08.220> at<00:30:08.340> the<00:30:08.460> same 00:30:08.630 --> 00:30:08.640 align:start position:0% interact with two chains at the same 00:30:08.640 --> 00:30:10.190 align:start position:0% interact with two chains at the same time<00:30:08.760> so<00:30:09.059> first<00:30:09.240> we<00:30:09.419> need<00:30:09.600> to<00:30:09.720> send<00:30:09.840> a<00:30:10.080> message 00:30:10.190 --> 00:30:10.200 align:start position:0% time so first we need to send a message 00:30:10.200 --> 00:30:13.490 align:start position:0% time so first we need to send a message and<00:30:10.500> consume<00:30:11.100> it<00:30:11.480> in<00:30:12.480> terms<00:30:12.600> of<00:30:12.720> trust<00:30:13.020> we<00:30:13.260> are 00:30:13.490 --> 00:30:13.500 align:start position:0% and consume it in terms of trust we are 00:30:13.500 --> 00:30:16.610 align:start position:0% and consume it in terms of trust we are pretty<00:30:13.679> happy<00:30:14.039> because<00:30:14.880> we<00:30:15.419> trust<00:30:16.020> the<00:30:16.260> rollup 00:30:16.610 --> 00:30:16.620 align:start position:0% pretty happy because we trust the rollup 00:30:16.620 --> 00:30:19.010 align:start position:0% pretty happy because we trust the rollup itself<00:30:16.919> and<00:30:17.100> it's<00:30:17.220> a<00:30:17.399> fair<00:30:17.520> assumption 00:30:19.010 --> 00:30:19.020 align:start position:0% itself and it's a fair assumption 00:30:19.020 --> 00:30:20.930 align:start position:0% itself and it's a fair assumption option<00:30:19.620> computation<00:30:20.100> overhead<00:30:20.460> we're<00:30:20.700> very 00:30:20.930 --> 00:30:20.940 align:start position:0% option computation overhead we're very 00:30:20.940 --> 00:30:23.330 align:start position:0% option computation overhead we're very happy<00:30:21.179> because<00:30:21.480> there<00:30:21.779> is<00:30:21.960> no<00:30:22.320> computation<00:30:22.919> to 00:30:23.330 --> 00:30:23.340 align:start position:0% happy because there is no computation to 00:30:23.340 --> 00:30:26.570 align:start position:0% happy because there is no computation to do<00:30:23.640> off-chain<00:30:24.320> verifying<00:30:25.320> the<00:30:25.440> consensus<00:30:25.919> so 00:30:26.570 --> 00:30:26.580 align:start position:0% do off-chain verifying the consensus so 00:30:26.580 --> 00:30:27.830 align:start position:0% do off-chain verifying the consensus so in<00:30:26.700> terms<00:30:26.880> of<00:30:26.940> latency<00:30:27.299> we<00:30:27.659> are<00:30:27.779> outside 00:30:27.830 --> 00:30:27.840 align:start position:0% in terms of latency we are outside 00:30:27.840 --> 00:30:30.350 align:start position:0% in terms of latency we are outside because<00:30:28.200> we<00:30:28.380> need<00:30:28.500> to<00:30:28.559> generate<00:30:28.919> the<00:30:29.100> proof 00:30:30.350 --> 00:30:30.360 align:start position:0% because we need to generate the proof 00:30:30.360 --> 00:30:31.850 align:start position:0% because we need to generate the proof that<00:30:30.600> we've<00:30:30.840> done<00:30:30.960> it<00:30:31.080> it<00:30:31.200> takes<00:30:31.380> a<00:30:31.559> bit<00:30:31.679> of 00:30:31.850 --> 00:30:31.860 align:start position:0% that we've done it it takes a bit of 00:30:31.860 --> 00:30:35.210 align:start position:0% that we've done it it takes a bit of time<00:30:32.039> in<00:30:32.580> terms<00:30:32.760> of<00:30:32.820> gas<00:30:33.059> costs<00:30:33.539> we<00:30:34.140> are<00:30:34.380> I 00:30:35.210 --> 00:30:35.220 align:start position:0% time in terms of gas costs we are I 00:30:35.220 --> 00:30:37.250 align:start position:0% time in terms of gas costs we are I would<00:30:35.399> say<00:30:35.520> sad<00:30:35.880> because<00:30:36.299> we<00:30:36.600> need<00:30:36.720> to<00:30:36.840> verify 00:30:37.250 --> 00:30:37.260 align:start position:0% would say sad because we need to verify 00:30:37.260 --> 00:30:39.409 align:start position:0% would say sad because we need to verify the<00:30:37.440> actual<00:30:37.679> ZK<00:30:38.039> proof<00:30:38.340> which<00:30:38.520> is<00:30:38.700> way<00:30:39.120> more 00:30:39.409 --> 00:30:39.419 align:start position:0% the actual ZK proof which is way more 00:30:39.419 --> 00:30:42.350 align:start position:0% the actual ZK proof which is way more expensive<00:30:39.840> than<00:30:40.260> just 00:30:42.350 --> 00:30:42.360 align:start position:0% expensive than just 00:30:42.360 --> 00:30:44.450 align:start position:0% expensive than just consuming<00:30:43.080> a<00:30:43.260> message<00:30:43.440> or<00:30:43.799> verifying<00:30:44.399> a 00:30:44.450 --> 00:30:44.460 align:start position:0% consuming a message or verifying a 00:30:44.460 --> 00:30:46.789 align:start position:0% consuming a message or verifying a signature<00:30:44.940> in<00:30:45.659> terms<00:30:45.840> of<00:30:45.899> trust<00:30:46.260> we<00:30:46.500> are<00:30:46.679> happy 00:30:46.789 --> 00:30:46.799 align:start position:0% signature in terms of trust we are happy 00:30:46.799 --> 00:30:49.250 align:start position:0% signature in terms of trust we are happy because<00:30:47.159> we<00:30:47.340> verify<00:30:47.700> the<00:30:47.880> consensus<00:30:48.299> itself 00:30:49.250 --> 00:30:49.260 align:start position:0% because we verify the consensus itself 00:30:49.260 --> 00:30:51.649 align:start position:0% because we verify the consensus itself and<00:30:50.220> computation<00:30:50.760> overhead<00:30:51.240> it's 00:30:51.649 --> 00:30:51.659 align:start position:0% and computation overhead it's 00:30:51.659 --> 00:30:52.970 align:start position:0% and computation overhead it's significant<00:30:52.140> right<00:30:52.320> because<00:30:52.559> we<00:30:52.740> need<00:30:52.860> to 00:30:52.970 --> 00:30:52.980 align:start position:0% significant right because we need to 00:30:52.980 --> 00:30:54.409 align:start position:0% significant right because we need to generate<00:30:53.279> the<00:30:53.399> proof 00:30:54.409 --> 00:30:54.419 align:start position:0% generate the proof 00:30:54.419 --> 00:30:55.909 align:start position:0% generate the proof Final<00:30:54.840> Approach 00:30:55.909 --> 00:30:55.919 align:start position:0% Final Approach 00:30:55.919 --> 00:30:58.909 align:start position:0% Final Approach this<00:30:56.460> optimistic<00:30:57.059> layer<00:30:57.600> so<00:30:58.440> in<00:30:58.620> terms<00:30:58.860> of 00:30:58.909 --> 00:30:58.919 align:start position:0% this optimistic layer so in terms of 00:30:58.919 --> 00:31:00.710 align:start position:0% this optimistic layer so in terms of latency<00:30:59.279> we're<00:30:59.520> happy<00:30:59.700> because<00:30:59.940> we<00:31:00.299> simply 00:31:00.710 --> 00:31:00.720 align:start position:0% latency we're happy because we simply 00:31:00.720 --> 00:31:02.510 align:start position:0% latency we're happy because we simply make<00:31:00.899> a<00:31:01.080> claim<00:31:01.320> and<00:31:01.440> we<00:31:01.620> post<00:31:01.919> it<00:31:02.220> on<00:31:02.340> the<00:31:02.460> other 00:31:02.510 --> 00:31:02.520 align:start position:0% make a claim and we post it on the other 00:31:02.520 --> 00:31:05.029 align:start position:0% make a claim and we post it on the other chain<00:31:02.880> that's<00:31:03.240> it<00:31:03.480> gas<00:31:04.020> cost<00:31:04.260> we're<00:31:04.799> very 00:31:05.029 --> 00:31:05.039 align:start position:0% chain that's it gas cost we're very 00:31:05.039 --> 00:31:06.590 align:start position:0% chain that's it gas cost we're very happy<00:31:05.220> because<00:31:05.520> the 00:31:06.590 --> 00:31:06.600 align:start position:0% happy because the 00:31:06.600 --> 00:31:08.990 align:start position:0% happy because the well<00:31:07.020> we<00:31:07.260> just<00:31:07.440> verify<00:31:07.679> a<00:31:07.860> signature 00:31:08.990 --> 00:31:09.000 align:start position:0% well we just verify a signature 00:31:09.000 --> 00:31:11.389 align:start position:0% well we just verify a signature in<00:31:09.240> terms<00:31:09.539> of<00:31:09.659> trust<00:31:10.140> well<00:31:10.500> we<00:31:10.860> are<00:31:11.039> not<00:31:11.159> that 00:31:11.389 --> 00:31:11.399 align:start position:0% in terms of trust well we are not that 00:31:11.399 --> 00:31:13.250 align:start position:0% in terms of trust well we are not that happy<00:31:11.640> but<00:31:11.940> also<00:31:12.179> not<00:31:12.360> that<00:31:12.539> sad<00:31:12.779> at<00:31:12.960> the<00:31:13.140> same 00:31:13.250 --> 00:31:13.260 align:start position:0% happy but also not that sad at the same 00:31:13.260 --> 00:31:15.590 align:start position:0% happy but also not that sad at the same time<00:31:13.440> because<00:31:14.039> it<00:31:14.460> still<00:31:14.820> can<00:31:15.059> be<00:31:15.179> challenged 00:31:15.590 --> 00:31:15.600 align:start position:0% time because it still can be challenged 00:31:15.600 --> 00:31:17.810 align:start position:0% time because it still can be challenged in<00:31:15.779> an<00:31:15.899> optimistic<00:31:16.380> manner<00:31:16.799> using<00:31:17.460> a<00:31:17.520> fraud 00:31:17.810 --> 00:31:17.820 align:start position:0% in an optimistic manner using a fraud 00:31:17.820 --> 00:31:19.090 align:start position:0% in an optimistic manner using a fraud proof 00:31:19.090 --> 00:31:19.100 align:start position:0% proof 00:31:19.100 --> 00:31:21.710 align:start position:0% proof computation<00:31:20.100> option<00:31:20.820> computation<00:31:21.240> overhead 00:31:21.710 --> 00:31:21.720 align:start position:0% computation option computation overhead 00:31:21.720 --> 00:31:23.690 align:start position:0% computation option computation overhead are<00:31:22.260> pretty<00:31:22.440> happy<00:31:22.679> because<00:31:22.919> we<00:31:23.220> participate 00:31:23.690 --> 00:31:23.700 align:start position:0% are pretty happy because we participate 00:31:23.700 --> 00:31:26.269 align:start position:0% are pretty happy because we participate like<00:31:23.880> an<00:31:24.059> NPC<00:31:24.480> protocol<00:31:25.260> so<00:31:25.679> essentially<00:31:26.039> the 00:31:26.269 --> 00:31:26.279 align:start position:0% like an NPC protocol so essentially the 00:31:26.279 --> 00:31:28.190 align:start position:0% like an NPC protocol so essentially the overhead<00:31:26.640> comes<00:31:27.120> mostly<00:31:27.419> from<00:31:27.600> communication 00:31:28.190 --> 00:31:28.200 align:start position:0% overhead comes mostly from communication 00:31:28.200 --> 00:31:31.130 align:start position:0% overhead comes mostly from communication not<00:31:29.100> computation<00:31:29.700> itself 00:31:31.130 --> 00:31:31.140 align:start position:0% not computation itself 00:31:31.140 --> 00:31:34.190 align:start position:0% not computation itself cool<00:31:31.799> so<00:31:32.460> this<00:31:32.820> is<00:31:32.940> part<00:31:33.179> number<00:31:33.360> one<00:31:33.659> these 00:31:34.190 --> 00:31:34.200 align:start position:0% cool so this is part number one these 00:31:34.200 --> 00:31:36.590 align:start position:0% cool so this is part number one these are<00:31:34.260> the<00:31:34.500> three<00:31:34.980> approaches<00:31:35.580> obviously<00:31:36.179> I'm 00:31:36.590 --> 00:31:36.600 align:start position:0% are the three approaches obviously I'm 00:31:36.600 --> 00:31:38.149 align:start position:0% are the three approaches obviously I'm not<00:31:36.779> gonna<00:31:36.899> say<00:31:37.200> which<00:31:37.440> one<00:31:37.620> is<00:31:37.799> the<00:31:37.980> best 00:31:38.149 --> 00:31:38.159 align:start position:0% not gonna say which one is the best 00:31:38.159 --> 00:31:40.070 align:start position:0% not gonna say which one is the best because<00:31:38.640> all<00:31:39.299> of<00:31:39.480> them<00:31:39.539> come<00:31:39.720> with<00:31:39.899> some 00:31:40.070 --> 00:31:40.080 align:start position:0% because all of them come with some 00:31:40.080 --> 00:31:41.630 align:start position:0% because all of them come with some trade-offs 00:31:41.630 --> 00:31:41.640 align:start position:0% trade-offs 00:31:41.640 --> 00:31:44.510 align:start position:0% trade-offs um<00:31:41.760> okay<00:31:42.260> accessing<00:31:43.260> the<00:31:43.440> headers<00:31:43.799> I<00:31:44.399> hope 00:31:44.510 --> 00:31:44.520 align:start position:0% um okay accessing the headers I hope 00:31:44.520 --> 00:31:46.070 align:start position:0% um okay accessing the headers I hope it's<00:31:44.640> self-explanatory<00:31:45.480> because<00:31:45.779> we 00:31:46.070 --> 00:31:46.080 align:start position:0% it's self-explanatory because we 00:31:46.080 --> 00:31:48.470 align:start position:0% it's self-explanatory because we literally<00:31:46.860> unroll<00:31:47.399> something<00:31:48.059> from<00:31:48.360> The 00:31:48.470 --> 00:31:48.480 align:start position:0% literally unroll something from The 00:31:48.480 --> 00:31:50.389 align:start position:0% literally unroll something from The Trusted<00:31:48.899> input 00:31:50.389 --> 00:31:50.399 align:start position:0% Trusted input 00:31:50.399 --> 00:31:52.430 align:start position:0% Trusted input and<00:31:50.820> The<00:31:50.940> Trusted<00:31:51.299> input<00:31:51.600> is<00:31:51.779> again<00:31:51.899> a<00:31:52.260> block 00:31:52.430 --> 00:31:52.440 align:start position:0% and The Trusted input is again a block 00:31:52.440 --> 00:31:56.269 align:start position:0% and The Trusted input is again a block hush<00:31:52.860> for<00:31:53.279> a<00:31:53.460> specific<00:31:53.760> block<00:31:54.179> X<00:31:54.480> and<00:31:55.440> if<00:31:56.039> you 00:31:56.269 --> 00:31:56.279 align:start position:0% hush for a specific block X and if you 00:31:56.279 --> 00:31:58.370 align:start position:0% hush for a specific block X and if you follow<00:31:56.700> the<00:31:57.059> initial<00:31:57.360> slides<00:31:57.779> that's 00:31:58.370 --> 00:31:58.380 align:start position:0% follow the initial slides that's 00:31:58.380 --> 00:32:00.289 align:start position:0% follow the initial slides that's essentially<00:31:58.799> each<00:31:59.159> block<00:31:59.460> we<00:31:59.820> given<00:32:00.179> a 00:32:00.289 --> 00:32:00.299 align:start position:0% essentially each block we given a 00:32:00.299 --> 00:32:01.490 align:start position:0% essentially each block we given a blockage<00:32:00.600> you<00:32:00.840> can<00:32:00.899> recreate<00:32:01.260> the<00:32:01.380> block 00:32:01.490 --> 00:32:01.500 align:start position:0% blockage you can recreate the block 00:32:01.500 --> 00:32:03.769 align:start position:0% blockage you can recreate the block header<00:32:01.980> and<00:32:02.520> knowing<00:32:02.880> the<00:32:03.000> block<00:32:03.120> header<00:32:03.600> we 00:32:03.769 --> 00:32:03.779 align:start position:0% header and knowing the block header we 00:32:03.779 --> 00:32:04.789 align:start position:0% header and knowing the block header we can 00:32:04.789 --> 00:32:04.799 align:start position:0% can 00:32:04.799 --> 00:32:06.950 align:start position:0% can access<00:32:05.399> the<00:32:05.700> parent<00:32:05.880> hash<00:32:06.299> and<00:32:06.480> by<00:32:06.659> knowing 00:32:06.950 --> 00:32:06.960 align:start position:0% access the parent hash and by knowing 00:32:06.960 --> 00:32:08.269 align:start position:0% access the parent hash and by knowing the<00:32:07.020> parent<00:32:07.140> hash<00:32:07.500> you<00:32:07.679> can<00:32:07.740> recreate<00:32:08.159> the 00:32:08.269 --> 00:32:08.279 align:start position:0% the parent hash you can recreate the 00:32:08.279 --> 00:32:10.250 align:start position:0% the parent hash you can recreate the previous<00:32:08.399> block<00:32:08.640> header<00:32:09.120> so<00:32:09.539> essentially<00:32:09.899> go 00:32:10.250 --> 00:32:10.260 align:start position:0% previous block header so essentially go 00:32:10.260 --> 00:32:12.169 align:start position:0% previous block header so essentially go to<00:32:10.500> the<00:32:10.740> Genesis<00:32:11.460> block 00:32:12.169 --> 00:32:12.179 align:start position:0% to the Genesis block 00:32:12.179 --> 00:32:14.450 align:start position:0% to the Genesis block so<00:32:12.600> given<00:32:13.020> this<00:32:13.200> very<00:32:13.380> small<00:32:13.620> input<00:32:14.039> we<00:32:14.340> can 00:32:14.450 --> 00:32:14.460 align:start position:0% so given this very small input we can 00:32:14.460 --> 00:32:16.490 align:start position:0% so given this very small input we can essentially<00:32:14.820> unroll<00:32:15.360> the<00:32:15.840> state<00:32:16.020> or<00:32:16.320> whatever 00:32:16.490 --> 00:32:16.500 align:start position:0% essentially unroll the state or whatever 00:32:16.500 --> 00:32:18.590 align:start position:0% essentially unroll the state or whatever was<00:32:16.860> present<00:32:17.159> on<00:32:17.340> the<00:32:17.520> chain<00:32:17.640> from<00:32:18.240> this<00:32:18.419> block 00:32:18.590 --> 00:32:18.600 align:start position:0% was present on the chain from this block 00:32:18.600 --> 00:32:21.049 align:start position:0% was present on the chain from this block till<00:32:19.200> the<00:32:19.440> Chinese<00:32:19.559> is<00:32:19.919> block 00:32:21.049 --> 00:32:21.059 align:start position:0% till the Chinese is block 00:32:21.059 --> 00:32:24.289 align:start position:0% till the Chinese is block okay<00:32:21.539> so<00:32:22.380> as<00:32:23.220> I<00:32:23.399> said<00:32:23.520> I'm<00:32:23.820> gonna<00:32:24.000> explain 00:32:24.289 --> 00:32:24.299 align:start position:0% okay so as I said I'm gonna explain 00:32:24.299 --> 00:32:27.289 align:start position:0% okay so as I said I'm gonna explain everything<00:32:24.840> on<00:32:25.799> on<00:32:26.159> the<00:32:26.399> example<00:32:26.640> of<00:32:26.820> ethereum 00:32:27.289 --> 00:32:27.299 align:start position:0% everything on on the example of ethereum 00:32:27.299 --> 00:32:30.590 align:start position:0% everything on on the example of ethereum and<00:32:27.960> today<00:32:28.559> all<00:32:29.159> the<00:32:29.340> block<00:32:29.460> headers<00:32:29.940> together 00:32:30.590 --> 00:32:30.600 align:start position:0% and today all the block headers together 00:32:30.600 --> 00:32:34.130 align:start position:0% and today all the block headers together are<00:32:31.080> like<00:32:31.320> roughly<00:32:31.919> seven<00:32:32.159> gigabytes<00:32:32.700> of<00:32:32.880> data 00:32:34.130 --> 00:32:34.140 align:start position:0% are like roughly seven gigabytes of data 00:32:34.140 --> 00:32:36.889 align:start position:0% are like roughly seven gigabytes of data so<00:32:34.559> it's<00:32:34.679> quite<00:32:34.919> a<00:32:35.039> lot<00:32:35.159> but<00:32:36.059> okay<00:32:36.179> this<00:32:36.600> is<00:32:36.659> how 00:32:36.889 --> 00:32:36.899 align:start position:0% so it's quite a lot but okay this is how 00:32:36.899 --> 00:32:38.510 align:start position:0% so it's quite a lot but okay this is how we<00:32:37.140> actually<00:32:37.620> do<00:32:37.860> that<00:32:37.980> this<00:32:38.159> is<00:32:38.279> the<00:32:38.399> high 00:32:38.510 --> 00:32:38.520 align:start position:0% we actually do that this is the high 00:32:38.520 --> 00:32:39.889 align:start position:0% we actually do that this is the high level<00:32:38.700> concept<00:32:39.179> and<00:32:39.419> what<00:32:39.600> are<00:32:39.779> the 00:32:39.889 --> 00:32:39.899 align:start position:0% level concept and what are the 00:32:39.899 --> 00:32:40.970 align:start position:0% level concept and what are the approaches 00:32:40.970 --> 00:32:40.980 align:start position:0% approaches 00:32:40.980 --> 00:32:42.710 align:start position:0% approaches so<00:32:41.520> the<00:32:41.760> first<00:32:41.880> one<00:32:42.059> we<00:32:42.299> call<00:32:42.419> it<00:32:42.539> like 00:32:42.710 --> 00:32:42.720 align:start position:0% so the first one we call it like 00:32:42.720 --> 00:32:45.049 align:start position:0% so the first one we call it like on-train<00:32:43.140> accumulation<00:32:43.740> so<00:32:44.399> essentially<00:32:44.760> we 00:32:45.049 --> 00:32:45.059 align:start position:0% on-train accumulation so essentially we 00:32:45.059 --> 00:32:47.029 align:start position:0% on-train accumulation so essentially we do<00:32:45.240> this<00:32:45.480> procedure<00:32:46.200> this<00:32:46.559> computation 00:32:47.029 --> 00:32:47.039 align:start position:0% do this procedure this computation 00:32:47.039 --> 00:32:49.850 align:start position:0% do this procedure this computation directly<00:32:47.940> on<00:32:48.059> the<00:32:48.240> Chain<00:32:48.360> so<00:32:48.659> we<00:32:48.840> provide<00:32:49.200> all 00:32:49.850 --> 00:32:49.860 align:start position:0% directly on the Chain so we provide all 00:32:49.860 --> 00:32:51.590 align:start position:0% directly on the Chain so we provide all these<00:32:50.159> properly<00:32:50.580> encoded<00:32:51.000> block<00:32:51.179> headers 00:32:51.590 --> 00:32:51.600 align:start position:0% these properly encoded block headers 00:32:51.600 --> 00:32:54.049 align:start position:0% these properly encoded block headers inside<00:32:52.440> the<00:32:52.679> call<00:32:52.860> data 00:32:54.049 --> 00:32:54.059 align:start position:0% inside the call data 00:32:54.059 --> 00:32:56.630 align:start position:0% inside the call data and<00:32:54.840> the<00:32:55.380> blockers<00:32:55.679> that<00:32:55.919> we<00:32:56.039> might<00:32:56.279> receive 00:32:56.630 --> 00:32:56.640 align:start position:0% and the blockers that we might receive 00:32:56.640 --> 00:32:58.730 align:start position:0% and the blockers that we might receive as<00:32:56.940> like<00:32:57.120> The<00:32:57.299> Trusted<00:32:57.659> input<00:32:57.960> by<00:32:58.260> sending<00:32:58.559> a 00:32:58.730 --> 00:32:58.740 align:start position:0% as like The Trusted input by sending a 00:32:58.740 --> 00:33:00.950 align:start position:0% as like The Trusted input by sending a message<00:32:58.919> relaying<00:32:59.820> it<00:32:59.880> in<00:33:00.000> optimistic<00:33:00.600> manner 00:33:00.950 --> 00:33:00.960 align:start position:0% message relaying it in optimistic manner 00:33:00.960 --> 00:33:03.350 align:start position:0% message relaying it in optimistic manner or<00:33:01.380> validating<00:33:01.799> the<00:33:02.039> consensus 00:33:03.350 --> 00:33:03.360 align:start position:0% or validating the consensus 00:33:03.360 --> 00:33:06.409 align:start position:0% or validating the consensus and<00:33:04.320> yeah<00:33:04.799> like<00:33:05.100> recursively<00:33:05.820> go<00:33:06.000> through<00:33:06.179> all 00:33:06.409 --> 00:33:06.419 align:start position:0% and yeah like recursively go through all 00:33:06.419 --> 00:33:08.990 align:start position:0% and yeah like recursively go through all these<00:33:06.600> headers<00:33:07.020> and<00:33:07.620> and<00:33:07.740> verify<00:33:08.220> them<00:33:08.399> but 00:33:08.990 --> 00:33:09.000 align:start position:0% these headers and and verify them but 00:33:09.000 --> 00:33:11.630 align:start position:0% these headers and and verify them but there<00:33:09.539> are<00:33:09.720> many<00:33:10.140> many<00:33:10.380> downsides<00:33:11.100> because 00:33:11.630 --> 00:33:11.640 align:start position:0% there are many many downsides because 00:33:11.640 --> 00:33:13.970 align:start position:0% there are many many downsides because first<00:33:12.000> of<00:33:12.179> all<00:33:12.299> it's<00:33:12.899> very<00:33:13.320> cool<00:33:13.559> data 00:33:13.970 --> 00:33:13.980 align:start position:0% first of all it's very cool data 00:33:13.980 --> 00:33:15.710 align:start position:0% first of all it's very cool data intensive<00:33:14.519> it's<00:33:15.000> very<00:33:15.240> computational 00:33:15.710 --> 00:33:15.720 align:start position:0% intensive it's very computational 00:33:15.720 --> 00:33:18.350 align:start position:0% intensive it's very computational intensive<00:33:16.440> and<00:33:17.039> now<00:33:17.220> we<00:33:17.399> can<00:33:17.580> store<00:33:17.820> all<00:33:18.179> these 00:33:18.350 --> 00:33:18.360 align:start position:0% intensive and now we can store all these 00:33:18.360 --> 00:33:20.810 align:start position:0% intensive and now we can store all these headers<00:33:18.720> on<00:33:19.440> the<00:33:19.620> actual<00:33:19.860> chain<00:33:20.100> but<00:33:20.399> you<00:33:20.700> know 00:33:20.810 --> 00:33:20.820 align:start position:0% headers on the actual chain but you know 00:33:20.820 --> 00:33:22.370 align:start position:0% headers on the actual chain but you know even<00:33:21.120> storing 00:33:22.370 --> 00:33:22.380 align:start position:0% even storing 00:33:22.380 --> 00:33:25.610 align:start position:0% even storing on<00:33:22.919> an<00:33:23.100> L2<00:33:23.460> is<00:33:24.000> throwing<00:33:24.419> 7<00:33:24.600> gigabytes<00:33:25.080> of<00:33:25.260> data 00:33:25.610 --> 00:33:25.620 align:start position:0% on an L2 is throwing 7 gigabytes of data 00:33:25.620 --> 00:33:28.490 align:start position:0% on an L2 is throwing 7 gigabytes of data is<00:33:26.340> still<00:33:26.519> a<00:33:26.760> significant<00:33:27.120> cost<00:33:27.360> because<00:33:27.720> the 00:33:28.490 --> 00:33:28.500 align:start position:0% is still a significant cost because the 00:33:28.500 --> 00:33:30.889 align:start position:0% is still a significant cost because the state<00:33:28.679> on<00:33:28.860> an<00:33:29.039> L2<00:33:29.340> is<00:33:29.519> reflected<00:33:29.940> as<00:33:30.179> call<00:33:30.539> data 00:33:30.889 --> 00:33:30.899 align:start position:0% state on an L2 is reflected as call data 00:33:30.899 --> 00:33:34.789 align:start position:0% state on an L2 is reflected as call data on<00:33:31.019> L1<00:33:31.440> so<00:33:32.279> it's<00:33:32.940> still<00:33:33.299> expensive<00:33:33.779> either<00:33:34.019> way 00:33:34.789 --> 00:33:34.799 align:start position:0% on L1 so it's still expensive either way 00:33:34.799 --> 00:33:36.769 align:start position:0% on L1 so it's still expensive either way but<00:33:35.279> the<00:33:35.399> cool<00:33:35.519> thing<00:33:35.820> is<00:33:36.000> that<00:33:36.120> I<00:33:36.299> have<00:33:36.480> direct 00:33:36.769 --> 00:33:36.779 align:start position:0% but the cool thing is that I have direct 00:33:36.779 --> 00:33:39.529 align:start position:0% but the cool thing is that I have direct access<00:33:37.140> to<00:33:37.919> like<00:33:38.460> State<00:33:38.760> routes<00:33:39.120> or<00:33:39.240> anything 00:33:39.529 --> 00:33:39.539 align:start position:0% access to like State routes or anything 00:33:39.539 --> 00:33:42.649 align:start position:0% access to like State routes or anything that<00:33:39.899> I<00:33:40.019> want<00:33:40.140> to<00:33:40.260> access 00:33:42.649 --> 00:33:42.659 align:start position:0% 00:33:42.659 --> 00:33:46.490 align:start position:0% next<00:33:43.080> approach<00:33:43.500> is<00:33:44.399> unchain<00:33:44.880> compression 00:33:46.490 --> 00:33:46.500 align:start position:0% next approach is unchain compression 00:33:46.500 --> 00:33:49.430 align:start position:0% next approach is unchain compression so<00:33:47.159> we<00:33:47.640> can<00:33:47.880> still<00:33:48.240> use<00:33:48.659> the<00:33:48.840> same<00:33:49.019> approaches 00:33:49.430 --> 00:33:49.440 align:start position:0% so we can still use the same approaches 00:33:49.440 --> 00:33:52.549 align:start position:0% so we can still use the same approaches previously<00:33:49.919> so<00:33:50.279> literally<00:33:50.640> unroll<00:33:51.120> it<00:33:51.559> and 00:33:52.549 --> 00:33:52.559 align:start position:0% previously so literally unroll it and 00:33:52.559 --> 00:33:55.009 align:start position:0% previously so literally unroll it and process<00:33:53.340> this<00:33:53.580> seven<00:33:53.820> gigabytes<00:33:54.419> of<00:33:54.539> data<00:33:54.840> but 00:33:55.009 --> 00:33:55.019 align:start position:0% process this seven gigabytes of data but 00:33:55.019 --> 00:33:57.110 align:start position:0% process this seven gigabytes of data but instead<00:33:55.320> of<00:33:55.440> like<00:33:55.620> storing<00:33:56.100> then<00:33:56.640> we<00:33:56.880> can<00:33:57.000> just 00:33:57.110 --> 00:33:57.120 align:start position:0% instead of like storing then we can just 00:33:57.120 --> 00:33:59.090 align:start position:0% instead of like storing then we can just update<00:33:57.480> the<00:33:57.600> miracle<00:33:57.899> tree<00:33:58.140> it's<00:33:58.799> a<00:33:58.980> nice 00:33:59.090 --> 00:33:59.100 align:start position:0% update the miracle tree it's a nice 00:33:59.100 --> 00:34:01.130 align:start position:0% update the miracle tree it's a nice approach<00:33:59.460> but<00:33:59.760> comes<00:34:00.240> again<00:34:00.419> with<00:34:00.720> a<00:34:00.840> few<00:34:00.960> dump 00:34:01.130 --> 00:34:01.140 align:start position:0% approach but comes again with a few dump 00:34:01.140 --> 00:34:03.710 align:start position:0% approach but comes again with a few dump sites<00:34:01.559> it's<00:34:02.279> very<00:34:02.519> computationally<00:34:03.179> intense 00:34:03.710 --> 00:34:03.720 align:start position:0% sites it's very computationally intense 00:34:03.720 --> 00:34:05.389 align:start position:0% sites it's very computationally intense because<00:34:04.080> if<00:34:04.500> we<00:34:04.620> have<00:34:04.740> like<00:34:04.919> millions<00:34:05.220> of 00:34:05.389 --> 00:34:05.399 align:start position:0% because if we have like millions of 00:34:05.399 --> 00:34:07.549 align:start position:0% because if we have like millions of headers<00:34:05.760> we<00:34:06.000> need<00:34:06.179> to<00:34:06.480> perform<00:34:06.840> millions<00:34:07.380> of 00:34:07.549 --> 00:34:07.559 align:start position:0% headers we need to perform millions of 00:34:07.559 --> 00:34:09.889 align:start position:0% headers we need to perform millions of hashes<00:34:07.980> on<00:34:08.339> the<00:34:08.460> Chain<00:34:08.659> that's<00:34:09.659> that's 00:34:09.889 --> 00:34:09.899 align:start position:0% hashes on the Chain that's that's 00:34:09.899 --> 00:34:12.589 align:start position:0% hashes on the Chain that's that's expensive<00:34:10.500> but<00:34:10.980> at<00:34:11.159> least<00:34:11.280> we<00:34:11.580> we<00:34:11.879> save<00:34:12.119> on<00:34:12.419> on 00:34:12.589 --> 00:34:12.599 align:start position:0% expensive but at least we we save on on 00:34:12.599 --> 00:34:15.530 align:start position:0% expensive but at least we we save on on storing<00:34:13.020> data<00:34:13.879> and<00:34:14.879> also<00:34:15.060> we<00:34:15.119> need<00:34:15.300> to<00:34:15.359> update 00:34:15.530 --> 00:34:15.540 align:start position:0% storing data and also we need to update 00:34:15.540 --> 00:34:16.909 align:start position:0% storing data and also we need to update the<00:34:15.659> miracle<00:34:15.960> tree<00:34:16.139> which<00:34:16.379> is<00:34:16.500> which<00:34:16.740> is 00:34:16.909 --> 00:34:16.919 align:start position:0% the miracle tree which is which is 00:34:16.919 --> 00:34:18.829 align:start position:0% the miracle tree which is which is another<00:34:17.040> cost 00:34:18.829 --> 00:34:18.839 align:start position:0% another cost 00:34:18.839 --> 00:34:19.490 align:start position:0% another cost um 00:34:19.490 --> 00:34:19.500 align:start position:0% um 00:34:19.500 --> 00:34:22.430 align:start position:0% um last<00:34:20.099> downside<00:34:20.580> is<00:34:21.359> that<00:34:21.540> we<00:34:21.659> need<00:34:21.839> to<00:34:22.020> index 00:34:22.430 --> 00:34:22.440 align:start position:0% last downside is that we need to index 00:34:22.440 --> 00:34:24.290 align:start position:0% last downside is that we need to index all<00:34:22.859> the<00:34:22.980> headers<00:34:23.280> that<00:34:23.460> have<00:34:23.639> been<00:34:23.820> processed 00:34:24.290 --> 00:34:24.300 align:start position:0% all the headers that have been processed 00:34:24.300 --> 00:34:26.389 align:start position:0% all the headers that have been processed why<00:34:24.720> we<00:34:24.960> need<00:34:25.020> to<00:34:25.139> index<00:34:25.440> them<00:34:25.679> because<00:34:25.859> if<00:34:26.220> I 00:34:26.389 --> 00:34:26.399 align:start position:0% why we need to index them because if I 00:34:26.399 --> 00:34:27.470 align:start position:0% why we need to index them because if I want<00:34:26.580> to 00:34:27.470 --> 00:34:27.480 align:start position:0% want to 00:34:27.480 --> 00:34:31.369 align:start position:0% want to up<00:34:28.020> the<00:34:28.260> access<00:34:28.800> a<00:34:29.580> specific<00:34:29.940> block<00:34:30.179> header<00:34:30.659> I 00:34:31.369 --> 00:34:31.379 align:start position:0% up the access a specific block header I 00:34:31.379 --> 00:34:32.690 align:start position:0% up the access a specific block header I need<00:34:31.560> to<00:34:31.679> provide<00:34:31.859> a<00:34:32.040> miracle<00:34:32.339> path<00:34:32.580> because 00:34:32.690 --> 00:34:32.700 align:start position:0% need to provide a miracle path because 00:34:32.700 --> 00:34:35.089 align:start position:0% need to provide a miracle path because as<00:34:32.879> we<00:34:33.000> update<00:34:33.240> the<00:34:33.419> miracle<00:34:33.720> 3<00:34:33.839> and<00:34:34.800> we<00:34:34.919> just 00:34:35.089 --> 00:34:35.099 align:start position:0% as we update the miracle 3 and we just 00:34:35.099 --> 00:34:37.190 align:start position:0% as we update the miracle 3 and we just store<00:34:35.280> the<00:34:35.520> root<00:34:35.700> in<00:34:36.419> the<00:34:36.599> contract<00:34:36.899> itself 00:34:37.190 --> 00:34:37.200 align:start position:0% store the root in the contract itself 00:34:37.200 --> 00:34:38.869 align:start position:0% store the root in the contract itself then<00:34:37.560> I<00:34:37.740> need<00:34:37.859> to<00:34:37.919> know<00:34:38.040> the<00:34:38.159> path<00:34:38.280> right<00:34:38.580> so<00:34:38.760> I 00:34:38.869 --> 00:34:38.879 align:start position:0% then I need to know the path right so I 00:34:38.879 --> 00:34:41.149 align:start position:0% then I need to know the path right so I need<00:34:39.000> to<00:34:39.119> index<00:34:39.659> the<00:34:39.899> data<00:34:40.260> and<00:34:40.379> essentially 00:34:41.149 --> 00:34:41.159 align:start position:0% need to index the data and essentially 00:34:41.159 --> 00:34:43.369 align:start position:0% need to index the data and essentially once<00:34:42.060> I<00:34:42.179> it's<00:34:42.480> the<00:34:42.659> moment<00:34:42.839> that<00:34:42.960> I<00:34:43.139> want<00:34:43.260> to 00:34:43.369 --> 00:34:43.379 align:start position:0% once I it's the moment that I want to 00:34:43.379 --> 00:34:45.530 align:start position:0% once I it's the moment that I want to access<00:34:43.440> that<00:34:43.740> I<00:34:43.919> need<00:34:43.980> to<00:34:44.099> provide<00:34:44.339> a<00:34:44.760> miracle 00:34:45.530 --> 00:34:45.540 align:start position:0% access that I need to provide a miracle 00:34:45.540 --> 00:34:46.490 align:start position:0% access that I need to provide a miracle path 00:34:46.490 --> 00:34:46.500 align:start position:0% path 00:34:46.500 --> 00:34:49.070 align:start position:0% path this<00:34:46.919> approach<00:34:47.220> is<00:34:47.399> okay<00:34:47.700> it's 00:34:49.070 --> 00:34:49.080 align:start position:0% this approach is okay it's 00:34:49.080 --> 00:34:50.810 align:start position:0% this approach is okay it's I<00:34:49.679> wouldn't<00:34:49.800> say<00:34:49.980> way<00:34:50.159> better<00:34:50.399> than<00:34:50.639> the 00:34:50.810 --> 00:34:50.820 align:start position:0% I wouldn't say way better than the 00:34:50.820 --> 00:34:54.950 align:start position:0% I wouldn't say way better than the previous<00:34:50.940> one<00:34:51.240> but<00:34:51.599> it's<00:34:52.200> way<00:34:52.679> cheaper 00:34:54.950 --> 00:34:54.960 align:start position:0% previous one but it's way cheaper 00:34:54.960 --> 00:34:56.750 align:start position:0% previous one but it's way cheaper last<00:34:55.560> approach 00:34:56.750 --> 00:34:56.760 align:start position:0% last approach 00:34:56.760 --> 00:34:59.210 align:start position:0% last approach so<00:34:57.240> there<00:34:57.540> is<00:34:57.720> a<00:34:57.900> very<00:34:58.080> cool<00:34:58.320> primitive<00:34:58.859> called 00:34:59.210 --> 00:34:59.220 align:start position:0% so there is a very cool primitive called 00:34:59.220 --> 00:35:01.310 align:start position:0% so there is a very cool primitive called Merkel<00:34:59.760> mountain<00:34:59.940> ranges 00:35:01.310 --> 00:35:01.320 align:start position:0% Merkel mountain ranges 00:35:01.320 --> 00:35:04.490 align:start position:0% Merkel mountain ranges love<00:35:01.980> it<00:35:02.220> and<00:35:03.060> the<00:35:03.180> idea<00:35:03.420> is<00:35:03.660> let's<00:35:04.020> do<00:35:04.320> the 00:35:04.490 --> 00:35:04.500 align:start position:0% love it and the idea is let's do the 00:35:04.500 --> 00:35:05.930 align:start position:0% love it and the idea is let's do the same 00:35:05.930 --> 00:35:05.940 align:start position:0% same 00:35:05.940 --> 00:35:08.870 align:start position:0% same that<00:35:06.359> we<00:35:06.480> do<00:35:06.660> previously<00:35:07.140> inside<00:35:07.440> this<00:35:07.740> Arc<00:35:08.160> so 00:35:08.870 --> 00:35:08.880 align:start position:0% that we do previously inside this Arc so 00:35:08.880 --> 00:35:11.510 align:start position:0% that we do previously inside this Arc so we<00:35:09.119> can<00:35:09.240> provide<00:35:09.660> this<00:35:10.380> tremendous<00:35:11.040> amount<00:35:11.339> of 00:35:11.510 --> 00:35:11.520 align:start position:0% we can provide this tremendous amount of 00:35:11.520 --> 00:35:14.510 align:start position:0% we can provide this tremendous amount of data<00:35:11.880> as<00:35:12.420> a<00:35:12.599> private<00:35:12.839> input<00:35:13.140> to<00:35:13.260> the<00:35:13.380> circuit 00:35:14.510 --> 00:35:14.520 align:start position:0% data as a private input to the circuit 00:35:14.520 --> 00:35:16.730 align:start position:0% data as a private input to the circuit and<00:35:15.180> essentially<00:35:15.660> do<00:35:15.960> the<00:35:16.140> same<00:35:16.260> computation 00:35:16.730 --> 00:35:16.740 align:start position:0% and essentially do the same computation 00:35:16.740 --> 00:35:19.670 align:start position:0% and essentially do the same computation like<00:35:16.980> unrolling<00:35:17.780> inside<00:35:18.780> this<00:35:19.020> record<00:35:19.200> itself 00:35:19.670 --> 00:35:19.680 align:start position:0% like unrolling inside this record itself 00:35:19.680 --> 00:35:22.250 align:start position:0% like unrolling inside this record itself and<00:35:20.280> now<00:35:20.520> we<00:35:21.119> have<00:35:21.300> a<00:35:21.420> public<00:35:21.540> input<00:35:21.960> which<00:35:22.200> is 00:35:22.250 --> 00:35:22.260 align:start position:0% and now we have a public input which is 00:35:22.260 --> 00:35:23.510 align:start position:0% and now we have a public input which is the<00:35:22.440> blockage<00:35:22.740> so<00:35:22.980> essentially<00:35:23.339> the 00:35:23.510 --> 00:35:23.520 align:start position:0% the blockage so essentially the 00:35:23.520 --> 00:35:26.150 align:start position:0% the blockage so essentially the commitment<00:35:23.940> from<00:35:24.240> which<00:35:24.420> we<00:35:24.660> unroll<00:35:25.380> it 00:35:26.150 --> 00:35:26.160 align:start position:0% commitment from which we unroll it 00:35:26.160 --> 00:35:28.550 align:start position:0% commitment from which we unroll it so<00:35:26.880> the<00:35:27.180> trusted<00:35:27.540> input<00:35:27.839> the<00:35:28.020> public<00:35:28.140> input 00:35:28.550 --> 00:35:28.560 align:start position:0% so the trusted input the public input 00:35:28.560 --> 00:35:30.290 align:start position:0% so the trusted input the public input can<00:35:28.740> be<00:35:28.920> literally<00:35:29.220> asserted<00:35:29.760> when<00:35:29.940> we<00:35:30.060> do<00:35:30.180> the 00:35:30.290 --> 00:35:30.300 align:start position:0% can be literally asserted when we do the 00:35:30.300 --> 00:35:32.030 align:start position:0% can be literally asserted when we do the on-train<00:35:30.660> verification 00:35:32.030 --> 00:35:32.040 align:start position:0% on-train verification 00:35:32.040 --> 00:35:34.250 align:start position:0% on-train verification and<00:35:32.579> why<00:35:32.760> we<00:35:32.940> unroll<00:35:33.240> it<00:35:33.480> we<00:35:33.660> can<00:35:33.780> accumulate 00:35:34.250 --> 00:35:34.260 align:start position:0% and why we unroll it we can accumulate 00:35:34.260 --> 00:35:36.349 align:start position:0% and why we unroll it we can accumulate inside<00:35:34.440> the<00:35:34.680> miracle<00:35:35.040> tree<00:35:35.220> or<00:35:36.060> American 00:35:36.349 --> 00:35:36.359 align:start position:0% inside the miracle tree or American 00:35:36.359 --> 00:35:38.270 align:start position:0% inside the miracle tree or American mountain<00:35:36.780> range<00:35:37.200> why<00:35:37.560> American<00:35:37.859> mountain 00:35:38.270 --> 00:35:38.280 align:start position:0% mountain range why American mountain 00:35:38.280 --> 00:35:40.790 align:start position:0% mountain range why American mountain range<00:35:38.760> is<00:35:39.119> is<00:35:39.359> cool<00:35:39.660> because<00:35:40.020> well<00:35:40.320> let's 00:35:40.790 --> 00:35:40.800 align:start position:0% range is is cool because well let's 00:35:40.800 --> 00:35:43.130 align:start position:0% range is is cool because well let's imagine<00:35:40.980> that<00:35:41.280> you<00:35:41.400> want<00:35:41.579> to<00:35:41.700> have<00:35:41.880> like<00:35:42.180> seven 00:35:43.130 --> 00:35:43.140 align:start position:0% imagine that you want to have like seven 00:35:43.140 --> 00:35:45.109 align:start position:0% imagine that you want to have like seven gigabytes<00:35:43.920> of<00:35:44.040> data<00:35:44.339> processing<00:35:44.700> one<00:35:44.940> star 00:35:45.109 --> 00:35:45.119 align:start position:0% gigabytes of data processing one star 00:35:45.119 --> 00:35:46.790 align:start position:0% gigabytes of data processing one star like<00:35:45.300> the<00:35:45.480> proving<00:35:45.720> time<00:35:45.900> is<00:35:46.079> going<00:35:46.440> to<00:35:46.560> be 00:35:46.790 --> 00:35:46.800 align:start position:0% like the proving time is going to be 00:35:46.800 --> 00:35:48.650 align:start position:0% like the proving time is going to be horrible<00:35:47.160> and<00:35:47.520> why<00:35:47.700> would<00:35:48.000> you<00:35:48.240> even<00:35:48.300> like 00:35:48.650 --> 00:35:48.660 align:start position:0% horrible and why would you even like 00:35:48.660 --> 00:35:51.470 align:start position:0% horrible and why would you even like prove<00:35:49.980> this<00:35:50.400> commitment<00:35:50.820> for<00:35:51.119> like<00:35:51.300> the 00:35:51.470 --> 00:35:51.480 align:start position:0% prove this commitment for like the 00:35:51.480 --> 00:35:53.270 align:start position:0% prove this commitment for like the entire<00:35:51.780> history<00:35:52.020> like<00:35:52.560> do<00:35:52.800> you<00:35:52.920> really<00:35:53.040> need 00:35:53.270 --> 00:35:53.280 align:start position:0% entire history like do you really need 00:35:53.280 --> 00:35:56.870 align:start position:0% entire history like do you really need that<00:35:53.460> probably<00:35:54.060> not<00:35:54.359> so<00:35:55.320> let's<00:35:55.980> chunk<00:35:56.460> it<00:35:56.640> like 00:35:56.870 --> 00:35:56.880 align:start position:0% that probably not so let's chunk it like 00:35:56.880 --> 00:35:58.849 align:start position:0% that probably not so let's chunk it like into<00:35:57.000> smaller<00:35:57.420> pieces<00:35:57.780> and<00:35:58.320> Miracle<00:35:58.740> mountain 00:35:58.849 --> 00:35:58.859 align:start position:0% into smaller pieces and Miracle mountain 00:35:58.859 --> 00:36:01.250 align:start position:0% into smaller pieces and Miracle mountain ranges<00:35:59.460> are<00:35:59.700> pretty<00:36:00.000> cool<00:36:00.240> primitive<00:36:00.720> that 00:36:01.250 --> 00:36:01.260 align:start position:0% ranges are pretty cool primitive that 00:36:01.260 --> 00:36:04.010 align:start position:0% ranges are pretty cool primitive that allow<00:36:01.560> to<00:36:01.800> do<00:36:01.920> this<00:36:02.099> to<00:36:02.460> do<00:36:02.640> to<00:36:02.820> do<00:36:03.000> this 00:36:04.010 --> 00:36:04.020 align:start position:0% allow to do this to do to do this 00:36:04.020 --> 00:36:07.490 align:start position:0% allow to do this to do to do this to<00:36:04.500> give<00:36:04.619> you<00:36:04.800> like<00:36:05.040> a<00:36:05.579> bit<00:36:05.880> of<00:36:06.000> intuition<00:36:06.500> how 00:36:07.490 --> 00:36:07.500 align:start position:0% to give you like a bit of intuition how 00:36:07.500 --> 00:36:09.829 align:start position:0% to give you like a bit of intuition how how<00:36:07.680> does<00:36:07.859> it<00:36:08.040> work<00:36:08.220> it's<00:36:08.940> essential<00:36:09.359> think<00:36:09.660> of 00:36:09.829 --> 00:36:09.839 align:start position:0% how does it work it's essential think of 00:36:09.839 --> 00:36:12.170 align:start position:0% how does it work it's essential think of it<00:36:09.960> as<00:36:10.140> a<00:36:10.320> tree<00:36:10.440> of<00:36:10.680> trees 00:36:12.170 --> 00:36:12.180 align:start position:0% it as a tree of trees 00:36:12.180 --> 00:36:14.630 align:start position:0% it as a tree of trees um<00:36:12.240> yeah<00:36:12.599> so<00:36:12.960> once<00:36:13.680> we<00:36:13.800> do<00:36:13.920> all<00:36:14.099> this<00:36:14.280> proving 00:36:14.630 --> 00:36:14.640 align:start position:0% um yeah so once we do all this proving 00:36:14.640 --> 00:36:16.790 align:start position:0% um yeah so once we do all this proving like<00:36:14.820> of<00:36:15.000> chain<00:36:15.300> we<00:36:15.599> simply<00:36:16.020> verify<00:36:16.380> the<00:36:16.560> proof 00:36:16.790 --> 00:36:16.800 align:start position:0% like of chain we simply verify the proof 00:36:16.800 --> 00:36:18.829 align:start position:0% like of chain we simply verify the proof on<00:36:16.980> chain<00:36:17.220> as<00:36:17.880> you<00:36:18.060> know<00:36:18.180> like<00:36:18.300> refine<00:36:18.720> the 00:36:18.829 --> 00:36:18.839 align:start position:0% on chain as you know like refine the 00:36:18.839 --> 00:36:20.089 align:start position:0% on chain as you know like refine the proof<00:36:19.079> is 00:36:20.089 --> 00:36:20.099 align:start position:0% proof is 00:36:20.099 --> 00:36:22.069 align:start position:0% proof is way<00:36:20.640> cheaper<00:36:20.940> than<00:36:21.119> doing<00:36:21.300> this<00:36:21.540> directly<00:36:21.900> on 00:36:22.069 --> 00:36:22.079 align:start position:0% way cheaper than doing this directly on 00:36:22.079 --> 00:36:23.030 align:start position:0% way cheaper than doing this directly on the<00:36:22.200> chain 00:36:23.030 --> 00:36:23.040 align:start position:0% the chain 00:36:23.040 --> 00:36:26.030 align:start position:0% the chain and<00:36:23.700> still<00:36:24.119> we<00:36:24.660> just<00:36:25.079> provide<00:36:25.380> a<00:36:25.500> miracle<00:36:25.859> path 00:36:26.030 --> 00:36:26.040 align:start position:0% and still we just provide a miracle path 00:36:26.040 --> 00:36:28.370 align:start position:0% and still we just provide a miracle path and<00:36:26.400> that's<00:36:26.520> it<00:36:27.180> we<00:36:27.660> essentially<00:36:27.960> have<00:36:28.260> access 00:36:28.370 --> 00:36:28.380 align:start position:0% and that's it we essentially have access 00:36:28.380 --> 00:36:30.710 align:start position:0% and that's it we essentially have access to<00:36:28.619> any<00:36:28.740> sort<00:36:28.980> of<00:36:29.099> data<00:36:29.400> we<00:36:29.520> want 00:36:30.710 --> 00:36:30.720 align:start position:0% to any sort of data we want 00:36:30.720 --> 00:36:34.069 align:start position:0% to any sort of data we want let's<00:36:31.200> do<00:36:31.440> a<00:36:31.560> recap<00:36:31.859> again<00:36:32.339> so<00:36:33.079> approach 00:36:34.069 --> 00:36:34.079 align:start position:0% let's do a recap again so approach 00:36:34.079 --> 00:36:36.650 align:start position:0% let's do a recap again so approach number<00:36:34.260> one<00:36:34.500> answer<00:36:34.859> accumulation<00:36:35.579> on<00:36:36.359> chain 00:36:36.650 --> 00:36:36.660 align:start position:0% number one answer accumulation on chain 00:36:36.660 --> 00:36:39.589 align:start position:0% number one answer accumulation on chain compression<00:36:37.200> option<00:36:38.160> compression<00:36:38.700> three 00:36:39.589 --> 00:36:39.599 align:start position:0% compression option compression three 00:36:39.599 --> 00:36:42.290 align:start position:0% compression option compression three categories<00:36:40.140> prover<00:36:40.800> overhead<00:36:41.280> gas<00:36:42.000> cost 00:36:42.290 --> 00:36:42.300 align:start position:0% categories prover overhead gas cost 00:36:42.300 --> 00:36:44.270 align:start position:0% categories prover overhead gas cost storage<00:36:42.900> cost 00:36:44.270 --> 00:36:44.280 align:start position:0% storage cost 00:36:44.280 --> 00:36:46.370 align:start position:0% storage cost actually<00:36:44.760> gasket<00:36:45.240> should<00:36:45.660> be<00:36:45.780> computational 00:36:46.370 --> 00:36:46.380 align:start position:0% actually gasket should be computational 00:36:46.380 --> 00:36:47.810 align:start position:0% actually gasket should be computational cost 00:36:47.810 --> 00:36:47.820 align:start position:0% cost 00:36:47.820 --> 00:36:49.790 align:start position:0% cost okay<00:36:48.240> so<00:36:48.480> prover<00:36:48.780> overhead<00:36:49.260> on<00:36:49.560> chain 00:36:49.790 --> 00:36:49.800 align:start position:0% okay so prover overhead on chain 00:36:49.800 --> 00:36:52.190 align:start position:0% okay so prover overhead on chain cumulation<00:36:50.220> do<00:36:50.820> we<00:36:50.940> prove<00:36:51.180> anything<00:36:51.359> well<00:36:51.780> not 00:36:52.190 --> 00:36:52.200 align:start position:0% cumulation do we prove anything well not 00:36:52.200 --> 00:36:54.829 align:start position:0% cumulation do we prove anything well not really<00:36:52.380> so<00:36:53.220> we<00:36:53.400> are<00:36:53.579> happy<00:36:53.839> answering 00:36:54.829 --> 00:36:54.839 align:start position:0% really so we are happy answering 00:36:54.839 --> 00:36:55.910 align:start position:0% really so we are happy answering compression 00:36:55.910 --> 00:36:55.920 align:start position:0% compression 00:36:55.920 --> 00:37:00.349 align:start position:0% compression well 00:37:00.349 --> 00:37:00.359 align:start position:0% 00:37:00.359 --> 00:37:02.329 align:start position:0% we<00:37:00.900> still<00:37:01.140> like<00:37:01.320> need<00:37:01.500> to<00:37:01.619> update<00:37:01.920> the<00:37:02.040> miracle 00:37:02.329 --> 00:37:02.339 align:start position:0% we still like need to update the miracle 00:37:02.339 --> 00:37:04.550 align:start position:0% we still like need to update the miracle tree<00:37:02.460> I<00:37:02.760> think<00:37:02.880> actually<00:37:03.000> there<00:37:03.420> is<00:37:03.599> uh<00:37:04.079> there 00:37:04.550 --> 00:37:04.560 align:start position:0% tree I think actually there is uh there 00:37:04.560 --> 00:37:06.589 align:start position:0% tree I think actually there is uh there is<00:37:04.680> an<00:37:04.800> issue<00:37:05.040> here<00:37:05.280> so<00:37:05.760> I'll<00:37:06.000> just<00:37:06.240> skip<00:37:06.420> this 00:37:06.589 --> 00:37:06.599 align:start position:0% is an issue here so I'll just skip this 00:37:06.599 --> 00:37:09.230 align:start position:0% is an issue here so I'll just skip this part<00:37:06.839> after<00:37:07.320> in<00:37:07.680> compression<00:37:08.099> we<00:37:08.760> are<00:37:09.000> very 00:37:09.230 --> 00:37:09.240 align:start position:0% part after in compression we are very 00:37:09.240 --> 00:37:12.050 align:start position:0% part after in compression we are very very<00:37:09.359> sad<00:37:09.780> because<00:37:10.260> well<00:37:11.099> we<00:37:11.460> need<00:37:11.579> to<00:37:11.700> prove 00:37:12.050 --> 00:37:12.060 align:start position:0% very sad because well we need to prove 00:37:12.060 --> 00:37:14.870 align:start position:0% very sad because well we need to prove actually<00:37:12.300> significant<00:37:13.260> computation<00:37:13.800> so<00:37:14.640> the 00:37:14.870 --> 00:37:14.880 align:start position:0% actually significant computation so the 00:37:14.880 --> 00:37:17.390 align:start position:0% actually significant computation so the proving<00:37:15.180> time<00:37:15.420> is<00:37:15.599> significant<00:37:16.079> okay<00:37:16.920> now<00:37:17.160> in 00:37:17.390 --> 00:37:17.400 align:start position:0% proving time is significant okay now in 00:37:17.400 --> 00:37:19.190 align:start position:0% proving time is significant okay now in terms<00:37:17.579> of<00:37:17.640> gas<00:37:17.880> cause<00:37:18.119> the<00:37:18.300> third<00:37:18.480> approach<00:37:18.900> is 00:37:19.190 --> 00:37:19.200 align:start position:0% terms of gas cause the third approach is 00:37:19.200 --> 00:37:20.870 align:start position:0% terms of gas cause the third approach is horrible<00:37:19.560> because<00:37:19.859> it<00:37:20.099> just<00:37:20.280> costs<00:37:20.640> a<00:37:20.760> lot 00:37:20.870 --> 00:37:20.880 align:start position:0% horrible because it just costs a lot 00:37:20.880 --> 00:37:23.030 align:start position:0% horrible because it just costs a lot because<00:37:21.540> we<00:37:21.780> do<00:37:21.960> the<00:37:22.079> entire<00:37:22.440> computation 00:37:23.030 --> 00:37:23.040 align:start position:0% because we do the entire computation 00:37:23.040 --> 00:37:26.150 align:start position:0% because we do the entire computation entry<00:37:24.000> compression<00:37:24.420> well<00:37:24.660> we're<00:37:25.440> a<00:37:25.740> bit<00:37:25.859> happy 00:37:26.150 --> 00:37:26.160 align:start position:0% entry compression well we're a bit happy 00:37:26.160 --> 00:37:28.250 align:start position:0% entry compression well we're a bit happy because<00:37:26.460> we<00:37:26.700> just<00:37:26.880> do<00:37:27.060> a<00:37:27.240> bit<00:37:27.420> of<00:37:27.599> computation 00:37:28.250 --> 00:37:28.260 align:start position:0% because we just do a bit of computation 00:37:28.260 --> 00:37:31.010 align:start position:0% because we just do a bit of computation but<00:37:28.800> still<00:37:29.280> it's<00:37:29.880> a<00:37:30.000> lot<00:37:30.119> of<00:37:30.180> cool<00:37:30.300> data<00:37:30.720> a<00:37:30.839> lot 00:37:31.010 --> 00:37:31.020 align:start position:0% but still it's a lot of cool data a lot 00:37:31.020 --> 00:37:33.170 align:start position:0% but still it's a lot of cool data a lot of<00:37:31.140> computation<00:37:31.560> but<00:37:31.920> lost<00:37:32.220> at<00:37:32.640> least<00:37:32.700> not<00:37:32.880> so 00:37:33.170 --> 00:37:33.180 align:start position:0% of computation but lost at least not so 00:37:33.180 --> 00:37:34.190 align:start position:0% of computation but lost at least not so much<00:37:33.359> storage 00:37:34.190 --> 00:37:34.200 align:start position:0% much storage 00:37:34.200 --> 00:37:37.550 align:start position:0% much storage storage<00:37:34.800> cost<00:37:35.160> oh<00:37:36.000> sorry<00:37:36.300> gas<00:37:36.720> cost<00:37:36.960> in<00:37:37.380> the 00:37:37.550 --> 00:37:37.560 align:start position:0% storage cost oh sorry gas cost in the 00:37:37.560 --> 00:37:38.990 align:start position:0% storage cost oh sorry gas cost in the second<00:37:37.740> approach<00:37:38.160> while<00:37:38.339> we<00:37:38.579> just<00:37:38.760> verify 00:37:38.990 --> 00:37:39.000 align:start position:0% second approach while we just verify 00:37:39.000 --> 00:37:41.150 align:start position:0% second approach while we just verify approved<00:37:39.480> so<00:37:39.599> it's<00:37:39.720> cool 00:37:41.150 --> 00:37:41.160 align:start position:0% approved so it's cool 00:37:41.160 --> 00:37:43.370 align:start position:0% approved so it's cool um<00:37:41.220> okay<00:37:41.579> storage<00:37:42.240> cost<00:37:42.660> for<00:37:43.079> the<00:37:43.260> first 00:37:43.370 --> 00:37:43.380 align:start position:0% um okay storage cost for the first 00:37:43.380 --> 00:37:46.310 align:start position:0% um okay storage cost for the first approach<00:37:43.740> well<00:37:44.099> seven<00:37:44.760> gigabytes<00:37:45.300> of<00:37:45.420> data<00:37:45.780> it 00:37:46.310 --> 00:37:46.320 align:start position:0% approach well seven gigabytes of data it 00:37:46.320 --> 00:37:48.650 align:start position:0% approach well seven gigabytes of data it is<00:37:46.440> horrible<00:37:46.859> so<00:37:47.220> we<00:37:47.339> are<00:37:47.460> very<00:37:47.579> sad 00:37:48.650 --> 00:37:48.660 align:start position:0% is horrible so we are very sad 00:37:48.660 --> 00:37:50.510 align:start position:0% is horrible so we are very sad unchain<00:37:49.260> compression 00:37:50.510 --> 00:37:50.520 align:start position:0% unchain compression 00:37:50.520 --> 00:37:53.210 align:start position:0% unchain compression uh<00:37:51.119> sorry<00:37:51.359> storage<00:37:52.260> cost<00:37:52.619> for<00:37:52.800> unchain 00:37:53.210 --> 00:37:53.220 align:start position:0% uh sorry storage cost for unchain 00:37:53.220 --> 00:37:55.310 align:start position:0% uh sorry storage cost for unchain compression<00:37:53.640> we<00:37:54.060> just 00:37:55.310 --> 00:37:55.320 align:start position:0% compression we just 00:37:55.320 --> 00:37:57.230 align:start position:0% compression we just the<00:37:55.500> root<00:37:56.040> of<00:37:56.099> the<00:37:56.220> miracle<00:37:56.520> tree<00:37:56.700> so<00:37:56.880> we<00:37:57.060> are 00:37:57.230 --> 00:37:57.240 align:start position:0% the root of the miracle tree so we are 00:37:57.240 --> 00:38:00.650 align:start position:0% the root of the miracle tree so we are happy<00:37:57.560> and<00:37:58.560> in<00:37:58.920> the<00:37:59.160> second<00:37:59.760> case<00:38:00.060> we're<00:38:00.359> even 00:38:00.650 --> 00:38:00.660 align:start position:0% happy and in the second case we're even 00:38:00.660 --> 00:38:02.569 align:start position:0% happy and in the second case we're even more<00:38:00.839> happy<00:38:01.079> because<00:38:01.380> we<00:38:01.740> again<00:38:02.040> we<00:38:02.400> just 00:38:02.569 --> 00:38:02.579 align:start position:0% more happy because we again we just 00:38:02.579 --> 00:38:04.370 align:start position:0% more happy because we again we just essentially<00:38:03.180> keep<00:38:03.420> updating<00:38:03.720> the<00:38:03.900> tree<00:38:04.140> and 00:38:04.370 --> 00:38:04.380 align:start position:0% essentially keep updating the tree and 00:38:04.380 --> 00:38:06.470 align:start position:0% essentially keep updating the tree and we<00:38:04.740> don't<00:38:04.859> even<00:38:04.980> need<00:38:05.280> to<00:38:05.400> post<00:38:05.579> a<00:38:05.820> lot<00:38:05.940> post<00:38:06.240> a 00:38:06.470 --> 00:38:06.480 align:start position:0% we don't even need to post a lot post a 00:38:06.480 --> 00:38:07.849 align:start position:0% we don't even need to post a lot post a lot<00:38:06.540> of<00:38:06.660> cool<00:38:06.780> data<00:38:07.140> because<00:38:07.260> the<00:38:07.440> call<00:38:07.560> data 00:38:07.849 --> 00:38:07.859 align:start position:0% lot of cool data because the call data 00:38:07.859 --> 00:38:10.370 align:start position:0% lot of cool data because the call data we<00:38:07.980> passed<00:38:08.400> is<00:38:08.820> literally<00:38:09.119> just<00:38:09.300> the<00:38:09.540> proof<00:38:09.839> so 00:38:10.370 --> 00:38:10.380 align:start position:0% we passed is literally just the proof so 00:38:10.380 --> 00:38:13.010 align:start position:0% we passed is literally just the proof so we're<00:38:10.619> very<00:38:11.040> very<00:38:11.220> happy<00:38:12.000> but<00:38:12.480> again<00:38:12.660> I<00:38:12.960> don't 00:38:13.010 --> 00:38:13.020 align:start position:0% we're very very happy but again I don't 00:38:13.020 --> 00:38:15.050 align:start position:0% we're very very happy but again I don't want<00:38:13.200> to<00:38:13.260> say<00:38:13.440> that<00:38:13.680> all<00:38:13.980> of<00:38:14.160> the<00:38:14.520> one<00:38:14.820> of<00:38:14.880> these 00:38:15.050 --> 00:38:15.060 align:start position:0% want to say that all of the one of these 00:38:15.060 --> 00:38:17.089 align:start position:0% want to say that all of the one of these approaches<00:38:15.359> is<00:38:15.540> the<00:38:15.720> best<00:38:15.900> one<00:38:16.079> because<00:38:16.680> as 00:38:17.089 --> 00:38:17.099 align:start position:0% approaches is the best one because as 00:38:17.099 --> 00:38:19.130 align:start position:0% approaches is the best one because as you<00:38:17.280> see<00:38:17.400> there<00:38:17.820> are<00:38:18.000> trade-offs 00:38:19.130 --> 00:38:19.140 align:start position:0% you see there are trade-offs 00:38:19.140 --> 00:38:21.349 align:start position:0% you see there are trade-offs and 00:38:21.349 --> 00:38:21.359 align:start position:0% and 00:38:21.359 --> 00:38:24.109 align:start position:0% and yeah<00:38:21.599> so<00:38:22.560> this<00:38:22.859> part<00:38:23.040> is<00:38:23.460> actually<00:38:23.700> pretty 00:38:24.109 --> 00:38:24.119 align:start position:0% yeah so this part is actually pretty 00:38:24.119 --> 00:38:26.329 align:start position:0% yeah so this part is actually pretty easy<00:38:24.420> so<00:38:24.960> as<00:38:25.140> you<00:38:25.320> know<00:38:25.500> as<00:38:25.740> you<00:38:25.859> may<00:38:25.980> notice 00:38:26.329 --> 00:38:26.339 align:start position:0% easy so as you know as you may notice 00:38:26.339 --> 00:38:28.490 align:start position:0% easy so as you know as you may notice here<00:38:27.300> I<00:38:27.480> was<00:38:27.599> explaining<00:38:27.900> like<00:38:28.079> the<00:38:28.320> second 00:38:28.490 --> 00:38:28.500 align:start position:0% here I was explaining like the second 00:38:28.500 --> 00:38:30.410 align:start position:0% here I was explaining like the second step<00:38:28.800> when<00:38:29.280> it<00:38:29.579> comes<00:38:29.820> to<00:38:29.940> dealing<00:38:30.300> with 00:38:30.410 --> 00:38:30.420 align:start position:0% step when it comes to dealing with 00:38:30.420 --> 00:38:33.290 align:start position:0% step when it comes to dealing with storage<00:38:30.660> Crews<00:38:31.140> and<00:38:31.740> now<00:38:31.920> there<00:38:32.280> is<00:38:32.460> the<00:38:33.119> the 00:38:33.290 --> 00:38:33.300 align:start position:0% storage Crews and now there is the the 00:38:33.300 --> 00:38:34.790 align:start position:0% storage Crews and now there is the the last<00:38:33.480> part<00:38:33.660> which<00:38:33.839> is<00:38:33.960> essentially<00:38:34.260> verifying 00:38:34.790 --> 00:38:34.800 align:start position:0% last part which is essentially verifying 00:38:34.800 --> 00:38:37.609 align:start position:0% last part which is essentially verifying the<00:38:34.920> proof<00:38:35.160> itself<00:38:35.599> so<00:38:36.599> approach<00:38:37.200> number<00:38:37.380> one 00:38:37.609 --> 00:38:37.619 align:start position:0% the proof itself so approach number one 00:38:37.619 --> 00:38:39.410 align:start position:0% the proof itself so approach number one is<00:38:37.980> verifying<00:38:38.460> the<00:38:38.520> proof<00:38:38.820> directly<00:38:39.119> on<00:38:39.300> the 00:38:39.410 --> 00:38:39.420 align:start position:0% is verifying the proof directly on the 00:38:39.420 --> 00:38:41.510 align:start position:0% is verifying the proof directly on the Chain<00:38:39.540> approach<00:38:40.260> number<00:38:40.440> two<00:38:40.740> let's<00:38:41.099> verify 00:38:41.510 --> 00:38:41.520 align:start position:0% Chain approach number two let's verify 00:38:41.520 --> 00:38:42.770 align:start position:0% Chain approach number two let's verify the<00:38:41.640> proof<00:38:41.940> inside<00:38:42.000> the<00:38:42.240> star<00:38:42.359> can<00:38:42.599> then 00:38:42.770 --> 00:38:42.780 align:start position:0% the proof inside the star can then 00:38:42.780 --> 00:38:44.690 align:start position:0% the proof inside the star can then verify<00:38:43.079> this<00:38:43.260> Arc<00:38:43.560> approach<00:38:44.280> number<00:38:44.400> three 00:38:44.690 --> 00:38:44.700 align:start position:0% verify this Arc approach number three 00:38:44.700 --> 00:38:47.210 align:start position:0% verify this Arc approach number three let's<00:38:45.180> verify<00:38:45.839> multiple<00:38:46.320> proofs<00:38:46.680> inside<00:38:46.980> the 00:38:47.210 --> 00:38:47.220 align:start position:0% let's verify multiple proofs inside the 00:38:47.220 --> 00:38:49.190 align:start position:0% let's verify multiple proofs inside the star<00:38:47.460> can<00:38:47.700> then<00:38:47.820> verify<00:38:48.180> the<00:38:48.300> snark<00:38:48.599> we<00:38:49.020> can 00:38:49.190 --> 00:38:49.200 align:start position:0% star can then verify the snark we can 00:38:49.200 --> 00:38:51.230 align:start position:0% star can then verify the snark we can aggregate<00:38:49.619> multiple<00:38:49.920> sharks<00:38:50.339> together<00:38:50.460> and 00:38:51.230 --> 00:38:51.240 align:start position:0% aggregate multiple sharks together and 00:38:51.240 --> 00:38:53.150 align:start position:0% aggregate multiple sharks together and so<00:38:51.420> on<00:38:51.540> but<00:38:51.780> obviously<00:38:52.200> there<00:38:52.859> are<00:38:52.980> some 00:38:53.150 --> 00:38:53.160 align:start position:0% so on but obviously there are some 00:38:53.160 --> 00:38:54.349 align:start position:0% so on but obviously there are some trade-offs<00:38:53.640> especially<00:38:53.880> when<00:38:54.060> it<00:38:54.180> comes<00:38:54.300> to 00:38:54.349 --> 00:38:54.359 align:start position:0% trade-offs especially when it comes to 00:38:54.359 --> 00:38:55.970 align:start position:0% trade-offs especially when it comes to proving<00:38:54.780> time 00:38:55.970 --> 00:38:55.980 align:start position:0% proving time 00:38:55.980 --> 00:38:58.550 align:start position:0% proving time um<00:38:56.040> and<00:38:56.700> yeah<00:38:56.820> so<00:38:57.119> now<00:38:57.300> why<00:38:58.200> the<00:38:58.440> first 00:38:58.550 --> 00:38:58.560 align:start position:0% um and yeah so now why the first 00:38:58.560 --> 00:39:01.310 align:start position:0% um and yeah so now why the first approach<00:38:58.920> is<00:38:59.280> feasible<00:38:59.820> on<00:39:00.119> on<00:39:00.420> ZK<00:39:00.839> rollups 00:39:01.310 --> 00:39:01.320 align:start position:0% approach is feasible on on ZK rollups 00:39:01.320 --> 00:39:02.810 align:start position:0% approach is feasible on on ZK rollups for<00:39:01.440> example<00:39:01.619> and<00:39:01.800> start<00:39:01.920> medical<00:39:02.160> data<00:39:02.700> is 00:39:02.810 --> 00:39:02.820 align:start position:0% for example and start medical data is 00:39:02.820 --> 00:39:04.910 align:start position:0% for example and start medical data is very<00:39:03.000> cheap<00:39:03.180> and<00:39:03.839> what<00:39:03.960> we<00:39:04.140> want<00:39:04.260> to<00:39:04.380> avoid<00:39:04.680> in 00:39:04.910 --> 00:39:04.920 align:start position:0% very cheap and what we want to avoid in 00:39:04.920 --> 00:39:07.430 align:start position:0% very cheap and what we want to avoid in this<00:39:05.220> specific<00:39:05.460> processes<00:39:06.119> called<00:39:06.540> Data<00:39:07.020> so 00:39:07.430 --> 00:39:07.440 align:start position:0% this specific processes called Data so 00:39:07.440 --> 00:39:09.230 align:start position:0% this specific processes called Data so this<00:39:07.619> approach<00:39:07.920> is<00:39:08.099> for<00:39:08.339> example<00:39:08.520> visible<00:39:09.000> on 00:39:09.230 --> 00:39:09.240 align:start position:0% this approach is for example visible on 00:39:09.240 --> 00:39:11.450 align:start position:0% this approach is for example visible on starknet<00:39:09.780> but<00:39:10.320> for<00:39:10.680> example<00:39:10.859> if<00:39:11.099> you<00:39:11.220> want<00:39:11.339> to 00:39:11.450 --> 00:39:11.460 align:start position:0% starknet but for example if you want to 00:39:11.460 --> 00:39:13.190 align:start position:0% starknet but for example if you want to verify<00:39:11.820> like<00:39:12.000> a<00:39:12.180> proof<00:39:12.420> an<00:39:12.540> optimism<00:39:12.900> or<00:39:13.079> a 00:39:13.190 --> 00:39:13.200 align:start position:0% verify like a proof an optimism or a 00:39:13.200 --> 00:39:14.930 align:start position:0% verify like a proof an optimism or a colleague<00:39:13.500> is<00:39:13.619> very<00:39:13.800> expensive<00:39:14.220> you<00:39:14.700> want<00:39:14.820> to 00:39:14.930 --> 00:39:14.940 align:start position:0% colleague is very expensive you want to 00:39:14.940 --> 00:39:17.030 align:start position:0% colleague is very expensive you want to reduce<00:39:15.180> it<00:39:15.480> as<00:39:15.720> much<00:39:15.839> as<00:39:16.020> possible<00:39:16.320> so<00:39:16.859> for 00:39:17.030 --> 00:39:17.040 align:start position:0% reduce it as much as possible so for 00:39:17.040 --> 00:39:18.470 align:start position:0% reduce it as much as possible so for that<00:39:17.160> reason<00:39:17.339> you<00:39:17.640> might<00:39:17.940> want<00:39:18.119> to<00:39:18.240> use<00:39:18.359> a 00:39:18.470 --> 00:39:18.480 align:start position:0% that reason you might want to use a 00:39:18.480 --> 00:39:21.890 align:start position:0% that reason you might want to use a snark<00:39:18.780> and<00:39:19.440> finally<00:39:19.680> if<00:39:20.040> you<00:39:20.160> have<00:39:20.280> like<00:39:20.520> many 00:39:21.890 --> 00:39:21.900 align:start position:0% snark and finally if you have like many 00:39:21.900 --> 00:39:24.349 align:start position:0% snark and finally if you have like many slots<00:39:22.680> that<00:39:22.859> you<00:39:22.980> want<00:39:23.099> to<00:39:23.220> prove<00:39:23.520> why<00:39:24.119> can't 00:39:24.349 --> 00:39:24.359 align:start position:0% slots that you want to prove why can't 00:39:24.359 --> 00:39:26.150 align:start position:0% slots that you want to prove why can't you<00:39:24.599> just<00:39:24.720> verify<00:39:25.140> them<00:39:25.320> inside<00:39:25.560> one<00:39:25.859> snark 00:39:26.150 --> 00:39:26.160 align:start position:0% you just verify them inside one snark 00:39:26.160 --> 00:39:29.150 align:start position:0% you just verify them inside one snark you're<00:39:26.579> gonna<00:39:26.700> pay<00:39:26.940> improver<00:39:27.300> time<00:39:27.599> but<00:39:28.380> you 00:39:29.150 --> 00:39:29.160 align:start position:0% you're gonna pay improver time but you 00:39:29.160 --> 00:39:31.190 align:start position:0% you're gonna pay improver time but you just<00:39:29.400> present<00:39:29.640> one<00:39:29.820> proof<00:39:30.240> at<00:39:30.359> the<00:39:30.480> end<00:39:30.599> so 00:39:31.190 --> 00:39:31.200 align:start position:0% just present one proof at the end so 00:39:31.200 --> 00:39:35.089 align:start position:0% just present one proof at the end so this<00:39:31.560> approach<00:39:31.920> is<00:39:32.700> cheaper<00:39:33.480> is<00:39:34.200> the<00:39:34.500> cheapest 00:39:35.089 --> 00:39:35.099 align:start position:0% this approach is cheaper is the cheapest 00:39:35.099 --> 00:39:36.890 align:start position:0% this approach is cheaper is the cheapest one<00:39:35.220> but<00:39:35.460> only<00:39:35.640> if<00:39:35.880> you<00:39:36.000> have<00:39:36.240> multiple 00:39:36.890 --> 00:39:36.900 align:start position:0% one but only if you have multiple 00:39:36.900 --> 00:39:40.370 align:start position:0% one but only if you have multiple actions<00:39:37.440> to<00:39:37.619> to<00:39:37.859> take<00:39:38.099> so 00:39:40.370 --> 00:39:40.380 align:start position:0% actions to to take so 00:39:40.380 --> 00:39:43.010 align:start position:0% actions to to take so there<00:39:40.800> are<00:39:40.920> trade-offs 00:39:43.010 --> 00:39:43.020 align:start position:0% there are trade-offs 00:39:43.020 --> 00:39:46.450 align:start position:0% there are trade-offs so<00:39:43.740> let's<00:39:44.160> identify<00:39:44.760> them 00:39:46.450 --> 00:39:46.460 align:start position:0% so let's identify them 00:39:46.460 --> 00:39:49.010 align:start position:0% so let's identify them categories<00:39:47.460> approval<00:39:48.060> overhead<00:39:48.420> latency 00:39:49.010 --> 00:39:49.020 align:start position:0% categories approval overhead latency 00:39:49.020 --> 00:39:52.790 align:start position:0% categories approval overhead latency verification<00:39:49.740> cost<00:39:50.420> so<00:39:51.560> verifying<00:39:52.560> the<00:39:52.619> proof 00:39:52.790 --> 00:39:52.800 align:start position:0% verification cost so verifying the proof 00:39:52.800 --> 00:39:54.770 align:start position:0% verification cost so verifying the proof directly<00:39:53.160> prove<00:39:53.820> our<00:39:53.940> overhead<00:39:54.300> doesn't 00:39:54.770 --> 00:39:54.780 align:start position:0% directly prove our overhead doesn't 00:39:54.780 --> 00:39:57.170 align:start position:0% directly prove our overhead doesn't exist<00:39:55.140> latency<00:39:55.859> doesn't<00:39:56.460> exist<00:39:56.820> because<00:39:57.000> we 00:39:57.170 --> 00:39:57.180 align:start position:0% exist latency doesn't exist because we 00:39:57.180 --> 00:39:58.089 align:start position:0% exist latency doesn't exist because we don't<00:39:57.359> need<00:39:57.480> to<00:39:57.599> prove<00:39:57.839> anything 00:39:58.089 --> 00:39:58.099 align:start position:0% don't need to prove anything 00:39:58.099 --> 00:40:00.050 align:start position:0% don't need to prove anything verification<00:39:59.099> costs<00:39:59.579> well<00:39:59.700> it<00:39:59.940> is 00:40:00.050 --> 00:40:00.060 align:start position:0% verification costs well it is 00:40:00.060 --> 00:40:01.130 align:start position:0% verification costs well it is significant 00:40:01.130 --> 00:40:01.140 align:start position:0% significant 00:40:01.140 --> 00:40:03.470 align:start position:0% significant because<00:40:01.680> we<00:40:02.220> need<00:40:02.460> to<00:40:02.520> possible<00:40:02.820> data<00:40:03.119> we<00:40:03.420> need 00:40:03.470 --> 00:40:03.480 align:start position:0% because we need to possible data we need 00:40:03.480 --> 00:40:05.089 align:start position:0% because we need to possible data we need and<00:40:03.839> we<00:40:04.020> need<00:40:04.079> to<00:40:04.140> do<00:40:04.260> the<00:40:04.380> actual<00:40:04.619> computation 00:40:05.089 --> 00:40:05.099 align:start position:0% and we need to do the actual computation 00:40:05.099 --> 00:40:06.710 align:start position:0% and we need to do the actual computation so<00:40:05.400> like<00:40:05.520> going<00:40:05.760> through<00:40:06.000> the<00:40:06.119> entire<00:40:06.420> path 00:40:06.710 --> 00:40:06.720 align:start position:0% so like going through the entire path 00:40:06.720 --> 00:40:08.870 align:start position:0% so like going through the entire path and<00:40:07.200> each<00:40:07.440> step<00:40:07.619> in<00:40:07.859> the<00:40:07.980> path<00:40:08.099> is<00:40:08.280> one<00:40:08.460> hashing 00:40:08.870 --> 00:40:08.880 align:start position:0% and each step in the path is one hashing 00:40:08.880 --> 00:40:11.630 align:start position:0% and each step in the path is one hashing function<00:40:09.240> oh<00:40:10.140> and<00:40:10.440> also 00:40:11.630 --> 00:40:11.640 align:start position:0% function oh and also 00:40:11.640 --> 00:40:13.849 align:start position:0% function oh and also let<00:40:12.119> me<00:40:12.240> get<00:40:12.359> back<00:40:12.540> to<00:40:12.660> the<00:40:12.780> previous<00:40:12.960> slide<00:40:13.320> I 00:40:13.849 --> 00:40:13.859 align:start position:0% let me get back to the previous slide I 00:40:13.859 --> 00:40:16.550 align:start position:0% let me get back to the previous slide I forgot<00:40:14.160> this<00:40:14.400> is<00:40:14.520> very<00:40:14.760> important<00:40:15.119> why 00:40:16.550 --> 00:40:16.560 align:start position:0% forgot this is very important why 00:40:16.560 --> 00:40:18.770 align:start position:0% forgot this is very important why wrapping<00:40:17.280> inside<00:40:17.520> this<00:40:17.880> wrapping<00:40:18.660> inside 00:40:18.770 --> 00:40:18.780 align:start position:0% wrapping inside this wrapping inside 00:40:18.780 --> 00:40:20.750 align:start position:0% wrapping inside this wrapping inside this<00:40:19.079> rank<00:40:19.320> is<00:40:19.500> pretty<00:40:19.680> important<00:40:20.040> if<00:40:20.700> you're 00:40:20.750 --> 00:40:20.760 align:start position:0% this rank is pretty important if you're 00:40:20.760 --> 00:40:23.510 align:start position:0% this rank is pretty important if you're like<00:40:21.000> dealing<00:40:21.359> with<00:40:21.540> a<00:40:21.720> storage<00:40:22.160> layout<00:40:23.160> that 00:40:23.510 --> 00:40:23.520 align:start position:0% like dealing with a storage layout that 00:40:23.520 --> 00:40:25.430 align:start position:0% like dealing with a storage layout that is<00:40:23.700> using<00:40:24.180> a<00:40:24.300> specific<00:40:24.599> hashing<00:40:25.079> function 00:40:25.430 --> 00:40:25.440 align:start position:0% is using a specific hashing function 00:40:25.440 --> 00:40:28.849 align:start position:0% is using a specific hashing function let's<00:40:26.040> say<00:40:26.220> for<00:40:26.520> example<00:40:26.900> Peterson<00:40:27.900> Peterson 00:40:28.849 --> 00:40:28.859 align:start position:0% let's say for example Peterson Peterson 00:40:28.859 --> 00:40:31.550 align:start position:0% let's say for example Peterson Peterson is<00:40:29.160> not<00:40:29.339> available<00:40:29.520> like<00:40:30.000> on<00:40:30.240> on<00:40:30.420> the<00:40:30.900> EVN<00:40:31.260> like 00:40:31.550 --> 00:40:31.560 align:start position:0% is not available like on on the EVN like 00:40:31.560 --> 00:40:33.230 align:start position:0% is not available like on on the EVN like you<00:40:31.740> just<00:40:32.160> need<00:40:32.339> to<00:40:32.460> implement<00:40:32.700> it's<00:40:32.940> not<00:40:33.119> the 00:40:33.230 --> 00:40:33.240 align:start position:0% you just need to implement it's not the 00:40:33.240 --> 00:40:35.450 align:start position:0% you just need to implement it's not the pre-composite<00:40:33.780> it's<00:40:34.140> gonna<00:40:34.320> be<00:40:34.500> costly<00:40:34.859> but 00:40:35.450 --> 00:40:35.460 align:start position:0% pre-composite it's gonna be costly but 00:40:35.460 --> 00:40:36.829 align:start position:0% pre-composite it's gonna be costly but if<00:40:35.700> you<00:40:35.880> do<00:40:36.000> inside<00:40:36.180> the<00:40:36.420> scenario<00:40:36.780> and 00:40:36.829 --> 00:40:36.839 align:start position:0% if you do inside the scenario and 00:40:36.839 --> 00:40:38.810 align:start position:0% if you do inside the scenario and Peterson<00:40:37.200> is<00:40:37.500> pretty<00:40:37.619> smart<00:40:37.920> friendly<00:40:38.339> it's 00:40:38.810 --> 00:40:38.820 align:start position:0% Peterson is pretty smart friendly it's 00:40:38.820 --> 00:40:41.150 align:start position:0% Peterson is pretty smart friendly it's not<00:40:39.060> friendly<00:40:39.420> then<00:40:39.780> well<00:40:40.260> it<00:40:40.500> just<00:40:40.740> verifies 00:40:41.150 --> 00:40:41.160 align:start position:0% not friendly then well it just verifies 00:40:41.160 --> 00:40:42.650 align:start position:0% not friendly then well it just verifies an<00:40:41.339> arc<00:40:41.579> on<00:40:41.700> the<00:40:41.760> one<00:40:41.880> and<00:40:42.060> you<00:40:42.119> abstract<00:40:42.420> it<00:40:42.540> so 00:40:42.650 --> 00:40:42.660 align:start position:0% an arc on the one and you abstract it so 00:40:42.660 --> 00:40:45.050 align:start position:0% an arc on the one and you abstract it so it's<00:40:42.780> going<00:40:42.960> to<00:40:43.079> be<00:40:43.260> way<00:40:43.740> way<00:40:43.800> way<00:40:43.920> cheaper<00:40:44.640> but 00:40:45.050 --> 00:40:45.060 align:start position:0% it's going to be way way way cheaper but 00:40:45.060 --> 00:40:47.450 align:start position:0% it's going to be way way way cheaper but again<00:40:45.240> there<00:40:45.960> are<00:40:46.140> trade-offs<00:40:46.680> let<00:40:47.160> me<00:40:47.280> get 00:40:47.450 --> 00:40:47.460 align:start position:0% again there are trade-offs let me get 00:40:47.460 --> 00:40:49.609 align:start position:0% again there are trade-offs let me get back<00:40:47.579> to<00:40:47.760> this<00:40:47.940> so<00:40:48.720> I<00:40:48.960> went<00:40:49.020> through<00:40:49.260> this<00:40:49.440> the 00:40:49.609 --> 00:40:49.619 align:start position:0% back to this so I went through this the 00:40:49.619 --> 00:40:51.530 align:start position:0% back to this so I went through this the normal<00:40:49.680> competition<00:40:50.099> 3<00:40:50.460> star<00:40:50.760> fight<00:40:51.180> proof 00:40:51.530 --> 00:40:51.540 align:start position:0% normal competition 3 star fight proof 00:40:51.540 --> 00:40:55.790 align:start position:0% normal competition 3 star fight proof through<00:40:51.900> overhead<00:40:52.500> it<00:40:53.339> exists<00:40:53.900> so<00:40:54.900> we<00:40:55.260> are<00:40:55.440> not 00:40:55.790 --> 00:40:55.800 align:start position:0% through overhead it exists so we are not 00:40:55.800 --> 00:40:59.030 align:start position:0% through overhead it exists so we are not super<00:40:56.460> happy<00:40:56.900> latency<00:40:57.900> we<00:40:58.619> are<00:40:58.800> also<00:40:58.980> not 00:40:59.030 --> 00:40:59.040 align:start position:0% super happy latency we are also not 00:40:59.040 --> 00:41:00.530 align:start position:0% super happy latency we are also not happy<00:40:59.280> because<00:40:59.520> we<00:40:59.760> actually<00:40:59.940> need<00:41:00.180> to<00:41:00.300> spend 00:41:00.530 --> 00:41:00.540 align:start position:0% happy because we actually need to spend 00:41:00.540 --> 00:41:02.530 align:start position:0% happy because we actually need to spend time<00:41:00.780> on<00:41:01.020> improving<00:41:01.500> this<00:41:01.680> this<00:41:01.920> thing 00:41:02.530 --> 00:41:02.540 align:start position:0% time on improving this this thing 00:41:02.540 --> 00:41:05.150 align:start position:0% time on improving this this thing verification<00:41:03.540> costs<00:41:04.079> we<00:41:04.560> are<00:41:04.680> happy<00:41:04.859> because 00:41:05.150 --> 00:41:05.160 align:start position:0% verification costs we are happy because 00:41:05.160 --> 00:41:07.310 align:start position:0% verification costs we are happy because well<00:41:05.579> we<00:41:05.940> we<00:41:06.240> just<00:41:06.420> verify<00:41:06.720> your<00:41:06.900> proof<00:41:07.140> so 00:41:07.310 --> 00:41:07.320 align:start position:0% well we we just verify your proof so 00:41:07.320 --> 00:41:09.710 align:start position:0% well we we just verify your proof so it's<00:41:07.440> fine<00:41:07.619> and<00:41:08.480> snarkifying<00:41:09.480> multiple 00:41:09.710 --> 00:41:09.720 align:start position:0% it's fine and snarkifying multiple 00:41:09.720 --> 00:41:11.750 align:start position:0% it's fine and snarkifying multiple proofs<00:41:10.200> the<00:41:10.560> prover<00:41:10.859> overhead<00:41:11.339> is<00:41:11.579> still 00:41:11.750 --> 00:41:11.760 align:start position:0% proofs the prover overhead is still 00:41:11.760 --> 00:41:13.970 align:start position:0% proofs the prover overhead is still there<00:41:12.000> latency<00:41:12.720> is<00:41:13.140> still<00:41:13.380> there<00:41:13.500> it's<00:41:13.740> even 00:41:13.970 --> 00:41:13.980 align:start position:0% there latency is still there it's even 00:41:13.980 --> 00:41:16.010 align:start position:0% there latency is still there it's even bigger<00:41:14.339> because<00:41:14.520> it<00:41:14.760> takes<00:41:14.940> a<00:41:15.119> bit<00:41:15.240> longer<00:41:15.599> in 00:41:16.010 --> 00:41:16.020 align:start position:0% bigger because it takes a bit longer in 00:41:16.020 --> 00:41:18.050 align:start position:0% bigger because it takes a bit longer in improving<00:41:16.440> time<00:41:16.980> and<00:41:17.400> verification<00:41:17.820> because 00:41:18.050 --> 00:41:18.060 align:start position:0% improving time and verification because 00:41:18.060 --> 00:41:19.550 align:start position:0% improving time and verification because we<00:41:18.359> are<00:41:18.480> super<00:41:18.660> happy<00:41:18.839> because<00:41:19.140> essentially 00:41:19.550 --> 00:41:19.560 align:start position:0% we are super happy because essentially 00:41:19.560 --> 00:41:22.130 align:start position:0% we are super happy because essentially we<00:41:19.859> can<00:41:20.060> mutualize<00:41:21.060> the<00:41:21.240> cost<00:41:21.420> of<00:41:21.599> verifying 00:41:22.130 --> 00:41:22.140 align:start position:0% we can mutualize the cost of verifying 00:41:22.140 --> 00:41:24.230 align:start position:0% we can mutualize the cost of verifying multiple<00:41:22.500> proofs 00:41:24.230 --> 00:41:24.240 align:start position:0% multiple proofs 00:41:24.240 --> 00:41:29.870 align:start position:0% multiple proofs by<00:41:24.599> just<00:41:24.780> verifying<00:41:25.320> one<00:41:25.619> single<00:41:26.040> Stark<00:41:26.460> proof 00:41:29.870 --> 00:41:29.880 align:start position:0% 00:41:29.880 --> 00:41:32.950 align:start position:0% okay<00:41:30.619> went<00:41:31.619> through<00:41:31.859> quite<00:41:32.339> a<00:41:32.460> lot<00:41:32.579> of<00:41:32.640> things 00:41:32.950 --> 00:41:32.960 align:start position:0% okay went through quite a lot of things 00:41:32.960 --> 00:41:36.230 align:start position:0% okay went through quite a lot of things let's<00:41:33.960> put<00:41:34.440> this<00:41:34.619> all<00:41:34.740> together 00:41:36.230 --> 00:41:36.240 align:start position:0% let's put this all together 00:41:36.240 --> 00:41:38.030 align:start position:0% let's put this all together so<00:41:36.540> let's<00:41:36.660> imagine<00:41:36.900> we<00:41:37.260> have<00:41:37.380> three<00:41:37.560> chains 00:41:38.030 --> 00:41:38.040 align:start position:0% so let's imagine we have three chains 00:41:38.040 --> 00:41:39.770 align:start position:0% so let's imagine we have three chains and<00:41:38.460> we<00:41:38.700> want<00:41:38.820> to<00:41:38.880> have<00:41:39.060> interoperability 00:41:39.770 --> 00:41:39.780 align:start position:0% and we want to have interoperability 00:41:39.780 --> 00:41:42.530 align:start position:0% and we want to have interoperability interoperability<00:41:40.740> between<00:41:41.160> them<00:41:41.460> so<00:41:42.180> we<00:41:42.359> have 00:41:42.530 --> 00:41:42.540 align:start position:0% interoperability between them so we have 00:41:42.540 --> 00:41:45.290 align:start position:0% interoperability between them so we have chain<00:41:42.720> Z<00:41:42.960> chain<00:41:43.260> X<00:41:43.440> and<00:41:43.619> chain<00:41:43.800> y 00:41:45.290 --> 00:41:45.300 align:start position:0% chain Z chain X and chain y 00:41:45.300 --> 00:41:47.870 align:start position:0% chain Z chain X and chain y so<00:41:45.540> it<00:41:46.020> all<00:41:46.140> starts<00:41:46.500> with<00:41:46.619> a<00:41:46.859> message<00:41:46.980> AKA 00:41:47.870 --> 00:41:47.880 align:start position:0% so it all starts with a message AKA 00:41:47.880 --> 00:41:50.030 align:start position:0% so it all starts with a message AKA commitment<00:41:48.480> we<00:41:48.960> send<00:41:49.140> a<00:41:49.320> message<00:41:49.440> in<00:41:49.740> order<00:41:49.859> to 00:41:50.030 --> 00:41:50.040 align:start position:0% commitment we send a message in order to 00:41:50.040 --> 00:41:52.310 align:start position:0% commitment we send a message in order to get<00:41:50.400> the<00:41:50.579> commitment<00:41:50.940> so<00:41:51.359> let's<00:41:51.839> say<00:41:52.020> that<00:41:52.200> we 00:41:52.310 --> 00:41:52.320 align:start position:0% get the commitment so let's say that we 00:41:52.320 --> 00:41:55.329 align:start position:0% get the commitment so let's say that we send<00:41:52.500> a<00:41:52.680> message<00:41:52.800> from<00:41:53.220> chain<00:41:53.640> Z<00:41:53.940> to<00:41:54.660> chain<00:41:54.960> X 00:41:55.329 --> 00:41:55.339 align:start position:0% send a message from chain Z to chain X 00:41:55.339 --> 00:41:58.430 align:start position:0% send a message from chain Z to chain X because<00:41:56.339> on<00:41:56.700> chain<00:41:56.820> X<00:41:57.119> we<00:41:57.359> want<00:41:57.480> to<00:41:57.599> access<00:41:57.839> the 00:41:58.430 --> 00:41:58.440 align:start position:0% because on chain X we want to access the 00:41:58.440 --> 00:42:01.670 align:start position:0% because on chain X we want to access the the<00:41:58.859> state<00:41:59.099> of<00:41:59.400> changing<00:42:00.119> so<00:42:01.020> what<00:42:01.260> do<00:42:01.380> we<00:42:01.560> do 00:42:01.670 --> 00:42:01.680 align:start position:0% the state of changing so what do we do 00:42:01.680 --> 00:42:03.349 align:start position:0% the state of changing so what do we do once<00:42:02.040> we<00:42:02.099> have<00:42:02.220> the<00:42:02.339> commitment<00:42:02.640> we<00:42:03.000> literally 00:42:03.349 --> 00:42:03.359 align:start position:0% once we have the commitment we literally 00:42:03.359 --> 00:42:05.569 align:start position:0% once we have the commitment we literally recreate<00:42:03.960> all<00:42:04.140> the<00:42:04.260> headers 00:42:05.569 --> 00:42:05.579 align:start position:0% recreate all the headers 00:42:05.579 --> 00:42:08.510 align:start position:0% recreate all the headers using<00:42:06.359> one<00:42:06.540> of<00:42:06.660> the<00:42:06.720> three<00:42:06.839> approaches 00:42:08.510 --> 00:42:08.520 align:start position:0% using one of the three approaches 00:42:08.520 --> 00:42:10.670 align:start position:0% using one of the three approaches and<00:42:09.060> once<00:42:09.359> we<00:42:09.420> recreated<00:42:09.900> the<00:42:10.260> header<00:42:10.560> is 00:42:10.670 --> 00:42:10.680 align:start position:0% and once we recreated the header is 00:42:10.680 --> 00:42:12.290 align:start position:0% and once we recreated the header is still<00:42:10.800> the<00:42:10.920> point<00:42:11.099> for<00:42:11.700> which<00:42:11.880> I<00:42:12.060> want<00:42:12.180> to 00:42:12.290 --> 00:42:12.300 align:start position:0% still the point for which I want to 00:42:12.300 --> 00:42:14.510 align:start position:0% still the point for which I want to prove<00:42:12.660> the<00:42:12.780> storage<00:42:12.960> I<00:42:13.619> just<00:42:13.800> verify<00:42:14.160> a<00:42:14.280> proof 00:42:14.510 --> 00:42:14.520 align:start position:0% prove the storage I just verify a proof 00:42:14.520 --> 00:42:16.069 align:start position:0% prove the storage I just verify a proof and<00:42:14.640> again<00:42:14.760> for<00:42:14.940> verifying<00:42:15.420> approved<00:42:15.839> there 00:42:16.069 --> 00:42:16.079 align:start position:0% and again for verifying approved there 00:42:16.079 --> 00:42:17.569 align:start position:0% and again for verifying approved there are<00:42:16.200> multiple<00:42:16.500> approaches<00:42:16.980> but<00:42:17.220> now<00:42:17.339> let's 00:42:17.569 --> 00:42:17.579 align:start position:0% are multiple approaches but now let's 00:42:17.579 --> 00:42:20.030 align:start position:0% are multiple approaches but now let's say<00:42:17.820> that<00:42:17.940> on<00:42:18.119> chain<00:42:18.300> y<00:42:18.599> I<00:42:19.380> want<00:42:19.440> to<00:42:19.560> access<00:42:19.740> the 00:42:20.030 --> 00:42:20.040 align:start position:0% say that on chain y I want to access the 00:42:20.040 --> 00:42:22.430 align:start position:0% say that on chain y I want to access the state<00:42:20.160> of<00:42:20.339> change<00:42:20.520> Z<00:42:20.820> and<00:42:21.660> there<00:42:21.960> is<00:42:22.140> no<00:42:22.260> direct 00:42:22.430 --> 00:42:22.440 align:start position:0% state of change Z and there is no direct 00:42:22.440 --> 00:42:24.890 align:start position:0% state of change Z and there is no direct communication<00:42:23.099> between<00:42:23.460> chain<00:42:23.820> Y<00:42:24.480> and<00:42:24.720> chain 00:42:24.890 --> 00:42:24.900 align:start position:0% communication between chain Y and chain 00:42:24.900 --> 00:42:28.430 align:start position:0% communication between chain Y and chain Z<00:42:25.200> so<00:42:25.740> it<00:42:26.160> must<00:42:26.280> be<00:42:26.400> routed<00:42:26.760> through<00:42:26.940> trainx<00:42:27.599> by 00:42:28.430 --> 00:42:28.440 align:start position:0% Z so it must be routed through trainx by 00:42:28.440 --> 00:42:29.569 align:start position:0% Z so it must be routed through trainx by the<00:42:28.560> way<00:42:28.619> I'm 00:42:29.569 --> 00:42:29.579 align:start position:0% the way I'm 00:42:29.579 --> 00:42:31.970 align:start position:0% the way I'm like<00:42:30.119> talking<00:42:30.540> about<00:42:31.380> this<00:42:31.560> in<00:42:31.740> a<00:42:31.859> pretty 00:42:31.970 --> 00:42:31.980 align:start position:0% like talking about this in a pretty 00:42:31.980 --> 00:42:34.130 align:start position:0% like talking about this in a pretty abstract<00:42:32.280> Way<00:42:32.460> by<00:42:32.700> Chain<00:42:33.060> X<00:42:33.300> I<00:42:33.480> just<00:42:33.599> miniature 00:42:34.130 --> 00:42:34.140 align:start position:0% abstract Way by Chain X I just miniature 00:42:34.140 --> 00:42:36.109 align:start position:0% abstract Way by Chain X I just miniature emulator<00:42:34.260> one 00:42:36.109 --> 00:42:36.119 align:start position:0% emulator one 00:42:36.119 --> 00:42:38.390 align:start position:0% emulator one um<00:42:36.180> yeah<00:42:36.420> so<00:42:36.839> from<00:42:37.320> chain<00:42:37.560> X<00:42:37.800> I'm<00:42:38.099> just<00:42:38.280> gonna 00:42:38.390 --> 00:42:38.400 align:start position:0% um yeah so from chain X I'm just gonna 00:42:38.400 --> 00:42:40.069 align:start position:0% um yeah so from chain X I'm just gonna send<00:42:38.640> again<00:42:38.880> the<00:42:39.180> commitment<00:42:39.480> about<00:42:39.780> change 00:42:40.069 --> 00:42:40.079 align:start position:0% send again the commitment about change 00:42:40.079 --> 00:42:42.349 align:start position:0% send again the commitment about change the<00:42:40.440> as<00:42:40.680> a<00:42:40.920> message<00:42:41.040> and<00:42:41.820> then<00:42:42.000> simply 00:42:42.349 --> 00:42:42.359 align:start position:0% the as a message and then simply 00:42:42.359 --> 00:42:44.930 align:start position:0% the as a message and then simply recreate<00:42:42.900> all<00:42:43.140> these<00:42:43.440> all<00:42:43.859> these<00:42:44.099> headers<00:42:44.400> as 00:42:44.930 --> 00:42:44.940 align:start position:0% recreate all these all these headers as 00:42:44.940 --> 00:42:47.510 align:start position:0% recreate all these all these headers as you<00:42:45.119> may<00:42:45.300> not<00:42:45.599> notice<00:42:46.320> it's<00:42:46.800> pretty<00:42:47.040> redundant 00:42:47.510 --> 00:42:47.520 align:start position:0% you may not notice it's pretty redundant 00:42:47.520 --> 00:42:49.490 align:start position:0% you may not notice it's pretty redundant because<00:42:47.820> we<00:42:48.180> perform<00:42:48.480> the<00:42:48.839> same<00:42:49.020> computation 00:42:49.490 --> 00:42:49.500 align:start position:0% because we perform the same computation 00:42:49.500 --> 00:42:53.030 align:start position:0% because we perform the same computation on<00:42:50.099> two<00:42:50.400> different<00:42:50.640> chains<00:42:51.260> and<00:42:52.260> we<00:42:52.920> don't 00:42:53.030 --> 00:42:53.040 align:start position:0% on two different chains and we don't 00:42:53.040 --> 00:42:54.470 align:start position:0% on two different chains and we don't need<00:42:53.220> to<00:42:53.339> do<00:42:53.460> that<00:42:53.640> especially<00:42:54.060> if<00:42:54.240> you<00:42:54.359> use 00:42:54.470 --> 00:42:54.480 align:start position:0% need to do that especially if you use 00:42:54.480 --> 00:42:56.210 align:start position:0% need to do that especially if you use like<00:42:54.720> the<00:42:54.960> third<00:42:55.320> approach<00:42:55.800> which<00:42:55.980> is 00:42:56.210 --> 00:42:56.220 align:start position:0% like the third approach which is 00:42:56.220 --> 00:42:59.150 align:start position:0% like the third approach which is generating<00:42:56.820> the<00:42:57.060> proof<00:42:57.359> on<00:42:57.480> chain<00:42:57.980> but<00:42:58.980> now 00:42:59.150 --> 00:42:59.160 align:start position:0% generating the proof on chain but now 00:42:59.160 --> 00:43:01.250 align:start position:0% generating the proof on chain but now there<00:42:59.460> is<00:42:59.640> another<00:42:59.760> problem<00:43:00.180> how<00:43:01.020> do<00:43:01.140> you 00:43:01.250 --> 00:43:01.260 align:start position:0% there is another problem how do you 00:43:01.260 --> 00:43:02.870 align:start position:0% there is another problem how do you actually<00:43:01.380> know<00:43:01.619> what<00:43:01.859> you<00:43:02.040> should<00:43:02.220> do<00:43:02.400> like 00:43:02.870 --> 00:43:02.880 align:start position:0% actually know what you should do like 00:43:02.880 --> 00:43:04.849 align:start position:0% actually know what you should do like you<00:43:03.060> need<00:43:03.240> to<00:43:03.359> be<00:43:03.540> somehow<00:43:03.960> aware<00:43:04.260> of<00:43:04.440> what<00:43:04.680> is 00:43:04.849 --> 00:43:04.859 align:start position:0% you need to be somehow aware of what is 00:43:04.859 --> 00:43:07.490 align:start position:0% you need to be somehow aware of what is happening<00:43:05.280> and<00:43:05.819> for<00:43:06.000> that<00:43:06.180> reason<00:43:06.359> uh<00:43:07.260> we 00:43:07.490 --> 00:43:07.500 align:start position:0% happening and for that reason uh we 00:43:07.500 --> 00:43:10.130 align:start position:0% happening and for that reason uh we introduce<00:43:07.920> an<00:43:08.339> API<00:43:08.700> we<00:43:09.359> don't<00:43:09.480> expect<00:43:09.720> like 00:43:10.130 --> 00:43:10.140 align:start position:0% introduce an API we don't expect like 00:43:10.140 --> 00:43:12.050 align:start position:0% introduce an API we don't expect like developers<00:43:10.859> to<00:43:11.160> deal<00:43:11.520> with<00:43:11.700> all<00:43:11.880> that 00:43:12.050 --> 00:43:12.060 align:start position:0% developers to deal with all that 00:43:12.060 --> 00:43:14.210 align:start position:0% developers to deal with all that complexities<00:43:12.619> choosing<00:43:13.619> the<00:43:13.800> right<00:43:13.920> approach 00:43:14.210 --> 00:43:14.220 align:start position:0% complexities choosing the right approach 00:43:14.220 --> 00:43:17.030 align:start position:0% complexities choosing the right approach for<00:43:14.520> the<00:43:14.760> direct<00:43:15.240> thing<00:43:15.599> essentially<00:43:16.440> right 00:43:17.030 --> 00:43:17.040 align:start position:0% for the direct thing essentially right 00:43:17.040 --> 00:43:21.410 align:start position:0% for the direct thing essentially right now<00:43:17.220> our<00:43:17.460> apis<00:43:18.500> optimizes<00:43:19.500> cost<00:43:19.859> wise<00:43:20.280> uh<00:43:21.180> soon 00:43:21.410 --> 00:43:21.420 align:start position:0% now our apis optimizes cost wise uh soon 00:43:21.420 --> 00:43:24.230 align:start position:0% now our apis optimizes cost wise uh soon we'll<00:43:21.660> be<00:43:21.839> able<00:43:22.020> to<00:43:22.140> optimize<00:43:22.560> latency<00:43:23.040> wise 00:43:24.230 --> 00:43:24.240 align:start position:0% we'll be able to optimize latency wise 00:43:24.240 --> 00:43:27.109 align:start position:0% we'll be able to optimize latency wise um<00:43:24.780> and<00:43:25.319> yeah<00:43:25.440> and<00:43:25.859> essentially 00:43:27.109 --> 00:43:27.119 align:start position:0% um and yeah and essentially 00:43:27.119 --> 00:43:28.490 align:start position:0% um and yeah and essentially that's<00:43:27.660> it 00:43:28.490 --> 00:43:28.500 align:start position:0% that's it 00:43:28.500 --> 00:43:31.849 align:start position:0% that's it um<00:43:28.980> just<00:43:29.520> about<00:43:29.700> our<00:43:29.940> API<00:43:30.359> I<00:43:31.140> highly<00:43:31.440> highly 00:43:31.849 --> 00:43:31.859 align:start position:0% um just about our API I highly highly 00:43:31.859 --> 00:43:35.030 align:start position:0% um just about our API I highly highly encourage<00:43:32.280> you<00:43:32.460> to<00:43:32.940> check<00:43:33.480> this<00:43:33.720> out 00:43:35.030 --> 00:43:35.040 align:start position:0% encourage you to check this out 00:43:35.040 --> 00:43:37.010 align:start position:0% encourage you to check this out um<00:43:35.099> and<00:43:35.640> yeah<00:43:35.700> like<00:43:36.060> a<00:43:36.240> few<00:43:36.359> final<00:43:36.540> words<00:43:36.780> about 00:43:37.010 --> 00:43:37.020 align:start position:0% um and yeah like a few final words about 00:43:37.020 --> 00:43:39.589 align:start position:0% um and yeah like a few final words about the<00:43:37.260> API<00:43:37.560> it<00:43:38.099> acts<00:43:38.339> as<00:43:38.400> a<00:43:38.579> coordinator<00:43:39.000> it 00:43:39.589 --> 00:43:39.599 align:start position:0% the API it acts as a coordinator it 00:43:39.599 --> 00:43:41.750 align:start position:0% the API it acts as a coordinator it optimizes<00:43:40.200> the<00:43:40.319> costs<00:43:40.619> it<00:43:41.040> optimizes<00:43:41.520> the 00:43:41.750 --> 00:43:41.760 align:start position:0% optimizes the costs it optimizes the 00:43:41.760 --> 00:43:43.309 align:start position:0% optimizes the costs it optimizes the cost<00:43:42.000> because<00:43:42.240> we<00:43:42.599> can<00:43:42.720> batch<00:43:42.960> multiple 00:43:43.309 --> 00:43:43.319 align:start position:0% cost because we can batch multiple 00:43:43.319 --> 00:43:46.910 align:start position:0% cost because we can batch multiple things<00:43:43.640> and<00:43:44.640> once<00:43:45.060> the<00:43:45.180> job<00:43:45.359> is<00:43:45.540> done<00:43:45.720> you<00:43:46.619> get 00:43:46.910 --> 00:43:46.920 align:start position:0% things and once the job is done you get 00:43:46.920 --> 00:43:49.730 align:start position:0% things and once the job is done you get a<00:43:47.040> notification<00:43:47.460> like<00:43:47.700> via<00:43:48.060> webhook<00:43:48.660> VIA<00:43:49.619> an 00:43:49.730 --> 00:43:49.740 align:start position:0% a notification like via webhook VIA an 00:43:49.740 --> 00:43:51.349 align:start position:0% a notification like via webhook VIA an event<00:43:49.859> like<00:43:50.160> whatever<00:43:50.339> you<00:43:50.760> want<00:43:50.880> so 00:43:51.349 --> 00:43:51.359 align:start position:0% event like whatever you want so 00:43:51.359 --> 00:43:53.569 align:start position:0% event like whatever you want so essentially<00:43:51.720> you're<00:43:52.619> not<00:43:52.800> you<00:43:53.220> don't<00:43:53.339> need<00:43:53.460> to 00:43:53.569 --> 00:43:53.579 align:start position:0% essentially you're not you don't need to 00:43:53.579 --> 00:43:56.569 align:start position:0% essentially you're not you don't need to be<00:43:53.819> like<00:43:54.359> an<00:43:54.599> infrastructure<00:43:55.319> maintainer<00:43:56.040> and 00:43:56.569 --> 00:43:56.579 align:start position:0% be like an infrastructure maintainer and 00:43:56.579 --> 00:43:57.890 align:start position:0% be like an infrastructure maintainer and you<00:43:56.819> can<00:43:56.880> just<00:43:57.060> focus<00:43:57.359> on<00:43:57.540> essentially 00:43:57.890 --> 00:43:57.900 align:start position:0% you can just focus on essentially 00:43:57.900 --> 00:44:00.109 align:start position:0% you can just focus on essentially building<00:43:58.260> on<00:43:58.619> top<00:43:58.800> of<00:43:58.980> this<00:43:59.099> primitive 00:44:00.109 --> 00:44:00.119 align:start position:0% building on top of this primitive 00:44:00.119 --> 00:44:02.030 align:start position:0% building on top of this primitive and<00:44:00.599> I<00:44:00.780> think<00:44:00.900> that's<00:44:01.079> it 00:44:02.030 --> 00:44:02.040 align:start position:0% and I think that's it 00:44:02.040 --> 00:44:16.849 align:start position:0% and I think that's it um<00:44:02.099> questions 00:44:16.849 --> 00:44:16.859 align:start position:0% 00:44:16.859 --> 00:44:20.030 align:start position:0% so<00:44:17.760> the<00:44:18.180> API<00:44:18.540> essentially<00:44:18.960> is<00:44:19.079> a<00:44:19.319> rest<00:44:19.440> API<00:44:19.859> for 00:44:20.030 --> 00:44:20.040 align:start position:0% so the API essentially is a rest API for 00:44:20.040 --> 00:44:22.609 align:start position:0% so the API essentially is a rest API for now<00:44:20.220> we<00:44:20.760> also<00:44:21.000> have<00:44:21.119> a<00:44:21.240> Json<00:44:21.540> interface<00:44:22.079> we 00:44:22.609 --> 00:44:22.619 align:start position:0% now we also have a Json interface we 00:44:22.619 --> 00:44:25.609 align:start position:0% now we also have a Json interface we have<00:44:22.740> option<00:44:23.339> function<00:44:23.940> entry<00:44:24.359> points<00:44:24.660> so<00:44:25.200> we 00:44:25.609 --> 00:44:25.619 align:start position:0% have option function entry points so we 00:44:25.619 --> 00:44:27.589 align:start position:0% have option function entry points so we can<00:44:25.740> request<00:44:26.040> the<00:44:26.280> data<00:44:26.700> like<00:44:27.240> by<00:44:27.420> making 00:44:27.589 --> 00:44:27.599 align:start position:0% can request the data like by making 00:44:27.599 --> 00:44:30.109 align:start position:0% can request the data like by making enough<00:44:27.780> jingle<00:44:28.380> like<00:44:28.680> calling<00:44:29.339> a<00:44:29.460> rest<00:44:29.579> API<00:44:30.000> or 00:44:30.109 --> 00:44:30.119 align:start position:0% enough jingle like calling a rest API or 00:44:30.119 --> 00:44:33.650 align:start position:0% enough jingle like calling a rest API or like<00:44:30.300> calling<00:44:30.660> a<00:44:30.780> Json<00:44:31.380> or<00:44:31.560> PC<00:44:31.800> method<00:44:32.420> or<00:44:33.420> if 00:44:33.650 --> 00:44:33.660 align:start position:0% like calling a Json or PC method or if 00:44:33.660 --> 00:44:35.089 align:start position:0% like calling a Json or PC method or if you're<00:44:33.780> a<00:44:33.900> smart<00:44:34.079> contracts<00:44:34.560> like<00:44:34.680> wants<00:44:34.980> to 00:44:35.089 --> 00:44:35.099 align:start position:0% you're a smart contracts like wants to 00:44:35.099 --> 00:44:36.890 align:start position:0% you're a smart contracts like wants to access<00:44:35.220> this<00:44:35.460> data<00:44:35.819> then<00:44:35.940> you<00:44:36.300> just<00:44:36.420> submit<00:44:36.780> an 00:44:36.890 --> 00:44:36.900 align:start position:0% access this data then you just submit an 00:44:36.900 --> 00:44:38.809 align:start position:0% access this data then you just submit an event<00:44:37.020> we're<00:44:37.260> gonna<00:44:37.380> catch<00:44:37.740> the<00:44:37.859> event<00:44:37.980> and 00:44:38.809 --> 00:44:38.819 align:start position:0% event we're gonna catch the event and 00:44:38.819 --> 00:44:41.510 align:start position:0% event we're gonna catch the event and later<00:44:39.000> on<00:44:39.240> like<00:44:39.480> after<00:44:40.200> a<00:44:40.440> bit<00:44:40.560> of<00:44:40.740> time<00:44:40.920> fit 00:44:41.510 --> 00:44:41.520 align:start position:0% later on like after a bit of time fit 00:44:41.520 --> 00:44:43.550 align:start position:0% later on like after a bit of time fit this<00:44:41.940> uh<00:44:42.359> the<00:44:42.599> specific<00:44:42.839> data<00:44:43.140> inside<00:44:43.319> the 00:44:43.550 --> 00:44:43.560 align:start position:0% this uh the specific data inside the 00:44:43.560 --> 00:44:45.290 align:start position:0% this uh the specific data inside the smart<00:44:43.680> contract<00:44:44.160> so<00:44:44.640> we<00:44:44.700> have<00:44:44.880> like<00:44:45.000> a<00:44:45.119> bunch 00:44:45.290 --> 00:44:45.300 align:start position:0% smart contract so we have like a bunch 00:44:45.300 --> 00:44:47.510 align:start position:0% smart contract so we have like a bunch of<00:44:45.359> interfaces<00:44:46.020> and<00:44:46.740> by<00:44:46.859> the<00:44:46.920> way<00:44:46.980> speaking<00:44:47.400> of 00:44:47.510 --> 00:44:47.520 align:start position:0% of interfaces and by the way speaking of 00:44:47.520 --> 00:44:49.250 align:start position:0% of interfaces and by the way speaking of like<00:44:47.640> the<00:44:47.760> off-train<00:44:48.180> entry<00:44:48.480> points<00:44:48.720> once<00:44:49.200> the 00:44:49.250 --> 00:44:49.260 align:start position:0% like the off-train entry points once the 00:44:49.260 --> 00:44:51.530 align:start position:0% like the off-train entry points once the entire<00:44:49.619> leg<00:44:49.859> work<00:44:50.040> is<00:44:50.280> done<00:44:50.400> on<00:44:50.520> our<00:44:50.700> side<00:44:50.940> you 00:44:51.530 --> 00:44:51.540 align:start position:0% entire leg work is done on our side you 00:44:51.540 --> 00:44:54.290 align:start position:0% entire leg work is done on our side you can<00:44:51.599> get<00:44:51.780> a<00:44:52.020> notification<00:44:52.859> it<00:44:53.339> can<00:44:53.520> be<00:44:53.640> like<00:44:53.880> a 00:44:54.290 --> 00:44:54.300 align:start position:0% can get a notification it can be like a 00:44:54.300 --> 00:44:56.390 align:start position:0% can get a notification it can be like a web<00:44:54.420> hook<00:44:54.660> we<00:44:55.260> can<00:44:55.440> like<00:44:55.560> send<00:44:55.800> you<00:44:55.920> a<00:44:56.099> bit<00:44:56.220> of 00:44:56.390 --> 00:44:56.400 align:start position:0% web hook we can like send you a bit of 00:44:56.400 --> 00:44:59.150 align:start position:0% web hook we can like send you a bit of information<00:44:56.579> like<00:44:57.180> using<00:44:57.599> a<00:44:57.720> websocket<00:44:58.319> uh<00:44:59.040> it 00:44:59.150 --> 00:44:59.160 align:start position:0% information like using a websocket uh it 00:44:59.160 --> 00:45:01.010 align:start position:0% information like using a websocket uh it can<00:44:59.280> be<00:44:59.400> essentially<00:44:59.760> whatever<00:45:00.180> whatever<00:45:00.599> you 00:45:01.010 --> 00:45:01.020 align:start position:0% can be essentially whatever whatever you 00:45:01.020 --> 00:45:10.630 align:start position:0% can be essentially whatever whatever you want 00:45:10.630 --> 00:45:10.640 align:start position:0% 00:45:10.640 --> 00:45:13.550 align:start position:0% oh<00:45:11.640> yeah<00:45:11.819> so<00:45:12.180> uh<00:45:12.599> that's<00:45:12.960> actually<00:45:13.200> a<00:45:13.440> great 00:45:13.550 --> 00:45:13.560 align:start position:0% oh yeah so uh that's actually a great 00:45:13.560 --> 00:45:16.430 align:start position:0% oh yeah so uh that's actually a great question<00:45:13.859> so<00:45:14.760> different<00:45:15.540> chains<00:45:16.079> use<00:45:16.200> a 00:45:16.430 --> 00:45:16.440 align:start position:0% question so different chains use a 00:45:16.440 --> 00:45:19.130 align:start position:0% question so different chains use a different<00:45:16.680> like<00:45:16.920> storage<00:45:17.280> uh<00:45:18.060> I<00:45:18.900> would<00:45:19.020> say 00:45:19.130 --> 00:45:19.140 align:start position:0% different like storage uh I would say 00:45:19.140 --> 00:45:20.450 align:start position:0% different like storage uh I would say architecture<00:45:19.680> they<00:45:19.920> might<00:45:20.099> commit<00:45:20.400> to 00:45:20.450 --> 00:45:20.460 align:start position:0% architecture they might commit to 00:45:20.460 --> 00:45:23.630 align:start position:0% architecture they might commit to America<00:45:20.579> Patricia<00:45:21.240> 3<00:45:21.359> Miracle<00:45:21.900> 3<00:45:22.220> uh<00:45:23.220> maybe 00:45:23.630 --> 00:45:23.640 align:start position:0% America Patricia 3 Miracle 3 uh maybe 00:45:23.640 --> 00:45:26.030 align:start position:0% America Patricia 3 Miracle 3 uh maybe even<00:45:23.880> vertical<00:45:24.300> tree<00:45:24.599> and<00:45:25.140> obviously<00:45:25.500> like<00:45:25.920> I 00:45:26.030 --> 00:45:26.040 align:start position:0% even vertical tree and obviously like I 00:45:26.040 --> 00:45:28.970 align:start position:0% even vertical tree and obviously like I start<00:45:26.160> having<00:45:26.400> a<00:45:26.640> generalized<00:45:27.240> verifier<00:45:28.200> it's 00:45:28.970 --> 00:45:28.980 align:start position:0% start having a generalized verifier it's 00:45:28.980 --> 00:45:32.569 align:start position:0% start having a generalized verifier it's like<00:45:29.460> pretty<00:45:29.780> it's<00:45:30.780> not<00:45:31.020> a<00:45:31.319> clean<00:45:31.500> approach<00:45:31.920> so 00:45:32.569 --> 00:45:32.579 align:start position:0% like pretty it's not a clean approach so 00:45:32.579 --> 00:45:35.390 align:start position:0% like pretty it's not a clean approach so we<00:45:32.819> essentially<00:45:33.180> abstract<00:45:33.720> it<00:45:34.140> but<00:45:34.920> by<00:45:35.099> using 00:45:35.390 --> 00:45:35.400 align:start position:0% we essentially abstract it but by using 00:45:35.400 --> 00:45:38.210 align:start position:0% we essentially abstract it but by using a<00:45:35.520> snark<00:45:35.819> and<00:45:36.599> inside<00:45:36.900> the<00:45:37.200> snark<00:45:37.500> itself<00:45:37.859> we 00:45:38.210 --> 00:45:38.220 align:start position:0% a snark and inside the snark itself we 00:45:38.220 --> 00:45:41.450 align:start position:0% a snark and inside the snark itself we just<00:45:38.460> do<00:45:39.300> the<00:45:39.599> proper<00:45:40.140> work<00:45:40.440> like 00:45:41.450 --> 00:45:41.460 align:start position:0% just do the proper work like 00:45:41.460 --> 00:45:43.730 align:start position:0% just do the proper work like you<00:45:42.000> know<00:45:42.180> we<00:45:42.359> go<00:45:42.660> for<00:45:42.780> the<00:45:42.960> for<00:45:43.200> the<00:45:43.380> tree<00:45:43.500> like 00:45:43.730 --> 00:45:43.740 align:start position:0% you know we go for the for the tree like 00:45:43.740 --> 00:45:45.170 align:start position:0% you know we go for the for the tree like through<00:45:43.920> the<00:45:44.160> for<00:45:44.339> the<00:45:44.640> um<00:45:44.640> through<00:45:45.060> the 00:45:45.170 --> 00:45:45.180 align:start position:0% through the for the um through the 00:45:45.180 --> 00:45:46.849 align:start position:0% through the for the um through the elements<00:45:45.480> of<00:45:45.599> the<00:45:45.780> proof<00:45:46.020> and<00:45:46.140> then<00:45:46.319> we<00:45:46.740> can 00:45:46.849 --> 00:45:46.859 align:start position:0% elements of the proof and then we can 00:45:46.859 --> 00:45:49.130 align:start position:0% elements of the proof and then we can like<00:45:47.040> use<00:45:47.220> a<00:45:47.460> specific<00:45:47.760> hashing<00:45:48.180> function<00:45:48.480> so 00:45:49.130 --> 00:45:49.140 align:start position:0% like use a specific hashing function so 00:45:49.140 --> 00:45:52.309 align:start position:0% like use a specific hashing function so for<00:45:49.380> example<00:45:49.760> now<00:45:50.760> Poseidon<00:45:51.359> is<00:45:51.480> Poseidon<00:45:52.020> is 00:45:52.309 --> 00:45:52.319 align:start position:0% for example now Poseidon is Poseidon is 00:45:52.319 --> 00:45:55.250 align:start position:0% for example now Poseidon is Poseidon is uh<00:45:52.859> is<00:45:53.460> is<00:45:53.640> pretty<00:45:53.940> popular 00:45:55.250 --> 00:45:55.260 align:start position:0% uh is is pretty popular 00:45:55.260 --> 00:45:57.770 align:start position:0% uh is is pretty popular um<00:45:55.380> I<00:45:55.920> think<00:45:56.099> that<00:45:56.339> scroll<00:45:56.700> uses<00:45:57.119> Poseidon<00:45:57.660> and 00:45:57.770 --> 00:45:57.780 align:start position:0% um I think that scroll uses Poseidon and 00:45:57.780 --> 00:46:01.190 align:start position:0% um I think that scroll uses Poseidon and also<00:45:58.140> SDK<00:45:58.920> sync<00:45:59.160> uses<00:45:59.339> Poseidon<00:45:59.940> on<00:46:00.780> the<00:46:00.839> avian 00:46:01.190 --> 00:46:01.200 align:start position:0% also SDK sync uses Poseidon on the avian 00:46:01.200 --> 00:46:02.930 align:start position:0% also SDK sync uses Poseidon on the avian like<00:46:01.440> performing<00:46:02.040> Poseidon<00:46:02.520> will<00:46:02.640> be<00:46:02.819> pretty 00:46:02.930 --> 00:46:02.940 align:start position:0% like performing Poseidon will be pretty 00:46:02.940 --> 00:46:05.030 align:start position:0% like performing Poseidon will be pretty expensive<00:46:03.480> so<00:46:04.140> for<00:46:04.319> that<00:46:04.440> reason<00:46:04.619> you<00:46:04.859> cannot 00:46:05.030 --> 00:46:05.040 align:start position:0% expensive so for that reason you cannot 00:46:05.040 --> 00:46:06.770 align:start position:0% expensive so for that reason you cannot verify<00:46:05.339> the<00:46:05.520> proof<00:46:05.819> directly<00:46:06.119> but<00:46:06.480> what<00:46:06.599> you 00:46:06.770 --> 00:46:06.780 align:start position:0% verify the proof directly but what you 00:46:06.780 --> 00:46:07.910 align:start position:0% verify the proof directly but what you can<00:46:06.900> do<00:46:07.020> you<00:46:07.140> can<00:46:07.319> do<00:46:07.560> the<00:46:07.680> entire 00:46:07.910 --> 00:46:07.920 align:start position:0% can do you can do the entire 00:46:07.920 --> 00:46:09.890 align:start position:0% can do you can do the entire verification<00:46:08.339> inside<00:46:08.579> the<00:46:08.760> snark<00:46:09.060> and<00:46:09.720> then 00:46:09.890 --> 00:46:09.900 align:start position:0% verification inside the snark and then 00:46:09.900 --> 00:46:11.390 align:start position:0% verification inside the snark and then on<00:46:10.140> the<00:46:10.260> one<00:46:10.440> you<00:46:10.560> don't<00:46:10.740> really<00:46:10.920> care<00:46:11.099> what 00:46:11.390 --> 00:46:11.400 align:start position:0% on the one you don't really care what 00:46:11.400 --> 00:46:13.309 align:start position:0% on the one you don't really care what the<00:46:11.579> Strunk<00:46:12.060> is<00:46:12.240> like<00:46:12.420> doing<00:46:12.660> you<00:46:12.900> just<00:46:13.140> just 00:46:13.309 --> 00:46:13.319 align:start position:0% the Strunk is like doing you just just 00:46:13.319 --> 00:46:15.349 align:start position:0% the Strunk is like doing you just just verify<00:46:13.740> it<00:46:13.920> so<00:46:14.400> that's<00:46:14.520> how<00:46:14.700> we<00:46:14.880> actually<00:46:15.000> did 00:46:15.349 --> 00:46:15.359 align:start position:0% verify it so that's how we actually did 00:46:15.359 --> 00:46:17.150 align:start position:0% verify it so that's how we actually did it<00:46:15.599> deal<00:46:15.900> with<00:46:16.079> it<00:46:16.200> if<00:46:16.440> we<00:46:16.619> need<00:46:16.740> to<00:46:16.800> have<00:46:17.040> it 00:46:17.150 --> 00:46:17.160 align:start position:0% it deal with it if we need to have it 00:46:17.160 --> 00:46:18.589 align:start position:0% it deal with it if we need to have it abstracted<00:46:17.520> we<00:46:17.700> have<00:46:17.819> it<00:46:17.940> abstracted<00:46:18.359> if<00:46:18.480> we 00:46:18.589 --> 00:46:18.599 align:start position:0% abstracted we have it abstracted if we 00:46:18.599 --> 00:46:23.510 align:start position:0% abstracted we have it abstracted if we don't<00:46:18.780> then<00:46:19.260> we<00:46:19.619> just<00:46:19.800> don't 00:46:23.510 --> 00:46:23.520 align:start position:0% 00:46:23.520 --> 00:46:28.250 align:start position:0% foreign 00:46:28.250 --> 00:46:28.260 align:start position:0% 00:46:28.260 --> 00:46:34.190 align:start position:0% oh<00:46:28.740> yeah 00:46:34.190 --> 00:46:34.200 align:start position:0% 00:46:34.200 --> 00:46:36.470 align:start position:0% oh<00:46:34.680> yeah<00:46:34.980> that's<00:46:35.339> uh<00:46:35.640> that's<00:46:35.940> actually<00:46:36.180> a<00:46:36.359> good 00:46:36.470 --> 00:46:36.480 align:start position:0% oh yeah that's uh that's actually a good 00:46:36.480 --> 00:46:38.089 align:start position:0% oh yeah that's uh that's actually a good question<00:46:36.660> because<00:46:36.900> I<00:46:37.140> think<00:46:37.319> I<00:46:37.500> went<00:46:37.680> super 00:46:38.089 --> 00:46:38.099 align:start position:0% question because I think I went super 00:46:38.099 --> 00:46:40.490 align:start position:0% question because I think I went super technical<00:46:38.640> uh<00:46:39.480> so<00:46:39.660> actually<00:46:39.780> what<00:46:40.079> we<00:46:40.200> do<00:46:40.380> at 00:46:40.490 --> 00:46:40.500 align:start position:0% technical uh so actually what we do at 00:46:40.500 --> 00:46:43.190 align:start position:0% technical uh so actually what we do at Herodotus<00:46:41.099> every<00:46:41.700> two<00:46:42.540> weeks<00:46:42.780> we<00:46:42.900> have<00:46:43.079> some 00:46:43.190 --> 00:46:43.200 align:start position:0% Herodotus every two weeks we have some 00:46:43.200 --> 00:46:45.290 align:start position:0% Herodotus every two weeks we have some internal<00:46:43.500> hackathons<00:46:44.040> and<00:46:44.400> right<00:46:44.760> before<00:46:45.000> the 00:46:45.290 --> 00:46:45.300 align:start position:0% internal hackathons and right before the 00:46:45.300 --> 00:46:48.290 align:start position:0% internal hackathons and right before the merge<00:46:45.660> uh<00:46:46.560> we<00:46:46.859> built<00:46:47.400> a<00:46:47.520> proof<00:46:47.880> of<00:46:47.940> concept 00:46:48.290 --> 00:46:48.300 align:start position:0% merge uh we built a proof of concept 00:46:48.300 --> 00:46:50.270 align:start position:0% merge uh we built a proof of concept that<00:46:48.599> we<00:46:48.720> called<00:46:48.900> merge<00:46:49.380> Swap<00:46:49.680> and 00:46:50.270 --> 00:46:50.280 align:start position:0% that we called merge Swap and 00:46:50.280 --> 00:46:52.190 align:start position:0% that we called merge Swap and essentially<00:46:50.579> we<00:46:50.880> allowed<00:46:51.300> anyone<00:46:51.780> to<00:46:52.020> dump 00:46:52.190 --> 00:46:52.200 align:start position:0% essentially we allowed anyone to dump 00:46:52.200 --> 00:46:55.190 align:start position:0% essentially we allowed anyone to dump their<00:46:52.500> proof<00:46:53.160> of<00:46:53.280> work<00:46:53.819> if<00:46:54.119> on<00:46:54.420> proof<00:46:54.780> of<00:46:54.839> stake 00:46:55.190 --> 00:46:55.200 align:start position:0% their proof of work if on proof of stake 00:46:55.200 --> 00:46:56.750 align:start position:0% their proof of work if on proof of stake and<00:46:55.560> the<00:46:55.740> way<00:46:55.859> how<00:46:56.040> it<00:46:56.160> works<00:46:56.460> would<00:46:56.579> you 00:46:56.750 --> 00:46:56.760 align:start position:0% and the way how it works would you 00:46:56.760 --> 00:46:58.430 align:start position:0% and the way how it works would you literally<00:46:57.000> build<00:46:57.240> a<00:46:57.480> bridge<00:46:57.599> on<00:46:57.900> top<00:46:58.020> of<00:46:58.200> this 00:46:58.430 --> 00:46:58.440 align:start position:0% literally build a bridge on top of this 00:46:58.440 --> 00:47:00.650 align:start position:0% literally build a bridge on top of this technology<00:46:59.220> and<00:46:59.579> the<00:46:59.700> bridge<00:46:59.880> Works<00:47:00.359> in<00:47:00.420> a<00:47:00.599> way 00:47:00.650 --> 00:47:00.660 align:start position:0% technology and the bridge Works in a way 00:47:00.660 --> 00:47:04.190 align:start position:0% technology and the bridge Works in a way that<00:47:00.839> you<00:47:01.020> can<00:47:01.140> lock<00:47:01.680> your<00:47:02.760> if<00:47:03.480> proof<00:47:03.960> of<00:47:04.020> work 00:47:04.190 --> 00:47:04.200 align:start position:0% that you can lock your if proof of work 00:47:04.200 --> 00:47:07.190 align:start position:0% that you can lock your if proof of work inside<00:47:04.500> a<00:47:04.800> smart<00:47:05.040> contract<00:47:05.520> on<00:47:06.480> if<00:47:06.780> proof<00:47:07.140> of 00:47:07.190 --> 00:47:07.200 align:start position:0% inside a smart contract on if proof of 00:47:07.200 --> 00:47:09.109 align:start position:0% inside a smart contract on if proof of under<00:47:07.380> if<00:47:07.619> proof<00:47:07.980> of<00:47:07.980> work<00:47:08.160> chain<00:47:08.400> you<00:47:09.000> can 00:47:09.109 --> 00:47:09.119 align:start position:0% under if proof of work chain you can 00:47:09.119 --> 00:47:11.329 align:start position:0% under if proof of work chain you can prove<00:47:09.420> that<00:47:09.540> you've<00:47:09.780> done<00:47:09.900> it<00:47:10.079> on<00:47:10.500> ethereum 00:47:11.329 --> 00:47:11.339 align:start position:0% prove that you've done it on ethereum 00:47:11.339 --> 00:47:13.370 align:start position:0% prove that you've done it on ethereum proof<00:47:11.579> of<00:47:11.640> stake<00:47:11.940> you<00:47:12.540> can<00:47:12.720> once<00:47:13.079> you<00:47:13.200> the 00:47:13.370 --> 00:47:13.380 align:start position:0% proof of stake you can once you the 00:47:13.380 --> 00:47:15.589 align:start position:0% proof of stake you can once you the proof<00:47:13.619> is<00:47:13.740> verified<00:47:14.040> you<00:47:14.640> can<00:47:14.760> meet<00:47:14.940> your<00:47:15.180> C20 00:47:15.589 --> 00:47:15.599 align:start position:0% proof is verified you can meet your C20 00:47:15.599 --> 00:47:17.990 align:start position:0% proof is verified you can meet your C20 token<00:47:16.140> and<00:47:16.980> you<00:47:17.220> can<00:47:17.280> do<00:47:17.400> whatever<00:47:17.579> you<00:47:17.880> want 00:47:17.990 --> 00:47:18.000 align:start position:0% token and you can do whatever you want 00:47:18.000 --> 00:47:19.730 align:start position:0% token and you can do whatever you want with<00:47:18.180> this<00:47:18.359> token<00:47:18.720> and<00:47:19.140> then<00:47:19.260> if<00:47:19.440> you<00:47:19.560> want<00:47:19.680> to 00:47:19.730 --> 00:47:19.740 align:start position:0% with this token and then if you want to 00:47:19.740 --> 00:47:21.349 align:start position:0% with this token and then if you want to withdraw<00:47:20.220> back<00:47:20.339> to<00:47:20.460> if<00:47:20.760> you're<00:47:20.940> in<00:47:21.060> proof<00:47:21.300> of 00:47:21.349 --> 00:47:21.359 align:start position:0% withdraw back to if you're in proof of 00:47:21.359 --> 00:47:23.930 align:start position:0% withdraw back to if you're in proof of work<00:47:21.780> you<00:47:22.319> just<00:47:22.500> burn<00:47:22.680> it<00:47:22.920> you<00:47:23.400> prove<00:47:23.700> the<00:47:23.760> fact 00:47:23.930 --> 00:47:23.940 align:start position:0% work you just burn it you prove the fact 00:47:23.940 --> 00:47:26.329 align:start position:0% work you just burn it you prove the fact that<00:47:24.119> you<00:47:24.359> burned<00:47:24.960> on<00:47:25.200> the<00:47:25.319> other<00:47:25.380> side<00:47:25.680> and 00:47:26.329 --> 00:47:26.339 align:start position:0% that you burned on the other side and 00:47:26.339 --> 00:47:28.190 align:start position:0% that you burned on the other side and and<00:47:26.579> yeah<00:47:26.760> that's<00:47:26.940> it<00:47:27.180> also<00:47:27.720> in<00:47:27.900> terms<00:47:28.079> of 00:47:28.190 --> 00:47:28.200 align:start position:0% and yeah that's it also in terms of 00:47:28.200 --> 00:47:31.510 align:start position:0% and yeah that's it also in terms of other<00:47:28.740> use<00:47:29.099> cases<00:47:29.400> I<00:47:30.300> think<00:47:30.420> that 00:47:31.510 --> 00:47:31.520 align:start position:0% other use cases I think that 00:47:31.520 --> 00:47:34.130 align:start position:0% other use cases I think that cross-chain<00:47:32.520> collateralization<00:47:33.240> is<00:47:33.839> pretty 00:47:34.130 --> 00:47:34.140 align:start position:0% cross-chain collateralization is pretty 00:47:34.140 --> 00:47:36.349 align:start position:0% cross-chain collateralization is pretty cool<00:47:34.380> because<00:47:35.040> this<00:47:35.280> is<00:47:35.460> the<00:47:35.700> place<00:47:35.880> where<00:47:36.180> you 00:47:36.349 --> 00:47:36.359 align:start position:0% cool because this is the place where you 00:47:36.359 --> 00:47:38.030 align:start position:0% cool because this is the place where you want<00:47:36.540> to<00:47:36.720> avoid<00:47:37.020> latency<00:47:37.380> as<00:47:37.740> much<00:47:37.859> as 00:47:38.030 --> 00:47:38.040 align:start position:0% want to avoid latency as much as 00:47:38.040 --> 00:47:40.849 align:start position:0% want to avoid latency as much as possible<00:47:38.339> and<00:47:39.000> you<00:47:39.180> want<00:47:39.359> to<00:47:39.480> be<00:47:39.859> asynchronous 00:47:40.849 --> 00:47:40.859 align:start position:0% possible and you want to be asynchronous 00:47:40.859 --> 00:47:42.650 align:start position:0% possible and you want to be asynchronous as<00:47:41.099> much<00:47:41.280> as<00:47:41.400> possible<00:47:41.700> and<00:47:42.300> essentially 00:47:42.650 --> 00:47:42.660 align:start position:0% as much as possible and essentially 00:47:42.660 --> 00:47:44.870 align:start position:0% as much as possible and essentially that's<00:47:42.960> that's<00:47:43.380> what<00:47:43.740> we<00:47:43.920> do<00:47:44.040> here<00:47:44.220> because 00:47:44.870 --> 00:47:44.880 align:start position:0% that's that's what we do here because 00:47:44.880 --> 00:47:47.390 align:start position:0% that's that's what we do here because our<00:47:45.180> latency<00:47:45.599> comes<00:47:46.020> only<00:47:46.200> from<00:47:46.680> from<00:47:47.160> the 00:47:47.390 --> 00:47:47.400 align:start position:0% our latency comes only from from the 00:47:47.400 --> 00:47:49.670 align:start position:0% our latency comes only from from the proving<00:47:47.700> time<00:47:47.940> but<00:47:48.660> again<00:47:48.839> using<00:47:49.560> some 00:47:49.670 --> 00:47:49.680 align:start position:0% proving time but again using some 00:47:49.680 --> 00:47:51.589 align:start position:0% proving time but again using some optimistic<00:47:50.220> approaches<00:47:50.520> and<00:47:50.640> so<00:47:50.819> on<00:47:50.940> there<00:47:51.119> a 00:47:51.589 --> 00:47:51.599 align:start position:0% optimistic approaches and so on there a 00:47:51.599 --> 00:47:53.089 align:start position:0% optimistic approaches and so on there a lot<00:47:51.720> of<00:47:51.839> things<00:47:52.020> we<00:47:52.200> can<00:47:52.440> do 00:47:53.089 --> 00:47:53.099 align:start position:0% lot of things we can do 00:47:53.099 --> 00:47:58.250 align:start position:0% lot of things we can do cure<00:47:53.700> I<00:47:54.240> hope<00:47:54.359> it<00:47:54.599> answers<00:47:55.319> the<00:47:55.560> question 00:47:58.250 --> 00:47:58.260 align:start position:0% 00:47:58.260 --> 00:48:00.410 align:start position:0% okay<00:47:58.619> I<00:47:59.040> think<00:47:59.160> that's<00:47:59.280> it<00:47:59.460> I<00:47:59.760> have<00:47:59.880> like<00:48:00.180> three 00:48:00.410 --> 00:48:00.420 align:start position:0% okay I think that's it I have like three 00:48:00.420 --> 00:48:03.349 align:start position:0% okay I think that's it I have like three minutes<00:48:00.660> so<00:48:01.200> I<00:48:01.440> guess<00:48:01.560> we<00:48:01.740> can<00:48:01.859> wrap<00:48:02.040> it<00:48:02.160> up<00:48:02.760> and 00:48:03.349 --> 00:48:03.359 align:start position:0% minutes so I guess we can wrap it up and 00:48:03.359 --> 00:48:04.840 align:start position:0% minutes so I guess we can wrap it up and yeah<00:48:03.540> thanks 00:48:04.840 --> 00:48:04.850 align:start position:0% yeah thanks 00:48:04.850 --> 00:48:09.400 align:start position:0% yeah thanks [Applause]