WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:10.070 align:start position:0% [Music] 00:00:10.070 --> 00:00:10.080 align:start position:0% [Music] 00:00:10.080 --> 00:00:12.549 align:start position:0% [Music] all<00:00:10.320> right<00:00:10.800> my<00:00:11.000> name<00:00:11.160> is<00:00:11.360> tiat<00:00:11.920> I'm<00:00:12.000> a<00:00:12.160> software 00:00:12.549 --> 00:00:12.559 align:start position:0% all right my name is tiat I'm a software 00:00:12.559 --> 00:00:14.230 align:start position:0% all right my name is tiat I'm a software engineer<00:00:13.160> at 00:00:14.230 --> 00:00:14.240 align:start position:0% engineer at 00:00:14.240 --> 00:00:18.029 align:start position:0% engineer at Lis<00:00:15.240> um<00:00:16.080> and<00:00:16.680> um<00:00:17.119> yeah<00:00:17.279> I'm<00:00:17.400> about<00:00:17.600> to<00:00:17.800> talk 00:00:18.029 --> 00:00:18.039 align:start position:0% Lis um and um yeah I'm about to talk 00:00:18.039 --> 00:00:20.550 align:start position:0% Lis um and um yeah I'm about to talk about<00:00:18.600> bring<00:00:18.880> you<00:00:19.000> on<00:00:19.119> our<00:00:19.279> journey<00:00:20.199> uh 00:00:20.550 --> 00:00:20.560 align:start position:0% about bring you on our journey uh 00:00:20.560 --> 00:00:21.870 align:start position:0% about bring you on our journey uh basically<00:00:20.960> building<00:00:21.439> the<00:00:21.600> best 00:00:21.870 --> 00:00:21.880 align:start position:0% basically building the best 00:00:21.880 --> 00:00:24.070 align:start position:0% basically building the best infrastructure<00:00:22.480> for<00:00:22.920> autonomous<00:00:23.480> worlds<00:00:23.880> and 00:00:24.070 --> 00:00:24.080 align:start position:0% infrastructure for autonomous worlds and 00:00:24.080 --> 00:00:27.349 align:start position:0% infrastructure for autonomous worlds and mud 00:00:27.349 --> 00:00:27.359 align:start position:0% 00:00:27.359 --> 00:00:32.069 align:start position:0% apps<00:00:28.359> okay<00:00:29.240> um<00:00:29.679> so<00:00:30.240> so<00:00:31.240> I<00:00:31.359> will<00:00:31.599> start<00:00:31.920> by 00:00:32.069 --> 00:00:32.079 align:start position:0% apps okay um so so I will start by 00:00:32.079 --> 00:00:33.190 align:start position:0% apps okay um so so I will start by talking<00:00:32.320> a<00:00:32.399> little<00:00:32.559> bit<00:00:32.719> bringing<00:00:33.000> a<00:00:33.079> little 00:00:33.190 --> 00:00:33.200 align:start position:0% talking a little bit bringing a little 00:00:33.200 --> 00:00:35.670 align:start position:0% talking a little bit bringing a little bit<00:00:33.320> of<00:00:33.559> context<00:00:34.559> uh<00:00:34.879> for<00:00:35.160> those<00:00:35.320> who<00:00:35.480> don't 00:00:35.670 --> 00:00:35.680 align:start position:0% bit of context uh for those who don't 00:00:35.680 --> 00:00:37.990 align:start position:0% bit of context uh for those who don't know<00:00:35.879> what<00:00:36.040> mud<00:00:36.399> is<00:00:36.559> and<00:00:37.040> what<00:00:37.160> are<00:00:37.480> autonomous 00:00:37.990 --> 00:00:38.000 align:start position:0% know what mud is and what are autonomous 00:00:38.000 --> 00:00:41.029 align:start position:0% know what mud is and what are autonomous worlds<00:00:39.000> I<00:00:39.120> will<00:00:39.399> then<00:00:39.719> kind<00:00:39.840> of<00:00:40.360> describe<00:00:40.760> some 00:00:41.029 --> 00:00:41.039 align:start position:0% worlds I will then kind of describe some 00:00:41.039 --> 00:00:44.310 align:start position:0% worlds I will then kind of describe some design<00:00:41.440> patterns<00:00:42.079> that<00:00:42.280> we<00:00:42.960> um<00:00:43.160> learned<00:00:43.600> about 00:00:44.310 --> 00:00:44.320 align:start position:0% design patterns that we um learned about 00:00:44.320 --> 00:00:47.389 align:start position:0% design patterns that we um learned about while<00:00:44.520> we<00:00:44.640> were<00:00:44.920> fa<00:00:45.480> uh<00:00:46.480> essentially<00:00:46.879> solving 00:00:47.389 --> 00:00:47.399 align:start position:0% while we were fa uh essentially solving 00:00:47.399 --> 00:00:50.110 align:start position:0% while we were fa uh essentially solving problems<00:00:47.879> for<00:00:48.120> mud<00:00:48.440> apps<00:00:49.399> uh<00:00:49.520> and<00:00:49.680> how 00:00:50.110 --> 00:00:50.120 align:start position:0% problems for mud apps uh and how 00:00:50.120 --> 00:00:52.189 align:start position:0% problems for mud apps uh and how basically<00:00:50.440> we<00:00:50.600> solve<00:00:50.920> them<00:00:51.760> uh<00:00:51.840> and<00:00:51.960> then<00:00:52.079> I'll 00:00:52.189 --> 00:00:52.199 align:start position:0% basically we solve them uh and then I'll 00:00:52.199 --> 00:00:54.549 align:start position:0% basically we solve them uh and then I'll be<00:00:52.440> describing<00:00:53.440> uh<00:00:53.559> a<00:00:53.680> new<00:00:53.960> system<00:00:54.280> that<00:00:54.399> we're 00:00:54.549 --> 00:00:54.559 align:start position:0% be describing uh a new system that we're 00:00:54.559 --> 00:00:56.349 align:start position:0% be describing uh a new system that we're prototyping<00:00:55.559> uh<00:00:55.640> you<00:00:55.719> might<00:00:55.879> have<00:00:56.000> gotten<00:00:56.239> a 00:00:56.349 --> 00:00:56.359 align:start position:0% prototyping uh you might have gotten a 00:00:56.359 --> 00:00:59.349 align:start position:0% prototyping uh you might have gotten a sneak<00:00:56.760> peek<00:00:57.199> already<00:00:57.840> if<00:00:57.960> you<00:00:58.519> catch<00:00:59.160> if<00:00:59.239> you 00:00:59.349 --> 00:00:59.359 align:start position:0% sneak peek already if you catch if you 00:00:59.359 --> 00:01:04.390 align:start position:0% sneak peek already if you catch if you caught<00:01:00.120> alvarus<00:01:00.719> talk<00:01:01.359> earlier<00:01:02.359> um<00:01:02.600> on<00:01:02.800> mud<00:01:03.400> so 00:01:04.390 --> 00:01:04.400 align:start position:0% caught alvarus talk earlier um on mud so 00:01:04.400 --> 00:01:06.670 align:start position:0% caught alvarus talk earlier um on mud so yeah<00:01:04.799> stay 00:01:06.670 --> 00:01:06.680 align:start position:0% yeah stay 00:01:06.680 --> 00:01:10.350 align:start position:0% yeah stay tuned<00:01:07.680> okay<00:01:08.600> um<00:01:08.960> so<00:01:09.560> if<00:01:09.640> you're<00:01:09.799> not<00:01:10.000> familiar 00:01:10.350 --> 00:01:10.360 align:start position:0% tuned okay um so if you're not familiar 00:01:10.360 --> 00:01:12.990 align:start position:0% tuned okay um so if you're not familiar with<00:01:10.520> lattice<00:01:11.320> uh<00:01:11.439> we've<00:01:11.600> been<00:01:11.880> promoting<00:01:12.720> a 00:01:12.990 --> 00:01:13.000 align:start position:0% with lattice uh we've been promoting a 00:01:13.000 --> 00:01:15.190 align:start position:0% with lattice uh we've been promoting a vision<00:01:13.320> for<00:01:13.520> launching<00:01:14.000> games<00:01:14.400> to<00:01:14.840> basically 00:01:15.190 --> 00:01:15.200 align:start position:0% vision for launching games to basically 00:01:15.200 --> 00:01:16.870 align:start position:0% vision for launching games to basically develop<00:01:15.680> properties<00:01:16.119> of<00:01:16.240> a<00:01:16.400> thing<00:01:16.600> that<00:01:16.720> we 00:01:16.870 --> 00:01:16.880 align:start position:0% develop properties of a thing that we 00:01:16.880 --> 00:01:20.390 align:start position:0% develop properties of a thing that we call<00:01:17.320> autonomous<00:01:18.200> world<00:01:19.200> uh<00:01:19.360> who<00:01:19.520> knows<00:01:20.159> who 00:01:20.390 --> 00:01:20.400 align:start position:0% call autonomous world uh who knows who 00:01:20.400 --> 00:01:22.710 align:start position:0% call autonomous world uh who knows who here<00:01:20.640> knows<00:01:21.040> what<00:01:21.400> autonomous<00:01:21.920> world<00:01:22.240> is<00:01:22.439> or 00:01:22.710 --> 00:01:22.720 align:start position:0% here knows what autonomous world is or 00:01:22.720 --> 00:01:25.429 align:start position:0% here knows what autonomous world is or has<00:01:22.880> an<00:01:23.159> idea<00:01:24.159> okay<00:01:24.520> that's<00:01:24.880> quite<00:01:25.040> a<00:01:25.159> lot<00:01:25.280> of 00:01:25.429 --> 00:01:25.439 align:start position:0% has an idea okay that's quite a lot of 00:01:25.439 --> 00:01:27.469 align:start position:0% has an idea okay that's quite a lot of people<00:01:25.880> who<00:01:26.040> knows<00:01:26.280> about 00:01:27.469 --> 00:01:27.479 align:start position:0% people who knows about 00:01:27.479 --> 00:01:30.910 align:start position:0% people who knows about mud<00:01:28.479> all<00:01:28.640> right<00:01:29.360> that<00:01:29.680> that's<00:01:29.920> it's<00:01:30.079> good<00:01:30.759> uh 00:01:30.910 --> 00:01:30.920 align:start position:0% mud all right that that's it's good uh 00:01:30.920 --> 00:01:33.190 align:start position:0% mud all right that that's it's good uh but<00:01:31.079> so<00:01:31.240> we're<00:01:31.400> all<00:01:31.560> on<00:01:31.720> the<00:01:31.840> same<00:01:32.119> page<00:01:32.960> um 00:01:33.190 --> 00:01:33.200 align:start position:0% but so we're all on the same page um 00:01:33.200 --> 00:01:37.350 align:start position:0% but so we're all on the same page um I'll<00:01:33.399> give<00:01:33.720> my<00:01:33.920> quick<00:01:34.159> definition<00:01:34.560> of<00:01:34.720> it<00:01:35.720> um 00:01:37.350 --> 00:01:37.360 align:start position:0% I'll give my quick definition of it um 00:01:37.360 --> 00:01:41.710 align:start position:0% I'll give my quick definition of it um essentially<00:01:38.360> um<00:01:39.240> whoa<00:01:39.759> things<00:01:39.960> are<00:01:40.119> moving<00:01:41.040> um 00:01:41.710 --> 00:01:41.720 align:start position:0% essentially um whoa things are moving um 00:01:41.720 --> 00:01:43.510 align:start position:0% essentially um whoa things are moving um so<00:01:42.119> when<00:01:42.240> I<00:01:42.320> say<00:01:42.479> autonomous<00:01:42.920> worlds<00:01:43.320> what<00:01:43.439> I 00:01:43.510 --> 00:01:43.520 align:start position:0% so when I say autonomous worlds what I 00:01:43.520 --> 00:01:45.469 align:start position:0% so when I say autonomous worlds what I mean<00:01:43.720> is<00:01:43.960> like<00:01:44.280> permissionless<00:01:45.119> Virtual 00:01:45.469 --> 00:01:45.479 align:start position:0% mean is like permissionless Virtual 00:01:45.479 --> 00:01:48.429 align:start position:0% mean is like permissionless Virtual Worlds<00:01:45.880> that<00:01:46.000> are<00:01:46.119> seated<00:01:46.600> by<00:01:47.079> initial<00:01:47.600> teams 00:01:48.429 --> 00:01:48.439 align:start position:0% Worlds that are seated by initial teams 00:01:48.439 --> 00:01:50.510 align:start position:0% Worlds that are seated by initial teams who<00:01:48.560> are<00:01:48.719> then<00:01:48.920> joined<00:01:49.360> by<00:01:49.600> early<00:01:50.000> adopters 00:01:50.510 --> 00:01:50.520 align:start position:0% who are then joined by early adopters 00:01:50.520 --> 00:01:52.630 align:start position:0% who are then joined by early adopters who<00:01:50.680> build<00:01:50.960> on<00:01:51.119> top<00:01:51.280> of<00:01:51.399> it<00:01:51.600> until<00:01:51.880> the<00:01:52.079> plot 00:01:52.630 --> 00:01:52.640 align:start position:0% who build on top of it until the plot 00:01:52.640 --> 00:01:54.749 align:start position:0% who build on top of it until the plot evolves<00:01:53.079> Beyond<00:01:53.520> anyone's<00:01:53.960> single<00:01:54.320> control 00:01:54.749 --> 00:01:54.759 align:start position:0% evolves Beyond anyone's single control 00:01:54.759 --> 00:01:56.830 align:start position:0% evolves Beyond anyone's single control and<00:01:54.880> then<00:01:55.159> complex<00:01:55.680> drama<00:01:56.240> and<00:01:56.439> social 00:01:56.830 --> 00:01:56.840 align:start position:0% and then complex drama and social 00:01:56.840 --> 00:02:00.109 align:start position:0% and then complex drama and social components<00:01:57.759> emerge<00:01:58.759> um<00:01:58.960> and<00:01:59.079> to<00:01:59.240> enable 00:02:00.109 --> 00:02:00.119 align:start position:0% components emerge um and to enable 00:02:00.119 --> 00:02:02.310 align:start position:0% components emerge um and to enable worlds<00:02:00.399> we've<00:02:00.560> built<00:02:00.799> mud<00:02:01.280> on<00:02:01.439> ethereum<00:02:02.119> so 00:02:02.310 --> 00:02:02.320 align:start position:0% worlds we've built mud on ethereum so 00:02:02.320 --> 00:02:04.590 align:start position:0% worlds we've built mud on ethereum so that<00:02:02.680> world<00:02:02.960> Builders<00:02:03.439> could<00:02:03.640> have<00:02:04.039> robust 00:02:04.590 --> 00:02:04.600 align:start position:0% that world Builders could have robust 00:02:04.600 --> 00:02:06.950 align:start position:0% that world Builders could have robust Primitives<00:02:05.039> to<00:02:05.200> implement<00:02:05.560> their<00:02:05.719> vision<00:02:06.719> and 00:02:06.950 --> 00:02:06.960 align:start position:0% Primitives to implement their vision and 00:02:06.960 --> 00:02:09.949 align:start position:0% Primitives to implement their vision and build<00:02:07.280> fully<00:02:07.640> onchain<00:02:08.200> gaming<00:02:08.800> loops<00:02:09.800> and 00:02:09.949 --> 00:02:09.959 align:start position:0% build fully onchain gaming loops and 00:02:09.959 --> 00:02:12.430 align:start position:0% build fully onchain gaming loops and then<00:02:10.280> onchain<00:02:10.679> games<00:02:10.920> are<00:02:11.599> well<00:02:12.160> too 00:02:12.430 --> 00:02:12.440 align:start position:0% then onchain games are well too 00:02:12.440 --> 00:02:14.390 align:start position:0% then onchain games are well too expensive<00:02:12.920> to<00:02:13.080> run<00:02:13.239> on<00:02:13.400> ethereum<00:02:13.800> Main<00:02:14.040> net<00:02:14.280> so 00:02:14.390 --> 00:02:14.400 align:start position:0% expensive to run on ethereum Main net so 00:02:14.400 --> 00:02:17.110 align:start position:0% expensive to run on ethereum Main net so we<00:02:14.480> needed<00:02:14.760> a<00:02:14.959> cheap<00:02:15.280> chain<00:02:15.640> with<00:02:15.959> Big<00:02:16.400> Blocks 00:02:17.110 --> 00:02:17.120 align:start position:0% we needed a cheap chain with Big Blocks 00:02:17.120 --> 00:02:21.070 align:start position:0% we needed a cheap chain with Big Blocks and<00:02:17.560> uh<00:02:17.760> infinitely<00:02:18.280> scalable<00:02:18.920> da<00:02:19.920> um<00:02:20.120> so<00:02:20.319> we 00:02:21.070 --> 00:02:21.080 align:start position:0% and uh infinitely scalable da um so we 00:02:21.080 --> 00:02:23.670 align:start position:0% and uh infinitely scalable da um so we basically<00:02:22.080> um<00:02:22.480> added<00:02:22.840> that<00:02:23.000> feature<00:02:23.400> to<00:02:23.560> the 00:02:23.670 --> 00:02:23.680 align:start position:0% basically um added that feature to the 00:02:23.680 --> 00:02:26.070 align:start position:0% basically um added that feature to the op<00:02:24.040> stack<00:02:24.680> and<00:02:24.840> deployed<00:02:25.280> it<00:02:25.440> as<00:02:25.560> a<00:02:25.680> chain 00:02:26.070 --> 00:02:26.080 align:start position:0% op stack and deployed it as a chain 00:02:26.080 --> 00:02:28.830 align:start position:0% op stack and deployed it as a chain called<00:02:26.760> Redstone<00:02:27.760> and<00:02:28.080> on<00:02:28.239> top<00:02:28.400> of<00:02:28.480> redstone 00:02:28.830 --> 00:02:28.840 align:start position:0% called Redstone and on top of redstone 00:02:28.840 --> 00:02:31.229 align:start position:0% called Redstone and on top of redstone we're<00:02:29.000> also<00:02:29.200> running<00:02:30.040> uh<00:02:30.280> free<00:02:30.599> services<00:02:31.040> for 00:02:31.229 --> 00:02:31.239 align:start position:0% we're also running uh free services for 00:02:31.239 --> 00:02:35.350 align:start position:0% we're also running uh free services for mud<00:02:31.519> apps<00:02:31.840> like<00:02:32.040> public<00:02:32.319> rpcs<00:02:32.920> and 00:02:35.350 --> 00:02:35.360 align:start position:0% 00:02:35.360 --> 00:02:37.430 align:start position:0% indexers<00:02:36.360> um<00:02:36.519> and<00:02:36.640> actually<00:02:36.959> to<00:02:37.120> give<00:02:37.239> you<00:02:37.360> a 00:02:37.430 --> 00:02:37.440 align:start position:0% indexers um and actually to give you a 00:02:37.440 --> 00:02:40.270 align:start position:0% indexers um and actually to give you a little<00:02:37.640> context<00:02:38.160> this<00:02:38.280> is<00:02:38.360> a<00:02:38.800> screenshot<00:02:39.800> of 00:02:40.270 --> 00:02:40.280 align:start position:0% little context this is a screenshot of 00:02:40.280 --> 00:02:43.270 align:start position:0% little context this is a screenshot of cwi's<00:02:41.200> public<00:02:41.480> rollup<00:02:41.920> dashboard<00:02:42.920> um<00:02:43.080> and<00:02:43.200> if 00:02:43.270 --> 00:02:43.280 align:start position:0% cwi's public rollup dashboard um and if 00:02:43.280 --> 00:02:46.550 align:start position:0% cwi's public rollup dashboard um and if you<00:02:43.400> look<00:02:43.519> at<00:02:43.640> the<00:02:43.840> top<00:02:44.040> six<00:02:44.560> l2s<00:02:45.560> um<00:02:46.280> you<00:02:46.360> can 00:02:46.550 --> 00:02:46.560 align:start position:0% you look at the top six l2s um you can 00:02:46.560 --> 00:02:51.390 align:start position:0% you look at the top six l2s um you can see<00:02:47.319> except<00:02:48.040> from<00:02:48.360> Bas<00:02:49.000> all<00:02:49.200> of<00:02:49.440> these<00:02:49.760> l2s<00:02:50.760> are 00:02:51.390 --> 00:02:51.400 align:start position:0% see except from Bas all of these l2s are 00:02:51.400 --> 00:02:54.149 align:start position:0% see except from Bas all of these l2s are mostly<00:02:51.760> focused<00:02:52.200> on<00:02:52.400> onchain<00:02:52.959> games<00:02:53.800> uh<00:02:54.000> so 00:02:54.149 --> 00:02:54.159 align:start position:0% mostly focused on onchain games uh so 00:02:54.159 --> 00:02:56.149 align:start position:0% mostly focused on onchain games uh so these<00:02:54.280> are<00:02:54.480> like<00:02:54.800> all<00:02:55.040> the<00:02:55.200> meag<00:02:55.560> gas<00:02:55.920> per 00:02:56.149 --> 00:02:56.159 align:start position:0% these are like all the meag gas per 00:02:56.159 --> 00:02:58.030 align:start position:0% these are like all the meag gas per second<00:02:56.519> that<00:02:56.640> is<00:02:56.840> here<00:02:57.360> uh<00:02:57.480> so<00:02:57.760> all<00:02:57.920> these 00:02:58.030 --> 00:02:58.040 align:start position:0% second that is here uh so all these 00:02:58.040 --> 00:02:59.949 align:start position:0% second that is here uh so all these rollups<00:02:58.440> are<00:02:58.640> ranked<00:02:59.000> by<00:02:59.159> meag<00:02:59.440> gas<00:02:59.599> per 00:02:59.949 --> 00:02:59.959 align:start position:0% rollups are ranked by meag gas per 00:02:59.959 --> 00:03:02.110 align:start position:0% rollups are ranked by meag gas per second<00:03:00.560> and<00:03:00.680> you<00:03:00.760> can<00:03:00.920> see<00:03:01.319> all<00:03:01.480> of<00:03:01.640> them<00:03:01.920> that 00:03:02.110 --> 00:03:02.120 align:start position:0% second and you can see all of them that 00:03:02.120 --> 00:03:04.509 align:start position:0% second and you can see all of them that have<00:03:02.440> extremely<00:03:02.879> high<00:03:03.040> meag<00:03:03.560> per<00:03:03.720> second<00:03:04.280> are 00:03:04.509 --> 00:03:04.519 align:start position:0% have extremely high meag per second are 00:03:04.519 --> 00:03:07.869 align:start position:0% have extremely high meag per second are basically<00:03:05.360> um<00:03:06.239> have<00:03:06.440> onchain<00:03:06.959> games<00:03:07.480> deployed 00:03:07.869 --> 00:03:07.879 align:start position:0% basically um have onchain games deployed 00:03:07.879 --> 00:03:10.670 align:start position:0% basically um have onchain games deployed on<00:03:08.040> it<00:03:08.920> um<00:03:09.159> and<00:03:09.319> actually<00:03:10.280> it's<00:03:10.440> kind<00:03:10.560> of 00:03:10.670 --> 00:03:10.680 align:start position:0% on it um and actually it's kind of 00:03:10.680 --> 00:03:13.270 align:start position:0% on it um and actually it's kind of interesting<00:03:11.040> too<00:03:11.280> is<00:03:12.159> redstone<00:03:12.720> doesn't<00:03:13.040> have 00:03:13.270 --> 00:03:13.280 align:start position:0% interesting too is redstone doesn't have 00:03:13.280 --> 00:03:15.430 align:start position:0% interesting too is redstone doesn't have that<00:03:13.440> much<00:03:13.840> transaction<00:03:14.360> per<00:03:14.560> second<00:03:15.040> but 00:03:15.430 --> 00:03:15.440 align:start position:0% that much transaction per second but 00:03:15.440 --> 00:03:18.430 align:start position:0% that much transaction per second but it's<00:03:15.799> Mega<00:03:16.120> gas<00:03:16.400> per<00:03:16.640> second<00:03:17.120> is<00:03:17.400> very<00:03:17.760> high 00:03:18.430 --> 00:03:18.440 align:start position:0% it's Mega gas per second is very high 00:03:18.440 --> 00:03:20.470 align:start position:0% it's Mega gas per second is very high that<00:03:18.560> means<00:03:18.920> that<00:03:19.239> mud<00:03:19.599> transactions<00:03:20.319> are 00:03:20.470 --> 00:03:20.480 align:start position:0% that means that mud transactions are 00:03:20.480 --> 00:03:22.229 align:start position:0% that means that mud transactions are actually<00:03:20.680> storing<00:03:21.080> a<00:03:21.200> lot<00:03:21.360> of<00:03:21.519> data<00:03:21.760> on<00:03:21.920> chains 00:03:22.229 --> 00:03:22.239 align:start position:0% actually storing a lot of data on chains 00:03:22.239 --> 00:03:24.509 align:start position:0% actually storing a lot of data on chains so<00:03:22.400> they're<00:03:22.640> actually<00:03:23.239> quite<00:03:23.519> big<00:03:24.120> so<00:03:24.319> that's 00:03:24.509 --> 00:03:24.519 align:start position:0% so they're actually quite big so that's 00:03:24.519 --> 00:03:27.710 align:start position:0% so they're actually quite big so that's why<00:03:24.760> we<00:03:24.879> needed<00:03:25.560> uh<00:03:25.920> Redstone<00:03:26.920> so<00:03:27.159> to<00:03:27.360> have<00:03:27.599> a 00:03:27.710 --> 00:03:27.720 align:start position:0% why we needed uh Redstone so to have a 00:03:27.720 --> 00:03:29.470 align:start position:0% why we needed uh Redstone so to have a chain<00:03:28.040> with<00:03:28.239> very<00:03:28.439> big<00:03:28.640> blocks<00:03:28.959> and<00:03:29.080> a<00:03:29.159> lot<00:03:29.280> of 00:03:29.470 --> 00:03:29.480 align:start position:0% chain with very big blocks and a lot of 00:03:29.480 --> 00:03:32.789 align:start position:0% chain with very big blocks and a lot of gas<00:03:30.000> and<00:03:30.159> so<00:03:30.360> that<00:03:31.080> um<00:03:31.560> mud<00:03:32.040> mud<00:03:32.319> apps<00:03:32.599> would 00:03:32.789 --> 00:03:32.799 align:start position:0% gas and so that um mud mud apps would 00:03:32.799 --> 00:03:33.830 align:start position:0% gas and so that um mud mud apps would stay 00:03:33.830 --> 00:03:33.840 align:start position:0% stay 00:03:33.840 --> 00:03:37.390 align:start position:0% stay cheap<00:03:34.840> so<00:03:35.120> some<00:03:35.799> applications<00:03:36.799> um<00:03:37.239> that 00:03:37.390 --> 00:03:37.400 align:start position:0% cheap so some applications um that 00:03:37.400 --> 00:03:40.070 align:start position:0% cheap so some applications um that launched<00:03:38.159> on<00:03:38.640> or<00:03:39.000> are<00:03:39.159> about<00:03:39.360> to<00:03:39.480> launch<00:03:39.720> on 00:03:40.070 --> 00:03:40.080 align:start position:0% launched on or are about to launch on 00:03:40.080 --> 00:03:42.710 align:start position:0% launched on or are about to launch on Redstone<00:03:41.080> um<00:03:41.519> if<00:03:41.599> you<00:03:41.760> didn't<00:03:41.959> haven't<00:03:42.239> caught 00:03:42.710 --> 00:03:42.720 align:start position:0% Redstone um if you didn't haven't caught 00:03:42.720 --> 00:03:45.789 align:start position:0% Redstone um if you didn't haven't caught the<00:03:43.000> eve<00:03:43.760> uh<00:03:43.879> talk<00:03:44.200> earlier<00:03:45.159> by<00:03:45.280> Hillmar<00:03:45.680> and 00:03:45.789 --> 00:03:45.799 align:start position:0% the eve uh talk earlier by Hillmar and 00:03:45.799 --> 00:03:48.350 align:start position:0% the eve uh talk earlier by Hillmar and Justin<00:03:46.760> but<00:03:47.120> I'll<00:03:47.280> talk<00:03:47.439> a<00:03:47.560> little<00:03:47.720> bit<00:03:47.879> is<00:03:48.120> e 00:03:48.350 --> 00:03:48.360 align:start position:0% Justin but I'll talk a little bit is e 00:03:48.360 --> 00:03:50.190 align:start position:0% Justin but I'll talk a little bit is e Frontier<00:03:48.840> is<00:03:48.920> a<00:03:49.040> part<00:03:49.200> of<00:03:49.400> the<00:03:49.640> E<00:03:49.879> online 00:03:50.190 --> 00:03:50.200 align:start position:0% Frontier is a part of the E online 00:03:50.200 --> 00:03:52.429 align:start position:0% Frontier is a part of the E online universe<00:03:50.799> so<00:03:51.000> they<00:03:51.200> designed<00:03:51.560> an<00:03:51.840> incredibly 00:03:52.429 --> 00:03:52.439 align:start position:0% universe so they designed an incredibly 00:03:52.439 --> 00:03:54.390 align:start position:0% universe so they designed an incredibly sophisticated<00:03:53.040> World<00:03:53.360> physics<00:03:53.760> and<00:03:54.159> are 00:03:54.390 --> 00:03:54.400 align:start position:0% sophisticated World physics and are 00:03:54.400 --> 00:03:55.949 align:start position:0% sophisticated World physics and are progressively<00:03:54.920> bringing<00:03:55.319> components<00:03:55.760> on 00:03:55.949 --> 00:03:55.959 align:start position:0% progressively bringing components on 00:03:55.959 --> 00:03:57.910 align:start position:0% progressively bringing components on chain<00:03:56.640> over<00:03:56.879> the<00:03:57.040> next<00:03:57.239> few<00:03:57.400> years<00:03:57.640> you<00:03:57.760> know 00:03:57.910 --> 00:03:57.920 align:start position:0% chain over the next few years you know 00:03:57.920 --> 00:03:59.990 align:start position:0% chain over the next few years you know they're<00:03:58.120> here<00:03:58.239> for<00:03:58.400> the<00:03:58.560> long<00:03:58.760> term<00:03:59.200> so<00:03:59.400> build 00:03:59.990 --> 00:04:00.000 align:start position:0% they're here for the long term so build 00:04:00.000 --> 00:04:01.830 align:start position:0% they're here for the long term so build can<00:04:00.280> basically<00:04:00.640> Implement<00:04:01.040> business<00:04:01.439> logic 00:04:01.830 --> 00:04:01.840 align:start position:0% can basically Implement business logic 00:04:01.840 --> 00:04:05.030 align:start position:0% can basically Implement business logic permissionless<00:04:02.439> Le<00:04:02.560> on<00:04:02.720> top<00:04:02.879> of<00:04:03.000> it<00:04:03.680> um<00:04:04.560> so<00:04:04.920> if 00:04:05.030 --> 00:04:05.040 align:start position:0% permissionless Le on top of it um so if 00:04:05.040 --> 00:04:06.830 align:start position:0% permissionless Le on top of it um so if you<00:04:05.159> missed<00:04:05.439> the<00:04:05.560> talk<00:04:05.760> earlier<00:04:06.439> recommend 00:04:06.830 --> 00:04:06.840 align:start position:0% you missed the talk earlier recommend 00:04:06.840 --> 00:04:09.509 align:start position:0% you missed the talk earlier recommend you<00:04:07.159> go<00:04:07.280> back<00:04:07.400> and<00:04:07.519> check<00:04:07.680> it<00:04:07.840> out<00:04:08.720> um<00:04:09.000> and<00:04:09.159> then 00:04:09.509 --> 00:04:09.519 align:start position:0% you go back and check it out um and then 00:04:09.519 --> 00:04:12.069 align:start position:0% you go back and check it out um and then biomes<00:04:10.480> is<00:04:10.640> bringing<00:04:11.040> Minecraft<00:04:11.560> physics<00:04:11.879> on 00:04:12.069 --> 00:04:12.079 align:start position:0% biomes is bringing Minecraft physics on 00:04:12.079 --> 00:04:13.910 align:start position:0% biomes is bringing Minecraft physics on chain<00:04:12.400> with<00:04:12.560> the<00:04:13.000> with<00:04:13.159> new<00:04:13.519> types<00:04:13.760> of 00:04:13.910 --> 00:04:13.920 align:start position:0% chain with the with new types of 00:04:13.920 --> 00:04:16.390 align:start position:0% chain with the with new types of creative<00:04:14.480> gaming<00:04:14.760> Loops<00:04:15.680> um<00:04:15.959> and<00:04:16.079> they<00:04:16.199> have 00:04:16.390 --> 00:04:16.400 align:start position:0% creative gaming Loops um and they have 00:04:16.400 --> 00:04:18.390 align:start position:0% creative gaming Loops um and they have very<00:04:16.639> intensive<00:04:17.199> requirements<00:04:17.880> to<00:04:18.079> enable 00:04:18.390 --> 00:04:18.400 align:start position:0% very intensive requirements to enable 00:04:18.400 --> 00:04:19.629 align:start position:0% very intensive requirements to enable multiplayer<00:04:19.040> they're<00:04:19.199> currently<00:04:19.519> on 00:04:19.629 --> 00:04:19.639 align:start position:0% multiplayer they're currently on 00:04:19.639 --> 00:04:22.230 align:start position:0% multiplayer they're currently on Redstone<00:04:20.040> mayet<00:04:20.680> actually<00:04:21.359> most<00:04:21.560> of<00:04:21.799> the<00:04:22.120> the 00:04:22.230 --> 00:04:22.240 align:start position:0% Redstone mayet actually most of the the 00:04:22.240 --> 00:04:23.990 align:start position:0% Redstone mayet actually most of the the gas<00:04:22.600> that<00:04:22.720> you<00:04:22.800> saw<00:04:23.040> on<00:04:23.160> the<00:04:23.560> dashboard 00:04:23.990 --> 00:04:24.000 align:start position:0% gas that you saw on the dashboard 00:04:24.000 --> 00:04:26.590 align:start position:0% gas that you saw on the dashboard earlier<00:04:24.680> is<00:04:24.880> coming<00:04:25.120> from<00:04:25.320> biome<00:04:25.800> so<00:04:26.360> very 00:04:26.590 --> 00:04:26.600 align:start position:0% earlier is coming from biome so very 00:04:26.600 --> 00:04:30.590 align:start position:0% earlier is coming from biome so very excited<00:04:27.040> about<00:04:27.720> um<00:04:28.160> this<00:04:28.520> world<00:04:29.520> um<00:04:29.919> and<00:04:30.240> while 00:04:30.590 --> 00:04:30.600 align:start position:0% excited about um this world um and while 00:04:30.600 --> 00:04:32.270 align:start position:0% excited about um this world um and while these<00:04:30.800> teams<00:04:31.160> develop<00:04:31.479> the<00:04:31.639> physics<00:04:31.960> and<00:04:32.120> they 00:04:32.270 --> 00:04:32.280 align:start position:0% these teams develop the physics and they 00:04:32.280 --> 00:04:34.390 align:start position:0% these teams develop the physics and they seeed<00:04:32.600> the<00:04:32.720> worlds<00:04:33.199> with<00:04:33.360> the<00:04:33.520> origin<00:04:33.919> stories 00:04:34.390 --> 00:04:34.400 align:start position:0% seeed the worlds with the origin stories 00:04:34.400 --> 00:04:38.310 align:start position:0% seeed the worlds with the origin stories and<00:04:34.560> the<00:04:34.759> gaming<00:04:35.400> Loop<00:04:36.400> um<00:04:36.840> it<00:04:36.960> is<00:04:37.199> when<00:04:37.520> people 00:04:38.310 --> 00:04:38.320 align:start position:0% and the gaming Loop um it is when people 00:04:38.320 --> 00:04:40.390 align:start position:0% and the gaming Loop um it is when people can<00:04:38.560> build<00:04:38.960> on<00:04:39.199> top<00:04:39.440> without<00:04:39.800> permission<00:04:40.199> and 00:04:40.390 --> 00:04:40.400 align:start position:0% can build on top without permission and 00:04:40.400 --> 00:04:42.390 align:start position:0% can build on top without permission and extend<00:04:40.720> the<00:04:40.840> world<00:04:41.080> with<00:04:41.240> new<00:04:41.479> experiences 00:04:42.390 --> 00:04:42.400 align:start position:0% extend the world with new experiences 00:04:42.400 --> 00:04:44.110 align:start position:0% extend the world with new experiences that<00:04:42.680> properties<00:04:43.120> of<00:04:43.400> autonomous<00:04:43.880> world 00:04:44.110 --> 00:04:44.120 align:start position:0% that properties of autonomous world 00:04:44.120 --> 00:04:47.029 align:start position:0% that properties of autonomous world really<00:04:44.440> emerge<00:04:45.440> uh<00:04:45.520> so<00:04:45.759> we<00:04:45.880> like<00:04:46.039> to<00:04:46.199> call<00:04:46.759> more 00:04:47.029 --> 00:04:47.039 align:start position:0% really emerge uh so we like to call more 00:04:47.039 --> 00:04:49.110 align:start position:0% really emerge uh so we like to call more technical<00:04:47.479> users<00:04:47.840> who<00:04:48.039> extend<00:04:48.320> the<00:04:48.440> worlds 00:04:49.110 --> 00:04:49.120 align:start position:0% technical users who extend the worlds 00:04:49.120 --> 00:04:51.230 align:start position:0% technical users who extend the worlds sewage<00:04:49.680> hackers<00:04:50.600> because<00:04:50.840> they<00:04:50.960> get<00:04:51.080> their 00:04:51.230 --> 00:04:51.240 align:start position:0% sewage hackers because they get their 00:04:51.240 --> 00:04:52.710 align:start position:0% sewage hackers because they get their hands<00:04:51.479> dirty<00:04:51.800> and<00:04:51.919> they<00:04:52.039> need<00:04:52.320> access<00:04:52.520> to 00:04:52.710 --> 00:04:52.720 align:start position:0% hands dirty and they need access to 00:04:52.720 --> 00:04:54.749 align:start position:0% hands dirty and they need access to lower<00:04:53.080> level<00:04:53.360> infrastructure<00:04:53.960> Primitives 00:04:54.749 --> 00:04:54.759 align:start position:0% lower level infrastructure Primitives 00:04:54.759 --> 00:04:58.189 align:start position:0% lower level infrastructure Primitives such<00:04:54.960> as<00:04:55.320> indexers<00:04:55.960> RPC<00:04:56.479> apis<00:04:56.960> to<00:04:57.160> power<00:04:58.080> um 00:04:58.189 --> 00:04:58.199 align:start position:0% such as indexers RPC apis to power um 00:04:58.199 --> 00:05:00.310 align:start position:0% such as indexers RPC apis to power um their<00:04:58.400> applications<00:04:59.759> and<00:04:59.960> you<00:05:00.039> know<00:05:00.199> it's 00:05:00.310 --> 00:05:00.320 align:start position:0% their applications and you know it's 00:05:00.320 --> 00:05:03.029 align:start position:0% their applications and you know it's like<00:05:00.680> most<00:05:01.080> inhabitants<00:05:01.680> of<00:05:01.800> a<00:05:02.000> city<00:05:02.800> they 00:05:03.029 --> 00:05:03.039 align:start position:0% like most inhabitants of a city they 00:05:03.039 --> 00:05:04.430 align:start position:0% like most inhabitants of a city they don't<00:05:03.240> need<00:05:03.560> or<00:05:03.680> they<00:05:03.800> don't<00:05:03.960> concern 00:05:04.430 --> 00:05:04.440 align:start position:0% don't need or they don't concern 00:05:04.440 --> 00:05:05.790 align:start position:0% don't need or they don't concern themselves<00:05:04.680> with<00:05:04.840> the<00:05:04.919> sewers<00:05:05.360> but<00:05:05.520> they're 00:05:05.790 --> 00:05:05.800 align:start position:0% themselves with the sewers but they're 00:05:05.800 --> 00:05:07.390 align:start position:0% themselves with the sewers but they're crucial<00:05:06.240> part<00:05:06.440> of<00:05:06.680> these<00:05:06.919> very<00:05:07.120> dense 00:05:07.390 --> 00:05:07.400 align:start position:0% crucial part of these very dense 00:05:07.400 --> 00:05:09.710 align:start position:0% crucial part of these very dense environments<00:05:08.280> if<00:05:08.400> your<00:05:08.520> sewers<00:05:08.919> stop<00:05:09.199> working 00:05:09.710 --> 00:05:09.720 align:start position:0% environments if your sewers stop working 00:05:09.720 --> 00:05:12.550 align:start position:0% environments if your sewers stop working you're<00:05:10.720> you're<00:05:10.960> pretty 00:05:12.550 --> 00:05:12.560 align:start position:0% you're you're pretty 00:05:12.560 --> 00:05:15.390 align:start position:0% you're you're pretty um<00:05:14.080> okay<00:05:14.199> so<00:05:14.400> I'll<00:05:14.520> go<00:05:14.840> about<00:05:15.199> over 00:05:15.390 --> 00:05:15.400 align:start position:0% um okay so I'll go about over 00:05:15.400 --> 00:05:18.550 align:start position:0% um okay so I'll go about over some<00:05:15.800> requirements<00:05:16.800> um<00:05:17.080> we<00:05:17.199> want<00:05:17.360> to<00:05:17.560> enable 00:05:18.550 --> 00:05:18.560 align:start position:0% some requirements um we want to enable 00:05:18.560 --> 00:05:20.710 align:start position:0% some requirements um we want to enable worlds<00:05:19.160> where<00:05:19.440> multi<00:05:19.840> multiple<00:05:20.199> players<00:05:20.520> can 00:05:20.710 --> 00:05:20.720 align:start position:0% worlds where multi multiple players can 00:05:20.720 --> 00:05:23.270 align:start position:0% worlds where multi multiple players can interact<00:05:21.080> with<00:05:21.199> the<00:05:21.319> state<00:05:21.680> at<00:05:21.840> the<00:05:22.000> same<00:05:22.280> time 00:05:23.270 --> 00:05:23.280 align:start position:0% interact with the state at the same time 00:05:23.280 --> 00:05:25.950 align:start position:0% interact with the state at the same time uh<00:05:23.400> we<00:05:23.520> want<00:05:23.880> low<00:05:24.120> friction<00:05:24.479> for<00:05:24.960> inhabitants 00:05:25.950 --> 00:05:25.960 align:start position:0% uh we want low friction for inhabitants 00:05:25.960 --> 00:05:27.670 align:start position:0% uh we want low friction for inhabitants uh<00:05:26.039> so<00:05:26.240> that<00:05:26.720> they<00:05:26.840> can<00:05:27.080> they<00:05:27.160> don't<00:05:27.360> have<00:05:27.479> to 00:05:27.670 --> 00:05:27.680 align:start position:0% uh so that they can they don't have to 00:05:27.680 --> 00:05:30.110 align:start position:0% uh so that they can they don't have to pay<00:05:28.240> uh<00:05:28.360> expensive<00:05:28.800> transaction<00:05:29.240> fees<00:05:30.000> we 00:05:30.110 --> 00:05:30.120 align:start position:0% pay uh expensive transaction fees we 00:05:30.120 --> 00:05:33.029 align:start position:0% pay uh expensive transaction fees we want<00:05:30.280> to<00:05:30.400> stay<00:05:30.680> evm<00:05:31.160> compatible<00:05:31.840> so<00:05:32.120> that<00:05:32.840> uh 00:05:33.029 --> 00:05:33.039 align:start position:0% want to stay evm compatible so that uh 00:05:33.039 --> 00:05:34.749 align:start position:0% want to stay evm compatible so that uh apps<00:05:33.319> can<00:05:33.520> be<00:05:33.680> compatible<00:05:34.080> with<00:05:34.240> other<00:05:34.400> chains 00:05:34.749 --> 00:05:34.759 align:start position:0% apps can be compatible with other chains 00:05:34.759 --> 00:05:36.870 align:start position:0% apps can be compatible with other chains and<00:05:34.919> other<00:05:35.160> tooling<00:05:35.680> that's<00:05:35.880> in<00:05:36.000> the<00:05:36.120> ethereum 00:05:36.870 --> 00:05:36.880 align:start position:0% and other tooling that's in the ethereum 00:05:36.880 --> 00:05:39.029 align:start position:0% and other tooling that's in the ethereum ecosystem<00:05:37.880> uh<00:05:38.000> and<00:05:38.120> lastly<00:05:38.400> we<00:05:38.560> want<00:05:38.759> this<00:05:38.880> to 00:05:39.029 --> 00:05:39.039 align:start position:0% ecosystem uh and lastly we want this to 00:05:39.039 --> 00:05:42.110 align:start position:0% ecosystem uh and lastly we want this to be<00:05:39.639> super<00:05:39.880> easy<00:05:40.120> for<00:05:40.280> mud<00:05:40.520> users<00:05:40.919> to<00:05:41.680> um 00:05:42.110 --> 00:05:42.120 align:start position:0% be super easy for mud users to um 00:05:42.120 --> 00:05:43.350 align:start position:0% be super easy for mud users to um integrate<00:05:42.600> so<00:05:42.759> they<00:05:42.840> shouldn't<00:05:43.120> have<00:05:43.240> to 00:05:43.350 --> 00:05:43.360 align:start position:0% integrate so they shouldn't have to 00:05:43.360 --> 00:05:45.350 align:start position:0% integrate so they shouldn't have to rewrite<00:05:43.680> their<00:05:43.840> apps<00:05:44.080> or<00:05:44.360> add<00:05:44.639> complex<00:05:45.039> client 00:05:45.350 --> 00:05:45.360 align:start position:0% rewrite their apps or add complex client 00:05:45.360 --> 00:05:47.909 align:start position:0% rewrite their apps or add complex client logic<00:05:46.080> if<00:05:46.199> you're<00:05:46.360> using<00:05:46.680> mud<00:05:47.240> all<00:05:47.400> the<00:05:47.560> tools 00:05:47.909 --> 00:05:47.919 align:start position:0% logic if you're using mud all the tools 00:05:47.919 --> 00:05:52.150 align:start position:0% logic if you're using mud all the tools that<00:05:48.039> we<00:05:48.199> built<00:05:48.960> uh<00:05:49.120> work<00:05:49.440> out<00:05:49.600> of<00:05:49.720> the 00:05:52.150 --> 00:05:52.160 align:start position:0% 00:05:52.160 --> 00:05:54.510 align:start position:0% box<00:05:53.160> okay<00:05:53.360> so<00:05:53.560> one<00:05:53.759> of<00:05:53.880> the<00:05:54.000> things<00:05:54.280> that<00:05:54.400> we 00:05:54.510 --> 00:05:54.520 align:start position:0% box okay so one of the things that we 00:05:54.520 --> 00:05:57.670 align:start position:0% box okay so one of the things that we worked<00:05:54.800> on<00:05:55.080> was<00:05:55.639> um<00:05:56.280> enabling<00:05:56.840> mud<00:05:57.240> apps<00:05:57.479> to 00:05:57.670 --> 00:05:57.680 align:start position:0% worked on was um enabling mud apps to 00:05:57.680 --> 00:06:00.790 align:start position:0% worked on was um enabling mud apps to deploy<00:05:58.039> on<00:05:58.199> Main<00:05:58.479> net<00:05:59.000> with<00:05:59.160> a<00:05:59.880> futureproof 00:06:00.790 --> 00:06:00.800 align:start position:0% deploy on Main net with a futureproof 00:06:00.800 --> 00:06:04.110 align:start position:0% deploy on Main net with a futureproof data<00:06:01.120> availability<00:06:01.639> solution<00:06:02.520> so<00:06:03.520> um<00:06:03.960> we 00:06:04.110 --> 00:06:04.120 align:start position:0% data availability solution so um we 00:06:04.120 --> 00:06:06.990 align:start position:0% data availability solution so um we actually<00:06:04.360> worked<00:06:04.680> with<00:06:04.840> optimism<00:06:05.360> to<00:06:06.039> u<00:06:06.919> i 00:06:06.990 --> 00:06:07.000 align:start position:0% actually worked with optimism to u i 00:06:07.000 --> 00:06:09.110 align:start position:0% actually worked with optimism to u i mean<00:06:07.160> we<00:06:07.280> designed<00:06:07.720> and<00:06:07.880> we<00:06:08.039> implemented<00:06:08.960> a 00:06:09.110 --> 00:06:09.120 align:start position:0% mean we designed and we implemented a 00:06:09.120 --> 00:06:12.550 align:start position:0% mean we designed and we implemented a plasma<00:06:09.560> da<00:06:09.960> protocol<00:06:10.960> uh<00:06:11.800> in<00:06:11.919> order<00:06:12.280> not<00:06:12.400> to 00:06:12.550 --> 00:06:12.560 align:start position:0% plasma da protocol uh in order not to 00:06:12.560 --> 00:06:15.029 align:start position:0% plasma da protocol uh in order not to use<00:06:13.039> blobs<00:06:14.039> there's<00:06:14.280> actually<00:06:14.479> a<00:06:14.639> talk<00:06:14.919> right 00:06:15.029 --> 00:06:15.039 align:start position:0% use blobs there's actually a talk right 00:06:15.039 --> 00:06:16.350 align:start position:0% use blobs there's actually a talk right now<00:06:15.199> in<00:06:15.319> the<00:06:15.400> other<00:06:15.680> stage<00:06:15.919> where<00:06:16.080> they're 00:06:16.350 --> 00:06:16.360 align:start position:0% now in the other stage where they're 00:06:16.360 --> 00:06:19.270 align:start position:0% now in the other stage where they're discussing<00:06:17.039> are<00:06:17.280> blobs<00:06:17.639> cool<00:06:18.440> uh<00:06:18.800> we<00:06:18.960> thought 00:06:19.270 --> 00:06:19.280 align:start position:0% discussing are blobs cool uh we thought 00:06:19.280 --> 00:06:21.749 align:start position:0% discussing are blobs cool uh we thought blobs<00:06:19.639> are<00:06:19.840> not<00:06:20.280> that<00:06:20.479> cool<00:06:20.759> so<00:06:21.440> I<00:06:21.520> mean<00:06:21.639> we 00:06:21.749 --> 00:06:21.759 align:start position:0% blobs are not that cool so I mean we 00:06:21.759 --> 00:06:23.029 align:start position:0% blobs are not that cool so I mean we like<00:06:21.960> blobs<00:06:22.280> but<00:06:22.360> we<00:06:22.479> wanted<00:06:22.720> something 00:06:23.029 --> 00:06:23.039 align:start position:0% like blobs but we wanted something 00:06:23.039 --> 00:06:24.710 align:start position:0% like blobs but we wanted something that's<00:06:23.199> more<00:06:23.400> future<00:06:23.800> proof<00:06:24.039> and<00:06:24.280> infinitely 00:06:24.710 --> 00:06:24.720 align:start position:0% that's more future proof and infinitely 00:06:24.720 --> 00:06:27.230 align:start position:0% that's more future proof and infinitely scalable<00:06:25.160> if<00:06:25.240> you<00:06:25.360> had<00:06:25.479> more<00:06:25.759> chains<00:06:26.759> um<00:06:27.120> and 00:06:27.230 --> 00:06:27.240 align:start position:0% scalable if you had more chains um and 00:06:27.240 --> 00:06:30.430 align:start position:0% scalable if you had more chains um and so<00:06:27.400> we<00:06:27.520> worked<00:06:27.800> with<00:06:28.160> optimism<00:06:29.160> uh<00:06:29.720> and<00:06:30.240> to 00:06:30.430 --> 00:06:30.440 align:start position:0% so we worked with optimism uh and to 00:06:30.440 --> 00:06:32.749 align:start position:0% so we worked with optimism uh and to Upstream<00:06:31.080> this<00:06:31.759> in<00:06:31.880> the<00:06:32.000> codebase<00:06:32.520> and<00:06:32.639> this 00:06:32.749 --> 00:06:32.759 align:start position:0% Upstream this in the codebase and this 00:06:32.759 --> 00:06:35.990 align:start position:0% Upstream this in the codebase and this is<00:06:32.880> known<00:06:33.120> in<00:06:33.319> out<00:06:33.599> da<00:06:33.960> mode<00:06:34.960> and<00:06:35.360> um<00:06:35.680> our 00:06:35.990 --> 00:06:36.000 align:start position:0% is known in out da mode and um our 00:06:36.000 --> 00:06:38.469 align:start position:0% is known in out da mode and um our specific<00:06:36.800> da<00:06:37.120> layer<00:06:37.360> uses<00:06:37.639> a<00:06:37.800> plasma<00:06:38.319> like 00:06:38.469 --> 00:06:38.479 align:start position:0% specific da layer uses a plasma like 00:06:38.479 --> 00:06:40.469 align:start position:0% specific da layer uses a plasma like design<00:06:38.880> so<00:06:39.039> that<00:06:39.240> stakeholders<00:06:39.800> can<00:06:40.039> have<00:06:40.319> an 00:06:40.469 --> 00:06:40.479 align:start position:0% design so that stakeholders can have an 00:06:40.479 --> 00:06:42.029 align:start position:0% design so that stakeholders can have an emergency<00:06:40.960> exit<00:06:41.280> hatch<00:06:41.639> where<00:06:41.800> they<00:06:41.919> can 00:06:42.029 --> 00:06:42.039 align:start position:0% emergency exit hatch where they can 00:06:42.039 --> 00:06:43.550 align:start position:0% emergency exit hatch where they can challenge<00:06:42.400> data<00:06:42.720> if<00:06:42.800> they<00:06:42.919> believe<00:06:43.160> the<00:06:43.319> data 00:06:43.550 --> 00:06:43.560 align:start position:0% challenge data if they believe the data 00:06:43.560 --> 00:06:45.589 align:start position:0% challenge data if they believe the data is<00:06:43.680> missing<00:06:44.360> and<00:06:44.520> they<00:06:44.720> you<00:06:44.800> can<00:06:45.160> basically 00:06:45.589 --> 00:06:45.599 align:start position:0% is missing and they you can basically 00:06:45.599 --> 00:06:47.189 align:start position:0% is missing and they you can basically keep<00:06:45.800> the<00:06:45.919> chain<00:06:46.479> running<00:06:46.880> while<00:06:47.039> you 00:06:47.189 --> 00:06:47.199 align:start position:0% keep the chain running while you 00:06:47.199 --> 00:06:49.270 align:start position:0% keep the chain running while you withdraw<00:06:47.560> your<00:06:47.680> funds<00:06:48.599> uh<00:06:48.680> and<00:06:48.800> if<00:06:48.919> you<00:06:49.160> want 00:06:49.270 --> 00:06:49.280 align:start position:0% withdraw your funds uh and if you want 00:06:49.280 --> 00:06:51.189 align:start position:0% withdraw your funds uh and if you want to<00:06:49.560> know<00:06:49.800> more<00:06:50.000> about<00:06:50.199> how<00:06:50.360> this<00:06:50.520> system<00:06:50.800> works 00:06:51.189 --> 00:06:51.199 align:start position:0% to know more about how this system works 00:06:51.199 --> 00:06:55.550 align:start position:0% to know more about how this system works I<00:06:51.440> recommend<00:06:51.800> you<00:06:51.919> check<00:06:52.199> the<00:06:52.880> uh<00:06:53.199> optimism<00:06:54.199> uh 00:06:55.550 --> 00:06:55.560 align:start position:0% I recommend you check the uh optimism uh 00:06:55.560 --> 00:06:58.749 align:start position:0% I recommend you check the uh optimism uh specs<00:06:56.560> actually<00:06:56.759> a<00:06:56.919> fun<00:06:57.199> fact<00:06:57.400> too<00:06:57.680> is<00:06:58.240> once<00:06:58.520> we 00:06:58.749 --> 00:06:58.759 align:start position:0% specs actually a fun fact too is once we 00:06:58.759 --> 00:07:00.589 align:start position:0% specs actually a fun fact too is once we decided<00:06:59.080> to<00:06:59.160> Launch<00:06:59.759> Stone<00:07:00.039> we<00:07:00.120> were<00:07:00.319> doing 00:07:00.589 --> 00:07:00.599 align:start position:0% decided to Launch Stone we were doing 00:07:00.599 --> 00:07:02.510 align:start position:0% decided to Launch Stone we were doing some<00:07:00.960> uh<00:07:01.240> load<00:07:01.599> testing<00:07:01.919> and<00:07:02.039> we<00:07:02.120> ended<00:07:02.360> up 00:07:02.510 --> 00:07:02.520 align:start position:0% some uh load testing and we ended up 00:07:02.520 --> 00:07:05.309 align:start position:0% some uh load testing and we ended up Breaking<00:07:02.840> the<00:07:03.000> Chain<00:07:03.400> on<00:07:03.599> test<00:07:03.919> net<00:07:04.800> um 00:07:05.309 --> 00:07:05.319 align:start position:0% Breaking the Chain on test net um 00:07:05.319 --> 00:07:08.309 align:start position:0% Breaking the Chain on test net um because<00:07:06.319> we<00:07:06.479> had<00:07:06.639> too<00:07:06.840> much<00:07:07.080> data<00:07:07.800> and<00:07:08.120> uh<00:07:08.199> we 00:07:08.309 --> 00:07:08.319 align:start position:0% because we had too much data and uh we 00:07:08.319 --> 00:07:11.150 align:start position:0% because we had too much data and uh we started<00:07:08.639> with<00:07:08.759> a<00:07:09.160> very<00:07:09.879> large<00:07:10.280> block<00:07:10.639> size<00:07:11.000> 100 00:07:11.150 --> 00:07:11.160 align:start position:0% started with a very large block size 100 00:07:11.160 --> 00:07:14.589 align:start position:0% started with a very large block size 100 Mil<00:07:11.360> in<00:07:11.560> gas<00:07:12.240> and<00:07:13.080> uh<00:07:13.280> the<00:07:13.639> op<00:07:14.039> stack<00:07:14.280> limits 00:07:14.589 --> 00:07:14.599 align:start position:0% Mil in gas and uh the op stack limits 00:07:14.599 --> 00:07:16.469 align:start position:0% Mil in gas and uh the op stack limits were<00:07:14.800> not<00:07:15.160> large<00:07:15.400> enough<00:07:15.720> to<00:07:15.840> enable<00:07:16.319> this 00:07:16.469 --> 00:07:16.479 align:start position:0% were not large enough to enable this 00:07:16.479 --> 00:07:18.990 align:start position:0% were not large enough to enable this kind<00:07:16.599> of<00:07:16.960> payload<00:07:17.440> size<00:07:18.360> uh<00:07:18.440> so<00:07:18.599> we<00:07:18.759> actually 00:07:18.990 --> 00:07:19.000 align:start position:0% kind of payload size uh so we actually 00:07:19.000 --> 00:07:20.790 align:start position:0% kind of payload size uh so we actually collaborated<00:07:19.680> to<00:07:19.919> with<00:07:20.039> the<00:07:20.120> opack<00:07:20.599> core 00:07:20.790 --> 00:07:20.800 align:start position:0% collaborated to with the opack core 00:07:20.800 --> 00:07:22.670 align:start position:0% collaborated to with the opack core developers<00:07:21.240> to<00:07:21.400> raise<00:07:21.720> this<00:07:21.919> limit<00:07:22.400> that<00:07:22.520> was 00:07:22.670 --> 00:07:22.680 align:start position:0% developers to raise this limit that was 00:07:22.680 --> 00:07:25.830 align:start position:0% developers to raise this limit that was introduced<00:07:23.160> in<00:07:23.319> the<00:07:23.560> for<00:07:24.039> Network<00:07:24.440> upgrade<00:07:25.440> um 00:07:25.830 --> 00:07:25.840 align:start position:0% introduced in the for Network upgrade um 00:07:25.840 --> 00:07:28.469 align:start position:0% introduced in the for Network upgrade um and<00:07:26.440> it<00:07:26.520> was<00:07:26.759> really<00:07:27.199> easy<00:07:27.479> to<00:07:27.639> ship<00:07:28.039> quickly 00:07:28.469 --> 00:07:28.479 align:start position:0% and it was really easy to ship quickly 00:07:28.479 --> 00:07:30.110 align:start position:0% and it was really easy to ship quickly because<00:07:28.720> we<00:07:28.879> control<00:07:29.280> the<00:07:29.560> full 00:07:30.110 --> 00:07:30.120 align:start position:0% because we control the full 00:07:30.120 --> 00:07:32.230 align:start position:0% because we control the full infrastructure<00:07:31.120> um<00:07:31.479> by<00:07:31.639> running<00:07:31.919> the<00:07:32.000> chain 00:07:32.230 --> 00:07:32.240 align:start position:0% infrastructure um by running the chain 00:07:32.240 --> 00:07:33.469 align:start position:0% infrastructure um by running the chain ourselves<00:07:32.759> instead<00:07:33.000> of<00:07:33.120> adding 00:07:33.469 --> 00:07:33.479 align:start position:0% ourselves instead of adding 00:07:33.479 --> 00:07:35.589 align:start position:0% ourselves instead of adding intermediaries<00:07:34.240> like<00:07:34.560> roll<00:07:34.840> up<00:07:35.000> as<00:07:35.120> a<00:07:35.240> service 00:07:35.589 --> 00:07:35.599 align:start position:0% intermediaries like roll up as a service 00:07:35.599 --> 00:07:37.790 align:start position:0% intermediaries like roll up as a service providers<00:07:36.560> uh<00:07:36.639> so<00:07:36.800> it<00:07:37.120> allows<00:07:37.360> us<00:07:37.520> to<00:07:37.639> make 00:07:37.790 --> 00:07:37.800 align:start position:0% providers uh so it allows us to make 00:07:37.800 --> 00:07:39.790 align:start position:0% providers uh so it allows us to make custom<00:07:38.120> changes<00:07:38.440> to<00:07:38.560> the<00:07:38.720> services<00:07:39.280> and<00:07:39.479> test 00:07:39.790 --> 00:07:39.800 align:start position:0% custom changes to the services and test 00:07:39.800 --> 00:07:41.990 align:start position:0% custom changes to the services and test potential<00:07:40.240> protocol<00:07:40.759> protocol<00:07:41.160> changes 00:07:41.990 --> 00:07:42.000 align:start position:0% potential protocol protocol changes 00:07:42.000 --> 00:07:43.990 align:start position:0% potential protocol protocol changes directly<00:07:43.000> um<00:07:43.080> so<00:07:43.199> we<00:07:43.319> can<00:07:43.440> observe<00:07:43.800> the 00:07:43.990 --> 00:07:44.000 align:start position:0% directly um so we can observe the 00:07:44.000 --> 00:07:46.110 align:start position:0% directly um so we can observe the effects<00:07:44.440> on<00:07:44.680> application<00:07:45.240> directly<00:07:46.000> uh 00:07:46.110 --> 00:07:46.120 align:start position:0% effects on application directly uh 00:07:46.120 --> 00:07:47.909 align:start position:0% effects on application directly uh before<00:07:46.360> they<00:07:46.520> eventually<00:07:47.120> get<00:07:47.280> upstreamed<00:07:47.800> in 00:07:47.909 --> 00:07:47.919 align:start position:0% before they eventually get upstreamed in 00:07:47.919 --> 00:07:49.990 align:start position:0% before they eventually get upstreamed in the<00:07:48.000> op 00:07:49.990 --> 00:07:50.000 align:start position:0% the op 00:07:50.000 --> 00:07:53.589 align:start position:0% the op stack<00:07:51.000> um<00:07:51.319> and<00:07:51.599> when<00:07:51.720> we<00:07:51.919> first<00:07:52.240> running<00:07:52.800> El<00:07:53.479> we 00:07:53.589 --> 00:07:53.599 align:start position:0% stack um and when we first running El we 00:07:53.599 --> 00:07:55.589 align:start position:0% stack um and when we first running El we started<00:07:53.800> running<00:07:54.080> dl2<00:07:54.479> chains<00:07:54.840> so<00:07:55.240> we<00:07:55.400> we<00:07:55.479> had 00:07:55.589 --> 00:07:55.599 align:start position:0% started running dl2 chains so we we had 00:07:55.599 --> 00:07:57.550 align:start position:0% started running dl2 chains so we we had to<00:07:55.960> you<00:07:56.080> know<00:07:56.360> learn<00:07:56.680> how<00:07:56.759> to<00:07:56.919> run<00:07:57.120> the<00:07:57.240> chain 00:07:57.550 --> 00:07:57.560 align:start position:0% to you know learn how to run the chain 00:07:57.560 --> 00:08:00.550 align:start position:0% to you know learn how to run the chain and<00:07:57.800> do<00:07:57.960> all<00:07:58.080> that<00:07:58.280> stuff<00:07:59.000> and<00:07:59.599> um<00:07:59.800> we<00:08:00.240> quickly 00:08:00.550 --> 00:08:00.560 align:start position:0% and do all that stuff and um we quickly 00:08:00.560 --> 00:08:02.790 align:start position:0% and do all that stuff and um we quickly ran<00:08:00.840> into<00:08:01.120> bottlenecks<00:08:01.960> because<00:08:02.639> our 00:08:02.790 --> 00:08:02.800 align:start position:0% ran into bottlenecks because our 00:08:02.800 --> 00:08:04.550 align:start position:0% ran into bottlenecks because our sequence<00:08:03.159> or<00:08:03.319> node<00:08:03.599> was<00:08:03.759> busy<00:08:04.159> building 00:08:04.550 --> 00:08:04.560 align:start position:0% sequence or node was busy building 00:08:04.560 --> 00:08:07.309 align:start position:0% sequence or node was busy building blocks<00:08:05.360> uh<00:08:05.520> and<00:08:06.039> handling<00:08:06.360> RPC<00:08:06.840> Quest<00:08:07.120> so<00:08:07.240> we 00:08:07.309 --> 00:08:07.319 align:start position:0% blocks uh and handling RPC Quest so we 00:08:07.319 --> 00:08:09.670 align:start position:0% blocks uh and handling RPC Quest so we did<00:08:07.840> some<00:08:08.120> basic<00:08:08.440> things<00:08:08.800> like<00:08:09.199> separating 00:08:09.670 --> 00:08:09.680 align:start position:0% did some basic things like separating 00:08:09.680 --> 00:08:13.149 align:start position:0% did some basic things like separating the<00:08:09.800> read<00:08:10.479> and<00:08:10.639> the<00:08:11.000> rides<00:08:12.000> um<00:08:12.680> and 00:08:13.149 --> 00:08:13.159 align:start position:0% the read and the rides um and 00:08:13.159 --> 00:08:14.710 align:start position:0% the read and the rides um and essentially<00:08:13.680> eventually<00:08:14.120> the<00:08:14.319> Redstone 00:08:14.710 --> 00:08:14.720 align:start position:0% essentially eventually the Redstone 00:08:14.720 --> 00:08:16.390 align:start position:0% essentially eventually the Redstone sequencer<00:08:15.199> State<00:08:15.479> private<00:08:15.879> we<00:08:16.000> exposed 00:08:16.390 --> 00:08:16.400 align:start position:0% sequencer State private we exposed 00:08:16.400 --> 00:08:17.589 align:start position:0% sequencer State private we exposed another<00:08:16.639> one<00:08:16.840> that<00:08:16.960> was<00:08:17.080> synced<00:08:17.400> over 00:08:17.589 --> 00:08:17.599 align:start position:0% another one that was synced over 00:08:17.599 --> 00:08:19.909 align:start position:0% another one that was synced over peer-to-peer<00:08:17.960> uh<00:08:18.879> then<00:08:19.080> that<00:08:19.199> node<00:08:19.520> also<00:08:19.720> got 00:08:19.909 --> 00:08:19.919 align:start position:0% peer-to-peer uh then that node also got 00:08:19.919 --> 00:08:21.430 align:start position:0% peer-to-peer uh then that node also got a<00:08:20.000> bit<00:08:20.240> overwhelmed<00:08:20.759> so<00:08:20.840> we<00:08:20.919> added<00:08:21.199> another 00:08:21.430 --> 00:08:21.440 align:start position:0% a bit overwhelmed so we added another 00:08:21.440 --> 00:08:24.909 align:start position:0% a bit overwhelmed so we added another node<00:08:21.800> and<00:08:22.240> split<00:08:22.680> them<00:08:22.919> by<00:08:23.199> regions<00:08:24.199> um<00:08:24.759> now 00:08:24.909 --> 00:08:24.919 align:start position:0% node and split them by regions um now 00:08:24.919 --> 00:08:26.670 align:start position:0% node and split them by regions um now the<00:08:25.080> problem<00:08:25.319> you<00:08:25.759> face<00:08:26.120> and<00:08:26.319> actually<00:08:26.599> you 00:08:26.670 --> 00:08:26.680 align:start position:0% the problem you face and actually you 00:08:26.680 --> 00:08:28.790 align:start position:0% the problem you face and actually you might<00:08:26.840> have<00:08:27.000> heard<00:08:27.319> Ryan<00:08:27.960> talk<00:08:28.199> about<00:08:28.400> it<00:08:28.599> in 00:08:28.790 --> 00:08:28.800 align:start position:0% might have heard Ryan talk about it in 00:08:28.800 --> 00:08:31.270 align:start position:0% might have heard Ryan talk about it in indexing<00:08:29.240> is<00:08:29.840> you<00:08:30.280> can<00:08:30.680> end<00:08:30.879> up<00:08:31.039> with 00:08:31.270 --> 00:08:31.280 align:start position:0% indexing is you can end up with 00:08:31.280 --> 00:08:32.630 align:start position:0% indexing is you can end up with different<00:08:31.560> states<00:08:31.960> if<00:08:32.039> you<00:08:32.159> have<00:08:32.279> a<00:08:32.399> load 00:08:32.630 --> 00:08:32.640 align:start position:0% different states if you have a load 00:08:32.640 --> 00:08:35.149 align:start position:0% different states if you have a load balancer<00:08:33.080> in<00:08:33.200> front<00:08:33.360> of<00:08:33.479> your<00:08:33.599> nodes<00:08:34.599> um<00:08:34.959> and 00:08:35.149 --> 00:08:35.159 align:start position:0% balancer in front of your nodes um and 00:08:35.159 --> 00:08:37.190 align:start position:0% balancer in front of your nodes um and there's<00:08:35.399> actually<00:08:35.800> really<00:08:36.039> cool<00:08:36.279> ways<00:08:36.760> that 00:08:37.190 --> 00:08:37.200 align:start position:0% there's actually really cool ways that 00:08:37.200 --> 00:08:39.269 align:start position:0% there's actually really cool ways that for<00:08:37.320> example<00:08:37.719> optimism<00:08:38.200> implemented<00:08:38.640> a<00:08:38.880> proxy 00:08:39.269 --> 00:08:39.279 align:start position:0% for example optimism implemented a proxy 00:08:39.279 --> 00:08:41.509 align:start position:0% for example optimism implemented a proxy D<00:08:39.959> which<00:08:40.159> helps<00:08:40.560> basically<00:08:40.919> keep<00:08:41.080> a<00:08:41.279> health 00:08:41.509 --> 00:08:41.519 align:start position:0% D which helps basically keep a health 00:08:41.519 --> 00:08:43.029 align:start position:0% D which helps basically keep a health check<00:08:41.760> Loop<00:08:42.000> so<00:08:42.159> you<00:08:42.240> can<00:08:42.399> check<00:08:42.640> that<00:08:42.760> each<00:08:42.919> of 00:08:43.029 --> 00:08:43.039 align:start position:0% check Loop so you can check that each of 00:08:43.039 --> 00:08:44.870 align:start position:0% check Loop so you can check that each of the<00:08:43.159> nodes<00:08:43.440> has<00:08:43.680> consistent<00:08:44.120> State<00:08:44.640> and<00:08:44.760> you 00:08:44.870 --> 00:08:44.880 align:start position:0% the nodes has consistent State and you 00:08:44.880 --> 00:08:47.150 align:start position:0% the nodes has consistent State and you removed<00:08:45.480> uh<00:08:45.720> them<00:08:45.880> from<00:08:46.080> the<00:08:46.200> set<00:08:46.600> if<00:08:46.839> they 00:08:47.150 --> 00:08:47.160 align:start position:0% removed uh them from the set if they 00:08:47.160 --> 00:08:49.430 align:start position:0% removed uh them from the set if they they're<00:08:47.480> inconsistent<00:08:48.480> uh<00:08:48.600> you<00:08:48.720> have<00:08:49.200> other 00:08:49.430 --> 00:08:49.440 align:start position:0% they're inconsistent uh you have other 00:08:49.440 --> 00:08:51.949 align:start position:0% they're inconsistent uh you have other goodies<00:08:49.880> like<00:08:50.120> caching<00:08:50.640> and<00:08:51.200> uh<00:08:51.320> rewriting 00:08:51.949 --> 00:08:51.959 align:start position:0% goodies like caching and uh rewriting 00:08:51.959 --> 00:08:55.389 align:start position:0% goodies like caching and uh rewriting reorgs<00:08:52.959> um<00:08:53.920> and<00:08:54.200> eventually<00:08:54.760> we<00:08:54.880> also<00:08:55.120> wanted 00:08:55.389 --> 00:08:55.399 align:start position:0% reorgs um and eventually we also wanted 00:08:55.399 --> 00:08:57.670 align:start position:0% reorgs um and eventually we also wanted to<00:08:55.560> have<00:08:55.680> better<00:08:56.000> latency<00:08:56.560> inside<00:08:56.920> of<00:08:57.480> um 00:08:57.670 --> 00:08:57.680 align:start position:0% to have better latency inside of um 00:08:57.680 --> 00:08:59.590 align:start position:0% to have better latency inside of um different<00:08:57.959> regions<00:08:58.800> uh<00:08:58.880> so<00:08:59.000> we<00:08:59.120> added<00:08:59.480> you 00:08:59.590 --> 00:08:59.600 align:start position:0% different regions uh so we added you 00:08:59.600 --> 00:09:02.269 align:start position:0% different regions uh so we added you know<00:09:00.560> uh<00:09:00.680> DNS<00:09:01.120> low<00:09:01.360> balancing<00:09:01.800> so<00:09:02.000> you 00:09:02.269 --> 00:09:02.279 align:start position:0% know uh DNS low balancing so you 00:09:02.279 --> 00:09:04.150 align:start position:0% know uh DNS low balancing so you basically<00:09:02.920> you<00:09:03.040> can<00:09:03.160> see<00:09:03.399> here<00:09:03.680> our<00:09:03.800> user<00:09:04.040> is 00:09:04.150 --> 00:09:04.160 align:start position:0% basically you can see here our user is 00:09:04.160 --> 00:09:05.389 align:start position:0% basically you can see here our user is in<00:09:04.240> the<00:09:04.360> south<00:09:04.519> of<00:09:04.640> France<00:09:05.040> he<00:09:05.160> gets 00:09:05.389 --> 00:09:05.399 align:start position:0% in the south of France he gets 00:09:05.399 --> 00:09:07.750 align:start position:0% in the south of France he gets redirected<00:09:05.920> to<00:09:06.040> the<00:09:06.200> closest<00:09:06.600> region<00:09:07.600> uh 00:09:07.750 --> 00:09:07.760 align:start position:0% redirected to the closest region uh 00:09:07.760 --> 00:09:09.269 align:start position:0% redirected to the closest region uh which<00:09:08.000> then<00:09:08.120> goes<00:09:08.320> to<00:09:08.440> our<00:09:08.640> proxy<00:09:08.959> and<00:09:09.079> low 00:09:09.269 --> 00:09:09.279 align:start position:0% which then goes to our proxy and low 00:09:09.279 --> 00:09:11.630 align:start position:0% which then goes to our proxy and low balancer<00:09:09.800> and<00:09:10.000> and<00:09:10.120> a<00:09:10.240> bunch<00:09:10.399> of<00:09:10.480> nodes<00:09:11.360> um<00:09:11.480> so 00:09:11.630 --> 00:09:11.640 align:start position:0% balancer and and a bunch of nodes um so 00:09:11.640 --> 00:09:14.829 align:start position:0% balancer and and a bunch of nodes um so this<00:09:11.800> is<00:09:12.120> things<00:09:12.440> that<00:09:12.800> that<00:09:13.079> we<00:09:13.480> um 00:09:14.829 --> 00:09:14.839 align:start position:0% this is things that that we um 00:09:14.839 --> 00:09:18.949 align:start position:0% this is things that that we um implemented<00:09:15.839> another<00:09:16.360> aspect<00:09:17.320> and<00:09:18.320> um<00:09:18.680> you<00:09:18.880> if 00:09:18.949 --> 00:09:18.959 align:start position:0% implemented another aspect and um you if 00:09:18.959 --> 00:09:20.710 align:start position:0% implemented another aspect and um you if you<00:09:19.079> heard<00:09:19.480> Ryan's<00:09:19.880> talk<00:09:20.079> earlier<00:09:20.560> you 00:09:20.710 --> 00:09:20.720 align:start position:0% you heard Ryan's talk earlier you 00:09:20.720 --> 00:09:22.150 align:start position:0% you heard Ryan's talk earlier you already<00:09:21.160> probably<00:09:21.399> know<00:09:21.600> how<00:09:21.720> to<00:09:21.839> implement 00:09:22.150 --> 00:09:22.160 align:start position:0% already probably know how to implement 00:09:22.160 --> 00:09:25.230 align:start position:0% already probably know how to implement your<00:09:22.279> own<00:09:22.519> indexer<00:09:23.519> um<00:09:23.839> but<00:09:24.399> actually<00:09:25.040> a 00:09:25.230 --> 00:09:25.240 align:start position:0% your own indexer um but actually a 00:09:25.240 --> 00:09:27.389 align:start position:0% your own indexer um but actually a common<00:09:25.519> bottleneck<00:09:26.079> is<00:09:26.360> by<00:09:26.519> mud<00:09:27.000> experiened 00:09:27.389 --> 00:09:27.399 align:start position:0% common bottleneck is by mud experiened 00:09:27.399 --> 00:09:29.030 align:start position:0% common bottleneck is by mud experiened by<00:09:27.560> mud<00:09:27.880> application<00:09:28.399> is<00:09:28.519> when<00:09:28.680> the<00:09:28.800> state 00:09:29.030 --> 00:09:29.040 align:start position:0% by mud application is when the state 00:09:29.040 --> 00:09:31.590 align:start position:0% by mud application is when the state grows<00:09:29.440> and<00:09:29.600> users<00:09:30.040> grow<00:09:30.720> the<00:09:30.880> initial<00:09:31.200> load<00:09:31.480> of 00:09:31.590 --> 00:09:31.600 align:start position:0% grows and users grow the initial load of 00:09:31.600 --> 00:09:34.590 align:start position:0% grows and users grow the initial load of the<00:09:31.760> game<00:09:32.279> can<00:09:32.480> be<00:09:33.120> um<00:09:33.440> very<00:09:33.680> slow<00:09:34.200> especially 00:09:34.590 --> 00:09:34.600 align:start position:0% the game can be um very slow especially 00:09:34.600 --> 00:09:36.110 align:start position:0% the game can be um very slow especially when<00:09:34.720> it's<00:09:34.920> hydrated<00:09:35.360> directly<00:09:35.680> from<00:09:35.800> a<00:09:35.920> node 00:09:36.110 --> 00:09:36.120 align:start position:0% when it's hydrated directly from a node 00:09:36.120 --> 00:09:39.269 align:start position:0% when it's hydrated directly from a node RPC<00:09:36.920> so<00:09:37.120> this<00:09:37.240> is<00:09:37.399> sold<00:09:37.760> by<00:09:37.880> loading<00:09:38.839> uh<00:09:39.120> the 00:09:39.269 --> 00:09:39.279 align:start position:0% RPC so this is sold by loading uh the 00:09:39.279 --> 00:09:41.550 align:start position:0% RPC so this is sold by loading uh the initial<00:09:39.600> state<00:09:39.839> from<00:09:39.959> an<00:09:40.079> indexer<00:09:40.560> database 00:09:41.550 --> 00:09:41.560 align:start position:0% initial state from an indexer database 00:09:41.560 --> 00:09:43.350 align:start position:0% initial state from an indexer database we<00:09:41.800> first<00:09:42.160> released<00:09:42.519> an<00:09:42.640> open<00:09:42.880> source<00:09:43.120> version 00:09:43.350 --> 00:09:43.360 align:start position:0% we first released an open source version 00:09:43.360 --> 00:09:46.389 align:start position:0% we first released an open source version of<00:09:43.480> the<00:09:43.560> indexer<00:09:44.120> so<00:09:44.680> index<00:09:45.240> uh<00:09:45.760> apps<00:09:46.079> could 00:09:46.389 --> 00:09:46.399 align:start position:0% of the indexer so index uh apps could 00:09:46.399 --> 00:09:48.990 align:start position:0% of the indexer so index uh apps could index<00:09:46.760> their<00:09:46.880> own<00:09:47.440> world<00:09:48.320> and<00:09:48.440> we<00:09:48.560> also<00:09:48.760> wanted 00:09:48.990 --> 00:09:49.000 align:start position:0% index their own world and we also wanted 00:09:49.000 --> 00:09:50.990 align:start position:0% index their own world and we also wanted to<00:09:49.160> offer<00:09:49.360> free<00:09:49.600> indexing<00:09:50.120> for<00:09:50.360> all<00:09:50.560> the<00:09:50.680> mud 00:09:50.990 --> 00:09:51.000 align:start position:0% to offer free indexing for all the mud 00:09:51.000 --> 00:09:53.470 align:start position:0% to offer free indexing for all the mud applications<00:09:52.000> um<00:09:52.480> and<00:09:52.600> our<00:09:52.760> first<00:09:52.959> indexer 00:09:53.470 --> 00:09:53.480 align:start position:0% applications um and our first indexer 00:09:53.480 --> 00:09:55.790 align:start position:0% applications um and our first indexer implementation<00:09:54.079> was<00:09:54.519> kind<00:09:54.640> of<00:09:55.399> not<00:09:55.600> as 00:09:55.790 --> 00:09:55.800 align:start position:0% implementation was kind of not as 00:09:55.800 --> 00:09:57.710 align:start position:0% implementation was kind of not as performance<00:09:56.480> it<00:09:56.600> had<00:09:56.800> limitations<00:09:57.399> so<00:09:57.560> we 00:09:57.710 --> 00:09:57.720 align:start position:0% performance it had limitations so we 00:09:57.720 --> 00:09:59.710 align:start position:0% performance it had limitations so we collaborated<00:09:58.240> with<00:09:58.399> Ryan<00:09:58.760> actually<00:09:59.079> in<00:09:59.440> and 00:09:59.710 --> 00:09:59.720 align:start position:0% collaborated with Ryan actually in and 00:09:59.720 --> 00:10:01.949 align:start position:0% collaborated with Ryan actually in and Ryan<00:10:00.160> built<00:10:00.560> ended<00:10:00.839> up<00:10:01.279> building<00:10:01.640> most<00:10:01.760> of<00:10:01.880> the 00:10:01.949 --> 00:10:01.959 align:start position:0% Ryan built ended up building most of the 00:10:01.959 --> 00:10:03.550 align:start position:0% Ryan built ended up building most of the indexer<00:10:02.480> that<00:10:02.680> that<00:10:02.800> we're<00:10:03.000> actually<00:10:03.200> running 00:10:03.550 --> 00:10:03.560 align:start position:0% indexer that that we're actually running 00:10:03.560 --> 00:10:05.870 align:start position:0% indexer that that we're actually running now<00:10:04.360> um<00:10:04.560> and<00:10:04.640> it<00:10:04.760> can<00:10:04.880> scale<00:10:05.200> for<00:10:05.560> a<00:10:05.720> whole 00:10:05.870 --> 00:10:05.880 align:start position:0% now um and it can scale for a whole 00:10:05.880 --> 00:10:09.710 align:start position:0% now um and it can scale for a whole bunch<00:10:06.040> of<00:10:06.160> Worlds<00:10:06.680> so<00:10:07.640> um 00:10:09.710 --> 00:10:09.720 align:start position:0% bunch of Worlds so um 00:10:09.720 --> 00:10:13.110 align:start position:0% bunch of Worlds so um yeah<00:10:10.720> okay<00:10:11.200> another<00:10:11.600> aspect<00:10:12.440> that<00:10:12.560> I<00:10:12.720> learned 00:10:13.110 --> 00:10:13.120 align:start position:0% yeah okay another aspect that I learned 00:10:13.120 --> 00:10:16.190 align:start position:0% yeah okay another aspect that I learned about<00:10:13.360> recently<00:10:13.839> myself<00:10:14.160> is<00:10:14.760> how<00:10:15.560> ethereum 00:10:16.190 --> 00:10:16.200 align:start position:0% about recently myself is how ethereum 00:10:16.200 --> 00:10:18.389 align:start position:0% about recently myself is how ethereum providers<00:10:17.200> um<00:10:17.360> like<00:10:17.480> browser<00:10:17.920> clients<00:10:18.279> and 00:10:18.389 --> 00:10:18.399 align:start position:0% providers um like browser clients and 00:10:18.399 --> 00:10:19.670 align:start position:0% providers um like browser clients and things<00:10:18.560> like<00:10:18.760> that<00:10:19.000> they<00:10:19.120> make<00:10:19.279> a<00:10:19.399> lot<00:10:19.519> of 00:10:19.670 --> 00:10:19.680 align:start position:0% things like that they make a lot of 00:10:19.680 --> 00:10:21.829 align:start position:0% things like that they make a lot of requests<00:10:20.040> by<00:10:20.200> default<00:10:20.600> before<00:10:20.839> sending<00:10:21.600> a 00:10:21.829 --> 00:10:21.839 align:start position:0% requests by default before sending a 00:10:21.839 --> 00:10:23.710 align:start position:0% requests by default before sending a transaction<00:10:22.839> and<00:10:22.959> if<00:10:23.079> you're<00:10:23.200> far<00:10:23.480> from<00:10:23.600> the 00:10:23.710 --> 00:10:23.720 align:start position:0% transaction and if you're far from the 00:10:23.720 --> 00:10:26.069 align:start position:0% transaction and if you're far from the RPC<00:10:24.160> server<00:10:24.399> the<00:10:24.519> latency<00:10:24.920> can<00:10:25.120> add<00:10:25.279> up<00:10:25.920> um 00:10:26.069 --> 00:10:26.079 align:start position:0% RPC server the latency can add up um 00:10:26.079 --> 00:10:28.670 align:start position:0% RPC server the latency can add up um some<00:10:26.240> of<00:10:26.399> these<00:10:26.600> requests<00:10:27.120> like<00:10:27.519> estimate<00:10:28.040> gas 00:10:28.670 --> 00:10:28.680 align:start position:0% some of these requests like estimate gas 00:10:28.680 --> 00:10:30.030 align:start position:0% some of these requests like estimate gas they're<00:10:28.839> also<00:10:29.040> quite<00:10:29.360> slow<00:10:29.600> because<00:10:29.720> they<00:10:29.800> run 00:10:30.030 --> 00:10:30.040 align:start position:0% they're also quite slow because they run 00:10:30.040 --> 00:10:31.949 align:start position:0% they're also quite slow because they run the<00:10:30.360> the<00:10:30.480> evm<00:10:30.839> quite<00:10:31.000> a<00:10:31.120> bunch<00:10:31.320> of<00:10:31.440> times<00:10:31.760> to 00:10:31.949 --> 00:10:31.959 align:start position:0% the the evm quite a bunch of times to 00:10:31.959 --> 00:10:34.910 align:start position:0% the the evm quite a bunch of times to estimate<00:10:32.279> the<00:10:32.480> gas<00:10:33.480> um<00:10:33.640> so<00:10:33.839> we<00:10:34.079> made<00:10:34.320> some 00:10:34.910 --> 00:10:34.920 align:start position:0% estimate the gas um so we made some 00:10:34.920 --> 00:10:37.269 align:start position:0% estimate the gas um so we made some optimizations<00:10:35.920> you<00:10:36.000> can<00:10:36.160> see<00:10:36.440> here<00:10:36.600> this<00:10:36.760> is 00:10:37.269 --> 00:10:37.279 align:start position:0% optimizations you can see here this is 00:10:37.279 --> 00:10:39.790 align:start position:0% optimizations you can see here this is all<00:10:37.600> the<00:10:38.160> by<00:10:38.320> default<00:10:38.720> you<00:10:38.839> can<00:10:39.000> be<00:10:39.240> making<00:10:39.639> as 00:10:39.790 --> 00:10:39.800 align:start position:0% all the by default you can be making as 00:10:39.800 --> 00:10:42.470 align:start position:0% all the by default you can be making as many<00:10:40.040> of<00:10:40.200> these<00:10:40.959> uh<00:10:41.279> requests<00:10:42.000> and<00:10:42.120> so<00:10:42.360> that 00:10:42.470 --> 00:10:42.480 align:start position:0% many of these uh requests and so that 00:10:42.480 --> 00:10:45.430 align:start position:0% many of these uh requests and so that that<00:10:42.560> ends<00:10:42.760> up<00:10:43.320> pretty<00:10:43.639> pretty<00:10:43.880> slow<00:10:44.880> um<00:10:45.120> so<00:10:45.320> we 00:10:45.430 --> 00:10:45.440 align:start position:0% that ends up pretty pretty slow um so we 00:10:45.440 --> 00:10:47.509 align:start position:0% that ends up pretty pretty slow um so we met<00:10:45.680> some<00:10:46.279> uh<00:10:46.399> optimizations<00:10:47.040> on<00:10:47.200> the<00:10:47.279> mud 00:10:47.509 --> 00:10:47.519 align:start position:0% met some uh optimizations on the mud 00:10:47.519 --> 00:10:49.389 align:start position:0% met some uh optimizations on the mud browser<00:10:47.880> clients<00:10:48.440> so<00:10:48.639> we<00:10:48.760> added<00:10:49.000> a<00:10:49.120> non 00:10:49.389 --> 00:10:49.399 align:start position:0% browser clients so we added a non 00:10:49.399 --> 00:10:51.389 align:start position:0% browser clients so we added a non manager<00:10:50.200> which<00:10:50.360> only<00:10:50.560> syncs<00:10:50.880> with<00:10:50.959> the<00:10:51.040> RPC 00:10:51.389 --> 00:10:51.399 align:start position:0% manager which only syncs with the RPC 00:10:51.399 --> 00:10:53.670 align:start position:0% manager which only syncs with the RPC when<00:10:51.519> you<00:10:51.600> need<00:10:51.800> to<00:10:52.639> uh<00:10:52.720> we<00:10:52.839> made<00:10:53.000> sure<00:10:53.320> that 00:10:53.670 --> 00:10:53.680 align:start position:0% when you need to uh we made sure that 00:10:53.680 --> 00:10:55.710 align:start position:0% when you need to uh we made sure that transaction<00:10:54.160> context<00:10:54.560> is<00:10:54.720> pre-loaded<00:10:55.360> so 00:10:55.710 --> 00:10:55.720 align:start position:0% transaction context is pre-loaded so 00:10:55.720 --> 00:10:57.269 align:start position:0% transaction context is pre-loaded so when<00:10:55.839> you<00:10:56.040> click<00:10:56.440> you're<00:10:56.639> only<00:10:56.839> sending<00:10:57.160> the 00:10:57.269 --> 00:10:57.279 align:start position:0% when you click you're only sending the 00:10:57.279 --> 00:10:58.710 align:start position:0% when you click you're only sending the transaction<00:10:57.720> you're<00:10:57.839> not<00:10:58.000> doing<00:10:58.240> a<00:10:58.320> bunch<00:10:58.519> of 00:10:58.710 --> 00:10:58.720 align:start position:0% transaction you're not doing a bunch of 00:10:58.720 --> 00:11:00.790 align:start position:0% transaction you're not doing a bunch of other<00:10:58.920> things<00:10:59.440> so<00:10:59.639> that<00:10:59.800> it<00:10:59.959> feels<00:11:00.480> kind<00:11:00.600> of 00:11:00.790 --> 00:11:00.800 align:start position:0% other things so that it feels kind of 00:11:00.800 --> 00:11:02.910 align:start position:0% other things so that it feels kind of Snappy<00:11:01.800> and<00:11:01.880> we're<00:11:02.040> also<00:11:02.279> caching<00:11:02.680> gas 00:11:02.910 --> 00:11:02.920 align:start position:0% Snappy and we're also caching gas 00:11:02.920 --> 00:11:04.430 align:start position:0% Snappy and we're also caching gas estimates<00:11:03.320> so<00:11:03.440> we<00:11:03.560> don't<00:11:04.000> actually<00:11:04.200> need<00:11:04.320> to 00:11:04.430 --> 00:11:04.440 align:start position:0% estimates so we don't actually need to 00:11:04.440 --> 00:11:07.629 align:start position:0% estimates so we don't actually need to call<00:11:04.760> gas<00:11:04.959> estimate<00:11:05.399> gas<00:11:05.600> every<00:11:05.839> time<00:11:06.839> uh<00:11:07.200> and 00:11:07.629 --> 00:11:07.639 align:start position:0% call gas estimate gas every time uh and 00:11:07.639 --> 00:11:08.949 align:start position:0% call gas estimate gas every time uh and and<00:11:07.760> things<00:11:07.959> like 00:11:08.949 --> 00:11:08.959 align:start position:0% and things like 00:11:08.959 --> 00:11:13.310 align:start position:0% and things like that<00:11:09.959> but<00:11:10.560> you<00:11:11.160> know<00:11:12.160> um<00:11:12.519> however<00:11:12.720> you<00:11:12.880> spread 00:11:13.310 --> 00:11:13.320 align:start position:0% that but you know um however you spread 00:11:13.320 --> 00:11:14.790 align:start position:0% that but you know um however you spread read<00:11:13.560> nodes<00:11:13.880> across<00:11:14.160> the<00:11:14.279> world<00:11:14.560> if<00:11:14.639> you're 00:11:14.790 --> 00:11:14.800 align:start position:0% read nodes across the world if you're 00:11:14.800 --> 00:11:17.310 align:start position:0% read nodes across the world if you're using<00:11:15.000> an<00:11:15.160> L2<00:11:15.600> at<00:11:15.720> the<00:11:15.800> end<00:11:15.880> of<00:11:16.000> the<00:11:16.160> day<00:11:16.959> um 00:11:17.310 --> 00:11:17.320 align:start position:0% using an L2 at the end of the day um 00:11:17.320 --> 00:11:19.030 align:start position:0% using an L2 at the end of the day um transaction<00:11:17.800> confirmations<00:11:18.360> will<00:11:18.600> always<00:11:18.880> be 00:11:19.030 --> 00:11:19.040 align:start position:0% transaction confirmations will always be 00:11:19.040 --> 00:11:20.629 align:start position:0% transaction confirmations will always be the<00:11:19.200> fastest<00:11:19.680> the<00:11:19.800> closest<00:11:20.160> you<00:11:20.279> are<00:11:20.440> to<00:11:20.519> the 00:11:20.629 --> 00:11:20.639 align:start position:0% the fastest the closest you are to the 00:11:20.639 --> 00:11:22.230 align:start position:0% the fastest the closest you are to the sequencer<00:11:21.480> and<00:11:21.560> you're<00:11:21.680> going<00:11:21.800> to<00:11:21.920> have<00:11:22.040> to 00:11:22.230 --> 00:11:22.240 align:start position:0% sequencer and you're going to have to 00:11:22.240 --> 00:11:24.269 align:start position:0% sequencer and you're going to have to wait<00:11:22.639> for<00:11:22.800> the<00:11:22.920> block<00:11:23.320> time<00:11:23.880> before<00:11:24.120> you 00:11:24.269 --> 00:11:24.279 align:start position:0% wait for the block time before you 00:11:24.279 --> 00:11:26.710 align:start position:0% wait for the block time before you actually<00:11:24.560> get<00:11:24.680> your<00:11:25.160> confirmation<00:11:26.160> um<00:11:26.279> so<00:11:26.480> if 00:11:26.710 --> 00:11:26.720 align:start position:0% actually get your confirmation um so if 00:11:26.720 --> 00:11:29.430 align:start position:0% actually get your confirmation um so if you're<00:11:26.920> running<00:11:27.600> a<00:11:27.720> sequence<00:11:28.200> in<00:11:28.320> Europe<00:11:29.079> uh 00:11:29.430 --> 00:11:29.440 align:start position:0% you're running a sequence in Europe uh 00:11:29.440 --> 00:11:30.829 align:start position:0% you're running a sequence in Europe uh users<00:11:29.720> in<00:11:29.880> California<00:11:30.320> and<00:11:30.440> Japan<00:11:30.720> are 00:11:30.829 --> 00:11:30.839 align:start position:0% users in California and Japan are 00:11:30.839 --> 00:11:33.110 align:start position:0% users in California and Japan are getting<00:11:31.120> pretty<00:11:31.360> awful<00:11:31.839> performance<00:11:32.839> um<00:11:33.000> and 00:11:33.110 --> 00:11:33.120 align:start position:0% getting pretty awful performance um and 00:11:33.120 --> 00:11:34.750 align:start position:0% getting pretty awful performance um and the<00:11:33.240> experience<00:11:33.560> play<00:11:33.720> in<00:11:33.800> the<00:11:33.920> game<00:11:34.079> can<00:11:34.200> be 00:11:34.750 --> 00:11:34.760 align:start position:0% the experience play in the game can be 00:11:34.760 --> 00:11:36.110 align:start position:0% the experience play in the game can be very<00:11:35.000> different<00:11:35.240> from<00:11:35.399> users<00:11:35.720> who<00:11:35.839> are<00:11:35.959> close 00:11:36.110 --> 00:11:36.120 align:start position:0% very different from users who are close 00:11:36.120 --> 00:11:40.230 align:start position:0% very different from users who are close to<00:11:36.200> the<00:11:36.600> sequencer<00:11:37.600> um<00:11:38.079> so<00:11:39.079> what<00:11:39.200> can<00:11:39.360> we<00:11:39.519> do<00:11:40.040> to 00:11:40.230 --> 00:11:40.240 align:start position:0% to the sequencer um so what can we do to 00:11:40.240 --> 00:11:42.269 align:start position:0% to the sequencer um so what can we do to improve<00:11:40.680> this<00:11:41.160> you<00:11:41.279> know<00:11:41.560> what<00:11:41.800> how<00:11:41.920> do<00:11:42.079> we 00:11:42.269 --> 00:11:42.279 align:start position:0% improve this you know what how do we 00:11:42.279 --> 00:11:46.190 align:start position:0% improve this you know what how do we scale<00:11:43.240> U<00:11:43.560> block<00:11:43.880> building<00:11:44.880> U<00:11:45.040> so<00:11:45.680> one<00:11:45.920> way<00:11:46.120> we 00:11:46.190 --> 00:11:46.200 align:start position:0% scale U block building U so one way we 00:11:46.200 --> 00:11:47.790 align:start position:0% scale U block building U so one way we could<00:11:46.360> do<00:11:46.560> this<00:11:46.760> is<00:11:47.040> we<00:11:47.160> could<00:11:47.320> have<00:11:47.440> multiple 00:11:47.790 --> 00:11:47.800 align:start position:0% could do this is we could have multiple 00:11:47.800 --> 00:11:50.350 align:start position:0% could do this is we could have multiple chains<00:11:48.360> in<00:11:48.519> multiple<00:11:48.920> regions<00:11:49.680> maybe<00:11:50.200> they 00:11:50.350 --> 00:11:50.360 align:start position:0% chains in multiple regions maybe they 00:11:50.360 --> 00:11:53.590 align:start position:0% chains in multiple regions maybe they could<00:11:50.600> even<00:11:50.800> be<00:11:50.959> l3s<00:11:51.839> you<00:11:52.000> know<00:11:52.760> or<00:11:53.320> I<00:11:53.399> mean 00:11:53.590 --> 00:11:53.600 align:start position:0% could even be l3s you know or I mean 00:11:53.600 --> 00:11:54.990 align:start position:0% could even be l3s you know or I mean that<00:11:53.720> could<00:11:53.920> work<00:11:54.200> maybe<00:11:54.519> they<00:11:54.760> with 00:11:54.990 --> 00:11:55.000 align:start position:0% that could work maybe they with 00:11:55.000 --> 00:11:57.470 align:start position:0% that could work maybe they with optimism's<00:11:55.920> interrup<00:11:56.480> protocol<00:11:57.120> if<00:11:57.200> we<00:11:57.320> want 00:11:57.470 --> 00:11:57.480 align:start position:0% optimism's interrup protocol if we want 00:11:57.480 --> 00:11:59.670 align:start position:0% optimism's interrup protocol if we want to<00:11:57.639> bring<00:11:58.079> block<00:11:58.399> buildings<00:11:59.240> very<00:11:59.399> close<00:11:59.560> to 00:11:59.670 --> 00:11:59.680 align:start position:0% to bring block buildings very close to 00:11:59.680 --> 00:12:01.190 align:start position:0% to bring block buildings very close to the<00:11:59.760> user<00:12:00.240> but<00:12:00.519> there's<00:12:00.680> going<00:12:00.800> to<00:12:00.880> be<00:12:01.000> a<00:12:01.079> lot 00:12:01.190 --> 00:12:01.200 align:start position:0% the user but there's going to be a lot 00:12:01.200 --> 00:12:02.910 align:start position:0% the user but there's going to be a lot of<00:12:01.320> chains<00:12:01.720> you<00:12:01.800> know<00:12:01.959> you<00:12:02.240> you<00:12:02.320> don't<00:12:02.440> want<00:12:02.519> to 00:12:02.910 --> 00:12:02.920 align:start position:0% of chains you know you you don't want to 00:12:02.920 --> 00:12:04.790 align:start position:0% of chains you know you you don't want to be<00:12:03.079> running<00:12:03.480> tons<00:12:03.720> of<00:12:03.880> different<00:12:04.120> chains<00:12:04.639> all 00:12:04.790 --> 00:12:04.800 align:start position:0% be running tons of different chains all 00:12:04.800 --> 00:12:06.829 align:start position:0% be running tons of different chains all these<00:12:04.959> different<00:12:05.240> regions<00:12:06.079> especially<00:12:06.600> when 00:12:06.829 --> 00:12:06.839 align:start position:0% these different regions especially when 00:12:06.839 --> 00:12:08.990 align:start position:0% these different regions especially when maybe<00:12:07.040> your<00:12:07.200> users<00:12:07.480> are<00:12:07.639> moving<00:12:08.160> so<00:12:08.639> you<00:12:08.839> just 00:12:08.990 --> 00:12:09.000 align:start position:0% maybe your users are moving so you just 00:12:09.000 --> 00:12:11.150 align:start position:0% maybe your users are moving so you just want<00:12:09.160> to<00:12:09.360> be<00:12:09.839> loading<00:12:10.360> block<00:12:10.600> building<00:12:10.920> at<00:12:11.040> the 00:12:11.150 --> 00:12:11.160 align:start position:0% want to be loading block building at the 00:12:11.160 --> 00:12:13.590 align:start position:0% want to be loading block building at the edge<00:12:11.639> wherever<00:12:12.000> you<00:12:12.160> need<00:12:12.360> to<00:12:13.040> so<00:12:13.240> what<00:12:13.360> if<00:12:13.480> we 00:12:13.590 --> 00:12:13.600 align:start position:0% edge wherever you need to so what if we 00:12:13.600 --> 00:12:15.590 align:start position:0% edge wherever you need to so what if we could<00:12:13.760> run<00:12:14.040> block<00:12:14.320> building<00:12:14.600> at<00:12:14.760> the<00:12:14.880> edge 00:12:15.590 --> 00:12:15.600 align:start position:0% could run block building at the edge 00:12:15.600 --> 00:12:18.590 align:start position:0% could run block building at the edge when<00:12:15.800> needed<00:12:16.600> just<00:12:16.800> for<00:12:16.959> a<00:12:17.120> piece<00:12:17.279> of<00:12:17.600> state 00:12:18.590 --> 00:12:18.600 align:start position:0% when needed just for a piece of state 00:12:18.600 --> 00:12:20.870 align:start position:0% when needed just for a piece of state and<00:12:19.279> uh<00:12:19.519> for<00:12:19.720> for<00:12:19.839> example<00:12:20.160> imagine<00:12:20.600> you<00:12:20.720> get 00:12:20.870 --> 00:12:20.880 align:start position:0% and uh for for example imagine you get 00:12:20.880 --> 00:12:22.389 align:start position:0% and uh for for example imagine you get matched<00:12:21.279> with<00:12:21.600> different<00:12:21.839> players<00:12:22.120> in<00:12:22.240> your 00:12:22.389 --> 00:12:22.399 align:start position:0% matched with different players in your 00:12:22.399 --> 00:12:24.949 align:start position:0% matched with different players in your area<00:12:22.680> and<00:12:22.760> you<00:12:22.880> start<00:12:23.240> an<00:12:23.399> ultra<00:12:24.199> low<00:12:24.519> latency 00:12:24.949 --> 00:12:24.959 align:start position:0% area and you start an ultra low latency 00:12:24.959 --> 00:12:29.470 align:start position:0% area and you start an ultra low latency game<00:12:25.399> match<00:12:26.680> um<00:12:27.680> and<00:12:27.880> so<00:12:28.560> I<00:12:28.639> will<00:12:28.839> proof<00:12:29.320> this 00:12:29.470 --> 00:12:29.480 align:start position:0% game match um and so I will proof this 00:12:29.480 --> 00:12:31.110 align:start position:0% game match um and so I will proof this by<00:12:29.560> saying<00:12:29.800> this<00:12:29.920> is<00:12:30.120> probably<00:12:30.519> not<00:12:30.720> the<00:12:30.839> only 00:12:31.110 --> 00:12:31.120 align:start position:0% by saying this is probably not the only 00:12:31.120 --> 00:12:33.509 align:start position:0% by saying this is probably not the only solution<00:12:31.920> um<00:12:32.519> but<00:12:32.720> this<00:12:32.800> is<00:12:32.920> the<00:12:33.040> one<00:12:33.199> we're 00:12:33.509 --> 00:12:33.519 align:start position:0% solution um but this is the one we're 00:12:33.519 --> 00:12:36.670 align:start position:0% solution um but this is the one we're currently<00:12:34.040> validating<00:12:35.040> as<00:12:35.120> a<00:12:35.440> prototype<00:12:36.440> and 00:12:36.670 --> 00:12:36.680 align:start position:0% currently validating as a prototype and 00:12:36.680 --> 00:12:39.030 align:start position:0% currently validating as a prototype and so<00:12:37.360> I'll<00:12:37.800> I'll<00:12:37.920> try<00:12:38.079> to<00:12:38.240> explain<00:12:38.480> a<00:12:38.560> little<00:12:38.760> bit 00:12:39.030 --> 00:12:39.040 align:start position:0% so I'll I'll try to explain a little bit 00:12:39.040 --> 00:12:41.509 align:start position:0% so I'll I'll try to explain a little bit how<00:12:39.279> this<00:12:39.360> is<00:12:39.560> made<00:12:39.839> so<00:12:40.600> if<00:12:40.680> you<00:12:40.880> remember<00:12:41.320> the 00:12:41.509 --> 00:12:41.519 align:start position:0% how this is made so if you remember the 00:12:41.519 --> 00:12:43.870 align:start position:0% how this is made so if you remember the the<00:12:41.600> previous<00:12:42.160> here<00:12:42.480> we're<00:12:42.760> like<00:12:43.519> actually 00:12:43.870 --> 00:12:43.880 align:start position:0% the previous here we're like actually 00:12:43.880 --> 00:12:45.790 align:start position:0% the previous here we're like actually deploying<00:12:44.440> block<00:12:44.720> Builders<00:12:45.240> directly<00:12:45.519> on<00:12:45.680> the 00:12:45.790 --> 00:12:45.800 align:start position:0% deploying block Builders directly on the 00:12:45.800 --> 00:12:47.949 align:start position:0% deploying block Builders directly on the edge<00:12:46.199> and<00:12:46.320> we<00:12:46.480> call<00:12:46.680> them<00:12:46.959> points<00:12:47.199> of<00:12:47.399> presence 00:12:47.949 --> 00:12:47.959 align:start position:0% edge and we call them points of presence 00:12:47.959 --> 00:12:51.030 align:start position:0% edge and we call them points of presence like<00:12:48.519> um<00:12:49.079> for<00:12:49.440> CDN<00:12:50.399> and<00:12:50.519> what<00:12:50.639> they<00:12:50.760> do<00:12:50.880> is 00:12:51.030 --> 00:12:51.040 align:start position:0% like um for CDN and what they do is 00:12:51.040 --> 00:12:52.750 align:start position:0% like um for CDN and what they do is essentially<00:12:51.440> they<00:12:51.639> act<00:12:51.880> like<00:12:52.000> a<00:12:52.240> full 00:12:52.750 --> 00:12:52.760 align:start position:0% essentially they act like a full 00:12:52.760 --> 00:12:55.150 align:start position:0% essentially they act like a full ethereum<00:12:53.320> RPC<00:12:54.240> but<00:12:54.399> they<00:12:54.519> only<00:12:54.760> pull<00:12:55.040> the 00:12:55.150 --> 00:12:55.160 align:start position:0% ethereum RPC but they only pull the 00:12:55.160 --> 00:12:57.670 align:start position:0% ethereum RPC but they only pull the state<00:12:55.440> they<00:12:55.600> need<00:12:55.920> from<00:12:56.079> the<00:12:56.240> Upstream<00:12:57.040> in<00:12:57.160> our 00:12:57.670 --> 00:12:57.680 align:start position:0% state they need from the Upstream in our 00:12:57.680 --> 00:13:00.350 align:start position:0% state they need from the Upstream in our situation<00:12:58.680> um<00:12:59.199> the<00:12:59.320> pubs<00:12:59.639> that<00:12:59.800> just<00:12:59.959> request 00:13:00.350 --> 00:13:00.360 align:start position:0% situation um the pubs that just request 00:13:00.360 --> 00:13:02.470 align:start position:0% situation um the pubs that just request the<00:13:00.440> latest<00:13:00.760> version<00:13:01.000> of<00:13:01.120> the<00:13:01.279> State<00:13:02.279> uh<00:13:02.360> and 00:13:02.470 --> 00:13:02.480 align:start position:0% the latest version of the State uh and 00:13:02.480 --> 00:13:04.230 align:start position:0% the latest version of the State uh and if<00:13:02.600> we<00:13:02.680> need<00:13:02.839> to<00:13:03.000> write<00:13:03.240> to<00:13:03.440> that<00:13:03.600> state<00:13:04.079> a 00:13:04.230 --> 00:13:04.240 align:start position:0% if we need to write to that state a 00:13:04.240 --> 00:13:05.870 align:start position:0% if we need to write to that state a point<00:13:04.440> of<00:13:04.600> presence<00:13:05.040> can<00:13:05.160> then<00:13:05.360> acquire<00:13:05.720> a 00:13:05.870 --> 00:13:05.880 align:start position:0% point of presence can then acquire a 00:13:05.880 --> 00:13:07.550 align:start position:0% point of presence can then acquire a lock<00:13:06.120> on<00:13:06.279> it<00:13:06.639> and<00:13:06.760> this<00:13:06.839> is<00:13:07.000> handled<00:13:07.360> at<00:13:07.480> the 00:13:07.550 --> 00:13:07.560 align:start position:0% lock on it and this is handled at the 00:13:07.560 --> 00:13:09.430 align:start position:0% lock on it and this is handled at the mud<00:13:07.800> level<00:13:08.360> because<00:13:08.519> we<00:13:08.600> have<00:13:08.839> static<00:13:09.120> ways<00:13:09.279> of 00:13:09.430 --> 00:13:09.440 align:start position:0% mud level because we have static ways of 00:13:09.440 --> 00:13:11.550 align:start position:0% mud level because we have static ways of determining<00:13:10.040> you<00:13:10.160> know<00:13:10.680> which<00:13:10.880> mud<00:13:11.120> table<00:13:11.399> the 00:13:11.550 --> 00:13:11.560 align:start position:0% determining you know which mud table the 00:13:11.560 --> 00:13:13.550 align:start position:0% determining you know which mud table the pup<00:13:11.760> needs<00:13:11.920> to<00:13:12.079> write<00:13:12.279> to<00:13:12.519> and<00:13:12.639> then<00:13:12.959> only<00:13:13.320> the 00:13:13.550 --> 00:13:13.560 align:start position:0% pup needs to write to and then only the 00:13:13.560 --> 00:13:15.670 align:start position:0% pup needs to write to and then only the pup<00:13:13.839> can<00:13:14.240> batch<00:13:14.560> transaction<00:13:14.959> to<00:13:15.160> modify<00:13:15.519> that 00:13:15.670 --> 00:13:15.680 align:start position:0% pup can batch transaction to modify that 00:13:15.680 --> 00:13:17.150 align:start position:0% pup can batch transaction to modify that state<00:13:15.959> and<00:13:16.120> then<00:13:16.480> they<00:13:16.600> can<00:13:16.760> send<00:13:17.000> the 00:13:17.150 --> 00:13:17.160 align:start position:0% state and then they can send the 00:13:17.160 --> 00:13:18.910 align:start position:0% state and then they can send the confirmations<00:13:17.839> immediately<00:13:18.639> without 00:13:18.910 --> 00:13:18.920 align:start position:0% confirmations immediately without 00:13:18.920 --> 00:13:20.550 align:start position:0% confirmations immediately without waiting<00:13:19.160> for<00:13:19.320> the<00:13:19.519> actual<00:13:19.800> chain<00:13:20.079> payload<00:13:20.480> to 00:13:20.550 --> 00:13:20.560 align:start position:0% waiting for the actual chain payload to 00:13:20.560 --> 00:13:23.350 align:start position:0% waiting for the actual chain payload to be<00:13:20.680> built<00:13:21.480> uh<00:13:21.560> so<00:13:21.839> p<00:13:22.160> p<00:13:22.360> Builders<00:13:22.760> can<00:13:22.920> send<00:13:23.199> in 00:13:23.350 --> 00:13:23.360 align:start position:0% be built uh so p p Builders can send in 00:13:23.360 --> 00:13:25.670 align:start position:0% be built uh so p p Builders can send in transaction<00:13:23.760> batches<00:13:24.079> to<00:13:24.160> the<00:13:24.519> Upstream<00:13:25.519> uh 00:13:25.670 --> 00:13:25.680 align:start position:0% transaction batches to the Upstream uh 00:13:25.680 --> 00:13:28.150 align:start position:0% transaction batches to the Upstream uh eventually<00:13:26.680> and<00:13:27.079> uh<00:13:27.240> just<00:13:27.399> in<00:13:27.600> time<00:13:27.959> before 00:13:28.150 --> 00:13:28.160 align:start position:0% eventually and uh just in time before 00:13:28.160 --> 00:13:29.670 align:start position:0% eventually and uh just in time before the<00:13:28.360> block<00:13:28.639> get<00:13:28.800> built 00:13:29.670 --> 00:13:29.680 align:start position:0% the block get built 00:13:29.680 --> 00:13:31.550 align:start position:0% the block get built um<00:13:29.920> and<00:13:30.040> then<00:13:30.199> no<00:13:30.399> other<00:13:30.959> pop<00:13:31.199> Builder<00:13:31.440> can 00:13:31.550 --> 00:13:31.560 align:start position:0% um and then no other pop Builder can 00:13:31.560 --> 00:13:33.870 align:start position:0% um and then no other pop Builder can modify<00:13:31.920> that<00:13:32.079> state<00:13:32.680> so<00:13:33.240> and<00:13:33.360> then<00:13:33.480> you<00:13:33.600> know 00:13:33.870 --> 00:13:33.880 align:start position:0% modify that state so and then you know 00:13:33.880 --> 00:13:35.670 align:start position:0% modify that state so and then you know you<00:13:34.000> have<00:13:34.160> basic<00:13:34.399> CDN<00:13:34.880> stuff<00:13:35.160> like<00:13:35.320> the<00:13:35.440> state 00:13:35.670 --> 00:13:35.680 align:start position:0% you have basic CDN stuff like the state 00:13:35.680 --> 00:13:37.990 align:start position:0% you have basic CDN stuff like the state locks<00:13:36.160> are<00:13:36.360> cleared<00:13:37.079> you<00:13:37.199> know<00:13:37.480> on<00:13:37.760> least 00:13:37.990 --> 00:13:38.000 align:start position:0% locks are cleared you know on least 00:13:38.000 --> 00:13:40.110 align:start position:0% locks are cleared you know on least recently<00:13:38.399> used<00:13:38.839> basis<00:13:39.720> um<00:13:39.839> and<00:13:39.959> they're 00:13:40.110 --> 00:13:40.120 align:start position:0% recently used basis um and they're 00:13:40.120 --> 00:13:41.710 align:start position:0% recently used basis um and they're automatic<00:13:40.519> cleaned<00:13:40.839> up<00:13:41.000> once<00:13:41.199> you<00:13:41.360> have<00:13:41.519> more 00:13:41.710 --> 00:13:41.720 align:start position:0% automatic cleaned up once you have more 00:13:41.720 --> 00:13:44.069 align:start position:0% automatic cleaned up once you have more data<00:13:41.959> that<00:13:42.120> comes<00:13:42.360> in<00:13:42.600> and<00:13:42.920> and<00:13:43.399> your<00:13:43.600> data<00:13:43.959> has 00:13:44.069 --> 00:13:44.079 align:start position:0% data that comes in and and your data has 00:13:44.079 --> 00:13:47.430 align:start position:0% data that comes in and and your data has been<00:13:44.199> stale<00:13:44.600> for<00:13:44.720> a 00:13:47.430 --> 00:13:47.440 align:start position:0% 00:13:47.440 --> 00:13:50.150 align:start position:0% while<00:13:48.440> um<00:13:48.680> and<00:13:48.839> then<00:13:49.120> these<00:13:49.240> are<00:13:49.920> other 00:13:50.150 --> 00:13:50.160 align:start position:0% while um and then these are other 00:13:50.160 --> 00:13:51.629 align:start position:0% while um and then these are other examples<00:13:50.560> of<00:13:50.720> things<00:13:50.880> that<00:13:51.000> you<00:13:51.079> can<00:13:51.199> speed<00:13:51.440> up 00:13:51.629 --> 00:13:51.639 align:start position:0% examples of things that you can speed up 00:13:51.639 --> 00:13:53.590 align:start position:0% examples of things that you can speed up once<00:13:51.800> you<00:13:51.880> can<00:13:52.000> run<00:13:52.240> them<00:13:52.399> on<00:13:52.519> the<00:13:52.680> edge<00:13:53.360> uh<00:13:53.480> for 00:13:53.590 --> 00:13:53.600 align:start position:0% once you can run them on the edge uh for 00:13:53.600 --> 00:13:55.550 align:start position:0% once you can run them on the edge uh for example<00:13:54.199> when<00:13:54.360> you're<00:13:54.519> estimating<00:13:54.959> the<00:13:55.160> gas 00:13:55.550 --> 00:13:55.560 align:start position:0% example when you're estimating the gas 00:13:55.560 --> 00:13:57.870 align:start position:0% example when you're estimating the gas or<00:13:55.800> you're<00:13:56.000> managing<00:13:56.320> the<00:13:56.440> nonces<00:13:57.120> and<00:13:57.279> so<00:13:57.759> you 00:13:57.870 --> 00:13:57.880 align:start position:0% or you're managing the nonces and so you 00:13:57.880 --> 00:14:00.949 align:start position:0% or you're managing the nonces and so you can<00:13:58.079> have<00:13:58.399> extremely<00:13:59.199> size<00:13:59.519> gas<00:13:59.800> estimates<00:14:00.800> uh 00:14:00.949 --> 00:14:00.959 align:start position:0% can have extremely size gas estimates uh 00:14:00.959 --> 00:14:02.790 align:start position:0% can have extremely size gas estimates uh by<00:14:01.079> running<00:14:01.399> them<00:14:01.600> directly<00:14:01.920> on<00:14:02.040> the<00:14:02.160> edge<00:14:02.680> you 00:14:02.790 --> 00:14:02.800 align:start position:0% by running them directly on the edge you 00:14:02.800 --> 00:14:05.670 align:start position:0% by running them directly on the edge you can<00:14:03.079> have<00:14:03.720> uh<00:14:04.279> fresh<00:14:04.680> non<00:14:05.079> management<00:14:05.560> when 00:14:05.670 --> 00:14:05.680 align:start position:0% can have uh fresh non management when 00:14:05.680 --> 00:14:08.030 align:start position:0% can have uh fresh non management when you're<00:14:05.759> sinking<00:14:06.160> it<00:14:06.600> and<00:14:06.680> you<00:14:06.759> can<00:14:06.920> do<00:14:07.120> even<00:14:07.320> do 00:14:08.030 --> 00:14:08.040 align:start position:0% you're sinking it and you can do even do 00:14:08.040 --> 00:14:10.870 align:start position:0% you're sinking it and you can do even do uh<00:14:08.160> ERC<00:14:08.600> 4337<00:14:09.519> user<00:14:09.800> are<00:14:10.040> bundling<00:14:10.480> on<00:14:10.680> the 00:14:10.870 --> 00:14:10.880 align:start position:0% uh ERC 4337 user are bundling on the 00:14:10.880 --> 00:14:12.790 align:start position:0% uh ERC 4337 user are bundling on the edge<00:14:11.680> um<00:14:11.959> and 00:14:12.790 --> 00:14:12.800 align:start position:0% edge um and 00:14:12.800 --> 00:14:15.949 align:start position:0% edge um and so<00:14:13.800> I<00:14:13.839> mean<00:14:14.360> this<00:14:14.720> just<00:14:15.199> accelerates<00:14:15.639> a<00:14:15.759> lot<00:14:15.839> of 00:14:15.949 --> 00:14:15.959 align:start position:0% so I mean this just accelerates a lot of 00:14:15.959 --> 00:14:18.150 align:start position:0% so I mean this just accelerates a lot of things<00:14:16.199> and<00:14:16.720> we<00:14:16.959> we<00:14:17.079> were<00:14:17.639> uh<00:14:17.759> when<00:14:17.880> we<00:14:18.000> were 00:14:18.150 --> 00:14:18.160 align:start position:0% things and we we were uh when we were 00:14:18.160 --> 00:14:20.790 align:start position:0% things and we we were uh when we were testing<00:14:18.600> this<00:14:19.240> uh<00:14:19.399> it<00:14:19.560> actually<00:14:19.759> ended<00:14:20.000> up 00:14:20.790 --> 00:14:20.800 align:start position:0% testing this uh it actually ended up 00:14:20.800 --> 00:14:25.110 align:start position:0% testing this uh it actually ended up getting<00:14:21.079> to<00:14:21.480> a<00:14:21.639> very<00:14:21.959> very<00:14:22.199> good 00:14:25.110 --> 00:14:25.120 align:start position:0% 00:14:25.120 --> 00:14:27.189 align:start position:0% performance<00:14:26.120> actually<00:14:26.399> I'll<00:14:26.600> I'll<00:14:26.880> show<00:14:27.079> you 00:14:27.189 --> 00:14:27.199 align:start position:0% performance actually I'll I'll show you 00:14:27.199 --> 00:14:30.550 align:start position:0% performance actually I'll I'll show you a<00:14:27.360> little<00:14:27.759> demo<00:14:28.560> um<00:14:28.759> I<00:14:29.199> if<00:14:29.360> I<00:14:29.680> if<00:14:29.800> I<00:14:29.959> press<00:14:30.199> play 00:14:30.550 --> 00:14:30.560 align:start position:0% a little demo um I if I if I press play 00:14:30.560 --> 00:14:34.069 align:start position:0% a little demo um I if I if I press play this<00:14:30.759> will<00:14:30.959> work<00:14:31.320> okay<00:14:31.759> cool<00:14:32.759> um<00:14:33.519> so<00:14:33.759> this<00:14:33.959> we 00:14:34.069 --> 00:14:34.079 align:start position:0% this will work okay cool um so this we 00:14:34.079 --> 00:14:36.710 align:start position:0% this will work okay cool um so this we implemented<00:14:34.560> this<00:14:35.079> the<00:14:35.480> this<00:14:36.000> uh<00:14:36.279> this<00:14:36.480> game 00:14:36.710 --> 00:14:36.720 align:start position:0% implemented this the this uh this game 00:14:36.720 --> 00:14:38.670 align:start position:0% implemented this the this uh this game just<00:14:36.920> to<00:14:37.160> demo<00:14:37.440> this<00:14:37.639> prototype<00:14:38.399> uh<00:14:38.480> it<00:14:38.560> is 00:14:38.670 --> 00:14:38.680 align:start position:0% just to demo this prototype uh it is 00:14:38.680 --> 00:14:40.790 align:start position:0% just to demo this prototype uh it is multiplayer<00:14:39.480> every<00:14:39.680> time<00:14:39.800> you<00:14:39.920> move<00:14:40.199> the<00:14:40.320> fly 00:14:40.790 --> 00:14:40.800 align:start position:0% multiplayer every time you move the fly 00:14:40.800 --> 00:14:42.949 align:start position:0% multiplayer every time you move the fly this<00:14:40.880> is<00:14:41.000> a<00:14:41.160> transaction<00:14:41.720> that<00:14:41.839> is<00:14:42.000> executed 00:14:42.949 --> 00:14:42.959 align:start position:0% this is a transaction that is executed 00:14:42.959 --> 00:14:44.509 align:start position:0% this is a transaction that is executed and<00:14:43.240> a<00:14:43.360> receipt<00:14:43.720> that<00:14:43.800> is<00:14:43.920> sent<00:14:44.160> back<00:14:44.279> to<00:14:44.399> the 00:14:44.509 --> 00:14:44.519 align:start position:0% and a receipt that is sent back to the 00:14:44.519 --> 00:14:46.430 align:start position:0% and a receipt that is sent back to the browser<00:14:44.800> so<00:14:44.920> you<00:14:45.000> can<00:14:45.160> see<00:14:45.399> like<00:14:45.560> all<00:14:45.680> of<00:14:45.880> these 00:14:46.430 --> 00:14:46.440 align:start position:0% browser so you can see like all of these 00:14:46.440 --> 00:14:48.790 align:start position:0% browser so you can see like all of these 20<00:14:46.759> milliseconds<00:14:47.639> here<00:14:48.199> um<00:14:48.440> every<00:14:48.639> time 00:14:48.790 --> 00:14:48.800 align:start position:0% 20 milliseconds here um every time 00:14:48.800 --> 00:14:50.870 align:start position:0% 20 milliseconds here um every time you're<00:14:49.800> executing<00:14:50.199> a<00:14:50.320> transaction<00:14:50.720> and 00:14:50.870 --> 00:14:50.880 align:start position:0% you're executing a transaction and 00:14:50.880 --> 00:14:55.509 align:start position:0% you're executing a transaction and getting<00:14:51.040> the<00:14:51.199> receipt<00:14:51.600> back<00:14:52.839> um<00:14:53.839> and<00:14:54.240> so<00:14:55.240> I 00:14:55.509 --> 00:14:55.519 align:start position:0% getting the receipt back um and so I 00:14:55.519 --> 00:14:56.670 align:start position:0% getting the receipt back um and so I this<00:14:55.600> is<00:14:55.720> still<00:14:55.880> a<00:14:56.000> prototype<00:14:56.399> but<00:14:56.519> if<00:14:56.600> you 00:14:56.670 --> 00:14:56.680 align:start position:0% this is still a prototype but if you 00:14:56.680 --> 00:15:00.030 align:start position:0% this is still a prototype but if you want<00:14:56.800> to<00:14:57.079> learn<00:14:57.399> more<00:14:57.920> and<00:14:58.440> get<00:14:58.560> to<00:14:58.720> know 00:15:00.030 --> 00:15:00.040 align:start position:0% want to learn more and get to know 00:15:00.040 --> 00:15:01.590 align:start position:0% want to learn more and get to know actually<00:15:00.360> test<00:15:00.639> the<00:15:00.759> thing<00:15:01.000> yourself<00:15:01.360> get<00:15:01.480> a 00:15:01.590 --> 00:15:01.600 align:start position:0% actually test the thing yourself get a 00:15:01.600 --> 00:15:03.389 align:start position:0% actually test the thing yourself get a feel<00:15:01.800> for<00:15:02.000> it<00:15:02.440> you<00:15:02.560> can<00:15:02.680> come<00:15:02.839> to<00:15:03.000> Mud<00:15:03.199> day 00:15:03.389 --> 00:15:03.399 align:start position:0% feel for it you can come to Mud day 00:15:03.399 --> 00:15:05.509 align:start position:0% feel for it you can come to Mud day tomorrow<00:15:04.000> and<00:15:04.320> actually<00:15:04.600> experience<00:15:05.199> the<00:15:05.399> all 00:15:05.509 --> 00:15:05.519 align:start position:0% tomorrow and actually experience the all 00:15:05.519 --> 00:15:08.910 align:start position:0% tomorrow and actually experience the all the<00:15:05.720> games<00:15:06.720> um<00:15:07.440> and<00:15:07.839> or<00:15:08.120> learn<00:15:08.360> more<00:15:08.519> about<00:15:08.720> how 00:15:08.910 --> 00:15:08.920 align:start position:0% the games um and or learn more about how 00:15:08.920 --> 00:15:11.230 align:start position:0% the games um and or learn more about how all<00:15:09.040> these<00:15:09.199> things 00:15:11.230 --> 00:15:11.240 align:start position:0% all these things 00:15:11.240 --> 00:15:18.820 align:start position:0% all these things works<00:15:12.240> all<00:15:12.440> right<00:15:13.000> thanks<00:15:13.279> for 00:15:18.820 --> 00:15:18.830 align:start position:0% 00:15:18.830 --> 00:15:20.829 align:start position:0% [Applause] 00:15:20.829 --> 00:15:20.839 align:start position:0% [Applause] 00:15:20.839 --> 00:15:23.470 align:start position:0% [Applause] listening 00:15:23.470 --> 00:15:23.480 align:start position:0% listening 00:15:23.480 --> 00:15:26.629 align:start position:0% listening chran<00:15:24.480> that<00:15:24.600> was<00:15:24.680> a<00:15:24.800> great<00:15:25.519> presentation<00:15:26.519> I 00:15:26.629 --> 00:15:26.639 align:start position:0% chran that was a great presentation I 00:15:26.639 --> 00:15:28.470 align:start position:0% chran that was a great presentation I noticed<00:15:27.079> that<00:15:27.279> no<00:15:27.399> one<00:15:27.680> had<00:15:27.839> any<00:15:28.079> questions<00:15:28.360> in 00:15:28.470 --> 00:15:28.480 align:start position:0% noticed that no one had any questions in 00:15:28.480 --> 00:15:30.030 align:start position:0% noticed that no one had any questions in the<00:15:28.600> Q&A 00:15:30.030 --> 00:15:30.040 align:start position:0% the Q&A 00:15:30.040 --> 00:15:32.110 align:start position:0% the Q&A oh<00:15:30.160> it's<00:15:30.360> coming<00:15:30.839> okay<00:15:31.560> cuz<00:15:31.680> I<00:15:31.759> was<00:15:31.920> going<00:15:32.000> to 00:15:32.110 --> 00:15:32.120 align:start position:0% oh it's coming okay cuz I was going to 00:15:32.120 --> 00:15:33.990 align:start position:0% oh it's coming okay cuz I was going to front<00:15:32.319> run<00:15:32.560> you 00:15:33.990 --> 00:15:34.000 align:start position:0% front run you 00:15:34.000 --> 00:15:39.030 align:start position:0% front run you guys<00:15:35.000> no<00:15:35.199> no<00:15:35.360> no<00:15:35.480> no<00:15:35.600> no<00:15:35.720> no<00:15:35.800> no<00:15:35.959> no<00:15:36.120> no<00:15:36.399> audience 00:15:39.030 --> 00:15:39.040 align:start position:0% 00:15:39.040 --> 00:15:41.550 align:start position:0% first<00:15:40.040> oh<00:15:40.319> man<00:15:40.639> okay<00:15:40.839> I'm<00:15:40.920> gonna<00:15:41.199> ask<00:15:41.360> my 00:15:41.550 --> 00:15:41.560 align:start position:0% first oh man okay I'm gonna ask my 00:15:41.560 --> 00:15:43.749 align:start position:0% first oh man okay I'm gonna ask my question<00:15:41.839> then<00:15:42.000> to<00:15:42.079> fill<00:15:42.279> the<00:15:42.480> G<00:15:42.680> time<00:15:42.920> Gap 00:15:43.749 --> 00:15:43.759 align:start position:0% question then to fill the G time Gap 00:15:43.759 --> 00:15:45.870 align:start position:0% question then to fill the G time Gap okay<00:15:44.160> so<00:15:44.680> this<00:15:44.959> seems<00:15:45.240> really<00:15:45.440> awesome<00:15:45.720> and 00:15:45.870 --> 00:15:45.880 align:start position:0% okay so this seems really awesome and 00:15:45.880 --> 00:15:47.910 align:start position:0% okay so this seems really awesome and amazing<00:15:46.560> but<00:15:46.720> given<00:15:46.959> my<00:15:47.120> background<00:15:47.639> I<00:15:47.720> do<00:15:47.839> a 00:15:47.910 --> 00:15:47.920 align:start position:0% amazing but given my background I do a 00:15:47.920 --> 00:15:50.230 align:start position:0% amazing but given my background I do a lot<00:15:48.040> of<00:15:48.160> security<00:15:48.560> research<00:15:49.240> so<00:15:49.399> all<00:15:49.560> I<00:15:49.680> see<00:15:49.959> is 00:15:50.230 --> 00:15:50.240 align:start position:0% lot of security research so all I see is 00:15:50.240 --> 00:15:52.829 align:start position:0% lot of security research so all I see is oh<00:15:50.360> my<00:15:50.560> God<00:15:51.000> scaling<00:15:51.800> extremely 00:15:52.829 --> 00:15:52.839 align:start position:0% oh my God scaling extremely 00:15:52.839 --> 00:15:55.829 align:start position:0% oh my God scaling extremely quickly<00:15:53.839> what<00:15:53.959> are<00:15:54.240> your<00:15:54.480> thoughts<00:15:54.720> around 00:15:55.829 --> 00:15:55.839 align:start position:0% quickly what are your thoughts around 00:15:55.839 --> 00:15:59.470 align:start position:0% quickly what are your thoughts around security<00:15:56.839> I<00:15:56.920> mean<00:15:57.880> obviously<00:15:58.560> you<00:15:58.759> have<00:15:59.079> have 00:15:59.470 --> 00:15:59.480 align:start position:0% security I mean obviously you have have 00:15:59.480 --> 00:16:00.670 align:start position:0% security I mean obviously you have have all<00:15:59.600> the<00:15:59.720> security<00:16:00.120> Assumption<00:16:00.440> of<00:16:00.560> the 00:16:00.670 --> 00:16:00.680 align:start position:0% all the security Assumption of the 00:16:00.680 --> 00:16:02.670 align:start position:0% all the security Assumption of the ethereum<00:16:01.120> protocol<00:16:01.720> which<00:16:01.839> are<00:16:02.199> respected 00:16:02.670 --> 00:16:02.680 align:start position:0% ethereum protocol which are respected 00:16:02.680 --> 00:16:04.509 align:start position:0% ethereum protocol which are respected you<00:16:02.800> know<00:16:02.959> we're<00:16:03.279> part<00:16:03.440> of<00:16:03.800> the<00:16:03.920> super<00:16:04.240> chain 00:16:04.509 --> 00:16:04.519 align:start position:0% you know we're part of the super chain 00:16:04.519 --> 00:16:06.790 align:start position:0% you know we're part of the super chain we're<00:16:04.680> trying<00:16:04.880> to<00:16:05.000> do<00:16:05.160> all<00:16:05.319> these<00:16:05.560> upgrades<00:16:06.199> so 00:16:06.790 --> 00:16:06.800 align:start position:0% we're trying to do all these upgrades so 00:16:06.800 --> 00:16:09.269 align:start position:0% we're trying to do all these upgrades so everything<00:16:07.279> is<00:16:07.839> that<00:16:08.000> is<00:16:08.600> basically<00:16:08.959> touching 00:16:09.269 --> 00:16:09.279 align:start position:0% everything is that is basically touching 00:16:09.279 --> 00:16:10.990 align:start position:0% everything is that is basically touching the<00:16:09.399> ethereum<00:16:09.759> protocol<00:16:10.160> has<00:16:10.399> the<00:16:10.519> guarantees 00:16:10.990 --> 00:16:11.000 align:start position:0% the ethereum protocol has the guarantees 00:16:11.000 --> 00:16:14.470 align:start position:0% the ethereum protocol has the guarantees of<00:16:11.519> Alda<00:16:12.079> chains<00:16:12.519> from<00:16:12.680> the<00:16:12.759> op<00:16:13.079> stack<00:16:14.000> uh<00:16:14.160> and 00:16:14.470 --> 00:16:14.480 align:start position:0% of Alda chains from the op stack uh and 00:16:14.480 --> 00:16:18.350 align:start position:0% of Alda chains from the op stack uh and you<00:16:14.880> know<00:16:15.880> all<00:16:16.040> of<00:16:16.240> this<00:16:16.480> is<00:16:16.880> audited<00:16:17.440> or<00:16:17.759> like 00:16:18.350 --> 00:16:18.360 align:start position:0% you know all of this is audited or like 00:16:18.360 --> 00:16:21.309 align:start position:0% you know all of this is audited or like has<00:16:18.680> is<00:16:18.800> reviewed<00:16:19.240> by<00:16:19.360> the<00:16:19.480> op<00:16:19.800> stack<00:16:20.360> uh<00:16:20.480> team 00:16:21.309 --> 00:16:21.319 align:start position:0% has is reviewed by the op stack uh team 00:16:21.319 --> 00:16:23.910 align:start position:0% has is reviewed by the op stack uh team and<00:16:21.440> then<00:16:22.199> um<00:16:22.759> on<00:16:23.040> the<00:16:23.399> things<00:16:23.680> that<00:16:23.800> we 00:16:23.910 --> 00:16:23.920 align:start position:0% and then um on the things that we 00:16:23.920 --> 00:16:25.990 align:start position:0% and then um on the things that we control<00:16:24.279> then<00:16:24.440> it's<00:16:24.720> it<00:16:24.839> looks<00:16:25.040> more<00:16:25.319> like<00:16:25.880> uh 00:16:25.990 --> 00:16:26.000 align:start position:0% control then it's it looks more like uh 00:16:26.000 --> 00:16:27.509 align:start position:0% control then it's it looks more like uh web<00:16:26.199> 2<00:16:26.480> security<00:16:26.920> where<00:16:27.120> you<00:16:27.240> have<00:16:27.399> your 00:16:27.509 --> 00:16:27.519 align:start position:0% web 2 security where you have your 00:16:27.519 --> 00:16:30.870 align:start position:0% web 2 security where you have your servers<00:16:28.000> and<00:16:28.319> your<00:16:28.680> D<00:16:28.920> DNS<00:16:29.360> and<00:16:29.920> you<00:16:30.040> know<00:16:30.199> TLS 00:16:30.870 --> 00:16:30.880 align:start position:0% servers and your D DNS and you know TLS 00:16:30.880 --> 00:16:33.509 align:start position:0% servers and your D DNS and you know TLS all<00:16:31.040> that<00:16:31.319> that<00:16:31.440> kind<00:16:31.560> of<00:16:31.680> stuff<00:16:32.240> so<00:16:33.160> you<00:16:33.319> do 00:16:33.509 --> 00:16:33.519 align:start position:0% all that that kind of stuff so you do 00:16:33.519 --> 00:16:36.309 align:start position:0% all that that kind of stuff so you do have<00:16:33.720> different<00:16:34.000> kind<00:16:34.120> of<00:16:34.279> areas<00:16:34.680> and<00:16:35.040> and<00:16:36.040> we 00:16:36.309 --> 00:16:36.319 align:start position:0% have different kind of areas and and we 00:16:36.319 --> 00:16:38.230 align:start position:0% have different kind of areas and and we have<00:16:36.519> different<00:16:36.800> ways<00:16:37.120> of<00:16:37.360> of<00:16:37.639> solving<00:16:38.040> these 00:16:38.230 --> 00:16:38.240 align:start position:0% have different ways of of solving these 00:16:38.240 --> 00:16:39.710 align:start position:0% have different ways of of solving these problems<00:16:38.560> that<00:16:38.680> are<00:16:38.839> more<00:16:39.199> specific<00:16:39.519> to 00:16:39.710 --> 00:16:39.720 align:start position:0% problems that are more specific to 00:16:39.720 --> 00:16:42.990 align:start position:0% problems that are more specific to either<00:16:39.959> ethereum<00:16:40.360> protocol<00:16:41.279> or<00:16:41.680> um<00:16:42.319> basic<00:16:42.880> you 00:16:42.990 --> 00:16:43.000 align:start position:0% either ethereum protocol or um basic you 00:16:43.000 --> 00:16:44.990 align:start position:0% either ethereum protocol or um basic you know<00:16:43.240> Services<00:16:43.920> hosted 00:16:44.990 --> 00:16:45.000 align:start position:0% know Services hosted 00:16:45.000 --> 00:16:47.069 align:start position:0% know Services hosted Services<00:16:46.000> gotcha<00:16:46.480> I<00:16:46.560> have<00:16:46.680> a<00:16:46.759> lot<00:16:46.880> more 00:16:47.069 --> 00:16:47.079 align:start position:0% Services gotcha I have a lot more 00:16:47.079 --> 00:16:50.670 align:start position:0% Services gotcha I have a lot more questions<00:16:47.519> for<00:16:47.720> offline<00:16:48.360> but<00:16:48.880> uh<00:16:49.519> any<00:16:49.720> other 00:16:50.670 --> 00:16:50.680 align:start position:0% questions for offline but uh any other 00:16:50.680 --> 00:16:52.870 align:start position:0% questions for offline but uh any other questions<00:16:51.160> since<00:16:51.480> then<00:16:51.839> okay<00:16:52.360> I'll<00:16:52.519> go<00:16:52.680> for 00:16:52.870 --> 00:16:52.880 align:start position:0% questions since then okay I'll go for 00:16:52.880 --> 00:16:55.550 align:start position:0% questions since then okay I'll go for the<00:16:53.040> first<00:16:53.199> one<00:16:53.480> here<00:16:53.800> so<00:16:54.319> how<00:16:54.440> are<00:16:54.680> you<00:16:55.040> in<00:16:55.240> the 00:16:55.550 --> 00:16:55.560 align:start position:0% the first one here so how are you in the 00:16:55.560 --> 00:16:59.069 align:start position:0% the first one here so how are you in the super<00:16:55.959> chain<00:16:56.399> with<00:16:56.519> a<00:16:56.680> custom<00:16:57.360> da<00:16:58.360> I<00:16:58.440> mean<00:16:58.959> the 00:16:59.069 --> 00:16:59.079 align:start position:0% super chain with a custom da I mean the 00:16:59.079 --> 00:17:02.749 align:start position:0% super chain with a custom da I mean the differ<00:17:00.079> we're<00:17:00.319> not<00:17:00.680> in<00:17:01.240> the<00:17:01.360> interrupt<00:17:01.959> Set<00:17:02.560> uh 00:17:02.749 --> 00:17:02.759 align:start position:0% differ we're not in the interrupt Set uh 00:17:02.759 --> 00:17:06.470 align:start position:0% differ we're not in the interrupt Set uh just<00:17:03.199> yet<00:17:03.480> so<00:17:04.319> I<00:17:04.439> guess<00:17:04.679> this<00:17:04.919> would<00:17:05.120> be<00:17:05.559> um<00:17:06.120> the 00:17:06.470 --> 00:17:06.480 align:start position:0% just yet so I guess this would be um the 00:17:06.480 --> 00:17:08.990 align:start position:0% just yet so I guess this would be um the kind<00:17:06.640> of<00:17:06.880> slight<00:17:07.520> differentiation<00:17:08.520> um<00:17:08.839> but 00:17:08.990 --> 00:17:09.000 align:start position:0% kind of slight differentiation um but 00:17:09.000 --> 00:17:11.029 align:start position:0% kind of slight differentiation um but we're<00:17:09.240> still<00:17:09.559> kind<00:17:09.679> of<00:17:09.919> so<00:17:10.240> we're<00:17:10.400> not<00:17:10.640> part<00:17:10.799> of 00:17:11.029 --> 00:17:11.039 align:start position:0% we're still kind of so we're not part of 00:17:11.039 --> 00:17:14.029 align:start position:0% we're still kind of so we're not part of the<00:17:12.000> um<00:17:12.520> upgrade<00:17:13.000> set<00:17:13.240> so<00:17:13.360> we<00:17:13.480> don't<00:17:13.679> get<00:17:13.880> the 00:17:14.029 --> 00:17:14.039 align:start position:0% the um upgrade set so we don't get the 00:17:14.039 --> 00:17:16.789 align:start position:0% the um upgrade set so we don't get the RO<00:17:14.439> the<00:17:14.600> basic<00:17:14.959> rollup<00:17:15.520> upgrades<00:17:16.520> uh<00:17:16.679> but 00:17:16.789 --> 00:17:16.799 align:start position:0% RO the basic rollup upgrades uh but 00:17:16.799 --> 00:17:19.029 align:start position:0% RO the basic rollup upgrades uh but we're<00:17:17.319> in<00:17:17.439> the<00:17:17.760> super<00:17:18.120> chain<00:17:18.439> per<00:17:18.600> se<00:17:18.839> because 00:17:19.029 --> 00:17:19.039 align:start position:0% we're in the super chain per se because 00:17:19.039 --> 00:17:21.270 align:start position:0% we're in the super chain per se because we're<00:17:19.439> actually<00:17:19.640> using<00:17:19.959> the<00:17:20.120> Upstream<00:17:21.120> uh 00:17:21.270 --> 00:17:21.280 align:start position:0% we're actually using the Upstream uh 00:17:21.280 --> 00:17:22.590 align:start position:0% we're actually using the Upstream uh protocol<00:17:21.720> version<00:17:21.959> of<00:17:22.039> the<00:17:22.160> protocol<00:17:22.480> we're 00:17:22.590 --> 00:17:22.600 align:start position:0% protocol version of the protocol we're 00:17:22.600 --> 00:17:25.710 align:start position:0% protocol version of the protocol we're not<00:17:22.679> running<00:17:22.959> a<00:17:23.120> fork<00:17:24.120> um<00:17:24.919> and<00:17:25.039> so<00:17:25.400> all<00:17:25.600> the 00:17:25.710 --> 00:17:25.720 align:start position:0% not running a fork um and so all the 00:17:25.720 --> 00:17:28.230 align:start position:0% not running a fork um and so all the code<00:17:26.000> that<00:17:26.120> we<00:17:26.240> run<00:17:26.520> is<00:17:27.000> basically<00:17:28.000> um 00:17:28.230 --> 00:17:28.240 align:start position:0% code that we run is basically um 00:17:28.240 --> 00:17:29.390 align:start position:0% code that we run is basically um reviewed<00:17:28.640> by 00:17:29.390 --> 00:17:29.400 align:start position:0% reviewed by 00:17:29.400 --> 00:17:32.390 align:start position:0% reviewed by op<00:17:29.799> stack<00:17:30.320> core 00:17:32.390 --> 00:17:32.400 align:start position:0% op stack core 00:17:32.400 --> 00:17:34.549 align:start position:0% op stack core protocols<00:17:33.400> what's<00:17:33.679> next<00:17:33.919> on<00:17:34.039> the<00:17:34.160> road<00:17:34.400> map 00:17:34.549 --> 00:17:34.559 align:start position:0% protocols what's next on the road map 00:17:34.559 --> 00:17:37.310 align:start position:0% protocols what's next on the road map for<00:17:34.720> mud<00:17:35.000> what<00:17:35.160> features<00:17:35.960> are<00:17:36.200> most<00:17:36.440> needed 00:17:37.310 --> 00:17:37.320 align:start position:0% for mud what features are most needed 00:17:37.320 --> 00:17:39.950 align:start position:0% for mud what features are most needed next<00:17:38.320> I<00:17:38.400> mean<00:17:38.880> I<00:17:38.960> can<00:17:39.120> speak<00:17:39.400> for<00:17:39.640> the 00:17:39.950 --> 00:17:39.960 align:start position:0% next I mean I can speak for the 00:17:39.960 --> 00:17:43.870 align:start position:0% next I mean I can speak for the infrastructure<00:17:40.760> part<00:17:41.120> of<00:17:41.320> things<00:17:42.520> um<00:17:43.520> yeah 00:17:43.870 --> 00:17:43.880 align:start position:0% infrastructure part of things um yeah 00:17:43.880 --> 00:17:45.470 align:start position:0% infrastructure part of things um yeah what<00:17:43.960> we're<00:17:44.120> really<00:17:44.320> trying<00:17:44.520> to<00:17:44.679> do<00:17:45.000> here<00:17:45.200> is 00:17:45.470 --> 00:17:45.480 align:start position:0% what we're really trying to do here is 00:17:45.480 --> 00:17:47.430 align:start position:0% what we're really trying to do here is is<00:17:45.799> get<00:17:45.960> to<00:17:46.160> this<00:17:46.400> extremely<00:17:46.840> extremely<00:17:47.200> low 00:17:47.430 --> 00:17:47.440 align:start position:0% is get to this extremely extremely low 00:17:47.440 --> 00:17:49.909 align:start position:0% is get to this extremely extremely low latency<00:17:47.880> and<00:17:48.039> get<00:17:48.200> those<00:17:48.679> uh<00:17:48.760> on<00:17:48.880> Main<00:17:49.160> Nets<00:17:49.679> so 00:17:49.909 --> 00:17:49.919 align:start position:0% latency and get those uh on Main Nets so 00:17:49.919 --> 00:17:51.669 align:start position:0% latency and get those uh on Main Nets so we're<00:17:50.080> trying<00:17:50.320> to<00:17:50.520> get<00:17:51.039> you<00:17:51.160> know<00:17:51.360> the<00:17:51.480> new 00:17:51.669 --> 00:17:51.679 align:start position:0% we're trying to get you know the new 00:17:51.679 --> 00:17:53.310 align:start position:0% we're trying to get you know the new indexing<00:17:52.320> we're<00:17:52.480> trying<00:17:52.679> to<00:17:52.799> get<00:17:52.960> all<00:17:53.120> these 00:17:53.310 --> 00:17:53.320 align:start position:0% indexing we're trying to get all these 00:17:53.320 --> 00:17:56.590 align:start position:0% indexing we're trying to get all these things<00:17:53.880> available<00:17:54.640> um<00:17:54.799> on<00:17:54.960> Redstone<00:17:55.600> mainnet 00:17:56.590 --> 00:17:56.600 align:start position:0% things available um on Redstone mainnet 00:17:56.600 --> 00:17:58.909 align:start position:0% things available um on Redstone mainnet um<00:17:56.919> and<00:17:57.039> then<00:17:57.400> probably<00:17:57.760> the<00:17:57.880> next<00:17:58.120> thing<00:17:58.360> that 00:17:58.909 --> 00:17:58.919 align:start position:0% um and then probably the next thing that 00:17:58.919 --> 00:18:01.990 align:start position:0% um and then probably the next thing that we<00:17:59.400> probably<00:17:59.679> will<00:17:59.799> be<00:17:59.960> working<00:18:00.240> on<00:18:00.480> is<00:18:01.120> um<00:18:01.840> you 00:18:01.990 --> 00:18:02.000 align:start position:0% we probably will be working on is um you 00:18:02.000 --> 00:18:04.870 align:start position:0% we probably will be working on is um you know<00:18:02.280> integrating<00:18:02.840> interrupt<00:18:03.440> so<00:18:03.880> optimism's 00:18:04.870 --> 00:18:04.880 align:start position:0% know integrating interrupt so optimism's 00:18:04.880 --> 00:18:07.789 align:start position:0% know integrating interrupt so optimism's uh<00:18:05.039> multi-chain<00:18:05.679> protocol<00:18:06.400> inside<00:18:06.720> of<00:18:06.880> mud<00:18:07.200> so 00:18:07.789 --> 00:18:07.799 align:start position:0% uh multi-chain protocol inside of mud so 00:18:07.799 --> 00:18:10.110 align:start position:0% uh multi-chain protocol inside of mud so we'll<00:18:08.039> also<00:18:08.360> have<00:18:08.760> some<00:18:09.159> uh<00:18:09.440> exciting<00:18:09.840> things 00:18:10.110 --> 00:18:10.120 align:start position:0% we'll also have some uh exciting things 00:18:10.120 --> 00:18:11.950 align:start position:0% we'll also have some uh exciting things like<00:18:10.320> this<00:18:10.559> but<00:18:10.760> this<00:18:10.880> is<00:18:11.000> still<00:18:11.200> work<00:18:11.440> in 00:18:11.950 --> 00:18:11.960 align:start position:0% like this but this is still work in 00:18:11.960 --> 00:18:14.590 align:start position:0% like this but this is still work in progress<00:18:12.960> gotcha<00:18:13.600> yeah<00:18:13.840> that<00:18:14.039> that<00:18:14.200> speaks<00:18:14.480> to 00:18:14.590 --> 00:18:14.600 align:start position:0% progress gotcha yeah that that speaks to 00:18:14.600 --> 00:18:16.029 align:start position:0% progress gotcha yeah that that speaks to my<00:18:14.799> question<00:18:15.000> of<00:18:15.159> why<00:18:15.280> you<00:18:15.400> joined<00:18:15.679> the<00:18:15.760> super 00:18:16.029 --> 00:18:16.039 align:start position:0% my question of why you joined the super 00:18:16.039 --> 00:18:18.710 align:start position:0% my question of why you joined the super chain<00:18:17.000> um<00:18:17.400> how<00:18:17.480> do<00:18:17.600> you<00:18:17.799> balance<00:18:18.200> the<00:18:18.320> benefits 00:18:18.710 --> 00:18:18.720 align:start position:0% chain um how do you balance the benefits 00:18:18.720 --> 00:18:21.510 align:start position:0% chain um how do you balance the benefits of<00:18:19.159> scaling<00:18:20.159> um<00:18:20.760> and<00:18:20.880> the<00:18:21.000> latency 00:18:21.510 --> 00:18:21.520 align:start position:0% of scaling um and the latency 00:18:21.520 --> 00:18:25.110 align:start position:0% of scaling um and the latency optimization<00:18:22.480> against<00:18:23.159> the<00:18:23.360> dollar<00:18:24.120> cost 00:18:25.110 --> 00:18:25.120 align:start position:0% optimization against the dollar cost 00:18:25.120 --> 00:18:27.510 align:start position:0% optimization against the dollar cost yeah<00:18:25.440> that<00:18:25.600> that's<00:18:25.720> a<00:18:25.880> good<00:18:26.080> question<00:18:26.760> um<00:18:27.480> I 00:18:27.510 --> 00:18:27.520 align:start position:0% yeah that that's a good question um I 00:18:27.520 --> 00:18:28.830 align:start position:0% yeah that that's a good question um I mean<00:18:27.679> one<00:18:27.840> thing<00:18:27.960> we've<00:18:28.120> been<00:18:28.240> trying<00:18:28.400> to<00:18:28.520> do 00:18:28.830 --> 00:18:28.840 align:start position:0% mean one thing we've been trying to do 00:18:28.840 --> 00:18:31.270 align:start position:0% mean one thing we've been trying to do is<00:18:29.000> like<00:18:29.240> move<00:18:29.600> towards<00:18:29.919> a<00:18:30.159> more<00:18:30.799> like<00:18:31.000> bare 00:18:31.270 --> 00:18:31.280 align:start position:0% is like move towards a more like bare 00:18:31.280 --> 00:18:33.270 align:start position:0% is like move towards a more like bare metal<00:18:31.679> server<00:18:32.159> architecture<00:18:32.760> so<00:18:32.919> instead<00:18:33.159> of 00:18:33.270 --> 00:18:33.280 align:start position:0% metal server architecture so instead of 00:18:33.280 --> 00:18:35.830 align:start position:0% metal server architecture so instead of using<00:18:33.720> AWS<00:18:34.320> as<00:18:34.559> very<00:18:34.840> expensive<00:18:35.320> servers 00:18:35.830 --> 00:18:35.840 align:start position:0% using AWS as very expensive servers 00:18:35.840 --> 00:18:38.190 align:start position:0% using AWS as very expensive servers we're<00:18:36.039> trying<00:18:36.280> to<00:18:36.880> run<00:18:37.240> things<00:18:37.880> uh<00:18:37.960> on 00:18:38.190 --> 00:18:38.200 align:start position:0% we're trying to run things uh on 00:18:38.200 --> 00:18:39.710 align:start position:0% we're trying to run things uh on different<00:18:38.480> bare<00:18:38.720> metal<00:18:39.039> providers<00:18:39.440> that<00:18:39.559> are 00:18:39.710 --> 00:18:39.720 align:start position:0% different bare metal providers that are 00:18:39.720 --> 00:18:42.430 align:start position:0% different bare metal providers that are like<00:18:39.919> cheaper<00:18:40.840> and<00:18:41.080> have<00:18:41.240> a<00:18:41.360> lot<00:18:41.480> of<00:18:41.799> you<00:18:41.880> know 00:18:42.430 --> 00:18:42.440 align:start position:0% like cheaper and have a lot of you know 00:18:42.440 --> 00:18:44.830 align:start position:0% like cheaper and have a lot of you know redundancy<00:18:43.440> uh<00:18:43.799> because<00:18:44.280> they're<00:18:44.480> obviously 00:18:44.830 --> 00:18:44.840 align:start position:0% redundancy uh because they're obviously 00:18:44.840 --> 00:18:47.750 align:start position:0% redundancy uh because they're obviously less<00:18:45.080> stable<00:18:45.480> so<00:18:45.679> that<00:18:46.480> uh<00:18:46.600> essentially<00:18:47.200> if<00:18:47.320> a 00:18:47.750 --> 00:18:47.760 align:start position:0% less stable so that uh essentially if a 00:18:47.760 --> 00:18:50.270 align:start position:0% less stable so that uh essentially if a region<00:18:48.120> goes<00:18:48.360> down<00:18:48.720> or<00:18:49.480> um<00:18:49.640> a<00:18:49.760> server<00:18:50.080> goes 00:18:50.270 --> 00:18:50.280 align:start position:0% region goes down or um a server goes 00:18:50.280 --> 00:18:53.230 align:start position:0% region goes down or um a server goes down<00:18:50.880> if<00:18:51.000> it's<00:18:51.120> not<00:18:51.360> as<00:18:51.799> as<00:18:51.919> stable<00:18:52.200> as<00:18:52.320> AWS 00:18:53.230 --> 00:18:53.240 align:start position:0% down if it's not as as stable as AWS 00:18:53.240 --> 00:18:55.590 align:start position:0% down if it's not as as stable as AWS it's<00:18:53.600> the<00:18:53.720> users<00:18:54.120> don't<00:18:54.400> don't<00:18:54.640> really<00:18:55.320> uh<00:18:55.400> see 00:18:55.590 --> 00:18:55.600 align:start position:0% it's the users don't don't really uh see 00:18:55.600 --> 00:18:58.190 align:start position:0% it's the users don't don't really uh see the<00:18:55.799> difference<00:18:56.559> and<00:18:56.679> then<00:18:56.799> you<00:18:56.960> know<00:18:57.919> basic 00:18:58.190 --> 00:18:58.200 align:start position:0% the difference and then you know basic 00:18:58.200 --> 00:19:00.230 align:start position:0% the difference and then you know basic stuff<00:18:58.440> like<00:18:58.960> packing<00:18:59.480> just<00:18:59.640> adding<00:18:59.919> a<00:19:00.039> bunch 00:19:00.230 --> 00:19:00.240 align:start position:0% stuff like packing just adding a bunch 00:19:00.240 --> 00:19:02.789 align:start position:0% stuff like packing just adding a bunch of<00:19:00.600> services<00:19:01.080> run<00:19:01.240> on<00:19:01.360> the<00:19:01.480> same<00:19:01.679> machine<00:19:02.159> so 00:19:02.789 --> 00:19:02.799 align:start position:0% of services run on the same machine so 00:19:02.799 --> 00:19:04.070 align:start position:0% of services run on the same machine so you<00:19:02.960> have<00:19:03.080> all<00:19:03.200> these<00:19:03.400> optimizations<00:19:04.000> that 00:19:04.070 --> 00:19:04.080 align:start position:0% you have all these optimizations that 00:19:04.080 --> 00:19:06.830 align:start position:0% you have all these optimizations that you<00:19:04.159> can<00:19:04.360> do<00:19:05.039> but<00:19:05.280> yeah<00:19:05.640> we're<00:19:05.840> we're<00:19:06.039> still 00:19:06.830 --> 00:19:06.840 align:start position:0% you can do but yeah we're we're still 00:19:06.840 --> 00:19:08.549 align:start position:0% you can do but yeah we're we're still fine-tuning<00:19:07.520> this<00:19:07.679> part 00:19:08.549 --> 00:19:08.559 align:start position:0% fine-tuning this part 00:19:08.559 --> 00:19:10.710 align:start position:0% fine-tuning this part actually<00:19:09.559> okay<00:19:09.720> we<00:19:09.840> got<00:19:09.960> a<00:19:10.159> question<00:19:10.480> that's 00:19:10.710 --> 00:19:10.720 align:start position:0% actually okay we got a question that's 00:19:10.720 --> 00:19:14.149 align:start position:0% actually okay we got a question that's really<00:19:11.080> popular<00:19:11.559> can<00:19:11.679> it<00:19:11.840> run<00:19:12.320> Doom<00:19:13.320> o<00:19:13.960> h 00:19:14.149 --> 00:19:14.159 align:start position:0% really popular can it run Doom o h 00:19:14.159 --> 00:19:16.070 align:start position:0% really popular can it run Doom o h that's<00:19:14.320> actually<00:19:14.520> a<00:19:14.640> really<00:19:14.919> good<00:19:15.120> question<00:19:15.520> I 00:19:16.070 --> 00:19:16.080 align:start position:0% that's actually a really good question I 00:19:16.080 --> 00:19:18.549 align:start position:0% that's actually a really good question I I<00:19:17.080> I<00:19:17.200> think<00:19:17.400> you<00:19:17.480> should<00:19:17.720> come<00:19:17.840> to<00:19:18.000> Mud<00:19:18.240> day<00:19:18.440> to 00:19:18.549 --> 00:19:18.559 align:start position:0% I I think you should come to Mud day to 00:19:18.559 --> 00:19:22.950 align:start position:0% I I think you should come to Mud day to find<00:19:18.720> out<00:19:18.919> about<00:19:19.440> that<00:19:20.440> can<00:19:20.640> wow<00:19:20.919> be 00:19:22.950 --> 00:19:22.960 align:start position:0% find out about that can wow be 00:19:22.960 --> 00:19:25.070 align:start position:0% find out about that can wow be next<00:19:23.960> next<00:19:24.240> question<00:19:24.480> by<00:19:24.600> the<00:19:24.679> way<00:19:24.799> that<00:19:24.880> was<00:19:24.960> a 00:19:25.070 --> 00:19:25.080 align:start position:0% next next question by the way that was a 00:19:25.080 --> 00:19:27.470 align:start position:0% next next question by the way that was a joke<00:19:25.280> you<00:19:25.400> didn't<00:19:25.559> have<00:19:25.679> to<00:19:25.840> laugh<00:19:26.600> um<00:19:27.280> what's 00:19:27.470 --> 00:19:27.480 align:start position:0% joke you didn't have to laugh um what's 00:19:27.480 --> 00:19:29.390 align:start position:0% joke you didn't have to laugh um what's your<00:19:27.799> thought<00:19:28.120> on 00:19:29.390 --> 00:19:29.400 align:start position:0% your thought on 00:19:29.400 --> 00:19:32.549 align:start position:0% your thought on crdt<00:19:30.400> in<00:19:30.600> crdt<00:19:31.400> plus<00:19:31.640> blockchain<00:19:32.159> I'm<00:19:32.280> sorry 00:19:32.549 --> 00:19:32.559 align:start position:0% crdt in crdt plus blockchain I'm sorry 00:19:32.559 --> 00:19:34.590 align:start position:0% crdt in crdt plus blockchain I'm sorry I'm<00:19:32.679> not<00:19:32.799> the<00:19:32.960> person<00:19:33.159> to<00:19:33.240> be<00:19:33.760> asking<00:19:34.080> that 00:19:34.590 --> 00:19:34.600 align:start position:0% I'm not the person to be asking that 00:19:34.600 --> 00:19:36.430 align:start position:0% I'm not the person to be asking that question<00:19:35.600> I<00:19:35.679> think<00:19:35.840> it's<00:19:36.200> it's<00:19:36.320> an 00:19:36.430 --> 00:19:36.440 align:start position:0% question I think it's it's an 00:19:36.440 --> 00:19:38.190 align:start position:0% question I think it's it's an interesting<00:19:36.840> question<00:19:37.159> because<00:19:37.600> it's<00:19:37.760> like 00:19:38.190 --> 00:19:38.200 align:start position:0% interesting question because it's like 00:19:38.200 --> 00:19:40.510 align:start position:0% interesting question because it's like crdt<00:19:38.880> use<00:19:39.080> if<00:19:39.200> you<00:19:39.400> really<00:19:39.600> want<00:19:39.799> to<00:19:39.960> do<00:19:40.200> like 00:19:40.510 --> 00:19:40.520 align:start position:0% crdt use if you really want to do like 00:19:40.520 --> 00:19:43.950 align:start position:0% crdt use if you really want to do like pure<00:19:41.080> decentralization<00:19:42.080> and<00:19:42.880> um<00:19:43.440> you<00:19:43.679> care 00:19:43.950 --> 00:19:43.960 align:start position:0% pure decentralization and um you care 00:19:43.960 --> 00:19:46.430 align:start position:0% pure decentralization and um you care about<00:19:44.840> you<00:19:44.960> know<00:19:45.320> not<00:19:45.559> having<00:19:45.799> a<00:19:45.919> single<00:19:46.200> point 00:19:46.430 --> 00:19:46.440 align:start position:0% about you know not having a single point 00:19:46.440 --> 00:19:48.230 align:start position:0% about you know not having a single point of<00:19:46.600> failure<00:19:47.080> and<00:19:47.360> having<00:19:47.679> you<00:19:47.799> know<00:19:47.960> all<00:19:48.120> the 00:19:48.230 --> 00:19:48.240 align:start position:0% of failure and having you know all the 00:19:48.240 --> 00:19:50.549 align:start position:0% of failure and having you know all the browsers<00:19:48.760> be<00:19:48.919> able<00:19:49.080> to<00:19:49.280> eventually<00:19:49.960> reconcile 00:19:50.549 --> 00:19:50.559 align:start position:0% browsers be able to eventually reconcile 00:19:50.559 --> 00:19:52.510 align:start position:0% browsers be able to eventually reconcile the<00:19:50.720> state<00:19:51.000> and<00:19:51.120> things<00:19:51.320> like<00:19:51.520> that<00:19:52.000> so<00:19:52.320> I<00:19:52.440> I 00:19:52.510 --> 00:19:52.520 align:start position:0% the state and things like that so I I 00:19:52.520 --> 00:19:53.909 align:start position:0% the state and things like that so I I guess<00:19:52.679> it<00:19:52.760> would<00:19:52.960> really<00:19:53.159> depend<00:19:53.480> on<00:19:53.760> what 00:19:53.909 --> 00:19:53.919 align:start position:0% guess it would really depend on what 00:19:53.919 --> 00:19:56.669 align:start position:0% guess it would really depend on what your<00:19:54.520> um<00:19:54.679> use<00:19:55.039> case<00:19:55.240> requirements<00:19:55.760> are<00:19:56.280> um<00:19:56.559> if 00:19:56.669 --> 00:19:56.679 align:start position:0% your um use case requirements are um if 00:19:56.679 --> 00:19:58.870 align:start position:0% your um use case requirements are um if you're<00:19:56.919> trying<00:19:57.120> to<00:19:57.240> build<00:19:57.440> a<00:19:57.640> game<00:19:58.159> that<00:19:58.280> is 00:19:58.870 --> 00:19:58.880 align:start position:0% you're trying to build a game that is 00:19:58.880 --> 00:20:01.549 align:start position:0% you're trying to build a game that is even<00:19:59.159> if<00:19:59.760> all<00:20:00.039> the<00:20:00.280> latest<00:20:00.679> servers<00:20:01.039> go<00:20:01.280> down 00:20:01.549 --> 00:20:01.559 align:start position:0% even if all the latest servers go down 00:20:01.559 --> 00:20:03.870 align:start position:0% even if all the latest servers go down you<00:20:01.720> can<00:20:01.880> still<00:20:02.120> play<00:20:02.280> the<00:20:02.440> game<00:20:03.120> then<00:20:03.320> crdt 00:20:03.870 --> 00:20:03.880 align:start position:0% you can still play the game then crdt 00:20:03.880 --> 00:20:05.750 align:start position:0% you can still play the game then crdt could<00:20:04.039> actually<00:20:04.200> be<00:20:04.400> a<00:20:04.960> pretty<00:20:05.320> pretty<00:20:05.520> good 00:20:05.750 --> 00:20:05.760 align:start position:0% could actually be a pretty pretty good 00:20:05.760 --> 00:20:08.270 align:start position:0% could actually be a pretty pretty good solution<00:20:06.760> but<00:20:07.039> otherwise<00:20:07.559> I'm<00:20:07.640> not<00:20:08.000> fully 00:20:08.270 --> 00:20:08.280 align:start position:0% solution but otherwise I'm not fully 00:20:08.280 --> 00:20:09.789 align:start position:0% solution but otherwise I'm not fully certain<00:20:08.600> that<00:20:08.720> you<00:20:08.799> can<00:20:08.960> get<00:20:09.200> the<00:20:09.360> the<00:20:09.600> same 00:20:09.789 --> 00:20:09.799 align:start position:0% certain that you can get the the same 00:20:09.799 --> 00:20:11.270 align:start position:0% certain that you can get the the same kind<00:20:09.919> of<00:20:10.080> performance<00:20:10.520> and<00:20:10.640> latency<00:20:11.120> that 00:20:11.270 --> 00:20:11.280 align:start position:0% kind of performance and latency that 00:20:11.280 --> 00:20:12.750 align:start position:0% kind of performance and latency that that<00:20:11.400> we<00:20:11.600> have<00:20:11.799> when<00:20:11.960> we<00:20:12.120> have<00:20:12.280> these<00:20:12.440> Edge 00:20:12.750 --> 00:20:12.760 align:start position:0% that we have when we have these Edge 00:20:12.760 --> 00:20:15.190 align:start position:0% that we have when we have these Edge block 00:20:15.190 --> 00:20:15.200 align:start position:0% 00:20:15.200 --> 00:20:18.710 align:start position:0% Builders<00:20:16.200> cool<00:20:16.480> any<00:20:16.640> other<00:20:16.840> question 00:20:18.710 --> 00:20:18.720 align:start position:0% Builders cool any other question 00:20:18.720 --> 00:20:22.310 align:start position:0% Builders cool any other question guys<00:20:19.720> I<00:20:19.840> got<00:20:20.000> one<00:20:20.200> spicy<00:20:20.679> question<00:20:21.039> here<00:20:21.919> oh 00:20:22.310 --> 00:20:22.320 align:start position:0% guys I got one spicy question here oh 00:20:22.320 --> 00:20:23.950 align:start position:0% guys I got one spicy question here oh nope<00:20:22.880> someone<00:20:23.080> else<00:20:23.280> has<00:20:23.440> another<00:20:23.760> question 00:20:23.950 --> 00:20:23.960 align:start position:0% nope someone else has another question 00:20:23.960 --> 00:20:27.190 align:start position:0% nope someone else has another question in<00:20:24.159> here<00:20:25.039> um<00:20:25.960> this<00:20:26.039> is<00:20:26.200> not<00:20:26.320> a<00:20:26.400> question<00:20:26.640> crdt 00:20:27.190 --> 00:20:27.200 align:start position:0% in here um this is not a question crdt 00:20:27.200 --> 00:20:30.110 align:start position:0% in here um this is not a question crdt is<00:20:27.559> yeah<00:20:27.720> someone<00:20:28.000> has<00:20:28.080> a<00:20:28.200> point<00:20:28.400> here<00:20:29.120> make 00:20:30.110 --> 00:20:30.120 align:start position:0% is yeah someone has a point here make 00:20:30.120 --> 00:20:32.190 align:start position:0% is yeah someone has a point here make what<00:20:30.200> is<00:20:30.320> your<00:20:30.480> take<00:20:30.679> on<00:20:30.840> that<00:20:31.039> crdt<00:20:31.640> is<00:20:31.840> only 00:20:32.190 --> 00:20:32.200 align:start position:0% what is your take on that crdt is only 00:20:32.200 --> 00:20:35.950 align:start position:0% what is your take on that crdt is only for<00:20:32.559> communitive<00:20:33.440> operations<00:20:34.360> bad<00:20:34.760> for<00:20:35.039> games 00:20:35.950 --> 00:20:35.960 align:start position:0% for communitive operations bad for games 00:20:35.960 --> 00:20:38.230 align:start position:0% for communitive operations bad for games thank<00:20:36.159> you<00:20:36.360> for<00:20:36.520> that<00:20:36.679> spicy<00:20:37.120> question<00:20:38.000> or 00:20:38.230 --> 00:20:38.240 align:start position:0% thank you for that spicy question or 00:20:38.240 --> 00:20:40.270 align:start position:0% thank you for that spicy question or opinion 00:20:40.270 --> 00:20:40.280 align:start position:0% opinion 00:20:40.280 --> 00:20:43.149 align:start position:0% opinion rather<00:20:41.280> what<00:20:41.400> was<00:20:41.559> the<00:20:41.720> other<00:20:42.320> take<00:20:42.559> you<00:20:42.760> had 00:20:43.149 --> 00:20:43.159 align:start position:0% rather what was the other take you had 00:20:43.159 --> 00:20:45.590 align:start position:0% rather what was the other take you had oh<00:20:43.320> the<00:20:43.440> other<00:20:43.640> take<00:20:43.919> I<00:20:44.080> had<00:20:44.480> uh<00:20:44.799> was<00:20:45.360> I'm 00:20:45.590 --> 00:20:45.600 align:start position:0% oh the other take I had uh was I'm 00:20:45.600 --> 00:20:47.430 align:start position:0% oh the other take I had uh was I'm curious<00:20:46.120> how<00:20:46.400> you<00:20:46.679> actually<00:20:46.919> see<00:20:47.240> the 00:20:47.430 --> 00:20:47.440 align:start position:0% curious how you actually see the 00:20:47.440 --> 00:20:50.350 align:start position:0% curious how you actually see the difference<00:20:47.919> between<00:20:48.919> um<00:20:49.159> ton<00:20:49.559> chain<00:20:49.960> and<00:20:50.200> all 00:20:50.350 --> 00:20:50.360 align:start position:0% difference between um ton chain and all 00:20:50.360 --> 00:20:52.510 align:start position:0% difference between um ton chain and all of<00:20:50.559> their<00:20:50.919> you<00:20:51.039> know<00:20:51.240> fun<00:20:51.559> mobile<00:20:51.880> app<00:20:52.120> games<00:20:52.440> I 00:20:52.510 --> 00:20:52.520 align:start position:0% of their you know fun mobile app games I 00:20:52.520 --> 00:20:53.710 align:start position:0% of their you know fun mobile app games I don't<00:20:52.679> know<00:20:52.799> if<00:20:52.880> you<00:20:53.000> guys<00:20:53.120> have<00:20:53.280> played<00:20:53.559> any 00:20:53.710 --> 00:20:53.720 align:start position:0% don't know if you guys have played any 00:20:53.720 --> 00:20:56.110 align:start position:0% don't know if you guys have played any of<00:20:53.840> them<00:20:54.039> but<00:20:54.159> they're<00:20:54.360> highly<00:20:54.760> addictive<00:20:55.760> um 00:20:56.110 --> 00:20:56.120 align:start position:0% of them but they're highly addictive um 00:20:56.120 --> 00:20:58.950 align:start position:0% of them but they're highly addictive um and<00:20:56.360> you<00:20:56.600> do<00:20:57.159> end<00:20:57.320> up<00:20:57.960> earning<00:20:58.600> whatever 00:20:58.950 --> 00:20:58.960 align:start position:0% and you do end up earning whatever 00:20:58.960 --> 00:21:01.070 align:start position:0% and you do end up earning whatever tokens<00:20:59.360> in<00:20:59.520> their<00:20:59.720> ecosystems<00:21:00.600> and<00:21:00.720> they<00:21:00.880> seem 00:21:01.070 --> 00:21:01.080 align:start position:0% tokens in their ecosystems and they seem 00:21:01.080 --> 00:21:04.070 align:start position:0% tokens in their ecosystems and they seem to<00:21:01.240> be<00:21:01.400> building<00:21:02.400> something<00:21:02.840> quite<00:21:03.120> similar 00:21:04.070 --> 00:21:04.080 align:start position:0% to be building something quite similar 00:21:04.080 --> 00:21:05.590 align:start position:0% to be building something quite similar probably<00:21:04.400> a<00:21:04.520> lot<00:21:04.720> less<00:21:04.960> complex<00:21:05.360> than<00:21:05.480> what 00:21:05.590 --> 00:21:05.600 align:start position:0% probably a lot less complex than what 00:21:05.600 --> 00:21:08.669 align:start position:0% probably a lot less complex than what you<00:21:05.760> guys<00:21:05.880> are<00:21:06.640> yeah<00:21:06.840> I<00:21:06.960> think<00:21:07.679> so<00:21:08.120> it's<00:21:08.480> quite 00:21:08.669 --> 00:21:08.679 align:start position:0% you guys are yeah I think so it's quite 00:21:08.679 --> 00:21:10.350 align:start position:0% you guys are yeah I think so it's quite interesting<00:21:09.039> too<00:21:09.280> because<00:21:10.000> what<00:21:10.159> we're 00:21:10.350 --> 00:21:10.360 align:start position:0% interesting too because what we're 00:21:10.360 --> 00:21:12.390 align:start position:0% interesting too because what we're really<00:21:10.559> focusing<00:21:11.080> here<00:21:11.240> is<00:21:11.440> like<00:21:11.840> autonomous 00:21:12.390 --> 00:21:12.400 align:start position:0% really focusing here is like autonomous 00:21:12.400 --> 00:21:14.990 align:start position:0% really focusing here is like autonomous worlds<00:21:12.760> where<00:21:13.000> you<00:21:13.159> bring<00:21:13.480> as<00:21:13.840> much<00:21:14.720> part<00:21:14.880> of 00:21:14.990 --> 00:21:15.000 align:start position:0% worlds where you bring as much part of 00:21:15.000 --> 00:21:16.269 align:start position:0% worlds where you bring as much part of the<00:21:15.200> you're<00:21:15.320> trying<00:21:15.480> to<00:21:15.600> bring<00:21:15.960> all<00:21:16.159> the 00:21:16.269 --> 00:21:16.279 align:start position:0% the you're trying to bring all the 00:21:16.279 --> 00:21:18.990 align:start position:0% the you're trying to bring all the physics<00:21:16.600> on<00:21:16.799> chain<00:21:17.320> so<00:21:17.520> it<00:21:17.640> can<00:21:17.840> live<00:21:18.200> without 00:21:18.990 --> 00:21:19.000 align:start position:0% physics on chain so it can live without 00:21:19.000 --> 00:21:21.230 align:start position:0% physics on chain so it can live without anything<00:21:19.320> on<00:21:19.480> the<00:21:19.720> client<00:21:20.720> um<00:21:20.919> and<00:21:21.039> then 00:21:21.230 --> 00:21:21.240 align:start position:0% anything on the client um and then 00:21:21.240 --> 00:21:23.750 align:start position:0% anything on the client um and then eventually<00:21:21.720> can<00:21:22.080> live<00:21:22.720> out<00:21:23.039> you<00:21:23.159> know<00:21:23.320> outlive 00:21:23.750 --> 00:21:23.760 align:start position:0% eventually can live out you know outlive 00:21:23.760 --> 00:21:25.950 align:start position:0% eventually can live out you know outlive the<00:21:23.880> teams<00:21:24.240> outlive<00:21:24.679> everything<00:21:25.360> and<00:21:25.480> so 00:21:25.950 --> 00:21:25.960 align:start position:0% the teams outlive everything and so 00:21:25.960 --> 00:21:27.110 align:start position:0% the teams outlive everything and so these<00:21:26.120> kind<00:21:26.240> of<00:21:26.360> games<00:21:26.600> that<00:21:26.720> are<00:21:26.880> kind<00:21:27.000> of 00:21:27.110 --> 00:21:27.120 align:start position:0% these kind of games that are kind of 00:21:27.120 --> 00:21:28.669 align:start position:0% these kind of games that are kind of addictive<00:21:27.559> they're<00:21:27.720> they're<00:21:27.880> not<00:21:28.039> really 00:21:28.669 --> 00:21:28.679 align:start position:0% addictive they're they're not really 00:21:28.679 --> 00:21:29.870 align:start position:0% addictive they're they're not really geared<00:21:29.000> for<00:21:29.159> this<00:21:29.320> kind<00:21:29.440> of<00:21:29.600> you<00:21:29.720> know 00:21:29.870 --> 00:21:29.880 align:start position:0% geared for this kind of you know 00:21:29.880 --> 00:21:31.669 align:start position:0% geared for this kind of you know long-term<00:21:30.440> view<00:21:30.880> or<00:21:31.039> things<00:21:31.240> like<00:21:31.400> that<00:21:31.559> you 00:21:31.669 --> 00:21:31.679 align:start position:0% long-term view or things like that you 00:21:31.679 --> 00:21:33.990 align:start position:0% long-term view or things like that you know<00:21:31.919> they<00:21:32.600> you<00:21:32.720> really<00:21:33.120> have<00:21:33.559> the<00:21:33.720> gaming 00:21:33.990 --> 00:21:34.000 align:start position:0% know they you really have the gaming 00:21:34.000 --> 00:21:35.390 align:start position:0% know they you really have the gaming Loop<00:21:34.279> that's<00:21:34.400> all<00:21:34.559> that<00:21:34.679> matters<00:21:35.159> whereas 00:21:35.390 --> 00:21:35.400 align:start position:0% Loop that's all that matters whereas 00:21:35.400 --> 00:21:36.830 align:start position:0% Loop that's all that matters whereas here<00:21:35.520> we're<00:21:35.640> trying<00:21:35.840> to<00:21:36.000> have<00:21:36.240> everything<00:21:36.640> be 00:21:36.830 --> 00:21:36.840 align:start position:0% here we're trying to have everything be 00:21:36.840 --> 00:21:38.789 align:start position:0% here we're trying to have everything be on<00:21:37.000> chain<00:21:37.320> eventually<00:21:37.720> and<00:21:37.840> that's<00:21:38.000> what<00:21:38.480> mud 00:21:38.789 --> 00:21:38.799 align:start position:0% on chain eventually and that's what mud 00:21:38.799 --> 00:21:41.190 align:start position:0% on chain eventually and that's what mud is<00:21:38.960> about<00:21:39.320> really<00:21:39.520> is<00:21:39.679> like<00:21:40.520> enabling<00:21:41.000> all 00:21:41.190 --> 00:21:41.200 align:start position:0% is about really is like enabling all 00:21:41.200 --> 00:21:44.789 align:start position:0% is about really is like enabling all these<00:21:41.400> very<00:21:41.640> complex<00:21:42.080> physics<00:21:42.760> fully<00:21:43.080> on 00:21:44.789 --> 00:21:44.799 align:start position:0% these very complex physics fully on 00:21:44.799 --> 00:21:46.990 align:start position:0% these very complex physics fully on chain<00:21:45.799> gotcha 00:21:46.990 --> 00:21:47.000 align:start position:0% chain gotcha 00:21:47.000 --> 00:21:52.200 align:start position:0% chain gotcha okay<00:21:48.000> thank<00:21:48.200> you<00:21:49.080> any<00:21:49.279> other<00:21:49.480> questions