WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:10.629 align:start position:0% [Music] 00:00:10.629 --> 00:00:10.639 align:start position:0% [Music] 00:00:10.639 --> 00:00:14.669 align:start position:0% [Music] uh<00:00:11.040> yeah<00:00:11.360> so<00:00:12.280> thanks<00:00:12.480> for<00:00:12.679> coming<00:00:13.599> um<00:00:14.040> I<00:00:14.200> assume 00:00:14.669 --> 00:00:14.679 align:start position:0% uh yeah so thanks for coming um I assume 00:00:14.679 --> 00:00:16.710 align:start position:0% uh yeah so thanks for coming um I assume if<00:00:14.839> you're<00:00:15.080> here<00:00:15.360> or<00:00:15.879> uh<00:00:16.119> that's<00:00:16.359> because<00:00:16.600> you 00:00:16.710 --> 00:00:16.720 align:start position:0% if you're here or uh that's because you 00:00:16.720 --> 00:00:19.390 align:start position:0% if you're here or uh that's because you might<00:00:16.920> have<00:00:17.240> heard<00:00:18.240> in<00:00:18.400> the<00:00:18.600> past<00:00:18.800> few<00:00:19.000> months 00:00:19.390 --> 00:00:19.400 align:start position:0% might have heard in the past few months 00:00:19.400 --> 00:00:23.870 align:start position:0% might have heard in the past few months some<00:00:19.960> uh<00:00:20.119> some<00:00:20.400> voice<00:00:20.760> saying<00:00:21.400> maybe<00:00:22.160> veral<00:00:23.039> is 00:00:23.870 --> 00:00:23.880 align:start position:0% some uh some voice saying maybe veral is 00:00:23.880 --> 00:00:26.950 align:start position:0% some uh some voice saying maybe veral is uh<00:00:24.599> you<00:00:24.680> know<00:00:24.800> should<00:00:25.039> be<00:00:25.640> replaced<00:00:26.160> with 00:00:26.950 --> 00:00:26.960 align:start position:0% uh you know should be replaced with 00:00:26.960 --> 00:00:30.550 align:start position:0% uh you know should be replaced with starked<00:00:27.679> binary<00:00:28.400> trees<00:00:29.400> and<00:00:30.039> the<00:00:30.119> purpose<00:00:30.400> of 00:00:30.550 --> 00:00:30.560 align:start position:0% starked binary trees and the purpose of 00:00:30.560 --> 00:00:32.910 align:start position:0% starked binary trees and the purpose of this<00:00:30.720> presentation<00:00:31.359> is<00:00:31.480> to<00:00:32.439> give<00:00:32.559> you<00:00:32.719> some 00:00:32.910 --> 00:00:32.920 align:start position:0% this presentation is to give you some 00:00:32.920 --> 00:00:35.910 align:start position:0% this presentation is to give you some arguments<00:00:33.440> to<00:00:33.960> understand<00:00:34.399> why<00:00:35.239> uh<00:00:35.520> now<00:00:35.760> is 00:00:35.910 --> 00:00:35.920 align:start position:0% arguments to understand why uh now is 00:00:35.920 --> 00:00:38.389 align:start position:0% arguments to understand why uh now is not<00:00:36.320> the<00:00:36.559> the<00:00:36.719> right<00:00:36.920> time<00:00:37.079> to<00:00:37.239> do 00:00:38.389 --> 00:00:38.399 align:start position:0% not the the right time to do 00:00:38.399 --> 00:00:43.029 align:start position:0% not the the right time to do this<00:00:39.399> uh<00:00:39.520> let's<00:00:40.440> briefly<00:00:40.879> go<00:00:41.120> over<00:00:42.039> the 00:00:43.029 --> 00:00:43.039 align:start position:0% this uh let's briefly go over the 00:00:43.039 --> 00:00:45.350 align:start position:0% this uh let's briefly go over the current<00:00:43.360> status<00:00:43.640> of<00:00:43.800> veral<00:00:44.120> trees<00:00:44.920> uh<00:00:45.079> the 00:00:45.350 --> 00:00:45.360 align:start position:0% current status of veral trees uh the 00:00:45.360 --> 00:00:47.990 align:start position:0% current status of veral trees uh the veral<00:00:45.760> tree<00:00:45.960> implementation<00:00:46.440> in<00:00:46.920> ethereum<00:00:47.920> uh 00:00:47.990 --> 00:00:48.000 align:start position:0% veral tree implementation in ethereum uh 00:00:48.000 --> 00:00:50.270 align:start position:0% veral tree implementation in ethereum uh we<00:00:48.120> launched<00:00:48.399> a<00:00:48.480> devet<00:00:48.960> two<00:00:49.360> two<00:00:49.559> weeks<00:00:49.840> ago 00:00:50.270 --> 00:00:50.280 align:start position:0% we launched a devet two two weeks ago 00:00:50.280 --> 00:00:53.630 align:start position:0% we launched a devet two two weeks ago it's<00:00:50.640> uh<00:00:50.760> chugging<00:00:51.199> along<00:00:51.719> fine<00:00:52.719> uh<00:00:52.920> we<00:00:53.280> have 00:00:53.630 --> 00:00:53.640 align:start position:0% it's uh chugging along fine uh we have 00:00:53.640 --> 00:00:55.549 align:start position:0% it's uh chugging along fine uh we have something<00:00:54.120> that<00:00:54.239> is<00:00:54.440> pretty<00:00:54.719> close<00:00:55.120> to<00:00:55.359> the 00:00:55.549 --> 00:00:55.559 align:start position:0% something that is pretty close to the 00:00:55.559 --> 00:00:58.310 align:start position:0% something that is pretty close to the final<00:00:56.120> spec<00:00:57.120> we're<00:00:57.320> missing<00:00:57.680> a<00:00:57.800> couple<00:00:58.120> gas 00:00:58.310 --> 00:00:58.320 align:start position:0% final spec we're missing a couple gas 00:00:58.320 --> 00:01:00.349 align:start position:0% final spec we're missing a couple gas costs<00:00:58.600> here<00:00:58.719> and<00:00:58.920> there<00:00:59.120> but<00:00:59.320> nothing<00:00:59.800> uh 00:01:00.349 --> 00:01:00.359 align:start position:0% costs here and there but nothing uh 00:01:00.359 --> 00:01:02.110 align:start position:0% costs here and there but nothing uh nothing<00:01:00.719> that<00:01:00.840> won't<00:01:01.039> be<00:01:01.120> fixed<00:01:01.519> by<00:01:01.840> by<00:01:01.960> the 00:01:02.110 --> 00:01:02.120 align:start position:0% nothing that won't be fixed by by the 00:01:02.120 --> 00:01:05.950 align:start position:0% nothing that won't be fixed by by the next<00:01:02.800> devet<00:01:03.800> um<00:01:04.320> and<00:01:04.559> you<00:01:04.720> can<00:01:05.080> go<00:01:05.400> have<00:01:05.519> a<00:01:05.680> look 00:01:05.950 --> 00:01:05.960 align:start position:0% next devet um and you can go have a look 00:01:05.960 --> 00:01:08.149 align:start position:0% next devet um and you can go have a look at<00:01:06.400> at<00:01:06.560> this<00:01:06.720> address<00:01:07.040> it<00:01:07.159> will<00:01:07.320> be<00:01:07.479> displayed 00:01:08.149 --> 00:01:08.159 align:start position:0% at at this address it will be displayed 00:01:08.159 --> 00:01:09.710 align:start position:0% at at this address it will be displayed again<00:01:08.400> at<00:01:08.560> the 00:01:09.710 --> 00:01:09.720 align:start position:0% again at the 00:01:09.720 --> 00:01:11.990 align:start position:0% again at the end<00:01:10.720> one<00:01:10.840> of<00:01:10.960> the<00:01:11.080> biggest<00:01:11.560> things<00:01:11.840> we 00:01:11.990 --> 00:01:12.000 align:start position:0% end one of the biggest things we 00:01:12.000 --> 00:01:13.749 align:start position:0% end one of the biggest things we achieved<00:01:12.360> during<00:01:12.600> the<00:01:12.759> last<00:01:13.200> uh<00:01:13.360> during<00:01:13.600> the 00:01:13.749 --> 00:01:13.759 align:start position:0% achieved during the last uh during the 00:01:13.759 --> 00:01:16.870 align:start position:0% achieved during the last uh during the last<00:01:14.000> year<00:01:14.680> was<00:01:14.880> a<00:01:15.040> holis<00:01:15.439> sky<00:01:15.560> Shadow<00:01:15.960> Fork<00:01:16.720> uh 00:01:16.870 --> 00:01:16.880 align:start position:0% last year was a holis sky Shadow Fork uh 00:01:16.880 --> 00:01:19.749 align:start position:0% last year was a holis sky Shadow Fork uh we<00:01:17.080> validated<00:01:17.880> that<00:01:18.280> the<00:01:18.479> transition<00:01:19.000> model 00:01:19.749 --> 00:01:19.759 align:start position:0% we validated that the transition model 00:01:19.759 --> 00:01:22.030 align:start position:0% we validated that the transition model works<00:01:20.759> so<00:01:20.920> we're<00:01:21.119> really<00:01:21.320> proud<00:01:21.520> of<00:01:21.680> that<00:01:21.840> and 00:01:22.030 --> 00:01:22.040 align:start position:0% works so we're really proud of that and 00:01:22.040 --> 00:01:24.429 align:start position:0% works so we're really proud of that and big<00:01:22.200> shout<00:01:22.560> shout<00:01:22.880> out<00:01:23.159> to<00:01:23.479> devop<00:01:23.960> for<00:01:24.119> helping 00:01:24.429 --> 00:01:24.439 align:start position:0% big shout shout out to devop for helping 00:01:24.439 --> 00:01:26.550 align:start position:0% big shout shout out to devop for helping us<00:01:24.600> through<00:01:24.880> this<00:01:25.119> because<00:01:25.360> that<00:01:25.520> was<00:01:25.840> uh<00:01:26.400> that 00:01:26.550 --> 00:01:26.560 align:start position:0% us through this because that was uh that 00:01:26.560 --> 00:01:28.910 align:start position:0% us through this because that was uh that was<00:01:26.799> quite<00:01:27.240> uh<00:01:27.479> quite<00:01:27.720> something<00:01:28.040> and<00:01:28.320> yes<00:01:28.759> the 00:01:28.910 --> 00:01:28.920 align:start position:0% was quite uh quite something and yes the 00:01:28.920 --> 00:01:31.590 align:start position:0% was quite uh quite something and yes the elephant<00:01:29.320> has<00:01:29.479> landed<00:01:30.400> that's<00:01:30.759> uh<00:01:31.360> that's 00:01:31.590 --> 00:01:31.600 align:start position:0% elephant has landed that's uh that's 00:01:31.600 --> 00:01:33.230 align:start position:0% elephant has landed that's uh that's because<00:01:31.920> the<00:01:32.079> spirit<00:01:32.399> animal<00:01:32.799> of<00:01:33.000> the 00:01:33.230 --> 00:01:33.240 align:start position:0% because the spirit animal of the 00:01:33.240 --> 00:01:36.590 align:start position:0% because the spirit animal of the stateless<00:01:33.720> Fork<00:01:34.280> is<00:01:34.720> uh<00:01:34.880> is<00:01:35.000> the 00:01:36.590 --> 00:01:36.600 align:start position:0% stateless Fork is uh is the 00:01:36.600 --> 00:01:40.350 align:start position:0% stateless Fork is uh is the elephant<00:01:37.720> we<00:01:38.720> simplified<00:01:39.479> and<00:01:39.640> clarified<00:01:40.240> so 00:01:40.350 --> 00:01:40.360 align:start position:0% elephant we simplified and clarified so 00:01:40.360 --> 00:01:42.550 align:start position:0% elephant we simplified and clarified so there<00:01:40.479> was<00:01:40.600> a<00:01:40.960> big<00:01:41.240> work<00:01:41.640> of<00:01:42.159> uh 00:01:42.550 --> 00:01:42.560 align:start position:0% there was a big work of uh 00:01:42.560 --> 00:01:44.990 align:start position:0% there was a big work of uh simplification<00:01:43.280> clarification<00:01:44.119> of<00:01:44.320> the<00:01:44.640> gas 00:01:44.990 --> 00:01:45.000 align:start position:0% simplification clarification of the gas 00:01:45.000 --> 00:01:48.270 align:start position:0% simplification clarification of the gas cost<00:01:45.240> EIP<00:01:45.719> so<00:01:46.040> veral<00:01:46.439> is<00:01:46.560> split<00:01:46.880> into<00:01:47.119> two<00:01:47.320> eips 00:01:48.270 --> 00:01:48.280 align:start position:0% cost EIP so veral is split into two eips 00:01:48.280 --> 00:01:50.910 align:start position:0% cost EIP so veral is split into two eips one<00:01:48.439> of<00:01:48.600> them<00:01:48.799> is<00:01:49.119> 4762<00:01:49.960> the<00:01:50.119> gas<00:01:50.360> cost<00:01:50.640> they 00:01:50.910 --> 00:01:50.920 align:start position:0% one of them is 4762 the gas cost they 00:01:50.920 --> 00:01:52.910 align:start position:0% one of them is 4762 the gas cost they pertain<00:01:51.240> to<00:01:51.399> stateless<00:01:52.000> and<00:01:52.119> then<00:01:52.240> there's 00:01:52.910 --> 00:01:52.920 align:start position:0% pertain to stateless and then there's 00:01:52.920 --> 00:01:55.630 align:start position:0% pertain to stateless and then there's 6800<00:01:53.920> which<00:01:54.119> is<00:01:54.520> the<00:01:54.719> pure<00:01:55.079> description<00:01:55.520> of 00:01:55.630 --> 00:01:55.640 align:start position:0% 6800 which is the pure description of 00:01:55.640 --> 00:02:00.230 align:start position:0% 6800 which is the pure description of the<00:01:55.759> tree<00:01:56.640> um<00:01:57.399> so<00:01:58.399> you<00:01:58.520> know<00:01:58.799> we<00:01:59.280> we<00:01:59.520> had<00:01:59.960> a<00:02:00.079> lot 00:02:00.230 --> 00:02:00.240 align:start position:0% the tree um so you know we we had a lot 00:02:00.240 --> 00:02:03.469 align:start position:0% the tree um so you know we we had a lot of<00:02:00.719> questions<00:02:01.600> uh<00:02:01.840> about<00:02:02.119> it<00:02:02.719> it<00:02:02.960> caused<00:02:03.280> a<00:02:03.360> lot 00:02:03.469 --> 00:02:03.479 align:start position:0% of questions uh about it it caused a lot 00:02:03.479 --> 00:02:06.389 align:start position:0% of questions uh about it it caused a lot of<00:02:03.560> corner<00:02:04.000> cases<00:02:04.759> we<00:02:04.960> addressed<00:02:05.360> all<00:02:05.520> of<00:02:05.719> that 00:02:06.389 --> 00:02:06.399 align:start position:0% of corner cases we addressed all of that 00:02:06.399 --> 00:02:08.150 align:start position:0% of corner cases we addressed all of that uh<00:02:06.600> so<00:02:07.399> I'm<00:02:07.479> not<00:02:07.640> going<00:02:07.719> to<00:02:07.880> say<00:02:08.039> it's 00:02:08.150 --> 00:02:08.160 align:start position:0% uh so I'm not going to say it's 00:02:08.160 --> 00:02:09.869 align:start position:0% uh so I'm not going to say it's completely<00:02:08.520> ready<00:02:08.879> because<00:02:09.280> we<00:02:09.440> still<00:02:09.720> need 00:02:09.869 --> 00:02:09.879 align:start position:0% completely ready because we still need 00:02:09.879 --> 00:02:13.150 align:start position:0% completely ready because we still need to<00:02:10.440> take<00:02:10.640> into<00:02:11.000> account<00:02:11.360> eof<00:02:11.879> 7702<00:02:12.879> and<00:02:13.080> I'm 00:02:13.150 --> 00:02:13.160 align:start position:0% to take into account eof 7702 and I'm 00:02:13.160 --> 00:02:14.750 align:start position:0% to take into account eof 7702 and I'm sure<00:02:13.400> a<00:02:13.520> billion<00:02:13.879> things<00:02:14.080> that<00:02:14.239> will<00:02:14.440> come<00:02:14.640> in 00:02:14.750 --> 00:02:14.760 align:start position:0% sure a billion things that will come in 00:02:14.760 --> 00:02:18.309 align:start position:0% sure a billion things that will come in the<00:02:14.879> next<00:02:15.040> two<00:02:15.200> forks<00:02:16.200> but<00:02:17.120> um<00:02:17.840> it's<00:02:18.160> it's 00:02:18.309 --> 00:02:18.319 align:start position:0% the next two forks but um it's it's 00:02:18.319 --> 00:02:20.470 align:start position:0% the next two forks but um it's it's looking<00:02:18.680> pretty<00:02:19.040> Advanced<00:02:19.519> and<00:02:19.760> pretty 00:02:20.470 --> 00:02:20.480 align:start position:0% looking pretty Advanced and pretty 00:02:20.480 --> 00:02:22.030 align:start position:0% looking pretty Advanced and pretty mature<00:02:21.000> at<00:02:21.160> this 00:02:22.030 --> 00:02:22.040 align:start position:0% mature at this 00:02:22.040 --> 00:02:26.110 align:start position:0% mature at this point<00:02:23.040> we<00:02:23.239> also<00:02:23.920> implemented<00:02:25.000> execution<00:02:26.000> the 00:02:26.110 --> 00:02:26.120 align:start position:0% point we also implemented execution the 00:02:26.120 --> 00:02:28.550 align:start position:0% point we also implemented execution the the<00:02:26.239> execution<00:02:27.040> spec<00:02:27.400> test<00:02:27.599> framework<00:02:28.080> so 00:02:28.550 --> 00:02:28.560 align:start position:0% the execution spec test framework so 00:02:28.560 --> 00:02:30.470 align:start position:0% the execution spec test framework so until<00:02:28.879> now<00:02:29.239> when<00:02:29.360> we<00:02:29.480> wanted<00:02:29.920> to<00:02:30.040> make<00:02:30.200> sure 00:02:30.470 --> 00:02:30.480 align:start position:0% until now when we wanted to make sure 00:02:30.480 --> 00:02:32.229 align:start position:0% until now when we wanted to make sure clients<00:02:30.840> agree<00:02:31.519> that<00:02:31.640> we<00:02:31.760> don't<00:02:31.920> have<00:02:32.040> any 00:02:32.229 --> 00:02:32.239 align:start position:0% clients agree that we don't have any 00:02:32.239 --> 00:02:34.990 align:start position:0% clients agree that we don't have any consensus<00:02:32.760> bugs<00:02:33.480> we<00:02:33.640> used<00:02:33.920> to<00:02:34.480> uh<00:02:34.599> we<00:02:34.720> used<00:02:34.920> to 00:02:34.990 --> 00:02:35.000 align:start position:0% consensus bugs we used to uh we used to 00:02:35.000 --> 00:02:36.910 align:start position:0% consensus bugs we used to uh we used to launch<00:02:35.239> a<00:02:35.400> test<00:02:35.640> net<00:02:35.879> and<00:02:36.040> and<00:02:36.200> verify<00:02:36.640> but<00:02:36.760> now 00:02:36.910 --> 00:02:36.920 align:start position:0% launch a test net and and verify but now 00:02:36.920 --> 00:02:39.509 align:start position:0% launch a test net and and verify but now we<00:02:37.000> don't<00:02:37.160> even<00:02:37.400> have<00:02:37.560> to<00:02:37.879> to<00:02:38.000> do<00:02:38.200> this<00:02:38.920> uh<00:02:39.040> we 00:02:39.509 --> 00:02:39.519 align:start position:0% we don't even have to to do this uh we 00:02:39.519 --> 00:02:43.149 align:start position:0% we don't even have to to do this uh we just<00:02:40.519> have<00:02:41.280> tests<00:02:41.800> that<00:02:42.239> Target<00:02:42.599> a<00:02:42.800> specific 00:02:43.149 --> 00:02:43.159 align:start position:0% just have tests that Target a specific 00:02:43.159 --> 00:02:45.910 align:start position:0% just have tests that Target a specific use<00:02:43.560> case<00:02:44.000> so<00:02:44.360> uh<00:02:44.519> big<00:02:44.680> shout<00:02:44.920> out<00:02:45.120> to<00:02:45.360> ignasio 00:02:45.910 --> 00:02:45.920 align:start position:0% use case so uh big shout out to ignasio 00:02:45.920 --> 00:02:47.869 align:start position:0% use case so uh big shout out to ignasio and<00:02:46.120> of<00:02:46.239> course<00:02:46.400> the<00:02:46.560> testing<00:02:46.879> team<00:02:47.159> for<00:02:47.519> uh 00:02:47.869 --> 00:02:47.879 align:start position:0% and of course the testing team for uh 00:02:47.879 --> 00:02:49.670 align:start position:0% and of course the testing team for uh for<00:02:48.080> working<00:02:48.360> on<00:02:48.560> this<00:02:48.680> one<00:02:48.959> because<00:02:49.440> uh<00:02:49.560> we 00:02:49.670 --> 00:02:49.680 align:start position:0% for working on this one because uh we 00:02:49.680 --> 00:02:52.070 align:start position:0% for working on this one because uh we found<00:02:50.159> countless<00:02:50.599> bugs<00:02:51.239> before<00:02:51.560> we<00:02:51.680> even<00:02:51.920> had 00:02:52.070 --> 00:02:52.080 align:start position:0% found countless bugs before we even had 00:02:52.080 --> 00:02:55.309 align:start position:0% found countless bugs before we even had to<00:02:52.440> launch<00:02:53.440> um<00:02:53.680> so<00:02:54.319> yeah<00:02:54.519> that<00:02:54.640> was<00:02:55.040> that<00:02:55.159> was 00:02:55.309 --> 00:02:55.319 align:start position:0% to launch um so yeah that was that was 00:02:55.319 --> 00:02:58.910 align:start position:0% to launch um so yeah that was that was also<00:02:55.800> a<00:02:55.920> great<00:02:56.159> progress<00:02:56.599> this<00:02:57.000> year<00:02:58.000> and<00:02:58.159> then 00:02:58.910 --> 00:02:58.920 align:start position:0% also a great progress this year and then 00:02:58.920 --> 00:03:00.589 align:start position:0% also a great progress this year and then uh<00:02:59.040> there's<00:02:59.239> been<00:02:59.440> experiment<00:02:59.840> ments<00:03:00.120> in 00:03:00.589 --> 00:03:00.599 align:start position:0% uh there's been experiment ments in 00:03:00.599 --> 00:03:03.750 align:start position:0% uh there's been experiment ments in implementing<00:03:01.599> veral<00:03:02.000> friendly<00:03:02.360> sync<00:03:03.360> uh<00:03:03.519> so 00:03:03.750 --> 00:03:03.760 align:start position:0% implementing veral friendly sync uh so 00:03:03.760 --> 00:03:05.509 align:start position:0% implementing veral friendly sync uh so this<00:03:03.879> one<00:03:04.159> was<00:03:04.400> actually<00:03:04.680> done<00:03:05.040> by<00:03:05.200> nether 00:03:05.509 --> 00:03:05.519 align:start position:0% this one was actually done by nether 00:03:05.519 --> 00:03:08.149 align:start position:0% this one was actually done by nether Mine<00:03:05.760> by<00:03:05.879> Tanish<00:03:06.239> and<00:03:06.400> nether<00:03:06.640> mine<00:03:07.519> and<00:03:08.040> uh 00:03:08.149 --> 00:03:08.159 align:start position:0% Mine by Tanish and nether mine and uh 00:03:08.159 --> 00:03:10.430 align:start position:0% Mine by Tanish and nether mine and uh it's<00:03:08.319> the<00:03:08.519> first<00:03:09.200> feature<00:03:09.640> full<00:03:09.879> feature<00:03:10.280> that 00:03:10.430 --> 00:03:10.440 align:start position:0% it's the first feature full feature that 00:03:10.440 --> 00:03:12.589 align:start position:0% it's the first feature full feature that has<00:03:10.599> been<00:03:11.000> implemented 00:03:12.589 --> 00:03:12.599 align:start position:0% has been implemented 00:03:12.599 --> 00:03:15.070 align:start position:0% has been implemented in<00:03:13.599> that<00:03:13.720> hasn't<00:03:14.000> first<00:03:14.239> been<00:03:14.440> implemented<00:03:14.920> in 00:03:15.070 --> 00:03:15.080 align:start position:0% in that hasn't first been implemented in 00:03:15.080 --> 00:03:18.229 align:start position:0% in that hasn't first been implemented in guest<00:03:15.319> so<00:03:15.560> big<00:03:16.000> uh<00:03:16.680> big<00:03:16.920> sh<00:03:17.239> shout<00:03:17.480> out<00:03:17.760> to<00:03:18.040> to 00:03:18.229 --> 00:03:18.239 align:start position:0% guest so big uh big sh shout out to to 00:03:18.239 --> 00:03:19.430 align:start position:0% guest so big uh big sh shout out to to Tanish 00:03:19.430 --> 00:03:19.440 align:start position:0% Tanish 00:03:19.440 --> 00:03:23.070 align:start position:0% Tanish again<00:03:20.440> um<00:03:21.440> right<00:03:21.760> and<00:03:21.879> the<00:03:22.080> last<00:03:22.480> uh<00:03:22.640> the<00:03:22.799> last 00:03:23.070 --> 00:03:23.080 align:start position:0% again um right and the last uh the last 00:03:23.080 --> 00:03:25.949 align:start position:0% again um right and the last uh the last thing<00:03:23.440> that<00:03:23.799> we<00:03:24.080> achieved<00:03:24.599> last<00:03:24.840> year<00:03:25.560> was<00:03:25.799> the 00:03:25.949 --> 00:03:25.959 align:start position:0% thing that we achieved last year was the 00:03:25.959 --> 00:03:28.869 align:start position:0% thing that we achieved last year was the state<00:03:26.319> expiry<00:03:27.239> um<00:03:27.480> like<00:03:27.720> we<00:03:27.920> there<00:03:28.080> was<00:03:28.200> an<00:03:28.360> EIP 00:03:28.869 --> 00:03:28.879 align:start position:0% state expiry um like we there was an EIP 00:03:28.879 --> 00:03:31.429 align:start position:0% state expiry um like we there was an EIP that<00:03:29.040> was<00:03:29.400> uh<00:03:30.040> by<00:03:30.200> hand<00:03:30.480> he<00:03:30.599> did<00:03:30.760> a<00:03:30.959> very<00:03:31.200> good 00:03:31.429 --> 00:03:31.439 align:start position:0% that was uh by hand he did a very good 00:03:31.439 --> 00:03:33.309 align:start position:0% that was uh by hand he did a very good presentation<00:03:32.080> this<00:03:32.200> morning<00:03:32.560> about<00:03:32.760> it<00:03:32.920> so<00:03:33.120> I 00:03:33.309 --> 00:03:33.319 align:start position:0% presentation this morning about it so I 00:03:33.319 --> 00:03:35.309 align:start position:0% presentation this morning about it so I if<00:03:33.400> you<00:03:33.519> haven't<00:03:33.720> seen<00:03:33.920> it<00:03:34.080> I<00:03:34.200> suggest<00:03:34.560> you<00:03:34.760> go 00:03:35.309 --> 00:03:35.319 align:start position:0% if you haven't seen it I suggest you go 00:03:35.319 --> 00:03:37.350 align:start position:0% if you haven't seen it I suggest you go you<00:03:35.480> go<00:03:35.599> and<00:03:35.840> watch<00:03:36.040> it<00:03:36.560> but<00:03:36.799> just<00:03:36.920> to<00:03:37.120> give<00:03:37.239> you 00:03:37.350 --> 00:03:37.360 align:start position:0% you go and watch it but just to give you 00:03:37.360 --> 00:03:40.550 align:start position:0% you go and watch it but just to give you a<00:03:37.480> quick<00:03:37.799> rundown<00:03:38.799> uh<00:03:38.920> the<00:03:39.080> idea<00:03:39.360> is<00:03:39.599> that 00:03:40.550 --> 00:03:40.560 align:start position:0% a quick rundown uh the idea is that 00:03:40.560 --> 00:03:44.509 align:start position:0% a quick rundown uh the idea is that veral<00:03:41.120> veral<00:03:41.519> trees<00:03:42.360> um<00:03:42.840> are<00:03:43.519> pulling<00:03:44.040> their 00:03:44.509 --> 00:03:44.519 align:start position:0% veral veral trees um are pulling their 00:03:44.519 --> 00:03:47.470 align:start position:0% veral veral trees um are pulling their um<00:03:44.879> their<00:03:45.000> leaves<00:03:45.400> together<00:03:45.760> by<00:03:46.159> groups<00:03:46.480> of 00:03:47.470 --> 00:03:47.480 align:start position:0% um their leaves together by groups of 00:03:47.480 --> 00:03:49.949 align:start position:0% um their leaves together by groups of 256<00:03:48.480> and<00:03:48.879> then<00:03:49.040> they<00:03:49.239> have<00:03:49.439> some<00:03:49.640> kind<00:03:49.799> of 00:03:49.949 --> 00:03:49.959 align:start position:0% 256 and then they have some kind of 00:03:49.959 --> 00:03:52.789 align:start position:0% 256 and then they have some kind of extension<00:03:50.400> stem<00:03:50.760> on<00:03:50.959> top<00:03:51.120> of<00:03:51.280> it<00:03:51.879> uh<00:03:52.159> and<00:03:52.439> the 00:03:52.789 --> 00:03:52.799 align:start position:0% extension stem on top of it uh and the 00:03:52.799 --> 00:03:56.149 align:start position:0% extension stem on top of it uh and the commitment<00:03:53.799> which<00:03:53.959> commits<00:03:54.319> to<00:03:54.560> the<00:03:55.439> to<00:03:55.680> the 00:03:56.149 --> 00:03:56.159 align:start position:0% commitment which commits to the to the 00:03:56.159 --> 00:03:58.270 align:start position:0% commitment which commits to the to the the<00:03:56.360> orange<00:03:56.920> uh<00:03:57.079> to<00:03:57.360> The<00:03:57.480> Orange<00:03:57.760> Box<00:03:58.040> which<00:03:58.159> is 00:03:58.270 --> 00:03:58.280 align:start position:0% the orange uh to The Orange Box which is 00:03:58.280 --> 00:04:00.309 align:start position:0% the orange uh to The Orange Box which is the<00:03:58.400> commitment 00:04:00.309 --> 00:04:00.319 align:start position:0% the commitment 00:04:00.319 --> 00:04:03.190 align:start position:0% the commitment um<00:04:00.680> what<00:04:00.799> we<00:04:00.920> do<00:04:01.120> is<00:04:01.280> we<00:04:01.439> add<00:04:01.599> a<00:04:01.720> new<00:04:02.000> field<00:04:03.000> um 00:04:03.190 --> 00:04:03.200 align:start position:0% um what we do is we add a new field um 00:04:03.200 --> 00:04:05.309 align:start position:0% um what we do is we add a new field um that<00:04:03.319> used<00:04:03.519> to<00:04:03.640> be<00:04:03.840> zero<00:04:04.439> and<00:04:04.599> now<00:04:04.840> it's<00:04:05.120> the 00:04:05.309 --> 00:04:05.319 align:start position:0% that used to be zero and now it's the 00:04:05.319 --> 00:04:06.630 align:start position:0% that used to be zero and now it's the epoch<00:04:05.640> number<00:04:05.920> so<00:04:06.079> it's<00:04:06.239> backwards 00:04:06.630 --> 00:04:06.640 align:start position:0% epoch number so it's backwards 00:04:06.640 --> 00:04:09.470 align:start position:0% epoch number so it's backwards compatible<00:04:07.120> it's<00:04:07.280> really<00:04:07.519> good<00:04:08.519> and<00:04:09.079> uh<00:04:09.239> when 00:04:09.470 --> 00:04:09.480 align:start position:0% compatible it's really good and uh when 00:04:09.480 --> 00:04:12.670 align:start position:0% compatible it's really good and uh when you<00:04:10.000> want<00:04:10.360> to<00:04:11.280> uh<00:04:11.400> delete<00:04:11.760> some<00:04:12.040> data<00:04:12.319> you<00:04:12.480> just 00:04:12.670 --> 00:04:12.680 align:start position:0% you want to uh delete some data you just 00:04:12.680 --> 00:04:14.110 align:start position:0% you want to uh delete some data you just delete<00:04:13.079> the<00:04:13.239> whole 00:04:14.110 --> 00:04:14.120 align:start position:0% delete the whole 00:04:14.120 --> 00:04:16.789 align:start position:0% delete the whole 266<00:04:15.120> values<00:04:16.040> and<00:04:16.160> you<00:04:16.280> just<00:04:16.479> keep<00:04:16.639> the 00:04:16.789 --> 00:04:16.799 align:start position:0% 266 values and you just keep the 00:04:16.799 --> 00:04:18.390 align:start position:0% 266 values and you just keep the commitment<00:04:17.359> and<00:04:17.560> because<00:04:17.880> everything<00:04:18.239> is 00:04:18.390 --> 00:04:18.400 align:start position:0% commitment and because everything is 00:04:18.400 --> 00:04:22.830 align:start position:0% commitment and because everything is polinomial<00:04:18.959> based<00:04:19.919> you<00:04:20.120> can<00:04:20.959> re<00:04:21.959> uh<00:04:22.280> provide<00:04:22.600> a 00:04:22.830 --> 00:04:22.840 align:start position:0% polinomial based you can re uh provide a 00:04:22.840 --> 00:04:24.830 align:start position:0% polinomial based you can re uh provide a proof<00:04:23.280> of<00:04:23.600> the<00:04:23.800> entire<00:04:24.120> sub<00:04:24.360> tree<00:04:24.560> so<00:04:24.639> you<00:04:24.759> have 00:04:24.830 --> 00:04:24.840 align:start position:0% proof of the entire sub tree so you have 00:04:24.840 --> 00:04:27.430 align:start position:0% proof of the entire sub tree so you have to<00:04:25.000> resurrect<00:04:25.639> the<00:04:26.520> the<00:04:26.680> whole<00:04:26.880> sub<00:04:27.160> Tree<00:04:27.320> in 00:04:27.430 --> 00:04:27.440 align:start position:0% to resurrect the the whole sub Tree in 00:04:27.440 --> 00:04:30.830 align:start position:0% to resurrect the the whole sub Tree in one<00:04:27.680> go<00:04:28.680> but<00:04:29.280> uh<00:04:29.440> it's<00:04:29.880> great<00:04:30.199> because 00:04:30.830 --> 00:04:30.840 align:start position:0% one go but uh it's great because 00:04:30.840 --> 00:04:32.230 align:start position:0% one go but uh it's great because effectively<00:04:31.320> you<00:04:31.400> only<00:04:31.600> keep<00:04:31.800> the<00:04:31.880> internal 00:04:32.230 --> 00:04:32.240 align:start position:0% effectively you only keep the internal 00:04:32.240 --> 00:04:34.270 align:start position:0% effectively you only keep the internal nodes<00:04:33.039> and<00:04:33.199> the<00:04:33.320> internal<00:04:33.680> nodes<00:04:33.960> is<00:04:34.120> where 00:04:34.270 --> 00:04:34.280 align:start position:0% nodes and the internal nodes is where 00:04:34.280 --> 00:04:36.990 align:start position:0% nodes and the internal nodes is where veral<00:04:34.639> trees<00:04:35.199> especially<00:04:35.680> shine<00:04:36.520> this<00:04:36.680> is 00:04:36.990 --> 00:04:37.000 align:start position:0% veral trees especially shine this is 00:04:37.000 --> 00:04:39.150 align:start position:0% veral trees especially shine this is what<00:04:37.520> takes<00:04:37.840> the<00:04:37.960> less<00:04:38.199> space<00:04:38.520> in<00:04:38.639> the<00:04:38.800> whole 00:04:39.150 --> 00:04:39.160 align:start position:0% what takes the less space in the whole 00:04:39.160 --> 00:04:41.310 align:start position:0% what takes the less space in the whole in<00:04:39.240> the<00:04:39.360> whole<00:04:39.520> thing<00:04:39.720> so<00:04:40.120> it<00:04:40.240> will<00:04:40.479> provide<00:04:41.039> a 00:04:41.310 --> 00:04:41.320 align:start position:0% in the whole thing so it will provide a 00:04:41.320 --> 00:04:43.350 align:start position:0% in the whole thing so it will provide a state<00:04:41.639> expiry<00:04:42.120> scheme<00:04:42.520> that<00:04:42.639> is<00:04:42.880> efficient 00:04:43.350 --> 00:04:43.360 align:start position:0% state expiry scheme that is efficient 00:04:43.360 --> 00:04:45.150 align:start position:0% state expiry scheme that is efficient that<00:04:43.759> that<00:04:43.840> is<00:04:44.000> pretty<00:04:44.199> much<00:04:44.360> TurnKey<00:04:45.039> we 00:04:45.150 --> 00:04:45.160 align:start position:0% that that is pretty much TurnKey we 00:04:45.160 --> 00:04:47.469 align:start position:0% that that is pretty much TurnKey we could<00:04:45.360> activate<00:04:45.800> on<00:04:46.039> day<00:04:46.440> it<00:04:46.600> on<00:04:46.759> day<00:04:46.919> one<00:04:47.080> of 00:04:47.469 --> 00:04:47.479 align:start position:0% could activate on day it on day one of 00:04:47.479 --> 00:04:52.749 align:start position:0% could activate on day it on day one of veral<00:04:48.479> and<00:04:49.320> uh<00:04:49.840> and<00:04:50.039> yes<00:04:50.320> it's<00:04:50.880> uh<00:04:51.560> it's<00:04:52.520> very 00:04:52.749 --> 00:04:52.759 align:start position:0% veral and uh and yes it's uh it's very 00:04:52.759 --> 00:04:53.870 align:start position:0% veral and uh and yes it's uh it's very simple<00:04:53.039> in<00:04:53.120> the<00:04:53.240> sense<00:04:53.440> you<00:04:53.520> don't<00:04:53.720> need 00:04:53.870 --> 00:04:53.880 align:start position:0% simple in the sense you don't need 00:04:53.880 --> 00:04:55.469 align:start position:0% simple in the sense you don't need address<00:04:54.199> space<00:04:54.479> extension<00:04:55.039> you<00:04:55.120> don't<00:04:55.320> need 00:04:55.469 --> 00:04:55.479 align:start position:0% address space extension you don't need 00:04:55.479 --> 00:04:58.150 align:start position:0% address space extension you don't need to<00:04:55.600> do<00:04:55.880> any<00:04:56.840> modification<00:04:57.759> it's<00:04:57.960> really 00:04:58.150 --> 00:04:58.160 align:start position:0% to do any modification it's really 00:04:58.160 --> 00:05:00.629 align:start position:0% to do any modification it's really working<00:04:58.440> out<00:04:58.600> of<00:04:58.720> the<00:04:58.840> box 00:05:00.629 --> 00:05:00.639 align:start position:0% working out of the box 00:05:00.639 --> 00:05:02.189 align:start position:0% working out of the box so<00:05:00.800> the<00:05:00.919> conclusion<00:05:01.360> is<00:05:01.479> that<00:05:01.639> after<00:05:01.919> four 00:05:02.189 --> 00:05:02.199 align:start position:0% so the conclusion is that after four 00:05:02.199 --> 00:05:04.629 align:start position:0% so the conclusion is that after four years<00:05:02.800> uh<00:05:02.919> veral<00:05:03.400> is<00:05:03.600> pretty<00:05:03.840> much<00:05:04.280> uh<00:05:04.400> ready 00:05:04.629 --> 00:05:04.639 align:start position:0% years uh veral is pretty much uh ready 00:05:04.639 --> 00:05:07.670 align:start position:0% years uh veral is pretty much uh ready for<00:05:04.800> its<00:05:05.240> prime<00:05:06.240> um<00:05:06.440> of<00:05:06.600> course<00:05:07.039> I'm<00:05:07.160> not<00:05:07.360> going 00:05:07.670 --> 00:05:07.680 align:start position:0% for its prime um of course I'm not going 00:05:07.680 --> 00:05:09.430 align:start position:0% for its prime um of course I'm not going to<00:05:07.840> pretend<00:05:08.240> it's<00:05:08.639> uh<00:05:08.759> ready<00:05:09.000> to<00:05:09.160> ship 00:05:09.430 --> 00:05:09.440 align:start position:0% to pretend it's uh ready to ship 00:05:09.440 --> 00:05:11.029 align:start position:0% to pretend it's uh ready to ship tomorrow<00:05:09.919> we<00:05:10.039> still<00:05:10.240> have<00:05:10.400> a<00:05:10.520> couple<00:05:10.840> things 00:05:11.029 --> 00:05:11.039 align:start position:0% tomorrow we still have a couple things 00:05:11.039 --> 00:05:14.110 align:start position:0% tomorrow we still have a couple things to<00:05:11.199> do<00:05:11.800> but<00:05:11.960> I<00:05:12.120> think<00:05:12.880> um<00:05:13.160> within<00:05:13.400> a<00:05:13.600> year<00:05:13.840> we'll 00:05:14.110 --> 00:05:14.120 align:start position:0% to do but I think um within a year we'll 00:05:14.120 --> 00:05:17.189 align:start position:0% to do but I think um within a year we'll we'll<00:05:14.320> be<00:05:14.720> uh<00:05:14.880> we'll<00:05:15.080> be<00:05:15.960> you<00:05:16.080> know<00:05:16.759> a<00:05:16.880> year<00:05:17.039> of 00:05:17.189 --> 00:05:17.199 align:start position:0% we'll be uh we'll be you know a year of 00:05:17.199 --> 00:05:19.430 align:start position:0% we'll be uh we'll be you know a year of focused<00:05:17.639> work<00:05:17.919> of<00:05:18.080> course<00:05:18.800> uh<00:05:18.919> we<00:05:19.039> could<00:05:19.240> be 00:05:19.430 --> 00:05:19.440 align:start position:0% focused work of course uh we could be 00:05:19.440 --> 00:05:22.710 align:start position:0% focused work of course uh we could be ready<00:05:19.720> to<00:05:20.360> we<00:05:20.479> could<00:05:20.600> be<00:05:20.720> ready<00:05:20.960> to<00:05:21.520> ship<00:05:22.520> um 00:05:22.710 --> 00:05:22.720 align:start position:0% ready to we could be ready to ship um 00:05:22.720 --> 00:05:25.029 align:start position:0% ready to we could be ready to ship um let's<00:05:22.919> go<00:05:23.039> over<00:05:23.400> the<00:05:23.720> pros<00:05:23.919> and<00:05:24.080> cons<00:05:24.319> of<00:05:24.440> veral 00:05:25.029 --> 00:05:25.039 align:start position:0% let's go over the pros and cons of veral 00:05:25.039 --> 00:05:27.150 align:start position:0% let's go over the pros and cons of veral to<00:05:25.479> for<00:05:25.639> the<00:05:25.800> rest<00:05:25.960> of<00:05:26.080> this<00:05:26.280> discussion<00:05:27.039> the 00:05:27.150 --> 00:05:27.160 align:start position:0% to for the rest of this discussion the 00:05:27.160 --> 00:05:30.029 align:start position:0% to for the rest of this discussion the first<00:05:27.440> pro<00:05:28.160> uh<00:05:28.360> is<00:05:28.639> that<00:05:29.120> if<00:05:29.240> you<00:05:29.440> take<00:05:29.880> the 00:05:30.029 --> 00:05:30.039 align:start position:0% first pro uh is that if you take the 00:05:30.039 --> 00:05:32.150 align:start position:0% first pro uh is that if you take the veral<00:05:30.400> proof<00:05:30.680> and<00:05:30.759> the<00:05:30.880> veral<00:05:31.199> witness<00:05:32.039> this 00:05:32.150 --> 00:05:32.160 align:start position:0% veral proof and the veral witness this 00:05:32.160 --> 00:05:33.749 align:start position:0% veral proof and the veral witness this is<00:05:32.400> really<00:05:32.639> small<00:05:32.960> and<00:05:33.080> this<00:05:33.199> is<00:05:33.400> like<00:05:33.560> much 00:05:33.749 --> 00:05:33.759 align:start position:0% is really small and this is like much 00:05:33.759 --> 00:05:35.950 align:start position:0% is really small and this is like much smaller<00:05:34.160> than<00:05:34.680> anything<00:05:35.240> any<00:05:35.400> alternative 00:05:35.950 --> 00:05:35.960 align:start position:0% smaller than anything any alternative 00:05:35.960 --> 00:05:39.870 align:start position:0% smaller than anything any alternative you<00:05:36.039> can<00:05:36.240> think<00:05:36.479> of<00:05:37.360> uh<00:05:37.479> we<00:05:37.759> had<00:05:38.039> several 00:05:39.870 --> 00:05:39.880 align:start position:0% you can think of uh we had several 00:05:39.880 --> 00:05:42.469 align:start position:0% you can think of uh we had several experiments<00:05:40.880> uh<00:05:41.400> and<00:05:41.720> we<00:05:41.880> found<00:05:42.240> some 00:05:42.469 --> 00:05:42.479 align:start position:0% experiments uh and we found some 00:05:42.479 --> 00:05:44.230 align:start position:0% experiments uh and we found some encoding<00:05:43.000> that<00:05:43.120> is<00:05:43.319> especially<00:05:43.759> efficient<00:05:44.080> so 00:05:44.230 --> 00:05:44.240 align:start position:0% encoding that is especially efficient so 00:05:44.240 --> 00:05:46.749 align:start position:0% encoding that is especially efficient so it's<00:05:44.520> it's<00:05:44.639> known<00:05:44.840> as<00:05:45.039> type<00:05:45.240> three<00:05:45.520> here<00:05:46.520> um 00:05:46.749 --> 00:05:46.759 align:start position:0% it's it's known as type three here um 00:05:46.759 --> 00:05:50.510 align:start position:0% it's it's known as type three here um the<00:05:46.960> average<00:05:47.440> size<00:05:48.080> is<00:05:48.759> uh<00:05:49.000> two<00:05:49.520> like<00:05:49.680> 400<00:05:50.120> KOB 00:05:50.510 --> 00:05:50.520 align:start position:0% the average size is uh two like 400 KOB 00:05:50.520 --> 00:05:53.189 align:start position:0% the average size is uh two like 400 KOB less<00:05:50.680> than<00:05:50.800> 400<00:05:51.440> kilobytes<00:05:52.440> and<00:05:52.759> the<00:05:52.880> worst 00:05:53.189 --> 00:05:53.199 align:start position:0% less than 400 kilobytes and the worst 00:05:53.199 --> 00:05:55.110 align:start position:0% less than 400 kilobytes and the worst case<00:05:53.479> that<00:05:53.680> we<00:05:53.840> observed<00:05:54.160> so<00:05:54.520> we<00:05:54.680> replayed 00:05:55.110 --> 00:05:55.120 align:start position:0% case that we observed so we replayed 00:05:55.120 --> 00:05:57.909 align:start position:0% case that we observed so we replayed historical<00:05:55.560> blocks<00:05:56.520> uh<00:05:56.720> caveat<00:05:57.280> of<00:05:57.440> course 00:05:57.909 --> 00:05:57.919 align:start position:0% historical blocks uh caveat of course 00:05:57.919 --> 00:05:59.430 align:start position:0% historical blocks uh caveat of course they<00:05:58.080> did<00:05:58.280> not<00:05:58.639> because<00:05:58.880> they're<00:05:59.080> historical 00:05:59.430 --> 00:05:59.440 align:start position:0% they did not because they're historical 00:05:59.440 --> 00:06:00.550 align:start position:0% they did not because they're historical block<00:05:59.800> they<00:05:59.919> didn't<00:06:00.120> have<00:06:00.280> the<00:06:00.400> whole 00:06:00.550 --> 00:06:00.560 align:start position:0% block they didn't have the whole 00:06:00.560 --> 00:06:03.469 align:start position:0% block they didn't have the whole vertical<00:06:01.039> gas<00:06:01.280> cost<00:06:01.560> in<00:06:02.280> activated<00:06:02.960> but<00:06:03.319> it's 00:06:03.469 --> 00:06:03.479 align:start position:0% vertical gas cost in activated but it's 00:06:03.479 --> 00:06:07.550 align:start position:0% vertical gas cost in activated but it's still<00:06:03.680> a<00:06:03.919> very<00:06:04.160> interesting<00:06:05.120> uh<00:06:06.120> um<00:06:07.080> yeah<00:06:07.319> like 00:06:07.550 --> 00:06:07.560 align:start position:0% still a very interesting uh um yeah like 00:06:07.560 --> 00:06:09.710 align:start position:0% still a very interesting uh um yeah like reference<00:06:08.560> uh<00:06:08.720> what<00:06:08.840> we<00:06:09.000> see<00:06:09.280> is<00:06:09.440> that<00:06:09.560> the 00:06:09.710 --> 00:06:09.720 align:start position:0% reference uh what we see is that the 00:06:09.720 --> 00:06:12.070 align:start position:0% reference uh what we see is that the worst<00:06:10.000> case<00:06:10.199> is<00:06:10.360> less<00:06:10.560> than<00:06:10.680> 1<00:06:10.960> Megabyte<00:06:11.960> uh 00:06:12.070 --> 00:06:12.080 align:start position:0% worst case is less than 1 Megabyte uh 00:06:12.080 --> 00:06:13.430 align:start position:0% worst case is less than 1 Megabyte uh the<00:06:12.160> theoretical<00:06:12.680> worst<00:06:12.919> case<00:06:13.080> is<00:06:13.199> 3 00:06:13.430 --> 00:06:13.440 align:start position:0% the theoretical worst case is 3 00:06:13.440 --> 00:06:15.270 align:start position:0% the theoretical worst case is 3 megabytes<00:06:13.960> but<00:06:14.120> on<00:06:14.319> average<00:06:14.720> it's<00:06:14.960> less<00:06:15.160> than 00:06:15.270 --> 00:06:15.280 align:start position:0% megabytes but on average it's less than 00:06:15.280 --> 00:06:18.990 align:start position:0% megabytes but on average it's less than 400<00:06:16.160> uh<00:06:17.080> um<00:06:17.319> kilobytes<00:06:17.919> which<00:06:18.080> is<00:06:18.360> really<00:06:18.639> good 00:06:18.990 --> 00:06:19.000 align:start position:0% 400 uh um kilobytes which is really good 00:06:19.000 --> 00:06:21.230 align:start position:0% 400 uh um kilobytes which is really good because<00:06:19.720> you've<00:06:20.080> probably<00:06:20.400> have<00:06:20.520> heard<00:06:20.880> about 00:06:21.230 --> 00:06:21.240 align:start position:0% because you've probably have heard about 00:06:21.240 --> 00:06:23.790 align:start position:0% because you've probably have heard about increasing<00:06:21.720> the<00:06:21.880> gas<00:06:22.120> limit<00:06:22.759> uh<00:06:23.280> increasing 00:06:23.790 --> 00:06:23.800 align:start position:0% increasing the gas limit uh increasing 00:06:23.800 --> 00:06:26.510 align:start position:0% increasing the gas limit uh increasing the<00:06:23.919> blob<00:06:24.280> count<00:06:25.120> all<00:06:25.759> all<00:06:25.919> of<00:06:26.080> this<00:06:26.240> is<00:06:26.360> going 00:06:26.510 --> 00:06:26.520 align:start position:0% the blob count all all of this is going 00:06:26.520 --> 00:06:28.550 align:start position:0% the blob count all all of this is going to<00:06:26.680> have<00:06:26.800> an<00:06:26.960> impact<00:06:27.440> on<00:06:27.520> the<00:06:27.680> bandwidth<00:06:28.400> so 00:06:28.550 --> 00:06:28.560 align:start position:0% to have an impact on the bandwidth so 00:06:28.560 --> 00:06:30.189 align:start position:0% to have an impact on the bandwidth so the<00:06:28.720> fact<00:06:28.919> we<00:06:29.039> have<00:06:29.120> a<00:06:29.280> very 00:06:30.189 --> 00:06:30.199 align:start position:0% the fact we have a very 00:06:30.199 --> 00:06:32.909 align:start position:0% the fact we have a very efficient<00:06:31.199> um<00:06:31.680> proof<00:06:32.000> structure<00:06:32.479> something 00:06:32.909 --> 00:06:32.919 align:start position:0% efficient um proof structure something 00:06:32.919 --> 00:06:34.870 align:start position:0% efficient um proof structure something that<00:06:33.120> like<00:06:33.280> we<00:06:33.360> will<00:06:33.599> add<00:06:33.840> some<00:06:34.199> some<00:06:34.440> size<00:06:34.720> but 00:06:34.870 --> 00:06:34.880 align:start position:0% that like we will add some some size but 00:06:34.880 --> 00:06:37.270 align:start position:0% that like we will add some some size but adding<00:06:35.400> very<00:06:35.639> little<00:06:36.000> compared<00:06:36.360> to<00:06:36.759> any<00:06:37.080> any 00:06:37.270 --> 00:06:37.280 align:start position:0% adding very little compared to any any 00:06:37.280 --> 00:06:40.469 align:start position:0% adding very little compared to any any other<00:06:37.560> option<00:06:37.880> is<00:06:38.160> a<00:06:38.400> is<00:06:38.639> definitely<00:06:39.000> a 00:06:40.469 --> 00:06:40.479 align:start position:0% other option is a is definitely a 00:06:40.479 --> 00:06:45.230 align:start position:0% other option is a is definitely a plus<00:06:41.479> um<00:06:41.960> the<00:06:42.120> trees<00:06:42.639> itself<00:06:43.199> is<00:06:43.639> small<00:06:44.639> um<00:06:45.039> we 00:06:45.230 --> 00:06:45.240 align:start position:0% plus um the trees itself is small um we 00:06:45.240 --> 00:06:47.390 align:start position:0% plus um the trees itself is small um we it's<00:06:45.599> like<00:06:45.759> on<00:06:45.960> average<00:06:46.599> from<00:06:46.919> measurements 00:06:47.390 --> 00:06:47.400 align:start position:0% it's like on average from measurements 00:06:47.400 --> 00:06:49.430 align:start position:0% it's like on average from measurements we've<00:06:47.599> made<00:06:47.840> so<00:06:48.000> we<00:06:48.120> take<00:06:48.280> an<00:06:48.440> MPT<00:06:49.000> we<00:06:49.160> convert 00:06:49.430 --> 00:06:49.440 align:start position:0% we've made so we take an MPT we convert 00:06:49.440 --> 00:06:51.710 align:start position:0% we've made so we take an MPT we convert it<00:06:49.560> to<00:06:49.720> veral<00:06:50.120> and<00:06:50.240> we<00:06:50.360> see<00:06:50.599> what<00:06:50.800> the<00:06:51.479> end 00:06:51.710 --> 00:06:51.720 align:start position:0% it to veral and we see what the end 00:06:51.720 --> 00:06:55.230 align:start position:0% it to veral and we see what the end result<00:06:52.000> is<00:06:52.440> it's<00:06:52.599> about<00:06:52.880> 25<00:06:53.880> person<00:06:54.280> smaller 00:06:55.230 --> 00:06:55.240 align:start position:0% result is it's about 25 person smaller 00:06:55.240 --> 00:06:56.790 align:start position:0% result is it's about 25 person smaller we<00:06:55.400> have<00:06:55.639> optimizations<00:06:56.400> where<00:06:56.520> we<00:06:56.639> could 00:06:56.790 --> 00:06:56.800 align:start position:0% we have optimizations where we could 00:06:56.800 --> 00:07:02.070 align:start position:0% we have optimizations where we could shave<00:06:57.319> yet<00:06:57.599> another<00:06:58.400> 10<00:06:59.080> maybe<00:06:59.280> 10<00:06:59.840> 20<00:07:00.319> 20<00:07:01.319> gab 00:07:02.070 --> 00:07:02.080 align:start position:0% shave yet another 10 maybe 10 20 20 gab 00:07:02.080 --> 00:07:06.189 align:start position:0% shave yet another 10 maybe 10 20 20 gab still<00:07:03.080> um<00:07:03.639> but<00:07:03.800> more<00:07:04.160> importantly<00:07:05.160> it's<00:07:05.919> uh 00:07:06.189 --> 00:07:06.199 align:start position:0% still um but more importantly it's uh 00:07:06.199 --> 00:07:08.909 align:start position:0% still um but more importantly it's uh also<00:07:07.160> changing<00:07:07.680> the<00:07:07.800> way<00:07:07.960> we<00:07:08.080> store<00:07:08.400> the<00:07:08.560> data 00:07:08.909 --> 00:07:08.919 align:start position:0% also changing the way we store the data 00:07:08.919 --> 00:07:11.029 align:start position:0% also changing the way we store the data so<00:07:09.080> you<00:07:09.199> can<00:07:09.440> write<00:07:09.759> to<00:07:09.879> the<00:07:10.039> DB<00:07:10.400> DB<00:07:10.759> more 00:07:11.029 --> 00:07:11.039 align:start position:0% so you can write to the DB DB more 00:07:11.039 --> 00:07:13.230 align:start position:0% so you can write to the DB DB more efficiently<00:07:12.039> at<00:07:12.160> least<00:07:12.319> the<00:07:12.440> guest<00:07:12.720> DB<00:07:13.120> this 00:07:13.230 --> 00:07:13.240 align:start position:0% efficiently at least the guest DB this 00:07:13.240 --> 00:07:15.550 align:start position:0% efficiently at least the guest DB this is<00:07:13.400> my<00:07:13.639> my<00:07:13.919> reference<00:07:14.919> uh<00:07:15.039> so<00:07:15.240> this<00:07:15.360> is 00:07:15.550 --> 00:07:15.560 align:start position:0% is my my reference uh so this is 00:07:15.560 --> 00:07:18.390 align:start position:0% is my my reference uh so this is something<00:07:16.000> that's<00:07:16.400> very<00:07:16.639> useful<00:07:17.639> um<00:07:18.080> one<00:07:18.199> of 00:07:18.390 --> 00:07:18.400 align:start position:0% something that's very useful um one of 00:07:18.400 --> 00:07:20.749 align:start position:0% something that's very useful um one of the<00:07:19.000> really<00:07:19.360> good<00:07:19.560> things<00:07:19.840> about<00:07:20.120> verical<00:07:20.599> or 00:07:20.749 --> 00:07:20.759 align:start position:0% the really good things about verical or 00:07:20.759 --> 00:07:22.029 align:start position:0% the really good things about verical or at<00:07:20.879> least<00:07:21.080> stateless<00:07:21.560> actually<00:07:21.800> it's<00:07:21.919> not 00:07:22.029 --> 00:07:22.039 align:start position:0% at least stateless actually it's not 00:07:22.039 --> 00:07:23.710 align:start position:0% at least stateless actually it's not even<00:07:22.199> just<00:07:22.400> verle<00:07:22.840> but<00:07:22.919> you<00:07:23.039> can<00:07:23.199> immediately 00:07:23.710 --> 00:07:23.720 align:start position:0% even just verle but you can immediately 00:07:23.720 --> 00:07:26.070 align:start position:0% even just verle but you can immediately join<00:07:23.960> the<00:07:24.120> network<00:07:24.479> when<00:07:24.599> you<00:07:24.720> want<00:07:24.840> to<00:07:25.080> sync 00:07:26.070 --> 00:07:26.080 align:start position:0% join the network when you want to sync 00:07:26.080 --> 00:07:28.029 align:start position:0% join the network when you want to sync and<00:07:26.280> then<00:07:26.840> uh<00:07:26.919> you<00:07:27.039> can<00:07:27.240> download<00:07:27.639> the<00:07:27.800> data 00:07:28.029 --> 00:07:28.039 align:start position:0% and then uh you can download the data 00:07:28.039 --> 00:07:29.189 align:start position:0% and then uh you can download the data you're<00:07:28.199> missing<00:07:28.520> if<00:07:28.639> you<00:07:28.720> want<00:07:28.840> to<00:07:28.960> build<00:07:29.120> a 00:07:29.189 --> 00:07:29.199 align:start position:0% you're missing if you want to build a 00:07:29.199 --> 00:07:31.270 align:start position:0% you're missing if you want to build a full<00:07:29.840> you<00:07:29.960> can<00:07:30.160> download<00:07:30.639> the<00:07:30.840> data<00:07:31.120> you're 00:07:31.270 --> 00:07:31.280 align:start position:0% full you can download the data you're 00:07:31.280 --> 00:07:33.749 align:start position:0% full you can download the data you're missing<00:07:31.560> in<00:07:31.680> the<00:07:31.879> background<00:07:32.759> but<00:07:33.280> unlike<00:07:33.639> the 00:07:33.749 --> 00:07:33.759 align:start position:0% missing in the background but unlike the 00:07:33.759 --> 00:07:36.629 align:start position:0% missing in the background but unlike the current<00:07:34.479> uh<00:07:34.639> experience<00:07:35.160> where<00:07:35.280> you<00:07:35.639> just 00:07:36.629 --> 00:07:36.639 align:start position:0% current uh experience where you just 00:07:36.639 --> 00:07:38.510 align:start position:0% current uh experience where you just wait<00:07:37.039> for<00:07:37.240> the<00:07:37.360> blocks<00:07:37.639> to<00:07:37.759> be<00:07:37.879> downloaded<00:07:38.360> and 00:07:38.510 --> 00:07:38.520 align:start position:0% wait for the blocks to be downloaded and 00:07:38.520 --> 00:07:40.469 align:start position:0% wait for the blocks to be downloaded and then<00:07:38.680> the<00:07:38.919> state<00:07:39.479> and<00:07:39.639> then<00:07:39.800> you<00:07:39.960> hope<00:07:40.319> that 00:07:40.469 --> 00:07:40.479 align:start position:0% then the state and then you hope that 00:07:40.479 --> 00:07:42.150 align:start position:0% then the state and then you hope that you've<00:07:40.680> got<00:07:40.879> everything<00:07:41.319> in<00:07:41.520> uh<00:07:41.639> in<00:07:41.759> order<00:07:42.039> to 00:07:42.150 --> 00:07:42.160 align:start position:0% you've got everything in uh in order to 00:07:42.160 --> 00:07:44.909 align:start position:0% you've got everything in uh in order to be<00:07:42.319> able<00:07:42.560> to<00:07:43.520> to<00:07:43.680> be<00:07:43.840> able<00:07:44.080> to<00:07:44.360> to<00:07:44.520> follow<00:07:44.800> the 00:07:44.909 --> 00:07:44.919 align:start position:0% be able to to be able to to follow the 00:07:44.919 --> 00:07:46.830 align:start position:0% be able to to be able to to follow the chain<00:07:45.639> you<00:07:45.759> start<00:07:46.000> following<00:07:46.440> the<00:07:46.560> chain 00:07:46.830 --> 00:07:46.840 align:start position:0% chain you start following the chain 00:07:46.840 --> 00:07:48.830 align:start position:0% chain you start following the chain right<00:07:47.000> off<00:07:47.120> the<00:07:47.240> bat<00:07:47.520> and<00:07:47.720> only<00:07:48.039> then<00:07:48.240> do<00:07:48.400> you 00:07:48.830 --> 00:07:48.840 align:start position:0% right off the bat and only then do you 00:07:48.840 --> 00:07:50.790 align:start position:0% right off the bat and only then do you uh<00:07:49.080> do<00:07:49.199> you<00:07:49.360> worry<00:07:49.639> about<00:07:49.879> downloading<00:07:50.280> the 00:07:50.790 --> 00:07:50.800 align:start position:0% uh do you worry about downloading the 00:07:50.800 --> 00:07:53.189 align:start position:0% uh do you worry about downloading the data<00:07:51.800> um<00:07:51.919> so<00:07:52.039> if<00:07:52.120> you<00:07:52.240> want<00:07:52.360> to<00:07:52.520> compare<00:07:52.960> the 00:07:53.189 --> 00:07:53.199 align:start position:0% data um so if you want to compare the 00:07:53.199 --> 00:07:55.469 align:start position:0% data um so if you want to compare the the<00:07:53.319> idea<00:07:53.560> of<00:07:53.639> a<00:07:53.720> vertical<00:07:54.080> sync<00:07:54.879> to<00:07:55.360> the 00:07:55.469 --> 00:07:55.479 align:start position:0% the idea of a vertical sync to the 00:07:55.479 --> 00:07:57.189 align:start position:0% the idea of a vertical sync to the current<00:07:55.759> state<00:07:55.919> of<00:07:56.039> snap<00:07:56.319> sync<00:07:56.840> what<00:07:56.960> happens 00:07:57.189 --> 00:07:57.199 align:start position:0% current state of snap sync what happens 00:07:57.199 --> 00:07:58.790 align:start position:0% current state of snap sync what happens in<00:07:57.360> snap<00:07:57.680> sync<00:07:57.960> is<00:07:58.120> that<00:07:58.240> you<00:07:58.400> start 00:07:58.790 --> 00:07:58.800 align:start position:0% in snap sync is that you start 00:07:58.800 --> 00:08:02.110 align:start position:0% in snap sync is that you start downloading<00:07:59.639> the<00:07:59.840> the<00:07:59.960> state<00:08:00.520> here<00:08:01.520> uh<00:08:01.759> this 00:08:02.110 --> 00:08:02.120 align:start position:0% downloading the the state here uh this 00:08:02.120 --> 00:08:05.510 align:start position:0% downloading the the state here uh this and<00:08:02.520> uh<00:08:02.680> I'm<00:08:02.800> using<00:08:03.360> Sprouts<00:08:04.360> because<00:08:05.280> uh<00:08:05.440> I 00:08:05.510 --> 00:08:05.520 align:start position:0% and uh I'm using Sprouts because uh I 00:08:05.520 --> 00:08:07.749 align:start position:0% and uh I'm using Sprouts because uh I want<00:08:05.720> to<00:08:06.360> point<00:08:06.599> out<00:08:06.759> that<00:08:06.879> the<00:08:07.080> data<00:08:07.479> at<00:08:07.599> this 00:08:07.749 --> 00:08:07.759 align:start position:0% want to point out that the data at this 00:08:07.759 --> 00:08:09.430 align:start position:0% want to point out that the data at this stage<00:08:08.000> is<00:08:08.159> fresh<00:08:08.520> it's<00:08:08.680> the<00:08:08.800> latest<00:08:09.159> data 00:08:09.430 --> 00:08:09.440 align:start position:0% stage is fresh it's the latest data 00:08:09.440 --> 00:08:12.869 align:start position:0% stage is fresh it's the latest data you've<00:08:09.680> got<00:08:10.680> but<00:08:10.919> as<00:08:11.199> blocks<00:08:12.199> keep<00:08:12.639> being 00:08:12.869 --> 00:08:12.879 align:start position:0% you've got but as blocks keep being 00:08:12.879 --> 00:08:15.790 align:start position:0% you've got but as blocks keep being added<00:08:13.159> to<00:08:13.280> the<00:08:13.639> chain<00:08:14.639> uh<00:08:14.800> the<00:08:14.960> node<00:08:15.280> keeps 00:08:15.790 --> 00:08:15.800 align:start position:0% added to the chain uh the node keeps 00:08:15.800 --> 00:08:19.550 align:start position:0% added to the chain uh the node keeps downloading<00:08:16.440> data<00:08:17.240> but<00:08:17.440> the<00:08:17.599> old<00:08:18.400> data<00:08:19.400> uh 00:08:19.550 --> 00:08:19.560 align:start position:0% downloading data but the old data uh 00:08:19.560 --> 00:08:22.270 align:start position:0% downloading data but the old data uh like<00:08:19.720> the<00:08:19.879> data<00:08:20.120> that<00:08:20.280> was<00:08:20.960> downloaded<00:08:21.560> before 00:08:22.270 --> 00:08:22.280 align:start position:0% like the data that was downloaded before 00:08:22.280 --> 00:08:24.270 align:start position:0% like the data that was downloaded before is<00:08:22.479> actually<00:08:22.840> becoming<00:08:23.240> stale<00:08:23.720> so<00:08:23.919> this<00:08:24.039> is 00:08:24.270 --> 00:08:24.280 align:start position:0% is actually becoming stale so this is 00:08:24.280 --> 00:08:28.830 align:start position:0% is actually becoming stale so this is represented<00:08:25.039> by<00:08:25.599> um<00:08:26.280> by<00:08:26.759> uh<00:08:26.960> dried<00:08:27.639> leaves<00:08:28.639> so 00:08:28.830 --> 00:08:28.840 align:start position:0% represented by um by uh dried leaves so 00:08:28.840 --> 00:08:30.189 align:start position:0% represented by um by uh dried leaves so what<00:08:28.919> you<00:08:29.039> have<00:08:29.159> to<00:08:29.240> do 00:08:30.189 --> 00:08:30.199 align:start position:0% what you have to do 00:08:30.199 --> 00:08:32.149 align:start position:0% what you have to do is<00:08:30.400> go<00:08:30.520> to<00:08:30.680> the<00:08:30.840> network<00:08:31.240> and<00:08:31.400> ask<00:08:31.680> nodes<00:08:32.039> that 00:08:32.149 --> 00:08:32.159 align:start position:0% is go to the network and ask nodes that 00:08:32.159 --> 00:08:36.389 align:start position:0% is go to the network and ask nodes that are<00:08:32.880> synced<00:08:33.760> to<00:08:34.440> send<00:08:34.680> you<00:08:34.839> the<00:08:35.080> data<00:08:35.519> that<00:08:35.880> is 00:08:36.389 --> 00:08:36.399 align:start position:0% are synced to send you the data that is 00:08:36.399 --> 00:08:40.790 align:start position:0% are synced to send you the data that is Obsolete<00:08:37.399> and<00:08:38.399> uh<00:08:39.399> update<00:08:39.839> it<00:08:40.200> and<00:08:40.399> keep<00:08:40.560> it 00:08:40.790 --> 00:08:40.800 align:start position:0% Obsolete and uh update it and keep it 00:08:40.800 --> 00:08:43.829 align:start position:0% Obsolete and uh update it and keep it fresh<00:08:41.800> but<00:08:42.320> while<00:08:42.519> you<00:08:42.640> do<00:08:42.880> this<00:08:43.120> of<00:08:43.279> course 00:08:43.829 --> 00:08:43.839 align:start position:0% fresh but while you do this of course 00:08:43.839 --> 00:08:47.030 align:start position:0% fresh but while you do this of course the<00:08:44.000> chain<00:08:44.320> keeps<00:08:44.600> advancing<00:08:45.080> so<00:08:45.360> the<00:08:45.640> data<00:08:46.160> is 00:08:47.030 --> 00:08:47.040 align:start position:0% the chain keeps advancing so the data is 00:08:47.040 --> 00:08:48.990 align:start position:0% the chain keeps advancing so the data is some<00:08:47.360> other<00:08:47.640> part<00:08:47.800> of<00:08:47.920> the<00:08:48.080> data<00:08:48.320> is<00:08:48.480> becoming 00:08:48.990 --> 00:08:49.000 align:start position:0% some other part of the data is becoming 00:08:49.000 --> 00:08:51.190 align:start position:0% some other part of the data is becoming obsolete<00:08:50.000> and<00:08:50.200> as<00:08:50.320> a 00:08:51.190 --> 00:08:51.200 align:start position:0% obsolete and as a 00:08:51.200 --> 00:08:53.990 align:start position:0% obsolete and as a result<00:08:52.200> um<00:08:52.440> you<00:08:52.600> need<00:08:52.800> to<00:08:53.000> hope<00:08:53.279> that<00:08:53.519> this 00:08:53.990 --> 00:08:54.000 align:start position:0% result um you need to hope that this 00:08:54.000 --> 00:08:56.150 align:start position:0% result um you need to hope that this dance<00:08:54.399> and<00:08:54.600> this<00:08:54.800> communication<00:08:55.480> can<00:08:55.640> go<00:08:55.880> fast 00:08:56.150 --> 00:08:56.160 align:start position:0% dance and this communication can go fast 00:08:56.160 --> 00:08:59.110 align:start position:0% dance and this communication can go fast enough<00:08:56.720> that<00:08:56.880> you<00:08:57.000> can<00:08:57.600> uh<00:08:57.720> hope<00:08:57.920> to<00:08:58.640> sync<00:08:58.959> up 00:08:59.110 --> 00:08:59.120 align:start position:0% enough that you can uh hope to sync up 00:08:59.120 --> 00:09:00.750 align:start position:0% enough that you can uh hope to sync up to<00:08:59.320> the<00:08:59.640> uh<00:08:59.800> to<00:08:59.959> the<00:09:00.120> to<00:09:00.240> the<00:09:00.399> head<00:09:00.519> of<00:09:00.640> the 00:09:00.750 --> 00:09:00.760 align:start position:0% to the uh to the to the head of the 00:09:00.760 --> 00:09:05.269 align:start position:0% to the uh to the to the head of the chain<00:09:01.560> in<00:09:01.800> a<00:09:02.000> reasonable<00:09:02.600> time<00:09:03.560> this<00:09:04.279> uh<00:09:05.120> this 00:09:05.269 --> 00:09:05.279 align:start position:0% chain in a reasonable time this uh this 00:09:05.279 --> 00:09:07.509 align:start position:0% chain in a reasonable time this uh this is<00:09:05.440> the<00:09:05.680> problem<00:09:06.160> that<00:09:06.399> might<00:09:06.680> hit<00:09:06.880> us<00:09:07.079> at<00:09:07.240> some 00:09:07.509 --> 00:09:07.519 align:start position:0% is the problem that might hit us at some 00:09:07.519 --> 00:09:09.590 align:start position:0% is the problem that might hit us at some point<00:09:08.040> especially<00:09:08.440> if<00:09:08.560> we<00:09:08.680> stress<00:09:09.040> the<00:09:09.160> chain 00:09:09.590 --> 00:09:09.600 align:start position:0% point especially if we stress the chain 00:09:09.600 --> 00:09:12.870 align:start position:0% point especially if we stress the chain with<00:09:09.880> uh<00:09:10.399> with<00:09:10.640> increasing<00:09:11.040> the<00:09:11.200> gas<00:09:11.480> limit<00:09:12.440> um 00:09:12.870 --> 00:09:12.880 align:start position:0% with uh with increasing the gas limit um 00:09:12.880 --> 00:09:14.630 align:start position:0% with uh with increasing the gas limit um inre<00:09:13.279> like<00:09:13.560> lowering<00:09:13.920> the<00:09:14.040> block<00:09:14.320> time 00:09:14.630 --> 00:09:14.640 align:start position:0% inre like lowering the block time 00:09:14.640 --> 00:09:16.350 align:start position:0% inre like lowering the block time whatever<00:09:15.040> there's<00:09:15.240> a<00:09:15.560> few<00:09:15.800> things<00:09:16.040> that<00:09:16.160> can 00:09:16.350 --> 00:09:16.360 align:start position:0% whatever there's a few things that can 00:09:16.360 --> 00:09:18.310 align:start position:0% whatever there's a few things that can happen<00:09:16.640> that<00:09:16.760> will<00:09:16.920> make<00:09:17.120> this<00:09:17.320> even<00:09:17.680> uh<00:09:18.079> even 00:09:18.310 --> 00:09:18.320 align:start position:0% happen that will make this even uh even 00:09:18.320 --> 00:09:21.630 align:start position:0% happen that will make this even uh even more<00:09:18.720> difficult<00:09:19.560> with<00:09:19.760> vertical<00:09:20.200> sync<00:09:20.920> uh<00:09:21.120> you 00:09:21.630 --> 00:09:21.640 align:start position:0% more difficult with vertical sync uh you 00:09:21.640 --> 00:09:23.509 align:start position:0% more difficult with vertical sync uh you have<00:09:21.839> what<00:09:22.000> I<00:09:22.120> call<00:09:22.360> the<00:09:22.480> instant<00:09:22.880> heel 00:09:23.509 --> 00:09:23.519 align:start position:0% have what I call the instant heel 00:09:23.519 --> 00:09:26.509 align:start position:0% have what I call the instant heel because<00:09:24.079> the<00:09:24.560> block<00:09:25.120> contains<00:09:25.680> extra<00:09:26.079> data 00:09:26.509 --> 00:09:26.519 align:start position:0% because the block contains extra data 00:09:26.519 --> 00:09:30.710 align:start position:0% because the block contains extra data here<00:09:27.200> that<00:09:27.440> is<00:09:28.440> a<00:09:28.640> proof<00:09:29.079> that<00:09:29.680> uh<00:09:30.200> a<00:09:30.360> proof 00:09:30.710 --> 00:09:30.720 align:start position:0% here that is a proof that uh a proof 00:09:30.720 --> 00:09:33.470 align:start position:0% here that is a proof that uh a proof plus<00:09:31.240> the<00:09:31.480> the<00:09:31.800> pre-state<00:09:32.800> and<00:09:32.920> the<00:09:33.040> pre-state 00:09:33.470 --> 00:09:33.480 align:start position:0% plus the the pre-state and the pre-state 00:09:33.480 --> 00:09:34.990 align:start position:0% plus the the pre-state and the pre-state is<00:09:33.640> everything<00:09:33.959> you<00:09:34.079> need<00:09:34.279> to<00:09:34.519> execute<00:09:34.880> the 00:09:34.990 --> 00:09:35.000 align:start position:0% is everything you need to execute the 00:09:35.000 --> 00:09:37.750 align:start position:0% is everything you need to execute the block<00:09:35.720> so<00:09:36.079> as<00:09:36.240> you<00:09:36.399> download<00:09:36.800> the<00:09:37.000> data<00:09:37.600> here 00:09:37.750 --> 00:09:37.760 align:start position:0% block so as you download the data here 00:09:37.760 --> 00:09:39.389 align:start position:0% block so as you download the data here it's<00:09:37.959> sparse<00:09:38.399> but<00:09:38.519> it<00:09:38.600> could<00:09:38.760> be<00:09:38.880> linear<00:09:39.279> it 00:09:39.389 --> 00:09:39.399 align:start position:0% it's sparse but it could be linear it 00:09:39.399 --> 00:09:42.910 align:start position:0% it's sparse but it could be linear it doesn't<00:09:39.920> matter<00:09:40.920> um<00:09:41.480> you<00:09:42.360> have<00:09:42.519> the<00:09:42.640> same 00:09:42.910 --> 00:09:42.920 align:start position:0% doesn't matter um you have the same 00:09:42.920 --> 00:09:45.910 align:start position:0% doesn't matter um you have the same problem<00:09:43.200> of<00:09:43.600> what<00:09:43.760> you<00:09:44.000> have<00:09:44.399> becoming<00:09:44.920> stale 00:09:45.910 --> 00:09:45.920 align:start position:0% problem of what you have becoming stale 00:09:45.920 --> 00:09:47.870 align:start position:0% problem of what you have becoming stale but<00:09:46.120> at<00:09:46.240> the<00:09:46.399> same<00:09:46.640> time<00:09:46.920> all<00:09:47.160> the<00:09:47.519> all<00:09:47.680> the 00:09:47.870 --> 00:09:47.880 align:start position:0% but at the same time all the all the 00:09:47.880 --> 00:09:51.030 align:start position:0% but at the same time all the all the data<00:09:48.279> that<00:09:48.399> you<00:09:48.519> need<00:09:48.880> to<00:09:49.160> heal<00:09:49.800> the<00:09:50.040> the<00:09:50.720> the 00:09:51.030 --> 00:09:51.040 align:start position:0% data that you need to heal the the the 00:09:51.040 --> 00:09:53.110 align:start position:0% data that you need to heal the the the the<00:09:51.160> state<00:09:51.440> you've<00:09:51.640> got<00:09:51.920> the<00:09:52.079> the<00:09:52.160> stale<00:09:52.519> state 00:09:53.110 --> 00:09:53.120 align:start position:0% the state you've got the the stale state 00:09:53.120 --> 00:09:55.790 align:start position:0% the state you've got the the stale state is<00:09:53.519> already<00:09:54.519> uh<00:09:54.640> provided<00:09:55.040> in<00:09:55.160> the<00:09:55.279> block<00:09:55.640> so 00:09:55.790 --> 00:09:55.800 align:start position:0% is already uh provided in the block so 00:09:55.800 --> 00:09:57.269 align:start position:0% is already uh provided in the block so you<00:09:55.920> can<00:09:56.240> immediately<00:09:56.680> heal<00:09:56.920> it<00:09:57.040> you<00:09:57.120> don't 00:09:57.269 --> 00:09:57.279 align:start position:0% you can immediately heal it you don't 00:09:57.279 --> 00:09:58.870 align:start position:0% you can immediately heal it you don't have<00:09:57.399> to<00:09:57.480> go<00:09:57.640> over<00:09:58.160> the<00:09:58.279> network<00:09:58.600> so<00:09:58.760> that 00:09:58.870 --> 00:09:58.880 align:start position:0% have to go over the network so that 00:09:58.880 --> 00:10:01.350 align:start position:0% have to go over the network so that makes<00:09:59.040> for<00:09:59.160> a<00:09:59.480> much<00:10:00.000> much<00:10:00.200> faster 00:10:01.350 --> 00:10:01.360 align:start position:0% makes for a much much faster 00:10:01.360 --> 00:10:04.150 align:start position:0% makes for a much much faster sync<00:10:02.360> and<00:10:02.640> eventually<00:10:03.160> you<00:10:03.399> get<00:10:03.839> the<00:10:03.959> whole 00:10:04.150 --> 00:10:04.160 align:start position:0% sync and eventually you get the whole 00:10:04.160 --> 00:10:07.710 align:start position:0% sync and eventually you get the whole data<00:10:04.440> downloaded<00:10:05.040> and<00:10:05.279> and<00:10:05.440> that's<00:10:06.000> it<00:10:07.000> um<00:10:07.399> so 00:10:07.710 --> 00:10:07.720 align:start position:0% data downloaded and and that's it um so 00:10:07.720 --> 00:10:10.230 align:start position:0% data downloaded and and that's it um so now<00:10:08.200> let's<00:10:08.800> uh<00:10:09.079> there's<00:10:09.560> there's<00:10:09.720> a<00:10:09.920> point 00:10:10.230 --> 00:10:10.240 align:start position:0% now let's uh there's there's a point 00:10:10.240 --> 00:10:12.750 align:start position:0% now let's uh there's there's a point that<00:10:10.720> uh<00:10:11.120> veral<00:10:11.640> is<00:10:11.720> not<00:10:11.959> perfect<00:10:12.399> there's<00:10:12.600> no 00:10:12.750 --> 00:10:12.760 align:start position:0% that uh veral is not perfect there's no 00:10:12.760 --> 00:10:15.590 align:start position:0% that uh veral is not perfect there's no Quantum<00:10:13.200> resistance<00:10:14.040> especially<00:10:15.040> uh<00:10:15.240> well<00:10:15.480> in 00:10:15.590 --> 00:10:15.600 align:start position:0% Quantum resistance especially uh well in 00:10:15.600 --> 00:10:18.710 align:start position:0% Quantum resistance especially uh well in two<00:10:15.839> places<00:10:16.279> really<00:10:16.800> the<00:10:17.000> proof<00:10:17.760> computation 00:10:18.710 --> 00:10:18.720 align:start position:0% two places really the proof computation 00:10:18.720 --> 00:10:21.470 align:start position:0% two places really the proof computation and<00:10:19.279> the<00:10:20.040> uh<00:10:20.320> the<00:10:20.440> balancing<00:10:20.880> of<00:10:20.959> the<00:10:21.079> tree<00:10:21.360> you 00:10:21.470 --> 00:10:21.480 align:start position:0% and the uh the balancing of the tree you 00:10:21.480 --> 00:10:25.550 align:start position:0% and the uh the balancing of the tree you could<00:10:22.079> craft<00:10:23.079> uh<00:10:23.519> keys<00:10:24.200> that<00:10:24.839> in<00:10:25.000> such<00:10:25.160> a<00:10:25.320> way 00:10:25.550 --> 00:10:25.560 align:start position:0% could craft uh keys that in such a way 00:10:25.560 --> 00:10:27.030 align:start position:0% could craft uh keys that in such a way that<00:10:25.680> the<00:10:25.800> tree<00:10:26.079> would<00:10:26.200> be<00:10:26.320> unbalance<00:10:26.920> which 00:10:27.030 --> 00:10:27.040 align:start position:0% that the tree would be unbalance which 00:10:27.040 --> 00:10:29.310 align:start position:0% that the tree would be unbalance which is<00:10:27.240> really<00:10:27.800> computation<00:10:28.640> would<00:10:28.800> make 00:10:29.310 --> 00:10:29.320 align:start position:0% is really computation would make 00:10:29.320 --> 00:10:31.350 align:start position:0% is really computation would make recomputing<00:10:29.800> the<00:10:30.000> state<00:10:30.200> rot<00:10:30.480> computation 00:10:31.350 --> 00:10:31.360 align:start position:0% recomputing the state rot computation 00:10:31.360 --> 00:10:34.430 align:start position:0% recomputing the state rot computation intensive<00:10:32.360> um<00:10:32.680> another<00:10:33.360> issue<00:10:33.720> with<00:10:34.120> uh<00:10:34.279> with 00:10:34.430 --> 00:10:34.440 align:start position:0% intensive um another issue with uh with 00:10:34.440 --> 00:10:36.710 align:start position:0% intensive um another issue with uh with veral<00:10:34.800> trees<00:10:35.200> is<00:10:35.440> that<00:10:36.079> uh<00:10:36.320> even<00:10:36.560> though 00:10:36.710 --> 00:10:36.720 align:start position:0% veral trees is that uh even though 00:10:36.720 --> 00:10:39.230 align:start position:0% veral trees is that uh even though they've<00:10:36.880> been<00:10:37.079> designed<00:10:37.480> to<00:10:37.600> be<00:10:38.120> ZK<00:10:38.519> friendly 00:10:39.230 --> 00:10:39.240 align:start position:0% they've been designed to be ZK friendly 00:10:39.240 --> 00:10:40.870 align:start position:0% they've been designed to be ZK friendly they're<00:10:39.480> not<00:10:39.720> the<00:10:39.880> most<00:10:40.120> efficient<00:10:40.480> structure 00:10:40.870 --> 00:10:40.880 align:start position:0% they're not the most efficient structure 00:10:40.880 --> 00:10:44.790 align:start position:0% they're not the most efficient structure for<00:10:41.120> the<00:10:41.320> latest<00:10:41.800> and<00:10:42.000> greatest<00:10:42.560> of<00:10:43.040> uh<00:10:43.399> ZK<00:10:44.399> ZK 00:10:44.790 --> 00:10:44.800 align:start position:0% for the latest and greatest of uh ZK ZK 00:10:44.800 --> 00:10:47.870 align:start position:0% for the latest and greatest of uh ZK ZK technology<00:10:45.360> as<00:10:45.560> I<00:10:45.959> call<00:10:46.160> it<00:10:46.720> however<00:10:46.880> you<00:10:47.000> want 00:10:47.870 --> 00:10:47.880 align:start position:0% technology as I call it however you want 00:10:47.880 --> 00:10:49.750 align:start position:0% technology as I call it however you want um<00:10:48.040> so<00:10:48.279> there<00:10:48.399> are<00:10:48.720> potent<00:10:49.360> bunch<00:10:49.600> of 00:10:49.750 --> 00:10:49.760 align:start position:0% um so there are potent bunch of 00:10:49.760 --> 00:10:52.150 align:start position:0% um so there are potent bunch of potential<00:10:50.160> fixes<00:10:51.079> one<00:10:51.200> of<00:10:51.360> them<00:10:51.560> is<00:10:51.760> that<00:10:52.040> at 00:10:52.150 --> 00:10:52.160 align:start position:0% potential fixes one of them is that at 00:10:52.160 --> 00:10:53.910 align:start position:0% potential fixes one of them is that at least<00:10:52.320> for<00:10:52.560> the<00:10:52.839> three<00:10:53.160> and<00:10:53.320> balancing<00:10:53.800> you 00:10:53.910 --> 00:10:53.920 align:start position:0% least for the three and balancing you 00:10:53.920 --> 00:10:57.310 align:start position:0% least for the three and balancing you could<00:10:54.120> simply<00:10:54.480> use<00:10:54.959> a<00:10:55.200> regular<00:10:56.040> um<00:10:56.600> hash<00:10:57.120> and 00:10:57.310 --> 00:10:57.320 align:start position:0% could simply use a regular um hash and 00:10:57.320 --> 00:10:58.870 align:start position:0% could simply use a regular um hash and that<00:10:57.440> would<00:10:57.600> that<00:10:57.800> problem<00:10:58.040> would<00:10:58.200> be<00:10:58.320> solved 00:10:58.870 --> 00:10:58.880 align:start position:0% that would that problem would be solved 00:10:58.880 --> 00:10:59.790 align:start position:0% that would that problem would be solved it<00:10:59.000> would 00:10:59.790 --> 00:10:59.800 align:start position:0% it would 00:10:59.800 --> 00:11:03.110 align:start position:0% it would also<00:11:00.079> make<00:11:00.399> veral<00:11:01.200> uh<00:11:01.880> veral<00:11:02.279> trees<00:11:02.839> much 00:11:03.110 --> 00:11:03.120 align:start position:0% also make veral uh veral trees much 00:11:03.120 --> 00:11:06.030 align:start position:0% also make veral uh veral trees much faster<00:11:03.600> because<00:11:04.120> the<00:11:04.279> pon<00:11:04.920> hashing<00:11:05.440> is<00:11:05.720> one<00:11:05.839> of 00:11:06.030 --> 00:11:06.040 align:start position:0% faster because the pon hashing is one of 00:11:06.040 --> 00:11:09.069 align:start position:0% faster because the pon hashing is one of the<00:11:06.600> one<00:11:06.760> of<00:11:06.880> the<00:11:07.000> biggest<00:11:07.760> um<00:11:08.440> uh<00:11:08.680> waste<00:11:08.920> of 00:11:09.069 --> 00:11:09.079 align:start position:0% the one of the biggest um uh waste of 00:11:09.079 --> 00:11:11.629 align:start position:0% the one of the biggest um uh waste of time<00:11:09.720> uh<00:11:09.880> speaking<00:11:10.200> of<00:11:10.639> uh<00:11:10.839> time<00:11:11.160> I'm<00:11:11.360> getting 00:11:11.629 --> 00:11:11.639 align:start position:0% time uh speaking of uh time I'm getting 00:11:11.639 --> 00:11:13.990 align:start position:0% time uh speaking of uh time I'm getting a<00:11:11.800> bit<00:11:12.360> uh<00:11:12.720> a<00:11:12.839> bit<00:11:13.040> late<00:11:13.240> so<00:11:13.360> I'm<00:11:13.440> going<00:11:13.600> to<00:11:13.760> skip 00:11:13.990 --> 00:11:14.000 align:start position:0% a bit uh a bit late so I'm going to skip 00:11:14.000 --> 00:11:16.069 align:start position:0% a bit uh a bit late so I'm going to skip the<00:11:14.120> rest<00:11:14.240> of<00:11:14.360> this<00:11:14.519> slide<00:11:14.880> and<00:11:15.079> switch<00:11:15.680> uh<00:11:15.800> and 00:11:16.069 --> 00:11:16.079 align:start position:0% the rest of this slide and switch uh and 00:11:16.079 --> 00:11:17.870 align:start position:0% the rest of this slide and switch uh and go<00:11:16.240> on<00:11:16.440> to<00:11:16.720> to<00:11:16.920> Binary 00:11:17.870 --> 00:11:17.880 align:start position:0% go on to to Binary 00:11:17.880 --> 00:11:21.030 align:start position:0% go on to to Binary trees<00:11:18.880> so<00:11:19.160> there<00:11:19.279> are<00:11:19.440> good<00:11:19.600> things<00:11:19.880> about<00:11:20.600> um 00:11:21.030 --> 00:11:21.040 align:start position:0% trees so there are good things about um 00:11:21.040 --> 00:11:24.069 align:start position:0% trees so there are good things about um about<00:11:21.639> binary<00:11:22.040> trees<00:11:23.040> it's<00:11:23.279> Quantum<00:11:23.600> secure<00:11:24.000> I 00:11:24.069 --> 00:11:24.079 align:start position:0% about binary trees it's Quantum secure I 00:11:24.079 --> 00:11:25.750 align:start position:0% about binary trees it's Quantum secure I mean<00:11:24.320> at<00:11:24.440> least<00:11:24.639> if<00:11:24.720> you<00:11:24.839> use<00:11:25.120> the<00:11:25.320> the<00:11:25.440> correct 00:11:25.750 --> 00:11:25.760 align:start position:0% mean at least if you use the the correct 00:11:25.760 --> 00:11:28.269 align:start position:0% mean at least if you use the the correct hash<00:11:26.000> function<00:11:27.000> uh<00:11:27.120> the<00:11:27.279> hash<00:11:27.560> functions<00:11:28.000> are 00:11:28.269 --> 00:11:28.279 align:start position:0% hash function uh the hash functions are 00:11:28.279 --> 00:11:31.629 align:start position:0% hash function uh the hash functions are faster<00:11:29.480> and<00:11:29.680> it<00:11:29.839> does<00:11:30.040> play<00:11:30.320> nice<00:11:30.920> uh<00:11:31.079> with<00:11:31.480> all 00:11:31.629 --> 00:11:31.639 align:start position:0% faster and it does play nice uh with all 00:11:31.639 --> 00:11:34.990 align:start position:0% faster and it does play nice uh with all the<00:11:31.839> fancy<00:11:32.279> new<00:11:33.200> new<00:11:33.639> ZK<00:11:34.079> Tech<00:11:34.639> especially 00:11:34.990 --> 00:11:35.000 align:start position:0% the fancy new new ZK Tech especially 00:11:35.000 --> 00:11:37.949 align:start position:0% the fancy new new ZK Tech especially Starks<00:11:35.440> like<00:11:35.560> circle<00:11:36.120> circle<00:11:36.440> Starks<00:11:36.959> binus 00:11:37.949 --> 00:11:37.959 align:start position:0% Starks like circle circle Starks binus 00:11:37.959 --> 00:11:41.790 align:start position:0% Starks like circle circle Starks binus uh<00:11:38.320> whatever<00:11:39.320> the<00:11:39.440> bad<00:11:39.800> part<00:11:40.480> is<00:11:40.800> that<00:11:41.519> um 00:11:41.790 --> 00:11:41.800 align:start position:0% uh whatever the bad part is that um 00:11:41.800 --> 00:11:45.310 align:start position:0% uh whatever the bad part is that um unless<00:11:42.240> you<00:11:42.440> do<00:11:42.760> have<00:11:43.399> proper<00:11:44.399> uh<00:11:44.680> performance 00:11:45.310 --> 00:11:45.320 align:start position:0% unless you do have proper uh performance 00:11:45.320 --> 00:11:47.949 align:start position:0% unless you do have proper uh performance which<00:11:45.560> might<00:11:45.920> happen<00:11:46.519> soon<00:11:46.920> if<00:11:47.120> Poseidon<00:11:47.760> is 00:11:47.949 --> 00:11:47.959 align:start position:0% which might happen soon if Poseidon is 00:11:47.959 --> 00:11:50.150 align:start position:0% which might happen soon if Poseidon is fast<00:11:48.320> enough<00:11:48.600> for<00:11:48.800> example<00:11:49.200> but<00:11:49.360> if<00:11:49.480> it's<00:11:49.680> not 00:11:50.150 --> 00:11:50.160 align:start position:0% fast enough for example but if it's not 00:11:50.160 --> 00:11:52.190 align:start position:0% fast enough for example but if it's not we're<00:11:50.440> still<00:11:50.680> a<00:11:50.800> bit<00:11:50.959> wanting<00:11:51.519> in<00:11:51.720> in<00:11:51.880> this 00:11:52.190 --> 00:11:52.200 align:start position:0% we're still a bit wanting in in this 00:11:52.200 --> 00:11:57.389 align:start position:0% we're still a bit wanting in in this respect<00:11:53.320> um<00:11:54.519> then<00:11:55.519> uh<00:11:55.639> you<00:11:55.760> will<00:11:56.000> have<00:11:56.120> to<00:11:56.399> use 00:11:57.389 --> 00:11:57.399 align:start position:0% respect um then uh you will have to use 00:11:57.399 --> 00:12:00.710 align:start position:0% respect um then uh you will have to use binary<00:11:58.200> like<00:11:58.320> just<00:11:58.519> binary<00:11:58.839> mer<00:11:59.240> proofs<00:12:00.160> this 00:12:00.710 --> 00:12:00.720 align:start position:0% binary like just binary mer proofs this 00:12:00.720 --> 00:12:02.910 align:start position:0% binary like just binary mer proofs this is<00:12:00.959> not<00:12:01.480> very<00:12:01.800> good<00:12:02.079> because<00:12:02.360> it<00:12:02.480> will<00:12:02.680> make 00:12:02.910 --> 00:12:02.920 align:start position:0% is not very good because it will make 00:12:02.920 --> 00:12:06.150 align:start position:0% is not very good because it will make proofs<00:12:03.440> much<00:12:04.040> uh<00:12:04.200> bigger<00:12:05.200> even<00:12:05.760> if<00:12:05.880> you 00:12:06.150 --> 00:12:06.160 align:start position:0% proofs much uh bigger even if you 00:12:06.160 --> 00:12:09.910 align:start position:0% proofs much uh bigger even if you activate<00:12:07.079> uh<00:12:08.040> ZK<00:12:09.000> well<00:12:09.120> sorry<00:12:09.360> not<00:12:09.480> ZK<00:12:09.839> but 00:12:09.910 --> 00:12:09.920 align:start position:0% activate uh ZK well sorry not ZK but 00:12:09.920 --> 00:12:11.509 align:start position:0% activate uh ZK well sorry not ZK but Starks<00:12:10.279> if<00:12:10.360> you<00:12:10.480> use<00:12:10.680> binary<00:12:10.959> Tres<00:12:11.320> with 00:12:11.509 --> 00:12:11.519 align:start position:0% Starks if you use binary Tres with 00:12:11.519 --> 00:12:15.430 align:start position:0% Starks if you use binary Tres with Starks<00:12:12.519> um<00:12:12.839> what<00:12:12.959> you<00:12:13.040> will<00:12:13.279> get<00:12:13.639> is<00:12:13.800> a<00:12:14.440> um<00:12:14.839> is<00:12:14.959> a 00:12:15.430 --> 00:12:15.440 align:start position:0% Starks um what you will get is a um is a 00:12:15.440 --> 00:12:18.389 align:start position:0% Starks um what you will get is a um is a proof<00:12:15.760> plus<00:12:16.000> witness<00:12:16.920> that<00:12:17.120> is<00:12:17.800> twice<00:12:18.240> at 00:12:18.389 --> 00:12:18.399 align:start position:0% proof plus witness that is twice at 00:12:18.399 --> 00:12:21.590 align:start position:0% proof plus witness that is twice at least<00:12:19.120> uh<00:12:19.320> twice<00:12:19.720> as<00:12:20.120> big<00:12:20.480> as<00:12:20.639> the<00:12:20.760> veral<00:12:21.160> proof 00:12:21.590 --> 00:12:21.600 align:start position:0% least uh twice as big as the veral proof 00:12:21.600 --> 00:12:23.470 align:start position:0% least uh twice as big as the veral proof so<00:12:21.760> we<00:12:21.880> were<00:12:22.040> talking<00:12:22.320> about<00:12:22.560> bandwidth<00:12:23.360> this 00:12:23.470 --> 00:12:23.480 align:start position:0% so we were talking about bandwidth this 00:12:23.480 --> 00:12:24.590 align:start position:0% so we were talking about bandwidth this will<00:12:23.680> have<00:12:23.800> a<00:12:23.959> cost<00:12:24.199> like<00:12:24.320> there's<00:12:24.480> a 00:12:24.590 --> 00:12:24.600 align:start position:0% will have a cost like there's a 00:12:24.600 --> 00:12:28.110 align:start position:0% will have a cost like there's a trade-off<00:12:25.079> here<00:12:26.040> U<00:12:26.320> and<00:12:26.519> then<00:12:26.920> the<00:12:27.120> tree 00:12:28.110 --> 00:12:28.120 align:start position:0% trade-off here U and then the tree 00:12:28.120 --> 00:12:29.910 align:start position:0% trade-off here U and then the tree because<00:12:28.480> there<00:12:28.600> are<00:12:28.720> more<00:12:28.880> noes<00:12:29.519> the<00:12:29.639> tree 00:12:29.910 --> 00:12:29.920 align:start position:0% because there are more noes the tree 00:12:29.920 --> 00:12:32.470 align:start position:0% because there are more noes the tree will<00:12:30.079> be<00:12:30.240> significantly<00:12:30.920> larger<00:12:31.639> so<00:12:31.920> caveat 00:12:32.470 --> 00:12:32.480 align:start position:0% will be significantly larger so caveat 00:12:32.480 --> 00:12:34.389 align:start position:0% will be significantly larger so caveat here<00:12:32.720> we're<00:12:32.920> working<00:12:33.240> on<00:12:33.399> someon<00:12:33.839> coding<00:12:34.240> that 00:12:34.389 --> 00:12:34.399 align:start position:0% here we're working on someon coding that 00:12:34.399 --> 00:12:37.509 align:start position:0% here we're working on someon coding that might<00:12:34.639> not<00:12:35.120> make<00:12:35.320> it<00:12:35.639> it<00:12:36.360> as<00:12:36.639> true<00:12:37.000> as<00:12:37.240> what<00:12:37.399> I 00:12:37.509 --> 00:12:37.519 align:start position:0% might not make it it as true as what I 00:12:37.519 --> 00:12:39.949 align:start position:0% might not make it it as true as what I just<00:12:37.680> stated<00:12:38.199> but<00:12:38.880> this<00:12:39.000> is<00:12:39.240> like<00:12:39.399> the<00:12:39.560> current 00:12:39.949 --> 00:12:39.959 align:start position:0% just stated but this is like the current 00:12:39.959 --> 00:12:43.310 align:start position:0% just stated but this is like the current state<00:12:40.440> of<00:12:41.040> uh<00:12:41.800> yeah<00:12:41.920> the<00:12:42.079> State<00:12:42.279> ofthe<00:12:42.560> art 00:12:43.310 --> 00:12:43.320 align:start position:0% state of uh yeah the State ofthe art 00:12:43.320 --> 00:12:45.430 align:start position:0% state of uh yeah the State ofthe art that<00:12:43.519> might<00:12:43.880> I<00:12:44.040> I<00:12:44.120> might<00:12:44.279> change<00:12:44.519> my<00:12:44.680> tune<00:12:44.959> in 00:12:45.430 --> 00:12:45.440 align:start position:0% that might I I might change my tune in 00:12:45.440 --> 00:12:47.230 align:start position:0% that might I I might change my tune in in<00:12:45.560> a<00:12:45.680> week<00:12:45.880> or<00:12:46.000> two<00:12:46.240> but<00:12:46.360> currently<00:12:46.839> this<00:12:46.959> is 00:12:47.230 --> 00:12:47.240 align:start position:0% in a week or two but currently this is 00:12:47.240 --> 00:12:50.389 align:start position:0% in a week or two but currently this is this<00:12:47.360> is<00:12:47.440> a<00:12:47.880> fact<00:12:48.880> um<00:12:49.360> and<00:12:49.680> it<00:12:49.800> doesn't<00:12:50.079> solve 00:12:50.389 --> 00:12:50.399 align:start position:0% this is a fact um and it doesn't solve 00:12:50.399 --> 00:12:52.269 align:start position:0% this is a fact um and it doesn't solve the<00:12:50.560> what<00:12:50.680> I<00:12:50.839> call<00:12:51.040> the<00:12:51.160> syn<00:12:51.480> race<00:12:51.800> issue<00:12:52.120> you 00:12:52.269 --> 00:12:52.279 align:start position:0% the what I call the syn race issue you 00:12:52.279 --> 00:12:54.470 align:start position:0% the what I call the syn race issue you still<00:12:52.480> need<00:12:52.639> to<00:12:52.839> ask<00:12:53.160> someone<00:12:53.480> to<00:12:53.839> Pro<00:12:54.240> provide 00:12:54.470 --> 00:12:54.480 align:start position:0% still need to ask someone to Pro provide 00:12:54.480 --> 00:12:56.710 align:start position:0% still need to ask someone to Pro provide you<00:12:54.600> with<00:12:54.720> a<00:12:54.880> proof<00:12:55.519> maybe<00:12:55.839> a<00:12:55.959> star<00:12:56.279> proof<00:12:56.600> this 00:12:56.710 --> 00:12:56.720 align:start position:0% you with a proof maybe a star proof this 00:12:56.720 --> 00:12:58.790 align:start position:0% you with a proof maybe a star proof this is<00:12:56.959> quite<00:12:57.399> uh<00:12:57.600> computationally<00:12:58.199> intensive<00:12:58.639> to 00:12:58.790 --> 00:12:58.800 align:start position:0% is quite uh computationally intensive to 00:12:58.800 --> 00:13:01.750 align:start position:0% is quite uh computationally intensive to provide<00:12:59.199> so<00:12:59.519> the<00:12:59.720> problem<00:13:00.120> Still<00:13:00.760> Remains 00:13:01.750 --> 00:13:01.760 align:start position:0% provide so the problem Still Remains 00:13:01.760 --> 00:13:03.829 align:start position:0% provide so the problem Still Remains okay<00:13:02.399> let's<00:13:02.680> get<00:13:02.839> to<00:13:03.040> the<00:13:03.360> to<00:13:03.480> the<00:13:03.639> big 00:13:03.829 --> 00:13:03.839 align:start position:0% okay let's get to the to the big 00:13:03.839 --> 00:13:06.670 align:start position:0% okay let's get to the to the big question<00:13:04.120> should<00:13:04.320> we<00:13:04.519> skip<00:13:04.880> veral<00:13:05.880> uh<00:13:06.240> and<00:13:06.480> go 00:13:06.670 --> 00:13:06.680 align:start position:0% question should we skip veral uh and go 00:13:06.680 --> 00:13:09.590 align:start position:0% question should we skip veral uh and go straight<00:13:07.160> to<00:13:07.600> uh<00:13:07.760> binary<00:13:08.079> trees<00:13:08.920> so<00:13:09.279> that<00:13:09.399> was 00:13:09.590 --> 00:13:09.600 align:start position:0% straight to uh binary trees so that was 00:13:09.600 --> 00:13:11.150 align:start position:0% straight to uh binary trees so that was to<00:13:09.720> be<00:13:09.839> clear<00:13:10.079> that<00:13:10.199> was<00:13:10.360> already<00:13:10.760> the<00:13:11.040> that 00:13:11.150 --> 00:13:11.160 align:start position:0% to be clear that was already the that 00:13:11.160 --> 00:13:12.990 align:start position:0% to be clear that was already the that was<00:13:11.360> always<00:13:11.760> the<00:13:11.959> the<00:13:12.079> goal<00:13:12.480> right<00:13:12.839> uh 00:13:12.990 --> 00:13:13.000 align:start position:0% was always the the goal right uh 00:13:13.000 --> 00:13:14.470 align:start position:0% was always the the goal right uh vertical<00:13:13.360> trees<00:13:13.600> are<00:13:13.800> here<00:13:13.959> in<00:13:14.079> the<00:13:14.160> middle 00:13:14.470 --> 00:13:14.480 align:start position:0% vertical trees are here in the middle 00:13:14.480 --> 00:13:16.910 align:start position:0% vertical trees are here in the middle it's<00:13:14.600> the<00:13:14.800> big<00:13:15.120> uh<00:13:15.440> it's<00:13:15.600> the<00:13:15.800> big<00:13:16.279> uh<00:13:16.639> blue 00:13:16.910 --> 00:13:16.920 align:start position:0% it's the big uh it's the big uh blue 00:13:16.920 --> 00:13:20.069 align:start position:0% it's the big uh it's the big uh blue square<00:13:17.920> but<00:13:18.120> if<00:13:18.240> you<00:13:18.399> look<00:13:18.839> at<00:13:19.519> uh<00:13:19.639> later 00:13:20.069 --> 00:13:20.079 align:start position:0% square but if you look at uh later 00:13:20.079 --> 00:13:22.629 align:start position:0% square but if you look at uh later there's<00:13:20.480> Quantum<00:13:21.480> like<00:13:21.800> the<00:13:21.920> end<00:13:22.199> game<00:13:22.560> I 00:13:22.629 --> 00:13:22.639 align:start position:0% there's Quantum like the end game I 00:13:22.639 --> 00:13:27.269 align:start position:0% there's Quantum like the end game I would<00:13:22.920> call<00:13:23.920> um<00:13:24.279> is<00:13:24.560> the<00:13:24.839> Quantum<00:13:25.240> safe 00:13:27.269 --> 00:13:27.279 align:start position:0% would call um is the Quantum safe 00:13:27.279 --> 00:13:31.430 align:start position:0% would call um is the Quantum safe stocks<00:13:28.279> um<00:13:28.959> this<00:13:29.360> this<00:13:30.360> like<00:13:30.560> stepping<00:13:31.320> uh 00:13:31.430 --> 00:13:31.440 align:start position:0% stocks um this this like stepping uh 00:13:31.440 --> 00:13:34.110 align:start position:0% stocks um this this like stepping uh stepping<00:13:31.839> over<00:13:32.560> uh<00:13:32.760> veral<00:13:33.399> would<00:13:33.839> you<00:13:33.959> know 00:13:34.110 --> 00:13:34.120 align:start position:0% stepping over uh veral would you know 00:13:34.120 --> 00:13:36.310 align:start position:0% stepping over uh veral would you know has<00:13:34.320> a<00:13:34.440> few<00:13:34.680> assumptions<00:13:35.519> the<00:13:35.639> first<00:13:35.880> thing<00:13:36.120> is 00:13:36.310 --> 00:13:36.320 align:start position:0% has a few assumptions the first thing is 00:13:36.320 --> 00:13:38.870 align:start position:0% has a few assumptions the first thing is that<00:13:36.519> the<00:13:36.639> end<00:13:36.920> game<00:13:37.560> Remains<00:13:37.880> the<00:13:38.040> Same<00:13:38.639> uh<00:13:38.760> we 00:13:38.870 --> 00:13:38.880 align:start position:0% that the end game Remains the Same uh we 00:13:38.880 --> 00:13:42.590 align:start position:0% that the end game Remains the Same uh we don't<00:13:39.199> decide<00:13:39.560> to<00:13:39.880> add<00:13:40.720> more<00:13:41.720> features<00:13:42.320> or<00:13:42.519> we 00:13:42.590 --> 00:13:42.600 align:start position:0% don't decide to add more features or we 00:13:42.600 --> 00:13:44.389 align:start position:0% don't decide to add more features or we don't<00:13:42.800> decide<00:13:43.040> to<00:13:43.199> go<00:13:43.360> in<00:13:43.519> a<00:13:43.720> in<00:13:43.839> another 00:13:44.389 --> 00:13:44.399 align:start position:0% don't decide to go in a in another 00:13:44.399 --> 00:13:46.949 align:start position:0% don't decide to go in a in another Direction<00:13:45.399> um<00:13:46.120> maybe<00:13:46.360> you've<00:13:46.519> heard<00:13:46.760> about 00:13:46.949 --> 00:13:46.959 align:start position:0% Direction um maybe you've heard about 00:13:46.959 --> 00:13:49.949 align:start position:0% Direction um maybe you've heard about beam<00:13:47.199> chain<00:13:48.120> you<00:13:48.240> know<00:13:48.920> uh<00:13:49.240> there<00:13:49.399> was<00:13:49.800> a 00:13:49.949 --> 00:13:49.959 align:start position:0% beam chain you know uh there was a 00:13:49.959 --> 00:13:51.670 align:start position:0% beam chain you know uh there was a direction<00:13:50.360> that<00:13:50.519> was<00:13:50.720> given<00:13:51.079> and<00:13:51.279> all<00:13:51.399> of<00:13:51.519> a 00:13:51.670 --> 00:13:51.680 align:start position:0% direction that was given and all of a 00:13:51.680 --> 00:13:53.670 align:start position:0% direction that was given and all of a sudden<00:13:52.240> we're<00:13:52.480> talking<00:13:52.759> about<00:13:53.079> changing 00:13:53.670 --> 00:13:53.680 align:start position:0% sudden we're talking about changing 00:13:53.680 --> 00:13:55.949 align:start position:0% sudden we're talking about changing changing<00:13:54.079> directions<00:13:55.000> this<00:13:55.199> has<00:13:55.399> always<00:13:55.680> been 00:13:55.949 --> 00:13:55.959 align:start position:0% changing directions this has always been 00:13:55.959 --> 00:13:57.470 align:start position:0% changing directions this has always been the<00:13:56.160> case<00:13:56.600> in 00:13:57.470 --> 00:13:57.480 align:start position:0% the case in 00:13:57.480 --> 00:14:00.590 align:start position:0% the case in ethereum<00:13:58.480> um<00:13:58.639> since<00:13:59.240> been<00:13:59.680> uh<00:14:00.000> in<00:14:00.199> part<00:14:00.360> of<00:14:00.440> the 00:14:00.590 --> 00:14:00.600 align:start position:0% ethereum um since been uh in part of the 00:14:00.600 --> 00:14:03.470 align:start position:0% ethereum um since been uh in part of the community<00:14:01.480> so<00:14:02.120> this<00:14:02.240> is<00:14:02.480> extremely<00:14:02.959> likely 00:14:03.470 --> 00:14:03.480 align:start position:0% community so this is extremely likely 00:14:03.480 --> 00:14:06.790 align:start position:0% community so this is extremely likely that<00:14:03.720> the<00:14:03.839> end<00:14:04.040> game<00:14:04.199> will<00:14:04.519> change<00:14:05.519> um<00:14:06.000> it<00:14:06.240> also 00:14:06.790 --> 00:14:06.800 align:start position:0% that the end game will change um it also 00:14:06.800 --> 00:14:09.590 align:start position:0% that the end game will change um it also assume<00:14:07.800> that<00:14:08.199> that<00:14:08.480> the<00:14:08.600> argument<00:14:08.959> is<00:14:09.160> always 00:14:09.590 --> 00:14:09.600 align:start position:0% assume that that the argument is always 00:14:09.600 --> 00:14:11.509 align:start position:0% assume that that the argument is always well<00:14:09.839> you<00:14:09.959> know<00:14:10.320> we<00:14:10.440> will<00:14:10.639> have<00:14:10.720> to<00:14:10.839> do<00:14:11.040> two<00:14:11.360> two 00:14:11.509 --> 00:14:11.519 align:start position:0% well you know we will have to do two two 00:14:11.519 --> 00:14:13.710 align:start position:0% well you know we will have to do two two transitions<00:14:12.079> instead<00:14:12.399> of<00:14:12.560> one<00:14:13.240> this<00:14:13.360> is<00:14:13.560> the 00:14:13.710 --> 00:14:13.720 align:start position:0% transitions instead of one this is the 00:14:13.720 --> 00:14:16.389 align:start position:0% transitions instead of one this is the least<00:14:13.959> likely<00:14:14.320> to<00:14:14.440> be<00:14:14.639> true<00:14:15.560> uh<00:14:15.720> of<00:14:15.880> all<00:14:16.079> these 00:14:16.389 --> 00:14:16.399 align:start position:0% least likely to be true uh of all these 00:14:16.399 --> 00:14:19.350 align:start position:0% least likely to be true uh of all these assumptions<00:14:17.399> because<00:14:18.360> um<00:14:18.839> right<00:14:19.000> now<00:14:19.240> you 00:14:19.350 --> 00:14:19.360 align:start position:0% assumptions because um right now you 00:14:19.360 --> 00:14:21.629 align:start position:0% assumptions because um right now you want<00:14:19.560> to<00:14:19.720> have<00:14:19.880> binary<00:14:20.199> Tres<00:14:20.560> with<00:14:20.680> Starks<00:14:21.519> in 00:14:21.629 --> 00:14:21.639 align:start position:0% want to have binary Tres with Starks in 00:14:21.639 --> 00:14:23.430 align:start position:0% want to have binary Tres with Starks in the<00:14:21.800> hope<00:14:22.120> that<00:14:22.279> the<00:14:22.480> technology<00:14:23.199> that<00:14:23.320> you 00:14:23.430 --> 00:14:23.440 align:start position:0% the hope that the technology that you 00:14:23.440 --> 00:14:25.870 align:start position:0% the hope that the technology that you use<00:14:23.720> will<00:14:23.880> be<00:14:24.079> the<00:14:24.199> one<00:14:24.480> that<00:14:24.600> you<00:14:24.720> can<00:14:24.920> use<00:14:25.160> to 00:14:25.870 --> 00:14:25.880 align:start position:0% use will be the one that you can use to 00:14:25.880 --> 00:14:28.269 align:start position:0% use will be the one that you can use to um<00:14:26.240> you<00:14:26.360> know<00:14:26.560> start<00:14:27.040> the<00:14:27.199> entire<00:14:27.600> block<00:14:28.160> uh 00:14:28.269 --> 00:14:28.279 align:start position:0% um you know start the entire block uh 00:14:28.279 --> 00:14:30.230 align:start position:0% um you know start the entire block uh block<00:14:28.519> execution<00:14:29.120> not<00:14:29.279> just<00:14:29.440> the<00:14:29.600> tree<00:14:29.880> root 00:14:30.230 --> 00:14:30.240 align:start position:0% block execution not just the tree root 00:14:30.240 --> 00:14:32.430 align:start position:0% block execution not just the tree root computation<00:14:31.240> but<00:14:31.480> because<00:14:31.720> you<00:14:31.959> delivered 00:14:32.430 --> 00:14:32.440 align:start position:0% computation but because you delivered 00:14:32.440 --> 00:14:33.870 align:start position:0% computation but because you delivered this<00:14:32.560> in<00:14:32.680> two<00:14:32.920> steps<00:14:33.360> there<00:14:33.519> will<00:14:33.680> be 00:14:33.870 --> 00:14:33.880 align:start position:0% this in two steps there will be 00:14:33.880 --> 00:14:36.829 align:start position:0% this in two steps there will be something<00:14:34.199> new<00:14:34.399> coming<00:14:34.680> up<00:14:35.480> that<00:14:36.040> uh<00:14:36.199> will<00:14:36.720> you 00:14:36.829 --> 00:14:36.839 align:start position:0% something new coming up that uh will you 00:14:36.839 --> 00:14:40.230 align:start position:0% something new coming up that uh will you know<00:14:37.199> maybe<00:14:37.519> not<00:14:37.720> play<00:14:38.160> as<00:14:38.600> nicely<00:14:39.600> with<00:14:40.120> uh 00:14:40.230 --> 00:14:40.240 align:start position:0% know maybe not play as nicely with uh 00:14:40.240 --> 00:14:41.949 align:start position:0% know maybe not play as nicely with uh the<00:14:40.399> technology<00:14:40.880> you<00:14:41.040> chose<00:14:41.320> to<00:14:41.519> compute<00:14:41.839> the 00:14:41.949 --> 00:14:41.959 align:start position:0% the technology you chose to compute the 00:14:41.959 --> 00:14:45.470 align:start position:0% the technology you chose to compute the tree<00:14:42.240> rout<00:14:42.880> so<00:14:43.480> I<00:14:43.560> would<00:14:43.839> say<00:14:44.839> there's<00:14:45.079> a<00:14:45.240> big 00:14:45.470 --> 00:14:45.480 align:start position:0% tree rout so I would say there's a big 00:14:45.480 --> 00:14:49.230 align:start position:0% tree rout so I would say there's a big question<00:14:45.720> mark<00:14:46.040> here<00:14:47.000> um<00:14:47.720> and<00:14:47.920> also<00:14:48.519> what<00:14:48.720> if 00:14:49.230 --> 00:14:49.240 align:start position:0% question mark here um and also what if 00:14:49.240 --> 00:14:51.790 align:start position:0% question mark here um and also what if uh<00:14:49.399> you<00:14:49.560> could<00:14:49.800> find<00:14:50.399> and<00:14:50.959> you<00:14:51.079> know<00:14:51.399> research 00:14:51.790 --> 00:14:51.800 align:start position:0% uh you could find and you know research 00:14:51.800 --> 00:14:53.990 align:start position:0% uh you could find and you know research has<00:14:51.920> barely<00:14:52.240> started<00:14:52.600> on<00:14:52.800> this<00:14:53.079> and<00:14:53.519> not<00:14:53.720> is 00:14:53.990 --> 00:14:54.000 align:start position:0% has barely started on this and not is 00:14:54.000 --> 00:14:56.590 align:start position:0% has barely started on this and not is also<00:14:54.320> not<00:14:54.680> as<00:14:54.959> as<00:14:55.160> active<00:14:55.480> as<00:14:55.600> it<00:14:55.720> should<00:14:55.920> be 00:14:56.590 --> 00:14:56.600 align:start position:0% also not as as active as it should be 00:14:56.600 --> 00:14:58.310 align:start position:0% also not as as active as it should be but<00:14:56.800> theoretically<00:14:57.399> you<00:14:57.519> could<00:14:57.720> find<00:14:57.959> a<00:14:58.120> way 00:14:58.310 --> 00:14:58.320 align:start position:0% but theoretically you could find a way 00:14:58.320 --> 00:15:03.550 align:start position:0% but theoretically you could find a way to<00:14:58.480> do<00:14:58.680> a<00:14:58.800> z<00:14:59.040> ZK<00:14:59.959> ZK<00:15:00.320> friendly<00:15:01.240> uh<00:15:01.720> sorry<00:15:02.040> ZK<00:15:02.639> and 00:15:03.550 --> 00:15:03.560 align:start position:0% to do a z ZK ZK friendly uh sorry ZK and 00:15:03.560 --> 00:15:08.509 align:start position:0% to do a z ZK ZK friendly uh sorry ZK and uh<00:15:03.680> Quantum<00:15:04.160> resistant<00:15:05.560> u<00:15:06.560> veral<00:15:07.360> tree<00:15:08.360> it 00:15:08.509 --> 00:15:08.519 align:start position:0% uh Quantum resistant u veral tree it 00:15:08.519 --> 00:15:11.030 align:start position:0% uh Quantum resistant u veral tree it also<00:15:08.759> assume<00:15:09.160> oh<00:15:09.320> sorry<00:15:09.519> I<00:15:09.600> went<00:15:09.720> a<00:15:09.839> bit<00:15:10.040> fast 00:15:11.030 --> 00:15:11.040 align:start position:0% also assume oh sorry I went a bit fast 00:15:11.040 --> 00:15:13.550 align:start position:0% also assume oh sorry I went a bit fast uh<00:15:11.199> it<00:15:11.360> assumes<00:15:11.759> that<00:15:11.920> posidon<00:15:12.480> is<00:15:12.639> secure<00:15:13.360> uh 00:15:13.550 --> 00:15:13.560 align:start position:0% uh it assumes that posidon is secure uh 00:15:13.560 --> 00:15:15.350 align:start position:0% uh it assumes that posidon is secure uh we're<00:15:13.880> like<00:15:14.000> the<00:15:14.160> E<00:15:14.440> theum<00:15:14.720> Foundation<00:15:15.160> is 00:15:15.350 --> 00:15:15.360 align:start position:0% we're like the E theum Foundation is 00:15:15.360 --> 00:15:19.230 align:start position:0% we're like the E theum Foundation is about<00:15:15.720> to<00:15:16.160> create<00:15:17.160> a<00:15:18.040> some<00:15:18.800> some<00:15:18.959> kind<00:15:19.120> of 00:15:19.230 --> 00:15:19.240 align:start position:0% about to create a some some kind of 00:15:19.240 --> 00:15:21.189 align:start position:0% about to create a some some kind of Grant<00:15:19.560> to<00:15:19.920> try<00:15:20.079> to<00:15:20.199> break<00:15:20.480> posidon<00:15:21.040> because 00:15:21.189 --> 00:15:21.199 align:start position:0% Grant to try to break posidon because 00:15:21.199 --> 00:15:23.269 align:start position:0% Grant to try to break posidon because posidon<00:15:21.720> did<00:15:21.839> not<00:15:22.079> get<00:15:22.399> enough 00:15:23.269 --> 00:15:23.279 align:start position:0% posidon did not get enough 00:15:23.279 --> 00:15:27.030 align:start position:0% posidon did not get enough scrutiny<00:15:24.279> um<00:15:24.759> and<00:15:25.240> then<00:15:25.920> uh<00:15:26.440> also<00:15:26.720> there's<00:15:26.880> a 00:15:27.030 --> 00:15:27.040 align:start position:0% scrutiny um and then uh also there's a 00:15:27.040 --> 00:15:28.629 align:start position:0% scrutiny um and then uh also there's a big<00:15:27.240> question<00:15:27.560> of<00:15:27.759> whether<00:15:27.920> or<00:15:28.079> not<00:15:28.279> we<00:15:28.440> want 00:15:28.629 --> 00:15:28.639 align:start position:0% big question of whether or not we want 00:15:28.639 --> 00:15:31.470 align:start position:0% big question of whether or not we want to<00:15:29.000> be<00:15:29.120> able<00:15:30.000> uh<00:15:30.360> or<00:15:30.639> what<00:15:30.759> do<00:15:30.880> we<00:15:31.040> do<00:15:31.279> for 00:15:31.470 --> 00:15:31.480 align:start position:0% to be able uh or what do we do for 00:15:31.480 --> 00:15:35.150 align:start position:0% to be able uh or what do we do for example<00:15:31.959> if<00:15:32.440> uh<00:15:32.680> producing<00:15:33.399> a<00:15:34.000> stark<00:15:34.440> proof<00:15:34.759> in 00:15:35.150 --> 00:15:35.160 align:start position:0% example if uh producing a stark proof in 00:15:35.160 --> 00:15:36.990 align:start position:0% example if uh producing a stark proof in in<00:15:35.279> an<00:15:35.519> acceptable<00:15:35.959> time<00:15:36.160> can<00:15:36.319> only<00:15:36.600> be<00:15:36.720> done 00:15:36.990 --> 00:15:37.000 align:start position:0% in an acceptable time can only be done 00:15:37.000 --> 00:15:38.150 align:start position:0% in an acceptable time can only be done in<00:15:37.160> Big<00:15:37.360> Data 00:15:38.150 --> 00:15:38.160 align:start position:0% in Big Data 00:15:38.160 --> 00:15:42.030 align:start position:0% in Big Data Centers<00:15:39.160> um<00:15:40.120> can<00:15:40.600> uh<00:15:40.720> do<00:15:40.920> we<00:15:41.319> you<00:15:41.440> know<00:15:41.600> do<00:15:41.759> we 00:15:42.030 --> 00:15:42.040 align:start position:0% Centers um can uh do we you know do we 00:15:42.040 --> 00:15:44.949 align:start position:0% Centers um can uh do we you know do we turn<00:15:42.279> our<00:15:42.480> backs<00:15:42.759> on<00:15:43.040> the<00:15:43.399> ethereum<00:15:43.920> itos<00:15:44.480> of 00:15:44.949 --> 00:15:44.959 align:start position:0% turn our backs on the ethereum itos of 00:15:44.959 --> 00:15:48.269 align:start position:0% turn our backs on the ethereum itos of of<00:15:45.360> solo<00:15:45.880> building<00:15:46.319> solo<00:15:47.160> blog<00:15:47.800> building<00:15:48.160> and 00:15:48.269 --> 00:15:48.279 align:start position:0% of solo building solo blog building and 00:15:48.279 --> 00:15:49.389 align:start position:0% of solo building solo blog building and solo<00:15:48.600> blog 00:15:49.389 --> 00:15:49.399 align:start position:0% solo blog 00:15:49.399 --> 00:15:51.949 align:start position:0% solo blog proving<00:15:50.399> um<00:15:51.000> this<00:15:51.120> is<00:15:51.240> a<00:15:51.399> big<00:15:51.560> question<00:15:51.800> to 00:15:51.949 --> 00:15:51.959 align:start position:0% proving um this is a big question to 00:15:51.959 --> 00:15:54.430 align:start position:0% proving um this is a big question to have<00:15:52.120> so<00:15:52.240> there's<00:15:52.440> a<00:15:52.560> lot<00:15:52.680> of<00:15:53.440> political 00:15:54.430 --> 00:15:54.440 align:start position:0% have so there's a lot of political 00:15:54.440 --> 00:15:56.189 align:start position:0% have so there's a lot of political there's<00:15:54.639> also<00:15:54.839> a<00:15:54.959> political<00:15:55.399> dimension<00:15:55.800> for 00:15:56.189 --> 00:15:56.199 align:start position:0% there's also a political dimension for 00:15:56.199 --> 00:16:00.269 align:start position:0% there's also a political dimension for this<00:15:57.199> um<00:15:58.000> and<00:15:58.199> then<00:15:58.560> yeah<00:15:58.720> like<00:15:59.120> I<00:15:59.319> was<00:15:59.839> uh<00:16:00.199> I 00:16:00.269 --> 00:16:00.279 align:start position:0% this um and then yeah like I was uh I 00:16:00.279 --> 00:16:02.350 align:start position:0% this um and then yeah like I was uh I mean<00:16:00.480> like<00:16:00.600> I<00:16:00.720> revealed<00:16:01.199> before<00:16:01.959> uh<00:16:02.120> there's 00:16:02.350 --> 00:16:02.360 align:start position:0% mean like I revealed before uh there's 00:16:02.360 --> 00:16:05.590 align:start position:0% mean like I revealed before uh there's also<00:16:02.720> the<00:16:03.160> like<00:16:03.480> this<00:16:03.639> tweet<00:16:03.959> proves<00:16:04.600> that 00:16:05.590 --> 00:16:05.600 align:start position:0% also the like this tweet proves that 00:16:05.600 --> 00:16:08.509 align:start position:0% also the like this tweet proves that there's<00:16:05.800> a<00:16:06.000> lot<00:16:06.199> of<00:16:06.800> um<00:16:07.360> innovation<00:16:07.880> in<00:16:08.040> ZK 00:16:08.509 --> 00:16:08.519 align:start position:0% there's a lot of um innovation in ZK 00:16:08.519 --> 00:16:13.150 align:start position:0% there's a lot of um innovation in ZK right<00:16:08.680> now<00:16:09.560> the<00:16:10.120> the<00:16:10.240> one<00:16:11.120> um<00:16:12.120> the<00:16:12.560> or<00:16:12.720> at<00:16:12.800> least 00:16:13.150 --> 00:16:13.160 align:start position:0% right now the the one um the or at least 00:16:13.160 --> 00:16:16.189 align:start position:0% right now the the one um the or at least tree<00:16:13.440> proving<00:16:13.759> State<00:16:14.240> proving<00:16:15.240> uh<00:16:15.639> the<00:16:15.800> one 00:16:16.189 --> 00:16:16.199 align:start position:0% tree proving State proving uh the one 00:16:16.199 --> 00:16:17.670 align:start position:0% tree proving State proving uh the one technology<00:16:16.680> that<00:16:16.800> we're<00:16:17.000> talking<00:16:17.319> about 00:16:17.670 --> 00:16:17.680 align:start position:0% technology that we're talking about 00:16:17.680 --> 00:16:20.230 align:start position:0% technology that we're talking about right<00:16:17.839> now<00:16:18.000> will<00:16:18.160> be<00:16:18.319> obsolete<00:16:18.759> in<00:16:18.920> six<00:16:19.240> months 00:16:20.230 --> 00:16:20.240 align:start position:0% right now will be obsolete in six months 00:16:20.240 --> 00:16:23.910 align:start position:0% right now will be obsolete in six months um<00:16:20.560> so<00:16:21.240> it<00:16:21.480> might<00:16:21.720> make<00:16:22.000> sense<00:16:22.319> to<00:16:22.959> just<00:16:23.720> take 00:16:23.910 --> 00:16:23.920 align:start position:0% um so it might make sense to just take 00:16:23.920 --> 00:16:28.910 align:start position:0% um so it might make sense to just take it<00:16:24.160> easy<00:16:24.759> wait<00:16:25.000> for<00:16:25.440> this<00:16:26.040> um<00:16:26.480> frenzy<00:16:27.199> to<00:16:28.120> to 00:16:28.910 --> 00:16:28.920 align:start position:0% it easy wait for this um frenzy to to 00:16:28.920 --> 00:16:32.470 align:start position:0% it easy wait for this um frenzy to to stabilize<00:16:29.399> a<00:16:29.560> bit<00:16:30.360> and<00:16:30.600> then<00:16:31.199> uh<00:16:31.519> make<00:16:31.720> the 00:16:32.470 --> 00:16:32.480 align:start position:0% stabilize a bit and then uh make the 00:16:32.480 --> 00:16:35.990 align:start position:0% stabilize a bit and then uh make the decision<00:16:33.480> um<00:16:34.360> and<00:16:34.839> uh<00:16:35.079> yes<00:16:35.319> well<00:16:35.519> there's<00:16:35.920> of 00:16:35.990 --> 00:16:36.000 align:start position:0% decision um and uh yes well there's of 00:16:36.000 --> 00:16:37.670 align:start position:0% decision um and uh yes well there's of course<00:16:36.199> the<00:16:36.319> quantum<00:16:36.680> Computing<00:16:37.120> risk 00:16:37.670 --> 00:16:37.680 align:start position:0% course the quantum Computing risk 00:16:37.680 --> 00:16:39.230 align:start position:0% course the quantum Computing risk there's<00:16:37.880> a<00:16:38.040> lot<00:16:38.279> there<00:16:38.399> seems<00:16:38.639> to<00:16:38.759> be<00:16:38.920> a<00:16:39.120> kind 00:16:39.230 --> 00:16:39.240 align:start position:0% there's a lot there seems to be a kind 00:16:39.240 --> 00:16:41.389 align:start position:0% there's a lot there seems to be a kind of<00:16:39.319> a<00:16:39.440> moral<00:16:39.800> Panic<00:16:40.199> right<00:16:40.360> now<00:16:40.639> about<00:16:40.959> Quantum 00:16:41.389 --> 00:16:41.399 align:start position:0% of a moral Panic right now about Quantum 00:16:41.399 --> 00:16:43.990 align:start position:0% of a moral Panic right now about Quantum Computing<00:16:42.360> I<00:16:42.519> am<00:16:43.000> a<00:16:43.240> skeptic<00:16:43.680> I'm<00:16:43.800> not<00:16:43.920> going 00:16:43.990 --> 00:16:44.000 align:start position:0% Computing I am a skeptic I'm not going 00:16:44.000 --> 00:16:46.670 align:start position:0% Computing I am a skeptic I'm not going to<00:16:44.160> hide<00:16:44.440> this<00:16:44.680> but<00:16:45.440> uh<00:16:45.639> yeah<00:16:45.839> there's<00:16:46.040> a<00:16:46.560> like 00:16:46.670 --> 00:16:46.680 align:start position:0% to hide this but uh yeah there's a like 00:16:46.680 --> 00:16:48.309 align:start position:0% to hide this but uh yeah there's a like your<00:16:46.880> guess<00:16:47.079> is<00:16:47.199> as<00:16:47.360> good<00:16:47.560> as<00:16:47.720> mine<00:16:47.959> should<00:16:48.120> we 00:16:48.309 --> 00:16:48.319 align:start position:0% your guess is as good as mine should we 00:16:48.319 --> 00:16:50.230 align:start position:0% your guess is as good as mine should we Panic<00:16:48.639> about<00:16:48.920> something<00:16:49.240> that<00:16:49.360> should<00:16:49.839> that 00:16:50.230 --> 00:16:50.240 align:start position:0% Panic about something that should that 00:16:50.240 --> 00:16:53.710 align:start position:0% Panic about something that should that might<00:16:50.519> not<00:16:51.000> ever<00:16:51.519> exist<00:16:52.519> um<00:16:53.120> yeah<00:16:53.360> we<00:16:53.480> don't 00:16:53.710 --> 00:16:53.720 align:start position:0% might not ever exist um yeah we don't 00:16:53.720 --> 00:16:56.150 align:start position:0% might not ever exist um yeah we don't really<00:16:54.240> understand<00:16:54.800> uh<00:16:54.920> decoherence<00:16:55.839> is<00:16:55.920> it 00:16:56.150 --> 00:16:56.160 align:start position:0% really understand uh decoherence is it 00:16:56.160 --> 00:16:59.269 align:start position:0% really understand uh decoherence is it possible<00:16:56.600> to<00:16:57.600> count<00:16:58.079> to<00:16:58.240> have<00:16:58.399> as<00:16:58.480> many<00:16:58.880> Q<00:16:59.040> bits 00:16:59.269 --> 00:16:59.279 align:start position:0% possible to count to have as many Q bits 00:16:59.279 --> 00:17:02.230 align:start position:0% possible to count to have as many Q bits as<00:16:59.600> uh<00:17:00.519> as<00:17:00.800> we<00:17:01.199> uh<00:17:01.360> as<00:17:01.480> would<00:17:01.639> be<00:17:01.759> needed<00:17:02.079> to 00:17:02.230 --> 00:17:02.240 align:start position:0% as uh as we uh as would be needed to 00:17:02.240 --> 00:17:05.470 align:start position:0% as uh as we uh as would be needed to break<00:17:02.680> uh<00:17:02.759> to<00:17:02.959> Break<00:17:03.600> um<00:17:04.280> uh<00:17:04.640> to<00:17:04.760> fake<00:17:05.000> a<00:17:05.120> veral 00:17:05.470 --> 00:17:05.480 align:start position:0% break uh to Break um uh to fake a veral 00:17:05.480 --> 00:17:07.909 align:start position:0% break uh to Break um uh to fake a veral proof<00:17:06.039> well<00:17:06.319> I<00:17:06.400> don't<00:17:06.559> know<00:17:06.720> the<00:17:06.880> future<00:17:07.760> will 00:17:07.909 --> 00:17:07.919 align:start position:0% proof well I don't know the future will 00:17:07.919 --> 00:17:09.110 align:start position:0% proof well I don't know the future will tell 00:17:09.110 --> 00:17:09.120 align:start position:0% tell 00:17:09.120 --> 00:17:12.150 align:start position:0% tell us<00:17:10.120> um<00:17:10.480> so<00:17:10.880> yeah<00:17:11.280> like<00:17:11.559> the<00:17:11.720> one<00:17:11.839> of<00:17:11.959> the 00:17:12.150 --> 00:17:12.160 align:start position:0% us um so yeah like the one of the 00:17:12.160 --> 00:17:14.350 align:start position:0% us um so yeah like the one of the problems<00:17:12.520> also<00:17:12.880> with<00:17:13.520> this<00:17:13.720> question<00:17:14.039> of 00:17:14.350 --> 00:17:14.360 align:start position:0% problems also with this question of 00:17:14.360 --> 00:17:17.390 align:start position:0% problems also with this question of skipping<00:17:14.720> verle<00:17:15.199> is<00:17:15.720> you<00:17:15.880> are<00:17:16.559> uh<00:17:16.720> effectively 00:17:17.390 --> 00:17:17.400 align:start position:0% skipping verle is you are uh effectively 00:17:17.400 --> 00:17:19.429 align:start position:0% skipping verle is you are uh effectively comparing<00:17:17.880> something<00:17:18.280> that<00:17:18.439> is<00:17:18.959> ready<00:17:19.240> to 00:17:19.429 --> 00:17:19.439 align:start position:0% comparing something that is ready to 00:17:19.439 --> 00:17:22.789 align:start position:0% comparing something that is ready to ship<00:17:20.160> quasy<00:17:20.600> ready<00:17:20.959> ready<00:17:21.160> to<00:17:21.319> ship<00:17:22.240> with 00:17:22.789 --> 00:17:22.799 align:start position:0% ship quasy ready ready to ship with 00:17:22.799 --> 00:17:24.829 align:start position:0% ship quasy ready ready to ship with something<00:17:23.559> that<00:17:23.720> is<00:17:24.000> quite<00:17:24.240> undefined<00:17:24.720> so 00:17:24.829 --> 00:17:24.839 align:start position:0% something that is quite undefined so 00:17:24.839 --> 00:17:27.990 align:start position:0% something that is quite undefined so there's<00:17:25.120> still<00:17:25.480> a<00:17:26.039> huge<00:17:27.039> uh<00:17:27.360> specification 00:17:27.990 --> 00:17:28.000 align:start position:0% there's still a huge uh specification 00:17:28.000 --> 00:17:29.430 align:start position:0% there's still a huge uh specification work<00:17:28.240> that<00:17:28.360> needs<00:17:28.520> to<00:17:28.600> be<00:17:28.720> done<00:17:28.919> done<00:17:29.080> and<00:17:29.280> has 00:17:29.430 --> 00:17:29.440 align:start position:0% work that needs to be done done and has 00:17:29.440 --> 00:17:31.549 align:start position:0% work that needs to be done done and has barely<00:17:29.760> started<00:17:30.720> we<00:17:30.840> don't<00:17:31.039> know<00:17:31.280> what<00:17:31.400> the 00:17:31.549 --> 00:17:31.559 align:start position:0% barely started we don't know what the 00:17:31.559 --> 00:17:33.590 align:start position:0% barely started we don't know what the exact<00:17:31.840> structure<00:17:32.160> of<00:17:32.280> the<00:17:32.760> binary<00:17:33.120> tree<00:17:33.400> would 00:17:33.590 --> 00:17:33.600 align:start position:0% exact structure of the binary tree would 00:17:33.600 --> 00:17:36.110 align:start position:0% exact structure of the binary tree would be<00:17:34.360> uh<00:17:34.480> we<00:17:34.600> don't<00:17:34.799> know<00:17:35.440> what<00:17:35.600> the<00:17:35.720> witness 00:17:36.110 --> 00:17:36.120 align:start position:0% be uh we don't know what the witness 00:17:36.120 --> 00:17:38.110 align:start position:0% be uh we don't know what the witness would<00:17:36.280> look<00:17:36.520> like<00:17:36.760> does<00:17:37.000> it<00:17:37.200> contain<00:17:37.840> uh<00:17:37.960> does 00:17:38.110 --> 00:17:38.120 align:start position:0% would look like does it contain uh does 00:17:38.120 --> 00:17:41.669 align:start position:0% would look like does it contain uh does it<00:17:38.320> contain<00:17:39.080> uh<00:17:39.520> all<00:17:39.799> the<00:17:40.000> state<00:17:40.360> diffs<00:17:41.200> um 00:17:41.669 --> 00:17:41.679 align:start position:0% it contain uh all the state diffs um 00:17:41.679 --> 00:17:44.029 align:start position:0% it contain uh all the state diffs um this<00:17:41.799> is<00:17:41.919> being<00:17:42.160> answered<00:17:42.919> as<00:17:43.360> uh<00:17:43.559> but<00:17:43.799> maybe 00:17:44.029 --> 00:17:44.039 align:start position:0% this is being answered as uh but maybe 00:17:44.039 --> 00:17:46.070 align:start position:0% this is being answered as uh but maybe not<00:17:44.200> as<00:17:44.360> we<00:17:44.520> speak<00:17:44.880> but<00:17:45.120> this<00:17:45.240> is<00:17:45.799> this<00:17:45.919> is 00:17:46.070 --> 00:17:46.080 align:start position:0% not as we speak but this is this is 00:17:46.080 --> 00:17:48.230 align:start position:0% not as we speak but this is this is being<00:17:46.440> answer<00:17:46.880> debated<00:17:47.440> and<00:17:47.720> we<00:17:47.880> we<00:17:48.000> need<00:17:48.120> to 00:17:48.230 --> 00:17:48.240 align:start position:0% being answer debated and we we need to 00:17:48.240 --> 00:17:51.029 align:start position:0% being answer debated and we we need to reach<00:17:48.440> a<00:17:48.600> conclusion<00:17:49.039> but<00:17:49.200> we<00:17:49.320> haven't<00:17:49.640> so<00:17:50.039> far 00:17:51.029 --> 00:17:51.039 align:start position:0% reach a conclusion but we haven't so far 00:17:51.039 --> 00:17:54.270 align:start position:0% reach a conclusion but we haven't so far um<00:17:51.840> is<00:17:52.080> posidon<00:17:52.720> secure<00:17:53.160> if<00:17:53.520> Poseidon<00:17:54.000> is<00:17:54.120> not 00:17:54.270 --> 00:17:54.280 align:start position:0% um is posidon secure if Poseidon is not 00:17:54.280 --> 00:17:57.190 align:start position:0% um is posidon secure if Poseidon is not secure<00:17:54.760> well<00:17:54.919> we<00:17:55.039> need<00:17:55.200> to<00:17:55.360> go<00:17:55.520> to<00:17:55.679> chatau<00:17:56.200> 56 00:17:57.190 --> 00:17:57.200 align:start position:0% secure well we need to go to chatau 56 00:17:57.200 --> 00:17:59.470 align:start position:0% secure well we need to go to chatau 56 this<00:17:57.320> is<00:17:57.520> much<00:17:57.720> harder<00:17:58.000> to<00:17:58.200> prove<00:17:58.720> uh<00:17:59.120> in<00:17:59.240> a<00:17:59.400> in 00:17:59.470 --> 00:17:59.480 align:start position:0% this is much harder to prove uh in a in 00:17:59.480 --> 00:18:02.470 align:start position:0% this is much harder to prove uh in a in a<00:17:59.640> circuit<00:18:00.640> uh<00:18:00.799> which<00:18:01.600> proving<00:18:02.000> system<00:18:02.360> this 00:18:02.470 --> 00:18:02.480 align:start position:0% a circuit uh which proving system this 00:18:02.480 --> 00:18:04.909 align:start position:0% a circuit uh which proving system this is<00:18:02.640> what<00:18:02.760> I<00:18:02.880> was<00:18:03.039> saying<00:18:03.320> before<00:18:04.080> we<00:18:04.240> need<00:18:04.440> to 00:18:04.909 --> 00:18:04.919 align:start position:0% is what I was saying before we need to 00:18:04.919 --> 00:18:08.029 align:start position:0% is what I was saying before we need to we<00:18:05.039> need<00:18:05.159> to<00:18:05.360> make<00:18:05.520> sure<00:18:05.880> that<00:18:06.400> um<00:18:07.400> that<00:18:07.880> we 00:18:08.029 --> 00:18:08.039 align:start position:0% we need to make sure that um that we 00:18:08.039 --> 00:18:10.549 align:start position:0% we need to make sure that um that we have<00:18:08.240> the<00:18:08.400> best<00:18:08.600> technology<00:18:09.120> for<00:18:09.360> for<00:18:09.480> the<00:18:09.679> job 00:18:10.549 --> 00:18:10.559 align:start position:0% have the best technology for for the job 00:18:10.559 --> 00:18:12.669 align:start position:0% have the best technology for for the job and<00:18:11.200> uh<00:18:11.440> yeah<00:18:11.640> there's<00:18:11.880> also<00:18:12.120> a<00:18:12.280> question<00:18:12.520> of 00:18:12.669 --> 00:18:12.679 align:start position:0% and uh yeah there's also a question of 00:18:12.679 --> 00:18:14.870 align:start position:0% and uh yeah there's also a question of values<00:18:13.159> do<00:18:13.320> we<00:18:13.440> want<00:18:13.679> to<00:18:13.919> only<00:18:14.200> build<00:18:14.520> blocks 00:18:14.870 --> 00:18:14.880 align:start position:0% values do we want to only build blocks 00:18:14.880 --> 00:18:17.149 align:start position:0% values do we want to only build blocks and<00:18:15.039> proof<00:18:15.320> blocks<00:18:15.679> in<00:18:16.000> data<00:18:16.280> centers<00:18:16.880> or<00:18:17.080> do 00:18:17.149 --> 00:18:17.159 align:start position:0% and proof blocks in data centers or do 00:18:17.159 --> 00:18:19.350 align:start position:0% and proof blocks in data centers or do we<00:18:17.280> want<00:18:17.400> to<00:18:17.520> do<00:18:17.640> on<00:18:17.760> a<00:18:17.880> Raspberry<00:18:18.320> Pi<00:18:18.880> surely 00:18:19.350 --> 00:18:19.360 align:start position:0% we want to do on a Raspberry Pi surely 00:18:19.360 --> 00:18:21.110 align:start position:0% we want to do on a Raspberry Pi surely the<00:18:19.600> question<00:18:19.919> is<00:18:20.400> the<00:18:20.520> answer<00:18:20.760> is<00:18:20.880> somewhere 00:18:21.110 --> 00:18:21.120 align:start position:0% the question is the answer is somewhere 00:18:21.120 --> 00:18:22.630 align:start position:0% the question is the answer is somewhere in<00:18:21.240> the<00:18:21.320> middle<00:18:21.760> but<00:18:21.960> it<00:18:22.080> needs<00:18:22.320> to<00:18:22.440> be 00:18:22.630 --> 00:18:22.640 align:start position:0% in the middle but it needs to be 00:18:22.640 --> 00:18:26.870 align:start position:0% in the middle but it needs to be discussed<00:18:23.240> and<00:18:23.600> uh<00:18:24.159> and<00:18:24.360> agreed<00:18:25.080> upon<00:18:26.080> um<00:18:26.720> let 00:18:26.870 --> 00:18:26.880 align:start position:0% discussed and uh and agreed upon um let 00:18:26.880 --> 00:18:30.029 align:start position:0% discussed and uh and agreed upon um let me<00:18:27.120> add<00:18:27.880> the<00:18:28.080> to<00:18:28.240> the<00:18:28.919> to<00:18:29.159> that<00:18:29.360> point<00:18:29.640> that<00:18:29.960> the 00:18:30.029 --> 00:18:30.039 align:start position:0% me add the to the to that point that the 00:18:30.039 --> 00:18:32.070 align:start position:0% me add the to the to that point that the more<00:18:30.240> uncertainty<00:18:30.919> you<00:18:31.080> add<00:18:31.400> the<00:18:31.520> more<00:18:31.679> delays 00:18:32.070 --> 00:18:32.080 align:start position:0% more uncertainty you add the more delays 00:18:32.080 --> 00:18:34.029 align:start position:0% more uncertainty you add the more delays you<00:18:32.200> add<00:18:32.559> because<00:18:33.240> questions<00:18:33.600> need<00:18:33.799> to<00:18:33.880> be 00:18:34.029 --> 00:18:34.039 align:start position:0% you add because questions need to be 00:18:34.039 --> 00:18:36.029 align:start position:0% you add because questions need to be answered<00:18:34.919> those<00:18:35.159> questions<00:18:35.520> I<00:18:35.679> just 00:18:36.029 --> 00:18:36.039 align:start position:0% answered those questions I just 00:18:36.039 --> 00:18:38.750 align:start position:0% answered those questions I just mentioned<00:18:37.039> uh<00:18:37.320> and<00:18:37.480> you<00:18:37.720> have<00:18:38.159> the<00:18:38.360> choice 00:18:38.750 --> 00:18:38.760 align:start position:0% mentioned uh and you have the choice 00:18:38.760 --> 00:18:41.590 align:start position:0% mentioned uh and you have the choice between<00:18:39.520> the<00:18:39.720> imperfect<00:18:40.440> technology<00:18:41.440> that 00:18:41.590 --> 00:18:41.600 align:start position:0% between the imperfect technology that 00:18:41.600 --> 00:18:44.909 align:start position:0% between the imperfect technology that bring<00:18:42.240> uh<00:18:42.400> that<00:18:42.480> you<00:18:42.600> can<00:18:42.840> have<00:18:43.159> now<00:18:44.159> and<00:18:44.559> the 00:18:44.909 --> 00:18:44.919 align:start position:0% bring uh that you can have now and the 00:18:44.919 --> 00:18:48.350 align:start position:0% bring uh that you can have now and the perfect<00:18:45.240> technology<00:18:45.720> that<00:18:45.919> never<00:18:46.120> will<00:18:46.640> be<00:18:47.640> um 00:18:48.350 --> 00:18:48.360 align:start position:0% perfect technology that never will be um 00:18:48.360 --> 00:18:52.230 align:start position:0% perfect technology that never will be um if<00:18:49.480> um<00:18:50.480> yeah<00:18:51.000> there<00:18:51.240> there<00:18:51.360> will<00:18:51.559> always<00:18:51.840> be<00:18:52.080> an 00:18:52.230 --> 00:18:52.240 align:start position:0% if um yeah there there will always be an 00:18:52.240 --> 00:18:53.750 align:start position:0% if um yeah there there will always be an improvement<00:18:52.880> in<00:18:53.039> fact<00:18:53.320> you<00:18:53.440> know<00:18:53.600> what 00:18:53.750 --> 00:18:53.760 align:start position:0% improvement in fact you know what 00:18:53.760 --> 00:18:55.350 align:start position:0% improvement in fact you know what happens<00:18:54.120> to<00:18:54.280> veral<00:18:54.720> right<00:18:54.840> now<00:18:55.000> will<00:18:55.159> happen 00:18:55.350 --> 00:18:55.360 align:start position:0% happens to veral right now will happen 00:18:55.360 --> 00:18:57.070 align:start position:0% happens to veral right now will happen to<00:18:55.559> Binary<00:18:55.960> trees<00:18:56.240> where<00:18:56.480> start<00:18:56.799> there<00:18:56.919> will 00:18:57.070 --> 00:18:57.080 align:start position:0% to Binary trees where start there will 00:18:57.080 --> 00:18:59.870 align:start position:0% to Binary trees where start there will be<00:18:57.200> something<00:18:57.559> better<00:18:58.559> uh 00:18:59.870 --> 00:18:59.880 align:start position:0% be something better uh 00:18:59.880 --> 00:19:02.630 align:start position:0% be something better uh veral<00:19:00.440> displaced<00:19:01.440> binary<00:19:01.840> trees<00:19:02.360> without 00:19:02.630 --> 00:19:02.640 align:start position:0% veral displaced binary trees without 00:19:02.640 --> 00:19:05.710 align:start position:0% veral displaced binary trees without Stark<00:19:03.080> so<00:19:03.440> it's<00:19:03.600> definitely<00:19:04.039> going<00:19:04.200> to<00:19:04.720> happen 00:19:05.710 --> 00:19:05.720 align:start position:0% Stark so it's definitely going to happen 00:19:05.720 --> 00:19:08.310 align:start position:0% Stark so it's definitely going to happen uh<00:19:06.159> in<00:19:06.320> my<00:19:06.480> view<00:19:07.039> done<00:19:07.360> is<00:19:07.520> better<00:19:07.799> than 00:19:08.310 --> 00:19:08.320 align:start position:0% uh in my view done is better than 00:19:08.320 --> 00:19:10.870 align:start position:0% uh in my view done is better than perfect<00:19:09.320> um<00:19:09.600> and<00:19:09.720> I<00:19:09.799> would<00:19:09.960> say<00:19:10.240> ethereum<00:19:10.720> has 00:19:10.870 --> 00:19:10.880 align:start position:0% perfect um and I would say ethereum has 00:19:10.880 --> 00:19:13.390 align:start position:0% perfect um and I would say ethereum has a<00:19:11.159> history<00:19:11.799> um<00:19:12.000> so<00:19:12.440> for<00:19:12.640> those<00:19:12.799> who<00:19:12.919> don't<00:19:13.120> know 00:19:13.390 --> 00:19:13.400 align:start position:0% a history um so for those who don't know 00:19:13.400 --> 00:19:16.630 align:start position:0% a history um so for those who don't know I<00:19:13.559> was<00:19:14.159> uh<00:19:14.360> with<00:19:14.520> M<00:19:14.960> Kini<00:19:15.320> and<00:19:15.480> Danny<00:19:15.799> Ryan<00:19:16.520> I 00:19:16.630 --> 00:19:16.640 align:start position:0% I was uh with M Kini and Danny Ryan I 00:19:16.640 --> 00:19:18.909 align:start position:0% I was uh with M Kini and Danny Ryan I built<00:19:16.919> the<00:19:17.039> first<00:19:17.280> prototype<00:19:18.080> uh<00:19:18.200> to<00:19:18.360> do<00:19:18.679> the 00:19:18.909 --> 00:19:18.919 align:start position:0% built the first prototype uh to do the 00:19:18.919 --> 00:19:21.789 align:start position:0% built the first prototype uh to do the to<00:19:19.080> do<00:19:19.200> the<00:19:19.400> merge<00:19:20.400> um<00:19:20.840> the<00:19:21.000> exact<00:19:21.280> same<00:19:21.520> thing 00:19:21.789 --> 00:19:21.799 align:start position:0% to do the merge um the exact same thing 00:19:21.799 --> 00:19:24.190 align:start position:0% to do the merge um the exact same thing happened<00:19:22.480> there<00:19:22.600> were<00:19:22.919> lots<00:19:23.080> of<00:19:23.280> ideas<00:19:24.000> but 00:19:24.190 --> 00:19:24.200 align:start position:0% happened there were lots of ideas but 00:19:24.200 --> 00:19:25.909 align:start position:0% happened there were lots of ideas but nothing<00:19:24.520> was<00:19:24.679> being<00:19:24.880> delivered<00:19:25.320> so<00:19:25.480> we<00:19:25.640> sat 00:19:25.909 --> 00:19:25.919 align:start position:0% nothing was being delivered so we sat 00:19:25.919 --> 00:19:27.830 align:start position:0% nothing was being delivered so we sat down<00:19:26.400> we<00:19:26.559> designed<00:19:26.880> a<00:19:27.039> very<00:19:27.200> simple<00:19:27.480> engine 00:19:27.830 --> 00:19:27.840 align:start position:0% down we designed a very simple engine 00:19:27.840 --> 00:19:30.350 align:start position:0% down we designed a very simple engine API<00:19:28.720> done<00:19:28.919> was<00:19:29.080> better<00:19:29.440> than<00:19:29.679> perfect 00:19:30.350 --> 00:19:30.360 align:start position:0% API done was better than perfect 00:19:30.360 --> 00:19:32.070 align:start position:0% API done was better than perfect ethereum<00:19:30.799> Advanced<00:19:31.520> and<00:19:31.640> I<00:19:31.760> think<00:19:31.919> the 00:19:32.070 --> 00:19:32.080 align:start position:0% ethereum Advanced and I think the 00:19:32.080 --> 00:19:33.549 align:start position:0% ethereum Advanced and I think the problem<00:19:32.280> of<00:19:32.400> ethereum<00:19:32.840> right<00:19:32.960> now<00:19:33.159> is<00:19:33.280> that<00:19:33.440> it 00:19:33.549 --> 00:19:33.559 align:start position:0% problem of ethereum right now is that it 00:19:33.559 --> 00:19:36.909 align:start position:0% problem of ethereum right now is that it doesn't<00:19:34.280> make<00:19:34.520> those<00:19:34.840> leaps<00:19:35.440> it<00:19:35.679> keeps<00:19:36.679> living 00:19:36.909 --> 00:19:36.919 align:start position:0% doesn't make those leaps it keeps living 00:19:36.919 --> 00:19:39.830 align:start position:0% doesn't make those leaps it keeps living in<00:19:37.080> that<00:19:37.559> future<00:19:38.559> and<00:19:38.919> toying<00:19:39.280> with<00:19:39.400> a<00:19:39.520> lot<00:19:39.679> of 00:19:39.830 --> 00:19:39.840 align:start position:0% in that future and toying with a lot of 00:19:39.840 --> 00:19:42.549 align:start position:0% in that future and toying with a lot of ideas<00:19:40.240> that<00:19:40.679> will<00:19:40.840> never<00:19:41.159> happen<00:19:42.080> right<00:19:42.240> now 00:19:42.549 --> 00:19:42.559 align:start position:0% ideas that will never happen right now 00:19:42.559 --> 00:19:44.830 align:start position:0% ideas that will never happen right now veral<00:19:43.080> exists<00:19:43.440> veral<00:19:43.840> is<00:19:44.039> there<00:19:44.400> it's<00:19:44.600> the 00:19:44.830 --> 00:19:44.840 align:start position:0% veral exists veral is there it's the 00:19:44.840 --> 00:19:46.549 align:start position:0% veral exists veral is there it's the strongest<00:19:45.159> Val<00:19:45.559> it's<00:19:45.720> the<00:19:45.880> only<00:19:46.240> value 00:19:46.549 --> 00:19:46.559 align:start position:0% strongest Val it's the only value 00:19:46.559 --> 00:19:51.230 align:start position:0% strongest Val it's the only value proposition<00:19:47.080> at<00:19:47.240> this<00:19:47.480> St<00:19:47.760> stage<00:19:48.559> so<00:19:49.320> um<00:19:50.159> we<00:19:51.159> I 00:19:51.230 --> 00:19:51.240 align:start position:0% proposition at this St stage so um we I 00:19:51.240 --> 00:19:52.549 align:start position:0% proposition at this St stage so um we I think<00:19:51.400> it<00:19:51.520> makes<00:19:51.720> sense<00:19:51.919> to<00:19:52.039> keep<00:19:52.200> working<00:19:52.440> on 00:19:52.549 --> 00:19:52.559 align:start position:0% think it makes sense to keep working on 00:19:52.559 --> 00:19:56.070 align:start position:0% think it makes sense to keep working on it<00:19:53.240> but<00:19:53.679> to<00:19:53.840> be<00:19:54.039> clear<00:19:54.600> veral<00:19:55.159> has<00:19:55.320> been<00:19:55.799> uh<00:19:55.919> or 00:19:56.070 --> 00:19:56.080 align:start position:0% it but to be clear veral has been uh or 00:19:56.080 --> 00:19:57.990 align:start position:0% it but to be clear veral has been uh or at<00:19:56.159> least<00:19:56.320> stateless<00:19:56.720> has<00:19:56.880> been<00:19:57.080> built<00:19:57.720> with 00:19:57.990 --> 00:19:58.000 align:start position:0% at least stateless has been built with 00:19:58.000 --> 00:19:59.310 align:start position:0% at least stateless has been built with upgradeability 00:19:59.310 --> 00:19:59.320 align:start position:0% upgradeability 00:19:59.320 --> 00:20:03.110 align:start position:0% upgradeability uh<00:19:59.679> re<00:20:00.240> reusability<00:20:01.120> in<00:20:01.559> in<00:20:01.799> in<00:20:01.919> mind<00:20:02.559> so<00:20:03.000> we 00:20:03.110 --> 00:20:03.120 align:start position:0% uh re reusability in in in mind so we 00:20:03.120 --> 00:20:05.110 align:start position:0% uh re reusability in in in mind so we will<00:20:03.320> change<00:20:03.559> the<00:20:03.679> tree<00:20:03.960> structure<00:20:04.720> but<00:20:04.960> the 00:20:05.110 --> 00:20:05.120 align:start position:0% will change the tree structure but the 00:20:05.120 --> 00:20:06.909 align:start position:0% will change the tree structure but the gas<00:20:05.400> cost<00:20:05.600> would<00:20:05.760> not<00:20:05.960> change<00:20:06.480> the<00:20:06.679> state 00:20:06.909 --> 00:20:06.919 align:start position:0% gas cost would not change the state 00:20:06.919 --> 00:20:08.350 align:start position:0% gas cost would not change the state conversion<00:20:07.320> would<00:20:07.480> not<00:20:07.640> change<00:20:08.000> like<00:20:08.159> all 00:20:08.350 --> 00:20:08.360 align:start position:0% conversion would not change like all 00:20:08.360 --> 00:20:10.870 align:start position:0% conversion would not change like all those<00:20:08.559> methods<00:20:08.880> have<00:20:09.039> been<00:20:09.440> validated<00:20:10.440> um<00:20:10.679> the 00:20:10.870 --> 00:20:10.880 align:start position:0% those methods have been validated um the 00:20:10.880 --> 00:20:14.070 align:start position:0% those methods have been validated um the historical<00:20:11.360> root<00:20:11.640> contract<00:20:12.080> like<00:20:12.240> 20<00:20:13.080> 2935 00:20:14.070 --> 00:20:14.080 align:start position:0% historical root contract like 20 2935 00:20:14.080 --> 00:20:16.430 align:start position:0% historical root contract like 20 2935 could<00:20:14.240> be<00:20:14.360> used<00:20:14.840> State<00:20:15.240> expiry<00:20:16.080> to<00:20:16.240> be 00:20:16.430 --> 00:20:16.440 align:start position:0% could be used State expiry to be 00:20:16.440 --> 00:20:18.190 align:start position:0% could be used State expiry to be confirmed<00:20:16.919> but<00:20:17.039> should<00:20:17.280> be<00:20:17.440> a<00:20:17.640> reusable 00:20:18.190 --> 00:20:18.200 align:start position:0% confirmed but should be a reusable 00:20:18.200 --> 00:20:21.870 align:start position:0% confirmed but should be a reusable verbatim<00:20:18.799> as<00:20:18.919> well<00:20:19.720> um<00:20:20.000> so<00:20:20.280> that's<00:20:20.760> uh<00:20:21.520> yeah 00:20:21.870 --> 00:20:21.880 align:start position:0% verbatim as well um so that's uh yeah 00:20:21.880 --> 00:20:24.270 align:start position:0% verbatim as well um so that's uh yeah that's<00:20:22.080> reassuring<00:20:22.600> I<00:20:22.760> think<00:20:23.360> uh<00:20:23.640> we<00:20:23.840> can 00:20:24.270 --> 00:20:24.280 align:start position:0% that's reassuring I think uh we can 00:20:24.280 --> 00:20:26.990 align:start position:0% that's reassuring I think uh we can afford<00:20:24.679> to<00:20:25.640> push<00:20:26.000> the<00:20:26.200> question<00:20:26.480> of<00:20:26.640> binary 00:20:26.990 --> 00:20:27.000 align:start position:0% afford to push the question of binary 00:20:27.000 --> 00:20:29.830 align:start position:0% afford to push the question of binary trees<00:20:27.360> to<00:20:27.720> a<00:20:27.919> time<00:20:28.120> where<00:20:28.240> it's<00:20:28.360> more 00:20:29.830 --> 00:20:29.840 align:start position:0% trees to a time where it's more 00:20:29.840 --> 00:20:32.789 align:start position:0% trees to a time where it's more defined<00:20:30.840> um<00:20:31.080> that's<00:20:31.280> pretty<00:20:31.520> much<00:20:31.720> it<00:20:32.080> go<00:20:32.640> uh 00:20:32.789 --> 00:20:32.799 align:start position:0% defined um that's pretty much it go uh 00:20:32.799 --> 00:20:35.230 align:start position:0% defined um that's pretty much it go uh check<00:20:33.039> verino<00:20:34.000> to<00:20:34.240> have<00:20:34.440> all<00:20:34.600> the<00:20:35.000> all<00:20:35.120> the 00:20:35.230 --> 00:20:35.240 align:start position:0% check verino to have all the all the 00:20:35.240 --> 00:20:38.470 align:start position:0% check verino to have all the all the news<00:20:36.159> and<00:20:36.440> ctin<00:20:36.880> and<00:20:37.039> test<00:20:37.320> net<00:20:37.600> to<00:20:37.840> check<00:20:38.200> our 00:20:38.470 --> 00:20:38.480 align:start position:0% news and ctin and test net to check our 00:20:38.480 --> 00:20:40.710 align:start position:0% news and ctin and test net to check our latest<00:20:38.840> test<00:20:39.120> net<00:20:39.360> come<00:20:39.520> break<00:20:39.799> it<00:20:40.039> help<00:20:40.280> us<00:20:40.600> uh 00:20:40.710 --> 00:20:40.720 align:start position:0% latest test net come break it help us uh 00:20:40.720 --> 00:20:48.430 align:start position:0% latest test net come break it help us uh help<00:20:40.919> us<00:20:41.080> build<00:20:41.559> it<00:20:42.559> um 00:20:48.430 --> 00:20:48.440 align:start position:0% 00:20:48.440 --> 00:20:51.430 align:start position:0% yep<00:20:49.440> thank<00:20:49.559> you<00:20:49.679> for<00:20:49.840> the<00:20:49.960> wonderful<00:20:50.320> talk<00:20:50.640> Gom 00:20:51.430 --> 00:20:51.440 align:start position:0% yep thank you for the wonderful talk Gom 00:20:51.440 --> 00:20:54.029 align:start position:0% yep thank you for the wonderful talk Gom let's<00:20:51.640> turn<00:20:51.799> our<00:20:51.960> attention<00:20:52.240> to<00:20:52.720> questions<00:20:53.720> if 00:20:54.029 --> 00:20:54.039 align:start position:0% let's turn our attention to questions if 00:20:54.039 --> 00:20:57.830 align:start position:0% let's turn our attention to questions if ethereum<00:20:54.919> Al<00:20:55.640> adopts<00:20:56.039> fkl<00:20:56.880> uh<00:20:56.960> should<00:20:57.200> rollups 00:20:57.830 --> 00:20:57.840 align:start position:0% ethereum Al adopts fkl uh should rollups 00:20:57.840 --> 00:20:59.750 align:start position:0% ethereum Al adopts fkl uh should rollups also<00:20:58.159> adopt<00:20:58.440> it<00:20:58.919> yeah<00:20:59.080> that's<00:20:59.240> a<00:20:59.400> good 00:20:59.750 --> 00:20:59.760 align:start position:0% also adopt it yeah that's a good 00:20:59.760 --> 00:21:02.190 align:start position:0% also adopt it yeah that's a good question<00:21:00.760> um<00:21:01.039> there<00:21:01.159> are<00:21:01.400> good<00:21:01.679> I<00:21:01.760> mean<00:21:02.000> it's 00:21:02.190 --> 00:21:02.200 align:start position:0% question um there are good I mean it's 00:21:02.200 --> 00:21:04.789 align:start position:0% question um there are good I mean it's always<00:21:02.720> a<00:21:03.000> question<00:21:03.240> of<00:21:03.440> maintaining<00:21:03.840> a<00:21:04.039> diff 00:21:04.789 --> 00:21:04.799 align:start position:0% always a question of maintaining a diff 00:21:04.799 --> 00:21:09.110 align:start position:0% always a question of maintaining a diff so<00:21:05.280> if<00:21:05.640> you<00:21:05.880> think<00:21:06.480> um<00:21:07.280> that<00:21:08.280> uh<00:21:08.520> so<00:21:08.960> yeah 00:21:09.110 --> 00:21:09.120 align:start position:0% so if you think um that uh so yeah 00:21:09.120 --> 00:21:10.990 align:start position:0% so if you think um that uh so yeah there's<00:21:09.360> this<00:21:09.480> thing<00:21:09.679> called<00:21:09.840> rollup<00:21:10.279> guas<00:21:10.840> uh 00:21:10.990 --> 00:21:11.000 align:start position:0% there's this thing called rollup guas uh 00:21:11.000 --> 00:21:13.990 align:start position:0% there's this thing called rollup guas uh that<00:21:11.279> tries<00:21:11.520> to<00:21:11.600> be<00:21:11.720> a<00:21:11.799> fork<00:21:12.080> of<00:21:12.320> guas<00:21:13.159> and<00:21:13.840> uh 00:21:13.990 --> 00:21:14.000 align:start position:0% that tries to be a fork of guas and uh 00:21:14.000 --> 00:21:16.350 align:start position:0% that tries to be a fork of guas and uh you<00:21:14.120> know<00:21:14.279> maintain<00:21:14.720> a<00:21:14.880> standard<00:21:15.279> base<00:21:16.080> maybe 00:21:16.350 --> 00:21:16.360 align:start position:0% you know maintain a standard base maybe 00:21:16.360 --> 00:21:18.470 align:start position:0% you know maintain a standard base maybe rollup<00:21:16.760> guas<00:21:17.039> could<00:21:17.400> Implement<00:21:17.799> binary<00:21:18.159> trees 00:21:18.470 --> 00:21:18.480 align:start position:0% rollup guas could Implement binary trees 00:21:18.480 --> 00:21:21.549 align:start position:0% rollup guas could Implement binary trees if<00:21:18.640> they<00:21:18.799> want<00:21:19.760> uh<00:21:20.039> but<00:21:20.200> should<00:21:20.559> they<00:21:21.240> um<00:21:21.480> I 00:21:21.549 --> 00:21:21.559 align:start position:0% if they want uh but should they um I 00:21:21.559 --> 00:21:22.750 align:start position:0% if they want uh but should they um I mean<00:21:21.720> I<00:21:21.799> don't<00:21:21.960> know<00:21:22.120> do<00:21:22.240> you<00:21:22.440> are<00:21:22.600> you 00:21:22.750 --> 00:21:22.760 align:start position:0% mean I don't know do you are you 00:21:22.760 --> 00:21:24.950 align:start position:0% mean I don't know do you are you interested<00:21:23.120> in<00:21:23.279> a<00:21:23.400> smaller<00:21:23.760> dis<00:21:24.240> footprint 00:21:24.950 --> 00:21:24.960 align:start position:0% interested in a smaller dis footprint 00:21:24.960 --> 00:21:28.630 align:start position:0% interested in a smaller dis footprint small<00:21:25.279> proofs<00:21:25.760> and<00:21:26.240> uh<00:21:27.080> and<00:21:27.640> uh<00:21:28.120> something 00:21:28.630 --> 00:21:28.640 align:start position:0% small proofs and uh and uh something 00:21:28.640 --> 00:21:31.830 align:start position:0% small proofs and uh and uh something that's<00:21:28.840> readily<00:21:29.320> available<00:21:30.200> I'd<00:21:30.400> say<00:21:30.960> yeah<00:21:31.480> uh 00:21:31.830 --> 00:21:31.840 align:start position:0% that's readily available I'd say yeah uh 00:21:31.840 --> 00:21:33.470 align:start position:0% that's readily available I'd say yeah uh I'm<00:21:31.960> not<00:21:32.120> going<00:21:32.200> to<00:21:32.320> tell<00:21:32.480> rollups<00:21:32.960> what<00:21:33.080> to<00:21:33.200> do 00:21:33.470 --> 00:21:33.480 align:start position:0% I'm not going to tell rollups what to do 00:21:33.480 --> 00:21:35.149 align:start position:0% I'm not going to tell rollups what to do I'm<00:21:33.600> saying<00:21:34.120> I<00:21:34.200> think<00:21:34.400> it's<00:21:34.559> also<00:21:34.760> a<00:21:35.000> strong 00:21:35.149 --> 00:21:35.159 align:start position:0% I'm saying I think it's also a strong 00:21:35.159 --> 00:21:37.830 align:start position:0% I'm saying I think it's also a strong value<00:21:35.480> proposition<00:21:35.880> for<00:21:36.520> rollups<00:21:37.520> how<00:21:37.640> do 00:21:37.830 --> 00:21:37.840 align:start position:0% value proposition for rollups how do 00:21:37.840 --> 00:21:40.669 align:start position:0% value proposition for rollups how do veral<00:21:38.240> trees<00:21:38.600> help<00:21:38.840> with<00:21:39.000> stateless<00:21:39.679> clients 00:21:40.669 --> 00:21:40.679 align:start position:0% veral trees help with stateless clients 00:21:40.679 --> 00:21:43.269 align:start position:0% veral trees help with stateless clients um<00:21:40.840> I<00:21:40.919> mean<00:21:41.080> it's<00:21:41.200> a<00:21:41.440> technology<00:21:42.080> that<00:21:42.400> okay<00:21:43.000> it 00:21:43.269 --> 00:21:43.279 align:start position:0% um I mean it's a technology that okay it 00:21:43.279 --> 00:21:46.230 align:start position:0% um I mean it's a technology that okay it basically<00:21:43.640> makes<00:21:44.159> very<00:21:44.320> small<00:21:44.799> proofs<00:21:45.799> so<00:21:46.120> you 00:21:46.230 --> 00:21:46.240 align:start position:0% basically makes very small proofs so you 00:21:46.240 --> 00:21:48.510 align:start position:0% basically makes very small proofs so you can<00:21:46.480> attach<00:21:46.760> it<00:21:46.880> to<00:21:47.000> the<00:21:47.159> block<00:21:48.000> and<00:21:48.200> as<00:21:48.279> a 00:21:48.510 --> 00:21:48.520 align:start position:0% can attach it to the block and as a 00:21:48.520 --> 00:21:50.630 align:start position:0% can attach it to the block and as a result<00:21:49.240> uh<00:21:49.360> stateless<00:21:49.840> clients<00:21:50.440> just 00:21:50.630 --> 00:21:50.640 align:start position:0% result uh stateless clients just 00:21:50.640 --> 00:21:52.710 align:start position:0% result uh stateless clients just download<00:21:51.080> one<00:21:51.279> block<00:21:51.679> and<00:21:51.919> they're<00:21:52.120> following 00:21:52.710 --> 00:21:52.720 align:start position:0% download one block and they're following 00:21:52.720 --> 00:21:54.149 align:start position:0% download one block and they're following it's<00:21:53.080> I<00:21:53.120> mean<00:21:53.279> they're<00:21:53.520> considered<00:21:53.919> to<00:21:54.039> be 00:21:54.149 --> 00:21:54.159 align:start position:0% it's I mean they're considered to be 00:21:54.159 --> 00:21:56.230 align:start position:0% it's I mean they're considered to be following<00:21:54.559> the<00:21:54.679> chain<00:21:55.120> that<00:21:55.360> it's<00:21:55.799> uh 00:21:56.230 --> 00:21:56.240 align:start position:0% following the chain that it's uh 00:21:56.240 --> 00:21:59.029 align:start position:0% following the chain that it's uh completely<00:21:56.840> secure<00:21:57.520> so<00:21:57.919> that's<00:21:58.320> uh 00:21:59.029 --> 00:21:59.039 align:start position:0% completely secure so that's uh 00:21:59.039 --> 00:22:01.789 align:start position:0% completely secure so that's uh that's<00:21:59.240> their<00:21:59.799> power<00:22:00.799> are<00:22:00.960> there<00:22:01.120> any<00:22:01.440> major 00:22:01.789 --> 00:22:01.799 align:start position:0% that's their power are there any major 00:22:01.799 --> 00:22:03.590 align:start position:0% that's their power are there any major trade-offs<00:22:02.240> of<00:22:02.400> verl<00:22:02.760> trees<00:22:03.039> over<00:22:03.240> merkl 00:22:03.590 --> 00:22:03.600 align:start position:0% trade-offs of verl trees over merkl 00:22:03.600 --> 00:22:06.269 align:start position:0% trade-offs of verl trees over merkl Patricia<00:22:03.960> tries<00:22:04.760> uh<00:22:04.880> it's<00:22:05.000> a<00:22:05.240> bit<00:22:05.799> uh<00:22:05.960> I<00:22:06.000> mean 00:22:06.269 --> 00:22:06.279 align:start position:0% Patricia tries uh it's a bit uh I mean 00:22:06.279 --> 00:22:08.029 align:start position:0% Patricia tries uh it's a bit uh I mean it's<00:22:06.559> like<00:22:06.760> maybe<00:22:07.000> an<00:22:07.120> order<00:22:07.400> of<00:22:07.520> magnitude 00:22:08.029 --> 00:22:08.039 align:start position:0% it's like maybe an order of magnitude 00:22:08.039 --> 00:22:10.710 align:start position:0% it's like maybe an order of magnitude it's<00:22:08.200> still<00:22:08.480> very<00:22:08.720> fast<00:22:09.039> but<00:22:09.400> it's<00:22:09.559> slower<00:22:10.000> to 00:22:10.710 --> 00:22:10.720 align:start position:0% it's still very fast but it's slower to 00:22:10.720 --> 00:22:13.110 align:start position:0% it's still very fast but it's slower to to<00:22:11.200> compute<00:22:11.559> the<00:22:11.679> root<00:22:11.919> commitment<00:22:12.440> in<00:22:12.799> veral 00:22:13.110 --> 00:22:13.120 align:start position:0% to compute the root commitment in veral 00:22:13.120 --> 00:22:15.870 align:start position:0% to compute the root commitment in veral trees<00:22:13.480> so<00:22:14.000> blocks<00:22:14.799> tend<00:22:15.039> to<00:22:15.200> be<00:22:15.320> a<00:22:15.440> bit<00:22:15.559> slower 00:22:15.870 --> 00:22:15.880 align:start position:0% trees so blocks tend to be a bit slower 00:22:15.880 --> 00:22:17.070 align:start position:0% trees so blocks tend to be a bit slower to 00:22:17.070 --> 00:22:17.080 align:start position:0% to 00:22:17.080 --> 00:22:20.990 align:start position:0% to build<00:22:18.120> okay<00:22:19.120> um<00:22:19.760> how<00:22:19.919> do<00:22:20.240> veral<00:22:20.640> trees 00:22:20.990 --> 00:22:21.000 align:start position:0% build okay um how do veral trees 00:22:21.000 --> 00:22:26.110 align:start position:0% build okay um how do veral trees generate<00:22:21.400> 01<00:22:22.000> proofs<00:22:23.000> um<00:22:23.400> by<00:22:23.600> the<00:22:23.840> magic<00:22:24.360> of<00:22:25.120> uh 00:22:26.110 --> 00:22:26.120 align:start position:0% generate 01 proofs um by the magic of uh 00:22:26.120 --> 00:22:28.149 align:start position:0% generate 01 proofs um by the magic of uh how<00:22:26.279> would<00:22:26.400> I<00:22:26.520> say<00:22:26.720> that<00:22:27.320> so<00:22:27.640> yes<00:22:27.840> because<00:22:28.039> I 00:22:28.149 --> 00:22:28.159 align:start position:0% how would I say that so yes because I 00:22:28.159 --> 00:22:29.350 align:start position:0% how would I say that so yes because I know<00:22:28.360> the<00:22:28.520> that's<00:22:28.640> probably<00:22:28.880> the<00:22:29.000> question<00:22:29.200> is 00:22:29.350 --> 00:22:29.360 align:start position:0% know the that's probably the question is 00:22:29.360 --> 00:22:31.750 align:start position:0% know the that's probably the question is probably<00:22:29.640> because<00:22:29.880> we<00:22:29.960> use<00:22:30.200> IPA<00:22:31.080> and<00:22:31.279> IPA<00:22:31.640> is 00:22:31.750 --> 00:22:31.760 align:start position:0% probably because we use IPA and IPA is 00:22:31.760 --> 00:22:34.830 align:start position:0% probably because we use IPA and IPA is logarithmic<00:22:32.640> but<00:22:33.120> uh<00:22:33.200> it's<00:22:33.400> logarithmic<00:22:34.080> on 00:22:34.830 --> 00:22:34.840 align:start position:0% logarithmic but uh it's logarithmic on 00:22:34.840 --> 00:22:37.990 align:start position:0% logarithmic but uh it's logarithmic on constant<00:22:35.279> Vector<00:22:36.120> so<00:22:36.840> uh<00:22:36.960> it's<00:22:37.200> effectively 00:22:37.990 --> 00:22:38.000 align:start position:0% constant Vector so uh it's effectively 00:22:38.000 --> 00:22:41.390 align:start position:0% constant Vector so uh it's effectively uh<00:22:38.440> o1<00:22:38.799> proof<00:22:39.279> if<00:22:39.360> you<00:22:39.480> want<00:22:39.679> some<00:22:40.159> details<00:22:41.159> uh 00:22:41.390 --> 00:22:41.400 align:start position:0% uh o1 proof if you want some details uh 00:22:41.400 --> 00:22:43.149 align:start position:0% uh o1 proof if you want some details uh we<00:22:41.520> can<00:22:41.720> talk<00:22:41.919> about<00:22:42.200> this<00:22:42.400> after<00:22:42.720> the<00:22:42.960> after 00:22:43.149 --> 00:22:43.159 align:start position:0% we can talk about this after the after 00:22:43.159 --> 00:22:45.909 align:start position:0% we can talk about this after the after the<00:22:43.480> talk<00:22:44.480> how<00:22:44.640> would<00:22:44.760> a<00:22:44.960> Quantum<00:22:45.400> attack<00:22:45.720> work 00:22:45.909 --> 00:22:45.919 align:start position:0% the talk how would a Quantum attack work 00:22:45.919 --> 00:22:47.789 align:start position:0% the talk how would a Quantum attack work on<00:22:46.080> veral<00:22:46.600> is<00:22:46.679> it<00:22:46.880> important<00:22:47.240> to<00:22:47.440> consider 00:22:47.789 --> 00:22:47.799 align:start position:0% on veral is it important to consider 00:22:47.799 --> 00:22:49.710 align:start position:0% on veral is it important to consider Quantum<00:22:48.240> resistance<00:22:49.000> it's<00:22:49.120> only<00:22:49.360> important 00:22:49.710 --> 00:22:49.720 align:start position:0% Quantum resistance it's only important 00:22:49.720 --> 00:22:53.269 align:start position:0% Quantum resistance it's only important if<00:22:49.840> quantum<00:22:50.559> uh<00:22:50.919> quantum<00:22:51.840> computers<00:22:52.240> are<00:22:52.400> real 00:22:53.269 --> 00:22:53.279 align:start position:0% if quantum uh quantum computers are real 00:22:53.279 --> 00:22:55.510 align:start position:0% if quantum uh quantum computers are real um<00:22:53.600> how<00:22:53.720> would<00:22:53.840> a<00:22:54.000> netac<00:22:54.360> work<00:22:54.520> on<00:22:54.679> veral<00:22:55.400> uh 00:22:55.510 --> 00:22:55.520 align:start position:0% um how would a netac work on veral uh 00:22:55.520 --> 00:22:57.190 align:start position:0% um how would a netac work on veral uh yeah<00:22:55.640> I<00:22:55.720> skimmed<00:22:56.039> a<00:22:56.159> bit<00:22:56.320> over<00:22:56.559> it<00:22:56.960> uh<00:22:57.080> you 00:22:57.190 --> 00:22:57.200 align:start position:0% yeah I skimmed a bit over it uh you 00:22:57.200 --> 00:22:59.149 align:start position:0% yeah I skimmed a bit over it uh you could<00:22:57.440> either<00:22:58.000> unbalance<00:22:58.640> the<00:22:58.760> tree<00:22:59.000> but 00:22:59.149 --> 00:22:59.159 align:start position:0% could either unbalance the tree but 00:22:59.159 --> 00:23:01.149 align:start position:0% could either unbalance the tree but that's<00:22:59.320> easy<00:22:59.520> to<00:22:59.720> fix<00:23:00.320> or<00:23:00.480> you<00:23:00.600> could<00:23:00.840> create 00:23:01.149 --> 00:23:01.159 align:start position:0% that's easy to fix or you could create 00:23:01.159 --> 00:23:03.470 align:start position:0% that's easy to fix or you could create fake<00:23:01.400> proofs<00:23:02.200> in<00:23:02.400> that<00:23:02.640> case<00:23:03.080> what<00:23:03.240> would 00:23:03.470 --> 00:23:03.480 align:start position:0% fake proofs in that case what would 00:23:03.480 --> 00:23:05.789 align:start position:0% fake proofs in that case what would happen<00:23:03.880> is<00:23:04.120> that<00:23:04.520> all<00:23:04.679> the<00:23:04.840> stateless<00:23:05.320> clients 00:23:05.789 --> 00:23:05.799 align:start position:0% happen is that all the stateless clients 00:23:05.799 --> 00:23:07.470 align:start position:0% happen is that all the stateless clients would<00:23:06.080> accept<00:23:06.640> a<00:23:06.760> block<00:23:07.120> and<00:23:07.240> all<00:23:07.360> the 00:23:07.470 --> 00:23:07.480 align:start position:0% would accept a block and all the 00:23:07.480 --> 00:23:08.909 align:start position:0% would accept a block and all the stateful<00:23:07.880> client<00:23:08.159> would<00:23:08.320> realize<00:23:08.720> that<00:23:08.840> the 00:23:08.909 --> 00:23:08.919 align:start position:0% stateful client would realize that the 00:23:08.919 --> 00:23:10.590 align:start position:0% stateful client would realize that the proof<00:23:09.159> is<00:23:09.320> completely<00:23:09.679> nonsense<00:23:10.080> and<00:23:10.240> would 00:23:10.590 --> 00:23:10.600 align:start position:0% proof is completely nonsense and would 00:23:10.600 --> 00:23:12.830 align:start position:0% proof is completely nonsense and would reject<00:23:10.919> the<00:23:11.039> block<00:23:11.520> so<00:23:11.720> the<00:23:11.840> network<00:23:12.240> would<00:23:12.679> uh 00:23:12.830 --> 00:23:12.840 align:start position:0% reject the block so the network would uh 00:23:12.840 --> 00:23:16.149 align:start position:0% reject the block so the network would uh would<00:23:13.240> split<00:23:14.240> um<00:23:15.159> that<00:23:15.279> comes<00:23:15.480> at<00:23:15.600> a<00:23:15.760> cost<00:23:16.039> of 00:23:16.149 --> 00:23:16.159 align:start position:0% would split um that comes at a cost of 00:23:16.159 --> 00:23:18.950 align:start position:0% would split um that comes at a cost of course<00:23:16.440> because<00:23:17.240> uh<00:23:17.679> obviously<00:23:18.120> if<00:23:18.559> quantum 00:23:18.950 --> 00:23:18.960 align:start position:0% course because uh obviously if quantum 00:23:18.960 --> 00:23:22.510 align:start position:0% course because uh obviously if quantum computers<00:23:19.720> happen<00:23:20.720> then<00:23:21.720> veral<00:23:22.120> is<00:23:22.240> of<00:23:22.360> the 00:23:22.510 --> 00:23:22.520 align:start position:0% computers happen then veral is of the 00:23:22.520 --> 00:23:24.470 align:start position:0% computers happen then veral is of the table<00:23:22.760> we're<00:23:22.880> not<00:23:23.039> doing<00:23:23.279> that<00:23:23.440> anymore<00:23:24.159> but 00:23:24.470 --> 00:23:24.480 align:start position:0% table we're not doing that anymore but 00:23:24.480 --> 00:23:26.110 align:start position:0% table we're not doing that anymore but the<00:23:24.600> question<00:23:24.880> is<00:23:25.039> what<00:23:25.200> happens<00:23:25.600> if<00:23:25.840> no<00:23:25.960> one 00:23:26.110 --> 00:23:26.120 align:start position:0% the question is what happens if no one 00:23:26.120 --> 00:23:28.110 align:start position:0% the question is what happens if no one knows<00:23:26.360> you<00:23:26.520> have<00:23:26.600> a<00:23:26.720> quantum<00:23:27.120> computer<00:23:28.000> in 00:23:28.110 --> 00:23:28.120 align:start position:0% knows you have a quantum computer in 00:23:28.120 --> 00:23:30.710 align:start position:0% knows you have a quantum computer in that<00:23:28.279> cas<00:23:28.559> case<00:23:28.840> you<00:23:28.960> would<00:23:29.320> reveal<00:23:30.320> like<00:23:30.600> you 00:23:30.710 --> 00:23:30.720 align:start position:0% that cas case you would reveal like you 00:23:30.720 --> 00:23:34.310 align:start position:0% that cas case you would reveal like you would<00:23:31.120> show<00:23:31.360> your<00:23:31.559> deck<00:23:31.799> to<00:23:32.360> everybody<00:23:33.360> um<00:23:33.960> so 00:23:34.310 --> 00:23:34.320 align:start position:0% would show your deck to everybody um so 00:23:34.320 --> 00:23:38.230 align:start position:0% would show your deck to everybody um so and<00:23:35.080> the<00:23:35.279> result<00:23:35.679> of<00:23:36.039> doing<00:23:36.360> this<00:23:37.320> uh<00:23:37.440> would<00:23:37.679> be 00:23:38.230 --> 00:23:38.240 align:start position:0% and the result of doing this uh would be 00:23:38.240 --> 00:23:41.549 align:start position:0% and the result of doing this uh would be that<00:23:39.080> um<00:23:39.840> you<00:23:39.960> know<00:23:40.200> you<00:23:40.320> would<00:23:40.480> be<00:23:40.600> a<00:23:41.039> newens 00:23:41.549 --> 00:23:41.559 align:start position:0% that um you know you would be a newens 00:23:41.559 --> 00:23:43.669 align:start position:0% that um you know you would be a newens to<00:23:41.720> ethereum<00:23:42.159> for<00:23:42.360> a<00:23:42.520> couple<00:23:43.039> couple<00:23:43.320> days<00:23:43.520> but 00:23:43.669 --> 00:23:43.679 align:start position:0% to ethereum for a couple couple days but 00:23:43.679 --> 00:23:45.630 align:start position:0% to ethereum for a couple couple days but then<00:23:43.840> everybody<00:23:44.200> would<00:23:44.480> just<00:23:45.039> go<00:23:45.279> back<00:23:45.440> to 00:23:45.630 --> 00:23:45.640 align:start position:0% then everybody would just go back to 00:23:45.640 --> 00:23:49.029 align:start position:0% then everybody would just go back to having<00:23:45.919> State<00:23:46.360> stateful<00:23:46.880> clients<00:23:47.720> so<00:23:48.600> yeah 00:23:49.029 --> 00:23:49.039 align:start position:0% having State stateful clients so yeah 00:23:49.039 --> 00:23:51.149 align:start position:0% having State stateful clients so yeah that<00:23:49.159> would<00:23:49.320> be<00:23:49.440> a<00:23:49.559> usability<00:23:50.159> drop<00:23:50.919> uh 00:23:51.149 --> 00:23:51.159 align:start position:0% that would be a usability drop uh 00:23:51.159 --> 00:23:54.590 align:start position:0% that would be a usability drop uh potentially<00:23:52.039> um<00:23:53.000> you<00:23:53.159> know<00:23:53.880> a<00:23:54.000> big<00:23:54.279> headache 00:23:54.590 --> 00:23:54.600 align:start position:0% potentially um you know a big headache 00:23:54.600 --> 00:23:57.269 align:start position:0% potentially um you know a big headache for<00:23:54.919> core<00:23:55.200> developers<00:23:55.880> But<00:23:56.600> ultimately 00:23:57.269 --> 00:23:57.279 align:start position:0% for core developers But ultimately 00:23:57.279 --> 00:23:59.630 align:start position:0% for core developers But ultimately that's<00:23:57.440> a<00:23:57.600> big<00:23:57.799> price<00:23:58.000> to<00:23:58.159> pay<00:23:58.520> to<00:23:58.960> to<00:23:59.240> just 00:23:59.630 --> 00:23:59.640 align:start position:0% that's a big price to pay to to just 00:23:59.640 --> 00:24:02.789 align:start position:0% that's a big price to pay to to just annoy<00:24:00.159> a<00:24:00.279> few<00:24:00.840> people<00:24:01.840> what<00:24:02.000> about<00:24:02.279> Legacy 00:24:02.789 --> 00:24:02.799 align:start position:0% annoy a few people what about Legacy 00:24:02.799 --> 00:24:05.390 align:start position:0% annoy a few people what about Legacy data<00:24:03.360> if<00:24:03.840> uh<00:24:04.200> veral<00:24:04.559> trees<00:24:04.760> are<00:24:04.919> adopted<00:24:05.240> on 00:24:05.390 --> 00:24:05.400 align:start position:0% data if uh veral trees are adopted on 00:24:05.400 --> 00:24:08.350 align:start position:0% data if uh veral trees are adopted on Main<00:24:05.640> net<00:24:06.120> the<00:24:06.200> whole<00:24:06.440> thing<00:24:06.640> is<00:24:07.120> converted<00:24:08.120> uh 00:24:08.350 --> 00:24:08.360 align:start position:0% Main net the whole thing is converted uh 00:24:08.360 --> 00:24:10.470 align:start position:0% Main net the whole thing is converted uh so<00:24:08.799> nothing<00:24:09.080> is 00:24:10.470 --> 00:24:10.480 align:start position:0% so nothing is 00:24:10.480 --> 00:24:12.909 align:start position:0% so nothing is lost<00:24:11.480> okay<00:24:12.120> uh<00:24:12.240> what's<00:24:12.440> your<00:24:12.600> opinion 00:24:12.909 --> 00:24:12.919 align:start position:0% lost okay uh what's your opinion 00:24:12.919 --> 00:24:14.750 align:start position:0% lost okay uh what's your opinion regarding<00:24:13.279> the<00:24:13.400> post<00:24:13.720> by<00:24:13.919> vitalic<00:24:14.400> to<00:24:14.559> wait 00:24:14.750 --> 00:24:14.760 align:start position:0% regarding the post by vitalic to wait 00:24:14.760 --> 00:24:16.789 align:start position:0% regarding the post by vitalic to wait longer<00:24:15.080> and<00:24:15.240> do<00:24:15.440> more<00:24:15.679> research<00:24:16.080> into<00:24:16.360> ZK 00:24:16.789 --> 00:24:16.799 align:start position:0% longer and do more research into ZK 00:24:16.799 --> 00:24:19.110 align:start position:0% longer and do more research into ZK instead<00:24:17.000> of<00:24:17.080> doing<00:24:17.279> veral<00:24:17.720> trees<00:24:18.000> soon<00:24:18.880> uh<00:24:19.039> I 00:24:19.110 --> 00:24:19.120 align:start position:0% instead of doing veral trees soon uh I 00:24:19.120 --> 00:24:24.590 align:start position:0% instead of doing veral trees soon uh I mean<00:24:19.360> the<00:24:19.480> whole<00:24:19.760> presentation<00:24:20.760> uh<00:24:20.880> is<00:24:21.039> my 00:24:24.590 --> 00:24:24.600 align:start position:0% 00:24:24.600 --> 00:24:27.710 align:start position:0% answer<00:24:25.600> but<00:24:25.760> to<00:24:25.840> be<00:24:26.000> fair<00:24:26.399> just<00:24:26.799> uh<00:24:27.000> vitalic 00:24:27.710 --> 00:24:27.720 align:start position:0% answer but to be fair just uh vitalic 00:24:27.720 --> 00:24:29.149 align:start position:0% answer but to be fair just uh vitalic you<00:24:27.799> know<00:24:27.919> is<00:24:28.039> more<00:24:28.200> like 00:24:29.149 --> 00:24:29.159 align:start position:0% you know is more like 00:24:29.159 --> 00:24:31.350 align:start position:0% you know is more like it's<00:24:29.399> a<00:24:29.559> it's<00:24:29.679> an<00:24:29.880> idea<00:24:30.240> it's<00:24:30.399> not<00:24:30.679> like<00:24:31.240> it's 00:24:31.350 --> 00:24:31.360 align:start position:0% it's a it's an idea it's not like it's 00:24:31.360 --> 00:24:34.350 align:start position:0% it's a it's an idea it's not like it's not<00:24:31.520> like<00:24:31.720> he's<00:24:32.480> hardcore<00:24:33.039> decided<00:24:33.399> on<00:24:33.559> it<00:24:34.240> I 00:24:34.350 --> 00:24:34.360 align:start position:0% not like he's hardcore decided on it I 00:24:34.360 --> 00:24:36.549 align:start position:0% not like he's hardcore decided on it I have<00:24:34.440> a<00:24:34.600> screenshot<00:24:35.159> that<00:24:35.320> says<00:24:35.919> veral<00:24:36.399> might 00:24:36.549 --> 00:24:36.559 align:start position:0% have a screenshot that says veral might 00:24:36.559 --> 00:24:38.149 align:start position:0% have a screenshot that says veral might be<00:24:36.679> the<00:24:36.799> last<00:24:37.039> thing<00:24:37.279> that<00:24:37.440> we<00:24:37.559> do<00:24:37.760> that<00:24:37.880> is<00:24:38.000> not 00:24:38.149 --> 00:24:38.159 align:start position:0% be the last thing that we do that is not 00:24:38.159 --> 00:24:39.110 align:start position:0% be the last thing that we do that is not Quantum 00:24:39.110 --> 00:24:39.120 align:start position:0% Quantum 00:24:39.120 --> 00:24:41.190 align:start position:0% Quantum resistant<00:24:40.120> well<00:24:40.279> the<00:24:40.399> next<00:24:40.559> one's<00:24:40.840> more<00:24:41.000> of<00:24:41.080> a 00:24:41.190 --> 00:24:41.200 align:start position:0% resistant well the next one's more of a 00:24:41.200 --> 00:24:42.870 align:start position:0% resistant well the next one's more of a command<00:24:41.600> than<00:24:41.720> a<00:24:41.919> question<00:24:42.399> but<00:24:42.600> stop 00:24:42.870 --> 00:24:42.880 align:start position:0% command than a question but stop 00:24:42.880 --> 00:24:44.590 align:start position:0% command than a question but stop delaying<00:24:43.240> veral<00:24:43.679> and<00:24:43.799> ship<00:24:44.039> it<00:24:44.159> instead<00:24:44.440> of 00:24:44.590 --> 00:24:44.600 align:start position:0% delaying veral and ship it instead of 00:24:44.600 --> 00:24:46.870 align:start position:0% delaying veral and ship it instead of other<00:24:44.880> non-urgent<00:24:45.279> features<00:24:45.880> do<00:24:46.000> you<00:24:46.159> have 00:24:46.870 --> 00:24:46.880 align:start position:0% other non-urgent features do you have 00:24:46.880 --> 00:24:50.310 align:start position:0% other non-urgent features do you have would<00:24:47.000> you<00:24:47.120> like<00:24:47.360> to<00:24:47.559> comment<00:24:47.840> on<00:24:48.559> no<00:24:49.200> no<00:24:50.200> I 00:24:50.310 --> 00:24:50.320 align:start position:0% would you like to comment on no no I 00:24:50.320 --> 00:24:52.669 align:start position:0% would you like to comment on no no I think<00:24:50.760> people<00:24:51.000> know<00:24:51.200> my<00:24:51.399> opinion<00:24:51.799> that's<00:24:52.159> uh 00:24:52.669 --> 00:24:52.679 align:start position:0% think people know my opinion that's uh 00:24:52.679 --> 00:24:55.269 align:start position:0% think people know my opinion that's uh enough<00:24:52.960> has<00:24:53.080> been<00:24:53.279> said<00:24:54.039> okay<00:24:54.320> great<00:24:54.840> and<00:24:55.120> how 00:24:55.269 --> 00:24:55.279 align:start position:0% enough has been said okay great and how 00:24:55.279 --> 00:24:57.549 align:start position:0% enough has been said okay great and how does<00:24:55.640> PCS<00:24:56.360> multi<00:24:56.799> prooof<00:24:57.080> with<00:24:57.240> random 00:24:57.549 --> 00:24:57.559 align:start position:0% does PCS multi prooof with random 00:24:57.559 --> 00:24:59.590 align:start position:0% does PCS multi prooof with random evaluation<00:24:58.039> work<00:24:58.440> on<00:24:58.559> veral<00:24:58.919> trees<00:24:59.200> I<00:24:59.320> tried 00:24:59.590 --> 00:24:59.600 align:start position:0% evaluation work on veral trees I tried 00:24:59.600 --> 00:25:01.350 align:start position:0% evaluation work on veral trees I tried hard<00:24:59.799> but<00:24:59.919> I'm<00:25:00.360> too<00:25:00.559> stupid<00:25:00.840> to<00:25:01.200> understand 00:25:01.350 --> 00:25:01.360 align:start position:0% hard but I'm too stupid to understand 00:25:01.360 --> 00:25:06.190 align:start position:0% hard but I'm too stupid to understand CRI<00:25:01.679> oji<00:25:01.919> *<00:25:02.200> 2<00:25:03.240> um<00:25:04.240> yeah<00:25:04.679> it's<00:25:05.000> quite<00:25:05.279> hard<00:25:05.880> uh 00:25:06.190 --> 00:25:06.200 align:start position:0% CRI oji * 2 um yeah it's quite hard uh 00:25:06.200 --> 00:25:08.830 align:start position:0% CRI oji * 2 um yeah it's quite hard uh we<00:25:06.880> we<00:25:07.000> can<00:25:07.200> definitely<00:25:07.600> explain<00:25:08.399> uh<00:25:08.600> just 00:25:08.830 --> 00:25:08.840 align:start position:0% we we can definitely explain uh just 00:25:08.840 --> 00:25:12.430 align:start position:0% we we can definitely explain uh just maybe<00:25:09.080> not<00:25:09.320> in<00:25:09.480> 37<00:25:10.240> seconds<00:25:11.240> okay<00:25:11.720> and<00:25:12.120> as<00:25:12.240> a 00:25:12.430 --> 00:25:12.440 align:start position:0% maybe not in 37 seconds okay and as a 00:25:12.440 --> 00:25:14.710 align:start position:0% maybe not in 37 seconds okay and as a last<00:25:12.679> one<00:25:13.240> uh<00:25:13.399> what<00:25:13.480> is<00:25:13.600> your<00:25:13.799> take<00:25:14.120> on<00:25:14.399> the 00:25:14.710 --> 00:25:14.720 align:start position:0% last one uh what is your take on the 00:25:14.720 --> 00:25:18.269 align:start position:0% last one uh what is your take on the bandwidth<00:25:15.600> disc<00:25:16.000> trade-off<00:25:17.000> I<00:25:17.120> think<00:25:17.640> uh<00:25:18.039> well 00:25:18.269 --> 00:25:18.279 align:start position:0% bandwidth disc trade-off I think uh well 00:25:18.279 --> 00:25:20.230 align:start position:0% bandwidth disc trade-off I think uh well bandwidth<00:25:18.840> is<00:25:19.000> going<00:25:19.159> to<00:25:19.640> be<00:25:19.799> the<00:25:19.960> biggest 00:25:20.230 --> 00:25:20.240 align:start position:0% bandwidth is going to be the biggest 00:25:20.240 --> 00:25:21.830 align:start position:0% bandwidth is going to be the biggest resource<00:25:20.640> in<00:25:20.720> the<00:25:20.840> future<00:25:21.320> my<00:25:21.520> just<00:25:21.679> my 00:25:21.830 --> 00:25:21.840 align:start position:0% resource in the future my just my 00:25:21.840 --> 00:25:25.269 align:start position:0% resource in the future my just my personal<00:25:22.279> opinion<00:25:23.279> um<00:25:23.679> so<00:25:24.240> whatever<00:25:25.039> uh 00:25:25.269 --> 00:25:25.279 align:start position:0% personal opinion um so whatever uh 00:25:25.279 --> 00:25:27.470 align:start position:0% personal opinion um so whatever uh whatever<00:25:25.600> makes<00:25:26.240> uh<00:25:26.480> improves<00:25:26.880> the<00:25:26.960> bandwidth 00:25:27.470 --> 00:25:27.480 align:start position:0% whatever makes uh improves the bandwidth 00:25:27.480 --> 00:25:30.830 align:start position:0% whatever makes uh improves the bandwidth requirement<00:25:27.960> is<00:25:28.120> is<00:25:28.320> is<00:25:28.399> a<00:25:28.520> good<00:25:28.799> thing<00:25:29.799> um<00:25:30.200> dis 00:25:30.830 --> 00:25:30.840 align:start position:0% requirement is is is a good thing um dis 00:25:30.840 --> 00:25:33.389 align:start position:0% requirement is is is a good thing um dis is<00:25:31.000> also<00:25:31.240> a<00:25:31.399> good<00:25:31.600> thing<00:25:32.320> uh<00:25:32.640> but<00:25:32.919> I<00:25:33.000> think<00:25:33.200> at 00:25:33.389 --> 00:25:33.399 align:start position:0% is also a good thing uh but I think at 00:25:33.399 --> 00:25:35.029 align:start position:0% is also a good thing uh but I think at this<00:25:33.559> point<00:25:33.760> veral<00:25:34.200> is<00:25:34.320> going<00:25:34.480> to<00:25:34.640> come<00:25:34.840> too 00:25:35.029 --> 00:25:35.039 align:start position:0% this point veral is going to come too 00:25:35.039 --> 00:25:38.389 align:start position:0% this point veral is going to come too late<00:25:35.320> to<00:25:36.000> prevent<00:25:36.760> the<00:25:37.360> the<00:25:37.480> switch<00:25:37.760> to 00:25:38.389 --> 00:25:38.399 align:start position:0% late to prevent the the switch to 00:25:38.399 --> 00:25:41.990 align:start position:0% late to prevent the the switch to requiring<00:25:39.240> 4<00:25:39.520> terabyte<00:25:40.399> hard<00:25:40.840> drive<00:25:41.840> all 00:25:41.990 --> 00:25:42.000 align:start position:0% requiring 4 terabyte hard drive all 00:25:42.000 --> 00:25:43.470 align:start position:0% requiring 4 terabyte hard drive all right<00:25:42.399> that's<00:25:42.559> it<00:25:42.720> for<00:25:42.880> questions<00:25:43.240> thank<00:25:43.399> you 00:25:43.470 --> 00:25:43.480 align:start position:0% right that's it for questions thank you 00:25:43.480 --> 00:25:45.679 align:start position:0% right that's it for questions thank you very