WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:19.550 align:start position:0% [Music] 00:00:19.550 --> 00:00:19.560 align:start position:0% 00:00:19.560 --> 00:00:24.230 align:start position:0% uh<00:00:20.560> show<00:00:20.880> too<00:00:21.039> many<00:00:21.519> slides<00:00:22.680> um<00:00:23.680> hi<00:00:23.880> how<00:00:24.039> we 00:00:24.230 --> 00:00:24.240 align:start position:0% uh show too many slides um hi how we 00:00:24.240 --> 00:00:29.429 align:start position:0% uh show too many slides um hi how we guys<00:00:24.840> doing<00:00:25.880> so<00:00:26.880> I'm<00:00:27.199> ta<00:00:28.199> AKA<00:00:28.640> fake<00:00:28.960> death<00:00:29.320> I'm 00:00:29.429 --> 00:00:29.439 align:start position:0% guys doing so I'm ta AKA fake death I'm 00:00:29.439 --> 00:00:32.350 align:start position:0% guys doing so I'm ta AKA fake death I'm a<00:00:29.599> ZKA<00:00:30.000> engineer<00:00:30.400> from<00:00:30.599> chroma<00:00:31.560> so<00:00:31.759> today<00:00:32.279> I 00:00:32.350 --> 00:00:32.360 align:start position:0% a ZKA engineer from chroma so today I 00:00:32.360 --> 00:00:36.350 align:start position:0% a ZKA engineer from chroma so today I would<00:00:32.520> like<00:00:32.680> to<00:00:32.880> share<00:00:34.079> our<00:00:35.079> experience<00:00:36.000> of 00:00:36.350 --> 00:00:36.360 align:start position:0% would like to share our experience of 00:00:36.360 --> 00:00:39.150 align:start position:0% would like to share our experience of advancing<00:00:36.920> all<00:00:37.120> P<00:00:37.320> tag<00:00:37.559> into<00:00:37.760> zare<00:00:38.160> rollup<00:00:39.000> so 00:00:39.150 --> 00:00:39.160 align:start position:0% advancing all P tag into zare rollup so 00:00:39.160 --> 00:00:41.630 align:start position:0% advancing all P tag into zare rollup so we're<00:00:39.360> trying<00:00:39.600> to<00:00:39.840> enhance<00:00:40.840> efficiency<00:00:41.440> and 00:00:41.630 --> 00:00:41.640 align:start position:0% we're trying to enhance efficiency and 00:00:41.640 --> 00:00:44.630 align:start position:0% we're trying to enhance efficiency and security<00:00:42.200> with<00:00:42.480> zero<00:00:42.800> knowledge 00:00:44.630 --> 00:00:44.640 align:start position:0% security with zero knowledge 00:00:44.640 --> 00:00:47.790 align:start position:0% security with zero knowledge proofs<00:00:45.640> so<00:00:46.480> for<00:00:46.719> those<00:00:46.879> of<00:00:47.039> you<00:00:47.199> who<00:00:47.559> don't 00:00:47.790 --> 00:00:47.800 align:start position:0% proofs so for those of you who don't 00:00:47.800 --> 00:00:49.430 align:start position:0% proofs so for those of you who don't know<00:00:48.000> about<00:00:48.199> chroma<00:00:48.800> I<00:00:48.879> want<00:00:49.000> to<00:00:49.160> First 00:00:49.430 --> 00:00:49.440 align:start position:0% know about chroma I want to First 00:00:49.440 --> 00:00:52.470 align:start position:0% know about chroma I want to First celebrate<00:00:49.879> our<00:00:50.320> successes<00:00:51.320> from<00:00:51.879> last<00:00:52.120> year 00:00:52.470 --> 00:00:52.480 align:start position:0% celebrate our successes from last year 00:00:52.480 --> 00:00:53.630 align:start position:0% celebrate our successes from last year our<00:00:52.640> Mainland 00:00:53.630 --> 00:00:53.640 align:start position:0% our Mainland 00:00:53.640 --> 00:00:55.470 align:start position:0% our Mainland launch 00:00:55.470 --> 00:00:55.480 align:start position:0% launch 00:00:55.480 --> 00:00:59.270 align:start position:0% launch so<00:00:56.760> uh<00:00:57.760> uh<00:00:57.879> we<00:00:57.960> were<00:00:58.160> one<00:00:58.239> of<00:00:58.399> the<00:00:58.600> projects 00:00:59.270 --> 00:00:59.280 align:start position:0% so uh uh we were one of the projects 00:00:59.280 --> 00:01:03.069 align:start position:0% so uh uh we were one of the projects built<00:00:59.519> on<00:00:59.680> op<00:01:00.199> stack<00:01:00.760> so<00:01:01.440> we're<00:01:01.719> one<00:01:01.840> of<00:01:02.079> the 00:01:03.069 --> 00:01:03.079 align:start position:0% built on op stack so we're one of the 00:01:03.079 --> 00:01:05.630 align:start position:0% built on op stack so we're one of the first<00:01:04.040> I<00:01:04.119> mean<00:01:04.280> we're<00:01:04.519> the<00:01:04.640> very<00:01:04.839> first 00:01:05.630 --> 00:01:05.640 align:start position:0% first I mean we're the very first 00:01:05.640 --> 00:01:08.630 align:start position:0% first I mean we're the very first optimism<00:01:06.200> rollup<00:01:06.799> optimistic<00:01:07.280> rollup<00:01:08.119> with 00:01:08.630 --> 00:01:08.640 align:start position:0% optimism rollup optimistic rollup with 00:01:08.640 --> 00:01:10.749 align:start position:0% optimism rollup optimistic rollup with an<00:01:08.880> active<00:01:09.119> fault<00:01:09.400> proof<00:01:09.680> system<00:01:10.400> so<00:01:10.600> we 00:01:10.749 --> 00:01:10.759 align:start position:0% an active fault proof system so we 00:01:10.759 --> 00:01:15.429 align:start position:0% an active fault proof system so we utilize<00:01:11.280> CK<00:01:11.640> proofs<00:01:11.920> for<00:01:12.119> it<00:01:13.119> and<00:01:14.119> so<00:01:14.600> ZK 00:01:15.429 --> 00:01:15.439 align:start position:0% utilize CK proofs for it and so ZK 00:01:15.439 --> 00:01:17.990 align:start position:0% utilize CK proofs for it and so ZK enables<00:01:15.960> to<00:01:16.400> solve<00:01:16.680> some<00:01:16.960> problems<00:01:17.360> in 00:01:17.990 --> 00:01:18.000 align:start position:0% enables to solve some problems in 00:01:18.000 --> 00:01:21.149 align:start position:0% enables to solve some problems in traditional<00:01:18.439> fault<00:01:18.720> proof<00:01:19.079> systems<00:01:20.159> and 00:01:21.149 --> 00:01:21.159 align:start position:0% traditional fault proof systems and 00:01:21.159 --> 00:01:23.429 align:start position:0% traditional fault proof systems and first<00:01:21.400> we<00:01:21.600> approach<00:01:22.040> with<00:01:22.320> a<00:01:22.520> circuit<00:01:23.079> circuit 00:01:23.429 --> 00:01:23.439 align:start position:0% first we approach with a circuit circuit 00:01:23.439 --> 00:01:26.950 align:start position:0% first we approach with a circuit circuit based<00:01:23.680> implementation<00:01:24.479> of<00:01:25.200> ZK<00:01:25.600> provs<00:01:26.200> but<00:01:26.799> it 00:01:26.950 --> 00:01:26.960 align:start position:0% based implementation of ZK provs but it 00:01:26.960 --> 00:01:29.429 align:start position:0% based implementation of ZK provs but it has<00:01:27.119> a<00:01:27.360> very<00:01:27.600> very<00:01:28.040> big<00:01:28.280> issue<00:01:29.000> so<00:01:29.280> we're 00:01:29.429 --> 00:01:29.439 align:start position:0% has a very very big issue so we're 00:01:29.439 --> 00:01:31.190 align:start position:0% has a very very big issue so we're trying<00:01:29.640> to<00:01:29.920> Transit<00:01:30.280> from<00:01:30.560> circuit<00:01:30.880> based 00:01:31.190 --> 00:01:31.200 align:start position:0% trying to Transit from circuit based 00:01:31.200 --> 00:01:34.789 align:start position:0% trying to Transit from circuit based approach<00:01:31.680> to<00:01:31.880> cdk<00:01:32.240> VM<00:01:32.520> based<00:01:32.920> approach<00:01:33.920> and 00:01:34.789 --> 00:01:34.799 align:start position:0% approach to cdk VM based approach and 00:01:34.799 --> 00:01:37.270 align:start position:0% approach to cdk VM based approach and lastly<00:01:35.240> we<00:01:35.439> all<00:01:35.759> we're<00:01:36.000> also<00:01:36.399> building<00:01:36.720> a<00:01:36.920> ZK 00:01:37.270 --> 00:01:37.280 align:start position:0% lastly we all we're also building a ZK 00:01:37.280 --> 00:01:39.789 align:start position:0% lastly we all we're also building a ZK backend<00:01:37.640> library<00:01:38.600> to<00:01:38.960> push<00:01:39.200> the<00:01:39.320> boundaries 00:01:39.789 --> 00:01:39.799 align:start position:0% backend library to push the boundaries 00:01:39.799 --> 00:01:42.109 align:start position:0% backend library to push the boundaries of<00:01:40.040> proof<00:01:40.320> generation 00:01:42.109 --> 00:01:42.119 align:start position:0% of proof generation 00:01:42.119 --> 00:01:45.950 align:start position:0% of proof generation speed<00:01:43.119> so<00:01:43.439> why<00:01:43.680> ZK<00:01:44.000> fault<00:01:44.200> proofs<00:01:44.719> So<00:01:45.200> In 00:01:45.950 --> 00:01:45.960 align:start position:0% speed so why ZK fault proofs So In 00:01:45.960 --> 00:01:48.749 align:start position:0% speed so why ZK fault proofs So In traditional<00:01:46.960> uh<00:01:47.079> fault<00:01:47.360> proof<00:01:47.640> systems<00:01:48.600> it 00:01:48.749 --> 00:01:48.759 align:start position:0% traditional uh fault proof systems it 00:01:48.759 --> 00:01:52.389 align:start position:0% traditional uh fault proof systems it requires<00:01:49.920> various<00:01:50.920> of<00:01:51.240> it<00:01:51.399> requires<00:01:51.920> a<00:01:52.040> lot<00:01:52.240> of 00:01:52.389 --> 00:01:52.399 align:start position:0% requires various of it requires a lot of 00:01:52.399 --> 00:01:54.910 align:start position:0% requires various of it requires a lot of interactions<00:01:53.320> which<00:01:53.439> leads<00:01:53.719> to<00:01:54.399> high<00:01:54.600> bond 00:01:54.910 --> 00:01:54.920 align:start position:0% interactions which leads to high bond 00:01:54.920 --> 00:01:58.429 align:start position:0% interactions which leads to high bond amounts<00:01:55.719> which<00:01:56.439> decreases<00:01:57.079> the<00:01:57.360> level<00:01:57.600> of 00:01:58.429 --> 00:01:58.439 align:start position:0% amounts which decreases the level of 00:01:58.439 --> 00:02:01.230 align:start position:0% amounts which decreases the level of decentralization<00:01:59.439> so<00:01:59.920> with<00:02:00.039> ZK<00:02:00.360> fault<00:02:00.640> proofs 00:02:01.230 --> 00:02:01.240 align:start position:0% decentralization so with ZK fault proofs 00:02:01.240 --> 00:02:03.190 align:start position:0% decentralization so with ZK fault proofs we<00:02:01.360> can<00:02:01.560> just<00:02:01.840> narrow<00:02:02.200> it<00:02:02.360> down<00:02:02.479> to<00:02:02.680> a<00:02:02.920> block 00:02:03.190 --> 00:02:03.200 align:start position:0% we can just narrow it down to a block 00:02:03.200 --> 00:02:05.190 align:start position:0% we can just narrow it down to a block level<00:02:03.799> instead<00:02:04.079> of<00:02:04.280> instruction<00:02:04.719> level<00:02:05.039> which 00:02:05.190 --> 00:02:05.200 align:start position:0% level instead of instruction level which 00:02:05.200 --> 00:02:07.790 align:start position:0% level instead of instruction level which requires<00:02:05.680> much<00:02:05.840> more<00:02:06.680> much<00:02:06.920> less<00:02:07.520> uh 00:02:07.790 --> 00:02:07.800 align:start position:0% requires much more much less uh 00:02:07.800 --> 00:02:11.790 align:start position:0% requires much more much less uh interactions<00:02:08.879> so<00:02:09.879> uh<00:02:10.119> it<00:02:10.640> not<00:02:10.840> only<00:02:11.239> reduces 00:02:11.790 --> 00:02:11.800 align:start position:0% interactions so uh it not only reduces 00:02:11.800 --> 00:02:14.190 align:start position:0% interactions so uh it not only reduces the<00:02:12.080> operational<00:02:12.640> cost<00:02:12.920> itself<00:02:13.920> since 00:02:14.190 --> 00:02:14.200 align:start position:0% the operational cost itself since 00:02:14.200 --> 00:02:16.750 align:start position:0% the operational cost itself since there's<00:02:14.560> less<00:02:15.200> interaction<00:02:15.720> so<00:02:15.959> we<00:02:16.120> need<00:02:16.400> less 00:02:16.750 --> 00:02:16.760 align:start position:0% there's less interaction so we need less 00:02:16.760 --> 00:02:18.949 align:start position:0% there's less interaction so we need less computation<00:02:17.760> but<00:02:17.959> also<00:02:18.560> it<00:02:18.720> can 00:02:18.949 --> 00:02:18.959 align:start position:0% computation but also it can 00:02:18.959 --> 00:02:20.710 align:start position:0% computation but also it can significantly<00:02:19.640> reduce<00:02:20.080> the<00:02:20.280> bond 00:02:20.710 --> 00:02:20.720 align:start position:0% significantly reduce the bond 00:02:20.720 --> 00:02:23.910 align:start position:0% significantly reduce the bond requirement<00:02:21.720> so<00:02:22.280> it<00:02:22.680> it<00:02:23.000> naturally<00:02:23.400> leads<00:02:23.640> to 00:02:23.910 --> 00:02:23.920 align:start position:0% requirement so it it naturally leads to 00:02:23.920 --> 00:02:26.150 align:start position:0% requirement so it it naturally leads to better<00:02:24.160> decentralization<00:02:25.120> and<00:02:25.319> security<00:02:26.040> of 00:02:26.150 --> 00:02:26.160 align:start position:0% better decentralization and security of 00:02:26.160 --> 00:02:27.589 align:start position:0% better decentralization and security of the 00:02:27.589 --> 00:02:27.599 align:start position:0% the 00:02:27.599 --> 00:02:31.430 align:start position:0% the network<00:02:28.599> so<00:02:29.519> more<00:02:30.000> over<00:02:30.280> for<00:02:30.599> like<00:02:30.879> arbitrum 00:02:31.430 --> 00:02:31.440 align:start position:0% network so more over for like arbitrum 00:02:31.440 --> 00:02:34.470 align:start position:0% network so more over for like arbitrum spold<00:02:32.200> if<00:02:32.360> we<00:02:32.599> apply<00:02:32.920> ZK<00:02:33.400> ZK<00:02:33.800> technology<00:02:34.239> into 00:02:34.470 --> 00:02:34.480 align:start position:0% spold if we apply ZK ZK technology into 00:02:34.480 --> 00:02:37.670 align:start position:0% spold if we apply ZK ZK technology into it<00:02:35.040> we<00:02:35.200> can<00:02:35.720> we<00:02:35.840> would<00:02:36.040> be<00:02:36.200> able<00:02:36.480> to<00:02:37.000> sign 00:02:37.670 --> 00:02:37.680 align:start position:0% it we can we would be able to sign 00:02:37.680 --> 00:02:40.070 align:start position:0% it we can we would be able to sign reduce<00:02:38.640> the<00:02:38.760> bond<00:02:39.080> requirement 00:02:40.070 --> 00:02:40.080 align:start position:0% reduce the bond requirement 00:02:40.080 --> 00:02:44.110 align:start position:0% reduce the bond requirement significantly<00:02:41.080> that<00:02:41.280> is<00:02:41.720> usually<00:02:42.640> used<00:02:43.120> for 00:02:44.110 --> 00:02:44.120 align:start position:0% significantly that is usually used for 00:02:44.120 --> 00:02:48.070 align:start position:0% significantly that is usually used for uh<00:02:44.239> blocking<00:02:44.680> Cil<00:02:45.120> attacks<00:02:46.120> also<00:02:46.720> optimism<00:02:47.440> is 00:02:48.070 --> 00:02:48.080 align:start position:0% uh blocking Cil attacks also optimism is 00:02:48.080 --> 00:02:50.190 align:start position:0% uh blocking Cil attacks also optimism is uh<00:02:48.400> putting<00:02:48.680> a<00:02:48.800> lot<00:02:48.959> of<00:02:49.120> resources<00:02:49.680> into 00:02:50.190 --> 00:02:50.200 align:start position:0% uh putting a lot of resources into 00:02:50.200 --> 00:02:53.270 align:start position:0% uh putting a lot of resources into exploring<00:02:51.200> ZK<00:02:51.599> fault 00:02:53.270 --> 00:02:53.280 align:start position:0% exploring ZK fault 00:02:53.280 --> 00:02:57.030 align:start position:0% exploring ZK fault proofs<00:02:54.280> so<00:02:54.680> we<00:02:54.920> have<00:02:55.080> a<00:02:55.840> uh<00:02:56.080> announcement<00:02:56.720> that 00:02:57.030 --> 00:02:57.040 align:start position:0% proofs so we have a uh announcement that 00:02:57.040 --> 00:03:00.509 align:start position:0% proofs so we have a uh announcement that we<00:02:57.239> have<00:02:57.760> received<00:02:58.480> uh<00:02:58.760> retro<00:02:59.120> pjf<00:02:59.560> round<00:02:59.959> five 00:03:00.509 --> 00:03:00.519 align:start position:0% we have received uh retro pjf round five 00:03:00.519 --> 00:03:03.949 align:start position:0% we have received uh retro pjf round five from<00:03:00.920> optimism<00:03:01.840> to<00:03:02.319> explore<00:03:02.720> more<00:03:02.920> on<00:03:03.080> the<00:03:03.239> ZK 00:03:03.949 --> 00:03:03.959 align:start position:0% from optimism to explore more on the ZK 00:03:03.959 --> 00:03:07.350 align:start position:0% from optimism to explore more on the ZK fallproof<00:03:04.720> size<00:03:05.720> and<00:03:06.200> this<00:03:06.400> recognition<00:03:07.080> I 00:03:07.350 --> 00:03:07.360 align:start position:0% fallproof size and this recognition I 00:03:07.360 --> 00:03:12.030 align:start position:0% fallproof size and this recognition I think<00:03:08.519> uh<00:03:09.519> shows<00:03:10.319> how<00:03:10.480> much<00:03:10.720> important<00:03:11.360> and<00:03:11.879> uh 00:03:12.030 --> 00:03:12.040 align:start position:0% think uh shows how much important and uh 00:03:12.040 --> 00:03:14.430 align:start position:0% think uh shows how much important and uh possibilities<00:03:12.599> are<00:03:12.879> there<00:03:13.519> into<00:03:13.840> building<00:03:14.200> a 00:03:14.430 --> 00:03:14.440 align:start position:0% possibilities are there into building a 00:03:14.440 --> 00:03:18.270 align:start position:0% possibilities are there into building a permissionless<00:03:15.239> fa<00:03:15.560> proc<00:03:15.799> system<00:03:16.360> with 00:03:18.270 --> 00:03:18.280 align:start position:0% permissionless fa proc system with 00:03:18.280 --> 00:03:21.270 align:start position:0% permissionless fa proc system with ZK<00:03:19.280> so<00:03:19.560> we've<00:03:19.760> looked<00:03:20.040> at<00:03:20.440> like<00:03:20.799> our 00:03:21.270 --> 00:03:21.280 align:start position:0% ZK so we've looked at like our 00:03:21.280 --> 00:03:23.350 align:start position:0% ZK so we've looked at like our achievements<00:03:22.120> since<00:03:22.599> last<00:03:22.920> maintenance 00:03:23.350 --> 00:03:23.360 align:start position:0% achievements since last maintenance 00:03:23.360 --> 00:03:26.470 align:start position:0% achievements since last maintenance launch<00:03:24.239> and<00:03:24.519> now<00:03:25.159> I<00:03:25.239> would<00:03:25.400> like<00:03:25.560> to<00:03:25.879> share 00:03:26.470 --> 00:03:26.480 align:start position:0% launch and now I would like to share 00:03:26.480 --> 00:03:30.350 align:start position:0% launch and now I would like to share some<00:03:27.480> our<00:03:28.000> lessons<00:03:28.400> learns<00:03:28.879> and<00:03:29.400> challenges 00:03:30.350 --> 00:03:30.360 align:start position:0% some our lessons learns and challenges 00:03:30.360 --> 00:03:33.030 align:start position:0% some our lessons learns and challenges that<00:03:30.480> we've<00:03:30.720> experienced<00:03:31.400> for<00:03:31.920> building<00:03:32.920> uh 00:03:33.030 --> 00:03:33.040 align:start position:0% that we've experienced for building uh 00:03:33.040 --> 00:03:35.710 align:start position:0% that we've experienced for building uh CK<00:03:33.400> fallproof<00:03:33.720> systems<00:03:34.280> in<00:03:34.400> our<00:03:34.560> main 00:03:35.710 --> 00:03:35.720 align:start position:0% CK fallproof systems in our main 00:03:35.720 --> 00:03:39.390 align:start position:0% CK fallproof systems in our main net<00:03:36.799> so<00:03:37.799> the<00:03:37.959> very<00:03:38.159> important<00:03:38.640> fact<00:03:39.159> that<00:03:39.280> we 00:03:39.390 --> 00:03:39.400 align:start position:0% net so the very important fact that we 00:03:39.400 --> 00:03:41.309 align:start position:0% net so the very important fact that we learned<00:03:40.080> is<00:03:40.280> that<00:03:40.480> the<00:03:40.599> circuit<00:03:41.000> based 00:03:41.309 --> 00:03:41.319 align:start position:0% learned is that the circuit based 00:03:41.319 --> 00:03:45.470 align:start position:0% learned is that the circuit based approach<00:03:41.840> is<00:03:42.400> just<00:03:42.840> just<00:03:43.000> not<00:03:43.480> sustainable<00:03:44.480> so 00:03:45.470 --> 00:03:45.480 align:start position:0% approach is just just not sustainable so 00:03:45.480 --> 00:03:47.949 align:start position:0% approach is just just not sustainable so we<00:03:45.760> currently<00:03:46.200> have<00:03:46.519> about<00:03:46.799> like<00:03:47.040> 100k<00:03:47.439> L<00:03:47.680> of 00:03:47.949 --> 00:03:47.959 align:start position:0% we currently have about like 100k L of 00:03:47.959 --> 00:03:51.550 align:start position:0% we currently have about like 100k L of code<00:03:48.879> which<00:03:49.360> are<00:03:49.599> for<00:03:50.040> custom<00:03:50.360> circuits<00:03:51.159> so<00:03:51.400> we 00:03:51.550 --> 00:03:51.560 align:start position:0% code which are for custom circuits so we 00:03:51.560 --> 00:03:53.390 align:start position:0% code which are for custom circuits so we have<00:03:51.640> to<00:03:51.799> write<00:03:51.959> it<00:03:52.079> in<00:03:52.239> a<00:03:52.439> circuit<00:03:52.840> language 00:03:53.390 --> 00:03:53.400 align:start position:0% have to write it in a circuit language 00:03:53.400 --> 00:03:57.309 align:start position:0% have to write it in a circuit language like<00:03:53.920> plish<00:03:54.920> and<00:03:55.120> it's<00:03:55.319> very<00:03:55.519> very<00:03:55.720> hard<00:03:56.079> to<00:03:57.079> uh 00:03:57.309 --> 00:03:57.319 align:start position:0% like plish and it's very very hard to uh 00:03:57.319 --> 00:04:01.309 align:start position:0% like plish and it's very very hard to uh write<00:03:58.040> and<00:03:58.599> debug<00:03:59.360> and<00:03:59.799> verify<00:04:00.360> so<00:04:01.079> what<00:04:01.200> we're 00:04:01.309 --> 00:04:01.319 align:start position:0% write and debug and verify so what we're 00:04:01.319 --> 00:04:03.789 align:start position:0% write and debug and verify so what we're trying<00:04:01.519> to<00:04:01.680> do<00:04:01.920> is<00:04:02.360> check<00:04:02.680> the<00:04:03.000> Integrity<00:04:03.560> of 00:04:03.789 --> 00:04:03.799 align:start position:0% trying to do is check the Integrity of 00:04:03.799 --> 00:04:07.149 align:start position:0% trying to do is check the Integrity of evm<00:04:04.280> St<00:04:04.640> State<00:04:05.040> transition<00:04:05.560> function<00:04:06.120> but<00:04:06.959> we 00:04:07.149 --> 00:04:07.159 align:start position:0% evm St State transition function but we 00:04:07.159 --> 00:04:10.710 align:start position:0% evm St State transition function but we have<00:04:07.360> we<00:04:07.480> need<00:04:07.920> like<00:04:08.480> several<00:04:09.480> uh<00:04:10.239> specific 00:04:10.710 --> 00:04:10.720 align:start position:0% have we need like several uh specific 00:04:10.720 --> 00:04:12.630 align:start position:0% have we need like several uh specific custom<00:04:11.079> circuits<00:04:11.760> written<00:04:12.120> in<00:04:12.280> circuit 00:04:12.630 --> 00:04:12.640 align:start position:0% custom circuits written in circuit 00:04:12.640 --> 00:04:15.149 align:start position:0% custom circuits written in circuit languages<00:04:13.159> to<00:04:13.879> verify<00:04:14.480> that<00:04:14.680> the<00:04:14.879> state 00:04:15.149 --> 00:04:15.159 align:start position:0% languages to verify that the state 00:04:15.159 --> 00:04:17.189 align:start position:0% languages to verify that the state transition<00:04:15.599> function<00:04:16.040> given<00:04:16.280> the<00:04:16.440> input<00:04:17.040> is 00:04:17.189 --> 00:04:17.199 align:start position:0% transition function given the input is 00:04:17.199 --> 00:04:22.069 align:start position:0% transition function given the input is done<00:04:17.840> correctly<00:04:19.000> and<00:04:20.000> back<00:04:20.120> in<00:04:20.479> 2022<00:04:21.479> uh<00:04:21.639> vital 00:04:22.069 --> 00:04:22.079 align:start position:0% done correctly and back in 2022 uh vital 00:04:22.079 --> 00:04:24.469 align:start position:0% done correctly and back in 2022 uh vital given<00:04:22.320> mentioned<00:04:23.120> at<00:04:23.240> the<00:04:23.479> time<00:04:23.880> there<00:04:23.960> was<00:04:24.160> no 00:04:24.469 --> 00:04:24.479 align:start position:0% given mentioned at the time there was no 00:04:24.479 --> 00:04:26.950 align:start position:0% given mentioned at the time there was no like<00:04:25.040> uh<00:04:25.199> production<00:04:25.639> ready<00:04:25.960> zkm<00:04:26.639> circuit 00:04:26.950 --> 00:04:26.960 align:start position:0% like uh production ready zkm circuit 00:04:26.960 --> 00:04:29.430 align:start position:0% like uh production ready zkm circuit codes<00:04:27.720> but<00:04:27.919> they<00:04:28.080> had<00:04:28.199> a<00:04:28.320> POC<00:04:28.800> version<00:04:29.080> of<00:04:29.199> it 00:04:29.430 --> 00:04:29.440 align:start position:0% codes but they had a POC version of it 00:04:29.440 --> 00:04:32.749 align:start position:0% codes but they had a POC version of it in<00:04:29.840> ethereum's<00:04:30.440> psse<00:04:31.400> and<00:04:31.680> back<00:04:31.880> in<00:04:32.000> the<00:04:32.160> days 00:04:32.749 --> 00:04:32.759 align:start position:0% in ethereum's psse and back in the days 00:04:32.759 --> 00:04:36.710 align:start position:0% in ethereum's psse and back in the days it<00:04:32.840> was<00:04:33.120> like<00:04:33.880> 35k<00:04:34.880> lines<00:04:35.120> of<00:04:35.280> code<00:04:36.039> but<00:04:36.440> even 00:04:36.710 --> 00:04:36.720 align:start position:0% it was like 35k lines of code but even 00:04:36.720 --> 00:04:38.510 align:start position:0% it was like 35k lines of code but even vital<00:04:37.120> mentioned<00:04:37.479> that<00:04:37.800> it's<00:04:38.000> never<00:04:38.199> going<00:04:38.360> to 00:04:38.510 --> 00:04:38.520 align:start position:0% vital mentioned that it's never going to 00:04:38.520 --> 00:04:40.510 align:start position:0% vital mentioned that it's never going to bug<00:04:38.759> free<00:04:39.199> for<00:04:39.360> a<00:04:39.479> long<00:04:39.680> long<00:04:39.919> time<00:04:40.199> so<00:04:40.360> it's 00:04:40.510 --> 00:04:40.520 align:start position:0% bug free for a long long time so it's 00:04:40.520 --> 00:04:42.909 align:start position:0% bug free for a long long time so it's very<00:04:40.720> prone<00:04:40.960> to<00:04:41.080> errors<00:04:41.960> very<00:04:42.160> prone<00:04:42.400> to<00:04:42.600> human 00:04:42.909 --> 00:04:42.919 align:start position:0% very prone to errors very prone to human 00:04:42.919 --> 00:04:46.990 align:start position:0% very prone to errors very prone to human errors<00:04:44.320> so<00:04:45.320> to<00:04:45.759> sum<00:04:46.000> up<00:04:46.520> there<00:04:46.600> are<00:04:46.800> two 00:04:46.990 --> 00:04:47.000 align:start position:0% errors so to sum up there are two 00:04:47.000 --> 00:04:49.390 align:start position:0% errors so to sum up there are two challenges<00:04:47.960> writing<00:04:48.320> the<00:04:48.440> circuit<00:04:48.840> itself<00:04:49.199> is 00:04:49.390 --> 00:04:49.400 align:start position:0% challenges writing the circuit itself is 00:04:49.400 --> 00:04:52.790 align:start position:0% challenges writing the circuit itself is tough<00:04:49.759> because<00:04:50.039> it's<00:04:50.240> hard<00:04:50.520> to<00:04:51.520> audit<00:04:52.199> and 00:04:52.790 --> 00:04:52.800 align:start position:0% tough because it's hard to audit and 00:04:52.800 --> 00:04:56.390 align:start position:0% tough because it's hard to audit and debug<00:04:53.800> and<00:04:54.039> also<00:04:55.000> since<00:04:55.400> optimism<00:04:56.160> and 00:04:56.390 --> 00:04:56.400 align:start position:0% debug and also since optimism and 00:04:56.400 --> 00:04:59.510 align:start position:0% debug and also since optimism and ethereum<00:04:57.000> keeps<00:04:57.639> keep<00:04:58.000> brings<00:04:59.000> upgrades<00:04:59.400> to 00:04:59.510 --> 00:04:59.520 align:start position:0% ethereum keeps keep brings upgrades to 00:04:59.520 --> 00:05:01.870 align:start position:0% ethereum keeps keep brings upgrades to the<00:04:59.880> main<00:05:00.120> net<00:05:00.680> to<00:05:00.880> support<00:05:01.320> like<00:05:01.479> full 00:05:01.870 --> 00:05:01.880 align:start position:0% the main net to support like full 00:05:01.880 --> 00:05:04.870 align:start position:0% the main net to support like full compatibility<00:05:02.880> we<00:05:03.039> have<00:05:03.160> to<00:05:03.479> keep<00:05:04.479> up<00:05:04.720> with 00:05:04.870 --> 00:05:04.880 align:start position:0% compatibility we have to keep up with 00:05:04.880 --> 00:05:06.830 align:start position:0% compatibility we have to keep up with the<00:05:05.080> protocol<00:05:05.479> upgrades<00:05:05.919> they're<00:05:06.160> making 00:05:06.830 --> 00:05:06.840 align:start position:0% the protocol upgrades they're making 00:05:06.840 --> 00:05:08.189 align:start position:0% the protocol upgrades they're making which<00:05:07.000> means<00:05:07.240> that<00:05:07.360> we<00:05:07.479> have<00:05:07.600> to<00:05:07.759> modify 00:05:08.189 --> 00:05:08.199 align:start position:0% which means that we have to modify 00:05:08.199 --> 00:05:10.790 align:start position:0% which means that we have to modify circuits<00:05:08.720> again<00:05:08.919> and<00:05:09.160> again<00:05:09.759> every<00:05:10.000> time<00:05:10.280> the 00:05:10.790 --> 00:05:10.800 align:start position:0% circuits again and again every time the 00:05:10.800 --> 00:05:14.189 align:start position:0% circuits again and again every time the upgrades<00:05:11.280> come<00:05:11.440> up<00:05:12.320> and<00:05:12.960> this<00:05:13.080> could<00:05:13.240> lead<00:05:13.479> to 00:05:14.189 --> 00:05:14.199 align:start position:0% upgrades come up and this could lead to 00:05:14.199 --> 00:05:16.710 align:start position:0% upgrades come up and this could lead to like<00:05:14.520> possibly<00:05:15.080> if<00:05:15.160> we<00:05:15.320> make<00:05:15.479> more<00:05:15.840> modifies 00:05:16.710 --> 00:05:16.720 align:start position:0% like possibly if we make more modifies 00:05:16.720 --> 00:05:18.390 align:start position:0% like possibly if we make more modifies modifications<00:05:17.479> then<00:05:17.639> there<00:05:17.759> will<00:05:17.880> be 00:05:18.390 --> 00:05:18.400 align:start position:0% modifications then there will be 00:05:18.400 --> 00:05:20.830 align:start position:0% modifications then there will be possibility<00:05:18.840> of<00:05:19.000> more<00:05:19.160> errors<00:05:19.919> which<00:05:20.080> would 00:05:20.830 --> 00:05:20.840 align:start position:0% possibility of more errors which would 00:05:20.840 --> 00:05:23.990 align:start position:0% possibility of more errors which would like<00:05:21.120> harm<00:05:21.360> our<00:05:21.600> security<00:05:22.240> of<00:05:22.400> our 00:05:23.990 --> 00:05:24.000 align:start position:0% like harm our security of our 00:05:24.000 --> 00:05:27.150 align:start position:0% like harm our security of our maintenance<00:05:25.000> so<00:05:25.400> we<00:05:25.520> need<00:05:25.680> a<00:05:25.840> better<00:05:26.160> approach 00:05:27.150 --> 00:05:27.160 align:start position:0% maintenance so we need a better approach 00:05:27.160 --> 00:05:29.990 align:start position:0% maintenance so we need a better approach so<00:05:27.600> now<00:05:28.000> we're<00:05:28.240> trying<00:05:28.440> to<00:05:28.639> take<00:05:29.000> a<00:05:29.280> ZK<00:05:29.800> VM 00:05:29.990 --> 00:05:30.000 align:start position:0% so now we're trying to take a ZK VM 00:05:30.000 --> 00:05:33.790 align:start position:0% so now we're trying to take a ZK VM based<00:05:30.280> approach<00:05:31.080> because<00:05:31.720> ZK<00:05:32.319> VMS<00:05:33.319> can<00:05:33.639> give 00:05:33.790 --> 00:05:33.800 align:start position:0% based approach because ZK VMS can give 00:05:33.800 --> 00:05:36.870 align:start position:0% based approach because ZK VMS can give us<00:05:34.280> generality<00:05:35.120> and<00:05:35.680> auditability<00:05:36.680> what<00:05:36.759> it 00:05:36.870 --> 00:05:36.880 align:start position:0% us generality and auditability what it 00:05:36.880 --> 00:05:39.189 align:start position:0% us generality and auditability what it means<00:05:37.199> is<00:05:37.880> as<00:05:38.000> I<00:05:38.120> mentioned<00:05:38.639> in<00:05:38.759> a<00:05:38.919> circuit 00:05:39.189 --> 00:05:39.199 align:start position:0% means is as I mentioned in a circuit 00:05:39.199 --> 00:05:41.749 align:start position:0% means is as I mentioned in a circuit based<00:05:39.520> approach<00:05:39.960> we<00:05:40.080> need<00:05:40.240> to<00:05:40.400> write<00:05:40.919> circuits 00:05:41.749 --> 00:05:41.759 align:start position:0% based approach we need to write circuits 00:05:41.759 --> 00:05:44.309 align:start position:0% based approach we need to write circuits in<00:05:42.280> a<00:05:42.400> circuit<00:05:42.759> language<00:05:43.120> like<00:05:43.280> plish<00:05:44.199> which 00:05:44.309 --> 00:05:44.319 align:start position:0% in a circuit language like plish which 00:05:44.319 --> 00:05:45.830 align:start position:0% in a circuit language like plish which is<00:05:44.639> very 00:05:45.830 --> 00:05:45.840 align:start position:0% is very 00:05:45.840 --> 00:05:48.469 align:start position:0% is very unfamiliar<00:05:46.840> and<00:05:47.600> because<00:05:47.840> of<00:05:48.080> that<00:05:48.360> the 00:05:48.469 --> 00:05:48.479 align:start position:0% unfamiliar and because of that the 00:05:48.479 --> 00:05:50.270 align:start position:0% unfamiliar and because of that the Auditors<00:05:48.919> will<00:05:49.160> have<00:05:49.400> also<00:05:49.639> have<00:05:49.759> a<00:05:49.880> hard<00:05:50.120> time 00:05:50.270 --> 00:05:50.280 align:start position:0% Auditors will have also have a hard time 00:05:50.280 --> 00:05:54.670 align:start position:0% Auditors will have also have a hard time auditing<00:05:50.960> and<00:05:51.319> even<00:05:51.800> us<00:05:52.120> can't<00:05:53.199> really<00:05:54.199> verify 00:05:54.670 --> 00:05:54.680 align:start position:0% auditing and even us can't really verify 00:05:54.680 --> 00:05:57.590 align:start position:0% auditing and even us can't really verify well<00:05:54.919> that<00:05:55.120> our<00:05:55.400> code<00:05:55.639> is<00:05:55.800> written<00:05:56.440> well<00:05:57.440> but 00:05:57.590 --> 00:05:57.600 align:start position:0% well that our code is written well but 00:05:57.600 --> 00:06:01.029 align:start position:0% well that our code is written well but ZK<00:05:57.960> VMS<00:05:58.440> allow<00:05:58.840> us<00:05:59.680> like<00:05:59.840> flexibility<00:06:00.639> we<00:06:00.759> can 00:06:01.029 --> 00:06:01.039 align:start position:0% ZK VMS allow us like flexibility we can 00:06:01.039 --> 00:06:03.870 align:start position:0% ZK VMS allow us like flexibility we can write<00:06:01.400> any<00:06:02.319> program<00:06:02.680> that<00:06:02.800> we<00:06:02.880> want<00:06:03.039> to<00:06:03.240> verify 00:06:03.870 --> 00:06:03.880 align:start position:0% write any program that we want to verify 00:06:03.880 --> 00:06:07.350 align:start position:0% write any program that we want to verify the<00:06:04.039> computation<00:06:04.840> in<00:06:05.039> Rust<00:06:06.039> and<00:06:07.039> since<00:06:07.240> it's 00:06:07.350 --> 00:06:07.360 align:start position:0% the computation in Rust and since it's 00:06:07.360 --> 00:06:09.710 align:start position:0% the computation in Rust and since it's written<00:06:07.639> in<00:06:07.800> Rust<00:06:08.280> it's<00:06:08.520> very<00:06:08.759> very<00:06:09.199> better<00:06:09.479> to 00:06:09.710 --> 00:06:09.720 align:start position:0% written in Rust it's very very better to 00:06:09.720 --> 00:06:12.230 align:start position:0% written in Rust it's very very better to audit<00:06:10.080> and 00:06:12.230 --> 00:06:12.240 align:start position:0% audit and 00:06:12.240 --> 00:06:15.950 align:start position:0% audit and debug<00:06:13.240> so<00:06:13.680> now<00:06:13.960> I<00:06:14.039> would<00:06:14.199> like<00:06:14.599> to<00:06:15.599> dive<00:06:15.800> in 00:06:15.950 --> 00:06:15.960 align:start position:0% debug so now I would like to dive in 00:06:15.960 --> 00:06:19.150 align:start position:0% debug so now I would like to dive in more<00:06:16.160> to<00:06:16.759> ZK<00:06:17.199> VM<00:06:17.599> area<00:06:18.160> so<00:06:18.520> how<00:06:18.680> we're<00:06:18.919> trying 00:06:19.150 --> 00:06:19.160 align:start position:0% more to ZK VM area so how we're trying 00:06:19.160 --> 00:06:22.830 align:start position:0% more to ZK VM area so how we're trying to<00:06:19.639> move<00:06:19.880> on<00:06:20.160> from<00:06:20.479> circuits<00:06:21.080> to<00:06:21.240> ZK 00:06:22.830 --> 00:06:22.840 align:start position:0% to move on from circuits to ZK 00:06:22.840 --> 00:06:26.270 align:start position:0% to move on from circuits to ZK VMS<00:06:23.840> so<00:06:24.160> as<00:06:24.240> I<00:06:24.400> mentioned<00:06:24.800> ZK<00:06:25.199> VMS<00:06:25.520> can<00:06:25.759> provide 00:06:26.270 --> 00:06:26.280 align:start position:0% VMS so as I mentioned ZK VMS can provide 00:06:26.280 --> 00:06:28.469 align:start position:0% VMS so as I mentioned ZK VMS can provide a<00:06:26.520> general<00:06:26.960> purpose<00:06:27.319> environment<00:06:27.880> for 00:06:28.469 --> 00:06:28.479 align:start position:0% a general purpose environment for 00:06:28.479 --> 00:06:30.790 align:start position:0% a general purpose environment for verifiable<00:06:29.120> computation 00:06:30.790 --> 00:06:30.800 align:start position:0% verifiable computation 00:06:30.800 --> 00:06:33.710 align:start position:0% verifiable computation so<00:06:31.800> uh<00:06:32.280> what<00:06:32.360> it<00:06:32.479> means<00:06:32.800> is<00:06:33.039> that<00:06:33.400> we<00:06:33.520> don't 00:06:33.710 --> 00:06:33.720 align:start position:0% so uh what it means is that we don't 00:06:33.720 --> 00:06:35.430 align:start position:0% so uh what it means is that we don't need<00:06:33.840> to<00:06:34.000> implement<00:06:34.319> circuits<00:06:34.720> anymore<00:06:35.319> we 00:06:35.430 --> 00:06:35.440 align:start position:0% need to implement circuits anymore we 00:06:35.440 --> 00:06:39.950 align:start position:0% need to implement circuits anymore we can<00:06:35.680> just<00:06:35.919> write<00:06:36.319> rust<00:06:36.759> program<00:06:37.759> and<00:06:38.680> ckvm<00:06:39.440> can 00:06:39.950 --> 00:06:39.960 align:start position:0% can just write rust program and ckvm can 00:06:39.960 --> 00:06:42.589 align:start position:0% can just write rust program and ckvm can basically<00:06:40.960> execute<00:06:41.319> the<00:06:41.520> program<00:06:42.000> and<00:06:42.240> give<00:06:42.400> a 00:06:42.589 --> 00:06:42.599 align:start position:0% basically execute the program and give a 00:06:42.599 --> 00:06:44.990 align:start position:0% basically execute the program and give a proof<00:06:43.319> which<00:06:43.479> proves<00:06:43.880> that<00:06:44.199> the<00:06:44.360> computation 00:06:44.990 --> 00:06:45.000 align:start position:0% proof which proves that the computation 00:06:45.000 --> 00:06:48.990 align:start position:0% proof which proves that the computation was<00:06:45.160> done<00:06:45.759> correctly<00:06:46.759> so<00:06:47.520> how<00:06:47.639> it<00:06:47.800> works<00:06:48.440> is 00:06:48.990 --> 00:06:49.000 align:start position:0% was done correctly so how it works is 00:06:49.000 --> 00:06:52.870 align:start position:0% was done correctly so how it works is first<00:06:50.000> the<00:06:50.960> each<00:06:51.360> zkv<00:06:51.840> M<00:06:51.960> vendor<00:06:52.319> would<00:06:52.560> have<00:06:52.680> a 00:06:52.870 --> 00:06:52.880 align:start position:0% first the each zkv M vendor would have a 00:06:52.880 --> 00:06:55.990 align:start position:0% first the each zkv M vendor would have a compiler<00:06:53.280> tool<00:06:53.560> chain<00:06:53.919> that<00:06:54.039> I<00:06:54.199> can<00:06:55.000> compile<00:06:55.759> a 00:06:55.990 --> 00:06:56.000 align:start position:0% compiler tool chain that I can compile a 00:06:56.000 --> 00:06:58.830 align:start position:0% compiler tool chain that I can compile a rust<00:06:56.440> program<00:06:56.840> into<00:06:57.639> let's<00:06:57.840> say<00:06:58.240> if<00:06:58.360> it's 00:06:58.830 --> 00:06:58.840 align:start position:0% rust program into let's say if it's 00:06:58.840 --> 00:07:00.029 align:start position:0% rust program into let's say if it's based<00:06:59.080> on<00:06:59.160> risk 00:07:00.029 --> 00:07:00.039 align:start position:0% based on risk 00:07:00.039 --> 00:07:02.150 align:start position:0% based on risk it<00:07:00.120> would<00:07:00.840> turn<00:07:01.080> into<00:07:01.240> a<00:07:01.360> machine<00:07:01.680> code<00:07:01.960> based 00:07:02.150 --> 00:07:02.160 align:start position:0% it would turn into a machine code based 00:07:02.160 --> 00:07:05.150 align:start position:0% it would turn into a machine code based on<00:07:02.319> risk<00:07:02.599> 5<00:07:03.280> and<00:07:03.440> then<00:07:03.720> inside<00:07:03.960> of<00:07:04.120> ZK<00:07:04.440> VM 00:07:05.150 --> 00:07:05.160 align:start position:0% on risk 5 and then inside of ZK VM 00:07:05.160 --> 00:07:07.670 align:start position:0% on risk 5 and then inside of ZK VM there's<00:07:05.360> an<00:07:05.560> Executor<00:07:06.520> which<00:07:06.879> executes<00:07:07.400> the 00:07:07.670 --> 00:07:07.680 align:start position:0% there's an Executor which executes the 00:07:07.680 --> 00:07:09.909 align:start position:0% there's an Executor which executes the program<00:07:08.360> and<00:07:08.560> generates<00:07:09.280> what's<00:07:09.520> called<00:07:09.759> an 00:07:09.909 --> 00:07:09.919 align:start position:0% program and generates what's called an 00:07:09.919 --> 00:07:13.510 align:start position:0% program and generates what's called an execution<00:07:10.560> Trace<00:07:11.560> execution<00:07:12.000> Trace<00:07:12.639> is 00:07:13.510 --> 00:07:13.520 align:start position:0% execution Trace execution Trace is 00:07:13.520 --> 00:07:17.510 align:start position:0% execution Trace execution Trace is basically<00:07:14.479> a<00:07:14.759> polinomial<00:07:15.759> Bound<00:07:16.160> by<00:07:17.039> some 00:07:17.510 --> 00:07:17.520 align:start position:0% basically a polinomial Bound by some 00:07:17.520 --> 00:07:20.070 align:start position:0% basically a polinomial Bound by some constraints<00:07:18.520> so<00:07:19.160> back<00:07:19.400> then<00:07:19.639> we<00:07:19.840> have<00:07:20.000> we 00:07:20.070 --> 00:07:20.080 align:start position:0% constraints so back then we have we 00:07:20.080 --> 00:07:22.909 align:start position:0% constraints so back then we have we would<00:07:20.240> have<00:07:20.360> to<00:07:20.520> write<00:07:20.879> like<00:07:21.039> circuits<00:07:22.039> to 00:07:22.909 --> 00:07:22.919 align:start position:0% would have to write like circuits to 00:07:22.919 --> 00:07:24.909 align:start position:0% would have to write like circuits to represent<00:07:23.720> some<00:07:23.919> input<00:07:24.280> data<00:07:24.560> into<00:07:24.800> a 00:07:24.909 --> 00:07:24.919 align:start position:0% represent some input data into a 00:07:24.919 --> 00:07:27.230 align:start position:0% represent some input data into a polinomial<00:07:25.879> and<00:07:26.039> then<00:07:26.479> have<00:07:26.639> constraints<00:07:27.080> for 00:07:27.230 --> 00:07:27.240 align:start position:0% polinomial and then have constraints for 00:07:27.240 --> 00:07:30.469 align:start position:0% polinomial and then have constraints for it<00:07:28.080> but<00:07:28.479> now<00:07:28.759> zkm<00:07:29.520> circuits<00:07:29.919> could<00:07:30.120> handle 00:07:30.469 --> 00:07:30.479 align:start position:0% it but now zkm circuits could handle 00:07:30.479 --> 00:07:32.869 align:start position:0% it but now zkm circuits could handle that<00:07:31.160> so<00:07:31.520> now<00:07:31.720> we<00:07:31.800> can<00:07:31.960> just<00:07:32.120> write<00:07:32.319> rust<00:07:32.639> code 00:07:32.869 --> 00:07:32.879 align:start position:0% that so now we can just write rust code 00:07:32.879 --> 00:07:33.830 align:start position:0% that so now we can just write rust code there's<00:07:33.080> more 00:07:33.830 --> 00:07:33.840 align:start position:0% there's more 00:07:33.840 --> 00:07:35.990 align:start position:0% there's more flexibility<00:07:34.840> and<00:07:35.000> then<00:07:35.440> in<00:07:35.560> the<00:07:35.680> proving 00:07:35.990 --> 00:07:36.000 align:start position:0% flexibility and then in the proving 00:07:36.000 --> 00:07:39.309 align:start position:0% flexibility and then in the proving stage<00:07:36.440> where<00:07:37.039> the<00:07:37.560> ZK<00:07:37.919> VM<00:07:38.240> gives<00:07:38.440> a<00:07:38.680> proof 00:07:39.309 --> 00:07:39.319 align:start position:0% stage where the ZK VM gives a proof 00:07:39.319 --> 00:07:41.589 align:start position:0% stage where the ZK VM gives a proof based<00:07:39.520> on<00:07:39.639> the<00:07:39.800> execution<00:07:40.280> trace<00:07:41.199> it<00:07:41.280> would 00:07:41.589 --> 00:07:41.599 align:start position:0% based on the execution trace it would 00:07:41.599 --> 00:07:44.710 align:start position:0% based on the execution trace it would commit<00:07:41.879> to<00:07:42.000> the<00:07:42.120> trace<00:07:42.520> and<00:07:42.680> then<00:07:42.800> generate<00:07:43.199> a 00:07:44.710 --> 00:07:44.720 align:start position:0% commit to the trace and then generate a 00:07:44.720 --> 00:07:50.790 align:start position:0% commit to the trace and then generate a proof<00:07:45.720> so<00:07:46.440> I<00:07:46.680> have<00:07:46.879> a<00:07:47.599> like<00:07:47.960> a<00:07:48.159> summary<00:07:49.159> kind<00:07:49.800> of 00:07:50.790 --> 00:07:50.800 align:start position:0% proof so I have a like a summary kind of 00:07:50.800 --> 00:07:53.589 align:start position:0% proof so I have a like a summary kind of uh<00:07:51.039> picture<00:07:51.680> that<00:07:51.879> we<00:07:52.039> can<00:07:52.440> compare<00:07:53.120> like<00:07:53.400> how 00:07:53.589 --> 00:07:53.599 align:start position:0% uh picture that we can compare like how 00:07:53.599 --> 00:07:55.430 align:start position:0% uh picture that we can compare like how it's<00:07:53.840> different<00:07:54.520> so<00:07:54.720> the<00:07:54.840> colored<00:07:55.159> green 00:07:55.430 --> 00:07:55.440 align:start position:0% it's different so the colored green 00:07:55.440 --> 00:07:57.830 align:start position:0% it's different so the colored green parts<00:07:55.720> are<00:07:56.000> the<00:07:56.520> code<00:07:57.000> that<00:07:57.199> we<00:07:57.400> used<00:07:57.680> to 00:07:57.830 --> 00:07:57.840 align:start position:0% parts are the code that we used to 00:07:57.840 --> 00:07:59.990 align:start position:0% parts are the code that we used to maintain<00:07:58.400> and<00:07:58.560> we<00:07:58.680> have<00:07:58.840> to<00:07:58.960> maintain 00:07:59.990 --> 00:08:00.000 align:start position:0% maintain and we have to maintain 00:08:00.000 --> 00:08:02.990 align:start position:0% maintain and we have to maintain so<00:08:01.000> back<00:08:01.240> then<00:08:01.520> we<00:08:01.639> would<00:08:01.840> have<00:08:01.960> to<00:08:02.159> maintain 00:08:02.990 --> 00:08:03.000 align:start position:0% so back then we would have to maintain 00:08:03.000 --> 00:08:06.149 align:start position:0% so back then we would have to maintain like<00:08:03.240> zkv<00:08:03.960> ZK<00:08:04.360> evm<00:08:04.800> circuits<00:08:05.319> written<00:08:05.720> in 00:08:06.149 --> 00:08:06.159 align:start position:0% like zkv ZK evm circuits written in 00:08:06.159 --> 00:08:09.189 align:start position:0% like zkv ZK evm circuits written in plish<00:08:07.159> so<00:08:07.680> there<00:08:07.800> would<00:08:07.960> be<00:08:08.120> like<00:08:08.319> evm<00:08:08.759> circuit 00:08:09.189 --> 00:08:09.199 align:start position:0% plish so there would be like evm circuit 00:08:09.199 --> 00:08:11.629 align:start position:0% plish so there would be like evm circuit RP<00:08:09.720> circuit<00:08:10.199> MPT<00:08:10.680> circuit<00:08:11.000> and<00:08:11.159> transaction 00:08:11.629 --> 00:08:11.639 align:start position:0% RP circuit MPT circuit and transaction 00:08:11.639 --> 00:08:14.589 align:start position:0% RP circuit MPT circuit and transaction circuit<00:08:12.479> which<00:08:12.759> could<00:08:13.759> uh<00:08:14.080> which<00:08:14.280> kind<00:08:14.400> of 00:08:14.589 --> 00:08:14.599 align:start position:0% circuit which could uh which kind of 00:08:14.599 --> 00:08:17.629 align:start position:0% circuit which could uh which kind of replicates<00:08:15.240> the<00:08:15.800> behavior<00:08:16.240> of<00:08:16.440> evm<00:08:17.360> so<00:08:17.560> it 00:08:17.629 --> 00:08:17.639 align:start position:0% replicates the behavior of evm so it 00:08:17.639 --> 00:08:20.909 align:start position:0% replicates the behavior of evm so it will<00:08:17.840> verify<00:08:18.240> the<00:08:18.400> logic<00:08:18.919> if<00:08:19.479> the<00:08:20.479> let's<00:08:20.680> say 00:08:20.909 --> 00:08:20.919 align:start position:0% will verify the logic if the let's say 00:08:20.919 --> 00:08:24.189 align:start position:0% will verify the logic if the let's say the<00:08:21.159> transaction<00:08:21.840> body<00:08:22.520> and<00:08:22.840> like<00:08:23.280> transtion 00:08:24.189 --> 00:08:24.199 align:start position:0% the transaction body and like transtion 00:08:24.199 --> 00:08:25.749 align:start position:0% the transaction body and like transtion I<00:08:24.240> mean<00:08:24.440> like<00:08:24.560> the<00:08:24.680> block<00:08:24.960> header<00:08:25.199> and<00:08:25.360> block 00:08:25.749 --> 00:08:25.759 align:start position:0% I mean like the block header and block 00:08:25.759 --> 00:08:28.469 align:start position:0% I mean like the block header and block body<00:08:26.759> comparing<00:08:27.280> with<00:08:27.639> like<00:08:27.879> hash<00:08:28.159> it<00:08:28.360> and 00:08:28.469 --> 00:08:28.479 align:start position:0% body comparing with like hash it and 00:08:28.479 --> 00:08:31.189 align:start position:0% body comparing with like hash it and then<00:08:28.639> like<00:08:28.759> compare<00:08:29.080> with<00:08:29.159> the<00:08:29.240> block<00:08:29.759> cash<00:08:30.759> uh 00:08:31.189 --> 00:08:31.199 align:start position:0% then like compare with the block cash uh 00:08:31.199 --> 00:08:33.029 align:start position:0% then like compare with the block cash uh that's<00:08:31.360> what<00:08:31.479> we<00:08:31.599> used<00:08:31.800> to<00:08:31.919> do<00:08:32.560> it's<00:08:32.719> very<00:08:32.880> very 00:08:33.029 --> 00:08:33.039 align:start position:0% that's what we used to do it's very very 00:08:33.039 --> 00:08:36.949 align:start position:0% that's what we used to do it's very very tricky<00:08:33.839> but<00:08:34.440> now<00:08:35.440> since<00:08:35.880> the<00:08:36.440> on<00:08:36.560> the<00:08:36.760> right 00:08:36.949 --> 00:08:36.959 align:start position:0% tricky but now since the on the right 00:08:36.959 --> 00:08:39.990 align:start position:0% tricky but now since the on the right side<00:08:37.159> there<00:08:37.240> are<00:08:37.479> ZK<00:08:37.760> VM<00:08:38.039> circuits<00:08:38.640> so<00:08:39.399> ZK<00:08:39.760> VM 00:08:39.990 --> 00:08:40.000 align:start position:0% side there are ZK VM circuits so ZK VM 00:08:40.000 --> 00:08:42.469 align:start position:0% side there are ZK VM circuits so ZK VM circuits<00:08:40.440> would<00:08:40.880> handle<00:08:41.279> that<00:08:41.959> and<00:08:42.120> instead 00:08:42.469 --> 00:08:42.479 align:start position:0% circuits would handle that and instead 00:08:42.479 --> 00:08:44.230 align:start position:0% circuits would handle that and instead we<00:08:42.599> would<00:08:42.800> just<00:08:42.959> write<00:08:43.279> a<00:08:43.440> blog<00:08:43.760> execution 00:08:44.230 --> 00:08:44.240 align:start position:0% we would just write a blog execution 00:08:44.240 --> 00:08:47.350 align:start position:0% we would just write a blog execution program<00:08:45.000> which<00:08:45.200> would<00:08:46.200> which<00:08:46.399> for<00:08:46.640> us<00:08:47.080> as<00:08:47.240> a 00:08:47.350 --> 00:08:47.360 align:start position:0% program which would which for us as a 00:08:47.360 --> 00:08:50.030 align:start position:0% program which would which for us as a ethereum<00:08:47.720> layer<00:08:47.959> to<00:08:48.560> we<00:08:48.680> would<00:08:49.040> derive<00:08:49.560> the 00:08:50.030 --> 00:08:50.040 align:start position:0% ethereum layer to we would derive the 00:08:50.040 --> 00:08:53.790 align:start position:0% ethereum layer to we would derive the batch<00:08:50.360> from<00:08:50.720> L1<00:08:51.320> and<00:08:51.440> then<00:08:51.640> execute<00:08:52.040> it<00:08:52.880> on<00:08:53.040> L2 00:08:53.790 --> 00:08:53.800 align:start position:0% batch from L1 and then execute it on L2 00:08:53.800 --> 00:08:55.190 align:start position:0% batch from L1 and then execute it on L2 so<00:08:54.240> that<00:08:54.360> will<00:08:54.480> be<00:08:54.600> the<00:08:54.680> program<00:08:55.000> we<00:08:55.080> were 00:08:55.190 --> 00:08:55.200 align:start position:0% so that will be the program we were 00:08:55.200 --> 00:08:57.949 align:start position:0% so that will be the program we were trying<00:08:55.360> to 00:08:57.949 --> 00:08:57.959 align:start position:0% 00:08:57.959 --> 00:08:59.949 align:start position:0% write<00:08:58.959> and 00:08:59.949 --> 00:08:59.959 align:start position:0% write and 00:08:59.959 --> 00:09:01.750 align:start position:0% write and uh<00:09:00.279> some<00:09:00.440> of<00:09:00.560> you<00:09:00.720> might<00:09:00.920> ask<00:09:01.200> like<00:09:01.360> vitalic 00:09:01.750 --> 00:09:01.760 align:start position:0% uh some of you might ask like vitalic 00:09:01.760 --> 00:09:03.710 align:start position:0% uh some of you might ask like vitalic mentioned<00:09:02.079> in<00:09:02.240> 2022<00:09:03.040> we<00:09:03.160> launched<00:09:03.440> our<00:09:03.519> main 00:09:03.710 --> 00:09:03.720 align:start position:0% mentioned in 2022 we launched our main 00:09:03.720 --> 00:09:05.949 align:start position:0% mentioned in 2022 we launched our main it<00:09:03.839> in<00:09:03.959> 2023<00:09:04.839> and<00:09:04.959> then<00:09:05.200> like<00:09:05.440> why<00:09:05.560> didn't<00:09:05.760> you 00:09:05.949 --> 00:09:05.959 align:start position:0% it in 2023 and then like why didn't you 00:09:05.959 --> 00:09:08.670 align:start position:0% it in 2023 and then like why didn't you guys<00:09:06.200> first<00:09:06.519> approach<00:09:06.959> with<00:09:07.480> ZK<00:09:07.800> VMS<00:09:08.079> at<00:09:08.279> first 00:09:08.670 --> 00:09:08.680 align:start position:0% guys first approach with ZK VMS at first 00:09:08.680 --> 00:09:10.350 align:start position:0% guys first approach with ZK VMS at first right<00:09:09.399> like<00:09:09.600> why<00:09:09.720> did<00:09:09.839> you<00:09:09.959> guys<00:09:10.120> ride 00:09:10.350 --> 00:09:10.360 align:start position:0% right like why did you guys ride 00:09:10.360 --> 00:09:12.710 align:start position:0% right like why did you guys ride circuits<00:09:10.760> and<00:09:10.880> do<00:09:11.079> all<00:09:11.279> that<00:09:11.440> hard<00:09:11.720> work 00:09:12.710 --> 00:09:12.720 align:start position:0% circuits and do all that hard work 00:09:12.720 --> 00:09:16.269 align:start position:0% circuits and do all that hard work that's<00:09:13.120> because<00:09:14.120> back<00:09:14.560> back<00:09:14.800> then<00:09:15.320> uh<00:09:15.600> ZK<00:09:15.920> VMS 00:09:16.269 --> 00:09:16.279 align:start position:0% that's because back back then uh ZK VMS 00:09:16.279 --> 00:09:19.670 align:start position:0% that's because back back then uh ZK VMS were<00:09:16.480> not<00:09:16.959> like<00:09:17.160> performant<00:09:18.279> so<00:09:19.279> since<00:09:19.560> the 00:09:19.670 --> 00:09:19.680 align:start position:0% were not like performant so since the 00:09:19.680 --> 00:09:22.310 align:start position:0% were not like performant so since the proving<00:09:20.079> time<00:09:20.320> is<00:09:20.519> long<00:09:21.399> in<00:09:21.720> in<00:09:21.920> within<00:09:22.160> the 00:09:22.310 --> 00:09:22.320 align:start position:0% proving time is long in in within the 00:09:22.320 --> 00:09:24.790 align:start position:0% proving time is long in in within the challenge<00:09:22.680> period<00:09:22.959> we<00:09:23.120> have<00:09:24.000> there<00:09:24.360> can<00:09:24.519> be 00:09:24.790 --> 00:09:24.800 align:start position:0% challenge period we have there can be 00:09:24.800 --> 00:09:25.710 align:start position:0% challenge period we have there can be possible 00:09:25.710 --> 00:09:25.720 align:start position:0% possible 00:09:25.720 --> 00:09:28.509 align:start position:0% possible volum<00:09:26.720> possible<00:09:27.200> attack<00:09:27.519> Vector<00:09:27.839> for<00:09:28.160> delay 00:09:28.509 --> 00:09:28.519 align:start position:0% volum possible attack Vector for delay 00:09:28.519 --> 00:09:31.190 align:start position:0% volum possible attack Vector for delay attacks<00:09:29.079> so<00:09:29.760> that's<00:09:29.920> one<00:09:30.040> of<00:09:30.120> the<00:09:30.279> reasons<00:09:30.800> why 00:09:31.190 --> 00:09:31.200 align:start position:0% attacks so that's one of the reasons why 00:09:31.200 --> 00:09:34.350 align:start position:0% attacks so that's one of the reasons why we<00:09:31.399> chose<00:09:32.000> a<00:09:32.200> circuit<00:09:32.519> based<00:09:32.839> approach<00:09:33.760> but 00:09:34.350 --> 00:09:34.360 align:start position:0% we chose a circuit based approach but 00:09:34.360 --> 00:09:37.990 align:start position:0% we chose a circuit based approach but now<00:09:35.360> uh<00:09:36.079> RIS<00:09:36.440> risk<00:09:36.720> zero<00:09:37.040> calls<00:09:37.279> it 00:09:37.990 --> 00:09:38.000 align:start position:0% now uh RIS risk zero calls it 00:09:38.000 --> 00:09:40.269 align:start position:0% now uh RIS risk zero calls it continuation<00:09:38.839> and<00:09:39.040> like<00:09:39.279> sp1<00:09:39.920> calls<00:09:40.120> it 00:09:40.269 --> 00:09:40.279 align:start position:0% continuation and like sp1 calls it 00:09:40.279 --> 00:09:42.470 align:start position:0% continuation and like sp1 calls it sharding<00:09:41.279> like<00:09:41.640> there<00:09:41.760> was<00:09:41.880> a<00:09:42.000> breakthrough 00:09:42.470 --> 00:09:42.480 align:start position:0% sharding like there was a breakthrough 00:09:42.480 --> 00:09:45.590 align:start position:0% sharding like there was a breakthrough called<00:09:42.720> sharding<00:09:43.760> which<00:09:44.760> with<00:09:44.959> the<00:09:45.360> full 00:09:45.590 --> 00:09:45.600 align:start position:0% called sharding which with the full 00:09:45.600 --> 00:09:47.790 align:start position:0% called sharding which with the full execution<00:09:46.040> Trace<00:09:46.480> you<00:09:46.600> can<00:09:46.839> now<00:09:47.320> divide<00:09:47.600> it 00:09:47.790 --> 00:09:47.800 align:start position:0% execution Trace you can now divide it 00:09:47.800 --> 00:09:52.030 align:start position:0% execution Trace you can now divide it into<00:09:48.800> a<00:09:49.279> a<00:09:49.440> unit<00:09:49.880> called<00:09:50.360> shards<00:09:51.120> so<00:09:51.760> it's 00:09:52.030 --> 00:09:52.040 align:start position:0% into a a unit called shards so it's 00:09:52.040 --> 00:09:53.710 align:start position:0% into a a unit called shards so it's usually<00:09:52.480> represented<00:09:53.040> in<00:09:53.200> the<00:09:53.360> number<00:09:53.600> of 00:09:53.710 --> 00:09:53.720 align:start position:0% usually represented in the number of 00:09:53.720 --> 00:09:57.550 align:start position:0% usually represented in the number of cycles<00:09:54.160> of<00:09:54.839> risk<00:09:55.160> five<00:09:55.720> so<00:09:56.120> sp1<00:09:56.839> they<00:09:57.200> kind<00:09:57.360> of 00:09:57.550 --> 00:09:57.560 align:start position:0% cycles of risk five so sp1 they kind of 00:09:57.560 --> 00:09:59.790 align:start position:0% cycles of risk five so sp1 they kind of have<00:09:57.720> an<00:09:58.079> optimal<00:09:58.480> number<00:09:58.800> of<00:09:59.040> like<00:09:59.440> two<00:09:59.680> to 00:09:59.790 --> 00:09:59.800 align:start position:0% have an optimal number of like two to 00:09:59.800 --> 00:10:03.630 align:start position:0% have an optimal number of like two to the^<00:10:00.120> of<00:10:00.200> 22<00:10:00.640> cycles<00:10:01.120> for<00:10:01.360> each<00:10:01.640> shart<00:10:02.640> and 00:10:03.630 --> 00:10:03.640 align:start position:0% the^ of 22 cycles for each shart and 00:10:03.640 --> 00:10:06.550 align:start position:0% the^ of 22 cycles for each shart and since<00:10:03.920> we<00:10:04.079> can<00:10:04.480> divide<00:10:04.720> it<00:10:04.920> into<00:10:05.360> charts<00:10:06.320> now 00:10:06.550 --> 00:10:06.560 align:start position:0% since we can divide it into charts now 00:10:06.560 --> 00:10:10.750 align:start position:0% since we can divide it into charts now we<00:10:06.720> can<00:10:07.720> uh<00:10:08.720> parall<00:10:09.680> generate<00:10:10.040> a<00:10:10.200> proof<00:10:10.519> for 00:10:10.750 --> 00:10:10.760 align:start position:0% we can uh parall generate a proof for 00:10:10.760 --> 00:10:13.350 align:start position:0% we can uh parall generate a proof for each<00:10:10.959> Shard<00:10:11.839> and<00:10:12.040> then<00:10:12.320> compress<00:10:12.680> it<00:10:12.880> later 00:10:13.350 --> 00:10:13.360 align:start position:0% each Shard and then compress it later 00:10:13.360 --> 00:10:16.790 align:start position:0% each Shard and then compress it later Into<00:10:13.600> A<00:10:13.720> Single<00:10:13.959> Shard<00:10:14.880> so<00:10:15.079> now<00:10:15.680> there's<00:10:15.920> more 00:10:16.790 --> 00:10:16.800 align:start position:0% Into A Single Shard so now there's more 00:10:16.800 --> 00:10:19.949 align:start position:0% Into A Single Shard so now there's more more<00:10:17.800> uh<00:10:18.079> upside<00:10:18.839> in<00:10:19.000> terms<00:10:19.200> of<00:10:19.320> throughput 00:10:19.949 --> 00:10:19.959 align:start position:0% more uh upside in terms of throughput 00:10:19.959 --> 00:10:22.910 align:start position:0% more uh upside in terms of throughput since<00:10:20.160> we<00:10:20.279> can<00:10:20.839> paralyze 00:10:22.910 --> 00:10:22.920 align:start position:0% since we can paralyze 00:10:22.920 --> 00:10:26.110 align:start position:0% since we can paralyze proofs<00:10:23.920> so<00:10:24.720> that's<00:10:25.079> what<00:10:25.200> we're<00:10:25.399> trying<00:10:25.680> to<00:10:25.839> do 00:10:26.110 --> 00:10:26.120 align:start position:0% proofs so that's what we're trying to do 00:10:26.120 --> 00:10:27.630 align:start position:0% proofs so that's what we're trying to do and<00:10:26.279> we're<00:10:26.519> almost<00:10:26.839> there<00:10:27.000> shipping<00:10:27.399> it<00:10:27.519> to 00:10:27.630 --> 00:10:27.640 align:start position:0% and we're almost there shipping it to 00:10:27.640 --> 00:10:30.509 align:start position:0% and we're almost there shipping it to the<00:10:27.760> main<00:10:28.000> net<00:10:28.800> and<00:10:29.079> now<00:10:29.320> now<00:10:29.399> I<00:10:29.519> want<00:10:29.640> to<00:10:30.360> like 00:10:30.509 --> 00:10:30.519 align:start position:0% the main net and now now I want to like 00:10:30.519 --> 00:10:34.069 align:start position:0% the main net and now now I want to like share<00:10:30.920> more<00:10:31.440> of<00:10:31.600> our<00:10:32.279> of<00:10:32.440> my<00:10:32.720> thought<00:10:33.240> that 00:10:34.069 --> 00:10:34.079 align:start position:0% share more of our of my thought that 00:10:34.079 --> 00:10:36.190 align:start position:0% share more of our of my thought that what<00:10:34.200> we<00:10:34.320> can<00:10:34.560> explore<00:10:35.000> more<00:10:35.200> in<00:10:35.320> the<00:10:35.440> future 00:10:36.190 --> 00:10:36.200 align:start position:0% what we can explore more in the future 00:10:36.200 --> 00:10:39.389 align:start position:0% what we can explore more in the future to<00:10:36.519> overcome<00:10:37.040> like<00:10:37.600> barriers<00:10:38.000> to<00:10:38.200> become<00:10:38.560> a 00:10:39.389 --> 00:10:39.399 align:start position:0% to overcome like barriers to become a 00:10:39.399 --> 00:10:42.509 align:start position:0% to overcome like barriers to become a from<00:10:39.639> a<00:10:39.920> optimistic<00:10:40.399> rollup<00:10:40.760> to<00:10:40.839> a<00:10:40.959> zare 00:10:42.509 --> 00:10:42.519 align:start position:0% from a optimistic rollup to a zare 00:10:42.519 --> 00:10:47.030 align:start position:0% from a optimistic rollup to a zare roll<00:10:43.600> so<00:10:44.600> my<00:10:44.800> concerns<00:10:45.399> about<00:10:45.680> zkm<00:10:46.680> based 00:10:47.030 --> 00:10:47.040 align:start position:0% roll so my concerns about zkm based 00:10:47.040 --> 00:10:50.990 align:start position:0% roll so my concerns about zkm based approach<00:10:47.440> is<00:10:47.720> since<00:10:48.360> zkm<00:10:49.200> vendor<00:10:50.200> uh<00:10:50.399> vendor 00:10:50.990 --> 00:10:51.000 align:start position:0% approach is since zkm vendor uh vendor 00:10:51.000 --> 00:10:52.550 align:start position:0% approach is since zkm vendor uh vendor business<00:10:51.320> model<00:10:51.680> is<00:10:51.839> usually<00:10:52.160> running<00:10:52.440> a 00:10:52.550 --> 00:10:52.560 align:start position:0% business model is usually running a 00:10:52.560 --> 00:10:55.110 align:start position:0% business model is usually running a prover<00:10:52.880> Network<00:10:53.600> so<00:10:54.200> they<00:10:54.360> get<00:10:54.480> a<00:10:54.639> delegated 00:10:55.110 --> 00:10:55.120 align:start position:0% prover Network so they get a delegated 00:10:55.120 --> 00:10:56.910 align:start position:0% prover Network so they get a delegated proof<00:10:55.440> and<00:10:55.519> then<00:10:55.639> they<00:10:56.120> generate<00:10:56.440> a<00:10:56.560> proof<00:10:56.800> for 00:10:56.910 --> 00:10:56.920 align:start position:0% proof and then they generate a proof for 00:10:56.920 --> 00:10:58.750 align:start position:0% proof and then they generate a proof for it<00:10:57.360> and<00:10:57.480> then<00:10:57.839> return<00:10:58.040> the<00:10:58.160> proof<00:10:58.360> to<00:10:58.519> the 00:10:58.750 --> 00:10:58.760 align:start position:0% it and then return the proof to the 00:10:58.760 --> 00:11:00.230 align:start position:0% it and then return the proof to the client 00:11:00.230 --> 00:11:00.240 align:start position:0% client 00:11:00.240 --> 00:11:02.949 align:start position:0% client but<00:11:00.959> there<00:11:01.120> might<00:11:01.279> be<00:11:01.399> a<00:11:01.560> situation<00:11:02.120> where<00:11:02.399> zkv 00:11:02.949 --> 00:11:02.959 align:start position:0% but there might be a situation where zkv 00:11:02.959 --> 00:11:06.870 align:start position:0% but there might be a situation where zkv Andover<00:11:03.639> Network<00:11:04.120> might<00:11:04.279> fail<00:11:05.200> so<00:11:06.200> uh<00:11:06.360> usually 00:11:06.870 --> 00:11:06.880 align:start position:0% Andover Network might fail so uh usually 00:11:06.880 --> 00:11:09.829 align:start position:0% Andover Network might fail so uh usually zkm<00:11:07.519> vendors<00:11:08.079> since<00:11:08.399> they've<00:11:08.720> built<00:11:09.160> their<00:11:09.440> ZK 00:11:09.829 --> 00:11:09.839 align:start position:0% zkm vendors since they've built their ZK 00:11:09.839 --> 00:11:14.710 align:start position:0% zkm vendors since they've built their ZK VM<00:11:10.279> they're<00:11:10.519> very<00:11:10.800> very<00:11:11.639> good<00:11:11.880> at<00:11:12.800> uh<00:11:13.800> like 00:11:14.710 --> 00:11:14.720 align:start position:0% VM they're very very good at uh like 00:11:14.720 --> 00:11:17.389 align:start position:0% VM they're very very good at uh like giving<00:11:14.959> a<00:11:15.160> good<00:11:15.399> performance<00:11:16.120> so<00:11:16.920> usually 00:11:17.389 --> 00:11:17.399 align:start position:0% giving a good performance so usually 00:11:17.399 --> 00:11:19.069 align:start position:0% giving a good performance so usually they<00:11:17.519> would<00:11:17.720> have<00:11:17.959> like<00:11:18.440> a<00:11:18.600> cluster<00:11:18.959> of 00:11:19.069 --> 00:11:19.079 align:start position:0% they would have like a cluster of 00:11:19.079 --> 00:11:22.430 align:start position:0% they would have like a cluster of machines<00:11:19.959> and<00:11:20.079> then<00:11:20.279> they<00:11:20.399> would<00:11:21.320> like<00:11:22.240> uh 00:11:22.430 --> 00:11:22.440 align:start position:0% machines and then they would like uh 00:11:22.440 --> 00:11:24.710 align:start position:0% machines and then they would like uh split<00:11:22.760> the<00:11:22.880> workloads<00:11:23.440> to<00:11:23.639> each<00:11:23.880> machine<00:11:24.600> and 00:11:24.710 --> 00:11:24.720 align:start position:0% split the workloads to each machine and 00:11:24.720 --> 00:11:26.629 align:start position:0% split the workloads to each machine and then<00:11:24.959> like<00:11:25.279> orchestrate<00:11:25.839> it<00:11:26.000> and<00:11:26.120> then<00:11:26.399> create 00:11:26.629 --> 00:11:26.639 align:start position:0% then like orchestrate it and then create 00:11:26.639 --> 00:11:30.629 align:start position:0% then like orchestrate it and then create a<00:11:26.800> proof<00:11:27.040> and<00:11:27.480> return<00:11:28.480> but<00:11:28.920> since<00:11:29.639> most<00:11:29.839> of<00:11:30.079> the 00:11:30.629 --> 00:11:30.639 align:start position:0% a proof and return but since most of the 00:11:30.639 --> 00:11:32.870 align:start position:0% a proof and return but since most of the such<00:11:30.920> Prov<00:11:31.320> Network<00:11:31.639> related<00:11:32.040> codes<00:11:32.399> are 00:11:32.870 --> 00:11:32.880 align:start position:0% such Prov Network related codes are 00:11:32.880 --> 00:11:36.870 align:start position:0% such Prov Network related codes are close<00:11:33.440> sourced<00:11:34.440> uh<00:11:34.639> maybe<00:11:35.600> to<00:11:36.279> handle<00:11:36.680> this 00:11:36.870 --> 00:11:36.880 align:start position:0% close sourced uh maybe to handle this 00:11:36.880 --> 00:11:39.430 align:start position:0% close sourced uh maybe to handle this kind<00:11:37.040> of<00:11:37.360> network<00:11:37.760> reliability<00:11:38.440> issue<00:11:39.279> we 00:11:39.430 --> 00:11:39.440 align:start position:0% kind of network reliability issue we 00:11:39.440 --> 00:11:42.269 align:start position:0% kind of network reliability issue we might<00:11:39.720> have<00:11:39.880> to<00:11:40.360> we<00:11:40.519> might<00:11:40.920> like<00:11:41.560> us<00:11:41.839> chroma 00:11:42.269 --> 00:11:42.279 align:start position:0% might have to we might like us chroma 00:11:42.279 --> 00:11:45.949 align:start position:0% might have to we might like us chroma might<00:11:42.480> have<00:11:42.600> to<00:11:43.519> implement<00:11:44.519> uh<00:11:44.800> a<00:11:44.959> code<00:11:45.279> to 00:11:45.949 --> 00:11:45.959 align:start position:0% might have to implement uh a code to 00:11:45.959 --> 00:11:48.470 align:start position:0% might have to implement uh a code to orchestrate<00:11:46.560> multiple<00:11:46.959> machines<00:11:47.959> so<00:11:48.200> that 00:11:48.470 --> 00:11:48.480 align:start position:0% orchestrate multiple machines so that 00:11:48.480 --> 00:11:50.590 align:start position:0% orchestrate multiple machines so that every<00:11:48.720> validators<00:11:49.360> could 00:11:50.590 --> 00:11:50.600 align:start position:0% every validators could 00:11:50.600 --> 00:11:53.949 align:start position:0% every validators could run<00:11:51.600> by<00:11:52.160> run<00:11:53.160> I'm<00:11:53.279> not<00:11:53.399> sure<00:11:53.560> if<00:11:53.680> this<00:11:53.800> is 00:11:53.949 --> 00:11:53.959 align:start position:0% run by run I'm not sure if this is 00:11:53.959 --> 00:11:55.470 align:start position:0% run by run I'm not sure if this is correct<00:11:54.320> but<00:11:54.680> they<00:11:54.839> they<00:11:54.920> might<00:11:55.120> have<00:11:55.200> to<00:11:55.320> run 00:11:55.470 --> 00:11:55.480 align:start position:0% correct but they they might have to run 00:11:55.480 --> 00:11:57.910 align:start position:0% correct but they they might have to run a<00:11:55.600> cluster<00:11:56.160> to<00:11:56.320> generate<00:11:56.639> a<00:11:56.800> proof<00:11:57.279> for<00:11:57.480> the 00:11:57.910 --> 00:11:57.920 align:start position:0% a cluster to generate a proof for the 00:11:57.920 --> 00:11:59.990 align:start position:0% a cluster to generate a proof for the network<00:11:58.920> so 00:11:59.990 --> 00:12:00.000 align:start position:0% network so 00:12:00.000 --> 00:12:03.990 align:start position:0% network so uh<00:12:00.200> another<00:12:00.800> concern<00:12:01.200> might<00:12:01.399> be<00:12:01.959> so<00:12:02.920> now<00:12:03.360> then 00:12:03.990 --> 00:12:04.000 align:start position:0% uh another concern might be so now then 00:12:04.000 --> 00:12:05.389 align:start position:0% uh another concern might be so now then now<00:12:04.200> there's<00:12:04.440> going<00:12:04.560> to<00:12:04.639> be<00:12:04.760> more<00:12:05.000> stage<00:12:05.200> one 00:12:05.389 --> 00:12:05.399 align:start position:0% now there's going to be more stage one 00:12:05.399 --> 00:12:09.069 align:start position:0% now there's going to be more stage one rule<00:12:05.639> ups<00:12:06.160> but<00:12:06.279> for<00:12:06.519> stage<00:12:06.920> two<00:12:07.920> uh<00:12:08.240> we<00:12:08.600> we<00:12:08.920> we 00:12:09.069 --> 00:12:09.079 align:start position:0% rule ups but for stage two uh we we we 00:12:09.079 --> 00:12:10.269 align:start position:0% rule ups but for stage two uh we we we only<00:12:09.320> want 00:12:10.269 --> 00:12:10.279 align:start position:0% only want 00:12:10.279 --> 00:12:13.790 align:start position:0% only want the<00:12:11.279> uh<00:12:11.440> Security<00:12:11.880> Council<00:12:12.399> to<00:12:13.279> come<00:12:13.440> in<00:12:13.600> and 00:12:13.790 --> 00:12:13.800 align:start position:0% the uh Security Council to come in and 00:12:13.800 --> 00:12:17.310 align:start position:0% the uh Security Council to come in and resolve<00:12:14.279> like<00:12:14.519> the<00:12:14.720> problem<00:12:15.399> if<00:12:16.399> the<00:12:16.519> failure 00:12:17.310 --> 00:12:17.320 align:start position:0% resolve like the problem if the failure 00:12:17.320 --> 00:12:20.750 align:start position:0% resolve like the problem if the failure is<00:12:17.680> only<00:12:17.920> onchain<00:12:18.399> provable<00:12:19.199> but<00:12:20.079> currently 00:12:20.750 --> 00:12:20.760 align:start position:0% is only onchain provable but currently 00:12:20.760 --> 00:12:23.269 align:start position:0% is only onchain provable but currently in<00:12:21.160> my<00:12:21.440> perspective<00:12:22.160> for<00:12:22.440> the<00:12:22.600> ZK<00:12:22.920> VMS 00:12:23.269 --> 00:12:23.279 align:start position:0% in my perspective for the ZK VMS 00:12:23.279 --> 00:12:25.550 align:start position:0% in my perspective for the ZK VMS currently<00:12:23.600> there's<00:12:23.839> no<00:12:24.040> way<00:12:24.199> to<00:12:25.000> make<00:12:25.399> like 00:12:25.550 --> 00:12:25.560 align:start position:0% currently there's no way to make like 00:12:25.560 --> 00:12:27.509 align:start position:0% currently there's no way to make like the<00:12:25.680> network<00:12:26.040> failure<00:12:26.800> to<00:12:26.959> be<00:12:27.079> onchain 00:12:27.509 --> 00:12:27.519 align:start position:0% the network failure to be onchain 00:12:27.519 --> 00:12:31.389 align:start position:0% the network failure to be onchain provable<00:12:28.240> so<00:12:28.480> that's<00:12:28.800> that's<00:12:28.920> enough<00:12:29.199> another 00:12:31.389 --> 00:12:31.399 align:start position:0% provable so that's that's enough another 00:12:31.399 --> 00:12:35.269 align:start position:0% provable so that's that's enough another concern<00:12:32.399> and<00:12:32.639> also<00:12:33.320> since<00:12:34.240> we<00:12:34.880> cannot 00:12:35.269 --> 00:12:35.279 align:start position:0% concern and also since we cannot 00:12:35.279 --> 00:12:37.750 align:start position:0% concern and also since we cannot Overlook<00:12:35.920> that<00:12:36.160> the<00:12:36.320> fact<00:12:36.600> that<00:12:36.760> ZK<00:12:37.199> VMS 00:12:37.750 --> 00:12:37.760 align:start position:0% Overlook that the fact that ZK VMS 00:12:37.760 --> 00:12:41.470 align:start position:0% Overlook that the fact that ZK VMS itself<00:12:38.160> might<00:12:38.360> have<00:12:38.480> a<00:12:38.959> bug<00:12:39.959> uh<00:12:40.360> so<00:12:41.199> what<00:12:41.320> I 00:12:41.470 --> 00:12:41.480 align:start position:0% itself might have a bug uh so what I 00:12:41.480 --> 00:12:44.350 align:start position:0% itself might have a bug uh so what I think<00:12:41.880> is<00:12:42.199> we<00:12:42.320> need<00:12:42.560> a<00:12:42.800> multi-pro<00:12:43.560> system<00:12:44.079> so 00:12:44.350 --> 00:12:44.360 align:start position:0% think is we need a multi-pro system so 00:12:44.360 --> 00:12:48.030 align:start position:0% think is we need a multi-pro system so that<00:12:44.800> we<00:12:44.959> can<00:12:45.199> compensate<00:12:45.680> the<00:12:45.800> bugs<00:12:46.079> for<00:12:46.440> that 00:12:48.030 --> 00:12:48.040 align:start position:0% that we can compensate the bugs for that 00:12:48.040 --> 00:12:50.750 align:start position:0% that we can compensate the bugs for that so<00:12:49.040> then<00:12:49.199> in<00:12:49.440> that<00:12:49.639> case<00:12:50.079> the<00:12:50.199> goal<00:12:50.440> would<00:12:50.600> be 00:12:50.750 --> 00:12:50.760 align:start position:0% so then in that case the goal would be 00:12:50.760 --> 00:12:52.790 align:start position:0% so then in that case the goal would be to<00:12:51.120> enhance<00:12:51.480> the<00:12:51.639> security<00:12:51.959> of<00:12:52.079> the<00:12:52.160> network 00:12:52.790 --> 00:12:52.800 align:start position:0% to enhance the security of the network 00:12:52.800 --> 00:12:54.910 align:start position:0% to enhance the security of the network but<00:12:53.360> not<00:12:53.560> much<00:12:53.760> with<00:12:53.920> the<00:12:54.079> overhead<00:12:54.639> so<00:12:54.839> we 00:12:54.910 --> 00:12:54.920 align:start position:0% but not much with the overhead so we 00:12:54.920 --> 00:12:58.389 align:start position:0% but not much with the overhead so we don't<00:12:55.120> want<00:12:55.560> like<00:12:56.560> uh<00:12:56.760> periods<00:12:57.160> to<00:12:57.240> be<00:12:57.399> longer 00:12:58.389 --> 00:12:58.399 align:start position:0% don't want like uh periods to be longer 00:12:58.399 --> 00:13:01.870 align:start position:0% don't want like uh periods to be longer so<00:12:59.399> there<00:12:59.560> might<00:12:59.760> be<00:12:59.959> like<00:13:00.440> three<00:13:01.440> types<00:13:01.680> of 00:13:01.870 --> 00:13:01.880 align:start position:0% so there might be like three types of 00:13:01.880 --> 00:13:05.150 align:start position:0% so there might be like three types of multi-prover<00:13:02.880> schemes<00:13:03.880> instead<00:13:04.240> of<00:13:04.480> like 00:13:05.150 --> 00:13:05.160 align:start position:0% multi-prover schemes instead of like 00:13:05.160 --> 00:13:08.550 align:start position:0% multi-prover schemes instead of like having<00:13:05.399> a<00:13:05.600> single<00:13:06.000> prover<00:13:06.959> so<00:13:07.320> one<00:13:08.040> I<00:13:08.160> think 00:13:08.550 --> 00:13:08.560 align:start position:0% having a single prover so one I think 00:13:08.560 --> 00:13:10.910 align:start position:0% having a single prover so one I think most<00:13:08.760> of<00:13:08.880> the<00:13:09.000> networks<00:13:09.519> like<00:13:09.760> scroll<00:13:10.279> and<00:13:10.480> Tao 00:13:10.910 --> 00:13:10.920 align:start position:0% most of the networks like scroll and Tao 00:13:10.920 --> 00:13:15.069 align:start position:0% most of the networks like scroll and Tao is<00:13:11.079> trying<00:13:11.320> to<00:13:11.519> use<00:13:12.160> teth<00:13:13.160> but<00:13:13.760> in<00:13:13.920> my<00:13:14.120> opinion 00:13:15.069 --> 00:13:15.079 align:start position:0% is trying to use teth but in my opinion 00:13:15.079 --> 00:13:17.670 align:start position:0% is trying to use teth but in my opinion uh<00:13:15.399> there's<00:13:15.600> a<00:13:15.760> trust<00:13:16.079> issue<00:13:16.480> that<00:13:16.639> we<00:13:16.800> have<00:13:16.920> to 00:13:17.670 --> 00:13:17.680 align:start position:0% uh there's a trust issue that we have to 00:13:17.680 --> 00:13:20.430 align:start position:0% uh there's a trust issue that we have to trust<00:13:18.040> the<00:13:18.440> te<00:13:18.720> implementation<00:13:19.440> itself<00:13:20.079> so 00:13:20.430 --> 00:13:20.440 align:start position:0% trust the te implementation itself so 00:13:20.440 --> 00:13:22.710 align:start position:0% trust the te implementation itself so and<00:13:21.399> there's<00:13:21.720> also<00:13:22.000> like<00:13:22.199> Hydro 00:13:22.710 --> 00:13:22.720 align:start position:0% and there's also like Hydro 00:13:22.720 --> 00:13:25.110 align:start position:0% and there's also like Hydro centralization<00:13:23.600> problem<00:13:24.000> so<00:13:24.600> we<00:13:24.760> might<00:13:25.000> have 00:13:25.110 --> 00:13:25.120 align:start position:0% centralization problem so we might have 00:13:25.120 --> 00:13:27.910 align:start position:0% centralization problem so we might have to<00:13:25.399> come<00:13:25.560> up<00:13:25.680> with<00:13:25.800> a<00:13:25.920> clever<00:13:26.320> idea<00:13:26.880> to<00:13:27.680> maybe 00:13:27.910 --> 00:13:27.920 align:start position:0% to come up with a clever idea to maybe 00:13:27.920 --> 00:13:30.590 align:start position:0% to come up with a clever idea to maybe use<00:13:28.320> like<00:13:28.480> three<00:13:28.720> vendors<00:13:29.279> of<00:13:29.600> te's<00:13:30.160> and<00:13:30.320> then 00:13:30.590 --> 00:13:30.600 align:start position:0% use like three vendors of te's and then 00:13:30.600 --> 00:13:34.750 align:start position:0% use like three vendors of te's and then like<00:13:31.240> have<00:13:31.760> a<00:13:32.360> multiset<00:13:32.959> kind<00:13:33.120> of<00:13:33.480> thing<00:13:34.480> and 00:13:34.750 --> 00:13:34.760 align:start position:0% like have a multiset kind of thing and 00:13:34.760 --> 00:13:36.949 align:start position:0% like have a multiset kind of thing and another<00:13:35.079> one<00:13:35.279> would<00:13:35.480> be<00:13:36.160> kind 00:13:36.949 --> 00:13:36.959 align:start position:0% another one would be kind 00:13:36.959 --> 00:13:40.750 align:start position:0% another one would be kind of<00:13:37.959> very<00:13:38.240> very<00:13:38.519> labor<00:13:38.959> intensive<00:13:39.639> but<00:13:40.360> come<00:13:40.560> up 00:13:40.750 --> 00:13:40.760 align:start position:0% of very very labor intensive but come up 00:13:40.760 --> 00:13:43.990 align:start position:0% of very very labor intensive but come up with<00:13:41.040> another<00:13:41.519> circuit<00:13:42.519> B<00:13:43.279> another<00:13:43.600> circuit 00:13:43.990 --> 00:13:44.000 align:start position:0% with another circuit B another circuit 00:13:44.000 --> 00:13:47.509 align:start position:0% with another circuit B another circuit based<00:13:44.240> ckvm<00:13:44.959> so<00:13:45.399> instead<00:13:45.720> of<00:13:46.600> plish<00:13:47.079> and<00:13:47.240> Halo 00:13:47.509 --> 00:13:47.519 align:start position:0% based ckvm so instead of plish and Halo 00:13:47.519 --> 00:13:50.870 align:start position:0% based ckvm so instead of plish and Halo 2<00:13:47.959> you<00:13:48.160> might<00:13:48.399> have<00:13:48.519> to<00:13:49.160> write<00:13:49.680> another<00:13:50.079> ZK<00:13:50.440> evm 00:13:50.870 --> 00:13:50.880 align:start position:0% 2 you might have to write another ZK evm 00:13:50.880 --> 00:13:54.310 align:start position:0% 2 you might have to write another ZK evm code<00:13:51.360> circuit<00:13:51.759> code<00:13:52.440> with<00:13:52.600> another<00:13:53.320> language 00:13:54.310 --> 00:13:54.320 align:start position:0% code circuit code with another language 00:13:54.320 --> 00:13:57.150 align:start position:0% code circuit code with another language uh<00:13:55.000> I<00:13:55.079> don't<00:13:55.320> think<00:13:55.680> no<00:13:55.800> one<00:13:55.959> will<00:13:56.160> try<00:13:56.480> that 00:13:57.150 --> 00:13:57.160 align:start position:0% uh I don't think no one will try that 00:13:57.160 --> 00:14:00.110 align:start position:0% uh I don't think no one will try that and<00:13:58.040> I<00:13:58.160> think<00:13:58.440> the<00:13:58.560> best<00:13:58.759> would<00:13:58.880> be 00:14:00.110 --> 00:14:00.120 align:start position:0% and I think the best would be 00:14:00.120 --> 00:14:03.310 align:start position:0% and I think the best would be uh<00:14:00.360> our<00:14:00.639> approach<00:14:01.440> to<00:14:01.800> have<00:14:02.079> another<00:14:02.519> ZK<00:14:02.959> VM 00:14:03.310 --> 00:14:03.320 align:start position:0% uh our approach to have another ZK VM 00:14:03.320 --> 00:14:06.829 align:start position:0% uh our approach to have another ZK VM based<00:14:04.120> zkm<00:14:05.120> I'll<00:14:05.320> tell<00:14:05.480> you<00:14:05.759> why<00:14:06.079> like<00:14:06.519> why<00:14:06.720> we 00:14:06.829 --> 00:14:06.839 align:start position:0% based zkm I'll tell you why like why we 00:14:06.839 --> 00:14:09.749 align:start position:0% based zkm I'll tell you why like why we think<00:14:07.160> this<00:14:07.279> is<00:14:07.399> the 00:14:09.749 --> 00:14:09.759 align:start position:0% 00:14:09.759 --> 00:14:13.790 align:start position:0% best<00:14:10.759> uh<00:14:11.279> and<00:14:11.880> if<00:14:12.120> if<00:14:12.240> we<00:14:12.480> have<00:14:12.880> a<00:14:13.079> multi-prover 00:14:13.790 --> 00:14:13.800 align:start position:0% best uh and if if we have a multi-prover 00:14:13.800 --> 00:14:17.189 align:start position:0% best uh and if if we have a multi-prover system<00:14:14.440> and<00:14:14.759> if<00:14:14.880> we<00:14:15.000> have<00:14:15.199> like<00:14:15.360> ZK<00:14:15.759> VMS<00:14:16.240> now<00:14:17.079> we 00:14:17.189 --> 00:14:17.199 align:start position:0% system and if we have like ZK VMS now we 00:14:17.199 --> 00:14:20.990 align:start position:0% system and if we have like ZK VMS now we could<00:14:17.720> really<00:14:18.000> really<00:14:18.320> easily<00:14:18.759> ship<00:14:19.480> ZK 00:14:20.990 --> 00:14:21.000 align:start position:0% could really really easily ship ZK 00:14:21.000 --> 00:14:25.670 align:start position:0% could really really easily ship ZK rups<00:14:22.000> then<00:14:22.360> like<00:14:22.680> pass<00:14:23.079> one<00:14:23.240> or<00:14:23.360> two<00:14:23.800> years<00:14:24.800> but 00:14:25.670 --> 00:14:25.680 align:start position:0% rups then like pass one or two years but 00:14:25.680 --> 00:14:28.389 align:start position:0% rups then like pass one or two years but I've<00:14:25.880> did<00:14:26.040> some<00:14:26.240> benchmarks<00:14:26.920> with<00:14:27.680> several<00:14:28.040> ZK 00:14:28.389 --> 00:14:28.399 align:start position:0% I've did some benchmarks with several ZK 00:14:28.399 --> 00:14:31.150 align:start position:0% I've did some benchmarks with several ZK VMS<00:14:29.240> but<00:14:29.639> there's<00:14:29.880> still<00:14:30.079> a<00:14:30.240> feasibility 00:14:31.150 --> 00:14:31.160 align:start position:0% VMS but there's still a feasibility 00:14:31.160 --> 00:14:34.509 align:start position:0% VMS but there's still a feasibility issue<00:14:32.160> so<00:14:32.759> first<00:14:33.040> there's<00:14:33.279> a<00:14:33.600> cost<00:14:33.880> barrier 00:14:34.509 --> 00:14:34.519 align:start position:0% issue so first there's a cost barrier 00:14:34.519 --> 00:14:37.670 align:start position:0% issue so first there's a cost barrier which<00:14:34.680> is<00:14:35.079> very<00:14:35.320> very<00:14:35.560> important<00:14:36.320> and<00:14:37.320> in<00:14:37.440> my 00:14:37.670 --> 00:14:37.680 align:start position:0% which is very very important and in my 00:14:37.680 --> 00:14:39.150 align:start position:0% which is very very important and in my opinion<00:14:38.079> it<00:14:38.160> would<00:14:38.279> be<00:14:38.480> really<00:14:38.720> really<00:14:38.959> hard 00:14:39.150 --> 00:14:39.160 align:start position:0% opinion it would be really really hard 00:14:39.160 --> 00:14:42.189 align:start position:0% opinion it would be really really hard to<00:14:39.839> like<00:14:40.279> charge<00:14:40.639> the<00:14:40.800> users<00:14:41.160> to<00:14:41.320> use<00:14:41.519> it<00:14:41.839> since 00:14:42.189 --> 00:14:42.199 align:start position:0% to like charge the users to use it since 00:14:42.199 --> 00:14:45.150 align:start position:0% to like charge the users to use it since like<00:14:42.759> most<00:14:42.920> of<00:14:43.040> the<00:14:43.160> layer<00:14:43.480> twos<00:14:44.199> and<00:14:44.759> most<00:14:44.959> of 00:14:45.150 --> 00:14:45.160 align:start position:0% like most of the layer twos and most of 00:14:45.160 --> 00:14:48.030 align:start position:0% like most of the layer twos and most of the<00:14:45.399> optimistic<00:14:46.040> rollups<00:14:46.839> now<00:14:47.120> have<00:14:47.800> very 00:14:48.030 --> 00:14:48.040 align:start position:0% the optimistic rollups now have very 00:14:48.040 --> 00:14:48.790 align:start position:0% the optimistic rollups now have very very 00:14:48.790 --> 00:14:48.800 align:start position:0% very 00:14:48.800 --> 00:14:54.350 align:start position:0% very cheap<00:14:49.800> uh<00:14:50.800> fees<00:14:52.279> so<00:14:53.279> there<00:14:53.360> are<00:14:53.920> three<00:14:54.160> types 00:14:54.350 --> 00:14:54.360 align:start position:0% cheap uh fees so there are three types 00:14:54.360 --> 00:14:57.310 align:start position:0% cheap uh fees so there are three types of<00:14:54.560> costs<00:14:54.920> that<00:14:55.120> we<00:14:55.560> need<00:14:55.720> to<00:14:55.959> pay<00:14:56.360> to<00:14:56.560> run<00:14:56.800> a<00:14:56.959> zq 00:14:57.310 --> 00:14:57.320 align:start position:0% of costs that we need to pay to run a zq 00:14:57.320 --> 00:14:59.949 align:start position:0% of costs that we need to pay to run a zq rollup<00:14:58.199> first<00:14:59.160> is<00:14:59.399> it's<00:14:59.519> the<00:14:59.680> biggest 00:14:59.949 --> 00:14:59.959 align:start position:0% rollup first is it's the biggest 00:14:59.959 --> 00:15:03.350 align:start position:0% rollup first is it's the biggest bottleneck<00:15:00.680> which<00:15:00.800> is<00:15:00.959> the<00:15:01.079> proving<00:15:01.440> cost<00:15:02.360> so 00:15:03.350 --> 00:15:03.360 align:start position:0% bottleneck which is the proving cost so 00:15:03.360 --> 00:15:05.749 align:start position:0% bottleneck which is the proving cost so uh<00:15:03.800> I've<00:15:04.000> tested<00:15:04.399> with<00:15:04.639> like<00:15:04.800> a<00:15:04.959> network<00:15:05.480> with 00:15:05.749 --> 00:15:05.759 align:start position:0% uh I've tested with like a network with 00:15:05.759 --> 00:15:08.389 align:start position:0% uh I've tested with like a network with about<00:15:06.040> like<00:15:06.199> three<00:15:06.600> TPS<00:15:07.600> and<00:15:07.759> you<00:15:07.920> need<00:15:08.199> about 00:15:08.389 --> 00:15:08.399 align:start position:0% about like three TPS and you need about 00:15:08.399 --> 00:15:11.790 align:start position:0% about like three TPS and you need about a<00:15:08.519> million<00:15:08.959> dollar<00:15:09.399> for<00:15:10.000> proving<00:15:11.000> the<00:15:11.399> blocks 00:15:11.790 --> 00:15:11.800 align:start position:0% a million dollar for proving the blocks 00:15:11.800 --> 00:15:15.509 align:start position:0% a million dollar for proving the blocks for<00:15:12.360> a<00:15:12.600> year<00:15:13.800> so<00:15:14.800> I<00:15:14.880> think<00:15:15.120> it's<00:15:15.240> not<00:15:15.399> that 00:15:15.509 --> 00:15:15.519 align:start position:0% for a year so I think it's not that 00:15:15.519 --> 00:15:18.030 align:start position:0% for a year so I think it's not that feasible<00:15:15.959> now<00:15:16.600> and<00:15:16.759> also<00:15:17.320> we<00:15:17.440> would<00:15:17.639> have<00:15:17.759> to 00:15:18.030 --> 00:15:18.040 align:start position:0% feasible now and also we would have to 00:15:18.040 --> 00:15:20.629 align:start position:0% feasible now and also we would have to com<00:15:18.279> commit<00:15:18.560> to<00:15:18.680> the<00:15:18.839> batches<00:15:19.279> we've<00:15:20.279> uh 00:15:20.629 --> 00:15:20.639 align:start position:0% com commit to the batches we've uh 00:15:20.639 --> 00:15:22.790 align:start position:0% com commit to the batches we've uh settled<00:15:21.040> into<00:15:21.399> layer<00:15:21.759> one<00:15:22.279> so<00:15:22.440> there<00:15:22.560> will<00:15:22.680> be 00:15:22.790 --> 00:15:22.800 align:start position:0% settled into layer one so there will be 00:15:22.800 --> 00:15:25.710 align:start position:0% settled into layer one so there will be settlement<00:15:23.240> fees<00:15:23.600> also<00:15:24.519> and<00:15:24.920> to<00:15:25.160> finalize<00:15:25.600> the 00:15:25.710 --> 00:15:25.720 align:start position:0% settlement fees also and to finalize the 00:15:25.720 --> 00:15:27.910 align:start position:0% settlement fees also and to finalize the blocks<00:15:26.079> we<00:15:26.199> would<00:15:26.399> have<00:15:26.519> to<00:15:27.320> send<00:15:27.560> the<00:15:27.680> proof 00:15:27.910 --> 00:15:27.920 align:start position:0% blocks we would have to send the proof 00:15:27.920 --> 00:15:30.269 align:start position:0% blocks we would have to send the proof to<00:15:28.040> the<00:15:28.160> contract<00:15:28.519> and<00:15:28.639> verify<00:15:29.440> on<00:15:29.639> chain<00:15:30.079> so 00:15:30.269 --> 00:15:30.279 align:start position:0% to the contract and verify on chain so 00:15:30.279 --> 00:15:31.870 align:start position:0% to the contract and verify on chain so there's<00:15:30.639> also<00:15:30.839> going<00:15:30.920> to<00:15:31.040> be<00:15:31.199> verification 00:15:31.870 --> 00:15:31.880 align:start position:0% there's also going to be verification 00:15:31.880 --> 00:15:34.030 align:start position:0% there's also going to be verification piece<00:15:32.880> but<00:15:33.120> that's<00:15:33.279> going<00:15:33.360> to<00:15:33.519> be<00:15:33.759> really 00:15:34.030 --> 00:15:34.040 align:start position:0% piece but that's going to be really 00:15:34.040 --> 00:15:36.870 align:start position:0% piece but that's going to be really really<00:15:34.680> small<00:15:35.199> because<00:15:35.720> we<00:15:35.839> will<00:15:36.000> be<00:15:36.160> able<00:15:36.360> to 00:15:36.870 --> 00:15:36.880 align:start position:0% really small because we will be able to 00:15:36.880 --> 00:15:40.590 align:start position:0% really small because we will be able to agre<00:15:37.319> aggregate<00:15:37.800> proofs<00:15:38.240> inside<00:15:38.720> a<00:15:39.600> ckvm 00:15:40.590 --> 00:15:40.600 align:start position:0% agre aggregate proofs inside a ckvm 00:15:40.600 --> 00:15:42.870 align:start position:0% agre aggregate proofs inside a ckvm which<00:15:40.720> would<00:15:40.920> be<00:15:41.279> way<00:15:41.560> cheaper<00:15:42.560> but<00:15:42.680> there's 00:15:42.870 --> 00:15:42.880 align:start position:0% which would be way cheaper but there's 00:15:42.880 --> 00:15:45.269 align:start position:0% which would be way cheaper but there's going<00:15:42.959> to<00:15:43.079> be<00:15:43.199> trade-off<00:15:43.680> between 00:15:45.269 --> 00:15:45.279 align:start position:0% going to be trade-off between 00:15:45.279 --> 00:15:47.949 align:start position:0% going to be trade-off between finality<00:15:46.279> and<00:15:46.519> also<00:15:46.880> we<00:15:47.040> could<00:15:47.319> Explore<00:15:47.720> More 00:15:47.949 --> 00:15:47.959 align:start position:0% finality and also we could Explore More 00:15:47.959 --> 00:15:50.710 align:start position:0% finality and also we could Explore More on<00:15:48.199> future<00:15:48.600> directions<00:15:49.399> where<00:15:49.959> I<00:15:50.199> introduced 00:15:50.710 --> 00:15:50.720 align:start position:0% on future directions where I introduced 00:15:50.720 --> 00:15:53.350 align:start position:0% on future directions where I introduced the<00:15:50.920> multipro<00:15:51.600> system<00:15:52.519> and 00:15:53.350 --> 00:15:53.360 align:start position:0% the multipro system and 00:15:53.360 --> 00:15:56.829 align:start position:0% the multipro system and also<00:15:54.360> uh<00:15:54.720> the<00:15:54.959> ckvm<00:15:55.680> vendors<00:15:56.040> would<00:15:56.279> have<00:15:56.399> to 00:15:56.829 --> 00:15:56.839 align:start position:0% also uh the ckvm vendors would have to 00:15:56.839 --> 00:15:59.710 align:start position:0% also uh the ckvm vendors would have to consider<00:15:57.199> more<00:15:57.480> about<00:15:57.720> Pro<00:15:58.079> decentralization 00:15:59.710 --> 00:15:59.720 align:start position:0% consider more about Pro decentralization 00:15:59.720 --> 00:16:02.670 align:start position:0% consider more about Pro decentralization where<00:16:00.519> they<00:16:00.680> don't<00:16:00.959> keep<00:16:01.480> the<00:16:02.279> Clusters 00:16:02.670 --> 00:16:02.680 align:start position:0% where they don't keep the Clusters 00:16:02.680 --> 00:16:04.509 align:start position:0% where they don't keep the Clusters running<00:16:03.199> on<00:16:03.440> only<00:16:03.720> their<00:16:03.920> Network<00:16:04.360> and 00:16:04.509 --> 00:16:04.519 align:start position:0% running on only their Network and 00:16:04.519 --> 00:16:06.309 align:start position:0% running on only their Network and getting<00:16:04.800> proof<00:16:05.040> requests<00:16:05.639> but<00:16:05.839> instead<00:16:06.120> of 00:16:06.309 --> 00:16:06.319 align:start position:0% getting proof requests but instead of 00:16:06.319 --> 00:16:09.309 align:start position:0% getting proof requests but instead of like<00:16:06.680> have<00:16:06.800> a<00:16:07.079> incentive<00:16:08.000> mechanism<00:16:08.639> so<00:16:08.839> that 00:16:09.309 --> 00:16:09.319 align:start position:0% like have a incentive mechanism so that 00:16:09.319 --> 00:16:13.110 align:start position:0% like have a incentive mechanism so that Pro<00:16:09.720> Network<00:16:10.079> can<00:16:10.199> be<00:16:10.399> decentralized<00:16:11.079> a<00:16:11.160> bit 00:16:13.110 --> 00:16:13.120 align:start position:0% Pro Network can be decentralized a bit 00:16:13.120 --> 00:16:16.790 align:start position:0% Pro Network can be decentralized a bit more<00:16:14.120> uh<00:16:14.560> and<00:16:15.440> like<00:16:15.639> we're<00:16:15.880> also<00:16:16.120> pushing<00:16:16.519> the 00:16:16.790 --> 00:16:16.800 align:start position:0% more uh and like we're also pushing the 00:16:16.800 --> 00:16:18.430 align:start position:0% more uh and like we're also pushing the at<00:16:16.920> the<00:16:17.040> same<00:16:17.279> time<00:16:17.560> pushing<00:16:17.839> the<00:16:17.959> boundaries 00:16:18.430 --> 00:16:18.440 align:start position:0% at the same time pushing the boundaries 00:16:18.440 --> 00:16:21.670 align:start position:0% at the same time pushing the boundaries of<00:16:18.720> proof<00:16:19.120> generation<00:16:20.120> so<00:16:20.480> we<00:16:20.639> have<00:16:20.839> our<00:16:21.160> own 00:16:21.670 --> 00:16:21.680 align:start position:0% of proof generation so we have our own 00:16:21.680 --> 00:16:24.790 align:start position:0% of proof generation so we have our own very<00:16:22.040> unique<00:16:23.040> uh<00:16:23.160> open<00:16:23.440> source<00:16:23.800> Library 00:16:24.790 --> 00:16:24.800 align:start position:0% very unique uh open source Library 00:16:24.800 --> 00:16:27.990 align:start position:0% very unique uh open source Library called<00:16:25.440> takon<00:16:26.440> which<00:16:26.639> is<00:16:26.959> a<00:16:27.120> particle<00:16:27.600> that's 00:16:27.990 --> 00:16:28.000 align:start position:0% called takon which is a particle that's 00:16:28.000 --> 00:16:31.470 align:start position:0% called takon which is a particle that's known<00:16:28.240> to<00:16:28.399> be<00:16:28.680> f<00:16:28.920> faster<00:16:29.199> than<00:16:29.319> the<00:16:29.800> light<00:16:30.800> uh 00:16:31.470 --> 00:16:31.480 align:start position:0% known to be f faster than the light uh 00:16:31.480 --> 00:16:35.069 align:start position:0% known to be f faster than the light uh and<00:16:32.199> it's<00:16:32.480> it's<00:16:32.720> basically<00:16:33.319> a<00:16:33.519> modular<00:16:34.160> ckvm 00:16:35.069 --> 00:16:35.079 align:start position:0% and it's it's basically a modular ckvm 00:16:35.079 --> 00:16:37.949 align:start position:0% and it's it's basically a modular ckvm CK<00:16:35.519> backend<00:16:35.959> library<00:16:36.839> and<00:16:37.040> we<00:16:37.199> also<00:16:37.440> have<00:16:37.800> a 00:16:37.949 --> 00:16:37.959 align:start position:0% CK backend library and we also have a 00:16:37.959 --> 00:16:42.309 align:start position:0% CK backend library and we also have a feature<00:16:38.279> of<00:16:38.519> Z<00:16:38.800> GPU<00:16:39.680> acceleration<00:16:40.959> so<00:16:41.959> since 00:16:42.309 --> 00:16:42.319 align:start position:0% feature of Z GPU acceleration so since 00:16:42.319 --> 00:16:45.350 align:start position:0% feature of Z GPU acceleration so since we've<00:16:42.680> built<00:16:43.360> our<00:16:43.639> ZK<00:16:44.040> VM<00:16:44.319> based<00:16:44.519> on<00:16:44.639> halo2<00:16:45.240> we 00:16:45.350 --> 00:16:45.360 align:start position:0% we've built our ZK VM based on halo2 we 00:16:45.360 --> 00:16:47.949 align:start position:0% we've built our ZK VM based on halo2 we first<00:16:45.720> optimized<00:16:46.199> Halo<00:16:46.480> 2<00:16:46.639> a<00:16:46.800> lot<00:16:47.399> and<00:16:47.560> we<00:16:47.720> have 00:16:47.949 --> 00:16:47.959 align:start position:0% first optimized Halo 2 a lot and we have 00:16:47.959 --> 00:16:52.910 align:start position:0% first optimized Halo 2 a lot and we have about<00:16:48.240> like<00:16:48.680> 1.5x<00:16:49.680> 6X<00:16:50.240> faster 00:16:52.910 --> 00:16:52.920 align:start position:0% about like 1.5x 6X faster 00:16:52.920 --> 00:16:56.189 align:start position:0% about like 1.5x 6X faster Benchmark<00:16:53.920> and<00:16:54.319> we<00:16:54.519> also<00:16:55.160> are<00:16:55.480> trying<00:16:55.759> to 00:16:56.189 --> 00:16:56.199 align:start position:0% Benchmark and we also are trying to 00:16:56.199 --> 00:16:59.470 align:start position:0% Benchmark and we also are trying to utilize<00:16:56.959> sp1<00:16:57.600> ZK<00:16:58.000> VM<00:16:58.279> at<00:16:58.399> the<00:16:58.519> moment<00:16:59.040> so<00:16:59.279> we 00:16:59.470 --> 00:16:59.480 align:start position:0% utilize sp1 ZK VM at the moment so we 00:16:59.480 --> 00:17:01.990 align:start position:0% utilize sp1 ZK VM at the moment so we also<00:16:59.959> optimize<00:17:00.519> planky<00:17:00.880> 3<00:17:01.199> as<00:17:01.360> well<00:17:01.759> which<00:17:01.880> is 00:17:01.990 --> 00:17:02.000 align:start position:0% also optimize planky 3 as well which is 00:17:02.000 --> 00:17:04.150 align:start position:0% also optimize planky 3 as well which is used<00:17:02.279> by 00:17:04.150 --> 00:17:04.160 align:start position:0% used by 00:17:04.160 --> 00:17:07.909 align:start position:0% used by sp1<00:17:05.160> and<00:17:05.439> last<00:17:05.919> since<00:17:06.280> circum<00:17:06.959> is<00:17:07.120> very<00:17:07.360> very 00:17:07.909 --> 00:17:07.919 align:start position:0% sp1 and last since circum is very very 00:17:07.919 --> 00:17:11.189 align:start position:0% sp1 and last since circum is very very widely<00:17:08.319> used<00:17:08.600> in<00:17:08.760> the<00:17:08.919> community<00:17:09.799> we<00:17:10.039> also<00:17:11.039> uh 00:17:11.189 --> 00:17:11.199 align:start position:0% widely used in the community we also uh 00:17:11.199 --> 00:17:13.669 align:start position:0% widely used in the community we also uh optimize<00:17:11.640> a<00:17:11.760> lot<00:17:12.000> in<00:17:12.120> terms<00:17:12.400> of<00:17:12.679> Rapid<00:17:13.039> snark 00:17:13.669 --> 00:17:13.679 align:start position:0% optimize a lot in terms of Rapid snark 00:17:13.679 --> 00:17:15.949 align:start position:0% optimize a lot in terms of Rapid snark so<00:17:14.360> it's<00:17:14.520> also 00:17:15.949 --> 00:17:15.959 align:start position:0% so it's also 00:17:15.959 --> 00:17:18.750 align:start position:0% so it's also faster<00:17:16.959> and<00:17:17.160> we<00:17:17.280> could<00:17:17.480> wrap<00:17:17.720> up<00:17:17.919> into<00:17:18.559> this 00:17:18.750 --> 00:17:18.760 align:start position:0% faster and we could wrap up into this 00:17:18.760 --> 00:17:22.029 align:start position:0% faster and we could wrap up into this one<00:17:19.240> figure<00:17:20.039> where<00:17:20.919> if<00:17:21.240> if<00:17:21.400> chroma<00:17:21.799> has<00:17:21.919> a 00:17:22.029 --> 00:17:22.039 align:start position:0% one figure where if if chroma has a 00:17:22.039 --> 00:17:25.270 align:start position:0% one figure where if if chroma has a multi<00:17:22.400> ckv<00:17:22.880> Andover<00:17:23.439> back<00:17:24.240> uh<00:17:24.760> backing<00:17:25.160> the 00:17:25.270 --> 00:17:25.280 align:start position:0% multi ckv Andover back uh backing the 00:17:25.280 --> 00:17:27.909 align:start position:0% multi ckv Andover back uh backing the network<00:17:26.240> we<00:17:26.360> would<00:17:26.640> also<00:17:26.919> have<00:17:27.120> takon<00:17:27.760> which 00:17:27.909 --> 00:17:27.919 align:start position:0% network we would also have takon which 00:17:27.919 --> 00:17:30.669 align:start position:0% network we would also have takon which is<00:17:28.039> a<00:17:28.199> modular<00:17:28.960> ZK<00:17:29.320> backend<00:17:29.679> Library<00:17:30.480> which 00:17:30.669 --> 00:17:30.679 align:start position:0% is a modular ZK backend Library which 00:17:30.679 --> 00:17:34.669 align:start position:0% is a modular ZK backend Library which could<00:17:30.919> support<00:17:31.400> all<00:17:31.840> all<00:17:32.000> kinds<00:17:32.200> of<00:17:32.320> ZK<00:17:32.880> VMS<00:17:33.880> so 00:17:34.669 --> 00:17:34.679 align:start position:0% could support all all kinds of ZK VMS so 00:17:34.679 --> 00:17:36.190 align:start position:0% could support all all kinds of ZK VMS so we<00:17:34.799> would<00:17:35.000> only<00:17:35.240> have<00:17:35.360> to 00:17:36.190 --> 00:17:36.200 align:start position:0% we would only have to 00:17:36.200 --> 00:17:40.029 align:start position:0% we would only have to maintain<00:17:37.200> the<00:17:37.559> very<00:17:37.840> front<00:17:38.480> like<00:17:38.720> ZK<00:17:39.160> VM<00:17:39.559> main 00:17:40.029 --> 00:17:40.039 align:start position:0% maintain the very front like ZK VM main 00:17:40.039 --> 00:17:43.029 align:start position:0% maintain the very front like ZK VM main which<00:17:40.160> is<00:17:40.520> written<00:17:40.840> in<00:17:41.000> Rust<00:17:41.720> and<00:17:42.640> which 00:17:43.029 --> 00:17:43.039 align:start position:0% which is written in Rust and which 00:17:43.039 --> 00:17:45.350 align:start position:0% which is written in Rust and which mainly<00:17:43.360> uses<00:17:44.000> the<00:17:44.160> library<00:17:44.559> Kona<00:17:45.080> which<00:17:45.160> is 00:17:45.350 --> 00:17:45.360 align:start position:0% mainly uses the library Kona which is 00:17:45.360 --> 00:17:48.029 align:start position:0% mainly uses the library Kona which is main<00:17:45.600> from<00:17:45.960> maintained<00:17:46.400> from<00:17:46.840> optimism<00:17:47.840> which 00:17:48.029 --> 00:17:48.039 align:start position:0% main from maintained from optimism which 00:17:48.039 --> 00:17:50.270 align:start position:0% main from maintained from optimism which has<00:17:48.400> block<00:17:48.760> derivation<00:17:49.280> logic<00:17:49.600> and<00:17:49.840> execution 00:17:50.270 --> 00:17:50.280 align:start position:0% has block derivation logic and execution 00:17:50.280 --> 00:17:54.350 align:start position:0% has block derivation logic and execution logic<00:17:50.720> so<00:17:51.280> we<00:17:51.440> could<00:17:51.640> easily<00:17:52.160> write<00:17:53.120> uh<00:17:54.120> a 00:17:54.350 --> 00:17:54.360 align:start position:0% logic so we could easily write uh a 00:17:54.360 --> 00:17:56.990 align:start position:0% logic so we could easily write uh a program<00:17:55.080> for<00:17:55.240> a<00:17:55.360> main<00:17:55.640> net<00:17:56.000> within<00:17:56.360> like<00:17:56.760> 200 00:17:56.990 --> 00:17:57.000 align:start position:0% program for a main net within like 200 00:17:57.000 --> 00:17:59.149 align:start position:0% program for a main net within like 200 lines<00:17:57.240> of<00:17:57.400> code<00:17:58.400> and<00:17:58.559> we<00:17:58.679> would<00:17:58.840> would<00:17:58.960> have<00:17:59.039> an 00:17:59.149 --> 00:17:59.159 align:start position:0% lines of code and we would would have an 00:17:59.159 --> 00:18:01.430 align:start position:0% lines of code and we would would have an input<00:17:59.799> with<00:18:00.080> which<00:18:00.559> the<00:18:00.840> which<00:18:00.960> would<00:18:01.120> be<00:18:01.280> the 00:18:01.430 --> 00:18:01.440 align:start position:0% input with which the which would be the 00:18:01.440 --> 00:18:03.390 align:start position:0% input with which the which would be the block<00:18:01.679> we're<00:18:01.880> trying<00:18:02.039> to<00:18:02.200> prove<00:18:02.960> and<00:18:03.159> we<00:18:03.240> would 00:18:03.390 --> 00:18:03.400 align:start position:0% block we're trying to prove and we would 00:18:03.400 --> 00:18:05.430 align:start position:0% block we're trying to prove and we would have<00:18:03.520> a<00:18:03.600> multi-prover<00:18:04.559> like<00:18:05.080> one<00:18:05.200> of<00:18:05.320> the 00:18:05.430 --> 00:18:05.440 align:start position:0% have a multi-prover like one of the 00:18:05.440 --> 00:18:10.990 align:start position:0% have a multi-prover like one of the Frontiers<00:18:06.200> risk<00:18:06.520> zero<00:18:07.280> sp1<00:18:08.280> o<00:18:08.919> VM<00:18:09.919> uh<00:18:10.360> Alida 00:18:10.990 --> 00:18:11.000 align:start position:0% Frontiers risk zero sp1 o VM uh Alida 00:18:11.000 --> 00:18:14.230 align:start position:0% Frontiers risk zero sp1 o VM uh Alida maybe<00:18:11.880> and<00:18:12.039> then<00:18:12.320> we<00:18:12.520> have<00:18:12.840> a<00:18:13.039> takon<00:18:13.559> which<00:18:13.679> is 00:18:14.230 --> 00:18:14.240 align:start position:0% maybe and then we have a takon which is 00:18:14.240 --> 00:18:17.470 align:start position:0% maybe and then we have a takon which is backing<00:18:14.640> with<00:18:15.240> powerful<00:18:15.640> GPU<00:18:16.480> optimizations 00:18:17.470 --> 00:18:17.480 align:start position:0% backing with powerful GPU optimizations 00:18:17.480 --> 00:18:19.430 align:start position:0% backing with powerful GPU optimizations which<00:18:17.600> will<00:18:18.000> accelate<00:18:18.600> accelerate<00:18:19.039> the<00:18:19.159> proof 00:18:19.430 --> 00:18:19.440 align:start position:0% which will accelate accelerate the proof 00:18:19.440 --> 00:18:22.390 align:start position:0% which will accelate accelerate the proof generation 00:18:22.390 --> 00:18:22.400 align:start position:0% 00:18:22.400 --> 00:18:25.510 align:start position:0% speed<00:18:23.400> yep<00:18:23.760> that's<00:18:23.960> it<00:18:24.159> for<00:18:24.360> today<00:18:25.159> and<00:18:25.360> you 00:18:25.510 --> 00:18:25.520 align:start position:0% speed yep that's it for today and you 00:18:25.520 --> 00:18:27.990 align:start position:0% speed yep that's it for today and you can<00:18:25.760> contact<00:18:26.080> me<00:18:26.480> with<00:18:26.679> fakee<00:18:27.200> 9999<00:18:27.840> on 00:18:27.990 --> 00:18:28.000 align:start position:0% can contact me with fakee 9999 on 00:18:28.000 --> 00:18:30.110 align:start position:0% can contact me with fakee 9999 on Twitter<00:18:28.320> Telegram<00:18:29.120> please<00:18:29.400> contact<00:18:29.880> we<00:18:30.000> could 00:18:30.110 --> 00:18:30.120 align:start position:0% Twitter Telegram please contact we could 00:18:30.120 --> 00:18:33.870 align:start position:0% Twitter Telegram please contact we could share<00:18:30.400> more<00:18:30.799> about<00:18:31.799> uh<00:18:32.120> fault<00:18:32.440> prooof<00:18:32.880> systems 00:18:33.870 --> 00:18:33.880 align:start position:0% share more about uh fault prooof systems 00:18:33.880 --> 00:18:36.149 align:start position:0% share more about uh fault prooof systems I<00:18:33.960> would<00:18:34.120> like<00:18:34.240> to<00:18:34.360> hear<00:18:34.520> your<00:18:34.919> ideas<00:18:35.919> and 00:18:36.149 --> 00:18:36.159 align:start position:0% I would like to hear your ideas and 00:18:36.159 --> 00:18:40.290 align:start position:0% I would like to hear your ideas and that's<00:18:36.360> it<00:18:36.640> thank 00:18:40.290 --> 00:18:40.300 align:start position:0% 00:18:40.300 --> 00:18:43.149 align:start position:0% [Music] 00:18:43.149 --> 00:18:43.159 align:start position:0% [Music] 00:18:43.159 --> 00:18:46.110 align:start position:0% [Music] you<00:18:44.159> oh<00:18:44.600> you<00:18:44.720> can<00:18:44.840> just<00:18:45.000> stay<00:18:45.200> over<00:18:45.440> here<00:18:45.960> all 00:18:46.110 --> 00:18:46.120 align:start position:0% you oh you can just stay over here all 00:18:46.120 --> 00:18:48.669 align:start position:0% you oh you can just stay over here all right<00:18:46.600> uh<00:18:46.760> great<00:18:46.960> talk<00:18:47.159> to<00:18:47.720> so<00:18:48.200> thank<00:18:48.360> you<00:18:48.520> to 00:18:48.669 --> 00:18:48.679 align:start position:0% right uh great talk to so thank you to 00:18:48.679 --> 00:18:50.830 align:start position:0% right uh great talk to so thank you to the<00:18:48.840> crowd<00:18:49.200> for<00:18:49.520> submitting<00:18:50.320> all<00:18:50.559> these 00:18:50.830 --> 00:18:50.840 align:start position:0% the crowd for submitting all these 00:18:50.840 --> 00:18:53.310 align:start position:0% the crowd for submitting all these amazing<00:18:51.280> questions<00:18:52.080> uh<00:18:52.240> we<00:18:52.400> do<00:18:52.760> have<00:18:53.080> less 00:18:53.310 --> 00:18:53.320 align:start position:0% amazing questions uh we do have less 00:18:53.320 --> 00:18:56.110 align:start position:0% amazing questions uh we do have less than<00:18:53.640> five<00:18:53.960> minutes<00:18:54.480> to<00:18:54.760> go<00:18:54.960> through<00:18:55.520> some<00:18:55.880> of 00:18:56.110 --> 00:18:56.120 align:start position:0% than five minutes to go through some of 00:18:56.120 --> 00:18:59.430 align:start position:0% than five minutes to go through some of them<00:18:57.080> uh<00:18:57.240> let's<00:18:57.520> go<00:18:58.200> through 00:18:59.430 --> 00:18:59.440 align:start position:0% them uh let's go through 00:18:59.440 --> 00:19:01.990 align:start position:0% them uh let's go through uh<00:18:59.600> the<00:18:59.760> most<00:19:00.480> upvoted<00:19:01.120> one<00:19:01.520> how<00:19:01.679> is<00:19:01.760> it 00:19:01.990 --> 00:19:02.000 align:start position:0% uh the most upvoted one how is it 00:19:02.000 --> 00:19:05.190 align:start position:0% uh the most upvoted one how is it different<00:19:02.360> than<00:19:02.559> op6<00:19:03.240> sync<00:19:03.880> yeah<00:19:04.480> uh<00:19:04.880> some<00:19:05.080> of 00:19:05.190 --> 00:19:05.200 align:start position:0% different than op6 sync yeah uh some of 00:19:05.200 --> 00:19:08.390 align:start position:0% different than op6 sync yeah uh some of you<00:19:05.440> guys<00:19:05.840> might<00:19:06.080> know<00:19:06.600> and<00:19:06.799> not<00:19:07.000> know<00:19:07.440> but<00:19:08.120> uh 00:19:08.390 --> 00:19:08.400 align:start position:0% you guys might know and not know but uh 00:19:08.400 --> 00:19:11.630 align:start position:0% you guys might know and not know but uh opung<00:19:09.280> and<00:19:09.640> us<00:19:10.240> we<00:19:10.440> have<00:19:10.559> a<00:19:10.720> very<00:19:10.960> very<00:19:11.200> similar 00:19:11.630 --> 00:19:11.640 align:start position:0% opung and us we have a very very similar 00:19:11.640 --> 00:19:15.190 align:start position:0% opung and us we have a very very similar logic<00:19:12.600> actually<00:19:13.120> we<00:19:13.240> were<00:19:13.960> working<00:19:14.360> under 00:19:15.190 --> 00:19:15.200 align:start position:0% logic actually we were working under 00:19:15.200 --> 00:19:18.390 align:start position:0% logic actually we were working under water<00:19:15.880> like<00:19:16.120> for<00:19:16.480> about<00:19:16.799> like<00:19:17.240> two<00:19:17.520> months<00:19:18.280> and 00:19:18.390 --> 00:19:18.400 align:start position:0% water like for about like two months and 00:19:18.400 --> 00:19:21.149 align:start position:0% water like for about like two months and then<00:19:18.559> like<00:19:18.679> we<00:19:18.760> shared<00:19:19.080> it<00:19:19.240> to<00:19:20.080> the<00:19:20.240> sp1<00:19:20.799> team 00:19:21.149 --> 00:19:21.159 align:start position:0% then like we shared it to the sp1 team 00:19:21.159 --> 00:19:24.029 align:start position:0% then like we shared it to the sp1 team about<00:19:21.799> oh<00:19:21.960> we<00:19:22.120> have<00:19:22.240> a<00:19:22.559> choma<00:19:23.080> SPO<00:19:23.640> improver 00:19:24.029 --> 00:19:24.039 align:start position:0% about oh we have a choma SPO improver 00:19:24.039 --> 00:19:25.990 align:start position:0% about oh we have a choma SPO improver repository<00:19:24.799> you<00:19:24.919> could<00:19:25.080> take<00:19:25.200> a<00:19:25.360> look<00:19:25.559> if<00:19:25.760> the 00:19:25.990 --> 00:19:26.000 align:start position:0% repository you could take a look if the 00:19:26.000 --> 00:19:28.430 align:start position:0% repository you could take a look if the logic<00:19:26.280> would<00:19:26.440> be<00:19:26.559> correct<00:19:26.840> for<00:19:27.480> ZK<00:19:27.840> VM<00:19:28.120> based 00:19:28.430 --> 00:19:28.440 align:start position:0% logic would be correct for ZK VM based 00:19:28.440 --> 00:19:29.510 align:start position:0% logic would be correct for ZK VM based Prov 00:19:29.510 --> 00:19:29.520 align:start position:0% Prov 00:19:29.520 --> 00:19:32.110 align:start position:0% Prov and<00:19:30.159> they<00:19:30.280> were<00:19:30.520> also<00:19:30.880> working<00:19:31.159> on<00:19:31.559> water<00:19:31.960> with 00:19:32.110 --> 00:19:32.120 align:start position:0% and they were also working on water with 00:19:32.120 --> 00:19:34.430 align:start position:0% and they were also working on water with the<00:19:32.280> same<00:19:32.520> thing<00:19:32.880> and<00:19:33.240> like<00:19:33.559> it<00:19:33.760> comes<00:19:34.120> out 00:19:34.430 --> 00:19:34.440 align:start position:0% the same thing and like it comes out 00:19:34.440 --> 00:19:37.390 align:start position:0% the same thing and like it comes out that<00:19:34.720> like<00:19:34.880> we<00:19:35.120> have<00:19:35.480> almost<00:19:35.799> similar<00:19:36.400> logic 00:19:37.390 --> 00:19:37.400 align:start position:0% that like we have almost similar logic 00:19:37.400 --> 00:19:40.230 align:start position:0% that like we have almost similar logic and<00:19:38.360> they<00:19:38.600> have<00:19:38.919> an<00:19:39.320> additional<00:19:39.679> feature<00:19:40.039> of 00:19:40.230 --> 00:19:40.240 align:start position:0% and they have an additional feature of 00:19:40.240 --> 00:19:42.190 align:start position:0% and they have an additional feature of what<00:19:40.360> I<00:19:40.480> mentioned<00:19:40.840> of<00:19:41.159> aggreg<00:19:41.720> aggregating 00:19:42.190 --> 00:19:42.200 align:start position:0% what I mentioned of aggreg aggregating 00:19:42.200 --> 00:19:45.990 align:start position:0% what I mentioned of aggreg aggregating the<00:19:42.320> proofs<00:19:43.240> so<00:19:44.200> the<00:19:44.400> logic<00:19:44.840> is<00:19:45.280> very<00:19:45.520> similar 00:19:45.990 --> 00:19:46.000 align:start position:0% the proofs so the logic is very similar 00:19:46.000 --> 00:19:50.310 align:start position:0% the proofs so the logic is very similar but<00:19:46.400> basically<00:19:46.919> we<00:19:47.280> built<00:19:47.600> the<00:19:47.720> same 00:19:50.310 --> 00:19:50.320 align:start position:0% 00:19:50.320 --> 00:19:53.470 align:start position:0% thing<00:19:51.320> uh<00:19:51.840> so<00:19:52.080> I'm<00:19:52.280> going<00:19:52.440> to<00:19:52.720> mark<00:19:53.039> this<00:19:53.200> as 00:19:53.470 --> 00:19:53.480 align:start position:0% thing uh so I'm going to mark this as 00:19:53.480 --> 00:19:56.350 align:start position:0% thing uh so I'm going to mark this as answered<00:19:53.880> any<00:19:54.080> stats<00:19:54.480> on<00:19:54.679> Pro<00:19:55.120> cost<00:19:55.679> specs<00:19:56.120> and 00:19:56.350 --> 00:19:56.360 align:start position:0% answered any stats on Pro cost specs and 00:19:56.360 --> 00:19:59.909 align:start position:0% answered any stats on Pro cost specs and time<00:19:57.280> so<00:19:57.919> the<00:19:58.080> Prov<00:19:58.440> cost 00:19:59.909 --> 00:19:59.919 align:start position:0% time so the Prov cost 00:19:59.919 --> 00:20:04.070 align:start position:0% time so the Prov cost for<00:20:00.919> uh<00:20:01.679> the<00:20:02.240> for<00:20:02.440> our<00:20:02.640> fault<00:20:02.960> proof<00:20:03.240> system 00:20:04.070 --> 00:20:04.080 align:start position:0% for uh the for our fault proof system 00:20:04.080 --> 00:20:09.789 align:start position:0% for uh the for our fault proof system for<00:20:04.520> about<00:20:04.799> a<00:20:05.799> block<00:20:06.799> with<00:20:07.120> a<00:20:07.320> TPS<00:20:07.840> of<00:20:08.039> three<00:20:08.799> to 00:20:09.789 --> 00:20:09.799 align:start position:0% for about a block with a TPS of three to 00:20:09.799 --> 00:20:11.350 align:start position:0% for about a block with a TPS of three to prove<00:20:10.080> a<00:20:10.200> faulty 00:20:11.350 --> 00:20:11.360 align:start position:0% prove a faulty 00:20:11.360 --> 00:20:16.390 align:start position:0% prove a faulty block<00:20:12.360> uh<00:20:13.000> of<00:20:13.480> tps3<00:20:14.480> I<00:20:14.679> think<00:20:14.840> it<00:20:15.080> costs<00:20:15.400> about 00:20:16.390 --> 00:20:16.400 align:start position:0% block uh of tps3 I think it costs about 00:20:16.400 --> 00:20:19.909 align:start position:0% block uh of tps3 I think it costs about like<00:20:17.400> uh<00:20:18.120> currently<00:20:18.720> if<00:20:18.880> you<00:20:19.280> so<00:20:19.480> it<00:20:19.600> depends 00:20:19.909 --> 00:20:19.919 align:start position:0% like uh currently if you so it depends 00:20:19.919 --> 00:20:21.950 align:start position:0% like uh currently if you so it depends on<00:20:20.080> the<00:20:20.280> pricing<00:20:20.640> of<00:20:20.840> the<00:20:21.159> N<00:20:21.440> the<00:20:21.600> approver 00:20:21.950 --> 00:20:21.960 align:start position:0% on the pricing of the N the approver 00:20:21.960 --> 00:20:23.830 align:start position:0% on the pricing of the N the approver network<00:20:22.280> you're<00:20:22.400> trying<00:20:22.679> to<00:20:22.799> use<00:20:23.200> but<00:20:23.720> if 00:20:23.830 --> 00:20:23.840 align:start position:0% network you're trying to use but if 00:20:23.840 --> 00:20:25.990 align:start position:0% network you're trying to use but if you're<00:20:24.360> just<00:20:24.640> using<00:20:24.919> an<00:20:25.080> ond<00:20:25.320> demand<00:20:25.640> plan 00:20:25.990 --> 00:20:26.000 align:start position:0% you're just using an ond demand plan 00:20:26.000 --> 00:20:29.350 align:start position:0% you're just using an ond demand plan which<00:20:26.200> would<00:20:26.400> be<00:20:26.600> the<00:20:27.120> most<00:20:27.640> expensive<00:20:28.679> per 00:20:29.350 --> 00:20:29.360 align:start position:0% which would be the most expensive per 00:20:29.360 --> 00:20:31.990 align:start position:0% which would be the most expensive per Cycles<00:20:30.360> uh<00:20:30.760> if<00:20:30.840> I<00:20:31.000> remember<00:20:31.320> correctly<00:20:31.799> it's 00:20:31.990 --> 00:20:32.000 align:start position:0% Cycles uh if I remember correctly it's 00:20:32.000 --> 00:20:33.590 align:start position:0% Cycles uh if I remember correctly it's it<00:20:32.080> was<00:20:32.240> about 00:20:33.590 --> 00:20:33.600 align:start position:0% it was about 00:20:33.600 --> 00:20:36.950 align:start position:0% it was about like<00:20:34.600> 20<00:20:34.919> 20<00:20:35.240> bucks<00:20:35.600> for<00:20:35.799> a<00:20:36.000> block<00:20:36.440> with<00:20:36.760> like 00:20:36.950 --> 00:20:36.960 align:start position:0% like 20 20 bucks for a block with like 00:20:36.960 --> 00:20:41.909 align:start position:0% like 20 20 bucks for a block with like about<00:20:37.520> like<00:20:38.520> uh 00:20:41.909 --> 00:20:41.919 align:start position:0% 00:20:41.919 --> 00:20:46.190 align:start position:0% tps3<00:20:42.919> and<00:20:43.520> uh<00:20:44.120> the<00:20:44.360> their<00:20:45.240> the<00:20:45.400> stats<00:20:45.679> and<00:20:45.919> like 00:20:46.190 --> 00:20:46.200 align:start position:0% tps3 and uh the their the stats and like 00:20:46.200 --> 00:20:48.669 align:start position:0% tps3 and uh the their the stats and like the<00:20:46.480> machine<00:20:46.880> specs<00:20:47.280> it's<00:20:47.720> not<00:20:48.039> revealed<00:20:48.559> at 00:20:48.669 --> 00:20:48.679 align:start position:0% the machine specs it's not revealed at 00:20:48.679 --> 00:20:51.950 align:start position:0% the machine specs it's not revealed at the<00:20:48.799> moment<00:20:49.200> for<00:20:49.559> SPO<00:20:50.000> Andover<00:20:50.440> Network<00:20:50.960> so 00:20:51.950 --> 00:20:51.960 align:start position:0% the moment for SPO Andover Network so 00:20:51.960 --> 00:20:54.350 align:start position:0% the moment for SPO Andover Network so I'm<00:20:52.080> not<00:20:52.200> sure<00:20:52.400> about<00:20:52.640> that<00:20:53.400> all<00:20:53.520> right<00:20:54.039> do<00:20:54.200> you 00:20:54.350 --> 00:20:54.360 align:start position:0% I'm not sure about that all right do you 00:20:54.360 --> 00:20:57.870 align:start position:0% I'm not sure about that all right do you know<00:20:54.960> if<00:20:55.280> the<00:20:55.520> ARB<00:20:56.200> ecosystem<00:20:57.120> have<00:20:57.400> similar 00:20:57.870 --> 00:20:57.880 align:start position:0% know if the ARB ecosystem have similar 00:20:57.880 --> 00:21:02.230 align:start position:0% know if the ARB ecosystem have similar plans<00:20:58.840> yes<00:20:59.120> I<00:20:59.320> I<00:20:59.520> definitely<00:20:59.960> know<00:21:00.360> and<00:21:00.720> I<00:21:01.320> also 00:21:02.230 --> 00:21:02.240 align:start position:0% plans yes I I definitely know and I also 00:21:02.240 --> 00:21:05.270 align:start position:0% plans yes I I definitely know and I also uh<00:21:02.360> know<00:21:02.640> the<00:21:02.799> fact<00:21:03.080> that<00:21:03.320> they<00:21:03.600> have<00:21:03.840> a<00:21:04.679> fast 00:21:05.270 --> 00:21:05.280 align:start position:0% uh know the fact that they have a fast 00:21:05.280 --> 00:21:09.230 align:start position:0% uh know the fact that they have a fast withdrawal<00:21:06.280> feature<00:21:06.960> now<00:21:07.559> with<00:21:07.880> ZK<00:21:08.280> proofs<00:21:09.120> I 00:21:09.230 --> 00:21:09.240 align:start position:0% withdrawal feature now with ZK proofs I 00:21:09.240 --> 00:21:10.909 align:start position:0% withdrawal feature now with ZK proofs I didn't<00:21:09.559> have<00:21:09.720> much<00:21:09.960> time<00:21:10.080> to<00:21:10.279> like<00:21:10.440> deep<00:21:10.679> dive 00:21:10.909 --> 00:21:10.919 align:start position:0% didn't have much time to like deep dive 00:21:10.919 --> 00:21:14.909 align:start position:0% didn't have much time to like deep dive into<00:21:11.120> it<00:21:11.679> but<00:21:12.679> I<00:21:13.559> I<00:21:13.679> definitely<00:21:14.080> think<00:21:14.440> like 00:21:14.909 --> 00:21:14.919 align:start position:0% into it but I I definitely think like 00:21:14.919 --> 00:21:16.430 align:start position:0% into it but I I definitely think like arbitrum 00:21:16.430 --> 00:21:16.440 align:start position:0% arbitrum 00:21:16.440 --> 00:21:20.070 align:start position:0% arbitrum also<00:21:17.440> is<00:21:17.600> going<00:21:18.000> through<00:21:18.400> the<00:21:18.640> right<00:21:19.039> path<00:21:19.400> so 00:21:20.070 --> 00:21:20.080 align:start position:0% also is going through the right path so 00:21:20.080 --> 00:21:21.870 align:start position:0% also is going through the right path so maybe<00:21:20.360> we<00:21:20.480> could<00:21:20.720> collab<00:21:21.120> more<00:21:21.320> and<00:21:21.480> talk<00:21:21.679> more 00:21:21.870 --> 00:21:21.880 align:start position:0% maybe we could collab more and talk more 00:21:21.880 --> 00:21:22.830 align:start position:0% maybe we could collab more and talk more about 00:21:22.830 --> 00:21:22.840 align:start position:0% about 00:21:22.840 --> 00:21:25.909 align:start position:0% about it<00:21:23.840> all<00:21:23.960> right<00:21:24.159> great<00:21:24.440> so<00:21:24.720> we<00:21:25.320> we<00:21:25.480> can<00:21:25.679> go 00:21:25.909 --> 00:21:25.919 align:start position:0% it all right great so we we can go 00:21:25.919 --> 00:21:28.110 align:start position:0% it all right great so we we can go through<00:21:26.520> I<00:21:26.720> guess<00:21:27.039> two<00:21:27.200> more<00:21:27.440> questions<00:21:27.799> real 00:21:28.110 --> 00:21:28.120 align:start position:0% through I guess two more questions real 00:21:28.120 --> 00:21:30.750 align:start position:0% through I guess two more questions real quick<00:21:29.000> uh<00:21:29.240> in<00:21:29.360> your<00:21:29.600> prior<00:21:29.919> implementation<00:21:30.559> by 00:21:30.750 --> 00:21:30.760 align:start position:0% quick uh in your prior implementation by 00:21:30.760 --> 00:21:33.269 align:start position:0% quick uh in your prior implementation by pish<00:21:31.240> circuit<00:21:31.760> you<00:21:31.840> mean<00:21:32.080> Pony<00:21:32.480> 2<00:21:32.640> or<00:21:32.799> three<00:21:33.039> or 00:21:33.269 --> 00:21:33.279 align:start position:0% pish circuit you mean Pony 2 or three or 00:21:33.279 --> 00:21:35.830 align:start position:0% pish circuit you mean Pony 2 or three or something<00:21:33.679> custom<00:21:34.400> oh<00:21:34.640> it's<00:21:34.880> it's<00:21:35.120> actually 00:21:35.830 --> 00:21:35.840 align:start position:0% something custom oh it's it's actually 00:21:35.840 --> 00:21:39.630 align:start position:0% something custom oh it's it's actually uh<00:21:36.400> Halo<00:21:36.799> to's<00:21:37.440> plish<00:21:38.039> arithmetization 00:21:39.630 --> 00:21:39.640 align:start position:0% uh Halo to's plish arithmetization 00:21:39.640 --> 00:21:42.590 align:start position:0% uh Halo to's plish arithmetization uh<00:21:40.640> it<00:21:40.919> might<00:21:41.320> have<00:21:41.720> like<00:21:41.919> confused<00:21:42.320> you<00:21:42.480> a 00:21:42.590 --> 00:21:42.600 align:start position:0% uh it might have like confused you a 00:21:42.600 --> 00:21:45.310 align:start position:0% uh it might have like confused you a little<00:21:42.799> bit<00:21:43.120> but<00:21:43.480> it<00:21:43.960> our<00:21:44.559> we're<00:21:44.760> using<00:21:45.000> a<00:21:45.159> back 00:21:45.310 --> 00:21:45.320 align:start position:0% little bit but it our we're using a back 00:21:45.320 --> 00:21:47.350 align:start position:0% little bit but it our we're using a back end<00:21:45.520> currently<00:21:46.120> Halo 00:21:47.350 --> 00:21:47.360 align:start position:0% end currently Halo 00:21:47.360 --> 00:21:50.710 align:start position:0% end currently Halo 2<00:21:48.360> all<00:21:48.480> right<00:21:48.799> so<00:21:49.159> one<00:21:49.440> last<00:21:49.840> question<00:21:50.440> what 00:21:50.710 --> 00:21:50.720 align:start position:0% 2 all right so one last question what 00:21:50.720 --> 00:21:53.190 align:start position:0% 2 all right so one last question what happens<00:21:51.159> if<00:21:51.320> the<00:21:51.520> guest<00:21:51.840> program<00:21:52.240> panics<00:21:53.080> can 00:21:53.190 --> 00:21:53.200 align:start position:0% happens if the guest program panics can 00:21:53.200 --> 00:21:56.149 align:start position:0% happens if the guest program panics can you<00:21:53.360> still<00:21:53.760> produce<00:21:54.080> a<00:21:54.279> proof<00:21:55.159> so<00:21:55.600> if<00:21:55.720> a<00:21:55.880> guest 00:21:56.149 --> 00:21:56.159 align:start position:0% you still produce a proof so if a guest 00:21:56.159 --> 00:21:59.430 align:start position:0% you still produce a proof so if a guest program<00:21:56.559> panics<00:21:57.400> then<00:21:58.200> uh<00:21:58.600> you<00:21:58.679> can't<00:21:59.120> produce 00:21:59.430 --> 00:21:59.440 align:start position:0% program panics then uh you can't produce 00:21:59.440 --> 00:22:00.909 align:start position:0% program panics then uh you can't produce a<00:21:59.640> proof 00:22:00.909 --> 00:22:00.919 align:start position:0% a proof 00:22:00.919 --> 00:22:03.430 align:start position:0% a proof so<00:22:01.919> uh<00:22:02.320> I'm<00:22:02.480> not 00:22:03.430 --> 00:22:03.440 align:start position:0% so uh I'm not 00:22:03.440 --> 00:22:07.110 align:start position:0% so uh I'm not sure<00:22:04.440> uh<00:22:05.159> the<00:22:05.720> person<00:22:06.000> who<00:22:06.200> ask<00:22:06.559> who's<00:22:06.840> asking 00:22:07.110 --> 00:22:07.120 align:start position:0% sure uh the person who ask who's asking 00:22:07.120 --> 00:22:09.909 align:start position:0% sure uh the person who ask who's asking the<00:22:07.320> question<00:22:07.960> like<00:22:08.679> is<00:22:09.120> intentionally 00:22:09.909 --> 00:22:09.919 align:start position:0% the question like is intentionally 00:22:09.919 --> 00:22:14.549 align:start position:0% the question like is intentionally panicking<00:22:10.760> the<00:22:11.000> program<00:22:11.400> or<00:22:11.600> not<00:22:11.919> but 00:22:14.549 --> 00:22:14.559 align:start position:0% 00:22:14.559 --> 00:22:17.350 align:start position:0% like<00:22:15.559> yeah<00:22:15.880> if<00:22:16.039> if<00:22:16.159> it's<00:22:16.320> a<00:22:16.480> bug<00:22:16.960> that's 00:22:17.350 --> 00:22:17.360 align:start position:0% like yeah if if it's a bug that's 00:22:17.360 --> 00:22:19.190 align:start position:0% like yeah if if it's a bug that's causing<00:22:17.840> panic 00:22:19.190 --> 00:22:19.200 align:start position:0% causing panic 00:22:19.200 --> 00:22:22.710 align:start position:0% causing panic then<00:22:20.200> proof<00:22:20.520> is<00:22:20.679> not<00:22:20.960> produced<00:22:21.760> so<00:22:22.360> this<00:22:22.559> is 00:22:22.710 --> 00:22:22.720 align:start position:0% then proof is not produced so this is 00:22:22.720 --> 00:22:25.789 align:start position:0% then proof is not produced so this is one<00:22:23.080> also<00:22:23.919> another<00:22:24.919> thing<00:22:25.120> I<00:22:25.240> mentioned<00:22:25.600> in 00:22:25.789 --> 00:22:25.799 align:start position:0% one also another thing I mentioned in 00:22:25.799 --> 00:22:29.190 align:start position:0% one also another thing I mentioned in the<00:22:26.720> slides<00:22:27.240> before<00:22:28.000> is 00:22:29.190 --> 00:22:29.200 align:start position:0% the slides before is 00:22:29.200 --> 00:22:34.990 align:start position:0% the slides before is we<00:22:29.360> need<00:22:29.520> a<00:22:29.720> way<00:22:29.919> to<00:22:30.720> like<00:22:32.080> uh<00:22:33.080> like<00:22:34.080> overcome 00:22:34.990 --> 00:22:35.000 align:start position:0% we need a way to like uh like overcome 00:22:35.000 --> 00:22:37.470 align:start position:0% we need a way to like uh like overcome like<00:22:35.279> if<00:22:35.480> the<00:22:35.640> program<00:22:35.960> panics<00:22:36.480> like<00:22:37.080> but<00:22:37.360> if 00:22:37.470 --> 00:22:37.480 align:start position:0% like if the program panics like but if 00:22:37.480 --> 00:22:39.909 align:start position:0% like if the program panics like but if it's<00:22:37.679> a<00:22:37.880> bug<00:22:38.120> inside<00:22:38.440> a<00:22:38.640> ckvm<00:22:39.320> or<00:22:39.520> if<00:22:39.600> it's<00:22:39.760> a 00:22:39.909 --> 00:22:39.919 align:start position:0% it's a bug inside a ckvm or if it's a 00:22:39.919 --> 00:22:42.669 align:start position:0% it's a bug inside a ckvm or if it's a bug<00:22:40.120> in<00:22:40.279> a<00:22:40.640> program<00:22:41.159> then<00:22:41.400> like<00:22:42.159> you<00:22:42.320> would 00:22:42.669 --> 00:22:42.679 align:start position:0% bug in a program then like you would 00:22:42.679 --> 00:22:45.549 align:start position:0% bug in a program then like you would need<00:22:42.880> to<00:22:43.080> wait<00:22:43.320> to<00:22:44.200> uh<00:22:44.480> verify<00:22:44.840> it<00:22:44.919> on<00:22:45.120> chain<00:22:45.400> or 00:22:45.549 --> 00:22:45.559 align:start position:0% need to wait to uh verify it on chain or 00:22:45.559 --> 00:22:48.789 align:start position:0% need to wait to uh verify it on chain or like<00:22:45.760> have<00:22:45.880> a<00:22:46.240> way<00:22:46.400> to<00:22:46.559> prove<00:22:46.799> it<00:22:46.919> on<00:22:47.120> chain<00:22:47.480> so 00:22:48.789 --> 00:22:48.799 align:start position:0% like have a way to prove it on chain so 00:22:48.799 --> 00:22:52.029 align:start position:0% like have a way to prove it on chain so that<00:22:49.799> so<00:22:50.039> that<00:22:50.480> Security<00:22:50.880> Council<00:22:51.279> could<00:22:51.520> like 00:22:52.029 --> 00:22:52.039 align:start position:0% that so that Security Council could like 00:22:52.039 --> 00:22:55.470 align:start position:0% that so that Security Council could like intervene<00:22:52.679> or<00:22:53.480> what<00:22:54.480> all<00:22:54.600> right<00:22:54.799> great<00:22:55.080> so<00:22:55.279> our 00:22:55.470 --> 00:22:55.480 align:start position:0% intervene or what all right great so our 00:22:55.480 --> 00:23:00.000 align:start position:0% intervene or what all right great so our time<00:22:55.679> is<00:22:55.880> up<00:22:56.200> thank<00:22:56.360> you<00:22:56.480> so<00:22:56.640> much<00:22:56.799> ta<00:22:57.799> uh