WEBVTT Kind: captions Language: en 00:00:01.010 --> 00:00:09.110 align:start position:0% [Music] 00:00:09.110 --> 00:00:09.120 align:start position:0% [Music] 00:00:09.120 --> 00:00:12.910 align:start position:0% [Music] so<00:00:10.080> uh<00:00:10.240> cool<00:00:10.679> doors<00:00:10.920> are<00:00:11.080> being<00:00:11.559> closed<00:00:12.559> hello 00:00:12.910 --> 00:00:12.920 align:start position:0% so uh cool doors are being closed hello 00:00:12.920 --> 00:00:14.910 align:start position:0% so uh cool doors are being closed hello folks<00:00:13.440> good<00:00:13.639> afternoon<00:00:14.320> welcome<00:00:14.639> back<00:00:14.759> from 00:00:14.910 --> 00:00:14.920 align:start position:0% folks good afternoon welcome back from 00:00:14.920 --> 00:00:17.670 align:start position:0% folks good afternoon welcome back from lunch<00:00:15.840> um<00:00:16.840> I'm<00:00:17.000> Justin<00:00:17.359> one<00:00:17.480> of<00:00:17.600> the 00:00:17.670 --> 00:00:17.680 align:start position:0% lunch um I'm Justin one of the 00:00:17.680 --> 00:00:20.630 align:start position:0% lunch um I'm Justin one of the co-founder<00:00:18.039> of<00:00:18.160> ltis<00:00:19.160> um<00:00:19.480> some<00:00:19.760> people<00:00:20.320> know 00:00:20.630 --> 00:00:20.640 align:start position:0% co-founder of ltis um some people know 00:00:20.640 --> 00:00:23.390 align:start position:0% co-founder of ltis um some people know ltis<00:00:21.199> as<00:00:21.359> the<00:00:21.519> company<00:00:21.840> that<00:00:21.960> started<00:00:22.320> mud<00:00:23.199> um 00:00:23.390 --> 00:00:23.400 align:start position:0% ltis as the company that started mud um 00:00:23.400 --> 00:00:25.029 align:start position:0% ltis as the company that started mud um and<00:00:23.560> then<00:00:23.720> later<00:00:24.119> the<00:00:24.240> company<00:00:24.560> that<00:00:24.720> launched 00:00:25.029 --> 00:00:25.039 align:start position:0% and then later the company that launched 00:00:25.039 --> 00:00:26.950 align:start position:0% and then later the company that launched Redstone<00:00:25.439> chain<00:00:26.119> in<00:00:26.240> other<00:00:26.439> words<00:00:26.679> what<00:00:26.800> we've 00:00:26.950 --> 00:00:26.960 align:start position:0% Redstone chain in other words what we've 00:00:26.960 --> 00:00:28.390 align:start position:0% Redstone chain in other words what we've been<00:00:27.080> doing<00:00:27.279> is<00:00:27.400> building<00:00:27.720> infrastructure 00:00:28.390 --> 00:00:28.400 align:start position:0% been doing is building infrastructure 00:00:28.400 --> 00:00:30.790 align:start position:0% been doing is building infrastructure for<00:00:28.640> autonomous<00:00:29.119> worlds<00:00:29.720> um<00:00:30.279> but<00:00:30.560> as<00:00:30.679> you 00:00:30.790 --> 00:00:30.800 align:start position:0% for autonomous worlds um but as you 00:00:30.800 --> 00:00:32.990 align:start position:0% for autonomous worlds um but as you might<00:00:30.960> have<00:00:31.080> seen<00:00:31.359> from<00:00:31.880> alvarus<00:00:32.640> opening 00:00:32.990 --> 00:00:33.000 align:start position:0% might have seen from alvarus opening 00:00:33.000 --> 00:00:34.510 align:start position:0% might have seen from alvarus opening talk<00:00:33.280> this<00:00:33.399> morning<00:00:33.719> we<00:00:33.879> actually<00:00:34.120> started 00:00:34.510 --> 00:00:34.520 align:start position:0% talk this morning we actually started 00:00:34.520 --> 00:00:37.030 align:start position:0% talk this morning we actually started off<00:00:35.520> by<00:00:35.840> building<00:00:36.239> our<00:00:36.399> an<00:00:36.520> onchain<00:00:36.840> gain 00:00:37.030 --> 00:00:37.040 align:start position:0% off by building our an onchain gain 00:00:37.040 --> 00:00:39.670 align:start position:0% off by building our an onchain gain ourselves<00:00:37.760> about<00:00:38.079> like<00:00:38.200> two<00:00:38.360> years<00:00:38.559> ago<00:00:39.440> uh<00:00:39.559> I 00:00:39.670 --> 00:00:39.680 align:start position:0% ourselves about like two years ago uh I 00:00:39.680 --> 00:00:42.190 align:start position:0% ourselves about like two years ago uh I was<00:00:39.960> personally<00:00:40.719> fascinated<00:00:41.600> by<00:00:41.760> the<00:00:41.879> idea<00:00:42.079> of 00:00:42.190 --> 00:00:42.200 align:start position:0% was personally fascinated by the idea of 00:00:42.200 --> 00:00:43.869 align:start position:0% was personally fascinated by the idea of building<00:00:42.480> multiplayer<00:00:43.120> games<00:00:43.360> on<00:00:43.520> the<00:00:43.640> world 00:00:43.869 --> 00:00:43.879 align:start position:0% building multiplayer games on the world 00:00:43.879 --> 00:00:46.110 align:start position:0% building multiplayer games on the world computer<00:00:44.520> following<00:00:44.879> the<00:00:44.960> footsteps<00:00:45.440> of<00:00:45.640> gbep 00:00:46.110 --> 00:00:46.120 align:start position:0% computer following the footsteps of gbep 00:00:46.120 --> 00:00:48.430 align:start position:0% computer following the footsteps of gbep in<00:00:46.280> Dark<00:00:46.520> Forest<00:00:47.440> we're<00:00:47.719> super<00:00:48.000> interested<00:00:48.320> in 00:00:48.430 --> 00:00:48.440 align:start position:0% in Dark Forest we're super interested in 00:00:48.440 --> 00:00:50.110 align:start position:0% in Dark Forest we're super interested in the<00:00:48.559> IDE<00:00:48.760> of<00:00:48.879> ethereum<00:00:49.239> as<00:00:49.320> a<00:00:49.399> computer<00:00:49.800> that 00:00:50.110 --> 00:00:50.120 align:start position:0% the IDE of ethereum as a computer that 00:00:50.120 --> 00:00:52.310 align:start position:0% the IDE of ethereum as a computer that know<00:00:50.440> single<00:00:50.760> party<00:00:51.079> controls<00:00:51.920> that<00:00:52.039> allows 00:00:52.310 --> 00:00:52.320 align:start position:0% know single party controls that allows 00:00:52.320 --> 00:00:54.670 align:start position:0% know single party controls that allows immutable<00:00:52.800> physics<00:00:53.120> and<00:00:53.280> roles<00:00:53.960> that<00:00:54.079> enbl 00:00:54.670 --> 00:00:54.680 align:start position:0% immutable physics and roles that enbl 00:00:54.680 --> 00:00:56.869 align:start position:0% immutable physics and roles that enbl massive<00:00:55.160> Valuable<00:00:55.600> Player<00:00:55.879> based<00:00:56.199> economy 00:00:56.869 --> 00:00:56.879 align:start position:0% massive Valuable Player based economy 00:00:56.879 --> 00:00:58.549 align:start position:0% massive Valuable Player based economy and<00:00:57.039> has<00:00:57.160> an<00:00:57.280> open<00:00:57.520> code<00:00:57.719> based<00:00:57.920> in<00:00:58.039> API<00:00:58.440> by 00:00:58.549 --> 00:00:58.559 align:start position:0% and has an open code based in API by 00:00:58.559 --> 00:01:00.430 align:start position:0% and has an open code based in API by default<00:00:59.000> for<00:00:59.160> anyone<00:00:59.399> to<00:00:59.559> extend 00:01:00.430 --> 00:01:00.440 align:start position:0% default for anyone to extend 00:01:00.440 --> 00:01:02.389 align:start position:0% default for anyone to extend and<00:01:00.719> while<00:01:01.039> these<00:01:01.320> properties<00:01:01.719> are<00:01:02.120> pretty 00:01:02.389 --> 00:01:02.399 align:start position:0% and while these properties are pretty 00:01:02.399 --> 00:01:04.950 align:start position:0% and while these properties are pretty damn<00:01:02.719> magical<00:01:03.640> um<00:01:03.760> the<00:01:03.879> computer<00:01:04.360> also<00:01:04.600> had 00:01:04.950 --> 00:01:04.960 align:start position:0% damn magical um the computer also had 00:01:04.960 --> 00:01:07.510 align:start position:0% damn magical um the computer also had some<00:01:05.400> significant<00:01:06.000> downsides<00:01:06.920> first<00:01:07.200> it<00:01:07.360> had 00:01:07.510 --> 00:01:07.520 align:start position:0% some significant downsides first it had 00:01:07.520 --> 00:01:09.310 align:start position:0% some significant downsides first it had no<00:01:07.720> development<00:01:08.280> framework<00:01:08.920> there<00:01:09.000> is<00:01:09.119> no 00:01:09.310 --> 00:01:09.320 align:start position:0% no development framework there is no 00:01:09.320 --> 00:01:12.190 align:start position:0% no development framework there is no Ruby<00:01:09.640> un<00:01:09.840> rails<00:01:10.200> no<00:01:10.400> Unity<00:01:10.759> no<00:01:10.920> Unreal<00:01:11.320> Engine 00:01:12.190 --> 00:01:12.200 align:start position:0% Ruby un rails no Unity no Unreal Engine 00:01:12.200 --> 00:01:14.070 align:start position:0% Ruby un rails no Unity no Unreal Engine and<00:01:12.360> so<00:01:12.680> that's<00:01:12.880> why<00:01:13.040> we<00:01:13.360> basically<00:01:13.640> build<00:01:13.880> mud 00:01:14.070 --> 00:01:14.080 align:start position:0% and so that's why we basically build mud 00:01:14.080 --> 00:01:15.510 align:start position:0% and so that's why we basically build mud from<00:01:14.200> the<00:01:14.280> ground<00:01:14.520> up<00:01:14.720> to<00:01:14.880> make<00:01:15.000> it<00:01:15.240> possible 00:01:15.510 --> 00:01:15.520 align:start position:0% from the ground up to make it possible 00:01:15.520 --> 00:01:17.390 align:start position:0% from the ground up to make it possible to<00:01:15.680> develop<00:01:16.040> onent<00:01:16.520> games<00:01:16.880> in<00:01:17.000> the<00:01:17.159> first 00:01:17.390 --> 00:01:17.400 align:start position:0% to develop onent games in the first 00:01:17.400 --> 00:01:19.950 align:start position:0% to develop onent games in the first place<00:01:17.880> without<00:01:18.159> spending<00:01:18.799> two<00:01:19.320> two<00:01:19.520> like<00:01:19.680> two 00:01:19.950 --> 00:01:19.960 align:start position:0% place without spending two two like two 00:01:19.960 --> 00:01:21.870 align:start position:0% place without spending two two like two years<00:01:20.720> like<00:01:20.920> dark<00:01:21.159> firstes<00:01:21.439> to<00:01:21.520> get<00:01:21.680> like<00:01:21.799> a 00:01:21.870 --> 00:01:21.880 align:start position:0% years like dark firstes to get like a 00:01:21.880 --> 00:01:24.510 align:start position:0% years like dark firstes to get like a few<00:01:22.119> a<00:01:22.240> few<00:01:22.520> few<00:01:22.680> features<00:01:23.040> up<00:01:23.960> we<00:01:24.079> were<00:01:24.240> hoping 00:01:24.510 --> 00:01:24.520 align:start position:0% few a few few features up we were hoping 00:01:24.520 --> 00:01:26.030 align:start position:0% few a few few features up we were hoping to<00:01:24.640> see<00:01:24.799> the<00:01:24.920> next<00:01:25.159> 10<00:01:25.360> dark<00:01:25.560> firstest<00:01:25.799> emerge 00:01:26.030 --> 00:01:26.040 align:start position:0% to see the next 10 dark firstest emerge 00:01:26.040 --> 00:01:27.749 align:start position:0% to see the next 10 dark firstest emerge from<00:01:26.200> this<00:01:26.360> work<00:01:26.960> and<00:01:27.159> the<00:01:27.280> amount<00:01:27.520> of 00:01:27.749 --> 00:01:27.759 align:start position:0% from this work and the amount of 00:01:27.759 --> 00:01:29.590 align:start position:0% from this work and the amount of projects<00:01:28.280> that<00:01:28.560> we're<00:01:28.759> demoing<00:01:29.240> this<00:01:29.320> morning 00:01:29.590 --> 00:01:29.600 align:start position:0% projects that we're demoing this morning 00:01:29.600 --> 00:01:31.550 align:start position:0% projects that we're demoing this morning is<00:01:29.720> a<00:01:30.000> Testament<00:01:30.439> to<00:01:30.560> the<00:01:30.680> success<00:01:31.000> of<00:01:31.119> these 00:01:31.550 --> 00:01:31.560 align:start position:0% is a Testament to the success of these 00:01:31.560 --> 00:01:34.030 align:start position:0% is a Testament to the success of these thesis<00:01:32.560> so<00:01:32.799> second<00:01:33.159> the<00:01:33.280> issue<00:01:33.520> with<00:01:33.720> the<00:01:33.960> the 00:01:34.030 --> 00:01:34.040 align:start position:0% thesis so second the issue with the the 00:01:34.040 --> 00:01:35.910 align:start position:0% thesis so second the issue with the the word<00:01:34.280> computer<00:01:34.640> is<00:01:34.759> it<00:01:34.960> cost<00:01:35.240> a<00:01:35.360> ton<00:01:35.560> of<00:01:35.720> money 00:01:35.910 --> 00:01:35.920 align:start position:0% word computer is it cost a ton of money 00:01:35.920 --> 00:01:39.550 align:start position:0% word computer is it cost a ton of money to<00:01:36.119> run<00:01:37.119> um<00:01:38.119> I<00:01:38.280> actually<00:01:38.840> dark<00:01:39.119> frest<00:01:39.439> was 00:01:39.550 --> 00:01:39.560 align:start position:0% to run um I actually dark frest was 00:01:39.560 --> 00:01:41.350 align:start position:0% to run um I actually dark frest was first<00:01:39.759> running<00:01:40.000> on<00:01:40.159> robone<00:01:40.720> test<00:01:40.960> net<00:01:41.240> and 00:01:41.350 --> 00:01:41.360 align:start position:0% first running on robone test net and 00:01:41.360 --> 00:01:42.950 align:start position:0% first running on robone test net and then<00:01:41.479> they<00:01:41.640> broke<00:01:41.960> the<00:01:42.079> test<00:01:42.360> net<00:01:42.759> and<00:01:42.880> then 00:01:42.950 --> 00:01:42.960 align:start position:0% then they broke the test net and then 00:01:42.960 --> 00:01:45.069 align:start position:0% then they broke the test net and then they<00:01:43.079> moved<00:01:43.320> to<00:01:43.960> U<00:01:44.079> noses<00:01:44.479> chain<00:01:44.719> formerly 00:01:45.069 --> 00:01:45.079 align:start position:0% they moved to U noses chain formerly 00:01:45.079 --> 00:01:47.910 align:start position:0% they moved to U noses chain formerly called<00:01:45.560> XI<00:01:46.560> uh<00:01:46.920> because<00:01:47.200> running<00:01:47.439> on<00:01:47.600> Main<00:01:47.799> it 00:01:47.910 --> 00:01:47.920 align:start position:0% called XI uh because running on Main it 00:01:47.920 --> 00:01:50.429 align:start position:0% called XI uh because running on Main it was<00:01:48.040> not<00:01:48.280> possible<00:01:48.600> and<00:01:48.719> this<00:01:48.880> was<00:01:49.159> before<00:01:49.479> l2s 00:01:50.429 --> 00:01:50.439 align:start position:0% was not possible and this was before l2s 00:01:50.439 --> 00:01:53.190 align:start position:0% was not possible and this was before l2s and<00:01:50.560> so<00:01:51.000> running<00:01:51.640> any<00:01:51.960> decently<00:01:52.479> complex<00:01:52.960> game 00:01:53.190 --> 00:01:53.200 align:start position:0% and so running any decently complex game 00:01:53.200 --> 00:01:54.749 align:start position:0% and so running any decently complex game would<00:01:53.399> cost<00:01:53.600> you<00:01:53.799> hundreds<00:01:54.119> of<00:01:54.240> dollars<00:01:54.560> every 00:01:54.749 --> 00:01:54.759 align:start position:0% would cost you hundreds of dollars every 00:01:54.759 --> 00:01:57.789 align:start position:0% would cost you hundreds of dollars every day<00:01:55.040> even<00:01:55.360> with<00:01:55.799> blobs<00:01:56.360> basically<00:01:57.159> so<00:01:57.640> the 00:01:57.789 --> 00:01:57.799 align:start position:0% day even with blobs basically so the 00:01:57.799 --> 00:02:00.190 align:start position:0% day even with blobs basically so the second<00:01:58.320> large<00:01:58.640> infrastructure<00:01:59.280> project<00:01:59.680> we 00:02:00.190 --> 00:02:00.200 align:start position:0% second large infrastructure project we 00:02:00.200 --> 00:02:02.389 align:start position:0% second large infrastructure project we we<00:02:00.479> we<00:02:00.600> we<00:02:00.759> worked<00:02:01.000> on<00:02:01.240> is<00:02:01.600> building<00:02:01.920> Redstone 00:02:02.389 --> 00:02:02.399 align:start position:0% we we we worked on is building Redstone 00:02:02.399 --> 00:02:04.990 align:start position:0% we we we worked on is building Redstone and<00:02:02.560> the<00:02:02.719> underlying<00:02:03.479> LDA<00:02:04.079> and<00:02:04.280> op<00:02:04.600> plasma 00:02:04.990 --> 00:02:05.000 align:start position:0% and the underlying LDA and op plasma 00:02:05.000 --> 00:02:07.230 align:start position:0% and the underlying LDA and op plasma protocol<00:02:05.520> with<00:02:05.640> the<00:02:05.759> op<00:02:06.000> stack<00:02:06.240> team<00:02:07.039> um<00:02:07.119> in 00:02:07.230 --> 00:02:07.240 align:start position:0% protocol with the op stack team um in 00:02:07.240 --> 00:02:09.109 align:start position:0% protocol with the op stack team um in order<00:02:07.399> to<00:02:07.520> reduce<00:02:07.799> cost<00:02:08.119> dramatically 00:02:09.109 --> 00:02:09.119 align:start position:0% order to reduce cost dramatically 00:02:09.119 --> 00:02:10.710 align:start position:0% order to reduce cost dramatically without<00:02:09.640> impacting<00:02:10.080> the<00:02:10.200> guarantee<00:02:10.560> of<00:02:10.640> the 00:02:10.710 --> 00:02:10.720 align:start position:0% without impacting the guarantee of the 00:02:10.720 --> 00:02:13.589 align:start position:0% without impacting the guarantee of the world<00:02:10.920> computer<00:02:11.319> too<00:02:11.720> significantly<00:02:12.720> and<00:02:12.840> so 00:02:13.589 --> 00:02:13.599 align:start position:0% world computer too significantly and so 00:02:13.599 --> 00:02:15.110 align:start position:0% world computer too significantly and so with<00:02:13.800> these<00:02:13.959> two<00:02:14.160> upgrades<00:02:14.640> we<00:02:14.760> saw<00:02:15.000> the 00:02:15.110 --> 00:02:15.120 align:start position:0% with these two upgrades we saw the 00:02:15.120 --> 00:02:17.309 align:start position:0% with these two upgrades we saw the design<00:02:15.400> space<00:02:15.680> open<00:02:16.000> up<00:02:16.239> like<00:02:16.400> massively<00:02:17.080> many 00:02:17.309 --> 00:02:17.319 align:start position:0% design space open up like massively many 00:02:17.319 --> 00:02:18.750 align:start position:0% design space open up like massively many many<00:02:17.560> games<00:02:17.800> are<00:02:17.920> being<00:02:18.120> worked<00:02:18.360> on<00:02:18.560> as<00:02:18.680> you 00:02:18.750 --> 00:02:18.760 align:start position:0% many games are being worked on as you 00:02:18.760 --> 00:02:20.790 align:start position:0% many games are being worked on as you have<00:02:18.840> seen<00:02:19.000> in<00:02:19.160> demos<00:02:19.480> this<00:02:19.599> morning<00:02:20.239> this<00:02:20.360> is 00:02:20.790 --> 00:02:20.800 align:start position:0% have seen in demos this morning this is 00:02:20.800 --> 00:02:22.869 align:start position:0% have seen in demos this morning this is a<00:02:20.959> snapshot<00:02:21.640> of<00:02:22.000> of<00:02:22.080> the<00:02:22.200> logos<00:02:22.480> of<00:02:22.599> the<00:02:22.680> people 00:02:22.869 --> 00:02:22.879 align:start position:0% a snapshot of of the logos of the people 00:02:22.879 --> 00:02:24.949 align:start position:0% a snapshot of of the logos of the people that<00:02:23.040> presented<00:02:23.400> so<00:02:23.599> far<00:02:24.400> but<00:02:24.519> a<00:02:24.640> computer 00:02:24.949 --> 00:02:24.959 align:start position:0% that presented so far but a computer 00:02:24.959 --> 00:02:26.390 align:start position:0% that presented so far but a computer still<00:02:25.160> lacks<00:02:25.400> some<00:02:25.599> pretty<00:02:25.840> significant 00:02:26.390 --> 00:02:26.400 align:start position:0% still lacks some pretty significant 00:02:26.400 --> 00:02:28.630 align:start position:0% still lacks some pretty significant capabilities<00:02:27.400> um<00:02:27.840> and<00:02:28.080> we've<00:02:28.280> been<00:02:28.400> kind<00:02:28.519> of 00:02:28.630 --> 00:02:28.640 align:start position:0% capabilities um and we've been kind of 00:02:28.640 --> 00:02:30.229 align:start position:0% capabilities um and we've been kind of thinking<00:02:29.000> what<00:02:29.239> further<00:02:29.560> improve<00:02:29.879> movements 00:02:30.229 --> 00:02:30.239 align:start position:0% thinking what further improve movements 00:02:30.239 --> 00:02:32.229 align:start position:0% thinking what further improve movements can<00:02:30.360> we<00:02:30.560> make<00:02:31.040> to<00:02:31.200> the<00:02:31.319> computer<00:02:31.720> to<00:02:31.879> benefit 00:02:32.229 --> 00:02:32.239 align:start position:0% can we make to the computer to benefit 00:02:32.239 --> 00:02:33.589 align:start position:0% can we make to the computer to benefit all<00:02:32.319> of<00:02:32.480> these<00:02:32.640> existing<00:02:33.080> projects<00:02:33.400> and 00:02:33.589 --> 00:02:33.599 align:start position:0% all of these existing projects and 00:02:33.599 --> 00:02:36.470 align:start position:0% all of these existing projects and further<00:02:34.040> up<00:02:34.239> open<00:02:34.519> up<00:02:34.720> the<00:02:34.879> design<00:02:35.319> space<00:02:36.120> and 00:02:36.470 --> 00:02:36.480 align:start position:0% further up open up the design space and 00:02:36.480 --> 00:02:37.990 align:start position:0% further up open up the design space and I<00:02:36.519> mean<00:02:36.720> we<00:02:36.840> have<00:02:36.959> some<00:02:37.120> leads<00:02:37.519> on<00:02:37.640> what<00:02:37.760> needs 00:02:37.990 --> 00:02:38.000 align:start position:0% I mean we have some leads on what needs 00:02:38.000 --> 00:02:40.070 align:start position:0% I mean we have some leads on what needs to<00:02:38.080> be<00:02:38.200> fixed<00:02:38.560> next<00:02:39.239> so<00:02:39.440> first<00:02:39.680> the<00:02:39.800> computer 00:02:40.070 --> 00:02:40.080 align:start position:0% to be fixed next so first the computer 00:02:40.080 --> 00:02:42.670 align:start position:0% to be fixed next so first the computer is<00:02:40.159> still<00:02:40.400> slow<00:02:40.680> as<00:02:40.879> hell<00:02:41.680> um<00:02:42.200> actions<00:02:42.519> are 00:02:42.670 --> 00:02:42.680 align:start position:0% is still slow as hell um actions are 00:02:42.680 --> 00:02:44.430 align:start position:0% is still slow as hell um actions are being<00:02:42.879> confirmed<00:02:43.280> after<00:02:43.680> two<00:02:43.959> plus<00:02:44.159> second 00:02:44.430 --> 00:02:44.440 align:start position:0% being confirmed after two plus second 00:02:44.440 --> 00:02:46.990 align:start position:0% being confirmed after two plus second delays<00:02:44.720> on<00:02:44.879> most<00:02:45.040> l2s<00:02:45.800> and<00:02:46.000> half<00:02:46.200> a<00:02:46.400> second<00:02:46.800> on 00:02:46.990 --> 00:02:47.000 align:start position:0% delays on most l2s and half a second on 00:02:47.000 --> 00:02:48.589 align:start position:0% delays on most l2s and half a second on the<00:02:47.120> lowest<00:02:47.440> latency<00:02:47.879> ones<00:02:48.239> like<00:02:48.360> this<00:02:48.480> is 00:02:48.589 --> 00:02:48.599 align:start position:0% the lowest latency ones like this is 00:02:48.599 --> 00:02:50.550 align:start position:0% the lowest latency ones like this is about<00:02:48.959> as<00:02:49.080> close<00:02:49.319> as<00:02:49.400> you<00:02:49.519> can<00:02:49.680> get<00:02:50.159> and<00:02:50.319> even 00:02:50.550 --> 00:02:50.560 align:start position:0% about as close as you can get and even 00:02:50.560 --> 00:02:52.190 align:start position:0% about as close as you can get and even then<00:02:50.800> with<00:02:51.000> all<00:02:51.280> this<00:02:51.480> the<00:02:51.560> other<00:02:51.879> kinds<00:02:52.080> of 00:02:52.190 --> 00:02:52.200 align:start position:0% then with all this the other kinds of 00:02:52.200 --> 00:02:54.309 align:start position:0% then with all this the other kinds of overhead<00:02:52.680> from<00:02:52.879> tools<00:02:53.519> usually<00:02:53.920> reach<00:02:54.200> like 00:02:54.309 --> 00:02:54.319 align:start position:0% overhead from tools usually reach like 00:02:54.319 --> 00:02:57.110 align:start position:0% overhead from tools usually reach like 1.5<00:02:54.800> seconds<00:02:55.080> to<00:02:55.200> 2<00:02:55.360> seconds<00:02:56.319> the<00:02:56.480> second 00:02:57.110 --> 00:02:57.120 align:start position:0% 1.5 seconds to 2 seconds the second 00:02:57.120 --> 00:02:59.110 align:start position:0% 1.5 seconds to 2 seconds the second biggest<00:02:57.519> issue<00:02:57.879> is<00:02:58.239> creating<00:02:58.519> an<00:02:58.680> account<00:02:58.959> is 00:02:59.110 --> 00:02:59.120 align:start position:0% biggest issue is creating an account is 00:02:59.120 --> 00:03:00.990 align:start position:0% biggest issue is creating an account is also<00:02:59.360> like<00:02:59.519> extreme<00:02:59.840> extremely<00:03:00.159> complicated 00:03:00.990 --> 00:03:01.000 align:start position:0% also like extreme extremely complicated 00:03:01.000 --> 00:03:02.270 align:start position:0% also like extreme extremely complicated you<00:03:01.159> thought<00:03:01.360> going<00:03:01.519> to<00:03:01.599> the<00:03:01.720> game<00:03:01.920> store<00:03:02.159> and 00:03:02.270 --> 00:03:02.280 align:start position:0% you thought going to the game store and 00:03:02.280 --> 00:03:03.670 align:start position:0% you thought going to the game store and buying<00:03:02.560> World<00:03:02.760> of<00:03:02.920> Warcraft<00:03:03.360> and<00:03:03.480> putting 00:03:03.670 --> 00:03:03.680 align:start position:0% buying World of Warcraft and putting 00:03:03.680 --> 00:03:05.710 align:start position:0% buying World of Warcraft and putting your<00:03:03.840> CD<00:03:04.159> key<00:03:04.319> in<00:03:04.519> was<00:03:04.720> hard<00:03:05.319> we<00:03:05.440> found 00:03:05.710 --> 00:03:05.720 align:start position:0% your CD key in was hard we found 00:03:05.720 --> 00:03:07.589 align:start position:0% your CD key in was hard we found something<00:03:06.000> harder<00:03:06.720> so<00:03:06.959> after<00:03:07.159> you<00:03:07.280> create<00:03:07.519> an 00:03:07.589 --> 00:03:07.599 align:start position:0% something harder so after you create an 00:03:07.599 --> 00:03:08.869 align:start position:0% something harder so after you create an account<00:03:07.840> on<00:03:07.920> the<00:03:08.000> world<00:03:08.239> computer<00:03:08.640> you<00:03:08.760> have 00:03:08.869 --> 00:03:08.879 align:start position:0% account on the world computer you have 00:03:08.879 --> 00:03:10.990 align:start position:0% account on the world computer you have to<00:03:09.080> like<00:03:09.440> add<00:03:09.680> money<00:03:09.959> to<00:03:10.200> it<00:03:10.599> and<00:03:10.760> because 00:03:10.990 --> 00:03:11.000 align:start position:0% to like add money to it and because 00:03:11.000 --> 00:03:12.630 align:start position:0% to like add money to it and because otherwise<00:03:11.280> you<00:03:11.319> can't<00:03:11.480> make<00:03:11.640> further<00:03:12.000> actions 00:03:12.630 --> 00:03:12.640 align:start position:0% otherwise you can't make further actions 00:03:12.640 --> 00:03:14.470 align:start position:0% otherwise you can't make further actions it's<00:03:12.760> a<00:03:12.920> whole<00:03:13.120> issue<00:03:13.560> and<00:03:13.920> there's<00:03:14.159> a<00:03:14.319> bunch 00:03:14.470 --> 00:03:14.480 align:start position:0% it's a whole issue and there's a bunch 00:03:14.480 --> 00:03:16.630 align:start position:0% it's a whole issue and there's a bunch of<00:03:14.640> people<00:03:14.920> working<00:03:15.440> on<00:03:15.640> that<00:03:16.120> uh<00:03:16.200> we're<00:03:16.400> not 00:03:16.630 --> 00:03:16.640 align:start position:0% of people working on that uh we're not 00:03:16.640 --> 00:03:18.390 align:start position:0% of people working on that uh we're not saying<00:03:16.920> we're<00:03:17.120> the<00:03:17.200> only<00:03:17.360> one<00:03:17.519> doing<00:03:17.799> this<00:03:18.280> but 00:03:18.390 --> 00:03:18.400 align:start position:0% saying we're the only one doing this but 00:03:18.400 --> 00:03:20.149 align:start position:0% saying we're the only one doing this but it<00:03:18.519> has<00:03:18.640> been<00:03:19.080> difficult<00:03:19.200> to<00:03:19.360> find<00:03:19.640> Integrated 00:03:20.149 --> 00:03:20.159 align:start position:0% it has been difficult to find Integrated 00:03:20.159 --> 00:03:21.830 align:start position:0% it has been difficult to find Integrated Solutions<00:03:20.560> that<00:03:20.720> don't<00:03:20.959> bring<00:03:21.239> other<00:03:21.599> kinds 00:03:21.830 --> 00:03:21.840 align:start position:0% Solutions that don't bring other kinds 00:03:21.840 --> 00:03:23.509 align:start position:0% Solutions that don't bring other kinds of<00:03:22.120> problem<00:03:22.640> when<00:03:22.760> you<00:03:22.840> start<00:03:23.080> adding<00:03:23.360> this 00:03:23.509 --> 00:03:23.519 align:start position:0% of problem when you start adding this 00:03:23.519 --> 00:03:26.990 align:start position:0% of problem when you start adding this stuff<00:03:23.720> up<00:03:24.720> um<00:03:25.239> and<00:03:25.400> so<00:03:25.799> earlier<00:03:26.200> today<00:03:26.760> uh<00:03:26.879> you 00:03:26.990 --> 00:03:27.000 align:start position:0% stuff up um and so earlier today uh you 00:03:27.000 --> 00:03:28.470 align:start position:0% stuff up um and so earlier today uh you know<00:03:27.200> already<00:03:27.440> if<00:03:27.519> you're<00:03:27.680> too<00:03:27.879> online<00:03:28.280> cuz<00:03:28.400> we 00:03:28.470 --> 00:03:28.480 align:start position:0% know already if you're too online cuz we 00:03:28.480 --> 00:03:30.070 align:start position:0% know already if you're too online cuz we tweeted<00:03:28.799> about<00:03:29.000> it<00:03:29.280> if<00:03:29.400> you<00:03:29.480> don't<00:03:29.599> know<00:03:29.879> about 00:03:30.070 --> 00:03:30.080 align:start position:0% tweeted about it if you don't know about 00:03:30.080 --> 00:03:31.390 align:start position:0% tweeted about it if you don't know about it<00:03:30.280> I'm<00:03:30.439> I'm<00:03:30.560> proud<00:03:30.760> of<00:03:30.840> you<00:03:31.000> guys<00:03:31.120> for<00:03:31.239> not 00:03:31.390 --> 00:03:31.400 align:start position:0% it I'm I'm proud of you guys for not 00:03:31.400 --> 00:03:32.830 align:start position:0% it I'm I'm proud of you guys for not spending<00:03:31.720> all<00:03:31.840> of<00:03:31.959> your<00:03:32.080> time<00:03:32.319> on<00:03:32.560> on<00:03:32.720> on 00:03:32.830 --> 00:03:32.840 align:start position:0% spending all of your time on on on 00:03:32.840 --> 00:03:35.149 align:start position:0% spending all of your time on on on Twitter<00:03:33.439> we<00:03:33.560> announced<00:03:34.040> Quarry<00:03:34.599> which<00:03:34.720> is<00:03:35.040> an 00:03:35.149 --> 00:03:35.159 align:start position:0% Twitter we announced Quarry which is an 00:03:35.159 --> 00:03:36.589 align:start position:0% Twitter we announced Quarry which is an upgrade<00:03:35.480> to<00:03:35.599> the<00:03:35.680> computer<00:03:36.080> that<00:03:36.239> tackled 00:03:36.589 --> 00:03:36.599 align:start position:0% upgrade to the computer that tackled 00:03:36.599 --> 00:03:38.750 align:start position:0% upgrade to the computer that tackled both<00:03:36.760> of<00:03:36.920> these<00:03:37.120> issues<00:03:38.080> so<00:03:38.360> the<00:03:38.480> biggest 00:03:38.750 --> 00:03:38.760 align:start position:0% both of these issues so the biggest 00:03:38.760 --> 00:03:40.270 align:start position:0% both of these issues so the biggest thing<00:03:38.879> from<00:03:39.080> qu<00:03:39.360> is<00:03:39.439> we<00:03:39.599> basically<00:03:39.920> decreased 00:03:40.270 --> 00:03:40.280 align:start position:0% thing from qu is we basically decreased 00:03:40.280 --> 00:03:43.070 align:start position:0% thing from qu is we basically decreased the<00:03:40.360> latency<00:03:41.000> 99%<00:03:42.000> from<00:03:42.200> the<00:03:42.360> now<00:03:42.599> to<00:03:42.760> Common 00:03:43.070 --> 00:03:43.080 align:start position:0% the latency 99% from the now to Common 00:03:43.080 --> 00:03:44.789 align:start position:0% the latency 99% from the now to Common 2C<00:03:43.519> block<00:03:43.760> time<00:03:43.879> to<00:03:44.040> as<00:03:44.159> low<00:03:44.319> as<00:03:44.480> 7 00:03:44.789 --> 00:03:44.799 align:start position:0% 2C block time to as low as 7 00:03:44.799 --> 00:03:46.869 align:start position:0% 2C block time to as low as 7 milliseconds<00:03:45.799> we<00:03:45.959> also<00:03:46.120> made<00:03:46.280> it<00:03:46.439> possible<00:03:46.720> to 00:03:46.869 --> 00:03:46.879 align:start position:0% milliseconds we also made it possible to 00:03:46.879 --> 00:03:48.670 align:start position:0% milliseconds we also made it possible to have<00:03:47.080> oneclick<00:03:47.599> Pass<00:03:47.879> Key<00:03:48.040> enabled<00:03:48.439> account 00:03:48.670 --> 00:03:48.680 align:start position:0% have oneclick Pass Key enabled account 00:03:48.680 --> 00:03:50.670 align:start position:0% have oneclick Pass Key enabled account Creation<00:03:49.120> with<00:03:49.280> sponsored<00:03:49.760> gas<00:03:50.239> so<00:03:50.439> behind 00:03:50.670 --> 00:03:50.680 align:start position:0% Creation with sponsored gas so behind 00:03:50.680 --> 00:03:52.470 align:start position:0% Creation with sponsored gas so behind this<00:03:50.879> mumbo<00:03:51.239> jumbo<00:03:51.640> what<00:03:51.720> this<00:03:51.879> means<00:03:52.079> is<00:03:52.319> your 00:03:52.470 --> 00:03:52.480 align:start position:0% this mumbo jumbo what this means is your 00:03:52.480 --> 00:03:53.350 align:start position:0% this mumbo jumbo what this means is your players<00:03:52.720> can<00:03:52.879> just<00:03:52.959> start<00:03:53.159> playing 00:03:53.350 --> 00:03:53.360 align:start position:0% players can just start playing 00:03:53.360 --> 00:03:55.110 align:start position:0% players can just start playing immediately<00:03:54.000> and<00:03:54.120> then<00:03:54.360> on<00:03:54.560> board 00:03:55.110 --> 00:03:55.120 align:start position:0% immediately and then on board 00:03:55.120 --> 00:03:57.910 align:start position:0% immediately and then on board progressively<00:03:56.120> um<00:03:56.920> and<00:03:57.159> in<00:03:57.280> order<00:03:57.480> to<00:03:57.680> show 00:03:57.910 --> 00:03:57.920 align:start position:0% progressively um and in order to show 00:03:57.920 --> 00:04:00.309 align:start position:0% progressively um and in order to show you<00:03:58.640> uh<00:03:58.840> cuz<00:03:59.159> we<00:03:59.319> hate<00:03:59.480> the<00:03:59.959> of<00:04:00.079> like<00:04:00.200> just 00:04:00.309 --> 00:04:00.319 align:start position:0% you uh cuz we hate the of like just 00:04:00.319 --> 00:04:01.710 align:start position:0% you uh cuz we hate the of like just build<00:04:00.519> a<00:04:00.599> bunch<00:04:00.799> of<00:04:00.920> infrastructure<00:04:01.439> and<00:04:01.560> hope 00:04:01.710 --> 00:04:01.720 align:start position:0% build a bunch of infrastructure and hope 00:04:01.720 --> 00:04:02.910 align:start position:0% build a bunch of infrastructure and hope people<00:04:01.879> are<00:04:01.959> going<00:04:02.120> to<00:04:02.239> be<00:04:02.360> able<00:04:02.599> to<00:04:02.720> make 00:04:02.910 --> 00:04:02.920 align:start position:0% people are going to be able to make 00:04:02.920 --> 00:04:04.270 align:start position:0% people are going to be able to make sense<00:04:03.159> of<00:04:03.280> what<00:04:03.400> you've<00:04:03.560> put<00:04:03.799> together<00:04:04.159> we 00:04:04.270 --> 00:04:04.280 align:start position:0% sense of what you've put together we 00:04:04.280 --> 00:04:05.470 align:start position:0% sense of what you've put together we actually<00:04:04.480> spend<00:04:04.680> a<00:04:04.799> lot<00:04:04.879> of<00:04:05.000> time<00:04:05.120> building<00:04:05.400> a 00:04:05.470 --> 00:04:05.480 align:start position:0% actually spend a lot of time building a 00:04:05.480 --> 00:04:10.589 align:start position:0% actually spend a lot of time building a bunch<00:04:05.640> of<00:04:05.760> demos<00:04:06.560> so<00:04:07.159> um<00:04:07.439> the<00:04:07.599> first<00:04:07.959> one<00:04:08.480> is 00:04:10.589 --> 00:04:10.599 align:start position:0% bunch of demos so um the first one is 00:04:10.599 --> 00:04:13.190 align:start position:0% bunch of demos so um the first one is Doom<00:04:11.599> we'll<00:04:11.799> see<00:04:11.959> if<00:04:12.079> that 00:04:13.190 --> 00:04:13.200 align:start position:0% Doom we'll see if that 00:04:13.200 --> 00:04:17.909 align:start position:0% Doom we'll see if that plays<00:04:14.200> there<00:04:14.360> we<00:04:14.519> go<00:04:14.799> so<00:04:15.280> this<00:04:15.400> is<00:04:16.000> um<00:04:16.919> Doom 00:04:17.909 --> 00:04:17.919 align:start position:0% plays there we go so this is um Doom 00:04:17.919 --> 00:04:19.349 align:start position:0% plays there we go so this is um Doom specifically<00:04:18.400> chocolate<00:04:18.759> Doom<00:04:18.959> a<00:04:19.040> fork<00:04:19.239> of 00:04:19.349 --> 00:04:19.359 align:start position:0% specifically chocolate Doom a fork of 00:04:19.359 --> 00:04:20.949 align:start position:0% specifically chocolate Doom a fork of chocolate<00:04:19.680> doom<00:04:20.320> and<00:04:20.440> it's<00:04:20.560> running<00:04:20.799> on 00:04:20.949 --> 00:04:20.959 align:start position:0% chocolate doom and it's running on 00:04:20.959 --> 00:04:24.710 align:start position:0% chocolate doom and it's running on Quarry<00:04:21.919> um<00:04:22.560> so<00:04:23.280> this<00:04:23.440> runs<00:04:23.759> at<00:04:23.880> about<00:04:24.080> like<00:04:24.240> 35 00:04:24.710 --> 00:04:24.720 align:start position:0% Quarry um so this runs at about like 35 00:04:24.720 --> 00:04:26.390 align:start position:0% Quarry um so this runs at about like 35 FPS<00:04:25.160> because<00:04:25.360> of<00:04:25.440> the<00:04:25.560> net<00:04:25.720> code<00:04:25.919> of<00:04:26.000> Doom 00:04:26.390 --> 00:04:26.400 align:start position:0% FPS because of the net code of Doom 00:04:26.400 --> 00:04:29.790 align:start position:0% FPS because of the net code of Doom transactions<00:04:27.400> are<00:04:27.759> sent<00:04:28.080> to<00:04:28.800> um<00:04:29.039> quarry 00:04:29.790 --> 00:04:29.800 align:start position:0% transactions are sent to um quarry 00:04:29.800 --> 00:04:31.310 align:start position:0% transactions are sent to um quarry confirm<00:04:30.160> in<00:04:30.320> about<00:04:30.560> like<00:04:30.680> 7<00:04:30.919> to<00:04:31.080> 15 00:04:31.310 --> 00:04:31.320 align:start position:0% confirm in about like 7 to 15 00:04:31.320 --> 00:04:32.749 align:start position:0% confirm in about like 7 to 15 milliseconds<00:04:31.880> come<00:04:32.039> back<00:04:32.199> and<00:04:32.320> reflect<00:04:32.680> the 00:04:32.749 --> 00:04:32.759 align:start position:0% milliseconds come back and reflect the 00:04:32.759 --> 00:04:34.350 align:start position:0% milliseconds come back and reflect the state<00:04:32.960> update<00:04:33.240> on<00:04:33.320> each<00:04:33.479> client<00:04:34.000> so<00:04:34.160> this<00:04:34.240> is 00:04:34.350 --> 00:04:34.360 align:start position:0% state update on each client so this is 00:04:34.360 --> 00:04:35.990 align:start position:0% state update on each client so this is running<00:04:34.600> in<00:04:34.720> real<00:04:34.919> time<00:04:35.039> there<00:04:35.120> are<00:04:35.280> no<00:04:35.400> tricks 00:04:35.990 --> 00:04:36.000 align:start position:0% running in real time there are no tricks 00:04:36.000 --> 00:04:38.629 align:start position:0% running in real time there are no tricks there<00:04:36.120> are<00:04:36.199> no<00:04:36.400> like<00:04:36.600> optimistic<00:04:37.199> updates<00:04:37.919> or 00:04:38.629 --> 00:04:38.639 align:start position:0% there are no like optimistic updates or 00:04:38.639 --> 00:04:40.189 align:start position:0% there are no like optimistic updates or like<00:04:38.840> a<00:04:38.960> lot<00:04:39.120> of<00:04:39.280> client<00:04:39.560> code<00:04:39.800> to<00:04:39.880> make<00:04:40.039> this 00:04:40.189 --> 00:04:40.199 align:start position:0% like a lot of client code to make this 00:04:40.199 --> 00:04:41.550 align:start position:0% like a lot of client code to make this work<00:04:40.440> this<00:04:40.520> is<00:04:40.680> basically<00:04:41.000> just<00:04:41.120> Doom<00:04:41.440> with 00:04:41.550 --> 00:04:41.560 align:start position:0% work this is basically just Doom with 00:04:41.560 --> 00:04:42.629 align:start position:0% work this is basically just Doom with like<00:04:41.680> a<00:04:41.759> little<00:04:41.919> bit<00:04:42.039> of<00:04:42.160> mud<00:04:42.400> State 00:04:42.629 --> 00:04:42.639 align:start position:0% like a little bit of mud State 00:04:42.639 --> 00:04:44.990 align:start position:0% like a little bit of mud State synchronization<00:04:43.240> on<00:04:43.440> top<00:04:44.280> um<00:04:44.600> and<00:04:44.800> some 00:04:44.990 --> 00:04:45.000 align:start position:0% synchronization on top um and some 00:04:45.000 --> 00:04:46.390 align:start position:0% synchronization on top um and some interesting<00:04:45.360> things<00:04:45.520> to<00:04:45.720> point<00:04:46.039> here<00:04:46.160> is 00:04:46.390 --> 00:04:46.400 align:start position:0% interesting things to point here is 00:04:46.400 --> 00:04:48.390 align:start position:0% interesting things to point here is every<00:04:46.639> second<00:04:47.039> each<00:04:47.199> client<00:04:47.520> is<00:04:47.600> sending<00:04:47.919> 35 00:04:48.390 --> 00:04:48.400 align:start position:0% every second each client is sending 35 00:04:48.400 --> 00:04:50.230 align:start position:0% every second each client is sending 35 transactions<00:04:49.120> so<00:04:49.320> inputs<00:04:49.600> and<00:04:49.759> state<00:04:49.960> update 00:04:50.230 --> 00:04:50.240 align:start position:0% transactions so inputs and state update 00:04:50.240 --> 00:04:51.550 align:start position:0% transactions so inputs and state update to<00:04:50.320> the<00:04:50.440> chain<00:04:50.919> from<00:04:51.080> which<00:04:51.240> the<00:04:51.320> other 00:04:51.550 --> 00:04:51.560 align:start position:0% to the chain from which the other 00:04:51.560 --> 00:04:52.790 align:start position:0% to the chain from which the other clients<00:04:51.919> receive<00:04:52.240> the<00:04:52.360> information<00:04:52.680> to 00:04:52.790 --> 00:04:52.800 align:start position:0% clients receive the information to 00:04:52.800 --> 00:04:54.510 align:start position:0% clients receive the information to synchronize<00:04:53.240> what's<00:04:53.360> shown<00:04:53.560> on<00:04:53.639> the<00:04:53.759> clients 00:04:54.510 --> 00:04:54.520 align:start position:0% synchronize what's shown on the clients 00:04:54.520 --> 00:04:56.310 align:start position:0% synchronize what's shown on the clients and<00:04:54.720> because<00:04:54.919> of<00:04:55.080> the<00:04:55.199> way<00:04:55.360> Doom<00:04:55.639> was<00:04:55.800> written 00:04:56.310 --> 00:04:56.320 align:start position:0% and because of the way Doom was written 00:04:56.320 --> 00:04:58.029 align:start position:0% and because of the way Doom was written which<00:04:56.440> is<00:04:56.600> very<00:04:56.840> poorly<00:04:57.320> I<00:04:57.400> mean<00:04:57.800> we<00:04:57.919> we 00:04:58.029 --> 00:04:58.039 align:start position:0% which is very poorly I mean we we 00:04:58.039 --> 00:04:59.510 align:start position:0% which is very poorly I mean we we forgive<00:04:58.440> them<00:04:58.600> they're<00:04:58.800> the<00:04:58.960> first<00:04:59.320> kind<00:04:59.440> of 00:04:59.510 --> 00:04:59.520 align:start position:0% forgive them they're the first kind of 00:04:59.520 --> 00:05:02.469 align:start position:0% forgive them they're the first kind of like<00:04:59.759> multiplayer<00:05:00.479> firstperson<00:05:01.120> shooter<00:05:02.120> um 00:05:02.469 --> 00:05:02.479 align:start position:0% like multiplayer firstperson shooter um 00:05:02.479 --> 00:05:04.029 align:start position:0% like multiplayer firstperson shooter um it's<00:05:02.680> before<00:05:03.000> any<00:05:03.199> modern<00:05:03.520> net<00:05:03.800> code 00:05:04.029 --> 00:05:04.039 align:start position:0% it's before any modern net code 00:05:04.039 --> 00:05:05.749 align:start position:0% it's before any modern net code implementation<00:05:04.600> so<00:05:04.759> there's<00:05:05.039> no<00:05:05.600> uh 00:05:05.749 --> 00:05:05.759 align:start position:0% implementation so there's no uh 00:05:05.759 --> 00:05:07.909 align:start position:0% implementation so there's no uh predictive<00:05:06.199> net<00:05:06.440> code<00:05:06.800> there's<00:05:07.039> no<00:05:07.160> roll<00:05:07.479> back 00:05:07.909 --> 00:05:07.919 align:start position:0% predictive net code there's no roll back 00:05:07.919 --> 00:05:09.749 align:start position:0% predictive net code there's no roll back so<00:05:08.199> any<00:05:08.520> little<00:05:08.800> amount<00:05:09.000> of<00:05:09.120> latency<00:05:09.560> gets 00:05:09.749 --> 00:05:09.759 align:start position:0% so any little amount of latency gets 00:05:09.759 --> 00:05:11.230 align:start position:0% so any little amount of latency gets reflected<00:05:10.240> immediately<00:05:10.800> because<00:05:11.000> the<00:05:11.080> whole 00:05:11.230 --> 00:05:11.240 align:start position:0% reflected immediately because the whole 00:05:11.240 --> 00:05:13.590 align:start position:0% reflected immediately because the whole game<00:05:11.400> freezes<00:05:12.240> so<00:05:12.440> as<00:05:12.560> we've<00:05:12.759> been<00:05:12.919> optimizing 00:05:13.590 --> 00:05:13.600 align:start position:0% game freezes so as we've been optimizing 00:05:13.600 --> 00:05:15.230 align:start position:0% game freezes so as we've been optimizing quiry<00:05:13.880> of<00:05:14.039> the<00:05:14.120> last<00:05:14.280> two<00:05:14.400> months<00:05:14.639> Doom<00:05:14.960> became 00:05:15.230 --> 00:05:15.240 align:start position:0% quiry of the last two months Doom became 00:05:15.240 --> 00:05:17.029 align:start position:0% quiry of the last two months Doom became kind<00:05:15.360> of<00:05:15.440> our<00:05:15.680> Benchmark<00:05:16.479> there<00:05:16.600> was<00:05:16.919> a 00:05:17.029 --> 00:05:17.039 align:start position:0% kind of our Benchmark there was a 00:05:17.039 --> 00:05:18.510 align:start position:0% kind of our Benchmark there was a notorious<00:05:17.560> problem<00:05:17.840> where<00:05:18.000> every<00:05:18.120> two<00:05:18.280> second 00:05:18.510 --> 00:05:18.520 align:start position:0% notorious problem where every two second 00:05:18.520 --> 00:05:19.830 align:start position:0% notorious problem where every two second there<00:05:18.600> would<00:05:18.720> be<00:05:18.800> a<00:05:18.880> little<00:05:19.080> blip<00:05:19.639> that<00:05:19.759> we 00:05:19.830 --> 00:05:19.840 align:start position:0% there would be a little blip that we 00:05:19.840 --> 00:05:21.189 align:start position:0% there would be a little blip that we didn't<00:05:20.160> catch<00:05:20.440> when<00:05:20.560> we<00:05:20.639> were<00:05:20.800> working<00:05:21.039> on 00:05:21.189 --> 00:05:21.199 align:start position:0% didn't catch when we were working on 00:05:21.199 --> 00:05:22.510 align:start position:0% didn't catch when we were working on Quarry<00:05:21.600> but<00:05:21.720> that<00:05:21.840> was<00:05:21.960> like<00:05:22.199> pretty 00:05:22.510 --> 00:05:22.520 align:start position:0% Quarry but that was like pretty 00:05:22.520 --> 00:05:24.390 align:start position:0% Quarry but that was like pretty significant<00:05:23.000> when<00:05:23.160> playing<00:05:23.360> Doom<00:05:23.960> so<00:05:24.199> yeah<00:05:24.319> it 00:05:24.390 --> 00:05:24.400 align:start position:0% significant when playing Doom so yeah it 00:05:24.400 --> 00:05:25.950 align:start position:0% significant when playing Doom so yeah it has<00:05:24.520> been<00:05:24.680> great<00:05:24.880> to<00:05:25.120> to<00:05:25.240> kind<00:05:25.360> of<00:05:25.479> use<00:05:25.720> that<00:05:25.880> as 00:05:25.950 --> 00:05:25.960 align:start position:0% has been great to to kind of use that as 00:05:25.960 --> 00:05:27.990 align:start position:0% has been great to to kind of use that as a<00:05:26.160> as<00:05:26.240> a<00:05:26.360> target<00:05:26.680> for<00:05:27.000> hey<00:05:27.280> if<00:05:27.360> we<00:05:27.479> can<00:05:27.600> run<00:05:27.759> doom 00:05:27.990 --> 00:05:28.000 align:start position:0% a as a target for hey if we can run doom 00:05:28.000 --> 00:05:29.469 align:start position:0% a as a target for hey if we can run doom and<00:05:28.160> Quarry<00:05:28.479> then<00:05:28.639> we<00:05:28.759> can<00:05:28.880> run<00:05:29.080> anything<00:05:29.360> we 00:05:29.469 --> 00:05:29.479 align:start position:0% and Quarry then we can run anything we 00:05:29.479 --> 00:05:30.590 align:start position:0% and Quarry then we can run anything we want 00:05:30.590 --> 00:05:30.600 align:start position:0% want 00:05:30.600 --> 00:05:35.469 align:start position:0% want um<00:05:31.319> the<00:05:31.479> second<00:05:31.800> demo<00:05:32.160> I<00:05:32.720> have<00:05:33.720> um<00:05:34.680> if<00:05:34.880> it<00:05:35.039> plays 00:05:35.469 --> 00:05:35.479 align:start position:0% um the second demo I have um if it plays 00:05:35.479 --> 00:05:38.629 align:start position:0% um the second demo I have um if it plays yes<00:05:35.919> is<00:05:36.080> move<00:05:36.319> the<00:05:36.440> fly<00:05:37.120> so<00:05:37.400> move<00:05:37.680> the<00:05:37.800> fly<00:05:38.400> oh 00:05:38.629 --> 00:05:38.639 align:start position:0% yes is move the fly so move the fly oh 00:05:38.639 --> 00:05:41.990 align:start position:0% yes is move the fly so move the fly oh no<00:05:39.240> no<00:05:39.479> don't<00:05:39.720> spoil<00:05:40.080> it<00:05:40.520> okay<00:05:41.520> uh<00:05:41.600> move<00:05:41.840> the 00:05:41.990 --> 00:05:42.000 align:start position:0% no no don't spoil it okay uh move the 00:05:42.000 --> 00:05:44.469 align:start position:0% no no don't spoil it okay uh move the fly<00:05:42.400> is<00:05:42.759> um<00:05:43.080> a<00:05:43.240> game<00:05:43.560> where<00:05:43.840> you<00:05:44.000> can<00:05:44.199> either 00:05:44.469 --> 00:05:44.479 align:start position:0% fly is um a game where you can either 00:05:44.479 --> 00:05:47.909 align:start position:0% fly is um a game where you can either move<00:05:45.000> a<00:05:45.479> fly<00:05:46.199> or<00:05:46.360> you<00:05:46.440> can<00:05:46.600> move<00:05:46.800> a<00:05:46.960> frog<00:05:47.520> frogs 00:05:47.909 --> 00:05:47.919 align:start position:0% move a fly or you can move a frog frogs 00:05:47.919 --> 00:05:50.110 align:start position:0% move a fly or you can move a frog frogs eat<00:05:48.160> flies<00:05:48.720> flies<00:05:49.039> don't<00:05:49.240> eat<00:05:49.479> anything<00:05:49.960> they 00:05:50.110 --> 00:05:50.120 align:start position:0% eat flies flies don't eat anything they 00:05:50.120 --> 00:05:53.350 align:start position:0% eat flies flies don't eat anything they just<00:05:50.280> get<00:05:50.759> eaten<00:05:51.759> um<00:05:52.400> and<00:05:52.800> you<00:05:52.960> can<00:05:53.120> start 00:05:53.350 --> 00:05:53.360 align:start position:0% just get eaten um and you can start 00:05:53.360 --> 00:05:55.230 align:start position:0% just get eaten um and you can start playing<00:05:53.680> move<00:05:53.880> the<00:05:54.000> fly<00:05:54.440> by<00:05:54.639> pulling<00:05:54.880> out<00:05:55.080> your 00:05:55.230 --> 00:05:55.240 align:start position:0% playing move the fly by pulling out your 00:05:55.240 --> 00:05:57.670 align:start position:0% playing move the fly by pulling out your phone<00:05:55.960> um<00:05:56.520> either<00:05:56.800> doing<00:05:57.039> face<00:05:57.280> ID<00:05:57.479> if<00:05:57.560> you're 00:05:57.670 --> 00:05:57.680 align:start position:0% phone um either doing face ID if you're 00:05:57.680 --> 00:06:00.150 align:start position:0% phone um either doing face ID if you're on<00:05:57.759> an<00:05:57.919> iPhone<00:05:58.440> or<00:05:59.039> um<00:05:59.199> the<00:05:59.319> Android<00:05:59.800> web<00:06:00.000> with 00:06:00.150 --> 00:06:00.160 align:start position:0% on an iPhone or um the Android web with 00:06:00.160 --> 00:06:01.749 align:start position:0% on an iPhone or um the Android web with and<00:06:00.319> protocol<00:06:00.960> and<00:06:01.080> you<00:06:01.160> can<00:06:01.280> just<00:06:01.479> like<00:06:01.639> get 00:06:01.749 --> 00:06:01.759 align:start position:0% and protocol and you can just like get 00:06:01.759 --> 00:06:03.510 align:start position:0% and protocol and you can just like get into<00:06:01.919> the<00:06:02.080> game<00:06:02.280> immediately<00:06:03.000> with<00:06:03.120> a<00:06:03.240> smart 00:06:03.510 --> 00:06:03.520 align:start position:0% into the game immediately with a smart 00:06:03.520 --> 00:06:05.710 align:start position:0% into the game immediately with a smart account<00:06:03.800> wallet<00:06:04.520> and<00:06:04.759> play<00:06:05.199> with<00:06:05.400> the<00:06:05.520> same 00:06:05.710 --> 00:06:05.720 align:start position:0% account wallet and play with the same 00:06:05.720 --> 00:06:08.029 align:start position:0% account wallet and play with the same kind<00:06:05.880> of<00:06:06.000> latency<00:06:06.360> as<00:06:06.520> Doom<00:06:06.919> so<00:06:07.599> this<00:06:07.800> same 00:06:08.029 --> 00:06:08.039 align:start position:0% kind of latency as Doom so this same 00:06:08.039 --> 00:06:09.510 align:start position:0% kind of latency as Doom so this same thing<00:06:08.360> this<00:06:08.520> doesn't<00:06:08.759> have<00:06:08.880> any<00:06:09.080> optimistic 00:06:09.510 --> 00:06:09.520 align:start position:0% thing this doesn't have any optimistic 00:06:09.520 --> 00:06:10.870 align:start position:0% thing this doesn't have any optimistic update<00:06:09.840> this<00:06:10.000> basically<00:06:10.280> plays<00:06:10.479> like<00:06:10.599> a<00:06:10.680> web 00:06:10.870 --> 00:06:10.880 align:start position:0% update this basically plays like a web 00:06:10.880 --> 00:06:13.589 align:start position:0% update this basically plays like a web to<00:06:11.039> iio<00:06:11.319> game<00:06:11.599> you<00:06:11.720> know<00:06:12.360> um<00:06:12.639> and<00:06:13.199> in<00:06:13.319> order<00:06:13.520> to 00:06:13.589 --> 00:06:13.599 align:start position:0% to iio game you know um and in order to 00:06:13.599 --> 00:06:15.189 align:start position:0% to iio game you know um and in order to build<00:06:13.840> this<00:06:14.000> we<00:06:14.160> pulled<00:06:14.400> out<00:06:14.560> the<00:06:14.639> normal<00:06:14.960> mud 00:06:15.189 --> 00:06:15.199 align:start position:0% build this we pulled out the normal mud 00:06:15.199 --> 00:06:16.990 align:start position:0% build this we pulled out the normal mud template<00:06:15.639> and<00:06:15.800> we<00:06:16.120> added<00:06:16.400> like<00:06:16.560> two<00:06:16.840> three 00:06:16.990 --> 00:06:17.000 align:start position:0% template and we added like two three 00:06:17.000 --> 00:06:19.950 align:start position:0% template and we added like two three lines<00:06:17.199> of<00:06:17.319> code<00:06:17.520> to<00:06:17.639> connect<00:06:17.880> it<00:06:18.000> to<00:06:18.319> query<00:06:19.319> um 00:06:19.950 --> 00:06:19.960 align:start position:0% lines of code to connect it to query um 00:06:19.960 --> 00:06:21.589 align:start position:0% lines of code to connect it to query um and<00:06:20.120> one<00:06:20.280> last<00:06:20.440> thing<00:06:20.639> I<00:06:20.720> want<00:06:20.840> to<00:06:21.120> show<00:06:21.400> you 00:06:21.589 --> 00:06:21.599 align:start position:0% and one last thing I want to show you 00:06:21.599 --> 00:06:25.790 align:start position:0% and one last thing I want to show you folks<00:06:22.680> is<00:06:23.680> this<00:06:24.520> which<00:06:24.720> is<00:06:25.240> basically 00:06:25.790 --> 00:06:25.800 align:start position:0% folks is this which is basically 00:06:25.800 --> 00:06:28.430 align:start position:0% folks is this which is basically fortnite<00:06:26.759> so<00:06:27.319> uh<00:06:27.400> we<00:06:27.520> took<00:06:27.720> the<00:06:27.840> codebase<00:06:28.280> from 00:06:28.430 --> 00:06:28.440 align:start position:0% fortnite so uh we took the codebase from 00:06:28.440 --> 00:06:31.990 align:start position:0% fortnite so uh we took the codebase from opcraft<00:06:29.360> uh<00:06:29.599> we<00:06:29.720> added<00:06:30.000> guns<00:06:30.440> and<00:06:30.639> walls<00:06:31.639> um 00:06:31.990 --> 00:06:32.000 align:start position:0% opcraft uh we added guns and walls um 00:06:32.000 --> 00:06:33.830 align:start position:0% opcraft uh we added guns and walls um alvaris<00:06:32.680> who<00:06:32.960> is<00:06:33.080> the<00:06:33.199> worst<00:06:33.440> person<00:06:33.680> on 00:06:33.830 --> 00:06:33.840 align:start position:0% alvaris who is the worst person on 00:06:33.840 --> 00:06:35.830 align:start position:0% alvaris who is the worst person on making<00:06:34.160> names<00:06:34.520> at<00:06:34.680> the<00:06:34.800> company<00:06:35.199> called<00:06:35.400> it<00:06:35.560> m 00:06:35.830 --> 00:06:35.840 align:start position:0% making names at the company called it m 00:06:35.840 --> 00:06:38.110 align:start position:0% making names at the company called it m shoot<00:06:36.440> we<00:06:36.560> all<00:06:36.800> hate<00:06:37.000> it<00:06:37.160> it's<00:06:37.319> such<00:06:37.479> a<00:06:37.759> stupid 00:06:38.110 --> 00:06:38.120 align:start position:0% shoot we all hate it it's such a stupid 00:06:38.120 --> 00:06:41.309 align:start position:0% shoot we all hate it it's such a stupid name<00:06:38.960> but<00:06:39.080> it's<00:06:39.280> called<00:06:39.520> M<00:06:39.840> shoot<00:06:40.840> um 00:06:41.309 --> 00:06:41.319 align:start position:0% name but it's called M shoot um 00:06:41.319 --> 00:06:42.790 align:start position:0% name but it's called M shoot um and<00:06:41.840> there's<00:06:42.039> a<00:06:42.120> lot<00:06:42.240> of<00:06:42.319> interesting<00:06:42.639> things 00:06:42.790 --> 00:06:42.800 align:start position:0% and there's a lot of interesting things 00:06:42.800 --> 00:06:44.350 align:start position:0% and there's a lot of interesting things in<00:06:42.919> this<00:06:43.039> game<00:06:43.240> so<00:06:43.400> first<00:06:43.639> all<00:06:43.840> the<00:06:43.960> physics<00:06:44.240> is 00:06:44.350 --> 00:06:44.360 align:start position:0% in this game so first all the physics is 00:06:44.360 --> 00:06:46.469 align:start position:0% in this game so first all the physics is on<00:06:44.479> chain<00:06:44.840> so<00:06:45.000> jumps<00:06:45.319> movement<00:06:45.680> Etc<00:06:46.120> Ray 00:06:46.469 --> 00:06:46.479 align:start position:0% on chain so jumps movement Etc Ray 00:06:46.479 --> 00:06:48.830 align:start position:0% on chain so jumps movement Etc Ray casting<00:06:46.840> as<00:06:47.000> well<00:06:47.280> so<00:06:47.520> you<00:06:47.680> can't<00:06:47.960> just<00:06:48.199> like 00:06:48.830 --> 00:06:48.840 align:start position:0% casting as well so you can't just like 00:06:48.840 --> 00:06:50.670 align:start position:0% casting as well so you can't just like declare<00:06:49.360> hey<00:06:49.520> I'm<00:06:49.680> hitting<00:06:49.960> that<00:06:50.160> player 00:06:50.670 --> 00:06:50.680 align:start position:0% declare hey I'm hitting that player 00:06:50.680 --> 00:06:52.029 align:start position:0% declare hey I'm hitting that player there's<00:06:50.880> actually<00:06:51.080> like<00:06:51.199> a<00:06:51.280> full<00:06:51.520> Ray<00:06:51.800> cast 00:06:52.029 --> 00:06:52.039 align:start position:0% there's actually like a full Ray cast 00:06:52.039 --> 00:06:53.990 align:start position:0% there's actually like a full Ray cast happening<00:06:52.280> on<00:06:52.400> it<00:06:52.840> and<00:06:52.960> all<00:06:53.080> of<00:06:53.199> this<00:06:53.360> just 00:06:53.990 --> 00:06:54.000 align:start position:0% happening on it and all of this just 00:06:54.000 --> 00:06:55.990 align:start position:0% happening on it and all of this just runs<00:06:54.520> same<00:06:54.720> thing<00:06:54.960> without<00:06:55.240> tricks<00:06:55.720> when<00:06:55.879> we 00:06:55.990 --> 00:06:56.000 align:start position:0% runs same thing without tricks when we 00:06:56.000 --> 00:06:57.510 align:start position:0% runs same thing without tricks when we built<00:06:56.240> opcraft<00:06:56.759> you<00:06:56.879> actually<00:06:57.039> had<00:06:57.199> a<00:06:57.319> lot<00:06:57.440> of 00:06:57.510 --> 00:06:57.520 align:start position:0% built opcraft you actually had a lot of 00:06:57.520 --> 00:06:59.110 align:start position:0% built opcraft you actually had a lot of tricks<00:06:57.800> to<00:06:57.919> make<00:06:58.000> it<00:06:58.120> feel<00:06:58.360> good<00:06:58.680> doesn't<00:06:59.000> have 00:06:59.110 --> 00:06:59.120 align:start position:0% tricks to make it feel good doesn't have 00:06:59.120 --> 00:07:00.390 align:start position:0% tricks to make it feel good doesn't have any<00:06:59.240> tricks<00:06:59.599> because<00:06:59.759> oh<00:06:59.960> we<00:07:00.120> just<00:07:00.240> like 00:07:00.390 --> 00:07:00.400 align:start position:0% any tricks because oh we just like 00:07:00.400 --> 00:07:02.869 align:start position:0% any tricks because oh we just like removed<00:07:01.039> a<00:07:01.160> ton<00:07:01.319> of<00:07:01.479> code<00:07:02.080> so<00:07:02.479> these<00:07:02.599> are<00:07:02.759> the 00:07:02.869 --> 00:07:02.879 align:start position:0% removed a ton of code so these are the 00:07:02.879 --> 00:07:04.830 align:start position:0% removed a ton of code so these are the three<00:07:03.039> demos<00:07:03.360> we<00:07:03.520> have<00:07:04.120> uh<00:07:04.199> you'll<00:07:04.400> be<00:07:04.479> able<00:07:04.680> to 00:07:04.830 --> 00:07:04.840 align:start position:0% three demos we have uh you'll be able to 00:07:04.840 --> 00:07:06.830 align:start position:0% three demos we have uh you'll be able to try<00:07:05.080> them<00:07:05.319> at<00:07:05.400> the<00:07:05.520> gaming<00:07:05.800> corner<00:07:06.240> at<00:07:06.479> at<00:07:06.599> 3 00:07:06.830 --> 00:07:06.840 align:start position:0% try them at the gaming corner at at 3 00:07:06.840 --> 00:07:08.710 align:start position:0% try them at the gaming corner at at 3 p.m.<00:07:07.039> I<00:07:07.120> think<00:07:07.240> later<00:07:07.560> today<00:07:08.319> now<00:07:08.440> I<00:07:08.520> want<00:07:08.599> to 00:07:08.710 --> 00:07:08.720 align:start position:0% p.m. I think later today now I want to 00:07:08.720 --> 00:07:10.189 align:start position:0% p.m. I think later today now I want to talk<00:07:08.840> a<00:07:08.919> little<00:07:09.039> bit<00:07:09.199> about<00:07:09.440> like<00:07:09.599> how<00:07:09.759> we<00:07:09.919> made 00:07:10.189 --> 00:07:10.199 align:start position:0% talk a little bit about like how we made 00:07:10.199 --> 00:07:13.350 align:start position:0% talk a little bit about like how we made this<00:07:11.000> so<00:07:12.000> um<00:07:12.360> common<00:07:12.720> across<00:07:13.000> the<00:07:13.120> three 00:07:13.350 --> 00:07:13.360 align:start position:0% this so um common across the three 00:07:13.360 --> 00:07:15.390 align:start position:0% this so um common across the three projects<00:07:13.840> is<00:07:13.960> the<00:07:14.080> need<00:07:14.280> for<00:07:14.560> low<00:07:14.840> latency 00:07:15.390 --> 00:07:15.400 align:start position:0% projects is the need for low latency 00:07:15.400 --> 00:07:17.230 align:start position:0% projects is the need for low latency without<00:07:15.720> sacrificing<00:07:16.240> on<00:07:16.479> boarding<00:07:16.919> so<00:07:17.039> we'll 00:07:17.230 --> 00:07:17.240 align:start position:0% without sacrificing on boarding so we'll 00:07:17.240 --> 00:07:19.430 align:start position:0% without sacrificing on boarding so we'll talk<00:07:17.400> about<00:07:17.599> how<00:07:17.720> that<00:07:17.879> works<00:07:18.160> so<00:07:18.520> this<00:07:18.639> is<00:07:19.240> um 00:07:19.430 --> 00:07:19.440 align:start position:0% talk about how that works so this is um 00:07:19.440 --> 00:07:21.430 align:start position:0% talk about how that works so this is um a<00:07:19.639> traditional<00:07:20.120> block<00:07:20.400> building<00:07:20.800> algorithm 00:07:21.430 --> 00:07:21.440 align:start position:0% a traditional block building algorithm 00:07:21.440 --> 00:07:23.670 align:start position:0% a traditional block building algorithm so<00:07:21.919> transactions<00:07:22.400> come<00:07:22.599> into<00:07:22.759> the<00:07:22.879> men<00:07:23.160> pool 00:07:23.670 --> 00:07:23.680 align:start position:0% so transactions come into the men pool 00:07:23.680 --> 00:07:24.990 align:start position:0% so transactions come into the men pool they<00:07:23.840> get<00:07:24.000> ordered<00:07:24.479> right<00:07:24.639> before<00:07:24.840> the 00:07:24.990 --> 00:07:25.000 align:start position:0% they get ordered right before the 00:07:25.000 --> 00:07:27.110 align:start position:0% they get ordered right before the payload<00:07:25.360> gets<00:07:25.560> built<00:07:26.000> by<00:07:26.120> the<00:07:26.240> consensus<00:07:26.800> node 00:07:27.110 --> 00:07:27.120 align:start position:0% payload gets built by the consensus node 00:07:27.120 --> 00:07:28.990 align:start position:0% payload gets built by the consensus node and<00:07:27.199> then<00:07:27.400> people<00:07:27.759> get<00:07:28.039> their<00:07:28.319> confirmation 00:07:28.990 --> 00:07:29.000 align:start position:0% and then people get their confirmation 00:07:29.000 --> 00:07:30.550 align:start position:0% and then people get their confirmation if<00:07:29.120> the<00:07:29.240> trans<00:07:29.599> action<00:07:29.759> l<00:07:29.960> in<00:07:30.080> the<00:07:30.199> blocks 00:07:30.550 --> 00:07:30.560 align:start position:0% if the trans action l in the blocks 00:07:30.560 --> 00:07:32.909 align:start position:0% if the trans action l in the blocks after<00:07:30.879> about<00:07:31.120> 2<00:07:31.280> seconds<00:07:32.240> the<00:07:32.360> way<00:07:32.560> query 00:07:32.909 --> 00:07:32.919 align:start position:0% after about 2 seconds the way query 00:07:32.919 --> 00:07:35.830 align:start position:0% after about 2 seconds the way query works<00:07:33.400> is<00:07:34.039> the<00:07:34.319> block<00:07:34.639> building<00:07:35.080> algorithm 00:07:35.830 --> 00:07:35.840 align:start position:0% works is the block building algorithm 00:07:35.840 --> 00:07:37.909 align:start position:0% works is the block building algorithm does<00:07:36.000> not<00:07:36.199> span<00:07:36.599> 2<00:07:36.879> seconds<00:07:37.240> it<00:07:37.479> operates<00:07:37.759> on 00:07:37.909 --> 00:07:37.919 align:start position:0% does not span 2 seconds it operates on 00:07:37.919 --> 00:07:39.790 align:start position:0% does not span 2 seconds it operates on much<00:07:38.039> smaller<00:07:38.400> micro<00:07:38.759> batches<00:07:39.280> and<00:07:39.400> so<00:07:39.639> you 00:07:39.790 --> 00:07:39.800 align:start position:0% much smaller micro batches and so you 00:07:39.800 --> 00:07:41.629 align:start position:0% much smaller micro batches and so you stream<00:07:40.280> the<00:07:40.360> block<00:07:40.599> as<00:07:40.720> it's<00:07:40.879> being<00:07:41.160> created 00:07:41.629 --> 00:07:41.639 align:start position:0% stream the block as it's being created 00:07:41.639 --> 00:07:43.510 align:start position:0% stream the block as it's being created we're<00:07:41.840> not<00:07:42.080> creating<00:07:42.440> the<00:07:42.560> blocks<00:07:42.919> every<00:07:43.120> 17 00:07:43.510 --> 00:07:43.520 align:start position:0% we're not creating the blocks every 17 00:07:43.520 --> 00:07:45.110 align:start position:0% we're not creating the blocks every 17 milliseconds<00:07:44.000> that<00:07:44.120> would<00:07:44.199> be<00:07:44.360> really<00:07:44.560> silly 00:07:45.110 --> 00:07:45.120 align:start position:0% milliseconds that would be really silly 00:07:45.120 --> 00:07:46.390 align:start position:0% milliseconds that would be really silly because<00:07:45.319> it<00:07:45.400> would<00:07:45.639> overwhelm<00:07:46.159> different 00:07:46.390 --> 00:07:46.400 align:start position:0% because it would overwhelm different 00:07:46.400 --> 00:07:47.830 align:start position:0% because it would overwhelm different kind<00:07:46.560> of<00:07:46.680> infrastructure<00:07:47.400> like<00:07:47.599> block 00:07:47.830 --> 00:07:47.840 align:start position:0% kind of infrastructure like block 00:07:47.840 --> 00:07:49.790 align:start position:0% kind of infrastructure like block explorers<00:07:48.319> wallets<00:07:48.680> Etc<00:07:49.360> you<00:07:49.440> would<00:07:49.599> also 00:07:49.790 --> 00:07:49.800 align:start position:0% explorers wallets Etc you would also 00:07:49.800 --> 00:07:51.350 align:start position:0% explorers wallets Etc you would also spend<00:07:50.080> most<00:07:50.240> of<00:07:50.319> your<00:07:50.479> time<00:07:50.639> Computing<00:07:51.000> Merkle 00:07:51.350 --> 00:07:51.360 align:start position:0% spend most of your time Computing Merkle 00:07:51.360 --> 00:07:53.270 align:start position:0% spend most of your time Computing Merkle Roots<00:07:51.680> which<00:07:51.800> is<00:07:51.879> the<00:07:52.039> very<00:07:52.240> expensive<00:07:52.960> action 00:07:53.270 --> 00:07:53.280 align:start position:0% Roots which is the very expensive action 00:07:53.280 --> 00:07:54.869 align:start position:0% Roots which is the very expensive action one<00:07:53.520> putting<00:07:53.840> together<00:07:54.039> a<00:07:54.159> block<00:07:54.599> so<00:07:54.759> the 00:07:54.869 --> 00:07:54.879 align:start position:0% one putting together a block so the 00:07:54.879 --> 00:07:57.589 align:start position:0% one putting together a block so the blocks<00:07:55.199> get<00:07:55.360> streamed<00:07:55.840> to<00:07:56.000> you<00:07:56.360> as<00:07:56.520> you<00:07:56.720> play 00:07:57.589 --> 00:07:57.599 align:start position:0% blocks get streamed to you as you play 00:07:57.599 --> 00:07:59.550 align:start position:0% blocks get streamed to you as you play um<00:07:57.840> and<00:07:57.960> you<00:07:58.319> and<00:07:58.520> because<00:07:58.759> we<00:07:58.879> don't<00:07:59.080> actually 00:07:59.550 --> 00:07:59.560 align:start position:0% um and you and because we don't actually 00:07:59.560 --> 00:08:01.670 align:start position:0% um and you and because we don't actually need<00:07:59.800> things<00:08:00.120> like<00:08:00.280> the<00:08:00.440> block<00:08:00.759> hash<00:08:01.360> in<00:08:01.440> order 00:08:01.670 --> 00:08:01.680 align:start position:0% need things like the block hash in order 00:08:01.680 --> 00:08:03.830 align:start position:0% need things like the block hash in order to<00:08:01.840> reflect<00:08:02.319> a<00:08:02.440> state<00:08:02.759> update<00:08:03.159> in<00:08:03.280> the<00:08:03.440> game 00:08:03.830 --> 00:08:03.840 align:start position:0% to reflect a state update in the game 00:08:03.840 --> 00:08:05.270 align:start position:0% to reflect a state update in the game you<00:08:03.919> don't<00:08:04.120> actually<00:08:04.319> need<00:08:04.479> to<00:08:04.680> wait<00:08:05.000> for<00:08:05.159> the 00:08:05.270 --> 00:08:05.280 align:start position:0% you don't actually need to wait for the 00:08:05.280 --> 00:08:07.149 align:start position:0% you don't actually need to wait for the full<00:08:05.479> block<00:08:05.680> to<00:08:05.800> be<00:08:05.919> built<00:08:06.479> to<00:08:06.720> to<00:08:06.840> be<00:08:06.919> able<00:08:07.080> to 00:08:07.149 --> 00:08:07.159 align:start position:0% full block to be built to to be able to 00:08:07.159 --> 00:08:09.909 align:start position:0% full block to be built to to be able to see<00:08:07.319> what<00:08:07.520> happen<00:08:08.360> and<00:08:09.080> this<00:08:09.280> does<00:08:09.479> not<00:08:09.720> like 00:08:09.909 --> 00:08:09.919 align:start position:0% see what happen and this does not like 00:08:09.919 --> 00:08:12.710 align:start position:0% see what happen and this does not like introduce<00:08:10.520> any<00:08:10.919> additional<00:08:11.800> kind<00:08:11.960> of<00:08:12.199> like 00:08:12.710 --> 00:08:12.720 align:start position:0% introduce any additional kind of like 00:08:12.720 --> 00:08:14.830 align:start position:0% introduce any additional kind of like security<00:08:13.199> assumptions<00:08:13.720> in<00:08:13.840> a<00:08:13.960> rollup<00:08:14.599> the<00:08:14.720> way 00:08:14.830 --> 00:08:14.840 align:start position:0% security assumptions in a rollup the way 00:08:14.840 --> 00:08:16.830 align:start position:0% security assumptions in a rollup the way rollups<00:08:15.280> work<00:08:15.599> with<00:08:15.840> centralized<00:08:16.360> sequencer 00:08:16.830 --> 00:08:16.840 align:start position:0% rollups work with centralized sequencer 00:08:16.840 --> 00:08:18.390 align:start position:0% rollups work with centralized sequencer is<00:08:17.000> basically<00:08:17.280> there's<00:08:17.400> a<00:08:17.560> window<00:08:17.840> of<00:08:18.039> time<00:08:18.199> of 00:08:18.390 --> 00:08:18.400 align:start position:0% is basically there's a window of time of 00:08:18.400 --> 00:08:20.270 align:start position:0% is basically there's a window of time of about<00:08:18.599> 20<00:08:18.879> minutes<00:08:19.479> where<00:08:19.639> the<00:08:19.720> sequencer<00:08:20.159> has 00:08:20.270 --> 00:08:20.280 align:start position:0% about 20 minutes where the sequencer has 00:08:20.280 --> 00:08:22.469 align:start position:0% about 20 minutes where the sequencer has s<00:08:20.560> authority<00:08:21.000> over<00:08:21.280> how<00:08:21.759> how<00:08:21.919> the<00:08:22.000> blocks<00:08:22.360> get 00:08:22.469 --> 00:08:22.479 align:start position:0% s authority over how how the blocks get 00:08:22.479 --> 00:08:24.950 align:start position:0% s authority over how how the blocks get built<00:08:23.120> so<00:08:23.280> this<00:08:23.400> is<00:08:23.639> not<00:08:24.240> this<00:08:24.360> does<00:08:24.520> not<00:08:24.720> add 00:08:24.950 --> 00:08:24.960 align:start position:0% built so this is not this does not add 00:08:24.960 --> 00:08:26.629 align:start position:0% built so this is not this does not add essentially<00:08:25.440> like<00:08:25.599> any<00:08:25.800> guarantees<00:08:26.280> at<00:08:26.360> all 00:08:26.629 --> 00:08:26.639 align:start position:0% essentially like any guarantees at all 00:08:26.639 --> 00:08:28.309 align:start position:0% essentially like any guarantees at all sorry<00:08:26.960> any<00:08:27.159> assumption<00:08:27.639> at<00:08:27.759> all<00:08:27.879> to<00:08:28.039> the<00:08:28.120> whole 00:08:28.309 --> 00:08:28.319 align:start position:0% sorry any assumption at all to the whole 00:08:28.319 --> 00:08:31.990 align:start position:0% sorry any assumption at all to the whole system<00:08:29.280> um<00:08:29.680> so<00:08:30.159> the<00:08:30.440> hot<00:08:30.879> path<00:08:31.199> of<00:08:31.360> query<00:08:31.879> which 00:08:31.990 --> 00:08:32.000 align:start position:0% system um so the hot path of query which 00:08:32.000 --> 00:08:34.149 align:start position:0% system um so the hot path of query which is<00:08:32.320> users<00:08:32.760> sending<00:08:33.039> a<00:08:33.159> transaction<00:08:33.919> adding 00:08:34.149 --> 00:08:34.159 align:start position:0% is users sending a transaction adding 00:08:34.159 --> 00:08:35.509 align:start position:0% is users sending a transaction adding into<00:08:34.360> the<00:08:34.479> bending<00:08:34.760> block<00:08:35.080> and<00:08:35.240> getting<00:08:35.399> a 00:08:35.509 --> 00:08:35.519 align:start position:0% into the bending block and getting a 00:08:35.519 --> 00:08:37.110 align:start position:0% into the bending block and getting a stream<00:08:35.800> update<00:08:36.159> happens<00:08:36.479> in<00:08:36.640> about<00:08:36.839> 7 00:08:37.110 --> 00:08:37.120 align:start position:0% stream update happens in about 7 00:08:37.120 --> 00:08:39.630 align:start position:0% stream update happens in about 7 millisecs<00:08:38.000> so<00:08:38.120> we<00:08:38.200> were<00:08:38.320> able<00:08:38.519> to<00:08:38.680> do<00:08:38.839> this<00:08:39.080> by 00:08:39.630 --> 00:08:39.640 align:start position:0% millisecs so we were able to do this by 00:08:39.640 --> 00:08:41.029 align:start position:0% millisecs so we were able to do this by essentially<00:08:40.000> rebuilding<00:08:40.399> the<00:08:40.479> whole<00:08:40.719> stack 00:08:41.029 --> 00:08:41.039 align:start position:0% essentially rebuilding the whole stack 00:08:41.039 --> 00:08:43.870 align:start position:0% essentially rebuilding the whole stack so<00:08:41.159> we<00:08:41.320> rebuilt<00:08:41.719> the<00:08:41.800> load<00:08:42.000> balancer<00:08:43.000> we<00:08:43.399> built 00:08:43.870 --> 00:08:43.880 align:start position:0% so we rebuilt the load balancer we built 00:08:43.880 --> 00:08:45.750 align:start position:0% so we rebuilt the load balancer we built a<00:08:44.159> custom<00:08:44.480> block<00:08:44.720> Builder<00:08:45.000> on<00:08:45.120> top<00:08:45.240> of<00:08:45.360> the<00:08:45.519> ref 00:08:45.750 --> 00:08:45.760 align:start position:0% a custom block Builder on top of the ref 00:08:45.760 --> 00:08:48.430 align:start position:0% a custom block Builder on top of the ref model<00:08:46.200> architecture<00:08:47.120> from<00:08:47.519> The<00:08:47.600> Ref<00:08:47.880> team<00:08:48.320> and 00:08:48.430 --> 00:08:48.440 align:start position:0% model architecture from The Ref team and 00:08:48.440 --> 00:08:49.710 align:start position:0% model architecture from The Ref team and we<00:08:48.560> also<00:08:48.720> rebuild<00:08:49.000> our<00:08:49.120> indexer<00:08:49.519> so 00:08:49.710 --> 00:08:49.720 align:start position:0% we also rebuild our indexer so 00:08:49.720 --> 00:08:52.269 align:start position:0% we also rebuild our indexer so everything<00:08:49.959> is<00:08:50.480> very<00:08:50.720> tightly<00:08:51.160> optimized<00:08:52.160> uh 00:08:52.269 --> 00:08:52.279 align:start position:0% everything is very tightly optimized uh 00:08:52.279 --> 00:08:53.310 align:start position:0% everything is very tightly optimized uh we<00:08:52.399> also<00:08:52.560> spend<00:08:52.720> a<00:08:52.800> lot<00:08:52.880> of<00:08:52.959> time<00:08:53.080> on<00:08:53.120> the 00:08:53.310 --> 00:08:53.320 align:start position:0% we also spend a lot of time on the 00:08:53.320 --> 00:08:55.829 align:start position:0% we also spend a lot of time on the networking<00:08:54.320> and<00:08:54.440> you<00:08:54.519> can<00:08:54.680> see<00:08:54.959> that<00:08:55.480> as<00:08:55.680> these 00:08:55.829 --> 00:08:55.839 align:start position:0% networking and you can see that as these 00:08:55.839 --> 00:08:57.190 align:start position:0% networking and you can see that as these spending<00:08:56.160> transactions<00:08:56.640> get<00:08:56.760> streamed<00:08:57.080> back 00:08:57.190 --> 00:08:57.200 align:start position:0% spending transactions get streamed back 00:08:57.200 --> 00:08:59.190 align:start position:0% spending transactions get streamed back to<00:08:57.279> the<00:08:57.399> users<00:08:58.200> an<00:08:58.360> actual<00:08:58.680> block<00:08:58.920> is<00:08:59.040> being 00:08:59.190 --> 00:08:59.200 align:start position:0% to the users an actual block is being 00:08:59.200 --> 00:09:00.870 align:start position:0% to the users an actual block is being built<00:08:59.440> build<00:08:59.640> and<00:08:59.720> then<00:08:59.880> send<00:09:00.240> back<00:09:00.440> to<00:09:00.680> other 00:09:00.870 --> 00:09:00.880 align:start position:0% built build and then send back to other 00:09:00.880 --> 00:09:02.389 align:start position:0% built build and then send back to other kinds<00:09:01.079> of<00:09:01.200> infrastructure<00:09:01.880> whether<00:09:02.120> they're 00:09:02.389 --> 00:09:02.399 align:start position:0% kinds of infrastructure whether they're 00:09:02.399 --> 00:09:05.910 align:start position:0% kinds of infrastructure whether they're block<00:09:02.680> Explorer<00:09:03.399> or<00:09:03.560> or<00:09:03.720> other<00:09:04.120> periphery<00:09:05.120> um 00:09:05.910 --> 00:09:05.920 align:start position:0% block Explorer or or other periphery um 00:09:05.920 --> 00:09:07.829 align:start position:0% block Explorer or or other periphery um the<00:09:06.040> other<00:09:06.279> interesting<00:09:06.680> thing<00:09:06.880> is<00:09:07.399> most 00:09:07.829 --> 00:09:07.839 align:start position:0% the other interesting thing is most 00:09:07.839 --> 00:09:09.990 align:start position:0% the other interesting thing is most tooling<00:09:08.480> outside<00:09:09.000> out<00:09:09.240> there<00:09:09.360> for<00:09:09.560> like<00:09:09.760> stuff 00:09:09.990 --> 00:09:10.000 align:start position:0% tooling outside out there for like stuff 00:09:10.000 --> 00:09:12.269 align:start position:0% tooling outside out there for like stuff like<00:09:10.160> ERC<00:09:10.560> 437<00:09:11.240> and<00:09:11.360> on<00:09:11.519> boarding<00:09:12.000> actually 00:09:12.269 --> 00:09:12.279 align:start position:0% like ERC 437 and on boarding actually 00:09:12.279 --> 00:09:14.110 align:start position:0% like ERC 437 and on boarding actually creates<00:09:12.600> a<00:09:12.720> lot<00:09:12.880> of<00:09:13.000> latency<00:09:13.760> because<00:09:13.959> it's 00:09:14.110 --> 00:09:14.120 align:start position:0% creates a lot of latency because it's 00:09:14.120 --> 00:09:15.670 align:start position:0% creates a lot of latency because it's just<00:09:14.279> another<00:09:14.600> part<00:09:14.720> of<00:09:14.839> the<00:09:14.920> hot<00:09:15.200> path<00:09:15.519> if<00:09:15.600> you 00:09:15.670 --> 00:09:15.680 align:start position:0% just another part of the hot path if you 00:09:15.680 --> 00:09:17.990 align:start position:0% just another part of the hot path if you want<00:09:15.800> to<00:09:15.920> send<00:09:16.240> a<00:09:16.399> 437<00:09:17.160> user<00:09:17.519> operation<00:09:17.920> and 00:09:17.990 --> 00:09:18.000 align:start position:0% want to send a 437 user operation and 00:09:18.000 --> 00:09:19.550 align:start position:0% want to send a 437 user operation and you<00:09:18.079> have<00:09:18.160> to<00:09:18.279> go<00:09:18.360> through<00:09:18.480> a<00:09:18.560> bundler<00:09:19.279> even<00:09:19.480> if 00:09:19.550 --> 00:09:19.560 align:start position:0% you have to go through a bundler even if 00:09:19.560 --> 00:09:21.110 align:start position:0% you have to go through a bundler even if you<00:09:19.680> have<00:09:19.839> fast<00:09:20.079> block<00:09:20.360> time<00:09:20.720> you<00:09:20.839> end<00:09:21.000> up 00:09:21.110 --> 00:09:21.120 align:start position:0% you have fast block time you end up 00:09:21.120 --> 00:09:22.990 align:start position:0% you have fast block time you end up spending<00:09:21.399> like<00:09:21.560> 1<00:09:21.720> to<00:09:21.880> 1.5<00:09:22.399> seconds<00:09:22.720> doing 00:09:22.990 --> 00:09:23.000 align:start position:0% spending like 1 to 1.5 seconds doing 00:09:23.000 --> 00:09:26.389 align:start position:0% spending like 1 to 1.5 seconds doing that<00:09:23.560> so<00:09:23.760> we<00:09:23.959> built<00:09:24.560> a<00:09:25.000> bundler<00:09:25.720> and<00:09:25.920> an<00:09:26.120> pain 00:09:26.389 --> 00:09:26.399 align:start position:0% that so we built a bundler and an pain 00:09:26.399 --> 00:09:29.389 align:start position:0% that so we built a bundler and an pain Master<00:09:26.720> inside<00:09:27.079> query<00:09:27.480> itself<00:09:28.160> so<00:09:28.480> the<00:09:28.760> 7<00:09:29.079> Mill 00:09:29.389 --> 00:09:29.399 align:start position:0% Master inside query itself so the 7 Mill 00:09:29.399 --> 00:09:32.030 align:start position:0% Master inside query itself so the 7 Mill second<00:09:29.680> Loop<00:09:30.120> Remains<00:09:30.440> the<00:09:30.600> Same<00:09:31.440> um<00:09:31.600> even<00:09:31.880> if 00:09:32.030 --> 00:09:32.040 align:start position:0% second Loop Remains the Same um even if 00:09:32.040 --> 00:09:33.550 align:start position:0% second Loop Remains the Same um even if you<00:09:32.399> use<00:09:32.720> these<00:09:32.880> kind<00:09:33.000> of<00:09:33.120> onboarding 00:09:33.550 --> 00:09:33.560 align:start position:0% you use these kind of onboarding 00:09:33.560 --> 00:09:35.310 align:start position:0% you use these kind of onboarding features<00:09:34.160> so<00:09:34.279> it's<00:09:34.480> pretty<00:09:34.680> neat<00:09:34.959> because<00:09:35.200> you 00:09:35.310 --> 00:09:35.320 align:start position:0% features so it's pretty neat because you 00:09:35.320 --> 00:09:36.750 align:start position:0% features so it's pretty neat because you can<00:09:35.440> have<00:09:35.600> something<00:09:35.920> like<00:09:36.040> move<00:09:36.279> the<00:09:36.399> fly 00:09:36.750 --> 00:09:36.760 align:start position:0% can have something like move the fly 00:09:36.760 --> 00:09:39.030 align:start position:0% can have something like move the fly where<00:09:37.000> you<00:09:37.519> basically<00:09:37.839> scan<00:09:38.120> your<00:09:38.320> face<00:09:38.880> it's 00:09:39.030 --> 00:09:39.040 align:start position:0% where you basically scan your face it's 00:09:39.040 --> 00:09:40.550 align:start position:0% where you basically scan your face it's a<00:09:39.120> bit<00:09:39.279> dystopian<00:09:39.800> but<00:09:39.920> you<00:09:40.000> scan<00:09:40.240> your<00:09:40.360> face 00:09:40.550 --> 00:09:40.560 align:start position:0% a bit dystopian but you scan your face 00:09:40.560 --> 00:09:42.110 align:start position:0% a bit dystopian but you scan your face you<00:09:40.680> become<00:09:40.839> a<00:09:40.959> fly<00:09:41.560> and<00:09:41.680> you<00:09:41.760> can<00:09:41.839> move<00:09:42.000> the 00:09:42.110 --> 00:09:42.120 align:start position:0% you become a fly and you can move the 00:09:42.120 --> 00:09:43.710 align:start position:0% you become a fly and you can move the fly<00:09:42.360> around<00:09:42.600> and<00:09:42.720> do<00:09:42.839> all<00:09:42.959> of<00:09:43.079> that<00:09:43.240> stuff<00:09:43.560> by 00:09:43.710 --> 00:09:43.720 align:start position:0% fly around and do all of that stuff by 00:09:43.720 --> 00:09:45.389 align:start position:0% fly around and do all of that stuff by using<00:09:44.079> like<00:09:44.560> everything<00:09:44.839> you<00:09:44.959> would<00:09:45.120> expect 00:09:45.389 --> 00:09:45.399 align:start position:0% using like everything you would expect 00:09:45.399 --> 00:09:46.710 align:start position:0% using like everything you would expect if<00:09:45.519> you're<00:09:45.640> a<00:09:45.720> developer<00:09:46.200> like<00:09:46.360> I<00:09:46.440> want<00:09:46.560> to 00:09:46.710 --> 00:09:46.720 align:start position:0% if you're a developer like I want to 00:09:46.720 --> 00:09:48.829 align:start position:0% if you're a developer like I want to have<00:09:46.959> my<00:09:47.079> users<00:09:47.600> like<00:09:47.880> log<00:09:48.120> in<00:09:48.279> with<00:09:48.399> an<00:09:48.519> email 00:09:48.829 --> 00:09:48.839 align:start position:0% have my users like log in with an email 00:09:48.839 --> 00:09:50.110 align:start position:0% have my users like log in with an email and<00:09:48.959> I<00:09:49.000> want<00:09:49.120> to<00:09:49.200> be<00:09:49.279> able<00:09:49.440> to<00:09:49.600> like<00:09:49.760> sponsor 00:09:50.110 --> 00:09:50.120 align:start position:0% and I want to be able to like sponsor 00:09:50.120 --> 00:09:51.550 align:start position:0% and I want to be able to like sponsor their<00:09:50.320> gas<00:09:50.560> and<00:09:50.680> all<00:09:50.839> that<00:09:51.000> you<00:09:51.079> can<00:09:51.200> do<00:09:51.320> all<00:09:51.440> of 00:09:51.550 --> 00:09:51.560 align:start position:0% their gas and all that you can do all of 00:09:51.560 --> 00:09:54.790 align:start position:0% their gas and all that you can do all of that<00:09:51.720> with<00:09:51.880> query<00:09:52.720> without<00:09:53.560> um<00:09:54.240> increasing 00:09:54.790 --> 00:09:54.800 align:start position:0% that with query without um increasing 00:09:54.800 --> 00:09:57.710 align:start position:0% that with query without um increasing additional<00:09:55.800> uh<00:09:56.240> latency<00:09:57.079> so<00:09:57.279> the<00:09:57.399> way<00:09:57.560> this 00:09:57.710 --> 00:09:57.720 align:start position:0% additional uh latency so the way this 00:09:57.720 --> 00:09:59.670 align:start position:0% additional uh latency so the way this works<00:09:58.160> from<00:09:58.279> a<00:09:58.399> networking<00:09:58.839> perspective<00:09:59.440> is 00:09:59.670 --> 00:09:59.680 align:start position:0% works from a networking perspective is 00:09:59.680 --> 00:10:03.389 align:start position:0% works from a networking perspective is we<00:09:59.880> have<00:10:00.240> built<00:10:01.000> um<00:10:01.600> kind<00:10:01.720> of<00:10:01.880> like<00:10:02.160> a<00:10:03.040> a<00:10:03.279> a 00:10:03.389 --> 00:10:03.399 align:start position:0% we have built um kind of like a a a 00:10:03.399 --> 00:10:05.310 align:start position:0% we have built um kind of like a a a series<00:10:03.640> of<00:10:03.800> edge<00:10:04.079> regions<00:10:04.480> on<00:10:04.680> bare<00:10:04.880> metal 00:10:05.310 --> 00:10:05.320 align:start position:0% series of edge regions on bare metal 00:10:05.320 --> 00:10:07.750 align:start position:0% series of edge regions on bare metal with<00:10:05.480> servers<00:10:06.279> all<00:10:06.480> around<00:10:06.720> the<00:10:06.839> world<00:10:07.600> where 00:10:07.750 --> 00:10:07.760 align:start position:0% with servers all around the world where 00:10:07.760 --> 00:10:09.550 align:start position:0% with servers all around the world where we<00:10:07.920> have<00:10:08.200> copies<00:10:08.519> of<00:10:08.720> the<00:10:08.880> state<00:10:09.240> that<00:10:09.399> get 00:10:09.550 --> 00:10:09.560 align:start position:0% we have copies of the state that get 00:10:09.560 --> 00:10:11.190 align:start position:0% we have copies of the state that get synchronized<00:10:10.040> with<00:10:10.120> the<00:10:10.279> central<00:10:10.600> sequencer 00:10:11.190 --> 00:10:11.200 align:start position:0% synchronized with the central sequencer 00:10:11.200 --> 00:10:13.670 align:start position:0% synchronized with the central sequencer and<00:10:11.360> copies<00:10:11.680> of<00:10:11.880> yo<00:10:12.399> or<00:10:12.519> block<00:10:12.760> Builder<00:10:13.480> So 00:10:13.670 --> 00:10:13.680 align:start position:0% and copies of yo or block Builder So 00:10:13.680 --> 00:10:15.350 align:start position:0% and copies of yo or block Builder So currently<00:10:14.079> the<00:10:14.200> thing<00:10:14.399> that's<00:10:14.640> live<00:10:15.040> is<00:10:15.160> a 00:10:15.350 --> 00:10:15.360 align:start position:0% currently the thing that's live is a 00:10:15.360 --> 00:10:17.310 align:start position:0% currently the thing that's live is a single<00:10:15.640> wire<00:10:15.880> so<00:10:16.200> chain<00:10:16.519> so<00:10:16.640> there's<00:10:16.839> a<00:10:16.959> single 00:10:17.310 --> 00:10:17.320 align:start position:0% single wire so chain so there's a single 00:10:17.320 --> 00:10:19.069 align:start position:0% single wire so chain so there's a single place<00:10:17.480> in<00:10:17.600> the<00:10:17.720> world<00:10:18.040> where<00:10:18.440> things<00:10:18.959> get 00:10:19.069 --> 00:10:19.079 align:start position:0% place in the world where things get 00:10:19.079 --> 00:10:22.190 align:start position:0% place in the world where things get built<00:10:20.000> um<00:10:20.200> over<00:10:20.560> 2025<00:10:21.360> we<00:10:21.480> want<00:10:21.640> to<00:10:21.760> build<00:10:22.000> a 00:10:22.190 --> 00:10:22.200 align:start position:0% built um over 2025 we want to build a 00:10:22.200 --> 00:10:23.509 align:start position:0% built um over 2025 we want to build a system<00:10:22.640> we<00:10:22.760> have<00:10:22.880> already<00:10:23.040> started<00:10:23.279> working 00:10:23.509 --> 00:10:23.519 align:start position:0% system we have already started working 00:10:23.519 --> 00:10:25.310 align:start position:0% system we have already started working on<00:10:23.640> it<00:10:23.760> but<00:10:23.839> it's<00:10:23.920> not<00:10:24.079> really<00:10:24.399> yet<00:10:24.920> where<00:10:25.120> the 00:10:25.310 --> 00:10:25.320 align:start position:0% on it but it's not really yet where the 00:10:25.320 --> 00:10:27.389 align:start position:0% on it but it's not really yet where the state<00:10:25.680> of<00:10:25.800> a<00:10:25.959> mud<00:10:26.240> world<00:10:26.519> can<00:10:26.680> be<00:10:26.920> partitioned 00:10:27.389 --> 00:10:27.399 align:start position:0% state of a mud world can be partitioned 00:10:27.399 --> 00:10:29.590 align:start position:0% state of a mud world can be partitioned into<00:10:27.640> different<00:10:28.079> geographical<00:10:28.760> location 00:10:29.590 --> 00:10:29.600 align:start position:0% into different geographical location 00:10:29.600 --> 00:10:30.990 align:start position:0% into different geographical location such<00:10:29.880> that<00:10:30.040> you<00:10:30.120> can<00:10:30.240> have<00:10:30.399> different<00:10:30.640> matches 00:10:30.990 --> 00:10:31.000 align:start position:0% such that you can have different matches 00:10:31.000 --> 00:10:32.430 align:start position:0% such that you can have different matches as<00:10:31.120> an<00:10:31.240> example<00:10:31.519> of<00:10:31.640> Sky<00:10:31.920> strive<00:10:32.200> or<00:10:32.279> of 00:10:32.430 --> 00:10:32.440 align:start position:0% as an example of Sky strive or of 00:10:32.440 --> 00:10:34.870 align:start position:0% as an example of Sky strive or of different<00:10:32.680> regions<00:10:33.000> of<00:10:33.200> biomes<00:10:34.040> where<00:10:34.519> the 00:10:34.870 --> 00:10:34.880 align:start position:0% different regions of biomes where the 00:10:34.880 --> 00:10:36.629 align:start position:0% different regions of biomes where the computer<00:10:35.240> doing<00:10:35.519> the<00:10:35.639> ordering<00:10:36.240> can<00:10:36.360> be<00:10:36.480> in 00:10:36.629 --> 00:10:36.639 align:start position:0% computer doing the ordering can be in 00:10:36.639 --> 00:10:39.190 align:start position:0% computer doing the ordering can be in Asia<00:10:37.120> North<00:10:37.399> America<00:10:37.839> Etc<00:10:38.560> because<00:10:38.920> even<00:10:39.079> if 00:10:39.190 --> 00:10:39.200 align:start position:0% Asia North America Etc because even if 00:10:39.200 --> 00:10:40.710 align:start position:0% Asia North America Etc because even if we<00:10:39.320> have<00:10:39.399> 7<00:10:39.600> millisecond<00:10:40.040> latency<00:10:40.440> you<00:10:40.560> still 00:10:40.710 --> 00:10:40.720 align:start position:0% we have 7 millisecond latency you still 00:10:40.720 --> 00:10:42.629 align:start position:0% we have 7 millisecond latency you still have<00:10:40.839> the<00:10:40.959> pay<00:10:41.160> the<00:10:41.279> cost<00:10:41.440> of<00:10:41.560> light<00:10:42.160> sadly<00:10:42.560> we 00:10:42.629 --> 00:10:42.639 align:start position:0% have the pay the cost of light sadly we 00:10:42.639 --> 00:10:44.150 align:start position:0% have the pay the cost of light sadly we have<00:10:42.800> not<00:10:42.959> worked<00:10:43.200> on<00:10:43.360> that<00:10:43.560> yet<00:10:44.000> we'll 00:10:44.150 --> 00:10:44.160 align:start position:0% have not worked on that yet we'll 00:10:44.160 --> 00:10:46.990 align:start position:0% have not worked on that yet we'll probably<00:10:44.399> do<00:10:44.519> that<00:10:44.680> later<00:10:45.680> um<00:10:46.360> so<00:10:46.560> yeah<00:10:46.720> we<00:10:46.880> we 00:10:46.990 --> 00:10:47.000 align:start position:0% probably do that later um so yeah we we 00:10:47.000 --> 00:10:49.230 align:start position:0% probably do that later um so yeah we we hope<00:10:47.200> that<00:10:47.399> this<00:10:47.880> both<00:10:48.160> benefit<00:10:48.680> existing<00:10:49.000> Mud 00:10:49.230 --> 00:10:49.240 align:start position:0% hope that this both benefit existing Mud 00:10:49.240 --> 00:10:50.790 align:start position:0% hope that this both benefit existing Mud Games<00:10:49.480> and<00:10:49.839> significantly<00:10:50.399> expand<00:10:50.680> the 00:10:50.790 --> 00:10:50.800 align:start position:0% Games and significantly expand the 00:10:50.800 --> 00:10:52.590 align:start position:0% Games and significantly expand the design<00:10:51.079> space<00:10:51.320> of<00:10:51.399> Onan<00:10:51.680> games<00:10:51.880> and<00:10:52.000> worlds 00:10:52.590 --> 00:10:52.600 align:start position:0% design space of Onan games and worlds 00:10:52.600 --> 00:10:54.150 align:start position:0% design space of Onan games and worlds it's<00:10:52.800> basically<00:10:53.160> put<00:10:53.399> plug<00:10:53.600> and<00:10:53.760> play<00:10:54.040> you 00:10:54.150 --> 00:10:54.160 align:start position:0% it's basically put plug and play you 00:10:54.160 --> 00:10:55.710 align:start position:0% it's basically put plug and play you just<00:10:54.320> have<00:10:54.440> to<00:10:54.560> add<00:10:54.880> five<00:10:55.040> lines<00:10:55.240> of<00:10:55.360> code<00:10:55.600> to 00:10:55.710 --> 00:10:55.720 align:start position:0% just have to add five lines of code to 00:10:55.720 --> 00:10:58.829 align:start position:0% just have to add five lines of code to your<00:10:55.880> system<00:10:56.720> so<00:10:57.160> I<00:10:57.320> had<00:10:57.519> some<00:10:58.079> biome<00:10:58.399> shell 00:10:58.829 --> 00:10:58.839 align:start position:0% your system so I had some biome shell 00:10:58.839 --> 00:11:01.430 align:start position:0% your system so I had some biome shell but<00:10:58.959> I<00:10:59.040> will<00:10:59.320> I<00:10:59.399> will<00:10:59.560> skip<00:10:59.800> it<00:11:00.279> sorry<00:11:00.680> guys<00:11:01.160> um 00:11:01.430 --> 00:11:01.440 align:start position:0% but I will I will skip it sorry guys um 00:11:01.440 --> 00:11:02.949 align:start position:0% but I will I will skip it sorry guys um so<00:11:01.600> that's<00:11:01.760> it<00:11:01.839> for<00:11:01.959> me<00:11:02.079> today<00:11:02.440> to<00:11:02.560> learn<00:11:02.800> more 00:11:02.949 --> 00:11:02.959 align:start position:0% so that's it for me today to learn more 00:11:02.959 --> 00:11:04.629 align:start position:0% so that's it for me today to learn more you<00:11:03.040> can<00:11:03.160> scan<00:11:03.440> this<00:11:03.560> QR<00:11:03.839> code<00:11:04.040> or<00:11:04.200> go<00:11:04.320> to<00:11:04.480> this 00:11:04.629 --> 00:11:04.639 align:start position:0% you can scan this QR code or go to this 00:11:04.639 --> 00:11:08.030 align:start position:0% you can scan this QR code or go to this link<00:11:05.000> l<00:11:05.800> xquery<00:11:06.800> it's<00:11:06.959> available<00:11:07.360> on<00:11:07.560> devet 00:11:08.030 --> 00:11:08.040 align:start position:0% link l xquery it's available on devet 00:11:08.040 --> 00:11:09.509 align:start position:0% link l xquery it's available on devet basically<00:11:08.360> starting<00:11:08.760> now<00:11:09.240> uh<00:11:09.320> you<00:11:09.399> can 00:11:09.509 --> 00:11:09.519 align:start position:0% basically starting now uh you can 00:11:09.519 --> 00:11:12.310 align:start position:0% basically starting now uh you can already<00:11:09.760> build<00:11:09.959> on<00:11:10.120> it<00:11:10.639> and<00:11:11.040> at<00:11:11.240> 3:30<00:11:11.839> p.m.<00:11:12.200> at 00:11:12.310 --> 00:11:12.320 align:start position:0% already build on it and at 3:30 p.m. at 00:11:12.320 --> 00:11:13.990 align:start position:0% already build on it and at 3:30 p.m. at the<00:11:12.440> gaming<00:11:12.720> Corner<00:11:13.079> we'll<00:11:13.320> have<00:11:13.440> a<00:11:13.639> doom 00:11:13.990 --> 00:11:14.000 align:start position:0% the gaming Corner we'll have a doom 00:11:14.000 --> 00:11:19.700 align:start position:0% the gaming Corner we'll have a doom tournament<00:11:14.839> so<00:11:15.200> thank 00:11:19.700 --> 00:11:19.710 align:start position:0% 00:11:19.710 --> 00:11:21.110 align:start position:0% [Applause] 00:11:21.110 --> 00:11:21.120 align:start position:0% [Applause] 00:11:21.120 --> 00:11:23.389 align:start position:0% [Applause] you<00:11:22.120> all<00:11:22.279> right<00:11:22.440> we<00:11:22.560> have<00:11:22.720> three<00:11:22.920> minutes<00:11:23.200> for 00:11:23.389 --> 00:11:23.399 align:start position:0% you all right we have three minutes for 00:11:23.399 --> 00:11:24.670 align:start position:0% you all right we have three minutes for questions<00:11:23.760> apparently<00:11:24.240> let's<00:11:24.360> just<00:11:24.519> stay 00:11:24.670 --> 00:11:24.680 align:start position:0% questions apparently let's just stay 00:11:24.680 --> 00:11:27.230 align:start position:0% questions apparently let's just stay here<00:11:24.880> oh<00:11:25.040> man<00:11:25.320> okay<00:11:25.959> right<00:11:26.959> if<00:11:27.040> you<00:11:27.120> have 00:11:27.230 --> 00:11:27.240 align:start position:0% here oh man okay right if you have 00:11:27.240 --> 00:11:29.790 align:start position:0% here oh man okay right if you have question<00:11:27.639> the<00:11:27.720> MC<00:11:28.079> so<00:11:28.200> I<00:11:28.279> can't<00:11:28.480> MC<00:11:28.839> myself<00:11:29.320> so 00:11:29.790 --> 00:11:29.800 align:start position:0% question the MC so I can't MC myself so 00:11:29.800 --> 00:11:32.190 align:start position:0% question the MC so I can't MC myself so about<00:11:30.160> flow<00:11:31.160> if<00:11:31.279> you<00:11:31.399> have<00:11:31.480> a<00:11:31.600> question<00:11:32.120> you 00:11:32.190 --> 00:11:32.200 align:start position:0% about flow if you have a question you 00:11:32.200 --> 00:11:34.990 align:start position:0% about flow if you have a question you can<00:11:32.399> either<00:11:32.600> scan<00:11:32.920> this<00:11:33.079> QR<00:11:33.399> code<00:11:33.720> or<00:11:34.519> um<00:11:34.839> if 00:11:34.990 --> 00:11:35.000 align:start position:0% can either scan this QR code or um if 00:11:35.000 --> 00:11:36.750 align:start position:0% can either scan this QR code or um if people<00:11:35.279> have<00:11:35.440> a<00:11:35.600> question<00:11:35.880> also<00:11:36.480> they<00:11:36.600> can 00:11:36.750 --> 00:11:36.760 align:start position:0% people have a question also they can 00:11:36.760 --> 00:11:39.949 align:start position:0% people have a question also they can just<00:11:36.880> raise<00:11:37.160> their<00:11:37.399> hand<00:11:38.200> then<00:11:38.360> I<00:11:38.480> can<00:11:38.680> run<00:11:39.000> and 00:11:39.949 --> 00:11:39.959 align:start position:0% just raise their hand then I can run and 00:11:39.959 --> 00:11:42.870 align:start position:0% just raise their hand then I can run and give<00:11:40.959> yo<00:11:41.760> uh<00:11:41.920> if<00:11:42.000> I'm<00:11:42.160> doing<00:11:42.480> local 00:11:42.870 --> 00:11:42.880 align:start position:0% give yo uh if I'm doing local 00:11:42.880 --> 00:11:44.949 align:start position:0% give yo uh if I'm doing local development<00:11:43.680> can<00:11:43.800> I<00:11:43.920> run<00:11:44.240> quar<00:11:44.680> like<00:11:44.800> this 00:11:44.949 --> 00:11:44.959 align:start position:0% development can I run quar like this 00:11:44.959 --> 00:11:47.150 align:start position:0% development can I run quar like this whole<00:11:45.320> system<00:11:45.680> locally<00:11:46.320> or<00:11:46.519> do<00:11:46.639> I<00:11:46.920> I<00:11:47.000> have<00:11:47.079> to 00:11:47.150 --> 00:11:47.160 align:start position:0% whole system locally or do I I have to 00:11:47.160 --> 00:11:49.870 align:start position:0% whole system locally or do I I have to do<00:11:47.279> it<00:11:47.360> on<00:11:47.519> devet<00:11:47.959> at<00:11:48.120> all<00:11:48.440> all<00:11:48.720> times<00:11:49.720> yeah 00:11:49.870 --> 00:11:49.880 align:start position:0% do it on devet at all all times yeah 00:11:49.880 --> 00:11:52.590 align:start position:0% do it on devet at all all times yeah currently<00:11:50.360> yes<00:11:51.040> so<00:11:51.639> you<00:11:51.720> can<00:11:51.920> put<00:11:52.079> envil<00:11:52.480> in 00:11:52.590 --> 00:11:52.600 align:start position:0% currently yes so you can put envil in 00:11:52.600 --> 00:11:55.110 align:start position:0% currently yes so you can put envil in automine<00:11:53.480> but<00:11:53.639> actually<00:11:53.959> funny<00:11:54.320> enough<00:11:54.800> envil 00:11:55.110 --> 00:11:55.120 align:start position:0% automine but actually funny enough envil 00:11:55.120 --> 00:11:56.269 align:start position:0% automine but actually funny enough envil automine<00:11:55.560> is 00:11:56.269 --> 00:11:56.279 align:start position:0% automine is 00:11:56.279 --> 00:11:58.509 align:start position:0% automine is slower<00:11:57.279> than<00:11:57.480> query<00:11:57.839> so<00:11:58.000> yes<00:11:58.120> we<00:11:58.200> don't<00:11:58.320> have 00:11:58.509 --> 00:11:58.519 align:start position:0% slower than query so yes we don't have 00:11:58.519 --> 00:12:00.430 align:start position:0% slower than query so yes we don't have great<00:11:58.880> de<00:11:59.320> local<00:11:59.519> development<00:11:59.959> environment 00:12:00.430 --> 00:12:00.440 align:start position:0% great de local development environment 00:12:00.440 --> 00:12:01.910 align:start position:0% great de local development environment yet<00:12:00.720> but<00:12:00.920> we'll<00:12:01.079> probably<00:12:01.279> work<00:12:01.440> on<00:12:01.560> this<00:12:01.680> next 00:12:01.910 --> 00:12:01.920 align:start position:0% yet but we'll probably work on this next 00:12:01.920 --> 00:12:03.310 align:start position:0% yet but we'll probably work on this next because<00:12:02.079> this<00:12:02.160> is<00:12:02.279> a<00:12:02.399> distribut<00:12:02.880> system<00:12:03.160> it's 00:12:03.310 --> 00:12:03.320 align:start position:0% because this is a distribut system it's 00:12:03.320 --> 00:12:05.509 align:start position:0% because this is a distribut system it's kind<00:12:03.399> of<00:12:03.519> a<00:12:03.600> pain<00:12:03.800> to<00:12:03.920> run 00:12:05.509 --> 00:12:05.519 align:start position:0% kind of a pain to run 00:12:05.519 --> 00:12:07.350 align:start position:0% kind of a pain to run yourself<00:12:06.519> all<00:12:06.639> right<00:12:06.800> we<00:12:06.880> have<00:12:07.000> another 00:12:07.350 --> 00:12:07.360 align:start position:0% yourself all right we have another 00:12:07.360 --> 00:12:09.430 align:start position:0% yourself all right we have another question<00:12:07.720> here<00:12:08.000> from<00:12:08.800> somebody<00:12:09.200> in<00:12:09.320> the 00:12:09.430 --> 00:12:09.440 align:start position:0% question here from somebody in the 00:12:09.440 --> 00:12:11.150 align:start position:0% question here from somebody in the audience<00:12:09.880> what<00:12:10.000> about<00:12:10.200> Doom<00:12:10.480> logic<00:12:10.920> is<00:12:11.000> it 00:12:11.150 --> 00:12:11.160 align:start position:0% audience what about Doom logic is it 00:12:11.160 --> 00:12:13.790 align:start position:0% audience what about Doom logic is it being<00:12:11.519> validated<00:12:12.000> on<00:12:12.160> mod<00:12:12.600> great<00:12:12.839> question<00:12:13.320> so 00:12:13.790 --> 00:12:13.800 align:start position:0% being validated on mod great question so 00:12:13.800 --> 00:12:16.629 align:start position:0% being validated on mod great question so out<00:12:13.920> of<00:12:14.079> the<00:12:14.199> three<00:12:14.440> demos<00:12:14.760> you've<00:12:14.920> seen<00:12:15.800> um 00:12:16.629 --> 00:12:16.639 align:start position:0% out of the three demos you've seen um 00:12:16.639 --> 00:12:20.030 align:start position:0% out of the three demos you've seen um the<00:12:16.839> Doom<00:12:17.279> demo<00:12:18.040> only<00:12:18.360> uses<00:12:18.920> query<00:12:19.279> for<00:12:19.600> event 00:12:20.030 --> 00:12:20.040 align:start position:0% the Doom demo only uses query for event 00:12:20.040 --> 00:12:22.430 align:start position:0% the Doom demo only uses query for event relaying<00:12:21.040> so<00:12:21.240> what<00:12:21.360> we<00:12:21.480> do<00:12:21.639> is<00:12:21.800> we<00:12:21.959> take<00:12:22.199> key 00:12:22.430 --> 00:12:22.440 align:start position:0% relaying so what we do is we take key 00:12:22.440 --> 00:12:24.189 align:start position:0% relaying so what we do is we take key strokes<00:12:22.800> from<00:12:22.959> Doom<00:12:23.399> which<00:12:23.519> is<00:12:23.600> how<00:12:23.720> the<00:12:23.839> P2P 00:12:24.189 --> 00:12:24.199 align:start position:0% strokes from Doom which is how the P2P 00:12:24.199 --> 00:12:26.949 align:start position:0% strokes from Doom which is how the P2P Network<00:12:24.880> the<00:12:24.959> P2P<00:12:25.360> protocol<00:12:25.720> of<00:12:26.160> Doom<00:12:26.440> works 00:12:26.949 --> 00:12:26.959 align:start position:0% Network the P2P protocol of Doom works 00:12:26.959 --> 00:12:29.870 align:start position:0% Network the P2P protocol of Doom works and<00:12:27.079> we<00:12:27.240> relate<00:12:28.000> through<00:12:28.360> a<00:12:28.519> single<00:12:28.839> m<00:12:29.199> table 00:12:29.870 --> 00:12:29.880 align:start position:0% and we relate through a single m table 00:12:29.880 --> 00:12:31.509 align:start position:0% and we relate through a single m table we<00:12:30.040> actually<00:12:30.279> attempted<00:12:30.680> to<00:12:30.839> rebuild<00:12:31.240> all<00:12:31.360> of 00:12:31.509 --> 00:12:31.519 align:start position:0% we actually attempted to rebuild all of 00:12:31.519 --> 00:12:33.629 align:start position:0% we actually attempted to rebuild all of Doom<00:12:31.880> in<00:12:32.040> mud<00:12:32.480> but<00:12:32.720> there<00:12:32.839> were<00:12:33.040> so<00:12:33.199> many<00:12:33.480> like 00:12:33.629 --> 00:12:33.639 align:start position:0% Doom in mud but there were so many like 00:12:33.639 --> 00:12:35.550 align:start position:0% Doom in mud but there were so many like weird<00:12:34.440> problems<00:12:35.040> because<00:12:35.320> John 00:12:35.550 --> 00:12:35.560 align:start position:0% weird problems because John 00:12:35.560 --> 00:12:37.710 align:start position:0% weird problems because John karmac<00:12:36.040> is<00:12:36.199> insane<00:12:36.959> that<00:12:37.160> we<00:12:37.279> kind<00:12:37.399> of<00:12:37.519> like 00:12:37.710 --> 00:12:37.720 align:start position:0% karmac is insane that we kind of like 00:12:37.720 --> 00:12:39.389 align:start position:0% karmac is insane that we kind of like gave<00:12:37.920> up<00:12:38.279> and<00:12:38.399> that's<00:12:38.560> where<00:12:38.720> we<00:12:38.839> built<00:12:39.120> M 00:12:39.389 --> 00:12:39.399 align:start position:0% gave up and that's where we built M 00:12:39.399 --> 00:12:41.110 align:start position:0% gave up and that's where we built M Shoot<00:12:39.680> actually<00:12:39.920> so<00:12:40.040> M<00:12:40.279> shoot<00:12:40.600> runs<00:12:40.839> fully 00:12:41.110 --> 00:12:41.120 align:start position:0% Shoot actually so M shoot runs fully 00:12:41.120 --> 00:12:44.189 align:start position:0% Shoot actually so M shoot runs fully inside<00:12:41.440> mud<00:12:42.440> it's<00:12:42.639> not<00:12:42.959> just<00:12:43.120> using<00:12:43.440> mud<00:12:43.720> for 00:12:44.189 --> 00:12:44.199 align:start position:0% inside mud it's not just using mud for 00:12:44.199 --> 00:12:46.590 align:start position:0% inside mud it's not just using mud for event<00:12:44.880> kind<00:12:45.000> of<00:12:45.240> like<00:12:45.399> coordination<00:12:46.279> but<00:12:46.440> for 00:12:46.590 --> 00:12:46.600 align:start position:0% event kind of like coordination but for 00:12:46.600 --> 00:12:48.590 align:start position:0% event kind of like coordination but for the<00:12:46.720> Doom<00:12:47.040> demo<00:12:47.440> specifically<00:12:48.120> we<00:12:48.240> only<00:12:48.440> use 00:12:48.590 --> 00:12:48.600 align:start position:0% the Doom demo specifically we only use 00:12:48.600 --> 00:12:51.310 align:start position:0% the Doom demo specifically we only use it<00:12:48.760> for<00:12:49.199> sending<00:12:49.760> events<00:12:50.079> around<00:12:50.720> mostly<00:12:51.079> As<00:12:51.199> A 00:12:51.310 --> 00:12:51.320 align:start position:0% it for sending events around mostly As A 00:12:51.320 --> 00:12:53.870 align:start position:0% it for sending events around mostly As A Benchmark<00:12:51.720> for<00:12:52.240> latency<00:12:53.240> next<00:12:53.480> question<00:12:53.720> is 00:12:53.870 --> 00:12:53.880 align:start position:0% Benchmark for latency next question is 00:12:53.880 --> 00:12:54.949 align:start position:0% Benchmark for latency next question is what<00:12:54.000> is 00:12:54.949 --> 00:12:54.959 align:start position:0% what is 00:12:54.959 --> 00:12:57.590 align:start position:0% what is wsaw<00:12:55.959> wiaw<00:12:56.399> is<00:12:56.480> a<00:12:56.600> Blog<00:12:56.880> Builder<00:12:57.320> the<00:12:57.399> reason 00:12:57.590 --> 00:12:57.600 align:start position:0% wsaw wiaw is a Blog Builder the reason 00:12:57.600 --> 00:12:59.829 align:start position:0% wsaw wiaw is a Blog Builder the reason it's<00:12:57.839> called<00:12:58.079> wiaw<00:12:58.560> it's<00:12:58.720> because<00:12:58.920> we<00:12:59.320> have<00:12:59.680> um 00:12:59.829 --> 00:12:59.839 align:start position:0% it's called wiaw it's because we have um 00:12:59.839 --> 00:13:02.150 align:start position:0% it's called wiaw it's because we have um our<00:13:00.040> internal<00:13:00.480> theme<00:13:00.720> for<00:13:00.959> names<00:13:01.440> is<00:13:01.760> uh<00:13:01.880> blue 00:13:02.150 --> 00:13:02.160 align:start position:0% our internal theme for names is uh blue 00:13:02.160 --> 00:13:05.310 align:start position:0% our internal theme for names is uh blue color<00:13:02.440> workers<00:13:03.040> so<00:13:03.199> we<00:13:03.320> have<00:13:03.639> Quarry<00:13:04.480> warso 00:13:05.310 --> 00:13:05.320 align:start position:0% color workers so we have Quarry warso 00:13:05.320 --> 00:13:07.629 align:start position:0% color workers so we have Quarry warso Redstone<00:13:05.920> rolite<00:13:06.480> so<00:13:06.600> it's<00:13:06.720> out<00:13:07.000> Stone<00:13:07.399> stuff 00:13:07.629 --> 00:13:07.639 align:start position:0% Redstone rolite so it's out Stone stuff 00:13:07.639 --> 00:13:09.509 align:start position:0% Redstone rolite so it's out Stone stuff to<00:13:07.839> cut<00:13:08.040> stones<00:13:08.440> with<00:13:08.680> or<00:13:08.880> things<00:13:09.079> related<00:13:09.399> to 00:13:09.509 --> 00:13:09.519 align:start position:0% to cut stones with or things related to 00:13:09.519 --> 00:13:11.829 align:start position:0% to cut stones with or things related to Stones<00:13:10.399> next<00:13:10.639> question<00:13:10.920> please<00:13:11.480> people<00:13:11.760> in 00:13:11.829 --> 00:13:11.839 align:start position:0% Stones next question please people in 00:13:11.839 --> 00:13:12.990 align:start position:0% Stones next question please people in the<00:13:11.959> audience<00:13:12.320> really<00:13:12.440> want<00:13:12.560> to<00:13:12.680> know<00:13:12.880> how 00:13:12.990 --> 00:13:13.000 align:start position:0% the audience really want to know how 00:13:13.000 --> 00:13:14.509 align:start position:0% the audience really want to know how your<00:13:13.279> last<00:13:13.480> name<00:13:13.680> is<00:13:13.800> pronounced<00:13:14.240> my<00:13:14.360> last 00:13:14.509 --> 00:13:14.519 align:start position:0% your last name is pronounced my last 00:13:14.519 --> 00:13:16.069 align:start position:0% your last name is pronounced my last name<00:13:14.720> is<00:13:15.199> it's<00:13:15.360> kind<00:13:15.440> of<00:13:15.560> funny<00:13:15.800> because<00:13:15.959> it 00:13:16.069 --> 00:13:16.079 align:start position:0% name is it's kind of funny because it 00:13:16.079 --> 00:13:18.710 align:start position:0% name is it's kind of funny because it says<00:13:16.320> is<00:13:16.440> it<00:13:16.639> pronounced<00:13:17.560> glibert<00:13:18.079> or<00:13:18.240> glibert 00:13:18.710 --> 00:13:18.720 align:start position:0% says is it pronounced glibert or glibert 00:13:18.720 --> 00:13:21.629 align:start position:0% says is it pronounced glibert or glibert it's<00:13:18.839> pronounced<00:13:19.160> gibert<00:13:19.680> so<00:13:19.839> you<00:13:19.959> were 00:13:21.629 --> 00:13:21.639 align:start position:0% it's pronounced gibert so you were 00:13:21.639 --> 00:13:24.150 align:start position:0% it's pronounced gibert so you were right<00:13:22.639> nice<00:13:22.880> can<00:13:23.040> you<00:13:23.240> expand<00:13:23.639> more<00:13:23.920> on<00:13:24.040> the 00:13:24.150 --> 00:13:24.160 align:start position:0% right nice can you expand more on the 00:13:24.160 --> 00:13:26.230 align:start position:0% right nice can you expand more on the features<00:13:24.600> around<00:13:25.040> gas<00:13:25.360> sponsorship<00:13:26.040> yeah<00:13:26.160> so 00:13:26.230 --> 00:13:26.240 align:start position:0% features around gas sponsorship yeah so 00:13:26.240 --> 00:13:28.870 align:start position:0% features around gas sponsorship yeah so the<00:13:26.320> way<00:13:26.440> it<00:13:26.519> works<00:13:26.760> is<00:13:26.959> we<00:13:27.160> have<00:13:27.519> a<00:13:28.199> p<00:13:28.480> Master 00:13:28.870 --> 00:13:28.880 align:start position:0% the way it works is we have a p Master 00:13:28.880 --> 00:13:30.990 align:start position:0% the way it works is we have a p Master that's<00:13:29.199> part<00:13:29.360> of<00:13:29.519> query<00:13:30.079> that<00:13:30.360> that<00:13:30.600> like<00:13:30.760> gets 00:13:30.990 --> 00:13:31.000 align:start position:0% that's part of query that that like gets 00:13:31.000 --> 00:13:33.269 align:start position:0% that's part of query that that like gets evaluated<00:13:31.519> within<00:13:31.720> the<00:13:31.839> sequencer<00:13:32.519> and<00:13:32.639> so 00:13:33.269 --> 00:13:33.279 align:start position:0% evaluated within the sequencer and so 00:13:33.279 --> 00:13:36.509 align:start position:0% evaluated within the sequencer and so this<00:13:33.839> uh<00:13:34.000> pay<00:13:34.240> Master<00:13:34.760> exposes<00:13:35.519> rules<00:13:36.240> you<00:13:36.360> can 00:13:36.509 --> 00:13:36.519 align:start position:0% this uh pay Master exposes rules you can 00:13:36.519 --> 00:13:38.430 align:start position:0% this uh pay Master exposes rules you can tap<00:13:36.720> into<00:13:36.920> as<00:13:37.000> a<00:13:37.120> game<00:13:37.320> developer<00:13:37.800> saying<00:13:38.079> like 00:13:38.430 --> 00:13:38.440 align:start position:0% tap into as a game developer saying like 00:13:38.440 --> 00:13:40.389 align:start position:0% tap into as a game developer saying like I<00:13:38.639> don't<00:13:38.800> like<00:13:38.920> users<00:13:39.320> can<00:13:39.519> get<00:13:39.720> their<00:13:40.079> first 00:13:40.389 --> 00:13:40.399 align:start position:0% I don't like users can get their first 00:13:40.399 --> 00:13:42.430 align:start position:0% I don't like users can get their first 20<00:13:40.720> actions<00:13:41.040> spored<00:13:41.600> by<00:13:41.720> the<00:13:41.839> game<00:13:42.000> developer 00:13:42.430 --> 00:13:42.440 align:start position:0% 20 actions spored by the game developer 00:13:42.440 --> 00:13:44.069 align:start position:0% 20 actions spored by the game developer or<00:13:42.639> under<00:13:42.920> these<00:13:43.120> certain<00:13:43.560> conditions<00:13:43.839> so<00:13:43.959> you 00:13:44.069 --> 00:13:44.079 align:start position:0% or under these certain conditions so you 00:13:44.079 --> 00:13:45.670 align:start position:0% or under these certain conditions so you kind<00:13:44.199> of<00:13:44.320> have<00:13:44.480> like<00:13:44.600> a<00:13:44.720> whole<00:13:45.079> system<00:13:45.399> you<00:13:45.519> can 00:13:45.670 --> 00:13:45.680 align:start position:0% kind of have like a whole system you can 00:13:45.680 --> 00:13:48.350 align:start position:0% kind of have like a whole system you can tap<00:13:45.880> into<00:13:46.480> to<00:13:46.720> have<00:13:46.880> flexible 00:13:48.350 --> 00:13:48.360 align:start position:0% tap into to have flexible 00:13:48.360 --> 00:13:50.430 align:start position:0% tap into to have flexible sponsoring<00:13:49.360> all<00:13:49.480> right<00:13:49.600> I<00:13:49.680> don't<00:13:49.839> see<00:13:50.040> any<00:13:50.240> new 00:13:50.430 --> 00:13:50.440 align:start position:0% sponsoring all right I don't see any new 00:13:50.440 --> 00:13:51.910 align:start position:0% sponsoring all right I don't see any new questions<00:13:50.759> on<00:13:51.000> here<00:13:51.240> if<00:13:51.320> you<00:13:51.440> have<00:13:51.600> another 00:13:51.910 --> 00:13:51.920 align:start position:0% questions on here if you have another 00:13:51.920 --> 00:13:53.310 align:start position:0% questions on here if you have another question<00:13:52.160> you<00:13:52.279> can<00:13:52.440> also<00:13:52.680> raise<00:13:52.839> your<00:13:53.040> hand 00:13:53.310 --> 00:13:53.320 align:start position:0% question you can also raise your hand 00:13:53.320 --> 00:13:55.749 align:start position:0% question you can also raise your hand real<00:13:53.560> quick<00:13:54.120> and<00:13:54.279> I<00:13:54.360> can<00:13:54.519> hand<00:13:54.680> you<00:13:54.839> the 00:13:55.749 --> 00:13:55.759 align:start position:0% real quick and I can hand you the 00:13:55.759 --> 00:13:58.389 align:start position:0% real quick and I can hand you the mic<00:13:56.759> all<00:13:56.920> the<00:13:57.040> way<00:13:57.199> back<00:13:57.560> okay<00:13:57.920> somebody<00:13:58.240> else 00:13:58.389 --> 00:13:58.399 align:start position:0% mic all the way back okay somebody else 00:13:58.399 --> 00:14:03.150 align:start position:0% mic all the way back okay somebody else is<00:13:58.519> running 00:14:03.150 --> 00:14:03.160 align:start position:0% 00:14:03.160 --> 00:14:05.790 align:start position:0% hello<00:14:04.160> have<00:14:04.279> you<00:14:04.440> tested<00:14:04.959> how<00:14:05.160> many<00:14:05.440> players 00:14:05.790 --> 00:14:05.800 align:start position:0% hello have you tested how many players 00:14:05.800 --> 00:14:09.350 align:start position:0% hello have you tested how many players can<00:14:06.000> it<00:14:06.240> support<00:14:06.639> on<00:14:06.839> this<00:14:07.160> update<00:14:07.920> yeah<00:14:08.480> so 00:14:09.350 --> 00:14:09.360 align:start position:0% can it support on this update yeah so 00:14:09.360 --> 00:14:11.870 align:start position:0% can it support on this update yeah so the<00:14:09.759> bottleneck<00:14:10.759> currently<00:14:11.279> I<00:14:11.360> mean<00:14:11.560> it<00:14:11.720> will 00:14:11.870 --> 00:14:11.880 align:start position:0% the bottleneck currently I mean it will 00:14:11.880 --> 00:14:13.389 align:start position:0% the bottleneck currently I mean it will always<00:14:12.040> be<00:14:12.199> the<00:14:12.279> bottleneck<00:14:12.759> is<00:14:12.920> the<00:14:13.079> size<00:14:13.279> of 00:14:13.389 --> 00:14:13.399 align:start position:0% always be the bottleneck is the size of 00:14:13.399 --> 00:14:17.069 align:start position:0% always be the bottleneck is the size of your<00:14:13.639> blocks<00:14:14.639> so<00:14:15.519> query<00:14:15.880> doesn't<00:14:16.240> really<00:14:16.560> add 00:14:17.069 --> 00:14:17.079 align:start position:0% your blocks so query doesn't really add 00:14:17.079 --> 00:14:20.189 align:start position:0% your blocks so query doesn't really add like<00:14:18.000> the<00:14:18.399> the<00:14:18.680> query<00:14:19.040> doesn't<00:14:19.399> really<00:14:19.800> have 00:14:20.189 --> 00:14:20.199 align:start position:0% like the the query doesn't really have 00:14:20.199 --> 00:14:22.069 align:start position:0% like the the query doesn't really have currently<00:14:20.839> doesn't<00:14:21.079> get<00:14:21.199> Bott<00:14:21.639> by<00:14:21.759> stuff<00:14:21.959> like 00:14:22.069 --> 00:14:22.079 align:start position:0% currently doesn't get Bott by stuff like 00:14:22.079 --> 00:14:24.470 align:start position:0% currently doesn't get Bott by stuff like CPU<00:14:22.480> on<00:14:22.639> RAM<00:14:23.000> if<00:14:23.160> you<00:14:23.320> use<00:14:24.040> good<00:14:24.240> enough 00:14:24.470 --> 00:14:24.480 align:start position:0% CPU on RAM if you use good enough 00:14:24.480 --> 00:14:26.629 align:start position:0% CPU on RAM if you use good enough machines<00:14:25.240> the<00:14:25.399> issue<00:14:25.639> becomes<00:14:25.959> how<00:14:26.199> big<00:14:26.480> big 00:14:26.629 --> 00:14:26.639 align:start position:0% machines the issue becomes how big big 00:14:26.639 --> 00:14:28.230 align:start position:0% machines the issue becomes how big big your<00:14:26.759> blocks<00:14:27.079> are<00:14:27.440> so<00:14:27.639> as<00:14:27.800> example<00:14:28.079> if<00:14:28.160> you 00:14:28.230 --> 00:14:28.240 align:start position:0% your blocks are so as example if you 00:14:28.240 --> 00:14:29.749 align:start position:0% your blocks are so as example if you have<00:14:28.399> transactions<00:14:29.120> that<00:14:29.279> have<00:14:29.639> that 00:14:29.749 --> 00:14:29.759 align:start position:0% have transactions that have that 00:14:29.759 --> 00:14:31.269 align:start position:0% have transactions that have that consumes<00:14:30.120> a<00:14:30.240> tiny<00:14:30.480> amount<00:14:30.639> of<00:14:30.800> gas<00:14:31.040> you<00:14:31.120> can 00:14:31.269 --> 00:14:31.279 align:start position:0% consumes a tiny amount of gas you can 00:14:31.279 --> 00:14:32.749 align:start position:0% consumes a tiny amount of gas you can actually<00:14:31.480> put<00:14:31.639> a<00:14:31.720> lot<00:14:31.880> of<00:14:32.000> players<00:14:32.560> if<00:14:32.639> you 00:14:32.749 --> 00:14:32.759 align:start position:0% actually put a lot of players if you 00:14:32.759 --> 00:14:34.030 align:start position:0% actually put a lot of players if you have<00:14:32.839> actions<00:14:33.120> that<00:14:33.199> use<00:14:33.320> a<00:14:33.440> ton<00:14:33.600> of<00:14:33.759> gas<00:14:33.920> you 00:14:34.030 --> 00:14:34.040 align:start position:0% have actions that use a ton of gas you 00:14:34.040 --> 00:14:36.430 align:start position:0% have actions that use a ton of gas you end<00:14:34.160> up<00:14:34.279> being<00:14:34.480> bottlenecked<00:14:35.279> by<00:14:35.519> block<00:14:35.839> size 00:14:36.430 --> 00:14:36.440 align:start position:0% end up being bottlenecked by block size 00:14:36.440 --> 00:14:37.710 align:start position:0% end up being bottlenecked by block size so<00:14:36.680> it<00:14:36.800> really<00:14:37.079> depends<00:14:37.360> on<00:14:37.480> what<00:14:37.600> you're 00:14:37.710 --> 00:14:37.720 align:start position:0% so it really depends on what you're 00:14:37.720 --> 00:14:40.069 align:start position:0% so it really depends on what you're doing<00:14:38.560> but<00:14:39.000> I<00:14:39.079> mean<00:14:39.360> I'd<00:14:39.519> say<00:14:39.759> you<00:14:39.880> can 00:14:40.069 --> 00:14:40.079 align:start position:0% doing but I mean I'd say you can 00:14:40.079 --> 00:14:41.990 align:start position:0% doing but I mean I'd say you can probably<00:14:40.320> have<00:14:40.560> like<00:14:41.399> depending<00:14:41.720> on<00:14:41.800> what<00:14:41.920> you 00:14:41.990 --> 00:14:42.000 align:start position:0% probably have like depending on what you 00:14:42.000 --> 00:14:43.949 align:start position:0% probably have like depending on what you do<00:14:42.120> you<00:14:42.279> probably<00:14:42.519> can<00:14:42.680> probably<00:14:42.920> get<00:14:43.160> like 00:14:43.949 --> 00:14:43.959 align:start position:0% do you probably can probably get like 00:14:43.959 --> 00:14:45.949 align:start position:0% do you probably can probably get like 200<00:14:44.399> concurrent<00:14:44.800> players<00:14:45.240> per<00:14:45.440> chain 00:14:45.949 --> 00:14:45.959 align:start position:0% 200 concurrent players per chain 00:14:45.959 --> 00:14:47.790 align:start position:0% 200 concurrent players per chain probably<00:14:46.720> like<00:14:46.880> doing<00:14:47.160> actions<00:14:47.440> all<00:14:47.600> at<00:14:47.680> the 00:14:47.790 --> 00:14:47.800 align:start position:0% probably like doing actions all at the 00:14:47.800 --> 00:14:49.990 align:start position:0% probably like doing actions all at the same<00:14:47.959> time<00:14:48.120> all<00:14:48.240> the<00:14:48.360> time<00:14:48.480> in<00:14:48.560> a<00:14:48.680> hot<00:14:49.000> Loop 00:14:49.990 --> 00:14:50.000 align:start position:0% same time all the time in a hot Loop 00:14:50.000 --> 00:14:52.030 align:start position:0% same time all the time in a hot Loop that's<00:14:50.079> is<00:14:50.279> pretty<00:14:50.560> cool<00:14:51.320> but<00:14:51.440> for<00:14:51.680> Doom 00:14:52.030 --> 00:14:52.040 align:start position:0% that's is pretty cool but for Doom 00:14:52.040 --> 00:14:53.949 align:start position:0% that's is pretty cool but for Doom specifically<00:14:52.480> it's<00:14:52.639> not<00:14:52.800> the<00:14:52.880> case<00:14:53.480> like<00:14:53.639> Doom 00:14:53.949 --> 00:14:53.959 align:start position:0% specifically it's not the case like Doom 00:14:53.959 --> 00:14:56.910 align:start position:0% specifically it's not the case like Doom is<00:14:54.160> just<00:14:54.320> a<00:14:54.880> beast<00:14:55.399> of<00:14:55.519> a<00:14:55.680> demo<00:14:56.079> and<00:14:56.399> I<00:14:56.800> you 00:14:56.910 --> 00:14:56.920 align:start position:0% is just a beast of a demo and I you 00:14:56.920 --> 00:14:59.749 align:start position:0% is just a beast of a demo and I you can't<00:14:57.160> get<00:14:57.279> to<00:14:57.680> 200<00:14:57.920> players 00:14:59.749 --> 00:14:59.759 align:start position:0% can't get to 200 players 00:14:59.759 --> 00:15:01.189 align:start position:0% can't get to 200 players all<00:14:59.880> right<00:15:00.079> another<00:15:00.399> question<00:15:00.680> that<00:15:00.800> we<00:15:00.959> have 00:15:01.189 --> 00:15:01.199 align:start position:0% all right another question that we have 00:15:01.199 --> 00:15:05.310 align:start position:0% all right another question that we have is<00:15:01.399> can<00:15:01.560> we<00:15:01.680> use<00:15:01.920> non-m<00:15:02.639> networks<00:15:03.120> underneath 00:15:05.310 --> 00:15:05.320 align:start position:0% is can we use non-m networks underneath 00:15:05.320 --> 00:15:07.790 align:start position:0% is can we use non-m networks underneath no<00:15:06.320> uh<00:15:06.560> because<00:15:06.800> we<00:15:06.920> have<00:15:07.079> not<00:15:07.240> built<00:15:07.519> that 00:15:07.790 --> 00:15:07.800 align:start position:0% no uh because we have not built that 00:15:07.800 --> 00:15:09.509 align:start position:0% no uh because we have not built that like<00:15:08.000> this<00:15:08.160> whole<00:15:08.399> thing<00:15:08.800> is<00:15:09.199> deeply 00:15:09.509 --> 00:15:09.519 align:start position:0% like this whole thing is deeply 00:15:09.519 --> 00:15:11.030 align:start position:0% like this whole thing is deeply integrated<00:15:09.959> in<00:15:10.079> the<00:15:10.160> way<00:15:10.279> ethereum<00:15:10.680> works<00:15:10.920> all 00:15:11.030 --> 00:15:11.040 align:start position:0% integrated in the way ethereum works all 00:15:11.040 --> 00:15:12.110 align:start position:0% integrated in the way ethereum works all the<00:15:11.120> way<00:15:11.240> from<00:15:11.399> the<00:15:11.519> clients<00:15:11.880> to<00:15:12.000> the 00:15:12.110 --> 00:15:12.120 align:start position:0% the way from the clients to the 00:15:12.120 --> 00:15:14.629 align:start position:0% the way from the clients to the sponsorship<00:15:12.680> to<00:15:12.839> the<00:15:12.920> block<00:15:13.120> building<00:15:13.480> Etc<00:15:13.959> so 00:15:14.629 --> 00:15:14.639 align:start position:0% sponsorship to the block building Etc so 00:15:14.639 --> 00:15:17.189 align:start position:0% sponsorship to the block building Etc so no<00:15:15.639> cool<00:15:15.920> all<00:15:16.040> right<00:15:16.199> somebody's<00:15:16.639> asking<00:15:17.040> will 00:15:17.189 --> 00:15:17.199 align:start position:0% no cool all right somebody's asking will 00:15:17.199 --> 00:15:19.870 align:start position:0% no cool all right somebody's asking will we<00:15:17.360> be<00:15:17.560> able<00:15:17.759> to<00:15:17.920> use<00:15:18.199> pods<00:15:18.600> with<00:15:18.880> quy 00:15:19.870 --> 00:15:19.880 align:start position:0% we be able to use pods with quy 00:15:19.880 --> 00:15:23.069 align:start position:0% we be able to use pods with quy absolutely<00:15:20.480> so<00:15:20.839> pods<00:15:21.639> uh<00:15:21.759> which<00:15:21.959> stands<00:15:22.279> for 00:15:23.069 --> 00:15:23.079 align:start position:0% absolutely so pods uh which stands for 00:15:23.079 --> 00:15:25.829 align:start position:0% absolutely so pods uh which stands for provable<00:15:23.639> object<00:15:24.079> data<00:15:24.959> uh<00:15:25.120> also<00:15:25.360> known<00:15:25.639> as 00:15:25.829 --> 00:15:25.839 align:start position:0% provable object data uh also known as 00:15:25.839 --> 00:15:28.670 align:start position:0% provable object data uh also known as frogs<00:15:26.519> all<00:15:26.639> of<00:15:26.759> your<00:15:26.920> frogs<00:15:27.240> are<00:15:27.519> pods<00:15:28.160> pods<00:15:28.519> or 00:15:28.670 --> 00:15:28.680 align:start position:0% frogs all of your frogs are pods pods or 00:15:28.680 --> 00:15:30.629 align:start position:0% frogs all of your frogs are pods pods or frog<00:15:29.160> are<00:15:29.279> not<00:15:29.480> pods<00:15:29.800> but<00:15:29.880> all<00:15:30.079> pods<00:15:30.279> are 00:15:30.629 --> 00:15:30.639 align:start position:0% frog are not pods but all pods are 00:15:30.639 --> 00:15:32.350 align:start position:0% frog are not pods but all pods are actually<00:15:31.079> some<00:15:31.319> pods<00:15:31.560> are<00:15:31.680> frogs<00:15:32.040> and<00:15:32.160> some 00:15:32.350 --> 00:15:32.360 align:start position:0% actually some pods are frogs and some 00:15:32.360 --> 00:15:34.910 align:start position:0% actually some pods are frogs and some frogs<00:15:32.639> are<00:15:32.839> pods<00:15:33.480> it's<00:15:33.600> not<00:15:33.759> an<00:15:33.959> exact<00:15:34.279> mapping 00:15:34.910 --> 00:15:34.920 align:start position:0% frogs are pods it's not an exact mapping 00:15:34.920 --> 00:15:36.590 align:start position:0% frogs are pods it's not an exact mapping but<00:15:35.079> yes<00:15:35.199> you'll<00:15:35.399> be<00:15:35.519> able<00:15:35.720> to<00:15:35.959> bring<00:15:36.199> pods<00:15:36.440> on 00:15:36.590 --> 00:15:36.600 align:start position:0% but yes you'll be able to bring pods on 00:15:36.600 --> 00:15:38.389 align:start position:0% but yes you'll be able to bring pods on chain<00:15:36.880> and<00:15:37.160> and<00:15:37.360> and<00:15:37.480> settle<00:15:37.880> them<00:15:38.160> because 00:15:38.389 --> 00:15:38.399 align:start position:0% chain and and and settle them because 00:15:38.399 --> 00:15:41.710 align:start position:0% chain and and and settle them because spots<00:15:38.680> can<00:15:38.800> be<00:15:38.920> verified<00:15:39.360> in 00:15:41.710 --> 00:15:41.720 align:start position:0% 00:15:41.720 --> 00:15:43.990 align:start position:0% evm<00:15:42.720> all<00:15:42.880> right<00:15:43.079> and<00:15:43.199> I<00:15:43.319> don't<00:15:43.480> see<00:15:43.680> any<00:15:43.800> more 00:15:43.990 --> 00:15:44.000 align:start position:0% evm all right and I don't see any more 00:15:44.000 --> 00:15:45.629 align:start position:0% evm all right and I don't see any more questions<00:15:44.360> here<00:15:44.480> we<00:15:44.600> have<00:15:44.720> 30<00:15:45.079> seconds<00:15:45.480> if 00:15:45.629 --> 00:15:45.639 align:start position:0% questions here we have 30 seconds if 00:15:45.639 --> 00:15:48.790 align:start position:0% questions here we have 30 seconds if somebody<00:15:45.959> wants<00:15:46.160> to<00:15:46.959> raise<00:15:47.240> a<00:15:47.480> super<00:15:47.800> quick 00:15:48.790 --> 00:15:48.800 align:start position:0% somebody wants to raise a super quick 00:15:48.800 --> 00:15:50.670 align:start position:0% somebody wants to raise a super quick inperson<00:15:49.360> question<00:15:49.680> but<00:15:49.839> I<00:15:49.920> think<00:15:50.079> we're<00:15:50.279> good 00:15:50.670 --> 00:15:50.680 align:start position:0% inperson question but I think we're good 00:15:50.680 --> 00:15:54.680 align:start position:0% inperson question but I think we're good all<00:15:50.800> right<00:15:51.199> well<00:15:51.399> thanks<00:15:51.680> again