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:18.590 align:start position:0% [Music] 00:00:18.590 --> 00:00:18.600 align:start position:0% 00:00:18.600 --> 00:00:20.269 align:start position:0% all<00:00:19.080> right<00:00:19.199> all<00:00:19.440> right<00:00:19.619> all<00:00:19.800> right<00:00:19.920> you<00:00:20.100> just 00:00:20.269 --> 00:00:20.279 align:start position:0% all right all right all right you just 00:00:20.279 --> 00:00:22.670 align:start position:0% all right all right all right you just heard<00:00:20.400> Carl<00:00:20.640> talk 00:00:22.670 --> 00:00:22.680 align:start position:0% heard Carl talk 00:00:22.680 --> 00:00:24.529 align:start position:0% heard Carl talk um 00:00:24.529 --> 00:00:24.539 align:start position:0% um 00:00:24.539 --> 00:00:27.050 align:start position:0% um about<00:00:24.779> a<00:00:25.019> lot<00:00:25.140> of<00:00:25.260> high<00:00:25.380> level<00:00:25.560> things 00:00:27.050 --> 00:00:27.060 align:start position:0% about a lot of high level things 00:00:27.060 --> 00:00:29.170 align:start position:0% about a lot of high level things my<00:00:27.480> talk<00:00:27.660> is 00:00:29.170 --> 00:00:29.180 align:start position:0% my talk is 00:00:29.180 --> 00:00:31.429 align:start position:0% my talk is unfortunately<00:00:30.180> that<00:00:30.660> slides<00:00:31.080> don't<00:00:31.260> look 00:00:31.429 --> 00:00:31.439 align:start position:0% unfortunately that slides don't look 00:00:31.439 --> 00:00:33.590 align:start position:0% unfortunately that slides don't look like<00:00:31.619> Carl's<00:00:32.099> talk<00:00:32.340> so<00:00:32.640> it's<00:00:33.239> a<00:00:33.360> little<00:00:33.420> bit 00:00:33.590 --> 00:00:33.600 align:start position:0% like Carl's talk so it's a little bit 00:00:33.600 --> 00:00:34.389 align:start position:0% like Carl's talk so it's a little bit different 00:00:34.389 --> 00:00:34.399 align:start position:0% different 00:00:34.399 --> 00:00:36.950 align:start position:0% different I<00:00:35.399> want<00:00:35.640> to 00:00:36.950 --> 00:00:36.960 align:start position:0% I want to 00:00:36.960 --> 00:00:39.709 align:start position:0% I want to I<00:00:37.559> want<00:00:37.680> to<00:00:37.920> ground<00:00:38.160> this<00:00:38.760> what<00:00:39.120> Carl<00:00:39.420> just 00:00:39.709 --> 00:00:39.719 align:start position:0% I want to ground this what Carl just 00:00:39.719 --> 00:00:42.650 align:start position:0% I want to ground this what Carl just talked<00:00:40.020> about<00:00:40.160> in<00:00:41.160> the<00:00:41.460> actual<00:00:41.820> Tech<00:00:42.180> behind 00:00:42.650 --> 00:00:42.660 align:start position:0% talked about in the actual Tech behind 00:00:42.660 --> 00:00:44.690 align:start position:0% talked about in the actual Tech behind the<00:00:42.840> op<00:00:43.020> stack<00:00:43.500> right<00:00:43.739> I<00:00:43.980> want<00:00:44.100> to<00:00:44.219> present<00:00:44.520> to 00:00:44.690 --> 00:00:44.700 align:start position:0% the op stack right I want to present to 00:00:44.700 --> 00:00:46.670 align:start position:0% the op stack right I want to present to you<00:00:44.879> what<00:00:45.420> the<00:00:45.540> op<00:00:45.660> stack<00:00:46.200> looks<00:00:46.440> like<00:00:46.500> under 00:00:46.670 --> 00:00:46.680 align:start position:0% you what the op stack looks like under 00:00:46.680 --> 00:00:48.889 align:start position:0% you what the op stack looks like under the<00:00:46.920> hood<00:00:47.040> I<00:00:47.460> want<00:00:47.640> to<00:00:47.700> present<00:00:47.940> to<00:00:48.120> you<00:00:48.239> the 00:00:48.889 --> 00:00:48.899 align:start position:0% the hood I want to present to you the 00:00:48.899 --> 00:00:51.049 align:start position:0% the hood I want to present to you the theory<00:00:49.260> of<00:00:49.800> how<00:00:50.100> you<00:00:50.340> build<00:00:50.520> modular 00:00:51.049 --> 00:00:51.059 align:start position:0% theory of how you build modular 00:00:51.059 --> 00:00:53.990 align:start position:0% theory of how you build modular blockchains<00:00:51.960> right<00:00:52.320> not<00:00:52.800> just<00:00:53.039> oh<00:00:53.640> you<00:00:53.940> know 00:00:53.990 --> 00:00:54.000 align:start position:0% blockchains right not just oh you know 00:00:54.000 --> 00:00:56.150 align:start position:0% blockchains right not just oh you know let's<00:00:54.180> make<00:00:54.420> some<00:00:54.660> charts<00:00:55.199> and<00:00:55.800> let's<00:00:55.920> figure 00:00:56.150 --> 00:00:56.160 align:start position:0% let's make some charts and let's figure 00:00:56.160 --> 00:00:58.130 align:start position:0% let's make some charts and let's figure it<00:00:56.399> out<00:00:56.579> and<00:00:56.940> and<00:00:57.180> you<00:00:57.420> know<00:00:57.539> somebody<00:00:57.840> will 00:00:58.130 --> 00:00:58.140 align:start position:0% it out and and you know somebody will 00:00:58.140 --> 00:00:59.689 align:start position:0% it out and and you know somebody will piece<00:00:58.620> these<00:00:58.860> things<00:00:58.920> together<00:00:59.160> I<00:00:59.460> want<00:00:59.579> to 00:00:59.689 --> 00:00:59.699 align:start position:0% piece these things together I want to 00:00:59.699 --> 00:01:03.410 align:start position:0% piece these things together I want to give<00:00:59.879> concrete<00:01:00.600> apis<00:01:01.559> and<00:01:02.460> functions<00:01:03.059> that 00:01:03.410 --> 00:01:03.420 align:start position:0% give concrete apis and functions that 00:01:03.420 --> 00:01:05.210 align:start position:0% give concrete apis and functions that describe<00:01:04.019> the<00:01:04.260> different<00:01:04.440> layers<00:01:04.860> of<00:01:05.100> a 00:01:05.210 --> 00:01:05.220 align:start position:0% describe the different layers of a 00:01:05.220 --> 00:01:06.710 align:start position:0% describe the different layers of a system<00:01:05.400> like<00:01:05.760> this<00:01:05.939> so<00:01:06.119> you<00:01:06.240> can<00:01:06.360> really<00:01:06.540> start 00:01:06.710 --> 00:01:06.720 align:start position:0% system like this so you can really start 00:01:06.720 --> 00:01:08.270 align:start position:0% system like this so you can really start to<00:01:06.900> wrap<00:01:07.080> your<00:01:07.260> head<00:01:07.380> around<00:01:07.560> how<00:01:07.920> something 00:01:08.270 --> 00:01:08.280 align:start position:0% to wrap your head around how something 00:01:08.280 --> 00:01:11.390 align:start position:0% to wrap your head around how something like<00:01:09.240> the<00:01:09.360> op<00:01:09.540> stack<00:01:10.020> works<00:01:10.439> I'm<00:01:11.040> going<00:01:11.159> to<00:01:11.280> be 00:01:11.390 --> 00:01:11.400 align:start position:0% like the op stack works I'm going to be 00:01:11.400 --> 00:01:13.190 align:start position:0% like the op stack works I'm going to be continuously<00:01:12.000> out<00:01:12.299> of<00:01:12.420> breath<00:01:12.720> because<00:01:12.960> we're 00:01:13.190 --> 00:01:13.200 align:start position:0% continuously out of breath because we're 00:01:13.200 --> 00:01:14.929 align:start position:0% continuously out of breath because we're like<00:01:13.380> 8<00:01:13.860> 000<00:01:13.920> feet<00:01:14.100> up<00:01:14.340> in<00:01:14.460> the<00:01:14.580> air<00:01:14.700> it's 00:01:14.929 --> 00:01:14.939 align:start position:0% like 8 000 feet up in the air it's 00:01:14.939 --> 00:01:17.510 align:start position:0% like 8 000 feet up in the air it's really<00:01:15.240> hard<00:01:15.479> to<00:01:15.720> talk<00:01:15.900> so<00:01:16.320> here<00:01:17.280> you<00:01:17.400> go 00:01:17.510 --> 00:01:17.520 align:start position:0% really hard to talk so here you go 00:01:17.520 --> 00:01:18.950 align:start position:0% really hard to talk so here you go modular<00:01:17.880> roll-up<00:01:18.240> Theory<00:01:18.479> through<00:01:18.659> the<00:01:18.780> lens 00:01:18.950 --> 00:01:18.960 align:start position:0% modular roll-up Theory through the lens 00:01:18.960 --> 00:01:21.050 align:start position:0% modular roll-up Theory through the lens of<00:01:19.080> the<00:01:19.140> op<00:01:19.260> stack<00:01:19.740> AKA<00:01:20.280> you<00:01:20.580> just<00:01:20.759> watched 00:01:21.050 --> 00:01:21.060 align:start position:0% of the op stack AKA you just watched 00:01:21.060 --> 00:01:22.789 align:start position:0% of the op stack AKA you just watched Carl's<00:01:21.420> talk<00:01:21.600> and<00:01:22.200> now<00:01:22.380> you<00:01:22.560> want<00:01:22.680> to 00:01:22.789 --> 00:01:22.799 align:start position:0% Carl's talk and now you want to 00:01:22.799 --> 00:01:24.350 align:start position:0% Carl's talk and now you want to understand<00:01:23.040> how<00:01:23.520> this<00:01:23.640> whole<00:01:23.820> modular<00:01:24.119> roll 00:01:24.350 --> 00:01:24.360 align:start position:0% understand how this whole modular roll 00:01:24.360 --> 00:01:26.350 align:start position:0% understand how this whole modular roll up<00:01:24.540> thing<00:01:24.720> actually<00:01:24.960> works 00:01:26.350 --> 00:01:26.360 align:start position:0% up thing actually works 00:01:26.360 --> 00:01:29.690 align:start position:0% up thing actually works okay<00:01:27.360> all<00:01:27.780> right<00:01:27.960> let's<00:01:28.140> go 00:01:29.690 --> 00:01:29.700 align:start position:0% okay all right let's go 00:01:29.700 --> 00:01:31.609 align:start position:0% okay all right let's go um<00:01:29.759> we're<00:01:29.939> gonna<00:01:30.060> do<00:01:30.299> drawings<00:01:30.900> we<00:01:31.200> always<00:01:31.320> do 00:01:31.609 --> 00:01:31.619 align:start position:0% um we're gonna do drawings we always do 00:01:31.619 --> 00:01:34.070 align:start position:0% um we're gonna do drawings we always do silly<00:01:32.220> drawings<00:01:32.580> uh<00:01:33.060> in<00:01:33.240> these<00:01:33.479> talks<00:01:33.840> so<00:01:33.960> here 00:01:34.070 --> 00:01:34.080 align:start position:0% silly drawings uh in these talks so here 00:01:34.080 --> 00:01:36.230 align:start position:0% silly drawings uh in these talks so here we<00:01:34.259> go<00:01:34.400> uh<00:01:35.400> first<00:01:35.579> I<00:01:35.759> want<00:01:35.880> to<00:01:36.000> give<00:01:36.060> some 00:01:36.230 --> 00:01:36.240 align:start position:0% we go uh first I want to give some 00:01:36.240 --> 00:01:37.969 align:start position:0% we go uh first I want to give some context<00:01:36.659> so<00:01:37.079> I'm<00:01:37.439> going<00:01:37.560> to<00:01:37.619> be<00:01:37.740> talking<00:01:37.860> about 00:01:37.969 --> 00:01:37.979 align:start position:0% context so I'm going to be talking about 00:01:37.979 --> 00:01:40.730 align:start position:0% context so I'm going to be talking about the<00:01:38.280> theory<00:01:38.759> behind<00:01:39.540> modular<00:01:40.200> roll-up 00:01:40.730 --> 00:01:40.740 align:start position:0% the theory behind modular roll-up 00:01:40.740 --> 00:01:42.710 align:start position:0% the theory behind modular roll-up architecture 00:01:42.710 --> 00:01:42.720 align:start position:0% architecture 00:01:42.720 --> 00:01:45.950 align:start position:0% architecture stack<00:01:43.320> is<00:01:43.860> a<00:01:44.159> specific<00:01:44.520> software<00:01:45.299> stack<00:01:45.540> that 00:01:45.950 --> 00:01:45.960 align:start position:0% stack is a specific software stack that 00:01:45.960 --> 00:01:47.810 align:start position:0% stack is a specific software stack that turns<00:01:46.320> this<00:01:46.500> Theory<00:01:46.860> into<00:01:47.159> practice<00:01:47.460> right 00:01:47.810 --> 00:01:47.820 align:start position:0% turns this Theory into practice right 00:01:47.820 --> 00:01:49.969 align:start position:0% turns this Theory into practice right this<00:01:48.060> is<00:01:48.180> about<00:01:48.299> taking<00:01:48.659> that<00:01:49.020> theory<00:01:49.380> and 00:01:49.969 --> 00:01:49.979 align:start position:0% this is about taking that theory and 00:01:49.979 --> 00:01:52.429 align:start position:0% this is about taking that theory and turning<00:01:50.280> into<00:01:50.659> specific<00:01:51.659> software 00:01:52.429 --> 00:01:52.439 align:start position:0% turning into specific software 00:01:52.439 --> 00:01:55.190 align:start position:0% turning into specific software components<00:01:53.159> that<00:01:53.820> you<00:01:54.060> can<00:01:54.240> then<00:01:54.479> use<00:01:54.840> to 00:01:55.190 --> 00:01:55.200 align:start position:0% components that you can then use to 00:01:55.200 --> 00:01:57.770 align:start position:0% components that you can then use to build<00:01:55.439> modular<00:01:55.920> chains 00:01:57.770 --> 00:01:57.780 align:start position:0% build modular chains 00:01:57.780 --> 00:01:59.149 align:start position:0% build modular chains um<00:01:57.840> and<00:01:58.079> I<00:01:58.259> just<00:01:58.380> don't<00:01:58.500> like<00:01:58.680> talking<00:01:58.920> about 00:01:59.149 --> 00:01:59.159 align:start position:0% um and I just don't like talking about 00:01:59.159 --> 00:02:01.310 align:start position:0% um and I just don't like talking about Theory<00:01:59.579> alone<00:01:59.759> I<00:02:00.119> think<00:02:00.180> Theory<00:02:00.540> alone<00:02:00.720> is<00:02:01.140> not 00:02:01.310 --> 00:02:01.320 align:start position:0% Theory alone I think Theory alone is not 00:02:01.320 --> 00:02:03.350 align:start position:0% Theory alone I think Theory alone is not very<00:02:01.439> useful<00:02:01.799> unless<00:02:02.100> you<00:02:02.280> ground<00:02:02.520> it<00:02:02.820> and<00:02:03.240> so 00:02:03.350 --> 00:02:03.360 align:start position:0% very useful unless you ground it and so 00:02:03.360 --> 00:02:05.149 align:start position:0% very useful unless you ground it and so I'm<00:02:03.479> going<00:02:03.600> to<00:02:03.659> be<00:02:03.780> using<00:02:04.200> this<00:02:04.380> stack<00:02:04.680> to<00:02:04.979> keep 00:02:05.149 --> 00:02:05.159 align:start position:0% I'm going to be using this stack to keep 00:02:05.159 --> 00:02:06.530 align:start position:0% I'm going to be using this stack to keep the<00:02:05.340> talk<00:02:05.460> grounded<00:02:05.939> right<00:02:06.119> I'm<00:02:06.299> going<00:02:06.420> to<00:02:06.479> be 00:02:06.530 --> 00:02:06.540 align:start position:0% the talk grounded right I'm going to be 00:02:06.540 --> 00:02:08.930 align:start position:0% the talk grounded right I'm going to be using<00:02:06.840> the<00:02:07.079> in<00:02:07.320> the<00:02:07.860> abstractions<00:02:08.459> that<00:02:08.700> we 00:02:08.930 --> 00:02:08.940 align:start position:0% using the in the abstractions that we 00:02:08.940 --> 00:02:10.910 align:start position:0% using the in the abstractions that we came<00:02:09.119> up<00:02:09.300> with<00:02:09.479> in<00:02:09.959> the<00:02:10.080> op<00:02:10.200> stack<00:02:10.619> to<00:02:10.800> keep 00:02:10.910 --> 00:02:10.920 align:start position:0% came up with in the op stack to keep 00:02:10.920 --> 00:02:12.290 align:start position:0% came up with in the op stack to keep things<00:02:11.099> grounded 00:02:12.290 --> 00:02:12.300 align:start position:0% things grounded 00:02:12.300 --> 00:02:13.729 align:start position:0% things grounded I'm<00:02:12.599> also<00:02:12.780> going<00:02:12.900> to<00:02:12.900> use<00:02:13.020> typescript<00:02:13.379> types 00:02:13.729 --> 00:02:13.739 align:start position:0% I'm also going to use typescript types 00:02:13.739 --> 00:02:15.530 align:start position:0% I'm also going to use typescript types to<00:02:13.860> represent<00:02:14.220> things<00:02:14.400> typescript<00:02:15.180> is<00:02:15.360> god 00:02:15.530 --> 00:02:15.540 align:start position:0% to represent things typescript is god 00:02:15.540 --> 00:02:17.809 align:start position:0% to represent things typescript is god tier<00:02:15.780> don't<00:02:16.020> at<00:02:16.200> me<00:02:16.379> here<00:02:17.280> is<00:02:17.400> typescript 00:02:17.809 --> 00:02:17.819 align:start position:0% tier don't at me here is typescript 00:02:17.819 --> 00:02:19.970 align:start position:0% tier don't at me here is typescript ascending<00:02:18.420> into<00:02:18.540> heaven<00:02:18.959> because<00:02:19.379> truly 00:02:19.970 --> 00:02:19.980 align:start position:0% ascending into heaven because truly 00:02:19.980 --> 00:02:22.490 align:start position:0% ascending into heaven because truly greatest<00:02:20.340> language<00:02:20.640> of<00:02:20.879> all<00:02:21.060> time<00:02:21.260> I<00:02:22.260> hope<00:02:22.379> you 00:02:22.490 --> 00:02:22.500 align:start position:0% greatest language of all time I hope you 00:02:22.500 --> 00:02:24.830 align:start position:0% greatest language of all time I hope you enjoy<00:02:22.800> it<00:02:22.920> let's<00:02:23.040> go<00:02:23.280> all<00:02:23.940> right<00:02:24.120> so<00:02:24.420> modular 00:02:24.830 --> 00:02:24.840 align:start position:0% enjoy it let's go all right so modular 00:02:24.840 --> 00:02:27.229 align:start position:0% enjoy it let's go all right so modular rollups<00:02:25.319> 101<00:02:25.680> which 00:02:27.229 --> 00:02:27.239 align:start position:0% rollups 101 which 00:02:27.239 --> 00:02:28.970 align:start position:0% rollups 101 which lost<00:02:27.660> the<00:02:27.900> money<00:02:28.020> oh<00:02:28.260> there<00:02:28.379> we<00:02:28.500> go<00:02:28.620> we<00:02:28.739> get<00:02:28.860> it 00:02:28.970 --> 00:02:28.980 align:start position:0% lost the money oh there we go we get it 00:02:28.980 --> 00:02:29.809 align:start position:0% lost the money oh there we go we get it back 00:02:29.809 --> 00:02:29.819 align:start position:0% back 00:02:29.819 --> 00:02:31.970 align:start position:0% back um<00:02:29.940> give<00:02:30.120> some<00:02:30.360> brief<00:02:30.660> history<00:02:30.840> back<00:02:31.440> in<00:02:31.560> 2020 00:02:31.970 --> 00:02:31.980 align:start position:0% um give some brief history back in 2020 00:02:31.980 --> 00:02:34.190 align:start position:0% um give some brief history back in 2020 everyone<00:02:32.400> was<00:02:32.700> building<00:02:32.940> monolithic<00:02:33.720> rollups 00:02:34.190 --> 00:02:34.200 align:start position:0% everyone was building monolithic rollups 00:02:34.200 --> 00:02:35.990 align:start position:0% everyone was building monolithic rollups this<00:02:34.319> is<00:02:34.440> what<00:02:34.620> they<00:02:34.739> looked<00:02:35.040> like<00:02:35.160> Beefcake 00:02:35.990 --> 00:02:36.000 align:start position:0% this is what they looked like Beefcake 00:02:36.000 --> 00:02:38.630 align:start position:0% this is what they looked like Beefcake Roll-Ups<00:02:36.599> really<00:02:37.200> absolutely<00:02:38.099> ripped 00:02:38.630 --> 00:02:38.640 align:start position:0% Roll-Ups really absolutely ripped 00:02:38.640 --> 00:02:40.970 align:start position:0% Roll-Ups really absolutely ripped six-pack<00:02:39.120> abs<00:02:39.480> roll<00:02:39.660> ups<00:02:39.959> it<00:02:40.080> was<00:02:40.200> one<00:02:40.620> giant 00:02:40.970 --> 00:02:40.980 align:start position:0% six-pack abs roll ups it was one giant 00:02:40.980 --> 00:02:43.430 align:start position:0% six-pack abs roll ups it was one giant code<00:02:41.220> base<00:02:41.519> and<00:02:42.480> it<00:02:42.720> was<00:02:42.840> really<00:02:43.080> hard<00:02:43.319> to 00:02:43.430 --> 00:02:43.440 align:start position:0% code base and it was really hard to 00:02:43.440 --> 00:02:45.110 align:start position:0% code base and it was really hard to understand<00:02:43.620> where<00:02:44.099> the<00:02:44.280> separations<00:02:44.760> were 00:02:45.110 --> 00:02:45.120 align:start position:0% understand where the separations were 00:02:45.120 --> 00:02:48.170 align:start position:0% understand where the separations were and<00:02:45.300> what<00:02:45.599> what<00:02:45.900> a<00:02:46.080> data<00:02:46.319> availability<00:02:46.739> mean 00:02:48.170 --> 00:02:48.180 align:start position:0% and what what a data availability mean 00:02:48.180 --> 00:02:50.210 align:start position:0% and what what a data availability mean um<00:02:48.300> basically<00:02:48.959> all<00:02:49.319> the<00:02:49.500> everything<00:02:49.860> was 00:02:50.210 --> 00:02:50.220 align:start position:0% um basically all the everything was 00:02:50.220 --> 00:02:52.610 align:start position:0% um basically all the everything was defined<00:02:50.760> and<00:02:51.000> limited<00:02:51.420> by<00:02:51.660> our<00:02:51.840> proof<00:02:52.200> systems 00:02:52.610 --> 00:02:52.620 align:start position:0% defined and limited by our proof systems 00:02:52.620 --> 00:02:54.410 align:start position:0% defined and limited by our proof systems right<00:02:52.800> so<00:02:53.040> we<00:02:53.220> would<00:02:53.340> we<00:02:53.700> would<00:02:53.879> we<00:02:54.180> were<00:02:54.300> like 00:02:54.410 --> 00:02:54.420 align:start position:0% right so we would we would we were like 00:02:54.420 --> 00:02:57.170 align:start position:0% right so we would we would we were like okay<00:02:54.660> what<00:02:55.080> is<00:02:55.200> a<00:02:55.319> roll-up<00:02:55.620> well<00:02:55.920> uh<00:02:56.760> we<00:02:56.940> an 00:02:57.170 --> 00:02:57.180 align:start position:0% okay what is a roll-up well uh we an 00:02:57.180 --> 00:02:58.670 align:start position:0% okay what is a roll-up well uh we an optimistic<00:02:57.660> roll<00:02:57.780> up<00:02:57.959> we<00:02:58.080> have<00:02:58.200> to<00:02:58.260> build<00:02:58.379> this 00:02:58.670 --> 00:02:58.680 align:start position:0% optimistic roll up we have to build this 00:02:58.680 --> 00:03:00.830 align:start position:0% optimistic roll up we have to build this this<00:02:59.040> this<00:02:59.160> fault<00:02:59.700> proof<00:03:00.000> so<00:03:00.239> we're<00:03:00.599> going<00:03:00.780> to 00:03:00.830 --> 00:03:00.840 align:start position:0% this this fault proof so we're going to 00:03:00.840 --> 00:03:02.390 align:start position:0% this this fault proof so we're going to build<00:03:00.959> default<00:03:01.379> proof 00:03:02.390 --> 00:03:02.400 align:start position:0% build default proof 00:03:02.400 --> 00:03:03.229 align:start position:0% build default proof um<00:03:02.459> and<00:03:02.640> then<00:03:02.700> we're<00:03:02.819> going<00:03:02.940> to<00:03:03.000> figure<00:03:03.120> out 00:03:03.229 --> 00:03:03.239 align:start position:0% um and then we're going to figure out 00:03:03.239 --> 00:03:05.449 align:start position:0% um and then we're going to figure out how<00:03:03.420> to<00:03:03.480> make<00:03:03.599> the<00:03:03.780> system<00:03:03.959> work<00:03:04.379> like<00:03:04.860> the<00:03:05.040> evm 00:03:05.449 --> 00:03:05.459 align:start position:0% how to make the system work like the evm 00:03:05.459 --> 00:03:07.670 align:start position:0% how to make the system work like the evm inside<00:03:05.760> of<00:03:06.060> a<00:03:06.120> functioning<00:03:06.540> fall<00:03:06.720> proof<00:03:07.140> and 00:03:07.670 --> 00:03:07.680 align:start position:0% inside of a functioning fall proof and 00:03:07.680 --> 00:03:09.770 align:start position:0% inside of a functioning fall proof and and<00:03:07.860> we<00:03:08.160> did<00:03:08.340> that<00:03:08.459> because<00:03:08.760> we<00:03:09.120> had<00:03:09.239> no<00:03:09.599> clue 00:03:09.770 --> 00:03:09.780 align:start position:0% and we did that because we had no clue 00:03:09.780 --> 00:03:11.149 align:start position:0% and we did that because we had no clue what<00:03:09.900> we<00:03:10.080> were<00:03:10.200> actually<00:03:10.379> doing<00:03:10.560> we<00:03:10.800> had<00:03:10.920> no 00:03:11.149 --> 00:03:11.159 align:start position:0% what we were actually doing we had no 00:03:11.159 --> 00:03:12.949 align:start position:0% what we were actually doing we had no clue<00:03:11.340> what<00:03:11.400> Roll-Ups<00:03:11.879> really<00:03:12.060> were<00:03:12.300> this<00:03:12.840> was 00:03:12.949 --> 00:03:12.959 align:start position:0% clue what Roll-Ups really were this was 00:03:12.959 --> 00:03:15.050 align:start position:0% clue what Roll-Ups really were this was us<00:03:13.140> how<00:03:13.440> do<00:03:13.560> we<00:03:13.680> roll<00:03:13.860> up<00:03:14.099> who<00:03:14.519> knows<00:03:14.819> let's 00:03:15.050 --> 00:03:15.060 align:start position:0% us how do we roll up who knows let's 00:03:15.060 --> 00:03:16.790 align:start position:0% us how do we roll up who knows let's just<00:03:15.239> build<00:03:15.480> something<00:03:15.840> oh<00:03:16.260> yeah<00:03:16.379> that's<00:03:16.620> what 00:03:16.790 --> 00:03:16.800 align:start position:0% just build something oh yeah that's what 00:03:16.800 --> 00:03:19.009 align:start position:0% just build something oh yeah that's what we<00:03:16.980> did<00:03:17.159> mental<00:03:18.000> models<00:03:18.360> are<00:03:18.599> really<00:03:18.780> really 00:03:19.009 --> 00:03:19.019 align:start position:0% we did mental models are really really 00:03:19.019 --> 00:03:20.630 align:start position:0% we did mental models are really really important<00:03:19.560> if<00:03:19.860> you<00:03:19.920> don't<00:03:20.099> know<00:03:20.280> what<00:03:20.519> you're 00:03:20.630 --> 00:03:20.640 align:start position:0% important if you don't know what you're 00:03:20.640 --> 00:03:22.850 align:start position:0% important if you don't know what you're building<00:03:20.879> you're<00:03:21.480> gonna<00:03:21.659> build<00:03:21.900> it<00:03:22.140> wrong 00:03:22.850 --> 00:03:22.860 align:start position:0% building you're gonna build it wrong 00:03:22.860 --> 00:03:25.070 align:start position:0% building you're gonna build it wrong as<00:03:23.340> an<00:03:23.519> aside<00:03:23.819> I<00:03:24.060> think<00:03:24.180> this<00:03:24.360> is<00:03:24.480> funny<00:03:24.659> you 00:03:25.070 --> 00:03:25.080 align:start position:0% as an aside I think this is funny you 00:03:25.080 --> 00:03:26.270 align:start position:0% as an aside I think this is funny you know<00:03:25.140> like<00:03:25.319> I've<00:03:25.620> been<00:03:25.739> working<00:03:25.920> on<00:03:26.159> this 00:03:26.270 --> 00:03:26.280 align:start position:0% know like I've been working on this 00:03:26.280 --> 00:03:27.830 align:start position:0% know like I've been working on this stuff<00:03:26.459> probably<00:03:26.700> for<00:03:27.000> like<00:03:27.120> five<00:03:27.360> years<00:03:27.540> now 00:03:27.830 --> 00:03:27.840 align:start position:0% stuff probably for like five years now 00:03:27.840 --> 00:03:30.290 align:start position:0% stuff probably for like five years now and<00:03:28.500> every<00:03:28.680> six<00:03:28.920> months<00:03:29.280> we<00:03:29.819> sit<00:03:30.000> there<00:03:30.180> and 00:03:30.290 --> 00:03:30.300 align:start position:0% and every six months we sit there and 00:03:30.300 --> 00:03:31.670 align:start position:0% and every six months we sit there and we're<00:03:30.420> like<00:03:30.599> ah 00:03:31.670 --> 00:03:31.680 align:start position:0% we're like ah 00:03:31.680 --> 00:03:33.530 align:start position:0% we're like ah it<00:03:32.099> actually<00:03:32.280> works<00:03:32.640> completely<00:03:33.120> differently 00:03:33.530 --> 00:03:33.540 align:start position:0% it actually works completely differently 00:03:33.540 --> 00:03:35.210 align:start position:0% it actually works completely differently from<00:03:33.840> how<00:03:33.959> we<00:03:34.080> thought<00:03:34.260> it<00:03:34.379> works<00:03:34.680> like<00:03:34.920> the 00:03:35.210 --> 00:03:35.220 align:start position:0% from how we thought it works like the 00:03:35.220 --> 00:03:36.589 align:start position:0% from how we thought it works like the other<00:03:35.340> day<00:03:35.459> Carl<00:03:35.760> and<00:03:36.000> I<00:03:36.120> are<00:03:36.239> sitting<00:03:36.480> there 00:03:36.589 --> 00:03:36.599 align:start position:0% other day Carl and I are sitting there 00:03:36.599 --> 00:03:39.410 align:start position:0% other day Carl and I are sitting there and<00:03:36.720> we're<00:03:36.840> like<00:03:37.019> oh<00:03:37.620> withdrawals<00:03:38.459> are<00:03:38.819> just 00:03:39.410 --> 00:03:39.420 align:start position:0% and we're like oh withdrawals are just 00:03:39.420 --> 00:03:41.270 align:start position:0% and we're like oh withdrawals are just totally<00:03:39.840> not<00:03:40.080> what<00:03:40.319> we<00:03:40.440> thought<00:03:40.560> withdrawals 00:03:41.270 --> 00:03:41.280 align:start position:0% totally not what we thought withdrawals 00:03:41.280 --> 00:03:43.850 align:start position:0% totally not what we thought withdrawals are<00:03:41.459> so<00:03:42.180> it's<00:03:42.659> crazy<00:03:42.900> it's<00:03:43.319> just<00:03:43.440> interesting 00:03:43.850 --> 00:03:43.860 align:start position:0% are so it's crazy it's just interesting 00:03:43.860 --> 00:03:45.589 align:start position:0% are so it's crazy it's just interesting I<00:03:44.159> think<00:03:44.280> you<00:03:44.519> know<00:03:44.640> we<00:03:45.120> really<00:03:45.299> don't 00:03:45.589 --> 00:03:45.599 align:start position:0% I think you know we really don't 00:03:45.599 --> 00:03:46.789 align:start position:0% I think you know we really don't understand<00:03:45.840> the<00:03:46.319> problems<00:03:46.560> that<00:03:46.680> we're 00:03:46.789 --> 00:03:46.799 align:start position:0% understand the problems that we're 00:03:46.799 --> 00:03:48.470 align:start position:0% understand the problems that we're working<00:03:46.980> on<00:03:47.159> it<00:03:47.340> takes<00:03:47.519> a<00:03:47.819> long<00:03:47.940> time<00:03:48.180> for<00:03:48.420> us 00:03:48.470 --> 00:03:48.480 align:start position:0% working on it takes a long time for us 00:03:48.480 --> 00:03:50.690 align:start position:0% working on it takes a long time for us to<00:03:48.659> build<00:03:48.840> those<00:03:49.080> mental<00:03:49.440> models<00:03:49.799> and<00:03:50.400> so<00:03:50.519> if 00:03:50.690 --> 00:03:50.700 align:start position:0% to build those mental models and so if 00:03:50.700 --> 00:03:51.949 align:start position:0% to build those mental models and so if you<00:03:50.819> don't<00:03:50.940> understand<00:03:51.120> something<00:03:51.599> that's 00:03:51.949 --> 00:03:51.959 align:start position:0% you don't understand something that's 00:03:51.959 --> 00:03:53.930 align:start position:0% you don't understand something that's okay<00:03:52.200> because<00:03:52.620> not<00:03:52.980> everybody<00:03:53.159> does<00:03:53.519> nobody 00:03:53.930 --> 00:03:53.940 align:start position:0% okay because not everybody does nobody 00:03:53.940 --> 00:03:55.190 align:start position:0% okay because not everybody does nobody really<00:03:54.239> understands<00:03:54.720> what<00:03:54.840> they're<00:03:55.019> working 00:03:55.190 --> 00:03:55.200 align:start position:0% really understands what they're working 00:03:55.200 --> 00:03:56.869 align:start position:0% really understands what they're working on<00:03:55.440> even<00:03:55.920> when<00:03:56.099> you're<00:03:56.220> working<00:03:56.459> on<00:03:56.640> it<00:03:56.760> and 00:03:56.869 --> 00:03:56.879 align:start position:0% on even when you're working on it and 00:03:56.879 --> 00:03:59.750 align:start position:0% on even when you're working on it and building<00:03:57.060> a<00:03:57.239> whole<00:03:57.360> protocol<00:03:57.659> out<00:03:57.900> of<00:03:58.019> it 00:03:59.750 --> 00:03:59.760 align:start position:0% building a whole protocol out of it 00:03:59.760 --> 00:04:01.610 align:start position:0% building a whole protocol out of it um<00:03:59.819> then<00:04:00.180> we<00:04:00.360> finally<00:04:00.659> got<00:04:00.900> it<00:04:01.080> so<00:04:01.379> between 00:04:01.610 --> 00:04:01.620 align:start position:0% um then we finally got it so between 00:04:01.620 --> 00:04:04.430 align:start position:0% um then we finally got it so between 2021<00:04:02.340> 2022<00:04:03.180> we<00:04:03.780> started<00:04:04.080> to<00:04:04.200> really 00:04:04.430 --> 00:04:04.440 align:start position:0% 2021 2022 we started to really 00:04:04.440 --> 00:04:06.949 align:start position:0% 2021 2022 we started to really understand<00:04:04.680> Roll-Ups<00:04:05.400> in<00:04:05.459> more<00:04:05.640> detail 00:04:06.949 --> 00:04:06.959 align:start position:0% understand Roll-Ups in more detail 00:04:06.959 --> 00:04:09.050 align:start position:0% understand Roll-Ups in more detail the<00:04:07.560> first<00:04:07.680> key<00:04:08.040> realization<00:04:08.519> was<00:04:08.819> that 00:04:09.050 --> 00:04:09.060 align:start position:0% the first key realization was that 00:04:09.060 --> 00:04:11.030 align:start position:0% the first key realization was that proofs<00:04:09.540> should<00:04:09.959> be<00:04:10.080> execute<00:04:10.560> or<00:04:10.739> should<00:04:10.920> be 00:04:11.030 --> 00:04:11.040 align:start position:0% proofs should be execute or should be 00:04:11.040 --> 00:04:13.550 align:start position:0% proofs should be execute or should be separated<00:04:11.519> from<00:04:12.180> execution<00:04:12.720> we<00:04:13.200> should<00:04:13.379> not 00:04:13.550 --> 00:04:13.560 align:start position:0% separated from execution we should not 00:04:13.560 --> 00:04:16.129 align:start position:0% separated from execution we should not allow<00:04:13.980> the<00:04:14.220> structure<00:04:14.580> of<00:04:14.700> the<00:04:14.939> proof<00:04:15.360> to 00:04:16.129 --> 00:04:16.139 align:start position:0% allow the structure of the proof to 00:04:16.139 --> 00:04:18.710 align:start position:0% allow the structure of the proof to control<00:04:16.680> the<00:04:17.459> behavior<00:04:17.820> of<00:04:18.120> our<00:04:18.239> execution 00:04:18.710 --> 00:04:18.720 align:start position:0% control the behavior of our execution 00:04:18.720 --> 00:04:21.050 align:start position:0% control the behavior of our execution layer<00:04:19.139> and<00:04:19.919> this<00:04:20.040> was<00:04:20.220> you<00:04:20.519> know<00:04:20.579> so<00:04:20.699> here<00:04:20.940> we 00:04:21.050 --> 00:04:21.060 align:start position:0% layer and this was you know so here we 00:04:21.060 --> 00:04:22.850 align:start position:0% layer and this was you know so here we go<00:04:21.239> you<00:04:21.780> know<00:04:21.840> with<00:04:22.019> the<00:04:22.199> power<00:04:22.320> of<00:04:22.500> mental 00:04:22.850 --> 00:04:22.860 align:start position:0% go you know with the power of mental 00:04:22.860 --> 00:04:26.450 align:start position:0% go you know with the power of mental models<00:04:23.220> I<00:04:23.759> Vanquish<00:04:24.240> the<00:04:24.860> monolithic<00:04:25.860> rollups 00:04:26.450 --> 00:04:26.460 align:start position:0% models I Vanquish the monolithic rollups 00:04:26.460 --> 00:04:28.909 align:start position:0% models I Vanquish the monolithic rollups oh<00:04:26.699> oh<00:04:27.120> Jesus<00:04:27.600> oh<00:04:27.900> they<00:04:28.139> got<00:04:28.259> ripped<00:04:28.620> in<00:04:28.740> half 00:04:28.909 --> 00:04:28.919 align:start position:0% oh oh Jesus oh they got ripped in half 00:04:28.919 --> 00:04:30.350 align:start position:0% oh oh Jesus oh they got ripped in half oh<00:04:29.220> no 00:04:30.350 --> 00:04:30.360 align:start position:0% oh no 00:04:30.360 --> 00:04:32.030 align:start position:0% oh no um<00:04:30.479> and<00:04:30.840> so<00:04:31.020> then<00:04:31.320> we<00:04:31.440> got<00:04:31.620> stuff<00:04:31.860> like 00:04:32.030 --> 00:04:32.040 align:start position:0% um and so then we got stuff like 00:04:32.040 --> 00:04:33.830 align:start position:0% um and so then we got stuff like optimisms<00:04:32.699> evm<00:04:33.060> equivalence<00:04:33.479> upgrade 00:04:33.830 --> 00:04:33.840 align:start position:0% optimisms evm equivalence upgrade 00:04:33.840 --> 00:04:36.469 align:start position:0% optimisms evm equivalence upgrade arbitrims<00:04:34.560> Nitro<00:04:34.919> upgrade<00:04:35.340> all<00:04:36.060> the<00:04:36.240> same 00:04:36.469 --> 00:04:36.479 align:start position:0% arbitrims Nitro upgrade all the same 00:04:36.479 --> 00:04:39.230 align:start position:0% arbitrims Nitro upgrade all the same idea<00:04:36.840> let's<00:04:37.199> separate<00:04:37.680> proofs<00:04:38.220> let's<00:04:38.820> just 00:04:39.230 --> 00:04:39.240 align:start position:0% idea let's separate proofs let's just 00:04:39.240 --> 00:04:42.110 align:start position:0% idea let's separate proofs let's just run<00:04:39.600> the<00:04:39.840> evm<00:04:40.320> as<00:04:41.040> built<00:04:41.460> with<00:04:41.759> minimal 00:04:42.110 --> 00:04:42.120 align:start position:0% run the evm as built with minimal 00:04:42.120 --> 00:04:43.909 align:start position:0% run the evm as built with minimal modifications<00:04:42.660> to<00:04:43.080> make<00:04:43.139> it<00:04:43.320> work<00:04:43.500> like<00:04:43.740> a 00:04:43.909 --> 00:04:43.919 align:start position:0% modifications to make it work like a 00:04:43.919 --> 00:04:46.070 align:start position:0% modifications to make it work like a roll-up<00:04:44.220> and<00:04:44.880> have<00:04:45.000> the<00:04:45.180> proofs<00:04:45.540> be<00:04:45.780> so 00:04:46.070 --> 00:04:46.080 align:start position:0% roll-up and have the proofs be so 00:04:46.080 --> 00:04:48.050 align:start position:0% roll-up and have the proofs be so General<00:04:46.320> that<00:04:47.040> it<00:04:47.220> doesn't<00:04:47.340> matter<00:04:47.639> what<00:04:47.940> you 00:04:48.050 --> 00:04:48.060 align:start position:0% General that it doesn't matter what you 00:04:48.060 --> 00:04:49.850 align:start position:0% General that it doesn't matter what you can<00:04:48.180> what<00:04:48.479> you<00:04:48.660> do<00:04:48.780> on<00:04:49.020> the<00:04:49.139> execution<00:04:49.500> layer 00:04:49.850 --> 00:04:49.860 align:start position:0% can what you do on the execution layer 00:04:49.860 --> 00:04:52.070 align:start position:0% can what you do on the execution layer you<00:04:49.979> can<00:04:50.100> do<00:04:50.220> whatever<00:04:50.340> you<00:04:50.580> want 00:04:52.070 --> 00:04:52.080 align:start position:0% you can do whatever you want 00:04:52.080 --> 00:04:54.230 align:start position:0% you can do whatever you want all<00:04:52.620> right<00:04:52.800> then<00:04:53.220> we<00:04:53.400> also<00:04:53.699> came<00:04:53.820> to<00:04:53.940> realize 00:04:54.230 --> 00:04:54.240 align:start position:0% all right then we also came to realize 00:04:54.240 --> 00:04:55.249 align:start position:0% all right then we also came to realize that<00:04:54.360> we<00:04:54.479> could<00:04:54.600> break<00:04:54.720> out<00:04:54.900> the<00:04:55.080> data 00:04:55.249 --> 00:04:55.259 align:start position:0% that we could break out the data 00:04:55.259 --> 00:04:57.050 align:start position:0% that we could break out the data availability<00:04:55.560> layer 00:04:57.050 --> 00:04:57.060 align:start position:0% availability layer 00:04:57.060 --> 00:05:00.530 align:start position:0% availability layer um<00:04:57.120> bra<00:04:57.600> right<00:04:57.860> so<00:04:58.860> uh<00:04:59.400> you<00:04:59.580> know<00:04:59.699> we<00:04:59.940> had<00:05:00.120> got<00:05:00.419> a 00:05:00.530 --> 00:05:00.540 align:start position:0% um bra right so uh you know we had got a 00:05:00.540 --> 00:05:02.090 align:start position:0% um bra right so uh you know we had got a fork<00:05:00.780> and<00:05:00.900> it<00:05:01.020> added<00:05:01.259> a<00:05:01.320> data<00:05:01.800> availability 00:05:02.090 --> 00:05:02.100 align:start position:0% fork and it added a data availability 00:05:02.100 --> 00:05:04.249 align:start position:0% fork and it added a data availability committee<00:05:02.639> arbitrim<00:05:03.419> releases<00:05:03.780> Nova<00:05:04.080> with 00:05:04.249 --> 00:05:04.259 align:start position:0% committee arbitrim releases Nova with 00:05:04.259 --> 00:05:05.510 align:start position:0% committee arbitrim releases Nova with the<00:05:04.320> data<00:05:04.500> availability<00:05:04.800> committee<00:05:05.220> this<00:05:05.460> is 00:05:05.510 --> 00:05:05.520 align:start position:0% the data availability committee this is 00:05:05.520 --> 00:05:07.430 align:start position:0% the data availability committee this is all<00:05:05.639> a<00:05:05.820> realization<00:05:06.240> that<00:05:06.840> we<00:05:06.960> can<00:05:07.080> also 00:05:07.430 --> 00:05:07.440 align:start position:0% all a realization that we can also 00:05:07.440 --> 00:05:09.290 align:start position:0% all a realization that we can also separate<00:05:07.860> data<00:05:08.220> availability<00:05:08.520> right<00:05:08.880> we<00:05:09.180> can 00:05:09.290 --> 00:05:09.300 align:start position:0% separate data availability right we can 00:05:09.300 --> 00:05:11.629 align:start position:0% separate data availability right we can we<00:05:09.660> can<00:05:09.840> include<00:05:10.259> a<00:05:10.919> different<00:05:11.040> thing<00:05:11.340> that's 00:05:11.629 --> 00:05:11.639 align:start position:0% we can include a different thing that's 00:05:11.639 --> 00:05:13.430 align:start position:0% we can include a different thing that's not<00:05:11.880> ethereum<00:05:12.360> and<00:05:12.600> these<00:05:12.780> systems<00:05:13.080> can<00:05:13.259> still 00:05:13.430 --> 00:05:13.440 align:start position:0% not ethereum and these systems can still 00:05:13.440 --> 00:05:16.850 align:start position:0% not ethereum and these systems can still work<00:05:13.740> with<00:05:14.340> different<00:05:14.520> security<00:05:14.940> properties 00:05:16.850 --> 00:05:16.860 align:start position:0% work with different security properties 00:05:16.860 --> 00:05:18.590 align:start position:0% work with different security properties and<00:05:17.280> so<00:05:17.460> Roll-Ups<00:05:17.940> were<00:05:18.060> coming<00:05:18.180> modular 00:05:18.590 --> 00:05:18.600 align:start position:0% and so Roll-Ups were coming modular 00:05:18.600 --> 00:05:21.230 align:start position:0% and so Roll-Ups were coming modular right<00:05:18.960> we<00:05:19.680> start<00:05:19.860> to<00:05:20.040> see<00:05:20.160> this<00:05:20.400> we<00:05:20.940> generally 00:05:21.230 --> 00:05:21.240 align:start position:0% right we start to see this we generally 00:05:21.240 --> 00:05:22.730 align:start position:0% right we start to see this we generally start<00:05:21.479> to<00:05:21.600> see<00:05:21.720> Roll-Ups<00:05:22.259> beginning<00:05:22.380> to<00:05:22.620> break 00:05:22.730 --> 00:05:22.740 align:start position:0% start to see Roll-Ups beginning to break 00:05:22.740 --> 00:05:24.950 align:start position:0% start to see Roll-Ups beginning to break down<00:05:22.860> into<00:05:23.100> three<00:05:23.400> primary<00:05:23.820> layers<00:05:24.180> if<00:05:24.720> you've 00:05:24.950 --> 00:05:24.960 align:start position:0% down into three primary layers if you've 00:05:24.960 --> 00:05:26.150 align:start position:0% down into three primary layers if you've looked<00:05:25.139> at<00:05:25.259> modular<00:05:25.560> Roll-Ups<00:05:26.039> before 00:05:26.150 --> 00:05:26.160 align:start position:0% looked at modular Roll-Ups before 00:05:26.160 --> 00:05:27.469 align:start position:0% looked at modular Roll-Ups before because<00:05:26.400> people<00:05:26.580> have<00:05:26.759> been<00:05:26.940> screaming<00:05:27.300> about 00:05:27.469 --> 00:05:27.479 align:start position:0% because people have been screaming about 00:05:27.479 --> 00:05:29.029 align:start position:0% because people have been screaming about this<00:05:27.720> for<00:05:28.020> the<00:05:28.139> last<00:05:28.259> year<00:05:28.500> you<00:05:28.740> kind<00:05:28.919> of 00:05:29.029 --> 00:05:29.039 align:start position:0% this for the last year you kind of 00:05:29.039 --> 00:05:30.409 align:start position:0% this for the last year you kind of understand<00:05:29.100> where<00:05:29.520> it's<00:05:29.639> going<00:05:29.759> consensus 00:05:30.409 --> 00:05:30.419 align:start position:0% understand where it's going consensus 00:05:30.419 --> 00:05:32.450 align:start position:0% understand where it's going consensus execution<00:05:31.199> settlement<00:05:31.740> that's<00:05:32.100> the<00:05:32.280> high 00:05:32.450 --> 00:05:32.460 align:start position:0% execution settlement that's the high 00:05:32.460 --> 00:05:34.189 align:start position:0% execution settlement that's the high level<00:05:32.580> idea<00:05:33.120> but<00:05:33.539> that's<00:05:33.660> the<00:05:33.840> high<00:05:34.020> level 00:05:34.189 --> 00:05:34.199 align:start position:0% level idea but that's the high level 00:05:34.199 --> 00:05:35.689 align:start position:0% level idea but that's the high level right<00:05:34.560> isn't<00:05:35.160> that<00:05:35.220> just<00:05:35.400> modular 00:05:35.689 --> 00:05:35.699 align:start position:0% right isn't that just modular 00:05:35.699 --> 00:05:39.469 align:start position:0% right isn't that just modular blockchains<00:05:36.360> yeah<00:05:36.660> in<00:05:36.960> a<00:05:37.080> way<00:05:37.199> but<00:05:37.979> really 00:05:39.469 --> 00:05:39.479 align:start position:0% blockchains yeah in a way but really 00:05:39.479 --> 00:05:41.570 align:start position:0% blockchains yeah in a way but really it's<00:05:39.960> about<00:05:40.139> taking<00:05:40.440> the<00:05:40.740> theory<00:05:41.100> of<00:05:41.280> modular 00:05:41.570 --> 00:05:41.580 align:start position:0% it's about taking the theory of modular 00:05:41.580 --> 00:05:43.730 align:start position:0% it's about taking the theory of modular blockchains<00:05:42.300> and<00:05:42.479> putting<00:05:42.840> it<00:05:43.020> into<00:05:43.440> practice 00:05:43.730 --> 00:05:43.740 align:start position:0% blockchains and putting it into practice 00:05:43.740 --> 00:05:46.129 align:start position:0% blockchains and putting it into practice it's<00:05:44.039> about<00:05:44.220> saying<00:05:44.699> okay<00:05:45.120> let's<00:05:45.720> not<00:05:45.960> just 00:05:46.129 --> 00:05:46.139 align:start position:0% it's about saying okay let's not just 00:05:46.139 --> 00:05:48.409 align:start position:0% it's about saying okay let's not just have<00:05:46.380> charts<00:05:47.039> in<00:05:47.340> a<00:05:47.460> blog<00:05:47.699> post<00:05:47.880> that<00:05:48.180> says 00:05:48.409 --> 00:05:48.419 align:start position:0% have charts in a blog post that says 00:05:48.419 --> 00:05:49.850 align:start position:0% have charts in a blog post that says well<00:05:48.600> if<00:05:48.780> you<00:05:48.960> separate<00:05:49.259> it<00:05:49.380> if<00:05:49.500> you<00:05:49.560> put<00:05:49.740> this 00:05:49.850 --> 00:05:49.860 align:start position:0% well if you separate it if you put this 00:05:49.860 --> 00:05:51.529 align:start position:0% well if you separate it if you put this it<00:05:50.100> could<00:05:50.280> be<00:05:50.400> this<00:05:50.820> thing<00:05:51.000> and<00:05:51.180> if<00:05:51.300> you<00:05:51.419> put 00:05:51.529 --> 00:05:51.539 align:start position:0% it could be this thing and if you put 00:05:51.539 --> 00:05:52.850 align:start position:0% it could be this thing and if you put this<00:05:51.660> it<00:05:51.780> could<00:05:51.900> be<00:05:52.020> a<00:05:52.080> validium<00:05:52.500> and<00:05:52.740> whatever 00:05:52.850 --> 00:05:52.860 align:start position:0% this it could be a validium and whatever 00:05:52.860 --> 00:05:54.950 align:start position:0% this it could be a validium and whatever but<00:05:53.580> actually<00:05:53.759> saying<00:05:54.120> let's<00:05:54.300> define<00:05:54.539> a 00:05:54.950 --> 00:05:54.960 align:start position:0% but actually saying let's define a 00:05:54.960 --> 00:05:58.490 align:start position:0% but actually saying let's define a software<00:05:55.380> stack<00:05:56.220> makes<00:05:56.940> it<00:05:57.120> possible<00:05:57.660> to<00:05:58.320> put 00:05:58.490 --> 00:05:58.500 align:start position:0% software stack makes it possible to put 00:05:58.500 --> 00:06:00.170 align:start position:0% software stack makes it possible to put the<00:05:58.740> things<00:05:58.860> together<00:05:59.160> for<00:05:59.759> the<00:05:59.940> average 00:06:00.170 --> 00:06:00.180 align:start position:0% the things together for the average 00:06:00.180 --> 00:06:01.730 align:start position:0% the things together for the average person<00:06:00.539> to<00:06:00.780> not<00:06:00.960> have<00:06:01.080> to<00:06:01.199> build<00:06:01.320> the<00:06:01.560> whole 00:06:01.730 --> 00:06:01.740 align:start position:0% person to not have to build the whole 00:06:01.740 --> 00:06:03.409 align:start position:0% person to not have to build the whole thing<00:06:01.919> from<00:06:02.160> scratch 00:06:03.409 --> 00:06:03.419 align:start position:0% thing from scratch 00:06:03.419 --> 00:06:05.210 align:start position:0% thing from scratch and<00:06:03.960> it<00:06:04.080> was<00:06:04.199> time<00:06:04.320> to<00:06:04.440> make<00:06:04.560> things<00:06:04.740> official 00:06:05.210 --> 00:06:05.220 align:start position:0% and it was time to make things official 00:06:05.220 --> 00:06:07.909 align:start position:0% and it was time to make things official so<00:06:05.660> this<00:06:06.660> was<00:06:06.780> modular<00:06:07.139> blockchain<00:06:07.620> design 00:06:07.909 --> 00:06:07.919 align:start position:0% so this was modular blockchain design 00:06:07.919 --> 00:06:09.469 align:start position:0% so this was modular blockchain design and<00:06:08.220> being<00:06:08.400> put<00:06:08.580> into<00:06:08.699> practice<00:06:09.000> but<00:06:09.300> the 00:06:09.469 --> 00:06:09.479 align:start position:0% and being put into practice but the 00:06:09.479 --> 00:06:10.969 align:start position:0% and being put into practice but the beginning<00:06:09.600> was<00:06:09.900> very<00:06:10.199> messy<00:06:10.680> and<00:06:10.800> very 00:06:10.969 --> 00:06:10.979 align:start position:0% beginning was very messy and very 00:06:10.979 --> 00:06:12.529 align:start position:0% beginning was very messy and very haphazard<00:06:11.460> right<00:06:11.699> people<00:06:11.940> were<00:06:12.120> kind<00:06:12.360> of<00:06:12.419> just 00:06:12.529 --> 00:06:12.539 align:start position:0% haphazard right people were kind of just 00:06:12.539 --> 00:06:14.330 align:start position:0% haphazard right people were kind of just ripping<00:06:12.960> things<00:06:13.139> out<00:06:13.380> they<00:06:13.919> were<00:06:14.160> kind<00:06:14.220> of 00:06:14.330 --> 00:06:14.340 align:start position:0% ripping things out they were kind of 00:06:14.340 --> 00:06:15.950 align:start position:0% ripping things out they were kind of just<00:06:14.460> tweaking<00:06:14.940> the<00:06:15.180> execution<00:06:15.539> layer<00:06:15.840> and 00:06:15.950 --> 00:06:15.960 align:start position:0% just tweaking the execution layer and 00:06:15.960 --> 00:06:17.270 align:start position:0% just tweaking the execution layer and hoping<00:06:16.259> it<00:06:16.500> worked<00:06:16.740> there<00:06:16.919> wasn't<00:06:17.039> a 00:06:17.270 --> 00:06:17.280 align:start position:0% hoping it worked there wasn't a 00:06:17.280 --> 00:06:19.070 align:start position:0% hoping it worked there wasn't a formality<00:06:17.759> around<00:06:18.000> it<00:06:18.300> so<00:06:18.660> you<00:06:18.840> know<00:06:18.960> what 00:06:19.070 --> 00:06:19.080 align:start position:0% formality around it so you know what 00:06:19.080 --> 00:06:22.370 align:start position:0% formality around it so you know what time<00:06:19.259> it<00:06:19.440> is<00:06:19.560> it's<00:06:20.280> formalization<00:06:20.880> time<00:06:21.380> uh 00:06:22.370 --> 00:06:22.380 align:start position:0% time it is it's formalization time uh 00:06:22.380 --> 00:06:23.870 align:start position:0% time it is it's formalization time uh you<00:06:22.560> know<00:06:22.620> like<00:06:22.800> Loosely<00:06:23.220> formalized<00:06:23.759> because 00:06:23.870 --> 00:06:23.880 align:start position:0% you know like Loosely formalized because 00:06:23.880 --> 00:06:25.430 align:start position:0% you know like Loosely formalized because I<00:06:24.060> never<00:06:24.180> graduated<00:06:24.660> college<00:06:24.960> so<00:06:25.199> I<00:06:25.319> don't 00:06:25.430 --> 00:06:25.440 align:start position:0% I never graduated college so I don't 00:06:25.440 --> 00:06:27.230 align:start position:0% I never graduated college so I don't know<00:06:25.500> how<00:06:25.620> to<00:06:25.740> do<00:06:25.800> that<00:06:25.919> but<00:06:26.220> we're<00:06:26.639> gonna<00:06:26.940> it's 00:06:27.230 --> 00:06:27.240 align:start position:0% know how to do that but we're gonna it's 00:06:27.240 --> 00:06:28.550 align:start position:0% know how to do that but we're gonna it's good<00:06:27.360> enough<00:06:27.539> it's<00:06:27.720> good<00:06:27.960> enough<00:06:28.080> all<00:06:28.380> right 00:06:28.550 --> 00:06:28.560 align:start position:0% good enough it's good enough all right 00:06:28.560 --> 00:06:32.210 align:start position:0% good enough it's good enough all right so<00:06:29.280> here<00:06:29.819> section<00:06:30.360> two<00:06:30.660> now<00:06:31.500> um 00:06:32.210 --> 00:06:32.220 align:start position:0% so here section two now um 00:06:32.220 --> 00:06:33.830 align:start position:0% so here section two now um the<00:06:32.699> section<00:06:32.880> numbers<00:06:33.180> are<00:06:33.539> completely 00:06:33.830 --> 00:06:33.840 align:start position:0% the section numbers are completely 00:06:33.840 --> 00:06:35.270 align:start position:0% the section numbers are completely messed<00:06:34.259> up<00:06:34.319> I<00:06:34.500> just<00:06:34.680> never<00:06:34.800> even<00:06:34.919> got<00:06:35.160> around 00:06:35.270 --> 00:06:35.280 align:start position:0% messed up I just never even got around 00:06:35.280 --> 00:06:37.189 align:start position:0% messed up I just never even got around to<00:06:35.460> fixing<00:06:35.639> it<00:06:35.759> but<00:06:35.880> whatever<00:06:36.000> beep<00:06:36.720> boop<00:06:36.960> bias 00:06:37.189 --> 00:06:37.199 align:start position:0% to fixing it but whatever beep boop bias 00:06:37.199 --> 00:06:38.689 align:start position:0% to fixing it but whatever beep boop bias warning<00:06:37.560> I'm<00:06:38.039> going<00:06:38.160> to<00:06:38.280> use<00:06:38.460> the 00:06:38.689 --> 00:06:38.699 align:start position:0% warning I'm going to use the 00:06:38.699 --> 00:06:39.950 align:start position:0% warning I'm going to use the abstractions<00:06:39.180> that<00:06:39.300> we<00:06:39.360> Define<00:06:39.539> in<00:06:39.720> the<00:06:39.840> op 00:06:39.950 --> 00:06:39.960 align:start position:0% abstractions that we Define in the op 00:06:39.960 --> 00:06:42.409 align:start position:0% abstractions that we Define in the op stack<00:06:40.520> I<00:06:41.520> think<00:06:41.639> these<00:06:41.819> abstractions<00:06:42.300> are 00:06:42.409 --> 00:06:42.419 align:start position:0% stack I think these abstractions are 00:06:42.419 --> 00:06:44.330 align:start position:0% stack I think these abstractions are good<00:06:42.600> there<00:06:43.080> are<00:06:43.199> other<00:06:43.440> abstractions<00:06:44.100> out 00:06:44.330 --> 00:06:44.340 align:start position:0% good there are other abstractions out 00:06:44.340 --> 00:06:45.590 align:start position:0% good there are other abstractions out there<00:06:44.460> but<00:06:44.639> I<00:06:44.759> think<00:06:44.880> the<00:06:44.940> OB<00:06:45.060> Stacks 00:06:45.590 --> 00:06:45.600 align:start position:0% there but I think the OB Stacks 00:06:45.600 --> 00:06:47.270 align:start position:0% there but I think the OB Stacks abstractions<00:06:46.020> are<00:06:46.139> pretty<00:06:46.319> good<00:06:46.500> so<00:06:47.039> deal 00:06:47.270 --> 00:06:47.280 align:start position:0% abstractions are pretty good so deal 00:06:47.280 --> 00:06:49.430 align:start position:0% abstractions are pretty good so deal with<00:06:47.460> it<00:06:47.580> I'm<00:06:47.759> going<00:06:47.880> to<00:06:48.000> use<00:06:48.120> those 00:06:49.430 --> 00:06:49.440 align:start position:0% with it I'm going to use those 00:06:49.440 --> 00:06:50.150 align:start position:0% with it I'm going to use those um 00:06:50.150 --> 00:06:50.160 align:start position:0% um 00:06:50.160 --> 00:06:51.950 align:start position:0% um like<00:06:50.580> I<00:06:50.699> said<00:06:50.819> there<00:06:51.120> are<00:06:51.240> three<00:06:51.539> primary 00:06:51.950 --> 00:06:51.960 align:start position:0% like I said there are three primary 00:06:51.960 --> 00:06:54.110 align:start position:0% like I said there are three primary layers<00:06:52.319> we<00:06:52.560> got<00:06:52.680> consensus<00:06:53.340> inside<00:06:53.819> of 00:06:54.110 --> 00:06:54.120 align:start position:0% layers we got consensus inside of 00:06:54.120 --> 00:06:56.090 align:start position:0% layers we got consensus inside of consensus<00:06:54.539> we<00:06:54.720> got<00:06:54.840> two<00:06:55.080> things<00:06:55.259> what<00:06:55.800> we<00:06:55.919> call 00:06:56.090 --> 00:06:56.100 align:start position:0% consensus we got two things what we call 00:06:56.100 --> 00:06:57.590 align:start position:0% consensus we got two things what we call data<00:06:56.580> availability<00:06:56.880> you've<00:06:57.240> heard<00:06:57.360> of<00:06:57.479> that 00:06:57.590 --> 00:06:57.600 align:start position:0% data availability you've heard of that 00:06:57.600 --> 00:06:59.510 align:start position:0% data availability you've heard of that before<00:06:57.780> derivation<00:06:58.620> you<00:06:58.979> may<00:06:59.100> not<00:06:59.280> have<00:06:59.400> heard 00:06:59.510 --> 00:06:59.520 align:start position:0% before derivation you may not have heard 00:06:59.520 --> 00:07:00.890 align:start position:0% before derivation you may not have heard of<00:06:59.699> that<00:06:59.819> before 00:07:00.890 --> 00:07:00.900 align:start position:0% of that before 00:07:00.900 --> 00:07:03.890 align:start position:0% of that before then<00:07:01.380> execution<00:07:01.919> then<00:07:02.880> settlement 00:07:03.890 --> 00:07:03.900 align:start position:0% then execution then settlement 00:07:03.900 --> 00:07:05.930 align:start position:0% then execution then settlement so<00:07:04.440> let's<00:07:04.680> look<00:07:04.860> at<00:07:05.039> consensus<00:07:05.639> let's 00:07:05.930 --> 00:07:05.940 align:start position:0% so let's look at consensus let's 00:07:05.940 --> 00:07:07.309 align:start position:0% so let's look at consensus let's specifically<00:07:06.600> look<00:07:06.780> at<00:07:06.960> these<00:07:07.199> two 00:07:07.309 --> 00:07:07.319 align:start position:0% specifically look at these two 00:07:07.319 --> 00:07:09.650 align:start position:0% specifically look at these two sub-components<00:07:08.160> we've<00:07:08.819> got<00:07:08.940> data<00:07:09.300> the<00:07:09.419> data 00:07:09.650 --> 00:07:09.660 align:start position:0% sub-components we've got data the data 00:07:09.660 --> 00:07:11.629 align:start position:0% sub-components we've got data the data availability<00:07:09.960> layer<00:07:10.440> and<00:07:11.160> we've<00:07:11.400> got<00:07:11.520> the 00:07:11.629 --> 00:07:11.639 align:start position:0% availability layer and we've got the 00:07:11.639 --> 00:07:14.029 align:start position:0% availability layer and we've got the derivation<00:07:12.060> layer<00:07:12.419> right 00:07:14.029 --> 00:07:14.039 align:start position:0% derivation layer right 00:07:14.039 --> 00:07:16.550 align:start position:0% derivation layer right so<00:07:14.520> what<00:07:14.880> is<00:07:15.120> the<00:07:15.360> data<00:07:15.600> availability<00:07:15.960> layer 00:07:16.550 --> 00:07:16.560 align:start position:0% so what is the data availability layer 00:07:16.560 --> 00:07:18.770 align:start position:0% so what is the data availability layer even<00:07:17.160> all<00:07:17.819> right<00:07:17.819> let's<00:07:18.060> try<00:07:18.240> to<00:07:18.360> formalize 00:07:18.770 --> 00:07:18.780 align:start position:0% even all right let's try to formalize 00:07:18.780 --> 00:07:20.210 align:start position:0% even all right let's try to formalize this<00:07:18.960> a<00:07:19.080> little<00:07:19.199> bit<00:07:19.319> well<00:07:19.800> you<00:07:20.099> know<00:07:20.160> it's 00:07:20.210 --> 00:07:20.220 align:start position:0% this a little bit well you know it's 00:07:20.220 --> 00:07:21.650 align:start position:0% this a little bit well you know it's like<00:07:20.400> the<00:07:20.580> place<00:07:20.699> where<00:07:20.819> you<00:07:21.000> post<00:07:21.120> data<00:07:21.539> right 00:07:21.650 --> 00:07:21.660 align:start position:0% like the place where you post data right 00:07:21.660 --> 00:07:22.790 align:start position:0% like the place where you post data right like<00:07:21.780> how<00:07:21.960> does<00:07:22.080> that<00:07:22.199> actually<00:07:22.380> work<00:07:22.620> so 00:07:22.790 --> 00:07:22.800 align:start position:0% like how does that actually work so 00:07:22.800 --> 00:07:24.110 align:start position:0% like how does that actually work so let's<00:07:22.919> form<00:07:23.099> let's<00:07:23.400> get<00:07:23.580> slightly<00:07:23.940> more 00:07:24.110 --> 00:07:24.120 align:start position:0% let's form let's get slightly more 00:07:24.120 --> 00:07:25.570 align:start position:0% let's form let's get slightly more formal 00:07:25.570 --> 00:07:25.580 align:start position:0% formal 00:07:25.580 --> 00:07:28.070 align:start position:0% formal I<00:07:26.580> like<00:07:26.699> to<00:07:26.880> say<00:07:27.060> and<00:07:27.240> I<00:07:27.419> think<00:07:27.539> a<00:07:27.660> good<00:07:27.780> way<00:07:27.960> to 00:07:28.070 --> 00:07:28.080 align:start position:0% I like to say and I think a good way to 00:07:28.080 --> 00:07:29.450 align:start position:0% I like to say and I think a good way to think<00:07:28.139> of<00:07:28.319> the<00:07:28.440> date<00:07:28.560> availability<00:07:28.979> layer<00:07:29.400> is 00:07:29.450 --> 00:07:29.460 align:start position:0% think of the date availability layer is 00:07:29.460 --> 00:07:31.850 align:start position:0% think of the date availability layer is it's<00:07:29.699> an<00:07:29.880> ordered<00:07:30.240> list<00:07:30.360> of<00:07:30.599> blobs<00:07:31.020> it's<00:07:31.740> just 00:07:31.850 --> 00:07:31.860 align:start position:0% it's an ordered list of blobs it's just 00:07:31.860 --> 00:07:33.710 align:start position:0% it's an ordered list of blobs it's just an<00:07:32.039> array<00:07:32.400> of<00:07:32.639> byte<00:07:33.000> strings<00:07:33.240> right<00:07:33.539> that's 00:07:33.710 --> 00:07:33.720 align:start position:0% an array of byte strings right that's 00:07:33.720 --> 00:07:36.230 align:start position:0% an array of byte strings right that's the<00:07:33.960> most<00:07:34.199> abstract<00:07:34.680> way<00:07:35.039> that<00:07:35.639> you<00:07:35.819> can<00:07:36.000> think 00:07:36.230 --> 00:07:36.240 align:start position:0% the most abstract way that you can think 00:07:36.240 --> 00:07:38.689 align:start position:0% the most abstract way that you can think of<00:07:36.720> the<00:07:36.840> data<00:07:37.080> availability<00:07:37.440> layer<00:07:37.919> there<00:07:38.580> are 00:07:38.689 --> 00:07:38.699 align:start position:0% of the data availability layer there are 00:07:38.699 --> 00:07:40.430 align:start position:0% of the data availability layer there are certain<00:07:38.940> properties<00:07:39.479> that<00:07:39.780> you<00:07:39.960> might<00:07:40.139> want 00:07:40.430 --> 00:07:40.440 align:start position:0% certain properties that you might want 00:07:40.440 --> 00:07:42.409 align:start position:0% certain properties that you might want out<00:07:40.680> of<00:07:40.800> a<00:07:40.919> data<00:07:41.160> availability<00:07:41.520> layer<00:07:42.000> in 00:07:42.409 --> 00:07:42.419 align:start position:0% out of a data availability layer in 00:07:42.419 --> 00:07:44.809 align:start position:0% out of a data availability layer in practice<00:07:42.660> right<00:07:43.139> you<00:07:43.680> really<00:07:44.160> want<00:07:44.460> this<00:07:44.639> to 00:07:44.809 --> 00:07:44.819 align:start position:0% practice right you really want this to 00:07:44.819 --> 00:07:47.510 align:start position:0% practice right you really want this to be<00:07:45.000> a<00:07:45.479> mostly<00:07:45.780> immutable<00:07:46.380> append<00:07:46.919> only<00:07:47.160> list 00:07:47.510 --> 00:07:47.520 align:start position:0% be a mostly immutable append only list 00:07:47.520 --> 00:07:49.670 align:start position:0% be a mostly immutable append only list you<00:07:48.180> want<00:07:48.300> this<00:07:48.479> the<00:07:48.660> data<00:07:49.020> to<00:07:49.139> actually<00:07:49.380> be 00:07:49.670 --> 00:07:49.680 align:start position:0% you want this the data to actually be 00:07:49.680 --> 00:07:51.589 align:start position:0% you want this the data to actually be available<00:07:49.919> but<00:07:50.819> that's<00:07:51.000> a<00:07:51.180> that's<00:07:51.419> an 00:07:51.589 --> 00:07:51.599 align:start position:0% available but that's a that's an 00:07:51.599 --> 00:07:53.689 align:start position:0% available but that's a that's an implementation<00:07:52.199> detail<00:07:52.800> of<00:07:53.220> the<00:07:53.460> data 00:07:53.689 --> 00:07:53.699 align:start position:0% implementation detail of the data 00:07:53.699 --> 00:07:55.909 align:start position:0% implementation detail of the data availability<00:07:54.000> layer<00:07:54.539> itself<00:07:54.840> at<00:07:55.560> the<00:07:55.680> highest 00:07:55.909 --> 00:07:55.919 align:start position:0% availability layer itself at the highest 00:07:55.919 --> 00:07:57.650 align:start position:0% availability layer itself at the highest level<00:07:56.099> it<00:07:56.580> really<00:07:56.699> just<00:07:56.880> looks<00:07:57.180> like<00:07:57.300> this 00:07:57.650 --> 00:07:57.660 align:start position:0% level it really just looks like this 00:07:57.660 --> 00:08:00.890 align:start position:0% level it really just looks like this it's<00:07:58.199> an<00:07:58.440> array<00:07:58.860> of<00:07:59.280> byte<00:07:59.639> streams<00:08:00.060> in<00:08:00.780> the 00:08:00.890 --> 00:08:00.900 align:start position:0% it's an array of byte streams in the 00:08:00.900 --> 00:08:03.290 align:start position:0% it's an array of byte streams in the context<00:08:01.259> of<00:08:01.620> ethereum<00:08:02.340> right<00:08:02.759> if<00:08:02.880> we<00:08:03.060> look<00:08:03.180> at 00:08:03.290 --> 00:08:03.300 align:start position:0% context of ethereum right if we look at 00:08:03.300 --> 00:08:05.150 align:start position:0% context of ethereum right if we look at this<00:08:03.479> what<00:08:04.080> is<00:08:04.199> that<00:08:04.319> array<00:08:04.560> of<00:08:04.680> byte<00:08:04.979> strings 00:08:05.150 --> 00:08:05.160 align:start position:0% this what is that array of byte strings 00:08:05.160 --> 00:08:06.589 align:start position:0% this what is that array of byte strings it's<00:08:05.460> pretty<00:08:05.699> straightforward<00:08:06.180> it's<00:08:06.419> just 00:08:06.589 --> 00:08:06.599 align:start position:0% it's pretty straightforward it's just 00:08:06.599 --> 00:08:08.029 align:start position:0% it's pretty straightforward it's just every<00:08:06.960> new<00:08:07.199> block 00:08:08.029 --> 00:08:08.039 align:start position:0% every new block 00:08:08.039 --> 00:08:10.430 align:start position:0% every new block every<00:08:08.580> block<00:08:08.819> is<00:08:09.060> our<00:08:09.240> blob<00:08:09.479> right<00:08:09.900> and<00:08:10.319> every 00:08:10.430 --> 00:08:10.440 align:start position:0% every block is our blob right and every 00:08:10.440 --> 00:08:12.170 align:start position:0% every block is our blob right and every it's<00:08:10.740> this<00:08:10.979> array<00:08:11.340> of<00:08:11.460> blocks<00:08:11.819> that<00:08:12.000> just 00:08:12.170 --> 00:08:12.180 align:start position:0% it's this array of blocks that just 00:08:12.180 --> 00:08:13.969 align:start position:0% it's this array of blocks that just grows<00:08:12.419> and<00:08:12.539> grows<00:08:12.780> and<00:08:12.900> grows<00:08:13.139> and<00:08:13.319> has<00:08:13.560> pretty 00:08:13.969 --> 00:08:13.979 align:start position:0% grows and grows and grows and has pretty 00:08:13.979 --> 00:08:15.529 align:start position:0% grows and grows and grows and has pretty good<00:08:14.160> data<00:08:14.520> availability<00:08:14.819> properties<00:08:15.360> and 00:08:15.529 --> 00:08:15.539 align:start position:0% good data availability properties and 00:08:15.539 --> 00:08:16.730 align:start position:0% good data availability properties and has<00:08:15.720> pretty<00:08:15.960> good<00:08:16.080> immutable<00:08:16.500> prop 00:08:16.730 --> 00:08:16.740 align:start position:0% has pretty good immutable prop 00:08:16.740 --> 00:08:18.589 align:start position:0% has pretty good immutable prop mutability<00:08:17.280> properties 00:08:18.589 --> 00:08:18.599 align:start position:0% mutability properties 00:08:18.599 --> 00:08:20.689 align:start position:0% mutability properties um<00:08:18.660> so<00:08:18.840> you<00:08:18.900> can<00:08:19.020> do<00:08:19.199> that<00:08:19.440> you<00:08:19.919> know<00:08:20.039> here's<00:08:20.460> a 00:08:20.689 --> 00:08:20.699 align:start position:0% um so you can do that you know here's a 00:08:20.699 --> 00:08:22.850 align:start position:0% um so you can do that you know here's a whatever<00:08:21.060> some<00:08:21.419> code<00:08:21.660> of<00:08:21.960> we're<00:08:22.440> pulling<00:08:22.740> the 00:08:22.850 --> 00:08:22.860 align:start position:0% whatever some code of we're pulling the 00:08:22.860 --> 00:08:24.830 align:start position:0% whatever some code of we're pulling the data<00:08:23.099> from<00:08:23.340> from<00:08:23.520> L1<00:08:23.940> blocks<00:08:24.419> those<00:08:24.599> are<00:08:24.720> our 00:08:24.830 --> 00:08:24.840 align:start position:0% data from from L1 blocks those are our 00:08:24.840 --> 00:08:26.150 align:start position:0% data from from L1 blocks those are our blobs 00:08:26.150 --> 00:08:26.160 align:start position:0% blobs 00:08:26.160 --> 00:08:28.430 align:start position:0% blobs um<00:08:26.220> same<00:08:26.460> idea<00:08:26.819> in<00:08:26.940> 4844<00:08:27.539> except<00:08:28.259> you're 00:08:28.430 --> 00:08:28.440 align:start position:0% um same idea in 4844 except you're 00:08:28.440 --> 00:08:31.129 align:start position:0% um same idea in 4844 except you're looking<00:08:28.560> at<00:08:28.800> the<00:08:29.039> 4844<00:08:29.759> you<00:08:30.419> know<00:08:30.479> data 00:08:31.129 --> 00:08:31.139 align:start position:0% looking at the 4844 you know data 00:08:31.139 --> 00:08:32.449 align:start position:0% looking at the 4844 you know data sidecar<00:08:31.560> instead<00:08:31.919> of<00:08:31.979> looking<00:08:32.159> at<00:08:32.339> the 00:08:32.449 --> 00:08:32.459 align:start position:0% sidecar instead of looking at the 00:08:32.459 --> 00:08:34.790 align:start position:0% sidecar instead of looking at the primary<00:08:32.760> block<00:08:33.060> got<00:08:33.839> stuff<00:08:34.080> like<00:08:34.260> Celestia 00:08:34.790 --> 00:08:34.800 align:start position:0% primary block got stuff like Celestia 00:08:34.800 --> 00:08:36.110 align:start position:0% primary block got stuff like Celestia and<00:08:34.919> you<00:08:35.039> got<00:08:35.159> like<00:08:35.279> a<00:08:35.399> stack<00:08:35.580> of<00:08:35.700> Post-its 00:08:36.110 --> 00:08:36.120 align:start position:0% and you got like a stack of Post-its 00:08:36.120 --> 00:08:37.130 align:start position:0% and you got like a stack of Post-its like<00:08:36.240> you<00:08:36.300> could<00:08:36.419> do<00:08:36.539> it<00:08:36.659> with<00:08:36.779> a<00:08:36.899> stack<00:08:37.020> of 00:08:37.130 --> 00:08:37.140 align:start position:0% like you could do it with a stack of 00:08:37.140 --> 00:08:38.570 align:start position:0% like you could do it with a stack of Post-its<00:08:37.560> if<00:08:37.680> it's<00:08:37.800> like<00:08:37.919> a<00:08:38.159> sufficiently 00:08:38.570 --> 00:08:38.580 align:start position:0% Post-its if it's like a sufficiently 00:08:38.580 --> 00:08:40.490 align:start position:0% Post-its if it's like a sufficiently good<00:08:38.760> stack<00:08:39.000> of<00:08:39.120> Post-its 00:08:40.490 --> 00:08:40.500 align:start position:0% good stack of Post-its 00:08:40.500 --> 00:08:41.570 align:start position:0% good stack of Post-its um 00:08:41.570 --> 00:08:41.580 align:start position:0% um 00:08:41.580 --> 00:08:43.010 align:start position:0% um all<00:08:42.120> right 00:08:43.010 --> 00:08:43.020 align:start position:0% all right 00:08:43.020 --> 00:08:45.829 align:start position:0% all right so<00:08:43.680> array<00:08:44.279> of<00:08:44.459> blobs<00:08:44.820> pretty<00:08:45.300> straightforward 00:08:45.829 --> 00:08:45.839 align:start position:0% so array of blobs pretty straightforward 00:08:45.839 --> 00:08:48.250 align:start position:0% so array of blobs pretty straightforward generally<00:08:46.620> blobs<00:08:47.160> blocks 00:08:48.250 --> 00:08:48.260 align:start position:0% generally blobs blocks 00:08:48.260 --> 00:08:50.990 align:start position:0% generally blobs blocks now<00:08:49.260> let's<00:08:49.440> get<00:08:49.740> into<00:08:49.980> derivation<00:08:50.760> because 00:08:50.990 --> 00:08:51.000 align:start position:0% now let's get into derivation because 00:08:51.000 --> 00:08:54.170 align:start position:0% now let's get into derivation because derivation<00:08:51.620> is<00:08:52.620> what<00:08:53.040> I<00:08:53.160> think<00:08:53.279> to<00:08:53.519> be<00:08:53.640> one<00:08:54.120> of 00:08:54.170 --> 00:08:54.180 align:start position:0% derivation is what I think to be one of 00:08:54.180 --> 00:08:55.370 align:start position:0% derivation is what I think to be one of the<00:08:54.300> more<00:08:54.420> interesting<00:08:54.720> layers<00:08:55.019> in<00:08:55.260> this 00:08:55.370 --> 00:08:55.380 align:start position:0% the more interesting layers in this 00:08:55.380 --> 00:08:56.329 align:start position:0% the more interesting layers in this whole<00:08:55.500> system 00:08:56.329 --> 00:08:56.339 align:start position:0% whole system 00:08:56.339 --> 00:08:59.269 align:start position:0% whole system at<00:08:56.760> a<00:08:56.880> high<00:08:57.000> level<00:08:57.180> derivation<00:08:58.019> is<00:08:58.740> taking<00:08:58.980> the 00:08:59.269 --> 00:08:59.279 align:start position:0% at a high level derivation is taking the 00:08:59.279 --> 00:09:00.949 align:start position:0% at a high level derivation is taking the data<00:08:59.519> availability<00:08:59.880> layer<00:09:00.420> and<00:09:00.779> it's 00:09:00.949 --> 00:09:00.959 align:start position:0% data availability layer and it's 00:09:00.959 --> 00:09:03.170 align:start position:0% data availability layer and it's understanding<00:09:01.560> what<00:09:01.800> that<00:09:01.980> data<00:09:02.339> means<00:09:02.640> and 00:09:03.170 --> 00:09:03.180 align:start position:0% understanding what that data means and 00:09:03.180 --> 00:09:06.110 align:start position:0% understanding what that data means and it's<00:09:03.360> parsing<00:09:03.899> it<00:09:04.080> and<00:09:04.740> using<00:09:05.160> that<00:09:05.459> data<00:09:05.760> plus 00:09:06.110 --> 00:09:06.120 align:start position:0% it's parsing it and using that data plus 00:09:06.120 --> 00:09:07.790 align:start position:0% it's parsing it and using that data plus the<00:09:06.420> current<00:09:06.600> state<00:09:06.839> of<00:09:07.019> your<00:09:07.140> layer<00:09:07.380> 2<00:09:07.500> system 00:09:07.790 --> 00:09:07.800 align:start position:0% the current state of your layer 2 system 00:09:07.800 --> 00:09:11.030 align:start position:0% the current state of your layer 2 system it's<00:09:08.399> producing<00:09:08.880> the<00:09:09.240> inputs<00:09:09.779> to<00:09:09.959> your<00:09:10.140> chain 00:09:11.030 --> 00:09:11.040 align:start position:0% it's producing the inputs to your chain 00:09:11.040 --> 00:09:13.250 align:start position:0% it's producing the inputs to your chain right<00:09:11.580> it's<00:09:11.880> producing<00:09:12.360> for<00:09:12.779> example<00:09:13.019> I'll 00:09:13.250 --> 00:09:13.260 align:start position:0% right it's producing for example I'll 00:09:13.260 --> 00:09:14.329 align:start position:0% right it's producing for example I'll get<00:09:13.440> to<00:09:13.560> it<00:09:13.680> but<00:09:13.860> it<00:09:13.980> can<00:09:14.100> produce 00:09:14.329 --> 00:09:14.339 align:start position:0% get to it but it can produce 00:09:14.339 --> 00:09:16.250 align:start position:0% get to it but it can produce transactions<00:09:15.060> you<00:09:15.600> know<00:09:15.720> that's<00:09:15.839> sort<00:09:16.080> of<00:09:16.200> the 00:09:16.250 --> 00:09:16.260 align:start position:0% transactions you know that's sort of the 00:09:16.260 --> 00:09:17.630 align:start position:0% transactions you know that's sort of the classic<00:09:16.440> example 00:09:17.630 --> 00:09:17.640 align:start position:0% classic example 00:09:17.640 --> 00:09:20.930 align:start position:0% classic example our<00:09:18.180> case<00:09:18.480> we<00:09:19.440> use<00:09:19.680> the<00:09:20.040> engine<00:09:20.160> API<00:09:20.640> the<00:09:20.820> op 00:09:20.930 --> 00:09:20.940 align:start position:0% our case we use the engine API the op 00:09:20.940 --> 00:09:23.329 align:start position:0% our case we use the engine API the op stack<00:09:21.300> uses<00:09:21.540> the<00:09:21.660> engine<00:09:21.779> API<00:09:22.380> why<00:09:23.040> the<00:09:23.220> engine 00:09:23.329 --> 00:09:23.339 align:start position:0% stack uses the engine API why the engine 00:09:23.339 --> 00:09:25.430 align:start position:0% stack uses the engine API why the engine API<00:09:23.940> yeah<00:09:24.600> it's<00:09:24.779> like<00:09:24.959> one<00:09:25.140> of<00:09:25.260> these<00:09:25.320> things 00:09:25.430 --> 00:09:25.440 align:start position:0% API yeah it's like one of these things 00:09:25.440 --> 00:09:27.350 align:start position:0% API yeah it's like one of these things we're<00:09:25.680> opinionated<00:09:26.100> on<00:09:26.399> basically<00:09:26.820> we<00:09:27.120> think 00:09:27.350 --> 00:09:27.360 align:start position:0% we're opinionated on basically we think 00:09:27.360 --> 00:09:29.509 align:start position:0% we're opinionated on basically we think you<00:09:27.839> know<00:09:27.959> where<00:09:28.140> as<00:09:28.380> as<00:09:28.620> optimism<00:09:29.160> we're 00:09:29.509 --> 00:09:29.519 align:start position:0% you know where as as optimism we're 00:09:29.519 --> 00:09:32.030 align:start position:0% you know where as as optimism we're building<00:09:29.700> this<00:09:30.120> evm<00:09:30.720> equivalent<00:09:31.260> optimistic 00:09:32.030 --> 00:09:32.040 align:start position:0% building this evm equivalent optimistic 00:09:32.040 --> 00:09:35.210 align:start position:0% building this evm equivalent optimistic rollup<00:09:32.459> the<00:09:33.360> ethereum<00:09:34.019> already<00:09:34.320> standardized 00:09:35.210 --> 00:09:35.220 align:start position:0% rollup the ethereum already standardized 00:09:35.220 --> 00:09:37.610 align:start position:0% rollup the ethereum already standardized the<00:09:35.459> separation<00:09:36.000> between<00:09:36.720> the<00:09:37.140> consensus 00:09:37.610 --> 00:09:37.620 align:start position:0% the separation between the consensus 00:09:37.620 --> 00:09:40.310 align:start position:0% the separation between the consensus client<00:09:37.980> and<00:09:38.339> the<00:09:38.459> ex<00:09:38.640> execution<00:09:39.420> client<00:09:39.839> it 00:09:40.310 --> 00:09:40.320 align:start position:0% client and the ex execution client it 00:09:40.320 --> 00:09:42.110 align:start position:0% client and the ex execution client it didn't<00:09:40.500> really<00:09:40.800> make<00:09:41.100> much<00:09:41.459> sense<00:09:41.640> to<00:09:41.880> come<00:09:42.000> up 00:09:42.110 --> 00:09:42.120 align:start position:0% didn't really make much sense to come up 00:09:42.120 --> 00:09:44.150 align:start position:0% didn't really make much sense to come up with<00:09:42.240> a<00:09:42.420> totally<00:09:42.660> new<00:09:42.959> way<00:09:43.260> of<00:09:43.800> driving 00:09:44.150 --> 00:09:44.160 align:start position:0% with a totally new way of driving 00:09:44.160 --> 00:09:46.550 align:start position:0% with a totally new way of driving execution<00:09:44.880> you<00:09:45.480> might<00:09:45.600> as<00:09:45.720> well<00:09:45.839> just<00:09:46.080> reuse 00:09:46.550 --> 00:09:46.560 align:start position:0% execution you might as well just reuse 00:09:46.560 --> 00:09:48.350 align:start position:0% execution you might as well just reuse the<00:09:46.800> same<00:09:47.040> thing<00:09:47.220> because<00:09:47.519> the<00:09:47.760> apis<00:09:48.120> are 00:09:48.350 --> 00:09:48.360 align:start position:0% the same thing because the apis are 00:09:48.360 --> 00:09:49.670 align:start position:0% the same thing because the apis are there 00:09:49.670 --> 00:09:49.680 align:start position:0% there 00:09:49.680 --> 00:09:50.930 align:start position:0% there um 00:09:50.930 --> 00:09:50.940 align:start position:0% um 00:09:50.940 --> 00:09:52.970 align:start position:0% um all<00:09:51.480> right<00:09:51.660> let's<00:09:51.839> go<00:09:52.019> so<00:09:52.380> let's<00:09:52.500> formalize 00:09:52.970 --> 00:09:52.980 align:start position:0% all right let's go so let's formalize 00:09:52.980 --> 00:09:55.009 align:start position:0% all right let's go so let's formalize this<00:09:53.220> what<00:09:53.399> does<00:09:53.519> this<00:09:53.700> actually<00:09:53.880> mean<00:09:54.300> I 00:09:55.009 --> 00:09:55.019 align:start position:0% this what does this actually mean I 00:09:55.019 --> 00:09:56.329 align:start position:0% this what does this actually mean I think<00:09:55.140> this<00:09:55.320> has<00:09:55.500> a<00:09:55.740> relatively<00:09:56.160> simple 00:09:56.329 --> 00:09:56.339 align:start position:0% think this has a relatively simple 00:09:56.339 --> 00:09:57.889 align:start position:0% think this has a relatively simple function<00:09:56.700> signature<00:09:57.240> and<00:09:57.360> it<00:09:57.480> kind<00:09:57.600> of<00:09:57.720> looks 00:09:57.889 --> 00:09:57.899 align:start position:0% function signature and it kind of looks 00:09:57.899 --> 00:09:59.389 align:start position:0% function signature and it kind of looks like<00:09:57.959> this<00:09:58.140> you<00:09:58.560> have<00:09:58.740> this<00:09:58.920> derivation 00:09:59.389 --> 00:09:59.399 align:start position:0% like this you have this derivation 00:09:59.399 --> 00:10:01.550 align:start position:0% like this you have this derivation function<00:09:59.880> and<00:10:00.480> it<00:10:00.600> takes<00:10:00.779> the<00:10:01.019> previous<00:10:01.200> state 00:10:01.550 --> 00:10:01.560 align:start position:0% function and it takes the previous state 00:10:01.560 --> 00:10:03.769 align:start position:0% function and it takes the previous state of<00:10:01.740> your<00:10:01.860> roll<00:10:02.040> up<00:10:02.220> or<00:10:02.640> your<00:10:02.820> system<00:10:03.000> it<00:10:03.660> takes 00:10:03.769 --> 00:10:03.779 align:start position:0% of your roll up or your system it takes 00:10:03.779 --> 00:10:05.690 align:start position:0% of your roll up or your system it takes the<00:10:03.959> data<00:10:04.200> availability<00:10:04.560> layer<00:10:05.040> and<00:10:05.580> it's 00:10:05.690 --> 00:10:05.700 align:start position:0% the data availability layer and it's 00:10:05.700 --> 00:10:08.210 align:start position:0% the data availability layer and it's either<00:10:05.940> going<00:10:06.240> to<00:10:06.360> produce<00:10:06.779> a<00:10:07.440> payload<00:10:07.920> for 00:10:08.210 --> 00:10:08.220 align:start position:0% either going to produce a payload for 00:10:08.220 --> 00:10:10.430 align:start position:0% either going to produce a payload for you<00:10:08.339> to<00:10:08.580> execute<00:10:09.060> on<00:10:09.360> the<00:10:09.480> on<00:10:09.779> the<00:10:09.959> execution 00:10:10.430 --> 00:10:10.440 align:start position:0% you to execute on the on the execution 00:10:10.440 --> 00:10:13.070 align:start position:0% you to execute on the on the execution layer<00:10:10.920> or<00:10:11.459> it's<00:10:11.580> going<00:10:11.760> to<00:10:11.880> produce<00:10:12.180> nothing 00:10:13.070 --> 00:10:13.080 align:start position:0% layer or it's going to produce nothing 00:10:13.080 --> 00:10:15.410 align:start position:0% layer or it's going to produce nothing and<00:10:13.500> it<00:10:13.620> might<00:10:13.800> produce<00:10:14.160> nothing<00:10:14.519> if<00:10:15.240> let's 00:10:15.410 --> 00:10:15.420 align:start position:0% and it might produce nothing if let's 00:10:15.420 --> 00:10:17.210 align:start position:0% and it might produce nothing if let's say<00:10:15.540> you're<00:10:15.720> a<00:10:15.899> roll-up<00:10:16.260> and<00:10:16.860> there<00:10:17.040> just 00:10:17.210 --> 00:10:17.220 align:start position:0% say you're a roll-up and there just 00:10:17.220 --> 00:10:18.470 align:start position:0% say you're a roll-up and there just haven't<00:10:17.339> been<00:10:17.580> any<00:10:17.760> new<00:10:17.940> transactions 00:10:18.470 --> 00:10:18.480 align:start position:0% haven't been any new transactions 00:10:18.480 --> 00:10:20.030 align:start position:0% haven't been any new transactions published<00:10:18.839> to<00:10:18.959> layer<00:10:19.200> one<00:10:19.320> it<00:10:19.560> might<00:10:19.680> just<00:10:19.800> say 00:10:20.030 --> 00:10:20.040 align:start position:0% published to layer one it might just say 00:10:20.040 --> 00:10:21.829 align:start position:0% published to layer one it might just say well<00:10:20.519> I<00:10:20.700> looked<00:10:20.940> at<00:10:21.000> this<00:10:21.240> new<00:10:21.360> block<00:10:21.540> that 00:10:21.829 --> 00:10:21.839 align:start position:0% well I looked at this new block that 00:10:21.839 --> 00:10:23.449 align:start position:0% well I looked at this new block that came<00:10:22.019> in<00:10:22.140> from<00:10:22.320> the<00:10:22.440> data<00:10:22.680> availability<00:10:22.980> layer 00:10:23.449 --> 00:10:23.459 align:start position:0% came in from the data availability layer 00:10:23.459 --> 00:10:25.009 align:start position:0% came in from the data availability layer and<00:10:23.880> there's<00:10:24.000> nothing<00:10:24.180> new<00:10:24.420> to<00:10:24.660> put<00:10:24.720> into<00:10:24.839> the 00:10:25.009 --> 00:10:25.019 align:start position:0% and there's nothing new to put into the 00:10:25.019 --> 00:10:26.090 align:start position:0% and there's nothing new to put into the roll<00:10:25.140> up<00:10:25.320> so<00:10:25.440> I'm<00:10:25.560> just<00:10:25.680> going<00:10:25.800> to<00:10:25.800> produce 00:10:26.090 --> 00:10:26.100 align:start position:0% roll up so I'm just going to produce 00:10:26.100 --> 00:10:28.130 align:start position:0% roll up so I'm just going to produce nothing<00:10:26.339> or<00:10:27.120> it<00:10:27.300> could<00:10:27.420> look<00:10:27.540> at<00:10:27.660> a<00:10:27.779> block<00:10:27.899> in 00:10:28.130 --> 00:10:28.140 align:start position:0% nothing or it could look at a block in 00:10:28.140 --> 00:10:29.690 align:start position:0% nothing or it could look at a block in the<00:10:28.260> date<00:10:28.380> availability<00:10:28.740> layer<00:10:29.160> or<00:10:29.339> a<00:10:29.459> blob 00:10:29.690 --> 00:10:29.700 align:start position:0% the date availability layer or a blob 00:10:29.700 --> 00:10:31.430 align:start position:0% the date availability layer or a blob whatever<00:10:29.880> and<00:10:30.480> it<00:10:30.600> could<00:10:30.779> say<00:10:30.899> okay<00:10:31.140> actually 00:10:31.430 --> 00:10:31.440 align:start position:0% whatever and it could say okay actually 00:10:31.440 --> 00:10:33.470 align:start position:0% whatever and it could say okay actually here<00:10:31.680> there's<00:10:31.920> a<00:10:32.100> transaction<00:10:32.580> that<00:10:33.180> we<00:10:33.360> need 00:10:33.470 --> 00:10:33.480 align:start position:0% here there's a transaction that we need 00:10:33.480 --> 00:10:36.710 align:start position:0% here there's a transaction that we need to<00:10:33.600> execute<00:10:34.080> on<00:10:34.260> our<00:10:34.380> layer<00:10:34.620> 2<00:10:34.740> system 00:10:36.710 --> 00:10:36.720 align:start position:0% to execute on our layer 2 system 00:10:36.720 --> 00:10:38.269 align:start position:0% to execute on our layer 2 system so<00:10:37.320> let's<00:10:37.500> make<00:10:37.740> this<00:10:37.860> a<00:10:38.040> little<00:10:38.100> more 00:10:38.269 --> 00:10:38.279 align:start position:0% so let's make this a little more 00:10:38.279 --> 00:10:39.769 align:start position:0% so let's make this a little more concrete<00:10:38.700> let's<00:10:38.880> look<00:10:39.000> at<00:10:39.120> derivation<00:10:39.600> in 00:10:39.769 --> 00:10:39.779 align:start position:0% concrete let's look at derivation in 00:10:39.779 --> 00:10:41.570 align:start position:0% concrete let's look at derivation in Bedrock<00:10:40.260> we<00:10:40.440> look<00:10:40.620> at<00:10:40.740> data<00:10:41.040> from<00:10:41.279> Three 00:10:41.570 --> 00:10:41.580 align:start position:0% Bedrock we look at data from Three 00:10:41.580 --> 00:10:44.030 align:start position:0% Bedrock we look at data from Three locations<00:10:42.240> the<00:10:42.899> number<00:10:43.080> one<00:10:43.260> piece<00:10:43.560> like<00:10:43.860> the 00:10:44.030 --> 00:10:44.040 align:start position:0% locations the number one piece like the 00:10:44.040 --> 00:10:45.769 align:start position:0% locations the number one piece like the most<00:10:44.160> common<00:10:44.279> place<00:10:44.579> we<00:10:44.760> look<00:10:44.940> for<00:10:45.060> data<00:10:45.420> is 00:10:45.769 --> 00:10:45.779 align:start position:0% most common place we look for data is 00:10:45.779 --> 00:10:47.690 align:start position:0% most common place we look for data is sequencer<00:10:46.320> data<00:10:46.680> posted<00:10:47.040> to<00:10:47.220> a<00:10:47.399> specific 00:10:47.690 --> 00:10:47.700 align:start position:0% sequencer data posted to a specific 00:10:47.700 --> 00:10:49.910 align:start position:0% sequencer data posted to a specific address<00:10:48.060> on<00:10:48.420> layer<00:10:48.720> one<00:10:48.899> this<00:10:49.560> kind<00:10:49.740> of<00:10:49.800> makes 00:10:49.910 --> 00:10:49.920 align:start position:0% address on layer one this kind of makes 00:10:49.920 --> 00:10:51.949 align:start position:0% address on layer one this kind of makes sense<00:10:50.160> we<00:10:50.519> the<00:10:50.820> sequencer<00:10:51.300> collects<00:10:51.720> a<00:10:51.839> bunch 00:10:51.949 --> 00:10:51.959 align:start position:0% sense we the sequencer collects a bunch 00:10:51.959 --> 00:10:54.050 align:start position:0% sense we the sequencer collects a bunch of<00:10:52.140> user<00:10:52.440> transactions<00:10:53.040> compresses<00:10:53.880> it 00:10:54.050 --> 00:10:54.060 align:start position:0% of user transactions compresses it 00:10:54.060 --> 00:10:56.030 align:start position:0% of user transactions compresses it shoves<00:10:54.660> it<00:10:54.779> onto<00:10:55.019> layer<00:10:55.260> one<00:10:55.380> and<00:10:55.560> it<00:10:55.680> posts<00:10:55.920> it 00:10:56.030 --> 00:10:56.040 align:start position:0% shoves it onto layer one and it posts it 00:10:56.040 --> 00:10:57.889 align:start position:0% shoves it onto layer one and it posts it on<00:10:56.160> to<00:10:56.399> a<00:10:56.519> specific<00:10:56.760> address<00:10:57.000> not<00:10:57.420> a<00:10:57.600> contract 00:10:57.889 --> 00:10:57.899 align:start position:0% on to a specific address not a contract 00:10:57.899 --> 00:10:59.750 align:start position:0% on to a specific address not a contract interestingly<00:10:58.500> enough 00:10:59.750 --> 00:10:59.760 align:start position:0% interestingly enough 00:10:59.760 --> 00:11:01.910 align:start position:0% interestingly enough um<00:10:59.820> you<00:11:00.000> know<00:11:00.120> and<00:11:00.300> it's<00:11:00.480> here's<00:11:01.079> the<00:11:01.680> many 00:11:01.910 --> 00:11:01.920 align:start position:0% um you know and it's here's the many 00:11:01.920 --> 00:11:04.009 align:start position:0% um you know and it's here's the many it's<00:11:02.220> actually<00:11:02.640> very<00:11:03.240> complicated<00:11:03.660> if<00:11:03.899> you 00:11:04.009 --> 00:11:04.019 align:start position:0% it's actually very complicated if you 00:11:04.019 --> 00:11:06.410 align:start position:0% it's actually very complicated if you want<00:11:04.200> to<00:11:04.380> derive<00:11:04.980> this<00:11:05.220> and<00:11:05.519> and<00:11:05.700> make<00:11:06.240> it 00:11:06.410 --> 00:11:06.420 align:start position:0% want to derive this and and make it 00:11:06.420 --> 00:11:08.090 align:start position:0% want to derive this and and make it extraordinarily<00:11:07.079> efficient<00:11:07.440> so<00:11:07.740> it's<00:11:07.920> in 00:11:08.090 --> 00:11:08.100 align:start position:0% extraordinarily efficient so it's in 00:11:08.100 --> 00:11:10.190 align:start position:0% extraordinarily efficient so it's in multiple 00:11:10.190 --> 00:11:10.200 align:start position:0% multiple 00:11:10.200 --> 00:11:12.110 align:start position:0% multiple files<00:11:10.980> here<00:11:11.100> but<00:11:11.279> you<00:11:11.459> could<00:11:11.519> make<00:11:11.700> this<00:11:11.940> much 00:11:12.110 --> 00:11:12.120 align:start position:0% files here but you could make this much 00:11:12.120 --> 00:11:13.550 align:start position:0% files here but you could make this much simpler<00:11:12.420> if<00:11:12.600> you<00:11:12.720> really<00:11:12.839> wanted<00:11:13.019> to<00:11:13.200> at<00:11:13.380> the 00:11:13.550 --> 00:11:13.560 align:start position:0% simpler if you really wanted to at the 00:11:13.560 --> 00:11:16.670 align:start position:0% simpler if you really wanted to at the expense<00:11:13.920> of<00:11:14.459> gas<00:11:15.060> costs 00:11:16.670 --> 00:11:16.680 align:start position:0% expense of gas costs 00:11:16.680 --> 00:11:18.230 align:start position:0% expense of gas costs then<00:11:17.100> we<00:11:17.279> derive<00:11:17.579> data<00:11:17.880> from<00:11:18.000> a<00:11:18.120> second 00:11:18.230 --> 00:11:18.240 align:start position:0% then we derive data from a second 00:11:18.240 --> 00:11:20.870 align:start position:0% then we derive data from a second location<00:11:18.480> which<00:11:18.959> is<00:11:19.019> deposits<00:11:19.800> sent<00:11:20.399> to<00:11:20.700> the 00:11:20.870 --> 00:11:20.880 align:start position:0% location which is deposits sent to the 00:11:20.880 --> 00:11:23.389 align:start position:0% location which is deposits sent to the portal<00:11:21.240> contract<00:11:21.660> which<00:11:21.899> is<00:11:22.079> basically<00:11:22.440> our 00:11:23.389 --> 00:11:23.399 align:start position:0% portal contract which is basically our 00:11:23.399 --> 00:11:25.730 align:start position:0% portal contract which is basically our deposit<00:11:24.360> contract<00:11:24.779> so<00:11:25.019> when<00:11:25.380> there's<00:11:25.560> a 00:11:25.730 --> 00:11:25.740 align:start position:0% deposit contract so when there's a 00:11:25.740 --> 00:11:27.470 align:start position:0% deposit contract so when there's a deposit<00:11:26.160> event<00:11:26.339> emitted<00:11:26.940> by<00:11:27.000> the<00:11:27.180> portal 00:11:27.470 --> 00:11:27.480 align:start position:0% deposit event emitted by the portal 00:11:27.480 --> 00:11:29.329 align:start position:0% deposit event emitted by the portal contract<00:11:27.899> in<00:11:28.200> a<00:11:28.320> block<00:11:28.500> we're<00:11:29.040> going<00:11:29.160> to 00:11:29.329 --> 00:11:29.339 align:start position:0% contract in a block we're going to 00:11:29.339 --> 00:11:31.370 align:start position:0% contract in a block we're going to derive<00:11:29.760> a<00:11:30.060> layer<00:11:30.300> to<00:11:30.480> deposit<00:11:31.019> transaction 00:11:31.370 --> 00:11:31.380 align:start position:0% derive a layer to deposit transaction 00:11:31.380 --> 00:11:33.230 align:start position:0% derive a layer to deposit transaction here's<00:11:32.100> how<00:11:32.279> we<00:11:32.399> do<00:11:32.519> that<00:11:32.700> right<00:11:32.940> whatever 00:11:33.230 --> 00:11:33.240 align:start position:0% here's how we do that right whatever 00:11:33.240 --> 00:11:37.009 align:start position:0% here's how we do that right whatever then<00:11:34.140> the<00:11:34.560> layer<00:11:34.860> 1<00:11:34.980> block<00:11:35.339> data<00:11:35.760> itself<00:11:36.060> every 00:11:37.009 --> 00:11:37.019 align:start position:0% then the layer 1 block data itself every 00:11:37.019 --> 00:11:39.230 align:start position:0% then the layer 1 block data itself every time<00:11:37.260> there's<00:11:37.560> a<00:11:37.740> new<00:11:37.860> layer<00:11:38.160> one<00:11:38.399> block<00:11:38.640> we're 00:11:39.230 --> 00:11:39.240 align:start position:0% time there's a new layer one block we're 00:11:39.240 --> 00:11:41.569 align:start position:0% time there's a new layer one block we're going<00:11:39.480> to<00:11:39.600> derive<00:11:40.260> a<00:11:40.620> special<00:11:40.740> transaction<00:11:41.279> on 00:11:41.569 --> 00:11:41.579 align:start position:0% going to derive a special transaction on 00:11:41.579 --> 00:11:43.850 align:start position:0% going to derive a special transaction on layer<00:11:41.940> 2<00:11:42.120> that<00:11:42.899> carries<00:11:43.380> the<00:11:43.680> information 00:11:43.850 --> 00:11:43.860 align:start position:0% layer 2 that carries the information 00:11:43.860 --> 00:11:46.610 align:start position:0% layer 2 that carries the information about<00:11:44.459> that<00:11:44.700> layer<00:11:45.000> one<00:11:45.180> block<00:11:45.480> into<00:11:46.140> Layer 00:11:46.610 --> 00:11:46.620 align:start position:0% about that layer one block into Layer 00:11:46.620 --> 00:11:49.130 align:start position:0% about that layer one block into Layer Two<00:11:46.800> into<00:11:47.279> the<00:11:47.579> layer<00:11:47.820> 2<00:11:48.000> State<00:11:48.420> here's<00:11:48.899> how<00:11:49.019> we 00:11:49.130 --> 00:11:49.140 align:start position:0% Two into the layer 2 State here's how we 00:11:49.140 --> 00:11:51.889 align:start position:0% Two into the layer 2 State here's how we do<00:11:49.320> that<00:11:49.440> whatever<00:11:49.920> the<00:11:50.760> point<00:11:50.940> is<00:11:51.180> that<00:11:51.720> we 00:11:51.889 --> 00:11:51.899 align:start position:0% do that whatever the point is that we 00:11:51.899 --> 00:11:53.810 align:start position:0% do that whatever the point is that we can<00:11:52.079> transform<00:11:52.560> all<00:11:53.160> of<00:11:53.279> these<00:11:53.579> different 00:11:53.810 --> 00:11:53.820 align:start position:0% can transform all of these different 00:11:53.820 --> 00:11:56.690 align:start position:0% can transform all of these different sort<00:11:54.420> of<00:11:54.480> data<00:11:54.899> sources<00:11:55.260> into<00:11:55.860> payloads<00:11:56.519> that 00:11:56.690 --> 00:11:56.700 align:start position:0% sort of data sources into payloads that 00:11:56.700 --> 00:11:59.870 align:start position:0% sort of data sources into payloads that get<00:11:56.880> executed<00:11:57.420> on<00:11:57.600> Layer<00:11:57.899> Two 00:11:59.870 --> 00:11:59.880 align:start position:0% get executed on Layer Two 00:11:59.880 --> 00:12:01.190 align:start position:0% get executed on Layer Two um and<00:12:00.180> this<00:12:00.300> abstraction<00:12:00.720> is<00:12:01.019> actually 00:12:01.190 --> 00:12:01.200 align:start position:0% um and this abstraction is actually 00:12:01.200 --> 00:12:02.630 align:start position:0% um and this abstraction is actually really<00:12:01.440> really<00:12:01.560> powerful<00:12:02.040> and<00:12:02.279> I<00:12:02.399> want<00:12:02.519> to 00:12:02.630 --> 00:12:02.640 align:start position:0% really really powerful and I want to 00:12:02.640 --> 00:12:05.210 align:start position:0% really really powerful and I want to kind<00:12:02.820> of<00:12:02.940> hammer<00:12:03.480> this<00:12:03.660> in<00:12:03.899> because<00:12:04.620> if<00:12:05.160> you 00:12:05.210 --> 00:12:05.220 align:start position:0% kind of hammer this in because if you 00:12:05.220 --> 00:12:06.650 align:start position:0% kind of hammer this in because if you want<00:12:05.339> to<00:12:05.459> build<00:12:05.519> a<00:12:05.700> roll-up<00:12:05.940> you<00:12:06.120> did<00:12:06.240> what<00:12:06.420> we 00:12:06.650 --> 00:12:06.660 align:start position:0% want to build a roll-up you did what we 00:12:06.660 --> 00:12:07.970 align:start position:0% want to build a roll-up you did what we do<00:12:06.839> what<00:12:06.959> we<00:12:07.019> just<00:12:07.260> talked<00:12:07.440> about<00:12:07.500> right<00:12:07.740> you 00:12:07.970 --> 00:12:07.980 align:start position:0% do what we just talked about right you 00:12:07.980 --> 00:12:10.069 align:start position:0% do what we just talked about right you read<00:12:08.160> sequence<00:12:08.519> transactions<00:12:09.240> read<00:12:09.600> deposit 00:12:10.069 --> 00:12:10.079 align:start position:0% read sequence transactions read deposit 00:12:10.079 --> 00:12:12.410 align:start position:0% read sequence transactions read deposit data<00:12:10.440> read<00:12:10.620> block<00:12:10.920> data<00:12:11.339> whatever<00:12:11.519> but<00:12:12.300> that's 00:12:12.410 --> 00:12:12.420 align:start position:0% data read block data whatever but that's 00:12:12.420 --> 00:12:14.030 align:start position:0% data read block data whatever but that's not<00:12:12.660> the<00:12:12.839> only<00:12:13.019> thing<00:12:13.200> you<00:12:13.380> can<00:12:13.500> do<00:12:13.680> with<00:12:13.860> this 00:12:14.030 --> 00:12:14.040 align:start position:0% not the only thing you can do with this 00:12:14.040 --> 00:12:16.730 align:start position:0% not the only thing you can do with this you<00:12:14.760> can<00:12:14.880> derive<00:12:15.300> data<00:12:15.720> from<00:12:15.959> almost<00:12:16.200> any 00:12:16.730 --> 00:12:16.740 align:start position:0% you can derive data from almost any 00:12:16.740 --> 00:12:18.230 align:start position:0% you can derive data from almost any piece<00:12:17.100> of<00:12:17.160> information<00:12:17.399> that<00:12:17.880> lives<00:12:18.120> on 00:12:18.230 --> 00:12:18.240 align:start position:0% piece of information that lives on 00:12:18.240 --> 00:12:20.449 align:start position:0% piece of information that lives on ethereum<00:12:18.660> or<00:12:18.839> lives<00:12:19.079> on<00:12:19.140> your<00:12:19.260> layer<00:12:19.560> one<00:12:19.740> uh 00:12:20.449 --> 00:12:20.459 align:start position:0% ethereum or lives on your layer one uh 00:12:20.459 --> 00:12:23.030 align:start position:0% ethereum or lives on your layer one uh or<00:12:20.640> your<00:12:20.820> data<00:12:21.480> availability<00:12:21.839> layer 00:12:23.030 --> 00:12:23.040 align:start position:0% or your data availability layer 00:12:23.040 --> 00:12:24.949 align:start position:0% or your data availability layer so<00:12:23.399> I<00:12:23.519> want<00:12:23.640> to<00:12:23.760> just<00:12:23.880> show<00:12:24.000> you<00:12:24.120> a<00:12:24.420> toy<00:12:24.660> example 00:12:24.949 --> 00:12:24.959 align:start position:0% so I want to just show you a toy example 00:12:24.959 --> 00:12:26.449 align:start position:0% so I want to just show you a toy example of<00:12:25.140> something<00:12:25.320> that<00:12:25.500> I<00:12:25.620> think<00:12:25.740> is<00:12:25.920> really<00:12:26.220> cool 00:12:26.449 --> 00:12:26.459 align:start position:0% of something that I think is really cool 00:12:26.459 --> 00:12:28.730 align:start position:0% of something that I think is really cool that<00:12:26.640> you<00:12:26.820> can<00:12:26.880> do<00:12:27.060> with<00:12:27.240> this<00:12:27.959> let's<00:12:28.440> say<00:12:28.560> that 00:12:28.730 --> 00:12:28.740 align:start position:0% that you can do with this let's say that 00:12:28.740 --> 00:12:30.230 align:start position:0% that you can do with this let's say that you<00:12:28.860> had<00:12:28.920> a<00:12:29.040> layer<00:12:29.279> two<00:12:29.459> without<00:12:29.760> user 00:12:30.230 --> 00:12:30.240 align:start position:0% you had a layer two without user 00:12:30.240 --> 00:12:32.810 align:start position:0% you had a layer two without user transactions<00:12:30.779> without<00:12:30.959> anything<00:12:31.380> right<00:12:32.339> and 00:12:32.810 --> 00:12:32.820 align:start position:0% transactions without anything right and 00:12:32.820 --> 00:12:34.730 align:start position:0% transactions without anything right and the<00:12:32.940> only<00:12:33.120> way<00:12:33.360> that<00:12:33.600> you<00:12:33.899> derive<00:12:34.380> these 00:12:34.730 --> 00:12:34.740 align:start position:0% the only way that you derive these 00:12:34.740 --> 00:12:36.769 align:start position:0% the only way that you derive these engine<00:12:34.920> payloads<00:12:35.640> was<00:12:36.060> every<00:12:36.300> time<00:12:36.480> there<00:12:36.660> was 00:12:36.769 --> 00:12:36.779 align:start position:0% engine payloads was every time there was 00:12:36.779 --> 00:12:39.350 align:start position:0% engine payloads was every time there was a<00:12:36.899> uniswap<00:12:37.440> swap<00:12:37.800> event<00:12:37.980> on<00:12:38.279> layer<00:12:38.579> one<00:12:38.760> you 00:12:39.350 --> 00:12:39.360 align:start position:0% a uniswap swap event on layer one you 00:12:39.360 --> 00:12:41.509 align:start position:0% a uniswap swap event on layer one you derive<00:12:39.720> a<00:12:39.899> transaction<00:12:40.200> on<00:12:40.500> Layer<00:12:40.800> Two<00:12:40.920> that 00:12:41.509 --> 00:12:41.519 align:start position:0% derive a transaction on Layer Two that 00:12:41.519 --> 00:12:43.910 align:start position:0% derive a transaction on Layer Two that includes<00:12:41.940> the<00:12:42.180> assets<00:12:42.540> and<00:12:43.380> the<00:12:43.500> amounts 00:12:43.910 --> 00:12:43.920 align:start position:0% includes the assets and the amounts 00:12:43.920 --> 00:12:46.550 align:start position:0% includes the assets and the amounts right<00:12:44.639> and<00:12:45.240> you<00:12:45.420> feed<00:12:45.540> that<00:12:45.779> transaction<00:12:46.200> into 00:12:46.550 --> 00:12:46.560 align:start position:0% right and you feed that transaction into 00:12:46.560 --> 00:12:48.530 align:start position:0% right and you feed that transaction into a<00:12:46.740> smart<00:12:46.920> contract<00:12:47.339> on<00:12:47.639> Layer<00:12:47.880> Two<00:12:48.000> that<00:12:48.300> keeps 00:12:48.530 --> 00:12:48.540 align:start position:0% a smart contract on Layer Two that keeps 00:12:48.540 --> 00:12:51.410 align:start position:0% a smart contract on Layer Two that keeps a<00:12:48.660> running<00:12:48.839> tally<00:12:49.380> of<00:12:50.040> the<00:12:50.220> volumes 00:12:51.410 --> 00:12:51.420 align:start position:0% a running tally of the volumes 00:12:51.420 --> 00:12:53.449 align:start position:0% a running tally of the volumes that<00:12:52.139> kind<00:12:52.320> of<00:12:52.440> looks<00:12:52.680> like<00:12:52.800> something<00:12:53.040> like 00:12:53.449 --> 00:12:53.459 align:start position:0% that kind of looks like something like 00:12:53.459 --> 00:12:55.490 align:start position:0% that kind of looks like something like all<00:12:53.579> of<00:12:53.700> a<00:12:53.760> sudden<00:12:53.880> you<00:12:54.060> have<00:12:54.240> this<00:12:54.480> thing<00:12:54.660> this 00:12:55.490 --> 00:12:55.500 align:start position:0% all of a sudden you have this thing this 00:12:55.500 --> 00:12:57.889 align:start position:0% all of a sudden you have this thing this provable<00:12:55.920> thing<00:12:56.339> that<00:12:56.940> is<00:12:57.120> deriving<00:12:57.480> data 00:12:57.889 --> 00:12:57.899 align:start position:0% provable thing that is deriving data 00:12:57.899 --> 00:13:00.530 align:start position:0% provable thing that is deriving data from<00:12:58.079> layer<00:12:58.440> one<00:12:58.560> and<00:12:59.339> is<00:12:59.519> generating<00:13:00.180> some 00:13:00.530 --> 00:13:00.540 align:start position:0% from layer one and is generating some 00:13:00.540 --> 00:13:03.410 align:start position:0% from layer one and is generating some sort<00:13:00.720> of<00:13:00.839> you<00:13:01.320> know<00:13:01.380> State<00:13:02.100> on<00:13:02.339> Layer<00:13:02.639> Two<00:13:02.820> and 00:13:03.410 --> 00:13:03.420 align:start position:0% sort of you know State on Layer Two and 00:13:03.420 --> 00:13:05.569 align:start position:0% sort of you know State on Layer Two and it<00:13:03.600> kind<00:13:03.720> of<00:13:03.839> looks<00:13:04.019> like<00:13:04.079> an<00:13:04.260> indexer<00:13:04.800> you<00:13:05.519> can 00:13:05.569 --> 00:13:05.579 align:start position:0% it kind of looks like an indexer you can 00:13:05.579 --> 00:13:07.730 align:start position:0% it kind of looks like an indexer you can essentially<00:13:06.060> build<00:13:06.360> an<00:13:06.660> entire<00:13:07.019> verifiable 00:13:07.730 --> 00:13:07.740 align:start position:0% essentially build an entire verifiable 00:13:07.740 --> 00:13:10.129 align:start position:0% essentially build an entire verifiable indexer<00:13:08.339> as<00:13:08.880> a<00:13:09.060> roll-up<00:13:09.360> are<00:13:09.839> they<00:13:10.019> just 00:13:10.129 --> 00:13:10.139 align:start position:0% indexer as a roll-up are they just 00:13:10.139 --> 00:13:12.110 align:start position:0% indexer as a roll-up are they just Roll-Ups<00:13:10.680> who<00:13:11.100> knows<00:13:11.399> I<00:13:11.639> think<00:13:11.760> secret 00:13:12.110 --> 00:13:12.120 align:start position:0% Roll-Ups who knows I think secret 00:13:12.120 --> 00:13:13.970 align:start position:0% Roll-Ups who knows I think secret indexes<00:13:12.839> are<00:13:13.019> kind<00:13:13.200> of<00:13:13.260> just<00:13:13.380> roll<00:13:13.560> ups<00:13:13.920> people 00:13:13.970 --> 00:13:13.980 align:start position:0% indexes are kind of just roll ups people 00:13:13.980 --> 00:13:15.769 align:start position:0% indexes are kind of just roll ups people just<00:13:14.220> didn't<00:13:14.339> realize<00:13:14.700> it 00:13:15.769 --> 00:13:15.779 align:start position:0% just didn't realize it 00:13:15.779 --> 00:13:16.430 align:start position:0% just didn't realize it um 00:13:16.430 --> 00:13:16.440 align:start position:0% um 00:13:16.440 --> 00:13:18.110 align:start position:0% um there's<00:13:16.920> a<00:13:17.100> lot<00:13:17.160> you<00:13:17.279> can<00:13:17.399> do<00:13:17.519> with<00:13:17.700> this<00:13:17.820> you 00:13:18.110 --> 00:13:18.120 align:start position:0% there's a lot you can do with this you 00:13:18.120 --> 00:13:20.449 align:start position:0% there's a lot you can do with this you can<00:13:18.240> derive<00:13:18.660> Layer<00:13:19.079> Two<00:13:19.260> payloads<00:13:20.160> from 00:13:20.449 --> 00:13:20.459 align:start position:0% can derive Layer Two payloads from 00:13:20.459 --> 00:13:22.250 align:start position:0% can derive Layer Two payloads from anything<00:13:20.820> on<00:13:21.180> layer<00:13:21.480> one<00:13:21.540> and<00:13:21.779> you<00:13:21.839> can<00:13:21.959> do<00:13:22.079> so 00:13:22.250 --> 00:13:22.260 align:start position:0% anything on layer one and you can do so 00:13:22.260 --> 00:13:23.870 align:start position:0% anything on layer one and you can do so much<00:13:22.380> with<00:13:22.560> that 00:13:23.870 --> 00:13:23.880 align:start position:0% much with that 00:13:23.880 --> 00:13:26.150 align:start position:0% much with that all<00:13:24.420> right<00:13:24.600> section<00:13:24.899> 4C<00:13:25.260> it<00:13:25.500> skipped<00:13:25.860> section 00:13:26.150 --> 00:13:26.160 align:start position:0% all right section 4C it skipped section 00:13:26.160 --> 00:13:28.910 align:start position:0% all right section 4C it skipped section three<00:13:26.399> this<00:13:26.820> is<00:13:27.019> uh<00:13:28.019> this<00:13:28.320> is<00:13:28.440> whatever 00:13:28.910 --> 00:13:28.920 align:start position:0% three this is uh this is whatever 00:13:28.920 --> 00:13:30.889 align:start position:0% three this is uh this is whatever section<00:13:29.519> three<00:13:29.820> four 00:13:30.889 --> 00:13:30.899 align:start position:0% section three four 00:13:30.899 --> 00:13:32.629 align:start position:0% section three four um<00:13:31.019> what<00:13:31.320> is<00:13:31.440> the<00:13:31.560> execution<00:13:31.920> layer<00:13:32.279> let's<00:13:32.459> get 00:13:32.629 --> 00:13:32.639 align:start position:0% um what is the execution layer let's get 00:13:32.639 --> 00:13:34.970 align:start position:0% um what is the execution layer let's get on<00:13:32.760> to<00:13:32.940> it<00:13:33.120> it<00:13:33.660> is<00:13:33.899> what<00:13:34.139> you<00:13:34.260> think<00:13:34.440> it<00:13:34.620> is<00:13:34.740> the 00:13:34.970 --> 00:13:34.980 align:start position:0% on to it it is what you think it is the 00:13:34.980 --> 00:13:36.410 align:start position:0% on to it it is what you think it is the execution<00:13:35.399> is<00:13:35.639> what<00:13:35.820> you<00:13:35.940> think<00:13:36.060> of<00:13:36.180> it<00:13:36.300> is 00:13:36.410 --> 00:13:36.420 align:start position:0% execution is what you think of it is 00:13:36.420 --> 00:13:38.690 align:start position:0% execution is what you think of it is it's<00:13:36.959> the<00:13:37.260> interesting<00:13:37.740> part<00:13:38.100> of<00:13:38.339> the<00:13:38.579> state 00:13:38.690 --> 00:13:38.700 align:start position:0% it's the interesting part of the state 00:13:38.700 --> 00:13:40.610 align:start position:0% it's the interesting part of the state transition<00:13:39.180> function<00:13:39.660> it's<00:13:39.839> the<00:13:40.139> fun<00:13:40.320> stuff 00:13:40.610 --> 00:13:40.620 align:start position:0% transition function it's the fun stuff 00:13:40.620 --> 00:13:41.990 align:start position:0% transition function it's the fun stuff it's<00:13:40.800> where<00:13:41.040> you<00:13:41.160> get<00:13:41.279> to<00:13:41.399> do<00:13:41.519> your<00:13:41.760> crazy 00:13:41.990 --> 00:13:42.000 align:start position:0% it's where you get to do your crazy 00:13:42.000 --> 00:13:45.410 align:start position:0% it's where you get to do your crazy crazy<00:13:42.779> applications<00:13:43.579> of<00:13:44.579> course<00:13:44.760> in<00:13:45.300> this 00:13:45.410 --> 00:13:45.420 align:start position:0% crazy applications of course in this 00:13:45.420 --> 00:13:47.150 align:start position:0% crazy applications of course in this system<00:13:45.660> it's<00:13:46.019> also<00:13:46.320> represented<00:13:46.800> as<00:13:46.980> a 00:13:47.150 --> 00:13:47.160 align:start position:0% system it's also represented as a 00:13:47.160 --> 00:13:49.310 align:start position:0% system it's also represented as a function<00:13:47.459> in<00:13:48.060> a<00:13:48.240> very<00:13:48.300> abstract<00:13:48.660> way<00:13:48.899> it<00:13:49.079> looks 00:13:49.310 --> 00:13:49.320 align:start position:0% function in a very abstract way it looks 00:13:49.320 --> 00:13:51.290 align:start position:0% function in a very abstract way it looks like<00:13:49.440> this<00:13:49.620> you<00:13:50.160> take<00:13:50.339> the<00:13:50.579> previous<00:13:50.700> state<00:13:51.120> of 00:13:51.290 --> 00:13:51.300 align:start position:0% like this you take the previous state of 00:13:51.300 --> 00:13:53.629 align:start position:0% like this you take the previous state of your<00:13:51.480> system<00:13:51.660> you<00:13:52.440> take<00:13:52.620> a<00:13:52.860> payload<00:13:53.339> that<00:13:53.519> was 00:13:53.629 --> 00:13:53.639 align:start position:0% your system you take a payload that was 00:13:53.639 --> 00:13:55.790 align:start position:0% your system you take a payload that was derived<00:13:54.060> by<00:13:54.240> the<00:13:54.420> derivation<00:13:54.899> layer<00:13:55.320> and 00:13:55.790 --> 00:13:55.800 align:start position:0% derived by the derivation layer and 00:13:55.800 --> 00:13:57.110 align:start position:0% derived by the derivation layer and you're<00:13:55.860> going<00:13:56.040> to<00:13:56.220> transition<00:13:56.579> your<00:13:57.000> state 00:13:57.110 --> 00:13:57.120 align:start position:0% you're going to transition your state 00:13:57.120 --> 00:13:58.670 align:start position:0% you're going to transition your state into<00:13:57.420> the<00:13:57.600> next<00:13:57.720> state 00:13:58.670 --> 00:13:58.680 align:start position:0% into the next state 00:13:58.680 --> 00:14:01.430 align:start position:0% into the next state this<00:13:59.339> is<00:13:59.519> very<00:13:59.820> abstract<00:14:00.240> this<00:14:00.600> is<00:14:00.779> not<00:14:00.959> you 00:14:01.430 --> 00:14:01.440 align:start position:0% this is very abstract this is not you 00:14:01.440 --> 00:14:03.290 align:start position:0% this is very abstract this is not you know<00:14:01.560> in<00:14:01.800> in<00:14:02.040> this<00:14:02.339> statement<00:14:02.639> it<00:14:02.940> says 00:14:03.290 --> 00:14:03.300 align:start position:0% know in in this statement it says 00:14:03.300 --> 00:14:04.910 align:start position:0% know in in this statement it says nothing<00:14:03.420> about<00:14:03.660> the<00:14:03.899> evm<00:14:04.320> it<00:14:04.500> says<00:14:04.740> nothing 00:14:04.910 --> 00:14:04.920 align:start position:0% nothing about the evm it says nothing 00:14:04.920 --> 00:14:06.829 align:start position:0% nothing about the evm it says nothing about<00:14:05.160> the<00:14:05.940> actual<00:14:06.240> State<00:14:06.420> transition 00:14:06.829 --> 00:14:06.839 align:start position:0% about the actual State transition 00:14:06.839 --> 00:14:08.810 align:start position:0% about the actual State transition function<00:14:07.260> it<00:14:07.440> just<00:14:07.620> says<00:14:07.860> you<00:14:08.220> need<00:14:08.399> a<00:14:08.639> state 00:14:08.810 --> 00:14:08.820 align:start position:0% function it just says you need a state 00:14:08.820 --> 00:14:11.569 align:start position:0% function it just says you need a state transition<00:14:09.240> function 00:14:11.569 --> 00:14:11.579 align:start position:0% transition function 00:14:11.579 --> 00:14:13.610 align:start position:0% transition function derivation<00:14:12.300> and<00:14:12.600> execution<00:14:13.019> in<00:14:13.320> this<00:14:13.440> system 00:14:13.610 --> 00:14:13.620 align:start position:0% derivation and execution in this system 00:14:13.620 --> 00:14:15.829 align:start position:0% derivation and execution in this system work<00:14:13.920> together<00:14:14.160> they<00:14:15.000> work<00:14:15.180> together<00:14:15.360> to<00:14:15.660> form 00:14:15.829 --> 00:14:15.839 align:start position:0% work together they work together to form 00:14:15.839 --> 00:14:17.030 align:start position:0% work together they work together to form something<00:14:16.139> that<00:14:16.380> I<00:14:16.500> call<00:14:16.620> the<00:14:16.800> state 00:14:17.030 --> 00:14:17.040 align:start position:0% something that I call the state 00:14:17.040 --> 00:14:19.970 align:start position:0% something that I call the state transition<00:14:17.399> function<00:14:17.820> loop<00:14:18.620> the<00:14:19.620> loop<00:14:19.860> is 00:14:19.970 --> 00:14:19.980 align:start position:0% transition function loop the loop is 00:14:19.980 --> 00:14:22.190 align:start position:0% transition function loop the loop is very<00:14:20.220> simple<00:14:20.459> when<00:14:21.240> there's<00:14:21.420> a<00:14:21.720> new<00:14:21.899> element 00:14:22.190 --> 00:14:22.200 align:start position:0% very simple when there's a new element 00:14:22.200 --> 00:14:24.050 align:start position:0% very simple when there's a new element that<00:14:22.620> comes<00:14:22.920> in<00:14:23.040> from<00:14:23.339> the<00:14:23.459> date<00:14:23.579> availability 00:14:24.050 --> 00:14:24.060 align:start position:0% that comes in from the date availability 00:14:24.060 --> 00:14:25.850 align:start position:0% that comes in from the date availability layer<00:14:24.540> so<00:14:24.720> let's<00:14:24.839> say<00:14:25.019> a<00:14:25.200> new<00:14:25.320> block<00:14:25.560> was 00:14:25.850 --> 00:14:25.860 align:start position:0% layer so let's say a new block was 00:14:25.860 --> 00:14:28.430 align:start position:0% layer so let's say a new block was produced<00:14:26.279> on<00:14:26.519> ethereum<00:14:27.540> we're<00:14:27.959> going<00:14:28.139> to<00:14:28.260> pass 00:14:28.430 --> 00:14:28.440 align:start position:0% produced on ethereum we're going to pass 00:14:28.440 --> 00:14:30.829 align:start position:0% produced on ethereum we're going to pass that<00:14:28.740> into<00:14:29.100> the<00:14:29.279> derivation<00:14:29.820> function<00:14:30.300> and 00:14:30.829 --> 00:14:30.839 align:start position:0% that into the derivation function and 00:14:30.839 --> 00:14:32.269 align:start position:0% that into the derivation function and the<00:14:31.019> derivation<00:14:31.440> function<00:14:31.800> is<00:14:31.920> going<00:14:32.100> to<00:14:32.160> do 00:14:32.269 --> 00:14:32.279 align:start position:0% the derivation function is going to do 00:14:32.279 --> 00:14:34.370 align:start position:0% the derivation function is going to do one<00:14:32.459> of<00:14:32.579> two<00:14:32.760> things<00:14:33.000> either<00:14:33.720> the<00:14:33.959> derivation 00:14:34.370 --> 00:14:34.380 align:start position:0% one of two things either the derivation 00:14:34.380 --> 00:14:36.590 align:start position:0% one of two things either the derivation function<00:14:34.740> looks<00:14:35.100> at<00:14:35.220> that<00:14:35.339> block<00:14:35.579> and<00:14:36.180> it<00:14:36.300> says 00:14:36.590 --> 00:14:36.600 align:start position:0% function looks at that block and it says 00:14:36.600 --> 00:14:38.150 align:start position:0% function looks at that block and it says Ah<00:14:37.200> there's<00:14:37.380> nothing<00:14:37.560> in<00:14:37.860> here<00:14:37.980> there's 00:14:38.150 --> 00:14:38.160 align:start position:0% Ah there's nothing in here there's 00:14:38.160 --> 00:14:39.710 align:start position:0% Ah there's nothing in here there's nothing<00:14:38.399> to<00:14:38.579> put<00:14:38.700> into<00:14:38.880> the<00:14:39.060> layer<00:14:39.300> 2<00:14:39.420> system 00:14:39.710 --> 00:14:39.720 align:start position:0% nothing to put into the layer 2 system 00:14:39.720 --> 00:14:41.689 align:start position:0% nothing to put into the layer 2 system there's<00:14:39.959> no<00:14:40.139> payloads<00:14:40.680> to<00:14:40.800> derive<00:14:41.160> you<00:14:41.579> know 00:14:41.689 --> 00:14:41.699 align:start position:0% there's no payloads to derive you know 00:14:41.699 --> 00:14:43.189 align:start position:0% there's no payloads to derive you know no<00:14:41.880> transactions<00:14:42.420> were<00:14:42.600> published<00:14:42.959> to<00:14:43.079> the 00:14:43.189 --> 00:14:43.199 align:start position:0% no transactions were published to the 00:14:43.199 --> 00:14:45.050 align:start position:0% no transactions were published to the special<00:14:43.380> sequencer<00:14:43.860> address<00:14:44.100> whatever 00:14:45.050 --> 00:14:45.060 align:start position:0% special sequencer address whatever 00:14:45.060 --> 00:14:46.550 align:start position:0% special sequencer address whatever and<00:14:45.540> in<00:14:45.660> that<00:14:45.839> case<00:14:45.899> it's<00:14:46.079> just<00:14:46.260> going<00:14:46.380> to<00:14:46.440> wait 00:14:46.550 --> 00:14:46.560 align:start position:0% and in that case it's just going to wait 00:14:46.560 --> 00:14:48.290 align:start position:0% and in that case it's just going to wait for<00:14:46.800> the<00:14:47.040> next<00:14:47.160> element<00:14:47.459> to<00:14:47.880> come<00:14:48.000> from<00:14:48.180> the 00:14:48.290 --> 00:14:48.300 align:start position:0% for the next element to come from the 00:14:48.300 --> 00:14:49.730 align:start position:0% for the next element to come from the data<00:14:48.540> availability<00:14:48.839> layer<00:14:49.199> to<00:14:49.380> look<00:14:49.500> for<00:14:49.620> the 00:14:49.730 --> 00:14:49.740 align:start position:0% data availability layer to look for the 00:14:49.740 --> 00:14:51.710 align:start position:0% data availability layer to look for the next<00:14:49.860> thing<00:14:50.040> that<00:14:50.220> it<00:14:50.339> might<00:14:50.459> derive 00:14:51.710 --> 00:14:51.720 align:start position:0% next thing that it might derive 00:14:51.720 --> 00:14:53.870 align:start position:0% next thing that it might derive then<00:14:52.320> the<00:14:52.740> other<00:14:52.800> option<00:14:53.100> it<00:14:53.279> has<00:14:53.459> is<00:14:53.639> to 00:14:53.870 --> 00:14:53.880 align:start position:0% then the other option it has is to 00:14:53.880 --> 00:14:56.750 align:start position:0% then the other option it has is to return<00:14:54.060> a<00:14:54.480> payload<00:14:54.959> if<00:14:55.680> it<00:14:55.800> returns<00:14:56.160> a<00:14:56.279> payload 00:14:56.750 --> 00:14:56.760 align:start position:0% return a payload if it returns a payload 00:14:56.760 --> 00:14:58.970 align:start position:0% return a payload if it returns a payload it's<00:14:56.940> going<00:14:57.180> to<00:14:57.300> pass<00:14:57.480> that<00:14:57.720> payload<00:14:58.320> into<00:14:58.740> the 00:14:58.970 --> 00:14:58.980 align:start position:0% it's going to pass that payload into the 00:14:58.980 --> 00:15:01.069 align:start position:0% it's going to pass that payload into the execution<00:14:59.459> function<00:14:59.940> where<00:15:00.540> the<00:15:00.720> state<00:15:00.839> is 00:15:01.069 --> 00:15:01.079 align:start position:0% execution function where the state is 00:15:01.079 --> 00:15:02.689 align:start position:0% execution function where the state is going<00:15:01.199> to<00:15:01.320> get<00:15:01.440> updated<00:15:01.860> then<00:15:02.339> we're<00:15:02.459> going<00:15:02.579> to 00:15:02.689 --> 00:15:02.699 align:start position:0% going to get updated then we're going to 00:15:02.699 --> 00:15:04.550 align:start position:0% going to get updated then we're going to go<00:15:02.880> back<00:15:03.060> to<00:15:03.240> the<00:15:03.420> derivation<00:15:03.839> function<00:15:04.260> see 00:15:04.550 --> 00:15:04.560 align:start position:0% go back to the derivation function see 00:15:04.560 --> 00:15:06.530 align:start position:0% go back to the derivation function see if<00:15:04.740> there's<00:15:04.860> anything<00:15:05.100> new<00:15:05.399> to<00:15:05.639> derive<00:15:06.000> and 00:15:06.530 --> 00:15:06.540 align:start position:0% if there's anything new to derive and 00:15:06.540 --> 00:15:08.150 align:start position:0% if there's anything new to derive and this<00:15:06.720> thing<00:15:06.899> just<00:15:07.139> repeats<00:15:07.560> and<00:15:07.680> repeats<00:15:08.040> and 00:15:08.150 --> 00:15:08.160 align:start position:0% this thing just repeats and repeats and 00:15:08.160 --> 00:15:09.410 align:start position:0% this thing just repeats and repeats and repeats<00:15:08.459> and<00:15:08.579> this<00:15:08.820> is<00:15:08.880> your<00:15:09.120> entire 00:15:09.410 --> 00:15:09.420 align:start position:0% repeats and this is your entire 00:15:09.420 --> 00:15:11.449 align:start position:0% repeats and this is your entire transition<00:15:09.899> function<00:15:10.380> if<00:15:11.040> you<00:15:11.220> want<00:15:11.279> to<00:15:11.399> see 00:15:11.449 --> 00:15:11.459 align:start position:0% transition function if you want to see 00:15:11.459 --> 00:15:13.069 align:start position:0% transition function if you want to see that<00:15:11.639> as<00:15:11.820> little<00:15:12.000> drawn<00:15:12.480> out<00:15:12.660> image 00:15:13.069 --> 00:15:13.079 align:start position:0% that as little drawn out image 00:15:13.079 --> 00:15:14.810 align:start position:0% that as little drawn out image essentially<00:15:13.920> we<00:15:14.339> have<00:15:14.399> the<00:15:14.519> data 00:15:14.810 --> 00:15:14.820 align:start position:0% essentially we have the data 00:15:14.820 --> 00:15:16.970 align:start position:0% essentially we have the data availability<00:15:15.180> layer<00:15:15.660> a<00:15:16.139> new<00:15:16.199> blob<00:15:16.560> comes<00:15:16.920> in 00:15:16.970 --> 00:15:16.980 align:start position:0% availability layer a new blob comes in 00:15:16.980 --> 00:15:19.189 align:start position:0% availability layer a new blob comes in we<00:15:17.220> derive<00:15:17.579> something<00:15:17.880> is<00:15:18.480> it<00:15:18.600> null<00:15:18.959> then 00:15:19.189 --> 00:15:19.199 align:start position:0% we derive something is it null then 00:15:19.199 --> 00:15:20.509 align:start position:0% we derive something is it null then let's<00:15:19.380> just<00:15:19.560> wait<00:15:19.680> for<00:15:19.860> the<00:15:19.980> next<00:15:20.100> thing<00:15:20.339> to 00:15:20.509 --> 00:15:20.519 align:start position:0% let's just wait for the next thing to 00:15:20.519 --> 00:15:22.610 align:start position:0% let's just wait for the next thing to come<00:15:20.639> in<00:15:20.820> if<00:15:21.300> it's<00:15:21.420> not<00:15:21.660> null<00:15:22.079> then<00:15:22.500> we're 00:15:22.610 --> 00:15:22.620 align:start position:0% come in if it's not null then we're 00:15:22.620 --> 00:15:24.470 align:start position:0% come in if it's not null then we're going<00:15:22.740> to<00:15:22.860> derive<00:15:23.160> a<00:15:23.339> payload<00:15:23.820> and<00:15:24.240> then<00:15:24.300> we 00:15:24.470 --> 00:15:24.480 align:start position:0% going to derive a payload and then we 00:15:24.480 --> 00:15:26.509 align:start position:0% going to derive a payload and then we have<00:15:24.600> to<00:15:24.720> execute<00:15:25.079> that<00:15:25.260> payload<00:15:25.800> see<00:15:26.220> if<00:15:26.399> we 00:15:26.509 --> 00:15:26.519 align:start position:0% have to execute that payload see if we 00:15:26.519 --> 00:15:28.310 align:start position:0% have to execute that payload see if we derive<00:15:26.820> anything<00:15:27.000> new<00:15:27.300> it<00:15:27.600> goes<00:15:27.839> in<00:15:27.959> this<00:15:28.079> you 00:15:28.310 --> 00:15:28.320 align:start position:0% derive anything new it goes in this you 00:15:28.320 --> 00:15:30.110 align:start position:0% derive anything new it goes in this you know<00:15:28.440> beautiful<00:15:28.740> figure<00:15:29.220> eight<00:15:29.519> for<00:15:29.880> all<00:15:30.000> of 00:15:30.110 --> 00:15:30.120 align:start position:0% know beautiful figure eight for all of 00:15:30.120 --> 00:15:32.569 align:start position:0% know beautiful figure eight for all of time<00:15:30.360> right<00:15:30.779> this<00:15:31.380> is<00:15:31.500> how<00:15:31.740> derivation<00:15:32.339> and 00:15:32.569 --> 00:15:32.579 align:start position:0% time right this is how derivation and 00:15:32.579 --> 00:15:34.910 align:start position:0% time right this is how derivation and execution<00:15:33.000> work<00:15:33.360> together<00:15:33.600> to<00:15:34.500> form<00:15:34.680> the 00:15:34.910 --> 00:15:34.920 align:start position:0% execution work together to form the 00:15:34.920 --> 00:15:37.730 align:start position:0% execution work together to form the state<00:15:35.100> transition<00:15:35.519> function<00:15:35.880> Loop 00:15:37.730 --> 00:15:37.740 align:start position:0% state transition function Loop 00:15:37.740 --> 00:15:40.069 align:start position:0% state transition function Loop all<00:15:38.339> right<00:15:38.459> execution<00:15:39.240> in<00:15:39.480> Bedrock<00:15:39.959> let's 00:15:40.069 --> 00:15:40.079 align:start position:0% all right execution in Bedrock let's 00:15:40.079 --> 00:15:41.329 align:start position:0% all right execution in Bedrock let's make<00:15:40.260> this<00:15:40.440> a<00:15:40.560> little<00:15:40.620> more<00:15:40.800> concrete<00:15:41.160> how 00:15:41.329 --> 00:15:41.339 align:start position:0% make this a little more concrete how 00:15:41.339 --> 00:15:42.590 align:start position:0% make this a little more concrete how does<00:15:41.459> this<00:15:41.579> apply<00:15:41.880> to<00:15:41.940> what<00:15:42.120> optimism<00:15:42.480> is 00:15:42.590 --> 00:15:42.600 align:start position:0% does this apply to what optimism is 00:15:42.600 --> 00:15:43.490 align:start position:0% does this apply to what optimism is doing 00:15:43.490 --> 00:15:43.500 align:start position:0% doing 00:15:43.500 --> 00:15:45.889 align:start position:0% doing in<00:15:43.920> optimism<00:15:44.339> it's<00:15:44.519> just<00:15:44.699> the<00:15:44.760> ebm<00:15:45.240> we<00:15:45.779> just 00:15:45.889 --> 00:15:45.899 align:start position:0% in optimism it's just the ebm we just 00:15:45.899 --> 00:15:47.810 align:start position:0% in optimism it's just the ebm we just changed<00:15:46.199> the<00:15:46.320> evm<00:15:46.680> we<00:15:46.920> you<00:15:47.160> know<00:15:47.279> mostly<00:15:47.639> it's 00:15:47.810 --> 00:15:47.820 align:start position:0% changed the evm we you know mostly it's 00:15:47.820 --> 00:15:49.310 align:start position:0% changed the evm we you know mostly it's just<00:15:48.000> dbm 00:15:49.310 --> 00:15:49.320 align:start position:0% just dbm 00:15:49.320 --> 00:15:51.290 align:start position:0% just dbm um we<00:15:49.620> added<00:15:49.920> a<00:15:50.100> few<00:15:50.279> things<00:15:50.579> that<00:15:50.940> you<00:15:51.120> need 00:15:51.290 --> 00:15:51.300 align:start position:0% um we added a few things that you need 00:15:51.300 --> 00:15:53.569 align:start position:0% um we added a few things that you need to<00:15:51.480> do<00:15:51.720> to<00:15:52.079> make<00:15:52.380> a<00:15:52.800> system<00:15:52.980> roll<00:15:53.339> up 00:15:53.569 --> 00:15:53.579 align:start position:0% to do to make a system roll up 00:15:53.579 --> 00:15:56.590 align:start position:0% to do to make a system roll up compatible<00:15:54.120> the<00:15:54.839> primary<00:15:55.260> diff<00:15:55.620> in<00:15:56.100> our<00:15:56.279> div 00:15:56.590 --> 00:15:56.600 align:start position:0% compatible the primary diff in our div 00:15:56.600 --> 00:15:59.210 align:start position:0% compatible the primary diff in our div is<00:15:57.600> the<00:15:57.959> addition<00:15:58.199> of<00:15:58.500> a<00:15:58.680> new<00:15:58.800> transaction 00:15:59.210 --> 00:15:59.220 align:start position:0% is the addition of a new transaction 00:15:59.220 --> 00:16:01.189 align:start position:0% is the addition of a new transaction type<00:15:59.519> called<00:15:59.760> a<00:16:00.000> deposit<00:16:00.420> transaction<00:16:00.839> type 00:16:01.189 --> 00:16:01.199 align:start position:0% type called a deposit transaction type 00:16:01.199 --> 00:16:04.069 align:start position:0% type called a deposit transaction type which<00:16:01.740> allows<00:16:02.100> contracts<00:16:02.639> on<00:16:02.820> layer<00:16:03.120> 1<00:16:03.300> to 00:16:04.069 --> 00:16:04.079 align:start position:0% which allows contracts on layer 1 to 00:16:04.079 --> 00:16:05.870 align:start position:0% which allows contracts on layer 1 to interact<00:16:04.500> with<00:16:04.800> Layer<00:16:05.160> Two<00:16:05.279> right<00:16:05.579> it's<00:16:05.760> what 00:16:05.870 --> 00:16:05.880 align:start position:0% interact with Layer Two right it's what 00:16:05.880 --> 00:16:07.430 align:start position:0% interact with Layer Two right it's what allows<00:16:06.180> you<00:16:06.240> to<00:16:06.420> perform<00:16:06.540> deposits<00:16:07.260> it's 00:16:07.430 --> 00:16:07.440 align:start position:0% allows you to perform deposits it's 00:16:07.440 --> 00:16:08.930 align:start position:0% allows you to perform deposits it's essentially<00:16:07.740> the<00:16:07.920> message<00:16:08.100> passing<00:16:08.639> layer 00:16:08.930 --> 00:16:08.940 align:start position:0% essentially the message passing layer 00:16:08.940 --> 00:16:11.210 align:start position:0% essentially the message passing layer you<00:16:09.600> need<00:16:09.779> this<00:16:10.019> in<00:16:10.199> the<00:16:10.320> evm<00:16:10.740> right<00:16:10.920> now<00:16:11.040> I 00:16:11.210 --> 00:16:11.220 align:start position:0% you need this in the evm right now I 00:16:11.220 --> 00:16:12.410 align:start position:0% you need this in the evm right now I don't<00:16:11.339> know<00:16:11.459> that<00:16:11.579> we<00:16:11.760> know<00:16:11.820> of<00:16:11.940> a<00:16:12.120> way<00:16:12.180> to<00:16:12.300> do 00:16:12.410 --> 00:16:12.420 align:start position:0% don't know that we know of a way to do 00:16:12.420 --> 00:16:14.990 align:start position:0% don't know that we know of a way to do it<00:16:12.540> without<00:16:13.019> adding<00:16:13.560> this<00:16:13.680> diff<00:16:13.920> but<00:16:14.579> it's<00:16:14.760> a 00:16:14.990 --> 00:16:15.000 align:start position:0% it without adding this diff but it's a 00:16:15.000 --> 00:16:17.870 align:start position:0% it without adding this diff but it's a very<00:16:15.180> very<00:16:15.360> very<00:16:15.540> small<00:16:15.899> diff 00:16:17.870 --> 00:16:17.880 align:start position:0% very very very small diff 00:16:17.880 --> 00:16:19.670 align:start position:0% very very very small diff um<00:16:17.940> and<00:16:18.300> essentially<00:16:18.600> we're<00:16:18.899> now<00:16:19.139> at<00:16:19.440> less 00:16:19.670 --> 00:16:19.680 align:start position:0% um and essentially we're now at less 00:16:19.680 --> 00:16:21.170 align:start position:0% um and essentially we're now at less than<00:16:19.800> a<00:16:19.980> thousand<00:16:20.160> lines<00:16:20.399> of<00:16:20.579> code<00:16:20.699> in<00:16:20.940> a 00:16:21.170 --> 00:16:21.180 align:start position:0% than a thousand lines of code in a 00:16:21.180 --> 00:16:24.170 align:start position:0% than a thousand lines of code in a segment<00:16:21.800> uh<00:16:22.800> here's<00:16:23.160> the<00:16:23.339> diff<00:16:23.519> like<00:16:23.880> Carl 00:16:24.170 --> 00:16:24.180 align:start position:0% segment uh here's the diff like Carl 00:16:24.180 --> 00:16:26.810 align:start position:0% segment uh here's the diff like Carl showed<00:16:24.720> and<00:16:25.079> actually<00:16:25.260> 71<00:16:26.040> of<00:16:26.279> those<00:16:26.459> lines 00:16:26.810 --> 00:16:26.820 align:start position:0% showed and actually 71 of those lines 00:16:26.820 --> 00:16:30.050 align:start position:0% showed and actually 71 of those lines are<00:16:27.540> this<00:16:27.959> uh<00:16:28.380> Circle<00:16:28.500> CI<00:16:29.040> config<00:16:29.519> file<00:16:29.820> so 00:16:30.050 --> 00:16:30.060 align:start position:0% are this uh Circle CI config file so 00:16:30.060 --> 00:16:34.430 align:start position:0% are this uh Circle CI config file so it's<00:16:30.240> 750.<00:16:31.399> uh<00:16:32.399> this<00:16:33.060> gives<00:16:33.420> you<00:16:33.600> a<00:16:34.260> really 00:16:34.430 --> 00:16:34.440 align:start position:0% it's 750. uh this gives you a really 00:16:34.440 --> 00:16:35.750 align:start position:0% it's 750. uh this gives you a really important<00:16:34.860> thing<00:16:35.040> because<00:16:35.279> it<00:16:35.519> gives<00:16:35.639> you 00:16:35.750 --> 00:16:35.760 align:start position:0% important thing because it gives you 00:16:35.760 --> 00:16:37.370 align:start position:0% important thing because it gives you support<00:16:36.000> for<00:16:36.300> multiple<00:16:36.660> clients<00:16:37.019> it<00:16:37.139> means 00:16:37.370 --> 00:16:37.380 align:start position:0% support for multiple clients it means 00:16:37.380 --> 00:16:40.490 align:start position:0% support for multiple clients it means that<00:16:37.500> we<00:16:37.680> can<00:16:37.920> very<00:16:38.339> easily<00:16:38.880> Port<00:16:39.180> our<00:16:39.480> diff<00:16:39.720> to 00:16:40.490 --> 00:16:40.500 align:start position:0% that we can very easily Port our diff to 00:16:40.500 --> 00:16:42.530 align:start position:0% that we can very easily Port our diff to multiple<00:16:40.920> clients<00:16:41.459> and<00:16:41.940> if<00:16:42.060> you<00:16:42.240> don't<00:16:42.360> have 00:16:42.530 --> 00:16:42.540 align:start position:0% multiple clients and if you don't have 00:16:42.540 --> 00:16:45.110 align:start position:0% multiple clients and if you don't have multiple<00:16:43.019> clients<00:16:43.440> running<00:16:43.740> a<00:16:44.399> bug<00:16:44.519> in<00:16:44.880> a 00:16:45.110 --> 00:16:45.120 align:start position:0% multiple clients running a bug in a 00:16:45.120 --> 00:16:46.910 align:start position:0% multiple clients running a bug in a single<00:16:45.360> client<00:16:45.600> can<00:16:45.839> be<00:16:46.019> catastrophic<00:16:46.680> for 00:16:46.910 --> 00:16:46.920 align:start position:0% single client can be catastrophic for 00:16:46.920 --> 00:16:49.009 align:start position:0% single client can be catastrophic for your<00:16:47.100> roll<00:16:47.279> up<00:16:47.459> no<00:16:47.639> no<00:16:48.060> matter<00:16:48.300> how<00:16:48.600> good<00:16:48.779> the 00:16:49.009 --> 00:16:49.019 align:start position:0% your roll up no no matter how good the 00:16:49.019 --> 00:16:51.110 align:start position:0% your roll up no no matter how good the proofs<00:16:49.380> are<00:16:49.560> because<00:16:49.980> the<00:16:50.339> proofs<00:16:50.639> are<00:16:50.940> just 00:16:51.110 --> 00:16:51.120 align:start position:0% proofs are because the proofs are just 00:16:51.120 --> 00:16:53.870 align:start position:0% proofs are because the proofs are just confirming<00:16:51.660> the<00:16:51.839> execution<00:16:52.259> of<00:16:52.500> your<00:16:52.680> clients 00:16:53.870 --> 00:16:53.880 align:start position:0% confirming the execution of your clients 00:16:53.880 --> 00:16:55.730 align:start position:0% confirming the execution of your clients if<00:16:54.420> the<00:16:54.540> proofs<00:16:54.899> are<00:16:55.079> just<00:16:55.199> confirming<00:16:55.560> the 00:16:55.730 --> 00:16:55.740 align:start position:0% if the proofs are just confirming the 00:16:55.740 --> 00:16:57.470 align:start position:0% if the proofs are just confirming the execution<00:16:56.100> of<00:16:56.339> your<00:16:56.459> clients<00:16:56.820> and<00:16:57.240> there's<00:16:57.360> a 00:16:57.470 --> 00:16:57.480 align:start position:0% execution of your clients and there's a 00:16:57.480 --> 00:16:59.030 align:start position:0% execution of your clients and there's a bug<00:16:57.600> in<00:16:57.839> your<00:16:57.959> client<00:16:58.199> then<00:16:58.560> the<00:16:58.740> proof<00:16:58.920> is 00:16:59.030 --> 00:16:59.040 align:start position:0% bug in your client then the proof is 00:16:59.040 --> 00:17:00.769 align:start position:0% bug in your client then the proof is going<00:16:59.160> to<00:16:59.220> say<00:16:59.339> go<00:16:59.579> ahead<00:16:59.820> the<00:17:00.000> bug<00:17:00.180> executed 00:17:00.769 --> 00:17:00.779 align:start position:0% going to say go ahead the bug executed 00:17:00.779 --> 00:17:02.629 align:start position:0% going to say go ahead the bug executed correctly<00:17:01.079> and<00:17:01.259> nothing<00:17:01.500> matters<00:17:01.920> so<00:17:02.399> you 00:17:02.629 --> 00:17:02.639 align:start position:0% correctly and nothing matters so you 00:17:02.639 --> 00:17:05.210 align:start position:0% correctly and nothing matters so you need<00:17:02.940> client<00:17:03.420> diversity<00:17:04.020> and<00:17:04.500> having<00:17:04.799> this 00:17:05.210 --> 00:17:05.220 align:start position:0% need client diversity and having this 00:17:05.220 --> 00:17:07.610 align:start position:0% need client diversity and having this small<00:17:05.339> diff<00:17:05.579> is<00:17:05.880> a<00:17:06.000> critical<00:17:06.240> part<00:17:06.419> of<00:17:06.600> that 00:17:07.610 --> 00:17:07.620 align:start position:0% small diff is a critical part of that 00:17:07.620 --> 00:17:09.949 align:start position:0% small diff is a critical part of that if<00:17:08.339> you<00:17:08.520> want<00:17:08.760> I<00:17:09.299> don't<00:17:09.480> know<00:17:09.540> if<00:17:09.600> people<00:17:09.780> can 00:17:09.949 --> 00:17:09.959 align:start position:0% if you want I don't know if people can 00:17:09.959 --> 00:17:12.590 align:start position:0% if you want I don't know if people can scan<00:17:10.260> this<00:17:10.439> ship<00:17:10.740> scan<00:17:11.100> this<00:17:11.579> is<00:17:11.640> the<00:17:11.880> diff<00:17:12.000> or 00:17:12.590 --> 00:17:12.600 align:start position:0% scan this ship scan this is the diff or 00:17:12.600 --> 00:17:15.230 align:start position:0% scan this ship scan this is the diff or you<00:17:12.720> can<00:17:12.839> go<00:17:12.959> on<00:17:13.199> our<00:17:13.620> GitHub<00:17:13.919> repo<00:17:14.339> op<00:17:14.640> Geth 00:17:15.230 --> 00:17:15.240 align:start position:0% you can go on our GitHub repo op Geth 00:17:15.240 --> 00:17:17.569 align:start position:0% you can go on our GitHub repo op Geth and<00:17:15.900> you<00:17:16.140> can<00:17:16.260> find<00:17:16.439> it's<00:17:16.740> a<00:17:16.919> single<00:17:17.220> commit 00:17:17.569 --> 00:17:17.579 align:start position:0% and you can find it's a single commit 00:17:17.579 --> 00:17:19.669 align:start position:0% and you can find it's a single commit which<00:17:17.819> makes<00:17:18.000> it<00:17:18.240> extremely<00:17:18.600> easy<00:17:18.839> to<00:17:19.140> rebase 00:17:19.669 --> 00:17:19.679 align:start position:0% which makes it extremely easy to rebase 00:17:19.679 --> 00:17:22.490 align:start position:0% which makes it extremely easy to rebase onto<00:17:20.579> the<00:17:21.120> latest<00:17:21.240> head<00:17:21.720> state<00:17:21.959> of<00:17:22.140> ethereum 00:17:22.490 --> 00:17:22.500 align:start position:0% onto the latest head state of ethereum 00:17:22.500 --> 00:17:26.510 align:start position:0% onto the latest head state of ethereum of<00:17:22.740> go<00:17:23.699> ethereum<00:17:24.679> makes<00:17:25.679> it<00:17:25.919> super<00:17:26.040> easy<00:17:26.280> to 00:17:26.510 --> 00:17:26.520 align:start position:0% of go ethereum makes it super easy to 00:17:26.520 --> 00:17:28.069 align:start position:0% of go ethereum makes it super easy to deal<00:17:26.880> with<00:17:27.120> so<00:17:27.360> all<00:17:27.600> right<00:17:27.780> let's<00:17:27.900> continue 00:17:28.069 --> 00:17:28.079 align:start position:0% deal with so all right let's continue 00:17:28.079 --> 00:17:29.450 align:start position:0% deal with so all right let's continue because<00:17:28.380> I<00:17:28.559> don't<00:17:28.620> have<00:17:28.740> a<00:17:28.860> lot<00:17:28.919> of<00:17:29.100> time<00:17:29.220> left 00:17:29.450 --> 00:17:29.460 align:start position:0% because I don't have a lot of time left 00:17:29.460 --> 00:17:32.090 align:start position:0% because I don't have a lot of time left just<00:17:30.299> because<00:17:30.480> we're<00:17:30.840> doing<00:17:31.140> the<00:17:31.320> evm<00:17:31.799> doesn't 00:17:32.090 --> 00:17:32.100 align:start position:0% just because we're doing the evm doesn't 00:17:32.100 --> 00:17:34.610 align:start position:0% just because we're doing the evm doesn't mean<00:17:32.400> you<00:17:32.760> have<00:17:32.880> to<00:17:33.059> do<00:17:33.179> the<00:17:33.480> evm<00:17:33.960> this 00:17:34.610 --> 00:17:34.620 align:start position:0% mean you have to do the evm this 00:17:34.620 --> 00:17:36.350 align:start position:0% mean you have to do the evm this approach<00:17:34.919> is<00:17:35.280> really<00:17:35.640> really<00:17:35.820> flexible 00:17:36.350 --> 00:17:36.360 align:start position:0% approach is really really flexible 00:17:36.360 --> 00:17:38.210 align:start position:0% approach is really really flexible there's<00:17:36.780> nothing<00:17:37.020> in<00:17:37.380> this<00:17:37.559> that<00:17:37.740> says<00:17:37.980> you 00:17:38.210 --> 00:17:38.220 align:start position:0% there's nothing in this that says you 00:17:38.220 --> 00:17:40.190 align:start position:0% there's nothing in this that says you have<00:17:38.340> to<00:17:38.460> do<00:17:38.640> the<00:17:38.880> evm<00:17:39.299> you<00:17:39.780> can<00:17:39.900> do<00:17:40.080> whatever 00:17:40.190 --> 00:17:40.200 align:start position:0% have to do the evm you can do whatever 00:17:40.200 --> 00:17:42.590 align:start position:0% have to do the evm you can do whatever you<00:17:40.440> want<00:17:40.559> you<00:17:40.860> can<00:17:40.980> annoy<00:17:41.280> the<00:17:41.460> Maxis<00:17:41.940> and<00:17:42.480> do 00:17:42.590 --> 00:17:42.600 align:start position:0% you want you can annoy the Maxis and do 00:17:42.600 --> 00:17:45.230 align:start position:0% you want you can annoy the Maxis and do a<00:17:42.780> Bitcoin<00:17:43.200> you<00:17:44.160> can<00:17:44.220> put<00:17:44.400> a<00:17:44.520> Game<00:17:44.700> Boy<00:17:44.940> inside 00:17:45.230 --> 00:17:45.240 align:start position:0% a Bitcoin you can put a Game Boy inside 00:17:45.240 --> 00:17:47.029 align:start position:0% a Bitcoin you can put a Game Boy inside of<00:17:45.539> a<00:17:45.660> roll-up<00:17:45.960> you<00:17:46.320> can<00:17:46.440> do<00:17:46.559> a<00:17:46.740> python 00:17:47.029 --> 00:17:47.039 align:start position:0% of a roll-up you can do a python 00:17:47.039 --> 00:17:49.070 align:start position:0% of a roll-up you can do a python interpreter<00:17:47.460> inside<00:17:47.700> of<00:17:47.880> a<00:17:48.000> roll<00:17:48.179> up<00:17:48.360> as<00:17:48.900> long 00:17:49.070 --> 00:17:49.080 align:start position:0% interpreter inside of a roll up as long 00:17:49.080 --> 00:17:51.049 align:start position:0% interpreter inside of a roll up as long as<00:17:49.260> you<00:17:49.500> have<00:17:49.620> a<00:17:49.919> state<00:17:50.100> transition<00:17:50.520> function 00:17:51.049 --> 00:17:51.059 align:start position:0% as you have a state transition function 00:17:51.059 --> 00:17:54.470 align:start position:0% as you have a state transition function you<00:17:51.840> can<00:17:51.960> put<00:17:52.200> it<00:17:52.320> behind<00:17:52.919> the<00:17:53.039> engine<00:17:53.220> API<00:17:53.880> and 00:17:54.470 --> 00:17:54.480 align:start position:0% you can put it behind the engine API and 00:17:54.480 --> 00:17:56.210 align:start position:0% you can put it behind the engine API and the<00:17:54.720> rest<00:17:54.780> of<00:17:55.020> the<00:17:55.200> system<00:17:55.380> will<00:17:55.679> just<00:17:55.919> work 00:17:56.210 --> 00:17:56.220 align:start position:0% the rest of the system will just work 00:17:56.220 --> 00:17:58.669 align:start position:0% the rest of the system will just work publishing<00:17:57.179> transactions<00:17:57.780> to<00:17:58.020> ethereum<00:17:58.440> will 00:17:58.669 --> 00:17:58.679 align:start position:0% publishing transactions to ethereum will 00:17:58.679 --> 00:18:00.830 align:start position:0% publishing transactions to ethereum will just<00:17:58.860> work<00:17:59.039> the<00:17:59.640> pro<00:17:59.820> the<00:18:00.179> fault<00:18:00.360> proof<00:18:00.660> system 00:18:00.830 --> 00:18:00.840 align:start position:0% just work the pro the fault proof system 00:18:00.840 --> 00:18:02.930 align:start position:0% just work the pro the fault proof system will<00:18:01.200> just<00:18:01.380> work<00:18:01.620> everything<00:18:02.220> just<00:18:02.460> works<00:18:02.820> you 00:18:02.930 --> 00:18:02.940 align:start position:0% will just work everything just works you 00:18:02.940 --> 00:18:04.730 align:start position:0% will just work everything just works you just<00:18:03.179> switch<00:18:03.840> it<00:18:04.020> out<00:18:04.200> as<00:18:04.440> long<00:18:04.559> as<00:18:04.620> it 00:18:04.730 --> 00:18:04.740 align:start position:0% just switch it out as long as it 00:18:04.740 --> 00:18:08.450 align:start position:0% just switch it out as long as it compiles<00:18:05.220> to<00:18:05.340> mips<00:18:05.700> you're<00:18:06.240> good<00:18:06.419> you're<00:18:06.900> fine 00:18:08.450 --> 00:18:08.460 align:start position:0% compiles to mips you're good you're fine 00:18:08.460 --> 00:18:10.490 align:start position:0% compiles to mips you're good you're fine so<00:18:08.940> like<00:18:09.179> Carl<00:18:09.360> said<00:18:09.600> the<00:18:09.900> sky's<00:18:10.080> the<00:18:10.320> limit 00:18:10.490 --> 00:18:10.500 align:start position:0% so like Carl said the sky's the limit 00:18:10.500 --> 00:18:12.529 align:start position:0% so like Carl said the sky's the limit you<00:18:11.039> have<00:18:11.160> so<00:18:11.460> much<00:18:11.580> flexibility<00:18:12.059> with<00:18:12.419> this 00:18:12.529 --> 00:18:12.539 align:start position:0% you have so much flexibility with this 00:18:12.539 --> 00:18:14.450 align:start position:0% you have so much flexibility with this design<00:18:12.720> and<00:18:13.440> I<00:18:13.559> highly<00:18:13.799> recommend<00:18:14.100> that<00:18:14.280> you 00:18:14.450 --> 00:18:14.460 align:start position:0% design and I highly recommend that you 00:18:14.460 --> 00:18:16.310 align:start position:0% design and I highly recommend that you mess<00:18:14.640> around<00:18:14.820> with<00:18:15.059> it 00:18:16.310 --> 00:18:16.320 align:start position:0% mess around with it 00:18:16.320 --> 00:18:19.490 align:start position:0% mess around with it okay<00:18:17.280> on<00:18:18.059> to<00:18:18.179> the<00:18:18.360> really<00:18:18.480> final<00:18:18.840> part<00:18:19.200> of<00:18:19.380> this 00:18:19.490 --> 00:18:19.500 align:start position:0% okay on to the really final part of this 00:18:19.500 --> 00:18:22.610 align:start position:0% okay on to the really final part of this talk<00:18:19.740> settlement<00:18:20.280> settlement<00:18:20.900> is<00:18:21.900> you<00:18:22.559> know 00:18:22.610 --> 00:18:22.620 align:start position:0% talk settlement settlement is you know 00:18:22.620 --> 00:18:24.529 align:start position:0% talk settlement settlement is you know like<00:18:22.860> kind<00:18:23.100> of<00:18:23.160> the<00:18:23.340> fakest<00:18:23.760> part<00:18:24.000> of<00:18:24.179> all<00:18:24.299> this 00:18:24.529 --> 00:18:24.539 align:start position:0% like kind of the fakest part of all this 00:18:24.539 --> 00:18:26.450 align:start position:0% like kind of the fakest part of all this it's<00:18:24.780> a<00:18:24.960> little<00:18:25.080> hard<00:18:25.320> to<00:18:25.500> understand<00:18:25.620> is<00:18:26.280> it 00:18:26.450 --> 00:18:26.460 align:start position:0% it's a little hard to understand is it 00:18:26.460 --> 00:18:29.150 align:start position:0% it's a little hard to understand is it even<00:18:26.640> a<00:18:26.940> real<00:18:27.059> thing<00:18:27.360> and<00:18:28.080> I<00:18:28.260> think<00:18:28.380> yeah<00:18:28.799> you 00:18:29.150 --> 00:18:29.160 align:start position:0% even a real thing and I think yeah you 00:18:29.160 --> 00:18:30.529 align:start position:0% even a real thing and I think yeah you know<00:18:29.220> in<00:18:29.400> a<00:18:29.580> way 00:18:30.529 --> 00:18:30.539 align:start position:0% know in a way 00:18:30.539 --> 00:18:31.430 align:start position:0% know in a way um 00:18:31.430 --> 00:18:31.440 align:start position:0% um 00:18:31.440 --> 00:18:33.350 align:start position:0% um this<00:18:31.860> is<00:18:31.980> how<00:18:32.100> I'll<00:18:32.280> Define<00:18:32.580> it<00:18:32.880> you<00:18:33.059> know<00:18:33.120> for 00:18:33.350 --> 00:18:33.360 align:start position:0% this is how I'll Define it you know for 00:18:33.360 --> 00:18:35.330 align:start position:0% this is how I'll Define it you know for the<00:18:33.480> sake<00:18:33.600> of<00:18:33.720> the<00:18:33.840> old<00:18:33.960> peace<00:18:34.260> time 00:18:35.330 --> 00:18:35.340 align:start position:0% the sake of the old peace time 00:18:35.340 --> 00:18:38.450 align:start position:0% the sake of the old peace time settlement<00:18:36.120> is<00:18:36.419> a<00:18:36.660> view<00:18:36.840> that<00:18:37.559> another<00:18:37.919> chain 00:18:38.450 --> 00:18:38.460 align:start position:0% settlement is a view that another chain 00:18:38.460 --> 00:18:41.270 align:start position:0% settlement is a view that another chain has<00:18:39.240> your<00:18:39.960> chain 00:18:41.270 --> 00:18:41.280 align:start position:0% has your chain 00:18:41.280 --> 00:18:44.090 align:start position:0% has your chain and<00:18:41.760> it's<00:18:41.880> about<00:18:42.059> making<00:18:42.600> claims<00:18:43.320> about<00:18:43.740> the 00:18:44.090 --> 00:18:44.100 align:start position:0% and it's about making claims about the 00:18:44.100 --> 00:18:46.250 align:start position:0% and it's about making claims about the state<00:18:44.220> of<00:18:44.460> your<00:18:44.580> chain<00:18:44.760> to<00:18:45.059> another<00:18:45.240> chain 00:18:46.250 --> 00:18:46.260 align:start position:0% state of your chain to another chain 00:18:46.260 --> 00:18:48.890 align:start position:0% state of your chain to another chain and<00:18:46.679> being<00:18:46.860> able<00:18:47.100> to<00:18:47.280> back<00:18:47.460> those<00:18:47.760> claims<00:18:48.179> up 00:18:48.890 --> 00:18:48.900 align:start position:0% and being able to back those claims up 00:18:48.900 --> 00:18:50.270 align:start position:0% and being able to back those claims up and<00:18:49.200> so<00:18:49.320> if<00:18:49.440> you<00:18:49.559> think<00:18:49.679> about<00:18:49.799> that<00:18:49.980> for<00:18:50.160> a 00:18:50.270 --> 00:18:50.280 align:start position:0% and so if you think about that for a 00:18:50.280 --> 00:18:51.770 align:start position:0% and so if you think about that for a second<00:18:50.400> that<00:18:50.700> means<00:18:50.940> that<00:18:51.059> you<00:18:51.240> can<00:18:51.299> settle<00:18:51.600> to 00:18:51.770 --> 00:18:51.780 align:start position:0% second that means that you can settle to 00:18:51.780 --> 00:18:53.210 align:start position:0% second that means that you can settle to multiple<00:18:52.080> chains<00:18:52.440> at<00:18:52.559> the<00:18:52.679> same<00:18:52.799> time<00:18:52.919> there's 00:18:53.210 --> 00:18:53.220 align:start position:0% multiple chains at the same time there's 00:18:53.220 --> 00:18:54.890 align:start position:0% multiple chains at the same time there's nothing<00:18:53.460> about<00:18:53.700> this<00:18:54.000> definition<00:18:54.179> that<00:18:54.600> says 00:18:54.890 --> 00:18:54.900 align:start position:0% nothing about this definition that says 00:18:54.900 --> 00:18:57.169 align:start position:0% nothing about this definition that says you<00:18:55.320> can't<00:18:55.440> sell<00:18:55.679> to<00:18:55.980> ethereum<00:18:56.520> and<00:18:56.760> Bitcoin 00:18:57.169 --> 00:18:57.179 align:start position:0% you can't sell to ethereum and Bitcoin 00:18:57.179 --> 00:18:58.370 align:start position:0% you can't sell to ethereum and Bitcoin at<00:18:57.299> the<00:18:57.480> same<00:18:57.600> time 00:18:58.370 --> 00:18:58.380 align:start position:0% at the same time 00:18:58.380 --> 00:18:59.870 align:start position:0% at the same time there's<00:18:58.740> nothing<00:18:58.919> about<00:18:59.100> this<00:18:59.340> claim<00:18:59.760> that 00:18:59.870 --> 00:18:59.880 align:start position:0% there's nothing about this claim that 00:18:59.880 --> 00:19:01.490 align:start position:0% there's nothing about this claim that says<00:19:00.179> you<00:19:00.299> can't<00:19:00.419> have<00:19:00.660> multiple<00:19:01.020> settlement 00:19:01.490 --> 00:19:01.500 align:start position:0% says you can't have multiple settlement 00:19:01.500 --> 00:19:03.710 align:start position:0% says you can't have multiple settlement layers<00:19:01.860> settlement<00:19:02.640> mechanisms<00:19:03.179> to<00:19:03.360> the<00:19:03.539> same 00:19:03.710 --> 00:19:03.720 align:start position:0% layers settlement mechanisms to the same 00:19:03.720 --> 00:19:05.630 align:start position:0% layers settlement mechanisms to the same chain<00:19:04.020> right<00:19:04.799> because<00:19:05.039> you<00:19:05.220> could<00:19:05.340> be<00:19:05.460> making 00:19:05.630 --> 00:19:05.640 align:start position:0% chain right because you could be making 00:19:05.640 --> 00:19:07.310 align:start position:0% chain right because you could be making claims<00:19:06.059> you<00:19:06.240> could<00:19:06.360> be<00:19:06.480> backing<00:19:06.780> those<00:19:06.960> claims 00:19:07.310 --> 00:19:07.320 align:start position:0% claims you could be backing those claims 00:19:07.320 --> 00:19:09.350 align:start position:0% claims you could be backing those claims up<00:19:07.440> in<00:19:07.620> different<00:19:07.799> ways<00:19:08.179> essentially<00:19:09.179> it's 00:19:09.350 --> 00:19:09.360 align:start position:0% up in different ways essentially it's 00:19:09.360 --> 00:19:11.690 align:start position:0% up in different ways essentially it's just<00:19:09.539> about<00:19:09.780> making<00:19:10.200> claims<00:19:10.799> and<00:19:11.280> backing 00:19:11.690 --> 00:19:11.700 align:start position:0% just about making claims and backing 00:19:11.700 --> 00:19:14.150 align:start position:0% just about making claims and backing them<00:19:11.880> up 00:19:14.150 --> 00:19:14.160 align:start position:0% 00:19:14.160 --> 00:19:15.590 align:start position:0% um<00:19:14.220> and<00:19:14.520> actually<00:19:14.640> let<00:19:14.820> me<00:19:14.940> get<00:19:15.059> to<00:19:15.179> that<00:19:15.299> in<00:19:15.480> a 00:19:15.590 --> 00:19:15.600 align:start position:0% um and actually let me get to that in a 00:19:15.600 --> 00:19:18.110 align:start position:0% um and actually let me get to that in a second<00:19:15.780> well<00:19:16.440> we'll<00:19:16.860> see<00:19:17.039> whatever<00:19:17.280> fine<00:19:17.700> all 00:19:18.110 --> 00:19:18.120 align:start position:0% second well we'll see whatever fine all 00:19:18.120 --> 00:19:19.669 align:start position:0% second well we'll see whatever fine all right<00:19:18.299> so<00:19:18.539> you<00:19:18.660> can<00:19:18.780> make<00:19:18.960> all<00:19:19.320> sorts<00:19:19.620> of 00:19:19.669 --> 00:19:19.679 align:start position:0% right so you can make all sorts of 00:19:19.679 --> 00:19:21.950 align:start position:0% right so you can make all sorts of claims<00:19:20.160> about<00:19:20.700> a<00:19:21.179> system 00:19:21.950 --> 00:19:21.960 align:start position:0% claims about a system 00:19:21.960 --> 00:19:23.870 align:start position:0% claims about a system but<00:19:22.380> the<00:19:22.500> one<00:19:22.620> that<00:19:22.799> you'll<00:19:23.039> find<00:19:23.280> most 00:19:23.870 --> 00:19:23.880 align:start position:0% but the one that you'll find most 00:19:23.880 --> 00:19:26.630 align:start position:0% but the one that you'll find most commonly<00:19:24.360> is<00:19:24.960> making<00:19:25.260> a<00:19:25.500> claim<00:19:25.799> about<00:19:26.220> what<00:19:26.520> we 00:19:26.630 --> 00:19:26.640 align:start position:0% commonly is making a claim about what we 00:19:26.640 --> 00:19:29.390 align:start position:0% commonly is making a claim about what we call<00:19:26.760> the<00:19:27.059> state<00:19:27.299> route<00:19:27.600> of<00:19:28.020> the<00:19:28.200> system<00:19:28.440> the 00:19:29.390 --> 00:19:29.400 align:start position:0% call the state route of the system the 00:19:29.400 --> 00:19:31.909 align:start position:0% call the state route of the system the state<00:19:29.580> route<00:19:29.820> in<00:19:30.179> ethereum<00:19:30.660> you<00:19:31.140> kind<00:19:31.500> of<00:19:31.620> if 00:19:31.909 --> 00:19:31.919 align:start position:0% state route in ethereum you kind of if 00:19:31.919 --> 00:19:33.350 align:start position:0% state route in ethereum you kind of if you've<00:19:32.220> played<00:19:32.580> around<00:19:32.700> with<00:19:32.880> ethereum 00:19:33.350 --> 00:19:33.360 align:start position:0% you've played around with ethereum 00:19:33.360 --> 00:19:34.909 align:start position:0% you've played around with ethereum before<00:19:33.480> you're<00:19:33.780> probably<00:19:34.020> familiar<00:19:34.500> with<00:19:34.799> it 00:19:34.909 --> 00:19:34.919 align:start position:0% before you're probably familiar with it 00:19:34.919 --> 00:19:37.190 align:start position:0% before you're probably familiar with it basically<00:19:35.700> it's<00:19:35.880> just<00:19:36.059> a<00:19:36.179> commitment<00:19:36.600> to 00:19:37.190 --> 00:19:37.200 align:start position:0% basically it's just a commitment to 00:19:37.200 --> 00:19:38.930 align:start position:0% basically it's just a commitment to everything<00:19:37.559> right<00:19:37.919> the<00:19:38.280> full<00:19:38.520> state<00:19:38.760> of 00:19:38.930 --> 00:19:38.940 align:start position:0% everything right the full state of 00:19:38.940 --> 00:19:40.010 align:start position:0% everything right the full state of ethereum 00:19:40.010 --> 00:19:40.020 align:start position:0% ethereum 00:19:40.020 --> 00:19:43.610 align:start position:0% ethereum so<00:19:40.559> similarly<00:19:41.480> generally<00:19:42.480> the<00:19:43.200> easiest<00:19:43.440> thing 00:19:43.610 --> 00:19:43.620 align:start position:0% so similarly generally the easiest thing 00:19:43.620 --> 00:19:46.130 align:start position:0% so similarly generally the easiest thing to<00:19:43.799> do<00:19:43.919> is<00:19:44.100> just<00:19:44.220> to<00:19:44.400> make<00:19:44.580> a<00:19:44.820> a<00:19:45.059> claim<00:19:45.660> about<00:19:45.840> a 00:19:46.130 --> 00:19:46.140 align:start position:0% to do is just to make a a claim about a 00:19:46.140 --> 00:19:47.750 align:start position:0% to do is just to make a a claim about a commitment<00:19:46.440> that<00:19:46.919> commits<00:19:47.340> to<00:19:47.460> everything 00:19:47.750 --> 00:19:47.760 align:start position:0% commitment that commits to everything 00:19:47.760 --> 00:19:49.789 align:start position:0% commitment that commits to everything and<00:19:48.480> then<00:19:48.600> when<00:19:48.780> you<00:19:48.900> make<00:19:49.020> that<00:19:49.260> claim<00:19:49.620> about 00:19:49.789 --> 00:19:49.799 align:start position:0% and then when you make that claim about 00:19:49.799 --> 00:19:50.990 align:start position:0% and then when you make that claim about the<00:19:50.039> commitment<00:19:50.340> that<00:19:50.520> commits<00:19:50.880> to 00:19:50.990 --> 00:19:51.000 align:start position:0% the commitment that commits to 00:19:51.000 --> 00:19:52.730 align:start position:0% the commitment that commits to everything<00:19:51.179> else<00:19:51.539> you<00:19:52.140> can<00:19:52.260> just<00:19:52.380> prove 00:19:52.730 --> 00:19:52.740 align:start position:0% everything else you can just prove 00:19:52.740 --> 00:19:54.650 align:start position:0% everything else you can just prove against<00:19:52.860> that<00:19:53.220> commitment<00:19:53.640> and<00:19:54.179> now<00:19:54.360> all<00:19:54.480> of<00:19:54.600> a 00:19:54.650 --> 00:19:54.660 align:start position:0% against that commitment and now all of a 00:19:54.660 --> 00:19:56.150 align:start position:0% against that commitment and now all of a sudden<00:19:54.780> you<00:19:55.140> can<00:19:55.200> do<00:19:55.380> you<00:19:55.679> know<00:19:55.799> pretty<00:19:56.039> much 00:19:56.150 --> 00:19:56.160 align:start position:0% sudden you can do you know pretty much 00:19:56.160 --> 00:19:58.490 align:start position:0% sudden you can do you know pretty much whatever<00:19:56.400> you<00:19:56.760> want 00:19:58.490 --> 00:19:58.500 align:start position:0% whatever you want 00:19:58.500 --> 00:19:59.870 align:start position:0% whatever you want um but<00:19:58.740> that<00:19:58.919> doesn't<00:19:59.100> mean<00:19:59.280> that's<00:19:59.460> the<00:19:59.700> only 00:19:59.870 --> 00:19:59.880 align:start position:0% um but that doesn't mean that's the only 00:19:59.880 --> 00:20:01.310 align:start position:0% um but that doesn't mean that's the only way<00:20:00.059> to<00:20:00.240> do<00:20:00.360> commitments<00:20:00.900> you<00:20:01.080> could<00:20:01.200> do 00:20:01.310 --> 00:20:01.320 align:start position:0% way to do commitments you could do 00:20:01.320 --> 00:20:03.710 align:start position:0% way to do commitments you could do commitments<00:20:01.860> about<00:20:02.039> specific<00:20:02.700> claims<00:20:03.419> on 00:20:03.710 --> 00:20:03.720 align:start position:0% commitments about specific claims on 00:20:03.720 --> 00:20:06.230 align:start position:0% commitments about specific claims on Layer<00:20:03.960> Two<00:20:04.080> like<00:20:04.440> this<00:20:05.160> very<00:20:05.460> specific<00:20:05.880> thing 00:20:06.230 --> 00:20:06.240 align:start position:0% Layer Two like this very specific thing 00:20:06.240 --> 00:20:08.029 align:start position:0% Layer Two like this very specific thing happened<00:20:06.539> on<00:20:06.780> Layer<00:20:07.080> Two 00:20:08.029 --> 00:20:08.039 align:start position:0% happened on Layer Two 00:20:08.039 --> 00:20:09.409 align:start position:0% happened on Layer Two um it's<00:20:08.280> just<00:20:08.400> that<00:20:08.580> the<00:20:08.760> most<00:20:08.880> General<00:20:09.059> and 00:20:09.409 --> 00:20:09.419 align:start position:0% um it's just that the most General and 00:20:09.419 --> 00:20:11.510 align:start position:0% um it's just that the most General and generally<00:20:09.780> the<00:20:09.960> easiest<00:20:10.260> thing<00:20:10.500> to<00:20:10.679> do<00:20:10.860> is<00:20:11.400> to 00:20:11.510 --> 00:20:11.520 align:start position:0% generally the easiest thing to do is to 00:20:11.520 --> 00:20:13.549 align:start position:0% generally the easiest thing to do is to make<00:20:11.640> a<00:20:11.760> claim<00:20:12.000> about<00:20:12.120> the<00:20:12.299> state<00:20:12.419> group 00:20:13.549 --> 00:20:13.559 align:start position:0% make a claim about the state group 00:20:13.559 --> 00:20:15.409 align:start position:0% make a claim about the state group in<00:20:14.039> order<00:20:14.160> to<00:20:14.400> make<00:20:14.520> a<00:20:14.700> claim<00:20:14.880> about<00:20:15.000> the<00:20:15.240> state 00:20:15.409 --> 00:20:15.419 align:start position:0% in order to make a claim about the state 00:20:15.419 --> 00:20:17.210 align:start position:0% in order to make a claim about the state route<00:20:15.660> we<00:20:16.140> see<00:20:16.320> we<00:20:16.559> need<00:20:16.679> a<00:20:16.860> function<00:20:17.039> that 00:20:17.210 --> 00:20:17.220 align:start position:0% route we see we need a function that 00:20:17.220 --> 00:20:19.430 align:start position:0% route we see we need a function that looks<00:20:17.520> like<00:20:17.640> this<00:20:17.880> it's<00:20:18.660> this<00:20:18.900> validity 00:20:19.430 --> 00:20:19.440 align:start position:0% looks like this it's this validity 00:20:19.440 --> 00:20:20.930 align:start position:0% looks like this it's this validity function<00:20:19.740> this<00:20:19.919> looks<00:20:20.220> very<00:20:20.340> straightforward 00:20:20.930 --> 00:20:20.940 align:start position:0% function this looks very straightforward 00:20:20.940 --> 00:20:23.450 align:start position:0% function this looks very straightforward we<00:20:21.600> have<00:20:21.720> a<00:20:21.900> previous<00:20:22.080> state<00:20:22.500> we<00:20:23.160> have<00:20:23.280> the 00:20:23.450 --> 00:20:23.460 align:start position:0% we have a previous state we have the 00:20:23.460 --> 00:20:24.830 align:start position:0% we have a previous state we have the next<00:20:23.580> state<00:20:23.880> that<00:20:24.120> we're<00:20:24.240> trying<00:20:24.600> to<00:20:24.780> figure 00:20:24.830 --> 00:20:24.840 align:start position:0% next state that we're trying to figure 00:20:24.840 --> 00:20:26.510 align:start position:0% next state that we're trying to figure out<00:20:25.020> if<00:20:25.200> that<00:20:25.380> next<00:20:25.500> state<00:20:25.740> is<00:20:25.919> valid<00:20:26.220> given 00:20:26.510 --> 00:20:26.520 align:start position:0% out if that next state is valid given 00:20:26.520 --> 00:20:28.250 align:start position:0% out if that next state is valid given the<00:20:26.700> previous<00:20:26.820> state<00:20:27.179> we<00:20:27.900> have<00:20:27.960> the<00:20:28.140> date 00:20:28.250 --> 00:20:28.260 align:start position:0% the previous state we have the date 00:20:28.260 --> 00:20:29.870 align:start position:0% the previous state we have the date availability<00:20:28.740> layer<00:20:29.220> we<00:20:29.640> have<00:20:29.760> the 00:20:29.870 --> 00:20:29.880 align:start position:0% availability layer we have the 00:20:29.880 --> 00:20:31.130 align:start position:0% availability layer we have the derivation<00:20:30.360> function<00:20:30.720> we<00:20:30.960> have<00:20:31.020> the 00:20:31.130 --> 00:20:31.140 align:start position:0% derivation function we have the 00:20:31.140 --> 00:20:32.870 align:start position:0% derivation function we have the execution<00:20:31.500> function<00:20:31.919> all<00:20:32.280> stuff<00:20:32.520> that<00:20:32.700> we've 00:20:32.870 --> 00:20:32.880 align:start position:0% execution function all stuff that we've 00:20:32.880 --> 00:20:34.850 align:start position:0% execution function all stuff that we've already<00:20:33.059> talked<00:20:33.419> about<00:20:33.480> and<00:20:34.140> we<00:20:34.320> spit<00:20:34.500> out<00:20:34.679> a 00:20:34.850 --> 00:20:34.860 align:start position:0% already talked about and we spit out a 00:20:34.860 --> 00:20:36.470 align:start position:0% already talked about and we spit out a Boolean<00:20:35.280> right<00:20:35.580> we<00:20:35.760> spit<00:20:35.940> out<00:20:36.120> something<00:20:36.240> that 00:20:36.470 --> 00:20:36.480 align:start position:0% Boolean right we spit out something that 00:20:36.480 --> 00:20:39.650 align:start position:0% Boolean right we spit out something that says<00:20:36.720> is<00:20:37.080> this<00:20:37.320> state<00:20:37.500> transition<00:20:37.919> valid 00:20:39.650 --> 00:20:39.660 align:start position:0% says is this state transition valid 00:20:39.660 --> 00:20:41.870 align:start position:0% says is this state transition valid and<00:20:40.320> so<00:20:40.500> the<00:20:40.679> key<00:20:40.860> question<00:20:41.039> of<00:20:41.340> how<00:20:41.640> do<00:20:41.760> you 00:20:41.870 --> 00:20:41.880 align:start position:0% and so the key question of how do you 00:20:41.880 --> 00:20:43.490 align:start position:0% and so the key question of how do you actually<00:20:42.120> make<00:20:42.539> this<00:20:42.840> work<00:20:43.020> in<00:20:43.320> practice 00:20:43.490 --> 00:20:43.500 align:start position:0% actually make this work in practice 00:20:43.500 --> 00:20:45.590 align:start position:0% actually make this work in practice right<00:20:43.860> this<00:20:44.100> is<00:20:44.220> this<00:20:44.760> sounds<00:20:45.000> great<00:20:45.240> but<00:20:45.419> how 00:20:45.590 --> 00:20:45.600 align:start position:0% right this is this sounds great but how 00:20:45.600 --> 00:20:47.150 align:start position:0% right this is this sounds great but how does<00:20:45.720> this<00:20:45.840> work<00:20:46.020> in<00:20:46.200> practice 00:20:47.150 --> 00:20:47.160 align:start position:0% does this work in practice 00:20:47.160 --> 00:20:48.770 align:start position:0% does this work in practice so<00:20:47.520> look<00:20:47.640> at<00:20:47.760> this<00:20:47.880> carefully<00:20:48.240> let's<00:20:48.480> try<00:20:48.720> to 00:20:48.770 --> 00:20:48.780 align:start position:0% so look at this carefully let's try to 00:20:48.780 --> 00:20:49.850 align:start position:0% so look at this carefully let's try to figure<00:20:48.900> out<00:20:49.080> where<00:20:49.320> each<00:20:49.500> one<00:20:49.620> of<00:20:49.740> these 00:20:49.850 --> 00:20:49.860 align:start position:0% figure out where each one of these 00:20:49.860 --> 00:20:52.010 align:start position:0% figure out where each one of these inputs<00:20:50.340> comes<00:20:50.760> from<00:20:51.000> on<00:20:51.419> chain<00:20:51.660> let's<00:20:51.900> say 00:20:52.010 --> 00:20:52.020 align:start position:0% inputs comes from on chain let's say 00:20:52.020 --> 00:20:53.510 align:start position:0% inputs comes from on chain let's say we're<00:20:52.200> settling<00:20:52.500> to<00:20:52.679> ethereum<00:20:53.160> where<00:20:53.340> does 00:20:53.510 --> 00:20:53.520 align:start position:0% we're settling to ethereum where does 00:20:53.520 --> 00:20:54.650 align:start position:0% we're settling to ethereum where does this<00:20:53.640> come<00:20:53.880> from 00:20:54.650 --> 00:20:54.660 align:start position:0% this come from 00:20:54.660 --> 00:20:57.049 align:start position:0% this come from so<00:20:55.140> state<00:20:55.440> is<00:20:55.740> a<00:20:55.860> given<00:20:56.160> the<00:20:56.580> previous<00:20:56.700> state 00:20:57.049 --> 00:20:57.059 align:start position:0% so state is a given the previous state 00:20:57.059 --> 00:20:58.909 align:start position:0% so state is a given the previous state we<00:20:57.539> agree<00:20:57.780> on<00:20:57.900> the<00:20:58.080> previous<00:20:58.200> state<00:20:58.559> generally 00:20:58.909 --> 00:20:58.919 align:start position:0% we agree on the previous state generally 00:20:58.919 --> 00:21:00.470 align:start position:0% we agree on the previous state generally that's<00:20:59.220> how<00:20:59.460> we<00:20:59.580> want<00:20:59.760> to<00:20:59.880> design<00:21:00.120> these 00:21:00.470 --> 00:21:00.480 align:start position:0% that's how we want to design these 00:21:00.480 --> 00:21:01.909 align:start position:0% that's how we want to design these systems<00:21:00.780> we<00:21:00.960> start<00:21:01.140> with<00:21:01.320> the<00:21:01.500> previous<00:21:01.620> state 00:21:01.909 --> 00:21:01.919 align:start position:0% systems we start with the previous state 00:21:01.919 --> 00:21:04.130 align:start position:0% systems we start with the previous state that<00:21:02.100> we<00:21:02.280> agree<00:21:02.520> on<00:21:02.700> and<00:21:03.360> then<00:21:03.419> we<00:21:03.600> have<00:21:03.720> a<00:21:03.960> next 00:21:04.130 --> 00:21:04.140 align:start position:0% that we agree on and then we have a next 00:21:04.140 --> 00:21:06.590 align:start position:0% that we agree on and then we have a next state<00:21:04.380> and<00:21:04.860> even<00:21:05.039> if<00:21:05.220> we<00:21:05.340> don't<00:21:05.460> agree<00:21:05.820> on<00:21:06.059> the 00:21:06.590 --> 00:21:06.600 align:start position:0% state and even if we don't agree on the 00:21:06.600 --> 00:21:08.690 align:start position:0% state and even if we don't agree on the validity<00:21:07.080> of<00:21:07.260> the<00:21:07.380> next<00:21:07.500> state<00:21:07.740> we<00:21:08.400> generally 00:21:08.690 --> 00:21:08.700 align:start position:0% validity of the next state we generally 00:21:08.700 --> 00:21:10.549 align:start position:0% validity of the next state we generally agree<00:21:09.179> on<00:21:09.600> the<00:21:09.720> fact<00:21:09.900> that<00:21:10.020> this<00:21:10.200> is<00:21:10.260> the<00:21:10.440> thing 00:21:10.549 --> 00:21:10.559 align:start position:0% agree on the fact that this is the thing 00:21:10.559 --> 00:21:11.870 align:start position:0% agree on the fact that this is the thing that<00:21:10.679> we're<00:21:10.799> putting<00:21:11.039> into<00:21:11.220> the<00:21:11.400> function<00:21:11.640> so 00:21:11.870 --> 00:21:11.880 align:start position:0% that we're putting into the function so 00:21:11.880 --> 00:21:13.970 align:start position:0% that we're putting into the function so the<00:21:12.059> first<00:21:12.179> two<00:21:12.299> are<00:21:12.480> Givens 00:21:13.970 --> 00:21:13.980 align:start position:0% the first two are Givens 00:21:13.980 --> 00:21:16.010 align:start position:0% the first two are Givens the<00:21:14.520> derivation<00:21:15.000> function<00:21:15.360> in<00:21:15.539> the<00:21:15.660> execution 00:21:16.010 --> 00:21:16.020 align:start position:0% the derivation function in the execution 00:21:16.020 --> 00:21:18.289 align:start position:0% the derivation function in the execution function<00:21:16.440> are<00:21:16.860> literally<00:21:17.280> functions<00:21:18.059> right 00:21:18.289 --> 00:21:18.299 align:start position:0% function are literally functions right 00:21:18.299 --> 00:21:21.169 align:start position:0% function are literally functions right they<00:21:18.780> are<00:21:18.960> pieces<00:21:19.260> of<00:21:19.440> code<00:21:19.740> that<00:21:20.100> run 00:21:21.169 --> 00:21:21.179 align:start position:0% they are pieces of code that run 00:21:21.179 --> 00:21:23.510 align:start position:0% they are pieces of code that run and<00:21:21.780> you<00:21:22.140> could<00:21:22.260> Implement<00:21:22.740> those<00:21:23.039> things<00:21:23.220> on 00:21:23.510 --> 00:21:23.520 align:start position:0% and you could Implement those things on 00:21:23.520 --> 00:21:25.610 align:start position:0% and you could Implement those things on chain<00:21:23.700> the<00:21:24.059> old<00:21:24.179> ovm<00:21:24.780> optimism's<00:21:25.500> old 00:21:25.610 --> 00:21:25.620 align:start position:0% chain the old ovm optimism's old 00:21:25.620 --> 00:21:27.890 align:start position:0% chain the old ovm optimism's old architecture<00:21:26.340> Implement<00:21:26.940> those<00:21:27.179> implemented 00:21:27.890 --> 00:21:27.900 align:start position:0% architecture Implement those implemented 00:21:27.900 --> 00:21:29.630 align:start position:0% architecture Implement those implemented those<00:21:28.080> things<00:21:28.260> literally<00:21:28.679> on<00:21:28.980> chain<00:21:29.159> so<00:21:29.400> you 00:21:29.630 --> 00:21:29.640 align:start position:0% those things literally on chain so you 00:21:29.640 --> 00:21:32.750 align:start position:0% those things literally on chain so you execute<00:21:30.059> the<00:21:30.299> entire<00:21:30.539> function<00:21:30.960> on<00:21:31.260> chain 00:21:32.750 --> 00:21:32.760 align:start position:0% execute the entire function on chain 00:21:32.760 --> 00:21:34.310 align:start position:0% execute the entire function on chain um<00:21:32.820> generally<00:21:33.419> speaking<00:21:33.840> that's<00:21:34.080> not 00:21:34.310 --> 00:21:34.320 align:start position:0% um generally speaking that's not 00:21:34.320 --> 00:21:35.990 align:start position:0% um generally speaking that's not feasible<00:21:34.740> depending<00:21:35.100> on<00:21:35.220> how<00:21:35.460> complex<00:21:35.760> your 00:21:35.990 --> 00:21:36.000 align:start position:0% feasible depending on how complex your 00:21:36.000 --> 00:21:38.870 align:start position:0% feasible depending on how complex your system<00:21:36.179> is<00:21:36.480> so<00:21:36.900> we<00:21:37.080> tend<00:21:37.320> to<00:21:37.440> bypass<00:21:37.980> this<00:21:38.400> and 00:21:38.870 --> 00:21:38.880 align:start position:0% system is so we tend to bypass this and 00:21:38.880 --> 00:21:40.730 align:start position:0% system is so we tend to bypass this and instead<00:21:39.179> of<00:21:39.299> implementing<00:21:40.020> the<00:21:40.200> functions<00:21:40.559> on 00:21:40.730 --> 00:21:40.740 align:start position:0% instead of implementing the functions on 00:21:40.740 --> 00:21:42.529 align:start position:0% instead of implementing the functions on chain<00:21:40.980> we<00:21:41.580> basically<00:21:41.880> Implement<00:21:42.299> something 00:21:42.529 --> 00:21:42.539 align:start position:0% chain we basically Implement something 00:21:42.539 --> 00:21:44.390 align:start position:0% chain we basically Implement something that<00:21:42.780> acts<00:21:43.140> like<00:21:43.200> a<00:21:43.380> proxy<00:21:43.799> of<00:21:43.919> the<00:21:44.100> function 00:21:44.390 --> 00:21:44.400 align:start position:0% that acts like a proxy of the function 00:21:44.400 --> 00:21:46.370 align:start position:0% that acts like a proxy of the function and<00:21:44.940> that's<00:21:45.059> usually<00:21:45.419> either<00:21:45.659> fault<00:21:46.020> proofs 00:21:46.370 --> 00:21:46.380 align:start position:0% and that's usually either fault proofs 00:21:46.380 --> 00:21:48.649 align:start position:0% and that's usually either fault proofs or<00:21:46.799> validity<00:21:47.280> proofs<00:21:47.700> right<00:21:48.059> these<00:21:48.360> are<00:21:48.480> our 00:21:48.649 --> 00:21:48.659 align:start position:0% or validity proofs right these are our 00:21:48.659 --> 00:21:50.930 align:start position:0% or validity proofs right these are our proxies<00:21:49.140> for<00:21:49.380> the<00:21:49.559> execution<00:21:49.980> because<00:21:50.640> it's 00:21:50.930 --> 00:21:50.940 align:start position:0% proxies for the execution because it's 00:21:50.940 --> 00:21:52.850 align:start position:0% proxies for the execution because it's too<00:21:51.179> expensive<00:21:51.659> to<00:21:52.020> actually<00:21:52.140> carry<00:21:52.559> out<00:21:52.679> the 00:21:52.850 --> 00:21:52.860 align:start position:0% too expensive to actually carry out the 00:21:52.860 --> 00:21:54.830 align:start position:0% too expensive to actually carry out the execution<00:21:53.220> on<00:21:53.460> chain<00:21:53.700> but<00:21:54.480> you<00:21:54.600> can<00:21:54.720> think 00:21:54.830 --> 00:21:54.840 align:start position:0% execution on chain but you can think 00:21:54.840 --> 00:21:56.029 align:start position:0% execution on chain but you can think about<00:21:54.960> how<00:21:55.200> this<00:21:55.380> fault<00:21:55.620> proof<00:21:55.860> of<00:21:55.919> this 00:21:56.029 --> 00:21:56.039 align:start position:0% about how this fault proof of this 00:21:56.039 --> 00:21:57.830 align:start position:0% about how this fault proof of this validity<00:21:56.460> proof<00:21:56.700> is<00:21:56.880> representing<00:21:57.659> the 00:21:57.830 --> 00:21:57.840 align:start position:0% validity proof is representing the 00:21:57.840 --> 00:21:59.690 align:start position:0% validity proof is representing the derivation<00:21:58.320> in<00:21:58.559> their<00:21:58.679> execution<00:21:59.159> functions 00:21:59.690 --> 00:21:59.700 align:start position:0% derivation in their execution functions 00:21:59.700 --> 00:22:02.149 align:start position:0% derivation in their execution functions it<00:22:00.179> is<00:22:00.299> the<00:22:00.539> code<00:22:00.780> of<00:22:00.960> those<00:22:01.200> functions<00:22:01.679> it's 00:22:02.149 --> 00:22:02.159 align:start position:0% it is the code of those functions it's 00:22:02.159 --> 00:22:03.649 align:start position:0% it is the code of those functions it's just<00:22:02.340> that<00:22:02.520> we<00:22:02.700> execute<00:22:03.059> it<00:22:03.240> in<00:22:03.419> a<00:22:03.539> different 00:22:03.649 --> 00:22:03.659 align:start position:0% just that we execute it in a different 00:22:03.659 --> 00:22:06.049 align:start position:0% just that we execute it in a different way<00:22:03.840> we<00:22:04.260> execute<00:22:04.620> it<00:22:04.740> in<00:22:04.980> a<00:22:05.159> way<00:22:05.280> that<00:22:05.940> is 00:22:06.049 --> 00:22:06.059 align:start position:0% way we execute it in a way that is 00:22:06.059 --> 00:22:08.870 align:start position:0% way we execute it in a way that is actually<00:22:06.299> feasible<00:22:06.780> to<00:22:06.960> do<00:22:07.080> on<00:22:07.260> chain 00:22:08.870 --> 00:22:08.880 align:start position:0% actually feasible to do on chain 00:22:08.880 --> 00:22:10.669 align:start position:0% actually feasible to do on chain but<00:22:09.419> the<00:22:09.600> interesting<00:22:10.020> question<00:22:10.200> is<00:22:10.440> how<00:22:10.620> do 00:22:10.669 --> 00:22:10.679 align:start position:0% but the interesting question is how do 00:22:10.679 --> 00:22:12.230 align:start position:0% but the interesting question is how do we<00:22:10.799> access<00:22:10.980> the<00:22:11.280> data<00:22:11.520> availability<00:22:11.820> layer 00:22:12.230 --> 00:22:12.240 align:start position:0% we access the data availability layer 00:22:12.240 --> 00:22:13.789 align:start position:0% we access the data availability layer right<00:22:12.360> how<00:22:12.659> do<00:22:12.720> we<00:22:12.840> get<00:22:13.020> access<00:22:13.200> to<00:22:13.500> that<00:22:13.559> data 00:22:13.789 --> 00:22:13.799 align:start position:0% right how do we get access to that data 00:22:13.799 --> 00:22:16.310 align:start position:0% right how do we get access to that data availability<00:22:14.100> layer<00:22:14.640> on<00:22:15.539> the<00:22:15.900> chain<00:22:16.020> that 00:22:16.310 --> 00:22:16.320 align:start position:0% availability layer on the chain that 00:22:16.320 --> 00:22:17.990 align:start position:0% availability layer on the chain that we're<00:22:16.440> settling<00:22:16.799> on 00:22:17.990 --> 00:22:18.000 align:start position:0% we're settling on 00:22:18.000 --> 00:22:20.270 align:start position:0% we're settling on of<00:22:18.419> course<00:22:18.539> it's<00:22:18.720> another<00:22:18.900> function<00:22:19.440> if<00:22:20.159> you 00:22:20.270 --> 00:22:20.280 align:start position:0% of course it's another function if you 00:22:20.280 --> 00:22:21.649 align:start position:0% of course it's another function if you remember<00:22:20.400> our<00:22:20.700> data<00:22:21.000> availability<00:22:21.299> layer 00:22:21.649 --> 00:22:21.659 align:start position:0% remember our data availability layer 00:22:21.659 --> 00:22:24.950 align:start position:0% remember our data availability layer takes<00:22:21.900> the<00:22:22.080> form<00:22:22.260> of<00:22:22.440> this<00:22:22.740> array<00:22:23.220> of<00:22:23.400> blobs 00:22:24.950 --> 00:22:24.960 align:start position:0% takes the form of this array of blobs 00:22:24.960 --> 00:22:26.810 align:start position:0% takes the form of this array of blobs so<00:22:25.500> we<00:22:25.620> want<00:22:25.799> a<00:22:25.919> function<00:22:26.100> to<00:22:26.340> access<00:22:26.460> this 00:22:26.810 --> 00:22:26.820 align:start position:0% so we want a function to access this 00:22:26.820 --> 00:22:28.970 align:start position:0% so we want a function to access this data<00:22:27.419> availability<00:22:27.720> layer<00:22:28.200> and<00:22:28.679> kind<00:22:28.799> of<00:22:28.860> an 00:22:28.970 --> 00:22:28.980 align:start position:0% data availability layer and kind of an 00:22:28.980 --> 00:22:30.230 align:start position:0% data availability layer and kind of an easy<00:22:29.159> way<00:22:29.340> to<00:22:29.460> do<00:22:29.580> this<00:22:29.700> is<00:22:29.880> you<00:22:30.000> have<00:22:30.120> this 00:22:30.230 --> 00:22:30.240 align:start position:0% easy way to do this is you have this 00:22:30.240 --> 00:22:32.390 align:start position:0% easy way to do this is you have this thing<00:22:30.419> that<00:22:30.539> says<00:22:30.780> get<00:22:30.960> Blob<00:22:31.380> by<00:22:31.620> Index<00:22:31.980> right 00:22:32.390 --> 00:22:32.400 align:start position:0% thing that says get Blob by Index right 00:22:32.400 --> 00:22:34.190 align:start position:0% thing that says get Blob by Index right if<00:22:32.940> it's<00:22:33.059> an<00:22:33.240> array<00:22:33.480> and<00:22:33.659> you<00:22:33.840> have<00:22:33.900> like<00:22:34.020> get 00:22:34.190 --> 00:22:34.200 align:start position:0% if it's an array and you have like get 00:22:34.200 --> 00:22:36.409 align:start position:0% if it's an array and you have like get Blob<00:22:34.559> by<00:22:34.799> index<00:22:35.100> you<00:22:35.280> can<00:22:35.400> access<00:22:35.520> any<00:22:35.940> element 00:22:36.409 --> 00:22:36.419 align:start position:0% Blob by index you can access any element 00:22:36.419 --> 00:22:38.149 align:start position:0% Blob by index you can access any element right 00:22:38.149 --> 00:22:38.159 align:start position:0% right 00:22:38.159 --> 00:22:39.890 align:start position:0% right but<00:22:38.640> there's<00:22:38.820> something<00:22:39.059> really<00:22:39.480> important 00:22:39.890 --> 00:22:39.900 align:start position:0% but there's something really important 00:22:39.900 --> 00:22:42.289 align:start position:0% but there's something really important being<00:22:40.260> formalized<00:22:40.919> in<00:22:41.100> this<00:22:41.220> idea 00:22:42.289 --> 00:22:42.299 align:start position:0% being formalized in this idea 00:22:42.299 --> 00:22:44.570 align:start position:0% being formalized in this idea and<00:22:43.080> the<00:22:43.380> important<00:22:43.679> thing<00:22:43.860> is<00:22:44.100> that<00:22:44.280> there's 00:22:44.570 --> 00:22:44.580 align:start position:0% and the important thing is that there's 00:22:44.580 --> 00:22:46.850 align:start position:0% and the important thing is that there's two<00:22:45.059> properties<00:22:45.600> that<00:22:45.840> this<00:22:46.140> function<00:22:46.440> kind 00:22:46.850 --> 00:22:46.860 align:start position:0% two properties that this function kind 00:22:46.860 --> 00:22:49.070 align:start position:0% two properties that this function kind of<00:22:46.980> encodes<00:22:47.280> under<00:22:47.580> the<00:22:47.760> hood<00:22:47.960> the<00:22:48.960> first 00:22:49.070 --> 00:22:49.080 align:start position:0% of encodes under the hood the first 00:22:49.080 --> 00:22:51.649 align:start position:0% of encodes under the hood the first property<00:22:49.559> is<00:22:50.039> that<00:22:50.220> the<00:22:50.400> ability<00:22:50.700> to<00:22:51.120> resolve 00:22:51.649 --> 00:22:51.659 align:start position:0% property is that the ability to resolve 00:22:51.659 --> 00:22:53.149 align:start position:0% property is that the ability to resolve this<00:22:51.900> function<00:22:52.200> the<00:22:52.559> ability<00:22:52.799> to<00:22:52.980> actually 00:22:53.149 --> 00:22:53.159 align:start position:0% this function the ability to actually 00:22:53.159 --> 00:22:56.210 align:start position:0% this function the ability to actually return<00:22:53.520> a<00:22:53.880> blob<00:22:54.179> by<00:22:54.480> a<00:22:54.659> given<00:22:54.900> index<00:22:55.200> is<00:22:55.860> fully 00:22:56.210 --> 00:22:56.220 align:start position:0% return a blob by a given index is fully 00:22:56.220 --> 00:22:58.789 align:start position:0% return a blob by a given index is fully dependent<00:22:56.580> on<00:22:56.940> actual<00:22:57.419> availability<00:22:57.960> of<00:22:58.380> data 00:22:58.789 --> 00:22:58.799 align:start position:0% dependent on actual availability of data 00:22:58.799 --> 00:23:01.190 align:start position:0% dependent on actual availability of data on<00:22:59.280> the<00:22:59.400> data<00:22:59.640> availability<00:23:00.000> layer<00:23:00.480> if<00:23:01.080> the 00:23:01.190 --> 00:23:01.200 align:start position:0% on the data availability layer if the 00:23:01.200 --> 00:23:03.230 align:start position:0% on the data availability layer if the data<00:23:01.500> is<00:23:01.559> not<00:23:01.740> available<00:23:01.919> how<00:23:02.880> are<00:23:03.000> you<00:23:03.120> going 00:23:03.230 --> 00:23:03.240 align:start position:0% data is not available how are you going 00:23:03.240 --> 00:23:04.490 align:start position:0% data is not available how are you going to<00:23:03.360> return<00:23:03.480> something<00:23:03.780> out<00:23:04.020> of<00:23:04.140> this<00:23:04.260> function 00:23:04.490 --> 00:23:04.500 align:start position:0% to return something out of this function 00:23:04.500 --> 00:23:05.810 align:start position:0% to return something out of this function you<00:23:04.799> just<00:23:04.919> can't 00:23:05.810 --> 00:23:05.820 align:start position:0% you just can't 00:23:05.820 --> 00:23:07.430 align:start position:0% you just can't the<00:23:06.299> second<00:23:06.419> thing<00:23:06.600> is<00:23:06.780> that<00:23:06.960> you<00:23:07.140> have<00:23:07.320> to 00:23:07.430 --> 00:23:07.440 align:start position:0% the second thing is that you have to 00:23:07.440 --> 00:23:09.710 align:start position:0% the second thing is that you have to depend<00:23:07.799> on<00:23:08.039> a<00:23:08.220> mechanism<00:23:08.580> to<00:23:09.000> prove<00:23:09.360> that<00:23:09.539> the 00:23:09.710 --> 00:23:09.720 align:start position:0% depend on a mechanism to prove that the 00:23:09.720 --> 00:23:11.690 align:start position:0% depend on a mechanism to prove that the blobs<00:23:10.080> are<00:23:10.200> correct<00:23:10.500> because<00:23:11.159> otherwise<00:23:11.520> I 00:23:11.690 --> 00:23:11.700 align:start position:0% blobs are correct because otherwise I 00:23:11.700 --> 00:23:12.950 align:start position:0% blobs are correct because otherwise I can<00:23:11.820> just<00:23:11.940> give<00:23:12.059> you<00:23:12.179> anything<00:23:12.360> right<00:23:12.720> and<00:23:12.840> I 00:23:12.950 --> 00:23:12.960 align:start position:0% can just give you anything right and I 00:23:12.960 --> 00:23:14.270 align:start position:0% can just give you anything right and I can<00:23:13.020> just<00:23:13.140> say<00:23:13.260> oh<00:23:13.320> the<00:23:13.559> database<00:23:13.860> is<00:23:14.039> you<00:23:14.220> know 00:23:14.270 --> 00:23:14.280 align:start position:0% can just say oh the database is you know 00:23:14.280 --> 00:23:15.470 align:start position:0% can just say oh the database is you know ABC<00:23:14.700> but<00:23:14.940> it<00:23:15.000> was<00:23:15.120> really<00:23:15.240> something 00:23:15.470 --> 00:23:15.480 align:start position:0% ABC but it was really something 00:23:15.480 --> 00:23:17.450 align:start position:0% ABC but it was really something completely<00:23:15.900> different<00:23:16.080> so<00:23:16.740> you<00:23:16.860> need<00:23:17.039> a<00:23:17.220> proof 00:23:17.450 --> 00:23:17.460 align:start position:0% completely different so you need a proof 00:23:17.460 --> 00:23:20.930 align:start position:0% completely different so you need a proof mechanism<00:23:18.320> let's<00:23:19.320> see<00:23:19.440> if<00:23:19.559> we<00:23:19.740> okay<00:23:20.580> let<00:23:20.760> me<00:23:20.880> go 00:23:20.930 --> 00:23:20.940 align:start position:0% mechanism let's see if we okay let me go 00:23:20.940 --> 00:23:22.490 align:start position:0% mechanism let's see if we okay let me go to<00:23:21.059> this<00:23:21.179> really<00:23:21.240> quickly<00:23:21.600> go 00:23:22.490 --> 00:23:22.500 align:start position:0% to this really quickly go 00:23:22.500 --> 00:23:25.789 align:start position:0% to this really quickly go back<00:23:23.100> for<00:23:23.340> a<00:23:23.460> second<00:23:23.580> okay<00:23:23.760> so<00:23:24.360> in<00:23:24.539> ethereum<00:23:25.080> uh 00:23:25.789 --> 00:23:25.799 align:start position:0% back for a second okay so in ethereum uh 00:23:25.799 --> 00:23:27.110 align:start position:0% back for a second okay so in ethereum uh you<00:23:25.919> know<00:23:26.039> you<00:23:26.220> know<00:23:26.340> the<00:23:26.460> proof<00:23:26.700> mechanism 00:23:27.110 --> 00:23:27.120 align:start position:0% you know you know the proof mechanism 00:23:27.120 --> 00:23:28.549 align:start position:0% you know you know the proof mechanism we'll<00:23:27.419> get<00:23:27.600> to<00:23:27.720> that<00:23:27.840> in<00:23:27.960> a<00:23:28.080> second<00:23:28.200> but<00:23:28.380> for 00:23:28.549 --> 00:23:28.559 align:start position:0% we'll get to that in a second but for 00:23:28.559 --> 00:23:30.710 align:start position:0% we'll get to that in a second but for something<00:23:28.679> like<00:23:28.919> let's<00:23:29.100> say<00:23:29.280> Celestia<00:23:29.940> this 00:23:30.710 --> 00:23:30.720 align:start position:0% something like let's say Celestia this 00:23:30.720 --> 00:23:32.810 align:start position:0% something like let's say Celestia this Celestia's<00:23:31.440> data<00:23:31.740> lives<00:23:31.980> on<00:23:32.100> a<00:23:32.220> chain<00:23:32.400> other 00:23:32.810 --> 00:23:32.820 align:start position:0% Celestia's data lives on a chain other 00:23:32.820 --> 00:23:35.210 align:start position:0% Celestia's data lives on a chain other than<00:23:33.059> ethereum<00:23:33.659> and<00:23:34.320> so<00:23:34.380> what<00:23:34.559> we<00:23:34.679> need<00:23:34.860> if<00:23:35.100> we 00:23:35.210 --> 00:23:35.220 align:start position:0% than ethereum and so what we need if we 00:23:35.220 --> 00:23:36.890 align:start position:0% than ethereum and so what we need if we want<00:23:35.340> to<00:23:35.460> prove<00:23:35.820> that<00:23:36.000> a<00:23:36.179> given<00:23:36.360> correct<00:23:36.539> piece 00:23:36.890 --> 00:23:36.900 align:start position:0% want to prove that a given correct piece 00:23:36.900 --> 00:23:38.270 align:start position:0% want to prove that a given correct piece of<00:23:37.020> data<00:23:37.260> is<00:23:37.320> correct<00:23:37.620> we<00:23:37.919> need<00:23:38.039> to<00:23:38.159> First 00:23:38.270 --> 00:23:38.280 align:start position:0% of data is correct we need to First 00:23:38.280 --> 00:23:41.149 align:start position:0% of data is correct we need to First carry<00:23:38.760> over<00:23:38.940> commitments<00:23:39.720> to<00:23:39.960> Celestia<00:23:40.500> on 00:23:41.149 --> 00:23:41.159 align:start position:0% carry over commitments to Celestia on 00:23:41.159 --> 00:23:43.010 align:start position:0% carry over commitments to Celestia on ethereum<00:23:41.700> and<00:23:42.179> then<00:23:42.240> we<00:23:42.419> need<00:23:42.539> to<00:23:42.659> prove 00:23:43.010 --> 00:23:43.020 align:start position:0% ethereum and then we need to prove 00:23:43.020 --> 00:23:45.169 align:start position:0% ethereum and then we need to prove against<00:23:43.200> those<00:23:43.559> commitments<00:23:44.159> so<00:23:44.760> now<00:23:44.940> we're 00:23:45.169 --> 00:23:45.179 align:start position:0% against those commitments so now we're 00:23:45.179 --> 00:23:47.450 align:start position:0% against those commitments so now we're essentially<00:23:45.539> relying<00:23:46.200> on<00:23:46.440> the<00:23:46.679> not<00:23:47.039> only<00:23:47.220> are 00:23:47.450 --> 00:23:47.460 align:start position:0% essentially relying on the not only are 00:23:47.460 --> 00:23:49.430 align:start position:0% essentially relying on the not only are we<00:23:47.640> relying<00:23:48.000> on<00:23:48.240> the<00:23:48.419> availability<00:23:48.900> of<00:23:49.260> the 00:23:49.430 --> 00:23:49.440 align:start position:0% we relying on the availability of the 00:23:49.440 --> 00:23:51.470 align:start position:0% we relying on the availability of the data<00:23:49.679> availability<00:23:50.039> layer<00:23:50.580> we're<00:23:51.120> also 00:23:51.470 --> 00:23:51.480 align:start position:0% data availability layer we're also 00:23:51.480 --> 00:23:53.750 align:start position:0% data availability layer we're also relying<00:23:51.900> on<00:23:52.080> the<00:23:52.320> correctness<00:23:52.799> of<00:23:53.580> the 00:23:53.750 --> 00:23:53.760 align:start position:0% relying on the correctness of the 00:23:53.760 --> 00:23:55.430 align:start position:0% relying on the correctness of the function<00:23:54.000> essentially<00:23:54.539> the<00:23:54.780> light<00:23:54.960> client 00:23:55.430 --> 00:23:55.440 align:start position:0% function essentially the light client 00:23:55.440 --> 00:23:58.130 align:start position:0% function essentially the light client that<00:23:55.919> is<00:23:56.039> carrying<00:23:56.520> commitments<00:23:57.179> to<00:23:57.600> Celestia 00:23:58.130 --> 00:23:58.140 align:start position:0% that is carrying commitments to Celestia 00:23:58.140 --> 00:24:00.289 align:start position:0% that is carrying commitments to Celestia onto<00:23:58.679> ethereum<00:23:59.100> there's<00:23:59.400> two<00:23:59.940> things<00:24:00.120> that 00:24:00.289 --> 00:24:00.299 align:start position:0% onto ethereum there's two things that 00:24:00.299 --> 00:24:01.909 align:start position:0% onto ethereum there's two things that you<00:24:00.419> need<00:24:00.539> to<00:24:00.659> think<00:24:00.780> about<00:24:00.900> when<00:24:01.500> you<00:24:01.679> want<00:24:01.799> to 00:24:01.909 --> 00:24:01.919 align:start position:0% you need to think about when you want to 00:24:01.919 --> 00:24:03.830 align:start position:0% you need to think about when you want to use<00:24:02.039> something<00:24:02.280> like<00:24:02.460> Celestia<00:24:03.000> as<00:24:03.419> your<00:24:03.600> data 00:24:03.830 --> 00:24:03.840 align:start position:0% use something like Celestia as your data 00:24:03.840 --> 00:24:05.450 align:start position:0% use something like Celestia as your data availability<00:24:04.200> layer 00:24:05.450 --> 00:24:05.460 align:start position:0% availability layer 00:24:05.460 --> 00:24:07.070 align:start position:0% availability layer all<00:24:05.940> right<00:24:06.120> so<00:24:06.240> let's<00:24:06.419> just<00:24:06.600> look<00:24:06.780> quickly 00:24:07.070 --> 00:24:07.080 align:start position:0% all right so let's just look quickly 00:24:07.080 --> 00:24:08.870 align:start position:0% all right so let's just look quickly about<00:24:07.200> how<00:24:07.559> Bedrock<00:24:08.159> sort<00:24:08.460> of<00:24:08.580> does<00:24:08.700> this 00:24:08.870 --> 00:24:08.880 align:start position:0% about how Bedrock sort of does this 00:24:08.880 --> 00:24:11.870 align:start position:0% about how Bedrock sort of does this validation<00:24:09.419> in<00:24:10.260> Bedrock<00:24:10.799> we<00:24:11.340> start<00:24:11.520> with<00:24:11.700> the 00:24:11.870 --> 00:24:11.880 align:start position:0% validation in Bedrock we start with the 00:24:11.880 --> 00:24:13.669 align:start position:0% validation in Bedrock we start with the latest<00:24:12.000> block<00:24:12.240> this<00:24:12.900> is<00:24:12.960> the<00:24:13.140> magic<00:24:13.320> right 00:24:13.669 --> 00:24:13.679 align:start position:0% latest block this is the magic right 00:24:13.679 --> 00:24:16.430 align:start position:0% latest block this is the magic right ethereum<00:24:14.460> has<00:24:14.700> this<00:24:14.940> beautiful<00:24:15.120> thing<00:24:15.600> that 00:24:16.430 --> 00:24:16.440 align:start position:0% ethereum has this beautiful thing that 00:24:16.440 --> 00:24:18.770 align:start position:0% ethereum has this beautiful thing that ethereum<00:24:16.980> from<00:24:17.640> the<00:24:17.820> latest<00:24:18.000> block<00:24:18.299> you<00:24:18.659> can 00:24:18.770 --> 00:24:18.780 align:start position:0% ethereum from the latest block you can 00:24:18.780 --> 00:24:21.409 align:start position:0% ethereum from the latest block you can access<00:24:19.100> everything<00:24:20.100> it's<00:24:20.760> beautiful<00:24:21.000> the 00:24:21.409 --> 00:24:21.419 align:start position:0% access everything it's beautiful the 00:24:21.419 --> 00:24:22.970 align:start position:0% access everything it's beautiful the block<00:24:21.600> hash<00:24:21.960> hidden<00:24:22.320> inside<00:24:22.440> of<00:24:22.740> the<00:24:22.799> latest 00:24:22.970 --> 00:24:22.980 align:start position:0% block hash hidden inside of the latest 00:24:22.980 --> 00:24:25.370 align:start position:0% block hash hidden inside of the latest block<00:24:23.220> hash<00:24:23.700> is<00:24:24.419> all<00:24:24.900> of<00:24:25.020> the<00:24:25.200> information 00:24:25.370 --> 00:24:25.380 align:start position:0% block hash is all of the information 00:24:25.380 --> 00:24:27.409 align:start position:0% block hash is all of the information about<00:24:25.799> ethereum<00:24:26.340> for<00:24:26.520> all<00:24:26.700> of<00:24:26.820> time<00:24:27.000> because<00:24:27.179> I 00:24:27.409 --> 00:24:27.419 align:start position:0% about ethereum for all of time because I 00:24:27.419 --> 00:24:29.270 align:start position:0% about ethereum for all of time because I can<00:24:27.539> start<00:24:27.659> with<00:24:27.840> the<00:24:27.960> latest<00:24:28.140> block<00:24:28.380> hash<00:24:28.799> and 00:24:29.270 --> 00:24:29.280 align:start position:0% can start with the latest block hash and 00:24:29.280 --> 00:24:30.710 align:start position:0% can start with the latest block hash and then<00:24:29.340> I<00:24:29.520> can<00:24:29.580> reveal<00:24:29.940> the<00:24:30.059> block<00:24:30.240> and<00:24:30.480> I<00:24:30.600> can 00:24:30.710 --> 00:24:30.720 align:start position:0% then I can reveal the block and I can 00:24:30.720 --> 00:24:32.570 align:start position:0% then I can reveal the block and I can reveal<00:24:30.960> the<00:24:31.080> previous<00:24:31.260> block<00:24:31.620> hash<00:24:31.980> and<00:24:32.400> I<00:24:32.520> can 00:24:32.570 --> 00:24:32.580 align:start position:0% reveal the previous block hash and I can 00:24:32.580 --> 00:24:34.070 align:start position:0% reveal the previous block hash and I can reveal<00:24:32.940> the<00:24:33.059> previous<00:24:33.240> block<00:24:33.539> hash<00:24:33.840> for<00:24:33.960> that 00:24:34.070 --> 00:24:34.080 align:start position:0% reveal the previous block hash for that 00:24:34.080 --> 00:24:35.630 align:start position:0% reveal the previous block hash for that and<00:24:34.200> I<00:24:34.320> can<00:24:34.380> just<00:24:34.500> go<00:24:34.799> back<00:24:34.919> in<00:24:35.159> time<00:24:35.280> to 00:24:35.630 --> 00:24:35.640 align:start position:0% and I can just go back in time to 00:24:35.640 --> 00:24:38.090 align:start position:0% and I can just go back in time to infinity<00:24:35.820> and<00:24:36.600> I<00:24:36.720> can<00:24:36.840> access<00:24:37.080> every<00:24:37.799> single 00:24:38.090 --> 00:24:38.100 align:start position:0% infinity and I can access every single 00:24:38.100 --> 00:24:40.490 align:start position:0% infinity and I can access every single block<00:24:38.340> in<00:24:39.120> the<00:24:39.299> entire<00:24:39.539> history<00:24:39.780> of<00:24:40.080> ethereum 00:24:40.490 --> 00:24:40.500 align:start position:0% block in the entire history of ethereum 00:24:40.500 --> 00:24:42.409 align:start position:0% block in the entire history of ethereum and<00:24:40.679> not<00:24:40.799> just<00:24:40.919> every<00:24:41.100> single<00:24:41.400> block<00:24:41.580> I<00:24:42.299> can 00:24:42.409 --> 00:24:42.419 align:start position:0% and not just every single block I can 00:24:42.419 --> 00:24:44.750 align:start position:0% and not just every single block I can pull<00:24:42.659> out<00:24:42.840> every<00:24:43.500> single<00:24:43.799> piece<00:24:44.039> of<00:24:44.159> data<00:24:44.460> in 00:24:44.750 --> 00:24:44.760 align:start position:0% pull out every single piece of data in 00:24:44.760 --> 00:24:46.730 align:start position:0% pull out every single piece of data in every<00:24:44.940> single<00:24:45.240> piece<00:24:45.539> every<00:24:46.020> single<00:24:46.320> block<00:24:46.500> in 00:24:46.730 --> 00:24:46.740 align:start position:0% every single piece every single block in 00:24:46.740 --> 00:24:48.529 align:start position:0% every single piece every single block in ethereum<00:24:47.159> and<00:24:47.760> so<00:24:47.880> what<00:24:48.000> I'm<00:24:48.120> going<00:24:48.179> to<00:24:48.299> do<00:24:48.360> in 00:24:48.529 --> 00:24:48.539 align:start position:0% ethereum and so what I'm going to do in 00:24:48.539 --> 00:24:49.850 align:start position:0% ethereum and so what I'm going to do in my<00:24:48.720> validation<00:24:49.080> function<00:24:49.440> is<00:24:49.559> I'm<00:24:49.740> going<00:24:49.799> to 00:24:49.850 --> 00:24:49.860 align:start position:0% my validation function is I'm going to 00:24:49.860 --> 00:24:52.010 align:start position:0% my validation function is I'm going to start<00:24:49.980> with<00:24:50.159> the<00:24:50.280> latest<00:24:50.400> block<00:24:50.700> and<00:24:51.539> in<00:24:51.659> my<00:24:51.840> is 00:24:52.010 --> 00:24:52.020 align:start position:0% start with the latest block and in my is 00:24:52.020 --> 00:24:53.570 align:start position:0% start with the latest block and in my is all<00:24:52.260> of<00:24:52.380> this<00:24:52.440> is<00:24:52.559> kind<00:24:52.740> of<00:24:52.799> hidden<00:24:53.100> inside<00:24:53.280> of 00:24:53.570 --> 00:24:53.580 align:start position:0% all of this is kind of hidden inside of 00:24:53.580 --> 00:24:55.430 align:start position:0% all of this is kind of hidden inside of the<00:24:53.700> the<00:24:53.820> fault<00:24:54.179> proof<00:24:54.480> but<00:24:54.600> my<00:24:54.840> program<00:24:55.080> is 00:24:55.430 --> 00:24:55.440 align:start position:0% the the fault proof but my program is 00:24:55.440 --> 00:24:56.570 align:start position:0% the the fault proof but my program is going<00:24:55.620> to<00:24:55.679> walk<00:24:55.799> backwards<00:24:56.280> and<00:24:56.400> walk 00:24:56.570 --> 00:24:56.580 align:start position:0% going to walk backwards and walk 00:24:56.580 --> 00:24:58.490 align:start position:0% going to walk backwards and walk backwards<00:24:57.000> and<00:24:57.059> walk<00:24:57.240> backwards<00:24:57.720> and<00:24:58.260> figure 00:24:58.490 --> 00:24:58.500 align:start position:0% backwards and walk backwards and figure 00:24:58.500 --> 00:25:00.770 align:start position:0% backwards and walk backwards and figure out<00:24:58.740> which<00:24:59.340> blob<00:24:59.760> in<00:25:00.000> the<00:25:00.120> data<00:25:00.360> availability 00:25:00.770 --> 00:25:00.780 align:start position:0% out which blob in the data availability 00:25:00.780 --> 00:25:02.750 align:start position:0% out which blob in the data availability layer<00:25:01.140> in<00:25:01.440> this<00:25:01.559> case<00:25:01.679> ethereum<00:25:02.220> blocks<00:25:02.580> it's 00:25:02.750 --> 00:25:02.760 align:start position:0% layer in this case ethereum blocks it's 00:25:02.760 --> 00:25:04.430 align:start position:0% layer in this case ethereum blocks it's going<00:25:03.000> to<00:25:03.120> start<00:25:03.419> the<00:25:03.840> state<00:25:04.020> transition 00:25:04.430 --> 00:25:04.440 align:start position:0% going to start the state transition 00:25:04.440 --> 00:25:06.710 align:start position:0% going to start the state transition function<00:25:04.860> loop<00:25:05.220> from<00:25:05.640> that's<00:25:06.179> the<00:25:06.360> loop<00:25:06.600> that 00:25:06.710 --> 00:25:06.720 align:start position:0% function loop from that's the loop that 00:25:06.720 --> 00:25:08.750 align:start position:0% function loop from that's the loop that we<00:25:06.900> just<00:25:07.080> saw<00:25:07.320> and<00:25:07.919> it's<00:25:08.100> going<00:25:08.220> to<00:25:08.220> apply<00:25:08.520> that 00:25:08.750 --> 00:25:08.760 align:start position:0% we just saw and it's going to apply that 00:25:08.760 --> 00:25:10.490 align:start position:0% we just saw and it's going to apply that Loop<00:25:09.059> over<00:25:09.299> and<00:25:09.419> over<00:25:09.600> and<00:25:09.720> over<00:25:09.900> again<00:25:10.020> in<00:25:10.320> the 00:25:10.490 --> 00:25:10.500 align:start position:0% Loop over and over and over again in the 00:25:10.500 --> 00:25:13.310 align:start position:0% Loop over and over and over again in the program<00:25:10.679> until<00:25:11.520> you<00:25:11.760> get<00:25:11.940> a<00:25:12.059> final<00:25:12.240> State<00:25:12.600> and 00:25:13.310 --> 00:25:13.320 align:start position:0% program until you get a final State and 00:25:13.320 --> 00:25:15.710 align:start position:0% program until you get a final State and you<00:25:13.440> compare<00:25:13.860> that<00:25:14.159> final<00:25:14.400> state<00:25:14.760> to<00:25:15.480> the 00:25:15.710 --> 00:25:15.720 align:start position:0% you compare that final state to the 00:25:15.720 --> 00:25:17.930 align:start position:0% you compare that final state to the final<00:25:15.900> state<00:25:16.260> that<00:25:16.860> you<00:25:17.159> pre<00:25:17.400> you<00:25:17.700> know<00:25:17.760> you 00:25:17.930 --> 00:25:17.940 align:start position:0% final state that you pre you know you 00:25:17.940 --> 00:25:19.909 align:start position:0% final state that you pre you know you proposed 00:25:19.909 --> 00:25:19.919 align:start position:0% proposed 00:25:19.919 --> 00:25:21.710 align:start position:0% proposed and<00:25:20.280> all<00:25:20.400> of<00:25:20.520> this<00:25:20.700> happens<00:25:20.880> inside<00:25:21.360> of<00:25:21.600> the 00:25:21.710 --> 00:25:21.720 align:start position:0% and all of this happens inside of the 00:25:21.720 --> 00:25:23.210 align:start position:0% and all of this happens inside of the fault<00:25:21.900> proof<00:25:22.260> so<00:25:22.380> none<00:25:22.559> of<00:25:22.679> this<00:25:22.799> computation 00:25:23.210 --> 00:25:23.220 align:start position:0% fault proof so none of this computation 00:25:23.220 --> 00:25:25.850 align:start position:0% fault proof so none of this computation really<00:25:23.640> happens<00:25:24.059> on<00:25:24.419> chain<00:25:24.659> you<00:25:25.440> just<00:25:25.500> sort<00:25:25.679> of 00:25:25.850 --> 00:25:25.860 align:start position:0% really happens on chain you just sort of 00:25:25.860 --> 00:25:27.289 align:start position:0% really happens on chain you just sort of have<00:25:26.279> to<00:25:26.460> you<00:25:26.640> know<00:25:26.700> if<00:25:26.940> you<00:25:27.000> want<00:25:27.179> to 00:25:27.289 --> 00:25:27.299 align:start position:0% have to you know if you want to 00:25:27.299 --> 00:25:28.430 align:start position:0% have to you know if you want to challenge<00:25:27.419> it<00:25:27.659> you<00:25:27.840> just<00:25:27.960> have<00:25:28.080> to<00:25:28.200> do<00:25:28.260> a 00:25:28.430 --> 00:25:28.440 align:start position:0% challenge it you just have to do a 00:25:28.440 --> 00:25:30.529 align:start position:0% challenge it you just have to do a single<00:25:28.679> step<00:25:28.860> but<00:25:29.700> this<00:25:29.820> is<00:25:29.940> the<00:25:30.120> magic<00:25:30.299> of 00:25:30.529 --> 00:25:30.539 align:start position:0% single step but this is the magic of 00:25:30.539 --> 00:25:32.630 align:start position:0% single step but this is the magic of ethereum<00:25:31.020> which<00:25:31.320> is<00:25:31.380> that<00:25:31.620> you<00:25:31.860> can<00:25:31.980> the<00:25:32.400> data 00:25:32.630 --> 00:25:32.640 align:start position:0% ethereum which is that you can the data 00:25:32.640 --> 00:25:34.970 align:start position:0% ethereum which is that you can the data is<00:25:32.760> guaranteed<00:25:33.120> to<00:25:33.360> be<00:25:33.480> available<00:25:33.720> and<00:25:34.679> the 00:25:34.970 --> 00:25:34.980 align:start position:0% is guaranteed to be available and the 00:25:34.980 --> 00:25:36.830 align:start position:0% is guaranteed to be available and the data<00:25:35.460> is<00:25:35.520> guaranteed<00:25:35.940> to<00:25:36.120> be<00:25:36.240> correct<00:25:36.539> because 00:25:36.830 --> 00:25:36.840 align:start position:0% data is guaranteed to be correct because 00:25:36.840 --> 00:25:39.049 align:start position:0% data is guaranteed to be correct because you're<00:25:37.080> settling<00:25:37.500> and<00:25:38.039> putting<00:25:38.460> data<00:25:38.760> onto 00:25:39.049 --> 00:25:39.059 align:start position:0% you're settling and putting data onto 00:25:39.059 --> 00:25:40.970 align:start position:0% you're settling and putting data onto the<00:25:39.179> same<00:25:39.360> place 00:25:40.970 --> 00:25:40.980 align:start position:0% the same place 00:25:40.980 --> 00:25:42.830 align:start position:0% the same place all<00:25:41.820> right<00:25:41.880> so<00:25:42.059> bringing<00:25:42.360> a<00:25:42.480> bell<00:25:42.600> back 00:25:42.830 --> 00:25:42.840 align:start position:0% all right so bringing a bell back 00:25:42.840 --> 00:25:44.210 align:start position:0% all right so bringing a bell back together<00:25:43.020> really<00:25:43.380> quickly 00:25:44.210 --> 00:25:44.220 align:start position:0% together really quickly 00:25:44.220 --> 00:25:45.890 align:start position:0% together really quickly um<00:25:44.279> with<00:25:44.520> the<00:25:44.640> multi-headed<00:25:45.240> angel<00:25:45.480> thing 00:25:45.890 --> 00:25:45.900 align:start position:0% um with the multi-headed angel thing 00:25:45.900 --> 00:25:48.049 align:start position:0% um with the multi-headed angel thing going<00:25:46.140> on<00:25:46.320> here<00:25:46.559> there's<00:25:47.340> a<00:25:47.520> lot<00:25:47.640> of<00:25:47.760> content 00:25:48.049 --> 00:25:48.059 align:start position:0% going on here there's a lot of content 00:25:48.059 --> 00:25:49.669 align:start position:0% going on here there's a lot of content but<00:25:48.299> there's<00:25:48.480> not<00:25:48.659> that<00:25:48.840> many<00:25:49.020> components<00:25:49.559> to 00:25:49.669 --> 00:25:49.679 align:start position:0% but there's not that many components to 00:25:49.679 --> 00:25:51.590 align:start position:0% but there's not that many components to something<00:25:49.860> like<00:25:50.100> this<00:25:50.480> remembering<00:25:51.480> the 00:25:51.590 --> 00:25:51.600 align:start position:0% something like this remembering the 00:25:51.600 --> 00:25:52.909 align:start position:0% something like this remembering the components<00:25:51.960> we<00:25:52.080> got<00:25:52.260> the<00:25:52.380> data<00:25:52.620> availability 00:25:52.909 --> 00:25:52.919 align:start position:0% components we got the data availability 00:25:52.919 --> 00:25:54.769 align:start position:0% components we got the data availability layer<00:25:53.340> which<00:25:53.460> this<00:25:53.700> is<00:25:53.880> array<00:25:54.059> of<00:25:54.179> bytes<00:25:54.539> right 00:25:54.769 --> 00:25:54.779 align:start position:0% layer which this is array of bytes right 00:25:54.779 --> 00:25:57.049 align:start position:0% layer which this is array of bytes right array<00:25:55.140> of<00:25:55.260> blobs<00:25:55.620> we've<00:25:56.340> got<00:25:56.400> the<00:25:56.580> derivation 00:25:57.049 --> 00:25:57.059 align:start position:0% array of blobs we've got the derivation 00:25:57.059 --> 00:25:58.610 align:start position:0% array of blobs we've got the derivation function<00:25:57.480> which<00:25:57.720> takes<00:25:57.900> the<00:25:58.140> previous<00:25:58.260> state 00:25:58.610 --> 00:25:58.620 align:start position:0% function which takes the previous state 00:25:58.620 --> 00:26:00.110 align:start position:0% function which takes the previous state and<00:25:58.799> the<00:25:58.980> date<00:25:59.039> availability<00:25:59.520> layer<00:25:59.880> and<00:26:00.000> it's 00:26:00.110 --> 00:26:00.120 align:start position:0% and the date availability layer and it's 00:26:00.120 --> 00:26:01.970 align:start position:0% and the date availability layer and it's either<00:26:00.299> going<00:26:00.480> to<00:26:00.539> spit<00:26:00.720> out<00:26:00.840> a<00:26:01.080> payload<00:26:01.620> or 00:26:01.970 --> 00:26:01.980 align:start position:0% either going to spit out a payload or 00:26:01.980 --> 00:26:03.710 align:start position:0% either going to spit out a payload or it's<00:26:02.100> going<00:26:02.279> to<00:26:02.340> spit<00:26:02.520> out<00:26:02.640> nothing<00:26:02.940> you've 00:26:03.710 --> 00:26:03.720 align:start position:0% it's going to spit out nothing you've 00:26:03.720 --> 00:26:05.269 align:start position:0% it's going to spit out nothing you've got<00:26:03.840> the<00:26:04.020> execution<00:26:04.440> function<00:26:04.799> which<00:26:05.039> takes 00:26:05.269 --> 00:26:05.279 align:start position:0% got the execution function which takes 00:26:05.279 --> 00:26:06.409 align:start position:0% got the execution function which takes the<00:26:05.460> previous<00:26:05.580> state<00:26:05.880> and<00:26:06.059> it's<00:26:06.179> going<00:26:06.360> to 00:26:06.409 --> 00:26:06.419 align:start position:0% the previous state and it's going to 00:26:06.419 --> 00:26:08.029 align:start position:0% the previous state and it's going to take<00:26:06.539> in<00:26:06.720> a<00:26:06.900> payload<00:26:07.320> generated<00:26:07.679> by<00:26:07.919> the 00:26:08.029 --> 00:26:08.039 align:start position:0% take in a payload generated by the 00:26:08.039 --> 00:26:09.590 align:start position:0% take in a payload generated by the derivation<00:26:08.460> function<00:26:08.880> it's<00:26:09.299> going<00:26:09.539> to 00:26:09.590 --> 00:26:09.600 align:start position:0% derivation function it's going to 00:26:09.600 --> 00:26:11.570 align:start position:0% derivation function it's going to produce<00:26:09.779> a<00:26:10.020> new<00:26:10.140> state<00:26:10.380> and<00:26:11.159> you've<00:26:11.279> got<00:26:11.400> this 00:26:11.570 --> 00:26:11.580 align:start position:0% produce a new state and you've got this 00:26:11.580 --> 00:26:13.490 align:start position:0% produce a new state and you've got this validity<00:26:12.059> function<00:26:12.419> and<00:26:12.960> then<00:26:13.080> inside<00:26:13.260> of 00:26:13.490 --> 00:26:13.500 align:start position:0% validity function and then inside of 00:26:13.500 --> 00:26:15.169 align:start position:0% validity function and then inside of this<00:26:13.620> validity<00:26:14.039> function<00:26:14.340> you<00:26:14.580> have<00:26:14.700> this<00:26:14.940> get 00:26:15.169 --> 00:26:15.179 align:start position:0% this validity function you have this get 00:26:15.179 --> 00:26:17.570 align:start position:0% this validity function you have this get Blob<00:26:15.600> by<00:26:15.779> Index<00:26:16.140> right<00:26:16.380> so<00:26:16.679> this<00:26:16.860> is<00:26:16.980> all<00:26:17.400> of 00:26:17.570 --> 00:26:17.580 align:start position:0% Blob by Index right so this is all of 00:26:17.580 --> 00:26:18.950 align:start position:0% Blob by Index right so this is all of this<00:26:17.700> composes<00:26:18.179> each<00:26:18.419> one<00:26:18.600> of<00:26:18.779> these 00:26:18.950 --> 00:26:18.960 align:start position:0% this composes each one of these 00:26:18.960 --> 00:26:21.289 align:start position:0% this composes each one of these different<00:26:19.080> layers<00:26:19.559> is<00:26:20.039> an<00:26:20.279> API<00:26:20.640> that<00:26:21.000> you<00:26:21.179> can 00:26:21.289 --> 00:26:21.299 align:start position:0% different layers is an API that you can 00:26:21.299 --> 00:26:22.430 align:start position:0% different layers is an API that you can plug<00:26:21.480> into 00:26:22.430 --> 00:26:22.440 align:start position:0% plug into 00:26:22.440 --> 00:26:23.990 align:start position:0% plug into so<00:26:22.860> you<00:26:23.039> can<00:26:23.159> take<00:26:23.279> this<00:26:23.460> or<00:26:23.640> you<00:26:23.760> can<00:26:23.820> build 00:26:23.990 --> 00:26:24.000 align:start position:0% so you can take this or you can build 00:26:24.000 --> 00:26:25.909 align:start position:0% so you can take this or you can build your<00:26:24.240> your<00:26:24.600> dream<00:26:24.840> chain<00:26:25.140> right<00:26:25.380> this<00:26:25.679> isn't 00:26:25.909 --> 00:26:25.919 align:start position:0% your your dream chain right this isn't 00:26:25.919 --> 00:26:28.190 align:start position:0% your your dream chain right this isn't just<00:26:26.039> Theory<00:26:26.400> this<00:26:26.760> is<00:26:26.880> in<00:26:27.360> optimism's<00:26:28.020> code 00:26:28.190 --> 00:26:28.200 align:start position:0% just Theory this is in optimism's code 00:26:28.200 --> 00:26:30.289 align:start position:0% just Theory this is in optimism's code base<00:26:28.380> in<00:26:28.620> the<00:26:28.740> Bedrock<00:26:29.159> code<00:26:29.340> base<00:26:29.580> you<00:26:30.240> can 00:26:30.289 --> 00:26:30.299 align:start position:0% base in the Bedrock code base you can 00:26:30.299 --> 00:26:32.029 align:start position:0% base in the Bedrock code base you can build<00:26:30.539> whatever<00:26:30.840> you<00:26:31.200> want<00:26:31.320> do<00:26:31.740> you<00:26:31.860> want<00:26:31.919> to 00:26:32.029 --> 00:26:32.039 align:start position:0% build whatever you want do you want to 00:26:32.039 --> 00:26:34.010 align:start position:0% build whatever you want do you want to build<00:26:32.159> a<00:26:32.340> Bitcoin<00:26:32.760> plasma<00:26:33.120> yeah<00:26:33.659> you<00:26:33.900> can 00:26:34.010 --> 00:26:34.020 align:start position:0% build a Bitcoin plasma yeah you can 00:26:34.020 --> 00:26:35.390 align:start position:0% build a Bitcoin plasma yeah you can build<00:26:34.140> a<00:26:34.320> Bitcoin<00:26:34.620> plasma<00:26:34.919> you<00:26:35.100> can<00:26:35.220> do<00:26:35.340> it 00:26:35.390 --> 00:26:35.400 align:start position:0% build a Bitcoin plasma you can do it 00:26:35.400 --> 00:26:36.950 align:start position:0% build a Bitcoin plasma you can do it really<00:26:35.520> easily<00:26:35.820> go<00:26:36.059> build<00:26:36.240> a<00:26:36.360> Bitcoin<00:26:36.659> plasma 00:26:36.950 --> 00:26:36.960 align:start position:0% really easily go build a Bitcoin plasma 00:26:36.960 --> 00:26:38.330 align:start position:0% really easily go build a Bitcoin plasma you<00:26:37.140> want<00:26:37.260> to<00:26:37.320> build<00:26:37.440> a<00:26:37.620> bridge<00:26:38.039> that's 00:26:38.330 --> 00:26:38.340 align:start position:0% you want to build a bridge that's 00:26:38.340 --> 00:26:40.430 align:start position:0% you want to build a bridge that's actually<00:26:38.580> a<00:26:38.820> roll-up<00:26:39.120> and<00:26:39.720> it<00:26:39.840> has<00:26:40.080> multiple 00:26:40.430 --> 00:26:40.440 align:start position:0% actually a roll-up and it has multiple 00:26:40.440 --> 00:26:41.930 align:start position:0% actually a roll-up and it has multiple data<00:26:40.799> availability<00:26:41.100> layers<00:26:41.520> and<00:26:41.700> multiple 00:26:41.930 --> 00:26:41.940 align:start position:0% data availability layers and multiple 00:26:41.940 --> 00:26:44.029 align:start position:0% data availability layers and multiple settlement<00:26:42.299> layers<00:26:42.659> why<00:26:42.840> not 00:26:44.029 --> 00:26:44.039 align:start position:0% settlement layers why not 00:26:44.039 --> 00:26:45.470 align:start position:0% settlement layers why not um<00:26:44.159> you<00:26:44.340> want<00:26:44.400> to<00:26:44.520> build<00:26:44.640> another<00:26:44.820> paralyzed 00:26:45.470 --> 00:26:45.480 align:start position:0% um you want to build another paralyzed 00:26:45.480 --> 00:26:47.269 align:start position:0% um you want to build another paralyzed VM<00:26:45.779> and<00:26:45.960> raise<00:26:46.200> like<00:26:46.440> 200<00:26:46.740> million<00:26:47.039> dollars 00:26:47.269 --> 00:26:47.279 align:start position:0% VM and raise like 200 million dollars 00:26:47.279 --> 00:26:49.909 align:start position:0% VM and raise like 200 million dollars from<00:26:47.460> VCS<00:26:47.940> why<00:26:48.059> not<00:26:48.179> you<00:26:48.360> can<00:26:48.480> do<00:26:48.600> that 00:26:49.909 --> 00:26:49.919 align:start position:0% from VCS why not you can do that 00:26:49.919 --> 00:26:51.950 align:start position:0% from VCS why not you can do that you<00:26:50.520> can<00:26:50.580> build<00:26:50.760> whatever<00:26:51.000> you<00:26:51.299> want<00:26:51.480> you<00:26:51.779> just 00:26:51.950 --> 00:26:51.960 align:start position:0% you can build whatever you want you just 00:26:51.960 --> 00:26:53.870 align:start position:0% you can build whatever you want you just have<00:26:52.140> to<00:26:52.320> fit<00:26:52.500> the<00:26:52.740> apis<00:26:53.100> right<00:26:53.400> that's<00:26:53.580> what 00:26:53.870 --> 00:26:53.880 align:start position:0% have to fit the apis right that's what 00:26:53.880 --> 00:26:56.330 align:start position:0% have to fit the apis right that's what we've<00:26:54.539> we've<00:26:55.140> boiled<00:26:55.559> this<00:26:55.740> all<00:26:55.860> down<00:26:56.039> to<00:26:56.220> a 00:26:56.330 --> 00:26:56.340 align:start position:0% we've we've boiled this all down to a 00:26:56.340 --> 00:26:58.610 align:start position:0% we've we've boiled this all down to a set<00:26:56.460> of<00:26:56.580> apis<00:26:57.000> if<00:26:57.480> you<00:26:57.600> fill<00:26:57.720> the<00:26:57.900> apis<00:26:58.260> you<00:26:58.500> can 00:26:58.610 --> 00:26:58.620 align:start position:0% set of apis if you fill the apis you can 00:26:58.620 --> 00:26:59.510 align:start position:0% set of apis if you fill the apis you can build<00:26:58.740> it 00:26:59.510 --> 00:26:59.520 align:start position:0% build it 00:26:59.520 --> 00:27:01.850 align:start position:0% build it so<00:26:59.940> that's<00:27:00.120> the<00:27:00.360> whole<00:27:00.480> talk<00:27:00.720> uh<00:27:01.559> thank<00:27:01.740> you 00:27:01.850 --> 00:27:01.860 align:start position:0% so that's the whole talk uh thank you 00:27:01.860 --> 00:27:03.470 align:start position:0% so that's the whole talk uh thank you try<00:27:02.100> to<00:27:02.220> remember<00:27:02.340> life<00:27:02.700> my<00:27:03.000> name<00:27:03.059> is<00:27:03.120> Kelvin 00:27:03.470 --> 00:27:03.480 align:start position:0% try to remember life my name is Kelvin 00:27:03.480 --> 00:27:05.870 align:start position:0% try to remember life my name is Kelvin I'm<00:27:03.720> building<00:27:03.840> the<00:27:04.020> optimism<00:27:04.380> Collective<00:27:04.919> uh 00:27:05.870 --> 00:27:05.880 align:start position:0% I'm building the optimism Collective uh 00:27:05.880 --> 00:27:11.029 align:start position:0% I'm building the optimism Collective uh Bedrock<00:27:06.360> specs<00:27:06.840> get<00:27:07.140> in<00:27:07.380> touch 00:27:11.029 --> 00:27:11.039 align:start position:0% 00:27:11.039 --> 00:27:16.010 align:start position:0% thank<00:27:11.520> you 00:27:16.010 --> 00:27:16.020 align:start position:0% 00:27:16.020 --> 00:27:18.860 align:start position:0% build<00:27:16.320> something<00:27:16.559> cool