WEBVTT Kind: captions Language: en 00:00:01.010 --> 00:00:09.110 align:start position:0% [Music] 00:00:09.110 --> 00:00:09.120 align:start position:0% [Music] 00:00:09.120 --> 00:00:10.030 align:start position:0% [Music] my<00:00:09.240> name<00:00:09.360> is 00:00:10.030 --> 00:00:10.040 align:start position:0% my name is 00:00:10.040 --> 00:00:13.070 align:start position:0% my name is alvarius<00:00:11.040> and<00:00:12.000> I<00:00:12.080> have<00:00:12.240> the<00:00:12.400> honor<00:00:12.719> of<00:00:12.840> doing 00:00:13.070 --> 00:00:13.080 align:start position:0% alvarius and I have the honor of doing 00:00:13.080 --> 00:00:15.749 align:start position:0% alvarius and I have the honor of doing the<00:00:13.160> intro<00:00:13.480> keino<00:00:13.799> today<00:00:14.639> and<00:00:14.839> I'm<00:00:14.960> gonna<00:00:15.480> talk 00:00:15.749 --> 00:00:15.759 align:start position:0% the intro keino today and I'm gonna talk 00:00:15.759 --> 00:00:17.870 align:start position:0% the intro keino today and I'm gonna talk about<00:00:16.080> the<00:00:16.320> past<00:00:16.760> the<00:00:16.920> present<00:00:17.480> and<00:00:17.760> the 00:00:17.870 --> 00:00:17.880 align:start position:0% about the past the present and the 00:00:17.880 --> 00:00:20.390 align:start position:0% about the past the present and the future<00:00:18.600> of<00:00:18.760> mut<00:00:19.640> um<00:00:19.760> some<00:00:19.880> of<00:00:20.000> you<00:00:20.119> might<00:00:20.279> have 00:00:20.390 --> 00:00:20.400 align:start position:0% future of mut um some of you might have 00:00:20.400 --> 00:00:22.269 align:start position:0% future of mut um some of you might have lived<00:00:20.720> through<00:00:20.960> the<00:00:21.160> past<00:00:21.400> of<00:00:21.519> mut<00:00:21.880> with<00:00:22.039> us 00:00:22.269 --> 00:00:22.279 align:start position:0% lived through the past of mut with us 00:00:22.279 --> 00:00:23.589 align:start position:0% lived through the past of mut with us and<00:00:22.439> some<00:00:22.600> of<00:00:22.720> you<00:00:22.880> might<00:00:23.039> have<00:00:23.240> just 00:00:23.589 --> 00:00:23.599 align:start position:0% and some of you might have just 00:00:23.599 --> 00:00:25.509 align:start position:0% and some of you might have just discovered<00:00:23.840> mut<00:00:24.160> so<00:00:24.720> after<00:00:25.000> this<00:00:25.160> hopefully 00:00:25.509 --> 00:00:25.519 align:start position:0% discovered mut so after this hopefully 00:00:25.519 --> 00:00:30.310 align:start position:0% discovered mut so after this hopefully all<00:00:25.640> of<00:00:25.720> you<00:00:25.840> should<00:00:26.039> have<00:00:26.199> the<00:00:26.320> same<00:00:26.599> context 00:00:30.310 --> 00:00:30.320 align:start position:0% 00:00:30.320 --> 00:00:32.589 align:start position:0% past<00:00:30.640> present<00:00:30.880> and<00:00:31.039> future<00:00:31.279> of<00:00:31.439> mud<00:00:31.759> or<00:00:32.320> with 00:00:32.589 --> 00:00:32.599 align:start position:0% past present and future of mud or with 00:00:32.599 --> 00:00:35.630 align:start position:0% past present and future of mud or with the<00:00:33.040> words<00:00:33.320> of<00:00:33.480> Kent<00:00:33.760> Beck<00:00:34.440> make<00:00:34.600> it<00:00:34.760> work<00:00:35.520> make 00:00:35.630 --> 00:00:35.640 align:start position:0% the words of Kent Beck make it work make 00:00:35.640 --> 00:00:37.709 align:start position:0% the words of Kent Beck make it work make it<00:00:35.840> right<00:00:36.239> and<00:00:36.360> then<00:00:36.520> make<00:00:36.680> it<00:00:36.840> fast<00:00:37.239> it<00:00:37.440> fits 00:00:37.709 --> 00:00:37.719 align:start position:0% it right and then make it fast it fits 00:00:37.719 --> 00:00:39.549 align:start position:0% it right and then make it fast it fits surprisingly<00:00:38.399> well<00:00:38.600> to<00:00:38.760> the<00:00:39.000> phases<00:00:39.360> or 00:00:39.549 --> 00:00:39.559 align:start position:0% surprisingly well to the phases or 00:00:39.559 --> 00:00:41.790 align:start position:0% surprisingly well to the phases or chapters<00:00:39.960> that<00:00:40.120> mut<00:00:40.399> went<00:00:40.559> through<00:00:41.360> um<00:00:41.480> so<00:00:41.680> I 00:00:41.790 --> 00:00:41.800 align:start position:0% chapters that mut went through um so I 00:00:41.800 --> 00:00:43.910 align:start position:0% chapters that mut went through um so I thought<00:00:42.079> I'd<00:00:42.559> I'd<00:00:42.719> structure<00:00:43.320> the<00:00:43.480> talk<00:00:43.719> like 00:00:43.910 --> 00:00:43.920 align:start position:0% thought I'd I'd structure the talk like 00:00:43.920 --> 00:00:45.910 align:start position:0% thought I'd I'd structure the talk like that<00:00:44.760> um<00:00:44.920> so<00:00:45.039> we<00:00:45.160> start<00:00:45.399> with<00:00:45.520> the<00:00:45.640> first 00:00:45.910 --> 00:00:45.920 align:start position:0% that um so we start with the first 00:00:45.920 --> 00:00:48.510 align:start position:0% that um so we start with the first chapter<00:00:46.559> make<00:00:46.760> it 00:00:48.510 --> 00:00:48.520 align:start position:0% chapter make it 00:00:48.520 --> 00:00:50.750 align:start position:0% chapter make it work<00:00:49.520> it<00:00:49.680> started<00:00:50.079> basically<00:00:50.440> three<00:00:50.600> and<00:00:50.680> a 00:00:50.750 --> 00:00:50.760 align:start position:0% work it started basically three and a 00:00:50.760 --> 00:00:53.510 align:start position:0% work it started basically three and a half<00:00:50.920> years<00:00:51.120> ago<00:00:51.600> when<00:00:52.160> Justin<00:00:52.520> and<00:00:52.719> I<00:00:53.160> um<00:00:53.320> got 00:00:53.510 --> 00:00:53.520 align:start position:0% half years ago when Justin and I um got 00:00:53.520 --> 00:00:55.709 align:start position:0% half years ago when Justin and I um got really<00:00:53.719> inspired<00:00:54.239> by<00:00:54.399> Dark<00:00:54.640> Forest<00:00:55.520> and 00:00:55.709 --> 00:00:55.719 align:start position:0% really inspired by Dark Forest and 00:00:55.719 --> 00:00:57.910 align:start position:0% really inspired by Dark Forest and decided<00:00:56.039> to<00:00:56.199> build<00:00:56.640> our<00:00:56.840> own<00:00:57.039> fully<00:00:57.320> onchain 00:00:57.910 --> 00:00:57.920 align:start position:0% decided to build our own fully onchain 00:00:57.920 --> 00:01:01.709 align:start position:0% decided to build our own fully onchain game<00:00:58.920> and<00:00:59.120> so<00:00:59.719> this<00:01:00.000> this<00:01:00.120> was<00:01:01.000> a<00:01:01.160> very<00:01:01.399> early 00:01:01.709 --> 00:01:01.719 align:start position:0% game and so this this was a very early 00:01:01.719 --> 00:01:03.670 align:start position:0% game and so this this was a very early version<00:01:02.039> of<00:01:02.199> what<00:01:02.320> we<00:01:02.399> started<00:01:02.719> building<00:01:03.359> um 00:01:03.670 --> 00:01:03.680 align:start position:0% version of what we started building um 00:01:03.680 --> 00:01:06.030 align:start position:0% version of what we started building um back<00:01:03.840> then<00:01:03.960> it<00:01:04.040> was<00:01:04.199> called<00:01:04.400> ZK<00:01:04.799> dungeon<00:01:05.680> we 00:01:06.030 --> 00:01:06.040 align:start position:0% back then it was called ZK dungeon we 00:01:06.040 --> 00:01:07.789 align:start position:0% back then it was called ZK dungeon we quickly<00:01:06.400> removed<00:01:06.799> all<00:01:06.920> the<00:01:07.040> ZK<00:01:07.479> from<00:01:07.640> it 00:01:07.789 --> 00:01:07.799 align:start position:0% quickly removed all the ZK from it 00:01:07.799 --> 00:01:09.109 align:start position:0% quickly removed all the ZK from it because<00:01:08.080> it<00:01:08.240> actually<00:01:08.400> didn't<00:01:08.640> really<00:01:08.840> matter 00:01:09.109 --> 00:01:09.119 align:start position:0% because it actually didn't really matter 00:01:09.119 --> 00:01:11.149 align:start position:0% because it actually didn't really matter for<00:01:09.320> the<00:01:09.479> for<00:01:09.640> the<00:01:09.759> game<00:01:09.960> mechanics<00:01:10.880> um<00:01:11.000> but 00:01:11.149 --> 00:01:11.159 align:start position:0% for the for the game mechanics um but 00:01:11.159 --> 00:01:13.550 align:start position:0% for the for the game mechanics um but the<00:01:11.320> game<00:01:11.880> the<00:01:12.000> name<00:01:12.200> stuck<00:01:12.520> for<00:01:12.640> a<00:01:12.759> little 00:01:13.550 --> 00:01:13.560 align:start position:0% the game the name stuck for a little 00:01:13.560 --> 00:01:17.149 align:start position:0% the game the name stuck for a little bit<00:01:14.560> and<00:01:14.759> then<00:01:15.000> after<00:01:15.280> around<00:01:15.560> six<00:01:15.799> months<00:01:16.640> um 00:01:17.149 --> 00:01:17.159 align:start position:0% bit and then after around six months um 00:01:17.159 --> 00:01:19.910 align:start position:0% bit and then after around six months um we<00:01:17.360> had<00:01:17.960> this<00:01:18.600> all<00:01:18.720> the<00:01:18.840> game<00:01:19.080> mechanics<00:01:19.439> were 00:01:19.910 --> 00:01:19.920 align:start position:0% we had this all the game mechanics were 00:01:19.920 --> 00:01:23.270 align:start position:0% we had this all the game mechanics were really<00:01:20.200> polished<00:01:21.200> um<00:01:21.400> all<00:01:21.680> the<00:01:22.439> all<00:01:22.680> the<00:01:22.880> UI 00:01:23.270 --> 00:01:23.280 align:start position:0% really polished um all the all the UI 00:01:23.280 --> 00:01:25.749 align:start position:0% really polished um all the all the UI was<00:01:23.439> really<00:01:23.640> polished<00:01:24.119> polished<00:01:24.479> as<00:01:24.640> well<00:01:25.479> um 00:01:25.749 --> 00:01:25.759 align:start position:0% was really polished polished as well um 00:01:25.759 --> 00:01:27.950 align:start position:0% was really polished polished as well um but<00:01:25.920> we<00:01:26.040> made<00:01:26.400> one<00:01:26.600> big<00:01:26.840> mistake<00:01:27.400> which<00:01:27.600> was<00:01:27.799> we 00:01:27.950 --> 00:01:27.960 align:start position:0% but we made one big mistake which was we 00:01:27.960 --> 00:01:29.630 align:start position:0% but we made one big mistake which was we didn't<00:01:28.159> really<00:01:28.320> do<00:01:28.479> any<00:01:28.680> play<00:01:29.000> tests<00:01:29.360> until 00:01:29.630 --> 00:01:29.640 align:start position:0% didn't really do any play tests until 00:01:29.640 --> 00:01:31.789 align:start position:0% didn't really do any play tests until then<00:01:30.280> we<00:01:30.560> really<00:01:30.759> only<00:01:31.040> played<00:01:31.400> with<00:01:31.520> the<00:01:31.640> two 00:01:31.789 --> 00:01:31.799 align:start position:0% then we really only played with the two 00:01:31.799 --> 00:01:33.910 align:start position:0% then we really only played with the two of<00:01:31.960> us<00:01:32.280> we<00:01:32.399> thought<00:01:32.600> it's<00:01:32.799> fun<00:01:33.399> and<00:01:33.560> maybe<00:01:33.799> with 00:01:33.910 --> 00:01:33.920 align:start position:0% of us we thought it's fun and maybe with 00:01:33.920 --> 00:01:35.670 align:start position:0% of us we thought it's fun and maybe with a<00:01:34.040> couple<00:01:34.280> of<00:01:34.439> people<00:01:34.720> from<00:01:34.920> The<00:01:35.079> Dark<00:01:35.280> Forest 00:01:35.670 --> 00:01:35.680 align:start position:0% a couple of people from The Dark Forest 00:01:35.680 --> 00:01:37.270 align:start position:0% a couple of people from The Dark Forest office<00:01:36.000> where<00:01:36.119> we<00:01:36.240> were<00:01:36.439> working<00:01:36.759> from<00:01:37.000> at<00:01:37.119> the 00:01:37.270 --> 00:01:37.280 align:start position:0% office where we were working from at the 00:01:37.280 --> 00:01:39.910 align:start position:0% office where we were working from at the time<00:01:38.240> um<00:01:38.479> but<00:01:38.600> yeah<00:01:38.720> we<00:01:38.920> never<00:01:39.119> did<00:01:39.320> any<00:01:39.520> larger 00:01:39.910 --> 00:01:39.920 align:start position:0% time um but yeah we never did any larger 00:01:39.920 --> 00:01:42.429 align:start position:0% time um but yeah we never did any larger scale<00:01:40.200> play<00:01:40.439> tests<00:01:40.799> and<00:01:40.920> so<00:01:41.840> when<00:01:41.960> we<00:01:42.079> did<00:01:42.240> our 00:01:42.429 --> 00:01:42.439 align:start position:0% scale play tests and so when we did our 00:01:42.439 --> 00:01:44.830 align:start position:0% scale play tests and so when we did our first<00:01:42.640> larger<00:01:42.960> scale<00:01:43.280> play<00:01:43.560> test<00:01:44.360> um<00:01:44.560> after 00:01:44.830 --> 00:01:44.840 align:start position:0% first larger scale play test um after 00:01:44.840 --> 00:01:46.670 align:start position:0% first larger scale play test um after like<00:01:45.000> six<00:01:45.240> months<00:01:45.960> we<00:01:46.079> realized<00:01:46.479> it's 00:01:46.670 --> 00:01:46.680 align:start position:0% like six months we realized it's 00:01:46.680 --> 00:01:48.990 align:start position:0% like six months we realized it's actually<00:01:46.920> not<00:01:47.159> as<00:01:47.360> fun<00:01:47.719> as<00:01:47.840> we<00:01:48.000> thought<00:01:48.719> and<00:01:48.840> so 00:01:48.990 --> 00:01:49.000 align:start position:0% actually not as fun as we thought and so 00:01:49.000 --> 00:01:50.469 align:start position:0% actually not as fun as we thought and so lesson<00:01:49.280> learned<00:01:49.560> you<00:01:49.640> should<00:01:49.840> do<00:01:50.040> play<00:01:50.240> tests 00:01:50.469 --> 00:01:50.479 align:start position:0% lesson learned you should do play tests 00:01:50.479 --> 00:01:53.429 align:start position:0% lesson learned you should do play tests early<00:01:50.759> and<00:01:50.920> iterate<00:01:51.360> based<00:01:51.560> on<00:01:51.799> that<00:01:52.719> um<00:01:53.280> we 00:01:53.429 --> 00:01:53.439 align:start position:0% early and iterate based on that um we 00:01:53.439 --> 00:01:56.230 align:start position:0% early and iterate based on that um we then<00:01:53.600> tried<00:01:53.880> to<00:01:54.079> iterate<00:01:55.040> from<00:01:55.240> that<00:01:55.360> point<00:01:55.600> on 00:01:56.230 --> 00:01:56.240 align:start position:0% then tried to iterate from that point on 00:01:56.240 --> 00:01:58.670 align:start position:0% then tried to iterate from that point on but<00:01:56.840> because<00:01:57.039> of<00:01:57.200> the<00:01:57.479> custom<00:01:57.880> Network<00:01:58.280> stack 00:01:58.670 --> 00:01:58.680 align:start position:0% but because of the custom Network stack 00:01:58.680 --> 00:02:00.870 align:start position:0% but because of the custom Network stack that<00:01:58.759> we<00:01:58.880> had<00:01:59.039> built<00:01:59.360> for<00:02:00.079> game<00:02:00.320> specifically 00:02:00.870 --> 00:02:00.880 align:start position:0% that we had built for game specifically 00:02:00.880 --> 00:02:03.310 align:start position:0% that we had built for game specifically because<00:02:01.119> there<00:02:01.240> was<00:02:01.399> no<00:02:01.560> mud<00:02:01.840> at<00:02:01.920> the<00:02:02.079> time<00:02:02.840> um 00:02:03.310 --> 00:02:03.320 align:start position:0% because there was no mud at the time um 00:02:03.320 --> 00:02:04.709 align:start position:0% because there was no mud at the time um iterating<00:02:03.840> on<00:02:03.960> this<00:02:04.119> game<00:02:04.320> was<00:02:04.479> actually 00:02:04.709 --> 00:02:04.719 align:start position:0% iterating on this game was actually 00:02:04.719 --> 00:02:07.109 align:start position:0% iterating on this game was actually really<00:02:04.920> hard<00:02:05.399> and<00:02:06.240> for<00:02:06.479> that<00:02:06.640> let<00:02:06.719> me<00:02:06.880> let<00:02:06.960> me 00:02:07.109 --> 00:02:07.119 align:start position:0% really hard and for that let me let me 00:02:07.119 --> 00:02:09.270 align:start position:0% really hard and for that let me let me illustrate<00:02:08.080> just<00:02:08.280> real<00:02:08.520> quick<00:02:08.800> how<00:02:08.920> we<00:02:09.039> had<00:02:09.160> to 00:02:09.270 --> 00:02:09.280 align:start position:0% illustrate just real quick how we had to 00:02:09.280 --> 00:02:12.350 align:start position:0% illustrate just real quick how we had to do<00:02:09.440> things<00:02:09.720> before<00:02:10.000> mud<00:02:10.440> was<00:02:10.560> a<00:02:10.800> thing<00:02:11.760> um<00:02:12.200> we 00:02:12.350 --> 00:02:12.360 align:start position:0% do things before mud was a thing um we 00:02:12.360 --> 00:02:14.350 align:start position:0% do things before mud was a thing um we had<00:02:12.640> positions<00:02:13.000> in<00:02:13.120> our<00:02:13.280> game<00:02:13.680> so<00:02:13.879> we<00:02:14.040> created 00:02:14.350 --> 00:02:14.360 align:start position:0% had positions in our game so we created 00:02:14.360 --> 00:02:16.710 align:start position:0% had positions in our game so we created a<00:02:14.480> mapping<00:02:14.879> on<00:02:15.000> our<00:02:15.200> contracts<00:02:16.120> and<00:02:16.200> then<00:02:16.400> GAA 00:02:16.710 --> 00:02:16.720 align:start position:0% a mapping on our contracts and then GAA 00:02:16.720 --> 00:02:18.309 align:start position:0% a mapping on our contracts and then GAA functions<00:02:17.040> on<00:02:17.200> the<00:02:17.319> contract<00:02:17.800> so<00:02:17.959> that<00:02:18.200> the 00:02:18.309 --> 00:02:18.319 align:start position:0% functions on the contract so that the 00:02:18.319 --> 00:02:20.470 align:start position:0% functions on the contract so that the client<00:02:18.640> can<00:02:19.160> initialize<00:02:19.680> the<00:02:19.840> initial<00:02:20.120> State 00:02:20.470 --> 00:02:20.480 align:start position:0% client can initialize the initial State 00:02:20.480 --> 00:02:22.589 align:start position:0% client can initialize the initial State when<00:02:20.599> the<00:02:20.720> client<00:02:20.959> loads<00:02:21.239> up<00:02:22.000> and<00:02:22.160> then<00:02:22.440> we 00:02:22.589 --> 00:02:22.599 align:start position:0% when the client loads up and then we 00:02:22.599 --> 00:02:25.270 align:start position:0% when the client loads up and then we also<00:02:22.959> had<00:02:23.440> um<00:02:24.000> events<00:02:24.560> whenever<00:02:25.000> anything 00:02:25.270 --> 00:02:25.280 align:start position:0% also had um events whenever anything 00:02:25.280 --> 00:02:26.630 align:start position:0% also had um events whenever anything changed<00:02:25.640> on<00:02:25.720> the<00:02:25.879> contract<00:02:26.200> so<00:02:26.319> here<00:02:26.440> in<00:02:26.480> our 00:02:26.630 --> 00:02:26.640 align:start position:0% changed on the contract so here in our 00:02:26.640 --> 00:02:28.990 align:start position:0% changed on the contract so here in our move<00:02:26.840> function<00:02:27.160> we<00:02:27.319> have<00:02:27.440> to<00:02:28.319> we<00:02:28.480> have<00:02:28.760> we<00:02:28.879> have 00:02:28.990 --> 00:02:29.000 align:start position:0% move function we have to we have we have 00:02:29.000 --> 00:02:30.390 align:start position:0% move function we have to we have we have to<00:02:29.400> um<00:02:29.599> like 00:02:30.390 --> 00:02:30.400 align:start position:0% to um like 00:02:30.400 --> 00:02:32.270 align:start position:0% to um like set<00:02:30.720> the<00:02:31.200> set<00:02:31.360> the<00:02:31.480> storage<00:02:31.840> but<00:02:31.959> then<00:02:32.080> also 00:02:32.270 --> 00:02:32.280 align:start position:0% set the set the storage but then also 00:02:32.280 --> 00:02:33.710 align:start position:0% set the set the storage but then also emit<00:02:32.519> an<00:02:32.640> event<00:02:32.840> and<00:02:32.959> then<00:02:33.120> replicate<00:02:33.599> the 00:02:33.710 --> 00:02:33.720 align:start position:0% emit an event and then replicate the 00:02:33.720 --> 00:02:37.030 align:start position:0% emit an event and then replicate the whole<00:02:33.879> state<00:02:34.280> on<00:02:34.440> the<00:02:34.879> client<00:02:35.879> um<00:02:36.640> and<00:02:36.760> then<00:02:36.920> we 00:02:37.030 --> 00:02:37.040 align:start position:0% whole state on the client um and then we 00:02:37.040 --> 00:02:38.550 align:start position:0% whole state on the client um and then we had<00:02:37.160> to<00:02:37.280> do<00:02:37.400> that<00:02:37.560> with<00:02:37.680> every<00:02:38.040> type<00:02:38.200> of<00:02:38.319> state 00:02:38.550 --> 00:02:38.560 align:start position:0% had to do that with every type of state 00:02:38.560 --> 00:02:39.710 align:start position:0% had to do that with every type of state that<00:02:38.680> we<00:02:38.800> wanted<00:02:39.000> to<00:02:39.120> have<00:02:39.200> in<00:02:39.280> our<00:02:39.440> game 00:02:39.710 --> 00:02:39.720 align:start position:0% that we wanted to have in our game 00:02:39.720 --> 00:02:41.229 align:start position:0% that we wanted to have in our game position<00:02:40.080> was<00:02:40.280> obviously<00:02:40.599> not<00:02:40.760> the<00:02:40.840> only<00:02:41.080> type 00:02:41.229 --> 00:02:41.239 align:start position:0% position was obviously not the only type 00:02:41.239 --> 00:02:43.910 align:start position:0% position was obviously not the only type of<00:02:41.360> state<00:02:41.599> so<00:02:42.239> Health 00:02:43.910 --> 00:02:43.920 align:start position:0% of state so Health 00:02:43.920 --> 00:02:45.430 align:start position:0% of state so Health Energy 00:02:45.430 --> 00:02:45.440 align:start position:0% Energy 00:02:45.440 --> 00:02:48.070 align:start position:0% Energy skills<00:02:46.440> inventory<00:02:47.000> and<00:02:47.120> so<00:02:47.239> on<00:02:47.519> like<00:02:47.760> you<00:02:47.920> you 00:02:48.070 --> 00:02:48.080 align:start position:0% skills inventory and so on like you you 00:02:48.080 --> 00:02:50.110 align:start position:0% skills inventory and so on like you you get<00:02:48.200> the<00:02:48.319> idea<00:02:48.959> lot<00:02:49.080> of<00:02:49.200> boiler<00:02:49.519> plate<00:02:49.800> just<00:02:49.959> to 00:02:50.110 --> 00:02:50.120 align:start position:0% get the idea lot of boiler plate just to 00:02:50.120 --> 00:02:51.670 align:start position:0% get the idea lot of boiler plate just to keep<00:02:50.319> the<00:02:50.480> contract<00:02:50.920> and<00:02:51.040> the<00:02:51.120> client<00:02:51.440> state 00:02:51.670 --> 00:02:51.680 align:start position:0% keep the contract and the client state 00:02:51.680 --> 00:02:52.710 align:start position:0% keep the contract and the client state in 00:02:52.710 --> 00:02:52.720 align:start position:0% in 00:02:52.720 --> 00:02:55.869 align:start position:0% in sync<00:02:53.720> and<00:02:53.879> then<00:02:54.040> at<00:02:54.200> some<00:02:54.400> point<00:02:55.280> we<00:02:55.519> also 00:02:55.869 --> 00:02:55.879 align:start position:0% sync and then at some point we also 00:02:55.879 --> 00:02:58.030 align:start position:0% sync and then at some point we also discovered<00:02:56.159> ECS<00:02:56.920> which<00:02:57.319> which<00:02:57.480> then<00:02:57.680> kind<00:02:57.800> of 00:02:58.030 --> 00:02:58.040 align:start position:0% discovered ECS which which then kind of 00:02:58.040 --> 00:03:00.309 align:start position:0% discovered ECS which which then kind of like<00:02:58.159> made<00:02:58.319> a<00:02:58.440> big<00:02:58.760> impression<00:02:59.120> of<00:02:59.280> us<00:02:59.840> on<00:02:59.959> us 00:03:00.309 --> 00:03:00.319 align:start position:0% like made a big impression of us on us 00:03:00.319 --> 00:03:01.630 align:start position:0% like made a big impression of us on us um<00:03:00.440> it's<00:03:00.599> kind<00:03:00.720> of<00:03:00.800> a<00:03:00.959> pattern<00:03:01.280> that<00:03:01.440> people 00:03:01.630 --> 00:03:01.640 align:start position:0% um it's kind of a pattern that people 00:03:01.640 --> 00:03:03.390 align:start position:0% um it's kind of a pattern that people use<00:03:01.840> in<00:03:02.000> the<00:03:02.440> you<00:03:02.560> know<00:03:02.720> traditional<00:03:03.120> gaming 00:03:03.390 --> 00:03:03.400 align:start position:0% use in the you know traditional gaming 00:03:03.400 --> 00:03:05.110 align:start position:0% use in the you know traditional gaming industry<00:03:03.760> a<00:03:03.840> lot<00:03:04.000> to<00:03:04.200> manage<00:03:04.480> the<00:03:04.640> complexity 00:03:05.110 --> 00:03:05.120 align:start position:0% industry a lot to manage the complexity 00:03:05.120 --> 00:03:07.390 align:start position:0% industry a lot to manage the complexity of<00:03:05.239> games<00:03:06.080> and<00:03:06.200> so<00:03:06.519> around<00:03:06.840> this<00:03:07.040> time<00:03:07.239> we 00:03:07.390 --> 00:03:07.400 align:start position:0% of games and so around this time we 00:03:07.400 --> 00:03:09.509 align:start position:0% of games and so around this time we decided<00:03:07.799> to<00:03:08.319> basically<00:03:08.720> trash<00:03:09.080> what<00:03:09.239> we<00:03:09.360> have 00:03:09.509 --> 00:03:09.519 align:start position:0% decided to basically trash what we have 00:03:09.519 --> 00:03:12.390 align:start position:0% decided to basically trash what we have so<00:03:09.720> far<00:03:10.400> and<00:03:10.640> instead<00:03:11.120> build<00:03:11.360> a<00:03:11.480> framework<00:03:12.120> for 00:03:12.390 --> 00:03:12.400 align:start position:0% so far and instead build a framework for 00:03:12.400 --> 00:03:14.550 align:start position:0% so far and instead build a framework for ourselves<00:03:12.920> to<00:03:13.080> solve<00:03:13.280> our<00:03:13.440> own<00:03:13.680> problems<00:03:14.400> so 00:03:14.550 --> 00:03:14.560 align:start position:0% ourselves to solve our own problems so 00:03:14.560 --> 00:03:16.270 align:start position:0% ourselves to solve our own problems so that<00:03:14.760> we<00:03:14.959> for<00:03:15.159> the<00:03:15.280> next<00:03:15.519> project<00:03:15.920> can<00:03:16.040> skip 00:03:16.270 --> 00:03:16.280 align:start position:0% that we for the next project can skip 00:03:16.280 --> 00:03:17.990 align:start position:0% that we for the next project can skip all<00:03:16.440> the<00:03:16.519> boiler<00:03:16.840> plate<00:03:17.080> and<00:03:17.239> jump<00:03:17.519> right<00:03:17.680> into 00:03:17.990 --> 00:03:18.000 align:start position:0% all the boiler plate and jump right into 00:03:18.000 --> 00:03:19.830 align:start position:0% all the boiler plate and jump right into the<00:03:18.280> the<00:03:18.400> game<00:03:18.599> mechanics<00:03:19.040> and<00:03:19.200> iterate<00:03:19.680> much 00:03:19.830 --> 00:03:19.840 align:start position:0% the the game mechanics and iterate much 00:03:19.840 --> 00:03:22.550 align:start position:0% the the game mechanics and iterate much more<00:03:20.159> quickly<00:03:21.159> and<00:03:21.280> so<00:03:21.519> that's<00:03:22.120> basically 00:03:22.550 --> 00:03:22.560 align:start position:0% more quickly and so that's basically 00:03:22.560 --> 00:03:25.229 align:start position:0% more quickly and so that's basically what<00:03:22.760> became<00:03:23.440> the<00:03:23.799> version<00:03:24.040> one<00:03:24.200> of 00:03:25.229 --> 00:03:25.239 align:start position:0% what became the version one of 00:03:25.239 --> 00:03:28.149 align:start position:0% what became the version one of mud<00:03:26.239> we<00:03:26.480> basically<00:03:26.879> implemented<00:03:27.440> ECS<00:03:27.959> on 00:03:28.149 --> 00:03:28.159 align:start position:0% mud we basically implemented ECS on 00:03:28.159 --> 00:03:31.270 align:start position:0% mud we basically implemented ECS on chain<00:03:29.120> and<00:03:29.799> it<00:03:29.920> worked<00:03:30.239> pretty<00:03:30.439> well<00:03:31.000> uh<00:03:31.159> at 00:03:31.270 --> 00:03:31.280 align:start position:0% chain and it worked pretty well uh at 00:03:31.280 --> 00:03:33.270 align:start position:0% chain and it worked pretty well uh at least<00:03:31.480> in<00:03:31.599> terms<00:03:31.840> of<00:03:32.040> iterating<00:03:32.599> faster<00:03:33.159> this 00:03:33.270 --> 00:03:33.280 align:start position:0% least in terms of iterating faster this 00:03:33.280 --> 00:03:35.670 align:start position:0% least in terms of iterating faster this is<00:03:33.480> a<00:03:34.080> screenshot<00:03:34.840> of<00:03:35.080> of<00:03:35.239> basically<00:03:35.519> our 00:03:35.670 --> 00:03:35.680 align:start position:0% is a screenshot of of basically our 00:03:35.680 --> 00:03:37.229 align:start position:0% is a screenshot of of basically our second<00:03:35.959> prototype<00:03:36.400> we<00:03:36.480> built<00:03:36.840> and<00:03:36.959> this<00:03:37.080> time 00:03:37.229 --> 00:03:37.239 align:start position:0% second prototype we built and this time 00:03:37.239 --> 00:03:39.229 align:start position:0% second prototype we built and this time it<00:03:37.360> only<00:03:37.519> took<00:03:37.760> us<00:03:37.879> a<00:03:37.959> couple<00:03:38.280> weeks<00:03:38.879> to<00:03:39.040> build 00:03:39.229 --> 00:03:39.239 align:start position:0% it only took us a couple weeks to build 00:03:39.239 --> 00:03:42.070 align:start position:0% it only took us a couple weeks to build a<00:03:39.480> functioning<00:03:40.000> prototype<00:03:41.000> um<00:03:41.200> this<00:03:41.319> is<00:03:41.560> what 00:03:42.070 --> 00:03:42.080 align:start position:0% a functioning prototype um this is what 00:03:42.080 --> 00:03:43.830 align:start position:0% a functioning prototype um this is what eventually<00:03:42.439> turned<00:03:42.720> into<00:03:42.920> Sky<00:03:43.239> Drive<00:03:43.560> we<00:03:43.640> did 00:03:43.830 --> 00:03:43.840 align:start position:0% eventually turned into Sky Drive we did 00:03:43.840 --> 00:03:45.750 align:start position:0% eventually turned into Sky Drive we did play<00:03:44.120> tests<00:03:44.799> uh<00:03:45.000> like<00:03:45.120> a<00:03:45.200> lot<00:03:45.360> of<00:03:45.439> them<00:03:45.599> and 00:03:45.750 --> 00:03:45.760 align:start position:0% play tests uh like a lot of them and 00:03:45.760 --> 00:03:48.750 align:start position:0% play tests uh like a lot of them and then<00:03:45.840> iterated<00:03:46.319> on<00:03:46.439> it<00:03:47.280> and<00:03:48.000> we<00:03:48.159> also<00:03:48.439> built 00:03:48.750 --> 00:03:48.760 align:start position:0% then iterated on it and we also built 00:03:48.760 --> 00:03:50.470 align:start position:0% then iterated on it and we also built another<00:03:49.040> game<00:03:49.239> around<00:03:49.480> this<00:03:49.680> time<00:03:50.120> which<00:03:50.319> we 00:03:50.470 --> 00:03:50.480 align:start position:0% another game around this time which we 00:03:50.480 --> 00:03:53.069 align:start position:0% another game around this time which we called<00:03:50.920> opcraft<00:03:51.920> and<00:03:52.159> that<00:03:52.319> started<00:03:52.760> almost 00:03:53.069 --> 00:03:53.079 align:start position:0% called opcraft and that started almost 00:03:53.079 --> 00:03:54.550 align:start position:0% called opcraft and that started almost as<00:03:53.159> a<00:03:53.360> challenge<00:03:53.760> for<00:03:53.879> ourselves<00:03:54.280> we<00:03:54.360> wanted 00:03:54.550 --> 00:03:54.560 align:start position:0% as a challenge for ourselves we wanted 00:03:54.560 --> 00:03:56.509 align:start position:0% as a challenge for ourselves we wanted to<00:03:54.720> see<00:03:54.879> if<00:03:55.000> we<00:03:55.120> could<00:03:55.560> put<00:03:55.799> Minecraft<00:03:56.280> fully 00:03:56.509 --> 00:03:56.519 align:start position:0% to see if we could put Minecraft fully 00:03:56.519 --> 00:04:00.309 align:start position:0% to see if we could put Minecraft fully on<00:03:56.640> chain<00:03:57.599> um<00:03:58.120> and<00:03:58.360> turned<00:03:58.599> out<00:03:58.799> it's<00:03:59.040> possible 00:04:00.309 --> 00:04:00.319 align:start position:0% on chain um and turned out it's possible 00:04:00.319 --> 00:04:02.630 align:start position:0% on chain um and turned out it's possible and<00:04:01.200> um<00:04:01.319> we<00:04:01.439> built<00:04:01.720> actually<00:04:01.920> the<00:04:02.159> Prototype 00:04:02.630 --> 00:04:02.640 align:start position:0% and um we built actually the Prototype 00:04:02.640 --> 00:04:04.110 align:start position:0% and um we built actually the Prototype of<00:04:02.760> this<00:04:02.959> even<00:04:03.159> in<00:04:03.319> in<00:04:03.439> the<00:04:03.599> in<00:04:03.680> the<00:04:03.760> matter<00:04:04.000> of 00:04:04.110 --> 00:04:04.120 align:start position:0% of this even in in the in the matter of 00:04:04.120 --> 00:04:06.670 align:start position:0% of this even in in the in the matter of a<00:04:04.200> couple<00:04:04.519> days<00:04:04.840> it<00:04:05.079> we<00:04:05.439> we<00:04:05.760> you<00:04:05.840> know<00:04:06.239> cut<00:04:06.480> some 00:04:06.670 --> 00:04:06.680 align:start position:0% a couple days it we we you know cut some 00:04:06.680 --> 00:04:09.069 align:start position:0% a couple days it we we you know cut some corners<00:04:07.280> but<00:04:07.680> um<00:04:08.159> like<00:04:08.319> position<00:04:08.640> for<00:04:08.799> example 00:04:09.069 --> 00:04:09.079 align:start position:0% corners but um like position for example 00:04:09.079 --> 00:04:10.390 align:start position:0% corners but um like position for example wasn't<00:04:09.280> fully<00:04:09.480> Unchained<00:04:09.879> like<00:04:09.959> the<00:04:10.079> player 00:04:10.390 --> 00:04:10.400 align:start position:0% wasn't fully Unchained like the player 00:04:10.400 --> 00:04:13.509 align:start position:0% wasn't fully Unchained like the player position<00:04:11.319> but<00:04:12.200> it<00:04:12.319> was<00:04:12.560> possible<00:04:12.959> because<00:04:13.200> M 00:04:13.509 --> 00:04:13.519 align:start position:0% position but it was possible because M 00:04:13.519 --> 00:04:15.110 align:start position:0% position but it was possible because M basically<00:04:13.879> solved<00:04:14.280> almost<00:04:14.519> all<00:04:14.680> the<00:04:14.799> hard 00:04:15.110 --> 00:04:15.120 align:start position:0% basically solved almost all the hard 00:04:15.120 --> 00:04:16.629 align:start position:0% basically solved almost all the hard problems<00:04:15.400> that<00:04:15.519> we<00:04:15.640> had<00:04:16.040> for<00:04:16.199> our<00:04:16.400> first 00:04:16.629 --> 00:04:16.639 align:start position:0% problems that we had for our first 00:04:16.639 --> 00:04:18.430 align:start position:0% problems that we had for our first prototypes<00:04:17.320> were<00:04:17.560> already<00:04:17.759> solved<00:04:18.120> so<00:04:18.320> here 00:04:18.430 --> 00:04:18.440 align:start position:0% prototypes were already solved so here 00:04:18.440 --> 00:04:21.670 align:start position:0% prototypes were already solved so here we<00:04:18.560> could<00:04:19.120> move<00:04:19.400> much<00:04:19.840> faster<00:04:20.840> and<00:04:21.040> then<00:04:21.560> we 00:04:21.670 --> 00:04:21.680 align:start position:0% we could move much faster and then we 00:04:21.680 --> 00:04:24.110 align:start position:0% we could move much faster and then we did<00:04:21.840> a<00:04:21.959> twoe<00:04:22.320> play<00:04:22.560> test<00:04:22.800> of<00:04:22.960> this<00:04:23.600> and<00:04:23.840> it<00:04:23.960> was 00:04:24.110 --> 00:04:24.120 align:start position:0% did a twoe play test of this and it was 00:04:24.120 --> 00:04:25.710 align:start position:0% did a twoe play test of this and it was really<00:04:24.320> fun<00:04:24.560> people<00:04:24.759> build<00:04:25.040> a<00:04:25.120> lot<00:04:25.240> of<00:04:25.360> crazy 00:04:25.710 --> 00:04:25.720 align:start position:0% really fun people build a lot of crazy 00:04:25.720 --> 00:04:27.670 align:start position:0% really fun people build a lot of crazy stuff<00:04:26.520> and<00:04:26.680> there<00:04:26.800> were<00:04:27.040> even<00:04:27.320> even<00:04:27.479> some 00:04:27.670 --> 00:04:27.680 align:start position:0% stuff and there were even even some 00:04:27.680 --> 00:04:29.870 align:start position:0% stuff and there were even even some emerging<00:04:28.120> drama<00:04:28.639> there<00:04:28.759> was<00:04:29.120> uh<00:04:29.240> one<00:04:29.400> player 00:04:29.870 --> 00:04:29.880 align:start position:0% emerging drama there was uh one player 00:04:29.880 --> 00:04:31.590 align:start position:0% emerging drama there was uh one player who<00:04:30.039> claimed<00:04:30.400> a<00:04:30.479> lot<00:04:30.600> of<00:04:30.800> regions<00:04:31.240> around<00:04:31.479> the 00:04:31.590 --> 00:04:31.600 align:start position:0% who claimed a lot of regions around the 00:04:31.600 --> 00:04:34.710 align:start position:0% who claimed a lot of regions around the spawn<00:04:32.520> and<00:04:32.680> then<00:04:32.919> claimed<00:04:33.560> the<00:04:33.960> or<00:04:34.199> declared 00:04:34.710 --> 00:04:34.720 align:start position:0% spawn and then claimed the or declared 00:04:34.720 --> 00:04:36.670 align:start position:0% spawn and then claimed the or declared the<00:04:34.919> autonomous<00:04:35.440> People's<00:04:35.919> Republic<00:04:36.400> of 00:04:36.670 --> 00:04:36.680 align:start position:0% the autonomous People's Republic of 00:04:36.680 --> 00:04:39.590 align:start position:0% the autonomous People's Republic of opcraft<00:04:37.680> and<00:04:37.919> declared<00:04:38.360> himself<00:04:38.800> the<00:04:38.960> Supreme 00:04:39.590 --> 00:04:39.600 align:start position:0% opcraft and declared himself the Supreme 00:04:39.600 --> 00:04:42.270 align:start position:0% opcraft and declared himself the Supreme Commander<00:04:40.600> and<00:04:41.199> um<00:04:41.520> it<00:04:41.639> was<00:04:41.800> basically<00:04:42.160> a 00:04:42.270 --> 00:04:42.280 align:start position:0% Commander and um it was basically a 00:04:42.280 --> 00:04:44.230 align:start position:0% Commander and um it was basically a Communist<00:04:42.720> Regime<00:04:43.400> they<00:04:43.720> they<00:04:43.960> you<00:04:44.080> could 00:04:44.230 --> 00:04:44.240 align:start position:0% Communist Regime they they you could 00:04:44.240 --> 00:04:46.029 align:start position:0% Communist Regime they they you could join<00:04:44.520> the<00:04:44.639> Communist<00:04:45.039> Regime<00:04:45.400> by<00:04:45.680> giving<00:04:45.880> up 00:04:46.029 --> 00:04:46.039 align:start position:0% join the Communist Regime by giving up 00:04:46.039 --> 00:04:48.310 align:start position:0% join the Communist Regime by giving up all<00:04:46.160> your<00:04:46.360> personal<00:04:47.039> belongings<00:04:48.039> and<00:04:48.160> they 00:04:48.310 --> 00:04:48.320 align:start position:0% all your personal belongings and they 00:04:48.320 --> 00:04:49.830 align:start position:0% all your personal belongings and they even<00:04:48.479> built<00:04:48.759> some<00:04:48.880> onchain<00:04:49.320> and<00:04:49.479> client 00:04:49.830 --> 00:04:49.840 align:start position:0% even built some onchain and client 00:04:49.840 --> 00:04:51.790 align:start position:0% even built some onchain and client extensions<00:04:50.320> to<00:04:50.520> basically<00:04:50.840> be<00:04:51.000> able<00:04:51.240> to<00:04:51.400> join 00:04:51.790 --> 00:04:51.800 align:start position:0% extensions to basically be able to join 00:04:51.800 --> 00:04:54.150 align:start position:0% extensions to basically be able to join the<00:04:52.479> the<00:04:52.759> the<00:04:52.919> autonomous<00:04:53.360> pup's<00:04:53.759> Republic 00:04:54.150 --> 00:04:54.160 align:start position:0% the the the autonomous pup's Republic 00:04:54.160 --> 00:04:56.670 align:start position:0% the the the autonomous pup's Republic and<00:04:54.320> then<00:04:54.919> tap<00:04:55.199> into<00:04:55.440> the<00:04:55.600> inventory<00:04:56.160> of<00:04:56.360> the 00:04:56.670 --> 00:04:56.680 align:start position:0% and then tap into the inventory of the 00:04:56.680 --> 00:04:58.469 align:start position:0% and then tap into the inventory of the of<00:04:56.800> the<00:04:56.919> Republic<00:04:57.360> and<00:04:57.479> so 00:04:58.469 --> 00:04:58.479 align:start position:0% of the Republic and so 00:04:58.479 --> 00:05:00.909 align:start position:0% of the Republic and so on<00:04:59.479> and<00:04:59.759> people<00:04:59.960> built<00:05:00.199> monuments<00:05:00.600> and<00:05:00.720> it<00:05:00.840> was 00:05:00.909 --> 00:05:00.919 align:start position:0% on and people built monuments and it was 00:05:00.919 --> 00:05:03.830 align:start position:0% on and people built monuments and it was all<00:05:01.120> very<00:05:01.280> fun<00:05:01.759> but<00:05:02.759> eventually<00:05:03.440> after<00:05:03.680> two 00:05:03.830 --> 00:05:03.840 align:start position:0% all very fun but eventually after two 00:05:03.840 --> 00:05:06.749 align:start position:0% all very fun but eventually after two weeks<00:05:04.120> play<00:05:04.360> test<00:05:04.880> nothing<00:05:05.160> worked<00:05:05.759> anymore 00:05:06.749 --> 00:05:06.759 align:start position:0% weeks play test nothing worked anymore 00:05:06.759 --> 00:05:09.189 align:start position:0% weeks play test nothing worked anymore and<00:05:06.919> that<00:05:07.080> was<00:05:07.320> because<00:05:08.280> we<00:05:08.440> used<00:05:08.880> pretty 00:05:09.189 --> 00:05:09.199 align:start position:0% and that was because we used pretty 00:05:09.199 --> 00:05:11.830 align:start position:0% and that was because we used pretty strict<00:05:09.560> ECS<00:05:10.160> patterns<00:05:10.840> back<00:05:11.039> then<00:05:11.360> but 00:05:11.830 --> 00:05:11.840 align:start position:0% strict ECS patterns back then but 00:05:11.840 --> 00:05:13.270 align:start position:0% strict ECS patterns back then but there's<00:05:12.080> some<00:05:12.280> problems<00:05:12.560> with<00:05:12.680> ECS<00:05:13.039> if<00:05:13.160> you 00:05:13.270 --> 00:05:13.280 align:start position:0% there's some problems with ECS if you 00:05:13.280 --> 00:05:15.310 align:start position:0% there's some problems with ECS if you want<00:05:13.360> to<00:05:13.520> really<00:05:13.680> model<00:05:14.039> everything<00:05:14.360> as<00:05:14.520> ECS 00:05:15.310 --> 00:05:15.320 align:start position:0% want to really model everything as ECS 00:05:15.320 --> 00:05:17.390 align:start position:0% want to really model everything as ECS in<00:05:15.440> our<00:05:15.840> case<00:05:16.199> one<00:05:16.400> example<00:05:16.840> was<00:05:17.039> the 00:05:17.390 --> 00:05:17.400 align:start position:0% in our case one example was the 00:05:17.400 --> 00:05:20.150 align:start position:0% in our case one example was the inventory<00:05:18.400> um<00:05:18.919> we<00:05:19.120> modeled<00:05:19.479> our<00:05:19.639> state<00:05:19.919> in<00:05:20.000> a 00:05:20.150 --> 00:05:20.160 align:start position:0% inventory um we modeled our state in a 00:05:20.160 --> 00:05:23.390 align:start position:0% inventory um we modeled our state in a way<00:05:20.520> where<00:05:21.520> each<00:05:22.280> individual<00:05:22.800> and<00:05:23.240> each 00:05:23.390 --> 00:05:23.400 align:start position:0% way where each individual and each 00:05:23.400 --> 00:05:26.270 align:start position:0% way where each individual and each individual<00:05:23.880> item<00:05:24.440> was<00:05:24.800> an<00:05:24.960> entity<00:05:25.520> and<00:05:25.680> so 00:05:26.270 --> 00:05:26.280 align:start position:0% individual item was an entity and so 00:05:26.280 --> 00:05:27.990 align:start position:0% individual item was an entity and so once<00:05:26.520> people<00:05:26.720> figured<00:05:27.039> out<00:05:27.199> how<00:05:27.319> to<00:05:27.479> mine<00:05:27.800> with 00:05:27.990 --> 00:05:28.000 align:start position:0% once people figured out how to mine with 00:05:28.000 --> 00:05:29.870 align:start position:0% once people figured out how to mine with Bots<00:05:28.400> they<00:05:28.520> had<00:05:28.720> like<00:05:28.919> tens<00:05:29.160> of<00:05:29.319> thousands<00:05:29.800> of 00:05:29.870 --> 00:05:29.880 align:start position:0% Bots they had like tens of thousands of 00:05:29.880 --> 00:05:31.870 align:start position:0% Bots they had like tens of thousands of dirt<00:05:30.120> blocks<00:05:30.400> in<00:05:30.520> their<00:05:30.680> inventory<00:05:31.560> and<00:05:31.680> then 00:05:31.870 --> 00:05:31.880 align:start position:0% dirt blocks in their inventory and then 00:05:31.880 --> 00:05:33.590 align:start position:0% dirt blocks in their inventory and then each<00:05:32.039> of<00:05:32.199> those<00:05:32.400> dirt<00:05:32.680> blocks<00:05:33.000> was<00:05:33.199> a<00:05:33.319> unique 00:05:33.590 --> 00:05:33.600 align:start position:0% each of those dirt blocks was a unique 00:05:33.600 --> 00:05:35.150 align:start position:0% each of those dirt blocks was a unique entity<00:05:34.000> that<00:05:34.120> had<00:05:34.240> to<00:05:34.319> be<00:05:34.520> synchronized<00:05:35.039> to 00:05:35.150 --> 00:05:35.160 align:start position:0% entity that had to be synchronized to 00:05:35.160 --> 00:05:37.430 align:start position:0% entity that had to be synchronized to the<00:05:35.360> client<00:05:36.360> and<00:05:36.600> also<00:05:36.800> because<00:05:37.000> of<00:05:37.080> our<00:05:37.240> data 00:05:37.430 --> 00:05:37.440 align:start position:0% the client and also because of our data 00:05:37.440 --> 00:05:39.830 align:start position:0% the client and also because of our data model<00:05:38.319> um<00:05:38.639> basically<00:05:39.039> every<00:05:39.280> player<00:05:39.560> had<00:05:39.720> to 00:05:39.830 --> 00:05:39.840 align:start position:0% model um basically every player had to 00:05:39.840 --> 00:05:41.590 align:start position:0% model um basically every player had to download<00:05:40.199> the<00:05:40.319> entire<00:05:40.759> state<00:05:41.080> of<00:05:41.199> the<00:05:41.319> entire 00:05:41.590 --> 00:05:41.600 align:start position:0% download the entire state of the entire 00:05:41.600 --> 00:05:43.270 align:start position:0% download the entire state of the entire world<00:05:41.840> and<00:05:42.000> the<00:05:42.120> inventory<00:05:42.560> of<00:05:42.680> every<00:05:42.880> player 00:05:43.270 --> 00:05:43.280 align:start position:0% world and the inventory of every player 00:05:43.280 --> 00:05:44.990 align:start position:0% world and the inventory of every player every<00:05:43.440> time<00:05:43.600> they<00:05:43.720> wanted<00:05:43.960> to<00:05:44.039> load<00:05:44.280> the<00:05:44.400> game 00:05:44.990 --> 00:05:45.000 align:start position:0% every time they wanted to load the game 00:05:45.000 --> 00:05:46.629 align:start position:0% every time they wanted to load the game and<00:05:45.080> so<00:05:45.280> after<00:05:45.479> two<00:05:45.720> weeks<00:05:45.960> people<00:05:46.199> had<00:05:46.319> to 00:05:46.629 --> 00:05:46.639 align:start position:0% and so after two weeks people had to 00:05:46.639 --> 00:05:48.430 align:start position:0% and so after two weeks people had to download<00:05:47.039> multiple<00:05:47.440> gigabytes<00:05:47.880> of<00:05:48.000> data<00:05:48.319> just 00:05:48.430 --> 00:05:48.440 align:start position:0% download multiple gigabytes of data just 00:05:48.440 --> 00:05:50.110 align:start position:0% download multiple gigabytes of data just to<00:05:48.600> boot<00:05:48.800> the 00:05:50.110 --> 00:05:50.120 align:start position:0% to boot the 00:05:50.120 --> 00:05:52.350 align:start position:0% to boot the client<00:05:51.120> which<00:05:51.240> brings<00:05:51.520> us<00:05:51.680> to<00:05:51.840> our<00:05:52.120> next 00:05:52.350 --> 00:05:52.360 align:start position:0% client which brings us to our next 00:05:52.360 --> 00:05:54.150 align:start position:0% client which brings us to our next chapter<00:05:52.720> make<00:05:52.840> it 00:05:54.150 --> 00:05:54.160 align:start position:0% chapter make it 00:05:54.160 --> 00:05:57.469 align:start position:0% chapter make it right<00:05:55.160> mud<00:05:55.440> one<00:05:56.000> was<00:05:56.240> really<00:05:56.960> more<00:05:57.120> of<00:05:57.240> a 00:05:57.469 --> 00:05:57.479 align:start position:0% right mud one was really more of a 00:05:57.479 --> 00:05:59.390 align:start position:0% right mud one was really more of a prototype<00:05:58.039> to<00:05:58.199> see<00:05:58.560> if<00:05:58.720> we<00:05:58.919> you<00:05:59.039> know<00:05:59.199> if<00:05:59.280> this 00:05:59.390 --> 00:05:59.400 align:start position:0% prototype to see if we you know if this 00:05:59.400 --> 00:06:01.029 align:start position:0% prototype to see if we you know if this makes<00:05:59.759> sense<00:06:00.039> like<00:06:00.199> does<00:06:00.319> it<00:06:00.479> make<00:06:00.639> sense<00:06:00.840> to 00:06:01.029 --> 00:06:01.039 align:start position:0% makes sense like does it make sense to 00:06:01.039 --> 00:06:03.150 align:start position:0% makes sense like does it make sense to have<00:06:01.440> a<00:06:01.560> full<00:06:01.800> stack<00:06:02.039> framework<00:06:02.680> and<00:06:02.880> this 00:06:03.150 --> 00:06:03.160 align:start position:0% have a full stack framework and this 00:06:03.160 --> 00:06:05.510 align:start position:0% have a full stack framework and this this<00:06:03.360> these<00:06:03.520> patterns<00:06:03.919> to<00:06:04.039> iterate<00:06:04.479> faster<00:06:05.400> um 00:06:05.510 --> 00:06:05.520 align:start position:0% this these patterns to iterate faster um 00:06:05.520 --> 00:06:06.710 align:start position:0% this these patterns to iterate faster um and<00:06:05.600> it<00:06:05.720> proved<00:06:06.000> that<00:06:06.120> the<00:06:06.240> developer 00:06:06.710 --> 00:06:06.720 align:start position:0% and it proved that the developer 00:06:06.720 --> 00:06:08.870 align:start position:0% and it proved that the developer experience<00:06:07.160> and<00:06:07.280> the<00:06:07.400> iteration<00:06:07.919> speed<00:06:08.639> was 00:06:08.870 --> 00:06:08.880 align:start position:0% experience and the iteration speed was 00:06:08.880 --> 00:06:10.870 align:start position:0% experience and the iteration speed was much<00:06:09.120> faster<00:06:09.400> with<00:06:09.520> it<00:06:09.759> but<00:06:09.880> it<00:06:10.039> had<00:06:10.240> some 00:06:10.870 --> 00:06:10.880 align:start position:0% much faster with it but it had some 00:06:10.880 --> 00:06:13.270 align:start position:0% much faster with it but it had some fundamental<00:06:11.479> limitations<00:06:12.199> and<00:06:12.440> for<00:06:12.680> that<00:06:13.120> to 00:06:13.270 --> 00:06:13.280 align:start position:0% fundamental limitations and for that to 00:06:13.280 --> 00:06:15.390 align:start position:0% fundamental limitations and for that to illustrate<00:06:13.800> that<00:06:14.599> um<00:06:14.840> I'm<00:06:14.960> going<00:06:15.039> to<00:06:15.160> give<00:06:15.280> you 00:06:15.390 --> 00:06:15.400 align:start position:0% illustrate that um I'm going to give you 00:06:15.400 --> 00:06:17.550 align:start position:0% illustrate that um I'm going to give you a<00:06:15.599> super<00:06:15.800> quick<00:06:16.000> ECS<00:06:16.680> crash<00:06:16.960> course<00:06:17.280> in<00:06:17.400> case 00:06:17.550 --> 00:06:17.560 align:start position:0% a super quick ECS crash course in case 00:06:17.560 --> 00:06:19.749 align:start position:0% a super quick ECS crash course in case you're<00:06:17.720> not<00:06:17.880> familiar<00:06:18.880> um<00:06:19.080> it's<00:06:19.240> very<00:06:19.440> simple 00:06:19.749 --> 00:06:19.759 align:start position:0% you're not familiar um it's very simple 00:06:19.759 --> 00:06:22.710 align:start position:0% you're not familiar um it's very simple ECS<00:06:20.400> stands<00:06:20.680> for<00:06:20.880> entity<00:06:21.280> component<00:06:21.759> systems 00:06:22.710 --> 00:06:22.720 align:start position:0% ECS stands for entity component systems 00:06:22.720 --> 00:06:25.070 align:start position:0% ECS stands for entity component systems and<00:06:22.919> entities<00:06:23.360> are<00:06:23.520> basically<00:06:23.880> just<00:06:24.080> IDs<00:06:24.960> and 00:06:25.070 --> 00:06:25.080 align:start position:0% and entities are basically just IDs and 00:06:25.080 --> 00:06:27.390 align:start position:0% and entities are basically just IDs and then<00:06:25.199> you<00:06:25.400> associate<00:06:25.880> data<00:06:26.240> with<00:06:26.400> them<00:06:26.720> with 00:06:27.390 --> 00:06:27.400 align:start position:0% then you associate data with them with 00:06:27.400 --> 00:06:29.830 align:start position:0% then you associate data with them with components<00:06:28.400> and<00:06:28.840> it<00:06:28.960> works<00:06:29.240> really<00:06:29.400> well<00:06:29.680> for 00:06:29.830 --> 00:06:29.840 align:start position:0% components and it works really well for 00:06:29.840 --> 00:06:31.270 align:start position:0% components and it works really well for something<00:06:30.080> like<00:06:30.280> position<00:06:30.759> you<00:06:30.880> can<00:06:31.000> have<00:06:31.120> a 00:06:31.270 --> 00:06:31.280 align:start position:0% something like position you can have a 00:06:31.280 --> 00:06:33.990 align:start position:0% something like position you can have a position<00:06:31.680> component<00:06:32.479> and<00:06:32.639> then<00:06:32.919> each<00:06:33.199> entity 00:06:33.990 --> 00:06:34.000 align:start position:0% position component and then each entity 00:06:34.000 --> 00:06:35.510 align:start position:0% position component and then each entity has<00:06:34.199> their<00:06:34.440> position<00:06:34.800> in<00:06:34.919> this<00:06:35.080> component 00:06:35.510 --> 00:06:35.520 align:start position:0% has their position in this component 00:06:35.520 --> 00:06:37.790 align:start position:0% has their position in this component works<00:06:35.800> well<00:06:36.520> but<00:06:36.680> then<00:06:37.199> for<00:06:37.400> something<00:06:37.680> like 00:06:37.790 --> 00:06:37.800 align:start position:0% works well but then for something like 00:06:37.800 --> 00:06:40.150 align:start position:0% works well but then for something like an<00:06:37.960> inventory<00:06:38.520> it's<00:06:38.680> much<00:06:38.880> trickier<00:06:39.520> because 00:06:40.150 --> 00:06:40.160 align:start position:0% an inventory it's much trickier because 00:06:40.160 --> 00:06:41.790 align:start position:0% an inventory it's much trickier because you<00:06:40.319> have<00:06:40.479> to<00:06:41.080> you<00:06:41.199> know<00:06:41.440> you<00:06:41.560> have<00:06:41.639> to 00:06:41.790 --> 00:06:41.800 align:start position:0% you have to you know you have to 00:06:41.800 --> 00:06:43.469 align:start position:0% you have to you know you have to associate<00:06:42.280> everything<00:06:42.599> with<00:06:42.759> entities<00:06:43.280> so 00:06:43.469 --> 00:06:43.479 align:start position:0% associate everything with entities so 00:06:43.479 --> 00:06:44.990 align:start position:0% associate everything with entities so you<00:06:43.560> have<00:06:43.759> basically<00:06:44.120> have<00:06:44.280> two<00:06:44.479> options<00:06:44.840> for 00:06:44.990 --> 00:06:45.000 align:start position:0% you have basically have two options for 00:06:45.000 --> 00:06:47.550 align:start position:0% you have basically have two options for an<00:06:45.280> inventory<00:06:46.280> um<00:06:46.479> option<00:06:46.759> one<00:06:47.160> is<00:06:47.319> what<00:06:47.440> we 00:06:47.550 --> 00:06:47.560 align:start position:0% an inventory um option one is what we 00:06:47.560 --> 00:06:50.710 align:start position:0% an inventory um option one is what we use<00:06:47.800> for<00:06:48.120> opcraft<00:06:49.120> which<00:06:49.240> is<00:06:49.599> each<00:06:49.960> item<00:06:50.560> is 00:06:50.710 --> 00:06:50.720 align:start position:0% use for opcraft which is each item is 00:06:50.720 --> 00:06:52.550 align:start position:0% use for opcraft which is each item is its<00:06:50.919> own<00:06:51.199> entity<00:06:52.080> and<00:06:52.160> then<00:06:52.280> you<00:06:52.400> have 00:06:52.550 --> 00:06:52.560 align:start position:0% its own entity and then you have 00:06:52.560 --> 00:06:54.189 align:start position:0% its own entity and then you have something<00:06:52.840> like<00:06:52.960> an<00:06:53.080> owned<00:06:53.360> by<00:06:53.639> component 00:06:54.189 --> 00:06:54.199 align:start position:0% something like an owned by component 00:06:54.199 --> 00:06:56.510 align:start position:0% something like an owned by component which<00:06:54.400> basically<00:06:55.240> Associates<00:06:55.879> the<00:06:56.000> owner<00:06:56.360> of 00:06:56.510 --> 00:06:56.520 align:start position:0% which basically Associates the owner of 00:06:56.520 --> 00:06:58.990 align:start position:0% which basically Associates the owner of this<00:06:56.680> entity<00:06:57.520> with<00:06:57.639> the<00:06:57.800> enti<00:06:58.199> with<00:06:58.319> the<00:06:58.479> item 00:06:58.990 --> 00:06:59.000 align:start position:0% this entity with the enti with the item 00:06:59.000 --> 00:07:00.390 align:start position:0% this entity with the enti with the item and<00:06:59.080> then<00:06:59.199> you<00:06:59.280> model<00:06:59.680> the<00:06:59.759> inventory<00:07:00.240> that 00:07:00.390 --> 00:07:00.400 align:start position:0% and then you model the inventory that 00:07:00.400 --> 00:07:02.070 align:start position:0% and then you model the inventory that way<00:07:00.800> but<00:07:00.919> then<00:07:01.039> you<00:07:01.120> run<00:07:01.319> into<00:07:01.560> this<00:07:01.759> problem 00:07:02.070 --> 00:07:02.080 align:start position:0% way but then you run into this problem 00:07:02.080 --> 00:07:04.189 align:start position:0% way but then you run into this problem with<00:07:02.280> you<00:07:02.400> know<00:07:02.599> 10,000<00:07:03.160> unique<00:07:03.639> dirt<00:07:03.919> blocks 00:07:04.189 --> 00:07:04.199 align:start position:0% with you know 10,000 unique dirt blocks 00:07:04.199 --> 00:07:05.990 align:start position:0% with you know 10,000 unique dirt blocks in<00:07:04.319> your 00:07:05.990 --> 00:07:06.000 align:start position:0% in your 00:07:06.000 --> 00:07:08.869 align:start position:0% in your inventory<00:07:07.000> another<00:07:07.360> option<00:07:08.039> is<00:07:08.440> a<00:07:08.560> little<00:07:08.720> bit 00:07:08.869 --> 00:07:08.879 align:start position:0% inventory another option is a little bit 00:07:08.879 --> 00:07:11.270 align:start position:0% inventory another option is a little bit more<00:07:09.080> hacky<00:07:10.000> um<00:07:10.280> you<00:07:10.400> can<00:07:10.639> basically<00:07:10.960> create 00:07:11.270 --> 00:07:11.280 align:start position:0% more hacky um you can basically create 00:07:11.280 --> 00:07:13.830 align:start position:0% more hacky um you can basically create this<00:07:11.440> kind<00:07:11.560> of<00:07:11.720> pseudo<00:07:12.160> entity<00:07:13.000> by<00:07:13.440> something 00:07:13.830 --> 00:07:13.840 align:start position:0% this kind of pseudo entity by something 00:07:13.840 --> 00:07:16.189 align:start position:0% this kind of pseudo entity by something like<00:07:14.120> hashing<00:07:14.680> together<00:07:14.919> the<00:07:15.080> player<00:07:15.840> and<00:07:16.000> the 00:07:16.189 --> 00:07:16.199 align:start position:0% like hashing together the player and the 00:07:16.199 --> 00:07:18.430 align:start position:0% like hashing together the player and the item<00:07:17.160> um<00:07:17.319> and<00:07:17.440> then<00:07:17.639> that's<00:07:17.840> your<00:07:18.000> entity<00:07:18.360> and 00:07:18.430 --> 00:07:18.440 align:start position:0% item um and then that's your entity and 00:07:18.440 --> 00:07:20.430 align:start position:0% item um and then that's your entity and then<00:07:18.560> you<00:07:18.720> associate<00:07:19.160> the<00:07:19.319> number<00:07:19.639> of<00:07:20.240> of 00:07:20.430 --> 00:07:20.440 align:start position:0% then you associate the number of of 00:07:20.440 --> 00:07:22.110 align:start position:0% then you associate the number of of entities<00:07:21.039> or<00:07:21.240> the<00:07:21.319> number<00:07:21.560> of<00:07:21.680> items<00:07:22.000> the 00:07:22.110 --> 00:07:22.120 align:start position:0% entities or the number of items the 00:07:22.120 --> 00:07:25.110 align:start position:0% entities or the number of items the player<00:07:22.479> has<00:07:23.360> um<00:07:23.720> with<00:07:23.919> this<00:07:24.080> pseudo<00:07:24.440> entity 00:07:25.110 --> 00:07:25.120 align:start position:0% player has um with this pseudo entity 00:07:25.120 --> 00:07:26.990 align:start position:0% player has um with this pseudo entity but<00:07:25.280> it's<00:07:25.479> really<00:07:25.720> hacky<00:07:26.240> not<00:07:26.400> nice<00:07:26.599> to<00:07:26.759> work 00:07:26.990 --> 00:07:27.000 align:start position:0% but it's really hacky not nice to work 00:07:27.000 --> 00:07:29.029 align:start position:0% but it's really hacky not nice to work with<00:07:27.479> you<00:07:27.599> know<00:07:27.759> you<00:07:27.879> have<00:07:28.080> only<00:07:28.400> still<00:07:28.720> one 00:07:29.029 --> 00:07:29.039 align:start position:0% with you know you have only still one 00:07:29.039 --> 00:07:31.350 align:start position:0% with you know you have only still one one<00:07:29.199> column<00:07:29.680> for<00:07:29.919> player<00:07:30.199> and<00:07:30.479> item<00:07:31.120> and<00:07:31.280> in 00:07:31.350 --> 00:07:31.360 align:start position:0% one column for player and item and in 00:07:31.360 --> 00:07:32.830 align:start position:0% one column for player and item and in the<00:07:31.479> worst<00:07:31.720> case<00:07:31.879> it's<00:07:32.000> a<00:07:32.160> hash<00:07:32.400> so<00:07:32.520> you<00:07:32.639> can't 00:07:32.830 --> 00:07:32.840 align:start position:0% the worst case it's a hash so you can't 00:07:32.840 --> 00:07:34.390 align:start position:0% the worst case it's a hash so you can't even<00:07:33.039> really<00:07:33.240> see<00:07:33.639> what's<00:07:33.840> the<00:07:33.960> player<00:07:34.240> and 00:07:34.390 --> 00:07:34.400 align:start position:0% even really see what's the player and 00:07:34.400 --> 00:07:36.270 align:start position:0% even really see what's the player and what's<00:07:34.560> the 00:07:36.270 --> 00:07:36.280 align:start position:0% what's the 00:07:36.280 --> 00:07:39.710 align:start position:0% what's the entity<00:07:37.280> then<00:07:37.599> we<00:07:38.000> um<00:07:38.120> had<00:07:38.240> a<00:07:38.720> realization 00:07:39.710 --> 00:07:39.720 align:start position:0% entity then we um had a realization 00:07:39.720 --> 00:07:42.350 align:start position:0% entity then we um had a realization which<00:07:39.919> is<00:07:40.919> um<00:07:41.120> ECS<00:07:41.599> is<00:07:41.759> basically<00:07:42.080> just<00:07:42.199> a 00:07:42.350 --> 00:07:42.360 align:start position:0% which is um ECS is basically just a 00:07:42.360 --> 00:07:45.869 align:start position:0% which is um ECS is basically just a subset<00:07:42.759> of<00:07:42.960> relational<00:07:43.919> databases<00:07:44.919> and<00:07:45.639> um<00:07:45.759> it 00:07:45.869 --> 00:07:45.879 align:start position:0% subset of relational databases and um it 00:07:45.879 --> 00:07:47.390 align:start position:0% subset of relational databases and um it has<00:07:46.000> one<00:07:46.159> limitation<00:07:46.639> which<00:07:46.759> is<00:07:46.919> the<00:07:47.039> entity 00:07:47.390 --> 00:07:47.400 align:start position:0% has one limitation which is the entity 00:07:47.400 --> 00:07:49.510 align:start position:0% has one limitation which is the entity has<00:07:47.520> to<00:07:47.639> be<00:07:47.759> the<00:07:47.919> key<00:07:48.440> and<00:07:48.520> so<00:07:48.720> we<00:07:48.879> decided<00:07:49.240> to 00:07:49.510 --> 00:07:49.520 align:start position:0% has to be the key and so we decided to 00:07:49.520 --> 00:07:51.950 align:start position:0% has to be the key and so we decided to lift<00:07:49.840> this<00:07:50.080> limitation<00:07:51.080> and<00:07:51.280> instead<00:07:51.639> model 00:07:51.950 --> 00:07:51.960 align:start position:0% lift this limitation and instead model 00:07:51.960 --> 00:07:54.390 align:start position:0% lift this limitation and instead model it<00:07:52.319> as<00:07:52.560> a<00:07:52.720> table<00:07:53.360> which<00:07:53.639> made<00:07:53.960> modeling 00:07:54.390 --> 00:07:54.400 align:start position:0% it as a table which made modeling 00:07:54.400 --> 00:07:56.869 align:start position:0% it as a table which made modeling something<00:07:54.639> like<00:07:54.759> an<00:07:54.919> inventory<00:07:55.400> much 00:07:56.869 --> 00:07:56.879 align:start position:0% something like an inventory much 00:07:56.879 --> 00:07:59.710 align:start position:0% something like an inventory much easier<00:07:57.879> and<00:07:58.080> ECS<00:07:58.560> can<00:07:58.720> still<00:07:58.879> be<00:07:59.039> represented 00:07:59.710 --> 00:07:59.720 align:start position:0% easier and ECS can still be represented 00:07:59.720 --> 00:08:01.149 align:start position:0% easier and ECS can still be represented within<00:07:59.919> this<00:08:00.039> new<00:08:00.240> model<00:08:00.599> because<00:08:00.879> it's<00:08:01.000> a 00:08:01.149 --> 00:08:01.159 align:start position:0% within this new model because it's a 00:08:01.159 --> 00:08:03.749 align:start position:0% within this new model because it's a subset<00:08:02.159> so<00:08:02.280> you<00:08:02.400> can<00:08:02.599> now<00:08:02.840> have<00:08:03.440> something 00:08:03.749 --> 00:08:03.759 align:start position:0% subset so you can now have something 00:08:03.759 --> 00:08:06.070 align:start position:0% subset so you can now have something like<00:08:03.919> the<00:08:04.039> position<00:08:04.360> table<00:08:04.680> still<00:08:05.360> um<00:08:05.599> just<00:08:05.840> by 00:08:06.070 --> 00:08:06.080 align:start position:0% like the position table still um just by 00:08:06.080 --> 00:08:07.830 align:start position:0% like the position table still um just by using<00:08:06.360> the<00:08:06.479> entity<00:08:06.840> as<00:08:06.960> the<00:08:07.080> only 00:08:07.830 --> 00:08:07.840 align:start position:0% using the entity as the only 00:08:07.840 --> 00:08:11.270 align:start position:0% using the entity as the only key<00:08:08.840> that<00:08:09.000> sounds<00:08:09.280> like<00:08:09.440> an<00:08:09.560> easy<00:08:09.840> change<00:08:10.800> but 00:08:11.270 --> 00:08:11.280 align:start position:0% key that sounds like an easy change but 00:08:11.280 --> 00:08:13.469 align:start position:0% key that sounds like an easy change but it<00:08:11.440> was<00:08:11.639> actually<00:08:11.960> much<00:08:12.840> harder<00:08:13.199> than<00:08:13.319> we 00:08:13.469 --> 00:08:13.479 align:start position:0% it was actually much harder than we 00:08:13.479 --> 00:08:16.189 align:start position:0% it was actually much harder than we thought<00:08:13.960> um<00:08:14.120> we<00:08:14.280> proposed<00:08:14.919> doing<00:08:15.240> this<00:08:16.000> um 00:08:16.189 --> 00:08:16.199 align:start position:0% thought um we proposed doing this um 00:08:16.199 --> 00:08:18.230 align:start position:0% thought um we proposed doing this um early<00:08:16.879> in 00:08:18.230 --> 00:08:18.240 align:start position:0% early in 00:08:18.240 --> 00:08:20.990 align:start position:0% early in 2023<00:08:19.240> and<00:08:19.400> then<00:08:19.639> we<00:08:19.840> also<00:08:20.159> proposed<00:08:20.919> uh 00:08:20.990 --> 00:08:21.000 align:start position:0% 2023 and then we also proposed uh 00:08:21.000 --> 00:08:22.469 align:start position:0% 2023 and then we also proposed uh changing<00:08:21.400> the<00:08:21.520> world<00:08:21.720> framework<00:08:22.159> to<00:08:22.280> work 00:08:22.469 --> 00:08:22.479 align:start position:0% changing the world framework to work 00:08:22.479 --> 00:08:26.350 align:start position:0% changing the world framework to work better<00:08:22.720> with<00:08:22.840> the<00:08:22.960> STA<00:08:23.479> model<00:08:24.520> but<00:08:25.520> turns<00:08:25.840> out 00:08:26.350 --> 00:08:26.360 align:start position:0% better with the STA model but turns out 00:08:26.360 --> 00:08:27.950 align:start position:0% better with the STA model but turns out we<00:08:26.479> were<00:08:26.680> wrong<00:08:26.879> it<00:08:27.000> wasn't<00:08:27.240> just<00:08:27.319> a<00:08:27.440> 20-minute 00:08:27.950 --> 00:08:27.960 align:start position:0% we were wrong it wasn't just a 20-minute 00:08:27.960 --> 00:08:30.309 align:start position:0% we were wrong it wasn't just a 20-minute Adventure<00:08:28.479> it<00:08:28.639> almost<00:08:28.879> took<00:08:29.080> us<00:08:29.720> um<00:08:29.840> an<00:08:30.000> entire 00:08:30.309 --> 00:08:30.319 align:start position:0% Adventure it almost took us um an entire 00:08:30.319 --> 00:08:32.469 align:start position:0% Adventure it almost took us um an entire year<00:08:30.560> and<00:08:30.720> was<00:08:30.919> basically<00:08:31.240> a<00:08:31.360> full<00:08:31.599> rewrite<00:08:32.279> of 00:08:32.469 --> 00:08:32.479 align:start position:0% year and was basically a full rewrite of 00:08:32.479 --> 00:08:33.949 align:start position:0% year and was basically a full rewrite of the<00:08:32.640> entire 00:08:33.949 --> 00:08:33.959 align:start position:0% the entire 00:08:33.959 --> 00:08:36.829 align:start position:0% the entire thing<00:08:34.959> and<00:08:35.159> migrating<00:08:35.760> from<00:08:36.039> version<00:08:36.279> one<00:08:36.479> to 00:08:36.829 --> 00:08:36.839 align:start position:0% thing and migrating from version one to 00:08:36.839 --> 00:08:39.269 align:start position:0% thing and migrating from version one to V2<00:08:37.680> was<00:08:37.880> pretty<00:08:38.120> painful<00:08:38.519> for<00:08:38.719> the<00:08:38.919> people<00:08:39.120> who 00:08:39.269 --> 00:08:39.279 align:start position:0% V2 was pretty painful for the people who 00:08:39.279 --> 00:08:40.709 align:start position:0% V2 was pretty painful for the people who started<00:08:39.560> building<00:08:39.959> with<00:08:40.159> version<00:08:40.440> one<00:08:40.640> we 00:08:40.709 --> 00:08:40.719 align:start position:0% started building with version one we 00:08:40.719 --> 00:08:42.750 align:start position:0% started building with version one we felt<00:08:40.919> that<00:08:41.039> in<00:08:41.159> our<00:08:41.279> own<00:08:41.479> team<00:08:42.279> and<00:08:42.399> we<00:08:42.519> started 00:08:42.750 --> 00:08:42.760 align:start position:0% felt that in our own team and we started 00:08:42.760 --> 00:08:45.350 align:start position:0% felt that in our own team and we started building<00:08:43.039> Sky<00:08:43.399> Strife<00:08:44.360> on<00:08:44.680> the<00:08:44.800> first<00:08:45.040> version 00:08:45.350 --> 00:08:45.360 align:start position:0% building Sky Strife on the first version 00:08:45.360 --> 00:08:46.750 align:start position:0% building Sky Strife on the first version and<00:08:45.480> then<00:08:45.600> we<00:08:45.720> had<00:08:45.839> to<00:08:45.959> migrate<00:08:46.320> it<00:08:46.440> to<00:08:46.600> the 00:08:46.750 --> 00:08:46.760 align:start position:0% and then we had to migrate it to the 00:08:46.760 --> 00:08:49.350 align:start position:0% and then we had to migrate it to the second<00:08:47.040> version<00:08:47.880> which<00:08:48.160> drove<00:08:48.600> kusaba<00:08:49.200> our 00:08:49.350 --> 00:08:49.360 align:start position:0% second version which drove kusaba our 00:08:49.360 --> 00:08:52.350 align:start position:0% second version which drove kusaba our main<00:08:49.560> engineer<00:08:49.920> on<00:08:50.080> Sky<00:08:50.360> strive<00:08:50.720> almost<00:08:51.360> crazy 00:08:52.350 --> 00:08:52.360 align:start position:0% main engineer on Sky strive almost crazy 00:08:52.360 --> 00:08:54.230 align:start position:0% main engineer on Sky strive almost crazy um<00:08:52.760> but<00:08:52.920> once<00:08:53.080> we<00:08:53.240> pushed<00:08:53.519> through<00:08:53.720> it<00:08:53.880> it<00:08:54.000> was 00:08:54.230 --> 00:08:54.240 align:start position:0% um but once we pushed through it it was 00:08:54.240 --> 00:08:56.710 align:start position:0% um but once we pushed through it it was worth<00:08:54.440> it<00:08:55.080> um<00:08:55.240> the<00:08:55.399> gas<00:08:55.760> was<00:08:56.040> way<00:08:56.279> down<00:08:56.560> because 00:08:56.710 --> 00:08:56.720 align:start position:0% worth it um the gas was way down because 00:08:56.720 --> 00:08:59.269 align:start position:0% worth it um the gas was way down because we<00:08:56.880> focused<00:08:57.240> way<00:08:57.399> more<00:08:57.600> on<00:08:57.800> gas<00:08:58.279> optimization 00:08:59.269 --> 00:08:59.279 align:start position:0% we focused way more on gas optimization 00:08:59.279 --> 00:09:00.069 align:start position:0% we focused way more on gas optimization and 00:09:00.069 --> 00:09:00.079 align:start position:0% and 00:09:00.079 --> 00:09:02.790 align:start position:0% and and<00:09:01.079> the<00:09:01.399> the<00:09:01.560> improved<00:09:01.959> data<00:09:02.200> model<00:09:02.440> on<00:09:02.680> the 00:09:02.790 --> 00:09:02.800 align:start position:0% and the the improved data model on the 00:09:02.800 --> 00:09:04.949 align:start position:0% and the the improved data model on the improve<00:09:03.560> the<00:09:03.680> improved<00:09:04.000> syn<00:09:04.279> stack<00:09:04.600> meant 00:09:04.949 --> 00:09:04.959 align:start position:0% improve the improved syn stack meant 00:09:04.959 --> 00:09:06.910 align:start position:0% improve the improved syn stack meant that<00:09:05.160> now<00:09:05.279> you<00:09:05.440> could<00:09:05.720> load<00:09:06.160> the<00:09:06.320> client<00:09:06.720> much 00:09:06.910 --> 00:09:06.920 align:start position:0% that now you could load the client much 00:09:06.920 --> 00:09:08.310 align:start position:0% that now you could load the client much much<00:09:07.120> much 00:09:08.310 --> 00:09:08.320 align:start position:0% much much 00:09:08.320 --> 00:09:10.870 align:start position:0% much much faster<00:09:09.320> and<00:09:09.440> so<00:09:09.760> once<00:09:09.920> we<00:09:10.079> pushed<00:09:10.399> through<00:09:10.560> it 00:09:10.870 --> 00:09:10.880 align:start position:0% faster and so once we pushed through it 00:09:10.880 --> 00:09:13.150 align:start position:0% faster and so once we pushed through it it<00:09:11.040> was<00:09:11.440> it<00:09:11.519> was<00:09:11.720> worth<00:09:11.920> it<00:09:12.320> and<00:09:12.519> kusaba<00:09:13.000> was 00:09:13.150 --> 00:09:13.160 align:start position:0% it was it was worth it and kusaba was 00:09:13.160 --> 00:09:14.630 align:start position:0% it was it was worth it and kusaba was happy 00:09:14.630 --> 00:09:14.640 align:start position:0% happy 00:09:14.640 --> 00:09:16.910 align:start position:0% happy again<00:09:15.640> then<00:09:15.800> more<00:09:15.920> and<00:09:16.079> more<00:09:16.240> teams<00:09:16.600> started 00:09:16.910 --> 00:09:16.920 align:start position:0% again then more and more teams started 00:09:16.920 --> 00:09:19.910 align:start position:0% again then more and more teams started using<00:09:17.240> M<00:09:17.800> and<00:09:18.279> also<00:09:18.560> larger<00:09:19.079> larger<00:09:19.440> Studios 00:09:19.910 --> 00:09:19.920 align:start position:0% using M and also larger larger Studios 00:09:19.920 --> 00:09:22.750 align:start position:0% using M and also larger larger Studios like<00:09:20.200> CCP<00:09:20.720> games<00:09:21.040> started<00:09:21.320> building<00:09:22.200> um<00:09:22.640> their 00:09:22.750 --> 00:09:22.760 align:start position:0% like CCP games started building um their 00:09:22.760 --> 00:09:24.949 align:start position:0% like CCP games started building um their new<00:09:22.920> game<00:09:23.120> e<00:09:23.320> Frontier<00:09:23.680> on<00:09:23.839> mud<00:09:24.480> and<00:09:24.600> so<00:09:24.760> we 00:09:24.949 --> 00:09:24.959 align:start position:0% new game e Frontier on mud and so we 00:09:24.959 --> 00:09:27.069 align:start position:0% new game e Frontier on mud and so we realized<00:09:25.839> oh<00:09:26.000> and<00:09:26.160> more<00:09:26.440> more<00:09:26.640> more<00:09:26.760> and<00:09:26.880> more 00:09:27.069 --> 00:09:27.079 align:start position:0% realized oh and more more more and more 00:09:27.079 --> 00:09:28.389 align:start position:0% realized oh and more more more and more team<00:09:27.320> teams<00:09:27.519> were<00:09:27.720> already<00:09:27.959> pushing<00:09:28.240> for 00:09:28.389 --> 00:09:28.399 align:start position:0% team teams were already pushing for 00:09:28.399 --> 00:09:30.790 align:start position:0% team teams were already pushing for production<00:09:28.800> back<00:09:28.959> then<00:09:29.720> and<00:09:29.959> so<00:09:30.120> we<00:09:30.279> realized 00:09:30.790 --> 00:09:30.800 align:start position:0% production back then and so we realized 00:09:30.800 --> 00:09:33.069 align:start position:0% production back then and so we realized okay<00:09:30.920> it's<00:09:31.079> time<00:09:31.240> for<00:09:31.399> an<00:09:31.519> audit<00:09:32.399> um<00:09:32.760> we<00:09:32.959> then 00:09:33.069 --> 00:09:33.079 align:start position:0% okay it's time for an audit um we then 00:09:33.079 --> 00:09:34.710 align:start position:0% okay it's time for an audit um we then worked<00:09:33.360> with<00:09:33.480> open<00:09:33.720> Zeppelin<00:09:34.079> to<00:09:34.240> audit<00:09:34.600> the 00:09:34.710 --> 00:09:34.720 align:start position:0% worked with open Zeppelin to audit the 00:09:34.720 --> 00:09:36.710 align:start position:0% worked with open Zeppelin to audit the core<00:09:34.959> of<00:09:35.120> mud<00:09:35.760> but<00:09:35.920> still<00:09:36.240> maintain<00:09:36.600> the 00:09:36.710 --> 00:09:36.720 align:start position:0% core of mud but still maintain the 00:09:36.720 --> 00:09:38.670 align:start position:0% core of mud but still maintain the flexibility<00:09:37.399> to<00:09:37.600> add<00:09:37.760> more<00:09:37.959> features<00:09:38.480> as 00:09:38.670 --> 00:09:38.680 align:start position:0% flexibility to add more features as 00:09:38.680 --> 00:09:41.230 align:start position:0% flexibility to add more features as modules<00:09:39.279> because<00:09:39.480> M<00:09:40.240> version<00:09:40.480> two<00:09:40.760> was<00:09:40.880> built 00:09:41.230 --> 00:09:41.240 align:start position:0% modules because M version two was built 00:09:41.240 --> 00:09:43.509 align:start position:0% modules because M version two was built to<00:09:41.360> be<00:09:41.560> very 00:09:43.509 --> 00:09:43.519 align:start position:0% to be very 00:09:43.519 --> 00:09:45.829 align:start position:0% to be very modular<00:09:44.519> but<00:09:44.680> what<00:09:44.800> that<00:09:44.959> also<00:09:45.160> means<00:09:45.560> is<00:09:45.720> that 00:09:45.829 --> 00:09:45.839 align:start position:0% modular but what that also means is that 00:09:45.839 --> 00:09:47.829 align:start position:0% modular but what that also means is that there<00:09:45.920> are<00:09:46.040> no<00:09:46.200> more<00:09:46.399> breaking<00:09:46.760> changes<00:09:47.440> in 00:09:47.829 --> 00:09:47.839 align:start position:0% there are no more breaking changes in 00:09:47.839 --> 00:09:50.509 align:start position:0% there are no more breaking changes in the<00:09:48.000> core<00:09:48.480> of<00:09:48.640> mud<00:09:49.480> and<00:09:49.680> that<00:09:49.880> now<00:09:50.040> means<00:09:50.399> that 00:09:50.509 --> 00:09:50.519 align:start position:0% the core of mud and that now means that 00:09:50.519 --> 00:09:53.069 align:start position:0% the core of mud and that now means that we<00:09:50.640> can<00:09:51.160> on<00:09:51.320> our<00:09:51.560> end<00:09:51.800> first<00:09:52.399> focus<00:09:52.720> more<00:09:52.880> on 00:09:53.069 --> 00:09:53.079 align:start position:0% we can on our end first focus more on 00:09:53.079 --> 00:09:54.509 align:start position:0% we can on our end first focus more on the<00:09:53.240> the<00:09:53.399> Integrations<00:09:53.920> and<00:09:54.079> developer 00:09:54.509 --> 00:09:54.519 align:start position:0% the the Integrations and developer 00:09:54.519 --> 00:09:57.190 align:start position:0% the the Integrations and developer experience<00:09:55.440> um<00:09:55.640> but<00:09:55.880> also<00:09:56.240> other<00:09:56.959> third 00:09:57.190 --> 00:09:57.200 align:start position:0% experience um but also other third 00:09:57.200 --> 00:09:58.910 align:start position:0% experience um but also other third parties<00:09:57.600> can<00:09:57.880> now<00:09:58.160> you<00:09:58.279> know<00:09:58.440> trust<00:09:58.760> this 00:09:58.910 --> 00:09:58.920 align:start position:0% parties can now you know trust this 00:09:58.920 --> 00:10:01.269 align:start position:0% parties can now you know trust this interface<00:09:59.440> is<00:09:59.839> that<00:09:59.920> it<00:10:00.040> won't<00:10:00.240> break<00:10:00.519> anymore 00:10:01.269 --> 00:10:01.279 align:start position:0% interface is that it won't break anymore 00:10:01.279 --> 00:10:03.430 align:start position:0% interface is that it won't break anymore um<00:10:01.399> and<00:10:01.519> build<00:10:01.760> Integrations<00:10:02.240> on<00:10:02.440> top<00:10:03.240> so<00:10:03.360> I 00:10:03.430 --> 00:10:03.440 align:start position:0% um and build Integrations on top so I 00:10:03.440 --> 00:10:05.470 align:start position:0% um and build Integrations on top so I want<00:10:03.560> to<00:10:03.680> show<00:10:03.880> you<00:10:04.160> a<00:10:04.279> couple<00:10:05.040> a<00:10:05.160> couple 00:10:05.470 --> 00:10:05.480 align:start position:0% want to show you a couple a couple 00:10:05.480 --> 00:10:07.670 align:start position:0% want to show you a couple a couple things<00:10:05.959> um<00:10:06.120> that<00:10:06.240> we<00:10:06.399> built<00:10:07.120> in<00:10:07.279> terms<00:10:07.519> of 00:10:07.670 --> 00:10:07.680 align:start position:0% things um that we built in terms of 00:10:07.680 --> 00:10:09.949 align:start position:0% things um that we built in terms of developer<00:10:08.120> experience<00:10:08.519> since<00:10:08.760> then<00:10:09.600> um<00:10:09.839> here 00:10:09.949 --> 00:10:09.959 align:start position:0% developer experience since then um here 00:10:09.959 --> 00:10:11.829 align:start position:0% developer experience since then um here you<00:10:10.040> see<00:10:10.240> the<00:10:10.320> world<00:10:10.640> Explorer<00:10:11.640> which 00:10:11.829 --> 00:10:11.839 align:start position:0% you see the world Explorer which 00:10:11.839 --> 00:10:14.630 align:start position:0% you see the world Explorer which basically<00:10:12.279> allows<00:10:12.560> you<00:10:12.720> to<00:10:13.279> interact<00:10:14.120> inspect 00:10:14.630 --> 00:10:14.640 align:start position:0% basically allows you to interact inspect 00:10:14.640 --> 00:10:16.190 align:start position:0% basically allows you to interact inspect the<00:10:14.800> transactions<00:10:15.360> that<00:10:15.519> happening<00:10:15.839> in<00:10:16.000> your 00:10:16.190 --> 00:10:16.200 align:start position:0% the transactions that happening in your 00:10:16.200 --> 00:10:18.030 align:start position:0% the transactions that happening in your in<00:10:16.360> this<00:10:16.519> case<00:10:16.760> local<00:10:17.079> client<00:10:17.440> but<00:10:17.600> also 00:10:18.030 --> 00:10:18.040 align:start position:0% in this case local client but also 00:10:18.040 --> 00:10:21.110 align:start position:0% in this case local client but also remote<00:10:18.440> deployed<00:10:18.880> World<00:10:19.880> um<00:10:20.320> in<00:10:20.480> real<00:10:20.760> time 00:10:21.110 --> 00:10:21.120 align:start position:0% remote deployed World um in real time 00:10:21.120 --> 00:10:22.350 align:start position:0% remote deployed World um in real time and<00:10:21.399> inspect<00:10:21.760> the<00:10:21.839> round<00:10:22.040> trip<00:10:22.240> and 00:10:22.350 --> 00:10:22.360 align:start position:0% and inspect the round trip and 00:10:22.360 --> 00:10:24.910 align:start position:0% and inspect the round trip and everything<00:10:22.880> and<00:10:23.519> then<00:10:23.720> also<00:10:24.200> the<00:10:24.360> table<00:10:24.640> view 00:10:24.910 --> 00:10:24.920 align:start position:0% everything and then also the table view 00:10:24.920 --> 00:10:26.630 align:start position:0% everything and then also the table view where<00:10:25.040> you<00:10:25.160> can<00:10:25.320> inspect<00:10:25.720> all<00:10:25.880> of<00:10:26.000> your<00:10:26.160> tables 00:10:26.630 --> 00:10:26.640 align:start position:0% where you can inspect all of your tables 00:10:26.640 --> 00:10:29.590 align:start position:0% where you can inspect all of your tables data<00:10:27.640> um<00:10:28.600> yeah<00:10:28.760> in<00:10:28.920> in<00:10:29.000> the<00:10:29.160> in<00:10:29.360> the<00:10:29.399> world 00:10:29.590 --> 00:10:29.600 align:start position:0% data um yeah in in the in the world 00:10:29.600 --> 00:10:30.990 align:start position:0% data um yeah in in the in the world Explorer<00:10:29.959> so<00:10:30.040> all<00:10:30.160> of<00:10:30.240> your<00:10:30.320> onchain<00:10:30.720> state 00:10:30.990 --> 00:10:31.000 align:start position:0% Explorer so all of your onchain state 00:10:31.000 --> 00:10:33.350 align:start position:0% Explorer so all of your onchain state you<00:10:31.079> can<00:10:31.240> just<00:10:31.399> inspect<00:10:31.720> it 00:10:33.350 --> 00:10:33.360 align:start position:0% you can just inspect it 00:10:33.360 --> 00:10:35.949 align:start position:0% you can just inspect it here<00:10:34.360> and<00:10:34.480> then<00:10:34.680> we<00:10:34.880> have<00:10:35.240> a<00:10:35.399> second<00:10:35.680> view<00:10:35.880> of 00:10:35.949 --> 00:10:35.959 align:start position:0% here and then we have a second view of 00:10:35.959 --> 00:10:37.710 align:start position:0% here and then we have a second view of the<00:10:36.079> world<00:10:36.320> Explorer<00:10:37.000> which<00:10:37.120> is<00:10:37.320> a<00:10:37.440> slightly 00:10:37.710 --> 00:10:37.720 align:start position:0% the world Explorer which is a slightly 00:10:37.720 --> 00:10:40.069 align:start position:0% the world Explorer which is a slightly more<00:10:37.920> complex<00:10:38.320> table<00:10:39.279> um<00:10:39.480> where<00:10:39.639> now<00:10:39.760> we<00:10:39.880> can 00:10:40.069 --> 00:10:40.079 align:start position:0% more complex table um where now we can 00:10:40.079 --> 00:10:43.470 align:start position:0% more complex table um where now we can even<00:10:40.240> use<00:10:40.519> SQL<00:10:41.399> to<00:10:41.920> uh<00:10:42.000> filter<00:10:42.720> the<00:10:42.920> table<00:10:43.320> so 00:10:43.470 --> 00:10:43.480 align:start position:0% even use SQL to uh filter the table so 00:10:43.480 --> 00:10:45.030 align:start position:0% even use SQL to uh filter the table so in<00:10:43.600> this<00:10:43.760> case<00:10:43.920> we<00:10:44.000> have<00:10:44.120> a<00:10:44.279> task<00:10:44.560> list<00:10:44.839> and<00:10:44.920> we 00:10:45.030 --> 00:10:45.040 align:start position:0% in this case we have a task list and we 00:10:45.040 --> 00:10:47.069 align:start position:0% in this case we have a task list and we filter<00:10:45.399> it<00:10:45.839> to<00:10:46.040> the<00:10:46.160> ones<00:10:46.360> that<00:10:46.440> are<00:10:46.600> completed 00:10:47.069 --> 00:10:47.079 align:start position:0% filter it to the ones that are completed 00:10:47.079 --> 00:10:52.269 align:start position:0% filter it to the ones that are completed or<00:10:47.240> the<00:10:47.360> ones<00:10:47.560> that<00:10:47.680> are<00:10:47.800> not 00:10:52.269 --> 00:10:52.279 align:start position:0% 00:10:52.279 --> 00:10:54.509 align:start position:0% completed<00:10:53.279> and<00:10:53.399> then<00:10:53.560> the<00:10:53.720> last<00:10:53.959> thing<00:10:54.320> I<00:10:54.399> want 00:10:54.509 --> 00:10:54.519 align:start position:0% completed and then the last thing I want 00:10:54.519 --> 00:10:56.590 align:start position:0% completed and then the last thing I want to<00:10:54.600> show<00:10:54.760> you<00:10:54.920> is<00:10:55.160> again<00:10:55.320> World<00:10:55.560> Explorer<00:10:56.480> but 00:10:56.590 --> 00:10:56.600 align:start position:0% to show you is again World Explorer but 00:10:56.600 --> 00:10:57.990 align:start position:0% to show you is again World Explorer but the<00:10:56.680> world<00:10:56.880> Explorer<00:10:57.240> is<00:10:57.320> basically<00:10:57.600> just<00:10:57.760> do 00:10:57.990 --> 00:10:58.000 align:start position:0% the world Explorer is basically just do 00:10:58.000 --> 00:10:59.430 align:start position:0% the world Explorer is basically just do your<00:10:58.160> ey<00:10:58.360> for<00:10:58.480> all<00:10:58.600> the<00:10:58.680> other<00:10:58.839> features<00:10:59.320> that 00:10:59.430 --> 00:10:59.440 align:start position:0% your ey for all the other features that 00:10:59.440 --> 00:11:02.190 align:start position:0% your ey for all the other features that we<00:10:59.560> had<00:10:59.680> to<00:10:59.760> build<00:11:00.200> below<00:11:00.560> that<00:11:01.360> um<00:11:01.959> here<00:11:02.079> you 00:11:02.190 --> 00:11:02.200 align:start position:0% we had to build below that um here you 00:11:02.200 --> 00:11:03.670 align:start position:0% we had to build below that um here you can<00:11:02.320> see<00:11:02.480> the<00:11:02.560> world<00:11:02.800> Explorer<00:11:03.200> automatically 00:11:03.670 --> 00:11:03.680 align:start position:0% can see the world Explorer automatically 00:11:03.680 --> 00:11:06.310 align:start position:0% can see the world Explorer automatically synchronizes<00:11:04.320> the<00:11:04.480> ABI<00:11:05.079> of<00:11:05.240> the<00:11:05.360> world<00:11:06.200> and 00:11:06.310 --> 00:11:06.320 align:start position:0% synchronizes the ABI of the world and 00:11:06.320 --> 00:11:08.509 align:start position:0% synchronizes the ABI of the world and you<00:11:06.399> can<00:11:06.639> interact<00:11:07.200> with<00:11:07.360> the<00:11:07.480> ABI<00:11:08.360> through 00:11:08.509 --> 00:11:08.519 align:start position:0% you can interact with the ABI through 00:11:08.519 --> 00:11:10.590 align:start position:0% you can interact with the ABI through the<00:11:08.680> world<00:11:08.959> Explorer<00:11:09.959> and<00:11:10.079> then<00:11:10.240> when<00:11:10.360> you 00:11:10.590 --> 00:11:10.600 align:start position:0% the world Explorer and then when you 00:11:10.600 --> 00:11:13.030 align:start position:0% the world Explorer and then when you modify<00:11:11.079> your<00:11:11.320> your<00:11:11.519> contracts<00:11:11.959> your<00:11:12.160> systems 00:11:13.030 --> 00:11:13.040 align:start position:0% modify your your contracts your systems 00:11:13.040 --> 00:11:15.550 align:start position:0% modify your your contracts your systems um<00:11:13.360> it's<00:11:13.560> automatically<00:11:14.120> picked<00:11:14.399> up<00:11:14.680> by<00:11:14.920> the 00:11:15.550 --> 00:11:15.560 align:start position:0% um it's automatically picked up by the 00:11:15.560 --> 00:11:17.509 align:start position:0% um it's automatically picked up by the you<00:11:15.680> know<00:11:15.839> contract<00:11:16.200> Staff<00:11:16.480> Runner<00:11:17.240> and<00:11:17.360> it's 00:11:17.509 --> 00:11:17.519 align:start position:0% you know contract Staff Runner and it's 00:11:17.519 --> 00:11:20.150 align:start position:0% you know contract Staff Runner and it's going<00:11:17.639> to<00:11:18.000> update<00:11:18.600> the<00:11:18.800> AI<00:11:19.680> on<00:11:19.839> the<00:11:19.920> world 00:11:20.150 --> 00:11:20.160 align:start position:0% going to update the AI on the world 00:11:20.160 --> 00:11:22.150 align:start position:0% going to update the AI on the world Explorer<00:11:20.560> immediately<00:11:21.399> so<00:11:21.519> you<00:11:21.639> can<00:11:21.839> again 00:11:22.150 --> 00:11:22.160 align:start position:0% Explorer immediately so you can again 00:11:22.160 --> 00:11:23.710 align:start position:0% Explorer immediately so you can again interact<00:11:22.600> with<00:11:22.720> your<00:11:22.920> new<00:11:23.079> functionality<00:11:23.600> on 00:11:23.710 --> 00:11:23.720 align:start position:0% interact with your new functionality on 00:11:23.720 --> 00:11:27.710 align:start position:0% interact with your new functionality on the<00:11:23.800> well<00:11:24.040> Explorer 00:11:27.710 --> 00:11:27.720 align:start position:0% 00:11:27.720 --> 00:11:30.030 align:start position:0% immediately<00:11:28.720> and 00:11:30.030 --> 00:11:30.040 align:start position:0% immediately and 00:11:30.040 --> 00:11:32.269 align:start position:0% immediately and these<00:11:30.440> you<00:11:30.560> know<00:11:31.040> like<00:11:31.720> these<00:11:31.920> stable 00:11:32.269 --> 00:11:32.279 align:start position:0% these you know like these stable 00:11:32.279 --> 00:11:34.750 align:start position:0% these you know like these stable interfaces<00:11:33.000> enable<00:11:33.959> um<00:11:34.240> more<00:11:34.399> and<00:11:34.560> more 00:11:34.750 --> 00:11:34.760 align:start position:0% interfaces enable um more and more 00:11:34.760 --> 00:11:36.710 align:start position:0% interfaces enable um more and more Integrations<00:11:35.240> to<00:11:35.360> be<00:11:35.480> built<00:11:36.240> and<00:11:36.360> we<00:11:36.480> wanted 00:11:36.710 --> 00:11:36.720 align:start position:0% Integrations to be built and we wanted 00:11:36.720 --> 00:11:38.990 align:start position:0% Integrations to be built and we wanted to<00:11:36.880> take<00:11:37.079> that<00:11:37.320> commitment<00:11:37.760> one<00:11:37.959> step<00:11:38.240> further 00:11:38.990 --> 00:11:39.000 align:start position:0% to take that commitment one step further 00:11:39.000 --> 00:11:41.069 align:start position:0% to take that commitment one step further for<00:11:39.200> a<00:11:39.360> dist<00:11:39.560> stable<00:11:39.839> interface<00:11:40.639> and<00:11:40.720> so<00:11:40.880> we're 00:11:41.069 --> 00:11:41.079 align:start position:0% for a dist stable interface and so we're 00:11:41.079 --> 00:11:43.110 align:start position:0% for a dist stable interface and so we're now<00:11:41.240> working<00:11:41.560> on<00:11:41.720> an<00:11:41.880> on<00:11:41.959> an<00:11:42.079> ERC<00:11:42.600> for<00:11:42.760> the 00:11:43.110 --> 00:11:43.120 align:start position:0% now working on an on an ERC for the 00:11:43.120 --> 00:11:45.269 align:start position:0% now working on an on an ERC for the store<00:11:43.519> standard<00:11:43.880> so<00:11:44.040> for<00:11:44.160> the<00:11:44.279> events<00:11:44.839> and<00:11:45.040> the 00:11:45.269 --> 00:11:45.279 align:start position:0% store standard so for the events and the 00:11:45.279 --> 00:11:47.389 align:start position:0% store standard so for the events and the interface<00:11:45.680> of<00:11:45.839> the<00:11:45.920> store<00:11:46.760> um<00:11:46.920> it's<00:11:47.079> currently 00:11:47.389 --> 00:11:47.399 align:start position:0% interface of the store um it's currently 00:11:47.399 --> 00:11:50.430 align:start position:0% interface of the store um it's currently in<00:11:47.480> draft<00:11:47.839> State<00:11:48.120> IRC<00:11:48.839> 7813<00:11:49.839> if<00:11:49.959> you<00:11:50.040> want<00:11:50.160> to 00:11:50.430 --> 00:11:50.440 align:start position:0% in draft State IRC 7813 if you want to 00:11:50.440 --> 00:11:53.430 align:start position:0% in draft State IRC 7813 if you want to follow<00:11:50.720> along<00:11:50.959> or<00:11:51.120> join<00:11:51.320> the<00:11:51.639> discussion<00:11:52.639> and 00:11:53.430 --> 00:11:53.440 align:start position:0% follow along or join the discussion and 00:11:53.440 --> 00:11:55.069 align:start position:0% follow along or join the discussion and yeah<00:11:53.880> the<00:11:53.959> hope<00:11:54.160> is<00:11:54.279> that<00:11:54.440> that<00:11:54.560> will<00:11:54.720> allow 00:11:55.069 --> 00:11:55.079 align:start position:0% yeah the hope is that that will allow 00:11:55.079 --> 00:11:56.870 align:start position:0% yeah the hope is that that will allow more<00:11:55.240> and<00:11:55.399> more<00:11:55.800> uh<00:11:55.920> tools<00:11:56.240> and<00:11:56.399> Integrations 00:11:56.870 --> 00:11:56.880 align:start position:0% more and more uh tools and Integrations 00:11:56.880 --> 00:11:59.949 align:start position:0% more and more uh tools and Integrations to<00:11:57.000> be<00:11:57.120> built<00:11:57.360> on<00:11:57.519> top<00:11:57.680> of<00:11:57.839> that<00:11:58.680> and<00:11:59.639> I<00:11:59.720> want<00:11:59.800> to 00:11:59.949 --> 00:11:59.959 align:start position:0% to be built on top of that and I want to 00:11:59.959 --> 00:12:01.710 align:start position:0% to be built on top of that and I want to give<00:12:00.079> a<00:12:00.160> shout<00:12:00.360> out<00:12:00.519> to<00:12:00.720> block<00:12:01.040> Scout<00:12:01.399> at<00:12:01.560> this 00:12:01.710 --> 00:12:01.720 align:start position:0% give a shout out to block Scout at this 00:12:01.720 --> 00:12:03.110 align:start position:0% give a shout out to block Scout at this point<00:12:02.040> because<00:12:02.279> they<00:12:02.440> already<00:12:02.720> built<00:12:02.959> an 00:12:03.110 --> 00:12:03.120 align:start position:0% point because they already built an 00:12:03.120 --> 00:12:05.110 align:start position:0% point because they already built an integration<00:12:03.880> format<00:12:04.360> so<00:12:04.519> now<00:12:04.639> you<00:12:04.720> can<00:12:04.839> go<00:12:05.000> on 00:12:05.110 --> 00:12:05.120 align:start position:0% integration format so now you can go on 00:12:05.120 --> 00:12:08.030 align:start position:0% integration format so now you can go on block<00:12:05.440> Scout<00:12:06.040> explore<00:12:06.399> the<00:12:06.480> worlds<00:12:06.880> there<00:12:07.399> and 00:12:08.030 --> 00:12:08.040 align:start position:0% block Scout explore the worlds there and 00:12:08.040 --> 00:12:10.430 align:start position:0% block Scout explore the worlds there and um<00:12:08.880> even<00:12:09.120> inspect<00:12:09.440> the<00:12:09.600> table<00:12:09.880> data<00:12:10.120> directly 00:12:10.430 --> 00:12:10.440 align:start position:0% um even inspect the table data directly 00:12:10.440 --> 00:12:12.470 align:start position:0% um even inspect the table data directly from<00:12:10.600> blog 00:12:12.470 --> 00:12:12.480 align:start position:0% from blog 00:12:12.480 --> 00:12:16.189 align:start position:0% from blog Scout<00:12:13.480> all<00:12:13.639> right<00:12:14.480> all<00:12:14.600> of<00:12:14.760> that<00:12:14.959> brings<00:12:15.320> us<00:12:15.480> to 00:12:16.189 --> 00:12:16.199 align:start position:0% Scout all right all of that brings us to 00:12:16.199 --> 00:12:20.069 align:start position:0% Scout all right all of that brings us to the<00:12:16.880> present<00:12:17.240> chapter<00:12:17.680> of<00:12:17.880> making<00:12:18.160> it 00:12:20.069 --> 00:12:20.079 align:start position:0% the present chapter of making it 00:12:20.079 --> 00:12:22.790 align:start position:0% the present chapter of making it fast<00:12:21.079> imagine<00:12:21.480> you<00:12:21.600> want<00:12:21.720> to<00:12:21.920> join<00:12:22.160> a<00:12:22.320> new 00:12:22.790 --> 00:12:22.800 align:start position:0% fast imagine you want to join a new 00:12:22.800 --> 00:12:27.269 align:start position:0% fast imagine you want to join a new shiny<00:12:23.279> autonomous 00:12:27.269 --> 00:12:27.279 align:start position:0% 00:12:27.279 --> 00:12:29.310 align:start position:0% world<00:12:28.279> all<00:12:28.399> right<00:12:28.560> that<00:12:28.680> doesn't<00:12:28.880> load<00:12:29.199> but 00:12:29.310 --> 00:12:29.320 align:start position:0% world all right that doesn't load but 00:12:29.320 --> 00:12:32.590 align:start position:0% world all right that doesn't load but just<00:12:29.480> imagine<00:12:29.920> use<00:12:30.120> your<00:12:30.760> imagination<00:12:31.760> um<00:12:32.480> but 00:12:32.590 --> 00:12:32.600 align:start position:0% just imagine use your imagination um but 00:12:32.600 --> 00:12:35.150 align:start position:0% just imagine use your imagination um but then<00:12:32.720> suddenly<00:12:33.040> you<00:12:33.160> greet<00:12:33.399> it<00:12:33.600> by<00:12:33.920> a<00:12:34.040> fox<00:12:34.920> and 00:12:35.150 --> 00:12:35.160 align:start position:0% then suddenly you greet it by a fox and 00:12:35.160 --> 00:12:37.230 align:start position:0% then suddenly you greet it by a fox and the<00:12:35.279> fox<00:12:35.600> tells<00:12:35.880> you<00:12:36.600> that<00:12:36.720> you<00:12:36.839> don't<00:12:37.040> have 00:12:37.230 --> 00:12:37.240 align:start position:0% the fox tells you that you don't have 00:12:37.240 --> 00:12:38.670 align:start position:0% the fox tells you that you don't have any<00:12:37.360> funds<00:12:37.600> on<00:12:37.760> this 00:12:38.670 --> 00:12:38.680 align:start position:0% any funds on this 00:12:38.680 --> 00:12:40.870 align:start position:0% any funds on this chain<00:12:39.680> and<00:12:39.800> now<00:12:39.920> you<00:12:40.000> have<00:12:40.120> to<00:12:40.240> find<00:12:40.399> a<00:12:40.560> bridge 00:12:40.870 --> 00:12:40.880 align:start position:0% chain and now you have to find a bridge 00:12:40.880 --> 00:12:43.030 align:start position:0% chain and now you have to find a bridge to<00:12:41.079> bridge<00:12:41.399> the<00:12:41.519> funds<00:12:41.800> to<00:12:42.000> this<00:12:42.120> chain<00:12:42.920> and 00:12:43.030 --> 00:12:43.040 align:start position:0% to bridge the funds to this chain and 00:12:43.040 --> 00:12:44.110 align:start position:0% to bridge the funds to this chain and then<00:12:43.199> you<00:12:43.320> have<00:12:43.440> to<00:12:43.639> approve<00:12:43.959> that 00:12:44.110 --> 00:12:44.120 align:start position:0% then you have to approve that 00:12:44.120 --> 00:12:45.550 align:start position:0% then you have to approve that transaction<00:12:44.760> and<00:12:44.839> then<00:12:45.000> when<00:12:45.199> you<00:12:45.320> want<00:12:45.440> to 00:12:45.550 --> 00:12:45.560 align:start position:0% transaction and then when you want to 00:12:45.560 --> 00:12:46.829 align:start position:0% transaction and then when you want to make<00:12:45.680> a<00:12:45.800> move<00:12:45.959> in<00:12:46.079> the<00:12:46.160> world<00:12:46.399> you<00:12:46.519> have<00:12:46.600> to 00:12:46.829 --> 00:12:46.839 align:start position:0% make a move in the world you have to 00:12:46.839 --> 00:12:48.829 align:start position:0% make a move in the world you have to approve<00:12:47.160> that<00:12:47.360> transaction<00:12:48.360> and<00:12:48.519> approve 00:12:48.829 --> 00:12:48.839 align:start position:0% approve that transaction and approve 00:12:48.839 --> 00:12:50.230 align:start position:0% approve that transaction and approve another<00:12:49.079> one<00:12:49.480> and<00:12:49.639> every<00:12:49.800> time<00:12:49.920> you<00:12:50.040> want<00:12:50.160> to 00:12:50.230 --> 00:12:50.240 align:start position:0% another one and every time you want to 00:12:50.240 --> 00:12:51.590 align:start position:0% another one and every time you want to do<00:12:50.399> anything<00:12:50.720> you<00:12:50.800> have<00:12:50.920> to<00:12:51.079> approve<00:12:51.360> all<00:12:51.480> of 00:12:51.590 --> 00:12:51.600 align:start position:0% do anything you have to approve all of 00:12:51.600 --> 00:12:53.790 align:start position:0% do anything you have to approve all of those<00:12:52.040> transactions<00:12:53.040> and<00:12:53.320> we<00:12:53.440> don't<00:12:53.600> want 00:12:53.790 --> 00:12:53.800 align:start position:0% those transactions and we don't want 00:12:53.800 --> 00:12:55.350 align:start position:0% those transactions and we don't want that<00:12:53.959> for<00:12:54.120> our<00:12:54.320> games<00:12:54.600> at<00:12:54.720> least<00:12:54.959> like<00:12:55.160> while 00:12:55.350 --> 00:12:55.360 align:start position:0% that for our games at least like while 00:12:55.360 --> 00:12:56.590 align:start position:0% that for our games at least like while when<00:12:55.440> you're<00:12:55.600> logged<00:12:55.880> in<00:12:56.000> we<00:12:56.120> don't<00:12:56.240> want<00:12:56.320> to 00:12:56.590 --> 00:12:56.600 align:start position:0% when you're logged in we don't want to 00:12:56.600 --> 00:12:59.629 align:start position:0% when you're logged in we don't want to hit<00:12:56.760> approve<00:12:57.120> every<00:12:57.399> time<00:12:58.399> and<00:12:58.560> so 00:12:59.629 --> 00:12:59.639 align:start position:0% hit approve every time and so 00:12:59.639 --> 00:13:01.189 align:start position:0% hit approve every time and so there<00:13:00.000> there<00:13:00.160> already<00:13:00.480> is<00:13:00.639> the<00:13:00.800> foundation 00:13:01.189 --> 00:13:01.199 align:start position:0% there there already is the foundation 00:13:01.199 --> 00:13:03.829 align:start position:0% there there already is the foundation for<00:13:01.440> very<00:13:01.639> smart<00:13:02.320> very<00:13:02.519> smooth<00:13:02.839> onboarding<00:13:03.720> in 00:13:03.829 --> 00:13:03.839 align:start position:0% for very smart very smooth onboarding in 00:13:03.839 --> 00:13:07.350 align:start position:0% for very smart very smooth onboarding in the<00:13:04.000> contracts<00:13:04.440> of<00:13:04.600> mud<00:13:05.760> but<00:13:06.760> we<00:13:06.920> can<00:13:07.040> take<00:13:07.240> it 00:13:07.350 --> 00:13:07.360 align:start position:0% the contracts of mud but we can take it 00:13:07.360 --> 00:13:09.150 align:start position:0% the contracts of mud but we can take it further<00:13:07.760> with<00:13:08.120> like<00:13:08.279> client<00:13:08.600> side<00:13:08.720> libraries 00:13:09.150 --> 00:13:09.160 align:start position:0% further with like client side libraries 00:13:09.160 --> 00:13:10.949 align:start position:0% further with like client side libraries and<00:13:09.440> deeper<00:13:09.760> integration<00:13:10.320> with<00:13:10.480> smart 00:13:10.949 --> 00:13:10.959 align:start position:0% and deeper integration with smart 00:13:10.959 --> 00:13:14.230 align:start position:0% and deeper integration with smart accounts<00:13:11.959> so<00:13:12.760> um<00:13:12.959> what<00:13:13.120> M<00:13:13.560> already<00:13:13.800> allows<00:13:14.079> you 00:13:14.230 --> 00:13:14.240 align:start position:0% accounts so um what M already allows you 00:13:14.240 --> 00:13:15.990 align:start position:0% accounts so um what M already allows you is<00:13:14.360> to<00:13:14.519> create<00:13:14.959> you<00:13:15.079> know<00:13:15.279> a<00:13:15.399> session<00:13:15.680> wallet 00:13:15.990 --> 00:13:16.000 align:start position:0% is to create you know a session wallet 00:13:16.000 --> 00:13:18.110 align:start position:0% is to create you know a session wallet and<00:13:16.079> then<00:13:16.240> create<00:13:16.440> a<00:13:16.560> scope<00:13:16.959> delegation<00:13:17.959> um 00:13:18.110 --> 00:13:18.120 align:start position:0% and then create a scope delegation um 00:13:18.120 --> 00:13:19.829 align:start position:0% and then create a scope delegation um and<00:13:18.240> then<00:13:18.440> avoid<00:13:18.760> that<00:13:18.920> approval<00:13:19.320> popup<00:13:19.680> and 00:13:19.829 --> 00:13:19.839 align:start position:0% and then avoid that approval popup and 00:13:19.839 --> 00:13:22.509 align:start position:0% and then avoid that approval popup and here's<00:13:20.079> what<00:13:20.199> it<00:13:20.320> looks<00:13:20.600> like<00:13:21.360> in<00:13:21.560> action 00:13:22.509 --> 00:13:22.519 align:start position:0% here's what it looks like in action 00:13:22.519 --> 00:13:24.550 align:start position:0% here's what it looks like in action hopefully<00:13:22.920> that<00:13:23.040> one 00:13:24.550 --> 00:13:24.560 align:start position:0% hopefully that one 00:13:24.560 --> 00:13:27.069 align:start position:0% hopefully that one loads<00:13:25.560> so<00:13:25.760> you<00:13:25.839> can<00:13:26.000> see<00:13:26.399> you<00:13:26.560> can<00:13:26.839> you<00:13:26.920> could 00:13:27.069 --> 00:13:27.079 align:start position:0% loads so you can see you can you could 00:13:27.079 --> 00:13:28.590 align:start position:0% loads so you can see you can you could connect<00:13:27.360> a<00:13:27.480> wallet<00:13:27.760> here<00:13:28.040> or<00:13:28.160> you<00:13:28.279> can<00:13:28.440> just 00:13:28.590 --> 00:13:28.600 align:start position:0% connect a wallet here or you can just 00:13:28.600 --> 00:13:30.350 align:start position:0% connect a wallet here or you can just create<00:13:28.800> a<00:13:28.880> new<00:13:29.240> wallet<00:13:29.680> if<00:13:29.800> you<00:13:29.920> don't<00:13:30.120> have<00:13:30.240> a 00:13:30.350 --> 00:13:30.360 align:start position:0% create a new wallet if you don't have a 00:13:30.360 --> 00:13:32.750 align:start position:0% create a new wallet if you don't have a wallet<00:13:30.680> yet<00:13:31.199> in<00:13:31.360> this<00:13:31.560> case<00:13:31.839> one<00:13:32.040> that's<00:13:32.480> um 00:13:32.750 --> 00:13:32.760 align:start position:0% wallet yet in this case one that's um 00:13:32.760 --> 00:13:36.069 align:start position:0% wallet yet in this case one that's um secured<00:13:33.199> by<00:13:33.600> pasy<00:13:34.600> and<00:13:34.800> then<00:13:35.320> you<00:13:35.720> get<00:13:35.880> an 00:13:36.069 --> 00:13:36.079 align:start position:0% secured by pasy and then you get an 00:13:36.079 --> 00:13:38.069 align:start position:0% secured by pasy and then you get an allowance<00:13:36.480> on<00:13:36.600> this<00:13:36.760> chain<00:13:37.079> immediately 00:13:38.069 --> 00:13:38.079 align:start position:0% allowance on this chain immediately 00:13:38.079 --> 00:13:39.790 align:start position:0% allowance on this chain immediately which<00:13:38.320> is<00:13:38.560> basically<00:13:38.920> some<00:13:39.160> some<00:13:39.320> e<00:13:39.600> that<00:13:39.720> you 00:13:39.790 --> 00:13:39.800 align:start position:0% which is basically some some e that you 00:13:39.800 --> 00:13:41.870 align:start position:0% which is basically some some e that you can<00:13:39.920> only<00:13:40.079> spend<00:13:40.320> on<00:13:40.480> actions<00:13:40.839> on<00:13:40.959> this<00:13:41.120> chain 00:13:41.870 --> 00:13:41.880 align:start position:0% can only spend on actions on this chain 00:13:41.880 --> 00:13:43.870 align:start position:0% can only spend on actions on this chain and<00:13:42.079> then<00:13:42.639> uh<00:13:42.839> you<00:13:43.079> basically<00:13:43.399> approve<00:13:43.720> the 00:13:43.870 --> 00:13:43.880 align:start position:0% and then uh you basically approve the 00:13:43.880 --> 00:13:46.430 align:start position:0% and then uh you basically approve the Del<00:13:44.279> the<00:13:44.440> delegation<00:13:45.160> scoped<00:13:45.680> and<00:13:46.000> temporary 00:13:46.430 --> 00:13:46.440 align:start position:0% Del the delegation scoped and temporary 00:13:46.440 --> 00:13:48.470 align:start position:0% Del the delegation scoped and temporary delegation<00:13:46.839> to<00:13:46.959> a<00:13:47.079> session<00:13:47.360> wallet<00:13:48.160> and<00:13:48.320> now 00:13:48.470 --> 00:13:48.480 align:start position:0% delegation to a session wallet and now 00:13:48.480 --> 00:13:50.870 align:start position:0% delegation to a session wallet and now you<00:13:48.600> can<00:13:48.959> make<00:13:49.240> moves<00:13:49.519> in<00:13:49.680> this<00:13:49.839> game<00:13:50.440> um 00:13:50.870 --> 00:13:50.880 align:start position:0% you can make moves in this game um 00:13:50.880 --> 00:13:52.470 align:start position:0% you can make moves in this game um immediately<00:13:51.440> without<00:13:51.720> having<00:13:51.920> to<00:13:52.079> click<00:13:52.320> the 00:13:52.470 --> 00:13:52.480 align:start position:0% immediately without having to click the 00:13:52.480 --> 00:13:57.350 align:start position:0% immediately without having to click the approv<00:13:52.839> button<00:13:53.360> all<00:13:53.480> the 00:13:57.350 --> 00:13:57.360 align:start position:0% 00:13:57.360 --> 00:13:59.870 align:start position:0% time<00:13:58.360> and<00:13:58.560> one<00:13:58.720> thing<00:13:58.839> you<00:13:59.160> also<00:13:59.279> saw<00:13:59.519> there<00:13:59.720> is 00:13:59.870 --> 00:13:59.880 align:start position:0% time and one thing you also saw there is 00:13:59.880 --> 00:14:02.150 align:start position:0% time and one thing you also saw there is the<00:14:00.000> fly<00:14:00.279> was<00:14:00.399> moving<00:14:00.720> pretty<00:14:01.000> fast<00:14:01.800> um<00:14:02.040> that's 00:14:02.150 --> 00:14:02.160 align:start position:0% the fly was moving pretty fast um that's 00:14:02.160 --> 00:14:03.670 align:start position:0% the fly was moving pretty fast um that's something<00:14:02.480> I'm<00:14:02.600> not<00:14:02.759> going<00:14:02.839> to<00:14:03.040> talk<00:14:03.240> about 00:14:03.670 --> 00:14:03.680 align:start position:0% something I'm not going to talk about 00:14:03.680 --> 00:14:05.189 align:start position:0% something I'm not going to talk about right<00:14:03.839> now<00:14:04.079> but<00:14:04.199> we<00:14:04.320> have<00:14:04.480> another<00:14:04.800> session 00:14:05.189 --> 00:14:05.199 align:start position:0% right now but we have another session 00:14:05.199 --> 00:14:07.870 align:start position:0% right now but we have another session later<00:14:05.480> today<00:14:05.880> that<00:14:06.040> explains<00:14:06.959> um<00:14:07.320> how<00:14:07.480> the<00:14:07.600> fly 00:14:07.870 --> 00:14:07.880 align:start position:0% later today that explains um how the fly 00:14:07.880 --> 00:14:10.749 align:start position:0% later today that explains um how the fly can<00:14:08.000> move<00:14:08.240> so<00:14:08.720> fast<00:14:09.720> um<00:14:09.920> okay<00:14:10.160> B<00:14:10.320> quick<00:14:10.480> bonus 00:14:10.749 --> 00:14:10.759 align:start position:0% can move so fast um okay B quick bonus 00:14:10.759 --> 00:14:12.350 align:start position:0% can move so fast um okay B quick bonus chapter<00:14:11.199> what's<00:14:11.399> happening<00:14:11.720> in<00:14:11.839> the<00:14:11.959> future 00:14:12.350 --> 00:14:12.360 align:start position:0% chapter what's happening in the future 00:14:12.360 --> 00:14:15.350 align:start position:0% chapter what's happening in the future after<00:14:12.639> making<00:14:12.880> it<00:14:13.120> fast<00:14:14.079> um<00:14:14.279> make<00:14:14.440> it 00:14:15.350 --> 00:14:15.360 align:start position:0% after making it fast um make it 00:14:15.360 --> 00:14:18.590 align:start position:0% after making it fast um make it scale<00:14:16.360> we<00:14:16.480> can<00:14:16.680> already<00:14:17.040> see<00:14:18.040> the<00:14:18.279> first 00:14:18.590 --> 00:14:18.600 align:start position:0% scale we can already see the first 00:14:18.600 --> 00:14:20.749 align:start position:0% scale we can already see the first worlds<00:14:19.399> that<00:14:19.519> are<00:14:19.720> starting<00:14:20.079> to<00:14:20.360> you<00:14:20.440> know 00:14:20.749 --> 00:14:20.759 align:start position:0% worlds that are starting to you know 00:14:20.759 --> 00:14:23.670 align:start position:0% worlds that are starting to you know outgrow<00:14:21.759> at<00:14:21.880> single<00:14:22.160> chains<00:14:22.600> and<00:14:22.759> we<00:14:22.920> can<00:14:23.120> see 00:14:23.670 --> 00:14:23.680 align:start position:0% outgrow at single chains and we can see 00:14:23.680 --> 00:14:25.350 align:start position:0% outgrow at single chains and we can see much<00:14:23.839> more<00:14:24.079> worlds<00:14:24.480> that<00:14:24.600> are<00:14:24.920> some<00:14:25.040> of<00:14:25.160> them 00:14:25.350 --> 00:14:25.360 align:start position:0% much more worlds that are some of them 00:14:25.360 --> 00:14:27.150 align:start position:0% much more worlds that are some of them presenting<00:14:25.720> today<00:14:26.320> that<00:14:26.399> are<00:14:26.639> basically<00:14:27.040> you 00:14:27.150 --> 00:14:27.160 align:start position:0% presenting today that are basically you 00:14:27.160 --> 00:14:29.230 align:start position:0% presenting today that are basically you know<00:14:27.279> have<00:14:27.399> a<00:14:27.519> clear<00:14:27.759> trajectory<00:14:28.399> of<00:14:28.600> outgrown 00:14:29.230 --> 00:14:29.240 align:start position:0% know have a clear trajectory of outgrown 00:14:29.240 --> 00:14:30.670 align:start position:0% know have a clear trajectory of outgrown a<00:14:29.320> single<00:14:29.519> chain<00:14:29.839> even<00:14:30.000> the<00:14:30.120> most<00:14:30.320> powerful 00:14:30.670 --> 00:14:30.680 align:start position:0% a single chain even the most powerful 00:14:30.680 --> 00:14:32.749 align:start position:0% a single chain even the most powerful single<00:14:30.920> chain<00:14:31.680> so<00:14:31.880> we<00:14:32.079> eventually<00:14:32.480> have<00:14:32.600> to 00:14:32.749 --> 00:14:32.759 align:start position:0% single chain so we eventually have to 00:14:32.759 --> 00:14:34.590 align:start position:0% single chain so we eventually have to scale<00:14:33.120> those<00:14:33.279> worlds<00:14:33.720> across<00:14:34.040> multiple 00:14:34.590 --> 00:14:34.600 align:start position:0% scale those worlds across multiple 00:14:34.600 --> 00:14:37.829 align:start position:0% scale those worlds across multiple chains<00:14:35.600> and<00:14:35.880> mud<00:14:36.240> was<00:14:36.440> always<00:14:36.720> about<00:14:37.680> um 00:14:37.829 --> 00:14:37.839 align:start position:0% chains and mud was always about um 00:14:37.839 --> 00:14:40.110 align:start position:0% chains and mud was always about um improving<00:14:38.240> the<00:14:38.399> developer<00:14:38.920> experience<00:14:39.920> um 00:14:40.110 --> 00:14:40.120 align:start position:0% improving the developer experience um 00:14:40.120 --> 00:14:42.629 align:start position:0% improving the developer experience um and<00:14:40.399> so<00:14:41.399> one<00:14:41.680> thing<00:14:41.959> that<00:14:42.240> one<00:14:42.360> thing<00:14:42.519> that 00:14:42.629 --> 00:14:42.639 align:start position:0% and so one thing that one thing that 00:14:42.639 --> 00:14:45.269 align:start position:0% and so one thing that one thing that will<00:14:42.759> be<00:14:42.880> a<00:14:43.000> big<00:14:43.160> theme<00:14:43.360> of<00:14:43.560> next<00:14:43.800> year<00:14:44.199> will<00:14:44.399> be 00:14:45.269 --> 00:14:45.279 align:start position:0% will be a big theme of next year will be 00:14:45.279 --> 00:14:47.550 align:start position:0% will be a big theme of next year will be can<00:14:45.440> we<00:14:45.839> use<00:14:46.120> mud<00:14:46.480> to<00:14:46.680> basically<00:14:47.120> abstract 00:14:47.550 --> 00:14:47.560 align:start position:0% can we use mud to basically abstract 00:14:47.560 --> 00:14:50.030 align:start position:0% can we use mud to basically abstract away<00:14:47.839> the<00:14:48.040> multi-chain<00:14:49.000> develop<00:14:49.560> experience 00:14:50.030 --> 00:14:50.040 align:start position:0% away the multi-chain develop experience 00:14:50.040 --> 00:14:51.030 align:start position:0% away the multi-chain develop experience and<00:14:50.160> just<00:14:50.320> make<00:14:50.480> it<00:14:50.600> feel<00:14:50.800> like<00:14:50.920> you're 00:14:51.030 --> 00:14:51.040 align:start position:0% and just make it feel like you're 00:14:51.040 --> 00:14:52.829 align:start position:0% and just make it feel like you're building<00:14:51.320> on<00:14:51.399> a<00:14:51.519> single<00:14:51.759> chain<00:14:52.399> but<00:14:52.600> have<00:14:52.720> the 00:14:52.829 --> 00:14:52.839 align:start position:0% building on a single chain but have the 00:14:52.839 --> 00:14:55.870 align:start position:0% building on a single chain but have the ability<00:14:53.240> to<00:14:53.399> scale<00:14:53.839> across<00:14:54.160> multiple 00:14:55.870 --> 00:14:55.880 align:start position:0% ability to scale across multiple 00:14:55.880 --> 00:14:57.829 align:start position:0% ability to scale across multiple chains<00:14:56.880> all<00:14:57.000> right<00:14:57.279> with<00:14:57.440> that<00:14:57.639> we've 00:14:57.829 --> 00:14:57.839 align:start position:0% chains all right with that we've 00:14:57.839 --> 00:14:59.749 align:start position:0% chains all right with that we've completed<00:14:58.240> the<00:14:58.360> mud<00:14:58.560> time<00:14:58.720> travel 00:14:59.749 --> 00:14:59.759 align:start position:0% completed the mud time travel 00:14:59.759 --> 00:15:01.430 align:start position:0% completed the mud time travel and<00:15:00.000> I'm<00:15:00.160> very<00:15:00.360> excited<00:15:00.720> for<00:15:00.920> what's<00:15:01.160> next 00:15:01.430 --> 00:15:01.440 align:start position:0% and I'm very excited for what's next 00:15:01.440 --> 00:15:03.230 align:start position:0% and I'm very excited for what's next we'll<00:15:01.639> see<00:15:01.920> a<00:15:02.000> bunch<00:15:02.199> of<00:15:02.360> demos<00:15:02.759> and<00:15:02.880> then<00:15:03.040> also 00:15:03.230 --> 00:15:03.240 align:start position:0% we'll see a bunch of demos and then also 00:15:03.240 --> 00:15:05.629 align:start position:0% we'll see a bunch of demos and then also later<00:15:03.519> a<00:15:03.639> bunch<00:15:03.800> of<00:15:04.000> talks<00:15:05.000> um<00:15:05.160> and<00:15:05.240> we<00:15:05.399> have<00:15:05.480> a 00:15:05.629 --> 00:15:05.639 align:start position:0% later a bunch of talks um and we have a 00:15:05.639 --> 00:15:07.829 align:start position:0% later a bunch of talks um and we have a gaming<00:15:05.920> Corner<00:15:06.320> over<00:15:06.519> there<00:15:06.839> where<00:15:07.399> later<00:15:07.720> you 00:15:07.829 --> 00:15:07.839 align:start position:0% gaming Corner over there where later you 00:15:07.839 --> 00:15:09.470 align:start position:0% gaming Corner over there where later you can<00:15:08.000> try<00:15:08.240> out<00:15:08.480> some<00:15:08.600> of<00:15:08.720> the<00:15:08.839> Mud<00:15:09.040> Games<00:15:09.320> as 00:15:09.470 --> 00:15:09.480 align:start position:0% can try out some of the Mud Games as 00:15:09.480 --> 00:15:12.230 align:start position:0% can try out some of the Mud Games as well<00:15:10.320> um<00:15:10.480> and<00:15:10.639> then<00:15:11.160> later<00:15:11.639> I<00:15:11.720> don't<00:15:11.839> know<00:15:12.040> what 00:15:12.230 --> 00:15:12.240 align:start position:0% well um and then later I don't know what 00:15:12.240 --> 00:15:13.990 align:start position:0% well um and then later I don't know what time<00:15:12.480> but<00:15:12.880> some<00:15:13.199> something<00:15:13.440> around<00:15:13.680> one<00:15:13.880> or 00:15:13.990 --> 00:15:14.000 align:start position:0% time but some something around one or 00:15:14.000 --> 00:15:15.670 align:start position:0% time but some something around one or something<00:15:14.279> we<00:15:14.440> have<00:15:14.680> also<00:15:15.079> some<00:15:15.480> some 00:15:15.670 --> 00:15:15.680 align:start position:0% something we have also some some 00:15:15.680 --> 00:15:17.829 align:start position:0% something we have also some some announcements<00:15:16.240> to<00:15:16.399> make<00:15:17.079> um<00:15:17.199> so<00:15:17.360> be<00:15:17.480> sure<00:15:17.639> to 00:15:17.829 --> 00:15:17.839 align:start position:0% announcements to make um so be sure to 00:15:17.839 --> 00:15:19.910 align:start position:0% announcements to make um so be sure to catch<00:15:18.120> that<00:15:18.880> and<00:15:19.079> yeah<00:15:19.279> with<00:15:19.440> that<00:15:19.639> thank<00:15:19.800> you 00:15:19.910 --> 00:15:19.920 align:start position:0% catch that and yeah with that thank you 00:15:19.920 --> 00:15:23.990 align:start position:0% catch that and yeah with that thank you very<00:15:20.120> much<00:15:20.440> and<00:15:20.839> have 00:15:23.990 --> 00:15:24.000 align:start position:0% 00:15:24.000 --> 00:15:27.389 align:start position:0% fun<00:15:25.000> all<00:15:25.160> right<00:15:25.800> um<00:15:26.360> alvaris<00:15:26.839> cannot<00:15:27.120> leave 00:15:27.389 --> 00:15:27.399 align:start position:0% fun all right um alvaris cannot leave 00:15:27.399 --> 00:15:29.590 align:start position:0% fun all right um alvaris cannot leave yet<00:15:28.319> um 00:15:29.590 --> 00:15:29.600 align:start position:0% yet um 00:15:29.600 --> 00:15:31.430 align:start position:0% yet um we're<00:15:29.880> going<00:15:30.040> to<00:15:30.240> give<00:15:30.360> you<00:15:30.560> guys<00:15:30.800> about<00:15:31.040> 30 00:15:31.430 --> 00:15:31.440 align:start position:0% we're going to give you guys about 30 00:15:31.440 --> 00:15:34.829 align:start position:0% we're going to give you guys about 30 seconds<00:15:31.839> to<00:15:32.240> scan<00:15:32.560> this<00:15:32.720> QR<00:15:33.079> code<00:15:33.880> um<00:15:34.120> log<00:15:34.360> into 00:15:34.829 --> 00:15:34.839 align:start position:0% seconds to scan this QR code um log into 00:15:34.839 --> 00:15:37.430 align:start position:0% seconds to scan this QR code um log into zass<00:15:35.839> uh<00:15:35.920> you<00:15:36.040> don't<00:15:36.199> need<00:15:36.399> a<00:15:36.519> frog<00:15:37.000> for<00:15:37.240> this 00:15:37.430 --> 00:15:37.440 align:start position:0% zass uh you don't need a frog for this 00:15:37.440 --> 00:15:39.470 align:start position:0% zass uh you don't need a frog for this interaction<00:15:38.440> um<00:15:38.600> but<00:15:38.720> you<00:15:38.800> should<00:15:39.000> have<00:15:39.120> frogs 00:15:39.470 --> 00:15:39.480 align:start position:0% interaction um but you should have frogs 00:15:39.480 --> 00:15:40.870 align:start position:0% interaction um but you should have frogs if<00:15:39.560> you<00:15:39.639> don't<00:15:39.800> have<00:15:39.920> frogs<00:15:40.240> anyway<00:15:40.600> so<00:15:40.759> you 00:15:40.870 --> 00:15:40.880 align:start position:0% if you don't have frogs anyway so you 00:15:40.880 --> 00:15:42.350 align:start position:0% if you don't have frogs anyway so you scan<00:15:41.199> this<00:15:41.360> thing<00:15:41.720> and<00:15:41.839> you<00:15:41.920> can<00:15:42.079> ask 00:15:42.350 --> 00:15:42.360 align:start position:0% scan this thing and you can ask 00:15:42.360 --> 00:15:44.269 align:start position:0% scan this thing and you can ask questions<00:15:43.000> to<00:15:43.199> alvarus<00:15:43.800> they<00:15:43.880> will<00:15:44.040> appear<00:15:44.199> on 00:15:44.269 --> 00:15:44.279 align:start position:0% questions to alvarus they will appear on 00:15:44.279 --> 00:15:46.749 align:start position:0% questions to alvarus they will appear on the<00:15:44.360> screen<00:15:44.639> I<00:15:44.680> will<00:15:44.839> read<00:15:45.079> the<00:15:45.399> questions<00:15:46.399> um 00:15:46.749 --> 00:15:46.759 align:start position:0% the screen I will read the questions um 00:15:46.759 --> 00:15:48.230 align:start position:0% the screen I will read the questions um and<00:15:46.959> we'll<00:15:47.160> see<00:15:47.360> what<00:15:47.480> he<00:15:47.639> thinks<00:15:47.959> we<00:15:48.079> have 00:15:48.230 --> 00:15:48.240 align:start position:0% and we'll see what he thinks we have 00:15:48.240 --> 00:15:50.629 align:start position:0% and we'll see what he thinks we have about<00:15:48.639> two<00:15:48.880> minutes<00:15:49.199> worth<00:15:49.399> of<00:15:49.560> question<00:15:49.880> time 00:15:50.629 --> 00:15:50.639 align:start position:0% about two minutes worth of question time 00:15:50.639 --> 00:16:08.990 align:start position:0% about two minutes worth of question time so<00:15:51.000> hurry<00:15:51.279> up 00:16:08.990 --> 00:16:09.000 align:start position:0% 00:16:09.000 --> 00:16:11.949 align:start position:0% everybody's<00:16:09.480> busy<00:16:09.759> making<00:16:10.079> ZK<00:16:10.480> proofs<00:16:11.040> whoa 00:16:11.949 --> 00:16:11.959 align:start position:0% everybody's busy making ZK proofs whoa 00:16:11.959 --> 00:16:15.470 align:start position:0% everybody's busy making ZK proofs whoa okay<00:16:12.959> first<00:16:13.319> question<00:16:14.319> are<00:16:14.519> there<00:16:14.720> any<00:16:15.120> plans 00:16:15.470 --> 00:16:15.480 align:start position:0% okay first question are there any plans 00:16:15.480 --> 00:16:17.710 align:start position:0% okay first question are there any plans to<00:16:15.680> make<00:16:15.880> mud<00:16:16.160> use<00:16:16.440> less<00:16:16.680> gas 00:16:17.710 --> 00:16:17.720 align:start position:0% to make mud use less gas 00:16:17.720 --> 00:16:22.870 align:start position:0% to make mud use less gas alvarus<00:16:18.720> that's<00:16:18.880> a<00:16:19.079> great<00:16:19.360> question 00:16:22.870 --> 00:16:22.880 align:start position:0% 00:16:22.880 --> 00:16:25.590 align:start position:0% um<00:16:23.880> so<00:16:24.120> we<00:16:24.279> spent<00:16:24.600> already<00:16:24.880> a<00:16:25.000> lot<00:16:25.120> of<00:16:25.319> lot<00:16:25.480> of 00:16:25.590 --> 00:16:25.600 align:start position:0% um so we spent already a lot of lot of 00:16:25.600 --> 00:16:27.389 align:start position:0% um so we spent already a lot of lot of time<00:16:25.880> making<00:16:26.120> mud<00:16:26.360> two<00:16:26.720> much<00:16:26.959> more<00:16:27.199> gas 00:16:27.389 --> 00:16:27.399 align:start position:0% time making mud two much more gas 00:16:27.399 --> 00:16:29.150 align:start position:0% time making mud two much more gas efficient<00:16:27.680> than<00:16:27.800> mud<00:16:28.040> one<00:16:28.480> and<00:16:28.720> now<00:16:28.920> now<00:16:29.000> we're 00:16:29.150 --> 00:16:29.160 align:start position:0% efficient than mud one and now now we're 00:16:29.160 --> 00:16:31.309 align:start position:0% efficient than mud one and now now we're at<00:16:29.279> the<00:16:29.399> point<00:16:29.639> where<00:16:29.839> if<00:16:29.920> you<00:16:30.079> use<00:16:30.319> mud<00:16:30.680> to<00:16:31.120> do 00:16:31.309 --> 00:16:31.319 align:start position:0% at the point where if you use mud to do 00:16:31.319 --> 00:16:33.870 align:start position:0% at the point where if you use mud to do the<00:16:31.519> things<00:16:32.319> you<00:16:32.880> you<00:16:33.000> know<00:16:33.240> like<00:16:33.639> if<00:16:33.759> you 00:16:33.870 --> 00:16:33.880 align:start position:0% the things you you know like if you 00:16:33.880 --> 00:16:36.509 align:start position:0% the things you you know like if you would<00:16:34.360> build<00:16:34.600> an<00:16:34.800> app<00:16:35.279> from<00:16:35.480> scratch<00:16:36.319> and<00:16:36.440> you 00:16:36.509 --> 00:16:36.519 align:start position:0% would build an app from scratch and you 00:16:36.519 --> 00:16:38.550 align:start position:0% would build an app from scratch and you would<00:16:36.639> set<00:16:36.880> the<00:16:37.000> storage<00:16:37.519> and<00:16:37.639> you<00:16:37.759> would<00:16:38.440> um 00:16:38.550 --> 00:16:38.560 align:start position:0% would set the storage and you would um 00:16:38.560 --> 00:16:41.069 align:start position:0% would set the storage and you would um emit<00:16:38.800> an<00:16:38.959> event<00:16:39.720> um<00:16:40.279> you<00:16:40.399> know<00:16:40.560> to<00:16:40.680> sync<00:16:40.959> the 00:16:41.069 --> 00:16:41.079 align:start position:0% emit an event um you know to sync the 00:16:41.079 --> 00:16:42.990 align:start position:0% emit an event um you know to sync the state<00:16:41.360> on<00:16:41.480> the<00:16:41.600> client<00:16:42.319> it's<00:16:42.480> not<00:16:42.639> going<00:16:42.720> to<00:16:42.880> be 00:16:42.990 --> 00:16:43.000 align:start position:0% state on the client it's not going to be 00:16:43.000 --> 00:16:44.470 align:start position:0% state on the client it's not going to be much<00:16:43.160> more<00:16:43.399> gas<00:16:43.639> efficient<00:16:44.040> actually<00:16:44.319> than 00:16:44.470 --> 00:16:44.480 align:start position:0% much more gas efficient actually than 00:16:44.480 --> 00:16:46.629 align:start position:0% much more gas efficient actually than than<00:16:44.600> to<00:16:44.720> use<00:16:45.000> mod<00:16:45.639> um<00:16:45.759> so<00:16:45.920> it<00:16:46.079> might<00:16:46.240> seem<00:16:46.519> like 00:16:46.629 --> 00:16:46.639 align:start position:0% than to use mod um so it might seem like 00:16:46.639 --> 00:16:48.550 align:start position:0% than to use mod um so it might seem like it's<00:16:46.759> using<00:16:47.040> more<00:16:47.360> gas<00:16:47.959> but<00:16:48.120> that's<00:16:48.360> just 00:16:48.550 --> 00:16:48.560 align:start position:0% it's using more gas but that's just 00:16:48.560 --> 00:16:49.670 align:start position:0% it's using more gas but that's just because<00:16:48.800> there's<00:16:48.959> so<00:16:49.079> much<00:16:49.240> stuff<00:16:49.480> that<00:16:49.600> you 00:16:49.670 --> 00:16:49.680 align:start position:0% because there's so much stuff that you 00:16:49.680 --> 00:16:51.430 align:start position:0% because there's so much stuff that you know<00:16:49.880> comes<00:16:50.279> by<00:16:50.440> default<00:16:50.759> out<00:16:50.880> of<00:16:51.000> the<00:16:51.160> box 00:16:51.430 --> 00:16:51.440 align:start position:0% know comes by default out of the box 00:16:51.440 --> 00:16:52.910 align:start position:0% know comes by default out of the box that<00:16:51.560> you<00:16:51.680> would<00:16:51.880> have<00:16:52.000> to<00:16:52.160> implement 00:16:52.910 --> 00:16:52.920 align:start position:0% that you would have to implement 00:16:52.920 --> 00:16:54.629 align:start position:0% that you would have to implement yourself<00:16:53.279> and<00:16:53.440> solidity<00:16:54.120> if<00:16:54.279> you<00:16:54.480> if<00:16:54.560> you 00:16:54.629 --> 00:16:54.639 align:start position:0% yourself and solidity if you if you 00:16:54.639 --> 00:16:56.870 align:start position:0% yourself and solidity if you if you wanted<00:16:54.880> to<00:16:55.000> get<00:16:55.120> to<00:16:55.279> the<00:16:55.440> same<00:16:56.319> um 00:16:56.870 --> 00:16:56.880 align:start position:0% wanted to get to the same um 00:16:56.880 --> 00:16:59.430 align:start position:0% wanted to get to the same um functionality<00:16:57.880> so<00:16:58.519> um<00:16:58.680> while<00:16:58.959> we<00:16:59.120> always<00:16:59.319> you 00:16:59.430 --> 00:16:59.440 align:start position:0% functionality so um while we always you 00:16:59.440 --> 00:17:01.710 align:start position:0% functionality so um while we always you know<00:17:00.000> optimize<00:17:00.480> the<00:17:00.639> stuff<00:17:00.920> it's<00:17:01.120> it's<00:17:01.240> not<00:17:01.480> as 00:17:01.710 --> 00:17:01.720 align:start position:0% know optimize the stuff it's it's not as 00:17:01.720 --> 00:17:03.150 align:start position:0% know optimize the stuff it's it's not as gas<00:17:01.959> inefficient<00:17:02.480> as<00:17:02.600> you<00:17:02.800> as<00:17:02.920> you<00:17:03.000> might 00:17:03.150 --> 00:17:03.160 align:start position:0% gas inefficient as you as you might 00:17:03.160 --> 00:17:05.870 align:start position:0% gas inefficient as you as you might think<00:17:03.319> on<00:17:03.519> first<00:17:03.759> side<00:17:04.520> thank<00:17:04.720> you<00:17:05.480> um<00:17:05.720> the 00:17:05.870 --> 00:17:05.880 align:start position:0% think on first side thank you um the 00:17:05.880 --> 00:17:08.270 align:start position:0% think on first side thank you um the other<00:17:06.520> the<00:17:06.640> next<00:17:06.919> most<00:17:07.199> upvoted<00:17:07.720> question<00:17:08.000> is 00:17:08.270 --> 00:17:08.280 align:start position:0% other the next most upvoted question is 00:17:08.280 --> 00:17:11.029 align:start position:0% other the next most upvoted question is sorry<00:17:09.079> I<00:17:09.160> am<00:17:09.280> a<00:17:09.400> noob<00:17:10.240> thanks<00:17:10.439> for<00:17:10.600> coming<00:17:10.919> by 00:17:11.029 --> 00:17:11.039 align:start position:0% sorry I am a noob thanks for coming by 00:17:11.039 --> 00:17:12.390 align:start position:0% sorry I am a noob thanks for coming by the<00:17:11.160> way<00:17:11.280> if<00:17:11.360> you're<00:17:11.520> a<00:17:11.600> noob<00:17:12.120> uh<00:17:12.240> we 00:17:12.390 --> 00:17:12.400 align:start position:0% the way if you're a noob uh we 00:17:12.400 --> 00:17:14.110 align:start position:0% the way if you're a noob uh we appreciate<00:17:13.240> why<00:17:13.360> is<00:17:13.480> it<00:17:13.600> good<00:17:13.760> to<00:17:13.919> put 00:17:14.110 --> 00:17:14.120 align:start position:0% appreciate why is it good to put 00:17:14.120 --> 00:17:17.510 align:start position:0% appreciate why is it good to put movements<00:17:14.559> on<00:17:14.880> chain<00:17:15.160> for 00:17:17.510 --> 00:17:17.520 align:start position:0% 00:17:17.520 --> 00:17:20.029 align:start position:0% example<00:17:18.520> it's<00:17:18.839> essentially<00:17:19.600> I<00:17:19.640> mean<00:17:19.839> it's 00:17:20.029 --> 00:17:20.039 align:start position:0% example it's essentially I mean it's 00:17:20.039 --> 00:17:21.470 align:start position:0% example it's essentially I mean it's it's<00:17:20.319> almost<00:17:20.559> like<00:17:20.679> a<00:17:20.839> philosophical 00:17:21.470 --> 00:17:21.480 align:start position:0% it's almost like a philosophical 00:17:21.480 --> 00:17:22.990 align:start position:0% it's almost like a philosophical question<00:17:21.760> but<00:17:21.919> the<00:17:22.000> more<00:17:22.240> stuff<00:17:22.439> you<00:17:22.600> put<00:17:22.760> on 00:17:22.990 --> 00:17:23.000 align:start position:0% question but the more stuff you put on 00:17:23.000 --> 00:17:25.429 align:start position:0% question but the more stuff you put on chain<00:17:23.799> the<00:17:23.919> more<00:17:24.319> Downstream<00:17:24.919> Integrations 00:17:25.429 --> 00:17:25.439 align:start position:0% chain the more Downstream Integrations 00:17:25.439 --> 00:17:27.270 align:start position:0% chain the more Downstream Integrations you<00:17:25.600> enable<00:17:26.039> because<00:17:26.480> it's<00:17:26.720> it's<00:17:26.880> like<00:17:27.039> a<00:17:27.160> you 00:17:27.270 --> 00:17:27.280 align:start position:0% you enable because it's it's like a you 00:17:27.280 --> 00:17:28.470 align:start position:0% you enable because it's it's like a you know<00:17:27.360> you're<00:17:27.520> deploying<00:17:27.880> to<00:17:28.039> this<00:17:28.199> public 00:17:28.470 --> 00:17:28.480 align:start position:0% know you're deploying to this public 00:17:28.480 --> 00:17:30.310 align:start position:0% know you're deploying to this public computer<00:17:29.280> and<00:17:29.440> this<00:17:29.640> public<00:17:30.039> you<00:17:30.120> know 00:17:30.310 --> 00:17:30.320 align:start position:0% computer and this public you know 00:17:30.320 --> 00:17:31.830 align:start position:0% computer and this public you know database<00:17:30.760> that<00:17:30.919> anybody<00:17:31.280> else<00:17:31.480> can<00:17:31.640> also 00:17:31.830 --> 00:17:31.840 align:start position:0% database that anybody else can also 00:17:31.840 --> 00:17:34.510 align:start position:0% database that anybody else can also deploy<00:17:32.160> to<00:17:32.679> and<00:17:32.840> the<00:17:33.000> more<00:17:33.200> stuff<00:17:33.440> is<00:17:33.679> in<00:17:33.919> there 00:17:34.510 --> 00:17:34.520 align:start position:0% deploy to and the more stuff is in there 00:17:34.520 --> 00:17:36.669 align:start position:0% deploy to and the more stuff is in there the<00:17:34.679> more<00:17:35.280> can<00:17:35.480> be<00:17:35.640> used<00:17:35.919> for<00:17:36.160> Downstream 00:17:36.669 --> 00:17:36.679 align:start position:0% the more can be used for Downstream 00:17:36.679 --> 00:17:38.150 align:start position:0% the more can be used for Downstream integration<00:17:37.280> so<00:17:37.520> let's<00:17:37.679> say<00:17:37.799> you<00:17:37.919> put 00:17:38.150 --> 00:17:38.160 align:start position:0% integration so let's say you put 00:17:38.160 --> 00:17:40.470 align:start position:0% integration so let's say you put movements<00:17:38.600> on<00:17:38.760> chain<00:17:39.640> um<00:17:39.799> now<00:17:40.039> somebody<00:17:40.320> could 00:17:40.470 --> 00:17:40.480 align:start position:0% movements on chain um now somebody could 00:17:40.480 --> 00:17:42.630 align:start position:0% movements on chain um now somebody could build<00:17:40.640> an<00:17:40.960> integration<00:17:41.600> that<00:17:41.960> you<00:17:42.080> know<00:17:42.360> does 00:17:42.630 --> 00:17:42.640 align:start position:0% build an integration that you know does 00:17:42.640 --> 00:17:44.110 align:start position:0% build an integration that you know does something<00:17:43.120> if<00:17:43.240> you<00:17:43.360> move<00:17:43.600> to<00:17:43.760> a<00:17:43.840> certain 00:17:44.110 --> 00:17:44.120 align:start position:0% something if you move to a certain 00:17:44.120 --> 00:17:45.310 align:start position:0% something if you move to a certain position<00:17:44.480> that<00:17:44.559> wouldn't<00:17:44.799> be<00:17:44.960> possible<00:17:45.240> if 00:17:45.310 --> 00:17:45.320 align:start position:0% position that wouldn't be possible if 00:17:45.320 --> 00:17:46.830 align:start position:0% position that wouldn't be possible if you<00:17:45.440> don't<00:17:45.559> put<00:17:45.720> movements<00:17:46.039> on 00:17:46.830 --> 00:17:46.840 align:start position:0% you don't put movements on 00:17:46.840 --> 00:17:49.150 align:start position:0% you don't put movements on chain<00:17:47.840> thank<00:17:48.000> you<00:17:48.120> alvarus<00:17:48.600> another<00:17:48.799> round<00:17:49.000> of 00:17:49.150 --> 00:17:49.160 align:start position:0% chain thank you alvarus another round of 00:17:49.160 --> 00:17:52.880 align:start position:0% chain thank you alvarus another round of applause<00:17:49.880> please