WEBVTT Kind: captions Language: en 00:00:00.030 --> 00:00:02.360 align:start position:0% up<00:00:00.659> next<00:00:00.810> we<00:00:00.989> have<00:00:01.020> Paul<00:00:01.350> and<00:00:01.589> Guillaume<00:00:02.129> who 00:00:02.360 --> 00:00:02.370 align:start position:0% up next we have Paul and Guillaume who 00:00:02.370 --> 00:00:04.910 align:start position:0% up next we have Paul and Guillaume who are<00:00:02.429> going<00:00:02.639> to<00:00:02.760> present<00:00:03.149> on<00:00:03.330> Watson<00:00:04.290> engines 00:00:04.910 --> 00:00:04.920 align:start position:0% are going to present on Watson engines 00:00:04.920 --> 00:00:14.089 align:start position:0% are going to present on Watson engines get<00:00:05.490> away<00:00:10.700> okay<00:00:11.700> hello<00:00:12.530> my<00:00:13.530> name<00:00:13.679> is<00:00:13.710> Paul<00:00:13.980> I'm 00:00:14.089 --> 00:00:14.099 align:start position:0% get away okay hello my name is Paul I'm 00:00:14.099 --> 00:00:15.499 align:start position:0% get away okay hello my name is Paul I'm going<00:00:14.219> to<00:00:14.280> talk<00:00:14.429> about<00:00:14.519> webassembly<00:00:14.969> engines 00:00:15.499 --> 00:00:15.509 align:start position:0% going to talk about webassembly engines 00:00:15.509 --> 00:00:20.660 align:start position:0% going to talk about webassembly engines for<00:00:16.379> awasum<00:00:18.109> those<00:00:19.109> are<00:00:19.320> they<00:00:19.439> one<00:00:20.100> two<00:00:20.310> three 00:00:20.660 --> 00:00:20.670 align:start position:0% for awasum those are they one two three 00:00:20.670 --> 00:00:25.160 align:start position:0% for awasum those are they one two three four<00:00:21.000> five<00:00:21.270> six<00:00:21.539> the<00:00:22.380> first<00:00:22.529> three<00:00:23.070> or<00:00:23.789> four<00:00:24.689> we 00:00:25.160 --> 00:00:25.170 align:start position:0% four five six the first three or four we 00:00:25.170 --> 00:00:27.640 align:start position:0% four five six the first three or four we have<00:00:25.350> working<00:00:25.650> at<00:00:25.890> in<00:00:26.099> some<00:00:26.369> in<00:00:26.670> some<00:00:27.150> capacity 00:00:27.640 --> 00:00:27.650 align:start position:0% have working at in some in some capacity 00:00:27.650 --> 00:00:30.349 align:start position:0% have working at in some in some capacity it<00:00:28.650> seems<00:00:28.890> that<00:00:29.039> there's<00:00:29.490> a<00:00:29.580> big<00:00:29.760> push<00:00:30.000> to<00:00:30.029> use 00:00:30.349 --> 00:00:30.359 align:start position:0% it seems that there's a big push to use 00:00:30.359 --> 00:00:33.139 align:start position:0% it seems that there's a big push to use the<00:00:30.929> Firefox<00:00:31.140> in<00:00:31.560> the<00:00:31.619> chromium<00:00:31.890> web<00:00:32.759> assembly 00:00:33.139 --> 00:00:33.149 align:start position:0% the Firefox in the chromium web assembly 00:00:33.149 --> 00:00:35.120 align:start position:0% the Firefox in the chromium web assembly engines<00:00:33.480> they<00:00:33.630> have<00:00:33.750> they<00:00:34.170> have<00:00:34.260> various<00:00:34.890> sort 00:00:35.120 --> 00:00:35.130 align:start position:0% engines they have they have various sort 00:00:35.130 --> 00:00:37.850 align:start position:0% engines they have they have various sort of<00:00:35.219> tiers<00:00:35.910> of<00:00:36.120> engines<00:00:36.809> they<00:00:37.649> have<00:00:37.739> their 00:00:37.850 --> 00:00:37.860 align:start position:0% of tiers of engines they have their 00:00:37.860 --> 00:00:39.470 align:start position:0% of tiers of engines they have their baseline<00:00:38.250> engines<00:00:38.430> which<00:00:38.730> are<00:00:38.850> just<00:00:39.059> single 00:00:39.470 --> 00:00:39.480 align:start position:0% baseline engines which are just single 00:00:39.480 --> 00:00:42.139 align:start position:0% baseline engines which are just single pass<00:00:39.660> linear<00:00:40.469> paths<00:00:40.710> to<00:00:41.280> compiled<00:00:41.579> to<00:00:41.910> machine 00:00:42.139 --> 00:00:42.149 align:start position:0% pass linear paths to compiled to machine 00:00:42.149 --> 00:00:44.030 align:start position:0% pass linear paths to compiled to machine code<00:00:42.660> then<00:00:43.200> there<00:00:43.379> are<00:00:43.500> the<00:00:43.620> optimized 00:00:44.030 --> 00:00:44.040 align:start position:0% code then there are the optimized 00:00:44.040 --> 00:00:48.650 align:start position:0% code then there are the optimized versions<00:00:45.530> but<00:00:46.610> so<00:00:47.610> I<00:00:47.940> was<00:00:48.270> asked<00:00:48.420> to<00:00:48.510> talk 00:00:48.650 --> 00:00:48.660 align:start position:0% versions but so I was asked to talk 00:00:48.660 --> 00:00:51.799 align:start position:0% versions but so I was asked to talk about<00:00:48.719> web<00:00:48.989> assembly<00:00:49.350> engines<00:00:50.600> but<00:00:51.600> I<00:00:51.629> just 00:00:51.799 --> 00:00:51.809 align:start position:0% about web assembly engines but I just 00:00:51.809 --> 00:00:53.240 align:start position:0% about web assembly engines but I just want<00:00:51.989> to<00:00:52.079> talk<00:00:52.199> about<00:00:52.350> what<00:00:52.559> web<00:00:52.710> assembly<00:00:53.100> is 00:00:53.240 --> 00:00:53.250 align:start position:0% want to talk about what web assembly is 00:00:53.250 --> 00:00:55.790 align:start position:0% want to talk about what web assembly is in<00:00:53.550> general<00:00:53.870> so<00:00:54.870> there's<00:00:55.020> 150<00:00:55.620> page 00:00:55.790 --> 00:00:55.800 align:start position:0% in general so there's 150 page 00:00:55.800 --> 00:01:00.770 align:start position:0% in general so there's 150 page specification<00:00:56.640> and<00:00:58.609> it<00:00:59.609> specifies<00:01:00.239> a<00:01:00.270> syntax 00:01:00.770 --> 00:01:00.780 align:start position:0% specification and it specifies a syntax 00:01:00.780 --> 00:01:02.479 align:start position:0% specification and it specifies a syntax of<00:01:01.079> the<00:01:01.260> language<00:01:01.289> sort<00:01:01.800> of<00:01:01.890> grammar<00:01:02.100> so<00:01:02.370> how 00:01:02.479 --> 00:01:02.489 align:start position:0% of the language sort of grammar so how 00:01:02.489 --> 00:01:05.329 align:start position:0% of the language sort of grammar so how to<00:01:02.550> construct<00:01:03.090> programs<00:01:03.799> and<00:01:04.799> on<00:01:04.890> top<00:01:05.100> of<00:01:05.189> this 00:01:05.329 --> 00:01:05.339 align:start position:0% to construct programs and on top of this 00:01:05.339 --> 00:01:06.830 align:start position:0% to construct programs and on top of this definition<00:01:05.700> of<00:01:05.909> the<00:01:06.060> syntax<00:01:06.420> they<00:01:06.540> define<00:01:06.810> a 00:01:06.830 --> 00:01:06.840 align:start position:0% definition of the syntax they define a 00:01:06.840 --> 00:01:09.740 align:start position:0% definition of the syntax they define a validity<00:01:07.140> which<00:01:08.070> says<00:01:08.280> you're<00:01:09.270> guaranteed<00:01:09.720> to 00:01:09.740 --> 00:01:09.750 align:start position:0% validity which says you're guaranteed to 00:01:09.750 --> 00:01:12.050 align:start position:0% validity which says you're guaranteed to return<00:01:10.170> or<00:01:10.439> pass<00:01:10.830> some<00:01:11.070> arguments<00:01:11.580> and<00:01:11.700> it's 00:01:12.050 --> 00:01:12.060 align:start position:0% return or pass some arguments and it's 00:01:12.060 --> 00:01:13.850 align:start position:0% return or pass some arguments and it's guaranteed<00:01:12.210> to<00:01:12.540> do<00:01:12.659> certain<00:01:12.930> things<00:01:12.960> and<00:01:13.380> then 00:01:13.850 --> 00:01:13.860 align:start position:0% guaranteed to do certain things and then 00:01:13.860 --> 00:01:17.300 align:start position:0% guaranteed to do certain things and then finally<00:01:14.159> they<00:01:14.580> define<00:01:15.270> execution<00:01:16.310> execution 00:01:17.300 --> 00:01:17.310 align:start position:0% finally they define execution execution 00:01:17.310 --> 00:01:22.240 align:start position:0% finally they define execution execution is<00:01:17.610> defined<00:01:17.970> as<00:01:18.210> rewrite<00:01:18.810> rules<00:01:19.080> what<00:01:20.040> is<00:01:20.159> that 00:01:22.240 --> 00:01:22.250 align:start position:0% is defined as rewrite rules what is that 00:01:22.250 --> 00:01:25.219 align:start position:0% is defined as rewrite rules what is that okay<00:01:23.280> so<00:01:23.820> somewhere<00:01:24.330> in<00:01:24.390> some<00:01:24.750> web<00:01:24.900> assembly 00:01:25.219 --> 00:01:25.229 align:start position:0% okay so somewhere in some web assembly 00:01:25.229 --> 00:01:27.260 align:start position:0% okay so somewhere in some web assembly program<00:01:25.560> we<00:01:25.710> have<00:01:25.890> these<00:01:26.040> two<00:01:26.369> -<00:01:26.790> app<00:01:26.970> codes 00:01:27.260 --> 00:01:27.270 align:start position:0% program we have these two - app codes 00:01:27.270 --> 00:01:34.249 align:start position:0% program we have these two - app codes kant's<00:01:28.259> 0<00:01:28.770> and<00:01:29.040> call<00:01:29.220> 0<00:01:32.900> what<00:01:33.900> does<00:01:33.990> it<00:01:34.079> mean 00:01:34.249 --> 00:01:34.259 align:start position:0% kant's 0 and call 0 what does it mean 00:01:34.259 --> 00:01:36.380 align:start position:0% kant's 0 and call 0 what does it mean what<00:01:34.560> does<00:01:34.590> it<00:01:34.770> do 00:01:36.380 --> 00:01:36.390 align:start position:0% what does it do 00:01:36.390 --> 00:01:40.249 align:start position:0% what does it do imagine<00:01:37.079> 0<00:01:37.619> ok<00:01:38.189> so<00:01:38.460> first<00:01:38.729> of<00:01:38.909> all<00:01:39.259> web 00:01:40.249 --> 00:01:40.259 align:start position:0% imagine 0 ok so first of all web 00:01:40.259 --> 00:01:41.990 align:start position:0% imagine 0 ok so first of all web assembly<00:01:40.680> is<00:01:40.860> given<00:01:41.159> to<00:01:41.280> you<00:01:41.369> as<00:01:41.520> a<00:01:41.549> module 00:01:41.990 --> 00:01:42.000 align:start position:0% assembly is given to you as a module 00:01:42.000 --> 00:01:43.940 align:start position:0% assembly is given to you as a module it's<00:01:42.360> a<00:01:42.509> web<00:01:42.689> assembly<00:01:43.020> module<00:01:43.170> dot<00:01:43.560> wasman 00:01:43.940 --> 00:01:43.950 align:start position:0% it's a web assembly module dot wasman 00:01:43.950 --> 00:01:46.760 align:start position:0% it's a web assembly module dot wasman file<00:01:44.159> it's<00:01:45.060> a<00:01:45.149> set<00:01:45.299> of<00:01:45.390> functions<00:01:45.840> it's<00:01:46.439> a 00:01:46.760 --> 00:01:46.770 align:start position:0% file it's a set of functions it's a 00:01:46.770 --> 00:01:50.660 align:start position:0% file it's a set of functions it's a that's<00:01:47.280> a<00:01:47.549> memory<00:01:48.000> it's<00:01:49.040> some<00:01:50.040> abstraction 00:01:50.660 --> 00:01:50.670 align:start position:0% that's a memory it's some abstraction 00:01:50.670 --> 00:01:51.800 align:start position:0% that's a memory it's some abstraction that<00:01:50.880> lets<00:01:51.000> you<00:01:51.090> do<00:01:51.180> function<00:01:51.509> pointers 00:01:51.800 --> 00:01:51.810 align:start position:0% that lets you do function pointers 00:01:51.810 --> 00:01:53.510 align:start position:0% that lets you do function pointers that's<00:01:51.960> called<00:01:52.140> a<00:01:52.170> table<00:01:52.500> some<00:01:53.159> things<00:01:53.340> to 00:01:53.510 --> 00:01:53.520 align:start position:0% that's called a table some things to 00:01:53.520 --> 00:01:55.219 align:start position:0% that's called a table some things to initialize<00:01:54.119> these<00:01:54.360> tables<00:01:54.960> in<00:01:55.110> these 00:01:55.219 --> 00:01:55.229 align:start position:0% initialize these tables in these 00:01:55.229 --> 00:01:57.709 align:start position:0% initialize these tables in these memories<00:01:55.649> things<00:01:56.490> to<00:01:56.700> import<00:01:57.060> an<00:01:57.119> export<00:01:57.570> and 00:01:57.709 --> 00:01:57.719 align:start position:0% memories things to import an export and 00:01:57.719 --> 00:01:59.300 align:start position:0% memories things to import an export and you<00:01:57.780> have<00:01:57.899> this<00:01:57.990> module<00:01:58.350> which<00:01:58.439> is<00:01:58.560> a<00:01:58.590> set<00:01:59.219> of 00:01:59.300 --> 00:01:59.310 align:start position:0% you have this module which is a set of 00:01:59.310 --> 00:02:01.280 align:start position:0% you have this module which is a set of functions<00:01:59.460> so<00:01:59.850> it<00:01:59.939> Maps<00:02:00.060> well<00:02:00.329> to<00:02:00.630> an<00:02:00.869> an 00:02:01.280 --> 00:02:01.290 align:start position:0% functions so it Maps well to an an 00:02:01.290 --> 00:02:03.950 align:start position:0% functions so it Maps well to an an ethereal<00:02:01.770> account<00:02:02.040> which<00:02:02.130> is<00:02:02.250> also<00:02:02.960> account 00:02:03.950 --> 00:02:03.960 align:start position:0% ethereal account which is also account 00:02:03.960 --> 00:02:05.859 align:start position:0% ethereal account which is also account code<00:02:04.140> which<00:02:04.290> is<00:02:04.380> also<00:02:04.710> a<00:02:04.740> set<00:02:04.920> of<00:02:05.009> functions 00:02:05.859 --> 00:02:05.869 align:start position:0% code which is also a set of functions 00:02:05.869 --> 00:02:08.510 align:start position:0% code which is also a set of functions and<00:02:06.869> you<00:02:07.469> can<00:02:07.590> call<00:02:07.799> you<00:02:07.920> have<00:02:08.009> imports<00:02:08.429> and 00:02:08.510 --> 00:02:08.520 align:start position:0% and you can call you have imports and 00:02:08.520 --> 00:02:10.029 align:start position:0% and you can call you have imports and exports<00:02:08.610> so<00:02:09.090> different<00:02:09.360> modules<00:02:09.660> can<00:02:09.750> call 00:02:10.029 --> 00:02:10.039 align:start position:0% exports so different modules can call 00:02:10.039 --> 00:02:13.010 align:start position:0% exports so different modules can call between<00:02:11.039> each<00:02:11.160> other<00:02:11.310> but<00:02:11.970> somewhere<00:02:12.330> in<00:02:12.450> one 00:02:13.010 --> 00:02:13.020 align:start position:0% between each other but somewhere in one 00:02:13.020 --> 00:02:13.550 align:start position:0% between each other but somewhere in one of<00:02:13.110> the<00:02:13.200> module 00:02:13.550 --> 00:02:13.560 align:start position:0% of the module 00:02:13.560 --> 00:02:14.870 align:start position:0% of the module and<00:02:13.770> one<00:02:13.860> of<00:02:13.890> the<00:02:14.010> functions<00:02:14.400> we<00:02:14.489> see<00:02:14.730> this 00:02:14.870 --> 00:02:14.880 align:start position:0% and one of the functions we see this 00:02:14.880 --> 00:02:18.470 align:start position:0% and one of the functions we see this what<00:02:15.330> is<00:02:15.420> it<00:02:15.450> what<00:02:16.050> does<00:02:16.110> it<00:02:16.170> mean 00:02:18.470 --> 00:02:18.480 align:start position:0% 00:02:18.480 --> 00:02:24.770 align:start position:0% so<00:02:18.920> Const<00:02:20.840> 32-bit<00:02:21.840> Const<00:02:22.230> and<00:02:22.410> call<00:02:22.890> zero<00:02:23.780> call 00:02:24.770 --> 00:02:24.780 align:start position:0% so Const 32-bit Const and call zero call 00:02:24.780 --> 00:02:28.490 align:start position:0% so Const 32-bit Const and call zero call zero<00:02:25.110> means<00:02:25.680> call<00:02:26.310> a<00:02:26.340> function<00:02:27.030> the<00:02:27.810> function 00:02:28.490 --> 00:02:28.500 align:start position:0% zero means call a function the function 00:02:28.500 --> 00:02:30.530 align:start position:0% zero means call a function the function in<00:02:28.860> this<00:02:29.010> module<00:02:29.459> which<00:02:29.640> has<00:02:29.790> index<00:02:30.120> 0<00:02:30.330> so 00:02:30.530 --> 00:02:30.540 align:start position:0% in this module which has index 0 so 00:02:30.540 --> 00:02:32.270 align:start position:0% in this module which has index 0 so imagine<00:02:30.900> that's<00:02:31.080> the<00:02:31.410> function<00:02:32.010> that<00:02:32.130> has 00:02:32.270 --> 00:02:32.280 align:start position:0% imagine that's the function that has 00:02:32.280 --> 00:02:33.620 align:start position:0% imagine that's the function that has index<00:02:32.580> 0<00:02:32.760> that's<00:02:32.910> what<00:02:33.060> assembly<00:02:33.420> code<00:02:33.540> you 00:02:33.620 --> 00:02:33.630 align:start position:0% index 0 that's what assembly code you 00:02:33.630 --> 00:02:34.940 align:start position:0% index 0 that's what assembly code you don't<00:02:33.660> have<00:02:33.900> to<00:02:33.989> know<00:02:34.080> what<00:02:34.200> it<00:02:34.290> means<00:02:34.470> but 00:02:34.940 --> 00:02:34.950 align:start position:0% don't have to know what it means but 00:02:34.950 --> 00:02:37.009 align:start position:0% don't have to know what it means but it's<00:02:35.130> some<00:02:35.310> chunk<00:02:35.910> of<00:02:36.060> whatever<00:02:36.390> that<00:02:36.900> you<00:02:36.989> can 00:02:37.009 --> 00:02:37.019 align:start position:0% it's some chunk of whatever that you can 00:02:37.019 --> 00:02:39.830 align:start position:0% it's some chunk of whatever that you can execute<00:02:37.489> when<00:02:38.489> you<00:02:38.580> see<00:02:38.760> this<00:02:38.910> code<00:02:39.510> somewhere 00:02:39.830 --> 00:02:39.840 align:start position:0% execute when you see this code somewhere 00:02:39.840 --> 00:02:43.790 align:start position:0% execute when you see this code somewhere else<00:02:40.050> in<00:02:40.200> that<00:02:40.230> module<00:02:40.500> so<00:02:42.080> this<00:02:43.080> is<00:02:43.170> how<00:02:43.290> a<00:02:43.560> web 00:02:43.790 --> 00:02:43.800 align:start position:0% else in that module so this is how a web 00:02:43.800 --> 00:02:45.770 align:start position:0% else in that module so this is how a web assembly<00:02:44.130> program<00:02:44.430> executes<00:02:44.910> we<00:02:45.420> see<00:02:45.600> this 00:02:45.770 --> 00:02:45.780 align:start position:0% assembly program executes we see this 00:02:45.780 --> 00:02:48.770 align:start position:0% assembly program executes we see this these<00:02:45.989> two<00:02:46.170> app<00:02:46.319> codes<00:02:46.590> and<00:02:47.330> then<00:02:48.330> we<00:02:48.480> execute 00:02:48.770 --> 00:02:48.780 align:start position:0% these two app codes and then we execute 00:02:48.780 --> 00:02:52.070 align:start position:0% these two app codes and then we execute these<00:02:48.989> app<00:02:49.200> codes<00:02:49.850> by<00:02:50.850> rewriting<00:02:51.269> wherever<00:02:51.870> we 00:02:52.070 --> 00:02:52.080 align:start position:0% these app codes by rewriting wherever we 00:02:52.080 --> 00:02:53.840 align:start position:0% these app codes by rewriting wherever we see<00:02:52.260> this<00:02:52.470> we<00:02:52.739> replace<00:02:53.100> it<00:02:53.280> with<00:02:53.400> that<00:02:53.519> chunk 00:02:53.840 --> 00:02:53.850 align:start position:0% see this we replace it with that chunk 00:02:53.850 --> 00:02:56.690 align:start position:0% see this we replace it with that chunk so<00:02:54.480> what<00:02:54.870> is<00:02:54.959> this<00:02:55.110> chunk<00:02:55.440> we<00:02:56.130> take<00:02:56.370> everything 00:02:56.690 --> 00:02:56.700 align:start position:0% so what is this chunk we take everything 00:02:56.700 --> 00:02:59.059 align:start position:0% so what is this chunk we take everything in<00:02:56.940> this<00:02:57.060> function<00:02:57.540> loop<00:02:58.019> to<00:02:58.230> get<00:02:58.380> local<00:02:58.590> we 00:02:59.059 --> 00:02:59.069 align:start position:0% in this function loop to get local we 00:02:59.069 --> 00:03:01.880 align:start position:0% in this function loop to get local we copy<00:02:59.310> it<00:02:59.489> we<00:02:59.670> paste<00:02:59.910> it<00:03:00.060> here<00:03:00.500> we've<00:03:01.500> used 00:03:01.880 --> 00:03:01.890 align:start position:0% copy it we paste it here we've used 00:03:01.890 --> 00:03:03.199 align:start position:0% copy it we paste it here we've used something<00:03:02.099> called<00:03:02.220> the<00:03:02.519> frame<00:03:02.700> this<00:03:02.849> is<00:03:02.970> just 00:03:03.199 --> 00:03:03.209 align:start position:0% something called the frame this is just 00:03:03.209 --> 00:03:04.370 align:start position:0% something called the frame this is just what<00:03:03.360> it<00:03:03.450> says<00:03:03.569> in<00:03:03.720> the<00:03:03.810> spec<00:03:04.049> I'm<00:03:04.170> just 00:03:04.370 --> 00:03:04.380 align:start position:0% what it says in the spec I'm just 00:03:04.380 --> 00:03:05.960 align:start position:0% what it says in the spec I'm just mechanically<00:03:05.069> doing<00:03:05.310> what<00:03:05.459> they<00:03:05.549> tell<00:03:05.760> what 00:03:05.960 --> 00:03:05.970 align:start position:0% mechanically doing what they tell what 00:03:05.970 --> 00:03:08.660 align:start position:0% mechanically doing what they tell what they<00:03:06.090> say<00:03:06.269> in<00:03:06.360> the<00:03:06.450> spec<00:03:06.690> to<00:03:06.810> do<00:03:06.959> it<00:03:07.799> says<00:03:08.069> well 00:03:08.660 --> 00:03:08.670 align:start position:0% they say in the spec to do it says well 00:03:08.670 --> 00:03:10.280 align:start position:0% they say in the spec to do it says well then<00:03:08.760> we<00:03:08.880> have<00:03:09.030> in<00:03:09.150> these<00:03:09.269> brackets<00:03:09.750> we<00:03:10.110> say 00:03:10.280 --> 00:03:10.290 align:start position:0% then we have in these brackets we say 00:03:10.290 --> 00:03:13.100 align:start position:0% then we have in these brackets we say locals<00:03:10.739> there's<00:03:11.580> a<00:03:11.670> parameter<00:03:11.940> it<00:03:12.690> takes<00:03:12.959> that 00:03:13.100 --> 00:03:13.110 align:start position:0% locals there's a parameter it takes that 00:03:13.110 --> 00:03:15.110 align:start position:0% locals there's a parameter it takes that constant<00:03:13.620> zero<00:03:13.830> we<00:03:13.980> copy<00:03:14.220> and<00:03:14.340> paste<00:03:14.610> it<00:03:14.790> here 00:03:15.110 --> 00:03:15.120 align:start position:0% constant zero we copy and paste it here 00:03:15.120 --> 00:03:17.240 align:start position:0% constant zero we copy and paste it here then<00:03:15.870> we<00:03:16.049> wrap<00:03:16.260> all<00:03:16.530> of<00:03:16.590> this<00:03:16.860> code<00:03:17.130> in 00:03:17.240 --> 00:03:17.250 align:start position:0% then we wrap all of this code in 00:03:17.250 --> 00:03:19.190 align:start position:0% then we wrap all of this code in something<00:03:17.549> called<00:03:17.670> the<00:03:17.790> block<00:03:18.030> that's<00:03:18.989> just 00:03:19.190 --> 00:03:19.200 align:start position:0% something called the block that's just 00:03:19.200 --> 00:03:20.479 align:start position:0% something called the block that's just what<00:03:19.350> it<00:03:19.440> says<00:03:19.590> to<00:03:19.769> do<00:03:19.890> so<00:03:20.100> that's<00:03:20.250> what<00:03:20.400> I'm 00:03:20.479 --> 00:03:20.489 align:start position:0% what it says to do so that's what I'm 00:03:20.489 --> 00:03:23.030 align:start position:0% what it says to do so that's what I'm doing<00:03:20.700> I'm<00:03:20.760> just<00:03:20.820> rewriting<00:03:21.150> that<00:03:22.040> I'm 00:03:23.030 --> 00:03:23.040 align:start position:0% doing I'm just rewriting that I'm 00:03:23.040 --> 00:03:25.009 align:start position:0% doing I'm just rewriting that I'm deleting<00:03:24.000> it<00:03:24.090> and<00:03:24.209> I'm<00:03:24.329> replacing<00:03:24.600> it<00:03:24.900> with 00:03:25.009 --> 00:03:25.019 align:start position:0% deleting it and I'm replacing it with 00:03:25.019 --> 00:03:31.250 align:start position:0% deleting it and I'm replacing it with that<00:03:25.700> then<00:03:26.700> what<00:03:26.880> happens<00:03:29.720> then<00:03:30.720> we<00:03:30.900> we 00:03:31.250 --> 00:03:31.260 align:start position:0% that then what happens then we we 00:03:31.260 --> 00:03:33.620 align:start position:0% that then what happens then we we rewrite<00:03:31.620> the<00:03:32.100> thing<00:03:32.579> that<00:03:32.700> says<00:03:32.880> block<00:03:33.150> with 00:03:33.620 --> 00:03:33.630 align:start position:0% rewrite the thing that says block with 00:03:33.630 --> 00:03:35.720 align:start position:0% rewrite the thing that says block with this<00:03:33.810> I<00:03:34.109> just<00:03:34.650> read<00:03:34.829> the<00:03:34.950> specification<00:03:35.640> I'm 00:03:35.720 --> 00:03:35.730 align:start position:0% this I just read the specification I'm 00:03:35.730 --> 00:03:38.599 align:start position:0% this I just read the specification I'm just<00:03:35.910> doing<00:03:36.120> what<00:03:36.269> it<00:03:36.299> told<00:03:36.510> me<00:03:36.660> to<00:03:36.780> do<00:03:37.609> then 00:03:38.599 --> 00:03:38.609 align:start position:0% just doing what it told me to do then 00:03:38.609 --> 00:03:44.990 align:start position:0% just doing what it told me to do then once<00:03:38.819> I<00:03:42.170> rewrite<00:03:43.170> where<00:03:43.350> it<00:03:43.440> says<00:03:43.650> loop<00:03:43.889> and<00:03:44.190> I 00:03:44.990 --> 00:03:45.000 align:start position:0% once I rewrite where it says loop and I 00:03:45.000 --> 00:03:48.170 align:start position:0% once I rewrite where it says loop and I punch<00:03:45.900> and<00:03:46.170> I<00:03:46.230> put<00:03:46.530> in<00:03:46.620> labels<00:03:47.040> 0<00:03:47.579> and<00:03:47.940> then<00:03:48.090> I 00:03:48.170 --> 00:03:48.180 align:start position:0% punch and I put in labels 0 and then I 00:03:48.180 --> 00:03:50.300 align:start position:0% punch and I put in labels 0 and then I copy<00:03:48.450> and<00:03:48.630> paste<00:03:48.900> all<00:03:49.109> of<00:03:49.230> this<00:03:49.380> this<00:03:49.859> text 00:03:50.300 --> 00:03:50.310 align:start position:0% copy and paste all of this this text 00:03:50.310 --> 00:03:52.670 align:start position:0% copy and paste all of this this text including<00:03:50.730> the<00:03:50.819> loop<00:03:50.970> parts<00:03:51.420> into<00:03:52.200> here<00:03:52.470> I 00:03:52.670 --> 00:03:52.680 align:start position:0% including the loop parts into here I 00:03:52.680 --> 00:03:54.879 align:start position:0% including the loop parts into here I wrote<00:03:53.130> it<00:03:53.250> in<00:03:53.340> small<00:03:53.609> text<00:03:53.940> so<00:03:54.030> it<00:03:54.150> could<00:03:54.269> fit 00:03:54.879 --> 00:03:54.889 align:start position:0% wrote it in small text so it could fit 00:03:54.889 --> 00:04:00.520 align:start position:0% wrote it in small text so it could fit what<00:03:55.889> happens<00:03:56.220> next 00:04:00.520 --> 00:04:00.530 align:start position:0% 00:04:00.530 --> 00:04:03.349 align:start position:0% this<00:04:01.530> get<00:04:01.769> local<00:04:02.160> so<00:04:02.489> we're<00:04:02.940> sort<00:04:03.120> of<00:04:03.209> going 00:04:03.349 --> 00:04:03.359 align:start position:0% this get local so we're sort of going 00:04:03.359 --> 00:04:06.199 align:start position:0% this get local so we're sort of going going<00:04:04.079> along<00:04:04.380> we<00:04:04.620> we<00:04:05.040> saw<00:04:05.220> a<00:04:05.250> black<00:04:05.549> we<00:04:05.790> saw<00:04:05.970> a 00:04:06.199 --> 00:04:06.209 align:start position:0% going along we we saw a black we saw a 00:04:06.209 --> 00:04:08.090 align:start position:0% going along we we saw a black we saw a loop<00:04:06.480> then<00:04:06.840> we<00:04:06.870> see<00:04:07.170> a<00:04:07.200> get<00:04:07.410> local<00:04:07.799> app<00:04:07.889> code 00:04:08.090 --> 00:04:08.100 align:start position:0% loop then we see a get local app code 00:04:08.100 --> 00:04:09.410 align:start position:0% loop then we see a get local app code what<00:04:08.280> does<00:04:08.370> that<00:04:08.400> mean<00:04:08.670> what<00:04:08.850> does<00:04:08.940> it<00:04:09.060> do<00:04:09.180> it 00:04:09.410 --> 00:04:09.420 align:start position:0% what does that mean what does it do it 00:04:09.420 --> 00:04:12.080 align:start position:0% what does that mean what does it do it says<00:04:09.690> to<00:04:09.810> take<00:04:10.019> that<00:04:10.290> counts<00:04:11.040> zero<00:04:11.310> that's<00:04:11.940> the 00:04:12.080 --> 00:04:12.090 align:start position:0% says to take that counts zero that's the 00:04:12.090 --> 00:04:14.059 align:start position:0% says to take that counts zero that's the first<00:04:12.299> local<00:04:12.630> there<00:04:12.750> could<00:04:12.900> be<00:04:12.930> more<00:04:13.170> and<00:04:13.410> copy 00:04:14.059 --> 00:04:14.069 align:start position:0% first local there could be more and copy 00:04:14.069 --> 00:04:14.870 align:start position:0% first local there could be more and copy and<00:04:14.280> paste<00:04:14.489> it 00:04:14.870 --> 00:04:14.880 align:start position:0% and paste it 00:04:14.880 --> 00:04:17.150 align:start position:0% and paste it delete<00:04:15.660> where<00:04:15.840> it<00:04:15.900> says<00:04:16.049> get<00:04:16.169> local<00:04:16.530> and<00:04:16.709> paste 00:04:17.150 --> 00:04:17.160 align:start position:0% delete where it says get local and paste 00:04:17.160 --> 00:04:21.409 align:start position:0% delete where it says get local and paste into<00:04:17.400> it<00:04:17.720> where<00:04:18.720> it<00:04:18.810> was<00:04:18.959> I<00:04:19.289> 32<00:04:19.950> can<00:04:20.220> 0<00:04:20.519> then 00:04:21.409 --> 00:04:21.419 align:start position:0% into it where it was I 32 can 0 then 00:04:21.419 --> 00:04:24.020 align:start position:0% into it where it was I 32 can 0 then what<00:04:21.800> so<00:04:22.800> we're<00:04:22.919> sort<00:04:23.070> of<00:04:23.130> going<00:04:23.280> along<00:04:23.520> and 00:04:24.020 --> 00:04:24.030 align:start position:0% what so we're sort of going along and 00:04:24.030 --> 00:04:26.120 align:start position:0% what so we're sort of going along and then<00:04:24.630> we<00:04:24.720> see<00:04:24.870> these<00:04:25.289> three<00:04:25.500> app<00:04:25.680> codes<00:04:25.979> what 00:04:26.120 --> 00:04:26.130 align:start position:0% then we see these three app codes what 00:04:26.130 --> 00:04:27.470 align:start position:0% then we see these three app codes what do<00:04:26.190> we<00:04:26.250> do<00:04:26.430> with<00:04:26.520> these<00:04:26.700> three<00:04:26.849> app<00:04:27.000> codes 00:04:27.470 --> 00:04:27.480 align:start position:0% do we do with these three app codes 00:04:27.480 --> 00:04:30.440 align:start position:0% do we do with these three app codes to<00:04:27.600> rewrite<00:04:27.930> rule<00:04:28.110> again<00:04:28.910> we<00:04:29.910> replace<00:04:30.270> these 00:04:30.440 --> 00:04:30.450 align:start position:0% to rewrite rule again we replace these 00:04:30.450 --> 00:04:33.020 align:start position:0% to rewrite rule again we replace these three<00:04:30.720> app<00:04:30.840> codes<00:04:31.140> with<00:04:31.590> the<00:04:31.710> sum<00:04:31.950> the<00:04:32.610> ad<00:04:32.760> with 00:04:33.020 --> 00:04:33.030 align:start position:0% three app codes with the sum the ad with 00:04:33.030 --> 00:04:35.330 align:start position:0% three app codes with the sum the ad with the<00:04:33.150> sum<00:04:33.360> of<00:04:33.390> the<00:04:33.630> two<00:04:33.810> so<00:04:34.410> we<00:04:34.470> replace<00:04:35.100> it<00:04:35.130> with 00:04:35.330 --> 00:04:35.340 align:start position:0% the sum of the two so we replace it with 00:04:35.340 --> 00:04:38.720 align:start position:0% the sum of the two so we replace it with a<00:04:35.370> count<00:04:35.640> one<00:04:35.910> as<00:04:36.860> you<00:04:37.860> see<00:04:38.040> it's<00:04:38.160> just<00:04:38.220> rewrite 00:04:38.720 --> 00:04:38.730 align:start position:0% a count one as you see it's just rewrite 00:04:38.730 --> 00:04:40.430 align:start position:0% a count one as you see it's just rewrite rules<00:04:38.970> the<00:04:39.510> whole<00:04:39.630> semantics<00:04:40.200> the<00:04:40.350> whole 00:04:40.430 --> 00:04:40.440 align:start position:0% rules the whole semantics the whole 00:04:40.440 --> 00:04:41.720 align:start position:0% rules the whole semantics the whole execution<00:04:40.680> semantics<00:04:41.340> is<00:04:41.460> we're<00:04:41.580> just 00:04:41.720 --> 00:04:41.730 align:start position:0% execution semantics is we're just 00:04:41.730 --> 00:04:43.040 align:start position:0% execution semantics is we're just rewriting<00:04:42.060> chunks<00:04:42.480> we're<00:04:42.630> capping<00:04:42.930> and 00:04:43.040 --> 00:04:43.050 align:start position:0% rewriting chunks we're capping and 00:04:43.050 --> 00:04:50.930 align:start position:0% rewriting chunks we're capping and pasting<00:04:43.440> text<00:04:43.880> what's<00:04:44.880> next<00:04:47.840> we<00:04:48.840> have<00:04:49.050> a<00:04:49.940> T 00:04:50.930 --> 00:04:50.940 align:start position:0% pasting text what's next we have a T 00:04:50.940 --> 00:04:52.820 align:start position:0% pasting text what's next we have a T local<00:04:51.360> which<00:04:51.570> means<00:04:51.840> we<00:04:52.050> take<00:04:52.290> whatever<00:04:52.620> is 00:04:52.820 --> 00:04:52.830 align:start position:0% local which means we take whatever is 00:04:52.830 --> 00:04:55.640 align:start position:0% local which means we take whatever is above<00:04:53.040> it<00:04:53.250> put<00:04:53.790> it<00:04:53.910> into<00:04:54.210> the<00:04:54.360> local<00:04:54.870> cons<00:04:55.380> and 00:04:55.640 --> 00:04:55.650 align:start position:0% above it put it into the local cons and 00:04:55.650 --> 00:04:58.130 align:start position:0% above it put it into the local cons and then<00:04:55.800> we<00:04:55.920> also<00:04:56.400> paste<00:04:56.820> it<00:04:57.000> here<00:04:57.030> and<00:04:57.510> we<00:04:57.870> delete 00:04:58.130 --> 00:04:58.140 align:start position:0% then we also paste it here and we delete 00:04:58.140 --> 00:04:59.870 align:start position:0% then we also paste it here and we delete where<00:04:58.320> it<00:04:58.410> says<00:04:58.560> T<00:04:58.740> local<00:04:59.100> I'm<00:04:59.340> just<00:04:59.700> rewriting 00:04:59.870 --> 00:04:59.880 align:start position:0% where it says T local I'm just rewriting 00:04:59.880 --> 00:05:00.980 align:start position:0% where it says T local I'm just rewriting stuff<00:05:00.330> I'm<00:05:00.480> not<00:05:00.600> doing<00:05:00.810> anything 00:05:00.980 --> 00:05:00.990 align:start position:0% stuff I'm not doing anything 00:05:00.990 --> 00:05:02.600 align:start position:0% stuff I'm not doing anything controversial<00:05:01.560> it's<00:05:01.830> just<00:05:01.980> what<00:05:02.130> the<00:05:02.220> spec 00:05:02.600 --> 00:05:02.610 align:start position:0% controversial it's just what the spec 00:05:02.610 --> 00:05:06.950 align:start position:0% controversial it's just what the spec told<00:05:02.850> me<00:05:02.970> to<00:05:03.060> do<00:05:05.090> then<00:05:06.090> I'm<00:05:06.210> doing<00:05:06.450> a<00:05:06.600> less<00:05:06.750> than 00:05:06.950 --> 00:05:06.960 align:start position:0% told me to do then I'm doing a less than 00:05:06.960 --> 00:05:09.110 align:start position:0% told me to do then I'm doing a less than unsigned<00:05:07.590> operation<00:05:08.250> and<00:05:08.520> replacing<00:05:09.000> it<00:05:09.060> with 00:05:09.110 --> 00:05:09.120 align:start position:0% unsigned operation and replacing it with 00:05:09.120 --> 00:05:11.740 align:start position:0% unsigned operation and replacing it with the<00:05:09.270> 1<00:05:09.420> because<00:05:09.570> 1<00:05:09.870> is<00:05:10.050> in<00:05:10.170> fact<00:05:10.410> less<00:05:10.590> than<00:05:10.770> 3 00:05:11.740 --> 00:05:11.750 align:start position:0% the 1 because 1 is in fact less than 3 00:05:11.750 --> 00:05:14.600 align:start position:0% the 1 because 1 is in fact less than 3 so<00:05:12.750> anyway<00:05:13.080> this<00:05:13.830> just<00:05:14.070> keeps<00:05:14.250> going<00:05:14.520> and 00:05:14.600 --> 00:05:14.610 align:start position:0% so anyway this just keeps going and 00:05:14.610 --> 00:05:17.390 align:start position:0% so anyway this just keeps going and going<00:05:14.700> and<00:05:15.180> finally<00:05:16.140> I<00:05:16.170> get<00:05:16.380> to<00:05:16.410> this<00:05:16.650> and<00:05:17.310> this 00:05:17.390 --> 00:05:17.400 align:start position:0% going and finally I get to this and this 00:05:17.400 --> 00:05:19.550 align:start position:0% going and finally I get to this and this is<00:05:17.550> my<00:05:17.640> last<00:05:17.850> slide<00:05:18.000> for<00:05:18.120> the<00:05:18.510> Oise<00:05:19.110> imagines 00:05:19.550 --> 00:05:19.560 align:start position:0% is my last slide for the Oise imagines 00:05:19.560 --> 00:05:21.350 align:start position:0% is my last slide for the Oise imagines talk<00:05:19.800> so<00:05:20.430> what's<00:05:20.580> the<00:05:20.730> point<00:05:20.880> why<00:05:21.060> did<00:05:21.210> I<00:05:21.300> just 00:05:21.350 --> 00:05:21.360 align:start position:0% talk so what's the point why did I just 00:05:21.360 --> 00:05:23.360 align:start position:0% talk so what's the point why did I just waste<00:05:21.810> your<00:05:21.930> time<00:05:22.200> with<00:05:22.800> this<00:05:23.070> sort<00:05:23.310> of 00:05:23.360 --> 00:05:23.370 align:start position:0% waste your time with this sort of 00:05:23.370 --> 00:05:28.150 align:start position:0% waste your time with this sort of rewrite<00:05:23.640> rule<00:05:23.850> stuff<00:05:24.410> I<00:05:25.410> went<00:05:26.250> from<00:05:26.720> this 00:05:28.150 --> 00:05:28.160 align:start position:0% rewrite rule stuff I went from this 00:05:28.160 --> 00:05:33.950 align:start position:0% rewrite rule stuff I went from this somewhere<00:05:29.160> in<00:05:29.870> my<00:05:31.670> code<00:05:32.670> and<00:05:32.940> I<00:05:33.330> and<00:05:33.690> I<00:05:33.750> just 00:05:33.950 --> 00:05:33.960 align:start position:0% somewhere in my code and I and I just 00:05:33.960 --> 00:05:36.140 align:start position:0% somewhere in my code and I and I just rewrote<00:05:34.380> it<00:05:34.770> a<00:05:34.890> bunch<00:05:35.040> of<00:05:35.160> times<00:05:35.220> all<00:05:35.850> the<00:05:36.060> way 00:05:36.140 --> 00:05:36.150 align:start position:0% rewrote it a bunch of times all the way 00:05:36.150 --> 00:05:38.930 align:start position:0% rewrote it a bunch of times all the way down<00:05:36.600> to<00:05:36.870> this<00:05:37.100> and<00:05:38.100> that's<00:05:38.250> how<00:05:38.370> we<00:05:38.430> executed 00:05:38.930 --> 00:05:38.940 align:start position:0% down to this and that's how we executed 00:05:38.940 --> 00:05:42.200 align:start position:0% down to this and that's how we executed web<00:05:39.090> assembly<00:05:39.570> these<00:05:40.530> rewrite<00:05:40.950> rules<00:05:41.220> so 00:05:42.200 --> 00:05:42.210 align:start position:0% web assembly these rewrite rules so 00:05:42.210 --> 00:05:44.960 align:start position:0% web assembly these rewrite rules so what's<00:05:42.360> the<00:05:42.510> point<00:05:43.490> that's<00:05:44.490> how<00:05:44.640> the<00:05:44.700> spec 00:05:44.960 --> 00:05:44.970 align:start position:0% what's the point that's how the spec 00:05:44.970 --> 00:05:46.670 align:start position:0% what's the point that's how the spec defines<00:05:45.360> it<00:05:45.600> it's<00:05:45.870> just<00:05:46.110> rewrite<00:05:46.440> rules 00:05:46.670 --> 00:05:46.680 align:start position:0% defines it it's just rewrite rules 00:05:46.680 --> 00:05:48.610 align:start position:0% defines it it's just rewrite rules nobody<00:05:46.920> implements<00:05:47.490> their<00:05:47.640> engine<00:05:47.940> like<00:05:48.090> this 00:05:48.610 --> 00:05:48.620 align:start position:0% nobody implements their engine like this 00:05:48.620 --> 00:05:50.480 align:start position:0% nobody implements their engine like this people<00:05:49.620> implement<00:05:49.890> their<00:05:50.070> engines<00:05:50.340> with 00:05:50.480 --> 00:05:50.490 align:start position:0% people implement their engines with 00:05:50.490 --> 00:05:52.760 align:start position:0% people implement their engines with swift<00:05:50.880> steps<00:05:51.210> there<00:05:52.110> could<00:05:52.290> be<00:05:52.320> one<00:05:52.530> stack 00:05:52.760 --> 00:05:52.770 align:start position:0% swift steps there could be one stack 00:05:52.770 --> 00:05:53.960 align:start position:0% swift steps there could be one stack there<00:05:52.980> could<00:05:53.130> be<00:05:53.160> two<00:05:53.340> stacks<00:05:53.610> there<00:05:53.820> could<00:05:53.940> be 00:05:53.960 --> 00:05:53.970 align:start position:0% there could be two stacks there could be 00:05:53.970 --> 00:05:56.120 align:start position:0% there could be two stacks there could be three<00:05:54.240> stacks<00:05:54.510> when<00:05:55.440> I<00:05:55.470> implemented<00:05:55.890> the 00:05:56.120 --> 00:05:56.130 align:start position:0% three stacks when I implemented the 00:05:56.130 --> 00:05:57.740 align:start position:0% three stacks when I implemented the engine<00:05:56.400> I<00:05:56.460> did<00:05:56.640> it<00:05:56.730> with<00:05:56.850> three<00:05:57.060> stacks<00:05:57.360> for 00:05:57.740 --> 00:05:57.750 align:start position:0% engine I did it with three stacks for 00:05:57.750 --> 00:06:00.920 align:start position:0% engine I did it with three stacks for for<00:05:58.140> various<00:05:58.410> reasons<00:05:59.300> there's<00:06:00.300> stacks<00:06:00.570> for 00:06:00.920 --> 00:06:00.930 align:start position:0% for various reasons there's stacks for 00:06:00.930 --> 00:06:03.440 align:start position:0% for various reasons there's stacks for these<00:06:01.110> function<00:06:01.650> call<00:06:01.890> frames<00:06:02.250> there's<00:06:03.030> I 00:06:03.440 --> 00:06:03.450 align:start position:0% these function call frames there's I 00:06:03.450 --> 00:06:04.880 align:start position:0% these function call frames there's I have<00:06:03.810> a<00:06:03.870> stack<00:06:04.080> for<00:06:04.230> the<00:06:04.260> function<00:06:04.560> call 00:06:04.880 --> 00:06:04.890 align:start position:0% have a stack for the function call 00:06:04.890 --> 00:06:06.200 align:start position:0% have a stack for the function call frames<00:06:05.130> I<00:06:05.280> have<00:06:05.370> a<00:06:05.400> stack<00:06:05.580> for<00:06:05.730> the<00:06:05.760> labels<00:06:06.090> and 00:06:06.200 --> 00:06:06.210 align:start position:0% frames I have a stack for the labels and 00:06:06.210 --> 00:06:07.790 align:start position:0% frames I have a stack for the labels and I<00:06:06.270> have<00:06:06.360> a<00:06:06.420> stack<00:06:06.690> for<00:06:06.900> the<00:06:06.930> for<00:06:07.260> the<00:06:07.320> operands 00:06:07.790 --> 00:06:07.800 align:start position:0% I have a stack for the for the operands 00:06:07.800 --> 00:06:10.130 align:start position:0% I have a stack for the for the operands other<00:06:08.400> people<00:06:08.730> keep<00:06:09.150> their<00:06:09.390> frame<00:06:09.750> their 00:06:10.130 --> 00:06:10.140 align:start position:0% other people keep their frame their 00:06:10.140 --> 00:06:12.190 align:start position:0% other people keep their frame their function<00:06:11.010> call<00:06:11.160> frames<00:06:11.430> and<00:06:11.610> their<00:06:11.730> and<00:06:12.000> their 00:06:12.190 --> 00:06:12.200 align:start position:0% function call frames and their and their 00:06:12.200 --> 00:06:14.960 align:start position:0% function call frames and their and their control<00:06:13.200> flow<00:06:13.440> labels<00:06:13.860> in<00:06:14.100> the<00:06:14.490> same<00:06:14.700> stack 00:06:14.960 --> 00:06:14.970 align:start position:0% control flow labels in the same stack 00:06:14.970 --> 00:06:16.730 align:start position:0% control flow labels in the same stack there<00:06:15.540> is<00:06:15.690> advantages<00:06:16.170> to<00:06:16.290> doing<00:06:16.380> it<00:06:16.590> my<00:06:16.710> way 00:06:16.730 --> 00:06:16.740 align:start position:0% there is advantages to doing it my way 00:06:16.740 --> 00:06:18.920 align:start position:0% there is advantages to doing it my way because<00:06:17.220> if<00:06:17.970> you<00:06:18.120> keep<00:06:18.330> these<00:06:18.540> in<00:06:18.660> the<00:06:18.720> same 00:06:18.920 --> 00:06:18.930 align:start position:0% because if you keep these in the same 00:06:18.930 --> 00:06:21.770 align:start position:0% because if you keep these in the same stack<00:06:19.250> you<00:06:20.250> have<00:06:20.370> to<00:06:20.490> sort<00:06:20.730> of<00:06:20.790> every<00:06:21.480> time<00:06:21.660> you 00:06:21.770 --> 00:06:21.780 align:start position:0% stack you have to sort of every time you 00:06:21.780 --> 00:06:23.600 align:start position:0% stack you have to sort of every time you return<00:06:22.440> from<00:06:22.470> a<00:06:22.710> function<00:06:22.740> you<00:06:23.130> have<00:06:23.190> you<00:06:23.490> have 00:06:23.600 --> 00:06:23.610 align:start position:0% return from a function you have you have 00:06:23.610 --> 00:06:25.100 align:start position:0% return from a function you have you have a<00:06:23.640> linear<00:06:24.000> time<00:06:24.240> if<00:06:24.450> you're<00:06:24.570> nested<00:06:24.960> in<00:06:25.050> a 00:06:25.100 --> 00:06:25.110 align:start position:0% a linear time if you're nested in a 00:06:25.110 --> 00:06:26.780 align:start position:0% a linear time if you're nested in a bunch<00:06:25.290> of<00:06:25.380> functions<00:06:25.650> so<00:06:26.370> that<00:06:26.520> could<00:06:26.640> be<00:06:26.670> a 00:06:26.780 --> 00:06:26.790 align:start position:0% bunch of functions so that could be a 00:06:26.790 --> 00:06:28.670 align:start position:0% bunch of functions so that could be a slow<00:06:27.030> down<00:06:27.180> the<00:06:27.600> point<00:06:27.870> is<00:06:28.050> everyone 00:06:28.670 --> 00:06:28.680 align:start position:0% slow down the point is everyone 00:06:28.680 --> 00:06:30.560 align:start position:0% slow down the point is everyone implements<00:06:29.190> their<00:06:29.370> engines<00:06:29.730> however<00:06:30.420> they 00:06:30.560 --> 00:06:30.570 align:start position:0% implements their engines however they 00:06:30.570 --> 00:06:33.200 align:start position:0% implements their engines however they want<00:06:30.750> to<00:06:30.780> implement<00:06:30.990> it<00:06:31.320> and<00:06:32.000> people<00:06:33.000> do<00:06:33.090> it 00:06:33.200 --> 00:06:33.210 align:start position:0% want to implement it and people do it 00:06:33.210 --> 00:06:35.930 align:start position:0% want to implement it and people do it differently<00:06:33.600> but<00:06:34.260> they're<00:06:35.070> the<00:06:35.580> whole<00:06:35.730> goal 00:06:35.930 --> 00:06:35.940 align:start position:0% differently but they're the whole goal 00:06:35.940 --> 00:06:37.430 align:start position:0% differently but they're the whole goal is<00:06:36.090> to<00:06:36.120> make<00:06:36.390> web<00:06:36.630> apps<00:06:36.660> they<00:06:37.050> want<00:06:37.230> to<00:06:37.320> have 00:06:37.430 --> 00:06:37.440 align:start position:0% is to make web apps they want to have 00:06:37.440 --> 00:06:39.290 align:start position:0% is to make web apps they want to have like<00:06:37.620> you<00:06:37.770> know<00:06:37.800> alien<00:06:38.460> fighting<00:06:38.820> games<00:06:39.060> and 00:06:39.290 --> 00:06:39.300 align:start position:0% like you know alien fighting games and 00:06:39.300 --> 00:06:41.030 align:start position:0% like you know alien fighting games and in<00:06:39.840> their<00:06:40.020> browsers<00:06:40.440> and<00:06:40.620> things<00:06:40.740> like<00:06:40.860> that 00:06:41.030 --> 00:06:41.040 align:start position:0% in their browsers and things like that 00:06:41.040 --> 00:06:41.390 align:start position:0% in their browsers and things like that and<00:06:41.220> if 00:06:41.390 --> 00:06:41.400 align:start position:0% and if 00:06:41.400 --> 00:06:44.719 align:start position:0% and if Crash's<00:06:41.910> if<00:06:42.030> it<00:06:42.120> fails<00:06:42.419> who<00:06:42.630> cares<00:06:43.050> but<00:06:43.919> if 00:06:44.719 --> 00:06:44.729 align:start position:0% Crash's if it fails who cares but if 00:06:44.729 --> 00:06:46.070 align:start position:0% Crash's if it fails who cares but if everyone's<00:06:45.150> implementing<00:06:45.630> things<00:06:45.810> their<00:06:46.050> own 00:06:46.070 --> 00:06:46.080 align:start position:0% everyone's implementing things their own 00:06:46.080 --> 00:06:49.129 align:start position:0% everyone's implementing things their own way<00:06:47.300> then<00:06:48.300> maybe<00:06:48.479> someone's<00:06:48.810> going<00:06:48.930> to<00:06:48.990> have<00:06:49.110> a 00:06:49.129 --> 00:06:49.139 align:start position:0% way then maybe someone's going to have a 00:06:49.139 --> 00:06:50.510 align:start position:0% way then maybe someone's going to have a bug<00:06:49.380> someone's<00:06:49.770> going<00:06:49.889> to<00:06:49.919> introduce<00:06:50.280> an 00:06:50.510 --> 00:06:50.520 align:start position:0% bug someone's going to introduce an 00:06:50.520 --> 00:06:51.560 align:start position:0% bug someone's going to introduce an invariant<00:06:50.970> that<00:06:51.060> they're<00:06:51.180> gonna<00:06:51.330> ignore 00:06:51.560 --> 00:06:51.570 align:start position:0% invariant that they're gonna ignore 00:06:51.570 --> 00:06:54.260 align:start position:0% invariant that they're gonna ignore later<00:06:51.840> on<00:06:52.080> and<00:06:52.490> something's<00:06:53.490> gonna<00:06:53.580> go<00:06:54.240> wrong 00:06:54.260 --> 00:06:54.270 align:start position:0% later on and something's gonna go wrong 00:06:54.270 --> 00:06:56.300 align:start position:0% later on and something's gonna go wrong and<00:06:54.810> if<00:06:54.960> it's<00:06:55.080> a<00:06:55.139> web<00:06:55.289> app<00:06:55.470> who<00:06:55.770> cares<00:06:56.039> but<00:06:56.250> if 00:06:56.300 --> 00:06:56.310 align:start position:0% and if it's a web app who cares but if 00:06:56.310 --> 00:06:57.650 align:start position:0% and if it's a web app who cares but if it's<00:06:56.460> adapt<00:06:56.699> when<00:06:56.940> there's<00:06:57.180> a<00:06:57.240> lot<00:06:57.360> of<00:06:57.479> money 00:06:57.650 --> 00:06:57.660 align:start position:0% it's adapt when there's a lot of money 00:06:57.660 --> 00:06:59.840 align:start position:0% it's adapt when there's a lot of money on<00:06:58.169> the<00:06:58.350> line<00:06:58.380> then<00:06:58.830> we<00:06:59.280> might<00:06:59.400> have<00:06:59.610> problems 00:06:59.840 --> 00:06:59.850 align:start position:0% on the line then we might have problems 00:06:59.850 --> 00:07:02.270 align:start position:0% on the line then we might have problems so<00:07:00.180> I<00:07:00.210> think<00:07:00.330> we<00:07:00.690> have<00:07:00.840> to<00:07:01.020> focus<00:07:01.350> and<00:07:01.889> spend<00:07:02.220> a 00:07:02.270 --> 00:07:02.280 align:start position:0% so I think we have to focus and spend a 00:07:02.280 --> 00:07:04.580 align:start position:0% so I think we have to focus and spend a lot<00:07:02.430> of<00:07:02.460> time<00:07:02.699> making<00:07:03.389> sure<00:07:03.539> we<00:07:04.020> implement<00:07:04.139> it 00:07:04.580 --> 00:07:04.590 align:start position:0% lot of time making sure we implement it 00:07:04.590 --> 00:07:07.400 align:start position:0% lot of time making sure we implement it right<00:07:04.620> to<00:07:04.919> audit<00:07:05.039> these<00:07:05.310> engines<00:07:05.960> these<00:07:06.960> you 00:07:07.400 --> 00:07:07.410 align:start position:0% right to audit these engines these you 00:07:07.410 --> 00:07:09.140 align:start position:0% right to audit these engines these you know<00:07:07.500> we<00:07:07.680> talk<00:07:08.070> about<00:07:08.190> Firefox<00:07:08.699> and<00:07:08.940> chromium 00:07:09.140 --> 00:07:09.150 align:start position:0% know we talk about Firefox and chromium 00:07:09.150 --> 00:07:10.400 align:start position:0% know we talk about Firefox and chromium they<00:07:09.539> want<00:07:09.720> to<00:07:09.810> have<00:07:09.900> some<00:07:10.110> micro 00:07:10.400 --> 00:07:10.410 align:start position:0% they want to have some micro 00:07:10.410 --> 00:07:12.170 align:start position:0% they want to have some micro optimizations<00:07:10.530> for<00:07:11.220> their<00:07:11.430> benchmarks<00:07:12.000> that 00:07:12.170 --> 00:07:12.180 align:start position:0% optimizations for their benchmarks that 00:07:12.180 --> 00:07:16.370 align:start position:0% optimizations for their benchmarks that they're<00:07:12.300> interested<00:07:12.720> in<00:07:13.400> but<00:07:14.400> but<00:07:15.360> you<00:07:16.260> know 00:07:16.370 --> 00:07:16.380 align:start position:0% they're interested in but but you know 00:07:16.380 --> 00:07:17.930 align:start position:0% they're interested in but but you know we<00:07:16.500> do<00:07:17.100> we<00:07:17.190> want<00:07:17.340> these<00:07:17.520> micro<00:07:17.850> optimizations 00:07:17.930 --> 00:07:17.940 align:start position:0% we do we want these micro optimizations 00:07:17.940 --> 00:07:20.360 align:start position:0% we do we want these micro optimizations so<00:07:18.479> I'm<00:07:18.600> just<00:07:18.720> asking<00:07:18.870> questions<00:07:19.350> about<00:07:19.500> do<00:07:20.280> we 00:07:20.360 --> 00:07:20.370 align:start position:0% so I'm just asking questions about do we 00:07:20.370 --> 00:07:22.490 align:start position:0% so I'm just asking questions about do we trust<00:07:20.580> this<00:07:20.850> stuff<00:07:21.090> the<00:07:21.840> spec<00:07:22.080> says<00:07:22.320> to 00:07:22.490 --> 00:07:22.500 align:start position:0% trust this stuff the spec says to 00:07:22.500 --> 00:07:23.990 align:start position:0% trust this stuff the spec says to rewrite<00:07:22.770> stuff<00:07:23.039> no<00:07:23.310> one's<00:07:23.430> rewriting<00:07:23.880> it 00:07:23.990 --> 00:07:24.000 align:start position:0% rewrite stuff no one's rewriting it 00:07:24.000 --> 00:07:25.330 align:start position:0% rewrite stuff no one's rewriting it everyone's<00:07:24.300> just<00:07:24.449> doing<00:07:24.630> it<00:07:24.750> their<00:07:24.900> own<00:07:24.930> way 00:07:25.330 --> 00:07:25.340 align:start position:0% everyone's just doing it their own way 00:07:25.340 --> 00:07:27.379 align:start position:0% everyone's just doing it their own way so<00:07:26.340> what's<00:07:26.520> the<00:07:26.639> right<00:07:26.760> way<00:07:26.940> to<00:07:26.970> do<00:07:27.180> it<00:07:27.270> I<00:07:27.360> think 00:07:27.379 --> 00:07:27.389 align:start position:0% so what's the right way to do it I think 00:07:27.389 --> 00:07:29.779 align:start position:0% so what's the right way to do it I think we<00:07:27.600> have<00:07:27.780> to<00:07:27.870> audit<00:07:28.139> and<00:07:28.830> keep<00:07:29.280> a<00:07:29.370> close<00:07:29.520> eye<00:07:29.699> on 00:07:29.779 --> 00:07:29.789 align:start position:0% we have to audit and keep a close eye on 00:07:29.789 --> 00:07:31.969 align:start position:0% we have to audit and keep a close eye on everything<00:07:30.060> so<00:07:30.510> that's<00:07:30.780> the<00:07:31.320> web<00:07:31.680> assembly 00:07:31.969 --> 00:07:31.979 align:start position:0% everything so that's the web assembly 00:07:31.979 --> 00:07:43.279 align:start position:0% everything so that's the web assembly engines<00:07:32.220> talk<00:07:41.090> so<00:07:42.090> as<00:07:42.210> lean<00:07:42.389> so<00:07:42.990> I'm<00:07:43.050> giving 00:07:43.279 --> 00:07:43.289 align:start position:0% engines talk so as lean so I'm giving 00:07:43.289 --> 00:07:44.150 align:start position:0% engines talk so as lean so I'm giving the<00:07:43.380> next<00:07:43.620> talk<00:07:43.710> as<00:07:43.830> well 00:07:44.150 --> 00:07:44.160 align:start position:0% the next talk as well 00:07:44.160 --> 00:07:47.540 align:start position:0% the next talk as well it's<00:07:45.090> called<00:07:45.360> turbo<00:07:45.690> awasum<00:07:46.550> increasing 00:07:47.540 --> 00:07:47.550 align:start position:0% it's called turbo awasum increasing 00:07:47.550 --> 00:07:49.159 align:start position:0% it's called turbo awasum increasing transaction<00:07:48.120> through<00:07:48.240> butter<00:07:48.570> blossom<00:07:48.930> is 00:07:49.159 --> 00:07:49.169 align:start position:0% transaction through butter blossom is 00:07:49.169 --> 00:07:50.830 align:start position:0% transaction through butter blossom is our<00:07:49.260> code<00:07:49.440> word<00:07:49.680> within<00:07:49.860> our<00:07:50.039> team<00:07:50.280> of 00:07:50.830 --> 00:07:50.840 align:start position:0% our code word within our team of 00:07:50.840 --> 00:07:55.939 align:start position:0% our code word within our team of increasing<00:07:51.840> transaction<00:07:52.380> throughput<00:07:54.949> this 00:07:55.939 --> 00:07:55.949 align:start position:0% increasing transaction throughput this 00:07:55.949 --> 00:07:58.700 align:start position:0% increasing transaction throughput this is<00:07:56.130> joint<00:07:56.880> work<00:07:56.940> between<00:07:57.320> Dielman<00:07:58.320> ID<00:07:58.470> and 00:07:58.700 --> 00:07:58.710 align:start position:0% is joint work between Dielman ID and 00:07:58.710 --> 00:08:00.740 align:start position:0% is joint work between Dielman ID and other<00:07:59.400> people<00:07:59.729> on<00:07:59.789> the<00:07:59.880> team<00:08:00.030> of<00:08:00.180> course<00:08:00.389> have 00:08:00.740 --> 00:08:00.750 align:start position:0% other people on the team of course have 00:08:00.750 --> 00:08:08.330 align:start position:0% other people on the team of course have had<00:08:01.110> good<00:08:01.470> conversations<00:08:02.099> with<00:08:02.130> us<00:08:02.400> and<00:08:07.340> so 00:08:08.330 --> 00:08:08.340 align:start position:0% had good conversations with us and so 00:08:08.340 --> 00:08:11.180 align:start position:0% had good conversations with us and so the<00:08:08.520> big<00:08:08.639> idea<00:08:08.970> is<00:08:09.710> what<00:08:10.710> is<00:08:10.830> what<00:08:11.099> are<00:08:11.130> we 00:08:11.180 --> 00:08:11.190 align:start position:0% the big idea is what is what are we 00:08:11.190 --> 00:08:14.659 align:start position:0% the big idea is what is what are we doing<00:08:11.250> now<00:08:11.610> a<00:08:12.120> theorem<00:08:12.630> execution<00:08:13.199> at<00:08:14.190> serial 00:08:14.659 --> 00:08:14.669 align:start position:0% doing now a theorem execution at serial 00:08:14.669 --> 00:08:17.629 align:start position:0% doing now a theorem execution at serial execution<00:08:14.909> as<00:08:15.510> you<00:08:15.599> all<00:08:15.870> know<00:08:16.220> we're<00:08:17.220> disk<00:08:17.460> i/o 00:08:17.629 --> 00:08:17.639 align:start position:0% execution as you all know we're disk i/o 00:08:17.639 --> 00:08:20.390 align:start position:0% execution as you all know we're disk i/o bound<00:08:17.909> they<00:08:18.300> say<00:08:18.539> and<00:08:18.810> we<00:08:19.710> have<00:08:19.740> max<00:08:20.039> 20 00:08:20.390 --> 00:08:20.400 align:start position:0% bound they say and we have max 20 00:08:20.400 --> 00:08:22.279 align:start position:0% bound they say and we have max 20 transactions<00:08:20.909> per<00:08:21.060> second<00:08:21.479> what<00:08:22.080> does<00:08:22.139> it 00:08:22.279 --> 00:08:22.289 align:start position:0% transactions per second what does it 00:08:22.289 --> 00:08:25.370 align:start position:0% transactions per second what does it mean<00:08:22.440> what<00:08:22.949> a<00:08:23.010> serial<00:08:23.400> execution<00:08:23.520> mean<00:08:24.380> we're 00:08:25.370 --> 00:08:25.380 align:start position:0% mean what a serial execution mean we're 00:08:25.380 --> 00:08:27.620 align:start position:0% mean what a serial execution mean we're executing<00:08:25.680> transaction<00:08:26.370> one<00:08:26.550> then<00:08:27.479> we're 00:08:27.620 --> 00:08:27.630 align:start position:0% executing transaction one then we're 00:08:27.630 --> 00:08:30.110 align:start position:0% executing transaction one then we're executing<00:08:27.960> transaction<00:08:28.650> 2<00:08:28.940> then<00:08:29.940> we're 00:08:30.110 --> 00:08:30.120 align:start position:0% executing transaction 2 then we're 00:08:30.120 --> 00:08:32.690 align:start position:0% executing transaction 2 then we're executing<00:08:30.659> transaction<00:08:31.349> 3<00:08:31.590> and<00:08:31.919> so<00:08:32.219> on<00:08:32.250> into 00:08:32.690 --> 00:08:32.700 align:start position:0% executing transaction 3 and so on into 00:08:32.700 --> 00:08:33.740 align:start position:0% executing transaction 3 and so on into the<00:08:32.789> last<00:08:32.969> transaction 00:08:33.740 --> 00:08:33.750 align:start position:0% the last transaction 00:08:33.750 --> 00:08:35.990 align:start position:0% the last transaction what<00:08:34.229> does<00:08:34.349> disk<00:08:34.680> i/o<00:08:34.830> bound<00:08:35.099> mean<00:08:35.339> this<00:08:35.820> isn't 00:08:35.990 --> 00:08:36.000 align:start position:0% what does disk i/o bound mean this isn't 00:08:36.000 --> 00:08:38.089 align:start position:0% what does disk i/o bound mean this isn't to<00:08:36.209> scale<00:08:36.360> by<00:08:36.690> the<00:08:36.719> way<00:08:36.930> but<00:08:37.529> if<00:08:37.650> you<00:08:37.680> took<00:08:37.860> some 00:08:38.089 --> 00:08:38.099 align:start position:0% to scale by the way but if you took some 00:08:38.099 --> 00:08:39.800 align:start position:0% to scale by the way but if you took some operating<00:08:38.459> systems<00:08:38.550> course<00:08:39.089> you've<00:08:39.539> seen 00:08:39.800 --> 00:08:39.810 align:start position:0% operating systems course you've seen 00:08:39.810 --> 00:08:41.149 align:start position:0% operating systems course you've seen some<00:08:40.020> image<00:08:40.260> where<00:08:40.440> you're<00:08:40.560> doing<00:08:40.770> some<00:08:40.950> work 00:08:41.149 --> 00:08:41.159 align:start position:0% some image where you're doing some work 00:08:41.159 --> 00:08:42.949 align:start position:0% some image where you're doing some work and<00:08:41.400> then<00:08:41.789> you're<00:08:41.909> waiting<00:08:42.209> for<00:08:42.240> IO<00:08:42.539> and 00:08:42.949 --> 00:08:42.959 align:start position:0% and then you're waiting for IO and 00:08:42.959 --> 00:08:44.810 align:start position:0% and then you're waiting for IO and you're<00:08:43.140> waiting<00:08:43.589> and<00:08:43.830> you're<00:08:44.279> waiting<00:08:44.400> and<00:08:44.730> if 00:08:44.810 --> 00:08:44.820 align:start position:0% you're waiting and you're waiting and if 00:08:44.820 --> 00:08:46.760 align:start position:0% you're waiting and you're waiting and if it's<00:08:44.940> this<00:08:45.120> guy<00:08:45.330> o<00:08:45.360> bound<00:08:45.690> the<00:08:45.990> disk<00:08:46.260> these 00:08:46.760 --> 00:08:46.770 align:start position:0% it's this guy o bound the disk these 00:08:46.770 --> 00:08:49.670 align:start position:0% it's this guy o bound the disk these these<00:08:47.130> sort<00:08:47.400> of<00:08:47.430> i/o<00:08:47.690> ranges<00:08:48.690> dominates<00:08:49.470> the 00:08:49.670 --> 00:08:49.680 align:start position:0% these sort of i/o ranges dominates the 00:08:49.680 --> 00:08:52.190 align:start position:0% these sort of i/o ranges dominates the work<00:08:49.860> ranges<00:08:50.339> and<00:08:51.150> so<00:08:51.390> we're<00:08:51.510> waiting<00:08:51.720> and 00:08:52.190 --> 00:08:52.200 align:start position:0% work ranges and so we're waiting and 00:08:52.200 --> 00:08:54.570 align:start position:0% work ranges and so we're waiting and waiting 00:08:54.570 --> 00:08:54.580 align:start position:0% waiting 00:08:54.580 --> 00:08:58.170 align:start position:0% waiting and<00:08:54.760> waiting<00:08:55.600> for<00:08:55.870> disk<00:08:56.230> IO<00:08:56.410> to<00:08:56.649> come<00:08:56.830> back<00:08:57.180> and 00:08:58.170 --> 00:08:58.180 align:start position:0% and waiting for disk IO to come back and 00:08:58.180 --> 00:08:59.430 align:start position:0% and waiting for disk IO to come back and it<00:08:58.300> comes<00:08:58.450> back<00:08:58.630> and<00:08:58.779> we<00:08:58.839> do<00:08:58.959> work<00:08:59.080> and<00:08:59.260> we<00:08:59.320> do 00:08:59.430 --> 00:08:59.440 align:start position:0% it comes back and we do work and we do 00:08:59.440 --> 00:09:00.720 align:start position:0% it comes back and we do work and we do work<00:08:59.500> and<00:08:59.680> it<00:08:59.740> worked<00:08:59.980> and<00:09:00.130> now<00:09:00.190> we're<00:09:00.490> waiting 00:09:00.720 --> 00:09:00.730 align:start position:0% work and it worked and now we're waiting 00:09:00.730 --> 00:09:05.220 align:start position:0% work and it worked and now we're waiting and<00:09:01.450> waiting<00:09:02.410> again<00:09:03.130> and<00:09:03.670> so<00:09:04.360> we're<00:09:04.480> doing<00:09:04.600> 20 00:09:05.220 --> 00:09:05.230 align:start position:0% and waiting again and so we're doing 20 00:09:05.230 --> 00:09:07.380 align:start position:0% and waiting again and so we're doing 20 transactions<00:09:05.769> per<00:09:05.920> second<00:09:06.339> and<00:09:06.519> I<00:09:06.760> don't<00:09:07.330> know 00:09:07.380 --> 00:09:07.390 align:start position:0% transactions per second and I don't know 00:09:07.390 --> 00:09:09.180 align:start position:0% transactions per second and I don't know when<00:09:07.540> sort<00:09:08.019> of<00:09:08.080> engineers<00:09:08.500> see<00:09:08.709> this<00:09:08.860> kind<00:09:09.100> of 00:09:09.180 --> 00:09:09.190 align:start position:0% when sort of engineers see this kind of 00:09:09.190 --> 00:09:11.759 align:start position:0% when sort of engineers see this kind of thing<00:09:09.250> they're<00:09:09.580> bothered<00:09:09.970> why<00:09:10.209> can't<00:09:10.690> we<00:09:10.899> fix 00:09:11.759 --> 00:09:11.769 align:start position:0% thing they're bothered why can't we fix 00:09:11.769 --> 00:09:15.090 align:start position:0% thing they're bothered why can't we fix improve<00:09:12.760> this<00:09:13.360> because<00:09:14.140> this<00:09:14.290> is<00:09:14.350> awkward<00:09:14.649> and 00:09:15.090 --> 00:09:15.100 align:start position:0% improve this because this is awkward and 00:09:15.100 --> 00:09:17.190 align:start position:0% improve this because this is awkward and we're<00:09:16.029> engineers<00:09:16.480> and<00:09:16.690> we<00:09:16.750> know<00:09:16.870> how<00:09:16.990> to<00:09:17.019> do 00:09:17.190 --> 00:09:17.200 align:start position:0% we're engineers and we know how to do 00:09:17.200 --> 00:09:18.900 align:start position:0% we're engineers and we know how to do these<00:09:17.350> kinds<00:09:17.649> of<00:09:17.709> things<00:09:17.769> so<00:09:18.130> that's<00:09:18.339> Geum<00:09:18.880> and 00:09:18.900 --> 00:09:18.910 align:start position:0% these kinds of things so that's Geum and 00:09:18.910 --> 00:09:20.930 align:start position:0% these kinds of things so that's Geum and I<00:09:19.120> had<00:09:19.420> some<00:09:19.630> conversations<00:09:20.350> about<00:09:20.440> this 00:09:20.930 --> 00:09:20.940 align:start position:0% I had some conversations about this 00:09:20.940 --> 00:09:23.610 align:start position:0% I had some conversations about this so<00:09:21.940> aetherium<00:09:22.480> shards<00:09:22.959> we<00:09:23.170> might<00:09:23.320> have<00:09:23.500> the 00:09:23.610 --> 00:09:23.620 align:start position:0% so aetherium shards we might have the 00:09:23.620 --> 00:09:27.870 align:start position:0% so aetherium shards we might have the same<00:09:23.829> thing<00:09:25.079> shard<00:09:26.079> one<00:09:26.459> might<00:09:27.459> also<00:09:27.610> be 00:09:27.870 --> 00:09:27.880 align:start position:0% same thing shard one might also be 00:09:27.880 --> 00:09:29.250 align:start position:0% same thing shard one might also be limited<00:09:28.209> to<00:09:28.240> 20<00:09:28.540> transactions 00:09:29.250 --> 00:09:29.260 align:start position:0% limited to 20 transactions 00:09:29.260 --> 00:09:31.650 align:start position:0% limited to 20 transactions likewise<00:09:29.680> with<00:09:29.860> char<00:09:30.070> -<00:09:30.310> likewise<00:09:30.880> with<00:09:31.360> all 00:09:31.650 --> 00:09:31.660 align:start position:0% likewise with char - likewise with all 00:09:31.660 --> 00:09:36.269 align:start position:0% likewise with char - likewise with all the<00:09:31.959> shots<00:09:33.269> so<00:09:34.290> some<00:09:35.290> use<00:09:35.620> cases<00:09:35.709> like<00:09:36.010> these 00:09:36.269 --> 00:09:36.279 align:start position:0% the shots so some use cases like these 00:09:36.279 --> 00:09:39.180 align:start position:0% the shots so some use cases like these plasma<00:09:36.820> on<00:09:37.000> ramps<00:09:37.329> off<00:09:37.480> ramps<00:09:37.930> state<00:09:38.800> channels 00:09:39.180 --> 00:09:39.190 align:start position:0% plasma on ramps off ramps state channels 00:09:39.190 --> 00:09:41.790 align:start position:0% plasma on ramps off ramps state channels payment<00:09:39.790> channels<00:09:40.149> whatever<00:09:40.500> might<00:09:41.500> not<00:09:41.680> be 00:09:41.790 --> 00:09:41.800 align:start position:0% payment channels whatever might not be 00:09:41.800 --> 00:09:43.769 align:start position:0% payment channels whatever might not be usable<00:09:42.130> if<00:09:42.399> we<00:09:42.579> only<00:09:42.700> have<00:09:42.880> 20<00:09:43.329> transactions 00:09:43.769 --> 00:09:43.779 align:start position:0% usable if we only have 20 transactions 00:09:43.779 --> 00:09:47.400 align:start position:0% usable if we only have 20 transactions per<00:09:43.870> second<00:09:44.260> so<00:09:45.029> sharding<00:09:46.029> does<00:09:46.209> scale<00:09:46.510> help 00:09:47.400 --> 00:09:47.410 align:start position:0% per second so sharding does scale help 00:09:47.410 --> 00:09:48.720 align:start position:0% per second so sharding does scale help us<00:09:47.560> scale<00:09:47.769> in<00:09:47.920> some<00:09:48.130> sense<00:09:48.370> but<00:09:48.550> is<00:09:48.640> it 00:09:48.720 --> 00:09:48.730 align:start position:0% us scale in some sense but is it 00:09:48.730 --> 00:09:49.199 align:start position:0% us scale in some sense but is it meaningful 00:09:49.199 --> 00:09:49.209 align:start position:0% meaningful 00:09:49.209 --> 00:09:51.720 align:start position:0% meaningful we<00:09:49.779> still<00:09:49.990> can't<00:09:50.200> use<00:09:50.260> you<00:09:50.680> know<00:09:50.800> if<00:09:51.339> a<00:09:51.490> million 00:09:51.720 --> 00:09:51.730 align:start position:0% we still can't use you know if a million 00:09:51.730 --> 00:09:52.980 align:start position:0% we still can't use you know if a million people<00:09:51.940> want<00:09:52.089> to<00:09:52.149> get<00:09:52.269> out<00:09:52.390> of<00:09:52.510> this<00:09:52.600> payment 00:09:52.980 --> 00:09:52.990 align:start position:0% people want to get out of this payment 00:09:52.990 --> 00:09:56.190 align:start position:0% people want to get out of this payment channel<00:09:53.200> we<00:09:53.290> still<00:09:53.769> unusable<00:09:54.420> so<00:09:55.420> let's<00:09:55.630> try 00:09:56.190 --> 00:09:56.200 align:start position:0% channel we still unusable so let's try 00:09:56.200 --> 00:09:58.740 align:start position:0% channel we still unusable so let's try to<00:09:56.260> talk<00:09:57.220> about<00:09:57.490> increasing<00:09:58.240> throughput<00:09:58.540> on 00:09:58.740 --> 00:09:58.750 align:start position:0% to talk about increasing throughput on 00:09:58.750 --> 00:10:00.180 align:start position:0% to talk about increasing throughput on each<00:09:58.870> individual<00:09:59.380> shard<00:09:59.649> and<00:09:59.800> maybe<00:09:59.920> cross 00:10:00.180 --> 00:10:00.190 align:start position:0% each individual shard and maybe cross 00:10:00.190 --> 00:10:02.670 align:start position:0% each individual shard and maybe cross shards<00:10:00.550> so<00:10:00.760> when<00:10:01.630> people<00:10:01.779> say<00:10:02.050> why<00:10:02.230> can<00:10:02.410> we<00:10:02.440> use 00:10:02.670 --> 00:10:02.680 align:start position:0% shards so when people say why can we use 00:10:02.680 --> 00:10:04.139 align:start position:0% shards so when people say why can we use sharding<00:10:03.130> they<00:10:03.550> start<00:10:03.790> talking<00:10:04.029> about 00:10:04.139 --> 00:10:04.149 align:start position:0% sharding they start talking about 00:10:04.149 --> 00:10:05.819 align:start position:0% sharding they start talking about independent<00:10:04.779> universes<00:10:05.290> independent 00:10:05.819 --> 00:10:05.829 align:start position:0% independent universes independent 00:10:05.829 --> 00:10:08.069 align:start position:0% independent universes independent galaxies<00:10:06.310> things<00:10:07.270> are<00:10:07.390> independent<00:10:07.630> what 00:10:08.069 --> 00:10:08.079 align:start position:0% galaxies things are independent what 00:10:08.079 --> 00:10:13.460 align:start position:0% galaxies things are independent what does<00:10:08.170> it<00:10:08.290> mean<00:10:08.760> what<00:10:09.760> does<00:10:09.880> independence<00:10:10.329> mean 00:10:13.460 --> 00:10:13.470 align:start position:0% 00:10:13.470 --> 00:10:17.340 align:start position:0% so<00:10:14.640> I<00:10:15.640> guess<00:10:16.329> -<00:10:16.510> transit<00:10:16.930> so<00:10:17.079> we'll<00:10:17.200> define 00:10:17.340 --> 00:10:17.350 align:start position:0% so I guess - transit so we'll define 00:10:17.350 --> 00:10:19.620 align:start position:0% so I guess - transit so we'll define what<00:10:17.920> independence<00:10:18.130> means<00:10:18.459> -<00:10:19.149> transactions 00:10:19.620 --> 00:10:19.630 align:start position:0% what independence means - transactions 00:10:19.630 --> 00:10:20.940 align:start position:0% what independence means - transactions are<00:10:19.750> independent<00:10:20.200> if<00:10:20.260> they<00:10:20.380> do<00:10:20.500> not<00:10:20.649> touch<00:10:20.800> the 00:10:20.940 --> 00:10:20.950 align:start position:0% are independent if they do not touch the 00:10:20.950 --> 00:10:22.199 align:start position:0% are independent if they do not touch the same<00:10:21.130> state<00:10:21.370> location<00:10:21.850> this<00:10:22.000> is<00:10:22.120> an 00:10:22.199 --> 00:10:22.209 align:start position:0% same state location this is an 00:10:22.209 --> 00:10:23.970 align:start position:0% same state location this is an illustration<00:10:22.680> transaction<00:10:23.680> one<00:10:23.829> in 00:10:23.970 --> 00:10:23.980 align:start position:0% illustration transaction one in 00:10:23.980 --> 00:10:27.389 align:start position:0% illustration transaction one in transaction<00:10:24.520> two<00:10:25.829> transaction<00:10:26.829> one<00:10:26.980> touches 00:10:27.389 --> 00:10:27.399 align:start position:0% transaction two transaction one touches 00:10:27.399 --> 00:10:28.800 align:start position:0% transaction two transaction one touches the<00:10:27.550> upper-left<00:10:28.029> the<00:10:28.180> transaction<00:10:28.690> two 00:10:28.800 --> 00:10:28.810 align:start position:0% the upper-left the transaction two 00:10:28.810 --> 00:10:32.460 align:start position:0% the upper-left the transaction two touches<00:10:29.350> the<00:10:29.470> two<00:10:29.620> bottoms<00:10:30.600> and<00:10:31.600> you<00:10:32.320> can 00:10:32.460 --> 00:10:32.470 align:start position:0% touches the two bottoms and you can 00:10:32.470 --> 00:10:34.079 align:start position:0% touches the two bottoms and you can consider<00:10:32.740> these<00:10:32.920> transactions<00:10:33.550> independent 00:10:34.079 --> 00:10:34.089 align:start position:0% consider these transactions independent 00:10:34.089 --> 00:10:39.510 align:start position:0% consider these transactions independent of<00:10:34.180> each<00:10:34.270> other<00:10:35.459> so<00:10:36.459> with<00:10:37.060> inch<00:10:37.240> so<00:10:38.199> crushed<00:10:38.709> in 00:10:39.510 --> 00:10:39.520 align:start position:0% of each other so with inch so crushed in 00:10:39.520 --> 00:10:41.939 align:start position:0% of each other so with inch so crushed in different<00:10:39.940> shards<00:10:40.360> we're<00:10:41.230> guaranteed<00:10:41.740> if 00:10:41.939 --> 00:10:41.949 align:start position:0% different shards we're guaranteed if 00:10:41.949 --> 00:10:44.040 align:start position:0% different shards we're guaranteed if they<00:10:42.070> say<00:10:42.310> that<00:10:42.579> a<00:10:42.820> transaction<00:10:43.300> in<00:10:43.630> shard<00:10:43.870> 1 00:10:44.040 --> 00:10:44.050 align:start position:0% they say that a transaction in shard 1 00:10:44.050 --> 00:10:45.360 align:start position:0% they say that a transaction in shard 1 and<00:10:44.260> a<00:10:44.290> transaction<00:10:44.829> in<00:10:44.920> chart<00:10:45.130> 2<00:10:45.160> are 00:10:45.360 --> 00:10:45.370 align:start position:0% and a transaction in chart 2 are 00:10:45.370 --> 00:10:47.250 align:start position:0% and a transaction in chart 2 are independent<00:10:45.610> of<00:10:46.029> each<00:10:46.089> other<00:10:46.270> so<00:10:46.540> we<00:10:47.170> can 00:10:47.250 --> 00:10:47.260 align:start position:0% independent of each other so we can 00:10:47.260 --> 00:10:48.600 align:start position:0% independent of each other so we can that's<00:10:47.680> the<00:10:47.829> whole<00:10:47.980> idea<00:10:48.220> they're 00:10:48.600 --> 00:10:48.610 align:start position:0% that's the whole idea they're 00:10:48.610 --> 00:10:50.430 align:start position:0% that's the whole idea they're independent<00:10:49.180> galaxies<00:10:49.510> we<00:10:49.630> can<00:10:49.750> execute<00:10:50.260> them 00:10:50.430 --> 00:10:50.440 align:start position:0% independent galaxies we can execute them 00:10:50.440 --> 00:10:52.829 align:start position:0% independent galaxies we can execute them currently<00:10:50.949> but<00:10:51.550> how<00:10:51.640> much<00:10:51.839> transactions 00:10:52.829 --> 00:10:52.839 align:start position:0% currently but how much transactions 00:10:52.839 --> 00:10:56.699 align:start position:0% currently but how much transactions within<00:10:53.019> the<00:10:53.230> same<00:10:53.410> shard<00:10:55.050> so<00:10:56.050> the<00:10:56.290> focus<00:10:56.500> of 00:10:56.699 --> 00:10:56.709 align:start position:0% within the same shard so the focus of 00:10:56.709 --> 00:10:58.590 align:start position:0% within the same shard so the focus of this<00:10:56.860> talk<00:10:57.070> is<00:10:57.279> within<00:10:57.640> shard<00:10:58.000> transactions 00:10:58.590 --> 00:10:58.600 align:start position:0% this talk is within shard transactions 00:10:58.600 --> 00:11:00.449 align:start position:0% this talk is within shard transactions into<00:10:58.839> trash<00:10:59.050> our<00:10:59.290> transactions<00:10:59.829> across<00:11:00.279> our 00:11:00.449 --> 00:11:00.459 align:start position:0% into trash our transactions across our 00:11:00.459 --> 00:11:02.009 align:start position:0% into trash our transactions across our transaction<00:11:00.970> is<00:11:01.060> the<00:11:01.120> transaction<00:11:01.660> for 00:11:02.009 --> 00:11:02.019 align:start position:0% transaction is the transaction for 00:11:02.019 --> 00:11:07.800 align:start position:0% transaction is the transaction for example<00:11:02.320> from<00:11:02.410> shard<00:11:02.649> one<00:11:02.829> -<00:11:02.920> char<00:11:03.100> - 00:11:07.800 --> 00:11:07.810 align:start position:0% 00:11:07.810 --> 00:11:10.270 align:start position:0% okay<00:11:08.810> so<00:11:08.870> what<00:11:09.170> is<00:11:09.290> someone<00:11:09.860> that<00:11:10.010> wants<00:11:10.250> to 00:11:10.270 --> 00:11:10.280 align:start position:0% okay so what is someone that wants to 00:11:10.280 --> 00:11:13.600 align:start position:0% okay so what is someone that wants to scale<00:11:10.580> do<00:11:10.820> an<00:11:11.120> engineer<00:11:11.600> usually<00:11:12.050> will<00:11:12.550> go<00:11:13.550> to 00:11:13.600 --> 00:11:13.610 align:start position:0% scale do an engineer usually will go to 00:11:13.610 --> 00:11:16.090 align:start position:0% scale do an engineer usually will go to perhaps<00:11:14.240> Wikipedia<00:11:14.990> and<00:11:15.260> look<00:11:15.320> up<00:11:15.650> models<00:11:16.010> of 00:11:16.090 --> 00:11:16.100 align:start position:0% perhaps Wikipedia and look up models of 00:11:16.100 --> 00:11:17.530 align:start position:0% perhaps Wikipedia and look up models of concurrency<00:11:16.310> and<00:11:16.790> they'll<00:11:17.060> read<00:11:17.360> about 00:11:17.530 --> 00:11:17.540 align:start position:0% concurrency and they'll read about 00:11:17.540 --> 00:11:19.450 align:start position:0% concurrency and they'll read about actors<00:11:17.960> models<00:11:18.260> and<00:11:18.680> process<00:11:18.980> calculus 00:11:19.450 --> 00:11:19.460 align:start position:0% actors models and process calculus 00:11:19.460 --> 00:11:21.580 align:start position:0% actors models and process calculus models<00:11:19.880> and<00:11:20.180> maybe<00:11:20.900> we<00:11:21.050> can<00:11:21.170> use<00:11:21.320> these<00:11:21.530> things 00:11:21.580 --> 00:11:21.590 align:start position:0% models and maybe we can use these things 00:11:21.590 --> 00:11:23.140 align:start position:0% models and maybe we can use these things and<00:11:21.890> people<00:11:22.130> are<00:11:22.190> using<00:11:22.340> people<00:11:22.820> are<00:11:22.910> looking 00:11:23.140 --> 00:11:23.150 align:start position:0% and people are using people are looking 00:11:23.150 --> 00:11:24.880 align:start position:0% and people are using people are looking at<00:11:23.270> this<00:11:23.450> I<00:11:23.630> spoke<00:11:23.990> with<00:11:24.050> actors<00:11:24.740> with 00:11:24.880 --> 00:11:24.890 align:start position:0% at this I spoke with actors with 00:11:24.890 --> 00:11:28.030 align:start position:0% at this I spoke with actors with capabilities<00:11:25.850> the<00:11:25.970> gentleman<00:11:26.360> that<00:11:27.040> invented 00:11:28.030 --> 00:11:28.040 align:start position:0% capabilities the gentleman that invented 00:11:28.040 --> 00:11:30.460 align:start position:0% capabilities the gentleman that invented the<00:11:28.130> premia<00:11:28.520> witch<00:11:29.150> Definity<00:11:29.660> is<00:11:29.780> using<00:11:30.170> Vanna 00:11:30.460 --> 00:11:30.470 align:start position:0% the premia witch Definity is using Vanna 00:11:30.470 --> 00:11:32.290 align:start position:0% the premia witch Definity is using Vanna goreck<00:11:30.740> is<00:11:30.860> using<00:11:31.160> these<00:11:31.220> ideas<00:11:31.430> process 00:11:32.290 --> 00:11:32.300 align:start position:0% goreck is using these ideas process 00:11:32.300 --> 00:11:35.260 align:start position:0% goreck is using these ideas process calculi<00:11:32.690> are<00:11:33.350> chained<00:11:33.860> rolling<00:11:34.610> doing<00:11:35.030> great 00:11:35.260 --> 00:11:35.270 align:start position:0% calculi are chained rolling doing great 00:11:35.270 --> 00:11:36.700 align:start position:0% calculi are chained rolling doing great work<00:11:35.450> fantastic<00:11:36.140> work<00:11:36.290> and<00:11:36.470> they're<00:11:36.560> talking 00:11:36.700 --> 00:11:36.710 align:start position:0% work fantastic work and they're talking 00:11:36.710 --> 00:11:38.080 align:start position:0% work fantastic work and they're talking about<00:11:36.920> paralyzing<00:11:37.580> and<00:11:37.670> increasing 00:11:38.080 --> 00:11:38.090 align:start position:0% about paralyzing and increasing 00:11:38.090 --> 00:11:41.260 align:start position:0% about paralyzing and increasing transaction<00:11:38.600> throughputs<00:11:40.150> there<00:11:41.150> are 00:11:41.260 --> 00:11:41.270 align:start position:0% transaction throughputs there are 00:11:41.270 --> 00:11:42.550 align:start position:0% transaction throughputs there are they're<00:11:41.480> also<00:11:41.630> using<00:11:42.050> these<00:11:42.140> idea<00:11:42.470> of 00:11:42.550 --> 00:11:42.560 align:start position:0% they're also using these idea of 00:11:42.560 --> 00:11:45.130 align:start position:0% they're also using these idea of Independence<00:11:43.240> with<00:11:44.240> premia<00:11:44.660> they're<00:11:44.870> called 00:11:45.130 --> 00:11:45.140 align:start position:0% Independence with premia they're called 00:11:45.140 --> 00:11:46.870 align:start position:0% Independence with premia they're called vats<00:11:45.470> or<00:11:45.830> with<00:11:45.950> the<00:11:46.040> actors<00:11:46.400> and<00:11:46.490> capabilities 00:11:46.870 --> 00:11:46.880 align:start position:0% vats or with the actors and capabilities 00:11:46.880 --> 00:11:48.730 align:start position:0% vats or with the actors and capabilities in<00:11:46.940> general<00:11:47.210> they're<00:11:47.330> called<00:11:47.600> bats<00:11:47.870> shardis 00:11:48.730 --> 00:11:48.740 align:start position:0% in general they're called bats shardis 00:11:48.740 --> 00:11:50.620 align:start position:0% in general they're called bats shardis equivalents<00:11:49.280> of<00:11:49.400> that<00:11:49.580> in<00:11:49.820> some<00:11:50.210> sense<00:11:50.420> and 00:11:50.620 --> 00:11:50.630 align:start position:0% equivalents of that in some sense and 00:11:50.630 --> 00:11:53.020 align:start position:0% equivalents of that in some sense and process<00:11:51.380> calculi<00:11:51.680> they<00:11:51.980> call<00:11:52.130> it<00:11:52.310> namespaces 00:11:53.020 --> 00:11:53.030 align:start position:0% process calculi they call it namespaces 00:11:53.030 --> 00:11:55.810 align:start position:0% process calculi they call it namespaces so<00:11:53.120> everyone's<00:11:53.420> using<00:11:53.570> independence<00:11:54.190> so<00:11:55.190> you 00:11:55.810 --> 00:11:55.820 align:start position:0% so everyone's using independence so you 00:11:55.820 --> 00:11:58.060 align:start position:0% so everyone's using independence so you know<00:11:55.940> a<00:11:56.180> good<00:11:56.870> scientist<00:11:57.320> or<00:11:57.500> engineer<00:11:57.590> says 00:11:58.060 --> 00:11:58.070 align:start position:0% know a good scientist or engineer says 00:11:58.070 --> 00:11:59.650 align:start position:0% know a good scientist or engineer says what<00:11:58.280> is<00:11:58.520> this<00:11:58.760> independence<00:11:59.300> thing<00:11:59.450> let's 00:11:59.650 --> 00:11:59.660 align:start position:0% what is this independence thing let's 00:11:59.660 --> 00:12:02.320 align:start position:0% what is this independence thing let's define<00:12:00.110> what<00:12:00.170> this<00:12:00.530> means<00:12:00.800> and<00:12:01.100> let's<00:12:01.250> take<00:12:02.210> it 00:12:02.320 --> 00:12:02.330 align:start position:0% define what this means and let's take it 00:12:02.330 --> 00:12:03.850 align:start position:0% define what this means and let's take it as<00:12:02.420> far<00:12:02.630> as<00:12:02.720> we<00:12:02.870> can<00:12:02.990> take<00:12:03.350> it<00:12:03.410> because<00:12:03.710> you 00:12:03.850 --> 00:12:03.860 align:start position:0% as far as we can take it because you 00:12:03.860 --> 00:12:05.440 align:start position:0% as far as we can take it because you know<00:12:04.070> we're<00:12:04.460> engineers<00:12:04.670> we're<00:12:05.060> working<00:12:05.360> at 00:12:05.440 --> 00:12:05.450 align:start position:0% know we're engineers we're working at 00:12:05.450 --> 00:12:06.940 align:start position:0% know we're engineers we're working at the<00:12:05.540> margins<00:12:05.930> let's<00:12:06.140> see<00:12:06.290> let's<00:12:06.620> see<00:12:06.740> what<00:12:06.860> we 00:12:06.940 --> 00:12:06.950 align:start position:0% the margins let's see let's see what we 00:12:06.950 --> 00:12:10.690 align:start position:0% the margins let's see let's see what we can<00:12:07.100> do<00:12:08.500> okay<00:12:09.500> so<00:12:09.920> we're<00:12:10.100> going<00:12:10.310> to<00:12:10.400> define 00:12:10.690 --> 00:12:10.700 align:start position:0% can do okay so we're going to define 00:12:10.700 --> 00:12:14.140 align:start position:0% can do okay so we're going to define what<00:12:10.810> independent<00:12:11.810> subset<00:12:12.230> of<00:12:12.260> a<00:12:12.440> block<00:12:12.650> is<00:12:13.150> an 00:12:14.140 --> 00:12:14.150 align:start position:0% what independent subset of a block is an 00:12:14.150 --> 00:12:16.180 align:start position:0% what independent subset of a block is an independent<00:12:14.750> side<00:12:14.930> a<00:12:15.320> subset<00:12:15.800> of<00:12:15.830> a<00:12:15.920> block<00:12:16.070> of 00:12:16.180 --> 00:12:16.190 align:start position:0% independent side a subset of a block of 00:12:16.190 --> 00:12:17.200 align:start position:0% independent side a subset of a block of transaction<00:12:16.610> is<00:12:16.700> such<00:12:16.850> that<00:12:17.030> each 00:12:17.200 --> 00:12:17.210 align:start position:0% transaction is such that each 00:12:17.210 --> 00:12:18.940 align:start position:0% transaction is such that each transaction<00:12:17.510> is<00:12:17.930> a<00:12:17.960> subset<00:12:18.470> such<00:12:18.680> that<00:12:18.830> each 00:12:18.940 --> 00:12:18.950 align:start position:0% transaction is a subset such that each 00:12:18.950 --> 00:12:20.680 align:start position:0% transaction is a subset such that each transaction<00:12:19.220> in<00:12:19.670> the<00:12:19.760> subset<00:12:20.120> is<00:12:20.210> independent 00:12:20.680 --> 00:12:20.690 align:start position:0% transaction in the subset is independent 00:12:20.690 --> 00:12:21.910 align:start position:0% transaction in the subset is independent of<00:12:20.720> all<00:12:20.810> transactions<00:12:21.380> outside<00:12:21.710> of<00:12:21.800> that 00:12:21.910 --> 00:12:21.920 align:start position:0% of all transactions outside of that 00:12:21.920 --> 00:12:23.380 align:start position:0% of all transactions outside of that subset<00:12:22.310> that's<00:12:22.490> a<00:12:22.550> tough<00:12:22.760> definition<00:12:23.240> that's 00:12:23.380 --> 00:12:23.390 align:start position:0% subset that's a tough definition that's 00:12:23.390 --> 00:12:26.200 align:start position:0% subset that's a tough definition that's a<00:12:23.450> toughest<00:12:23.720> definition<00:12:24.140> of<00:12:24.230> this<00:12:24.320> talk<00:12:25.210> for 00:12:26.200 --> 00:12:26.210 align:start position:0% a toughest definition of this talk for 00:12:26.210 --> 00:12:29.400 align:start position:0% a toughest definition of this talk for example<00:12:26.830> an<00:12:27.830> independent<00:12:28.490> subset<00:12:28.940> is 00:12:29.400 --> 00:12:29.410 align:start position:0% example an independent subset is 00:12:29.410 --> 00:12:32.770 align:start position:0% example an independent subset is transactions<00:12:30.410> two<00:12:30.620> and<00:12:30.890> three<00:12:31.780> they're 00:12:32.770 --> 00:12:32.780 align:start position:0% transactions two and three they're 00:12:32.780 --> 00:12:36.430 align:start position:0% transactions two and three they're independent<00:12:33.320> of<00:12:34.090> all<00:12:35.090> transactions<00:12:36.080> outside 00:12:36.430 --> 00:12:36.440 align:start position:0% independent of all transactions outside 00:12:36.440 --> 00:12:37.570 align:start position:0% independent of all transactions outside of<00:12:36.560> the<00:12:36.650> subset<00:12:37.040> transaction<00:12:37.400> two<00:12:37.490> is 00:12:37.570 --> 00:12:37.580 align:start position:0% of the subset transaction two is 00:12:37.580 --> 00:12:39.010 align:start position:0% of the subset transaction two is independent<00:12:37.970> of<00:12:38.030> one<00:12:38.180> transaction<00:12:38.660> three<00:12:38.960> is 00:12:39.010 --> 00:12:39.020 align:start position:0% independent of one transaction three is 00:12:39.020 --> 00:12:40.510 align:start position:0% independent of one transaction three is independent<00:12:39.410> of<00:12:39.470> one<00:12:39.620> so<00:12:39.920> these<00:12:40.040> two<00:12:40.310> are<00:12:40.430> an 00:12:40.510 --> 00:12:40.520 align:start position:0% independent of one so these two are an 00:12:40.520 --> 00:12:42.730 align:start position:0% independent of one so these two are an independent<00:12:40.730> subsets<00:12:41.470> just<00:12:42.470> to<00:12:42.560> clarify 00:12:42.730 --> 00:12:42.740 align:start position:0% independent subsets just to clarify 00:12:42.740 --> 00:12:46.570 align:start position:0% independent subsets just to clarify that's<00:12:43.280> because<00:12:44.290> transaction<00:12:45.290> one<00:12:45.500> okay<00:12:46.460> we 00:12:46.570 --> 00:12:46.580 align:start position:0% that's because transaction one okay we 00:12:46.580 --> 00:12:48.640 align:start position:0% that's because transaction one okay we do<00:12:47.060> not<00:12:47.180> write<00:12:47.480> to<00:12:47.600> any<00:12:47.810> location<00:12:48.050> that<00:12:48.380> the 00:12:48.640 --> 00:12:48.650 align:start position:0% do not write to any location that the 00:12:48.650 --> 00:12:50.860 align:start position:0% do not write to any location that the set<00:12:48.920> of<00:12:48.950> teks<00:12:49.340> two<00:12:49.580> antiques<00:12:49.940> transaction 00:12:50.860 --> 00:12:50.870 align:start position:0% set of teks two antiques transaction 00:12:50.870 --> 00:12:52.480 align:start position:0% set of teks two antiques transaction transaction<00:12:51.290> two<00:12:51.590> and<00:12:51.740> transition<00:12:52.310> three 00:12:52.480 --> 00:12:52.490 align:start position:0% transaction two and transition three 00:12:52.490 --> 00:12:54.850 align:start position:0% transaction two and transition three fright<00:12:52.730> to<00:12:52.910> correct<00:12:53.840> yeah<00:12:54.230> so<00:12:54.470> we<00:12:54.560> have<00:12:54.680> some 00:12:54.850 --> 00:12:54.860 align:start position:0% fright to correct yeah so we have some 00:12:54.860 --> 00:12:56.200 align:start position:0% fright to correct yeah so we have some sort<00:12:55.010> of<00:12:55.100> maybe<00:12:55.340> you<00:12:55.490> can<00:12:55.610> have<00:12:55.790> a<00:12:55.820> visual 00:12:56.200 --> 00:12:56.210 align:start position:0% sort of maybe you can have a visual 00:12:56.210 --> 00:12:59.350 align:start position:0% sort of maybe you can have a visual proof<00:12:56.450> that<00:12:56.720> you<00:12:57.590> see<00:12:57.800> that<00:12:58.240> transaction<00:12:59.240> one 00:12:59.350 --> 00:12:59.360 align:start position:0% proof that you see that transaction one 00:12:59.360 --> 00:13:01.030 align:start position:0% proof that you see that transaction one writes<00:12:59.570> to<00:12:59.750> this<00:12:59.900> and<00:13:00.230> it's<00:13:00.410> independent 00:13:01.030 --> 00:13:01.040 align:start position:0% writes to this and it's independent 00:13:01.040 --> 00:13:03.130 align:start position:0% writes to this and it's independent based<00:13:01.670> on<00:13:01.790> this<00:13:01.910> the<00:13:02.150> definition<00:13:03.050> of 00:13:03.130 --> 00:13:03.140 align:start position:0% based on this the definition of 00:13:03.140 --> 00:13:04.210 align:start position:0% based on this the definition of Independence<00:13:03.620> which<00:13:03.740> was<00:13:03.770> in<00:13:03.980> a<00:13:04.070> previous 00:13:04.210 --> 00:13:04.220 align:start position:0% Independence which was in a previous 00:13:04.220 --> 00:13:05.440 align:start position:0% Independence which was in a previous slide<00:13:04.460> which<00:13:04.700> is<00:13:04.730> a<00:13:04.850> relationship<00:13:05.240> between 00:13:05.440 --> 00:13:05.450 align:start position:0% slide which is a relationship between 00:13:05.450 --> 00:13:08.350 align:start position:0% slide which is a relationship between two<00:13:05.690> transactions<00:13:06.460> and<00:13:07.460> an<00:13:07.940> independence 00:13:08.350 --> 00:13:08.360 align:start position:0% two transactions and an independence 00:13:08.360 --> 00:13:10.060 align:start position:0% two transactions and an independence partition<00:13:08.720> of<00:13:08.810> a<00:13:08.840> block<00:13:09.020> is<00:13:09.140> of<00:13:09.530> transactions 00:13:10.060 --> 00:13:10.070 align:start position:0% partition of a block is of transactions 00:13:10.070 --> 00:13:12.340 align:start position:0% partition of a block is of transactions as<00:13:10.220> such<00:13:10.340> is<00:13:10.520> a<00:13:10.610> it's<00:13:11.450> partition<00:13:11.990> into 00:13:12.340 --> 00:13:12.350 align:start position:0% as such is a it's partition into 00:13:12.350 --> 00:13:13.780 align:start position:0% as such is a it's partition into independent<00:13:12.800> subsets<00:13:13.130> partition<00:13:13.550> we<00:13:13.670> know 00:13:13.780 --> 00:13:13.790 align:start position:0% independent subsets partition we know 00:13:13.790 --> 00:13:14.830 align:start position:0% independent subsets partition we know this<00:13:13.970> partitions 00:13:14.830 --> 00:13:14.840 align:start position:0% this partitions 00:13:14.840 --> 00:13:17.080 align:start position:0% this partitions partition<00:13:15.350> of<00:13:15.410> a<00:13:15.470> set<00:13:15.500> is<00:13:15.740> is<00:13:15.950> a<00:13:16.000> breaking<00:13:17.000> it 00:13:17.080 --> 00:13:17.090 align:start position:0% partition of a set is is a breaking it 00:13:17.090 --> 00:13:19.000 align:start position:0% partition of a set is is a breaking it into<00:13:17.210> subsets<00:13:17.780> such<00:13:18.320> that<00:13:18.530> their<00:13:18.680> union<00:13:18.950> is 00:13:19.000 --> 00:13:19.010 align:start position:0% into subsets such that their union is 00:13:19.010 --> 00:13:19.810 align:start position:0% into subsets such that their union is the<00:13:19.070> whole<00:13:19.250> sudden<00:13:19.550> there 00:13:19.810 --> 00:13:19.820 align:start position:0% the whole sudden there 00:13:19.820 --> 00:13:23.860 align:start position:0% the whole sudden there pairwise<00:13:20.120> intersections<00:13:20.660> empty<00:13:21.850> so<00:13:22.850> the<00:13:23.480> the 00:13:23.860 --> 00:13:23.870 align:start position:0% pairwise intersections empty so the the 00:13:23.870 --> 00:13:25.990 align:start position:0% pairwise intersections empty so the the independence<00:13:24.650> partition<00:13:25.070> of<00:13:25.190> this<00:13:25.370> sort<00:13:25.940> of 00:13:25.990 --> 00:13:26.000 align:start position:0% independence partition of this sort of 00:13:26.000 --> 00:13:28.390 align:start position:0% independence partition of this sort of black<00:13:26.210> would<00:13:26.750> be<00:13:26.780> one<00:13:27.230> subset<00:13:27.650> is<00:13:27.770> this<00:13:27.950> just 00:13:28.390 --> 00:13:28.400 align:start position:0% black would be one subset is this just 00:13:28.400 --> 00:13:30.340 align:start position:0% black would be one subset is this just this<00:13:28.520> transaction<00:13:29.090> a<00:13:29.240> subset<00:13:30.140> with<00:13:30.230> this 00:13:30.340 --> 00:13:30.350 align:start position:0% this transaction a subset with this 00:13:30.350 --> 00:13:31.990 align:start position:0% this transaction a subset with this transaction<00:13:30.680> and<00:13:30.920> other<00:13:31.310> subset<00:13:31.760> is<00:13:31.850> these 00:13:31.990 --> 00:13:32.000 align:start position:0% transaction and other subset is these 00:13:32.000 --> 00:13:35.470 align:start position:0% transaction and other subset is these two<00:13:32.150> transactions<00:13:32.750> and<00:13:33.460> we<00:13:34.460> noticed<00:13:34.820> that<00:13:34.880> we 00:13:35.470 --> 00:13:35.480 align:start position:0% two transactions and we noticed that we 00:13:35.480 --> 00:13:36.820 align:start position:0% two transactions and we noticed that we might<00:13:35.660> be<00:13:35.750> able<00:13:35.840> to<00:13:35.960> run<00:13:36.080> these<00:13:36.230> concurrently 00:13:36.820 --> 00:13:36.830 align:start position:0% might be able to run these concurrently 00:13:36.830 --> 00:13:37.930 align:start position:0% might be able to run these concurrently because<00:13:37.190> they're<00:13:37.340> independent<00:13:37.550> of<00:13:37.850> each 00:13:37.930 --> 00:13:37.940 align:start position:0% because they're independent of each 00:13:37.940 --> 00:13:39.760 align:start position:0% because they're independent of each other<00:13:38.090> just<00:13:38.780> like<00:13:38.870> shards<00:13:39.290> are<00:13:39.380> independent 00:13:39.760 --> 00:13:39.770 align:start position:0% other just like shards are independent 00:13:39.770 --> 00:13:43.090 align:start position:0% other just like shards are independent of<00:13:39.800> each<00:13:39.920> other<00:13:41.170> okay<00:13:42.170> so<00:13:42.230> how<00:13:42.440> do<00:13:42.500> we<00:13:42.620> how<00:13:43.040> do 00:13:43.090 --> 00:13:43.100 align:start position:0% of each other okay so how do we how do 00:13:43.100 --> 00:13:45.520 align:start position:0% of each other okay so how do we how do we<00:13:43.250> build<00:13:44.060> this<00:13:44.450> independence<00:13:44.960> partition<00:13:45.380> for 00:13:45.520 --> 00:13:45.530 align:start position:0% we build this independence partition for 00:13:45.530 --> 00:13:47.380 align:start position:0% we build this independence partition for three<00:13:46.160> transactions<00:13:46.670> we<00:13:46.790> could<00:13:46.910> just<00:13:47.060> look<00:13:47.210> in 00:13:47.380 --> 00:13:47.390 align:start position:0% three transactions we could just look in 00:13:47.390 --> 00:13:48.520 align:start position:0% three transactions we could just look in point<00:13:47.630> and<00:13:47.810> say<00:13:47.870> look<00:13:48.080> these<00:13:48.230> are<00:13:48.350> independent 00:13:48.520 --> 00:13:48.530 align:start position:0% point and say look these are independent 00:13:48.530 --> 00:13:49.930 align:start position:0% point and say look these are independent but<00:13:48.860> if<00:13:48.950> we<00:13:49.040> have<00:13:49.160> a<00:13:49.190> whole<00:13:49.340> block<00:13:49.550> of<00:13:49.580> things 00:13:49.930 --> 00:13:49.940 align:start position:0% but if we have a whole block of things 00:13:49.940 --> 00:13:51.910 align:start position:0% but if we have a whole block of things it<00:13:50.480> might<00:13:50.600> be<00:13:50.720> difficult<00:13:50.930> so<00:13:51.500> we<00:13:51.620> have<00:13:51.770> some 00:13:51.910 --> 00:13:51.920 align:start position:0% it might be difficult so we have some 00:13:51.920 --> 00:13:54.660 align:start position:0% it might be difficult so we have some algorithms<00:13:52.430> to<00:13:52.640> partition<00:13:53.150> the<00:13:53.390> pool 00:13:54.660 --> 00:13:54.670 align:start position:0% algorithms to partition the pool 00:13:54.670 --> 00:13:56.800 align:start position:0% algorithms to partition the pool transaction<00:13:55.670> pool<00:13:55.850> or<00:13:56.060> block<00:13:56.660> of 00:13:56.800 --> 00:13:56.810 align:start position:0% transaction pool or block of 00:13:56.810 --> 00:13:58.350 align:start position:0% transaction pool or block of transactions<00:13:57.320> into<00:13:57.470> independent<00:13:57.890> subsets 00:13:58.350 --> 00:13:58.360 align:start position:0% transactions into independent subsets 00:13:58.360 --> 00:14:02.250 align:start position:0% transactions into independent subsets what<00:13:59.360> is<00:13:59.450> access<00:13:59.840> lists<00:14:00.110> first<00:14:00.260> of<00:14:00.470> all 00:14:02.250 --> 00:14:02.260 align:start position:0% what is access lists first of all 00:14:02.260 --> 00:14:05.770 align:start position:0% what is access lists first of all there's<00:14:03.260> a<00:14:03.740> IP<00:14:03.980> 648<00:14:04.820> there's<00:14:05.150> a<00:14:05.210> push<00:14:05.480> with 00:14:05.770 --> 00:14:05.780 align:start position:0% there's a IP 648 there's a push with 00:14:05.780 --> 00:14:07.420 align:start position:0% there's a IP 648 there's a push with each<00:14:05.930> transaction<00:14:06.350> you<00:14:06.830> say<00:14:07.040> I'm<00:14:07.250> going<00:14:07.370> to 00:14:07.420 --> 00:14:07.430 align:start position:0% each transaction you say I'm going to 00:14:07.430 --> 00:14:09.160 align:start position:0% each transaction you say I'm going to touch<00:14:07.670> these<00:14:07.880> state<00:14:08.270> locations<00:14:08.780> and<00:14:08.930> only 00:14:09.160 --> 00:14:09.170 align:start position:0% touch these state locations and only 00:14:09.170 --> 00:14:11.230 align:start position:0% touch these state locations and only these<00:14:09.290> state<00:14:09.740> locations<00:14:10.220> if<00:14:10.460> I<00:14:10.640> violate<00:14:10.820> this 00:14:11.230 --> 00:14:11.240 align:start position:0% these state locations if I violate this 00:14:11.240 --> 00:14:13.120 align:start position:0% these state locations if I violate this then<00:14:11.510> then<00:14:11.840> my<00:14:11.990> transaction<00:14:12.470> is<00:14:12.560> invalid<00:14:12.980> so 00:14:13.120 --> 00:14:13.130 align:start position:0% then then my transaction is invalid so 00:14:13.130 --> 00:14:15.010 align:start position:0% then then my transaction is invalid so there's<00:14:13.850> a<00:14:13.910> push<00:14:14.150> for<00:14:14.180> access<00:14:14.450> lists<00:14:14.900> and 00:14:15.010 --> 00:14:15.020 align:start position:0% there's a push for access lists and 00:14:15.020 --> 00:14:17.380 align:start position:0% there's a push for access lists and shards<00:14:15.350> so<00:14:15.950> there's<00:14:16.400> there's<00:14:16.760> two<00:14:16.820> cases<00:14:17.270> we 00:14:17.380 --> 00:14:17.390 align:start position:0% shards so there's there's two cases we 00:14:17.390 --> 00:14:18.520 align:start position:0% shards so there's there's two cases we can<00:14:17.540> either<00:14:17.660> we<00:14:17.810> can<00:14:17.930> do<00:14:17.990> it<00:14:18.080> with<00:14:18.200> access 00:14:18.520 --> 00:14:18.530 align:start position:0% can either we can do it with access 00:14:18.530 --> 00:14:20.350 align:start position:0% can either we can do it with access lists<00:14:18.770> or<00:14:18.890> without<00:14:19.130> access<00:14:19.460> lists<00:14:19.760> let's<00:14:20.180> talk 00:14:20.350 --> 00:14:20.360 align:start position:0% lists or without access lists let's talk 00:14:20.360 --> 00:14:23.170 align:start position:0% lists or without access lists let's talk first<00:14:20.570> about<00:14:20.720> with<00:14:20.990> access<00:14:21.350> lists<00:14:22.090> so<00:14:23.090> I'm 00:14:23.170 --> 00:14:23.180 align:start position:0% first about with access lists so I'm 00:14:23.180 --> 00:14:28.930 align:start position:0% first about with access lists so I'm gonna<00:14:23.420> do<00:14:23.720> a<00:14:23.750> visualization<00:14:24.590> and<00:14:24.830> it<00:14:26.050> it<00:14:27.050> is<00:14:27.940> it 00:14:28.930 --> 00:14:28.940 align:start position:0% gonna do a visualization and it it is it 00:14:28.940 --> 00:14:33.430 align:start position:0% gonna do a visualization and it it is it might<00:14:29.240> be<00:14:29.360> tough<00:14:29.630> so<00:14:30.500> we<00:14:30.710> have<00:14:30.860> our<00:14:30.890> block<00:14:32.440> we 00:14:33.430 --> 00:14:33.440 align:start position:0% might be tough so we have our block we 00:14:33.440 --> 00:14:35.380 align:start position:0% might be tough so we have our block we order<00:14:33.830> our<00:14:33.950> transactions<00:14:34.580> from<00:14:34.790> one<00:14:35.000> just 00:14:35.380 --> 00:14:35.390 align:start position:0% order our transactions from one just 00:14:35.390 --> 00:14:37.570 align:start position:0% order our transactions from one just forget<00:14:35.990> about<00:14:36.020> anything<00:14:36.590> below<00:14:36.890> transaction 00:14:37.570 --> 00:14:37.580 align:start position:0% forget about anything below transaction 00:14:37.580 --> 00:14:39.580 align:start position:0% forget about anything below transaction zero<00:14:37.910> transaction<00:14:38.330> one<00:14:38.660> all<00:14:38.870> the<00:14:38.960> way<00:14:39.050> to<00:14:39.110> st. 00:14:39.580 --> 00:14:39.590 align:start position:0% zero transaction one all the way to st. 00:14:39.590 --> 00:14:42.850 align:start position:0% zero transaction one all the way to st. transaction<00:14:40.220> 60-63<00:14:41.440> we<00:14:42.440> notice<00:14:42.740> that 00:14:42.850 --> 00:14:42.860 align:start position:0% transaction 60-63 we notice that 00:14:42.860 --> 00:14:44.620 align:start position:0% transaction 60-63 we notice that transact<00:14:43.310> and<00:14:43.400> then<00:14:43.580> we<00:14:43.700> write<00:14:44.360> the<00:14:44.390> same 00:14:44.620 --> 00:14:44.630 align:start position:0% transact and then we write the same 00:14:44.630 --> 00:14:46.720 align:start position:0% transact and then we write the same transactions<00:14:45.290> on<00:14:45.530> this<00:14:45.710> column<00:14:46.130> we<00:14:46.460> notice 00:14:46.720 --> 00:14:46.730 align:start position:0% transactions on this column we notice 00:14:46.730 --> 00:14:48.400 align:start position:0% transactions on this column we notice that<00:14:46.820> transaction<00:14:47.360> 0<00:14:47.570> and<00:14:47.720> transaction<00:14:48.170> 0 00:14:48.400 --> 00:14:48.410 align:start position:0% that transaction 0 and transaction 0 00:14:48.410 --> 00:14:51.340 align:start position:0% that transaction 0 and transaction 0 interact<00:14:49.370> which<00:14:49.550> are<00:14:50.230> dependent<00:14:51.230> on<00:14:51.290> each 00:14:51.340 --> 00:14:51.350 align:start position:0% interact which are dependent on each 00:14:51.350 --> 00:14:53.470 align:start position:0% interact which are dependent on each other<00:14:51.590> so<00:14:51.770> we<00:14:51.830> put<00:14:52.040> a<00:14:52.070> orange<00:14:52.940> square<00:14:53.330> there 00:14:53.470 --> 00:14:53.480 align:start position:0% other so we put a orange square there 00:14:53.480 --> 00:14:55.990 align:start position:0% other so we put a orange square there and<00:14:53.630> also<00:14:54.020> 63<00:14:54.800> whatever<00:14:55.310> this<00:14:55.610> is<00:14:55.730> based<00:14:55.910> on 00:14:55.990 --> 00:14:56.000 align:start position:0% and also 63 whatever this is based on 00:14:56.000 --> 00:14:57.520 align:start position:0% and also 63 whatever this is based on accesses<00:14:56.480> we<00:14:56.570> take<00:14:56.750> these<00:14:56.840> access<00:14:57.200> lists<00:14:57.440> we 00:14:57.520 --> 00:14:57.530 align:start position:0% accesses we take these access lists we 00:14:57.530 --> 00:14:59.260 align:start position:0% accesses we take these access lists we compare<00:14:57.890> see<00:14:58.310> if<00:14:58.400> they<00:14:58.490> intersect<00:14:58.910> with<00:14:58.970> the 00:14:59.260 --> 00:14:59.270 align:start position:0% compare see if they intersect with the 00:14:59.270 --> 00:15:01.570 align:start position:0% compare see if they intersect with the with<00:14:59.540> you<00:15:00.050> know<00:15:00.140> 10<00:15:00.320> second<00:15:00.560> 0<00:15:00.740> in<00:15:00.860> 63<00:15:01.190> yes<00:15:01.400> they 00:15:01.570 --> 00:15:01.580 align:start position:0% with you know 10 second 0 in 63 yes they 00:15:01.580 --> 00:15:04.660 align:start position:0% with you know 10 second 0 in 63 yes they do<00:15:01.640> 4<00:15:01.880> 0<00:15:02.060> in<00:15:02.150> 63<00:15:02.510> so<00:15:02.930> we<00:15:02.990> put<00:15:03.230> a<00:15:03.410> a<00:15:03.770> orange<00:15:04.430> square 00:15:04.660 --> 00:15:04.670 align:start position:0% do 4 0 in 63 so we put a a orange square 00:15:04.670 --> 00:15:07.900 align:start position:0% do 4 0 in 63 so we put a a orange square there<00:15:04.880> and<00:15:05.090> we<00:15:05.690> can<00:15:05.840> partition<00:15:06.200> this<00:15:06.700> block<00:15:07.700> of 00:15:07.900 --> 00:15:07.910 align:start position:0% there and we can partition this block of 00:15:07.910 --> 00:15:16.429 align:start position:0% there and we can partition this block of transactions 00:15:16.429 --> 00:15:16.439 align:start position:0% 00:15:16.439 --> 00:15:19.739 align:start position:0% into<00:15:17.439> independent<00:15:17.920> subsets<00:15:18.369> so<00:15:18.819> this<00:15:19.149> subset 00:15:19.739 --> 00:15:19.749 align:start position:0% into independent subsets so this subset 00:15:19.749 --> 00:15:22.979 align:start position:0% into independent subsets so this subset this<00:15:20.459> this<00:15:21.459> is<00:15:21.579> upset<00:15:21.970> you<00:15:22.299> know<00:15:22.329> this<00:15:22.720> chunk 00:15:22.979 --> 00:15:22.989 align:start position:0% this this is upset you know this chunk 00:15:22.989 --> 00:15:25.499 align:start position:0% this this is upset you know this chunk of<00:15:23.110> transactions<00:15:23.769> is<00:15:24.699> independent<00:15:25.299> of<00:15:25.389> all 00:15:25.499 --> 00:15:25.509 align:start position:0% of transactions is independent of all 00:15:25.509 --> 00:15:27.449 align:start position:0% of transactions is independent of all other<00:15:25.540> transactions<00:15:26.410> why<00:15:26.619> because<00:15:27.309> there's 00:15:27.449 --> 00:15:27.459 align:start position:0% other transactions why because there's 00:15:27.459 --> 00:15:30.269 align:start position:0% other transactions why because there's no<00:15:27.610> orange<00:15:27.850> you<00:15:28.480> know<00:15:28.769> things<00:15:29.769> colored<00:15:30.160> in 00:15:30.269 --> 00:15:30.279 align:start position:0% no orange you know things colored in 00:15:30.279 --> 00:15:32.639 align:start position:0% no orange you know things colored in here<00:15:30.489> so<00:15:30.819> this<00:15:30.939> is<00:15:31.059> maybe<00:15:31.209> the<00:15:31.360> kitty<00:15:32.230> cat<00:15:32.499> app 00:15:32.639 --> 00:15:32.649 align:start position:0% here so this is maybe the kitty cat app 00:15:32.649 --> 00:15:35.669 align:start position:0% here so this is maybe the kitty cat app this<00:15:33.189> is<00:15:33.249> a<00:15:33.459> decentralized<00:15:34.239> exchange<00:15:34.569> this<00:15:35.470> is 00:15:35.669 --> 00:15:35.679 align:start position:0% this is a decentralized exchange this is 00:15:35.679 --> 00:15:38.519 align:start position:0% this is a decentralized exchange this is some<00:15:36.119> mixer<00:15:37.119> this<00:15:37.360> is<00:15:37.540> some<00:15:37.689> ICO<00:15:38.079> these<00:15:38.379> are 00:15:38.519 --> 00:15:38.529 align:start position:0% some mixer this is some ICO these are 00:15:38.529 --> 00:15:41.189 align:start position:0% some mixer this is some ICO these are one-off<00:15:38.860> transactions<00:15:39.579> and<00:15:39.819> we<00:15:40.269> can<00:15:40.420> execute 00:15:41.189 --> 00:15:41.199 align:start position:0% one-off transactions and we can execute 00:15:41.199 --> 00:15:42.269 align:start position:0% one-off transactions and we can execute each<00:15:41.410> of<00:15:41.559> these<00:15:41.679> sort<00:15:41.920> of<00:15:41.980> chunks 00:15:42.269 --> 00:15:42.279 align:start position:0% each of these sort of chunks 00:15:42.279 --> 00:15:44.999 align:start position:0% each of these sort of chunks independently<00:15:42.910> of<00:15:43.029> each<00:15:43.420> other<00:15:43.980> because<00:15:44.980> of 00:15:44.999 --> 00:15:45.009 align:start position:0% independently of each other because of 00:15:45.009 --> 00:15:46.289 align:start position:0% independently of each other because of this<00:15:45.160> independence<00:15:45.670> property<00:15:45.850> just<00:15:46.239> like 00:15:46.289 --> 00:15:46.299 align:start position:0% this independence property just like 00:15:46.299 --> 00:15:53.879 align:start position:0% this independence property just like shards<00:15:46.660> are<00:15:46.749> independent<00:15:47.259> yeah<00:15:48.220> I<00:15:52.799> got<00:15:53.799> it 00:15:53.879 --> 00:15:53.889 align:start position:0% shards are independent yeah I got it 00:15:53.889 --> 00:15:58.499 align:start position:0% shards are independent yeah I got it okay<00:15:55.980> likewise<00:15:56.980> if<00:15:57.160> you<00:15:57.279> have<00:15:57.459> many<00:15:58.329> more 00:15:58.499 --> 00:15:58.509 align:start position:0% okay likewise if you have many more 00:15:58.509 --> 00:15:59.970 align:start position:0% okay likewise if you have many more transactions<00:15:59.139> you<00:15:59.230> can<00:15:59.259> break<00:15:59.739> it<00:15:59.860> into 00:15:59.970 --> 00:15:59.980 align:start position:0% transactions you can break it into 00:15:59.980 --> 00:16:04.889 align:start position:0% transactions you can break it into independent<00:16:00.459> subsets<00:16:03.420> so<00:16:04.420> this<00:16:04.569> is<00:16:04.660> just<00:16:04.779> an 00:16:04.889 --> 00:16:04.899 align:start position:0% independent subsets so this is just an 00:16:04.899 --> 00:16:09.150 align:start position:0% independent subsets so this is just an idea<00:16:05.019> to<00:16:05.470> paralyze<00:16:06.689> a<00:16:07.689> given<00:16:08.410> block<00:16:08.589> we're<00:16:09.040> not 00:16:09.150 --> 00:16:09.160 align:start position:0% idea to paralyze a given block we're not 00:16:09.160 --> 00:16:14.009 align:start position:0% idea to paralyze a given block we're not doing<00:16:09.399> it<00:16:09.549> yes<00:16:10.379> so<00:16:11.379> that's<00:16:11.769> the<00:16:12.009> big<00:16:12.989> so<00:16:13.989> you 00:16:14.009 --> 00:16:14.019 align:start position:0% doing it yes so that's the big so you 00:16:14.019 --> 00:16:15.449 align:start position:0% doing it yes so that's the big so you see<00:16:14.230> these<00:16:14.379> independent<00:16:14.860> there's<00:16:14.980> many<00:16:15.189> so<00:16:15.369> we 00:16:15.449 --> 00:16:15.459 align:start position:0% see these independent there's many so we 00:16:15.459 --> 00:16:19.679 align:start position:0% see these independent there's many so we can<00:16:15.579> do<00:16:15.639> it<00:16:15.670> we<00:16:15.879> can<00:16:16.239> scale<00:16:16.540> this<00:16:18.480> okay<00:16:19.480> without 00:16:19.679 --> 00:16:19.689 align:start position:0% can do it we can scale this okay without 00:16:19.689 --> 00:16:21.299 align:start position:0% can do it we can scale this okay without excess<00:16:20.110> list<00:16:20.350> that's<00:16:20.439> awkward<00:16:20.619> we<00:16:21.100> currently 00:16:21.299 --> 00:16:21.309 align:start position:0% excess list that's awkward we currently 00:16:21.309 --> 00:16:22.859 align:start position:0% excess list that's awkward we currently don't<00:16:21.549> have<00:16:21.669> excess<00:16:21.970> list<00:16:22.179> and<00:16:22.269> etherium<00:16:22.660> so 00:16:22.859 --> 00:16:22.869 align:start position:0% don't have excess list and etherium so 00:16:22.869 --> 00:16:24.840 align:start position:0% don't have excess list and etherium so we<00:16:22.989> might<00:16:23.139> execute<00:16:23.619> a<00:16:23.769> transaction<00:16:24.369> see<00:16:24.579> if<00:16:24.669> it 00:16:24.840 --> 00:16:24.850 align:start position:0% we might execute a transaction see if it 00:16:24.850 --> 00:16:27.929 align:start position:0% we might execute a transaction see if it sort<00:16:25.179> of<00:16:25.619> hinders<00:16:26.619> our<00:16:26.860> concurrency<00:16:27.610> so<00:16:27.759> if<00:16:27.850> it 00:16:27.929 --> 00:16:27.939 align:start position:0% sort of hinders our concurrency so if it 00:16:27.939 --> 00:16:29.220 align:start position:0% sort of hinders our concurrency so if it touches<00:16:28.149> a<00:16:28.299> bunch<00:16:28.509> of<00:16:28.600> these<00:16:28.779> independent 00:16:29.220 --> 00:16:29.230 align:start position:0% touches a bunch of these independent 00:16:29.230 --> 00:16:30.600 align:start position:0% touches a bunch of these independent subsets<00:16:29.589> then<00:16:29.709> we<00:16:29.889> won't<00:16:30.040> include<00:16:30.220> it<00:16:30.519> of 00:16:30.600 --> 00:16:30.610 align:start position:0% subsets then we won't include it of 00:16:30.610 --> 00:16:32.100 align:start position:0% subsets then we won't include it of course<00:16:30.730> there's<00:16:30.939> a<00:16:31.029> DA<00:16:31.179> stack<00:16:31.480> worst<00:16:31.899> case 00:16:32.100 --> 00:16:32.110 align:start position:0% course there's a DA stack worst case 00:16:32.110 --> 00:16:35.159 align:start position:0% course there's a DA stack worst case will<00:16:32.259> go<00:16:32.410> to<00:16:32.439> serial<00:16:32.919> execution<00:16:33.899> but<00:16:34.899> this<00:16:35.049> is 00:16:35.159 --> 00:16:35.169 align:start position:0% will go to serial execution but this is 00:16:35.169 --> 00:16:36.869 align:start position:0% will go to serial execution but this is one<00:16:35.379> possibility<00:16:35.799> to<00:16:36.100> scale<00:16:36.309> the<00:16:36.459> main<00:16:36.579> chain 00:16:36.869 --> 00:16:36.879 align:start position:0% one possibility to scale the main chain 00:16:36.879 --> 00:16:38.460 align:start position:0% one possibility to scale the main chain and<00:16:37.149> it's<00:16:37.360> all<00:16:37.480> based<00:16:37.660> on<00:16:37.779> independence<00:16:38.319> the 00:16:38.460 --> 00:16:38.470 align:start position:0% and it's all based on independence the 00:16:38.470 --> 00:16:40.019 align:start position:0% and it's all based on independence the simple<00:16:38.769> idea<00:16:39.040> that<00:16:39.129> you<00:16:39.699> know<00:16:39.790> independent 00:16:40.019 --> 00:16:40.029 align:start position:0% simple idea that you know independent 00:16:40.029 --> 00:16:41.759 align:start position:0% simple idea that you know independent universe's<00:16:40.720> galaxies<00:16:41.230> we're<00:16:41.410> just<00:16:41.559> taking 00:16:41.759 --> 00:16:41.769 align:start position:0% universe's galaxies we're just taking 00:16:41.769 --> 00:16:43.650 align:start position:0% universe's galaxies we're just taking this<00:16:42.040> as<00:16:42.610> far<00:16:42.879> as<00:16:42.970> we<00:16:43.059> possibly<00:16:43.419> can<00:16:43.569> like 00:16:43.650 --> 00:16:43.660 align:start position:0% this as far as we possibly can like 00:16:43.660 --> 00:16:48.059 align:start position:0% this as far as we possibly can like we're<00:16:43.959> maybe<00:16:44.619> scientists<00:16:45.220> or<00:16:45.309> engineers<00:16:47.069> so 00:16:48.059 --> 00:16:48.069 align:start position:0% we're maybe scientists or engineers so 00:16:48.069 --> 00:16:50.699 align:start position:0% we're maybe scientists or engineers so then<00:16:48.220> each<00:16:48.549> independent<00:16:49.179> subset<00:16:49.660> we<00:16:50.110> execute 00:16:50.699 --> 00:16:50.709 align:start position:0% then each independent subset we execute 00:16:50.709 --> 00:16:52.919 align:start position:0% then each independent subset we execute on<00:16:51.040> its<00:16:51.730> own<00:16:51.850> CQ<00:16:52.299> perhaps<00:16:52.600> we've<00:16:52.779> already 00:16:52.919 --> 00:16:52.929 align:start position:0% on its own CQ perhaps we've already 00:16:52.929 --> 00:16:55.590 align:start position:0% on its own CQ perhaps we've already known<00:16:53.169> this<00:16:53.319> since<00:16:53.529> since<00:16:54.100> e<00:16:54.369> IQ<00:16:54.669> 648<00:16:55.329> this<00:16:55.480> is 00:16:55.590 --> 00:16:55.600 align:start position:0% known this since since e IQ 648 this is 00:16:55.600 --> 00:16:58.859 align:start position:0% known this since since e IQ 648 this is nothing<00:16:55.929> new<00:16:56.790> but<00:16:57.790> this<00:16:57.970> but<00:16:58.360> this<00:16:58.569> sort<00:16:58.779> of 00:16:58.859 --> 00:16:58.869 align:start position:0% nothing new but this but this sort of 00:16:58.869 --> 00:17:00.539 align:start position:0% nothing new but this but this sort of act<00:16:59.169> this<00:16:59.439> this<00:16:59.769> looks<00:16:59.980> like<00:17:00.069> the<00:17:00.220> sharding 00:17:00.539 --> 00:17:00.549 align:start position:0% act this this looks like the sharding 00:17:00.549 --> 00:17:02.519 align:start position:0% act this this looks like the sharding picture<00:17:00.879> where<00:17:01.119> shard<00:17:01.540> zero<00:17:01.749> shard<00:17:02.049> one<00:17:02.199> to 00:17:02.519 --> 00:17:02.529 align:start position:0% picture where shard zero shard one to 00:17:02.529 --> 00:17:04.980 align:start position:0% picture where shard zero shard one to shard<00:17:02.739> n<00:17:02.949> but<00:17:03.639> each<00:17:03.790> one<00:17:04.029> is<00:17:04.209> sort<00:17:04.389> of<00:17:04.539> not 00:17:04.980 --> 00:17:04.990 align:start position:0% shard n but each one is sort of not 00:17:04.990 --> 00:17:07.049 align:start position:0% shard n but each one is sort of not shard<00:17:05.319> we're<00:17:05.500> sort<00:17:05.679> of<00:17:05.740> dynamically<00:17:06.250> creating 00:17:07.049 --> 00:17:07.059 align:start position:0% shard we're sort of dynamically creating 00:17:07.059 --> 00:17:10.230 align:start position:0% shard we're sort of dynamically creating shards<00:17:07.419> and<00:17:08.490> we're<00:17:09.490> solving<00:17:09.639> two<00:17:09.880> important 00:17:10.230 --> 00:17:10.240 align:start position:0% shards and we're solving two important 00:17:10.240 --> 00:17:12.720 align:start position:0% shards and we're solving two important problems<00:17:10.470> within<00:17:11.470> a<00:17:11.740> single<00:17:12.159> shard<00:17:12.370> and<00:17:12.519> cross 00:17:12.720 --> 00:17:12.730 align:start position:0% problems within a single shard and cross 00:17:12.730 --> 00:17:15.419 align:start position:0% problems within a single shard and cross shards<00:17:13.120> we<00:17:13.809> we<00:17:14.049> can<00:17:14.470> use<00:17:14.559> these<00:17:14.679> ideas<00:17:14.829> so<00:17:15.399> we 00:17:15.419 --> 00:17:15.429 align:start position:0% shards we we can use these ideas so we 00:17:15.429 --> 00:17:17.759 align:start position:0% shards we we can use these ideas so we vom<00:17:16.179> and<00:17:16.329> I<00:17:16.389> are<00:17:16.449> sort<00:17:16.779> of<00:17:16.899> trained<00:17:17.679> in 00:17:17.759 --> 00:17:17.769 align:start position:0% vom and I are sort of trained in 00:17:17.769 --> 00:17:19.769 align:start position:0% vom and I are sort of trained in computer<00:17:18.339> science<00:17:18.490> science<00:17:19.299> and<00:17:19.449> we<00:17:19.539> sort<00:17:19.750> of 00:17:19.769 --> 00:17:19.779 align:start position:0% computer science science and we sort of 00:17:19.779 --> 00:17:21.539 align:start position:0% computer science science and we sort of talk<00:17:19.959> about<00:17:20.199> operating<00:17:20.529> systems<00:17:20.919> and<00:17:21.159> when 00:17:21.539 --> 00:17:21.549 align:start position:0% talk about operating systems and when 00:17:21.549 --> 00:17:23.909 align:start position:0% talk about operating systems and when you<00:17:21.610> take<00:17:21.760> an<00:17:21.850> operating<00:17:22.240> systems<00:17:22.569> course<00:17:22.919> you 00:17:23.909 --> 00:17:23.919 align:start position:0% you take an operating systems course you 00:17:23.919 --> 00:17:27.210 align:start position:0% you take an operating systems course you learn<00:17:24.130> about<00:17:24.569> threads<00:17:25.569> and<00:17:25.809> preemption<00:17:26.380> and 00:17:27.210 --> 00:17:27.220 align:start position:0% learn about threads and preemption and 00:17:27.220 --> 00:17:29.520 align:start position:0% learn about threads and preemption and we<00:17:27.339> have<00:17:27.429> this<00:17:27.549> disk<00:17:27.819> i/o<00:17:28.029> bottleneck 00:17:29.520 --> 00:17:29.530 align:start position:0% we have this disk i/o bottleneck 00:17:29.530 --> 00:17:32.250 align:start position:0% we have this disk i/o bottleneck so<00:17:29.950> our<00:17:30.070> idea<00:17:30.580> is<00:17:31.030> to<00:17:31.059> use<00:17:31.360> threads<00:17:31.900> so<00:17:32.110> each 00:17:32.250 --> 00:17:32.260 align:start position:0% so our idea is to use threads so each 00:17:32.260 --> 00:17:33.930 align:start position:0% so our idea is to use threads so each thread<00:17:32.620> corresponds<00:17:33.250> with<00:17:33.280> an<00:17:33.490> independent 00:17:33.930 --> 00:17:33.940 align:start position:0% thread corresponds with an independent 00:17:33.940 --> 00:17:36.060 align:start position:0% thread corresponds with an independent subset<00:17:34.330> so<00:17:34.450> we<00:17:34.540> start<00:17:34.750> executing<00:17:34.990> thread<00:17:35.860> 1 00:17:36.060 --> 00:17:36.070 align:start position:0% subset so we start executing thread 1 00:17:36.070 --> 00:17:37.380 align:start position:0% subset so we start executing thread 1 which<00:17:36.280> is<00:17:36.400> independent<00:17:36.820> you<00:17:36.940> know<00:17:37.000> the<00:17:37.179> top 00:17:37.380 --> 00:17:37.390 align:start position:0% which is independent you know the top 00:17:37.390 --> 00:17:39.960 align:start position:0% which is independent you know the top left<00:17:37.720> corner<00:17:38.020> of<00:17:38.140> independent<00:17:38.799> or<00:17:39.460> whatever 00:17:39.960 --> 00:17:39.970 align:start position:0% left corner of independent or whatever 00:17:39.970 --> 00:17:42.230 align:start position:0% left corner of independent or whatever it<00:17:40.240> starts<00:17:40.720> executing<00:17:40.870> it<00:17:41.350> asks<00:17:41.650> for<00:17:41.679> disk<00:17:42.040> i/o 00:17:42.230 --> 00:17:42.240 align:start position:0% it starts executing it asks for disk i/o 00:17:42.240 --> 00:17:44.760 align:start position:0% it starts executing it asks for disk i/o there's<00:17:43.240> a<00:17:43.299> scheduler<00:17:43.990> in<00:17:44.110> operating<00:17:44.410> systems 00:17:44.760 --> 00:17:44.770 align:start position:0% there's a scheduler in operating systems 00:17:44.770 --> 00:17:47.070 align:start position:0% there's a scheduler in operating systems as<00:17:44.890> you<00:17:44.919> know<00:17:45.130> it'll<00:17:45.610> preempt<00:17:46.299> this<00:17:46.750> thread 00:17:47.070 --> 00:17:47.080 align:start position:0% as you know it'll preempt this thread 00:17:47.080 --> 00:17:49.380 align:start position:0% as you know it'll preempt this thread while<00:17:47.980> it's<00:17:48.160> waiting<00:17:48.400> for<00:17:48.549> i/o<00:17:48.640> and<00:17:48.970> schedule 00:17:49.380 --> 00:17:49.390 align:start position:0% while it's waiting for i/o and schedule 00:17:49.390 --> 00:17:52.440 align:start position:0% while it's waiting for i/o and schedule this<00:17:49.510> thread<00:17:49.870> so<00:17:50.440> it's<00:17:50.559> doing<00:17:50.799> work<00:17:51.059> this<00:17:52.059> this 00:17:52.440 --> 00:17:52.450 align:start position:0% this thread so it's doing work this this 00:17:52.450 --> 00:17:53.640 align:start position:0% this thread so it's doing work this this this<00:17:52.840> thread<00:17:53.049> starts<00:17:53.290> waiting<00:17:53.530> this 00:17:53.640 --> 00:17:53.650 align:start position:0% this thread starts waiting this 00:17:53.650 --> 00:17:55.350 align:start position:0% this thread starts waiting this independent<00:17:54.100> subset<00:17:54.400> is<00:17:54.520> waiting<00:17:54.730> for<00:17:54.880> for 00:17:55.350 --> 00:17:55.360 align:start position:0% independent subset is waiting for for 00:17:55.360 --> 00:17:57.780 align:start position:0% independent subset is waiting for for i/o<00:17:55.590> preempted<00:17:56.590> this<00:17:57.040> one<00:17:57.250> is<00:17:57.309> doing<00:17:57.429> works<00:17:57.640> or 00:17:57.780 --> 00:17:57.790 align:start position:0% i/o preempted this one is doing works or 00:17:57.790 --> 00:18:00.470 align:start position:0% i/o preempted this one is doing works or essentially<00:17:58.240> we're<00:17:58.660> trying<00:17:58.690> to<00:17:59.020> use<00:17:59.140> 100%<00:17:59.620> CPU 00:18:00.470 --> 00:18:00.480 align:start position:0% essentially we're trying to use 100% CPU 00:18:00.480 --> 00:18:02.700 align:start position:0% essentially we're trying to use 100% CPU so<00:18:01.480> we're<00:18:01.570> trying<00:18:01.780> to<00:18:01.840> eliminate<00:18:02.260> this<00:18:02.380> i/o 00:18:02.700 --> 00:18:02.710 align:start position:0% so we're trying to eliminate this i/o 00:18:02.710 --> 00:18:04.590 align:start position:0% so we're trying to eliminate this i/o bottleneck<00:18:02.980> whether<00:18:03.490> it's<00:18:03.730> disk<00:18:04.030> i/o<00:18:04.240> whether 00:18:04.590 --> 00:18:04.600 align:start position:0% bottleneck whether it's disk i/o whether 00:18:04.600 --> 00:18:08.270 align:start position:0% bottleneck whether it's disk i/o whether it's<00:18:04.840> network<00:18:05.679> i/o<00:18:05.890> whatever<00:18:06.250> it<00:18:06.400> may<00:18:06.520> be<00:18:06.750> and 00:18:08.270 --> 00:18:08.280 align:start position:0% it's network i/o whatever it may be and 00:18:08.280 --> 00:18:10.500 align:start position:0% it's network i/o whatever it may be and we're<00:18:09.280> just<00:18:09.370> using<00:18:09.549> a<00:18:09.700> things<00:18:10.090> from<00:18:10.240> operating 00:18:10.500 --> 00:18:10.510 align:start position:0% we're just using a things from operating 00:18:10.510 --> 00:18:12.330 align:start position:0% we're just using a things from operating so<00:18:10.600> we<00:18:10.780> can<00:18:10.929> just<00:18:11.140> use<00:18:11.320> a<00:18:11.350> regular<00:18:11.590> operating 00:18:12.330 --> 00:18:12.340 align:start position:0% so we can just use a regular operating 00:18:12.340 --> 00:18:13.950 align:start position:0% so we can just use a regular operating system<00:18:12.700> with<00:18:12.790> P<00:18:12.970> threads<00:18:13.210> or<00:18:13.390> whatever<00:18:13.660> this 00:18:13.950 --> 00:18:13.960 align:start position:0% system with P threads or whatever this 00:18:13.960 --> 00:18:18.750 align:start position:0% system with P threads or whatever this stuff<00:18:14.080> is<00:18:14.260> available<00:18:14.770> now<00:18:14.970> or<00:18:16.919> do<00:18:17.919> it<00:18:18.040> you<00:18:18.610> know 00:18:18.750 --> 00:18:18.760 align:start position:0% stuff is available now or do it you know 00:18:18.760 --> 00:18:21.630 align:start position:0% stuff is available now or do it you know with<00:18:19.120> many<00:18:19.299> CPUs<00:18:19.870> so<00:18:20.280> hopefully<00:18:21.280> we<00:18:21.370> can<00:18:21.520> use 00:18:21.630 --> 00:18:21.640 align:start position:0% with many CPUs so hopefully we can use 00:18:21.640 --> 00:18:25.350 align:start position:0% with many CPUs so hopefully we can use 100%<00:18:22.120> of<00:18:22.330> hardware<00:18:23.820> that's<00:18:24.820> the<00:18:25.059> dream<00:18:25.299> of 00:18:25.350 --> 00:18:25.360 align:start position:0% 100% of hardware that's the dream of 00:18:25.360 --> 00:18:26.940 align:start position:0% 100% of hardware that's the dream of like<00:18:25.660> you<00:18:25.900> know<00:18:25.929> computer<00:18:26.410> scientists<00:18:26.919> use 00:18:26.940 --> 00:18:26.950 align:start position:0% like you know computer scientists use 00:18:26.950 --> 00:18:32.490 align:start position:0% like you know computer scientists use 100%<00:18:27.549> of<00:18:28.059> hardware<00:18:28.390> I<00:18:28.450> think<00:18:28.890> so<00:18:31.230> yawn<00:18:32.230> play 00:18:32.490 --> 00:18:32.500 align:start position:0% 100% of hardware I think so yawn play 00:18:32.500 --> 00:18:37.740 align:start position:0% 100% of hardware I think so yawn play clean<00:18:32.980> up<00:18:33.450> so<00:18:34.450> as<00:18:35.400> quick<00:18:36.400> maybe<00:18:37.030> a<00:18:37.120> reminder<00:18:37.540> so 00:18:37.740 --> 00:18:37.750 align:start position:0% clean up so as quick maybe a reminder so 00:18:37.750 --> 00:18:40.440 align:start position:0% clean up so as quick maybe a reminder so the<00:18:37.929> question<00:18:38.230> thank<00:18:38.470> you<00:18:38.530> was<00:18:39.130> about<00:18:39.460> ball 00:18:40.440 --> 00:18:40.450 align:start position:0% the question thank you was about ball 00:18:40.450 --> 00:18:45.000 align:start position:0% the question thank you was about ball neck<00:18:40.660> so<00:18:40.900> i/o<00:18:42.450> was<00:18:43.450> very<00:18:43.990> well<00:18:44.140> explained<00:18:44.500> that 00:18:45.000 --> 00:18:45.010 align:start position:0% neck so i/o was very well explained that 00:18:45.010 --> 00:18:50.039 align:start position:0% neck so i/o was very well explained that I<00:18:45.460> always<00:18:46.200> make<00:18:47.200> in<00:18:47.380> a<00:18:47.470> theorem<00:18:47.740> 1.0<00:18:48.400> it's<00:18:49.090> disk 00:18:50.039 --> 00:18:50.049 align:start position:0% I always make in a theorem 1.0 it's disk 00:18:50.049 --> 00:18:53.730 align:start position:0% I always make in a theorem 1.0 it's disk i/o<00:18:50.290> it's<00:18:51.750> apparently<00:18:52.750> it's<00:18:52.900> debated<00:18:53.620> whether 00:18:53.730 --> 00:18:53.740 align:start position:0% i/o it's apparently it's debated whether 00:18:53.740 --> 00:18:55.049 align:start position:0% i/o it's apparently it's debated whether it's<00:18:53.980> the<00:18:54.130> biggest<00:18:54.429> bottleneck<00:18:54.790> but<00:18:54.940> it's 00:18:55.049 --> 00:18:55.059 align:start position:0% it's the biggest bottleneck but it's 00:18:55.059 --> 00:18:58.860 align:start position:0% it's the biggest bottleneck but it's definitely<00:18:55.200> up<00:18:56.200> there<00:18:56.700> in<00:18:57.700> ECM<00:18:58.000> 2.0<00:18:58.570> if<00:18:58.750> you 00:18:58.860 --> 00:18:58.870 align:start position:0% definitely up there in ECM 2.0 if you 00:18:58.870 --> 00:19:00.840 align:start position:0% definitely up there in ECM 2.0 if you start<00:18:59.110> having<00:18:59.290> stateless<00:19:00.130> clients<00:19:00.669> if<00:19:00.730> you 00:19:00.840 --> 00:19:00.850 align:start position:0% start having stateless clients if you 00:19:00.850 --> 00:19:02.760 align:start position:0% start having stateless clients if you need<00:19:01.419> to<00:19:01.570> get<00:19:01.690> your<00:19:01.870> state<00:19:02.140> from<00:19:02.290> the<00:19:02.410> network 00:19:02.760 --> 00:19:02.770 align:start position:0% need to get your state from the network 00:19:02.770 --> 00:19:05.610 align:start position:0% need to get your state from the network it's<00:19:03.610> not<00:19:03.790> so<00:19:04.059> much<00:19:04.240> this<00:19:04.480> guy<00:19:04.750> oh<00:19:04.780> well<00:19:05.110> altum 00:19:05.610 --> 00:19:05.620 align:start position:0% it's not so much this guy oh well altum 00:19:05.620 --> 00:19:07.620 align:start position:0% it's not so much this guy oh well altum Utley<00:19:05.890> will<00:19:06.130> be<00:19:06.250> this<00:19:06.429> guy<00:19:06.610> oh<00:19:06.640> but<00:19:06.940> it's<00:19:07.360> not 00:19:07.620 --> 00:19:07.630 align:start position:0% Utley will be this guy oh but it's not 00:19:07.630 --> 00:19:10.409 align:start position:0% Utley will be this guy oh but it's not so<00:19:07.929> much<00:19:08.110> this<00:19:08.320> guy<00:19:08.500> has<00:19:08.770> network<00:19:09.330> latency<00:19:10.330> and 00:19:10.409 --> 00:19:10.419 align:start position:0% so much this guy has network latency and 00:19:10.419 --> 00:19:12.539 align:start position:0% so much this guy has network latency and things<00:19:10.600> like<00:19:10.720> that<00:19:10.780> but<00:19:11.440> that<00:19:11.679> means<00:19:11.980> that<00:19:12.280> you 00:19:12.539 --> 00:19:12.549 align:start position:0% things like that but that means that you 00:19:12.549 --> 00:19:15.140 align:start position:0% things like that but that means that you will<00:19:12.610> spend<00:19:13.000> a<00:19:13.150> lot<00:19:13.330> of<00:19:13.360> time<00:19:13.660> waiting<00:19:14.080> for 00:19:15.140 --> 00:19:15.150 align:start position:0% will spend a lot of time waiting for 00:19:15.150 --> 00:19:18.480 align:start position:0% will spend a lot of time waiting for your<00:19:16.150> data<00:19:16.360> to<00:19:16.720> arrive<00:19:17.260> or<00:19:17.500> to<00:19:17.830> be<00:19:17.950> written<00:19:18.309> and 00:19:18.480 --> 00:19:18.490 align:start position:0% your data to arrive or to be written and 00:19:18.490 --> 00:19:21.210 align:start position:0% your data to arrive or to be written and as<00:19:18.850> a<00:19:18.880> result<00:19:19.330> this<00:19:19.990> is<00:19:20.049> this<00:19:20.710> really<00:19:21.010> makes 00:19:21.210 --> 00:19:21.220 align:start position:0% as a result this is this really makes 00:19:21.220 --> 00:19:24.330 align:start position:0% as a result this is this really makes sense<00:19:21.400> to<00:19:21.669> try<00:19:21.970> to<00:19:22.030> get<00:19:22.990> the<00:19:23.350> the<00:19:23.799> computer<00:19:24.190> or 00:19:24.330 --> 00:19:24.340 align:start position:0% sense to try to get the the computer or 00:19:24.340 --> 00:19:26.909 align:start position:0% sense to try to get the the computer or the<00:19:24.580> the<00:19:25.270> miner<00:19:25.480> to<00:19:25.750> do<00:19:25.870> something<00:19:26.320> while<00:19:26.770> this 00:19:26.909 --> 00:19:26.919 align:start position:0% the the miner to do something while this 00:19:26.919 --> 00:19:30.570 align:start position:0% the the miner to do something while this is<00:19:27.070> happening<00:19:27.190> so<00:19:27.870> what<00:19:28.919> we<00:19:29.919> want<00:19:30.100> to<00:19:30.160> do<00:19:30.340> with 00:19:30.570 --> 00:19:30.580 align:start position:0% is happening so what we want to do with 00:19:30.580 --> 00:19:32.159 align:start position:0% is happening so what we want to do with this<00:19:30.760> with<00:19:31.030> this<00:19:31.210> work<00:19:31.419> like<00:19:31.750> that<00:19:31.960> was<00:19:32.080> the 00:19:32.159 --> 00:19:32.169 align:start position:0% this with this work like that was the 00:19:32.169 --> 00:19:33.690 align:start position:0% this with this work like that was the preliminary<00:19:32.650> research<00:19:32.890> work<00:19:33.250> what<00:19:33.460> we<00:19:33.549> want 00:19:33.690 --> 00:19:33.700 align:start position:0% preliminary research work what we want 00:19:33.700 --> 00:19:37.230 align:start position:0% preliminary research work what we want to<00:19:33.790> do<00:19:33.940> is<00:19:34.150> to<00:19:34.870> is<00:19:35.500> to<00:19:35.799> increase<00:19:36.250> story<00:19:37.120> to 00:19:37.230 --> 00:19:37.240 align:start position:0% to do is to is to increase story to 00:19:37.240 --> 00:19:39.750 align:start position:0% to do is to is to increase story to extend<00:19:37.929> the<00:19:38.409> definition<00:19:38.650> the<00:19:39.220> definition<00:19:39.340> of 00:19:39.750 --> 00:19:39.760 align:start position:0% extend the definition the definition of 00:19:39.760 --> 00:19:41.610 align:start position:0% extend the definition the definition of independent<00:19:40.299> independence<00:19:41.260> between 00:19:41.610 --> 00:19:41.620 align:start position:0% independent independence between 00:19:41.620 --> 00:19:42.749 align:start position:0% independent independence between transactions<00:19:42.190> do 00:19:42.749 --> 00:19:42.759 align:start position:0% transactions do 00:19:42.759 --> 00:19:45.259 align:start position:0% transactions do you<00:19:42.820> want<00:19:43.059> for<00:19:43.419> example<00:19:43.449> imagine<00:19:44.019> you<00:19:44.229> have 00:19:45.259 --> 00:19:45.269 align:start position:0% you want for example imagine you have 00:19:45.269 --> 00:19:49.349 align:start position:0% you want for example imagine you have like<00:19:46.739> let's<00:19:47.739> say<00:19:47.949> an<00:19:48.099> IC<00:19:48.399> or<00:19:48.519> a<00:19:48.759> crypto<00:19:49.149> Kitty 00:19:49.349 --> 00:19:49.359 align:start position:0% like let's say an IC or a crypto Kitty 00:19:49.359 --> 00:19:52.619 align:start position:0% like let's say an IC or a crypto Kitty kind<00:19:49.659> of<00:19:49.779> kind<00:19:50.739> of<00:19:51.179> profile<00:19:52.179> where<00:19:52.389> a<00:19:52.419> lot<00:19:52.599> of 00:19:52.619 --> 00:19:52.629 align:start position:0% kind of kind of profile where a lot of 00:19:52.629 --> 00:19:54.869 align:start position:0% kind of kind of profile where a lot of transactions<00:19:53.229> correspond<00:19:53.829> to<00:19:53.919> the<00:19:54.190> to<00:19:54.759> the 00:19:54.869 --> 00:19:54.879 align:start position:0% transactions correspond to the to the 00:19:54.879 --> 00:19:58.639 align:start position:0% transactions correspond to the to the same<00:19:55.379> into<00:19:56.379> the<00:19:56.499> same<00:19:56.739> contract<00:19:57.159> can<00:19:58.149> you<00:19:58.299> also 00:19:58.639 --> 00:19:58.649 align:start position:0% same into the same contract can you also 00:19:58.649 --> 00:20:01.859 align:start position:0% same into the same contract can you also generalize<00:19:59.649> the<00:19:59.949> independence<00:20:00.519> to<00:20:00.629> two<00:20:01.629> cause 00:20:01.859 --> 00:20:01.869 align:start position:0% generalize the independence to two cause 00:20:01.869 --> 00:20:04.109 align:start position:0% generalize the independence to two cause within<00:20:02.139> the<00:20:02.349> same<00:20:02.529> contract<00:20:03.009> can<00:20:03.609> you<00:20:03.759> for 00:20:04.109 --> 00:20:04.119 align:start position:0% within the same contract can you for 00:20:04.119 --> 00:20:08.279 align:start position:0% within the same contract can you for example<00:20:04.329> use<00:20:04.599> something<00:20:05.079> like<00:20:06.690> SIMD<00:20:07.690> or<00:20:07.989> you 00:20:08.279 --> 00:20:08.289 align:start position:0% example use something like SIMD or you 00:20:08.289 --> 00:20:11.569 align:start position:0% example use something like SIMD or you know<00:20:08.379> some<00:20:08.679> MapReduce<00:20:09.249> kind<00:20:09.519> of<00:20:09.669> kind<00:20:10.659> of 00:20:11.569 --> 00:20:11.579 align:start position:0% know some MapReduce kind of kind of 00:20:11.579 --> 00:20:14.189 align:start position:0% know some MapReduce kind of kind of programming<00:20:12.579> paradigm<00:20:13.299> so<00:20:13.690> that<00:20:13.839> you<00:20:13.989> can 00:20:14.189 --> 00:20:14.199 align:start position:0% programming paradigm so that you can 00:20:14.199 --> 00:20:16.769 align:start position:0% programming paradigm so that you can make<00:20:14.529> sure<00:20:14.559> that<00:20:14.919> every<00:20:15.309> single<00:20:15.519> thread<00:20:16.419> or 00:20:16.769 --> 00:20:16.779 align:start position:0% make sure that every single thread or 00:20:16.779 --> 00:20:18.269 align:start position:0% make sure that every single thread or every<00:20:17.019> single<00:20:17.229> transaction<00:20:17.709> touches<00:20:18.249> a 00:20:18.269 --> 00:20:18.279 align:start position:0% every single transaction touches a 00:20:18.279 --> 00:20:21.180 align:start position:0% every single transaction touches a different<00:20:18.789> area<00:20:19.419> of<00:20:19.449> the<00:20:19.539> state<00:20:19.899> and<00:20:20.139> run<00:20:20.979> them 00:20:21.180 --> 00:20:21.190 align:start position:0% different area of the state and run them 00:20:21.190 --> 00:20:23.219 align:start position:0% different area of the state and run them concurrently<00:20:21.759> knowing<00:20:22.359> that<00:20:22.569> they<00:20:23.079> won't 00:20:23.219 --> 00:20:23.229 align:start position:0% concurrently knowing that they won't 00:20:23.229 --> 00:20:25.499 align:start position:0% concurrently knowing that they won't they<00:20:23.589> wanted<00:20:23.859> to<00:20:23.979> hear<00:20:24.219> so<00:20:24.999> that<00:20:25.149> yeah<00:20:25.269> that's 00:20:25.499 --> 00:20:25.509 align:start position:0% they wanted to hear so that yeah that's 00:20:25.509 --> 00:20:28.349 align:start position:0% they wanted to hear so that yeah that's that's<00:20:26.079> what<00:20:26.229> we're<00:20:26.499> looking<00:20:27.039> into<00:20:27.209> we<00:20:28.209> also 00:20:28.349 --> 00:20:28.359 align:start position:0% that's what we're looking into we also 00:20:28.359 --> 00:20:31.769 align:start position:0% that's what we're looking into we also want<00:20:28.719> to<00:20:28.809> look<00:20:29.019> into<00:20:29.319> other<00:20:29.759> other<00:20:30.759> ideas<00:20:31.569> for 00:20:31.769 --> 00:20:31.779 align:start position:0% want to look into other other ideas for 00:20:31.779 --> 00:20:34.289 align:start position:0% want to look into other other ideas for example<00:20:32.169> gas<00:20:32.469> calculation<00:20:33.190> so<00:20:33.429> you<00:20:34.149> heard 00:20:34.289 --> 00:20:34.299 align:start position:0% example gas calculation so you heard 00:20:34.299 --> 00:20:36.839 align:start position:0% example gas calculation so you heard before<00:20:34.569> about<00:20:35.319> the<00:20:36.099> metering<00:20:36.489> or<00:20:36.729> the 00:20:36.839 --> 00:20:36.849 align:start position:0% before about the metering or the 00:20:36.849 --> 00:20:38.309 align:start position:0% before about the metering or the Sentinel<00:20:37.269> contract<00:20:37.779> something<00:20:37.959> that<00:20:38.199> will 00:20:38.309 --> 00:20:38.319 align:start position:0% Sentinel contract something that will 00:20:38.319 --> 00:20:41.729 align:start position:0% Sentinel contract something that will scan<00:20:38.679> your<00:20:38.859> contract<00:20:39.399> and<00:20:39.609> add<00:20:39.729> calls<00:20:40.239> just<00:20:40.989> to 00:20:41.729 --> 00:20:41.739 align:start position:0% scan your contract and add calls just to 00:20:41.739 --> 00:20:43.889 align:start position:0% scan your contract and add calls just to use<00:20:41.979> gas<00:20:42.249> to<00:20:42.669> make<00:20:42.819> sure<00:20:42.999> that<00:20:43.149> gas<00:20:43.659> get 00:20:43.889 --> 00:20:43.899 align:start position:0% use gas to make sure that gas get 00:20:43.899 --> 00:20:46.619 align:start position:0% use gas to make sure that gas get properly<00:20:44.409> accounted<00:20:45.249> for<00:20:45.389> what<00:20:46.389> we<00:20:46.479> would 00:20:46.619 --> 00:20:46.629 align:start position:0% properly accounted for what we would 00:20:46.629 --> 00:20:49.019 align:start position:0% properly accounted for what we would like<00:20:46.749> to<00:20:46.899> do<00:20:47.049> maybe<00:20:47.259> is<00:20:47.499> like<00:20:47.639> to<00:20:48.639> see<00:20:48.879> if<00:20:48.999> we 00:20:49.019 --> 00:20:49.029 align:start position:0% like to do maybe is like to see if we 00:20:49.029 --> 00:20:51.269 align:start position:0% like to do maybe is like to see if we can<00:20:49.299> explore<00:20:49.889> what<00:20:50.889> we<00:20:51.039> would<00:20:51.129> like<00:20:51.219> to 00:20:51.269 --> 00:20:51.279 align:start position:0% can explore what we would like to 00:20:51.279 --> 00:20:53.489 align:start position:0% can explore what we would like to explore<00:20:51.699> possibilities<00:20:52.179> to<00:20:52.690> actually<00:20:53.139> pre 00:20:53.489 --> 00:20:53.499 align:start position:0% explore possibilities to actually pre 00:20:53.499 --> 00:20:55.769 align:start position:0% explore possibilities to actually pre meter<00:20:53.769> the<00:20:53.979> contract<00:20:54.369> so<00:20:54.459> reduce<00:20:55.149> the<00:20:55.389> need<00:20:55.569> to 00:20:55.769 --> 00:20:55.779 align:start position:0% meter the contract so reduce the need to 00:20:55.779 --> 00:20:58.680 align:start position:0% meter the contract so reduce the need to do<00:20:56.139> this<00:20:56.319> because<00:20:56.949> first<00:20:57.909> you<00:20:58.059> have<00:20:58.179> to<00:20:58.329> scan 00:20:58.680 --> 00:20:58.690 align:start position:0% do this because first you have to scan 00:20:58.690 --> 00:21:01.019 align:start position:0% do this because first you have to scan the<00:20:59.139> contract<00:20:59.589> but<00:20:59.709> then<00:20:59.919> every<00:21:00.669> time<00:21:00.849> you 00:21:01.019 --> 00:21:01.029 align:start position:0% the contract but then every time you 00:21:01.029 --> 00:21:04.199 align:start position:0% the contract but then every time you have<00:21:01.179> to<00:21:01.299> make<00:21:01.449> a<00:21:01.479> call<00:21:01.839> and<00:21:02.219> that's<00:21:03.219> kind<00:21:04.149> of 00:21:04.199 --> 00:21:04.209 align:start position:0% have to make a call and that's kind of 00:21:04.209 --> 00:21:06.809 align:start position:0% have to make a call and that's kind of inefficient<00:21:04.809> so<00:21:05.769> we<00:21:05.919> want<00:21:06.219> to<00:21:06.309> see<00:21:06.489> if<00:21:06.579> we<00:21:06.639> can 00:21:06.809 --> 00:21:06.819 align:start position:0% inefficient so we want to see if we can 00:21:06.819 --> 00:21:09.839 align:start position:0% inefficient so we want to see if we can just<00:21:06.999> have<00:21:07.299> a<00:21:07.359> simple<00:21:07.989> gas<00:21:08.979> rule<00:21:09.279> see<00:21:09.609> if<00:21:09.699> we 00:21:09.839 --> 00:21:09.849 align:start position:0% just have a simple gas rule see if we 00:21:09.849 --> 00:21:13.079 align:start position:0% just have a simple gas rule see if we can<00:21:10.059> have<00:21:10.509> an<00:21:11.109> upper<00:21:11.739> bound<00:21:11.919> or<00:21:12.190> a<00:21:12.249> formula<00:21:12.819> we 00:21:13.079 --> 00:21:13.089 align:start position:0% can have an upper bound or a formula we 00:21:13.089 --> 00:21:15.629 align:start position:0% can have an upper bound or a formula we just<00:21:13.359> look<00:21:13.509> at<00:21:13.690> at<00:21:14.440> your<00:21:14.649> binary<00:21:14.859> we<00:21:15.249> say<00:21:15.429> okay 00:21:15.629 --> 00:21:15.639 align:start position:0% just look at at your binary we say okay 00:21:15.639 --> 00:21:17.279 align:start position:0% just look at at your binary we say okay this<00:21:15.759> is<00:21:15.909> roughly<00:21:16.239> what<00:21:16.299> it's<00:21:16.539> gonna<00:21:16.629> cost<00:21:16.899> and 00:21:17.279 --> 00:21:17.289 align:start position:0% this is roughly what it's gonna cost and 00:21:17.289 --> 00:21:20.669 align:start position:0% this is roughly what it's gonna cost and charge<00:21:17.529> that<00:21:18.299> we<00:21:19.299> one<00:21:19.719> of<00:21:19.749> the<00:21:19.839> interesting 00:21:20.669 --> 00:21:20.679 align:start position:0% charge that we one of the interesting 00:21:20.679 --> 00:21:23.819 align:start position:0% charge that we one of the interesting things<00:21:20.919> that<00:21:21.009> really<00:21:22.079> where<00:21:23.079> wisdom<00:21:23.469> really 00:21:23.819 --> 00:21:23.829 align:start position:0% things that really where wisdom really 00:21:23.829 --> 00:21:25.979 align:start position:0% things that really where wisdom really brings<00:21:24.069> a<00:21:24.190> benefit<00:21:24.669> it's<00:21:25.119> the<00:21:25.449> replace 00:21:25.979 --> 00:21:25.989 align:start position:0% brings a benefit it's the replace 00:21:25.989 --> 00:21:28.289 align:start position:0% brings a benefit it's the replace contracts<00:21:26.589> contracts<00:21:27.399> call<00:21:27.699> with<00:21:27.909> function 00:21:28.289 --> 00:21:28.299 align:start position:0% contracts contracts call with function 00:21:28.299 --> 00:21:30.869 align:start position:0% contracts contracts call with function calls<00:21:28.769> so<00:21:29.769> right<00:21:29.949> now<00:21:30.099> when<00:21:30.309> you<00:21:30.399> call<00:21:30.639> a 00:21:30.869 --> 00:21:30.879 align:start position:0% calls so right now when you call a 00:21:30.879 --> 00:21:33.509 align:start position:0% calls so right now when you call a contract<00:21:31.479> you<00:21:31.719> have<00:21:31.899> to<00:21:32.109> reinstate<00:21:32.889> a<00:21:33.190> lot<00:21:33.399> of 00:21:33.509 --> 00:21:33.519 align:start position:0% contract you have to reinstate a lot of 00:21:33.519 --> 00:21:35.339 align:start position:0% contract you have to reinstate a lot of things<00:21:33.759> like<00:21:33.909> you<00:21:34.029> basically<00:21:34.419> I'm<00:21:35.079> talking 00:21:35.339 --> 00:21:35.349 align:start position:0% things like you basically I'm talking 00:21:35.349 --> 00:21:38.489 align:start position:0% things like you basically I'm talking about<00:21:35.529> yes<00:21:35.709> you<00:21:36.549> create<00:21:37.109> pretty<00:21:38.109> much<00:21:38.289> a<00:21:38.319> new 00:21:38.489 --> 00:21:38.499 align:start position:0% about yes you create pretty much a new 00:21:38.499 --> 00:21:40.709 align:start position:0% about yes you create pretty much a new VM<00:21:38.829> a<00:21:39.039> lot<00:21:39.249> of<00:21:39.369> data<00:21:39.759> structures<00:21:40.209> but 00:21:40.709 --> 00:21:40.719 align:start position:0% VM a lot of data structures but 00:21:40.719 --> 00:21:43.229 align:start position:0% VM a lot of data structures but ultimately<00:21:41.619> this<00:21:42.009> is<00:21:42.159> what<00:21:42.759> you<00:21:42.879> want<00:21:43.059> to<00:21:43.149> do 00:21:43.229 --> 00:21:43.239 align:start position:0% ultimately this is what you want to do 00:21:43.239 --> 00:21:45.059 align:start position:0% ultimately this is what you want to do is<00:21:43.419> is<00:21:43.929> a<00:21:44.199> function<00:21:44.679> call<00:21:44.859> you're<00:21:45.039> not 00:21:45.059 --> 00:21:45.069 align:start position:0% is is a function call you're not 00:21:45.069 --> 00:21:46.919 align:start position:0% is is a function call you're not actually<00:21:45.699> calling<00:21:45.969> a<00:21:46.239> contract<00:21:46.749> on<00:21:46.839> a 00:21:46.919 --> 00:21:46.929 align:start position:0% actually calling a contract on a 00:21:46.929 --> 00:21:48.599 align:start position:0% actually calling a contract on a different<00:21:47.319> computer<00:21:48.009> you're<00:21:48.309> coming 00:21:48.599 --> 00:21:48.609 align:start position:0% different computer you're coming 00:21:48.609 --> 00:21:50.789 align:start position:0% different computer you're coming something<00:21:49.239> on<00:21:49.359> the<00:21:49.449> same<00:21:49.599> computer<00:21:49.839> so<00:21:50.589> why 00:21:50.789 --> 00:21:50.799 align:start position:0% something on the same computer so why 00:21:50.799 --> 00:21:54.419 align:start position:0% something on the same computer so why not<00:21:50.979> make<00:21:51.190> it<00:21:51.249> a<00:21:51.609> function<00:21:52.389> call<00:21:52.769> so<00:21:53.769> you<00:21:54.249> would 00:21:54.419 --> 00:21:54.429 align:start position:0% not make it a function call so you would 00:21:54.429 --> 00:21:56.759 align:start position:0% not make it a function call so you would have<00:21:54.729> something<00:21:55.479> like<00:21:55.959> imp 00:21:56.759 --> 00:21:56.769 align:start position:0% have something like imp 00:21:56.769 --> 00:21:59.539 align:start position:0% have something like imp you<00:21:57.129> know<00:21:57.249> like<00:21:57.399> pseudocode<00:21:58.119> or<00:21:58.330> sudo<00:21:59.289> python 00:21:59.539 --> 00:21:59.549 align:start position:0% you know like pseudocode or sudo python 00:21:59.549 --> 00:22:02.940 align:start position:0% you know like pseudocode or sudo python import<00:22:00.549> that<00:22:01.090> function<00:22:01.570> from<00:22:01.929> a<00:22:02.259> contract 00:22:02.940 --> 00:22:02.950 align:start position:0% import that function from a contract 00:22:02.950 --> 00:22:05.430 align:start position:0% import that function from a contract address<00:22:03.309> and<00:22:03.580> just<00:22:04.240> get<00:22:04.779> everything<00:22:05.080> loaded 00:22:05.430 --> 00:22:05.440 align:start position:0% address and just get everything loaded 00:22:05.440 --> 00:22:07.320 align:start position:0% address and just get everything loaded and<00:22:05.769> you<00:22:05.830> can<00:22:06.009> start<00:22:06.249> doing<00:22:06.399> lots<00:22:06.940> of<00:22:07.059> things 00:22:07.320 --> 00:22:07.330 align:start position:0% and you can start doing lots of things 00:22:07.330 --> 00:22:11.009 align:start position:0% and you can start doing lots of things that<00:22:08.110> get<00:22:09.039> inspired<00:22:09.369> by<00:22:09.549> operating<00:22:10.539> systems 00:22:11.009 --> 00:22:11.019 align:start position:0% that get inspired by operating systems 00:22:11.019 --> 00:22:13.470 align:start position:0% that get inspired by operating systems like<00:22:11.259> you<00:22:11.740> know<00:22:11.889> manage<00:22:12.549> modules<00:22:13.029> like<00:22:13.240> you 00:22:13.470 --> 00:22:13.480 align:start position:0% like you know manage modules like you 00:22:13.480 --> 00:22:15.299 align:start position:0% like you know manage modules like you like<00:22:13.840> operating<00:22:14.230> systems<00:22:14.590> manage<00:22:14.889> libraries 00:22:15.299 --> 00:22:15.309 align:start position:0% like operating systems manage libraries 00:22:15.309 --> 00:22:16.889 align:start position:0% like operating systems manage libraries if<00:22:15.549> you<00:22:15.730> see<00:22:15.940> that<00:22:16.059> a<00:22:16.090> module<00:22:16.299> gets<00:22:16.600> loaded 00:22:16.889 --> 00:22:16.899 align:start position:0% if you see that a module gets loaded 00:22:16.899 --> 00:22:18.869 align:start position:0% if you see that a module gets loaded very<00:22:17.289> often<00:22:17.710> you<00:22:18.039> just<00:22:18.070> leave<00:22:18.460> it<00:22:18.580> in<00:22:18.669> memory 00:22:18.869 --> 00:22:18.879 align:start position:0% very often you just leave it in memory 00:22:18.879 --> 00:22:22.289 align:start position:0% very often you just leave it in memory so<00:22:19.149> that<00:22:19.179> when<00:22:19.480> you<00:22:19.570> load<00:22:19.779> it<00:22:19.990> you<00:22:21.299> it's 00:22:22.289 --> 00:22:22.299 align:start position:0% so that when you load it you it's 00:22:22.299 --> 00:22:25.369 align:start position:0% so that when you load it you it's already<00:22:22.539> there<00:22:22.840> you<00:22:23.830> can<00:22:24.009> do<00:22:24.220> something 00:22:25.369 --> 00:22:25.379 align:start position:0% already there you can do something 00:22:25.379 --> 00:22:28.019 align:start position:0% already there you can do something require<00:22:26.379> modules<00:22:26.860> to<00:22:26.980> have<00:22:27.129> the<00:22:27.340> full<00:22:27.639> list<00:22:27.879> of 00:22:28.019 --> 00:22:28.029 align:start position:0% require modules to have the full list of 00:22:28.029 --> 00:22:30.119 align:start position:0% require modules to have the full list of contracts<00:22:28.539> to<00:22:28.649> basically<00:22:29.649> like<00:22:29.830> you<00:22:29.950> had 00:22:30.119 --> 00:22:30.129 align:start position:0% contracts to basically like you had 00:22:30.129 --> 00:22:32.909 align:start position:0% contracts to basically like you had access<00:22:30.369> lists<00:22:30.879> for<00:22:31.330> state<00:22:32.259> locations<00:22:32.769> you 00:22:32.909 --> 00:22:32.919 align:start position:0% access lists for state locations you 00:22:32.919 --> 00:22:34.950 align:start position:0% access lists for state locations you could<00:22:33.100> also<00:22:33.580> enforce<00:22:34.389> the<00:22:34.509> same<00:22:34.629> thing<00:22:34.840> for 00:22:34.950 --> 00:22:34.960 align:start position:0% could also enforce the same thing for 00:22:34.960 --> 00:22:38.340 align:start position:0% could also enforce the same thing for modules<00:22:36.119> we<00:22:37.119> also<00:22:37.299> get<00:22:37.720> inspired<00:22:37.960> by<00:22:38.289> two 00:22:38.340 --> 00:22:38.350 align:start position:0% modules we also get inspired by two 00:22:38.350 --> 00:22:42.799 align:start position:0% modules we also get inspired by two turbojet<00:22:39.309> unfortunately<00:22:40.470> the<00:22:41.470> two<00:22:42.100> bogus 00:22:42.799 --> 00:22:42.809 align:start position:0% turbojet unfortunately the two bogus 00:22:42.809 --> 00:22:45.960 align:start position:0% turbojet unfortunately the two bogus presentation<00:22:43.809> was<00:22:43.990> at<00:22:44.860> the<00:22:45.039> concurrent<00:22:45.759> time 00:22:45.960 --> 00:22:45.970 align:start position:0% presentation was at the concurrent time 00:22:45.970 --> 00:22:47.879 align:start position:0% presentation was at the concurrent time in<00:22:46.119> in<00:22:46.480> a<00:22:46.600> different<00:22:46.960> room 00:22:47.879 --> 00:22:47.889 align:start position:0% in in a different room 00:22:47.889 --> 00:22:51.899 align:start position:0% in in a different room but<00:22:48.460> yes<00:22:49.149> so<00:22:49.389> they<00:22:49.690> try<00:22:50.200> to<00:22:50.230> replace<00:22:50.769> all<00:22:51.129> the 00:22:51.899 --> 00:22:51.909 align:start position:0% but yes so they try to replace all the 00:22:51.909 --> 00:22:53.940 align:start position:0% but yes so they try to replace all the state<00:22:52.450> try<00:22:52.720> or<00:22:52.929> at<00:22:53.019> least<00:22:53.230> try<00:22:53.379> to<00:22:53.409> optimize 00:22:53.940 --> 00:22:53.950 align:start position:0% state try or at least try to optimize 00:22:53.950 --> 00:22:55.799 align:start position:0% state try or at least try to optimize the<00:22:54.249> way<00:22:54.399> it<00:22:54.549> stored<00:22:54.909> the<00:22:55.119> weight<00:22:55.299> success 00:22:55.799 --> 00:22:55.809 align:start position:0% the way it stored the weight success 00:22:55.809 --> 00:22:59.909 align:start position:0% the way it stored the weight success maybe<00:22:56.470> that's<00:22:56.980> still<00:22:57.070> a<00:22:57.840> suggestion<00:22:58.840> from<00:22:59.019> the 00:22:59.909 --> 00:22:59.919 align:start position:0% maybe that's still a suggestion from the 00:22:59.919 --> 00:23:02.129 align:start position:0% maybe that's still a suggestion from the name<00:23:00.070> escapes<00:23:00.220> me<00:23:00.519> Alex<00:23:01.419> there<00:23:01.600> at<00:23:01.779> least<00:23:01.899> say 00:23:02.129 --> 00:23:02.139 align:start position:0% name escapes me Alex there at least say 00:23:02.139 --> 00:23:05.879 align:start position:0% name escapes me Alex there at least say thank<00:23:02.409> you<00:23:02.559> mark<00:23:03.009> a<00:23:03.389> very<00:23:04.389> smart<00:23:04.570> guy<00:23:04.860> how<00:23:05.860> to 00:23:05.879 --> 00:23:05.889 align:start position:0% thank you mark a very smart guy how to 00:23:05.889 --> 00:23:08.730 align:start position:0% thank you mark a very smart guy how to maybe<00:23:06.610> have<00:23:07.059> all<00:23:07.570> those<00:23:07.869> contrasts<00:23:08.440> all<00:23:08.559> those 00:23:08.730 --> 00:23:08.740 align:start position:0% maybe have all those contrasts all those 00:23:08.740 --> 00:23:12.149 align:start position:0% maybe have all those contrasts all those states<00:23:09.070> in<00:23:09.249> a<00:23:09.960> like<00:23:10.960> linear<00:23:11.289> contiguous<00:23:12.039> space 00:23:12.149 --> 00:23:12.159 align:start position:0% states in a like linear contiguous space 00:23:12.159 --> 00:23:15.840 align:start position:0% states in a like linear contiguous space why<00:23:12.639> not<00:23:12.879> with<00:23:13.269> protection<00:23:13.869> of<00:23:14.110> course<00:23:14.850> yes 00:23:15.840 --> 00:23:15.850 align:start position:0% why not with protection of course yes 00:23:15.850 --> 00:23:19.859 align:start position:0% why not with protection of course yes and<00:23:16.119> we<00:23:16.779> also<00:23:16.929> want<00:23:17.409> to<00:23:17.999> use<00:23:18.999> some<00:23:19.240> of<00:23:19.389> the 00:23:19.859 --> 00:23:19.869 align:start position:0% and we also want to use some of the 00:23:19.869 --> 00:23:21.720 align:start position:0% and we also want to use some of the features<00:23:20.049> of<00:23:20.259> wisdom<00:23:20.740> that<00:23:20.919> are<00:23:21.070> on<00:23:21.309> the 00:23:21.720 --> 00:23:21.730 align:start position:0% features of wisdom that are on the 00:23:21.730 --> 00:23:24.169 align:start position:0% features of wisdom that are on the roadmap<00:23:21.940> they<00:23:22.299> are<00:23:22.360> not<00:23:22.539> they<00:23:23.080> haven't<00:23:23.259> been 00:23:24.169 --> 00:23:24.179 align:start position:0% roadmap they are not they haven't been 00:23:24.179 --> 00:23:26.820 align:start position:0% roadmap they are not they haven't been released<00:23:25.179> yet<00:23:25.509> or<00:23:25.779> at<00:23:25.899> least<00:23:26.110> not<00:23:26.259> officially 00:23:26.820 --> 00:23:26.830 align:start position:0% released yet or at least not officially 00:23:26.830 --> 00:23:29.519 align:start position:0% released yet or at least not officially agreed<00:23:27.129> on<00:23:27.429> yet<00:23:27.730> but<00:23:27.970> you<00:23:28.149> have<00:23:28.350> mutexes<00:23:29.350> you 00:23:29.519 --> 00:23:29.529 align:start position:0% agreed on yet but you have mutexes you 00:23:29.529 --> 00:23:31.590 align:start position:0% agreed on yet but you have mutexes you have<00:23:29.679> SIMD<00:23:30.549> so<00:23:30.970> for<00:23:31.119> those<00:23:31.269> who<00:23:31.389> don't<00:23:31.570> know 00:23:31.590 --> 00:23:31.600 align:start position:0% have SIMD so for those who don't know 00:23:31.600 --> 00:23:34.080 align:start position:0% have SIMD so for those who don't know SIMD<00:23:32.259> is<00:23:32.440> a<00:23:32.889> single<00:23:33.610> instruction<00:23:33.909> multiple 00:23:34.080 --> 00:23:34.090 align:start position:0% SIMD is a single instruction multiple 00:23:34.090 --> 00:23:37.379 align:start position:0% SIMD is a single instruction multiple data<00:23:34.960> so<00:23:35.470> the<00:23:35.619> processor<00:23:36.309> has<00:23:37.179> one 00:23:37.379 --> 00:23:37.389 align:start position:0% data so the processor has one 00:23:37.389 --> 00:23:40.019 align:start position:0% data so the processor has one instruction<00:23:37.960> that<00:23:38.669> does<00:23:39.669> the<00:23:39.820> same<00:23:39.850> thing 00:23:40.019 --> 00:23:40.029 align:start position:0% instruction that does the same thing 00:23:40.029 --> 00:23:42.810 align:start position:0% instruction that does the same thing several<00:23:40.600> times<00:23:41.009> it<00:23:42.009> uses<00:23:42.369> the<00:23:42.460> parallelism 00:23:42.810 --> 00:23:42.820 align:start position:0% several times it uses the parallelism 00:23:42.820 --> 00:23:45.570 align:start position:0% several times it uses the parallelism that<00:23:43.210> is<00:23:43.480> inside<00:23:43.899> the<00:23:44.110> processor<00:23:44.799> and<00:23:45.129> yeah 00:23:45.570 --> 00:23:45.580 align:start position:0% that is inside the processor and yeah 00:23:45.580 --> 00:23:47.860 align:start position:0% that is inside the processor and yeah that's<00:23:46.029> what<00:23:46.179> we're<00:23:46.330> and<00:23:46.509> we're<00:23:46.629> looking<00:23:46.899> into 00:23:47.860 --> 00:23:47.870 align:start position:0% that's what we're and we're looking into 00:23:47.870 --> 00:23:56.120 align:start position:0% that's what we're and we're looking into [Music] 00:23:56.120 --> 00:23:56.130 align:start position:0% 00:23:56.130 --> 00:24:00.779 align:start position:0% [Applause] 00:24:00.779 --> 00:24:00.789 align:start position:0% [Applause] 00:24:00.789 --> 00:24:04.149 align:start position:0% [Applause] Thank<00:24:01.789> You<00:24:01.970> Kim<00:24:02.510> and<00:24:02.899> Paul<00:24:03.590> there<00:24:03.799> was<00:24:03.950> really 00:24:04.149 --> 00:24:04.159 align:start position:0% Thank You Kim and Paul there was really 00:24:04.159 --> 00:24:13.450 align:start position:0% Thank You Kim and Paul there was really intense<00:24:04.490> big<00:24:05.360> applause<00:24:05.659> again<00:24:05.990> for<00:24:06.169> them<00:24:12.460> one 00:24:13.450 --> 00:24:13.460 align:start position:0% intense big applause again for them one 00:24:13.460 --> 00:24:16.509 align:start position:0% intense big applause again for them one addition<00:24:14.029> to<00:24:14.059> all<00:24:14.299> of<00:24:14.419> this<00:24:14.600> is<00:24:15.490> we<00:24:16.490> are 00:24:16.509 --> 00:24:16.519 align:start position:0% addition to all of this is we are 00:24:16.519 --> 00:24:17.740 align:start position:0% addition to all of this is we are considering<00:24:17.000> all<00:24:17.210> these<00:24:17.360> different 00:24:17.740 --> 00:24:17.750 align:start position:0% considering all these different 00:24:17.750 --> 00:24:19.600 align:start position:0% considering all these different improvements<00:24:18.409> and<00:24:18.620> we're<00:24:19.100> lucky<00:24:19.309> if<00:24:19.460> you're 00:24:19.600 --> 00:24:19.610 align:start position:0% improvements and we're lucky if you're 00:24:19.610 --> 00:24:21.250 align:start position:0% improvements and we're lucky if you're in<00:24:19.730> a<00:24:19.760> really<00:24:19.970> lucky<00:24:20.149> position<00:24:20.390> that<00:24:20.840> we<00:24:20.990> can 00:24:21.250 --> 00:24:21.260 align:start position:0% in a really lucky position that we can 00:24:21.260 --> 00:24:23.169 align:start position:0% in a really lucky position that we can consider<00:24:21.710> adding<00:24:22.279> these<00:24:22.580> improvements<00:24:22.909> today 00:24:23.169 --> 00:24:23.179 align:start position:0% consider adding these improvements today 00:24:23.179 --> 00:24:25.419 align:start position:0% consider adding these improvements today wasn't<00:24:23.630> test<00:24:23.809> net<00:24:24.019> or<00:24:24.350> spinning<00:24:24.860> up<00:24:24.980> a<00:24:25.070> new<00:24:25.250> it 00:24:25.419 --> 00:24:25.429 align:start position:0% wasn't test net or spinning up a new it 00:24:25.429 --> 00:24:27.009 align:start position:0% wasn't test net or spinning up a new it wasn't<00:24:25.730> tested<00:24:26.090> and<00:24:26.299> add<00:24:26.450> these<00:24:26.659> improvements 00:24:27.009 --> 00:24:27.019 align:start position:0% wasn't tested and add these improvements 00:24:27.019 --> 00:24:29.769 align:start position:0% wasn't tested and add these improvements to<00:24:27.320> it<00:24:27.440> but<00:24:28.190> hopefully<00:24:28.549> if<00:24:28.820> we<00:24:29.149> managed<00:24:29.510> to<00:24:29.539> at 00:24:29.769 --> 00:24:29.779 align:start position:0% to it but hopefully if we managed to at 00:24:29.779 --> 00:24:31.480 align:start position:0% to it but hopefully if we managed to at any<00:24:29.899> of<00:24:30.019> these<00:24:30.159> they're<00:24:31.159> going<00:24:31.340> to<00:24:31.399> be<00:24:31.460> a 00:24:31.480 --> 00:24:31.490 align:start position:0% any of these they're going to be a 00:24:31.490 --> 00:24:33.970 align:start position:0% any of these they're going to be a really<00:24:31.639> good<00:24:31.850> test<00:24:32.659> bed<00:24:32.899> to<00:24:32.929> have<00:24:33.289> them<00:24:33.470> fully 00:24:33.970 --> 00:24:33.980 align:start position:0% really good test bed to have them fully 00:24:33.980 --> 00:24:35.889 align:start position:0% really good test bed to have them fully specified<00:24:34.549> and<00:24:34.760> finally<00:24:35.360> implemented<00:24:35.750> in<00:24:35.840> the 00:24:35.889 --> 00:24:35.899 align:start position:0% specified and finally implemented in the 00:24:35.899 --> 00:24:39.850 align:start position:0% specified and finally implemented in the main<00:24:36.049> net<00:24:36.250> now<00:24:37.250> next<00:24:38.210> one<00:24:38.389> on<00:24:38.630> stage<00:24:39.230> is<00:24:39.500> Casey 00:24:39.850 --> 00:24:39.860 align:start position:0% main net now next one on stage is Casey 00:24:39.860 --> 00:24:42.549 align:start position:0% main net now next one on stage is Casey d3o<00:24:40.279> Casey<00:24:41.179> has<00:24:41.450> been<00:24:41.600> around<00:24:41.809> forever<00:24:42.049> he's 00:24:42.549 --> 00:24:42.559 align:start position:0% d3o Casey has been around forever he's 00:24:42.559 --> 00:24:44.860 align:start position:0% d3o Casey has been around forever he's really<00:24:42.830> into<00:24:43.010> research<00:24:43.370> and<00:24:43.580> he's<00:24:44.360> more<00:24:44.510> into 00:24:44.860 --> 00:24:44.870 align:start position:0% really into research and he's more into 00:24:44.870 --> 00:24:46.389 align:start position:0% really into research and he's more into keeping<00:24:45.200> it<00:24:45.320> to<00:24:45.409> him<00:24:45.559> alive<00:24:45.740> and<00:24:45.950> in<00:24:46.130> to 00:24:46.389 --> 00:24:46.399 align:start position:0% keeping it to him alive and in to 00:24:46.399 --> 00:24:48.730 align:start position:0% keeping it to him alive and in to improve<00:24:46.909> etherium<00:24:47.389> and<00:24:47.840> his<00:24:48.260> talk<00:24:48.470> will<00:24:48.710> be 00:24:48.730 --> 00:24:48.740 align:start position:0% improve etherium and his talk will be 00:24:48.740 --> 00:24:51.419 align:start position:0% improve etherium and his talk will be about<00:24:48.860> a<00:24:49.789> new<00:24:50.360> idea<00:24:50.630> how<00:24:50.840> you<00:24:50.899> could<00:24:51.169> do 00:24:51.419 --> 00:24:51.429 align:start position:0% about a new idea how you could do 00:24:51.429 --> 00:24:54.940 align:start position:0% about a new idea how you could do scaling<00:24:52.429> on<00:24:52.730> a<00:24:53.090> much<00:24:53.299> bigger<00:24:53.480> scale<00:24:53.799> and<00:24:54.799> we 00:24:54.940 --> 00:24:54.950 align:start position:0% scaling on a much bigger scale and we 00:24:54.950 --> 00:24:56.590 align:start position:0% scaling on a much bigger scale and we may<00:24:55.070> also<00:24:55.220> consider<00:24:55.580> having<00:24:55.970> this<00:24:56.090> on<00:24:56.299> only 00:24:56.590 --> 00:24:56.600 align:start position:0% may also consider having this on only 00:24:56.600 --> 00:24:58.509 align:start position:0% may also consider having this on only wasn't<00:24:56.899> at<00:24:56.960> some<00:24:57.110> point<00:24:57.350> big<00:24:58.100> applause<00:24:58.399> for 00:24:58.509 --> 00:24:58.519 align:start position:0% wasn't at some point big applause for 00:24:58.519 --> 00:25:07.600 align:start position:0% wasn't at some point big applause for Casey<00:25:03.130> thank<00:25:04.130> you<00:25:04.990> it's<00:25:05.990> not<00:25:06.679> exactly<00:25:07.429> new 00:25:07.600 --> 00:25:07.610 align:start position:0% Casey thank you it's not exactly new 00:25:07.610 --> 00:25:10.750 align:start position:0% Casey thank you it's not exactly new idea<00:25:07.880> it's<00:25:08.029> just<00:25:08.210> a<00:25:08.419> dream<00:25:08.779> 2.0<00:25:09.409> the<00:25:09.760> Jasper 00:25:10.750 --> 00:25:10.760 align:start position:0% idea it's just a dream 2.0 the Jasper 00:25:10.760 --> 00:25:16.899 align:start position:0% idea it's just a dream 2.0 the Jasper serenity<00:25:11.529> research<00:25:13.389> which<00:25:14.389> I<00:25:15.639> heard<00:25:16.639> in<00:25:16.820> the 00:25:16.899 --> 00:25:16.909 align:start position:0% serenity research which I heard in the 00:25:16.909 --> 00:25:19.240 align:start position:0% serenity research which I heard in the news<00:25:17.090> recently<00:25:17.360> that<00:25:17.659> the<00:25:18.529> etherium<00:25:18.860> 2.0 00:25:19.240 --> 00:25:19.250 align:start position:0% news recently that the etherium 2.0 00:25:19.250 --> 00:25:22.570 align:start position:0% news recently that the etherium 2.0 research<00:25:19.610> is<00:25:20.110> stabilizing<00:25:21.580> finally 00:25:22.570 --> 00:25:22.580 align:start position:0% research is stabilizing finally 00:25:22.580 --> 00:25:24.039 align:start position:0% research is stabilizing finally stabilizing<00:25:23.029> which<00:25:23.480> is<00:25:23.630> good<00:25:23.809> to<00:25:23.929> hear 00:25:24.039 --> 00:25:24.049 align:start position:0% stabilizing which is good to hear 00:25:24.049 --> 00:25:27.490 align:start position:0% stabilizing which is good to hear because<00:25:25.419> maybe<00:25:26.419> now<00:25:26.600> we<00:25:26.659> can<00:25:26.779> answer<00:25:27.049> one<00:25:27.470> of 00:25:27.490 --> 00:25:27.500 align:start position:0% because maybe now we can answer one of 00:25:27.500 --> 00:25:31.149 align:start position:0% because maybe now we can answer one of the<00:25:27.620> most<00:25:27.769> basic<00:25:27.950> questions<00:25:29.529> just<00:25:30.529> how<00:25:30.649> do<00:25:30.710> how 00:25:31.149 --> 00:25:31.159 align:start position:0% the most basic questions just how do how 00:25:31.159 --> 00:25:33.430 align:start position:0% the most basic questions just how do how are<00:25:31.820> we<00:25:31.940> going<00:25:32.059> to<00:25:32.120> deal<00:25:32.330> with<00:25:32.360> a<00:25:32.570> large<00:25:33.139> and 00:25:33.430 --> 00:25:33.440 align:start position:0% are we going to deal with a large and 00:25:33.440 --> 00:25:37.350 align:start position:0% are we going to deal with a large and growing<00:25:33.850> account<00:25:34.850> state<00:25:35.179> this<00:25:36.169> is<00:25:36.350> one<00:25:36.529> of<00:25:36.620> the 00:25:37.350 --> 00:25:37.360 align:start position:0% growing account state this is one of the 00:25:37.360 --> 00:25:39.730 align:start position:0% growing account state this is one of the main<00:25:38.360> problems<00:25:38.779> in<00:25:38.899> scaling<00:25:39.169> even<00:25:39.590> if<00:25:39.679> we 00:25:39.730 --> 00:25:39.740 align:start position:0% main problems in scaling even if we 00:25:39.740 --> 00:25:43.180 align:start position:0% main problems in scaling even if we wanted<00:25:39.950> to<00:25:40.010> scale<00:25:40.250> 1.0<00:25:41.830> we<00:25:42.830> would<00:25:42.950> have<00:25:43.070> to 00:25:43.180 --> 00:25:43.190 align:start position:0% wanted to scale 1.0 we would have to 00:25:43.190 --> 00:25:49.040 align:start position:0% wanted to scale 1.0 we would have to deal<00:25:43.399> with<00:25:44.710> the<00:25:45.710> account<00:25:45.980> state 00:25:49.040 --> 00:25:49.050 align:start position:0% 00:25:49.050 --> 00:25:55.720 align:start position:0% [Music] 00:25:55.720 --> 00:25:55.730 align:start position:0% 00:25:55.730 --> 00:25:59.180 align:start position:0% sorry<00:25:56.730> and<00:25:56.910> actually<00:25:57.330> doesn't<00:25:57.480> have<00:25:58.190> really 00:25:59.180 --> 00:25:59.190 align:start position:0% sorry and actually doesn't have really 00:25:59.190 --> 00:26:00.910 align:start position:0% sorry and actually doesn't have really anything<00:25:59.370> to<00:25:59.550> do<00:25:59.670> with<00:25:59.700> you<00:25:59.910> awesome<00:26:00.090> because 00:26:00.910 --> 00:26:00.920 align:start position:0% anything to do with you awesome because 00:26:00.920 --> 00:26:04.760 align:start position:0% anything to do with you awesome because he<00:26:01.920> was<00:26:02.220> them<00:26:02.430> is<00:26:02.630> just<00:26:03.630> an<00:26:03.780> execution<00:26:04.440> engine 00:26:04.760 --> 00:26:04.770 align:start position:0% he was them is just an execution engine 00:26:04.770 --> 00:26:07.790 align:start position:0% he was them is just an execution engine and<00:26:05.360> the<00:26:06.360> execution<00:26:06.930> reads<00:26:07.320> and<00:26:07.500> writes<00:26:07.590> to 00:26:07.790 --> 00:26:07.800 align:start position:0% and the execution reads and writes to 00:26:07.800 --> 00:26:10.850 align:start position:0% and the execution reads and writes to the<00:26:07.920> state<00:26:08.130> so<00:26:09.050> if<00:26:10.050> you<00:26:10.230> want<00:26:10.380> to<00:26:10.440> implement<00:26:10.620> an 00:26:10.850 --> 00:26:10.860 align:start position:0% the state so if you want to implement an 00:26:10.860 --> 00:26:12.170 align:start position:0% the state so if you want to implement an execution<00:26:11.280> engine<00:26:11.520> then<00:26:11.820> you've<00:26:11.940> got<00:26:12.060> to 00:26:12.170 --> 00:26:12.180 align:start position:0% execution engine then you've got to 00:26:12.180 --> 00:26:15.010 align:start position:0% execution engine then you've got to decide<00:26:12.780> how<00:26:13.500> you're<00:26:13.680> gonna<00:26:13.740> handle<00:26:14.070> the<00:26:14.190> state 00:26:15.010 --> 00:26:15.020 align:start position:0% decide how you're gonna handle the state 00:26:15.020 --> 00:26:17.840 align:start position:0% decide how you're gonna handle the state so<00:26:16.020> I<00:26:16.050> guess<00:26:16.260> it<00:26:16.380> kind<00:26:16.530> of<00:26:16.590> falls<00:26:17.310> on<00:26:17.460> us<00:26:17.580> to 00:26:17.840 --> 00:26:17.850 align:start position:0% so I guess it kind of falls on us to 00:26:17.850 --> 00:26:21.740 align:start position:0% so I guess it kind of falls on us to decide<00:26:18.750> that<00:26:19.760> so<00:26:20.760> we<00:26:20.820> wanted<00:26:21.030> to<00:26:21.090> say<00:26:21.240> a<00:26:21.270> little 00:26:21.740 --> 00:26:21.750 align:start position:0% decide that so we wanted to say a little 00:26:21.750 --> 00:26:26.120 align:start position:0% decide that so we wanted to say a little bit<00:26:22.200> about<00:26:22.260> it<00:26:24.260> this<00:26:25.260> talk<00:26:25.560> it's<00:26:25.800> not<00:26:25.860> going<00:26:26.070> to 00:26:26.120 --> 00:26:26.130 align:start position:0% bit about it this talk it's not going to 00:26:26.130 --> 00:26:29.390 align:start position:0% bit about it this talk it's not going to be<00:26:26.630> highly<00:26:27.630> technical<00:26:27.780> this<00:26:28.410> is<00:26:28.590> supposed<00:26:29.310> to 00:26:29.390 --> 00:26:29.400 align:start position:0% be highly technical this is supposed to 00:26:29.400 --> 00:26:34.850 align:start position:0% be highly technical this is supposed to be<00:26:29.460> an<00:26:29.820> overview<00:26:30.320> for<00:26:32.930> you<00:26:33.930> know<00:26:34.020> of<00:26:34.260> like<00:26:34.650> the 00:26:34.850 --> 00:26:34.860 align:start position:0% be an overview for you know of like the 00:26:34.860 --> 00:26:37.100 align:start position:0% be an overview for you know of like the developer<00:26:35.640> experience<00:26:36.180> and<00:26:36.600> the<00:26:36.900> user 00:26:37.100 --> 00:26:37.110 align:start position:0% developer experience and the user 00:26:37.110 --> 00:26:39.830 align:start position:0% developer experience and the user experience<00:26:37.230> and<00:26:38.010> the<00:26:38.570> challenges<00:26:39.570> and 00:26:39.830 --> 00:26:39.840 align:start position:0% experience and the challenges and 00:26:39.840 --> 00:26:43.580 align:start position:0% experience and the challenges and changes<00:26:40.230> that<00:26:40.760> will<00:26:41.760> have<00:26:41.940> to<00:26:42.060> be<00:26:42.150> made<00:26:42.590> in 00:26:43.580 --> 00:26:43.590 align:start position:0% changes that will have to be made in 00:26:43.590 --> 00:26:49.130 align:start position:0% changes that will have to be made in order<00:26:43.770> to<00:26:44.100> scale<00:26:44.640> aetherium<00:26:47.210> so<00:26:48.210> just<00:26:48.960> the 00:26:49.130 --> 00:26:49.140 align:start position:0% order to scale aetherium so just the 00:26:49.140 --> 00:26:52.910 align:start position:0% order to scale aetherium so just the goal<00:26:49.320> is<00:26:49.730> having<00:26:50.730> a<00:26:51.030> a<00:26:51.570> lot<00:26:52.200> of<00:26:52.320> users<00:26:52.620> lot<00:26:52.860> of 00:26:52.910 --> 00:26:52.920 align:start position:0% goal is having a a lot of users lot of 00:26:52.920 --> 00:26:57.020 align:start position:0% goal is having a a lot of users lot of transactions<00:26:53.580> and<00:26:54.380> transactions<00:26:55.380> and<00:26:56.030> where 00:26:57.020 --> 00:26:57.030 align:start position:0% transactions and transactions and where 00:26:57.030 --> 00:27:02.150 align:start position:0% transactions and transactions and where the<00:26:57.240> gas<00:26:58.220> price<00:26:59.220> remains<00:26:59.640> cheap<00:27:00.740> if<00:27:01.740> the<00:27:01.980> gas 00:27:02.150 --> 00:27:02.160 align:start position:0% the gas price remains cheap if the gas 00:27:02.160 --> 00:27:05.210 align:start position:0% the gas price remains cheap if the gas price<00:27:02.640> is<00:27:03.050> if<00:27:04.050> the<00:27:04.230> gas<00:27:04.380> supply<00:27:04.530> is<00:27:04.740> limited 00:27:05.210 --> 00:27:05.220 align:start position:0% price is if the gas supply is limited 00:27:05.220 --> 00:27:07.490 align:start position:0% price is if the gas supply is limited and<00:27:05.670> you<00:27:06.180> have<00:27:06.300> a<00:27:06.360> lot<00:27:06.480> of<00:27:06.510> users<00:27:06.840> then<00:27:07.230> the<00:27:07.350> gas 00:27:07.490 --> 00:27:07.500 align:start position:0% and you have a lot of users then the gas 00:27:07.500 --> 00:27:12.950 align:start position:0% and you have a lot of users then the gas price<00:27:07.920> goes<00:27:08.550> sky-high<00:27:10.820> so<00:27:11.820> how<00:27:11.970> do<00:27:12.030> we<00:27:12.120> keep 00:27:12.950 --> 00:27:12.960 align:start position:0% price goes sky-high so how do we keep 00:27:12.960 --> 00:27:17.990 align:start position:0% price goes sky-high so how do we keep the<00:27:13.110> gas<00:27:13.430> gas<00:27:14.430> prices<00:27:14.790> cheap<00:27:14.970> again<00:27:16.700> well<00:27:17.700> if 00:27:17.990 --> 00:27:18.000 align:start position:0% the gas gas prices cheap again well if 00:27:18.000 --> 00:27:19.000 align:start position:0% the gas gas prices cheap again well if you<00:27:18.090> don't<00:27:18.180> want<00:27:18.390> to<00:27:18.450> sacrifice 00:27:19.000 --> 00:27:19.010 align:start position:0% you don't want to sacrifice 00:27:19.010 --> 00:27:22.100 align:start position:0% you don't want to sacrifice decentralization<00:27:20.010> you<00:27:20.670> could<00:27:20.910> just<00:27:21.180> run<00:27:21.540> all 00:27:22.100 --> 00:27:22.110 align:start position:0% decentralization you could just run all 00:27:22.110 --> 00:27:26.420 align:start position:0% decentralization you could just run all the<00:27:22.410> validator<00:27:22.800> notes<00:27:23.040> on<00:27:24.770> all<00:27:25.770> transactions 00:27:26.420 --> 00:27:26.430 align:start position:0% the validator notes on all transactions 00:27:26.430 --> 00:27:30.940 align:start position:0% the validator notes on all transactions on<00:27:26.580> 21<00:27:27.350> validator<00:27:28.350> nodes<00:27:29.130> on<00:27:29.430> supercomputers 00:27:30.940 --> 00:27:30.950 align:start position:0% on 21 validator nodes on supercomputers 00:27:30.950 --> 00:27:34.370 align:start position:0% on 21 validator nodes on supercomputers but<00:27:31.950> if<00:27:32.220> you<00:27:32.670> don't<00:27:33.480> want<00:27:33.630> to<00:27:33.720> trade<00:27:33.870> off<00:27:34.080> do 00:27:34.370 --> 00:27:34.380 align:start position:0% but if you don't want to trade off do 00:27:34.380 --> 00:27:36.980 align:start position:0% but if you don't want to trade off do you<00:27:34.440> centralization<00:27:35.130> then<00:27:35.490> ideally<00:27:36.450> you'd<00:27:36.840> be 00:27:36.980 --> 00:27:36.990 align:start position:0% you centralization then ideally you'd be 00:27:36.990 --> 00:27:39.500 align:start position:0% you centralization then ideally you'd be able<00:27:37.080> to<00:27:37.200> run<00:27:37.560> a<00:27:37.800> validator<00:27:38.340> note<00:27:38.580> on<00:27:38.850> you<00:27:39.420> know 00:27:39.500 --> 00:27:39.510 align:start position:0% able to run a validator note on you know 00:27:39.510 --> 00:27:42.290 align:start position:0% able to run a validator note on you know any<00:27:39.690> consumer<00:27:40.050> laptop<00:27:41.000> that<00:27:42.000> way<00:27:42.090> you<00:27:42.180> can 00:27:42.290 --> 00:27:42.300 align:start position:0% any consumer laptop that way you can 00:27:42.300 --> 00:27:45.550 align:start position:0% any consumer laptop that way you can just<00:27:42.450> keep<00:27:42.600> adding<00:27:42.900> more<00:27:42.930> laptops<00:27:43.620> and 00:27:45.550 --> 00:27:45.560 align:start position:0% just keep adding more laptops and 00:27:45.560 --> 00:27:51.320 align:start position:0% just keep adding more laptops and network<00:27:46.560> and<00:27:46.740> scale<00:27:49.550> so<00:27:50.550> to<00:27:50.610> solve<00:27:51.150> this 00:27:51.320 --> 00:27:51.330 align:start position:0% network and scale so to solve this 00:27:51.330 --> 00:27:51.770 align:start position:0% network and scale so to solve this dilemma 00:27:51.770 --> 00:27:51.780 align:start position:0% dilemma 00:27:51.780 --> 00:27:56.860 align:start position:0% dilemma our<00:27:52.290> hero<00:27:53.120> sharding<00:27:54.120> chess<00:27:54.630> perma<00:27:54.900> card<00:27:55.140> face 00:27:56.860 --> 00:27:56.870 align:start position:0% our hero sharding chess perma card face 00:27:56.870 --> 00:27:58.570 align:start position:0% our hero sharding chess perma card face [Music] 00:27:58.570 --> 00:27:58.580 align:start position:0% [Music] 00:27:58.580 --> 00:28:03.290 align:start position:0% [Music] what's<00:27:59.580> the<00:27:59.670> plan<00:28:00.470> phase<00:28:01.470> one<00:28:01.710> we<00:28:02.580> collect<00:28:03.030> a 00:28:03.290 --> 00:28:03.300 align:start position:0% what's the plan phase one we collect a 00:28:03.300 --> 00:28:06.560 align:start position:0% what's the plan phase one we collect a lot<00:28:03.480> of<00:28:03.510> data<00:28:03.750> blobs 00:28:06.560 --> 00:28:06.570 align:start position:0% 00:28:06.570 --> 00:28:08.390 align:start position:0% we<00:28:06.840> have<00:28:06.990> a<00:28:07.020> pretty<00:28:07.230> comprehensive<00:28:07.560> spec<00:28:08.160> for 00:28:08.390 --> 00:28:08.400 align:start position:0% we have a pretty comprehensive spec for 00:28:08.400 --> 00:28:12.800 align:start position:0% we have a pretty comprehensive spec for doing<00:28:08.670> this<00:28:08.820> you<00:28:09.620> know<00:28:10.620> it's<00:28:11.630> like<00:28:12.630> eight 00:28:12.800 --> 00:28:12.810 align:start position:0% doing this you know it's like eight 00:28:12.810 --> 00:28:15.230 align:start position:0% doing this you know it's like eight different<00:28:12.960> teams<00:28:13.410> building<00:28:14.010> it<00:28:14.130> out<00:28:14.280> it's<00:28:14.850> the 00:28:15.230 --> 00:28:15.240 align:start position:0% different teams building it out it's the 00:28:15.240 --> 00:28:20.810 align:start position:0% different teams building it out it's the beacon<00:28:15.930> chain<00:28:17.990> they<00:28:18.990> say<00:28:19.230> you<00:28:19.290> know<00:28:19.700> some<00:28:20.700> of 00:28:20.810 --> 00:28:20.820 align:start position:0% beacon chain they say you know some of 00:28:20.820 --> 00:28:23.300 align:start position:0% beacon chain they say you know some of these<00:28:20.880> prototypes<00:28:21.570> should<00:28:22.440> be<00:28:22.560> functional 00:28:23.300 --> 00:28:23.310 align:start position:0% these prototypes should be functional 00:28:23.310 --> 00:28:24.980 align:start position:0% these prototypes should be functional soonish 00:28:24.980 --> 00:28:24.990 align:start position:0% soonish 00:28:24.990 --> 00:28:29.570 align:start position:0% soonish and<00:28:25.680> then<00:28:27.080> then<00:28:28.080> there's<00:28:28.320> phase<00:28:28.890> -<00:28:29.160> well<00:28:29.370> phase 00:28:29.570 --> 00:28:29.580 align:start position:0% and then then there's phase - well phase 00:28:29.580 --> 00:28:32.230 align:start position:0% and then then there's phase - well phase two<00:28:29.790> we<00:28:30.200> think<00:28:31.200> we're<00:28:31.290> gonna<00:28:31.380> use<00:28:31.500> yozma<00:28:32.070> but 00:28:32.230 --> 00:28:32.240 align:start position:0% two we think we're gonna use yozma but 00:28:32.240 --> 00:28:35.210 align:start position:0% two we think we're gonna use yozma but we<00:28:33.240> still<00:28:33.690> I<00:28:34.020> mean<00:28:34.620> we're<00:28:34.890> not<00:28:34.950> really<00:28:35.130> sure 00:28:35.210 --> 00:28:35.220 align:start position:0% we still I mean we're not really sure 00:28:35.220 --> 00:28:37.040 align:start position:0% we still I mean we're not really sure how<00:28:35.760> we're<00:28:35.880> gonna<00:28:35.940> do<00:28:36.150> phase<00:28:36.420> two<00:28:36.630> we<00:28:36.840> still 00:28:37.040 --> 00:28:37.050 align:start position:0% how we're gonna do phase two we still 00:28:37.050 --> 00:28:47.150 align:start position:0% how we're gonna do phase two we still have<00:28:37.140> to<00:28:37.260> iron<00:28:37.530> out<00:28:37.770> some<00:28:37.800> details<00:28:46.010> but<00:28:47.010> there 00:28:47.150 --> 00:28:47.160 align:start position:0% have to iron out some details but there 00:28:47.160 --> 00:28:50.840 align:start position:0% have to iron out some details but there is<00:28:47.220> good<00:28:47.400> news<00:28:47.580> because<00:28:49.460> phase<00:28:50.460> one<00:28:50.730> is 00:28:50.840 --> 00:28:50.850 align:start position:0% is good news because phase one is 00:28:50.850 --> 00:28:54.080 align:start position:0% is good news because phase one is actually<00:28:51.240> the<00:28:51.480> hard<00:28:52.290> part<00:28:52.560> so<00:28:52.920> phase<00:28:53.520> one<00:28:53.820> is 00:28:54.080 --> 00:28:54.090 align:start position:0% actually the hard part so phase one is 00:28:54.090 --> 00:28:56.480 align:start position:0% actually the hard part so phase one is the<00:28:54.150> consensus<00:28:54.990> protocol<00:28:55.410> the<00:28:55.800> consensus 00:28:56.480 --> 00:28:56.490 align:start position:0% the consensus protocol the consensus 00:28:56.490 --> 00:29:01.070 align:start position:0% the consensus protocol the consensus protocol<00:28:57.950> comes<00:28:58.950> to<00:28:59.130> consensus<00:28:59.760> on<00:28:59.940> the<00:29:00.330> order 00:29:01.070 --> 00:29:01.080 align:start position:0% protocol comes to consensus on the order 00:29:01.080 --> 00:29:06.700 align:start position:0% protocol comes to consensus on the order of<00:29:01.260> the<00:29:01.710> data<00:29:02.370> blobs<00:29:03.800> coming<00:29:04.800> to<00:29:05.070> the 00:29:06.700 --> 00:29:06.710 align:start position:0% of the data blobs coming to the 00:29:06.710 --> 00:29:09.830 align:start position:0% of the data blobs coming to the consensus<00:29:07.710> protocol<00:29:08.070> is<00:29:08.220> actually<00:29:08.720> you<00:29:09.720> know 00:29:09.830 --> 00:29:09.840 align:start position:0% consensus protocol is actually you know 00:29:09.840 --> 00:29:13.280 align:start position:0% consensus protocol is actually you know very<00:29:10.140> complicated<00:29:10.650> because<00:29:11.660> the<00:29:12.660> outcome<00:29:13.110> is 00:29:13.280 --> 00:29:13.290 align:start position:0% very complicated because the outcome is 00:29:13.290 --> 00:29:15.650 align:start position:0% very complicated because the outcome is non-deterministic<00:29:13.830> every<00:29:14.640> validator<00:29:15.090> has<00:29:15.330> a 00:29:15.650 --> 00:29:15.660 align:start position:0% non-deterministic every validator has a 00:29:15.660 --> 00:29:17.330 align:start position:0% non-deterministic every validator has a different<00:29:16.140> view<00:29:16.320> of<00:29:16.350> the<00:29:16.560> network<00:29:16.710> you<00:29:17.250> know 00:29:17.330 --> 00:29:17.340 align:start position:0% different view of the network you know 00:29:17.340 --> 00:29:20.210 align:start position:0% different view of the network you know data<00:29:17.850> blobs<00:29:18.150> arrive<00:29:18.570> in<00:29:18.900> you<00:29:19.620> know<00:29:19.710> different 00:29:20.210 --> 00:29:20.220 align:start position:0% data blobs arrive in you know different 00:29:20.220 --> 00:29:22.340 align:start position:0% data blobs arrive in you know different orders<00:29:20.580> and<00:29:20.610> different<00:29:21.090> validators<00:29:21.570> you<00:29:22.170> have 00:29:22.340 --> 00:29:22.350 align:start position:0% orders and different validators you have 00:29:22.350 --> 00:29:25.120 align:start position:0% orders and different validators you have all<00:29:23.160> kinds<00:29:23.460> of<00:29:23.550> hairy<00:29:23.820> game<00:29:24.330> theory<00:29:24.600> issues 00:29:25.120 --> 00:29:25.130 align:start position:0% all kinds of hairy game theory issues 00:29:25.130 --> 00:29:29.720 align:start position:0% all kinds of hairy game theory issues with<00:29:26.960> you<00:29:27.960> know<00:29:28.050> malicious<00:29:28.830> actors<00:29:29.280> and 00:29:29.720 --> 00:29:29.730 align:start position:0% with you know malicious actors and 00:29:29.730 --> 00:29:35.030 align:start position:0% with you know malicious actors and network<00:29:29.970> partitions<00:29:30.540> and<00:29:31.970> it's<00:29:33.860> yeah<00:29:34.860> it's 00:29:35.030 --> 00:29:35.040 align:start position:0% network partitions and it's yeah it's 00:29:35.040 --> 00:29:40.330 align:start position:0% network partitions and it's yeah it's it's<00:29:35.370> it's<00:29:35.760> a<00:29:36.660> challenge<00:29:38.570> phase<00:29:39.570> two 00:29:40.330 --> 00:29:40.340 align:start position:0% it's it's a challenge phase two 00:29:40.340 --> 00:29:43.100 align:start position:0% it's it's a challenge phase two relatively<00:29:41.340> speaking<00:29:41.520> is<00:29:42.060> much<00:29:42.930> more 00:29:43.100 --> 00:29:43.110 align:start position:0% relatively speaking is much more 00:29:43.110 --> 00:29:46.790 align:start position:0% relatively speaking is much more straightforward<00:29:43.410> you<00:29:44.280> all<00:29:45.120> you<00:29:45.420> have<00:29:45.600> is<00:29:45.870> it's 00:29:46.790 --> 00:29:46.800 align:start position:0% straightforward you all you have is it's 00:29:46.800 --> 00:29:49.580 align:start position:0% straightforward you all you have is it's a<00:29:46.950> deterministic<00:29:47.670> system<00:29:48.090> the<00:29:48.990> order<00:29:49.260> of<00:29:49.470> the 00:29:49.580 --> 00:29:49.590 align:start position:0% a deterministic system the order of the 00:29:49.590 --> 00:29:51.590 align:start position:0% a deterministic system the order of the data<00:29:49.770> blob<00:29:49.980> is<00:29:50.130> already<00:29:50.370> known<00:29:50.550> you<00:29:51.270> have<00:29:51.420> one 00:29:51.590 --> 00:29:51.600 align:start position:0% data blob is already known you have one 00:29:51.600 --> 00:29:53.660 align:start position:0% data blob is already known you have one block<00:29:51.750> you<00:29:51.810> process<00:29:52.380> it<00:29:52.530> you<00:29:52.860> get<00:29:53.040> you<00:29:53.580> know 00:29:53.660 --> 00:29:53.670 align:start position:0% block you process it you get you know 00:29:53.670 --> 00:29:55.520 align:start position:0% block you process it you get you know the<00:29:53.700> next<00:29:53.970> block<00:29:54.180> comes<00:29:54.450> you<00:29:54.630> process<00:29:55.050> it<00:29:55.230> and 00:29:55.520 --> 00:29:55.530 align:start position:0% the next block comes you process it and 00:29:55.530 --> 00:29:58.000 align:start position:0% the next block comes you process it and so<00:29:55.860> forth 00:29:58.000 --> 00:29:58.010 align:start position:0% so forth 00:29:58.010 --> 00:30:03.860 align:start position:0% so forth so<00:29:59.930> with<00:30:00.930> if<00:30:01.230> phase<00:30:01.800> one<00:30:02.070> is<00:30:02.340> behind<00:30:03.330> us<00:30:03.600> and 00:30:03.860 --> 00:30:03.870 align:start position:0% so with if phase one is behind us and 00:30:03.870 --> 00:30:05.600 align:start position:0% so with if phase one is behind us and you<00:30:04.620> only<00:30:04.770> have<00:30:05.010> to<00:30:05.130> worry<00:30:05.280> about<00:30:05.400> the 00:30:05.600 --> 00:30:05.610 align:start position:0% you only have to worry about the 00:30:05.610 --> 00:30:07.880 align:start position:0% you only have to worry about the execution<00:30:05.880> engine<00:30:06.450> and<00:30:06.660> Phase<00:30:06.870> two<00:30:06.900> next<00:30:07.650> then 00:30:07.880 --> 00:30:07.890 align:start position:0% execution engine and Phase two next then 00:30:07.890 --> 00:30:12.770 align:start position:0% execution engine and Phase two next then you're<00:30:08.160> actually<00:30:08.550> you<00:30:09.120> know<00:30:09.230> not<00:30:11.570> that<00:30:12.570> far 00:30:12.770 --> 00:30:12.780 align:start position:0% you're actually you know not that far 00:30:12.780 --> 00:30:17.380 align:start position:0% you're actually you know not that far from<00:30:12.810> the<00:30:13.050> finish<00:30:13.140> line 00:30:17.380 --> 00:30:17.390 align:start position:0% 00:30:17.390 --> 00:30:21.340 align:start position:0% we<00:30:17.690> learned<00:30:17.960> yesterday<00:30:19.030> that<00:30:20.200> Jasper<00:30:21.200> is 00:30:21.340 --> 00:30:21.350 align:start position:0% we learned yesterday that Jasper is 00:30:21.350 --> 00:30:24.760 align:start position:0% we learned yesterday that Jasper is actually<00:30:21.680> kind<00:30:22.550> of<00:30:22.640> lame<00:30:23.230> it<00:30:24.230> can<00:30:24.380> be<00:30:24.500> a<00:30:24.530> bit<00:30:24.680> of 00:30:24.760 --> 00:30:24.770 align:start position:0% actually kind of lame it can be a bit of 00:30:24.770 --> 00:30:28.630 align:start position:0% actually kind of lame it can be a bit of a<00:30:24.830> buzzkill<00:30:25.810> my<00:30:26.810> two<00:30:26.870> main<00:30:27.500> complaints<00:30:28.070> about 00:30:28.630 --> 00:30:28.640 align:start position:0% a buzzkill my two main complaints about 00:30:28.640 --> 00:30:31.360 align:start position:0% a buzzkill my two main complaints about Jasper<00:30:29.090> are<00:30:29.660> that<00:30:29.990> for<00:30:30.620> one<00:30:30.770> it<00:30:30.890> won't<00:30:30.980> shard 00:30:31.360 --> 00:30:31.370 align:start position:0% Jasper are that for one it won't shard 00:30:31.370 --> 00:30:34.540 align:start position:0% Jasper are that for one it won't shard it<00:30:32.300> won't<00:30:32.480> it<00:30:32.600> won't<00:30:32.720> scale<00:30:33.340> contracts<00:30:34.340> that 00:30:34.540 --> 00:30:34.550 align:start position:0% it won't it won't scale contracts that 00:30:34.550 --> 00:30:36.940 align:start position:0% it won't it won't scale contracts that exist<00:30:35.300> on<00:30:35.480> the<00:30:35.840> main<00:30:36.320> chain 00:30:36.940 --> 00:30:36.950 align:start position:0% exist on the main chain 00:30:36.950 --> 00:30:39.880 align:start position:0% exist on the main chain you<00:30:37.370> know<00:30:37.490> Jasper<00:30:37.880> is<00:30:38.210> going<00:30:38.510> to<00:30:38.630> be<00:30:38.770> excuse<00:30:39.770> me 00:30:39.880 --> 00:30:39.890 align:start position:0% you know Jasper is going to be excuse me 00:30:39.890 --> 00:30:44.080 align:start position:0% you know Jasper is going to be excuse me serenity<00:30:40.400> will<00:30:41.060> be<00:30:41.180> a<00:30:42.040> new<00:30:43.040> you<00:30:43.580> know<00:30:43.640> parallel 00:30:44.080 --> 00:30:44.090 align:start position:0% serenity will be a new you know parallel 00:30:44.090 --> 00:30:47.860 align:start position:0% serenity will be a new you know parallel universe<00:30:44.480> of<00:30:44.720> 1,000<00:30:45.500> empty<00:30:46.070> shards<00:30:46.730> and<00:30:47.000> users 00:30:47.860 --> 00:30:47.870 align:start position:0% universe of 1,000 empty shards and users 00:30:47.870 --> 00:30:50.980 align:start position:0% universe of 1,000 empty shards and users will<00:30:48.020> have<00:30:48.080> to<00:30:48.410> migrate<00:30:49.540> to<00:30:50.540> them<00:30:50.720> you<00:30:50.870> know<00:30:50.960> I 00:30:50.980 --> 00:30:50.990 align:start position:0% will have to migrate to them you know I 00:30:50.990 --> 00:30:51.400 align:start position:0% will have to migrate to them you know I don't<00:30:51.170> know 00:30:51.400 --> 00:30:51.410 align:start position:0% don't know 00:30:51.410 --> 00:30:54.370 align:start position:0% don't know redeploy<00:30:51.710> contracts<00:30:52.370> transfer<00:30:53.380> state 00:30:54.370 --> 00:30:54.380 align:start position:0% redeploy contracts transfer state 00:30:54.380 --> 00:30:57.420 align:start position:0% redeploy contracts transfer state somehow<00:30:55.300> but<00:30:56.300> when<00:30:56.420> it<00:30:56.510> launches<00:30:56.810> it'll<00:30:57.020> be<00:30:57.140> a 00:30:57.420 --> 00:30:57.430 align:start position:0% somehow but when it launches it'll be a 00:30:57.430 --> 00:31:03.840 align:start position:0% somehow but when it launches it'll be a ghost<00:30:58.430> town<00:30:58.900> get<00:30:59.900> it<00:31:00.080> Casper<00:31:00.590> ghost<00:31:01.430> own 00:31:03.840 --> 00:31:03.850 align:start position:0% 00:31:03.850 --> 00:31:08.290 align:start position:0% secondly<00:31:05.830> shards<00:31:06.830> are<00:31:06.890> gonna<00:31:06.980> have<00:31:07.220> the<00:31:07.850> gas 00:31:08.290 --> 00:31:08.300 align:start position:0% secondly shards are gonna have the gas 00:31:08.300 --> 00:31:10.090 align:start position:0% secondly shards are gonna have the gas prices<00:31:08.690> will<00:31:08.810> be<00:31:08.930> independent<00:31:09.230> on<00:31:09.620> each 00:31:10.090 --> 00:31:10.100 align:start position:0% prices will be independent on each 00:31:10.100 --> 00:31:14.500 align:start position:0% prices will be independent on each different<00:31:10.550> shards<00:31:11.000> so<00:31:12.400> you<00:31:13.400> know<00:31:13.520> in<00:31:14.180> theory 00:31:14.500 --> 00:31:14.510 align:start position:0% different shards so you know in theory 00:31:14.510 --> 00:31:16.210 align:start position:0% different shards so you know in theory this<00:31:14.630> is<00:31:14.690> not<00:31:14.870> really<00:31:15.020> a<00:31:15.080> problem<00:31:15.260> because<00:31:15.710> if 00:31:16.210 --> 00:31:16.220 align:start position:0% this is not really a problem because if 00:31:16.220 --> 00:31:18.940 align:start position:0% this is not really a problem because if you<00:31:16.670> end<00:31:17.090> up<00:31:17.390> on<00:31:17.540> a<00:31:17.600> really<00:31:17.930> popular<00:31:18.200> shard<00:31:18.680> and 00:31:18.940 --> 00:31:18.950 align:start position:0% you end up on a really popular shard and 00:31:18.950 --> 00:31:21.760 align:start position:0% you end up on a really popular shard and the<00:31:19.070> gas<00:31:19.220> price<00:31:19.490> is<00:31:19.520> expensive<00:31:20.150> then<00:31:21.020> you<00:31:21.620> can 00:31:21.760 --> 00:31:21.770 align:start position:0% the gas price is expensive then you can 00:31:21.770 --> 00:31:23.650 align:start position:0% the gas price is expensive then you can just<00:31:21.980> you<00:31:22.220> know<00:31:22.250> move<00:31:22.610> to<00:31:22.850> a<00:31:22.880> cheaper<00:31:23.450> shard 00:31:23.650 --> 00:31:23.660 align:start position:0% just you know move to a cheaper shard 00:31:23.660 --> 00:31:25.530 align:start position:0% just you know move to a cheaper shard where<00:31:23.810> there's<00:31:23.960> not<00:31:24.080> as<00:31:24.170> much<00:31:24.290> activity<00:31:24.470> I 00:31:25.530 --> 00:31:25.540 align:start position:0% where there's not as much activity I 00:31:25.540 --> 00:31:29.470 align:start position:0% where there's not as much activity I think<00:31:26.540> you<00:31:27.470> know<00:31:27.590> this<00:31:28.250> is<00:31:28.430> I<00:31:28.700> mean<00:31:29.030> yes<00:31:29.270> in 00:31:29.470 --> 00:31:29.480 align:start position:0% think you know this is I mean yes in 00:31:29.480 --> 00:31:31.660 align:start position:0% think you know this is I mean yes in theory<00:31:29.830> it's<00:31:30.830> kind<00:31:31.070> of<00:31:31.100> like<00:31:31.280> telling<00:31:31.640> people 00:31:31.660 --> 00:31:31.670 align:start position:0% theory it's kind of like telling people 00:31:31.670 --> 00:31:34.630 align:start position:0% theory it's kind of like telling people you<00:31:32.630> know<00:31:32.750> who<00:31:33.020> live<00:31:33.440> in<00:31:33.590> San<00:31:33.770> Francisco<00:31:33.800> and 00:31:34.630 --> 00:31:34.640 align:start position:0% you know who live in San Francisco and 00:31:34.640 --> 00:31:37.840 align:start position:0% you know who live in San Francisco and are<00:31:34.940> complaining<00:31:35.360> that<00:31:35.830> the<00:31:36.830> city<00:31:37.490> is<00:31:37.700> not 00:31:37.840 --> 00:31:37.850 align:start position:0% are complaining that the city is not 00:31:37.850 --> 00:31:40.660 align:start position:0% are complaining that the city is not scaling<00:31:38.420> the<00:31:38.600> supply<00:31:39.020> of<00:31:39.050> housing<00:31:39.370> that<00:31:40.370> well 00:31:40.660 --> 00:31:40.670 align:start position:0% scaling the supply of housing that well 00:31:40.670 --> 00:31:42.460 align:start position:0% scaling the supply of housing that well it's<00:31:40.850> no<00:31:40.940> problem<00:31:41.180> you<00:31:41.720> should<00:31:41.900> because<00:31:42.350> you 00:31:42.460 --> 00:31:42.470 align:start position:0% it's no problem you should because you 00:31:42.470 --> 00:31:46.030 align:start position:0% it's no problem you should because you can<00:31:42.590> just<00:31:42.740> move<00:31:43.160> to<00:31:43.340> North<00:31:43.640> Dakota<00:31:44.830> one<00:31:45.830> point 00:31:46.030 --> 00:31:46.040 align:start position:0% can just move to North Dakota one point 00:31:46.040 --> 00:31:49.030 align:start position:0% can just move to North Dakota one point no<00:31:46.100> problem<00:31:46.780> of<00:31:47.780> this<00:31:48.500> kind<00:31:48.680> problem<00:31:48.980> in 00:31:49.030 --> 00:31:49.040 align:start position:0% no problem of this kind problem in 00:31:49.040 --> 00:31:52.000 align:start position:0% no problem of this kind problem in general<00:31:49.160> 1.0<00:31:49.730> 2.0<00:31:50.090> is<00:31:50.210> that<00:31:50.360> there's<00:31:50.600> a<00:31:51.010> too 00:31:52.000 --> 00:31:52.010 align:start position:0% general 1.0 2.0 is that there's a too 00:31:52.010 --> 00:31:56.920 align:start position:0% general 1.0 2.0 is that there's a too much<00:31:52.190> state<00:31:54.250> users<00:31:55.250> pay<00:31:55.880> a<00:31:55.910> one-time<00:31:56.270> Gatsby 00:31:56.920 --> 00:31:56.930 align:start position:0% much state users pay a one-time Gatsby 00:31:56.930 --> 00:32:00.370 align:start position:0% much state users pay a one-time Gatsby they<00:31:57.680> create<00:31:58.160> an<00:31:58.220> account<00:31:58.520> in<00:31:58.730> the<00:31:59.450> state<00:32:00.110> tree 00:32:00.370 --> 00:32:00.380 align:start position:0% they create an account in the state tree 00:32:00.380 --> 00:32:05.970 align:start position:0% they create an account in the state tree and<00:32:01.480> that<00:32:02.480> account<00:32:03.170> is<00:32:03.380> there<00:32:04.480> forever<00:32:05.480> and 00:32:05.970 --> 00:32:05.980 align:start position:0% and that account is there forever and 00:32:05.980 --> 00:32:09.850 align:start position:0% and that account is there forever and all<00:32:06.980> the<00:32:07.040> full<00:32:07.670> amount<00:32:07.820> all<00:32:08.030> the<00:32:08.060> miners<00:32:08.860> just 00:32:09.850 --> 00:32:09.860 align:start position:0% all the full amount all the miners just 00:32:09.860 --> 00:32:11.590 align:start position:0% all the full amount all the miners just have<00:32:09.980> to<00:32:10.070> keep<00:32:10.280> all<00:32:10.490> this<00:32:10.640> these<00:32:11.270> you<00:32:11.510> know 00:32:11.590 --> 00:32:11.600 align:start position:0% have to keep all this these you know 00:32:11.600 --> 00:32:18.100 align:start position:0% have to keep all this these you know junk<00:32:12.140> around<00:32:13.630> indefinitely<00:32:16.660> so<00:32:17.660> what 00:32:18.100 --> 00:32:18.110 align:start position:0% junk around indefinitely so what 00:32:18.110 --> 00:32:20.500 align:start position:0% junk around indefinitely so what techniques<00:32:18.830> do<00:32:18.950> we<00:32:19.040> have<00:32:19.220> what<00:32:20.000> approaches<00:32:20.360> we 00:32:20.500 --> 00:32:20.510 align:start position:0% techniques do we have what approaches we 00:32:20.510 --> 00:32:22.150 align:start position:0% techniques do we have what approaches we have<00:32:20.600> to<00:32:20.690> reduce<00:32:20.900> the<00:32:21.020> state<00:32:21.260> we<00:32:21.680> have<00:32:21.710> two<00:32:22.070> of 00:32:22.150 --> 00:32:22.160 align:start position:0% have to reduce the state we have two of 00:32:22.160 --> 00:32:23.130 align:start position:0% have to reduce the state we have two of them 00:32:23.130 --> 00:32:23.140 align:start position:0% them 00:32:23.140 --> 00:32:27.670 align:start position:0% them stateless<00:32:24.140> clients<00:32:24.530> and<00:32:24.680> storage<00:32:24.920> ran<00:32:26.680> with 00:32:27.670 --> 00:32:27.680 align:start position:0% stateless clients and storage ran with 00:32:27.680 --> 00:32:29.890 align:start position:0% stateless clients and storage ran with stateless<00:32:28.220> clients<00:32:28.610> there's<00:32:28.850> a<00:32:29.180> single 00:32:29.890 --> 00:32:29.900 align:start position:0% stateless clients there's a single 00:32:29.900 --> 00:32:31.270 align:start position:0% stateless clients there's a single 32-byte 00:32:31.270 --> 00:32:31.280 align:start position:0% 32-byte 00:32:31.280 --> 00:32:35.680 align:start position:0% 32-byte storage<00:32:31.550> root<00:32:32.200> and<00:32:34.240> when<00:32:35.240> you<00:32:35.390> send<00:32:35.630> a 00:32:35.680 --> 00:32:35.690 align:start position:0% storage root and when you send a 00:32:35.690 --> 00:32:39.280 align:start position:0% storage root and when you send a transaction<00:32:36.230> to<00:32:36.260> the<00:32:36.440> network<00:32:37.810> so<00:32:38.810> miners 00:32:39.280 --> 00:32:39.290 align:start position:0% transaction to the network so miners 00:32:39.290 --> 00:32:42.880 align:start position:0% transaction to the network so miners Valladares<00:32:40.070> have<00:32:40.310> only<00:32:40.520> the<00:32:40.760> 32<00:32:41.390> byte<00:32:41.890> storage 00:32:42.880 --> 00:32:42.890 align:start position:0% Valladares have only the 32 byte storage 00:32:42.890 --> 00:32:44.950 align:start position:0% Valladares have only the 32 byte storage route<00:32:43.070> and<00:32:43.280> when<00:32:44.030> you<00:32:44.150> as<00:32:44.270> a<00:32:44.300> user<00:32:44.570> send<00:32:44.900> a 00:32:44.950 --> 00:32:44.960 align:start position:0% route and when you as a user send a 00:32:44.960 --> 00:32:46.300 align:start position:0% route and when you as a user send a transaction<00:32:45.470> to<00:32:45.500> the<00:32:45.650> network<00:32:45.890> you<00:32:46.070> have<00:32:46.100> to 00:32:46.300 --> 00:32:46.310 align:start position:0% transaction to the network you have to 00:32:46.310 --> 00:32:49.420 align:start position:0% transaction to the network you have to supply<00:32:46.820> the<00:32:46.940> merkel<00:32:47.780> proof<00:32:48.050> of<00:32:48.260> your<00:32:49.070> account 00:32:49.420 --> 00:32:49.430 align:start position:0% supply the merkel proof of your account 00:32:49.430 --> 00:32:50.860 align:start position:0% supply the merkel proof of your account so<00:32:49.760> you<00:32:49.820> can<00:32:50.030> prove<00:32:50.180> that<00:32:50.360> your<00:32:50.510> account<00:32:50.780> has 00:32:50.860 --> 00:32:50.870 align:start position:0% so you can prove that your account has 00:32:50.870 --> 00:32:54.070 align:start position:0% so you can prove that your account has such-and-such<00:32:51.620> a<00:32:51.950> balance<00:32:52.310> and<00:32:52.520> you<00:32:53.180> can<00:32:53.360> send 00:32:54.070 --> 00:32:54.080 align:start position:0% such-and-such a balance and you can send 00:32:54.080 --> 00:32:58.780 align:start position:0% such-and-such a balance and you can send either<00:32:56.830> these<00:32:57.830> merkel<00:32:58.220> proofs<00:32:58.400> have<00:32:58.580> to<00:32:58.700> be 00:32:58.780 --> 00:32:58.790 align:start position:0% either these merkel proofs have to be 00:32:58.790 --> 00:33:03.700 align:start position:0% either these merkel proofs have to be up-to-date<00:32:59.200> so<00:33:00.200> i'm<00:33:00.700> have<00:33:01.700> a<00:33:02.710> visualization 00:33:03.700 --> 00:33:03.710 align:start position:0% up-to-date so i'm have a visualization 00:33:03.710 --> 00:33:08.410 align:start position:0% up-to-date so i'm have a visualization of<00:33:04.070> that<00:33:04.130> next<00:33:05.030> but<00:33:05.890> in<00:33:06.890> contrast<00:33:07.430> storage 00:33:08.410 --> 00:33:08.420 align:start position:0% of that next but in contrast storage 00:33:08.420 --> 00:33:14.370 align:start position:0% of that next but in contrast storage rent<00:33:10.420> validators<00:33:11.420> basically<00:33:13.030> users<00:33:14.030> pay 00:33:14.370 --> 00:33:14.380 align:start position:0% rent validators basically users pay 00:33:14.380 --> 00:33:17.200 align:start position:0% rent validators basically users pay validators<00:33:15.380> to<00:33:15.560> do<00:33:15.680> this<00:33:15.800> job<00:33:16.100> to<00:33:16.400> keep<00:33:16.880> the 00:33:17.200 --> 00:33:17.210 align:start position:0% validators to do this job to keep the 00:33:17.210 --> 00:33:19.270 align:start position:0% validators to do this job to keep the account<00:33:17.600> in<00:33:17.780> their<00:33:17.960> state<00:33:18.200> and<00:33:18.230> to<00:33:18.650> keep<00:33:18.890> the 00:33:19.270 --> 00:33:19.280 align:start position:0% account in their state and to keep the 00:33:19.280 --> 00:33:25.900 align:start position:0% account in their state and to keep the merkel<00:33:20.180> proofs<00:33:20.390> up-to-date<00:33:20.930> and<00:33:24.820> when<00:33:25.820> you 00:33:25.900 --> 00:33:25.910 align:start position:0% merkel proofs up-to-date and when you 00:33:25.910 --> 00:33:30.730 align:start position:0% merkel proofs up-to-date and when you have<00:33:26.620> storage<00:33:27.620> rent<00:33:27.920> within<00:33:28.810> an<00:33:29.810> eviction<00:33:30.110> or 00:33:30.730 --> 00:33:30.740 align:start position:0% have storage rent within an eviction or 00:33:30.740 --> 00:33:34.300 align:start position:0% have storage rent within an eviction or sleep<00:33:31.220> and<00:33:31.400> awake<00:33:31.640> like<00:33:31.880> a<00:33:32.680> if<00:33:33.680> accounts<00:33:34.160> don't 00:33:34.300 --> 00:33:34.310 align:start position:0% sleep and awake like a if accounts don't 00:33:34.310 --> 00:33:35.800 align:start position:0% sleep and awake like a if accounts don't pay<00:33:34.520> rent<00:33:34.730> then<00:33:34.940> they<00:33:35.030> get<00:33:35.120> evicted<00:33:35.390> from<00:33:35.630> the 00:33:35.800 --> 00:33:35.810 align:start position:0% pay rent then they get evicted from the 00:33:35.810 --> 00:33:39.220 align:start position:0% pay rent then they get evicted from the tree<00:33:36.250> but<00:33:37.250> then<00:33:37.460> there's<00:33:37.640> ways<00:33:37.910> that<00:33:38.360> they<00:33:39.020> can 00:33:39.220 --> 00:33:39.230 align:start position:0% tree but then there's ways that they can 00:33:39.230 --> 00:33:44.520 align:start position:0% tree but then there's ways that they can be<00:33:40.010> a<00:33:40.040> can<00:33:40.670> revive<00:33:40.970> their<00:33:41.150> account<00:33:41.480> and<00:33:42.730> come 00:33:44.520 --> 00:33:44.530 align:start position:0% be a can revive their account and come 00:33:44.530 --> 00:33:47.650 align:start position:0% be a can revive their account and come come<00:33:45.530> back<00:33:45.770> into<00:33:45.950> the<00:33:46.100> tree<00:33:46.310> then<00:33:47.090> I<00:33:47.420> mean 00:33:47.650 --> 00:33:47.660 align:start position:0% come back into the tree then I mean 00:33:47.660 --> 00:33:48.610 align:start position:0% come back into the tree then I mean basically<00:33:47.960> those<00:33:48.110> techniques<00:33:48.470> are<00:33:48.590> very 00:33:48.610 --> 00:33:48.620 align:start position:0% basically those techniques are very 00:33:48.620 --> 00:33:53.980 align:start position:0% basically those techniques are very similar<00:33:49.010> to<00:33:50.920> how<00:33:51.920> stateless<00:33:52.520> clients<00:33:52.910> work<00:33:53.540> so 00:33:53.980 --> 00:33:53.990 align:start position:0% similar to how stateless clients work so 00:33:53.990 --> 00:33:56.980 align:start position:0% similar to how stateless clients work so it's<00:33:54.860> kind<00:33:55.040> of<00:33:55.070> like<00:33:55.480> with<00:33:56.480> storage<00:33:56.750> rent 00:33:56.980 --> 00:33:56.990 align:start position:0% it's kind of like with storage rent 00:33:56.990 --> 00:33:59.230 align:start position:0% it's kind of like with storage rent there's<00:33:57.230> two<00:33:58.130> classes<00:33:58.310> of<00:33:58.580> users<00:33:58.970> there's 00:33:59.230 --> 00:33:59.240 align:start position:0% there's two classes of users there's 00:33:59.240 --> 00:34:01.270 align:start position:0% there's two classes of users there's like<00:33:59.510> first<00:33:59.840> class<00:34:00.050> people<00:34:00.710> who<00:34:00.860> can<00:34:01.190> afford 00:34:01.270 --> 00:34:01.280 align:start position:0% like first class people who can afford 00:34:01.280 --> 00:34:04.210 align:start position:0% like first class people who can afford the<00:34:01.580> rent<00:34:01.730> who<00:34:02.270> the<00:34:02.840> validators<00:34:03.320> handles<00:34:03.980> all 00:34:04.210 --> 00:34:04.220 align:start position:0% the rent who the validators handles all 00:34:04.220 --> 00:34:07.270 align:start position:0% the rent who the validators handles all of<00:34:04.370> their<00:34:04.550> merkel<00:34:05.330> proofs<00:34:05.540> and<00:34:05.980> the<00:34:06.980> second 00:34:07.270 --> 00:34:07.280 align:start position:0% of their merkel proofs and the second 00:34:07.280 --> 00:34:09.280 align:start position:0% of their merkel proofs and the second class<00:34:07.490> which<00:34:08.120> is<00:34:08.300> all<00:34:08.630> the<00:34:08.810> poor<00:34:08.960> people<00:34:09.260> who 00:34:09.280 --> 00:34:09.290 align:start position:0% class which is all the poor people who 00:34:09.290 --> 00:34:10.930 align:start position:0% class which is all the poor people who have<00:34:09.649> been<00:34:09.770> evicted<00:34:10.040> and<00:34:10.370> will<00:34:10.669> have<00:34:10.790> to 00:34:10.930 --> 00:34:10.940 align:start position:0% have been evicted and will have to 00:34:10.940 --> 00:34:13.710 align:start position:0% have been evicted and will have to supply<00:34:11.149> their<00:34:11.419> merkel<00:34:12.169> proofs<00:34:12.380> in<00:34:12.500> order<00:34:12.679> to 00:34:13.710 --> 00:34:13.720 align:start position:0% supply their merkel proofs in order to 00:34:13.720 --> 00:34:18.010 align:start position:0% supply their merkel proofs in order to reawaken<00:34:14.720> their<00:34:15.140> accounts<00:34:16.659> with<00:34:17.659> stateless 00:34:18.010 --> 00:34:18.020 align:start position:0% reawaken their accounts with stateless 00:34:18.020 --> 00:34:19.510 align:start position:0% reawaken their accounts with stateless clients<00:34:18.350> there's<00:34:18.649> just<00:34:18.830> one<00:34:19.040> class<00:34:19.220> it's 00:34:19.510 --> 00:34:19.520 align:start position:0% clients there's just one class it's 00:34:19.520 --> 00:34:22.740 align:start position:0% clients there's just one class it's everybody<00:34:19.970> you<00:34:20.659> know<00:34:20.780> in<00:34:21.020> coach 00:34:22.740 --> 00:34:22.750 align:start position:0% everybody you know in coach 00:34:22.750 --> 00:34:25.360 align:start position:0% everybody you know in coach everybody<00:34:23.750> has<00:34:23.929> to<00:34:23.960> supply<00:34:24.560> their<00:34:24.830> merkel 00:34:25.360 --> 00:34:25.370 align:start position:0% everybody has to supply their merkel 00:34:25.370 --> 00:34:30.419 align:start position:0% everybody has to supply their merkel proofs<00:34:27.429> yeah<00:34:28.429> it's<00:34:28.610> not<00:34:28.760> a<00:34:28.820> new<00:34:28.940> idea<00:34:28.970> either 00:34:30.419 --> 00:34:30.429 align:start position:0% proofs yeah it's not a new idea either 00:34:30.429 --> 00:34:34.240 align:start position:0% proofs yeah it's not a new idea either just<00:34:31.429> you<00:34:31.700> know<00:34:31.820> this<00:34:32.120> is<00:34:32.179> from<00:34:32.510> the<00:34:33.250> etherium 00:34:34.240 --> 00:34:34.250 align:start position:0% just you know this is from the etherium 00:34:34.250 --> 00:34:36.580 align:start position:0% just you know this is from the etherium analysis<00:34:34.730> report<00:34:35.149> from<00:34:35.450> lisa<00:34:35.810> authority<00:34:36.290> back 00:34:36.580 --> 00:34:36.590 align:start position:0% analysis report from lisa authority back 00:34:36.590 --> 00:34:38.950 align:start position:0% analysis report from lisa authority back in<00:34:36.820> 2015<00:34:37.820> and<00:34:38.090> it<00:34:38.210> was<00:34:38.300> even<00:34:38.540> you<00:34:38.870> know 00:34:38.950 --> 00:34:38.960 align:start position:0% in 2015 and it was even you know 00:34:38.960 --> 00:34:44.529 align:start position:0% in 2015 and it was even you know discussed<00:34:39.440> in<00:34:40.060> bitcoin<00:34:41.060> before<00:34:41.450> then 00:34:44.529 --> 00:34:44.539 align:start position:0% 00:34:44.539 --> 00:34:47.049 align:start position:0% so<00:34:45.289> yeah<00:34:45.529> the<00:34:46.039> problem<00:34:46.519> with<00:34:46.669> keeping<00:34:46.849> your 00:34:47.049 --> 00:34:47.059 align:start position:0% so yeah the problem with keeping your 00:34:47.059 --> 00:34:51.729 align:start position:0% so yeah the problem with keeping your Merkel<00:34:47.690> proofs<00:34:47.899> up-to-date<00:34:48.409> is<00:34:48.649> that<00:34:50.589> at<00:34:51.589> the 00:34:51.729 --> 00:34:51.739 align:start position:0% Merkel proofs up-to-date is that at the 00:34:51.739 --> 00:34:54.519 align:start position:0% Merkel proofs up-to-date is that at the top<00:34:51.950> is<00:34:52.159> the<00:34:52.429> stake<00:34:52.849> road<00:34:53.029> and<00:34:53.239> then<00:34:53.749> so<00:34:54.379> at<00:34:54.470> the 00:34:54.519 --> 00:34:54.529 align:start position:0% top is the stake road and then so at the 00:34:54.529 --> 00:34:57.970 align:start position:0% top is the stake road and then so at the top<00:34:54.679> of<00:34:54.829> the<00:34:54.889> tree<00:34:55.779> at<00:34:56.779> the<00:34:57.079> bottom<00:34:57.499> are<00:34:57.920> the 00:34:57.970 --> 00:34:57.980 align:start position:0% top of the tree at the bottom are the 00:34:57.980 --> 00:34:59.739 align:start position:0% top of the tree at the bottom are the leaves<00:34:58.279> these<00:34:58.579> are<00:34:58.759> where<00:34:58.910> the<00:34:59.180> accounts<00:34:59.569> are 00:34:59.739 --> 00:34:59.749 align:start position:0% leaves these are where the accounts are 00:34:59.749 --> 00:35:02.739 align:start position:0% leaves these are where the accounts are so<00:35:00.680> your<00:35:01.130> account<00:35:01.369> is<00:35:01.609> one<00:35:01.849> leaf<00:35:02.029> and<00:35:02.239> then 00:35:02.739 --> 00:35:02.749 align:start position:0% so your account is one leaf and then 00:35:02.749 --> 00:35:06.009 align:start position:0% so your account is one leaf and then next<00:35:03.579> next<00:35:04.579> to<00:35:04.670> you<00:35:04.759> is<00:35:04.999> a<00:35:05.029> another<00:35:05.660> account 00:35:06.009 --> 00:35:06.019 align:start position:0% next next to you is a another account 00:35:06.019 --> 00:35:09.999 align:start position:0% next next to you is a another account and<00:35:06.519> that's<00:35:07.519> somebody<00:35:07.670> else's<00:35:07.970> account<00:35:09.009> but 00:35:09.999 --> 00:35:10.009 align:start position:0% and that's somebody else's account but 00:35:10.009 --> 00:35:11.950 align:start position:0% and that's somebody else's account but the<00:35:10.160> branch<00:35:10.489> the<00:35:11.150> the<00:35:11.329> proof<00:35:11.480> data<00:35:11.720> that<00:35:11.900> you 00:35:11.950 --> 00:35:11.960 align:start position:0% the branch the the proof data that you 00:35:11.960 --> 00:35:13.359 align:start position:0% the branch the the proof data that you want<00:35:12.109> to<00:35:12.170> supply<00:35:12.410> is<00:35:12.470> this<00:35:12.799> Merkel<00:35:13.160> branch 00:35:13.359 --> 00:35:13.369 align:start position:0% want to supply is this Merkel branch 00:35:13.369 --> 00:35:16.450 align:start position:0% want to supply is this Merkel branch from<00:35:13.789> you<00:35:14.569> know<00:35:14.769> your<00:35:15.769> leaf<00:35:15.980> account<00:35:16.279> up<00:35:16.430> to 00:35:16.450 --> 00:35:16.460 align:start position:0% from you know your leaf account up to 00:35:16.460 --> 00:35:19.359 align:start position:0% from you know your leaf account up to the<00:35:16.640> state<00:35:16.849> route<00:35:17.059> and<00:35:17.440> in<00:35:18.440> that<00:35:18.890> branch<00:35:19.160> are 00:35:19.359 --> 00:35:19.369 align:start position:0% the state route and in that branch are 00:35:19.369 --> 00:35:23.950 align:start position:0% the state route and in that branch are these<00:35:19.489> intermediate<00:35:19.849> tree<00:35:20.630> nodes<00:35:21.460> now<00:35:22.960> these 00:35:23.950 --> 00:35:23.960 align:start position:0% these intermediate tree nodes now these 00:35:23.960 --> 00:35:28.180 align:start position:0% these intermediate tree nodes now these intermediate<00:35:24.529> tree<00:35:24.710> nodes<00:35:25.809> change<00:35:26.809> when<00:35:27.380> the 00:35:28.180 --> 00:35:28.190 align:start position:0% intermediate tree nodes change when the 00:35:28.190 --> 00:35:30.549 align:start position:0% intermediate tree nodes change when the guy<00:35:28.309> next<00:35:28.519> to<00:35:28.670> you<00:35:28.789> makes<00:35:29.180> a<00:35:29.269> transaction<00:35:29.869> so 00:35:30.549 --> 00:35:30.559 align:start position:0% guy next to you makes a transaction so 00:35:30.559 --> 00:35:34.390 align:start position:0% guy next to you makes a transaction so it's<00:35:30.829> not<00:35:30.950> so<00:35:31.339> if<00:35:31.640> you<00:35:32.239> go<00:35:32.359> offline<00:35:32.749> and<00:35:33.400> then 00:35:34.390 --> 00:35:34.400 align:start position:0% it's not so if you go offline and then 00:35:34.400 --> 00:35:36.339 align:start position:0% it's not so if you go offline and then you<00:35:34.519> come<00:35:34.759> back<00:35:34.789> it<00:35:35.720> doesn't<00:35:35.989> matter<00:35:36.140> that<00:35:36.200> you 00:35:36.339 --> 00:35:36.349 align:start position:0% you come back it doesn't matter that you 00:35:36.349 --> 00:35:38.229 align:start position:0% you come back it doesn't matter that you didn't<00:35:36.529> make<00:35:36.619> any<00:35:36.769> transactions<00:35:37.400> it<00:35:37.880> matters 00:35:38.229 --> 00:35:38.239 align:start position:0% didn't make any transactions it matters 00:35:38.239 --> 00:35:40.029 align:start position:0% didn't make any transactions it matters that<00:35:38.269> you<00:35:39.109> know<00:35:39.230> other<00:35:39.470> people<00:35:39.829> are<00:35:39.890> making 00:35:40.029 --> 00:35:40.039 align:start position:0% that you know other people are making 00:35:40.039 --> 00:35:42.400 align:start position:0% that you know other people are making transactions<00:35:40.759> and<00:35:41.059> now<00:35:41.779> your<00:35:41.989> proof<00:35:42.170> is<00:35:42.289> out 00:35:42.400 --> 00:35:42.410 align:start position:0% transactions and now your proof is out 00:35:42.410 --> 00:35:45.180 align:start position:0% transactions and now your proof is out of<00:35:42.440> date<00:35:42.680> so<00:35:43.279> you<00:35:43.309> have<00:35:43.609> to<00:35:43.789> go<00:35:44.569> back<00:35:44.779> in 00:35:45.180 --> 00:35:45.190 align:start position:0% of date so you have to go back in 00:35:45.190 --> 00:35:48.009 align:start position:0% of date so you have to go back in history<00:35:46.190> and<00:35:46.430> kind<00:35:46.700> of<00:35:46.849> reprocess<00:35:47.839> these 00:35:48.009 --> 00:35:48.019 align:start position:0% history and kind of reprocess these 00:35:48.019 --> 00:35:49.930 align:start position:0% history and kind of reprocess these transactions<00:35:48.710> to<00:35:48.890> get<00:35:49.039> your<00:35:49.220> proofs<00:35:49.670> up<00:35:49.819> to 00:35:49.930 --> 00:35:49.940 align:start position:0% transactions to get your proofs up to 00:35:49.940 --> 00:35:59.170 align:start position:0% transactions to get your proofs up to date<00:35:57.099> yeah<00:35:58.099> so<00:35:58.309> people<00:35:58.549> really<00:35:58.730> don't<00:35:58.970> like 00:35:59.170 --> 00:35:59.180 align:start position:0% date yeah so people really don't like 00:35:59.180 --> 00:36:02.529 align:start position:0% date yeah so people really don't like either<00:36:00.140> statelessness<00:36:00.950> or<00:36:01.279> storage<00:36:01.609> rent<00:36:01.849> the 00:36:02.529 --> 00:36:02.539 align:start position:0% either statelessness or storage rent the 00:36:02.539 --> 00:36:04.539 align:start position:0% either statelessness or storage rent the reason<00:36:02.839> they<00:36:02.960> don't<00:36:03.049> like<00:36:03.200> statelessness<00:36:04.160> is 00:36:04.539 --> 00:36:04.549 align:start position:0% reason they don't like statelessness is 00:36:04.549 --> 00:36:07.839 align:start position:0% reason they don't like statelessness is because<00:36:05.619> again<00:36:06.619> the<00:36:07.190> problem<00:36:07.489> of<00:36:07.549> keeping 00:36:07.839 --> 00:36:07.849 align:start position:0% because again the problem of keeping 00:36:07.849 --> 00:36:12.539 align:start position:0% because again the problem of keeping your<00:36:07.970> merkel<00:36:08.720> proofs<00:36:08.930> up-to-date<00:36:09.849> also 00:36:12.539 --> 00:36:12.549 align:start position:0% your merkel proofs up-to-date also 00:36:12.549 --> 00:36:16.239 align:start position:0% your merkel proofs up-to-date also somebody<00:36:13.549> who<00:36:14.230> flirts<00:36:15.230> and<00:36:15.470> smokes<00:36:16.009> weed<00:36:16.220> a 00:36:16.239 --> 00:36:16.249 align:start position:0% somebody who flirts and smokes weed a 00:36:16.249 --> 00:36:19.539 align:start position:0% somebody who flirts and smokes weed a lot<00:36:16.460> such<00:36:17.180> that<00:36:17.660> when<00:36:18.589> I<00:36:18.859> wake<00:36:19.279> up<00:36:19.430> from 00:36:19.539 --> 00:36:19.549 align:start position:0% lot such that when I wake up from 00:36:19.549 --> 00:36:22.749 align:start position:0% lot such that when I wake up from Crowley<00:36:20.059> if<00:36:20.150> I<00:36:20.239> just<00:36:20.390> want<00:36:20.599> my<00:36:21.460> brain<00:36:22.460> wallet 00:36:22.749 --> 00:36:22.759 align:start position:0% Crowley if I just want my brain wallet 00:36:22.759 --> 00:36:29.499 align:start position:0% Crowley if I just want my brain wallet to<00:36:22.880> work<00:36:23.059> I<00:36:23.619> don't<00:36:24.619> want<00:36:25.069> to<00:36:25.970> have<00:36:26.119> to<00:36:28.450> you<00:36:29.450> know 00:36:29.499 --> 00:36:29.509 align:start position:0% to work I don't want to have to you know 00:36:29.509 --> 00:36:34.479 align:start position:0% to work I don't want to have to you know you<00:36:30.230> imagine<00:36:30.920> if<00:36:31.039> 50<00:36:31.519> years<00:36:31.640> later<00:36:33.190> your<00:36:34.190> proof 00:36:34.479 --> 00:36:34.489 align:start position:0% you imagine if 50 years later your proof 00:36:34.489 --> 00:36:36.160 align:start position:0% you imagine if 50 years later your proof would<00:36:34.670> have<00:36:34.789> just<00:36:35.029> been<00:36:35.119> changed<00:36:35.660> like<00:36:35.869> you 00:36:36.160 --> 00:36:36.170 align:start position:0% would have just been changed like you 00:36:36.170 --> 00:36:37.239 align:start position:0% would have just been changed like you know<00:36:36.259> within<00:36:36.470> the<00:36:36.559> first<00:36:36.619> year<00:36:36.920> after<00:36:37.190> you 00:36:37.239 --> 00:36:37.249 align:start position:0% know within the first year after you 00:36:37.249 --> 00:36:41.289 align:start position:0% know within the first year after you went<00:36:37.400> to<00:36:37.430> sleep<00:36:37.660> so<00:36:39.309> if<00:36:40.309> those<00:36:40.730> blocks<00:36:41.119> are 00:36:41.289 --> 00:36:41.299 align:start position:0% went to sleep so if those blocks are 00:36:41.299 --> 00:36:42.759 align:start position:0% went to sleep so if those blocks are still<00:36:41.509> available<00:36:41.690> somewhere<00:36:42.259> then<00:36:42.619> you're 00:36:42.759 --> 00:36:42.769 align:start position:0% still available somewhere then you're 00:36:42.769 --> 00:36:45.910 align:start position:0% still available somewhere then you're okay<00:36:43.069> but<00:36:43.489> the<00:36:43.730> question<00:36:44.329> is<00:36:44.480> you<00:36:44.900> know<00:36:44.930> what 00:36:45.910 --> 00:36:45.920 align:start position:0% okay but the question is you know what 00:36:45.920 --> 00:36:48.220 align:start position:0% okay but the question is you know what happens<00:36:46.220> if<00:36:46.339> those<00:36:46.489> blocks<00:36:46.849> are<00:36:47.180> no<00:36:48.019> longer 00:36:48.220 --> 00:36:48.230 align:start position:0% happens if those blocks are no longer 00:36:48.230 --> 00:36:53.769 align:start position:0% happens if those blocks are no longer available<00:36:48.940> then<00:36:50.170> well<00:36:51.200> you're<00:36:51.529> screwed<00:36:52.779> and 00:36:53.769 --> 00:36:53.779 align:start position:0% available then well you're screwed and 00:36:53.779 --> 00:36:57.130 align:start position:0% available then well you're screwed and that's<00:36:54.769> kind<00:36:55.009> of<00:36:55.069> why<00:36:55.190> people<00:36:55.519> also<00:36:56.049> you<00:36:57.049> know 00:36:57.130 --> 00:36:57.140 align:start position:0% that's kind of why people also you know 00:36:57.140 --> 00:36:57.790 align:start position:0% that's kind of why people also you know you 00:36:57.790 --> 00:36:57.800 align:start position:0% you 00:36:57.800 --> 00:36:59.980 align:start position:0% you say<00:36:58.190> setup<00:36:58.880> there<00:36:59.180> could<00:36:59.330> be<00:36:59.360> some<00:36:59.570> service 00:36:59.980 --> 00:36:59.990 align:start position:0% say setup there could be some service 00:36:59.990 --> 00:37:03.370 align:start position:0% say setup there could be some service that<00:37:00.260> says<00:37:00.440> I<00:37:00.590> promise<00:37:00.980> I<00:37:01.130> will<00:37:01.190> store<00:37:02.380> you 00:37:03.370 --> 00:37:03.380 align:start position:0% that says I promise I will store you 00:37:03.380 --> 00:37:05.170 align:start position:0% that says I promise I will store you know<00:37:03.470> all<00:37:03.830> the<00:37:04.070> old<00:37:04.190> blocks<00:37:04.430> even<00:37:04.850> if<00:37:04.940> you<00:37:05.030> come 00:37:05.170 --> 00:37:05.180 align:start position:0% know all the old blocks even if you come 00:37:05.180 --> 00:37:07.510 align:start position:0% know all the old blocks even if you come back<00:37:05.300> 50<00:37:05.630> years<00:37:05.890> trust<00:37:06.890> me<00:37:07.010> they'll<00:37:07.190> be<00:37:07.220> here 00:37:07.510 --> 00:37:07.520 align:start position:0% back 50 years trust me they'll be here 00:37:07.520 --> 00:37:09.460 align:start position:0% back 50 years trust me they'll be here and<00:37:07.900> people<00:37:08.900> say<00:37:09.050> well<00:37:09.140> I<00:37:09.170> don't<00:37:09.290> want<00:37:09.410> to 00:37:09.460 --> 00:37:09.470 align:start position:0% and people say well I don't want to 00:37:09.470 --> 00:37:11.350 align:start position:0% and people say well I don't want to trust<00:37:09.680> these<00:37:09.860> rickety<00:37:10.160> you<00:37:10.760> know<00:37:10.850> layer<00:37:11.120> 2 00:37:11.350 --> 00:37:11.360 align:start position:0% trust these rickety you know layer 2 00:37:11.360 --> 00:37:14.260 align:start position:0% trust these rickety you know layer 2 services<00:37:11.990> I<00:37:12.020> want<00:37:12.500> you<00:37:13.040> know<00:37:13.160> about<00:37:13.730> to<00:37:14.180> have 00:37:14.260 --> 00:37:14.270 align:start position:0% services I want you know about to have 00:37:14.270 --> 00:37:16.240 align:start position:0% services I want you know about to have some<00:37:14.480> guarantee<00:37:14.630> that<00:37:15.140> validators<00:37:15.860> will<00:37:16.070> be 00:37:16.240 --> 00:37:16.250 align:start position:0% some guarantee that validators will be 00:37:16.250 --> 00:37:23.020 align:start position:0% some guarantee that validators will be storing<00:37:16.520> my<00:37:17.410> my<00:37:18.410> account<00:37:20.200> obviously<00:37:22.030> people 00:37:23.020 --> 00:37:23.030 align:start position:0% storing my my account obviously people 00:37:23.030 --> 00:37:24.640 align:start position:0% storing my my account obviously people dislike<00:37:23.330> rent<00:37:23.570> because<00:37:23.870> you<00:37:24.110> get<00:37:24.230> evicted<00:37:24.410> if 00:37:24.640 --> 00:37:24.650 align:start position:0% dislike rent because you get evicted if 00:37:24.650 --> 00:37:27.640 align:start position:0% dislike rent because you get evicted if you<00:37:24.740> don't<00:37:24.890> pay<00:37:25.070> also<00:37:26.440> capacity<00:37:27.440> is<00:37:27.530> limited 00:37:27.640 --> 00:37:27.650 align:start position:0% you don't pay also capacity is limited 00:37:27.650 --> 00:37:34.090 align:start position:0% you don't pay also capacity is limited so<00:37:28.100> the<00:37:28.400> you<00:37:28.910> know<00:37:29.000> fees<00:37:29.390> can<00:37:29.750> spike<00:37:30.380> high<00:37:33.100> it 00:37:34.090 --> 00:37:34.100 align:start position:0% so the you know fees can spike high it 00:37:34.100 --> 00:37:37.030 align:start position:0% so the you know fees can spike high it breaks<00:37:34.460> user<00:37:35.000> experience<00:37:35.600> that<00:37:36.320> we've<00:37:36.560> you 00:37:37.030 --> 00:37:37.040 align:start position:0% breaks user experience that we've you 00:37:37.040 --> 00:37:39.520 align:start position:0% breaks user experience that we've you know<00:37:37.070> come<00:37:37.820> to<00:37:37.850> expect<00:37:38.300> that<00:37:38.480> a<00:37:38.840> contract<00:37:39.380> will 00:37:39.520 --> 00:37:39.530 align:start position:0% know come to expect that a contract will 00:37:39.530 --> 00:37:42.220 align:start position:0% know come to expect that a contract will still<00:37:39.740> be<00:37:39.890> there<00:37:40.570> there<00:37:41.570> are<00:37:41.660> workarounds<00:37:41.990> for 00:37:42.220 --> 00:37:42.230 align:start position:0% still be there there are workarounds for 00:37:42.230 --> 00:37:46.210 align:start position:0% still be there there are workarounds for this<00:37:42.470> like<00:37:42.800> if<00:37:44.140> you<00:37:45.140> know<00:37:45.230> again<00:37:45.500> this<00:37:45.680> sleep 00:37:46.210 --> 00:37:46.220 align:start position:0% this like if you know again this sleep 00:37:46.220 --> 00:37:48.300 align:start position:0% this like if you know again this sleep in<00:37:46.370> awake<00:37:46.580> but<00:37:46.850> that's<00:37:47.000> just<00:37:47.210> you<00:37:47.660> know<00:37:47.690> adds 00:37:48.300 --> 00:37:48.310 align:start position:0% in awake but that's just you know adds 00:37:48.310 --> 00:37:51.940 align:start position:0% in awake but that's just you know adds its<00:37:49.310> complexity<00:37:49.880> which<00:37:50.750> maybe<00:37:50.960> you<00:37:51.080> can<00:37:51.290> tuck 00:37:51.940 --> 00:37:51.950 align:start position:0% its complexity which maybe you can tuck 00:37:51.950 --> 00:37:55.150 align:start position:0% its complexity which maybe you can tuck under<00:37:52.220> the<00:37:52.310> hood<00:37:53.470> from<00:37:54.470> the<00:37:54.650> implementers 00:37:55.150 --> 00:37:55.160 align:start position:0% under the hood from the implementers 00:37:55.160 --> 00:37:56.920 align:start position:0% under the hood from the implementers point<00:37:55.400> of<00:37:55.490> view<00:37:55.610> if<00:37:56.390> you're<00:37:56.570> starting<00:37:56.840> from 00:37:56.920 --> 00:37:56.930 align:start position:0% point of view if you're starting from 00:37:56.930 --> 00:38:00.240 align:start position:0% point of view if you're starting from scratch<00:37:56.990> then<00:37:57.620> in<00:37:58.070> my<00:37:58.280> opinion<00:37:58.360> stateless<00:37:59.360> is 00:38:00.240 --> 00:38:00.250 align:start position:0% scratch then in my opinion stateless is 00:38:00.250 --> 00:38:02.770 align:start position:0% scratch then in my opinion stateless is obviously<00:38:01.250> the<00:38:01.400> way<00:38:01.490> to<00:38:01.550> go<00:38:01.730> it's<00:38:02.330> clean 00:38:02.770 --> 00:38:02.780 align:start position:0% obviously the way to go it's clean 00:38:02.780 --> 00:38:08.560 align:start position:0% obviously the way to go it's clean simple<00:38:04.330> it's<00:38:05.330> ideal<00:38:05.990> about<00:38:07.270> validator<00:38:08.270> only 00:38:08.560 --> 00:38:08.570 align:start position:0% simple it's ideal about validator only 00:38:08.570 --> 00:38:13.180 align:start position:0% simple it's ideal about validator only has<00:38:08.690> to<00:38:08.810> store<00:38:09.080> a<00:38:09.350> 32<00:38:10.160> byte<00:38:10.340> State<00:38:10.970> Road<00:38:12.190> rent 00:38:13.180 --> 00:38:13.190 align:start position:0% has to store a 32 byte State Road rent 00:38:13.190 --> 00:38:15.730 align:start position:0% has to store a 32 byte State Road rent is<00:38:13.430> messy<00:38:14.330> and<00:38:14.360> complex<00:38:14.870> there<00:38:15.170> are<00:38:15.200> lots<00:38:15.590> of 00:38:15.730 --> 00:38:15.740 align:start position:0% is messy and complex there are lots of 00:38:15.740 --> 00:38:17.650 align:start position:0% is messy and complex there are lots of parameters<00:38:15.950> you<00:38:16.310> have<00:38:16.400> to<00:38:16.460> decide<00:38:16.730> well<00:38:17.030> you 00:38:17.650 --> 00:38:17.660 align:start position:0% parameters you have to decide well you 00:38:17.660 --> 00:38:20.440 align:start position:0% parameters you have to decide well you know<00:38:17.780> I<00:38:18.020> mean<00:38:18.680> do<00:38:19.010> you<00:38:19.040> set<00:38:19.280> it<00:38:19.370> at<00:38:19.460> 16<00:38:19.850> gigs<00:38:20.120> or 00:38:20.440 --> 00:38:20.450 align:start position:0% know I mean do you set it at 16 gigs or 00:38:20.450 --> 00:38:23.140 align:start position:0% know I mean do you set it at 16 gigs or 32<00:38:20.930> gigs<00:38:21.230> and<00:38:21.530> then<00:38:21.590> you<00:38:22.400> know<00:38:22.520> how<00:38:22.880> do<00:38:22.940> you<00:38:23.060> do 00:38:23.140 --> 00:38:23.150 align:start position:0% 32 gigs and then you know how do you do 00:38:23.150 --> 00:38:25.120 align:start position:0% 32 gigs and then you know how do you do the<00:38:23.270> fee<00:38:23.420> market<00:38:23.810> so<00:38:24.020> forth 00:38:25.120 --> 00:38:25.130 align:start position:0% the fee market so forth 00:38:25.130 --> 00:38:29.800 align:start position:0% the fee market so forth I<00:38:26.410> think<00:38:27.410> some<00:38:28.370> people<00:38:28.490> even<00:38:28.880> the<00:38:29.420> stateless 00:38:29.800 --> 00:38:29.810 align:start position:0% I think some people even the stateless 00:38:29.810 --> 00:38:32.230 align:start position:0% I think some people even the stateless is<00:38:30.020> almost<00:38:30.350> too<00:38:30.620> simple<00:38:30.860> so<00:38:31.610> they<00:38:31.880> just<00:38:32.030> like 00:38:32.230 --> 00:38:32.240 align:start position:0% is almost too simple so they just like 00:38:32.240 --> 00:38:34.120 align:start position:0% is almost too simple so they just like you<00:38:32.600> know<00:38:32.720> engineers<00:38:33.410> who<00:38:33.560> sometimes<00:38:33.770> like 00:38:34.120 --> 00:38:34.130 align:start position:0% you know engineers who sometimes like 00:38:34.130 --> 00:38:36.130 align:start position:0% you know engineers who sometimes like complexity<00:38:34.700> and<00:38:34.910> they<00:38:35.630> just<00:38:35.780> can't<00:38:35.990> resist 00:38:36.130 --> 00:38:36.140 align:start position:0% complexity and they just can't resist 00:38:36.140 --> 00:38:39.400 align:start position:0% complexity and they just can't resist from<00:38:36.650> adding<00:38:37.520> a<00:38:37.700> rent<00:38:37.970> feature<00:38:38.260> onto<00:38:39.260> the 00:38:39.400 --> 00:38:39.410 align:start position:0% from adding a rent feature onto the 00:38:39.410 --> 00:38:43.120 align:start position:0% from adding a rent feature onto the stateless<00:38:40.390> I<00:38:41.590> mean<00:38:42.590> if<00:38:42.680> you're<00:38:42.770> not<00:38:42.800> starting 00:38:43.120 --> 00:38:43.130 align:start position:0% stateless I mean if you're not starting 00:38:43.130 --> 00:38:45.220 align:start position:0% stateless I mean if you're not starting from<00:38:43.220> scratch<00:38:43.460> so<00:38:43.760> if<00:38:43.850> you<00:38:43.940> have<00:38:44.060> like<00:38:44.330> if 00:38:45.220 --> 00:38:45.230 align:start position:0% from scratch so if you have like if 00:38:45.230 --> 00:38:48.490 align:start position:0% from scratch so if you have like if you're<00:38:45.470> in<00:38:45.560> 1.0<00:38:45.980> today<00:38:46.310> then<00:38:46.960> it's<00:38:47.960> probably 00:38:48.490 --> 00:38:48.500 align:start position:0% you're in 1.0 today then it's probably 00:38:48.500 --> 00:38:51.520 align:start position:0% you're in 1.0 today then it's probably easier<00:38:48.860> you<00:38:49.430> already<00:38:49.940> have<00:38:50.090> a<00:38:50.120> whole<00:38:50.530> tree 00:38:51.520 --> 00:38:51.530 align:start position:0% easier you already have a whole tree 00:38:51.530 --> 00:38:55.210 align:start position:0% easier you already have a whole tree that<00:38:51.830> the<00:38:51.920> miner<00:38:52.100> is<00:38:52.280> forced<00:38:52.610> to<00:38:53.920> to<00:38:54.920> store 00:38:55.210 --> 00:38:55.220 align:start position:0% that the miner is forced to to store 00:38:55.220 --> 00:38:58.510 align:start position:0% that the miner is forced to to store it's<00:38:55.880> probably<00:38:56.240> easier<00:38:56.540> to<00:38:56.840> you<00:38:57.500> know<00:38:57.620> add<00:38:58.010> on 00:38:58.510 --> 00:38:58.520 align:start position:0% it's probably easier to you know add on 00:38:58.520 --> 00:39:00.850 align:start position:0% it's probably easier to you know add on a<00:38:58.550> rent<00:38:58.820> feature<00:38:59.060> and<00:38:59.510> you<00:39:00.500> know<00:39:00.590> start 00:39:00.850 --> 00:39:00.860 align:start position:0% a rent feature and you know start 00:39:00.860 --> 00:39:08.860 align:start position:0% a rent feature and you know start trimming<00:39:01.130> the<00:39:01.550> accounts<00:39:07.300> then<00:39:08.300> you<00:39:08.780> know 00:39:08.860 --> 00:39:08.870 align:start position:0% trimming the accounts then you know 00:39:08.870 --> 00:39:10.600 align:start position:0% trimming the accounts then you know swapping<00:39:09.320> out<00:39:09.410> the<00:39:09.740> whole<00:39:10.280> thing<00:39:10.310> and 00:39:10.600 --> 00:39:10.610 align:start position:0% swapping out the whole thing and 00:39:10.610 --> 00:39:11.590 align:start position:0% swapping out the whole thing and switching<00:39:11.000> to<00:39:11.090> stateless 00:39:11.590 --> 00:39:11.600 align:start position:0% switching to stateless 00:39:11.600 --> 00:39:17.380 align:start position:0% switching to stateless so<00:39:12.410> lastly<00:39:14.140> point<00:39:15.140> is<00:39:15.260> that<00:39:15.530> change<00:39:16.520> is<00:39:16.910> coming 00:39:17.380 --> 00:39:17.390 align:start position:0% so lastly point is that change is coming 00:39:17.390 --> 00:39:18.990 align:start position:0% so lastly point is that change is coming here 00:39:18.990 --> 00:39:19.000 align:start position:0% here 00:39:19.000 --> 00:39:22.380 align:start position:0% here currently<00:39:20.000> minors<00:39:20.870> have<00:39:21.410> this<00:39:21.590> full<00:39:21.860> burden 00:39:22.380 --> 00:39:22.390 align:start position:0% currently minors have this full burden 00:39:22.390 --> 00:39:25.960 align:start position:0% currently minors have this full burden and<00:39:23.710> while<00:39:24.710> it's<00:39:24.890> you<00:39:25.190> know<00:39:25.280> it<00:39:25.490> seems<00:39:25.760> kind<00:39:25.940> of 00:39:25.960 --> 00:39:25.970 align:start position:0% and while it's you know it seems kind of 00:39:25.970 --> 00:39:28.360 align:start position:0% and while it's you know it seems kind of easy<00:39:26.150> because<00:39:26.390> you<00:39:27.050> know<00:39:27.080> somebody<00:39:27.410> else's<00:39:27.830> I 00:39:28.360 --> 00:39:28.370 align:start position:0% easy because you know somebody else's I 00:39:28.370 --> 00:39:30.490 align:start position:0% easy because you know somebody else's I don't<00:39:29.030> know<00:39:29.090> if<00:39:29.150> you're<00:39:29.270> using<00:39:29.450> in<00:39:29.630> inferior 00:39:30.490 --> 00:39:30.500 align:start position:0% don't know if you're using in inferior 00:39:30.500 --> 00:39:34.780 align:start position:0% don't know if you're using in inferior or<00:39:30.650> made<00:39:30.800> a<00:39:30.830> mask<00:39:31.100> or<00:39:31.340> a<00:39:31.610> light<00:39:31.880> client<00:39:33.490> it<00:39:34.490> you 00:39:34.780 --> 00:39:34.790 align:start position:0% or made a mask or a light client it you 00:39:34.790 --> 00:39:36.940 align:start position:0% or made a mask or a light client it you know<00:39:34.880> it's<00:39:35.210> relatively<00:39:35.870> easy<00:39:35.960> to<00:39:36.230> sink<00:39:36.770> if 00:39:36.940 --> 00:39:36.950 align:start position:0% know it's relatively easy to sink if 00:39:36.950 --> 00:39:38.320 align:start position:0% know it's relatively easy to sink if you're<00:39:37.100> running<00:39:37.310> a<00:39:37.460> full<00:39:37.670> note<00:39:37.880> it's<00:39:38.090> still 00:39:38.320 --> 00:39:38.330 align:start position:0% you're running a full note it's still 00:39:38.330 --> 00:39:43.120 align:start position:0% you're running a full note it's still difficult<00:39:38.540> to<00:39:38.810> sink<00:39:40.840> what<00:39:41.840> is<00:39:42.100> going<00:39:43.100> to 00:39:43.120 --> 00:39:43.130 align:start position:0% difficult to sink what is going to 00:39:43.130 --> 00:39:43.570 align:start position:0% difficult to sink what is going to happen 00:39:43.570 --> 00:39:43.580 align:start position:0% happen 00:39:43.580 --> 00:39:48.370 align:start position:0% happen is<00:39:43.790> that<00:39:45.520> it's<00:39:46.520> not<00:39:46.700> sustainable<00:39:46.910> for<00:39:47.380> miners 00:39:48.370 --> 00:39:48.380 align:start position:0% is that it's not sustainable for miners 00:39:48.380 --> 00:39:51.180 align:start position:0% is that it's not sustainable for miners to<00:39:48.530> keep<00:39:48.710> storing<00:39:48.920> all<00:39:49.070> the<00:39:49.130> state<00:39:49.370> so 00:39:51.180 --> 00:39:51.190 align:start position:0% to keep storing all the state so 00:39:51.190 --> 00:39:55.030 align:start position:0% to keep storing all the state so validators<00:39:52.190> are<00:39:53.500> the<00:39:54.500> gist<00:39:54.680> space<00:39:54.830> is<00:39:54.950> going 00:39:55.030 --> 00:39:55.040 align:start position:0% validators are the gist space is going 00:39:55.040 --> 00:39:58.050 align:start position:0% validators are the gist space is going to<00:39:55.130> be<00:39:55.220> minimized<00:39:55.610> the<00:39:56.420> core<00:39:57.230> of<00:39:57.260> the<00:39:57.410> network 00:39:58.050 --> 00:39:58.060 align:start position:0% to be minimized the core of the network 00:39:58.060 --> 00:40:00.550 align:start position:0% to be minimized the core of the network you'll<00:39:59.060> be<00:39:59.150> able<00:39:59.300> to<00:39:59.360> sink<00:39:59.600> very<00:39:59.810> quick<00:40:00.320> so 00:40:00.550 --> 00:40:00.560 align:start position:0% you'll be able to sink very quick so 00:40:00.560 --> 00:40:06.970 align:start position:0% you'll be able to sink very quick so lifer<00:40:01.250> a<00:40:01.280> validator<00:40:01.760> will<00:40:02.740> become<00:40:03.740> great<00:40:05.980> you 00:40:06.970 --> 00:40:06.980 align:start position:0% lifer a validator will become great you 00:40:06.980 --> 00:40:08.950 align:start position:0% lifer a validator will become great you know<00:40:07.100> the<00:40:07.490> process<00:40:07.700> of<00:40:08.090> sinking<00:40:08.660> and 00:40:08.950 --> 00:40:08.960 align:start position:0% know the process of sinking and 00:40:08.960 --> 00:40:10.720 align:start position:0% know the process of sinking and processing<00:40:09.650> blocks<00:40:09.920> will<00:40:10.100> become<00:40:10.220> very 00:40:10.720 --> 00:40:10.730 align:start position:0% processing blocks will become very 00:40:10.730 --> 00:40:14.200 align:start position:0% processing blocks will become very streamlined<00:40:11.410> but<00:40:12.410> on<00:40:12.560> the<00:40:12.710> other<00:40:12.830> hand<00:40:13.130> if<00:40:13.490> you 00:40:14.200 --> 00:40:14.210 align:start position:0% streamlined but on the other hand if you 00:40:14.210 --> 00:40:18.550 align:start position:0% streamlined but on the other hand if you are<00:40:14.240> a<00:40:14.420> user<00:40:14.750> or<00:40:15.170> a<00:40:15.440> wallet<00:40:15.860> client<00:40:17.410> life<00:40:18.410> is 00:40:18.550 --> 00:40:18.560 align:start position:0% are a user or a wallet client life is 00:40:18.560 --> 00:40:21.910 align:start position:0% are a user or a wallet client life is going<00:40:19.010> to<00:40:19.130> get<00:40:19.280> somewhat<00:40:20.240> painful<00:40:20.830> sinking<00:40:21.830> is 00:40:21.910 --> 00:40:21.920 align:start position:0% going to get somewhat painful sinking is 00:40:21.920 --> 00:40:26.830 align:start position:0% going to get somewhat painful sinking is going<00:40:22.190> to<00:40:22.250> be<00:40:22.370> harder<00:40:24.010> scraping<00:40:25.630> you<00:40:26.630> know<00:40:26.750> if 00:40:26.830 --> 00:40:26.840 align:start position:0% going to be harder scraping you know if 00:40:26.840 --> 00:40:28.840 align:start position:0% going to be harder scraping you know if the<00:40:26.960> data<00:40:27.200> to<00:40:27.560> you'll<00:40:28.370> have<00:40:28.490> to<00:40:28.580> manage<00:40:28.790> your 00:40:28.840 --> 00:40:28.850 align:start position:0% the data to you'll have to manage your 00:40:28.850 --> 00:40:29.920 align:start position:0% the data to you'll have to manage your own<00:40:28.940> data<00:40:29.210> you<00:40:29.360> have<00:40:29.480> to<00:40:29.510> come<00:40:29.690> up<00:40:29.720> with<00:40:29.840> your 00:40:29.920 --> 00:40:29.930 align:start position:0% own data you have to come up with your 00:40:29.930 --> 00:40:33.010 align:start position:0% own data you have to come up with your own<00:40:29.990> proofs<00:40:30.790> unless<00:40:31.790> you<00:40:31.970> you<00:40:32.330> know<00:40:32.420> can<00:40:32.870> pay 00:40:33.010 --> 00:40:33.020 align:start position:0% own proofs unless you you know can pay 00:40:33.020 --> 00:40:40.120 align:start position:0% own proofs unless you you know can pay the<00:40:33.140> rent<00:40:34.150> so<00:40:37.660> that's<00:40:38.660> it<00:40:38.840> I<00:40:38.870> mean<00:40:39.070> you<00:40:40.070> know 00:40:40.120 --> 00:40:40.130 align:start position:0% the rent so that's it I mean you know 00:40:40.130 --> 00:40:42.340 align:start position:0% the rent so that's it I mean you know while<00:40:40.310> it<00:40:40.400> developers<00:40:40.910> are<00:40:41.180> gonna<00:40:42.110> have<00:40:42.230> a 00:40:42.340 --> 00:40:42.350 align:start position:0% while it developers are gonna have a 00:40:42.350 --> 00:40:52.140 align:start position:0% while it developers are gonna have a tough<00:40:43.100> time<00:40:45.490> okay<00:40:47.350> thanks 00:40:52.140 --> 00:40:52.150 align:start position:0% 00:40:52.150 --> 00:41:01.380 align:start position:0% Thank<00:40:53.150> You<00:40:53.299> KC<00:40:57.069> big<00:40:58.069> applause<00:40:58.400> for<00:40:58.430> KC<00:40:58.849> again 00:41:01.380 --> 00:41:01.390 align:start position:0% 00:41:01.390 --> 00:41:04.109 align:start position:0% [Applause] 00:41:04.109 --> 00:41:04.119 align:start position:0% [Applause] 00:41:04.119 --> 00:41:07.299 align:start position:0% [Applause] so<00:41:05.119> thank<00:41:05.329> you<00:41:05.480> all<00:41:05.509> for<00:41:05.799> being<00:41:06.799> here<00:41:06.920> today 00:41:07.299 --> 00:41:07.309 align:start position:0% so thank you all for being here today 00:41:07.309 --> 00:41:09.999 align:start position:0% so thank you all for being here today we're<00:41:08.089> gonna<00:41:08.180> pull<00:41:08.390> up<00:41:08.480> the<00:41:08.660> the<00:41:09.170> URLs<00:41:09.529> again 00:41:09.999 --> 00:41:10.009 align:start position:0% we're gonna pull up the the URLs again 00:41:10.009 --> 00:41:12.789 align:start position:0% we're gonna pull up the the URLs again please<00:41:10.430> join<00:41:10.670> the<00:41:10.819> Gator<00:41:10.970> room<00:41:11.410> try<00:41:12.410> the<00:41:12.470> test 00:41:12.789 --> 00:41:12.799 align:start position:0% please join the Gator room try the test 00:41:12.799 --> 00:41:14.859 align:start position:0% please join the Gator room try the test net<00:41:13.039> the<00:41:13.220> URL<00:41:13.519> for<00:41:13.670> that<00:41:13.700> it's<00:41:13.940> II<00:41:14.180> wasn't<00:41:14.509> that 00:41:14.859 --> 00:41:14.869 align:start position:0% net the URL for that it's II wasn't that 00:41:14.869 --> 00:41:17.920 align:start position:0% net the URL for that it's II wasn't that material<00:41:15.349> the<00:41:15.499> doric<00:41:15.970> all<00:41:16.970> the<00:41:17.359> demo<00:41:17.630> what 00:41:17.920 --> 00:41:17.930 align:start position:0% material the doric all the demo what 00:41:17.930 --> 00:41:19.809 align:start position:0% material the doric all the demo what Jarrett<00:41:18.739> has<00:41:18.859> shown<00:41:19.099> should<00:41:19.430> be<00:41:19.519> visible 00:41:19.809 --> 00:41:19.819 align:start position:0% Jarrett has shown should be visible 00:41:19.819 --> 00:41:23.049 align:start position:0% Jarrett has shown should be visible they're<00:41:20.499> joined<00:41:21.499> Gator<00:41:21.710> again<00:41:21.970> get<00:41:22.970> the 00:41:23.049 --> 00:41:23.059 align:start position:0% they're joined Gator again get the 00:41:23.059 --> 00:41:25.150 align:start position:0% they're joined Gator again get the discussion<00:41:23.329> started<00:41:23.739> we're<00:41:24.739> gonna<00:41:24.890> have<00:41:25.039> the 00:41:25.150 --> 00:41:25.160 align:start position:0% discussion started we're gonna have the 00:41:25.160 --> 00:41:28.329 align:start position:0% discussion started we're gonna have the CVM<00:41:25.489> panel<00:41:25.759> now<00:41:25.910> focus<00:41:26.809> on<00:41:26.930> EVM<00:41:27.230> we<00:41:28.130> probably 00:41:28.329 --> 00:41:28.339 align:start position:0% CVM panel now focus on EVM we probably 00:41:28.339 --> 00:41:29.680 align:start position:0% CVM panel now focus on EVM we probably gonna<00:41:28.519> be<00:41:28.670> free<00:41:28.849> after<00:41:29.059> that<00:41:29.089> if<00:41:29.329> you<00:41:29.359> guys 00:41:29.680 --> 00:41:29.690 align:start position:0% gonna be free after that if you guys 00:41:29.690 --> 00:41:32.859 align:start position:0% gonna be free after that if you guys have<00:41:29.869> any<00:41:30.049> more<00:41:30.109> questions<00:41:31.630> that's<00:41:32.630> all<00:41:32.749> the 00:41:32.859 --> 00:41:32.869 align:start position:0% have any more questions that's all the 00:41:32.869 --> 00:41:44.220 align:start position:0% have any more questions that's all the details<00:41:33.170> you<00:41:33.289> need<00:41:33.319> to<00:41:33.440> know<00:41:33.529> thank<00:41:34.519> you 00:41:44.220 --> 00:41:44.230 align:start position:0% 00:41:44.230 --> 00:41:46.290 align:start position:0% you