WEBVTT Kind: captions Language: en 00:00:02.870 --> 00:00:08.910 align:start position:0% [Music] 00:00:08.910 --> 00:00:08.920 align:start position:0% 00:00:08.920 --> 00:00:11.070 align:start position:0% uh<00:00:09.120> hello<00:00:09.679> uh<00:00:09.760> so<00:00:09.960> I'm<00:00:10.080> Orin<00:00:10.480> I'm<00:00:10.800> uh<00:00:10.920> from 00:00:11.070 --> 00:00:11.080 align:start position:0% uh hello uh so I'm Orin I'm uh from 00:00:11.080 --> 00:00:13.030 align:start position:0% uh hello uh so I'm Orin I'm uh from starkware<00:00:12.000> and<00:00:12.120> starkware<00:00:12.559> is<00:00:12.679> one<00:00:12.799> of<00:00:12.920> the 00:00:13.030 --> 00:00:13.040 align:start position:0% starkware and starkware is one of the 00:00:13.040 --> 00:00:15.829 align:start position:0% starkware and starkware is one of the main<00:00:13.280> teams<00:00:13.839> building<00:00:14.160> Stark<00:00:14.519> net<00:00:14.759> which<00:00:14.879> is<00:00:15.080> a 00:00:15.829 --> 00:00:15.839 align:start position:0% main teams building Stark net which is a 00:00:15.839 --> 00:00:18.070 align:start position:0% main teams building Stark net which is a public<00:00:16.199> general<00:00:16.520> purpose<00:00:17.160> zarola<00:00:17.720> built<00:00:17.920> on 00:00:18.070 --> 00:00:18.080 align:start position:0% public general purpose zarola built on 00:00:18.080 --> 00:00:20.429 align:start position:0% public general purpose zarola built on top<00:00:18.240> of<00:00:18.680> ethereum<00:00:19.680> and<00:00:19.840> what<00:00:19.960> I<00:00:20.039> want<00:00:20.160> to<00:00:20.279> do 00:00:20.429 --> 00:00:20.439 align:start position:0% top of ethereum and what I want to do 00:00:20.439 --> 00:00:24.950 align:start position:0% top of ethereum and what I want to do here<00:00:20.560> is<00:00:20.720> share<00:00:21.080> some<00:00:21.279> of 00:00:24.950 --> 00:00:24.960 align:start position:0% 00:00:24.960 --> 00:00:29.429 align:start position:0% our<00:00:25.960> do<00:00:26.160> I<00:00:26.320> need<00:00:26.840> to<00:00:27.840> yeah<00:00:28.320> it<00:00:28.480> share<00:00:28.840> some<00:00:29.039> of 00:00:29.429 --> 00:00:29.439 align:start position:0% our do I need to yeah it share some of 00:00:29.439 --> 00:00:32.069 align:start position:0% our do I need to yeah it share some of our<00:00:29.720> things<00:00:30.279> around<00:00:30.599> how<00:00:30.759> to<00:00:31.000> build<00:00:31.840> like<00:00:32.000> a 00:00:32.069 --> 00:00:32.079 align:start position:0% our things around how to build like a 00:00:32.079 --> 00:00:34.830 align:start position:0% our things around how to build like a rollup<00:00:32.520> which<00:00:32.640> is<00:00:32.880> a<00:00:33.320> uh<00:00:33.640> indeed<00:00:33.960> future<00:00:34.399> proof 00:00:34.830 --> 00:00:34.840 align:start position:0% rollup which is a uh indeed future proof 00:00:34.840 --> 00:00:36.270 align:start position:0% rollup which is a uh indeed future proof and<00:00:34.960> we're<00:00:35.120> building<00:00:35.399> it<00:00:35.520> using<00:00:35.800> proof<00:00:36.120> so 00:00:36.270 --> 00:00:36.280 align:start position:0% and we're building it using proof so 00:00:36.280 --> 00:00:38.430 align:start position:0% and we're building it using proof so there<00:00:36.399> is<00:00:36.520> some<00:00:36.640> double<00:00:36.879> meaning<00:00:37.280> here<00:00:38.160> uh<00:00:38.280> now 00:00:38.430 --> 00:00:38.440 align:start position:0% there is some double meaning here uh now 00:00:38.440 --> 00:00:39.709 align:start position:0% there is some double meaning here uh now another<00:00:38.760> angle<00:00:39.040> of<00:00:39.160> this<00:00:39.280> is<00:00:39.440> if<00:00:39.520> you're 00:00:39.709 --> 00:00:39.719 align:start position:0% another angle of this is if you're 00:00:39.719 --> 00:00:41.430 align:start position:0% another angle of this is if you're building<00:00:40.039> an<00:00:40.239> app<00:00:40.440> and<00:00:40.559> you're<00:00:40.920> thinking<00:00:41.280> of 00:00:41.430 --> 00:00:41.440 align:start position:0% building an app and you're thinking of 00:00:41.440 --> 00:00:43.790 align:start position:0% building an app and you're thinking of which<00:00:41.640> chain<00:00:41.920> you<00:00:42.000> should<00:00:42.200> Deploy<00:00:42.520> on<00:00:43.360> uh<00:00:43.680> this 00:00:43.790 --> 00:00:43.800 align:start position:0% which chain you should Deploy on uh this 00:00:43.800 --> 00:00:45.110 align:start position:0% which chain you should Deploy on uh this should<00:00:44.000> also<00:00:44.239> tell<00:00:44.440> you<00:00:44.559> some<00:00:44.719> of<00:00:44.800> the<00:00:44.920> things 00:00:45.110 --> 00:00:45.120 align:start position:0% should also tell you some of the things 00:00:45.120 --> 00:00:51.349 align:start position:0% should also tell you some of the things you<00:00:45.600> probably<00:00:45.840> should<00:00:46.039> be<00:00:46.239> thinking 00:00:51.349 --> 00:00:51.359 align:start position:0% 00:00:51.359 --> 00:00:54.229 align:start position:0% about<00:00:52.359> not 00:00:54.229 --> 00:00:54.239 align:start position:0% about not 00:00:54.239 --> 00:00:56.349 align:start position:0% about not working<00:00:55.239> okay<00:00:55.600> so<00:00:55.800> this<00:00:55.879> is<00:00:56.000> what<00:00:56.160> I'm<00:00:56.239> going 00:00:56.349 --> 00:00:56.359 align:start position:0% working okay so this is what I'm going 00:00:56.359 --> 00:00:59.389 align:start position:0% working okay so this is what I'm going to<00:00:56.520> cover<00:00:57.320> uh<00:00:57.680> briefly<00:00:58.120> how<00:00:58.359> we<00:00:58.519> see<00:00:58.840> web<00:00:59.079> 3 00:00:59.389 --> 00:00:59.399 align:start position:0% to cover uh briefly how we see web 3 00:00:59.399 --> 00:01:00.509 align:start position:0% to cover uh briefly how we see web 3 today 00:01:00.509 --> 00:01:00.519 align:start position:0% today 00:01:00.519 --> 00:01:02.910 align:start position:0% today uh<00:01:01.239> touch<00:01:01.559> some<00:01:01.760> types<00:01:02.000> of<00:01:02.160> networks<00:01:02.559> that<00:01:02.680> are 00:01:02.910 --> 00:01:02.920 align:start position:0% uh touch some types of networks that are 00:01:02.920 --> 00:01:04.189 align:start position:0% uh touch some types of networks that are there<00:01:03.039> you<00:01:03.239> probably<00:01:03.399> heard<00:01:03.640> layer<00:01:03.920> ones 00:01:04.189 --> 00:01:04.199 align:start position:0% there you probably heard layer ones 00:01:04.199 --> 00:01:06.149 align:start position:0% there you probably heard layer ones layer<00:01:04.479> twos<00:01:04.839> validity<00:01:05.239> rollups<00:01:05.680> optimistic 00:01:06.149 --> 00:01:06.159 align:start position:0% layer twos validity rollups optimistic 00:01:06.159 --> 00:01:07.950 align:start position:0% layer twos validity rollups optimistic rollups<00:01:06.760> public<00:01:07.000> chains<00:01:07.400> app<00:01:07.560> chains<00:01:07.799> I'm 00:01:07.950 --> 00:01:07.960 align:start position:0% rollups public chains app chains I'm 00:01:07.960 --> 00:01:10.230 align:start position:0% rollups public chains app chains I'm going<00:01:08.040> to<00:01:08.119> touch<00:01:08.400> that<00:01:08.560> a<00:01:08.680> bit<00:01:09.439> and<00:01:09.600> then<00:01:10.119> uh 00:01:10.230 --> 00:01:10.240 align:start position:0% going to touch that a bit and then uh 00:01:10.240 --> 00:01:12.270 align:start position:0% going to touch that a bit and then uh I'll<00:01:10.400> mention<00:01:10.840> the<00:01:11.000> few<00:01:11.320> aspects<00:01:11.720> that<00:01:12.080> we 00:01:12.270 --> 00:01:12.280 align:start position:0% I'll mention the few aspects that we 00:01:12.280 --> 00:01:13.510 align:start position:0% I'll mention the few aspects that we think<00:01:12.479> at<00:01:12.600> least<00:01:12.799> are<00:01:12.960> important<00:01:13.280> in<00:01:13.360> the 00:01:13.510 --> 00:01:13.520 align:start position:0% think at least are important in the 00:01:13.520 --> 00:01:16.230 align:start position:0% think at least are important in the chain<00:01:14.200> some<00:01:14.360> of<00:01:14.479> them<00:01:14.640> are<00:01:14.759> like<00:01:14.960> the<00:01:15.240> harder 00:01:16.230 --> 00:01:16.240 align:start position:0% chain some of them are like the harder 00:01:16.240 --> 00:01:18.429 align:start position:0% chain some of them are like the harder uh<00:01:16.400> technology<00:01:16.960> and<00:01:17.159> infrastructure<00:01:17.880> stuff 00:01:18.429 --> 00:01:18.439 align:start position:0% uh technology and infrastructure stuff 00:01:18.439 --> 00:01:20.190 align:start position:0% uh technology and infrastructure stuff some<00:01:18.720> which<00:01:18.840> are<00:01:19.000> not<00:01:19.240> less<00:01:19.520> important<00:01:20.000> are 00:01:20.190 --> 00:01:20.200 align:start position:0% some which are not less important are 00:01:20.200 --> 00:01:22.190 align:start position:0% some which are not less important are more<00:01:20.479> around<00:01:20.840> Vision<00:01:21.280> Values<00:01:21.640> and<00:01:21.799> Community 00:01:22.190 --> 00:01:22.200 align:start position:0% more around Vision Values and Community 00:01:22.200 --> 00:01:27.749 align:start position:0% more around Vision Values and Community the<00:01:22.360> softer 00:01:27.749 --> 00:01:27.759 align:start position:0% 00:01:27.759 --> 00:01:30.950 align:start position:0% aspects<00:01:28.759> okay<00:01:29.000> so<00:01:29.240> we<00:01:29.400> probably<00:01:29.640> know<00:01:30.079> this<00:01:30.520> uh 00:01:30.950 --> 00:01:30.960 align:start position:0% aspects okay so we probably know this uh 00:01:30.960 --> 00:01:33.910 align:start position:0% aspects okay so we probably know this uh uh<00:01:31.200> graph<00:01:32.159> uh<00:01:32.399> what<00:01:32.560> I<00:01:32.680> would<00:01:32.880> like<00:01:33.240> to<00:01:33.479> claim 00:01:33.910 --> 00:01:33.920 align:start position:0% uh graph uh what I would like to claim 00:01:33.920 --> 00:01:36.230 align:start position:0% uh graph uh what I would like to claim is<00:01:34.079> that<00:01:34.479> blockchain<00:01:35.079> today<00:01:35.520> is<00:01:35.680> still<00:01:35.880> in<00:01:36.079> one 00:01:36.230 --> 00:01:36.240 align:start position:0% is that blockchain today is still in one 00:01:36.240 --> 00:01:39.270 align:start position:0% is that blockchain today is still in one of<00:01:36.439> these<00:01:37.119> leftmost<00:01:38.000> phases<00:01:38.600> it<00:01:38.720> still<00:01:39.079> has 00:01:39.270 --> 00:01:39.280 align:start position:0% of these leftmost phases it still has 00:01:39.280 --> 00:01:41.749 align:start position:0% of these leftmost phases it still has not<00:01:40.240> made<00:01:40.439> it<00:01:40.560> to 00:01:41.749 --> 00:01:41.759 align:start position:0% not made it to 00:01:41.759 --> 00:01:44.190 align:start position:0% not made it to mainstream<00:01:42.759> uh<00:01:43.320> and<00:01:43.600> why<00:01:43.759> aren't<00:01:44.040> we 00:01:44.190 --> 00:01:44.200 align:start position:0% mainstream uh and why aren't we 00:01:44.200 --> 00:01:45.910 align:start position:0% mainstream uh and why aren't we mainstream<00:01:44.759> yet<00:01:44.960> well<00:01:45.119> a<00:01:45.200> large<00:01:45.479> part<00:01:45.600> of<00:01:45.719> it 00:01:45.910 --> 00:01:45.920 align:start position:0% mainstream yet well a large part of it 00:01:45.920 --> 00:01:48.069 align:start position:0% mainstream yet well a large part of it is<00:01:46.159> that<00:01:46.719> the<00:01:46.880> infrastructure<00:01:47.479> is<00:01:47.640> not<00:01:47.880> there 00:01:48.069 --> 00:01:48.079 align:start position:0% is that the infrastructure is not there 00:01:48.079 --> 00:01:49.709 align:start position:0% is that the infrastructure is not there or<00:01:48.240> it<00:01:48.399> at<00:01:48.479> least<00:01:48.759> wasn't<00:01:49.079> there<00:01:49.200> until 00:01:49.709 --> 00:01:49.719 align:start position:0% or it at least wasn't there until 00:01:49.719 --> 00:01:52.310 align:start position:0% or it at least wasn't there until recently<00:01:50.719> especially<00:01:51.119> in<00:01:51.240> terms<00:01:51.479> of<00:01:51.680> scale 00:01:52.310 --> 00:01:52.320 align:start position:0% recently especially in terms of scale 00:01:52.320 --> 00:01:55.149 align:start position:0% recently especially in terms of scale cost<00:01:52.640> and<00:01:53.119> ux<00:01:54.119> and<00:01:54.240> the<00:01:54.360> thing<00:01:54.560> that's<00:01:54.799> greatly 00:01:55.149 --> 00:01:55.159 align:start position:0% cost and ux and the thing that's greatly 00:01:55.159 --> 00:01:57.789 align:start position:0% cost and ux and the thing that's greatly needed<00:01:55.640> is<00:01:56.200> some<00:01:56.399> killer<00:01:56.759> apps<00:01:57.320> like<00:01:57.560> there 00:01:57.789 --> 00:01:57.799 align:start position:0% needed is some killer apps like there 00:01:57.799 --> 00:01:59.510 align:start position:0% needed is some killer apps like there there<00:01:58.000> really<00:01:58.200> aren't<00:01:58.600> that<00:01:58.759> many<00:01:59.000> kill<00:01:59.280> or 00:01:59.510 --> 00:01:59.520 align:start position:0% there really aren't that many kill or 00:01:59.520 --> 00:02:01.230 align:start position:0% there really aren't that many kill or probably<00:01:59.960> aren't<00:02:00.159> any<00:02:00.360> killer<00:02:00.719> apps<00:02:01.079> right 00:02:01.230 --> 00:02:01.240 align:start position:0% probably aren't any killer apps right 00:02:01.240 --> 00:02:05.149 align:start position:0% probably aren't any killer apps right now<00:02:01.360> in<00:02:01.520> crypto<00:02:01.920> that<00:02:02.079> has<00:02:02.280> made<00:02:02.479> it<00:02:02.759> main 00:02:05.149 --> 00:02:05.159 align:start position:0% 00:02:05.159 --> 00:02:07.350 align:start position:0% mainstream<00:02:06.159> okay<00:02:06.360> so<00:02:06.520> we<00:02:06.640> have<00:02:06.799> layer<00:02:07.119> ones 00:02:07.350 --> 00:02:07.360 align:start position:0% mainstream okay so we have layer ones 00:02:07.360 --> 00:02:10.109 align:start position:0% mainstream okay so we have layer ones and<00:02:07.520> layer<00:02:07.880> twos<00:02:08.840> uh<00:02:09.399> generally<00:02:09.800> speaking 00:02:10.109 --> 00:02:10.119 align:start position:0% and layer twos uh generally speaking 00:02:10.119 --> 00:02:12.309 align:start position:0% and layer twos uh generally speaking ethereum<00:02:10.759> and<00:02:10.879> and<00:02:11.039> also<00:02:11.360> Bitcoin<00:02:11.879> are<00:02:12.080> really 00:02:12.309 --> 00:02:12.319 align:start position:0% ethereum and and also Bitcoin are really 00:02:12.319 --> 00:02:14.110 align:start position:0% ethereum and and also Bitcoin are really great<00:02:12.560> layer<00:02:12.840> ones<00:02:13.200> vitalic<00:02:13.599> mentioned<00:02:13.920> it 00:02:14.110 --> 00:02:14.120 align:start position:0% great layer ones vitalic mentioned it 00:02:14.120 --> 00:02:16.110 align:start position:0% great layer ones vitalic mentioned it his<00:02:14.280> opening<00:02:14.959> yesterday<00:02:15.400> layer<00:02:15.680> one<00:02:15.959> is 00:02:16.110 --> 00:02:16.120 align:start position:0% his opening yesterday layer one is 00:02:16.120 --> 00:02:18.710 align:start position:0% his opening yesterday layer one is really<00:02:16.360> the<00:02:16.519> trust<00:02:17.319> machine<00:02:18.319> uh<00:02:18.440> they're 00:02:18.710 --> 00:02:18.720 align:start position:0% really the trust machine uh they're 00:02:18.720 --> 00:02:20.309 align:start position:0% really the trust machine uh they're secure<00:02:19.160> they're<00:02:19.400> decentralized 00:02:20.309 --> 00:02:20.319 align:start position:0% secure they're decentralized 00:02:20.319 --> 00:02:22.070 align:start position:0% secure they're decentralized permissionless<00:02:21.000> censorship<00:02:21.519> resistant 00:02:22.070 --> 00:02:22.080 align:start position:0% permissionless censorship resistant 00:02:22.080 --> 00:02:24.630 align:start position:0% permissionless censorship resistant credibly<00:02:22.480> neutral<00:02:22.840> all<00:02:23.080> those<00:02:23.280> nice<00:02:23.560> words<00:02:24.560> uh 00:02:24.630 --> 00:02:24.640 align:start position:0% credibly neutral all those nice words uh 00:02:24.640 --> 00:02:26.110 align:start position:0% credibly neutral all those nice words uh but<00:02:24.760> they<00:02:24.879> also<00:02:25.080> have<00:02:25.319> strong<00:02:25.480> networks<00:02:26.000> they 00:02:26.110 --> 00:02:26.120 align:start position:0% but they also have strong networks they 00:02:26.120 --> 00:02:27.710 align:start position:0% but they also have strong networks they have<00:02:26.239> lots<00:02:26.440> of<00:02:26.519> users<00:02:26.920> lots<00:02:27.120> of<00:02:27.239> operators 00:02:27.710 --> 00:02:27.720 align:start position:0% have lots of users lots of operators 00:02:27.720 --> 00:02:29.350 align:start position:0% have lots of users lots of operators lots<00:02:27.920> of<00:02:28.040> liquidity<00:02:28.480> writing<00:02:28.800> on<00:02:28.920> top<00:02:29.080> of<00:02:29.200> them 00:02:29.350 --> 00:02:29.360 align:start position:0% lots of liquidity writing on top of them 00:02:29.360 --> 00:02:31.589 align:start position:0% lots of liquidity writing on top of them they're<00:02:30.000> usually<00:02:30.280> field<00:02:30.720> proven<00:02:31.280> lots<00:02:31.440> of 00:02:31.589 --> 00:02:31.599 align:start position:0% they're usually field proven lots of 00:02:31.599 --> 00:02:34.710 align:start position:0% they're usually field proven lots of apps<00:02:31.879> writing<00:02:32.200> on<00:02:32.360> top<00:02:32.519> of<00:02:32.720> them<00:02:33.720> but<00:02:34.640> uh 00:02:34.710 --> 00:02:34.720 align:start position:0% apps writing on top of them but uh 00:02:34.720 --> 00:02:37.070 align:start position:0% apps writing on top of them but uh they're<00:02:34.959> severely<00:02:35.400> limited<00:02:36.080> and<00:02:36.200> mainly<00:02:36.840> from 00:02:37.070 --> 00:02:37.080 align:start position:0% they're severely limited and mainly from 00:02:37.080 --> 00:02:38.949 align:start position:0% they're severely limited and mainly from these<00:02:37.360> aspects<00:02:37.720> in<00:02:37.879> terms<00:02:38.120> of<00:02:38.280> scale<00:02:38.640> in<00:02:38.760> terms 00:02:38.949 --> 00:02:38.959 align:start position:0% these aspects in terms of scale in terms 00:02:38.959 --> 00:02:42.830 align:start position:0% these aspects in terms of scale in terms of<00:02:39.239> cost<00:02:39.879> and<00:02:40.080> also<00:02:40.280> in<00:02:40.440> terms<00:02:40.680> of 00:02:42.830 --> 00:02:42.840 align:start position:0% of cost and also in terms of 00:02:42.840 --> 00:02:45.630 align:start position:0% of cost and also in terms of ux<00:02:43.840> so<00:02:44.040> you<00:02:44.200> have<00:02:44.560> then<00:02:44.680> you<00:02:44.800> have<00:02:44.959> some<00:02:45.400> other 00:02:45.630 --> 00:02:45.640 align:start position:0% ux so you have then you have some other 00:02:45.640 --> 00:02:49.229 align:start position:0% ux so you have then you have some other lay<00:02:46.040> ones<00:02:46.480> that<00:02:46.840> apparently<00:02:47.319> solve<00:02:48.040> this<00:02:49.040> but 00:02:49.229 --> 00:02:49.239 align:start position:0% lay ones that apparently solve this but 00:02:49.239 --> 00:02:51.350 align:start position:0% lay ones that apparently solve this but if<00:02:49.319> you<00:02:49.480> look<00:02:49.680> closely<00:02:50.440> they<00:02:50.599> usually<00:02:50.879> do<00:02:51.159> that 00:02:51.350 --> 00:02:51.360 align:start position:0% if you look closely they usually do that 00:02:51.360 --> 00:02:54.110 align:start position:0% if you look closely they usually do that by<00:02:51.720> compromising<00:02:52.720> the<00:02:52.920> trust<00:02:53.640> so<00:02:53.920> they're 00:02:54.110 --> 00:02:54.120 align:start position:0% by compromising the trust so they're 00:02:54.120 --> 00:02:55.790 align:start position:0% by compromising the trust so they're either<00:02:54.519> not<00:02:54.720> decentralized<00:02:55.360> or<00:02:55.560> less 00:02:55.790 --> 00:02:55.800 align:start position:0% either not decentralized or less 00:02:55.800 --> 00:02:59.550 align:start position:0% either not decentralized or less decentralized<00:02:56.519> or<00:02:56.720> less<00:02:57.319> secure<00:02:58.319> uh<00:02:59.239> so<00:02:59.400> you 00:02:59.550 --> 00:02:59.560 align:start position:0% decentralized or less secure uh so you 00:02:59.560 --> 00:03:02.190 align:start position:0% decentralized or less secure uh so you give<00:02:59.959> something<00:03:00.319> out<00:03:00.840> for<00:03:01.120> for<00:03:01.560> uh<00:03:01.680> for<00:03:01.879> scale 00:03:02.190 --> 00:03:02.200 align:start position:0% give something out for for uh for scale 00:03:02.200 --> 00:03:05.229 align:start position:0% give something out for for uh for scale and<00:03:02.480> cost<00:03:03.319> what<00:03:03.480> layer<00:03:03.760> twos<00:03:04.120> try<00:03:04.400> to<00:03:04.560> do<00:03:05.080> is 00:03:05.229 --> 00:03:05.239 align:start position:0% and cost what layer twos try to do is 00:03:05.239 --> 00:03:07.949 align:start position:0% and cost what layer twos try to do is solve<00:03:05.519> these<00:03:05.720> limitation<00:03:06.400> on<00:03:06.920> a<00:03:07.080> second<00:03:07.400> layer 00:03:07.949 --> 00:03:07.959 align:start position:0% solve these limitation on a second layer 00:03:07.959 --> 00:03:10.470 align:start position:0% solve these limitation on a second layer the<00:03:08.159> the<00:03:08.280> scale<00:03:08.640> cost<00:03:08.879> and<00:03:09.040> ux<00:03:09.400> issues<00:03:09.680> and<00:03:10.280> but 00:03:10.470 --> 00:03:10.480 align:start position:0% the the scale cost and ux issues and but 00:03:10.480 --> 00:03:13.030 align:start position:0% the the scale cost and ux issues and but still<00:03:10.799> keep<00:03:11.480> the<00:03:11.640> trust<00:03:11.959> machine<00:03:12.440> on<00:03:12.840> those 00:03:13.030 --> 00:03:13.040 align:start position:0% still keep the trust machine on those 00:03:13.040 --> 00:03:15.670 align:start position:0% still keep the trust machine on those layer<00:03:13.599> ones<00:03:14.599> so<00:03:14.760> the<00:03:14.840> trust<00:03:15.120> machine<00:03:15.360> is<00:03:15.480> still 00:03:15.670 --> 00:03:15.680 align:start position:0% layer ones so the trust machine is still 00:03:15.680 --> 00:03:17.550 align:start position:0% layer ones so the trust machine is still ethereum<00:03:16.280> or<00:03:16.400> or<00:03:16.560> Bitcoin<00:03:16.920> I'll<00:03:17.080> mention<00:03:17.360> that 00:03:17.550 --> 00:03:17.560 align:start position:0% ethereum or or Bitcoin I'll mention that 00:03:17.560 --> 00:03:20.149 align:start position:0% ethereum or or Bitcoin I'll mention that later<00:03:18.560> uh<00:03:18.720> but<00:03:18.840> we<00:03:18.959> can<00:03:19.120> provide<00:03:19.519> scale<00:03:19.920> and 00:03:20.149 --> 00:03:20.159 align:start position:0% later uh but we can provide scale and 00:03:20.159 --> 00:03:22.270 align:start position:0% later uh but we can provide scale and and<00:03:20.319> and<00:03:20.560> cost<00:03:20.879> in<00:03:21.040> ux<00:03:21.400> better<00:03:21.640> scale<00:03:21.959> cost<00:03:22.159> in 00:03:22.270 --> 00:03:22.280 align:start position:0% and and cost in ux better scale cost in 00:03:22.280 --> 00:03:24.030 align:start position:0% and and cost in ux better scale cost in ux<00:03:22.640> on<00:03:22.760> a<00:03:22.959> on<00:03:23.040> a<00:03:23.159> different 00:03:24.030 --> 00:03:24.040 align:start position:0% ux on a on a different 00:03:24.040 --> 00:03:26.390 align:start position:0% ux on a on a different layer<00:03:25.040> you<00:03:25.200> probably<00:03:25.480> know<00:03:25.680> of<00:03:25.879> this<00:03:26.040> as<00:03:26.159> well 00:03:26.390 --> 00:03:26.400 align:start position:0% layer you probably know of this as well 00:03:26.400 --> 00:03:28.149 align:start position:0% layer you probably know of this as well this<00:03:26.480> is<00:03:26.640> the<00:03:26.760> blockchain<00:03:27.200> trilemma<00:03:28.000> it 00:03:28.149 --> 00:03:28.159 align:start position:0% this is the blockchain trilemma it 00:03:28.159 --> 00:03:29.869 align:start position:0% this is the blockchain trilemma it basically<00:03:28.560> states<00:03:28.920> that<00:03:29.040> you<00:03:29.159> have<00:03:29.280> to<00:03:29.400> choose 00:03:29.869 --> 00:03:29.879 align:start position:0% basically states that you have to choose 00:03:29.879 --> 00:03:31.470 align:start position:0% basically states that you have to choose two<00:03:30.080> out<00:03:30.200> of<00:03:30.360> these<00:03:30.560> three<00:03:30.799> decentralization 00:03:31.470 --> 00:03:31.480 align:start position:0% two out of these three decentralization 00:03:31.480 --> 00:03:33.270 align:start position:0% two out of these three decentralization scalability<00:03:32.040> of<00:03:32.280> security<00:03:32.720> you<00:03:32.840> can't<00:03:33.080> have 00:03:33.270 --> 00:03:33.280 align:start position:0% scalability of security you can't have 00:03:33.280 --> 00:03:37.070 align:start position:0% scalability of security you can't have all<00:03:33.560> three<00:03:34.560> why<00:03:35.239> so<00:03:35.480> from<00:03:35.720> first<00:03:36.080> principles 00:03:37.070 --> 00:03:37.080 align:start position:0% all three why so from first principles 00:03:37.080 --> 00:03:40.830 align:start position:0% all three why so from first principles in<00:03:37.200> order<00:03:37.439> to<00:03:38.080> secure<00:03:39.080> to<00:03:39.280> ensure<00:03:39.840> security 00:03:40.830 --> 00:03:40.840 align:start position:0% in order to secure to ensure security 00:03:40.840 --> 00:03:43.149 align:start position:0% in order to secure to ensure security you<00:03:41.000> have<00:03:41.159> to<00:03:41.280> have<00:03:41.480> all<00:03:41.680> nodes<00:03:42.400> run<00:03:42.799> all<00:03:42.959> the 00:03:43.149 --> 00:03:43.159 align:start position:0% you have to have all nodes run all the 00:03:43.159 --> 00:03:45.030 align:start position:0% you have to have all nodes run all the transactions<00:03:43.879> just<00:03:44.000> to<00:03:44.239> verify<00:03:44.680> that<00:03:44.799> they're 00:03:45.030 --> 00:03:45.040 align:start position:0% transactions just to verify that they're 00:03:45.040 --> 00:03:46.229 align:start position:0% transactions just to verify that they're indeed 00:03:46.229 --> 00:03:46.239 align:start position:0% indeed 00:03:46.239 --> 00:03:48.270 align:start position:0% indeed valid<00:03:47.239> on<00:03:47.360> the<00:03:47.480> other<00:03:47.640> hand<00:03:47.799> to<00:03:47.920> be 00:03:48.270 --> 00:03:48.280 align:start position:0% valid on the other hand to be 00:03:48.280 --> 00:03:50.270 align:start position:0% valid on the other hand to be decentralized<00:03:49.280> you<00:03:49.400> need<00:03:49.560> to<00:03:49.680> be<00:03:49.799> able<00:03:49.959> to<00:03:50.120> run 00:03:50.270 --> 00:03:50.280 align:start position:0% decentralized you need to be able to run 00:03:50.280 --> 00:03:52.149 align:start position:0% decentralized you need to be able to run a<00:03:50.400> node<00:03:50.680> on<00:03:50.799> a<00:03:50.920> weak<00:03:51.159> machine<00:03:51.560> so<00:03:51.760> everybody 00:03:52.149 --> 00:03:52.159 align:start position:0% a node on a weak machine so everybody 00:03:52.159 --> 00:03:55.390 align:start position:0% a node on a weak machine so everybody could<00:03:52.319> run<00:03:52.599> it<00:03:53.599> so<00:03:54.519> the<00:03:54.640> natural<00:03:55.000> conclusion 00:03:55.390 --> 00:03:55.400 align:start position:0% could run it so the natural conclusion 00:03:55.400 --> 00:03:57.149 align:start position:0% could run it so the natural conclusion is<00:03:55.519> that<00:03:55.640> you<00:03:55.760> have<00:03:55.920> to<00:03:56.239> limit<00:03:56.519> the<00:03:56.640> throughput 00:03:57.149 --> 00:03:57.159 align:start position:0% is that you have to limit the throughput 00:03:57.159 --> 00:03:59.110 align:start position:0% is that you have to limit the throughput so<00:03:57.360> you<00:03:57.519> could<00:03:57.959> run<00:03:58.200> all<00:03:58.400> these<00:03:58.599> transactions 00:03:59.110 --> 00:03:59.120 align:start position:0% so you could run all these transactions 00:03:59.120 --> 00:04:00.390 align:start position:0% so you could run all these transactions even<00:03:59.280> on<00:03:59.400> a<00:03:59.480> week 00:04:00.390 --> 00:04:00.400 align:start position:0% even on a week 00:04:00.400 --> 00:04:02.949 align:start position:0% even on a week machine<00:04:01.400> the<00:04:01.519> only<00:04:01.799> thing<00:04:02.360> uh<00:04:02.480> wrong<00:04:02.799> with 00:04:02.949 --> 00:04:02.959 align:start position:0% machine the only thing uh wrong with 00:04:02.959 --> 00:04:05.229 align:start position:0% machine the only thing uh wrong with this<00:04:03.079> blockchain<00:04:03.480> trilemma<00:04:04.040> is<00:04:04.280> that<00:04:05.079> it 00:04:05.229 --> 00:04:05.239 align:start position:0% this blockchain trilemma is that it 00:04:05.239 --> 00:04:08.509 align:start position:0% this blockchain trilemma is that it isn't<00:04:05.560> really<00:04:06.120> true<00:04:07.120> and<00:04:07.319> why<00:04:07.480> isn't<00:04:07.760> it<00:04:07.879> true 00:04:08.509 --> 00:04:08.519 align:start position:0% isn't really true and why isn't it true 00:04:08.519 --> 00:04:11.350 align:start position:0% isn't really true and why isn't it true uh<00:04:08.680> and<00:04:08.840> here<00:04:09.079> we<00:04:09.280> have<00:04:10.079> uh<00:04:10.799> I<00:04:10.879> mean<00:04:11.000> the<00:04:11.120> people 00:04:11.350 --> 00:04:11.360 align:start position:0% uh and here we have uh I mean the people 00:04:11.360 --> 00:04:13.270 align:start position:0% uh and here we have uh I mean the people who<00:04:11.560> actually<00:04:11.879> phrased<00:04:12.319> it<00:04:12.519> didn't<00:04:12.799> take<00:04:13.000> into 00:04:13.270 --> 00:04:13.280 align:start position:0% who actually phrased it didn't take into 00:04:13.280 --> 00:04:15.789 align:start position:0% who actually phrased it didn't take into account<00:04:13.599> this<00:04:14.000> neographic<00:04:15.000> algorithm<00:04:15.599> that 00:04:15.789 --> 00:04:15.799 align:start position:0% account this neographic algorithm that 00:04:15.799 --> 00:04:17.229 align:start position:0% account this neographic algorithm that that<00:04:15.959> we<00:04:16.079> use<00:04:16.280> and<00:04:16.440> others<00:04:16.680> use<00:04:16.919> as<00:04:17.040> well 00:04:17.229 --> 00:04:17.239 align:start position:0% that we use and others use as well 00:04:17.239 --> 00:04:19.270 align:start position:0% that we use and others use as well that's<00:04:17.519> called<00:04:18.199> validity 00:04:19.270 --> 00:04:19.280 align:start position:0% that's called validity 00:04:19.280 --> 00:04:21.670 align:start position:0% that's called validity proofs<00:04:20.280> uh<00:04:20.400> so<00:04:20.560> what's<00:04:20.759> validity<00:04:21.199> proofs<00:04:21.560> it 00:04:21.670 --> 00:04:21.680 align:start position:0% proofs uh so what's validity proofs it 00:04:21.680 --> 00:04:23.189 align:start position:0% proofs uh so what's validity proofs it came<00:04:21.840> from<00:04:22.040> Academia<00:04:22.560> long<00:04:22.759> before 00:04:23.189 --> 00:04:23.199 align:start position:0% came from Academia long before 00:04:23.199 --> 00:04:25.070 align:start position:0% came from Academia long before blockchain<00:04:23.759> it's<00:04:23.919> not<00:04:24.240> specifically<00:04:24.680> related 00:04:25.070 --> 00:04:25.080 align:start position:0% blockchain it's not specifically related 00:04:25.080 --> 00:04:27.310 align:start position:0% blockchain it's not specifically related just<00:04:25.240> to<00:04:25.400> blockchain<00:04:26.360> it<00:04:26.520> tries<00:04:26.759> to<00:04:26.919> solve<00:04:27.199> the 00:04:27.310 --> 00:04:27.320 align:start position:0% just to blockchain it tries to solve the 00:04:27.320 --> 00:04:29.189 align:start position:0% just to blockchain it tries to solve the following<00:04:27.800> problem<00:04:28.160> let's<00:04:28.400> say<00:04:28.680> I'm<00:04:29.039> I'm 00:04:29.189 --> 00:04:29.199 align:start position:0% following problem let's say I'm I'm 00:04:29.199 --> 00:04:31.390 align:start position:0% following problem let's say I'm I'm aover<00:04:29.600> and<00:04:29.800> you're<00:04:29.919> the<00:04:30.080> verifier<00:04:30.720> I<00:04:30.800> want<00:04:30.960> to 00:04:31.390 --> 00:04:31.400 align:start position:0% aover and you're the verifier I want to 00:04:31.400 --> 00:04:33.790 align:start position:0% aover and you're the verifier I want to uh<00:04:31.520> I<00:04:31.600> want<00:04:31.720> to<00:04:32.000> convince<00:04:32.560> you<00:04:33.320> that<00:04:33.479> I<00:04:33.600> have 00:04:33.790 --> 00:04:33.800 align:start position:0% uh I want to convince you that I have 00:04:33.800 --> 00:04:36.950 align:start position:0% uh I want to convince you that I have done<00:04:34.400> uh<00:04:34.520> a<00:04:34.720> complex<00:04:35.160> computation<00:04:35.960> correctly 00:04:36.950 --> 00:04:36.960 align:start position:0% done uh a complex computation correctly 00:04:36.960 --> 00:04:38.830 align:start position:0% done uh a complex computation correctly so<00:04:37.160> what<00:04:37.280> I<00:04:37.440> do<00:04:37.680> is<00:04:37.919> in<00:04:38.080> addition<00:04:38.320> to<00:04:38.479> doing<00:04:38.720> the 00:04:38.830 --> 00:04:38.840 align:start position:0% so what I do is in addition to doing the 00:04:38.840 --> 00:04:40.510 align:start position:0% so what I do is in addition to doing the actual<00:04:39.160> computation<00:04:39.840> I<00:04:40.160> I<00:04:40.240> do<00:04:40.360> some 00:04:40.510 --> 00:04:40.520 align:start position:0% actual computation I I do some 00:04:40.520 --> 00:04:42.710 align:start position:0% actual computation I I do some additional<00:04:41.000> work<00:04:41.199> and<00:04:41.320> I<00:04:41.440> generate<00:04:41.840> a<00:04:42.000> proof 00:04:42.710 --> 00:04:42.720 align:start position:0% additional work and I generate a proof 00:04:42.720 --> 00:04:44.310 align:start position:0% additional work and I generate a proof the<00:04:42.840> format<00:04:43.199> of<00:04:43.360> of<00:04:43.440> the<00:04:43.560> proof<00:04:43.759> is<00:04:43.880> defined<00:04:44.240> by 00:04:44.310 --> 00:04:44.320 align:start position:0% the format of of the proof is defined by 00:04:44.320 --> 00:04:46.390 align:start position:0% the format of of the proof is defined by the<00:04:44.479> protocol<00:04:45.320> I<00:04:45.400> send<00:04:45.759> you<00:04:45.880> the<00:04:46.000> proof<00:04:46.240> you're 00:04:46.390 --> 00:04:46.400 align:start position:0% the protocol I send you the proof you're 00:04:46.400 --> 00:04:48.029 align:start position:0% the protocol I send you the proof you're the<00:04:46.560> verifier<00:04:47.080> the<00:04:47.160> verifier<00:04:47.600> looks<00:04:47.759> at<00:04:47.919> the 00:04:48.029 --> 00:04:48.039 align:start position:0% the verifier the verifier looks at the 00:04:48.039 --> 00:04:49.710 align:start position:0% the verifier the verifier looks at the proof<00:04:48.320> and<00:04:48.479> decides<00:04:48.880> whether<00:04:49.039> it<00:04:49.240> accepts<00:04:49.560> it 00:04:49.710 --> 00:04:49.720 align:start position:0% proof and decides whether it accepts it 00:04:49.720 --> 00:04:52.070 align:start position:0% proof and decides whether it accepts it or<00:04:50.080> not<00:04:51.080> and<00:04:51.199> there<00:04:51.280> are<00:04:51.479> three<00:04:51.680> things<00:04:51.919> we 00:04:52.070 --> 00:04:52.080 align:start position:0% or not and there are three things we 00:04:52.080 --> 00:04:54.430 align:start position:0% or not and there are three things we want<00:04:52.360> here<00:04:52.600> one<00:04:52.800> is<00:04:53.080> that<00:04:53.600> if<00:04:53.800> the<00:04:53.960> computation 00:04:54.430 --> 00:04:54.440 align:start position:0% want here one is that if the computation 00:04:54.440 --> 00:04:56.230 align:start position:0% want here one is that if the computation is<00:04:54.600> indeed<00:04:54.960> correct<00:04:55.360> I<00:04:55.440> should<00:04:55.680> be<00:04:55.880> able<00:04:56.080> to 00:04:56.230 --> 00:04:56.240 align:start position:0% is indeed correct I should be able to 00:04:56.240 --> 00:04:57.909 align:start position:0% is indeed correct I should be able to generate<00:04:56.600> a<00:04:56.720> proof<00:04:56.960> that<00:04:57.120> you<00:04:57.320> the<00:04:57.440> verifier 00:04:57.909 --> 00:04:57.919 align:start position:0% generate a proof that you the verifier 00:04:57.919 --> 00:05:00.909 align:start position:0% generate a proof that you the verifier will<00:04:58.320> accept<00:04:59.320> two<00:04:59.800> is<00:04:59.960> if<00:05:00.080> the<00:05:00.160> computation<00:05:00.759> is 00:05:00.909 --> 00:05:00.919 align:start position:0% will accept two is if the computation is 00:05:00.919 --> 00:05:03.950 align:start position:0% will accept two is if the computation is not<00:05:01.160> correct<00:05:02.000> I<00:05:02.120> should<00:05:02.360> not<00:05:02.600> be<00:05:02.800> able<00:05:03.280> to<00:05:03.520> to 00:05:03.950 --> 00:05:03.960 align:start position:0% not correct I should not be able to to 00:05:03.960 --> 00:05:05.310 align:start position:0% not correct I should not be able to to uh<00:05:04.039> generate<00:05:04.360> a<00:05:04.479> proof<00:05:04.720> that<00:05:04.840> the<00:05:04.919> verifier 00:05:05.310 --> 00:05:05.320 align:start position:0% uh generate a proof that the verifier 00:05:05.320 --> 00:05:07.029 align:start position:0% uh generate a proof that the verifier will<00:05:05.520> accept<00:05:05.919> which<00:05:06.080> basically<00:05:06.440> means<00:05:06.680> that<00:05:06.880> I 00:05:07.029 --> 00:05:07.039 align:start position:0% will accept which basically means that I 00:05:07.039 --> 00:05:09.550 align:start position:0% will accept which basically means that I I<00:05:07.120> am<00:05:07.199> not<00:05:07.360> able<00:05:07.680> to<00:05:07.840> cheat<00:05:08.720> I<00:05:08.840> can't<00:05:09.160> convince 00:05:09.550 --> 00:05:09.560 align:start position:0% I am not able to cheat I can't convince 00:05:09.560 --> 00:05:12.110 align:start position:0% I am not able to cheat I can't convince you<00:05:09.720> of<00:05:09.880> something<00:05:10.320> that's<00:05:10.520> not<00:05:10.800> true<00:05:11.800> and<00:05:11.919> the 00:05:12.110 --> 00:05:12.120 align:start position:0% you of something that's not true and the 00:05:12.120 --> 00:05:14.550 align:start position:0% you of something that's not true and the third<00:05:12.840> is<00:05:13.039> that<00:05:13.240> we<00:05:13.360> want<00:05:13.560> the<00:05:13.720> verification 00:05:14.550 --> 00:05:14.560 align:start position:0% third is that we want the verification 00:05:14.560 --> 00:05:16.830 align:start position:0% third is that we want the verification cost<00:05:14.960> to<00:05:15.080> be<00:05:15.240> small<00:05:15.759> so<00:05:15.919> verifications<00:05:16.600> should 00:05:16.830 --> 00:05:16.840 align:start position:0% cost to be small so verifications should 00:05:16.840 --> 00:05:19.029 align:start position:0% cost to be small so verifications should be<00:05:17.160> should<00:05:17.360> be<00:05:17.520> a<00:05:17.639> lot<00:05:17.960> faster<00:05:18.400> and<00:05:18.560> a<00:05:18.639> lot<00:05:18.840> less 00:05:19.029 --> 00:05:19.039 align:start position:0% be should be a lot faster and a lot less 00:05:19.039 --> 00:05:20.790 align:start position:0% be should be a lot faster and a lot less resource<00:05:19.440> intensive<00:05:19.960> than<00:05:20.160> the<00:05:20.360> original 00:05:20.790 --> 00:05:20.800 align:start position:0% resource intensive than the original 00:05:20.800 --> 00:05:23.150 align:start position:0% resource intensive than the original computation<00:05:21.319> the<00:05:21.440> one<00:05:21.600> that<00:05:21.759> I'm<00:05:22.000> doing<00:05:23.000> so 00:05:23.150 --> 00:05:23.160 align:start position:0% computation the one that I'm doing so 00:05:23.160 --> 00:05:24.469 align:start position:0% computation the one that I'm doing so there<00:05:23.280> are<00:05:23.360> a<00:05:23.440> bunch<00:05:23.600> of<00:05:23.759> protocols<00:05:24.199> that<00:05:24.319> do 00:05:24.469 --> 00:05:24.479 align:start position:0% there are a bunch of protocols that do 00:05:24.479 --> 00:05:25.749 align:start position:0% there are a bunch of protocols that do that<00:05:24.680> star<00:05:25.120> which<00:05:25.199> is<00:05:25.319> the<00:05:25.400> one<00:05:25.520> that<00:05:25.600> we're 00:05:25.749 --> 00:05:25.759 align:start position:0% that star which is the one that we're 00:05:25.759 --> 00:05:28.309 align:start position:0% that star which is the one that we're using<00:05:26.120> has<00:05:26.360> some<00:05:26.560> very<00:05:26.720> good<00:05:27.120> properties<00:05:28.120> uh 00:05:28.309 --> 00:05:28.319 align:start position:0% using has some very good properties uh 00:05:28.319 --> 00:05:30.189 align:start position:0% using has some very good properties uh but<00:05:28.479> this<00:05:28.600> is<00:05:28.840> basically<00:05:29.199> a<00:05:29.280> solve<00:05:29.800> problem 00:05:30.189 --> 00:05:30.199 align:start position:0% but this is basically a solve problem 00:05:30.199 --> 00:05:31.950 align:start position:0% but this is basically a solve problem again<00:05:30.440> not<00:05:30.600> necessarily<00:05:31.000> in 00:05:31.950 --> 00:05:31.960 align:start position:0% again not necessarily in 00:05:31.960 --> 00:05:34.270 align:start position:0% again not necessarily in blockchain<00:05:32.960> so<00:05:33.199> how<00:05:33.400> can<00:05:33.560> how<00:05:33.680> do<00:05:33.800> we<00:05:33.919> use<00:05:34.080> it 00:05:34.270 --> 00:05:34.280 align:start position:0% blockchain so how can how do we use it 00:05:34.280 --> 00:05:36.309 align:start position:0% blockchain so how can how do we use it here<00:05:34.520> so<00:05:34.720> validity<00:05:35.160> rollups<00:05:36.000> uh<00:05:36.080> which<00:05:36.199> is 00:05:36.309 --> 00:05:36.319 align:start position:0% here so validity rollups uh which is 00:05:36.319 --> 00:05:38.350 align:start position:0% here so validity rollups uh which is what<00:05:36.440> we're<00:05:36.600> doing<00:05:36.880> as<00:05:37.080> well<00:05:37.680> basically<00:05:38.039> says 00:05:38.350 --> 00:05:38.360 align:start position:0% what we're doing as well basically says 00:05:38.360 --> 00:05:39.029 align:start position:0% what we're doing as well basically says the 00:05:39.029 --> 00:05:39.039 align:start position:0% the 00:05:39.039 --> 00:05:42.150 align:start position:0% the following<00:05:40.039> okay<00:05:40.360> I'll<00:05:40.479> start<00:05:40.800> with<00:05:41.000> the<00:05:41.880> with 00:05:42.150 --> 00:05:42.160 align:start position:0% following okay I'll start with the with 00:05:42.160 --> 00:05:43.430 align:start position:0% following okay I'll start with the with the<00:05:42.360> the<00:05:42.440> issue<00:05:42.680> that<00:05:42.759> I<00:05:42.840> mentioned<00:05:43.120> before 00:05:43.430 --> 00:05:43.440 align:start position:0% the the issue that I mentioned before 00:05:43.440 --> 00:05:46.029 align:start position:0% the the issue that I mentioned before without<00:05:44.160> proofs<00:05:45.160> there<00:05:45.280> are<00:05:45.400> two<00:05:45.720> aspects 00:05:46.029 --> 00:05:46.039 align:start position:0% without proofs there are two aspects 00:05:46.039 --> 00:05:48.309 align:start position:0% without proofs there are two aspects here<00:05:46.199> you<00:05:46.319> have<00:05:46.440> the<00:05:46.560> sequencers<00:05:47.560> or<00:05:47.720> miners 00:05:48.309 --> 00:05:48.319 align:start position:0% here you have the sequencers or miners 00:05:48.319 --> 00:05:50.990 align:start position:0% here you have the sequencers or miners or<00:05:48.639> validators<00:05:49.639> whatever<00:05:49.960> you<00:05:50.080> call<00:05:50.479> those<00:05:50.880> uh 00:05:50.990 --> 00:05:51.000 align:start position:0% or validators whatever you call those uh 00:05:51.000 --> 00:05:53.469 align:start position:0% or validators whatever you call those uh entities<00:05:51.440> that<00:05:51.560> generate<00:05:51.960> the<00:05:52.280> blocks<00:05:53.280> they 00:05:53.469 --> 00:05:53.479 align:start position:0% entities that generate the blocks they 00:05:53.479 --> 00:05:55.029 align:start position:0% entities that generate the blocks they have<00:05:53.680> to<00:05:53.840> execute<00:05:54.240> all 00:05:55.029 --> 00:05:55.039 align:start position:0% have to execute all 00:05:55.039 --> 00:05:57.870 align:start position:0% have to execute all transactions<00:05:56.039> but<00:05:56.880> in<00:05:57.080> blockchain<00:05:57.560> such<00:05:57.720> as 00:05:57.870 --> 00:05:57.880 align:start position:0% transactions but in blockchain such as 00:05:57.880 --> 00:05:59.790 align:start position:0% transactions but in blockchain such as ethereum<00:05:58.360> and<00:05:58.720> and<00:05:58.919> Bitcoin<00:05:59.280> that's<00:05:59.440> not 00:05:59.790 --> 00:05:59.800 align:start position:0% ethereum and and Bitcoin that's not 00:05:59.800 --> 00:06:01.469 align:start position:0% ethereum and and Bitcoin that's not enough<00:06:00.000> you<00:06:00.120> have<00:06:00.199> to<00:06:00.360> have<00:06:00.560> all<00:06:00.759> full<00:06:01.039> nod<00:06:01.360> so 00:06:01.469 --> 00:06:01.479 align:start position:0% enough you have to have all full nod so 00:06:01.479 --> 00:06:02.710 align:start position:0% enough you have to have all full nod so you're<00:06:01.680> full<00:06:01.880> node<00:06:02.120> you<00:06:02.199> want<00:06:02.280> to<00:06:02.400> know<00:06:02.520> what's 00:06:02.710 --> 00:06:02.720 align:start position:0% you're full node you want to know what's 00:06:02.720 --> 00:06:04.070 align:start position:0% you're full node you want to know what's happening<00:06:03.000> with<00:06:03.120> the<00:06:03.240> network<00:06:03.639> the<00:06:03.720> only<00:06:03.919> way 00:06:04.070 --> 00:06:04.080 align:start position:0% happening with the network the only way 00:06:04.080 --> 00:06:05.550 align:start position:0% happening with the network the only way you<00:06:04.160> could<00:06:04.280> be<00:06:04.400> certain<00:06:04.759> that<00:06:04.919> this<00:06:05.039> is<00:06:05.199> indeed 00:06:05.550 --> 00:06:05.560 align:start position:0% you could be certain that this is indeed 00:06:05.560 --> 00:06:06.950 align:start position:0% you could be certain that this is indeed valid<00:06:05.840> is<00:06:05.960> you<00:06:06.080> have<00:06:06.160> to<00:06:06.319> execute<00:06:06.720> all<00:06:06.840> the 00:06:06.950 --> 00:06:06.960 align:start position:0% valid is you have to execute all the 00:06:06.960 --> 00:06:09.070 align:start position:0% valid is you have to execute all the transactions<00:06:07.639> yourselves<00:06:08.639> and<00:06:08.759> there<00:06:08.840> are<00:06:08.960> a 00:06:09.070 --> 00:06:09.080 align:start position:0% transactions yourselves and there are a 00:06:09.080 --> 00:06:11.230 align:start position:0% transactions yourselves and there are a lot<00:06:09.240> more<00:06:09.440> nodes<00:06:09.880> than<00:06:10.120> than<00:06:10.360> sequencers<00:06:11.000> or 00:06:11.230 --> 00:06:11.240 align:start position:0% lot more nodes than than sequencers or 00:06:11.240 --> 00:06:13.230 align:start position:0% lot more nodes than than sequencers or validators<00:06:12.080> in<00:06:12.199> ethereum<00:06:12.639> you<00:06:12.759> have<00:06:13.000> maybe 00:06:13.230 --> 00:06:13.240 align:start position:0% validators in ethereum you have maybe 00:06:13.240 --> 00:06:16.230 align:start position:0% validators in ethereum you have maybe millions<00:06:13.639> of<00:06:13.800> them<00:06:14.319> right<00:06:15.319> now<00:06:15.599> with<00:06:15.840> proofs 00:06:16.230 --> 00:06:16.240 align:start position:0% millions of them right now with proofs 00:06:16.240 --> 00:06:19.830 align:start position:0% millions of them right now with proofs you<00:06:16.440> actually<00:06:16.720> break<00:06:17.240> this<00:06:17.840> uh<00:06:18.319> connection<00:06:19.319> uh 00:06:19.830 --> 00:06:19.840 align:start position:0% you actually break this uh connection uh 00:06:19.840 --> 00:06:22.110 align:start position:0% you actually break this uh connection uh because<00:06:20.840> all<00:06:21.080> the<00:06:21.199> nodes<00:06:21.479> in<00:06:21.599> order<00:06:21.800> to<00:06:21.960> know 00:06:22.110 --> 00:06:22.120 align:start position:0% because all the nodes in order to know 00:06:22.120 --> 00:06:23.390 align:start position:0% because all the nodes in order to know that<00:06:22.280> the<00:06:22.400> transactions<00:06:22.880> are<00:06:23.039> correct<00:06:23.319> they 00:06:23.390 --> 00:06:23.400 align:start position:0% that the transactions are correct they 00:06:23.400 --> 00:06:25.110 align:start position:0% that the transactions are correct they don't<00:06:23.520> need<00:06:23.680> to<00:06:23.840> reexecute<00:06:24.280> them<00:06:24.840> they<00:06:24.960> only 00:06:25.110 --> 00:06:25.120 align:start position:0% don't need to reexecute them they only 00:06:25.120 --> 00:06:26.909 align:start position:0% don't need to reexecute them they only need<00:06:25.360> to<00:06:25.520> verify<00:06:25.880> the<00:06:26.039> proof<00:06:26.440> and<00:06:26.560> like<00:06:26.680> I<00:06:26.759> said 00:06:26.909 --> 00:06:26.919 align:start position:0% need to verify the proof and like I said 00:06:26.919 --> 00:06:28.469 align:start position:0% need to verify the proof and like I said before<00:06:27.160> verifying<00:06:27.560> a<00:06:27.639> proof<00:06:27.840> is<00:06:27.919> a<00:06:28.039> lot<00:06:28.280> less 00:06:28.469 --> 00:06:28.479 align:start position:0% before verifying a proof is a lot less 00:06:28.479 --> 00:06:31.029 align:start position:0% before verifying a proof is a lot less work<00:06:28.800> than<00:06:29.000> than<00:06:29.120> running<00:06:29.319> the<00:06:30.039> transactions 00:06:31.029 --> 00:06:31.039 align:start position:0% work than than running the transactions 00:06:31.039 --> 00:06:32.870 align:start position:0% work than than running the transactions and<00:06:31.319> this<00:06:31.440> is<00:06:31.720> the<00:06:31.840> only<00:06:32.039> way<00:06:32.199> that<00:06:32.360> I<00:06:32.520> know<00:06:32.720> of 00:06:32.870 --> 00:06:32.880 align:start position:0% and this is the only way that I know of 00:06:32.880 --> 00:06:34.710 align:start position:0% and this is the only way that I know of that<00:06:33.039> actually<00:06:33.280> solves<00:06:33.639> this 00:06:34.710 --> 00:06:34.720 align:start position:0% that actually solves this 00:06:34.720 --> 00:06:37.070 align:start position:0% that actually solves this trilemma<00:06:35.720> all<00:06:35.960> other<00:06:36.199> ways<00:06:36.520> typically<00:06:36.880> if<00:06:36.960> you 00:06:37.070 --> 00:06:37.080 align:start position:0% trilemma all other ways typically if you 00:06:37.080 --> 00:06:39.230 align:start position:0% trilemma all other ways typically if you look<00:06:37.199> at<00:06:37.319> it<00:06:37.720> closely<00:06:38.720> you<00:06:38.880> probably 00:06:39.230 --> 00:06:39.240 align:start position:0% look at it closely you probably 00:06:39.240 --> 00:06:40.990 align:start position:0% look at it closely you probably sacrifice<00:06:39.840> either<00:06:40.120> security<00:06:40.599> and<00:06:40.800> or 00:06:40.990 --> 00:06:41.000 align:start position:0% sacrifice either security and or 00:06:41.000 --> 00:06:43.790 align:start position:0% sacrifice either security and or decentralization<00:06:41.800> to<00:06:41.960> get<00:06:42.120> the 00:06:43.790 --> 00:06:43.800 align:start position:0% decentralization to get the 00:06:43.800 --> 00:06:45.790 align:start position:0% decentralization to get the scale<00:06:44.800> okay<00:06:45.000> another<00:06:45.280> thing<00:06:45.400> you<00:06:45.599> probably 00:06:45.790 --> 00:06:45.800 align:start position:0% scale okay another thing you probably 00:06:45.800 --> 00:06:47.469 align:start position:0% scale okay another thing you probably heard<00:06:46.000> of<00:06:46.120> there<00:06:46.240> are<00:06:46.400> public<00:06:46.680> chains<00:06:47.280> like 00:06:47.469 --> 00:06:47.479 align:start position:0% heard of there are public chains like 00:06:47.479 --> 00:06:49.510 align:start position:0% heard of there are public chains like ethereum<00:06:48.160> Bitcoin<00:06:48.599> Stark<00:06:48.960> net<00:06:49.160> a<00:06:49.280> public 00:06:49.510 --> 00:06:49.520 align:start position:0% ethereum Bitcoin Stark net a public 00:06:49.520 --> 00:06:51.390 align:start position:0% ethereum Bitcoin Stark net a public chain<00:06:49.759> there<00:06:49.880> are<00:06:50.000> also<00:06:50.280> app<00:06:50.520> chains<00:06:50.919> so<00:06:51.160> app 00:06:51.390 --> 00:06:51.400 align:start position:0% chain there are also app chains so app 00:06:51.400 --> 00:06:52.749 align:start position:0% chain there are also app chains so app specific<00:06:51.759> chains<00:06:52.039> that<00:06:52.160> you<00:06:52.240> could<00:06:52.400> spin<00:06:52.639> your 00:06:52.749 --> 00:06:52.759 align:start position:0% specific chains that you could spin your 00:06:52.759 --> 00:06:54.710 align:start position:0% specific chains that you could spin your own<00:06:52.960> and<00:06:53.120> just<00:06:53.240> run<00:06:53.479> whatever<00:06:53.800> you<00:06:53.919> want<00:06:54.160> on 00:06:54.710 --> 00:06:54.720 align:start position:0% own and just run whatever you want on 00:06:54.720 --> 00:06:57.950 align:start position:0% own and just run whatever you want on that<00:06:55.720> and<00:06:56.000> there<00:06:56.360> are<00:06:57.360> both<00:06:57.560> are<00:06:57.720> probably 00:06:57.950 --> 00:06:57.960 align:start position:0% that and there are both are probably 00:06:57.960 --> 00:07:00.150 align:start position:0% that and there are both are probably needed<00:06:58.199> for<00:06:58.360> different<00:06:58.599> use<00:06:58.919> cases<00:06:59.280> so<00:06:59.800> we<00:06:59.960> try 00:07:00.150 --> 00:07:00.160 align:start position:0% needed for different use cases so we try 00:07:00.160 --> 00:07:03.629 align:start position:0% needed for different use cases so we try to<00:07:00.360> categorize<00:07:00.879> It<00:07:01.520> generally<00:07:02.520> uh<00:07:03.199> when<00:07:03.440> in 00:07:03.629 --> 00:07:03.639 align:start position:0% to categorize It generally uh when in 00:07:03.639 --> 00:07:05.469 align:start position:0% to categorize It generally uh when in general<00:07:04.000> would<00:07:04.160> you<00:07:04.319> opt<00:07:04.599> to<00:07:04.759> run<00:07:04.960> on<00:07:05.039> a<00:07:05.199> public 00:07:05.469 --> 00:07:05.479 align:start position:0% general would you opt to run on a public 00:07:05.479 --> 00:07:07.670 align:start position:0% general would you opt to run on a public chain<00:07:05.919> typically<00:07:06.319> when<00:07:06.479> you<00:07:07.199> either<00:07:07.400> when<00:07:07.560> you 00:07:07.670 --> 00:07:07.680 align:start position:0% chain typically when you either when you 00:07:07.680 --> 00:07:09.150 align:start position:0% chain typically when you either when you care<00:07:07.840> a<00:07:07.960> lot<00:07:08.120> about<00:07:08.319> composability<00:07:08.759> you<00:07:09.080> want 00:07:09.150 --> 00:07:09.160 align:start position:0% care a lot about composability you want 00:07:09.160 --> 00:07:10.390 align:start position:0% care a lot about composability you want to<00:07:09.280> connect<00:07:09.560> to<00:07:09.720> other<00:07:09.919> apps<00:07:10.160> that<00:07:10.280> are 00:07:10.390 --> 00:07:10.400 align:start position:0% to connect to other apps that are 00:07:10.400 --> 00:07:12.909 align:start position:0% to connect to other apps that are already<00:07:10.840> there<00:07:11.840> or<00:07:12.039> you<00:07:12.160> want<00:07:12.319> to<00:07:12.479> leverage 00:07:12.909 --> 00:07:12.919 align:start position:0% already there or you want to leverage 00:07:12.919 --> 00:07:15.309 align:start position:0% already there or you want to leverage the<00:07:13.039> network<00:07:13.520> effects<00:07:13.960> of<00:07:14.280> that<00:07:14.479> chain<00:07:15.199> the 00:07:15.309 --> 00:07:15.319 align:start position:0% the network effects of that chain the 00:07:15.319 --> 00:07:18.469 align:start position:0% the network effects of that chain the users<00:07:15.720> that<00:07:15.840> are<00:07:16.000> already<00:07:16.360> there<00:07:16.599> other<00:07:16.960> apps 00:07:18.469 --> 00:07:18.479 align:start position:0% users that are already there other apps 00:07:18.479 --> 00:07:21.869 align:start position:0% users that are already there other apps liquidity<00:07:19.479> or<00:07:20.319> uh<00:07:20.599> or<00:07:21.199> often<00:07:21.479> this<00:07:21.599> is<00:07:21.759> the 00:07:21.869 --> 00:07:21.879 align:start position:0% liquidity or uh or often this is the 00:07:21.879 --> 00:07:23.189 align:start position:0% liquidity or uh or often this is the simplest<00:07:22.240> thing<00:07:22.360> to<00:07:22.520> do<00:07:22.680> because<00:07:22.919> it's<00:07:23.080> it's 00:07:23.189 --> 00:07:23.199 align:start position:0% simplest thing to do because it's it's 00:07:23.199 --> 00:07:24.710 align:start position:0% simplest thing to do because it's it's lower<00:07:23.560> touch<00:07:23.800> you<00:07:23.960> just<00:07:24.080> build<00:07:24.280> an<00:07:24.440> app<00:07:24.599> you 00:07:24.710 --> 00:07:24.720 align:start position:0% lower touch you just build an app you 00:07:24.720 --> 00:07:26.070 align:start position:0% lower touch you just build an app you throw<00:07:24.919> it<00:07:25.039> for<00:07:25.160> instance<00:07:25.400> on<00:07:25.560> ethereum<00:07:25.879> and<00:07:26.000> it 00:07:26.070 --> 00:07:26.080 align:start position:0% throw it for instance on ethereum and it 00:07:26.080 --> 00:07:27.469 align:start position:0% throw it for instance on ethereum and it runs<00:07:26.319> by<00:07:26.440> itself<00:07:26.720> you<00:07:26.800> throw<00:07:27.000> it<00:07:27.080> on<00:07:27.160> Stark 00:07:27.469 --> 00:07:27.479 align:start position:0% runs by itself you throw it on Stark 00:07:27.479 --> 00:07:29.869 align:start position:0% runs by itself you throw it on Stark knet<00:07:27.639> it<00:07:27.720> runs<00:07:28.000> by<00:07:28.319> itself<00:07:29.319> when<00:07:29.639> would<00:07:29.759> you 00:07:29.869 --> 00:07:29.879 align:start position:0% knet it runs by itself when would you 00:07:29.879 --> 00:07:32.629 align:start position:0% knet it runs by itself when would you opt<00:07:30.080> for<00:07:30.199> an<00:07:30.319> app<00:07:30.680> chain<00:07:31.680> so<00:07:31.919> one<00:07:32.199> major 00:07:32.629 --> 00:07:32.639 align:start position:0% opt for an app chain so one major 00:07:32.639 --> 00:07:35.350 align:start position:0% opt for an app chain so one major category<00:07:33.199> is<00:07:33.319> when<00:07:33.440> you<00:07:33.560> want<00:07:33.759> more<00:07:34.360> control 00:07:35.350 --> 00:07:35.360 align:start position:0% category is when you want more control 00:07:35.360 --> 00:07:36.629 align:start position:0% category is when you want more control what's<00:07:35.599> more<00:07:35.759> control<00:07:36.120> you<00:07:36.199> may<00:07:36.360> want<00:07:36.479> to 00:07:36.629 --> 00:07:36.639 align:start position:0% what's more control you may want to 00:07:36.639 --> 00:07:38.189 align:start position:0% what's more control you may want to customize<00:07:37.080> the<00:07:37.400> network<00:07:37.720> in<00:07:37.840> a<00:07:37.960> different 00:07:38.189 --> 00:07:38.199 align:start position:0% customize the network in a different 00:07:38.199 --> 00:07:40.390 align:start position:0% customize the network in a different manner<00:07:38.520> than<00:07:38.639> a<00:07:38.800> public<00:07:39.039> chain<00:07:39.280> is<00:07:39.440> running 00:07:40.390 --> 00:07:40.400 align:start position:0% manner than a public chain is running 00:07:40.400 --> 00:07:42.070 align:start position:0% manner than a public chain is running you<00:07:40.560> may<00:07:40.759> not<00:07:40.960> want<00:07:41.199> to<00:07:41.360> be<00:07:41.520> affected<00:07:41.879> by 00:07:42.070 --> 00:07:42.080 align:start position:0% you may not want to be affected by 00:07:42.080 --> 00:07:44.629 align:start position:0% you may not want to be affected by congestion<00:07:42.599> due<00:07:42.800> to<00:07:43.039> other<00:07:43.360> apps<00:07:44.240> uh<00:07:44.360> you<00:07:44.440> may 00:07:44.629 --> 00:07:44.639 align:start position:0% congestion due to other apps uh you may 00:07:44.639 --> 00:07:46.950 align:start position:0% congestion due to other apps uh you may want<00:07:45.000> privacy<00:07:45.800> that<00:07:46.000> on<00:07:46.199> public<00:07:46.440> chains<00:07:46.759> you 00:07:46.950 --> 00:07:46.960 align:start position:0% want privacy that on public chains you 00:07:46.960 --> 00:07:49.830 align:start position:0% want privacy that on public chains you typically<00:07:47.360> don't<00:07:47.960> get<00:07:48.960> that's<00:07:49.159> one<00:07:49.440> aspect 00:07:49.830 --> 00:07:49.840 align:start position:0% typically don't get that's one aspect 00:07:49.840 --> 00:07:51.749 align:start position:0% typically don't get that's one aspect another<00:07:50.159> is<00:07:50.680> uh<00:07:50.840> maybe<00:07:51.039> you<00:07:51.159> want<00:07:51.280> to<00:07:51.479> capture 00:07:51.749 --> 00:07:51.759 align:start position:0% another is uh maybe you want to capture 00:07:51.759 --> 00:07:53.950 align:start position:0% another is uh maybe you want to capture the<00:07:51.879> network<00:07:52.240> Revenue<00:07:52.720> yourself<00:07:53.520> or<00:07:53.680> at<00:07:53.759> least 00:07:53.950 --> 00:07:53.960 align:start position:0% the network Revenue yourself or at least 00:07:53.960 --> 00:07:56.110 align:start position:0% the network Revenue yourself or at least part<00:07:54.120> of<00:07:54.240> it<00:07:54.520> in<00:07:54.599> the<00:07:54.759> public<00:07:54.960> chain<00:07:55.280> typically 00:07:56.110 --> 00:07:56.120 align:start position:0% part of it in the public chain typically 00:07:56.120 --> 00:07:58.670 align:start position:0% part of it in the public chain typically the<00:07:56.319> miners<00:07:56.960> the<00:07:57.199> verifier<00:07:57.800> sequencers<00:07:58.479> they 00:07:58.670 --> 00:07:58.680 align:start position:0% the miners the verifier sequencers they 00:07:58.680 --> 00:08:01.029 align:start position:0% the miners the verifier sequencers they get<00:07:59.520> the<00:07:59.599> network<00:07:59.919> fees<00:08:00.319> they<00:08:00.440> get<00:08:00.720> the<00:08:00.960> the 00:08:01.029 --> 00:08:01.039 align:start position:0% get the network fees they get the the 00:08:01.039 --> 00:08:03.550 align:start position:0% get the network fees they get the the block<00:08:01.520> rewards<00:08:02.520> maybe<00:08:02.720> you<00:08:02.840> want<00:08:02.960> to<00:08:03.400> uh 00:08:03.550 --> 00:08:03.560 align:start position:0% block rewards maybe you want to uh 00:08:03.560 --> 00:08:05.469 align:start position:0% block rewards maybe you want to uh capture<00:08:03.919> that<00:08:04.159> yourself<00:08:04.560> if<00:08:04.639> you<00:08:04.800> have<00:08:04.919> a<00:08:05.159> good 00:08:05.469 --> 00:08:05.479 align:start position:0% capture that yourself if you have a good 00:08:05.479 --> 00:08:09.029 align:start position:0% capture that yourself if you have a good app<00:08:06.479> the<00:08:06.639> third<00:08:06.960> main<00:08:07.199> thing<00:08:07.479> is<00:08:08.479> branding<00:08:08.879> and 00:08:09.029 --> 00:08:09.039 align:start position:0% app the third main thing is branding and 00:08:09.039 --> 00:08:10.430 align:start position:0% app the third main thing is branding and distribution<00:08:09.520> you<00:08:09.599> want<00:08:09.840> you<00:08:10.000> may<00:08:10.159> want<00:08:10.319> your 00:08:10.430 --> 00:08:10.440 align:start position:0% distribution you want you may want your 00:08:10.440 --> 00:08:12.070 align:start position:0% distribution you want you may want your own<00:08:10.639> network<00:08:11.280> because<00:08:11.479> you<00:08:11.560> want<00:08:11.720> it<00:08:11.840> to<00:08:11.919> be 00:08:12.070 --> 00:08:12.080 align:start position:0% own network because you want it to be 00:08:12.080 --> 00:08:14.309 align:start position:0% own network because you want it to be called<00:08:13.080> by<00:08:13.199> your<00:08:13.440> name<00:08:13.720> or<00:08:13.840> maybe<00:08:14.039> you<00:08:14.120> have<00:08:14.240> a 00:08:14.309 --> 00:08:14.319 align:start position:0% called by your name or maybe you have a 00:08:14.319 --> 00:08:15.469 align:start position:0% called by your name or maybe you have a good<00:08:14.479> distribution<00:08:14.919> Channel<00:08:15.199> you<00:08:15.280> want<00:08:15.400> to 00:08:15.469 --> 00:08:15.479 align:start position:0% good distribution Channel you want to 00:08:15.479 --> 00:08:16.909 align:start position:0% good distribution Channel you want to bring<00:08:15.639> them<00:08:15.759> to<00:08:15.840> your<00:08:15.960> own<00:08:16.360> network<00:08:16.639> and<00:08:16.759> not 00:08:16.909 --> 00:08:16.919 align:start position:0% bring them to your own network and not 00:08:16.919 --> 00:08:18.430 align:start position:0% bring them to your own network and not to<00:08:17.000> a<00:08:17.120> public 00:08:18.430 --> 00:08:18.440 align:start position:0% to a public 00:08:18.440 --> 00:08:21.189 align:start position:0% to a public chain<00:08:19.440> okay<00:08:19.599> so<00:08:19.759> what's<00:08:19.960> important<00:08:20.240> in<00:08:20.360> the 00:08:21.189 --> 00:08:21.199 align:start position:0% chain okay so what's important in the 00:08:21.199 --> 00:08:24.029 align:start position:0% chain okay so what's important in the chain<00:08:22.199> this<00:08:22.400> plays<00:08:22.759> different<00:08:23.319> uh<00:08:23.919> a 00:08:24.029 --> 00:08:24.039 align:start position:0% chain this plays different uh a 00:08:24.039 --> 00:08:25.230 align:start position:0% chain this plays different uh a different<00:08:24.280> role<00:08:24.520> whether<00:08:24.680> it's<00:08:24.800> an<00:08:24.919> app<00:08:25.080> chain 00:08:25.230 --> 00:08:25.240 align:start position:0% different role whether it's an app chain 00:08:25.240 --> 00:08:26.710 align:start position:0% different role whether it's an app chain or<00:08:25.319> a<00:08:25.400> main<00:08:25.560> chain<00:08:25.800> but<00:08:25.919> all<00:08:26.159> these<00:08:26.400> aspects 00:08:26.710 --> 00:08:26.720 align:start position:0% or a main chain but all these aspects 00:08:26.720 --> 00:08:28.309 align:start position:0% or a main chain but all these aspects are<00:08:26.879> somewhat<00:08:27.280> import<00:08:27.599> important<00:08:27.919> in<00:08:28.120> both 00:08:28.309 --> 00:08:28.319 align:start position:0% are somewhat import important in both 00:08:28.319 --> 00:08:30.230 align:start position:0% are somewhat import important in both and<00:08:28.479> when<00:08:28.599> you<00:08:28.720> choose<00:08:29.520> you<00:08:29.720> should<00:08:29.919> probably 00:08:30.230 --> 00:08:30.240 align:start position:0% and when you choose you should probably 00:08:30.240 --> 00:08:31.629 align:start position:0% and when you choose you should probably think<00:08:30.560> like<00:08:30.759> where<00:08:30.919> you<00:08:31.039> fall<00:08:31.280> on<00:08:31.479> these 00:08:31.629 --> 00:08:31.639 align:start position:0% think like where you fall on these 00:08:31.639 --> 00:08:33.829 align:start position:0% think like where you fall on these continues<00:08:32.200> so<00:08:32.560> I'm<00:08:32.680> going<00:08:32.760> to<00:08:33.000> touch<00:08:33.440> briefly 00:08:33.829 --> 00:08:33.839 align:start position:0% continues so I'm going to touch briefly 00:08:33.839 --> 00:08:36.430 align:start position:0% continues so I'm going to touch briefly touch<00:08:34.120> some<00:08:34.320> of<00:08:34.479> them<00:08:35.479> uh<00:08:35.560> I'll<00:08:35.719> start<00:08:35.959> with 00:08:36.430 --> 00:08:36.440 align:start position:0% touch some of them uh I'll start with 00:08:36.440 --> 00:08:39.310 align:start position:0% touch some of them uh I'll start with security<00:08:37.440> uh<00:08:37.800> I'm<00:08:38.000> often<00:08:38.320> told<00:08:38.760> and<00:08:38.959> I<00:08:39.080> think 00:08:39.310 --> 00:08:39.320 align:start position:0% security uh I'm often told and I think 00:08:39.320 --> 00:08:40.909 align:start position:0% security uh I'm often told and I think reality<00:08:39.680> shows<00:08:39.959> it<00:08:40.120> in<00:08:40.240> many<00:08:40.479> cases<00:08:40.760> that 00:08:40.909 --> 00:08:40.919 align:start position:0% reality shows it in many cases that 00:08:40.919 --> 00:08:42.269 align:start position:0% reality shows it in many cases that nobody<00:08:41.240> cares<00:08:41.519> about 00:08:42.269 --> 00:08:42.279 align:start position:0% nobody cares about 00:08:42.279 --> 00:08:44.670 align:start position:0% nobody cares about security<00:08:43.279> uh<00:08:43.560> or<00:08:43.719> at<00:08:43.880> least<00:08:44.240> they<00:08:44.360> don't<00:08:44.560> care 00:08:44.670 --> 00:08:44.680 align:start position:0% security uh or at least they don't care 00:08:44.680 --> 00:08:47.269 align:start position:0% security uh or at least they don't care about<00:08:44.880> security<00:08:45.240> until<00:08:45.519> they<00:08:45.720> get<00:08:46.160> hacked<00:08:47.160> uh 00:08:47.269 --> 00:08:47.279 align:start position:0% about security until they get hacked uh 00:08:47.279 --> 00:08:49.509 align:start position:0% about security until they get hacked uh so<00:08:47.440> I<00:08:47.560> claim<00:08:47.959> that<00:08:48.519> you<00:08:48.640> should<00:08:48.959> think<00:08:49.160> about 00:08:49.509 --> 00:08:49.519 align:start position:0% so I claim that you should think about 00:08:49.519 --> 00:08:51.910 align:start position:0% so I claim that you should think about security<00:08:50.519> especially<00:08:50.959> in 00:08:51.910 --> 00:08:51.920 align:start position:0% security especially in 00:08:51.920 --> 00:08:55.070 align:start position:0% security especially in blockchain<00:08:53.040> uh<00:08:54.040> so<00:08:54.279> I<00:08:54.440> I<00:08:54.519> do<00:08:54.680> agree<00:08:54.880> that 00:08:55.070 --> 00:08:55.080 align:start position:0% blockchain uh so I I do agree that 00:08:55.080 --> 00:08:56.750 align:start position:0% blockchain uh so I I do agree that different<00:08:55.320> block<00:08:55.760> like<00:08:55.959> different<00:08:56.200> use<00:08:56.480> cases 00:08:56.750 --> 00:08:56.760 align:start position:0% different block like different use cases 00:08:56.760 --> 00:08:58.389 align:start position:0% different block like different use cases call<00:08:56.920> for<00:08:57.160> different<00:08:57.399> levels<00:08:57.760> of<00:08:57.920> security 00:08:58.389 --> 00:08:58.399 align:start position:0% call for different levels of security 00:08:58.399 --> 00:08:59.790 align:start position:0% call for different levels of security and<00:08:58.519> then<00:08:58.640> you<00:08:58.800> can<00:08:58.920> make<00:08:59.079> concessions<00:08:59.680> in 00:08:59.790 --> 00:08:59.800 align:start position:0% and then you can make concessions in 00:08:59.800 --> 00:09:01.670 align:start position:0% and then you can make concessions in some<00:09:00.000> cases<00:09:00.440> but<00:09:00.959> I<00:09:01.040> think<00:09:01.200> these<00:09:01.320> are<00:09:01.399> a<00:09:01.519> few 00:09:01.670 --> 00:09:01.680 align:start position:0% some cases but I think these are a few 00:09:01.680 --> 00:09:03.389 align:start position:0% some cases but I think these are a few things<00:09:01.880> you<00:09:01.959> should<00:09:02.160> at<00:09:02.279> least<00:09:02.600> ask 00:09:03.389 --> 00:09:03.399 align:start position:0% things you should at least ask 00:09:03.399 --> 00:09:07.389 align:start position:0% things you should at least ask yourself<00:09:04.480> uh<00:09:05.480> so<00:09:06.040> like<00:09:06.200> how<00:09:06.440> strong<00:09:06.600> is<00:09:06.680> the 00:09:07.389 --> 00:09:07.399 align:start position:0% yourself uh so like how strong is the 00:09:07.399 --> 00:09:09.430 align:start position:0% yourself uh so like how strong is the cryptography<00:09:08.399> uh<00:09:08.519> and<00:09:08.680> yesterday's<00:09:09.160> opening 00:09:09.430 --> 00:09:09.440 align:start position:0% cryptography uh and yesterday's opening 00:09:09.440 --> 00:09:11.030 align:start position:0% cryptography uh and yesterday's opening remarks<00:09:09.920> ralic<00:09:10.240> mentioned<00:09:10.640> as<00:09:10.720> well<00:09:10.880> do<00:09:10.959> you 00:09:11.030 --> 00:09:11.040 align:start position:0% remarks ralic mentioned as well do you 00:09:11.040 --> 00:09:13.430 align:start position:0% remarks ralic mentioned as well do you want<00:09:11.160> it<00:09:11.240> to<00:09:11.360> be<00:09:12.240> Quantum<00:09:12.800> post<00:09:13.079> Quantum 00:09:13.430 --> 00:09:13.440 align:start position:0% want it to be Quantum post Quantum 00:09:13.440 --> 00:09:16.829 align:start position:0% want it to be Quantum post Quantum secure<00:09:14.160> does<00:09:14.399> that<00:09:14.560> matter<00:09:14.839> to<00:09:15.200> you<00:09:16.200> uh<00:09:16.600> is<00:09:16.680> it 00:09:16.829 --> 00:09:16.839 align:start position:0% secure does that matter to you uh is it 00:09:16.839 --> 00:09:19.310 align:start position:0% secure does that matter to you uh is it field<00:09:17.200> proving<00:09:18.160> is<00:09:18.279> it<00:09:18.640> is<00:09:18.720> it<00:09:18.839> been<00:09:19.000> running 00:09:19.310 --> 00:09:19.320 align:start position:0% field proving is it is it been running 00:09:19.320 --> 00:09:21.509 align:start position:0% field proving is it is it been running for<00:09:19.519> a<00:09:19.640> while<00:09:19.880> is<00:09:20.040> a<00:09:20.120> lot<00:09:20.279> of<00:09:20.399> economic<00:09:20.880> value 00:09:21.509 --> 00:09:21.519 align:start position:0% for a while is a lot of economic value 00:09:21.519 --> 00:09:23.470 align:start position:0% for a while is a lot of economic value writing<00:09:21.920> on<00:09:22.120> what's<00:09:22.320> been<00:09:22.480> running<00:09:22.959> up<00:09:23.120> until 00:09:23.470 --> 00:09:23.480 align:start position:0% writing on what's been running up until 00:09:23.480 --> 00:09:26.269 align:start position:0% writing on what's been running up until now<00:09:24.200> which<00:09:24.800> is<00:09:24.959> some<00:09:25.240> evidence<00:09:25.640> that<00:09:25.760> it's 00:09:26.269 --> 00:09:26.279 align:start position:0% now which is some evidence that it's 00:09:26.279 --> 00:09:28.990 align:start position:0% now which is some evidence that it's probably<00:09:27.279> field<00:09:27.680> proven<00:09:27.959> it's<00:09:28.160> probably<00:09:28.800> more 00:09:28.990 --> 00:09:29.000 align:start position:0% probably field proven it's probably more 00:09:29.000 --> 00:09:31.110 align:start position:0% probably field proven it's probably more sound 00:09:31.110 --> 00:09:31.120 align:start position:0% sound 00:09:31.120 --> 00:09:34.269 align:start position:0% sound uh<00:09:32.120> what<00:09:32.320> damage<00:09:32.640> can<00:09:32.800> the<00:09:32.959> operator<00:09:33.440> do<00:09:34.079> now 00:09:34.269 --> 00:09:34.279 align:start position:0% uh what damage can the operator do now 00:09:34.279 --> 00:09:35.949 align:start position:0% uh what damage can the operator do now now<00:09:34.440> here<00:09:34.680> again<00:09:35.160> sometimes<00:09:35.320> it's<00:09:35.440> a<00:09:35.600> single 00:09:35.949 --> 00:09:35.959 align:start position:0% now here again sometimes it's a single 00:09:35.959 --> 00:09:38.710 align:start position:0% now here again sometimes it's a single operator<00:09:36.640> which<00:09:36.800> makes<00:09:37.000> it<00:09:37.160> very<00:09:37.560> very<00:09:37.959> uh<00:09:38.360> uh 00:09:38.710 --> 00:09:38.720 align:start position:0% operator which makes it very very uh uh 00:09:38.720 --> 00:09:41.030 align:start position:0% operator which makes it very very uh uh important<00:09:39.320> but<00:09:39.519> also<00:09:39.760> if<00:09:39.880> it's<00:09:40.240> uh<00:09:40.720> it's<00:09:40.880> some 00:09:41.030 --> 00:09:41.040 align:start position:0% important but also if it's uh it's some 00:09:41.040 --> 00:09:43.350 align:start position:0% important but also if it's uh it's some decentralized<00:09:41.680> network<00:09:42.600> if<00:09:42.720> you<00:09:42.880> have<00:09:43.160> like<00:09:43.279> a 00:09:43.350 --> 00:09:43.360 align:start position:0% decentralized network if you have like a 00:09:43.360 --> 00:09:44.949 align:start position:0% decentralized network if you have like a malicious<00:09:43.839> majority<00:09:44.240> for<00:09:44.399> a<00:09:44.480> certain<00:09:44.720> period 00:09:44.949 --> 00:09:44.959 align:start position:0% malicious majority for a certain period 00:09:44.959 --> 00:09:46.670 align:start position:0% malicious majority for a certain period of<00:09:45.079> time<00:09:45.240> what's<00:09:45.519> the<00:09:45.880> what's<00:09:46.079> the<00:09:46.440> worst 00:09:46.670 --> 00:09:46.680 align:start position:0% of time what's the what's the worst 00:09:46.680 --> 00:09:49.389 align:start position:0% of time what's the what's the worst thing<00:09:46.880> they<00:09:47.000> could<00:09:47.360> do<00:09:48.360> could<00:09:48.519> they<00:09:48.680> steal 00:09:49.389 --> 00:09:49.399 align:start position:0% thing they could do could they steal 00:09:49.399 --> 00:09:51.590 align:start position:0% thing they could do could they steal tokens<00:09:50.279> could<00:09:50.440> they<00:09:50.560> just<00:09:50.760> stop<00:09:51.040> the<00:09:51.240> network 00:09:51.590 --> 00:09:51.600 align:start position:0% tokens could they just stop the network 00:09:51.600 --> 00:09:52.870 align:start position:0% tokens could they just stop the network could<00:09:51.760> they<00:09:51.920> censor<00:09:52.360> there<00:09:52.440> are<00:09:52.600> different 00:09:52.870 --> 00:09:52.880 align:start position:0% could they censor there are different 00:09:52.880 --> 00:09:54.350 align:start position:0% could they censor there are different levels<00:09:53.200> of<00:09:53.440> of<00:09:53.600> damage<00:09:53.880> that<00:09:54.000> they<00:09:54.079> could<00:09:54.200> do 00:09:54.350 --> 00:09:54.360 align:start position:0% levels of of damage that they could do 00:09:54.360 --> 00:09:56.310 align:start position:0% levels of of damage that they could do and<00:09:54.480> different<00:09:54.680> networks<00:09:55.560> fall<00:09:55.920> differently 00:09:56.310 --> 00:09:56.320 align:start position:0% and different networks fall differently 00:09:56.320 --> 00:09:57.670 align:start position:0% and different networks fall differently in<00:09:56.480> these 00:09:57.670 --> 00:09:57.680 align:start position:0% in these 00:09:57.680 --> 00:09:59.710 align:start position:0% in these categories<00:09:58.680> uh<00:09:58.880> if<00:09:59.000> somebody<00:09:59.440> wants<00:09:59.600> to 00:09:59.710 --> 00:09:59.720 align:start position:0% categories uh if somebody wants to 00:09:59.720 --> 00:10:02.590 align:start position:0% categories uh if somebody wants to attack<00:09:59.959> the<00:10:00.079> network<00:10:00.440> how<00:10:00.640> expensive<00:10:01.120> is 00:10:02.590 --> 00:10:02.600 align:start position:0% attack the network how expensive is 00:10:02.600 --> 00:10:04.870 align:start position:0% attack the network how expensive is that<00:10:03.600> uh<00:10:03.680> so<00:10:03.920> this<00:10:04.120> this<00:10:04.200> is<00:10:04.320> from<00:10:04.480> vitalic 00:10:04.870 --> 00:10:04.880 align:start position:0% that uh so this this is from vitalic 00:10:04.880 --> 00:10:06.710 align:start position:0% that uh so this this is from vitalic talk<00:10:05.160> yesterday<00:10:05.519> he<00:10:05.680> actually<00:10:06.320> gave<00:10:06.480> us<00:10:06.600> a 00:10:06.710 --> 00:10:06.720 align:start position:0% talk yesterday he actually gave us a 00:10:06.720 --> 00:10:08.269 align:start position:0% talk yesterday he actually gave us a shout<00:10:06.959> out<00:10:07.120> for<00:10:07.440> for<00:10:07.640> this<00:10:07.760> thing<00:10:07.920> that<00:10:08.040> we've 00:10:08.269 --> 00:10:08.279 align:start position:0% shout out for for this thing that we've 00:10:08.279 --> 00:10:10.630 align:start position:0% shout out for for this thing that we've actually<00:10:08.480> done<00:10:08.680> three<00:10:08.920> years<00:10:09.160> ago<00:10:09.959> uh<00:10:10.519> this 00:10:10.630 --> 00:10:10.640 align:start position:0% actually done three years ago uh this 00:10:10.640 --> 00:10:13.509 align:start position:0% actually done three years ago uh this was<00:10:10.800> dydx<00:10:11.360> V3<00:10:11.880> which<00:10:12.000> was<00:10:12.200> built<00:10:12.480> on<00:10:13.200> uh<00:10:13.360> a 00:10:13.509 --> 00:10:13.519 align:start position:0% was dydx V3 which was built on uh a 00:10:13.519 --> 00:10:15.110 align:start position:0% was dydx V3 which was built on uh a product<00:10:13.839> that<00:10:14.000> we've<00:10:14.240> built<00:10:14.760> uh<00:10:14.880> was<00:10:15.000> an 00:10:15.110 --> 00:10:15.120 align:start position:0% product that we've built uh was an 00:10:15.120 --> 00:10:16.829 align:start position:0% product that we've built uh was an earlier<00:10:15.519> rollup<00:10:15.920> it<00:10:16.000> was<00:10:16.120> an<00:10:16.240> app<00:10:16.440> chain<00:10:16.680> in 00:10:16.829 --> 00:10:16.839 align:start position:0% earlier rollup it was an app chain in 00:10:16.839 --> 00:10:20.069 align:start position:0% earlier rollup it was an app chain in this<00:10:17.040> case<00:10:17.480> with<00:10:17.640> a<00:10:17.760> single<00:10:18.320> operator<00:10:19.320> but<00:10:19.839> now 00:10:20.069 --> 00:10:20.079 align:start position:0% this case with a single operator but now 00:10:20.079 --> 00:10:22.190 align:start position:0% this case with a single operator but now came<00:10:20.240> the<00:10:20.399> time<00:10:20.560> where<00:10:20.720> dydx<00:10:21.360> start<00:10:21.839> decided 00:10:22.190 --> 00:10:22.200 align:start position:0% came the time where dydx start decided 00:10:22.200 --> 00:10:23.670 align:start position:0% came the time where dydx start decided they<00:10:22.320> want<00:10:22.440> to<00:10:22.680> wind<00:10:22.920> it<00:10:23.120> down<00:10:23.480> and<00:10:23.600> they 00:10:23.670 --> 00:10:23.680 align:start position:0% they want to wind it down and they 00:10:23.680 --> 00:10:25.590 align:start position:0% they want to wind it down and they stopped<00:10:24.000> operating<00:10:24.480> network<00:10:24.959> but<00:10:25.079> the<00:10:25.160> users 00:10:25.590 --> 00:10:25.600 align:start position:0% stopped operating network but the users 00:10:25.600 --> 00:10:27.910 align:start position:0% stopped operating network but the users can<00:10:25.800> still<00:10:26.760> uh<00:10:26.880> pull<00:10:27.120> their<00:10:27.320> funds<00:10:27.640> off 00:10:27.910 --> 00:10:27.920 align:start position:0% can still uh pull their funds off 00:10:27.920 --> 00:10:30.069 align:start position:0% can still uh pull their funds off because<00:10:28.160> we<00:10:28.320> designed<00:10:28.800> this<00:10:29.440> uh<00:10:29.560> mechanism<00:10:29.959> we 00:10:30.069 --> 00:10:30.079 align:start position:0% because we designed this uh mechanism we 00:10:30.079 --> 00:10:32.230 align:start position:0% because we designed this uh mechanism we called<00:10:30.279> an<00:10:30.399> escaped<00:10:30.800> hash<00:10:31.120> that<00:10:31.240> was<00:10:31.399> back<00:10:31.519> in 00:10:32.230 --> 00:10:32.240 align:start position:0% called an escaped hash that was back in 00:10:32.240 --> 00:10:34.430 align:start position:0% called an escaped hash that was back in 2021<00:10:33.240> but<00:10:33.399> this<00:10:33.519> is<00:10:33.880> something<00:10:34.120> that<00:10:34.279> if<00:10:34.360> you 00:10:34.430 --> 00:10:34.440 align:start position:0% 2021 but this is something that if you 00:10:34.440 --> 00:10:35.990 align:start position:0% 2021 but this is something that if you don't<00:10:34.640> think<00:10:34.839> about<00:10:35.120> beforehand<00:10:35.600> you<00:10:35.680> may<00:10:35.880> end 00:10:35.990 --> 00:10:36.000 align:start position:0% don't think about beforehand you may end 00:10:36.000 --> 00:10:37.829 align:start position:0% don't think about beforehand you may end up<00:10:36.160> having<00:10:36.399> a<00:10:36.560> problem 00:10:37.829 --> 00:10:37.839 align:start position:0% up having a problem 00:10:37.839 --> 00:10:40.430 align:start position:0% up having a problem afterwards<00:10:38.839> okay<00:10:39.279> one<00:10:39.440> of<00:10:39.560> the<00:10:39.720> major<00:10:40.040> things 00:10:40.430 --> 00:10:40.440 align:start position:0% afterwards okay one of the major things 00:10:40.440 --> 00:10:42.790 align:start position:0% afterwards okay one of the major things people<00:10:40.720> use<00:10:41.399> uh<00:10:41.519> layer<00:10:41.880> Twos<00:10:42.160> for<00:10:42.399> is<00:10:42.560> because 00:10:42.790 --> 00:10:42.800 align:start position:0% people use uh layer Twos for is because 00:10:42.800 --> 00:10:44.470 align:start position:0% people use uh layer Twos for is because they<00:10:42.959> solve<00:10:43.399> the<00:10:43.600> the<00:10:43.720> throughput<00:10:44.160> issue<00:10:44.360> the 00:10:44.470 --> 00:10:44.480 align:start position:0% they solve the the throughput issue the 00:10:44.480 --> 00:10:48.829 align:start position:0% they solve the the throughput issue the scalability<00:10:45.519> issue<00:10:46.519> so<00:10:47.160> what<00:10:47.279> are<00:10:47.680> uh<00:10:48.160> uh<00:10:48.720> what 00:10:48.829 --> 00:10:48.839 align:start position:0% scalability issue so what are uh uh what 00:10:48.839 --> 00:10:50.350 align:start position:0% scalability issue so what are uh uh what are<00:10:49.000> the<00:10:49.160> main<00:10:49.519> things<00:10:49.800> that<00:10:49.959> limit<00:10:50.240> the 00:10:50.350 --> 00:10:50.360 align:start position:0% are the main things that limit the 00:10:50.360 --> 00:10:53.069 align:start position:0% are the main things that limit the throughput<00:10:50.839> so<00:10:50.920> if<00:10:51.000> you<00:10:51.120> look<00:10:51.240> at<00:10:51.360> layer<00:10:52.079> ones 00:10:53.069 --> 00:10:53.079 align:start position:0% throughput so if you look at layer ones 00:10:53.079 --> 00:10:54.629 align:start position:0% throughput so if you look at layer ones uh<00:10:53.480> they<00:10:53.600> have<00:10:53.720> to<00:10:53.959> execute<00:10:54.360> all<00:10:54.480> the 00:10:54.629 --> 00:10:54.639 align:start position:0% uh they have to execute all the 00:10:54.639 --> 00:10:56.430 align:start position:0% uh they have to execute all the transactions<00:10:55.360> all<00:10:55.560> nodes<00:10:55.920> execute<00:10:56.279> all 00:10:56.430 --> 00:10:56.440 align:start position:0% transactions all nodes execute all 00:10:56.440 --> 00:10:59.310 align:start position:0% transactions all nodes execute all transactions<00:10:56.959> like<00:10:57.079> I<00:10:57.200> said<00:10:57.519> before<00:10:58.519> there 00:10:59.310 --> 00:10:59.320 align:start position:0% transactions like I said before there 00:10:59.320 --> 00:11:00.750 align:start position:0% transactions like I said before there subset<00:10:59.600> of<00:10:59.680> the<00:10:59.760> nodes<00:11:00.040> that<00:11:00.200> take<00:11:00.399> part<00:11:00.560> in 00:11:00.750 --> 00:11:00.760 align:start position:0% subset of the nodes that take part in 00:11:00.760 --> 00:11:02.750 align:start position:0% subset of the nodes that take part in consensus<00:11:01.360> but<00:11:01.480> a<00:11:01.639> large<00:11:01.920> subset<00:11:02.320> so<00:11:02.519> this<00:11:02.600> is 00:11:02.750 --> 00:11:02.760 align:start position:0% consensus but a large subset so this is 00:11:02.760 --> 00:11:04.110 align:start position:0% consensus but a large subset so this is also<00:11:03.040> quite 00:11:04.110 --> 00:11:04.120 align:start position:0% also quite 00:11:04.120 --> 00:11:06.590 align:start position:0% also quite expensive<00:11:05.120> uh<00:11:05.320> and<00:11:05.639> all<00:11:05.800> the<00:11:05.959> data<00:11:06.240> is<00:11:06.440> there 00:11:06.590 --> 00:11:06.600 align:start position:0% expensive uh and all the data is there 00:11:06.600 --> 00:11:08.470 align:start position:0% expensive uh and all the data is there for<00:11:06.839> everybody<00:11:07.399> right<00:11:07.519> so<00:11:07.639> you<00:11:07.800> have<00:11:08.240> all 00:11:08.470 --> 00:11:08.480 align:start position:0% for everybody right so you have all 00:11:08.480 --> 00:11:10.190 align:start position:0% for everybody right so you have all these<00:11:08.680> things<00:11:08.880> are<00:11:09.120> things<00:11:09.320> that<00:11:09.560> potentially 00:11:10.190 --> 00:11:10.200 align:start position:0% these things are things that potentially 00:11:10.200 --> 00:11:11.910 align:start position:0% these things are things that potentially limit<00:11:10.519> the<00:11:10.639> throughput<00:11:11.440> because<00:11:11.639> you<00:11:11.720> want 00:11:11.910 --> 00:11:11.920 align:start position:0% limit the throughput because you want 00:11:11.920 --> 00:11:13.949 align:start position:0% limit the throughput because you want everybody<00:11:12.240> to<00:11:12.360> be<00:11:12.480> able<00:11:12.680> to<00:11:12.839> run<00:11:13.079> it<00:11:13.680> now<00:11:13.839> the 00:11:13.949 --> 00:11:13.959 align:start position:0% everybody to be able to run it now the 00:11:13.959 --> 00:11:15.670 align:start position:0% everybody to be able to run it now the secret<00:11:14.279> sauce<00:11:14.639> that<00:11:14.760> we<00:11:14.920> have<00:11:15.079> I<00:11:15.279> mentioned<00:11:15.519> it 00:11:15.670 --> 00:11:15.680 align:start position:0% secret sauce that we have I mentioned it 00:11:15.680 --> 00:11:18.949 align:start position:0% secret sauce that we have I mentioned it before<00:11:15.920> is<00:11:16.160> proofs<00:11:16.639> and<00:11:17.279> proofs<00:11:18.279> affect<00:11:18.639> scale 00:11:18.949 --> 00:11:18.959 align:start position:0% before is proofs and proofs affect scale 00:11:18.959 --> 00:11:20.829 align:start position:0% before is proofs and proofs affect scale in<00:11:19.160> two<00:11:19.360> main<00:11:19.720> aspects<00:11:20.160> the<00:11:20.240> main<00:11:20.440> one<00:11:20.600> is<00:11:20.720> the 00:11:20.829 --> 00:11:20.839 align:start position:0% in two main aspects the main one is the 00:11:20.839 --> 00:11:23.430 align:start position:0% in two main aspects the main one is the one<00:11:20.959> I<00:11:21.079> mentioned<00:11:21.480> before<00:11:22.279> we<00:11:22.440> don't<00:11:22.720> need<00:11:23.040> all 00:11:23.430 --> 00:11:23.440 align:start position:0% one I mentioned before we don't need all 00:11:23.440 --> 00:11:25.069 align:start position:0% one I mentioned before we don't need all the<00:11:23.519> nodes<00:11:23.880> to<00:11:24.000> run<00:11:24.200> the<00:11:24.320> transactions<00:11:24.959> we 00:11:25.069 --> 00:11:25.079 align:start position:0% the nodes to run the transactions we 00:11:25.079 --> 00:11:26.710 align:start position:0% the nodes to run the transactions we just<00:11:25.200> need<00:11:25.360> the<00:11:25.519> consensus<00:11:26.000> nodes<00:11:26.240> to<00:11:26.360> run<00:11:26.600> all 00:11:26.710 --> 00:11:26.720 align:start position:0% just need the consensus nodes to run all 00:11:26.720 --> 00:11:28.190 align:start position:0% just need the consensus nodes to run all the<00:11:26.839> actions<00:11:27.200> these<00:11:27.519> there<00:11:27.600> are<00:11:27.720> a<00:11:27.800> lot<00:11:28.000> less 00:11:28.190 --> 00:11:28.200 align:start position:0% the actions these there are a lot less 00:11:28.200 --> 00:11:30.430 align:start position:0% the actions these there are a lot less of<00:11:28.360> them<00:11:28.680> and<00:11:28.880> this<00:11:29.560> means<00:11:29.800> that<00:11:29.920> you<00:11:30.000> can<00:11:30.160> do<00:11:30.279> a 00:11:30.430 --> 00:11:30.440 align:start position:0% of them and this means that you can do a 00:11:30.440 --> 00:11:32.110 align:start position:0% of them and this means that you can do a lot<00:11:30.639> a<00:11:30.760> lot<00:11:30.920> more<00:11:31.160> execution<00:11:31.600> orders<00:11:31.959> of 00:11:32.110 --> 00:11:32.120 align:start position:0% lot a lot more execution orders of 00:11:32.120 --> 00:11:34.750 align:start position:0% lot a lot more execution orders of magnitude<00:11:32.600> more<00:11:33.240> execution<00:11:34.240> the<00:11:34.399> other 00:11:34.750 --> 00:11:34.760 align:start position:0% magnitude more execution the other 00:11:34.760 --> 00:11:37.350 align:start position:0% magnitude more execution the other aspect<00:11:35.279> is<00:11:35.560> that<00:11:36.000> it<00:11:36.160> actually<00:11:36.839> enables 00:11:37.350 --> 00:11:37.360 align:start position:0% aspect is that it actually enables 00:11:37.360 --> 00:11:39.949 align:start position:0% aspect is that it actually enables submitting<00:11:37.760> a<00:11:37.920> lot<00:11:38.160> less<00:11:38.440> data<00:11:38.720> to<00:11:38.959> layer<00:11:39.240> one 00:11:39.949 --> 00:11:39.959 align:start position:0% submitting a lot less data to layer one 00:11:39.959 --> 00:11:42.190 align:start position:0% submitting a lot less data to layer one because<00:11:40.200> we<00:11:40.320> could<00:11:40.480> just<00:11:40.720> submit<00:11:41.160> the<00:11:41.800> state 00:11:42.190 --> 00:11:42.200 align:start position:0% because we could just submit the state 00:11:42.200 --> 00:11:44.590 align:start position:0% because we could just submit the state diffs<00:11:43.000> for<00:11:43.279> every<00:11:43.639> bunch<00:11:43.880> of<00:11:44.040> transactions 00:11:44.590 --> 00:11:44.600 align:start position:0% diffs for every bunch of transactions 00:11:44.600 --> 00:11:45.829 align:start position:0% diffs for every bunch of transactions you<00:11:44.720> don't<00:11:44.839> need<00:11:45.000> to<00:11:45.120> have<00:11:45.320> each<00:11:45.480> and<00:11:45.639> every 00:11:45.829 --> 00:11:45.839 align:start position:0% you don't need to have each and every 00:11:45.839 --> 00:11:48.150 align:start position:0% you don't need to have each and every transaction<00:11:46.360> with<00:11:46.519> all<00:11:46.680> its 00:11:48.150 --> 00:11:48.160 align:start position:0% transaction with all its 00:11:48.160 --> 00:11:51.269 align:start position:0% transaction with all its data<00:11:49.160> uh<00:11:49.639> optimistic<00:11:50.160> rollups<00:11:50.639> for<00:11:50.760> instance 00:11:51.269 --> 00:11:51.279 align:start position:0% data uh optimistic rollups for instance 00:11:51.279 --> 00:11:52.590 align:start position:0% data uh optimistic rollups for instance which<00:11:51.440> don't<00:11:51.680> use 00:11:52.590 --> 00:11:52.600 align:start position:0% which don't use 00:11:52.600 --> 00:11:54.910 align:start position:0% which don't use proofs<00:11:53.600> uh<00:11:53.880> either<00:11:54.240> sacrifice 00:11:54.910 --> 00:11:54.920 align:start position:0% proofs uh either sacrifice 00:11:54.920 --> 00:11:56.750 align:start position:0% proofs uh either sacrifice decentralization<00:11:55.920> or<00:11:56.079> they<00:11:56.240> sacrifice 00:11:56.750 --> 00:11:56.760 align:start position:0% decentralization or they sacrifice 00:11:56.760 --> 00:11:59.470 align:start position:0% decentralization or they sacrifice security<00:11:57.240> because<00:11:57.760> at<00:11:57.880> the<00:11:57.959> end<00:11:58.120> of<00:11:58.279> the<00:11:58.440> day 00:11:59.470 --> 00:11:59.480 align:start position:0% security because at the end of the day 00:11:59.480 --> 00:12:01.389 align:start position:0% security because at the end of the day if<00:11:59.600> you<00:11:59.680> want<00:11:59.839> to<00:12:00.560> make<00:12:00.760> sure<00:12:01.079> that<00:12:01.240> the 00:12:01.389 --> 00:12:01.399 align:start position:0% if you want to make sure that the 00:12:01.399 --> 00:12:02.949 align:start position:0% if you want to make sure that the transactions<00:12:01.839> are<00:12:02.000> indeed<00:12:02.279> secure<00:12:02.639> you<00:12:02.760> still 00:12:02.949 --> 00:12:02.959 align:start position:0% transactions are indeed secure you still 00:12:02.959 --> 00:12:05.550 align:start position:0% transactions are indeed secure you still need<00:12:03.200> each<00:12:03.360> and<00:12:03.519> every<00:12:03.680> full<00:12:03.959> node<00:12:04.200> to<00:12:04.959> to<00:12:05.399> uh 00:12:05.550 --> 00:12:05.560 align:start position:0% need each and every full node to to uh 00:12:05.560 --> 00:12:07.750 align:start position:0% need each and every full node to to uh execute<00:12:05.959> all<00:12:06.079> the<00:12:06.440> transactions<00:12:07.440> and<00:12:07.639> you 00:12:07.750 --> 00:12:07.760 align:start position:0% execute all the transactions and you 00:12:07.760 --> 00:12:09.430 align:start position:0% execute all the transactions and you also<00:12:08.000> need<00:12:08.160> to<00:12:08.360> submit<00:12:08.680> all<00:12:08.800> the<00:12:08.959> transaction 00:12:09.430 --> 00:12:09.440 align:start position:0% also need to submit all the transaction 00:12:09.440 --> 00:12:11.269 align:start position:0% also need to submit all the transaction data<00:12:09.639> to<00:12:09.800> layer<00:12:10.040> one<00:12:10.399> because<00:12:10.760> you<00:12:10.880> need<00:12:11.120> that 00:12:11.269 --> 00:12:11.279 align:start position:0% data to layer one because you need that 00:12:11.279 --> 00:12:14.590 align:start position:0% data to layer one because you need that for<00:12:11.440> the<00:12:11.560> optimistic<00:12:12.480> for<00:12:12.680> the<00:12:12.880> fraud<00:12:13.199> proof 00:12:14.590 --> 00:12:14.600 align:start position:0% for the optimistic for the fraud proof 00:12:14.600 --> 00:12:17.189 align:start position:0% for the optimistic for the fraud proof mechanism<00:12:15.600> uh<00:12:15.760> so<00:12:15.959> when<00:12:16.120> you<00:12:16.279> compare<00:12:17.040> uh 00:12:17.189 --> 00:12:17.199 align:start position:0% mechanism uh so when you compare uh 00:12:17.199 --> 00:12:19.670 align:start position:0% mechanism uh so when you compare uh validity<00:12:17.639> rollups<00:12:18.199> in<00:12:18.320> terms<00:12:18.560> of<00:12:18.720> throughput 00:12:19.670 --> 00:12:19.680 align:start position:0% validity rollups in terms of throughput 00:12:19.680 --> 00:12:21.150 align:start position:0% validity rollups in terms of throughput looking<00:12:19.959> towards<00:12:20.320> the<00:12:20.440> future<00:12:20.800> the<00:12:20.920> main 00:12:21.150 --> 00:12:21.160 align:start position:0% looking towards the future the main 00:12:21.160 --> 00:12:23.310 align:start position:0% looking towards the future the main thing<00:12:21.320> you<00:12:21.399> should<00:12:21.639> look<00:12:21.839> at<00:12:22.720> is<00:12:22.920> like<00:12:23.079> the 00:12:23.310 --> 00:12:23.320 align:start position:0% thing you should look at is like the 00:12:23.320 --> 00:12:26.430 align:start position:0% thing you should look at is like the execution<00:12:23.920> times<00:12:24.639> like<00:12:24.959> how<00:12:25.760> efficient<00:12:26.279> is 00:12:26.430 --> 00:12:26.440 align:start position:0% execution times like how efficient is 00:12:26.440 --> 00:12:28.470 align:start position:0% execution times like how efficient is the<00:12:26.560> sequencing<00:12:27.120> of<00:12:27.279> that<00:12:27.480> network<00:12:28.279> if<00:12:28.360> you 00:12:28.470 --> 00:12:28.480 align:start position:0% the sequencing of that network if you 00:12:28.480 --> 00:12:30.470 align:start position:0% the sequencing of that network if you look<00:12:28.600> at<00:12:28.760> optimistic<00:12:29.199> scoll<00:12:29.480> up<00:12:29.680> you<00:12:29.920> you<00:12:30.360> you 00:12:30.470 --> 00:12:30.480 align:start position:0% look at optimistic scoll up you you you 00:12:30.480 --> 00:12:32.430 align:start position:0% look at optimistic scoll up you you you need<00:12:30.639> to<00:12:31.079> look<00:12:31.279> even<00:12:31.480> more<00:12:31.760> strongly<00:12:32.079> at<00:12:32.240> that 00:12:32.430 --> 00:12:32.440 align:start position:0% need to look even more strongly at that 00:12:32.440 --> 00:12:33.710 align:start position:0% need to look even more strongly at that it's<00:12:32.560> going<00:12:32.680> to<00:12:32.760> be<00:12:32.880> much<00:12:33.040> more<00:12:33.199> limited<00:12:33.560> but 00:12:33.710 --> 00:12:33.720 align:start position:0% it's going to be much more limited but 00:12:33.720 --> 00:12:35.590 align:start position:0% it's going to be much more limited but also<00:12:33.920> on<00:12:34.079> the 00:12:35.590 --> 00:12:35.600 align:start position:0% also on the 00:12:35.600 --> 00:12:38.389 align:start position:0% also on the data<00:12:36.600> so<00:12:36.760> for<00:12:36.880> instance<00:12:37.199> with<00:12:37.360> Stark<00:12:37.720> net<00:12:38.240> uh 00:12:38.389 --> 00:12:38.399 align:start position:0% data so for instance with Stark net uh 00:12:38.399 --> 00:12:40.269 align:start position:0% data so for instance with Stark net uh here<00:12:38.519> you<00:12:38.639> could<00:12:38.800> see<00:12:39.040> things<00:12:39.360> that<00:12:40.000> these<00:12:40.120> are 00:12:40.269 --> 00:12:40.279 align:start position:0% here you could see things that these are 00:12:40.279 --> 00:12:41.590 align:start position:0% here you could see things that these are actual<00:12:40.560> measurements<00:12:41.000> from<00:12:41.120> the<00:12:41.279> live 00:12:41.590 --> 00:12:41.600 align:start position:0% actual measurements from the live 00:12:41.600 --> 00:12:44.030 align:start position:0% actual measurements from the live Network<00:12:42.040> as<00:12:42.160> you<00:12:42.240> could<00:12:42.399> see<00:12:42.639> this<00:12:42.760> is<00:12:43.519> greatly 00:12:44.030 --> 00:12:44.040 align:start position:0% Network as you could see this is greatly 00:12:44.040 --> 00:12:46.670 align:start position:0% Network as you could see this is greatly increasing<00:12:45.040> uh<00:12:45.720> mainly<00:12:46.040> since<00:12:46.199> we're<00:12:46.399> putting 00:12:46.670 --> 00:12:46.680 align:start position:0% increasing uh mainly since we're putting 00:12:46.680 --> 00:12:48.949 align:start position:0% increasing uh mainly since we're putting an<00:12:47.079> an<00:12:47.240> extended<00:12:47.839> effort<00:12:48.160> on<00:12:48.360> that<00:12:48.680> on<00:12:48.839> this 00:12:48.949 --> 00:12:48.959 align:start position:0% an an extended effort on that on this 00:12:48.959 --> 00:12:50.670 align:start position:0% an an extended effort on that on this and<00:12:49.120> this<00:12:49.240> will<00:12:49.480> continue<00:12:50.279> and<00:12:50.399> this<00:12:50.480> will 00:12:50.670 --> 00:12:50.680 align:start position:0% and this will continue and this will 00:12:50.680 --> 00:12:52.110 align:start position:0% and this will continue and this will also<00:12:50.880> continue<00:12:51.199> when<00:12:51.360> the<00:12:51.440> network<00:12:51.800> is<00:12:51.920> very 00:12:52.110 --> 00:12:52.120 align:start position:0% also continue when the network is very 00:12:52.120 --> 00:12:53.829 align:start position:0% also continue when the network is very decentralized<00:12:52.839> because<00:12:53.079> as<00:12:53.240> I<00:12:53.360> said<00:12:53.560> we<00:12:53.639> don't 00:12:53.829 --> 00:12:53.839 align:start position:0% decentralized because as I said we don't 00:12:53.839 --> 00:12:56.110 align:start position:0% decentralized because as I said we don't need<00:12:54.000> all<00:12:54.199> full<00:12:54.440> nod<00:12:54.720> to<00:12:54.920> execute<00:12:55.600> so<00:12:55.800> this<00:12:55.920> is 00:12:56.110 --> 00:12:56.120 align:start position:0% need all full nod to execute so this is 00:12:56.120 --> 00:12:57.350 align:start position:0% need all full nod to execute so this is just<00:12:56.360> the<00:12:56.600> the<00:12:56.760> efficiency<00:12:57.160> of<00:12:57.279> the 00:12:57.350 --> 00:12:57.360 align:start position:0% just the the efficiency of the 00:12:57.360 --> 00:12:59.910 align:start position:0% just the the efficiency of the sequencers<00:12:58.120> themselves 00:12:59.910 --> 00:12:59.920 align:start position:0% sequencers themselves 00:12:59.920 --> 00:13:03.269 align:start position:0% sequencers themselves so<00:13:00.120> that's<00:13:00.360> throughput<00:13:01.680> cost<00:13:02.680> is<00:13:02.959> quite 00:13:03.269 --> 00:13:03.279 align:start position:0% so that's throughput cost is quite 00:13:03.279 --> 00:13:05.389 align:start position:0% so that's throughput cost is quite similar<00:13:03.760> but<00:13:03.920> not<00:13:04.199> exactly<00:13:04.760> the<00:13:04.880> same<00:13:05.160> I<00:13:05.199> mean 00:13:05.389 --> 00:13:05.399 align:start position:0% similar but not exactly the same I mean 00:13:05.399 --> 00:13:06.790 align:start position:0% similar but not exactly the same I mean the<00:13:05.519> main<00:13:05.760> difference<00:13:06.120> here<00:13:06.279> is<00:13:06.480> that<00:13:06.680> at 00:13:06.790 --> 00:13:06.800 align:start position:0% the main difference here is that at 00:13:06.800 --> 00:13:08.990 align:start position:0% the main difference here is that at least<00:13:07.680> with<00:13:07.839> validity<00:13:08.240> RS<00:13:08.639> you<00:13:08.720> have<00:13:08.839> an 00:13:08.990 --> 00:13:09.000 align:start position:0% least with validity RS you have an 00:13:09.000 --> 00:13:10.389 align:start position:0% least with validity RS you have an additional<00:13:09.519> aspect<00:13:09.839> here<00:13:10.040> which<00:13:10.160> is<00:13:10.279> the 00:13:10.389 --> 00:13:10.399 align:start position:0% additional aspect here which is the 00:13:10.399 --> 00:13:12.110 align:start position:0% additional aspect here which is the prover<00:13:11.000> right<00:13:11.160> because<00:13:11.320> we<00:13:11.399> need<00:13:11.519> to<00:13:11.639> generate 00:13:12.110 --> 00:13:12.120 align:start position:0% prover right because we need to generate 00:13:12.120 --> 00:13:14.629 align:start position:0% prover right because we need to generate proofs<00:13:13.120> indeed<00:13:13.440> it's<00:13:13.600> always<00:13:13.839> a<00:13:14.040> single<00:13:14.360> node 00:13:14.629 --> 00:13:14.639 align:start position:0% proofs indeed it's always a single node 00:13:14.639 --> 00:13:15.949 align:start position:0% proofs indeed it's always a single node that<00:13:14.720> needs<00:13:14.920> to<00:13:15.000> generate<00:13:15.360> a<00:13:15.519> proof<00:13:15.720> for<00:13:15.839> a 00:13:15.949 --> 00:13:15.959 align:start position:0% that needs to generate a proof for a 00:13:15.959 --> 00:13:17.550 align:start position:0% that needs to generate a proof for a block<00:13:16.320> but<00:13:16.440> it's<00:13:16.639> still<00:13:17.160> it's<00:13:17.279> still 00:13:17.550 --> 00:13:17.560 align:start position:0% block but it's still it's still 00:13:17.560 --> 00:13:19.350 align:start position:0% block but it's still it's still expensive<00:13:18.079> so<00:13:18.279> if<00:13:18.360> you<00:13:18.519> look<00:13:18.720> at<00:13:19.160> if<00:13:19.240> you 00:13:19.350 --> 00:13:19.360 align:start position:0% expensive so if you look at if you 00:13:19.360 --> 00:13:21.350 align:start position:0% expensive so if you look at if you compare<00:13:19.720> validity<00:13:20.120> rollups<00:13:20.600> to<00:13:21.040> to<00:13:21.160> one 00:13:21.350 --> 00:13:21.360 align:start position:0% compare validity rollups to to one 00:13:21.360 --> 00:13:24.430 align:start position:0% compare validity rollups to to one another<00:13:22.079> you<00:13:22.240> need<00:13:22.399> to<00:13:22.600> look<00:13:23.320> both<00:13:23.519> on<00:13:23.800> the 00:13:24.430 --> 00:13:24.440 align:start position:0% another you need to look both on the 00:13:24.440 --> 00:13:26.350 align:start position:0% another you need to look both on the sequencer<00:13:25.079> cost<00:13:25.360> and<00:13:25.560> also<00:13:25.800> on<00:13:25.959> the<00:13:26.160> on<00:13:26.279> the 00:13:26.350 --> 00:13:26.360 align:start position:0% sequencer cost and also on the on the 00:13:26.360 --> 00:13:29.629 align:start position:0% sequencer cost and also on the on the prover<00:13:27.079> cost<00:13:28.079> optimistic<00:13:28.519> rollups<00:13:28.880> and<00:13:29.160> L<00:13:29.519> uh 00:13:29.629 --> 00:13:29.639 align:start position:0% prover cost optimistic rollups and L uh 00:13:29.639 --> 00:13:34.150 align:start position:0% prover cost optimistic rollups and L uh L<00:13:29.880> ones<00:13:30.160> typically<00:13:30.519> don't<00:13:30.800> have 00:13:34.150 --> 00:13:34.160 align:start position:0% 00:13:34.160 --> 00:13:36.790 align:start position:0% that<00:13:35.160> so<00:13:35.360> this<00:13:35.480> is<00:13:35.720> the<00:13:36.120> this<00:13:36.240> is<00:13:36.320> a<00:13:36.440> similar 00:13:36.790 --> 00:13:36.800 align:start position:0% that so this is the this is a similar 00:13:36.800 --> 00:13:39.110 align:start position:0% that so this is the this is a similar graph<00:13:37.079> from<00:13:37.360> uh<00:13:37.480> the<00:13:37.600> cost<00:13:37.800> of<00:13:37.959> storet<00:13:38.880> uh<00:13:39.000> as 00:13:39.110 --> 00:13:39.120 align:start position:0% graph from uh the cost of storet uh as 00:13:39.120 --> 00:13:40.590 align:start position:0% graph from uh the cost of storet uh as much<00:13:39.279> as<00:13:39.360> I<00:13:39.480> would<00:13:39.600> like<00:13:39.760> to<00:13:39.880> take<00:13:40.120> credit<00:13:40.360> for 00:13:40.590 --> 00:13:40.600 align:start position:0% much as I would like to take credit for 00:13:40.600 --> 00:13:43.069 align:start position:0% much as I would like to take credit for this<00:13:40.880> the<00:13:41.199> big<00:13:41.440> drop<00:13:41.760> that<00:13:41.839> you<00:13:42.000> see<00:13:42.240> here<00:13:42.920> uh 00:13:43.069 --> 00:13:43.079 align:start position:0% this the big drop that you see here uh 00:13:43.079 --> 00:13:45.069 align:start position:0% this the big drop that you see here uh didn't<00:13:43.399> have<00:13:43.600> that<00:13:43.760> much<00:13:43.920> to<00:13:44.040> do<00:13:44.240> with<00:13:44.399> us<00:13:44.920> it 00:13:45.069 --> 00:13:45.079 align:start position:0% didn't have that much to do with us it 00:13:45.079 --> 00:13:47.949 align:start position:0% didn't have that much to do with us it was<00:13:45.279> actually<00:13:45.480> due<00:13:45.680> to<00:13:45.800> 4844<00:13:46.760> from<00:13:46.959> ethereum 00:13:47.949 --> 00:13:47.959 align:start position:0% was actually due to 4844 from ethereum 00:13:47.959 --> 00:13:50.749 align:start position:0% was actually due to 4844 from ethereum uh<00:13:48.040> when<00:13:48.199> ethereum<00:13:48.600> moved<00:13:48.839> to<00:13:49.079> blobs<00:13:50.079> uh<00:13:50.560> like 00:13:50.749 --> 00:13:50.759 align:start position:0% uh when ethereum moved to blobs uh like 00:13:50.759 --> 00:13:52.470 align:start position:0% uh when ethereum moved to blobs uh like the<00:13:50.920> data<00:13:51.240> cost<00:13:51.519> submitted<00:13:51.880> to<00:13:52.000> layer<00:13:52.240> one 00:13:52.470 --> 00:13:52.480 align:start position:0% the data cost submitted to layer one 00:13:52.480 --> 00:13:54.949 align:start position:0% the data cost submitted to layer one effectively<00:13:52.920> went<00:13:53.199> down<00:13:53.360> to<00:13:53.680> zero<00:13:54.680> uh<00:13:54.800> and 00:13:54.949 --> 00:13:54.959 align:start position:0% effectively went down to zero uh and 00:13:54.959 --> 00:13:57.350 align:start position:0% effectively went down to zero uh and that's<00:13:55.120> the<00:13:55.240> big<00:13:55.399> drop<00:13:55.680> you<00:13:55.800> see<00:13:56.040> over<00:13:56.279> here<00:13:57.120> uh 00:13:57.350 --> 00:13:57.360 align:start position:0% that's the big drop you see over here uh 00:13:57.360 --> 00:13:59.230 align:start position:0% that's the big drop you see over here uh but<00:13:57.639> and<00:13:57.800> that's<00:13:58.000> important<00:13:58.279> to<00:13:58.440> realize<00:13:59.160> this 00:13:59.230 --> 00:13:59.240 align:start position:0% but and that's important to realize this 00:13:59.240 --> 00:14:00.870 align:start position:0% but and that's important to realize this is<00:13:59.399> not<00:13:59.600> going<00:13:59.680> to<00:13:59.839> stay<00:14:00.160> this<00:14:00.279> way<00:14:00.680> I<00:14:00.720> mean 00:14:00.870 --> 00:14:00.880 align:start position:0% is not going to stay this way I mean 00:14:00.880 --> 00:14:02.829 align:start position:0% is not going to stay this way I mean it's<00:14:01.120> already<00:14:01.680> on<00:14:01.800> the<00:14:01.920> verge<00:14:02.160> of<00:14:02.320> congesting 00:14:02.829 --> 00:14:02.839 align:start position:0% it's already on the verge of congesting 00:14:02.839 --> 00:14:04.590 align:start position:0% it's already on the verge of congesting now<00:14:03.079> once<00:14:03.199> it<00:14:03.360> starts<00:14:03.639> congesting<00:14:04.279> it's<00:14:04.519> it's 00:14:04.590 --> 00:14:04.600 align:start position:0% now once it starts congesting it's it's 00:14:04.600 --> 00:14:06.790 align:start position:0% now once it starts congesting it's it's a<00:14:04.759> market<00:14:05.320> data<00:14:05.639> prices<00:14:05.920> are<00:14:06.040> going<00:14:06.160> to<00:14:06.360> go<00:14:06.560> go 00:14:06.790 --> 00:14:06.800 align:start position:0% a market data prices are going to go go 00:14:06.800 --> 00:14:10.389 align:start position:0% a market data prices are going to go go up<00:14:07.800> how<00:14:07.959> much<00:14:08.240> up<00:14:09.040> we<00:14:09.199> don't<00:14:09.399> know<00:14:09.839> probably<00:14:10.199> a 00:14:10.389 --> 00:14:10.399 align:start position:0% up how much up we don't know probably a 00:14:10.399 --> 00:14:12.710 align:start position:0% up how much up we don't know probably a lot<00:14:11.399> uh<00:14:11.519> and<00:14:11.680> once<00:14:12.000> that<00:14:12.199> happens<00:14:12.560> you're 00:14:12.710 --> 00:14:12.720 align:start position:0% lot uh and once that happens you're 00:14:12.720 --> 00:14:14.110 align:start position:0% lot uh and once that happens you're going<00:14:12.800> to<00:14:12.959> start<00:14:13.160> seeing<00:14:13.440> the<00:14:13.600> differences 00:14:14.110 --> 00:14:14.120 align:start position:0% going to start seeing the differences 00:14:14.120 --> 00:14:15.710 align:start position:0% going to start seeing the differences between<00:14:14.399> validity<00:14:14.759> rollups<00:14:15.160> and<00:14:15.320> optimistic 00:14:15.710 --> 00:14:15.720 align:start position:0% between validity rollups and optimistic 00:14:15.720 --> 00:14:17.790 align:start position:0% between validity rollups and optimistic rollups<00:14:16.199> because<00:14:16.839> valid<00:14:17.199> rollups<00:14:17.560> have<00:14:17.639> an 00:14:17.790 --> 00:14:17.800 align:start position:0% rollups because valid rollups have an 00:14:17.800 --> 00:14:21.030 align:start position:0% rollups because valid rollups have an advantage<00:14:18.240> the<00:14:18.320> one<00:14:18.480> that<00:14:18.600> I've<00:14:18.759> just 00:14:21.030 --> 00:14:21.040 align:start position:0% 00:14:21.040 --> 00:14:23.430 align:start position:0% described<00:14:22.040> uh<00:14:22.240> this<00:14:22.320> is<00:14:22.480> a<00:14:22.600> zoom<00:14:22.839> in<00:14:23.000> on<00:14:23.240> on 00:14:23.430 --> 00:14:23.440 align:start position:0% described uh this is a zoom in on on 00:14:23.440 --> 00:14:25.230 align:start position:0% described uh this is a zoom in on on specifically<00:14:23.839> on<00:14:23.959> the<00:14:24.120> proving<00:14:25.079> uh 00:14:25.230 --> 00:14:25.240 align:start position:0% specifically on the proving uh 00:14:25.240 --> 00:14:27.749 align:start position:0% specifically on the proving uh technology<00:14:26.240> uh<00:14:26.399> We've<00:14:26.680> recently<00:14:27.199> announced 00:14:27.749 --> 00:14:27.759 align:start position:0% technology uh We've recently announced 00:14:27.759 --> 00:14:30.470 align:start position:0% technology uh We've recently announced well<00:14:28.639> over<00:14:29.279> six<00:14:29.480> months<00:14:29.680> ago<00:14:29.920> the<00:14:30.160> our<00:14:30.279> next 00:14:30.470 --> 00:14:30.480 align:start position:0% well over six months ago the our next 00:14:30.480 --> 00:14:32.870 align:start position:0% well over six months ago the our next Generation<00:14:30.880> prover<00:14:31.240> which<00:14:31.360> is<00:14:31.480> called<00:14:31.800> St<00:14:32.759> uh 00:14:32.870 --> 00:14:32.880 align:start position:0% Generation prover which is called St uh 00:14:32.880 --> 00:14:35.269 align:start position:0% Generation prover which is called St uh it<00:14:33.040> rides<00:14:33.360> on<00:14:33.480> an<00:14:33.680> improved<00:14:34.240> start<00:14:34.720> protocol 00:14:35.269 --> 00:14:35.279 align:start position:0% it rides on an improved start protocol 00:14:35.279 --> 00:14:37.189 align:start position:0% it rides on an improved start protocol which<00:14:35.360> is<00:14:35.480> a<00:14:35.600> collaboration<00:14:36.240> between<00:14:36.880> us 00:14:37.189 --> 00:14:37.199 align:start position:0% which is a collaboration between us 00:14:37.199 --> 00:14:41.749 align:start position:0% which is a collaboration between us starware<00:14:38.040> and<00:14:38.480> uh<00:14:38.720> uh<00:14:38.880> polygon<00:14:39.680> zero<00:14:40.680> and<00:14:41.160> uh 00:14:41.749 --> 00:14:41.759 align:start position:0% starware and uh uh polygon zero and uh 00:14:41.759 --> 00:14:43.790 align:start position:0% starware and uh uh polygon zero and uh it<00:14:42.000> enables<00:14:42.399> the<00:14:42.519> pro<00:14:42.800> to<00:14:42.920> be<00:14:43.040> a<00:14:43.160> lot<00:14:43.360> less<00:14:43.720> a 00:14:43.790 --> 00:14:43.800 align:start position:0% it enables the pro to be a lot less a 00:14:43.800 --> 00:14:45.749 align:start position:0% it enables the pro to be a lot less a lot<00:14:43.959> more<00:14:44.279> efficient<00:14:45.279> how<00:14:45.440> much<00:14:45.560> more 00:14:45.749 --> 00:14:45.759 align:start position:0% lot more efficient how much more 00:14:45.759 --> 00:14:47.030 align:start position:0% lot more efficient how much more efficient<00:14:46.160> two<00:14:46.320> to<00:14:46.480> three<00:14:46.639> orders<00:14:46.920> of 00:14:47.030 --> 00:14:47.040 align:start position:0% efficient two to three orders of 00:14:47.040 --> 00:14:48.389 align:start position:0% efficient two to three orders of magnitude<00:14:47.480> more<00:14:47.639> efficient<00:14:47.959> so<00:14:48.079> what<00:14:48.199> you<00:14:48.279> see 00:14:48.389 --> 00:14:48.399 align:start position:0% magnitude more efficient so what you see 00:14:48.399 --> 00:14:49.870 align:start position:0% magnitude more efficient so what you see here<00:14:48.600> stone<00:14:48.880> is<00:14:49.000> our<00:14:49.160> current<00:14:49.399> Pro<00:14:49.759> that's 00:14:49.870 --> 00:14:49.880 align:start position:0% here stone is our current Pro that's 00:14:49.880 --> 00:14:51.230 align:start position:0% here stone is our current Pro that's what's<00:14:50.040> running<00:14:50.360> in<00:14:50.560> in<00:14:50.680> Stark<00:14:51.040> net 00:14:51.230 --> 00:14:51.240 align:start position:0% what's running in in Stark net 00:14:51.240 --> 00:14:53.150 align:start position:0% what's running in in Stark net production<00:14:51.639> today<00:14:52.199> so<00:14:52.360> the<00:14:52.480> numbers<00:14:52.759> I<00:14:52.880> showed 00:14:53.150 --> 00:14:53.160 align:start position:0% production today so the numbers I showed 00:14:53.160 --> 00:14:55.870 align:start position:0% production today so the numbers I showed you<00:14:53.320> before<00:14:53.800> our<00:14:54.040> running<00:14:54.399> Stone<00:14:55.240> Su<00:14:55.680> who's 00:14:55.870 --> 00:14:55.880 align:start position:0% you before our running Stone Su who's 00:14:55.880 --> 00:14:57.670 align:start position:0% you before our running Stone Su who's coming<00:14:56.120> out<00:14:56.279> in<00:14:56.440> q1<00:14:56.800> next<00:14:57.000> year<00:14:57.199> is<00:14:57.320> going<00:14:57.399> to 00:14:57.670 --> 00:14:57.680 align:start position:0% coming out in q1 next year is going to 00:14:57.680 --> 00:15:02.430 align:start position:0% coming out in q1 next year is going to be<00:14:58.680> 100<00:14:59.040> to<00:14:59.199> 1,000x<00:15:00.279> more<00:15:01.279> uh<00:15:01.639> efficient<00:15:02.079> than 00:15:02.430 --> 00:15:02.440 align:start position:0% be 100 to 1,000x more uh efficient than 00:15:02.440 --> 00:15:05.350 align:start position:0% be 100 to 1,000x more uh efficient than Stone<00:15:03.440> what<00:15:03.639> that<00:15:03.880> does<00:15:04.560> first<00:15:04.800> it<00:15:04.959> reduces 00:15:05.350 --> 00:15:05.360 align:start position:0% Stone what that does first it reduces 00:15:05.360 --> 00:15:07.030 align:start position:0% Stone what that does first it reduces proven<00:15:05.720> cost<00:15:06.000> like<00:15:06.120> I<00:15:06.199> said<00:15:06.320> proven<00:15:06.639> cost<00:15:06.839> is 00:15:07.030 --> 00:15:07.040 align:start position:0% proven cost like I said proven cost is 00:15:07.040 --> 00:15:09.550 align:start position:0% proven cost like I said proven cost is important<00:15:07.320> for<00:15:07.480> validity<00:15:08.160> rollups<00:15:09.160> uh<00:15:09.240> but<00:15:09.399> on 00:15:09.550 --> 00:15:09.560 align:start position:0% important for validity rollups uh but on 00:15:09.560 --> 00:15:11.150 align:start position:0% important for validity rollups uh but on top<00:15:09.720> of<00:15:09.839> that<00:15:09.959> it<00:15:10.040> opens<00:15:10.360> new<00:15:10.600> possibilities 00:15:11.150 --> 00:15:11.160 align:start position:0% top of that it opens new possibilities 00:15:11.160 --> 00:15:12.710 align:start position:0% top of that it opens new possibilities such<00:15:11.320> as<00:15:11.440> client<00:15:11.880> side<00:15:12.040> proving<00:15:12.360> maybe<00:15:12.600> I'll 00:15:12.710 --> 00:15:12.720 align:start position:0% such as client side proving maybe I'll 00:15:12.720 --> 00:15:15.269 align:start position:0% such as client side proving maybe I'll touch<00:15:13.000> that<00:15:13.160> in<00:15:13.240> a<00:15:13.560> second<00:15:14.560> another<00:15:14.880> thing 00:15:15.269 --> 00:15:15.279 align:start position:0% touch that in a second another thing 00:15:15.279 --> 00:15:16.710 align:start position:0% touch that in a second another thing that 00:15:16.710 --> 00:15:16.720 align:start position:0% that 00:15:16.720 --> 00:15:19.389 align:start position:0% that uh<00:15:17.720> you<00:15:17.880> could<00:15:18.240> sometimes<00:15:18.480> do<00:15:18.680> with<00:15:19.000> the<00:15:19.240> with 00:15:19.389 --> 00:15:19.399 align:start position:0% uh you could sometimes do with the with 00:15:19.399 --> 00:15:21.069 align:start position:0% uh you could sometimes do with the with Layer<00:15:19.639> Two<00:15:19.800> so<00:15:19.920> ethereum<00:15:20.320> and<00:15:20.399> evm<00:15:20.800> have<00:15:20.959> their 00:15:21.069 --> 00:15:21.079 align:start position:0% Layer Two so ethereum and evm have their 00:15:21.079 --> 00:15:23.389 align:start position:0% Layer Two so ethereum and evm have their own<00:15:21.240> set<00:15:21.440> of<00:15:21.600> limitations<00:15:22.600> some<00:15:22.800> of<00:15:23.000> which<00:15:23.240> no 00:15:23.389 --> 00:15:23.399 align:start position:0% own set of limitations some of which no 00:15:23.399 --> 00:15:25.110 align:start position:0% own set of limitations some of which no longer<00:15:23.680> have<00:15:23.839> to<00:15:24.120> exist<00:15:24.440> when<00:15:24.600> you<00:15:24.680> move<00:15:24.959> to 00:15:25.110 --> 00:15:25.120 align:start position:0% longer have to exist when you move to 00:15:25.120 --> 00:15:27.629 align:start position:0% longer have to exist when you move to proofs<00:15:25.519> and<00:15:25.680> and<00:15:25.759> to<00:15:25.880> layer<00:15:26.279> tws<00:15:27.279> uh<00:15:27.360> so<00:15:27.560> these 00:15:27.629 --> 00:15:27.639 align:start position:0% proofs and and to layer tws uh so these 00:15:27.639 --> 00:15:29.110 align:start position:0% proofs and and to layer tws uh so these are<00:15:27.800> some<00:15:28.040> examples<00:15:28.399> from<00:15:28.519> Stark<00:15:29.000> for 00:15:29.110 --> 00:15:29.120 align:start position:0% are some examples from Stark for 00:15:29.120 --> 00:15:30.470 align:start position:0% are some examples from Stark for instance<00:15:29.319> dark<00:15:29.639> you<00:15:29.720> have<00:15:29.839> native<00:15:30.160> account 00:15:30.470 --> 00:15:30.480 align:start position:0% instance dark you have native account 00:15:30.480 --> 00:15:32.910 align:start position:0% instance dark you have native account abstraction<00:15:31.120> so<00:15:31.279> all<00:15:31.560> accounts<00:15:32.279> are<00:15:32.560> smart 00:15:32.910 --> 00:15:32.920 align:start position:0% abstraction so all accounts are smart 00:15:32.920 --> 00:15:35.870 align:start position:0% abstraction so all accounts are smart contracts<00:15:33.720> this<00:15:34.279> allows<00:15:34.759> very<00:15:35.279> uh<00:15:35.680> great 00:15:35.870 --> 00:15:35.880 align:start position:0% contracts this allows very uh great 00:15:35.880 --> 00:15:37.350 align:start position:0% contracts this allows very uh great flexibility<00:15:36.519> I'll<00:15:36.639> show<00:15:36.800> you<00:15:36.959> in<00:15:37.040> a<00:15:37.120> second 00:15:37.350 --> 00:15:37.360 align:start position:0% flexibility I'll show you in a second 00:15:37.360 --> 00:15:38.749 align:start position:0% flexibility I'll show you in a second some<00:15:37.480> of<00:15:37.600> the<00:15:37.680> things<00:15:37.920> people<00:15:38.120> do<00:15:38.319> with<00:15:38.440> it 00:15:38.749 --> 00:15:38.759 align:start position:0% some of the things people do with it 00:15:38.759 --> 00:15:40.829 align:start position:0% some of the things people do with it today<00:15:39.759> uh<00:15:39.880> for<00:15:40.040> instance<00:15:40.319> it<00:15:40.399> allows<00:15:40.639> you<00:15:40.720> to 00:15:40.829 --> 00:15:40.839 align:start position:0% today uh for instance it allows you to 00:15:40.839 --> 00:15:42.470 align:start position:0% today uh for instance it allows you to use<00:15:41.000> different<00:15:41.360> cryptography<00:15:42.040> for<00:15:42.279> for 00:15:42.470 --> 00:15:42.480 align:start position:0% use different cryptography for for 00:15:42.480 --> 00:15:44.710 align:start position:0% use different cryptography for for signing<00:15:42.880> for<00:15:43.040> user<00:15:43.639> signing 00:15:44.710 --> 00:15:44.720 align:start position:0% signing for user signing 00:15:44.720 --> 00:15:46.670 align:start position:0% signing for user signing transaction<00:15:45.720> other<00:15:45.959> things<00:15:46.160> that<00:15:46.360> you<00:15:46.480> could 00:15:46.670 --> 00:15:46.680 align:start position:0% transaction other things that you could 00:15:46.680 --> 00:15:48.470 align:start position:0% transaction other things that you could you<00:15:46.800> could<00:15:46.959> provide<00:15:47.279> some<00:15:47.519> some<00:15:47.680> more<00:15:47.959> privacy 00:15:48.470 --> 00:15:48.480 align:start position:0% you could provide some some more privacy 00:15:48.480 --> 00:15:51.870 align:start position:0% you could provide some some more privacy than<00:15:48.880> uh<00:15:49.240> using<00:15:49.880> proofs<00:15:50.880> you<00:15:51.000> have<00:15:51.399> a<00:15:51.560> wider 00:15:51.870 --> 00:15:51.880 align:start position:0% than uh using proofs you have a wider 00:15:51.880 --> 00:15:54.110 align:start position:0% than uh using proofs you have a wider variety<00:15:52.279> of<00:15:52.399> data<00:15:52.639> availability<00:15:53.399> options 00:15:54.110 --> 00:15:54.120 align:start position:0% variety of data availability options 00:15:54.120 --> 00:15:56.069 align:start position:0% variety of data availability options specifically<00:15:54.560> our<00:15:54.800> language<00:15:55.160> is<00:15:55.319> rlike<00:15:55.800> so 00:15:56.069 --> 00:15:56.079 align:start position:0% specifically our language is rlike so 00:15:56.079 --> 00:15:59.230 align:start position:0% specifically our language is rlike so it's<00:15:56.480> easier<00:15:56.800> to<00:15:56.959> develop<00:15:57.639> in<00:15:58.639> so<00:15:59.000> these<00:15:59.079> are 00:15:59.230 --> 00:15:59.240 align:start position:0% it's easier to develop in so these are 00:15:59.240 --> 00:16:00.389 align:start position:0% it's easier to develop in so these are some<00:15:59.399> some<00:15:59.519> of<00:15:59.639> the<00:15:59.720> things<00:15:59.880> that<00:16:00.000> used<00:16:00.240> dat 00:16:00.389 --> 00:16:00.399 align:start position:0% some some of the things that used dat 00:16:00.399 --> 00:16:02.189 align:start position:0% some some of the things that used dat and<00:16:00.519> are<00:16:00.759> alive<00:16:01.040> on<00:16:01.240> on<00:16:01.360> Stark<00:16:01.680> net<00:16:01.839> today<00:16:02.040> so 00:16:02.189 --> 00:16:02.199 align:start position:0% and are alive on on Stark net today so 00:16:02.199 --> 00:16:03.629 align:start position:0% and are alive on on Stark net today so Argent<00:16:02.600> that's<00:16:02.759> one<00:16:02.839> of<00:16:02.959> the<00:16:03.040> leading<00:16:03.319> Wallets 00:16:03.629 --> 00:16:03.639 align:start position:0% Argent that's one of the leading Wallets 00:16:03.639 --> 00:16:06.269 align:start position:0% Argent that's one of the leading Wallets on<00:16:04.040> starnet<00:16:05.040> uh<00:16:05.199> they<00:16:05.319> have<00:16:05.440> two<00:16:05.639> Factor 00:16:06.269 --> 00:16:06.279 align:start position:0% on starnet uh they have two Factor 00:16:06.279 --> 00:16:07.790 align:start position:0% on starnet uh they have two Factor authentication<00:16:07.040> you<00:16:07.120> can<00:16:07.240> have<00:16:07.360> a<00:16:07.480> gaming 00:16:07.790 --> 00:16:07.800 align:start position:0% authentication you can have a gaming 00:16:07.800 --> 00:16:09.230 align:start position:0% authentication you can have a gaming session<00:16:08.120> so<00:16:08.279> if<00:16:08.399> you<00:16:08.519> play<00:16:08.759> you<00:16:08.839> don't<00:16:09.000> have<00:16:09.120> to 00:16:09.230 --> 00:16:09.240 align:start position:0% session so if you play you don't have to 00:16:09.240 --> 00:16:11.430 align:start position:0% session so if you play you don't have to sign<00:16:09.480> anything<00:16:09.800> during<00:16:10.079> the<00:16:10.240> session<00:16:11.240> uh<00:16:11.360> you 00:16:11.430 --> 00:16:11.440 align:start position:0% sign anything during the session uh you 00:16:11.440 --> 00:16:13.150 align:start position:0% sign anything during the session uh you could<00:16:11.639> approve<00:16:11.959> in<00:16:12.120> advance<00:16:12.519> up<00:16:12.639> to<00:16:12.759> a<00:16:12.839> certain 00:16:13.150 --> 00:16:13.160 align:start position:0% could approve in advance up to a certain 00:16:13.160 --> 00:16:15.670 align:start position:0% could approve in advance up to a certain spending<00:16:13.600> limit<00:16:14.519> uh<00:16:14.639> braavos<00:16:15.199> that's<00:16:15.399> another 00:16:15.670 --> 00:16:15.680 align:start position:0% spending limit uh braavos that's another 00:16:15.680 --> 00:16:17.710 align:start position:0% spending limit uh braavos that's another major<00:16:16.000> wallet<00:16:16.399> they<00:16:16.519> have<00:16:16.680> face<00:16:16.920> ID<00:16:17.279> so<00:16:17.519> this 00:16:17.710 --> 00:16:17.720 align:start position:0% major wallet they have face ID so this 00:16:17.720 --> 00:16:19.790 align:start position:0% major wallet they have face ID so this really<00:16:17.959> gives<00:16:18.160> you<00:16:18.440> a<00:16:18.880> a<00:16:19.000> web<00:16:19.199> to<00:16:19.480> look<00:16:19.639> and 00:16:19.790 --> 00:16:19.800 align:start position:0% really gives you a a web to look and 00:16:19.800 --> 00:16:21.829 align:start position:0% really gives you a a web to look and feel<00:16:20.360> when<00:16:20.480> you're<00:16:20.600> using<00:16:20.920> it<00:16:21.319> you<00:16:21.440> could<00:16:21.680> have 00:16:21.829 --> 00:16:21.839 align:start position:0% feel when you're using it you could have 00:16:21.839 --> 00:16:23.309 align:start position:0% feel when you're using it you could have multi<00:16:22.160> owners<00:16:22.480> for<00:16:22.600> an<00:16:22.759> account<00:16:23.079> you<00:16:23.199> could 00:16:23.309 --> 00:16:23.319 align:start position:0% multi owners for an account you could 00:16:23.319 --> 00:16:26.670 align:start position:0% multi owners for an account you could have<00:16:23.480> spending<00:16:24.040> limits<00:16:25.040> iubu<00:16:25.600> is<00:16:25.920> a<00:16:26.480> one<00:16:26.600> of 00:16:26.670 --> 00:16:26.680 align:start position:0% have spending limits iubu is a one of 00:16:26.680 --> 00:16:29.389 align:start position:0% have spending limits iubu is a one of the<00:16:26.800> main<00:16:27.000> amm<00:16:27.399> on<00:16:27.560> stet<00:16:28.360> check<00:16:28.560> it<00:16:28.680> out<00:16:29.079> it<00:16:29.199> it 00:16:29.389 --> 00:16:29.399 align:start position:0% the main amm on stet check it out it it 00:16:29.399 --> 00:16:31.069 align:start position:0% the main amm on stet check it out it it provides<00:16:29.800> very<00:16:29.959> good<00:16:30.160> Capital<00:16:30.519> efficiency 00:16:31.069 --> 00:16:31.079 align:start position:0% provides very good Capital efficiency 00:16:31.079 --> 00:16:33.389 align:start position:0% provides very good Capital efficiency with<00:16:31.839> uh<00:16:31.959> the<00:16:32.120> capabilities<00:16:32.600> that<00:16:32.720> Stark 00:16:33.389 --> 00:16:33.399 align:start position:0% with uh the capabilities that Stark 00:16:33.399 --> 00:16:37.749 align:start position:0% with uh the capabilities that Stark enables<00:16:33.720> you<00:16:33.880> today<00:16:34.639> to<00:16:34.920> do<00:16:35.920> uh<00:16:36.440> Avenue<00:16:37.440> run<00:16:37.639> a 00:16:37.749 --> 00:16:37.759 align:start position:0% enables you today to do uh Avenue run a 00:16:37.759 --> 00:16:39.110 align:start position:0% enables you today to do uh Avenue run a pay<00:16:37.959> Master<00:16:38.240> pay<00:16:38.399> Master<00:16:38.600> meaning<00:16:38.839> the<00:16:38.920> user 00:16:39.110 --> 00:16:39.120 align:start position:0% pay Master pay Master meaning the user 00:16:39.120 --> 00:16:40.470 align:start position:0% pay Master pay Master meaning the user could<00:16:39.240> send<00:16:39.399> a<00:16:39.560> transaction<00:16:40.040> but<00:16:40.199> somebody 00:16:40.470 --> 00:16:40.480 align:start position:0% could send a transaction but somebody 00:16:40.480 --> 00:16:43.069 align:start position:0% could send a transaction but somebody else<00:16:40.759> pays<00:16:41.000> for<00:16:41.160> that<00:16:41.800> transaction<00:16:42.800> so<00:16:42.959> you 00:16:43.069 --> 00:16:43.079 align:start position:0% else pays for that transaction so you 00:16:43.079 --> 00:16:45.389 align:start position:0% else pays for that transaction so you could<00:16:43.240> use<00:16:43.519> that<00:16:43.920> oh 00:16:45.389 --> 00:16:45.399 align:start position:0% could use that oh 00:16:45.399 --> 00:16:47.829 align:start position:0% could use that oh sorry<00:16:46.399> so<00:16:46.600> that<00:16:46.759> could<00:16:46.880> be<00:16:47.040> used<00:16:47.279> to<00:16:47.480> provide 00:16:47.829 --> 00:16:47.839 align:start position:0% sorry so that could be used to provide 00:16:47.839 --> 00:16:49.749 align:start position:0% sorry so that could be used to provide like<00:16:48.040> you<00:16:48.160> could<00:16:48.319> go<00:16:48.480> in<00:16:48.680> we<00:16:48.839> just<00:16:48.959> did<00:16:49.160> a<00:16:49.519> a<00:16:49.600> few 00:16:49.749 --> 00:16:49.759 align:start position:0% like you could go in we just did a a few 00:16:49.759 --> 00:16:51.870 align:start position:0% like you could go in we just did a a few weeks<00:16:50.000> ago<00:16:50.279> we<00:16:50.399> did<00:16:50.639> a<00:16:50.920> a<00:16:51.079> stress<00:16:51.399> test<00:16:51.639> like<00:16:51.759> a 00:16:51.870 --> 00:16:51.880 align:start position:0% weeks ago we did a a stress test like a 00:16:51.880 --> 00:16:53.550 align:start position:0% weeks ago we did a a stress test like a real<00:16:52.079> stress<00:16:52.399> test<00:16:52.600> on<00:16:52.880> production<00:16:53.399> with 00:16:53.550 --> 00:16:53.560 align:start position:0% real stress test on production with 00:16:53.560 --> 00:16:55.150 align:start position:0% real stress test on production with users<00:16:53.920> playing<00:16:54.160> a<00:16:54.319> game<00:16:54.519> that<00:16:54.680> did<00:16:54.839> lots<00:16:55.000> of 00:16:55.150 --> 00:16:55.160 align:start position:0% users playing a game that did lots of 00:16:55.160 --> 00:16:57.150 align:start position:0% users playing a game that did lots of transactions<00:16:56.000> they<00:16:56.120> didn't<00:16:56.360> have<00:16:56.480> to<00:16:56.639> sign<00:16:56.920> in 00:16:57.150 --> 00:16:57.160 align:start position:0% transactions they didn't have to sign in 00:16:57.160 --> 00:16:59.030 align:start position:0% transactions they didn't have to sign in they<00:16:57.279> didn't<00:16:57.480> have<00:16:57.600> to<00:16:57.720> install<00:16:58.000> a<00:16:58.160> wallet<00:16:58.920> no 00:16:59.030 --> 00:16:59.040 align:start position:0% they didn't have to install a wallet no 00:16:59.040 --> 00:17:02.949 align:start position:0% they didn't have to install a wallet no seed<00:16:59.480> phrases<00:17:00.480> they<00:17:00.600> could<00:17:00.800> go<00:17:00.959> in<00:17:01.199> with<00:17:01.600> uh<00:17:02.519> uh 00:17:02.949 --> 00:17:02.959 align:start position:0% seed phrases they could go in with uh uh 00:17:02.959 --> 00:17:05.590 align:start position:0% seed phrases they could go in with uh uh fingerprints<00:17:03.600> and<00:17:03.800> just 00:17:05.590 --> 00:17:05.600 align:start position:0% fingerprints and just 00:17:05.600 --> 00:17:08.549 align:start position:0% fingerprints and just play<00:17:06.600> okay<00:17:06.799> I'm<00:17:07.079> um<00:17:07.919> other<00:17:08.160> things<00:17:08.319> you<00:17:08.439> could 00:17:08.549 --> 00:17:08.559 align:start position:0% play okay I'm um other things you could 00:17:08.559 --> 00:17:11.069 align:start position:0% play okay I'm um other things you could do<00:17:08.720> Dojo<00:17:09.120> they<00:17:09.280> provided<00:17:09.919> U<00:17:10.280> this<00:17:10.520> game<00:17:10.760> engine 00:17:11.069 --> 00:17:11.079 align:start position:0% do Dojo they provided U this game engine 00:17:11.079 --> 00:17:15.029 align:start position:0% do Dojo they provided U this game engine that<00:17:11.679> enables<00:17:12.039> you<00:17:12.120> to<00:17:12.240> run<00:17:12.439> a<00:17:12.559> lot<00:17:12.919> of<00:17:13.919> uh<00:17:14.720> game 00:17:15.029 --> 00:17:15.039 align:start position:0% that enables you to run a lot of uh game 00:17:15.039 --> 00:17:16.750 align:start position:0% that enables you to run a lot of uh game logic<00:17:15.439> on<00:17:15.679> chain<00:17:15.959> a<00:17:16.079> lot<00:17:16.240> more<00:17:16.400> than<00:17:16.520> you<00:17:16.600> could 00:17:16.750 --> 00:17:16.760 align:start position:0% logic on chain a lot more than you could 00:17:16.760 --> 00:17:19.630 align:start position:0% logic on chain a lot more than you could do<00:17:16.880> on<00:17:17.480> ethereum<00:17:18.480> uh<00:17:18.760> their<00:17:19.000> longer<00:17:19.360> term 00:17:19.630 --> 00:17:19.640 align:start position:0% do on ethereum uh their longer term 00:17:19.640 --> 00:17:21.870 align:start position:0% do on ethereum uh their longer term vision<00:17:20.000> is<00:17:20.199> to<00:17:20.600> use<00:17:21.160> what<00:17:21.240> I<00:17:21.360> mentioned<00:17:21.679> before 00:17:21.870 --> 00:17:21.880 align:start position:0% vision is to use what I mentioned before 00:17:21.880 --> 00:17:23.549 align:start position:0% vision is to use what I mentioned before when<00:17:22.000> I<00:17:22.120> talked<00:17:22.360> about<00:17:22.520> St<00:17:22.880> a<00:17:23.000> client<00:17:23.360> side 00:17:23.549 --> 00:17:23.559 align:start position:0% when I talked about St a client side 00:17:23.559 --> 00:17:25.710 align:start position:0% when I talked about St a client side proving<00:17:24.559> which<00:17:24.839> basically<00:17:25.199> says<00:17:25.480> that<00:17:25.600> you 00:17:25.710 --> 00:17:25.720 align:start position:0% proving which basically says that you 00:17:25.720 --> 00:17:27.669 align:start position:0% proving which basically says that you could<00:17:25.919> run<00:17:26.280> most<00:17:26.839> of<00:17:26.959> the<00:17:27.079> game<00:17:27.319> logic 00:17:27.669 --> 00:17:27.679 align:start position:0% could run most of the game logic 00:17:27.679 --> 00:17:30.029 align:start position:0% could run most of the game logic offchain<00:17:28.120> on<00:17:28.240> the<00:17:28.360> client<00:17:28.600> Des<00:17:29.160> device 00:17:30.029 --> 00:17:30.039 align:start position:0% offchain on the client Des device 00:17:30.039 --> 00:17:31.909 align:start position:0% offchain on the client Des device generate<00:17:30.440> a<00:17:30.600> proof<00:17:30.840> and<00:17:31.000> submit<00:17:31.440> that<00:17:31.640> to<00:17:31.799> the 00:17:31.909 --> 00:17:31.919 align:start position:0% generate a proof and submit that to the 00:17:31.919 --> 00:17:34.390 align:start position:0% generate a proof and submit that to the chain<00:17:32.240> just<00:17:32.400> to<00:17:32.520> be<00:17:32.720> verified<00:17:33.600> so<00:17:33.840> this<00:17:33.960> is<00:17:34.240> a 00:17:34.390 --> 00:17:34.400 align:start position:0% chain just to be verified so this is a 00:17:34.400 --> 00:17:37.669 align:start position:0% chain just to be verified so this is a real<00:17:34.880> GameChanger<00:17:35.799> sorry<00:17:36.120> the<00:17:36.440> pun<00:17:37.440> uh<00:17:37.559> you 00:17:37.669 --> 00:17:37.679 align:start position:0% real GameChanger sorry the pun uh you 00:17:37.679 --> 00:17:39.070 align:start position:0% real GameChanger sorry the pun uh you don't<00:17:37.840> have<00:17:37.960> to<00:17:38.080> run<00:17:38.320> all<00:17:38.480> the<00:17:38.600> game<00:17:38.799> logic 00:17:39.070 --> 00:17:39.080 align:start position:0% don't have to run all the game logic 00:17:39.080 --> 00:17:40.990 align:start position:0% don't have to run all the game logic onchain<00:17:39.480> to<00:17:39.600> be<00:17:39.679> able<00:17:39.880> to<00:17:40.000> trust 00:17:40.990 --> 00:17:41.000 align:start position:0% onchain to be able to trust 00:17:41.000 --> 00:17:43.950 align:start position:0% onchain to be able to trust it<00:17:42.000> uh<00:17:42.160> Giza<00:17:42.919> have<00:17:43.039> a<00:17:43.200> similar<00:17:43.840> uh 00:17:43.950 --> 00:17:43.960 align:start position:0% it uh Giza have a similar uh 00:17:43.960 --> 00:17:46.430 align:start position:0% it uh Giza have a similar uh infrastructure<00:17:44.520> for<00:17:44.679> machine<00:17:45.000> learning<00:17:45.760> same 00:17:46.430 --> 00:17:46.440 align:start position:0% infrastructure for machine learning same 00:17:46.440 --> 00:17:48.150 align:start position:0% infrastructure for machine learning same it's<00:17:46.600> the<00:17:46.760> same<00:17:47.039> IDE<00:17:47.400> similar<00:17:47.720> idea<00:17:47.960> you<00:17:48.039> could 00:17:48.150 --> 00:17:48.160 align:start position:0% it's the same IDE similar idea you could 00:17:48.160 --> 00:17:49.590 align:start position:0% it's the same IDE similar idea you could run<00:17:48.320> a<00:17:48.400> bunch<00:17:48.600> of<00:17:48.679> thing<00:17:48.880> offchain<00:17:49.320> but<00:17:49.440> then 00:17:49.590 --> 00:17:49.600 align:start position:0% run a bunch of thing offchain but then 00:17:49.600 --> 00:17:52.630 align:start position:0% run a bunch of thing offchain but then just<00:17:50.240> verify<00:17:50.679> onchain<00:17:51.160> that<00:17:51.240> you've<00:17:51.400> run<00:17:51.640> them 00:17:52.630 --> 00:17:52.640 align:start position:0% just verify onchain that you've run them 00:17:52.640 --> 00:17:55.350 align:start position:0% just verify onchain that you've run them correctly<00:17:53.640> and<00:17:53.799> this<00:17:53.960> year<00:17:54.320> if<00:17:54.400> you<00:17:54.559> like<00:17:55.039> uh 00:17:55.350 --> 00:17:55.360 align:start position:0% correctly and this year if you like uh 00:17:55.360 --> 00:17:57.830 align:start position:0% correctly and this year if you like uh mmps<00:17:56.120> try<00:17:56.440> this<00:17:56.559> one<00:17:56.760> out<00:17:57.080> it's<00:17:57.320> it's<00:17:57.559> pretty 00:17:57.830 --> 00:17:57.840 align:start position:0% mmps try this one out it's it's pretty 00:17:57.840 --> 00:18:00.510 align:start position:0% mmps try this one out it's it's pretty amazing<00:17:59.120> uh<00:17:59.400> so<00:17:59.640> these<00:17:59.760> are<00:17:59.919> the<00:18:00.039> hardware 00:18:00.510 --> 00:18:00.520 align:start position:0% amazing uh so these are the hardware 00:18:00.520 --> 00:18:02.029 align:start position:0% amazing uh so these are the hardware aspects<00:18:00.840> related<00:18:01.159> to<00:18:01.320> infrastructure<00:18:01.880> or 00:18:02.029 --> 00:18:02.039 align:start position:0% aspects related to infrastructure or 00:18:02.039 --> 00:18:04.950 align:start position:0% aspects related to infrastructure or technology<00:18:03.039> uh<00:18:03.280> what's<00:18:03.880> also<00:18:04.240> important<00:18:04.640> is<00:18:04.799> a 00:18:04.950 --> 00:18:04.960 align:start position:0% technology uh what's also important is a 00:18:04.960 --> 00:18:07.990 align:start position:0% technology uh what's also important is a bunch<00:18:05.360> of<00:18:06.360> software<00:18:07.039> aspects<00:18:07.440> related<00:18:07.799> to 00:18:07.990 --> 00:18:08.000 align:start position:0% bunch of software aspects related to 00:18:08.000 --> 00:18:09.669 align:start position:0% bunch of software aspects related to community<00:18:08.559> to<00:18:08.720> the<00:18:08.880> people<00:18:09.159> and<00:18:09.320> to<00:18:09.480> the 00:18:09.669 --> 00:18:09.679 align:start position:0% community to the people and to the 00:18:09.679 --> 00:18:11.510 align:start position:0% community to the people and to the values<00:18:10.080> of<00:18:10.320> that<00:18:10.520> community<00:18:11.159> so<00:18:11.320> when<00:18:11.400> you 00:18:11.510 --> 00:18:11.520 align:start position:0% values of that community so when you 00:18:11.520 --> 00:18:12.830 align:start position:0% values of that community so when you choose<00:18:11.760> a<00:18:11.919> chain<00:18:12.240> I<00:18:12.320> think<00:18:12.480> it's<00:18:12.640> also 00:18:12.830 --> 00:18:12.840 align:start position:0% choose a chain I think it's also 00:18:12.840 --> 00:18:14.070 align:start position:0% choose a chain I think it's also important<00:18:13.159> to<00:18:13.280> look<00:18:13.520> like<00:18:13.679> who<00:18:13.799> are<00:18:13.919> the 00:18:14.070 --> 00:18:14.080 align:start position:0% important to look like who are the 00:18:14.080 --> 00:18:16.710 align:start position:0% important to look like who are the people<00:18:14.400> there<00:18:15.000> what's<00:18:15.240> the<00:18:15.360> community<00:18:15.840> like 00:18:16.710 --> 00:18:16.720 align:start position:0% people there what's the community like 00:18:16.720 --> 00:18:18.990 align:start position:0% people there what's the community like uh<00:18:16.880> what's<00:18:17.120> the<00:18:17.280> vision<00:18:18.080> what<00:18:18.200> are<00:18:18.320> the<00:18:18.520> values 00:18:18.990 --> 00:18:19.000 align:start position:0% uh what's the vision what are the values 00:18:19.000 --> 00:18:20.549 align:start position:0% uh what's the vision what are the values what<00:18:19.159> energy<00:18:19.520> do<00:18:19.640> you<00:18:19.720> feel<00:18:19.960> from<00:18:20.159> the<00:18:20.280> team 00:18:20.549 --> 00:18:20.559 align:start position:0% what energy do you feel from the team 00:18:20.559 --> 00:18:22.230 align:start position:0% what energy do you feel from the team there<00:18:20.679> are<00:18:21.080> very<00:18:21.280> big<00:18:21.480> differences<00:18:21.960> between 00:18:22.230 --> 00:18:22.240 align:start position:0% there are very big differences between 00:18:22.240 --> 00:18:26.190 align:start position:0% there are very big differences between the<00:18:22.480> different<00:18:23.480> uh<00:18:24.320> chains<00:18:24.799> in<00:18:25.039> that 00:18:26.190 --> 00:18:26.200 align:start position:0% the different uh chains in that 00:18:26.200 --> 00:18:28.350 align:start position:0% the different uh chains in that aspect<00:18:27.200> uh<00:18:27.360> so<00:18:27.559> for<00:18:27.720> instance<00:18:28.000> look<00:18:28.159> at<00:18:28.240> the 00:18:28.350 --> 00:18:28.360 align:start position:0% aspect uh so for instance look at the 00:18:28.360 --> 00:18:29.950 align:start position:0% aspect uh so for instance look at the team<00:18:28.520> behind<00:18:28.760> behind<00:18:29.000> it<00:18:29.200> this<00:18:29.440> specifically 00:18:29.950 --> 00:18:29.960 align:start position:0% team behind behind it this specifically 00:18:29.960 --> 00:18:33.190 align:start position:0% team behind behind it this specifically is<00:18:30.120> our<00:18:30.600> starkware<00:18:31.600> uh<00:18:31.720> track<00:18:32.000> record<00:18:32.720> uh<00:18:33.000> with 00:18:33.190 --> 00:18:33.200 align:start position:0% is our starkware uh track record uh with 00:18:33.200 --> 00:18:34.350 align:start position:0% is our starkware uh track record uh with lots<00:18:33.400> of<00:18:33.520> innovation<00:18:33.960> I<00:18:34.039> think<00:18:34.159> we're<00:18:34.280> the 00:18:34.350 --> 00:18:34.360 align:start position:0% lots of innovation I think we're the 00:18:34.360 --> 00:18:37.950 align:start position:0% lots of innovation I think we're the first<00:18:34.559> ones<00:18:34.720> who<00:18:35.039> put<00:18:36.039> uh<00:18:37.000> who<00:18:37.120> who<00:18:37.320> productize 00:18:37.950 --> 00:18:37.960 align:start position:0% first ones who put uh who who productize 00:18:37.960 --> 00:18:39.710 align:start position:0% first ones who put uh who who productize provs<00:18:38.760> uh<00:18:38.880> we're<00:18:39.080> the<00:18:39.159> first<00:18:39.320> one<00:18:39.480> who<00:18:39.600> put 00:18:39.710 --> 00:18:39.720 align:start position:0% provs uh we're the first one who put 00:18:39.720 --> 00:18:41.390 align:start position:0% provs uh we're the first one who put Layer<00:18:39.919> Two<00:18:40.120> rollups<00:18:40.559> in 00:18:41.390 --> 00:18:41.400 align:start position:0% Layer Two rollups in 00:18:41.400 --> 00:18:44.190 align:start position:0% Layer Two rollups in production<00:18:42.400> uh<00:18:42.960> Circle<00:18:43.320> star<00:18:43.720> I<00:18:43.799> mentioned 00:18:44.190 --> 00:18:44.200 align:start position:0% production uh Circle star I mentioned 00:18:44.200 --> 00:18:46.230 align:start position:0% production uh Circle star I mentioned before<00:18:44.880> these<00:18:45.039> things<00:18:45.280> typically<00:18:45.720> continue 00:18:46.230 --> 00:18:46.240 align:start position:0% before these things typically continue 00:18:46.240 --> 00:18:47.430 align:start position:0% before these things typically continue if<00:18:46.320> you<00:18:46.440> have<00:18:46.520> a<00:18:46.640> team<00:18:46.840> that's<00:18:47.000> Innovative 00:18:47.430 --> 00:18:47.440 align:start position:0% if you have a team that's Innovative 00:18:47.440 --> 00:18:48.950 align:start position:0% if you have a team that's Innovative they're<00:18:47.559> going<00:18:47.640> to<00:18:47.799> continue<00:18:48.120> to<00:18:48.280> innovate 00:18:48.950 --> 00:18:48.960 align:start position:0% they're going to continue to innovate 00:18:48.960 --> 00:18:50.510 align:start position:0% they're going to continue to innovate and<00:18:49.120> Innovation<00:18:49.559> on<00:18:49.720> the<00:18:49.880> infrastructure 00:18:50.510 --> 00:18:50.520 align:start position:0% and Innovation on the infrastructure 00:18:50.520 --> 00:18:52.029 align:start position:0% and Innovation on the infrastructure level<00:18:50.799> also<00:18:51.039> affects<00:18:51.360> Innovation<00:18:51.760> on<00:18:51.919> the 00:18:52.029 --> 00:18:52.039 align:start position:0% level also affects Innovation on the 00:18:52.039 --> 00:18:54.510 align:start position:0% level also affects Innovation on the application<00:18:52.520> Level<00:18:52.799> as<00:18:52.919> I<00:18:53.039> showed<00:18:53.240> you 00:18:54.510 --> 00:18:54.520 align:start position:0% application Level as I showed you 00:18:54.520 --> 00:18:56.710 align:start position:0% application Level as I showed you before<00:18:55.520> um<00:18:55.640> in<00:18:55.760> terms<00:18:55.960> of<00:18:56.120> vision<00:18:56.440> again<00:18:56.640> this 00:18:56.710 --> 00:18:56.720 align:start position:0% before um in terms of vision again this 00:18:56.720 --> 00:18:58.350 align:start position:0% before um in terms of vision again this is<00:18:56.840> starware<00:18:57.440> Vision<00:18:57.679> we<00:18:57.760> want<00:18:57.880> to<00:18:57.960> fuel<00:18:58.240> the 00:18:58.350 --> 00:18:58.360 align:start position:0% is starware Vision we want to fuel the 00:18:58.360 --> 00:19:00.510 align:start position:0% is starware Vision we want to fuel the integrity<00:18:59.080> web<00:18:59.360> what's<00:18:59.520> the<00:18:59.679> Integrity<00:19:00.240> web 00:19:00.510 --> 00:19:00.520 align:start position:0% integrity web what's the Integrity web 00:19:00.520 --> 00:19:02.070 align:start position:0% integrity web what's the Integrity web so<00:19:00.760> blockchains<00:19:01.280> often<00:19:01.520> we<00:19:01.640> talk<00:19:01.840> about 00:19:02.070 --> 00:19:02.080 align:start position:0% so blockchains often we talk about 00:19:02.080 --> 00:19:03.350 align:start position:0% so blockchains often we talk about technical<00:19:02.600> stuff<00:19:02.880> we<00:19:03.000> talk<00:19:03.159> about 00:19:03.350 --> 00:19:03.360 align:start position:0% technical stuff we talk about 00:19:03.360 --> 00:19:05.789 align:start position:0% technical stuff we talk about cryptography<00:19:04.080> computers<00:19:05.080> all<00:19:05.280> these<00:19:05.520> nice 00:19:05.789 --> 00:19:05.799 align:start position:0% cryptography computers all these nice 00:19:05.799 --> 00:19:07.909 align:start position:0% cryptography computers all these nice little<00:19:06.039> things<00:19:06.640> uh<00:19:07.039> I<00:19:07.120> want<00:19:07.240> to<00:19:07.400> claim<00:19:07.640> that 00:19:07.909 --> 00:19:07.919 align:start position:0% little things uh I want to claim that 00:19:07.919 --> 00:19:10.990 align:start position:0% little things uh I want to claim that blockchains<00:19:08.400> are<00:19:09.080> primarily<00:19:09.600> not<00:19:09.840> about<00:19:10.240> that 00:19:10.990 --> 00:19:11.000 align:start position:0% blockchains are primarily not about that 00:19:11.000 --> 00:19:13.310 align:start position:0% blockchains are primarily not about that but<00:19:11.159> they're<00:19:11.400> actually<00:19:11.760> much<00:19:11.960> more<00:19:12.320> about 00:19:13.310 --> 00:19:13.320 align:start position:0% but they're actually much more about 00:19:13.320 --> 00:19:16.390 align:start position:0% but they're actually much more about these<00:19:13.600> things<00:19:14.280> about<00:19:14.600> Community<00:19:15.360> about<00:19:16.159> about 00:19:16.390 --> 00:19:16.400 align:start position:0% these things about Community about about 00:19:16.400 --> 00:19:18.390 align:start position:0% these things about Community about about Freedom<00:19:16.880> about<00:19:17.120> human<00:19:17.440> rights<00:19:17.760> about<00:19:18.000> social 00:19:18.390 --> 00:19:18.400 align:start position:0% Freedom about human rights about social 00:19:18.400 --> 00:19:20.710 align:start position:0% Freedom about human rights about social functions<00:19:18.799> that<00:19:18.919> they<00:19:19.039> enable<00:19:19.440> people<00:19:19.640> to 00:19:20.710 --> 00:19:20.720 align:start position:0% functions that they enable people to 00:19:20.720 --> 00:19:23.110 align:start position:0% functions that they enable people to do<00:19:21.720> so<00:19:21.919> we<00:19:22.000> want<00:19:22.120> to<00:19:22.280> focus<00:19:22.679> technology 00:19:23.110 --> 00:19:23.120 align:start position:0% do so we want to focus technology 00:19:23.120 --> 00:19:24.870 align:start position:0% do so we want to focus technology enables<00:19:23.600> that<00:19:23.799> but<00:19:23.919> we<00:19:24.039> focus<00:19:24.400> a<00:19:24.520> lot<00:19:24.679> more 00:19:24.870 --> 00:19:24.880 align:start position:0% enables that but we focus a lot more 00:19:24.880 --> 00:19:27.270 align:start position:0% enables that but we focus a lot more about<00:19:25.480> making<00:19:25.720> sure<00:19:26.000> that<00:19:26.240> these<00:19:26.520> things<00:19:27.159> uh 00:19:27.270 --> 00:19:27.280 align:start position:0% about making sure that these things uh 00:19:27.280 --> 00:19:29.830 align:start position:0% about making sure that these things uh are<00:19:28.120> embodied<00:19:28.559> in<00:19:28.720> in<00:19:28.840> whatever<00:19:29.159> we 00:19:29.830 --> 00:19:29.840 align:start position:0% are embodied in in whatever we 00:19:29.840 --> 00:19:32.430 align:start position:0% are embodied in in whatever we do<00:19:30.840> uh<00:19:31.200> another<00:19:31.520> main<00:19:31.760> thing<00:19:31.960> we're<00:19:32.159> working 00:19:32.430 --> 00:19:32.440 align:start position:0% do uh another main thing we're working 00:19:32.440 --> 00:19:35.230 align:start position:0% do uh another main thing we're working on<00:19:32.760> right<00:19:32.919> now<00:19:33.600> uh<00:19:34.080> is<00:19:34.320> actually<00:19:34.600> making<00:19:34.880> Stark 00:19:35.230 --> 00:19:35.240 align:start position:0% on right now uh is actually making Stark 00:19:35.240 --> 00:19:37.190 align:start position:0% on right now uh is actually making Stark net<00:19:35.440> air<00:19:35.720> to<00:19:35.960> on<00:19:36.120> top<00:19:36.280> of<00:19:36.400> not<00:19:36.679> just<00:19:36.799> ethereum 00:19:37.190 --> 00:19:37.200 align:start position:0% net air to on top of not just ethereum 00:19:37.200 --> 00:19:39.470 align:start position:0% net air to on top of not just ethereum but<00:19:37.360> also<00:19:37.720> Bitcoin<00:19:38.720> which<00:19:38.840> is<00:19:39.000> something<00:19:39.320> that 00:19:39.470 --> 00:19:39.480 align:start position:0% but also Bitcoin which is something that 00:19:39.480 --> 00:19:41.149 align:start position:0% but also Bitcoin which is something that until<00:19:39.720> recently<00:19:40.159> we<00:19:40.320> thought<00:19:40.520> was<00:19:40.679> not 00:19:41.149 --> 00:19:41.159 align:start position:0% until recently we thought was not 00:19:41.159 --> 00:19:43.830 align:start position:0% until recently we thought was not possible<00:19:41.600> either<00:19:41.960> but<00:19:42.880> uh<00:19:43.039> with<00:19:43.240> some<00:19:43.640> uh 00:19:43.830 --> 00:19:43.840 align:start position:0% possible either but uh with some uh 00:19:43.840 --> 00:19:46.110 align:start position:0% possible either but uh with some uh major<00:19:44.159> advances<00:19:44.679> in<00:19:44.840> research<00:19:45.320> there<00:19:45.480> it 00:19:46.110 --> 00:19:46.120 align:start position:0% major advances in research there it 00:19:46.120 --> 00:19:49.070 align:start position:0% major advances in research there it seems<00:19:46.440> that<00:19:46.720> once<00:19:47.000> opcat<00:19:47.480> is<00:19:47.919> enabled<00:19:48.919> this 00:19:49.070 --> 00:19:49.080 align:start position:0% seems that once opcat is enabled this 00:19:49.080 --> 00:19:51.470 align:start position:0% seems that once opcat is enabled this will<00:19:49.320> be<00:19:49.559> possible<00:19:50.080> and<00:19:50.840> this<00:19:50.919> is<00:19:51.159> an<00:19:51.360> an 00:19:51.470 --> 00:19:51.480 align:start position:0% will be possible and this is an an 00:19:51.480 --> 00:19:53.390 align:start position:0% will be possible and this is an an article<00:19:51.799> that<00:19:51.960> came<00:19:52.120> out<00:19:52.320> last<00:19:52.919> last<00:19:53.120> week<00:19:53.280> or 00:19:53.390 --> 00:19:53.400 align:start position:0% article that came out last last week or 00:19:53.400 --> 00:19:54.909 align:start position:0% article that came out last last week or maybe<00:19:53.600> even<00:19:53.840> this<00:19:53.960> week<00:19:54.200> that<00:19:54.520> actually<00:19:54.679> shows 00:19:54.909 --> 00:19:54.919 align:start position:0% maybe even this week that actually shows 00:19:54.919 --> 00:19:56.630 align:start position:0% maybe even this week that actually shows that<00:19:55.039> you<00:19:55.120> could<00:19:55.360> even<00:19:55.520> do<00:19:55.640> it<00:19:55.799> without<00:19:56.080> opcat 00:19:56.630 --> 00:19:56.640 align:start position:0% that you could even do it without opcat 00:19:56.640 --> 00:19:57.549 align:start position:0% that you could even do it without opcat it's<00:19:56.760> just<00:19:56.880> going<00:19:56.960> to<00:19:57.039> be<00:19:57.159> a<00:19:57.240> lot<00:19:57.360> more 00:19:57.549 --> 00:19:57.559 align:start position:0% it's just going to be a lot more 00:19:57.559 --> 00:19:59.590 align:start position:0% it's just going to be a lot more expensive 00:19:59.590 --> 00:19:59.600 align:start position:0% expensive 00:19:59.600 --> 00:20:01.669 align:start position:0% expensive uh<00:20:00.039> these<00:20:00.400> for<00:20:00.640> example<00:20:01.240> these<00:20:01.360> are<00:20:01.520> actually 00:20:01.669 --> 00:20:01.679 align:start position:0% uh these for example these are actually 00:20:01.679 --> 00:20:03.070 align:start position:0% uh these for example these are actually from<00:20:01.840> the<00:20:01.919> Stark<00:20:02.240> net<00:20:02.440> Foundation<00:20:02.919> they're 00:20:03.070 --> 00:20:03.080 align:start position:0% from the Stark net Foundation they're 00:20:03.080 --> 00:20:05.470 align:start position:0% from the Stark net Foundation they're not<00:20:03.280> Stark<00:20:03.640> net<00:20:04.240> they're<00:20:04.440> not 00:20:05.470 --> 00:20:05.480 align:start position:0% not Stark net they're not 00:20:05.480 --> 00:20:07.549 align:start position:0% not Stark net they're not starkware<00:20:06.480> but<00:20:06.679> again<00:20:06.880> check<00:20:07.159> these<00:20:07.320> things 00:20:07.549 --> 00:20:07.559 align:start position:0% starkware but again check these things 00:20:07.559 --> 00:20:09.510 align:start position:0% starkware but again check these things out<00:20:07.760> if<00:20:07.880> you<00:20:07.960> want<00:20:08.080> to<00:20:08.280> join<00:20:08.919> a<00:20:09.080> chain<00:20:09.360> a 00:20:09.510 --> 00:20:09.520 align:start position:0% out if you want to join a chain a 00:20:09.520 --> 00:20:10.830 align:start position:0% out if you want to join a chain a community<00:20:10.039> like<00:20:10.240> what<00:20:10.480> what<00:20:10.559> does<00:20:10.720> the 00:20:10.830 --> 00:20:10.840 align:start position:0% community like what what does the 00:20:10.840 --> 00:20:12.870 align:start position:0% community like what what does the community<00:20:11.280> stand<00:20:11.600> for<00:20:12.200> what's<00:20:12.400> important<00:20:12.720> to 00:20:12.870 --> 00:20:12.880 align:start position:0% community stand for what's important to 00:20:12.880 --> 00:20:15.750 align:start position:0% community stand for what's important to the<00:20:13.000> people<00:20:13.559> there<00:20:14.559> uh<00:20:14.799> and<00:20:15.000> finally<00:20:15.440> it's 00:20:15.750 --> 00:20:15.760 align:start position:0% the people there uh and finally it's 00:20:15.760 --> 00:20:18.510 align:start position:0% the people there uh and finally it's it's<00:20:16.760> still<00:20:17.679> at<00:20:17.799> the<00:20:17.880> end<00:20:18.039> of<00:20:18.159> the<00:20:18.280> day<00:20:18.400> a 00:20:18.510 --> 00:20:18.520 align:start position:0% it's still at the end of the day a 00:20:18.520 --> 00:20:20.990 align:start position:0% it's still at the end of the day a matter<00:20:18.760> of<00:20:19.000> people<00:20:20.000> uh<00:20:20.120> so<00:20:20.240> it's<00:20:20.400> worthwhile 00:20:20.990 --> 00:20:21.000 align:start position:0% matter of people uh so it's worthwhile 00:20:21.000 --> 00:20:22.990 align:start position:0% matter of people uh so it's worthwhile like<00:20:21.440> talking<00:20:21.760> to<00:20:21.960> the<00:20:22.120> people<00:20:22.400> seeing<00:20:22.840> what 00:20:22.990 --> 00:20:23.000 align:start position:0% like talking to the people seeing what 00:20:23.000 --> 00:20:26.029 align:start position:0% like talking to the people seeing what they're<00:20:23.280> like<00:20:23.520> feeling<00:20:23.960> the<00:20:24.520> energy<00:20:25.520> uh<00:20:25.760> see 00:20:26.029 --> 00:20:26.039 align:start position:0% they're like feeling the energy uh see 00:20:26.039 --> 00:20:28.390 align:start position:0% they're like feeling the energy uh see what<00:20:26.280> they<00:20:26.600> value<00:20:27.600> uh<00:20:27.720> that's<00:20:27.919> often<00:20:28.159> a<00:20:28.280> lot 00:20:28.390 --> 00:20:28.400 align:start position:0% what they value uh that's often a lot 00:20:28.400 --> 00:20:33.310 align:start position:0% what they value uh that's often a lot more<00:20:28.760> important<00:20:29.159> than<00:20:30.080> technical 00:20:33.310 --> 00:20:33.320 align:start position:0% 00:20:33.320 --> 00:20:36.669 align:start position:0% stuff<00:20:34.320> so<00:20:34.600> that's<00:20:34.880> it<00:20:35.320> uh<00:20:35.559> for<00:20:35.799> my 00:20:36.669 --> 00:20:36.679 align:start position:0% stuff so that's it uh for my 00:20:36.679 --> 00:20:40.990 align:start position:0% stuff so that's it uh for my part<00:20:37.679> all<00:20:38.039> right<00:20:38.520> thank<00:20:38.760> you<00:20:39.159> thank<00:20:39.760> you<00:20:40.760> yes 00:20:40.990 --> 00:20:41.000 align:start position:0% part all right thank you thank you yes 00:20:41.000 --> 00:20:43.350 align:start position:0% part all right thank you thank you yes let's<00:20:41.200> give<00:20:41.360> him<00:20:41.480> a<00:20:41.600> big<00:20:42.039> round<00:20:42.240> of<00:20:42.440> applause 00:20:43.350 --> 00:20:43.360 align:start position:0% let's give him a big round of applause 00:20:43.360 --> 00:20:46.990 align:start position:0% let's give him a big round of applause all<00:20:43.520> right<00:20:43.760> let's<00:20:43.960> do<00:20:44.520> Q&A<00:20:45.520> uh<00:20:46.480> yeah<00:20:46.679> when 00:20:46.990 --> 00:20:47.000 align:start position:0% all right let's do Q&A uh yeah when 00:20:47.000 --> 00:20:49.190 align:start position:0% all right let's do Q&A uh yeah when stage 00:20:49.190 --> 00:20:49.200 align:start position:0% stage 00:20:49.200 --> 00:20:51.870 align:start position:0% stage two<00:20:50.200> okay<00:20:50.919> I<00:20:51.039> start<00:20:51.320> with<00:20:51.480> first<00:20:51.679> question 00:20:51.870 --> 00:20:51.880 align:start position:0% two okay I start with first question 00:20:51.880 --> 00:20:53.750 align:start position:0% two okay I start with first question about<00:20:52.159> Bitcoin<00:20:52.799> okay<00:20:52.960> Bitcoin<00:20:53.320> is<00:20:53.440> weaker 00:20:53.750 --> 00:20:53.760 align:start position:0% about Bitcoin okay Bitcoin is weaker 00:20:53.760 --> 00:20:55.909 align:start position:0% about Bitcoin okay Bitcoin is weaker than<00:20:54.000> ethereum<00:20:54.840> no<00:20:54.960> no<00:20:55.120> no<00:20:55.320> the<00:20:55.520> the<00:20:55.640> the<00:20:55.720> first 00:20:55.909 --> 00:20:55.919 align:start position:0% than ethereum no no no the the the first 00:20:55.919 --> 00:20:59.110 align:start position:0% than ethereum no no no the the the first one<00:20:56.120> when<00:20:56.320> stage<00:20:56.600> two<00:20:57.480> ah<00:20:57.799> when 00:20:59.110 --> 00:20:59.120 align:start position:0% one when stage two ah when 00:20:59.120 --> 00:21:01.830 align:start position:0% one when stage two ah when stage<00:20:59.559> two<00:20:59.840> rollups<00:21:00.559> uh<00:21:00.720> so<00:21:01.080> we<00:21:01.200> are<00:21:01.440> working 00:21:01.830 --> 00:21:01.840 align:start position:0% stage two rollups uh so we are working 00:21:01.840 --> 00:21:04.549 align:start position:0% stage two rollups uh so we are working on<00:21:02.240> on<00:21:02.360> decentralization<00:21:03.360> as<00:21:03.520> we<00:21:03.679> speak<00:21:04.400> uh 00:21:04.549 --> 00:21:04.559 align:start position:0% on on decentralization as we speak uh 00:21:04.559 --> 00:21:06.310 align:start position:0% on on decentralization as we speak uh it's<00:21:04.679> coming<00:21:04.919> out<00:21:05.080> in<00:21:05.280> phases<00:21:05.799> so<00:21:06.000> we<00:21:06.159> have 00:21:06.310 --> 00:21:06.320 align:start position:0% it's coming out in phases so we have 00:21:06.320 --> 00:21:08.390 align:start position:0% it's coming out in phases so we have started<00:21:07.039> uh<00:21:07.320> uh<00:21:07.440> Gathering<00:21:07.840> people<00:21:08.039> to<00:21:08.159> start 00:21:08.390 --> 00:21:08.400 align:start position:0% started uh uh Gathering people to start 00:21:08.400 --> 00:21:10.430 align:start position:0% started uh uh Gathering people to start staking<00:21:09.200> at<00:21:09.320> First<00:21:09.559> St<00:21:10.000> they<00:21:10.080> still<00:21:10.240> don't 00:21:10.430 --> 00:21:10.440 align:start position:0% staking at First St they still don't 00:21:10.440 --> 00:21:13.029 align:start position:0% staking at First St they still don't play<00:21:10.600> a<00:21:10.679> part<00:21:10.840> in<00:21:11.480> consensus<00:21:12.480> uh<00:21:12.600> and<00:21:12.720> we're 00:21:13.029 --> 00:21:13.039 align:start position:0% play a part in consensus uh and we're 00:21:13.039 --> 00:21:14.950 align:start position:0% play a part in consensus uh and we're basically<00:21:13.440> rebuilding<00:21:14.000> our<00:21:14.240> code<00:21:14.640> it<00:21:14.760> was 00:21:14.950 --> 00:21:14.960 align:start position:0% basically rebuilding our code it was 00:21:14.960 --> 00:21:16.870 align:start position:0% basically rebuilding our code it was initially<00:21:15.919> uh<00:21:16.159> built<00:21:16.440> for<00:21:16.559> a<00:21:16.640> different 00:21:16.870 --> 00:21:16.880 align:start position:0% initially uh built for a different 00:21:16.880 --> 00:21:19.070 align:start position:0% initially uh built for a different system<00:21:17.200> than<00:21:17.360> we've<00:21:17.559> used<00:21:17.799> it<00:21:17.880> for<00:21:18.000> stet<00:21:18.960> the 00:21:19.070 --> 00:21:19.080 align:start position:0% system than we've used it for stet the 00:21:19.080 --> 00:21:21.390 align:start position:0% system than we've used it for stet the next<00:21:19.279> phase<00:21:19.480> is<00:21:19.600> coming<00:21:19.799> out<00:21:19.960> in<00:21:20.200> q1<00:21:21.200> our 00:21:21.390 --> 00:21:21.400 align:start position:0% next phase is coming out in q1 our 00:21:21.400 --> 00:21:23.549 align:start position:0% next phase is coming out in q1 our Target<00:21:21.720> is<00:21:21.880> towards<00:21:22.200> the<00:21:22.320> end<00:21:22.480> of<00:21:22.760> next<00:21:23.039> year 00:21:23.549 --> 00:21:23.559 align:start position:0% Target is towards the end of next year 00:21:23.559 --> 00:21:26.390 align:start position:0% Target is towards the end of next year to<00:21:23.760> start<00:21:24.400> uh<00:21:25.000> having<00:21:25.279> a<00:21:25.640> a<00:21:25.720> decentralized 00:21:26.390 --> 00:21:26.400 align:start position:0% to start uh having a a decentralized 00:21:26.400 --> 00:21:28.070 align:start position:0% to start uh having a a decentralized operation<00:21:26.919> of<00:21:27.039> the<00:21:27.159> network<00:21:27.559> so<00:21:27.679> basically 00:21:28.070 --> 00:21:28.080 align:start position:0% operation of the network so basically 00:21:28.080 --> 00:21:30.350 align:start position:0% operation of the network so basically anybody<00:21:28.720> wants<00:21:29.000> to<00:21:29.200> will<00:21:29.360> be<00:21:29.520> able<00:21:29.760> to 00:21:30.350 --> 00:21:30.360 align:start position:0% anybody wants to will be able to 00:21:30.360 --> 00:21:32.390 align:start position:0% anybody wants to will be able to sequence<00:21:30.840> and<00:21:31.039> prove<00:21:31.279> so<00:21:31.440> to<00:21:31.600> prove<00:21:31.799> star<00:21:32.200> net 00:21:32.390 --> 00:21:32.400 align:start position:0% sequence and prove so to prove star net 00:21:32.400 --> 00:21:35.630 align:start position:0% sequence and prove so to prove star net blocks<00:21:33.159> and<00:21:33.320> take<00:21:33.559> part<00:21:33.760> in<00:21:34.039> this<00:21:35.039> it's<00:21:35.400> it's<00:21:35.520> a 00:21:35.630 --> 00:21:35.640 align:start position:0% blocks and take part in this it's it's a 00:21:35.640 --> 00:21:38.110 align:start position:0% blocks and take part in this it's it's a major<00:21:35.960> effort<00:21:36.360> but<00:21:36.880> uh<00:21:37.200> it's<00:21:37.400> coming<00:21:37.960> all 00:21:38.110 --> 00:21:38.120 align:start position:0% major effort but uh it's coming all 00:21:38.120 --> 00:21:40.029 align:start position:0% major effort but uh it's coming all right<00:21:38.240> it's<00:21:38.440> coming<00:21:38.880> let's<00:21:39.159> keep<00:21:39.400> watching 00:21:40.029 --> 00:21:40.039 align:start position:0% right it's coming let's keep watching 00:21:40.039 --> 00:21:42.830 align:start position:0% right it's coming let's keep watching okay<00:21:40.320> next<00:21:40.520> one<00:21:41.279> uh<00:21:41.440> with<00:21:41.600> so<00:21:41.840> many<00:21:42.159> altoos 00:21:42.830 --> 00:21:42.840 align:start position:0% okay next one uh with so many altoos 00:21:42.840 --> 00:21:44.789 align:start position:0% okay next one uh with so many altoos it's<00:21:43.039> too<00:21:43.240> much<00:21:43.480> fragmentation<00:21:44.279> which<00:21:44.400> one<00:21:44.640> we 00:21:44.789 --> 00:21:44.799 align:start position:0% it's too much fragmentation which one we 00:21:44.799 --> 00:21:46.750 align:start position:0% it's too much fragmentation which one we win<00:21:45.440> what<00:21:45.559> are<00:21:45.720> the<00:21:45.919> characteristic<00:21:46.480> of<00:21:46.600> the 00:21:46.750 --> 00:21:46.760 align:start position:0% win what are the characteristic of the 00:21:46.760 --> 00:21:50.630 align:start position:0% win what are the characteristic of the winning<00:21:47.400> and<00:21:47.760> possibility<00:21:48.159> of<00:21:48.720> unifying<00:21:49.720> okay 00:21:50.630 --> 00:21:50.640 align:start position:0% winning and possibility of unifying okay 00:21:50.640 --> 00:21:53.789 align:start position:0% winning and possibility of unifying okay so<00:21:51.640> a<00:21:51.760> lot<00:21:51.880> of<00:21:52.000> what<00:21:52.120> I<00:21:52.240> said<00:21:52.440> is<00:21:52.679> around<00:21:53.120> that 00:21:53.789 --> 00:21:53.799 align:start position:0% so a lot of what I said is around that 00:21:53.799 --> 00:21:55.830 align:start position:0% so a lot of what I said is around that uh<00:21:54.360> I<00:21:54.559> don't<00:21:54.799> think<00:21:55.000> it's<00:21:55.120> going<00:21:55.240> to<00:21:55.360> be<00:21:55.480> a<00:21:55.640> one- 00:21:55.830 --> 00:21:55.840 align:start position:0% uh I don't think it's going to be a one- 00:21:55.840 --> 00:21:57.789 align:start position:0% uh I don't think it's going to be a one- winner<00:21:56.159> take<00:21:56.440> all<00:21:57.120> uh<00:21:57.279> I<00:21:57.360> think<00:21:57.520> there<00:21:57.600> are<00:21:57.720> a 00:21:57.789 --> 00:21:57.799 align:start position:0% winner take all uh I think there are a 00:21:57.799 --> 00:22:00.470 align:start position:0% winner take all uh I think there are a bunch<00:21:57.960> of<00:21:58.080> use<00:21:58.600> cases<00:21:59.039> that<00:21:59.799> do<00:22:00.039> allow 00:22:00.470 --> 00:22:00.480 align:start position:0% bunch of use cases that do allow 00:22:00.480 --> 00:22:02.149 align:start position:0% bunch of use cases that do allow different<00:22:00.799> things<00:22:01.039> and<00:22:01.240> even<00:22:01.720> prefer 00:22:02.149 --> 00:22:02.159 align:start position:0% different things and even prefer 00:22:02.159 --> 00:22:04.830 align:start position:0% different things and even prefer different<00:22:02.440> things<00:22:02.840> so<00:22:03.080> even<00:22:04.080> the<00:22:04.279> public 00:22:04.830 --> 00:22:04.840 align:start position:0% different things so even the public 00:22:04.840 --> 00:22:07.590 align:start position:0% different things so even the public network<00:22:05.240> versus<00:22:05.600> app<00:22:05.840> chain<00:22:06.520> uh<00:22:07.120> aspect<00:22:07.480> that 00:22:07.590 --> 00:22:07.600 align:start position:0% network versus app chain uh aspect that 00:22:07.600 --> 00:22:10.029 align:start position:0% network versus app chain uh aspect that I<00:22:07.720> touched<00:22:08.159> before<00:22:09.159> in<00:22:09.320> some<00:22:09.559> cases<00:22:09.840> people 00:22:10.029 --> 00:22:10.039 align:start position:0% I touched before in some cases people 00:22:10.039 --> 00:22:11.430 align:start position:0% I touched before in some cases people will<00:22:10.200> want<00:22:10.279> to<00:22:10.400> run<00:22:10.600> app<00:22:10.799> chains<00:22:11.000> and<00:22:11.120> not<00:22:11.279> run 00:22:11.430 --> 00:22:11.440 align:start position:0% will want to run app chains and not run 00:22:11.440 --> 00:22:12.470 align:start position:0% will want to run app chains and not run on<00:22:11.520> the<00:22:11.640> main<00:22:11.799> chain<00:22:11.960> so<00:22:12.080> I<00:22:12.159> don't<00:22:12.279> think<00:22:12.400> it's 00:22:12.470 --> 00:22:12.480 align:start position:0% on the main chain so I don't think it's 00:22:12.480 --> 00:22:13.870 align:start position:0% on the main chain so I don't think it's going<00:22:12.600> to<00:22:12.679> be<00:22:12.840> just<00:22:13.000> one<00:22:13.200> chain<00:22:13.440> that<00:22:13.559> rules 00:22:13.870 --> 00:22:13.880 align:start position:0% going to be just one chain that rules 00:22:13.880 --> 00:22:16.750 align:start position:0% going to be just one chain that rules them<00:22:14.279> all<00:22:15.279> um<00:22:15.760> I<00:22:15.840> do<00:22:16.039> think<00:22:16.240> that<00:22:16.400> validity 00:22:16.750 --> 00:22:16.760 align:start position:0% them all um I do think that validity 00:22:16.760 --> 00:22:20.789 align:start position:0% them all um I do think that validity rups<00:22:17.279> have<00:22:17.679> uh<00:22:17.799> some<00:22:18.440> inherent<00:22:19.440> uh<00:22:19.799> benefits 00:22:20.789 --> 00:22:20.799 align:start position:0% rups have uh some inherent uh benefits 00:22:20.799 --> 00:22:22.230 align:start position:0% rups have uh some inherent uh benefits over<00:22:21.120> the<00:22:21.240> other<00:22:21.480> options<00:22:21.799> so<00:22:22.000> I<00:22:22.080> think 00:22:22.230 --> 00:22:22.240 align:start position:0% over the other options so I think 00:22:22.240 --> 00:22:24.630 align:start position:0% over the other options so I think they're<00:22:22.559> M<00:22:22.960> much<00:22:23.200> better<00:22:23.480> poised<00:22:23.960> longer<00:22:24.320> term 00:22:24.630 --> 00:22:24.640 align:start position:0% they're M much better poised longer term 00:22:24.640 --> 00:22:27.830 align:start position:0% they're M much better poised longer term to<00:22:24.840> to<00:22:25.159> give<00:22:26.159> scale<00:22:26.679> and<00:22:26.840> and<00:22:27.000> better<00:22:27.320> cost<00:22:27.679> and 00:22:27.830 --> 00:22:27.840 align:start position:0% to to give scale and and better cost and 00:22:27.840 --> 00:22:29.870 align:start position:0% to to give scale and and better cost and and<00:22:27.960> better<00:22:28.159> us<00:22:28.559> next<00:22:29.200> uh<00:22:29.279> but<00:22:29.400> there<00:22:29.480> are<00:22:29.679> lots 00:22:29.870 --> 00:22:29.880 align:start position:0% and better us next uh but there are lots 00:22:29.880 --> 00:22:32.669 align:start position:0% and better us next uh but there are lots of<00:22:30.080> them<00:22:30.279> as<00:22:30.440> well<00:22:31.360> uh<00:22:31.919> and<00:22:32.120> and<00:22:32.279> definitely 00:22:32.669 --> 00:22:32.679 align:start position:0% of them as well uh and and definitely 00:22:32.679 --> 00:22:33.830 align:start position:0% of them as well uh and and definitely there's<00:22:32.880> going<00:22:33.000> to<00:22:33.080> be<00:22:33.240> some<00:22:33.440> it's<00:22:33.559> not<00:22:33.679> just 00:22:33.830 --> 00:22:33.840 align:start position:0% there's going to be some it's not just 00:22:33.840 --> 00:22:35.630 align:start position:0% there's going to be some it's not just unification<00:22:34.600> it's<00:22:34.760> going<00:22:34.880> to<00:22:35.000> be<00:22:35.440> there's 00:22:35.630 --> 00:22:35.640 align:start position:0% unification it's going to be there's 00:22:35.640 --> 00:22:37.669 align:start position:0% unification it's going to be there's going<00:22:35.720> to<00:22:35.840> be<00:22:36.000> some<00:22:36.760> uh<00:22:37.159> like<00:22:37.360> better 00:22:37.669 --> 00:22:37.679 align:start position:0% going to be some uh like better 00:22:37.679 --> 00:22:40.710 align:start position:0% going to be some uh like better coordination<00:22:38.559> or<00:22:38.960> uh<00:22:39.279> uh<00:22:39.480> bridging<00:22:40.480> or 00:22:40.710 --> 00:22:40.720 align:start position:0% coordination or uh uh bridging or 00:22:40.720 --> 00:22:43.510 align:start position:0% coordination or uh uh bridging or aggregation<00:22:41.720> between<00:22:42.720> uh<00:22:42.960> different<00:22:43.200> layer 00:22:43.510 --> 00:22:43.520 align:start position:0% aggregation between uh different layer 00:22:43.520 --> 00:22:45.149 align:start position:0% aggregation between uh different layer toos<00:22:43.840> a<00:22:43.960> lot<00:22:44.080> of<00:22:44.200> teams<00:22:44.480> are<00:22:44.600> working<00:22:44.840> on<00:22:44.960> it 00:22:45.149 --> 00:22:45.159 align:start position:0% toos a lot of teams are working on it 00:22:45.159 --> 00:22:46.470 align:start position:0% toos a lot of teams are working on it right<00:22:45.279> now<00:22:45.400> it's<00:22:45.520> still<00:22:45.720> not<00:22:45.880> working<00:22:46.240> well 00:22:46.470 --> 00:22:46.480 align:start position:0% right now it's still not working well 00:22:46.480 --> 00:22:48.269 align:start position:0% right now it's still not working well but<00:22:46.600> I<00:22:46.720> believe<00:22:47.000> that<00:22:47.159> will<00:22:47.400> happen<00:22:47.919> all<00:22:48.039> right 00:22:48.269 --> 00:22:48.279 align:start position:0% but I believe that will happen all right 00:22:48.279 --> 00:22:50.110 align:start position:0% but I believe that will happen all right and<00:22:48.440> I<00:22:48.640> encourage<00:22:49.080> you<00:22:49.200> all<00:22:49.400> to<00:22:49.559> stay<00:22:49.799> for<00:22:49.960> the 00:22:50.110 --> 00:22:50.120 align:start position:0% and I encourage you all to stay for the 00:22:50.120 --> 00:22:52.029 align:start position:0% and I encourage you all to stay for the next<00:22:50.360> session<00:22:50.840> because<00:22:51.080> we<00:22:51.279> are<00:22:51.640> about<00:22:51.840> to 00:22:52.029 --> 00:22:52.039 align:start position:0% next session because we are about to 00:22:52.039 --> 00:22:54.269 align:start position:0% next session because we are about to talking<00:22:52.400> about<00:22:52.679> this<00:22:52.880> topic<00:22:53.240> exactly<00:22:54.159> all 00:22:54.269 --> 00:22:54.279 align:start position:0% talking about this topic exactly all 00:22:54.279 --> 00:22:57.269 align:start position:0% talking about this topic exactly all right<00:22:54.480> next<00:22:54.640> one<00:22:55.320> why<00:22:55.600> Kyo<00:22:55.960> not 00:22:57.269 --> 00:22:57.279 align:start position:0% right next one why Kyo not 00:22:57.279 --> 00:22:59.750 align:start position:0% right next one why Kyo not rust<00:22:58.279> why<00:22:58.640> Cairo<00:22:58.960> and<00:22:59.039> not<00:22:59.200> rust<00:22:59.520> okay<00:22:59.600> so 00:22:59.750 --> 00:22:59.760 align:start position:0% rust why Cairo and not rust okay so 00:22:59.760 --> 00:23:02.789 align:start position:0% rust why Cairo and not rust okay so Cairo<00:23:00.120> is<00:23:00.279> very<00:23:00.480> much<00:23:00.720> like<00:23:01.000> rust<00:23:02.000> uh<00:23:02.400> not<00:23:02.640> that 00:23:02.789 --> 00:23:02.799 align:start position:0% Cairo is very much like rust uh not that 00:23:02.799 --> 00:23:05.470 align:start position:0% Cairo is very much like rust uh not that many<00:23:03.279> differences<00:23:04.279> uh<00:23:04.760> it<00:23:04.880> is<00:23:05.000> a<00:23:05.159> smart 00:23:05.470 --> 00:23:05.480 align:start position:0% many differences uh it is a smart 00:23:05.480 --> 00:23:08.029 align:start position:0% many differences uh it is a smart contract<00:23:06.000> language<00:23:06.320> so<00:23:06.559> rust<00:23:06.919> is<00:23:07.559> wider<00:23:07.919> in 00:23:08.029 --> 00:23:08.039 align:start position:0% contract language so rust is wider in 00:23:08.039 --> 00:23:09.149 align:start position:0% contract language so rust is wider in its<00:23:08.200> scope<00:23:08.440> you<00:23:08.520> could<00:23:08.640> write<00:23:08.799> a<00:23:08.919> lot<00:23:09.039> of 00:23:09.149 --> 00:23:09.159 align:start position:0% its scope you could write a lot of 00:23:09.159 --> 00:23:10.630 align:start position:0% its scope you could write a lot of things<00:23:09.320> in<00:23:09.480> Rust<00:23:09.799> that<00:23:09.919> you<00:23:10.080> can't<00:23:10.320> really 00:23:10.630 --> 00:23:10.640 align:start position:0% things in Rust that you can't really 00:23:10.640 --> 00:23:13.070 align:start position:0% things in Rust that you can't really prove<00:23:11.080> because<00:23:11.279> they<00:23:11.440> use<00:23:11.640> some<00:23:11.799> other<00:23:12.080> stuff 00:23:13.070 --> 00:23:13.080 align:start position:0% prove because they use some other stuff 00:23:13.080 --> 00:23:15.789 align:start position:0% prove because they use some other stuff uh<00:23:13.240> it's<00:23:13.400> not<00:23:13.679> very<00:23:13.919> far<00:23:14.200> from<00:23:14.360> it<00:23:15.159> uh<00:23:15.360> we<00:23:15.480> are 00:23:15.789 --> 00:23:15.799 align:start position:0% uh it's not very far from it uh we are 00:23:15.799 --> 00:23:17.310 align:start position:0% uh it's not very far from it uh we are always<00:23:16.159> considering<00:23:16.720> whether<00:23:16.960> we<00:23:17.039> want<00:23:17.159> to 00:23:17.310 --> 00:23:17.320 align:start position:0% always considering whether we want to 00:23:17.320 --> 00:23:19.590 align:start position:0% always considering whether we want to support<00:23:17.679> additional<00:23:18.080> VMS<00:23:18.520> and<00:23:18.679> some<00:23:19.159> like<00:23:19.480> the 00:23:19.590 --> 00:23:19.600 align:start position:0% support additional VMS and some like the 00:23:19.600 --> 00:23:22.149 align:start position:0% support additional VMS and some like the next<00:23:19.760> one<00:23:20.000> might<00:23:20.200> be<00:23:20.360> rust<00:23:20.919> itself<00:23:21.919> uh<00:23:22.000> but 00:23:22.149 --> 00:23:22.159 align:start position:0% next one might be rust itself uh but 00:23:22.159 --> 00:23:24.269 align:start position:0% next one might be rust itself uh but again<00:23:22.320> if<00:23:22.480> you<00:23:22.600> like<00:23:22.760> rust<00:23:23.520> uh<00:23:23.840> I<00:23:23.919> don't<00:23:24.120> think 00:23:24.269 --> 00:23:24.279 align:start position:0% again if you like rust uh I don't think 00:23:24.279 --> 00:23:26.070 align:start position:0% again if you like rust uh I don't think you'll<00:23:24.520> find<00:23:24.799> CYO<00:23:25.200> major<00:23:25.440> difference<00:23:25.960> how 00:23:26.070 --> 00:23:26.080 align:start position:0% you'll find CYO major difference how 00:23:26.080 --> 00:23:27.909 align:start position:0% you'll find CYO major difference how hard<00:23:26.279> is<00:23:26.400> it<00:23:26.600> if<00:23:26.679> I<00:23:26.799> know<00:23:27.000> rust<00:23:27.480> like<00:23:27.600> how<00:23:27.760> hard 00:23:27.909 --> 00:23:27.919 align:start position:0% hard is it if I know rust like how hard 00:23:27.919 --> 00:23:29.070 align:start position:0% hard is it if I know rust like how hard is<00:23:28.039> it<00:23:28.120> to 00:23:29.070 --> 00:23:29.080 align:start position:0% is it to 00:23:29.080 --> 00:23:31.430 align:start position:0% is it to it's<00:23:29.279> pretty<00:23:29.520> easy<00:23:29.919> it's<00:23:30.360> uh<00:23:31.000> like<00:23:31.120> for<00:23:31.279> people 00:23:31.430 --> 00:23:31.440 align:start position:0% it's pretty easy it's uh like for people 00:23:31.440 --> 00:23:33.750 align:start position:0% it's pretty easy it's uh like for people who<00:23:31.559> come<00:23:31.720> from<00:23:31.880> rust<00:23:32.600> typically<00:23:33.159> Cairo<00:23:33.520> is<00:23:33.600> a 00:23:33.750 --> 00:23:33.760 align:start position:0% who come from rust typically Cairo is a 00:23:33.760 --> 00:23:35.950 align:start position:0% who come from rust typically Cairo is a very<00:23:34.039> natural<00:23:34.440> example<00:23:35.400> uh<00:23:35.520> if<00:23:35.640> they<00:23:35.760> go<00:23:35.840> to 00:23:35.950 --> 00:23:35.960 align:start position:0% very natural example uh if they go to 00:23:35.960 --> 00:23:37.390 align:start position:0% very natural example uh if they go to Solana<00:23:36.360> it's<00:23:36.480> like<00:23:36.640> rust<00:23:36.919> but<00:23:37.039> it's<00:23:37.159> not 00:23:37.390 --> 00:23:37.400 align:start position:0% Solana it's like rust but it's not 00:23:37.400 --> 00:23:40.110 align:start position:0% Solana it's like rust but it's not exactly<00:23:37.799> rust<00:23:38.200> either<00:23:38.480> so<00:23:38.679> it's<00:23:38.960> it's<00:23:39.120> similar 00:23:40.110 --> 00:23:40.120 align:start position:0% exactly rust either so it's it's similar 00:23:40.120 --> 00:23:42.350 align:start position:0% exactly rust either so it's it's similar okay<00:23:40.600> thanks<00:23:41.080> all<00:23:41.200> right<00:23:41.400> next<00:23:41.600> one<00:23:42.000> I<00:23:42.120> heard 00:23:42.350 --> 00:23:42.360 align:start position:0% okay thanks all right next one I heard 00:23:42.360 --> 00:23:45.149 align:start position:0% okay thanks all right next one I heard State<00:23:42.799> offer<00:23:43.200> two<00:23:43.480> seconds<00:23:43.880> finality<00:23:44.559> but<00:23:44.720> eum 00:23:45.149 --> 00:23:45.159 align:start position:0% State offer two seconds finality but eum 00:23:45.159 --> 00:23:47.510 align:start position:0% State offer two seconds finality but eum itself<00:23:45.559> cannot<00:23:45.840> finalize<00:23:46.279> block<00:23:46.600> that<00:23:46.799> fast 00:23:47.510 --> 00:23:47.520 align:start position:0% itself cannot finalize block that fast 00:23:47.520 --> 00:23:50.230 align:start position:0% itself cannot finalize block that fast what<00:23:47.640> do<00:23:47.720> you<00:23:47.799> mean<00:23:47.960> by<00:23:48.440> okay<00:23:48.720> so<00:23:49.720> always<00:23:50.080> in 00:23:50.230 --> 00:23:50.240 align:start position:0% what do you mean by okay so always in 00:23:50.240 --> 00:23:51.669 align:start position:0% what do you mean by okay so always in Layer<00:23:50.520> Two<00:23:50.760> you<00:23:50.880> have<00:23:51.039> two<00:23:51.240> levels<00:23:51.520> of 00:23:51.669 --> 00:23:51.679 align:start position:0% Layer Two you have two levels of 00:23:51.679 --> 00:23:53.470 align:start position:0% Layer Two you have two levels of finality<00:23:52.159> you<00:23:52.279> have<00:23:52.480> Layer<00:23:52.679> Two<00:23:52.919> finality<00:23:53.360> and 00:23:53.470 --> 00:23:53.480 align:start position:0% finality you have Layer Two finality and 00:23:53.480 --> 00:23:55.110 align:start position:0% finality you have Layer Two finality and they're<00:23:53.600> in<00:23:53.720> layer<00:23:53.960> one<00:23:54.159> finality<00:23:54.679> layer<00:23:54.919> one 00:23:55.110 --> 00:23:55.120 align:start position:0% they're in layer one finality layer one 00:23:55.120 --> 00:23:56.950 align:start position:0% they're in layer one finality layer one finality<00:23:55.559> you<00:23:55.720> only<00:23:55.960> get<00:23:56.240> once<00:23:56.480> the<00:23:56.640> proofs 00:23:56.950 --> 00:23:56.960 align:start position:0% finality you only get once the proofs 00:23:56.960 --> 00:23:58.430 align:start position:0% finality you only get once the proofs reach<00:23:57.240> ethereum<00:23:57.679> and<00:23:57.799> ethereum<00:23:58.200> very 00:23:58.430 --> 00:23:58.440 align:start position:0% reach ethereum and ethereum very 00:23:58.440 --> 00:24:00.350 align:start position:0% reach ethereum and ethereum very verifies<00:23:58.799> it<00:23:59.000> which<00:23:59.080> is<00:23:59.240> definitely<00:23:59.559> lot<00:24:00.159> more 00:24:00.350 --> 00:24:00.360 align:start position:0% verifies it which is definitely lot more 00:24:00.360 --> 00:24:03.310 align:start position:0% verifies it which is definitely lot more than<00:24:00.559> 10<00:24:00.960> than<00:24:01.080> two<00:24:01.400> seconds<00:24:02.400> but<00:24:02.919> you<00:24:03.080> also 00:24:03.310 --> 00:24:03.320 align:start position:0% than 10 than two seconds but you also 00:24:03.320 --> 00:24:06.070 align:start position:0% than 10 than two seconds but you also have<00:24:03.840> earlier<00:24:04.279> fin<00:24:04.720> finality<00:24:05.159> in<00:24:05.279> Layer<00:24:05.559> Two 00:24:06.070 --> 00:24:06.080 align:start position:0% have earlier fin finality in Layer Two 00:24:06.080 --> 00:24:08.510 align:start position:0% have earlier fin finality in Layer Two right<00:24:06.240> now<00:24:06.880> Stark<00:24:07.320> net<00:24:07.480> is<00:24:07.640> centralized<00:24:08.279> so 00:24:08.510 --> 00:24:08.520 align:start position:0% right now Stark net is centralized so 00:24:08.520 --> 00:24:10.909 align:start position:0% right now Stark net is centralized so this<00:24:08.720> basically<00:24:09.080> rides<00:24:09.400> on<00:24:09.559> a<00:24:09.960> centralized 00:24:10.909 --> 00:24:10.919 align:start position:0% this basically rides on a centralized 00:24:10.919 --> 00:24:13.710 align:start position:0% this basically rides on a centralized sequencer<00:24:11.919> uh<00:24:12.640> ensuring<00:24:13.080> that<00:24:13.240> transactions 00:24:13.710 --> 00:24:13.720 align:start position:0% sequencer uh ensuring that transactions 00:24:13.720 --> 00:24:15.430 align:start position:0% sequencer uh ensuring that transactions have<00:24:13.880> been<00:24:14.000> included<00:24:14.760> but<00:24:14.919> once<00:24:15.159> this<00:24:15.279> is 00:24:15.430 --> 00:24:15.440 align:start position:0% have been included but once this is 00:24:15.440 --> 00:24:16.510 align:start position:0% have been included but once this is decentralized<00:24:16.080> there's<00:24:16.240> going<00:24:16.360> to<00:24:16.400> be 00:24:16.510 --> 00:24:16.520 align:start position:0% decentralized there's going to be 00:24:16.520 --> 00:24:17.870 align:start position:0% decentralized there's going to be consensus<00:24:16.960> protocol<00:24:17.320> in<00:24:17.400> Layer<00:24:17.640> Two<00:24:17.799> and 00:24:17.870 --> 00:24:17.880 align:start position:0% consensus protocol in Layer Two and 00:24:17.880 --> 00:24:19.630 align:start position:0% consensus protocol in Layer Two and you're<00:24:18.000> going<00:24:18.080> to<00:24:18.240> get<00:24:18.840> much<00:24:19.080> quicker<00:24:19.400> Layer 00:24:19.630 --> 00:24:19.640 align:start position:0% you're going to get much quicker Layer 00:24:19.640 --> 00:24:21.789 align:start position:0% you're going to get much quicker Layer Two<00:24:19.880> finality<00:24:20.400> before<00:24:20.720> layer<00:24:21.000> one<00:24:21.520> and<00:24:21.679> that 00:24:21.789 --> 00:24:21.799 align:start position:0% Two finality before layer one and that 00:24:21.799 --> 00:24:23.070 align:start position:0% Two finality before layer one and that could<00:24:21.960> be<00:24:22.039> in<00:24:22.159> the<00:24:22.240> order<00:24:22.480> of<00:24:22.559> magnitude<00:24:22.960> of 00:24:23.070 --> 00:24:23.080 align:start position:0% could be in the order of magnitude of 00:24:23.080 --> 00:24:25.269 align:start position:0% could be in the order of magnitude of two<00:24:23.279> seconds<00:24:23.600> probably<00:24:23.880> even<00:24:24.120> less<00:24:24.880> all<00:24:25.039> right 00:24:25.269 --> 00:24:25.279 align:start position:0% two seconds probably even less all right 00:24:25.279 --> 00:24:27.549 align:start position:0% two seconds probably even less all right thank<00:24:25.480> you<00:24:25.880> okay<00:24:26.200> next<00:24:26.440> one<00:24:26.960> uh<00:24:27.159> let's<00:24:27.360> talk 00:24:27.549 --> 00:24:27.559 align:start position:0% thank you okay next one uh let's talk 00:24:27.559 --> 00:24:29.310 align:start position:0% thank you okay next one uh let's talk about<00:24:27.880> Bitcoin<00:24:28.399> eum<00:24:28.799> that<00:24:28.880> you<00:24:29.000> mentioned 00:24:29.310 --> 00:24:29.320 align:start position:0% about Bitcoin eum that you mentioned 00:24:29.320 --> 00:24:31.990 align:start position:0% about Bitcoin eum that you mentioned that<00:24:29.440> you<00:24:29.520> will<00:24:29.720> post<00:24:30.000> on<00:24:30.120> the<00:24:30.640> two<00:24:30.880> chains<00:24:31.559> uh 00:24:31.990 --> 00:24:32.000 align:start position:0% that you will post on the two chains uh 00:24:32.000 --> 00:24:35.310 align:start position:0% that you will post on the two chains uh Wier<00:24:32.600> board<00:24:33.159> and<00:24:33.440> yeah<00:24:33.600> what<00:24:33.720> if<00:24:33.880> they<00:24:34.320> okay<00:24:34.559> so 00:24:35.310 --> 00:24:35.320 align:start position:0% Wier board and yeah what if they okay so 00:24:35.320 --> 00:24:37.110 align:start position:0% Wier board and yeah what if they okay so I<00:24:35.440> I<00:24:35.559> wouldn't<00:24:35.840> say<00:24:36.120> Bitcoin<00:24:36.559> is<00:24:36.679> weaker<00:24:37.000> than 00:24:37.110 --> 00:24:37.120 align:start position:0% I I wouldn't say Bitcoin is weaker than 00:24:37.120 --> 00:24:38.909 align:start position:0% I I wouldn't say Bitcoin is weaker than ethereum<00:24:37.600> I<00:24:37.679> think<00:24:37.840> in<00:24:37.960> terms<00:24:38.200> of<00:24:38.440> security 00:24:38.909 --> 00:24:38.919 align:start position:0% ethereum I think in terms of security 00:24:38.919 --> 00:24:40.389 align:start position:0% ethereum I think in terms of security it's<00:24:39.080> probably<00:24:39.399> actually<00:24:39.840> stronger<00:24:40.120> than 00:24:40.389 --> 00:24:40.399 align:start position:0% it's probably actually stronger than 00:24:40.399 --> 00:24:43.549 align:start position:0% it's probably actually stronger than ethereum<00:24:41.399> uh<00:24:41.640> in<00:24:41.799> terms<00:24:42.120> of<00:24:42.559> uh<00:24:43.000> uh 00:24:43.549 --> 00:24:43.559 align:start position:0% ethereum uh in terms of uh uh 00:24:43.559 --> 00:24:45.549 align:start position:0% ethereum uh in terms of uh uh programmability<00:24:44.559> it<00:24:44.679> offers<00:24:45.000> a<00:24:45.120> lot<00:24:45.320> less 00:24:45.549 --> 00:24:45.559 align:start position:0% programmability it offers a lot less 00:24:45.559 --> 00:24:47.909 align:start position:0% programmability it offers a lot less options<00:24:45.840> than<00:24:46.159> ethereum<00:24:47.159> uh<00:24:47.360> but<00:24:47.520> it<00:24:47.679> is 00:24:47.909 --> 00:24:47.919 align:start position:0% options than ethereum uh but it is 00:24:47.919 --> 00:24:49.630 align:start position:0% options than ethereum uh but it is actually<00:24:48.279> very<00:24:48.520> secure<00:24:48.880> and<00:24:49.000> it<00:24:49.080> is<00:24:49.200> a<00:24:49.320> very 00:24:49.630 --> 00:24:49.640 align:start position:0% actually very secure and it is a very 00:24:49.640 --> 00:24:51.029 align:start position:0% actually very secure and it is a very strong<00:24:49.840> Network<00:24:50.200> there<00:24:50.279> are<00:24:50.399> lots<00:24:50.600> of<00:24:50.720> people 00:24:51.029 --> 00:24:51.039 align:start position:0% strong Network there are lots of people 00:24:51.039 --> 00:24:53.750 align:start position:0% strong Network there are lots of people there<00:24:51.200> and<00:24:51.360> there's<00:24:51.640> lots<00:24:51.880> of<00:24:52.240> of<00:24:52.640> uh<00:24:53.159> hardware 00:24:53.750 --> 00:24:53.760 align:start position:0% there and there's lots of of uh hardware 00:24:53.760 --> 00:24:55.950 align:start position:0% there and there's lots of of uh hardware and<00:24:54.240> capital<00:24:54.720> actually<00:24:55.000> securing<00:24:55.520> that 00:24:55.950 --> 00:24:55.960 align:start position:0% and capital actually securing that 00:24:55.960 --> 00:24:58.389 align:start position:0% and capital actually securing that network<00:24:56.960> uh<00:24:57.120> and<00:24:57.279> today<00:24:57.600> for<00:24:57.799> the<00:24:57.880> people<00:24:58.080> on 00:24:58.389 --> 00:24:58.399 align:start position:0% network uh and today for the people on 00:24:58.399 --> 00:24:59.830 align:start position:0% network uh and today for the people on Bitcoin<00:24:58.799> they<00:24:58.919> can't<00:24:59.120> do<00:24:59.320> that<00:24:59.520> much<00:24:59.679> with 00:24:59.830 --> 00:24:59.840 align:start position:0% Bitcoin they can't do that much with 00:24:59.840 --> 00:25:02.630 align:start position:0% Bitcoin they can't do that much with their<00:25:00.039> tokens<00:25:00.559> because<00:25:01.360> because<00:25:01.559> of<00:25:01.679> the<00:25:01.880> pro 00:25:02.630 --> 00:25:02.640 align:start position:0% their tokens because because of the pro 00:25:02.640 --> 00:25:04.669 align:start position:0% their tokens because because of the pro uh<00:25:03.080> uh<00:25:03.399> programmability<00:25:04.080> issue<00:25:04.360> that<00:25:04.440> I<00:25:04.559> just 00:25:04.669 --> 00:25:04.679 align:start position:0% uh uh programmability issue that I just 00:25:04.679 --> 00:25:06.710 align:start position:0% uh uh programmability issue that I just mentioned<00:25:05.279> so<00:25:05.480> if<00:25:05.559> you<00:25:05.640> have<00:25:05.799> Stark<00:25:06.120> net<00:25:06.360> r<00:25:06.559> on 00:25:06.710 --> 00:25:06.720 align:start position:0% mentioned so if you have Stark net r on 00:25:06.720 --> 00:25:08.990 align:start position:0% mentioned so if you have Stark net r on top<00:25:06.840> of<00:25:07.240> Bitcoin<00:25:07.679> as<00:25:07.799> well<00:25:08.360> all<00:25:08.480> of<00:25:08.600> a<00:25:08.720> sudden 00:25:08.990 --> 00:25:09.000 align:start position:0% top of Bitcoin as well all of a sudden 00:25:09.000 --> 00:25:11.029 align:start position:0% top of Bitcoin as well all of a sudden you<00:25:09.120> could<00:25:09.279> take<00:25:09.440> your<00:25:09.679> Bitcoin<00:25:10.440> move<00:25:10.640> it<00:25:10.799> to 00:25:11.029 --> 00:25:11.039 align:start position:0% you could take your Bitcoin move it to 00:25:11.039 --> 00:25:12.870 align:start position:0% you could take your Bitcoin move it to to<00:25:11.159> a<00:25:11.240> layer<00:25:11.520> two<00:25:11.799> which<00:25:11.919> is<00:25:12.200> as<00:25:12.360> secure<00:25:12.679> as 00:25:12.870 --> 00:25:12.880 align:start position:0% to a layer two which is as secure as 00:25:12.880 --> 00:25:14.750 align:start position:0% to a layer two which is as secure as Bitcoin<00:25:13.640> and<00:25:13.760> do<00:25:14.000> stuff<00:25:14.200> with<00:25:14.360> it<00:25:14.480> and<00:25:14.600> have 00:25:14.750 --> 00:25:14.760 align:start position:0% Bitcoin and do stuff with it and have 00:25:14.760 --> 00:25:17.310 align:start position:0% Bitcoin and do stuff with it and have Smart<00:25:15.080> contracts<00:25:15.520> that<00:25:15.640> you<00:25:15.760> could<00:25:16.120> run<00:25:17.120> uh 00:25:17.310 --> 00:25:17.320 align:start position:0% Smart contracts that you could run uh 00:25:17.320 --> 00:25:19.669 align:start position:0% Smart contracts that you could run uh ethereum<00:25:17.760> allows<00:25:18.120> it<00:25:18.320> today<00:25:18.840> but<00:25:19.440> for<00:25:19.600> the 00:25:19.669 --> 00:25:19.679 align:start position:0% ethereum allows it today but for the 00:25:19.679 --> 00:25:21.430 align:start position:0% ethereum allows it today but for the ethereum<00:25:20.120> community<00:25:20.520> so<00:25:20.679> I<00:25:20.799> think<00:25:20.960> unifying 00:25:21.430 --> 00:25:21.440 align:start position:0% ethereum community so I think unifying 00:25:21.440 --> 00:25:24.590 align:start position:0% ethereum community so I think unifying the<00:25:21.600> two<00:25:21.840> will<00:25:22.080> have<00:25:22.600> uh<00:25:23.600> great<00:25:23.919> benefits 00:25:24.590 --> 00:25:24.600 align:start position:0% the two will have uh great benefits 00:25:24.600 --> 00:25:26.269 align:start position:0% the two will have uh great benefits definitely<00:25:24.960> for<00:25:25.120> the<00:25:25.440> Bitcoin<00:25:25.799> Community<00:25:26.159> but 00:25:26.269 --> 00:25:26.279 align:start position:0% definitely for the Bitcoin Community but 00:25:26.279 --> 00:25:27.549 align:start position:0% definitely for the Bitcoin Community but also<00:25:26.440> for<00:25:26.559> the<00:25:26.640> ethereum<00:25:27.000> community<00:25:27.320> because 00:25:27.549 --> 00:25:27.559 align:start position:0% also for the ethereum community because 00:25:27.559 --> 00:25:29.029 align:start position:0% also for the ethereum community because now<00:25:27.679> you<00:25:27.760> could<00:25:27.880> run<00:25:28.039> the<00:25:28.080> same<00:25:28.440> applications 00:25:29.029 --> 00:25:29.039 align:start position:0% now you could run the same applications 00:25:29.039 --> 00:25:32.799 align:start position:0% now you could run the same applications and<00:25:29.240> and<00:25:29.360> Target<00:25:29.799> both<00:25:30.000> audiences