WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:16.930 align:start position:0% [Music] 00:00:16.930 --> 00:00:16.940 align:start position:0% 00:00:16.940 --> 00:00:22.070 align:start position:0% talking<00:00:17.940> about<00:00:18.119> essentially<00:00:18.720> is<00:00:19.020> scaling<00:00:19.800> and 00:00:22.070 --> 00:00:22.080 align:start position:0% talking about essentially is scaling and 00:00:22.080 --> 00:00:24.230 align:start position:0% talking about essentially is scaling and there's<00:00:22.439> some<00:00:22.740> lag<00:00:22.920> but<00:00:23.699> basically<00:00:24.000> there's 00:00:24.230 --> 00:00:24.240 align:start position:0% there's some lag but basically there's 00:00:24.240 --> 00:00:26.269 align:start position:0% there's some lag but basically there's two<00:00:24.420> kinds<00:00:24.720> of<00:00:24.840> scaling<00:00:25.260> vertical<00:00:25.740> scaling 00:00:26.269 --> 00:00:26.279 align:start position:0% two kinds of scaling vertical scaling 00:00:26.279 --> 00:00:30.529 align:start position:0% two kinds of scaling vertical scaling which<00:00:27.119> is<00:00:27.240> when<00:00:27.420> you<00:00:27.599> have<00:00:27.720> a<00:00:28.080> huge<00:00:28.699> machine<00:00:29.699> an 00:00:30.529 --> 00:00:30.539 align:start position:0% which is when you have a huge machine an 00:00:30.539 --> 00:00:32.030 align:start position:0% which is when you have a huge machine an horizontal<00:00:30.960> scaling<00:00:31.380> when<00:00:31.560> you<00:00:31.679> spread<00:00:31.920> the 00:00:32.030 --> 00:00:32.040 align:start position:0% horizontal scaling when you spread the 00:00:32.040 --> 00:00:35.530 align:start position:0% horizontal scaling when you spread the load<00:00:32.340> between<00:00:33.059> multiple<00:00:33.600> machines 00:00:35.530 --> 00:00:35.540 align:start position:0% load between multiple machines 00:00:35.540 --> 00:00:39.170 align:start position:0% load between multiple machines so<00:00:36.540> yeah<00:00:36.719> scaling<00:00:37.559> so<00:00:38.040> basically<00:00:38.399> I<00:00:38.760> mean<00:00:38.880> I 00:00:39.170 --> 00:00:39.180 align:start position:0% so yeah scaling so basically I mean I 00:00:39.180 --> 00:00:40.970 align:start position:0% so yeah scaling so basically I mean I can<00:00:39.300> wing<00:00:39.540> it<00:00:39.660> without<00:00:39.780> the<00:00:40.020> slides<00:00:40.320> by<00:00:40.860> the 00:00:40.970 --> 00:00:40.980 align:start position:0% can wing it without the slides by the 00:00:40.980 --> 00:00:43.670 align:start position:0% can wing it without the slides by the time<00:00:41.100> they<00:00:41.280> come<00:00:41.399> by<00:00:41.579> so<00:00:42.420> in<00:00:43.079> this<00:00:43.260> talk<00:00:43.440> well 00:00:43.670 --> 00:00:43.680 align:start position:0% time they come by so in this talk well 00:00:43.680 --> 00:00:44.930 align:start position:0% time they come by so in this talk well it<00:00:43.860> goes<00:00:44.100> great 00:00:44.930 --> 00:00:44.940 align:start position:0% it goes great 00:00:44.940 --> 00:00:46.910 align:start position:0% it goes great um<00:00:45.000> I<00:00:45.300> want<00:00:45.420> to<00:00:45.540> conceptualize 00:00:46.910 --> 00:00:46.920 align:start position:0% um I want to conceptualize 00:00:46.920 --> 00:00:48.410 align:start position:0% um I want to conceptualize um<00:00:46.980> you<00:00:47.340> know<00:00:47.460> vertical<00:00:47.700> and<00:00:47.940> horizontal 00:00:48.410 --> 00:00:48.420 align:start position:0% um you know vertical and horizontal 00:00:48.420 --> 00:00:50.389 align:start position:0% um you know vertical and horizontal scaling<00:00:48.840> I<00:00:49.500> want<00:00:49.680> to<00:00:49.739> show<00:00:49.860> you<00:00:49.920> a<00:00:50.039> cool<00:00:50.219> new 00:00:50.389 --> 00:00:50.399 align:start position:0% scaling I want to show you a cool new 00:00:50.399 --> 00:00:53.510 align:start position:0% scaling I want to show you a cool new idea<00:00:50.700> I<00:00:50.820> have<00:00:50.940> for<00:00:51.300> a<00:00:51.480> shorting<00:00:52.079> scheme<00:00:52.920> which 00:00:53.510 --> 00:00:53.520 align:start position:0% idea I have for a shorting scheme which 00:00:53.520 --> 00:00:56.090 align:start position:0% idea I have for a shorting scheme which has<00:00:53.899> Atomic<00:00:54.899> growth<00:00:55.260> short<00:00:55.379> transactions<00:00:55.980> and 00:00:56.090 --> 00:00:56.100 align:start position:0% has Atomic growth short transactions and 00:00:56.100 --> 00:00:57.650 align:start position:0% has Atomic growth short transactions and we're<00:00:56.340> going<00:00:56.520> to<00:00:56.579> explain<00:00:56.699> exactly<00:00:57.300> what<00:00:57.480> that 00:00:57.650 --> 00:00:57.660 align:start position:0% we're going to explain exactly what that 00:00:57.660 --> 00:01:00.950 align:start position:0% we're going to explain exactly what that means<00:00:58.379> and<00:00:58.980> but<00:00:59.399> more<00:00:59.640> importantly<00:01:00.000> what<00:01:00.780> I 00:01:00.950 --> 00:01:00.960 align:start position:0% means and but more importantly what I 00:01:00.960 --> 00:01:02.689 align:start position:0% means and but more importantly what I want<00:01:01.020> to<00:01:01.140> do<00:01:01.260> is<00:01:01.440> demonstrate<00:01:02.100> some<00:01:02.340> research 00:01:02.689 --> 00:01:02.699 align:start position:0% want to do is demonstrate some research 00:01:02.699 --> 00:01:05.090 align:start position:0% want to do is demonstrate some research process<00:01:03.000> so<00:01:03.239> like<00:01:03.480> hey<00:01:04.199> can<00:01:04.619> we<00:01:04.799> do<00:01:04.920> this 00:01:05.090 --> 00:01:05.100 align:start position:0% process so like hey can we do this 00:01:05.100 --> 00:01:07.010 align:start position:0% process so like hey can we do this there's<00:01:05.640> a<00:01:05.880> problem<00:01:06.060> there's<00:01:06.479> a<00:01:06.659> solution 00:01:07.010 --> 00:01:07.020 align:start position:0% there's a problem there's a solution 00:01:07.020 --> 00:01:08.929 align:start position:0% there's a problem there's a solution maybe<00:01:07.680> it's<00:01:07.860> at<00:01:08.040> the<00:01:08.159> then<00:01:08.280> we<00:01:08.580> need<00:01:08.700> to<00:01:08.760> go<00:01:08.820> in 00:01:08.929 --> 00:01:08.939 align:start position:0% maybe it's at the then we need to go in 00:01:08.939 --> 00:01:11.030 align:start position:0% maybe it's at the then we need to go in our<00:01:09.119> Direction<00:01:09.360> so<00:01:10.260> can<00:01:10.439> I<00:01:10.500> restrict<00:01:10.860> the 00:01:11.030 --> 00:01:11.040 align:start position:0% our Direction so can I restrict the 00:01:11.040 --> 00:01:11.929 align:start position:0% our Direction so can I restrict the process 00:01:11.929 --> 00:01:11.939 align:start position:0% process 00:01:11.939 --> 00:01:14.149 align:start position:0% process and<00:01:12.479> generally<00:01:12.840> what<00:01:13.200> I<00:01:13.320> want<00:01:13.439> is<00:01:13.619> to<00:01:13.799> Foster 00:01:14.149 --> 00:01:14.159 align:start position:0% and generally what I want is to Foster 00:01:14.159 --> 00:01:15.890 align:start position:0% and generally what I want is to Foster interest<00:01:14.340> in<00:01:14.700> this<00:01:14.820> kind<00:01:15.000> of<00:01:15.060> research<00:01:15.360> and<00:01:15.780> I 00:01:15.890 --> 00:01:15.900 align:start position:0% interest in this kind of research and I 00:01:15.900 --> 00:01:17.210 align:start position:0% interest in this kind of research and I want<00:01:16.020> to<00:01:16.140> I<00:01:16.320> want<00:01:16.439> people<00:01:16.619> to<00:01:16.860> collaborate 00:01:17.210 --> 00:01:17.220 align:start position:0% want to I want people to collaborate 00:01:17.220 --> 00:01:19.789 align:start position:0% want to I want people to collaborate with<00:01:17.400> and<00:01:18.119> and<00:01:18.240> to<00:01:18.479> work<00:01:18.659> with<00:01:19.020> me<00:01:19.200> and<00:01:19.380> with<00:01:19.680> us 00:01:19.789 --> 00:01:19.799 align:start position:0% with and and to work with me and with us 00:01:19.799 --> 00:01:21.890 align:start position:0% with and and to work with me and with us at<00:01:19.979> optimism<00:01:20.400> on<00:01:20.640> this<00:01:20.820> stuff<00:01:21.000> because<00:01:21.240> this 00:01:21.890 --> 00:01:21.900 align:start position:0% at optimism on this stuff because this 00:01:21.900 --> 00:01:23.030 align:start position:0% at optimism on this stuff because this is<00:01:21.960> the<00:01:22.020> kind<00:01:22.200> of<00:01:22.320> stuff 00:01:23.030 --> 00:01:23.040 align:start position:0% is the kind of stuff 00:01:23.040 --> 00:01:24.710 align:start position:0% is the kind of stuff we<00:01:23.520> care<00:01:23.640> about<00:01:23.759> this<00:01:24.180> is<00:01:24.299> not<00:01:24.420> something 00:01:24.710 --> 00:01:24.720 align:start position:0% we care about this is not something 00:01:24.720 --> 00:01:26.749 align:start position:0% we care about this is not something that's<00:01:25.140> really<00:01:25.320> on<00:01:25.500> the<00:01:25.619> roadmap<00:01:25.979> it's<00:01:26.400> a 00:01:26.749 --> 00:01:26.759 align:start position:0% that's really on the roadmap it's a 00:01:26.759 --> 00:01:28.429 align:start position:0% that's really on the roadmap it's a complete<00:01:27.180> side<00:01:27.299> quest<00:01:27.600> and<00:01:27.900> so<00:01:28.020> like<00:01:28.200> I<00:01:28.320> said 00:01:28.429 --> 00:01:28.439 align:start position:0% complete side quest and so like I said 00:01:28.439 --> 00:01:29.870 align:start position:0% complete side quest and so like I said this<00:01:28.560> is<00:01:28.680> a<00:01:28.799> nurse<00:01:29.100> knife<00:01:29.340> like<00:01:29.580> this<00:01:29.759> is 00:01:29.870 --> 00:01:29.880 align:start position:0% this is a nurse knife like this is 00:01:29.880 --> 00:01:31.490 align:start position:0% this is a nurse knife like this is supposed<00:01:30.060> to<00:01:30.180> be<00:01:30.360> brain<00:01:30.900> candy<00:01:31.080> super 00:01:31.490 --> 00:01:31.500 align:start position:0% supposed to be brain candy super 00:01:31.500 --> 00:01:33.350 align:start position:0% supposed to be brain candy super interesting<00:01:31.979> stuff<00:01:32.220> but<00:01:32.880> if<00:01:33.060> you<00:01:33.180> want<00:01:33.240> to 00:01:33.350 --> 00:01:33.360 align:start position:0% interesting stuff but if you want to 00:01:33.360 --> 00:01:35.690 align:start position:0% interesting stuff but if you want to work<00:01:33.479> on<00:01:33.659> it<00:01:33.840> if<00:01:34.320> you<00:01:34.439> talk<00:01:34.680> to<00:01:34.860> me 00:01:35.690 --> 00:01:35.700 align:start position:0% work on it if you talk to me 00:01:35.700 --> 00:01:38.749 align:start position:0% work on it if you talk to me so<00:01:36.119> like<00:01:36.360> I<00:01:36.540> said<00:01:36.720> vertical<00:01:37.619> skating<00:01:38.400> big 00:01:38.749 --> 00:01:38.759 align:start position:0% so like I said vertical skating big 00:01:38.759 --> 00:01:40.249 align:start position:0% so like I said vertical skating big machines<00:01:39.060> horizontal<00:01:39.540> scaling<00:01:39.960> many 00:01:40.249 --> 00:01:40.259 align:start position:0% machines horizontal scaling many 00:01:40.259 --> 00:01:43.670 align:start position:0% machines horizontal scaling many machines<00:01:40.740> spread<00:01:41.460> the<00:01:41.579> load<00:01:41.820> and 00:01:43.670 --> 00:01:43.680 align:start position:0% machines spread the load and 00:01:43.680 --> 00:01:47.030 align:start position:0% machines spread the load and in<00:01:44.280> terms<00:01:44.880> of<00:01:44.939> ethereum<00:01:45.500> vertical<00:01:46.500> scaling 00:01:47.030 --> 00:01:47.040 align:start position:0% in terms of ethereum vertical scaling 00:01:47.040 --> 00:01:49.010 align:start position:0% in terms of ethereum vertical scaling has<00:01:47.159> been<00:01:47.340> done<00:01:47.520> by<00:01:47.759> Roll-Ups<00:01:48.360> right<00:01:48.540> roll-up 00:01:49.010 --> 00:01:49.020 align:start position:0% has been done by Roll-Ups right roll-up 00:01:49.020 --> 00:01:51.469 align:start position:0% has been done by Roll-Ups right roll-up enable<00:01:49.259> vertical<00:01:49.619> scaling<00:01:50.520> because<00:01:51.119> if 00:01:51.469 --> 00:01:51.479 align:start position:0% enable vertical scaling because if 00:01:51.479 --> 00:01:52.850 align:start position:0% enable vertical scaling because if you're<00:01:51.659> a<00:01:51.780> validator<00:01:52.140> you<00:01:52.320> can<00:01:52.439> validate<00:01:52.740> the 00:01:52.850 --> 00:01:52.860 align:start position:0% you're a validator you can validate the 00:01:52.860 --> 00:01:54.950 align:start position:0% you're a validator you can validate the Roll<00:01:53.040> Up<00:01:53.280> by<00:01:53.700> validating<00:01:54.119> The<00:01:54.360> Atrium<00:01:54.780> main 00:01:54.950 --> 00:01:54.960 align:start position:0% Roll Up by validating The Atrium main 00:01:54.960 --> 00:01:56.749 align:start position:0% Roll Up by validating The Atrium main chain<00:01:55.140> there's<00:01:55.680> only<00:01:55.799> one<00:01:55.979> extra<00:01:56.159> assumption 00:01:56.749 --> 00:01:56.759 align:start position:0% chain there's only one extra assumption 00:01:56.759 --> 00:02:00.530 align:start position:0% chain there's only one extra assumption is<00:01:57.180> that<00:01:57.360> there<00:01:57.600> is<00:01:57.780> one<00:01:58.680> honest<00:01:59.220> L2<00:02:00.119> valid 00:02:00.530 --> 00:02:00.540 align:start position:0% is that there is one honest L2 valid 00:02:00.540 --> 00:02:03.889 align:start position:0% is that there is one honest L2 valid errors<00:02:01.320> that<00:02:01.799> can<00:02:01.979> also<00:02:02.220> Supply<00:02:02.700> data<00:02:03.360> for<00:02:03.780> the 00:02:03.889 --> 00:02:03.899 align:start position:0% errors that can also Supply data for the 00:02:03.899 --> 00:02:05.330 align:start position:0% errors that can also Supply data for the roll<00:02:04.020> up 00:02:05.330 --> 00:02:05.340 align:start position:0% roll up 00:02:05.340 --> 00:02:07.789 align:start position:0% roll up but<00:02:05.640> the<00:02:05.880> question<00:02:06.000> is<00:02:06.240> okay<00:02:06.840> we<00:02:07.320> can<00:02:07.500> scale 00:02:07.789 --> 00:02:07.799 align:start position:0% but the question is okay we can scale 00:02:07.799 --> 00:02:09.290 align:start position:0% but the question is okay we can scale vertically<00:02:08.280> and<00:02:08.520> we<00:02:08.700> can<00:02:08.819> probably<00:02:09.000> scale 00:02:09.290 --> 00:02:09.300 align:start position:0% vertically and we can probably scale 00:02:09.300 --> 00:02:12.229 align:start position:0% vertically and we can probably scale ethereum<00:02:09.780> 10<00:02:10.080> times<00:02:10.259> maybe<00:02:11.099> 100<00:02:11.400> times<00:02:11.879> if<00:02:12.120> we 00:02:12.229 --> 00:02:12.239 align:start position:0% ethereum 10 times maybe 100 times if we 00:02:12.239 --> 00:02:14.089 align:start position:0% ethereum 10 times maybe 100 times if we start<00:02:12.420> pushing<00:02:12.780> some<00:02:13.020> buttons<00:02:13.379> like<00:02:13.620> skilled 00:02:14.089 --> 00:02:14.099 align:start position:0% start pushing some buttons like skilled 00:02:14.099 --> 00:02:15.949 align:start position:0% start pushing some buttons like skilled database<00:02:14.459> and<00:02:14.640> things<00:02:14.760> like<00:02:14.940> that<00:02:15.060> what<00:02:15.660> if<00:02:15.840> we 00:02:15.949 --> 00:02:15.959 align:start position:0% database and things like that what if we 00:02:15.959 --> 00:02:18.470 align:start position:0% database and things like that what if we need<00:02:16.080> extra<00:02:16.260> scalability 00:02:18.470 --> 00:02:18.480 align:start position:0% need extra scalability 00:02:18.480 --> 00:02:19.850 align:start position:0% need extra scalability um and<00:02:18.780> and<00:02:18.840> there's<00:02:19.020> multiple<00:02:19.200> reasons<00:02:19.680> we 00:02:19.850 --> 00:02:19.860 align:start position:0% um and and there's multiple reasons we 00:02:19.860 --> 00:02:21.050 align:start position:0% um and and there's multiple reasons we might<00:02:19.980> want<00:02:20.160> that 00:02:21.050 --> 00:02:21.060 align:start position:0% might want that 00:02:21.060 --> 00:02:23.809 align:start position:0% might want that so<00:02:21.540> one<00:02:21.720> is<00:02:21.900> that<00:02:22.560> sure<00:02:23.099> we<00:02:23.400> could<00:02:23.520> like 00:02:23.809 --> 00:02:23.819 align:start position:0% so one is that sure we could like 00:02:23.819 --> 00:02:27.130 align:start position:0% so one is that sure we could like require<00:02:24.599> a<00:02:24.900> data<00:02:25.200> center<00:02:25.319> for<00:02:25.920> L2<00:02:26.520> sequencers 00:02:27.130 --> 00:02:27.140 align:start position:0% require a data center for L2 sequencers 00:02:27.140 --> 00:02:30.229 align:start position:0% require a data center for L2 sequencers but<00:02:28.140> we<00:02:28.440> want<00:02:28.560> to<00:02:28.680> have<00:02:28.860> a<00:02:29.040> healthy 00:02:30.229 --> 00:02:30.239 align:start position:0% but we want to have a healthy 00:02:30.239 --> 00:02:32.089 align:start position:0% but we want to have a healthy um<00:02:30.300> very<00:02:30.660> Data<00:02:31.080> Network<00:02:31.200> and<00:02:31.680> not<00:02:31.920> everybody 00:02:32.089 --> 00:02:32.099 align:start position:0% um very Data Network and not everybody 00:02:32.099 --> 00:02:34.790 align:start position:0% um very Data Network and not everybody can<00:02:32.520> get<00:02:32.700> a<00:02:33.180> data<00:02:33.660> center<00:02:33.720> not<00:02:34.080> even<00:02:34.260> not<00:02:34.739> even 00:02:34.790 --> 00:02:34.800 align:start position:0% can get a data center not even not even 00:02:34.800 --> 00:02:36.949 align:start position:0% can get a data center not even not even every<00:02:35.099> company<00:02:35.340> or<00:02:35.700> every<00:02:35.819> Dao 00:02:36.949 --> 00:02:36.959 align:start position:0% every company or every Dao 00:02:36.959 --> 00:02:39.290 align:start position:0% every company or every Dao so<00:02:37.440> we<00:02:37.680> might<00:02:37.860> want<00:02:38.040> to<00:02:38.340> spread<00:02:38.819> the<00:02:38.879> load<00:02:39.180> so 00:02:39.290 --> 00:02:39.300 align:start position:0% so we might want to spread the load so 00:02:39.300 --> 00:02:41.509 align:start position:0% so we might want to spread the load so that<00:02:39.420> you<00:02:39.599> can<00:02:39.720> validate<00:02:40.140> a<00:02:40.319> subset<00:02:40.739> really<00:02:41.160> of 00:02:41.509 --> 00:02:41.519 align:start position:0% that you can validate a subset really of 00:02:41.519 --> 00:02:42.830 align:start position:0% that you can validate a subset really of the<00:02:41.640> chain 00:02:42.830 --> 00:02:42.840 align:start position:0% the chain 00:02:42.840 --> 00:02:44.930 align:start position:0% the chain other<00:02:43.379> thing<00:02:43.920> is<00:02:44.099> that<00:02:44.220> we<00:02:44.459> might<00:02:44.580> want<00:02:44.700> many 00:02:44.930 --> 00:02:44.940 align:start position:0% other thing is that we might want many 00:02:44.940 --> 00:02:46.850 align:start position:0% other thing is that we might want many different<00:02:45.180> roll-ups<00:02:46.200> this<00:02:46.620> might<00:02:46.739> be 00:02:46.850 --> 00:02:46.860 align:start position:0% different roll-ups this might be 00:02:46.860 --> 00:02:47.809 align:start position:0% different roll-ups this might be Roll-Ups<00:02:47.340> with<00:02:47.400> different<00:02:47.580> security 00:02:47.809 --> 00:02:47.819 align:start position:0% Roll-Ups with different security 00:02:47.819 --> 00:02:49.850 align:start position:0% Roll-Ups with different security assumptions<00:02:48.480> and<00:02:49.140> different<00:02:49.319> parameters 00:02:49.850 --> 00:02:49.860 align:start position:0% assumptions and different parameters 00:02:49.860 --> 00:02:52.550 align:start position:0% assumptions and different parameters like<00:02:50.099> different<00:02:50.280> fee<00:02:50.819> different<00:02:51.540> paid<00:02:52.260> tokens 00:02:52.550 --> 00:02:52.560 align:start position:0% like different fee different paid tokens 00:02:52.560 --> 00:02:55.190 align:start position:0% like different fee different paid tokens in<00:02:52.739> a<00:02:52.920> different<00:02:53.599> pay<00:02:54.599> fees<00:02:54.840> in<00:02:54.959> a<00:02:55.140> different 00:02:55.190 --> 00:02:55.200 align:start position:0% in a different pay fees in a different 00:02:55.200 --> 00:02:57.110 align:start position:0% in a different pay fees in a different token<00:02:55.620> increase<00:02:56.099> the<00:02:56.340> troll<00:02:56.580> output<00:02:56.819> change 00:02:57.110 --> 00:02:57.120 align:start position:0% token increase the troll output change 00:02:57.120 --> 00:02:59.270 align:start position:0% token increase the troll output change the<00:02:57.300> value<00:02:57.480> rules<00:02:57.959> maybe<00:02:58.200> use<00:02:58.440> a<00:02:58.620> different<00:02:58.800> VM 00:02:59.270 --> 00:02:59.280 align:start position:0% the value rules maybe use a different VM 00:02:59.280 --> 00:03:02.990 align:start position:0% the value rules maybe use a different VM all<00:02:59.940> that<00:03:00.120> stuff<00:03:00.379> you<00:03:01.379> might<00:03:01.500> want<00:03:01.680> to<00:03:01.800> do<00:03:02.459> but 00:03:02.990 --> 00:03:03.000 align:start position:0% all that stuff you might want to do but 00:03:03.000 --> 00:03:05.089 align:start position:0% all that stuff you might want to do but you<00:03:03.239> might<00:03:03.420> still<00:03:03.660> want<00:03:03.900> to<00:03:04.080> have<00:03:04.680> multiple 00:03:05.089 --> 00:03:05.099 align:start position:0% you might still want to have multiple 00:03:05.099 --> 00:03:07.369 align:start position:0% you might still want to have multiple Roll-Ups<00:03:05.760> talking<00:03:05.879> to<00:03:06.060> one<00:03:06.239> another 00:03:07.369 --> 00:03:07.379 align:start position:0% Roll-Ups talking to one another 00:03:07.379 --> 00:03:09.110 align:start position:0% Roll-Ups talking to one another okay<00:03:07.800> so<00:03:08.040> there's<00:03:08.160> two<00:03:08.340> main<00:03:08.519> approaches<00:03:08.940> to 00:03:09.110 --> 00:03:09.120 align:start position:0% okay so there's two main approaches to 00:03:09.120 --> 00:03:10.790 align:start position:0% okay so there's two main approaches to horizontal<00:03:09.660> ability<00:03:10.379> one<00:03:10.620> is 00:03:10.790 --> 00:03:10.800 align:start position:0% horizontal ability one is 00:03:10.800 --> 00:03:12.890 align:start position:0% horizontal ability one is parallelization<00:03:11.280> and<00:03:12.120> in<00:03:12.300> that<00:03:12.420> approach<00:03:12.720> you 00:03:12.890 --> 00:03:12.900 align:start position:0% parallelization and in that approach you 00:03:12.900 --> 00:03:14.809 align:start position:0% parallelization and in that approach you can<00:03:13.019> have<00:03:13.200> a<00:03:13.440> big<00:03:13.560> blockchain<00:03:13.920> lots<00:03:14.519> of<00:03:14.580> state 00:03:14.809 --> 00:03:14.819 align:start position:0% can have a big blockchain lots of state 00:03:14.819 --> 00:03:16.309 align:start position:0% can have a big blockchain lots of state and<00:03:15.599> you<00:03:15.720> can<00:03:15.780> spread<00:03:15.959> the<00:03:16.019> role<00:03:16.200> between 00:03:16.309 --> 00:03:16.319 align:start position:0% and you can spread the role between 00:03:16.319 --> 00:03:17.809 align:start position:0% and you can spread the role between machines 00:03:17.809 --> 00:03:17.819 align:start position:0% machines 00:03:17.819 --> 00:03:20.809 align:start position:0% machines two<00:03:18.120> options<00:03:18.360> to<00:03:18.599> do<00:03:18.720> that<00:03:18.900> optimistic 00:03:20.809 --> 00:03:20.819 align:start position:0% two options to do that optimistic 00:03:20.819 --> 00:03:22.970 align:start position:0% two options to do that optimistic you<00:03:21.360> just<00:03:21.540> try<00:03:21.959> to<00:03:22.140> do<00:03:22.319> things<00:03:22.440> in<00:03:22.680> parallel 00:03:22.970 --> 00:03:22.980 align:start position:0% you just try to do things in parallel 00:03:22.980 --> 00:03:24.350 align:start position:0% you just try to do things in parallel and<00:03:23.220> you<00:03:23.400> hope<00:03:23.519> they<00:03:23.700> don't<00:03:23.819> touch<00:03:24.000> the<00:03:24.239> same 00:03:24.350 --> 00:03:24.360 align:start position:0% and you hope they don't touch the same 00:03:24.360 --> 00:03:26.930 align:start position:0% and you hope they don't touch the same state<00:03:24.540> if<00:03:25.440> they<00:03:25.560> do<00:03:25.739> you<00:03:25.920> just<00:03:26.099> throw<00:03:26.340> away<00:03:26.519> one 00:03:26.930 --> 00:03:26.940 align:start position:0% state if they do you just throw away one 00:03:26.940 --> 00:03:29.509 align:start position:0% state if they do you just throw away one of<00:03:27.060> them<00:03:27.120> and<00:03:27.360> you<00:03:27.480> start<00:03:27.900> again 00:03:29.509 --> 00:03:29.519 align:start position:0% of them and you start again 00:03:29.519 --> 00:03:31.309 align:start position:0% of them and you start again if<00:03:30.000> you<00:03:30.000> do<00:03:30.300> this<00:03:30.420> the<00:03:30.659> pitfall<00:03:31.019> is<00:03:31.140> that<00:03:31.260> you 00:03:31.309 --> 00:03:31.319 align:start position:0% if you do this the pitfall is that you 00:03:31.319 --> 00:03:34.009 align:start position:0% if you do this the pitfall is that you can't<00:03:31.440> increase<00:03:31.620> the<00:03:31.860> throughput<00:03:32.159> because 00:03:34.009 --> 00:03:34.019 align:start position:0% can't increase the throughput because 00:03:34.019 --> 00:03:35.509 align:start position:0% can't increase the throughput because um basically<00:03:34.319> you<00:03:34.440> can't<00:03:34.620> charge<00:03:34.860> more<00:03:35.159> for 00:03:35.509 --> 00:03:35.519 align:start position:0% um basically you can't charge more for 00:03:35.519 --> 00:03:37.550 align:start position:0% um basically you can't charge more for transactions<00:03:36.360> are<00:03:36.480> not<00:03:36.659> paralyzable<00:03:37.200> that's 00:03:37.550 --> 00:03:37.560 align:start position:0% transactions are not paralyzable that's 00:03:37.560 --> 00:03:39.470 align:start position:0% transactions are not paralyzable that's because<00:03:37.739> you<00:03:37.980> don't<00:03:38.040> have<00:03:38.220> a<00:03:38.400> clear<00:03:38.879> criteria 00:03:39.470 --> 00:03:39.480 align:start position:0% because you don't have a clear criteria 00:03:39.480 --> 00:03:41.210 align:start position:0% because you don't have a clear criteria of<00:03:39.720> what<00:03:39.900> is<00:03:40.140> parallelizable<00:03:40.739> and<00:03:40.920> what<00:03:41.040> is 00:03:41.210 --> 00:03:41.220 align:start position:0% of what is parallelizable and what is 00:03:41.220 --> 00:03:42.170 align:start position:0% of what is parallelizable and what is not 00:03:42.170 --> 00:03:42.180 align:start position:0% not 00:03:42.180 --> 00:03:44.570 align:start position:0% not our<00:03:42.659> option<00:03:43.080> is<00:03:43.200> to<00:03:43.379> use<00:03:43.560> a<00:03:43.980> strict<00:03:44.400> access 00:03:44.570 --> 00:03:44.580 align:start position:0% our option is to use a strict access 00:03:44.580 --> 00:03:47.809 align:start position:0% our option is to use a strict access list<00:03:44.940> some<00:03:45.840> fancy<00:03:46.140> people<00:03:46.319> call<00:03:46.680> this<00:03:46.860> utxo 00:03:47.809 --> 00:03:47.819 align:start position:0% list some fancy people call this utxo 00:03:47.819 --> 00:03:49.789 align:start position:0% list some fancy people call this utxo but<00:03:48.120> I<00:03:48.360> think<00:03:48.480> strict<00:03:48.840> assets<00:03:49.140> list<00:03:49.379> is 00:03:49.789 --> 00:03:49.799 align:start position:0% but I think strict assets list is 00:03:49.799 --> 00:03:52.850 align:start position:0% but I think strict assets list is clearer<00:03:50.220> and<00:03:50.879> so<00:03:51.060> basically<00:03:51.440> that's<00:03:52.440> shipping 00:03:52.850 --> 00:03:52.860 align:start position:0% clearer and so basically that's shipping 00:03:52.860 --> 00:03:54.770 align:start position:0% clearer and so basically that's shipping every<00:03:52.980> transaction<00:03:53.400> with<00:03:53.700> a<00:03:53.879> list<00:03:54.000> of<00:03:54.360> either 00:03:54.770 --> 00:03:54.780 align:start position:0% every transaction with a list of either 00:03:54.780 --> 00:03:56.630 align:start position:0% every transaction with a list of either all<00:03:55.019> the<00:03:55.260> contracted<00:03:55.739> touches<00:03:56.159> so<00:03:56.459> you<00:03:56.580> can 00:03:56.630 --> 00:03:56.640 align:start position:0% all the contracted touches so you can 00:03:56.640 --> 00:03:58.729 align:start position:0% all the contracted touches so you can have<00:03:56.760> a<00:03:56.879> lock<00:03:57.000> on<00:03:57.120> the<00:03:57.299> contract<00:03:57.599> or<00:03:58.379> all<00:03:58.620> the 00:03:58.729 --> 00:03:58.739 align:start position:0% have a lock on the contract or all the 00:03:58.739 --> 00:04:00.710 align:start position:0% have a lock on the contract or all the storage<00:03:58.920> slots<00:03:59.340> that<00:03:59.519> touches<00:03:59.940> so<00:04:00.480> you<00:04:00.659> can 00:04:00.710 --> 00:04:00.720 align:start position:0% storage slots that touches so you can 00:04:00.720 --> 00:04:03.649 align:start position:0% storage slots that touches so you can lock<00:04:00.900> this<00:04:01.440> specific<00:04:01.920> storage<00:04:02.159> shots 00:04:03.649 --> 00:04:03.659 align:start position:0% lock this specific storage shots 00:04:03.659 --> 00:04:05.809 align:start position:0% lock this specific storage shots the<00:04:04.260> polarization<00:04:04.680> approach 00:04:05.809 --> 00:04:05.819 align:start position:0% the polarization approach 00:04:05.819 --> 00:04:08.750 align:start position:0% the polarization approach Stills<00:04:06.360> assume<00:04:06.780> that<00:04:06.959> you<00:04:07.200> have<00:04:07.319> one<00:04:07.560> entity 00:04:08.750 --> 00:04:08.760 align:start position:0% Stills assume that you have one entity 00:04:08.760 --> 00:04:11.390 align:start position:0% Stills assume that you have one entity that's<00:04:09.239> why<00:04:09.420> it<00:04:09.599> is<00:04:09.720> everything 00:04:11.390 --> 00:04:11.400 align:start position:0% that's why it is everything 00:04:11.400 --> 00:04:13.309 align:start position:0% that's why it is everything just<00:04:11.879> now<00:04:12.000> it's<00:04:12.180> spreading<00:04:12.599> things<00:04:12.720> across 00:04:13.309 --> 00:04:13.319 align:start position:0% just now it's spreading things across 00:04:13.319 --> 00:04:15.170 align:start position:0% just now it's spreading things across cores<00:04:13.680> and<00:04:13.799> across<00:04:14.159> machines<00:04:14.459> so<00:04:14.879> it's<00:04:15.000> still 00:04:15.170 --> 00:04:15.180 align:start position:0% cores and across machines so it's still 00:04:15.180 --> 00:04:18.289 align:start position:0% cores and across machines so it's still high<00:04:15.360> cost<00:04:15.540> of<00:04:15.780> ideas<00:04:15.959> if<00:04:16.859> you<00:04:16.979> want<00:04:17.220> to<00:04:17.340> reduce 00:04:18.289 --> 00:04:18.299 align:start position:0% high cost of ideas if you want to reduce 00:04:18.299 --> 00:04:20.270 align:start position:0% high cost of ideas if you want to reduce the<00:04:18.840> the<00:04:19.019> load<00:04:19.380> and<00:04:19.440> validators<00:04:19.859> you<00:04:20.040> may<00:04:20.160> want 00:04:20.270 --> 00:04:20.280 align:start position:0% the the load and validators you may want 00:04:20.280 --> 00:04:22.250 align:start position:0% the the load and validators you may want to<00:04:20.340> do<00:04:20.459> sharding<00:04:20.820> and<00:04:21.359> then<00:04:21.419> values<00:04:21.959> can<00:04:22.139> value 00:04:22.250 --> 00:04:22.260 align:start position:0% to do sharding and then values can value 00:04:22.260 --> 00:04:24.890 align:start position:0% to do sharding and then values can value a<00:04:22.560> single<00:04:22.740> chart<00:04:22.979> so<00:04:23.580> a<00:04:23.759> short<00:04:23.940> is<00:04:24.180> basically<00:04:24.419> a 00:04:24.890 --> 00:04:24.900 align:start position:0% a single chart so a short is basically a 00:04:24.900 --> 00:04:27.170 align:start position:0% a single chart so a short is basically a small<00:04:25.199> sub<00:04:25.440> blockchain 00:04:27.170 --> 00:04:27.180 align:start position:0% small sub blockchain 00:04:27.180 --> 00:04:29.629 align:start position:0% small sub blockchain the<00:04:27.600> only<00:04:27.780> thing<00:04:28.020> was<00:04:28.199> that<00:04:28.380> that<00:04:28.680> apps<00:04:29.520> not 00:04:29.629 --> 00:04:29.639 align:start position:0% the only thing was that that apps not 00:04:29.639 --> 00:04:31.249 align:start position:0% the only thing was that that apps not need<00:04:29.880> to<00:04:30.000> think<00:04:30.120> about 00:04:31.249 --> 00:04:31.259 align:start position:0% need to think about 00:04:31.259 --> 00:04:32.749 align:start position:0% need to think about um<00:04:31.320> on<00:04:31.620> which<00:04:31.800> chart<00:04:31.979> they<00:04:32.220> want<00:04:32.340> to<00:04:32.460> deploy 00:04:32.749 --> 00:04:32.759 align:start position:0% um on which chart they want to deploy 00:04:32.759 --> 00:04:34.909 align:start position:0% um on which chart they want to deploy which<00:04:33.180> might<00:04:33.360> not<00:04:33.479> be<00:04:33.660> great 00:04:34.909 --> 00:04:34.919 align:start position:0% which might not be great 00:04:34.919 --> 00:04:37.969 align:start position:0% which might not be great but<00:04:35.520> the<00:04:36.000> great<00:04:36.120> thing<00:04:36.360> is<00:04:36.479> that<00:04:36.720> we<00:04:37.020> can<00:04:37.139> do<00:04:37.259> it 00:04:37.969 --> 00:04:37.979 align:start position:0% but the great thing is that we can do it 00:04:37.979 --> 00:04:39.530 align:start position:0% but the great thing is that we can do it eterogeneous<00:04:38.520> roll<00:04:38.699> up<00:04:38.820> so<00:04:39.000> like<00:04:39.180> I<00:04:39.300> said<00:04:39.360> you 00:04:39.530 --> 00:04:39.540 align:start position:0% eterogeneous roll up so like I said you 00:04:39.540 --> 00:04:40.850 align:start position:0% eterogeneous roll up so like I said you can<00:04:39.660> customize<00:04:40.020> roll<00:04:40.199> ups<00:04:40.500> to<00:04:40.620> have<00:04:40.740> different 00:04:40.850 --> 00:04:40.860 align:start position:0% can customize roll ups to have different 00:04:40.860 --> 00:04:42.530 align:start position:0% can customize roll ups to have different VMS<00:04:41.400> different<00:04:41.580> view<00:04:41.820> models<00:04:42.300> and<00:04:42.360> things 00:04:42.530 --> 00:04:42.540 align:start position:0% VMS different view models and things 00:04:42.540 --> 00:04:44.390 align:start position:0% VMS different view models and things like<00:04:42.660> that<00:04:42.840> and<00:04:43.440> they<00:04:43.560> can<00:04:43.740> all<00:04:43.860> talk<00:04:44.100> to<00:04:44.220> each 00:04:44.390 --> 00:04:44.400 align:start position:0% like that and they can all talk to each 00:04:44.400 --> 00:04:45.710 align:start position:0% like that and they can all talk to each other 00:04:45.710 --> 00:04:45.720 align:start position:0% other 00:04:45.720 --> 00:04:47.570 align:start position:0% other uh<00:04:46.139> the<00:04:46.320> problem<00:04:46.440> with<00:04:46.680> shorting<00:04:47.040> is<00:04:47.160> that<00:04:47.220> if 00:04:47.570 --> 00:04:47.580 align:start position:0% uh the problem with shorting is that if 00:04:47.580 --> 00:04:49.969 align:start position:0% uh the problem with shorting is that if there<00:04:47.699> is<00:04:47.820> no<00:04:47.940> way<00:04:48.120> for<00:04:48.500> shards<00:04:49.500> to<00:04:49.620> talk<00:04:49.800> to 00:04:49.969 --> 00:04:49.979 align:start position:0% there is no way for shards to talk to 00:04:49.979 --> 00:04:51.770 align:start position:0% there is no way for shards to talk to one<00:04:50.100> another<00:04:50.280> in<00:04:50.820> a<00:04:51.000> way<00:04:51.060> that's<00:04:51.300> effective 00:04:51.770 --> 00:04:51.780 align:start position:0% one another in a way that's effective 00:04:51.780 --> 00:04:54.469 align:start position:0% one another in a way that's effective that's<00:04:52.380> a<00:04:52.560> bad<00:04:52.680> solution<00:04:53.460> so<00:04:54.060> I'll<00:04:54.300> explain 00:04:54.469 --> 00:04:54.479 align:start position:0% that's a bad solution so I'll explain 00:04:54.479 --> 00:04:56.270 align:start position:0% that's a bad solution so I'll explain what<00:04:54.780> you<00:04:54.960> know<00:04:55.080> an<00:04:55.199> effective<00:04:55.560> way<00:04:55.680> means<00:04:56.040> but 00:04:56.270 --> 00:04:56.280 align:start position:0% what you know an effective way means but 00:04:56.280 --> 00:04:58.010 align:start position:0% what you know an effective way means but as<00:04:56.759> you<00:04:56.880> guessed<00:04:57.060> it<00:04:57.180> from<00:04:57.300> title<00:04:57.780> this<00:04:57.960> is 00:04:58.010 --> 00:04:58.020 align:start position:0% as you guessed it from title this is 00:04:58.020 --> 00:05:00.830 align:start position:0% as you guessed it from title this is about<00:04:58.139> atomic<00:04:58.740> composability 00:05:00.830 --> 00:05:00.840 align:start position:0% about atomic composability 00:05:00.840 --> 00:05:03.110 align:start position:0% about atomic composability so<00:05:01.500> this<00:05:01.740> is<00:05:01.800> an<00:05:01.860> example<00:05:02.100> I<00:05:02.400> will<00:05:02.580> use<00:05:02.699> for<00:05:02.940> a 00:05:03.110 --> 00:05:03.120 align:start position:0% so this is an example I will use for a 00:05:03.120 --> 00:05:05.030 align:start position:0% so this is an example I will use for a cross<00:05:03.240> chart<00:05:03.540> transaction 00:05:05.030 --> 00:05:05.040 align:start position:0% cross chart transaction 00:05:05.040 --> 00:05:06.830 align:start position:0% cross chart transaction it's<00:05:05.400> a<00:05:05.520> transaction<00:05:05.820> that<00:05:06.060> swaps<00:05:06.419> Bitcoin 00:05:06.830 --> 00:05:06.840 align:start position:0% it's a transaction that swaps Bitcoin 00:05:06.840 --> 00:05:09.290 align:start position:0% it's a transaction that swaps Bitcoin for<00:05:06.960> either<00:05:07.139> on<00:05:07.800> chart<00:05:07.979> a<00:05:08.280> then<00:05:08.639> Bridges<00:05:09.060> The 00:05:09.290 --> 00:05:09.300 align:start position:0% for either on chart a then Bridges The 00:05:09.300 --> 00:05:11.870 align:start position:0% for either on chart a then Bridges The Ether<00:05:09.660> to<00:05:09.900> a<00:05:10.080> short<00:05:10.199> B<00:05:10.440> and<00:05:11.100> on<00:05:11.280> chart<00:05:11.460> B<00:05:11.699> will 00:05:11.870 --> 00:05:11.880 align:start position:0% Ether to a short B and on chart B will 00:05:11.880 --> 00:05:14.270 align:start position:0% Ether to a short B and on chart B will buy<00:05:12.060> nft<00:05:12.419> for<00:05:12.840> either 00:05:14.270 --> 00:05:14.280 align:start position:0% buy nft for either 00:05:14.280 --> 00:05:15.530 align:start position:0% buy nft for either so<00:05:14.639> this<00:05:14.759> specified<00:05:15.060> in<00:05:15.240> a<00:05:15.360> single 00:05:15.530 --> 00:05:15.540 align:start position:0% so this specified in a single 00:05:15.540 --> 00:05:17.810 align:start position:0% so this specified in a single transaction<00:05:15.840> that<00:05:16.139> you<00:05:16.320> send<00:05:17.160> either<00:05:17.400> to<00:05:17.639> a 00:05:17.810 --> 00:05:17.820 align:start position:0% transaction that you send either to a 00:05:17.820 --> 00:05:19.790 align:start position:0% transaction that you send either to a system<00:05:17.940> or<00:05:18.300> to<00:05:18.419> short<00:05:18.660> a<00:05:18.900> depending<00:05:19.380> on<00:05:19.560> on 00:05:19.790 --> 00:05:19.800 align:start position:0% system or to short a depending on on 00:05:19.800 --> 00:05:21.650 align:start position:0% system or to short a depending on on your<00:05:19.979> architecture 00:05:21.650 --> 00:05:21.660 align:start position:0% your architecture 00:05:21.660 --> 00:05:23.570 align:start position:0% your architecture so<00:05:22.080> one<00:05:22.320> very<00:05:22.560> desirable<00:05:22.979> property<00:05:23.400> is 00:05:23.570 --> 00:05:23.580 align:start position:0% so one very desirable property is 00:05:23.580 --> 00:05:24.830 align:start position:0% so one very desirable property is atomicity 00:05:24.830 --> 00:05:24.840 align:start position:0% atomicity 00:05:24.840 --> 00:05:27.409 align:start position:0% atomicity if<00:05:25.199> any<00:05:25.380> part<00:05:25.620> of<00:05:25.919> this<00:05:26.639> reverts<00:05:27.180> everything 00:05:27.409 --> 00:05:27.419 align:start position:0% if any part of this reverts everything 00:05:27.419 --> 00:05:29.150 align:start position:0% if any part of this reverts everything reverts<00:05:28.020> and<00:05:28.199> in<00:05:28.320> this<00:05:28.440> case<00:05:28.560> in<00:05:28.860> particular 00:05:29.150 --> 00:05:29.160 align:start position:0% reverts and in this case in particular 00:05:29.160 --> 00:05:31.550 align:start position:0% reverts and in this case in particular if<00:05:29.820> you<00:05:29.940> come<00:05:30.060> by<00:05:30.240> your<00:05:30.419> nft<00:05:30.660> for<00:05:30.960> either<00:05:31.080> then 00:05:31.550 --> 00:05:31.560 align:start position:0% if you come by your nft for either then 00:05:31.560 --> 00:05:34.070 align:start position:0% if you come by your nft for either then you<00:05:31.800> also<00:05:31.979> don't<00:05:32.100> want<00:05:32.340> to<00:05:32.479> swap<00:05:33.479> your<00:05:33.660> Bitcoin 00:05:34.070 --> 00:05:34.080 align:start position:0% you also don't want to swap your Bitcoin 00:05:34.080 --> 00:05:35.510 align:start position:0% you also don't want to swap your Bitcoin for<00:05:34.139> either 00:05:35.510 --> 00:05:35.520 align:start position:0% for either 00:05:35.520 --> 00:05:38.210 align:start position:0% for either sometimes<00:05:36.419> you<00:05:36.780> can<00:05:36.900> achieve<00:05:37.320> this<00:05:37.560> via 00:05:38.210 --> 00:05:38.220 align:start position:0% sometimes you can achieve this via 00:05:38.220 --> 00:05:41.330 align:start position:0% sometimes you can achieve this via application<00:05:38.759> Level<00:05:39.000> atomicity<00:05:40.100> but<00:05:41.100> in<00:05:41.220> this 00:05:41.330 --> 00:05:41.340 align:start position:0% application Level atomicity but in this 00:05:41.340 --> 00:05:43.550 align:start position:0% application Level atomicity but in this case<00:05:41.460> it<00:05:41.699> doesn't<00:05:41.820> work<00:05:42.120> because 00:05:43.550 --> 00:05:43.560 align:start position:0% case it doesn't work because 00:05:43.560 --> 00:05:46.070 align:start position:0% case it doesn't work because sure<00:05:44.100> if<00:05:44.460> you<00:05:44.639> you<00:05:44.880> know<00:05:45.060> if<00:05:45.419> you<00:05:45.539> can't<00:05:45.660> buy 00:05:46.070 --> 00:05:46.080 align:start position:0% sure if you you know if you can't buy 00:05:46.080 --> 00:05:48.590 align:start position:0% sure if you you know if you can't buy your<00:05:46.860> nft<00:05:47.100> for<00:05:47.460> either<00:05:47.580> you<00:05:48.060> could<00:05:48.120> swap<00:05:48.419> back 00:05:48.590 --> 00:05:48.600 align:start position:0% your nft for either you could swap back 00:05:48.600 --> 00:05:49.969 align:start position:0% your nft for either you could swap back your<00:05:48.720> user<00:05:49.020> for<00:05:49.199> Bitcoin<00:05:49.560> but<00:05:49.680> now<00:05:49.800> you've 00:05:49.969 --> 00:05:49.979 align:start position:0% your user for Bitcoin but now you've 00:05:49.979 --> 00:05:51.950 align:start position:0% your user for Bitcoin but now you've paid<00:05:50.160> two<00:05:50.340> swap<00:05:50.639> fees<00:05:50.940> and<00:05:51.600> you've<00:05:51.780> been 00:05:51.950 --> 00:05:51.960 align:start position:0% paid two swap fees and you've been 00:05:51.960 --> 00:05:54.529 align:start position:0% paid two swap fees and you've been exposed<00:05:52.320> to<00:05:52.380> bitcoin<00:05:52.919> either<00:05:53.160> volatility 00:05:54.529 --> 00:05:54.539 align:start position:0% exposed to bitcoin either volatility 00:05:54.539 --> 00:05:57.529 align:start position:0% exposed to bitcoin either volatility but<00:05:55.320> there<00:05:55.680> are<00:05:55.860> sometimes<00:05:56.220> cases<00:05:56.699> where<00:05:57.060> you 00:05:57.529 --> 00:05:57.539 align:start position:0% but there are sometimes cases where you 00:05:57.539 --> 00:06:00.290 align:start position:0% but there are sometimes cases where you can<00:05:57.660> revert<00:05:58.199> the<00:05:58.680> action<00:05:58.979> on<00:05:59.220> chart<00:05:59.400> a<00:05:59.759> and<00:06:00.120> if 00:06:00.290 --> 00:06:00.300 align:start position:0% can revert the action on chart a and if 00:06:00.300 --> 00:06:04.010 align:start position:0% can revert the action on chart a and if you<00:06:00.360> can<00:06:00.479> do<00:06:00.660> that<00:06:00.840> then<00:06:01.139> you<00:06:01.320> can<00:06:01.440> do<00:06:01.680> okay 00:06:04.010 --> 00:06:04.020 align:start position:0% you can do that then you can do okay 00:06:04.020 --> 00:06:06.800 align:start position:0% you can do that then you can do okay I<00:06:04.500> was<00:06:04.620> standing<00:06:04.919> in<00:06:04.979> the<00:06:05.039> wrong<00:06:05.160> area<00:06:05.820> so 00:06:06.800 --> 00:06:06.810 align:start position:0% I was standing in the wrong area so 00:06:06.810 --> 00:06:07.070 align:start position:0% I was standing in the wrong area so [Music] 00:06:07.070 --> 00:06:07.080 align:start position:0% [Music] 00:06:07.080 --> 00:06:08.689 align:start position:0% [Music] um 00:06:08.689 --> 00:06:08.699 align:start position:0% um 00:06:08.699 --> 00:06:10.129 align:start position:0% um yeah<00:06:09.180> so<00:06:09.300> in<00:06:09.419> some<00:06:09.600> cases<00:06:09.720> you<00:06:09.900> can<00:06:10.020> do 00:06:10.129 --> 00:06:10.139 align:start position:0% yeah so in some cases you can do 00:06:10.139 --> 00:06:11.570 align:start position:0% yeah so in some cases you can do application<00:06:10.500> Level<00:06:10.680> automaticity<00:06:11.280> if<00:06:11.520> you 00:06:11.570 --> 00:06:11.580 align:start position:0% application Level automaticity if you 00:06:11.580 --> 00:06:14.930 align:start position:0% application Level automaticity if you can<00:06:11.699> roll<00:06:11.820> back<00:06:12.000> the<00:06:12.240> thing<00:06:12.419> on<00:06:12.600> chart<00:06:12.780> a 00:06:14.930 --> 00:06:14.940 align:start position:0% can roll back the thing on chart a 00:06:14.940 --> 00:06:16.610 align:start position:0% can roll back the thing on chart a um<00:06:15.060> so<00:06:15.360> what<00:06:15.600> do<00:06:15.720> we<00:06:15.840> have<00:06:15.900> today<00:06:16.080> today<00:06:16.380> we 00:06:16.610 --> 00:06:16.620 align:start position:0% um so what do we have today today we 00:06:16.620 --> 00:06:18.409 align:start position:0% um so what do we have today today we don't<00:06:16.740> have<00:06:16.860> Atomic<00:06:17.340> composability<00:06:17.880> but 00:06:18.409 --> 00:06:18.419 align:start position:0% don't have Atomic composability but 00:06:18.419 --> 00:06:20.390 align:start position:0% don't have Atomic composability but between<00:06:18.660> pretty<00:06:19.199> much<00:06:19.320> any<00:06:19.680> pair<00:06:19.979> of<00:06:20.100> chains 00:06:20.390 --> 00:06:20.400 align:start position:0% between pretty much any pair of chains 00:06:20.400 --> 00:06:21.770 align:start position:0% between pretty much any pair of chains you<00:06:20.460> can<00:06:20.580> do 00:06:21.770 --> 00:06:21.780 align:start position:0% you can do 00:06:21.780 --> 00:06:24.050 align:start position:0% you can do um<00:06:21.840> eventual<00:06:22.380> delivery<00:06:22.800> of<00:06:22.979> messages<00:06:23.220> okay<00:06:23.819> so 00:06:24.050 --> 00:06:24.060 align:start position:0% um eventual delivery of messages okay so 00:06:24.060 --> 00:06:26.510 align:start position:0% um eventual delivery of messages okay so imagine<00:06:24.479> you<00:06:24.780> have<00:06:24.900> a<00:06:25.020> chain<00:06:25.139> a<00:06:25.380> that<00:06:26.039> chain<00:06:26.280> B 00:06:26.510 --> 00:06:26.520 align:start position:0% imagine you have a chain a that chain B 00:06:26.520 --> 00:06:29.090 align:start position:0% imagine you have a chain a that chain B you<00:06:27.360> can<00:06:27.419> use<00:06:27.600> systems<00:06:28.139> like 00:06:29.090 --> 00:06:29.100 align:start position:0% you can use systems like 00:06:29.100 --> 00:06:32.330 align:start position:0% you can use systems like um<00:06:29.160> layer<00:06:29.699> 0<00:06:30.259> I<00:06:31.259> think<00:06:31.380> Wormhole<00:06:31.919> does<00:06:32.160> this 00:06:32.330 --> 00:06:32.340 align:start position:0% um layer 0 I think Wormhole does this 00:06:32.340 --> 00:06:34.129 align:start position:0% um layer 0 I think Wormhole does this Nomad<00:06:32.940> to<00:06:33.180> exchange<00:06:33.479> messages<00:06:33.720> between 00:06:34.129 --> 00:06:34.139 align:start position:0% Nomad to exchange messages between 00:06:34.139 --> 00:06:35.749 align:start position:0% Nomad to exchange messages between chains 00:06:35.749 --> 00:06:35.759 align:start position:0% chains 00:06:35.759 --> 00:06:38.029 align:start position:0% chains and<00:06:36.360> what<00:06:36.600> you<00:06:36.780> you<00:06:36.960> have<00:06:37.139> is<00:06:37.319> that<00:06:37.560> the 00:06:38.029 --> 00:06:38.039 align:start position:0% and what you you have is that the 00:06:38.039 --> 00:06:40.249 align:start position:0% and what you you have is that the guarantee<00:06:38.400> that<00:06:38.639> if<00:06:39.060> you<00:06:39.360> do<00:06:39.720> the<00:06:39.840> action<00:06:40.020> on 00:06:40.249 --> 00:06:40.259 align:start position:0% guarantee that if you do the action on 00:06:40.259 --> 00:06:42.050 align:start position:0% guarantee that if you do the action on chain<00:06:40.500> a<00:06:40.740> eventually<00:06:41.460> you'll<00:06:41.699> do<00:06:41.819> the<00:06:41.940> action 00:06:42.050 --> 00:06:42.060 align:start position:0% chain a eventually you'll do the action 00:06:42.060 --> 00:06:43.309 align:start position:0% chain a eventually you'll do the action on<00:06:42.300> chain<00:06:42.479> B 00:06:43.309 --> 00:06:43.319 align:start position:0% on chain B 00:06:43.319 --> 00:06:45.170 align:start position:0% on chain B detection<00:06:43.860> we<00:06:44.400> can<00:06:44.520> fail<00:06:44.699> and<00:06:45.060> there's 00:06:45.170 --> 00:06:45.180 align:start position:0% detection we can fail and there's 00:06:45.180 --> 00:06:46.610 align:start position:0% detection we can fail and there's nothing<00:06:45.360> you<00:06:45.600> can<00:06:45.660> do<00:06:45.780> about<00:06:45.960> reversing<00:06:46.500> the 00:06:46.610 --> 00:06:46.620 align:start position:0% nothing you can do about reversing the 00:06:46.620 --> 00:06:47.930 align:start position:0% nothing you can do about reversing the action<00:06:46.740> a 00:06:47.930 --> 00:06:47.940 align:start position:0% action a 00:06:47.940 --> 00:06:49.790 align:start position:0% action a that's<00:06:48.300> what<00:06:48.479> we<00:06:48.600> have<00:06:48.720> today<00:06:48.900> I<00:06:49.560> just 00:06:49.790 --> 00:06:49.800 align:start position:0% that's what we have today I just 00:06:49.800 --> 00:06:51.409 align:start position:0% that's what we have today I just implemented<00:06:50.280> ideally<00:06:50.639> with<00:06:50.880> like<00:06:51.000> Clans<00:06:51.300> and 00:06:51.409 --> 00:06:51.419 align:start position:0% implemented ideally with like Clans and 00:06:51.419 --> 00:06:53.689 align:start position:0% implemented ideally with like Clans and ziki<00:06:51.840> proofs<00:06:52.139> but<00:06:52.319> maybe<00:06:52.860> also<00:06:53.220> a<00:06:53.400> good<00:06:53.520> old 00:06:53.689 --> 00:06:53.699 align:start position:0% ziki proofs but maybe also a good old 00:06:53.699 --> 00:06:57.290 align:start position:0% ziki proofs but maybe also a good old multi-sig<00:06:54.539> uh<00:06:55.139> that<00:06:55.620> happens 00:06:57.290 --> 00:06:57.300 align:start position:0% multi-sig uh that happens 00:06:57.300 --> 00:06:58.730 align:start position:0% multi-sig uh that happens so 00:06:58.730 --> 00:06:58.740 align:start position:0% so 00:06:58.740 --> 00:07:00.650 align:start position:0% so getting<00:06:59.100> to<00:06:59.280> the<00:06:59.460> fractal<00:06:59.880> part<00:07:00.180> of<00:07:00.360> the<00:07:00.539> talk 00:07:00.650 --> 00:07:00.660 align:start position:0% getting to the fractal part of the talk 00:07:00.660 --> 00:07:02.390 align:start position:0% getting to the fractal part of the talk we<00:07:01.259> can<00:07:01.319> do<00:07:01.440> a<00:07:01.620> little<00:07:01.680> bit<00:07:01.800> better<00:07:01.919> with<00:07:02.160> roll 00:07:02.390 --> 00:07:02.400 align:start position:0% we can do a little bit better with roll 00:07:02.400 --> 00:07:04.550 align:start position:0% we can do a little bit better with roll ups<00:07:02.759> and<00:07:02.880> especially<00:07:03.180> with<00:07:03.360> ZK<00:07:03.660> Roll-Ups<00:07:04.139> we 00:07:04.550 --> 00:07:04.560 align:start position:0% ups and especially with ZK Roll-Ups we 00:07:04.560 --> 00:07:06.230 align:start position:0% ups and especially with ZK Roll-Ups we can<00:07:04.680> at<00:07:04.860> least<00:07:04.979> ensure<00:07:05.460> a<00:07:05.639> bound<00:07:05.880> on<00:07:06.120> this 00:07:06.230 --> 00:07:06.240 align:start position:0% can at least ensure a bound on this 00:07:06.240 --> 00:07:08.689 align:start position:0% can at least ensure a bound on this right<00:07:06.479> this<00:07:06.960> was<00:07:07.199> eventual<00:07:07.620> delivery<00:07:08.100> could 00:07:08.689 --> 00:07:08.699 align:start position:0% right this was eventual delivery could 00:07:08.699 --> 00:07:10.370 align:start position:0% right this was eventual delivery could mean<00:07:08.940> if<00:07:09.240> I<00:07:09.360> go<00:07:09.479> back<00:07:09.600> to<00:07:09.780> the<00:07:09.900> previous<00:07:10.080> slide 00:07:10.370 --> 00:07:10.380 align:start position:0% mean if I go back to the previous slide 00:07:10.380 --> 00:07:14.090 align:start position:0% mean if I go back to the previous slide it<00:07:10.740> could<00:07:10.979> mean<00:07:11.100> many<00:07:11.340> blocks<00:07:11.819> sorry 00:07:14.090 --> 00:07:14.100 align:start position:0% it could mean many blocks sorry 00:07:14.100 --> 00:07:16.550 align:start position:0% it could mean many blocks sorry didn't<00:07:14.580> mean<00:07:14.759> to<00:07:14.880> do<00:07:15.060> that<00:07:15.180> you<00:07:15.840> could<00:07:15.960> go<00:07:16.380> back 00:07:16.550 --> 00:07:16.560 align:start position:0% didn't mean to do that you could go back 00:07:16.560 --> 00:07:18.350 align:start position:0% didn't mean to do that you could go back like<00:07:16.680> many<00:07:16.860> blocks<00:07:17.220> in<00:07:17.340> the<00:07:17.460> future<00:07:17.580> go<00:07:18.060> you 00:07:18.350 --> 00:07:18.360 align:start position:0% like many blocks in the future go you 00:07:18.360 --> 00:07:19.850 align:start position:0% like many blocks in the future go you know<00:07:18.479> forward<00:07:18.600> main<00:07:18.840> blocks 00:07:19.850 --> 00:07:19.860 align:start position:0% know forward main blocks 00:07:19.860 --> 00:07:21.529 align:start position:0% know forward main blocks what<00:07:20.400> you<00:07:20.460> could<00:07:20.580> do<00:07:20.759> is<00:07:20.940> say<00:07:21.120> well<00:07:21.300> we're 00:07:21.529 --> 00:07:21.539 align:start position:0% what you could do is say well we're 00:07:21.539 --> 00:07:23.570 align:start position:0% what you could do is say well we're going<00:07:21.720> to<00:07:21.780> do<00:07:21.900> this<00:07:22.080> on<00:07:22.380> the<00:07:22.500> next<00:07:22.620> block<00:07:22.860> okay 00:07:23.570 --> 00:07:23.580 align:start position:0% going to do this on the next block okay 00:07:23.580 --> 00:07:25.969 align:start position:0% going to do this on the next block okay one<00:07:24.419> scheme<00:07:24.840> to<00:07:24.900> do<00:07:25.020> this 00:07:25.969 --> 00:07:25.979 align:start position:0% one scheme to do this 00:07:25.979 --> 00:07:28.550 align:start position:0% one scheme to do this roll<00:07:26.880> ups<00:07:27.479> and<00:07:27.780> so<00:07:27.960> basically<00:07:28.199> you<00:07:28.319> have<00:07:28.440> this 00:07:28.550 --> 00:07:28.560 align:start position:0% roll ups and so basically you have this 00:07:28.560 --> 00:07:30.110 align:start position:0% roll ups and so basically you have this architecture<00:07:29.160> where 00:07:30.110 --> 00:07:30.120 align:start position:0% architecture where 00:07:30.120 --> 00:07:32.570 align:start position:0% architecture where uh<00:07:30.720> you<00:07:30.900> have<00:07:31.020> a<00:07:31.139> apparent<00:07:31.620> roll<00:07:31.800> up<00:07:32.039> here<00:07:32.220> the 00:07:32.570 --> 00:07:32.580 align:start position:0% uh you have a apparent roll up here the 00:07:32.580 --> 00:07:35.029 align:start position:0% uh you have a apparent roll up here the cover<00:07:32.880> up<00:07:33.120> one<00:07:33.300> it<00:07:33.960> has<00:07:34.199> child<00:07:34.380> draw<00:07:34.620> UPS<00:07:34.919> you 00:07:35.029 --> 00:07:35.039 align:start position:0% cover up one it has child draw UPS you 00:07:35.039 --> 00:07:38.089 align:start position:0% cover up one it has child draw UPS you give<00:07:35.220> up<00:07:35.400> 11<00:07:35.880> and<00:07:36.180> 12.<00:07:36.599> and<00:07:37.259> basically<00:07:37.560> it's<00:07:37.919> a 00:07:38.089 --> 00:07:38.099 align:start position:0% give up 11 and 12. and basically it's a 00:07:38.099 --> 00:07:39.710 align:start position:0% give up 11 and 12. and basically it's a fractal<00:07:38.520> structure<00:07:38.880> because<00:07:39.060> the<00:07:39.300> roll<00:07:39.539> up 00:07:39.710 --> 00:07:39.720 align:start position:0% fractal structure because the roll up 00:07:39.720 --> 00:07:42.230 align:start position:0% fractal structure because the roll up one<00:07:40.080> rolls<00:07:40.500> up<00:07:40.620> to<00:07:40.800> the<00:07:40.919> layer<00:07:41.220> one<00:07:41.340> but<00:07:42.120> the 00:07:42.230 --> 00:07:42.240 align:start position:0% one rolls up to the layer one but the 00:07:42.240 --> 00:07:45.170 align:start position:0% one rolls up to the layer one but the layer<00:07:42.539> 11<00:07:42.720> and<00:07:43.080> 12<00:07:43.199> they<00:07:43.500> roll<00:07:43.680> up<00:07:43.800> to<00:07:43.979> the<00:07:44.099> uh 00:07:45.170 --> 00:07:45.180 align:start position:0% layer 11 and 12 they roll up to the uh 00:07:45.180 --> 00:07:47.689 align:start position:0% layer 11 and 12 they roll up to the uh to<00:07:45.660> the<00:07:45.900> role<00:07:46.139> of<00:07:46.259> one 00:07:47.689 --> 00:07:47.699 align:start position:0% to the role of one 00:07:47.699 --> 00:07:50.210 align:start position:0% to the role of one and<00:07:48.360> if<00:07:48.539> you<00:07:48.720> assume<00:07:49.139> that<00:07:49.380> there<00:07:49.560> is<00:07:49.680> Ezekiel 00:07:50.210 --> 00:07:50.220 align:start position:0% and if you assume that there is Ezekiel 00:07:50.220 --> 00:07:52.490 align:start position:0% and if you assume that there is Ezekiel proof<00:07:50.520> boosted<00:07:50.880> every<00:07:51.120> single<00:07:51.419> block<00:07:51.599> then 00:07:52.490 --> 00:07:52.500 align:start position:0% proof boosted every single block then 00:07:52.500 --> 00:07:54.710 align:start position:0% proof boosted every single block then now<00:07:52.680> what<00:07:52.860> you<00:07:53.039> can<00:07:53.160> do<00:07:53.280> is<00:07:53.460> do 00:07:54.710 --> 00:07:54.720 align:start position:0% now what you can do is do 00:07:54.720 --> 00:07:55.370 align:start position:0% now what you can do is do um 00:07:55.370 --> 00:07:55.380 align:start position:0% um 00:07:55.380 --> 00:07:58.450 align:start position:0% um instant<00:07:56.039> delivery<00:07:56.460> transaction<00:07:56.880> between 00:07:58.450 --> 00:07:58.460 align:start position:0% instant delivery transaction between 00:07:58.460 --> 00:08:01.070 align:start position:0% instant delivery transaction between say<00:07:59.460> this<00:07:59.699> one<00:07:59.819> 11<00:08:00.060> and<00:08:00.360> one<00:08:00.539> so<00:08:00.780> for<00:08:00.900> instance 00:08:01.070 --> 00:08:01.080 align:start position:0% say this one 11 and one so for instance 00:08:01.080 --> 00:08:03.830 align:start position:0% say this one 11 and one so for instance you<00:08:01.319> could<00:08:02.039> do<00:08:02.580> your<00:08:02.819> swap<00:08:03.120> here 00:08:03.830 --> 00:08:03.840 align:start position:0% you could do your swap here 00:08:03.840 --> 00:08:06.529 align:start position:0% you could do your swap here and<00:08:04.199> then<00:08:04.319> buy<00:08:04.560> your<00:08:04.740> nft<00:08:04.979> here 00:08:06.529 --> 00:08:06.539 align:start position:0% and then buy your nft here 00:08:06.539 --> 00:08:08.150 align:start position:0% and then buy your nft here it's<00:08:06.840> still<00:08:07.080> not<00:08:07.199> Atomic<00:08:07.620> because<00:08:07.800> you<00:08:08.039> can't 00:08:08.150 --> 00:08:08.160 align:start position:0% it's still not Atomic because you can't 00:08:08.160 --> 00:08:09.890 align:start position:0% it's still not Atomic because you can't revert<00:08:08.639> but<00:08:08.880> now<00:08:09.060> at<00:08:09.300> least<00:08:09.419> you<00:08:09.599> know<00:08:09.780> it's 00:08:09.890 --> 00:08:09.900 align:start position:0% revert but now at least you know it's 00:08:09.900 --> 00:08:11.570 align:start position:0% revert but now at least you know it's going<00:08:10.080> to<00:08:10.139> be<00:08:10.259> done<00:08:10.380> like<00:08:10.620> in<00:08:11.039> the<00:08:11.160> next<00:08:11.280> block 00:08:11.570 --> 00:08:11.580 align:start position:0% going to be done like in the next block 00:08:11.580 --> 00:08:14.330 align:start position:0% going to be done like in the next block or<00:08:12.000> one<00:08:12.360> block<00:08:12.539> apart 00:08:14.330 --> 00:08:14.340 align:start position:0% or one block apart 00:08:14.340 --> 00:08:15.950 align:start position:0% or one block apart that's<00:08:14.759> good<00:08:15.060> but<00:08:15.180> that's<00:08:15.360> still<00:08:15.479> not<00:08:15.660> what<00:08:15.840> we 00:08:15.950 --> 00:08:15.960 align:start position:0% that's good but that's still not what we 00:08:15.960 --> 00:08:17.089 align:start position:0% that's good but that's still not what we want 00:08:17.089 --> 00:08:17.099 align:start position:0% want 00:08:17.099 --> 00:08:19.430 align:start position:0% want so<00:08:17.460> what<00:08:17.639> about<00:08:17.819> uh<00:08:18.180> crush<00:08:18.539> or<00:08:18.660> atomicity<00:08:19.199> so 00:08:19.430 --> 00:08:19.440 align:start position:0% so what about uh crush or atomicity so 00:08:19.440 --> 00:08:22.610 align:start position:0% so what about uh crush or atomicity so I'm<00:08:19.620> going<00:08:19.740> to<00:08:19.860> propose<00:08:20.099> a<00:08:20.280> solution<00:08:20.460> for<00:08:20.699> this 00:08:22.610 --> 00:08:22.620 align:start position:0% I'm going to propose a solution for this 00:08:22.620 --> 00:08:24.830 align:start position:0% I'm going to propose a solution for this um<00:08:22.680> and<00:08:22.860> we're<00:08:23.039> going<00:08:23.160> to<00:08:23.220> assume<00:08:23.699> that<00:08:24.180> we're 00:08:24.830 --> 00:08:24.840 align:start position:0% um and we're going to assume that we're 00:08:24.840 --> 00:08:26.510 align:start position:0% um and we're going to assume that we're slicing<00:08:25.319> our<00:08:25.440> system<00:08:25.620> into<00:08:25.860> one<00:08:26.099> blockchain 00:08:26.510 --> 00:08:26.520 align:start position:0% slicing our system into one blockchain 00:08:26.520 --> 00:08:29.749 align:start position:0% slicing our system into one blockchain block<00:08:27.180> which<00:08:27.900> is<00:08:28.080> going<00:08:28.259> to<00:08:28.379> comprise<00:08:29.340> one 00:08:29.749 --> 00:08:29.759 align:start position:0% block which is going to comprise one 00:08:29.759 --> 00:08:31.249 align:start position:0% block which is going to comprise one block<00:08:29.940> for<00:08:30.180> every<00:08:30.300> charge<00:08:30.599> so<00:08:30.780> every<00:08:31.020> chart 00:08:31.249 --> 00:08:31.259 align:start position:0% block for every charge so every chart 00:08:31.259 --> 00:08:33.490 align:start position:0% block for every charge so every chart Advance<00:08:31.680> at<00:08:31.979> the<00:08:32.099> same<00:08:32.219> rate 00:08:33.490 --> 00:08:33.500 align:start position:0% Advance at the same rate 00:08:33.500 --> 00:08:36.230 align:start position:0% Advance at the same rate and<00:08:34.500> we<00:08:34.800> want<00:08:34.919> to<00:08:35.039> have<00:08:35.099> some<00:08:35.339> form<00:08:35.520> of<00:08:35.760> atomic 00:08:36.230 --> 00:08:36.240 align:start position:0% and we want to have some form of atomic 00:08:36.240 --> 00:08:37.790 align:start position:0% and we want to have some form of atomic crochet<00:08:36.539> transactions 00:08:37.790 --> 00:08:37.800 align:start position:0% crochet transactions 00:08:37.800 --> 00:08:39.769 align:start position:0% crochet transactions to<00:08:38.099> enable<00:08:38.339> this<00:08:38.580> sure<00:08:39.060> need<00:08:39.419> to<00:08:39.539> be<00:08:39.599> able<00:08:39.719> to 00:08:39.769 --> 00:08:39.779 align:start position:0% to enable this sure need to be able to 00:08:39.779 --> 00:08:42.469 align:start position:0% to enable this sure need to be able to send<00:08:39.959> messages<00:08:40.260> to<00:08:40.860> other<00:08:40.979> shards 00:08:42.469 --> 00:08:42.479 align:start position:0% send messages to other shards 00:08:42.479 --> 00:08:44.630 align:start position:0% send messages to other shards so<00:08:42.899> let's<00:08:43.020> just<00:08:43.320> take<00:08:43.740> the<00:08:43.919> most<00:08:44.219> nice 00:08:44.630 --> 00:08:44.640 align:start position:0% so let's just take the most nice 00:08:44.640 --> 00:08:47.570 align:start position:0% so let's just take the most nice possible<00:08:45.120> idea<00:08:45.480> which<00:08:46.260> is<00:08:46.440> eager<00:08:46.920> enter<00:08:47.279> chart 00:08:47.570 --> 00:08:47.580 align:start position:0% possible idea which is eager enter chart 00:08:47.580 --> 00:08:49.550 align:start position:0% possible idea which is eager enter chart blocking<00:08:48.180> so<00:08:48.480> you<00:08:48.720> just<00:08:48.839> process<00:08:49.140> all<00:08:49.380> your 00:08:49.550 --> 00:08:49.560 align:start position:0% blocking so you just process all your 00:08:49.560 --> 00:08:50.509 align:start position:0% blocking so you just process all your transaction 00:08:50.509 --> 00:08:50.519 align:start position:0% transaction 00:08:50.519 --> 00:08:52.970 align:start position:0% transaction at<00:08:51.000> some<00:08:51.120> point<00:08:51.240> you<00:08:51.480> hit<00:08:51.660> onto<00:08:52.080> a<00:08:52.620> transaction 00:08:52.970 --> 00:08:52.980 align:start position:0% at some point you hit onto a transaction 00:08:52.980 --> 00:08:54.050 align:start position:0% at some point you hit onto a transaction I<00:08:53.160> want<00:08:53.279> to<00:08:53.399> send<00:08:53.580> a<00:08:53.700> message<00:08:53.760> to<00:08:53.940> another 00:08:54.050 --> 00:08:54.060 align:start position:0% I want to send a message to another 00:08:54.060 --> 00:08:56.090 align:start position:0% I want to send a message to another charge<00:08:54.420> you<00:08:55.080> just<00:08:55.200> literally<00:08:55.620> call<00:08:55.860> that 00:08:56.090 --> 00:08:56.100 align:start position:0% charge you just literally call that 00:08:56.100 --> 00:08:57.769 align:start position:0% charge you just literally call that chart<00:08:56.279> you<00:08:56.700> wait<00:08:56.880> for<00:08:57.060> the<00:08:57.180> answer<00:08:57.300> and<00:08:57.660> then 00:08:57.769 --> 00:08:57.779 align:start position:0% chart you wait for the answer and then 00:08:57.779 --> 00:08:58.850 align:start position:0% chart you wait for the answer and then you<00:08:57.899> continue 00:08:58.850 --> 00:08:58.860 align:start position:0% you continue 00:08:58.860 --> 00:09:00.650 align:start position:0% you continue so 00:09:00.650 --> 00:09:00.660 align:start position:0% so 00:09:00.660 --> 00:09:01.910 align:start position:0% so this<00:09:01.140> is 00:09:01.910 --> 00:09:01.920 align:start position:0% this is 00:09:01.920 --> 00:09:03.710 align:start position:0% this is less<00:09:02.459> coincidence<00:09:02.880> sounds<00:09:03.300> and<00:09:03.600> it's 00:09:03.710 --> 00:09:03.720 align:start position:0% less coincidence sounds and it's 00:09:03.720 --> 00:09:05.090 align:start position:0% less coincidence sounds and it's somewhat<00:09:04.080> equivalent<00:09:04.440> to<00:09:04.620> what<00:09:04.800> strict 00:09:05.090 --> 00:09:05.100 align:start position:0% somewhat equivalent to what strict 00:09:05.100 --> 00:09:07.730 align:start position:0% somewhat equivalent to what strict access<00:09:05.279> list<00:09:05.640> do<00:09:06.000> because<00:09:06.660> at<00:09:07.080> do<00:09:07.440> in<00:09:07.620> the 00:09:07.730 --> 00:09:07.740 align:start position:0% access list do because at do in the 00:09:07.740 --> 00:09:09.110 align:start position:0% access list do because at do in the worst<00:09:07.920> case<00:09:08.040> you<00:09:08.339> have<00:09:08.459> the<00:09:08.640> same<00:09:08.760> throughput 00:09:09.110 --> 00:09:09.120 align:start position:0% worst case you have the same throughput 00:09:09.120 --> 00:09:11.810 align:start position:0% worst case you have the same throughput as<00:09:09.300> a<00:09:09.420> synchronous<00:09:09.720> blockchain<00:09:10.140> in<00:09:10.800> theory 00:09:11.810 --> 00:09:11.820 align:start position:0% as a synchronous blockchain in theory 00:09:11.820 --> 00:09:13.370 align:start position:0% as a synchronous blockchain in theory but<00:09:12.120> you<00:09:12.300> can<00:09:12.420> charge<00:09:12.540> fees<00:09:13.019> because<00:09:13.140> you<00:09:13.260> know 00:09:13.370 --> 00:09:13.380 align:start position:0% but you can charge fees because you know 00:09:13.380 --> 00:09:15.350 align:start position:0% but you can charge fees because you know exactly<00:09:13.680> which<00:09:13.860> transactions<00:09:14.459> are<00:09:14.700> crossing 00:09:15.350 --> 00:09:15.360 align:start position:0% exactly which transactions are crossing 00:09:15.360 --> 00:09:16.610 align:start position:0% exactly which transactions are crossing the<00:09:15.480> shards 00:09:16.610 --> 00:09:16.620 align:start position:0% the shards 00:09:16.620 --> 00:09:18.050 align:start position:0% the shards the<00:09:17.220> great<00:09:17.339> thing<00:09:17.519> is<00:09:17.640> you<00:09:17.760> don't<00:09:17.880> need<00:09:18.000> to 00:09:18.050 --> 00:09:18.060 align:start position:0% the great thing is you don't need to 00:09:18.060 --> 00:09:20.570 align:start position:0% the great thing is you don't need to specify<00:09:18.300> the<00:09:18.480> access<00:09:18.600> list<00:09:19.380> but<00:09:20.040> the<00:09:20.399> really 00:09:20.570 --> 00:09:20.580 align:start position:0% specify the access list but the really 00:09:20.580 --> 00:09:22.370 align:start position:0% specify the access list but the really really<00:09:20.820> bad<00:09:21.060> thing<00:09:21.300> in<00:09:21.540> practice<00:09:21.779> not<00:09:22.200> in 00:09:22.370 --> 00:09:22.380 align:start position:0% really bad thing in practice not in 00:09:22.380 --> 00:09:24.650 align:start position:0% really bad thing in practice not in theory<00:09:22.740> is<00:09:22.920> that<00:09:23.220> you're<00:09:23.880> assuming<00:09:24.300> that<00:09:24.540> all 00:09:24.650 --> 00:09:24.660 align:start position:0% theory is that you're assuming that all 00:09:24.660 --> 00:09:26.329 align:start position:0% theory is that you're assuming that all these<00:09:24.839> shards<00:09:25.200> are<00:09:25.320> being<00:09:25.440> validated<00:09:25.920> by 00:09:26.329 --> 00:09:26.339 align:start position:0% these shards are being validated by 00:09:26.339 --> 00:09:29.750 align:start position:0% these shards are being validated by different<00:09:27.380> uh<00:09:28.380> entities<00:09:28.680> and<00:09:28.980> so<00:09:29.160> the<00:09:29.339> latency 00:09:29.750 --> 00:09:29.760 align:start position:0% different uh entities and so the latency 00:09:29.760 --> 00:09:31.730 align:start position:0% different uh entities and so the latency for<00:09:30.420> one<00:09:30.540> chart<00:09:30.720> to<00:09:31.019> talk<00:09:31.080> to<00:09:31.200> one<00:09:31.320> another<00:09:31.440> is 00:09:31.730 --> 00:09:31.740 align:start position:0% for one chart to talk to one another is 00:09:31.740 --> 00:09:32.690 align:start position:0% for one chart to talk to one another is really<00:09:31.920> high 00:09:32.690 --> 00:09:32.700 align:start position:0% really high 00:09:32.700 --> 00:09:34.850 align:start position:0% really high and<00:09:33.240> so<00:09:33.420> in<00:09:33.839> reality<00:09:34.080> this<00:09:34.320> is<00:09:34.440> not<00:09:34.500> feasible 00:09:34.850 --> 00:09:34.860 align:start position:0% and so in reality this is not feasible 00:09:34.860 --> 00:09:36.829 align:start position:0% and so in reality this is not feasible because<00:09:35.040> the<00:09:35.279> latency<00:09:35.519> will<00:09:35.880> just<00:09:36.060> kill<00:09:36.240> any 00:09:36.829 --> 00:09:36.839 align:start position:0% because the latency will just kill any 00:09:36.839 --> 00:09:39.290 align:start position:0% because the latency will just kill any throughput<00:09:37.320> that<00:09:37.560> you<00:09:37.680> may<00:09:37.800> have<00:09:37.980> let's<00:09:38.880> try 00:09:39.290 --> 00:09:39.300 align:start position:0% throughput that you may have let's try 00:09:39.300 --> 00:09:40.910 align:start position:0% throughput that you may have let's try to<00:09:39.600> instead<00:09:40.019> reduce<00:09:40.200> the<00:09:40.560> number<00:09:40.740> of 00:09:40.910 --> 00:09:40.920 align:start position:0% to instead reduce the number of 00:09:40.920 --> 00:09:42.829 align:start position:0% to instead reduce the number of exchanges<00:09:41.519> between<00:09:41.760> charts<00:09:42.300> right<00:09:42.420> let's<00:09:42.600> try 00:09:42.829 --> 00:09:42.839 align:start position:0% exchanges between charts right let's try 00:09:42.839 --> 00:09:45.050 align:start position:0% exchanges between charts right let's try to<00:09:42.959> bound<00:09:43.260> this<00:09:43.500> very<00:09:43.740> tightly 00:09:45.050 --> 00:09:45.060 align:start position:0% to bound this very tightly 00:09:45.060 --> 00:09:47.090 align:start position:0% to bound this very tightly and<00:09:45.360> so<00:09:45.480> the<00:09:45.660> idea<00:09:45.839> would<00:09:46.080> be<00:09:46.200> to<00:09:46.440> divide<00:09:46.860> the 00:09:47.090 --> 00:09:47.100 align:start position:0% and so the idea would be to divide the 00:09:47.100 --> 00:09:49.550 align:start position:0% and so the idea would be to divide the the<00:09:47.339> block<00:09:47.519> time<00:09:47.760> into<00:09:47.940> multiple<00:09:48.300> slots<00:09:48.660> in 00:09:49.550 --> 00:09:49.560 align:start position:0% the block time into multiple slots in 00:09:49.560 --> 00:09:52.190 align:start position:0% the block time into multiple slots in the<00:09:49.680> first<00:09:49.800> slot<00:09:50.160> every<00:09:50.580> Shard<00:09:50.940> executes<00:09:51.480> its 00:09:52.190 --> 00:09:52.200 align:start position:0% the first slot every Shard executes its 00:09:52.200 --> 00:09:54.290 align:start position:0% the first slot every Shard executes its own<00:09:52.320> transactions<00:09:52.920> and<00:09:53.580> also<00:09:53.880> collects 00:09:54.290 --> 00:09:54.300 align:start position:0% own transactions and also collects 00:09:54.300 --> 00:09:56.570 align:start position:0% own transactions and also collects messages<00:09:54.420> to<00:09:54.779> send<00:09:54.899> to<00:09:55.080> other<00:09:55.200> shards 00:09:56.570 --> 00:09:56.580 align:start position:0% messages to send to other shards 00:09:56.580 --> 00:09:58.190 align:start position:0% messages to send to other shards in<00:09:56.940> the<00:09:57.060> second<00:09:57.180> slot 00:09:58.190 --> 00:09:58.200 align:start position:0% in the second slot 00:09:58.200 --> 00:10:00.949 align:start position:0% in the second slot all<00:09:58.800> the<00:09:58.980> shards<00:09:59.339> extension<00:09:59.700> messages 00:10:00.949 --> 00:10:00.959 align:start position:0% all the shards extension messages 00:10:00.959 --> 00:10:02.630 align:start position:0% all the shards extension messages and<00:10:01.440> then<00:10:01.500> they<00:10:01.680> run<00:10:01.860> the<00:10:02.040> messages<00:10:02.160> that<00:10:02.519> they 00:10:02.630 --> 00:10:02.640 align:start position:0% and then they run the messages that they 00:10:02.640 --> 00:10:03.530 align:start position:0% and then they run the messages that they receive 00:10:03.530 --> 00:10:03.540 align:start position:0% receive 00:10:03.540 --> 00:10:05.389 align:start position:0% receive optionally<00:10:04.320> you<00:10:04.560> can<00:10:04.680> keep<00:10:04.800> this<00:10:04.980> going<00:10:05.160> so 00:10:05.389 --> 00:10:05.399 align:start position:0% optionally you can keep this going so 00:10:05.399 --> 00:10:06.829 align:start position:0% optionally you can keep this going so you<00:10:05.519> can<00:10:05.640> have<00:10:05.700> many<00:10:05.880> many<00:10:06.120> slots<00:10:06.480> you<00:10:06.720> could 00:10:06.829 --> 00:10:06.839 align:start position:0% you can have many many slots you could 00:10:06.839 --> 00:10:09.470 align:start position:0% you can have many many slots you could say<00:10:06.959> all<00:10:07.320> messages<00:10:07.560> can<00:10:07.980> send<00:10:08.160> our<00:10:08.339> messages 00:10:09.470 --> 00:10:09.480 align:start position:0% say all messages can send our messages 00:10:09.480 --> 00:10:10.850 align:start position:0% say all messages can send our messages etc<00:10:09.899> etc 00:10:10.850 --> 00:10:10.860 align:start position:0% etc etc 00:10:10.860 --> 00:10:12.889 align:start position:0% etc etc I<00:10:11.459> think<00:10:11.580> in<00:10:11.880> practice<00:10:12.060> you<00:10:12.660> don't<00:10:12.779> really 00:10:12.889 --> 00:10:12.899 align:start position:0% I think in practice you don't really 00:10:12.899 --> 00:10:14.269 align:start position:0% I think in practice you don't really need<00:10:13.140> this<00:10:13.320> you<00:10:13.560> can<00:10:13.680> have<00:10:13.920> a<00:10:14.100> lot<00:10:14.160> of 00:10:14.269 --> 00:10:14.279 align:start position:0% need this you can have a lot of 00:10:14.279 --> 00:10:16.490 align:start position:0% need this you can have a lot of expressivity<00:10:14.820> with<00:10:15.060> just<00:10:15.240> like<00:10:15.480> one<00:10:15.660> hop<00:10:15.839> just 00:10:16.490 --> 00:10:16.500 align:start position:0% expressivity with just like one hop just 00:10:16.500 --> 00:10:18.110 align:start position:0% expressivity with just like one hop just one<00:10:16.920> short<00:10:17.100> talking<00:10:17.339> to<00:10:17.580> one<00:10:17.700> to<00:10:17.940> another 00:10:18.110 --> 00:10:18.120 align:start position:0% one short talking to one to another 00:10:18.120 --> 00:10:19.730 align:start position:0% one short talking to one to another shark 00:10:19.730 --> 00:10:19.740 align:start position:0% shark 00:10:19.740 --> 00:10:21.769 align:start position:0% shark so<00:10:20.100> this<00:10:20.279> is<00:10:20.459> still<00:10:20.700> a<00:10:21.120> bounded<00:10:21.600> message 00:10:21.769 --> 00:10:21.779 align:start position:0% so this is still a bounded message 00:10:21.779 --> 00:10:24.170 align:start position:0% so this is still a bounded message delivery<00:10:22.260> though<00:10:22.440> you<00:10:22.680> can't<00:10:22.740> revert<00:10:23.279> uh<00:10:24.060> you 00:10:24.170 --> 00:10:24.180 align:start position:0% delivery though you can't revert uh you 00:10:24.180 --> 00:10:26.570 align:start position:0% delivery though you can't revert uh you can't<00:10:24.300> revert<00:10:24.720> part<00:10:24.839> A<00:10:25.200> If<00:10:25.500> Part<00:10:25.740> B<00:10:25.980> fails<00:10:26.399> and 00:10:26.570 --> 00:10:26.580 align:start position:0% can't revert part A If Part B fails and 00:10:26.580 --> 00:10:29.269 align:start position:0% can't revert part A If Part B fails and that's<00:10:26.700> because<00:10:27.080> other<00:10:28.080> transactions<00:10:28.920> rely 00:10:29.269 --> 00:10:29.279 align:start position:0% that's because other transactions rely 00:10:29.279 --> 00:10:31.070 align:start position:0% that's because other transactions rely on<00:10:29.399> the<00:10:29.519> result<00:10:29.700> of<00:10:29.940> the<00:10:30.060> a<00:10:30.180> part<00:10:30.420> okay<00:10:30.720> so<00:10:30.959> this 00:10:31.070 --> 00:10:31.080 align:start position:0% on the result of the a part okay so this 00:10:31.080 --> 00:10:32.870 align:start position:0% on the result of the a part okay so this is<00:10:31.200> very<00:10:31.380> unclear<00:10:31.800> so<00:10:32.160> there's<00:10:32.339> a<00:10:32.519> graphic 00:10:32.870 --> 00:10:32.880 align:start position:0% is very unclear so there's a graphic 00:10:32.880 --> 00:10:33.590 align:start position:0% is very unclear so there's a graphic here 00:10:33.590 --> 00:10:33.600 align:start position:0% here 00:10:33.600 --> 00:10:35.930 align:start position:0% here so<00:10:34.200> say<00:10:34.500> I'm<00:10:34.740> saying<00:10:35.040> a<00:10:35.220> I'm<00:10:35.519> doing<00:10:35.640> my<00:10:35.820> local 00:10:35.930 --> 00:10:35.940 align:start position:0% so say I'm saying a I'm doing my local 00:10:35.940 --> 00:10:37.190 align:start position:0% so say I'm saying a I'm doing my local transactions 00:10:37.190 --> 00:10:37.200 align:start position:0% transactions 00:10:37.200 --> 00:10:39.650 align:start position:0% transactions I'm<00:10:37.920> doing<00:10:38.220> the<00:10:38.459> a<00:10:38.580> part<00:10:38.820> of<00:10:39.060> a<00:10:39.180> cross<00:10:39.420> chart 00:10:39.650 --> 00:10:39.660 align:start position:0% I'm doing the a part of a cross chart 00:10:39.660 --> 00:10:40.610 align:start position:0% I'm doing the a part of a cross chart transaction 00:10:40.610 --> 00:10:40.620 align:start position:0% transaction 00:10:40.620 --> 00:10:42.050 align:start position:0% transaction and<00:10:40.980> let's<00:10:41.100> say<00:10:41.279> that's<00:10:41.399> you<00:10:41.640> know<00:10:41.700> that's<00:10:41.940> a 00:10:42.050 --> 00:10:42.060 align:start position:0% and let's say that's you know that's a 00:10:42.060 --> 00:10:43.970 align:start position:0% and let's say that's you know that's a swap<00:10:42.360> so<00:10:42.600> both<00:10:42.839> of<00:10:43.019> these<00:10:43.200> will<00:10:43.380> be<00:10:43.500> swapping 00:10:43.970 --> 00:10:43.980 align:start position:0% swap so both of these will be swapping 00:10:43.980 --> 00:10:46.790 align:start position:0% swap so both of these will be swapping and<00:10:44.220> then<00:10:44.399> on<00:10:44.880> video<00:10:45.060> will<00:10:45.360> be<00:10:45.420> buying<00:10:45.660> an<00:10:45.779> ft 00:10:46.790 --> 00:10:46.800 align:start position:0% and then on video will be buying an ft 00:10:46.800 --> 00:10:48.710 align:start position:0% and then on video will be buying an ft so<00:10:47.220> this<00:10:47.459> transaction<00:10:47.820> here 00:10:48.710 --> 00:10:48.720 align:start position:0% so this transaction here 00:10:48.720 --> 00:10:50.690 align:start position:0% so this transaction here the<00:10:49.079> a<00:10:49.200> part<00:10:49.380> depends<00:10:49.860> on<00:10:49.980> the<00:10:50.100> a<00:10:50.220> part<00:10:50.399> of<00:10:50.579> the 00:10:50.690 --> 00:10:50.700 align:start position:0% the a part depends on the a part of the 00:10:50.700 --> 00:10:52.850 align:start position:0% the a part depends on the a part of the first<00:10:50.820> one<00:10:51.000> because<00:10:51.660> the<00:10:51.959> first<00:10:52.079> one<00:10:52.260> swapped 00:10:52.850 --> 00:10:52.860 align:start position:0% first one because the first one swapped 00:10:52.860 --> 00:10:55.190 align:start position:0% first one because the first one swapped uh<00:10:53.519> say<00:10:53.640> Bitcoin<00:10:54.120> for<00:10:54.240> either<00:10:54.360> so<00:10:54.779> it<00:10:54.899> moved 00:10:55.190 --> 00:10:55.200 align:start position:0% uh say Bitcoin for either so it moved 00:10:55.200 --> 00:10:57.290 align:start position:0% uh say Bitcoin for either so it moved the<00:10:55.320> price<00:10:55.440> so<00:10:56.100> this<00:10:56.339> one<00:10:56.459> will<00:10:56.760> use<00:10:57.000> the<00:10:57.180> price 00:10:57.290 --> 00:10:57.300 align:start position:0% the price so this one will use the price 00:10:57.300 --> 00:10:59.509 align:start position:0% the price so this one will use the price from<00:10:57.660> from<00:10:57.899> that<00:10:58.200> was<00:10:58.380> moved<00:10:58.680> here<00:10:58.800> so<00:10:59.339> there 00:10:59.509 --> 00:10:59.519 align:start position:0% from from that was moved here so there 00:10:59.519 --> 00:11:01.490 align:start position:0% from from that was moved here so there is<00:10:59.640> a<00:10:59.760> dependency<00:11:00.180> link 00:11:01.490 --> 00:11:01.500 align:start position:0% is a dependency link 00:11:01.500 --> 00:11:03.350 align:start position:0% is a dependency link and<00:11:01.920> because<00:11:02.100> of<00:11:02.279> this<00:11:02.399> dependency<00:11:02.820> link<00:11:03.060> you 00:11:03.350 --> 00:11:03.360 align:start position:0% and because of this dependency link you 00:11:03.360 --> 00:11:06.050 align:start position:0% and because of this dependency link you can<00:11:03.480> just<00:11:03.600> revert<00:11:04.500> uh<00:11:05.220> you<00:11:05.459> can<00:11:05.519> just<00:11:05.640> revert 00:11:06.050 --> 00:11:06.060 align:start position:0% can just revert uh you can just revert 00:11:06.060 --> 00:11:07.430 align:start position:0% can just revert uh you can just revert this<00:11:06.180> transaction<00:11:06.480> if<00:11:06.779> this<00:11:07.019> one<00:11:07.140> fails 00:11:07.430 --> 00:11:07.440 align:start position:0% this transaction if this one fails 00:11:07.440 --> 00:11:09.290 align:start position:0% this transaction if this one fails because<00:11:07.560> this<00:11:07.740> one<00:11:07.920> uses<00:11:08.160> the<00:11:08.339> result 00:11:09.290 --> 00:11:09.300 align:start position:0% because this one uses the result 00:11:09.300 --> 00:11:10.550 align:start position:0% because this one uses the result so<00:11:09.600> this<00:11:09.779> is<00:11:09.839> the<00:11:09.959> problem<00:11:10.140> that<00:11:10.440> we're 00:11:10.550 --> 00:11:10.560 align:start position:0% so this is the problem that we're 00:11:10.560 --> 00:11:12.470 align:start position:0% so this is the problem that we're dealing<00:11:10.860> with 00:11:12.470 --> 00:11:12.480 align:start position:0% dealing with 00:11:12.480 --> 00:11:15.170 align:start position:0% dealing with and<00:11:13.200> the<00:11:13.560> general<00:11:13.760> properties<00:11:14.760> that 00:11:15.170 --> 00:11:15.180 align:start position:0% and the general properties that 00:11:15.180 --> 00:11:18.110 align:start position:0% and the general properties that atomicity<00:11:15.839> requires<00:11:16.500> synchronicity 00:11:18.110 --> 00:11:18.120 align:start position:0% atomicity requires synchronicity 00:11:18.120 --> 00:11:21.230 align:start position:0% atomicity requires synchronicity basically<00:11:18.920> local<00:11:19.920> transaction<00:11:20.519> can<00:11:20.820> still<00:11:21.060> be 00:11:21.230 --> 00:11:21.240 align:start position:0% basically local transaction can still be 00:11:21.240 --> 00:11:23.269 align:start position:0% basically local transaction can still be processed<00:11:21.660> separately<00:11:22.079> but<00:11:22.740> we<00:11:22.920> would<00:11:23.100> like 00:11:23.269 --> 00:11:23.279 align:start position:0% processed separately but we would like 00:11:23.279 --> 00:11:25.090 align:start position:0% processed separately but we would like all<00:11:23.579> the<00:11:23.760> crocheting<00:11:24.180> transaction<00:11:24.480> to<00:11:24.839> be 00:11:25.090 --> 00:11:25.100 align:start position:0% all the crocheting transaction to be 00:11:25.100 --> 00:11:27.829 align:start position:0% all the crocheting transaction to be executed<00:11:26.100> as<00:11:26.459> though<00:11:26.700> it<00:11:27.240> was<00:11:27.360> a<00:11:27.480> single 00:11:27.829 --> 00:11:27.839 align:start position:0% executed as though it was a single 00:11:27.839 --> 00:11:29.810 align:start position:0% executed as though it was a single person<00:11:28.140> executing<00:11:28.800> them 00:11:29.810 --> 00:11:29.820 align:start position:0% person executing them 00:11:29.820 --> 00:11:31.490 align:start position:0% person executing them right 00:11:31.490 --> 00:11:31.500 align:start position:0% right 00:11:31.500 --> 00:11:32.150 align:start position:0% right um 00:11:32.150 --> 00:11:32.160 align:start position:0% um 00:11:32.160 --> 00:11:33.889 align:start position:0% um so<00:11:32.579> we<00:11:32.700> have<00:11:32.880> a<00:11:32.940> problem<00:11:33.120> which<00:11:33.420> is<00:11:33.480> we<00:11:33.779> don't 00:11:33.889 --> 00:11:33.899 align:start position:0% so we have a problem which is we don't 00:11:33.899 --> 00:11:36.230 align:start position:0% so we have a problem which is we don't want<00:11:34.140> chart<00:11:35.100> to<00:11:35.339> talk<00:11:35.519> to<00:11:35.760> each<00:11:35.880> other<00:11:36.000> too 00:11:36.230 --> 00:11:36.240 align:start position:0% want chart to talk to each other too 00:11:36.240 --> 00:11:38.449 align:start position:0% want chart to talk to each other too much<00:11:36.839> solution<00:11:37.260> to<00:11:37.560> that<00:11:37.680> is<00:11:37.860> to<00:11:38.040> create<00:11:38.220> a 00:11:38.449 --> 00:11:38.459 align:start position:0% much solution to that is to create a 00:11:38.459 --> 00:11:39.590 align:start position:0% much solution to that is to create a special<00:11:38.579> chart<00:11:38.820> and<00:11:39.120> I'm<00:11:39.240> going<00:11:39.360> to<00:11:39.360> call<00:11:39.480> it 00:11:39.590 --> 00:11:39.600 align:start position:0% special chart and I'm going to call it 00:11:39.600 --> 00:11:40.970 align:start position:0% special chart and I'm going to call it the<00:11:39.779> atomic<00:11:40.140> shard 00:11:40.970 --> 00:11:40.980 align:start position:0% the atomic shard 00:11:40.980 --> 00:11:43.370 align:start position:0% the atomic shard that<00:11:41.700> will<00:11:41.880> execute<00:11:42.360> all<00:11:42.720> the<00:11:42.839> cross-shar 00:11:43.370 --> 00:11:43.380 align:start position:0% that will execute all the cross-shar 00:11:43.380 --> 00:11:45.110 align:start position:0% that will execute all the cross-shar transactions 00:11:45.110 --> 00:11:45.120 align:start position:0% transactions 00:11:45.120 --> 00:11:47.509 align:start position:0% transactions and<00:11:45.420> we<00:11:45.540> have<00:11:45.660> a<00:11:45.779> second<00:11:45.839> problem<00:11:46.079> is<00:11:46.260> that<00:11:46.560> to 00:11:47.509 --> 00:11:47.519 align:start position:0% and we have a second problem is that to 00:11:47.519 --> 00:11:49.130 align:start position:0% and we have a second problem is that to execute<00:11:48.000> all<00:11:48.360> the<00:11:48.480> crosstalk<00:11:48.899> transaction 00:11:49.130 --> 00:11:49.140 align:start position:0% execute all the crosstalk transaction 00:11:49.140 --> 00:11:50.810 align:start position:0% execute all the crosstalk transaction you<00:11:49.380> need<00:11:49.500> to<00:11:49.620> state<00:11:49.740> from<00:11:50.040> all<00:11:50.220> the<00:11:50.339> charts 00:11:50.810 --> 00:11:50.820 align:start position:0% you need to state from all the charts 00:11:50.820 --> 00:11:53.329 align:start position:0% you need to state from all the charts right<00:11:51.060> and<00:11:51.720> this<00:11:51.899> is<00:11:52.019> this<00:11:52.320> removes<00:11:52.800> one<00:11:53.220> of 00:11:53.329 --> 00:11:53.339 align:start position:0% right and this is this removes one of 00:11:53.339 --> 00:11:54.949 align:start position:0% right and this is this removes one of the<00:11:53.459> big<00:11:53.579> points<00:11:53.940> of<00:11:54.120> shorting<00:11:54.540> which<00:11:54.660> is<00:11:54.779> that 00:11:54.949 --> 00:11:54.959 align:start position:0% the big points of shorting which is that 00:11:54.959 --> 00:11:56.630 align:start position:0% the big points of shorting which is that you<00:11:55.079> can<00:11:55.200> separate<00:11:55.560> the<00:11:55.740> the<00:11:56.100> state<00:11:56.459> between 00:11:56.630 --> 00:11:56.640 align:start position:0% you can separate the the state between 00:11:56.640 --> 00:11:58.610 align:start position:0% you can separate the the state between all<00:11:56.880> the<00:11:57.060> shards<00:11:57.480> so 00:11:58.610 --> 00:11:58.620 align:start position:0% all the shards so 00:11:58.620 --> 00:12:01.310 align:start position:0% all the shards so uh<00:11:59.279> the<00:11:59.579> solution<00:11:59.760> to<00:12:00.000> that<00:12:00.120> is<00:12:00.899> to<00:12:01.079> make<00:12:01.200> the 00:12:01.310 --> 00:12:01.320 align:start position:0% uh the solution to that is to make the 00:12:01.320 --> 00:12:03.889 align:start position:0% uh the solution to that is to make the execution<00:12:01.620> in<00:12:01.920> the<00:12:02.160> atomic<00:12:03.120> chart<00:12:03.300> stateless 00:12:03.889 --> 00:12:03.899 align:start position:0% execution in the atomic chart stateless 00:12:03.899 --> 00:12:06.230 align:start position:0% execution in the atomic chart stateless and<00:12:04.740> that<00:12:04.920> means<00:12:05.160> you<00:12:05.220> will<00:12:05.399> supply<00:12:05.579> all<00:12:06.120> the 00:12:06.230 --> 00:12:06.240 align:start position:0% and that means you will supply all the 00:12:06.240 --> 00:12:08.630 align:start position:0% and that means you will supply all the state<00:12:06.360> that's<00:12:06.600> being<00:12:06.779> accessed<00:12:07.260> by<00:12:08.160> the<00:12:08.399> the 00:12:08.630 --> 00:12:08.640 align:start position:0% state that's being accessed by the the 00:12:08.640 --> 00:12:09.949 align:start position:0% state that's being accessed by the the transactions 00:12:09.949 --> 00:12:09.959 align:start position:0% transactions 00:12:09.959 --> 00:12:11.990 align:start position:0% transactions for<00:12:10.620> the<00:12:10.800> atomic<00:12:11.160> short 00:12:11.990 --> 00:12:12.000 align:start position:0% for the atomic short 00:12:12.000 --> 00:12:13.910 align:start position:0% for the atomic short so<00:12:12.540> uh<00:12:12.779> This<00:12:12.959> sounds<00:12:13.079> too<00:12:13.320> good<00:12:13.500> so<00:12:13.680> where's 00:12:13.910 --> 00:12:13.920 align:start position:0% so uh This sounds too good so where's 00:12:13.920 --> 00:12:15.230 align:start position:0% so uh This sounds too good so where's the<00:12:14.160> poop 00:12:15.230 --> 00:12:15.240 align:start position:0% the poop 00:12:15.240 --> 00:12:17.750 align:start position:0% the poop the<00:12:15.720> poop<00:12:15.839> is<00:12:16.079> that<00:12:16.320> you<00:12:17.220> need<00:12:17.399> to<00:12:17.459> simulate 00:12:17.750 --> 00:12:17.760 align:start position:0% the poop is that you need to simulate 00:12:17.760 --> 00:12:19.310 align:start position:0% the poop is that you need to simulate transactions 00:12:19.310 --> 00:12:19.320 align:start position:0% transactions 00:12:19.320 --> 00:12:19.910 align:start position:0% transactions um 00:12:19.910 --> 00:12:19.920 align:start position:0% um 00:12:19.920 --> 00:12:22.790 align:start position:0% um on<00:12:20.279> each<00:12:20.519> chart<00:12:20.700> individually<00:12:21.180> so 00:12:22.790 --> 00:12:22.800 align:start position:0% on each chart individually so 00:12:22.800 --> 00:12:24.949 align:start position:0% on each chart individually so in<00:12:23.160> general<00:12:23.339> I<00:12:23.519> need<00:12:23.640> VM<00:12:23.940> given<00:12:24.600> that<00:12:24.839> you're 00:12:24.949 --> 00:12:24.959 align:start position:0% in general I need VM given that you're 00:12:24.959 --> 00:12:26.509 align:start position:0% in general I need VM given that you're not<00:12:25.140> sure<00:12:25.260> the<00:12:25.440> state<00:12:25.620> it's<00:12:25.800> impossible<00:12:26.220> to 00:12:26.509 --> 00:12:26.519 align:start position:0% not sure the state it's impossible to 00:12:26.519 --> 00:12:28.550 align:start position:0% not sure the state it's impossible to collect<00:12:26.760> all<00:12:26.940> the<00:12:27.060> storage<00:12:27.180> slots<00:12:27.660> accessed 00:12:28.550 --> 00:12:28.560 align:start position:0% collect all the storage slots accessed 00:12:28.560 --> 00:12:29.990 align:start position:0% collect all the storage slots accessed by<00:12:28.680> a<00:12:28.800> transaction 00:12:29.990 --> 00:12:30.000 align:start position:0% by a transaction 00:12:30.000 --> 00:12:31.550 align:start position:0% by a transaction you<00:12:30.300> can<00:12:30.420> approximate<00:12:30.959> and<00:12:31.140> the<00:12:31.260> easiest<00:12:31.440> way 00:12:31.550 --> 00:12:31.560 align:start position:0% you can approximate and the easiest way 00:12:31.560 --> 00:12:33.650 align:start position:0% you can approximate and the easiest way to<00:12:31.740> approximate<00:12:32.160> is<00:12:32.399> just<00:12:32.519> to<00:12:32.700> run<00:12:32.880> a 00:12:33.650 --> 00:12:33.660 align:start position:0% to approximate is just to run a 00:12:33.660 --> 00:12:35.210 align:start position:0% to approximate is just to run a transaction<00:12:33.959> against<00:12:34.440> the<00:12:34.740> current<00:12:34.920> state 00:12:35.210 --> 00:12:35.220 align:start position:0% transaction against the current state 00:12:35.220 --> 00:12:37.009 align:start position:0% transaction against the current state and<00:12:35.700> just<00:12:35.880> assume<00:12:36.360> that<00:12:36.540> the<00:12:36.720> transaction 00:12:37.009 --> 00:12:37.019 align:start position:0% and just assume that the transaction 00:12:37.019 --> 00:12:39.230 align:start position:0% and just assume that the transaction before<00:12:37.260> it<00:12:37.560> will<00:12:37.800> not<00:12:37.920> revert<00:12:38.339> so<00:12:38.640> you<00:12:39.120> know 00:12:39.230 --> 00:12:39.240 align:start position:0% before it will not revert so you know 00:12:39.240 --> 00:12:41.630 align:start position:0% before it will not revert so you know here<00:12:39.540> it's<00:12:39.720> easy<00:12:39.839> you<00:12:40.079> just<00:12:40.200> run<00:12:40.320> the<00:12:40.500> state<00:12:40.680> of 00:12:41.630 --> 00:12:41.640 align:start position:0% here it's easy you just run the state of 00:12:41.640 --> 00:12:43.129 align:start position:0% here it's easy you just run the state of the<00:12:41.760> first<00:12:41.880> transaction<00:12:42.300> against<00:12:42.540> the<00:12:42.779> state 00:12:43.129 --> 00:12:43.139 align:start position:0% the first transaction against the state 00:12:43.139 --> 00:12:44.930 align:start position:0% the first transaction against the state after<00:12:43.380> all<00:12:43.680> the<00:12:43.800> local<00:12:43.920> transactions<00:12:44.519> for 00:12:44.930 --> 00:12:44.940 align:start position:0% after all the local transactions for 00:12:44.940 --> 00:12:46.790 align:start position:0% after all the local transactions for this<00:12:45.120> one<00:12:45.240> you<00:12:45.480> just<00:12:45.600> assume<00:12:46.019> this<00:12:46.139> wall<00:12:46.320> this 00:12:46.790 --> 00:12:46.800 align:start position:0% this one you just assume this wall this 00:12:46.800 --> 00:12:49.670 align:start position:0% this one you just assume this wall this one<00:12:46.860> will<00:12:47.040> revert<00:12:47.940> and<00:12:48.420> execute<00:12:48.899> and<00:12:49.320> simulate 00:12:49.670 --> 00:12:49.680 align:start position:0% one will revert and execute and simulate 00:12:49.680 --> 00:12:52.129 align:start position:0% one will revert and execute and simulate but<00:12:50.459> maybe<00:12:50.579> it<00:12:50.820> will<00:12:50.940> revert<00:12:51.300> so<00:12:51.420> maybe<00:12:51.660> your 00:12:52.129 --> 00:12:52.139 align:start position:0% but maybe it will revert so maybe your 00:12:52.139 --> 00:12:54.650 align:start position:0% but maybe it will revert so maybe your simulation<00:12:52.560> will<00:12:52.800> be<00:12:52.920> incorrect 00:12:54.650 --> 00:12:54.660 align:start position:0% simulation will be incorrect 00:12:54.660 --> 00:12:56.150 align:start position:0% simulation will be incorrect everything<00:12:55.079> you<00:12:55.440> can<00:12:55.500> do<00:12:55.560> with<00:12:55.680> anything<00:12:55.860> so 00:12:56.150 --> 00:12:56.160 align:start position:0% everything you can do with anything so 00:12:56.160 --> 00:12:57.350 align:start position:0% everything you can do with anything so you<00:12:56.339> just 00:12:57.350 --> 00:12:57.360 align:start position:0% you just 00:12:57.360 --> 00:12:57.949 align:start position:0% you just um 00:12:57.949 --> 00:12:57.959 align:start position:0% um 00:12:57.959 --> 00:12:59.629 align:start position:0% um tell<00:12:58.320> The<00:12:58.560> Shard<00:12:58.800> well 00:12:59.629 --> 00:12:59.639 align:start position:0% tell The Shard well 00:12:59.639 --> 00:13:00.410 align:start position:0% tell The Shard well um 00:13:00.410 --> 00:13:00.420 align:start position:0% um 00:13:00.420 --> 00:13:01.910 align:start position:0% um this<00:13:00.839> transaction<00:13:01.139> is<00:13:01.320> going<00:13:01.500> to<00:13:01.500> touch<00:13:01.740> this 00:13:01.910 --> 00:13:01.920 align:start position:0% this transaction is going to touch this 00:13:01.920 --> 00:13:04.009 align:start position:0% this transaction is going to touch this slot<00:13:02.279> or<00:13:02.639> you<00:13:02.760> can<00:13:02.880> give<00:13:03.120> him<00:13:03.240> some<00:13:03.480> logic<00:13:03.839> to 00:13:04.009 --> 00:13:04.019 align:start position:0% slot or you can give him some logic to 00:13:04.019 --> 00:13:06.230 align:start position:0% slot or you can give him some logic to find<00:13:04.139> all<00:13:04.320> the<00:13:04.500> slots<00:13:04.740> are<00:13:04.920> being<00:13:05.100> touched 00:13:06.230 --> 00:13:06.240 align:start position:0% find all the slots are being touched 00:13:06.240 --> 00:13:07.850 align:start position:0% find all the slots are being touched and<00:13:06.660> there's<00:13:06.839> many<00:13:07.019> ways<00:13:07.260> to<00:13:07.440> do<00:13:07.500> this<00:13:07.620> that 00:13:07.850 --> 00:13:07.860 align:start position:0% and there's many ways to do this that 00:13:07.860 --> 00:13:09.650 align:start position:0% and there's many ways to do this that can<00:13:08.040> be<00:13:08.100> explored<00:13:08.519> it<00:13:09.000> could<00:13:09.180> just<00:13:09.300> be<00:13:09.420> some 00:13:09.650 --> 00:13:09.660 align:start position:0% can be explored it could just be some 00:13:09.660 --> 00:13:12.230 align:start position:0% can be explored it could just be some evm<00:13:10.019> code<00:13:10.200> that<00:13:10.500> just<00:13:10.620> touches<00:13:10.980> the<00:13:11.100> slots 00:13:12.230 --> 00:13:12.240 align:start position:0% evm code that just touches the slots 00:13:12.240 --> 00:13:13.790 align:start position:0% evm code that just touches the slots could<00:13:12.540> be<00:13:12.720> some<00:13:13.019> kind<00:13:13.139> of<00:13:13.260> infrological 00:13:13.790 --> 00:13:13.800 align:start position:0% could be some kind of infrological 00:13:13.800 --> 00:13:15.290 align:start position:0% could be some kind of infrological information<00:13:14.040> or<00:13:14.519> even<00:13:14.639> out<00:13:14.880> of<00:13:15.060> protocol 00:13:15.290 --> 00:13:15.300 align:start position:0% information or even out of protocol 00:13:15.300 --> 00:13:16.850 align:start position:0% information or even out of protocol information<00:13:15.660> that<00:13:16.019> is<00:13:16.139> not<00:13:16.260> being<00:13:16.380> validated 00:13:16.850 --> 00:13:16.860 align:start position:0% information that is not being validated 00:13:16.860 --> 00:13:18.889 align:start position:0% information that is not being validated but<00:13:17.100> that's<00:13:17.220> being<00:13:17.459> sent<00:13:17.760> to<00:13:18.360> the<00:13:18.480> to<00:13:18.720> the 00:13:18.889 --> 00:13:18.899 align:start position:0% but that's being sent to the to the 00:13:18.899 --> 00:13:21.410 align:start position:0% but that's being sent to the to the sequencers<00:13:19.519> so<00:13:20.519> I<00:13:20.700> want<00:13:20.820> to<00:13:21.000> make<00:13:21.060> things<00:13:21.240> a 00:13:21.410 --> 00:13:21.420 align:start position:0% sequencers so I want to make things a 00:13:21.420 --> 00:13:22.910 align:start position:0% sequencers so I want to make things a little<00:13:21.480> bit<00:13:21.660> more<00:13:21.779> clear<00:13:22.019> so<00:13:22.320> here's<00:13:22.740> a 00:13:22.910 --> 00:13:22.920 align:start position:0% little bit more clear so here's a 00:13:22.920 --> 00:13:26.090 align:start position:0% little bit more clear so here's a Crosshair<00:13:23.579> transaction<00:13:24.000> very<00:13:24.660> abstract<00:13:25.100> it 00:13:26.090 --> 00:13:26.100 align:start position:0% Crosshair transaction very abstract it 00:13:26.100 --> 00:13:28.370 align:start position:0% Crosshair transaction very abstract it computes<00:13:26.579> things<00:13:26.880> be<00:13:27.360> on<00:13:27.660> some<00:13:27.839> State<00:13:28.079> and 00:13:28.370 --> 00:13:28.380 align:start position:0% computes things be on some State and 00:13:28.380 --> 00:13:30.230 align:start position:0% computes things be on some State and this<00:13:28.560> state<00:13:28.740> might<00:13:29.160> change<00:13:29.399> right<00:13:29.760> we're<00:13:30.060> not 00:13:30.230 --> 00:13:30.240 align:start position:0% this state might change right we're not 00:13:30.240 --> 00:13:32.030 align:start position:0% this state might change right we're not exactly<00:13:30.660> sure<00:13:30.779> what<00:13:31.019> it<00:13:31.139> is 00:13:32.030 --> 00:13:32.040 align:start position:0% exactly sure what it is 00:13:32.040 --> 00:13:33.769 align:start position:0% exactly sure what it is then<00:13:32.579> he's<00:13:32.760> going<00:13:32.940> to<00:13:33.000> send<00:13:33.180> a<00:13:33.360> message<00:13:33.480> to 00:13:33.769 --> 00:13:33.779 align:start position:0% then he's going to send a message to 00:13:33.779 --> 00:13:35.810 align:start position:0% then he's going to send a message to short<00:13:33.959> B<00:13:34.260> and<00:13:34.980> this<00:13:35.100> message<00:13:35.279> is<00:13:35.519> going<00:13:35.700> to 00:13:35.810 --> 00:13:35.820 align:start position:0% short B and this message is going to 00:13:35.820 --> 00:13:38.030 align:start position:0% short B and this message is going to depend<00:13:36.000> on<00:13:36.180> the<00:13:36.300> result<00:13:36.420> of<00:13:36.660> the<00:13:36.720> computation 00:13:38.030 --> 00:13:38.040 align:start position:0% depend on the result of the computation 00:13:38.040 --> 00:13:41.030 align:start position:0% depend on the result of the computation uh<00:13:38.760> that<00:13:39.180> message<00:13:39.420> will<00:13:39.720> have<00:13:39.959> a<00:13:40.079> result 00:13:41.030 --> 00:13:41.040 align:start position:0% uh that message will have a result 00:13:41.040 --> 00:13:42.590 align:start position:0% uh that message will have a result when<00:13:41.399> I<00:13:41.639> compute<00:13:41.880> something<00:13:42.000> based<00:13:42.420> on<00:13:42.480> that 00:13:42.590 --> 00:13:42.600 align:start position:0% when I compute something based on that 00:13:42.600 --> 00:13:43.430 align:start position:0% when I compute something based on that result 00:13:43.430 --> 00:13:43.440 align:start position:0% result 00:13:43.440 --> 00:13:45.230 align:start position:0% result and<00:13:43.920> we're<00:13:44.040> also<00:13:44.279> going<00:13:44.399> to<00:13:44.639> send<00:13:44.940> the<00:13:45.120> results 00:13:45.230 --> 00:13:45.240 align:start position:0% and we're also going to send the results 00:13:45.240 --> 00:13:47.090 align:start position:0% and we're also going to send the results to<00:13:45.600> sort<00:13:45.779> C<00:13:46.139> and<00:13:46.560> then<00:13:46.680> do<00:13:46.860> some<00:13:46.980> more 00:13:47.090 --> 00:13:47.100 align:start position:0% to sort C and then do some more 00:13:47.100 --> 00:13:49.310 align:start position:0% to sort C and then do some more computation<00:13:47.579> so<00:13:48.240> this<00:13:48.540> shows<00:13:48.839> you<00:13:48.899> like<00:13:49.139> sort 00:13:49.310 --> 00:13:49.320 align:start position:0% computation so this shows you like sort 00:13:49.320 --> 00:13:50.810 align:start position:0% computation so this shows you like sort of<00:13:49.380> the<00:13:49.500> dependency<00:13:49.800> we<00:13:50.100> have<00:13:50.220> right<00:13:50.399> we<00:13:50.639> can 00:13:50.810 --> 00:13:50.820 align:start position:0% of the dependency we have right we can 00:13:50.820 --> 00:13:53.329 align:start position:0% of the dependency we have right we can depend<00:13:51.120> on<00:13:51.360> the<00:13:51.480> results<00:13:51.660> from<00:13:51.959> one<00:13:52.200> chart<00:13:52.440> we 00:13:53.329 --> 00:13:53.339 align:start position:0% depend on the results from one chart we 00:13:53.339 --> 00:13:55.310 align:start position:0% depend on the results from one chart we can<00:13:53.519> send<00:13:54.120> to<00:13:54.300> our<00:13:54.480> chart<00:13:54.660> things<00:13:54.959> that<00:13:55.200> have 00:13:55.310 --> 00:13:55.320 align:start position:0% can send to our chart things that have 00:13:55.320 --> 00:13:56.629 align:start position:0% can send to our chart things that have been<00:13:55.440> computed 00:13:56.629 --> 00:13:56.639 align:start position:0% been computed 00:13:56.639 --> 00:13:57.949 align:start position:0% been computed and<00:13:57.000> so<00:13:57.120> this<00:13:57.240> will<00:13:57.360> be<00:13:57.480> important<00:13:57.779> to 00:13:57.949 --> 00:13:57.959 align:start position:0% and so this will be important to 00:13:57.959 --> 00:13:59.870 align:start position:0% and so this will be important to understand<00:13:58.079> later 00:13:59.870 --> 00:13:59.880 align:start position:0% understand later 00:13:59.880 --> 00:14:03.350 align:start position:0% understand later so<00:14:00.480> to<00:14:00.800> rephrase<00:14:01.800> what<00:14:02.040> I'm<00:14:02.160> proposing 00:14:03.350 --> 00:14:03.360 align:start position:0% so to rephrase what I'm proposing 00:14:03.360 --> 00:14:05.509 align:start position:0% so to rephrase what I'm proposing before<00:14:03.959> we<00:14:04.200> dig<00:14:04.440> deeper<00:14:04.800> into<00:14:04.860> the<00:14:05.160> problems 00:14:05.509 --> 00:14:05.519 align:start position:0% before we dig deeper into the problems 00:14:05.519 --> 00:14:07.490 align:start position:0% before we dig deeper into the problems like<00:14:05.820> I've<00:14:06.300> showed<00:14:06.660> you<00:14:06.720> only<00:14:06.959> a<00:14:07.200> small<00:14:07.320> part 00:14:07.490 --> 00:14:07.500 align:start position:0% like I've showed you only a small part 00:14:07.500 --> 00:14:10.550 align:start position:0% like I've showed you only a small part of<00:14:07.620> the<00:14:07.740> poop<00:14:07.920> a<00:14:08.519> lot<00:14:08.639> more<00:14:08.820> poop<00:14:09.000> coming<00:14:09.300> up 00:14:10.550 --> 00:14:10.560 align:start position:0% of the poop a lot more poop coming up 00:14:10.560 --> 00:14:11.150 align:start position:0% of the poop a lot more poop coming up um 00:14:11.150 --> 00:14:11.160 align:start position:0% um 00:14:11.160 --> 00:14:14.329 align:start position:0% um but<00:14:11.639> the<00:14:11.880> scheme<00:14:12.180> is<00:14:12.240> this<00:14:12.480> phase<00:14:13.139> one 00:14:14.329 --> 00:14:14.339 align:start position:0% but the scheme is this phase one 00:14:14.339 --> 00:14:16.190 align:start position:0% but the scheme is this phase one uh<00:14:15.000> the<00:14:15.180> short<00:14:15.360> execute<00:14:15.899> the<00:14:16.019> local 00:14:16.190 --> 00:14:16.200 align:start position:0% uh the short execute the local 00:14:16.200 --> 00:14:18.050 align:start position:0% uh the short execute the local transaction<00:14:16.680> and<00:14:17.040> the<00:14:17.160> simulated<00:14:17.519> cross-star 00:14:18.050 --> 00:14:18.060 align:start position:0% transaction and the simulated cross-star 00:14:18.060 --> 00:14:19.370 align:start position:0% transaction and the simulated cross-star transaction 00:14:19.370 --> 00:14:19.380 align:start position:0% transaction 00:14:19.380 --> 00:14:20.629 align:start position:0% transaction when<00:14:19.680> they<00:14:19.800> do<00:14:19.920> this<00:14:19.980> they<00:14:20.160> will<00:14:20.279> collect<00:14:20.459> all 00:14:20.629 --> 00:14:20.639 align:start position:0% when they do this they will collect all 00:14:20.639 --> 00:14:22.790 align:start position:0% when they do this they will collect all the<00:14:20.820> cross<00:14:20.940> shot<00:14:21.120> messages<00:14:21.420> and<00:14:22.320> all<00:14:22.560> the 00:14:22.790 --> 00:14:22.800 align:start position:0% the cross shot messages and all the 00:14:22.800 --> 00:14:24.650 align:start position:0% the cross shot messages and all the access<00:14:22.920> storage<00:14:23.279> slots<00:14:23.700> in<00:14:24.060> phase<00:14:24.240> two<00:14:24.420> we<00:14:24.600> do 00:14:24.650 --> 00:14:24.660 align:start position:0% access storage slots in phase two we do 00:14:24.660 --> 00:14:25.790 align:start position:0% access storage slots in phase two we do the<00:14:24.779> exchange 00:14:25.790 --> 00:14:25.800 align:start position:0% the exchange 00:14:25.800 --> 00:14:28.129 align:start position:0% the exchange and<00:14:26.220> the<00:14:26.339> short<00:14:26.519> simulate<00:14:27.000> the<00:14:27.120> messages<00:14:27.300> and 00:14:28.129 --> 00:14:28.139 align:start position:0% and the short simulate the messages and 00:14:28.139 --> 00:14:29.329 align:start position:0% and the short simulate the messages and similarly<00:14:28.560> they<00:14:28.740> collect<00:14:28.980> all<00:14:29.100> the<00:14:29.220> search 00:14:29.329 --> 00:14:29.339 align:start position:0% similarly they collect all the search 00:14:29.339 --> 00:14:30.550 align:start position:0% similarly they collect all the search slots 00:14:30.550 --> 00:14:30.560 align:start position:0% slots 00:14:30.560 --> 00:14:32.990 align:start position:0% slots all<00:14:31.560> this<00:14:31.740> oh<00:14:32.040> sorry 00:14:32.990 --> 00:14:33.000 align:start position:0% all this oh sorry 00:14:33.000 --> 00:14:34.550 align:start position:0% all this oh sorry if<00:14:33.420> history<00:14:33.660> all<00:14:34.019> this<00:14:34.139> stuff<00:14:34.320> that<00:14:34.500> we 00:14:34.550 --> 00:14:34.560 align:start position:0% if history all this stuff that we 00:14:34.560 --> 00:14:36.590 align:start position:0% if history all this stuff that we collected<00:14:34.920> here<00:14:35.100> and<00:14:35.339> there<00:14:35.459> we<00:14:35.940> ship<00:14:36.180> it<00:14:36.360> to 00:14:36.590 --> 00:14:36.600 align:start position:0% collected here and there we ship it to 00:14:36.600 --> 00:14:38.530 align:start position:0% collected here and there we ship it to the<00:14:36.959> atomic<00:14:37.320> charge 00:14:38.530 --> 00:14:38.540 align:start position:0% the atomic charge 00:14:38.540 --> 00:14:41.449 align:start position:0% the atomic charge and<00:14:39.540> this<00:14:40.019> will<00:14:40.260> atomically<00:14:41.100> execute 00:14:41.449 --> 00:14:41.459 align:start position:0% and this will atomically execute 00:14:41.459 --> 00:14:42.290 align:start position:0% and this will atomically execute everything 00:14:42.290 --> 00:14:42.300 align:start position:0% everything 00:14:42.300 --> 00:14:45.050 align:start position:0% everything and<00:14:42.959> normally<00:14:43.260> you<00:14:43.440> should<00:14:43.620> have<00:14:43.940> all<00:14:44.940> the 00:14:45.050 --> 00:14:45.060 align:start position:0% and normally you should have all the 00:14:45.060 --> 00:14:46.610 align:start position:0% and normally you should have all the stated<00:14:45.300> needs<00:14:45.660> and<00:14:45.720> if<00:14:45.899> it<00:14:46.019> does<00:14:46.139> then<00:14:46.320> it<00:14:46.440> will 00:14:46.610 --> 00:14:46.620 align:start position:0% stated needs and if it does then it will 00:14:46.620 --> 00:14:48.470 align:start position:0% stated needs and if it does then it will just<00:14:46.740> basically<00:14:47.639> fail<00:14:47.820> to<00:14:48.060> execute 00:14:48.470 --> 00:14:48.480 align:start position:0% just basically fail to execute 00:14:48.480 --> 00:14:50.090 align:start position:0% just basically fail to execute transactions 00:14:50.090 --> 00:14:50.100 align:start position:0% transactions 00:14:50.100 --> 00:14:52.970 align:start position:0% transactions so<00:14:50.639> the<00:14:51.060> big<00:14:51.180> problem<00:14:51.360> with<00:14:51.600> this<00:14:51.779> scheme 00:14:52.970 --> 00:14:52.980 align:start position:0% so the big problem with this scheme 00:14:52.980 --> 00:14:54.650 align:start position:0% so the big problem with this scheme is<00:14:53.399> that<00:14:53.579> the<00:14:53.760> simulation<00:14:54.060> restrict<00:14:54.480> the 00:14:54.650 --> 00:14:54.660 align:start position:0% is that the simulation restrict the 00:14:54.660 --> 00:14:56.090 align:start position:0% is that the simulation restrict the expressivity 00:14:56.090 --> 00:14:56.100 align:start position:0% expressivity 00:14:56.100 --> 00:14:59.449 align:start position:0% expressivity right<00:14:56.519> so<00:14:57.300> we<00:14:57.420> can<00:14:57.600> only<00:14:57.839> safely<00:14:58.260> Express<00:14:58.500> a 00:14:59.449 --> 00:14:59.459 align:start position:0% right so we can only safely Express a 00:14:59.459 --> 00:15:01.069 align:start position:0% right so we can only safely Express a transaction<00:14:59.880> where<00:15:00.180> the<00:15:00.420> simulation<00:15:00.779> will<00:15:00.959> be 00:15:01.069 --> 00:15:01.079 align:start position:0% transaction where the simulation will be 00:15:01.079 --> 00:15:03.650 align:start position:0% transaction where the simulation will be deterministic<00:15:01.740> in<00:15:01.920> some<00:15:02.040> ways 00:15:03.650 --> 00:15:03.660 align:start position:0% deterministic in some ways 00:15:03.660 --> 00:15:06.050 align:start position:0% deterministic in some ways because<00:15:03.899> otherwise<00:15:04.440> you<00:15:04.800> you<00:15:05.040> know 00:15:06.050 --> 00:15:06.060 align:start position:0% because otherwise you you know 00:15:06.060 --> 00:15:07.790 align:start position:0% because otherwise you you know it<00:15:06.420> might<00:15:06.839> change<00:15:07.019> and<00:15:07.260> you<00:15:07.440> might<00:15:07.560> not<00:15:07.680> be 00:15:07.790 --> 00:15:07.800 align:start position:0% it might change and you might not be 00:15:07.800 --> 00:15:09.530 align:start position:0% it might change and you might not be able<00:15:07.920> to<00:15:08.040> execute<00:15:08.399> things<00:15:08.579> so<00:15:09.120> you<00:15:09.300> might 00:15:09.530 --> 00:15:09.540 align:start position:0% able to execute things so you might 00:15:09.540 --> 00:15:11.629 align:start position:0% able to execute things so you might sometimes<00:15:09.899> take<00:15:10.139> the<00:15:10.320> risk 00:15:11.629 --> 00:15:11.639 align:start position:0% sometimes take the risk 00:15:11.639 --> 00:15:13.069 align:start position:0% sometimes take the risk um that<00:15:11.820> transaction<00:15:12.180> won't<00:15:12.420> work<00:15:12.600> say<00:15:12.839> well 00:15:13.069 --> 00:15:13.079 align:start position:0% um that transaction won't work say well 00:15:13.079 --> 00:15:15.470 align:start position:0% um that transaction won't work say well I'm<00:15:13.680> gonna<00:15:13.860> try<00:15:14.279> if<00:15:14.940> the<00:15:15.060> sales<00:15:15.240> doesn't 00:15:15.470 --> 00:15:15.480 align:start position:0% I'm gonna try if the sales doesn't 00:15:15.480 --> 00:15:17.389 align:start position:0% I'm gonna try if the sales doesn't change<00:15:15.720> it's<00:15:15.839> gonna<00:15:16.019> succeed<00:15:16.560> but<00:15:16.980> if<00:15:17.220> the 00:15:17.389 --> 00:15:17.399 align:start position:0% change it's gonna succeed but if the 00:15:17.399 --> 00:15:19.430 align:start position:0% change it's gonna succeed but if the state<00:15:17.579> changes<00:15:18.060> it's<00:15:18.240> not<00:15:18.420> going<00:15:18.540> to<00:15:18.660> succeed 00:15:19.430 --> 00:15:19.440 align:start position:0% state changes it's not going to succeed 00:15:19.440 --> 00:15:21.290 align:start position:0% state changes it's not going to succeed uh<00:15:19.920> we'll<00:15:20.100> see<00:15:20.279> that<00:15:20.459> sometimes<00:15:20.940> that<00:15:21.120> doesn't 00:15:21.290 --> 00:15:21.300 align:start position:0% uh we'll see that sometimes that doesn't 00:15:21.300 --> 00:15:23.329 align:start position:0% uh we'll see that sometimes that doesn't work<00:15:21.600> uh<00:15:22.260> by<00:15:22.380> the<00:15:22.500> way<00:15:22.560> this<00:15:22.800> is<00:15:22.860> exactly<00:15:23.220> the 00:15:23.329 --> 00:15:23.339 align:start position:0% work uh by the way this is exactly the 00:15:23.339 --> 00:15:24.889 align:start position:0% work uh by the way this is exactly the same<00:15:23.459> problem<00:15:23.639> as<00:15:23.880> building<00:15:24.240> strict<00:15:24.720> access 00:15:24.889 --> 00:15:24.899 align:start position:0% same problem as building strict access 00:15:24.899 --> 00:15:27.530 align:start position:0% same problem as building strict access list<00:15:25.199> or<00:15:25.560> you<00:15:25.800> take<00:15:25.980> so<00:15:26.220> for<00:15:26.459> slots 00:15:27.530 --> 00:15:27.540 align:start position:0% list or you take so for slots 00:15:27.540 --> 00:15:29.329 align:start position:0% list or you take so for slots same<00:15:27.959> thing<00:15:28.139> you<00:15:28.320> need<00:15:28.440> to<00:15:28.560> collect<00:15:28.860> all<00:15:29.100> the 00:15:29.329 --> 00:15:29.339 align:start position:0% same thing you need to collect all the 00:15:29.339 --> 00:15:30.590 align:start position:0% same thing you need to collect all the the<00:15:29.579> storage<00:15:29.820> slots<00:15:30.180> that<00:15:30.300> have<00:15:30.480> been 00:15:30.590 --> 00:15:30.600 align:start position:0% the storage slots that have been 00:15:30.600 --> 00:15:33.470 align:start position:0% the storage slots that have been accessed<00:15:31.139> so<00:15:31.440> this<00:15:32.100> problem<00:15:32.279> is<00:15:32.579> uh<00:15:32.940> is<00:15:33.300> pretty 00:15:33.470 --> 00:15:33.480 align:start position:0% accessed so this problem is uh is pretty 00:15:33.480 --> 00:15:36.829 align:start position:0% accessed so this problem is uh is pretty similar<00:15:33.839> so<00:15:34.620> the<00:15:35.220> the<00:15:35.880> problem<00:15:36.120> you<00:15:36.660> know<00:15:36.720> what 00:15:36.829 --> 00:15:36.839 align:start position:0% similar so the the problem you know what 00:15:36.839 --> 00:15:39.530 align:start position:0% similar so the the problem you know what gets<00:15:37.260> worse<00:15:37.560> is<00:15:38.220> that<00:15:38.399> crucial<00:15:38.699> messages<00:15:39.060> may 00:15:39.530 --> 00:15:39.540 align:start position:0% gets worse is that crucial messages may 00:15:39.540 --> 00:15:41.870 align:start position:0% gets worse is that crucial messages may depend<00:15:39.779> on<00:15:40.079> uncertain<00:15:40.500> States 00:15:41.870 --> 00:15:41.880 align:start position:0% depend on uncertain States 00:15:41.880 --> 00:15:44.030 align:start position:0% depend on uncertain States and<00:15:42.360> we<00:15:42.540> derive<00:15:43.320> all<00:15:43.440> the<00:15:43.560> messages<00:15:43.680> during 00:15:44.030 --> 00:15:44.040 align:start position:0% and we derive all the messages during 00:15:44.040 --> 00:15:45.170 align:start position:0% and we derive all the messages during simulation 00:15:45.170 --> 00:15:45.180 align:start position:0% simulation 00:15:45.180 --> 00:15:46.370 align:start position:0% simulation and<00:15:45.600> that's<00:15:45.720> why<00:15:45.899> we<00:15:46.019> want<00:15:46.139> to<00:15:46.260> be 00:15:46.370 --> 00:15:46.380 align:start position:0% and that's why we want to be 00:15:46.380 --> 00:15:49.069 align:start position:0% and that's why we want to be deterministic 00:15:49.069 --> 00:15:49.079 align:start position:0% 00:15:49.079 --> 00:15:52.250 align:start position:0% um<00:15:49.139> we<00:15:49.680> can<00:15:50.040> also<00:15:50.459> want<00:15:51.420> an<00:15:51.660> answer<00:15:51.779> from<00:15:52.079> a 00:15:52.250 --> 00:15:52.260 align:start position:0% um we can also want an answer from a 00:15:52.260 --> 00:15:55.310 align:start position:0% um we can also want an answer from a chart<00:15:52.380> and<00:15:53.279> so<00:15:53.459> we<00:15:53.639> absolutely<00:15:54.000> need<00:15:54.300> to<00:15:54.720> have 00:15:55.310 --> 00:15:55.320 align:start position:0% chart and so we absolutely need to have 00:15:55.320 --> 00:15:56.930 align:start position:0% chart and so we absolutely need to have a<00:15:55.500> hint<00:15:55.620> for<00:15:55.860> the<00:15:56.040> answer<00:15:56.100> so<00:15:56.760> let<00:15:56.820> me 00:15:56.930 --> 00:15:56.940 align:start position:0% a hint for the answer so let me 00:15:56.940 --> 00:15:58.129 align:start position:0% a hint for the answer so let me illustrate<00:15:57.240> because<00:15:57.420> this<00:15:57.540> is<00:15:57.660> very<00:15:57.720> abstract 00:15:58.129 --> 00:15:58.139 align:start position:0% illustrate because this is very abstract 00:15:58.139 --> 00:16:00.889 align:start position:0% illustrate because this is very abstract so<00:15:58.920> what<00:15:59.040> I<00:15:59.220> was<00:15:59.279> saying<00:15:59.519> was<00:15:59.760> that<00:16:00.060> this 00:16:00.889 --> 00:16:00.899 align:start position:0% so what I was saying was that this 00:16:00.899 --> 00:16:03.889 align:start position:0% so what I was saying was that this parameter<00:16:01.440> here<00:16:01.620> x<00:16:02.180> depends<00:16:03.180> on<00:16:03.660> the<00:16:03.779> result 00:16:03.889 --> 00:16:03.899 align:start position:0% parameter here x depends on the result 00:16:03.899 --> 00:16:06.230 align:start position:0% parameter here x depends on the result of<00:16:04.139> computation<00:16:04.560> so<00:16:05.279> this<00:16:05.519> we<00:16:05.760> need<00:16:05.880> this<00:16:06.060> to 00:16:06.230 --> 00:16:06.240 align:start position:0% of computation so this we need this to 00:16:06.240 --> 00:16:08.689 align:start position:0% of computation so this we need this to be<00:16:06.360> always<00:16:06.540> the<00:16:06.779> same<00:16:06.959> otherwise<00:16:07.440> we<00:16:07.680> just 00:16:08.689 --> 00:16:08.699 align:start position:0% be always the same otherwise we just 00:16:08.699 --> 00:16:11.030 align:start position:0% be always the same otherwise we just asking<00:16:09.660> the<00:16:10.019> visual<00:16:10.380> to<00:16:10.620> compute<00:16:10.920> something 00:16:11.030 --> 00:16:11.040 align:start position:0% asking the visual to compute something 00:16:11.040 --> 00:16:12.710 align:start position:0% asking the visual to compute something that<00:16:11.279> might<00:16:11.459> not<00:16:11.579> be<00:16:11.760> what<00:16:11.940> we<00:16:12.060> want<00:16:12.180> so<00:16:12.540> we 00:16:12.710 --> 00:16:12.720 align:start position:0% that might not be what we want so we 00:16:12.720 --> 00:16:14.710 align:start position:0% that might not be what we want so we absolutely<00:16:13.139> need<00:16:13.320> X<00:16:13.560> to<00:16:13.800> be<00:16:13.980> uh<00:16:14.220> to<00:16:14.399> be<00:16:14.519> known 00:16:14.710 --> 00:16:14.720 align:start position:0% absolutely need X to be uh to be known 00:16:14.720 --> 00:16:17.930 align:start position:0% absolutely need X to be uh to be known and<00:16:15.720> you<00:16:16.380> know<00:16:16.560> that<00:16:16.800> the<00:16:17.100> message<00:16:17.279> sends<00:16:17.880> an 00:16:17.930 --> 00:16:17.940 align:start position:0% and you know that the message sends an 00:16:17.940 --> 00:16:19.189 align:start position:0% and you know that the message sends an answer<00:16:18.180> and<00:16:18.540> we're<00:16:18.660> going<00:16:18.839> to<00:16:18.899> send<00:16:19.019> this 00:16:19.189 --> 00:16:19.199 align:start position:0% answer and we're going to send this 00:16:19.199 --> 00:16:20.990 align:start position:0% answer and we're going to send this answer<00:16:19.320> actually<00:16:19.620> directly<00:16:20.040> to<00:16:20.220> C<00:16:20.459> so<00:16:20.699> we 00:16:20.990 --> 00:16:21.000 align:start position:0% answer actually directly to C so we 00:16:21.000 --> 00:16:22.009 align:start position:0% answer actually directly to C so we absolutely<00:16:21.300> need<00:16:21.480> to<00:16:21.600> know<00:16:21.720> the<00:16:21.899> answer 00:16:22.009 --> 00:16:22.019 align:start position:0% absolutely need to know the answer 00:16:22.019 --> 00:16:24.350 align:start position:0% absolutely need to know the answer already<00:16:22.380> also 00:16:24.350 --> 00:16:24.360 align:start position:0% already also 00:16:24.360 --> 00:16:25.850 align:start position:0% already also um<00:16:24.420> I've<00:16:24.660> actually<00:16:24.839> Illustrated<00:16:25.560> these 00:16:25.850 --> 00:16:25.860 align:start position:0% um I've actually Illustrated these 00:16:25.860 --> 00:16:27.829 align:start position:0% um I've actually Illustrated these constraints<00:16:26.639> so 00:16:27.829 --> 00:16:27.839 align:start position:0% constraints so 00:16:27.839 --> 00:16:30.650 align:start position:0% constraints so here<00:16:28.320> we<00:16:28.440> need<00:16:28.560> the<00:16:28.680> computation<00:16:29.060> to<00:16:30.060> be 00:16:30.650 --> 00:16:30.660 align:start position:0% here we need the computation to be 00:16:30.660 --> 00:16:32.150 align:start position:0% here we need the computation to be deterministic<00:16:31.260> in<00:16:31.380> the<00:16:31.500> storage<00:16:31.620> class<00:16:31.920> that 00:16:32.150 --> 00:16:32.160 align:start position:0% deterministic in the storage class that 00:16:32.160 --> 00:16:33.470 align:start position:0% deterministic in the storage class that accesses 00:16:33.470 --> 00:16:33.480 align:start position:0% accesses 00:16:33.480 --> 00:16:35.030 align:start position:0% accesses here<00:16:33.779> we<00:16:33.959> actually<00:16:34.079> need<00:16:34.380> the<00:16:34.500> computation<00:16:34.860> to 00:16:35.030 --> 00:16:35.040 align:start position:0% here we actually need the computation to 00:16:35.040 --> 00:16:36.470 align:start position:0% here we actually need the computation to be<00:16:35.100> deterministic<00:16:35.639> so<00:16:35.760> to<00:16:35.940> always<00:16:36.000> return<00:16:36.180> the 00:16:36.470 --> 00:16:36.480 align:start position:0% be deterministic so to always return the 00:16:36.480 --> 00:16:37.670 align:start position:0% be deterministic so to always return the same<00:16:36.600> result 00:16:37.670 --> 00:16:37.680 align:start position:0% same result 00:16:37.680 --> 00:16:41.090 align:start position:0% same result here<00:16:38.220> if<00:16:38.639> we<00:16:38.820> use<00:16:38.940> y<00:16:39.120> just<00:16:39.420> in<00:16:39.600> a<00:16:39.720> computation 00:16:41.090 --> 00:16:41.100 align:start position:0% here if we use y just in a computation 00:16:41.100 --> 00:16:42.550 align:start position:0% here if we use y just in a computation we<00:16:41.459> need<00:16:41.519> to<00:16:41.639> hence<00:16:41.820> the<00:16:42.120> result 00:16:42.550 --> 00:16:42.560 align:start position:0% we need to hence the result 00:16:42.560 --> 00:16:44.689 align:start position:0% we need to hence the result approximately<00:16:43.560> just<00:16:44.100> to<00:16:44.220> get<00:16:44.339> the<00:16:44.459> correct 00:16:44.689 --> 00:16:44.699 align:start position:0% approximately just to get the correct 00:16:44.699 --> 00:16:46.550 align:start position:0% approximately just to get the correct shot<00:16:45.060> but<00:16:45.480> if<00:16:45.660> we<00:16:45.779> send<00:16:45.899> it<00:16:46.019> to<00:16:46.139> another<00:16:46.259> chart 00:16:46.550 --> 00:16:46.560 align:start position:0% shot but if we send it to another chart 00:16:46.560 --> 00:16:49.129 align:start position:0% shot but if we send it to another chart then<00:16:46.800> we<00:16:47.639> need<00:16:47.759> to<00:16:47.880> know<00:16:48.000> exactly<00:16:48.480> what<00:16:48.660> Y<00:16:48.899> is 00:16:49.129 --> 00:16:49.139 align:start position:0% then we need to know exactly what Y is 00:16:49.139 --> 00:16:51.650 align:start position:0% then we need to know exactly what Y is like<00:16:49.380> no<00:16:49.680> no<00:16:49.980> guessing<00:16:50.459> otherwise<00:16:51.180> we're<00:16:51.420> just 00:16:51.650 --> 00:16:51.660 align:start position:0% like no no guessing otherwise we're just 00:16:51.660 --> 00:16:53.689 align:start position:0% like no no guessing otherwise we're just asking<00:16:52.259> C<00:16:52.440> to<00:16:52.680> do<00:16:52.800> some<00:16:53.279> and<00:16:53.519> we 00:16:53.689 --> 00:16:53.699 align:start position:0% asking C to do some and we 00:16:53.699 --> 00:16:56.150 align:start position:0% asking C to do some and we don't<00:16:53.820> want<00:16:54.000> that 00:16:56.150 --> 00:16:56.160 align:start position:0% don't want that 00:16:56.160 --> 00:16:58.730 align:start position:0% don't want that um<00:16:56.220> so<00:16:56.639> open<00:16:57.000> questions 00:16:58.730 --> 00:16:58.740 align:start position:0% um so open questions 00:16:58.740 --> 00:17:00.889 align:start position:0% um so open questions is<00:16:59.339> this<00:16:59.459> reasonable 00:17:00.889 --> 00:17:00.899 align:start position:0% is this reasonable 00:17:00.899 --> 00:17:03.650 align:start position:0% is this reasonable is<00:17:01.380> this<00:17:01.500> a<00:17:01.680> good<00:17:01.920> idea<00:17:02.300> are<00:17:03.300> these 00:17:03.650 --> 00:17:03.660 align:start position:0% is this a good idea are these 00:17:03.660 --> 00:17:05.449 align:start position:0% is this a good idea are these restriction 00:17:05.449 --> 00:17:05.459 align:start position:0% restriction 00:17:05.459 --> 00:17:07.429 align:start position:0% restriction um<00:17:05.520> feasible<00:17:06.240> do<00:17:06.480> they<00:17:06.600> give<00:17:06.720> us<00:17:06.839> a<00:17:07.020> powerful 00:17:07.429 --> 00:17:07.439 align:start position:0% um feasible do they give us a powerful 00:17:07.439 --> 00:17:09.530 align:start position:0% um feasible do they give us a powerful model<00:17:07.679> that<00:17:07.980> is<00:17:08.100> useful<00:17:08.339> in<00:17:08.459> practice 00:17:09.530 --> 00:17:09.540 align:start position:0% model that is useful in practice 00:17:09.540 --> 00:17:11.270 align:start position:0% model that is useful in practice another<00:17:09.900> question<00:17:10.319> is<00:17:10.500> can<00:17:10.740> we<00:17:10.919> aesthetically 00:17:11.270 --> 00:17:11.280 align:start position:0% another question is can we aesthetically 00:17:11.280 --> 00:17:13.490 align:start position:0% another question is can we aesthetically guard<00:17:11.520> against<00:17:11.880> some<00:17:12.360> some<00:17:12.720> cases<00:17:13.260> of<00:17:13.380> the 00:17:13.490 --> 00:17:13.500 align:start position:0% guard against some some cases of the 00:17:13.500 --> 00:17:14.929 align:start position:0% guard against some some cases of the non-deterministic<00:17:14.220> execution<00:17:14.520> that<00:17:14.760> we<00:17:14.819> want 00:17:14.929 --> 00:17:14.939 align:start position:0% non-deterministic execution that we want 00:17:14.939 --> 00:17:17.210 align:start position:0% non-deterministic execution that we want to<00:17:15.059> avoid<00:17:15.360> or<00:17:16.020> do<00:17:16.199> we<00:17:16.319> just<00:17:16.439> say<00:17:16.620> well<00:17:16.860> it's<00:17:17.100> a 00:17:17.210 --> 00:17:17.220 align:start position:0% to avoid or do we just say well it's a 00:17:17.220 --> 00:17:18.590 align:start position:0% to avoid or do we just say well it's a user<00:17:17.459> responsibility<00:17:17.939> and<00:17:18.179> maybe<00:17:18.360> some 00:17:18.590 --> 00:17:18.600 align:start position:0% user responsibility and maybe some 00:17:18.600 --> 00:17:20.150 align:start position:0% user responsibility and maybe some people<00:17:18.720> will<00:17:18.959> build<00:17:19.199> some<00:17:19.380> tools<00:17:19.740> to<00:17:19.860> detect 00:17:20.150 --> 00:17:20.160 align:start position:0% people will build some tools to detect 00:17:20.160 --> 00:17:22.789 align:start position:0% people will build some tools to detect some<00:17:20.400> of<00:17:20.520> these<00:17:20.699> cases<00:17:21.480> uh<00:17:22.199> this<00:17:22.439> is<00:17:22.500> for<00:17:22.679> sure 00:17:22.789 --> 00:17:22.799 align:start position:0% some of these cases uh this is for sure 00:17:22.799 --> 00:17:24.590 align:start position:0% some of these cases uh this is for sure a<00:17:22.980> foot<00:17:23.160> gun<00:17:23.339> right<00:17:23.579> like<00:17:23.760> if<00:17:24.240> you're<00:17:24.419> going<00:17:24.540> to 00:17:24.590 --> 00:17:24.600 align:start position:0% a foot gun right like if you're going to 00:17:24.600 --> 00:17:27.409 align:start position:0% a foot gun right like if you're going to make<00:17:24.720> a<00:17:24.980> Crosshair<00:17:25.980> transaction<00:17:26.400> and 00:17:27.409 --> 00:17:27.419 align:start position:0% make a Crosshair transaction and 00:17:27.419 --> 00:17:29.330 align:start position:0% make a Crosshair transaction and you<00:17:28.020> don't<00:17:28.140> expect<00:17:28.319> it<00:17:28.620> you<00:17:28.799> expect<00:17:28.980> it<00:17:29.160> to<00:17:29.280> be 00:17:29.330 --> 00:17:29.340 align:start position:0% you don't expect it you expect it to be 00:17:29.340 --> 00:17:30.890 align:start position:0% you don't expect it you expect it to be deterministic<00:17:29.940> but<00:17:30.120> isn't<00:17:30.540> there's 00:17:30.890 --> 00:17:30.900 align:start position:0% deterministic but isn't there's 00:17:30.900 --> 00:17:31.970 align:start position:0% deterministic but isn't there's definitely<00:17:31.380> there<00:17:31.620> are<00:17:31.740> a<00:17:31.799> lot<00:17:31.799> of 00:17:31.970 --> 00:17:31.980 align:start position:0% definitely there are a lot of 00:17:31.980 --> 00:17:33.650 align:start position:0% definitely there are a lot of possibility<00:17:32.340> to<00:17:32.520> make<00:17:32.640> bugs 00:17:33.650 --> 00:17:33.660 align:start position:0% possibility to make bugs 00:17:33.660 --> 00:17:36.049 align:start position:0% possibility to make bugs but<00:17:34.140> is<00:17:34.260> it<00:17:34.440> worth<00:17:34.620> the<00:17:34.860> cost 00:17:36.049 --> 00:17:36.059 align:start position:0% but is it worth the cost 00:17:36.059 --> 00:17:38.870 align:start position:0% but is it worth the cost our<00:17:36.539> question<00:17:36.840> is<00:17:37.140> what<00:17:37.440> is<00:17:37.620> the<00:17:37.799> correct 00:17:38.870 --> 00:17:38.880 align:start position:0% our question is what is the correct 00:17:38.880 --> 00:17:41.029 align:start position:0% our question is what is the correct abstraction<00:17:39.480> level<00:17:39.720> for<00:17:40.080> all<00:17:40.260> this<00:17:40.500> if<00:17:40.860> we 00:17:41.029 --> 00:17:41.039 align:start position:0% abstraction level for all this if we 00:17:41.039 --> 00:17:43.370 align:start position:0% abstraction level for all this if we don't<00:17:41.160> enshrine<00:17:42.000> static<00:17:42.600> checks<00:17:42.960> we<00:17:43.260> can 00:17:43.370 --> 00:17:43.380 align:start position:0% don't enshrine static checks we can 00:17:43.380 --> 00:17:45.409 align:start position:0% don't enshrine static checks we can simply<00:17:43.620> add<00:17:43.860> like<00:17:44.039> a<00:17:44.280> cross<00:17:44.520> short<00:17:44.820> call<00:17:45.059> up 00:17:45.409 --> 00:17:45.419 align:start position:0% simply add like a cross short call up 00:17:45.419 --> 00:17:48.409 align:start position:0% simply add like a cross short call up code<00:17:45.600> to<00:17:45.780> the<00:17:45.900> evm<00:17:46.320> and<00:17:47.100> then<00:17:47.280> just 00:17:48.409 --> 00:17:48.419 align:start position:0% code to the evm and then just 00:17:48.419 --> 00:17:49.970 align:start position:0% code to the evm and then just on<00:17:48.840> the<00:17:48.960> back<00:17:49.020> end<00:17:49.200> it<00:17:49.440> will<00:17:49.559> do<00:17:49.679> what<00:17:49.860> I 00:17:49.970 --> 00:17:49.980 align:start position:0% on the back end it will do what I 00:17:49.980 --> 00:17:52.430 align:start position:0% on the back end it will do what I explained<00:17:50.820> but<00:17:51.419> from<00:17:51.840> the<00:17:51.960> point<00:17:52.080> of<00:17:52.200> view<00:17:52.260> of 00:17:52.430 --> 00:17:52.440 align:start position:0% explained but from the point of view of 00:17:52.440 --> 00:17:54.130 align:start position:0% explained but from the point of view of DVM<00:17:52.740> this<00:17:52.919> is<00:17:53.039> the<00:17:53.160> new<00:17:53.280> up<00:17:53.400> code 00:17:54.130 --> 00:17:54.140 align:start position:0% DVM this is the new up code 00:17:54.140 --> 00:17:58.130 align:start position:0% DVM this is the new up code this<00:17:55.140> has<00:17:55.260> been<00:17:55.440> my<00:17:56.220> presentation 00:17:58.130 --> 00:17:58.140 align:start position:0% this has been my presentation 00:17:58.140 --> 00:18:00.169 align:start position:0% this has been my presentation we<00:17:58.740> have<00:17:58.919> five<00:17:59.100> minutes<00:17:59.280> for<00:17:59.580> questions<00:17:59.820> I'm 00:18:00.169 --> 00:18:00.179 align:start position:0% we have five minutes for questions I'm 00:18:00.179 --> 00:18:02.450 align:start position:0% we have five minutes for questions I'm sure<00:18:00.360> some<00:18:00.539> of<00:18:00.660> you<00:18:00.780> have<00:18:00.900> burning<00:18:01.260> questions 00:18:02.450 --> 00:18:02.460 align:start position:0% sure some of you have burning questions 00:18:02.460 --> 00:18:03.470 align:start position:0% sure some of you have burning questions you<00:18:02.760> should<00:18:02.880> have<00:18:03.000> a<00:18:03.179> lot<00:18:03.240> of<00:18:03.360> questions 00:18:03.470 --> 00:18:03.480 align:start position:0% you should have a lot of questions 00:18:03.480 --> 00:18:06.350 align:start position:0% you should have a lot of questions because<00:18:03.720> this<00:18:04.020> is<00:18:04.140> very<00:18:04.320> questionable 00:18:06.350 --> 00:18:06.360 align:start position:0% because this is very questionable 00:18:06.360 --> 00:18:07.610 align:start position:0% because this is very questionable um<00:18:06.419> yeah<00:18:06.600> do<00:18:06.780> you<00:18:06.900> think<00:18:06.960> sharding<00:18:07.380> is<00:18:07.500> maybe 00:18:07.610 --> 00:18:07.620 align:start position:0% um yeah do you think sharding is maybe 00:18:07.620 --> 00:18:09.650 align:start position:0% um yeah do you think sharding is maybe just<00:18:07.919> fundamentally<00:18:08.580> kind<00:18:09.059> of<00:18:09.179> impossible 00:18:09.650 --> 00:18:09.660 align:start position:0% just fundamentally kind of impossible 00:18:09.660 --> 00:18:12.169 align:start position:0% just fundamentally kind of impossible and<00:18:10.080> like<00:18:10.799> kind<00:18:11.160> of<00:18:11.280> like<00:18:11.460> when<00:18:11.940> you're<00:18:12.059> trying 00:18:12.169 --> 00:18:12.179 align:start position:0% and like kind of like when you're trying 00:18:12.179 --> 00:18:13.669 align:start position:0% and like kind of like when you're trying to<00:18:12.299> deal<00:18:12.419> it's<00:18:12.660> like<00:18:12.840> you<00:18:13.260> have<00:18:13.440> all<00:18:13.500> these 00:18:13.669 --> 00:18:13.679 align:start position:0% to deal it's like you have all these 00:18:13.679 --> 00:18:14.930 align:start position:0% to deal it's like you have all these different<00:18:13.799> systems 00:18:14.930 --> 00:18:14.940 align:start position:0% different systems 00:18:14.940 --> 00:18:16.250 align:start position:0% different systems it's<00:18:15.179> almost<00:18:15.419> like<00:18:15.600> they<00:18:15.720> shouldn't<00:18:16.020> be<00:18:16.140> able 00:18:16.250 --> 00:18:16.260 align:start position:0% it's almost like they shouldn't be able 00:18:16.260 --> 00:18:17.810 align:start position:0% it's almost like they shouldn't be able to<00:18:16.440> interact<00:18:16.740> in<00:18:16.919> this<00:18:17.100> way 00:18:17.810 --> 00:18:17.820 align:start position:0% to interact in this way 00:18:17.820 --> 00:18:19.730 align:start position:0% to interact in this way it's<00:18:17.940> a<00:18:18.120> really<00:18:18.299> dumb<00:18:18.539> question 00:18:19.730 --> 00:18:19.740 align:start position:0% it's a really dumb question 00:18:19.740 --> 00:18:22.310 align:start position:0% it's a really dumb question um<00:18:20.280> I<00:18:20.760> mean<00:18:20.940> in<00:18:21.480> a<00:18:21.660> certain<00:18:21.780> way<00:18:22.020> you're<00:18:22.140> right 00:18:22.310 --> 00:18:22.320 align:start position:0% um I mean in a certain way you're right 00:18:22.320 --> 00:18:23.630 align:start position:0% um I mean in a certain way you're right like<00:18:22.559> we're 00:18:23.630 --> 00:18:23.640 align:start position:0% like we're 00:18:23.640 --> 00:18:25.789 align:start position:0% like we're yeah<00:18:24.120> do<00:18:24.419> ideas<00:18:24.720> like<00:18:25.020> you<00:18:25.140> can<00:18:25.260> paralyze<00:18:25.679> what 00:18:25.789 --> 00:18:25.799 align:start position:0% yeah do ideas like you can paralyze what 00:18:25.799 --> 00:18:27.110 align:start position:0% yeah do ideas like you can paralyze what you<00:18:25.919> can<00:18:26.100> but<00:18:26.280> then<00:18:26.460> sometimes<00:18:26.760> you<00:18:27.000> don't 00:18:27.110 --> 00:18:27.120 align:start position:0% you can but then sometimes you don't 00:18:27.120 --> 00:18:28.909 align:start position:0% you can but then sometimes you don't want<00:18:27.360> to<00:18:27.480> paralyze<00:18:28.080> and<00:18:28.500> you're<00:18:28.620> just<00:18:28.799> trying 00:18:28.909 --> 00:18:28.919 align:start position:0% want to paralyze and you're just trying 00:18:28.919 --> 00:18:31.190 align:start position:0% want to paralyze and you're just trying to<00:18:29.100> build<00:18:29.220> this<00:18:29.400> abrid<00:18:29.940> like<00:18:30.240> a<00:18:30.780> synchronous 00:18:31.190 --> 00:18:31.200 align:start position:0% to build this abrid like a synchronous 00:18:31.200 --> 00:18:32.450 align:start position:0% to build this abrid like a synchronous synchronous<00:18:31.620> system 00:18:32.450 --> 00:18:32.460 align:start position:0% synchronous system 00:18:32.460 --> 00:18:35.930 align:start position:0% synchronous system uh<00:18:33.419> so<00:18:33.900> yes<00:18:34.080> I<00:18:34.320> know 00:18:35.930 --> 00:18:35.940 align:start position:0% uh so yes I know 00:18:35.940 --> 00:18:37.970 align:start position:0% uh so yes I know someone<00:18:36.360> else<00:18:36.600> someone<00:18:36.840> comes<00:18:37.500> from<00:18:37.860> some 00:18:37.970 --> 00:18:37.980 align:start position:0% someone else someone comes from some 00:18:37.980 --> 00:18:39.590 align:start position:0% someone else someone comes from some wacky<00:18:38.340> idea<00:18:38.520> there's<00:18:38.760> not<00:18:38.940> a<00:18:39.059> dumb<00:18:39.419> question 00:18:39.590 --> 00:18:39.600 align:start position:0% wacky idea there's not a dumb question 00:18:39.600 --> 00:18:43.250 align:start position:0% wacky idea there's not a dumb question yeah<00:18:40.500> in<00:18:40.980> your<00:18:41.100> model<00:18:41.400> the 00:18:43.250 --> 00:18:43.260 align:start position:0% yeah in your model the 00:18:43.260 --> 00:18:46.010 align:start position:0% yeah in your model the regarding<00:18:43.980> the<00:18:44.160> new<00:18:44.460> OP<00:18:44.700> code<00:18:44.940> that<00:18:45.600> is<00:18:45.720> aware 00:18:46.010 --> 00:18:46.020 align:start position:0% regarding the new OP code that is aware 00:18:46.020 --> 00:18:48.650 align:start position:0% regarding the new OP code that is aware of<00:18:46.200> sending<00:18:46.740> message<00:18:46.980> cross<00:18:47.340> charging<00:18:47.880> does 00:18:48.650 --> 00:18:48.660 align:start position:0% of sending message cross charging does 00:18:48.660 --> 00:18:50.930 align:start position:0% of sending message cross charging does that<00:18:48.840> mean<00:18:49.140> like<00:18:49.500> smart<00:18:49.919> contracts<00:18:50.520> need<00:18:50.760> to 00:18:50.930 --> 00:18:50.940 align:start position:0% that mean like smart contracts need to 00:18:50.940 --> 00:18:53.690 align:start position:0% that mean like smart contracts need to be<00:18:51.120> aware<00:18:51.539> of<00:18:51.720> calling<00:18:52.559> another<00:18:53.280> smart 00:18:53.690 --> 00:18:53.700 align:start position:0% be aware of calling another smart 00:18:53.700 --> 00:18:56.029 align:start position:0% be aware of calling another smart contract<00:18:54.179> that<00:18:54.419> is<00:18:54.539> in<00:18:54.780> another<00:18:54.960> chart<00:18:55.320> yeah 00:18:56.029 --> 00:18:56.039 align:start position:0% contract that is in another chart yeah 00:18:56.039 --> 00:18:58.190 align:start position:0% contract that is in another chart yeah how<00:18:56.340> do<00:18:56.460> we<00:18:56.460> envision<00:18:56.760> those<00:18:57.059> things<00:18:57.299> and<00:18:57.900> also 00:18:58.190 --> 00:18:58.200 align:start position:0% how do we envision those things and also 00:18:58.200 --> 00:19:00.770 align:start position:0% how do we envision those things and also in<00:18:58.679> charting<00:18:59.280> without<00:18:59.820> the<00:19:00.179> New<00:19:00.240> Hope<00:19:00.419> code 00:19:00.770 --> 00:19:00.780 align:start position:0% in charting without the New Hope code 00:19:00.780 --> 00:19:03.950 align:start position:0% in charting without the New Hope code our<00:19:01.559> smart<00:19:01.919> contracts<00:19:02.460> being<00:19:02.760> aware<00:19:03.120> of 00:19:03.950 --> 00:19:03.960 align:start position:0% our smart contracts being aware of 00:19:03.960 --> 00:19:06.110 align:start position:0% our smart contracts being aware of calling<00:19:04.919> something<00:19:05.340> that<00:19:05.700> is<00:19:05.820> in<00:19:06.000> another 00:19:06.110 --> 00:19:06.120 align:start position:0% calling something that is in another 00:19:06.120 --> 00:19:08.630 align:start position:0% calling something that is in another chart<00:19:06.600> because<00:19:07.080> that<00:19:07.500> brings 00:19:08.630 --> 00:19:08.640 align:start position:0% chart because that brings 00:19:08.640 --> 00:19:11.930 align:start position:0% chart because that brings friction<00:19:09.480> to<00:19:09.900> Smart<00:19:10.200> contract<00:19:10.620> Developers 00:19:11.930 --> 00:19:11.940 align:start position:0% friction to Smart contract Developers 00:19:11.940 --> 00:19:14.510 align:start position:0% friction to Smart contract Developers so<00:19:12.539> yeah<00:19:12.840> the<00:19:13.200> model<00:19:13.320> I've<00:19:13.679> been<00:19:14.039> assuming<00:19:14.400> is 00:19:14.510 --> 00:19:14.520 align:start position:0% so yeah the model I've been assuming is 00:19:14.520 --> 00:19:16.610 align:start position:0% so yeah the model I've been assuming is the<00:19:14.700> model<00:19:14.820> of<00:19:15.059> sharding<00:19:15.419> as<00:19:15.600> like<00:19:15.900> small<00:19:16.320> sub 00:19:16.610 --> 00:19:16.620 align:start position:0% the model of sharding as like small sub 00:19:16.620 --> 00:19:18.590 align:start position:0% the model of sharding as like small sub blockchains 00:19:18.590 --> 00:19:18.600 align:start position:0% blockchains 00:19:18.600 --> 00:19:19.730 align:start position:0% blockchains um 00:19:19.730 --> 00:19:19.740 align:start position:0% um 00:19:19.740 --> 00:19:21.710 align:start position:0% um there<00:19:20.160> are<00:19:20.280> some<00:19:20.460> proposals<00:19:21.059> of<00:19:21.179> shorting 00:19:21.710 --> 00:19:21.720 align:start position:0% there are some proposals of shorting 00:19:21.720 --> 00:19:23.150 align:start position:0% there are some proposals of shorting that<00:19:22.200> I<00:19:22.380> would<00:19:22.559> classify<00:19:22.980> under 00:19:23.150 --> 00:19:23.160 align:start position:0% that I would classify under 00:19:23.160 --> 00:19:24.890 align:start position:0% that I would classify under parallelizations<00:19:23.880> you<00:19:24.179> just<00:19:24.360> pretend<00:19:24.720> you 00:19:24.890 --> 00:19:24.900 align:start position:0% parallelizations you just pretend you 00:19:24.900 --> 00:19:26.630 align:start position:0% parallelizations you just pretend you have<00:19:25.020> a<00:19:25.080> big<00:19:25.140> blockchain<00:19:25.559> and<00:19:26.220> then<00:19:26.340> on<00:19:26.520> the 00:19:26.630 --> 00:19:26.640 align:start position:0% have a big blockchain and then on the 00:19:26.640 --> 00:19:28.190 align:start position:0% have a big blockchain and then on the back<00:19:26.760> end<00:19:26.880> you<00:19:27.240> just<00:19:27.360> put<00:19:27.600> things<00:19:27.780> in<00:19:28.020> short 00:19:28.190 --> 00:19:28.200 align:start position:0% back end you just put things in short 00:19:28.200 --> 00:19:30.169 align:start position:0% back end you just put things in short and<00:19:28.440> you<00:19:28.559> move<00:19:28.740> things<00:19:28.919> around<00:19:29.160> but<00:19:29.820> for<00:19:30.000> the 00:19:30.169 --> 00:19:30.179 align:start position:0% and you move things around but for the 00:19:30.179 --> 00:19:31.850 align:start position:0% and you move things around but for the user<00:19:30.419> they<00:19:30.600> don't<00:19:30.720> see<00:19:30.900> that<00:19:31.080> here<00:19:31.500> the<00:19:31.740> model 00:19:31.850 --> 00:19:31.860 align:start position:0% user they don't see that here the model 00:19:31.860 --> 00:19:33.890 align:start position:0% user they don't see that here the model is<00:19:32.039> explicitly<00:19:32.520> you<00:19:32.580> have<00:19:32.760> multiple<00:19:32.940> sub 00:19:33.890 --> 00:19:33.900 align:start position:0% is explicitly you have multiple sub 00:19:33.900 --> 00:19:37.070 align:start position:0% is explicitly you have multiple sub blockchains<00:19:34.620> and<00:19:34.980> they<00:19:35.100> talk<00:19:35.280> to<00:19:35.460> each<00:19:35.580> other 00:19:37.070 --> 00:19:37.080 align:start position:0% blockchains and they talk to each other 00:19:37.080 --> 00:19:38.330 align:start position:0% blockchains and they talk to each other um<00:19:37.140> this<00:19:37.380> I<00:19:37.620> think<00:19:37.740> simplifies<00:19:38.160> the 00:19:38.330 --> 00:19:38.340 align:start position:0% um this I think simplifies the 00:19:38.340 --> 00:19:40.370 align:start position:0% um this I think simplifies the implementation<00:19:38.820> a<00:19:39.000> lot<00:19:39.120> but<00:19:40.020> not<00:19:40.200> everybody 00:19:40.370 --> 00:19:40.380 align:start position:0% implementation a lot but not everybody 00:19:40.380 --> 00:19:42.950 align:start position:0% implementation a lot but not everybody agrees<00:19:40.980> uh<00:19:41.580> actually<00:19:41.940> my<00:19:42.179> good<00:19:42.360> colleague<00:19:42.720> car 00:19:42.950 --> 00:19:42.960 align:start position:0% agrees uh actually my good colleague car 00:19:42.960 --> 00:19:45.890 align:start position:0% agrees uh actually my good colleague car does<00:19:43.440> not<00:19:43.679> entirely<00:19:44.460> agree<00:19:44.640> with<00:19:44.760> that 00:19:45.890 --> 00:19:45.900 align:start position:0% does not entirely agree with that 00:19:45.900 --> 00:19:46.190 align:start position:0% does not entirely agree with that [Music] 00:19:46.190 --> 00:19:46.200 align:start position:0% [Music] 00:19:46.200 --> 00:19:47.690 align:start position:0% [Music] um 00:19:47.690 --> 00:19:47.700 align:start position:0% um 00:19:47.700 --> 00:19:49.970 align:start position:0% um but<00:19:48.179> that's<00:19:48.299> at<00:19:48.480> least<00:19:48.660> my<00:19:48.840> point<00:19:48.960> of<00:19:49.140> view 00:19:49.970 --> 00:19:49.980 align:start position:0% but that's at least my point of view 00:19:49.980 --> 00:19:51.830 align:start position:0% but that's at least my point of view and<00:19:50.460> there<00:19:50.640> are<00:19:50.760> other<00:19:50.880> advantages<00:19:51.360> which<00:19:51.720> is 00:19:51.830 --> 00:19:51.840 align:start position:0% and there are other advantages which is 00:19:51.840 --> 00:19:53.690 align:start position:0% and there are other advantages which is that<00:19:52.020> you<00:19:52.140> can<00:19:52.320> have<00:19:52.559> multiple<00:19:53.039> Roll-Ups<00:19:53.640> that 00:19:53.690 --> 00:19:53.700 align:start position:0% that you can have multiple Roll-Ups that 00:19:53.700 --> 00:19:55.190 align:start position:0% that you can have multiple Roll-Ups that do<00:19:53.880> things<00:19:54.059> slightly<00:19:54.419> differently<00:19:54.840> as<00:19:55.020> I 00:19:55.190 --> 00:19:55.200 align:start position:0% do things slightly differently as I 00:19:55.200 --> 00:19:56.510 align:start position:0% do things slightly differently as I mentioned 00:19:56.510 --> 00:19:56.520 align:start position:0% mentioned 00:19:56.520 --> 00:19:58.789 align:start position:0% mentioned um<00:19:56.580> so<00:19:57.000> that's<00:19:57.179> an<00:19:57.299> advantage 00:19:58.789 --> 00:19:58.799 align:start position:0% um so that's an advantage 00:19:58.799 --> 00:20:01.490 align:start position:0% um so that's an advantage does<00:19:59.220> it<00:19:59.400> okay<00:19:59.700> so<00:20:00.360> regarding<00:20:00.900> the<00:20:01.320> the 00:20:01.490 --> 00:20:01.500 align:start position:0% does it okay so regarding the the 00:20:01.500 --> 00:20:04.070 align:start position:0% does it okay so regarding the the shutting<00:20:01.980> in<00:20:02.100> itself<00:20:02.400> is<00:20:03.120> it<00:20:03.299> possible<00:20:03.720> for 00:20:04.070 --> 00:20:04.080 align:start position:0% shutting in itself is it possible for 00:20:04.080 --> 00:20:06.590 align:start position:0% shutting in itself is it possible for instance<00:20:04.380> to<00:20:04.860> imagine<00:20:05.160> a<00:20:05.640> system<00:20:05.820> where<00:20:06.299> the 00:20:06.590 --> 00:20:06.600 align:start position:0% instance to imagine a system where the 00:20:06.600 --> 00:20:09.230 align:start position:0% instance to imagine a system where the accounts<00:20:07.140> who<00:20:07.380> dynamically<00:20:07.980> move<00:20:08.520> across<00:20:09.120> the 00:20:09.230 --> 00:20:09.240 align:start position:0% accounts who dynamically move across the 00:20:09.240 --> 00:20:13.070 align:start position:0% accounts who dynamically move across the shards<00:20:09.720> to<00:20:10.200> try<00:20:10.440> to<00:20:10.799> reduce<00:20:11.100> as<00:20:11.940> much<00:20:12.539> as<00:20:12.840> can 00:20:13.070 --> 00:20:13.080 align:start position:0% shards to try to reduce as much as can 00:20:13.080 --> 00:20:16.310 align:start position:0% shards to try to reduce as much as can be<00:20:13.260> the<00:20:13.860> internship<00:20:14.520> exchanges<00:20:15.480> on<00:20:15.960> so<00:20:16.200> to 00:20:16.310 --> 00:20:16.320 align:start position:0% be the internship exchanges on so to 00:20:16.320 --> 00:20:18.409 align:start position:0% be the internship exchanges on so to simplify<00:20:16.740> the<00:20:16.919> whole<00:20:17.039> process 00:20:18.409 --> 00:20:18.419 align:start position:0% simplify the whole process 00:20:18.419 --> 00:20:21.230 align:start position:0% simplify the whole process or<00:20:18.900> is<00:20:19.080> it<00:20:19.260> like<00:20:19.440> completely<00:20:19.679> deterior<00:20:20.039> use 00:20:21.230 --> 00:20:21.240 align:start position:0% or is it like completely deterior use 00:20:21.240 --> 00:20:23.090 align:start position:0% or is it like completely deterior use it<00:20:21.660> is<00:20:21.840> possible<00:20:22.200> I<00:20:22.440> know<00:20:22.559> there's<00:20:22.740> research 00:20:23.090 --> 00:20:23.100 align:start position:0% it is possible I know there's research 00:20:23.100 --> 00:20:24.470 align:start position:0% it is possible I know there's research on<00:20:23.280> this<00:20:23.460> I<00:20:23.820> don't<00:20:23.940> really<00:20:24.059> know<00:20:24.240> anything 00:20:24.470 --> 00:20:24.480 align:start position:0% on this I don't really know anything 00:20:24.480 --> 00:20:27.230 align:start position:0% on this I don't really know anything about<00:20:24.780> it<00:20:25.020> but<00:20:25.860> yeah<00:20:26.160> I<00:20:26.340> think<00:20:26.640> this<00:20:26.820> was<00:20:27.059> more 00:20:27.230 --> 00:20:27.240 align:start position:0% about it but yeah I think this was more 00:20:27.240 --> 00:20:28.909 align:start position:0% about it but yeah I think this was more related<00:20:27.539> to<00:20:28.020> the<00:20:28.140> models<00:20:28.440> where<00:20:28.559> you<00:20:28.740> just 00:20:28.909 --> 00:20:28.919 align:start position:0% related to the models where you just 00:20:28.919 --> 00:20:30.409 align:start position:0% related to the models where you just like<00:20:29.039> rebalance<00:20:29.460> The<00:20:29.640> Shard<00:20:29.880> and<00:20:30.120> like<00:20:30.240> you 00:20:30.409 --> 00:20:30.419 align:start position:0% like rebalance The Shard and like you 00:20:30.419 --> 00:20:31.850 align:start position:0% like rebalance The Shard and like you would<00:20:30.539> you<00:20:30.840> necessarily<00:20:31.260> be<00:20:31.380> aware<00:20:31.620> of<00:20:31.679> the 00:20:31.850 --> 00:20:31.860 align:start position:0% would you necessarily be aware of the 00:20:31.860 --> 00:20:33.230 align:start position:0% would you necessarily be aware of the charts 00:20:33.230 --> 00:20:33.240 align:start position:0% charts 00:20:33.240 --> 00:20:35.810 align:start position:0% charts um<00:20:33.419> yeah<00:20:34.080> it<00:20:34.440> exists<00:20:35.100> it's<00:20:35.400> definitely 00:20:35.810 --> 00:20:35.820 align:start position:0% um yeah it exists it's definitely 00:20:35.820 --> 00:20:37.730 align:start position:0% um yeah it exists it's definitely feasible 00:20:37.730 --> 00:20:37.740 align:start position:0% feasible 00:20:37.740 --> 00:20:40.310 align:start position:0% feasible it<00:20:38.220> wasn't<00:20:38.340> really<00:20:38.640> thought<00:20:39.419> through<00:20:39.840> here<00:20:40.140> in 00:20:40.310 --> 00:20:40.320 align:start position:0% it wasn't really thought through here in 00:20:40.320 --> 00:20:42.350 align:start position:0% it wasn't really thought through here in this<00:20:40.440> simple<00:20:40.620> model 00:20:42.350 --> 00:20:42.360 align:start position:0% this simple model 00:20:42.360 --> 00:20:44.630 align:start position:0% this simple model um<00:20:42.480> yeah<00:20:42.780> I<00:20:43.020> think<00:20:43.200> this<00:20:43.440> sort<00:20:43.620> of<00:20:43.740> needs<00:20:44.160> some 00:20:44.630 --> 00:20:44.640 align:start position:0% um yeah I think this sort of needs some 00:20:44.640 --> 00:20:46.130 align:start position:0% um yeah I think this sort of needs some like 00:20:46.130 --> 00:20:46.140 align:start position:0% like 00:20:46.140 --> 00:20:48.470 align:start position:0% like like<00:20:46.860> a<00:20:47.220> balance<00:20:47.760> chain<00:20:47.880> where<00:20:48.120> you<00:20:48.240> have<00:20:48.360> all 00:20:48.470 --> 00:20:48.480 align:start position:0% like a balance chain where you have all 00:20:48.480 --> 00:20:51.230 align:start position:0% like a balance chain where you have all your<00:20:48.600> coins<00:20:48.960> that<00:20:49.440> will<00:20:49.740> probably<00:20:49.980> uh<00:20:50.460> or<00:20:50.760> at 00:20:51.230 --> 00:20:51.240 align:start position:0% your coins that will probably uh or at 00:20:51.240 --> 00:20:52.789 align:start position:0% your coins that will probably uh or at least<00:20:51.360> have<00:20:51.539> your<00:20:51.780> balances<00:20:52.200> be<00:20:52.440> accessible 00:20:52.789 --> 00:20:52.799 align:start position:0% least have your balances be accessible 00:20:52.799 --> 00:20:54.650 align:start position:0% least have your balances be accessible by<00:20:53.039> every<00:20:53.220> Shard<00:20:53.640> that<00:20:54.240> would<00:20:54.419> probably 00:20:54.650 --> 00:20:54.660 align:start position:0% by every Shard that would probably 00:20:54.660 --> 00:20:56.810 align:start position:0% by every Shard that would probably simplify<00:20:55.140> design<00:20:55.320> a<00:20:55.620> lot<00:20:55.679> and<00:20:55.980> in<00:20:56.580> practice 00:20:56.810 --> 00:20:56.820 align:start position:0% simplify design a lot and in practice 00:20:56.820 --> 00:20:58.190 align:start position:0% simplify design a lot and in practice when<00:20:57.240> we<00:20:57.480> see 00:20:58.190 --> 00:20:58.200 align:start position:0% when we see 00:20:58.200 --> 00:20:59.810 align:start position:0% when we see things<00:20:58.620> like<00:20:58.860> Avalanche<00:20:59.340> they<00:20:59.460> have<00:20:59.580> like<00:20:59.700> a 00:20:59.810 --> 00:20:59.820 align:start position:0% things like Avalanche they have like a 00:20:59.820 --> 00:21:01.370 align:start position:0% things like Avalanche they have like a special<00:20:59.940> like<00:21:00.240> chain<00:21:00.539> for<00:21:00.780> like<00:21:00.960> payments 00:21:01.370 --> 00:21:01.380 align:start position:0% special like chain for like payments 00:21:01.380 --> 00:21:04.130 align:start position:0% special like chain for like payments because<00:21:01.559> it's<00:21:01.799> so<00:21:02.039> special<00:21:02.220> and<00:21:02.520> so<00:21:02.700> important 00:21:04.130 --> 00:21:04.140 align:start position:0% because it's so special and so important 00:21:04.140 --> 00:21:05.570 align:start position:0% because it's so special and so important um so<00:21:04.440> that<00:21:04.620> might<00:21:04.799> be<00:21:04.980> one<00:21:05.160> part<00:21:05.340> of<00:21:05.460> the 00:21:05.570 --> 00:21:05.580 align:start position:0% um so that might be one part of the 00:21:05.580 --> 00:21:08.150 align:start position:0% um so that might be one part of the answer 00:21:08.150 --> 00:21:08.160 align:start position:0% 00:21:08.160 --> 00:21:10.909 align:start position:0% hey<00:21:09.000> um<00:21:09.059> my<00:21:09.299> other<00:21:09.419> question<00:21:09.660> was<00:21:10.260> um<00:21:10.260> could<00:21:10.799> we 00:21:10.909 --> 00:21:10.919 align:start position:0% hey um my other question was um could we 00:21:10.919 --> 00:21:13.010 align:start position:0% hey um my other question was um could we use<00:21:11.100> things<00:21:11.280> such<00:21:11.520> as<00:21:11.640> like<00:21:11.880> AI<00:21:12.360> or<00:21:12.600> sort<00:21:12.900> of 00:21:13.010 --> 00:21:13.020 align:start position:0% use things such as like AI or sort of 00:21:13.020 --> 00:21:15.470 align:start position:0% use things such as like AI or sort of predictive<00:21:13.500> behavior<00:21:14.039> in<00:21:14.760> combination<00:21:15.179> with 00:21:15.470 --> 00:21:15.480 align:start position:0% predictive behavior in combination with 00:21:15.480 --> 00:21:17.870 align:start position:0% predictive behavior in combination with this<00:21:15.600> to<00:21:15.900> sort<00:21:16.140> of<00:21:16.260> like<00:21:16.500> just<00:21:17.220> automatically 00:21:17.870 --> 00:21:17.880 align:start position:0% this to sort of like just automatically 00:21:17.880 --> 00:21:20.270 align:start position:0% this to sort of like just automatically optimize<00:21:18.480> or<00:21:18.960> is<00:21:19.140> somebody<00:21:19.320> working<00:21:19.679> on<00:21:19.980> on 00:21:20.270 --> 00:21:20.280 align:start position:0% optimize or is somebody working on on 00:21:20.280 --> 00:21:22.669 align:start position:0% optimize or is somebody working on on stuff<00:21:20.520> like<00:21:20.700> that<00:21:20.880> to<00:21:21.299> sort<00:21:21.960> of<00:21:22.080> predict<00:21:22.380> the 00:21:22.669 --> 00:21:22.679 align:start position:0% stuff like that to sort of predict the 00:21:22.679 --> 00:21:24.529 align:start position:0% stuff like that to sort of predict the interactions<00:21:23.400> between<00:21:23.640> the<00:21:23.880> smart<00:21:24.059> contracts 00:21:24.529 --> 00:21:24.539 align:start position:0% interactions between the smart contracts 00:21:24.539 --> 00:21:26.150 align:start position:0% interactions between the smart contracts and<00:21:24.780> how<00:21:24.960> to<00:21:25.080> kind<00:21:25.260> of<00:21:25.380> optimize<00:21:25.740> across 00:21:26.150 --> 00:21:26.160 align:start position:0% and how to kind of optimize across 00:21:26.160 --> 00:21:28.130 align:start position:0% and how to kind of optimize across charts 00:21:28.130 --> 00:21:28.140 align:start position:0% charts 00:21:28.140 --> 00:21:30.169 align:start position:0% charts uh<00:21:28.860> I'm<00:21:28.980> sure<00:21:29.159> some<00:21:29.340> people<00:21:29.580> are<00:21:29.760> working<00:21:29.880> on 00:21:30.169 --> 00:21:30.179 align:start position:0% uh I'm sure some people are working on 00:21:30.179 --> 00:21:31.370 align:start position:0% uh I'm sure some people are working on it<00:21:30.299> I<00:21:30.539> know 00:21:31.370 --> 00:21:31.380 align:start position:0% it I know 00:21:31.380 --> 00:21:33.049 align:start position:0% it I know I<00:21:31.860> know<00:21:31.980> there's<00:21:32.159> a<00:21:32.340> bunch<00:21:32.460> of<00:21:32.580> research<00:21:32.820> with 00:21:33.049 --> 00:21:33.059 align:start position:0% I know there's a bunch of research with 00:21:33.059 --> 00:21:35.149 align:start position:0% I know there's a bunch of research with that<00:21:33.299> even<00:21:33.900> on<00:21:34.140> payment<00:21:34.380> chains<00:21:34.860> so<00:21:35.039> things 00:21:35.149 --> 00:21:35.159 align:start position:0% that even on payment chains so things 00:21:35.159 --> 00:21:36.649 align:start position:0% that even on payment chains so things like<00:21:35.280> Bitcoin<00:21:35.760> and<00:21:35.880> stuff<00:21:36.059> I<00:21:36.240> don't<00:21:36.360> know<00:21:36.480> why 00:21:36.649 --> 00:21:36.659 align:start position:0% like Bitcoin and stuff I don't know why 00:21:36.659 --> 00:21:38.870 align:start position:0% like Bitcoin and stuff I don't know why it<00:21:37.080> was<00:21:37.200> very<00:21:37.380> hot<00:21:37.559> academic<00:21:38.220> like<00:21:38.400> academics 00:21:38.870 --> 00:21:38.880 align:start position:0% it was very hot academic like academics 00:21:38.880 --> 00:21:40.909 align:start position:0% it was very hot academic like academics are<00:21:39.059> like<00:21:39.179> lagging<00:21:39.659> behind<00:21:40.080> uh<00:21:40.500> the<00:21:40.679> stuff<00:21:40.799> we 00:21:40.909 --> 00:21:40.919 align:start position:0% are like lagging behind uh the stuff we 00:21:40.919 --> 00:21:43.669 align:start position:0% are like lagging behind uh the stuff we do<00:21:41.159> a<00:21:41.280> lot<00:21:41.400> and<00:21:42.120> they've<00:21:42.419> been<00:21:42.539> like<00:21:42.780> very<00:21:43.380> like 00:21:43.669 --> 00:21:43.679 align:start position:0% do a lot and they've been like very like 00:21:43.679 --> 00:21:45.230 align:start position:0% do a lot and they've been like very like I've<00:21:43.860> been<00:21:44.039> to<00:21:44.220> a<00:21:44.340> workshop<00:21:44.820> this<00:21:45.000> year<00:21:45.120> and 00:21:45.230 --> 00:21:45.240 align:start position:0% I've been to a workshop this year and 00:21:45.240 --> 00:21:46.549 align:start position:0% I've been to a workshop this year and they're<00:21:45.419> very<00:21:45.600> interested<00:21:45.900> in<00:21:45.960> exactly<00:21:46.380> this 00:21:46.549 --> 00:21:46.559 align:start position:0% they're very interested in exactly this 00:21:46.559 --> 00:21:48.110 align:start position:0% they're very interested in exactly this problem<00:21:46.799> and<00:21:47.340> I'm<00:21:47.460> like<00:21:47.640> does<00:21:47.820> this<00:21:48.000> change 00:21:48.110 --> 00:21:48.120 align:start position:0% problem and I'm like does this change 00:21:48.120 --> 00:21:49.669 align:start position:0% problem and I'm like does this change the<00:21:48.360> smart<00:21:48.480> contract<00:21:48.840> and<00:21:49.020> we're<00:21:49.200> like<00:21:49.320> no<00:21:49.500> I'm 00:21:49.669 --> 00:21:49.679 align:start position:0% the smart contract and we're like no I'm 00:21:49.679 --> 00:21:51.770 align:start position:0% the smart contract and we're like no I'm like<00:21:49.860> What's<00:21:50.640> even<00:21:50.880> the<00:21:51.059> point<00:21:51.240> like<00:21:51.539> just<00:21:51.659> put 00:21:51.770 --> 00:21:51.780 align:start position:0% like What's even the point like just put 00:21:51.780 --> 00:21:54.289 align:start position:0% like What's even the point like just put it<00:21:51.960> on<00:21:52.080> a<00:21:52.200> big<00:21:52.260> server<00:21:52.559> and<00:21:52.679> be<00:21:52.860> done<00:21:53.039> with<00:21:53.159> it 00:21:54.289 --> 00:21:54.299 align:start position:0% it on a big server and be done with it 00:21:54.299 --> 00:21:55.549 align:start position:0% it on a big server and be done with it um 00:21:55.549 --> 00:21:55.559 align:start position:0% um 00:21:55.559 --> 00:21:57.289 align:start position:0% um but<00:21:56.039> yeah<00:21:56.159> you<00:21:56.340> could<00:21:56.460> do<00:21:56.580> it's<00:21:56.760> sort<00:21:57.240> of 00:21:57.289 --> 00:21:57.299 align:start position:0% but yeah you could do it's sort of 00:21:57.299 --> 00:21:58.610 align:start position:0% but yeah you could do it's sort of didn't<00:21:57.419> assume<00:21:57.840> that<00:21:57.900> model<00:21:58.080> here<00:21:58.320> but<00:21:58.500> it's 00:21:58.610 --> 00:21:58.620 align:start position:0% didn't assume that model here but it's 00:21:58.620 --> 00:21:59.930 align:start position:0% didn't assume that model here but it's doable 00:21:59.930 --> 00:21:59.940 align:start position:0% doable 00:21:59.940 --> 00:22:02.090 align:start position:0% doable okay<00:22:00.600> thank<00:22:01.200> you<00:22:01.320> very<00:22:01.440> much 00:22:02.090 --> 00:22:02.100 align:start position:0% okay thank you very much 00:22:02.100 --> 00:22:03.690 align:start position:0% okay thank you very much foreign 00:22:03.690 --> 00:22:03.700 align:start position:0% foreign 00:22:03.700 --> 00:22:06.829 align:start position:0% foreign [Music]