WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:19.670 align:start position:0% [Music] 00:00:19.670 --> 00:00:19.680 align:start position:0% 00:00:19.680 --> 00:00:22.130 align:start position:0% and<00:00:20.340> today<00:00:20.580> I'm<00:00:20.820> going<00:00:21.000> to<00:00:21.119> present 00:00:22.130 --> 00:00:22.140 align:start position:0% and today I'm going to present 00:00:22.140 --> 00:00:24.830 align:start position:0% and today I'm going to present mainly<00:00:22.800> the<00:00:23.039> public<00:00:23.279> test<00:00:23.580> net<00:00:23.820> that<00:00:24.539> we 00:00:24.830 --> 00:00:24.840 align:start position:0% mainly the public test net that we 00:00:24.840 --> 00:00:28.609 align:start position:0% mainly the public test net that we publish<00:00:25.140> it<00:00:25.460> last<00:00:26.460> last<00:00:26.640> Monday 00:00:28.609 --> 00:00:28.619 align:start position:0% publish it last last Monday 00:00:28.619 --> 00:00:30.109 align:start position:0% publish it last last Monday first<00:00:29.039> of<00:00:29.160> all<00:00:29.220> I'm<00:00:29.460> going<00:00:29.580> to<00:00:29.640> explain<00:00:29.760> a 00:00:30.109 --> 00:00:30.119 align:start position:0% first of all I'm going to explain a 00:00:30.119 --> 00:00:33.170 align:start position:0% first of all I'm going to explain a little<00:00:30.180> bit<00:00:30.420> how<00:00:31.019> the<00:00:31.199> ckvm<00:00:31.859> works<00:00:32.279> and<00:00:33.000> then 00:00:33.170 --> 00:00:33.180 align:start position:0% little bit how the ckvm works and then 00:00:33.180 --> 00:00:37.690 align:start position:0% little bit how the ckvm works and then we<00:00:33.660> are<00:00:33.840> going<00:00:33.960> to<00:00:34.020> proceed<00:00:34.380> to<00:00:34.620> a<00:00:34.860> demo 00:00:37.690 --> 00:00:37.700 align:start position:0% 00:00:37.700 --> 00:00:40.610 align:start position:0% works<00:00:38.700> from<00:00:38.880> the<00:00:39.059> user<00:00:39.300> perspective 00:00:40.610 --> 00:00:40.620 align:start position:0% works from the user perspective 00:00:40.620 --> 00:00:43.310 align:start position:0% works from the user perspective well<00:00:41.280> a<00:00:41.940> user 00:00:43.310 --> 00:00:43.320 align:start position:0% well a user 00:00:43.320 --> 00:00:45.290 align:start position:0% well a user should<00:00:43.980> not<00:00:44.160> see<00:00:44.340> any<00:00:44.579> much<00:00:44.879> any<00:00:45.239> any 00:00:45.290 --> 00:00:45.300 align:start position:0% should not see any much any any 00:00:45.300 --> 00:00:47.630 align:start position:0% should not see any much any any difference<00:00:45.780> like<00:00:46.680> working<00:00:46.920> with<00:00:47.280> any<00:00:47.460> other 00:00:47.630 --> 00:00:47.640 align:start position:0% difference like working with any other 00:00:47.640 --> 00:00:49.130 align:start position:0% difference like working with any other network 00:00:49.130 --> 00:00:49.140 align:start position:0% network 00:00:49.140 --> 00:00:52.610 align:start position:0% network what<00:00:49.680> we<00:00:49.860> will<00:00:49.980> do<00:00:50.219> is<00:00:50.460> first<00:00:50.760> we<00:00:51.059> will<00:00:51.239> send<00:00:51.660> uh 00:00:52.610 --> 00:00:52.620 align:start position:0% what we will do is first we will send uh 00:00:52.620 --> 00:00:55.310 align:start position:0% what we will do is first we will send uh transactions<00:00:53.160> to<00:00:53.340> a<00:00:53.460> sequencer<00:00:54.480> a<00:00:54.719> sequencer 00:00:55.310 --> 00:00:55.320 align:start position:0% transactions to a sequencer a sequencer 00:00:55.320 --> 00:00:58.910 align:start position:0% transactions to a sequencer a sequencer we're<00:00:55.559> already<00:00:56.120> give<00:00:57.120> a<00:00:57.420> a<00:00:57.899> state 00:00:58.910 --> 00:00:58.920 align:start position:0% we're already give a a state 00:00:58.920 --> 00:01:00.529 align:start position:0% we're already give a a state that<00:00:59.399> means<00:00:59.579> that<00:00:59.699> the<00:00:59.820> state<00:00:59.940> will<00:01:00.180> be<00:01:00.360> final 00:01:00.529 --> 00:01:00.539 align:start position:0% that means that the state will be final 00:01:00.539 --> 00:01:02.689 align:start position:0% that means that the state will be final as<00:01:01.320> far<00:01:01.440> as<00:01:01.620> you<00:01:01.739> try<00:01:01.920> as<00:01:02.100> a<00:01:02.219> sequencer 00:01:02.689 --> 00:01:02.699 align:start position:0% as far as you try as a sequencer 00:01:02.699 --> 00:01:04.729 align:start position:0% as far as you try as a sequencer sequencer<00:01:03.539> the<00:01:03.899> first<00:01:04.080> version<00:01:04.260> is<00:01:04.500> going<00:01:04.680> to 00:01:04.729 --> 00:01:04.739 align:start position:0% sequencer the first version is going to 00:01:04.739 --> 00:01:06.890 align:start position:0% sequencer the first version is going to be<00:01:04.799> a<00:01:04.979> centralized<00:01:05.400> sequencer<00:01:06.000> with<00:01:06.600> the 00:01:06.890 --> 00:01:06.900 align:start position:0% be a centralized sequencer with the 00:01:06.900 --> 00:01:09.590 align:start position:0% be a centralized sequencer with the centralized<00:01:07.439> later<00:01:07.500> on<00:01:07.740> but<00:01:08.520> if<00:01:09.119> you<00:01:09.240> trust<00:01:09.479> a 00:01:09.590 --> 00:01:09.600 align:start position:0% centralized later on but if you trust a 00:01:09.600 --> 00:01:11.750 align:start position:0% centralized later on but if you trust a sequencer<00:01:10.080> this<00:01:10.439> transaction<00:01:10.799> is<00:01:11.100> final<00:01:11.280> and 00:01:11.750 --> 00:01:11.760 align:start position:0% sequencer this transaction is final and 00:01:11.760 --> 00:01:13.550 align:start position:0% sequencer this transaction is final and you<00:01:11.880> have<00:01:12.000> the<00:01:12.180> warranty<00:01:12.540> by<00:01:12.900> the<00:01:13.080> sequencer 00:01:13.550 --> 00:01:13.560 align:start position:0% you have the warranty by the sequencer 00:01:13.560 --> 00:01:14.690 align:start position:0% you have the warranty by the sequencer that<00:01:13.680> this<00:01:13.799> transaction<00:01:14.159> is<00:01:14.400> going<00:01:14.580> to<00:01:14.640> be 00:01:14.690 --> 00:01:14.700 align:start position:0% that this transaction is going to be 00:01:14.700 --> 00:01:17.570 align:start position:0% that this transaction is going to be mine<00:01:14.939> it's<00:01:15.240> going<00:01:15.479> to<00:01:15.600> be<00:01:15.780> process<00:01:16.320> it 00:01:17.570 --> 00:01:17.580 align:start position:0% mine it's going to be process it 00:01:17.580 --> 00:01:20.149 align:start position:0% mine it's going to be process it the<00:01:18.119> sequencer<00:01:18.720> will<00:01:19.200> collect<00:01:19.439> transactions 00:01:20.149 --> 00:01:20.159 align:start position:0% the sequencer will collect transactions 00:01:20.159 --> 00:01:22.010 align:start position:0% the sequencer will collect transactions and<00:01:20.759> at<00:01:20.880> some<00:01:21.060> point<00:01:21.180> we'll<00:01:21.659> send<00:01:21.900> these 00:01:22.010 --> 00:01:22.020 align:start position:0% and at some point we'll send these 00:01:22.020 --> 00:01:23.690 align:start position:0% and at some point we'll send these transactions<00:01:22.560> to<00:01:22.680> the<00:01:22.799> blockchain 00:01:23.690 --> 00:01:23.700 align:start position:0% transactions to the blockchain 00:01:23.700 --> 00:01:26.270 align:start position:0% transactions to the blockchain okay<00:01:24.060> and<00:01:24.479> and<00:01:24.720> then<00:01:25.200> at<00:01:25.560> this<00:01:25.740> point<00:01:25.860> the 00:01:26.270 --> 00:01:26.280 align:start position:0% okay and and then at this point the 00:01:26.280 --> 00:01:29.330 align:start position:0% okay and and then at this point the state<00:01:26.460> is<00:01:26.759> final<00:01:27.180> and<00:01:28.020> safe<00:01:28.380> here<00:01:29.040> we<00:01:29.220> don't 00:01:29.330 --> 00:01:29.340 align:start position:0% state is final and safe here we don't 00:01:29.340 --> 00:01:31.550 align:start position:0% state is final and safe here we don't have<00:01:29.460> any<00:01:29.640> proof<00:01:30.000> yet<00:01:30.180> it's<00:01:31.020> just<00:01:31.320> the 00:01:31.550 --> 00:01:31.560 align:start position:0% have any proof yet it's just the 00:01:31.560 --> 00:01:33.590 align:start position:0% have any proof yet it's just the transactions<00:01:32.159> are<00:01:32.460> set<00:01:32.700> and<00:01:33.180> you<00:01:33.360> have<00:01:33.479> the 00:01:33.590 --> 00:01:33.600 align:start position:0% transactions are set and you have the 00:01:33.600 --> 00:01:35.450 align:start position:0% transactions are set and you have the warranty<00:01:34.020> that<00:01:34.500> those<00:01:34.680> transactions<00:01:35.340> are 00:01:35.450 --> 00:01:35.460 align:start position:0% warranty that those transactions are 00:01:35.460 --> 00:01:38.090 align:start position:0% warranty that those transactions are going<00:01:35.640> to<00:01:35.759> be<00:01:35.820> processed<00:01:36.439> uh<00:01:37.439> in<00:01:37.740> that<00:01:37.860> order 00:01:38.090 --> 00:01:38.100 align:start position:0% going to be processed uh in that order 00:01:38.100 --> 00:01:40.370 align:start position:0% going to be processed uh in that order and<00:01:38.640> because<00:01:38.820> they<00:01:39.060> are<00:01:39.240> on<00:01:39.360> chain<00:01:39.540> you<00:01:40.259> could 00:01:40.370 --> 00:01:40.380 align:start position:0% and because they are on chain you could 00:01:40.380 --> 00:01:41.690 align:start position:0% and because they are on chain you could they<00:01:40.619> cannot<00:01:40.860> they<00:01:41.159> are<00:01:41.280> not<00:01:41.400> going<00:01:41.460> to<00:01:41.579> be 00:01:41.690 --> 00:01:41.700 align:start position:0% they cannot they are not going to be 00:01:41.700 --> 00:01:43.190 align:start position:0% they cannot they are not going to be changed<00:01:42.000> so<00:01:42.180> they<00:01:42.420> you<00:01:42.600> know<00:01:42.780> that<00:01:42.900> they<00:01:43.079> are 00:01:43.190 --> 00:01:43.200 align:start position:0% changed so they you know that they are 00:01:43.200 --> 00:01:44.749 align:start position:0% changed so they you know that they are final<00:01:43.380> and<00:01:43.860> you<00:01:44.040> don't<00:01:44.100> need<00:01:44.220> to<00:01:44.340> trust<00:01:44.640> the 00:01:44.749 --> 00:01:44.759 align:start position:0% final and you don't need to trust the 00:01:44.759 --> 00:01:46.550 align:start position:0% final and you don't need to trust the sequencer<00:01:45.119> anymore<00:01:45.360> you<00:01:46.079> know<00:01:46.200> that<00:01:46.320> these 00:01:46.550 --> 00:01:46.560 align:start position:0% sequencer anymore you know that these 00:01:46.560 --> 00:01:48.109 align:start position:0% sequencer anymore you know that these transactions<00:01:47.040> are<00:01:47.159> final 00:01:48.109 --> 00:01:48.119 align:start position:0% transactions are final 00:01:48.119 --> 00:01:50.569 align:start position:0% transactions are final and<00:01:48.659> in<00:01:48.780> background<00:01:49.079> in<00:01:49.320> parallel<00:01:49.799> it's<00:01:50.460> going 00:01:50.569 --> 00:01:50.579 align:start position:0% and in background in parallel it's going 00:01:50.579 --> 00:01:52.670 align:start position:0% and in background in parallel it's going to<00:01:50.700> be<00:01:50.759> the<00:01:50.880> proverb<00:01:51.360> actually<00:01:52.020> that's<00:01:52.439> going 00:01:52.670 --> 00:01:52.680 align:start position:0% to be the proverb actually that's going 00:01:52.680 --> 00:01:54.950 align:start position:0% to be the proverb actually that's going to<00:01:52.799> take<00:01:52.920> all<00:01:53.100> these<00:01:53.340> transactions<00:01:53.880> and<00:01:54.600> it's 00:01:54.950 --> 00:01:54.960 align:start position:0% to take all these transactions and it's 00:01:54.960 --> 00:01:56.690 align:start position:0% to take all these transactions and it's going<00:01:55.140> to<00:01:55.259> compute<00:01:55.680> it's<00:01:55.979> going<00:01:56.220> to<00:01:56.340> prove 00:01:56.690 --> 00:01:56.700 align:start position:0% going to compute it's going to prove 00:01:56.700 --> 00:01:59.630 align:start position:0% going to compute it's going to prove that<00:01:57.479> this<00:01:58.320> implicit<00:01:58.740> state<00:01:59.040> so<00:01:59.280> this<00:01:59.399> is<00:01:59.579> a 00:01:59.630 --> 00:01:59.640 align:start position:0% that this implicit state so this is a 00:01:59.640 --> 00:02:01.670 align:start position:0% that this implicit state so this is a state<00:01:59.820> that's<00:02:00.119> everybody<00:02:00.780> can<00:02:01.140> compute<00:02:01.439> but 00:02:01.670 --> 00:02:01.680 align:start position:0% state that's everybody can compute but 00:02:01.680 --> 00:02:03.170 align:start position:0% state that's everybody can compute but it's<00:02:01.860> not<00:02:01.979> it's<00:02:02.220> not<00:02:02.399> Unchained<00:02:02.820> because<00:02:02.880> you 00:02:03.170 --> 00:02:03.180 align:start position:0% it's not it's not Unchained because you 00:02:03.180 --> 00:02:04.969 align:start position:0% it's not it's not Unchained because you know<00:02:03.240> Chinese<00:02:03.540> are<00:02:03.960> only<00:02:04.140> the<00:02:04.320> transactions 00:02:04.969 --> 00:02:04.979 align:start position:0% know Chinese are only the transactions 00:02:04.979 --> 00:02:06.709 align:start position:0% know Chinese are only the transactions the<00:02:05.520> data<00:02:05.880> availability<00:02:06.240> if<00:02:06.420> you<00:02:06.479> want<00:02:06.600> the 00:02:06.709 --> 00:02:06.719 align:start position:0% the data availability if you want the 00:02:06.719 --> 00:02:07.969 align:start position:0% the data availability if you want the transactions<00:02:07.140> are<00:02:07.259> going<00:02:07.380> to<00:02:07.500> be<00:02:07.560> processed 00:02:07.969 --> 00:02:07.979 align:start position:0% transactions are going to be processed 00:02:07.979 --> 00:02:09.830 align:start position:0% transactions are going to be processed but<00:02:08.459> it's<00:02:08.580> going<00:02:08.700> to<00:02:08.759> be<00:02:08.880> converted<00:02:09.179> to<00:02:09.300> a<00:02:09.599> rare 00:02:09.830 --> 00:02:09.840 align:start position:0% but it's going to be converted to a rare 00:02:09.840 --> 00:02:12.650 align:start position:0% but it's going to be converted to a rare to<00:02:10.319> a<00:02:10.440> real<00:02:10.560> State<00:02:10.860> and<00:02:11.400> this<00:02:11.580> is<00:02:11.700> proved<00:02:12.120> by 00:02:12.650 --> 00:02:12.660 align:start position:0% to a real State and this is proved by 00:02:12.660 --> 00:02:14.270 align:start position:0% to a real State and this is proved by the<00:02:12.780> approver<00:02:13.140> this<00:02:13.739> is<00:02:13.860> the<00:02:13.980> big<00:02:14.099> difference 00:02:14.270 --> 00:02:14.280 align:start position:0% the approver this is the big difference 00:02:14.280 --> 00:02:15.890 align:start position:0% the approver this is the big difference with<00:02:14.640> the<00:02:14.819> optimistic<00:02:15.360> rollups<00:02:15.780> in 00:02:15.890 --> 00:02:15.900 align:start position:0% with the optimistic rollups in 00:02:15.900 --> 00:02:17.750 align:start position:0% with the optimistic rollups in optimistic<00:02:16.319> relapse<00:02:16.739> you<00:02:16.860> need<00:02:16.980> to<00:02:17.099> write<00:02:17.280> for 00:02:17.750 --> 00:02:17.760 align:start position:0% optimistic relapse you need to write for 00:02:17.760 --> 00:02:20.210 align:start position:0% optimistic relapse you need to write for somebody<00:02:17.879> to<00:02:18.239> to<00:02:18.540> challenge<00:02:18.840> this<00:02:19.200> state<00:02:19.500> in 00:02:20.210 --> 00:02:20.220 align:start position:0% somebody to to challenge this state in 00:02:20.220 --> 00:02:22.670 align:start position:0% somebody to to challenge this state in the<00:02:20.340> in<00:02:20.520> you<00:02:20.760> know<00:02:20.940> in<00:02:21.239> in<00:02:21.360> a<00:02:21.540> zero<00:02:21.959> app<00:02:22.200> this 00:02:22.670 --> 00:02:22.680 align:start position:0% the in you know in in a zero app this 00:02:22.680 --> 00:02:25.670 align:start position:0% the in you know in in a zero app this estate<00:02:22.920> it's<00:02:23.520> become<00:02:23.959> the<00:02:24.959> prover<00:02:25.260> just<00:02:25.440> set 00:02:25.670 --> 00:02:25.680 align:start position:0% estate it's become the prover just set 00:02:25.680 --> 00:02:27.770 align:start position:0% estate it's become the prover just set this<00:02:25.860> state<00:02:26.099> and<00:02:26.459> you<00:02:26.640> know<00:02:26.819> for<00:02:27.000> sure<00:02:27.180> that 00:02:27.770 --> 00:02:27.780 align:start position:0% this state and you know for sure that 00:02:27.780 --> 00:02:30.050 align:start position:0% this state and you know for sure that this<00:02:27.959> that<00:02:28.319> that<00:02:28.560> this<00:02:28.980> is<00:02:29.099> valid<00:02:29.459> it's<00:02:29.879> at 00:02:30.050 --> 00:02:30.060 align:start position:0% this that that this is valid it's at 00:02:30.060 --> 00:02:31.790 align:start position:0% this that that this is valid it's at this<00:02:30.180> point<00:02:30.300> where<00:02:30.720> the<00:02:30.900> user<00:02:31.140> can<00:02:31.319> withdraw 00:02:31.790 --> 00:02:31.800 align:start position:0% this point where the user can withdraw 00:02:31.800 --> 00:02:34.670 align:start position:0% this point where the user can withdraw with<00:02:32.340> router<00:02:32.700> funds<00:02:33.060> so<00:02:33.780> here<00:02:33.959> the<00:02:34.560> most 00:02:34.670 --> 00:02:34.680 align:start position:0% with router funds so here the most 00:02:34.680 --> 00:02:36.710 align:start position:0% with router funds so here the most important<00:02:35.040> piece<00:02:35.340> or<00:02:35.520> the<00:02:35.700> differential<00:02:36.120> pipe 00:02:36.710 --> 00:02:36.720 align:start position:0% important piece or the differential pipe 00:02:36.720 --> 00:02:40.250 align:start position:0% important piece or the differential pipe is<00:02:36.840> of<00:02:37.500> a<00:02:37.620> CK<00:02:37.980> Roll<00:02:38.400> Up<00:02:38.640> is<00:02:39.120> the<00:02:39.239> proverb<00:02:39.660> the 00:02:40.250 --> 00:02:40.260 align:start position:0% is of a CK Roll Up is the proverb the 00:02:40.260 --> 00:02:42.170 align:start position:0% is of a CK Roll Up is the proverb the proverb<00:02:40.560> is<00:02:40.739> a<00:02:40.800> zero<00:02:41.099> knowledge<00:02:41.400> proof<00:02:41.700> If<00:02:42.000> you 00:02:42.170 --> 00:02:42.180 align:start position:0% proverb is a zero knowledge proof If you 00:02:42.180 --> 00:02:44.930 align:start position:0% proverb is a zero knowledge proof If you want<00:02:42.239> a<00:02:42.420> validity<00:02:42.599> proof<00:02:43.019> that<00:02:43.680> uh<00:02:44.280> validates 00:02:44.930 --> 00:02:44.940 align:start position:0% want a validity proof that uh validates 00:02:44.940 --> 00:02:46.670 align:start position:0% want a validity proof that uh validates the<00:02:45.239> transactions<00:02:45.840> which<00:02:46.019> transactions 00:02:46.670 --> 00:02:46.680 align:start position:0% the transactions which transactions 00:02:46.680 --> 00:02:49.850 align:start position:0% the transactions which transactions ethereum<00:02:47.220> transactions<00:02:48.180> is<00:02:48.720> taking<00:02:49.080> a<00:02:49.680> state 00:02:49.850 --> 00:02:49.860 align:start position:0% ethereum transactions is taking a state 00:02:49.860 --> 00:02:51.770 align:start position:0% ethereum transactions is taking a state is<00:02:50.160> taking<00:02:50.459> a<00:02:50.640> set<00:02:50.700> of<00:02:50.819> infinity<00:02:51.000> transactions 00:02:51.770 --> 00:02:51.780 align:start position:0% is taking a set of infinity transactions 00:02:51.780 --> 00:02:53.390 align:start position:0% is taking a set of infinity transactions and<00:02:52.140> is<00:02:52.260> Computing<00:02:52.680> in<00:02:52.800> your<00:02:52.920> state<00:02:53.160> and 00:02:53.390 --> 00:02:53.400 align:start position:0% and is Computing in your state and 00:02:53.400 --> 00:02:56.150 align:start position:0% and is Computing in your state and validating<00:02:53.819> that<00:02:54.180> this<00:02:54.420> state<00:02:54.660> is<00:02:55.140> valid<00:02:55.560> so 00:02:56.150 --> 00:02:56.160 align:start position:0% validating that this state is valid so 00:02:56.160 --> 00:02:56.990 align:start position:0% validating that this state is valid so how 00:02:56.990 --> 00:02:57.000 align:start position:0% how 00:02:57.000 --> 00:02:58.970 align:start position:0% how how<00:02:57.420> the<00:02:57.660> program<00:02:57.780> is<00:02:58.140> built<00:02:58.500> so<00:02:58.739> what's 00:02:58.970 --> 00:02:58.980 align:start position:0% how the program is built so what's 00:02:58.980 --> 00:03:00.890 align:start position:0% how the program is built so what's what's<00:02:59.220> inside<00:02:59.519> the<00:02:59.819> approver<00:03:00.120> well<00:03:00.720> the 00:03:00.890 --> 00:03:00.900 align:start position:0% what's inside the approver well the 00:03:00.900 --> 00:03:03.550 align:start position:0% what's inside the approver well the approver<00:03:01.200> is<00:03:01.440> a<00:03:01.860> set<00:03:02.040> of<00:03:02.220> Technologies<00:03:02.700> but 00:03:03.550 --> 00:03:03.560 align:start position:0% approver is a set of Technologies but 00:03:03.560 --> 00:03:06.770 align:start position:0% approver is a set of Technologies but the<00:03:04.560> way<00:03:04.680> we<00:03:04.800> build<00:03:04.980> this<00:03:05.160> we<00:03:05.459> have<00:03:05.640> a<00:03:05.879> circuit 00:03:06.770 --> 00:03:06.780 align:start position:0% the way we build this we have a circuit 00:03:06.780 --> 00:03:10.250 align:start position:0% the way we build this we have a circuit with<00:03:07.560> a<00:03:07.800> traditional<00:03:08.280> circuit<00:03:08.879> written<00:03:09.720> in<00:03:10.019> in 00:03:10.250 --> 00:03:10.260 align:start position:0% with a traditional circuit written in in 00:03:10.260 --> 00:03:12.290 align:start position:0% with a traditional circuit written in in pill<00:03:10.800> specific<00:03:11.340> language<00:03:11.519> we<00:03:11.819> built<00:03:12.120> for<00:03:12.180> the 00:03:12.290 --> 00:03:12.300 align:start position:0% pill specific language we built for the 00:03:12.300 --> 00:03:14.809 align:start position:0% pill specific language we built for the ckvm<00:03:12.959> that's<00:03:13.440> mainly<00:03:13.739> a<00:03:13.860> processor<00:03:14.280> it's<00:03:14.640> a 00:03:14.809 --> 00:03:14.819 align:start position:0% ckvm that's mainly a processor it's a 00:03:14.819 --> 00:03:18.050 align:start position:0% ckvm that's mainly a processor it's a generic<00:03:15.180> processor<00:03:15.659> it's<00:03:16.319> generic<00:03:16.800> it's<00:03:17.159> with 00:03:18.050 --> 00:03:18.060 align:start position:0% generic processor it's generic it's with 00:03:18.060 --> 00:03:21.110 align:start position:0% generic processor it's generic it's with some<00:03:18.480> specifies<00:03:19.260> that<00:03:19.500> but<00:03:19.739> it's<00:03:20.220> a<00:03:20.400> processor 00:03:21.110 --> 00:03:21.120 align:start position:0% some specifies that but it's a processor 00:03:21.120 --> 00:03:24.350 align:start position:0% some specifies that but it's a processor that's<00:03:21.840> built<00:03:22.440> with<00:03:22.739> this<00:03:22.860> zero<00:03:23.220> knowledge<00:03:23.519> uh 00:03:24.350 --> 00:03:24.360 align:start position:0% that's built with this zero knowledge uh 00:03:24.360 --> 00:03:26.869 align:start position:0% that's built with this zero knowledge uh technology<00:03:24.780> and<00:03:25.620> on<00:03:25.920> top<00:03:26.099> of<00:03:26.220> this<00:03:26.400> processor 00:03:26.869 --> 00:03:26.879 align:start position:0% technology and on top of this processor 00:03:26.879 --> 00:03:29.030 align:start position:0% technology and on top of this processor we<00:03:27.300> are<00:03:27.420> running<00:03:27.599> a<00:03:27.840> program<00:03:28.019> we<00:03:28.620> call<00:03:28.739> it<00:03:28.920> a 00:03:29.030 --> 00:03:29.040 align:start position:0% we are running a program we call it a 00:03:29.040 --> 00:03:32.990 align:start position:0% we are running a program we call it a ROM<00:03:29.220> okay<00:03:29.940> that<00:03:30.420> actually<00:03:30.659> is<00:03:31.080> an<00:03:31.920> ethereum<00:03:32.400> it 00:03:32.990 --> 00:03:33.000 align:start position:0% ROM okay that actually is an ethereum it 00:03:33.000 --> 00:03:34.670 align:start position:0% ROM okay that actually is an ethereum it emulates<00:03:33.420> ethereum<00:03:33.840> it<00:03:34.200> actually<00:03:34.319> this 00:03:34.670 --> 00:03:34.680 align:start position:0% emulates ethereum it actually this 00:03:34.680 --> 00:03:36.710 align:start position:0% emulates ethereum it actually this program<00:03:34.980> just<00:03:35.580> is<00:03:35.760> the<00:03:36.000> is<00:03:36.239> this<00:03:36.420> problem<00:03:36.540> is 00:03:36.710 --> 00:03:36.720 align:start position:0% program just is the is this problem is 00:03:36.720 --> 00:03:38.210 align:start position:0% program just is the is this problem is the<00:03:36.900> one<00:03:37.019> that<00:03:37.200> is<00:03:37.319> actually<00:03:37.560> taking<00:03:37.860> the 00:03:38.210 --> 00:03:38.220 align:start position:0% the one that is actually taking the 00:03:38.220 --> 00:03:40.309 align:start position:0% the one that is actually taking the transactions<00:03:38.760> uh<00:03:39.720> analyzing<00:03:40.140> the 00:03:40.309 --> 00:03:40.319 align:start position:0% transactions uh analyzing the 00:03:40.319 --> 00:03:41.869 align:start position:0% transactions uh analyzing the transactions<00:03:40.799> checking<00:03:41.099> that<00:03:41.220> the<00:03:41.340> signatory 00:03:41.869 --> 00:03:41.879 align:start position:0% transactions checking that the signatory 00:03:41.879 --> 00:03:43.670 align:start position:0% transactions checking that the signatory is<00:03:41.940> valid<00:03:42.299> discounting<00:03:43.140> the<00:03:43.260> balances 00:03:43.670 --> 00:03:43.680 align:start position:0% is valid discounting the balances 00:03:43.680 --> 00:03:45.710 align:start position:0% is valid discounting the balances checking<00:03:44.459> the<00:03:44.580> fees<00:03:44.879> deploying<00:03:45.420> the<00:03:45.540> smart 00:03:45.710 --> 00:03:45.720 align:start position:0% checking the fees deploying the smart 00:03:45.720 --> 00:03:47.630 align:start position:0% checking the fees deploying the smart contracts<00:03:46.200> executing<00:03:46.920> the<00:03:47.040> smart<00:03:47.159> contracts 00:03:47.630 --> 00:03:47.640 align:start position:0% contracts executing the smart contracts 00:03:47.640 --> 00:03:49.970 align:start position:0% contracts executing the smart contracts and<00:03:48.060> doing<00:03:48.239> exactly<00:03:48.840> the<00:03:49.200> same<00:03:49.319> that<00:03:49.799> does 00:03:49.970 --> 00:03:49.980 align:start position:0% and doing exactly the same that does 00:03:49.980 --> 00:03:51.890 align:start position:0% and doing exactly the same that does gaffer<00:03:50.459> that<00:03:50.640> doesn't<00:03:50.819> mean<00:03:51.239> ethereum<00:03:51.599> node 00:03:51.890 --> 00:03:51.900 align:start position:0% gaffer that doesn't mean ethereum node 00:03:51.900 --> 00:03:55.550 align:start position:0% gaffer that doesn't mean ethereum node just<00:03:53.000> processing<00:03:54.000> this<00:03:54.540> processing<00:03:55.260> these 00:03:55.550 --> 00:03:55.560 align:start position:0% just processing this processing these 00:03:55.560 --> 00:03:57.890 align:start position:0% just processing this processing these transactions<00:03:56.459> all<00:03:56.940> this<00:03:57.120> goes<00:03:57.420> to<00:03:57.480> approver 00:03:57.890 --> 00:03:57.900 align:start position:0% transactions all this goes to approver 00:03:57.900 --> 00:04:00.410 align:start position:0% transactions all this goes to approver and<00:03:58.799> it's<00:03:59.159> and<00:03:59.400> this<00:03:59.580> Brewery<00:03:59.940> is<00:04:00.180> the<00:04:00.299> one 00:04:00.410 --> 00:04:00.420 align:start position:0% and it's and this Brewery is the one 00:04:00.420 --> 00:04:01.449 align:start position:0% and it's and this Brewery is the one that's 00:04:01.449 --> 00:04:01.459 align:start position:0% that's 00:04:01.459 --> 00:04:04.789 align:start position:0% that's verified<00:04:02.459> on<00:04:03.360> chain 00:04:04.789 --> 00:04:04.799 align:start position:0% verified on chain 00:04:04.799 --> 00:04:08.210 align:start position:0% verified on chain if<00:04:05.159> you<00:04:05.220> zoom<00:04:05.640> in<00:04:05.760> in<00:04:06.360> the<00:04:06.599> processor<00:04:07.440> well<00:04:07.980> we 00:04:08.210 --> 00:04:08.220 align:start position:0% if you zoom in in the processor well we 00:04:08.220 --> 00:04:11.990 align:start position:0% if you zoom in in the processor well we have<00:04:08.340> a<00:04:08.640> mainly<00:04:09.480> a<00:04:09.659> processor<00:04:10.200> is<00:04:10.920> this<00:04:11.220> ZK 00:04:11.990 --> 00:04:12.000 align:start position:0% have a mainly a processor is this ZK 00:04:12.000 --> 00:04:15.229 align:start position:0% have a mainly a processor is this ZK processor<00:04:12.599> it's<00:04:13.140> a<00:04:13.439> all<00:04:13.799> these<00:04:14.159> processor<00:04:15.000> is 00:04:15.229 --> 00:04:15.239 align:start position:0% processor it's a all these processor is 00:04:15.239 --> 00:04:20.030 align:start position:0% processor it's a all these processor is very<00:04:15.480> tailor<00:04:15.900> made<00:04:16.139> for<00:04:17.239> uh<00:04:18.239> the<00:04:18.660> ckbm<00:04:19.320> so<00:04:19.799> it's 00:04:20.030 --> 00:04:20.040 align:start position:0% very tailor made for uh the ckbm so it's 00:04:20.040 --> 00:04:21.890 align:start position:0% very tailor made for uh the ckbm so it's not<00:04:20.220> like<00:04:20.579> a<00:04:20.760> very<00:04:20.940> generic<00:04:21.299> processor<00:04:21.720> it's 00:04:21.890 --> 00:04:21.900 align:start position:0% not like a very generic processor it's 00:04:21.900 --> 00:04:23.870 align:start position:0% not like a very generic processor it's this<00:04:22.139> part<00:04:22.440> that's<00:04:22.560> generic<00:04:23.040> but<00:04:23.460> there<00:04:23.699> are 00:04:23.870 --> 00:04:23.880 align:start position:0% this part that's generic but there are 00:04:23.880 --> 00:04:28.249 align:start position:0% this part that's generic but there are specific<00:04:24.300> pieces<00:04:24.780> that<00:04:25.500> are<00:04:25.880> made<00:04:27.259> explicitly 00:04:28.249 --> 00:04:28.259 align:start position:0% specific pieces that are made explicitly 00:04:28.259 --> 00:04:32.990 align:start position:0% specific pieces that are made explicitly to<00:04:29.100> be<00:04:29.639> optimal<00:04:30.180> for<00:04:30.600> running<00:04:30.840> the<00:04:32.000> evm 00:04:32.990 --> 00:04:33.000 align:start position:0% to be optimal for running the evm 00:04:33.000 --> 00:04:35.570 align:start position:0% to be optimal for running the evm program<00:04:33.240> the<00:04:33.479> ckvm<00:04:34.139> program<00:04:34.320> okay<00:04:34.979> this 00:04:35.570 --> 00:04:35.580 align:start position:0% program the ckvm program okay this 00:04:35.580 --> 00:04:37.969 align:start position:0% program the ckvm program okay this processor<00:04:36.000> has<00:04:36.180> a<00:04:36.360> ram<00:04:36.479> has<00:04:37.139> a<00:04:37.380> ROM<00:04:37.500> which 00:04:37.969 --> 00:04:37.979 align:start position:0% processor has a ram has a ROM which 00:04:37.979 --> 00:04:39.950 align:start position:0% processor has a ram has a ROM which contains<00:04:38.340> this<00:04:38.520> program<00:04:38.759> that's<00:04:39.419> executed 00:04:39.950 --> 00:04:39.960 align:start position:0% contains this program that's executed 00:04:39.960 --> 00:04:42.950 align:start position:0% contains this program that's executed contains<00:04:40.919> the<00:04:40.979> storage<00:04:41.160> because<00:04:41.880> the<00:04:42.120> ABM<00:04:42.540> you 00:04:42.950 --> 00:04:42.960 align:start position:0% contains the storage because the ABM you 00:04:42.960 --> 00:04:45.590 align:start position:0% contains the storage because the ABM you should<00:04:43.080> be<00:04:43.199> able<00:04:43.380> to<00:04:43.560> store<00:04:44.220> values<00:04:44.759> and<00:04:45.120> and 00:04:45.590 --> 00:04:45.600 align:start position:0% should be able to store values and and 00:04:45.600 --> 00:04:47.749 align:start position:0% should be able to store values and and and<00:04:45.720> get<00:04:46.380> the<00:04:46.620> values 00:04:47.749 --> 00:04:47.759 align:start position:0% and get the values 00:04:47.759 --> 00:04:50.450 align:start position:0% and get the values it<00:04:48.300> have<00:04:48.600> also<00:04:49.020> uh 00:04:50.450 --> 00:04:50.460 align:start position:0% it have also uh 00:04:50.460 --> 00:04:53.270 align:start position:0% it have also uh kind<00:04:50.940> of<00:04:51.060> a<00:04:51.180> suit<00:04:51.360> processor<00:04:51.960> that<00:04:52.680> handles 00:04:53.270 --> 00:04:53.280 align:start position:0% kind of a suit processor that handles 00:04:53.280 --> 00:04:54.950 align:start position:0% kind of a suit processor that handles all<00:04:53.520> the<00:04:53.639> binaries<00:04:54.120> operations<00:04:54.540> here 00:04:54.950 --> 00:04:54.960 align:start position:0% all the binaries operations here 00:04:54.960 --> 00:04:58.490 align:start position:0% all the binaries operations here includes<00:04:55.380> addition<00:04:55.919> subtraction<00:04:57.020> and<00:04:58.020> torque 00:04:58.490 --> 00:04:58.500 align:start position:0% includes addition subtraction and torque 00:04:58.500 --> 00:05:01.730 align:start position:0% includes addition subtraction and torque xores<00:04:59.280> and<00:04:59.580> so<00:04:59.759> on<00:04:59.940> has<00:05:00.660> a<00:05:00.960> model<00:05:01.199> that's<00:05:01.560> for 00:05:01.730 --> 00:05:01.740 align:start position:0% xores and so on has a model that's for 00:05:01.740 --> 00:05:04.909 align:start position:0% xores and so on has a model that's for identic<00:05:02.460> this<00:05:03.060> is<00:05:03.240> you<00:05:03.780> know<00:05:03.840> in<00:05:04.020> the<00:05:04.139> in<00:05:04.740> the 00:05:04.909 --> 00:05:04.919 align:start position:0% identic this is you know in the in the 00:05:04.919 --> 00:05:08.450 align:start position:0% identic this is you know in the in the in<00:05:05.460> the<00:05:05.639> IBM<00:05:06.060> it<00:05:06.600> works<00:05:06.840> in<00:05:06.900> 256<00:05:07.560> bits<00:05:07.979> so<00:05:08.340> this 00:05:08.450 --> 00:05:08.460 align:start position:0% in the IBM it works in 256 bits so this 00:05:08.460 --> 00:05:10.730 align:start position:0% in the IBM it works in 256 bits so this arithmetic<00:05:09.180> circuit<00:05:09.840> actually<00:05:10.139> does<00:05:10.440> all 00:05:10.730 --> 00:05:10.740 align:start position:0% arithmetic circuit actually does all 00:05:10.740 --> 00:05:14.210 align:start position:0% arithmetic circuit actually does all these<00:05:10.979> operations<00:05:11.280> in<00:05:11.520> the<00:05:11.639> 256<00:05:12.479> 56<00:05:13.199> bits<00:05:13.620> okay 00:05:14.210 --> 00:05:14.220 align:start position:0% these operations in the 256 56 bits okay 00:05:14.220 --> 00:05:18.350 align:start position:0% these operations in the 256 56 bits okay and<00:05:14.880> then<00:05:15.060> has<00:05:15.540> uh<00:05:15.840> the<00:05:16.139> hashing<00:05:16.639> for<00:05:17.639> ketchups 00:05:18.350 --> 00:05:18.360 align:start position:0% and then has uh the hashing for ketchups 00:05:18.360 --> 00:05:21.530 align:start position:0% and then has uh the hashing for ketchups and<00:05:18.860> other<00:05:19.860> hashes<00:05:20.340> that<00:05:20.880> are<00:05:21.060> also<00:05:21.300> inside 00:05:21.530 --> 00:05:21.540 align:start position:0% and other hashes that are also inside 00:05:21.540 --> 00:05:23.749 align:start position:0% and other hashes that are also inside the<00:05:21.960> inside<00:05:22.560> the<00:05:22.800> process<00:05:23.039> inside<00:05:23.340> this 00:05:23.749 --> 00:05:23.759 align:start position:0% the inside the process inside this 00:05:23.759 --> 00:05:25.070 align:start position:0% the inside the process inside this processor 00:05:25.070 --> 00:05:25.080 align:start position:0% processor 00:05:25.080 --> 00:05:27.469 align:start position:0% processor on<00:05:25.620> top<00:05:25.800> of<00:05:25.919> this<00:05:26.039> processor<00:05:26.580> there<00:05:27.120> is<00:05:27.360> this 00:05:27.469 --> 00:05:27.479 align:start position:0% on top of this processor there is this 00:05:27.479 --> 00:05:29.990 align:start position:0% on top of this processor there is this ROM<00:05:27.720> okay<00:05:28.199> this<00:05:28.500> ROM<00:05:28.620> is<00:05:28.860> written<00:05:29.220> in<00:05:29.460> assembly 00:05:29.990 --> 00:05:30.000 align:start position:0% ROM okay this ROM is written in assembly 00:05:30.000 --> 00:05:32.450 align:start position:0% ROM okay this ROM is written in assembly it's<00:05:30.660> a<00:05:30.840> specific<00:05:31.139> assembly<00:05:31.620> for<00:05:32.160> this 00:05:32.450 --> 00:05:32.460 align:start position:0% it's a specific assembly for this 00:05:32.460 --> 00:05:35.629 align:start position:0% it's a specific assembly for this processor<00:05:33.419> and<00:05:33.900> here<00:05:34.080> is<00:05:34.320> what<00:05:34.500> contains<00:05:35.039> that 00:05:35.629 --> 00:05:35.639 align:start position:0% processor and here is what contains that 00:05:35.639 --> 00:05:37.070 align:start position:0% processor and here is what contains that this<00:05:35.759> here<00:05:36.060> contains<00:05:36.419> all<00:05:36.600> the<00:05:36.780> logic 00:05:37.070 --> 00:05:37.080 align:start position:0% this here contains all the logic 00:05:37.080 --> 00:05:39.050 align:start position:0% this here contains all the logic actually<00:05:37.259> what<00:05:37.800> contains<00:05:38.160> all<00:05:38.280> the<00:05:38.520> all<00:05:38.880> the 00:05:39.050 --> 00:05:39.060 align:start position:0% actually what contains all the all the 00:05:39.060 --> 00:05:41.810 align:start position:0% actually what contains all the all the sodium<00:05:39.360> logic<00:05:39.780> that<00:05:40.380> when<00:05:40.860> we<00:05:41.039> are<00:05:41.460> processing 00:05:41.810 --> 00:05:41.820 align:start position:0% sodium logic that when we are processing 00:05:41.820 --> 00:05:43.969 align:start position:0% sodium logic that when we are processing here<00:05:42.060> here<00:05:42.600> I<00:05:42.840> want<00:05:42.960> to<00:05:43.080> show<00:05:43.199> you<00:05:43.380> just<00:05:43.680> a 00:05:43.969 --> 00:05:43.979 align:start position:0% here here I want to show you just a 00:05:43.979 --> 00:05:46.129 align:start position:0% here here I want to show you just a snippet<00:05:44.520> of<00:05:44.639> code<00:05:44.880> of<00:05:45.419> how<00:05:45.600> this<00:05:45.780> looks<00:05:46.020> like 00:05:46.129 --> 00:05:46.139 align:start position:0% snippet of code of how this looks like 00:05:46.139 --> 00:05:49.670 align:start position:0% snippet of code of how this looks like this<00:05:46.500> is<00:05:46.620> just<00:05:46.860> for<00:05:47.100> example<00:05:47.400> the<00:05:47.759> the<00:05:48.500> one<00:05:49.500> and 00:05:49.670 --> 00:05:49.680 align:start position:0% this is just for example the the one and 00:05:49.680 --> 00:05:51.650 align:start position:0% this is just for example the the one and two<00:05:49.800> but<00:05:50.280> here<00:05:50.400> we<00:05:50.580> have<00:05:50.699> all<00:05:50.820> the<00:05:50.940> opcodes<00:05:51.360> we 00:05:51.650 --> 00:05:51.660 align:start position:0% two but here we have all the opcodes we 00:05:51.660 --> 00:05:53.330 align:start position:0% two but here we have all the opcodes we have<00:05:51.780> implemented<00:05:52.199> all<00:05:52.380> the<00:05:52.560> ethereum<00:05:52.919> of 00:05:53.330 --> 00:05:53.340 align:start position:0% have implemented all the ethereum of 00:05:53.340 --> 00:05:56.689 align:start position:0% have implemented all the ethereum of codes<00:05:53.580> uh<00:05:54.240> at<00:05:54.479> this<00:05:54.600> point<00:05:54.740> and<00:05:55.740> then<00:05:55.919> once<00:05:56.580> we 00:05:56.689 --> 00:05:56.699 align:start position:0% codes uh at this point and then once we 00:05:56.699 --> 00:05:58.129 align:start position:0% codes uh at this point and then once we run<00:05:57.060> this<00:05:57.300> then<00:05:57.539> we<00:05:57.720> need<00:05:57.840> like<00:05:58.020> the 00:05:58.129 --> 00:05:58.139 align:start position:0% run this then we need like the 00:05:58.139 --> 00:06:00.050 align:start position:0% run this then we need like the cryptographic<00:05:58.680> prover<00:05:58.979> the<00:05:59.520> cryptographic 00:06:00.050 --> 00:06:00.060 align:start position:0% cryptographic prover the cryptographic 00:06:00.060 --> 00:06:02.749 align:start position:0% cryptographic prover the cryptographic proverb<00:06:00.479> uh<00:06:01.320> what<00:06:01.560> we<00:06:01.680> do<00:06:01.860> is<00:06:02.100> mainly<00:06:02.460> we<00:06:02.580> are 00:06:02.749 --> 00:06:02.759 align:start position:0% proverb uh what we do is mainly we are 00:06:02.759 --> 00:06:06.170 align:start position:0% proverb uh what we do is mainly we are using<00:06:02.940> Starks<00:06:03.539> with<00:06:03.840> a<00:06:04.080> a<00:06:04.800> very<00:06:05.520> optimal<00:06:05.940> way 00:06:06.170 --> 00:06:06.180 align:start position:0% using Starks with a a very optimal way 00:06:06.180 --> 00:06:08.390 align:start position:0% using Starks with a a very optimal way to<00:06:06.419> compute<00:06:06.780> proving<00:06:07.380> systems<00:06:07.800> we<00:06:07.979> are<00:06:08.160> using 00:06:08.390 --> 00:06:08.400 align:start position:0% to compute proving systems we are using 00:06:08.400 --> 00:06:10.550 align:start position:0% to compute proving systems we are using Goldilocks<00:06:09.060> it's<00:06:09.180> a<00:06:09.360> technology<00:06:09.660> for<00:06:10.020> from 00:06:10.550 --> 00:06:10.560 align:start position:0% Goldilocks it's a technology for from 00:06:10.560 --> 00:06:12.430 align:start position:0% Goldilocks it's a technology for from people<00:06:10.800> from<00:06:11.100> for<00:06:11.400> our<00:06:11.699> colleagues<00:06:12.240> in 00:06:12.430 --> 00:06:12.440 align:start position:0% people from for our colleagues in 00:06:12.440 --> 00:06:15.170 align:start position:0% people from for our colleagues in polygon<00:06:13.440> 0<00:06:13.620> that<00:06:14.280> makes<00:06:14.400> to<00:06:14.639> build<00:06:14.820> these 00:06:15.170 --> 00:06:15.180 align:start position:0% polygon 0 that makes to build these 00:06:15.180 --> 00:06:17.749 align:start position:0% polygon 0 that makes to build these proofs<00:06:15.479> really<00:06:15.960> fast<00:06:16.199> and<00:06:16.979> it's<00:06:17.340> again<00:06:17.520> for 00:06:17.749 --> 00:06:17.759 align:start position:0% proofs really fast and it's again for 00:06:17.759 --> 00:06:19.909 align:start position:0% proofs really fast and it's again for recursion<00:06:18.300> so<00:06:18.539> it's<00:06:18.720> approver<00:06:19.139> can<00:06:19.380> aggregate 00:06:19.909 --> 00:06:19.919 align:start position:0% recursion so it's approver can aggregate 00:06:19.919 --> 00:06:22.730 align:start position:0% recursion so it's approver can aggregate many<00:06:20.460> proofs<00:06:21.000> and<00:06:21.539> at<00:06:21.720> the<00:06:21.840> end<00:06:21.960> this<00:06:22.440> is<00:06:22.620> a 00:06:22.730 --> 00:06:22.740 align:start position:0% many proofs and at the end this is a 00:06:22.740 --> 00:06:24.950 align:start position:0% many proofs and at the end this is a stark<00:06:22.979> and<00:06:23.520> at<00:06:23.940> the<00:06:24.060> end<00:06:24.120> what's<00:06:24.539> doing<00:06:24.720> is<00:06:24.840> we 00:06:24.950 --> 00:06:24.960 align:start position:0% stark and at the end what's doing is we 00:06:24.960 --> 00:06:26.870 align:start position:0% stark and at the end what's doing is we are<00:06:25.020> are<00:06:25.380> converting<00:06:25.800> we<00:06:26.039> are<00:06:26.220> very<00:06:26.280> fine<00:06:26.520> is<00:06:26.699> a 00:06:26.870 --> 00:06:26.880 align:start position:0% are are converting we are very fine is a 00:06:26.880 --> 00:06:29.090 align:start position:0% are are converting we are very fine is a stark<00:06:27.060> with<00:06:27.240> a<00:06:27.360> snark<00:06:27.660> so<00:06:28.139> at<00:06:28.319> the<00:06:28.440> end<00:06:28.560> we<00:06:28.919> just 00:06:29.090 --> 00:06:29.100 align:start position:0% stark with a snark so at the end we just 00:06:29.100 --> 00:06:31.550 align:start position:0% stark with a snark so at the end we just in<00:06:29.340> ethereum<00:06:29.819> we<00:06:30.360> are<00:06:30.479> just<00:06:30.720> verifying<00:06:31.259> a 00:06:31.550 --> 00:06:31.560 align:start position:0% in ethereum we are just verifying a 00:06:31.560 --> 00:06:35.090 align:start position:0% in ethereum we are just verifying a normal<00:06:31.740> growth<00:06:32.639> 16<00:06:32.819> or<00:06:33.120> block<00:06:33.419> uh<00:06:34.199> proof<00:06:34.620> it's 00:06:35.090 --> 00:06:35.100 align:start position:0% normal growth 16 or block uh proof it's 00:06:35.100 --> 00:06:37.189 align:start position:0% normal growth 16 or block uh proof it's just<00:06:35.340> a<00:06:35.520> circle<00:06:35.699> it's<00:06:36.120> a<00:06:36.300> circum<00:06:36.600> circuit<00:06:36.900> in 00:06:37.189 --> 00:06:37.199 align:start position:0% just a circle it's a circum circuit in 00:06:37.199 --> 00:06:39.350 align:start position:0% just a circle it's a circum circuit in the<00:06:37.259> last<00:06:37.380> in<00:06:37.680> the<00:06:37.800> bottom<00:06:38.100> of<00:06:38.639> that<00:06:38.819> piece<00:06:39.000> so 00:06:39.350 --> 00:06:39.360 align:start position:0% the last in the bottom of that piece so 00:06:39.360 --> 00:06:41.150 align:start position:0% the last in the bottom of that piece so this<00:06:39.539> is<00:06:39.600> the<00:06:39.780> stack<00:06:40.080> the<00:06:40.560> cryptographic 00:06:41.150 --> 00:06:41.160 align:start position:0% this is the stack the cryptographic 00:06:41.160 --> 00:06:43.730 align:start position:0% this is the stack the cryptographic stack<00:06:41.520> for<00:06:42.000> verifying<00:06:42.600> that 00:06:43.730 --> 00:06:43.740 align:start position:0% stack for verifying that 00:06:43.740 --> 00:06:45.469 align:start position:0% stack for verifying that okay<00:06:44.100> so<00:06:44.340> let's 00:06:45.469 --> 00:06:45.479 align:start position:0% okay so let's 00:06:45.479 --> 00:06:47.749 align:start position:0% okay so let's cross<00:06:45.780> fingers<00:06:46.319> and<00:06:46.680> let's<00:06:46.860> try<00:06:47.280> to<00:06:47.460> see<00:06:47.580> the 00:06:47.749 --> 00:06:47.759 align:start position:0% cross fingers and let's try to see the 00:06:47.759 --> 00:06:50.210 align:start position:0% cross fingers and let's try to see the demo<00:06:48.180> let's<00:06:48.840> see<00:06:49.020> if<00:06:49.080> it<00:06:49.199> works<00:06:49.500> if<00:06:49.680> it<00:06:49.860> doesn't 00:06:50.210 --> 00:06:50.220 align:start position:0% demo let's see if it works if it doesn't 00:06:50.220 --> 00:06:52.930 align:start position:0% demo let's see if it works if it doesn't work<00:06:50.400> you<00:06:50.699> can<00:06:50.759> try<00:06:51.000> it<00:06:51.600> okay<00:06:51.780> you<00:06:52.199> can<00:06:52.319> go<00:06:52.500> to 00:06:52.930 --> 00:06:52.940 align:start position:0% work you can try it okay you can go to 00:06:52.940 --> 00:06:54.969 align:start position:0% work you can try it okay you can go to public.c 00:06:54.969 --> 00:06:54.979 align:start position:0% public.c 00:06:54.979 --> 00:06:57.469 align:start position:0% public.c kvm.test.net<00:06:55.979> and<00:06:56.520> fantastic<00:06:56.940> you<00:06:57.240> will<00:06:57.360> see 00:06:57.469 --> 00:06:57.479 align:start position:0% kvm.test.net and fantastic you will see 00:06:57.479 --> 00:06:59.210 align:start position:0% kvm.test.net and fantastic you will see that's<00:06:57.660> very<00:06:57.960> simple<00:06:58.139> the<00:06:58.680> demo<00:06:58.979> that<00:06:59.039> I'm 00:06:59.210 --> 00:06:59.220 align:start position:0% that's very simple the demo that I'm 00:06:59.220 --> 00:07:01.550 align:start position:0% that's very simple the demo that I'm gonna<00:06:59.340> do<00:07:00.060> is<00:07:00.600> first<00:07:00.900> of<00:07:01.020> all<00:07:01.139> I'm<00:07:01.440> gonna 00:07:01.550 --> 00:07:01.560 align:start position:0% gonna do is first of all I'm gonna 00:07:01.560 --> 00:07:05.270 align:start position:0% gonna do is first of all I'm gonna Bridge<00:07:01.860> it<00:07:02.160> let<00:07:02.460> me<00:07:02.580> just<00:07:02.819> uh<00:07:03.180> switch<00:07:04.020> okay<00:07:04.560> so 00:07:05.270 --> 00:07:05.280 align:start position:0% Bridge it let me just uh switch okay so 00:07:05.280 --> 00:07:06.590 align:start position:0% Bridge it let me just uh switch okay so the<00:07:05.639> first<00:07:05.699> thing<00:07:05.880> that<00:07:06.000> I'm<00:07:06.180> going<00:07:06.240> to<00:07:06.360> do<00:07:06.479> is 00:07:06.590 --> 00:07:06.600 align:start position:0% the first thing that I'm going to do is 00:07:06.600 --> 00:07:09.590 align:start position:0% the first thing that I'm going to do is I'm<00:07:06.780> gonna<00:07:06.960> I'm<00:07:07.440> gonna<00:07:07.560> Bridge<00:07:07.979> uh<00:07:08.819> so<00:07:09.120> I<00:07:09.419> mean 00:07:09.590 --> 00:07:09.600 align:start position:0% I'm gonna I'm gonna Bridge uh so I mean 00:07:09.600 --> 00:07:12.350 align:start position:0% I'm gonna I'm gonna Bridge uh so I mean go<00:07:09.780> early<00:07:09.960> uh<00:07:10.919> I'm<00:07:11.039> going<00:07:11.280> to<00:07:11.400> early<00:07:11.580> Network<00:07:11.880> I 00:07:12.350 --> 00:07:12.360 align:start position:0% go early uh I'm going to early Network I 00:07:12.360 --> 00:07:15.710 align:start position:0% go early uh I'm going to early Network I have<00:07:12.479> an<00:07:12.660> account<00:07:12.840> here<00:07:13.319> that's<00:07:14.220> uh<00:07:14.699> has<00:07:15.419> three 00:07:15.710 --> 00:07:15.720 align:start position:0% have an account here that's uh has three 00:07:15.720 --> 00:07:18.650 align:start position:0% have an account here that's uh has three go<00:07:15.960> early<00:07:16.139> already<00:07:16.620> and<00:07:17.280> it's<00:07:17.460> just<00:07:17.699> a<00:07:17.940> strike 00:07:18.650 --> 00:07:18.660 align:start position:0% go early already and it's just a strike 00:07:18.660 --> 00:07:20.330 align:start position:0% go early already and it's just a strike new<00:07:18.840> account<00:07:19.080> that<00:07:19.440> I<00:07:19.620> just<00:07:19.740> created<00:07:20.039> before 00:07:20.330 --> 00:07:20.340 align:start position:0% new account that I just created before 00:07:20.340 --> 00:07:22.070 align:start position:0% new account that I just created before this<00:07:20.699> so<00:07:21.300> the<00:07:21.419> first<00:07:21.539> thing<00:07:21.720> that<00:07:21.840> I'm<00:07:21.960> going 00:07:22.070 --> 00:07:22.080 align:start position:0% this so the first thing that I'm going 00:07:22.080 --> 00:07:23.629 align:start position:0% this so the first thing that I'm going to<00:07:22.199> do<00:07:22.319> is<00:07:22.500> I'm<00:07:22.620> gonna<00:07:22.800> transfer<00:07:23.280> I'm<00:07:23.520> gonna 00:07:23.629 --> 00:07:23.639 align:start position:0% to do is I'm gonna transfer I'm gonna 00:07:23.639 --> 00:07:26.950 align:start position:0% to do is I'm gonna transfer I'm gonna Bridge<00:07:23.880> three<00:07:24.599> ethers<00:07:25.319> uh<00:07:26.220> three<00:07:26.400> uh<00:07:26.699> well 00:07:26.950 --> 00:07:26.960 align:start position:0% Bridge three ethers uh three uh well 00:07:26.960 --> 00:07:29.749 align:start position:0% Bridge three ethers uh three uh well 0.25<00:07:27.960> first<00:07:28.620> this<00:07:28.919> is<00:07:28.979> the<00:07:29.099> maximum<00:07:29.460> that<00:07:29.699> we 00:07:29.749 --> 00:07:29.759 align:start position:0% 0.25 first this is the maximum that we 00:07:29.759 --> 00:07:31.430 align:start position:0% 0.25 first this is the maximum that we allow<00:07:30.060> here<00:07:30.300> in<00:07:30.539> this<00:07:30.660> test<00:07:30.840> now<00:07:31.020> just<00:07:31.319> to 00:07:31.430 --> 00:07:31.440 align:start position:0% allow here in this test now just to 00:07:31.440 --> 00:07:33.050 align:start position:0% allow here in this test now just to protect<00:07:31.680> some<00:07:31.919> Daniel<00:07:32.099> of<00:07:32.460> service<00:07:32.580> attacks 00:07:33.050 --> 00:07:33.060 align:start position:0% protect some Daniel of service attacks 00:07:33.060 --> 00:07:36.469 align:start position:0% protect some Daniel of service attacks here<00:07:33.319> uh<00:07:34.319> and<00:07:34.620> we<00:07:34.800> are<00:07:34.919> just<00:07:35.099> to<00:07:35.340> transfer<00:07:35.940> to 00:07:36.469 --> 00:07:36.479 align:start position:0% here uh and we are just to transfer to 00:07:36.479 --> 00:07:39.350 align:start position:0% here uh and we are just to transfer to the<00:07:36.720> uh<00:07:36.900> to<00:07:37.319> the<00:07:37.440> layer<00:07:37.740> to<00:07:37.979> the<00:07:38.160> layers<00:07:38.460> too<00:07:38.880> so 00:07:39.350 --> 00:07:39.360 align:start position:0% the uh to the layer to the layers too so 00:07:39.360 --> 00:07:43.189 align:start position:0% the uh to the layer to the layers too so I<00:07:40.139> mean<00:07:40.259> go<00:07:40.500> early<00:07:40.740> right<00:07:40.979> now<00:07:41.160> so<00:07:41.460> I'm<00:07:41.639> just<00:07:41.940> uh 00:07:43.189 --> 00:07:43.199 align:start position:0% I mean go early right now so I'm just uh 00:07:43.199 --> 00:07:46.189 align:start position:0% I mean go early right now so I'm just uh like<00:07:43.740> let's<00:07:44.039> see<00:07:44.340> if<00:07:44.400> ethereum<00:07:45.120> works<00:07:45.900> okay 00:07:46.189 --> 00:07:46.199 align:start position:0% like let's see if ethereum works okay 00:07:46.199 --> 00:07:47.330 align:start position:0% like let's see if ethereum works okay here<00:07:46.500> we<00:07:46.620> are 00:07:47.330 --> 00:07:47.340 align:start position:0% here we are 00:07:47.340 --> 00:07:49.550 align:start position:0% here we are uh<00:07:48.120> let's<00:07:48.300> Bridge<00:07:48.479> it 00:07:49.550 --> 00:07:49.560 align:start position:0% uh let's Bridge it 00:07:49.560 --> 00:07:53.689 align:start position:0% uh let's Bridge it okay<00:07:50.039> so<00:07:50.460> let's<00:07:50.699> sign<00:07:51.060> let<00:07:51.960> me<00:07:52.139> just<00:07:52.380> uh 00:07:53.689 --> 00:07:53.699 align:start position:0% okay so let's sign let me just uh 00:07:53.699 --> 00:07:57.230 align:start position:0% okay so let's sign let me just uh let<00:07:54.060> me<00:07:54.180> just<00:07:54.419> let<00:07:54.599> me<00:07:54.780> just<00:07:54.960> modify 00:07:57.230 --> 00:07:57.240 align:start position:0% let me just let me just modify 00:07:57.240 --> 00:08:00.409 align:start position:0% let me just let me just modify the<00:07:57.660> gas<00:07:57.780> fee<00:07:58.199> so<00:07:58.319> that<00:07:58.620> it<00:07:58.860> takes<00:07:59.160> uh<00:07:59.940> it<00:08:00.180> goes 00:08:00.409 --> 00:08:00.419 align:start position:0% the gas fee so that it takes uh it goes 00:08:00.419 --> 00:08:01.370 align:start position:0% the gas fee so that it takes uh it goes faster 00:08:01.370 --> 00:08:01.380 align:start position:0% faster 00:08:01.380 --> 00:08:04.309 align:start position:0% faster let's<00:08:01.560> go<00:08:01.860> early<00:08:02.099> so<00:08:02.580> you<00:08:02.819> never<00:08:02.940> know<00:08:03.180> save 00:08:04.309 --> 00:08:04.319 align:start position:0% let's go early so you never know save 00:08:04.319 --> 00:08:07.309 align:start position:0% let's go early so you never know save okay<00:08:04.680> and<00:08:04.919> then<00:08:05.039> just<00:08:05.280> send<00:08:05.580> this<00:08:05.759> transaction 00:08:07.309 --> 00:08:07.319 align:start position:0% okay and then just send this transaction 00:08:07.319 --> 00:08:11.210 align:start position:0% okay and then just send this transaction okay<00:08:07.740> okay<00:08:08.000> now<00:08:09.000> that<00:08:09.240> that<00:08:09.479> no<00:08:10.080> that<00:08:10.560> so<00:08:11.099> we 00:08:11.210 --> 00:08:11.220 align:start position:0% okay okay now that that no that so we 00:08:11.220 --> 00:08:13.010 align:start position:0% okay okay now that that no that so we just<00:08:11.460> deposit<00:08:11.940> the<00:08:12.060> transaction<00:08:12.419> this 00:08:13.010 --> 00:08:13.020 align:start position:0% just deposit the transaction this 00:08:13.020 --> 00:08:16.189 align:start position:0% just deposit the transaction this transaction<00:08:13.440> is<00:08:14.180> mining<00:08:15.180> inwardly<00:08:15.660> we<00:08:16.080> need 00:08:16.189 --> 00:08:16.199 align:start position:0% transaction is mining inwardly we need 00:08:16.199 --> 00:08:17.749 align:start position:0% transaction is mining inwardly we need to<00:08:16.319> White<00:08:16.560> also<00:08:16.919> a<00:08:17.099> little<00:08:17.160> bit<00:08:17.280> so<00:08:17.520> that<00:08:17.639> this 00:08:17.749 --> 00:08:17.759 align:start position:0% to White also a little bit so that this 00:08:17.759 --> 00:08:20.029 align:start position:0% to White also a little bit so that this transaction<00:08:18.180> is<00:08:18.539> kind<00:08:18.780> of<00:08:18.960> a<00:08:19.080> final<00:08:19.259> so<00:08:19.860> that 00:08:20.029 --> 00:08:20.039 align:start position:0% transaction is kind of a final so that 00:08:20.039 --> 00:08:22.550 align:start position:0% transaction is kind of a final so that this<00:08:20.220> transaction<00:08:20.699> is<00:08:21.300> included<00:08:21.780> okay<00:08:22.080> right 00:08:22.550 --> 00:08:22.560 align:start position:0% this transaction is included okay right 00:08:22.560 --> 00:08:25.610 align:start position:0% this transaction is included okay right now<00:08:22.800> it's<00:08:23.280> this<00:08:23.520> is<00:08:23.759> already<00:08:23.879> so<00:08:24.599> it's<00:08:25.080> this<00:08:25.440> is 00:08:25.610 --> 00:08:25.620 align:start position:0% now it's this is already so it's this is 00:08:25.620 --> 00:08:27.110 align:start position:0% now it's this is already so it's this is already<00:08:25.680> done<00:08:25.919> what<00:08:26.280> we<00:08:26.400> have<00:08:26.520> done<00:08:26.699> is<00:08:26.879> we 00:08:27.110 --> 00:08:27.120 align:start position:0% already done what we have done is we 00:08:27.120 --> 00:08:28.909 align:start position:0% already done what we have done is we just<00:08:27.419> put<00:08:27.900> this<00:08:28.080> transaction<00:08:28.500> in<00:08:28.740> America 00:08:28.909 --> 00:08:28.919 align:start position:0% just put this transaction in America 00:08:28.919 --> 00:08:31.070 align:start position:0% just put this transaction in America tree<00:08:29.280> and<00:08:29.759> then<00:08:29.879> the<00:08:30.120> root<00:08:30.360> of<00:08:30.479> this<00:08:30.599> migratory 00:08:31.070 --> 00:08:31.080 align:start position:0% tree and then the root of this migratory 00:08:31.080 --> 00:08:34.790 align:start position:0% tree and then the root of this migratory of<00:08:31.259> all<00:08:31.379> deposits<00:08:32.039> is<00:08:32.640> passed<00:08:33.599> uh<00:08:34.080> is<00:08:34.440> passed 00:08:34.790 --> 00:08:34.800 align:start position:0% of all deposits is passed uh is passed 00:08:34.800 --> 00:08:37.550 align:start position:0% of all deposits is passed uh is passed as<00:08:34.919> the<00:08:35.099> as<00:08:35.520> the<00:08:35.700> state<00:08:35.940> of<00:08:36.479> the<00:08:36.659> of<00:08:37.200> the<00:08:37.380> Roll 00:08:37.550 --> 00:08:37.560 align:start position:0% as the as the state of the of the Roll 00:08:37.560 --> 00:08:39.889 align:start position:0% as the as the state of the of the Roll Up<00:08:37.740> the<00:08:38.219> sequencer<00:08:38.760> actually<00:08:39.180> there<00:08:39.479> has<00:08:39.779> not 00:08:39.889 --> 00:08:39.899 align:start position:0% Up the sequencer actually there has not 00:08:39.899 --> 00:08:42.050 align:start position:0% Up the sequencer actually there has not been<00:08:40.080> any<00:08:40.260> trans<00:08:40.560> any<00:08:41.039> special<00:08:41.580> transaction 00:08:42.050 --> 00:08:42.060 align:start position:0% been any trans any special transaction 00:08:42.060 --> 00:08:44.269 align:start position:0% been any trans any special transaction on<00:08:42.300> chain<00:08:42.539> because<00:08:42.899> the<00:08:43.140> sequencer<00:08:43.740> already 00:08:44.269 --> 00:08:44.279 align:start position:0% on chain because the sequencer already 00:08:44.279 --> 00:08:47.449 align:start position:0% on chain because the sequencer already takes<00:08:44.880> in<00:08:45.120> account<00:08:45.300> that<00:08:45.600> okay<00:08:46.260> so<00:08:46.860> now<00:08:47.220> let's 00:08:47.449 --> 00:08:47.459 align:start position:0% takes in account that okay so now let's 00:08:47.459 --> 00:08:50.690 align:start position:0% takes in account that okay so now let's uh<00:08:47.880> finalize<00:08:48.420> this<00:08:48.779> okay<00:08:49.380> and<00:08:49.920> this<00:08:50.279> finalize 00:08:50.690 --> 00:08:50.700 align:start position:0% uh finalize this okay and this finalize 00:08:50.700 --> 00:08:53.329 align:start position:0% uh finalize this okay and this finalize what<00:08:51.060> is<00:08:51.180> doing<00:08:51.360> is<00:08:51.720> collecting<00:08:52.560> is<00:08:52.860> doing<00:08:53.040> an 00:08:53.329 --> 00:08:53.339 align:start position:0% what is doing is collecting is doing an 00:08:53.339 --> 00:08:56.269 align:start position:0% what is doing is collecting is doing an L2<00:08:53.700> transaction<00:08:54.180> to<00:08:54.839> collect<00:08:55.200> these<00:08:55.860> uh<00:08:56.160> for 00:08:56.269 --> 00:08:56.279 align:start position:0% L2 transaction to collect these uh for 00:08:56.279 --> 00:08:59.090 align:start position:0% L2 transaction to collect these uh for these<00:08:56.760> phones<00:08:57.000> this<00:08:57.600> ethereum<00:08:58.080> in<00:08:58.500> the<00:08:58.620> in<00:08:58.980> the 00:08:59.090 --> 00:08:59.100 align:start position:0% these phones this ethereum in the in the 00:08:59.100 --> 00:09:01.850 align:start position:0% these phones this ethereum in the in the layer<00:08:59.399> two<00:08:59.519> so<00:08:59.940> here<00:09:00.240> when<00:09:00.720> I<00:09:00.959> push<00:09:01.320> here<00:09:01.500> the 00:09:01.850 --> 00:09:01.860 align:start position:0% layer two so here when I push here the 00:09:01.860 --> 00:09:04.190 align:start position:0% layer two so here when I push here the first<00:09:02.040> thing<00:09:02.160> that<00:09:02.519> I'll<00:09:02.880> ask<00:09:03.480> me<00:09:03.660> is<00:09:03.779> ask<00:09:03.959> me 00:09:04.190 --> 00:09:04.200 align:start position:0% first thing that I'll ask me is ask me 00:09:04.200 --> 00:09:06.050 align:start position:0% first thing that I'll ask me is ask me is<00:09:04.320> just<00:09:04.500> to<00:09:04.680> switch<00:09:04.800> the<00:09:05.100> network<00:09:05.279> so<00:09:05.940> I'm 00:09:06.050 --> 00:09:06.060 align:start position:0% is just to switch the network so I'm 00:09:06.060 --> 00:09:08.449 align:start position:0% is just to switch the network so I'm just<00:09:06.300> switch<00:09:06.540> the<00:09:06.779> network 00:09:08.449 --> 00:09:08.459 align:start position:0% just switch the network 00:09:08.459 --> 00:09:10.970 align:start position:0% just switch the network and<00:09:08.940> now<00:09:09.180> I'm<00:09:09.360> just<00:09:09.540> signing<00:09:10.140> the<00:09:10.620> transaction 00:09:10.970 --> 00:09:10.980 align:start position:0% and now I'm just signing the transaction 00:09:10.980 --> 00:09:13.550 align:start position:0% and now I'm just signing the transaction in<00:09:11.399> in<00:09:11.760> and<00:09:12.180> just<00:09:12.540> on<00:09:12.720> just<00:09:13.019> signing<00:09:13.380> the 00:09:13.550 --> 00:09:13.560 align:start position:0% in in and just on just signing the 00:09:13.560 --> 00:09:15.170 align:start position:0% in in and just on just signing the transaction<00:09:13.860> in<00:09:14.160> Layer<00:09:14.399> Two 00:09:15.170 --> 00:09:15.180 align:start position:0% transaction in Layer Two 00:09:15.180 --> 00:09:16.730 align:start position:0% transaction in Layer Two okay<00:09:15.420> because<00:09:15.959> I<00:09:16.260> just<00:09:16.380> signed<00:09:16.680> into 00:09:16.730 --> 00:09:16.740 align:start position:0% okay because I just signed into 00:09:16.740 --> 00:09:19.430 align:start position:0% okay because I just signed into transaction 00:09:19.430 --> 00:09:19.440 align:start position:0% 00:09:19.440 --> 00:09:21.710 align:start position:0% let's<00:09:19.920> see<00:09:20.100> if<00:09:20.220> it<00:09:20.339> works 00:09:21.710 --> 00:09:21.720 align:start position:0% let's see if it works 00:09:21.720 --> 00:09:23.389 align:start position:0% let's see if it works there<00:09:22.080> we<00:09:22.260> go 00:09:23.389 --> 00:09:23.399 align:start position:0% there we go 00:09:23.399 --> 00:09:26.269 align:start position:0% there we go shoot<00:09:23.820> yeah<00:09:24.300> here<00:09:24.540> is<00:09:24.779> okay<00:09:25.380> so<00:09:25.800> now<00:09:25.920> if<00:09:26.160> I 00:09:26.269 --> 00:09:26.279 align:start position:0% shoot yeah here is okay so now if I 00:09:26.279 --> 00:09:28.070 align:start position:0% shoot yeah here is okay so now if I check<00:09:26.399> the<00:09:26.640> account<00:09:26.760> I'm<00:09:27.240> in<00:09:27.420> the<00:09:27.540> layer<00:09:27.959> two 00:09:28.070 --> 00:09:28.080 align:start position:0% check the account I'm in the layer two 00:09:28.080 --> 00:09:31.370 align:start position:0% check the account I'm in the layer two now<00:09:28.440> I<00:09:28.680> have<00:09:28.740> the<00:09:28.920> 0.25<00:09:29.700> ether<00:09:30.180> in<00:09:30.839> the<00:09:30.959> layer 00:09:31.370 --> 00:09:31.380 align:start position:0% now I have the 0.25 ether in the layer 00:09:31.380 --> 00:09:34.310 align:start position:0% now I have the 0.25 ether in the layer in<00:09:31.800> the<00:09:31.920> layer<00:09:32.160> two<00:09:32.279> okay<00:09:32.880> so<00:09:33.480> now<00:09:33.720> let's<00:09:33.959> now 00:09:34.310 --> 00:09:34.320 align:start position:0% in the layer two okay so now let's now 00:09:34.320 --> 00:09:36.470 align:start position:0% in the layer two okay so now let's now let's<00:09:34.620> go<00:09:34.860> to<00:09:35.040> do<00:09:35.820> something<00:09:36.060> with<00:09:36.300> this 00:09:36.470 --> 00:09:36.480 align:start position:0% let's go to do something with this 00:09:36.480 --> 00:09:37.910 align:start position:0% let's go to do something with this account<00:09:36.600> okay<00:09:36.959> let's<00:09:37.260> create<00:09:37.620> a<00:09:37.800> smart 00:09:37.910 --> 00:09:37.920 align:start position:0% account okay let's create a smart 00:09:37.920 --> 00:09:40.850 align:start position:0% account okay let's create a smart contract<00:09:38.399> and<00:09:38.820> deploy<00:09:39.180> it<00:09:39.360> in<00:09:39.540> this<00:09:39.720> layer<00:09:40.080> too 00:09:40.850 --> 00:09:40.860 align:start position:0% contract and deploy it in this layer too 00:09:40.860 --> 00:09:43.550 align:start position:0% contract and deploy it in this layer too so<00:09:41.459> let's<00:09:41.700> go<00:09:41.880> to<00:09:42.000> remix 00:09:43.550 --> 00:09:43.560 align:start position:0% so let's go to remix 00:09:43.560 --> 00:09:47.030 align:start position:0% so let's go to remix just<00:09:44.100> gonna<00:09:44.399> use<00:09:44.820> uh<00:09:45.300> an<00:09:45.720> example<00:09:46.140> very<00:09:46.800> simple 00:09:47.030 --> 00:09:47.040 align:start position:0% just gonna use uh an example very simple 00:09:47.040 --> 00:09:48.930 align:start position:0% just gonna use uh an example very simple smart<00:09:47.700> contract 00:09:48.930 --> 00:09:48.940 align:start position:0% smart contract 00:09:48.940 --> 00:09:50.509 align:start position:0% smart contract [Music] 00:09:50.509 --> 00:09:50.519 align:start position:0% [Music] 00:09:50.519 --> 00:09:51.889 align:start position:0% [Music] looks<00:09:51.060> like 00:09:51.889 --> 00:09:51.899 align:start position:0% looks like 00:09:51.899 --> 00:09:55.070 align:start position:0% looks like remix<00:09:52.260> is<00:09:52.680> gone 00:09:55.070 --> 00:09:55.080 align:start position:0% 00:09:55.080 --> 00:09:57.350 align:start position:0% so<00:09:55.500> let's<00:09:55.620> meet<00:09:56.100> this<00:09:56.279> little<00:09:56.459> work 00:09:57.350 --> 00:09:57.360 align:start position:0% so let's meet this little work 00:09:57.360 --> 00:10:00.110 align:start position:0% so let's meet this little work yes<00:09:57.720> it's<00:09:58.620> just<00:09:58.860> a<00:09:58.980> very<00:09:59.100> example<00:09:59.580> smart 00:10:00.110 --> 00:10:00.120 align:start position:0% yes it's just a very example smart 00:10:00.120 --> 00:10:03.230 align:start position:0% yes it's just a very example smart contract<00:10:00.600> so<00:10:01.200> let<00:10:01.380> me<00:10:01.560> compile<00:10:02.160> let<00:10:03.120> me 00:10:03.230 --> 00:10:03.240 align:start position:0% contract so let me compile let me 00:10:03.240 --> 00:10:05.949 align:start position:0% contract so let me compile let me compile<00:10:03.540> this<00:10:03.720> smart<00:10:04.019> contract 00:10:05.949 --> 00:10:05.959 align:start position:0% compile this smart contract 00:10:05.959 --> 00:10:08.930 align:start position:0% compile this smart contract there<00:10:06.959> is<00:10:07.140> and<00:10:07.800> now<00:10:07.920> I'm<00:10:08.100> going<00:10:08.279> to<00:10:08.399> deploy<00:10:08.820> it 00:10:08.930 --> 00:10:08.940 align:start position:0% there is and now I'm going to deploy it 00:10:08.940 --> 00:10:10.670 align:start position:0% there is and now I'm going to deploy it to<00:10:09.120> the<00:10:09.360> layer<00:10:09.600> two<00:10:09.720> so<00:10:09.959> I'm<00:10:10.080> going<00:10:10.200> to<00:10:10.320> connect 00:10:10.670 --> 00:10:10.680 align:start position:0% to the layer two so I'm going to connect 00:10:10.680 --> 00:10:14.030 align:start position:0% to the layer two so I'm going to connect this<00:10:10.980> to<00:10:11.480> a<00:10:12.480> metamask 00:10:14.030 --> 00:10:14.040 align:start position:0% this to a metamask 00:10:14.040 --> 00:10:18.290 align:start position:0% this to a metamask okay<00:10:14.700> I'm<00:10:15.420> just<00:10:15.660> using<00:10:16.560> this<00:10:16.920> account<00:10:17.339> and 00:10:18.290 --> 00:10:18.300 align:start position:0% okay I'm just using this account and 00:10:18.300 --> 00:10:20.810 align:start position:0% okay I'm just using this account and then<00:10:18.480> I'm<00:10:18.779> just<00:10:19.080> uh<00:10:19.680> well<00:10:20.040> this<00:10:20.279> is<00:10:20.399> I<00:10:20.700> don't 00:10:20.810 --> 00:10:20.820 align:start position:0% then I'm just uh well this is I don't 00:10:20.820 --> 00:10:23.329 align:start position:0% then I'm just uh well this is I don't know<00:10:20.940> if<00:10:21.120> I'm<00:10:21.300> connected<00:10:21.779> to<00:10:21.959> the<00:10:22.080> last<00:10:22.200> one 00:10:23.329 --> 00:10:23.339 align:start position:0% know if I'm connected to the last one 00:10:23.339 --> 00:10:24.470 align:start position:0% know if I'm connected to the last one well 00:10:24.470 --> 00:10:24.480 align:start position:0% well 00:10:24.480 --> 00:10:26.269 align:start position:0% well just<00:10:25.019> connect<00:10:25.260> here 00:10:26.269 --> 00:10:26.279 align:start position:0% just connect here 00:10:26.279 --> 00:10:28.310 align:start position:0% just connect here yeah<00:10:26.519> this<00:10:26.820> is<00:10:26.880> the<00:10:27.000> one<00:10:27.180> that<00:10:27.480> I<00:10:27.899> just<00:10:27.959> did<00:10:28.140> I 00:10:28.310 --> 00:10:28.320 align:start position:0% yeah this is the one that I just did I 00:10:28.320 --> 00:10:30.530 align:start position:0% yeah this is the one that I just did I have<00:10:28.440> the<00:10:28.560> 25<00:10:28.740> feature<00:10:29.339> here<00:10:29.459> so<00:10:30.060> and<00:10:30.240> let's 00:10:30.530 --> 00:10:30.540 align:start position:0% have the 25 feature here so and let's 00:10:30.540 --> 00:10:32.930 align:start position:0% have the 25 feature here so and let's deploy<00:10:31.019> this<00:10:31.200> okay<00:10:31.560> so<00:10:31.920> just<00:10:32.220> deploy<00:10:32.760> this 00:10:32.930 --> 00:10:32.940 align:start position:0% deploy this okay so just deploy this 00:10:32.940 --> 00:10:35.750 align:start position:0% deploy this okay so just deploy this Mark<00:10:33.240> on<00:10:33.420> track 00:10:35.750 --> 00:10:35.760 align:start position:0% 00:10:35.760 --> 00:10:38.630 align:start position:0% it<00:10:36.300> asked<00:10:36.600> me<00:10:36.720> to<00:10:36.839> sign<00:10:37.140> I<00:10:37.740> just<00:10:38.040> confirm<00:10:38.459> this 00:10:38.630 --> 00:10:38.640 align:start position:0% it asked me to sign I just confirm this 00:10:38.640 --> 00:10:41.509 align:start position:0% it asked me to sign I just confirm this transaction 00:10:41.509 --> 00:10:41.519 align:start position:0% 00:10:41.519 --> 00:10:45.470 align:start position:0% see<00:10:41.940> if<00:10:42.060> it<00:10:42.240> goes 00:10:45.470 --> 00:10:45.480 align:start position:0% 00:10:45.480 --> 00:10:47.990 align:start position:0% its<00:10:46.200> internet<00:10:46.320> is<00:10:46.740> not<00:10:46.920> like<00:10:47.279> the<00:10:47.519> fastest 00:10:47.990 --> 00:10:48.000 align:start position:0% its internet is not like the fastest 00:10:48.000 --> 00:10:49.370 align:start position:0% its internet is not like the fastest thing<00:10:48.240> here 00:10:49.370 --> 00:10:49.380 align:start position:0% thing here 00:10:49.380 --> 00:10:52.970 align:start position:0% thing here but<00:10:49.980> here<00:10:50.220> is<00:10:50.459> okay<00:10:50.899> so<00:10:51.899> now<00:10:52.320> here<00:10:52.560> we<00:10:52.680> have<00:10:52.800> the 00:10:52.970 --> 00:10:52.980 align:start position:0% but here is okay so now here we have the 00:10:52.980 --> 00:10:54.889 align:start position:0% but here is okay so now here we have the smart<00:10:53.100> contract<00:10:53.519> if<00:10:53.760> we<00:10:53.880> do<00:10:54.000> a<00:10:54.120> get<00:10:54.240> a<00:10:54.480> it's<00:10:54.720> we 00:10:54.889 --> 00:10:54.899 align:start position:0% smart contract if we do a get a it's we 00:10:54.899 --> 00:10:57.110 align:start position:0% smart contract if we do a get a it's we get<00:10:55.019> a<00:10:55.140> zero<00:10:55.500> but<00:10:55.920> if<00:10:56.100> we<00:10:56.279> for<00:10:56.459> example<00:10:56.700> we<00:10:56.940> set 00:10:57.110 --> 00:10:57.120 align:start position:0% get a zero but if we for example we set 00:10:57.120 --> 00:10:59.389 align:start position:0% get a zero but if we for example we set a<00:10:57.300> 22<00:10:57.779> so<00:10:58.140> this<00:10:58.320> will<00:10:58.500> generate<00:10:58.920> a<00:10:59.040> transaction 00:10:59.389 --> 00:10:59.399 align:start position:0% a 22 so this will generate a transaction 00:10:59.399 --> 00:11:02.509 align:start position:0% a 22 so this will generate a transaction to<00:10:59.940> set<00:11:00.120> this<00:11:00.300> state<00:11:00.660> variable<00:11:00.959> to<00:11:01.140> 22<00:11:01.500> we<00:11:02.279> sign 00:11:02.509 --> 00:11:02.519 align:start position:0% to set this state variable to 22 we sign 00:11:02.519 --> 00:11:03.829 align:start position:0% to set this state variable to 22 we sign it 00:11:03.829 --> 00:11:03.839 align:start position:0% it 00:11:03.839 --> 00:11:07.490 align:start position:0% it confirm 00:11:07.490 --> 00:11:07.500 align:start position:0% 00:11:07.500 --> 00:11:09.050 align:start position:0% save 00:11:09.050 --> 00:11:09.060 align:start position:0% save 00:11:09.060 --> 00:11:15.230 align:start position:0% save there<00:11:09.600> is<00:11:09.839> and<00:11:10.620> just<00:11:10.860> get<00:11:10.980> the<00:11:11.160> value 00:11:15.230 --> 00:11:15.240 align:start position:0% 00:11:15.240 --> 00:11:18.590 align:start position:0% and<00:11:15.720> I<00:11:15.899> see<00:11:16.260> here<00:11:16.440> 22<00:11:16.980> right<00:11:17.279> here<00:11:17.519> okay<00:11:18.120> so<00:11:18.420> I 00:11:18.590 --> 00:11:18.600 align:start position:0% and I see here 22 right here okay so I 00:11:18.600 --> 00:11:21.410 align:start position:0% and I see here 22 right here okay so I just<00:11:18.720> deployed<00:11:19.200> that<00:11:19.620> in<00:11:20.160> layer<00:11:20.700> 2<00:11:20.820> like<00:11:21.120> any 00:11:21.410 --> 00:11:21.420 align:start position:0% just deployed that in layer 2 like any 00:11:21.420 --> 00:11:25.730 align:start position:0% just deployed that in layer 2 like any other<00:11:21.660> network<00:11:22.500> here<00:11:23.279> okay<00:11:23.760> so<00:11:24.600> uh<00:11:25.320> what's 00:11:25.730 --> 00:11:25.740 align:start position:0% other network here okay so uh what's 00:11:25.740 --> 00:11:27.710 align:start position:0% other network here okay so uh what's going<00:11:25.980> on<00:11:26.160> in<00:11:26.519> here<00:11:26.700> so<00:11:26.880> let's<00:11:27.000> let's<00:11:27.180> see 00:11:27.710 --> 00:11:27.720 align:start position:0% going on in here so let's let's see 00:11:27.720 --> 00:11:30.590 align:start position:0% going on in here so let's let's see let's<00:11:28.079> see<00:11:28.320> the<00:11:28.500> let's<00:11:28.980> go<00:11:29.220> to<00:11:29.339> the<00:11:29.640> let's<00:11:30.360> go 00:11:30.590 --> 00:11:30.600 align:start position:0% let's see the let's go to the let's go 00:11:30.600 --> 00:11:32.930 align:start position:0% let's see the let's go to the let's go to<00:11:30.779> the 00:11:32.930 --> 00:11:32.940 align:start position:0% to the 00:11:32.940 --> 00:11:34.550 align:start position:0% to the uh 00:11:34.550 --> 00:11:34.560 align:start position:0% uh 00:11:34.560 --> 00:11:38.150 align:start position:0% uh to<00:11:35.279> the<00:11:35.660> uh<00:11:36.660> this<00:11:37.019> is<00:11:37.140> the<00:11:37.380> roll<00:11:37.620> up<00:11:37.860> the<00:11:37.980> smart 00:11:38.150 --> 00:11:38.160 align:start position:0% to the uh this is the roll up the smart 00:11:38.160 --> 00:11:40.310 align:start position:0% to the uh this is the roll up the smart contract<00:11:38.459> in<00:11:38.700> the<00:11:38.820> layer<00:11:39.060> one<00:11:39.180> okay<00:11:39.720> and<00:11:40.200> here 00:11:40.310 --> 00:11:40.320 align:start position:0% contract in the layer one okay and here 00:11:40.320 --> 00:11:42.350 align:start position:0% contract in the layer one okay and here we<00:11:40.560> see<00:11:40.680> two<00:11:40.920> kind<00:11:41.100> of<00:11:41.220> transactions<00:11:41.760> one<00:11:42.120> are 00:11:42.350 --> 00:11:42.360 align:start position:0% we see two kind of transactions one are 00:11:42.360 --> 00:11:45.230 align:start position:0% we see two kind of transactions one are the<00:11:42.480> sequence<00:11:42.899> uh<00:11:43.560> batches<00:11:44.040> like<00:11:44.399> here<00:11:44.640> where 00:11:45.230 --> 00:11:45.240 align:start position:0% the sequence uh batches like here where 00:11:45.240 --> 00:11:47.389 align:start position:0% the sequence uh batches like here where here<00:11:45.540> you<00:11:45.660> can<00:11:45.839> see<00:11:45.959> in<00:11:46.079> the<00:11:46.260> data<00:11:46.620> that<00:11:47.160> this 00:11:47.389 --> 00:11:47.399 align:start position:0% here you can see in the data that this 00:11:47.399 --> 00:11:49.850 align:start position:0% here you can see in the data that this is<00:11:47.579> here<00:11:47.880> all<00:11:48.300> the<00:11:48.600> all<00:11:49.079> the<00:11:49.320> transactions 00:11:49.850 --> 00:11:49.860 align:start position:0% is here all the all the transactions 00:11:49.860 --> 00:11:51.650 align:start position:0% is here all the all the transactions that<00:11:50.160> we<00:11:50.279> are<00:11:50.399> setting 00:11:51.650 --> 00:11:51.660 align:start position:0% that we are setting 00:11:51.660 --> 00:11:54.350 align:start position:0% that we are setting okay<00:11:52.140> but<00:11:52.740> in<00:11:52.980> parallel 00:11:54.350 --> 00:11:54.360 align:start position:0% okay but in parallel 00:11:54.360 --> 00:11:57.590 align:start position:0% okay but in parallel but<00:11:54.779> in<00:11:54.959> parallel<00:11:55.320> to<00:11:55.440> this<00:11:55.620> we<00:11:56.339> have<00:11:56.519> the<00:11:56.880> the 00:11:57.590 --> 00:11:57.600 align:start position:0% but in parallel to this we have the the 00:11:57.600 --> 00:11:59.990 align:start position:0% but in parallel to this we have the the batch<00:11:57.839> the<00:11:58.260> batches<00:11:58.620> is<00:11:58.800> the<00:11:58.920> proverb<00:11:59.339> that's 00:11:59.990 --> 00:12:00.000 align:start position:0% batch the batches is the proverb that's 00:12:00.000 --> 00:12:01.490 align:start position:0% batch the batches is the proverb that's generating<00:12:00.540> batches<00:12:01.019> that's<00:12:01.260> actually 00:12:01.490 --> 00:12:01.500 align:start position:0% generating batches that's actually 00:12:01.500 --> 00:12:03.350 align:start position:0% generating batches that's actually validating<00:12:02.100> these<00:12:02.519> transactions<00:12:03.000> and<00:12:03.240> here 00:12:03.350 --> 00:12:03.360 align:start position:0% validating these transactions and here 00:12:03.360 --> 00:12:05.690 align:start position:0% validating these transactions and here is<00:12:03.540> where<00:12:03.720> all<00:12:03.839> the<00:12:04.019> magic<00:12:04.140> happens<00:12:04.620> okay<00:12:05.040> here 00:12:05.690 --> 00:12:05.700 align:start position:0% is where all the magic happens okay here 00:12:05.700 --> 00:12:07.009 align:start position:0% is where all the magic happens okay here in<00:12:05.880> the<00:12:06.000> blockchain<00:12:06.300> you<00:12:06.480> cannot<00:12:06.720> see<00:12:06.839> much 00:12:07.009 --> 00:12:07.019 align:start position:0% in the blockchain you cannot see much 00:12:07.019 --> 00:12:09.170 align:start position:0% in the blockchain you cannot see much but<00:12:07.320> here<00:12:07.620> is<00:12:07.740> the<00:12:07.920> proof<00:12:08.279> actually<00:12:08.760> this<00:12:09.060> is 00:12:09.170 --> 00:12:09.180 align:start position:0% but here is the proof actually this is 00:12:09.180 --> 00:12:11.329 align:start position:0% but here is the proof actually this is the<00:12:09.300> grow<00:12:09.420> 16<00:12:09.660> proof<00:12:10.140> in<00:12:10.380> this<00:12:10.500> case<00:12:10.680> that 00:12:11.329 --> 00:12:11.339 align:start position:0% the grow 16 proof in this case that 00:12:11.339 --> 00:12:14.269 align:start position:0% the grow 16 proof in this case that validates<00:12:11.880> all<00:12:12.420> the<00:12:12.540> transactions<00:12:13.140> that<00:12:13.860> we 00:12:14.269 --> 00:12:14.279 align:start position:0% validates all the transactions that we 00:12:14.279 --> 00:12:16.490 align:start position:0% validates all the transactions that we have<00:12:14.399> been<00:12:14.640> processing<00:12:15.180> processing 00:12:16.490 --> 00:12:16.500 align:start position:0% have been processing processing 00:12:16.500 --> 00:12:20.210 align:start position:0% have been processing processing ok<00:12:17.040> so<00:12:17.880> until<00:12:18.300> here<00:12:18.720> is<00:12:18.839> well<00:12:19.079> I<00:12:19.320> can<00:12:19.560> maybe<00:12:20.040> I 00:12:20.210 --> 00:12:20.220 align:start position:0% ok so until here is well I can maybe I 00:12:20.220 --> 00:12:22.970 align:start position:0% ok so until here is well I can maybe I can<00:12:20.339> give<00:12:20.459> you<00:12:20.579> a<00:12:20.760> bonus<00:12:21.120> bonus<00:12:21.959> track<00:12:22.140> here<00:12:22.440> so 00:12:22.970 --> 00:12:22.980 align:start position:0% can give you a bonus bonus track here so 00:12:22.980 --> 00:12:26.150 align:start position:0% can give you a bonus bonus track here so we<00:12:23.100> can<00:12:23.220> go<00:12:23.399> for<00:12:23.579> example<00:12:23.880> to<00:12:24.240> UNI<00:12:24.720> swap 00:12:26.150 --> 00:12:26.160 align:start position:0% we can go for example to UNI swap 00:12:26.160 --> 00:12:29.410 align:start position:0% we can go for example to UNI swap okay<00:12:26.579> this<00:12:27.300> unit<00:12:27.480> is<00:12:27.660> obviously<00:12:28.079> is<00:12:28.320> already 00:12:29.410 --> 00:12:29.420 align:start position:0% okay this unit is obviously is already 00:12:29.420 --> 00:12:32.090 align:start position:0% okay this unit is obviously is already deployed<00:12:30.420> assist<00:12:30.899> without<00:12:31.320> compelling<00:12:31.920> and 00:12:32.090 --> 00:12:32.100 align:start position:0% deployed assist without compelling and 00:12:32.100 --> 00:12:34.730 align:start position:0% deployed assist without compelling and recompiling<00:12:33.000> anything<00:12:33.120> it's<00:12:34.019> just<00:12:34.260> a<00:12:34.500> normal 00:12:34.730 --> 00:12:34.740 align:start position:0% recompiling anything it's just a normal 00:12:34.740 --> 00:12:37.130 align:start position:0% recompiling anything it's just a normal unit<00:12:35.040> swap<00:12:35.459> it's<00:12:35.700> deployed<00:12:36.180> in<00:12:36.300> Layer<00:12:36.540> Two<00:12:36.660> and 00:12:37.130 --> 00:12:37.140 align:start position:0% unit swap it's deployed in Layer Two and 00:12:37.140 --> 00:12:38.630 align:start position:0% unit swap it's deployed in Layer Two and here<00:12:37.320> we<00:12:37.440> can<00:12:37.560> do<00:12:37.680> for<00:12:37.860> example<00:12:38.100> a<00:12:38.279> transfer 00:12:38.630 --> 00:12:38.640 align:start position:0% here we can do for example a transfer 00:12:38.640 --> 00:12:40.910 align:start position:0% here we can do for example a transfer let<00:12:39.060> me<00:12:39.240> just 00:12:40.910 --> 00:12:40.920 align:start position:0% let me just 00:12:40.920 --> 00:12:44.090 align:start position:0% let me just just<00:12:41.339> change<00:12:41.760> the<00:12:42.060> account<00:12:42.480> to<00:12:43.139> the<00:12:43.740> first<00:12:43.860> one 00:12:44.090 --> 00:12:44.100 align:start position:0% just change the account to the first one 00:12:44.100 --> 00:12:46.190 align:start position:0% just change the account to the first one so<00:12:44.339> that<00:12:44.519> I<00:12:44.639> have<00:12:44.820> some<00:12:45.060> some<00:12:45.300> tokens<00:12:45.720> to<00:12:46.019> to 00:12:46.190 --> 00:12:46.200 align:start position:0% so that I have some some tokens to to 00:12:46.200 --> 00:12:47.810 align:start position:0% so that I have some some tokens to to exchange 00:12:47.810 --> 00:12:47.820 align:start position:0% exchange 00:12:47.820 --> 00:12:50.990 align:start position:0% exchange okay<00:12:48.300> and<00:12:48.660> here<00:12:49.019> I<00:12:49.620> want<00:12:49.800> to<00:12:50.040> compare<00:12:50.700> from 00:12:50.990 --> 00:12:51.000 align:start position:0% okay and here I want to compare from 00:12:51.000 --> 00:12:52.009 align:start position:0% okay and here I want to compare from Full 00:12:52.009 --> 00:12:52.019 align:start position:0% Full 00:12:52.019 --> 00:12:57.050 align:start position:0% Full to<00:12:52.380> Bar<00:12:53.100> just<00:12:53.579> a<00:12:53.700> normal<00:12:53.880> swap 00:12:57.050 --> 00:12:57.060 align:start position:0% 00:12:57.060 --> 00:12:58.550 align:start position:0% it's<00:12:57.240> fetching<00:12:57.720> the<00:12:57.779> price<00:12:57.959> and<00:12:58.200> just<00:12:58.380> doing 00:12:58.550 --> 00:12:58.560 align:start position:0% it's fetching the price and just doing 00:12:58.560 --> 00:12:59.629 align:start position:0% it's fetching the price and just doing the<00:12:58.740> swap 00:12:59.629 --> 00:12:59.639 align:start position:0% the swap 00:12:59.639 --> 00:13:00.970 align:start position:0% the swap The<00:12:59.820> Firm<00:13:00.120> swap 00:13:00.970 --> 00:13:00.980 align:start position:0% The Firm swap 00:13:00.980 --> 00:13:03.829 align:start position:0% The Firm swap I<00:13:01.980> should<00:13:02.100> sign<00:13:02.279> the<00:13:02.519> transaction 00:13:03.829 --> 00:13:03.839 align:start position:0% I should sign the transaction 00:13:03.839 --> 00:13:06.829 align:start position:0% I should sign the transaction so<00:13:04.260> here<00:13:04.440> we<00:13:04.680> have<00:13:04.860> uh<00:13:05.519> deploy<00:13:05.880> it<00:13:06.120> so<00:13:06.420> we<00:13:06.600> here 00:13:06.829 --> 00:13:06.839 align:start position:0% so here we have uh deploy it so we here 00:13:06.839 --> 00:13:08.810 align:start position:0% so here we have uh deploy it so we here we<00:13:07.019> have<00:13:07.139> already<00:13:07.320> deployed<00:13:07.920> the<00:13:08.279> full<00:13:08.399> uni 00:13:08.810 --> 00:13:08.820 align:start position:0% we have already deployed the full uni 00:13:08.820 --> 00:13:11.389 align:start position:0% we have already deployed the full uni swap<00:13:09.060> but<00:13:09.240> version<00:13:09.480> 3<00:13:09.839> in<00:13:10.440> the<00:13:10.560> layer<00:13:10.800> two<00:13:10.980> and 00:13:11.389 --> 00:13:11.399 align:start position:0% swap but version 3 in the layer two and 00:13:11.399 --> 00:13:13.730 align:start position:0% swap but version 3 in the layer two and all<00:13:11.579> this<00:13:11.760> is<00:13:11.880> verified<00:13:12.240> in<00:13:12.839> the<00:13:12.959> program<00:13:13.320> just 00:13:13.730 --> 00:13:13.740 align:start position:0% all this is verified in the program just 00:13:13.740 --> 00:13:16.190 align:start position:0% all this is verified in the program just confirm<00:13:14.100> that<00:13:14.339> okay<00:13:14.940> now<00:13:15.240> this<00:13:15.540> is<00:13:15.660> confirmed 00:13:16.190 --> 00:13:16.200 align:start position:0% confirm that okay now this is confirmed 00:13:16.200 --> 00:13:19.250 align:start position:0% confirm that okay now this is confirmed now<00:13:16.980> here<00:13:17.519> the<00:13:17.880> the<00:13:18.060> unit<00:13:18.300> swap<00:13:18.660> interface<00:13:19.019> has 00:13:19.250 --> 00:13:19.260 align:start position:0% now here the the unit swap interface has 00:13:19.260 --> 00:13:22.009 align:start position:0% now here the the unit swap interface has some<00:13:19.620> uh<00:13:20.459> it's<00:13:20.700> iterating<00:13:21.120> takes<00:13:21.540> maybe<00:13:21.720> some 00:13:22.009 --> 00:13:22.019 align:start position:0% some uh it's iterating takes maybe some 00:13:22.019 --> 00:13:25.430 align:start position:0% some uh it's iterating takes maybe some 10<00:13:22.200> seconds<00:13:22.440> or<00:13:22.800> so<00:13:22.980> to<00:13:23.220> to<00:13:24.019> realize<00:13:25.019> that<00:13:25.320> the 00:13:25.430 --> 00:13:25.440 align:start position:0% 10 seconds or so to to realize that the 00:13:25.440 --> 00:13:29.290 align:start position:0% 10 seconds or so to to realize that the transaction<00:13:25.800> has<00:13:26.579> been<00:13:26.760> moved 00:13:29.290 --> 00:13:29.300 align:start position:0% 00:13:29.300 --> 00:13:32.990 align:start position:0% but<00:13:30.300> that's<00:13:30.600> mainly<00:13:31.260> the<00:13:31.380> thing<00:13:31.560> okay<00:13:32.279> so<00:13:32.820> let 00:13:32.990 --> 00:13:33.000 align:start position:0% but that's mainly the thing okay so let 00:13:33.000 --> 00:13:34.670 align:start position:0% but that's mainly the thing okay so let me<00:13:33.120> go<00:13:33.420> well<00:13:33.839> just<00:13:34.079> let<00:13:34.200> me<00:13:34.320> see<00:13:34.440> if<00:13:34.500> it 00:13:34.670 --> 00:13:34.680 align:start position:0% me go well just let me see if it 00:13:34.680 --> 00:13:37.329 align:start position:0% me go well just let me see if it finished<00:13:34.860> this 00:13:37.329 --> 00:13:37.339 align:start position:0% 00:13:37.339 --> 00:13:40.370 align:start position:0% okay<00:13:38.339> so<00:13:38.760> I<00:13:38.940> already<00:13:39.060> do<00:13:39.480> the<00:13:39.720> swap<00:13:39.959> so<00:13:40.139> I<00:13:40.320> can 00:13:40.370 --> 00:13:40.380 align:start position:0% okay so I already do the swap so I can 00:13:40.380 --> 00:13:42.050 align:start position:0% okay so I already do the swap so I can just<00:13:40.560> checking<00:13:40.920> in<00:13:41.100> swap<00:13:41.339> just<00:13:41.519> like<00:13:41.760> normal 00:13:42.050 --> 00:13:42.060 align:start position:0% just checking in swap just like normal 00:13:42.060 --> 00:13:44.930 align:start position:0% just checking in swap just like normal like<00:13:42.720> any<00:13:42.959> other<00:13:43.200> uh<00:13:44.160> ethernet<00:13:44.579> transaction 00:13:44.930 --> 00:13:44.940 align:start position:0% like any other uh ethernet transaction 00:13:44.940 --> 00:13:46.850 align:start position:0% like any other uh ethernet transaction so<00:13:45.240> let<00:13:45.420> me<00:13:45.600> switch<00:13:46.139> back<00:13:46.440> to<00:13:46.740> the 00:13:46.850 --> 00:13:46.860 align:start position:0% so let me switch back to the 00:13:46.860 --> 00:13:50.449 align:start position:0% so let me switch back to the presentation 00:13:50.449 --> 00:13:50.459 align:start position:0% 00:13:50.459 --> 00:13:53.629 align:start position:0% so 00:13:53.629 --> 00:13:53.639 align:start position:0% 00:13:53.639 --> 00:13:57.290 align:start position:0% nothing<00:13:54.060> fancy<00:13:54.540> right 00:13:57.290 --> 00:13:57.300 align:start position:0% 00:13:57.300 --> 00:13:59.269 align:start position:0% that's<00:13:57.720> the<00:13:57.899> cool<00:13:58.019> thing<00:13:58.320> and<00:13:58.860> that's<00:13:59.040> like 00:13:59.269 --> 00:13:59.279 align:start position:0% that's the cool thing and that's like 00:13:59.279 --> 00:14:00.949 align:start position:0% that's the cool thing and that's like strange<00:13:59.639> things<00:13:59.820> even<00:14:00.060> for<00:14:00.360> me<00:14:00.480> explaining 00:14:00.949 --> 00:14:00.959 align:start position:0% strange things even for me explaining 00:14:00.959 --> 00:14:03.829 align:start position:0% strange things even for me explaining for<00:14:01.560> me<00:14:01.620> here<00:14:02.399> I'm<00:14:02.700> just<00:14:02.940> feeling<00:14:03.240> that<00:14:03.540> I<00:14:03.720> did 00:14:03.829 --> 00:14:03.839 align:start position:0% for me here I'm just feeling that I did 00:14:03.839 --> 00:14:06.410 align:start position:0% for me here I'm just feeling that I did a<00:14:04.019> demo<00:14:04.320> of<00:14:04.500> ethereum<00:14:05.459> but<00:14:06.000> this<00:14:06.180> is<00:14:06.300> the 00:14:06.410 --> 00:14:06.420 align:start position:0% a demo of ethereum but this is the 00:14:06.420 --> 00:14:09.110 align:start position:0% a demo of ethereum but this is the interesting<00:14:06.839> thing<00:14:07.139> it's<00:14:08.100> that<00:14:08.459> the<00:14:08.760> all<00:14:08.880> this 00:14:09.110 --> 00:14:09.120 align:start position:0% interesting thing it's that the all this 00:14:09.120 --> 00:14:11.090 align:start position:0% interesting thing it's that the all this is<00:14:09.300> running<00:14:09.540> all<00:14:10.079> this<00:14:10.320> is<00:14:10.380> validated<00:14:10.800> in<00:14:10.980> the 00:14:11.090 --> 00:14:11.100 align:start position:0% is running all this is validated in the 00:14:11.100 --> 00:14:13.730 align:start position:0% is running all this is validated in the Brewer<00:14:11.519> all<00:14:11.940> these<00:14:12.120> transactions<00:14:12.660> that<00:14:13.440> are 00:14:13.730 --> 00:14:13.740 align:start position:0% Brewer all these transactions that are 00:14:13.740 --> 00:14:15.949 align:start position:0% Brewer all these transactions that are really<00:14:14.160> complex<00:14:14.459> or<00:14:15.060> all<00:14:15.300> the<00:14:15.420> unit<00:14:15.540> swap 00:14:15.949 --> 00:14:15.959 align:start position:0% really complex or all the unit swap 00:14:15.959 --> 00:14:17.690 align:start position:0% really complex or all the unit swap transactions<00:14:16.800> and<00:14:17.040> everything<00:14:17.160> this<00:14:17.519> is 00:14:17.690 --> 00:14:17.700 align:start position:0% transactions and everything this is 00:14:17.700 --> 00:14:20.629 align:start position:0% transactions and everything this is validated<00:14:18.180> uh<00:14:19.019> inside<00:14:19.200> the<00:14:19.440> broker<00:14:19.860> and<00:14:20.459> this 00:14:20.629 --> 00:14:20.639 align:start position:0% validated uh inside the broker and this 00:14:20.639 --> 00:14:23.269 align:start position:0% validated uh inside the broker and this is<00:14:20.760> what<00:14:21.000> this<00:14:21.420> zkbm<00:14:22.320> and<00:14:22.860> the<00:14:23.040> main 00:14:23.269 --> 00:14:23.279 align:start position:0% is what this zkbm and the main 00:14:23.279 --> 00:14:25.370 align:start position:0% is what this zkbm and the main importance<00:14:23.880> of<00:14:24.060> this<00:14:24.240> design<00:14:24.480> you<00:14:25.079> don't<00:14:25.200> have 00:14:25.370 --> 00:14:25.380 align:start position:0% importance of this design you don't have 00:14:25.380 --> 00:14:27.530 align:start position:0% importance of this design you don't have to<00:14:25.500> recompile<00:14:26.040> anything<00:14:26.459> you<00:14:27.060> just<00:14:27.240> take<00:14:27.420> the 00:14:27.530 --> 00:14:27.540 align:start position:0% to recompile anything you just take the 00:14:27.540 --> 00:14:29.030 align:start position:0% to recompile anything you just take the code<00:14:27.720> exactly<00:14:28.260> the<00:14:28.380> same<00:14:28.500> code<00:14:28.680> you<00:14:28.920> don't 00:14:29.030 --> 00:14:29.040 align:start position:0% code exactly the same code you don't 00:14:29.040 --> 00:14:30.889 align:start position:0% code exactly the same code you don't have<00:14:29.160> to<00:14:29.279> reality<00:14:29.760> anything<00:14:30.000> you<00:14:30.600> don't<00:14:30.720> have 00:14:30.889 --> 00:14:30.899 align:start position:0% have to reality anything you don't have 00:14:30.899 --> 00:14:32.990 align:start position:0% have to reality anything you don't have to<00:14:31.019> learn<00:14:31.260> anything<00:14:31.500> you<00:14:31.980> can<00:14:32.100> use<00:14:32.579> exactly 00:14:32.990 --> 00:14:33.000 align:start position:0% to learn anything you can use exactly 00:14:33.000 --> 00:14:35.509 align:start position:0% to learn anything you can use exactly the<00:14:33.300> same<00:14:33.480> tooling<00:14:33.899> you<00:14:34.320> can<00:14:34.440> use<00:14:34.740> the<00:14:35.339> same 00:14:35.509 --> 00:14:35.519 align:start position:0% the same tooling you can use the same 00:14:35.519 --> 00:14:37.670 align:start position:0% the same tooling you can use the same the<00:14:36.000> same<00:14:36.180> language<00:14:36.420> the<00:14:37.079> same<00:14:37.200> gas<00:14:37.380> model 00:14:37.670 --> 00:14:37.680 align:start position:0% the same language the same gas model 00:14:37.680 --> 00:14:41.090 align:start position:0% the same language the same gas model it's<00:14:38.639> no<00:14:38.940> difference<00:14:39.180> for<00:14:40.019> developers<00:14:40.500> they 00:14:41.090 --> 00:14:41.100 align:start position:0% it's no difference for developers they 00:14:41.100 --> 00:14:43.870 align:start position:0% it's no difference for developers they should<00:14:41.279> not<00:14:41.519> notice<00:14:42.000> any<00:14:42.420> difference<00:14:42.860> in 00:14:43.870 --> 00:14:43.880 align:start position:0% should not notice any difference in 00:14:43.880 --> 00:14:47.449 align:start position:0% should not notice any difference in deploying<00:14:44.880> in<00:14:45.180> working<00:14:45.480> with<00:14:45.959> ethereum<00:14:46.560> or<00:14:47.100> in 00:14:47.449 --> 00:14:47.459 align:start position:0% deploying in working with ethereum or in 00:14:47.459 --> 00:14:50.030 align:start position:0% deploying in working with ethereum or in uh<00:14:48.060> or<00:14:48.360> in<00:14:48.480> the<00:14:48.600> KVM<00:14:49.139> the<00:14:49.620> only<00:14:49.740> difference 00:14:50.030 --> 00:14:50.040 align:start position:0% uh or in the KVM the only difference 00:14:50.040 --> 00:14:52.370 align:start position:0% uh or in the KVM the only difference should<00:14:50.699> be<00:14:50.820> the<00:14:51.000> gas<00:14:51.180> price<00:14:51.480> and<00:14:51.959> the<00:14:52.079> quantity 00:14:52.370 --> 00:14:52.380 align:start position:0% should be the gas price and the quantity 00:14:52.380 --> 00:14:54.050 align:start position:0% should be the gas price and the quantity of<00:14:52.560> transactions<00:14:53.160> that<00:14:53.519> you<00:14:53.699> should<00:14:53.820> be<00:14:53.940> able 00:14:54.050 --> 00:14:54.060 align:start position:0% of transactions that you should be able 00:14:54.060 --> 00:14:55.250 align:start position:0% of transactions that you should be able to<00:14:54.240> deploy 00:14:55.250 --> 00:14:55.260 align:start position:0% to deploy 00:14:55.260 --> 00:14:58.550 align:start position:0% to deploy this<00:14:55.740> is<00:14:55.920> a<00:14:56.040> test<00:14:56.160> net<00:14:56.399> please<00:14:57.060> test<00:14:57.420> it<00:14:58.079> we 00:14:58.550 --> 00:14:58.560 align:start position:0% this is a test net please test it we 00:14:58.560 --> 00:15:00.410 align:start position:0% this is a test net please test it we have<00:14:58.680> been<00:14:58.860> running<00:14:59.100> for<00:14:59.699> this<00:14:59.940> week<00:15:00.180> already 00:15:00.410 --> 00:15:00.420 align:start position:0% have been running for this week already 00:15:00.420 --> 00:15:03.769 align:start position:0% have been running for this week already we<00:15:00.899> have<00:15:01.079> more<00:15:01.380> than<00:15:01.560> 1<00:15:02.339> 000<00:15:02.399> accounts<00:15:02.940> we<00:15:03.600> have 00:15:03.769 --> 00:15:03.779 align:start position:0% we have more than 1 000 accounts we have 00:15:03.779 --> 00:15:06.470 align:start position:0% we have more than 1 000 accounts we have most<00:15:04.199> of<00:15:04.380> them<00:15:04.500> are<00:15:04.980> just<00:15:05.220> deploying<00:15:05.760> uh 00:15:06.470 --> 00:15:06.480 align:start position:0% most of them are just deploying uh 00:15:06.480 --> 00:15:08.269 align:start position:0% most of them are just deploying uh transactions<00:15:07.079> some<00:15:07.620> of<00:15:07.740> the<00:15:07.860> projects 00:15:08.269 --> 00:15:08.279 align:start position:0% transactions some of the projects 00:15:08.279 --> 00:15:11.949 align:start position:0% transactions some of the projects already<00:15:08.459> tested<00:15:09.060> uh<00:15:09.959> already<00:15:10.199> tested<00:15:10.800> without 00:15:11.949 --> 00:15:11.959 align:start position:0% already tested uh already tested without 00:15:11.959 --> 00:15:15.710 align:start position:0% already tested uh already tested without any<00:15:12.959> big<00:15:13.260> issue<00:15:13.620> we<00:15:13.800> have<00:15:14.240> some<00:15:15.240> reports<00:15:15.600> of 00:15:15.710 --> 00:15:15.720 align:start position:0% any big issue we have some reports of 00:15:15.720 --> 00:15:17.930 align:start position:0% any big issue we have some reports of some<00:15:15.899> bugs<00:15:16.199> that<00:15:16.320> we<00:15:16.440> haven't<00:15:16.620> fixed<00:15:16.980> also<00:15:17.459> and 00:15:17.930 --> 00:15:17.940 align:start position:0% some bugs that we haven't fixed also and 00:15:17.940 --> 00:15:20.269 align:start position:0% some bugs that we haven't fixed also and we<00:15:18.120> will<00:15:18.240> continue<00:15:18.600> work<00:15:18.959> it's<00:15:19.560> this<00:15:19.800> testnet 00:15:20.269 --> 00:15:20.279 align:start position:0% we will continue work it's this testnet 00:15:20.279 --> 00:15:22.629 align:start position:0% we will continue work it's this testnet is<00:15:20.399> a<00:15:20.519> little<00:15:20.579> bit<00:15:20.760> like<00:15:20.940> a<00:15:21.120> baby<00:15:21.240> it<00:15:21.600> was<00:15:21.720> worn 00:15:22.629 --> 00:15:22.639 align:start position:0% is a little bit like a baby it was worn 00:15:22.639 --> 00:15:26.509 align:start position:0% is a little bit like a baby it was worn last<00:15:23.639> Monday<00:15:24.019> but<00:15:25.019> uh<00:15:25.620> it's<00:15:26.160> gonna<00:15:26.279> get 00:15:26.509 --> 00:15:26.519 align:start position:0% last Monday but uh it's gonna get 00:15:26.519 --> 00:15:30.170 align:start position:0% last Monday but uh it's gonna get stronger<00:15:27.019> and<00:15:28.019> this<00:15:28.620> is<00:15:28.740> the<00:15:29.220> the<00:15:29.820> previous 00:15:30.170 --> 00:15:30.180 align:start position:0% stronger and this is the the previous 00:15:30.180 --> 00:15:32.509 align:start position:0% stronger and this is the the previous stage<00:15:30.660> just<00:15:31.019> to<00:15:31.199> the<00:15:31.380> to<00:15:31.560> the<00:15:31.800> to<00:15:31.980> the<00:15:32.160> main<00:15:32.279> net 00:15:32.509 --> 00:15:32.519 align:start position:0% stage just to the to the to the main net 00:15:32.519 --> 00:15:35.930 align:start position:0% stage just to the to the to the main net okay<00:15:33.300> here<00:15:34.139> is<00:15:34.380> uh<00:15:34.860> okay<00:15:35.279> and<00:15:35.519> what's<00:15:35.699> the 00:15:35.930 --> 00:15:35.940 align:start position:0% okay here is uh okay and what's the 00:15:35.940 --> 00:15:39.050 align:start position:0% okay here is uh okay and what's the limit<00:15:36.060> of<00:15:36.660> the<00:15:36.839> scaling<00:15:37.260> list 00:15:39.050 --> 00:15:39.060 align:start position:0% limit of the scaling list 00:15:39.060 --> 00:15:41.329 align:start position:0% limit of the scaling list we<00:15:39.899> don't<00:15:40.079> know<00:15:40.199> yet<00:15:40.380> what's<00:15:40.740> clear<00:15:40.980> is<00:15:41.220> not 00:15:41.329 --> 00:15:41.339 align:start position:0% we don't know yet what's clear is not 00:15:41.339 --> 00:15:42.949 align:start position:0% we don't know yet what's clear is not gonna<00:15:41.459> it's<00:15:41.699> not<00:15:41.820> gonna<00:15:41.940> be<00:15:42.120> in<00:15:42.240> the<00:15:42.360> proverb 00:15:42.949 --> 00:15:42.959 align:start position:0% gonna it's not gonna be in the proverb 00:15:42.959 --> 00:15:44.030 align:start position:0% gonna it's not gonna be in the proverb it's<00:15:43.139> going<00:15:43.320> to<00:15:43.380> be<00:15:43.500> maybe<00:15:43.620> not<00:15:43.860> that 00:15:44.030 --> 00:15:44.040 align:start position:0% it's going to be maybe not that 00:15:44.040 --> 00:15:45.889 align:start position:0% it's going to be maybe not that availability<00:15:44.399> it's<00:15:44.880> going<00:15:45.120> to<00:15:45.300> be<00:15:45.420> in<00:15:45.600> the 00:15:45.889 --> 00:15:45.899 align:start position:0% availability it's going to be in the 00:15:45.899 --> 00:15:48.110 align:start position:0% availability it's going to be in the maybe<00:15:46.320> in<00:15:46.500> the<00:15:46.620> sequencer<00:15:47.160> in<00:15:47.820> the<00:15:48.000> other 00:15:48.110 --> 00:15:48.120 align:start position:0% maybe in the sequencer in the other 00:15:48.120 --> 00:15:50.090 align:start position:0% maybe in the sequencer in the other pieces<00:15:48.540> but<00:15:48.899> because<00:15:49.199> why<00:15:49.620> because<00:15:49.920> the 00:15:50.090 --> 00:15:50.100 align:start position:0% pieces but because why because the 00:15:50.100 --> 00:15:52.370 align:start position:0% pieces but because why because the proverb<00:15:50.459> can<00:15:50.579> be<00:15:50.699> parallelized<00:15:51.360> and<00:15:52.019> here<00:15:52.199> the 00:15:52.370 --> 00:15:52.380 align:start position:0% proverb can be parallelized and here the 00:15:52.380 --> 00:15:54.230 align:start position:0% proverb can be parallelized and here the important<00:15:52.740> part<00:15:52.920> actually<00:15:53.459> for<00:15:53.820> example<00:15:54.000> we 00:15:54.230 --> 00:15:54.240 align:start position:0% important part actually for example we 00:15:54.240 --> 00:15:57.410 align:start position:0% important part actually for example we are<00:15:54.360> running<00:15:54.740> uh<00:15:55.740> seven<00:15:56.040> Brewers<00:15:56.699> at<00:15:57.300> this 00:15:57.410 --> 00:15:57.420 align:start position:0% are running uh seven Brewers at this 00:15:57.420 --> 00:15:59.030 align:start position:0% are running uh seven Brewers at this point<00:15:57.540> because<00:15:57.899> this<00:15:58.260> week<00:15:58.440> you<00:15:58.740> know<00:15:58.920> there 00:15:59.030 --> 00:15:59.040 align:start position:0% point because this week you know there 00:15:59.040 --> 00:16:00.170 align:start position:0% point because this week you know there is<00:15:59.160> main<00:15:59.279> transactions<00:15:59.880> some<00:16:00.000> of<00:16:00.060> the 00:16:00.170 --> 00:16:00.180 align:start position:0% is main transactions some of the 00:16:00.180 --> 00:16:01.730 align:start position:0% is main transactions some of the products<00:16:00.480> have<00:16:00.600> been<00:16:00.720> stopped<00:16:01.199> so<00:16:01.440> we<00:16:01.560> are 00:16:01.730 --> 00:16:01.740 align:start position:0% products have been stopped so we are 00:16:01.740 --> 00:16:03.410 align:start position:0% products have been stopped so we are just<00:16:01.860> just<00:16:02.100> trying<00:16:02.339> to<00:16:02.519> catch<00:16:02.820> up<00:16:02.940> with<00:16:03.300> the 00:16:03.410 --> 00:16:03.420 align:start position:0% just just trying to catch up with the 00:16:03.420 --> 00:16:05.389 align:start position:0% just just trying to catch up with the trend<00:16:03.660> with<00:16:04.019> some<00:16:04.139> of<00:16:04.199> these<00:16:04.380> transactions 00:16:05.389 --> 00:16:05.399 align:start position:0% trend with some of these transactions 00:16:05.399 --> 00:16:07.310 align:start position:0% trend with some of these transactions but<00:16:05.880> this<00:16:06.060> is<00:16:06.180> the<00:16:06.300> cool<00:16:06.420> thing<00:16:06.600> we<00:16:06.959> can<00:16:07.079> run<00:16:07.199> as 00:16:07.310 --> 00:16:07.320 align:start position:0% but this is the cool thing we can run as 00:16:07.320 --> 00:16:09.290 align:start position:0% but this is the cool thing we can run as many<00:16:07.500> Proverbs<00:16:07.920> as<00:16:07.980> we<00:16:08.160> want<00:16:08.279> so<00:16:08.880> if<00:16:09.000> there<00:16:09.120> is 00:16:09.290 --> 00:16:09.300 align:start position:0% many Proverbs as we want so if there is 00:16:09.300 --> 00:16:10.790 align:start position:0% many Proverbs as we want so if there is a<00:16:09.420> lot<00:16:09.480> of<00:16:09.600> demand<00:16:09.959> we're<00:16:10.260> just<00:16:10.440> running<00:16:10.620> more 00:16:10.790 --> 00:16:10.800 align:start position:0% a lot of demand we're just running more 00:16:10.800 --> 00:16:13.250 align:start position:0% a lot of demand we're just running more Brewers<00:16:11.300> and<00:16:12.300> the<00:16:12.660> only<00:16:12.779> thing<00:16:12.899> you<00:16:13.019> need<00:16:13.199> to 00:16:13.250 --> 00:16:13.260 align:start position:0% Brewers and the only thing you need to 00:16:13.260 --> 00:16:14.569 align:start position:0% Brewers and the only thing you need to take<00:16:13.380> in<00:16:13.560> account<00:16:13.680> is<00:16:13.920> what's<00:16:14.100> a<00:16:14.279> cost<00:16:14.459> per 00:16:14.569 --> 00:16:14.579 align:start position:0% take in account is what's a cost per 00:16:14.579 --> 00:16:15.949 align:start position:0% take in account is what's a cost per transaction<00:16:14.940> because<00:16:15.360> running<00:16:15.600> these 00:16:15.949 --> 00:16:15.959 align:start position:0% transaction because running these 00:16:15.959 --> 00:16:18.769 align:start position:0% transaction because running these servers<00:16:16.260> are<00:16:16.440> not<00:16:16.620> free<00:16:16.860> so<00:16:17.820> what's<00:16:18.300> it<00:16:18.540> what's 00:16:18.769 --> 00:16:18.779 align:start position:0% servers are not free so what's it what's 00:16:18.779 --> 00:16:21.829 align:start position:0% servers are not free so what's it what's this<00:16:18.959> cost<00:16:19.139> well<00:16:19.620> the<00:16:20.160> cost<00:16:20.579> right<00:16:20.940> now<00:16:21.180> is 00:16:21.829 --> 00:16:21.839 align:start position:0% this cost well the cost right now is 00:16:21.839 --> 00:16:24.350 align:start position:0% this cost well the cost right now is less<00:16:22.079> than<00:16:22.260> one<00:16:22.440> cent<00:16:22.680> per<00:16:23.100> transaction 00:16:24.350 --> 00:16:24.360 align:start position:0% less than one cent per transaction 00:16:24.360 --> 00:16:27.769 align:start position:0% less than one cent per transaction and<00:16:25.139> there<00:16:25.500> is<00:16:25.680> this<00:16:26.100> is<00:16:26.279> in<00:16:26.459> AWS<00:16:27.180> cost<00:16:27.420> which 00:16:27.769 --> 00:16:27.779 align:start position:0% and there is this is in AWS cost which 00:16:27.779 --> 00:16:30.050 align:start position:0% and there is this is in AWS cost which is<00:16:27.839> probably<00:16:28.079> the<00:16:28.380> the<00:16:28.740> most<00:16:28.980> expensive<00:16:29.519> cloud 00:16:30.050 --> 00:16:30.060 align:start position:0% is probably the the most expensive cloud 00:16:30.060 --> 00:16:32.930 align:start position:0% is probably the the most expensive cloud service<00:16:30.300> in<00:16:30.660> the<00:16:30.899> in<00:16:31.620> the<00:16:31.800> in<00:16:31.980> the<00:16:32.160> in<00:16:32.339> the 00:16:32.930 --> 00:16:32.940 align:start position:0% service in the in the in the in the 00:16:32.940 --> 00:16:35.389 align:start position:0% service in the in the in the in the world<00:16:33.000> and<00:16:33.959> there<00:16:34.380> is<00:16:34.560> also<00:16:34.980> a<00:16:35.160> lot<00:16:35.279> of 00:16:35.389 --> 00:16:35.399 align:start position:0% world and there is also a lot of 00:16:35.399 --> 00:16:37.249 align:start position:0% world and there is also a lot of optimizations<00:16:36.000> that<00:16:36.420> are<00:16:36.540> coming 00:16:37.249 --> 00:16:37.259 align:start position:0% optimizations that are coming 00:16:37.259 --> 00:16:39.710 align:start position:0% optimizations that are coming here<00:16:37.620> in<00:16:37.920> GPU<00:16:38.339> we<00:16:38.699> can<00:16:38.820> we<00:16:39.120> believe<00:16:39.300> that<00:16:39.600> we 00:16:39.710 --> 00:16:39.720 align:start position:0% here in GPU we can we believe that we 00:16:39.720 --> 00:16:41.389 align:start position:0% here in GPU we can we believe that we can<00:16:39.839> improve<00:16:40.139> one<00:16:40.320> order<00:16:40.500> of<00:16:40.740> magnitude<00:16:41.160> and 00:16:41.389 --> 00:16:41.399 align:start position:0% can improve one order of magnitude and 00:16:41.399 --> 00:16:43.249 align:start position:0% can improve one order of magnitude and there<00:16:41.579> is<00:16:41.759> other<00:16:42.060> improvements<00:16:42.779> that<00:16:42.959> we<00:16:43.139> are 00:16:43.249 --> 00:16:43.259 align:start position:0% there is other improvements that we are 00:16:43.259 --> 00:16:45.949 align:start position:0% there is other improvements that we are working<00:16:43.500> on<00:16:44.339> that<00:16:44.519> but 00:16:45.949 --> 00:16:45.959 align:start position:0% working on that but 00:16:45.959 --> 00:16:49.910 align:start position:0% working on that but proverb<00:16:46.680> is<00:16:47.100> not<00:16:47.339> the<00:16:48.240> is<00:16:48.600> not<00:16:48.959> the<00:16:49.620> the 00:16:49.910 --> 00:16:49.920 align:start position:0% proverb is not the is not the the 00:16:49.920 --> 00:16:52.490 align:start position:0% proverb is not the is not the the bottleneck<00:16:50.579> anymore 00:16:52.490 --> 00:16:52.500 align:start position:0% bottleneck anymore 00:16:52.500 --> 00:16:55.310 align:start position:0% bottleneck anymore what's<00:16:53.040> missing<00:16:53.459> well 00:16:55.310 --> 00:16:55.320 align:start position:0% what's missing well 00:16:55.320 --> 00:16:57.290 align:start position:0% what's missing well not<00:16:55.920> much 00:16:57.290 --> 00:16:57.300 align:start position:0% not much 00:16:57.300 --> 00:16:59.810 align:start position:0% not much so<00:16:58.019> we<00:16:58.500> are<00:16:58.680> fully<00:16:58.980> compatible<00:16:59.339> we<00:16:59.699> are 00:16:59.810 --> 00:16:59.820 align:start position:0% so we are fully compatible we are 00:16:59.820 --> 00:17:02.210 align:start position:0% so we are fully compatible we are running<00:17:00.120> all<00:17:00.420> the<00:17:00.660> all<00:17:00.899> the<00:17:01.199> all<00:17:01.740> the<00:17:01.980> off 00:17:02.210 --> 00:17:02.220 align:start position:0% running all the all the all the off 00:17:02.220 --> 00:17:05.210 align:start position:0% running all the all the all the off codes<00:17:02.459> everything<00:17:03.240> works<00:17:03.720> as<00:17:03.779> as<00:17:04.140> ethereum<00:17:04.980> is 00:17:05.210 --> 00:17:05.220 align:start position:0% codes everything works as as ethereum is 00:17:05.220 --> 00:17:06.710 align:start position:0% codes everything works as as ethereum is there<00:17:05.760> are<00:17:05.880> some<00:17:06.059> things<00:17:06.240> that<00:17:06.480> we<00:17:06.600> are 00:17:06.710 --> 00:17:06.720 align:start position:0% there are some things that we are 00:17:06.720 --> 00:17:08.090 align:start position:0% there are some things that we are already<00:17:06.839> implementing<00:17:07.439> they<00:17:07.799> are<00:17:07.980> not 00:17:08.090 --> 00:17:08.100 align:start position:0% already implementing they are not 00:17:08.100 --> 00:17:09.890 align:start position:0% already implementing they are not implemented<00:17:08.520> yet<00:17:08.760> and<00:17:09.179> I'm<00:17:09.299> just<00:17:09.540> listening 00:17:09.890 --> 00:17:09.900 align:start position:0% implemented yet and I'm just listening 00:17:09.900 --> 00:17:12.110 align:start position:0% implemented yet and I'm just listening here<00:17:10.020> but<00:17:10.740> everything<00:17:11.040> is<00:17:11.339> there<00:17:11.520> what<00:17:11.939> is 00:17:12.110 --> 00:17:12.120 align:start position:0% here but everything is there what is 00:17:12.120 --> 00:17:15.110 align:start position:0% here but everything is there what is missing<00:17:12.540> is<00:17:13.140> that<00:17:13.520> AIP<00:17:14.520> is<00:17:14.819> the<00:17:14.939> original 00:17:15.110 --> 00:17:15.120 align:start position:0% missing is that AIP is the original 00:17:15.120 --> 00:17:17.929 align:start position:0% missing is that AIP is the original ethereum<00:17:15.959> transactions<00:17:16.919> this<00:17:17.280> is<00:17:17.400> mainly<00:17:17.699> to 00:17:17.929 --> 00:17:17.939 align:start position:0% ethereum transactions this is mainly to 00:17:17.939 --> 00:17:21.230 align:start position:0% ethereum transactions this is mainly to deploy<00:17:18.419> mainly<00:17:19.260> not<00:17:19.380> safe<00:17:19.740> but<00:17:20.100> it's<00:17:20.459> uh<00:17:20.699> just 00:17:21.230 --> 00:17:21.240 align:start position:0% deploy mainly not safe but it's uh just 00:17:21.240 --> 00:17:23.329 align:start position:0% deploy mainly not safe but it's uh just for<00:17:21.419> for<00:17:21.720> distance<00:17:21.959> these<00:17:22.679> smart<00:17:22.860> contracts 00:17:23.329 --> 00:17:23.339 align:start position:0% for for distance these smart contracts 00:17:23.339 --> 00:17:26.210 align:start position:0% for for distance these smart contracts that<00:17:23.520> have<00:17:23.640> the<00:17:23.880> same<00:17:24.000> address<00:17:24.240> in<00:17:25.199> many<00:17:25.380> in<00:17:26.220> in 00:17:26.210 --> 00:17:26.220 align:start position:0% that have the same address in many in in 00:17:26.220 --> 00:17:28.909 align:start position:0% that have the same address in many in in in<00:17:26.459> in<00:17:26.579> many<00:17:27.179> chains<00:17:27.839> they<00:17:28.380> use<00:17:28.500> they<00:17:28.799> are 00:17:28.909 --> 00:17:28.919 align:start position:0% in in many chains they use they are 00:17:28.919 --> 00:17:30.590 align:start position:0% in in many chains they use they are using<00:17:29.100> these<00:17:29.400> primitive<00:17:29.760> transactions<00:17:30.419> that 00:17:30.590 --> 00:17:30.600 align:start position:0% using these primitive transactions that 00:17:30.600 --> 00:17:32.150 align:start position:0% using these primitive transactions that they<00:17:30.720> don't<00:17:30.900> include<00:17:31.140> the<00:17:31.260> chain<00:17:31.440> AV<00:17:31.679> we<00:17:31.980> are 00:17:32.150 --> 00:17:32.160 align:start position:0% they don't include the chain AV we are 00:17:32.160 --> 00:17:34.549 align:start position:0% they don't include the chain AV we are implementing<00:17:32.580> those<00:17:32.760> and<00:17:33.480> then<00:17:33.660> the<00:17:34.080> we<00:17:34.380> are 00:17:34.549 --> 00:17:34.559 align:start position:0% implementing those and then the we are 00:17:34.559 --> 00:17:36.830 align:start position:0% implementing those and then the we are not<00:17:34.620> supporting<00:17:35.100> yet<00:17:35.400> the<00:17:35.700> shadow<00:17:36.120> 56<00:17:36.539> the 00:17:36.830 --> 00:17:36.840 align:start position:0% not supporting yet the shadow 56 the 00:17:36.840 --> 00:17:38.810 align:start position:0% not supporting yet the shadow 56 the Blake<00:17:37.140> and<00:17:37.320> the<00:17:37.500> paintings<00:17:37.919> pre-compile<00:17:38.760> to 00:17:38.810 --> 00:17:38.820 align:start position:0% Blake and the paintings pre-compile to 00:17:38.820 --> 00:17:40.669 align:start position:0% Blake and the paintings pre-compile to Smart<00:17:39.000> contracts<00:17:39.480> but<00:17:39.960> this<00:17:40.080> is<00:17:40.200> a<00:17:40.320> work<00:17:40.440> in 00:17:40.669 --> 00:17:40.679 align:start position:0% Smart contracts but this is a work in 00:17:40.679 --> 00:17:43.970 align:start position:0% Smart contracts but this is a work in progress<00:17:40.980> all<00:17:41.640> of<00:17:41.760> them<00:17:41.880> are<00:17:42.179> doable<00:17:43.080> and<00:17:43.740> we 00:17:43.970 --> 00:17:43.980 align:start position:0% progress all of them are doable and we 00:17:43.980 --> 00:17:46.430 align:start position:0% progress all of them are doable and we will<00:17:44.160> we<00:17:44.760> will<00:17:45.000> work<00:17:45.299> in<00:17:45.600> the<00:17:45.720> upcoming<00:17:46.080> on 00:17:46.430 --> 00:17:46.440 align:start position:0% will we will work in the upcoming on 00:17:46.440 --> 00:17:48.350 align:start position:0% will we will work in the upcoming on those<00:17:46.740> on<00:17:47.100> in<00:17:47.280> the<00:17:47.460> upcoming<00:17:47.820> in<00:17:48.059> the<00:17:48.240> coming 00:17:48.350 --> 00:17:48.360 align:start position:0% those on in the upcoming in the coming 00:17:48.360 --> 00:17:49.730 align:start position:0% those on in the upcoming in the coming months 00:17:49.730 --> 00:17:49.740 align:start position:0% months 00:17:49.740 --> 00:17:51.590 align:start position:0% months there<00:17:50.220> is<00:17:50.400> the<00:17:50.460> Audi<00:17:50.700> Title<00:17:51.000> One<00:17:51.059> to<00:17:51.240> enter<00:17:51.360> an 00:17:51.590 --> 00:17:51.600 align:start position:0% there is the Audi Title One to enter an 00:17:51.600 --> 00:17:53.090 align:start position:0% there is the Audi Title One to enter an entertaining<00:17:52.200> the<00:17:52.320> Audi<00:17:52.620> but<00:17:52.860> this<00:17:52.980> is 00:17:53.090 --> 00:17:53.100 align:start position:0% entertaining the Audi but this is 00:17:53.100 --> 00:17:55.970 align:start position:0% entertaining the Audi but this is probably<00:17:53.480> the<00:17:54.480> the<00:17:55.140> most<00:17:55.320> challenging<00:17:55.679> part 00:17:55.970 --> 00:17:55.980 align:start position:0% probably the the most challenging part 00:17:55.980 --> 00:17:58.190 align:start position:0% probably the the most challenging part that<00:17:56.340> we're<00:17:56.700> facing<00:17:57.059> right<00:17:57.240> now<00:17:57.419> there<00:17:57.900> is<00:17:58.080> a 00:17:58.190 --> 00:17:58.200 align:start position:0% that we're facing right now there is a 00:17:58.200 --> 00:18:00.350 align:start position:0% that we're facing right now there is a full<00:17:58.320> plan<00:17:58.559> for<00:17:58.980> running<00:17:59.220> this<00:17:59.460> outage<00:17:59.940> if 00:18:00.350 --> 00:18:00.360 align:start position:0% full plan for running this outage if 00:18:00.360 --> 00:18:01.789 align:start position:0% full plan for running this outage if anyone<00:18:00.660> interested<00:18:01.020> in<00:18:01.140> that<00:18:01.320> please<00:18:01.500> contact 00:18:01.789 --> 00:18:01.799 align:start position:0% anyone interested in that please contact 00:18:01.799 --> 00:18:02.750 align:start position:0% anyone interested in that please contact me 00:18:02.750 --> 00:18:02.760 align:start position:0% me 00:18:02.760 --> 00:18:06.470 align:start position:0% me what<00:18:03.660> else<00:18:03.780> are<00:18:04.140> we<00:18:04.320> working<00:18:04.740> on<00:18:05.640> we<00:18:06.360> are 00:18:06.470 --> 00:18:06.480 align:start position:0% what else are we working on we are 00:18:06.480 --> 00:18:08.029 align:start position:0% what else are we working on we are working<00:18:06.600> also<00:18:06.960> in<00:18:07.080> aggregating<00:18:07.500> of<00:18:07.679> the<00:18:07.799> proof 00:18:08.029 --> 00:18:08.039 align:start position:0% working also in aggregating of the proof 00:18:08.039 --> 00:18:09.650 align:start position:0% working also in aggregating of the proof right<00:18:08.160> now<00:18:08.340> the<00:18:08.520> aggregators<00:18:09.059> right<00:18:09.419> now<00:18:09.539> we 00:18:09.650 --> 00:18:09.660 align:start position:0% right now the aggregators right now we 00:18:09.660 --> 00:18:12.409 align:start position:0% right now the aggregators right now we are<00:18:09.840> running<00:18:09.960> one<00:18:10.440> one<00:18:10.740> proof<00:18:11.160> per<00:18:11.460> batch<00:18:11.940> okay 00:18:12.409 --> 00:18:12.419 align:start position:0% are running one one proof per batch okay 00:18:12.419 --> 00:18:15.529 align:start position:0% are running one one proof per batch okay but<00:18:12.840> we<00:18:13.260> have<00:18:13.500> to<00:18:13.799> uh<00:18:14.220> run<00:18:14.580> one<00:18:14.880> so<00:18:15.179> we<00:18:15.360> need<00:18:15.419> to 00:18:15.529 --> 00:18:15.539 align:start position:0% but we have to uh run one so we need to 00:18:15.539 --> 00:18:16.909 align:start position:0% but we have to uh run one so we need to aggregate<00:18:15.900> all<00:18:16.020> these<00:18:16.200> proofs<00:18:16.440> in<00:18:16.620> a<00:18:16.679> single 00:18:16.909 --> 00:18:16.919 align:start position:0% aggregate all these proofs in a single 00:18:16.919 --> 00:18:18.950 align:start position:0% aggregate all these proofs in a single transaction<00:18:17.220> and<00:18:18.000> and<00:18:18.120> with<00:18:18.480> this<00:18:18.539> in<00:18:18.840> a 00:18:18.950 --> 00:18:18.960 align:start position:0% transaction and and with this in a 00:18:18.960 --> 00:18:20.630 align:start position:0% transaction and and with this in a single<00:18:19.140> proof<00:18:19.380> actually<00:18:19.559> we're<00:18:20.160> working<00:18:20.400> in 00:18:20.630 --> 00:18:20.640 align:start position:0% single proof actually we're working in 00:18:20.640 --> 00:18:21.770 align:start position:0% single proof actually we're working in this<00:18:20.700> proof<00:18:21.000> this<00:18:21.120> is<00:18:21.179> not<00:18:21.299> that<00:18:21.419> much<00:18:21.600> because 00:18:21.770 --> 00:18:21.780 align:start position:0% this proof this is not that much because 00:18:21.780 --> 00:18:23.510 align:start position:0% this proof this is not that much because we<00:18:22.080> have<00:18:22.260> all<00:18:22.380> the<00:18:22.559> recursion<00:18:22.980> already<00:18:23.160> done 00:18:23.510 --> 00:18:23.520 align:start position:0% we have all the recursion already done 00:18:23.520 --> 00:18:25.010 align:start position:0% we have all the recursion already done and<00:18:23.700> it's<00:18:23.820> just<00:18:24.059> putting<00:18:24.720> them<00:18:24.840> together 00:18:25.010 --> 00:18:25.020 align:start position:0% and it's just putting them together 00:18:25.020 --> 00:18:27.830 align:start position:0% and it's just putting them together that's<00:18:25.440> a<00:18:25.740> piece<00:18:25.919> that<00:18:26.160> we<00:18:26.760> need<00:18:26.880> to<00:18:26.940> put<00:18:27.120> there 00:18:27.830 --> 00:18:27.840 align:start position:0% that's a piece that we need to put there 00:18:27.840 --> 00:18:31.070 align:start position:0% that's a piece that we need to put there and<00:18:28.679> we're<00:18:28.980> also<00:18:29.280> working<00:18:29.460> with<00:18:29.700> AAP<00:18:30.059> 4844<00:18:30.780> for 00:18:31.070 --> 00:18:31.080 align:start position:0% and we're also working with AAP 4844 for 00:18:31.080 --> 00:18:32.990 align:start position:0% and we're also working with AAP 4844 for line<00:18:31.260> shelving<00:18:31.679> this<00:18:32.100> is<00:18:32.220> uh<00:18:32.460> clearly<00:18:32.820> the 00:18:32.990 --> 00:18:33.000 align:start position:0% line shelving this is uh clearly the 00:18:33.000 --> 00:18:35.990 align:start position:0% line shelving this is uh clearly the future<00:18:33.179> for<00:18:33.600> the<00:18:33.720> scalability<00:18:34.340> and<00:18:35.340> uh<00:18:35.760> we 00:18:35.990 --> 00:18:36.000 align:start position:0% future for the scalability and uh we 00:18:36.000 --> 00:18:39.110 align:start position:0% future for the scalability and uh we already<00:18:36.380> uh<00:18:37.380> working<00:18:37.740> uh<00:18:38.460> on<00:18:38.640> that<00:18:38.700> we're<00:18:38.940> very 00:18:39.110 --> 00:18:39.120 align:start position:0% already uh working uh on that we're very 00:18:39.120 --> 00:18:40.730 align:start position:0% already uh working uh on that we're very excited<00:18:39.419> on<00:18:39.480> that<00:18:39.660> I<00:18:39.900> I<00:18:40.020> have<00:18:40.200> to<00:18:40.320> recognize 00:18:40.730 --> 00:18:40.740 align:start position:0% excited on that I I have to recognize 00:18:40.740 --> 00:18:42.950 align:start position:0% excited on that I I have to recognize that<00:18:41.039> when<00:18:41.220> I<00:18:41.400> read<00:18:41.580> this<00:18:41.820> EIP<00:18:42.299> I<00:18:42.660> was<00:18:42.780> very 00:18:42.950 --> 00:18:42.960 align:start position:0% that when I read this EIP I was very 00:18:42.960 --> 00:18:45.770 align:start position:0% that when I read this EIP I was very skeptical<00:18:43.440> at<00:18:43.620> the<00:18:43.740> beginning<00:18:43.880> but<00:18:44.880> uh<00:18:45.419> it's 00:18:45.770 --> 00:18:45.780 align:start position:0% skeptical at the beginning but uh it's 00:18:45.780 --> 00:18:48.409 align:start position:0% skeptical at the beginning but uh it's really<00:18:45.900> the<00:18:46.080> way<00:18:46.200> to<00:18:46.380> go<00:18:46.500> we<00:18:46.860> we<00:18:47.280> can<00:18:48.059> Implement 00:18:48.409 --> 00:18:48.419 align:start position:0% really the way to go we we can Implement 00:18:48.419 --> 00:18:50.450 align:start position:0% really the way to go we we can Implement insight<00:18:48.900> and<00:18:49.080> it<00:18:49.320> really<00:18:49.500> go<00:18:49.799> will<00:18:50.100> go<00:18:50.280> even 00:18:50.450 --> 00:18:50.460 align:start position:0% insight and it really go will go even 00:18:50.460 --> 00:18:52.789 align:start position:0% insight and it really go will go even faster<00:18:50.820> and<00:18:51.299> it's<00:18:51.480> even<00:18:51.720> better<00:18:52.020> that<00:18:52.320> what<00:18:52.620> I 00:18:52.789 --> 00:18:52.799 align:start position:0% faster and it's even better that what I 00:18:52.799 --> 00:18:55.490 align:start position:0% faster and it's even better that what I would<00:18:52.919> what<00:18:53.280> I<00:18:53.580> would<00:18:53.820> do<00:18:54.480> it's<00:18:54.780> just<00:18:54.960> that<00:18:55.140> you 00:18:55.490 --> 00:18:55.500 align:start position:0% would what I would do it's just that you 00:18:55.500 --> 00:18:56.750 align:start position:0% would what I would do it's just that you the<00:18:55.799> only<00:18:55.860> thing<00:18:56.039> is<00:18:56.100> that<00:18:56.220> you<00:18:56.340> need<00:18:56.400> to<00:18:56.460> go<00:18:56.580> a 00:18:56.750 --> 00:18:56.760 align:start position:0% the only thing is that you need to go a 00:18:56.760 --> 00:18:59.029 align:start position:0% the only thing is that you need to go a little<00:18:56.820> bit<00:18:57.000> deep<00:18:57.240> to<00:18:58.140> understand<00:18:58.260> this<00:18:58.620> VIP 00:18:59.029 --> 00:18:59.039 align:start position:0% little bit deep to understand this VIP 00:18:59.039 --> 00:19:01.430 align:start position:0% little bit deep to understand this VIP that's<00:18:59.700> really<00:19:00.140> interesting<00:19:01.140> I'm<00:19:01.260> very 00:19:01.430 --> 00:19:01.440 align:start position:0% that's really interesting I'm very 00:19:01.440 --> 00:19:03.289 align:start position:0% that's really interesting I'm very excited<00:19:01.799> for<00:19:01.919> this<00:19:02.100> gaming 00:19:03.289 --> 00:19:03.299 align:start position:0% excited for this gaming 00:19:03.299 --> 00:19:06.650 align:start position:0% excited for this gaming testing<00:19:04.140> we're<00:19:04.980> running<00:19:05.220> the<00:19:05.580> the<00:19:05.820> ethereum 00:19:06.650 --> 00:19:06.660 align:start position:0% testing we're running the the ethereum 00:19:06.660 --> 00:19:08.810 align:start position:0% testing we're running the the ethereum test<00:19:06.900> Suites 00:19:08.810 --> 00:19:08.820 align:start position:0% test Suites 00:19:08.820 --> 00:19:12.529 align:start position:0% test Suites right<00:19:09.299> now<00:19:09.419> we<00:19:09.539> are<00:19:09.660> at<00:19:09.720> 97.7<00:19:10.620> 97<00:19:11.400> of<00:19:12.299> uh 00:19:12.529 --> 00:19:12.539 align:start position:0% right now we are at 97.7 97 of uh 00:19:12.539 --> 00:19:14.690 align:start position:0% right now we are at 97.7 97 of uh passing<00:19:13.080> all<00:19:13.380> these<00:19:13.620> tests<00:19:13.919> there<00:19:14.100> are<00:19:14.280> edge 00:19:14.690 --> 00:19:14.700 align:start position:0% passing all these tests there are edge 00:19:14.700 --> 00:19:17.090 align:start position:0% passing all these tests there are edge cases<00:19:15.120> that<00:19:15.419> we're<00:19:15.600> still<00:19:16.020> uh<00:19:16.559> working<00:19:16.799> on 00:19:17.090 --> 00:19:17.100 align:start position:0% cases that we're still uh working on 00:19:17.100 --> 00:19:20.510 align:start position:0% cases that we're still uh working on that<00:19:17.280> but<00:19:18.120> I'm<00:19:18.539> sure<00:19:18.780> that<00:19:19.200> uh<00:19:19.620> very<00:19:19.860> soon<00:19:20.100> uh 00:19:20.510 --> 00:19:20.520 align:start position:0% that but I'm sure that uh very soon uh 00:19:20.520 --> 00:19:22.789 align:start position:0% that but I'm sure that uh very soon uh we<00:19:20.700> will<00:19:20.880> be<00:19:21.000> covering<00:19:21.419> the<00:19:21.660> will<00:19:22.260> be<00:19:22.500> in<00:19:22.620> 100 00:19:22.789 --> 00:19:22.799 align:start position:0% we will be covering the will be in 100 00:19:22.799 --> 00:19:28.370 align:start position:0% we will be covering the will be in 100 of<00:19:23.520> the<00:19:23.760> of<00:19:24.299> the<00:19:24.539> ethereum<00:19:25.080> of<00:19:25.500> ethereum<00:19:25.919> test 00:19:28.370 --> 00:19:28.380 align:start position:0% 00:19:28.380 --> 00:19:30.890 align:start position:0% roadmap<00:19:29.100> of<00:19:29.760> course<00:19:29.880> we<00:19:30.240> just<00:19:30.360> launched<00:19:30.660> the 00:19:30.890 --> 00:19:30.900 align:start position:0% roadmap of course we just launched the 00:19:30.900 --> 00:19:33.409 align:start position:0% roadmap of course we just launched the public<00:19:31.020> test<00:19:31.260> net<00:19:31.440> uh<00:19:32.160> we<00:19:32.340> need<00:19:32.400> to<00:19:32.520> audit<00:19:32.880> and 00:19:33.409 --> 00:19:33.419 align:start position:0% public test net uh we need to audit and 00:19:33.419 --> 00:19:35.510 align:start position:0% public test net uh we need to audit and we<00:19:33.600> will<00:19:33.720> launch<00:19:33.960> when<00:19:34.320> it's<00:19:34.500> ready<00:19:34.740> here<00:19:35.220> is 00:19:35.510 --> 00:19:35.520 align:start position:0% we will launch when it's ready here is 00:19:35.520 --> 00:19:38.210 align:start position:0% we will launch when it's ready here is uh<00:19:35.820> we<00:19:36.059> want<00:19:36.240> we<00:19:36.960> want<00:19:37.140> to<00:19:37.260> be<00:19:37.380> enough<00:19:37.559> safe<00:19:37.980> we 00:19:38.210 --> 00:19:38.220 align:start position:0% uh we want we want to be enough safe we 00:19:38.220 --> 00:19:39.950 align:start position:0% uh we want we want to be enough safe we want<00:19:38.760> enough 00:19:39.950 --> 00:19:39.960 align:start position:0% want enough 00:19:39.960 --> 00:19:44.750 align:start position:0% want enough sure<00:19:40.860> that<00:19:41.820> so<00:19:42.179> 100<00:19:43.039> uh<00:19:44.039> safe<00:19:44.220> is<00:19:44.460> going<00:19:44.580> to<00:19:44.700> be 00:19:44.750 --> 00:19:44.760 align:start position:0% sure that so 100 uh safe is going to be 00:19:44.760 --> 00:19:46.070 align:start position:0% sure that so 100 uh safe is going to be impossible<00:19:45.059> but<00:19:45.299> we<00:19:45.419> want<00:19:45.539> we<00:19:45.780> want<00:19:45.900> to<00:19:46.020> be 00:19:46.070 --> 00:19:46.080 align:start position:0% impossible but we want we want to be 00:19:46.080 --> 00:19:47.870 align:start position:0% impossible but we want we want to be responsible<00:19:46.559> and<00:19:46.799> we<00:19:46.980> want<00:19:47.100> to<00:19:47.220> update<00:19:47.640> this 00:19:47.870 --> 00:19:47.880 align:start position:0% responsible and we want to update this 00:19:47.880 --> 00:19:49.970 align:start position:0% responsible and we want to update this very<00:19:48.059> well<00:19:48.299> and<00:19:49.020> when<00:19:49.200> we<00:19:49.380> feel<00:19:49.559> comfortable 00:19:49.970 --> 00:19:49.980 align:start position:0% very well and when we feel comfortable 00:19:49.980 --> 00:19:53.029 align:start position:0% very well and when we feel comfortable then<00:19:50.280> we<00:19:50.580> will<00:19:50.760> we<00:19:51.240> will<00:19:51.419> we<00:19:51.840> will<00:19:52.020> launch 00:19:53.029 --> 00:19:53.039 align:start position:0% then we will we will we will launch 00:19:53.039 --> 00:19:55.789 align:start position:0% then we will we will we will launch a<00:19:53.940> reminder<00:19:54.179> everything<00:19:54.539> is<00:19:54.840> open<00:19:54.960> source<00:19:55.440> you 00:19:55.789 --> 00:19:55.799 align:start position:0% a reminder everything is open source you 00:19:55.799 --> 00:19:58.430 align:start position:0% a reminder everything is open source you can<00:19:55.919> take<00:19:56.160> a<00:19:56.340> look<00:19:56.460> you<00:19:56.820> can<00:19:56.940> see<00:19:57.179> you<00:19:57.539> can<00:19:57.960> you 00:19:58.430 --> 00:19:58.440 align:start position:0% can take a look you can see you can you 00:19:58.440 --> 00:20:00.890 align:start position:0% can take a look you can see you can you can<00:19:58.559> review<00:19:58.740> everything<00:19:59.100> is<00:19:59.520> uh<00:20:00.120> in<00:20:00.780> the 00:20:00.890 --> 00:20:00.900 align:start position:0% can review everything is uh in the 00:20:00.900 --> 00:20:03.230 align:start position:0% can review everything is uh in the GitHub<00:20:01.200> repositories 00:20:03.230 --> 00:20:03.240 align:start position:0% GitHub repositories 00:20:03.240 --> 00:20:07.370 align:start position:0% GitHub repositories and<00:20:03.720> yeah<00:20:03.919> gkbm<00:20:04.919> is<00:20:05.100> no<00:20:05.220> longer<00:20:05.400> a<00:20:05.520> myth 00:20:07.370 --> 00:20:07.380 align:start position:0% and yeah gkbm is no longer a myth 00:20:07.380 --> 00:20:08.990 align:start position:0% and yeah gkbm is no longer a myth foreign 00:20:08.990 --> 00:20:09.000 align:start position:0% foreign 00:20:09.000 --> 00:20:15.409 align:start position:0% foreign [Applause] 00:20:15.409 --> 00:20:15.419 align:start position:0% 00:20:15.419 --> 00:20:17.630 align:start position:0% thank<00:20:15.960> you<00:20:16.080> so<00:20:16.200> much<00:20:16.380> uh<00:20:16.919> we<00:20:17.100> have<00:20:17.280> a<00:20:17.400> couple<00:20:17.520> of 00:20:17.630 --> 00:20:17.640 align:start position:0% thank you so much uh we have a couple of 00:20:17.640 --> 00:20:20.330 align:start position:0% thank you so much uh we have a couple of minutes<00:20:17.940> for<00:20:18.539> uh<00:20:19.080> questions<00:20:19.320> so<00:20:19.799> if<00:20:20.039> you<00:20:20.160> have 00:20:20.330 --> 00:20:20.340 align:start position:0% minutes for uh questions so if you have 00:20:20.340 --> 00:20:23.409 align:start position:0% minutes for uh questions so if you have a<00:20:20.460> question<00:20:20.640> please<00:20:20.940> raise<00:20:21.240> your<00:20:21.480> hand 00:20:23.409 --> 00:20:23.419 align:start position:0% a question please raise your hand 00:20:23.419 --> 00:20:26.210 align:start position:0% a question please raise your hand hello<00:20:24.419> thank<00:20:24.780> you<00:20:24.900> for<00:20:25.020> the<00:20:25.200> presentation<00:20:25.559> uh 00:20:26.210 --> 00:20:26.220 align:start position:0% hello thank you for the presentation uh 00:20:26.220 --> 00:20:28.730 align:start position:0% hello thank you for the presentation uh the<00:20:26.640> AVM<00:20:27.059> is<00:20:27.240> not<00:20:27.360> a<00:20:27.480> frozen<00:20:27.600> object<00:20:28.140> it's 00:20:28.730 --> 00:20:28.740 align:start position:0% the AVM is not a frozen object it's 00:20:28.740 --> 00:20:30.650 align:start position:0% the AVM is not a frozen object it's leaving<00:20:29.039> and<00:20:29.280> it's<00:20:29.400> evolving<00:20:29.820> with<00:20:30.059> new<00:20:30.240> eips 00:20:30.650 --> 00:20:30.660 align:start position:0% leaving and it's evolving with new eips 00:20:30.660 --> 00:20:33.529 align:start position:0% leaving and it's evolving with new eips and<00:20:31.559> we<00:20:31.679> are<00:20:31.860> going<00:20:32.160> to<00:20:32.340> see<00:20:32.700> possibly<00:20:33.360> big 00:20:33.529 --> 00:20:33.539 align:start position:0% and we are going to see possibly big 00:20:33.539 --> 00:20:35.690 align:start position:0% and we are going to see possibly big change<00:20:33.720> like<00:20:34.020> the<00:20:34.200> eof<00:20:34.620> or<00:20:35.039> other<00:20:35.160> things<00:20:35.520> like 00:20:35.690 --> 00:20:35.700 align:start position:0% change like the eof or other things like 00:20:35.700 --> 00:20:37.850 align:start position:0% change like the eof or other things like that<00:20:35.880> and<00:20:36.539> they<00:20:36.720> will<00:20:36.900> be<00:20:37.020> way<00:20:37.320> easier<00:20:37.740> to 00:20:37.850 --> 00:20:37.860 align:start position:0% that and they will be way easier to 00:20:37.860 --> 00:20:40.850 align:start position:0% that and they will be way easier to implement<00:20:38.220> for<00:20:38.760> core<00:20:39.120> devs<00:20:39.660> and<00:20:39.840> for<00:20:40.440> you<00:20:40.620> so 00:20:40.850 --> 00:20:40.860 align:start position:0% implement for core devs and for you so 00:20:40.860 --> 00:20:43.490 align:start position:0% implement for core devs and for you so are<00:20:41.160> you<00:20:41.340> worried<00:20:41.700> that<00:20:42.120> some<00:20:42.660> possible<00:20:43.020> evm 00:20:43.490 --> 00:20:43.500 align:start position:0% are you worried that some possible evm 00:20:43.500 --> 00:20:45.110 align:start position:0% are you worried that some possible evm change<00:20:43.679> will<00:20:43.919> be<00:20:44.039> hard<00:20:44.280> to<00:20:44.580> translate<00:20:44.760> into 00:20:45.110 --> 00:20:45.120 align:start position:0% change will be hard to translate into 00:20:45.120 --> 00:20:47.150 align:start position:0% change will be hard to translate into circuits<00:20:45.660> in<00:20:45.780> the<00:20:45.900> future 00:20:47.150 --> 00:20:47.160 align:start position:0% circuits in the future 00:20:47.160 --> 00:20:48.770 align:start position:0% circuits in the future uh 00:20:48.770 --> 00:20:48.780 align:start position:0% uh 00:20:48.780 --> 00:20:51.289 align:start position:0% uh we<00:20:49.320> need<00:20:49.440> to<00:20:49.679> see<00:20:49.919> which<00:20:50.280> are<00:20:50.520> those<00:20:50.760> changes 00:20:51.289 --> 00:20:51.299 align:start position:0% we need to see which are those changes 00:20:51.299 --> 00:20:54.289 align:start position:0% we need to see which are those changes and<00:20:51.840> once<00:20:52.140> I<00:20:52.260> see<00:20:52.440> the<00:20:52.620> changes<00:20:53.039> I<00:20:53.520> will<00:20:53.820> tell 00:20:54.289 --> 00:20:54.299 align:start position:0% and once I see the changes I will tell 00:20:54.299 --> 00:20:56.510 align:start position:0% and once I see the changes I will tell you<00:20:54.480> but<00:20:54.960> there<00:20:55.559> is<00:20:55.679> one<00:20:55.860> thing<00:20:56.039> that<00:20:56.280> because 00:20:56.510 --> 00:20:56.520 align:start position:0% you but there is one thing that because 00:20:56.520 --> 00:20:59.330 align:start position:0% you but there is one thing that because this<00:20:57.059> is<00:20:57.240> this<00:20:57.780> is<00:20:57.960> some<00:20:58.200> of<00:20:58.320> the<00:20:58.620> the 00:20:59.330 --> 00:20:59.340 align:start position:0% this is this is some of the the 00:20:59.340 --> 00:21:00.890 align:start position:0% this is this is some of the the questions<00:20:59.580> that<00:20:59.880> I<00:21:00.059> received<00:21:00.360> now<00:21:00.539> it<00:21:00.780> is 00:21:00.890 --> 00:21:00.900 align:start position:0% questions that I received now it is 00:21:00.900 --> 00:21:02.390 align:start position:0% questions that I received now it is sometimes<00:21:01.320> it's<00:21:01.500> more<00:21:01.679> about<00:21:01.860> the 00:21:02.390 --> 00:21:02.400 align:start position:0% sometimes it's more about the 00:21:02.400 --> 00:21:05.150 align:start position:0% sometimes it's more about the upgradability<00:21:03.000> of<00:21:03.720> uh<00:21:04.320> this<00:21:04.740> what<00:21:04.980> happened 00:21:05.150 --> 00:21:05.160 align:start position:0% upgradability of uh this what happened 00:21:05.160 --> 00:21:06.950 align:start position:0% upgradability of uh this what happened if<00:21:05.460> the<00:21:05.580> ckvm<00:21:06.179> upgrade<00:21:06.480> and<00:21:06.600> then<00:21:06.780> what 00:21:06.950 --> 00:21:06.960 align:start position:0% if the ckvm upgrade and then what 00:21:06.960 --> 00:21:08.390 align:start position:0% if the ckvm upgrade and then what happened<00:21:07.320> with<00:21:07.559> the<00:21:07.740> roll<00:21:07.860> up<00:21:08.100> it<00:21:08.280> will 00:21:08.390 --> 00:21:08.400 align:start position:0% happened with the roll up it will 00:21:08.400 --> 00:21:09.710 align:start position:0% happened with the roll up it will upgrade<00:21:08.700> and<00:21:08.820> if<00:21:08.940> you<00:21:09.059> want<00:21:09.120> to<00:21:09.240> decentralized 00:21:09.710 --> 00:21:09.720 align:start position:0% upgrade and if you want to decentralized 00:21:09.720 --> 00:21:11.029 align:start position:0% upgrade and if you want to decentralized system 00:21:11.029 --> 00:21:11.039 align:start position:0% system 00:21:11.039 --> 00:21:13.909 align:start position:0% system and<00:21:11.880> but<00:21:12.240> here<00:21:12.539> is<00:21:12.780> uh<00:21:13.200> we<00:21:13.559> need<00:21:13.679> to<00:21:13.799> understand 00:21:13.909 --> 00:21:13.919 align:start position:0% and but here is uh we need to understand 00:21:13.919 --> 00:21:18.169 align:start position:0% and but here is uh we need to understand as<00:21:14.400> a<00:21:14.640> community<00:21:15.020> that<00:21:16.020> uh<00:21:16.860> the<00:21:16.980> ABM<00:21:17.460> at<00:21:17.760> this 00:21:18.169 --> 00:21:18.179 align:start position:0% as a community that uh the ABM at this 00:21:18.179 --> 00:21:19.789 align:start position:0% as a community that uh the ABM at this point<00:21:18.299> is<00:21:18.539> evolving<00:21:19.020> because<00:21:19.200> it's<00:21:19.440> work<00:21:19.620> in 00:21:19.789 --> 00:21:19.799 align:start position:0% point is evolving because it's work in 00:21:19.799 --> 00:21:21.770 align:start position:0% point is evolving because it's work in progress<00:21:20.100> but<00:21:20.760> at<00:21:20.880> some<00:21:21.059> point<00:21:21.179> this<00:21:21.539> will 00:21:21.770 --> 00:21:21.780 align:start position:0% progress but at some point this will 00:21:21.780 --> 00:21:24.169 align:start position:0% progress but at some point this will this<00:21:22.200> this<00:21:22.380> will<00:21:22.679> need<00:21:22.860> to<00:21:22.980> be<00:21:23.160> frozen 00:21:24.169 --> 00:21:24.179 align:start position:0% this this will need to be frozen 00:21:24.179 --> 00:21:25.970 align:start position:0% this this will need to be frozen uh 00:21:25.970 --> 00:21:25.980 align:start position:0% uh 00:21:25.980 --> 00:21:28.610 align:start position:0% uh I<00:21:26.340> don't<00:21:26.460> know<00:21:26.580> when<00:21:26.700> and<00:21:26.940> how<00:21:27.179> but<00:21:28.020> and<00:21:28.500> I'm 00:21:28.610 --> 00:21:28.620 align:start position:0% I don't know when and how but and I'm 00:21:28.620 --> 00:21:30.289 align:start position:0% I don't know when and how but and I'm not<00:21:28.799> talking<00:21:28.980> about<00:21:29.159> the<00:21:29.400> ckvm<00:21:30.000> I'm<00:21:30.179> talking 00:21:30.289 --> 00:21:30.299 align:start position:0% not talking about the ckvm I'm talking 00:21:30.299 --> 00:21:32.930 align:start position:0% not talking about the ckvm I'm talking about<00:21:30.480> the<00:21:30.720> AVM<00:21:31.140> so<00:21:31.320> the<00:21:31.500> ABM<00:21:31.919> if<00:21:32.220> you<00:21:32.340> want<00:21:32.520> uh 00:21:32.930 --> 00:21:32.940 align:start position:0% about the AVM so the ABM if you want uh 00:21:32.940 --> 00:21:37.610 align:start position:0% about the AVM so the ABM if you want uh I<00:21:33.179> believe<00:21:33.299> I<00:21:33.659> I<00:21:33.780> I<00:21:33.960> I<00:21:34.320> believe<00:21:34.919> I<00:21:35.400> hope<00:21:35.580> and<00:21:36.620> if 00:21:37.610 --> 00:21:37.620 align:start position:0% I believe I I I I believe I hope and if 00:21:37.620 --> 00:21:39.710 align:start position:0% I believe I I I I believe I hope and if talking<00:21:38.159> with<00:21:38.460> people<00:21:38.640> with<00:21:38.940> the<00:21:39.120> effort<00:21:39.480> they 00:21:39.710 --> 00:21:39.720 align:start position:0% talking with people with the effort they 00:21:39.720 --> 00:21:42.169 align:start position:0% talking with people with the effort they already<00:21:40.200> think<00:21:40.740> very<00:21:41.340> much<00:21:41.460> on<00:21:41.640> that<00:21:41.820> time<00:21:41.940> is 00:21:42.169 --> 00:21:42.179 align:start position:0% already think very much on that time is 00:21:42.179 --> 00:21:43.850 align:start position:0% already think very much on that time is that<00:21:42.360> at<00:21:42.480> some<00:21:42.659> point<00:21:42.780> maybe<00:21:43.140> in<00:21:43.440> two<00:21:43.679> years 00:21:43.850 --> 00:21:43.860 align:start position:0% that at some point maybe in two years 00:21:43.860 --> 00:21:46.310 align:start position:0% that at some point maybe in two years three<00:21:44.100> years<00:21:44.340> five<00:21:44.640> years<00:21:44.880> once<00:21:45.780> the<00:21:45.900> ethereum 00:21:46.310 --> 00:21:46.320 align:start position:0% three years five years once the ethereum 00:21:46.320 --> 00:21:48.950 align:start position:0% three years five years once the ethereum is<00:21:46.559> finish<00:21:46.799> it<00:21:47.039> then<00:21:47.760> the<00:21:48.000> IBM<00:21:48.480> will<00:21:48.659> be<00:21:48.780> Frozen 00:21:48.950 --> 00:21:48.960 align:start position:0% is finish it then the IBM will be Frozen 00:21:48.960 --> 00:21:51.049 align:start position:0% is finish it then the IBM will be Frozen and<00:21:49.440> then<00:21:49.559> it<00:21:49.740> will<00:21:49.860> be<00:21:50.039> also<00:21:50.280> the<00:21:50.400> time<00:21:50.520> to<00:21:50.820> for 00:21:51.049 --> 00:21:51.059 align:start position:0% and then it will be also the time to for 00:21:51.059 --> 00:21:54.350 align:start position:0% and then it will be also the time to for to<00:21:51.480> freeze<00:21:51.900> the<00:21:52.620> the<00:21:52.919> roll-ups 00:21:54.350 --> 00:21:54.360 align:start position:0% to freeze the the roll-ups 00:21:54.360 --> 00:21:56.090 align:start position:0% to freeze the the roll-ups thank<00:21:54.900> you<00:21:55.080> for<00:21:55.140> the<00:21:55.320> presentation<00:21:55.740> great 00:21:56.090 --> 00:21:56.100 align:start position:0% thank you for the presentation great 00:21:56.100 --> 00:21:58.789 align:start position:0% thank you for the presentation great talk<00:21:56.400> I<00:21:57.360> would<00:21:57.539> like<00:21:57.900> I<00:21:58.140> mean<00:21:58.320> could<00:21:58.559> you 00:21:58.789 --> 00:21:58.799 align:start position:0% talk I would like I mean could you 00:21:58.799 --> 00:22:00.710 align:start position:0% talk I would like I mean could you detail<00:21:59.340> a<00:21:59.520> little<00:21:59.580> bit<00:21:59.760> what<00:22:00.120> are<00:22:00.299> the<00:22:00.480> edge 00:22:00.710 --> 00:22:00.720 align:start position:0% detail a little bit what are the edge 00:22:00.720 --> 00:22:04.130 align:start position:0% detail a little bit what are the edge cases<00:22:01.140> that<00:22:01.559> you<00:22:01.679> are<00:22:01.919> meeting<00:22:02.900> regarding<00:22:03.900> the 00:22:04.130 --> 00:22:04.140 align:start position:0% cases that you are meeting regarding the 00:22:04.140 --> 00:22:05.990 align:start position:0% cases that you are meeting regarding the failing<00:22:04.919> tests 00:22:05.990 --> 00:22:06.000 align:start position:0% failing tests 00:22:06.000 --> 00:22:09.230 align:start position:0% failing tests uh<00:22:06.840> here<00:22:07.200> we<00:22:07.559> have<00:22:07.740> uh<00:22:08.100> Carlos<00:22:08.700> in<00:22:08.940> the<00:22:09.120> room 00:22:09.230 --> 00:22:09.240 align:start position:0% uh here we have uh Carlos in the room 00:22:09.240 --> 00:22:11.810 align:start position:0% uh here we have uh Carlos in the room that's<00:22:09.720> responsible<00:22:10.500> for<00:22:10.860> testing<00:22:11.220> you<00:22:11.760> can 00:22:11.810 --> 00:22:11.820 align:start position:0% that's responsible for testing you can 00:22:11.820 --> 00:22:13.490 align:start position:0% that's responsible for testing you can ask<00:22:12.000> them<00:22:12.179> but<00:22:12.360> they<00:22:12.480> are<00:22:12.659> very<00:22:12.720> very<00:22:12.900> they<00:22:13.260> are 00:22:13.490 --> 00:22:13.500 align:start position:0% ask them but they are very very they are 00:22:13.500 --> 00:22:17.450 align:start position:0% ask them but they are very very they are very<00:22:13.679> very<00:22:13.860> uh<00:22:15.059> complex<00:22:15.659> one<00:22:15.900> it's<00:22:16.440> a<00:22:16.799> Carl<00:22:17.159> of 00:22:17.450 --> 00:22:17.460 align:start position:0% very very uh complex one it's a Carl of 00:22:17.460 --> 00:22:19.250 align:start position:0% very very uh complex one it's a Carl of a<00:22:17.640> static<00:22:17.940> call<00:22:18.120> and<00:22:18.419> then<00:22:18.600> do<00:22:18.780> a<00:22:18.960> surface 00:22:19.250 --> 00:22:19.260 align:start position:0% a static call and then do a surface 00:22:19.260 --> 00:22:21.289 align:start position:0% a static call and then do a surface truck<00:22:19.500> and<00:22:19.799> and<00:22:20.159> do<00:22:20.460> whatever<00:22:20.700> you<00:22:21.059> know<00:22:21.120> this 00:22:21.289 --> 00:22:21.299 align:start position:0% truck and and do whatever you know this 00:22:21.299 --> 00:22:25.310 align:start position:0% truck and and do whatever you know this is<00:22:21.539> our<00:22:21.720> very<00:22:21.960> very<00:22:22.080> edge<00:22:22.919> cases<00:22:23.900> uh<00:22:24.900> very<00:22:25.140> very 00:22:25.310 --> 00:22:25.320 align:start position:0% is our very very edge cases uh very very 00:22:25.320 --> 00:22:27.350 align:start position:0% is our very very edge cases uh very very edge<00:22:25.559> cases<00:22:25.919> testing<00:22:26.340> but<00:22:26.580> you<00:22:27.059> have<00:22:27.120> to<00:22:27.240> take 00:22:27.350 --> 00:22:27.360 align:start position:0% edge cases testing but you have to take 00:22:27.360 --> 00:22:29.090 align:start position:0% edge cases testing but you have to take you<00:22:27.659> have<00:22:27.780> to<00:22:27.900> look<00:22:28.020> at<00:22:28.200> it<00:22:28.320> because<00:22:28.559> you<00:22:28.919> never 00:22:29.090 --> 00:22:29.100 align:start position:0% you have to look at it because you never 00:22:29.100 --> 00:22:30.710 align:start position:0% you have to look at it because you never know<00:22:29.280> one<00:22:29.460> and<00:22:29.700> it's<00:22:29.880> important<00:22:30.299> that's<00:22:30.480> why 00:22:30.710 --> 00:22:30.720 align:start position:0% know one and it's important that's why 00:22:30.720 --> 00:22:33.409 align:start position:0% know one and it's important that's why those<00:22:31.080> tests<00:22:31.440> are<00:22:31.559> are<00:22:31.799> there<00:22:32.460> but<00:22:32.880> are<00:22:33.120> really 00:22:33.409 --> 00:22:33.419 align:start position:0% those tests are are there but are really 00:22:33.419 --> 00:22:35.450 align:start position:0% those tests are are there but are really really<00:22:33.900> edge<00:22:34.200> cases<00:22:34.620> at<00:22:34.799> this<00:22:34.980> point<00:22:35.100> and 00:22:35.450 --> 00:22:35.460 align:start position:0% really edge cases at this point and 00:22:35.460 --> 00:22:37.730 align:start position:0% really edge cases at this point and complex<00:22:35.880> ones<00:22:36.299> hi<00:22:37.080> thank<00:22:37.320> you<00:22:37.440> for<00:22:37.559> the 00:22:37.730 --> 00:22:37.740 align:start position:0% complex ones hi thank you for the 00:22:37.740 --> 00:22:39.470 align:start position:0% complex ones hi thank you for the presentation<00:22:38.159> uh<00:22:38.640> when<00:22:38.880> you<00:22:39.000> were<00:22:39.120> showing 00:22:39.470 --> 00:22:39.480 align:start position:0% presentation uh when you were showing 00:22:39.480 --> 00:22:42.649 align:start position:0% presentation uh when you were showing the<00:22:39.900> uh<00:22:40.500> on<00:22:40.679> ethoscan<00:22:41.520> the<00:22:42.120> contents<00:22:42.480> of<00:22:42.539> the 00:22:42.649 --> 00:22:42.659 align:start position:0% the uh on ethoscan the contents of the 00:22:42.659 --> 00:22:44.810 align:start position:0% the uh on ethoscan the contents of the badge<00:22:43.020> you<00:22:43.799> showed<00:22:44.039> like<00:22:44.159> that<00:22:44.400> there<00:22:44.640> was 00:22:44.810 --> 00:22:44.820 align:start position:0% badge you showed like that there was 00:22:44.820 --> 00:22:47.770 align:start position:0% badge you showed like that there was like<00:22:45.059> you<00:22:45.600> know<00:22:45.659> uh<00:22:46.200> the<00:22:46.559> code<00:22:46.799> like<00:22:47.159> encoded 00:22:47.770 --> 00:22:47.780 align:start position:0% like you know uh the code like encoded 00:22:47.780 --> 00:22:50.450 align:start position:0% like you know uh the code like encoded set<00:22:48.780> of<00:22:48.960> transactions<00:22:49.380> is<00:22:49.799> there<00:22:49.919> any<00:22:50.100> way<00:22:50.280> to 00:22:50.450 --> 00:22:50.460 align:start position:0% set of transactions is there any way to 00:22:50.460 --> 00:22:53.330 align:start position:0% set of transactions is there any way to decode<00:22:50.880> them<00:22:51.240> uh<00:22:52.020> to<00:22:52.140> to<00:22:52.320> see<00:22:52.500> what<00:22:52.740> exactly<00:22:53.100> is 00:22:53.330 --> 00:22:53.340 align:start position:0% decode them uh to to see what exactly is 00:22:53.340 --> 00:22:56.570 align:start position:0% decode them uh to to see what exactly is in<00:22:53.520> the<00:22:53.640> batch<00:22:53.880> yeah<00:22:54.480> it's<00:22:55.020> mainly<00:22:55.679> many<00:22:56.340> other 00:22:56.570 --> 00:22:56.580 align:start position:0% in the batch yeah it's mainly many other 00:22:56.580 --> 00:23:01.250 align:start position:0% in the batch yeah it's mainly many other transactions<00:22:57.360> uh<00:22:57.840> one<00:22:58.080> after<00:22:58.260> the<00:22:58.620> other<00:22:58.740> uh 00:23:01.250 --> 00:23:01.260 align:start position:0% transactions uh one after the other uh 00:23:01.260 --> 00:23:04.190 align:start position:0% transactions uh one after the other uh um we<00:23:02.220> have<00:23:02.400> some<00:23:02.700> internal<00:23:03.120> tooling<00:23:03.600> just<00:23:03.960> to 00:23:04.190 --> 00:23:04.200 align:start position:0% um we have some internal tooling just to 00:23:04.200 --> 00:23:05.930 align:start position:0% um we have some internal tooling just to to<00:23:04.440> take<00:23:04.740> a<00:23:04.860> look<00:23:04.980> on<00:23:05.159> that<00:23:05.340> well<00:23:05.760> actually 00:23:05.930 --> 00:23:05.940 align:start position:0% to take a look on that well actually 00:23:05.940 --> 00:23:07.430 align:start position:0% to take a look on that well actually they<00:23:06.179> are<00:23:06.360> open<00:23:06.419> source<00:23:06.840> you<00:23:07.020> can<00:23:07.140> check<00:23:07.260> the 00:23:07.430 --> 00:23:07.440 align:start position:0% they are open source you can check the 00:23:07.440 --> 00:23:10.850 align:start position:0% they are open source you can check the repositories<00:23:08.299> but<00:23:09.299> we<00:23:09.780> are<00:23:09.900> building<00:23:10.080> it<00:23:10.380> and 00:23:10.850 --> 00:23:10.860 align:start position:0% repositories but we are building it and 00:23:10.860 --> 00:23:14.770 align:start position:0% repositories but we are building it and in<00:23:11.100> any<00:23:11.280> case<00:23:11.460> it<00:23:11.760> would<00:23:11.940> not<00:23:12.059> be<00:23:12.299> difficult<00:23:12.659> to 00:23:14.770 --> 00:23:14.780 align:start position:0% in any case it would not be difficult to 00:23:14.780 --> 00:23:16.909 align:start position:0% in any case it would not be difficult to interpret<00:23:15.780> at<00:23:15.960> the<00:23:16.080> end<00:23:16.200> it's<00:23:16.320> just<00:23:16.440> a<00:23:16.559> format 00:23:16.909 --> 00:23:16.919 align:start position:0% interpret at the end it's just a format 00:23:16.919 --> 00:23:20.029 align:start position:0% interpret at the end it's just a format with<00:23:17.159> with<00:23:17.700> the<00:23:18.000> array<00:23:18.419> of<00:23:18.480> transactions<00:23:19.559> I 00:23:20.029 --> 00:23:20.039 align:start position:0% with with the array of transactions I 00:23:20.039 --> 00:23:21.950 align:start position:0% with with the array of transactions I think<00:23:20.159> we<00:23:20.400> have<00:23:20.580> time<00:23:20.820> for<00:23:21.120> one<00:23:21.360> more<00:23:21.600> question 00:23:21.950 --> 00:23:21.960 align:start position:0% think we have time for one more question 00:23:21.960 --> 00:23:25.070 align:start position:0% think we have time for one more question so<00:23:22.740> if<00:23:23.039> you<00:23:23.220> can<00:23:23.400> lend<00:23:23.940> the<00:23:24.240> microphone<00:23:24.720> to<00:23:24.900> our 00:23:25.070 --> 00:23:25.080 align:start position:0% so if you can lend the microphone to our 00:23:25.080 --> 00:23:26.810 align:start position:0% so if you can lend the microphone to our speaker 00:23:26.810 --> 00:23:26.820 align:start position:0% speaker 00:23:26.820 --> 00:23:29.450 align:start position:0% speaker ah<00:23:27.480> cool<00:23:27.659> go<00:23:28.020> ahead 00:23:29.450 --> 00:23:29.460 align:start position:0% ah cool go ahead 00:23:29.460 --> 00:23:32.510 align:start position:0% ah cool go ahead hey<00:23:29.940> thank<00:23:30.179> you<00:23:30.240> can<00:23:30.419> you<00:23:30.539> hear<00:23:30.659> me<00:23:30.780> yep<00:23:31.500> okay 00:23:32.510 --> 00:23:32.520 align:start position:0% hey thank you can you hear me yep okay 00:23:32.520 --> 00:23:34.370 align:start position:0% hey thank you can you hear me yep okay um<00:23:32.580> first<00:23:32.880> of<00:23:33.000> all<00:23:33.120> congratulations<00:23:33.840> this<00:23:34.260> is 00:23:34.370 --> 00:23:34.380 align:start position:0% um first of all congratulations this is 00:23:34.380 --> 00:23:35.630 align:start position:0% um first of all congratulations this is amazing 00:23:35.630 --> 00:23:35.640 align:start position:0% amazing 00:23:35.640 --> 00:23:37.130 align:start position:0% amazing um when<00:23:35.940> you<00:23:36.120> launched<00:23:36.480> let's<00:23:36.659> suppose<00:23:37.020> it's 00:23:37.130 --> 00:23:37.140 align:start position:0% um when you launched let's suppose it's 00:23:37.140 --> 00:23:39.289 align:start position:0% um when you launched let's suppose it's early<00:23:37.380> next<00:23:37.620> year<00:23:37.919> obviously<00:23:38.880> it's<00:23:39.000> a<00:23:39.179> very 00:23:39.289 --> 00:23:39.299 align:start position:0% early next year obviously it's a very 00:23:39.299 --> 00:23:42.470 align:start position:0% early next year obviously it's a very complicated<00:23:39.720> system<00:23:40.020> if<00:23:40.980> you<00:23:41.159> find<00:23:41.400> some<00:23:41.940> bug 00:23:42.470 --> 00:23:42.480 align:start position:0% complicated system if you find some bug 00:23:42.480 --> 00:23:44.090 align:start position:0% complicated system if you find some bug or<00:23:42.720> something<00:23:42.960> that<00:23:43.200> needs<00:23:43.440> to<00:23:43.440> be<00:23:43.620> addressed 00:23:44.090 --> 00:23:44.100 align:start position:0% or something that needs to be addressed 00:23:44.100 --> 00:23:46.669 align:start position:0% or something that needs to be addressed what<00:23:44.580> can<00:23:44.760> you<00:23:44.880> do<00:23:45.000> in<00:23:45.120> that<00:23:45.299> situation 00:23:46.669 --> 00:23:46.679 align:start position:0% what can you do in that situation 00:23:46.679 --> 00:23:48.890 align:start position:0% what can you do in that situation with<00:23:47.400> the<00:23:47.640> strapping<00:23:48.000> decentralized<00:23:48.539> systems 00:23:48.890 --> 00:23:48.900 align:start position:0% with the strapping decentralized systems 00:23:48.900 --> 00:23:52.490 align:start position:0% with the strapping decentralized systems is<00:23:49.080> not<00:23:49.380> uh<00:23:49.799> is<00:23:50.340> not<00:23:50.520> an<00:23:50.640> easy<00:23:50.760> topic<00:23:51.240> uh<00:23:52.080> here 00:23:52.490 --> 00:23:52.500 align:start position:0% is not uh is not an easy topic uh here 00:23:52.500 --> 00:23:54.950 align:start position:0% is not uh is not an easy topic uh here we<00:23:52.679> have<00:23:52.860> the<00:23:52.980> experience<00:23:53.340> of<00:23:53.580> Hermes<00:23:54.120> 1.0<00:23:54.659> in 00:23:54.950 --> 00:23:54.960 align:start position:0% we have the experience of Hermes 1.0 in 00:23:54.960 --> 00:23:58.370 align:start position:0% we have the experience of Hermes 1.0 in our<00:23:55.140> team<00:23:55.320> and<00:23:56.100> here<00:23:56.520> you<00:23:56.760> do<00:23:57.120> some<00:23:57.659> I<00:23:58.260> would 00:23:58.370 --> 00:23:58.380 align:start position:0% our team and here you do some I would 00:23:58.380 --> 00:24:01.070 align:start position:0% our team and here you do some I would say<00:23:58.500> nasty<00:23:59.039> tricks<00:23:59.400> uh<00:24:00.179> here<00:24:00.360> is<00:24:00.539> maybe<00:24:00.720> you<00:24:00.960> do 00:24:01.070 --> 00:24:01.080 align:start position:0% say nasty tricks uh here is maybe you do 00:24:01.080 --> 00:24:03.710 align:start position:0% say nasty tricks uh here is maybe you do an<00:24:01.200> upgradability<00:24:01.860> things<00:24:02.700> that<00:24:03.059> you<00:24:03.240> we<00:24:03.539> can 00:24:03.710 --> 00:24:03.720 align:start position:0% an upgradability things that you we can 00:24:03.720 --> 00:24:05.630 align:start position:0% an upgradability things that you we can you<00:24:03.900> can<00:24:04.020> do<00:24:04.140> is<00:24:04.380> an<00:24:04.620> upgrade<00:24:04.980> so<00:24:05.340> you<00:24:05.520> can 00:24:05.630 --> 00:24:05.640 align:start position:0% you can do is an upgrade so you can 00:24:05.640 --> 00:24:06.950 align:start position:0% you can do is an upgrade so you can upgrade<00:24:05.940> the<00:24:06.059> smart<00:24:06.179> contracts<00:24:06.659> with<00:24:06.840> maybe 00:24:06.950 --> 00:24:06.960 align:start position:0% upgrade the smart contracts with maybe 00:24:06.960 --> 00:24:11.690 align:start position:0% upgrade the smart contracts with maybe with<00:24:07.260> a<00:24:07.500> time<00:24:07.620> lock<00:24:08.059> and<00:24:09.059> you<00:24:10.020> can<00:24:10.340> do<00:24:11.340> for 00:24:11.690 --> 00:24:11.700 align:start position:0% with a time lock and you can do for 00:24:11.700 --> 00:24:14.330 align:start position:0% with a time lock and you can do for example<00:24:11.880> is<00:24:12.059> limit<00:24:12.299> the<00:24:12.780> the<00:24:13.080> withdrawal<00:24:14.039> the 00:24:14.330 --> 00:24:14.340 align:start position:0% example is limit the the withdrawal the 00:24:14.340 --> 00:24:16.610 align:start position:0% example is limit the the withdrawal the the<00:24:14.460> withdrawal<00:24:15.240> flow<00:24:15.600> that's<00:24:16.020> leaving<00:24:16.260> the 00:24:16.610 --> 00:24:16.620 align:start position:0% the withdrawal flow that's leaving the 00:24:16.620 --> 00:24:19.549 align:start position:0% the withdrawal flow that's leaving the smart<00:24:17.159> contract<00:24:17.580> so<00:24:17.880> that<00:24:18.120> it's<00:24:18.419> like<00:24:18.780> if<00:24:19.440> you 00:24:19.549 --> 00:24:19.559 align:start position:0% smart contract so that it's like if you 00:24:19.559 --> 00:24:21.649 align:start position:0% smart contract so that it's like if you are<00:24:19.740> working<00:24:19.980> with<00:24:20.820> less<00:24:21.059> as<00:24:21.299> a<00:24:21.480> certain 00:24:21.649 --> 00:24:21.659 align:start position:0% are working with less as a certain 00:24:21.659 --> 00:24:24.470 align:start position:0% are working with less as a certain amount<00:24:22.559> you<00:24:22.980> are<00:24:23.159> purely<00:24:23.580> decentralized<00:24:24.179> but 00:24:24.470 --> 00:24:24.480 align:start position:0% amount you are purely decentralized but 00:24:24.480 --> 00:24:26.330 align:start position:0% amount you are purely decentralized but if<00:24:24.659> you<00:24:24.780> want<00:24:24.900> to<00:24:25.020> run<00:24:25.200> fast<00:24:25.440> and<00:24:25.740> run<00:24:26.039> bigger 00:24:26.330 --> 00:24:26.340 align:start position:0% if you want to run fast and run bigger 00:24:26.340 --> 00:24:28.610 align:start position:0% if you want to run fast and run bigger numbers<00:24:26.580> then<00:24:26.940> you<00:24:27.600> can<00:24:27.840> you<00:24:28.020> have<00:24:28.200> the<00:24:28.320> option 00:24:28.610 --> 00:24:28.620 align:start position:0% numbers then you can you have the option 00:24:28.620 --> 00:24:30.830 align:start position:0% numbers then you can you have the option to<00:24:28.860> go<00:24:28.980> Central<00:24:29.220> lights<00:24:29.580> or<00:24:29.820> just<00:24:30.059> or<00:24:30.299> or<00:24:30.539> white 00:24:30.830 --> 00:24:30.840 align:start position:0% to go Central lights or just or or white 00:24:30.840 --> 00:24:33.169 align:start position:0% to go Central lights or just or or white until<00:24:31.140> you<00:24:31.380> you<00:24:31.559> there<00:24:31.860> are<00:24:31.980> some<00:24:32.100> tricks<00:24:32.520> for 00:24:33.169 --> 00:24:33.179 align:start position:0% until you you there are some tricks for 00:24:33.179 --> 00:24:35.330 align:start position:0% until you you there are some tricks for Buddha<00:24:33.780> strapping<00:24:34.200> but<00:24:34.500> this<00:24:34.679> is<00:24:34.919> our<00:24:35.100> just 00:24:35.330 --> 00:24:35.340 align:start position:0% Buddha strapping but this is our just 00:24:35.340 --> 00:24:38.750 align:start position:0% Buddha strapping but this is our just temporary<00:24:36.080> uh<00:24:37.080> Solutions<00:24:37.500> until<00:24:38.159> we<00:24:38.580> feel 00:24:38.750 --> 00:24:38.760 align:start position:0% temporary uh Solutions until we feel 00:24:38.760 --> 00:24:40.789 align:start position:0% temporary uh Solutions until we feel comfortable<00:24:39.240> at<00:24:39.600> some<00:24:39.780> point<00:24:39.900> the<00:24:40.380> roll<00:24:40.559> up 00:24:40.789 --> 00:24:40.799 align:start position:0% comfortable at some point the roll up 00:24:40.799 --> 00:24:41.649 align:start position:0% comfortable at some point the roll up should 00:24:41.649 --> 00:24:41.659 align:start position:0% should 00:24:41.659 --> 00:24:43.850 align:start position:0% should go<00:24:42.659> along<00:24:42.840> we<00:24:43.380> are<00:24:43.500> building<00:24:43.559> on<00:24:43.740> the 00:24:43.850 --> 00:24:43.860 align:start position:0% go along we are building on the 00:24:43.860 --> 00:24:45.890 align:start position:0% go along we are building on the centralized<00:24:44.280> system<00:24:44.400> and<00:24:44.880> and<00:24:45.179> it<00:24:45.539> should<00:24:45.720> be 00:24:45.890 --> 00:24:45.900 align:start position:0% centralized system and and it should be 00:24:45.900 --> 00:24:48.409 align:start position:0% centralized system and and it should be safe<00:24:46.020> enough<00:24:46.200> here<00:24:46.440> is<00:24:46.620> uh<00:24:47.400> we<00:24:47.880> are<00:24:48.000> managing 00:24:48.409 --> 00:24:48.419 align:start position:0% safe enough here is uh we are managing 00:24:48.419 --> 00:24:50.570 align:start position:0% safe enough here is uh we are managing that<00:24:48.720> in<00:24:49.020> the<00:24:49.200> in<00:24:49.559> the<00:24:49.740> in<00:24:50.039> the<00:24:50.280> in<00:24:50.400> the 00:24:50.570 --> 00:24:50.580 align:start position:0% that in the in the in the in the 00:24:50.580 --> 00:24:52.190 align:start position:0% that in the in the in the in the beginning 00:24:52.190 --> 00:24:52.200 align:start position:0% beginning 00:24:52.200 --> 00:24:54.350 align:start position:0% beginning thank<00:24:52.679> you<00:24:52.799> so<00:24:52.919> much<00:24:53.100> Jersey<00:24:53.520> valina<00:24:54.059> please 00:24:54.350 --> 00:24:54.360 align:start position:0% thank you so much Jersey valina please 00:24:54.360 --> 00:24:55.760 align:start position:0% thank you so much Jersey valina please give<00:24:54.720> him<00:24:54.900> any<00:24:55.140> thoughts 00:24:55.760 --> 00:24:55.770 align:start position:0% give him any thoughts 00:24:55.770 --> 00:24:59.049 align:start position:0% give him any thoughts [Applause]