WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:05.950 align:start position:0% [Music] 00:00:05.950 --> 00:00:05.960 align:start position:0% [Music] 00:00:05.960 --> 00:00:09.310 align:start position:0% [Music] hello<00:00:06.319> everybody 00:00:09.310 --> 00:00:09.320 align:start position:0% hello everybody 00:00:09.320 --> 00:00:13.350 align:start position:0% um<00:00:10.320> we<00:00:10.719> need<00:00:11.719> fast 00:00:13.350 --> 00:00:13.360 align:start position:0% um we need fast 00:00:13.360 --> 00:00:15.509 align:start position:0% um we need fast proving<00:00:14.360> at<00:00:14.480> the<00:00:14.559> beginning<00:00:14.920> was<00:00:15.160> we<00:00:15.280> need 00:00:15.509 --> 00:00:15.519 align:start position:0% proving at the beginning was we need 00:00:15.519 --> 00:00:18.390 align:start position:0% proving at the beginning was we need proof<00:00:16.000> we<00:00:16.119> need<00:00:16.240> to<00:00:16.320> generate<00:00:17.080> proofs<00:00:18.080> at<00:00:18.199> some 00:00:18.390 --> 00:00:18.400 align:start position:0% proof we need to generate proofs at some 00:00:18.400 --> 00:00:20.429 align:start position:0% proof we need to generate proofs at some point<00:00:18.600> we<00:00:18.720> need<00:00:18.880> to<00:00:19.039> generate<00:00:19.439> cheap<00:00:19.800> proof 00:00:20.429 --> 00:00:20.439 align:start position:0% point we need to generate cheap proof 00:00:20.439 --> 00:00:23.589 align:start position:0% point we need to generate cheap proof this<00:00:20.640> was<00:00:20.920> the<00:00:21.720> beginning<00:00:22.080> of<00:00:22.240> the<00:00:22.400> zkm<00:00:23.400> but 00:00:23.589 --> 00:00:23.599 align:start position:0% this was the beginning of the zkm but 00:00:23.599 --> 00:00:25.670 align:start position:0% this was the beginning of the zkm but what<00:00:23.760> we<00:00:23.840> are<00:00:24.000> seeing<00:00:24.359> now<00:00:24.800> is<00:00:24.960> that<00:00:25.160> no<00:00:25.400> proof 00:00:25.670 --> 00:00:25.680 align:start position:0% what we are seeing now is that no proof 00:00:25.680 --> 00:00:27.310 align:start position:0% what we are seeing now is that no proof are<00:00:25.920> would<00:00:26.080> say<00:00:26.279> it's<00:00:26.480> cheap<00:00:26.840> enough 00:00:27.310 --> 00:00:27.320 align:start position:0% are would say it's cheap enough 00:00:27.320 --> 00:00:28.830 align:start position:0% are would say it's cheap enough especially<00:00:27.720> if<00:00:27.800> you<00:00:27.880> are<00:00:28.000> doing<00:00:28.160> a<00:00:28.279> rollup<00:00:28.720> and 00:00:28.830 --> 00:00:28.840 align:start position:0% especially if you are doing a rollup and 00:00:28.840 --> 00:00:30.710 align:start position:0% especially if you are doing a rollup and you<00:00:29.000> have<00:00:29.199> a<00:00:29.519> transaction<00:00:30.160> but<00:00:30.240> we<00:00:30.359> need<00:00:30.519> to 00:00:30.710 --> 00:00:30.720 align:start position:0% you have a transaction but we need to 00:00:30.720 --> 00:00:34.270 align:start position:0% you have a transaction but we need to proof<00:00:31.119> them<00:00:31.480> fast<00:00:32.480> why<00:00:32.680> we<00:00:32.840> need<00:00:33.079> fast 00:00:34.270 --> 00:00:34.280 align:start position:0% proof them fast why we need fast 00:00:34.280 --> 00:00:38.069 align:start position:0% proof them fast why we need fast proofs<00:00:35.280> I<00:00:35.360> would<00:00:35.520> say<00:00:35.719> for<00:00:35.879> many<00:00:36.399> reasons 00:00:38.069 --> 00:00:38.079 align:start position:0% proofs I would say for many reasons 00:00:38.079 --> 00:00:40.950 align:start position:0% proofs I would say for many reasons uh<00:00:39.079> the<00:00:39.320> the<00:00:39.440> reasons<00:00:39.879> I<00:00:39.960> mean<00:00:40.200> in<00:00:40.360> polygon<00:00:40.800> for 00:00:40.950 --> 00:00:40.960 align:start position:0% uh the the reasons I mean in polygon for 00:00:40.960 --> 00:00:42.470 align:start position:0% uh the the reasons I mean in polygon for example<00:00:41.200> we<00:00:41.320> need<00:00:41.480> it<00:00:41.680> very<00:00:41.840> much<00:00:42.000> for<00:00:42.160> the<00:00:42.280> ACT 00:00:42.470 --> 00:00:42.480 align:start position:0% example we need it very much for the ACT 00:00:42.480 --> 00:00:46.029 align:start position:0% example we need it very much for the ACT layer<00:00:43.160> when<00:00:43.320> you<00:00:43.760> when<00:00:43.879> you<00:00:44.039> want<00:00:44.559> to<00:00:45.559> transfer 00:00:46.029 --> 00:00:46.039 align:start position:0% layer when you when you want to transfer 00:00:46.039 --> 00:00:48.910 align:start position:0% layer when you when you want to transfer funds<00:00:46.399> from<00:00:46.559> one<00:00:46.760> chain<00:00:47.000> to<00:00:47.239> another<00:00:47.680> chain<00:00:48.680> U 00:00:48.910 --> 00:00:48.920 align:start position:0% funds from one chain to another chain U 00:00:48.920 --> 00:00:50.630 align:start position:0% funds from one chain to another chain U two<00:00:49.160> things<00:00:49.399> needs<00:00:49.640> to<00:00:49.879> happen<00:00:50.320> first<00:00:50.520> you 00:00:50.630 --> 00:00:50.640 align:start position:0% two things needs to happen first you 00:00:50.640 --> 00:00:53.029 align:start position:0% two things needs to happen first you need<00:00:50.800> to<00:00:51.199> one<00:00:51.320> chain<00:00:51.600> needs<00:00:51.800> to<00:00:51.960> commit<00:00:52.600> to<00:00:52.800> one 00:00:53.029 --> 00:00:53.039 align:start position:0% need to one chain needs to commit to one 00:00:53.039 --> 00:00:54.510 align:start position:0% need to one chain needs to commit to one state<00:00:53.320> so<00:00:53.480> that<00:00:53.600> the<00:00:53.680> other<00:00:53.879> chain<00:00:54.120> can<00:00:54.320> use 00:00:54.510 --> 00:00:54.520 align:start position:0% state so that the other chain can use 00:00:54.520 --> 00:00:56.510 align:start position:0% state so that the other chain can use the<00:00:54.600> fonts<00:00:54.879> of<00:00:55.039> the<00:00:55.160> first<00:00:55.399> chain<00:00:56.239> and<00:00:56.399> the 00:00:56.510 --> 00:00:56.520 align:start position:0% the fonts of the first chain and the 00:00:56.520 --> 00:00:57.790 align:start position:0% the fonts of the first chain and the other<00:00:56.760> thing<00:00:56.960> is<00:00:57.079> that<00:00:57.239> the<00:00:57.359> second<00:00:57.600> chain 00:00:57.790 --> 00:00:57.800 align:start position:0% other thing is that the second chain 00:00:57.800 --> 00:01:00.029 align:start position:0% other thing is that the second chain needs<00:00:58.000> to<00:00:58.120> be<00:00:58.239> sure<00:00:58.559> that<00:00:59.079> this<00:00:59.320> state<00:00:59.600> is 00:01:00.029 --> 00:01:00.039 align:start position:0% needs to be sure that this state is 00:01:00.039 --> 00:01:03.750 align:start position:0% needs to be sure that this state is correct<00:01:00.879> okay<00:01:01.359> so<00:01:01.680> it<00:01:01.840> has<00:01:02.039> two<00:01:02.640> options<00:01:03.640> the 00:01:03.750 --> 00:01:03.760 align:start position:0% correct okay so it has two options the 00:01:03.760 --> 00:01:05.390 align:start position:0% correct okay so it has two options the first<00:01:03.960> thing<00:01:04.119> is<00:01:04.199> that<00:01:04.400> the<00:01:04.640> second<00:01:04.920> chain 00:01:05.390 --> 00:01:05.400 align:start position:0% first thing is that the second chain 00:01:05.400 --> 00:01:08.070 align:start position:0% first thing is that the second chain just<00:01:05.880> follows<00:01:06.360> that<00:01:06.520> chain<00:01:07.119> and<00:01:07.400> then<00:01:07.640> warant 00:01:08.070 --> 00:01:08.080 align:start position:0% just follows that chain and then warant 00:01:08.080 --> 00:01:10.510 align:start position:0% just follows that chain and then warant is<00:01:08.240> that<00:01:08.439> this<00:01:08.720> this<00:01:08.960> this<00:01:09.159> state<00:01:09.439> is<00:01:09.600> correct 00:01:10.510 --> 00:01:10.520 align:start position:0% is that this this this state is correct 00:01:10.520 --> 00:01:13.390 align:start position:0% is that this this this state is correct or<00:01:10.960> the<00:01:11.119> other<00:01:11.360> option<00:01:12.040> is<00:01:12.200> that<00:01:12.439> the<00:01:12.600> chain<00:01:12.880> a 00:01:13.390 --> 00:01:13.400 align:start position:0% or the other option is that the chain a 00:01:13.400 --> 00:01:15.950 align:start position:0% or the other option is that the chain a provides<00:01:14.119> uh<00:01:14.320> zero<00:01:14.600> knowledge<00:01:14.920> proof<00:01:15.280> that<00:01:15.720> uh 00:01:15.950 --> 00:01:15.960 align:start position:0% provides uh zero knowledge proof that uh 00:01:15.960 --> 00:01:19.429 align:start position:0% provides uh zero knowledge proof that uh his<00:01:16.200> state<00:01:16.600> is<00:01:17.000> correct<00:01:18.000> in<00:01:18.119> the<00:01:18.280> first<00:01:18.600> case 00:01:19.429 --> 00:01:19.439 align:start position:0% his state is correct in the first case 00:01:19.439 --> 00:01:20.950 align:start position:0% his state is correct in the first case well<00:01:19.640> it<00:01:19.759> works<00:01:20.079> well<00:01:20.280> maybe<00:01:20.479> if<00:01:20.560> you<00:01:20.680> have<00:01:20.799> two 00:01:20.950 --> 00:01:20.960 align:start position:0% well it works well maybe if you have two 00:01:20.960 --> 00:01:22.749 align:start position:0% well it works well maybe if you have two networks<00:01:21.439> but<00:01:21.560> if<00:01:21.680> you<00:01:21.799> have<00:01:22.079> hundreds<00:01:22.520> or 00:01:22.749 --> 00:01:22.759 align:start position:0% networks but if you have hundreds or 00:01:22.759 --> 00:01:24.310 align:start position:0% networks but if you have hundreds or thousands<00:01:23.119> of<00:01:23.280> networks<00:01:23.680> that<00:01:23.840> are<00:01:24.000> appearing 00:01:24.310 --> 00:01:24.320 align:start position:0% thousands of networks that are appearing 00:01:24.320 --> 00:01:26.350 align:start position:0% thousands of networks that are appearing or<00:01:24.479> disappearing<00:01:25.000> every<00:01:25.240> time<00:01:25.799> it<00:01:25.960> does<00:01:26.159> not 00:01:26.350 --> 00:01:26.360 align:start position:0% or disappearing every time it does not 00:01:26.360 --> 00:01:29.550 align:start position:0% or disappearing every time it does not scale<00:01:26.799> well<00:01:27.240> I<00:01:27.280> mean<00:01:27.479> you<00:01:27.640> cannot<00:01:28.159> ask<00:01:28.560> all<00:01:28.799> the 00:01:29.550 --> 00:01:29.560 align:start position:0% scale well I mean you cannot ask all the 00:01:29.560 --> 00:01:31.310 align:start position:0% scale well I mean you cannot ask all the all<00:01:29.720> the<00:01:30.079> all<00:01:30.240> the<00:01:30.400> all<00:01:30.520> the<00:01:30.680> validators<00:01:31.159> of 00:01:31.310 --> 00:01:31.320 align:start position:0% all the all the all the validators of 00:01:31.320 --> 00:01:33.550 align:start position:0% all the all the all the validators of all<00:01:31.439> the<00:01:31.560> chains<00:01:31.840> to<00:01:32.000> run<00:01:32.439> a<00:01:32.680> validator<00:01:33.240> of<00:01:33.399> all 00:01:33.550 --> 00:01:33.560 align:start position:0% all the chains to run a validator of all 00:01:33.560 --> 00:01:34.630 align:start position:0% all the chains to run a validator of all the<00:01:33.680> other<00:01:33.840> chains<00:01:34.200> that<00:01:34.320> are<00:01:34.439> in<00:01:34.520> the 00:01:34.630 --> 00:01:34.640 align:start position:0% the other chains that are in the 00:01:34.640 --> 00:01:37.149 align:start position:0% the other chains that are in the aggregation<00:01:35.079> space<00:01:35.640> so<00:01:35.880> the<00:01:36.000> way<00:01:36.200> to<00:01:36.799> the<00:01:36.960> way 00:01:37.149 --> 00:01:37.159 align:start position:0% aggregation space so the way to the way 00:01:37.159 --> 00:01:40.789 align:start position:0% aggregation space so the way to the way to<00:01:38.119> uh<00:01:38.680> U<00:01:39.079> scale<00:01:39.479> that<00:01:39.759> is<00:01:39.920> by<00:01:40.200> having<00:01:40.399> a<00:01:40.520> zero 00:01:40.789 --> 00:01:40.799 align:start position:0% to uh U scale that is by having a zero 00:01:40.799 --> 00:01:42.950 align:start position:0% to uh U scale that is by having a zero knowledge<00:01:41.119> proof<00:01:41.520> that<00:01:41.960> uh<00:01:42.079> warrant<00:01:42.520> is<00:01:42.640> at 00:01:42.950 --> 00:01:42.960 align:start position:0% knowledge proof that uh warrant is at 00:01:42.960 --> 00:01:47.270 align:start position:0% knowledge proof that uh warrant is at state<00:01:43.280> is<00:01:43.479> valid<00:01:44.399> this<00:01:44.560> is<00:01:45.200> um<00:01:45.799> um<00:01:46.719> and<00:01:46.920> then 00:01:47.270 --> 00:01:47.280 align:start position:0% state is valid this is um um and then 00:01:47.280 --> 00:01:49.310 align:start position:0% state is valid this is um um and then but<00:01:47.439> then<00:01:47.680> this<00:01:47.880> means<00:01:48.240> that<00:01:48.479> the<00:01:48.600> user<00:01:49.159> when 00:01:49.310 --> 00:01:49.320 align:start position:0% but then this means that the user when 00:01:49.320 --> 00:01:52.190 align:start position:0% but then this means that the user when he's<00:01:49.520> doing<00:01:49.759> some<00:01:50.040> interchain<00:01:51.119> communication 00:01:52.190 --> 00:01:52.200 align:start position:0% he's doing some interchain communication 00:01:52.200 --> 00:01:56.109 align:start position:0% he's doing some interchain communication uh<00:01:53.200> in<00:01:53.360> the<00:01:53.520> user<00:01:54.240> in<00:01:54.360> the<00:01:54.479> user<00:01:55.399> interaction<00:01:56.039> I 00:01:56.109 --> 00:01:56.119 align:start position:0% uh in the user in the user interaction I 00:01:56.119 --> 00:01:58.550 align:start position:0% uh in the user in the user interaction I mean<00:01:56.280> in<00:01:56.399> the<00:01:56.520> user<00:01:57.079> in<00:01:57.200> the<00:01:57.320> ux<00:01:58.000> you<00:01:58.119> will<00:01:58.280> need 00:01:58.550 --> 00:01:58.560 align:start position:0% mean in the user in the ux you will need 00:01:58.560 --> 00:02:00.910 align:start position:0% mean in the user in the ux you will need this<00:01:59.000> uh<00:01:59.200> you<00:01:59.360> need<00:01:59.479> to<00:01:59.600> Wi<00:01:59.920> for<00:02:00.079> this<00:02:00.320> time 00:02:00.910 --> 00:02:00.920 align:start position:0% this uh you need to Wi for this time 00:02:00.920 --> 00:02:04.270 align:start position:0% this uh you need to Wi for this time okay<00:02:01.119> so<00:02:01.680> and<00:02:02.399> uh<00:02:02.799> so<00:02:02.960> we<00:02:03.079> need<00:02:03.280> to<00:02:03.840> generate 00:02:04.270 --> 00:02:04.280 align:start position:0% okay so and uh so we need to generate 00:02:04.280 --> 00:02:06.830 align:start position:0% okay so and uh so we need to generate these<00:02:04.439> proofs<00:02:04.840> as<00:02:05.039> fast<00:02:05.280> as<00:02:05.439> you<00:02:05.600> want<00:02:06.520> other 00:02:06.830 --> 00:02:06.840 align:start position:0% these proofs as fast as you want other 00:02:06.840 --> 00:02:09.669 align:start position:0% these proofs as fast as you want other context<00:02:07.479> I<00:02:07.560> mean<00:02:07.759> yesterday<00:02:08.319> in<00:02:08.759> uh<00:02:08.920> in<00:02:09.160> the 00:02:09.669 --> 00:02:09.679 align:start position:0% context I mean yesterday in uh in the 00:02:09.679 --> 00:02:12.390 align:start position:0% context I mean yesterday in uh in the presentation<00:02:10.119> of<00:02:10.239> The<00:02:10.399> Bean<00:02:10.640> chain<00:02:11.280> was<00:02:11.440> a<00:02:11.599> ZK 00:02:12.390 --> 00:02:12.400 align:start position:0% presentation of The Bean chain was a ZK 00:02:12.400 --> 00:02:14.270 align:start position:0% presentation of The Bean chain was a ZK uh<00:02:12.520> chain<00:02:12.920> so<00:02:13.120> that<00:02:13.239> means<00:02:13.520> that<00:02:13.760> in<00:02:13.920> in<00:02:14.080> this 00:02:14.270 --> 00:02:14.280 align:start position:0% uh chain so that means that in in this 00:02:14.280 --> 00:02:16.150 align:start position:0% uh chain so that means that in in this context<00:02:14.640> you<00:02:14.760> need<00:02:15.000> a<00:02:15.120> lot<00:02:15.280> of<00:02:15.440> places<00:02:15.959> like 00:02:16.150 --> 00:02:16.160 align:start position:0% context you need a lot of places like 00:02:16.160 --> 00:02:18.150 align:start position:0% context you need a lot of places like clients<00:02:16.519> needs<00:02:16.720> to<00:02:16.920> validate<00:02:17.480> so<00:02:17.680> needs<00:02:17.959> to 00:02:18.150 --> 00:02:18.160 align:start position:0% clients needs to validate so needs to 00:02:18.160 --> 00:02:20.229 align:start position:0% clients needs to validate so needs to prove<00:02:18.480> that<00:02:18.680> the<00:02:19.080> the<00:02:19.200> full<00:02:19.440> execution<00:02:19.879> chain 00:02:20.229 --> 00:02:20.239 align:start position:0% prove that the the full execution chain 00:02:20.239 --> 00:02:22.470 align:start position:0% prove that the the full execution chain it's<00:02:20.440> another<00:02:20.840> case<00:02:21.120> that's<00:02:21.760> important<00:02:22.200> so<00:02:22.360> in 00:02:22.470 --> 00:02:22.480 align:start position:0% it's another case that's important so in 00:02:22.480 --> 00:02:25.869 align:start position:0% it's another case that's important so in many<00:02:22.800> cases<00:02:23.480> this<00:02:23.720> chain<00:02:24.720> uh<00:02:25.120> so<00:02:25.400> generating 00:02:25.869 --> 00:02:25.879 align:start position:0% many cases this chain uh so generating 00:02:25.879 --> 00:02:28.990 align:start position:0% many cases this chain uh so generating fast<00:02:26.200> proof<00:02:26.519> is<00:02:26.680> important<00:02:27.360> so<00:02:27.599> how<00:02:27.879> fast<00:02:28.760> can 00:02:28.990 --> 00:02:29.000 align:start position:0% fast proof is important so how fast can 00:02:29.000 --> 00:02:32.270 align:start position:0% fast proof is important so how fast can we<00:02:29.200> go<00:02:29.959> and<00:02:30.720> I<00:02:30.800> want<00:02:30.959> to<00:02:31.160> present<00:02:31.560> here<00:02:31.840> so<00:02:32.120> an 00:02:32.270 --> 00:02:32.280 align:start position:0% we go and I want to present here so an 00:02:32.280 --> 00:02:33.589 align:start position:0% we go and I want to present here so an internal<00:02:32.720> project<00:02:33.040> that<00:02:33.160> we<00:02:33.280> have<00:02:33.440> been 00:02:33.589 --> 00:02:33.599 align:start position:0% internal project that we have been 00:02:33.599 --> 00:02:36.949 align:start position:0% internal project that we have been working<00:02:33.920> for<00:02:34.760> uh<00:02:34.920> the<00:02:35.080> last<00:02:35.720> five<00:02:36.000> six<00:02:36.239> months 00:02:36.949 --> 00:02:36.959 align:start position:0% working for uh the last five six months 00:02:36.959 --> 00:02:39.390 align:start position:0% working for uh the last five six months uh<00:02:37.120> inside<00:02:37.519> ethereum<00:02:38.239> we<00:02:38.400> call<00:02:38.560> it<00:02:38.680> internally 00:02:39.390 --> 00:02:39.400 align:start position:0% uh inside ethereum we call it internally 00:02:39.400 --> 00:02:42.070 align:start position:0% uh inside ethereum we call it internally zisk<00:02:40.200> and<00:02:40.360> is<00:02:40.840> very<00:02:41.040> much<00:02:41.239> about<00:02:41.480> that<00:02:41.720> is<00:02:41.879> how 00:02:42.070 --> 00:02:42.080 align:start position:0% zisk and is very much about that is how 00:02:42.080 --> 00:02:45.550 align:start position:0% zisk and is very much about that is how much<00:02:42.440> we<00:02:42.599> can<00:02:42.879> push<00:02:43.440> the<00:02:43.599> proving<00:02:44.159> system<00:02:45.159> zis 00:02:45.550 --> 00:02:45.560 align:start position:0% much we can push the proving system zis 00:02:45.560 --> 00:02:48.630 align:start position:0% much we can push the proving system zis is<00:02:45.680> also<00:02:46.080> based<00:02:46.680> U<00:02:46.959> it's<00:02:47.080> a<00:02:47.280> system<00:02:47.640> that<00:02:47.840> can 00:02:48.630 --> 00:02:48.640 align:start position:0% is also based U it's a system that can 00:02:48.640 --> 00:02:51.070 align:start position:0% is also based U it's a system that can uh<00:02:48.800> prove<00:02:49.400> u<00:02:49.760> i<00:02:49.879> mean<00:02:50.000> you<00:02:50.120> can<00:02:50.239> build<00:02:50.440> a<00:02:50.599> pro 00:02:51.070 --> 00:02:51.080 align:start position:0% uh prove u i mean you can build a pro 00:02:51.080 --> 00:02:53.309 align:start position:0% uh prove u i mean you can build a pro programming<00:02:51.480> rust<00:02:51.800> it's<00:02:51.920> a<00:02:52.120> r<00:02:52.440> five<00:02:53.120> uh 00:02:53.309 --> 00:02:53.319 align:start position:0% programming rust it's a r five uh 00:02:53.319 --> 00:02:55.990 align:start position:0% programming rust it's a r five uh compiler<00:02:53.760> is<00:02:53.920> a<00:02:54.040> r<00:02:54.239> 564<00:02:54.840> bits<00:02:55.560> it's<00:02:55.720> a<00:02:55.840> little 00:02:55.990 --> 00:02:56.000 align:start position:0% compiler is a r 564 bits it's a little 00:02:56.000 --> 00:02:58.309 align:start position:0% compiler is a r 564 bits it's a little bit<00:02:56.200> different<00:02:56.680> from<00:02:56.959> other<00:02:57.360> projects<00:02:58.200> but 00:02:58.309 --> 00:02:58.319 align:start position:0% bit different from other projects but 00:02:58.319 --> 00:03:00.470 align:start position:0% bit different from other projects but the<00:02:58.440> full<00:02:58.640> idea<00:02:58.920> of<00:02:59.040> this<00:02:59.239> project<00:02:59.920> is<00:03:00.159> how 00:03:00.470 --> 00:03:00.480 align:start position:0% the full idea of this project is how 00:03:00.480 --> 00:03:04.630 align:start position:0% the full idea of this project is how fast<00:03:01.200> can<00:03:01.480> we<00:03:02.280> uh<00:03:02.480> can<00:03:02.599> we<00:03:02.799> move<00:03:03.799> how<00:03:03.959> short<00:03:04.480> how 00:03:04.630 --> 00:03:04.640 align:start position:0% fast can we uh can we move how short how 00:03:04.640 --> 00:03:06.710 align:start position:0% fast can we uh can we move how short how fast<00:03:04.840> can<00:03:04.959> we<00:03:05.120> generate<00:03:05.480> this<00:03:05.680> proof<00:03:06.440> this 00:03:06.710 --> 00:03:06.720 align:start position:0% fast can we generate this proof this 00:03:06.720 --> 00:03:08.630 align:start position:0% fast can we generate this proof this actually<00:03:07.080> are<00:03:07.360> this<00:03:08.000> three<00:03:08.239> different<00:03:08.560> I 00:03:08.630 --> 00:03:08.640 align:start position:0% actually are this three different I 00:03:08.640 --> 00:03:10.789 align:start position:0% actually are this three different I would<00:03:08.799> say<00:03:09.080> three<00:03:09.560> different<00:03:10.120> pieces<00:03:10.599> or 00:03:10.789 --> 00:03:10.799 align:start position:0% would say three different pieces or 00:03:10.799 --> 00:03:13.229 align:start position:0% would say three different pieces or three<00:03:11.040> different<00:03:11.560> projects<00:03:12.080> itself<00:03:12.920> one<00:03:13.080> is 00:03:13.229 --> 00:03:13.239 align:start position:0% three different projects itself one is 00:03:13.239 --> 00:03:16.509 align:start position:0% three different projects itself one is the<00:03:13.400> pr<00:03:13.879> itself<00:03:14.799> Pro<00:03:15.120> is<00:03:15.200> a<00:03:15.360> generic<00:03:15.799> Pro<00:03:16.319> so 00:03:16.509 --> 00:03:16.519 align:start position:0% the pr itself Pro is a generic Pro so 00:03:16.519 --> 00:03:18.670 align:start position:0% the pr itself Pro is a generic Pro so the<00:03:16.640> idea<00:03:16.920> is<00:03:17.040> that<00:03:17.239> you<00:03:17.360> can<00:03:17.640> build<00:03:18.280> uh<00:03:18.400> your 00:03:18.670 --> 00:03:18.680 align:start position:0% the idea is that you can build uh your 00:03:18.680 --> 00:03:21.430 align:start position:0% the idea is that you can build uh your own<00:03:18.959> Pro<00:03:19.680> that<00:03:19.879> can<00:03:20.080> proves<00:03:20.599> anything<00:03:21.280> which 00:03:21.430 --> 00:03:21.440 align:start position:0% own Pro that can proves anything which 00:03:21.440 --> 00:03:23.589 align:start position:0% own Pro that can proves anything which say<00:03:21.599> It's<00:03:21.799> Kind<00:03:21.959> the<00:03:22.080> hardware<00:03:22.480> layer<00:03:23.159> you<00:03:23.400> you 00:03:23.589 --> 00:03:23.599 align:start position:0% say It's Kind the hardware layer you you 00:03:23.599 --> 00:03:25.630 align:start position:0% say It's Kind the hardware layer you you we<00:03:23.720> have<00:03:23.920> the<00:03:24.080> pill<00:03:24.319> two<00:03:24.680> pill<00:03:24.920> two<00:03:25.120> is<00:03:25.280> based 00:03:25.630 --> 00:03:25.640 align:start position:0% we have the pill two pill two is based 00:03:25.640 --> 00:03:30.589 align:start position:0% we have the pill two pill two is based on<00:03:26.640> um<00:03:27.480> pill<00:03:27.720> two<00:03:27.959> is<00:03:28.120> based<00:03:28.439> on<00:03:29.400> um<00:03:30.159> the<00:03:30.360> pill 00:03:30.589 --> 00:03:30.599 align:start position:0% on um pill two is based on um the pill 00:03:30.599 --> 00:03:32.990 align:start position:0% on um pill two is based on um the pill one<00:03:30.840> language<00:03:31.239> that<00:03:31.360> we<00:03:31.480> use<00:03:31.640> in<00:03:31.799> the<00:03:32.000> zbm<00:03:32.840> and 00:03:32.990 --> 00:03:33.000 align:start position:0% one language that we use in the zbm and 00:03:33.000 --> 00:03:35.350 align:start position:0% one language that we use in the zbm and allows<00:03:33.280> you<00:03:33.400> to<00:03:33.519> do<00:03:33.680> an<00:03:33.840> arithmetization<00:03:34.400> and 00:03:35.350 --> 00:03:35.360 align:start position:0% allows you to do an arithmetization and 00:03:35.360 --> 00:03:38.190 align:start position:0% allows you to do an arithmetization and way<00:03:35.560> we<00:03:35.680> extended<00:03:36.080> a<00:03:36.200> lot<00:03:36.319> of<00:03:36.519> the<00:03:37.000> a<00:03:37.120> lot<00:03:37.640> uh<00:03:37.959> of 00:03:38.190 --> 00:03:38.200 align:start position:0% way we extended a lot of the a lot uh of 00:03:38.200 --> 00:03:40.789 align:start position:0% way we extended a lot of the a lot uh of the<00:03:39.040> we<00:03:39.239> extended<00:03:39.640> a<00:03:39.720> lot<00:03:40.159> the<00:03:40.400> pill<00:03:40.640> to 00:03:40.789 --> 00:03:40.799 align:start position:0% the we extended a lot the pill to 00:03:40.799 --> 00:03:43.990 align:start position:0% the we extended a lot the pill to language<00:03:41.400> the<00:03:41.680> the<00:03:41.760> pill<00:03:41.920> to<00:03:42.400> language<00:03:43.400> uh<00:03:43.920> I 00:03:43.990 --> 00:03:44.000 align:start position:0% language the the pill to language uh I 00:03:44.000 --> 00:03:47.190 align:start position:0% language the the pill to language uh I mean<00:03:44.319> making<00:03:44.680> them<00:03:44.920> more<00:03:45.280> easy<00:03:45.760> for<00:03:46.200> auditing 00:03:47.190 --> 00:03:47.200 align:start position:0% mean making them more easy for auditing 00:03:47.200 --> 00:03:50.070 align:start position:0% mean making them more easy for auditing uh<00:03:47.400> this<00:03:47.599> arithmetization<00:03:48.480> and<00:03:49.480> mainly 00:03:50.070 --> 00:03:50.080 align:start position:0% uh this arithmetization and mainly 00:03:50.080 --> 00:03:52.470 align:start position:0% uh this arithmetization and mainly including<00:03:51.080> um<00:03:51.599> one<00:03:51.799> thing<00:03:52.000> that's<00:03:52.200> called 00:03:52.470 --> 00:03:52.480 align:start position:0% including um one thing that's called 00:03:52.480 --> 00:03:55.030 align:start position:0% including um one thing that's called vcops<00:03:53.200> that<00:03:53.360> mainly<00:03:53.959> means<00:03:54.319> that<00:03:54.519> instead<00:03:54.840> of 00:03:55.030 --> 00:03:55.040 align:start position:0% vcops that mainly means that instead of 00:03:55.040 --> 00:03:57.710 align:start position:0% vcops that mainly means that instead of having<00:03:55.799> uh<00:03:55.959> monolithic<00:03:56.560> proof<00:03:57.000> we<00:03:57.159> can<00:03:57.400> divide 00:03:57.710 --> 00:03:57.720 align:start position:0% having uh monolithic proof we can divide 00:03:57.720 --> 00:03:59.830 align:start position:0% having uh monolithic proof we can divide the<00:03:57.879> proof<00:03:58.239> in<00:03:58.439> sub<00:03:58.760> proofs<00:03:59.280> this<00:03:59.360> is<00:03:59.480> very 00:03:59.830 --> 00:03:59.840 align:start position:0% the proof in sub proofs this is very 00:03:59.840 --> 00:04:01.309 align:start position:0% the proof in sub proofs this is very important<00:04:00.159> because<00:04:00.360> then<00:04:00.519> we<00:04:00.599> can<00:04:00.799> paralyze 00:04:01.309 --> 00:04:01.319 align:start position:0% important because then we can paralyze 00:04:01.319 --> 00:04:02.949 align:start position:0% important because then we can paralyze very<00:04:01.480> well<00:04:01.879> so<00:04:02.000> we<00:04:02.120> have<00:04:02.239> a<00:04:02.360> proof<00:04:02.599> we<00:04:02.720> divide 00:04:02.949 --> 00:04:02.959 align:start position:0% very well so we have a proof we divide 00:04:02.959 --> 00:04:04.670 align:start position:0% very well so we have a proof we divide the<00:04:03.120> work<00:04:03.360> in<00:04:03.519> different<00:04:03.760> sub<00:04:04.000> proofs<00:04:04.519> and 00:04:04.670 --> 00:04:04.680 align:start position:0% the work in different sub proofs and 00:04:04.680 --> 00:04:06.670 align:start position:0% the work in different sub proofs and then<00:04:04.799> we<00:04:04.959> aggregate<00:04:05.400> them<00:04:05.760> together<00:04:06.319> this<00:04:06.439> is 00:04:06.670 --> 00:04:06.680 align:start position:0% then we aggregate them together this is 00:04:06.680 --> 00:04:09.670 align:start position:0% then we aggregate them together this is the<00:04:07.079> main<00:04:07.400> idea<00:04:07.920> of<00:04:08.079> how<00:04:08.239> we<00:04:08.360> can<00:04:08.720> accelerate 00:04:09.670 --> 00:04:09.680 align:start position:0% the main idea of how we can accelerate 00:04:09.680 --> 00:04:14.949 align:start position:0% the main idea of how we can accelerate uh<00:04:10.519> uh<00:04:11.040> the<00:04:11.200> things<00:04:12.040> okay<00:04:12.439> so<00:04:13.400> the<00:04:13.799> the<00:04:13.959> pro<00:04:14.879> I 00:04:14.949 --> 00:04:14.959 align:start position:0% uh uh the things okay so the the pro I 00:04:14.959 --> 00:04:17.469 align:start position:0% uh uh the things okay so the the pro I mean<00:04:15.120> it's<00:04:15.200> a<00:04:15.319> generic<00:04:15.760> Pro<00:04:16.560> so<00:04:16.840> how<00:04:17.079> it<00:04:17.239> would 00:04:17.469 --> 00:04:17.479 align:start position:0% mean it's a generic Pro so how it would 00:04:17.479 --> 00:04:20.189 align:start position:0% mean it's a generic Pro so how it would work<00:04:17.919> okay<00:04:18.120> this<00:04:18.199> is<00:04:18.359> the<00:04:18.639> process<00:04:19.519> that<00:04:20.079> if 00:04:20.189 --> 00:04:20.199 align:start position:0% work okay this is the process that if 00:04:20.199 --> 00:04:23.189 align:start position:0% work okay this is the process that if you<00:04:20.320> want<00:04:20.479> to<00:04:20.639> build<00:04:21.160> a<00:04:21.840> any<00:04:22.199> proof<00:04:22.800> it<00:04:22.919> can<00:04:23.080> be 00:04:23.189 --> 00:04:23.199 align:start position:0% you want to build a any proof it can be 00:04:23.199 --> 00:04:24.950 align:start position:0% you want to build a any proof it can be from<00:04:23.320> a<00:04:23.440> fibon<00:04:24.040> serious<00:04:24.360> if<00:04:24.479> it's<00:04:24.600> the<00:04:24.720> kind<00:04:24.880> of 00:04:24.950 --> 00:04:24.960 align:start position:0% from a fibon serious if it's the kind of 00:04:24.960 --> 00:04:28.189 align:start position:0% from a fibon serious if it's the kind of a<00:04:25.080> Hello<00:04:25.320> World<00:04:25.759> until<00:04:26.759> uh<00:04:27.199> I<00:04:27.280> mean<00:04:27.479> a<00:04:27.600> VM 00:04:28.189 --> 00:04:28.199 align:start position:0% a Hello World until uh I mean a VM 00:04:28.199 --> 00:04:30.390 align:start position:0% a Hello World until uh I mean a VM project<00:04:28.639> that's<00:04:28.840> in<00:04:29.080> there<00:04:29.720> or<00:04:29.840> maybe<00:04:30.080> some 00:04:30.390 --> 00:04:30.400 align:start position:0% project that's in there or maybe some 00:04:30.400 --> 00:04:32.110 align:start position:0% project that's in there or maybe some whatever<00:04:30.720> you<00:04:30.800> want<00:04:30.960> to<00:04:31.120> build<00:04:31.800> mainly<00:04:32.039> you 00:04:32.110 --> 00:04:32.120 align:start position:0% whatever you want to build mainly you 00:04:32.120 --> 00:04:33.670 align:start position:0% whatever you want to build mainly you need<00:04:32.280> to<00:04:32.400> build<00:04:32.639> two<00:04:32.840> things<00:04:33.199> so<00:04:33.360> you<00:04:33.440> need<00:04:33.600> to 00:04:33.670 --> 00:04:33.680 align:start position:0% need to build two things so you need to 00:04:33.680 --> 00:04:36.270 align:start position:0% need to build two things so you need to build<00:04:33.960> armatization<00:04:34.960> the<00:04:35.080> aration<00:04:35.880> is<00:04:36.039> in 00:04:36.270 --> 00:04:36.280 align:start position:0% build armatization the aration is in 00:04:36.280 --> 00:04:39.909 align:start position:0% build armatization the aration is in this<00:04:36.840> um<00:04:37.240> in<00:04:37.400> the<00:04:37.919> in<00:04:38.120> this<00:04:38.680> uh<00:04:39.199> so<00:04:39.560> we<00:04:39.720> just 00:04:39.909 --> 00:04:39.919 align:start position:0% this um in the in this uh so we just 00:04:39.919 --> 00:04:41.950 align:start position:0% this um in the in this uh so we just write<00:04:40.120> the<00:04:40.280> pill<00:04:40.759> so<00:04:41.000> is<00:04:41.160> are<00:04:41.280> in<00:04:41.400> meditation 00:04:41.950 --> 00:04:41.960 align:start position:0% write the pill so is are in meditation 00:04:41.960 --> 00:04:44.310 align:start position:0% write the pill so is are in meditation itself<00:04:42.880> you<00:04:43.000> need<00:04:43.160> to<00:04:43.360> write<00:04:43.880> what<00:04:44.000> we<00:04:44.120> call 00:04:44.310 --> 00:04:44.320 align:start position:0% itself you need to write what we call 00:04:44.320 --> 00:04:45.749 align:start position:0% itself you need to write what we call the<00:04:44.400> windows<00:04:44.759> computation<00:04:45.320> this<00:04:45.440> is<00:04:45.520> at<00:04:45.680> the 00:04:45.749 --> 00:04:45.759 align:start position:0% the windows computation this is at the 00:04:45.759 --> 00:04:47.590 align:start position:0% the windows computation this is at the end<00:04:45.919> is<00:04:46.039> filling<00:04:46.759> it's<00:04:46.919> a<00:04:47.080> program<00:04:47.400> that's 00:04:47.590 --> 00:04:47.600 align:start position:0% end is filling it's a program that's 00:04:47.600 --> 00:04:51.230 align:start position:0% end is filling it's a program that's actually<00:04:47.840> filling<00:04:48.800> um<00:04:49.120> the<00:04:49.280> trace<00:04:50.280> of<00:04:50.520> this 00:04:51.230 --> 00:04:51.240 align:start position:0% actually filling um the trace of this 00:04:51.240 --> 00:04:52.909 align:start position:0% actually filling um the trace of this and<00:04:51.360> that's<00:04:51.560> very<00:04:51.759> much<00:04:52.240> and<00:04:52.440> with<00:04:52.600> that<00:04:52.759> you 00:04:52.909 --> 00:04:52.919 align:start position:0% and that's very much and with that you 00:04:52.919 --> 00:04:56.230 align:start position:0% and that's very much and with that you already<00:04:53.199> have<00:04:53.400> a<00:04:54.280> so<00:04:54.479> with<00:04:54.720> this<00:04:55.600> um<00:04:55.919> well<00:04:56.080> you 00:04:56.230 --> 00:04:56.240 align:start position:0% already have a so with this um well you 00:04:56.240 --> 00:04:58.670 align:start position:0% already have a so with this um well you compile<00:04:56.600> the<00:04:56.720> pill<00:04:57.360> okay<00:04:57.520> so<00:04:57.720> you<00:04:57.880> get<00:04:58.160> a<00:04:58.520> kind 00:04:58.670 --> 00:04:58.680 align:start position:0% compile the pill okay so you get a kind 00:04:58.680 --> 00:05:01.230 align:start position:0% compile the pill okay so you get a kind of<00:04:58.759> a<00:04:58.919> pill<00:04:59.120> out<00:04:59.320> format<00:05:00.080> you<00:05:00.280> get<00:05:00.520> the<00:05:00.800> rust 00:05:01.230 --> 00:05:01.240 align:start position:0% of a pill out format you get the rust 00:05:01.240 --> 00:05:03.830 align:start position:0% of a pill out format you get the rust you<00:05:01.440> compile<00:05:02.440> uh<00:05:02.720> a<00:05:02.880> library<00:05:03.280> I<00:05:03.360> mean<00:05:03.520> you<00:05:03.680> get 00:05:03.830 --> 00:05:03.840 align:start position:0% you compile uh a library I mean you get 00:05:03.840 --> 00:05:06.390 align:start position:0% you compile uh a library I mean you get a<00:05:04.120> a<00:05:04.360> dynamic<00:05:04.840> Library<00:05:05.639> okay<00:05:05.840> from<00:05:06.000> the<00:05:06.160> pill 00:05:06.390 --> 00:05:06.400 align:start position:0% a a dynamic Library okay from the pill 00:05:06.400 --> 00:05:08.670 align:start position:0% a a dynamic Library okay from the pill you<00:05:06.600> get<00:05:06.800> some<00:05:07.280> helpers<00:05:07.800> so<00:05:08.000> that<00:05:08.199> allows<00:05:08.520> you 00:05:08.670 --> 00:05:08.680 align:start position:0% you get some helpers so that allows you 00:05:08.680 --> 00:05:11.870 align:start position:0% you get some helpers so that allows you to<00:05:09.280> build<00:05:09.680> this<00:05:10.039> Windows<00:05:10.440> computation<00:05:10.960> easily 00:05:11.870 --> 00:05:11.880 align:start position:0% to build this Windows computation easily 00:05:11.880 --> 00:05:13.950 align:start position:0% to build this Windows computation easily okay<00:05:12.360> and<00:05:12.479> then<00:05:12.720> here<00:05:12.880> we<00:05:13.039> just<00:05:13.199> run<00:05:13.440> a<00:05:13.600> normal 00:05:13.950 --> 00:05:13.960 align:start position:0% okay and then here we just run a normal 00:05:13.960 --> 00:05:16.710 align:start position:0% okay and then here we just run a normal setup<00:05:14.400> Pro<00:05:14.919> setup<00:05:15.680> here<00:05:15.800> the<00:05:15.960> setup<00:05:16.320> is<00:05:16.479> the 00:05:16.710 --> 00:05:16.720 align:start position:0% setup Pro setup here the setup is the 00:05:16.720 --> 00:05:19.189 align:start position:0% setup Pro setup here the setup is the configuration<00:05:17.400> of<00:05:17.600> the<00:05:17.720> pr<00:05:18.120> itself<00:05:18.440> some 00:05:19.189 --> 00:05:19.199 align:start position:0% configuration of the pr itself some 00:05:19.199 --> 00:05:21.629 align:start position:0% configuration of the pr itself some Starks<00:05:20.199> configuration<00:05:20.960> that's<00:05:21.199> just<00:05:21.360> a 00:05:21.629 --> 00:05:21.639 align:start position:0% Starks configuration that's just a 00:05:21.639 --> 00:05:23.350 align:start position:0% Starks configuration that's just a configuration<00:05:22.199> file<00:05:22.639> here<00:05:22.800> we<00:05:22.960> generate<00:05:23.280> a 00:05:23.350 --> 00:05:23.360 align:start position:0% configuration file here we generate a 00:05:23.360 --> 00:05:24.950 align:start position:0% configuration file here we generate a normal<00:05:23.680> approving<00:05:24.039> key<00:05:24.240> and<00:05:24.360> a<00:05:24.680> and<00:05:24.800> a 00:05:24.950 --> 00:05:24.960 align:start position:0% normal approving key and a and a 00:05:24.960 --> 00:05:26.710 align:start position:0% normal approving key and a and a verification<00:05:25.520> key<00:05:26.080> and<00:05:26.199> then<00:05:26.360> we<00:05:26.479> have<00:05:26.600> the 00:05:26.710 --> 00:05:26.720 align:start position:0% verification key and then we have the 00:05:26.720 --> 00:05:28.830 align:start position:0% verification key and then we have the normal<00:05:27.039> thing<00:05:27.280> we<00:05:27.400> have<00:05:27.560> a<00:05:28.000> approver<00:05:28.520> for<00:05:28.680> the 00:05:28.830 --> 00:05:28.840 align:start position:0% normal thing we have a approver for the 00:05:28.840 --> 00:05:30.590 align:start position:0% normal thing we have a approver for the approver<00:05:29.520> have<00:05:29.800> an<00:05:29.919> interface<00:05:30.280> that<00:05:30.400> you<00:05:30.479> get 00:05:30.590 --> 00:05:30.600 align:start position:0% approver have an interface that you get 00:05:30.600 --> 00:05:32.309 align:start position:0% approver have an interface that you get an<00:05:30.720> input<00:05:31.080> and<00:05:31.240> this<00:05:31.400> Pro<00:05:31.759> generates<00:05:32.199> the 00:05:32.309 --> 00:05:32.319 align:start position:0% an input and this Pro generates the 00:05:32.319 --> 00:05:34.350 align:start position:0% an input and this Pro generates the proof<00:05:32.680> and<00:05:32.880> the<00:05:33.039> public<00:05:33.720> uh<00:05:33.960> uh<00:05:34.120> and<00:05:34.240> the 00:05:34.350 --> 00:05:34.360 align:start position:0% proof and the public uh uh and the 00:05:34.360 --> 00:05:35.950 align:start position:0% proof and the public uh uh and the public<00:05:34.639> outputs<00:05:35.319> and<00:05:35.440> you<00:05:35.520> can<00:05:35.680> take<00:05:35.840> the 00:05:35.950 --> 00:05:35.960 align:start position:0% public outputs and you can take the 00:05:35.960 --> 00:05:37.189 align:start position:0% public outputs and you can take the proof<00:05:36.120> and<00:05:36.240> the<00:05:36.319> public<00:05:36.520> outputs<00:05:36.800> and<00:05:36.919> verify 00:05:37.189 --> 00:05:37.199 align:start position:0% proof and the public outputs and verify 00:05:37.199 --> 00:05:39.710 align:start position:0% proof and the public outputs and verify and<00:05:37.240> the<00:05:37.720> verify<00:05:38.720> you<00:05:38.880> see<00:05:39.080> that's<00:05:39.280> got<00:05:39.520> it 00:05:39.710 --> 00:05:39.720 align:start position:0% and the verify you see that's got it 00:05:39.720 --> 00:05:41.950 align:start position:0% and the verify you see that's got it here<00:05:40.000> okay<00:05:40.479> so<00:05:40.720> this<00:05:40.840> is<00:05:41.080> the<00:05:41.400> so<00:05:41.680> this<00:05:41.800> is 00:05:41.950 --> 00:05:41.960 align:start position:0% here okay so this is the so this is 00:05:41.960 --> 00:05:43.950 align:start position:0% here okay so this is the so this is would<00:05:42.080> be<00:05:42.240> the<00:05:42.479> schema<00:05:43.199> that<00:05:43.400> would<00:05:43.759> that 00:05:43.950 --> 00:05:43.960 align:start position:0% would be the schema that would that 00:05:43.960 --> 00:05:47.990 align:start position:0% would be the schema that would that would<00:05:44.240> work<00:05:44.960> okay<00:05:46.400> um<00:05:47.400> thing<00:05:47.560> is<00:05:47.680> that<00:05:47.840> this 00:05:47.990 --> 00:05:48.000 align:start position:0% would work okay um thing is that this 00:05:48.000 --> 00:05:49.990 align:start position:0% would work okay um thing is that this Pro<00:05:48.400> is<00:05:48.880> generic<00:05:49.240> I<00:05:49.319> mean<00:05:49.440> you<00:05:49.520> don't<00:05:49.680> need<00:05:49.840> to 00:05:49.990 --> 00:05:50.000 align:start position:0% Pro is generic I mean you don't need to 00:05:50.000 --> 00:05:53.309 align:start position:0% Pro is generic I mean you don't need to recompile<00:05:50.560> the<00:05:50.639> pr<00:05:51.000> it's<00:05:51.160> just<00:05:51.400> a<00:05:51.960> u<00:05:52.960> just<00:05:53.120> a 00:05:53.309 --> 00:05:53.319 align:start position:0% recompile the pr it's just a u just a 00:05:53.319 --> 00:05:54.909 align:start position:0% recompile the pr it's just a u just a program<00:05:53.720> that's<00:05:53.880> running<00:05:54.240> there<00:05:54.520> but<00:05:54.680> can<00:05:54.800> be 00:05:54.909 --> 00:05:54.919 align:start position:0% program that's running there but can be 00:05:54.919 --> 00:05:58.749 align:start position:0% program that's running there but can be a<00:05:55.039> program<00:05:55.479> can<00:05:55.639> be<00:05:55.800> a<00:05:56.440> service<00:05:57.440> uh<00:05:58.120> can<00:05:58.360> be<00:05:58.680> I 00:05:58.749 --> 00:05:58.759 align:start position:0% a program can be a service uh can be I 00:05:58.759 --> 00:06:00.150 align:start position:0% a program can be a service uh can be I mean<00:05:59.199> um 00:06:00.150 --> 00:06:00.160 align:start position:0% mean um 00:06:00.160 --> 00:06:02.189 align:start position:0% mean um this<00:06:00.360> PR<00:06:01.120> and<00:06:01.240> this<00:06:01.360> program<00:06:01.639> can<00:06:01.800> have<00:06:02.039> like 00:06:02.189 --> 00:06:02.199 align:start position:0% this PR and this program can have like 00:06:02.199 --> 00:06:03.629 align:start position:0% this PR and this program can have like different<00:06:02.680> versions<00:06:03.039> I<00:06:03.120> mean<00:06:03.240> it<00:06:03.280> can<00:06:03.400> be<00:06:03.520> in 00:06:03.629 --> 00:06:03.639 align:start position:0% different versions I mean it can be in 00:06:03.639 --> 00:06:07.029 align:start position:0% different versions I mean it can be in GP<00:06:04.160> GPU<00:06:04.840> in<00:06:05.199> I<00:06:05.280> mean<00:06:05.560> you<00:06:05.680> can<00:06:06.639> it<00:06:06.759> doesn't 00:06:07.029 --> 00:06:07.039 align:start position:0% GP GPU in I mean you can it doesn't 00:06:07.039 --> 00:06:08.909 align:start position:0% GP GPU in I mean you can it doesn't change<00:06:07.360> I<00:06:07.440> mean<00:06:07.599> you<00:06:07.720> can<00:06:08.039> have<00:06:08.560> it's<00:06:08.800> a 00:06:08.909 --> 00:06:08.919 align:start position:0% change I mean you can have it's a 00:06:08.919 --> 00:06:10.990 align:start position:0% change I mean you can have it's a generic<00:06:09.319> for<00:06:09.560> any<00:06:10.080> the<00:06:10.199> co<00:06:10.440> the<00:06:10.520> idea<00:06:10.759> is<00:06:10.880> that 00:06:10.990 --> 00:06:11.000 align:start position:0% generic for any the co the idea is that 00:06:11.000 --> 00:06:13.390 align:start position:0% generic for any the co the idea is that it's<00:06:11.120> generic<00:06:11.479> for<00:06:11.680> any<00:06:12.280> for<00:06:12.479> any 00:06:13.390 --> 00:06:13.400 align:start position:0% it's generic for any for any 00:06:13.400 --> 00:06:16.749 align:start position:0% it's generic for any for any circuit<00:06:14.400> this<00:06:14.560> program<00:06:15.000> is<00:06:15.319> I<00:06:15.360> mean<00:06:15.639> is<00:06:15.919> is<00:06:16.440> U 00:06:16.749 --> 00:06:16.759 align:start position:0% circuit this program is I mean is is U 00:06:16.759 --> 00:06:21.150 align:start position:0% circuit this program is I mean is is U it's<00:06:16.960> open<00:06:17.280> source<00:06:18.160> um<00:06:19.120> and<00:06:19.599> is<00:06:20.440> uh<00:06:20.800> everything 00:06:21.150 --> 00:06:21.160 align:start position:0% it's open source um and is uh everything 00:06:21.160 --> 00:06:23.510 align:start position:0% it's open source um and is uh everything is<00:06:21.319> designed<00:06:21.800> to<00:06:22.000> minimize<00:06:22.440> the<00:06:22.599> latency<00:06:23.360> okay 00:06:23.510 --> 00:06:23.520 align:start position:0% is designed to minimize the latency okay 00:06:23.520 --> 00:06:25.909 align:start position:0% is designed to minimize the latency okay we<00:06:23.639> will<00:06:23.800> see<00:06:24.039> later<00:06:25.039> uh<00:06:25.400> the<00:06:25.599> different 00:06:25.909 --> 00:06:25.919 align:start position:0% we will see later uh the different 00:06:25.919 --> 00:06:29.029 align:start position:0% we will see later uh the different things<00:06:26.280> on<00:06:26.639> related<00:06:27.000> to<00:06:27.199> that<00:06:27.840> okay<00:06:28.639> so<00:06:28.840> and 00:06:29.029 --> 00:06:29.039 align:start position:0% things on related to that okay so and 00:06:29.039 --> 00:06:32.589 align:start position:0% things on related to that okay so and then<00:06:29.440> uh<00:06:29.680> um<00:06:30.280> let<00:06:30.400> me<00:06:30.599> just<00:06:30.759> go<00:06:30.960> back<00:06:31.199> so 00:06:32.589 --> 00:06:32.599 align:start position:0% then uh um let me just go back so 00:06:32.599 --> 00:06:35.550 align:start position:0% then uh um let me just go back so um<00:06:33.599> this<00:06:33.759> would<00:06:33.919> be<00:06:34.039> the<00:06:34.160> prer<00:06:34.960> okay<00:06:35.240> but<00:06:35.400> on 00:06:35.550 --> 00:06:35.560 align:start position:0% um this would be the prer okay but on 00:06:35.560 --> 00:06:37.029 align:start position:0% um this would be the prer okay but on top<00:06:35.680> of<00:06:35.800> the<00:06:35.919> prer<00:06:36.240> we<00:06:36.360> have<00:06:36.479> a<00:06:36.639> specific 00:06:37.029 --> 00:06:37.039 align:start position:0% top of the prer we have a specific 00:06:37.039 --> 00:06:40.950 align:start position:0% top of the prer we have a specific circuit<00:06:37.680> so<00:06:37.840> it's<00:06:38.240> a<00:06:39.240> just<00:06:39.520> just<00:06:39.759> one<00:06:40.479> uh<00:06:40.680> so<00:06:40.840> we 00:06:40.950 --> 00:06:40.960 align:start position:0% circuit so it's a just just one uh so we 00:06:40.960 --> 00:06:42.870 align:start position:0% circuit so it's a just just one uh so we are<00:06:41.080> using<00:06:41.400> it's<00:06:41.560> like<00:06:41.759> a<00:06:42.080> so<00:06:42.440> the<00:06:42.560> specific 00:06:42.870 --> 00:06:42.880 align:start position:0% are using it's like a so the specific 00:06:42.880 --> 00:06:44.749 align:start position:0% are using it's like a so the specific circuit<00:06:43.240> using<00:06:43.520> p<00:06:43.720> 21<00:06:44.080> that's<00:06:44.240> implemented<00:06:44.639> in 00:06:44.749 --> 00:06:44.759 align:start position:0% circuit using p 21 that's implemented in 00:06:44.759 --> 00:06:47.710 align:start position:0% circuit using p 21 that's implemented in P<00:06:44.919> 21<00:06:45.560> we<00:06:45.680> can<00:06:45.800> use<00:06:45.960> the<00:06:46.120> pro<00:06:46.680> that's<00:06:46.919> actually 00:06:47.710 --> 00:06:47.720 align:start position:0% P 21 we can use the pro that's actually 00:06:47.720 --> 00:06:50.870 align:start position:0% P 21 we can use the pro that's actually this<00:06:48.240> um<00:06:48.960> uh<00:06:49.120> this<00:06:49.280> dis<00:06:49.639> is<00:06:49.840> this<00:06:50.280> uh<00:06:50.520> let's<00:06:50.680> say 00:06:50.870 --> 00:06:50.880 align:start position:0% this um uh this dis is this uh let's say 00:06:50.880 --> 00:06:54.189 align:start position:0% this um uh this dis is this uh let's say RIS<00:06:51.199> five<00:06:51.840> emulator<00:06:52.759> kind<00:06:52.960> of<00:06:53.280> actually<00:06:53.720> is 00:06:54.189 --> 00:06:54.199 align:start position:0% RIS five emulator kind of actually is 00:06:54.199 --> 00:06:56.990 align:start position:0% RIS five emulator kind of actually is not<00:06:55.199> I<00:06:55.280> would<00:06:55.479> not<00:06:55.639> call<00:06:55.840> it<00:06:55.960> an<00:06:56.160> emulator<00:06:56.840> it's 00:06:56.990 --> 00:06:57.000 align:start position:0% not I would not call it an emulator it's 00:06:57.000 --> 00:07:00.070 align:start position:0% not I would not call it an emulator it's a<00:06:57.560> ZK<00:06:58.199> processor<00:06:59.120> the<00:06:59.319> thing<00:06:59.599> the<00:06:59.680> only<00:06:59.879> thing 00:07:00.070 --> 00:07:00.080 align:start position:0% a ZK processor the thing the only thing 00:07:00.080 --> 00:07:02.629 align:start position:0% a ZK processor the thing the only thing is<00:07:00.240> that<00:07:00.680> uh<00:07:00.919> there<00:07:01.080> is<00:07:01.240> a<00:07:01.440> direct<00:07:01.759> conversion 00:07:02.629 --> 00:07:02.639 align:start position:0% is that uh there is a direct conversion 00:07:02.639 --> 00:07:06.350 align:start position:0% is that uh there is a direct conversion between<00:07:03.280> R<00:07:03.639> 5<00:07:03.960> or<00:07:04.120> even<00:07:04.400> wasam<00:07:05.000> or<00:07:05.280> other<00:07:06.000> or<00:07:06.199> or 00:07:06.350 --> 00:07:06.360 align:start position:0% between R 5 or even wasam or other or or 00:07:06.360 --> 00:07:09.749 align:start position:0% between R 5 or even wasam or other or or llbm<00:07:07.280> to<00:07:07.840> this<00:07:08.160> ZK<00:07:09.000> processor<00:07:09.479> it's<00:07:09.599> a 00:07:09.749 --> 00:07:09.759 align:start position:0% llbm to this ZK processor it's a 00:07:09.759 --> 00:07:13.189 align:start position:0% llbm to this ZK processor it's a processor<00:07:10.240> that<00:07:10.440> has<00:07:10.599> only<00:07:11.280> about<00:07:12.039> uh<00:07:12.759> 50 00:07:13.189 --> 00:07:13.199 align:start position:0% processor that has only about uh 50 00:07:13.199 --> 00:07:15.469 align:start position:0% processor that has only about uh 50 polinomial<00:07:13.919> so<00:07:14.120> it's<00:07:14.319> very<00:07:14.560> very<00:07:14.800> lightweight 00:07:15.469 --> 00:07:15.479 align:start position:0% polinomial so it's very very lightweight 00:07:15.479 --> 00:07:17.670 align:start position:0% polinomial so it's very very lightweight uh<00:07:15.720> processor<00:07:16.199> and<00:07:16.440> really<00:07:16.680> fast<00:07:17.160> and<00:07:17.520> and 00:07:17.670 --> 00:07:17.680 align:start position:0% uh processor and really fast and and 00:07:17.680 --> 00:07:22.629 align:start position:0% uh processor and really fast and and really<00:07:17.879> fast<00:07:18.560> processor<00:07:19.560> okay<00:07:20.280> so<00:07:21.440> um<00:07:22.440> and 00:07:22.629 --> 00:07:22.639 align:start position:0% really fast processor okay so um and 00:07:22.639 --> 00:07:25.350 align:start position:0% really fast processor okay so um and then<00:07:22.919> it<00:07:23.039> works<00:07:23.319> very<00:07:23.560> much<00:07:23.879> like<00:07:24.360> any<00:07:25.039> other 00:07:25.350 --> 00:07:25.360 align:start position:0% then it works very much like any other 00:07:25.360 --> 00:07:27.990 align:start position:0% then it works very much like any other VM<00:07:26.039> in<00:07:26.280> there<00:07:26.639> so<00:07:26.800> you<00:07:26.960> can<00:07:27.160> build<00:07:27.479> a<00:07:27.680> program 00:07:27.990 --> 00:07:28.000 align:start position:0% VM in there so you can build a program 00:07:28.000 --> 00:07:30.309 align:start position:0% VM in there so you can build a program so<00:07:28.199> you<00:07:28.400> you<00:07:28.520> build<00:07:28.759> the<00:07:29.039> the<00:07:29.160> circuit<00:07:29.879> in<00:07:30.080> in<00:07:30.199> a 00:07:30.309 --> 00:07:30.319 align:start position:0% so you you build the the circuit in in a 00:07:30.319 --> 00:07:32.110 align:start position:0% so you you build the the circuit in in a normal<00:07:30.720> program<00:07:31.280> of<00:07:31.400> course<00:07:31.599> you<00:07:31.720> can<00:07:31.919> test 00:07:32.110 --> 00:07:32.120 align:start position:0% normal program of course you can test 00:07:32.120 --> 00:07:33.029 align:start position:0% normal program of course you can test your<00:07:32.240> circuit<00:07:32.560> at<00:07:32.639> the<00:07:32.720> end<00:07:32.840> it's<00:07:32.919> a 00:07:33.029 --> 00:07:33.039 align:start position:0% your circuit at the end it's a 00:07:33.039 --> 00:07:35.790 align:start position:0% your circuit at the end it's a deterministic<00:07:33.680> program<00:07:34.000> so<00:07:34.199> you<00:07:34.639> compile<00:07:35.199> the 00:07:35.790 --> 00:07:35.800 align:start position:0% deterministic program so you compile the 00:07:35.800 --> 00:07:37.469 align:start position:0% deterministic program so you compile the the<00:07:36.039> the<00:07:36.160> circuit<00:07:36.599> you<00:07:36.720> get<00:07:36.879> a<00:07:37.039> program<00:07:37.319> and 00:07:37.469 --> 00:07:37.479 align:start position:0% the the circuit you get a program and 00:07:37.479 --> 00:07:38.749 align:start position:0% the the circuit you get a program and then<00:07:37.599> you<00:07:37.680> have<00:07:37.800> an<00:07:37.960> input<00:07:38.240> and<00:07:38.319> an<00:07:38.440> output 00:07:38.749 --> 00:07:38.759 align:start position:0% then you have an input and an output 00:07:38.759 --> 00:07:39.990 align:start position:0% then you have an input and an output it's<00:07:38.840> a<00:07:38.960> deterministic<00:07:39.599> program<00:07:39.879> that 00:07:39.990 --> 00:07:40.000 align:start position:0% it's a deterministic program that 00:07:40.000 --> 00:07:41.869 align:start position:0% it's a deterministic program that generates<00:07:40.319> the<00:07:40.440> circuit<00:07:41.199> once<00:07:41.360> you<00:07:41.520> have<00:07:41.680> that 00:07:41.869 --> 00:07:41.879 align:start position:0% generates the circuit once you have that 00:07:41.879 --> 00:07:43.270 align:start position:0% generates the circuit once you have that that's<00:07:42.039> the<00:07:42.160> only<00:07:42.360> thing<00:07:42.520> you<00:07:42.639> need<00:07:43.000> you<00:07:43.120> can 00:07:43.270 --> 00:07:43.280 align:start position:0% that's the only thing you need you can 00:07:43.280 --> 00:07:45.749 align:start position:0% that's the only thing you need you can take<00:07:43.520> this<00:07:43.720> program<00:07:44.360> you<00:07:44.479> can<00:07:44.720> generate<00:07:45.560> mean 00:07:45.749 --> 00:07:45.759 align:start position:0% take this program you can generate mean 00:07:45.759 --> 00:07:48.909 align:start position:0% take this program you can generate mean you<00:07:45.840> can<00:07:46.120> compile<00:07:46.879> using<00:07:47.199> rust<00:07:47.639> and<00:07:48.120> some 00:07:48.909 --> 00:07:48.919 align:start position:0% you can compile using rust and some 00:07:48.919 --> 00:07:50.749 align:start position:0% you can compile using rust and some setup<00:07:49.400> and<00:07:49.520> then<00:07:49.639> you<00:07:49.759> get<00:07:49.960> a<00:07:50.080> kind<00:07:50.199> of<00:07:50.319> a<00:07:50.440> ROM 00:07:50.749 --> 00:07:50.759 align:start position:0% setup and then you get a kind of a ROM 00:07:50.759 --> 00:07:53.749 align:start position:0% setup and then you get a kind of a ROM or<00:07:50.879> if<00:07:50.960> you<00:07:51.080> want<00:07:51.280> a<00:07:52.159> you<00:07:52.280> know<00:07:52.840> an<00:07:53.000> elf<00:07:53.479> kind<00:07:53.639> of 00:07:53.749 --> 00:07:53.759 align:start position:0% or if you want a you know an elf kind of 00:07:53.759 --> 00:07:55.149 align:start position:0% or if you want a you know an elf kind of a<00:07:53.960> program 00:07:55.149 --> 00:07:55.159 align:start position:0% a program 00:07:55.159 --> 00:07:59.510 align:start position:0% a program itself<00:07:56.159> um<00:07:56.879> and<00:07:57.720> then<00:07:58.560> uh<00:07:58.680> you<00:07:58.800> can<00:07:58.960> use<00:07:59.159> the 00:07:59.510 --> 00:07:59.520 align:start position:0% itself um and then uh you can use the 00:07:59.520 --> 00:08:01.790 align:start position:0% itself um and then uh you can use the Pro<00:07:59.879> I<00:07:59.919> mean<00:08:00.080> the<00:08:00.199> pro<00:08:00.520> that<00:08:00.639> we<00:08:00.759> saw<00:08:01.080> before<00:08:01.680> of 00:08:01.790 --> 00:08:01.800 align:start position:0% Pro I mean the pro that we saw before of 00:08:01.800 --> 00:08:04.270 align:start position:0% Pro I mean the pro that we saw before of course<00:08:02.120> here<00:08:02.479> the<00:08:02.960> the<00:08:03.120> the<00:08:03.280> zis<00:08:03.759> the<00:08:03.919> private 00:08:04.270 --> 00:08:04.280 align:start position:0% course here the the the zis the private 00:08:04.280 --> 00:08:06.070 align:start position:0% course here the the the zis the private key<00:08:04.479> the<00:08:04.680> the<00:08:04.800> verification<00:08:05.280> key<00:08:05.440> is<00:08:05.599> already 00:08:06.070 --> 00:08:06.080 align:start position:0% key the the verification key is already 00:08:06.080 --> 00:08:08.510 align:start position:0% key the the verification key is already is<00:08:06.199> already<00:08:06.479> done<00:08:06.759> because<00:08:07.039> this<00:08:07.159> is<00:08:07.319> a<00:08:07.680> an<00:08:08.360> a 00:08:08.510 --> 00:08:08.520 align:start position:0% is already done because this is a an a 00:08:08.520 --> 00:08:10.110 align:start position:0% is already done because this is a an a specific<00:08:08.879> application<00:08:09.319> a<00:08:09.440> specific<00:08:09.759> circuit 00:08:10.110 --> 00:08:10.120 align:start position:0% specific application a specific circuit 00:08:10.120 --> 00:08:11.869 align:start position:0% specific application a specific circuit for<00:08:10.319> the<00:08:10.479> prover<00:08:10.800> but<00:08:10.919> the<00:08:11.039> prover<00:08:11.319> is<00:08:11.520> exactly 00:08:11.869 --> 00:08:11.879 align:start position:0% for the prover but the prover is exactly 00:08:11.879 --> 00:08:14.070 align:start position:0% for the prover but the prover is exactly the<00:08:12.039> same<00:08:12.720> and<00:08:12.879> then<00:08:13.360> of<00:08:13.479> course<00:08:13.639> you<00:08:13.800> have<00:08:13.919> an 00:08:14.070 --> 00:08:14.080 align:start position:0% the same and then of course you have an 00:08:14.080 --> 00:08:16.350 align:start position:0% the same and then of course you have an input<00:08:15.080> uh<00:08:15.280> a<00:08:15.479> proof<00:08:15.720> and<00:08:15.840> output<00:08:16.159> and<00:08:16.240> the 00:08:16.350 --> 00:08:16.360 align:start position:0% input uh a proof and output and the 00:08:16.360 --> 00:08:17.869 align:start position:0% input uh a proof and output and the verifier<00:08:17.000> the<00:08:17.120> only<00:08:17.319> thing<00:08:17.479> is<00:08:17.560> that<00:08:17.720> the 00:08:17.869 --> 00:08:17.879 align:start position:0% verifier the only thing is that the 00:08:17.879 --> 00:08:20.670 align:start position:0% verifier the only thing is that the input<00:08:18.240> includes<00:08:18.759> the<00:08:19.479> the<00:08:19.680> private<00:08:20.400> private 00:08:20.670 --> 00:08:20.680 align:start position:0% input includes the the private private 00:08:20.680 --> 00:08:22.710 align:start position:0% input includes the the private private input<00:08:21.000> and<00:08:21.240> and<00:08:21.360> the<00:08:21.479> ROM<00:08:21.840> so<00:08:21.960> you<00:08:22.080> can<00:08:22.319> prove 00:08:22.710 --> 00:08:22.720 align:start position:0% input and and the ROM so you can prove 00:08:22.720 --> 00:08:25.790 align:start position:0% input and and the ROM so you can prove any<00:08:23.680> any<00:08:24.159> program<00:08:24.759> that<00:08:24.919> you<00:08:25.039> want<00:08:25.560> and<00:08:25.680> of 00:08:25.790 --> 00:08:25.800 align:start position:0% any any program that you want and of 00:08:25.800 --> 00:08:27.390 align:start position:0% any any program that you want and of course<00:08:25.960> in<00:08:26.039> the<00:08:26.159> verifier<00:08:26.720> you<00:08:26.919> can<00:08:27.159> you<00:08:27.240> can 00:08:27.390 --> 00:08:27.400 align:start position:0% course in the verifier you can you can 00:08:27.400 --> 00:08:29.629 align:start position:0% course in the verifier you can you can use<00:08:27.560> the<00:08:27.720> ROM<00:08:28.039> has<00:08:28.400> so<00:08:28.639> you<00:08:28.840> you<00:08:28.919> can<00:08:29.039> use<00:08:29.199> the 00:08:29.629 --> 00:08:29.639 align:start position:0% use the ROM has so you you can use the 00:08:29.639 --> 00:08:31.190 align:start position:0% use the ROM has so you you can use the fire 00:08:31.190 --> 00:08:31.200 align:start position:0% fire 00:08:31.200 --> 00:08:35.870 align:start position:0% fire itself<00:08:32.200> okay<00:08:33.039> so<00:08:33.240> let's<00:08:33.519> go<00:08:33.760> deep<00:08:34.200> in<00:08:34.680> how<00:08:35.680> uh 00:08:35.870 --> 00:08:35.880 align:start position:0% itself okay so let's go deep in how uh 00:08:35.880 --> 00:08:38.310 align:start position:0% itself okay so let's go deep in how uh this<00:08:36.279> I<00:08:36.360> mean<00:08:36.640> how<00:08:37.039> how<00:08:37.599> the<00:08:37.680> architecture<00:08:38.240> I 00:08:38.310 --> 00:08:38.320 align:start position:0% this I mean how how the architecture I 00:08:38.320 --> 00:08:42.230 align:start position:0% this I mean how how the architecture I mean<00:08:38.519> how<00:08:38.800> this<00:08:39.240> um<00:08:39.880> uh<00:08:40.000> circuit<00:08:40.880> works<00:08:41.880> well 00:08:42.230 --> 00:08:42.240 align:start position:0% mean how this um uh circuit works well 00:08:42.240 --> 00:08:44.670 align:start position:0% mean how this um uh circuit works well as<00:08:42.360> I<00:08:42.479> told<00:08:42.680> you<00:08:42.880> before<00:08:43.279> this<00:08:43.440> circuit<00:08:44.159> uh<00:08:44.480> is 00:08:44.670 --> 00:08:44.680 align:start position:0% as I told you before this circuit uh is 00:08:44.680 --> 00:08:47.230 align:start position:0% as I told you before this circuit uh is based<00:08:45.080> on<00:08:45.480> uh<00:08:45.680> vops<00:08:46.240> actually<00:08:46.600> is<00:08:46.880> many<00:08:47.160> there 00:08:47.230 --> 00:08:47.240 align:start position:0% based on uh vops actually is many there 00:08:47.240 --> 00:08:50.110 align:start position:0% based on uh vops actually is many there are<00:08:47.399> many<00:08:47.640> sub<00:08:47.920> proofs<00:08:48.600> each<00:08:49.240> this<00:08:49.640> Su<00:08:49.880> prooof 00:08:50.110 --> 00:08:50.120 align:start position:0% are many sub proofs each this Su prooof 00:08:50.120 --> 00:08:51.990 align:start position:0% are many sub proofs each this Su prooof there<00:08:50.200> are<00:08:50.360> different<00:08:50.720> kinds<00:08:51.200> and<00:08:51.480> this<00:08:51.880> this 00:08:51.990 --> 00:08:52.000 align:start position:0% there are different kinds and this this 00:08:52.000 --> 00:08:54.350 align:start position:0% there are different kinds and this this works<00:08:52.320> very<00:08:52.519> much<00:08:52.720> like<00:08:52.880> a<00:08:53.040> normal<00:08:53.560> processor 00:08:54.350 --> 00:08:54.360 align:start position:0% works very much like a normal processor 00:08:54.360 --> 00:08:56.590 align:start position:0% works very much like a normal processor we<00:08:54.519> have<00:08:54.720> like<00:08:54.880> a<00:08:55.200> a<00:08:55.399> main<00:08:55.720> processor<00:08:56.279> with<00:08:56.440> a 00:08:56.590 --> 00:08:56.600 align:start position:0% we have like a a main processor with a 00:08:56.600 --> 00:08:58.710 align:start position:0% we have like a a main processor with a program<00:08:56.959> with<00:08:57.080> a<00:08:57.200> ROM<00:08:57.760> and<00:08:57.920> then<00:08:58.120> we<00:08:58.279> have<00:08:58.480> a 00:08:58.710 --> 00:08:58.720 align:start position:0% program with a ROM and then we have a 00:08:58.720 --> 00:09:00.350 align:start position:0% program with a ROM and then we have a ram<00:08:59.040> we<00:08:59.160> have<00:08:59.279> a<00:08:59.440> arithmetic<00:08:59.839> operations<00:09:00.240> we 00:09:00.350 --> 00:09:00.360 align:start position:0% ram we have a arithmetic operations we 00:09:00.360 --> 00:09:03.509 align:start position:0% ram we have a arithmetic operations we have<00:09:00.480> a<00:09:00.600> lot<00:09:00.720> of<00:09:01.320> co-processors<00:09:02.320> um<00:09:02.800> uh<00:09:03.200> that 00:09:03.509 --> 00:09:03.519 align:start position:0% have a lot of co-processors um uh that 00:09:03.519 --> 00:09:06.910 align:start position:0% have a lot of co-processors um uh that can<00:09:03.720> be<00:09:04.000> connected<00:09:04.760> here<00:09:05.440> okay<00:09:06.120> uh<00:09:06.480> so<00:09:06.720> each 00:09:06.910 --> 00:09:06.920 align:start position:0% can be connected here okay uh so each 00:09:06.920 --> 00:09:09.790 align:start position:0% can be connected here okay uh so each one<00:09:07.120> of<00:09:07.279> these<00:09:07.600> is<00:09:08.200> one<00:09:08.519> some<00:09:08.880> proof<00:09:09.360> and 00:09:09.790 --> 00:09:09.800 align:start position:0% one of these is one some proof and 00:09:09.800 --> 00:09:11.150 align:start position:0% one of these is one some proof and actually<00:09:10.160> you<00:09:10.279> can<00:09:10.519> have<00:09:10.680> for<00:09:10.839> example 00:09:11.150 --> 00:09:11.160 align:start position:0% actually you can have for example 00:09:11.160 --> 00:09:12.389 align:start position:0% actually you can have for example arithmetic<00:09:11.720> if<00:09:11.800> you<00:09:11.920> have<00:09:12.079> a<00:09:12.160> lot<00:09:12.320> of 00:09:12.389 --> 00:09:12.399 align:start position:0% arithmetic if you have a lot of 00:09:12.399 --> 00:09:14.509 align:start position:0% arithmetic if you have a lot of arithmetic<00:09:12.880> operations<00:09:13.320> you<00:09:13.440> can<00:09:13.640> have<00:09:14.200> a<00:09:14.360> lot 00:09:14.509 --> 00:09:14.519 align:start position:0% arithmetic operations you can have a lot 00:09:14.519 --> 00:09:16.750 align:start position:0% arithmetic operations you can have a lot of<00:09:14.680> sub<00:09:14.920> circuits<00:09:15.279> and<00:09:15.480> all<00:09:15.720> them<00:09:16.200> add<00:09:16.440> them<00:09:16.640> to 00:09:16.750 --> 00:09:16.760 align:start position:0% of sub circuits and all them add them to 00:09:16.760 --> 00:09:18.790 align:start position:0% of sub circuits and all them add them to the<00:09:16.920> bus<00:09:17.240> and<00:09:17.360> they<00:09:17.519> connect<00:09:17.839> them<00:09:18.160> together 00:09:18.790 --> 00:09:18.800 align:start position:0% the bus and they connect them together 00:09:18.800 --> 00:09:21.030 align:start position:0% the bus and they connect them together this<00:09:19.000> bus<00:09:19.360> I<00:09:19.440> mean<00:09:19.600> is<00:09:19.720> not<00:09:19.880> an<00:09:20.079> electronic<00:09:20.560> bus 00:09:21.030 --> 00:09:21.040 align:start position:0% this bus I mean is not an electronic bus 00:09:21.040 --> 00:09:23.710 align:start position:0% this bus I mean is not an electronic bus but<00:09:21.200> there<00:09:21.560> something<00:09:22.560> would<00:09:22.760> say<00:09:23.120> similar 00:09:23.710 --> 00:09:23.720 align:start position:0% but there something would say similar 00:09:23.720 --> 00:09:26.550 align:start position:0% but there something would say similar it's<00:09:23.800> more<00:09:23.920> an<00:09:24.079> algebraic<00:09:24.720> boss<00:09:25.440> but<00:09:25.640> this<00:09:26.040> um 00:09:26.550 --> 00:09:26.560 align:start position:0% it's more an algebraic boss but this um 00:09:26.560 --> 00:09:28.430 align:start position:0% it's more an algebraic boss but this um we<00:09:26.640> are<00:09:26.800> using<00:09:27.079> here<00:09:27.279> lock<00:09:27.519> ups<00:09:28.000> and<00:09:28.160> here<00:09:28.320> the 00:09:28.430 --> 00:09:28.440 align:start position:0% we are using here lock ups and here the 00:09:28.440 --> 00:09:30.509 align:start position:0% we are using here lock ups and here the idea<00:09:28.640> is<00:09:28.800> you<00:09:28.920> can<00:09:29.040> have<00:09:29.560> Su<00:09:29.760> proof<00:09:30.160> so<00:09:30.279> you<00:09:30.360> can 00:09:30.509 --> 00:09:30.519 align:start position:0% idea is you can have Su proof so you can 00:09:30.519 --> 00:09:31.910 align:start position:0% idea is you can have Su proof so you can have<00:09:30.680> the<00:09:30.800> main<00:09:31.079> processor<00:09:31.519> you<00:09:31.680> have<00:09:31.839> the 00:09:31.910 --> 00:09:31.920 align:start position:0% have the main processor you have the 00:09:31.920 --> 00:09:34.230 align:start position:0% have the main processor you have the arithmetic<00:09:32.440> processor<00:09:33.200> each<00:09:33.399> one<00:09:33.680> is<00:09:34.000> like 00:09:34.230 --> 00:09:34.240 align:start position:0% arithmetic processor each one is like 00:09:34.240 --> 00:09:36.430 align:start position:0% arithmetic processor each one is like sending<00:09:34.720> things<00:09:34.920> to<00:09:35.079> the<00:09:35.240> BS<00:09:36.000> and<00:09:36.120> the<00:09:36.200> main 00:09:36.430 --> 00:09:36.440 align:start position:0% sending things to the BS and the main 00:09:36.440 --> 00:09:38.470 align:start position:0% sending things to the BS and the main processor<00:09:36.880> says<00:09:37.200> okay<00:09:37.600> I'm<00:09:37.800> assuming<00:09:38.279> that 00:09:38.470 --> 00:09:38.480 align:start position:0% processor says okay I'm assuming that 00:09:38.480 --> 00:09:40.670 align:start position:0% processor says okay I'm assuming that this<00:09:38.680> arithmetic<00:09:39.200> operation<00:09:39.640> is<00:09:40.000> correct 00:09:40.670 --> 00:09:40.680 align:start position:0% this arithmetic operation is correct 00:09:40.680 --> 00:09:42.550 align:start position:0% this arithmetic operation is correct okay<00:09:41.120> and<00:09:41.240> then<00:09:41.440> there<00:09:41.560> is<00:09:41.839> the<00:09:42.000> arithmetic 00:09:42.550 --> 00:09:42.560 align:start position:0% okay and then there is the arithmetic 00:09:42.560 --> 00:09:44.150 align:start position:0% okay and then there is the arithmetic coprocessor<00:09:43.160> that's<00:09:43.320> saying<00:09:43.920> I'm 00:09:44.150 --> 00:09:44.160 align:start position:0% coprocessor that's saying I'm 00:09:44.160 --> 00:09:46.150 align:start position:0% coprocessor that's saying I'm guaranteeing<00:09:44.920> that<00:09:45.120> this<00:09:45.680> arithmetic 00:09:46.150 --> 00:09:46.160 align:start position:0% guaranteeing that this arithmetic 00:09:46.160 --> 00:09:48.949 align:start position:0% guaranteeing that this arithmetic operation<00:09:46.600> with<00:09:46.760> these<00:09:47.000> values<00:09:47.800> is<00:09:48.079> correct 00:09:48.949 --> 00:09:48.959 align:start position:0% operation with these values is correct 00:09:48.959 --> 00:09:50.870 align:start position:0% operation with these values is correct okay<00:09:49.120> so<00:09:49.279> the<00:09:49.360> full<00:09:49.600> system<00:09:49.880> is<00:09:50.040> correct<00:09:50.680> so 00:09:50.870 --> 00:09:50.880 align:start position:0% okay so the full system is correct so 00:09:50.880 --> 00:09:53.030 align:start position:0% okay so the full system is correct so one<00:09:51.079> is<00:09:51.399> adding<00:09:51.720> to<00:09:51.920> the<00:09:52.079> BS<00:09:52.560> the<00:09:52.680> other<00:09:52.880> is 00:09:53.030 --> 00:09:53.040 align:start position:0% one is adding to the BS the other is 00:09:53.040 --> 00:09:55.910 align:start position:0% one is adding to the BS the other is substracting<00:09:53.680> to<00:09:53.839> the<00:09:53.959> boss<00:09:54.760> and<00:09:54.959> at<00:09:55.120> the<00:09:55.240> end 00:09:55.910 --> 00:09:55.920 align:start position:0% substracting to the boss and at the end 00:09:55.920 --> 00:09:58.430 align:start position:0% substracting to the boss and at the end the<00:09:56.040> boss<00:09:56.279> means<00:09:56.720> zero<00:09:57.120> if<00:09:57.279> if<00:09:57.480> everything<00:09:57.839> is 00:09:58.430 --> 00:09:58.440 align:start position:0% the boss means zero if if everything is 00:09:58.440 --> 00:10:01.110 align:start position:0% the boss means zero if if everything is uh<00:09:59.079> uh<00:09:59.440> warranted<00:10:00.240> and<00:10:00.399> the<00:10:00.519> cool<00:10:00.720> thing<00:10:00.920> is 00:10:01.110 --> 00:10:01.120 align:start position:0% uh uh warranted and the cool thing is 00:10:01.120 --> 00:10:02.990 align:start position:0% uh uh warranted and the cool thing is that<00:10:01.600> I<00:10:01.680> mean<00:10:01.839> in<00:10:02.000> this<00:10:02.120> boss<00:10:02.399> I<00:10:02.480> can<00:10:02.640> add 00:10:02.990 --> 00:10:03.000 align:start position:0% that I mean in this boss I can add 00:10:03.000 --> 00:10:05.310 align:start position:0% that I mean in this boss I can add arithmetic<00:10:03.480> operations<00:10:03.959> I<00:10:04.079> can<00:10:04.399> add<00:10:04.959> memory 00:10:05.310 --> 00:10:05.320 align:start position:0% arithmetic operations I can add memory 00:10:05.320 --> 00:10:07.069 align:start position:0% arithmetic operations I can add memory instructions<00:10:05.880> I<00:10:05.959> can<00:10:06.120> add<00:10:06.360> whatever<00:10:06.680> you 00:10:07.069 --> 00:10:07.079 align:start position:0% instructions I can add whatever you 00:10:07.079 --> 00:10:08.790 align:start position:0% instructions I can add whatever you whatever<00:10:07.440> you<00:10:07.600> want<00:10:07.839> we<00:10:07.959> can<00:10:08.240> have<00:10:08.440> we<00:10:08.560> have<00:10:08.680> a 00:10:08.790 --> 00:10:08.800 align:start position:0% whatever you want we can have we have a 00:10:08.800 --> 00:10:10.430 align:start position:0% whatever you want we can have we have a kind<00:10:08.920> of<00:10:09.079> identifier<00:10:09.880> but<00:10:10.000> with<00:10:10.120> the<00:10:10.240> same 00:10:10.430 --> 00:10:10.440 align:start position:0% kind of identifier but with the same 00:10:10.440 --> 00:10:12.110 align:start position:0% kind of identifier but with the same polinomial<00:10:11.200> we<00:10:11.320> are<00:10:11.480> just<00:10:11.720> adding<00:10:11.959> and 00:10:12.110 --> 00:10:12.120 align:start position:0% polinomial we are just adding and 00:10:12.120 --> 00:10:14.710 align:start position:0% polinomial we are just adding and substracting<00:10:13.000> different<00:10:13.360> things<00:10:13.839> all<00:10:14.200> all 00:10:14.710 --> 00:10:14.720 align:start position:0% substracting different things all all 00:10:14.720 --> 00:10:17.389 align:start position:0% substracting different things all all together<00:10:15.959> okay<00:10:16.959> you<00:10:17.079> see<00:10:17.279> the 00:10:17.389 --> 00:10:17.399 align:start position:0% together okay you see the 00:10:17.399 --> 00:10:19.509 align:start position:0% together okay you see the arithmetization<00:10:17.920> I'm<00:10:18.519> not<00:10:18.680> going<00:10:18.760> to<00:10:18.959> go<00:10:19.279> in 00:10:19.509 --> 00:10:19.519 align:start position:0% arithmetization I'm not going to go in 00:10:19.519 --> 00:10:21.389 align:start position:0% arithmetization I'm not going to go in detail<00:10:20.000> on<00:10:20.160> the<00:10:20.279> arithmetization<00:10:20.720> but<00:10:21.120> I<00:10:21.240> give 00:10:21.389 --> 00:10:21.399 align:start position:0% detail on the arithmetization but I give 00:10:21.399 --> 00:10:24.430 align:start position:0% detail on the arithmetization but I give you<00:10:21.600> the<00:10:22.000> the<00:10:22.120> big<00:10:22.399> idea<00:10:22.839> I<00:10:22.920> mean<00:10:23.640> um<00:10:24.240> the 00:10:24.430 --> 00:10:24.440 align:start position:0% you the the big idea I mean um the 00:10:24.440 --> 00:10:27.110 align:start position:0% you the the big idea I mean um the processor<00:10:24.959> is<00:10:25.680> not<00:10:25.920> based<00:10:26.279> in<00:10:26.480> registers 00:10:27.110 --> 00:10:27.120 align:start position:0% processor is not based in registers 00:10:27.120 --> 00:10:30.350 align:start position:0% processor is not based in registers registers<00:10:27.519> in<00:10:27.680> ZK<00:10:28.160> I<00:10:28.680> are<00:10:29.360> relatively 00:10:30.350 --> 00:10:30.360 align:start position:0% registers in ZK I are relatively 00:10:30.360 --> 00:10:32.069 align:start position:0% registers in ZK I are relatively expensive<00:10:31.079> mainly<00:10:31.440> because<00:10:31.760> in<00:10:31.880> one 00:10:32.069 --> 00:10:32.079 align:start position:0% expensive mainly because in one 00:10:32.079 --> 00:10:33.630 align:start position:0% expensive mainly because in one instruction<00:10:32.560> you<00:10:32.640> are<00:10:32.800> using<00:10:33.079> in<00:10:33.200> general<00:10:33.480> one 00:10:33.630 --> 00:10:33.640 align:start position:0% instruction you are using in general one 00:10:33.640 --> 00:10:35.430 align:start position:0% instruction you are using in general one or<00:10:33.760> two<00:10:33.959> registers<00:10:34.720> so<00:10:34.880> that<00:10:35.000> means<00:10:35.279> that 00:10:35.430 --> 00:10:35.440 align:start position:0% or two registers so that means that 00:10:35.440 --> 00:10:38.190 align:start position:0% or two registers so that means that there<00:10:35.600> is<00:10:36.320> like<00:10:36.880> if<00:10:37.000> you<00:10:37.120> have<00:10:37.360> 32<00:10:37.720> registers 00:10:38.190 --> 00:10:38.200 align:start position:0% there is like if you have 32 registers 00:10:38.200 --> 00:10:41.710 align:start position:0% there is like if you have 32 registers you<00:10:38.399> may<00:10:38.600> have<00:10:38.839> like<00:10:39.040> 30<00:10:40.000> 30<00:10:40.680> columns<00:10:41.440> that<00:10:41.560> you 00:10:41.710 --> 00:10:41.720 align:start position:0% you may have like 30 30 columns that you 00:10:41.720 --> 00:10:43.829 align:start position:0% you may have like 30 30 columns that you are<00:10:41.880> not<00:10:42.079> even<00:10:42.320> using<00:10:42.760> in<00:10:42.920> that<00:10:43.079> line<00:10:43.320> so<00:10:43.560> doing 00:10:43.829 --> 00:10:43.839 align:start position:0% are not even using in that line so doing 00:10:43.839 --> 00:10:47.150 align:start position:0% are not even using in that line so doing registers<00:10:44.320> in<00:10:44.480> ZK<00:10:44.959> is<00:10:45.320> quite<00:10:45.680> suboptimal<00:10:46.680> so 00:10:47.150 --> 00:10:47.160 align:start position:0% registers in ZK is quite suboptimal so 00:10:47.160 --> 00:10:50.190 align:start position:0% registers in ZK is quite suboptimal so the<00:10:47.360> main<00:10:47.600> idea<00:10:48.000> here<00:10:48.200> is<00:10:48.600> okay<00:10:48.800> we<00:10:48.959> have<00:10:49.240> like 00:10:50.190 --> 00:10:50.200 align:start position:0% the main idea here is okay we have like 00:10:50.200 --> 00:10:52.190 align:start position:0% the main idea here is okay we have like so<00:10:50.399> in<00:10:50.560> each<00:10:50.880> so<00:10:51.120> in<00:10:51.279> each<00:10:51.480> instruction<00:10:52.040> what 00:10:52.190 --> 00:10:52.200 align:start position:0% so in each so in each instruction what 00:10:52.200 --> 00:10:54.110 align:start position:0% so in each so in each instruction what we<00:10:52.320> do<00:10:52.519> is<00:10:52.680> we<00:10:52.800> go<00:10:53.040> directly<00:10:53.440> to<00:10:53.600> memory<00:10:53.920> we<00:10:54.040> are 00:10:54.110 --> 00:10:54.120 align:start position:0% we do is we go directly to memory we are 00:10:54.120 --> 00:10:55.509 align:start position:0% we do is we go directly to memory we are doing<00:10:54.320> two<00:10:54.600> access<00:10:54.839> to<00:10:55.000> memory<00:10:55.320> we<00:10:55.399> are 00:10:55.509 --> 00:10:55.519 align:start position:0% doing two access to memory we are 00:10:55.519 --> 00:10:57.509 align:start position:0% doing two access to memory we are reading<00:10:55.800> to<00:10:55.959> things<00:10:56.200> and<00:10:56.360> we<00:10:56.440> are<00:10:56.959> storing 00:10:57.509 --> 00:10:57.519 align:start position:0% reading to things and we are storing 00:10:57.519 --> 00:11:00.509 align:start position:0% reading to things and we are storing back<00:10:57.920> to<00:10:58.160> the<00:10:58.880> story<00:10:59.399> back<00:10:59.519> to<00:10:59.639> the<00:10:59.720> memory<00:11:00.320> and 00:11:00.509 --> 00:11:00.519 align:start position:0% back to the story back to the memory and 00:11:00.519 --> 00:11:03.870 align:start position:0% back to the story back to the memory and in<00:11:00.680> this<00:11:01.399> and<00:11:01.600> this<00:11:01.839> so<00:11:02.279> this<00:11:02.399> is<00:11:02.680> the<00:11:03.279> the<00:11:03.760> the 00:11:03.870 --> 00:11:03.880 align:start position:0% in this and this so this is the the the 00:11:03.880 --> 00:11:06.470 align:start position:0% in this and this so this is the the the main<00:11:04.120> idea<00:11:04.760> okay<00:11:05.120> so<00:11:05.320> we<00:11:05.440> have<00:11:05.680> only<00:11:06.160> we<00:11:06.279> have 00:11:06.470 --> 00:11:06.480 align:start position:0% main idea okay so we have only we have 00:11:06.480 --> 00:11:08.710 align:start position:0% main idea okay so we have only we have only<00:11:06.720> one<00:11:07.519> one<00:11:07.760> register<00:11:08.240> actually<00:11:08.440> we<00:11:08.560> have<00:11:08.639> a 00:11:08.710 --> 00:11:08.720 align:start position:0% only one one register actually we have a 00:11:08.720 --> 00:11:10.389 align:start position:0% only one one register actually we have a couple<00:11:08.920> of<00:11:09.040> registers<00:11:09.440> a<00:11:09.600> program<00:11:09.920> counter<00:11:10.279> a 00:11:10.389 --> 00:11:10.399 align:start position:0% couple of registers a program counter a 00:11:10.399 --> 00:11:13.190 align:start position:0% couple of registers a program counter a kind<00:11:10.560> of<00:11:10.720> a<00:11:11.000> frame<00:11:11.320> pointer<00:11:11.600> or<00:11:11.760> stack<00:11:12.200> pointer 00:11:13.190 --> 00:11:13.200 align:start position:0% kind of a frame pointer or stack pointer 00:11:13.200 --> 00:11:16.670 align:start position:0% kind of a frame pointer or stack pointer um<00:11:13.600> in<00:11:13.920> there<00:11:14.920> we<00:11:15.079> have<00:11:15.399> this<00:11:15.720> main<00:11:16.200> so<00:11:16.480> this 00:11:16.670 --> 00:11:16.680 align:start position:0% um in there we have this main so this 00:11:16.680 --> 00:11:18.710 align:start position:0% um in there we have this main so this main<00:11:17.440> instruction<00:11:17.959> that<00:11:18.079> can<00:11:18.240> be<00:11:18.440> any 00:11:18.710 --> 00:11:18.720 align:start position:0% main instruction that can be any 00:11:18.720 --> 00:11:21.030 align:start position:0% main instruction that can be any instruction<00:11:19.360> there<00:11:19.839> so<00:11:20.000> we<00:11:20.120> have<00:11:20.279> a<00:11:20.480> way<00:11:20.880> this 00:11:21.030 --> 00:11:21.040 align:start position:0% instruction there so we have a way this 00:11:21.040 --> 00:11:24.470 align:start position:0% instruction there so we have a way this is<00:11:21.160> a<00:11:21.320> way<00:11:21.440> to<00:11:21.639> load<00:11:22.320> the<00:11:22.480> first<00:11:22.880> register<00:11:23.880> load 00:11:24.470 --> 00:11:24.480 align:start position:0% is a way to load the first register load 00:11:24.480 --> 00:11:26.470 align:start position:0% is a way to load the first register load second<00:11:24.880> registers<00:11:25.399> I<00:11:25.480> mean<00:11:25.639> you<00:11:25.760> can<00:11:26.200> load 00:11:26.470 --> 00:11:26.480 align:start position:0% second registers I mean you can load 00:11:26.480 --> 00:11:27.949 align:start position:0% second registers I mean you can load from<00:11:26.639> memory<00:11:26.959> or<00:11:27.079> you<00:11:27.160> can<00:11:27.279> load<00:11:27.560> maybe<00:11:27.800> from 00:11:27.949 --> 00:11:27.959 align:start position:0% from memory or you can load maybe from 00:11:27.959 --> 00:11:31.230 align:start position:0% from memory or you can load maybe from an<00:11:28.120> immediate<00:11:28.600> value<00:11:29.000> or<00:11:29.560> other<00:11:30.360> um<00:11:30.839> uh<00:11:30.959> things 00:11:31.230 --> 00:11:31.240 align:start position:0% an immediate value or other um uh things 00:11:31.240 --> 00:11:32.990 align:start position:0% an immediate value or other um uh things maybe<00:11:31.399> you<00:11:31.480> can<00:11:31.680> take<00:11:31.880> just<00:11:32.079> the<00:11:32.200> prev<00:11:32.600> see<00:11:32.839> and 00:11:32.990 --> 00:11:33.000 align:start position:0% maybe you can take just the prev see and 00:11:33.000 --> 00:11:38.230 align:start position:0% maybe you can take just the prev see and things<00:11:33.279> like<00:11:33.440> that<00:11:34.360> okay<00:11:35.399> um<00:11:36.399> we<00:11:36.959> um<00:11:37.279> we<00:11:37.480> store 00:11:38.230 --> 00:11:38.240 align:start position:0% things like that okay um we um we store 00:11:38.240 --> 00:11:39.949 align:start position:0% things like that okay um we um we store the<00:11:38.360> memory<00:11:38.880> we<00:11:39.120> gener<00:11:39.440> we<00:11:39.560> store<00:11:39.760> to<00:11:39.839> the 00:11:39.949 --> 00:11:39.959 align:start position:0% the memory we gener we store to the 00:11:39.959 --> 00:11:41.670 align:start position:0% the memory we gener we store to the memory<00:11:40.279> we<00:11:40.399> can<00:11:40.560> also<00:11:40.800> for<00:11:40.959> example<00:11:41.240> store<00:11:41.560> to 00:11:41.670 --> 00:11:41.680 align:start position:0% memory we can also for example store to 00:11:41.680 --> 00:11:43.629 align:start position:0% memory we can also for example store to a<00:11:41.800> program<00:11:42.079> counter<00:11:42.440> so<00:11:42.560> we<00:11:42.680> can<00:11:42.800> do<00:11:42.959> a<00:11:43.240> dynamic 00:11:43.629 --> 00:11:43.639 align:start position:0% a program counter so we can do a dynamic 00:11:43.639 --> 00:11:47.750 align:start position:0% a program counter so we can do a dynamic jump<00:11:44.079> in<00:11:44.279> there<00:11:45.040> okay<00:11:45.800> and<00:11:46.360> the<00:11:47.320> we<00:11:47.480> have<00:11:47.639> the 00:11:47.750 --> 00:11:47.760 align:start position:0% jump in there okay and the we have the 00:11:47.760 --> 00:11:49.269 align:start position:0% jump in there okay and the we have the operations<00:11:48.279> the<00:11:48.360> operations<00:11:48.760> at<00:11:48.880> the<00:11:48.959> end<00:11:49.120> is 00:11:49.269 --> 00:11:49.279 align:start position:0% operations the operations at the end is 00:11:49.279 --> 00:11:50.670 align:start position:0% operations the operations at the end is just<00:11:49.399> throw<00:11:49.680> into<00:11:49.880> the<00:11:50.000> boss<00:11:50.200> the<00:11:50.320> operation 00:11:50.670 --> 00:11:50.680 align:start position:0% just throw into the boss the operation 00:11:50.680 --> 00:11:52.829 align:start position:0% just throw into the boss the operation that<00:11:50.760> you<00:11:50.880> want<00:11:51.000> to<00:11:51.160> build<00:11:51.440> so<00:11:51.760> the<00:11:52.320> the<00:11:52.720> the 00:11:52.829 --> 00:11:52.839 align:start position:0% that you want to build so the the the 00:11:52.839 --> 00:11:55.150 align:start position:0% that you want to build so the the the main<00:11:53.079> St<00:11:53.360> machine<00:11:53.680> is<00:11:53.920> quite<00:11:54.399> uh<00:11:54.600> simple<00:11:54.959> in 00:11:55.150 --> 00:11:55.160 align:start position:0% main St machine is quite uh simple in 00:11:55.160 --> 00:11:58.750 align:start position:0% main St machine is quite uh simple in there<00:11:56.079> and<00:11:56.240> then<00:11:56.399> we<00:11:56.600> have<00:11:56.839> some<00:11:57.800> um 00:11:58.750 --> 00:11:58.760 align:start position:0% there and then we have some um 00:11:58.760 --> 00:12:01.470 align:start position:0% there and then we have some um conditional<00:11:59.240> jumps<00:12:00.040> uh<00:12:00.160> somehow<00:12:00.639> I<00:12:00.680> mean<00:12:00.839> this 00:12:01.470 --> 00:12:01.480 align:start position:0% conditional jumps uh somehow I mean this 00:12:01.480 --> 00:12:03.910 align:start position:0% conditional jumps uh somehow I mean this this<00:12:01.800> logic<00:12:02.360> there<00:12:02.560> at<00:12:02.680> the<00:12:02.760> end<00:12:02.920> we<00:12:03.000> are<00:12:03.560> just 00:12:03.910 --> 00:12:03.920 align:start position:0% this logic there at the end we are just 00:12:03.920 --> 00:12:06.750 align:start position:0% this logic there at the end we are just so<00:12:04.160> the<00:12:04.279> operations<00:12:04.760> is<00:12:05.040> a<00:12:05.639> plus<00:12:05.880> b<00:12:06.120> equals<00:12:06.440> c 00:12:06.750 --> 00:12:06.760 align:start position:0% so the operations is a plus b equals c 00:12:06.760 --> 00:12:09.910 align:start position:0% so the operations is a plus b equals c maybe<00:12:07.000> with<00:12:07.200> aari<00:12:07.680> or<00:12:07.920> with<00:12:08.240> a<00:12:08.680> some<00:12:08.920> flag<00:12:09.600> that 00:12:09.910 --> 00:12:09.920 align:start position:0% maybe with aari or with a some flag that 00:12:09.920 --> 00:12:11.829 align:start position:0% maybe with aari or with a some flag that you<00:12:10.120> where<00:12:10.240> you<00:12:10.360> can<00:12:10.519> do<00:12:10.680> a<00:12:10.839> jump<00:12:11.320> to<00:12:11.519> one<00:12:11.680> line 00:12:11.829 --> 00:12:11.839 align:start position:0% you where you can do a jump to one line 00:12:11.839 --> 00:12:14.030 align:start position:0% you where you can do a jump to one line of<00:12:12.000> cod<00:12:12.279> or<00:12:12.440> a<00:12:12.560> different<00:12:12.880> line<00:12:13.440> of<00:12:13.639> cod<00:12:13.920> so 00:12:14.030 --> 00:12:14.040 align:start position:0% of cod or a different line of cod so 00:12:14.040 --> 00:12:16.189 align:start position:0% of cod or a different line of cod so this<00:12:14.160> is<00:12:14.360> very<00:12:14.560> a<00:12:14.639> little<00:12:14.800> bit<00:12:15.040> the<00:12:15.680> the<00:12:16.000> the 00:12:16.189 --> 00:12:16.199 align:start position:0% this is very a little bit the the the 00:12:16.199 --> 00:12:18.750 align:start position:0% this is very a little bit the the the the<00:12:16.320> deepness<00:12:17.000> the<00:12:17.079> big<00:12:17.279> idea<00:12:17.600> of<00:12:17.800> the<00:12:18.320> FK 00:12:18.750 --> 00:12:18.760 align:start position:0% the deepness the big idea of the FK 00:12:18.760 --> 00:12:22.110 align:start position:0% the deepness the big idea of the FK itself<00:12:19.560> okay<00:12:20.240> and<00:12:21.000> as<00:12:21.120> I<00:12:21.279> told<00:12:21.480> you<00:12:21.680> this<00:12:21.839> goes 00:12:22.110 --> 00:12:22.120 align:start position:0% itself okay and as I told you this goes 00:12:22.120 --> 00:12:24.790 align:start position:0% itself okay and as I told you this goes through<00:12:22.360> this<00:12:23.079> through<00:12:23.320> this<00:12:23.480> bus<00:12:24.079> okay<00:12:24.480> and 00:12:24.790 --> 00:12:24.800 align:start position:0% through this through this bus okay and 00:12:24.800 --> 00:12:26.430 align:start position:0% through this through this bus okay and one<00:12:24.920> of<00:12:25.040> the<00:12:25.199> advantages<00:12:25.760> and<00:12:25.920> I<00:12:26.000> want<00:12:26.120> to<00:12:26.240> see 00:12:26.430 --> 00:12:26.440 align:start position:0% one of the advantages and I want to see 00:12:26.440 --> 00:12:28.910 align:start position:0% one of the advantages and I want to see here<00:12:26.560> I<00:12:26.639> won't<00:12:26.880> give<00:12:27.000> you<00:12:27.120> details<00:12:27.680> about<00:12:28.079> the 00:12:28.910 --> 00:12:28.920 align:start position:0% here I won't give you details about the 00:12:28.920 --> 00:12:31.870 align:start position:0% here I won't give you details about the why<00:12:29.560> uh<00:12:30.040> this<00:12:30.240> architecture<00:12:30.760> is<00:12:30.959> very<00:12:31.160> optimal 00:12:31.870 --> 00:12:31.880 align:start position:0% why uh this architecture is very optimal 00:12:31.880 --> 00:12:33.990 align:start position:0% why uh this architecture is very optimal for<00:12:32.040> example<00:12:32.360> when<00:12:32.480> you<00:12:32.639> have<00:12:32.800> an<00:12:33.160> um<00:12:33.360> a 00:12:33.990 --> 00:12:34.000 align:start position:0% for example when you have an um a 00:12:34.000 --> 00:12:36.030 align:start position:0% for example when you have an um a multiplication<00:12:35.000> so<00:12:35.160> the<00:12:35.279> six<00:12:35.519> processor<00:12:35.920> is 00:12:36.030 --> 00:12:36.040 align:start position:0% multiplication so the six processor is 00:12:36.040 --> 00:12:38.750 align:start position:0% multiplication so the six processor is sending<00:12:36.760> that<00:12:37.199> and<00:12:37.720> uh<00:12:37.839> the<00:12:37.959> arithmetic<00:12:38.600> is 00:12:38.750 --> 00:12:38.760 align:start position:0% sending that and uh the arithmetic is 00:12:38.760 --> 00:12:41.470 align:start position:0% sending that and uh the arithmetic is also<00:12:39.320> somehow<00:12:39.959> proving<00:12:40.680> that<00:12:41.000> specific 00:12:41.470 --> 00:12:41.480 align:start position:0% also somehow proving that specific 00:12:41.480 --> 00:12:43.910 align:start position:0% also somehow proving that specific operation<00:12:42.240> in<00:12:42.440> there<00:12:42.880> okay<00:12:43.240> so<00:12:43.360> you<00:12:43.480> can<00:12:43.680> have 00:12:43.910 --> 00:12:43.920 align:start position:0% operation in there okay so you can have 00:12:43.920 --> 00:12:47.110 align:start position:0% operation in there okay so you can have this<00:12:44.160> arithmetic<00:12:44.880> operation<00:12:45.880> but<00:12:46.680> one<00:12:46.880> thing 00:12:47.110 --> 00:12:47.120 align:start position:0% this arithmetic operation but one thing 00:12:47.120 --> 00:12:48.949 align:start position:0% this arithmetic operation but one thing one<00:12:47.320> optimization<00:12:48.000> that<00:12:48.120> we<00:12:48.240> can<00:12:48.360> do<00:12:48.560> is<00:12:48.800> okay 00:12:48.949 --> 00:12:48.959 align:start position:0% one optimization that we can do is okay 00:12:48.959 --> 00:12:50.710 align:start position:0% one optimization that we can do is okay for<00:12:49.120> example<00:12:49.440> imagine<00:12:49.880> there<00:12:49.959> are<00:12:50.120> a<00:12:50.240> lot<00:12:50.399> of 00:12:50.710 --> 00:12:50.720 align:start position:0% for example imagine there are a lot of 00:12:50.720 --> 00:12:53.670 align:start position:0% for example imagine there are a lot of uh<00:12:51.040> operations<00:12:51.680> that<00:12:51.800> are<00:12:52.519> uh<00:12:52.680> usual<00:12:53.399> when<00:12:53.519> I'm 00:12:53.670 --> 00:12:53.680 align:start position:0% uh operations that are uh usual when I'm 00:12:53.680 --> 00:12:57.069 align:start position:0% uh operations that are uh usual when I'm doing<00:12:53.920> for<00:12:54.079> example<00:12:54.639> 1+<00:12:55.160> 1<00:12:55.600> or<00:12:56.079> uh<00:12:56.199> 3<00:12:56.519> +<00:12:56.760> 1<00:12:57.000> I 00:12:57.069 --> 00:12:57.079 align:start position:0% doing for example 1+ 1 or uh 3 + 1 I 00:12:57.079 --> 00:12:58.910 align:start position:0% doing for example 1+ 1 or uh 3 + 1 I mean<00:12:57.240> I'm<00:12:57.360> doing<00:12:57.560> the<00:12:57.680> small<00:12:57.920> numbers<00:12:58.800> I'm 00:12:58.910 --> 00:12:58.920 align:start position:0% mean I'm doing the small numbers I'm 00:12:58.920 --> 00:13:01.670 align:start position:0% mean I'm doing the small numbers I'm going<00:12:59.040> to<00:12:59.279> do<00:12:59.440> a<00:12:59.560> lot<00:12:59.760> of<00:12:59.959> them<00:13:00.560> in<00:13:00.800> the<00:13:01.360> in<00:13:01.480> the 00:13:01.670 --> 00:13:01.680 align:start position:0% going to do a lot of them in the in the 00:13:01.680 --> 00:13:03.910 align:start position:0% going to do a lot of them in the in the processor<00:13:02.399> so<00:13:02.600> instead<00:13:03.000> of<00:13:03.160> proving<00:13:03.560> all<00:13:03.720> of 00:13:03.910 --> 00:13:03.920 align:start position:0% processor so instead of proving all of 00:13:03.920 --> 00:13:06.629 align:start position:0% processor so instead of proving all of them<00:13:04.320> in<00:13:04.399> the<00:13:04.560> processor<00:13:05.040> I<00:13:05.120> can<00:13:05.440> have<00:13:06.320> um 00:13:06.629 --> 00:13:06.639 align:start position:0% them in the processor I can have um 00:13:06.639 --> 00:13:08.470 align:start position:0% them in the processor I can have um another<00:13:07.000> steam<00:13:07.320> machine<00:13:07.680> that's<00:13:07.920> kind<00:13:08.120> of<00:13:08.279> a 00:13:08.470 --> 00:13:08.480 align:start position:0% another steam machine that's kind of a 00:13:08.480 --> 00:13:10.990 align:start position:0% another steam machine that's kind of a cash<00:13:08.959> where<00:13:09.240> I<00:13:09.360> have<00:13:09.600> precomputed<00:13:10.240> operations 00:13:10.990 --> 00:13:11.000 align:start position:0% cash where I have precomputed operations 00:13:11.000 --> 00:13:13.790 align:start position:0% cash where I have precomputed operations that<00:13:11.120> are<00:13:11.279> used<00:13:11.639> quite<00:13:11.839> often<00:13:12.560> and<00:13:12.720> then<00:13:13.199> so<00:13:13.560> so 00:13:13.790 --> 00:13:13.800 align:start position:0% that are used quite often and then so so 00:13:13.800 --> 00:13:15.509 align:start position:0% that are used quite often and then so so the<00:13:14.040> processor<00:13:14.519> it's<00:13:14.680> always<00:13:15.000> it's<00:13:15.399> it's 00:13:15.509 --> 00:13:15.519 align:start position:0% the processor it's always it's it's 00:13:15.519 --> 00:13:17.990 align:start position:0% the processor it's always it's it's sending<00:13:15.880> the<00:13:16.000> same<00:13:16.240> thing<00:13:16.720> but<00:13:16.920> then<00:13:17.360> these<00:13:17.800> uh 00:13:17.990 --> 00:13:18.000 align:start position:0% sending the same thing but then these uh 00:13:18.000 --> 00:13:20.030 align:start position:0% sending the same thing but then these uh basic<00:13:18.360> operations<00:13:18.959> can<00:13:19.120> be<00:13:19.279> sended<00:13:19.800> can<00:13:19.920> be 00:13:20.030 --> 00:13:20.040 align:start position:0% basic operations can be sended can be 00:13:20.040 --> 00:13:21.829 align:start position:0% basic operations can be sended can be proven<00:13:20.399> back<00:13:20.560> to<00:13:20.680> the<00:13:20.800> bus<00:13:21.320> so<00:13:21.519> that<00:13:21.600> means 00:13:21.829 --> 00:13:21.839 align:start position:0% proven back to the bus so that means 00:13:21.839 --> 00:13:23.430 align:start position:0% proven back to the bus so that means that<00:13:21.959> for<00:13:22.160> these<00:13:22.399> small<00:13:22.680> operations<00:13:23.160> or<00:13:23.279> for 00:13:23.430 --> 00:13:23.440 align:start position:0% that for these small operations or for 00:13:23.440 --> 00:13:26.110 align:start position:0% that for these small operations or for these<00:13:23.600> usual<00:13:23.959> operations<00:13:24.959> the<00:13:25.480> cost<00:13:25.839> I<00:13:25.920> mean 00:13:26.110 --> 00:13:26.120 align:start position:0% these usual operations the cost I mean 00:13:26.120 --> 00:13:27.990 align:start position:0% these usual operations the cost I mean the<00:13:26.199> number<00:13:26.440> of<00:13:26.560> cells<00:13:27.120> that<00:13:27.240> we<00:13:27.320> are<00:13:27.440> doing 00:13:27.990 --> 00:13:28.000 align:start position:0% the number of cells that we are doing 00:13:28.000 --> 00:13:32.470 align:start position:0% the number of cells that we are doing are<00:13:28.920> uh<00:13:29.240> very<00:13:29.800> low<00:13:30.800> okay<00:13:31.720> can<00:13:31.920> extend<00:13:32.279> this 00:13:32.470 --> 00:13:32.480 align:start position:0% are uh very low okay can extend this 00:13:32.480 --> 00:13:34.389 align:start position:0% are uh very low okay can extend this idea<00:13:33.000> so<00:13:33.199> we<00:13:33.360> can<00:13:33.600> have<00:13:33.800> this<00:13:33.959> processor 00:13:34.389 --> 00:13:34.399 align:start position:0% idea so we can have this processor 00:13:34.399 --> 00:13:36.509 align:start position:0% idea so we can have this processor imagine<00:13:34.800> that<00:13:34.959> I<00:13:35.120> have<00:13:35.320> a<00:13:35.680> operations<00:13:36.240> I<00:13:36.320> can 00:13:36.509 --> 00:13:36.519 align:start position:0% imagine that I have a operations I can 00:13:36.519 --> 00:13:38.590 align:start position:0% imagine that I have a operations I can have<00:13:36.680> a<00:13:36.800> usual<00:13:37.199> operations<00:13:37.639> table<00:13:38.160> I<00:13:38.279> can<00:13:38.440> have 00:13:38.590 --> 00:13:38.600 align:start position:0% have a usual operations table I can have 00:13:38.600 --> 00:13:40.389 align:start position:0% have a usual operations table I can have operations<00:13:39.079> that<00:13:39.199> are<00:13:39.360> doing<00:13:39.680> so<00:13:39.880> a<00:13:40.040> specific 00:13:40.389 --> 00:13:40.399 align:start position:0% operations that are doing so a specific 00:13:40.399 --> 00:13:42.389 align:start position:0% operations that are doing so a specific stain<00:13:40.680> machine<00:13:41.000> that's<00:13:41.160> doing<00:13:41.680> 32<00:13:42.120> bits 00:13:42.389 --> 00:13:42.399 align:start position:0% stain machine that's doing 32 bits 00:13:42.399 --> 00:13:43.750 align:start position:0% stain machine that's doing 32 bits operations<00:13:42.800> and<00:13:42.959> another<00:13:43.240> stain<00:13:43.480> machine 00:13:43.750 --> 00:13:43.760 align:start position:0% operations and another stain machine 00:13:43.760 --> 00:13:46.030 align:start position:0% operations and another stain machine that<00:13:43.839> are<00:13:44.000> doing<00:13:44.279> 64<00:13:45.279> uh<00:13:45.440> stain<00:13:45.720> machines 00:13:46.030 --> 00:13:46.040 align:start position:0% that are doing 64 uh stain machines 00:13:46.040 --> 00:13:48.189 align:start position:0% that are doing 64 uh stain machines operations<00:13:46.519> just<00:13:46.639> to<00:13:46.839> save<00:13:47.600> here<00:13:47.880> just<00:13:48.040> to 00:13:48.189 --> 00:13:48.199 align:start position:0% operations just to save here just to 00:13:48.199 --> 00:13:50.949 align:start position:0% operations just to save here just to save<00:13:48.760> uh<00:13:49.240> space 00:13:50.949 --> 00:13:50.959 align:start position:0% save uh space 00:13:50.959 --> 00:13:53.710 align:start position:0% save uh space okay<00:13:51.959> this<00:13:52.120> idea<00:13:52.440> for<00:13:52.680> works<00:13:52.880> for<00:13:53.079> example<00:13:53.360> for 00:13:53.710 --> 00:13:53.720 align:start position:0% okay this idea for works for example for 00:13:53.720 --> 00:13:56.150 align:start position:0% okay this idea for works for example for memory<00:13:54.079> for<00:13:54.320> the<00:13:54.480> memory<00:13:55.279> memory<00:13:55.600> alignment<00:13:56.079> I 00:13:56.150 --> 00:13:56.160 align:start position:0% memory for the memory memory alignment I 00:13:56.160 --> 00:13:57.710 align:start position:0% memory for the memory memory alignment I mean<00:13:56.320> what<00:13:56.440> I'm<00:13:56.560> doing<00:13:56.800> in<00:13:56.920> general<00:13:57.240> most<00:13:57.639> of 00:13:57.710 --> 00:13:57.720 align:start position:0% mean what I'm doing in general most of 00:13:57.720 --> 00:14:00.269 align:start position:0% mean what I'm doing in general most of the<00:13:57.800> process<00:13:58.040> are<00:13:58.160> doing<00:13:58.720> uh<00:13:59.199> reads<00:13:59.720> and<00:13:59.920> bries 00:14:00.269 --> 00:14:00.279 align:start position:0% the process are doing uh reads and bries 00:14:00.279 --> 00:14:03.069 align:start position:0% the process are doing uh reads and bries that<00:14:00.360> are<00:14:00.560> aligned<00:14:01.519> well<00:14:01.880> no<00:14:02.160> problem<00:14:02.560> the<00:14:02.920> the 00:14:03.069 --> 00:14:03.079 align:start position:0% that are aligned well no problem the the 00:14:03.079 --> 00:14:05.350 align:start position:0% that are aligned well no problem the the processor<00:14:03.519> is<00:14:03.639> doing<00:14:03.920> some<00:14:04.120> memory<00:14:04.480> operation 00:14:05.350 --> 00:14:05.360 align:start position:0% processor is doing some memory operation 00:14:05.360 --> 00:14:07.949 align:start position:0% processor is doing some memory operation and<00:14:05.519> the<00:14:05.680> memory<00:14:06.040> that<00:14:06.240> just<00:14:06.399> works<00:14:06.759> in<00:14:07.240> in<00:14:07.440> 64 00:14:07.949 --> 00:14:07.959 align:start position:0% and the memory that just works in in 64 00:14:07.959 --> 00:14:11.389 align:start position:0% and the memory that just works in in 64 bits<00:14:08.480> 64<00:14:08.959> bits<00:14:09.480> uh<00:14:09.680> words<00:14:10.680> then<00:14:10.959> you're<00:14:11.199> doing 00:14:11.389 --> 00:14:11.399 align:start position:0% bits 64 bits uh words then you're doing 00:14:11.399 --> 00:14:13.509 align:start position:0% bits 64 bits uh words then you're doing a<00:14:11.600> read<00:14:12.000> aligned<00:14:12.519> read<00:14:12.839> you<00:14:13.000> get<00:14:13.120> it<00:14:13.240> from<00:14:13.399> the 00:14:13.509 --> 00:14:13.519 align:start position:0% a read aligned read you get it from the 00:14:13.519 --> 00:14:15.269 align:start position:0% a read aligned read you get it from the memory<00:14:14.160> aligned<00:14:14.519> read<00:14:14.680> you<00:14:14.800> get<00:14:14.880> it<00:14:14.959> from<00:14:15.160> the 00:14:15.269 --> 00:14:15.279 align:start position:0% memory aligned read you get it from the 00:14:15.279 --> 00:14:17.389 align:start position:0% memory aligned read you get it from the memory<00:14:15.839> but<00:14:16.040> what<00:14:16.279> happen<00:14:16.880> when<00:14:17.040> you<00:14:17.160> are 00:14:17.389 --> 00:14:17.399 align:start position:0% memory but what happen when you are 00:14:17.399 --> 00:14:20.629 align:start position:0% memory but what happen when you are reading<00:14:18.000> an<00:14:18.199> an<00:14:18.399> align<00:14:18.800> it<00:14:19.279> well<00:14:19.639> we<00:14:19.759> can<00:14:20.040> have 00:14:20.629 --> 00:14:20.639 align:start position:0% reading an an align it well we can have 00:14:20.639 --> 00:14:22.949 align:start position:0% reading an an align it well we can have a<00:14:21.040> special<00:14:21.440> St<00:14:21.800> machine<00:14:22.320> that's<00:14:22.519> solving 00:14:22.949 --> 00:14:22.959 align:start position:0% a special St machine that's solving 00:14:22.959 --> 00:14:25.949 align:start position:0% a special St machine that's solving these<00:14:23.240> un<00:14:23.519> aligning<00:14:24.279> things<00:14:24.560> and<00:14:24.959> actually<00:14:25.320> is 00:14:25.949 --> 00:14:25.959 align:start position:0% these un aligning things and actually is 00:14:25.959 --> 00:14:28.870 align:start position:0% these un aligning things and actually is okay<00:14:26.320> so<00:14:26.560> you<00:14:26.680> want<00:14:27.079> a<00:14:27.240> non-aligned<00:14:27.920> operation 00:14:28.870 --> 00:14:28.880 align:start position:0% okay so you want a non-aligned operation 00:14:28.880 --> 00:14:32.550 align:start position:0% okay so you want a non-aligned operation this<00:14:29.160> is<00:14:29.800> solve<00:14:30.800> so<00:14:31.800> the<00:14:31.959> the<00:14:32.040> arrow<00:14:32.320> to<00:14:32.440> the 00:14:32.550 --> 00:14:32.560 align:start position:0% this is solve so the the arrow to the 00:14:32.560 --> 00:14:35.389 align:start position:0% this is solve so the the arrow to the bus<00:14:32.759> means<00:14:33.040> adding<00:14:33.320> to<00:14:33.480> the<00:14:33.600> bus<00:14:34.320> the<00:14:35.320> the 00:14:35.389 --> 00:14:35.399 align:start position:0% bus means adding to the bus the the 00:14:35.399 --> 00:14:36.749 align:start position:0% bus means adding to the bus the the other<00:14:35.600> arrow<00:14:35.880> that<00:14:36.000> goes<00:14:36.160> in<00:14:36.279> the<00:14:36.360> other<00:14:36.519> way 00:14:36.749 --> 00:14:36.759 align:start position:0% other arrow that goes in the other way 00:14:36.759 --> 00:14:39.230 align:start position:0% other arrow that goes in the other way subtract<00:14:37.240> to<00:14:37.399> the<00:14:37.519> BS<00:14:37.839> so<00:14:38.399> okay<00:14:38.680> I'm<00:14:38.839> proving 00:14:39.230 --> 00:14:39.240 align:start position:0% subtract to the BS so okay I'm proving 00:14:39.240 --> 00:14:41.030 align:start position:0% subtract to the BS so okay I'm proving this<00:14:39.480> but<00:14:39.759> in<00:14:39.880> order<00:14:40.120> to<00:14:40.279> prove<00:14:40.560> this<00:14:40.800> I<00:14:40.880> need 00:14:41.030 --> 00:14:41.040 align:start position:0% this but in order to prove this I need 00:14:41.040 --> 00:14:43.350 align:start position:0% this but in order to prove this I need to<00:14:41.199> do<00:14:41.639> two<00:14:41.880> R<00:14:42.279> operations<00:14:42.839> and<00:14:43.000> of<00:14:43.120> course 00:14:43.350 --> 00:14:43.360 align:start position:0% to do two R operations and of course 00:14:43.360 --> 00:14:45.910 align:start position:0% to do two R operations and of course some<00:14:44.040> Logic<00:14:44.399> for<00:14:44.680> check<00:14:44.959> I<00:14:45.000> mean<00:14:45.199> for<00:14:45.360> putting 00:14:45.910 --> 00:14:45.920 align:start position:0% some Logic for check I mean for putting 00:14:45.920 --> 00:14:48.030 align:start position:0% some Logic for check I mean for putting these<00:14:46.079> two<00:14:46.639> two<00:14:46.839> reads<00:14:47.240> in<00:14:47.399> the<00:14:47.560> same<00:14:47.839> in<00:14:47.920> the 00:14:48.030 --> 00:14:48.040 align:start position:0% these two two reads in the same in the 00:14:48.040 --> 00:14:49.470 align:start position:0% these two two reads in the same in the same<00:14:48.240> one<00:14:48.560> and<00:14:48.680> then<00:14:48.880> of<00:14:49.000> course<00:14:49.160> the<00:14:49.279> same 00:14:49.470 --> 00:14:49.480 align:start position:0% same one and then of course the same 00:14:49.480 --> 00:14:51.509 align:start position:0% same one and then of course the same memory<00:14:49.759> machine<00:14:50.320> is<00:14:50.480> doing<00:14:50.839> these<00:14:51.199> uh<00:14:51.320> two 00:14:51.509 --> 00:14:51.519 align:start position:0% memory machine is doing these uh two 00:14:51.519 --> 00:14:53.990 align:start position:0% memory machine is doing these uh two reads<00:14:51.920> in<00:14:52.160> there<00:14:52.600> this<00:14:52.759> allows<00:14:53.079> us<00:14:53.199> to<00:14:53.360> do<00:14:53.600> this 00:14:53.990 --> 00:14:54.000 align:start position:0% reads in there this allows us to do this 00:14:54.000 --> 00:14:56.910 align:start position:0% reads in there this allows us to do this kind<00:14:54.199> of<00:14:55.079> techniques<00:14:56.079> it<00:14:56.240> allows<00:14:56.519> us<00:14:56.639> to<00:14:56.759> do 00:14:56.910 --> 00:14:56.920 align:start position:0% kind of techniques it allows us to do 00:14:56.920 --> 00:14:58.910 align:start position:0% kind of techniques it allows us to do for<00:14:57.040> example<00:14:57.399> continuations<00:14:58.279> in<00:14:58.399> a<00:14:58.519> very<00:14:58.720> easy 00:14:58.910 --> 00:14:58.920 align:start position:0% for example continuations in a very easy 00:14:58.920 --> 00:15:01.590 align:start position:0% for example continuations in a very easy way<00:14:59.120> way<00:14:59.560> so<00:15:00.079> if<00:15:00.240> I<00:15:00.399> have<00:15:00.560> a<00:15:00.880> processor<00:15:01.320> I<00:15:01.399> mean 00:15:01.590 --> 00:15:01.600 align:start position:0% way way so if I have a processor I mean 00:15:01.600 --> 00:15:04.870 align:start position:0% way way so if I have a processor I mean I<00:15:01.720> have<00:15:01.880> a<00:15:02.360> I<00:15:02.480> can<00:15:02.800> I<00:15:02.880> can<00:15:03.199> I<00:15:03.480> I<00:15:03.560> can<00:15:04.360> divide<00:15:04.720> the 00:15:04.870 --> 00:15:04.880 align:start position:0% I have a I can I can I I can divide the 00:15:04.880 --> 00:15:07.030 align:start position:0% I have a I can I can I I can divide the execution<00:15:05.320> in<00:15:05.480> different<00:15:06.079> different<00:15:06.440> slots 00:15:07.030 --> 00:15:07.040 align:start position:0% execution in different different slots 00:15:07.040 --> 00:15:08.749 align:start position:0% execution in different different slots in<00:15:07.199> different<00:15:07.600> different<00:15:07.880> phes<00:15:08.360> okay<00:15:08.480> so<00:15:08.680> it 00:15:08.749 --> 00:15:08.759 align:start position:0% in different different phes okay so it 00:15:08.759 --> 00:15:11.310 align:start position:0% in different different phes okay so it this<00:15:09.120> the<00:15:09.279> first<00:15:09.920> 100<00:15:10.240> clocks<00:15:10.680> second<00:15:11.160> 100 00:15:11.310 --> 00:15:11.320 align:start position:0% this the first 100 clocks second 100 00:15:11.320 --> 00:15:13.470 align:start position:0% this the first 100 clocks second 100 clocks<00:15:11.600> and<00:15:11.720> so<00:15:11.839> on<00:15:12.279> so<00:15:12.480> I<00:15:12.720> I<00:15:12.880> can<00:15:13.199> I<00:15:13.279> can't 00:15:13.470 --> 00:15:13.480 align:start position:0% clocks and so on so I I can I can't 00:15:13.480 --> 00:15:16.310 align:start position:0% clocks and so on so I I can I can't divide<00:15:13.880> them<00:15:14.480> but<00:15:15.000> at<00:15:15.120> the<00:15:15.199> end<00:15:15.360> of<00:15:15.480> the 00:15:16.310 --> 00:15:16.320 align:start position:0% divide them but at the end of the 00:15:16.320 --> 00:15:19.110 align:start position:0% divide them but at the end of the processor<00:15:17.320> so<00:15:17.920> I<00:15:18.040> need<00:15:18.199> to<00:15:18.399> connect<00:15:18.759> I<00:15:18.839> mean 00:15:19.110 --> 00:15:19.120 align:start position:0% processor so I need to connect I mean 00:15:19.120 --> 00:15:21.910 align:start position:0% processor so I need to connect I mean the<00:15:19.839> the<00:15:19.959> next<00:15:20.360> slot<00:15:20.920> needs<00:15:21.160> to<00:15:21.360> have<00:15:21.519> the<00:15:21.639> same 00:15:21.910 --> 00:15:21.920 align:start position:0% the the next slot needs to have the same 00:15:21.920 --> 00:15:23.870 align:start position:0% the the next slot needs to have the same state<00:15:22.240> that<00:15:22.399> when<00:15:22.519> I<00:15:22.639> finish<00:15:23.320> well<00:15:23.519> what<00:15:23.639> I<00:15:23.759> can 00:15:23.870 --> 00:15:23.880 align:start position:0% state that when I finish well what I can 00:15:23.880 --> 00:15:27.030 align:start position:0% state that when I finish well what I can do<00:15:24.040> is<00:15:24.199> just<00:15:24.360> send<00:15:25.279> this<00:15:25.759> uh<00:15:25.959> state<00:15:26.240> to<00:15:26.360> the<00:15:26.519> bus 00:15:27.030 --> 00:15:27.040 align:start position:0% do is just send this uh state to the bus 00:15:27.040 --> 00:15:29.509 align:start position:0% do is just send this uh state to the bus uh<00:15:27.440> and<00:15:27.880> recover<00:15:28.480> this<00:15:28.680> state<00:15:29.000> from<00:15:29.160> the<00:15:29.240> bus 00:15:29.509 --> 00:15:29.519 align:start position:0% uh and recover this state from the bus 00:15:29.519 --> 00:15:32.030 align:start position:0% uh and recover this state from the bus and<00:15:29.680> then<00:15:29.880> connecting<00:15:30.360> all<00:15:30.600> them<00:15:31.040> together 00:15:32.030 --> 00:15:32.040 align:start position:0% and then connecting all them together 00:15:32.040 --> 00:15:33.629 align:start position:0% and then connecting all them together okay<00:15:32.240> the<00:15:32.399> final<00:15:32.680> one<00:15:32.880> the<00:15:32.959> first<00:15:33.160> one<00:15:33.319> this<00:15:33.480> is 00:15:33.629 --> 00:15:33.639 align:start position:0% okay the final one the first one this is 00:15:33.639 --> 00:15:35.710 align:start position:0% okay the final one the first one this is because<00:15:33.880> it's<00:15:34.120> cyclic<00:15:34.560> I<00:15:34.639> mean<00:15:35.079> z<00:15:35.399> in<00:15:35.480> general 00:15:35.710 --> 00:15:35.720 align:start position:0% because it's cyclic I mean z in general 00:15:35.720 --> 00:15:38.470 align:start position:0% because it's cyclic I mean z in general we<00:15:35.839> wor<00:15:36.000> cyclic<00:15:36.399> and<00:15:36.560> then<00:15:37.360> disconnects<00:15:38.360> the 00:15:38.470 --> 00:15:38.480 align:start position:0% we wor cyclic and then disconnects the 00:15:38.480 --> 00:15:41.470 align:start position:0% we wor cyclic and then disconnects the same<00:15:38.800> with<00:15:39.279> uh<00:15:39.560> continuations<00:15:40.160> in<00:15:40.319> the<00:15:40.480> ram 00:15:41.470 --> 00:15:41.480 align:start position:0% same with uh continuations in the ram 00:15:41.480 --> 00:15:42.870 align:start position:0% same with uh continuations in the ram continuations<00:15:42.000> in<00:15:42.120> the<00:15:42.240> ram<00:15:42.440> of<00:15:42.560> course<00:15:42.720> is 00:15:42.870 --> 00:15:42.880 align:start position:0% continuations in the ram of course is 00:15:42.880 --> 00:15:46.670 align:start position:0% continuations in the ram of course is not<00:15:43.720> time<00:15:44.319> frame<00:15:45.000> in<00:15:45.120> the<00:15:45.240> ram<00:15:45.440> you<00:15:45.560> want<00:15:45.800> more 00:15:46.670 --> 00:15:46.680 align:start position:0% not time frame in the ram you want more 00:15:46.680 --> 00:15:49.949 align:start position:0% not time frame in the ram you want more address<00:15:47.360> uh<00:15:47.480> face<00:15:47.880> but<00:15:48.360> so<00:15:48.720> I<00:15:48.839> can<00:15:49.079> divide<00:15:49.759> the 00:15:49.949 --> 00:15:49.959 align:start position:0% address uh face but so I can divide the 00:15:49.959 --> 00:15:52.110 align:start position:0% address uh face but so I can divide the proof<00:15:50.240> of<00:15:50.319> the<00:15:50.440> ram<00:15:50.720> that<00:15:50.839> can<00:15:50.959> be<00:15:51.120> big<00:15:51.480> in 00:15:52.110 --> 00:15:52.120 align:start position:0% proof of the ram that can be big in 00:15:52.120 --> 00:15:54.389 align:start position:0% proof of the ram that can be big in smaller<00:15:52.600> pieces<00:15:53.360> and<00:15:53.639> but<00:15:53.800> the<00:15:53.920> idea<00:15:54.160> is<00:15:54.279> the 00:15:54.389 --> 00:15:54.399 align:start position:0% smaller pieces and but the idea is the 00:15:54.399 --> 00:15:56.670 align:start position:0% smaller pieces and but the idea is the same<00:15:54.680> I<00:15:54.800> have<00:15:54.959> an<00:15:55.160> State<00:15:55.480> transition<00:15:55.959> function 00:15:56.670 --> 00:15:56.680 align:start position:0% same I have an State transition function 00:15:56.680 --> 00:15:59.710 align:start position:0% same I have an State transition function that<00:15:56.839> goes<00:15:57.079> line<00:15:57.279> by<00:15:57.480> line<00:15:58.079> but<00:15:58.639> uh<00:15:59.240> from<00:15:59.480> the 00:15:59.710 --> 00:15:59.720 align:start position:0% that goes line by line but uh from the 00:15:59.720 --> 00:16:03.069 align:start position:0% that goes line by line but uh from the one<00:15:59.920> Chun<00:16:00.240> to<00:16:00.399> the<00:16:00.519> next<00:16:00.680> Chun<00:16:01.440> I<00:16:01.680> I<00:16:01.800> can<00:16:02.600> um 00:16:03.069 --> 00:16:03.079 align:start position:0% one Chun to the next Chun I I can um 00:16:03.079 --> 00:16:04.870 align:start position:0% one Chun to the next Chun I I can um send<00:16:03.440> this<00:16:03.759> the<00:16:03.920> state<00:16:04.160> of<00:16:04.279> the<00:16:04.360> run<00:16:04.639> to<00:16:04.759> the 00:16:04.870 --> 00:16:04.880 align:start position:0% send this the state of the run to the 00:16:04.880 --> 00:16:06.509 align:start position:0% send this the state of the run to the bus<00:16:05.199> recover<00:16:05.600> the<00:16:05.720> state<00:16:05.920> of<00:16:06.040> the<00:16:06.120> run<00:16:06.360> to<00:16:06.440> the 00:16:06.509 --> 00:16:06.519 align:start position:0% bus recover the state of the run to the 00:16:06.519 --> 00:16:08.430 align:start position:0% bus recover the state of the run to the bus<00:16:06.880> the<00:16:07.079> last<00:16:07.279> the<00:16:07.399> last<00:16:07.680> address<00:16:08.120> that<00:16:08.319> you 00:16:08.430 --> 00:16:08.440 align:start position:0% bus the last the last address that you 00:16:08.440 --> 00:16:11.150 align:start position:0% bus the last the last address that you are<00:16:09.000> reading<00:16:09.399> or<00:16:09.600> writing<00:16:10.440> and<00:16:10.639> then<00:16:10.839> you<00:16:10.959> can 00:16:11.150 --> 00:16:11.160 align:start position:0% are reading or writing and then you can 00:16:11.160 --> 00:16:12.710 align:start position:0% are reading or writing and then you can continue<00:16:11.560> so<00:16:11.720> we<00:16:11.839> can<00:16:12.000> split<00:16:12.360> also<00:16:12.560> for 00:16:12.710 --> 00:16:12.720 align:start position:0% continue so we can split also for 00:16:12.720 --> 00:16:15.069 align:start position:0% continue so we can split also for example<00:16:13.040> the<00:16:13.199> ram<00:16:13.839> in<00:16:14.040> there<00:16:14.360> so<00:16:14.560> this<00:16:14.680> allows 00:16:15.069 --> 00:16:15.079 align:start position:0% example the ram in there so this allows 00:16:15.079 --> 00:16:17.749 align:start position:0% example the ram in there so this allows us<00:16:15.399> to<00:16:16.399> divide<00:16:16.839> all<00:16:17.079> the<00:16:17.199> work<00:16:17.399> I<00:16:17.480> mean<00:16:17.639> there 00:16:17.749 --> 00:16:17.759 align:start position:0% us to divide all the work I mean there 00:16:17.759 --> 00:16:19.590 align:start position:0% us to divide all the work I mean there is<00:16:17.880> no<00:16:18.240> big<00:16:18.560> state<00:16:19.040> there<00:16:19.120> is<00:16:19.240> no<00:16:19.360> State 00:16:19.590 --> 00:16:19.600 align:start position:0% is no big state there is no State 00:16:19.600 --> 00:16:20.990 align:start position:0% is no big state there is no State machine<00:16:19.880> that<00:16:20.000> you<00:16:20.079> need<00:16:20.240> a<00:16:20.399> big<00:16:20.560> thing<00:16:20.800> so<00:16:20.920> you 00:16:20.990 --> 00:16:21.000 align:start position:0% machine that you need a big thing so you 00:16:21.000 --> 00:16:24.150 align:start position:0% machine that you need a big thing so you can<00:16:21.199> divide<00:16:21.600> always<00:16:22.000> the<00:16:22.160> work<00:16:22.920> uh<00:16:23.279> in 00:16:24.150 --> 00:16:24.160 align:start position:0% can divide always the work uh in 00:16:24.160 --> 00:16:28.150 align:start position:0% can divide always the work uh in everything<00:16:25.199> okay<00:16:26.199> here<00:16:26.399> I<00:16:26.600> as<00:16:26.680> I<00:16:26.839> mentioned<00:16:27.600> um 00:16:28.150 --> 00:16:28.160 align:start position:0% everything okay here I as I mentioned um 00:16:28.160 --> 00:16:29.870 align:start position:0% everything okay here I as I mentioned um this<00:16:28.440> there<00:16:28.560> is<00:16:28.639> a<00:16:28.959> direct<00:16:29.199> conversion<00:16:29.759> this 00:16:29.870 --> 00:16:29.880 align:start position:0% this there is a direct conversion this 00:16:29.880 --> 00:16:31.309 align:start position:0% this there is a direct conversion this is<00:16:30.079> important<00:16:30.560> direct<00:16:30.800> conversion<00:16:31.199> that 00:16:31.309 --> 00:16:31.319 align:start position:0% is important direct conversion that 00:16:31.319 --> 00:16:33.590 align:start position:0% is important direct conversion that means<00:16:31.480> that<00:16:31.639> you<00:16:31.720> can<00:16:31.880> use<00:16:32.240> Ras<00:16:32.920> or<00:16:33.240> or<00:16:33.399> any 00:16:33.590 --> 00:16:33.600 align:start position:0% means that you can use Ras or or any 00:16:33.600 --> 00:16:35.670 align:start position:0% means that you can use Ras or or any other<00:16:33.880> Pro<00:16:34.319> or<00:16:34.480> any<00:16:34.680> other<00:16:35.240> compiling 00:16:35.670 --> 00:16:35.680 align:start position:0% other Pro or any other compiling 00:16:35.680 --> 00:16:38.150 align:start position:0% other Pro or any other compiling language<00:16:36.000> is<00:16:36.160> 64<00:16:36.639> bits<00:16:37.120> you<00:16:37.240> can<00:16:37.399> use<00:16:37.600> goang<00:16:38.040> or 00:16:38.150 --> 00:16:38.160 align:start position:0% language is 64 bits you can use goang or 00:16:38.160 --> 00:16:40.910 align:start position:0% language is 64 bits you can use goang or you<00:16:38.240> can<00:16:38.399> use<00:16:38.600> C++<00:16:39.279> or<00:16:39.360> you<00:16:39.480> can<00:16:39.639> use<00:16:40.079> uh<00:16:40.800> uh 00:16:40.910 --> 00:16:40.920 align:start position:0% you can use C++ or you can use uh uh 00:16:40.920 --> 00:16:46.030 align:start position:0% you can use C++ or you can use uh uh even<00:16:41.399> Java<00:16:41.839> I<00:16:41.920> mean<00:16:42.079> there<00:16:42.199> is<00:16:42.519> a<00:16:43.040> so<00:16:43.759> um<00:16:44.800> um<00:16:45.800> uh 00:16:46.030 --> 00:16:46.040 align:start position:0% even Java I mean there is a so um um uh 00:16:46.040 --> 00:16:49.470 align:start position:0% even Java I mean there is a so um um uh this<00:16:46.319> 5<00:16:46.560> 64<00:16:47.040> bits<00:16:47.399> is<00:16:47.720> is<00:16:47.920> quite<00:16:48.120> a<00:16:48.360> standard<00:16:49.360> uh 00:16:49.470 --> 00:16:49.480 align:start position:0% this 5 64 bits is is quite a standard uh 00:16:49.480 --> 00:16:52.509 align:start position:0% this 5 64 bits is is quite a standard uh in<00:16:49.680> there<00:16:50.199> and<00:16:50.560> as<00:16:50.680> I<00:16:50.800> told<00:16:50.959> you<00:16:51.240> there<00:16:51.360> is<00:16:51.519> one 00:16:52.509 --> 00:16:52.519 align:start position:0% in there and as I told you there is one 00:16:52.519 --> 00:16:55.790 align:start position:0% in there and as I told you there is one um<00:16:52.959> direct<00:16:53.480> conversion<00:16:54.040> one<00:16:54.240> to<00:16:54.440> one<00:16:55.040> from<00:16:55.639> uh 00:16:55.790 --> 00:16:55.800 align:start position:0% um direct conversion one to one from uh 00:16:55.800 --> 00:16:59.150 align:start position:0% um direct conversion one to one from uh risk<00:16:56.560> uh<00:16:57.040> uh<00:16:57.160> from<00:16:57.319> risk<00:16:57.600> to<00:16:57.759> thisk<00:16:58.480> we<00:16:58.680> also<00:16:58.920> Al 00:16:59.150 --> 00:16:59.160 align:start position:0% risk uh uh from risk to thisk we also Al 00:16:59.160 --> 00:17:00.749 align:start position:0% risk uh uh from risk to thisk we also Al have<00:16:59.319> a<00:16:59.560> kind<00:16:59.680> of<00:16:59.800> a<00:16:59.920> side<00:17:00.199> project<00:17:00.560> that<00:17:00.680> we 00:17:00.749 --> 00:17:00.759 align:start position:0% have a kind of a side project that we 00:17:00.759 --> 00:17:03.829 align:start position:0% have a kind of a side project that we are<00:17:01.440> um<00:17:01.839> evaluating<00:17:02.680> converting<00:17:03.160> from<00:17:03.440> wasam 00:17:03.829 --> 00:17:03.839 align:start position:0% are um evaluating converting from wasam 00:17:03.839 --> 00:17:06.150 align:start position:0% are um evaluating converting from wasam to<00:17:04.000> CIS<00:17:04.360> and<00:17:04.559> even<00:17:04.799> directly<00:17:05.120> from<00:17:05.280> LM<00:17:05.760> to<00:17:05.880> CIS 00:17:06.150 --> 00:17:06.160 align:start position:0% to CIS and even directly from LM to CIS 00:17:06.160 --> 00:17:08.029 align:start position:0% to CIS and even directly from LM to CIS this<00:17:06.240> is<00:17:06.400> particularly<00:17:06.919> possible<00:17:07.640> and<00:17:07.760> it<00:17:07.880> can 00:17:08.029 --> 00:17:08.039 align:start position:0% this is particularly possible and it can 00:17:08.039 --> 00:17:10.630 align:start position:0% this is particularly possible and it can be<00:17:08.199> quite<00:17:08.439> optimal<00:17:09.000> because<00:17:09.520> when<00:17:09.679> you<00:17:09.799> go<00:17:10.039> to 00:17:10.630 --> 00:17:10.640 align:start position:0% be quite optimal because when you go to 00:17:10.640 --> 00:17:13.470 align:start position:0% be quite optimal because when you go to intermediate<00:17:11.360> code<00:17:12.079> U<00:17:12.439> you<00:17:12.559> don't<00:17:12.760> need<00:17:13.199> these 00:17:13.470 --> 00:17:13.480 align:start position:0% intermediate code U you don't need these 00:17:13.480 --> 00:17:16.150 align:start position:0% intermediate code U you don't need these registers<00:17:14.039> and<00:17:14.240> then<00:17:14.439> you<00:17:14.600> can<00:17:15.439> uh<00:17:15.640> have 00:17:16.150 --> 00:17:16.160 align:start position:0% registers and then you can uh have 00:17:16.160 --> 00:17:18.429 align:start position:0% registers and then you can uh have better<00:17:16.520> code<00:17:17.000> in<00:17:17.160> the<00:17:17.360> processor<00:17:18.120> but<00:17:18.280> in 00:17:18.429 --> 00:17:18.439 align:start position:0% better code in the processor but in 00:17:18.439 --> 00:17:21.029 align:start position:0% better code in the processor but in general<00:17:19.400> um<00:17:19.720> the<00:17:19.919> cost<00:17:20.160> of<00:17:20.280> the 00:17:21.029 --> 00:17:21.039 align:start position:0% general um the cost of the 00:17:21.039 --> 00:17:23.150 align:start position:0% general um the cost of the proof<00:17:22.039> um<00:17:22.199> of<00:17:22.319> course<00:17:22.520> the<00:17:22.600> processor<00:17:23.000> is 00:17:23.150 --> 00:17:23.160 align:start position:0% proof um of course the processor is 00:17:23.160 --> 00:17:24.309 align:start position:0% proof um of course the processor is important<00:17:23.559> but<00:17:23.679> I<00:17:23.760> would<00:17:23.919> say<00:17:24.079> that<00:17:24.199> the 00:17:24.309 --> 00:17:24.319 align:start position:0% important but I would say that the 00:17:24.319 --> 00:17:25.829 align:start position:0% important but I would say that the operations<00:17:24.839> that<00:17:24.959> are<00:17:25.079> doing<00:17:25.319> the<00:17:25.439> processor 00:17:25.829 --> 00:17:25.839 align:start position:0% operations that are doing the processor 00:17:25.839 --> 00:17:27.470 align:start position:0% operations that are doing the processor are<00:17:26.039> even<00:17:26.280> more<00:17:26.480> important<00:17:26.839> in<00:17:26.959> general<00:17:27.280> so 00:17:27.470 --> 00:17:27.480 align:start position:0% are even more important in general so 00:17:27.480 --> 00:17:29.830 align:start position:0% are even more important in general so also<00:17:27.799> the<00:17:28.360> the<00:17:28.520> mean<00:17:28.720> the 00:17:29.830 --> 00:17:29.840 align:start position:0% also the the mean the 00:17:29.840 --> 00:17:31.470 align:start position:0% also the the mean the well<00:17:30.280> it's<00:17:30.440> not<00:17:30.640> that<00:17:30.760> you<00:17:30.880> are<00:17:31.000> optimizing 00:17:31.470 --> 00:17:31.480 align:start position:0% well it's not that you are optimizing 00:17:31.480 --> 00:17:32.710 align:start position:0% well it's not that you are optimizing the<00:17:31.640> processor<00:17:31.960> and<00:17:32.080> then<00:17:32.200> you<00:17:32.280> get<00:17:32.400> a<00:17:32.480> better 00:17:32.710 --> 00:17:32.720 align:start position:0% the processor and then you get a better 00:17:32.720 --> 00:17:34.470 align:start position:0% the processor and then you get a better proof<00:17:33.000> you<00:17:33.120> need<00:17:33.360> it's<00:17:33.640> the<00:17:33.760> whole<00:17:34.039> thing<00:17:34.360> that 00:17:34.470 --> 00:17:34.480 align:start position:0% proof you need it's the whole thing that 00:17:34.480 --> 00:17:35.470 align:start position:0% proof you need it's the whole thing that you<00:17:34.600> need<00:17:34.760> to 00:17:35.470 --> 00:17:35.480 align:start position:0% you need to 00:17:35.480 --> 00:17:39.230 align:start position:0% you need to optimize<00:17:36.600> okay<00:17:37.600> um<00:17:38.320> well<00:17:38.480> this<00:17:38.760> Advantage<00:17:39.120> we 00:17:39.230 --> 00:17:39.240 align:start position:0% optimize okay um well this Advantage we 00:17:39.240 --> 00:17:41.630 align:start position:0% optimize okay um well this Advantage we already<00:17:39.480> talk<00:17:39.840> most<00:17:40.039> of<00:17:40.200> them<00:17:41.039> okay<00:17:41.200> it's<00:17:41.400> low 00:17:41.630 --> 00:17:41.640 align:start position:0% already talk most of them okay it's low 00:17:41.640 --> 00:17:45.909 align:start position:0% already talk most of them okay it's low latency<00:17:42.320> low<00:17:42.559> latency<00:17:42.960> low<00:17:43.280> latency<00:17:44.280> and<00:17:44.919> uh 00:17:45.909 --> 00:17:45.919 align:start position:0% latency low latency low latency and uh 00:17:45.919 --> 00:17:47.430 align:start position:0% latency low latency low latency and uh yeah<00:17:46.039> we<00:17:46.160> integrate<00:17:46.559> with<00:17:46.679> the<00:17:46.799> recursor<00:17:47.320> we 00:17:47.430 --> 00:17:47.440 align:start position:0% yeah we integrate with the recursor we 00:17:47.440 --> 00:17:48.750 align:start position:0% yeah we integrate with the recursor we didn't<00:17:47.679> talk<00:17:47.840> about<00:17:48.000> the<00:17:48.120> recursor<00:17:48.520> but<00:17:48.640> the 00:17:48.750 --> 00:17:48.760 align:start position:0% didn't talk about the recursor but the 00:17:48.760 --> 00:17:50.150 align:start position:0% didn't talk about the recursor but the recursor<00:17:49.160> is<00:17:49.280> the<00:17:49.400> idea<00:17:49.640> is<00:17:49.720> that<00:17:49.880> you<00:17:49.960> can 00:17:50.150 --> 00:17:50.160 align:start position:0% recursor is the idea is that you can 00:17:50.160 --> 00:17:54.350 align:start position:0% recursor is the idea is that you can take<00:17:50.799> the<00:17:51.559> the<00:17:51.919> any<00:17:52.200> proof<00:17:52.760> and<00:17:53.000> then<00:17:53.200> you<00:17:53.360> can 00:17:54.350 --> 00:17:54.360 align:start position:0% take the the any proof and then you can 00:17:54.360 --> 00:17:58.149 align:start position:0% take the the any proof and then you can uh<00:17:55.080> build<00:17:55.840> kind<00:17:56.000> of<00:17:56.400> automatically<00:17:57.400> uh<00:17:57.799> uh<00:17:57.960> a 00:17:58.149 --> 00:17:58.159 align:start position:0% uh build kind of automatically uh uh a 00:17:58.159 --> 00:18:00.350 align:start position:0% uh build kind of automatically uh uh a proof<00:17:58.480> that<00:17:59.200> uh<00:17:59.360> Aggregates<00:17:59.799> both<00:18:00.000> proof<00:18:00.240> for 00:18:00.350 --> 00:18:00.360 align:start position:0% proof that uh Aggregates both proof for 00:18:00.360 --> 00:18:02.390 align:start position:0% proof that uh Aggregates both proof for example<00:18:00.600> if<00:18:00.720> you<00:18:00.799> are<00:18:00.919> proving<00:18:01.200> two<00:18:01.400> blocks<00:18:02.280> uh 00:18:02.390 --> 00:18:02.400 align:start position:0% example if you are proving two blocks uh 00:18:02.400 --> 00:18:05.270 align:start position:0% example if you are proving two blocks uh of<00:18:02.520> ethereum<00:18:03.000> you<00:18:03.159> can<00:18:03.679> get<00:18:03.919> a<00:18:04.440> a<00:18:04.600> proof<00:18:04.960> that 00:18:05.270 --> 00:18:05.280 align:start position:0% of ethereum you can get a a proof that 00:18:05.280 --> 00:18:07.110 align:start position:0% of ethereum you can get a a proof that actually<00:18:05.640> Aggregates<00:18:06.120> this<00:18:06.280> proof<00:18:06.640> okay<00:18:07.000> and 00:18:07.110 --> 00:18:07.120 align:start position:0% actually Aggregates this proof okay and 00:18:07.120 --> 00:18:08.510 align:start position:0% actually Aggregates this proof okay and we<00:18:07.240> have<00:18:07.360> this<00:18:07.520> recursor<00:18:07.960> that's<00:18:08.080> a<00:18:08.200> tooling 00:18:08.510 --> 00:18:08.520 align:start position:0% we have this recursor that's a tooling 00:18:08.520 --> 00:18:10.830 align:start position:0% we have this recursor that's a tooling that<00:18:08.640> allows<00:18:08.880> you<00:18:08.960> to<00:18:09.080> do<00:18:09.280> that<00:18:09.840> automatically 00:18:10.830 --> 00:18:10.840 align:start position:0% that allows you to do that automatically 00:18:10.840 --> 00:18:18.190 align:start position:0% that allows you to do that automatically uh<00:18:11.280> uh<00:18:12.280> on<00:18:12.559> this<00:18:13.559> okay<00:18:14.480> so<00:18:15.360> latency<00:18:16.320> how<00:18:16.559> we<00:18:17.440> uh 00:18:18.190 --> 00:18:18.200 align:start position:0% uh uh on this okay so latency how we uh 00:18:18.200 --> 00:18:20.510 align:start position:0% uh uh on this okay so latency how we uh push<00:18:18.520> hard<00:18:18.919> on<00:18:19.080> the<00:18:19.240> latency<00:18:20.039> actually<00:18:20.400> there 00:18:20.510 --> 00:18:20.520 align:start position:0% push hard on the latency actually there 00:18:20.520 --> 00:18:22.630 align:start position:0% push hard on the latency actually there is<00:18:20.840> four<00:18:21.120> pieces<00:18:21.720> I<00:18:21.840> have<00:18:22.000> not<00:18:22.159> much<00:18:22.360> time<00:18:22.520> but 00:18:22.630 --> 00:18:22.640 align:start position:0% is four pieces I have not much time but 00:18:22.640 --> 00:18:25.230 align:start position:0% is four pieces I have not much time but I'm<00:18:22.799> going<00:18:22.919> to<00:18:23.039> try<00:18:23.200> to<00:18:23.360> go<00:18:23.840> fast<00:18:24.840> the<00:18:25.000> first 00:18:25.230 --> 00:18:25.240 align:start position:0% I'm going to try to go fast the first 00:18:25.240 --> 00:18:28.070 align:start position:0% I'm going to try to go fast the first one<00:18:25.600> is<00:18:25.720> the<00:18:25.880> one<00:18:26.080> that<00:18:26.240> you<00:18:26.400> cannot<00:18:27.080> paralyze 00:18:28.070 --> 00:18:28.080 align:start position:0% one is the one that you cannot paralyze 00:18:28.080 --> 00:18:29.750 align:start position:0% one is the one that you cannot paralyze okay<00:18:28.200> it's<00:18:28.400> like<00:18:28.600> okay<00:18:28.919> if<00:18:29.080> I<00:18:29.200> want<00:18:29.320> to<00:18:29.440> prove<00:18:29.640> a 00:18:29.750 --> 00:18:29.760 align:start position:0% okay it's like okay if I want to prove a 00:18:29.760 --> 00:18:31.470 align:start position:0% okay it's like okay if I want to prove a computation<00:18:30.200> I<00:18:30.280> need<00:18:30.440> to<00:18:30.600> compute<00:18:31.000> that<00:18:31.159> thing 00:18:31.470 --> 00:18:31.480 align:start position:0% computation I need to compute that thing 00:18:31.480 --> 00:18:33.270 align:start position:0% computation I need to compute that thing okay<00:18:31.600> so<00:18:31.720> I<00:18:31.840> cannot<00:18:32.120> paralyze<00:18:32.919> that 00:18:33.270 --> 00:18:33.280 align:start position:0% okay so I cannot paralyze that 00:18:33.280 --> 00:18:36.830 align:start position:0% okay so I cannot paralyze that computation<00:18:34.280> very<00:18:34.520> much<00:18:34.960> okay<00:18:35.799> uh<00:18:36.159> and<00:18:36.360> also 00:18:36.830 --> 00:18:36.840 align:start position:0% computation very much okay uh and also 00:18:36.840 --> 00:18:38.710 align:start position:0% computation very much okay uh and also if<00:18:36.960> we<00:18:37.039> are<00:18:37.159> emulating<00:18:37.559> for<00:18:37.720> example<00:18:38.200> 5<00:18:38.360> I<00:18:38.480> do 00:18:38.710 --> 00:18:38.720 align:start position:0% if we are emulating for example 5 I do 00:18:38.720 --> 00:18:41.070 align:start position:0% if we are emulating for example 5 I do an<00:18:38.880> emulation<00:18:39.360> so<00:18:39.559> here<00:18:39.840> I<00:18:39.960> can<00:18:40.080> go<00:18:40.280> as<00:18:40.440> slow 00:18:41.070 --> 00:18:41.080 align:start position:0% an emulation so here I can go as slow 00:18:41.080 --> 00:18:42.750 align:start position:0% an emulation so here I can go as slow but<00:18:41.240> we<00:18:41.320> are<00:18:41.480> trying<00:18:41.760> this<00:18:41.919> to<00:18:42.080> go<00:18:42.280> as<00:18:42.440> fast<00:18:42.640> as 00:18:42.750 --> 00:18:42.760 align:start position:0% but we are trying this to go as fast as 00:18:42.760 --> 00:18:45.390 align:start position:0% but we are trying this to go as fast as we<00:18:42.880> can<00:18:43.159> currently<00:18:43.640> we<00:18:43.720> are<00:18:43.919> at<00:18:44.159> 80<00:18:44.480> mahz<00:18:45.159> so<00:18:45.320> we 00:18:45.390 --> 00:18:45.400 align:start position:0% we can currently we are at 80 mahz so we 00:18:45.400 --> 00:18:47.430 align:start position:0% we can currently we are at 80 mahz so we can<00:18:45.559> run<00:18:45.720> a<00:18:45.919> processor<00:18:46.640> running<00:18:47.120> let's<00:18:47.280> say 00:18:47.430 --> 00:18:47.440 align:start position:0% can run a processor running let's say 00:18:47.440 --> 00:18:49.029 align:start position:0% can run a processor running let's say the<00:18:47.559> minimum<00:18:47.880> Trace<00:18:48.280> that<00:18:48.400> you<00:18:48.480> need<00:18:48.679> then<00:18:48.840> to 00:18:49.029 --> 00:18:49.039 align:start position:0% the minimum Trace that you need then to 00:18:49.039 --> 00:18:50.510 align:start position:0% the minimum Trace that you need then to generate<00:18:49.400> the<00:18:49.600> winess 00:18:50.510 --> 00:18:50.520 align:start position:0% generate the winess 00:18:50.520 --> 00:18:53.430 align:start position:0% generate the winess computation<00:18:51.520> uh<00:18:51.720> we<00:18:51.840> can<00:18:52.039> go<00:18:53.039> I<00:18:53.120> think<00:18:53.280> that 00:18:53.430 --> 00:18:53.440 align:start position:0% computation uh we can go I think that 00:18:53.440 --> 00:18:54.950 align:start position:0% computation uh we can go I think that there<00:18:53.520> is<00:18:53.679> margin<00:18:54.120> here<00:18:54.280> for<00:18:54.520> at<00:18:54.640> least<00:18:54.799> one 00:18:54.950 --> 00:18:54.960 align:start position:0% there is margin here for at least one 00:18:54.960 --> 00:18:57.710 align:start position:0% there is margin here for at least one order<00:18:55.200> of<00:18:55.360> magnitude<00:18:56.480> Improvement<00:18:57.480> then<00:18:57.600> we 00:18:57.710 --> 00:18:57.720 align:start position:0% order of magnitude Improvement then we 00:18:57.720 --> 00:18:59.350 align:start position:0% order of magnitude Improvement then we have<00:18:57.840> the<00:18:57.960> winess<00:18:58.280> computation<00:18:59.000> the<00:18:59.080> windows 00:18:59.350 --> 00:18:59.360 align:start position:0% have the winess computation the windows 00:18:59.360 --> 00:19:00.630 align:start position:0% have the winess computation the windows computation<00:18:59.799> this<00:18:59.880> is<00:19:00.000> already<00:19:00.280> done<00:19:00.480> in 00:19:00.630 --> 00:19:00.640 align:start position:0% computation this is already done in 00:19:00.640 --> 00:19:03.430 align:start position:0% computation this is already done in parallel<00:19:01.280> so<00:19:01.480> this<00:19:01.600> can<00:19:01.760> be<00:19:01.960> paralyzed<00:19:02.960> Um 00:19:03.430 --> 00:19:03.440 align:start position:0% parallel so this can be paralyzed Um 00:19:03.440 --> 00:19:06.990 align:start position:0% parallel so this can be paralyzed Um this<00:19:03.600> can<00:19:03.720> be<00:19:03.880> paralyzed<00:19:05.000> um<00:19:06.000> uh<00:19:06.240> very<00:19:06.440> much 00:19:06.990 --> 00:19:07.000 align:start position:0% this can be paralyzed um uh very much 00:19:07.000 --> 00:19:09.149 align:start position:0% this can be paralyzed um uh very much and<00:19:07.559> you<00:19:07.720> can<00:19:07.919> even<00:19:08.280> start<00:19:08.559> building<00:19:09.000> this 00:19:09.149 --> 00:19:09.159 align:start position:0% and you can even start building this 00:19:09.159 --> 00:19:11.630 align:start position:0% and you can even start building this Windows<00:19:09.520> computation<00:19:10.320> while<00:19:10.720> while<00:19:11.280> you<00:19:11.400> are 00:19:11.630 --> 00:19:11.640 align:start position:0% Windows computation while while you are 00:19:11.640 --> 00:19:13.750 align:start position:0% Windows computation while while you are executing<00:19:12.240> that<00:19:12.640> also<00:19:13.280> the<00:19:13.400> windows 00:19:13.750 --> 00:19:13.760 align:start position:0% executing that also the windows 00:19:13.760 --> 00:19:16.029 align:start position:0% executing that also the windows computation<00:19:14.679> the<00:19:14.799> idea<00:19:15.000> is<00:19:15.120> that<00:19:15.240> we're<00:19:15.440> doing 00:19:16.029 --> 00:19:16.039 align:start position:0% computation the idea is that we're doing 00:19:16.039 --> 00:19:17.950 align:start position:0% computation the idea is that we're doing that<00:19:16.240> work<00:19:16.480> in<00:19:16.600> the<00:19:16.760> worker<00:19:17.240> we<00:19:17.360> are<00:19:17.520> not<00:19:17.720> have 00:19:17.950 --> 00:19:17.960 align:start position:0% that work in the worker we are not have 00:19:17.960 --> 00:19:19.750 align:start position:0% that work in the worker we are not have like<00:19:18.080> a<00:19:18.200> central<00:19:18.600> Pro<00:19:18.960> we<00:19:19.039> can<00:19:19.200> do<00:19:19.440> that<00:19:19.559> in<00:19:19.640> the 00:19:19.750 --> 00:19:19.760 align:start position:0% like a central Pro we can do that in the 00:19:19.760 --> 00:19:22.510 align:start position:0% like a central Pro we can do that in the worker<00:19:20.400> that<00:19:20.559> means<00:19:20.880> that<00:19:21.360> here<00:19:21.559> we<00:19:22.039> limit<00:19:22.400> a 00:19:22.510 --> 00:19:22.520 align:start position:0% worker that means that here we limit a 00:19:22.520 --> 00:19:25.870 align:start position:0% worker that means that here we limit a lot<00:19:23.080> the<00:19:23.840> the<00:19:24.240> the<00:19:24.360> bandwidth<00:19:24.960> so<00:19:25.159> we<00:19:25.280> have<00:19:25.520> one 00:19:25.870 --> 00:19:25.880 align:start position:0% lot the the the bandwidth so we have one 00:19:25.880 --> 00:19:27.149 align:start position:0% lot the the the bandwidth so we have one bandwidth<00:19:26.280> we<00:19:26.360> don't<00:19:26.520> have<00:19:26.720> bandwidth 00:19:27.149 --> 00:19:27.159 align:start position:0% bandwidth we don't have bandwidth 00:19:27.159 --> 00:19:29.510 align:start position:0% bandwidth we don't have bandwidth requirements<00:19:27.799> it's<00:19:27.960> minimal<00:19:28.799> the<00:19:29.159> quantity 00:19:29.510 --> 00:19:29.520 align:start position:0% requirements it's minimal the quantity 00:19:29.520 --> 00:19:32.549 align:start position:0% requirements it's minimal the quantity of<00:19:29.679> information<00:19:30.240> that<00:19:30.400> goes<00:19:30.640> from<00:19:30.919> the<00:19:31.760> uh<00:19:32.360> uh 00:19:32.549 --> 00:19:32.559 align:start position:0% of information that goes from the uh uh 00:19:32.559 --> 00:19:35.430 align:start position:0% of information that goes from the uh uh between<00:19:33.000> the<00:19:33.480> the<00:19:33.640> workers<00:19:34.360> or<00:19:34.600> a<00:19:34.760> central<00:19:35.360> I 00:19:35.430 --> 00:19:35.440 align:start position:0% between the the workers or a central I 00:19:35.440 --> 00:19:37.669 align:start position:0% between the the workers or a central I mean<00:19:35.760> the<00:19:35.880> coordinator<00:19:36.400> and<00:19:36.559> the<00:19:37.000> and<00:19:37.200> the 00:19:37.669 --> 00:19:37.679 align:start position:0% mean the coordinator and the and the 00:19:37.679 --> 00:19:40.230 align:start position:0% mean the coordinator and the and the workers<00:19:38.679> okay<00:19:39.280> then<00:19:39.400> we<00:19:39.520> have<00:19:39.679> the<00:19:39.760> Su<00:19:40.000> proof 00:19:40.230 --> 00:19:40.240 align:start position:0% workers okay then we have the Su proof 00:19:40.240 --> 00:19:42.950 align:start position:0% workers okay then we have the Su proof building<00:19:40.600> actually<00:19:40.880> this<00:19:41.000> is<00:19:41.159> the<00:19:41.919> high<00:19:42.200> work 00:19:42.950 --> 00:19:42.960 align:start position:0% building actually this is the high work 00:19:42.960 --> 00:19:44.830 align:start position:0% building actually this is the high work but<00:19:43.080> the<00:19:43.200> cool<00:19:43.400> thing<00:19:43.559> is<00:19:43.679> that<00:19:43.919> because<00:19:44.360> we 00:19:44.830 --> 00:19:44.840 align:start position:0% but the cool thing is that because we 00:19:44.840 --> 00:19:47.789 align:start position:0% but the cool thing is that because we can<00:19:45.840> we<00:19:46.039> can<00:19:46.240> we<00:19:46.360> we<00:19:46.559> have<00:19:46.799> control<00:19:47.320> of<00:19:47.600> what's 00:19:47.789 --> 00:19:47.799 align:start position:0% can we can we we have control of what's 00:19:47.799 --> 00:19:51.549 align:start position:0% can we can we we have control of what's the<00:19:48.039> sides<00:19:48.559> of<00:19:48.760> the<00:19:49.240> sub<00:19:49.640> proof<00:19:50.559> then<00:19:51.120> uh<00:19:51.400> it's 00:19:51.549 --> 00:19:51.559 align:start position:0% the sides of the sub proof then uh it's 00:19:51.559 --> 00:19:54.070 align:start position:0% the sides of the sub proof then uh it's just<00:19:51.760> a<00:19:51.880> matter<00:19:52.400> of<00:19:52.679> putting<00:19:53.000> more<00:19:53.320> subs<00:19:53.960> of 00:19:54.070 --> 00:19:54.080 align:start position:0% just a matter of putting more subs of 00:19:54.080 --> 00:19:56.110 align:start position:0% just a matter of putting more subs of course<00:19:54.280> if<00:19:54.440> they<00:19:54.559> are<00:19:54.799> cheaper<00:19:55.240> and<00:19:55.720> faster 00:19:56.110 --> 00:19:56.120 align:start position:0% course if they are cheaper and faster 00:19:56.120 --> 00:19:58.390 align:start position:0% course if they are cheaper and faster you<00:19:56.200> will<00:19:56.400> need<00:19:56.880> less<00:19:57.039> sus<00:19:57.600> if<00:19:57.760> are<00:19:58.000> slower<00:19:58.320> you 00:19:58.390 --> 00:19:58.400 align:start position:0% you will need less sus if are slower you 00:19:58.400 --> 00:20:00.789 align:start position:0% you will need less sus if are slower you will<00:19:58.760> need<00:19:59.000> more<00:19:59.720> and<00:20:00.039> that's<00:20:00.360> very<00:20:00.559> much<00:20:00.679> a 00:20:00.789 --> 00:20:00.799 align:start position:0% will need more and that's very much a 00:20:00.799 --> 00:20:02.470 align:start position:0% will need more and that's very much a matter<00:20:01.000> of<00:20:01.120> a<00:20:01.280> cost<00:20:01.600> but<00:20:01.760> not<00:20:01.880> a<00:20:02.039> matter<00:20:02.240> of<00:20:02.360> a 00:20:02.470 --> 00:20:02.480 align:start position:0% matter of a cost but not a matter of a 00:20:02.480 --> 00:20:05.110 align:start position:0% matter of a cost but not a matter of a latency<00:20:02.960> because<00:20:03.200> we<00:20:03.320> can<00:20:03.960> control<00:20:04.440> very<00:20:04.679> much 00:20:05.110 --> 00:20:05.120 align:start position:0% latency because we can control very much 00:20:05.120 --> 00:20:08.789 align:start position:0% latency because we can control very much this<00:20:05.720> uh<00:20:05.960> proving<00:20:06.799> this<00:20:07.000> proving<00:20:07.400> time<00:20:08.159> okay 00:20:08.789 --> 00:20:08.799 align:start position:0% this uh proving this proving time okay 00:20:08.799 --> 00:20:10.549 align:start position:0% this uh proving this proving time okay and<00:20:08.960> then<00:20:09.280> the<00:20:09.400> other<00:20:09.600> last<00:20:09.919> is<00:20:10.120> okay<00:20:10.320> then<00:20:10.440> we 00:20:10.549 --> 00:20:10.559 align:start position:0% and then the other last is okay then we 00:20:10.559 --> 00:20:12.669 align:start position:0% and then the other last is okay then we need<00:20:10.679> to<00:20:10.799> aggregate<00:20:11.400> okay<00:20:11.600> this<00:20:11.720> is<00:20:11.840> probably 00:20:12.669 --> 00:20:12.679 align:start position:0% need to aggregate okay this is probably 00:20:12.679 --> 00:20:15.029 align:start position:0% need to aggregate okay this is probably cently<00:20:13.039> where<00:20:13.159> we<00:20:13.280> have<00:20:13.400> the<00:20:13.559> bottleneck<00:20:14.480> but 00:20:15.029 --> 00:20:15.039 align:start position:0% cently where we have the bottleneck but 00:20:15.039 --> 00:20:17.669 align:start position:0% cently where we have the bottleneck but uh<00:20:15.919> I<00:20:16.000> mean<00:20:16.200> the<00:20:16.320> good<00:20:16.480> news<00:20:16.720> is<00:20:16.919> that<00:20:17.400> we<00:20:17.520> are 00:20:17.669 --> 00:20:17.679 align:start position:0% uh I mean the good news is that we are 00:20:17.679 --> 00:20:20.149 align:start position:0% uh I mean the good news is that we are getting<00:20:18.000> much<00:20:18.240> much<00:20:18.440> much<00:20:18.640> better<00:20:19.360> and<00:20:19.799> uh 00:20:20.149 --> 00:20:20.159 align:start position:0% getting much much much better and uh 00:20:20.159 --> 00:20:22.909 align:start position:0% getting much much much better and uh this<00:20:20.320> number<00:20:20.679> 10<00:20:20.960> seconds<00:20:21.760> we<00:20:21.960> already<00:20:22.720> get 00:20:22.909 --> 00:20:22.919 align:start position:0% this number 10 seconds we already get 00:20:22.919 --> 00:20:25.870 align:start position:0% this number 10 seconds we already get lower<00:20:23.360> to<00:20:23.559> that<00:20:23.919> here<00:20:24.640> as<00:20:24.799> mentioned<00:20:25.200> plony<00:20:25.600> 2 00:20:25.870 --> 00:20:25.880 align:start position:0% lower to that here as mentioned plony 2 00:20:25.880 --> 00:20:27.630 align:start position:0% lower to that here as mentioned plony 2 has<00:20:26.159> very<00:20:26.320> good<00:20:26.520> circuit<00:20:26.919> for<00:20:27.159> there<00:20:27.480> and 00:20:27.630 --> 00:20:27.640 align:start position:0% has very good circuit for there and 00:20:27.640 --> 00:20:30.029 align:start position:0% has very good circuit for there and optimizing<00:20:28.200> this<00:20:28.799> ation<00:20:28.960> circuit<00:20:29.400> is<00:20:29.799> uh 00:20:30.029 --> 00:20:30.039 align:start position:0% optimizing this ation circuit is uh 00:20:30.039 --> 00:20:33.230 align:start position:0% optimizing this ation circuit is uh super<00:20:30.720> is<00:20:30.880> super<00:20:31.320> important<00:20:32.320> okay<00:20:32.799> there<00:20:32.919> is<00:20:33.039> a 00:20:33.230 --> 00:20:33.240 align:start position:0% super is super important okay there is a 00:20:33.240 --> 00:20:35.070 align:start position:0% super is super important okay there is a talk<00:20:33.679> think<00:20:33.960> I<00:20:34.039> think<00:20:34.159> in<00:20:34.320> 1<00:20:34.520> hour<00:20:34.720> or<00:20:34.799> so<00:20:35.039> I 00:20:35.070 --> 00:20:35.080 align:start position:0% talk think I think in 1 hour or so I 00:20:35.080 --> 00:20:36.630 align:start position:0% talk think I think in 1 hour or so I think<00:20:35.200> it's<00:20:35.320> in<00:20:35.480> this<00:20:35.640> room<00:20:35.919> that<00:20:36.120> will<00:20:36.400> give 00:20:36.630 --> 00:20:36.640 align:start position:0% think it's in this room that will give 00:20:36.640 --> 00:20:39.029 align:start position:0% think it's in this room that will give more<00:20:36.840> details<00:20:37.320> on<00:20:37.520> this<00:20:37.960> U<00:20:38.640> uh<00:20:38.919> uh 00:20:39.029 --> 00:20:39.039 align:start position:0% more details on this U uh uh 00:20:39.039 --> 00:20:41.029 align:start position:0% more details on this U uh uh optimization<00:20:39.679> parallelization<00:20:40.679> all<00:20:40.880> the 00:20:41.029 --> 00:20:41.039 align:start position:0% optimization parallelization all the 00:20:41.039 --> 00:20:42.830 align:start position:0% optimization parallelization all the proofs<00:20:41.440> that<00:20:41.760> I<00:20:41.840> mean<00:20:42.000> all<00:20:42.159> the<00:20:42.280> proof<00:20:42.640> we<00:20:42.720> are 00:20:42.830 --> 00:20:42.840 align:start position:0% proofs that I mean all the proof we are 00:20:42.840 --> 00:20:45.350 align:start position:0% proofs that I mean all the proof we are been<00:20:43.039> running<00:20:43.480> in<00:20:43.600> a<00:20:44.320> super<00:20:44.760> computer<00:20:45.200> and 00:20:45.350 --> 00:20:45.360 align:start position:0% been running in a super computer and 00:20:45.360 --> 00:20:47.310 align:start position:0% been running in a super computer and doing<00:20:45.679> experiments<00:20:46.240> and<00:20:46.600> see<00:20:46.840> that<00:20:47.000> all<00:20:47.159> these 00:20:47.310 --> 00:20:47.320 align:start position:0% doing experiments and see that all these 00:20:47.320 --> 00:20:49.029 align:start position:0% doing experiments and see that all these numbers<00:20:47.799> get<00:20:48.120> very<00:20:48.360> very<00:20:48.520> good<00:20:48.679> and<00:20:48.840> this 00:20:49.029 --> 00:20:49.039 align:start position:0% numbers get very very good and this 00:20:49.039 --> 00:20:52.830 align:start position:0% numbers get very very good and this scales<00:20:49.760> uh<00:20:49.919> very<00:20:50.240> well<00:20:51.240> okay<00:20:51.480> future<00:20:51.919> plans 00:20:52.830 --> 00:20:52.840 align:start position:0% scales uh very well okay future plans 00:20:52.840 --> 00:20:54.149 align:start position:0% scales uh very well okay future plans lot<00:20:53.000> of<00:20:53.120> things<00:20:53.280> to<00:20:53.440> do<00:20:53.600> a<00:20:53.679> lot<00:20:53.799> of<00:20:53.880> things<00:20:54.039> in 00:20:54.149 --> 00:20:54.159 align:start position:0% lot of things to do a lot of things in 00:20:54.159 --> 00:20:57.070 align:start position:0% lot of things to do a lot of things in the<00:20:54.280> bck<00:20:54.720> a<00:20:54.799> lot<00:20:54.919> of<00:20:55.520> optimizations<00:20:56.520> that<00:20:56.919> uh 00:20:57.070 --> 00:20:57.080 align:start position:0% the bck a lot of optimizations that uh 00:20:57.080 --> 00:20:59.149 align:start position:0% the bck a lot of optimizations that uh we<00:20:57.240> want<00:20:57.440> to<00:20:57.640> implement 00:20:59.149 --> 00:20:59.159 align:start position:0% we want to implement 00:20:59.159 --> 00:21:02.029 align:start position:0% we want to implement and<00:20:59.720> uh<00:21:00.000> you<00:21:00.120> can<00:21:00.320> try<00:21:00.559> it<00:21:01.159> it's<00:21:01.360> working<00:21:01.880> right 00:21:02.029 --> 00:21:02.039 align:start position:0% and uh you can try it it's working right 00:21:02.039 --> 00:21:04.430 align:start position:0% and uh you can try it it's working right now<00:21:02.159> we<00:21:02.280> have<00:21:02.400> a<00:21:02.640> basic<00:21:03.039> thing<00:21:03.280> it's<00:21:03.640> working 00:21:04.430 --> 00:21:04.440 align:start position:0% now we have a basic thing it's working 00:21:04.440 --> 00:21:06.590 align:start position:0% now we have a basic thing it's working the<00:21:04.559> last<00:21:04.760> time<00:21:04.919> that<00:21:05.039> I<00:21:05.159> said<00:21:05.440> that<00:21:05.600> in<00:21:05.799> the<00:21:06.320> in 00:21:06.590 --> 00:21:06.600 align:start position:0% the last time that I said that in the in 00:21:06.600 --> 00:21:08.950 align:start position:0% the last time that I said that in the in the<00:21:06.960> in<00:21:07.320> in<00:21:07.440> a<00:21:07.679> in<00:21:07.840> a<00:21:08.039> scenario<00:21:08.559> somebody 00:21:08.950 --> 00:21:08.960 align:start position:0% the in in a in a scenario somebody 00:21:08.960 --> 00:21:11.870 align:start position:0% the in in a in a scenario somebody created<00:21:09.559> a<00:21:10.279> tornado<00:21:10.760> cash<00:21:10.960> and<00:21:11.080> was<00:21:11.360> inter<00:21:11.760> a 00:21:11.870 --> 00:21:11.880 align:start position:0% created a tornado cash and was inter a 00:21:11.880 --> 00:21:17.110 align:start position:0% created a tornado cash and was inter a nightmare<00:21:13.120> but<00:21:14.120> but<00:21:14.880> but<00:21:15.600> just<00:21:16.600> this<00:21:16.720> is<00:21:16.880> work 00:21:17.110 --> 00:21:17.120 align:start position:0% nightmare but but but just this is work 00:21:17.120 --> 00:21:19.350 align:start position:0% nightmare but but but just this is work in<00:21:17.320> progress<00:21:18.120> okay<00:21:18.360> so<00:21:18.760> I<00:21:18.840> would<00:21:19.000> say<00:21:19.159> at<00:21:19.279> this 00:21:19.350 --> 00:21:19.360 align:start position:0% in progress okay so I would say at this 00:21:19.360 --> 00:21:21.830 align:start position:0% in progress okay so I would say at this point<00:21:19.520> is<00:21:19.720> the<00:21:19.880> status<00:21:20.159> that<00:21:20.360> it's<00:21:20.840> working 00:21:21.830 --> 00:21:21.840 align:start position:0% point is the status that it's working 00:21:21.840 --> 00:21:24.029 align:start position:0% point is the status that it's working requires<00:21:22.279> some<00:21:22.679> refactors<00:21:23.200> of<00:21:23.360> some<00:21:23.600> pizzas 00:21:24.029 --> 00:21:24.039 align:start position:0% requires some refactors of some pizzas 00:21:24.039 --> 00:21:26.510 align:start position:0% requires some refactors of some pizzas some<00:21:24.240> cleanups<00:21:24.760> some<00:21:24.960> documentations<00:21:25.880> and<00:21:26.360> we 00:21:26.510 --> 00:21:26.520 align:start position:0% some cleanups some documentations and we 00:21:26.520 --> 00:21:28.230 align:start position:0% some cleanups some documentations and we hope<00:21:26.760> that<00:21:27.000> let's<00:21:27.200> see<00:21:27.360> if<00:21:27.520> in<00:21:27.679> the<00:21:28.000> coming 00:21:28.230 --> 00:21:28.240 align:start position:0% hope that let's see if in the coming 00:21:28.240 --> 00:21:29.470 align:start position:0% hope that let's see if in the coming weeks 00:21:29.470 --> 00:21:29.480 align:start position:0% weeks 00:21:29.480 --> 00:21:32.830 align:start position:0% weeks everything<00:21:30.480> looks<00:21:30.960> nicer<00:21:31.960> and<00:21:32.360> uh<00:21:32.480> we<00:21:32.559> want<00:21:32.720> to 00:21:32.830 --> 00:21:32.840 align:start position:0% everything looks nicer and uh we want to 00:21:32.840 --> 00:21:35.269 align:start position:0% everything looks nicer and uh we want to build<00:21:33.200> the<00:21:33.960> it<00:21:34.159> has<00:21:34.279> no<00:21:34.440> PR<00:21:34.679> compiles<00:21:35.039> I<00:21:35.120> mean 00:21:35.269 --> 00:21:35.279 align:start position:0% build the it has no PR compiles I mean 00:21:35.279 --> 00:21:36.710 align:start position:0% build the it has no PR compiles I mean know<00:21:35.400> these<00:21:35.559> estate<00:21:35.840> machines<00:21:36.120> are<00:21:36.279> limited 00:21:36.710 --> 00:21:36.720 align:start position:0% know these estate machines are limited 00:21:36.720 --> 00:21:38.630 align:start position:0% know these estate machines are limited but<00:21:36.960> you<00:21:37.080> can<00:21:37.559> build<00:21:37.880> any<00:21:38.080> program<00:21:38.440> and<00:21:38.559> you 00:21:38.630 --> 00:21:38.640 align:start position:0% but you can build any program and you 00:21:38.640 --> 00:21:40.830 align:start position:0% but you can build any program and you can<00:21:38.840> prove<00:21:39.120> any<00:21:39.320> program<00:21:39.880> for<00:21:40.159> these<00:21:40.480> uh<00:21:40.600> pre 00:21:40.830 --> 00:21:40.840 align:start position:0% can prove any program for these uh pre 00:21:40.840 --> 00:21:42.789 align:start position:0% can prove any program for these uh pre compil<00:21:41.120> so<00:21:41.279> for<00:21:41.440> these<00:21:41.679> specialized<00:21:42.440> uh<00:21:42.520> State 00:21:42.789 --> 00:21:42.799 align:start position:0% compil so for these specialized uh State 00:21:42.799 --> 00:21:46.269 align:start position:0% compil so for these specialized uh State machines<00:21:43.360> we<00:21:43.919> we<00:21:44.159> we<00:21:44.320> wait<00:21:44.840> uh<00:21:44.960> I<00:21:45.039> mean<00:21:45.919> take 00:21:46.269 --> 00:21:46.279 align:start position:0% machines we we we wait uh I mean take 00:21:46.279 --> 00:21:49.549 align:start position:0% machines we we we wait uh I mean take maybe<00:21:47.279> uh<00:21:47.400> two<00:21:47.679> three<00:21:47.880> months<00:21:48.240> still<00:21:48.559> to<00:21:48.880> to<00:21:49.159> to 00:21:49.549 --> 00:21:49.559 align:start position:0% maybe uh two three months still to to to 00:21:49.559 --> 00:21:51.950 align:start position:0% maybe uh two three months still to to to to<00:21:49.799> complete<00:21:50.799> okay<00:21:50.960> and<00:21:51.120> that's<00:21:51.360> very<00:21:51.559> much<00:21:51.760> my 00:21:51.950 --> 00:21:51.960 align:start position:0% to complete okay and that's very much my 00:21:51.960 --> 00:21:56.789 align:start position:0% to complete okay and that's very much my presentation<00:21:52.880> enjoy 00:21:56.789 --> 00:21:56.799 align:start position:0% 00:21:56.799 --> 00:21:59.350 align:start position:0% it<00:21:57.799> thank<00:21:58.000> you<00:21:58.159> very<00:21:58.320> much<00:21:58.760> let's<00:21:59.039> go<00:21:59.200> through 00:21:59.350 --> 00:21:59.360 align:start position:0% it thank you very much let's go through 00:21:59.360 --> 00:22:01.149 align:start position:0% it thank you very much let's go through some<00:21:59.600> questions<00:22:00.200> so<00:22:00.440> what<00:22:00.600> issues<00:22:00.919> did<00:22:01.080> you 00:22:01.149 --> 00:22:01.159 align:start position:0% some questions so what issues did you 00:22:01.159 --> 00:22:04.269 align:start position:0% some questions so what issues did you run<00:22:01.360> into<00:22:01.679> using<00:22:01.960> risk<00:22:02.240> V<00:22:02.559> 64<00:22:03.080> that<00:22:03.200> risk<00:22:03.440> V<00:22:03.760> 32 00:22:04.269 --> 00:22:04.279 align:start position:0% run into using risk V 64 that risk V 32 00:22:04.279 --> 00:22:06.470 align:start position:0% run into using risk V 64 that risk V 32 wouldn't 00:22:06.470 --> 00:22:06.480 align:start position:0% wouldn't 00:22:06.480 --> 00:22:09.110 align:start position:0% wouldn't have<00:22:07.480> I<00:22:07.559> mean<00:22:07.840> well<00:22:08.000> these<00:22:08.120> are<00:22:08.360> we<00:22:08.480> have<00:22:08.640> been 00:22:09.110 --> 00:22:09.120 align:start position:0% have I mean well these are we have been 00:22:09.120 --> 00:22:11.990 align:start position:0% have I mean well these are we have been checking<00:22:09.760> what's<00:22:10.039> better<00:22:10.520> what's<00:22:11.200> worst<00:22:11.760> here 00:22:11.990 --> 00:22:12.000 align:start position:0% checking what's better what's worst here 00:22:12.000 --> 00:22:15.029 align:start position:0% checking what's better what's worst here there<00:22:12.120> are<00:22:12.880> uh<00:22:13.880> I<00:22:13.960> mean<00:22:14.279> there<00:22:14.400> are<00:22:14.640> pros<00:22:14.840> and 00:22:15.029 --> 00:22:15.039 align:start position:0% there are uh I mean there are pros and 00:22:15.039 --> 00:22:16.710 align:start position:0% there are uh I mean there are pros and cons<00:22:15.400> I<00:22:15.480> would<00:22:15.640> say<00:22:15.799> that<00:22:15.960> the<00:22:16.120> big<00:22:16.400> the<00:22:16.520> big 00:22:16.710 --> 00:22:16.720 align:start position:0% cons I would say that the big the big 00:22:16.720 --> 00:22:18.430 align:start position:0% cons I would say that the big the big Pros<00:22:17.200> is<00:22:17.360> that<00:22:17.559> when<00:22:17.720> you<00:22:17.799> are<00:22:18.000> doing 00:22:18.430 --> 00:22:18.440 align:start position:0% Pros is that when you are doing 00:22:18.440 --> 00:22:20.310 align:start position:0% Pros is that when you are doing especially<00:22:19.279> when<00:22:19.400> you<00:22:19.520> are<00:22:19.600> running<00:22:19.960> rust<00:22:20.240> you 00:22:20.310 --> 00:22:20.320 align:start position:0% especially when you are running rust you 00:22:20.320 --> 00:22:21.669 align:start position:0% especially when you are running rust you are<00:22:20.400> doing<00:22:20.559> a<00:22:20.679> lot<00:22:20.799> of<00:22:20.919> M<00:22:21.159> copies<00:22:21.440> I<00:22:21.480> mean<00:22:21.600> you 00:22:21.669 --> 00:22:21.679 align:start position:0% are doing a lot of M copies I mean you 00:22:21.679 --> 00:22:23.070 align:start position:0% are doing a lot of M copies I mean you are<00:22:21.760> moving<00:22:22.039> a<00:22:22.159> lot<00:22:22.320> of<00:22:22.600> uh<00:22:22.720> memory 00:22:23.070 --> 00:22:23.080 align:start position:0% are moving a lot of uh memory 00:22:23.080 --> 00:22:25.230 align:start position:0% are moving a lot of uh memory information<00:22:23.919> and<00:22:24.039> when<00:22:24.159> you<00:22:24.279> are<00:22:24.440> using<00:22:24.760> 64 00:22:25.230 --> 00:22:25.240 align:start position:0% information and when you are using 64 00:22:25.240 --> 00:22:27.190 align:start position:0% information and when you are using 64 bits<00:22:25.520> this<00:22:25.640> is<00:22:25.799> much<00:22:26.039> much<00:22:26.240> much<00:22:26.440> more<00:22:26.720> optimal 00:22:27.190 --> 00:22:27.200 align:start position:0% bits this is much much much more optimal 00:22:27.200 --> 00:22:28.350 align:start position:0% bits this is much much much more optimal I<00:22:27.279> would<00:22:27.440> say<00:22:27.600> this<00:22:27.720> is<00:22:27.840> one<00:22:27.960> of<00:22:28.080> the<00:22:28.159> things 00:22:28.350 --> 00:22:28.360 align:start position:0% I would say this is one of the things 00:22:28.360 --> 00:22:30.750 align:start position:0% I would say this is one of the things that<00:22:28.520> that<00:22:28.640> we<00:22:28.760> saw<00:22:29.080> that<00:22:29.600> there<00:22:29.760> is<00:22:29.919> a<00:22:30.080> lot<00:22:30.279> of 00:22:30.750 --> 00:22:30.760 align:start position:0% that that we saw that there is a lot of 00:22:30.760 --> 00:22:34.590 align:start position:0% that that we saw that there is a lot of uh<00:22:30.960> copies<00:22:31.799> uh<00:22:32.320> in<00:22:32.720> uh<00:22:33.000> moving<00:22:33.559> back<00:22:33.760> and<00:22:33.919> forth 00:22:34.590 --> 00:22:34.600 align:start position:0% uh copies uh in uh moving back and forth 00:22:34.600 --> 00:22:38.909 align:start position:0% uh copies uh in uh moving back and forth uh<00:22:35.360> uh<00:22:35.520> in<00:22:35.640> a<00:22:35.840> place<00:22:36.200> and<00:22:36.480> because<00:22:37.120> uh<00:22:37.600> also<00:22:38.080> the 00:22:38.909 --> 00:22:38.919 align:start position:0% uh uh in a place and because uh also the 00:22:38.919 --> 00:22:41.909 align:start position:0% uh uh in a place and because uh also the the<00:22:39.559> the<00:22:39.679> corrent<00:22:40.240> kurrent<00:22:41.240> uh<00:22:41.679> I<00:22:41.760> mean 00:22:41.909 --> 00:22:41.919 align:start position:0% the the corrent kurrent uh I mean 00:22:41.919 --> 00:22:43.590 align:start position:0% the the corrent kurrent uh I mean current<00:22:42.200> systems<00:22:42.520> are<00:22:42.720> 64<00:22:43.159> bits<00:22:43.440> so 00:22:43.590 --> 00:22:43.600 align:start position:0% current systems are 64 bits so 00:22:43.600 --> 00:22:45.190 align:start position:0% current systems are 64 bits so everything<00:22:43.880> is<00:22:44.039> much<00:22:44.159> more<00:22:44.480> standard<00:22:45.080> for 00:22:45.190 --> 00:22:45.200 align:start position:0% everything is much more standard for 00:22:45.200 --> 00:22:46.630 align:start position:0% everything is much more standard for example<00:22:45.480> if<00:22:45.559> you<00:22:45.640> want<00:22:45.799> to<00:22:45.919> build<00:22:46.320> I<00:22:46.400> mean<00:22:46.520> if 00:22:46.630 --> 00:22:46.640 align:start position:0% example if you want to build I mean if 00:22:46.640 --> 00:22:48.909 align:start position:0% example if you want to build I mean if you<00:22:46.720> want<00:22:46.840> to<00:22:46.960> use<00:22:47.360> rust<00:22:47.760> is<00:22:47.960> 32<00:22:48.320> bits<00:22:48.559> is<00:22:48.720> okay 00:22:48.909 --> 00:22:48.919 align:start position:0% you want to use rust is 32 bits is okay 00:22:48.919 --> 00:22:50.510 align:start position:0% you want to use rust is 32 bits is okay but<00:22:49.039> if<00:22:49.120> you<00:22:49.200> want<00:22:49.320> to<00:22:49.400> do<00:22:49.679> go<00:22:49.960> for<00:22:50.120> example<00:22:50.400> you 00:22:50.510 --> 00:22:50.520 align:start position:0% but if you want to do go for example you 00:22:50.520 --> 00:22:52.190 align:start position:0% but if you want to do go for example you cannot<00:22:50.799> do<00:22:50.880> it<00:22:51.000> in<00:22:51.080> 32<00:22:51.440> bits<00:22:51.640> so<00:22:51.760> you<00:22:51.840> can<00:22:51.960> do<00:22:52.080> in 00:22:52.190 --> 00:22:52.200 align:start position:0% cannot do it in 32 bits so you can do in 00:22:52.200 --> 00:22:55.710 align:start position:0% cannot do it in 32 bits so you can do in 64<00:22:52.600> so<00:22:52.760> 64<00:22:53.200> is<00:22:53.720> also<00:22:54.039> much<00:22:54.200> more<00:22:54.520> standard<00:22:55.520> and 00:22:55.710 --> 00:22:55.720 align:start position:0% 64 so 64 is also much more standard and 00:22:55.720 --> 00:22:57.830 align:start position:0% 64 so 64 is also much more standard and but<00:22:55.919> again<00:22:56.520> the<00:22:56.960> the<00:22:57.080> different<00:22:57.360> test<00:22:57.600> that<00:22:57.720> we 00:22:57.830 --> 00:22:57.840 align:start position:0% but again the the different test that we 00:22:57.840 --> 00:22:59.909 align:start position:0% but again the the different test that we did<00:22:58.039> is<00:22:58.200> that 00:22:59.909 --> 00:22:59.919 align:start position:0% did is that 00:22:59.919 --> 00:23:04.269 align:start position:0% did is that we're<00:23:00.919> slightly<00:23:01.600> better<00:23:02.279> doing<00:23:02.679> in<00:23:02.919> 64<00:23:03.640> in<00:23:03.799> 64 00:23:04.269 --> 00:23:04.279 align:start position:0% we're slightly better doing in 64 in 64 00:23:04.279 --> 00:23:06.630 align:start position:0% we're slightly better doing in 64 in 64 bits<00:23:04.640> so<00:23:04.799> that's<00:23:04.960> why<00:23:05.120> we<00:23:05.400> stick<00:23:05.799> it<00:23:06.000> at<00:23:06.159> 64 00:23:06.630 --> 00:23:06.640 align:start position:0% bits so that's why we stick it at 64 00:23:06.640 --> 00:23:08.830 align:start position:0% bits so that's why we stick it at 64 beats<00:23:07.520> and<00:23:07.720> how<00:23:07.840> will<00:23:08.080> this<00:23:08.279> be<00:23:08.480> different 00:23:08.830 --> 00:23:08.840 align:start position:0% beats and how will this be different 00:23:08.840 --> 00:23:11.269 align:start position:0% beats and how will this be different than<00:23:09.279> sp1<00:23:10.120> risk 00:23:11.269 --> 00:23:11.279 align:start position:0% than sp1 risk 00:23:11.279 --> 00:23:15.669 align:start position:0% than sp1 risk zero<00:23:12.279> uh<00:23:13.240> well<00:23:13.559> uh<00:23:13.760> uh<00:23:14.600> we<00:23:14.720> need<00:23:15.080> we<00:23:15.279> still<00:23:15.480> need 00:23:15.669 --> 00:23:15.679 align:start position:0% zero uh well uh uh we need we still need 00:23:15.679 --> 00:23:18.630 align:start position:0% zero uh well uh uh we need we still need to<00:23:15.840> do<00:23:16.039> some<00:23:16.400> benchmarks<00:23:16.960> and<00:23:17.200> compare<00:23:18.039> but<00:23:18.440> uh 00:23:18.630 --> 00:23:18.640 align:start position:0% to do some benchmarks and compare but uh 00:23:18.640 --> 00:23:20.549 align:start position:0% to do some benchmarks and compare but uh here<00:23:18.880> the<00:23:19.039> thing<00:23:19.200> is<00:23:19.320> that<00:23:19.520> we<00:23:19.600> are<00:23:19.840> designing 00:23:20.549 --> 00:23:20.559 align:start position:0% here the thing is that we are designing 00:23:20.559 --> 00:23:22.669 align:start position:0% here the thing is that we are designing not<00:23:20.840> for<00:23:21.440> cost<00:23:21.720> I<00:23:21.799> mean<00:23:22.000> that<00:23:22.159> we<00:23:22.240> are<00:23:22.360> here<00:23:22.559> we 00:23:22.669 --> 00:23:22.679 align:start position:0% not for cost I mean that we are here we 00:23:22.679 --> 00:23:25.750 align:start position:0% not for cost I mean that we are here we are<00:23:22.919> going<00:23:23.120> to<00:23:23.279> push<00:23:24.240> uh<00:23:24.440> as<00:23:24.640> hard<00:23:24.960> as<00:23:25.159> we<00:23:25.600> as 00:23:25.750 --> 00:23:25.760 align:start position:0% are going to push uh as hard as we as 00:23:25.760 --> 00:23:29.390 align:start position:0% are going to push uh as hard as we as hard<00:23:26.039> as<00:23:26.159> we<00:23:26.320> can<00:23:27.039> in<00:23:27.799> uh<00:23:28.200> in<00:23:28.559> doing<00:23:28.760> the<00:23:28.880> speeds 00:23:29.390 --> 00:23:29.400 align:start position:0% hard as we can in uh in doing the speeds 00:23:29.400 --> 00:23:32.830 align:start position:0% hard as we can in uh in doing the speeds uh<00:23:29.760> as<00:23:29.919> fast<00:23:30.159> as<00:23:30.400> as<00:23:30.640> as<00:23:30.880> as<00:23:31.039> fast<00:23:31.320> as<00:23:31.799> uh<00:23:31.919> we<00:23:32.080> can 00:23:32.830 --> 00:23:32.840 align:start position:0% uh as fast as as as as fast as uh we can 00:23:32.840 --> 00:23:35.070 align:start position:0% uh as fast as as as as fast as uh we can so<00:23:33.240> it's<00:23:33.720> difficult<00:23:34.200> it's<00:23:34.600> difficult<00:23:34.720> to 00:23:35.070 --> 00:23:35.080 align:start position:0% so it's difficult it's difficult to 00:23:35.080 --> 00:23:37.549 align:start position:0% so it's difficult it's difficult to compare<00:23:36.080> it's<00:23:36.400> difficult<00:23:36.559> to<00:23:36.720> compare<00:23:37.159> yet 00:23:37.549 --> 00:23:37.559 align:start position:0% compare it's difficult to compare yet 00:23:37.559 --> 00:23:41.470 align:start position:0% compare it's difficult to compare yet also<00:23:37.919> we<00:23:38.080> have<00:23:38.279> some<00:23:39.120> um<00:23:39.400> this<00:23:40.400> uh<00:23:40.799> machines 00:23:41.470 --> 00:23:41.480 align:start position:0% also we have some um this uh machines 00:23:41.480 --> 00:23:43.310 align:start position:0% also we have some um this uh machines that<00:23:42.000> these<00:23:42.240> special<00:23:42.559> State<00:23:42.840> machines<00:23:43.200> that 00:23:43.310 --> 00:23:43.320 align:start position:0% that these special State machines that 00:23:43.320 --> 00:23:46.630 align:start position:0% that these special State machines that needs<00:23:43.520> to<00:23:43.679> be<00:23:44.440> finaly<00:23:45.440> but<00:23:45.919> uh<00:23:46.240> I<00:23:46.320> mean<00:23:46.520> the 00:23:46.630 --> 00:23:46.640 align:start position:0% needs to be finaly but uh I mean the 00:23:46.640 --> 00:23:48.070 align:start position:0% needs to be finaly but uh I mean the numbers<00:23:46.960> that<00:23:47.120> we<00:23:47.200> have<00:23:47.320> seen<00:23:47.520> is<00:23:47.679> that<00:23:47.799> we<00:23:47.919> are 00:23:48.070 --> 00:23:48.080 align:start position:0% numbers that we have seen is that we are 00:23:48.080 --> 00:23:51.149 align:start position:0% numbers that we have seen is that we are much<00:23:48.279> faster<00:23:48.679> especially<00:23:49.080> in<00:23:49.760> CPU<00:23:50.760> uh<00:23:50.880> we<00:23:51.000> are 00:23:51.149 --> 00:23:51.159 align:start position:0% much faster especially in CPU uh we are 00:23:51.159 --> 00:23:54.350 align:start position:0% much faster especially in CPU uh we are working<00:23:51.520> very<00:23:51.720> much<00:23:51.919> in<00:23:52.120> the<00:23:52.640> GPU<00:23:53.640> and<00:23:54.039> the<00:23:54.240> the 00:23:54.350 --> 00:23:54.360 align:start position:0% working very much in the GPU and the the 00:23:54.360 --> 00:23:56.830 align:start position:0% working very much in the GPU and the the numbers<00:23:54.679> are<00:23:54.919> quite<00:23:55.159> promising<00:23:55.799> but<00:23:56.159> again<00:23:56.760> I 00:23:56.830 --> 00:23:56.840 align:start position:0% numbers are quite promising but again I 00:23:56.840 --> 00:23:59.310 align:start position:0% numbers are quite promising but again I don't<00:23:57.000> like<00:23:57.159> to<00:23:57.320> talk<00:23:57.960> yet<00:23:58.440> about<00:23:58.640> the<00:23:58.760> numbers 00:23:59.310 --> 00:23:59.320 align:start position:0% don't like to talk yet about the numbers 00:23:59.320 --> 00:24:01.430 align:start position:0% don't like to talk yet about the numbers because<00:23:59.880> it<00:24:00.039> probably<00:24:00.360> would<00:24:00.520> not<00:24:00.679> be<00:24:00.840> fair 00:24:01.430 --> 00:24:01.440 align:start position:0% because it probably would not be fair 00:24:01.440 --> 00:24:04.669 align:start position:0% because it probably would not be fair and<00:24:01.760> and<00:24:02.000> and<00:24:02.880> uh<00:24:03.200> things<00:24:03.400> needs<00:24:03.640> to<00:24:03.760> be<00:24:03.960> more 00:24:04.669 --> 00:24:04.679 align:start position:0% and and and uh things needs to be more 00:24:04.679 --> 00:24:08.070 align:start position:0% and and and uh things needs to be more um<00:24:05.400> seted<00:24:06.279> uh<00:24:06.600> I<00:24:06.679> would<00:24:06.919> probably<00:24:07.320> both<00:24:07.520> sides 00:24:08.070 --> 00:24:08.080 align:start position:0% um seted uh I would probably both sides 00:24:08.080 --> 00:24:11.149 align:start position:0% um seted uh I would probably both sides to<00:24:08.279> start<00:24:08.559> getting<00:24:08.880> some<00:24:09.520> real<00:24:10.159> comparations 00:24:11.149 --> 00:24:11.159 align:start position:0% to start getting some real comparations 00:24:11.159 --> 00:24:12.669 align:start position:0% to start getting some real comparations from<00:24:11.320> a<00:24:11.480> developer<00:24:11.960> experience<00:24:12.360> point<00:24:12.559> of 00:24:12.669 --> 00:24:12.679 align:start position:0% from a developer experience point of 00:24:12.679 --> 00:24:14.149 align:start position:0% from a developer experience point of view<00:24:12.960> what<00:24:13.080> does<00:24:13.240> the<00:24:13.400> developer<00:24:13.760> need<00:24:13.919> to<00:24:14.039> do 00:24:14.149 --> 00:24:14.159 align:start position:0% view what does the developer need to do 00:24:14.159 --> 00:24:16.950 align:start position:0% view what does the developer need to do to<00:24:14.400> incode<00:24:14.679> the<00:24:14.799> chain<00:24:15.279> rules<00:24:15.640> into<00:24:16.000> zis<00:24:16.760> just 00:24:16.950 --> 00:24:16.960 align:start position:0% to incode the chain rules into zis just 00:24:16.960 --> 00:24:18.710 align:start position:0% to incode the chain rules into zis just write<00:24:17.159> a<00:24:17.279> Ras<00:24:17.600> code<00:24:17.840> I<00:24:17.919> mean<00:24:18.120> just<00:24:18.400> just<00:24:18.520> write 00:24:18.710 --> 00:24:18.720 align:start position:0% write a Ras code I mean just just write 00:24:18.720 --> 00:24:20.789 align:start position:0% write a Ras code I mean just just write a<00:24:18.880> program<00:24:19.279> that<00:24:19.600> do<00:24:19.840> do<00:24:20.039> the<00:24:20.200> whatever<00:24:20.480> rules 00:24:20.789 --> 00:24:20.799 align:start position:0% a program that do do the whatever rules 00:24:20.799 --> 00:24:23.909 align:start position:0% a program that do do the whatever rules that's<00:24:21.039> in<00:24:21.240> there<00:24:22.039> uh<00:24:22.640> just<00:24:23.000> a<00:24:23.120> side<00:24:23.360> note<00:24:23.679> here 00:24:23.909 --> 00:24:23.919 align:start position:0% that's in there uh just a side note here 00:24:23.919 --> 00:24:27.590 align:start position:0% that's in there uh just a side note here is<00:24:24.520> take<00:24:24.760> care<00:24:24.960> on<00:24:25.159> the<00:24:25.320> security<00:24:25.760> of<00:24:25.960> that<00:24:26.600> is 00:24:27.590 --> 00:24:27.600 align:start position:0% is take care on the security of that is 00:24:27.600 --> 00:24:29.110 align:start position:0% is take care on the security of that is um<00:24:28.200> um 00:24:29.110 --> 00:24:29.120 align:start position:0% um um 00:24:29.120 --> 00:24:30.470 align:start position:0% um um when<00:24:29.279> you<00:24:29.360> are<00:24:29.520> proving<00:24:29.919> when<00:24:30.039> you're<00:24:30.240> getting 00:24:30.470 --> 00:24:30.480 align:start position:0% when you are proving when you're getting 00:24:30.480 --> 00:24:31.950 align:start position:0% when you are proving when you're getting some<00:24:30.640> input<00:24:30.960> and<00:24:31.080> getting<00:24:31.320> some<00:24:31.480> output<00:24:31.840> the 00:24:31.950 --> 00:24:31.960 align:start position:0% some input and getting some output the 00:24:31.960 --> 00:24:35.430 align:start position:0% some input and getting some output the input<00:24:32.799> uh<00:24:33.760> you<00:24:33.919> can<00:24:34.399> you<00:24:34.520> can<00:24:34.720> still<00:24:35.039> have 00:24:35.430 --> 00:24:35.440 align:start position:0% input uh you can you can still have 00:24:35.440 --> 00:24:36.950 align:start position:0% input uh you can you can still have soundness<00:24:36.080> problems<00:24:36.520> if<00:24:36.600> you<00:24:36.679> are<00:24:36.840> not 00:24:36.950 --> 00:24:36.960 align:start position:0% soundness problems if you are not 00:24:36.960 --> 00:24:39.029 align:start position:0% soundness problems if you are not writing<00:24:37.279> the<00:24:37.480> right<00:24:37.679> way<00:24:37.960> so<00:24:38.360> you<00:24:38.480> need<00:24:38.640> to 00:24:39.029 --> 00:24:39.039 align:start position:0% writing the right way so you need to 00:24:39.039 --> 00:24:40.149 align:start position:0% writing the right way so you need to understand<00:24:39.159> a<00:24:39.240> little<00:24:39.440> bit<00:24:39.640> how<00:24:39.760> the<00:24:39.919> things 00:24:40.149 --> 00:24:40.159 align:start position:0% understand a little bit how the things 00:24:40.159 --> 00:24:41.389 align:start position:0% understand a little bit how the things work<00:24:40.520> even<00:24:40.720> if<00:24:40.840> you're<00:24:41.000> writing<00:24:41.279> a 00:24:41.389 --> 00:24:41.399 align:start position:0% work even if you're writing a 00:24:41.399 --> 00:24:43.110 align:start position:0% work even if you're writing a programming<00:24:41.840> rust<00:24:42.240> because<00:24:42.640> there<00:24:42.760> are<00:24:42.919> some 00:24:43.110 --> 00:24:43.120 align:start position:0% programming rust because there are some 00:24:43.120 --> 00:24:44.750 align:start position:0% programming rust because there are some security<00:24:43.480> issues<00:24:43.840> that<00:24:43.960> can<00:24:44.159> happen<00:24:44.480> there 00:24:44.750 --> 00:24:44.760 align:start position:0% security issues that can happen there 00:24:44.760 --> 00:24:46.230 align:start position:0% security issues that can happen there but<00:24:45.000> yeah<00:24:45.159> at<00:24:45.279> the<00:24:45.360> end<00:24:45.520> is<00:24:45.679> but<00:24:45.799> at<00:24:45.919> the<00:24:45.960> end<00:24:46.120> is 00:24:46.230 --> 00:24:46.240 align:start position:0% but yeah at the end is but at the end is 00:24:46.240 --> 00:24:48.269 align:start position:0% but yeah at the end is but at the end is writing<00:24:46.520> a<00:24:46.679> rasco<00:24:47.640> and<00:24:47.760> are<00:24:47.919> there<00:24:48.080> any 00:24:48.269 --> 00:24:48.279 align:start position:0% writing a rasco and are there any 00:24:48.279 --> 00:24:50.230 align:start position:0% writing a rasco and are there any drawbacks<00:24:48.799> that<00:24:48.960> come<00:24:49.240> with 00:24:50.230 --> 00:24:50.240 align:start position:0% drawbacks that come with 00:24:50.240 --> 00:24:53.230 align:start position:0% drawbacks that come with cisk<00:24:51.240> I<00:24:51.360> mentioned<00:24:52.240> this<00:24:52.480> security<00:24:52.880> things 00:24:53.230 --> 00:24:53.240 align:start position:0% cisk I mentioned this security things 00:24:53.240 --> 00:24:55.950 align:start position:0% cisk I mentioned this security things that<00:24:53.559> uh<00:24:53.919> but<00:24:54.080> this<00:24:54.200> is<00:24:54.440> common<00:24:54.760> in<00:24:54.919> anym<00:24:55.799> okay 00:24:55.950 --> 00:24:55.960 align:start position:0% that uh but this is common in anym okay 00:24:55.960 --> 00:24:57.750 align:start position:0% that uh but this is common in anym okay you<00:24:56.080> need<00:24:56.279> to<00:24:56.640> you<00:24:56.799> still<00:24:57.039> need<00:24:57.200> to<00:24:57.640> understand 00:24:57.750 --> 00:24:57.760 align:start position:0% you need to you still need to understand 00:24:57.760 --> 00:25:00.310 align:start position:0% you need to you still need to understand a<00:24:57.840> little<00:24:58.039> bit<00:24:58.200> what<00:24:58.600> behind<00:24:59.399> but<00:24:59.840> uh<00:25:00.039> it's 00:25:00.310 --> 00:25:00.320 align:start position:0% a little bit what behind but uh it's 00:25:00.320 --> 00:25:02.430 align:start position:0% a little bit what behind but uh it's much<00:25:00.520> more<00:25:00.799> practical<00:25:01.279> and<00:25:01.480> it's<00:25:01.760> I<00:25:01.840> mean<00:25:02.159> it's 00:25:02.430 --> 00:25:02.440 align:start position:0% much more practical and it's I mean it's 00:25:02.440 --> 00:25:04.990 align:start position:0% much more practical and it's I mean it's it's<00:25:02.600> much<00:25:02.799> easier<00:25:03.200> to<00:25:03.799> to<00:25:04.159> to<00:25:04.360> write<00:25:04.600> a<00:25:04.720> Ras 00:25:04.990 --> 00:25:05.000 align:start position:0% it's much easier to to to write a Ras 00:25:05.000 --> 00:25:06.909 align:start position:0% it's much easier to to to write a Ras code<00:25:05.240> and<00:25:05.480> out<00:25:05.720> it<00:25:05.880> on<00:25:05.960> a<00:25:06.080> Ras<00:25:06.360> code<00:25:06.600> that<00:25:06.760> not 00:25:06.909 --> 00:25:06.919 align:start position:0% code and out it on a Ras code that not 00:25:06.919 --> 00:25:09.269 align:start position:0% code and out it on a Ras code that not an<00:25:07.080> assembly<00:25:07.640> written<00:25:08.039> in<00:25:08.279> some<00:25:08.640> specific 00:25:09.269 --> 00:25:09.279 align:start position:0% an assembly written in some specific 00:25:09.279 --> 00:25:11.950 align:start position:0% an assembly written in some specific special<00:25:09.799> processor 00:25:11.950 --> 00:25:11.960 align:start position:0% special processor 00:25:11.960 --> 00:25:14.350 align:start position:0% special processor there<00:25:12.960> don't<00:25:13.240> all<00:25:13.399> these<00:25:13.600> improvements<00:25:14.120> by 00:25:14.350 --> 00:25:14.360 align:start position:0% there don't all these improvements by 00:25:14.360 --> 00:25:17.669 align:start position:0% there don't all these improvements by build<00:25:15.039> built<00:25:15.480> specific<00:25:16.039> Hardware<00:25:17.039> are<00:25:17.279> they 00:25:17.669 --> 00:25:17.679 align:start position:0% build built specific Hardware are they 00:25:17.679 --> 00:25:20.549 align:start position:0% build built specific Hardware are they better<00:25:17.960> than<00:25:18.120> making<00:25:18.520> optimizations<00:25:19.159> on<00:25:19.559> VMS 00:25:20.549 --> 00:25:20.559 align:start position:0% better than making optimizations on VMS 00:25:20.559 --> 00:25:24.149 align:start position:0% better than making optimizations on VMS I<00:25:20.640> think<00:25:20.840> that's<00:25:21.039> what<00:25:21.159> that 00:25:24.149 --> 00:25:24.159 align:start position:0% 00:25:24.159 --> 00:25:28.070 align:start position:0% says<00:25:25.159> maybe<00:25:26.120> uh<00:25:26.399> if<00:25:26.600> they<00:25:26.720> do<00:25:27.240> uh<00:25:27.360> we<00:25:27.440> will<00:25:27.960> we 00:25:28.070 --> 00:25:28.080 align:start position:0% says maybe uh if they do uh we will we 00:25:28.080 --> 00:25:31.350 align:start position:0% says maybe uh if they do uh we will we will<00:25:28.520> we<00:25:28.640> will<00:25:29.200> we<00:25:29.320> will<00:25:30.240> uh<00:25:30.520> Implement<00:25:31.120> them 00:25:31.350 --> 00:25:31.360 align:start position:0% will we will we will uh Implement them 00:25:31.360 --> 00:25:34.230 align:start position:0% will we will we will uh Implement them but<00:25:31.640> they<00:25:31.760> are<00:25:31.960> not<00:25:32.840> hard<00:25:33.440> to<00:25:33.679> build<00:25:34.039> this 00:25:34.230 --> 00:25:34.240 align:start position:0% but they are not hard to build this 00:25:34.240 --> 00:25:36.830 align:start position:0% but they are not hard to build this Hardware<00:25:34.679> I<00:25:34.720> mean<00:25:34.919> this<00:25:35.039> is<00:25:35.200> not<00:25:35.520> like<00:25:35.840> a<00:25:36.480> uh 00:25:36.830 --> 00:25:36.840 align:start position:0% Hardware I mean this is not like a uh 00:25:36.840 --> 00:25:38.549 align:start position:0% Hardware I mean this is not like a uh real<00:25:37.200> Hardware<00:25:37.600> that<00:25:37.720> you<00:25:37.799> need<00:25:37.960> to<00:25:38.120> build 00:25:38.549 --> 00:25:38.559 align:start position:0% real Hardware that you need to build 00:25:38.559 --> 00:25:41.430 align:start position:0% real Hardware that you need to build like<00:25:39.000> uh<00:25:39.760> machine<00:25:40.240> machinery<00:25:40.640> and<00:25:41.159> this<00:25:41.240> is 00:25:41.430 --> 00:25:41.440 align:start position:0% like uh machine machinery and this is 00:25:41.440 --> 00:25:43.389 align:start position:0% like uh machine machinery and this is just<00:25:41.880> a<00:25:42.000> program<00:25:42.360> and<00:25:42.640> electronics<00:25:43.159> you<00:25:43.240> need 00:25:43.389 --> 00:25:43.399 align:start position:0% just a program and electronics you need 00:25:43.399 --> 00:25:45.190 align:start position:0% just a program and electronics you need to<00:25:43.480> have<00:25:43.640> them<00:25:43.919> the<00:25:44.039> right<00:25:44.279> way<00:25:44.720> and<00:25:44.880> once<00:25:45.039> you 00:25:45.190 --> 00:25:45.200 align:start position:0% to have them the right way and once you 00:25:45.200 --> 00:25:47.230 align:start position:0% to have them the right way and once you have<00:25:45.360> it<00:25:45.480> you're<00:25:45.679> they<00:25:45.880> already<00:25:46.200> there<00:25:47.120> I 00:25:47.230 --> 00:25:47.240 align:start position:0% have it you're they already there I 00:25:47.240 --> 00:25:49.029 align:start position:0% have it you're they already there I don't<00:25:47.399> know<00:25:47.559> what<00:25:47.720> these<00:25:47.880> mean<00:25:48.399> so<00:25:48.600> maybe<00:25:48.880> you 00:25:49.029 --> 00:25:49.039 align:start position:0% don't know what these mean so maybe you 00:25:49.039 --> 00:25:50.630 align:start position:0% don't know what these mean so maybe you could<00:25:49.200> read<00:25:49.440> them<00:25:49.600> out<00:25:49.960> if<00:25:50.080> they<00:25:50.200> make<00:25:50.440> any 00:25:50.630 --> 00:25:50.640 align:start position:0% could read them out if they make any 00:25:50.640 --> 00:25:52.350 align:start position:0% could read them out if they make any sense<00:25:50.880> to 00:25:52.350 --> 00:25:52.360 align:start position:0% sense to 00:25:52.360 --> 00:25:56.549 align:start position:0% sense to you<00:25:53.360> um<00:25:54.279> yeah<00:25:54.520> this<00:25:54.720> is<00:25:55.440> um<00:25:56.200> I<00:25:56.320> we<00:25:56.399> would 00:25:56.549 --> 00:25:56.559 align:start position:0% you um yeah this is um I we would 00:25:56.559 --> 00:25:58.909 align:start position:0% you um yeah this is um I we would probably<00:25:56.799> need<00:25:57.080> the<00:25:57.320> the<00:25:57.520> context<00:25:58.559> but<00:25:58.760> this 00:25:58.909 --> 00:25:58.919 align:start position:0% probably need the the context but this 00:25:58.919 --> 00:26:01.909 align:start position:0% probably need the the context but this is<00:25:59.360> at<00:25:59.480> the<00:25:59.600> end<00:25:59.880> is<00:26:00.480> uh<00:26:01.120> is<00:26:01.279> the<00:26:01.480> position<00:26:01.760> of 00:26:01.909 --> 00:26:01.919 align:start position:0% is at the end is uh is the position of 00:26:01.919 --> 00:26:03.029 align:start position:0% is at the end is uh is the position of the<00:26:02.080> this<00:26:02.159> is<00:26:02.279> the<00:26:02.440> position<00:26:02.760> of<00:26:02.880> the 00:26:03.029 --> 00:26:03.039 align:start position:0% the this is the position of the 00:26:03.039 --> 00:26:04.789 align:start position:0% the this is the position of the registers<00:26:03.640> because<00:26:04.039> we<00:26:04.159> are<00:26:04.279> emulating 00:26:04.789 --> 00:26:04.799 align:start position:0% registers because we are emulating 00:26:04.799 --> 00:26:06.909 align:start position:0% registers because we are emulating registers<00:26:05.200> in<00:26:05.360> RIS<00:26:05.679> 5<00:26:06.039> so<00:26:06.279> we<00:26:06.399> are<00:26:06.520> setting<00:26:06.799> a 00:26:06.909 --> 00:26:06.919 align:start position:0% registers in RIS 5 so we are setting a 00:26:06.919 --> 00:26:08.750 align:start position:0% registers in RIS 5 so we are setting a specific<00:26:07.360> positions<00:26:07.720> in<00:26:07.840> the<00:26:07.960> memory<00:26:08.559> that 00:26:08.750 --> 00:26:08.760 align:start position:0% specific positions in the memory that 00:26:08.760 --> 00:26:10.510 align:start position:0% specific positions in the memory that actually<00:26:09.000> are<00:26:09.399> the<00:26:09.559> registers<00:26:10.039> and<00:26:10.200> this<00:26:10.320> is 00:26:10.510 --> 00:26:10.520 align:start position:0% actually are the registers and this is 00:26:10.520 --> 00:26:13.389 align:start position:0% actually are the registers and this is just<00:26:11.159> defining<00:26:11.799> the<00:26:12.159> this<00:26:12.279> is<00:26:12.480> just<00:26:12.679> defining 00:26:13.389 --> 00:26:13.399 align:start position:0% just defining the this is just defining 00:26:13.399 --> 00:26:15.549 align:start position:0% just defining the this is just defining the<00:26:13.840> constants<00:26:14.360> that<00:26:14.520> defines<00:26:14.960> the<00:26:15.360> the 00:26:15.549 --> 00:26:15.559 align:start position:0% the constants that defines the the 00:26:15.559 --> 00:26:17.510 align:start position:0% the constants that defines the the registers<00:26:16.200> in<00:26:16.360> in<00:26:16.440> there<00:26:16.720> there<00:26:16.919> question<00:26:17.200> in 00:26:17.510 --> 00:26:17.520 align:start position:0% registers in in there there question in 00:26:17.520 --> 00:26:20.389 align:start position:0% registers in in there there question in there<00:26:18.520> yeah<00:26:19.000> that's<00:26:19.200> very<00:26:19.440> much<00:26:19.880> the<00:26:20.240> the 00:26:20.389 --> 00:26:20.399 align:start position:0% there yeah that's very much the the 00:26:20.399 --> 00:26:22.269 align:start position:0% there yeah that's very much the the thing<00:26:20.679> I<00:26:20.720> mean<00:26:21.240> I<00:26:21.360> can't<00:26:21.559> we<00:26:21.640> can<00:26:21.799> give<00:26:21.919> you<00:26:22.039> the 00:26:22.269 --> 00:26:22.279 align:start position:0% thing I mean I can't we can give you the 00:26:22.279 --> 00:26:24.190 align:start position:0% thing I mean I can't we can give you the tail<00:26:22.559> I<00:26:22.640> mean<00:26:22.799> there<00:26:22.960> is<00:26:23.399> on<00:26:23.600> that<00:26:23.799> but<00:26:23.960> that's 00:26:24.190 --> 00:26:24.200 align:start position:0% tail I mean there is on that but that's 00:26:24.200 --> 00:26:25.990 align:start position:0% tail I mean there is on that but that's yeah<00:26:24.360> that's<00:26:24.520> the<00:26:24.640> developer<00:26:25.039> needs<00:26:25.279> to<00:26:25.480> write 00:26:25.990 --> 00:26:26.000 align:start position:0% yeah that's the developer needs to write 00:26:26.000 --> 00:26:28.710 align:start position:0% yeah that's the developer needs to write uh<00:26:26.120> P<00:26:26.399> do<00:26:26.640> not<00:26:26.840> at<00:26:26.960> all<00:26:27.799> not<00:26:27.960> at<00:26:28.080> all<00:26:28.320> unless<00:26:28.600> you 00:26:28.710 --> 00:26:28.720 align:start position:0% uh P do not at all not at all unless you 00:26:28.720 --> 00:26:31.110 align:start position:0% uh P do not at all not at all unless you want<00:26:28.919> to<00:26:29.120> build<00:26:29.440> maybe<00:26:29.760> some<00:26:30.080> specific<00:26:30.520> State 00:26:31.110 --> 00:26:31.120 align:start position:0% want to build maybe some specific State 00:26:31.120 --> 00:26:33.070 align:start position:0% want to build maybe some specific State uh<00:26:31.520> some<00:26:31.799> specific<00:26:32.279> uh<00:26:32.399> State<00:26:32.679> machines<00:26:33.000> I 00:26:33.070 --> 00:26:33.080 align:start position:0% uh some specific uh State machines I 00:26:33.080 --> 00:26:35.029 align:start position:0% uh some specific uh State machines I mean<00:26:33.240> some<00:26:33.440> co-processors<00:26:34.440> or<00:26:34.600> things<00:26:34.840> like 00:26:35.029 --> 00:26:35.039 align:start position:0% mean some co-processors or things like 00:26:35.039 --> 00:26:37.110 align:start position:0% mean some co-processors or things like that<00:26:35.240> that<00:26:35.399> then<00:26:35.559> you<00:26:35.679> can<00:26:36.360> extend<00:26:36.720> that<00:26:36.919> way 00:26:37.110 --> 00:26:37.120 align:start position:0% that that then you can extend that way 00:26:37.120 --> 00:26:39.149 align:start position:0% that that then you can extend that way but<00:26:37.279> the<00:26:37.399> idea<00:26:37.640> is<00:26:37.760> that<00:26:38.039> the<00:26:38.679> the<00:26:38.799> final 00:26:39.149 --> 00:26:39.159 align:start position:0% but the idea is that the the final 00:26:39.159 --> 00:26:40.630 align:start position:0% but the idea is that the the final process<00:26:39.520> the<00:26:39.640> final<00:26:40.000> person<00:26:40.240> that's<00:26:40.440> writing 00:26:40.630 --> 00:26:40.640 align:start position:0% process the final person that's writing 00:26:40.640 --> 00:26:42.830 align:start position:0% process the final person that's writing in<00:26:40.799> Ras<00:26:41.039> just<00:26:41.200> write<00:26:41.360> in<00:26:41.480> Ras<00:26:41.720> and<00:26:41.840> that's<00:26:42.000> it 00:26:42.830 --> 00:26:42.840 align:start position:0% in Ras just write in Ras and that's it 00:26:42.840 --> 00:26:47.880 align:start position:0% in Ras just write in Ras and that's it great<00:26:43.159> give<00:26:43.320> a<00:26:43.480> hand<00:26:44.200> uh<00:26:44.399> for<00:26:44.559> Jordy<00:26:44.880> BINA