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:13.629 align:start position:0% [Music] 00:00:13.629 --> 00:00:13.639 align:start position:0% 00:00:13.639 --> 00:00:16.790 align:start position:0% my<00:00:14.639> name<00:00:14.700> is<00:00:14.820> Justin<00:00:15.320> and<00:00:16.320> along<00:00:16.560> with 00:00:16.790 --> 00:00:16.800 align:start position:0% my name is Justin and along with 00:00:16.800 --> 00:00:18.710 align:start position:0% my name is Justin and along with alvarius<00:00:17.520> and<00:00:17.760> our<00:00:17.820> friend<00:00:18.000> Kelvin<00:00:18.480> from 00:00:18.710 --> 00:00:18.720 align:start position:0% alvarius and our friend Kelvin from 00:00:18.720 --> 00:00:20.510 align:start position:0% alvarius and our friend Kelvin from optimism<00:00:19.140> we're<00:00:19.740> going<00:00:19.920> to<00:00:20.039> go<00:00:20.100> over<00:00:20.220> new 00:00:20.510 --> 00:00:20.520 align:start position:0% optimism we're going to go over new 00:00:20.520 --> 00:00:23.330 align:start position:0% optimism we're going to go over new technologies<00:00:21.180> for<00:00:21.480> ancient<00:00:21.900> gaming<00:00:22.800> so 00:00:23.330 --> 00:00:23.340 align:start position:0% technologies for ancient gaming so 00:00:23.340 --> 00:00:26.390 align:start position:0% technologies for ancient gaming so Alvarez<00:00:24.060> and<00:00:24.180> I<00:00:24.359> work<00:00:24.660> on<00:00:24.960> lattice<00:00:25.439> among<00:00:26.220> with 00:00:26.390 --> 00:00:26.400 align:start position:0% Alvarez and I work on lattice among with 00:00:26.400 --> 00:00:28.130 align:start position:0% Alvarez and I work on lattice among with many<00:00:26.699> others<00:00:27.180> it's<00:00:27.480> a<00:00:27.599> project<00:00:27.720> that's<00:00:27.960> been 00:00:28.130 --> 00:00:28.140 align:start position:0% many others it's a project that's been 00:00:28.140 --> 00:00:30.230 align:start position:0% many others it's a project that's been out<00:00:28.320> of<00:00:28.439> Zurich<00:00:28.800> spark<00:00:29.099> in<00:00:29.460> others<00:00:29.880> to<00:00:30.000> in 00:00:30.230 --> 00:00:30.240 align:start position:0% out of Zurich spark in others to in 00:00:30.240 --> 00:00:31.970 align:start position:0% out of Zurich spark in others to in order<00:00:30.359> to<00:00:30.539> push<00:00:30.660> the<00:00:30.840> envelope<00:00:31.199> of<00:00:31.380> Unchained 00:00:31.970 --> 00:00:31.980 align:start position:0% order to push the envelope of Unchained 00:00:31.980 --> 00:00:33.130 align:start position:0% order to push the envelope of Unchained gaming 00:00:33.130 --> 00:00:33.140 align:start position:0% gaming 00:00:33.140 --> 00:00:35.450 align:start position:0% gaming we<00:00:34.140> basically<00:00:34.380> want<00:00:34.559> to<00:00:34.680> enable<00:00:34.920> people<00:00:35.219> to 00:00:35.450 --> 00:00:35.460 align:start position:0% we basically want to enable people to 00:00:35.460 --> 00:00:38.389 align:start position:0% we basically want to enable people to build<00:00:35.579> crazy<00:00:35.820> things<00:00:36.059> on<00:00:36.300> top<00:00:36.420> of<00:00:36.540> ethereum 00:00:38.389 --> 00:00:38.399 align:start position:0% build crazy things on top of ethereum 00:00:38.399 --> 00:00:41.090 align:start position:0% build crazy things on top of ethereum um<00:00:38.460> and<00:00:39.059> things<00:00:39.840> like<00:00:40.079> full-on<00:00:40.620> Virtual 00:00:41.090 --> 00:00:41.100 align:start position:0% um and things like full-on Virtual 00:00:41.100 --> 00:00:44.209 align:start position:0% um and things like full-on Virtual Worlds<00:00:41.520> worlds<00:00:42.180> whose<00:00:42.600> rules<00:00:43.079> run<00:00:43.440> on<00:00:43.680> the<00:00:43.800> evm 00:00:44.209 --> 00:00:44.219 align:start position:0% Worlds worlds whose rules run on the evm 00:00:44.219 --> 00:00:46.610 align:start position:0% Worlds worlds whose rules run on the evm and<00:00:44.399> whose<00:00:44.760> state<00:00:44.940> is<00:00:45.180> secured<00:00:45.540> by<00:00:45.719> ethereum 00:00:46.610 --> 00:00:46.620 align:start position:0% and whose state is secured by ethereum 00:00:46.620 --> 00:00:48.410 align:start position:0% and whose state is secured by ethereum people<00:00:47.100> usually<00:00:47.460> refer<00:00:47.760> to<00:00:47.879> those<00:00:48.059> projects 00:00:48.410 --> 00:00:48.420 align:start position:0% people usually refer to those projects 00:00:48.420 --> 00:00:50.690 align:start position:0% people usually refer to those projects as<00:00:48.660> on-chain<00:00:49.260> games<00:00:49.440> but<00:00:49.860> we<00:00:50.219> prefer<00:00:50.460> to<00:00:50.579> call 00:00:50.690 --> 00:00:50.700 align:start position:0% as on-chain games but we prefer to call 00:00:50.700 --> 00:00:52.130 align:start position:0% as on-chain games but we prefer to call them<00:00:50.820> autonomous<00:00:51.239> worlds<00:00:51.600> because<00:00:51.719> we<00:00:51.899> think 00:00:52.130 --> 00:00:52.140 align:start position:0% them autonomous worlds because we think 00:00:52.140 --> 00:00:53.510 align:start position:0% them autonomous worlds because we think it<00:00:52.260> goes<00:00:52.500> well<00:00:52.620> beyond<00:00:52.920> gaming<00:00:53.219> it's<00:00:53.399> about 00:00:53.510 --> 00:00:53.520 align:start position:0% it goes well beyond gaming it's about 00:00:53.520 --> 00:00:55.130 align:start position:0% it goes well beyond gaming it's about giving<00:00:53.760> autonomy<00:00:54.300> and<00:00:54.420> sovereignty<00:00:54.899> to 00:00:55.130 --> 00:00:55.140 align:start position:0% giving autonomy and sovereignty to 00:00:55.140 --> 00:00:57.110 align:start position:0% giving autonomy and sovereignty to complex<00:00:55.440> systems 00:00:57.110 --> 00:00:57.120 align:start position:0% complex systems 00:00:57.120 --> 00:00:58.970 align:start position:0% complex systems so<00:00:57.660> the<00:00:57.960> problem<00:00:58.079> is<00:00:58.320> building<00:00:58.620> large 00:00:58.970 --> 00:00:58.980 align:start position:0% so the problem is building large 00:00:58.980 --> 00:01:00.470 align:start position:0% so the problem is building large on-chain<00:00:59.520> projects<00:00:59.879> is<00:01:00.000> actually<00:01:00.180> really 00:01:00.470 --> 00:01:00.480 align:start position:0% on-chain projects is actually really 00:01:00.480 --> 00:01:02.510 align:start position:0% on-chain projects is actually really hard<00:01:00.840> which<00:01:01.559> is<00:01:01.680> why<00:01:01.860> today<00:01:02.100> we're<00:01:02.340> going<00:01:02.460> to 00:01:02.510 --> 00:01:02.520 align:start position:0% hard which is why today we're going to 00:01:02.520 --> 00:01:04.130 align:start position:0% hard which is why today we're going to go<00:01:02.640> over<00:01:02.760> two<00:01:03.239> new<00:01:03.480> key<00:01:03.660> pieces<00:01:03.960> of 00:01:04.130 --> 00:01:04.140 align:start position:0% go over two new key pieces of 00:01:04.140 --> 00:01:05.929 align:start position:0% go over two new key pieces of Technologies<00:01:04.619> built<00:01:05.159> by<00:01:05.280> lattice<00:01:05.760> and 00:01:05.929 --> 00:01:05.939 align:start position:0% Technologies built by lattice and 00:01:05.939 --> 00:01:07.670 align:start position:0% Technologies built by lattice and optimism<00:01:06.360> in<00:01:06.720> order<00:01:06.780> to<00:01:06.960> enable<00:01:07.200> autonomous 00:01:07.670 --> 00:01:07.680 align:start position:0% optimism in order to enable autonomous 00:01:07.680 --> 00:01:09.469 align:start position:0% optimism in order to enable autonomous worlds<00:01:08.100> and<00:01:08.580> I'm<00:01:08.700> going<00:01:08.880> to<00:01:09.000> pass<00:01:09.060> it<00:01:09.240> to<00:01:09.360> a 00:01:09.469 --> 00:01:09.479 align:start position:0% worlds and I'm going to pass it to a 00:01:09.479 --> 00:01:11.950 align:start position:0% worlds and I'm going to pass it to a various<00:01:09.780> to<00:01:09.960> go<00:01:10.080> over<00:01:10.140> the<00:01:10.380> first<00:01:10.500> one 00:01:11.950 --> 00:01:11.960 align:start position:0% various to go over the first one 00:01:11.960 --> 00:01:14.929 align:start position:0% various to go over the first one cool<00:01:12.979> so<00:01:13.979> the<00:01:14.159> first<00:01:14.280> key<00:01:14.520> piece<00:01:14.820> of 00:01:14.929 --> 00:01:14.939 align:start position:0% cool so the first key piece of 00:01:14.939 --> 00:01:16.310 align:start position:0% cool so the first key piece of technology<00:01:15.299> that<00:01:15.600> we<00:01:15.780> want<00:01:15.900> to<00:01:15.960> introduce 00:01:16.310 --> 00:01:16.320 align:start position:0% technology that we want to introduce 00:01:16.320 --> 00:01:18.830 align:start position:0% technology that we want to introduce today<00:01:16.500> is<00:01:16.920> Matt<00:01:17.159> mud<00:01:17.939> is<00:01:18.119> an<00:01:18.240> on-chain<00:01:18.600> game 00:01:18.830 --> 00:01:18.840 align:start position:0% today is Matt mud is an on-chain game 00:01:18.840 --> 00:01:20.630 align:start position:0% today is Matt mud is an on-chain game engine<00:01:19.080> or<00:01:19.560> how<00:01:19.740> we<00:01:19.860> like<00:01:20.040> to<00:01:20.159> call<00:01:20.280> it<00:01:20.460> an 00:01:20.630 --> 00:01:20.640 align:start position:0% engine or how we like to call it an 00:01:20.640 --> 00:01:22.429 align:start position:0% engine or how we like to call it an engine<00:01:20.820> for<00:01:21.240> autonomous<00:01:21.659> worlds<00:01:22.140> that<00:01:22.320> we 00:01:22.429 --> 00:01:22.439 align:start position:0% engine for autonomous worlds that we 00:01:22.439 --> 00:01:25.370 align:start position:0% engine for autonomous worlds that we develop<00:01:22.799> here<00:01:22.979> at<00:01:23.100> lattice<00:01:24.000> and<00:01:24.659> when<00:01:25.259> we 00:01:25.370 --> 00:01:25.380 align:start position:0% develop here at lattice and when we 00:01:25.380 --> 00:01:27.109 align:start position:0% develop here at lattice and when we started<00:01:25.740> working<00:01:25.860> on<00:01:26.100> on-chain<00:01:26.520> games<00:01:26.700> there 00:01:27.109 --> 00:01:27.119 align:start position:0% started working on on-chain games there 00:01:27.119 --> 00:01:28.969 align:start position:0% started working on on-chain games there was<00:01:27.299> no<00:01:27.420> engine<00:01:27.600> to<00:01:27.900> build<00:01:27.960> upon<00:01:28.320> so<00:01:28.500> we<00:01:28.680> had<00:01:28.799> to 00:01:28.969 --> 00:01:28.979 align:start position:0% was no engine to build upon so we had to 00:01:28.979 --> 00:01:30.830 align:start position:0% was no engine to build upon so we had to run<00:01:29.520> through<00:01:29.700> all<00:01:29.939> of<00:01:30.060> these<00:01:30.299> very<00:01:30.659> common 00:01:30.830 --> 00:01:30.840 align:start position:0% run through all of these very common 00:01:30.840 --> 00:01:33.230 align:start position:0% run through all of these very common very<00:01:31.259> like<00:01:31.619> General<00:01:31.860> problems<00:01:32.460> very 00:01:33.230 --> 00:01:33.240 align:start position:0% very like General problems very 00:01:33.240 --> 00:01:34.730 align:start position:0% very like General problems very non-trivial<00:01:33.780> problems<00:01:34.140> as<00:01:34.259> well<00:01:34.380> but<00:01:34.560> they 00:01:34.730 --> 00:01:34.740 align:start position:0% non-trivial problems as well but they 00:01:34.740 --> 00:01:36.109 align:start position:0% non-trivial problems as well but they were<00:01:34.860> common<00:01:35.100> in<00:01:35.400> all<00:01:35.520> the<00:01:35.640> games<00:01:35.759> we<00:01:35.939> were 00:01:36.109 --> 00:01:36.119 align:start position:0% were common in all the games we were 00:01:36.119 --> 00:01:38.270 align:start position:0% were common in all the games we were building<00:01:36.299> so<00:01:36.900> we<00:01:37.020> set<00:01:37.140> out<00:01:37.320> to<00:01:37.500> build<00:01:37.680> this<00:01:37.979> key 00:01:38.270 --> 00:01:38.280 align:start position:0% building so we set out to build this key 00:01:38.280 --> 00:01:40.370 align:start position:0% building so we set out to build this key missing<00:01:38.640> piece<00:01:38.939> of<00:01:39.000> infrastructure<00:01:39.600> and 00:01:40.370 --> 00:01:40.380 align:start position:0% missing piece of infrastructure and 00:01:40.380 --> 00:01:42.350 align:start position:0% missing piece of infrastructure and build<00:01:40.680> mud<00:01:41.100> with<00:01:41.280> the<00:01:41.400> goal<00:01:41.640> of<00:01:41.759> solving<00:01:42.119> all 00:01:42.350 --> 00:01:42.360 align:start position:0% build mud with the goal of solving all 00:01:42.360 --> 00:01:44.210 align:start position:0% build mud with the goal of solving all the<00:01:42.479> hard<00:01:42.600> problems<00:01:43.079> of<00:01:43.380> building<00:01:43.619> on-chain 00:01:44.210 --> 00:01:44.220 align:start position:0% the hard problems of building on-chain 00:01:44.220 --> 00:01:45.710 align:start position:0% the hard problems of building on-chain games 00:01:45.710 --> 00:01:45.720 align:start position:0% games 00:01:45.720 --> 00:01:47.510 align:start position:0% games so<00:01:46.140> what<00:01:46.320> are<00:01:46.500> the<00:01:46.619> hard<00:01:46.680> problems<00:01:47.100> of<00:01:47.280> of 00:01:47.510 --> 00:01:47.520 align:start position:0% so what are the hard problems of of 00:01:47.520 --> 00:01:49.249 align:start position:0% so what are the hard problems of of building<00:01:47.759> Unchained<00:01:48.299> games<00:01:48.360> well<00:01:48.659> they've 00:01:49.249 --> 00:01:49.259 align:start position:0% building Unchained games well they've 00:01:49.259 --> 00:01:50.990 align:start position:0% building Unchained games well they've Fallen<00:01:49.500> to<00:01:49.680> mainly<00:01:50.040> three<00:01:50.280> categories<00:01:50.700> the 00:01:50.990 --> 00:01:51.000 align:start position:0% Fallen to mainly three categories the 00:01:51.000 --> 00:01:52.789 align:start position:0% Fallen to mainly three categories the first<00:01:51.180> one<00:01:51.360> is<00:01:51.600> how<00:01:52.020> to<00:01:52.140> make<00:01:52.259> sure<00:01:52.439> that<00:01:52.680> your 00:01:52.789 --> 00:01:52.799 align:start position:0% first one is how to make sure that your 00:01:52.799 --> 00:01:54.469 align:start position:0% first one is how to make sure that your client<00:01:53.100> and<00:01:53.460> your<00:01:53.579> contract<00:01:53.880> state<00:01:54.180> are 00:01:54.469 --> 00:01:54.479 align:start position:0% client and your contract state are 00:01:54.479 --> 00:01:56.749 align:start position:0% client and your contract state are always<00:01:54.600> in<00:01:54.840> sync<00:01:55.200> and<00:01:55.799> then<00:01:56.040> the<00:01:56.159> next<00:01:56.280> one<00:01:56.520> is 00:01:56.749 --> 00:01:56.759 align:start position:0% always in sync and then the next one is 00:01:56.759 --> 00:01:59.210 align:start position:0% always in sync and then the next one is how<00:01:57.299> to<00:01:57.479> architect<00:01:58.020> your<00:01:58.259> game<00:01:58.380> in<00:01:58.560> a<00:01:58.740> way<00:01:58.799> that 00:01:59.210 --> 00:01:59.220 align:start position:0% how to architect your game in a way that 00:01:59.220 --> 00:02:00.649 align:start position:0% how to architect your game in a way that it<00:01:59.399> that<00:01:59.640> makes<00:01:59.820> it<00:01:59.939> easy<00:02:00.119> to<00:02:00.299> add<00:02:00.479> more 00:02:00.649 --> 00:02:00.659 align:start position:0% it that makes it easy to add more 00:02:00.659 --> 00:02:02.569 align:start position:0% it that makes it easy to add more content<00:02:01.020> later<00:02:01.259> without<00:02:01.560> having<00:02:01.860> to<00:02:02.040> refactor 00:02:02.569 --> 00:02:02.579 align:start position:0% content later without having to refactor 00:02:02.579 --> 00:02:04.969 align:start position:0% content later without having to refactor the<00:02:03.060> entire<00:02:03.299> code<00:02:03.479> base<00:02:03.720> and<00:02:04.500> then<00:02:04.619> the<00:02:04.860> third 00:02:04.969 --> 00:02:04.979 align:start position:0% the entire code base and then the third 00:02:04.979 --> 00:02:07.429 align:start position:0% the entire code base and then the third thing<00:02:05.219> if<00:02:05.759> you<00:02:05.939> care<00:02:06.180> about<00:02:06.420> impact<00:02:07.020> Beyond 00:02:07.429 --> 00:02:07.439 align:start position:0% thing if you care about impact Beyond 00:02:07.439 --> 00:02:09.529 align:start position:0% thing if you care about impact Beyond just<00:02:07.619> an<00:02:07.860> individual<00:02:08.280> game<00:02:08.459> then<00:02:08.819> how<00:02:09.300> do<00:02:09.420> you 00:02:09.529 --> 00:02:09.539 align:start position:0% just an individual game then how do you 00:02:09.539 --> 00:02:10.550 align:start position:0% just an individual game then how do you make<00:02:09.599> sure<00:02:09.780> that<00:02:10.080> your<00:02:10.259> game<00:02:10.440> is 00:02:10.550 --> 00:02:10.560 align:start position:0% make sure that your game is 00:02:10.560 --> 00:02:12.170 align:start position:0% make sure that your game is interoperable<00:02:11.160> with<00:02:11.580> all<00:02:11.760> the<00:02:11.879> other<00:02:12.000> games 00:02:12.170 --> 00:02:12.180 align:start position:0% interoperable with all the other games 00:02:12.180 --> 00:02:14.270 align:start position:0% interoperable with all the other games out<00:02:12.480> there 00:02:14.270 --> 00:02:14.280 align:start position:0% out there 00:02:14.280 --> 00:02:17.030 align:start position:0% out there so<00:02:14.700> before<00:02:14.879> I<00:02:15.180> go<00:02:15.360> into<00:02:15.599> how<00:02:16.319> mud<00:02:16.560> solves<00:02:16.860> all 00:02:17.030 --> 00:02:17.040 align:start position:0% so before I go into how mud solves all 00:02:17.040 --> 00:02:19.070 align:start position:0% so before I go into how mud solves all of<00:02:17.160> these<00:02:17.340> problems<00:02:17.700> let<00:02:18.300> me<00:02:18.420> quickly<00:02:18.660> go<00:02:18.959> over 00:02:19.070 --> 00:02:19.080 align:start position:0% of these problems let me quickly go over 00:02:19.080 --> 00:02:22.010 align:start position:0% of these problems let me quickly go over like<00:02:19.500> the<00:02:19.860> previous<00:02:20.040> common<00:02:20.400> approach<00:02:20.879> of 00:02:22.010 --> 00:02:22.020 align:start position:0% like the previous common approach of 00:02:22.020 --> 00:02:24.430 align:start position:0% like the previous common approach of um<00:02:22.080> yeah<00:02:22.459> approaching<00:02:23.459> these<00:02:24.000> challenges 00:02:24.430 --> 00:02:24.440 align:start position:0% um yeah approaching these challenges 00:02:24.440 --> 00:02:26.690 align:start position:0% um yeah approaching these challenges usually<00:02:25.440> the<00:02:25.860> the<00:02:25.980> most<00:02:26.220> common<00:02:26.340> approach 00:02:26.690 --> 00:02:26.700 align:start position:0% usually the the most common approach 00:02:26.700 --> 00:02:28.430 align:start position:0% usually the the most common approach before<00:02:26.879> was<00:02:27.180> you<00:02:27.420> have<00:02:27.599> one<00:02:27.900> struct<00:02:28.260> per 00:02:28.430 --> 00:02:28.440 align:start position:0% before was you have one struct per 00:02:28.440 --> 00:02:30.890 align:start position:0% before was you have one struct per entity<00:02:28.739> type<00:02:29.040> on<00:02:29.640> your<00:02:29.760> contract<00:02:30.120> like<00:02:30.480> if<00:02:30.780> you 00:02:30.890 --> 00:02:30.900 align:start position:0% entity type on your contract like if you 00:02:30.900 --> 00:02:32.150 align:start position:0% entity type on your contract like if you want<00:02:31.020> to<00:02:31.140> have<00:02:31.200> a<00:02:31.319> monster<00:02:31.440> then<00:02:31.800> you<00:02:31.920> have<00:02:32.040> a 00:02:32.150 --> 00:02:32.160 align:start position:0% want to have a monster then you have a 00:02:32.160 --> 00:02:34.070 align:start position:0% want to have a monster then you have a monster<00:02:32.280> struct<00:02:32.760> and<00:02:33.239> in<00:02:33.420> that<00:02:33.540> struct<00:02:33.900> you 00:02:34.070 --> 00:02:34.080 align:start position:0% monster struct and in that struct you 00:02:34.080 --> 00:02:36.710 align:start position:0% monster struct and in that struct you store<00:02:34.260> all<00:02:34.440> the<00:02:34.680> data<00:02:35.040> for<00:02:35.760> that<00:02:36.000> struct<00:02:36.300> for 00:02:36.710 --> 00:02:36.720 align:start position:0% store all the data for that struct for 00:02:36.720 --> 00:02:38.990 align:start position:0% store all the data for that struct for that<00:02:37.080> entity<00:02:37.440> and<00:02:38.280> then<00:02:38.400> of<00:02:38.580> course<00:02:38.700> on<00:02:38.879> the 00:02:38.990 --> 00:02:39.000 align:start position:0% that entity and then of course on the 00:02:39.000 --> 00:02:41.330 align:start position:0% that entity and then of course on the client<00:02:39.239> you<00:02:39.420> have<00:02:39.540> to<00:02:39.660> replicate<00:02:40.319> that<00:02:41.040> like 00:02:41.330 --> 00:02:41.340 align:start position:0% client you have to replicate that like 00:02:41.340 --> 00:02:42.770 align:start position:0% client you have to replicate that like interface<00:02:41.700> in<00:02:41.879> order<00:02:42.000> to<00:02:42.239> represent<00:02:42.599> the 00:02:42.770 --> 00:02:42.780 align:start position:0% interface in order to represent the 00:02:42.780 --> 00:02:45.050 align:start position:0% interface in order to represent the state<00:02:42.959> there<00:02:43.200> and<00:02:44.099> then<00:02:44.280> you<00:02:44.580> have<00:02:44.700> getter 00:02:45.050 --> 00:02:45.060 align:start position:0% state there and then you have getter 00:02:45.060 --> 00:02:46.790 align:start position:0% state there and then you have getter functions<00:02:45.420> for<00:02:45.660> each<00:02:45.840> individual<00:02:46.260> like<00:02:46.500> type 00:02:46.790 --> 00:02:46.800 align:start position:0% functions for each individual like type 00:02:46.800 --> 00:02:48.410 align:start position:0% functions for each individual like type of<00:02:46.920> entity<00:02:47.220> that<00:02:47.519> you<00:02:47.640> want<00:02:47.819> to<00:02:47.879> sync<00:02:48.120> to<00:02:48.239> a 00:02:48.410 --> 00:02:48.420 align:start position:0% of entity that you want to sync to a 00:02:48.420 --> 00:02:50.690 align:start position:0% of entity that you want to sync to a client<00:02:48.660> and<00:02:49.620> you<00:02:49.860> implement<00:02:50.160> your<00:02:50.340> logic 00:02:50.690 --> 00:02:50.700 align:start position:0% client and you implement your logic 00:02:50.700 --> 00:02:52.729 align:start position:0% client and you implement your logic based<00:02:51.060> on<00:02:51.180> these<00:02:51.420> specific<00:02:51.720> structs<00:02:52.319> and 00:02:52.729 --> 00:02:52.739 align:start position:0% based on these specific structs and 00:02:52.739 --> 00:02:54.949 align:start position:0% based on these specific structs and every<00:02:52.920> time<00:02:53.160> you<00:02:53.580> modify<00:02:54.180> one<00:02:54.420> of<00:02:54.480> these<00:02:54.660> data 00:02:54.949 --> 00:02:54.959 align:start position:0% every time you modify one of these data 00:02:54.959 --> 00:02:56.449 align:start position:0% every time you modify one of these data structures<00:02:55.200> you<00:02:55.500> have<00:02:55.620> to<00:02:55.739> emit<00:02:56.099> a<00:02:56.280> custom 00:02:56.449 --> 00:02:56.459 align:start position:0% structures you have to emit a custom 00:02:56.459 --> 00:02:58.490 align:start position:0% structures you have to emit a custom event<00:02:56.760> that<00:02:57.480> then<00:02:57.660> can<00:02:57.840> be<00:02:57.959> called<00:02:58.140> by<00:02:58.379> the 00:02:58.490 --> 00:02:58.500 align:start position:0% event that then can be called by the 00:02:58.500 --> 00:03:00.589 align:start position:0% event that then can be called by the client<00:02:58.800> to<00:02:59.340> then<00:02:59.519> like<00:02:59.760> update<00:03:00.120> the<00:03:00.420> local 00:03:00.589 --> 00:03:00.599 align:start position:0% client to then like update the local 00:03:00.599 --> 00:03:03.050 align:start position:0% client to then like update the local client<00:03:01.019> state 00:03:03.050 --> 00:03:03.060 align:start position:0% client state 00:03:03.060 --> 00:03:04.729 align:start position:0% client state and<00:03:03.599> this<00:03:03.780> is<00:03:03.840> already<00:03:04.019> this<00:03:04.319> sounds<00:03:04.500> already 00:03:04.729 --> 00:03:04.739 align:start position:0% and this is already this sounds already 00:03:04.739 --> 00:03:06.229 align:start position:0% and this is already this sounds already pretty<00:03:05.040> annoying<00:03:05.400> but<00:03:05.519> it<00:03:05.700> gets<00:03:05.879> even<00:03:06.000> more 00:03:06.229 --> 00:03:06.239 align:start position:0% pretty annoying but it gets even more 00:03:06.239 --> 00:03:07.610 align:start position:0% pretty annoying but it gets even more annoying<00:03:06.540> when<00:03:06.780> you<00:03:06.959> want<00:03:07.140> to<00:03:07.260> now<00:03:07.440> add 00:03:07.610 --> 00:03:07.620 align:start position:0% annoying when you want to now add 00:03:07.620 --> 00:03:09.770 align:start position:0% annoying when you want to now add content<00:03:08.040> because<00:03:08.340> now<00:03:09.000> you<00:03:09.300> have<00:03:09.360> to<00:03:09.480> add<00:03:09.599> a 00:03:09.770 --> 00:03:09.780 align:start position:0% content because now you have to add a 00:03:09.780 --> 00:03:11.030 align:start position:0% content because now you have to add a new<00:03:09.900> struct<00:03:10.140> and<00:03:10.379> you<00:03:10.560> basically<00:03:10.800> have<00:03:10.920> to 00:03:11.030 --> 00:03:11.040 align:start position:0% new struct and you basically have to 00:03:11.040 --> 00:03:13.070 align:start position:0% new struct and you basically have to edit<00:03:11.340> your<00:03:11.459> entire<00:03:11.760> network<00:03:12.000> stack<00:03:12.480> in<00:03:12.959> order 00:03:13.070 --> 00:03:13.080 align:start position:0% edit your entire network stack in order 00:03:13.080 --> 00:03:14.869 align:start position:0% edit your entire network stack in order to<00:03:13.260> make<00:03:13.440> it<00:03:13.620> compatible<00:03:13.980> with<00:03:14.280> this<00:03:14.459> this<00:03:14.640> new 00:03:14.869 --> 00:03:14.879 align:start position:0% to make it compatible with this this new 00:03:14.879 --> 00:03:17.930 align:start position:0% to make it compatible with this this new struct<00:03:15.180> from<00:03:15.599> the<00:03:16.319> event<00:03:16.739> over<00:03:17.280> the<00:03:17.519> getter 00:03:17.930 --> 00:03:17.940 align:start position:0% struct from the event over the getter 00:03:17.940 --> 00:03:20.750 align:start position:0% struct from the event over the getter functions<00:03:18.420> to<00:03:18.840> like<00:03:19.440> the<00:03:20.220> um<00:03:20.280> yeah<00:03:20.519> event 00:03:20.750 --> 00:03:20.760 align:start position:0% functions to like the um yeah event 00:03:20.760 --> 00:03:22.190 align:start position:0% functions to like the um yeah event handling<00:03:21.120> on<00:03:21.239> the<00:03:21.360> client<00:03:21.599> you<00:03:21.959> have<00:03:22.080> to 00:03:22.190 --> 00:03:22.200 align:start position:0% handling on the client you have to 00:03:22.200 --> 00:03:23.750 align:start position:0% handling on the client you have to modify<00:03:22.560> everything 00:03:23.750 --> 00:03:23.760 align:start position:0% modify everything 00:03:23.760 --> 00:03:25.490 align:start position:0% modify everything and<00:03:24.060> then<00:03:24.180> on<00:03:24.420> the<00:03:24.540> interoperability<00:03:25.080> side 00:03:25.490 --> 00:03:25.500 align:start position:0% and then on the interoperability side 00:03:25.500 --> 00:03:27.589 align:start position:0% and then on the interoperability side basically<00:03:26.340> all<00:03:26.580> you<00:03:26.700> have<00:03:26.879> are<00:03:27.180> existing 00:03:27.589 --> 00:03:27.599 align:start position:0% basically all you have are existing 00:03:27.599 --> 00:03:31.309 align:start position:0% basically all you have are existing interfaces<00:03:28.140> like<00:03:28.319> erc20<00:03:28.980> erc721<00:03:30.300> Etc<00:03:30.480> which 00:03:31.309 --> 00:03:31.319 align:start position:0% interfaces like erc20 erc721 Etc which 00:03:31.319 --> 00:03:33.229 align:start position:0% interfaces like erc20 erc721 Etc which were<00:03:31.620> not<00:03:31.800> built<00:03:32.040> for<00:03:32.099> unchain<00:03:32.459> games<00:03:32.700> and<00:03:33.000> are 00:03:33.229 --> 00:03:33.239 align:start position:0% were not built for unchain games and are 00:03:33.239 --> 00:03:34.850 align:start position:0% were not built for unchain games and are very<00:03:33.480> limited<00:03:33.780> in<00:03:33.959> what<00:03:34.379> they<00:03:34.500> can<00:03:34.680> express 00:03:34.850 --> 00:03:34.860 align:start position:0% very limited in what they can express 00:03:34.860 --> 00:03:37.850 align:start position:0% very limited in what they can express right 00:03:37.850 --> 00:03:37.860 align:start position:0% 00:03:37.860 --> 00:03:40.430 align:start position:0% so<00:03:38.400> our<00:03:38.580> goal<00:03:38.879> with<00:03:39.000> mud<00:03:39.300> is<00:03:39.659> to<00:03:39.900> solve<00:03:40.140> all<00:03:40.319> of 00:03:40.430 --> 00:03:40.440 align:start position:0% so our goal with mud is to solve all of 00:03:40.440 --> 00:03:42.050 align:start position:0% so our goal with mud is to solve all of these<00:03:40.620> like<00:03:40.799> General<00:03:40.980> problems<00:03:41.519> so<00:03:41.700> that<00:03:41.879> you 00:03:42.050 --> 00:03:42.060 align:start position:0% these like General problems so that you 00:03:42.060 --> 00:03:43.850 align:start position:0% these like General problems so that you as<00:03:42.299> game<00:03:42.599> developers<00:03:43.080> launching<00:03:43.680> game 00:03:43.850 --> 00:03:43.860 align:start position:0% as game developers launching game 00:03:43.860 --> 00:03:46.130 align:start position:0% as game developers launching game developers<00:03:44.340> can<00:03:44.760> just<00:03:44.940> focus<00:03:45.180> on<00:03:45.360> making<00:03:45.599> a 00:03:46.130 --> 00:03:46.140 align:start position:0% developers can just focus on making a 00:03:46.140 --> 00:03:48.470 align:start position:0% developers can just focus on making a fun<00:03:46.319> game 00:03:48.470 --> 00:03:48.480 align:start position:0% fun game 00:03:48.480 --> 00:03:50.630 align:start position:0% fun game all<00:03:48.900> right<00:03:48.959> so<00:03:49.260> this<00:03:49.560> is<00:03:49.680> for<00:03:49.860> the<00:03:50.040> Y<00:03:50.220> and<00:03:50.519> now 00:03:50.630 --> 00:03:50.640 align:start position:0% all right so this is for the Y and now 00:03:50.640 --> 00:03:51.949 align:start position:0% all right so this is for the Y and now let's<00:03:50.760> go<00:03:50.940> into<00:03:51.000> the<00:03:51.239> how<00:03:51.360> how<00:03:51.599> does<00:03:51.780> Matt 00:03:51.949 --> 00:03:51.959 align:start position:0% let's go into the how how does Matt 00:03:51.959 --> 00:03:53.509 align:start position:0% let's go into the how how does Matt solve<00:03:52.260> these<00:03:52.440> problems 00:03:53.509 --> 00:03:53.519 align:start position:0% solve these problems 00:03:53.519 --> 00:03:55.850 align:start position:0% solve these problems um<00:03:53.640> mud<00:03:54.120> is<00:03:54.239> built<00:03:54.540> around<00:03:54.720> an<00:03:55.319> architecture 00:03:55.850 --> 00:03:55.860 align:start position:0% um mud is built around an architecture 00:03:55.860 --> 00:03:57.649 align:start position:0% um mud is built around an architecture pattern<00:03:56.159> called<00:03:56.400> entity<00:03:56.879> component<00:03:57.420> system 00:03:57.649 --> 00:03:57.659 align:start position:0% pattern called entity component system 00:03:57.659 --> 00:04:00.229 align:start position:0% pattern called entity component system this<00:03:58.080> is<00:03:58.200> a<00:03:58.440> very<00:03:58.560> popular<00:03:58.799> pattern<00:03:59.400> in<00:04:00.060> the 00:04:00.229 --> 00:04:00.239 align:start position:0% this is a very popular pattern in the 00:04:00.239 --> 00:04:01.970 align:start position:0% this is a very popular pattern in the traditional<00:04:00.599> gaming<00:04:00.900> industry<00:04:01.260> for<00:04:01.620> a<00:04:01.860> reason 00:04:01.970 --> 00:04:01.980 align:start position:0% traditional gaming industry for a reason 00:04:01.980 --> 00:04:04.009 align:start position:0% traditional gaming industry for a reason but<00:04:02.760> if<00:04:02.879> you're<00:04:03.060> not<00:04:03.180> familiar<00:04:03.480> with<00:04:03.599> it<00:04:03.720> I'm 00:04:04.009 --> 00:04:04.019 align:start position:0% but if you're not familiar with it I'm 00:04:04.019 --> 00:04:06.229 align:start position:0% but if you're not familiar with it I'm gonna<00:04:04.140> give<00:04:04.560> you<00:04:04.739> a<00:04:04.920> brief<00:04:05.340> crash<00:04:05.879> course<00:04:06.000> on 00:04:06.229 --> 00:04:06.239 align:start position:0% gonna give you a brief crash course on 00:04:06.239 --> 00:04:07.850 align:start position:0% gonna give you a brief crash course on ECS 00:04:07.850 --> 00:04:07.860 align:start position:0% ECS 00:04:07.860 --> 00:04:11.509 align:start position:0% ECS in<00:04:08.340> ECS<00:04:08.819> an<00:04:09.060> entity<00:04:09.360> is<00:04:10.140> just<00:04:10.319> a<00:04:10.560> numeric<00:04:11.099> ID<00:04:11.220> so 00:04:11.509 --> 00:04:11.519 align:start position:0% in ECS an entity is just a numeric ID so 00:04:11.519 --> 00:04:14.330 align:start position:0% in ECS an entity is just a numeric ID so in<00:04:11.640> our<00:04:11.819> case<00:04:12.000> it's<00:04:12.180> just<00:04:12.299> a<00:04:12.480> un256<00:04:13.260> and<00:04:14.159> then 00:04:14.330 --> 00:04:14.340 align:start position:0% in our case it's just a un256 and then 00:04:14.340 --> 00:04:16.189 align:start position:0% in our case it's just a un256 and then you<00:04:14.640> have<00:04:14.819> components 00:04:16.189 --> 00:04:16.199 align:start position:0% you have components 00:04:16.199 --> 00:04:18.530 align:start position:0% you have components you<00:04:16.560> have<00:04:16.680> components<00:04:17.220> oops<00:04:17.880> you<00:04:18.359> have 00:04:18.530 --> 00:04:18.540 align:start position:0% you have components oops you have 00:04:18.540 --> 00:04:20.810 align:start position:0% you have components oops you have components<00:04:19.139> that<00:04:19.739> store<00:04:20.040> the<00:04:20.220> data<00:04:20.459> for<00:04:20.639> this 00:04:20.810 --> 00:04:20.820 align:start position:0% components that store the data for this 00:04:20.820 --> 00:04:23.270 align:start position:0% components that store the data for this entity<00:04:21.060> so<00:04:21.900> in<00:04:22.019> our<00:04:22.199> case<00:04:22.380> we<00:04:22.919> could<00:04:23.040> have<00:04:23.160> a 00:04:23.270 --> 00:04:23.280 align:start position:0% entity so in our case we could have a 00:04:23.280 --> 00:04:25.550 align:start position:0% entity so in our case we could have a component<00:04:23.639> that<00:04:23.820> stores<00:04:24.000> the<00:04:24.600> data<00:04:24.900> like<00:04:25.199> you 00:04:25.550 --> 00:04:25.560 align:start position:0% component that stores the data like you 00:04:25.560 --> 00:04:27.170 align:start position:0% component that stores the data like you can<00:04:25.680> think<00:04:25.740> of<00:04:25.860> it<00:04:26.040> as<00:04:26.220> a<00:04:26.340> as<00:04:26.520> a<00:04:26.699> mapping<00:04:26.940> from 00:04:27.170 --> 00:04:27.180 align:start position:0% can think of it as a as a mapping from 00:04:27.180 --> 00:04:29.270 align:start position:0% can think of it as a as a mapping from The<00:04:27.300> Entity<00:04:27.600> ID<00:04:27.840> to<00:04:28.320> the<00:04:28.500> component<00:04:28.860> value<00:04:29.040> you 00:04:29.270 --> 00:04:29.280 align:start position:0% The Entity ID to the component value you 00:04:29.280 --> 00:04:31.129 align:start position:0% The Entity ID to the component value you can<00:04:29.400> think<00:04:29.520> of<00:04:29.639> it<00:04:29.759> as<00:04:29.940> a<00:04:30.120> as<00:04:30.300> a<00:04:30.479> fancy<00:04:30.840> like 00:04:31.129 --> 00:04:31.139 align:start position:0% can think of it as a as a fancy like 00:04:31.139 --> 00:04:33.290 align:start position:0% can think of it as a as a fancy like standard<00:04:31.620> ethereum<00:04:32.040> mapping 00:04:33.290 --> 00:04:33.300 align:start position:0% standard ethereum mapping 00:04:33.300 --> 00:04:35.390 align:start position:0% standard ethereum mapping and<00:04:33.780> then<00:04:33.900> you<00:04:34.080> have<00:04:34.199> the<00:04:34.380> systems<00:04:34.860> which 00:04:35.390 --> 00:04:35.400 align:start position:0% and then you have the systems which 00:04:35.400 --> 00:04:37.070 align:start position:0% and then you have the systems which implement<00:04:35.759> the<00:04:35.880> logic<00:04:36.240> so<00:04:36.419> components<00:04:36.960> are 00:04:37.070 --> 00:04:37.080 align:start position:0% implement the logic so components are 00:04:37.080 --> 00:04:38.870 align:start position:0% implement the logic so components are only<00:04:37.199> Data<00:04:37.620> Systems<00:04:38.100> implement<00:04:38.400> the<00:04:38.580> logic 00:04:38.870 --> 00:04:38.880 align:start position:0% only Data Systems implement the logic 00:04:38.880 --> 00:04:41.450 align:start position:0% only Data Systems implement the logic and<00:04:39.540> systems<00:04:39.960> don't<00:04:40.199> act<00:04:40.440> on<00:04:40.740> specific<00:04:41.040> entity 00:04:41.450 --> 00:04:41.460 align:start position:0% and systems don't act on specific entity 00:04:41.460 --> 00:04:43.010 align:start position:0% and systems don't act on specific entity types<00:04:41.880> because<00:04:42.060> there<00:04:42.419> are<00:04:42.540> no<00:04:42.720> specific 00:04:43.010 --> 00:04:43.020 align:start position:0% types because there are no specific 00:04:43.020 --> 00:04:45.469 align:start position:0% types because there are no specific entity<00:04:43.380> types<00:04:43.740> in<00:04:43.860> ECS<00:04:44.340> but<00:04:44.759> rather<00:04:45.000> an<00:04:45.180> entity 00:04:45.469 --> 00:04:45.479 align:start position:0% entity types in ECS but rather an entity 00:04:45.479 --> 00:04:48.050 align:start position:0% entity types in ECS but rather an entity is<00:04:45.840> just<00:04:46.139> the<00:04:46.560> collection<00:04:46.919> of<00:04:47.340> components 00:04:48.050 --> 00:04:48.060 align:start position:0% is just the collection of components 00:04:48.060 --> 00:04:50.510 align:start position:0% is just the collection of components that<00:04:48.360> are<00:04:48.600> attached<00:04:48.960> to<00:04:49.080> it<00:04:49.259> basically<00:04:49.620> and<00:04:50.400> so 00:04:50.510 --> 00:04:50.520 align:start position:0% that are attached to it basically and so 00:04:50.520 --> 00:04:52.550 align:start position:0% that are attached to it basically and so your<00:04:50.699> move<00:04:51.000> system<00:04:51.240> as<00:04:51.540> an<00:04:51.720> example<00:04:52.020> doesn't 00:04:52.550 --> 00:04:52.560 align:start position:0% your move system as an example doesn't 00:04:52.560 --> 00:04:54.590 align:start position:0% your move system as an example doesn't care<00:04:52.800> about<00:04:52.919> whether<00:04:53.220> it's<00:04:53.460> moving<00:04:53.880> a<00:04:54.180> donkey 00:04:54.590 --> 00:04:54.600 align:start position:0% care about whether it's moving a donkey 00:04:54.600 --> 00:04:56.570 align:start position:0% care about whether it's moving a donkey or<00:04:54.900> a<00:04:55.020> dog<00:04:55.139> it<00:04:55.440> only<00:04:55.560> cares<00:04:55.860> about<00:04:56.040> whether 00:04:56.570 --> 00:04:56.580 align:start position:0% or a dog it only cares about whether 00:04:56.580 --> 00:04:58.610 align:start position:0% or a dog it only cares about whether this<00:04:56.880> entity<00:04:57.180> that<00:04:57.419> it<00:04:57.600> is<00:04:57.720> moving<00:04:57.960> has<00:04:58.440> a 00:04:58.610 --> 00:04:58.620 align:start position:0% this entity that it is moving has a 00:04:58.620 --> 00:05:00.110 align:start position:0% this entity that it is moving has a position<00:04:58.800> component<00:04:59.340> attached<00:04:59.759> to<00:04:59.820> it<00:05:00.000> and 00:05:00.110 --> 00:05:00.120 align:start position:0% position component attached to it and 00:05:00.120 --> 00:05:01.430 align:start position:0% position component attached to it and then<00:05:00.240> it<00:05:00.360> can<00:05:00.479> modify<00:05:00.840> that<00:05:01.020> position 00:05:01.430 --> 00:05:01.440 align:start position:0% then it can modify that position 00:05:01.440 --> 00:05:03.290 align:start position:0% then it can modify that position component 00:05:03.290 --> 00:05:03.300 align:start position:0% component 00:05:03.300 --> 00:05:04.969 align:start position:0% component and<00:05:03.780> if<00:05:03.900> you<00:05:04.080> think<00:05:04.199> about<00:05:04.320> it<00:05:04.560> that's 00:05:04.969 --> 00:05:04.979 align:start position:0% and if you think about it that's 00:05:04.979 --> 00:05:07.310 align:start position:0% and if you think about it that's actually<00:05:05.220> in<00:05:05.580> a<00:05:05.759> way<00:05:05.880> how<00:05:06.240> ethereum<00:05:06.780> already 00:05:07.310 --> 00:05:07.320 align:start position:0% actually in a way how ethereum already 00:05:07.320 --> 00:05:09.710 align:start position:0% actually in a way how ethereum already works<00:05:07.860> today<00:05:08.280> you<00:05:08.820> can<00:05:08.880> think<00:05:09.000> of<00:05:09.180> addresses 00:05:09.710 --> 00:05:09.720 align:start position:0% works today you can think of addresses 00:05:09.720 --> 00:05:12.469 align:start position:0% works today you can think of addresses as<00:05:10.139> entities<00:05:10.560> and<00:05:11.400> then<00:05:11.580> a<00:05:11.820> token<00:05:12.180> contract 00:05:12.469 --> 00:05:12.479 align:start position:0% as entities and then a token contract 00:05:12.479 --> 00:05:16.010 align:start position:0% as entities and then a token contract like<00:05:12.720> a<00:05:12.960> year<00:05:13.259> c721<00:05:14.220> token<00:05:14.759> contract<00:05:15.060> can<00:05:15.720> be 00:05:16.010 --> 00:05:16.020 align:start position:0% like a year c721 token contract can be 00:05:16.020 --> 00:05:17.689 align:start position:0% like a year c721 token contract can be thought<00:05:16.139> of<00:05:16.320> as<00:05:16.560> a<00:05:16.740> component<00:05:17.100> and<00:05:17.400> a<00:05:17.520> system 00:05:17.689 --> 00:05:17.699 align:start position:0% thought of as a component and a system 00:05:17.699 --> 00:05:19.730 align:start position:0% thought of as a component and a system mixed<00:05:18.180> together<00:05:18.300> and<00:05:19.020> attached<00:05:19.380> to<00:05:19.500> this 00:05:19.730 --> 00:05:19.740 align:start position:0% mixed together and attached to this 00:05:19.740 --> 00:05:22.070 align:start position:0% mixed together and attached to this entity<00:05:20.100> to<00:05:20.580> this<00:05:20.759> address<00:05:20.940> and<00:05:21.600> if<00:05:21.900> you<00:05:21.960> wanted 00:05:22.070 --> 00:05:22.080 align:start position:0% entity to this address and if you wanted 00:05:22.080 --> 00:05:24.529 align:start position:0% entity to this address and if you wanted to<00:05:22.320> model<00:05:22.440> this<00:05:22.680> in<00:05:22.860> like<00:05:23.039> pure<00:05:23.280> ECS<00:05:23.880> then<00:05:24.360> you 00:05:24.529 --> 00:05:24.539 align:start position:0% to model this in like pure ECS then you 00:05:24.539 --> 00:05:25.969 align:start position:0% to model this in like pure ECS then you would<00:05:24.660> just<00:05:24.840> have<00:05:25.020> a<00:05:25.259> balanced<00:05:25.620> component 00:05:25.969 --> 00:05:25.979 align:start position:0% would just have a balanced component 00:05:25.979 --> 00:05:28.070 align:start position:0% would just have a balanced component that<00:05:26.220> stores<00:05:26.400> the<00:05:26.699> data<00:05:27.000> and<00:05:27.419> then<00:05:27.539> a<00:05:27.720> transfer 00:05:28.070 --> 00:05:28.080 align:start position:0% that stores the data and then a transfer 00:05:28.080 --> 00:05:29.510 align:start position:0% that stores the data and then a transfer system<00:05:28.259> that<00:05:28.560> implements<00:05:28.979> the<00:05:29.039> logic<00:05:29.340> of 00:05:29.510 --> 00:05:29.520 align:start position:0% system that implements the logic of 00:05:29.520 --> 00:05:32.570 align:start position:0% system that implements the logic of transferring<00:05:30.240> stuff 00:05:32.570 --> 00:05:32.580 align:start position:0% 00:05:32.580 --> 00:05:34.969 align:start position:0% all<00:05:33.000> right<00:05:33.120> so<00:05:33.300> with<00:05:33.479> ECS<00:05:33.960> in<00:05:34.139> mind<00:05:34.320> how<00:05:34.800> does 00:05:34.969 --> 00:05:34.979 align:start position:0% all right so with ECS in mind how does 00:05:34.979 --> 00:05:37.850 align:start position:0% all right so with ECS in mind how does much<00:05:35.160> handle<00:05:35.580> the<00:05:35.940> state<00:05:36.180> sync<00:05:36.660> in<00:05:37.199> Mata<00:05:37.560> is<00:05:37.680> a 00:05:37.850 --> 00:05:37.860 align:start position:0% much handle the state sync in Mata is a 00:05:37.860 --> 00:05:39.529 align:start position:0% much handle the state sync in Mata is a very<00:05:37.919> Central<00:05:38.100> contract<00:05:38.580> the<00:05:38.880> world<00:05:39.060> contract 00:05:39.529 --> 00:05:39.539 align:start position:0% very Central contract the world contract 00:05:39.539 --> 00:05:41.810 align:start position:0% very Central contract the world contract and<00:05:40.139> every<00:05:40.259> time<00:05:40.500> you<00:05:40.680> add<00:05:40.800> a<00:05:40.979> contract<00:05:41.340> and 00:05:41.810 --> 00:05:41.820 align:start position:0% and every time you add a contract and 00:05:41.820 --> 00:05:43.550 align:start position:0% and every time you add a contract and every<00:05:42.180> time<00:05:42.360> you<00:05:42.479> add<00:05:42.600> a<00:05:42.780> component<00:05:43.139> which<00:05:43.440> is 00:05:43.550 --> 00:05:43.560 align:start position:0% every time you add a component which is 00:05:43.560 --> 00:05:46.070 align:start position:0% every time you add a component which is also<00:05:43.800> a<00:05:43.919> contract<00:05:44.280> it<00:05:45.180> gets<00:05:45.479> registered<00:05:45.900> on 00:05:46.070 --> 00:05:46.080 align:start position:0% also a contract it gets registered on 00:05:46.080 --> 00:05:47.990 align:start position:0% also a contract it gets registered on the<00:05:46.139> world<00:05:46.259> contract<00:05:46.740> and<00:05:47.460> then<00:05:47.580> every<00:05:47.759> time 00:05:47.990 --> 00:05:48.000 align:start position:0% the world contract and then every time 00:05:48.000 --> 00:05:49.790 align:start position:0% the world contract and then every time that<00:05:48.180> component<00:05:48.539> gets<00:05:48.840> updated<00:05:49.080> an<00:05:49.380> event<00:05:49.560> is 00:05:49.790 --> 00:05:49.800 align:start position:0% that component gets updated an event is 00:05:49.800 --> 00:05:51.409 align:start position:0% that component gets updated an event is emitted<00:05:50.220> automatically<00:05:50.759> through<00:05:51.120> the<00:05:51.300> world 00:05:51.409 --> 00:05:51.419 align:start position:0% emitted automatically through the world 00:05:51.419 --> 00:05:54.170 align:start position:0% emitted automatically through the world contract<00:05:51.960> that<00:05:52.680> means<00:05:52.979> the<00:05:53.400> client<00:05:53.639> only<00:05:53.940> has 00:05:54.170 --> 00:05:54.180 align:start position:0% contract that means the client only has 00:05:54.180 --> 00:05:55.850 align:start position:0% contract that means the client only has to<00:05:54.300> listen<00:05:54.479> to<00:05:54.660> this<00:05:54.900> one<00:05:55.080> Central<00:05:55.320> stream<00:05:55.680> of 00:05:55.850 --> 00:05:55.860 align:start position:0% to listen to this one Central stream of 00:05:55.860 --> 00:05:57.350 align:start position:0% to listen to this one Central stream of events<00:05:56.220> coming<00:05:56.400> from<00:05:56.639> the<00:05:56.759> world<00:05:56.880> contract 00:05:57.350 --> 00:05:57.360 align:start position:0% events coming from the world contract 00:05:57.360 --> 00:05:59.870 align:start position:0% events coming from the world contract and<00:05:57.960> can<00:05:58.139> then<00:05:58.380> like<00:05:58.860> keep<00:05:59.160> the<00:05:59.460> local<00:05:59.639> state 00:05:59.870 --> 00:05:59.880 align:start position:0% and can then like keep the local state 00:05:59.880 --> 00:06:01.670 align:start position:0% and can then like keep the local state in<00:06:00.120> sync<00:06:00.419> basically 00:06:01.670 --> 00:06:01.680 align:start position:0% in sync basically 00:06:01.680 --> 00:06:03.350 align:start position:0% in sync basically and<00:06:02.160> the<00:06:02.280> great<00:06:02.400> thing<00:06:02.520> is<00:06:02.639> with<00:06:02.820> mud<00:06:03.060> you 00:06:03.350 --> 00:06:03.360 align:start position:0% and the great thing is with mud you 00:06:03.360 --> 00:06:05.029 align:start position:0% and the great thing is with mud you don't<00:06:03.479> have<00:06:03.539> to<00:06:03.720> worry<00:06:03.960> about<00:06:04.440> any<00:06:04.740> of<00:06:04.919> that 00:06:05.029 --> 00:06:05.039 align:start position:0% don't have to worry about any of that 00:06:05.039 --> 00:06:07.610 align:start position:0% don't have to worry about any of that because<00:06:05.639> mud<00:06:06.600> handles<00:06:06.840> all<00:06:07.020> of<00:06:07.139> that<00:06:07.259> for<00:06:07.440> you 00:06:07.610 --> 00:06:07.620 align:start position:0% because mud handles all of that for you 00:06:07.620 --> 00:06:09.290 align:start position:0% because mud handles all of that for you what<00:06:08.100> you<00:06:08.220> do<00:06:08.340> what<00:06:08.580> you<00:06:08.699> have<00:06:08.820> to<00:06:08.880> do<00:06:09.000> as<00:06:09.120> a 00:06:09.290 --> 00:06:09.300 align:start position:0% what you do what you have to do as a 00:06:09.300 --> 00:06:10.909 align:start position:0% what you do what you have to do as a game<00:06:09.360> developer<00:06:09.840> is<00:06:10.320> just<00:06:10.500> create<00:06:10.680> a 00:06:10.909 --> 00:06:10.919 align:start position:0% game developer is just create a 00:06:10.919 --> 00:06:12.890 align:start position:0% game developer is just create a component<00:06:11.340> contract 00:06:12.890 --> 00:06:12.900 align:start position:0% component contract 00:06:12.900 --> 00:06:14.510 align:start position:0% component contract um<00:06:12.960> give<00:06:13.139> it<00:06:13.259> some<00:06:13.440> ID<00:06:13.620> and<00:06:13.979> then<00:06:14.100> create<00:06:14.340> a 00:06:14.510 --> 00:06:14.520 align:start position:0% um give it some ID and then create a 00:06:14.520 --> 00:06:15.950 align:start position:0% um give it some ID and then create a component<00:06:14.880> on<00:06:15.060> the<00:06:15.180> client<00:06:15.360> and<00:06:15.539> give<00:06:15.720> it<00:06:15.840> the 00:06:15.950 --> 00:06:15.960 align:start position:0% component on the client and give it the 00:06:15.960 --> 00:06:18.290 align:start position:0% component on the client and give it the same<00:06:16.080> ID<00:06:16.320> and<00:06:16.919> mut<00:06:17.160> handles<00:06:17.520> the<00:06:17.699> state<00:06:17.880> sync 00:06:18.290 --> 00:06:18.300 align:start position:0% same ID and mut handles the state sync 00:06:18.300 --> 00:06:21.230 align:start position:0% same ID and mut handles the state sync automatically 00:06:21.230 --> 00:06:21.240 align:start position:0% 00:06:21.240 --> 00:06:22.610 align:start position:0% and<00:06:21.600> the<00:06:21.720> great<00:06:21.900> thing<00:06:22.020> with<00:06:22.259> this<00:06:22.440> General 00:06:22.610 --> 00:06:22.620 align:start position:0% and the great thing with this General 00:06:22.620 --> 00:06:24.230 align:start position:0% and the great thing with this General approach<00:06:23.100> is<00:06:23.220> also<00:06:23.460> that<00:06:23.580> we<00:06:23.759> can<00:06:23.880> provide 00:06:24.230 --> 00:06:24.240 align:start position:0% approach is also that we can provide 00:06:24.240 --> 00:06:26.629 align:start position:0% approach is also that we can provide generic<00:06:24.960> indexes<00:06:25.560> that<00:06:25.919> help<00:06:26.220> your<00:06:26.400> client 00:06:26.629 --> 00:06:26.639 align:start position:0% generic indexes that help your client 00:06:26.639 --> 00:06:29.330 align:start position:0% generic indexes that help your client catch<00:06:27.000> up<00:06:27.120> faster<00:06:27.900> and<00:06:28.380> reduce<00:06:28.680> their<00:06:28.919> RPC 00:06:29.330 --> 00:06:29.340 align:start position:0% catch up faster and reduce their RPC 00:06:29.340 --> 00:06:30.830 align:start position:0% catch up faster and reduce their RPC load<00:06:29.639> and<00:06:30.060> you<00:06:30.120> don't<00:06:30.240> have<00:06:30.360> to<00:06:30.479> write<00:06:30.600> any 00:06:30.830 --> 00:06:30.840 align:start position:0% load and you don't have to write any 00:06:30.840 --> 00:06:32.689 align:start position:0% load and you don't have to write any like<00:06:31.080> custom<00:06:31.319> sub<00:06:31.680> graphs<00:06:32.160> because<00:06:32.280> all<00:06:32.580> the 00:06:32.689 --> 00:06:32.699 align:start position:0% like custom sub graphs because all the 00:06:32.699 --> 00:06:35.450 align:start position:0% like custom sub graphs because all the data<00:06:33.000> is<00:06:33.180> stored<00:06:33.539> in<00:06:33.720> a<00:06:33.840> very<00:06:33.960> generic<00:06:34.319> way 00:06:35.450 --> 00:06:35.460 align:start position:0% data is stored in a very generic way 00:06:35.460 --> 00:06:40.550 align:start position:0% data is stored in a very generic way um<00:06:35.880> and<00:06:36.360> that's<00:06:36.479> why<00:06:36.660> we<00:06:36.780> can<00:06:36.900> have<00:06:36.960> indexes 00:06:40.550 --> 00:06:40.560 align:start position:0% 00:06:40.560 --> 00:06:42.650 align:start position:0% cool<00:06:40.979> now<00:06:41.280> to<00:06:41.460> the<00:06:41.580> fun<00:06:41.699> part<00:06:41.880> of<00:06:42.060> adding 00:06:42.650 --> 00:06:42.660 align:start position:0% cool now to the fun part of adding 00:06:42.660 --> 00:06:45.290 align:start position:0% cool now to the fun part of adding content<00:06:43.020> as<00:06:43.620> a<00:06:43.860> quick<00:06:43.979> reminder<00:06:44.160> in<00:06:44.699> ECS 00:06:45.290 --> 00:06:45.300 align:start position:0% content as a quick reminder in ECS 00:06:45.300 --> 00:06:47.330 align:start position:0% content as a quick reminder in ECS entities<00:06:45.780> are<00:06:46.560> just<00:06:46.740> a<00:06:46.860> collection<00:06:47.160> of 00:06:47.330 --> 00:06:47.340 align:start position:0% entities are just a collection of 00:06:47.340 --> 00:06:49.850 align:start position:0% entities are just a collection of components<00:06:47.880> so<00:06:48.120> our<00:06:48.360> fighter<00:06:48.840> entity<00:06:49.080> here<00:06:49.319> is 00:06:49.850 --> 00:06:49.860 align:start position:0% components so our fighter entity here is 00:06:49.860 --> 00:06:51.710 align:start position:0% components so our fighter entity here is actually<00:06:50.039> just<00:06:50.340> a<00:06:50.520> collection<00:06:50.880> of<00:06:51.240> a<00:06:51.539> health 00:06:51.710 --> 00:06:51.720 align:start position:0% actually just a collection of a health 00:06:51.720 --> 00:06:53.270 align:start position:0% actually just a collection of a health component<00:06:52.139> and<00:06:52.319> attack<00:06:52.440> component<00:06:52.979> and<00:06:53.160> a 00:06:53.270 --> 00:06:53.280 align:start position:0% component and attack component and a 00:06:53.280 --> 00:06:55.490 align:start position:0% component and attack component and a movable<00:06:53.639> component<00:06:54.180> and<00:06:54.780> now<00:06:54.900> if<00:06:55.080> we<00:06:55.259> want<00:06:55.380> to 00:06:55.490 --> 00:06:55.500 align:start position:0% movable component and now if we want to 00:06:55.500 --> 00:06:57.350 align:start position:0% movable component and now if we want to add<00:06:55.680> more<00:06:56.100> entities<00:06:56.400> or<00:06:56.699> stronger<00:06:57.120> entities 00:06:57.350 --> 00:06:57.360 align:start position:0% add more entities or stronger entities 00:06:57.360 --> 00:07:00.230 align:start position:0% add more entities or stronger entities like<00:06:57.660> a<00:06:57.840> dragon<00:06:58.020> then<00:06:58.740> we<00:06:59.039> can<00:06:59.340> just<00:06:59.520> modify 00:07:00.230 --> 00:07:00.240 align:start position:0% like a dragon then we can just modify 00:07:00.240 --> 00:07:01.550 align:start position:0% like a dragon then we can just modify those<00:07:00.419> component<00:07:00.840> values<00:07:01.080> give<00:07:01.259> it<00:07:01.380> more 00:07:01.550 --> 00:07:01.560 align:start position:0% those component values give it more 00:07:01.560 --> 00:07:03.110 align:start position:0% those component values give it more Health<00:07:01.680> give<00:07:01.919> it<00:07:02.039> more<00:07:02.220> attack<00:07:02.340> and<00:07:02.819> suddenly 00:07:03.110 --> 00:07:03.120 align:start position:0% Health give it more attack and suddenly 00:07:03.120 --> 00:07:05.150 align:start position:0% Health give it more attack and suddenly we<00:07:03.240> have<00:07:03.360> a<00:07:03.479> dragon<00:07:03.660> another<00:07:04.440> way<00:07:04.680> to<00:07:04.860> add<00:07:05.039> more 00:07:05.150 --> 00:07:05.160 align:start position:0% we have a dragon another way to add more 00:07:05.160 --> 00:07:07.370 align:start position:0% we have a dragon another way to add more content<00:07:05.520> is<00:07:05.699> to<00:07:06.000> modify<00:07:06.360> or<00:07:06.600> like<00:07:06.840> recombine 00:07:07.370 --> 00:07:07.380 align:start position:0% content is to modify or like recombine 00:07:07.380 --> 00:07:09.830 align:start position:0% content is to modify or like recombine existing<00:07:07.860> components<00:07:08.400> together<00:07:09.000> for<00:07:09.600> example 00:07:09.830 --> 00:07:09.840 align:start position:0% existing components together for example 00:07:09.840 --> 00:07:11.990 align:start position:0% existing components together for example remove<00:07:10.380> the<00:07:10.620> movable<00:07:10.919> component<00:07:11.460> and 00:07:11.990 --> 00:07:12.000 align:start position:0% remove the movable component and 00:07:12.000 --> 00:07:14.450 align:start position:0% remove the movable component and suddenly<00:07:12.240> you<00:07:12.479> have<00:07:12.539> a<00:07:12.720> defense<00:07:12.960> tower 00:07:14.450 --> 00:07:14.460 align:start position:0% suddenly you have a defense tower 00:07:14.460 --> 00:07:16.070 align:start position:0% suddenly you have a defense tower and<00:07:15.000> the<00:07:15.120> last<00:07:15.240> way<00:07:15.419> of<00:07:15.539> adding<00:07:15.780> Quantum 00:07:16.070 --> 00:07:16.080 align:start position:0% and the last way of adding Quantum 00:07:16.080 --> 00:07:19.129 align:start position:0% and the last way of adding Quantum content<00:07:16.860> is<00:07:17.520> adding<00:07:17.819> new<00:07:18.000> components<00:07:18.539> every 00:07:19.129 --> 00:07:19.139 align:start position:0% content is adding new components every 00:07:19.139 --> 00:07:21.290 align:start position:0% content is adding new components every time<00:07:19.319> you<00:07:19.500> add<00:07:19.620> a<00:07:19.800> new<00:07:19.860> component<00:07:20.340> the<00:07:21.120> number 00:07:21.290 --> 00:07:21.300 align:start position:0% time you add a new component the number 00:07:21.300 --> 00:07:23.689 align:start position:0% time you add a new component the number of<00:07:21.479> possibilities<00:07:22.199> of<00:07:22.919> combining<00:07:23.580> your 00:07:23.689 --> 00:07:23.699 align:start position:0% of possibilities of combining your 00:07:23.699 --> 00:07:26.150 align:start position:0% of possibilities of combining your components<00:07:24.240> actually<00:07:24.419> doubles<00:07:24.900> so<00:07:25.680> you<00:07:26.039> can 00:07:26.150 --> 00:07:26.160 align:start position:0% components actually doubles so you can 00:07:26.160 --> 00:07:27.830 align:start position:0% components actually doubles so you can just<00:07:26.340> recombine<00:07:26.940> your<00:07:27.120> components<00:07:27.479> in<00:07:27.599> a<00:07:27.780> new 00:07:27.830 --> 00:07:27.840 align:start position:0% just recombine your components in a new 00:07:27.840 --> 00:07:28.969 align:start position:0% just recombine your components in a new way<00:07:28.020> you<00:07:28.199> have<00:07:28.319> double<00:07:28.500> the<00:07:28.740> amount<00:07:28.919> of 00:07:28.969 --> 00:07:28.979 align:start position:0% way you have double the amount of 00:07:28.979 --> 00:07:31.430 align:start position:0% way you have double the amount of entities<00:07:29.220> you<00:07:29.460> can<00:07:29.580> now<00:07:29.699> represent<00:07:30.259> as<00:07:31.259> an 00:07:31.430 --> 00:07:31.440 align:start position:0% entities you can now represent as an 00:07:31.440 --> 00:07:33.409 align:start position:0% entities you can now represent as an example<00:07:31.680> you<00:07:32.039> add<00:07:32.160> a<00:07:32.280> healing<00:07:32.580> component<00:07:33.000> now 00:07:33.409 --> 00:07:33.419 align:start position:0% example you add a healing component now 00:07:33.419 --> 00:07:35.450 align:start position:0% example you add a healing component now you<00:07:33.660> can<00:07:33.780> build<00:07:34.199> a<00:07:34.440> healing<00:07:34.680> Shrine<00:07:34.979> A<00:07:35.099> Healer 00:07:35.450 --> 00:07:35.460 align:start position:0% you can build a healing Shrine A Healer 00:07:35.460 --> 00:07:37.309 align:start position:0% you can build a healing Shrine A Healer and<00:07:35.580> a<00:07:35.699> healing<00:07:35.940> potion<00:07:36.240> without<00:07:36.780> changing 00:07:37.309 --> 00:07:37.319 align:start position:0% and a healing potion without changing 00:07:37.319 --> 00:07:40.969 align:start position:0% and a healing potion without changing any<00:07:37.560> of<00:07:37.740> the<00:07:37.979> existing<00:07:38.400> logic 00:07:40.969 --> 00:07:40.979 align:start position:0% 00:07:40.979 --> 00:07:42.110 align:start position:0% and<00:07:41.460> then<00:07:41.580> when<00:07:41.759> it<00:07:41.880> comes<00:07:42.000> to 00:07:42.110 --> 00:07:42.120 align:start position:0% and then when it comes to 00:07:42.120 --> 00:07:44.570 align:start position:0% and then when it comes to interoperability<00:07:42.860> in<00:07:43.860> theory<00:07:44.160> everything 00:07:44.570 --> 00:07:44.580 align:start position:0% interoperability in theory everything 00:07:44.580 --> 00:07:46.249 align:start position:0% interoperability in theory everything that<00:07:44.880> you<00:07:45.000> build<00:07:45.120> on<00:07:45.300> chain<00:07:45.479> is<00:07:45.720> interoperable 00:07:46.249 --> 00:07:46.259 align:start position:0% that you build on chain is interoperable 00:07:46.259 --> 00:07:48.050 align:start position:0% that you build on chain is interoperable to<00:07:46.620> everything<00:07:46.800> else<00:07:47.099> already<00:07:47.400> you<00:07:47.759> just<00:07:47.940> have 00:07:48.050 --> 00:07:48.060 align:start position:0% to everything else already you just have 00:07:48.060 --> 00:07:49.790 align:start position:0% to everything else already you just have to<00:07:48.240> make<00:07:48.539> like<00:07:48.780> a<00:07:48.960> custom<00:07:49.080> integration<00:07:49.560> for 00:07:49.790 --> 00:07:49.800 align:start position:0% to make like a custom integration for 00:07:49.800 --> 00:07:52.370 align:start position:0% to make like a custom integration for everything<00:07:50.180> which<00:07:51.180> gets<00:07:51.599> obviously<00:07:51.960> kind<00:07:52.319> of 00:07:52.370 --> 00:07:52.380 align:start position:0% everything which gets obviously kind of 00:07:52.380 --> 00:07:53.990 align:start position:0% everything which gets obviously kind of annoying<00:07:52.680> and<00:07:52.800> is<00:07:52.979> not<00:07:53.160> scalable<00:07:53.520> so<00:07:53.759> in<00:07:53.880> other 00:07:53.990 --> 00:07:54.000 align:start position:0% annoying and is not scalable so in other 00:07:54.000 --> 00:07:56.629 align:start position:0% annoying and is not scalable so in other words<00:07:54.380> interoperability<00:07:55.380> needs<00:07:55.919> interfaces 00:07:56.629 --> 00:07:56.639 align:start position:0% words interoperability needs interfaces 00:07:56.639 --> 00:07:57.770 align:start position:0% words interoperability needs interfaces to<00:07:56.880> scale 00:07:57.770 --> 00:07:57.780 align:start position:0% to scale 00:07:57.780 --> 00:08:00.170 align:start position:0% to scale and<00:07:58.319> you<00:07:58.440> can<00:07:58.500> think<00:07:58.620> of<00:07:58.800> mud<00:07:59.039> as<00:07:59.639> an<00:07:59.819> interface 00:08:00.170 --> 00:08:00.180 align:start position:0% and you can think of mud as an interface 00:08:00.180 --> 00:08:02.210 align:start position:0% and you can think of mud as an interface for<00:08:00.539> those<00:08:00.720> Unchained<00:08:01.259> worlds 00:08:02.210 --> 00:08:02.220 align:start position:0% for those Unchained worlds 00:08:02.220 --> 00:08:04.129 align:start position:0% for those Unchained worlds you<00:08:02.699> can<00:08:02.819> read<00:08:03.060> the<00:08:03.479> state<00:08:03.660> from<00:08:03.900> your<00:08:04.020> own 00:08:04.129 --> 00:08:04.139 align:start position:0% you can read the state from your own 00:08:04.139 --> 00:08:06.050 align:start position:0% you can read the state from your own world<00:08:04.319> in<00:08:04.860> the<00:08:04.979> exact<00:08:05.160> same<00:08:05.340> way<00:08:05.520> as<00:08:05.819> you<00:08:05.940> can 00:08:06.050 --> 00:08:06.060 align:start position:0% world in the exact same way as you can 00:08:06.060 --> 00:08:07.490 align:start position:0% world in the exact same way as you can read<00:08:06.120> the<00:08:06.300> state<00:08:06.479> from<00:08:06.660> other<00:08:06.780> worlds<00:08:07.139> so<00:08:07.319> all 00:08:07.490 --> 00:08:07.500 align:start position:0% read the state from other worlds so all 00:08:07.500 --> 00:08:08.809 align:start position:0% read the state from other worlds so all those<00:08:07.680> words<00:08:07.800> are<00:08:08.099> just<00:08:08.280> by<00:08:08.460> default 00:08:08.809 --> 00:08:08.819 align:start position:0% those words are just by default 00:08:08.819 --> 00:08:11.809 align:start position:0% those words are just by default interoperable<00:08:09.360> with<00:08:09.660> each<00:08:09.840> other 00:08:11.809 --> 00:08:11.819 align:start position:0% interoperable with each other 00:08:11.819 --> 00:08:13.790 align:start position:0% interoperable with each other and<00:08:12.300> you<00:08:12.479> can<00:08:12.539> think<00:08:12.660> of<00:08:12.900> existing<00:08:13.380> interfaces 00:08:13.790 --> 00:08:13.800 align:start position:0% and you can think of existing interfaces 00:08:13.800 --> 00:08:16.610 align:start position:0% and you can think of existing interfaces like<00:08:14.060> erc721<00:08:15.060> as<00:08:15.599> an<00:08:15.840> interface<00:08:16.199> for 00:08:16.610 --> 00:08:16.620 align:start position:0% like erc721 as an interface for 00:08:16.620 --> 00:08:19.369 align:start position:0% like erc721 as an interface for ownership<00:08:17.120> but<00:08:18.120> mud<00:08:18.840> on<00:08:19.020> the<00:08:19.139> other<00:08:19.199> hand 00:08:19.369 --> 00:08:19.379 align:start position:0% ownership but mud on the other hand 00:08:19.379 --> 00:08:21.830 align:start position:0% ownership but mud on the other hand since<00:08:20.039> every<00:08:20.340> component<00:08:20.879> is<00:08:21.180> a<00:08:21.360> standardized 00:08:21.830 --> 00:08:21.840 align:start position:0% since every component is a standardized 00:08:21.840 --> 00:08:23.869 align:start position:0% since every component is a standardized way<00:08:22.020> of<00:08:22.199> storing<00:08:22.560> the<00:08:22.680> data<00:08:22.979> and<00:08:23.220> we<00:08:23.520> have<00:08:23.699> the 00:08:23.869 --> 00:08:23.879 align:start position:0% way of storing the data and we have the 00:08:23.879 --> 00:08:26.029 align:start position:0% way of storing the data and we have the standardized<00:08:24.360> query<00:08:24.660> system<00:08:24.900> basically<00:08:25.740> mud 00:08:26.029 --> 00:08:26.039 align:start position:0% standardized query system basically mud 00:08:26.039 --> 00:08:28.070 align:start position:0% standardized query system basically mud is<00:08:26.220> an<00:08:26.340> interface<00:08:26.699> for<00:08:26.940> anything<00:08:27.240> like<00:08:27.900> you 00:08:28.070 --> 00:08:28.080 align:start position:0% is an interface for anything like you 00:08:28.080 --> 00:08:30.230 align:start position:0% is an interface for anything like you can<00:08:28.199> just<00:08:28.319> write<00:08:28.620> a<00:08:28.800> query<00:08:28.979> for<00:08:29.580> any<00:08:29.699> world<00:08:29.940> out 00:08:30.230 --> 00:08:30.240 align:start position:0% can just write a query for any world out 00:08:30.240 --> 00:08:32.810 align:start position:0% can just write a query for any world out there<00:08:30.560> and<00:08:31.560> just<00:08:31.919> represent<00:08:32.279> whatever<00:08:32.520> you 00:08:32.810 --> 00:08:32.820 align:start position:0% there and just represent whatever you 00:08:32.820 --> 00:08:34.130 align:start position:0% there and just represent whatever you want<00:08:32.940> basically<00:08:33.300> this<00:08:33.479> query<00:08:33.719> this<00:08:33.959> very 00:08:34.130 --> 00:08:34.140 align:start position:0% want basically this query this very 00:08:34.140 --> 00:08:36.170 align:start position:0% want basically this query this very simple<00:08:34.320> query<00:08:34.680> gives<00:08:35.399> you<00:08:35.520> all<00:08:35.700> the<00:08:35.820> movable 00:08:36.170 --> 00:08:36.180 align:start position:0% simple query gives you all the movable 00:08:36.180 --> 00:08:37.850 align:start position:0% simple query gives you all the movable attack<00:08:36.419> entities<00:08:36.899> owned<00:08:37.380> by<00:08:37.440> this<00:08:37.680> address 00:08:37.850 --> 00:08:37.860 align:start position:0% attack entities owned by this address 00:08:37.860 --> 00:08:40.130 align:start position:0% attack entities owned by this address but<00:08:38.459> you<00:08:38.640> can<00:08:38.760> get<00:08:38.940> arbitrarily<00:08:39.599> complex<00:08:39.899> with 00:08:40.130 --> 00:08:40.140 align:start position:0% but you can get arbitrarily complex with 00:08:40.140 --> 00:08:42.889 align:start position:0% but you can get arbitrarily complex with that 00:08:42.889 --> 00:08:42.899 align:start position:0% 00:08:42.899 --> 00:08:44.810 align:start position:0% so<00:08:43.440> this<00:08:43.620> is<00:08:43.680> how<00:08:43.860> much<00:08:44.039> solves<00:08:44.520> all<00:08:44.700> the 00:08:44.810 --> 00:08:44.820 align:start position:0% so this is how much solves all the 00:08:44.820 --> 00:08:46.670 align:start position:0% so this is how much solves all the problems<00:08:45.180> for<00:08:45.480> building<00:08:45.600> ancient<00:08:46.080> games<00:08:46.260> but 00:08:46.670 --> 00:08:46.680 align:start position:0% problems for building ancient games but 00:08:46.680 --> 00:08:48.470 align:start position:0% problems for building ancient games but the<00:08:46.860> great<00:08:47.040> thing<00:08:47.160> for<00:08:47.339> mud<00:08:47.640> is<00:08:48.060> that<00:08:48.300> it's 00:08:48.470 --> 00:08:48.480 align:start position:0% the great thing for mud is that it's 00:08:48.480 --> 00:08:51.769 align:start position:0% the great thing for mud is that it's actually<00:08:48.720> completely<00:08:49.440> genre<00:08:49.860> agnostic<00:08:50.459> we 00:08:51.769 --> 00:08:51.779 align:start position:0% actually completely genre agnostic we 00:08:51.779 --> 00:08:54.290 align:start position:0% actually completely genre agnostic we build<00:08:52.500> two<00:08:53.100> different<00:08:53.399> games<00:08:53.640> in-house 00:08:54.290 --> 00:08:54.300 align:start position:0% build two different games in-house 00:08:54.300 --> 00:08:55.910 align:start position:0% build two different games in-house Atlantis<00:08:54.959> over<00:08:55.080> the<00:08:55.200> last<00:08:55.320> couple<00:08:55.440> of<00:08:55.620> weeks 00:08:55.910 --> 00:08:55.920 align:start position:0% Atlantis over the last couple of weeks 00:08:55.920 --> 00:08:58.250 align:start position:0% Atlantis over the last couple of weeks two<00:08:56.339> completely<00:08:56.700> different<00:08:56.820> genres 00:08:58.250 --> 00:08:58.260 align:start position:0% two completely different genres 00:08:58.260 --> 00:09:00.350 align:start position:0% two completely different genres the<00:08:58.680> first<00:08:58.800> one<00:08:58.980> is<00:08:59.160> called<00:08:59.339> skystrive<00:09:00.120> and 00:09:00.350 --> 00:09:00.360 align:start position:0% the first one is called skystrive and 00:09:00.360 --> 00:09:03.350 align:start position:0% the first one is called skystrive and it's<00:09:00.480> an<00:09:00.660> Unchained<00:09:01.140> RTS<00:09:01.760> the<00:09:02.760> goal<00:09:03.060> is<00:09:03.120> to 00:09:03.350 --> 00:09:03.360 align:start position:0% it's an Unchained RTS the goal is to 00:09:03.360 --> 00:09:05.090 align:start position:0% it's an Unchained RTS the goal is to build<00:09:03.540> your<00:09:03.720> army<00:09:04.019> to<00:09:04.200> defeat<00:09:04.560> your<00:09:04.620> opponents 00:09:05.090 --> 00:09:05.100 align:start position:0% build your army to defeat your opponents 00:09:05.100 --> 00:09:06.710 align:start position:0% build your army to defeat your opponents and<00:09:05.339> then<00:09:05.459> steal<00:09:05.940> the<00:09:06.060> loot<00:09:06.300> from<00:09:06.480> the<00:09:06.660> center 00:09:06.710 --> 00:09:06.720 align:start position:0% and then steal the loot from the center 00:09:06.720 --> 00:09:08.570 align:start position:0% and then steal the loot from the center of<00:09:06.959> the<00:09:07.140> island<00:09:07.260> and<00:09:07.560> then<00:09:07.800> escape<00:09:07.980> the<00:09:08.279> loot 00:09:08.570 --> 00:09:08.580 align:start position:0% of the island and then escape the loot 00:09:08.580 --> 00:09:11.449 align:start position:0% of the island and then escape the loot as<00:09:08.760> the<00:09:08.940> first<00:09:09.060> person<00:09:09.380> it<00:09:10.380> uses<00:09:10.920> 39 00:09:11.449 --> 00:09:11.459 align:start position:0% as the first person it uses 39 00:09:11.459 --> 00:09:14.030 align:start position:0% as the first person it uses 39 components<00:09:12.000> 20<00:09:12.240> systems<00:09:12.839> and<00:09:13.500> not<00:09:13.680> a<00:09:13.860> single 00:09:14.030 --> 00:09:14.040 align:start position:0% components 20 systems and not a single 00:09:14.040 --> 00:09:15.650 align:start position:0% components 20 systems and not a single line<00:09:14.160> of<00:09:14.339> networking<00:09:14.760> code<00:09:14.880> because<00:09:15.180> mud 00:09:15.650 --> 00:09:15.660 align:start position:0% line of networking code because mud 00:09:15.660 --> 00:09:17.449 align:start position:0% line of networking code because mud handles<00:09:15.959> all<00:09:16.140> of<00:09:16.260> that<00:09:16.380> for<00:09:16.560> you<00:09:16.680> and<00:09:17.279> we're 00:09:17.449 --> 00:09:17.459 align:start position:0% handles all of that for you and we're 00:09:17.459 --> 00:09:19.250 align:start position:0% handles all of that for you and we're actually<00:09:17.580> going<00:09:17.820> to<00:09:17.940> play<00:09:18.120> tonight<00:09:18.420> at<00:09:18.899> or<00:09:19.080> not 00:09:19.250 --> 00:09:19.260 align:start position:0% actually going to play tonight at or not 00:09:19.260 --> 00:09:20.630 align:start position:0% actually going to play tonight at or not tonight<00:09:19.380> this<00:09:19.740> afternoon<00:09:19.860> at<00:09:20.220> the<00:09:20.339> hacker 00:09:20.630 --> 00:09:20.640 align:start position:0% tonight this afternoon at the hacker 00:09:20.640 --> 00:09:22.250 align:start position:0% tonight this afternoon at the hacker basement<00:09:20.760> at<00:09:21.180> 4pm<00:09:21.600> so<00:09:21.779> if<00:09:21.899> you<00:09:22.019> want<00:09:22.080> to<00:09:22.200> check 00:09:22.250 --> 00:09:22.260 align:start position:0% basement at 4pm so if you want to check 00:09:22.260 --> 00:09:23.810 align:start position:0% basement at 4pm so if you want to check it<00:09:22.380> out<00:09:22.500> come<00:09:22.680> there 00:09:23.810 --> 00:09:23.820 align:start position:0% it out come there 00:09:23.820 --> 00:09:26.690 align:start position:0% it out come there and<00:09:24.300> then<00:09:24.420> the<00:09:24.600> other<00:09:24.720> game<00:09:24.959> we've<00:09:25.440> built<00:09:25.800> is 00:09:26.690 --> 00:09:26.700 align:start position:0% and then the other game we've built is 00:09:26.700 --> 00:09:28.970 align:start position:0% and then the other game we've built is yet<00:09:27.180> to<00:09:27.360> be<00:09:27.480> announced<00:09:27.839> it's<00:09:28.320> an<00:09:28.500> on-chained 00:09:28.970 --> 00:09:28.980 align:start position:0% yet to be announced it's an on-chained 00:09:28.980 --> 00:09:31.250 align:start position:0% yet to be announced it's an on-chained boxel<00:09:29.339> game<00:09:29.580> it<00:09:30.420> features<00:09:30.660> an<00:09:30.839> infinitely 00:09:31.250 --> 00:09:31.260 align:start position:0% boxel game it features an infinitely 00:09:31.260 --> 00:09:33.350 align:start position:0% boxel game it features an infinitely proceededly<00:09:31.980> generated<00:09:32.459> world<00:09:32.700> you<00:09:33.000> can<00:09:33.120> mine 00:09:33.350 --> 00:09:33.360 align:start position:0% proceededly generated world you can mine 00:09:33.360 --> 00:09:35.690 align:start position:0% proceededly generated world you can mine you<00:09:33.600> can<00:09:33.779> build<00:09:34.620> stuff<00:09:34.860> you<00:09:35.100> can<00:09:35.220> craft<00:09:35.399> stuff 00:09:35.690 --> 00:09:35.700 align:start position:0% you can build stuff you can craft stuff 00:09:35.700 --> 00:09:37.550 align:start position:0% you can build stuff you can craft stuff and<00:09:36.240> it<00:09:36.360> only<00:09:36.480> has<00:09:36.660> eight<00:09:36.899> components<00:09:37.380> and 00:09:37.550 --> 00:09:37.560 align:start position:0% and it only has eight components and 00:09:37.560 --> 00:09:39.889 align:start position:0% and it only has eight components and seven<00:09:37.740> systems<00:09:38.279> and<00:09:38.820> also<00:09:39.120> here<00:09:39.300> zero 00:09:39.889 --> 00:09:39.899 align:start position:0% seven systems and also here zero 00:09:39.899 --> 00:09:42.050 align:start position:0% seven systems and also here zero networking<00:09:40.320> code 00:09:42.050 --> 00:09:42.060 align:start position:0% networking code 00:09:42.060 --> 00:09:43.370 align:start position:0% networking code and<00:09:42.420> those<00:09:42.540> two<00:09:42.720> games<00:09:42.899> are<00:09:43.140> completely 00:09:43.370 --> 00:09:43.380 align:start position:0% and those two games are completely 00:09:43.380 --> 00:09:45.410 align:start position:0% and those two games are completely different<00:09:43.560> genres<00:09:43.980> but<00:09:44.519> they<00:09:44.820> build<00:09:45.060> on<00:09:45.240> the 00:09:45.410 --> 00:09:45.420 align:start position:0% different genres but they build on the 00:09:45.420 --> 00:09:47.630 align:start position:0% different genres but they build on the exact<00:09:45.720> same<00:09:45.839> infrastructure<00:09:46.560> they<00:09:47.100> just<00:09:47.279> use 00:09:47.630 --> 00:09:47.640 align:start position:0% exact same infrastructure they just use 00:09:47.640 --> 00:09:49.130 align:start position:0% exact same infrastructure they just use different<00:09:47.880> components<00:09:48.360> and<00:09:48.540> combine<00:09:48.839> them<00:09:49.019> in 00:09:49.130 --> 00:09:49.140 align:start position:0% different components and combine them in 00:09:49.140 --> 00:09:50.750 align:start position:0% different components and combine them in a<00:09:49.260> different<00:09:49.380> way 00:09:50.750 --> 00:09:50.760 align:start position:0% a different way 00:09:50.760 --> 00:09:54.050 align:start position:0% a different way yeah<00:09:51.240> and<00:09:51.480> this<00:09:51.600> is<00:09:51.720> much<00:09:52.160> as<00:09:53.160> a<00:09:53.339> summary<00:09:53.580> with 00:09:54.050 --> 00:09:54.060 align:start position:0% yeah and this is much as a summary with 00:09:54.060 --> 00:09:55.310 align:start position:0% yeah and this is much as a summary with mutts<00:09:54.420> you<00:09:54.540> don't<00:09:54.660> have<00:09:54.779> to<00:09:54.839> write<00:09:54.959> a<00:09:55.140> single 00:09:55.310 --> 00:09:55.320 align:start position:0% mutts you don't have to write a single 00:09:55.320 --> 00:09:56.690 align:start position:0% mutts you don't have to write a single line<00:09:55.440> of<00:09:55.620> networking<00:09:55.980> code<00:09:56.100> because<00:09:56.339> mud 00:09:56.690 --> 00:09:56.700 align:start position:0% line of networking code because mud 00:09:56.700 --> 00:09:58.430 align:start position:0% line of networking code because mud handles<00:09:57.000> all<00:09:57.120> of<00:09:57.240> that<00:09:57.360> for<00:09:57.540> you<00:09:57.660> adding 00:09:58.430 --> 00:09:58.440 align:start position:0% handles all of that for you adding 00:09:58.440 --> 00:10:00.530 align:start position:0% handles all of that for you adding content<00:09:58.740> is<00:09:58.920> completely<00:09:59.279> trivial<00:09:59.700> adding<00:10:00.480> a 00:10:00.530 --> 00:10:00.540 align:start position:0% content is completely trivial adding a 00:10:00.540 --> 00:10:01.910 align:start position:0% content is completely trivial adding a new<00:10:00.660> component<00:10:01.019> doubles<00:10:01.380> the<00:10:01.560> amount<00:10:01.800> of 00:10:01.910 --> 00:10:01.920 align:start position:0% new component doubles the amount of 00:10:01.920 --> 00:10:03.829 align:start position:0% new component doubles the amount of entities<00:10:02.160> the<00:10:02.760> types<00:10:03.120> of<00:10:03.180> entities<00:10:03.480> you<00:10:03.720> can 00:10:03.829 --> 00:10:03.839 align:start position:0% entities the types of entities you can 00:10:03.839 --> 00:10:06.110 align:start position:0% entities the types of entities you can represent<00:10:04.200> and<00:10:04.920> any<00:10:05.160> mod<00:10:05.339> world<00:10:05.640> is<00:10:05.940> by 00:10:06.110 --> 00:10:06.120 align:start position:0% represent and any mod world is by 00:10:06.120 --> 00:10:08.630 align:start position:0% represent and any mod world is by default<00:10:06.420> interoperable<00:10:07.080> with<00:10:07.680> any<00:10:07.920> other<00:10:08.100> mud 00:10:08.630 --> 00:10:08.640 align:start position:0% default interoperable with any other mud 00:10:08.640 --> 00:10:10.490 align:start position:0% default interoperable with any other mud world<00:10:08.820> and<00:10:09.540> that<00:10:09.660> is<00:10:09.779> how<00:10:09.899> we<00:10:10.019> solve<00:10:10.260> all<00:10:10.320> the 00:10:10.490 --> 00:10:10.500 align:start position:0% world and that is how we solve all the 00:10:10.500 --> 00:10:15.590 align:start position:0% world and that is how we solve all the problems 00:10:15.590 --> 00:10:15.600 align:start position:0% 00:10:15.600 --> 00:10:18.290 align:start position:0% cool<00:10:16.200> all<00:10:16.620> right<00:10:16.740> I'm<00:10:17.279> gonna<00:10:17.459> drop<00:10:17.760> some<00:10:18.000> more 00:10:18.290 --> 00:10:18.300 align:start position:0% cool all right I'm gonna drop some more 00:10:18.300 --> 00:10:19.970 align:start position:0% cool all right I'm gonna drop some more crazy<00:10:18.720> stuff 00:10:19.970 --> 00:10:19.980 align:start position:0% crazy stuff 00:10:19.980 --> 00:10:23.389 align:start position:0% crazy stuff um full<00:10:20.580> nodes<00:10:20.940> are<00:10:21.120> great<00:10:21.300> so<00:10:22.620> after<00:10:23.160> this 00:10:23.389 --> 00:10:23.399 align:start position:0% um full nodes are great so after this 00:10:23.399 --> 00:10:24.889 align:start position:0% um full nodes are great so after this like<00:10:23.580> short<00:10:23.700> introduction<00:10:24.180> to<00:10:24.300> mud<00:10:24.540> I<00:10:24.720> want<00:10:24.779> to 00:10:24.889 --> 00:10:24.899 align:start position:0% like short introduction to mud I want to 00:10:24.899 --> 00:10:27.050 align:start position:0% like short introduction to mud I want to go<00:10:24.959> over<00:10:25.080> two<00:10:25.740> kind<00:10:26.160> of<00:10:26.279> like<00:10:26.339> Advanced 00:10:27.050 --> 00:10:27.060 align:start position:0% go over two kind of like Advanced 00:10:27.060 --> 00:10:29.150 align:start position:0% go over two kind of like Advanced features<00:10:27.660> slash<00:10:28.080> mental<00:10:28.560> model<00:10:28.680> from<00:10:28.980> what 00:10:29.150 --> 00:10:29.160 align:start position:0% features slash mental model from what 00:10:29.160 --> 00:10:31.910 align:start position:0% features slash mental model from what mud<00:10:29.519> is<00:10:29.760> so<00:10:30.540> the<00:10:31.260> interesting<00:10:31.620> thing<00:10:31.680> with 00:10:31.910 --> 00:10:31.920 align:start position:0% mud is so the interesting thing with 00:10:31.920 --> 00:10:33.650 align:start position:0% mud is so the interesting thing with full<00:10:32.100> nodes<00:10:32.399> is<00:10:32.580> that<00:10:32.820> they<00:10:33.120> give<00:10:33.300> you<00:10:33.420> access 00:10:33.650 --> 00:10:33.660 align:start position:0% full nodes is that they give you access 00:10:33.660 --> 00:10:35.750 align:start position:0% full nodes is that they give you access to<00:10:34.140> the<00:10:34.380> entire<00:10:34.620> chain<00:10:34.860> directly<00:10:35.459> from<00:10:35.640> the 00:10:35.750 --> 00:10:35.760 align:start position:0% to the entire chain directly from the 00:10:35.760 --> 00:10:37.190 align:start position:0% to the entire chain directly from the node<00:10:35.940> database 00:10:37.190 --> 00:10:37.200 align:start position:0% node database 00:10:37.200 --> 00:10:39.170 align:start position:0% node database um<00:10:37.260> with<00:10:37.500> a<00:10:37.620> node<00:10:37.860> you<00:10:38.100> can<00:10:38.220> do<00:10:38.519> things<00:10:38.700> like<00:10:38.940> oh 00:10:39.170 --> 00:10:39.180 align:start position:0% um with a node you can do things like oh 00:10:39.180 --> 00:10:41.269 align:start position:0% um with a node you can do things like oh what<00:10:39.839> is<00:10:39.959> the<00:10:40.080> counterfactual<00:10:40.680> of<00:10:40.860> this<00:10:40.980> can<00:10:41.160> I 00:10:41.269 --> 00:10:41.279 align:start position:0% what is the counterfactual of this can I 00:10:41.279 --> 00:10:42.530 align:start position:0% what is the counterfactual of this can I execute<00:10:41.519> a<00:10:41.640> transaction<00:10:41.940> but<00:10:42.240> slightly 00:10:42.530 --> 00:10:42.540 align:start position:0% execute a transaction but slightly 00:10:42.540 --> 00:10:44.750 align:start position:0% execute a transaction but slightly change<00:10:42.779> the<00:10:43.019> storage<00:10:43.440> of<00:10:43.680> that<00:10:43.860> contract<00:10:44.220> like 00:10:44.750 --> 00:10:44.760 align:start position:0% change the storage of that contract like 00:10:44.760 --> 00:10:46.370 align:start position:0% change the storage of that contract like what<00:10:45.120> would<00:10:45.240> happen<00:10:45.480> if<00:10:45.660> I<00:10:45.779> were<00:10:45.899> to<00:10:46.079> make<00:10:46.260> a 00:10:46.370 --> 00:10:46.380 align:start position:0% what would happen if I were to make a 00:10:46.380 --> 00:10:47.990 align:start position:0% what would happen if I were to make a transaction<00:10:46.680> in<00:10:46.920> unit<00:10:47.040> Swap<00:10:47.399> and<00:10:47.579> have<00:10:47.760> a 00:10:47.990 --> 00:10:48.000 align:start position:0% transaction in unit Swap and have a 00:10:48.000 --> 00:10:50.269 align:start position:0% transaction in unit Swap and have a billion<00:10:48.240> die<00:10:48.480> instead<00:10:48.899> of<00:10:48.959> like<00:10:49.079> 10. 00:10:50.269 --> 00:10:50.279 align:start position:0% billion die instead of like 10. 00:10:50.279 --> 00:10:52.910 align:start position:0% billion die instead of like 10. um<00:10:50.399> the<00:10:51.240> problem<00:10:51.360> is<00:10:51.660> that<00:10:51.959> traditional<00:10:52.560> dap 00:10:52.910 --> 00:10:52.920 align:start position:0% um the problem is that traditional dap 00:10:52.920 --> 00:10:55.370 align:start position:0% um the problem is that traditional dap clients<00:10:53.279> today<00:10:53.519> are<00:10:54.000> not<00:10:54.180> full<00:10:54.360> nodes 00:10:55.370 --> 00:10:55.380 align:start position:0% clients today are not full nodes 00:10:55.380 --> 00:10:57.350 align:start position:0% clients today are not full nodes they<00:10:55.860> rely<00:10:56.160> on<00:10:56.339> things<00:10:56.459> like<00:10:56.640> inferior<00:10:57.180> or 00:10:57.350 --> 00:10:57.360 align:start position:0% they rely on things like inferior or 00:10:57.360 --> 00:10:59.449 align:start position:0% they rely on things like inferior or Alchemy<00:10:57.779> to<00:10:58.320> serve<00:10:58.620> their<00:10:58.740> data<00:10:59.100> and<00:10:59.339> then 00:10:59.449 --> 00:10:59.459 align:start position:0% Alchemy to serve their data and then 00:10:59.459 --> 00:11:00.829 align:start position:0% Alchemy to serve their data and then they<00:10:59.579> have<00:10:59.640> to<00:10:59.760> build<00:10:59.880> this<00:11:00.120> like<00:11:00.300> complex 00:11:00.829 --> 00:11:00.839 align:start position:0% they have to build this like complex 00:11:00.839 --> 00:11:02.870 align:start position:0% they have to build this like complex State<00:11:01.079> machine<00:11:01.380> of<00:11:01.680> indexers<00:11:02.160> and<00:11:02.399> events<00:11:02.700> in 00:11:02.870 --> 00:11:02.880 align:start position:0% State machine of indexers and events in 00:11:02.880 --> 00:11:04.310 align:start position:0% State machine of indexers and events in order<00:11:03.000> to<00:11:03.180> serve<00:11:03.540> the<00:11:03.660> data<00:11:03.839> they<00:11:04.019> need<00:11:04.200> to 00:11:04.310 --> 00:11:04.320 align:start position:0% order to serve the data they need to 00:11:04.320 --> 00:11:05.870 align:start position:0% order to serve the data they need to their<00:11:04.500> users 00:11:05.870 --> 00:11:05.880 align:start position:0% their users 00:11:05.880 --> 00:11:07.730 align:start position:0% their users um as<00:11:06.120> an<00:11:06.240> example<00:11:06.480> the<00:11:06.660> uniswap<00:11:07.200> client<00:11:07.500> has 00:11:07.730 --> 00:11:07.740 align:start position:0% um as an example the uniswap client has 00:11:07.740 --> 00:11:09.410 align:start position:0% um as an example the uniswap client has to<00:11:07.860> connect<00:11:07.980> to<00:11:08.160> a<00:11:08.279> full<00:11:08.399> node<00:11:08.700> and<00:11:09.060> it<00:11:09.180> has<00:11:09.300> to 00:11:09.410 --> 00:11:09.420 align:start position:0% to connect to a full node and it has to 00:11:09.420 --> 00:11:11.030 align:start position:0% to connect to a full node and it has to fetch<00:11:09.660> the<00:11:09.720> state<00:11:09.839> it<00:11:10.079> is<00:11:10.200> interested<00:11:10.560> in<00:11:10.740> just 00:11:11.030 --> 00:11:11.040 align:start position:0% fetch the state it is interested in just 00:11:11.040 --> 00:11:12.230 align:start position:0% fetch the state it is interested in just in<00:11:11.220> time<00:11:11.339> because<00:11:11.519> otherwise<00:11:11.820> it<00:11:11.940> would<00:11:12.060> take 00:11:12.230 --> 00:11:12.240 align:start position:0% in time because otherwise it would take 00:11:12.240 --> 00:11:13.850 align:start position:0% in time because otherwise it would take way<00:11:12.360> too<00:11:12.540> long<00:11:12.660> so<00:11:13.079> as<00:11:13.200> you<00:11:13.380> like<00:11:13.500> move<00:11:13.680> around 00:11:13.850 --> 00:11:13.860 align:start position:0% way too long so as you like move around 00:11:13.860 --> 00:11:15.110 align:start position:0% way too long so as you like move around and<00:11:14.040> uniswap<00:11:14.519> and<00:11:14.640> you<00:11:14.760> like<00:11:14.880> select 00:11:15.110 --> 00:11:15.120 align:start position:0% and uniswap and you like select 00:11:15.120 --> 00:11:16.370 align:start position:0% and uniswap and you like select different<00:11:15.240> polls<00:11:15.600> you<00:11:15.720> have<00:11:15.839> to<00:11:15.959> wait<00:11:16.079> every 00:11:16.370 --> 00:11:16.380 align:start position:0% different polls you have to wait every 00:11:16.380 --> 00:11:18.470 align:start position:0% different polls you have to wait every single<00:11:16.620> time<00:11:16.740> to<00:11:16.920> know<00:11:17.040> what's<00:11:17.160> going<00:11:17.339> on 00:11:18.470 --> 00:11:18.480 align:start position:0% single time to know what's going on 00:11:18.480 --> 00:11:20.150 align:start position:0% single time to know what's going on um<00:11:18.540> the<00:11:19.140> I<00:11:19.440> don't<00:11:19.500> know<00:11:19.620> if<00:11:19.680> you've<00:11:19.860> ever<00:11:19.920> read 00:11:20.150 --> 00:11:20.160 align:start position:0% um the I don't know if you've ever read 00:11:20.160 --> 00:11:21.769 align:start position:0% um the I don't know if you've ever read the<00:11:20.339> unicewap<00:11:20.820> client<00:11:21.060> code<00:11:21.240> but<00:11:21.480> it's<00:11:21.600> pretty 00:11:21.769 --> 00:11:21.779 align:start position:0% the unicewap client code but it's pretty 00:11:21.779 --> 00:11:23.449 align:start position:0% the unicewap client code but it's pretty insane<00:11:22.200> just<00:11:22.380> to<00:11:22.560> be<00:11:22.620> able<00:11:22.740> to<00:11:22.860> keep<00:11:23.040> such<00:11:23.279> a 00:11:23.449 --> 00:11:23.459 align:start position:0% insane just to be able to keep such a 00:11:23.459 --> 00:11:25.009 align:start position:0% insane just to be able to keep such a short<00:11:23.640> like<00:11:23.880> a<00:11:24.060> simple<00:11:24.240> State<00:11:24.480> machine<00:11:24.779> in 00:11:25.009 --> 00:11:25.019 align:start position:0% short like a simple State machine in 00:11:25.019 --> 00:11:26.990 align:start position:0% short like a simple State machine in sync<00:11:25.440> and<00:11:26.160> there<00:11:26.279> needs<00:11:26.459> to<00:11:26.519> be<00:11:26.640> like<00:11:26.700> a<00:11:26.820> lot<00:11:26.940> of 00:11:26.990 --> 00:11:27.000 align:start position:0% sync and there needs to be like a lot of 00:11:27.000 --> 00:11:28.970 align:start position:0% sync and there needs to be like a lot of custom<00:11:27.180> code<00:11:27.420> and<00:11:27.660> indexers<00:11:28.200> additionally 00:11:28.970 --> 00:11:28.980 align:start position:0% custom code and indexers additionally 00:11:28.980 --> 00:11:30.829 align:start position:0% custom code and indexers additionally the<00:11:29.220> unit<00:11:29.399> swap<00:11:29.760> client<00:11:30.000> cannot<00:11:30.600> actually 00:11:30.829 --> 00:11:30.839 align:start position:0% the unit swap client cannot actually 00:11:30.839 --> 00:11:32.630 align:start position:0% the unit swap client cannot actually simulate<00:11:31.380> transactions<00:11:31.920> and<00:11:32.220> it<00:11:32.399> doesn't 00:11:32.630 --> 00:11:32.640 align:start position:0% simulate transactions and it doesn't 00:11:32.640 --> 00:11:34.190 align:start position:0% simulate transactions and it doesn't know<00:11:32.940> what<00:11:33.120> will<00:11:33.360> happen<00:11:33.540> if<00:11:33.839> you<00:11:33.959> like 00:11:34.190 --> 00:11:34.200 align:start position:0% know what will happen if you like 00:11:34.200 --> 00:11:37.250 align:start position:0% know what will happen if you like execute<00:11:34.560> that<00:11:34.800> that<00:11:34.980> single<00:11:35.399> Swap<00:11:35.640> so<00:11:36.480> the<00:11:37.200> way 00:11:37.250 --> 00:11:37.260 align:start position:0% execute that that single Swap so the way 00:11:37.260 --> 00:11:38.870 align:start position:0% execute that that single Swap so the way it<00:11:37.380> actually<00:11:37.560> works<00:11:37.920> is<00:11:38.100> you<00:11:38.579> have<00:11:38.640> the<00:11:38.760> unit 00:11:38.870 --> 00:11:38.880 align:start position:0% it actually works is you have the unit 00:11:38.880 --> 00:11:40.790 align:start position:0% it actually works is you have the unit swap<00:11:39.240> client<00:11:39.480> and<00:11:39.720> then<00:11:39.899> remotely<00:11:40.320> you<00:11:40.560> have<00:11:40.680> a 00:11:40.790 --> 00:11:40.800 align:start position:0% swap client and then remotely you have a 00:11:40.800 --> 00:11:41.750 align:start position:0% swap client and then remotely you have a full<00:11:40.860> node<00:11:41.100> and<00:11:41.220> you<00:11:41.339> have<00:11:41.459> a<00:11:41.519> bunch<00:11:41.640> of 00:11:41.750 --> 00:11:41.760 align:start position:0% full node and you have a bunch of 00:11:41.760 --> 00:11:43.850 align:start position:0% full node and you have a bunch of indexers<00:11:42.180> and<00:11:42.720> the<00:11:42.899> universal<00:11:43.260> plan<00:11:43.380> estimate 00:11:43.850 --> 00:11:43.860 align:start position:0% indexers and the universal plan estimate 00:11:43.860 --> 00:11:45.949 align:start position:0% indexers and the universal plan estimate very<00:11:44.279> slow<00:11:44.519> Network<00:11:44.880> requests<00:11:45.420> in<00:11:45.660> order<00:11:45.779> to 00:11:45.949 --> 00:11:45.959 align:start position:0% very slow Network requests in order to 00:11:45.959 --> 00:11:47.269 align:start position:0% very slow Network requests in order to be<00:11:46.019> able<00:11:46.140> to<00:11:46.260> populate<00:11:46.620> the<00:11:46.800> information<00:11:46.920> that 00:11:47.269 --> 00:11:47.279 align:start position:0% be able to populate the information that 00:11:47.279 --> 00:11:50.030 align:start position:0% be able to populate the information that the<00:11:47.399> user<00:11:47.700> needs<00:11:47.940> so<00:11:48.720> why<00:11:49.079> don't<00:11:49.260> we<00:11:49.440> put<00:11:49.800> the 00:11:50.030 --> 00:11:50.040 align:start position:0% the user needs so why don't we put the 00:11:50.040 --> 00:11:51.769 align:start position:0% the user needs so why don't we put the full<00:11:50.160> node<00:11:50.399> and<00:11:50.519> indexer<00:11:51.000> inside<00:11:51.180> the<00:11:51.540> client 00:11:51.769 --> 00:11:51.779 align:start position:0% full node and indexer inside the client 00:11:51.779 --> 00:11:54.650 align:start position:0% full node and indexer inside the client right<00:11:52.200> like<00:11:52.980> that<00:11:53.519> would<00:11:53.700> allow<00:11:53.940> you<00:11:54.120> to<00:11:54.300> make 00:11:54.650 --> 00:11:54.660 align:start position:0% right like that would allow you to make 00:11:54.660 --> 00:11:56.449 align:start position:0% right like that would allow you to make instant<00:11:55.140> queries<00:11:55.560> you<00:11:55.980> would<00:11:56.100> be<00:11:56.220> able<00:11:56.339> to 00:11:56.449 --> 00:11:56.459 align:start position:0% instant queries you would be able to 00:11:56.459 --> 00:11:58.310 align:start position:0% instant queries you would be able to index<00:11:56.820> the<00:11:57.240> chain<00:11:57.540> however<00:11:57.899> you<00:11:58.079> want<00:11:58.200> you 00:11:58.310 --> 00:11:58.320 align:start position:0% index the chain however you want you 00:11:58.320 --> 00:11:59.690 align:start position:0% index the chain however you want you don't<00:11:58.440> have<00:11:58.560> Network<00:11:58.800> delays<00:11:59.279> anymore<00:11:59.399> after 00:11:59.690 --> 00:11:59.700 align:start position:0% don't have Network delays anymore after 00:11:59.700 --> 00:12:01.009 align:start position:0% don't have Network delays anymore after you're<00:11:59.940> synced<00:12:00.360> and<00:12:00.420> then<00:12:00.540> you<00:12:00.600> can<00:12:00.720> simulate 00:12:01.009 --> 00:12:01.019 align:start position:0% you're synced and then you can simulate 00:12:01.019 --> 00:12:03.650 align:start position:0% you're synced and then you can simulate transactions<00:12:01.500> right<00:12:01.620> that<00:12:01.920> would<00:12:02.040> be<00:12:02.160> amazing 00:12:03.650 --> 00:12:03.660 align:start position:0% transactions right that would be amazing 00:12:03.660 --> 00:12:05.329 align:start position:0% transactions right that would be amazing um<00:12:03.779> and<00:12:04.140> actually<00:12:04.260> for<00:12:04.680> like<00:12:04.860> the<00:12:04.980> ethereum 00:12:05.329 --> 00:12:05.339 align:start position:0% um and actually for like the ethereum 00:12:05.339 --> 00:12:06.949 align:start position:0% um and actually for like the ethereum ogs<00:12:05.820> here<00:12:05.940> that's<00:12:06.120> how<00:12:06.300> Mist<00:12:06.600> was<00:12:06.779> working 00:12:06.949 --> 00:12:06.959 align:start position:0% ogs here that's how Mist was working 00:12:06.959 --> 00:12:08.569 align:start position:0% ogs here that's how Mist was working which<00:12:07.200> was<00:12:07.320> the<00:12:07.440> ethereum<00:12:07.800> browser<00:12:08.160> like<00:12:08.399> five 00:12:08.569 --> 00:12:08.579 align:start position:0% which was the ethereum browser like five 00:12:08.579 --> 00:12:10.430 align:start position:0% which was the ethereum browser like five years<00:12:08.760> ago<00:12:09.060> but<00:12:09.540> the<00:12:09.660> thing<00:12:09.779> is<00:12:09.899> full<00:12:10.140> nodes 00:12:10.430 --> 00:12:10.440 align:start position:0% years ago but the thing is full nodes 00:12:10.440 --> 00:12:11.930 align:start position:0% years ago but the thing is full nodes are<00:12:10.560> super<00:12:10.740> expensive 00:12:11.930 --> 00:12:11.940 align:start position:0% are super expensive 00:12:11.940 --> 00:12:13.310 align:start position:0% are super expensive um<00:12:12.000> they<00:12:12.180> require<00:12:12.360> a<00:12:12.600> lot<00:12:12.660> of<00:12:12.779> bandwidth<00:12:13.200> and 00:12:13.310 --> 00:12:13.320 align:start position:0% um they require a lot of bandwidth and 00:12:13.320 --> 00:12:14.750 align:start position:0% um they require a lot of bandwidth and storage<00:12:13.560> they<00:12:13.980> have<00:12:14.220> very<00:12:14.339> expensive 00:12:14.750 --> 00:12:14.760 align:start position:0% storage they have very expensive 00:12:14.760 --> 00:12:16.370 align:start position:0% storage they have very expensive cryptographic<00:12:15.420> data<00:12:15.720> structures<00:12:16.019> that<00:12:16.260> are 00:12:16.370 --> 00:12:16.380 align:start position:0% cryptographic data structures that are 00:12:16.380 --> 00:12:18.590 align:start position:0% cryptographic data structures that are needed<00:12:16.620> in<00:12:16.740> order<00:12:16.860> to<00:12:17.100> serve<00:12:17.399> live<00:12:17.519> clients<00:12:18.060> so 00:12:18.590 --> 00:12:18.600 align:start position:0% needed in order to serve live clients so 00:12:18.600 --> 00:12:20.329 align:start position:0% needed in order to serve live clients so it's<00:12:18.899> pretty<00:12:19.079> much<00:12:19.260> like<00:12:19.740> it's<00:12:19.980> not<00:12:20.100> really 00:12:20.329 --> 00:12:20.339 align:start position:0% it's pretty much like it's not really 00:12:20.339 --> 00:12:22.910 align:start position:0% it's pretty much like it's not really practical<00:12:20.820> today<00:12:21.120> to<00:12:21.779> put<00:12:21.899> full<00:12:22.140> nodes<00:12:22.500> in<00:12:22.800> the 00:12:22.910 --> 00:12:22.920 align:start position:0% practical today to put full nodes in the 00:12:22.920 --> 00:12:24.050 align:start position:0% practical today to put full nodes in the clients 00:12:24.050 --> 00:12:24.060 align:start position:0% clients 00:12:24.060 --> 00:12:26.930 align:start position:0% clients and<00:12:24.660> so<00:12:24.899> because<00:12:25.320> of<00:12:25.560> that<00:12:25.800> most<00:12:26.279> dabs<00:12:26.820> today 00:12:26.930 --> 00:12:26.940 align:start position:0% and so because of that most dabs today 00:12:26.940 --> 00:12:29.150 align:start position:0% and so because of that most dabs today like<00:12:27.300> if<00:12:27.420> you<00:12:27.540> use<00:12:27.660> D5<00:12:28.140> or<00:12:28.440> like<00:12:28.620> whatever<00:12:28.800> kind 00:12:29.150 --> 00:12:29.160 align:start position:0% like if you use D5 or like whatever kind 00:12:29.160 --> 00:12:31.069 align:start position:0% like if you use D5 or like whatever kind of<00:12:29.279> stuff<00:12:29.399> usually<00:12:30.000> they<00:12:30.180> have<00:12:30.360> ux<00:12:30.720> hurting 00:12:31.069 --> 00:12:31.079 align:start position:0% of stuff usually they have ux hurting 00:12:31.079 --> 00:12:32.449 align:start position:0% of stuff usually they have ux hurting Network<00:12:31.260> calls<00:12:31.680> you<00:12:31.740> have<00:12:31.860> to<00:12:31.920> wait<00:12:32.040> a<00:12:32.220> lot<00:12:32.279> for 00:12:32.449 --> 00:12:32.459 align:start position:0% Network calls you have to wait a lot for 00:12:32.459 --> 00:12:33.769 align:start position:0% Network calls you have to wait a lot for every<00:12:32.640> single<00:12:32.880> thing 00:12:33.769 --> 00:12:33.779 align:start position:0% every single thing 00:12:33.779 --> 00:12:35.210 align:start position:0% every single thing um<00:12:33.839> you<00:12:34.079> have<00:12:34.200> to<00:12:34.260> wait<00:12:34.440> for<00:12:34.620> the<00:12:34.740> TX<00:12:34.980> to<00:12:35.160> be 00:12:35.210 --> 00:12:35.220 align:start position:0% um you have to wait for the TX to be 00:12:35.220 --> 00:12:36.590 align:start position:0% um you have to wait for the TX to be mine<00:12:35.399> in<00:12:35.519> order<00:12:35.700> to<00:12:35.880> know<00:12:36.060> what<00:12:36.300> the<00:12:36.480> side 00:12:36.590 --> 00:12:36.600 align:start position:0% mine in order to know what the side 00:12:36.600 --> 00:12:38.210 align:start position:0% mine in order to know what the side effects<00:12:36.839> of<00:12:36.959> what<00:12:37.140> you<00:12:37.200> have<00:12:37.320> done<00:12:37.500> like 00:12:38.210 --> 00:12:38.220 align:start position:0% effects of what you have done like 00:12:38.220 --> 00:12:40.250 align:start position:0% effects of what you have done like actually<00:12:38.760> is<00:12:39.120> there<00:12:39.660> are<00:12:39.779> services<00:12:39.899> today 00:12:40.250 --> 00:12:40.260 align:start position:0% actually is there are services today 00:12:40.260 --> 00:12:41.750 align:start position:0% actually is there are services today like<00:12:40.500> tenderly<00:12:41.040> and<00:12:41.160> stuff<00:12:41.279> that<00:12:41.459> allow<00:12:41.640> you 00:12:41.750 --> 00:12:41.760 align:start position:0% like tenderly and stuff that allow you 00:12:41.760 --> 00:12:43.069 align:start position:0% like tenderly and stuff that allow you to<00:12:41.880> simulate<00:12:42.180> transactions<00:12:42.540> but<00:12:42.720> they<00:12:42.899> add 00:12:43.069 --> 00:12:43.079 align:start position:0% to simulate transactions but they add 00:12:43.079 --> 00:12:44.569 align:start position:0% to simulate transactions but they add additional<00:12:43.440> complexity<00:12:43.860> to<00:12:44.100> the<00:12:44.220> code<00:12:44.339> base 00:12:44.569 --> 00:12:44.579 align:start position:0% additional complexity to the code base 00:12:44.579 --> 00:12:46.430 align:start position:0% additional complexity to the code base and<00:12:45.180> more<00:12:45.360> often<00:12:45.540> than<00:12:45.660> not<00:12:45.839> they<00:12:46.019> need<00:12:46.200> to<00:12:46.260> use 00:12:46.430 --> 00:12:46.440 align:start position:0% and more often than not they need to use 00:12:46.440 --> 00:12:48.410 align:start position:0% and more often than not they need to use remote<00:12:46.680> indexers<00:12:47.279> which<00:12:47.579> are<00:12:47.880> yet<00:12:48.180> another 00:12:48.410 --> 00:12:48.420 align:start position:0% remote indexers which are yet another 00:12:48.420 --> 00:12:50.690 align:start position:0% remote indexers which are yet another like<00:12:48.720> surface<00:12:49.139> of<00:12:49.440> things<00:12:50.040> that<00:12:50.220> can<00:12:50.339> possibly 00:12:50.690 --> 00:12:50.700 align:start position:0% like surface of things that can possibly 00:12:50.700 --> 00:12:53.389 align:start position:0% like surface of things that can possibly go<00:12:50.880> down<00:12:51.060> in<00:12:51.300> complexity<00:12:51.839> so 00:12:53.389 --> 00:12:53.399 align:start position:0% go down in complexity so 00:12:53.399 --> 00:12:55.310 align:start position:0% go down in complexity so can<00:12:53.880> we<00:12:54.000> do<00:12:54.180> better 00:12:55.310 --> 00:12:55.320 align:start position:0% can we do better 00:12:55.320 --> 00:12:57.350 align:start position:0% can we do better now<00:12:55.980> that<00:12:56.279> we<00:12:56.700> have 00:12:57.350 --> 00:12:57.360 align:start position:0% now that we have 00:12:57.360 --> 00:12:58.670 align:start position:0% now that we have like 00:12:58.670 --> 00:12:58.680 align:start position:0% like 00:12:58.680 --> 00:13:00.710 align:start position:0% like slightly<00:12:59.399> better<00:12:59.579> infrastructure<00:13:00.120> than<00:13:00.480> when 00:13:00.710 --> 00:13:00.720 align:start position:0% slightly better infrastructure than when 00:13:00.720 --> 00:13:03.530 align:start position:0% slightly better infrastructure than when web3<00:13:01.200> JS<00:13:01.740> and<00:13:01.860> ethersjs<00:13:02.459> was<00:13:02.639> invented<00:13:03.240> is 00:13:03.530 --> 00:13:03.540 align:start position:0% web3 JS and ethersjs was invented is 00:13:03.540 --> 00:13:05.150 align:start position:0% web3 JS and ethersjs was invented is there<00:13:03.660> a<00:13:03.839> way<00:13:03.959> to<00:13:04.200> essentially<00:13:04.440> have<00:13:04.680> our<00:13:04.920> cake 00:13:05.150 --> 00:13:05.160 align:start position:0% there a way to essentially have our cake 00:13:05.160 --> 00:13:06.889 align:start position:0% there a way to essentially have our cake and<00:13:05.339> needed<00:13:05.639> to 00:13:06.889 --> 00:13:06.899 align:start position:0% and needed to 00:13:06.899 --> 00:13:07.670 align:start position:0% and needed to um 00:13:07.670 --> 00:13:07.680 align:start position:0% um 00:13:07.680 --> 00:13:09.050 align:start position:0% um the<00:13:08.100> one<00:13:08.279> interesting<00:13:08.639> fact<00:13:08.820> about 00:13:09.050 --> 00:13:09.060 align:start position:0% the one interesting fact about 00:13:09.060 --> 00:13:10.790 align:start position:0% the one interesting fact about autonomous<00:13:09.660> Wars<00:13:09.959> or<00:13:10.019> unchain<00:13:10.380> game<00:13:10.560> is<00:13:10.680> that 00:13:10.790 --> 00:13:10.800 align:start position:0% autonomous Wars or unchain game is that 00:13:10.800 --> 00:13:12.710 align:start position:0% autonomous Wars or unchain game is that there<00:13:10.980> are<00:13:11.160> more<00:13:11.339> often<00:13:11.639> than<00:13:11.820> not<00:13:12.060> Standalone 00:13:12.710 --> 00:13:12.720 align:start position:0% there are more often than not Standalone 00:13:12.720 --> 00:13:14.990 align:start position:0% there are more often than not Standalone unlike<00:13:13.440> traditional<00:13:13.800> d-apps<00:13:14.399> what<00:13:14.880> that 00:13:14.990 --> 00:13:15.000 align:start position:0% unlike traditional d-apps what that 00:13:15.000 --> 00:13:16.970 align:start position:0% unlike traditional d-apps what that means<00:13:15.300> is<00:13:15.420> that<00:13:15.720> the<00:13:16.440> state<00:13:16.560> transition 00:13:16.970 --> 00:13:16.980 align:start position:0% means is that the state transition 00:13:16.980 --> 00:13:19.190 align:start position:0% means is that the state transition function<00:13:17.459> of<00:13:17.760> an<00:13:17.880> autonomous<00:13:18.240> word<00:13:18.480> almost 00:13:19.190 --> 00:13:19.200 align:start position:0% function of an autonomous word almost 00:13:19.200 --> 00:13:21.889 align:start position:0% function of an autonomous word almost always<00:13:19.620> only<00:13:20.160> depend<00:13:20.639> on<00:13:20.820> its<00:13:21.060> own<00:13:21.120> state<00:13:21.360> so 00:13:21.889 --> 00:13:21.899 align:start position:0% always only depend on its own state so 00:13:21.899 --> 00:13:23.389 align:start position:0% always only depend on its own state so as<00:13:22.019> an<00:13:22.200> example<00:13:22.440> when<00:13:22.680> doc<00:13:22.920> first<00:13:23.100> was<00:13:23.279> running 00:13:23.389 --> 00:13:23.399 align:start position:0% as an example when doc first was running 00:13:23.399 --> 00:13:25.550 align:start position:0% as an example when doc first was running on<00:13:23.579> xdi<00:13:24.060> Doc<00:13:24.720> first<00:13:24.839> could<00:13:25.079> have<00:13:25.200> run<00:13:25.260> on<00:13:25.440> a 00:13:25.550 --> 00:13:25.560 align:start position:0% on xdi Doc first could have run on a 00:13:25.560 --> 00:13:27.170 align:start position:0% on xdi Doc first could have run on a chain<00:13:25.680> with<00:13:25.920> nothing<00:13:26.100> else<00:13:26.339> but<00:13:26.579> Dark<00:13:26.760> Forest 00:13:27.170 --> 00:13:27.180 align:start position:0% chain with nothing else but Dark Forest 00:13:27.180 --> 00:13:29.090 align:start position:0% chain with nothing else but Dark Forest Dark<00:13:27.540> first<00:13:27.899> didn't<00:13:28.139> care<00:13:28.500> about<00:13:28.800> the<00:13:28.980> other 00:13:29.090 --> 00:13:29.100 align:start position:0% Dark first didn't care about the other 00:13:29.100 --> 00:13:31.190 align:start position:0% Dark first didn't care about the other things<00:13:29.279> on<00:13:29.459> xdi<00:13:30.000> right<00:13:30.180> that's<00:13:30.420> unlike<00:13:30.839> most 00:13:31.190 --> 00:13:31.200 align:start position:0% things on xdi right that's unlike most 00:13:31.200 --> 00:13:34.129 align:start position:0% things on xdi right that's unlike most dapps<00:13:32.160> today<00:13:32.279> which<00:13:32.700> rely<00:13:33.180> heavily<00:13:33.600> on<00:13:33.839> like<00:13:33.959> a 00:13:34.129 --> 00:13:34.139 align:start position:0% dapps today which rely heavily on like a 00:13:34.139 --> 00:13:35.930 align:start position:0% dapps today which rely heavily on like a plethora<00:13:34.680> of<00:13:34.740> different<00:13:34.980> services<00:13:35.279> on<00:13:35.700> chain 00:13:35.930 --> 00:13:35.940 align:start position:0% plethora of different services on chain 00:13:35.940 --> 00:13:37.850 align:start position:0% plethora of different services on chain that<00:13:36.300> they<00:13:36.420> connect<00:13:36.480> to<00:13:36.720> things<00:13:36.959> like<00:13:37.139> oracles 00:13:37.850 --> 00:13:37.860 align:start position:0% that they connect to things like oracles 00:13:37.860 --> 00:13:40.509 align:start position:0% that they connect to things like oracles things<00:13:38.519> like<00:13:38.760> erc20<00:13:39.360> contracts<00:13:39.899> and<00:13:40.019> so<00:13:40.139> forth 00:13:40.509 --> 00:13:40.519 align:start position:0% things like erc20 contracts and so forth 00:13:40.519 --> 00:13:42.650 align:start position:0% things like erc20 contracts and so forth and<00:13:41.519> again<00:13:41.639> this<00:13:41.880> is<00:13:42.000> unlike<00:13:42.240> as<00:13:42.360> an<00:13:42.480> example 00:13:42.650 --> 00:13:42.660 align:start position:0% and again this is unlike as an example 00:13:42.660 --> 00:13:44.990 align:start position:0% and again this is unlike as an example unit<00:13:42.899> swap<00:13:43.260> where<00:13:43.440> if<00:13:43.740> you<00:13:43.860> were<00:13:44.100> to<00:13:44.279> want<00:13:44.820> to 00:13:44.990 --> 00:13:45.000 align:start position:0% unit swap where if you were to want to 00:13:45.000 --> 00:13:47.629 align:start position:0% unit swap where if you were to want to simulate<00:13:45.420> the<00:13:45.540> transactions<00:13:46.260> of<00:13:47.100> like<00:13:47.220> a<00:13:47.339> uni 00:13:47.629 --> 00:13:47.639 align:start position:0% simulate the transactions of like a uni 00:13:47.639 --> 00:13:49.550 align:start position:0% simulate the transactions of like a uni swap<00:13:47.820> trade<00:13:48.120> you<00:13:48.540> would<00:13:48.660> need<00:13:48.779> to<00:13:48.959> know<00:13:49.139> about 00:13:49.550 --> 00:13:49.560 align:start position:0% swap trade you would need to know about 00:13:49.560 --> 00:13:51.230 align:start position:0% swap trade you would need to know about the<00:13:49.860> other<00:13:49.980> smart<00:13:50.279> contracts<00:13:50.820> like<00:13:51.060> the 00:13:51.230 --> 00:13:51.240 align:start position:0% the other smart contracts like the 00:13:51.240 --> 00:13:52.910 align:start position:0% the other smart contracts like the erc20s<00:13:51.959> on<00:13:52.079> each<00:13:52.139> side<00:13:52.260> of<00:13:52.440> the<00:13:52.560> pool<00:13:52.680> because 00:13:52.910 --> 00:13:52.920 align:start position:0% erc20s on each side of the pool because 00:13:52.920 --> 00:13:54.110 align:start position:0% erc20s on each side of the pool because they<00:13:53.040> could<00:13:53.160> be<00:13:53.279> implemented<00:13:53.820> slightly 00:13:54.110 --> 00:13:54.120 align:start position:0% they could be implemented slightly 00:13:54.120 --> 00:13:55.550 align:start position:0% they could be implemented slightly differently 00:13:55.550 --> 00:13:55.560 align:start position:0% differently 00:13:55.560 --> 00:13:57.889 align:start position:0% differently um so<00:13:56.220> one<00:13:56.459> like<00:13:56.820> mantle<00:13:57.420> model<00:13:57.600> for<00:13:57.779> what 00:13:57.889 --> 00:13:57.899 align:start position:0% um so one like mantle model for what 00:13:57.899 --> 00:13:59.930 align:start position:0% um so one like mantle model for what murders<00:13:58.380> is<00:13:58.500> that<00:13:58.620> it's<00:13:58.800> a<00:13:59.040> namespaced<00:13:59.760> full 00:13:59.930 --> 00:13:59.940 align:start position:0% murders is that it's a namespaced full 00:13:59.940 --> 00:14:01.730 align:start position:0% murders is that it's a namespaced full node<00:14:00.300> which<00:14:00.839> is<00:14:00.899> why<00:14:01.079> we<00:14:01.139> think<00:14:01.260> this<00:14:01.380> goes 00:14:01.730 --> 00:14:01.740 align:start position:0% node which is why we think this goes 00:14:01.740 --> 00:14:03.170 align:start position:0% node which is why we think this goes like<00:14:01.800> well<00:14:01.980> beyond<00:14:02.339> gaming<00:14:02.700> it's<00:14:02.820> a<00:14:03.000> way<00:14:03.060> to 00:14:03.170 --> 00:14:03.180 align:start position:0% like well beyond gaming it's a way to 00:14:03.180 --> 00:14:04.790 align:start position:0% like well beyond gaming it's a way to build<00:14:03.360> actually<00:14:03.600> like<00:14:03.839> better<00:14:04.079> clients<00:14:04.620> than 00:14:04.790 --> 00:14:04.800 align:start position:0% build actually like better clients than 00:14:04.800 --> 00:14:06.710 align:start position:0% build actually like better clients than what<00:14:04.980> exists<00:14:05.279> today<00:14:05.399> and<00:14:06.120> the<00:14:06.240> reason<00:14:06.360> we<00:14:06.540> can 00:14:06.710 --> 00:14:06.720 align:start position:0% what exists today and the reason we can 00:14:06.720 --> 00:14:08.690 align:start position:0% what exists today and the reason we can build<00:14:06.899> a<00:14:07.139> namespace<00:14:07.620> full<00:14:08.100> note<00:14:08.279> is<00:14:08.519> because 00:14:08.690 --> 00:14:08.700 align:start position:0% build a namespace full note is because 00:14:08.700 --> 00:14:10.310 align:start position:0% build a namespace full note is because as<00:14:09.000> I<00:14:09.120> said<00:14:09.240> earlier<00:14:09.540> autonomous<00:14:09.959> words<00:14:10.139> are 00:14:10.310 --> 00:14:10.320 align:start position:0% as I said earlier autonomous words are 00:14:10.320 --> 00:14:13.009 align:start position:0% as I said earlier autonomous words are mostly<00:14:10.560> Standalone<00:14:10.980> so<00:14:11.700> mud<00:14:12.300> sinks<00:14:12.779> a<00:14:12.839> world 00:14:13.009 --> 00:14:13.019 align:start position:0% mostly Standalone so mud sinks a world 00:14:13.019 --> 00:14:15.050 align:start position:0% mostly Standalone so mud sinks a world the<00:14:13.500> word<00:14:13.620> contract<00:14:14.100> that<00:14:14.339> Alvarez<00:14:14.760> talked 00:14:15.050 --> 00:14:15.060 align:start position:0% the word contract that Alvarez talked 00:14:15.060 --> 00:14:16.730 align:start position:0% the word contract that Alvarez talked about<00:14:15.120> it's<00:14:15.600> a<00:14:15.779> namespace<00:14:16.139> for<00:14:16.320> data<00:14:16.620> and 00:14:16.730 --> 00:14:16.740 align:start position:0% about it's a namespace for data and 00:14:16.740 --> 00:14:19.190 align:start position:0% about it's a namespace for data and logic<00:14:17.100> so<00:14:17.339> data<00:14:17.820> are<00:14:18.120> components<00:14:18.660> and<00:14:18.839> logic 00:14:19.190 --> 00:14:19.200 align:start position:0% logic so data are components and logic 00:14:19.200 --> 00:14:22.490 align:start position:0% logic so data are components and logic are<00:14:19.320> systems<00:14:19.800> so<00:14:20.639> mud<00:14:21.300> can<00:14:21.540> sync<00:14:21.899> the<00:14:22.079> data<00:14:22.380> of 00:14:22.490 --> 00:14:22.500 align:start position:0% are systems so mud can sync the data of 00:14:22.500 --> 00:14:24.170 align:start position:0% are systems so mud can sync the data of every<00:14:22.920> single<00:14:23.220> component<00:14:23.639> connected<00:14:24.060> to 00:14:24.170 --> 00:14:24.180 align:start position:0% every single component connected to 00:14:24.180 --> 00:14:26.629 align:start position:0% every single component connected to every<00:14:24.420> single<00:14:24.720> entity<00:14:25.019> and<00:14:25.740> download<00:14:25.920> the<00:14:26.220> evm 00:14:26.629 --> 00:14:26.639 align:start position:0% every single entity and download the evm 00:14:26.639 --> 00:14:29.210 align:start position:0% every single entity and download the evm by<00:14:26.760> code<00:14:27.000> of<00:14:27.180> every<00:14:27.360> single<00:14:27.660> system<00:14:28.100> and<00:14:29.100> the 00:14:29.210 --> 00:14:29.220 align:start position:0% by code of every single system and the 00:14:29.220 --> 00:14:30.710 align:start position:0% by code of every single system and the way<00:14:29.339> it<00:14:29.399> does<00:14:29.579> it<00:14:29.700> is<00:14:29.880> it<00:14:30.060> does<00:14:30.240> its<00:14:30.540> initial 00:14:30.710 --> 00:14:30.720 align:start position:0% way it does it is it does its initial 00:14:30.720 --> 00:14:33.530 align:start position:0% way it does it is it does its initial sync<00:14:31.139> via<00:14:31.500> a<00:14:32.160> general<00:14:32.279> mud<00:14:32.700> indexer<00:14:33.120> or<00:14:33.360> a<00:14:33.420> full 00:14:33.530 --> 00:14:33.540 align:start position:0% sync via a general mud indexer or a full 00:14:33.540 --> 00:14:35.150 align:start position:0% sync via a general mud indexer or a full node<00:14:33.839> and<00:14:34.019> it<00:14:34.139> keeps<00:14:34.380> its<00:14:34.500> state<00:14:34.620> up<00:14:34.860> to<00:14:34.980> date 00:14:35.150 --> 00:14:35.160 align:start position:0% node and it keeps its state up to date 00:14:35.160 --> 00:14:37.750 align:start position:0% node and it keeps its state up to date via<00:14:35.700> a<00:14:35.880> full<00:14:36.240> node<00:14:36.540> or<00:14:36.779> a<00:14:36.899> mud<00:14:37.079> stream<00:14:37.200> service 00:14:37.750 --> 00:14:37.760 align:start position:0% via a full node or a mud stream service 00:14:37.760 --> 00:14:40.550 align:start position:0% via a full node or a mud stream service mud<00:14:38.760> doesn't<00:14:38.940> need<00:14:39.240> the<00:14:39.540> cryptographic<00:14:40.199> data 00:14:40.550 --> 00:14:40.560 align:start position:0% mud doesn't need the cryptographic data 00:14:40.560 --> 00:14:41.629 align:start position:0% mud doesn't need the cryptographic data structures<00:14:40.860> that<00:14:41.040> are<00:14:41.160> usually<00:14:41.339> in<00:14:41.459> a<00:14:41.579> full 00:14:41.629 --> 00:14:41.639 align:start position:0% structures that are usually in a full 00:14:41.639 --> 00:14:42.829 align:start position:0% structures that are usually in a full node<00:14:41.880> because<00:14:42.180> we<00:14:42.360> don't<00:14:42.420> want<00:14:42.540> to<00:14:42.660> serve 00:14:42.829 --> 00:14:42.839 align:start position:0% node because we don't want to serve 00:14:42.839 --> 00:14:44.449 align:start position:0% node because we don't want to serve light<00:14:43.019> clients<00:14:43.380> we<00:14:43.500> just<00:14:43.680> trust<00:14:43.980> a<00:14:44.279> node 00:14:44.449 --> 00:14:44.459 align:start position:0% light clients we just trust a node 00:14:44.459 --> 00:14:45.829 align:start position:0% light clients we just trust a node remotely<00:14:44.880> but<00:14:45.060> what<00:14:45.240> we<00:14:45.360> want<00:14:45.480> to<00:14:45.540> be<00:14:45.660> able<00:14:45.720> to 00:14:45.829 --> 00:14:45.839 align:start position:0% remotely but what we want to be able to 00:14:45.839 --> 00:14:47.629 align:start position:0% remotely but what we want to be able to do<00:14:45.959> is<00:14:46.079> like<00:14:46.260> give<00:14:46.500> like<00:14:46.800> build<00:14:47.040> extremely 00:14:47.629 --> 00:14:47.639 align:start position:0% do is like give like build extremely 00:14:47.639 --> 00:14:49.730 align:start position:0% do is like give like build extremely Snappy<00:14:48.120> applications<00:14:48.600> by<00:14:49.079> having<00:14:49.320> the<00:14:49.560> entire 00:14:49.730 --> 00:14:49.740 align:start position:0% Snappy applications by having the entire 00:14:49.740 --> 00:14:52.550 align:start position:0% Snappy applications by having the entire student<00:14:49.980> logic<00:14:50.459> client<00:14:50.699> side<00:14:50.880> so<00:14:51.779> I<00:14:52.440> think 00:14:52.550 --> 00:14:52.560 align:start position:0% student logic client side so I think 00:14:52.560 --> 00:14:53.870 align:start position:0% student logic client side so I think that<00:14:52.680> is<00:14:52.800> interesting<00:14:53.100> with<00:14:53.339> Mod<00:14:53.519> is<00:14:53.760> that 00:14:53.870 --> 00:14:53.880 align:start position:0% that is interesting with Mod is that 00:14:53.880 --> 00:14:55.449 align:start position:0% that is interesting with Mod is that components<00:14:54.240> are<00:14:54.360> self-descriptive 00:14:55.449 --> 00:14:55.459 align:start position:0% components are self-descriptive 00:14:55.459 --> 00:14:57.710 align:start position:0% components are self-descriptive components<00:14:56.459> of<00:14:56.579> on-chain<00:14:57.060> schema<00:14:57.540> that 00:14:57.710 --> 00:14:57.720 align:start position:0% components of on-chain schema that 00:14:57.720 --> 00:14:59.750 align:start position:0% components of on-chain schema that explains<00:14:58.139> how<00:14:58.380> to<00:14:58.500> interpret<00:14:59.040> their<00:14:59.519> actual 00:14:59.750 --> 00:14:59.760 align:start position:0% explains how to interpret their actual 00:14:59.760 --> 00:15:02.509 align:start position:0% explains how to interpret their actual like<00:14:59.940> row<00:15:00.360> bytes<00:15:00.720> and<00:15:01.560> so<00:15:01.680> the<00:15:01.980> mud<00:15:02.160> client<00:15:02.399> can 00:15:02.509 --> 00:15:02.519 align:start position:0% like row bytes and so the mud client can 00:15:02.519 --> 00:15:04.550 align:start position:0% like row bytes and so the mud client can read<00:15:02.639> the<00:15:02.760> onshine<00:15:03.120> schema<00:15:03.540> and<00:15:03.899> so<00:15:04.019> compare 00:15:04.550 --> 00:15:04.560 align:start position:0% read the onshine schema and so compare 00:15:04.560 --> 00:15:06.050 align:start position:0% read the onshine schema and so compare that<00:15:04.680> to<00:15:04.800> a<00:15:04.920> full<00:15:04.980> node<00:15:05.220> with<00:15:05.459> a<00:15:05.579> full<00:15:05.699> node<00:15:05.940> you 00:15:06.050 --> 00:15:06.060 align:start position:0% that to a full node with a full node you 00:15:06.060 --> 00:15:07.970 align:start position:0% that to a full node with a full node you know<00:15:06.240> this<00:15:06.420> the<00:15:06.779> actual<00:15:07.079> storage<00:15:07.260> lots<00:15:07.500> of<00:15:07.560> of 00:15:07.970 --> 00:15:07.980 align:start position:0% know this the actual storage lots of of 00:15:07.980 --> 00:15:10.250 align:start position:0% know this the actual storage lots of of every<00:15:08.220> single<00:15:08.519> contracts<00:15:09.060> but<00:15:09.720> then<00:15:09.959> you<00:15:10.079> just 00:15:10.250 --> 00:15:10.260 align:start position:0% every single contracts but then you just 00:15:10.260 --> 00:15:12.350 align:start position:0% every single contracts but then you just have<00:15:10.380> like<00:15:10.620> 256<00:15:11.399> bits<00:15:11.760> of<00:15:11.880> like<00:15:12.000> you<00:15:12.180> don't 00:15:12.350 --> 00:15:12.360 align:start position:0% have like 256 bits of like you don't 00:15:12.360 --> 00:15:13.850 align:start position:0% have like 256 bits of like you don't know<00:15:12.480> what<00:15:12.660> that<00:15:12.839> is<00:15:13.019> this<00:15:13.440> is<00:15:13.560> why<00:15:13.680> people 00:15:13.850 --> 00:15:13.860 align:start position:0% know what that is this is why people 00:15:13.860 --> 00:15:15.769 align:start position:0% know what that is this is why people write<00:15:14.220> view<00:15:14.519> functions<00:15:15.000> in<00:15:15.180> their<00:15:15.360> contracts 00:15:15.769 --> 00:15:15.779 align:start position:0% write view functions in their contracts 00:15:15.779 --> 00:15:16.970 align:start position:0% write view functions in their contracts in<00:15:15.899> order<00:15:16.019> to<00:15:16.139> be<00:15:16.260> able<00:15:16.380> to<00:15:16.440> like<00:15:16.620> load 00:15:16.970 --> 00:15:16.980 align:start position:0% in order to be able to like load 00:15:16.980 --> 00:15:18.530 align:start position:0% in order to be able to like load actually<00:15:17.100> contextual<00:15:17.699> data<00:15:18.180> from<00:15:18.420> those 00:15:18.530 --> 00:15:18.540 align:start position:0% actually contextual data from those 00:15:18.540 --> 00:15:20.449 align:start position:0% actually contextual data from those applications<00:15:18.959> with<00:15:19.500> mud<00:15:19.680> what<00:15:19.920> you<00:15:20.040> get<00:15:20.160> is<00:15:20.339> a 00:15:20.449 --> 00:15:20.459 align:start position:0% applications with mud what you get is a 00:15:20.459 --> 00:15:22.129 align:start position:0% applications with mud what you get is a key<00:15:20.579> value<00:15:20.699> database<00:15:21.180> of<00:15:21.420> entities<00:15:21.660> mapping 00:15:22.129 --> 00:15:22.139 align:start position:0% key value database of entities mapping 00:15:22.139 --> 00:15:23.930 align:start position:0% key value database of entities mapping to<00:15:22.260> a<00:15:22.380> bunch<00:15:22.500> of<00:15:22.560> components<00:15:23.100> and<00:15:23.639> it<00:15:23.820> doesn't 00:15:23.930 --> 00:15:23.940 align:start position:0% to a bunch of components and it doesn't 00:15:23.940 --> 00:15:26.090 align:start position:0% to a bunch of components and it doesn't matter<00:15:24.240> who<00:15:24.899> deployed<00:15:25.320> those<00:15:25.440> components<00:15:25.920> the 00:15:26.090 --> 00:15:26.100 align:start position:0% matter who deployed those components the 00:15:26.100 --> 00:15:27.590 align:start position:0% matter who deployed those components the client<00:15:26.279> just<00:15:26.459> knows<00:15:26.760> what<00:15:26.880> they<00:15:27.000> are<00:15:27.120> it<00:15:27.360> knows 00:15:27.590 --> 00:15:27.600 align:start position:0% client just knows what they are it knows 00:15:27.600 --> 00:15:28.790 align:start position:0% client just knows what they are it knows what<00:15:27.660> their<00:15:27.839> name<00:15:28.019> is<00:15:28.139> it<00:15:28.320> knows<00:15:28.560> what<00:15:28.680> their 00:15:28.790 --> 00:15:28.800 align:start position:0% what their name is it knows what their 00:15:28.800 --> 00:15:30.710 align:start position:0% what their name is it knows what their structure<00:15:29.100> is<00:15:29.279> so<00:15:29.639> as<00:15:29.820> an<00:15:29.940> example<00:15:30.180> when<00:15:30.480> you 00:15:30.710 --> 00:15:30.720 align:start position:0% structure is so as an example when you 00:15:30.720 --> 00:15:33.050 align:start position:0% structure is so as an example when you sync<00:15:31.199> like<00:15:31.320> a<00:15:31.560> mud<00:15:31.800> full<00:15:32.040> node<00:15:32.339> so<00:15:32.699> a<00:15:32.820> mud 00:15:33.050 --> 00:15:33.060 align:start position:0% sync like a mud full node so a mud 00:15:33.060 --> 00:15:35.210 align:start position:0% sync like a mud full node so a mud client<00:15:33.420> you<00:15:34.260> would<00:15:34.380> know<00:15:34.560> that<00:15:34.800> the<00:15:35.100> first 00:15:35.210 --> 00:15:35.220 align:start position:0% client you would know that the first 00:15:35.220 --> 00:15:38.030 align:start position:0% client you would know that the first entity<00:15:35.519> 0x0<00:15:36.240> has<00:15:36.660> position<00:15:36.899> 1245<00:15:37.680> and<00:15:37.920> health 00:15:38.030 --> 00:15:38.040 align:start position:0% entity 0x0 has position 1245 and health 00:15:38.040 --> 00:15:39.350 align:start position:0% entity 0x0 has position 1245 and health 200. 00:15:39.350 --> 00:15:39.360 align:start position:0% 200. 00:15:39.360 --> 00:15:41.210 align:start position:0% 200. so<00:15:39.720> it's<00:15:39.899> way<00:15:40.079> more<00:15:40.199> contextual<00:15:40.680> than<00:15:40.920> the<00:15:41.100> way 00:15:41.210 --> 00:15:41.220 align:start position:0% so it's way more contextual than the way 00:15:41.220 --> 00:15:42.650 align:start position:0% so it's way more contextual than the way full<00:15:41.399> nodes<00:15:41.579> are<00:15:41.699> done<00:15:41.820> today<00:15:42.480> um<00:15:42.540> it's 00:15:42.650 --> 00:15:42.660 align:start position:0% full nodes are done today um it's 00:15:42.660 --> 00:15:44.150 align:start position:0% full nodes are done today um it's because<00:15:42.839> I<00:15:43.199> mean<00:15:43.320> ethereum<00:15:43.680> is<00:15:43.800> trying<00:15:43.920> to<00:15:44.040> be 00:15:44.150 --> 00:15:44.160 align:start position:0% because I mean ethereum is trying to be 00:15:44.160 --> 00:15:45.710 align:start position:0% because I mean ethereum is trying to be as<00:15:44.339> general<00:15:44.519> as<00:15:44.760> possible<00:15:45.000> whereas<00:15:45.420> here<00:15:45.540> we 00:15:45.710 --> 00:15:45.720 align:start position:0% as general as possible whereas here we 00:15:45.720 --> 00:15:47.210 align:start position:0% as general as possible whereas here we impose<00:15:46.079> constraints<00:15:46.560> in<00:15:46.860> order<00:15:46.920> to<00:15:47.040> get 00:15:47.210 --> 00:15:47.220 align:start position:0% impose constraints in order to get 00:15:47.220 --> 00:15:48.650 align:start position:0% impose constraints in order to get features 00:15:48.650 --> 00:15:48.660 align:start position:0% features 00:15:48.660 --> 00:15:50.990 align:start position:0% features um<00:15:48.779> this<00:15:49.139> allows<00:15:49.560> a<00:15:49.980> client<00:15:50.220> to<00:15:50.399> run<00:15:50.519> complex 00:15:50.990 --> 00:15:51.000 align:start position:0% um this allows a client to run complex 00:15:51.000 --> 00:15:52.730 align:start position:0% um this allows a client to run complex queries<00:15:51.480> on<00:15:51.720> components<00:15:52.199> without<00:15:52.440> any 00:15:52.730 --> 00:15:52.740 align:start position:0% queries on components without any 00:15:52.740 --> 00:15:54.650 align:start position:0% queries on components without any network<00:15:52.920> delay<00:15:53.339> so<00:15:53.699> you<00:15:53.820> can<00:15:53.940> run<00:15:54.120> aggregated 00:15:54.650 --> 00:15:54.660 align:start position:0% network delay so you can run aggregated 00:15:54.660 --> 00:15:56.389 align:start position:0% network delay so you can run aggregated queries<00:15:55.019> like<00:15:55.260> oh<00:15:55.380> give<00:15:55.680> me<00:15:55.800> all<00:15:56.100> the<00:15:56.220> entities 00:15:56.389 --> 00:15:56.399 align:start position:0% queries like oh give me all the entities 00:15:56.399 --> 00:15:58.670 align:start position:0% queries like oh give me all the entities that<00:15:56.699> have<00:15:56.820> a<00:15:56.940> position<00:15:57.060> and<00:15:57.480> a<00:15:57.660> health<00:15:57.779> with 00:15:58.670 --> 00:15:58.680 align:start position:0% that have a position and a health with 00:15:58.680 --> 00:16:01.069 align:start position:0% that have a position and a health with value<00:15:58.860> 10.<00:15:59.459> you<00:15:59.820> can<00:16:00.000> do<00:16:00.180> crazier<00:16:00.779> stuff<00:16:00.959> like 00:16:01.069 --> 00:16:01.079 align:start position:0% value 10. you can do crazier stuff like 00:16:01.079 --> 00:16:02.329 align:start position:0% value 10. you can do crazier stuff like Aggregates<00:16:01.500> and<00:16:01.740> stuff<00:16:01.860> like<00:16:01.920> that<00:16:02.040> but<00:16:02.220> all 00:16:02.329 --> 00:16:02.339 align:start position:0% Aggregates and stuff like that but all 00:16:02.339 --> 00:16:03.889 align:start position:0% Aggregates and stuff like that but all of<00:16:02.459> these<00:16:02.579> are<00:16:02.699> executed<00:16:03.180> instantly<00:16:03.600> in<00:16:03.779> like 00:16:03.889 --> 00:16:03.899 align:start position:0% of these are executed instantly in like 00:16:03.899 --> 00:16:06.110 align:start position:0% of these are executed instantly in like one<00:16:04.079> millisecond<00:16:04.560> on<00:16:04.860> the<00:16:04.980> actual<00:16:05.220> state<00:16:05.459> so 00:16:06.110 --> 00:16:06.120 align:start position:0% one millisecond on the actual state so 00:16:06.120 --> 00:16:07.550 align:start position:0% one millisecond on the actual state so if<00:16:06.420> you<00:16:06.540> were<00:16:06.660> to<00:16:06.720> rebuild<00:16:06.959> unit<00:16:07.139> swap<00:16:07.440> with 00:16:07.550 --> 00:16:07.560 align:start position:0% if you were to rebuild unit swap with 00:16:07.560 --> 00:16:08.810 align:start position:0% if you were to rebuild unit swap with mud<00:16:07.740> today<00:16:07.920> or<00:16:08.100> at<00:16:08.160> least<00:16:08.279> the<00:16:08.399> unit<00:16:08.519> swap 00:16:08.810 --> 00:16:08.820 align:start position:0% mud today or at least the unit swap 00:16:08.820 --> 00:16:10.490 align:start position:0% mud today or at least the unit swap client<00:16:09.120> you<00:16:09.839> would<00:16:09.899> be<00:16:10.079> able<00:16:10.139> to<00:16:10.199> move<00:16:10.380> around 00:16:10.490 --> 00:16:10.500 align:start position:0% client you would be able to move around 00:16:10.500 --> 00:16:12.050 align:start position:0% client you would be able to move around and<00:16:10.800> do<00:16:10.920> things<00:16:11.040> without<00:16:11.220> any<00:16:11.519> network<00:16:11.699> delay 00:16:12.050 --> 00:16:12.060 align:start position:0% and do things without any network delay 00:16:12.060 --> 00:16:13.730 align:start position:0% and do things without any network delay when<00:16:12.240> it's<00:16:12.360> synced<00:16:12.779> and<00:16:13.139> downloading<00:16:13.620> the 00:16:13.730 --> 00:16:13.740 align:start position:0% when it's synced and downloading the 00:16:13.740 --> 00:16:15.470 align:start position:0% when it's synced and downloading the actual<00:16:13.980> snitch<00:16:14.339> subshot<00:16:14.820> usually<00:16:15.120> takes<00:16:15.360> like 00:16:15.470 --> 00:16:15.480 align:start position:0% actual snitch subshot usually takes like 00:16:15.480 --> 00:16:17.689 align:start position:0% actual snitch subshot usually takes like less<00:16:15.720> than<00:16:15.839> a<00:16:15.959> second<00:16:16.139> so 00:16:17.689 --> 00:16:17.699 align:start position:0% less than a second so 00:16:17.699 --> 00:16:18.889 align:start position:0% less than a second so the<00:16:18.180> other<00:16:18.300> thing<00:16:18.480> that<00:16:18.600> is<00:16:18.720> pretty 00:16:18.889 --> 00:16:18.899 align:start position:0% the other thing that is pretty 00:16:18.899 --> 00:16:20.269 align:start position:0% the other thing that is pretty interesting<00:16:19.199> with<00:16:19.440> mud<00:16:19.620> is<00:16:19.860> that<00:16:19.980> it<00:16:20.100> ships 00:16:20.269 --> 00:16:20.279 align:start position:0% interesting with mud is that it ships 00:16:20.279 --> 00:16:23.150 align:start position:0% interesting with mud is that it ships with<00:16:20.459> a<00:16:20.639> local<00:16:20.760> evm<00:16:21.300> so<00:16:22.079> when<00:16:22.380> you<00:16:22.500> make<00:16:22.740> a 00:16:23.150 --> 00:16:23.160 align:start position:0% with a local evm so when you make a 00:16:23.160 --> 00:16:24.530 align:start position:0% with a local evm so when you make a transaction<00:16:23.519> in<00:16:23.760> mode<00:16:23.940> that<00:16:24.180> is<00:16:24.300> when<00:16:24.420> you 00:16:24.530 --> 00:16:24.540 align:start position:0% transaction in mode that is when you 00:16:24.540 --> 00:16:27.290 align:start position:0% transaction in mode that is when you call<00:16:24.660> a<00:16:24.839> system<00:16:25.019> what<00:16:25.920> mud<00:16:26.160> does<00:16:26.339> is<00:16:26.519> it<00:16:26.880> runs 00:16:27.290 --> 00:16:27.300 align:start position:0% call a system what mud does is it runs 00:16:27.300 --> 00:16:29.930 align:start position:0% call a system what mud does is it runs an<00:16:27.540> evm<00:16:28.079> on<00:16:28.740> that<00:16:28.920> system<00:16:29.100> given<00:16:29.459> it<00:16:29.519> knows<00:16:29.760> its 00:16:29.930 --> 00:16:29.940 align:start position:0% an evm on that system given it knows its 00:16:29.940 --> 00:16:31.970 align:start position:0% an evm on that system given it knows its bytecode<00:16:30.300> and<00:16:30.779> it<00:16:30.899> injects<00:16:31.260> the<00:16:31.440> easier<00:16:31.800> State 00:16:31.970 --> 00:16:31.980 align:start position:0% bytecode and it injects the easier State 00:16:31.980 --> 00:16:34.670 align:start position:0% bytecode and it injects the easier State when<00:16:32.880> that<00:16:33.240> actual<00:16:33.480> like<00:16:33.600> EVN<00:16:34.079> by<00:16:34.139> code<00:16:34.380> needs 00:16:34.670 --> 00:16:34.680 align:start position:0% when that actual like EVN by code needs 00:16:34.680 --> 00:16:36.170 align:start position:0% when that actual like EVN by code needs to<00:16:34.740> write<00:16:34.860> the<00:16:35.040> state<00:16:35.220> needs<00:16:35.880> to<00:16:35.940> read<00:16:36.060> the 00:16:36.170 --> 00:16:36.180 align:start position:0% to write the state needs to read the 00:16:36.180 --> 00:16:37.790 align:start position:0% to write the state needs to read the state<00:16:36.300> it<00:16:36.540> registers<00:16:37.019> all<00:16:37.259> the<00:16:37.380> side<00:16:37.560> effects 00:16:37.790 --> 00:16:37.800 align:start position:0% state it registers all the side effects 00:16:37.800 --> 00:16:39.050 align:start position:0% state it registers all the side effects that<00:16:37.860> happen<00:16:38.100> so<00:16:38.279> as<00:16:38.399> an<00:16:38.459> example<00:16:38.699> if<00:16:38.820> you<00:16:38.940> were 00:16:39.050 --> 00:16:39.060 align:start position:0% that happen so as an example if you were 00:16:39.060 --> 00:16:41.629 align:start position:0% that happen so as an example if you were to<00:16:39.120> like<00:16:39.300> call<00:16:39.660> the<00:16:39.899> move<00:16:40.079> system<00:16:40.380> on<00:16:41.279> entity 00:16:41.629 --> 00:16:41.639 align:start position:0% to like call the move system on entity 00:16:41.639 --> 00:16:44.150 align:start position:0% to like call the move system on entity one<00:16:41.940> and<00:16:42.300> you<00:16:42.360> say<00:16:42.540> move<00:16:42.720> to<00:16:42.899> X10<00:16:43.320> y<00:16:43.620> minus<00:16:43.980> 3 00:16:44.150 --> 00:16:44.160 align:start position:0% one and you say move to X10 y minus 3 00:16:44.160 --> 00:16:46.790 align:start position:0% one and you say move to X10 y minus 3 mud<00:16:45.120> can<00:16:45.300> run<00:16:45.480> that<00:16:45.660> into<00:16:46.019> an<00:16:46.199> evm<00:16:46.560> and<00:16:46.620> note 00:16:46.790 --> 00:16:46.800 align:start position:0% mud can run that into an evm and note 00:16:46.800 --> 00:16:48.230 align:start position:0% mud can run that into an evm and note that<00:16:46.920> the<00:16:47.040> side<00:16:47.160> effect<00:16:47.279> is<00:16:47.459> that<00:16:47.579> like<00:16:47.759> oh<00:16:47.940> no 00:16:48.230 --> 00:16:48.240 align:start position:0% that the side effect is that like oh no 00:16:48.240 --> 00:16:50.449 align:start position:0% that the side effect is that like oh no the<00:16:48.420> position<00:16:48.600> component<00:16:49.139> of<00:16:49.320> entity01<00:16:50.100> is 00:16:50.449 --> 00:16:50.459 align:start position:0% the position component of entity01 is 00:16:50.459 --> 00:16:52.009 align:start position:0% the position component of entity01 is 10-3 00:16:52.009 --> 00:16:52.019 align:start position:0% 10-3 00:16:52.019 --> 00:16:53.870 align:start position:0% 10-3 it<00:16:52.560> also<00:16:52.860> sends<00:16:53.160> the<00:16:53.220> transaction<00:16:53.519> on<00:16:53.699> chain 00:16:53.870 --> 00:16:53.880 align:start position:0% it also sends the transaction on chain 00:16:53.880 --> 00:16:55.310 align:start position:0% it also sends the transaction on chain of<00:16:54.120> course<00:16:54.240> and<00:16:54.540> then<00:16:54.720> when<00:16:54.899> the<00:16:55.079> transaction 00:16:55.310 --> 00:16:55.320 align:start position:0% of course and then when the transaction 00:16:55.320 --> 00:16:56.870 align:start position:0% of course and then when the transaction has<00:16:55.500> been<00:16:55.620> mined<00:16:55.860> on<00:16:55.920> chain<00:16:56.100> it<00:16:56.279> compares<00:16:56.759> the 00:16:56.870 --> 00:16:56.880 align:start position:0% has been mined on chain it compares the 00:16:56.880 --> 00:16:58.069 align:start position:0% has been mined on chain it compares the side<00:16:57.060> effects<00:16:57.300> that<00:16:57.420> happen<00:16:57.540> on<00:16:57.779> chain<00:16:57.899> with 00:16:58.069 --> 00:16:58.079 align:start position:0% side effects that happen on chain with 00:16:58.079 --> 00:16:59.629 align:start position:0% side effects that happen on chain with the<00:16:58.199> one<00:16:58.320> that<00:16:58.440> were<00:16:58.560> predicted<00:16:58.920> if<00:16:59.459> they 00:16:59.629 --> 00:16:59.639 align:start position:0% the one that were predicted if they 00:16:59.639 --> 00:17:01.790 align:start position:0% the one that were predicted if they match<00:16:59.820> nothing<00:17:00.300> happened<00:17:00.600> and<00:17:01.199> so<00:17:01.380> from<00:17:01.680> the 00:17:01.790 --> 00:17:01.800 align:start position:0% match nothing happened and so from the 00:17:01.800 --> 00:17:04.309 align:start position:0% match nothing happened and so from the user<00:17:02.040> specific<00:17:02.399> it<00:17:02.940> seems<00:17:03.240> it<00:17:03.480> seems<00:17:03.959> like<00:17:04.020> the 00:17:04.309 --> 00:17:04.319 align:start position:0% user specific it seems it seems like the 00:17:04.319 --> 00:17:05.870 align:start position:0% user specific it seems it seems like the transaction<00:17:04.799> was<00:17:05.100> essentially<00:17:05.400> executed 00:17:05.870 --> 00:17:05.880 align:start position:0% transaction was essentially executed 00:17:05.880 --> 00:17:08.110 align:start position:0% transaction was essentially executed instantly<00:17:06.299> which<00:17:06.839> like<00:17:07.079> gives<00:17:07.319> way<00:17:07.500> better<00:17:07.679> ux 00:17:08.110 --> 00:17:08.120 align:start position:0% instantly which like gives way better ux 00:17:08.120 --> 00:17:10.970 align:start position:0% instantly which like gives way better ux and<00:17:09.120> when<00:17:09.419> it's<00:17:09.600> not<00:17:09.780> the<00:17:09.900> case<00:17:10.079> when<00:17:10.740> the 00:17:10.970 --> 00:17:10.980 align:start position:0% and when it's not the case when the 00:17:10.980 --> 00:17:13.370 align:start position:0% and when it's not the case when the prediction<00:17:11.280> fails<00:17:11.760> so<00:17:12.120> as<00:17:12.240> an<00:17:12.419> example<00:17:12.660> if 00:17:13.370 --> 00:17:13.380 align:start position:0% prediction fails so as an example if 00:17:13.380 --> 00:17:14.990 align:start position:0% prediction fails so as an example if someone<00:17:13.620> else<00:17:13.860> kind<00:17:14.160> of<00:17:14.280> like<00:17:14.339> Clash<00:17:14.640> with<00:17:14.819> our 00:17:14.990 --> 00:17:15.000 align:start position:0% someone else kind of like Clash with our 00:17:15.000 --> 00:17:16.010 align:start position:0% someone else kind of like Clash with our state 00:17:16.010 --> 00:17:16.020 align:start position:0% state 00:17:16.020 --> 00:17:17.689 align:start position:0% state by<00:17:16.559> having<00:17:16.740> their<00:17:16.980> transaction<00:17:17.280> execute 00:17:17.689 --> 00:17:17.699 align:start position:0% by having their transaction execute 00:17:17.699 --> 00:17:19.549 align:start position:0% by having their transaction execute before<00:17:17.819> ORS<00:17:18.299> or<00:17:18.540> if<00:17:18.720> we're<00:17:18.839> behind<00:17:19.140> the<00:17:19.260> tip<00:17:19.439> of 00:17:19.549 --> 00:17:19.559 align:start position:0% before ORS or if we're behind the tip of 00:17:19.559 --> 00:17:21.110 align:start position:0% before ORS or if we're behind the tip of the<00:17:19.679> chain<00:17:19.860> we<00:17:20.400> just<00:17:20.520> revert<00:17:20.880> the<00:17:21.000> side 00:17:21.110 --> 00:17:21.120 align:start position:0% the chain we just revert the side 00:17:21.120 --> 00:17:22.970 align:start position:0% the chain we just revert the side effects<00:17:21.419> and<00:17:21.540> apply<00:17:21.780> the<00:17:21.959> actual<00:17:22.140> ones<00:17:22.500> and 00:17:22.970 --> 00:17:22.980 align:start position:0% effects and apply the actual ones and 00:17:22.980 --> 00:17:24.230 align:start position:0% effects and apply the actual ones and but<00:17:23.100> that<00:17:23.280> happens<00:17:23.459> like<00:17:23.760> quite<00:17:24.000> rarely 00:17:24.230 --> 00:17:24.240 align:start position:0% but that happens like quite rarely 00:17:24.240 --> 00:17:26.030 align:start position:0% but that happens like quite rarely actually<00:17:24.419> this<00:17:24.900> is<00:17:24.959> how<00:17:25.140> modern<00:17:25.319> MMOs<00:17:25.799> work 00:17:26.030 --> 00:17:26.040 align:start position:0% actually this is how modern MMOs work 00:17:26.040 --> 00:17:27.470 align:start position:0% actually this is how modern MMOs work they<00:17:26.220> do<00:17:26.339> prediction<00:17:26.579> in<00:17:26.760> Roblox<00:17:26.939> all<00:17:27.360> the 00:17:27.470 --> 00:17:27.480 align:start position:0% they do prediction in Roblox all the 00:17:27.480 --> 00:17:28.909 align:start position:0% they do prediction in Roblox all the time 00:17:28.909 --> 00:17:28.919 align:start position:0% time 00:17:28.919 --> 00:17:30.650 align:start position:0% time um so<00:17:29.400> yeah<00:17:29.520> with<00:17:29.760> mud<00:17:29.940> you<00:17:30.179> can<00:17:30.299> essentially 00:17:30.650 --> 00:17:30.660 align:start position:0% um so yeah with mud you can essentially 00:17:30.660 --> 00:17:32.210 align:start position:0% um so yeah with mud you can essentially read<00:17:30.900> and<00:17:31.140> index<00:17:31.440> components<00:17:32.040> without 00:17:32.210 --> 00:17:32.220 align:start position:0% read and index components without 00:17:32.220 --> 00:17:34.190 align:start position:0% read and index components without network<00:17:32.520> delay<00:17:32.940> client-side<00:17:33.419> and<00:17:33.960> you<00:17:34.080> can 00:17:34.190 --> 00:17:34.200 align:start position:0% network delay client-side and you can 00:17:34.200 --> 00:17:35.810 align:start position:0% network delay client-side and you can also<00:17:34.620> simulate<00:17:34.980> transactions<00:17:35.580> without 00:17:35.810 --> 00:17:35.820 align:start position:0% also simulate transactions without 00:17:35.820 --> 00:17:37.190 align:start position:0% also simulate transactions without waiting 00:17:37.190 --> 00:17:37.200 align:start position:0% waiting 00:17:37.200 --> 00:17:39.289 align:start position:0% waiting um<00:17:37.260> and<00:17:37.500> we<00:17:37.620> think<00:17:37.799> that<00:17:38.039> oh<00:17:38.400> sorry<00:17:38.700> we<00:17:39.120> think 00:17:39.289 --> 00:17:39.299 align:start position:0% um and we think that oh sorry we think 00:17:39.299 --> 00:17:41.990 align:start position:0% um and we think that oh sorry we think that<00:17:39.539> this<00:17:40.200> actual<00:17:40.559> like<00:17:40.799> increase<00:17:41.160> in<00:17:41.580> user 00:17:41.990 --> 00:17:42.000 align:start position:0% that this actual like increase in user 00:17:42.000 --> 00:17:44.630 align:start position:0% that this actual like increase in user experience<00:17:42.360> is<00:17:42.900> pretty<00:17:43.380> insane<00:17:43.860> we've<00:17:44.520> seen 00:17:44.630 --> 00:17:44.640 align:start position:0% experience is pretty insane we've seen 00:17:44.640 --> 00:17:45.890 align:start position:0% experience is pretty insane we've seen it<00:17:44.760> for<00:17:44.880> games<00:17:45.059> because<00:17:45.299> that's<00:17:45.480> what<00:17:45.720> we're 00:17:45.890 --> 00:17:45.900 align:start position:0% it for games because that's what we're 00:17:45.900 --> 00:17:48.409 align:start position:0% it for games because that's what we're trying<00:17:46.140> to<00:17:46.260> do<00:17:46.380> but<00:17:46.740> I'm<00:17:47.400> I<00:17:47.640> can't<00:17:48.120> wait<00:17:48.299> for 00:17:48.409 --> 00:17:48.419 align:start position:0% trying to do but I'm I can't wait for 00:17:48.419 --> 00:17:50.270 align:start position:0% trying to do but I'm I can't wait for someone<00:17:48.539> to<00:17:48.780> build<00:17:48.900> a<00:17:49.020> D5<00:17:49.260> protocol<00:17:49.620> mode<00:17:50.039> and 00:17:50.270 --> 00:17:50.280 align:start position:0% someone to build a D5 protocol mode and 00:17:50.280 --> 00:17:52.730 align:start position:0% someone to build a D5 protocol mode and make<00:17:50.580> it<00:17:50.760> like<00:17:50.940> the<00:17:51.360> the<00:17:51.539> snap<00:17:51.960> yes<00:17:52.260> swapping 00:17:52.730 --> 00:17:52.740 align:start position:0% make it like the the snap yes swapping 00:17:52.740 --> 00:17:54.409 align:start position:0% make it like the the snap yes swapping protocol<00:17:52.980> ever 00:17:54.409 --> 00:17:54.419 align:start position:0% protocol ever 00:17:54.419 --> 00:17:55.130 align:start position:0% protocol ever um 00:17:55.130 --> 00:17:55.140 align:start position:0% um 00:17:55.140 --> 00:17:56.750 align:start position:0% um another<00:17:55.559> thing<00:17:55.860> I'd<00:17:55.919> like<00:17:56.100> to<00:17:56.160> talk<00:17:56.280> about<00:17:56.400> is 00:17:56.750 --> 00:17:56.760 align:start position:0% another thing I'd like to talk about is 00:17:56.760 --> 00:17:59.450 align:start position:0% another thing I'd like to talk about is is<00:17:57.059> this<00:17:57.419> like<00:17:58.020> concept<00:17:58.500> of<00:17:58.679> extending<00:17:59.220> words 00:17:59.450 --> 00:17:59.460 align:start position:0% is this like concept of extending words 00:17:59.460 --> 00:18:02.270 align:start position:0% is this like concept of extending words with<00:17:59.760> mud<00:18:00.059> so 00:18:02.270 --> 00:18:02.280 align:start position:0% with mud so 00:18:02.280 --> 00:18:04.490 align:start position:0% with mud so today<00:18:02.880> with<00:18:03.360> like<00:18:03.660> fully<00:18:03.960> Unchained 00:18:04.490 --> 00:18:04.500 align:start position:0% today with like fully Unchained 00:18:04.500 --> 00:18:06.529 align:start position:0% today with like fully Unchained permission<00:18:04.740> is<00:18:05.039> up<00:18:05.220> things<00:18:05.520> like<00:18:05.700> uniswap<00:18:06.360> or 00:18:06.529 --> 00:18:06.539 align:start position:0% permission is up things like uniswap or 00:18:06.539 --> 00:18:08.090 align:start position:0% permission is up things like uniswap or dark<00:18:06.600> phrase<00:18:07.020> developers<00:18:07.620> can<00:18:07.740> extend<00:18:07.980> the 00:18:08.090 --> 00:18:08.100 align:start position:0% dark phrase developers can extend the 00:18:08.100 --> 00:18:09.830 align:start position:0% dark phrase developers can extend the protocol<00:18:08.400> via<00:18:08.880> new<00:18:09.059> contracts<00:18:09.539> and<00:18:09.720> custom 00:18:09.830 --> 00:18:09.840 align:start position:0% protocol via new contracts and custom 00:18:09.840 --> 00:18:11.390 align:start position:0% protocol via new contracts and custom client<00:18:10.200> right<00:18:10.380> that's<00:18:10.620> the<00:18:10.860> power<00:18:11.039> of<00:18:11.280> those 00:18:11.390 --> 00:18:11.400 align:start position:0% client right that's the power of those 00:18:11.400 --> 00:18:13.130 align:start position:0% client right that's the power of those applications<00:18:11.820> so<00:18:12.419> as<00:18:12.480> an<00:18:12.660> example<00:18:12.840> in<00:18:12.960> unit 00:18:13.130 --> 00:18:13.140 align:start position:0% applications so as an example in unit 00:18:13.140 --> 00:18:14.690 align:start position:0% applications so as an example in unit swap<00:18:13.500> you<00:18:13.740> can<00:18:13.860> build 00:18:14.690 --> 00:18:14.700 align:start position:0% swap you can build 00:18:14.700 --> 00:18:17.690 align:start position:0% swap you can build an<00:18:15.240> LP<00:18:15.600> kind<00:18:16.020> of<00:18:16.140> like<00:18:16.260> liquidity 00:18:17.690 --> 00:18:17.700 align:start position:0% an LP kind of like liquidity 00:18:17.700 --> 00:18:19.850 align:start position:0% an LP kind of like liquidity um mining<00:18:18.179> program<00:18:18.419> on<00:18:19.140> top<00:18:19.260> of<00:18:19.380> uniswap 00:18:19.850 --> 00:18:19.860 align:start position:0% um mining program on top of uniswap 00:18:19.860 --> 00:18:21.130 align:start position:0% um mining program on top of uniswap permissionlessly<00:18:20.400> you<00:18:20.520> don't<00:18:20.580> have<00:18:20.700> to<00:18:20.880> like 00:18:21.130 --> 00:18:21.140 align:start position:0% permissionlessly you don't have to like 00:18:21.140 --> 00:18:23.510 align:start position:0% permissionlessly you don't have to like phone<00:18:22.140> the<00:18:22.440> uni<00:18:22.740> swap<00:18:22.919> company<00:18:23.100> in<00:18:23.280> New<00:18:23.400> York 00:18:23.510 --> 00:18:23.520 align:start position:0% phone the uni swap company in New York 00:18:23.520 --> 00:18:25.310 align:start position:0% phone the uni swap company in New York to<00:18:23.640> ask<00:18:23.760> if<00:18:23.880> you<00:18:24.059> can<00:18:24.120> do<00:18:24.240> that<00:18:24.419> similarly<00:18:24.960> with 00:18:25.310 --> 00:18:25.320 align:start position:0% to ask if you can do that similarly with 00:18:25.320 --> 00:18:27.230 align:start position:0% to ask if you can do that similarly with dark<00:18:25.500> Forest<00:18:25.980> you<00:18:26.580> can<00:18:26.640> create<00:18:26.940> smart 00:18:27.230 --> 00:18:27.240 align:start position:0% dark Forest you can create smart 00:18:27.240 --> 00:18:29.630 align:start position:0% dark Forest you can create smart contract<00:18:27.600> players<00:18:27.900> or<00:18:28.080> new<00:18:28.320> features 00:18:29.630 --> 00:18:29.640 align:start position:0% contract players or new features 00:18:29.640 --> 00:18:31.250 align:start position:0% contract players or new features um however<00:18:30.539> the<00:18:30.720> problem<00:18:30.900> is<00:18:31.080> that 00:18:31.250 --> 00:18:31.260 align:start position:0% um however the problem is that 00:18:31.260 --> 00:18:33.110 align:start position:0% um however the problem is that developers<00:18:31.860> that<00:18:32.280> do<00:18:32.460> that<00:18:32.640> they<00:18:32.880> need<00:18:33.000> to 00:18:33.110 --> 00:18:33.120 align:start position:0% developers that do that they need to 00:18:33.120 --> 00:18:34.789 align:start position:0% developers that do that they need to ship<00:18:33.360> new<00:18:33.600> clients<00:18:33.900> and<00:18:34.020> indexers<00:18:34.500> when<00:18:34.679> they 00:18:34.789 --> 00:18:34.799 align:start position:0% ship new clients and indexers when they 00:18:34.799 --> 00:18:35.690 align:start position:0% ship new clients and indexers when they do<00:18:34.980> that 00:18:35.690 --> 00:18:35.700 align:start position:0% do that 00:18:35.700 --> 00:18:36.710 align:start position:0% do that um so<00:18:35.820> as<00:18:35.940> an<00:18:36.000> example<00:18:36.179> if<00:18:36.360> you<00:18:36.480> want<00:18:36.600> to<00:18:36.660> build 00:18:36.710 --> 00:18:36.720 align:start position:0% um so as an example if you want to build 00:18:36.720 --> 00:18:38.150 align:start position:0% um so as an example if you want to build a<00:18:36.840> yield<00:18:37.020> like<00:18:37.140> sorry<00:18:37.500> not<00:18:37.679> a<00:18:37.740> yield<00:18:37.919> agree 00:18:38.150 --> 00:18:38.160 align:start position:0% a yield like sorry not a yield agree 00:18:38.160 --> 00:18:39.770 align:start position:0% a yield like sorry not a yield agree there<00:18:38.340> a<00:18:38.520> swapping<00:18:38.880> kind<00:18:39.059> of<00:18:39.179> like<00:18:39.299> aggregator 00:18:39.770 --> 00:18:39.780 align:start position:0% there a swapping kind of like aggregator 00:18:39.780 --> 00:18:41.570 align:start position:0% there a swapping kind of like aggregator that<00:18:40.320> finds<00:18:40.559> the<00:18:40.620> best<00:18:40.799> prices<00:18:40.980> well<00:18:41.340> you<00:18:41.460> need 00:18:41.570 --> 00:18:41.580 align:start position:0% that finds the best prices well you need 00:18:41.580 --> 00:18:43.190 align:start position:0% that finds the best prices well you need to<00:18:41.640> build<00:18:41.820> one<00:18:42.059> inch<00:18:42.419> you<00:18:42.660> need<00:18:42.840> to<00:18:42.960> build<00:18:43.020> a 00:18:43.190 --> 00:18:43.200 align:start position:0% to build one inch you need to build a 00:18:43.200 --> 00:18:46.310 align:start position:0% to build one inch you need to build a new<00:18:43.260> client<00:18:44.059> also<00:18:45.059> users<00:18:45.419> need<00:18:45.660> to<00:18:45.840> know<00:18:45.960> where 00:18:46.310 --> 00:18:46.320 align:start position:0% new client also users need to know where 00:18:46.320 --> 00:18:48.409 align:start position:0% new client also users need to know where those<00:18:46.559> new<00:18:46.740> features<00:18:47.100> are<00:18:47.340> they<00:18:47.700> have<00:18:47.940> no<00:18:48.120> idea 00:18:48.409 --> 00:18:48.419 align:start position:0% those new features are they have no idea 00:18:48.419 --> 00:18:49.789 align:start position:0% those new features are they have no idea that<00:18:48.660> someone<00:18:48.840> out<00:18:49.140> there<00:18:49.260> built<00:18:49.679> new 00:18:49.789 --> 00:18:49.799 align:start position:0% that someone out there built new 00:18:49.799 --> 00:18:51.350 align:start position:0% that someone out there built new contracts<00:18:50.220> and<00:18:50.400> new<00:18:50.580> features<00:18:50.880> for<00:18:51.120> that 00:18:51.350 --> 00:18:51.360 align:start position:0% contracts and new features for that 00:18:51.360 --> 00:18:53.090 align:start position:0% contracts and new features for that specific<00:18:51.600> d-app 00:18:53.090 --> 00:18:53.100 align:start position:0% specific d-app 00:18:53.100 --> 00:18:55.130 align:start position:0% specific d-app um<00:18:53.160> and<00:18:54.000> that<00:18:54.240> actually<00:18:54.419> creates<00:18:54.780> a<00:18:54.960> clear 00:18:55.130 --> 00:18:55.140 align:start position:0% um and that actually creates a clear 00:18:55.140 --> 00:18:57.049 align:start position:0% um and that actually creates a clear distinction<00:18:55.559> between<00:18:55.919> first<00:18:56.280> party<00:18:56.580> code<00:18:56.820> and 00:18:57.049 --> 00:18:57.059 align:start position:0% distinction between first party code and 00:18:57.059 --> 00:18:59.090 align:start position:0% distinction between first party code and third-party<00:18:57.660> code<00:18:57.840> which<00:18:58.500> in<00:18:58.679> our<00:18:58.799> opinion 00:18:59.090 --> 00:18:59.100 align:start position:0% third-party code which in our opinion 00:18:59.100 --> 00:19:01.669 align:start position:0% third-party code which in our opinion like<00:18:59.340> greatly<00:18:59.880> hurt<00:19:00.179> like<00:19:00.960> interoperability 00:19:01.669 --> 00:19:01.679 align:start position:0% like greatly hurt like interoperability 00:19:01.679 --> 00:19:05.029 align:start position:0% like greatly hurt like interoperability and<00:19:02.039> like<00:19:02.220> creativity<00:19:02.760> so<00:19:03.660> as<00:19:04.380> an<00:19:04.500> example<00:19:04.799> in 00:19:05.029 --> 00:19:05.039 align:start position:0% and like creativity so as an example in 00:19:05.039 --> 00:19:07.490 align:start position:0% and like creativity so as an example in dark<00:19:05.220> first<00:19:05.460> you<00:19:05.700> can<00:19:05.820> do<00:19:05.880> something<00:19:06.059> like<00:19:06.240> hey 00:19:07.490 --> 00:19:07.500 align:start position:0% dark first you can do something like hey 00:19:07.500 --> 00:19:10.250 align:start position:0% dark first you can do something like hey um<00:19:07.620> I'm<00:19:07.919> team<00:19:08.280> XYZ<00:19:09.120> and<00:19:09.480> I'm<00:19:09.600> going<00:19:09.720> to<00:19:09.840> deploy 00:19:10.250 --> 00:19:10.260 align:start position:0% um I'm team XYZ and I'm going to deploy 00:19:10.260 --> 00:19:12.350 align:start position:0% um I'm team XYZ and I'm going to deploy a<00:19:10.679> thing<00:19:10.860> that<00:19:11.220> marks<00:19:11.640> some<00:19:11.760> planets<00:19:12.179> as 00:19:12.350 --> 00:19:12.360 align:start position:0% a thing that marks some planets as 00:19:12.360 --> 00:19:14.270 align:start position:0% a thing that marks some planets as rewarding<00:19:12.900> and<00:19:13.380> if<00:19:13.500> there's<00:19:13.740> captures<00:19:14.160> them 00:19:14.270 --> 00:19:14.280 align:start position:0% rewarding and if there's captures them 00:19:14.280 --> 00:19:16.370 align:start position:0% rewarding and if there's captures them they<00:19:14.460> get<00:19:14.640> some<00:19:15.000> eth<00:19:15.360> that's<00:19:15.840> pretty<00:19:16.020> cool<00:19:16.200> you 00:19:16.370 --> 00:19:16.380 align:start position:0% they get some eth that's pretty cool you 00:19:16.380 --> 00:19:19.070 align:start position:0% they get some eth that's pretty cool you can<00:19:16.500> do<00:19:16.620> that<00:19:16.740> but<00:19:17.280> now<00:19:17.460> how<00:19:18.360> do<00:19:18.480> user<00:19:18.840> know 00:19:19.070 --> 00:19:19.080 align:start position:0% can do that but now how do user know 00:19:19.080 --> 00:19:21.590 align:start position:0% can do that but now how do user know that<00:19:19.320> this<00:19:19.500> exists<00:19:19.980> right<00:19:20.520> like<00:19:20.940> where<00:19:21.419> are 00:19:21.590 --> 00:19:21.600 align:start position:0% that this exists right like where are 00:19:21.600 --> 00:19:24.049 align:start position:0% that this exists right like where are the<00:19:21.720> contracts<00:19:22.200> how<00:19:22.740> do<00:19:22.860> you<00:19:22.980> like<00:19:23.280> even<00:19:23.820> if 00:19:24.049 --> 00:19:24.059 align:start position:0% the contracts how do you like even if 00:19:24.059 --> 00:19:25.549 align:start position:0% the contracts how do you like even if you<00:19:24.179> had<00:19:24.299> that<00:19:24.539> information<00:19:24.780> in<00:19:25.200> your<00:19:25.380> client 00:19:25.549 --> 00:19:25.559 align:start position:0% you had that information in your client 00:19:25.559 --> 00:19:27.049 align:start position:0% you had that information in your client how<00:19:25.919> does<00:19:26.100> your<00:19:26.280> client<00:19:26.520> know<00:19:26.640> what<00:19:26.820> to<00:19:26.940> do 00:19:27.049 --> 00:19:27.059 align:start position:0% how does your client know what to do 00:19:27.059 --> 00:19:28.610 align:start position:0% how does your client know what to do with<00:19:27.179> that<00:19:27.299> data<00:19:27.600> does<00:19:27.840> it<00:19:28.020> render<00:19:28.200> a<00:19:28.440> button 00:19:28.610 --> 00:19:28.620 align:start position:0% with that data does it render a button 00:19:28.620 --> 00:19:30.409 align:start position:0% with that data does it render a button does<00:19:28.860> it<00:19:29.039> trigger<00:19:29.280> a<00:19:29.400> Shader 00:19:30.409 --> 00:19:30.419 align:start position:0% does it trigger a Shader 00:19:30.419 --> 00:19:31.310 align:start position:0% does it trigger a Shader um similarly<00:19:30.840> you<00:19:30.960> probably<00:19:31.080> have<00:19:31.200> to 00:19:31.310 --> 00:19:31.320 align:start position:0% um similarly you probably have to 00:19:31.320 --> 00:19:32.870 align:start position:0% um similarly you probably have to rebuild<00:19:31.620> all<00:19:31.679> your<00:19:31.799> indexer<00:19:32.160> from<00:19:32.340> scratch<00:19:32.580> so 00:19:32.870 --> 00:19:32.880 align:start position:0% rebuild all your indexer from scratch so 00:19:32.880 --> 00:19:34.370 align:start position:0% rebuild all your indexer from scratch so you<00:19:33.059> get<00:19:33.179> a<00:19:33.299> fragmentation<00:19:33.840> essentially 00:19:34.370 --> 00:19:34.380 align:start position:0% you get a fragmentation essentially 00:19:34.380 --> 00:19:36.110 align:start position:0% you get a fragmentation essentially between<00:19:34.620> first<00:19:34.919> party<00:19:35.160> code<00:19:35.460> and<00:19:35.580> third-party 00:19:36.110 --> 00:19:36.120 align:start position:0% between first party code and third-party 00:19:36.120 --> 00:19:37.010 align:start position:0% between first party code and third-party code 00:19:37.010 --> 00:19:37.020 align:start position:0% code 00:19:37.020 --> 00:19:39.169 align:start position:0% code so<00:19:37.320> again<00:19:37.440> can<00:19:37.740> we<00:19:37.860> do<00:19:37.980> better 00:19:39.169 --> 00:19:39.179 align:start position:0% so again can we do better 00:19:39.179 --> 00:19:40.130 align:start position:0% so again can we do better um 00:19:40.130 --> 00:19:40.140 align:start position:0% um 00:19:40.140 --> 00:19:42.650 align:start position:0% um in<00:19:40.740> mud<00:19:40.919> the<00:19:41.520> central<00:19:41.640> contract<00:19:42.179> is<00:19:42.360> the<00:19:42.539> word 00:19:42.650 --> 00:19:42.660 align:start position:0% in mud the central contract is the word 00:19:42.660 --> 00:19:44.450 align:start position:0% in mud the central contract is the word contract<00:19:43.080> if<00:19:43.559> you<00:19:43.620> know<00:19:43.799> the<00:19:43.980> address<00:19:44.160> of<00:19:44.400> the 00:19:44.450 --> 00:19:44.460 align:start position:0% contract if you know the address of the 00:19:44.460 --> 00:19:45.590 align:start position:0% contract if you know the address of the word<00:19:44.580> contract<00:19:44.880> you<00:19:45.059> know<00:19:45.179> everything<00:19:45.360> you 00:19:45.590 --> 00:19:45.600 align:start position:0% word contract you know everything you 00:19:45.600 --> 00:19:46.789 align:start position:0% word contract you know everything you know<00:19:45.720> about<00:19:45.840> all<00:19:46.080> the<00:19:46.200> components<00:19:46.559> you<00:19:46.679> know 00:19:46.789 --> 00:19:46.799 align:start position:0% know about all the components you know 00:19:46.799 --> 00:19:48.049 align:start position:0% know about all the components you know about<00:19:46.919> all<00:19:47.100> the<00:19:47.280> systems<00:19:47.520> you<00:19:47.640> know<00:19:47.760> about<00:19:47.820> all 00:19:48.049 --> 00:19:48.059 align:start position:0% about all the systems you know about all 00:19:48.059 --> 00:19:49.190 align:start position:0% about all the systems you know about all the<00:19:48.179> entities 00:19:49.190 --> 00:19:49.200 align:start position:0% the entities 00:19:49.200 --> 00:19:50.510 align:start position:0% the entities and<00:19:49.620> the<00:19:49.740> thing<00:19:49.860> that<00:19:49.980> is<00:19:50.160> interesting<00:19:50.340> with 00:19:50.510 --> 00:19:50.520 align:start position:0% and the thing that is interesting with 00:19:50.520 --> 00:19:51.890 align:start position:0% and the thing that is interesting with the<00:19:50.640> word<00:19:50.760> contract<00:19:51.120> is<00:19:51.240> that<00:19:51.419> it's<00:19:51.660> it 00:19:51.890 --> 00:19:51.900 align:start position:0% the word contract is that it's it 00:19:51.900 --> 00:19:53.810 align:start position:0% the word contract is that it's it actually<00:19:52.080> has<00:19:52.320> no<00:19:52.559> owner 00:19:53.810 --> 00:19:53.820 align:start position:0% actually has no owner 00:19:53.820 --> 00:19:56.810 align:start position:0% actually has no owner um<00:19:53.940> if<00:19:54.299> you<00:19:54.480> deploy<00:19:54.960> yeah<00:19:55.679> so<00:19:55.919> it<00:19:56.160> has<00:19:56.280> no<00:19:56.460> owner 00:19:56.810 --> 00:19:56.820 align:start position:0% um if you deploy yeah so it has no owner 00:19:56.820 --> 00:19:58.430 align:start position:0% um if you deploy yeah so it has no owner it's<00:19:57.000> permissionless<00:19:57.600> and<00:19:58.020> so<00:19:58.140> that<00:19:58.260> means 00:19:58.430 --> 00:19:58.440 align:start position:0% it's permissionless and so that means 00:19:58.440 --> 00:19:59.450 align:start position:0% it's permissionless and so that means there<00:19:58.559> is<00:19:58.679> no<00:19:58.799> difference<00:19:58.919> between<00:19:59.160> first 00:19:59.450 --> 00:19:59.460 align:start position:0% there is no difference between first 00:19:59.460 --> 00:20:00.890 align:start position:0% there is no difference between first party<00:19:59.700> code<00:19:59.940> and<00:20:00.120> third-party<00:20:00.539> code<00:20:00.660> anymore 00:20:00.890 --> 00:20:00.900 align:start position:0% party code and third-party code anymore 00:20:00.900 --> 00:20:03.890 align:start position:0% party code and third-party code anymore everybody's<00:20:01.799> first<00:20:02.160> party<00:20:02.460> so<00:20:03.299> the<00:20:03.600> creators 00:20:03.890 --> 00:20:03.900 align:start position:0% everybody's first party so the creators 00:20:03.900 --> 00:20:05.570 align:start position:0% everybody's first party so the creators of<00:20:04.080> the<00:20:04.200> world<00:20:04.320> contract<00:20:04.740> the<00:20:05.039> deployers<00:20:05.460> of 00:20:05.570 --> 00:20:05.580 align:start position:0% of the world contract the deployers of 00:20:05.580 --> 00:20:07.070 align:start position:0% of the world contract the deployers of that<00:20:05.700> contract<00:20:06.000> actually<00:20:06.240> have<00:20:06.480> no<00:20:06.780> special 00:20:07.070 --> 00:20:07.080 align:start position:0% that contract actually have no special 00:20:07.080 --> 00:20:08.870 align:start position:0% that contract actually have no special kind<00:20:07.440> of<00:20:07.559> access<00:20:07.740> to<00:20:08.039> it<00:20:08.220> they're<00:20:08.640> not 00:20:08.870 --> 00:20:08.880 align:start position:0% kind of access to it they're not 00:20:08.880 --> 00:20:10.490 align:start position:0% kind of access to it they're not privileged<00:20:09.360> in<00:20:09.480> any<00:20:09.720> mean 00:20:10.490 --> 00:20:10.500 align:start position:0% privileged in any mean 00:20:10.500 --> 00:20:12.950 align:start position:0% privileged in any mean um<00:20:10.559> the<00:20:10.679> word<00:20:10.799> contract<00:20:11.100> is<00:20:11.220> non-upgradable 00:20:12.950 --> 00:20:12.960 align:start position:0% um the word contract is non-upgradable 00:20:12.960 --> 00:20:15.350 align:start position:0% um the word contract is non-upgradable so<00:20:13.380> the<00:20:13.500> rule<00:20:13.740> is<00:20:13.860> anyone<00:20:14.520> can<00:20:15.120> create 00:20:15.350 --> 00:20:15.360 align:start position:0% so the rule is anyone can create 00:20:15.360 --> 00:20:17.750 align:start position:0% so the rule is anyone can create components<00:20:15.900> and<00:20:16.080> systems<00:20:16.500> so<00:20:17.039> when<00:20:17.220> Alvarez 00:20:17.750 --> 00:20:17.760 align:start position:0% components and systems so when Alvarez 00:20:17.760 --> 00:20:19.070 align:start position:0% components and systems so when Alvarez was<00:20:17.940> talking<00:20:18.059> earlier<00:20:18.419> about<00:20:18.660> the<00:20:18.900> health 00:20:19.070 --> 00:20:19.080 align:start position:0% was talking earlier about the health 00:20:19.080 --> 00:20:20.810 align:start position:0% was talking earlier about the health component<00:20:19.559> and<00:20:19.679> position<00:20:19.980> component<00:20:20.580> and<00:20:20.700> the 00:20:20.810 --> 00:20:20.820 align:start position:0% component and position component and the 00:20:20.820 --> 00:20:22.610 align:start position:0% component and position component and the move<00:20:21.000> system<00:20:21.240> anyone<00:20:21.960> can<00:20:22.080> register<00:20:22.320> those 00:20:22.610 --> 00:20:22.620 align:start position:0% move system anyone can register those 00:20:22.620 --> 00:20:23.990 align:start position:0% move system anyone can register those components<00:20:22.980> in<00:20:23.100> those<00:20:23.220> systems<00:20:23.520> on<00:20:23.700> the<00:20:23.880> world 00:20:23.990 --> 00:20:24.000 align:start position:0% components in those systems on the world 00:20:24.000 --> 00:20:26.690 align:start position:0% components in those systems on the world itself<00:20:24.299> and 00:20:26.690 --> 00:20:26.700 align:start position:0% itself and 00:20:26.700 --> 00:20:28.430 align:start position:0% itself and when<00:20:27.299> you<00:20:27.480> do<00:20:27.600> that<00:20:27.780> when<00:20:27.960> you<00:20:28.080> create<00:20:28.200> new 00:20:28.430 --> 00:20:28.440 align:start position:0% when you do that when you create new 00:20:28.440 --> 00:20:30.350 align:start position:0% when you do that when you create new components<00:20:28.860> that<00:20:29.039> is<00:20:29.220> like<00:20:29.340> new<00:20:29.520> data<00:20:29.940> or<00:20:30.179> new 00:20:30.350 --> 00:20:30.360 align:start position:0% components that is like new data or new 00:20:30.360 --> 00:20:32.450 align:start position:0% components that is like new data or new systems<00:20:30.840> that<00:20:31.140> is<00:20:31.320> New<00:20:31.500> Logic<00:20:31.980> they're 00:20:32.450 --> 00:20:32.460 align:start position:0% systems that is New Logic they're 00:20:32.460 --> 00:20:34.130 align:start position:0% systems that is New Logic they're accessible<00:20:32.880> in<00:20:33.120> the<00:20:33.240> client<00:20:33.419> they're<00:20:33.720> indexed 00:20:34.130 --> 00:20:34.140 align:start position:0% accessible in the client they're indexed 00:20:34.140 --> 00:20:35.570 align:start position:0% accessible in the client they're indexed they<00:20:34.320> can<00:20:34.440> be<00:20:34.559> found<00:20:34.679> in<00:20:34.860> a<00:20:34.980> debugger<00:20:35.340> and<00:20:35.460> they 00:20:35.570 --> 00:20:35.580 align:start position:0% they can be found in a debugger and they 00:20:35.580 --> 00:20:37.370 align:start position:0% they can be found in a debugger and they can<00:20:35.640> be<00:20:35.760> executed<00:20:36.059> in<00:20:36.240> locally<00:20:36.480> VM<00:20:36.840> and 00:20:37.370 --> 00:20:37.380 align:start position:0% can be executed in locally VM and 00:20:37.380 --> 00:20:38.390 align:start position:0% can be executed in locally VM and there's<00:20:37.500> actually<00:20:37.679> no<00:20:37.919> difference<00:20:38.100> between 00:20:38.390 --> 00:20:38.400 align:start position:0% there's actually no difference between 00:20:38.400 --> 00:20:40.250 align:start position:0% there's actually no difference between like<00:20:38.760> what<00:20:39.120> the<00:20:39.299> core<00:20:39.419> team<00:20:39.660> deployed<00:20:40.080> and 00:20:40.250 --> 00:20:40.260 align:start position:0% like what the core team deployed and 00:20:40.260 --> 00:20:42.470 align:start position:0% like what the core team deployed and what<00:20:40.380> like<00:20:40.559> any<00:20:40.860> other<00:20:41.039> people<00:20:41.280> did<00:20:41.580> deploy<00:20:42.299> as 00:20:42.470 --> 00:20:42.480 align:start position:0% what like any other people did deploy as 00:20:42.480 --> 00:20:43.850 align:start position:0% what like any other people did deploy as well 00:20:43.850 --> 00:20:43.860 align:start position:0% well 00:20:43.860 --> 00:20:46.070 align:start position:0% well so<00:20:44.280> the<00:20:44.760> only<00:20:44.880> like<00:20:45.240> the<00:20:45.480> rule<00:20:45.660> is<00:20:45.720> that<00:20:45.900> all 00:20:46.070 --> 00:20:46.080 align:start position:0% so the only like the rule is that all 00:20:46.080 --> 00:20:48.169 align:start position:0% so the only like the rule is that all systems<00:20:46.500> can<00:20:46.620> read<00:20:46.799> from<00:20:46.980> any<00:20:47.160> components<00:20:47.700> so 00:20:48.169 --> 00:20:48.179 align:start position:0% systems can read from any components so 00:20:48.179 --> 00:20:49.669 align:start position:0% systems can read from any components so and<00:20:48.360> and<00:20:48.480> those<00:20:48.720> components<00:20:49.140> can<00:20:49.260> be<00:20:49.320> deployed 00:20:49.669 --> 00:20:49.679 align:start position:0% and and those components can be deployed 00:20:49.679 --> 00:20:51.409 align:start position:0% and and those components can be deployed by<00:20:49.740> different<00:20:49.919> teams<00:20:50.220> so<00:20:50.280> as<00:20:50.460> an<00:20:50.580> example<00:20:50.820> you 00:20:51.409 --> 00:20:51.419 align:start position:0% by different teams so as an example you 00:20:51.419 --> 00:20:53.270 align:start position:0% by different teams so as an example you could<00:20:51.539> write<00:20:51.840> a<00:20:52.020> system<00:20:52.200> that<00:20:52.559> runs<00:20:52.919> a<00:20:53.039> query 00:20:53.270 --> 00:20:53.280 align:start position:0% could write a system that runs a query 00:20:53.280 --> 00:20:54.890 align:start position:0% could write a system that runs a query on<00:20:53.460> the<00:20:53.640> world<00:20:53.760> that<00:20:54.059> queries<00:20:54.360> a<00:20:54.539> component 00:20:54.890 --> 00:20:54.900 align:start position:0% on the world that queries a component 00:20:54.900 --> 00:20:57.590 align:start position:0% on the world that queries a component developed<00:20:55.520> deployed<00:20:56.520> by<00:20:56.580> team<00:20:56.760> XYZ<00:20:57.240> and<00:20:57.480> a 00:20:57.590 --> 00:20:57.600 align:start position:0% developed deployed by team XYZ and a 00:20:57.600 --> 00:20:59.750 align:start position:0% developed deployed by team XYZ and a component<00:20:57.780> deployed<00:20:58.140> by<00:20:58.260> team<00:20:58.380> TTT<00:20:58.740> and<00:20:59.580> they 00:20:59.750 --> 00:20:59.760 align:start position:0% component deployed by team TTT and they 00:20:59.760 --> 00:21:00.830 align:start position:0% component deployed by team TTT and they can<00:20:59.880> actually<00:21:00.000> aggregate<00:21:00.419> those<00:21:00.539> data 00:21:00.830 --> 00:21:00.840 align:start position:0% can actually aggregate those data 00:21:00.840 --> 00:21:02.690 align:start position:0% can actually aggregate those data together<00:21:00.960> the<00:21:01.620> Only<00:21:01.679> Rule<00:21:02.160> is<00:21:02.580> that 00:21:02.690 --> 00:21:02.700 align:start position:0% together the Only Rule is that 00:21:02.700 --> 00:21:03.950 align:start position:0% together the Only Rule is that components<00:21:03.120> have<00:21:03.240> to<00:21:03.419> whitelist<00:21:03.840> which 00:21:03.950 --> 00:21:03.960 align:start position:0% components have to whitelist which 00:21:03.960 --> 00:21:05.450 align:start position:0% components have to whitelist which systems<00:21:04.260> can<00:21:04.440> write<00:21:04.559> to<00:21:04.679> their<00:21:04.860> states<00:21:05.039> and 00:21:05.450 --> 00:21:05.460 align:start position:0% systems can write to their states and 00:21:05.460 --> 00:21:06.169 align:start position:0% systems can write to their states and that's<00:21:05.580> really<00:21:05.760> important<00:21:06.059> because 00:21:06.169 --> 00:21:06.179 align:start position:0% that's really important because 00:21:06.179 --> 00:21:07.730 align:start position:0% that's really important because otherwise<00:21:06.600> an<00:21:06.840> attacker<00:21:07.140> could<00:21:07.380> deploy<00:21:07.620> A 00:21:07.730 --> 00:21:07.740 align:start position:0% otherwise an attacker could deploy A 00:21:07.740 --> 00:21:08.930 align:start position:0% otherwise an attacker could deploy A system<00:21:07.860> that<00:21:08.100> just<00:21:08.220> resets<00:21:08.460> everybody's 00:21:08.930 --> 00:21:08.940 align:start position:0% system that just resets everybody's 00:21:08.940 --> 00:21:11.210 align:start position:0% system that just resets everybody's inventories<00:21:09.480> so<00:21:10.140> the<00:21:10.500> way<00:21:10.559> it<00:21:10.679> looks<00:21:10.980> like<00:21:11.039> is 00:21:11.210 --> 00:21:11.220 align:start position:0% inventories so the way it looks like is 00:21:11.220 --> 00:21:12.890 align:start position:0% inventories so the way it looks like is you<00:21:11.400> have<00:21:11.580> this<00:21:11.820> this<00:21:12.120> like<00:21:12.360> graph<00:21:12.660> of 00:21:12.890 --> 00:21:12.900 align:start position:0% you have this this like graph of 00:21:12.900 --> 00:21:14.270 align:start position:0% you have this this like graph of components<00:21:13.380> and<00:21:13.500> systems<00:21:13.799> that<00:21:13.919> kind<00:21:14.100> of<00:21:14.220> like 00:21:14.270 --> 00:21:14.280 align:start position:0% components and systems that kind of like 00:21:14.280 --> 00:21:17.210 align:start position:0% components and systems that kind of like trust<00:21:14.580> each<00:21:14.760> other<00:21:14.940> but<00:21:15.720> also<00:21:16.080> you<00:21:16.679> have<00:21:16.860> this 00:21:17.210 --> 00:21:17.220 align:start position:0% trust each other but also you have this 00:21:17.220 --> 00:21:18.770 align:start position:0% trust each other but also you have this interesting<00:21:17.640> social<00:21:17.820> phenomena<00:21:18.419> as<00:21:18.600> where 00:21:18.770 --> 00:21:18.780 align:start position:0% interesting social phenomena as where 00:21:18.780 --> 00:21:20.990 align:start position:0% interesting social phenomena as where users<00:21:19.080> of<00:21:19.260> those<00:21:19.440> applications<00:21:19.799> decide<00:21:20.700> what 00:21:20.990 --> 00:21:21.000 align:start position:0% users of those applications decide what 00:21:21.000 --> 00:21:22.730 align:start position:0% users of those applications decide what is<00:21:21.179> real<00:21:21.419> so<00:21:22.020> if<00:21:22.140> you<00:21:22.260> have<00:21:22.380> two<00:21:22.500> position 00:21:22.730 --> 00:21:22.740 align:start position:0% is real so if you have two position 00:21:22.740 --> 00:21:25.070 align:start position:0% is real so if you have two position components<00:21:23.520> that<00:21:24.120> like<00:21:24.299> don't<00:21:24.539> match<00:21:24.780> with 00:21:25.070 --> 00:21:25.080 align:start position:0% components that like don't match with 00:21:25.080 --> 00:21:26.630 align:start position:0% components that like don't match with each<00:21:25.260> other<00:21:25.380> the<00:21:25.860> users<00:21:26.039> have<00:21:26.220> to<00:21:26.340> decide<00:21:26.580> okay 00:21:26.630 --> 00:21:26.640 align:start position:0% each other the users have to decide okay 00:21:26.640 --> 00:21:28.070 align:start position:0% each other the users have to decide okay do<00:21:26.820> we<00:21:26.940> believe<00:21:27.059> in<00:21:27.240> position<00:21:27.360> one<00:21:27.720> or<00:21:27.900> in 00:21:28.070 --> 00:21:28.080 align:start position:0% do we believe in position one or in 00:21:28.080 --> 00:21:29.510 align:start position:0% do we believe in position one or in position<00:21:28.260> two<00:21:28.559> and<00:21:28.980> that's<00:21:29.100> really<00:21:29.280> what 00:21:29.510 --> 00:21:29.520 align:start position:0% position two and that's really what 00:21:29.520 --> 00:21:31.070 align:start position:0% position two and that's really what happens<00:21:29.640> today<00:21:29.880> on<00:21:30.059> ethereum<00:21:30.419> if<00:21:30.600> I<00:21:30.720> deploy<00:21:30.900> a 00:21:31.070 --> 00:21:31.080 align:start position:0% happens today on ethereum if I deploy a 00:21:31.080 --> 00:21:34.130 align:start position:0% happens today on ethereum if I deploy a new<00:21:31.200> die<00:21:31.500> contract<00:21:32.039> my<00:21:32.460> die<00:21:32.640> is<00:21:32.880> worthless<00:21:33.240> so 00:21:34.130 --> 00:21:34.140 align:start position:0% new die contract my die is worthless so 00:21:34.140 --> 00:21:35.690 align:start position:0% new die contract my die is worthless so it's<00:21:34.380> all<00:21:34.559> based<00:21:34.919> on<00:21:34.980> essentially<00:21:35.340> what<00:21:35.580> you 00:21:35.690 --> 00:21:35.700 align:start position:0% it's all based on essentially what you 00:21:35.700 --> 00:21:38.810 align:start position:0% it's all based on essentially what you think<00:21:35.880> is<00:21:36.059> real<00:21:36.299> but<00:21:37.080> it<00:21:37.380> is<00:21:37.500> made<00:21:37.679> in<00:21:37.860> like<00:21:38.159> mud 00:21:38.810 --> 00:21:38.820 align:start position:0% think is real but it is made in like mud 00:21:38.820 --> 00:21:40.370 align:start position:0% think is real but it is made in like mud is<00:21:38.940> architected<00:21:39.480> in<00:21:39.659> such<00:21:39.780> a<00:21:39.900> way<00:21:40.020> that<00:21:40.200> you 00:21:40.370 --> 00:21:40.380 align:start position:0% is architected in such a way that you 00:21:40.380 --> 00:21:41.930 align:start position:0% is architected in such a way that you never<00:21:40.500> have<00:21:40.679> the<00:21:40.860> problem<00:21:41.039> or<00:21:41.400> you<00:21:41.760> need<00:21:41.820> to 00:21:41.930 --> 00:21:41.940 align:start position:0% never have the problem or you need to 00:21:41.940 --> 00:21:43.789 align:start position:0% never have the problem or you need to create<00:21:42.000> something<00:21:42.240> like<00:21:42.659> oh<00:21:43.260> like<00:21:43.440> we<00:21:43.559> need<00:21:43.679> to 00:21:43.789 --> 00:21:43.799 align:start position:0% create something like oh like we need to 00:21:43.799 --> 00:21:46.250 align:start position:0% create something like oh like we need to like<00:21:44.340> give<00:21:44.640> or<00:21:44.880> upgrade<00:21:45.299> keys<00:21:45.600> to<00:21:45.720> Dao<00:21:46.080> in 00:21:46.250 --> 00:21:46.260 align:start position:0% like give or upgrade keys to Dao in 00:21:46.260 --> 00:21:47.570 align:start position:0% like give or upgrade keys to Dao in order<00:21:46.380> to<00:21:46.500> let<00:21:46.620> our<00:21:46.799> players<00:21:47.039> upgrade<00:21:47.280> it<00:21:47.400> snow 00:21:47.570 --> 00:21:47.580 align:start position:0% order to let our players upgrade it snow 00:21:47.580 --> 00:21:48.950 align:start position:0% order to let our players upgrade it snow this<00:21:47.760> can<00:21:47.880> emerge<00:21:48.240> naturally<00:21:48.539> essentially 00:21:48.950 --> 00:21:48.960 align:start position:0% this can emerge naturally essentially 00:21:48.960 --> 00:21:50.750 align:start position:0% this can emerge naturally essentially from<00:21:49.559> the<00:21:49.679> web<00:21:49.799> of<00:21:49.980> trust<00:21:50.220> of<00:21:50.340> the<00:21:50.460> players 00:21:50.750 --> 00:21:50.760 align:start position:0% from the web of trust of the players 00:21:50.760 --> 00:21:52.430 align:start position:0% from the web of trust of the players themselves 00:21:52.430 --> 00:21:52.440 align:start position:0% themselves 00:21:52.440 --> 00:21:54.710 align:start position:0% themselves and<00:21:53.400> this<00:21:53.520> leads<00:21:53.820> us<00:21:53.880> into<00:21:54.059> like<00:21:54.360> an 00:21:54.710 --> 00:21:54.720 align:start position:0% and this leads us into like an 00:21:54.720 --> 00:21:56.330 align:start position:0% and this leads us into like an interesting<00:21:55.080> kind<00:21:55.440> of<00:21:55.559> like<00:21:55.620> idea<00:21:56.039> of 00:21:56.330 --> 00:21:56.340 align:start position:0% interesting kind of like idea of 00:21:56.340 --> 00:21:58.789 align:start position:0% interesting kind of like idea of augmented<00:21:56.820> reality<00:21:57.240> so<00:21:58.140> this<00:21:58.440> is<00:21:58.559> not<00:21:58.679> the 00:21:58.789 --> 00:21:58.799 align:start position:0% augmented reality so this is not the 00:21:58.799 --> 00:22:00.770 align:start position:0% augmented reality so this is not the augmented<00:21:59.280> reality<00:21:59.580> you<00:21:59.820> know<00:22:00.000> with<00:22:00.360> fancy 00:22:00.770 --> 00:22:00.780 align:start position:0% augmented reality you know with fancy 00:22:00.780 --> 00:22:02.750 align:start position:0% augmented reality you know with fancy glasses<00:22:01.200> and<00:22:01.380> Hardware<00:22:01.559> it's<00:22:02.340> more<00:22:02.640> about 00:22:02.750 --> 00:22:02.760 align:start position:0% glasses and Hardware it's more about 00:22:02.760 --> 00:22:05.930 align:start position:0% glasses and Hardware it's more about layering<00:22:03.919> Bayes<00:22:04.919> rules<00:22:05.220> with<00:22:05.760> new 00:22:05.930 --> 00:22:05.940 align:start position:0% layering Bayes rules with new 00:22:05.940 --> 00:22:07.370 align:start position:0% layering Bayes rules with new interpretations 00:22:07.370 --> 00:22:07.380 align:start position:0% interpretations 00:22:07.380 --> 00:22:09.950 align:start position:0% interpretations so<00:22:07.919> beyond<00:22:08.880> the<00:22:09.000> core<00:22:09.179> components<00:22:09.840> and 00:22:09.950 --> 00:22:09.960 align:start position:0% so beyond the core components and 00:22:09.960 --> 00:22:12.169 align:start position:0% so beyond the core components and systems<00:22:10.440> all<00:22:11.039> players<00:22:11.400> believe<00:22:11.700> in<00:22:11.880> probably 00:22:12.169 --> 00:22:12.179 align:start position:0% systems all players believe in probably 00:22:12.179 --> 00:22:13.610 align:start position:0% systems all players believe in probably the<00:22:12.360> ones<00:22:12.539> that<00:22:12.659> have<00:22:12.720> been<00:22:12.840> deployed<00:22:13.140> by<00:22:13.320> the 00:22:13.610 --> 00:22:13.620 align:start position:0% the ones that have been deployed by the 00:22:13.620 --> 00:22:16.370 align:start position:0% the ones that have been deployed by the core<00:22:13.799> team<00:22:14.039> the<00:22:14.280> low<00:22:14.400> level<00:22:14.520> physics<00:22:15.260> it<00:22:16.260> is 00:22:16.370 --> 00:22:16.380 align:start position:0% core team the low level physics it is 00:22:16.380 --> 00:22:18.950 align:start position:0% core team the low level physics it is possible<00:22:16.740> for<00:22:17.100> anyone<00:22:17.460> to<00:22:18.000> create<00:22:18.179> augmented 00:22:18.950 --> 00:22:18.960 align:start position:0% possible for anyone to create augmented 00:22:18.960 --> 00:22:21.169 align:start position:0% possible for anyone to create augmented reality<00:22:19.320> layers<00:22:19.740> that<00:22:20.159> only<00:22:20.340> a<00:22:20.580> subset<00:22:21.000> of 00:22:21.169 --> 00:22:21.179 align:start position:0% reality layers that only a subset of 00:22:21.179 --> 00:22:22.970 align:start position:0% reality layers that only a subset of players<00:22:21.600> engage<00:22:22.080> in<00:22:22.320> and<00:22:22.740> that 00:22:22.970 --> 00:22:22.980 align:start position:0% players engage in and that 00:22:22.980 --> 00:22:24.590 align:start position:0% players engage in and that permissionlessly<00:22:23.820> so<00:22:24.299> we're<00:22:24.419> going<00:22:24.480> to 00:22:24.590 --> 00:22:24.600 align:start position:0% permissionlessly so we're going to 00:22:24.600 --> 00:22:25.970 align:start position:0% permissionlessly so we're going to illustrate<00:22:24.960> this 00:22:25.970 --> 00:22:25.980 align:start position:0% illustrate this 00:22:25.980 --> 00:22:26.810 align:start position:0% illustrate this um 00:22:26.810 --> 00:22:26.820 align:start position:0% um 00:22:26.820 --> 00:22:29.510 align:start position:0% um imagine<00:22:27.480> a<00:22:28.320> game 00:22:29.510 --> 00:22:29.520 align:start position:0% imagine a game 00:22:29.520 --> 00:22:32.330 align:start position:0% imagine a game it's<00:22:29.820> a<00:22:29.940> very<00:22:30.120> simple<00:22:30.299> game<00:22:30.600> it<00:22:31.020> was<00:22:31.620> deployed 00:22:32.330 --> 00:22:32.340 align:start position:0% it's a very simple game it was deployed 00:22:32.340 --> 00:22:34.310 align:start position:0% it's a very simple game it was deployed by<00:22:32.460> the<00:22:32.580> like<00:22:33.000> one<00:22:33.299> core<00:22:33.480> team<00:22:33.780> it<00:22:34.020> has<00:22:34.140> three 00:22:34.310 --> 00:22:34.320 align:start position:0% by the like one core team it has three 00:22:34.320 --> 00:22:36.289 align:start position:0% by the like one core team it has three components<00:22:34.799> position<00:22:35.039> movable<00:22:35.640> and<00:22:35.880> resource 00:22:36.289 --> 00:22:36.299 align:start position:0% components position movable and resource 00:22:36.299 --> 00:22:38.210 align:start position:0% components position movable and resource there's<00:22:36.780> three<00:22:37.080> systems<00:22:37.500> you<00:22:37.740> can<00:22:37.860> move<00:22:38.039> you 00:22:38.210 --> 00:22:38.220 align:start position:0% there's three systems you can move you 00:22:38.220 --> 00:22:39.409 align:start position:0% there's three systems you can move you can<00:22:38.340> pick<00:22:38.460> up<00:22:38.580> a<00:22:38.760> resource<00:22:39.059> so<00:22:39.120> you<00:22:39.240> can<00:22:39.299> drop 00:22:39.409 --> 00:22:39.419 align:start position:0% can pick up a resource so you can drop 00:22:39.419 --> 00:22:40.730 align:start position:0% can pick up a resource so you can drop it<00:22:39.600> and<00:22:40.080> you<00:22:40.140> can<00:22:40.260> see<00:22:40.380> there<00:22:40.500> are<00:22:40.620> three 00:22:40.730 --> 00:22:40.740 align:start position:0% it and you can see there are three 00:22:40.740 --> 00:22:42.409 align:start position:0% it and you can see there are three players<00:22:41.039> there<00:22:41.159> zero<00:22:41.520> zero<00:22:41.760> one<00:22:41.880> zero<00:22:42.179> zero 00:22:42.409 --> 00:22:42.419 align:start position:0% players there zero zero one zero zero 00:22:42.419 --> 00:22:43.970 align:start position:0% players there zero zero one zero zero seven<00:22:42.480> zero<00:22:42.840> zero<00:22:43.140> five<00:22:43.260> there<00:22:43.740> are<00:22:43.860> little 00:22:43.970 --> 00:22:43.980 align:start position:0% seven zero zero five there are little 00:22:43.980 --> 00:22:45.770 align:start position:0% seven zero zero five there are little characters<00:22:44.280> riding<00:22:44.760> horses<00:22:45.120> and<00:22:45.419> you<00:22:45.600> have<00:22:45.720> a 00:22:45.770 --> 00:22:45.780 align:start position:0% characters riding horses and you have a 00:22:45.780 --> 00:22:47.090 align:start position:0% characters riding horses and you have a bunch<00:22:45.900> of<00:22:45.960> resources<00:22:46.260> on<00:22:46.440> the<00:22:46.559> floor<00:22:46.679> what 00:22:47.090 --> 00:22:47.100 align:start position:0% bunch of resources on the floor what 00:22:47.100 --> 00:22:48.529 align:start position:0% bunch of resources on the floor what players<00:22:47.340> do<00:22:47.520> is<00:22:47.640> they<00:22:47.760> can<00:22:47.880> vary<00:22:48.059> resources 00:22:48.529 --> 00:22:48.539 align:start position:0% players do is they can vary resources 00:22:48.539 --> 00:22:49.669 align:start position:0% players do is they can vary resources around<00:22:48.720> this<00:22:49.020> game<00:22:49.140> doesn't<00:22:49.380> actually<00:22:49.559> have 00:22:49.669 --> 00:22:49.679 align:start position:0% around this game doesn't actually have 00:22:49.679 --> 00:22:51.289 align:start position:0% around this game doesn't actually have any<00:22:49.860> goal<00:22:50.159> it's<00:22:50.280> just<00:22:50.460> some<00:22:50.640> rules<00:22:50.880> of<00:22:51.059> physics 00:22:51.289 --> 00:22:51.299 align:start position:0% any goal it's just some rules of physics 00:22:51.299 --> 00:22:52.610 align:start position:0% any goal it's just some rules of physics essentially 00:22:52.610 --> 00:22:52.620 align:start position:0% essentially 00:22:52.620 --> 00:22:53.450 align:start position:0% essentially um 00:22:53.450 --> 00:22:53.460 align:start position:0% um 00:22:53.460 --> 00:22:55.250 align:start position:0% um and<00:22:53.880> like<00:22:54.000> as<00:22:54.120> an<00:22:54.240> example<00:22:54.480> I<00:22:54.659> can<00:22:54.780> call<00:22:54.960> move 00:22:55.250 --> 00:22:55.260 align:start position:0% and like as an example I can call move 00:22:55.260 --> 00:22:57.049 align:start position:0% and like as an example I can call move on<00:22:55.679> my<00:22:55.799> player<00:22:56.159> and<00:22:56.340> I<00:22:56.460> would<00:22:56.580> move<00:22:56.760> my<00:22:57.000> horse 00:22:57.049 --> 00:22:57.059 align:start position:0% on my player and I would move my horse 00:22:57.059 --> 00:22:58.669 align:start position:0% on my player and I would move my horse from<00:22:57.299> one<00:22:57.419> place<00:22:57.600> to<00:22:57.780> another 00:22:58.669 --> 00:22:58.679 align:start position:0% from one place to another 00:22:58.679 --> 00:23:01.909 align:start position:0% from one place to another no<00:22:59.280> team<00:22:59.760> TTT<00:23:00.120> team<00:23:00.659> tic-tac-toe<00:23:01.500> comes<00:23:01.799> in 00:23:01.909 --> 00:23:01.919 align:start position:0% no team TTT team tic-tac-toe comes in 00:23:01.919 --> 00:23:03.830 align:start position:0% no team TTT team tic-tac-toe comes in and<00:23:02.520> they<00:23:02.700> deploy<00:23:03.000> two<00:23:03.179> new<00:23:03.299> components<00:23:03.720> on 00:23:03.830 --> 00:23:03.840 align:start position:0% and they deploy two new components on 00:23:03.840 --> 00:23:05.149 align:start position:0% and they deploy two new components on the<00:23:03.900> world<00:23:04.020> because<00:23:04.200> they<00:23:04.440> can<00:23:04.620> you<00:23:04.919> know<00:23:04.980> they 00:23:05.149 --> 00:23:05.159 align:start position:0% the world because they can you know they 00:23:05.159 --> 00:23:06.770 align:start position:0% the world because they can you know they don't<00:23:05.280> have<00:23:05.400> to<00:23:05.520> ask<00:23:05.640> anyone<00:23:06.000> those<00:23:06.539> two 00:23:06.770 --> 00:23:06.780 align:start position:0% don't have to ask anyone those two 00:23:06.780 --> 00:23:08.090 align:start position:0% don't have to ask anyone those two components<00:23:07.140> are<00:23:07.260> the<00:23:07.380> stick<00:23:07.559> component<00:23:07.919> in 00:23:08.090 --> 00:23:08.100 align:start position:0% components are the stick component in 00:23:08.100 --> 00:23:09.830 align:start position:0% components are the stick component in the<00:23:08.220> board<00:23:08.340> component<00:23:08.820> and<00:23:09.299> they<00:23:09.419> add<00:23:09.600> three 00:23:09.830 --> 00:23:09.840 align:start position:0% the board component and they add three 00:23:09.840 --> 00:23:12.230 align:start position:0% the board component and they add three systems<00:23:10.320> challenge<00:23:10.740> accept<00:23:11.340> Challenge<00:23:11.820> and 00:23:12.230 --> 00:23:12.240 align:start position:0% systems challenge accept Challenge and 00:23:12.240 --> 00:23:13.549 align:start position:0% systems challenge accept Challenge and resolve 00:23:13.549 --> 00:23:13.559 align:start position:0% resolve 00:23:13.559 --> 00:23:16.130 align:start position:0% resolve um<00:23:13.679> now<00:23:14.220> all<00:23:14.640> clients<00:23:15.120> are<00:23:15.419> aware<00:23:15.659> of<00:23:15.840> those 00:23:16.130 --> 00:23:16.140 align:start position:0% um now all clients are aware of those 00:23:16.140 --> 00:23:17.630 align:start position:0% um now all clients are aware of those new<00:23:16.440> components<00:23:16.919> and<00:23:16.980> systems<00:23:17.280> they<00:23:17.400> just 00:23:17.630 --> 00:23:17.640 align:start position:0% new components and systems they just 00:23:17.640 --> 00:23:19.909 align:start position:0% new components and systems they just don't<00:23:17.760> know<00:23:17.880> what<00:23:18.059> to<00:23:18.179> do<00:23:18.299> with<00:23:18.480> it<00:23:18.600> yet 00:23:19.909 --> 00:23:19.919 align:start position:0% don't know what to do with it yet 00:23:19.919 --> 00:23:21.529 align:start position:0% don't know what to do with it yet if<00:23:20.400> you<00:23:20.520> open<00:23:20.640> your<00:23:20.880> game<00:23:21.059> at<00:23:21.240> that<00:23:21.419> time 00:23:21.529 --> 00:23:21.539 align:start position:0% if you open your game at that time 00:23:21.539 --> 00:23:22.970 align:start position:0% if you open your game at that time you'll<00:23:21.900> see<00:23:22.020> a<00:23:22.140> little<00:23:22.200> install<00:23:22.380> box<00:23:22.740> it's 00:23:22.970 --> 00:23:22.980 align:start position:0% you'll see a little install box it's 00:23:22.980 --> 00:23:24.470 align:start position:0% you'll see a little install box it's like<00:23:23.159> hey<00:23:23.400> there<00:23:23.940> is<00:23:24.059> some<00:23:24.179> piece<00:23:24.419> of 00:23:24.470 --> 00:23:24.480 align:start position:0% like hey there is some piece of 00:23:24.480 --> 00:23:26.090 align:start position:0% like hey there is some piece of JavaScript<00:23:24.900> that<00:23:25.260> is<00:23:25.380> linked<00:23:25.740> with<00:23:25.860> those 00:23:26.090 --> 00:23:26.100 align:start position:0% JavaScript that is linked with those 00:23:26.100 --> 00:23:27.470 align:start position:0% JavaScript that is linked with those components<00:23:26.580> and<00:23:26.700> systems<00:23:27.000> do<00:23:27.179> you<00:23:27.299> want<00:23:27.360> to 00:23:27.470 --> 00:23:27.480 align:start position:0% components and systems do you want to 00:23:27.480 --> 00:23:28.730 align:start position:0% components and systems do you want to use<00:23:27.539> them 00:23:28.730 --> 00:23:28.740 align:start position:0% use them 00:23:28.740 --> 00:23:31.070 align:start position:0% use them um<00:23:28.799> if<00:23:29.400> you<00:23:29.520> do<00:23:29.700> now<00:23:30.299> you<00:23:30.539> can<00:23:30.600> play<00:23:30.840> a 00:23:31.070 --> 00:23:31.080 align:start position:0% um if you do now you can play a 00:23:31.080 --> 00:23:32.870 align:start position:0% um if you do now you can play a radically<00:23:31.559> different<00:23:31.740> game<00:23:32.039> while<00:23:32.460> still 00:23:32.870 --> 00:23:32.880 align:start position:0% radically different game while still 00:23:32.880 --> 00:23:34.850 align:start position:0% radically different game while still being<00:23:33.600> compatible<00:23:34.080> with<00:23:34.380> the<00:23:34.559> low<00:23:34.620> level 00:23:34.850 --> 00:23:34.860 align:start position:0% being compatible with the low level 00:23:34.860 --> 00:23:36.830 align:start position:0% being compatible with the low level rules<00:23:35.280> so<00:23:35.700> as<00:23:35.820> an<00:23:35.940> example<00:23:36.179> I<00:23:36.360> can<00:23:36.480> take<00:23:36.600> my 00:23:36.830 --> 00:23:36.840 align:start position:0% rules so as an example I can take my 00:23:36.840 --> 00:23:39.409 align:start position:0% rules so as an example I can take my player<00:23:37.140> I<00:23:37.620> can<00:23:37.740> move<00:23:37.860> to<00:23:38.039> the<00:23:38.159> gold<00:23:38.280> at<00:23:38.580> 0x03<00:23:39.179> I 00:23:39.409 --> 00:23:39.419 align:start position:0% player I can move to the gold at 0x03 I 00:23:39.419 --> 00:23:40.850 align:start position:0% player I can move to the gold at 0x03 I can<00:23:39.539> pick<00:23:39.600> it<00:23:39.720> up<00:23:39.840> move<00:23:40.080> again<00:23:40.260> and<00:23:40.500> I<00:23:40.679> can<00:23:40.740> come 00:23:40.850 --> 00:23:40.860 align:start position:0% can pick it up move again and I can come 00:23:40.860 --> 00:23:42.950 align:start position:0% can pick it up move again and I can come next<00:23:41.100> to<00:23:41.220> that<00:23:41.340> player<00:23:41.640> at<00:23:41.760> 0x07<00:23:42.419> and<00:23:42.600> call<00:23:42.840> the 00:23:42.950 --> 00:23:42.960 align:start position:0% next to that player at 0x07 and call the 00:23:42.960 --> 00:23:44.750 align:start position:0% next to that player at 0x07 and call the challenge<00:23:43.140> system<00:23:43.440> on<00:23:43.860> that<00:23:44.039> player<00:23:44.340> that 00:23:44.750 --> 00:23:44.760 align:start position:0% challenge system on that player that 00:23:44.760 --> 00:23:46.190 align:start position:0% challenge system on that player that challenge<00:23:44.940> system<00:23:45.299> is<00:23:45.480> new<00:23:45.659> it<00:23:45.840> was<00:23:45.900> deployed 00:23:46.190 --> 00:23:46.200 align:start position:0% challenge system is new it was deployed 00:23:46.200 --> 00:23:48.350 align:start position:0% challenge system is new it was deployed by<00:23:46.320> the<00:23:46.440> team<00:23:46.559> Tic-tac-toe<00:23:47.280> and<00:23:47.640> attached<00:23:48.179> one 00:23:48.350 --> 00:23:48.360 align:start position:0% by the team Tic-tac-toe and attached one 00:23:48.360 --> 00:23:50.090 align:start position:0% by the team Tic-tac-toe and attached one eth<00:23:48.720> to<00:23:48.900> my<00:23:49.020> transaction 00:23:50.090 --> 00:23:50.100 align:start position:0% eth to my transaction 00:23:50.100 --> 00:23:51.890 align:start position:0% eth to my transaction the<00:23:50.580> other<00:23:50.760> player<00:23:51.120> if<00:23:51.360> they're<00:23:51.539> aware<00:23:51.780> of 00:23:51.890 --> 00:23:51.900 align:start position:0% the other player if they're aware of 00:23:51.900 --> 00:23:53.210 align:start position:0% the other player if they're aware of that<00:23:52.020> augmented<00:23:52.440> reality<00:23:52.679> layer<00:23:52.980> can<00:23:53.159> accept 00:23:53.210 --> 00:23:53.220 align:start position:0% that augmented reality layer can accept 00:23:53.220 --> 00:23:55.610 align:start position:0% that augmented reality layer can accept the<00:23:53.460> challenge<00:23:53.640> stick<00:23:54.299> the<00:23:54.539> same<00:23:54.659> amount<00:23:54.840> and 00:23:55.610 --> 00:23:55.620 align:start position:0% the challenge stick the same amount and 00:23:55.620 --> 00:23:57.649 align:start position:0% the challenge stick the same amount and now<00:23:55.860> my<00:23:56.159> like<00:23:56.400> this<00:23:56.880> new<00:23:57.000> system<00:23:57.179> is<00:23:57.360> going<00:23:57.539> to 00:23:57.649 --> 00:23:57.659 align:start position:0% now my like this new system is going to 00:23:57.659 --> 00:24:00.049 align:start position:0% now my like this new system is going to create<00:23:57.780> a<00:23:58.020> new<00:23:58.140> entity<00:23:58.440> 0x09<00:23:59.400> because<00:23:59.700> anyone 00:24:00.049 --> 00:24:00.059 align:start position:0% create a new entity 0x09 because anyone 00:24:00.059 --> 00:24:01.850 align:start position:0% create a new entity 0x09 because anyone can<00:24:00.179> create<00:24:00.360> entities<00:24:00.720> and<00:24:01.080> attach<00:24:01.380> the<00:24:01.679> state 00:24:01.850 --> 00:24:01.860 align:start position:0% can create entities and attach the state 00:24:01.860 --> 00:24:03.230 align:start position:0% can create entities and attach the state component<00:24:02.220> in<00:24:02.340> the<00:24:02.460> board<00:24:02.580> component<00:24:02.940> to<00:24:03.120> it 00:24:03.230 --> 00:24:03.240 align:start position:0% component in the board component to it 00:24:03.240 --> 00:24:05.330 align:start position:0% component in the board component to it so<00:24:03.720> now<00:24:03.840> for<00:24:04.260> the<00:24:04.380> players<00:24:04.679> that<00:24:04.860> have<00:24:05.100> the 00:24:05.330 --> 00:24:05.340 align:start position:0% so now for the players that have the 00:24:05.340 --> 00:24:06.649 align:start position:0% so now for the players that have the actual<00:24:05.580> code<00:24:05.760> that<00:24:06.000> allows<00:24:06.299> them<00:24:06.419> to 00:24:06.649 --> 00:24:06.659 align:start position:0% actual code that allows them to 00:24:06.659 --> 00:24:08.510 align:start position:0% actual code that allows them to experience<00:24:07.260> the<00:24:07.500> tic-tac-toe<00:24:08.159> augmented 00:24:08.510 --> 00:24:08.520 align:start position:0% experience the tic-tac-toe augmented 00:24:08.520 --> 00:24:10.310 align:start position:0% experience the tic-tac-toe augmented reality<00:24:08.880> they<00:24:09.360> can<00:24:09.539> see<00:24:09.659> your<00:24:09.780> board<00:24:09.960> on<00:24:10.140> the 00:24:10.310 --> 00:24:10.320 align:start position:0% reality they can see your board on the 00:24:10.320 --> 00:24:11.149 align:start position:0% reality they can see your board on the floor 00:24:11.149 --> 00:24:11.159 align:start position:0% floor 00:24:11.159 --> 00:24:12.529 align:start position:0% floor um<00:24:11.220> I<00:24:11.340> know<00:24:11.460> they<00:24:11.580> can<00:24:11.700> play<00:24:11.760> Tic-Tac-Toe<00:24:12.360> they 00:24:12.529 --> 00:24:12.539 align:start position:0% um I know they can play Tic-Tac-Toe they 00:24:12.539 --> 00:24:14.630 align:start position:0% um I know they can play Tic-Tac-Toe they can<00:24:12.720> drop<00:24:12.840> the<00:24:13.080> resources<00:24:13.559> in<00:24:14.280> order<00:24:14.340> to<00:24:14.520> play 00:24:14.630 --> 00:24:14.640 align:start position:0% can drop the resources in order to play 00:24:14.640 --> 00:24:16.610 align:start position:0% can drop the resources in order to play Tic-tac-toe<00:24:15.419> and<00:24:15.600> someone<00:24:15.780> can<00:24:16.080> win<00:24:16.260> they<00:24:16.500> can 00:24:16.610 --> 00:24:16.620 align:start position:0% Tic-tac-toe and someone can win they can 00:24:16.620 --> 00:24:17.990 align:start position:0% Tic-tac-toe and someone can win they can call<00:24:16.799> the<00:24:16.919> resolve<00:24:17.280> system<00:24:17.460> and<00:24:17.700> they<00:24:17.880> can 00:24:17.990 --> 00:24:18.000 align:start position:0% call the resolve system and they can 00:24:18.000 --> 00:24:19.750 align:start position:0% call the resolve system and they can take<00:24:18.120> the<00:24:18.299> stick<00:24:18.480> and<00:24:18.840> destroy<00:24:19.200> that<00:24:19.320> entity 00:24:19.750 --> 00:24:19.760 align:start position:0% take the stick and destroy that entity 00:24:19.760 --> 00:24:22.190 align:start position:0% take the stick and destroy that entity and<00:24:20.760> you<00:24:20.880> can<00:24:21.000> do<00:24:21.120> that<00:24:21.299> without<00:24:21.600> clashing 00:24:22.190 --> 00:24:22.200 align:start position:0% and you can do that without clashing 00:24:22.200 --> 00:24:23.810 align:start position:0% and you can do that without clashing with<00:24:22.500> the<00:24:22.620> rules<00:24:22.860> that<00:24:23.039> all<00:24:23.220> other<00:24:23.400> players 00:24:23.810 --> 00:24:23.820 align:start position:0% with the rules that all other players 00:24:23.820 --> 00:24:26.210 align:start position:0% with the rules that all other players believe<00:24:24.120> in<00:24:24.360> so<00:24:25.080> tic-tac-toe<00:24:25.860> is<00:24:25.980> just<00:24:26.100> like 00:24:26.210 --> 00:24:26.220 align:start position:0% believe in so tic-tac-toe is just like 00:24:26.220 --> 00:24:28.250 align:start position:0% believe in so tic-tac-toe is just like tennis<00:24:26.460> like<00:24:27.059> tennis<00:24:27.360> is<00:24:27.659> an<00:24:27.840> augmented 00:24:28.250 --> 00:24:28.260 align:start position:0% tennis like tennis is an augmented 00:24:28.260 --> 00:24:30.649 align:start position:0% tennis like tennis is an augmented reality<00:24:28.620> layer<00:24:28.980> on<00:24:29.100> top<00:24:29.220> of<00:24:29.340> our<00:24:29.460> physics<00:24:29.820> I 00:24:30.649 --> 00:24:30.659 align:start position:0% reality layer on top of our physics I 00:24:30.659 --> 00:24:31.970 align:start position:0% reality layer on top of our physics I can<00:24:30.780> drive<00:24:30.900> in<00:24:31.140> my<00:24:31.260> car<00:24:31.380> and<00:24:31.559> look<00:24:31.679> at<00:24:31.799> tennis 00:24:31.970 --> 00:24:31.980 align:start position:0% can drive in my car and look at tennis 00:24:31.980 --> 00:24:34.130 align:start position:0% can drive in my car and look at tennis players<00:24:32.400> and<00:24:32.700> we're<00:24:33.059> not<00:24:33.360> breaching<00:24:34.020> the 00:24:34.130 --> 00:24:34.140 align:start position:0% players and we're not breaching the 00:24:34.140 --> 00:24:35.870 align:start position:0% players and we're not breaching the rules<00:24:34.380> like<00:24:34.620> we're<00:24:34.860> all<00:24:35.100> like<00:24:35.580> living 00:24:35.870 --> 00:24:35.880 align:start position:0% rules like we're all like living 00:24:35.880 --> 00:24:37.370 align:start position:0% rules like we're all like living according<00:24:36.299> to<00:24:36.419> the<00:24:36.480> symbols<00:24:36.900> but<00:24:37.020> we're<00:24:37.140> just 00:24:37.370 --> 00:24:37.380 align:start position:0% according to the symbols but we're just 00:24:37.380 --> 00:24:38.990 align:start position:0% according to the symbols but we're just like<00:24:37.559> experiencing<00:24:38.280> the<00:24:38.460> world<00:24:38.640> in<00:24:38.820> different 00:24:38.990 --> 00:24:39.000 align:start position:0% like experiencing the world in different 00:24:39.000 --> 00:24:41.630 align:start position:0% like experiencing the world in different ways<00:24:39.360> so<00:24:39.840> it's<00:24:39.960> an<00:24:40.080> augmented<00:24:40.559> reality<00:24:40.919> and 00:24:41.630 --> 00:24:41.640 align:start position:0% ways so it's an augmented reality and 00:24:41.640 --> 00:24:43.010 align:start position:0% ways so it's an augmented reality and from<00:24:41.760> the<00:24:41.880> perspective<00:24:42.240> of<00:24:42.419> other<00:24:42.659> players 00:24:43.010 --> 00:24:43.020 align:start position:0% from the perspective of other players 00:24:43.020 --> 00:24:44.570 align:start position:0% from the perspective of other players they're<00:24:43.440> just<00:24:43.620> like<00:24:43.740> what<00:24:43.919> the<00:24:44.100> hell<00:24:44.280> is<00:24:44.400> going 00:24:44.570 --> 00:24:44.580 align:start position:0% they're just like what the hell is going 00:24:44.580 --> 00:24:47.270 align:start position:0% they're just like what the hell is going on<00:24:44.760> why<00:24:45.360> are<00:24:45.539> people<00:24:45.720> dropping<00:24:46.320> resources<00:24:47.100> on 00:24:47.270 --> 00:24:47.280 align:start position:0% on why are people dropping resources on 00:24:47.280 --> 00:24:49.490 align:start position:0% on why are people dropping resources on the<00:24:47.400> floor<00:24:47.580> on<00:24:47.940> a<00:24:48.059> grid<00:24:48.299> but<00:24:48.780> they<00:24:49.200> can<00:24:49.380> still 00:24:49.490 --> 00:24:49.500 align:start position:0% the floor on a grid but they can still 00:24:49.500 --> 00:24:52.370 align:start position:0% the floor on a grid but they can still coexist<00:24:49.860> together<00:24:50.039> other<00:24:50.539> so<00:24:51.539> there<00:24:52.200> are<00:24:52.380> a 00:24:52.370 --> 00:24:52.380 align:start position:0% coexist together other so there are a 00:24:52.380 --> 00:24:54.590 align:start position:0% coexist together other so there are a lot<00:24:52.500> of<00:24:52.559> augmented<00:24:53.039> reality<00:24:53.400> out<00:24:53.940> there<00:24:54.120> the 00:24:54.590 --> 00:24:54.600 align:start position:0% lot of augmented reality out there the 00:24:54.600 --> 00:24:57.169 align:start position:0% lot of augmented reality out there the main<00:24:54.720> one<00:24:54.840> is<00:24:55.020> capitalism<00:24:55.500> it<00:24:55.980> was<00:24:56.100> made<00:24:56.280> up<00:24:56.460> uh 00:24:57.169 --> 00:24:57.179 align:start position:0% main one is capitalism it was made up uh 00:24:57.179 --> 00:24:59.149 align:start position:0% main one is capitalism it was made up uh we<00:24:57.539> all<00:24:57.720> wear<00:24:58.080> the<00:24:58.320> glasses<00:24:58.620> that<00:24:58.740> allows<00:24:59.100> us 00:24:59.149 --> 00:24:59.159 align:start position:0% we all wear the glasses that allows us 00:24:59.159 --> 00:25:01.190 align:start position:0% we all wear the glasses that allows us to<00:24:59.340> see<00:24:59.520> capitalism<00:25:00.059> but<00:25:00.600> I<00:25:00.780> can<00:25:00.900> interact 00:25:01.190 --> 00:25:01.200 align:start position:0% to see capitalism but I can interact 00:25:01.200 --> 00:25:02.450 align:start position:0% to see capitalism but I can interact with<00:25:01.320> an<00:25:01.500> anarchist<00:25:01.919> that<00:25:02.159> doesn't<00:25:02.280> believe 00:25:02.450 --> 00:25:02.460 align:start position:0% with an anarchist that doesn't believe 00:25:02.460 --> 00:25:04.549 align:start position:0% with an anarchist that doesn't believe in<00:25:02.640> money<00:25:02.820> I<00:25:03.360> can<00:25:03.539> go<00:25:03.720> and<00:25:03.960> like<00:25:04.200> have<00:25:04.380> dinner 00:25:04.549 --> 00:25:04.559 align:start position:0% in money I can go and like have dinner 00:25:04.559 --> 00:25:06.049 align:start position:0% in money I can go and like have dinner with<00:25:04.799> them<00:25:04.980> and<00:25:05.400> we<00:25:05.580> won't<00:25:05.820> actually 00:25:06.049 --> 00:25:06.059 align:start position:0% with them and we won't actually 00:25:06.059 --> 00:25:07.490 align:start position:0% with them and we won't actually experience<00:25:06.419> the<00:25:06.600> same<00:25:06.720> augmented<00:25:07.140> reality 00:25:07.490 --> 00:25:07.500 align:start position:0% experience the same augmented reality 00:25:07.500 --> 00:25:09.470 align:start position:0% experience the same augmented reality but<00:25:07.679> we<00:25:07.799> share<00:25:07.980> the<00:25:08.220> same<00:25:08.340> low<00:25:08.580> level<00:25:08.820> rules 00:25:09.470 --> 00:25:09.480 align:start position:0% but we share the same low level rules 00:25:09.480 --> 00:25:11.930 align:start position:0% but we share the same low level rules competition<00:25:10.380> is<00:25:10.620> also<00:25:11.100> an<00:25:11.220> augmented<00:25:11.640> reality 00:25:11.930 --> 00:25:11.940 align:start position:0% competition is also an augmented reality 00:25:11.940 --> 00:25:13.190 align:start position:0% competition is also an augmented reality the<00:25:12.240> thing<00:25:12.360> that<00:25:12.480> is<00:25:12.600> interesting<00:25:12.840> with<00:25:13.020> this 00:25:13.190 --> 00:25:13.200 align:start position:0% the thing that is interesting with this 00:25:13.200 --> 00:25:14.330 align:start position:0% the thing that is interesting with this game 00:25:14.330 --> 00:25:14.340 align:start position:0% game 00:25:14.340 --> 00:25:16.970 align:start position:0% game um<00:25:14.460> is<00:25:15.000> that<00:25:15.120> it<00:25:15.360> has<00:25:15.480> it<00:25:15.659> has<00:25:15.840> no<00:25:16.020> goal<00:25:16.440> some 00:25:16.970 --> 00:25:16.980 align:start position:0% um is that it has it has no goal some 00:25:16.980 --> 00:25:18.169 align:start position:0% um is that it has it has no goal some people<00:25:17.159> just<00:25:17.340> made<00:25:17.520> a<00:25:17.700> set<00:25:17.760> of<00:25:17.880> interesting 00:25:18.169 --> 00:25:18.179 align:start position:0% people just made a set of interesting 00:25:18.179 --> 00:25:20.390 align:start position:0% people just made a set of interesting rules<00:25:18.480> and<00:25:18.659> resources<00:25:19.080> but<00:25:19.679> now<00:25:19.799> anyone<00:25:20.220> can 00:25:20.390 --> 00:25:20.400 align:start position:0% rules and resources but now anyone can 00:25:20.400 --> 00:25:22.190 align:start position:0% rules and resources but now anyone can come<00:25:20.580> in<00:25:20.760> and<00:25:21.299> essentially 00:25:22.190 --> 00:25:22.200 align:start position:0% come in and essentially 00:25:22.200 --> 00:25:25.430 align:start position:0% come in and essentially puts<00:25:22.980> a<00:25:23.100> competitive<00:25:23.520> layer<00:25:23.940> on<00:25:24.120> top<00:25:24.299> of<00:25:24.480> it 00:25:25.430 --> 00:25:25.440 align:start position:0% puts a competitive layer on top of it 00:25:25.440 --> 00:25:26.870 align:start position:0% puts a competitive layer on top of it um<00:25:25.500> many<00:25:25.980> games<00:25:26.220> are<00:25:26.340> also<00:25:26.520> augmented 00:25:26.870 --> 00:25:26.880 align:start position:0% um many games are also augmented 00:25:26.880 --> 00:25:28.430 align:start position:0% um many games are also augmented realities<00:25:27.240> so<00:25:27.480> for<00:25:27.659> the<00:25:27.960> people<00:25:28.020> here<00:25:28.260> that 00:25:28.430 --> 00:25:28.440 align:start position:0% realities so for the people here that 00:25:28.440 --> 00:25:30.169 align:start position:0% realities so for the people here that have<00:25:28.559> played<00:25:28.799> Minecraft<00:25:29.000> in<00:25:30.000> Minecraft 00:25:30.169 --> 00:25:30.179 align:start position:0% have played Minecraft in Minecraft 00:25:30.179 --> 00:25:32.390 align:start position:0% have played Minecraft in Minecraft servers<00:25:30.779> a<00:25:31.440> lot<00:25:31.500> of<00:25:31.620> people<00:25:31.679> build<00:25:31.919> minigames 00:25:32.390 --> 00:25:32.400 align:start position:0% servers a lot of people build minigames 00:25:32.400 --> 00:25:33.470 align:start position:0% servers a lot of people build minigames you<00:25:32.520> know<00:25:32.580> you<00:25:32.700> have<00:25:32.760> to<00:25:32.880> break<00:25:33.059> the<00:25:33.299> wall 00:25:33.470 --> 00:25:33.480 align:start position:0% you know you have to break the wall 00:25:33.480 --> 00:25:35.210 align:start position:0% you know you have to break the wall underneath<00:25:34.020> people's<00:25:34.559> feet<00:25:34.679> and<00:25:34.799> fall<00:25:34.980> in<00:25:35.100> the 00:25:35.210 --> 00:25:35.220 align:start position:0% underneath people's feet and fall in the 00:25:35.220 --> 00:25:36.769 align:start position:0% underneath people's feet and fall in the lava<00:25:35.520> those<00:25:35.940> minigames<00:25:36.480> actually<00:25:36.539> don't 00:25:36.769 --> 00:25:36.779 align:start position:0% lava those minigames actually don't 00:25:36.779 --> 00:25:37.730 align:start position:0% lava those minigames actually don't clash<00:25:37.020> with<00:25:37.140> the<00:25:37.260> rules<00:25:37.440> of<00:25:37.559> Minecraft 00:25:37.730 --> 00:25:37.740 align:start position:0% clash with the rules of Minecraft 00:25:37.740 --> 00:25:39.470 align:start position:0% clash with the rules of Minecraft they're<00:25:38.159> just<00:25:38.400> like<00:25:38.580> new<00:25:38.880> systems<00:25:39.240> that<00:25:39.360> have 00:25:39.470 --> 00:25:39.480 align:start position:0% they're just like new systems that have 00:25:39.480 --> 00:25:41.210 align:start position:0% they're just like new systems that have been<00:25:39.539> created<00:25:39.840> on<00:25:40.020> top 00:25:41.210 --> 00:25:41.220 align:start position:0% been created on top 00:25:41.220 --> 00:25:42.950 align:start position:0% been created on top um<00:25:41.279> and<00:25:41.760> you<00:25:41.880> can<00:25:42.000> do<00:25:42.120> that<00:25:42.240> permissionlessly 00:25:42.950 --> 00:25:42.960 align:start position:0% um and you can do that permissionlessly 00:25:42.960 --> 00:25:44.510 align:start position:0% um and you can do that permissionlessly you<00:25:43.440> don't<00:25:43.559> need<00:25:43.679> a<00:25:43.860> governance<00:25:44.100> for<00:25:44.400> the 00:25:44.510 --> 00:25:44.520 align:start position:0% you don't need a governance for the 00:25:44.520 --> 00:25:45.649 align:start position:0% you don't need a governance for the world<00:25:44.640> because<00:25:44.820> the<00:25:45.000> world<00:25:45.179> is<00:25:45.299> onerous 00:25:45.649 --> 00:25:45.659 align:start position:0% world because the world is onerous 00:25:45.659 --> 00:25:47.269 align:start position:0% world because the world is onerous anyone<00:25:46.080> can<00:25:46.260> deploy<00:25:46.500> new<00:25:46.679> components<00:25:47.100> and 00:25:47.269 --> 00:25:47.279 align:start position:0% anyone can deploy new components and 00:25:47.279 --> 00:25:49.310 align:start position:0% anyone can deploy new components and systems<00:25:47.640> and<00:25:47.820> players<00:25:48.240> believe<00:25:48.600> in<00:25:49.020> whatever 00:25:49.310 --> 00:25:49.320 align:start position:0% systems and players believe in whatever 00:25:49.320 --> 00:25:52.130 align:start position:0% systems and players believe in whatever components<00:25:49.860> the<00:25:49.980> system<00:25:50.159> they<00:25:50.520> care<00:25:50.700> about 00:25:52.130 --> 00:25:52.140 align:start position:0% components the system they care about 00:25:52.140 --> 00:25:53.870 align:start position:0% components the system they care about um<00:25:52.200> and<00:25:52.440> I'm<00:25:52.679> gonna<00:25:52.860> pass<00:25:53.039> it<00:25:53.220> to<00:25:53.460> our<00:25:53.700> friend 00:25:53.870 --> 00:25:53.880 align:start position:0% um and I'm gonna pass it to our friend 00:25:53.880 --> 00:25:55.909 align:start position:0% um and I'm gonna pass it to our friend Kelvin<00:25:54.360> who's<00:25:55.140> gonna 00:25:55.909 --> 00:25:55.919 align:start position:0% Kelvin who's gonna 00:25:55.919 --> 00:26:00.529 align:start position:0% Kelvin who's gonna drop<00:25:56.460> some<00:25:56.760> more<00:25:57.000> cool<00:25:57.360> stuff 00:26:00.529 --> 00:26:00.539 align:start position:0% 00:26:00.539 --> 00:26:02.210 align:start position:0% um<00:26:00.659> so<00:26:00.840> you<00:26:01.080> want<00:26:01.200> to<00:26:01.320> build<00:26:01.440> an<00:26:01.679> autonomous 00:26:02.210 --> 00:26:02.220 align:start position:0% um so you want to build an autonomous 00:26:02.220 --> 00:26:05.210 align:start position:0% um so you want to build an autonomous World<00:26:02.720> good<00:26:03.720> luck<00:26:03.960> good<00:26:04.380> luck<00:26:04.559> have<00:26:04.980> fun 00:26:05.210 --> 00:26:05.220 align:start position:0% World good luck good luck have fun 00:26:05.220 --> 00:26:08.330 align:start position:0% World good luck good luck have fun trying<00:26:05.580> just<00:26:06.419> kidding<00:26:06.779> of<00:26:07.020> course 00:26:08.330 --> 00:26:08.340 align:start position:0% trying just kidding of course 00:26:08.340 --> 00:26:09.649 align:start position:0% trying just kidding of course um 00:26:09.649 --> 00:26:09.659 align:start position:0% um 00:26:09.659 --> 00:26:11.510 align:start position:0% um I'm<00:26:09.960> gonna<00:26:10.140> be<00:26:10.260> talking<00:26:10.559> to<00:26:10.799> you<00:26:10.919> today<00:26:11.100> about 00:26:11.510 --> 00:26:11.520 align:start position:0% I'm gonna be talking to you today about 00:26:11.520 --> 00:26:15.049 align:start position:0% I'm gonna be talking to you today about the<00:26:11.880> op<00:26:12.000> stack<00:26:12.720> uh<00:26:13.620> technically<00:26:14.340> we<00:26:14.940> were 00:26:15.049 --> 00:26:15.059 align:start position:0% the op stack uh technically we were 00:26:15.059 --> 00:26:16.549 align:start position:0% the op stack uh technically we were originally<00:26:15.360> hoping<00:26:15.720> that<00:26:15.960> this<00:26:16.080> talk<00:26:16.260> would 00:26:16.549 --> 00:26:16.559 align:start position:0% originally hoping that this talk would 00:26:16.559 --> 00:26:18.649 align:start position:0% originally hoping that this talk would be<00:26:16.679> after<00:26:17.220> the<00:26:17.580> other<00:26:17.760> talk<00:26:18.000> about<00:26:18.299> the<00:26:18.539> op 00:26:18.649 --> 00:26:18.659 align:start position:0% be after the other talk about the op 00:26:18.659 --> 00:26:20.810 align:start position:0% be after the other talk about the op stack<00:26:19.200> so<00:26:19.380> just<00:26:19.559> pretend<00:26:19.980> pretend<00:26:20.580> that 00:26:20.810 --> 00:26:20.820 align:start position:0% stack so just pretend pretend that 00:26:20.820 --> 00:26:23.269 align:start position:0% stack so just pretend pretend that you're<00:26:21.120> five<00:26:21.539> hours<00:26:21.779> in<00:26:22.080> the<00:26:22.260> future<00:26:22.440> you've 00:26:23.269 --> 00:26:23.279 align:start position:0% you're five hours in the future you've 00:26:23.279 --> 00:26:26.090 align:start position:0% you're five hours in the future you've watched<00:26:23.640> the<00:26:23.700> other<00:26:23.940> talk<00:26:24.320> uh<00:26:25.320> and<00:26:25.679> you<00:26:25.980> know 00:26:26.090 --> 00:26:26.100 align:start position:0% watched the other talk uh and you know 00:26:26.100 --> 00:26:28.370 align:start position:0% watched the other talk uh and you know whatever<00:26:26.640> time<00:26:27.120> doesn't<00:26:27.419> doesn't<00:26:28.020> matter 00:26:28.370 --> 00:26:28.380 align:start position:0% whatever time doesn't doesn't matter 00:26:28.380 --> 00:26:29.230 align:start position:0% whatever time doesn't doesn't matter anymore 00:26:29.230 --> 00:26:29.240 align:start position:0% anymore 00:26:29.240 --> 00:26:32.149 align:start position:0% anymore so<00:26:30.240> introducing<00:26:30.779> the<00:26:30.960> op<00:26:31.080> stack<00:26:31.559> except<00:26:31.919> Carl 00:26:32.149 --> 00:26:32.159 align:start position:0% so introducing the op stack except Carl 00:26:32.159 --> 00:26:34.090 align:start position:0% so introducing the op stack except Carl has<00:26:32.460> already<00:26:32.580> done<00:26:32.820> it<00:26:33.000> five<00:26:33.240> hours<00:26:33.419> from<00:26:33.779> now 00:26:34.090 --> 00:26:34.100 align:start position:0% has already done it five hours from now 00:26:34.100 --> 00:26:36.230 align:start position:0% has already done it five hours from now kinda<00:26:35.100> we<00:26:35.340> still<00:26:35.520> need<00:26:35.640> to<00:26:35.760> write<00:26:35.880> all<00:26:36.120> the 00:26:36.230 --> 00:26:36.240 align:start position:0% kinda we still need to write all the 00:26:36.240 --> 00:26:38.510 align:start position:0% kinda we still need to write all the docs<00:26:36.659> so<00:26:36.840> if<00:26:37.320> you<00:26:37.440> want<00:26:37.559> to<00:26:37.740> use<00:26:37.980> this<00:26:38.220> you're 00:26:38.510 --> 00:26:38.520 align:start position:0% docs so if you want to use this you're 00:26:38.520 --> 00:26:39.950 align:start position:0% docs so if you want to use this you're going<00:26:38.640> to<00:26:38.760> have<00:26:38.880> to<00:26:39.000> dig<00:26:39.240> deep<00:26:39.480> a<00:26:39.720> little<00:26:39.779> bit 00:26:39.950 --> 00:26:39.960 align:start position:0% going to have to dig deep a little bit 00:26:39.960 --> 00:26:42.890 align:start position:0% going to have to dig deep a little bit uh<00:26:40.620> you<00:26:40.799> can<00:26:40.919> talk<00:26:41.039> to<00:26:41.220> me<00:26:41.340> afterwards<00:26:41.940> about 00:26:42.890 --> 00:26:42.900 align:start position:0% uh you can talk to me afterwards about 00:26:42.900 --> 00:26:44.870 align:start position:0% uh you can talk to me afterwards about how<00:26:43.140> you<00:26:43.260> can<00:26:43.380> actually<00:26:43.500> achieve<00:26:43.980> this<00:26:44.159> but 00:26:44.870 --> 00:26:44.880 align:start position:0% how you can actually achieve this but 00:26:44.880 --> 00:26:46.549 align:start position:0% how you can actually achieve this but all<00:26:45.120> right<00:26:45.240> introducing<00:26:45.779> the<00:26:45.900> op<00:26:46.020> stack<00:26:46.440> I 00:26:46.549 --> 00:26:46.559 align:start position:0% all right introducing the op stack I 00:26:46.559 --> 00:26:47.810 align:start position:0% all right introducing the op stack I want<00:26:46.679> to<00:26:46.799> talk<00:26:46.860> to<00:26:46.919> you<00:26:47.039> a<00:26:47.159> little<00:26:47.279> bit<00:26:47.400> about 00:26:47.810 --> 00:26:47.820 align:start position:0% want to talk to you a little bit about 00:26:47.820 --> 00:26:50.690 align:start position:0% want to talk to you a little bit about basically<00:26:48.720> how<00:26:49.320> you<00:26:49.440> can<00:26:49.559> achieve<00:26:50.100> this<00:26:50.460> build 00:26:50.690 --> 00:26:50.700 align:start position:0% basically how you can achieve this build 00:26:50.700 --> 00:26:53.450 align:start position:0% basically how you can achieve this build your<00:26:50.940> own<00:26:51.179> system<00:26:51.539> today<00:26:52.140> and<00:26:52.919> get<00:26:53.100> really 00:26:53.450 --> 00:26:53.460 align:start position:0% your own system today and get really 00:26:53.460 --> 00:26:55.250 align:start position:0% your own system today and get really good<00:26:53.760> security<00:26:54.240> guarantees<00:26:54.900> at<00:26:55.020> the<00:26:55.140> same 00:26:55.250 --> 00:26:55.260 align:start position:0% good security guarantees at the same 00:26:55.260 --> 00:26:58.549 align:start position:0% good security guarantees at the same time<00:26:55.500> all<00:26:55.980> right<00:26:56.220> so<00:26:56.700> boom<00:26:57.419> what<00:26:58.140> is<00:26:58.260> the<00:26:58.440> op 00:26:58.549 --> 00:26:58.559 align:start position:0% time all right so boom what is the op 00:26:58.559 --> 00:27:01.250 align:start position:0% time all right so boom what is the op stack<00:26:59.159> essentially<00:27:00.000> the<00:27:00.419> op<00:27:00.539> stack<00:27:01.080> is 00:27:01.250 --> 00:27:01.260 align:start position:0% stack essentially the op stack is 00:27:01.260 --> 00:27:04.370 align:start position:0% stack essentially the op stack is rollups<00:27:01.919> gone<00:27:02.220> modular<00:27:02.820> over<00:27:03.299> the<00:27:03.539> last<00:27:03.779> year 00:27:04.370 --> 00:27:04.380 align:start position:0% rollups gone modular over the last year 00:27:04.380 --> 00:27:06.289 align:start position:0% rollups gone modular over the last year we've<00:27:05.100> been<00:27:05.159> designing<00:27:05.640> and<00:27:05.820> building<00:27:06.000> this 00:27:06.289 --> 00:27:06.299 align:start position:0% we've been designing and building this 00:27:06.299 --> 00:27:07.850 align:start position:0% we've been designing and building this thing<00:27:06.419> called<00:27:06.659> Bedrock<00:27:07.200> which<00:27:07.380> is<00:27:07.500> the<00:27:07.740> next 00:27:07.850 --> 00:27:07.860 align:start position:0% thing called Bedrock which is the next 00:27:07.860 --> 00:27:10.490 align:start position:0% thing called Bedrock which is the next major<00:27:08.159> upgrade<00:27:08.520> to<00:27:08.700> optimism 00:27:10.490 --> 00:27:10.500 align:start position:0% major upgrade to optimism 00:27:10.500 --> 00:27:12.230 align:start position:0% major upgrade to optimism um<00:27:10.559> and<00:27:10.919> while<00:27:11.100> we<00:27:11.279> were<00:27:11.400> doing<00:27:11.580> that<00:27:11.820> I<00:27:12.120> think 00:27:12.230 --> 00:27:12.240 align:start position:0% um and while we were doing that I think 00:27:12.240 --> 00:27:13.850 align:start position:0% um and while we were doing that I think we<00:27:12.419> realized<00:27:12.720> that<00:27:12.960> the<00:27:13.200> key<00:27:13.380> part<00:27:13.620> of 00:27:13.850 --> 00:27:13.860 align:start position:0% we realized that the key part of 00:27:13.860 --> 00:27:16.190 align:start position:0% we realized that the key part of building<00:27:14.039> a<00:27:14.279> solid<00:27:14.580> roll-up<00:27:14.940> client<00:27:15.299> was<00:27:15.900> to 00:27:16.190 --> 00:27:16.200 align:start position:0% building a solid roll-up client was to 00:27:16.200 --> 00:27:18.289 align:start position:0% building a solid roll-up client was to make<00:27:16.380> it<00:27:16.559> as<00:27:16.799> modular<00:27:17.220> as<00:27:17.580> you<00:27:17.700> can<00:27:17.880> possibly 00:27:18.289 --> 00:27:18.299 align:start position:0% make it as modular as you can possibly 00:27:18.299 --> 00:27:20.210 align:start position:0% make it as modular as you can possibly make<00:27:18.600> it<00:27:18.779> and<00:27:19.200> we<00:27:19.380> sort<00:27:19.559> of<00:27:19.679> we'll<00:27:19.919> talk<00:27:20.100> about 00:27:20.210 --> 00:27:20.220 align:start position:0% make it and we sort of we'll talk about 00:27:20.220 --> 00:27:22.130 align:start position:0% make it and we sort of we'll talk about this<00:27:20.520> a<00:27:20.640> lot<00:27:20.760> in<00:27:21.059> the<00:27:21.179> talk<00:27:21.299> later<00:27:21.600> today<00:27:21.840> the 00:27:22.130 --> 00:27:22.140 align:start position:0% this a lot in the talk later today the 00:27:22.140 --> 00:27:23.570 align:start position:0% this a lot in the talk later today the back-to-back<00:27:22.620> talk<00:27:22.799> that<00:27:22.980> I<00:27:23.100> have<00:27:23.220> with<00:27:23.340> Carl 00:27:23.570 --> 00:27:23.580 align:start position:0% back-to-back talk that I have with Carl 00:27:23.580 --> 00:27:25.610 align:start position:0% back-to-back talk that I have with Carl but<00:27:24.360> we<00:27:24.539> kind<00:27:24.720> of<00:27:24.779> realized<00:27:25.140> at<00:27:25.320> a<00:27:25.500> certain 00:27:25.610 --> 00:27:25.620 align:start position:0% but we kind of realized at a certain 00:27:25.620 --> 00:27:26.930 align:start position:0% but we kind of realized at a certain point 00:27:26.930 --> 00:27:26.940 align:start position:0% point 00:27:26.940 --> 00:27:28.970 align:start position:0% point that<00:27:27.480> if<00:27:27.720> you<00:27:27.900> really<00:27:28.020> want<00:27:28.260> to<00:27:28.380> maintain<00:27:28.679> one 00:27:28.970 --> 00:27:28.980 align:start position:0% that if you really want to maintain one 00:27:28.980 --> 00:27:31.010 align:start position:0% that if you really want to maintain one of<00:27:29.100> these<00:27:29.279> things<00:27:29.520> you<00:27:30.299> can't<00:27:30.480> allow 00:27:31.010 --> 00:27:31.020 align:start position:0% of these things you can't allow 00:27:31.020 --> 00:27:33.049 align:start position:0% of these things you can't allow different<00:27:31.380> parts<00:27:31.679> of<00:27:31.919> the<00:27:32.100> system<00:27:32.340> to<00:27:32.700> bleed 00:27:33.049 --> 00:27:33.059 align:start position:0% different parts of the system to bleed 00:27:33.059 --> 00:27:35.330 align:start position:0% different parts of the system to bleed complexity<00:27:33.720> into<00:27:34.380> other<00:27:34.740> parts<00:27:34.980> of<00:27:35.220> the 00:27:35.330 --> 00:27:35.340 align:start position:0% complexity into other parts of the 00:27:35.340 --> 00:27:37.490 align:start position:0% complexity into other parts of the system<00:27:35.580> and<00:27:36.120> the<00:27:36.299> classic<00:27:36.539> example<00:27:37.080> that<00:27:37.320> we 00:27:37.490 --> 00:27:37.500 align:start position:0% system and the classic example that we 00:27:37.500 --> 00:27:40.190 align:start position:0% system and the classic example that we saw<00:27:37.740> over<00:27:38.039> the<00:27:38.279> last<00:27:38.460> two<00:27:38.700> years<00:27:38.940> was<00:27:39.840> we 00:27:40.190 --> 00:27:40.200 align:start position:0% saw over the last two years was we 00:27:40.200 --> 00:27:43.190 align:start position:0% saw over the last two years was we separated<00:27:40.679> execution<00:27:41.460> from<00:27:42.120> proving<00:27:42.659> this 00:27:43.190 --> 00:27:43.200 align:start position:0% separated execution from proving this 00:27:43.200 --> 00:27:45.110 align:start position:0% separated execution from proving this was<00:27:43.320> the<00:27:43.500> big<00:27:43.679> thing<00:27:43.860> this<00:27:44.220> is<00:27:44.340> what<00:27:44.580> basically 00:27:45.110 --> 00:27:45.120 align:start position:0% was the big thing this is what basically 00:27:45.120 --> 00:27:47.210 align:start position:0% was the big thing this is what basically optimism's<00:27:45.960> evm<00:27:46.380> equivalence<00:27:46.860> upgrade 00:27:47.210 --> 00:27:47.220 align:start position:0% optimism's evm equivalence upgrade 00:27:47.220 --> 00:27:49.250 align:start position:0% optimism's evm equivalence upgrade arbitrims<00:27:48.179> Nitro<00:27:48.539> upgrade<00:27:48.900> they<00:27:49.140> all 00:27:49.250 --> 00:27:49.260 align:start position:0% arbitrims Nitro upgrade they all 00:27:49.260 --> 00:27:51.230 align:start position:0% arbitrims Nitro upgrade they all followed<00:27:49.559> the<00:27:49.740> same<00:27:49.860> pattern<00:27:50.279> which<00:27:50.520> is<00:27:50.700> let's 00:27:51.230 --> 00:27:51.240 align:start position:0% followed the same pattern which is let's 00:27:51.240 --> 00:27:52.850 align:start position:0% followed the same pattern which is let's build<00:27:51.480> the<00:27:51.720> client<00:27:51.960> the<00:27:52.200> way<00:27:52.320> that<00:27:52.500> we<00:27:52.620> want<00:27:52.740> to 00:27:52.850 --> 00:27:52.860 align:start position:0% build the client the way that we want to 00:27:52.860 --> 00:27:54.950 align:start position:0% build the client the way that we want to build<00:27:52.980> the<00:27:53.220> client<00:27:53.460> and<00:27:54.240> then<00:27:54.419> let's<00:27:54.720> make 00:27:54.950 --> 00:27:54.960 align:start position:0% build the client and then let's make 00:27:54.960 --> 00:27:57.470 align:start position:0% build the client and then let's make execution<00:27:55.440> work<00:27:55.740> on<00:27:55.980> top<00:27:56.159> so<00:27:56.880> the<00:27:57.179> end<00:27:57.299> result 00:27:57.470 --> 00:27:57.480 align:start position:0% execution work on top so the end result 00:27:57.480 --> 00:27:59.269 align:start position:0% execution work on top so the end result of<00:27:57.779> all<00:27:57.960> of<00:27:58.080> this<00:27:58.200> overall<00:27:58.620> this<00:27:58.799> time<00:27:58.980> is<00:27:59.100> that 00:27:59.269 --> 00:27:59.279 align:start position:0% of all of this overall this time is that 00:27:59.279 --> 00:28:01.610 align:start position:0% of all of this overall this time is that we've<00:27:59.520> broken<00:27:59.700> up<00:28:00.000> our<00:28:00.360> system<00:28:00.600> into<00:28:01.200> a<00:28:01.380> highly 00:28:01.610 --> 00:28:01.620 align:start position:0% we've broken up our system into a highly 00:28:01.620 --> 00:28:02.990 align:start position:0% we've broken up our system into a highly modular<00:28:01.980> system<00:28:02.279> with<00:28:02.580> lots<00:28:02.820> of<00:28:02.880> different 00:28:02.990 --> 00:28:03.000 align:start position:0% modular system with lots of different 00:28:03.000 --> 00:28:05.570 align:start position:0% modular system with lots of different pieces<00:28:03.919> we<00:28:04.919> think<00:28:05.039> that<00:28:05.159> there's<00:28:05.340> three 00:28:05.570 --> 00:28:05.580 align:start position:0% pieces we think that there's three 00:28:05.580 --> 00:28:07.370 align:start position:0% pieces we think that there's three simple<00:28:05.820> layers<00:28:06.240> that<00:28:06.659> kind<00:28:06.900> of<00:28:07.020> follow<00:28:07.140> what 00:28:07.370 --> 00:28:07.380 align:start position:0% simple layers that kind of follow what 00:28:07.380 --> 00:28:08.930 align:start position:0% simple layers that kind of follow what you<00:28:07.500> think<00:28:07.679> oh<00:28:07.980> there<00:28:08.220> we<00:28:08.340> go<00:28:08.460> look<00:28:08.640> you've 00:28:08.930 --> 00:28:08.940 align:start position:0% you think oh there we go look you've 00:28:08.940 --> 00:28:10.690 align:start position:0% you think oh there we go look you've seen<00:28:09.059> these<00:28:09.299> things<00:28:09.360> before<00:28:09.600> consensus 00:28:10.690 --> 00:28:10.700 align:start position:0% seen these things before consensus 00:28:10.700 --> 00:28:13.070 align:start position:0% seen these things before consensus execution<00:28:11.700> settlement<00:28:12.299> you've<00:28:12.659> seen<00:28:12.840> these 00:28:13.070 --> 00:28:13.080 align:start position:0% execution settlement you've seen these 00:28:13.080 --> 00:28:14.149 align:start position:0% execution settlement you've seen these things<00:28:13.140> before<00:28:13.380> if<00:28:13.620> you've<00:28:13.860> heard<00:28:13.980> anything 00:28:14.149 --> 00:28:14.159 align:start position:0% things before if you've heard anything 00:28:14.159 --> 00:28:16.370 align:start position:0% things before if you've heard anything about<00:28:14.400> modular<00:28:14.960> blockchains<00:28:15.960> you<00:28:16.080> kind<00:28:16.260> of 00:28:16.370 --> 00:28:16.380 align:start position:0% about modular blockchains you kind of 00:28:16.380 --> 00:28:17.590 align:start position:0% about modular blockchains you kind of have<00:28:16.500> an<00:28:16.740> idea 00:28:17.590 --> 00:28:17.600 align:start position:0% have an idea 00:28:17.600 --> 00:28:20.590 align:start position:0% have an idea of<00:28:18.600> what<00:28:18.779> the<00:28:18.900> op<00:28:19.020> stack<00:28:19.500> is<00:28:19.679> all<00:28:19.860> about 00:28:20.590 --> 00:28:20.600 align:start position:0% of what the op stack is all about 00:28:20.600 --> 00:28:23.930 align:start position:0% of what the op stack is all about except<00:28:21.600> the<00:28:22.500> lp<00:28:22.799> stack<00:28:23.100> is<00:28:23.400> putting<00:28:23.760> this 00:28:23.930 --> 00:28:23.940 align:start position:0% except the lp stack is putting this 00:28:23.940 --> 00:28:26.090 align:start position:0% except the lp stack is putting this modular<00:28:24.299> Theory<00:28:24.779> into<00:28:25.080> practice<00:28:25.380> so<00:28:25.799> the<00:28:25.919> real 00:28:26.090 --> 00:28:26.100 align:start position:0% modular Theory into practice so the real 00:28:26.100 --> 00:28:28.610 align:start position:0% modular Theory into practice so the real difference<00:28:26.340> here<00:28:26.580> is<00:28:26.940> it's<00:28:27.539> not<00:28:27.779> just<00:28:28.020> charts 00:28:28.610 --> 00:28:28.620 align:start position:0% difference here is it's not just charts 00:28:28.620 --> 00:28:30.950 align:start position:0% difference here is it's not just charts on<00:28:28.919> a<00:28:29.039> blog<00:28:29.279> post<00:28:29.460> about<00:28:29.760> okay<00:28:30.360> if<00:28:30.600> you<00:28:30.720> plugged 00:28:30.950 --> 00:28:30.960 align:start position:0% on a blog post about okay if you plugged 00:28:30.960 --> 00:28:32.630 align:start position:0% on a blog post about okay if you plugged in<00:28:31.080> this<00:28:31.260> data<00:28:31.559> availability<00:28:31.860> layer<00:28:32.340> you'd 00:28:32.630 --> 00:28:32.640 align:start position:0% in this data availability layer you'd 00:28:32.640 --> 00:28:34.430 align:start position:0% in this data availability layer you'd get<00:28:32.760> you<00:28:33.120> get<00:28:33.299> this<00:28:33.539> behavior<00:28:33.960> and<00:28:34.140> if<00:28:34.320> you 00:28:34.430 --> 00:28:34.440 align:start position:0% get you get this behavior and if you 00:28:34.440 --> 00:28:35.930 align:start position:0% get you get this behavior and if you plugged<00:28:34.679> in<00:28:34.799> this<00:28:34.980> data<00:28:35.279> availability<00:28:35.520> layer 00:28:35.930 --> 00:28:35.940 align:start position:0% plugged in this data availability layer 00:28:35.940 --> 00:28:38.510 align:start position:0% plugged in this data availability layer you<00:28:36.059> get<00:28:36.240> this<00:28:36.360> other<00:28:36.539> Behavior<00:28:37.020> instead<00:28:37.919> it's 00:28:38.510 --> 00:28:38.520 align:start position:0% you get this other Behavior instead it's 00:28:38.520 --> 00:28:40.430 align:start position:0% you get this other Behavior instead it's actually<00:28:38.760> concrete<00:28:39.480> components<00:28:40.020> that<00:28:40.260> you 00:28:40.430 --> 00:28:40.440 align:start position:0% actually concrete components that you 00:28:40.440 --> 00:28:42.409 align:start position:0% actually concrete components that you can<00:28:40.559> Implement<00:28:40.860> and<00:28:41.039> you<00:28:41.279> can<00:28:41.340> switch<00:28:41.580> out<00:28:41.820> to 00:28:42.409 --> 00:28:42.419 align:start position:0% can Implement and you can switch out to 00:28:42.419 --> 00:28:45.049 align:start position:0% can Implement and you can switch out to get<00:28:42.600> the<00:28:42.840> behavior<00:28:43.200> that<00:28:43.559> you<00:28:43.740> want 00:28:45.049 --> 00:28:45.059 align:start position:0% get the behavior that you want 00:28:45.059 --> 00:28:45.830 align:start position:0% get the behavior that you want um 00:28:45.830 --> 00:28:45.840 align:start position:0% um 00:28:45.840 --> 00:28:46.970 align:start position:0% um so<00:28:46.140> I'm<00:28:46.260> going<00:28:46.380> to<00:28:46.380> talk<00:28:46.500> to<00:28:46.620> you<00:28:46.679> about<00:28:46.799> the 00:28:46.970 --> 00:28:46.980 align:start position:0% so I'm going to talk to you about the 00:28:46.980 --> 00:28:48.590 align:start position:0% so I'm going to talk to you about the Core<00:28:47.159> Concepts<00:28:47.700> the<00:28:47.880> different<00:28:48.059> components 00:28:48.590 --> 00:28:48.600 align:start position:0% Core Concepts the different components 00:28:48.600 --> 00:28:50.690 align:start position:0% Core Concepts the different components that<00:28:48.840> you<00:28:49.020> can<00:28:49.140> switch<00:28:49.380> out<00:28:49.679> and<00:28:50.279> sort<00:28:50.400> of<00:28:50.520> what 00:28:50.690 --> 00:28:50.700 align:start position:0% that you can switch out and sort of what 00:28:50.700 --> 00:28:52.370 align:start position:0% that you can switch out and sort of what you<00:28:50.880> might<00:28:51.059> do<00:28:51.299> if<00:28:51.600> you<00:28:51.720> wanted<00:28:51.840> to<00:28:52.020> build<00:28:52.200> a 00:28:52.370 --> 00:28:52.380 align:start position:0% you might do if you wanted to build a 00:28:52.380 --> 00:28:54.649 align:start position:0% you might do if you wanted to build a game<00:28:52.880> to<00:28:53.880> to<00:28:54.059> use<00:28:54.299> these<00:28:54.600> different 00:28:54.649 --> 00:28:54.659 align:start position:0% game to to use these different 00:28:54.659 --> 00:28:55.850 align:start position:0% game to to use these different components<00:28:55.140> and<00:28:55.260> do<00:28:55.440> something<00:28:55.620> really 00:28:55.850 --> 00:28:55.860 align:start position:0% components and do something really 00:28:55.860 --> 00:28:56.870 align:start position:0% components and do something really interesting 00:28:56.870 --> 00:28:56.880 align:start position:0% interesting 00:28:56.880 --> 00:28:59.210 align:start position:0% interesting so<00:28:57.659> the<00:28:58.020> first<00:28:58.140> layer<00:28:58.440> that<00:28:58.620> we<00:28:58.799> like<00:28:58.919> to<00:28:59.100> break 00:28:59.210 --> 00:28:59.220 align:start position:0% so the first layer that we like to break 00:28:59.220 --> 00:29:01.070 align:start position:0% so the first layer that we like to break out<00:28:59.460> of<00:28:59.880> these<00:29:00.120> different<00:29:00.299> there's<00:29:00.659> obviously 00:29:01.070 --> 00:29:01.080 align:start position:0% out of these different there's obviously 00:29:01.080 --> 00:29:03.110 align:start position:0% out of these different there's obviously the<00:29:01.320> three<00:29:01.559> the<00:29:01.860> three<00:29:02.279> primary<00:29:02.700> layers 00:29:03.110 --> 00:29:03.120 align:start position:0% the three the three primary layers 00:29:03.120 --> 00:29:05.750 align:start position:0% the three the three primary layers inside<00:29:04.080> of<00:29:04.440> consensus<00:29:04.980> we<00:29:05.159> think<00:29:05.340> of<00:29:05.520> two 00:29:05.750 --> 00:29:05.760 align:start position:0% inside of consensus we think of two 00:29:05.760 --> 00:29:08.029 align:start position:0% inside of consensus we think of two sub-layers<00:29:06.480> quickly<00:29:06.900> here<00:29:07.140> we've<00:29:07.380> got<00:29:07.559> what 00:29:08.029 --> 00:29:08.039 align:start position:0% sub-layers quickly here we've got what 00:29:08.039 --> 00:29:09.950 align:start position:0% sub-layers quickly here we've got what we<00:29:08.159> call<00:29:08.279> data<00:29:08.640> availability<00:29:09.000> and<00:29:09.419> derivation 00:29:09.950 --> 00:29:09.960 align:start position:0% we call data availability and derivation 00:29:09.960 --> 00:29:12.049 align:start position:0% we call data availability and derivation but<00:29:10.740> I'll<00:29:10.860> start<00:29:11.039> with<00:29:11.159> data<00:29:11.460> availability<00:29:11.760> so 00:29:12.049 --> 00:29:12.059 align:start position:0% but I'll start with data availability so 00:29:12.059 --> 00:29:13.370 align:start position:0% but I'll start with data availability so you've<00:29:12.360> probably<00:29:12.480> heard<00:29:12.720> about<00:29:12.900> this<00:29:13.140> you 00:29:13.370 --> 00:29:13.380 align:start position:0% you've probably heard about this you 00:29:13.380 --> 00:29:14.810 align:start position:0% you've probably heard about this you probably<00:29:13.559> have<00:29:13.740> a<00:29:13.860> basic<00:29:14.100> idea<00:29:14.400> of<00:29:14.520> how<00:29:14.700> this 00:29:14.810 --> 00:29:14.820 align:start position:0% probably have a basic idea of how this 00:29:14.820 --> 00:29:17.390 align:start position:0% probably have a basic idea of how this works<00:29:15.620> data<00:29:16.620> availability<00:29:16.860> is<00:29:17.100> where<00:29:17.279> you 00:29:17.390 --> 00:29:17.400 align:start position:0% works data availability is where you 00:29:17.400 --> 00:29:19.970 align:start position:0% works data availability is where you publish<00:29:17.640> your<00:29:17.820> data<00:29:18.179> right<00:29:18.539> so<00:29:19.320> the<00:29:19.620> idea<00:29:19.860> is 00:29:19.970 --> 00:29:19.980 align:start position:0% publish your data right so the idea is 00:29:19.980 --> 00:29:22.070 align:start position:0% publish your data right so the idea is well<00:29:20.460> people<00:29:20.820> don't<00:29:21.179> always<00:29:21.480> want<00:29:21.720> to<00:29:21.840> publish 00:29:22.070 --> 00:29:22.080 align:start position:0% well people don't always want to publish 00:29:22.080 --> 00:29:23.810 align:start position:0% well people don't always want to publish their<00:29:22.260> data<00:29:22.500> to<00:29:22.620> ethereum<00:29:23.100> all<00:29:23.279> the<00:29:23.399> Roll-Ups 00:29:23.810 --> 00:29:23.820 align:start position:0% their data to ethereum all the Roll-Ups 00:29:23.820 --> 00:29:25.490 align:start position:0% their data to ethereum all the Roll-Ups originally<00:29:24.120> were<00:29:24.360> built<00:29:24.659> under<00:29:25.020> the<00:29:25.260> idea 00:29:25.490 --> 00:29:25.500 align:start position:0% originally were built under the idea 00:29:25.500 --> 00:29:27.230 align:start position:0% originally were built under the idea that<00:29:25.740> okay<00:29:25.980> we're<00:29:26.520> always<00:29:26.700> going<00:29:26.880> to<00:29:27.000> publish 00:29:27.230 --> 00:29:27.240 align:start position:0% that okay we're always going to publish 00:29:27.240 --> 00:29:29.630 align:start position:0% that okay we're always going to publish our<00:29:27.360> data<00:29:27.659> to<00:29:27.720> ethereum<00:29:28.260> so<00:29:29.039> let's<00:29:29.159> just<00:29:29.399> build 00:29:29.630 --> 00:29:29.640 align:start position:0% our data to ethereum so let's just build 00:29:29.640 --> 00:29:31.549 align:start position:0% our data to ethereum so let's just build our<00:29:29.880> architecture<00:29:30.419> under<00:29:30.779> that<00:29:31.020> assumption 00:29:31.549 --> 00:29:31.559 align:start position:0% our architecture under that assumption 00:29:31.559 --> 00:29:34.130 align:start position:0% our architecture under that assumption and<00:29:32.399> so<00:29:32.580> the<00:29:32.760> op<00:29:32.940> stack<00:29:33.360> basically<00:29:33.659> says<00:29:33.899> well 00:29:34.130 --> 00:29:34.140 align:start position:0% and so the op stack basically says well 00:29:34.140 --> 00:29:36.230 align:start position:0% and so the op stack basically says well actually<00:29:34.320> whatever<00:29:34.679> as<00:29:35.399> long<00:29:35.580> as<00:29:35.700> you<00:29:35.940> kind<00:29:36.120> of 00:29:36.230 --> 00:29:36.240 align:start position:0% actually whatever as long as you kind of 00:29:36.240 --> 00:29:38.990 align:start position:0% actually whatever as long as you kind of have<00:29:36.419> an<00:29:36.659> array<00:29:37.020> of<00:29:37.679> blobs<00:29:38.279> that's<00:29:38.640> what<00:29:38.880> we 00:29:38.990 --> 00:29:39.000 align:start position:0% have an array of blobs that's what we 00:29:39.000 --> 00:29:40.789 align:start position:0% have an array of blobs that's what we call<00:29:39.179> them<00:29:39.360> they<00:29:39.840> can<00:29:39.960> be<00:29:40.080> blocks<00:29:40.559> if<00:29:40.679> you're 00:29:40.789 --> 00:29:40.799 align:start position:0% call them they can be blocks if you're 00:29:40.799 --> 00:29:42.230 align:start position:0% call them they can be blocks if you're ethereum<00:29:41.279> they<00:29:41.399> can<00:29:41.580> be<00:29:41.640> blocks<00:29:42.000> if<00:29:42.120> you're 00:29:42.230 --> 00:29:42.240 align:start position:0% ethereum they can be blocks if you're 00:29:42.240 --> 00:29:43.730 align:start position:0% ethereum they can be blocks if you're Celestia<00:29:42.720> they<00:29:42.899> could<00:29:43.020> be<00:29:43.140> all<00:29:43.320> sorts<00:29:43.679> of 00:29:43.730 --> 00:29:43.740 align:start position:0% Celestia they could be all sorts of 00:29:43.740 --> 00:29:45.529 align:start position:0% Celestia they could be all sorts of different<00:29:43.919> things<00:29:44.220> but<00:29:44.940> essentially<00:29:45.299> what 00:29:45.529 --> 00:29:45.539 align:start position:0% different things but essentially what 00:29:45.539 --> 00:29:49.010 align:start position:0% different things but essentially what you<00:29:45.720> want<00:29:45.840> is<00:29:46.020> an<00:29:46.260> array<00:29:46.500> of<00:29:46.679> things 00:29:49.010 --> 00:29:49.020 align:start position:0% 00:29:49.020 --> 00:29:51.830 align:start position:0% where<00:29:49.679> you<00:29:49.860> can<00:29:49.980> publish<00:29:50.279> data<00:29:50.700> to<00:29:50.840> and 00:29:51.830 --> 00:29:51.840 align:start position:0% where you can publish data to and 00:29:51.840 --> 00:29:52.909 align:start position:0% where you can publish data to and ideally 00:29:52.909 --> 00:29:52.919 align:start position:0% ideally 00:29:52.919 --> 00:29:55.250 align:start position:0% ideally you<00:29:53.460> have<00:29:53.520> some<00:29:53.700> properties<00:29:54.059> about<00:29:54.419> this<00:29:54.840> data 00:29:55.250 --> 00:29:55.260 align:start position:0% you have some properties about this data 00:29:55.260 --> 00:29:56.570 align:start position:0% you have some properties about this data availability<00:29:55.559> layer 00:29:56.570 --> 00:29:56.580 align:start position:0% availability layer 00:29:56.580 --> 00:29:58.669 align:start position:0% availability layer ideally<00:29:57.480> it's<00:29:57.779> somewhat<00:29:58.140> immutable 00:29:58.669 --> 00:29:58.679 align:start position:0% ideally it's somewhat immutable 00:29:58.679 --> 00:30:00.110 align:start position:0% ideally it's somewhat immutable otherwise<00:29:59.159> the<00:29:59.399> whole<00:29:59.520> thing<00:29:59.700> is<00:29:59.880> just<00:30:00.000> going 00:30:00.110 --> 00:30:00.120 align:start position:0% otherwise the whole thing is just going 00:30:00.120 --> 00:30:01.669 align:start position:0% otherwise the whole thing is just going to<00:30:00.240> keep<00:30:00.360> rearging<00:30:00.899> itself<00:30:01.200> and<00:30:01.380> that's<00:30:01.500> going 00:30:01.669 --> 00:30:01.679 align:start position:0% to keep rearging itself and that's going 00:30:01.679 --> 00:30:03.590 align:start position:0% to keep rearging itself and that's going to<00:30:01.740> be<00:30:01.799> really<00:30:01.980> annoying<00:30:02.340> ideally<00:30:03.120> the<00:30:03.299> data 00:30:03.590 --> 00:30:03.600 align:start position:0% to be really annoying ideally the data 00:30:03.600 --> 00:30:04.730 align:start position:0% to be really annoying ideally the data is<00:30:03.659> actually<00:30:03.840> available<00:30:04.020> otherwise<00:30:04.620> you 00:30:04.730 --> 00:30:04.740 align:start position:0% is actually available otherwise you 00:30:04.740 --> 00:30:06.710 align:start position:0% is actually available otherwise you can't<00:30:04.860> do<00:30:05.100> anything<00:30:05.340> with<00:30:05.640> it<00:30:05.820> so<00:30:06.539> there's 00:30:06.710 --> 00:30:06.720 align:start position:0% can't do anything with it so there's 00:30:06.720 --> 00:30:08.450 align:start position:0% can't do anything with it so there's some<00:30:06.960> properties<00:30:07.320> that<00:30:07.620> you<00:30:07.740> want<00:30:07.919> about<00:30:08.159> this 00:30:08.450 --> 00:30:08.460 align:start position:0% some properties that you want about this 00:30:08.460 --> 00:30:09.889 align:start position:0% some properties that you want about this but<00:30:08.880> the<00:30:09.000> nice<00:30:09.059> thing<00:30:09.240> is<00:30:09.299> the<00:30:09.419> openstack 00:30:09.889 --> 00:30:09.899 align:start position:0% but the nice thing is the openstack 00:30:09.899 --> 00:30:11.330 align:start position:0% but the nice thing is the openstack basically<00:30:10.200> says<00:30:10.380> well<00:30:10.620> whatever<00:30:10.860> you<00:30:11.279> can 00:30:11.330 --> 00:30:11.340 align:start position:0% basically says well whatever you can 00:30:11.340 --> 00:30:13.190 align:start position:0% basically says well whatever you can Define<00:30:11.520> any<00:30:11.940> data<00:30:12.240> availability<00:30:12.539> layer<00:30:12.960> as 00:30:13.190 --> 00:30:13.200 align:start position:0% Define any data availability layer as 00:30:13.200 --> 00:30:14.990 align:start position:0% Define any data availability layer as long<00:30:13.320> as<00:30:13.440> it<00:30:13.559> fits<00:30:13.860> this<00:30:14.039> basic<00:30:14.460> idea<00:30:14.760> that 00:30:14.990 --> 00:30:15.000 align:start position:0% long as it fits this basic idea that 00:30:15.000 --> 00:30:18.130 align:start position:0% long as it fits this basic idea that it's<00:30:15.120> an<00:30:15.299> array<00:30:15.720> of<00:30:16.440> you<00:30:16.799> know<00:30:16.860> byte<00:30:17.279> strings 00:30:18.130 --> 00:30:18.140 align:start position:0% it's an array of you know byte strings 00:30:18.140 --> 00:30:20.210 align:start position:0% it's an array of you know byte strings you<00:30:19.140> can<00:30:19.200> slot<00:30:19.559> it<00:30:19.679> in<00:30:19.740> as<00:30:19.919> your<00:30:20.039> data 00:30:20.210 --> 00:30:20.220 align:start position:0% you can slot it in as your data 00:30:20.220 --> 00:30:21.769 align:start position:0% you can slot it in as your data availability<00:30:20.520> layer<00:30:20.940> so<00:30:21.059> concretely<00:30:21.539> what 00:30:21.769 --> 00:30:21.779 align:start position:0% availability layer so concretely what 00:30:21.779 --> 00:30:23.450 align:start position:0% availability layer so concretely what can<00:30:21.960> you<00:30:22.080> do<00:30:22.140> with<00:30:22.320> this<00:30:22.500> I<00:30:22.980> think<00:30:23.100> the<00:30:23.279> easy 00:30:23.450 --> 00:30:23.460 align:start position:0% can you do with this I think the easy 00:30:23.460 --> 00:30:26.029 align:start position:0% can you do with this I think the easy example<00:30:24.360> is<00:30:24.659> instead<00:30:25.380> of<00:30:25.500> putting<00:30:25.799> all<00:30:25.919> your 00:30:26.029 --> 00:30:26.039 align:start position:0% example is instead of putting all your 00:30:26.039 --> 00:30:29.510 align:start position:0% example is instead of putting all your data<00:30:26.399> onto<00:30:27.320> ethereum<00:30:28.320> you<00:30:28.799> can<00:30:28.860> use<00:30:29.100> something 00:30:29.510 --> 00:30:29.520 align:start position:0% data onto ethereum you can use something 00:30:29.520 --> 00:30:31.669 align:start position:0% data onto ethereum you can use something like<00:30:30.000> a<00:30:30.419> data<00:30:30.720> availability<00:30:31.020> committee 00:30:31.669 --> 00:30:31.679 align:start position:0% like a data availability committee 00:30:31.679 --> 00:30:33.710 align:start position:0% like a data availability committee instead<00:30:32.039> reduce<00:30:32.460> your<00:30:32.760> costs<00:30:33.179> make<00:30:33.539> your 00:30:33.710 --> 00:30:33.720 align:start position:0% instead reduce your costs make your 00:30:33.720 --> 00:30:35.570 align:start position:0% instead reduce your costs make your system<00:30:33.899> cheaper<00:30:34.320> I<00:30:34.559> think<00:30:34.679> this<00:30:34.919> is<00:30:35.039> a<00:30:35.340> really 00:30:35.570 --> 00:30:35.580 align:start position:0% system cheaper I think this is a really 00:30:35.580 --> 00:30:37.310 align:start position:0% system cheaper I think this is a really good<00:30:35.820> application<00:30:36.240> for<00:30:36.480> gaming<00:30:36.840> because<00:30:37.020> you 00:30:37.310 --> 00:30:37.320 align:start position:0% good application for gaming because you 00:30:37.320 --> 00:30:39.289 align:start position:0% good application for gaming because you basically<00:30:37.620> you<00:30:38.340> don't<00:30:38.460> need<00:30:38.700> those<00:30:39.000> sort<00:30:39.179> of 00:30:39.289 --> 00:30:39.299 align:start position:0% basically you don't need those sort of 00:30:39.299 --> 00:30:41.630 align:start position:0% basically you don't need those sort of ridiculously<00:30:40.080> high<00:30:40.559> security<00:30:40.860> guarantees 00:30:41.630 --> 00:30:41.640 align:start position:0% ridiculously high security guarantees 00:30:41.640 --> 00:30:43.430 align:start position:0% ridiculously high security guarantees that<00:30:42.179> you<00:30:42.299> do<00:30:42.419> when<00:30:42.659> you<00:30:42.779> have<00:30:42.899> a<00:30:43.080> basic<00:30:43.320> roll 00:30:43.430 --> 00:30:43.440 align:start position:0% that you do when you have a basic roll 00:30:43.440 --> 00:30:45.649 align:start position:0% that you do when you have a basic roll up<00:30:43.620> where<00:30:43.799> you're<00:30:43.980> just<00:30:44.100> putting<00:30:44.940> data<00:30:45.539> on 00:30:45.649 --> 00:30:45.659 align:start position:0% up where you're just putting data on 00:30:45.659 --> 00:30:47.930 align:start position:0% up where you're just putting data on ethereum<00:30:46.080> the<00:30:46.500> ability<00:30:47.039> to<00:30:47.340> switch<00:30:47.520> this<00:30:47.760> out 00:30:47.930 --> 00:30:47.940 align:start position:0% ethereum the ability to switch this out 00:30:47.940 --> 00:30:50.269 align:start position:0% ethereum the ability to switch this out for<00:30:48.299> the<00:30:48.659> data<00:30:48.899> availability<00:30:49.260> committee<00:30:49.860> or<00:30:50.159> a 00:30:50.269 --> 00:30:50.279 align:start position:0% for the data availability committee or a 00:30:50.279 --> 00:30:51.769 align:start position:0% for the data availability committee or a different<00:30:50.399> data<00:30:50.820> availability<00:30:51.059> layer<00:30:51.539> all 00:30:51.769 --> 00:30:51.779 align:start position:0% different data availability layer all 00:30:51.779 --> 00:30:54.830 align:start position:0% different data availability layer all all<00:30:51.899> together<00:30:52.440> is<00:30:53.279> really<00:30:53.520> important<00:30:53.940> to<00:30:54.419> you 00:30:54.830 --> 00:30:54.840 align:start position:0% all together is really important to you 00:30:54.840 --> 00:30:56.510 align:start position:0% all together is really important to you know<00:30:54.899> get<00:30:55.200> the<00:30:55.559> exact<00:30:55.860> sort<00:30:56.100> of<00:30:56.159> security 00:30:56.510 --> 00:30:56.520 align:start position:0% know get the exact sort of security 00:30:56.520 --> 00:30:58.549 align:start position:0% know get the exact sort of security properties<00:30:57.179> that<00:30:57.419> you<00:30:57.600> want<00:30:57.720> depending<00:30:58.380> on 00:30:58.549 --> 00:30:58.559 align:start position:0% properties that you want depending on 00:30:58.559 --> 00:30:59.750 align:start position:0% properties that you want depending on the<00:30:58.679> amount<00:30:58.919> of<00:30:59.039> value<00:30:59.159> that<00:30:59.460> you<00:30:59.640> actually 00:30:59.750 --> 00:30:59.760 align:start position:0% the amount of value that you actually 00:30:59.760 --> 00:31:01.549 align:start position:0% the amount of value that you actually need<00:31:00.000> to<00:31:00.120> secure 00:31:01.549 --> 00:31:01.559 align:start position:0% need to secure 00:31:01.559 --> 00:31:03.889 align:start position:0% need to secure all<00:31:01.919> right<00:31:02.039> derivation<00:31:02.659> derivation<00:31:03.659> is 00:31:03.889 --> 00:31:03.899 align:start position:0% all right derivation derivation is 00:31:03.899 --> 00:31:05.510 align:start position:0% all right derivation derivation is interesting<00:31:04.260> I<00:31:04.500> think<00:31:04.620> derivation<00:31:05.039> is<00:31:05.279> one<00:31:05.399> of 00:31:05.510 --> 00:31:05.520 align:start position:0% interesting I think derivation is one of 00:31:05.520 --> 00:31:07.549 align:start position:0% interesting I think derivation is one of the<00:31:05.580> coolest<00:31:05.880> parts<00:31:06.120> of<00:31:06.360> the<00:31:06.480> the<00:31:06.600> op<00:31:07.020> stack 00:31:07.549 --> 00:31:07.559 align:start position:0% the coolest parts of the the op stack 00:31:07.559 --> 00:31:09.950 align:start position:0% the coolest parts of the the op stack design<00:31:07.740> and<00:31:08.520> essentially<00:31:08.880> the<00:31:09.179> idea<00:31:09.419> is<00:31:09.720> that 00:31:09.950 --> 00:31:09.960 align:start position:0% design and essentially the idea is that 00:31:09.960 --> 00:31:13.070 align:start position:0% design and essentially the idea is that derivation<00:31:10.440> is<00:31:11.100> how<00:31:11.399> you<00:31:11.820> are<00:31:11.940> pulling<00:31:12.419> inputs 00:31:13.070 --> 00:31:13.080 align:start position:0% derivation is how you are pulling inputs 00:31:13.080 --> 00:31:15.289 align:start position:0% derivation is how you are pulling inputs for<00:31:13.380> your<00:31:13.500> blockchain<00:31:13.919> from<00:31:14.820> the<00:31:15.000> data 00:31:15.289 --> 00:31:15.299 align:start position:0% for your blockchain from the data 00:31:15.299 --> 00:31:17.389 align:start position:0% for your blockchain from the data availability<00:31:15.659> layer<00:31:16.200> so<00:31:16.620> derivation<00:31:17.159> is 00:31:17.389 --> 00:31:17.399 align:start position:0% availability layer so derivation is 00:31:17.399 --> 00:31:19.430 align:start position:0% availability layer so derivation is basically<00:31:17.640> like<00:31:17.880> a<00:31:18.059> function<00:31:18.360> that's<00:31:18.960> aware 00:31:19.430 --> 00:31:19.440 align:start position:0% basically like a function that's aware 00:31:19.440 --> 00:31:20.870 align:start position:0% basically like a function that's aware of<00:31:19.620> the<00:31:19.980> structure<00:31:20.340> of<00:31:20.520> the<00:31:20.640> data 00:31:20.870 --> 00:31:20.880 align:start position:0% of the structure of the data 00:31:20.880 --> 00:31:22.549 align:start position:0% of the structure of the data availability<00:31:21.240> layer<00:31:21.659> it's<00:31:21.840> like<00:31:22.080> you<00:31:22.500> know 00:31:22.549 --> 00:31:22.559 align:start position:0% availability layer it's like you know 00:31:22.559 --> 00:31:24.710 align:start position:0% availability layer it's like you know let's<00:31:22.799> say<00:31:22.980> we're<00:31:23.340> putting<00:31:23.820> data<00:31:24.120> on<00:31:24.240> ethereum 00:31:24.710 --> 00:31:24.720 align:start position:0% let's say we're putting data on ethereum 00:31:24.720 --> 00:31:26.510 align:start position:0% let's say we're putting data on ethereum it's<00:31:25.200> aware<00:31:25.500> of<00:31:25.620> the<00:31:25.799> block<00:31:25.919> structure<00:31:26.399> it's 00:31:26.510 --> 00:31:26.520 align:start position:0% it's aware of the block structure it's 00:31:26.520 --> 00:31:28.909 align:start position:0% it's aware of the block structure it's aware<00:31:26.820> of<00:31:26.940> how<00:31:27.179> data<00:31:27.539> is<00:31:27.659> put<00:31:28.080> onto<00:31:28.380> ethereum 00:31:28.909 --> 00:31:28.919 align:start position:0% aware of how data is put onto ethereum 00:31:28.919 --> 00:31:31.490 align:start position:0% aware of how data is put onto ethereum and<00:31:29.460> it<00:31:29.640> parses<00:31:30.120> that<00:31:30.360> data<00:31:30.659> it<00:31:30.840> pulls<00:31:31.200> it<00:31:31.320> out 00:31:31.490 --> 00:31:31.500 align:start position:0% and it parses that data it pulls it out 00:31:31.500 --> 00:31:34.490 align:start position:0% and it parses that data it pulls it out and<00:31:32.100> it<00:31:32.220> turns<00:31:32.580> it<00:31:32.760> into<00:31:33.059> inputs<00:31:34.020> to<00:31:34.320> your 00:31:34.490 --> 00:31:34.500 align:start position:0% and it turns it into inputs to your 00:31:34.500 --> 00:31:36.730 align:start position:0% and it turns it into inputs to your layer<00:31:34.860> 2<00:31:35.039> execution<00:31:35.880> engine 00:31:36.730 --> 00:31:36.740 align:start position:0% layer 2 execution engine 00:31:36.740 --> 00:31:39.049 align:start position:0% layer 2 execution engine derivation<00:31:37.740> is<00:31:37.980> really<00:31:38.159> important<00:31:38.520> and<00:31:38.820> it's 00:31:39.049 --> 00:31:39.059 align:start position:0% derivation is really important and it's 00:31:39.059 --> 00:31:40.669 align:start position:0% derivation is really important and it's you<00:31:39.600> know<00:31:39.720> generically<00:31:40.200> you<00:31:40.440> can<00:31:40.559> understand 00:31:40.669 --> 00:31:40.679 align:start position:0% you know generically you can understand 00:31:40.679 --> 00:31:42.350 align:start position:0% you know generically you can understand why<00:31:41.100> this<00:31:41.279> is<00:31:41.399> important<00:31:41.700> let's<00:31:41.880> say<00:31:42.000> we're<00:31:42.240> a 00:31:42.350 --> 00:31:42.360 align:start position:0% why this is important let's say we're a 00:31:42.360 --> 00:31:44.269 align:start position:0% why this is important let's say we're a roll-up<00:31:42.720> you<00:31:43.500> know<00:31:43.559> the<00:31:43.740> same<00:31:43.919> thing<00:31:44.039> that 00:31:44.269 --> 00:31:44.279 align:start position:0% roll-up you know the same thing that 00:31:44.279 --> 00:31:46.610 align:start position:0% roll-up you know the same thing that we're<00:31:44.399> doing<00:31:44.580> for<00:31:45.000> unannounced<00:31:45.720> game<00:31:45.960> will<00:31:46.440> be 00:31:46.610 --> 00:31:46.620 align:start position:0% we're doing for unannounced game will be 00:31:46.620 --> 00:31:47.769 align:start position:0% we're doing for unannounced game will be announced<00:31:46.919> soon 00:31:47.769 --> 00:31:47.779 align:start position:0% announced soon 00:31:47.779 --> 00:31:50.330 align:start position:0% announced soon if<00:31:48.779> you're<00:31:48.899> one<00:31:49.080> of<00:31:49.200> these<00:31:49.380> systems<00:31:49.799> what<00:31:50.220> you 00:31:50.330 --> 00:31:50.340 align:start position:0% if you're one of these systems what you 00:31:50.340 --> 00:31:52.909 align:start position:0% if you're one of these systems what you do<00:31:50.520> generically<00:31:51.299> is<00:31:51.539> you<00:31:51.720> post<00:31:51.960> data<00:31:52.440> to<00:31:52.679> an 00:31:52.909 --> 00:31:52.919 align:start position:0% do generically is you post data to an 00:31:52.919 --> 00:31:55.010 align:start position:0% do generically is you post data to an address<00:31:53.100> on<00:31:53.460> layer<00:31:53.760> one<00:31:53.940> and<00:31:54.539> maybe<00:31:54.659> you<00:31:54.840> have 00:31:55.010 --> 00:31:55.020 align:start position:0% address on layer one and maybe you have 00:31:55.020 --> 00:31:56.510 align:start position:0% address on layer one and maybe you have deposits<00:31:55.679> and<00:31:55.799> maybe<00:31:55.980> you<00:31:56.100> have<00:31:56.220> some<00:31:56.399> other 00:31:56.510 --> 00:31:56.520 align:start position:0% deposits and maybe you have some other 00:31:56.520 --> 00:31:59.090 align:start position:0% deposits and maybe you have some other sort<00:31:56.820> of<00:31:56.940> information<00:31:57.539> and<00:31:58.440> you<00:31:58.620> transform 00:31:59.090 --> 00:31:59.100 align:start position:0% sort of information and you transform 00:31:59.100 --> 00:32:01.130 align:start position:0% sort of information and you transform all<00:31:59.520> of<00:31:59.640> that<00:31:59.820> maybe<00:32:00.179> you<00:32:00.480> know<00:32:00.600> if<00:32:00.720> it's<00:32:00.840> data 00:32:01.130 --> 00:32:01.140 align:start position:0% all of that maybe you know if it's data 00:32:01.140 --> 00:32:02.990 align:start position:0% all of that maybe you know if it's data posted<00:32:01.320> to<00:32:01.500> layer<00:32:01.980> 1<00:32:02.100> by<00:32:02.279> the<00:32:02.399> sequencer<00:32:02.760> let's 00:32:02.990 --> 00:32:03.000 align:start position:0% posted to layer 1 by the sequencer let's 00:32:03.000 --> 00:32:05.269 align:start position:0% posted to layer 1 by the sequencer let's say<00:32:03.179> you<00:32:03.419> you<00:32:03.779> decompress<00:32:04.440> all<00:32:04.679> of<00:32:04.799> that<00:32:04.980> data 00:32:05.269 --> 00:32:05.279 align:start position:0% say you you decompress all of that data 00:32:05.279 --> 00:32:07.730 align:start position:0% say you you decompress all of that data you<00:32:05.760> transform<00:32:06.179> it<00:32:06.360> into<00:32:06.659> inputs<00:32:07.200> on<00:32:07.380> layer 00:32:07.730 --> 00:32:07.740 align:start position:0% you transform it into inputs on layer 00:32:07.740 --> 00:32:09.470 align:start position:0% you transform it into inputs on layer two<00:32:07.860> and<00:32:08.700> then<00:32:08.820> you're<00:32:08.940> going<00:32:09.059> to<00:32:09.120> execute 00:32:09.470 --> 00:32:09.480 align:start position:0% two and then you're going to execute 00:32:09.480 --> 00:32:11.510 align:start position:0% two and then you're going to execute those<00:32:09.720> inputs<00:32:10.159> derivation<00:32:11.159> is<00:32:11.399> really 00:32:11.510 --> 00:32:11.520 align:start position:0% those inputs derivation is really 00:32:11.520 --> 00:32:12.710 align:start position:0% those inputs derivation is really interesting<00:32:11.820> I<00:32:12.000> think<00:32:12.179> there's<00:32:12.299> a<00:32:12.480> lot<00:32:12.600> of 00:32:12.710 --> 00:32:12.720 align:start position:0% interesting I think there's a lot of 00:32:12.720 --> 00:32:14.210 align:start position:0% interesting I think there's a lot of like<00:32:12.960> hidden<00:32:13.500> things<00:32:13.679> that<00:32:13.860> you<00:32:13.980> can<00:32:14.100> do 00:32:14.210 --> 00:32:14.220 align:start position:0% like hidden things that you can do 00:32:14.220 --> 00:32:15.889 align:start position:0% like hidden things that you can do inside<00:32:14.340> of<00:32:14.580> here<00:32:14.700> that<00:32:15.000> might<00:32:15.179> maybe<00:32:15.419> aren't 00:32:15.889 --> 00:32:15.899 align:start position:0% inside of here that might maybe aren't 00:32:15.899 --> 00:32:17.580 align:start position:0% inside of here that might maybe aren't always<00:32:16.500> obvious 00:32:17.580 --> 00:32:17.590 align:start position:0% always obvious 00:32:17.590 --> 00:32:18.169 align:start position:0% always obvious [Music] 00:32:18.169 --> 00:32:18.179 align:start position:0% [Music] 00:32:18.179 --> 00:32:18.769 align:start position:0% [Music] um 00:32:18.769 --> 00:32:18.779 align:start position:0% um 00:32:18.779 --> 00:32:20.570 align:start position:0% um one<00:32:19.320> of<00:32:19.440> the<00:32:19.500> things<00:32:19.679> that<00:32:19.980> I<00:32:20.159> think<00:32:20.340> people 00:32:20.570 --> 00:32:20.580 align:start position:0% one of the things that I think people 00:32:20.580 --> 00:32:23.750 align:start position:0% one of the things that I think people can<00:32:21.120> achieve<00:32:21.539> with<00:32:21.720> this<00:32:21.960> is<00:32:22.740> have<00:32:23.279> in-game 00:32:23.750 --> 00:32:23.760 align:start position:0% can achieve with this is have in-game 00:32:23.760 --> 00:32:25.310 align:start position:0% can achieve with this is have in-game events<00:32:24.120> or<00:32:24.240> have<00:32:24.419> events<00:32:24.779> on<00:32:25.020> your<00:32:25.140> chain 00:32:25.310 --> 00:32:25.320 align:start position:0% events or have events on your chain 00:32:25.320 --> 00:32:28.850 align:start position:0% events or have events on your chain happen<00:32:25.799> when<00:32:26.580> things<00:32:26.820> happen<00:32:27.240> on<00:32:28.200> the<00:32:28.559> layer 00:32:28.850 --> 00:32:28.860 align:start position:0% happen when things happen on the layer 00:32:28.860 --> 00:32:31.070 align:start position:0% happen when things happen on the layer one<00:32:28.980> so<00:32:29.640> let's<00:32:29.820> say<00:32:30.059> you<00:32:30.539> want<00:32:30.659> to<00:32:30.779> have<00:32:30.899> an 00:32:31.070 --> 00:32:31.080 align:start position:0% one so let's say you want to have an 00:32:31.080 --> 00:32:33.230 align:start position:0% one so let's say you want to have an in-game<00:32:31.440> event<00:32:31.679> happen<00:32:32.100> every<00:32:32.820> time<00:32:33.000> there's 00:32:33.230 --> 00:32:33.240 align:start position:0% in-game event happen every time there's 00:32:33.240 --> 00:32:35.870 align:start position:0% in-game event happen every time there's a<00:32:33.360> uniswap<00:32:33.899> swap<00:32:34.200> event<00:32:34.380> on<00:32:34.679> layer<00:32:34.980> 1<00:32:35.159> over<00:32:35.640> a 00:32:35.870 --> 00:32:35.880 align:start position:0% a uniswap swap event on layer 1 over a 00:32:35.880 --> 00:32:37.730 align:start position:0% a uniswap swap event on layer 1 over a certain<00:32:36.059> value<00:32:36.299> what<00:32:36.960> you<00:32:37.140> can<00:32:37.200> literally<00:32:37.500> do 00:32:37.730 --> 00:32:37.740 align:start position:0% certain value what you can literally do 00:32:37.740 --> 00:32:39.350 align:start position:0% certain value what you can literally do is<00:32:37.919> in<00:32:38.100> your<00:32:38.220> derivation<00:32:38.640> function<00:32:39.000> you<00:32:39.240> can 00:32:39.350 --> 00:32:39.360 align:start position:0% is in your derivation function you can 00:32:39.360 --> 00:32:40.669 align:start position:0% is in your derivation function you can take<00:32:39.480> our<00:32:39.659> derivation<00:32:40.080> function<00:32:40.380> you<00:32:40.559> can 00:32:40.669 --> 00:32:40.679 align:start position:0% take our derivation function you can 00:32:40.679 --> 00:32:42.289 align:start position:0% take our derivation function you can tweak<00:32:40.919> it<00:32:41.039> slightly<00:32:41.340> and<00:32:41.760> you<00:32:41.880> can<00:32:42.000> say<00:32:42.120> okay 00:32:42.289 --> 00:32:42.299 align:start position:0% tweak it slightly and you can say okay 00:32:42.299 --> 00:32:44.149 align:start position:0% tweak it slightly and you can say okay I'm<00:32:42.600> also<00:32:42.840> going<00:32:42.960> to<00:32:43.080> look<00:32:43.140> for<00:32:43.320> uniswap<00:32:43.860> swap 00:32:44.149 --> 00:32:44.159 align:start position:0% I'm also going to look for uniswap swap 00:32:44.159 --> 00:32:45.649 align:start position:0% I'm also going to look for uniswap swap events<00:32:44.520> and<00:32:44.940> then<00:32:45.000> whenever<00:32:45.299> there's<00:32:45.480> a 00:32:45.649 --> 00:32:45.659 align:start position:0% events and then whenever there's a 00:32:45.659 --> 00:32:47.630 align:start position:0% events and then whenever there's a uniswap<00:32:46.140> swap<00:32:46.380> event<00:32:46.559> I'm<00:32:47.039> going<00:32:47.220> to<00:32:47.340> generate 00:32:47.630 --> 00:32:47.640 align:start position:0% uniswap swap event I'm going to generate 00:32:47.640 --> 00:32:49.669 align:start position:0% uniswap swap event I'm going to generate a<00:32:47.820> transaction<00:32:48.059> on<00:32:48.360> layer<00:32:48.659> 2<00:32:48.779> that<00:32:49.260> makes<00:32:49.440> this 00:32:49.669 --> 00:32:49.679 align:start position:0% a transaction on layer 2 that makes this 00:32:49.679 --> 00:32:51.110 align:start position:0% a transaction on layer 2 that makes this thing<00:32:49.860> happen<00:32:50.100> and<00:32:50.340> the<00:32:50.460> end<00:32:50.580> result<00:32:50.760> is<00:32:51.000> that 00:32:51.110 --> 00:32:51.120 align:start position:0% thing happen and the end result is that 00:32:51.120 --> 00:32:53.029 align:start position:0% thing happen and the end result is that in<00:32:51.299> my<00:32:51.419> game<00:32:51.539> fireworks<00:32:52.200> go<00:32:52.320> off<00:32:52.500> whatever<00:32:52.740> you 00:32:53.029 --> 00:32:53.039 align:start position:0% in my game fireworks go off whatever you 00:32:53.039 --> 00:32:54.830 align:start position:0% in my game fireworks go off whatever you want<00:32:53.159> you<00:32:53.640> can<00:32:53.760> basically<00:32:54.059> modify<00:32:54.659> this 00:32:54.830 --> 00:32:54.840 align:start position:0% want you can basically modify this 00:32:54.840 --> 00:32:57.409 align:start position:0% want you can basically modify this however<00:32:55.200> you<00:32:55.500> want<00:32:55.740> to<00:32:56.279> have<00:32:56.520> the<00:32:57.000> state<00:32:57.179> of 00:32:57.409 --> 00:32:57.419 align:start position:0% however you want to have the state of 00:32:57.419 --> 00:32:59.810 align:start position:0% however you want to have the state of your<00:32:57.600> layer<00:32:57.899> 1<00:32:58.080> Define<00:32:58.799> what's<00:32:59.279> going<00:32:59.460> on<00:32:59.640> on 00:32:59.810 --> 00:32:59.820 align:start position:0% your layer 1 Define what's going on on 00:32:59.820 --> 00:33:01.430 align:start position:0% your layer 1 Define what's going on on your<00:32:59.940> Layer<00:33:00.240> Two<00:33:00.360> it<00:33:00.779> doesn't<00:33:00.960> just<00:33:01.140> have<00:33:01.320> to 00:33:01.430 --> 00:33:01.440 align:start position:0% your Layer Two it doesn't just have to 00:33:01.440 --> 00:33:03.529 align:start position:0% your Layer Two it doesn't just have to be<00:33:01.559> transactions<00:33:02.340> you<00:33:02.820> can<00:33:02.880> build<00:33:03.059> amazing 00:33:03.529 --> 00:33:03.539 align:start position:0% be transactions you can build amazing 00:33:03.539 --> 00:33:06.350 align:start position:0% be transactions you can build amazing things<00:33:03.720> with<00:33:04.080> this<00:33:04.399> and<00:33:05.399> it<00:33:05.760> can<00:33:05.820> be<00:33:06.000> very<00:33:06.179> very 00:33:06.350 --> 00:33:06.360 align:start position:0% things with this and it can be very very 00:33:06.360 --> 00:33:07.850 align:start position:0% things with this and it can be very very stateful<00:33:06.840> so<00:33:07.080> you<00:33:07.200> can<00:33:07.260> do<00:33:07.380> a<00:33:07.500> lot<00:33:07.559> of<00:33:07.679> cool 00:33:07.850 --> 00:33:07.860 align:start position:0% stateful so you can do a lot of cool 00:33:07.860 --> 00:33:10.190 align:start position:0% stateful so you can do a lot of cool stuff<00:33:08.159> here 00:33:10.190 --> 00:33:10.200 align:start position:0% stuff here 00:33:10.200 --> 00:33:13.370 align:start position:0% stuff here boom<00:33:10.860> execution<00:33:11.279> okay<00:33:11.580> execution<00:33:12.380> is 00:33:13.370 --> 00:33:13.380 align:start position:0% boom execution okay execution is 00:33:13.380 --> 00:33:15.649 align:start position:0% boom execution okay execution is probably<00:33:13.740> what<00:33:14.220> you<00:33:14.340> think<00:33:14.519> execution<00:33:15.179> is 00:33:15.649 --> 00:33:15.659 align:start position:0% probably what you think execution is 00:33:15.659 --> 00:33:17.870 align:start position:0% probably what you think execution is it's<00:33:16.320> your<00:33:16.679> execution<00:33:17.159> engine<00:33:17.340> on<00:33:17.580> Layer<00:33:17.820> Two 00:33:17.870 --> 00:33:17.880 align:start position:0% it's your execution engine on Layer Two 00:33:17.880 --> 00:33:19.909 align:start position:0% it's your execution engine on Layer Two it's<00:33:18.059> your<00:33:18.240> state<00:33:18.419> transition<00:33:18.840> function<00:33:19.380> it's 00:33:19.909 --> 00:33:19.919 align:start position:0% it's your state transition function it's 00:33:19.919 --> 00:33:22.490 align:start position:0% it's your state transition function it's the<00:33:20.159> thing<00:33:20.340> that<00:33:20.700> takes<00:33:20.940> up<00:33:21.480> the<00:33:21.840> inputs<00:33:22.260> that 00:33:22.490 --> 00:33:22.500 align:start position:0% the thing that takes up the inputs that 00:33:22.500 --> 00:33:24.409 align:start position:0% the thing that takes up the inputs that were<00:33:22.679> generated<00:33:23.039> by<00:33:23.340> the<00:33:23.460> derivation<00:33:24.000> layer 00:33:24.409 --> 00:33:24.419 align:start position:0% were generated by the derivation layer 00:33:24.419 --> 00:33:26.570 align:start position:0% were generated by the derivation layer and<00:33:24.840> it<00:33:24.960> takes<00:33:25.140> the<00:33:25.380> current<00:33:25.620> state<00:33:25.980> and<00:33:26.460> it's 00:33:26.570 --> 00:33:26.580 align:start position:0% and it takes the current state and it's 00:33:26.580 --> 00:33:28.669 align:start position:0% and it takes the current state and it's going<00:33:26.700> to<00:33:26.820> translate<00:33:27.120> that<00:33:27.659> state<00:33:27.840> into<00:33:28.260> a<00:33:28.559> new 00:33:28.669 --> 00:33:28.679 align:start position:0% going to translate that state into a new 00:33:28.679 --> 00:33:30.889 align:start position:0% going to translate that state into a new state<00:33:28.980> right<00:33:29.580> it's<00:33:30.059> going<00:33:30.299> to<00:33:30.419> take<00:33:30.659> that 00:33:30.889 --> 00:33:30.899 align:start position:0% state right it's going to take that 00:33:30.899 --> 00:33:32.690 align:start position:0% state right it's going to take that state<00:33:31.080> into<00:33:31.500> a<00:33:31.679> new<00:33:31.799> state<00:33:31.980> and<00:33:32.220> that<00:33:32.340> state<00:33:32.519> is 00:33:32.690 --> 00:33:32.700 align:start position:0% state into a new state and that state is 00:33:32.700 --> 00:33:34.310 align:start position:0% state into a new state and that state is going<00:33:32.820> to<00:33:32.880> be<00:33:33.000> used<00:33:33.120> to<00:33:33.419> derive<00:33:33.720> new<00:33:33.899> inputs 00:33:34.310 --> 00:33:34.320 align:start position:0% going to be used to derive new inputs 00:33:34.320 --> 00:33:35.930 align:start position:0% going to be used to derive new inputs and<00:33:34.500> it's<00:33:34.620> going<00:33:34.799> to<00:33:34.919> be<00:33:34.980> you<00:33:35.340> know<00:33:35.460> you<00:33:35.700> get<00:33:35.820> it 00:33:35.930 --> 00:33:35.940 align:start position:0% and it's going to be you know you get it 00:33:35.940 --> 00:33:38.029 align:start position:0% and it's going to be you know you get it right<00:33:36.120> every<00:33:36.419> time<00:33:36.720> I<00:33:37.080> make<00:33:37.380> a<00:33:37.559> transaction 00:33:38.029 --> 00:33:38.039 align:start position:0% right every time I make a transaction 00:33:38.039 --> 00:33:40.310 align:start position:0% right every time I make a transaction and<00:33:38.700> something<00:33:38.880> happens<00:33:39.179> in<00:33:39.480> my<00:33:39.659> voxel<00:33:40.019> game 00:33:40.310 --> 00:33:40.320 align:start position:0% and something happens in my voxel game 00:33:40.320 --> 00:33:42.769 align:start position:0% and something happens in my voxel game and<00:33:40.799> the<00:33:40.980> world<00:33:41.100> updates<00:33:41.640> that's<00:33:42.480> what's 00:33:42.769 --> 00:33:42.779 align:start position:0% and the world updates that's what's 00:33:42.779 --> 00:33:43.909 align:start position:0% and the world updates that's what's happening<00:33:43.140> under<00:33:43.320> the<00:33:43.500> hood<00:33:43.620> in<00:33:43.799> the 00:33:43.909 --> 00:33:43.919 align:start position:0% happening under the hood in the 00:33:43.919 --> 00:33:46.789 align:start position:0% happening under the hood in the execution<00:33:44.279> engine<00:33:44.960> the<00:33:45.960> execution<00:33:46.320> engine<00:33:46.559> in 00:33:46.789 --> 00:33:46.799 align:start position:0% execution engine the execution engine in 00:33:46.799 --> 00:33:49.430 align:start position:0% execution engine the execution engine in the<00:33:46.919> op<00:33:47.039> stack<00:33:47.519> lives<00:33:48.179> behind<00:33:48.539> the<00:33:48.720> engine<00:33:48.840> API 00:33:49.430 --> 00:33:49.440 align:start position:0% the op stack lives behind the engine API 00:33:49.440 --> 00:33:52.090 align:start position:0% the op stack lives behind the engine API right<00:33:49.740> so<00:33:49.980> what<00:33:50.159> we<00:33:50.279> decided<00:33:50.700> to<00:33:50.760> do<00:33:50.940> was 00:33:52.090 --> 00:33:52.100 align:start position:0% right so what we decided to do was 00:33:52.100 --> 00:33:54.350 align:start position:0% right so what we decided to do was ethereum<00:33:53.100> you<00:33:53.580> know<00:33:53.700> while<00:33:53.820> it<00:33:54.000> was<00:33:54.059> going<00:33:54.179> to 00:33:54.350 --> 00:33:54.360 align:start position:0% ethereum you know while it was going to 00:33:54.360 --> 00:33:56.990 align:start position:0% ethereum you know while it was going to the<00:33:54.480> merge<00:33:54.779> needed<00:33:55.380> consensus<00:33:56.039> clients<00:33:56.460> and<00:33:56.880> a 00:33:56.990 --> 00:33:57.000 align:start position:0% the merge needed consensus clients and a 00:33:57.000 --> 00:33:59.269 align:start position:0% the merge needed consensus clients and a needed<00:33:57.360> execution<00:33:57.840> clients<00:33:58.380> right<00:33:58.559> so<00:33:59.159> you 00:33:59.269 --> 00:33:59.279 align:start position:0% needed execution clients right so you 00:33:59.279 --> 00:34:01.370 align:start position:0% needed execution clients right so you need<00:33:59.460> a<00:33:59.640> way<00:33:59.760> to<00:34:00.059> talk<00:34:00.299> between<00:34:00.600> the<00:34:00.899> consensus 00:34:01.370 --> 00:34:01.380 align:start position:0% need a way to talk between the consensus 00:34:01.380 --> 00:34:03.529 align:start position:0% need a way to talk between the consensus client<00:34:01.620> and<00:34:01.860> the<00:34:01.980> execution<00:34:02.340> client<00:34:02.760> and<00:34:03.299> that 00:34:03.529 --> 00:34:03.539 align:start position:0% client and the execution client and that 00:34:03.539 --> 00:34:06.409 align:start position:0% client and the execution client and that interface<00:34:03.960> between<00:34:04.260> the<00:34:04.500> two<00:34:04.679> clients<00:34:05.100> is<00:34:06.000> the 00:34:06.409 --> 00:34:06.419 align:start position:0% interface between the two clients is the 00:34:06.419 --> 00:34:08.389 align:start position:0% interface between the two clients is the engine<00:34:06.600> API 00:34:08.389 --> 00:34:08.399 align:start position:0% engine API 00:34:08.399 --> 00:34:10.909 align:start position:0% engine API so<00:34:08.820> what<00:34:09.060> we<00:34:09.179> did<00:34:09.300> was<00:34:09.599> basically<00:34:10.139> take<00:34:10.679> the 00:34:10.909 --> 00:34:10.919 align:start position:0% so what we did was basically take the 00:34:10.919 --> 00:34:13.669 align:start position:0% so what we did was basically take the same<00:34:11.040> API<00:34:11.580> and<00:34:12.300> you<00:34:12.480> stick<00:34:12.780> the<00:34:13.020> the<00:34:13.320> data 00:34:13.669 --> 00:34:13.679 align:start position:0% same API and you stick the the data 00:34:13.679 --> 00:34:15.230 align:start position:0% same API and you stick the the data availability<00:34:13.980> and<00:34:14.339> the<00:34:14.460> derivation<00:34:14.879> thing 00:34:15.230 --> 00:34:15.240 align:start position:0% availability and the derivation thing 00:34:15.240 --> 00:34:17.450 align:start position:0% availability and the derivation thing and<00:34:15.540> you<00:34:15.720> separate<00:34:16.320> that<00:34:16.500> from<00:34:16.740> execution<00:34:17.159> by 00:34:17.450 --> 00:34:17.460 align:start position:0% and you separate that from execution by 00:34:17.460 --> 00:34:20.329 align:start position:0% and you separate that from execution by that<00:34:17.639> same<00:34:17.820> exact<00:34:18.119> API<00:34:18.599> so<00:34:19.200> it<00:34:19.379> looks<00:34:19.859> exactly 00:34:20.329 --> 00:34:20.339 align:start position:0% that same exact API so it looks exactly 00:34:20.339 --> 00:34:22.909 align:start position:0% that same exact API so it looks exactly like<00:34:20.639> ethereum<00:34:21.300> looks 00:34:22.909 --> 00:34:22.919 align:start position:0% like ethereum looks 00:34:22.919 --> 00:34:25.190 align:start position:0% like ethereum looks um<00:34:23.040> the<00:34:23.460> nice<00:34:23.639> thing<00:34:23.879> about<00:34:24.119> this<00:34:24.419> is<00:34:24.780> that<00:34:24.960> you 00:34:25.190 --> 00:34:25.200 align:start position:0% um the nice thing about this is that you 00:34:25.200 --> 00:34:27.169 align:start position:0% um the nice thing about this is that you can<00:34:25.320> plug<00:34:25.560> in<00:34:25.800> absolutely<00:34:26.339> anything<00:34:26.639> in<00:34:27.000> here 00:34:27.169 --> 00:34:27.179 align:start position:0% can plug in absolutely anything in here 00:34:27.179 --> 00:34:29.389 align:start position:0% can plug in absolutely anything in here you<00:34:27.540> can<00:34:27.659> it<00:34:28.080> doesn't<00:34:28.200> have<00:34:28.440> to<00:34:28.619> be<00:34:28.740> the<00:34:28.919> evm 00:34:29.389 --> 00:34:29.399 align:start position:0% you can it doesn't have to be the evm 00:34:29.399 --> 00:34:31.669 align:start position:0% you can it doesn't have to be the evm you<00:34:30.300> could<00:34:30.359> take<00:34:30.480> the<00:34:30.599> evm<00:34:31.020> and<00:34:31.139> maybe<00:34:31.260> you<00:34:31.560> can 00:34:31.669 --> 00:34:31.679 align:start position:0% you could take the evm and maybe you can 00:34:31.679 --> 00:34:33.230 align:start position:0% you could take the evm and maybe you can make<00:34:31.800> some<00:34:31.980> easy<00:34:32.159> tweaks<00:34:32.639> you<00:34:32.760> can<00:34:32.879> add<00:34:33.000> a<00:34:33.119> new 00:34:33.230 --> 00:34:33.240 align:start position:0% make some easy tweaks you can add a new 00:34:33.240 --> 00:34:36.050 align:start position:0% make some easy tweaks you can add a new pre-compile<00:34:33.839> you<00:34:34.740> can<00:34:34.859> tweak<00:34:35.339> a<00:34:35.520> few<00:34:35.639> op<00:34:35.820> codes 00:34:36.050 --> 00:34:36.060 align:start position:0% pre-compile you can tweak a few op codes 00:34:36.060 --> 00:34:37.609 align:start position:0% pre-compile you can tweak a few op codes if<00:34:36.300> you<00:34:36.480> really<00:34:36.540> want<00:34:36.780> and<00:34:37.020> that'll<00:34:37.320> just<00:34:37.440> work 00:34:37.609 --> 00:34:37.619 align:start position:0% if you really want and that'll just work 00:34:37.619 --> 00:34:40.369 align:start position:0% if you really want and that'll just work really<00:34:37.919> easily<00:34:38.220> in<00:34:38.580> optimism<00:34:39.119> in<00:34:39.780> Bedrock<00:34:40.260> we 00:34:40.369 --> 00:34:40.379 align:start position:0% really easily in optimism in Bedrock we 00:34:40.379 --> 00:34:42.470 align:start position:0% really easily in optimism in Bedrock we add<00:34:40.619> a<00:34:40.800> new<00:34:40.919> transaction<00:34:41.339> type<00:34:41.639> we<00:34:42.119> add<00:34:42.300> this 00:34:42.470 --> 00:34:42.480 align:start position:0% add a new transaction type we add this 00:34:42.480 --> 00:34:44.629 align:start position:0% add a new transaction type we add this deposit<00:34:43.200> transaction<00:34:43.560> type<00:34:43.859> that's<00:34:44.399> really 00:34:44.629 --> 00:34:44.639 align:start position:0% deposit transaction type that's really 00:34:44.639 --> 00:34:46.970 align:start position:0% deposit transaction type that's really easy<00:34:44.879> but<00:34:45.599> it<00:34:45.780> really<00:34:46.020> can<00:34:46.200> be<00:34:46.379> whatever<00:34:46.619> you 00:34:46.970 --> 00:34:46.980 align:start position:0% easy but it really can be whatever you 00:34:46.980 --> 00:34:49.790 align:start position:0% easy but it really can be whatever you want<00:34:47.159> it<00:34:47.639> could<00:34:47.760> be<00:34:48.000> Bitcoin<00:34:48.960> it<00:34:49.379> could<00:34:49.500> be<00:34:49.619> a 00:34:49.790 --> 00:34:49.800 align:start position:0% want it could be Bitcoin it could be a 00:34:49.800 --> 00:34:51.649 align:start position:0% want it could be Bitcoin it could be a Game<00:34:49.980> Boy<00:34:50.220> as<00:34:50.760> long<00:34:50.879> as<00:34:51.000> you<00:34:51.119> have<00:34:51.300> a<00:34:51.480> state 00:34:51.649 --> 00:34:51.659 align:start position:0% Game Boy as long as you have a state 00:34:51.659 --> 00:34:53.329 align:start position:0% Game Boy as long as you have a state transition<00:34:52.080> function<00:34:52.500> and<00:34:52.800> you<00:34:52.980> wrap<00:34:53.220> it 00:34:53.329 --> 00:34:53.339 align:start position:0% transition function and you wrap it 00:34:53.339 --> 00:34:55.010 align:start position:0% transition function and you wrap it inside<00:34:53.580> of<00:34:53.820> the<00:34:53.940> engine<00:34:54.060> API<00:34:54.599> you<00:34:54.780> can<00:34:54.899> do 00:34:55.010 --> 00:34:55.020 align:start position:0% inside of the engine API you can do 00:34:55.020 --> 00:34:56.869 align:start position:0% inside of the engine API you can do whatever<00:34:55.139> you<00:34:55.619> want<00:34:55.740> and<00:34:56.280> it<00:34:56.520> should<00:34:56.639> just 00:34:56.869 --> 00:34:56.879 align:start position:0% whatever you want and it should just 00:34:56.879 --> 00:34:59.030 align:start position:0% whatever you want and it should just work<00:34:57.119> the<00:34:57.420> whole<00:34:57.540> thing<00:34:57.660> should<00:34:57.839> just<00:34:58.020> work<00:34:58.260> so 00:34:59.030 --> 00:34:59.040 align:start position:0% work the whole thing should just work so 00:34:59.040 --> 00:35:00.829 align:start position:0% work the whole thing should just work so if<00:34:59.280> you<00:34:59.400> want<00:34:59.520> to<00:34:59.640> build<00:34:59.760> a<00:34:59.940> game<00:35:00.119> and<00:35:00.660> you<00:35:00.780> want 00:35:00.829 --> 00:35:00.839 align:start position:0% if you want to build a game and you want 00:35:00.839 --> 00:35:02.570 align:start position:0% if you want to build a game and you want to<00:35:00.960> use<00:35:01.080> an<00:35:01.260> evm<00:35:01.740> and<00:35:02.040> you<00:35:02.099> want<00:35:02.220> to<00:35:02.280> add<00:35:02.400> a<00:35:02.520> new 00:35:02.570 --> 00:35:02.580 align:start position:0% to use an evm and you want to add a new 00:35:02.580 --> 00:35:04.730 align:start position:0% to use an evm and you want to add a new pre-compile<00:35:03.240> because<00:35:03.599> you<00:35:04.140> have<00:35:04.320> some 00:35:04.730 --> 00:35:04.740 align:start position:0% pre-compile because you have some 00:35:04.740 --> 00:35:06.349 align:start position:0% pre-compile because you have some complicated<00:35:05.280> game<00:35:05.520> State<00:35:05.760> function<00:35:06.119> that's 00:35:06.349 --> 00:35:06.359 align:start position:0% complicated game State function that's 00:35:06.359 --> 00:35:07.670 align:start position:0% complicated game State function that's just<00:35:06.540> too<00:35:06.780> expensive<00:35:07.200> to<00:35:07.440> run<00:35:07.500> inside 00:35:07.670 --> 00:35:07.680 align:start position:0% just too expensive to run inside 00:35:07.680 --> 00:35:10.849 align:start position:0% just too expensive to run inside solidity<00:35:08.339> then<00:35:09.180> you<00:35:09.960> know<00:35:10.020> just<00:35:10.380> modify<00:35:10.740> the 00:35:10.849 --> 00:35:10.859 align:start position:0% solidity then you know just modify the 00:35:10.859 --> 00:35:12.530 align:start position:0% solidity then you know just modify the evm<00:35:11.280> if<00:35:11.460> you<00:35:11.579> want<00:35:11.700> to<00:35:11.820> run<00:35:11.880> a<00:35:12.180> totally 00:35:12.530 --> 00:35:12.540 align:start position:0% evm if you want to run a totally 00:35:12.540 --> 00:35:14.990 align:start position:0% evm if you want to run a totally different<00:35:13.160> execution<00:35:14.160> client<00:35:14.520> all<00:35:14.760> together 00:35:14.990 --> 00:35:15.000 align:start position:0% different execution client all together 00:35:15.000 --> 00:35:17.750 align:start position:0% different execution client all together you<00:35:15.720> can<00:35:15.780> also<00:35:16.320> do<00:35:16.560> that<00:35:16.859> and<00:35:17.280> it<00:35:17.400> just<00:35:17.520> sits 00:35:17.750 --> 00:35:17.760 align:start position:0% you can also do that and it just sits 00:35:17.760 --> 00:35:19.730 align:start position:0% you can also do that and it just sits behind<00:35:18.000> the<00:35:18.060> same<00:35:18.240> API<00:35:18.720> and<00:35:19.200> all<00:35:19.380> the<00:35:19.500> rest<00:35:19.560> of 00:35:19.730 --> 00:35:19.740 align:start position:0% behind the same API and all the rest of 00:35:19.740 --> 00:35:21.650 align:start position:0% behind the same API and all the rest of the<00:35:19.800> stack<00:35:19.980> all<00:35:20.220> the<00:35:20.339> roll<00:35:20.520> up<00:35:20.700> stuff<00:35:21.000> all<00:35:21.480> the 00:35:21.650 --> 00:35:21.660 align:start position:0% the stack all the roll up stuff all the 00:35:21.660 --> 00:35:23.150 align:start position:0% the stack all the roll up stuff all the transaction<00:35:21.960> stuff<00:35:22.140> it's<00:35:22.320> just<00:35:22.859> keeps 00:35:23.150 --> 00:35:23.160 align:start position:0% transaction stuff it's just keeps 00:35:23.160 --> 00:35:25.010 align:start position:0% transaction stuff it's just keeps working<00:35:23.339> as<00:35:23.940> if<00:35:24.180> you<00:35:24.300> didn't<00:35:24.420> do<00:35:24.599> anything<00:35:24.780> at 00:35:25.010 --> 00:35:25.020 align:start position:0% working as if you didn't do anything at 00:35:25.020 --> 00:35:26.390 align:start position:0% working as if you didn't do anything at all 00:35:26.390 --> 00:35:26.400 align:start position:0% all 00:35:26.400 --> 00:35:28.430 align:start position:0% all right<00:35:27.060> and<00:35:27.480> then<00:35:27.599> finally<00:35:27.960> settlement 00:35:28.430 --> 00:35:28.440 align:start position:0% right and then finally settlement 00:35:28.440 --> 00:35:30.890 align:start position:0% right and then finally settlement settlement<00:35:29.220> is<00:35:29.460> this<00:35:29.760> weird<00:35:29.880> one<00:35:30.180> it's<00:35:30.660> a 00:35:30.890 --> 00:35:30.900 align:start position:0% settlement is this weird one it's a 00:35:30.900 --> 00:35:32.990 align:start position:0% settlement is this weird one it's a little<00:35:31.020> fake<00:35:31.440> it's<00:35:32.040> you<00:35:32.400> know<00:35:32.460> what<00:35:32.700> does<00:35:32.820> this 00:35:32.990 --> 00:35:33.000 align:start position:0% little fake it's you know what does this 00:35:33.000 --> 00:35:34.910 align:start position:0% little fake it's you know what does this really<00:35:33.240> mean<00:35:33.599> I<00:35:34.320> like<00:35:34.440> to<00:35:34.560> say<00:35:34.680> that 00:35:34.910 --> 00:35:34.920 align:start position:0% really mean I like to say that 00:35:34.920 --> 00:35:37.010 align:start position:0% really mean I like to say that settlement<00:35:35.280> is<00:35:35.520> about<00:35:35.700> establishing<00:35:36.420> a<00:35:36.780> view 00:35:37.010 --> 00:35:37.020 align:start position:0% settlement is about establishing a view 00:35:37.020 --> 00:35:40.490 align:start position:0% settlement is about establishing a view of<00:35:37.740> your<00:35:38.040> system<00:35:38.339> on<00:35:39.119> some<00:35:39.359> other<00:35:39.540> system<00:35:39.900> and 00:35:40.490 --> 00:35:40.500 align:start position:0% of your system on some other system and 00:35:40.500 --> 00:35:42.349 align:start position:0% of your system on some other system and it's<00:35:40.619> all<00:35:40.740> about<00:35:40.859> making<00:35:41.220> claims<00:35:41.880> right<00:35:42.119> I'm 00:35:42.349 --> 00:35:42.359 align:start position:0% it's all about making claims right I'm 00:35:42.359 --> 00:35:44.150 align:start position:0% it's all about making claims right I'm making<00:35:42.599> a<00:35:42.900> claim<00:35:43.200> about<00:35:43.380> the<00:35:43.680> state<00:35:43.800> of<00:35:43.980> my 00:35:44.150 --> 00:35:44.160 align:start position:0% making a claim about the state of my 00:35:44.160 --> 00:35:46.790 align:start position:0% making a claim about the state of my system<00:35:44.460> onto<00:35:45.300> another<00:35:45.480> system<00:35:45.839> and<00:35:46.680> so 00:35:46.790 --> 00:35:46.800 align:start position:0% system onto another system and so 00:35:46.800 --> 00:35:49.130 align:start position:0% system onto another system and so settlement<00:35:47.220> is<00:35:47.460> really<00:35:47.640> useful<00:35:48.060> obviously<00:35:48.900> in 00:35:49.130 --> 00:35:49.140 align:start position:0% settlement is really useful obviously in 00:35:49.140 --> 00:35:50.390 align:start position:0% settlement is really useful obviously in the<00:35:49.260> you<00:35:49.380> know<00:35:49.500> in<00:35:49.680> traditional<00:35:50.040> roll-up 00:35:50.390 --> 00:35:50.400 align:start position:0% the you know in traditional roll-up 00:35:50.400 --> 00:35:51.829 align:start position:0% the you know in traditional roll-up settlements<00:35:50.940> is<00:35:51.060> really<00:35:51.240> useful<00:35:51.480> if<00:35:51.599> you<00:35:51.780> want 00:35:51.829 --> 00:35:51.839 align:start position:0% settlements is really useful if you want 00:35:51.839 --> 00:35:53.569 align:start position:0% settlements is really useful if you want to<00:35:51.960> do<00:35:52.020> withdrawals<00:35:52.680> if<00:35:53.099> you<00:35:53.220> want<00:35:53.339> to<00:35:53.460> be<00:35:53.520> able 00:35:53.569 --> 00:35:53.579 align:start position:0% to do withdrawals if you want to be able 00:35:53.579 --> 00:35:55.910 align:start position:0% to do withdrawals if you want to be able to<00:35:53.700> move<00:35:53.880> funds<00:35:54.359> out<00:35:54.900> of<00:35:55.020> your<00:35:55.200> your<00:35:55.440> roll<00:35:55.680> up 00:35:55.910 --> 00:35:55.920 align:start position:0% to move funds out of your your roll up 00:35:55.920 --> 00:35:58.430 align:start position:0% to move funds out of your your roll up onto<00:35:56.640> let's<00:35:56.760> say<00:35:56.940> layer<00:35:57.300> one<00:35:57.480> you<00:35:58.140> need<00:35:58.260> to<00:35:58.320> be 00:35:58.430 --> 00:35:58.440 align:start position:0% onto let's say layer one you need to be 00:35:58.440 --> 00:36:00.410 align:start position:0% onto let's say layer one you need to be able<00:35:58.560> to<00:35:58.740> settle<00:35:59.160> the<00:35:59.400> state<00:35:59.579> of<00:35:59.880> Layer<00:36:00.240> Two 00:36:00.410 --> 00:36:00.420 align:start position:0% able to settle the state of Layer Two 00:36:00.420 --> 00:36:03.109 align:start position:0% able to settle the state of Layer Two onto<00:36:01.079> layer<00:36:01.380> one<00:36:01.500> so<00:36:01.980> that<00:36:02.160> I<00:36:02.280> can<00:36:02.400> say<00:36:02.579> okay 00:36:03.109 --> 00:36:03.119 align:start position:0% onto layer one so that I can say okay 00:36:03.119 --> 00:36:05.510 align:start position:0% onto layer one so that I can say okay that<00:36:03.720> is<00:36:03.900> the<00:36:04.079> true<00:36:04.200> state<00:36:04.440> of<00:36:04.619> Layer<00:36:04.920> Two<00:36:05.099> let 00:36:05.510 --> 00:36:05.520 align:start position:0% that is the true state of Layer Two let 00:36:05.520 --> 00:36:07.609 align:start position:0% that is the true state of Layer Two let me<00:36:05.640> pull<00:36:05.820> it<00:36:06.000> out<00:36:06.180> let<00:36:06.599> me<00:36:06.720> let<00:36:06.900> me<00:36:07.079> operate<00:36:07.440> on 00:36:07.609 --> 00:36:07.619 align:start position:0% me pull it out let me let me operate on 00:36:07.619 --> 00:36:09.230 align:start position:0% me pull it out let me let me operate on it<00:36:07.740> and<00:36:07.920> maybe<00:36:08.099> I'll<00:36:08.339> give<00:36:08.579> you<00:36:08.640> a<00:36:08.760> withdrawal 00:36:09.230 --> 00:36:09.240 align:start position:0% it and maybe I'll give you a withdrawal 00:36:09.240 --> 00:36:10.970 align:start position:0% it and maybe I'll give you a withdrawal as<00:36:09.420> a<00:36:09.540> result 00:36:10.970 --> 00:36:10.980 align:start position:0% as a result 00:36:10.980 --> 00:36:12.530 align:start position:0% as a result but<00:36:11.460> the<00:36:11.579> thing<00:36:11.640> is<00:36:11.760> you<00:36:11.940> can<00:36:12.060> do<00:36:12.180> a<00:36:12.359> lot<00:36:12.480> of 00:36:12.530 --> 00:36:12.540 align:start position:0% but the thing is you can do a lot of 00:36:12.540 --> 00:36:13.430 align:start position:0% but the thing is you can do a lot of really<00:36:12.720> interesting<00:36:13.079> things<00:36:13.260> with 00:36:13.430 --> 00:36:13.440 align:start position:0% really interesting things with 00:36:13.440 --> 00:36:15.349 align:start position:0% really interesting things with settlement<00:36:13.800> you<00:36:14.160> don't<00:36:14.400> just<00:36:14.760> have<00:36:15.000> to<00:36:15.119> make 00:36:15.349 --> 00:36:15.359 align:start position:0% settlement you don't just have to make 00:36:15.359 --> 00:36:17.210 align:start position:0% settlement you don't just have to make claims<00:36:15.780> about<00:36:15.960> let's<00:36:16.380> say<00:36:16.500> the<00:36:16.740> total<00:36:17.040> state 00:36:17.210 --> 00:36:17.220 align:start position:0% claims about let's say the total state 00:36:17.220 --> 00:36:18.890 align:start position:0% claims about let's say the total state of<00:36:17.400> the<00:36:17.579> system<00:36:17.760> I<00:36:18.359> think<00:36:18.480> a<00:36:18.720> really 00:36:18.890 --> 00:36:18.900 align:start position:0% of the system I think a really 00:36:18.900 --> 00:36:19.970 align:start position:0% of the system I think a really interesting<00:36:19.260> way<00:36:19.560> to<00:36:19.740> think<00:36:19.859> about 00:36:19.970 --> 00:36:19.980 align:start position:0% interesting way to think about 00:36:19.980 --> 00:36:22.010 align:start position:0% interesting way to think about settlement<00:36:20.400> for<00:36:20.579> gaming<00:36:20.940> is<00:36:21.420> that<00:36:21.599> you<00:36:21.839> can 00:36:22.010 --> 00:36:22.020 align:start position:0% settlement for gaming is that you can 00:36:22.020 --> 00:36:25.550 align:start position:0% settlement for gaming is that you can have<00:36:22.440> a<00:36:23.040> short-lived<00:36:23.940> chain<00:36:24.359> that<00:36:25.140> plays<00:36:25.440> some 00:36:25.550 --> 00:36:25.560 align:start position:0% have a short-lived chain that plays some 00:36:25.560 --> 00:36:26.930 align:start position:0% have a short-lived chain that plays some game<00:36:25.740> let's<00:36:25.920> say<00:36:26.040> we<00:36:26.220> all<00:36:26.339> want<00:36:26.520> to<00:36:26.640> play<00:36:26.700> a 00:36:26.930 --> 00:36:26.940 align:start position:0% game let's say we all want to play a 00:36:26.940 --> 00:36:28.849 align:start position:0% game let's say we all want to play a chess<00:36:27.119> tournament<00:36:27.480> right<00:36:27.839> we<00:36:28.320> can<00:36:28.440> play<00:36:28.619> a 00:36:28.849 --> 00:36:28.859 align:start position:0% chess tournament right we can play a 00:36:28.859 --> 00:36:30.890 align:start position:0% chess tournament right we can play a short-lived<00:36:29.339> game<00:36:29.520> and<00:36:30.240> then<00:36:30.359> at<00:36:30.540> the<00:36:30.660> end<00:36:30.780> of 00:36:30.890 --> 00:36:30.900 align:start position:0% short-lived game and then at the end of 00:36:30.900 --> 00:36:32.930 align:start position:0% short-lived game and then at the end of the<00:36:31.020> game<00:36:31.200> we<00:36:31.800> can<00:36:31.920> all<00:36:32.099> you<00:36:32.400> know<00:36:32.460> we<00:36:32.579> see<00:36:32.760> who 00:36:32.930 --> 00:36:32.940 align:start position:0% the game we can all you know we see who 00:36:32.940 --> 00:36:34.670 align:start position:0% the game we can all you know we see who wins<00:36:33.240> the<00:36:33.359> whole<00:36:33.540> tournament<00:36:33.900> and<00:36:34.440> we<00:36:34.560> can 00:36:34.670 --> 00:36:34.680 align:start position:0% wins the whole tournament and we can 00:36:34.680 --> 00:36:36.349 align:start position:0% wins the whole tournament and we can make<00:36:34.859> a<00:36:35.040> claim<00:36:35.280> and<00:36:35.460> we<00:36:35.579> can<00:36:35.700> say<00:36:35.880> you<00:36:36.240> know 00:36:36.349 --> 00:36:36.359 align:start position:0% make a claim and we can say you know 00:36:36.359 --> 00:36:38.870 align:start position:0% make a claim and we can say you know Kelvin<00:36:36.780> won<00:36:37.079> the<00:36:37.320> whole<00:36:37.500> tournament<00:36:38.400> and 00:36:38.870 --> 00:36:38.880 align:start position:0% Kelvin won the whole tournament and 00:36:38.880 --> 00:36:40.250 align:start position:0% Kelvin won the whole tournament and that's<00:36:39.000> one<00:36:39.180> that's<00:36:39.480> the<00:36:39.660> claim<00:36:39.960> that<00:36:40.079> I'm 00:36:40.250 --> 00:36:40.260 align:start position:0% that's one that's the claim that I'm 00:36:40.260 --> 00:36:41.690 align:start position:0% that's one that's the claim that I'm settling<00:36:40.619> and<00:36:41.040> then<00:36:41.099> you<00:36:41.220> can<00:36:41.339> have<00:36:41.460> this 00:36:41.690 --> 00:36:41.700 align:start position:0% settling and then you can have this 00:36:41.700 --> 00:36:43.670 align:start position:0% settling and then you can have this generic<00:36:42.060> proof<00:36:42.420> system<00:36:42.660> that<00:36:43.320> will<00:36:43.500> just 00:36:43.670 --> 00:36:43.680 align:start position:0% generic proof system that will just 00:36:43.680 --> 00:36:46.250 align:start position:0% generic proof system that will just prove<00:36:44.220> arbitrary<00:36:44.880> claims<00:36:45.480> about<00:36:45.900> the<00:36:46.140> state 00:36:46.250 --> 00:36:46.260 align:start position:0% prove arbitrary claims about the state 00:36:46.260 --> 00:36:48.109 align:start position:0% prove arbitrary claims about the state of<00:36:46.440> your<00:36:46.560> layer<00:36:46.859> too<00:36:46.980> and<00:36:47.460> so<00:36:47.579> you<00:36:47.700> can<00:36:47.760> prove 00:36:48.109 --> 00:36:48.119 align:start position:0% of your layer too and so you can prove 00:36:48.119 --> 00:36:50.210 align:start position:0% of your layer too and so you can prove this<00:36:48.300> idea<00:36:48.540> that<00:36:48.720> okay<00:36:48.900> Kelvin<00:36:49.380> won<00:36:49.619> and<00:36:50.099> then 00:36:50.210 --> 00:36:50.220 align:start position:0% this idea that okay Kelvin won and then 00:36:50.220 --> 00:36:52.010 align:start position:0% this idea that okay Kelvin won and then we<00:36:50.400> can<00:36:50.520> resolve<00:36:50.940> that<00:36:51.119> winner<00:36:51.359> back<00:36:51.599> to<00:36:51.720> layer 00:36:52.010 --> 00:36:52.020 align:start position:0% we can resolve that winner back to layer 00:36:52.020 --> 00:36:54.530 align:start position:0% we can resolve that winner back to layer one<00:36:52.140> and<00:36:52.320> we<00:36:52.440> can<00:36:52.560> pay<00:36:52.920> that<00:36:53.280> person<00:36:53.460> out<00:36:53.760> and 00:36:54.530 --> 00:36:54.540 align:start position:0% one and we can pay that person out and 00:36:54.540 --> 00:36:55.849 align:start position:0% one and we can pay that person out and then<00:36:54.599> we<00:36:54.780> can<00:36:54.900> throw<00:36:55.079> the<00:36:55.260> chain<00:36:55.380> away<00:36:55.619> because 00:36:55.849 --> 00:36:55.859 align:start position:0% then we can throw the chain away because 00:36:55.859 --> 00:36:57.950 align:start position:0% then we can throw the chain away because we<00:36:56.040> don't<00:36:56.099> need<00:36:56.280> it<00:36:56.400> anymore<00:36:56.579> so<00:36:57.359> we<00:36:57.540> got<00:36:57.660> this 00:36:57.950 --> 00:36:57.960 align:start position:0% we don't need it anymore so we got this 00:36:57.960 --> 00:37:00.530 align:start position:0% we don't need it anymore so we got this short-lived<00:36:58.680> verifiable<00:36:59.579> system<00:37:00.000> right<00:37:00.359> this 00:37:00.530 --> 00:37:00.540 align:start position:0% short-lived verifiable system right this 00:37:00.540 --> 00:37:02.630 align:start position:0% short-lived verifiable system right this game<00:37:00.839> that<00:37:01.140> we<00:37:01.619> know<00:37:01.740> that<00:37:02.040> the<00:37:02.220> whole<00:37:02.339> thing 00:37:02.630 --> 00:37:02.640 align:start position:0% game that we know that the whole thing 00:37:02.640 --> 00:37:05.150 align:start position:0% game that we know that the whole thing ran<00:37:03.359> as<00:37:03.540> it<00:37:03.720> should<00:37:03.839> have<00:37:03.960> ran<00:37:04.260> there's<00:37:04.859> no 00:37:05.150 --> 00:37:05.160 align:start position:0% ran as it should have ran there's no 00:37:05.160 --> 00:37:07.250 align:start position:0% ran as it should have ran there's no weird<00:37:05.400> State<00:37:05.640> coming<00:37:05.940> out<00:37:06.180> of<00:37:06.300> it<00:37:06.420> we<00:37:06.900> prove 00:37:07.250 --> 00:37:07.260 align:start position:0% weird State coming out of it we prove 00:37:07.260 --> 00:37:09.230 align:start position:0% weird State coming out of it we prove that<00:37:07.380> back<00:37:07.619> to<00:37:07.800> the<00:37:07.920> base<00:37:08.099> layer<00:37:08.520> and<00:37:08.940> then<00:37:09.060> we 00:37:09.230 --> 00:37:09.240 align:start position:0% that back to the base layer and then we 00:37:09.240 --> 00:37:11.030 align:start position:0% that back to the base layer and then we can<00:37:09.359> throw<00:37:09.540> the<00:37:09.780> whole<00:37:09.900> chain<00:37:10.079> away<00:37:10.320> and<00:37:10.920> we 00:37:11.030 --> 00:37:11.040 align:start position:0% can throw the whole chain away and we 00:37:11.040 --> 00:37:12.890 align:start position:0% can throw the whole chain away and we don't<00:37:11.160> have<00:37:11.339> to<00:37:11.460> worry<00:37:11.640> about<00:37:11.760> storing<00:37:12.359> it<00:37:12.540> and 00:37:12.890 --> 00:37:12.900 align:start position:0% don't have to worry about storing it and 00:37:12.900 --> 00:37:14.870 align:start position:0% don't have to worry about storing it and so<00:37:13.020> for<00:37:13.260> short-lived<00:37:13.920> you<00:37:14.339> know<00:37:14.400> high 00:37:14.870 --> 00:37:14.880 align:start position:0% so for short-lived you know high 00:37:14.880 --> 00:37:16.970 align:start position:0% so for short-lived you know high capacity<00:37:15.480> games<00:37:15.720> you<00:37:16.079> can<00:37:16.200> really<00:37:16.440> bump<00:37:16.800> up 00:37:16.970 --> 00:37:16.980 align:start position:0% capacity games you can really bump up 00:37:16.980 --> 00:37:18.589 align:start position:0% capacity games you can really bump up the<00:37:17.220> gas<00:37:17.400> limit<00:37:17.579> you<00:37:17.880> can<00:37:18.000> do<00:37:18.119> crazy<00:37:18.300> stuff 00:37:18.589 --> 00:37:18.599 align:start position:0% the gas limit you can do crazy stuff 00:37:18.599 --> 00:37:20.569 align:start position:0% the gas limit you can do crazy stuff because<00:37:18.780> you're<00:37:19.020> not<00:37:19.200> worried<00:37:19.680> about<00:37:20.220> State 00:37:20.569 --> 00:37:20.579 align:start position:0% because you're not worried about State 00:37:20.579 --> 00:37:23.150 align:start position:0% because you're not worried about State bloating<00:37:21.060> to<00:37:21.359> infinity<00:37:21.740> and<00:37:22.740> then<00:37:22.920> you<00:37:23.040> can 00:37:23.150 --> 00:37:23.160 align:start position:0% bloating to infinity and then you can 00:37:23.160 --> 00:37:24.470 align:start position:0% bloating to infinity and then you can just<00:37:23.280> settle<00:37:23.640> any<00:37:23.940> sort<00:37:24.180> of<00:37:24.300> information 00:37:24.470 --> 00:37:24.480 align:start position:0% just settle any sort of information 00:37:24.480 --> 00:37:26.630 align:start position:0% just settle any sort of information about<00:37:25.079> the<00:37:25.380> state<00:37:25.500> of<00:37:25.680> your<00:37:25.740> Layer<00:37:26.040> Two<00:37:26.160> back 00:37:26.630 --> 00:37:26.640 align:start position:0% about the state of your Layer Two back 00:37:26.640 --> 00:37:28.310 align:start position:0% about the state of your Layer Two back to<00:37:26.820> layer<00:37:27.119> one 00:37:28.310 --> 00:37:28.320 align:start position:0% to layer one 00:37:28.320 --> 00:37:30.290 align:start position:0% to layer one all<00:37:28.800> right<00:37:28.980> no<00:37:29.280> sequencer<00:37:29.760> no<00:37:30.060> problem 00:37:30.290 --> 00:37:30.300 align:start position:0% all right no sequencer no problem 00:37:30.300 --> 00:37:31.849 align:start position:0% all right no sequencer no problem actually<00:37:30.660> currently<00:37:31.020> a<00:37:31.260> very<00:37:31.440> big<00:37:31.619> problem 00:37:31.849 --> 00:37:31.859 align:start position:0% actually currently a very big problem 00:37:31.859 --> 00:37:34.849 align:start position:0% actually currently a very big problem but<00:37:32.280> this<00:37:32.520> is<00:37:32.700> just<00:37:32.940> an<00:37:33.119> idea<00:37:33.480> of<00:37:34.260> basically 00:37:34.849 --> 00:37:34.859 align:start position:0% but this is just an idea of basically 00:37:34.859 --> 00:37:36.829 align:start position:0% but this is just an idea of basically what<00:37:35.220> where<00:37:35.400> we<00:37:35.640> imagine<00:37:35.820> this<00:37:36.240> system<00:37:36.420> going 00:37:36.829 --> 00:37:36.839 align:start position:0% what where we imagine this system going 00:37:36.839 --> 00:37:39.530 align:start position:0% what where we imagine this system going in<00:37:37.440> the<00:37:37.619> future<00:37:37.800> because<00:37:38.579> there's<00:37:39.240> a<00:37:39.480> big 00:37:39.530 --> 00:37:39.540 align:start position:0% in the future because there's a big 00:37:39.540 --> 00:37:42.230 align:start position:0% in the future because there's a big issue<00:37:39.900> which<00:37:40.079> is<00:37:40.200> that<00:37:40.440> every<00:37:40.680> single<00:37:41.040> time<00:37:41.400> I 00:37:42.230 --> 00:37:42.240 align:start position:0% issue which is that every single time I 00:37:42.240 --> 00:37:44.450 align:start position:0% issue which is that every single time I talk<00:37:42.420> about<00:37:42.599> this<00:37:42.960> idea<00:37:43.320> somebody<00:37:43.980> comes<00:37:44.400> up 00:37:44.450 --> 00:37:44.460 align:start position:0% talk about this idea somebody comes up 00:37:44.460 --> 00:37:45.890 align:start position:0% talk about this idea somebody comes up to<00:37:44.640> me<00:37:44.760> and<00:37:44.820> they<00:37:44.940> ask<00:37:45.119> me<00:37:45.240> doesn't<00:37:45.480> that<00:37:45.720> mean 00:37:45.890 --> 00:37:45.900 align:start position:0% to me and they ask me doesn't that mean 00:37:45.900 --> 00:37:47.150 align:start position:0% to me and they ask me doesn't that mean you<00:37:46.140> still<00:37:46.260> have<00:37:46.440> to<00:37:46.500> run<00:37:46.680> all<00:37:46.980> this 00:37:47.150 --> 00:37:47.160 align:start position:0% you still have to run all this 00:37:47.160 --> 00:37:49.069 align:start position:0% you still have to run all this sequencing<00:37:47.700> infrastructure<00:37:48.359> and<00:37:48.960> the 00:37:49.069 --> 00:37:49.079 align:start position:0% sequencing infrastructure and the 00:37:49.079 --> 00:37:51.710 align:start position:0% sequencing infrastructure and the reality<00:37:49.380> right<00:37:49.680> now<00:37:49.859> is<00:37:50.040> yes<00:37:50.400> but<00:37:51.240> we<00:37:51.480> want<00:37:51.599> to 00:37:51.710 --> 00:37:51.720 align:start position:0% reality right now is yes but we want to 00:37:51.720 --> 00:37:53.270 align:start position:0% reality right now is yes but we want to get<00:37:51.780> to<00:37:51.960> a<00:37:52.079> future<00:37:52.200> where<00:37:52.500> the<00:37:52.740> answer<00:37:52.920> is<00:37:53.099> no 00:37:53.270 --> 00:37:53.280 align:start position:0% get to a future where the answer is no 00:37:53.280 --> 00:37:55.670 align:start position:0% get to a future where the answer is no right<00:37:53.579> because<00:37:53.760> most<00:37:54.240> people<00:37:54.540> don't<00:37:55.380> really 00:37:55.670 --> 00:37:55.680 align:start position:0% right because most people don't really 00:37:55.680 --> 00:37:57.470 align:start position:0% right because most people don't really want<00:37:55.920> to<00:37:56.040> run<00:37:56.160> this<00:37:56.400> infrastructure<00:37:56.940> you<00:37:57.359> want 00:37:57.470 --> 00:37:57.480 align:start position:0% want to run this infrastructure you want 00:37:57.480 --> 00:37:59.450 align:start position:0% want to run this infrastructure you want to<00:37:57.599> focus<00:37:57.839> on<00:37:58.140> building<00:37:58.380> a<00:37:58.619> game<00:37:58.800> especially 00:37:59.450 --> 00:37:59.460 align:start position:0% to focus on building a game especially 00:37:59.460 --> 00:38:00.290 align:start position:0% to focus on building a game especially let's<00:37:59.579> say<00:37:59.760> you<00:37:59.880> just<00:37:59.940> want<00:38:00.060> to<00:38:00.180> build 00:38:00.290 --> 00:38:00.300 align:start position:0% let's say you just want to build 00:38:00.300 --> 00:38:01.670 align:start position:0% let's say you just want to build something<00:38:00.480> small<00:38:00.780> you<00:38:01.020> want<00:38:01.140> to<00:38:01.260> run<00:38:01.320> it<00:38:01.500> for 00:38:01.670 --> 00:38:01.680 align:start position:0% something small you want to run it for 00:38:01.680 --> 00:38:03.770 align:start position:0% something small you want to run it for for<00:38:02.040> a<00:38:02.339> couple<00:38:02.460> of<00:38:02.579> days<00:38:02.820> you<00:38:03.300> want<00:38:03.420> to<00:38:03.540> put<00:38:03.660> it 00:38:03.770 --> 00:38:03.780 align:start position:0% for a couple of days you want to put it 00:38:03.780 --> 00:38:06.770 align:start position:0% for a couple of days you want to put it up<00:38:03.900> there<00:38:04.140> the<00:38:04.740> reality<00:38:05.099> is<00:38:05.339> if<00:38:06.119> you<00:38:06.240> if<00:38:06.540> you're 00:38:06.770 --> 00:38:06.780 align:start position:0% up there the reality is if you if you're 00:38:06.780 --> 00:38:08.270 align:start position:0% up there the reality is if you if you're you<00:38:07.020> know<00:38:07.140> I'm<00:38:07.619> sure<00:38:07.800> that<00:38:07.980> the<00:38:08.160> average 00:38:08.270 --> 00:38:08.280 align:start position:0% you know I'm sure that the average 00:38:08.280 --> 00:38:09.890 align:start position:0% you know I'm sure that the average person<00:38:08.579> does<00:38:08.940> not<00:38:09.060> want<00:38:09.180> to<00:38:09.300> deal<00:38:09.480> with<00:38:09.720> the 00:38:09.890 --> 00:38:09.900 align:start position:0% person does not want to deal with the 00:38:09.900 --> 00:38:11.329 align:start position:0% person does not want to deal with the level<00:38:10.079> of<00:38:10.320> stuff<00:38:10.560> that<00:38:10.800> we<00:38:10.920> have<00:38:10.980> to<00:38:11.099> deal<00:38:11.220> with 00:38:11.329 --> 00:38:11.339 align:start position:0% level of stuff that we have to deal with 00:38:11.339 --> 00:38:12.829 align:start position:0% level of stuff that we have to deal with at<00:38:11.520> optimism<00:38:11.940> to<00:38:12.180> keep<00:38:12.300> the<00:38:12.420> sequencer 00:38:12.829 --> 00:38:12.839 align:start position:0% at optimism to keep the sequencer 00:38:12.839 --> 00:38:13.609 align:start position:0% at optimism to keep the sequencer running 00:38:13.609 --> 00:38:13.619 align:start position:0% running 00:38:13.619 --> 00:38:15.230 align:start position:0% running so<00:38:14.099> we<00:38:14.280> have<00:38:14.400> this<00:38:14.640> concept<00:38:14.940> that<00:38:15.119> we're 00:38:15.230 --> 00:38:15.240 align:start position:0% so we have this concept that we're 00:38:15.240 --> 00:38:18.170 align:start position:0% so we have this concept that we're exploring<00:38:15.480> called<00:38:15.720> shared<00:38:16.079> sequencing 00:38:18.170 --> 00:38:18.180 align:start position:0% exploring called shared sequencing 00:38:18.180 --> 00:38:20.270 align:start position:0% exploring called shared sequencing um<00:38:18.300> basically<00:38:18.960> shared<00:38:19.320> sequencing<00:38:19.740> is<00:38:19.980> taking 00:38:20.270 --> 00:38:20.280 align:start position:0% um basically shared sequencing is taking 00:38:20.280 --> 00:38:21.470 align:start position:0% um basically shared sequencing is taking all<00:38:20.460> the<00:38:20.579> headache<00:38:20.880> of<00:38:21.000> running<00:38:21.180> your<00:38:21.359> own 00:38:21.470 --> 00:38:21.480 align:start position:0% all the headache of running your own 00:38:21.480 --> 00:38:24.190 align:start position:0% all the headache of running your own sequencer<00:38:22.020> and<00:38:22.500> it's<00:38:22.619> deleting<00:38:23.040> all<00:38:23.280> of<00:38:23.339> that 00:38:24.190 --> 00:38:24.200 align:start position:0% sequencer and it's deleting all of that 00:38:24.200 --> 00:38:26.990 align:start position:0% sequencer and it's deleting all of that and<00:38:25.200> the<00:38:25.320> basic<00:38:25.619> idea<00:38:25.920> is<00:38:26.220> that<00:38:26.400> all<00:38:26.640> of<00:38:26.760> these 00:38:26.990 --> 00:38:27.000 align:start position:0% and the basic idea is that all of these 00:38:27.000 --> 00:38:29.390 align:start position:0% and the basic idea is that all of these different<00:38:27.180> autonomous<00:38:27.780> worlds<00:38:28.260> can<00:38:28.800> share<00:38:29.099> a 00:38:29.390 --> 00:38:29.400 align:start position:0% different autonomous worlds can share a 00:38:29.400 --> 00:38:30.710 align:start position:0% different autonomous worlds can share a single<00:38:29.640> sequencer 00:38:30.710 --> 00:38:30.720 align:start position:0% single sequencer 00:38:30.720 --> 00:38:32.569 align:start position:0% single sequencer and<00:38:31.079> of<00:38:31.260> course<00:38:31.380> when<00:38:31.560> I<00:38:31.680> talk<00:38:31.800> about<00:38:31.920> a<00:38:32.220> single 00:38:32.569 --> 00:38:32.579 align:start position:0% and of course when I talk about a single 00:38:32.579 --> 00:38:33.770 align:start position:0% and of course when I talk about a single sequencer<00:38:32.940> you<00:38:33.119> can<00:38:33.180> see<00:38:33.300> there's<00:38:33.420> multiple 00:38:33.770 --> 00:38:33.780 align:start position:0% sequencer you can see there's multiple 00:38:33.780 --> 00:38:35.630 align:start position:0% sequencer you can see there's multiple machines<00:38:34.200> there<00:38:34.500> I<00:38:34.920> like<00:38:35.099> to<00:38:35.280> think<00:38:35.339> about<00:38:35.520> the 00:38:35.630 --> 00:38:35.640 align:start position:0% machines there I like to think about the 00:38:35.640 --> 00:38:37.130 align:start position:0% machines there I like to think about the sequencer<00:38:36.060> as<00:38:36.240> sort<00:38:36.359> of<00:38:36.420> a<00:38:36.540> single<00:38:36.839> logical 00:38:37.130 --> 00:38:37.140 align:start position:0% sequencer as sort of a single logical 00:38:37.140 --> 00:38:39.710 align:start position:0% sequencer as sort of a single logical entity<00:38:37.500> but<00:38:38.220> in<00:38:38.400> the<00:38:38.520> future<00:38:38.640> what's<00:38:39.420> going<00:38:39.599> to 00:38:39.710 --> 00:38:39.720 align:start position:0% entity but in the future what's going to 00:38:39.720 --> 00:38:40.370 align:start position:0% entity but in the future what's going to happen<00:38:39.780> is<00:38:40.020> you're<00:38:40.140> going<00:38:40.260> to<00:38:40.320> get 00:38:40.370 --> 00:38:40.380 align:start position:0% happen is you're going to get 00:38:40.380 --> 00:38:41.930 align:start position:0% happen is you're going to get decentralized<00:38:41.099> sequencing<00:38:41.520> you're<00:38:41.760> going<00:38:41.880> to 00:38:41.930 --> 00:38:41.940 align:start position:0% decentralized sequencing you're going to 00:38:41.940 --> 00:38:43.130 align:start position:0% decentralized sequencing you're going to have<00:38:42.060> something<00:38:42.180> that<00:38:42.359> looks<00:38:42.599> like<00:38:42.660> a<00:38:42.839> leader 00:38:43.130 --> 00:38:43.140 align:start position:0% have something that looks like a leader 00:38:43.140 --> 00:38:45.530 align:start position:0% have something that looks like a leader election<00:38:43.380> where<00:38:44.220> at<00:38:44.400> any<00:38:44.520> given<00:38:44.880> time<00:38:45.119> slot 00:38:45.530 --> 00:38:45.540 align:start position:0% election where at any given time slot 00:38:45.540 --> 00:38:47.630 align:start position:0% election where at any given time slot there's<00:38:45.720> a<00:38:45.960> specific<00:38:46.260> sequencer<00:38:46.980> and<00:38:47.460> that 00:38:47.630 --> 00:38:47.640 align:start position:0% there's a specific sequencer and that 00:38:47.640 --> 00:38:49.849 align:start position:0% there's a specific sequencer and that sequencer<00:38:48.060> sequencing<00:38:48.599> Your<00:38:48.780> Role<00:38:49.020> up<00:38:49.200> and 00:38:49.849 --> 00:38:49.859 align:start position:0% sequencer sequencing Your Role up and 00:38:49.859 --> 00:38:51.349 align:start position:0% sequencer sequencing Your Role up and then<00:38:49.980> there's<00:38:50.220> the<00:38:50.400> next<00:38:50.520> time<00:38:50.700> slot<00:38:51.060> and<00:38:51.180> the 00:38:51.349 --> 00:38:51.359 align:start position:0% then there's the next time slot and the 00:38:51.359 --> 00:38:54.589 align:start position:0% then there's the next time slot and the next<00:38:51.480> sequencer<00:38:51.960> comes<00:38:52.260> in<00:38:52.320> right<00:38:53.099> so<00:38:53.940> the<00:38:54.540> the 00:38:54.589 --> 00:38:54.599 align:start position:0% next sequencer comes in right so the the 00:38:54.599 --> 00:38:55.970 align:start position:0% next sequencer comes in right so the the thing<00:38:54.960> with<00:38:55.200> this<00:38:55.320> is<00:38:55.560> you<00:38:55.680> could<00:38:55.859> do 00:38:55.970 --> 00:38:55.980 align:start position:0% thing with this is you could do 00:38:55.980 --> 00:38:57.710 align:start position:0% thing with this is you could do something<00:38:56.220> really<00:38:56.579> really<00:38:56.700> interesting<00:38:57.180> if 00:38:57.710 --> 00:38:57.720 align:start position:0% something really really interesting if 00:38:57.720 --> 00:39:00.589 align:start position:0% something really really interesting if you<00:38:57.839> have<00:38:58.020> one<00:38:58.440> sequencer<00:38:59.460> sequencing<00:39:00.180> all<00:39:00.480> of 00:39:00.589 --> 00:39:00.599 align:start position:0% you have one sequencer sequencing all of 00:39:00.599 --> 00:39:01.970 align:start position:0% you have one sequencer sequencing all of these<00:39:00.780> different<00:39:00.900> chains<00:39:01.320> at<00:39:01.440> the<00:39:01.619> same<00:39:01.740> time 00:39:01.970 --> 00:39:01.980 align:start position:0% these different chains at the same time 00:39:01.980 --> 00:39:03.829 align:start position:0% these different chains at the same time right<00:39:02.700> instead<00:39:03.119> of<00:39:03.240> having<00:39:03.420> multiple 00:39:03.829 --> 00:39:03.839 align:start position:0% right instead of having multiple 00:39:03.839 --> 00:39:05.089 align:start position:0% right instead of having multiple different<00:39:04.079> chains<00:39:04.500> that<00:39:04.619> are<00:39:04.740> talking<00:39:04.859> to 00:39:05.089 --> 00:39:05.099 align:start position:0% different chains that are talking to 00:39:05.099 --> 00:39:06.890 align:start position:0% different chains that are talking to each<00:39:05.280> other<00:39:05.400> the<00:39:05.880> problem<00:39:06.000> today<00:39:06.300> is<00:39:06.540> if<00:39:06.720> I 00:39:06.890 --> 00:39:06.900 align:start position:0% each other the problem today is if I 00:39:06.900 --> 00:39:09.230 align:start position:0% each other the problem today is if I have<00:39:07.020> let's<00:39:07.500> say<00:39:07.619> I'm<00:39:07.800> ethereum<00:39:08.280> and<00:39:08.940> I<00:39:09.119> have 00:39:09.230 --> 00:39:09.240 align:start position:0% have let's say I'm ethereum and I have 00:39:09.240 --> 00:39:11.569 align:start position:0% have let's say I'm ethereum and I have Cosmos<00:39:09.839> right<00:39:10.020> now<00:39:10.079> I<00:39:10.320> want<00:39:10.800> to<00:39:10.920> sort<00:39:11.099> of<00:39:11.160> I 00:39:11.569 --> 00:39:11.579 align:start position:0% Cosmos right now I want to sort of I 00:39:11.579 --> 00:39:13.130 align:start position:0% Cosmos right now I want to sort of I want<00:39:11.700> to<00:39:11.820> interact<00:39:12.119> between<00:39:12.300> a<00:39:12.599> cosmos<00:39:12.960> chain 00:39:13.130 --> 00:39:13.140 align:start position:0% want to interact between a cosmos chain 00:39:13.140 --> 00:39:15.770 align:start position:0% want to interact between a cosmos chain from<00:39:13.440> a<00:39:13.560> from<00:39:13.980> ethereum<00:39:14.460> they<00:39:15.180> don't<00:39:15.300> share<00:39:15.599> a 00:39:15.770 --> 00:39:15.780 align:start position:0% from a from ethereum they don't share a 00:39:15.780 --> 00:39:17.390 align:start position:0% from a from ethereum they don't share a validator<00:39:16.200> set 00:39:17.390 --> 00:39:17.400 align:start position:0% validator set 00:39:17.400 --> 00:39:19.010 align:start position:0% validator set which<00:39:17.820> means<00:39:18.060> that<00:39:18.240> my<00:39:18.540> communication 00:39:19.010 --> 00:39:19.020 align:start position:0% which means that my communication 00:39:19.020 --> 00:39:22.310 align:start position:0% which means that my communication inherently<00:39:19.740> has<00:39:20.099> to<00:39:20.220> be<00:39:20.540> asynchronous<00:39:21.540> but<00:39:22.200> if 00:39:22.310 --> 00:39:22.320 align:start position:0% inherently has to be asynchronous but if 00:39:22.320 --> 00:39:24.470 align:start position:0% inherently has to be asynchronous but if you<00:39:22.440> have<00:39:22.560> a<00:39:22.800> single<00:39:23.099> sequencer<00:39:23.640> producing 00:39:24.470 --> 00:39:24.480 align:start position:0% you have a single sequencer producing 00:39:24.480 --> 00:39:26.569 align:start position:0% you have a single sequencer producing the<00:39:24.599> blocks<00:39:25.020> on<00:39:25.320> many<00:39:25.680> different<00:39:25.980> autonomous 00:39:26.569 --> 00:39:26.579 align:start position:0% the blocks on many different autonomous 00:39:26.579 --> 00:39:28.550 align:start position:0% the blocks on many different autonomous changes<00:39:26.940> the<00:39:27.060> autonomous<00:39:27.540> autonomous<00:39:28.140> Worlds 00:39:28.550 --> 00:39:28.560 align:start position:0% changes the autonomous autonomous Worlds 00:39:28.560 --> 00:39:30.470 align:start position:0% changes the autonomous autonomous Worlds at<00:39:28.680> the<00:39:28.800> same<00:39:28.980> time<00:39:29.220> you<00:39:30.060> can<00:39:30.119> get<00:39:30.300> this 00:39:30.470 --> 00:39:30.480 align:start position:0% at the same time you can get this 00:39:30.480 --> 00:39:33.290 align:start position:0% at the same time you can get this amazing<00:39:30.839> property<00:39:31.320> of<00:39:32.099> atomic<00:39:32.760> composability 00:39:33.290 --> 00:39:33.300 align:start position:0% amazing property of atomic composability 00:39:33.300 --> 00:39:35.329 align:start position:0% amazing property of atomic composability between<00:39:33.660> all<00:39:33.960> these<00:39:34.140> different<00:39:34.260> chains<00:39:34.740> you 00:39:35.329 --> 00:39:35.339 align:start position:0% between all these different chains you 00:39:35.339 --> 00:39:36.890 align:start position:0% between all these different chains you basically<00:39:35.640> have<00:39:35.760> a<00:39:35.940> single<00:39:36.180> sequencer<00:39:36.599> saying 00:39:36.890 --> 00:39:36.900 align:start position:0% basically have a single sequencer saying 00:39:36.900 --> 00:39:38.510 align:start position:0% basically have a single sequencer saying okay<00:39:37.079> there's<00:39:37.380> a<00:39:37.560> transaction<00:39:37.859> coming<00:39:38.160> in<00:39:38.339> on 00:39:38.510 --> 00:39:38.520 align:start position:0% okay there's a transaction coming in on 00:39:38.520 --> 00:39:40.430 align:start position:0% okay there's a transaction coming in on chain<00:39:38.700> a<00:39:39.119> and<00:39:39.599> there's<00:39:39.720> a<00:39:39.900> transaction<00:39:40.140> coming 00:39:40.430 --> 00:39:40.440 align:start position:0% chain a and there's a transaction coming 00:39:40.440 --> 00:39:42.410 align:start position:0% chain a and there's a transaction coming in<00:39:40.619> on<00:39:40.740> chain<00:39:40.920> B<00:39:41.220> and<00:39:41.820> I'm<00:39:42.000> supposed<00:39:42.240> to 00:39:42.410 --> 00:39:42.420 align:start position:0% in on chain B and I'm supposed to 00:39:42.420 --> 00:39:43.550 align:start position:0% in on chain B and I'm supposed to guarantee<00:39:42.780> that<00:39:42.960> they<00:39:43.079> can<00:39:43.260> come<00:39:43.440> in 00:39:43.550 --> 00:39:43.560 align:start position:0% guarantee that they can come in 00:39:43.560 --> 00:39:45.829 align:start position:0% guarantee that they can come in atomically<00:39:44.099> and<00:39:44.280> I<00:39:44.400> could<00:39:44.520> do<00:39:44.760> that<00:39:45.000> because<00:39:45.540> I 00:39:45.829 --> 00:39:45.839 align:start position:0% atomically and I could do that because I 00:39:45.839 --> 00:39:47.329 align:start position:0% atomically and I could do that because I sequence<00:39:46.140> all<00:39:46.260> the<00:39:46.440> chains<00:39:46.680> at<00:39:46.800> the<00:39:46.920> same<00:39:47.099> time 00:39:47.329 --> 00:39:47.339 align:start position:0% sequence all the chains at the same time 00:39:47.339 --> 00:39:49.190 align:start position:0% sequence all the chains at the same time so<00:39:48.000> now<00:39:48.180> you<00:39:48.359> have<00:39:48.480> different<00:39:48.839> games 00:39:49.190 --> 00:39:49.200 align:start position:0% so now you have different games 00:39:49.200 --> 00:39:50.870 align:start position:0% so now you have different games different<00:39:49.560> worlds<00:39:50.099> different<00:39:50.339> realities 00:39:50.870 --> 00:39:50.880 align:start position:0% different worlds different realities 00:39:50.880 --> 00:39:52.490 align:start position:0% different worlds different realities that<00:39:51.480> can<00:39:51.660> interact<00:39:51.960> with<00:39:52.140> each<00:39:52.380> other 00:39:52.490 --> 00:39:52.500 align:start position:0% that can interact with each other 00:39:52.500 --> 00:39:54.829 align:start position:0% that can interact with each other they're<00:39:53.160> their<00:39:53.460> own<00:39:53.579> States<00:39:53.880> right<00:39:54.180> there<00:39:54.420> the 00:39:54.829 --> 00:39:54.839 align:start position:0% they're their own States right there the 00:39:54.839 --> 00:39:57.109 align:start position:0% they're their own States right there the validation<00:39:55.320> is<00:39:55.500> separated<00:39:55.940> none<00:39:56.940> of<00:39:57.060> the 00:39:57.109 --> 00:39:57.119 align:start position:0% validation is separated none of the 00:39:57.119 --> 00:39:58.730 align:start position:0% validation is separated none of the validity<00:39:57.540> of<00:39:57.720> one<00:39:57.900> of<00:39:58.020> these<00:39:58.140> chains<00:39:58.440> depends 00:39:58.730 --> 00:39:58.740 align:start position:0% validity of one of these chains depends 00:39:58.740 --> 00:40:00.650 align:start position:0% validity of one of these chains depends on<00:39:58.859> the<00:39:58.980> validity<00:39:59.339> of<00:39:59.460> the<00:39:59.520> other<00:39:59.640> chain<00:39:59.880> but 00:40:00.650 --> 00:40:00.660 align:start position:0% on the validity of the other chain but 00:40:00.660 --> 00:40:02.030 align:start position:0% on the validity of the other chain but they<00:40:00.839> can<00:40:00.960> talk<00:40:01.140> to<00:40:01.320> each<00:40:01.500> other<00:40:01.619> as<00:40:01.859> if 00:40:02.030 --> 00:40:02.040 align:start position:0% they can talk to each other as if 00:40:02.040 --> 00:40:04.190 align:start position:0% they can talk to each other as if they're<00:40:02.220> on<00:40:02.400> one<00:40:02.820> unified<00:40:03.300> chain<00:40:03.660> that's 00:40:04.190 --> 00:40:04.200 align:start position:0% they're on one unified chain that's 00:40:04.200 --> 00:40:06.290 align:start position:0% they're on one unified chain that's crazy<00:40:04.440> right<00:40:04.800> now<00:40:04.980> now<00:40:05.280> you<00:40:05.520> can<00:40:05.640> have<00:40:05.760> I<00:40:06.180> can 00:40:06.290 --> 00:40:06.300 align:start position:0% crazy right now now you can have I can 00:40:06.300 --> 00:40:08.329 align:start position:0% crazy right now now you can have I can have<00:40:06.420> an<00:40:06.599> action<00:40:06.900> in<00:40:07.140> one<00:40:07.320> game<00:40:07.560> all<00:40:08.099> of<00:40:08.280> a 00:40:08.329 --> 00:40:08.339 align:start position:0% have an action in one game all of a 00:40:08.339 --> 00:40:10.730 align:start position:0% have an action in one game all of a sudden<00:40:08.520> create<00:40:09.060> some<00:40:09.480> simultaneous<00:40:10.380> action 00:40:10.730 --> 00:40:10.740 align:start position:0% sudden create some simultaneous action 00:40:10.740 --> 00:40:12.890 align:start position:0% sudden create some simultaneous action in<00:40:10.920> another<00:40:11.099> world<00:40:11.460> at<00:40:12.060> the<00:40:12.180> same<00:40:12.359> exact<00:40:12.720> time 00:40:12.890 --> 00:40:12.900 align:start position:0% in another world at the same exact time 00:40:12.900 --> 00:40:14.690 align:start position:0% in another world at the same exact time if<00:40:13.200> those<00:40:13.320> two<00:40:13.500> worlds<00:40:13.800> want<00:40:13.980> to<00:40:14.160> want<00:40:14.400> to<00:40:14.579> talk 00:40:14.690 --> 00:40:14.700 align:start position:0% if those two worlds want to want to talk 00:40:14.700 --> 00:40:15.710 align:start position:0% if those two worlds want to want to talk to<00:40:14.820> each<00:40:15.000> other 00:40:15.710 --> 00:40:15.720 align:start position:0% to each other 00:40:15.720 --> 00:40:18.230 align:start position:0% to each other so<00:40:16.500> this<00:40:17.160> is<00:40:17.280> part<00:40:17.520> of<00:40:17.700> something<00:40:17.940> that 00:40:18.230 --> 00:40:18.240 align:start position:0% so this is part of something that 00:40:18.240 --> 00:40:19.910 align:start position:0% so this is part of something that optimism<00:40:18.660> is<00:40:18.900> playing<00:40:19.079> with<00:40:19.260> that<00:40:19.740> we're 00:40:19.910 --> 00:40:19.920 align:start position:0% optimism is playing with that we're 00:40:19.920 --> 00:40:21.290 align:start position:0% optimism is playing with that we're calling<00:40:20.280> the<00:40:20.400> super<00:40:20.579> chain<00:40:20.820> we<00:40:21.060> think<00:40:21.180> that 00:40:21.290 --> 00:40:21.300 align:start position:0% calling the super chain we think that 00:40:21.300 --> 00:40:23.630 align:start position:0% calling the super chain we think that this<00:40:21.480> extends<00:40:21.900> a<00:40:22.020> little<00:40:22.140> bit<00:40:22.260> more<00:40:22.500> than<00:40:23.280> just 00:40:23.630 --> 00:40:23.640 align:start position:0% this extends a little bit more than just 00:40:23.640 --> 00:40:25.730 align:start position:0% this extends a little bit more than just its<00:40:24.480> shared<00:40:24.720> infrastructure<00:40:25.260> I<00:40:25.500> think<00:40:25.619> that 00:40:25.730 --> 00:40:25.740 align:start position:0% its shared infrastructure I think that 00:40:25.740 --> 00:40:27.349 align:start position:0% its shared infrastructure I think that the<00:40:25.980> incentive<00:40:26.339> here<00:40:26.520> is<00:40:26.700> not<00:40:26.880> just<00:40:27.000> to<00:40:27.180> share 00:40:27.349 --> 00:40:27.359 align:start position:0% the incentive here is not just to share 00:40:27.359 --> 00:40:29.329 align:start position:0% the incentive here is not just to share infrastructure<00:40:27.900> it's<00:40:28.079> to<00:40:28.320> share<00:40:28.500> code<00:40:28.800> it's 00:40:29.329 --> 00:40:29.339 align:start position:0% infrastructure it's to share code it's 00:40:29.339 --> 00:40:31.550 align:start position:0% infrastructure it's to share code it's to<00:40:29.520> share<00:40:29.640> a<00:40:29.820> set<00:40:29.940> of<00:40:30.060> values<00:40:30.540> is<00:40:31.020> to<00:40:31.200> basically 00:40:31.550 --> 00:40:31.560 align:start position:0% to share a set of values is to basically 00:40:31.560 --> 00:40:33.589 align:start position:0% to share a set of values is to basically collaborate<00:40:32.339> on<00:40:32.880> having<00:40:33.060> all<00:40:33.359> of<00:40:33.420> these 00:40:33.589 --> 00:40:33.599 align:start position:0% collaborate on having all of these 00:40:33.599 --> 00:40:35.089 align:start position:0% collaborate on having all of these different<00:40:33.780> games<00:40:34.140> and<00:40:34.680> all<00:40:34.859> these<00:40:34.980> different 00:40:35.089 --> 00:40:35.099 align:start position:0% different games and all these different 00:40:35.099 --> 00:40:36.650 align:start position:0% different games and all these different worlds<00:40:35.520> maybe<00:40:35.700> it's<00:40:35.820> not<00:40:36.000> games<00:40:36.180> maybe<00:40:36.480> it's 00:40:36.650 --> 00:40:36.660 align:start position:0% worlds maybe it's not games maybe it's 00:40:36.660 --> 00:40:38.630 align:start position:0% worlds maybe it's not games maybe it's entirely<00:40:37.020> different<00:40:37.260> Roll-Ups<00:40:37.859> but<00:40:38.400> they 00:40:38.630 --> 00:40:38.640 align:start position:0% entirely different Roll-Ups but they 00:40:38.640 --> 00:40:40.010 align:start position:0% entirely different Roll-Ups but they basically<00:40:38.940> I<00:40:39.180> think<00:40:39.300> there's<00:40:39.420> we<00:40:39.720> think<00:40:39.900> that 00:40:40.010 --> 00:40:40.020 align:start position:0% basically I think there's we think that 00:40:40.020 --> 00:40:42.290 align:start position:0% basically I think there's we think that there's<00:40:40.200> a<00:40:40.440> strong<00:40:40.680> incentive<00:40:41.339> for<00:40:41.940> these 00:40:42.290 --> 00:40:42.300 align:start position:0% there's a strong incentive for these 00:40:42.300 --> 00:40:44.630 align:start position:0% there's a strong incentive for these systems<00:40:42.780> to<00:40:43.320> not<00:40:43.500> just<00:40:43.680> be<00:40:43.800> able<00:40:43.980> to<00:40:44.099> transact 00:40:44.630 --> 00:40:44.640 align:start position:0% systems to not just be able to transact 00:40:44.640 --> 00:40:46.790 align:start position:0% systems to not just be able to transact atomically<00:40:45.300> but<00:40:45.839> to<00:40:46.020> really<00:40:46.200> be<00:40:46.500> able<00:40:46.680> to 00:40:46.790 --> 00:40:46.800 align:start position:0% atomically but to really be able to 00:40:46.800 --> 00:40:48.770 align:start position:0% atomically but to really be able to collaborate<00:40:47.280> with<00:40:47.460> one<00:40:47.700> another 00:40:48.770 --> 00:40:48.780 align:start position:0% collaborate with one another 00:40:48.780 --> 00:40:50.750 align:start position:0% collaborate with one another um<00:40:48.839> towards<00:40:49.320> some<00:40:49.619> coherent<00:40:50.220> Vision<00:40:50.400> because 00:40:50.750 --> 00:40:50.760 align:start position:0% um towards some coherent Vision because 00:40:50.760 --> 00:40:53.329 align:start position:0% um towards some coherent Vision because you're<00:40:51.300> much<00:40:51.540> better<00:40:51.839> joining<00:40:52.619> in<00:40:52.800> on<00:40:53.099> this 00:40:53.329 --> 00:40:53.339 align:start position:0% you're much better joining in on this 00:40:53.339 --> 00:40:55.130 align:start position:0% you're much better joining in on this system<00:40:53.579> than<00:40:54.060> you<00:40:54.300> are<00:40:54.359> trying<00:40:54.599> to<00:40:54.720> build<00:40:54.839> your 00:40:55.130 --> 00:40:55.140 align:start position:0% system than you are trying to build your 00:40:55.140 --> 00:40:56.630 align:start position:0% system than you are trying to build your own<00:40:55.200> chains<00:40:55.740> separately<00:40:56.040> with<00:40:56.339> your<00:40:56.520> own 00:40:56.630 --> 00:40:56.640 align:start position:0% own chains separately with your own 00:40:56.640 --> 00:40:58.010 align:start position:0% own chains separately with your own sequencer<00:40:57.119> set<00:40:57.300> and<00:40:57.480> you<00:40:57.599> have<00:40:57.660> to<00:40:57.720> run<00:40:57.839> all 00:40:58.010 --> 00:40:58.020 align:start position:0% sequencer set and you have to run all 00:40:58.020 --> 00:40:59.750 align:start position:0% sequencer set and you have to run all the<00:40:58.140> infrastructure<00:40:58.680> and<00:40:59.160> you<00:40:59.339> don't<00:40:59.460> get<00:40:59.640> to 00:40:59.750 --> 00:40:59.760 align:start position:0% the infrastructure and you don't get to 00:40:59.760 --> 00:41:02.210 align:start position:0% the infrastructure and you don't get to talk<00:40:59.940> it<00:41:00.420> you<00:41:00.780> know<00:41:00.900> atomically<00:41:01.859> with<00:41:02.040> the 00:41:02.210 --> 00:41:02.220 align:start position:0% talk it you know atomically with the 00:41:02.220 --> 00:41:03.410 align:start position:0% talk it you know atomically with the rest<00:41:02.280> of<00:41:02.460> the<00:41:02.579> system 00:41:03.410 --> 00:41:03.420 align:start position:0% rest of the system 00:41:03.420 --> 00:41:05.870 align:start position:0% rest of the system so<00:41:04.200> you<00:41:04.740> know<00:41:04.859> long<00:41:05.099> live<00:41:05.280> the<00:41:05.520> super<00:41:05.640> chain 00:41:05.870 --> 00:41:05.880 align:start position:0% so you know long live the super chain 00:41:05.880 --> 00:41:07.849 align:start position:0% so you know long live the super chain very<00:41:06.240> I<00:41:06.660> would<00:41:06.960> highly<00:41:07.200> recommend<00:41:07.560> if<00:41:07.740> you're 00:41:07.849 --> 00:41:07.859 align:start position:0% very I would highly recommend if you're 00:41:07.859 --> 00:41:09.109 align:start position:0% very I would highly recommend if you're interested<00:41:08.160> in<00:41:08.280> this<00:41:08.400> how<00:41:08.640> this<00:41:08.820> might<00:41:09.000> work 00:41:09.109 --> 00:41:09.119 align:start position:0% interested in this how this might work 00:41:09.119 --> 00:41:11.630 align:start position:0% interested in this how this might work in<00:41:09.359> more<00:41:09.540> detail<00:41:09.900> come<00:41:10.859> to<00:41:11.099> the<00:41:11.220> back-to-back 00:41:11.630 --> 00:41:11.640 align:start position:0% in more detail come to the back-to-back 00:41:11.640 --> 00:41:13.370 align:start position:0% in more detail come to the back-to-back talk<00:41:11.820> with<00:41:12.060> Carl<00:41:12.240> and<00:41:12.540> me<00:41:12.720> later<00:41:13.079> this 00:41:13.370 --> 00:41:13.380 align:start position:0% talk with Carl and me later this 00:41:13.380 --> 00:41:14.750 align:start position:0% talk with Carl and me later this afternoon<00:41:13.500> we'll<00:41:13.920> go<00:41:14.040> into<00:41:14.160> much<00:41:14.339> more<00:41:14.460> detail 00:41:14.750 --> 00:41:14.760 align:start position:0% afternoon we'll go into much more detail 00:41:14.760 --> 00:41:17.329 align:start position:0% afternoon we'll go into much more detail about<00:41:14.880> how<00:41:15.119> this<00:41:15.359> how<00:41:15.780> all<00:41:15.900> this<00:41:16.079> works 00:41:17.329 --> 00:41:17.339 align:start position:0% about how this how all this works 00:41:17.339 --> 00:41:19.849 align:start position:0% about how this how all this works all<00:41:17.760> right<00:41:17.880> where<00:41:18.060> are<00:41:18.240> we<00:41:18.359> all<00:41:19.140> right<00:41:19.260> so<00:41:19.560> uh 00:41:19.849 --> 00:41:19.859 align:start position:0% all right where are we all right so uh 00:41:19.859 --> 00:41:21.290 align:start position:0% all right where are we all right so uh the<00:41:19.980> other<00:41:20.099> question<00:41:20.280> I<00:41:20.460> get<00:41:20.579> is<00:41:20.760> why<00:41:20.940> make<00:41:21.119> it 00:41:21.290 --> 00:41:21.300 align:start position:0% the other question I get is why make it 00:41:21.300 --> 00:41:22.490 align:start position:0% the other question I get is why make it you<00:41:21.420> know<00:41:21.540> free<00:41:21.660> and<00:41:21.839> open<00:41:21.960> source<00:41:22.380> right 00:41:22.490 --> 00:41:22.500 align:start position:0% you know free and open source right 00:41:22.500 --> 00:41:24.650 align:start position:0% you know free and open source right aren't<00:41:22.800> you<00:41:22.980> basically<00:41:23.700> just<00:41:24.000> like<00:41:24.180> letting 00:41:24.650 --> 00:41:24.660 align:start position:0% aren't you basically just like letting 00:41:24.660 --> 00:41:27.230 align:start position:0% aren't you basically just like letting people<00:41:25.140> compete<00:41:25.619> with<00:41:25.740> optimism<00:41:26.220> and<00:41:27.119> build 00:41:27.230 --> 00:41:27.240 align:start position:0% people compete with optimism and build 00:41:27.240 --> 00:41:28.609 align:start position:0% people compete with optimism and build their<00:41:27.420> own<00:41:27.540> roll<00:41:27.720> up<00:41:27.839> and<00:41:28.020> the<00:41:28.140> answer<00:41:28.260> is<00:41:28.440> like 00:41:28.609 --> 00:41:28.619 align:start position:0% their own roll up and the answer is like 00:41:28.619 --> 00:41:30.950 align:start position:0% their own roll up and the answer is like kind<00:41:28.800> of<00:41:28.920> yeah<00:41:29.099> right<00:41:29.400> this<00:41:29.700> is<00:41:29.760> the<00:41:29.940> idea 00:41:30.950 --> 00:41:30.960 align:start position:0% kind of yeah right this is the idea 00:41:30.960 --> 00:41:32.569 align:start position:0% kind of yeah right this is the idea um<00:41:31.020> and<00:41:31.260> and<00:41:31.380> the<00:41:31.740> idea<00:41:31.980> basically<00:41:32.400> the 00:41:32.569 --> 00:41:32.579 align:start position:0% um and and the idea basically the 00:41:32.579 --> 00:41:34.130 align:start position:0% um and and the idea basically the argument<00:41:32.880> is<00:41:33.119> that<00:41:33.300> the<00:41:33.480> reason<00:41:33.599> we<00:41:33.839> have<00:41:34.020> to 00:41:34.130 --> 00:41:34.140 align:start position:0% argument is that the reason we have to 00:41:34.140 --> 00:41:35.750 align:start position:0% argument is that the reason we have to do<00:41:34.320> this<00:41:34.500> is<00:41:34.920> because<00:41:35.099> there's<00:41:35.280> just<00:41:35.460> no<00:41:35.640> other 00:41:35.750 --> 00:41:35.760 align:start position:0% do this is because there's just no other 00:41:35.760 --> 00:41:38.270 align:start position:0% do this is because there's just no other way<00:41:36.000> to<00:41:36.119> do<00:41:36.240> this<00:41:36.420> we<00:41:37.200> need<00:41:37.440> you<00:41:37.859> know<00:41:37.980> we<00:41:38.099> think 00:41:38.270 --> 00:41:38.280 align:start position:0% way to do this we need you know we think 00:41:38.280 --> 00:41:39.890 align:start position:0% way to do this we need you know we think that<00:41:38.400> there's<00:41:38.520> going<00:41:38.700> to<00:41:38.760> be<00:41:38.880> this<00:41:39.119> explosion 00:41:39.890 --> 00:41:39.900 align:start position:0% that there's going to be this explosion 00:41:39.900 --> 00:41:42.050 align:start position:0% that there's going to be this explosion of<00:41:40.320> people<00:41:40.619> who<00:41:41.220> are<00:41:41.339> interested<00:41:41.700> in<00:41:41.820> building 00:41:42.050 --> 00:41:42.060 align:start position:0% of people who are interested in building 00:41:42.060 --> 00:41:44.210 align:start position:0% of people who are interested in building layer<00:41:42.540> twos<00:41:42.839> interested<00:41:43.500> in<00:41:43.560> building<00:41:43.800> layer 00:41:44.210 --> 00:41:44.220 align:start position:0% layer twos interested in building layer 00:41:44.220 --> 00:41:46.130 align:start position:0% layer twos interested in building layer threes<00:41:44.579> right<00:41:45.060> we're<00:41:45.300> already<00:41:45.540> seeing<00:41:45.960> all 00:41:46.130 --> 00:41:46.140 align:start position:0% threes right we're already seeing all 00:41:46.140 --> 00:41:49.190 align:start position:0% threes right we're already seeing all these<00:41:46.440> you<00:41:46.800> know<00:41:46.920> big<00:41:47.520> L1<00:41:48.060> systems<00:41:48.780> come<00:41:49.020> in 00:41:49.190 --> 00:41:49.200 align:start position:0% these you know big L1 systems come in 00:41:49.200 --> 00:41:50.990 align:start position:0% these you know big L1 systems come in and<00:41:49.740> they're<00:41:49.920> experimenting<00:41:50.579> on<00:41:50.880> the 00:41:50.990 --> 00:41:51.000 align:start position:0% and they're experimenting on the 00:41:51.000 --> 00:41:52.670 align:start position:0% and they're experimenting on the execution<00:41:51.420> layer<00:41:51.839> right<00:41:52.140> they're<00:41:52.619> they're 00:41:52.670 --> 00:41:52.680 align:start position:0% execution layer right they're they're 00:41:52.680 --> 00:41:55.010 align:start position:0% execution layer right they're they're competing<00:41:53.280> with<00:41:53.520> ethereum<00:41:54.000> on<00:41:54.540> the<00:41:54.660> execution 00:41:55.010 --> 00:41:55.020 align:start position:0% competing with ethereum on the execution 00:41:55.020 --> 00:41:55.849 align:start position:0% competing with ethereum on the execution layer<00:41:55.260> they're<00:41:55.380> saying<00:41:55.560> we're<00:41:55.680> going<00:41:55.800> to 00:41:55.849 --> 00:41:55.859 align:start position:0% layer they're saying we're going to 00:41:55.859 --> 00:41:58.550 align:start position:0% layer they're saying we're going to build<00:41:55.980> a<00:41:56.220> parallelized<00:41:56.880> VM<00:41:57.240> and<00:41:57.900> that's<00:41:58.260> our 00:41:58.550 --> 00:41:58.560 align:start position:0% build a parallelized VM and that's our 00:41:58.560 --> 00:42:00.890 align:start position:0% build a parallelized VM and that's our advantage<00:41:59.040> and<00:41:59.640> if<00:41:59.820> you<00:42:00.180> really<00:42:00.420> want<00:42:00.780> to 00:42:00.890 --> 00:42:00.900 align:start position:0% advantage and if you really want to 00:42:00.900 --> 00:42:02.870 align:start position:0% advantage and if you really want to survive<00:42:01.380> you're<00:42:02.040> going<00:42:02.280> to<00:42:02.400> need<00:42:02.579> to<00:42:02.640> be<00:42:02.760> able 00:42:02.870 --> 00:42:02.880 align:start position:0% survive you're going to need to be able 00:42:02.880 --> 00:42:04.609 align:start position:0% survive you're going to need to be able to<00:42:03.000> compete<00:42:03.540> on<00:42:03.660> this<00:42:03.780> stuff<00:42:03.960> and<00:42:04.380> we<00:42:04.500> think 00:42:04.609 --> 00:42:04.619 align:start position:0% to compete on this stuff and we think 00:42:04.619 --> 00:42:05.510 align:start position:0% to compete on this stuff and we think you're<00:42:04.740> going<00:42:04.920> to<00:42:04.980> need<00:42:05.099> to<00:42:05.160> be<00:42:05.280> able<00:42:05.339> to 00:42:05.510 --> 00:42:05.520 align:start position:0% you're going to need to be able to 00:42:05.520 --> 00:42:07.430 align:start position:0% you're going to need to be able to compete<00:42:05.880> on<00:42:06.000> this<00:42:06.180> stuff<00:42:06.359> without<00:42:06.960> having<00:42:07.320> to 00:42:07.430 --> 00:42:07.440 align:start position:0% compete on this stuff without having to 00:42:07.440 --> 00:42:09.650 align:start position:0% compete on this stuff without having to have<00:42:07.680> 25<00:42:08.220> Engineers<00:42:08.880> work<00:42:09.180> on<00:42:09.300> this<00:42:09.480> problem 00:42:09.650 --> 00:42:09.660 align:start position:0% have 25 Engineers work on this problem 00:42:09.660 --> 00:42:11.510 align:start position:0% have 25 Engineers work on this problem like<00:42:09.960> three<00:42:10.140> years<00:42:10.380> like<00:42:10.680> for<00:42:10.920> three<00:42:11.339> years 00:42:11.510 --> 00:42:11.520 align:start position:0% like three years like for three years 00:42:11.520 --> 00:42:13.670 align:start position:0% like three years like for three years like<00:42:11.760> we<00:42:12.000> did<00:42:12.180> and<00:42:13.020> instead<00:42:13.320> you're<00:42:13.440> going<00:42:13.619> to 00:42:13.670 --> 00:42:13.680 align:start position:0% like we did and instead you're going to 00:42:13.680 --> 00:42:15.470 align:start position:0% like we did and instead you're going to want<00:42:13.800> the<00:42:13.980> ability<00:42:14.220> to<00:42:14.400> have<00:42:14.640> three<00:42:15.000> Engineers 00:42:15.470 --> 00:42:15.480 align:start position:0% want the ability to have three Engineers 00:42:15.480 --> 00:42:16.790 align:start position:0% want the ability to have three Engineers figure<00:42:15.780> out<00:42:15.960> how<00:42:16.140> to<00:42:16.260> do<00:42:16.380> this<00:42:16.500> in<00:42:16.680> three 00:42:16.790 --> 00:42:16.800 align:start position:0% figure out how to do this in three 00:42:16.800 --> 00:42:18.829 align:start position:0% figure out how to do this in three months<00:42:16.920> and<00:42:17.040> start<00:42:17.280> business<00:42:17.700> out<00:42:17.940> of<00:42:18.119> it<00:42:18.240> so 00:42:18.829 --> 00:42:18.839 align:start position:0% months and start business out of it so 00:42:18.839 --> 00:42:20.569 align:start position:0% months and start business out of it so this<00:42:19.079> is<00:42:19.200> basically<00:42:19.440> the<00:42:19.680> argument<00:42:19.920> we<00:42:20.220> if<00:42:20.400> you 00:42:20.569 --> 00:42:20.579 align:start position:0% this is basically the argument we if you 00:42:20.579 --> 00:42:22.490 align:start position:0% this is basically the argument we if you if<00:42:20.880> you<00:42:21.060> want<00:42:21.240> to<00:42:21.420> really<00:42:21.599> make<00:42:22.079> it<00:42:22.200> possible 00:42:22.490 --> 00:42:22.500 align:start position:0% if you want to really make it possible 00:42:22.500 --> 00:42:24.770 align:start position:0% if you want to really make it possible for<00:42:22.800> ethereum<00:42:23.220> to<00:42:23.460> continue<00:42:23.579> to<00:42:23.880> compete<00:42:24.300> and 00:42:24.770 --> 00:42:24.780 align:start position:0% for ethereum to continue to compete and 00:42:24.780 --> 00:42:26.510 align:start position:0% for ethereum to continue to compete and for<00:42:24.960> people<00:42:25.140> to<00:42:25.440> experiment<00:42:26.160> on<00:42:26.400> the 00:42:26.510 --> 00:42:26.520 align:start position:0% for people to experiment on the 00:42:26.520 --> 00:42:27.950 align:start position:0% for people to experiment on the execution<00:42:26.880> layer<00:42:27.240> experiment<00:42:27.660> on<00:42:27.839> the 00:42:27.950 --> 00:42:27.960 align:start position:0% execution layer experiment on the 00:42:27.960 --> 00:42:29.690 align:start position:0% execution layer experiment on the derivation<00:42:28.320> layer<00:42:28.680> experiment<00:42:29.099> on<00:42:29.280> all<00:42:29.460> these 00:42:29.690 --> 00:42:29.700 align:start position:0% derivation layer experiment on all these 00:42:29.700 --> 00:42:31.609 align:start position:0% derivation layer experiment on all these different<00:42:29.880> layers<00:42:30.300> it<00:42:31.020> just<00:42:31.140> has<00:42:31.320> to<00:42:31.500> be 00:42:31.609 --> 00:42:31.619 align:start position:0% different layers it just has to be 00:42:31.619 --> 00:42:33.050 align:start position:0% different layers it just has to be available<00:42:31.859> right<00:42:32.220> if<00:42:32.520> there's<00:42:32.640> not<00:42:32.880> a 00:42:33.050 --> 00:42:33.060 align:start position:0% available right if there's not a 00:42:33.060 --> 00:42:34.970 align:start position:0% available right if there's not a permissive<00:42:33.420> license<00:42:33.599> on<00:42:33.960> it<00:42:34.079> you<00:42:34.619> can't<00:42:34.740> use 00:42:34.970 --> 00:42:34.980 align:start position:0% permissive license on it you can't use 00:42:34.980 --> 00:42:36.950 align:start position:0% permissive license on it you can't use it<00:42:35.160> if<00:42:35.579> it's<00:42:35.700> not<00:42:35.940> if<00:42:36.240> it's<00:42:36.420> not<00:42:36.599> modular 00:42:36.950 --> 00:42:36.960 align:start position:0% it if it's not if it's not modular 00:42:36.960 --> 00:42:39.170 align:start position:0% it if it's not if it's not modular enough<00:42:37.260> if<00:42:37.560> it's<00:42:37.740> too<00:42:37.980> hectic<00:42:38.339> to<00:42:38.640> try<00:42:38.760> to<00:42:38.880> hack 00:42:39.170 --> 00:42:39.180 align:start position:0% enough if it's too hectic to try to hack 00:42:39.180 --> 00:42:41.510 align:start position:0% enough if it's too hectic to try to hack in<00:42:39.480> your<00:42:40.140> modifications<00:42:40.740> to<00:42:40.980> the<00:42:41.160> execution 00:42:41.510 --> 00:42:41.520 align:start position:0% in your modifications to the execution 00:42:41.520 --> 00:42:43.490 align:start position:0% in your modifications to the execution layer<00:42:41.880> you<00:42:42.119> can't<00:42:42.240> use<00:42:42.480> it<00:42:42.660> so<00:42:43.079> the<00:42:43.200> goal<00:42:43.440> is 00:42:43.490 --> 00:42:43.500 align:start position:0% layer you can't use it so the goal is 00:42:43.500 --> 00:42:45.770 align:start position:0% layer you can't use it so the goal is just<00:42:43.680> make<00:42:43.859> it<00:42:44.040> as<00:42:44.220> available<00:42:44.460> as<00:42:44.820> possible<00:42:45.240> so 00:42:45.770 --> 00:42:45.780 align:start position:0% just make it as available as possible so 00:42:45.780 --> 00:42:48.349 align:start position:0% just make it as available as possible so that<00:42:45.900> ethereum<00:42:46.380> can<00:42:46.619> continue<00:42:46.859> to<00:42:47.280> compete<00:42:47.760> on 00:42:48.349 --> 00:42:48.359 align:start position:0% that ethereum can continue to compete on 00:42:48.359 --> 00:42:50.450 align:start position:0% that ethereum can continue to compete on every<00:42:48.660> single<00:42:48.960> layer<00:42:49.200> of<00:42:49.380> the<00:42:49.500> stack<00:42:49.740> but<00:42:50.280> you 00:42:50.450 --> 00:42:50.460 align:start position:0% every single layer of the stack but you 00:42:50.460 --> 00:42:51.710 align:start position:0% every single layer of the stack but you can<00:42:50.520> still<00:42:50.700> stay<00:42:50.880> within<00:42:51.240> the<00:42:51.359> ethereum 00:42:51.710 --> 00:42:51.720 align:start position:0% can still stay within the ethereum 00:42:51.720 --> 00:42:53.510 align:start position:0% can still stay within the ethereum ecosystem 00:42:53.510 --> 00:42:53.520 align:start position:0% ecosystem 00:42:53.520 --> 00:42:55.130 align:start position:0% ecosystem um and<00:42:53.760> you<00:42:53.820> know<00:42:53.940> this<00:42:54.180> is<00:42:54.300> us<00:42:54.480> today<00:42:54.720> this<00:42:55.079> is 00:42:55.130 --> 00:42:55.140 align:start position:0% um and you know this is us today this is 00:42:55.140 --> 00:42:57.349 align:start position:0% um and you know this is us today this is where<00:42:55.380> we<00:42:55.560> are<00:42:55.680> this<00:42:56.280> is<00:42:56.339> we<00:42:56.579> got<00:42:56.700> lattice<00:42:57.180> we 00:42:57.349 --> 00:42:57.359 align:start position:0% where we are this is we got lattice we 00:42:57.359 --> 00:42:59.150 align:start position:0% where we are this is we got lattice we got<00:42:57.480> a<00:42:57.599> couple<00:42:57.720> other<00:42:57.900> people<00:42:58.200> and<00:42:58.920> you<00:42:59.040> know 00:42:59.150 --> 00:42:59.160 align:start position:0% got a couple other people and you know 00:42:59.160 --> 00:43:00.589 align:start position:0% got a couple other people and you know this<00:42:59.400> is<00:42:59.520> the<00:42:59.700> world<00:42:59.819> that<00:43:00.060> we're<00:43:00.180> imagining 00:43:00.589 --> 00:43:00.599 align:start position:0% this is the world that we're imagining 00:43:00.599 --> 00:43:01.910 align:start position:0% this is the world that we're imagining right<00:43:00.780> we're<00:43:01.079> imagining<00:43:01.440> that<00:43:01.560> basically 00:43:01.910 --> 00:43:01.920 align:start position:0% right we're imagining that basically 00:43:01.920 --> 00:43:04.069 align:start position:0% right we're imagining that basically everybody<00:43:02.700> is<00:43:03.060> building<00:43:03.240> on<00:43:03.540> a<00:43:03.660> system<00:43:03.780> like 00:43:04.069 --> 00:43:04.079 align:start position:0% everybody is building on a system like 00:43:04.079 --> 00:43:05.630 align:start position:0% everybody is building on a system like this<00:43:04.319> and<00:43:04.800> they're<00:43:04.980> collaborating<00:43:05.400> and 00:43:05.630 --> 00:43:05.640 align:start position:0% this and they're collaborating and 00:43:05.640 --> 00:43:06.829 align:start position:0% this and they're collaborating and they're<00:43:05.760> working<00:43:05.940> on<00:43:06.180> a<00:43:06.420> shared 00:43:06.829 --> 00:43:06.839 align:start position:0% they're working on a shared 00:43:06.839 --> 00:43:08.930 align:start position:0% they're working on a shared infrastructure 00:43:08.930 --> 00:43:08.940 align:start position:0% infrastructure 00:43:08.940 --> 00:43:10.130 align:start position:0% infrastructure and<00:43:09.240> by<00:43:09.359> working<00:43:09.540> on<00:43:09.780> a<00:43:09.839> shared 00:43:10.130 --> 00:43:10.140 align:start position:0% and by working on a shared 00:43:10.140 --> 00:43:12.170 align:start position:0% and by working on a shared infrastructure<00:43:10.560> you<00:43:10.740> share<00:43:10.980> audits<00:43:11.520> right 00:43:12.170 --> 00:43:12.180 align:start position:0% infrastructure you share audits right 00:43:12.180 --> 00:43:14.690 align:start position:0% infrastructure you share audits right you<00:43:12.780> can<00:43:12.839> share<00:43:13.079> engineering<00:43:13.740> time<00:43:14.040> it 00:43:14.690 --> 00:43:14.700 align:start position:0% you can share engineering time it 00:43:14.700 --> 00:43:16.670 align:start position:0% you can share engineering time it basically<00:43:14.940> takes<00:43:15.180> you<00:43:15.420> a<00:43:15.900> hundred<00:43:16.140> times<00:43:16.319> less 00:43:16.670 --> 00:43:16.680 align:start position:0% basically takes you a hundred times less 00:43:16.680 --> 00:43:19.670 align:start position:0% basically takes you a hundred times less effort<00:43:17.160> to<00:43:17.819> build<00:43:17.940> 100<00:43:18.180> companies<00:43:18.839> instead<00:43:19.619> of 00:43:19.670 --> 00:43:19.680 align:start position:0% effort to build 100 companies instead of 00:43:19.680 --> 00:43:22.309 align:start position:0% effort to build 100 companies instead of having<00:43:19.859> every<00:43:20.339> single<00:43:20.700> company<00:43:21.000> fragment<00:43:21.839> and 00:43:22.309 --> 00:43:22.319 align:start position:0% having every single company fragment and 00:43:22.319 --> 00:43:24.170 align:start position:0% having every single company fragment and build<00:43:22.500> their<00:43:22.740> own<00:43:22.920> system<00:43:23.220> you<00:43:23.819> basically 00:43:24.170 --> 00:43:24.180 align:start position:0% build their own system you basically 00:43:24.180 --> 00:43:25.309 align:start position:0% build their own system you basically have<00:43:24.359> all<00:43:24.540> the<00:43:24.660> freedom<00:43:24.960> in<00:43:25.079> the<00:43:25.200> world 00:43:25.309 --> 00:43:25.319 align:start position:0% have all the freedom in the world 00:43:25.319 --> 00:43:27.109 align:start position:0% have all the freedom in the world without<00:43:25.740> actually<00:43:26.099> worrying<00:43:26.640> about<00:43:26.819> the 00:43:27.109 --> 00:43:27.119 align:start position:0% without actually worrying about the 00:43:27.119 --> 00:43:28.849 align:start position:0% without actually worrying about the low-level<00:43:27.480> technical<00:43:27.839> details<00:43:28.319> about<00:43:28.440> how 00:43:28.849 --> 00:43:28.859 align:start position:0% low-level technical details about how 00:43:28.859 --> 00:43:30.230 align:start position:0% low-level technical details about how are<00:43:28.980> you<00:43:29.099> going<00:43:29.220> to<00:43:29.339> publish<00:43:29.579> transactions<00:43:30.060> to 00:43:30.230 --> 00:43:30.240 align:start position:0% are you going to publish transactions to 00:43:30.240 --> 00:43:31.970 align:start position:0% are you going to publish transactions to layer<00:43:30.540> one<00:43:30.660> reliably<00:43:31.200> how<00:43:31.500> are<00:43:31.680> you<00:43:31.740> going<00:43:31.859> to 00:43:31.970 --> 00:43:31.980 align:start position:0% layer one reliably how are you going to 00:43:31.980 --> 00:43:33.829 align:start position:0% layer one reliably how are you going to deal<00:43:32.040> with<00:43:32.220> reorgs<00:43:32.940> right<00:43:33.119> how<00:43:33.480> are<00:43:33.599> you<00:43:33.720> going 00:43:33.829 --> 00:43:33.839 align:start position:0% deal with reorgs right how are you going 00:43:33.839 --> 00:43:35.270 align:start position:0% deal with reorgs right how are you going to<00:43:33.900> make<00:43:34.020> the<00:43:34.200> proof<00:43:34.500> work<00:43:34.680> because<00:43:34.920> all<00:43:35.099> that 00:43:35.270 --> 00:43:35.280 align:start position:0% to make the proof work because all that 00:43:35.280 --> 00:43:36.770 align:start position:0% to make the proof work because all that stuff<00:43:35.400> is<00:43:35.579> extraordinarily<00:43:36.240> complicated 00:43:36.770 --> 00:43:36.780 align:start position:0% stuff is extraordinarily complicated 00:43:36.780 --> 00:43:39.530 align:start position:0% stuff is extraordinarily complicated there's<00:43:37.380> no<00:43:37.740> reason<00:43:38.099> why<00:43:38.819> every<00:43:39.180> single 00:43:39.530 --> 00:43:39.540 align:start position:0% there's no reason why every single 00:43:39.540 --> 00:43:41.210 align:start position:0% there's no reason why every single person<00:43:39.780> who<00:43:40.140> wants<00:43:40.380> to<00:43:40.500> build<00:43:40.680> one<00:43:40.920> of<00:43:41.040> these 00:43:41.210 --> 00:43:41.220 align:start position:0% person who wants to build one of these 00:43:41.220 --> 00:43:43.309 align:start position:0% person who wants to build one of these chains<00:43:41.579> should<00:43:42.119> have<00:43:42.359> to<00:43:42.540> basically<00:43:42.839> build<00:43:43.140> it 00:43:43.309 --> 00:43:43.319 align:start position:0% chains should have to basically build it 00:43:43.319 --> 00:43:45.710 align:start position:0% chains should have to basically build it from<00:43:43.560> scratch<00:43:43.740> doesn't<00:43:44.160> make<00:43:44.400> any<00:43:44.579> sense 00:43:45.710 --> 00:43:45.720 align:start position:0% from scratch doesn't make any sense 00:43:45.720 --> 00:43:47.030 align:start position:0% from scratch doesn't make any sense all<00:43:46.319> right 00:43:47.030 --> 00:43:47.040 align:start position:0% all right 00:43:47.040 --> 00:43:49.250 align:start position:0% all right so<00:43:47.700> some<00:43:48.060> closing<00:43:48.420> remarks<00:43:48.780> here<00:43:48.900> basically 00:43:49.250 --> 00:43:49.260 align:start position:0% so some closing remarks here basically 00:43:49.260 --> 00:43:50.990 align:start position:0% so some closing remarks here basically go<00:43:49.500> nuts<00:43:49.800> build<00:43:49.920> something<00:43:50.160> crazy<00:43:50.339> you<00:43:50.640> can<00:43:50.819> do 00:43:50.990 --> 00:43:51.000 align:start position:0% go nuts build something crazy you can do 00:43:51.000 --> 00:43:53.569 align:start position:0% go nuts build something crazy you can do so<00:43:51.359> much<00:43:51.599> with<00:43:52.140> this<00:43:52.319> architecture<00:43:52.859> right<00:43:53.160> you 00:43:53.569 --> 00:43:53.579 align:start position:0% so much with this architecture right you 00:43:53.579 --> 00:43:55.069 align:start position:0% so much with this architecture right you can<00:43:53.640> swap<00:43:53.880> out<00:43:54.000> the<00:43:54.180> data<00:43:54.359> availability<00:43:54.660> layer 00:43:55.069 --> 00:43:55.079 align:start position:0% can swap out the data availability layer 00:43:55.079 --> 00:43:56.390 align:start position:0% can swap out the data availability layer make<00:43:55.260> your<00:43:55.380> chain<00:43:55.560> cheaper<00:43:55.920> you<00:43:55.980> can<00:43:56.099> swap<00:43:56.280> out 00:43:56.390 --> 00:43:56.400 align:start position:0% make your chain cheaper you can swap out 00:43:56.400 --> 00:43:58.430 align:start position:0% make your chain cheaper you can swap out the<00:43:56.579> execution<00:43:56.940> layer<00:43:57.359> build<00:43:57.839> an<00:43:58.079> entirely 00:43:58.430 --> 00:43:58.440 align:start position:0% the execution layer build an entirely 00:43:58.440 --> 00:44:00.470 align:start position:0% the execution layer build an entirely on-chain<00:43:58.980> game<00:43:59.280> you<00:43:59.760> know<00:43:59.819> you<00:44:00.060> can<00:44:00.180> literally 00:44:00.470 --> 00:44:00.480 align:start position:0% on-chain game you know you can literally 00:44:00.480 --> 00:44:03.950 align:start position:0% on-chain game you know you can literally take<00:44:00.900> an<00:44:01.319> emulator<00:44:01.619> of<00:44:02.520> some<00:44:02.819> system<00:44:03.119> you<00:44:03.839> can 00:44:03.950 --> 00:44:03.960 align:start position:0% take an emulator of some system you can 00:44:03.960 --> 00:44:06.109 align:start position:0% take an emulator of some system you can put<00:44:04.140> it<00:44:04.260> into<00:44:04.500> the<00:44:04.680> execution<00:44:05.160> layer<00:44:05.640> and<00:44:06.000> you 00:44:06.109 --> 00:44:06.119 align:start position:0% put it into the execution layer and you 00:44:06.119 --> 00:44:07.990 align:start position:0% put it into the execution layer and you can<00:44:06.240> even<00:44:06.480> prove<00:44:07.020> that<00:44:07.140> the<00:44:07.380> whole<00:44:07.500> emulator 00:44:07.990 --> 00:44:08.000 align:start position:0% can even prove that the whole emulator 00:44:08.000 --> 00:44:10.190 align:start position:0% can even prove that the whole emulator functioned<00:44:09.000> properly<00:44:09.420> you<00:44:09.720> can<00:44:09.780> do<00:44:09.960> an 00:44:10.190 --> 00:44:10.200 align:start position:0% functioned properly you can do an 00:44:10.200 --> 00:44:11.990 align:start position:0% functioned properly you can do an enormous<00:44:10.500> amount<00:44:10.800> of<00:44:10.920> stuff<00:44:11.099> with<00:44:11.339> this<00:44:11.520> and 00:44:11.990 --> 00:44:12.000 align:start position:0% enormous amount of stuff with this and 00:44:12.000 --> 00:44:13.490 align:start position:0% enormous amount of stuff with this and the<00:44:12.180> nice<00:44:12.300> thing<00:44:12.480> is<00:44:12.599> you<00:44:12.839> don't<00:44:13.020> have<00:44:13.260> to 00:44:13.490 --> 00:44:13.500 align:start position:0% the nice thing is you don't have to 00:44:13.500 --> 00:44:15.170 align:start position:0% the nice thing is you don't have to worry<00:44:13.740> about<00:44:14.040> how<00:44:14.579> are<00:44:14.640> you<00:44:14.760> going<00:44:14.880> to<00:44:15.000> go 00:44:15.170 --> 00:44:15.180 align:start position:0% worry about how are you going to go 00:44:15.180 --> 00:44:17.150 align:start position:0% worry about how are you going to go build<00:44:15.540> the<00:44:16.079> sequencer<00:44:16.500> how<00:44:16.740> are<00:44:16.859> you<00:44:16.980> going<00:44:17.040> to 00:44:17.150 --> 00:44:17.160 align:start position:0% build the sequencer how are you going to 00:44:17.160 --> 00:44:18.589 align:start position:0% build the sequencer how are you going to go<00:44:17.280> build<00:44:17.520> the<00:44:17.880> proof<00:44:18.180> and<00:44:18.300> all<00:44:18.480> these 00:44:18.589 --> 00:44:18.599 align:start position:0% go build the proof and all these 00:44:18.599 --> 00:44:19.849 align:start position:0% go build the proof and all these different<00:44:18.720> things<00:44:18.960> you<00:44:19.260> basically<00:44:19.560> get<00:44:19.740> all 00:44:19.849 --> 00:44:19.859 align:start position:0% different things you basically get all 00:44:19.859 --> 00:44:20.930 align:start position:0% different things you basically get all that<00:44:20.040> for<00:44:20.280> free 00:44:20.930 --> 00:44:20.940 align:start position:0% that for free 00:44:20.940 --> 00:44:23.870 align:start position:0% that for free so<00:44:21.839> that's<00:44:22.319> the<00:44:22.560> idea 00:44:23.870 --> 00:44:23.880 align:start position:0% so that's the idea 00:44:23.880 --> 00:44:26.750 align:start position:0% so that's the idea um where<00:44:24.480> are<00:44:24.660> we<00:44:24.780> yeah<00:44:25.020> thanks<00:44:25.380> we're<00:44:26.099> thanks 00:44:26.750 --> 00:44:26.760 align:start position:0% um where are we yeah thanks we're thanks 00:44:26.760 --> 00:44:28.490 align:start position:0% um where are we yeah thanks we're thanks for<00:44:26.880> coming<00:44:27.000> to<00:44:27.240> my<00:44:27.300> TED<00:44:27.540> Talk 00:44:28.490 --> 00:44:28.500 align:start position:0% for coming to my TED Talk 00:44:28.500 --> 00:44:29.569 align:start position:0% for coming to my TED Talk um 00:44:29.569 --> 00:44:29.579 align:start position:0% um 00:44:29.579 --> 00:44:32.210 align:start position:0% um where<00:44:30.060> are<00:44:30.180> we<00:44:30.300> right<00:44:30.480> now<00:44:30.660> so<00:44:31.440> the<00:44:31.859> code<00:44:31.980> is 00:44:32.210 --> 00:44:32.220 align:start position:0% where are we right now so the code is 00:44:32.220 --> 00:44:33.829 align:start position:0% where are we right now so the code is all<00:44:32.339> there<00:44:32.520> it's<00:44:32.760> possible<00:44:33.119> to<00:44:33.300> hack<00:44:33.480> on<00:44:33.660> this 00:44:33.829 --> 00:44:33.839 align:start position:0% all there it's possible to hack on this 00:44:33.839 --> 00:44:35.809 align:start position:0% all there it's possible to hack on this stuff<00:44:34.020> the<00:44:34.440> real<00:44:34.619> the<00:44:34.859> next<00:44:35.040> goal<00:44:35.339> is<00:44:35.400> to<00:44:35.640> take 00:44:35.809 --> 00:44:35.819 align:start position:0% stuff the real the next goal is to take 00:44:35.819 --> 00:44:38.210 align:start position:0% stuff the real the next goal is to take take<00:44:36.119> all<00:44:36.420> these<00:44:36.660> modules<00:44:37.079> and<00:44:37.740> make<00:44:37.920> really 00:44:38.210 --> 00:44:38.220 align:start position:0% take all these modules and make really 00:44:38.220 --> 00:44:40.190 align:start position:0% take all these modules and make really really<00:44:38.400> clean<00:44:38.700> documentation<00:44:39.420> so<00:44:39.720> it's<00:44:39.900> clear 00:44:40.190 --> 00:44:40.200 align:start position:0% really clean documentation so it's clear 00:44:40.200 --> 00:44:42.349 align:start position:0% really clean documentation so it's clear what<00:44:40.920> you<00:44:41.099> have<00:44:41.220> to<00:44:41.400> change<00:44:41.640> where<00:44:42.060> you<00:44:42.180> have 00:44:42.349 --> 00:44:42.359 align:start position:0% what you have to change where you have 00:44:42.359 --> 00:44:44.030 align:start position:0% what you have to change where you have to<00:44:42.480> change<00:44:42.660> it<00:44:42.900> to<00:44:43.260> make<00:44:43.380> all<00:44:43.560> this<00:44:43.680> possible 00:44:44.030 --> 00:44:44.040 align:start position:0% to change it to make all this possible 00:44:44.040 --> 00:44:46.490 align:start position:0% to change it to make all this possible if<00:44:44.579> you<00:44:44.700> go<00:44:44.880> in<00:44:45.060> today<00:44:45.240> you<00:44:45.780> know<00:44:45.839> lattice<00:44:46.319> has 00:44:46.490 --> 00:44:46.500 align:start position:0% if you go in today you know lattice has 00:44:46.500 --> 00:44:47.470 align:start position:0% if you go in today you know lattice has been 00:44:47.470 --> 00:44:47.480 align:start position:0% been 00:44:47.480 --> 00:44:50.270 align:start position:0% been extraordinarily<00:44:48.480> Brave<00:44:49.380> to<00:44:49.680> go<00:44:49.800> in<00:44:49.980> and 00:44:50.270 --> 00:44:50.280 align:start position:0% extraordinarily Brave to go in and 00:44:50.280 --> 00:44:51.950 align:start position:0% extraordinarily Brave to go in and basically<00:44:50.579> hack<00:44:50.880> this<00:44:51.119> system<00:44:51.300> together<00:44:51.599> and 00:44:51.950 --> 00:44:51.960 align:start position:0% basically hack this system together and 00:44:51.960 --> 00:44:53.569 align:start position:0% basically hack this system together and really<00:44:52.079> make<00:44:52.319> it<00:44:52.440> work<00:44:52.619> for<00:44:52.859> them<00:44:53.040> and<00:44:53.460> we've 00:44:53.569 --> 00:44:53.579 align:start position:0% really make it work for them and we've 00:44:53.579 --> 00:44:55.849 align:start position:0% really make it work for them and we've seen<00:44:53.760> other<00:44:54.000> people<00:44:54.180> do<00:44:54.420> it<00:44:54.599> as<00:44:54.720> well<00:44:54.900> if 00:44:55.849 --> 00:44:55.859 align:start position:0% seen other people do it as well if 00:44:55.859 --> 00:44:57.170 align:start position:0% seen other people do it as well if you're<00:44:55.980> interested<00:44:56.339> in<00:44:56.460> doing<00:44:56.700> this<00:44:56.880> you<00:44:57.119> know 00:44:57.170 --> 00:44:57.180 align:start position:0% you're interested in doing this you know 00:44:57.180 --> 00:44:58.730 align:start position:0% you're interested in doing this you know come<00:44:57.359> talk<00:44:57.599> to<00:44:57.780> me<00:44:57.900> later<00:44:58.079> and<00:44:58.260> I<00:44:58.380> can<00:44:58.500> give<00:44:58.619> you 00:44:58.730 --> 00:44:58.740 align:start position:0% come talk to me later and I can give you 00:44:58.740 --> 00:45:00.710 align:start position:0% come talk to me later and I can give you pointers<00:44:59.160> but<00:44:59.760> the<00:44:59.940> goal<00:45:00.180> is<00:45:00.300> you<00:45:00.540> know<00:45:00.660> right 00:45:00.710 --> 00:45:00.720 align:start position:0% pointers but the goal is you know right 00:45:00.720 --> 00:45:02.030 align:start position:0% pointers but the goal is you know right now<00:45:00.900> it's<00:45:01.200> still<00:45:01.380> a<00:45:01.500> little<00:45:01.619> early<00:45:01.800> we're 00:45:02.030 --> 00:45:02.040 align:start position:0% now it's still a little early we're 00:45:02.040 --> 00:45:03.829 align:start position:0% now it's still a little early we're looking<00:45:02.220> for<00:45:02.460> people<00:45:02.640> to<00:45:02.880> come<00:45:03.060> in<00:45:03.240> help<00:45:03.720> us 00:45:03.829 --> 00:45:03.839 align:start position:0% looking for people to come in help us 00:45:03.839 --> 00:45:05.569 align:start position:0% looking for people to come in help us figure<00:45:04.079> out<00:45:04.260> where<00:45:04.500> the<00:45:04.619> apis<00:45:05.040> aren't<00:45:05.339> clean 00:45:05.569 --> 00:45:05.579 align:start position:0% figure out where the apis aren't clean 00:45:05.579 --> 00:45:07.370 align:start position:0% figure out where the apis aren't clean enough<00:45:05.819> right<00:45:06.240> help<00:45:06.720> us<00:45:06.839> figure<00:45:07.020> out<00:45:07.140> where 00:45:07.370 --> 00:45:07.380 align:start position:0% enough right help us figure out where 00:45:07.380 --> 00:45:10.130 align:start position:0% enough right help us figure out where the<00:45:07.500> documentation<00:45:07.980> is<00:45:08.220> in<00:45:08.339> clean<00:45:08.579> enough<00:45:09.140> if 00:45:10.130 --> 00:45:10.140 align:start position:0% the documentation is in clean enough if 00:45:10.140 --> 00:45:11.630 align:start position:0% the documentation is in clean enough if you're<00:45:10.319> if<00:45:10.619> you<00:45:10.800> know<00:45:10.920> what<00:45:11.040> you're<00:45:11.220> doing<00:45:11.400> and 00:45:11.630 --> 00:45:11.640 align:start position:0% you're if you know what you're doing and 00:45:11.640 --> 00:45:12.950 align:start position:0% you're if you know what you're doing and you're<00:45:11.819> really<00:45:12.000> interested<00:45:12.359> in<00:45:12.540> hacking<00:45:12.900> on 00:45:12.950 --> 00:45:12.960 align:start position:0% you're really interested in hacking on 00:45:12.960 --> 00:45:15.470 align:start position:0% you're really interested in hacking on something<00:45:13.200> new<00:45:13.500> like<00:45:14.099> come<00:45:14.339> find<00:45:14.640> me<00:45:14.819> and<00:45:15.359> I 00:45:15.470 --> 00:45:15.480 align:start position:0% something new like come find me and I 00:45:15.480 --> 00:45:17.450 align:start position:0% something new like come find me and I will<00:45:15.599> try<00:45:15.780> to<00:45:15.900> help<00:45:16.140> you<00:45:16.380> get<00:45:16.859> started<00:45:17.220> with 00:45:17.450 --> 00:45:17.460 align:start position:0% will try to help you get started with 00:45:17.460 --> 00:45:20.030 align:start position:0% will try to help you get started with this<00:45:17.640> whole<00:45:17.819> thing<00:45:18.020> and<00:45:19.020> the<00:45:19.140> goal<00:45:19.440> is<00:45:19.619> make 00:45:20.030 --> 00:45:20.040 align:start position:0% this whole thing and the goal is make 00:45:20.040 --> 00:45:21.349 align:start position:0% this whole thing and the goal is make this<00:45:20.220> accessible<00:45:20.520> to<00:45:20.760> the<00:45:20.880> average<00:45:21.060> person 00:45:21.349 --> 00:45:21.359 align:start position:0% this accessible to the average person 00:45:21.359 --> 00:45:24.050 align:start position:0% this accessible to the average person who<00:45:22.079> just<00:45:22.319> you<00:45:22.740> know<00:45:22.800> doesn't<00:45:23.099> want<00:45:23.460> to<00:45:23.640> under 00:45:24.050 --> 00:45:24.060 align:start position:0% who just you know doesn't want to under 00:45:24.060 --> 00:45:25.790 align:start position:0% who just you know doesn't want to under doesn't<00:45:24.420> want<00:45:24.660> to<00:45:24.780> deeply<00:45:25.079> understand<00:45:25.319> how 00:45:25.790 --> 00:45:25.800 align:start position:0% doesn't want to deeply understand how 00:45:25.800 --> 00:45:27.950 align:start position:0% doesn't want to deeply understand how this<00:45:25.920> whole<00:45:26.040> architecture<00:45:26.579> Works 00:45:27.950 --> 00:45:27.960 align:start position:0% this whole architecture Works 00:45:27.960 --> 00:45:30.410 align:start position:0% this whole architecture Works um<00:45:28.380> so<00:45:29.099> that's<00:45:29.400> me<00:45:29.640> I'm<00:45:29.819> going<00:45:29.940> to<00:45:30.000> hand<00:45:30.119> it<00:45:30.300> off 00:45:30.410 --> 00:45:30.420 align:start position:0% um so that's me I'm going to hand it off 00:45:30.420 --> 00:45:32.930 align:start position:0% um so that's me I'm going to hand it off now<00:45:30.900> all<00:45:31.680> right 00:45:32.930 --> 00:45:32.940 align:start position:0% now all right 00:45:32.940 --> 00:45:36.170 align:start position:0% now all right all<00:45:33.359> right<00:45:33.599> cool<00:45:33.780> three<00:45:34.440> minutes<00:45:34.680> left 00:45:36.170 --> 00:45:36.180 align:start position:0% all right cool three minutes left 00:45:36.180 --> 00:45:36.770 align:start position:0% all right cool three minutes left um 00:45:36.770 --> 00:45:36.780 align:start position:0% um 00:45:36.780 --> 00:45:39.950 align:start position:0% um announcement<00:45:37.500> time<00:45:37.880> announcement<00:45:38.880> time<00:45:39.119> so 00:45:39.950 --> 00:45:39.960 align:start position:0% announcement time announcement time so 00:45:39.960 --> 00:45:42.230 align:start position:0% announcement time announcement time so just<00:45:40.500> like<00:45:40.680> the<00:45:40.800> op<00:45:40.920> stack<00:45:41.400> is<00:45:41.579> meant<00:45:41.819> to<00:45:41.940> like 00:45:42.230 --> 00:45:42.240 align:start position:0% just like the op stack is meant to like 00:45:42.240 --> 00:45:45.290 align:start position:0% just like the op stack is meant to like essentially<00:45:43.200> increase<00:45:43.500> pluralism<00:45:44.280> by<00:45:44.940> making 00:45:45.290 --> 00:45:45.300 align:start position:0% essentially increase pluralism by making 00:45:45.300 --> 00:45:46.849 align:start position:0% essentially increase pluralism by making something<00:45:45.540> free<00:45:45.839> and<00:45:46.079> open<00:45:46.260> source<00:45:46.619> and<00:45:46.680> easy 00:45:46.849 --> 00:45:46.859 align:start position:0% something free and open source and easy 00:45:46.859 --> 00:45:48.349 align:start position:0% something free and open source and easy to<00:45:47.040> use<00:45:47.220> we<00:45:47.700> kind<00:45:47.819> of<00:45:47.880> did<00:45:48.060> the<00:45:48.180> same<00:45:48.240> thing 00:45:48.349 --> 00:45:48.359 align:start position:0% to use we kind of did the same thing 00:45:48.359 --> 00:45:51.170 align:start position:0% to use we kind of did the same thing with<00:45:48.540> Mod<00:45:48.720> mud<00:45:49.200> is<00:45:49.319> MIT<00:45:49.560> licensed<00:45:50.220> at<00:45:51.000> soft 00:45:51.170 --> 00:45:51.180 align:start position:0% with Mod mud is MIT licensed at soft 00:45:51.180 --> 00:45:53.089 align:start position:0% with Mod mud is MIT licensed at soft launch<00:45:51.540> today<00:45:51.720> and<00:45:52.319> to<00:45:52.560> kind<00:45:52.680> of<00:45:52.800> like<00:45:52.859> pave 00:45:53.089 --> 00:45:53.099 align:start position:0% launch today and to kind of like pave 00:45:53.099 --> 00:45:54.650 align:start position:0% launch today and to kind of like pave the<00:45:53.220> way<00:45:53.400> forward 00:45:54.650 --> 00:45:54.660 align:start position:0% the way forward 00:45:54.660 --> 00:45:56.329 align:start position:0% the way forward um that<00:45:55.260> is<00:45:55.440> an<00:45:55.560> optimism<00:45:55.859> have<00:45:56.040> been<00:45:56.160> working 00:45:56.329 --> 00:45:56.339 align:start position:0% um that is an optimism have been working 00:45:56.339 --> 00:45:58.130 align:start position:0% um that is an optimism have been working together<00:45:56.520> over<00:45:56.819> the<00:45:57.060> last<00:45:57.240> month<00:45:57.720> and<00:45:57.900> a<00:45:58.079> half 00:45:58.130 --> 00:45:58.140 align:start position:0% together over the last month and a half 00:45:58.140 --> 00:46:00.770 align:start position:0% together over the last month and a half on<00:45:58.980> an<00:45:59.099> autonomous<00:45:59.460> world<00:45:59.700> that 00:46:00.770 --> 00:46:00.780 align:start position:0% on an autonomous world that 00:46:00.780 --> 00:46:02.809 align:start position:0% on an autonomous world that was<00:46:01.319> built<00:46:01.619> on<00:46:01.680> mud<00:46:01.920> and<00:46:02.280> runs<00:46:02.520> on<00:46:02.579> the<00:46:02.700> op 00:46:02.809 --> 00:46:02.819 align:start position:0% was built on mud and runs on the op 00:46:02.819 --> 00:46:04.670 align:start position:0% was built on mud and runs on the op stack<00:46:03.240> so 00:46:04.670 --> 00:46:04.680 align:start position:0% stack so 00:46:04.680 --> 00:46:07.069 align:start position:0% stack so we're<00:46:05.160> like<00:46:05.460> pretty<00:46:05.819> excited<00:46:06.359> to<00:46:06.839> show 00:46:07.069 --> 00:46:07.079 align:start position:0% we're like pretty excited to show 00:46:07.079 --> 00:46:10.190 align:start position:0% we're like pretty excited to show opicraft<00:46:07.680> to<00:46:07.920> everybody<00:46:08.119> it's<00:46:09.119> a<00:46:09.420> 3D<00:46:09.780> voxel 00:46:10.190 --> 00:46:10.200 align:start position:0% opicraft to everybody it's a 3D voxel 00:46:10.200 --> 00:46:12.950 align:start position:0% opicraft to everybody it's a 3D voxel game<00:46:10.440> powered<00:46:11.099> by<00:46:11.160> mud<00:46:11.520> running<00:46:12.060> on<00:46:12.420> a<00:46:12.660> crazy 00:46:12.950 --> 00:46:12.960 align:start position:0% game powered by mud running on a crazy 00:46:12.960 --> 00:46:17.750 align:start position:0% game powered by mud running on a crazy to<00:46:13.319> generate<00:46:13.619> op<00:46:13.859> chain<00:46:14.300> uh<00:46:15.300> yeah 00:46:17.750 --> 00:46:17.760 align:start position:0% to generate op chain uh yeah 00:46:17.760 --> 00:46:20.329 align:start position:0% to generate op chain uh yeah I<00:46:18.180> even<00:46:18.300> have<00:46:18.599> a<00:46:18.839> video<00:46:19.020> well<00:46:19.619> I<00:46:19.920> will<00:46:20.040> see<00:46:20.220> if 00:46:20.329 --> 00:46:20.339 align:start position:0% I even have a video well I will see if 00:46:20.339 --> 00:46:21.829 align:start position:0% I even have a video well I will see if it<00:46:20.460> plays<00:46:20.760> but<00:46:20.940> Alvarez<00:46:21.420> and<00:46:21.540> I<00:46:21.660> yesterday 00:46:21.829 --> 00:46:21.839 align:start position:0% it plays but Alvarez and I yesterday 00:46:21.839 --> 00:46:24.109 align:start position:0% it plays but Alvarez and I yesterday were<00:46:22.079> trying<00:46:22.319> to<00:46:22.380> build<00:46:22.560> the<00:46:22.740> house<00:46:22.980> so<00:46:23.940> yeah 00:46:24.109 --> 00:46:24.119 align:start position:0% were trying to build the house so yeah 00:46:24.119 --> 00:46:26.870 align:start position:0% were trying to build the house so yeah that's<00:46:24.540> that's<00:46:24.960> uh<00:46:25.619> that's<00:46:26.099> running<00:46:26.220> on<00:46:26.460> DVM 00:46:26.870 --> 00:46:26.880 align:start position:0% that's that's uh that's running on DVM 00:46:26.880 --> 00:46:27.730 align:start position:0% that's that's uh that's running on DVM guys 00:46:27.730 --> 00:46:27.740 align:start position:0% guys 00:46:27.740 --> 00:46:30.470 align:start position:0% guys it's<00:46:28.740> it's<00:46:28.980> a<00:46:29.280> procedurally<00:46:29.760> generated<00:46:30.180> world 00:46:30.470 --> 00:46:30.480 align:start position:0% it's it's a procedurally generated world 00:46:30.480 --> 00:46:32.150 align:start position:0% it's it's a procedurally generated world I<00:46:31.079> can't<00:46:31.200> wait<00:46:31.380> to<00:46:31.560> see<00:46:31.619> what<00:46:31.740> people<00:46:31.859> will<00:46:32.040> do 00:46:32.150 --> 00:46:32.160 align:start position:0% I can't wait to see what people will do 00:46:32.160 --> 00:46:33.950 align:start position:0% I can't wait to see what people will do with<00:46:32.339> that<00:46:32.460> you<00:46:32.700> can<00:46:32.880> deploy<00:46:33.180> marketplaces 00:46:33.950 --> 00:46:33.960 align:start position:0% with that you can deploy marketplaces 00:46:33.960 --> 00:46:36.349 align:start position:0% with that you can deploy marketplaces oracles<00:46:34.680> extend<00:46:35.460> it<00:46:35.579> build<00:46:35.819> augmented 00:46:36.349 --> 00:46:36.359 align:start position:0% oracles extend it build augmented 00:46:36.359 --> 00:46:38.690 align:start position:0% oracles extend it build augmented reality<00:46:36.780> tennis<00:46:37.440> capitalism<00:46:38.040> whatever<00:46:38.400> you 00:46:38.690 --> 00:46:38.700 align:start position:0% reality tennis capitalism whatever you 00:46:38.700 --> 00:46:39.890 align:start position:0% reality tennis capitalism whatever you want 00:46:39.890 --> 00:46:39.900 align:start position:0% want 00:46:39.900 --> 00:46:41.270 align:start position:0% want um<00:46:39.960> it's<00:46:40.260> going<00:46:40.380> to<00:46:40.440> be<00:46:40.560> open<00:46:40.680> source<00:46:41.099> soon 00:46:41.270 --> 00:46:41.280 align:start position:0% um it's going to be open source soon 00:46:41.280 --> 00:46:43.309 align:start position:0% um it's going to be open source soon it's<00:46:41.880> playable<00:46:42.180> today 00:46:43.309 --> 00:46:43.319 align:start position:0% it's playable today 00:46:43.319 --> 00:46:43.910 align:start position:0% it's playable today um 00:46:43.910 --> 00:46:43.920 align:start position:0% um 00:46:43.920 --> 00:46:45.950 align:start position:0% um let's<00:46:44.520> let's<00:46:44.700> let's<00:46:44.760> let's<00:46:44.940> actually<00:46:45.540> see<00:46:45.780> how 00:46:45.950 --> 00:46:45.960 align:start position:0% let's let's let's let's actually see how 00:46:45.960 --> 00:46:47.450 align:start position:0% let's let's let's let's actually see how we<00:46:46.079> built<00:46:46.319> the<00:46:46.380> house<00:46:46.560> I<00:46:46.859> remember<00:46:46.980> it<00:46:47.280> was 00:46:47.450 --> 00:46:47.460 align:start position:0% we built the house I remember it was 00:46:47.460 --> 00:46:50.210 align:start position:0% we built the house I remember it was quite<00:46:47.819> quite<00:46:48.180> hard<00:46:48.359> given<00:46:49.020> we<00:46:49.200> didn't<00:46:49.980> really 00:46:50.210 --> 00:46:50.220 align:start position:0% quite quite hard given we didn't really 00:46:50.220 --> 00:46:51.829 align:start position:0% quite quite hard given we didn't really have<00:46:50.400> consensus<00:46:50.880> on<00:46:51.000> how<00:46:51.240> to<00:46:51.359> how<00:46:51.599> it<00:46:51.720> should 00:46:51.829 --> 00:46:51.839 align:start position:0% have consensus on how to how it should 00:46:51.839 --> 00:47:02.450 align:start position:0% have consensus on how to how it should look<00:46:52.020> like 00:47:02.450 --> 00:47:02.460 align:start position:0% 00:47:02.460 --> 00:47:06.470 align:start position:0% yeah<00:47:03.300> okay<00:47:03.720> cool<00:47:04.220> we<00:47:05.220> did<00:47:05.460> it 00:47:06.470 --> 00:47:06.480 align:start position:0% yeah okay cool we did it 00:47:06.480 --> 00:47:08.569 align:start position:0% yeah okay cool we did it um 00:47:08.569 --> 00:47:08.579 align:start position:0% um 00:47:08.579 --> 00:47:11.089 align:start position:0% um opicraft<00:47:09.359> is<00:47:09.720> gonna<00:47:09.900> be<00:47:10.079> soft<00:47:10.500> launch<00:47:10.859> and 00:47:11.089 --> 00:47:11.099 align:start position:0% opicraft is gonna be soft launch and 00:47:11.099 --> 00:47:12.890 align:start position:0% opicraft is gonna be soft launch and playable<00:47:11.460> at<00:47:11.700> the<00:47:11.880> autonomous<00:47:12.240> World<00:47:12.420> Arcade 00:47:12.890 --> 00:47:12.900 align:start position:0% playable at the autonomous World Arcade 00:47:12.900 --> 00:47:15.050 align:start position:0% playable at the autonomous World Arcade at<00:47:13.140> 4<00:47:13.260> pm<00:47:13.500> today<00:47:13.680> at<00:47:13.859> the<00:47:13.920> hacker<00:47:14.220> basement<00:47:14.339> so 00:47:15.050 --> 00:47:15.060 align:start position:0% at 4 pm today at the hacker basement so 00:47:15.060 --> 00:47:16.849 align:start position:0% at 4 pm today at the hacker basement so if<00:47:15.180> you<00:47:15.359> want<00:47:15.420> to<00:47:15.599> play<00:47:15.660> it<00:47:16.319> um<00:47:16.380> come<00:47:16.619> there 00:47:16.849 --> 00:47:16.859 align:start position:0% if you want to play it um come there 00:47:16.859 --> 00:47:18.349 align:start position:0% if you want to play it um come there additionally<00:47:17.640> we're<00:47:17.940> going<00:47:18.060> to<00:47:18.119> have<00:47:18.180> a 00:47:18.349 --> 00:47:18.359 align:start position:0% additionally we're going to have a 00:47:18.359 --> 00:47:20.569 align:start position:0% additionally we're going to have a tournament<00:47:18.599> of<00:47:18.720> skyscribe<00:47:19.380> which<00:47:19.560> is<00:47:19.740> the<00:47:20.099> RTS 00:47:20.569 --> 00:47:20.579 align:start position:0% tournament of skyscribe which is the RTS 00:47:20.579 --> 00:47:22.250 align:start position:0% tournament of skyscribe which is the RTS that<00:47:20.700> was<00:47:20.819> built<00:47:21.060> with<00:47:21.119> Mod<00:47:21.300> uh<00:47:21.960> we<00:47:22.140> have 00:47:22.250 --> 00:47:22.260 align:start position:0% that was built with Mod uh we have 00:47:22.260 --> 00:47:23.930 align:start position:0% that was built with Mod uh we have playlisted<00:47:22.740> it<00:47:22.859> weekly<00:47:23.220> for<00:47:23.460> like<00:47:23.640> the<00:47:23.760> last 00:47:23.930 --> 00:47:23.940 align:start position:0% playlisted it weekly for like the last 00:47:23.940 --> 00:47:25.550 align:start position:0% playlisted it weekly for like the last month<00:47:24.119> people<00:47:24.420> really<00:47:24.720> like<00:47:24.900> it<00:47:25.079> there<00:47:25.380> are 00:47:25.550 --> 00:47:25.560 align:start position:0% month people really like it there are 00:47:25.560 --> 00:47:27.290 align:start position:0% month people really like it there are Starcraft<00:47:25.800> players<00:47:26.160> that<00:47:26.400> don't<00:47:26.640> even<00:47:26.760> know 00:47:27.290 --> 00:47:27.300 align:start position:0% Starcraft players that don't even know 00:47:27.300 --> 00:47:28.550 align:start position:0% Starcraft players that don't even know that<00:47:27.540> it's<00:47:27.660> running<00:47:27.780> on<00:47:28.020> chain<00:47:28.200> they<00:47:28.440> just 00:47:28.550 --> 00:47:28.560 align:start position:0% that it's running on chain they just 00:47:28.560 --> 00:47:30.950 align:start position:0% that it's running on chain they just like<00:47:28.680> the<00:47:28.859> game<00:47:29.040> so<00:47:29.880> yeah<00:47:30.240> we're<00:47:30.420> gonna<00:47:30.599> try<00:47:30.839> to 00:47:30.950 --> 00:47:30.960 align:start position:0% like the game so yeah we're gonna try to 00:47:30.960 --> 00:47:32.930 align:start position:0% like the game so yeah we're gonna try to hit<00:47:31.079> 64<00:47:31.500> players<00:47:31.859> so<00:47:32.160> come<00:47:32.400> along<00:47:32.579> as<00:47:32.819> well 00:47:32.930 --> 00:47:32.940 align:start position:0% hit 64 players so come along as well 00:47:32.940 --> 00:47:35.750 align:start position:0% hit 64 players so come along as well hacker<00:47:33.420> basement<00:47:33.540> 4pm<00:47:34.319> so<00:47:35.160> what<00:47:35.400> about<00:47:35.579> the 00:47:35.750 --> 00:47:35.760 align:start position:0% hacker basement 4pm so what about the 00:47:35.760 --> 00:47:37.309 align:start position:0% hacker basement 4pm so what about the other<00:47:35.880> stuff<00:47:36.119> well<00:47:36.300> mud<00:47:36.660> is<00:47:36.900> actually<00:47:37.079> already 00:47:37.309 --> 00:47:37.319 align:start position:0% other stuff well mud is actually already 00:47:37.319 --> 00:47:38.930 align:start position:0% other stuff well mud is actually already available<00:47:37.560> we<00:47:38.040> just<00:47:38.220> don't<00:47:38.520> really<00:47:38.700> talk 00:47:38.930 --> 00:47:38.940 align:start position:0% available we just don't really talk 00:47:38.940 --> 00:47:39.890 align:start position:0% available we just don't really talk about<00:47:39.060> it<00:47:39.240> because<00:47:39.420> it's<00:47:39.599> not<00:47:39.720> very 00:47:39.890 --> 00:47:39.900 align:start position:0% about it because it's not very 00:47:39.900 --> 00:47:42.950 align:start position:0% about it because it's not very documented<00:47:40.560> it's<00:47:40.980> like<00:47:41.160> the<00:47:41.280> op<00:47:41.400> stack<00:47:41.940> it's<00:47:42.780> a 00:47:42.950 --> 00:47:42.960 align:start position:0% documented it's like the op stack it's a 00:47:42.960 --> 00:47:46.010 align:start position:0% documented it's like the op stack it's a mud.dev<00:47:44.040> um<00:47:44.160> the<00:47:44.400> code<00:47:44.520> is<00:47:44.700> on<00:47:44.819> GitHub 00:47:46.010 --> 00:47:46.020 align:start position:0% mud.dev um the code is on GitHub 00:47:46.020 --> 00:47:46.730 align:start position:0% mud.dev um the code is on GitHub um 00:47:46.730 --> 00:47:46.740 align:start position:0% um 00:47:46.740 --> 00:47:48.589 align:start position:0% um we<00:47:47.400> have<00:47:47.520> a<00:47:47.640> bunch<00:47:47.760> of<00:47:47.880> teams<00:47:48.180> building<00:47:48.359> stuff 00:47:48.589 --> 00:47:48.599 align:start position:0% we have a bunch of teams building stuff 00:47:48.599 --> 00:47:50.809 align:start position:0% we have a bunch of teams building stuff with<00:47:48.780> it<00:47:48.900> but<00:47:49.200> it's<00:47:49.440> it's<00:47:49.680> yeah<00:47:49.980> talk<00:47:50.280> to<00:47:50.520> me<00:47:50.640> if 00:47:50.809 --> 00:47:50.819 align:start position:0% with it but it's it's yeah talk to me if 00:47:50.819 --> 00:47:52.609 align:start position:0% with it but it's it's yeah talk to me if if<00:47:51.060> you're<00:47:51.240> interested 00:47:52.609 --> 00:47:52.619 align:start position:0% if you're interested 00:47:52.619 --> 00:47:55.609 align:start position:0% if you're interested um the<00:47:52.920> op<00:47:53.099> stack<00:47:53.579> is<00:47:54.240> going<00:47:54.960> to<00:47:55.140> be<00:47:55.200> announced 00:47:55.609 --> 00:47:55.619 align:start position:0% um the op stack is going to be announced 00:47:55.619 --> 00:47:58.250 align:start position:0% um the op stack is going to be announced soon<00:47:55.740> by<00:47:56.460> Carl<00:47:56.700> at<00:47:57.060> 1<00:47:57.240> 30<00:47:57.359> pm<00:47:57.720> on<00:47:58.020> the<00:47:58.140> main 00:47:58.250 --> 00:47:58.260 align:start position:0% soon by Carl at 1 30 pm on the main 00:47:58.260 --> 00:47:59.390 align:start position:0% soon by Carl at 1 30 pm on the main stage 00:47:59.390 --> 00:47:59.400 align:start position:0% stage 00:47:59.400 --> 00:48:03.200 align:start position:0% stage um<00:47:59.520> and<00:48:00.119> yeah<00:48:00.240> that's<00:48:00.480> us<00:48:00.660> thank<00:48:00.960> you<00:48:01.079> guys