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:13.030 align:start position:0% [Music] 00:00:13.030 --> 00:00:13.040 align:start position:0% 00:00:13.040 --> 00:00:15.770 align:start position:0% we're<00:00:14.040> going<00:00:14.160> to<00:00:14.280> be<00:00:14.340> talking<00:00:14.519> in<00:00:14.759> English<00:00:14.940> and 00:00:15.770 --> 00:00:15.780 align:start position:0% we're going to be talking in English and 00:00:15.780 --> 00:00:17.090 align:start position:0% we're going to be talking in English and if<00:00:15.960> you<00:00:16.080> don't<00:00:16.199> understand<00:00:16.320> anything<00:00:16.680> on<00:00:16.980> the 00:00:17.090 --> 00:00:17.100 align:start position:0% if you don't understand anything on the 00:00:17.100 --> 00:00:18.890 align:start position:0% if you don't understand anything on the slides<00:00:17.400> please<00:00:17.520> let<00:00:17.699> me<00:00:17.820> know<00:00:17.940> no<00:00:18.119> problem<00:00:18.359> but 00:00:18.890 --> 00:00:18.900 align:start position:0% slides please let me know no problem but 00:00:18.900 --> 00:00:23.029 align:start position:0% slides please let me know no problem but just<00:00:19.440> focus<00:00:19.980> on<00:00:20.160> me 00:00:23.029 --> 00:00:23.039 align:start position:0% 00:00:23.039 --> 00:00:24.950 align:start position:0% so<00:00:23.400> on<00:00:23.520> the<00:00:23.640> layer<00:00:23.880> one<00:00:24.000> we<00:00:24.240> had<00:00:24.420> amazing 00:00:24.950 --> 00:00:24.960 align:start position:0% so on the layer one we had amazing 00:00:24.960 --> 00:00:26.630 align:start position:0% so on the layer one we had amazing applications<00:00:25.500> we<00:00:26.039> got<00:00:26.279> a<00:00:26.460> lot<00:00:26.580> of 00:00:26.630 --> 00:00:26.640 align:start position:0% applications we got a lot of 00:00:26.640 --> 00:00:28.370 align:start position:0% applications we got a lot of applications<00:00:27.000> very<00:00:27.359> interesting<00:00:28.080> for 00:00:28.370 --> 00:00:28.380 align:start position:0% applications very interesting for 00:00:28.380 --> 00:00:30.890 align:start position:0% applications very interesting for example<00:00:28.680> amms 00:00:30.890 --> 00:00:30.900 align:start position:0% example amms 00:00:30.900 --> 00:00:33.350 align:start position:0% example amms that<00:00:31.560> could<00:00:31.920> let<00:00:32.220> you<00:00:32.520> transact<00:00:33.120> with 00:00:33.350 --> 00:00:33.360 align:start position:0% that could let you transact with 00:00:33.360 --> 00:00:35.389 align:start position:0% that could let you transact with different<00:00:33.540> tokens<00:00:34.020> but<00:00:34.680> these<00:00:34.980> were<00:00:35.160> very 00:00:35.389 --> 00:00:35.399 align:start position:0% different tokens but these were very 00:00:35.399 --> 00:00:37.370 align:start position:0% different tokens but these were very very<00:00:35.579> very<00:00:35.820> expensive<00:00:36.360> right 00:00:37.370 --> 00:00:37.380 align:start position:0% very very expensive right 00:00:37.380 --> 00:00:40.069 align:start position:0% very very expensive right we<00:00:37.800> also<00:00:37.980> had<00:00:38.100> oracles<00:00:38.700> that<00:00:39.300> allow<00:00:39.719> us<00:00:39.899> to 00:00:40.069 --> 00:00:40.079 align:start position:0% we also had oracles that allow us to 00:00:40.079 --> 00:00:42.470 align:start position:0% we also had oracles that allow us to introduce<00:00:40.500> data<00:00:40.920> of<00:00:41.040> chain<00:00:41.340> into<00:00:41.879> one<00:00:42.180> chain 00:00:42.470 --> 00:00:42.480 align:start position:0% introduce data of chain into one chain 00:00:42.480 --> 00:00:45.590 align:start position:0% introduce data of chain into one chain right<00:00:43.079> but<00:00:43.739> it<00:00:43.980> was<00:00:44.160> also<00:00:44.460> very<00:00:44.579> expensive 00:00:45.590 --> 00:00:45.600 align:start position:0% right but it was also very expensive 00:00:45.600 --> 00:00:48.950 align:start position:0% right but it was also very expensive moving<00:00:46.140> data<00:00:46.620> on<00:00:46.980> chain<00:00:47.219> is<00:00:47.520> expensive 00:00:48.950 --> 00:00:48.960 align:start position:0% moving data on chain is expensive 00:00:48.960 --> 00:00:50.810 align:start position:0% moving data on chain is expensive we<00:00:49.260> also<00:00:49.500> had<00:00:49.620> gaming<00:00:50.039> where<00:00:50.340> you<00:00:50.520> can<00:00:50.640> have 00:00:50.810 --> 00:00:50.820 align:start position:0% we also had gaming where you can have 00:00:50.820 --> 00:00:53.029 align:start position:0% we also had gaming where you can have nfts<00:00:51.600> very<00:00:51.780> cute<00:00:52.020> nfts<00:00:52.559> you<00:00:52.680> can<00:00:52.739> have<00:00:52.860> your 00:00:53.029 --> 00:00:53.039 align:start position:0% nfts very cute nfts you can have your 00:00:53.039 --> 00:00:55.549 align:start position:0% nfts very cute nfts you can have your sword<00:00:53.280> for<00:00:53.640> your<00:00:53.760> game<00:00:54.000> you're<00:00:54.660> gone<00:00:54.960> and<00:00:55.379> so 00:00:55.549 --> 00:00:55.559 align:start position:0% sword for your game you're gone and so 00:00:55.559 --> 00:00:58.189 align:start position:0% sword for your game you're gone and so on<00:00:55.800> you<00:00:56.039> can<00:00:56.160> maybe<00:00:56.340> move<00:00:57.000> it<00:00:57.180> to<00:00:57.239> another<00:00:57.360> game 00:00:58.189 --> 00:00:58.199 align:start position:0% on you can maybe move it to another game 00:00:58.199 --> 00:01:00.830 align:start position:0% on you can maybe move it to another game but<00:00:58.559> still<00:00:59.100> the<00:00:59.340> game<00:00:59.460> was 00:01:00.830 --> 00:01:00.840 align:start position:0% but still the game was 00:01:00.840 --> 00:01:04.490 align:start position:0% but still the game was was<00:01:01.680> lit<00:01:02.219> was<00:01:02.520> directed<00:01:03.059> by<00:01:03.719> a<00:01:03.899> single<00:01:04.199> entity 00:01:04.490 --> 00:01:04.500 align:start position:0% was lit was directed by a single entity 00:01:04.500 --> 00:01:06.950 align:start position:0% was lit was directed by a single entity that<00:01:04.739> had<00:01:04.920> the<00:01:05.100> control<00:01:05.280> over<00:01:05.640> the<00:01:05.880> game 00:01:06.950 --> 00:01:06.960 align:start position:0% that had the control over the game 00:01:06.960 --> 00:01:09.590 align:start position:0% that had the control over the game so<00:01:07.380> the<00:01:07.500> game<00:01:07.619> Logistics<00:01:08.100> the<00:01:08.400> game<00:01:08.520> logic<00:01:09.119> was 00:01:09.590 --> 00:01:09.600 align:start position:0% so the game Logistics the game logic was 00:01:09.600 --> 00:01:12.050 align:start position:0% so the game Logistics the game logic was not<00:01:09.840> on<00:01:10.080> chain<00:01:10.380> it<00:01:10.680> was<00:01:10.920> not<00:01:11.040> Auto<00:01:11.340> regulate<00:01:11.880> it 00:01:12.050 --> 00:01:12.060 align:start position:0% not on chain it was not Auto regulate it 00:01:12.060 --> 00:01:14.750 align:start position:0% not on chain it was not Auto regulate it yes<00:01:12.540> because<00:01:12.720> it's<00:01:12.960> very<00:01:13.140> expensive<00:01:13.560> right 00:01:14.750 --> 00:01:14.760 align:start position:0% yes because it's very expensive right 00:01:14.760 --> 00:01:17.410 align:start position:0% yes because it's very expensive right also<00:01:15.299> we<00:01:15.420> had<00:01:15.540> both<00:01:15.720> in<00:01:15.960> apps<00:01:16.320> but<00:01:16.680> also<00:01:17.040> again 00:01:17.410 --> 00:01:17.420 align:start position:0% also we had both in apps but also again 00:01:17.420 --> 00:01:19.609 align:start position:0% also we had both in apps but also again writing<00:01:18.420> in<00:01:18.600> the<00:01:18.720> storage<00:01:18.840> right<00:01:19.260> into<00:01:19.380> the 00:01:19.609 --> 00:01:19.619 align:start position:0% writing in the storage right into the 00:01:19.619 --> 00:01:21.590 align:start position:0% writing in the storage right into the blockchain<00:01:19.979> is<00:01:20.159> very<00:01:20.340> expensive<00:01:20.820> so<00:01:21.180> voting 00:01:21.590 --> 00:01:21.600 align:start position:0% blockchain is very expensive so voting 00:01:21.600 --> 00:01:23.749 align:start position:0% blockchain is very expensive so voting was<00:01:21.840> also<00:01:22.200> real<00:01:22.380> expensive<00:01:22.799> on<00:01:22.979> layer<00:01:23.280> one<00:01:23.400> so 00:01:23.749 --> 00:01:23.759 align:start position:0% was also real expensive on layer one so 00:01:23.759 --> 00:01:25.070 align:start position:0% was also real expensive on layer one so this<00:01:23.939> is 00:01:25.070 --> 00:01:25.080 align:start position:0% this is 00:01:25.080 --> 00:01:26.810 align:start position:0% this is very<00:01:25.619> interesting<00:01:25.979> applications<00:01:26.460> that<00:01:26.640> we 00:01:26.810 --> 00:01:26.820 align:start position:0% very interesting applications that we 00:01:26.820 --> 00:01:29.450 align:start position:0% very interesting applications that we have<00:01:27.060> in<00:01:27.600> the<00:01:27.780> layer<00:01:28.020> one<00:01:28.200> both<00:01:28.740> that 00:01:29.450 --> 00:01:29.460 align:start position:0% have in the layer one both that 00:01:29.460 --> 00:01:31.070 align:start position:0% have in the layer one both that introduces<00:01:29.939> problems<00:01:30.299> when<00:01:30.540> we<00:01:30.780> are<00:01:30.960> talking 00:01:31.070 --> 00:01:31.080 align:start position:0% introduces problems when we are talking 00:01:31.080 --> 00:01:34.070 align:start position:0% introduces problems when we are talking out<00:01:31.380> costs<00:01:32.040> so<00:01:32.640> we<00:01:32.939> know<00:01:33.119> the<00:01:33.299> states<00:01:33.540> the 00:01:34.070 --> 00:01:34.080 align:start position:0% out costs so we know the states the 00:01:34.080 --> 00:01:36.230 align:start position:0% out costs so we know the states the current<00:01:34.200> state<00:01:34.500> of<00:01:34.680> things<00:01:34.860> is<00:01:35.400> either<00:01:35.939> we 00:01:36.230 --> 00:01:36.240 align:start position:0% current state of things is either we 00:01:36.240 --> 00:01:38.030 align:start position:0% current state of things is either we have<00:01:36.420> a<00:01:36.600> huge<00:01:36.840> machine<00:01:37.020> that<00:01:37.500> is<00:01:37.619> processing 00:01:38.030 --> 00:01:38.040 align:start position:0% have a huge machine that is processing 00:01:38.040 --> 00:01:39.890 align:start position:0% have a huge machine that is processing everything<00:01:38.280> we<00:01:38.759> know<00:01:38.939> this<00:01:39.180> and<00:01:39.479> for<00:01:39.720> example 00:01:39.890 --> 00:01:39.900 align:start position:0% everything we know this and for example 00:01:39.900 --> 00:01:44.149 align:start position:0% everything we know this and for example Banks<00:01:40.500> Acorn<00:01:41.280> apis<00:01:42.320> companies<00:01:43.320> startups<00:01:44.040> and 00:01:44.149 --> 00:01:44.159 align:start position:0% Banks Acorn apis companies startups and 00:01:44.159 --> 00:01:45.950 align:start position:0% Banks Acorn apis companies startups and so<00:01:44.340> on<00:01:44.460> very<00:01:45.000> huge<00:01:45.360> machines<00:01:45.600> they<00:01:45.780> can 00:01:45.950 --> 00:01:45.960 align:start position:0% so on very huge machines they can 00:01:45.960 --> 00:01:47.390 align:start position:0% so on very huge machines they can process<00:01:46.320> a<00:01:46.500> lot<00:01:46.560> of<00:01:46.560> transactions<00:01:47.159> very 00:01:47.390 --> 00:01:47.400 align:start position:0% process a lot of transactions very 00:01:47.400 --> 00:01:48.590 align:start position:0% process a lot of transactions very quickly 00:01:48.590 --> 00:01:48.600 align:start position:0% quickly 00:01:48.600 --> 00:01:50.450 align:start position:0% quickly and<00:01:49.200> now<00:01:49.439> we're<00:01:49.619> looking<00:01:49.799> at<00:01:49.979> the<00:01:50.100> blue<00:01:50.220> Parts 00:01:50.450 --> 00:01:50.460 align:start position:0% and now we're looking at the blue Parts 00:01:50.460 --> 00:01:51.889 align:start position:0% and now we're looking at the blue Parts where<00:01:50.939> we<00:01:51.060> are<00:01:51.240> trying<00:01:51.360> to<00:01:51.540> create<00:01:51.720> a 00:01:51.889 --> 00:01:51.899 align:start position:0% where we are trying to create a 00:01:51.899 --> 00:01:54.289 align:start position:0% where we are trying to create a centralized<00:01:52.500> system<00:01:52.740> which<00:01:53.220> is<00:01:53.399> when<00:01:53.759> a<00:01:54.180> lot 00:01:54.289 --> 00:01:54.299 align:start position:0% centralized system which is when a lot 00:01:54.299 --> 00:01:57.170 align:start position:0% centralized system which is when a lot of<00:01:54.360> persons<00:01:54.840> can<00:01:55.200> verify<00:01:55.680> the<00:01:56.040> Integrity<00:01:56.460> of 00:01:57.170 --> 00:01:57.180 align:start position:0% of persons can verify the Integrity of 00:01:57.180 --> 00:01:58.850 align:start position:0% of persons can verify the Integrity of the<00:01:57.360> system<00:01:57.479> right<00:01:57.840> this<00:01:58.439> is<00:01:58.619> what<00:01:58.680> we're 00:01:58.850 --> 00:01:58.860 align:start position:0% the system right this is what we're 00:01:58.860 --> 00:01:59.990 align:start position:0% the system right this is what we're trying<00:01:59.100> to<00:01:59.220> do 00:01:59.990 --> 00:02:00.000 align:start position:0% trying to do 00:02:00.000 --> 00:02:01.910 align:start position:0% trying to do the<00:02:00.540> problem<00:02:00.720> is<00:02:01.020> that<00:02:01.140> this<00:02:01.320> is<00:02:01.500> very<00:02:01.680> slow 00:02:01.910 --> 00:02:01.920 align:start position:0% the problem is that this is very slow 00:02:01.920 --> 00:02:03.950 align:start position:0% the problem is that this is very slow and<00:02:02.280> this<00:02:02.460> is<00:02:02.579> very<00:02:02.700> expensive<00:02:03.180> and<00:02:03.840> the 00:02:03.950 --> 00:02:03.960 align:start position:0% and this is very expensive and the 00:02:03.960 --> 00:02:06.109 align:start position:0% and this is very expensive and the computation<00:02:04.259> repeated<00:02:04.740> itself<00:02:05.340> various 00:02:06.109 --> 00:02:06.119 align:start position:0% computation repeated itself various 00:02:06.119 --> 00:02:08.449 align:start position:0% computation repeated itself various times<00:02:06.360> at<00:02:07.200> different<00:02:07.380> points 00:02:08.449 --> 00:02:08.459 align:start position:0% times at different points 00:02:08.459 --> 00:02:10.969 align:start position:0% times at different points so<00:02:08.940> it's<00:02:09.060> not<00:02:09.239> optimal<00:02:09.660> for<00:02:09.840> scalability 00:02:10.969 --> 00:02:10.979 align:start position:0% so it's not optimal for scalability 00:02:10.979 --> 00:02:13.010 align:start position:0% so it's not optimal for scalability of<00:02:11.280> course<00:02:11.400> this<00:02:11.640> was<00:02:11.819> a<00:02:11.940> choice<00:02:12.120> when<00:02:12.480> we 00:02:13.010 --> 00:02:13.020 align:start position:0% of course this was a choice when we 00:02:13.020 --> 00:02:14.930 align:start position:0% of course this was a choice when we decided<00:02:13.680> to<00:02:13.739> create<00:02:13.920> theorem<00:02:14.400> we<00:02:14.580> wanted<00:02:14.700> this 00:02:14.930 --> 00:02:14.940 align:start position:0% decided to create theorem we wanted this 00:02:14.940 --> 00:02:17.390 align:start position:0% decided to create theorem we wanted this centralization<00:02:15.780> we<00:02:16.020> wanted<00:02:16.200> security<00:02:16.560> it<00:02:17.280> was 00:02:17.390 --> 00:02:17.400 align:start position:0% centralization we wanted security it was 00:02:17.400 --> 00:02:19.309 align:start position:0% centralization we wanted security it was a<00:02:17.580> choice<00:02:17.760> to<00:02:18.360> sacrifice<00:02:18.660> at<00:02:18.840> that<00:02:19.020> moment's 00:02:19.309 --> 00:02:19.319 align:start position:0% a choice to sacrifice at that moment's 00:02:19.319 --> 00:02:20.449 align:start position:0% a choice to sacrifice at that moment's scalability 00:02:20.449 --> 00:02:20.459 align:start position:0% scalability 00:02:20.459 --> 00:02:22.369 align:start position:0% scalability but<00:02:20.879> now<00:02:21.060> we<00:02:21.300> know<00:02:21.420> better<00:02:21.660> and<00:02:21.959> we<00:02:22.140> can<00:02:22.260> do 00:02:22.369 --> 00:02:22.379 align:start position:0% but now we know better and we can do 00:02:22.379 --> 00:02:24.650 align:start position:0% but now we know better and we can do better<00:02:22.560> stuff<00:02:22.920> so<00:02:23.580> the<00:02:23.700> question<00:02:23.879> is<00:02:24.120> can<00:02:24.480> we 00:02:24.650 --> 00:02:24.660 align:start position:0% better stuff so the question is can we 00:02:24.660 --> 00:02:26.089 align:start position:0% better stuff so the question is can we head<00:02:24.840> can<00:02:25.200> we<00:02:25.260> get<00:02:25.379> the<00:02:25.500> centralization 00:02:26.089 --> 00:02:26.099 align:start position:0% head can we get the centralization 00:02:26.099 --> 00:02:28.970 align:start position:0% head can we get the centralization security<00:02:26.459> and<00:02:27.180> also<00:02:27.420> scaling<00:02:27.959> yes<00:02:28.500> we<00:02:28.739> can<00:02:28.860> do 00:02:28.970 --> 00:02:28.980 align:start position:0% security and also scaling yes we can do 00:02:28.980 --> 00:02:32.449 align:start position:0% security and also scaling yes we can do with<00:02:29.220> your<00:02:29.340> knowledge<00:02:29.700> roles 00:02:32.449 --> 00:02:32.459 align:start position:0% 00:02:32.459 --> 00:02:34.790 align:start position:0% and<00:02:33.060> we<00:02:33.300> are<00:02:33.480> here<00:02:33.599> today<00:02:33.840> to<00:02:34.140> talk<00:02:34.319> about<00:02:34.500> star 00:02:34.790 --> 00:02:34.800 align:start position:0% and we are here today to talk about star 00:02:34.800 --> 00:02:35.990 align:start position:0% and we are here today to talk about star Nets 00:02:35.990 --> 00:02:36.000 align:start position:0% Nets 00:02:36.000 --> 00:02:37.790 align:start position:0% Nets so<00:02:36.599> we're<00:02:36.780> talking<00:02:36.959> about<00:02:37.080> a<00:02:37.260> platformer 00:02:37.790 --> 00:02:37.800 align:start position:0% so we're talking about a platformer 00:02:37.800 --> 00:02:40.369 align:start position:0% so we're talking about a platformer layer<00:02:38.099> 2<00:02:38.160> that<00:02:38.400> is<00:02:38.580> secure<00:02:38.940> by<00:02:39.420> ethereum 00:02:40.369 --> 00:02:40.379 align:start position:0% layer 2 that is secure by ethereum 00:02:40.379 --> 00:02:42.830 align:start position:0% layer 2 that is secure by ethereum it<00:02:40.860> allows<00:02:41.220> you<00:02:41.280> to<00:02:41.459> create<00:02:41.700> smart<00:02:42.300> contracts 00:02:42.830 --> 00:02:42.840 align:start position:0% it allows you to create smart contracts 00:02:42.840 --> 00:02:44.630 align:start position:0% it allows you to create smart contracts General<00:02:43.140> smart<00:02:43.620> contracts<00:02:44.160> it's<00:02:44.400> too 00:02:44.630 --> 00:02:44.640 align:start position:0% General smart contracts it's too 00:02:44.640 --> 00:02:46.009 align:start position:0% General smart contracts it's too incomplete 00:02:46.009 --> 00:02:46.019 align:start position:0% incomplete 00:02:46.019 --> 00:02:51.410 align:start position:0% incomplete the<00:02:46.500> cost<00:02:46.620> of<00:02:46.800> execution<00:02:47.160> is<00:02:47.519> much<00:02:47.760> lower<00:02:48.000> and 00:02:51.410 --> 00:02:51.420 align:start position:0% 00:02:51.420 --> 00:02:53.390 align:start position:0% you<00:02:51.840> can<00:02:51.900> create<00:02:52.080> amazing<00:02:52.620> things<00:02:52.860> that<00:02:53.220> are 00:02:53.390 --> 00:02:53.400 align:start position:0% you can create amazing things that are 00:02:53.400 --> 00:02:55.130 align:start position:0% you can create amazing things that are not<00:02:53.519> possible<00:02:53.879> even<00:02:54.180> imaginable<00:02:54.780> in<00:02:55.019> the 00:02:55.130 --> 00:02:55.140 align:start position:0% not possible even imaginable in the 00:02:55.140 --> 00:02:58.430 align:start position:0% not possible even imaginable in the layer<00:02:55.379> one<00:02:55.500> so<00:02:56.040> we<00:02:56.340> can<00:02:56.459> get<00:02:56.700> much<00:02:57.480> more<00:02:57.780> for 00:02:58.430 --> 00:02:58.440 align:start position:0% layer one so we can get much more for 00:02:58.440 --> 00:03:02.869 align:start position:0% layer one so we can get much more for each<00:02:58.739> piece<00:02:59.220> of<00:02:59.340> gas 00:03:02.869 --> 00:03:02.879 align:start position:0% 00:03:02.879 --> 00:03:04.550 align:start position:0% so<00:03:03.180> this<00:03:03.300> is<00:03:03.420> a<00:03:03.599> quote<00:03:03.720> from<00:03:03.900> Albion<00:03:04.319> session 00:03:04.550 --> 00:03:04.560 align:start position:0% so this is a quote from Albion session 00:03:04.560 --> 00:03:05.809 align:start position:0% so this is a quote from Albion session our<00:03:04.860> founder 00:03:05.809 --> 00:03:05.819 align:start position:0% our founder 00:03:05.819 --> 00:03:09.410 align:start position:0% our founder at<00:03:06.239> Bangles<00:03:06.660> in<00:03:06.959> the<00:03:07.200> 29th<00:03:07.739> of<00:03:07.860> July 00:03:09.410 --> 00:03:09.420 align:start position:0% at Bangles in the 29th of July 00:03:09.420 --> 00:03:11.030 align:start position:0% at Bangles in the 29th of July he's<00:03:09.840> talking<00:03:10.080> about<00:03:10.319> the<00:03:10.500> objective<00:03:10.860> of 00:03:11.030 --> 00:03:11.040 align:start position:0% he's talking about the objective of 00:03:11.040 --> 00:03:13.070 align:start position:0% he's talking about the objective of starnet<00:03:11.459> which<00:03:11.640> is<00:03:11.760> creating<00:03:12.180> a<00:03:12.420> solution<00:03:12.780> for 00:03:13.070 --> 00:03:13.080 align:start position:0% starnet which is creating a solution for 00:03:13.080 --> 00:03:16.009 align:start position:0% starnet which is creating a solution for scaling<00:03:13.560> that<00:03:13.800> is<00:03:14.040> focus<00:03:14.940> focus<00:03:15.420> only<00:03:15.659> on 00:03:16.009 --> 00:03:16.019 align:start position:0% scaling that is focus focus only on 00:03:16.019 --> 00:03:18.470 align:start position:0% scaling that is focus focus only on scaling<00:03:16.440> theorem<00:03:16.739> and<00:03:16.980> this<00:03:17.099> is<00:03:17.220> called<00:03:17.400> Cairo 00:03:18.470 --> 00:03:18.480 align:start position:0% scaling theorem and this is called Cairo 00:03:18.480 --> 00:03:21.350 align:start position:0% scaling theorem and this is called Cairo so<00:03:19.019> our<00:03:19.260> Star<00:03:19.500> Wars<00:03:19.860> are<00:03:19.980> experts<00:03:20.640> on<00:03:21.000> both<00:03:21.180> the 00:03:21.350 --> 00:03:21.360 align:start position:0% so our Star Wars are experts on both the 00:03:21.360 --> 00:03:23.330 align:start position:0% so our Star Wars are experts on both the attribution<00:03:21.840> machine<00:03:22.200> and<00:03:22.680> also<00:03:23.040> creating 00:03:23.330 --> 00:03:23.340 align:start position:0% attribution machine and also creating 00:03:23.340 --> 00:03:26.449 align:start position:0% attribution machine and also creating stock<00:03:23.640> systems<00:03:24.180> and<00:03:24.900> there<00:03:25.080> was<00:03:25.319> a<00:03:25.560> conscious 00:03:26.449 --> 00:03:26.459 align:start position:0% stock systems and there was a conscious 00:03:26.459 --> 00:03:29.330 align:start position:0% stock systems and there was a conscious choice<00:03:26.760> not<00:03:27.180> to<00:03:27.360> use<00:03:27.480> the<00:03:27.599> evm<00:03:28.080> to<00:03:28.379> scale 00:03:29.330 --> 00:03:29.340 align:start position:0% choice not to use the evm to scale 00:03:29.340 --> 00:03:31.250 align:start position:0% choice not to use the evm to scale we<00:03:29.819> created<00:03:30.060> a<00:03:30.300> new<00:03:30.420> virtual<00:03:30.840> machine<00:03:31.019> called 00:03:31.250 --> 00:03:31.260 align:start position:0% we created a new virtual machine called 00:03:31.260 --> 00:03:33.710 align:start position:0% we created a new virtual machine called Cairo<00:03:31.800> this<00:03:32.400> is<00:03:32.519> this<00:03:32.700> WhatsApp<00:03:33.060> comes<00:03:33.480> choice 00:03:33.710 --> 00:03:33.720 align:start position:0% Cairo this is this WhatsApp comes choice 00:03:33.720 --> 00:03:36.110 align:start position:0% Cairo this is this WhatsApp comes choice because<00:03:34.080> we<00:03:34.739> believe<00:03:34.860> this<00:03:35.220> is<00:03:35.340> a<00:03:35.580> way<00:03:35.760> to 00:03:36.110 --> 00:03:36.120 align:start position:0% because we believe this is a way to 00:03:36.120 --> 00:03:41.030 align:start position:0% because we believe this is a way to achieve<00:03:36.599> the<00:03:36.900> biggest<00:03:37.019> scale 00:03:41.030 --> 00:03:41.040 align:start position:0% 00:03:41.040 --> 00:03:43.070 align:start position:0% and<00:03:41.340> this<00:03:41.459> scaling<00:03:41.940> is<00:03:42.120> going<00:03:42.299> to<00:03:42.480> it's<00:03:42.900> going 00:03:43.070 --> 00:03:43.080 align:start position:0% and this scaling is going to it's going 00:03:43.080 --> 00:03:45.830 align:start position:0% and this scaling is going to it's going to<00:03:43.200> come<00:03:43.379> from<00:03:43.980> Smart<00:03:44.819> contrast<00:03:45.180> with<00:03:45.420> them<00:03:45.599> in 00:03:45.830 --> 00:03:45.840 align:start position:0% to come from Smart contrast with them in 00:03:45.840 --> 00:03:49.190 align:start position:0% to come from Smart contrast with them in Cairo<00:03:46.200> in<00:03:46.860> Cairo<00:03:47.400> is<00:03:47.580> a<00:03:47.760> virtual<00:03:48.060> machine<00:03:48.840> but 00:03:49.190 --> 00:03:49.200 align:start position:0% Cairo in Cairo is a virtual machine but 00:03:49.200 --> 00:03:51.890 align:start position:0% Cairo in Cairo is a virtual machine but also<00:03:49.440> language<00:03:49.680> we<00:03:49.980> have 00:03:51.890 --> 00:03:51.900 align:start position:0% also language we have 00:03:51.900 --> 00:03:53.690 align:start position:0% also language we have so<00:03:52.319> what<00:03:52.500> is<00:03:52.620> Cairo 00:03:53.690 --> 00:03:53.700 align:start position:0% so what is Cairo 00:03:53.700 --> 00:03:55.869 align:start position:0% so what is Cairo currents<00:03:54.480> are<00:03:54.480> doing<00:03:54.599> complete<00:03:55.080> language 00:03:55.869 --> 00:03:55.879 align:start position:0% currents are doing complete language 00:03:55.879 --> 00:03:57.949 align:start position:0% currents are doing complete language programming<00:03:56.879> language<00:03:57.060> that<00:03:57.480> allows<00:03:57.720> you<00:03:57.840> to 00:03:57.949 --> 00:03:57.959 align:start position:0% programming language that allows you to 00:03:57.959 --> 00:04:00.890 align:start position:0% programming language that allows you to create<00:03:58.200> brewable<00:03:59.040> programs<00:03:59.940> in<00:04:00.360> this<00:04:00.540> case<00:04:00.720> in 00:04:00.890 --> 00:04:00.900 align:start position:0% create brewable programs in this case in 00:04:00.900 --> 00:04:03.890 align:start position:0% create brewable programs in this case in Spanish 00:04:03.890 --> 00:04:03.900 align:start position:0% 00:04:03.900 --> 00:04:05.809 align:start position:0% you<00:04:04.319> can<00:04:04.379> execute<00:04:04.739> your<00:04:04.920> Cairo<00:04:05.340> program<00:04:05.519> and 00:04:05.809 --> 00:04:05.819 align:start position:0% you can execute your Cairo program and 00:04:05.819 --> 00:04:08.149 align:start position:0% you can execute your Cairo program and then<00:04:05.940> you<00:04:06.120> can<00:04:06.299> prove<00:04:06.720> a<00:04:07.019> smart<00:04:07.500> contract<00:04:07.920> on 00:04:08.149 --> 00:04:08.159 align:start position:0% then you can prove a smart contract on 00:04:08.159 --> 00:04:10.729 align:start position:0% then you can prove a smart contract on the<00:04:08.280> layer<00:04:08.519> 1<00:04:08.640> on<00:04:08.879> assume<00:04:09.480> that<00:04:09.959> this<00:04:10.439> a 00:04:10.729 --> 00:04:10.739 align:start position:0% the layer 1 on assume that this a 00:04:10.739 --> 00:04:12.770 align:start position:0% the layer 1 on assume that this a transaction<00:04:11.159> was<00:04:11.580> correct 00:04:12.770 --> 00:04:12.780 align:start position:0% transaction was correct 00:04:12.780 --> 00:04:17.090 align:start position:0% transaction was correct this<00:04:13.200> allows<00:04:13.500> us<00:04:13.620> to<00:04:13.739> have<00:04:13.980> much<00:04:14.519> more 00:04:17.090 --> 00:04:17.100 align:start position:0% 00:04:17.100 --> 00:04:20.270 align:start position:0% much<00:04:17.639> cheaper<00:04:18.239> transactions<00:04:19.199> cost<00:04:19.440> and 00:04:20.270 --> 00:04:20.280 align:start position:0% much cheaper transactions cost and 00:04:20.280 --> 00:04:22.670 align:start position:0% much cheaper transactions cost and because<00:04:20.699> Pro<00:04:21.359> when<00:04:21.900> the<00:04:22.019> smart<00:04:22.139> contract<00:04:22.500> on 00:04:22.670 --> 00:04:22.680 align:start position:0% because Pro when the smart contract on 00:04:22.680 --> 00:04:24.050 align:start position:0% because Pro when the smart contract on the<00:04:22.800> layer<00:04:22.979> one 00:04:24.050 --> 00:04:24.060 align:start position:0% the layer one 00:04:24.060 --> 00:04:26.390 align:start position:0% the layer one Valley<00:04:24.900> days<00:04:25.259> that<00:04:25.440> this<00:04:25.560> proof<00:04:25.860> is<00:04:26.040> correct 00:04:26.390 --> 00:04:26.400 align:start position:0% Valley days that this proof is correct 00:04:26.400 --> 00:04:29.150 align:start position:0% Valley days that this proof is correct it's<00:04:26.940> much<00:04:27.240> cheaper<00:04:28.020> than<00:04:28.500> running<00:04:28.800> the 00:04:29.150 --> 00:04:29.160 align:start position:0% it's much cheaper than running the 00:04:29.160 --> 00:04:31.370 align:start position:0% it's much cheaper than running the transaction<00:04:29.460> itself<00:04:29.880> so<00:04:30.600> this<00:04:30.720> allows<00:04:31.080> us<00:04:31.199> to 00:04:31.370 --> 00:04:31.380 align:start position:0% transaction itself so this allows us to 00:04:31.380 --> 00:04:33.830 align:start position:0% transaction itself so this allows us to create<00:04:31.500> more<00:04:32.280> to<00:04:32.520> get<00:04:32.759> much<00:04:33.120> more<00:04:33.360> scalable 00:04:33.830 --> 00:04:33.840 align:start position:0% create more to get much more scalable 00:04:33.840 --> 00:04:36.409 align:start position:0% create more to get much more scalable Solutions<00:04:34.620> uh<00:04:35.400> using<00:04:35.699> the<00:04:35.820> layer<00:04:36.060> 2<00:04:36.120> in<00:04:36.300> this 00:04:36.409 --> 00:04:36.419 align:start position:0% Solutions uh using the layer 2 in this 00:04:36.419 --> 00:04:41.990 align:start position:0% Solutions uh using the layer 2 in this case<00:04:36.600> with<00:04:36.840> cat<00:04:37.020> with<00:04:37.320> Chiron<00:04:37.680> starts 00:04:41.990 --> 00:04:42.000 align:start position:0% 00:04:42.000 --> 00:04:44.150 align:start position:0% so<00:04:42.419> this<00:04:42.660> is<00:04:42.780> our<00:04:42.900> solution<00:04:43.199> let's<00:04:43.740> generally 00:04:44.150 --> 00:04:44.160 align:start position:0% so this is our solution let's generally 00:04:44.160 --> 00:04:45.409 align:start position:0% so this is our solution let's generally follow-ups<00:04:44.699> specifically<00:04:45.060> talking<00:04:45.240> about 00:04:45.409 --> 00:04:45.419 align:start position:0% follow-ups specifically talking about 00:04:45.419 --> 00:04:47.810 align:start position:0% follow-ups specifically talking about Chiron<00:04:45.960> starnet<00:04:46.560> you<00:04:47.040> can<00:04:47.220> get<00:04:47.340> extremely 00:04:47.810 --> 00:04:47.820 align:start position:0% Chiron starnet you can get extremely 00:04:47.820 --> 00:04:50.629 align:start position:0% Chiron starnet you can get extremely extremely<00:04:48.540> cheap<00:04:49.080> computation<00:04:49.860> thanks<00:04:50.400> to 00:04:50.629 --> 00:04:50.639 align:start position:0% extremely cheap computation thanks to 00:04:50.639 --> 00:04:53.570 align:start position:0% extremely cheap computation thanks to Cairo<00:04:51.540> and 00:04:53.570 --> 00:04:53.580 align:start position:0% Cairo and 00:04:53.580 --> 00:04:55.610 align:start position:0% Cairo and we<00:04:54.120> can<00:04:54.300> create<00:04:54.479> and<00:04:54.780> this<00:04:54.900> is<00:04:55.020> key<00:04:55.199> we<00:04:55.500> can 00:04:55.610 --> 00:04:55.620 align:start position:0% we can create and this is key we can 00:04:55.620 --> 00:04:57.590 align:start position:0% we can create and this is key we can create<00:04:55.740> interesting<00:04:56.400> applications 00:04:57.590 --> 00:04:57.600 align:start position:0% create interesting applications 00:04:57.600 --> 00:05:00.550 align:start position:0% create interesting applications that<00:04:58.320> are<00:04:58.500> only<00:04:58.680> be<00:04:59.040> that<00:04:59.520> could<00:04:59.699> only<00:04:59.940> be<00:05:00.120> made 00:05:00.550 --> 00:05:00.560 align:start position:0% that are only be that could only be made 00:05:00.560 --> 00:05:03.170 align:start position:0% that are only be that could only be made using<00:05:01.560> the<00:05:02.040> layer<00:05:02.280> two<00:05:02.400> it's<00:05:02.820> impossible 00:05:03.170 --> 00:05:03.180 align:start position:0% using the layer two it's impossible 00:05:03.180 --> 00:05:04.790 align:start position:0% using the layer two it's impossible practically<00:05:03.660> impossible<00:05:04.020> to<00:05:04.199> do<00:05:04.320> on<00:05:04.440> layer 00:05:04.790 --> 00:05:04.800 align:start position:0% practically impossible to do on layer 00:05:04.800 --> 00:05:06.650 align:start position:0% practically impossible to do on layer one 00:05:06.650 --> 00:05:06.660 align:start position:0% one 00:05:06.660 --> 00:05:09.830 align:start position:0% one this<00:05:07.139> is<00:05:07.320> an<00:05:07.440> interesting<00:05:07.919> data<00:05:08.400> that<00:05:08.580> we<00:05:09.060> got 00:05:09.830 --> 00:05:09.840 align:start position:0% this is an interesting data that we got 00:05:09.840 --> 00:05:12.409 align:start position:0% this is an interesting data that we got during<00:05:10.199> the<00:05:10.440> last<00:05:10.560> week 00:05:12.409 --> 00:05:12.419 align:start position:0% during the last week 00:05:12.419 --> 00:05:15.290 align:start position:0% during the last week a<00:05:12.900> standard<00:05:13.259> plus<00:05:13.560> start<00:05:14.040> startix<00:05:14.759> blocks 00:05:15.290 --> 00:05:15.300 align:start position:0% a standard plus start startix blocks 00:05:15.300 --> 00:05:18.050 align:start position:0% a standard plus start startix blocks stagnant<00:05:15.900> so<00:05:16.080> Star<00:05:16.320> Wars<00:05:16.620> the<00:05:16.860> company<00:05:17.060> has 00:05:18.050 --> 00:05:18.060 align:start position:0% stagnant so Star Wars the company has 00:05:18.060 --> 00:05:19.670 align:start position:0% stagnant so Star Wars the company has different<00:05:18.240> solutions<00:05:18.600> one<00:05:18.900> of<00:05:19.020> them<00:05:19.139> is<00:05:19.380> star 00:05:19.670 --> 00:05:19.680 align:start position:0% different solutions one of them is star 00:05:19.680 --> 00:05:22.070 align:start position:0% different solutions one of them is star trekx<00:05:20.100> and<00:05:20.880> the<00:05:21.060> other<00:05:21.120> one<00:05:21.300> is<00:05:21.479> started<00:05:21.780> that 00:05:22.070 --> 00:05:22.080 align:start position:0% trekx and the other one is started that 00:05:22.080 --> 00:05:24.230 align:start position:0% trekx and the other one is started that we're<00:05:22.259> talking<00:05:22.440> about<00:05:22.560> right<00:05:22.860> now<00:05:23.520> and<00:05:24.000> both 00:05:24.230 --> 00:05:24.240 align:start position:0% we're talking about right now and both 00:05:24.240 --> 00:05:26.749 align:start position:0% we're talking about right now and both together<00:05:24.600> had<00:05:25.440> more<00:05:25.680> transactions<00:05:26.340> since 00:05:26.749 --> 00:05:26.759 align:start position:0% together had more transactions since 00:05:26.759 --> 00:05:29.749 align:start position:0% together had more transactions since July<00:05:27.180> than<00:05:27.900> Bitcoin<00:05:28.500> lining<00:05:29.039> and<00:05:29.280> all<00:05:29.400> layer 00:05:29.749 --> 00:05:29.759 align:start position:0% July than Bitcoin lining and all layer 00:05:29.759 --> 00:05:31.850 align:start position:0% July than Bitcoin lining and all layer 2's<00:05:30.539> this<00:05:30.960> is<00:05:31.139> something<00:05:31.259> that<00:05:31.440> is<00:05:31.560> not<00:05:31.740> very 00:05:31.850 --> 00:05:31.860 align:start position:0% 2's this is something that is not very 00:05:31.860 --> 00:05:34.129 align:start position:0% 2's this is something that is not very well<00:05:32.039> known<00:05:32.300> whereas<00:05:33.300> you<00:05:33.419> can<00:05:33.539> see<00:05:33.720> coming 00:05:34.129 --> 00:05:34.139 align:start position:0% well known whereas you can see coming 00:05:34.139 --> 00:05:37.310 align:start position:0% well known whereas you can see coming from<00:05:34.380> July<00:05:34.740> the<00:05:35.280> blue<00:05:35.400> line<00:05:35.580> is<00:05:36.300> the<00:05:36.780> starcakes 00:05:37.310 --> 00:05:37.320 align:start position:0% from July the blue line is the starcakes 00:05:37.320 --> 00:05:39.650 align:start position:0% from July the blue line is the starcakes plus<00:05:37.620> Stark<00:05:38.039> Nets 00:05:39.650 --> 00:05:39.660 align:start position:0% plus Stark Nets 00:05:39.660 --> 00:05:42.469 align:start position:0% plus Stark Nets down<00:05:40.139> is<00:05:40.440> Bitcoin<00:05:40.919> in<00:05:41.039> Orange<00:05:41.280> and<00:05:42.000> under<00:05:42.180> that 00:05:42.469 --> 00:05:42.479 align:start position:0% down is Bitcoin in Orange and under that 00:05:42.479 --> 00:05:44.810 align:start position:0% down is Bitcoin in Orange and under that are<00:05:42.900> other<00:05:43.080> layer<00:05:43.500> 2<00:05:43.620> Solutions 00:05:44.810 --> 00:05:44.820 align:start position:0% are other layer 2 Solutions 00:05:44.820 --> 00:05:46.790 align:start position:0% are other layer 2 Solutions so<00:05:45.120> as<00:05:45.240> you<00:05:45.360> can<00:05:45.479> see<00:05:45.600> Stark<00:05:46.080> is<00:05:46.259> an<00:05:46.380> external 00:05:46.790 --> 00:05:46.800 align:start position:0% so as you can see Stark is an external 00:05:46.800 --> 00:05:49.670 align:start position:0% so as you can see Stark is an external it's<00:05:47.520> currently<00:05:47.820> being<00:05:48.060> very<00:05:48.479> very<00:05:48.660> used<00:05:48.960> and 00:05:49.670 --> 00:05:49.680 align:start position:0% it's currently being very very used and 00:05:49.680 --> 00:05:51.950 align:start position:0% it's currently being very very used and we<00:05:49.800> have<00:05:49.979> been<00:05:50.100> live<00:05:50.340> in<00:05:50.580> Maine<00:05:50.759> since<00:05:51.300> June 00:05:51.950 --> 00:05:51.960 align:start position:0% we have been live in Maine since June 00:05:51.960 --> 00:05:55.370 align:start position:0% we have been live in Maine since June yes<00:05:52.320> June<00:05:52.860> 2020.<00:05:53.759> so<00:05:54.180> we<00:05:54.419> are<00:05:54.539> not<00:05:54.660> new<00:05:55.020> at<00:05:55.199> this 00:05:55.370 --> 00:05:55.380 align:start position:0% yes June 2020. so we are not new at this 00:05:55.380 --> 00:05:58.010 align:start position:0% yes June 2020. so we are not new at this we<00:05:56.039> know<00:05:56.160> how<00:05:56.340> to<00:05:56.460> do<00:05:56.639> it<00:05:56.820> the<00:05:57.419> Star<00:05:57.600> Solutions 00:05:58.010 --> 00:05:58.020 align:start position:0% we know how to do it the Star Solutions 00:05:58.020 --> 00:05:59.810 align:start position:0% we know how to do it the Star Solutions is<00:05:58.199> very<00:05:58.380> good<00:05:58.560> and<00:05:58.919> as<00:05:59.340> you<00:05:59.460> can<00:05:59.580> see<00:05:59.699> it's 00:05:59.810 --> 00:05:59.820 align:start position:0% is very good and as you can see it's 00:05:59.820 --> 00:06:02.629 align:start position:0% is very good and as you can see it's very<00:06:00.120> very<00:06:00.300> it's<00:06:00.900> been<00:06:01.139> very<00:06:01.320> used<00:06:01.620> and<00:06:02.400> very 00:06:02.629 --> 00:06:02.639 align:start position:0% very very it's been very used and very 00:06:02.639 --> 00:06:05.390 align:start position:0% very very it's been very used and very interestingly<00:06:03.180> also<00:06:03.600> is<00:06:03.840> that<00:06:04.139> 70<00:06:04.740> percent<00:06:05.100> of 00:06:05.390 --> 00:06:05.400 align:start position:0% interestingly also is that 70 percent of 00:06:05.400 --> 00:06:07.790 align:start position:0% interestingly also is that 70 percent of that<00:06:05.580> come<00:06:06.180> from<00:06:06.419> nfts 00:06:07.790 --> 00:06:07.800 align:start position:0% that come from nfts 00:06:07.800 --> 00:06:09.710 align:start position:0% that come from nfts it's<00:06:08.220> very<00:06:08.400> interesting 00:06:09.710 --> 00:06:09.720 align:start position:0% it's very interesting 00:06:09.720 --> 00:06:11.689 align:start position:0% it's very interesting for<00:06:10.199> example<00:06:10.380> with<00:06:10.620> immutable 00:06:11.689 --> 00:06:11.699 align:start position:0% for example with immutable 00:06:11.699 --> 00:06:13.249 align:start position:0% for example with immutable with<00:06:12.240> sorare 00:06:13.249 --> 00:06:13.259 align:start position:0% with sorare 00:06:13.259 --> 00:06:16.430 align:start position:0% with sorare interesting 00:06:16.430 --> 00:06:16.440 align:start position:0% 00:06:16.440 --> 00:06:17.930 align:start position:0% so<00:06:16.800> now<00:06:16.919> thank<00:06:17.160> you<00:06:17.280> very<00:06:17.400> much<00:06:17.520> for<00:06:17.759> coming 00:06:17.930 --> 00:06:17.940 align:start position:0% so now thank you very much for coming 00:06:17.940 --> 00:06:20.450 align:start position:0% so now thank you very much for coming now<00:06:18.539> we<00:06:18.720> know<00:06:18.900> that<00:06:19.259> Stan<00:06:19.979> has<00:06:20.160> a<00:06:20.280> lot<00:06:20.340> of 00:06:20.450 --> 00:06:20.460 align:start position:0% now we know that Stan has a lot of 00:06:20.460 --> 00:06:21.409 align:start position:0% now we know that Stan has a lot of potential 00:06:21.409 --> 00:06:21.419 align:start position:0% potential 00:06:21.419 --> 00:06:23.330 align:start position:0% potential you<00:06:21.840> can<00:06:21.900> create<00:06:22.080> needs<00:06:22.680> whenever<00:06:23.039> you<00:06:23.220> want 00:06:23.330 --> 00:06:23.340 align:start position:0% you can create needs whenever you want 00:06:23.340 --> 00:06:25.189 align:start position:0% you can create needs whenever you want you<00:06:23.639> can<00:06:23.759> deploy<00:06:24.060> it<00:06:24.180> currently<00:06:24.539> and<00:06:25.080> actually 00:06:25.189 --> 00:06:25.199 align:start position:0% you can deploy it currently and actually 00:06:25.199 --> 00:06:26.749 align:start position:0% you can deploy it currently and actually today<00:06:25.560> we'll<00:06:25.860> be<00:06:26.039> creating<00:06:26.280> a<00:06:26.520> boating 00:06:26.749 --> 00:06:26.759 align:start position:0% today we'll be creating a boating 00:06:26.759 --> 00:06:28.790 align:start position:0% today we'll be creating a boating application<00:06:27.360> that<00:06:28.020> we're<00:06:28.199> gonna<00:06:28.380> be<00:06:28.620> trying 00:06:28.790 --> 00:06:28.800 align:start position:0% application that we're gonna be trying 00:06:28.800 --> 00:06:30.710 align:start position:0% application that we're gonna be trying on<00:06:29.580> starnet 00:06:30.710 --> 00:06:30.720 align:start position:0% on starnet 00:06:30.720 --> 00:06:32.570 align:start position:0% on starnet you<00:06:31.259> can<00:06:31.380> use<00:06:31.500> it<00:06:31.680> Cairo<00:06:32.160> is<00:06:32.280> a<00:06:32.460> different 00:06:32.570 --> 00:06:32.580 align:start position:0% you can use it Cairo is a different 00:06:32.580 --> 00:06:34.969 align:start position:0% you can use it Cairo is a different language<00:06:32.819> we<00:06:33.120> know<00:06:33.240> it<00:06:33.479> but<00:06:34.139> it's<00:06:34.620> also<00:06:34.860> a 00:06:34.969 --> 00:06:34.979 align:start position:0% language we know it but it's also a 00:06:34.979 --> 00:06:36.950 align:start position:0% language we know it but it's also a language<00:06:35.160> that<00:06:35.460> everybody<00:06:35.699> can<00:06:36.060> use<00:06:36.240> it's<00:06:36.780> not 00:06:36.950 --> 00:06:36.960 align:start position:0% language that everybody can use it's not 00:06:36.960 --> 00:06:41.510 align:start position:0% language that everybody can use it's not hard<00:06:37.199> at<00:06:37.440> all 00:06:41.510 --> 00:06:41.520 align:start position:0% 00:06:41.520 --> 00:06:43.189 align:start position:0% so<00:06:41.880> my<00:06:42.060> name<00:06:42.180> is<00:06:42.240> Marshall<00:06:42.539> Hill<00:06:42.840> I'm<00:06:43.080> a 00:06:43.189 --> 00:06:43.199 align:start position:0% so my name is Marshall Hill I'm a 00:06:43.199 --> 00:06:45.409 align:start position:0% so my name is Marshall Hill I'm a developer<00:06:43.500> Advocate<00:06:43.979> server<00:06:44.460> and<00:06:44.819> thank<00:06:45.300> you 00:06:45.409 --> 00:06:45.419 align:start position:0% developer Advocate server and thank you 00:06:45.419 --> 00:06:47.629 align:start position:0% developer Advocate server and thank you very<00:06:45.539> much<00:06:45.720> for<00:06:45.960> coming<00:06:46.139> today<00:06:46.560> the<00:06:47.460> golf 00:06:47.629 --> 00:06:47.639 align:start position:0% very much for coming today the golf 00:06:47.639 --> 00:06:50.390 align:start position:0% very much for coming today the golf today<00:06:47.880> is<00:06:48.120> for<00:06:48.300> you<00:06:48.539> to<00:06:48.840> get<00:06:49.139> the<00:06:49.319> resources<00:06:49.860> to 00:06:50.390 --> 00:06:50.400 align:start position:0% today is for you to get the resources to 00:06:50.400 --> 00:06:52.430 align:start position:0% today is for you to get the resources to start<00:06:50.639> to<00:06:51.000> start<00:06:51.120> studying<00:06:51.660> Cairo<00:06:52.020> if<00:06:52.319> you 00:06:52.430 --> 00:06:52.440 align:start position:0% start to start studying Cairo if you 00:06:52.440 --> 00:06:55.969 align:start position:0% start to start studying Cairo if you want<00:06:52.680> to<00:06:53.580> go<00:06:53.699> into<00:06:53.880> starnet<00:06:54.419> and<00:06:55.020> also<00:06:55.259> make<00:06:55.800> a 00:06:55.969 --> 00:06:55.979 align:start position:0% want to go into starnet and also make a 00:06:55.979 --> 00:07:00.230 align:start position:0% want to go into starnet and also make a small<00:06:56.100> example<00:06:56.520> of<00:06:56.819> a<00:06:56.940> boring<00:06:57.300> application 00:07:00.230 --> 00:07:00.240 align:start position:0% 00:07:00.240 --> 00:07:02.749 align:start position:0% so<00:07:00.660> now<00:07:00.780> we<00:07:01.020> talk<00:07:01.199> a<00:07:01.380> little<00:07:01.500> bit<00:07:01.680> about<00:07:02.100> what 00:07:02.749 --> 00:07:02.759 align:start position:0% so now we talk a little bit about what 00:07:02.759 --> 00:07:04.610 align:start position:0% so now we talk a little bit about what is<00:07:03.000> being<00:07:03.300> done<00:07:03.539> in<00:07:03.720> layer<00:07:04.020> one<00:07:04.139> that<00:07:04.319> is<00:07:04.500> very 00:07:04.610 --> 00:07:04.620 align:start position:0% is being done in layer one that is very 00:07:04.620 --> 00:07:07.430 align:start position:0% is being done in layer one that is very costly<00:07:05.039> and<00:07:05.280> we<00:07:05.819> can<00:07:06.000> improve 00:07:07.430 --> 00:07:07.440 align:start position:0% costly and we can improve 00:07:07.440 --> 00:07:10.909 align:start position:0% costly and we can improve what<00:07:08.220> now<00:07:08.699> let's<00:07:09.660> talk<00:07:09.840> about<00:07:10.020> what<00:07:10.440> can<00:07:10.620> we<00:07:10.800> do 00:07:10.909 --> 00:07:10.919 align:start position:0% what now let's talk about what can we do 00:07:10.919 --> 00:07:12.770 align:start position:0% what now let's talk about what can we do with<00:07:11.280> all<00:07:11.400> this<00:07:11.580> power<00:07:11.819> that<00:07:12.240> chip 00:07:12.770 --> 00:07:12.780 align:start position:0% with all this power that chip 00:07:12.780 --> 00:07:14.510 align:start position:0% with all this power that chip computation<00:07:13.259> can<00:07:13.440> provide<00:07:13.800> us 00:07:14.510 --> 00:07:14.520 align:start position:0% computation can provide us 00:07:14.520 --> 00:07:16.189 align:start position:0% computation can provide us for<00:07:15.000> example<00:07:15.240> we<00:07:15.479> have<00:07:15.600> a<00:07:15.720> solution<00:07:15.960> called 00:07:16.189 --> 00:07:16.199 align:start position:0% for example we have a solution called 00:07:16.199 --> 00:07:18.710 align:start position:0% for example we have a solution called ckex<00:07:16.860> it's<00:07:17.220> a<00:07:17.400> company<00:07:17.520> that<00:07:18.000> is<00:07:18.120> offering 00:07:18.710 --> 00:07:18.720 align:start position:0% ckex it's a company that is offering 00:07:18.720 --> 00:07:20.689 align:start position:0% ckex it's a company that is offering high<00:07:18.840> frequency<00:07:19.139> trading<00:07:19.620> this<00:07:20.099> of<00:07:20.340> course<00:07:20.460> is 00:07:20.689 --> 00:07:20.699 align:start position:0% high frequency trading this of course is 00:07:20.699 --> 00:07:22.490 align:start position:0% high frequency trading this of course is impossible<00:07:21.120> in<00:07:21.360> layer<00:07:21.660> one<00:07:21.780> imagine<00:07:22.080> having 00:07:22.490 --> 00:07:22.500 align:start position:0% impossible in layer one imagine having 00:07:22.500 --> 00:07:25.969 align:start position:0% impossible in layer one imagine having micro<00:07:23.160> positions<00:07:24.000> and<00:07:24.660> trading<00:07:25.020> with<00:07:25.199> them 00:07:25.969 --> 00:07:25.979 align:start position:0% micro positions and trading with them 00:07:25.979 --> 00:07:28.070 align:start position:0% micro positions and trading with them I<00:07:26.520> don't<00:07:26.880> know<00:07:27.060> it<00:07:27.240> would<00:07:27.419> be<00:07:27.539> impossible 00:07:28.070 --> 00:07:28.080 align:start position:0% I don't know it would be impossible 00:07:28.080 --> 00:07:29.510 align:start position:0% I don't know it would be impossible because<00:07:28.380> of<00:07:28.560> the<00:07:28.680> course<00:07:28.800> in<00:07:29.039> the<00:07:29.099> year<00:07:29.280> one 00:07:29.510 --> 00:07:29.520 align:start position:0% because of the course in the year one 00:07:29.520 --> 00:07:32.570 align:start position:0% because of the course in the year one makes<00:07:29.940> no<00:07:30.180> sense 00:07:32.570 --> 00:07:32.580 align:start position:0% 00:07:32.580 --> 00:07:34.370 align:start position:0% we<00:07:32.940> talked<00:07:33.060> before<00:07:33.240> about<00:07:33.479> voting<00:07:33.900> voting<00:07:34.259> is 00:07:34.370 --> 00:07:34.380 align:start position:0% we talked before about voting voting is 00:07:34.380 --> 00:07:36.230 align:start position:0% we talked before about voting voting is very<00:07:34.560> expensive<00:07:34.919> too<00:07:35.160> so<00:07:35.699> there<00:07:35.880> are<00:07:36.000> also 00:07:36.230 --> 00:07:36.240 align:start position:0% very expensive too so there are also 00:07:36.240 --> 00:07:38.390 align:start position:0% very expensive too so there are also solutions<00:07:36.539> for<00:07:36.780> example<00:07:36.960> snapshot<00:07:37.560> X<00:07:37.740> that 00:07:38.390 --> 00:07:38.400 align:start position:0% solutions for example snapshot X that 00:07:38.400 --> 00:07:40.850 align:start position:0% solutions for example snapshot X that allow<00:07:38.639> us<00:07:38.819> to<00:07:39.000> bolt<00:07:39.419> much<00:07:39.780> more<00:07:39.960> cheaply<00:07:40.319> yes 00:07:40.850 --> 00:07:40.860 align:start position:0% allow us to bolt much more cheaply yes 00:07:40.860 --> 00:07:42.230 align:start position:0% allow us to bolt much more cheaply yes so<00:07:41.220> there<00:07:41.340> are<00:07:41.520> a<00:07:41.580> lot<00:07:41.699> of<00:07:41.759> applications<00:07:42.060> that 00:07:42.230 --> 00:07:42.240 align:start position:0% so there are a lot of applications that 00:07:42.240 --> 00:07:44.210 align:start position:0% so there are a lot of applications that have<00:07:42.419> been<00:07:42.479> already<00:07:42.780> developed<00:07:43.440> since<00:07:44.039> I 00:07:44.210 --> 00:07:44.220 align:start position:0% have been already developed since I 00:07:44.220 --> 00:07:46.790 align:start position:0% have been already developed since I started<00:07:44.580> using<00:07:45.240> all<00:07:45.360> this<00:07:45.539> power<00:07:45.720> another<00:07:46.500> one 00:07:46.790 --> 00:07:46.800 align:start position:0% started using all this power another one 00:07:46.800 --> 00:07:48.890 align:start position:0% started using all this power another one for<00:07:46.979> example<00:07:47.280> is<00:07:47.520> the<00:07:47.699> government<00:07:47.880> of<00:07:48.120> Buenos 00:07:48.890 --> 00:07:48.900 align:start position:0% for example is the government of Buenos 00:07:48.900 --> 00:07:51.110 align:start position:0% for example is the government of Buenos Aires<00:07:49.199> create<00:07:49.440> an<00:07:49.680> application<00:07:50.160> that<00:07:50.819> allows 00:07:51.110 --> 00:07:51.120 align:start position:0% Aires create an application that allows 00:07:51.120 --> 00:07:53.510 align:start position:0% Aires create an application that allows you<00:07:51.240> to<00:07:51.360> have<00:07:51.599> an<00:07:52.319> identity<00:07:52.800> on<00:07:53.340> the 00:07:53.510 --> 00:07:53.520 align:start position:0% you to have an identity on the 00:07:53.520 --> 00:07:56.629 align:start position:0% you to have an identity on the blockchain<00:07:53.880> as<00:07:54.180> a<00:07:54.360> user<00:07:54.900> as<00:07:55.080> a<00:07:55.199> citizen<00:07:55.639> they 00:07:56.629 --> 00:07:56.639 align:start position:0% blockchain as a user as a citizen they 00:07:56.639 --> 00:07:58.790 align:start position:0% blockchain as a user as a citizen they show<00:07:56.880> they<00:07:57.360> chose<00:07:57.539> starnet<00:07:58.080> because<00:07:58.319> it's 00:07:58.790 --> 00:07:58.800 align:start position:0% show they chose starnet because it's 00:07:58.800 --> 00:08:00.710 align:start position:0% show they chose starnet because it's very<00:07:58.979> secure<00:07:59.400> it's<00:07:59.880> highly<00:08:00.240> highly<00:08:00.479> secure 00:08:00.710 --> 00:08:00.720 align:start position:0% very secure it's highly highly secure 00:08:00.720 --> 00:08:02.570 align:start position:0% very secure it's highly highly secure and<00:08:01.199> also<00:08:01.440> it's<00:08:01.560> very<00:08:01.740> scalable<00:08:02.160> and<00:08:02.400> very 00:08:02.570 --> 00:08:02.580 align:start position:0% and also it's very scalable and very 00:08:02.580 --> 00:08:04.610 align:start position:0% and also it's very scalable and very quick 00:08:04.610 --> 00:08:04.620 align:start position:0% quick 00:08:04.620 --> 00:08:06.650 align:start position:0% quick so<00:08:05.099> these<00:08:05.400> are<00:08:05.460> only<00:08:05.639> some<00:08:05.880> examples<00:08:06.240> but<00:08:06.479> the 00:08:06.650 --> 00:08:06.660 align:start position:0% so these are only some examples but the 00:08:06.660 --> 00:08:09.230 align:start position:0% so these are only some examples but the custom<00:08:06.900> is<00:08:07.199> growing<00:08:07.500> by<00:08:07.979> the<00:08:08.160> day<00:08:08.340> for<00:08:09.060> example 00:08:09.230 --> 00:08:09.240 align:start position:0% custom is growing by the day for example 00:08:09.240 --> 00:08:11.390 align:start position:0% custom is growing by the day for example we<00:08:09.539> have<00:08:09.720> tools 00:08:11.390 --> 00:08:11.400 align:start position:0% we have tools 00:08:11.400 --> 00:08:13.070 align:start position:0% we have tools amazing<00:08:11.940> tooling<00:08:12.300> for<00:08:12.479> example<00:08:12.599> coming<00:08:12.840> from 00:08:13.070 --> 00:08:13.080 align:start position:0% amazing tooling for example coming from 00:08:13.080 --> 00:08:16.070 align:start position:0% amazing tooling for example coming from hard<00:08:13.259> hat<00:08:13.620> open<00:08:13.800> sepulime<00:08:14.460> and<00:08:15.419> chain<00:08:15.840> link 00:08:16.070 --> 00:08:16.080 align:start position:0% hard hat open sepulime and chain link 00:08:16.080 --> 00:08:18.350 align:start position:0% hard hat open sepulime and chain link soon<00:08:16.740> Alchemy<00:08:17.580> those<00:08:17.880> are<00:08:18.000> well-known 00:08:18.350 --> 00:08:18.360 align:start position:0% soon Alchemy those are well-known 00:08:18.360 --> 00:08:19.369 align:start position:0% soon Alchemy those are well-known companies 00:08:19.369 --> 00:08:19.379 align:start position:0% companies 00:08:19.379 --> 00:08:21.409 align:start position:0% companies but<00:08:19.860> we<00:08:19.979> also<00:08:20.160> and<00:08:20.520> maybe<00:08:20.759> more<00:08:21.000> interesting 00:08:21.409 --> 00:08:21.419 align:start position:0% but we also and maybe more interesting 00:08:21.419 --> 00:08:23.390 align:start position:0% but we also and maybe more interesting we<00:08:21.720> have<00:08:21.900> different<00:08:22.500> applications<00:08:22.979> on<00:08:23.220> the 00:08:23.390 --> 00:08:23.400 align:start position:0% we have different applications on the 00:08:23.400 --> 00:08:25.249 align:start position:0% we have different applications on the top<00:08:23.520> as<00:08:23.879> you<00:08:24.000> can<00:08:24.120> see<00:08:24.240> that<00:08:24.900> are<00:08:25.139> being 00:08:25.249 --> 00:08:25.259 align:start position:0% top as you can see that are being 00:08:25.259 --> 00:08:27.589 align:start position:0% top as you can see that are being created<00:08:25.560> originally<00:08:25.979> on<00:08:26.220> the<00:08:26.340> layer<00:08:26.520> too 00:08:27.589 --> 00:08:27.599 align:start position:0% created originally on the layer too 00:08:27.599 --> 00:08:29.869 align:start position:0% created originally on the layer too so<00:08:27.840> this<00:08:28.020> is<00:08:28.139> very<00:08:28.259> interesting<00:08:28.680> because<00:08:28.979> it's 00:08:29.869 --> 00:08:29.879 align:start position:0% so this is very interesting because it's 00:08:29.879 --> 00:08:32.269 align:start position:0% so this is very interesting because it's at<00:08:30.240> least<00:08:30.419> my<00:08:30.599> opinion<00:08:30.900> is<00:08:31.080> not<00:08:31.259> for<00:08:31.860> the 00:08:32.269 --> 00:08:32.279 align:start position:0% at least my opinion is not for the 00:08:32.279 --> 00:08:34.670 align:start position:0% at least my opinion is not for the company<00:08:32.399> overall<00:08:33.060> but<00:08:33.839> it<00:08:34.320> is<00:08:34.500> interesting 00:08:34.670 --> 00:08:34.680 align:start position:0% company overall but it is interesting 00:08:34.680 --> 00:08:37.130 align:start position:0% company overall but it is interesting when<00:08:35.039> a<00:08:35.219> company<00:08:35.399> comes<00:08:35.940> from<00:08:36.240> Lane<00:08:36.419> one<00:08:36.779> and 00:08:37.130 --> 00:08:37.140 align:start position:0% when a company comes from Lane one and 00:08:37.140 --> 00:08:39.469 align:start position:0% when a company comes from Lane one and then<00:08:37.320> puts<00:08:38.039> its<00:08:38.279> applications<00:08:38.520> layer<00:08:38.940> to<00:08:39.060> it's 00:08:39.469 --> 00:08:39.479 align:start position:0% then puts its applications layer to it's 00:08:39.479 --> 00:08:43.310 align:start position:0% then puts its applications layer to it's great<00:08:39.779> they<00:08:40.500> are<00:08:40.620> using<00:08:40.979> the<00:08:41.279> the<00:08:42.000> lower<00:08:42.479> fees 00:08:43.310 --> 00:08:43.320 align:start position:0% great they are using the the lower fees 00:08:43.320 --> 00:08:44.690 align:start position:0% great they are using the the lower fees and<00:08:43.500> that<00:08:43.740> kind<00:08:43.860> of<00:08:43.979> stuff 00:08:44.690 --> 00:08:44.700 align:start position:0% and that kind of stuff 00:08:44.700 --> 00:08:47.630 align:start position:0% and that kind of stuff however<00:08:45.480> I<00:08:45.779> believe<00:08:45.899> that<00:08:46.500> the<00:08:46.740> real<00:08:46.860> power<00:08:47.279> is 00:08:47.630 --> 00:08:47.640 align:start position:0% however I believe that the real power is 00:08:47.640 --> 00:08:49.310 align:start position:0% however I believe that the real power is being<00:08:47.820> used<00:08:48.060> but<00:08:48.300> those<00:08:48.660> that<00:08:48.839> are<00:08:49.019> created 00:08:49.310 --> 00:08:49.320 align:start position:0% being used but those that are created 00:08:49.320 --> 00:08:51.829 align:start position:0% being used but those that are created natively<00:08:49.800> on<00:08:50.100> Cairo<00:08:50.519> in<00:08:50.580> the<00:08:50.700> layer<00:08:50.940> two<00:08:51.120> yes 00:08:51.829 --> 00:08:51.839 align:start position:0% natively on Cairo in the layer two yes 00:08:51.839 --> 00:08:53.509 align:start position:0% natively on Cairo in the layer two yes it's<00:08:52.260> a<00:08:52.440> little<00:08:52.500> bit<00:08:52.680> like<00:08:52.860> for<00:08:53.100> example<00:08:53.279> when 00:08:53.509 --> 00:08:53.519 align:start position:0% it's a little bit like for example when 00:08:53.519 --> 00:08:55.070 align:start position:0% it's a little bit like for example when you<00:08:53.640> have<00:08:53.820> Windows<00:08:54.420> in<00:08:54.720> your<00:08:54.899> computer 00:08:55.070 --> 00:08:55.080 align:start position:0% you have Windows in your computer 00:08:55.080 --> 00:08:58.970 align:start position:0% you have Windows in your computer Windows<00:08:55.800> 98<00:08:56.399> for<00:08:56.700> example<00:08:56.940> and<00:08:57.660> you<00:08:57.779> had<00:08:58.019> this 00:08:58.970 --> 00:08:58.980 align:start position:0% Windows 98 for example and you had this 00:08:58.980 --> 00:09:01.730 align:start position:0% Windows 98 for example and you had this nice<00:08:59.160> and<00:08:59.580> cute<00:08:59.820> games<00:09:00.120> and<00:09:01.019> then<00:09:01.140> comes<00:09:01.560> for 00:09:01.730 --> 00:09:01.740 align:start position:0% nice and cute games and then comes for 00:09:01.740 --> 00:09:04.550 align:start position:0% nice and cute games and then comes for example<00:09:01.980> Windows<00:09:02.459> XP<00:09:03.240> right<00:09:03.899> it's<00:09:04.380> more 00:09:04.550 --> 00:09:04.560 align:start position:0% example Windows XP right it's more 00:09:04.560 --> 00:09:06.590 align:start position:0% example Windows XP right it's more powerful<00:09:04.860> you<00:09:05.100> can<00:09:05.220> do<00:09:05.339> much<00:09:05.519> more<00:09:05.700> stuff<00:09:05.940> and 00:09:06.590 --> 00:09:06.600 align:start position:0% powerful you can do much more stuff and 00:09:06.600 --> 00:09:10.070 align:start position:0% powerful you can do much more stuff and these<00:09:06.839> games<00:09:06.959> can<00:09:07.440> be<00:09:07.740> can<00:09:08.640> be<00:09:08.820> passed<00:09:09.300> into<00:09:09.540> XP 00:09:10.070 --> 00:09:10.080 align:start position:0% these games can be can be passed into XP 00:09:10.080 --> 00:09:12.949 align:start position:0% these games can be can be passed into XP okay<00:09:10.500> so<00:09:10.980> these<00:09:11.279> old<00:09:11.459> games<00:09:11.700> can<00:09:12.480> be<00:09:12.660> passed 00:09:12.949 --> 00:09:12.959 align:start position:0% okay so these old games can be passed 00:09:12.959 --> 00:09:15.110 align:start position:0% okay so these old games can be passed into<00:09:13.080> the<00:09:13.320> new<00:09:13.440> software<00:09:13.800> and<00:09:14.519> they<00:09:14.700> run<00:09:14.880> well 00:09:15.110 --> 00:09:15.120 align:start position:0% into the new software and they run well 00:09:15.120 --> 00:09:17.990 align:start position:0% into the new software and they run well it's<00:09:15.600> okay<00:09:15.839> they<00:09:16.620> maybe<00:09:16.860> could<00:09:17.279> leverage<00:09:17.700> some 00:09:17.990 --> 00:09:18.000 align:start position:0% it's okay they maybe could leverage some 00:09:18.000 --> 00:09:19.730 align:start position:0% it's okay they maybe could leverage some of<00:09:18.120> the<00:09:18.180> power<00:09:18.300> of<00:09:18.480> the<00:09:18.660> new<00:09:18.899> operating<00:09:19.380> system 00:09:19.730 --> 00:09:19.740 align:start position:0% of the power of the new operating system 00:09:19.740 --> 00:09:22.430 align:start position:0% of the power of the new operating system but<00:09:20.700> the<00:09:21.060> real<00:09:21.120> power<00:09:21.480> comes<00:09:21.899> from<00:09:22.080> that<00:09:22.260> that 00:09:22.430 --> 00:09:22.440 align:start position:0% but the real power comes from that that 00:09:22.440 --> 00:09:24.889 align:start position:0% but the real power comes from that that is<00:09:22.620> being<00:09:22.740> built<00:09:23.160> on<00:09:23.459> top<00:09:23.580> of<00:09:23.700> XP<00:09:24.180> that<00:09:24.779> could 00:09:24.889 --> 00:09:24.899 align:start position:0% is being built on top of XP that could 00:09:24.899 --> 00:09:26.810 align:start position:0% is being built on top of XP that could not<00:09:25.080> be<00:09:25.200> done<00:09:25.500> in<00:09:26.100> the<00:09:26.220> previous<00:09:26.399> operating 00:09:26.810 --> 00:09:26.820 align:start position:0% not be done in the previous operating 00:09:26.820 --> 00:09:29.030 align:start position:0% not be done in the previous operating system<00:09:27.180> right<00:09:27.660> that's<00:09:28.560> what<00:09:28.740> we're<00:09:28.860> talking 00:09:29.030 --> 00:09:29.040 align:start position:0% system right that's what we're talking 00:09:29.040 --> 00:09:30.769 align:start position:0% system right that's what we're talking about<00:09:29.220> here<00:09:29.519> something<00:09:29.820> that<00:09:30.240> is<00:09:30.360> completely 00:09:30.769 --> 00:09:30.779 align:start position:0% about here something that is completely 00:09:30.779 --> 00:09:32.509 align:start position:0% about here something that is completely different<00:09:31.080> and<00:09:31.620> out<00:09:31.800> of<00:09:31.920> the<00:09:32.100> leak<00:09:32.339> of<00:09:32.459> the 00:09:32.509 --> 00:09:32.519 align:start position:0% different and out of the leak of the 00:09:32.519 --> 00:09:34.730 align:start position:0% different and out of the leak of the layer<00:09:32.820> one<00:09:32.940> we<00:09:33.720> can<00:09:33.899> create<00:09:34.019> something<00:09:34.380> very 00:09:34.730 --> 00:09:34.740 align:start position:0% layer one we can create something very 00:09:34.740 --> 00:09:37.070 align:start position:0% layer one we can create something very very<00:09:34.980> interesting<00:09:35.339> that<00:09:36.060> is<00:09:36.300> impossible<00:09:36.779> to 00:09:37.070 --> 00:09:37.080 align:start position:0% very interesting that is impossible to 00:09:37.080 --> 00:09:38.810 align:start position:0% very interesting that is impossible to create<00:09:37.200> for<00:09:37.800> example<00:09:37.980> we<00:09:38.279> were<00:09:38.459> talking<00:09:38.580> about 00:09:38.810 --> 00:09:38.820 align:start position:0% create for example we were talking about 00:09:38.820 --> 00:09:41.150 align:start position:0% create for example we were talking about the<00:09:39.180> games<00:09:39.480> that<00:09:40.260> they<00:09:40.440> didn't<00:09:40.680> have<00:09:40.980> the 00:09:41.150 --> 00:09:41.160 align:start position:0% the games that they didn't have the 00:09:41.160 --> 00:09:43.670 align:start position:0% the games that they didn't have the logic<00:09:41.519> on<00:09:41.640> chain<00:09:42.300> is<00:09:42.779> now<00:09:43.019> possible<00:09:43.380> so 00:09:43.670 --> 00:09:43.680 align:start position:0% logic on chain is now possible so 00:09:43.680 --> 00:09:45.290 align:start position:0% logic on chain is now possible so imagine<00:09:43.920> that<00:09:44.279> you<00:09:44.459> can<00:09:44.580> do<00:09:44.760> operations 00:09:45.290 --> 00:09:45.300 align:start position:0% imagine that you can do operations 00:09:45.300 --> 00:09:47.990 align:start position:0% imagine that you can do operations summations<00:09:46.200> multiplications<00:09:47.000> divisions 00:09:47.990 --> 00:09:48.000 align:start position:0% summations multiplications divisions 00:09:48.000 --> 00:09:50.329 align:start position:0% summations multiplications divisions whatever<00:09:48.360> you<00:09:48.779> can<00:09:48.839> do<00:09:49.019> that<00:09:49.200> because<00:09:49.860> the<00:09:50.100> gas 00:09:50.329 --> 00:09:50.339 align:start position:0% whatever you can do that because the gas 00:09:50.339 --> 00:09:53.389 align:start position:0% whatever you can do that because the gas is<00:09:50.820> much<00:09:51.180> much<00:09:51.420> cheaper<00:09:51.959> so<00:09:52.380> a<00:09:52.680> company<00:09:52.920> I 00:09:53.389 --> 00:09:53.399 align:start position:0% is much much cheaper so a company I 00:09:53.399 --> 00:09:55.250 align:start position:0% is much much cheaper so a company I don't<00:09:53.519> remember<00:09:53.640> I<00:09:53.940> know<00:09:54.060> the<00:09:54.240> num<00:09:54.779> what<00:09:55.140> is 00:09:55.250 --> 00:09:55.260 align:start position:0% don't remember I know the num what is 00:09:55.260 --> 00:09:56.389 align:start position:0% don't remember I know the num what is the<00:09:55.380> name<00:09:55.440> of<00:09:55.560> the<00:09:55.620> project<00:09:55.800> that<00:09:56.220> was 00:09:56.389 --> 00:09:56.399 align:start position:0% the name of the project that was 00:09:56.399 --> 00:09:59.990 align:start position:0% the name of the project that was creating<00:09:57.240> this<00:09:57.540> on<00:09:57.959> chain<00:09:58.200> reality 00:09:59.990 --> 00:10:00.000 align:start position:0% creating this on chain reality 00:10:00.000 --> 00:10:03.290 align:start position:0% creating this on chain reality topology<00:10:00.540> so<00:10:01.019> topology<00:10:01.440> created<00:10:02.160> a<00:10:02.580> game<00:10:03.000> on 00:10:03.290 --> 00:10:03.300 align:start position:0% topology so topology created a game on 00:10:03.300 --> 00:10:04.370 align:start position:0% topology so topology created a game on chain 00:10:04.370 --> 00:10:04.380 align:start position:0% chain 00:10:04.380 --> 00:10:07.550 align:start position:0% chain and<00:10:04.920> it's<00:10:05.040> Auto<00:10:05.279> regulated<00:10:05.820> okay<00:10:06.600> so<00:10:07.140> do<00:10:07.380> you 00:10:07.550 --> 00:10:07.560 align:start position:0% and it's Auto regulated okay so do you 00:10:07.560 --> 00:10:09.769 align:start position:0% and it's Auto regulated okay so do you need<00:10:07.680> a<00:10:07.920> central<00:10:08.100> limited<00:10:08.640> to<00:10:08.760> the<00:10:08.940> sides<00:10:09.300> if 00:10:09.769 --> 00:10:09.779 align:start position:0% need a central limited to the sides if 00:10:09.779 --> 00:10:11.750 align:start position:0% need a central limited to the sides if you're<00:10:09.899> allowed<00:10:10.200> to<00:10:10.320> play<00:10:10.440> it<00:10:10.620> or<00:10:10.800> not<00:10:10.920> so<00:10:11.580> it 00:10:11.750 --> 00:10:11.760 align:start position:0% you're allowed to play it or not so it 00:10:11.760 --> 00:10:14.630 align:start position:0% you're allowed to play it or not so it will<00:10:12.180> stay<00:10:12.600> forever<00:10:13.320> as<00:10:13.860> long<00:10:13.980> as<00:10:14.100> ethereum 00:10:14.630 --> 00:10:14.640 align:start position:0% will stay forever as long as ethereum 00:10:14.640 --> 00:10:17.150 align:start position:0% will stay forever as long as ethereum exists<00:10:15.540> this<00:10:16.080> is<00:10:16.200> something<00:10:16.380> that<00:10:16.740> is<00:10:16.920> again 00:10:17.150 --> 00:10:17.160 align:start position:0% exists this is something that is again 00:10:17.160 --> 00:10:19.550 align:start position:0% exists this is something that is again impossible<00:10:17.700> layer<00:10:18.120> one<00:10:18.240> and<00:10:18.720> for<00:10:18.959> me<00:10:19.080> those 00:10:19.550 --> 00:10:19.560 align:start position:0% impossible layer one and for me those 00:10:19.560 --> 00:10:21.889 align:start position:0% impossible layer one and for me those the<00:10:20.040> powers<00:10:20.220> is<00:10:20.880> going<00:10:21.060> to<00:10:21.180> come<00:10:21.360> from<00:10:21.720> that 00:10:21.889 --> 00:10:21.899 align:start position:0% the powers is going to come from that 00:10:21.899 --> 00:10:25.670 align:start position:0% the powers is going to come from that part 00:10:25.670 --> 00:10:25.680 align:start position:0% 00:10:25.680 --> 00:10:27.650 align:start position:0% so<00:10:25.980> now<00:10:26.100> the<00:10:26.339> question<00:10:26.519> is 00:10:27.650 --> 00:10:27.660 align:start position:0% so now the question is 00:10:27.660 --> 00:10:30.110 align:start position:0% so now the question is um what<00:10:28.260> can<00:10:28.440> you<00:10:28.560> create 00:10:30.110 --> 00:10:30.120 align:start position:0% um what can you create 00:10:30.120 --> 00:10:32.210 align:start position:0% um what can you create that<00:10:30.660> is<00:10:30.839> completely<00:10:31.140> different<00:10:31.440> from<00:10:31.980> what 00:10:32.210 --> 00:10:32.220 align:start position:0% that is completely different from what 00:10:32.220 --> 00:10:34.190 align:start position:0% that is completely different from what has<00:10:32.399> been<00:10:32.580> created<00:10:32.880> in<00:10:33.000> the<00:10:33.120> layer<00:10:33.360> one<00:10:33.480> using 00:10:34.190 --> 00:10:34.200 align:start position:0% has been created in the layer one using 00:10:34.200 --> 00:10:35.990 align:start position:0% has been created in the layer one using all<00:10:34.440> these<00:10:34.740> new<00:10:34.920> power 00:10:35.990 --> 00:10:36.000 align:start position:0% all these new power 00:10:36.000 --> 00:10:38.090 align:start position:0% all these new power all<00:10:36.540> these<00:10:36.720> new<00:10:36.899> potential<00:10:37.560> that<00:10:37.800> you<00:10:37.980> can 00:10:38.090 --> 00:10:38.100 align:start position:0% all these new potential that you can 00:10:38.100 --> 00:10:40.790 align:start position:0% all these new potential that you can find<00:10:38.279> in<00:10:38.640> the<00:10:38.760> layer<00:10:39.060> 2.<00:10:39.959> that<00:10:40.380> is<00:10:40.560> so 00:10:40.790 --> 00:10:40.800 align:start position:0% find in the layer 2. that is so 00:10:40.800 --> 00:10:43.370 align:start position:0% find in the layer 2. that is so completely<00:10:41.220> different<00:10:41.519> never<00:10:42.300> done<00:10:42.540> before 00:10:43.370 --> 00:10:43.380 align:start position:0% completely different never done before 00:10:43.380 --> 00:10:45.170 align:start position:0% completely different never done before imagine<00:10:43.740> you<00:10:44.100> can<00:10:44.220> do<00:10:44.399> for<00:10:44.700> example<00:10:44.880> machine 00:10:45.170 --> 00:10:45.180 align:start position:0% imagine you can do for example machine 00:10:45.180 --> 00:10:47.389 align:start position:0% imagine you can do for example machine learning<00:10:45.660> on<00:10:45.899> chain<00:10:46.140> you<00:10:46.620> can<00:10:46.740> print<00:10:46.920> models 00:10:47.389 --> 00:10:47.399 align:start position:0% learning on chain you can print models 00:10:47.399 --> 00:10:49.370 align:start position:0% learning on chain you can print models on<00:10:47.519> chain<00:10:47.640> you<00:10:48.420> can<00:10:48.540> create<00:10:48.720> any<00:10:49.140> kind<00:10:49.260> of 00:10:49.370 --> 00:10:49.380 align:start position:0% on chain you can create any kind of 00:10:49.380 --> 00:10:51.590 align:start position:0% on chain you can create any kind of mathematical<00:10:49.860> operations<00:10:50.100> on<00:10:50.339> chain 00:10:51.590 --> 00:10:51.600 align:start position:0% mathematical operations on chain 00:10:51.600 --> 00:10:53.329 align:start position:0% mathematical operations on chain it's<00:10:52.079> completely<00:10:52.440> different<00:10:52.620> and<00:10:52.980> what<00:10:53.220> we 00:10:53.329 --> 00:10:53.339 align:start position:0% it's completely different and what we 00:10:53.339 --> 00:10:55.610 align:start position:0% it's completely different and what we need<00:10:53.519> is<00:10:53.700> people<00:10:54.000> I<00:10:54.720> start<00:10:54.899> building<00:10:55.140> these 00:10:55.610 --> 00:10:55.620 align:start position:0% need is people I start building these 00:10:55.620 --> 00:11:01.550 align:start position:0% need is people I start building these applications<00:10:56.100> that<00:10:56.640> are<00:10:56.820> eye-opening 00:11:01.550 --> 00:11:01.560 align:start position:0% 00:11:01.560 --> 00:11:04.430 align:start position:0% so<00:11:02.279> uh<00:11:03.060> for<00:11:03.180> the<00:11:03.360> beginning<00:11:03.480> you<00:11:04.140> would<00:11:04.320> need 00:11:04.430 --> 00:11:04.440 align:start position:0% so uh for the beginning you would need 00:11:04.440 --> 00:11:07.430 align:start position:0% so uh for the beginning you would need to<00:11:04.620> start<00:11:04.860> installing<00:11:05.640> Cairo<00:11:06.060> starnet<00:11:06.600> hey<00:11:07.200> of 00:11:07.430 --> 00:11:07.440 align:start position:0% to start installing Cairo starnet hey of 00:11:07.440 --> 00:11:08.810 align:start position:0% to start installing Cairo starnet hey of course<00:11:07.500> I<00:11:07.680> don't<00:11:07.740> expect<00:11:07.920> to<00:11:08.220> expect<00:11:08.459> you<00:11:08.700> to 00:11:08.810 --> 00:11:08.820 align:start position:0% course I don't expect to expect you to 00:11:08.820 --> 00:11:11.509 align:start position:0% course I don't expect to expect you to do<00:11:09.000> it<00:11:09.120> right<00:11:09.240> now<00:11:09.420> but<00:11:10.140> you<00:11:10.740> can<00:11:10.800> follow<00:11:10.980> these 00:11:11.509 --> 00:11:11.519 align:start position:0% do it right now but you can follow these 00:11:11.519 --> 00:11:13.850 align:start position:0% do it right now but you can follow these QR<00:11:11.940> codes<00:11:12.120> for<00:11:12.779> some<00:11:12.959> instructions<00:11:13.380> on<00:11:13.560> how<00:11:13.740> to 00:11:13.850 --> 00:11:13.860 align:start position:0% QR codes for some instructions on how to 00:11:13.860 --> 00:11:15.769 align:start position:0% QR codes for some instructions on how to install<00:11:14.040> Cairo<00:11:14.640> and<00:11:14.760> starnet<00:11:15.300> so<00:11:15.420> you<00:11:15.540> can<00:11:15.660> get 00:11:15.769 --> 00:11:15.779 align:start position:0% install Cairo and starnet so you can get 00:11:15.779 --> 00:11:17.269 align:start position:0% install Cairo and starnet so you can get going 00:11:17.269 --> 00:11:17.279 align:start position:0% going 00:11:17.279 --> 00:11:19.310 align:start position:0% going it's<00:11:17.640> not<00:11:17.820> difficult<00:11:18.120> at<00:11:18.300> all 00:11:19.310 --> 00:11:19.320 align:start position:0% it's not difficult at all 00:11:19.320 --> 00:11:21.949 align:start position:0% it's not difficult at all and<00:11:19.860> say<00:11:20.160> while<00:11:20.399> you<00:11:20.579> scroll<00:11:20.760> it<00:11:21.060> we<00:11:21.480> also<00:11:21.720> have 00:11:21.949 --> 00:11:21.959 align:start position:0% and say while you scroll it we also have 00:11:21.959 --> 00:11:24.230 align:start position:0% and say while you scroll it we also have a<00:11:22.320> report<00:11:22.560> that<00:11:22.920> is<00:11:23.100> called<00:11:23.279> started<00:11:23.760> edu 00:11:24.230 --> 00:11:24.240 align:start position:0% a report that is called started edu 00:11:24.240 --> 00:11:25.970 align:start position:0% a report that is called started edu where<00:11:24.600> you<00:11:24.839> can<00:11:24.899> find<00:11:25.140> a<00:11:25.320> lot<00:11:25.440> of<00:11:25.560> educational 00:11:25.970 --> 00:11:25.980 align:start position:0% where you can find a lot of educational 00:11:25.980 --> 00:11:27.769 align:start position:0% where you can find a lot of educational material<00:11:26.519> I<00:11:26.820> will<00:11:27.000> show<00:11:27.120> you<00:11:27.240> the<00:11:27.360> link<00:11:27.540> with 00:11:27.769 --> 00:11:27.779 align:start position:0% material I will show you the link with 00:11:27.779 --> 00:11:31.550 align:start position:0% material I will show you the link with in<00:11:28.320> a<00:11:28.440> couple<00:11:28.680> moments 00:11:31.550 --> 00:11:31.560 align:start position:0% 00:11:31.560 --> 00:11:34.250 align:start position:0% and<00:11:32.279> Inside<00:11:32.459> Story<00:11:32.880> du<00:11:33.420> you<00:11:33.660> can<00:11:33.779> find<00:11:33.959> a<00:11:34.140> lot 00:11:34.250 --> 00:11:34.260 align:start position:0% and Inside Story du you can find a lot 00:11:34.260 --> 00:11:35.930 align:start position:0% and Inside Story du you can find a lot of tutorials<00:11:34.680> on<00:11:34.860> different<00:11:35.040> stuff<00:11:35.519> for 00:11:35.930 --> 00:11:35.940 align:start position:0% of tutorials on different stuff for 00:11:35.940 --> 00:11:38.030 align:start position:0% of tutorials on different stuff for example<00:11:36.240> you<00:11:36.540> can<00:11:36.660> know<00:11:36.779> how<00:11:37.019> to 00:11:38.030 --> 00:11:38.040 align:start position:0% example you can know how to 00:11:38.040 --> 00:11:41.269 align:start position:0% example you can know how to how<00:11:38.399> the<00:11:38.640> cowboy<00:11:39.200> syntax<00:11:40.200> look<00:11:40.440> we're<00:11:41.160> going 00:11:41.269 --> 00:11:41.279 align:start position:0% how the cowboy syntax look we're going 00:11:41.279 --> 00:11:43.610 align:start position:0% how the cowboy syntax look we're going to<00:11:41.459> look<00:11:41.519> at<00:11:41.700> it<00:11:41.820> in<00:11:42.060> a<00:11:42.180> moment 00:11:43.610 --> 00:11:43.620 align:start position:0% to look at it in a moment 00:11:43.620 --> 00:11:46.310 align:start position:0% to look at it in a moment you<00:11:44.100> can<00:11:44.160> for<00:11:44.339> example<00:11:44.700> create<00:11:45.660> a<00:11:45.839> token<00:11:46.140> an 00:11:46.310 --> 00:11:46.320 align:start position:0% you can for example create a token an 00:11:46.320 --> 00:11:49.790 align:start position:0% you can for example create a token an erc20<00:11:46.920> you<00:11:47.459> can<00:11:47.519> create<00:11:47.640> your<00:11:47.940> nft<00:11:48.240> your<00:11:48.800> c721 00:11:49.790 --> 00:11:49.800 align:start position:0% erc20 you can create your nft your c721 00:11:49.800 --> 00:11:52.910 align:start position:0% erc20 you can create your nft your c721 tutorials<00:11:50.760> for<00:11:51.660> even<00:11:52.140> more<00:11:52.320> interesting<00:11:52.740> how 00:11:52.910 --> 00:11:52.920 align:start position:0% tutorials for even more interesting how 00:11:52.920 --> 00:11:55.009 align:start position:0% tutorials for even more interesting how you<00:11:53.160> can<00:11:53.279> create<00:11:53.459> your<00:11:53.760> own<00:11:53.940> Bridge<00:11:54.180> from 00:11:55.009 --> 00:11:55.019 align:start position:0% you can create your own Bridge from 00:11:55.019 --> 00:11:56.750 align:start position:0% you can create your own Bridge from layer<00:11:55.320> 1<00:11:55.440> and<00:11:55.560> layer<00:11:55.860> 2. 00:11:56.750 --> 00:11:56.760 align:start position:0% layer 1 and layer 2. 00:11:56.760 --> 00:11:59.090 align:start position:0% layer 1 and layer 2. Bridge 00:11:59.090 --> 00:11:59.100 align:start position:0% Bridge 00:11:59.100 --> 00:12:01.069 align:start position:0% Bridge and<00:11:59.640> for<00:11:59.940> example<00:12:00.120> how<00:12:00.360> can<00:12:00.540> you<00:12:00.660> create<00:12:00.839> your 00:12:01.069 --> 00:12:01.079 align:start position:0% and for example how can you create your 00:12:01.079 --> 00:12:03.769 align:start position:0% and for example how can you create your own<00:12:01.260> wallets<00:12:01.620> so<00:12:02.399> you<00:12:02.640> can<00:12:02.760> if<00:12:03.120> you<00:12:03.420> can<00:12:03.480> scan 00:12:03.769 --> 00:12:03.779 align:start position:0% own wallets so you can if you can scan 00:12:03.779 --> 00:12:05.630 align:start position:0% own wallets so you can if you can scan this<00:12:04.260> QR<00:12:04.620> code<00:12:04.740> you<00:12:04.920> will<00:12:05.100> find<00:12:05.220> all<00:12:05.459> that 00:12:05.630 --> 00:12:05.640 align:start position:0% this QR code you will find all that 00:12:05.640 --> 00:12:08.389 align:start position:0% this QR code you will find all that material<00:12:06.000> inside<00:12:06.300> and<00:12:07.260> you<00:12:07.500> can<00:12:07.620> get 00:12:08.389 --> 00:12:08.399 align:start position:0% material inside and you can get 00:12:08.399 --> 00:12:11.569 align:start position:0% material inside and you can get uh<00:12:09.000> going<00:12:09.240> by<00:12:09.480> yourself<00:12:09.720> without<00:12:10.500> without<00:12:11.279> any 00:12:11.569 --> 00:12:11.579 align:start position:0% uh going by yourself without without any 00:12:11.579 --> 00:12:13.610 align:start position:0% uh going by yourself without without any problem<00:12:11.820> those<00:12:12.360> tutorials<00:12:12.899> are<00:12:12.959> amazing<00:12:13.440> and 00:12:13.610 --> 00:12:13.620 align:start position:0% problem those tutorials are amazing and 00:12:13.620 --> 00:12:14.990 align:start position:0% problem those tutorials are amazing and they<00:12:13.800> have<00:12:13.980> onboarded<00:12:14.399> a<00:12:14.459> lot<00:12:14.579> of<00:12:14.640> people<00:12:14.760> into 00:12:14.990 --> 00:12:15.000 align:start position:0% they have onboarded a lot of people into 00:12:15.000 --> 00:12:20.329 align:start position:0% they have onboarded a lot of people into the<00:12:15.240> ecosystem 00:12:20.329 --> 00:12:20.339 align:start position:0% 00:12:20.339 --> 00:12:23.090 align:start position:0% also<00:12:20.820> we<00:12:21.000> have<00:12:21.120> a<00:12:21.240> newsletter<00:12:21.600> that<00:12:22.200> is<00:12:22.740> very 00:12:23.090 --> 00:12:23.100 align:start position:0% also we have a newsletter that is very 00:12:23.100 --> 00:12:24.470 align:start position:0% also we have a newsletter that is very nice<00:12:23.279> and<00:12:23.640> you<00:12:23.880> will<00:12:24.060> have<00:12:24.180> a<00:12:24.300> lot<00:12:24.420> of 00:12:24.470 --> 00:12:24.480 align:start position:0% nice and you will have a lot of 00:12:24.480 --> 00:12:26.630 align:start position:0% nice and you will have a lot of educational<00:12:24.899> material<00:12:25.380> there<00:12:25.560> too<00:12:25.800> and<00:12:26.399> also 00:12:26.630 --> 00:12:26.640 align:start position:0% educational material there too and also 00:12:26.640 --> 00:12:29.870 align:start position:0% educational material there too and also some<00:12:27.079> interesting<00:12:28.079> projects<00:12:29.040> happening<00:12:29.459> on 00:12:29.870 --> 00:12:29.880 align:start position:0% some interesting projects happening on 00:12:29.880 --> 00:12:32.930 align:start position:0% some interesting projects happening on the<00:12:30.120> on<00:12:30.899> the<00:12:31.200> on<00:12:31.320> the<00:12:31.440> ecosystem<00:12:31.800> it's<00:12:32.640> also 00:12:32.930 --> 00:12:32.940 align:start position:0% the on the on the ecosystem it's also 00:12:32.940 --> 00:12:34.190 align:start position:0% the on the on the ecosystem it's also there<00:12:33.060> you<00:12:33.240> can<00:12:33.420> subscribe<00:12:33.720> it's<00:12:33.899> a<00:12:34.079> soft 00:12:34.190 --> 00:12:34.200 align:start position:0% there you can subscribe it's a soft 00:12:34.200 --> 00:12:40.610 align:start position:0% there you can subscribe it's a soft stack<00:12:34.560> newsletter 00:12:40.610 --> 00:12:40.620 align:start position:0% 00:12:40.620 --> 00:12:42.410 align:start position:0% and<00:12:40.980> finally<00:12:41.279> what<00:12:41.640> we're<00:12:42.000> going<00:12:42.120> to<00:12:42.180> be<00:12:42.300> doing 00:12:42.410 --> 00:12:42.420 align:start position:0% and finally what we're going to be doing 00:12:42.420 --> 00:12:45.050 align:start position:0% and finally what we're going to be doing today<00:12:42.660> is<00:12:43.139> a<00:12:43.500> voting<00:12:43.800> application 00:12:45.050 --> 00:12:45.060 align:start position:0% today is a voting application 00:12:45.060 --> 00:12:48.410 align:start position:0% today is a voting application they<00:12:45.720> will<00:12:46.019> allow<00:12:46.260> a<00:12:46.860> person<00:12:47.040> to<00:12:47.399> either<00:12:48.120> vote 00:12:48.410 --> 00:12:48.420 align:start position:0% they will allow a person to either vote 00:12:48.420 --> 00:12:50.750 align:start position:0% they will allow a person to either vote for<00:12:48.660> one<00:12:48.899> or<00:12:49.200> zero<00:12:49.560> one<00:12:49.740> for<00:12:50.040> yes<00:12:50.339> for<00:12:50.579> example 00:12:50.750 --> 00:12:50.760 align:start position:0% for one or zero one for yes for example 00:12:50.760 --> 00:12:53.269 align:start position:0% for one or zero one for yes for example zero<00:12:51.180> for<00:12:51.300> no<00:12:51.480> and<00:12:52.260> deploy<00:12:52.680> it<00:12:52.800> on<00:12:52.980> the<00:12:53.100> test 00:12:53.269 --> 00:12:53.279 align:start position:0% zero for no and deploy it on the test 00:12:53.279 --> 00:12:55.730 align:start position:0% zero for no and deploy it on the test Nets<00:12:53.760> if<00:12:54.420> you<00:12:54.600> have<00:12:54.720> any<00:12:54.839> question<00:12:55.079> until<00:12:55.380> now 00:12:55.730 --> 00:12:55.740 align:start position:0% Nets if you have any question until now 00:12:55.740 --> 00:12:58.850 align:start position:0% Nets if you have any question until now you<00:12:56.399> can<00:12:56.639> tell<00:12:56.820> me<00:12:57.000> this<00:12:57.600> is<00:12:57.779> the<00:12:58.200> report<00:12:58.500> that 00:12:58.850 --> 00:12:58.860 align:start position:0% you can tell me this is the report that 00:12:58.860 --> 00:13:00.290 align:start position:0% you can tell me this is the report that we're<00:12:58.920> gonna<00:12:59.100> be<00:12:59.220> using<00:12:59.519> so<00:12:59.820> if<00:12:59.940> you<00:13:00.060> want<00:13:00.180> to 00:13:00.290 --> 00:13:00.300 align:start position:0% we're gonna be using so if you want to 00:13:00.300 --> 00:13:02.389 align:start position:0% we're gonna be using so if you want to have<00:13:00.420> the<00:13:00.540> report<00:13:00.660> you<00:13:01.019> want<00:13:01.139> to<00:13:01.260> clone<00:13:01.440> it<00:13:01.680> you 00:13:02.389 --> 00:13:02.399 align:start position:0% have the report you want to clone it you 00:13:02.399 --> 00:13:05.389 align:start position:0% have the report you want to clone it you want<00:13:02.579> to<00:13:02.760> copy<00:13:03.240> the<00:13:03.360> code<00:13:03.600> or<00:13:04.079> just<00:13:04.320> look<00:13:04.500> at<00:13:04.620> it 00:13:05.389 --> 00:13:05.399 align:start position:0% want to copy the code or just look at it 00:13:05.399 --> 00:13:10.430 align:start position:0% want to copy the code or just look at it feel<00:13:05.820> free<00:13:05.940> to<00:13:06.120> scan<00:13:06.420> these<00:13:06.779> QR<00:13:07.139> codes 00:13:10.430 --> 00:13:10.440 align:start position:0% 00:13:10.440 --> 00:13:13.430 align:start position:0% any<00:13:10.980> questions<00:13:11.279> comments<00:13:12.180> well<00:13:13.019> we'll<00:13:13.200> start 00:13:13.430 --> 00:13:13.440 align:start position:0% any questions comments well we'll start 00:13:13.440 --> 00:13:18.290 align:start position:0% any questions comments well we'll start with<00:13:13.620> the<00:13:13.740> coding<00:13:14.040> parts 00:13:18.290 --> 00:13:18.300 align:start position:0% 00:13:18.300 --> 00:13:21.170 align:start position:0% oh<00:13:18.899> okay<00:13:19.620> and<00:13:20.160> I<00:13:20.459> have<00:13:20.579> a<00:13:20.700> question<00:13:20.820> actually 00:13:21.170 --> 00:13:21.180 align:start position:0% oh okay and I have a question actually 00:13:21.180 --> 00:13:23.030 align:start position:0% oh okay and I have a question actually how<00:13:21.660> many<00:13:21.779> of<00:13:21.959> you<00:13:22.079> know<00:13:22.320> how<00:13:22.560> to<00:13:22.680> code<00:13:22.860> in 00:13:23.030 --> 00:13:23.040 align:start position:0% how many of you know how to code in 00:13:23.040 --> 00:13:26.150 align:start position:0% how many of you know how to code in solidity<00:13:24.000> can<00:13:24.360> you<00:13:24.540> raise<00:13:24.660> your<00:13:24.839> hand<00:13:25.500> how 00:13:26.150 --> 00:13:26.160 align:start position:0% solidity can you raise your hand how 00:13:26.160 --> 00:13:29.329 align:start position:0% solidity can you raise your hand how many<00:13:26.339> of<00:13:26.459> you<00:13:26.639> have<00:13:26.820> ever<00:13:27.180> coded<00:13:27.959> in<00:13:28.139> Cairo 00:13:29.329 --> 00:13:29.339 align:start position:0% many of you have ever coded in Cairo 00:13:29.339 --> 00:13:35.389 align:start position:0% many of you have ever coded in Cairo oh<00:13:29.760> a<00:13:30.000> few<00:13:30.120> of<00:13:30.240> you<00:13:30.360> cool 00:13:35.389 --> 00:13:35.399 align:start position:0% 00:13:35.399 --> 00:13:37.430 align:start position:0% coming<00:13:35.760> from<00:13:36.000> so<00:13:36.240> late<00:13:36.420> into<00:13:36.660> Cairo<00:13:37.079> is<00:13:37.200> very 00:13:37.430 --> 00:13:37.440 align:start position:0% coming from so late into Cairo is very 00:13:37.440 --> 00:13:39.230 align:start position:0% coming from so late into Cairo is very simple<00:13:37.680> yeah<00:13:37.980> really<00:13:38.399> really<00:13:38.579> simple<00:13:38.880> and 00:13:39.230 --> 00:13:39.240 align:start position:0% simple yeah really really simple and 00:13:39.240 --> 00:13:40.370 align:start position:0% simple yeah really really simple and it's<00:13:39.420> great<00:13:39.600> that<00:13:39.779> you're<00:13:39.899> already<00:13:40.079> working 00:13:40.370 --> 00:13:40.380 align:start position:0% it's great that you're already working 00:13:40.380 --> 00:13:44.509 align:start position:0% it's great that you're already working with<00:13:40.680> solid 00:13:44.509 --> 00:13:44.519 align:start position:0% 00:13:44.519 --> 00:13:46.430 align:start position:0% perfect 00:13:46.430 --> 00:13:46.440 align:start position:0% perfect 00:13:46.440 --> 00:13:49.850 align:start position:0% perfect you<00:13:46.800> want<00:13:47.040> to<00:13:47.160> go<00:13:47.339> to<00:13:47.639> Tesla<00:13:48.180> and<00:13:48.420> see<00:13:48.839> away<00:13:49.440> and 00:13:49.850 --> 00:13:49.860 align:start position:0% you want to go to Tesla and see away and 00:13:49.860 --> 00:13:52.190 align:start position:0% you want to go to Tesla and see away and interact<00:13:50.279> with<00:13:50.459> with<00:13:51.180> this<00:13:51.480> contract<00:13:51.839> feel 00:13:52.190 --> 00:13:52.200 align:start position:0% interact with with this contract feel 00:13:52.200 --> 00:13:54.590 align:start position:0% interact with with this contract feel free<00:13:52.320> also<00:13:52.620> to<00:13:52.740> scan<00:13:53.160> these<00:13:53.339> QR<00:13:53.639> codes<00:13:53.760> the 00:13:54.590 --> 00:13:54.600 align:start position:0% free also to scan these QR codes the 00:13:54.600 --> 00:13:56.810 align:start position:0% free also to scan these QR codes the test<00:13:54.779> Nets<00:13:55.200> already<00:13:55.320> working<00:13:55.680> with<00:13:56.100> this<00:13:56.459> both 00:13:56.810 --> 00:13:56.820 align:start position:0% test Nets already working with this both 00:13:56.820 --> 00:14:00.590 align:start position:0% test Nets already working with this both team<00:13:57.060> contracts 00:14:00.590 --> 00:14:00.600 align:start position:0% 00:14:00.600 --> 00:14:09.129 align:start position:0% foreign 00:14:09.129 --> 00:14:09.139 align:start position:0% 00:14:09.139 --> 00:14:12.290 align:start position:0% here<00:14:10.139> if<00:14:10.440> you<00:14:10.620> want<00:14:10.680> to<00:14:10.800> come<00:14:10.920> also<00:14:11.279> and<00:14:11.579> I 00:14:12.290 --> 00:14:12.300 align:start position:0% here if you want to come also and I 00:14:12.300 --> 00:14:13.910 align:start position:0% here if you want to come also and I don't<00:14:12.480> know<00:14:12.540> guys<00:14:12.720> do<00:14:12.899> you<00:14:13.079> want<00:14:13.200> to<00:14:13.380> add 00:14:13.910 --> 00:14:13.920 align:start position:0% don't know guys do you want to add 00:14:13.920 --> 00:14:16.310 align:start position:0% don't know guys do you want to add something<00:14:14.100> else<00:14:14.399> before<00:14:14.700> we<00:14:14.940> start<00:14:15.120> going 00:14:16.310 --> 00:14:16.320 align:start position:0% something else before we start going 00:14:16.320 --> 00:14:19.970 align:start position:0% something else before we start going oh<00:14:16.800> perfect 00:14:19.970 --> 00:14:19.980 align:start position:0% 00:14:19.980 --> 00:14:21.110 align:start position:0% okay 00:14:21.110 --> 00:14:21.120 align:start position:0% okay 00:14:21.120 --> 00:14:24.110 align:start position:0% okay do<00:14:21.420> you<00:14:21.600> need<00:14:21.720> another<00:14:22.139> QR<00:14:22.800> codes<00:14:22.980> uh<00:14:23.639> do<00:14:23.940> you 00:14:24.110 --> 00:14:24.120 align:start position:0% do you need another QR codes uh do you 00:14:24.120 --> 00:14:25.370 align:start position:0% do you need another QR codes uh do you have<00:14:24.240> already<00:14:24.360> the<00:14:24.660> the<00:14:24.959> one<00:14:25.139> with<00:14:25.320> the 00:14:25.370 --> 00:14:25.380 align:start position:0% have already the the one with the 00:14:25.380 --> 00:14:27.230 align:start position:0% have already the the one with the contract<00:14:25.680> will<00:14:25.800> win<00:14:26.040> we're<00:14:26.639> going<00:14:26.820> to<00:14:26.940> use<00:14:27.060> is 00:14:27.230 --> 00:14:27.240 align:start position:0% contract will win we're going to use is 00:14:27.240 --> 00:14:30.110 align:start position:0% contract will win we're going to use is this<00:14:27.480> one<00:14:27.600> remember<00:14:27.720> please 00:14:30.110 --> 00:14:30.120 align:start position:0% this one remember please 00:14:30.120 --> 00:14:32.389 align:start position:0% this one remember please so<00:14:30.839> let's<00:14:31.139> go 00:14:32.389 --> 00:14:32.399 align:start position:0% so let's go 00:14:32.399 --> 00:14:41.389 align:start position:0% so let's go to<00:14:32.760> the<00:14:33.000> counts 00:14:41.389 --> 00:14:41.399 align:start position:0% 00:14:41.399 --> 00:14:45.410 align:start position:0% so<00:14:41.940> this<00:14:42.060> is<00:14:42.180> our<00:14:42.360> boating<00:14:42.779> contract 00:14:45.410 --> 00:14:45.420 align:start position:0% so this is our boating contract 00:14:45.420 --> 00:14:48.889 align:start position:0% so this is our boating contract again<00:14:45.959> the<00:14:46.860> goal<00:14:47.519> is<00:14:47.880> to<00:14:48.120> create<00:14:48.360> a<00:14:48.600> contract 00:14:48.889 --> 00:14:48.899 align:start position:0% again the goal is to create a contract 00:14:48.899 --> 00:14:51.769 align:start position:0% again the goal is to create a contract that<00:14:49.079> allows<00:14:49.500> certain<00:14:50.399> predefined<00:14:51.180> addresses 00:14:51.769 --> 00:14:51.779 align:start position:0% that allows certain predefined addresses 00:14:51.779 --> 00:14:55.670 align:start position:0% that allows certain predefined addresses for<00:14:52.620> example<00:14:52.860> me<00:14:53.220> as<00:14:53.459> the<00:14:53.880> admin<00:14:54.360> of<00:14:54.600> the<00:14:54.899> of 00:14:55.670 --> 00:14:55.680 align:start position:0% for example me as the admin of the of 00:14:55.680 --> 00:14:58.310 align:start position:0% for example me as the admin of the of the<00:14:55.980> of<00:14:56.160> the<00:14:56.399> boat<00:14:56.579> I<00:14:57.420> can<00:14:57.540> tell<00:14:57.720> okay<00:14:57.959> this 00:14:58.310 --> 00:14:58.320 align:start position:0% the of the boat I can tell okay this 00:14:58.320 --> 00:15:00.050 align:start position:0% the of the boat I can tell okay this address<00:14:58.500> can<00:14:58.920> vote<00:14:59.160> this<00:14:59.399> or<00:14:59.579> address<00:14:59.760> can 00:15:00.050 --> 00:15:00.060 align:start position:0% address can vote this or address can 00:15:00.060 --> 00:15:01.730 align:start position:0% address can vote this or address can both<00:15:00.240> these<00:15:00.779> are<00:15:00.839> the<00:15:00.959> Rescue<00:15:01.260> Bots<00:15:01.380> because 00:15:01.730 --> 00:15:01.740 align:start position:0% both these are the Rescue Bots because 00:15:01.740 --> 00:15:03.290 align:start position:0% both these are the Rescue Bots because we<00:15:01.980> don't<00:15:02.160> want<00:15:02.339> everybody<00:15:02.519> to<00:15:02.880> be<00:15:03.000> able<00:15:03.120> to 00:15:03.290 --> 00:15:03.300 align:start position:0% we don't want everybody to be able to 00:15:03.300 --> 00:15:06.050 align:start position:0% we don't want everybody to be able to post<00:15:03.540> only<00:15:04.079> certain<00:15:04.560> participants<00:15:05.160> of<00:15:05.519> of<00:15:05.820> a 00:15:06.050 --> 00:15:06.060 align:start position:0% post only certain participants of of a 00:15:06.060 --> 00:15:07.910 align:start position:0% post only certain participants of of a project<00:15:06.240> I<00:15:06.720> don't<00:15:06.839> know 00:15:07.910 --> 00:15:07.920 align:start position:0% project I don't know 00:15:07.920 --> 00:15:10.370 align:start position:0% project I don't know and<00:15:08.579> they<00:15:08.820> will<00:15:08.940> be<00:15:09.060> able<00:15:09.180> to<00:15:09.360> vote<00:15:09.600> Yes<00:15:09.899> or<00:15:10.199> no 00:15:10.370 --> 00:15:10.380 align:start position:0% and they will be able to vote Yes or no 00:15:10.380 --> 00:15:14.689 align:start position:0% and they will be able to vote Yes or no just<00:15:10.920> with<00:15:11.220> one<00:15:11.459> no<00:15:12.240> with<00:15:12.540> zero<00:15:12.959> and<00:15:13.500> yes<00:15:14.459> that 00:15:14.689 --> 00:15:14.699 align:start position:0% just with one no with zero and yes that 00:15:14.699 --> 00:15:17.210 align:start position:0% just with one no with zero and yes that will<00:15:14.880> be<00:15:15.000> all 00:15:17.210 --> 00:15:17.220 align:start position:0% 00:15:17.220 --> 00:15:20.509 align:start position:0% so<00:15:17.639> for<00:15:17.760> this<00:15:18.420> let's<00:15:18.839> review<00:15:19.079> the 00:15:20.509 --> 00:15:20.519 align:start position:0% so for this let's review the 00:15:20.519 --> 00:15:24.350 align:start position:0% so for this let's review the structure<00:15:21.240> and<00:15:21.420> how<00:15:21.660> Carol<00:15:22.199> looks 00:15:24.350 --> 00:15:24.360 align:start position:0% structure and how Carol looks 00:15:24.360 --> 00:15:26.930 align:start position:0% structure and how Carol looks here<00:15:24.720> we<00:15:24.959> are<00:15:25.079> importing<00:15:25.500> our<00:15:26.040> packages<00:15:26.459> very 00:15:26.930 --> 00:15:26.940 align:start position:0% here we are importing our packages very 00:15:26.940 --> 00:15:29.269 align:start position:0% here we are importing our packages very similar<00:15:27.240> to<00:15:27.360> how<00:15:27.779> it<00:15:27.899> looks<00:15:28.139> in<00:15:28.199> python<00:15:28.680> as<00:15:29.100> you 00:15:29.269 --> 00:15:29.279 align:start position:0% similar to how it looks in python as you 00:15:29.279 --> 00:15:30.949 align:start position:0% similar to how it looks in python as you can<00:15:29.339> see<00:15:29.459> it 00:15:30.949 --> 00:15:30.959 align:start position:0% can see it 00:15:30.959 --> 00:15:33.949 align:start position:0% can see it then<00:15:31.320> we<00:15:31.500> Define<00:15:31.680> its<00:15:32.100> drugs 00:15:33.949 --> 00:15:33.959 align:start position:0% then we Define its drugs 00:15:33.959 --> 00:15:37.910 align:start position:0% then we Define its drugs as<00:15:34.320> you<00:15:34.440> would<00:15:34.620> for<00:15:34.920> example<00:15:35.220> in<00:15:35.699> Rust 00:15:37.910 --> 00:15:37.920 align:start position:0% as you would for example in Rust 00:15:37.920 --> 00:15:39.829 align:start position:0% as you would for example in Rust flush<00:15:38.399> the<00:15:38.459> grain<00:15:38.760> are<00:15:39.060> both<00:15:39.180> counting 00:15:39.829 --> 00:15:39.839 align:start position:0% flush the grain are both counting 00:15:39.839 --> 00:15:42.050 align:start position:0% flush the grain are both counting structs<00:15:40.440> where<00:15:40.860> you<00:15:41.040> will<00:15:41.220> be<00:15:41.399> able<00:15:41.579> to<00:15:41.699> store 00:15:42.050 --> 00:15:42.060 align:start position:0% structs where you will be able to store 00:15:42.060 --> 00:15:44.269 align:start position:0% structs where you will be able to store the<00:15:42.300> boats<00:15:42.720> with<00:15:42.839> yes<00:15:43.019> or<00:15:43.380> no 00:15:44.269 --> 00:15:44.279 align:start position:0% the boats with yes or no 00:15:44.279 --> 00:15:46.610 align:start position:0% the boats with yes or no so<00:15:44.760> for<00:15:44.880> example<00:15:45.060> we'll<00:15:45.300> have<00:15:45.600> 10<00:15:46.019> volts<00:15:46.500> with 00:15:46.610 --> 00:15:46.620 align:start position:0% so for example we'll have 10 volts with 00:15:46.620 --> 00:15:48.829 align:start position:0% so for example we'll have 10 volts with yes<00:15:46.800> zero<00:15:47.459> bolts<00:15:47.699> with<00:15:47.820> null<00:15:48.120> something<00:15:48.600> like 00:15:48.829 --> 00:15:48.839 align:start position:0% yes zero bolts with null something like 00:15:48.839 --> 00:15:52.550 align:start position:0% yes zero bolts with null something like that<00:15:48.959> the<00:15:49.139> counting<00:15:49.500> of<00:15:49.620> the<00:15:49.740> boat 00:15:52.550 --> 00:15:52.560 align:start position:0% 00:15:52.560 --> 00:15:55.129 align:start position:0% secondly<00:15:53.220> we<00:15:53.399> have<00:15:53.639> border<00:15:54.180> info<00:15:54.540> where<00:15:54.899> we 00:15:55.129 --> 00:15:55.139 align:start position:0% secondly we have border info where we 00:15:55.139 --> 00:15:56.810 align:start position:0% secondly we have border info where we store<00:15:55.320> information<00:15:55.620> about<00:15:55.980> the<00:15:56.220> Border<00:15:56.579> in 00:15:56.810 --> 00:15:56.820 align:start position:0% store information about the Border in 00:15:56.820 --> 00:15:59.030 align:start position:0% store information about the Border in this<00:15:56.940> case<00:15:57.060> I<00:15:57.300> only<00:15:57.480> very<00:15:57.959> simply<00:15:58.260> allowed<00:15:58.620> I 00:15:59.030 --> 00:15:59.040 align:start position:0% this case I only very simply allowed I 00:15:59.040 --> 00:16:01.910 align:start position:0% this case I only very simply allowed I simply<00:15:59.480> added<00:16:00.480> an<00:16:00.720> allowed 00:16:01.910 --> 00:16:01.920 align:start position:0% simply added an allowed 00:16:01.920 --> 00:16:05.030 align:start position:0% simply added an allowed member<00:16:02.639> that<00:16:03.480> it<00:16:03.779> will<00:16:03.959> have<00:16:04.199> a<00:16:04.380> one<00:16:04.620> if<00:16:04.860> it's 00:16:05.030 --> 00:16:05.040 align:start position:0% member that it will have a one if it's 00:16:05.040 --> 00:16:07.250 align:start position:0% member that it will have a one if it's allowed<00:16:05.399> to<00:16:05.459> vote<00:16:05.699> or<00:16:05.940> zero<00:16:06.240> if<00:16:06.360> not<00:16:06.540> if<00:16:07.019> if 00:16:07.250 --> 00:16:07.260 align:start position:0% allowed to vote or zero if not if if 00:16:07.260 --> 00:16:09.110 align:start position:0% allowed to vote or zero if not if if this<00:16:07.500> person<00:16:07.680> has<00:16:07.920> already<00:16:08.040> vote<00:16:08.459> it<00:16:08.940> will 00:16:09.110 --> 00:16:09.120 align:start position:0% this person has already vote it will 00:16:09.120 --> 00:16:12.410 align:start position:0% this person has already vote it will have<00:16:09.300> a<00:16:09.420> zero 00:16:12.410 --> 00:16:12.420 align:start position:0% 00:16:12.420 --> 00:16:16.370 align:start position:0% now<00:16:12.779> coming<00:16:13.079> to<00:16:13.320> the<00:16:13.500> storage 00:16:16.370 --> 00:16:16.380 align:start position:0% 00:16:16.380 --> 00:16:18.470 align:start position:0% this<00:16:16.800> is<00:16:16.980> storage<00:16:17.100> variables 00:16:18.470 --> 00:16:18.480 align:start position:0% this is storage variables 00:16:18.480 --> 00:16:20.990 align:start position:0% this is storage variables uh<00:16:19.380> allow<00:16:19.740> you<00:16:19.800> to<00:16:19.920> know<00:16:20.100> if<00:16:20.339> you're<00:16:20.519> not<00:16:20.639> solid 00:16:20.990 --> 00:16:21.000 align:start position:0% uh allow you to know if you're not solid 00:16:21.000 --> 00:16:22.550 align:start position:0% uh allow you to know if you're not solid already<00:16:21.180> these<00:16:21.720> are<00:16:21.839> very<00:16:21.899> similar<00:16:22.199> to<00:16:22.380> you 00:16:22.550 --> 00:16:22.560 align:start position:0% already these are very similar to you 00:16:22.560 --> 00:16:25.730 align:start position:0% already these are very similar to you they<00:16:23.160> allow<00:16:23.459> you<00:16:23.579> to<00:16:23.760> map<00:16:24.000> from<00:16:24.660> when 00:16:25.730 --> 00:16:25.740 align:start position:0% they allow you to map from when 00:16:25.740 --> 00:16:28.009 align:start position:0% they allow you to map from when um<00:16:26.100> from<00:16:26.579> one<00:16:26.699> expression<00:16:27.120> to<00:16:27.360> the<00:16:27.540> other<00:16:27.660> in 00:16:28.009 --> 00:16:28.019 align:start position:0% um from one expression to the other in 00:16:28.019 --> 00:16:30.170 align:start position:0% um from one expression to the other in this<00:16:28.199> case<00:16:28.320> for<00:16:28.560> example<00:16:28.860> the<00:16:29.220> first<00:16:29.339> one<00:16:29.579> now 00:16:30.170 --> 00:16:30.180 align:start position:0% this case for example the first one now 00:16:30.180 --> 00:16:32.150 align:start position:0% this case for example the first one now let's<00:16:30.300> go<00:16:30.480> to<00:16:30.600> the<00:16:30.779> third<00:16:30.959> one<00:16:31.139> here 00:16:32.150 --> 00:16:32.160 align:start position:0% let's go to the third one here 00:16:32.160 --> 00:16:34.129 align:start position:0% let's go to the third one here I<00:16:32.579> am<00:16:32.699> able<00:16:33.000> to<00:16:33.180> map 00:16:34.129 --> 00:16:34.139 align:start position:0% I am able to map 00:16:34.139 --> 00:16:36.889 align:start position:0% I am able to map and<00:16:34.500> address 00:16:36.889 --> 00:16:36.899 align:start position:0% 00:16:36.899 --> 00:16:40.550 align:start position:0% to<00:16:37.380> to<00:16:38.160> a<00:16:38.880> is<00:16:39.060> register<00:16:39.480> Bible<00:16:39.839> that<00:16:40.199> in<00:16:40.380> this 00:16:40.550 --> 00:16:40.560 align:start position:0% to to a is register Bible that in this 00:16:40.560 --> 00:16:43.189 align:start position:0% to to a is register Bible that in this case<00:16:40.740> is<00:16:41.160> a<00:16:41.339> field<00:16:41.519> so<00:16:42.000> Cairo<00:16:42.420> is<00:16:42.600> type<00:16:42.779> it's<00:16:43.019> a 00:16:43.189 --> 00:16:43.199 align:start position:0% case is a field so Cairo is type it's a 00:16:43.199 --> 00:16:44.210 align:start position:0% case is a field so Cairo is type it's a type<00:16:43.320> language 00:16:44.210 --> 00:16:44.220 align:start position:0% type language 00:16:44.220 --> 00:16:46.430 align:start position:0% type language now<00:16:44.820> you<00:16:45.120> might<00:16:45.540> ask<00:16:45.720> yourself<00:16:45.899> what<00:16:46.199> is<00:16:46.320> a 00:16:46.430 --> 00:16:46.440 align:start position:0% now you might ask yourself what is a 00:16:46.440 --> 00:16:48.970 align:start position:0% now you might ask yourself what is a felt 00:16:48.970 --> 00:16:48.980 align:start position:0% 00:16:48.980 --> 00:16:51.350 align:start position:0% everything<00:16:49.980> is<00:16:50.279> a<00:16:50.399> fell<00:16:50.519> inside<00:16:50.699> Cairo 00:16:51.350 --> 00:16:51.360 align:start position:0% everything is a fell inside Cairo 00:16:51.360 --> 00:16:53.449 align:start position:0% everything is a fell inside Cairo conversion<00:16:52.259> to<00:16:52.380> Felts 00:16:53.449 --> 00:16:53.459 align:start position:0% conversion to Felts 00:16:53.459 --> 00:16:55.670 align:start position:0% conversion to Felts and<00:16:54.000> basically<00:16:54.420> for<00:16:54.720> our<00:16:54.899> purpose<00:16:55.320> right<00:16:55.560> now 00:16:55.670 --> 00:16:55.680 align:start position:0% and basically for our purpose right now 00:16:55.680 --> 00:16:57.710 align:start position:0% and basically for our purpose right now if<00:16:56.399> you<00:16:56.519> want<00:16:56.759> we<00:16:57.000> can<00:16:57.120> get<00:16:57.360> a<00:16:57.540> little<00:16:57.600> bit 00:16:57.710 --> 00:16:57.720 align:start position:0% if you want we can get a little bit 00:16:57.720 --> 00:17:00.110 align:start position:0% if you want we can get a little bit deeper<00:16:58.079> in<00:16:58.620> a<00:16:58.800> moment<00:16:58.920> both<00:16:59.279> for<00:16:59.519> now<00:16:59.699> in<00:17:00.000> order 00:17:00.110 --> 00:17:00.120 align:start position:0% deeper in a moment both for now in order 00:17:00.120 --> 00:17:01.069 align:start position:0% deeper in a moment both for now in order to 00:17:01.069 --> 00:17:01.079 align:start position:0% to 00:17:01.079 --> 00:17:03.769 align:start position:0% to to<00:17:01.740> get<00:17:02.040> to<00:17:02.339> make<00:17:02.519> the<00:17:02.699> most<00:17:02.820> of<00:17:02.940> the<00:17:03.060> time<00:17:03.240> I 00:17:03.769 --> 00:17:03.779 align:start position:0% to get to make the most of the time I 00:17:03.779 --> 00:17:05.990 align:start position:0% to get to make the most of the time I felt<00:17:04.079> it's<00:17:04.140> like<00:17:04.380> a<00:17:04.559> big<00:17:04.919> interview 00:17:05.990 --> 00:17:06.000 align:start position:0% felt it's like a big interview 00:17:06.000 --> 00:17:08.990 align:start position:0% felt it's like a big interview a huge<00:17:06.419> interior<00:17:06.780> number<00:17:07.439> okay 00:17:08.990 --> 00:17:09.000 align:start position:0% a huge interior number okay 00:17:09.000 --> 00:17:11.150 align:start position:0% a huge interior number okay so<00:17:09.540> in<00:17:10.079> this<00:17:10.199> case<00:17:10.380> as<00:17:10.500> you<00:17:10.679> can<00:17:10.799> see<00:17:10.980> the 00:17:11.150 --> 00:17:11.160 align:start position:0% so in this case as you can see the 00:17:11.160 --> 00:17:12.169 align:start position:0% so in this case as you can see the address 00:17:12.169 --> 00:17:12.179 align:start position:0% address 00:17:12.179 --> 00:17:15.230 align:start position:0% address has<00:17:12.600> not<00:17:12.780> address<00:17:13.260> type<00:17:13.740> as<00:17:14.040> in<00:17:14.220> solidity<00:17:14.640> it's 00:17:15.230 --> 00:17:15.240 align:start position:0% has not address type as in solidity it's 00:17:15.240 --> 00:17:17.929 align:start position:0% has not address type as in solidity it's a<00:17:15.360> field<00:17:15.540> okay 00:17:17.929 --> 00:17:17.939 align:start position:0% a field okay 00:17:17.939 --> 00:17:20.030 align:start position:0% a field okay so<00:17:18.419> we're<00:17:18.600> mapping<00:17:18.959> an<00:17:19.199> address<00:17:19.319> there<00:17:19.799> is<00:17:19.980> a 00:17:20.030 --> 00:17:20.040 align:start position:0% so we're mapping an address there is a 00:17:20.040 --> 00:17:22.789 align:start position:0% so we're mapping an address there is a failed<00:17:20.400> to<00:17:20.880> a<00:17:21.240> field<00:17:21.480> called<00:17:22.020> is<00:17:22.319> register 00:17:22.789 --> 00:17:22.799 align:start position:0% failed to a field called is register 00:17:22.799 --> 00:17:24.829 align:start position:0% failed to a field called is register that<00:17:23.160> will<00:17:23.280> have<00:17:23.459> a<00:17:23.699> one<00:17:23.880> or<00:17:24.059> zero<00:17:24.419> or<00:17:24.660> whatever 00:17:24.829 --> 00:17:24.839 align:start position:0% that will have a one or zero or whatever 00:17:24.839 --> 00:17:26.689 align:start position:0% that will have a one or zero or whatever we<00:17:25.380> haven't<00:17:25.439> defined<00:17:25.919> it<00:17:25.980> yet 00:17:26.689 --> 00:17:26.699 align:start position:0% we haven't defined it yet 00:17:26.699 --> 00:17:29.390 align:start position:0% we haven't defined it yet and<00:17:27.179> on<00:17:27.360> the<00:17:27.540> other<00:17:27.600> ones<00:17:27.839> we<00:17:28.199> are<00:17:28.439> mapping<00:17:28.860> our 00:17:29.390 --> 00:17:29.400 align:start position:0% and on the other ones we are mapping our 00:17:29.400 --> 00:17:31.549 align:start position:0% and on the other ones we are mapping our information<00:17:29.780> and<00:17:30.780> interestingly<00:17:31.260> in<00:17:31.380> the 00:17:31.549 --> 00:17:31.559 align:start position:0% information and interestingly in the 00:17:31.559 --> 00:17:34.190 align:start position:0% information and interestingly in the first<00:17:31.679> one<00:17:31.860> we<00:17:32.220> are<00:17:32.400> mapping<00:17:32.760> nothing<00:17:33.200> yes 00:17:34.190 --> 00:17:34.200 align:start position:0% first one we are mapping nothing yes 00:17:34.200 --> 00:17:35.390 align:start position:0% first one we are mapping nothing yes nothing 00:17:35.390 --> 00:17:35.400 align:start position:0% nothing 00:17:35.400 --> 00:17:39.470 align:start position:0% nothing to<00:17:35.820> a<00:17:36.120> structure<00:17:36.600> about<00:17:37.320> Counting 00:17:39.470 --> 00:17:39.480 align:start position:0% to a structure about Counting 00:17:39.480 --> 00:17:41.810 align:start position:0% to a structure about Counting so<00:17:39.900> this<00:17:40.200> allows<00:17:40.500> us<00:17:40.559> to<00:17:40.740> read<00:17:40.980> or<00:17:41.460> write<00:17:41.640> into 00:17:41.810 --> 00:17:41.820 align:start position:0% so this allows us to read or write into 00:17:41.820 --> 00:17:44.029 align:start position:0% so this allows us to read or write into the<00:17:42.120> memory<00:17:42.360> that's<00:17:42.720> as<00:17:42.960> simple<00:17:43.080> as<00:17:43.260> that<00:17:43.440> I 00:17:44.029 --> 00:17:44.039 align:start position:0% the memory that's as simple as that I 00:17:44.039 --> 00:17:45.110 align:start position:0% the memory that's as simple as that I can<00:17:44.160> read<00:17:44.340> this 00:17:45.110 --> 00:17:45.120 align:start position:0% can read this 00:17:45.120 --> 00:17:47.930 align:start position:0% can read this or<00:17:45.660> I<00:17:45.840> can<00:17:46.080> write<00:17:46.919> into<00:17:47.160> the<00:17:47.340> memory<00:17:47.580> using 00:17:47.930 --> 00:17:47.940 align:start position:0% or I can write into the memory using 00:17:47.940 --> 00:17:50.210 align:start position:0% or I can write into the memory using these<00:17:48.120> ones 00:17:50.210 --> 00:17:50.220 align:start position:0% these ones 00:17:50.220 --> 00:17:52.250 align:start position:0% these ones so<00:17:50.760> using<00:17:51.240> the<00:17:51.360> storage<00:17:51.480> variable<00:17:51.840> boat<00:17:52.080> in 00:17:52.250 --> 00:17:52.260 align:start position:0% so using the storage variable boat in 00:17:52.260 --> 00:17:55.310 align:start position:0% so using the storage variable boat in status<00:17:52.559> and<00:17:53.100> if<00:17:53.340> we<00:17:53.460> read<00:17:53.640> it<00:17:53.880> and<00:17:54.360> if<00:17:54.600> I<00:17:54.780> I<00:17:55.080> will 00:17:55.310 --> 00:17:55.320 align:start position:0% status and if we read it and if I I will 00:17:55.320 --> 00:17:59.510 align:start position:0% status and if we read it and if I I will go<00:17:55.500> right<00:17:55.860> now<00:17:56.039> to<00:17:56.220> the<00:17:56.520> deploy<00:17:57.059> contracts 00:17:59.510 --> 00:17:59.520 align:start position:0% go right now to the deploy contracts 00:17:59.520 --> 00:18:01.730 align:start position:0% go right now to the deploy contracts so<00:17:59.880> this<00:18:00.000> is<00:18:00.000> the<00:18:00.240> deploy<00:18:00.780> contract<00:18:01.200> I'm<00:18:01.380> using 00:18:01.730 --> 00:18:01.740 align:start position:0% so this is the deploy contract I'm using 00:18:01.740 --> 00:18:03.289 align:start position:0% so this is the deploy contract I'm using right<00:18:01.919> now<00:18:02.100> boilinger<00:18:02.640> which<00:18:02.820> is<00:18:02.940> a<00:18:03.059> Blog 00:18:03.289 --> 00:18:03.299 align:start position:0% right now boilinger which is a Blog 00:18:03.299 --> 00:18:06.110 align:start position:0% right now boilinger which is a Blog Explorer<00:18:03.720> for<00:18:04.200> starnet 00:18:06.110 --> 00:18:06.120 align:start position:0% Explorer for starnet 00:18:06.120 --> 00:18:08.870 align:start position:0% Explorer for starnet if<00:18:06.360> I<00:18:06.600> go<00:18:06.720> to<00:18:06.960> the<00:18:07.140> read<00:18:07.320> part<00:18:07.620> of<00:18:07.740> the<00:18:07.860> contract 00:18:08.870 --> 00:18:08.880 align:start position:0% if I go to the read part of the contract 00:18:08.880 --> 00:18:11.750 align:start position:0% if I go to the read part of the contract I<00:18:09.360> can<00:18:09.539> see 00:18:11.750 --> 00:18:11.760 align:start position:0% I can see 00:18:11.760 --> 00:18:15.110 align:start position:0% I can see what<00:18:12.000> both<00:18:12.240> in<00:18:12.480> his<00:18:12.600> status<00:18:12.780> is<00:18:13.140> doing 00:18:15.110 --> 00:18:15.120 align:start position:0% what both in his status is doing 00:18:15.120 --> 00:18:16.850 align:start position:0% what both in his status is doing using<00:18:15.600> a<00:18:15.720> getter<00:18:16.020> function<00:18:16.260> that<00:18:16.440> we<00:18:16.559> will<00:18:16.740> see 00:18:16.850 --> 00:18:16.860 align:start position:0% using a getter function that we will see 00:18:16.860 --> 00:18:19.250 align:start position:0% using a getter function that we will see in<00:18:17.100> a<00:18:17.220> moment<00:18:17.400> you<00:18:18.240> can<00:18:18.360> see<00:18:18.539> the<00:18:18.720> status<00:18:18.840> of 00:18:19.250 --> 00:18:19.260 align:start position:0% in a moment you can see the status of 00:18:19.260 --> 00:18:21.110 align:start position:0% in a moment you can see the status of developing<00:18:19.799> right<00:18:20.100> now<00:18:20.280> because<00:18:20.520> nobody<00:18:20.940> has 00:18:21.110 --> 00:18:21.120 align:start position:0% developing right now because nobody has 00:18:21.120 --> 00:18:23.810 align:start position:0% developing right now because nobody has both<00:18:21.299> Jets<00:18:21.780> we<00:18:22.500> have<00:18:22.679> zero<00:18:23.340> codes<00:18:23.460> with<00:18:23.700> this 00:18:23.810 --> 00:18:23.820 align:start position:0% both Jets we have zero codes with this 00:18:23.820 --> 00:18:26.390 align:start position:0% both Jets we have zero codes with this three<00:18:24.179> boats<00:18:24.480> would<00:18:24.600> know<00:18:25.080> so<00:18:25.679> that<00:18:26.160> is<00:18:26.280> the 00:18:26.390 --> 00:18:26.400 align:start position:0% three boats would know so that is the 00:18:26.400 --> 00:18:28.430 align:start position:0% three boats would know so that is the storage<00:18:26.580> we<00:18:27.120> are<00:18:27.240> reading<00:18:27.480> right<00:18:27.660> now<00:18:27.840> this 00:18:28.430 --> 00:18:28.440 align:start position:0% storage we are reading right now this 00:18:28.440 --> 00:18:30.110 align:start position:0% storage we are reading right now this storage<00:18:28.799> variable<00:18:29.220> will<00:18:29.520> I<00:18:29.640> get<00:18:29.760> our<00:18:29.880> function 00:18:30.110 --> 00:18:30.120 align:start position:0% storage variable will I get our function 00:18:30.120 --> 00:18:32.270 align:start position:0% storage variable will I get our function that<00:18:30.299> we'll<00:18:30.419> get<00:18:30.660> to<00:18:30.780> that<00:18:30.840> in<00:18:31.020> a<00:18:31.140> moment 00:18:32.270 --> 00:18:32.280 align:start position:0% that we'll get to that in a moment 00:18:32.280 --> 00:18:34.070 align:start position:0% that we'll get to that in a moment and<00:18:32.820> also<00:18:33.000> we<00:18:33.179> have<00:18:33.240> the<00:18:33.360> boring<00:18:33.660> info<00:18:33.960> and 00:18:34.070 --> 00:18:34.080 align:start position:0% and also we have the boring info and 00:18:34.080 --> 00:18:35.810 align:start position:0% and also we have the boring info and it's<00:18:34.200> the<00:18:34.380> same<00:18:34.500> everyone<00:18:34.860> goes<00:18:35.340> into<00:18:35.460> this 00:18:35.810 --> 00:18:35.820 align:start position:0% it's the same everyone goes into this 00:18:35.820 --> 00:18:38.029 align:start position:0% it's the same everyone goes into this but<00:18:36.120> basically<00:18:36.960> we're<00:18:37.320> storing<00:18:37.860> information 00:18:38.029 --> 00:18:38.039 align:start position:0% but basically we're storing information 00:18:38.039 --> 00:18:41.810 align:start position:0% but basically we're storing information into<00:18:38.880> the<00:18:39.480> uh<00:18:39.840> in<00:18:40.200> this<00:18:40.260> into<00:18:40.380> the<00:18:40.620> storage<00:18:40.820> of 00:18:41.810 --> 00:18:41.820 align:start position:0% into the uh in this into the storage of 00:18:41.820 --> 00:18:42.890 align:start position:0% into the uh in this into the storage of the 00:18:42.890 --> 00:18:42.900 align:start position:0% the 00:18:42.900 --> 00:18:44.870 align:start position:0% the of<00:18:43.320> the<00:18:43.559> blockchain 00:18:44.870 --> 00:18:44.880 align:start position:0% of the blockchain 00:18:44.880 --> 00:18:47.270 align:start position:0% of the blockchain now<00:18:45.360> let's<00:18:45.660> go<00:18:45.840> to<00:18:45.960> the<00:18:46.080> Constructor<00:18:46.440> looks 00:18:47.270 --> 00:18:47.280 align:start position:0% now let's go to the Constructor looks 00:18:47.280 --> 00:18:48.590 align:start position:0% now let's go to the Constructor looks very<00:18:47.400> similar<00:18:47.700> you<00:18:47.880> know<00:18:48.000> we're<00:18:48.120> doing<00:18:48.360> an 00:18:48.590 --> 00:18:48.600 align:start position:0% very similar you know we're doing an 00:18:48.600 --> 00:18:50.270 align:start position:0% very similar you know we're doing an initialize<00:18:49.080> your<00:18:49.260> your<00:18:49.500> contract<00:18:49.980> with<00:18:50.100> your 00:18:50.270 --> 00:18:50.280 align:start position:0% initialize your your contract with your 00:18:50.280 --> 00:18:52.010 align:start position:0% initialize your your contract with your deploy<00:18:50.700> it<00:18:50.760> you<00:18:51.120> have<00:18:51.299> to<00:18:51.480> Define<00:18:51.600> certain 00:18:52.010 --> 00:18:52.020 align:start position:0% deploy it you have to Define certain 00:18:52.020 --> 00:18:53.750 align:start position:0% deploy it you have to Define certain inputs 00:18:53.750 --> 00:18:53.760 align:start position:0% inputs 00:18:53.760 --> 00:18:56.690 align:start position:0% inputs as<00:18:54.299> insulated<00:18:54.840> exactly<00:18:55.440> the<00:18:55.559> same<00:18:55.679> name 00:18:56.690 --> 00:18:56.700 align:start position:0% as insulated exactly the same name 00:18:56.700 --> 00:18:59.090 align:start position:0% as insulated exactly the same name so<00:18:57.179> this<00:18:57.360> Constructor<00:18:57.780> will<00:18:58.380> ask<00:18:58.559> for<00:18:58.799> three 00:18:59.090 --> 00:18:59.100 align:start position:0% so this Constructor will ask for three 00:18:59.100 --> 00:19:00.710 align:start position:0% so this Constructor will ask for three different<00:18:59.280> input<00:18:59.820> Bibles<00:19:00.179> as<00:19:00.360> you<00:19:00.539> can<00:19:00.600> see 00:19:00.710 --> 00:19:00.720 align:start position:0% different input Bibles as you can see 00:19:00.720 --> 00:19:02.810 align:start position:0% different input Bibles as you can see now<00:19:00.900> we<00:19:01.140> can<00:19:01.320> we<00:19:01.740> can<00:19:01.860> view<00:19:02.100> how<00:19:02.460> the<00:19:02.640> a 00:19:02.810 --> 00:19:02.820 align:start position:0% now we can we can view how the a 00:19:02.820 --> 00:19:04.909 align:start position:0% now we can we can view how the a function<00:19:03.120> looks<00:19:03.539> into<00:19:03.660> Cairo 00:19:04.909 --> 00:19:04.919 align:start position:0% function looks into Cairo 00:19:04.919 --> 00:19:07.610 align:start position:0% function looks into Cairo it's<00:19:05.280> very<00:19:05.460> simple<00:19:05.640> very<00:19:06.059> similar<00:19:06.419> also<00:19:06.780> to<00:19:07.020> to 00:19:07.610 --> 00:19:07.620 align:start position:0% it's very simple very similar also to to 00:19:07.620 --> 00:19:10.490 align:start position:0% it's very simple very similar also to to Python<00:19:08.160> and<00:19:08.760> what<00:19:09.419> is<00:19:09.600> important<00:19:09.780> here<00:19:10.140> is 00:19:10.490 --> 00:19:10.500 align:start position:0% Python and what is important here is 00:19:10.500 --> 00:19:12.950 align:start position:0% Python and what is important here is this<00:19:10.799> part<00:19:10.980> these<00:19:11.760> are<00:19:11.820> the<00:19:11.940> inputs<00:19:12.480> the 00:19:12.950 --> 00:19:12.960 align:start position:0% this part these are the inputs the 00:19:12.960 --> 00:19:15.110 align:start position:0% this part these are the inputs the explicit<00:19:13.500> inputs<00:19:14.039> to<00:19:14.160> this<00:19:14.340> function<00:19:14.640> in<00:19:15.000> this 00:19:15.110 --> 00:19:15.120 align:start position:0% explicit inputs to this function in this 00:19:15.120 --> 00:19:17.270 align:start position:0% explicit inputs to this function in this case<00:19:15.240> the<00:19:15.480> inputs<00:19:15.900> for<00:19:16.020> the<00:19:16.140> Constructor<00:19:16.559> that 00:19:17.270 --> 00:19:17.280 align:start position:0% case the inputs for the Constructor that 00:19:17.280 --> 00:19:19.490 align:start position:0% case the inputs for the Constructor that we<00:19:17.460> have<00:19:17.580> to<00:19:17.880> provide<00:19:18.660> it<00:19:18.780> when<00:19:19.020> we<00:19:19.140> deploy 00:19:19.490 --> 00:19:19.500 align:start position:0% we have to provide it when we deploy 00:19:19.500 --> 00:19:20.810 align:start position:0% we have to provide it when we deploy this<00:19:19.679> contracts 00:19:20.810 --> 00:19:20.820 align:start position:0% this contracts 00:19:20.820 --> 00:19:23.450 align:start position:0% this contracts so<00:19:21.299> I'm<00:19:21.600> asking<00:19:21.960> for<00:19:22.140> an<00:19:22.320> admin<00:19:22.740> address<00:19:22.860> the 00:19:23.450 --> 00:19:23.460 align:start position:0% so I'm asking for an admin address the 00:19:23.460 --> 00:19:26.270 align:start position:0% so I'm asking for an admin address the person<00:19:23.640> that's<00:19:23.880> going<00:19:24.120> to<00:19:24.240> be<00:19:24.480> able<00:19:25.260> to<00:19:25.440> to 00:19:26.270 --> 00:19:26.280 align:start position:0% person that's going to be able to to 00:19:26.280 --> 00:19:30.650 align:start position:0% person that's going to be able to to manage<00:19:26.820> this<00:19:27.240> contracts<00:19:28.559> with<00:19:28.980> a<00:19:29.220> felt<00:19:29.520> again 00:19:30.650 --> 00:19:30.660 align:start position:0% manage this contracts with a felt again 00:19:30.660 --> 00:19:33.529 align:start position:0% manage this contracts with a felt again then<00:19:31.380> the<00:19:31.740> number<00:19:31.860> of<00:19:32.160> addresses<00:19:33.000> that<00:19:33.360> will 00:19:33.529 --> 00:19:33.539 align:start position:0% then the number of addresses that will 00:19:33.539 --> 00:19:35.870 align:start position:0% then the number of addresses that will be<00:19:33.660> able<00:19:33.960> to<00:19:34.200> vote 00:19:35.870 --> 00:19:35.880 align:start position:0% be able to vote 00:19:35.880 --> 00:19:37.250 align:start position:0% be able to vote and<00:19:36.419> finally 00:19:37.250 --> 00:19:37.260 align:start position:0% and finally 00:19:37.260 --> 00:19:38.630 align:start position:0% and finally the 00:19:38.630 --> 00:19:38.640 align:start position:0% the 00:19:38.640 --> 00:19:40.430 align:start position:0% the disappointed 00:19:40.430 --> 00:19:40.440 align:start position:0% disappointed 00:19:40.440 --> 00:19:42.230 align:start position:0% disappointed so<00:19:40.799> it's<00:19:40.919> important<00:19:41.220> to<00:19:41.460> know<00:19:41.580> that<00:19:41.760> Cairo<00:19:42.120> is 00:19:42.230 --> 00:19:42.240 align:start position:0% so it's important to know that Cairo is 00:19:42.240 --> 00:19:44.330 align:start position:0% so it's important to know that Cairo is a<00:19:42.299> low-level<00:19:42.660> language<00:19:42.900> so<00:19:43.799> here<00:19:43.980> we<00:19:44.220> can 00:19:44.330 --> 00:19:44.340 align:start position:0% a low-level language so here we can 00:19:44.340 --> 00:19:47.630 align:start position:0% a low-level language so here we can manage<00:19:44.700> the<00:19:45.179> memory<00:19:45.720> we<00:19:46.260> have<00:19:46.380> to<00:19:46.559> manage<00:19:46.860> it 00:19:47.630 --> 00:19:47.640 align:start position:0% manage the memory we have to manage it 00:19:47.640 --> 00:19:50.990 align:start position:0% manage the memory we have to manage it so<00:19:48.179> the<00:19:48.419> register<00:19:48.720> addresses<00:19:49.320> is<00:19:49.679> basically<00:19:50.100> a 00:19:50.990 --> 00:19:51.000 align:start position:0% so the register addresses is basically a 00:19:51.000 --> 00:19:52.490 align:start position:0% so the register addresses is basically a vector<00:19:51.419> with<00:19:51.780> a<00:19:51.900> different<00:19:52.020> addresses 00:19:52.490 --> 00:19:52.500 align:start position:0% vector with a different addresses 00:19:52.500 --> 00:19:55.310 align:start position:0% vector with a different addresses arrival<00:19:52.860> to<00:19:53.100> both<00:19:53.220> I<00:19:54.000> can<00:19:54.120> add<00:19:54.299> five<00:19:54.720> six<00:19:55.080> seven 00:19:55.310 --> 00:19:55.320 align:start position:0% arrival to both I can add five six seven 00:19:55.320 --> 00:19:56.870 align:start position:0% arrival to both I can add five six seven eight<00:19:55.620> whatever 00:19:56.870 --> 00:19:56.880 align:start position:0% eight whatever 00:19:56.880 --> 00:19:59.570 align:start position:0% eight whatever and<00:19:57.480> this<00:19:57.660> pointer<00:19:58.020> felt 00:19:59.570 --> 00:19:59.580 align:start position:0% and this pointer felt 00:19:59.580 --> 00:20:01.669 align:start position:0% and this pointer felt points<00:20:00.360> to<00:20:00.480> the<00:20:00.720> start 00:20:01.669 --> 00:20:01.679 align:start position:0% points to the start 00:20:01.679 --> 00:20:04.310 align:start position:0% points to the start of<00:20:01.740> that<00:20:02.220> Vector<00:20:02.700> but<00:20:03.179> you<00:20:03.660> would<00:20:03.840> even<00:20:04.020> notice 00:20:04.310 --> 00:20:04.320 align:start position:0% of that Vector but you would even notice 00:20:04.320 --> 00:20:07.190 align:start position:0% of that Vector but you would even notice that<00:20:04.559> this<00:20:04.940> the<00:20:05.940> logic<00:20:06.299> behind<00:20:06.539> it<00:20:06.720> is<00:20:06.960> that 00:20:07.190 --> 00:20:07.200 align:start position:0% that this the logic behind it is that 00:20:07.200 --> 00:20:09.890 align:start position:0% that this the logic behind it is that this<00:20:07.559> is<00:20:07.740> pointing<00:20:08.100> to<00:20:08.220> the<00:20:08.460> start<00:20:08.640> of<00:20:09.480> this 00:20:09.890 --> 00:20:09.900 align:start position:0% this is pointing to the start of this 00:20:09.900 --> 00:20:10.970 align:start position:0% this is pointing to the start of this array 00:20:10.970 --> 00:20:10.980 align:start position:0% array 00:20:10.980 --> 00:20:13.250 align:start position:0% array of<00:20:11.400> different<00:20:11.520> addresses<00:20:12.179> but<00:20:12.660> you<00:20:12.900> won't<00:20:13.080> you 00:20:13.250 --> 00:20:13.260 align:start position:0% of different addresses but you won't you 00:20:13.260 --> 00:20:16.490 align:start position:0% of different addresses but you won't you will<00:20:13.440> notice<00:20:13.679> this<00:20:13.860> do<00:20:14.400> as<00:20:14.640> you<00:20:14.760> will<00:20:14.880> see 00:20:16.490 --> 00:20:16.500 align:start position:0% will notice this do as you will see 00:20:16.500 --> 00:20:19.130 align:start position:0% will notice this do as you will see then<00:20:16.919> we're<00:20:17.160> basically<00:20:17.520> using<00:20:17.940> a<00:20:18.780> contract 00:20:19.130 --> 00:20:19.140 align:start position:0% then we're basically using a contract 00:20:19.140 --> 00:20:21.590 align:start position:0% then we're basically using a contract because<00:20:19.620> we<00:20:19.860> have<00:20:19.980> open<00:20:20.220> simply<00:20:20.580> on<00:20:20.820> top<00:20:21.000> also 00:20:21.590 --> 00:20:21.600 align:start position:0% because we have open simply on top also 00:20:21.600 --> 00:20:24.289 align:start position:0% because we have open simply on top also of<00:20:21.780> stone<00:20:22.260> it<00:20:22.559> so<00:20:22.799> you<00:20:23.220> are<00:20:23.340> able<00:20:23.460> to<00:20:23.580> use<00:20:23.880> a 00:20:24.289 --> 00:20:24.299 align:start position:0% of stone it so you are able to use a 00:20:24.299 --> 00:20:26.750 align:start position:0% of stone it so you are able to use a very<00:20:24.480> secure<00:20:24.840> contracts<00:20:25.440> thanks<00:20:25.919> to<00:20:26.280> open 00:20:26.750 --> 00:20:26.760 align:start position:0% very secure contracts thanks to open 00:20:26.760 --> 00:20:29.450 align:start position:0% very secure contracts thanks to open sampling<00:20:27.419> and<00:20:28.080> we're<00:20:28.559> using<00:20:28.860> the<00:20:28.980> owner<00:20:29.340> will 00:20:29.450 --> 00:20:29.460 align:start position:0% sampling and we're using the owner will 00:20:29.460 --> 00:20:31.909 align:start position:0% sampling and we're using the owner will contract<00:20:29.820> from<00:20:30.000> our<00:20:30.120> principaline<00:20:30.780> before 00:20:31.909 --> 00:20:31.919 align:start position:0% contract from our principaline before 00:20:31.919 --> 00:20:34.850 align:start position:0% contract from our principaline before I<00:20:32.460> import<00:20:32.700> them<00:20:33.120> here 00:20:34.850 --> 00:20:34.860 align:start position:0% I import them here 00:20:34.860 --> 00:20:37.370 align:start position:0% I import them here so<00:20:35.460> I<00:20:35.700> imported<00:20:36.059> The<00:20:36.240> Honorable<00:20:36.600> a<00:20:37.080> contract 00:20:37.370 --> 00:20:37.380 align:start position:0% so I imported The Honorable a contract 00:20:37.380 --> 00:20:39.710 align:start position:0% so I imported The Honorable a contract and<00:20:37.620> the<00:20:37.740> possible<00:20:38.039> contract<00:20:38.460> libraries<00:20:39.059> from 00:20:39.710 --> 00:20:39.720 align:start position:0% and the possible contract libraries from 00:20:39.720 --> 00:20:41.390 align:start position:0% and the possible contract libraries from openstepperling<00:20:40.559> owner<00:20:40.919> will<00:20:41.039> basically 00:20:41.390 --> 00:20:41.400 align:start position:0% openstepperling owner will basically 00:20:41.400 --> 00:20:43.610 align:start position:0% openstepperling owner will basically defines<00:20:42.360> who<00:20:42.720> the<00:20:42.900> owner<00:20:43.140> is<00:20:43.260> of<00:20:43.440> something 00:20:43.610 --> 00:20:43.620 align:start position:0% defines who the owner is of something 00:20:43.620 --> 00:20:46.250 align:start position:0% defines who the owner is of something and<00:20:44.400> possible<00:20:44.760> it<00:20:45.120> allows<00:20:45.360> you<00:20:45.480> to<00:20:45.660> post<00:20:45.900> a 00:20:46.250 --> 00:20:46.260 align:start position:0% and possible it allows you to post a 00:20:46.260 --> 00:20:48.950 align:start position:0% and possible it allows you to post a contract<00:20:46.620> in<00:20:47.220> case<00:20:47.340> of<00:20:47.460> an<00:20:47.640> emergency<00:20:47.960> say 00:20:48.950 --> 00:20:48.960 align:start position:0% contract in case of an emergency say 00:20:48.960 --> 00:20:50.930 align:start position:0% contract in case of an emergency say that<00:20:49.200> for<00:20:49.440> example<00:20:49.620> my<00:20:49.980> application<00:20:50.460> is<00:20:50.760> being 00:20:50.930 --> 00:20:50.940 align:start position:0% that for example my application is being 00:20:50.940 --> 00:20:53.210 align:start position:0% that for example my application is being hacked<00:20:51.419> so<00:20:51.720> I<00:20:51.840> can<00:20:51.960> pause<00:20:52.140> it<00:20:52.380> as<00:20:52.799> simple<00:20:52.980> as 00:20:53.210 --> 00:20:53.220 align:start position:0% hacked so I can pause it as simple as 00:20:53.220 --> 00:20:56.390 align:start position:0% hacked so I can pause it as simple as that<00:20:53.820> but<00:20:54.179> also<00:20:54.419> we<00:20:54.539> have<00:20:54.660> erc721<00:20:55.620> Logics<00:20:56.160> and 00:20:56.390 --> 00:20:56.400 align:start position:0% that but also we have erc721 Logics and 00:20:56.400 --> 00:20:59.029 align:start position:0% that but also we have erc721 Logics and erc's<00:20:57.059> 20<00:20:57.660> so<00:20:58.200> you<00:20:58.380> can<00:20:58.500> use<00:20:58.620> it<00:20:58.740> with<00:20:58.919> open 00:20:59.029 --> 00:20:59.039 align:start position:0% erc's 20 so you can use it with open 00:20:59.039 --> 00:21:01.010 align:start position:0% erc's 20 so you can use it with open supplement<00:20:59.520> that's<00:20:59.880> very<00:21:00.120> very<00:21:00.240> useful<00:21:00.600> very 00:21:01.010 --> 00:21:01.020 align:start position:0% supplement that's very very useful very 00:21:01.020 --> 00:21:03.830 align:start position:0% supplement that's very very useful very very<00:21:01.500> useful 00:21:03.830 --> 00:21:03.840 align:start position:0% very useful 00:21:03.840 --> 00:21:05.870 align:start position:0% very useful any<00:21:04.260> question<00:21:04.559> until<00:21:04.799> now<00:21:05.100> we<00:21:05.400> have<00:21:05.580> seen<00:21:05.700> the 00:21:05.870 --> 00:21:05.880 align:start position:0% any question until now we have seen the 00:21:05.880 --> 00:21:07.130 align:start position:0% any question until now we have seen the Constructor<00:21:06.179> we<00:21:06.539> can<00:21:06.660> see<00:21:06.780> in<00:21:06.900> the<00:21:07.020> storage 00:21:07.130 --> 00:21:07.140 align:start position:0% Constructor we can see in the storage 00:21:07.140 --> 00:21:10.970 align:start position:0% Constructor we can see in the storage variables<00:21:07.940> Strokes<00:21:08.940> how<00:21:09.419> to<00:21:09.600> import<00:21:09.860> how<00:21:10.860> are 00:21:10.970 --> 00:21:10.980 align:start position:0% variables Strokes how to import how are 00:21:10.980 --> 00:21:13.490 align:start position:0% variables Strokes how to import how are you<00:21:11.100> finding<00:21:11.400> Cairo<00:21:11.760> too<00:21:12.120> difficult<00:21:12.539> or<00:21:13.200> is<00:21:13.380> it 00:21:13.490 --> 00:21:13.500 align:start position:0% you finding Cairo too difficult or is it 00:21:13.500 --> 00:21:15.590 align:start position:0% you finding Cairo too difficult or is it nice 00:21:15.590 --> 00:21:15.600 align:start position:0% nice 00:21:15.600 --> 00:21:22.190 align:start position:0% nice any<00:21:15.900> questions<00:21:16.260> yes 00:21:22.190 --> 00:21:22.200 align:start position:0% 00:21:22.200 --> 00:21:28.430 align:start position:0% have<00:21:22.679> you 00:21:28.430 --> 00:21:28.440 align:start position:0% 00:21:28.440 --> 00:21:37.130 align:start position:0% sorry<00:21:28.799> what<00:21:29.039> was<00:21:29.100> the<00:21:29.280> question 00:21:37.130 --> 00:21:37.140 align:start position:0% 00:21:37.140 --> 00:21:39.470 align:start position:0% yes<00:21:37.559> for<00:21:38.100> example<00:21:38.220> we<00:21:38.460> have<00:21:38.640> in<00:21:38.940> this<00:21:39.059> case<00:21:39.179> we 00:21:39.470 --> 00:21:39.480 align:start position:0% yes for example we have in this case we 00:21:39.480 --> 00:21:42.470 align:start position:0% yes for example we have in this case we will<00:21:39.600> be<00:21:39.720> using<00:21:40.020> addresses 00:21:42.470 --> 00:21:42.480 align:start position:0% will be using addresses 00:21:42.480 --> 00:21:45.289 align:start position:0% will be using addresses that<00:21:43.080> are<00:21:43.260> in<00:21:43.440> an<00:21:43.679> Excel<00:21:44.100> in<00:21:44.400> hexadecimal 00:21:45.289 --> 00:21:45.299 align:start position:0% that are in an Excel in hexadecimal 00:21:45.299 --> 00:21:47.450 align:start position:0% that are in an Excel in hexadecimal format<00:21:45.780> right<00:21:45.960> it<00:21:46.559> will<00:21:46.740> simply<00:21:46.980> be<00:21:47.039> converted 00:21:47.450 --> 00:21:47.460 align:start position:0% format right it will simply be converted 00:21:47.460 --> 00:21:48.970 align:start position:0% format right it will simply be converted to<00:21:47.580> a<00:21:47.700> field 00:21:48.970 --> 00:21:48.980 align:start position:0% to a field 00:21:48.980 --> 00:21:51.649 align:start position:0% to a field behind<00:21:49.980> it<00:21:50.159> will<00:21:50.400> be 00:21:51.649 --> 00:21:51.659 align:start position:0% behind it will be 00:21:51.659 --> 00:21:53.510 align:start position:0% behind it will be we<00:21:52.080> will<00:21:52.200> actually<00:21:52.440> deploy<00:21:52.860> right<00:21:53.039> now<00:21:53.220> our 00:21:53.510 --> 00:21:53.520 align:start position:0% we will actually deploy right now our 00:21:53.520 --> 00:21:56.990 align:start position:0% we will actually deploy right now our control<00:21:53.700> using<00:21:54.299> hex<00:21:54.840> hexadecimal<00:21:55.740> values<00:21:56.100> and 00:21:56.990 --> 00:21:57.000 align:start position:0% control using hex hexadecimal values and 00:21:57.000 --> 00:21:58.850 align:start position:0% control using hex hexadecimal values and you<00:21:57.240> will<00:21:57.419> have<00:21:57.600> to<00:21:57.720> convert<00:21:57.960> two<00:21:58.140> Fields<00:21:58.559> but 00:21:58.850 --> 00:21:58.860 align:start position:0% you will have to convert two Fields but 00:21:58.860 --> 00:22:00.590 align:start position:0% you will have to convert two Fields but you<00:21:59.100> also<00:21:59.340> could<00:21:59.460> compare<00:21:59.760> it<00:21:59.880> to<00:21:59.940> a<00:22:00.059> field<00:22:00.179> and 00:22:00.590 --> 00:22:00.600 align:start position:0% you also could compare it to a field and 00:22:00.600 --> 00:22:02.510 align:start position:0% you also could compare it to a field and also<00:22:00.780> you<00:22:00.900> play<00:22:01.080> with<00:22:01.260> this<00:22:01.440> no<00:22:01.919> problem<00:22:02.159> right 00:22:02.510 --> 00:22:02.520 align:start position:0% also you play with this no problem right 00:22:02.520 --> 00:22:04.730 align:start position:0% also you play with this no problem right now<00:22:02.580> we<00:22:02.700> can<00:22:02.820> think<00:22:03.000> of<00:22:03.179> it<00:22:03.360> like<00:22:03.539> big<00:22:04.200> integers 00:22:04.730 --> 00:22:04.740 align:start position:0% now we can think of it like big integers 00:22:04.740 --> 00:22:07.330 align:start position:0% now we can think of it like big integers and<00:22:04.919> we<00:22:05.039> can<00:22:05.159> get<00:22:05.280> deeper<00:22:05.640> into<00:22:05.700> that 00:22:07.330 --> 00:22:07.340 align:start position:0% and we can get deeper into that 00:22:07.340 --> 00:22:09.950 align:start position:0% and we can get deeper into that any<00:22:08.340> other<00:22:08.580> question<00:22:08.820> right<00:22:09.120> now<00:22:09.240> we<00:22:09.780> have 00:22:09.950 --> 00:22:09.960 align:start position:0% any other question right now we have 00:22:09.960 --> 00:22:11.450 align:start position:0% any other question right now we have seen<00:22:10.080> Constructors<00:22:10.620> towards<00:22:10.980> variables 00:22:11.450 --> 00:22:11.460 align:start position:0% seen Constructors towards variables 00:22:11.460 --> 00:22:14.810 align:start position:0% seen Constructors towards variables Strokes 00:22:14.810 --> 00:22:14.820 align:start position:0% 00:22:14.820 --> 00:22:17.210 align:start position:0% well<00:22:15.360> perfect<00:22:15.720> okay<00:22:16.080> so<00:22:16.860> here<00:22:17.039> our 00:22:17.210 --> 00:22:17.220 align:start position:0% well perfect okay so here our 00:22:17.220 --> 00:22:19.010 align:start position:0% well perfect okay so here our Constructor<00:22:17.640> and<00:22:18.059> with<00:22:18.240> this<00:22:18.419> we<00:22:18.600> can<00:22:18.780> deploy 00:22:19.010 --> 00:22:19.020 align:start position:0% Constructor and with this we can deploy 00:22:19.020 --> 00:22:21.409 align:start position:0% Constructor and with this we can deploy our<00:22:19.200> contracts 00:22:21.409 --> 00:22:21.419 align:start position:0% our contracts 00:22:21.419 --> 00:22:23.090 align:start position:0% our contracts also<00:22:22.080> this 00:22:23.090 --> 00:22:23.100 align:start position:0% also this 00:22:23.100 --> 00:22:24.830 align:start position:0% also this um as<00:22:23.760> you<00:22:23.880> can<00:22:24.000> see 00:22:24.830 --> 00:22:24.840 align:start position:0% um as you can see 00:22:24.840 --> 00:22:26.450 align:start position:0% um as you can see the<00:22:25.260> structure<00:22:25.559> of<00:22:25.679> the<00:22:25.799> contract<00:22:26.100> is<00:22:26.280> very 00:22:26.450 --> 00:22:26.460 align:start position:0% the structure of the contract is very 00:22:26.460 --> 00:22:28.610 align:start position:0% the structure of the contract is very similar<00:22:26.760> to<00:22:26.880> solidity<00:22:27.360> we're<00:22:28.140> trying<00:22:28.440> to 00:22:28.610 --> 00:22:28.620 align:start position:0% similar to solidity we're trying to 00:22:28.620 --> 00:22:30.529 align:start position:0% similar to solidity we're trying to follow<00:22:28.799> the<00:22:29.280> guidelines<00:22:29.760> of<00:22:30.120> smart 00:22:30.529 --> 00:22:30.539 align:start position:0% follow the guidelines of smart 00:22:30.539 --> 00:22:33.470 align:start position:0% follow the guidelines of smart conducting<00:22:31.080> solidity<00:22:31.500> you<00:22:31.679> have<00:22:31.860> Getters<00:22:32.480> you 00:22:33.470 --> 00:22:33.480 align:start position:0% conducting solidity you have Getters you 00:22:33.480 --> 00:22:36.950 align:start position:0% conducting solidity you have Getters you have<00:22:33.659> the<00:22:33.900> Constructor<00:22:34.380> and<00:22:35.280> the<00:22:36.179> format<00:22:36.780> is 00:22:36.950 --> 00:22:36.960 align:start position:0% have the Constructor and the format is 00:22:36.960 --> 00:22:38.690 align:start position:0% have the Constructor and the format is very<00:22:37.080> similar<00:22:37.440> also<00:22:38.100> if<00:22:38.220> you<00:22:38.220> go<00:22:38.400> to<00:22:38.520> this 00:22:38.690 --> 00:22:38.700 align:start position:0% very similar also if you go to this 00:22:38.700 --> 00:22:41.090 align:start position:0% very similar also if you go to this contract<00:22:39.059> is<00:22:39.360> very<00:22:39.659> well<00:22:39.960> commented<00:22:40.740> so<00:22:40.919> you 00:22:41.090 --> 00:22:41.100 align:start position:0% contract is very well commented so you 00:22:41.100 --> 00:22:42.890 align:start position:0% contract is very well commented so you can<00:22:41.220> know<00:22:41.340> what<00:22:41.520> is<00:22:41.700> happening 00:22:42.890 --> 00:22:42.900 align:start position:0% can know what is happening 00:22:42.900 --> 00:22:48.350 align:start position:0% can know what is happening because 00:22:48.350 --> 00:22:48.360 align:start position:0% 00:22:48.360 --> 00:23:03.549 align:start position:0% foreign 00:23:03.549 --> 00:23:03.559 align:start position:0% 00:23:03.559 --> 00:23:07.370 align:start position:0% I<00:23:04.559> think<00:23:04.679> you<00:23:05.520> guys<00:23:05.700> can<00:23:05.940> yeah<00:23:06.480> sure<00:23:06.840> so 00:23:07.370 --> 00:23:07.380 align:start position:0% I think you guys can yeah sure so 00:23:07.380 --> 00:23:09.830 align:start position:0% I think you guys can yeah sure so there's<00:23:08.100> no<00:23:08.340> inheritance<00:23:08.940> in<00:23:09.120> Cairo<00:23:09.539> you 00:23:09.830 --> 00:23:09.840 align:start position:0% there's no inheritance in Cairo you 00:23:09.840 --> 00:23:11.930 align:start position:0% there's no inheritance in Cairo you don't<00:23:10.020> inherit<00:23:10.500> your<00:23:10.679> contract<00:23:11.039> what<00:23:11.640> you<00:23:11.760> do 00:23:11.930 --> 00:23:11.940 align:start position:0% don't inherit your contract what you do 00:23:11.940 --> 00:23:13.970 align:start position:0% don't inherit your contract what you do is<00:23:12.059> you<00:23:12.240> import<00:23:12.419> your<00:23:12.780> function<00:23:13.200> so<00:23:13.799> if<00:23:13.919> you're 00:23:13.970 --> 00:23:13.980 align:start position:0% is you import your function so if you're 00:23:13.980 --> 00:23:16.669 align:start position:0% is you import your function so if you're looking<00:23:14.159> at<00:23:14.400> the<00:23:14.520> the<00:23:15.000> top<00:23:15.240> of<00:23:15.360> the<00:23:15.539> uh<00:23:15.900> of<00:23:16.500> the 00:23:16.669 --> 00:23:16.679 align:start position:0% looking at the the top of the uh of the 00:23:16.679 --> 00:23:20.750 align:start position:0% looking at the the top of the uh of the contract<00:23:16.980> up<00:23:17.340> there<00:23:18.020> here<00:23:19.020> is<00:23:19.260> importing<00:23:19.760> a 00:23:20.750 --> 00:23:20.760 align:start position:0% contract up there here is importing a 00:23:20.760 --> 00:23:22.610 align:start position:0% contract up there here is importing a templates<00:23:21.059> developed<00:23:21.659> by<00:23:21.780> open<00:23:21.960> the<00:23:22.260> printer 00:23:22.610 --> 00:23:22.620 align:start position:0% templates developed by open the printer 00:23:22.620 --> 00:23:24.830 align:start position:0% templates developed by open the printer is<00:23:22.799> importing<00:23:23.220> the<00:23:23.640> full<00:23:24.000> contract<00:23:24.480> which<00:23:24.720> is 00:23:24.830 --> 00:23:24.840 align:start position:0% is importing the full contract which is 00:23:24.840 --> 00:23:27.110 align:start position:0% is importing the full contract which is called<00:23:25.020> audible<00:23:25.559> so<00:23:26.280> it<00:23:26.400> means<00:23:26.640> that<00:23:26.820> he 00:23:27.110 --> 00:23:27.120 align:start position:0% called audible so it means that he 00:23:27.120 --> 00:23:28.970 align:start position:0% called audible so it means that he Imports<00:23:27.659> all<00:23:27.900> the<00:23:28.140> functions<00:23:28.500> that<00:23:28.740> are 00:23:28.970 --> 00:23:28.980 align:start position:0% Imports all the functions that are 00:23:28.980 --> 00:23:31.190 align:start position:0% Imports all the functions that are inside<00:23:29.280> of<00:23:29.580> this<00:23:29.760> contract<00:23:30.120> and<00:23:30.720> inside<00:23:30.960> of 00:23:31.190 --> 00:23:31.200 align:start position:0% inside of this contract and inside of 00:23:31.200 --> 00:23:33.289 align:start position:0% inside of this contract and inside of this<00:23:31.380> contract<00:23:31.679> you<00:23:32.039> know<00:23:32.159> it<00:23:32.340> creates<00:23:32.760> it 00:23:33.289 --> 00:23:33.299 align:start position:0% this contract you know it creates it 00:23:33.299 --> 00:23:34.789 align:start position:0% this contract you know it creates it creates<00:23:33.600> a<00:23:33.720> few<00:23:33.840> variables<00:23:34.320> that<00:23:34.500> can<00:23:34.679> be 00:23:34.789 --> 00:23:34.799 align:start position:0% creates a few variables that can be 00:23:34.799 --> 00:23:37.010 align:start position:0% creates a few variables that can be initialized<00:23:35.280> and 00:23:37.010 --> 00:23:37.020 align:start position:0% initialized and 00:23:37.020 --> 00:23:39.230 align:start position:0% initialized and um one<00:23:37.500> of<00:23:37.620> them<00:23:37.740> is<00:23:38.220> called<00:23:38.400> the<00:23:38.580> initializer 00:23:39.230 --> 00:23:39.240 align:start position:0% um one of them is called the initializer 00:23:39.240 --> 00:23:40.549 align:start position:0% um one of them is called the initializer which<00:23:39.480> is<00:23:39.600> supposed<00:23:39.780> to<00:23:39.960> be<00:23:40.080> called<00:23:40.260> during 00:23:40.549 --> 00:23:40.559 align:start position:0% which is supposed to be called during 00:23:40.559 --> 00:23:42.350 align:start position:0% which is supposed to be called during this<00:23:40.919> Constructor<00:23:41.400> does<00:23:41.880> that<00:23:42.059> make<00:23:42.179> sense 00:23:42.350 --> 00:23:42.360 align:start position:0% this Constructor does that make sense 00:23:42.360 --> 00:23:45.710 align:start position:0% this Constructor does that make sense yes<00:23:43.200> I<00:23:43.799> was<00:23:43.980> just<00:23:44.100> curious<00:23:44.640> because<00:23:44.940> usually 00:23:45.710 --> 00:23:45.720 align:start position:0% yes I was just curious because usually 00:23:45.720 --> 00:23:47.690 align:start position:0% yes I was just curious because usually that's 00:23:47.690 --> 00:23:47.700 align:start position:0% that's 00:23:47.700 --> 00:23:49.210 align:start position:0% that's thread 00:23:49.210 --> 00:23:49.220 align:start position:0% thread 00:23:49.220 --> 00:23:51.710 align:start position:0% thread so<00:23:50.220> it's<00:23:50.460> not<00:23:50.580> explicitly<00:23:51.120> it's<00:23:51.480> not 00:23:51.710 --> 00:23:51.720 align:start position:0% so it's not explicitly it's not 00:23:51.720 --> 00:23:54.950 align:start position:0% so it's not explicitly it's not automatically<00:23:52.500> initialized<00:23:53.460> because 00:23:54.950 --> 00:23:54.960 align:start position:0% automatically initialized because 00:23:54.960 --> 00:23:57.350 align:start position:0% automatically initialized because um<00:23:55.020> because<00:23:55.380> it's<00:23:55.559> not<00:23:55.679> like<00:23:56.220> the<00:23:56.580> contract<00:23:56.940> is 00:23:57.350 --> 00:23:57.360 align:start position:0% um because it's not like the contract is 00:23:57.360 --> 00:23:59.570 align:start position:0% um because it's not like the contract is not<00:23:57.480> ownable<00:23:57.900> it<00:23:58.200> Imports<00:23:58.620> some<00:23:58.860> function<00:23:59.220> and 00:23:59.570 --> 00:23:59.580 align:start position:0% not ownable it Imports some function and 00:23:59.580 --> 00:24:01.490 align:start position:0% not ownable it Imports some function and it<00:23:59.700> has<00:23:59.820> no<00:23:59.940> way<00:24:00.120> to<00:24:00.240> know<00:24:00.480> that<00:24:01.020> this<00:24:01.200> is<00:24:01.320> the 00:24:01.490 --> 00:24:01.500 align:start position:0% it has no way to know that this is the 00:24:01.500 --> 00:24:02.870 align:start position:0% it has no way to know that this is the specific<00:24:01.740> context<00:24:02.039> of<00:24:02.220> the<00:24:02.340> Constructor<00:24:02.640> so 00:24:02.870 --> 00:24:02.880 align:start position:0% specific context of the Constructor so 00:24:02.880 --> 00:24:04.909 align:start position:0% specific context of the Constructor so you<00:24:03.000> need<00:24:03.179> to<00:24:03.240> initialize<00:24:03.720> it<00:24:03.900> explicitly 00:24:04.909 --> 00:24:04.919 align:start position:0% you need to initialize it explicitly 00:24:04.919 --> 00:24:08.330 align:start position:0% you need to initialize it explicitly regarding<00:24:05.700> the<00:24:05.820> question<00:24:06.000> on<00:24:06.299> felt<00:24:06.840> earlier 00:24:08.330 --> 00:24:08.340 align:start position:0% regarding the question on felt earlier 00:24:08.340 --> 00:24:10.310 align:start position:0% regarding the question on felt earlier um I'm<00:24:08.520> not<00:24:08.700> sure<00:24:08.820> what<00:24:09.059> confuses<00:24:09.659> you<00:24:09.900> but 00:24:10.310 --> 00:24:10.320 align:start position:0% um I'm not sure what confuses you but 00:24:10.320 --> 00:24:12.110 align:start position:0% um I'm not sure what confuses you but when<00:24:10.740> you're<00:24:10.860> looking<00:24:11.039> at<00:24:11.340> variables<00:24:12.000> in 00:24:12.110 --> 00:24:12.120 align:start position:0% when you're looking at variables in 00:24:12.120 --> 00:24:14.810 align:start position:0% when you're looking at variables in solidity<00:24:12.659> you<00:24:13.200> know<00:24:13.260> at<00:24:13.559> the<00:24:13.679> bottom<00:24:13.919> of<00:24:14.100> it<00:24:14.280> at 00:24:14.810 --> 00:24:14.820 align:start position:0% solidity you know at the bottom of it at 00:24:14.820 --> 00:24:17.210 align:start position:0% solidity you know at the bottom of it at the<00:24:14.940> end<00:24:15.000> of<00:24:15.120> the<00:24:15.240> day<00:24:15.360> it's<00:24:15.900> a<00:24:16.080> number<00:24:16.260> and 00:24:17.210 --> 00:24:17.220 align:start position:0% the end of the day it's a number and 00:24:17.220 --> 00:24:19.970 align:start position:0% the end of the day it's a number and Cairo<00:24:17.880> is<00:24:18.120> a<00:24:18.600> fairly<00:24:18.900> new<00:24:19.200> language<00:24:19.440> it<00:24:19.860> will 00:24:19.970 --> 00:24:19.980 align:start position:0% Cairo is a fairly new language it will 00:24:19.980 --> 00:24:22.250 align:start position:0% Cairo is a fairly new language it will get<00:24:20.159> better<00:24:20.340> in<00:24:20.760> the<00:24:20.940> next<00:24:21.000> few<00:24:21.240> months<00:24:21.600> but 00:24:22.250 --> 00:24:22.260 align:start position:0% get better in the next few months but 00:24:22.260 --> 00:24:24.110 align:start position:0% get better in the next few months but right<00:24:22.500> now<00:24:22.740> it<00:24:23.159> treats<00:24:23.520> everything<00:24:23.700> as<00:24:24.000> a 00:24:24.110 --> 00:24:24.120 align:start position:0% right now it treats everything as a 00:24:24.120 --> 00:24:26.090 align:start position:0% right now it treats everything as a number<00:24:24.299> so<00:24:24.900> if<00:24:25.080> you<00:24:25.200> want<00:24:25.320> to<00:24:25.440> perform<00:24:25.620> actions 00:24:26.090 --> 00:24:26.100 align:start position:0% number so if you want to perform actions 00:24:26.100 --> 00:24:27.590 align:start position:0% number so if you want to perform actions when<00:24:26.220> you<00:24:26.340> need<00:24:26.520> strings<00:24:26.820> you<00:24:27.120> basically<00:24:27.419> need 00:24:27.590 --> 00:24:27.600 align:start position:0% when you need strings you basically need 00:24:27.600 --> 00:24:29.210 align:start position:0% when you need strings you basically need to<00:24:27.720> assume<00:24:28.140> that<00:24:28.380> you<00:24:28.620> receive<00:24:28.919> them<00:24:29.039> as 00:24:29.210 --> 00:24:29.220 align:start position:0% to assume that you receive them as 00:24:29.220 --> 00:24:30.770 align:start position:0% to assume that you receive them as numbers<00:24:29.460> you<00:24:29.820> convert<00:24:30.179> them<00:24:30.299> you<00:24:30.480> do<00:24:30.600> your 00:24:30.770 --> 00:24:30.780 align:start position:0% numbers you convert them you do your 00:24:30.780 --> 00:24:32.450 align:start position:0% numbers you convert them you do your operations<00:24:31.200> and<00:24:31.620> you<00:24:31.679> do<00:24:31.860> all<00:24:32.039> this<00:24:32.220> kind<00:24:32.340> of 00:24:32.450 --> 00:24:32.460 align:start position:0% operations and you do all this kind of 00:24:32.460 --> 00:24:34.070 align:start position:0% operations and you do all this kind of stuff<00:24:32.580> make<00:24:33.059> sense 00:24:34.070 --> 00:24:34.080 align:start position:0% stuff make sense 00:24:34.080 --> 00:24:37.549 align:start position:0% stuff make sense sort<00:24:34.860> of 00:24:37.549 --> 00:24:37.559 align:start position:0% 00:24:37.559 --> 00:24:43.970 align:start position:0% yep 00:24:43.970 --> 00:24:43.980 align:start position:0% 00:24:43.980 --> 00:24:46.789 align:start position:0% yeah<00:24:44.580> so<00:24:45.000> a<00:24:45.539> felt<00:24:46.020> is<00:24:46.140> as<00:24:46.440> you<00:24:46.559> mentioned 00:24:46.789 --> 00:24:46.799 align:start position:0% yeah so a felt is as you mentioned 00:24:46.799 --> 00:24:48.230 align:start position:0% yeah so a felt is as you mentioned earlier<00:24:47.100> I<00:24:47.220> think<00:24:47.340> I<00:24:47.460> heard<00:24:47.640> you<00:24:47.760> say<00:24:47.880> it<00:24:48.059> it's 00:24:48.230 --> 00:24:48.240 align:start position:0% earlier I think I heard you say it it's 00:24:48.240 --> 00:24:52.970 align:start position:0% earlier I think I heard you say it it's a<00:24:48.419> field<00:24:48.539> element<00:24:48.919> so<00:24:49.919> Cairo<00:24:50.760> is<00:24:51.480> like 00:24:52.970 --> 00:24:52.980 align:start position:0% a field element so Cairo is like 00:24:52.980 --> 00:24:55.789 align:start position:0% a field element so Cairo is like the<00:24:53.580> felt<00:24:54.240> you<00:24:54.360> can't<00:24:54.900> think<00:24:55.080> of<00:24:55.200> it<00:24:55.380> as<00:24:55.559> a<00:24:55.679> big 00:24:55.789 --> 00:24:55.799 align:start position:0% the felt you can't think of it as a big 00:24:55.799 --> 00:24:58.669 align:start position:0% the felt you can't think of it as a big end<00:24:55.980> but<00:24:56.159> it's<00:24:56.340> basically<00:24:56.700> a<00:24:57.120> number<00:24:57.900> over<00:24:58.380> a 00:24:58.669 --> 00:24:58.679 align:start position:0% end but it's basically a number over a 00:24:58.679 --> 00:25:01.430 align:start position:0% end but it's basically a number over a big<00:24:58.919> film<00:24:59.220> The<00:24:59.640> Field<00:25:00.120> that<00:25:00.360> is<00:25:00.480> a<00:25:00.659> prime<00:25:00.840> that 00:25:01.430 --> 00:25:01.440 align:start position:0% big film The Field that is a prime that 00:25:01.440 --> 00:25:03.590 align:start position:0% big film The Field that is a prime that does<00:25:01.620> indeed<00:25:02.039> uh 00:25:03.590 --> 00:25:03.600 align:start position:0% does indeed uh 00:25:03.600 --> 00:25:06.289 align:start position:0% does indeed uh um<00:25:03.740> field<00:25:04.740> integer<00:25:05.400> mathematics<00:25:06.179> and 00:25:06.289 --> 00:25:06.299 align:start position:0% um field integer mathematics and 00:25:06.299 --> 00:25:08.149 align:start position:0% um field integer mathematics and arithmetics<00:25:06.840> that<00:25:07.080> makes<00:25:07.320> sense<00:25:07.500> so<00:25:08.039> it's 00:25:08.149 --> 00:25:08.159 align:start position:0% arithmetics that makes sense so it's 00:25:08.159 --> 00:25:10.490 align:start position:0% arithmetics that makes sense so it's really<00:25:08.340> like<00:25:08.640> you<00:25:09.059> can<00:25:09.179> treat<00:25:09.360> it<00:25:09.600> as<00:25:09.780> modulo 00:25:10.490 --> 00:25:10.500 align:start position:0% really like you can treat it as modulo 00:25:10.500 --> 00:25:12.830 align:start position:0% really like you can treat it as modulo operations<00:25:10.980> the<00:25:11.520> only<00:25:11.700> time<00:25:12.120> where<00:25:12.419> it<00:25:12.539> gets 00:25:12.830 --> 00:25:12.840 align:start position:0% operations the only time where it gets 00:25:12.840 --> 00:25:16.070 align:start position:0% operations the only time where it gets weird<00:25:12.960> is<00:25:13.559> for<00:25:13.860> divisions<00:25:14.520> division<00:25:15.419> sucks<00:25:15.840> I 00:25:16.070 --> 00:25:16.080 align:start position:0% weird is for divisions division sucks I 00:25:16.080 --> 00:25:18.370 align:start position:0% weird is for divisions division sucks I don't<00:25:16.200> like<00:25:16.380> them 00:25:18.370 --> 00:25:18.380 align:start position:0% don't like them 00:25:18.380 --> 00:25:20.810 align:start position:0% don't like them no<00:25:19.380> problem<00:25:19.500> with<00:25:19.799> that 00:25:20.810 --> 00:25:20.820 align:start position:0% no problem with that 00:25:20.820 --> 00:25:22.970 align:start position:0% no problem with that so<00:25:21.179> for<00:25:21.360> example<00:25:21.659> we<00:25:22.320> were<00:25:22.440> talking<00:25:22.559> about<00:25:22.799> the 00:25:22.970 --> 00:25:22.980 align:start position:0% so for example we were talking about the 00:25:22.980 --> 00:25:24.529 align:start position:0% so for example we were talking about the honorable<00:25:23.340> contract<00:25:23.700> this<00:25:23.940> is<00:25:24.059> the<00:25:24.179> one<00:25:24.299> that 00:25:24.529 --> 00:25:24.539 align:start position:0% honorable contract this is the one that 00:25:24.539 --> 00:25:26.210 align:start position:0% honorable contract this is the one that were<00:25:24.720> important<00:25:25.140> so<00:25:25.679> we<00:25:25.799> have<00:25:25.919> it<00:25:26.039> here 00:25:26.210 --> 00:25:26.220 align:start position:0% were important so we have it here 00:25:26.220 --> 00:25:28.669 align:start position:0% were important so we have it here locally<00:25:27.059> and<00:25:27.539> we're<00:25:27.659> importing<00:25:28.080> for<00:25:28.260> me<00:25:28.380> this 00:25:28.669 --> 00:25:28.679 align:start position:0% locally and we're importing for me this 00:25:28.679 --> 00:25:33.110 align:start position:0% locally and we're importing for me this is<00:25:28.799> the<00:25:28.980> owner<00:25:29.400> which<00:25:29.760> comes<00:25:30.000> in<00:25:30.059> a<00:25:30.240> namespace 00:25:33.110 --> 00:25:33.120 align:start position:0% 00:25:33.120 --> 00:25:40.850 align:start position:0% so<00:25:33.600> we're<00:25:33.779> importing<00:25:34.200> these<00:25:34.500> functions 00:25:40.850 --> 00:25:40.860 align:start position:0% 00:25:40.860 --> 00:25:43.330 align:start position:0% yes 00:25:43.330 --> 00:25:43.340 align:start position:0% yes 00:25:43.340 --> 00:25:46.430 align:start position:0% yes there<00:25:44.340> are<00:25:44.400> no<00:25:44.460> inheritance<00:25:45.120> in<00:25:45.299> Cairo 00:25:46.430 --> 00:25:46.440 align:start position:0% there are no inheritance in Cairo 00:25:46.440 --> 00:25:49.610 align:start position:0% there are no inheritance in Cairo perfect<00:25:46.860> so<00:25:47.159> going<00:25:47.520> back<00:25:47.700> to 00:25:49.610 --> 00:25:49.620 align:start position:0% perfect so going back to 00:25:49.620 --> 00:25:51.590 align:start position:0% perfect so going back to I<00:25:50.159> can't<00:25:50.400> read 00:25:51.590 --> 00:25:51.600 align:start position:0% I can't read 00:25:51.600 --> 00:25:55.610 align:start position:0% I can't read two 00:25:55.610 --> 00:25:55.620 align:start position:0% 00:25:55.620 --> 00:25:58.010 align:start position:0% so<00:25:56.340> we<00:25:56.880> import<00:25:57.059> these<00:25:57.360> functions<00:25:57.659> honorable 00:25:58.010 --> 00:25:58.020 align:start position:0% so we import these functions honorable 00:25:58.020 --> 00:26:01.130 align:start position:0% so we import these functions honorable and<00:25:58.260> possible<00:25:58.620> from<00:25:59.240> functions<00:26:00.240> inside<00:26:00.720> the 00:26:01.130 --> 00:26:01.140 align:start position:0% and possible from functions inside the 00:26:01.140 --> 00:26:02.990 align:start position:0% and possible from functions inside the ownable<00:26:01.620> namespace<00:26:02.400> and<00:26:02.640> inside<00:26:02.760> the 00:26:02.990 --> 00:26:03.000 align:start position:0% ownable namespace and inside the 00:26:03.000 --> 00:26:05.810 align:start position:0% ownable namespace and inside the possible<00:26:03.299> namespace<00:26:03.779> you<00:26:04.320> can<00:26:04.500> yeah 00:26:05.810 --> 00:26:05.820 align:start position:0% possible namespace you can yeah 00:26:05.820 --> 00:26:07.730 align:start position:0% possible namespace you can yeah and 00:26:07.730 --> 00:26:07.740 align:start position:0% and 00:26:07.740 --> 00:26:08.470 align:start position:0% and there's<00:26:08.039> a<00:26:08.220> question 00:26:08.470 --> 00:26:08.480 align:start position:0% there's a question 00:26:08.480 --> 00:26:22.430 align:start position:0% there's a question [Music] 00:26:22.430 --> 00:26:22.440 align:start position:0% [Music] 00:26:22.440 --> 00:26:23.290 align:start position:0% [Music] foreign 00:26:23.290 --> 00:26:23.300 align:start position:0% foreign 00:26:23.300 --> 00:26:48.310 align:start position:0% foreign [Music] 00:26:48.310 --> 00:26:48.320 align:start position:0% 00:26:48.320 --> 00:26:51.769 align:start position:0% yes<00:26:49.320> open<00:26:49.559> Zeppelin<00:26:50.100> is<00:26:50.279> working<00:26:50.460> to<00:26:51.179> create 00:26:51.769 --> 00:26:51.779 align:start position:0% yes open Zeppelin is working to create 00:26:51.779 --> 00:26:53.810 align:start position:0% yes open Zeppelin is working to create the<00:26:52.260> standard<00:26:52.559> implementation<00:26:53.100> so<00:26:53.400> any<00:26:53.700> kind 00:26:53.810 --> 00:26:53.820 align:start position:0% the standard implementation so any kind 00:26:53.820 --> 00:26:55.490 align:start position:0% the standard implementation so any kind of<00:26:53.940> contract<00:26:54.240> you<00:26:54.480> have<00:26:54.600> on<00:26:54.779> solidity<00:26:55.200> you're 00:26:55.490 --> 00:26:55.500 align:start position:0% of contract you have on solidity you're 00:26:55.500 --> 00:26:56.710 align:start position:0% of contract you have on solidity you're used<00:26:55.740> to<00:26:55.919> have 00:26:56.710 --> 00:26:56.720 align:start position:0% used to have 00:26:56.720 --> 00:26:59.269 align:start position:0% used to have that<00:26:57.720> is<00:26:57.840> done<00:26:57.960> by<00:26:58.140> open<00:26:58.200> Zeppelin<00:26:58.740> we're 00:26:59.269 --> 00:26:59.279 align:start position:0% that is done by open Zeppelin we're 00:26:59.279 --> 00:27:02.090 align:start position:0% that is done by open Zeppelin we're walking<00:26:59.580> towards<00:27:00.240> having<00:27:00.720> that<00:27:01.080> that<00:27:01.860> being 00:27:02.090 --> 00:27:02.100 align:start position:0% walking towards having that that being 00:27:02.100 --> 00:27:03.529 align:start position:0% walking towards having that that being said<00:27:02.279> I<00:27:02.400> mean<00:27:02.520> it<00:27:02.640> takes<00:27:02.820> time<00:27:03.000> to<00:27:03.240> develop 00:27:03.529 --> 00:27:03.539 align:start position:0% said I mean it takes time to develop 00:27:03.539 --> 00:27:04.850 align:start position:0% said I mean it takes time to develop contracts<00:27:03.960> that<00:27:04.080> are<00:27:04.260> secure<00:27:04.559> and<00:27:04.740> everything 00:27:04.850 --> 00:27:04.860 align:start position:0% contracts that are secure and everything 00:27:04.860 --> 00:27:07.250 align:start position:0% contracts that are secure and everything so<00:27:05.400> if<00:27:06.000> you<00:27:06.120> want<00:27:06.240> to<00:27:06.360> develop<00:27:06.600> them<00:27:06.840> you 00:27:07.250 --> 00:27:07.260 align:start position:0% so if you want to develop them you 00:27:07.260 --> 00:27:09.529 align:start position:0% so if you want to develop them you should<00:27:07.380> it's<00:27:07.799> worth<00:27:07.980> it<00:27:08.220> it's<00:27:08.580> fun<00:27:08.820> and<00:27:09.360> you 00:27:09.529 --> 00:27:09.539 align:start position:0% should it's worth it it's fun and you 00:27:09.539 --> 00:27:11.029 align:start position:0% should it's worth it it's fun and you know<00:27:09.659> you<00:27:09.840> may<00:27:09.960> develop<00:27:10.260> stuff<00:27:10.559> that<00:27:10.740> gets 00:27:11.029 --> 00:27:11.039 align:start position:0% know you may develop stuff that gets 00:27:11.039 --> 00:27:13.010 align:start position:0% know you may develop stuff that gets used<00:27:11.100> by<00:27:11.340> other<00:27:11.520> people<00:27:11.760> which<00:27:12.059> is<00:27:12.179> great 00:27:13.010 --> 00:27:13.020 align:start position:0% used by other people which is great 00:27:13.020 --> 00:27:15.409 align:start position:0% used by other people which is great this<00:27:13.740> actually<00:27:14.100> principally<00:27:14.700> the<00:27:15.059> contracts 00:27:15.409 --> 00:27:15.419 align:start position:0% this actually principally the contracts 00:27:15.419 --> 00:27:16.970 align:start position:0% this actually principally the contracts incredible<00:27:15.779> principling<00:27:16.440> they<00:27:16.679> have<00:27:16.799> a<00:27:16.860> lot 00:27:16.970 --> 00:27:16.980 align:start position:0% incredible principling they have a lot 00:27:16.980 --> 00:27:19.070 align:start position:0% incredible principling they have a lot of<00:27:17.039> contributions<00:27:17.580> from<00:27:17.940> people<00:27:18.480> outside<00:27:18.779> the 00:27:19.070 --> 00:27:19.080 align:start position:0% of contributions from people outside the 00:27:19.080 --> 00:27:21.409 align:start position:0% of contributions from people outside the community<00:27:19.320> so<00:27:19.799> that<00:27:20.159> will<00:27:20.340> be<00:27:20.400> where<00:27:20.520> it<00:27:20.760> also 00:27:21.409 --> 00:27:21.419 align:start position:0% community so that will be where it also 00:27:21.419 --> 00:27:23.990 align:start position:0% community so that will be where it also if<00:27:21.900> somebody<00:27:22.140> manages<00:27:22.620> to<00:27:22.980> write<00:27:23.279> a<00:27:23.580> Cairo 00:27:23.990 --> 00:27:24.000 align:start position:0% if somebody manages to write a Cairo 00:27:24.000 --> 00:27:25.909 align:start position:0% if somebody manages to write a Cairo contract<00:27:24.419> that<00:27:24.840> is<00:27:24.960> the<00:27:25.140> equivalent<00:27:25.500> to<00:27:25.799> this 00:27:25.909 --> 00:27:25.919 align:start position:0% contract that is the equivalent to this 00:27:25.919 --> 00:27:29.090 align:start position:0% contract that is the equivalent to this taking<00:27:26.279> contract<00:27:26.820> in<00:27:27.659> synthetics<00:27:28.260> which<00:27:28.919> is 00:27:29.090 --> 00:27:29.100 align:start position:0% taking contract in synthetics which is 00:27:29.100 --> 00:27:33.230 align:start position:0% taking contract in synthetics which is used<00:27:29.520> by<00:27:29.820> everyone<00:27:30.120> I'll<00:27:30.720> buy<00:27:30.960> you<00:27:31.080> a<00:27:31.260> beer 00:27:33.230 --> 00:27:33.240 align:start position:0% used by everyone I'll buy you a beer 00:27:33.240 --> 00:27:34.240 align:start position:0% used by everyone I'll buy you a beer more<00:27:33.600> than<00:27:33.779> a<00:27:33.960> view 00:27:34.240 --> 00:27:34.250 align:start position:0% more than a view 00:27:34.250 --> 00:27:34.370 align:start position:0% more than a view [Music] 00:27:34.370 --> 00:27:34.380 align:start position:0% [Music] 00:27:34.380 --> 00:27:39.110 align:start position:0% [Music] [Laughter] 00:27:39.110 --> 00:27:39.120 align:start position:0% 00:27:39.120 --> 00:27:41.750 align:start position:0% it<00:27:39.659> will<00:27:39.720> eventually<00:27:40.080> happen<00:27:40.440> it's<00:27:41.340> very<00:27:41.520> if 00:27:41.750 --> 00:27:41.760 align:start position:0% it will eventually happen it's very if 00:27:41.760 --> 00:27:44.930 align:start position:0% it will eventually happen it's very if you<00:27:41.880> it's<00:27:42.120> one<00:27:42.299> of<00:27:42.419> you 00:27:44.930 --> 00:27:44.940 align:start position:0% 00:27:44.940 --> 00:27:46.789 align:start position:0% okay 00:27:46.789 --> 00:27:46.799 align:start position:0% okay 00:27:46.799 --> 00:27:49.430 align:start position:0% okay so<00:27:47.279> we<00:27:47.400> got<00:27:47.580> our<00:27:47.700> Constructor 00:27:49.430 --> 00:27:49.440 align:start position:0% so we got our Constructor 00:27:49.440 --> 00:27:52.250 align:start position:0% so we got our Constructor and<00:27:50.039> then<00:27:50.220> we<00:27:50.520> can<00:27:50.640> get<00:27:50.820> to<00:27:51.000> the<00:27:51.240> here<00:27:52.080> we're 00:27:52.250 --> 00:27:52.260 align:start position:0% and then we can get to the here we're 00:27:52.260 --> 00:27:53.990 align:start position:0% and then we can get to the here we're using<00:27:52.559> the<00:27:52.679> initializer<00:27:53.220> function<00:27:53.520> inside 00:27:53.990 --> 00:27:54.000 align:start position:0% using the initializer function inside 00:27:54.000 --> 00:27:55.970 align:start position:0% using the initializer function inside the<00:27:54.299> ownable<00:27:54.779> namespace 00:27:55.970 --> 00:27:55.980 align:start position:0% the ownable namespace 00:27:55.980 --> 00:27:59.390 align:start position:0% the ownable namespace and<00:27:56.640> then<00:27:56.940> we<00:27:57.120> go<00:27:57.240> to<00:27:57.360> the<00:27:57.539> Getters<00:27:57.900> is<00:27:58.620> very 00:27:59.390 --> 00:27:59.400 align:start position:0% and then we go to the Getters is very 00:27:59.400 --> 00:28:02.870 align:start position:0% and then we go to the Getters is very simple<00:28:00.020> functions<00:28:01.020> by<00:28:01.260> definition<00:28:01.440> in<00:28:02.340> Cairo 00:28:02.870 --> 00:28:02.880 align:start position:0% simple functions by definition in Cairo 00:28:02.880 --> 00:28:08.029 align:start position:0% simple functions by definition in Cairo are<00:28:03.120> private<00:28:04.080> not<00:28:04.860> like<00:28:05.600> solidity<00:28:06.600> so<00:28:07.559> here<00:28:07.799> if 00:28:08.029 --> 00:28:08.039 align:start position:0% are private not like solidity so here if 00:28:08.039 --> 00:28:09.950 align:start position:0% are private not like solidity so here if we<00:28:08.159> want<00:28:08.279> to<00:28:08.400> have<00:28:08.580> Getters<00:28:09.179> functions<00:28:09.720> to 00:28:09.950 --> 00:28:09.960 align:start position:0% we want to have Getters functions to 00:28:09.960 --> 00:28:12.710 align:start position:0% we want to have Getters functions to read<00:28:10.260> information<00:28:10.880> we<00:28:11.880> have<00:28:12.120> to<00:28:12.240> explicitly 00:28:12.710 --> 00:28:12.720 align:start position:0% read information we have to explicitly 00:28:12.720 --> 00:28:15.470 align:start position:0% read information we have to explicitly tell<00:28:13.020> that<00:28:13.320> they<00:28:13.500> are<00:28:13.679> getters<00:28:14.580> so<00:28:15.240> and 00:28:15.470 --> 00:28:15.480 align:start position:0% tell that they are getters so and 00:28:15.480 --> 00:28:16.490 align:start position:0% tell that they are getters so and something<00:28:15.659> that<00:28:15.900> I<00:28:15.960> forgot<00:28:16.260> to<00:28:16.320> mention 00:28:16.490 --> 00:28:16.500 align:start position:0% something that I forgot to mention 00:28:16.500 --> 00:28:18.649 align:start position:0% something that I forgot to mention before<00:28:16.799> but<00:28:17.220> this<00:28:17.520> is<00:28:17.700> the<00:28:17.880> way 00:28:18.649 --> 00:28:18.659 align:start position:0% before but this is the way 00:28:18.659 --> 00:28:20.810 align:start position:0% before but this is the way like<00:28:19.200> very<00:28:19.440> similar<00:28:19.799> to<00:28:19.980> how<00:28:20.279> you<00:28:20.460> do<00:28:20.580> it<00:28:20.700> in 00:28:20.810 --> 00:28:20.820 align:start position:0% like very similar to how you do it in 00:28:20.820 --> 00:28:22.130 align:start position:0% like very similar to how you do it in Python 00:28:22.130 --> 00:28:22.140 align:start position:0% Python 00:28:22.140 --> 00:28:24.950 align:start position:0% Python how<00:28:22.559> do<00:28:22.740> you<00:28:22.799> define<00:28:22.919> that<00:28:23.700> this<00:28:24.059> has<00:28:24.779> a 00:28:24.950 --> 00:28:24.960 align:start position:0% how do you define that this has a 00:28:24.960 --> 00:28:26.630 align:start position:0% how do you define that this has a particular<00:28:25.260> set<00:28:25.559> of<00:28:25.860> properties<00:28:26.279> this 00:28:26.630 --> 00:28:26.640 align:start position:0% particular set of properties this 00:28:26.640 --> 00:28:28.789 align:start position:0% particular set of properties this function<00:28:26.940> that<00:28:27.120> that<00:28:27.419> is<00:28:27.659> coming<00:28:27.840> in<00:28:28.559> this 00:28:28.789 --> 00:28:28.799 align:start position:0% function that that is coming in this 00:28:28.799 --> 00:28:31.190 align:start position:0% function that that is coming in this case<00:28:28.919> with<00:28:29.400> view<00:28:29.640> we<00:28:30.059> are<00:28:30.240> defining<00:28:30.600> get<00:28:30.900> our 00:28:31.190 --> 00:28:31.200 align:start position:0% case with view we are defining get our 00:28:31.200 --> 00:28:32.510 align:start position:0% case with view we are defining get our functions<00:28:31.500> functions<00:28:31.860> what<00:28:32.039> you<00:28:32.220> can<00:28:32.340> read 00:28:32.510 --> 00:28:32.520 align:start position:0% functions functions what you can read 00:28:32.520 --> 00:28:34.070 align:start position:0% functions functions what you can read from 00:28:34.070 --> 00:28:34.080 align:start position:0% from 00:28:34.080 --> 00:28:36.289 align:start position:0% from so<00:28:34.320> right<00:28:34.500> now<00:28:34.679> we're<00:28:34.799> creating<00:28:35.460> this<00:28:35.820> admin 00:28:36.289 --> 00:28:36.299 align:start position:0% so right now we're creating this admin 00:28:36.299 --> 00:28:38.450 align:start position:0% so right now we're creating this admin function<00:28:36.600> that<00:28:36.900> as<00:28:37.200> you<00:28:37.320> can<00:28:37.440> see<00:28:37.620> is<00:28:37.980> exactly 00:28:38.450 --> 00:28:38.460 align:start position:0% function that as you can see is exactly 00:28:38.460 --> 00:28:39.890 align:start position:0% function that as you can see is exactly the<00:28:38.640> same<00:28:38.820> format<00:28:39.179> as<00:28:39.360> it<00:28:39.480> comes<00:28:39.720> in<00:28:39.779> open 00:28:39.890 --> 00:28:39.900 align:start position:0% the same format as it comes in open 00:28:39.900 --> 00:28:44.029 align:start position:0% the same format as it comes in open sapling<00:28:40.440> for<00:28:40.679> example<00:28:40.860> in<00:28:41.039> erc20<00:28:41.760> or<00:28:42.120> erc721 00:28:44.029 --> 00:28:44.039 align:start position:0% sapling for example in erc20 or erc721 00:28:44.039 --> 00:28:46.430 align:start position:0% sapling for example in erc20 or erc721 simply<00:28:44.940> reading<00:28:45.720> who<00:28:45.840> the<00:28:46.020> owner<00:28:46.200> of<00:28:46.320> the 00:28:46.430 --> 00:28:46.440 align:start position:0% simply reading who the owner of the 00:28:46.440 --> 00:28:48.769 align:start position:0% simply reading who the owner of the contract<00:28:46.740> is<00:28:47.340> so<00:28:47.760> for<00:28:47.880> example<00:28:48.059> if<00:28:48.179> I<00:28:48.360> go<00:28:48.539> again 00:28:48.769 --> 00:28:48.779 align:start position:0% contract is so for example if I go again 00:28:48.779 --> 00:28:51.470 align:start position:0% contract is so for example if I go again back<00:28:49.380> to<00:28:49.559> the<00:28:49.740> contract<00:28:50.159> deploy<00:28:51.059> control<00:28:51.179> here 00:28:51.470 --> 00:28:51.480 align:start position:0% back to the contract deploy control here 00:28:51.480 --> 00:28:53.330 align:start position:0% back to the contract deploy control here I<00:28:51.840> can 00:28:53.330 --> 00:28:53.340 align:start position:0% I can 00:28:53.340 --> 00:28:54.470 align:start position:0% I can read 00:28:54.470 --> 00:28:54.480 align:start position:0% read 00:28:54.480 --> 00:28:56.570 align:start position:0% read who<00:28:54.840> the<00:28:55.020> admin<00:28:55.320> is<00:28:55.440> as<00:28:55.799> you<00:28:55.919> can<00:28:56.039> see<00:28:56.159> this<00:28:56.400> is 00:28:56.570 --> 00:28:56.580 align:start position:0% who the admin is as you can see this is 00:28:56.580 --> 00:28:58.490 align:start position:0% who the admin is as you can see this is a<00:28:56.700> field 00:28:58.490 --> 00:28:58.500 align:start position:0% a field 00:28:58.500 --> 00:29:01.430 align:start position:0% a field but<00:28:58.919> if<00:28:59.220> I<00:28:59.400> convert<00:28:59.760> it<00:28:59.880> to<00:29:00.000> hex<00:29:00.360> this<00:29:01.140> is<00:29:01.260> the 00:29:01.430 --> 00:29:01.440 align:start position:0% but if I convert it to hex this is the 00:29:01.440 --> 00:29:05.269 align:start position:0% but if I convert it to hex this is the owner<00:29:01.679> of<00:29:01.740> the<00:29:01.860> contract<00:29:02.159> that<00:29:02.520> is<00:29:02.640> myself 00:29:05.269 --> 00:29:05.279 align:start position:0% 00:29:05.279 --> 00:29:08.450 align:start position:0% is<00:29:05.760> this<00:29:05.940> same<00:29:06.240> direction<00:29:06.559> so<00:29:07.559> talking<00:29:08.279> about 00:29:08.450 --> 00:29:08.460 align:start position:0% is this same direction so talking about 00:29:08.460 --> 00:29:10.250 align:start position:0% is this same direction so talking about wallets<00:29:09.000> it's<00:29:09.360> a<00:29:09.539> good<00:29:09.659> opportunity<00:29:10.020> right 00:29:10.250 --> 00:29:10.260 align:start position:0% wallets it's a good opportunity right 00:29:10.260 --> 00:29:11.090 align:start position:0% wallets it's a good opportunity right now 00:29:11.090 --> 00:29:11.100 align:start position:0% now 00:29:11.100 --> 00:29:14.390 align:start position:0% now you<00:29:11.760> can<00:29:11.880> use<00:29:12.059> right<00:29:12.299> now<00:29:12.480> RDM<00:29:13.320> X<00:29:13.500> which<00:29:14.279> is 00:29:14.390 --> 00:29:14.400 align:start position:0% you can use right now RDM X which is 00:29:14.400 --> 00:29:15.289 align:start position:0% you can use right now RDM X which is this<00:29:14.580> one 00:29:15.289 --> 00:29:15.299 align:start position:0% this one 00:29:15.299 --> 00:29:19.190 align:start position:0% this one and<00:29:15.779> also<00:29:16.080> Bravos<00:29:16.559> that<00:29:17.340> is<00:29:17.520> this<00:29:18.000> other<00:29:18.179> one 00:29:19.190 --> 00:29:19.200 align:start position:0% and also Bravos that is this other one 00:29:19.200 --> 00:29:21.950 align:start position:0% and also Bravos that is this other one very<00:29:19.740> recommended<00:29:20.340> you<00:29:21.059> can<00:29:21.179> use<00:29:21.480> the 00:29:21.950 --> 00:29:21.960 align:start position:0% very recommended you can use the 00:29:21.960 --> 00:29:24.289 align:start position:0% very recommended you can use the Standard<00:29:22.559> faucets<00:29:23.039> you<00:29:23.580> can<00:29:23.640> simply<00:29:23.880> put<00:29:24.120> in 00:29:24.289 --> 00:29:24.299 align:start position:0% Standard faucets you can simply put in 00:29:24.299 --> 00:29:26.870 align:start position:0% Standard faucets you can simply put in Google<00:29:24.419> started<00:29:25.380> faucet<00:29:25.740> and<00:29:26.220> you<00:29:26.340> will<00:29:26.520> be 00:29:26.870 --> 00:29:26.880 align:start position:0% Google started faucet and you will be 00:29:26.880 --> 00:29:29.690 align:start position:0% Google started faucet and you will be able<00:29:27.059> to<00:29:27.240> send<00:29:27.480> yourself<00:29:27.779> some<00:29:28.740> fake<00:29:29.159> it<00:29:29.340> so 00:29:29.690 --> 00:29:29.700 align:start position:0% able to send yourself some fake it so 00:29:29.700 --> 00:29:31.070 align:start position:0% able to send yourself some fake it so you<00:29:29.880> can<00:29:29.940> start<00:29:30.179> making<00:29:30.360> some<00:29:30.720> interesting 00:29:31.070 --> 00:29:31.080 align:start position:0% you can start making some interesting 00:29:31.080 --> 00:29:33.889 align:start position:0% you can start making some interesting things<00:29:31.260> using<00:29:31.620> girly<00:29:32.460> or<00:29:33.179> more<00:29:33.360> interestingly 00:29:33.889 --> 00:29:33.899 align:start position:0% things using girly or more interestingly 00:29:33.899 --> 00:29:38.090 align:start position:0% things using girly or more interestingly you<00:29:34.260> can<00:29:34.380> also<00:29:34.799> Bridge<00:29:35.279> your<00:29:36.179> own<00:29:36.480> it<00:29:37.200> from<00:29:37.980> the 00:29:38.090 --> 00:29:38.100 align:start position:0% you can also Bridge your own it from the 00:29:38.100 --> 00:29:40.909 align:start position:0% you can also Bridge your own it from the girl<00:29:38.279> testnet<00:29:39.000> in<00:29:39.299> in<00:29:39.539> the<00:29:39.779> layer<00:29:40.080> one<00:29:40.200> into 00:29:40.909 --> 00:29:40.919 align:start position:0% girl testnet in in the layer one into 00:29:40.919 --> 00:29:42.649 align:start position:0% girl testnet in in the layer one into the<00:29:41.159> layer<00:29:41.399> to<00:29:41.580> start<00:29:41.940> it<00:29:42.120> for<00:29:42.299> example<00:29:42.480> here 00:29:42.649 --> 00:29:42.659 align:start position:0% the layer to start it for example here 00:29:42.659 --> 00:29:46.490 align:start position:0% the layer to start it for example here we're<00:29:42.840> using<00:29:43.080> program<00:29:43.460> I<00:29:44.460> can<00:29:44.899> I<00:29:45.899> can<00:29:46.140> ask<00:29:46.260> for 00:29:46.490 --> 00:29:46.500 align:start position:0% we're using program I can I can ask for 00:29:46.500 --> 00:29:49.070 align:start position:0% we're using program I can I can ask for some<00:29:46.740> fake<00:29:47.039> it<00:29:47.340> send<00:29:47.760> it<00:29:47.940> to<00:29:48.059> my<00:29:48.179> metamask<00:29:48.659> for 00:29:49.070 --> 00:29:49.080 align:start position:0% some fake it send it to my metamask for 00:29:49.080 --> 00:29:50.810 align:start position:0% some fake it send it to my metamask for example 00:29:50.810 --> 00:29:50.820 align:start position:0% example 00:29:50.820 --> 00:29:53.090 align:start position:0% example and<00:29:51.419> then<00:29:51.539> using<00:29:51.899> the<00:29:52.080> bridge<00:29:52.200> I<00:29:52.799> can<00:29:52.919> connect 00:29:53.090 --> 00:29:53.100 align:start position:0% and then using the bridge I can connect 00:29:53.100 --> 00:29:56.029 align:start position:0% and then using the bridge I can connect my<00:29:53.580> meta<00:29:54.000> mask<00:29:54.120> which<00:29:54.720> is<00:29:54.899> currently<00:29:55.440> my<00:29:55.620> my 00:29:56.029 --> 00:29:56.039 align:start position:0% my meta mask which is currently my my 00:29:56.039 --> 00:29:58.250 align:start position:0% my meta mask which is currently my my wallet<00:29:56.460> in<00:29:56.640> layer<00:29:56.880> one<00:29:57.000> and<00:29:57.720> connect<00:29:57.899> for 00:29:58.250 --> 00:29:58.260 align:start position:0% wallet in layer one and connect for 00:29:58.260 --> 00:30:00.529 align:start position:0% wallet in layer one and connect for example<00:29:58.440> RDX<00:29:59.039> here<00:29:59.340> as<00:29:59.640> my<00:29:59.820> wallet<00:30:00.120> layer<00:30:00.419> 2 00:30:00.529 --> 00:30:00.539 align:start position:0% example RDX here as my wallet layer 2 00:30:00.539 --> 00:30:03.710 align:start position:0% example RDX here as my wallet layer 2 and<00:30:00.960> I<00:30:01.080> can<00:30:01.200> reach<00:30:01.620> these<00:30:02.399> fake<00:30:02.700> it<00:30:02.880> from<00:30:03.299> girly 00:30:03.710 --> 00:30:03.720 align:start position:0% and I can reach these fake it from girly 00:30:03.720 --> 00:30:06.649 align:start position:0% and I can reach these fake it from girly layer<00:30:04.080> 1<00:30:04.200> to<00:30:04.679> layer<00:30:05.340> 2.<00:30:05.700> so<00:30:06.120> this<00:30:06.240> is<00:30:06.360> also<00:30:06.600> very 00:30:06.649 --> 00:30:06.659 align:start position:0% layer 1 to layer 2. so this is also very 00:30:06.659 --> 00:30:08.389 align:start position:0% layer 1 to layer 2. so this is also very interesting<00:30:07.080> it's<00:30:07.559> the<00:30:07.740> same<00:30:07.919> thing<00:30:08.100> as 00:30:08.389 --> 00:30:08.399 align:start position:0% interesting it's the same thing as 00:30:08.399 --> 00:30:12.350 align:start position:0% interesting it's the same thing as asking<00:30:08.880> for<00:30:09.480> it<00:30:09.779> in<00:30:09.960> the<00:30:10.140> faucets 00:30:12.350 --> 00:30:12.360 align:start position:0% asking for it in the faucets 00:30:12.360 --> 00:30:18.250 align:start position:0% asking for it in the faucets so<00:30:12.899> going<00:30:13.320> back<00:30:13.500> to<00:30:13.620> the<00:30:13.799> contracts 00:30:18.250 --> 00:30:18.260 align:start position:0% 00:30:18.260 --> 00:30:21.049 align:start position:0% we<00:30:19.260> have<00:30:19.320> another<00:30:19.500> gear<00:30:19.860> function<00:30:20.220> here<00:30:20.520> it's 00:30:21.049 --> 00:30:21.059 align:start position:0% we have another gear function here it's 00:30:21.059 --> 00:30:23.269 align:start position:0% we have another gear function here it's also<00:30:21.360> a<00:30:21.539> very<00:30:21.720> typical<00:30:22.020> open<00:30:22.320> setting<00:30:22.860> style 00:30:23.269 --> 00:30:23.279 align:start position:0% also a very typical open setting style 00:30:23.279 --> 00:30:25.789 align:start position:0% also a very typical open setting style function<00:30:24.240> where<00:30:24.539> you<00:30:24.779> what<00:30:25.080> we<00:30:25.260> are<00:30:25.380> posting 00:30:25.789 --> 00:30:25.799 align:start position:0% function where you what we are posting 00:30:25.799 --> 00:30:28.909 align:start position:0% function where you what we are posting we're<00:30:26.580> asking<00:30:27.059> when<00:30:27.779> we<00:30:27.960> think<00:30:28.140> if<00:30:28.500> this 00:30:28.909 --> 00:30:28.919 align:start position:0% we're asking when we think if this 00:30:28.919 --> 00:30:31.070 align:start position:0% we're asking when we think if this contract<00:30:29.399> is<00:30:29.700> currently<00:30:30.000> post 00:30:31.070 --> 00:30:31.080 align:start position:0% contract is currently post 00:30:31.080 --> 00:30:32.570 align:start position:0% contract is currently post very<00:30:31.679> simple 00:30:32.570 --> 00:30:32.580 align:start position:0% very simple 00:30:32.580 --> 00:30:35.389 align:start position:0% very simple and<00:30:33.299> then<00:30:33.419> more<00:30:33.840> interestingly<00:30:34.440> here<00:30:35.159> we<00:30:35.340> have 00:30:35.389 --> 00:30:35.399 align:start position:0% and then more interestingly here we have 00:30:35.399 --> 00:30:36.889 align:start position:0% and then more interestingly here we have a<00:30:35.520> view<00:30:35.640> function<00:30:36.000> to<00:30:36.179> know<00:30:36.360> the<00:30:36.600> boring 00:30:36.889 --> 00:30:36.899 align:start position:0% a view function to know the boring 00:30:36.899 --> 00:30:38.149 align:start position:0% a view function to know the boring status<00:30:37.200> is<00:30:37.500> the<00:30:37.620> one<00:30:37.679> that<00:30:37.799> I<00:30:37.919> showed<00:30:38.100> you 00:30:38.149 --> 00:30:38.159 align:start position:0% status is the one that I showed you 00:30:38.159 --> 00:30:39.889 align:start position:0% status is the one that I showed you before<00:30:38.340> it<00:30:38.700> will<00:30:38.880> let<00:30:39.059> us<00:30:39.179> know<00:30:39.360> how<00:30:39.779> many 00:30:39.889 --> 00:30:39.899 align:start position:0% before it will let us know how many 00:30:39.899 --> 00:30:41.510 align:start position:0% before it will let us know how many people<00:30:40.080> voted<00:30:40.559> this<00:30:40.740> how<00:30:40.980> many<00:30:41.159> people<00:30:41.220> bought 00:30:41.510 --> 00:30:41.520 align:start position:0% people voted this how many people bought 00:30:41.520 --> 00:30:42.409 align:start position:0% people voted this how many people bought it<00:30:41.700> now 00:30:42.409 --> 00:30:42.419 align:start position:0% it now 00:30:42.419 --> 00:30:44.510 align:start position:0% it now as<00:30:42.659> simple<00:30:42.840> as<00:30:43.140> that<00:30:43.260> again<00:30:43.919> you<00:30:44.159> can<00:30:44.279> see<00:30:44.399> in 00:30:44.510 --> 00:30:44.520 align:start position:0% as simple as that again you can see in 00:30:44.520 --> 00:30:46.610 align:start position:0% as simple as that again you can see in this<00:30:44.640> function<00:30:44.940> that<00:30:45.299> we<00:30:46.020> have<00:30:46.200> an<00:30:46.260> explicit 00:30:46.610 --> 00:30:46.620 align:start position:0% this function that we have an explicit 00:30:46.620 --> 00:30:48.470 align:start position:0% this function that we have an explicit argument<00:30:46.980> and<00:30:47.399> by<00:30:47.640> now<00:30:47.820> you<00:30:48.120> are<00:30:48.299> already 00:30:48.470 --> 00:30:48.480 align:start position:0% argument and by now you are already 00:30:48.480 --> 00:30:51.350 align:start position:0% argument and by now you are already asking<00:30:48.840> yourself<00:30:49.020> what<00:30:49.500> is<00:30:49.679> this 00:30:51.350 --> 00:30:51.360 align:start position:0% asking yourself what is this 00:30:51.360 --> 00:30:54.710 align:start position:0% asking yourself what is this what<00:30:51.720> is<00:30:51.960> this<00:30:52.080> inside<00:30:52.380> these<00:30:52.860> keys 00:30:54.710 --> 00:30:54.720 align:start position:0% what is this inside these keys 00:30:54.720 --> 00:30:57.190 align:start position:0% what is this inside these keys these<00:30:55.320> are<00:30:55.380> implicit<00:30:55.860> arguments 00:30:57.190 --> 00:30:57.200 align:start position:0% these are implicit arguments 00:30:57.200 --> 00:31:00.049 align:start position:0% these are implicit arguments this<00:30:58.200> is<00:30:58.559> something<00:30:58.980> that<00:30:59.279> is<00:30:59.399> different<00:30:59.640> from 00:31:00.049 --> 00:31:00.059 align:start position:0% this is something that is different from 00:31:00.059 --> 00:31:01.789 align:start position:0% this is something that is different from other<00:31:00.240> languages<00:31:00.600> you<00:31:01.080> might<00:31:01.200> not<00:31:01.380> seen<00:31:01.620> that 00:31:01.789 --> 00:31:01.799 align:start position:0% other languages you might not seen that 00:31:01.799 --> 00:31:05.389 align:start position:0% other languages you might not seen that before<00:31:02.100> but<00:31:03.059> basically<00:31:03.659> uh<00:31:04.620> these<00:31:05.279> repeat 00:31:05.389 --> 00:31:05.399 align:start position:0% before but basically uh these repeat 00:31:05.399 --> 00:31:07.010 align:start position:0% before but basically uh these repeat themselves<00:31:05.940> all<00:31:06.179> the<00:31:06.299> time 00:31:07.010 --> 00:31:07.020 align:start position:0% themselves all the time 00:31:07.020 --> 00:31:09.769 align:start position:0% themselves all the time Cisco<00:31:07.799> pointer<00:31:08.279> person<00:31:08.580> pointer<00:31:09.179> and<00:31:09.539> Rich 00:31:09.769 --> 00:31:09.779 align:start position:0% Cisco pointer person pointer and Rich 00:31:09.779 --> 00:31:12.169 align:start position:0% Cisco pointer person pointer and Rich check<00:31:10.260> Pointer<00:31:10.740> while<00:31:11.520> interacting<00:31:12.000> with<00:31:12.059> the 00:31:12.169 --> 00:31:12.179 align:start position:0% check Pointer while interacting with the 00:31:12.179 --> 00:31:14.450 align:start position:0% check Pointer while interacting with the memory<00:31:12.419> here<00:31:12.659> so<00:31:13.200> we<00:31:13.380> are<00:31:13.559> talking<00:31:13.679> that<00:31:14.039> these 00:31:14.450 --> 00:31:14.460 align:start position:0% memory here so we are talking that these 00:31:14.460 --> 00:31:17.330 align:start position:0% memory here so we are talking that these are<00:31:14.580> Pointers<00:31:15.000> actually<00:31:15.179> into<00:31:15.539> a<00:31:15.779> felt<00:31:16.559> and<00:31:17.159> to 00:31:17.330 --> 00:31:17.340 align:start position:0% are Pointers actually into a felt and to 00:31:17.340 --> 00:31:19.850 align:start position:0% are Pointers actually into a felt and to a<00:31:17.520> stroke<00:31:17.700> Circle<00:31:17.880> has<00:31:18.600> built<00:31:19.200> it<00:31:19.260> no<00:31:19.679> problem 00:31:19.850 --> 00:31:19.860 align:start position:0% a stroke Circle has built it no problem 00:31:19.860 --> 00:31:22.789 align:start position:0% a stroke Circle has built it no problem no<00:31:20.399> we<00:31:20.880> will<00:31:21.059> need<00:31:21.299> to<00:31:21.419> get<00:31:21.539> that<00:31:21.960> that<00:31:22.559> is 00:31:22.789 --> 00:31:22.799 align:start position:0% no we will need to get that that is 00:31:22.799 --> 00:31:24.049 align:start position:0% no we will need to get that that is something<00:31:22.919> that<00:31:23.100> we're<00:31:23.220> repeating<00:31:23.640> in<00:31:23.820> each 00:31:24.049 --> 00:31:24.059 align:start position:0% something that we're repeating in each 00:31:24.059 --> 00:31:25.070 align:start position:0% something that we're repeating in each function 00:31:25.070 --> 00:31:25.080 align:start position:0% function 00:31:25.080 --> 00:31:26.510 align:start position:0% function it<00:31:25.260> doesn't<00:31:25.500> matter 00:31:26.510 --> 00:31:26.520 align:start position:0% it doesn't matter 00:31:26.520 --> 00:31:30.289 align:start position:0% it doesn't matter the<00:31:27.000> real<00:31:27.200> use<00:31:28.200> is<00:31:28.620> here<00:31:29.220> so<00:31:29.580> we<00:31:29.700> ask<00:31:29.880> in<00:31:30.059> here 00:31:30.289 --> 00:31:30.299 align:start position:0% the real use is here so we ask in here 00:31:30.299 --> 00:31:32.570 align:start position:0% the real use is here so we ask in here for<00:31:30.659> an<00:31:30.960> explicit<00:31:31.620> argument<00:31:32.100> that<00:31:32.340> is<00:31:32.460> about 00:31:32.570 --> 00:31:32.580 align:start position:0% for an explicit argument that is about 00:31:32.580 --> 00:31:33.889 align:start position:0% for an explicit argument that is about Counting 00:31:33.889 --> 00:31:33.899 align:start position:0% Counting 00:31:33.899 --> 00:31:36.289 align:start position:0% Counting sorry<00:31:34.380> sorry<00:31:34.460> we're<00:31:35.460> asking<00:31:35.880> for<00:31:36.059> nothing 00:31:36.289 --> 00:31:36.299 align:start position:0% sorry sorry we're asking for nothing 00:31:36.299 --> 00:31:39.710 align:start position:0% sorry sorry we're asking for nothing here<00:31:36.659> it's<00:31:37.559> empty<00:31:38.039> the<00:31:38.520> inputs<00:31:39.059> and<00:31:39.539> the 00:31:39.710 --> 00:31:39.720 align:start position:0% here it's empty the inputs and the 00:31:39.720 --> 00:31:42.470 align:start position:0% here it's empty the inputs and the output<00:31:40.020> is<00:31:40.559> this<00:31:40.919> a<00:31:41.700> status<00:31:41.940> a<00:31:42.299> variable 00:31:42.470 --> 00:31:42.480 align:start position:0% output is this a status a variable 00:31:42.480 --> 00:31:44.210 align:start position:0% output is this a status a variable called<00:31:42.720> status<00:31:43.020> that<00:31:43.440> is<00:31:43.559> about<00:31:43.740> counting 00:31:44.210 --> 00:31:44.220 align:start position:0% called status that is about counting 00:31:44.220 --> 00:31:46.070 align:start position:0% called status that is about counting structure<00:31:44.640> that<00:31:44.820> we<00:31:44.940> saw<00:31:45.120> before<00:31:45.360> again 00:31:46.070 --> 00:31:46.080 align:start position:0% structure that we saw before again 00:31:46.080 --> 00:31:48.830 align:start position:0% structure that we saw before again Kairus<00:31:46.919> type<00:31:47.159> is<00:31:47.460> a<00:31:47.640> type<00:31:47.760> language<00:31:48.000> this 00:31:48.830 --> 00:31:48.840 align:start position:0% Kairus type is a type language this 00:31:48.840 --> 00:31:50.750 align:start position:0% Kairus type is a type language this helps<00:31:49.140> for<00:31:49.260> security 00:31:50.750 --> 00:31:50.760 align:start position:0% helps for security 00:31:50.760 --> 00:31:52.610 align:start position:0% helps for security any<00:31:51.299> question<00:31:51.539> until<00:31:51.779> now<00:31:52.080> for<00:31:52.260> this<00:31:52.380> function 00:31:52.610 --> 00:31:52.620 align:start position:0% any question until now for this function 00:31:52.620 --> 00:31:56.450 align:start position:0% any question until now for this function for<00:31:52.799> example<00:31:53.100> yes 00:31:56.450 --> 00:31:56.460 align:start position:0% 00:31:56.460 --> 00:31:57.649 align:start position:0% yes 00:31:57.649 --> 00:31:57.659 align:start position:0% yes 00:31:57.659 --> 00:31:59.510 align:start position:0% yes this<00:31:58.080> is 00:31:59.510 --> 00:31:59.520 align:start position:0% this is 00:31:59.520 --> 00:32:01.310 align:start position:0% this is again<00:31:59.880> you<00:32:00.240> can<00:32:00.360> read<00:32:00.480> it 00:32:01.310 --> 00:32:01.320 align:start position:0% again you can read it 00:32:01.320 --> 00:32:03.470 align:start position:0% again you can read it you<00:32:01.679> can<00:32:01.860> read<00:32:02.039> from<00:32:02.399> the<00:32:02.640> gates<00:32:02.940> boring 00:32:03.470 --> 00:32:03.480 align:start position:0% you can read from the gates boring 00:32:03.480 --> 00:32:05.149 align:start position:0% you can read from the gates boring status<00:32:03.779> this<00:32:04.260> is<00:32:04.320> the<00:32:04.440> one<00:32:04.620> that<00:32:04.799> I<00:32:04.980> was 00:32:05.149 --> 00:32:05.159 align:start position:0% status this is the one that I was 00:32:05.159 --> 00:32:06.230 align:start position:0% status this is the one that I was showing<00:32:05.399> before 00:32:06.230 --> 00:32:06.240 align:start position:0% showing before 00:32:06.240 --> 00:32:08.210 align:start position:0% showing before and<00:32:06.600> currently<00:32:06.960> the<00:32:07.140> votes<00:32:07.380> are<00:32:07.500> yes<00:32:07.799> or<00:32:08.039> no 00:32:08.210 --> 00:32:08.220 align:start position:0% and currently the votes are yes or no 00:32:08.220 --> 00:32:10.669 align:start position:0% and currently the votes are yes or no this<00:32:08.760> is<00:32:09.000> practically<00:32:09.360> in<00:32:09.600> the<00:32:09.720> structure<00:32:10.140> we 00:32:10.669 --> 00:32:10.679 align:start position:0% this is practically in the structure we 00:32:10.679 --> 00:32:13.549 align:start position:0% this is practically in the structure we have<00:32:10.919> and<00:32:11.399> Define<00:32:11.580> here 00:32:13.549 --> 00:32:13.559 align:start position:0% have and Define here 00:32:13.559 --> 00:32:16.130 align:start position:0% have and Define here this<00:32:13.980> one<00:32:14.100> both<00:32:14.340> yes<00:32:14.640> both<00:32:15.120> know 00:32:16.130 --> 00:32:16.140 align:start position:0% this one both yes both know 00:32:16.140 --> 00:32:18.950 align:start position:0% this one both yes both know it's<00:32:16.380> exactly<00:32:16.919> the<00:32:17.100> same<00:32:17.279> here 00:32:18.950 --> 00:32:18.960 align:start position:0% it's exactly the same here 00:32:18.960 --> 00:32:22.010 align:start position:0% it's exactly the same here Okay<00:32:19.200> so 00:32:22.010 --> 00:32:22.020 align:start position:0% Okay so 00:32:22.020 --> 00:32:25.010 align:start position:0% Okay so foreign 00:32:25.010 --> 00:32:25.020 align:start position:0% foreign 00:32:25.020 --> 00:32:32.340 align:start position:0% foreign [Music] 00:32:32.340 --> 00:32:32.350 align:start position:0% 00:32:32.350 --> 00:32:50.890 align:start position:0% [Music] 00:32:50.890 --> 00:32:50.900 align:start position:0% 00:32:50.900 --> 00:33:05.110 align:start position:0% [Music] 00:33:05.110 --> 00:33:05.120 align:start position:0% 00:33:05.120 --> 00:33:07.730 align:start position:0% explicitly<00:33:06.120> telling<00:33:06.720> these<00:33:07.080> functions<00:33:07.500> that 00:33:07.730 --> 00:33:07.740 align:start position:0% explicitly telling these functions that 00:33:07.740 --> 00:33:09.049 align:start position:0% explicitly telling these functions that you<00:33:07.919> have<00:33:08.039> passed<00:33:08.399> them 00:33:09.049 --> 00:33:09.059 align:start position:0% you have passed them 00:33:09.059 --> 00:33:11.210 align:start position:0% you have passed them so<00:33:09.720> they<00:33:09.960> for<00:33:10.200> example<00:33:10.380> when<00:33:10.620> we<00:33:10.799> are<00:33:10.919> reading 00:33:11.210 --> 00:33:11.220 align:start position:0% so they for example when we are reading 00:33:11.220 --> 00:33:13.130 align:start position:0% so they for example when we are reading from<00:33:11.520> the<00:33:11.700> from<00:33:12.059> the<00:33:12.240> storage<00:33:12.360> you<00:33:12.840> have<00:33:13.019> to 00:33:13.130 --> 00:33:13.140 align:start position:0% from the from the storage you have to 00:33:13.140 --> 00:33:15.830 align:start position:0% from the from the storage you have to provide<00:33:13.500> these<00:33:14.340> functions<00:33:14.700> that<00:33:15.059> the<00:33:15.600> sorry 00:33:15.830 --> 00:33:15.840 align:start position:0% provide these functions that the sorry 00:33:15.840 --> 00:33:18.049 align:start position:0% provide these functions that the sorry the<00:33:16.500> pencil<00:33:16.860> pointer<00:33:17.159> and<00:33:17.340> the<00:33:17.399> Cisco<00:33:17.700> pointer 00:33:18.049 --> 00:33:18.059 align:start position:0% the pencil pointer and the Cisco pointer 00:33:18.059 --> 00:33:20.210 align:start position:0% the pencil pointer and the Cisco pointer you<00:33:18.600> have<00:33:18.779> to<00:33:18.899> provide<00:33:19.200> them<00:33:19.320> and<00:33:19.860> they<00:33:20.039> go 00:33:20.210 --> 00:33:20.220 align:start position:0% you have to provide them and they go 00:33:20.220 --> 00:33:22.669 align:start position:0% you have to provide them and they go into<00:33:20.460> the<00:33:20.640> read<00:33:20.820> function<00:33:21.299> so<00:33:21.600> inside<00:33:22.260> here 00:33:22.669 --> 00:33:22.679 align:start position:0% into the read function so inside here 00:33:22.679 --> 00:33:25.009 align:start position:0% into the read function so inside here our<00:33:23.340> implicit<00:33:23.760> function<00:33:24.000> implicit<00:33:24.539> arguments 00:33:25.009 --> 00:33:25.019 align:start position:0% our implicit function implicit arguments 00:33:25.019 --> 00:33:26.870 align:start position:0% our implicit function implicit arguments you<00:33:25.559> don't<00:33:25.740> see<00:33:25.919> it<00:33:26.100> because<00:33:26.460> they<00:33:26.760> are 00:33:26.870 --> 00:33:26.880 align:start position:0% you don't see it because they are 00:33:26.880 --> 00:33:32.870 align:start position:0% you don't see it because they are implicit<00:33:27.299> but 00:33:32.870 --> 00:33:32.880 align:start position:0% 00:33:32.880 --> 00:33:34.549 align:start position:0% yes 00:33:34.549 --> 00:33:34.559 align:start position:0% yes 00:33:34.559 --> 00:33:36.830 align:start position:0% yes exactly<00:33:35.220> this<00:33:35.700> input<00:33:36.000> functions<00:33:36.419> if<00:33:36.480> I<00:33:36.659> take 00:33:36.830 --> 00:33:36.840 align:start position:0% exactly this input functions if I take 00:33:36.840 --> 00:33:39.169 align:start position:0% exactly this input functions if I take them<00:33:37.019> off<00:33:37.140> they<00:33:37.620> will<00:33:37.860> have<00:33:38.039> an<00:33:38.220> error 00:33:39.169 --> 00:33:39.179 align:start position:0% them off they will have an error 00:33:39.179 --> 00:33:40.490 align:start position:0% them off they will have an error no<00:33:39.659> problem 00:33:40.490 --> 00:33:40.500 align:start position:0% no problem 00:33:40.500 --> 00:33:43.970 align:start position:0% no problem it's<00:33:41.159> it's<00:33:41.159> not<00:33:41.460> hard<00:33:41.700> to<00:33:41.940> to<00:33:42.899> to<00:33:42.899> get<00:33:43.620> used<00:33:43.799> to 00:33:43.970 --> 00:33:43.980 align:start position:0% it's it's not hard to to to get used to 00:33:43.980 --> 00:33:46.009 align:start position:0% it's it's not hard to to to get used to them<00:33:44.159> and<00:33:44.700> also<00:33:44.940> you<00:33:45.120> can<00:33:45.299> see<00:33:45.419> each<00:33:45.720> function 00:33:46.009 --> 00:33:46.019 align:start position:0% them and also you can see each function 00:33:46.019 --> 00:33:48.889 align:start position:0% them and also you can see each function that<00:33:46.200> I<00:33:46.380> adding<00:33:46.740> here<00:33:46.919> has<00:33:47.279> them<00:33:47.580> repeated<00:33:48.299> so 00:33:48.889 --> 00:33:48.899 align:start position:0% that I adding here has them repeated so 00:33:48.899 --> 00:33:51.769 align:start position:0% that I adding here has them repeated so no<00:33:49.559> problem<00:33:49.679> with<00:33:49.980> that 00:33:51.769 --> 00:33:51.779 align:start position:0% no problem with that 00:33:51.779 --> 00:33:53.029 align:start position:0% no problem with that okay 00:33:53.029 --> 00:33:53.039 align:start position:0% okay 00:33:53.039 --> 00:33:54.830 align:start position:0% okay also<00:33:53.519> we<00:33:53.640> have<00:33:53.760> an<00:33:53.820> overview<00:33:54.120> function<00:33:54.539> where 00:33:54.830 --> 00:33:54.840 align:start position:0% also we have an overview function where 00:33:54.840 --> 00:33:59.690 align:start position:0% also we have an overview function where we<00:33:54.960> are<00:33:55.080> getting<00:33:55.200> the<00:33:55.440> status<00:33:56.039> of<00:33:56.279> a<00:33:56.460> motor<00:33:56.580> and 00:33:59.690 --> 00:33:59.700 align:start position:0% 00:33:59.700 --> 00:34:01.970 align:start position:0% just<00:34:00.120> if<00:34:00.419> you<00:34:00.659> were<00:34:00.779> simply<00:34:01.019> reading<00:34:01.440> into<00:34:01.740> the 00:34:01.970 --> 00:34:01.980 align:start position:0% just if you were simply reading into the 00:34:01.980 --> 00:34:03.350 align:start position:0% just if you were simply reading into the voter<00:34:02.340> info 00:34:03.350 --> 00:34:03.360 align:start position:0% voter info 00:34:03.360 --> 00:34:05.029 align:start position:0% voter info a<00:34:03.419> storage<00:34:03.720> variable<00:34:04.260> that<00:34:04.620> we<00:34:04.679> have<00:34:04.860> before 00:34:05.029 --> 00:34:05.039 align:start position:0% a storage variable that we have before 00:34:05.039 --> 00:34:07.909 align:start position:0% a storage variable that we have before using<00:34:05.940> the<00:34:06.000> argument<00:34:06.299> reads<00:34:06.779> so<00:34:07.380> now<00:34:07.679> going 00:34:07.909 --> 00:34:07.919 align:start position:0% using the argument reads so now going 00:34:07.919 --> 00:34:09.829 align:start position:0% using the argument reads so now going deeper<00:34:08.280> into<00:34:08.399> this<00:34:08.639> we<00:34:09.179> can<00:34:09.300> read<00:34:09.480> and<00:34:09.659> write 00:34:09.829 --> 00:34:09.839 align:start position:0% deeper into this we can read and write 00:34:09.839 --> 00:34:11.930 align:start position:0% deeper into this we can read and write from<00:34:10.379> this<00:34:10.500> storage<00:34:10.740> function 00:34:11.930 --> 00:34:11.940 align:start position:0% from this storage function 00:34:11.940 --> 00:34:14.329 align:start position:0% from this storage function in<00:34:12.419> this<00:34:12.540> case<00:34:12.659> we<00:34:12.899> are<00:34:13.020> reading 00:34:14.329 --> 00:34:14.339 align:start position:0% in this case we are reading 00:34:14.339 --> 00:34:17.329 align:start position:0% in this case we are reading and<00:34:15.000> as<00:34:15.300> you<00:34:15.419> remember<00:34:15.679> this<00:34:16.679> search<00:34:16.919> function 00:34:17.329 --> 00:34:17.339 align:start position:0% and as you remember this search function 00:34:17.339 --> 00:34:19.490 align:start position:0% and as you remember this search function asks<00:34:18.000> us<00:34:18.060> why<00:34:18.419> do<00:34:18.659> you<00:34:18.720> surround<00:34:19.020> device<00:34:19.139> and 00:34:19.490 --> 00:34:19.500 align:start position:0% asks us why do you surround device and 00:34:19.500 --> 00:34:21.649 align:start position:0% asks us why do you surround device and it<00:34:19.619> was<00:34:19.740> precisely<00:34:20.099> a<00:34:20.280> failed<00:34:21.000> so<00:34:21.419> if<00:34:21.540> we 00:34:21.649 --> 00:34:21.659 align:start position:0% it was precisely a failed so if we 00:34:21.659 --> 00:34:23.990 align:start position:0% it was precisely a failed so if we provided<00:34:22.020> a<00:34:22.200> field<00:34:22.320> then<00:34:22.800> it<00:34:22.980> will<00:34:23.099> return<00:34:23.339> us 00:34:23.990 --> 00:34:24.000 align:start position:0% provided a field then it will return us 00:34:24.000 --> 00:34:30.290 align:start position:0% provided a field then it will return us let's<00:34:24.599> see<00:34:24.839> once<00:34:25.379> does<00:34:25.679> it<00:34:25.859> return 00:34:30.290 --> 00:34:30.300 align:start position:0% 00:34:30.300 --> 00:34:32.570 align:start position:0% yes<00:34:30.659> if<00:34:30.839> we<00:34:31.020> provide<00:34:31.260> an<00:34:31.500> RIS<00:34:31.859> it<00:34:32.280> will<00:34:32.399> return 00:34:32.570 --> 00:34:32.580 align:start position:0% yes if we provide an RIS it will return 00:34:32.580 --> 00:34:36.349 align:start position:0% yes if we provide an RIS it will return us<00:34:32.879> about<00:34:33.179> our<00:34:33.480> info<00:34:33.780> structure<00:34:34.320> okay 00:34:36.349 --> 00:34:36.359 align:start position:0% us about our info structure okay 00:34:36.359 --> 00:34:38.750 align:start position:0% us about our info structure okay so<00:34:36.780> here<00:34:36.960> I'm<00:34:37.139> reading<00:34:37.560> from<00:34:37.740> it 00:34:38.750 --> 00:34:38.760 align:start position:0% so here I'm reading from it 00:34:38.760 --> 00:34:41.089 align:start position:0% so here I'm reading from it and<00:34:39.240> then<00:34:39.300> we're<00:34:39.540> returning<00:34:40.080> it<00:34:40.200> simply<00:34:40.919> as 00:34:41.089 --> 00:34:41.099 align:start position:0% and then we're returning it simply as 00:34:41.099 --> 00:34:43.190 align:start position:0% and then we're returning it simply as that<00:34:41.399> status<00:34:41.879> equal<00:34:42.300> status<00:34:42.599> because<00:34:43.020> the 00:34:43.190 --> 00:34:43.200 align:start position:0% that status equal status because the 00:34:43.200 --> 00:34:48.010 align:start position:0% that status equal status because the name<00:34:43.320> of<00:34:43.440> the<00:34:43.560> variable<00:34:43.800> here<00:34:43.980> is<00:34:44.220> a<00:34:44.339> status 00:34:48.010 --> 00:34:48.020 align:start position:0% 00:34:48.020 --> 00:34:52.970 align:start position:0% and<00:34:49.020> to<00:34:49.560> see<00:34:49.740> an<00:34:49.919> example<00:34:50.220> of<00:34:50.820> how<00:34:51.060> to<00:34:51.179> write 00:34:52.970 --> 00:34:52.980 align:start position:0% and to see an example of how to write 00:34:52.980 --> 00:34:55.129 align:start position:0% and to see an example of how to write exactly<00:34:53.639> the<00:34:54.000> same 00:34:55.129 --> 00:34:55.139 align:start position:0% exactly the same 00:34:55.139 --> 00:34:56.750 align:start position:0% exactly the same the<00:34:55.619> same<00:34:55.679> storage<00:34:55.919> variable<00:34:56.280> that<00:34:56.460> we<00:34:56.580> saw 00:34:56.750 --> 00:34:56.760 align:start position:0% the same storage variable that we saw 00:34:56.760 --> 00:34:58.670 align:start position:0% the same storage variable that we saw before<00:34:56.879> motor<00:34:57.240> info<00:34:57.780> we<00:34:58.080> were<00:34:58.200> able<00:34:58.380> to<00:34:58.500> read 00:34:58.670 --> 00:34:58.680 align:start position:0% before motor info we were able to read 00:34:58.680 --> 00:35:01.010 align:start position:0% before motor info we were able to read from<00:34:58.980> it<00:34:59.160> if<00:35:00.000> we<00:35:00.119> are<00:35:00.240> imputing<00:35:00.720> with<00:35:00.900> the 00:35:01.010 --> 00:35:01.020 align:start position:0% from it if we are imputing with the 00:35:01.020 --> 00:35:02.150 align:start position:0% from it if we are imputing with the address 00:35:02.150 --> 00:35:02.160 align:start position:0% address 00:35:02.160 --> 00:35:04.970 align:start position:0% address and<00:35:02.580> we<00:35:02.700> know<00:35:02.880> we<00:35:03.300> now<00:35:03.480> know<00:35:03.780> that<00:35:04.080> it<00:35:04.320> returns 00:35:04.970 --> 00:35:04.980 align:start position:0% and we know we now know that it returns 00:35:04.980 --> 00:35:08.329 align:start position:0% and we know we now know that it returns an<00:35:05.400> instructs<00:35:05.940> okay<00:35:06.660> so<00:35:07.500> now<00:35:07.680> we<00:35:07.920> can<00:35:08.040> write 00:35:08.329 --> 00:35:08.339 align:start position:0% an instructs okay so now we can write 00:35:08.339 --> 00:35:10.550 align:start position:0% an instructs okay so now we can write using<00:35:09.180> the<00:35:09.300> argument<00:35:09.540> right<00:35:09.780> we<00:35:10.020> can<00:35:10.200> write<00:35:10.380> on 00:35:10.550 --> 00:35:10.560 align:start position:0% using the argument right we can write on 00:35:10.560 --> 00:35:11.270 align:start position:0% using the argument right we can write on it 00:35:11.270 --> 00:35:11.280 align:start position:0% it 00:35:11.280 --> 00:35:13.310 align:start position:0% it so<00:35:11.700> we're<00:35:11.820> writing<00:35:12.180> on<00:35:12.300> the<00:35:12.420> storage<00:35:12.599> of<00:35:13.079> our 00:35:13.310 --> 00:35:13.320 align:start position:0% so we're writing on the storage of our 00:35:13.320 --> 00:35:14.329 align:start position:0% so we're writing on the storage of our contract 00:35:14.329 --> 00:35:14.339 align:start position:0% contract 00:35:14.339 --> 00:35:17.329 align:start position:0% contract and<00:35:15.060> right<00:35:15.359> now<00:35:15.599> this<00:35:16.500> is<00:35:16.680> basically<00:35:17.040> an 00:35:17.329 --> 00:35:17.339 align:start position:0% and right now this is basically an 00:35:17.339 --> 00:35:19.250 align:start position:0% and right now this is basically an address<00:35:17.520> we<00:35:18.180> will<00:35:18.359> go<00:35:18.480> deeper<00:35:18.839> in<00:35:19.020> the<00:35:19.140> moon 00:35:19.250 --> 00:35:19.260 align:start position:0% address we will go deeper in the moon 00:35:19.260 --> 00:35:22.690 align:start position:0% address we will go deeper in the moon over<00:35:19.740> it<00:35:19.980> but<00:35:20.160> this<00:35:20.339> is<00:35:20.460> an<00:35:20.579> address 00:35:22.690 --> 00:35:22.700 align:start position:0% over it but this is an address 00:35:22.700 --> 00:35:26.870 align:start position:0% over it but this is an address for<00:35:23.700> this<00:35:23.940> address<00:35:24.060> please<00:35:25.020> map 00:35:26.870 --> 00:35:26.880 align:start position:0% for this address please map 00:35:26.880 --> 00:35:29.089 align:start position:0% for this address please map this<00:35:27.359> instruct<00:35:27.780> okay 00:35:29.089 --> 00:35:29.099 align:start position:0% this instruct okay 00:35:29.099 --> 00:35:31.310 align:start position:0% this instruct okay very<00:35:29.460> similar<00:35:29.820> to<00:35:30.000> how<00:35:30.420> you 00:35:31.310 --> 00:35:31.320 align:start position:0% very similar to how you 00:35:31.320 --> 00:35:33.650 align:start position:0% very similar to how you look<00:35:31.680> at<00:35:31.859> it<00:35:31.980> in<00:35:32.099> solid 00:35:33.650 --> 00:35:33.660 align:start position:0% look at it in solid 00:35:33.660 --> 00:35:38.349 align:start position:0% look at it in solid yes 00:35:38.349 --> 00:35:38.359 align:start position:0% 00:35:38.359 --> 00:35:41.690 align:start position:0% sender<00:35:39.359> is<00:35:39.780> a 00:35:41.690 --> 00:35:41.700 align:start position:0% sender is a 00:35:41.700 --> 00:35:45.109 align:start position:0% sender is a I<00:35:41.880> think<00:35:42.060> we<00:35:42.180> have<00:35:42.359> it<00:35:42.540> here<00:35:42.839> get<00:35:43.560> code<00:35:43.800> address 00:35:45.109 --> 00:35:45.119 align:start position:0% I think we have it here get code address 00:35:45.119 --> 00:35:46.970 align:start position:0% I think we have it here get code address with<00:35:45.480> this<00:35:45.660> you're<00:35:45.839> getting<00:35:46.079> the<00:35:46.380> address<00:35:46.619> of 00:35:46.970 --> 00:35:46.980 align:start position:0% with this you're getting the address of 00:35:46.980 --> 00:35:50.210 align:start position:0% with this you're getting the address of the<00:35:47.160> of<00:35:47.460> the<00:35:47.700> contract<00:35:48.119> that<00:35:48.359> is<00:35:48.480> calling<00:35:48.900> this 00:35:50.210 --> 00:35:50.220 align:start position:0% the of the contract that is calling this 00:35:50.220 --> 00:35:52.069 align:start position:0% the of the contract that is calling this this<00:35:50.640> contract<00:35:51.119> so<00:35:51.300> for<00:35:51.480> example<00:35:51.720> in<00:35:51.960> this 00:35:52.069 --> 00:35:52.079 align:start position:0% this contract so for example in this 00:35:52.079 --> 00:35:54.230 align:start position:0% this contract so for example in this case<00:35:52.339> this<00:35:53.339> is<00:35:53.460> the<00:35:53.520> most<00:35:53.640> important<00:35:53.940> function 00:35:54.230 --> 00:35:54.240 align:start position:0% case this is the most important function 00:35:54.240 --> 00:35:56.210 align:start position:0% case this is the most important function is<00:35:54.540> the<00:35:54.660> both<00:35:54.900> function 00:35:56.210 --> 00:35:56.220 align:start position:0% is the both function 00:35:56.220 --> 00:35:59.329 align:start position:0% is the both function so<00:35:56.820> what<00:35:57.180> it<00:35:57.599> does<00:35:57.839> is<00:35:58.200> simply<00:35:58.500> it's<00:35:59.040> getting 00:35:59.329 --> 00:35:59.339 align:start position:0% so what it does is simply it's getting 00:35:59.339 --> 00:36:01.130 align:start position:0% so what it does is simply it's getting the<00:35:59.640> address<00:35:59.760> of<00:36:00.119> the<00:36:00.300> color 00:36:01.130 --> 00:36:01.140 align:start position:0% the address of the color 00:36:01.140 --> 00:36:03.950 align:start position:0% the address of the color is<00:36:01.560> turn<00:36:01.859> it<00:36:02.160> and<00:36:03.119> then 00:36:03.950 --> 00:36:03.960 align:start position:0% is turn it and then 00:36:03.960 --> 00:36:05.810 align:start position:0% is turn it and then we'll<00:36:04.380> reviewing<00:36:04.980> the<00:36:05.040> information<00:36:05.160> of<00:36:05.640> this 00:36:05.810 --> 00:36:05.820 align:start position:0% we'll reviewing the information of this 00:36:05.820 --> 00:36:07.430 align:start position:0% we'll reviewing the information of this person<00:36:06.000> to<00:36:06.359> see<00:36:06.540> if<00:36:06.660> this<00:36:06.960> person<00:36:07.079> has<00:36:07.320> already 00:36:07.430 --> 00:36:07.440 align:start position:0% person to see if this person has already 00:36:07.440 --> 00:36:09.589 align:start position:0% person to see if this person has already bought<00:36:07.740> or<00:36:08.040> not<00:36:08.160> because<00:36:08.460> we<00:36:08.700> can<00:36:08.880> only<00:36:09.300> allow 00:36:09.589 --> 00:36:09.599 align:start position:0% bought or not because we can only allow 00:36:09.599 --> 00:36:11.810 align:start position:0% bought or not because we can only allow them<00:36:09.720> if<00:36:09.900> they<00:36:10.140> have<00:36:10.320> bought<00:36:10.680> it 00:36:11.810 --> 00:36:11.820 align:start position:0% them if they have bought it 00:36:11.820 --> 00:36:16.609 align:start position:0% them if they have bought it and<00:36:12.420> just<00:36:12.839> in<00:36:13.200> a<00:36:13.320> moment<00:36:13.440> we'll<00:36:13.680> go<00:36:13.859> into<00:36:14.040> that 00:36:16.609 --> 00:36:16.619 align:start position:0% 00:36:16.619 --> 00:36:24.010 align:start position:0% um 00:36:24.010 --> 00:36:24.020 align:start position:0% 00:36:24.020 --> 00:36:25.970 align:start position:0% could<00:36:25.020> you<00:36:25.200> repeat<00:36:25.260> the<00:36:25.440> question<00:36:25.619> a<00:36:25.920> little 00:36:25.970 --> 00:36:25.980 align:start position:0% could you repeat the question a little 00:36:25.980 --> 00:36:31.670 align:start position:0% could you repeat the question a little bit<00:36:26.160> louder<00:36:26.280> please 00:36:31.670 --> 00:36:31.680 align:start position:0% 00:36:31.680 --> 00:36:33.109 align:start position:0% value 00:36:33.109 --> 00:36:33.119 align:start position:0% value 00:36:33.119 --> 00:36:36.250 align:start position:0% value like<00:36:33.660> an<00:36:33.839> address<00:36:34.040> there's<00:36:35.040> no<00:36:35.280> notion<00:36:35.700> of 00:36:36.250 --> 00:36:36.260 align:start position:0% like an address there's no notion of 00:36:36.260 --> 00:36:39.650 align:start position:0% like an address there's no notion of msg.value<00:36:37.260> in<00:36:38.040> stock<00:36:38.460> net<00:36:38.700> because<00:36:39.119> there's 00:36:39.650 --> 00:36:39.660 align:start position:0% msg.value in stock net because there's 00:36:39.660 --> 00:36:41.990 align:start position:0% msg.value in stock net because there's no<00:36:40.079> native<00:36:40.440> currency<00:36:40.920> everything's<00:36:41.760> in<00:36:41.880> near 00:36:41.990 --> 00:36:42.000 align:start position:0% no native currency everything's in near 00:36:42.000 --> 00:36:44.450 align:start position:0% no native currency everything's in near C20<00:36:42.480> so<00:36:43.020> there's<00:36:43.200> no<00:36:43.440> value<00:36:43.680> attached<00:36:44.220> to<00:36:44.339> a 00:36:44.450 --> 00:36:44.460 align:start position:0% C20 so there's no value attached to a 00:36:44.460 --> 00:36:46.430 align:start position:0% C20 so there's no value attached to a call<00:36:44.640> there's<00:36:45.540> no 00:36:46.430 --> 00:36:46.440 align:start position:0% call there's no 00:36:46.440 --> 00:36:48.470 align:start position:0% call there's no um and<00:36:46.800> there's<00:36:46.920> no<00:36:47.099> payable<00:36:47.460> function 00:36:48.470 --> 00:36:48.480 align:start position:0% um and there's no payable function 00:36:48.480 --> 00:36:52.970 align:start position:0% um and there's no payable function that<00:36:48.780> answer<00:36:49.020> your<00:36:49.260> question 00:36:52.970 --> 00:36:52.980 align:start position:0% 00:36:52.980 --> 00:36:56.030 align:start position:0% Okay<00:36:53.339> so 00:36:56.030 --> 00:36:56.040 align:start position:0% 00:36:56.040 --> 00:36:57.020 align:start position:0% yes 00:36:57.020 --> 00:36:57.030 align:start position:0% yes 00:36:57.030 --> 00:36:57.230 align:start position:0% yes [Music] 00:36:57.230 --> 00:36:57.240 align:start position:0% [Music] 00:36:57.240 --> 00:36:58.190 align:start position:0% [Music] um 00:36:58.190 --> 00:36:58.200 align:start position:0% um 00:36:58.200 --> 00:37:00.290 align:start position:0% um so<00:36:58.619> let's<00:36:58.740> go<00:36:58.920> quickly<00:36:59.460> into<00:36:59.760> the<00:37:00.119> most 00:37:00.290 --> 00:37:00.300 align:start position:0% so let's go quickly into the most 00:37:00.300 --> 00:37:01.670 align:start position:0% so let's go quickly into the most important<00:37:00.660> function<00:37:01.140> the<00:37:01.380> two<00:37:01.500> most 00:37:01.670 --> 00:37:01.680 align:start position:0% important function the two most 00:37:01.680 --> 00:37:03.410 align:start position:0% important function the two most important<00:37:02.040> functions<00:37:02.339> the<00:37:02.579> register<00:37:02.880> voters 00:37:03.410 --> 00:37:03.420 align:start position:0% important functions the register voters 00:37:03.420 --> 00:37:05.450 align:start position:0% important functions the register voters and<00:37:03.900> this<00:37:04.020> will<00:37:04.200> help<00:37:04.380> me<00:37:04.560> to 00:37:05.450 --> 00:37:05.460 align:start position:0% and this will help me to 00:37:05.460 --> 00:37:07.490 align:start position:0% and this will help me to and<00:37:06.119> talk<00:37:06.480> a<00:37:06.720> little<00:37:06.960> bit<00:37:07.079> more<00:37:07.320> about 00:37:07.490 --> 00:37:07.500 align:start position:0% and talk a little bit more about 00:37:07.500 --> 00:37:10.550 align:start position:0% and talk a little bit more about recursion<00:37:08.339> that<00:37:08.760> we<00:37:08.940> use<00:37:09.119> in<00:37:09.300> Cairo 00:37:10.550 --> 00:37:10.560 align:start position:0% recursion that we use in Cairo 00:37:10.560 --> 00:37:12.290 align:start position:0% recursion that we use in Cairo so<00:37:10.980> again<00:37:11.099> as<00:37:11.280> you<00:37:11.460> can<00:37:11.520> see<00:37:11.640> we<00:37:11.880> have<00:37:12.060> the 00:37:12.290 --> 00:37:12.300 align:start position:0% so again as you can see we have the 00:37:12.300 --> 00:37:15.770 align:start position:0% so again as you can see we have the implicit<00:37:12.900> arguments<00:37:13.740> as<00:37:13.920> always<00:37:14.300> and<00:37:15.300> then<00:37:15.540> we 00:37:15.770 --> 00:37:15.780 align:start position:0% implicit arguments as always and then we 00:37:15.780 --> 00:37:18.050 align:start position:0% implicit arguments as always and then we are<00:37:15.960> asking<00:37:16.260> for<00:37:16.440> two<00:37:16.619> explicit<00:37:17.099> arguments 00:37:18.050 --> 00:37:18.060 align:start position:0% are asking for two explicit arguments 00:37:18.060 --> 00:37:20.510 align:start position:0% are asking for two explicit arguments the<00:37:18.480> register<00:37:18.720> address<00:37:19.079> Lane<00:37:19.440> this<00:37:20.160> this<00:37:20.339> is 00:37:20.510 --> 00:37:20.520 align:start position:0% the register address Lane this this is 00:37:20.520 --> 00:37:22.970 align:start position:0% the register address Lane this this is the<00:37:20.700> the<00:37:20.880> length<00:37:21.599> of<00:37:21.720> an<00:37:21.900> array 00:37:22.970 --> 00:37:22.980 align:start position:0% the the length of an array 00:37:22.980 --> 00:37:26.270 align:start position:0% the the length of an array and<00:37:23.400> the<00:37:23.579> second<00:37:23.760> value<00:37:24.300> is<00:37:24.900> the<00:37:25.320> array<00:37:25.680> itself 00:37:26.270 --> 00:37:26.280 align:start position:0% and the second value is the array itself 00:37:26.280 --> 00:37:28.670 align:start position:0% and the second value is the array itself so<00:37:26.940> first<00:37:27.359> argument<00:37:27.780> is<00:37:27.960> the<00:37:28.140> length<00:37:28.380> of<00:37:28.440> the 00:37:28.670 --> 00:37:28.680 align:start position:0% so first argument is the length of the 00:37:28.680 --> 00:37:30.230 align:start position:0% so first argument is the length of the length<00:37:28.920> of<00:37:29.040> this<00:37:29.160> array<00:37:29.520> the<00:37:29.700> second<00:37:29.820> argument 00:37:30.230 --> 00:37:30.240 align:start position:0% length of this array the second argument 00:37:30.240 --> 00:37:33.349 align:start position:0% length of this array the second argument is<00:37:30.660> the<00:37:30.900> the<00:37:31.260> array<00:37:31.619> by<00:37:31.800> itself 00:37:33.349 --> 00:37:33.359 align:start position:0% is the the array by itself 00:37:33.359 --> 00:37:35.990 align:start position:0% is the the array by itself then<00:37:34.020> what<00:37:34.320> we're<00:37:34.440> doing<00:37:34.680> here<00:37:34.980> is 00:37:35.990 --> 00:37:36.000 align:start position:0% then what we're doing here is 00:37:36.000 --> 00:37:37.910 align:start position:0% then what we're doing here is and<00:37:36.540> again<00:37:36.780> you<00:37:37.079> can<00:37:37.260> see<00:37:37.380> all<00:37:37.680> these 00:37:37.910 --> 00:37:37.920 align:start position:0% and again you can see all these 00:37:37.920 --> 00:37:39.650 align:start position:0% and again you can see all these contracts<00:37:38.400> in<00:37:38.700> the<00:37:38.820> report<00:37:39.060> I<00:37:39.359> showed<00:37:39.599> you 00:37:39.650 --> 00:37:39.660 align:start position:0% contracts in the report I showed you 00:37:39.660 --> 00:37:41.930 align:start position:0% contracts in the report I showed you before<00:37:39.780> isn't<00:37:40.440> started<00:37:40.800> with<00:37:40.980> you 00:37:41.930 --> 00:37:41.940 align:start position:0% before isn't started with you 00:37:41.940 --> 00:37:44.270 align:start position:0% before isn't started with you in<00:37:42.480> case<00:37:42.599> you<00:37:42.900> are 00:37:44.270 --> 00:37:44.280 align:start position:0% in case you are 00:37:44.280 --> 00:37:46.010 align:start position:0% in case you are you<00:37:44.700> want<00:37:44.820> to<00:37:44.940> follow<00:37:45.060> it<00:37:45.300> closer<00:37:45.720> in<00:37:45.839> your 00:37:46.010 --> 00:37:46.020 align:start position:0% you want to follow it closer in your 00:37:46.020 --> 00:37:48.470 align:start position:0% you want to follow it closer in your houses<00:37:46.200> and 00:37:48.470 --> 00:37:48.480 align:start position:0% houses and 00:37:48.480 --> 00:37:50.270 align:start position:0% houses and then<00:37:48.900> what<00:37:49.079> we're<00:37:49.200> doing<00:37:49.380> here<00:37:49.619> is<00:37:49.859> simply<00:37:50.160> and 00:37:50.270 --> 00:37:50.280 align:start position:0% then what we're doing here is simply and 00:37:50.280 --> 00:37:52.370 align:start position:0% then what we're doing here is simply and this<00:37:50.460> is<00:37:50.579> a<00:37:50.820> at<00:37:51.119> least<00:37:51.240> a<00:37:51.540> classic<00:37:51.780> function<00:37:52.200> of 00:37:52.370 --> 00:37:52.380 align:start position:0% this is a at least a classic function of 00:37:52.380 --> 00:37:55.490 align:start position:0% this is a at least a classic function of Cairo<00:37:52.920> that<00:37:53.400> is<00:37:53.579> using<00:37:53.940> recursion<00:37:54.540> so<00:37:55.320> right 00:37:55.490 --> 00:37:55.500 align:start position:0% Cairo that is using recursion so right 00:37:55.500 --> 00:37:57.410 align:start position:0% Cairo that is using recursion so right now<00:37:55.680> we<00:37:55.980> don't<00:37:56.099> have<00:37:56.280> Force 00:37:57.410 --> 00:37:57.420 align:start position:0% now we don't have Force 00:37:57.420 --> 00:38:00.230 align:start position:0% now we don't have Force in<00:37:57.839> Cairo<00:37:58.200> you<00:37:58.380> have<00:37:58.500> to<00:37:58.619> use<00:37:58.740> precaution<00:37:59.820> and 00:38:00.230 --> 00:38:00.240 align:start position:0% in Cairo you have to use precaution and 00:38:00.240 --> 00:38:02.390 align:start position:0% in Cairo you have to use precaution and this<00:38:00.359> is<00:38:00.480> a<00:38:00.599> classic<00:38:00.720> function<00:38:01.140> for<00:38:01.320> it 00:38:02.390 --> 00:38:02.400 align:start position:0% this is a classic function for it 00:38:02.400 --> 00:38:06.230 align:start position:0% this is a classic function for it when<00:38:03.060> we<00:38:03.359> review<00:38:03.720> here<00:38:04.140> is<00:38:04.619> that<00:38:05.099> uh<00:38:05.760> it<00:38:05.940> is<00:38:06.060> the 00:38:06.230 --> 00:38:06.240 align:start position:0% when we review here is that uh it is the 00:38:06.240 --> 00:38:08.930 align:start position:0% when we review here is that uh it is the end<00:38:06.359> of<00:38:06.540> the<00:38:06.720> recursion<00:38:07.260> so<00:38:08.099> if<00:38:08.520> we<00:38:08.820> have 00:38:08.930 --> 00:38:08.940 align:start position:0% end of the recursion so if we have 00:38:08.940 --> 00:38:11.210 align:start position:0% end of the recursion so if we have already<00:38:09.119> passed<00:38:09.720> to<00:38:09.900> every<00:38:10.320> each<00:38:10.680> of<00:38:10.920> these 00:38:11.210 --> 00:38:11.220 align:start position:0% already passed to every each of these 00:38:11.220 --> 00:38:13.790 align:start position:0% already passed to every each of these different<00:38:11.460> members<00:38:12.240> of<00:38:12.420> the<00:38:12.599> array<00:38:12.839> that<00:38:13.680> is 00:38:13.790 --> 00:38:13.800 align:start position:0% different members of the array that is 00:38:13.800 --> 00:38:16.550 align:start position:0% different members of the array that is if<00:38:13.980> the<00:38:14.160> length<00:38:14.520> is<00:38:14.640> zero<00:38:15.060> then<00:38:15.960> we<00:38:16.200> can<00:38:16.380> return 00:38:16.550 --> 00:38:16.560 align:start position:0% if the length is zero then we can return 00:38:16.560 --> 00:38:22.069 align:start position:0% if the length is zero then we can return and<00:38:17.040> the<00:38:17.280> recursion<00:38:17.700> is<00:38:17.880> finished 00:38:22.069 --> 00:38:22.079 align:start position:0% 00:38:22.079 --> 00:38:25.089 align:start position:0% then<00:38:22.740> he<00:38:22.980> will<00:38:23.160> create<00:38:23.339> a<00:38:23.579> small<00:38:23.880> a<00:38:24.660> small 00:38:25.089 --> 00:38:25.099 align:start position:0% then he will create a small a small 00:38:25.099 --> 00:38:27.829 align:start position:0% then he will create a small a small struct<00:38:26.099> the<00:38:26.460> water<00:38:26.700> info<00:38:27.119> do<00:38:27.359> you<00:38:27.420> remember<00:38:27.540> we 00:38:27.829 --> 00:38:27.839 align:start position:0% struct the water info do you remember we 00:38:27.839 --> 00:38:29.630 align:start position:0% struct the water info do you remember we defined<00:38:28.260> the<00:38:28.440> stroke<00:38:28.740> called<00:38:28.920> motor<00:38:29.160> info 00:38:29.630 --> 00:38:29.640 align:start position:0% defined the stroke called motor info 00:38:29.640 --> 00:38:33.290 align:start position:0% defined the stroke called motor info here<00:38:30.480> we<00:38:30.780> are<00:38:31.020> creating<00:38:31.560> this<00:38:31.859> butante 00:38:33.290 --> 00:38:33.300 align:start position:0% here we are creating this butante 00:38:33.300 --> 00:38:36.829 align:start position:0% here we are creating this butante info<00:38:34.079> where<00:38:34.560> we<00:38:34.800> have<00:38:34.980> this<00:38:35.940> new<00:38:36.060> motor<00:38:36.300> info 00:38:36.829 --> 00:38:36.839 align:start position:0% info where we have this new motor info 00:38:36.839 --> 00:38:39.050 align:start position:0% info where we have this new motor info so<00:38:37.020> empty<00:38:37.440> anything<00:38:37.680> here<00:38:38.220> that<00:38:38.400> allow<00:38:38.760> is 00:38:39.050 --> 00:38:39.060 align:start position:0% so empty anything here that allow is 00:38:39.060 --> 00:38:41.630 align:start position:0% so empty anything here that allow is equal<00:38:39.240> one<00:38:39.599> it<00:38:39.960> could<00:38:40.079> be<00:38:40.200> zero<00:38:40.560> for<00:38:40.680> example 00:38:41.630 --> 00:38:41.640 align:start position:0% equal one it could be zero for example 00:38:41.640 --> 00:38:43.250 align:start position:0% equal one it could be zero for example so<00:38:41.940> this<00:38:42.060> function<00:38:42.240> what<00:38:42.480> it's<00:38:42.660> doing<00:38:42.780> is<00:38:43.140> that 00:38:43.250 --> 00:38:43.260 align:start position:0% so this function what it's doing is that 00:38:43.260 --> 00:38:44.690 align:start position:0% so this function what it's doing is that each<00:38:43.500> of<00:38:43.619> the<00:38:43.740> address<00:38:43.859> that<00:38:44.160> I'm<00:38:44.280> providing 00:38:44.690 --> 00:38:44.700 align:start position:0% each of the address that I'm providing 00:38:44.700 --> 00:38:47.089 align:start position:0% each of the address that I'm providing it<00:38:45.000> will<00:38:45.240> register<00:38:45.599> them<00:38:45.900> as<00:38:46.079> voters<00:38:46.560> and<00:38:46.920> we 00:38:47.089 --> 00:38:47.099 align:start position:0% it will register them as voters and we 00:38:47.099 --> 00:38:49.550 align:start position:0% it will register them as voters and we tell<00:38:47.339> we<00:38:47.820> tell<00:38:48.240> us<00:38:48.420> that<00:38:48.599> they<00:38:48.900> are<00:38:49.079> allowed<00:38:49.440> to 00:38:49.550 --> 00:38:49.560 align:start position:0% tell we tell us that they are allowed to 00:38:49.560 --> 00:38:51.650 align:start position:0% tell we tell us that they are allowed to vote<00:38:50.280> okay 00:38:51.650 --> 00:38:51.660 align:start position:0% vote okay 00:38:51.660 --> 00:38:54.050 align:start position:0% vote okay and<00:38:52.380> then<00:38:52.500> continue<00:38:52.800> a<00:38:53.280> little<00:38:53.400> bit<00:38:53.579> with<00:38:53.940> the 00:38:54.050 --> 00:38:54.060 align:start position:0% and then continue a little bit with the 00:38:54.060 --> 00:38:56.210 align:start position:0% and then continue a little bit with the recursion 00:38:56.210 --> 00:38:56.220 align:start position:0% recursion 00:38:56.220 --> 00:38:58.730 align:start position:0% recursion what<00:38:56.640> we're<00:38:56.820> doing<00:38:57.000> here<00:38:57.359> is<00:38:57.720> writing<00:38:58.619> into 00:38:58.730 --> 00:38:58.740 align:start position:0% what we're doing here is writing into 00:38:58.740 --> 00:39:01.010 align:start position:0% what we're doing here is writing into storage<00:38:59.099> into<00:39:00.060> the<00:39:00.300> storage<00:39:00.599> variable 00:39:01.010 --> 00:39:01.020 align:start position:0% storage into the storage variable 00:39:01.020 --> 00:39:07.430 align:start position:0% storage into the storage variable register<00:39:01.440> motor 00:39:07.430 --> 00:39:07.440 align:start position:0% 00:39:07.440 --> 00:39:10.010 align:start position:0% yes<00:39:08.099> this<00:39:08.579> one<00:39:08.760> we're<00:39:09.119> mapping<00:39:09.599> as<00:39:09.900> you 00:39:10.010 --> 00:39:10.020 align:start position:0% yes this one we're mapping as you 00:39:10.020 --> 00:39:12.170 align:start position:0% yes this one we're mapping as you remember<00:39:10.140> before<00:39:10.500> we<00:39:10.740> mapping<00:39:11.099> an<00:39:11.280> address<00:39:11.400> to 00:39:12.170 --> 00:39:12.180 align:start position:0% remember before we mapping an address to 00:39:12.180 --> 00:39:15.230 align:start position:0% remember before we mapping an address to a<00:39:12.359> number<00:39:12.480> so<00:39:13.320> this<00:39:13.560> is<00:39:13.740> an<00:39:13.920> address<00:39:14.060> what<00:39:15.060> we 00:39:15.230 --> 00:39:15.240 align:start position:0% a number so this is an address what we 00:39:15.240 --> 00:39:16.370 align:start position:0% a number so this is an address what we have<00:39:15.420> here 00:39:16.370 --> 00:39:16.380 align:start position:0% have here 00:39:16.380 --> 00:39:19.069 align:start position:0% have here is<00:39:17.040> this<00:39:17.460> is<00:39:17.579> the<00:39:17.760> array<00:39:18.000> as<00:39:18.300> very<00:39:18.540> similar<00:39:18.839> as 00:39:19.069 --> 00:39:19.079 align:start position:0% is this is the array as very similar as 00:39:19.079 --> 00:39:20.750 align:start position:0% is this is the array as very similar as you<00:39:19.140> would<00:39:19.320> do<00:39:19.440> it<00:39:19.560> in<00:39:19.740> Python<00:39:20.099> for<00:39:20.339> example<00:39:20.520> on 00:39:20.750 --> 00:39:20.760 align:start position:0% you would do it in Python for example on 00:39:20.760 --> 00:39:22.609 align:start position:0% you would do it in Python for example on all<00:39:21.000> languages<00:39:21.240> you<00:39:21.839> have<00:39:21.960> that<00:39:22.140> right<00:39:22.320> and 00:39:22.609 --> 00:39:22.619 align:start position:0% all languages you have that right and 00:39:22.619 --> 00:39:25.430 align:start position:0% all languages you have that right and you<00:39:22.740> can<00:39:22.859> index<00:39:23.280> to<00:39:23.579> it<00:39:23.760> using<00:39:24.599> the<00:39:25.260> square 00:39:25.430 --> 00:39:25.440 align:start position:0% you can index to it using the square 00:39:25.440 --> 00:39:28.790 align:start position:0% you can index to it using the square brackets<00:39:25.980> okay<00:39:26.579> so<00:39:27.420> I<00:39:27.599> am<00:39:27.839> indexing<00:39:28.500> in<00:39:28.680> the 00:39:28.790 --> 00:39:28.800 align:start position:0% brackets okay so I am indexing in the 00:39:28.800 --> 00:39:30.530 align:start position:0% brackets okay so I am indexing in the inside<00:39:29.040> this<00:39:29.339> array<00:39:29.640> for<00:39:29.940> this<00:39:30.180> could<00:39:30.300> be<00:39:30.420> a 00:39:30.530 --> 00:39:30.540 align:start position:0% inside this array for this could be a 00:39:30.540 --> 00:39:32.810 align:start position:0% inside this array for this could be a number<00:39:30.660> like<00:39:30.960> one<00:39:31.260> or<00:39:31.500> two<00:39:31.680> or<00:39:31.920> five 00:39:32.810 --> 00:39:32.820 align:start position:0% number like one or two or five 00:39:32.820 --> 00:39:34.609 align:start position:0% number like one or two or five depends<00:39:33.420> on<00:39:33.480> the<00:39:33.599> number<00:39:33.720> of<00:39:33.839> address<00:39:34.140> that<00:39:34.500> we 00:39:34.609 --> 00:39:34.619 align:start position:0% depends on the number of address that we 00:39:34.619 --> 00:39:35.750 align:start position:0% depends on the number of address that we are<00:39:34.680> adding 00:39:35.750 --> 00:39:35.760 align:start position:0% are adding 00:39:35.760 --> 00:39:39.410 align:start position:0% are adding and<00:39:36.660> then<00:39:37.140> we<00:39:37.500> say<00:39:38.099> that<00:39:38.400> the<00:39:38.640> value<00:39:38.820> for<00:39:39.180> that 00:39:39.410 --> 00:39:39.420 align:start position:0% and then we say that the value for that 00:39:39.420 --> 00:39:42.170 align:start position:0% and then we say that the value for that address<00:39:39.960> is<00:39:40.560> one<00:39:40.740> we<00:39:41.280> are<00:39:41.460> simply<00:39:41.700> mapping<00:39:42.000> it 00:39:42.170 --> 00:39:42.180 align:start position:0% address is one we are simply mapping it 00:39:42.180 --> 00:39:43.190 align:start position:0% address is one we are simply mapping it here 00:39:43.190 --> 00:39:43.200 align:start position:0% here 00:39:43.200 --> 00:39:46.970 align:start position:0% here and<00:39:43.740> then<00:39:43.859> we<00:39:44.160> become<00:39:44.820> the<00:39:44.880> recursion<00:39:45.780> part 00:39:46.970 --> 00:39:46.980 align:start position:0% and then we become the recursion part 00:39:46.980 --> 00:39:48.470 align:start position:0% and then we become the recursion part here 00:39:48.470 --> 00:39:48.480 align:start position:0% here 00:39:48.480 --> 00:39:50.390 align:start position:0% here we<00:39:48.839> are<00:39:49.020> reading<00:39:49.260> again<00:39:49.440> the<00:39:49.740> same<00:39:49.980> function 00:39:50.390 --> 00:39:50.400 align:start position:0% we are reading again the same function 00:39:50.400 --> 00:39:53.690 align:start position:0% we are reading again the same function and<00:39:51.359> providing<00:39:51.900> the<00:39:52.260> length<00:39:52.619> but<00:39:52.859> this<00:39:53.280> is<00:39:53.460> a 00:39:53.690 --> 00:39:53.700 align:start position:0% and providing the length but this is a 00:39:53.700 --> 00:39:55.970 align:start position:0% and providing the length but this is a lower<00:39:53.880> length<00:39:54.660> as<00:39:55.200> you<00:39:55.320> can<00:39:55.440> see<00:39:55.500> if<00:39:55.680> we<00:39:55.859> have 00:39:55.970 --> 00:39:55.980 align:start position:0% lower length as you can see if we have 00:39:55.980 --> 00:39:57.410 align:start position:0% lower length as you can see if we have for<00:39:56.160> example<00:39:56.280> five<00:39:56.579> different<00:39:56.760> voters<00:39:57.240> that 00:39:57.410 --> 00:39:57.420 align:start position:0% for example five different voters that 00:39:57.420 --> 00:40:00.010 align:start position:0% for example five different voters that now<00:39:57.660> we<00:39:57.780> are<00:39:57.900> providing<00:39:58.140> it<00:39:58.320> with<00:39:58.440> four<00:39:58.619> okay 00:40:00.010 --> 00:40:00.020 align:start position:0% now we are providing it with four okay 00:40:00.020 --> 00:40:02.569 align:start position:0% now we are providing it with four okay and<00:40:01.020> we<00:40:01.320> are<00:40:01.500> sending<00:40:01.800> it<00:40:01.920> with<00:40:02.160> the<00:40:02.280> register 00:40:02.569 --> 00:40:02.579 align:start position:0% and we are sending it with the register 00:40:02.579 --> 00:40:04.910 align:start position:0% and we are sending it with the register address<00:40:03.300> and<00:40:03.839> then<00:40:03.960> it<00:40:04.200> will<00:40:04.320> repeat<00:40:04.440> it<00:40:04.800> will 00:40:04.910 --> 00:40:04.920 align:start position:0% address and then it will repeat it will 00:40:04.920 --> 00:40:06.589 align:start position:0% address and then it will repeat it will repeat<00:40:05.099> until<00:40:05.460> it<00:40:05.760> passes<00:40:06.119> through<00:40:06.240> each<00:40:06.480> of 00:40:06.589 --> 00:40:06.599 align:start position:0% repeat until it passes through each of 00:40:06.599 --> 00:40:08.150 align:start position:0% repeat until it passes through each of the<00:40:06.720> different<00:40:06.839> addresses<00:40:07.440> and<00:40:07.859> it<00:40:08.040> is 00:40:08.150 --> 00:40:08.160 align:start position:0% the different addresses and it is 00:40:08.160 --> 00:40:10.609 align:start position:0% the different addresses and it is starting<00:40:08.339> for<00:40:08.700> from<00:40:08.880> the<00:40:09.060> last<00:40:09.240> one<00:40:09.420> up<00:40:10.079> to<00:40:10.440> the 00:40:10.609 --> 00:40:10.619 align:start position:0% starting for from the last one up to the 00:40:10.619 --> 00:40:12.230 align:start position:0% starting for from the last one up to the first<00:40:10.740> ones 00:40:12.230 --> 00:40:12.240 align:start position:0% first ones 00:40:12.240 --> 00:40:13.730 align:start position:0% first ones I<00:40:12.599> know<00:40:12.780> what<00:40:12.900> this<00:40:13.079> looks<00:40:13.320> a<00:40:13.500> little<00:40:13.560> bit 00:40:13.730 --> 00:40:13.740 align:start position:0% I know what this looks a little bit 00:40:13.740 --> 00:40:16.190 align:start position:0% I know what this looks a little bit crazy<00:40:13.980> here<00:40:14.400> using<00:40:14.760> caution<00:40:15.180> Bots 00:40:16.190 --> 00:40:16.200 align:start position:0% crazy here using caution Bots 00:40:16.200 --> 00:40:18.170 align:start position:0% crazy here using caution Bots it's<00:40:16.740> no<00:40:16.980> problem<00:40:17.099> you<00:40:17.339> you<00:40:17.579> can<00:40:17.700> get<00:40:17.880> used<00:40:18.000> to 00:40:18.170 --> 00:40:18.180 align:start position:0% it's no problem you you can get used to 00:40:18.180 --> 00:40:21.170 align:start position:0% it's no problem you you can get used to it<00:40:18.359> and<00:40:18.599> I<00:40:19.380> think<00:40:19.560> that<00:40:19.980> this<00:40:20.579> will<00:40:20.760> improve<00:40:21.060> in 00:40:21.170 --> 00:40:21.180 align:start position:0% it and I think that this will improve in 00:40:21.180 --> 00:40:29.510 align:start position:0% it and I think that this will improve in the<00:40:21.300> near<00:40:21.780> future<00:40:21.960> right 00:40:29.510 --> 00:40:29.520 align:start position:0% 00:40:29.520 --> 00:40:32.690 align:start position:0% yes well<00:40:29.880> that's<00:40:30.119> a<00:40:30.240> good<00:40:30.359> question 00:40:32.690 --> 00:40:32.700 align:start position:0% 00:40:32.700 --> 00:40:34.490 align:start position:0% the<00:40:33.060> question<00:40:33.180> is<00:40:33.420> that<00:40:33.660> what<00:40:33.839> happens<00:40:34.020> if<00:40:34.320> you 00:40:34.490 --> 00:40:34.500 align:start position:0% the question is that what happens if you 00:40:34.500 --> 00:40:37.069 align:start position:0% the question is that what happens if you get<00:40:34.619> into<00:40:34.800> an<00:40:34.980> infinite<00:40:35.339> recursion 00:40:37.069 --> 00:40:37.079 align:start position:0% get into an infinite recursion 00:40:37.079 --> 00:40:39.290 align:start position:0% get into an infinite recursion um<00:40:37.140> you 00:40:39.290 --> 00:40:39.300 align:start position:0% um you 00:40:39.300 --> 00:40:41.990 align:start position:0% um you okay<00:40:39.780> so<00:40:40.020> there's<00:40:40.320> there<00:40:40.800> is<00:40:41.040> the<00:40:41.400> there's<00:40:41.760> an 00:40:41.990 --> 00:40:42.000 align:start position:0% okay so there's there is the there's an 00:40:42.000 --> 00:40:43.970 align:start position:0% okay so there's there is the there's an answer<00:40:42.119> for<00:40:42.420> today<00:40:42.660> and<00:40:43.320> an<00:40:43.440> answer<00:40:43.619> for 00:40:43.970 --> 00:40:43.980 align:start position:0% answer for today and an answer for 00:40:43.980 --> 00:40:45.829 align:start position:0% answer for today and an answer for tomorrow<00:40:44.280> but<00:40:44.700> basically<00:40:45.060> there's<00:40:45.300> a<00:40:45.540> form<00:40:45.660> of 00:40:45.829 --> 00:40:45.839 align:start position:0% tomorrow but basically there's a form of 00:40:45.839 --> 00:40:48.230 align:start position:0% tomorrow but basically there's a form of gas<00:40:46.020> metering<00:40:46.680> in<00:40:47.040> starknot<00:40:47.579> just<00:40:47.700> like<00:40:47.880> in 00:40:48.230 --> 00:40:48.240 align:start position:0% gas metering in starknot just like in 00:40:48.240 --> 00:40:50.510 align:start position:0% gas metering in starknot just like in ethereum<00:40:48.660> and<00:40:49.079> if<00:40:49.260> we<00:40:49.440> reach<00:40:49.680> a<00:40:49.859> match<00:40:49.980> maximum 00:40:50.510 --> 00:40:50.520 align:start position:0% ethereum and if we reach a match maximum 00:40:50.520 --> 00:40:52.190 align:start position:0% ethereum and if we reach a match maximum number<00:40:50.820> of<00:40:51.000> steps<00:40:51.359> the<00:40:51.540> sequencer<00:40:51.960> will 00:40:52.190 --> 00:40:52.200 align:start position:0% number of steps the sequencer will 00:40:52.200 --> 00:40:54.290 align:start position:0% number of steps the sequencer will recheck<00:40:52.859> your<00:40:52.920> transaction 00:40:54.290 --> 00:40:54.300 align:start position:0% recheck your transaction 00:40:54.300 --> 00:40:56.930 align:start position:0% recheck your transaction today<00:40:54.660> you're<00:40:54.960> not<00:40:55.260> you<00:40:56.099> don't<00:40:56.339> pay<00:40:56.520> for<00:40:56.760> this 00:40:56.930 --> 00:40:56.940 align:start position:0% today you're not you don't pay for this 00:40:56.940 --> 00:40:58.250 align:start position:0% today you're not you don't pay for this kind<00:40:57.119> of<00:40:57.180> transactions<00:40:57.720> they're<00:40:58.020> just 00:40:58.250 --> 00:40:58.260 align:start position:0% kind of transactions they're just 00:40:58.260 --> 00:41:00.829 align:start position:0% kind of transactions they're just rejected<00:40:58.740> tomorrow 00:41:00.829 --> 00:41:00.839 align:start position:0% rejected tomorrow 00:41:00.839 --> 00:41:02.630 align:start position:0% rejected tomorrow um<00:41:00.900> you<00:41:01.140> will<00:41:01.320> be<00:41:01.560> it<00:41:01.980> will<00:41:02.099> be<00:41:02.220> like<00:41:02.339> a<00:41:02.460> fake 00:41:02.630 --> 00:41:02.640 align:start position:0% um you will be it will be like a fake 00:41:02.640 --> 00:41:04.250 align:start position:0% um you will be it will be like a fake transactional<00:41:03.119> ethereum<00:41:03.480> you<00:41:03.660> will<00:41:03.780> pay<00:41:03.960> fees 00:41:04.250 --> 00:41:04.260 align:start position:0% transactional ethereum you will pay fees 00:41:04.260 --> 00:41:08.569 align:start position:0% transactional ethereum you will pay fees for<00:41:04.440> the<00:41:04.560> execution<00:41:04.980> that<00:41:05.280> led<00:41:05.579> nowhere 00:41:08.569 --> 00:41:08.579 align:start position:0% 00:41:08.579 --> 00:41:10.670 align:start position:0% good 00:41:10.670 --> 00:41:10.680 align:start position:0% good 00:41:10.680 --> 00:41:13.970 align:start position:0% good perfect<00:41:11.160> any<00:41:11.460> other<00:41:11.640> questions<00:41:11.940> for<00:41:12.480> a<00:41:12.599> moment 00:41:13.970 --> 00:41:13.980 align:start position:0% perfect any other questions for a moment 00:41:13.980 --> 00:41:16.550 align:start position:0% perfect any other questions for a moment okay<00:41:14.579> so<00:41:15.420> simply<00:41:15.780> we<00:41:15.900> have<00:41:16.020> a<00:41:16.140> recursion 00:41:16.550 --> 00:41:16.560 align:start position:0% okay so simply we have a recursion 00:41:16.560 --> 00:41:18.530 align:start position:0% okay so simply we have a recursion function<00:41:16.800> here<00:41:17.040> again<00:41:17.460> it's<00:41:17.880> not<00:41:18.119> that<00:41:18.300> hard 00:41:18.530 --> 00:41:18.540 align:start position:0% function here again it's not that hard 00:41:18.540 --> 00:41:20.270 align:start position:0% function here again it's not that hard and<00:41:18.839> it<00:41:18.960> will<00:41:19.079> improve<00:41:19.440> we're<00:41:19.740> talking<00:41:20.040> that 00:41:20.270 --> 00:41:20.280 align:start position:0% and it will improve we're talking that 00:41:20.280 --> 00:41:22.069 align:start position:0% and it will improve we're talking that Cairo<00:41:20.760> is<00:41:20.880> a<00:41:21.000> low<00:41:21.119> level<00:41:21.300> language<00:41:21.540> and<00:41:21.839> we 00:41:22.069 --> 00:41:22.079 align:start position:0% Cairo is a low level language and we 00:41:22.079 --> 00:41:24.109 align:start position:0% Cairo is a low level language and we have<00:41:22.260> to<00:41:22.380> be<00:41:22.560> very<00:41:22.859> honest<00:41:23.640> and<00:41:23.760> conscious 00:41:24.109 --> 00:41:24.119 align:start position:0% have to be very honest and conscious 00:41:24.119 --> 00:41:27.829 align:start position:0% have to be very honest and conscious about<00:41:24.300> that 00:41:27.829 --> 00:41:27.839 align:start position:0% 00:41:27.839 --> 00:41:29.390 align:start position:0% and<00:41:28.260> finally<00:41:28.500> let's<00:41:28.740> go<00:41:28.920> to<00:41:29.040> the<00:41:29.160> last 00:41:29.390 --> 00:41:29.400 align:start position:0% and finally let's go to the last 00:41:29.400 --> 00:41:31.609 align:start position:0% and finally let's go to the last function<00:41:29.820> that<00:41:30.660> is<00:41:30.780> the<00:41:30.900> Boating<00:41:31.200> function 00:41:31.609 --> 00:41:31.619 align:start position:0% function that is the Boating function 00:41:31.619 --> 00:41:33.890 align:start position:0% function that is the Boating function this<00:41:31.920> will<00:41:32.099> allow<00:41:32.400> us<00:41:32.520> to<00:41:32.820> call<00:41:33.000> a<00:41:33.300> function<00:41:33.599> as 00:41:33.890 --> 00:41:33.900 align:start position:0% this will allow us to call a function as 00:41:33.900 --> 00:41:35.750 align:start position:0% this will allow us to call a function as as<00:41:34.079> you<00:41:34.260> can<00:41:34.380> see<00:41:34.560> here<00:41:34.800> it's<00:41:35.099> an<00:41:35.280> external 00:41:35.750 --> 00:41:35.760 align:start position:0% as you can see here it's an external 00:41:35.760 --> 00:41:36.890 align:start position:0% as you can see here it's an external function 00:41:36.890 --> 00:41:36.900 align:start position:0% function 00:41:36.900 --> 00:41:38.329 align:start position:0% function external<00:41:37.260> function<00:41:37.560> simply<00:41:37.859> means<00:41:38.099> that<00:41:38.160> we 00:41:38.329 --> 00:41:38.339 align:start position:0% external function simply means that we 00:41:38.339 --> 00:41:41.030 align:start position:0% external function simply means that we can<00:41:38.520> write<00:41:38.820> on<00:41:39.359> the<00:41:39.480> storage<00:41:39.660> using<00:41:40.260> it<00:41:40.380> okay 00:41:41.030 --> 00:41:41.040 align:start position:0% can write on the storage using it okay 00:41:41.040 --> 00:41:44.510 align:start position:0% can write on the storage using it okay not<00:41:41.760> only<00:41:41.880> reads<00:41:42.480> but<00:41:43.200> we<00:41:43.500> can<00:41:43.800> hear<00:41:44.040> right 00:41:44.510 --> 00:41:44.520 align:start position:0% not only reads but we can hear right 00:41:44.520 --> 00:41:45.710 align:start position:0% not only reads but we can hear right into<00:41:44.700> the<00:41:44.940> storage 00:41:45.710 --> 00:41:45.720 align:start position:0% into the storage 00:41:45.720 --> 00:41:51.230 align:start position:0% into the storage again<00:41:46.260> we<00:41:46.619> have<00:41:46.740> our<00:41:46.859> implicit<00:41:47.339> arguments 00:41:51.230 --> 00:41:51.240 align:start position:0% 00:41:51.240 --> 00:41:54.230 align:start position:0% we<00:41:51.720> have<00:41:51.839> an<00:41:51.960> explicit<00:41:52.260> argument<00:41:52.619> called<00:41:52.920> both 00:41:54.230 --> 00:41:54.240 align:start position:0% we have an explicit argument called both 00:41:54.240 --> 00:41:55.910 align:start position:0% we have an explicit argument called both and<00:41:54.720> here 00:41:55.910 --> 00:41:55.920 align:start position:0% and here 00:41:55.920 --> 00:41:58.790 align:start position:0% and here don't<00:41:56.280> mind<00:41:56.520> this<00:41:56.760> part<00:41:57.000> simply<00:41:57.680> telling<00:41:58.680> the 00:41:58.790 --> 00:41:58.800 align:start position:0% don't mind this part simply telling the 00:41:58.800 --> 00:41:59.930 align:start position:0% don't mind this part simply telling the memory<00:41:59.040> that<00:41:59.220> we<00:41:59.339> will<00:41:59.460> be<00:41:59.579> using<00:41:59.820> the 00:41:59.930 --> 00:41:59.940 align:start position:0% memory that we will be using the 00:41:59.940 --> 00:42:01.130 align:start position:0% memory that we will be using the compiler<00:42:00.359> that<00:42:00.480> will<00:42:00.599> be<00:42:00.720> using<00:42:00.960> local 00:42:01.130 --> 00:42:01.140 align:start position:0% compiler that will be using local 00:42:01.140 --> 00:42:02.470 align:start position:0% compiler that will be using local variables 00:42:02.470 --> 00:42:02.480 align:start position:0% variables 00:42:02.480 --> 00:42:05.690 align:start position:0% variables we<00:42:03.480> don't<00:42:04.140> need<00:42:04.380> to<00:42:04.500> go<00:42:04.619> through<00:42:04.800> that<00:42:04.980> we're 00:42:05.690 --> 00:42:05.700 align:start position:0% we don't need to go through that we're 00:42:05.700 --> 00:42:07.190 align:start position:0% we don't need to go through that we're called<00:42:05.940> the<00:42:06.119> possible<00:42:06.480> function<00:42:06.780> from<00:42:06.960> from 00:42:07.190 --> 00:42:07.200 align:start position:0% called the possible function from from 00:42:07.200 --> 00:42:09.349 align:start position:0% called the possible function from from open<00:42:07.380> sampling<00:42:07.859> contracts<00:42:08.400> specifically<00:42:09.240> the 00:42:09.349 --> 00:42:09.359 align:start position:0% open sampling contracts specifically the 00:42:09.359 --> 00:42:11.569 align:start position:0% open sampling contracts specifically the function<00:42:09.660> called<00:42:09.900> assert<00:42:10.320> not<00:42:10.619> pause 00:42:11.569 --> 00:42:11.579 align:start position:0% function called assert not pause 00:42:11.579 --> 00:42:13.430 align:start position:0% function called assert not pause it<00:42:11.640> checks<00:42:12.119> that<00:42:12.240> if<00:42:12.599> if<00:42:12.780> this<00:42:12.960> control<00:42:13.140> is 00:42:13.430 --> 00:42:13.440 align:start position:0% it checks that if if this control is 00:42:13.440 --> 00:42:15.290 align:start position:0% it checks that if if this control is false<00:42:13.740> or<00:42:13.859> not<00:42:13.980> if<00:42:14.460> it<00:42:14.579> pause<00:42:14.820> this<00:42:15.180> person 00:42:15.290 --> 00:42:15.300 align:start position:0% false or not if it pause this person 00:42:15.300 --> 00:42:17.569 align:start position:0% false or not if it pause this person cannot<00:42:15.720> vote<00:42:15.960> as<00:42:16.320> simple<00:42:16.619> as<00:42:16.800> that 00:42:17.569 --> 00:42:17.579 align:start position:0% cannot vote as simple as that 00:42:17.579 --> 00:42:20.089 align:start position:0% cannot vote as simple as that then<00:42:18.300> you<00:42:18.480> get<00:42:18.660> the<00:42:18.780> caller<00:42:19.140> address<00:42:19.260> this<00:42:19.859> was 00:42:20.089 --> 00:42:20.099 align:start position:0% then you get the caller address this was 00:42:20.099 --> 00:42:22.730 align:start position:0% then you get the caller address this was a<00:42:20.480> question<00:42:21.480> from<00:42:21.780> before<00:42:21.960> with<00:42:22.619> this 00:42:22.730 --> 00:42:22.740 align:start position:0% a question from before with this 00:42:22.740 --> 00:42:25.310 align:start position:0% a question from before with this function<00:42:23.040> we<00:42:23.280> can<00:42:23.400> get<00:42:24.060> the<00:42:24.599> address<00:42:24.660> of<00:42:25.140> this 00:42:25.310 --> 00:42:25.320 align:start position:0% function we can get the address of this 00:42:25.320 --> 00:42:27.230 align:start position:0% function we can get the address of this color<00:42:25.500> we're<00:42:26.040> storing<00:42:26.460> it<00:42:26.579> inside<00:42:26.760> the<00:42:27.000> color 00:42:27.230 --> 00:42:27.240 align:start position:0% color we're storing it inside the color 00:42:27.240 --> 00:42:28.310 align:start position:0% color we're storing it inside the color function 00:42:28.310 --> 00:42:28.320 align:start position:0% function 00:42:28.320 --> 00:42:31.490 align:start position:0% function then<00:42:28.920> we<00:42:29.280> can<00:42:29.400> read<00:42:29.660> the<00:42:30.660> information<00:42:30.839> of<00:42:31.380> this 00:42:31.490 --> 00:42:31.500 align:start position:0% then we can read the information of this 00:42:31.500 --> 00:42:34.490 align:start position:0% then we can read the information of this color<00:42:31.740> of<00:42:32.040> this<00:42:32.220> address<00:42:32.400> using<00:42:33.240> the<00:42:33.359> reads 00:42:34.490 --> 00:42:34.500 align:start position:0% color of this address using the reads 00:42:34.500 --> 00:42:36.950 align:start position:0% color of this address using the reads argument<00:42:35.160> from<00:42:35.460> this<00:42:35.579> touch<00:42:35.820> variable<00:42:36.300> that's 00:42:36.950 --> 00:42:36.960 align:start position:0% argument from this touch variable that's 00:42:36.960 --> 00:42:38.870 align:start position:0% argument from this touch variable that's already<00:42:37.260> the<00:42:37.500> nympho 00:42:38.870 --> 00:42:38.880 align:start position:0% already the nympho 00:42:38.880 --> 00:42:41.630 align:start position:0% already the nympho and<00:42:39.420> then<00:42:39.540> we<00:42:39.839> are<00:42:39.960> simply<00:42:40.200> reviewing<00:42:40.800> is<00:42:41.339> this 00:42:41.630 --> 00:42:41.640 align:start position:0% and then we are simply reviewing is this 00:42:41.640 --> 00:42:44.089 align:start position:0% and then we are simply reviewing is this person<00:42:41.880> can<00:42:42.720> vote<00:42:43.020> or<00:42:43.320> not 00:42:44.089 --> 00:42:44.099 align:start position:0% person can vote or not 00:42:44.099 --> 00:42:46.370 align:start position:0% person can vote or not if<00:42:44.640> they<00:42:44.820> have<00:42:45.000> a<00:42:45.119> low<00:42:45.300> zero<00:42:45.780> then<00:42:45.960> they<00:42:46.140> cannot 00:42:46.370 --> 00:42:46.380 align:start position:0% if they have a low zero then they cannot 00:42:46.380 --> 00:42:49.910 align:start position:0% if they have a low zero then they cannot vote 00:42:49.910 --> 00:42:49.920 align:start position:0% 00:42:49.920 --> 00:42:53.150 align:start position:0% then<00:42:50.460> we're<00:42:50.640> creating<00:42:51.000> a<00:42:51.480> new<00:42:51.660> bullet<00:42:52.160> border 00:42:53.150 --> 00:42:53.160 align:start position:0% then we're creating a new bullet border 00:42:53.160 --> 00:42:55.609 align:start position:0% then we're creating a new bullet border info<00:42:53.579> extract<00:42:54.180> that<00:42:55.020> it<00:42:55.140> says<00:42:55.320> that<00:42:55.440> this 00:42:55.609 --> 00:42:55.619 align:start position:0% info extract that it says that this 00:42:55.619 --> 00:42:57.890 align:start position:0% info extract that it says that this person<00:42:55.740> has<00:42:56.040> already<00:42:56.220> bought<00:42:56.579> because<00:42:57.480> we 00:42:57.890 --> 00:42:57.900 align:start position:0% person has already bought because we 00:42:57.900 --> 00:43:00.950 align:start position:0% person has already bought because we wanted<00:42:58.260> to<00:42:58.560> vote<00:42:58.800> again 00:43:00.950 --> 00:43:00.960 align:start position:0% wanted to vote again 00:43:00.960 --> 00:43:03.190 align:start position:0% wanted to vote again we<00:43:01.500> are<00:43:01.680> writing<00:43:01.980> on<00:43:02.099> the<00:43:02.220> storage<00:43:02.280> here 00:43:03.190 --> 00:43:03.200 align:start position:0% we are writing on the storage here 00:43:03.200 --> 00:43:06.650 align:start position:0% we are writing on the storage here everything<00:43:04.200> here<00:43:04.560> we<00:43:04.800> already<00:43:04.980> know<00:43:05.220> that 00:43:06.650 --> 00:43:06.660 align:start position:0% everything here we already know that 00:43:06.660 --> 00:43:09.410 align:start position:0% everything here we already know that and<00:43:07.440> finally<00:43:07.859> we<00:43:08.400> are<00:43:08.579> updating<00:43:08.940> the<00:43:09.240> status 00:43:09.410 --> 00:43:09.420 align:start position:0% and finally we are updating the status 00:43:09.420 --> 00:43:11.089 align:start position:0% and finally we are updating the status of<00:43:09.780> the<00:43:09.900> boats<00:43:10.260> with<00:43:10.440> the<00:43:10.619> vote<00:43:10.740> of<00:43:10.980> this 00:43:11.089 --> 00:43:11.099 align:start position:0% of the boats with the vote of this 00:43:11.099 --> 00:43:14.210 align:start position:0% of the boats with the vote of this person<00:43:11.280> if<00:43:11.579> this<00:43:12.060> person<00:43:12.240> voted<00:43:12.720> yes<00:43:12.960> or<00:43:13.800> zero 00:43:14.210 --> 00:43:14.220 align:start position:0% person if this person voted yes or zero 00:43:14.220 --> 00:43:16.309 align:start position:0% person if this person voted yes or zero in<00:43:14.460> this<00:43:14.520> case<00:43:14.700> then<00:43:15.540> it<00:43:15.720> will<00:43:15.900> update<00:43:16.140> that 00:43:16.309 --> 00:43:16.319 align:start position:0% in this case then it will update that 00:43:16.319 --> 00:43:17.809 align:start position:0% in this case then it will update that with<00:43:16.500> zero 00:43:17.809 --> 00:43:17.819 align:start position:0% with zero 00:43:17.819 --> 00:43:20.089 align:start position:0% with zero the<00:43:18.180> count<00:43:18.420> with<00:43:18.780> zero<00:43:19.200> and<00:43:19.380> if<00:43:19.740> they<00:43:19.920> bought 00:43:20.089 --> 00:43:20.099 align:start position:0% the count with zero and if they bought 00:43:20.099 --> 00:43:22.490 align:start position:0% the count with zero and if they bought it<00:43:20.339> yes<00:43:20.640> in<00:43:21.000> this<00:43:21.060> case<00:43:21.180> one<00:43:21.480> for<00:43:21.780> example<00:43:22.079> then 00:43:22.490 --> 00:43:22.500 align:start position:0% it yes in this case one for example then 00:43:22.500 --> 00:43:24.470 align:start position:0% it yes in this case one for example then it<00:43:22.740> will<00:43:22.859> be<00:43:22.980> updated<00:43:23.280> the<00:43:23.640> count<00:43:24.000> will<00:43:24.300> be 00:43:24.470 --> 00:43:24.480 align:start position:0% it will be updated the count will be 00:43:24.480 --> 00:43:29.270 align:start position:0% it will be updated the count will be updated<00:43:24.780> with<00:43:25.079> a<00:43:25.260> sum<00:43:25.500> that<00:43:25.920> we<00:43:26.099> have<00:43:26.220> here 00:43:29.270 --> 00:43:29.280 align:start position:0% 00:43:29.280 --> 00:43:32.870 align:start position:0% and<00:43:29.940> finally<00:43:30.300> we<00:43:30.599> are<00:43:30.720> updating<00:43:31.280> the<00:43:32.280> final 00:43:32.870 --> 00:43:32.880 align:start position:0% and finally we are updating the final 00:43:32.880 --> 00:43:35.690 align:start position:0% and finally we are updating the final status<00:43:33.480> of<00:43:33.900> our<00:43:34.140> update<00:43:34.800> the<00:43:35.040> story<00:43:35.280> of<00:43:35.520> our 00:43:35.690 --> 00:43:35.700 align:start position:0% status of our update the story of our 00:43:35.700 --> 00:43:38.990 align:start position:0% status of our update the story of our voting<00:43:36.180> and<00:43:36.839> storing<00:43:37.440> it<00:43:37.560> into<00:43:37.800> the<00:43:38.040> storage 00:43:38.990 --> 00:43:39.000 align:start position:0% voting and storing it into the storage 00:43:39.000 --> 00:43:41.930 align:start position:0% voting and storing it into the storage as<00:43:39.660> you<00:43:39.780> can<00:43:39.960> see<00:43:40.260> this<00:43:40.800> function<00:43:41.160> is<00:43:41.460> scheme 00:43:41.930 --> 00:43:41.940 align:start position:0% as you can see this function is scheme 00:43:41.940 --> 00:43:45.530 align:start position:0% as you can see this function is scheme and<00:43:42.660> if<00:43:42.839> we<00:43:42.960> go<00:43:43.200> to<00:43:43.380> the<00:43:43.800> deploy<00:43:44.339> contract<00:43:44.819> we 00:43:45.530 --> 00:43:45.540 align:start position:0% and if we go to the deploy contract we 00:43:45.540 --> 00:43:47.510 align:start position:0% and if we go to the deploy contract we go<00:43:45.720> to<00:43:45.839> the<00:43:46.020> right<00:43:46.200> contract 00:43:47.510 --> 00:43:47.520 align:start position:0% go to the right contract 00:43:47.520 --> 00:43:50.870 align:start position:0% go to the right contract and<00:43:48.060> then<00:43:48.240> I<00:43:48.540> can<00:43:48.660> vote<00:43:48.980> in<00:43:49.980> this<00:43:50.099> case<00:43:50.280> this<00:43:50.760> is 00:43:50.870 --> 00:43:50.880 align:start position:0% and then I can vote in this case this is 00:43:50.880 --> 00:43:52.609 align:start position:0% and then I can vote in this case this is the<00:43:51.000> function 00:43:52.609 --> 00:43:52.619 align:start position:0% the function 00:43:52.619 --> 00:43:55.309 align:start position:0% the function I<00:43:53.099> don't<00:43:53.220> remember<00:43:53.339> where<00:43:53.640> I<00:43:54.180> say<00:43:54.240> and<00:43:54.780> that<00:43:55.020> I 00:43:55.309 --> 00:43:55.319 align:start position:0% I don't remember where I say and that I 00:43:55.319 --> 00:43:56.750 align:start position:0% I don't remember where I say and that I think 00:43:56.750 --> 00:43:56.760 align:start position:0% think 00:43:56.760 --> 00:44:00.470 align:start position:0% think so<00:43:57.119> I<00:43:57.240> will<00:43:57.359> go<00:43:57.540> to<00:43:57.660> my<00:43:57.900> Bravos<00:43:58.700> wide<00:43:59.700> in<00:44:00.000> here<00:44:00.180> I 00:44:00.470 --> 00:44:00.480 align:start position:0% so I will go to my Bravos wide in here I 00:44:00.480 --> 00:44:03.410 align:start position:0% so I will go to my Bravos wide in here I was<00:44:00.599> in<00:44:00.780> my<00:44:00.900> origin<00:44:01.260> before<00:44:01.440> and<00:44:02.099> let's<00:44:03.060> see<00:44:03.240> if 00:44:03.410 --> 00:44:03.420 align:start position:0% was in my origin before and let's see if 00:44:03.420 --> 00:44:06.290 align:start position:0% was in my origin before and let's see if it<00:44:03.540> allows<00:44:03.900> me<00:44:03.960> to<00:44:04.140> vote 00:44:06.290 --> 00:44:06.300 align:start position:0% it allows me to vote 00:44:06.300 --> 00:44:10.910 align:start position:0% it allows me to vote so<00:44:07.200> I<00:44:07.859> will<00:44:07.980> vote<00:44:08.160> with<00:44:08.460> that<00:44:08.700> one 00:44:10.910 --> 00:44:10.920 align:start position:0% so I will vote with that one 00:44:10.920 --> 00:44:12.710 align:start position:0% so I will vote with that one and<00:44:11.460> I<00:44:11.640> will<00:44:11.760> be<00:44:11.940> able<00:44:12.119> to<00:44:12.300> sign<00:44:12.480> this 00:44:12.710 --> 00:44:12.720 align:start position:0% and I will be able to sign this 00:44:12.720 --> 00:44:14.870 align:start position:0% and I will be able to sign this transaction<00:44:13.079> because<00:44:13.920> this<00:44:14.339> address<00:44:14.520> is 00:44:14.870 --> 00:44:14.880 align:start position:0% transaction because this address is 00:44:14.880 --> 00:44:16.309 align:start position:0% transaction because this address is registered<00:44:15.359> to<00:44:15.540> both 00:44:16.309 --> 00:44:16.319 align:start position:0% registered to both 00:44:16.319 --> 00:44:18.230 align:start position:0% registered to both I<00:44:16.740> did<00:44:16.980> when<00:44:17.160> I<00:44:17.280> deploy<00:44:17.579> it 00:44:18.230 --> 00:44:18.240 align:start position:0% I did when I deploy it 00:44:18.240 --> 00:44:21.230 align:start position:0% I did when I deploy it and<00:44:18.900> right<00:44:19.560> now<00:44:19.740> what<00:44:19.980> it<00:44:20.220> this<00:44:21.000> is<00:44:21.119> the 00:44:21.230 --> 00:44:21.240 align:start position:0% and right now what it this is the 00:44:21.240 --> 00:44:22.910 align:start position:0% and right now what it this is the transaction<00:44:21.480> hash<00:44:21.900> and<00:44:22.200> we<00:44:22.319> have<00:44:22.440> to<00:44:22.560> wait<00:44:22.740> for 00:44:22.910 --> 00:44:22.920 align:start position:0% transaction hash and we have to wait for 00:44:22.920 --> 00:44:24.589 align:start position:0% transaction hash and we have to wait for a<00:44:23.099> test<00:44:23.220> to<00:44:23.520> process<00:44:23.700> this<00:44:23.880> and<00:44:24.180> we<00:44:24.300> will<00:44:24.420> have 00:44:24.589 --> 00:44:24.599 align:start position:0% a test to process this and we will have 00:44:24.599 --> 00:44:25.970 align:start position:0% a test to process this and we will have our<00:44:24.900> bolts 00:44:25.970 --> 00:44:25.980 align:start position:0% our bolts 00:44:25.980 --> 00:44:28.550 align:start position:0% our bolts now<00:44:26.579> how<00:44:27.180> can<00:44:27.359> you<00:44:27.540> deploy<00:44:27.900> these<00:44:28.140> contracts 00:44:28.550 --> 00:44:28.560 align:start position:0% now how can you deploy these contracts 00:44:28.560 --> 00:44:30.470 align:start position:0% now how can you deploy these contracts you<00:44:28.920> can<00:44:29.040> deploy<00:44:29.339> it<00:44:29.460> using<00:44:29.819> the<00:44:30.000> command<00:44:30.359> line 00:44:30.470 --> 00:44:30.480 align:start position:0% you can deploy it using the command line 00:44:30.480 --> 00:44:33.410 align:start position:0% you can deploy it using the command line tools<00:44:31.020> by<00:44:31.200> its<00:44:31.380> targets<00:44:31.980> or<00:44:32.700> also<00:44:33.000> and<00:44:33.240> my 00:44:33.410 --> 00:44:33.420 align:start position:0% tools by its targets or also and my 00:44:33.420 --> 00:44:34.990 align:start position:0% tools by its targets or also and my preferred<00:44:33.780> ways<00:44:34.020> to<00:44:34.200> use<00:44:34.319> protostar 00:44:34.990 --> 00:44:35.000 align:start position:0% preferred ways to use protostar 00:44:35.000 --> 00:44:38.030 align:start position:0% preferred ways to use protostar protostar<00:44:36.000> is<00:44:36.240> a<00:44:36.420> tool<00:44:36.720> created<00:44:37.319> in<00:44:37.560> the<00:44:37.740> image 00:44:38.030 --> 00:44:38.040 align:start position:0% protostar is a tool created in the image 00:44:38.040 --> 00:44:39.250 align:start position:0% protostar is a tool created in the image of<00:44:38.220> Foundry 00:44:39.250 --> 00:44:39.260 align:start position:0% of Foundry 00:44:39.260 --> 00:44:41.690 align:start position:0% of Foundry it<00:44:40.260> has<00:44:40.380> the<00:44:40.560> best<00:44:40.680> practices<00:44:40.980> from<00:44:41.280> Foundry 00:44:41.690 --> 00:44:41.700 align:start position:0% it has the best practices from Foundry 00:44:41.700 --> 00:44:43.730 align:start position:0% it has the best practices from Foundry and<00:44:42.119> also<00:44:42.359> some<00:44:42.480> from<00:44:42.720> haircut<00:44:42.960> sorry<00:44:43.500> from 00:44:43.730 --> 00:44:43.740 align:start position:0% and also some from haircut sorry from 00:44:43.740 --> 00:44:45.530 align:start position:0% and also some from haircut sorry from profile<00:44:44.220> so<00:44:44.700> it's<00:44:44.819> very<00:44:44.940> interesting<00:44:45.300> it 00:44:45.530 --> 00:44:45.540 align:start position:0% profile so it's very interesting it 00:44:45.540 --> 00:44:48.770 align:start position:0% profile so it's very interesting it helped<00:44:45.839> us<00:44:45.900> to<00:44:46.140> to<00:44:46.440> test<00:44:47.099> but<00:44:47.400> also<00:44:47.700> to<00:44:47.819> deploy 00:44:48.770 --> 00:44:48.780 align:start position:0% helped us to to test but also to deploy 00:44:48.780 --> 00:44:54.290 align:start position:0% helped us to to test but also to deploy so<00:44:49.500> if<00:44:49.859> I<00:44:50.040> go<00:44:50.220> right<00:44:50.460> now<00:44:50.640> to<00:44:50.819> my<00:44:51.060> command<00:44:51.420> line 00:44:54.290 --> 00:44:54.300 align:start position:0% 00:44:54.300 --> 00:45:02.990 align:start position:0% [Music] 00:45:02.990 --> 00:45:03.000 align:start position:0% 00:45:03.000 --> 00:45:05.030 align:start position:0% this<00:45:03.660> is<00:45:03.780> how<00:45:04.020> deploying<00:45:04.560> this<00:45:04.740> contract 00:45:05.030 --> 00:45:05.040 align:start position:0% this is how deploying this contract 00:45:05.040 --> 00:45:07.069 align:start position:0% this is how deploying this contract looks<00:45:05.400> like<00:45:05.520> so<00:45:06.180> basically<00:45:06.480> I'm<00:45:06.720> saying 00:45:07.069 --> 00:45:07.079 align:start position:0% looks like so basically I'm saying 00:45:07.079 --> 00:45:10.130 align:start position:0% looks like so basically I'm saying entering<00:45:07.619> protostar<00:45:08.160> deploy<00:45:08.720> this<00:45:09.720> a 00:45:10.130 --> 00:45:10.140 align:start position:0% entering protostar deploy this a 00:45:10.140 --> 00:45:11.809 align:start position:0% entering protostar deploy this a contract<00:45:10.560> that<00:45:10.800> is<00:45:10.920> already<00:45:11.040> compiled<00:45:11.700> by 00:45:11.809 --> 00:45:11.819 align:start position:0% contract that is already compiled by 00:45:11.819 --> 00:45:13.849 align:start position:0% contract that is already compiled by this<00:45:12.000> moment<00:45:12.240> and<00:45:13.079> what<00:45:13.319> I<00:45:13.440> want<00:45:13.560> you<00:45:13.740> to 00:45:13.849 --> 00:45:13.859 align:start position:0% this moment and what I want you to 00:45:13.859 --> 00:45:16.730 align:start position:0% this moment and what I want you to notice<00:45:14.160> here<00:45:14.520> is<00:45:14.760> the<00:45:14.880> part<00:45:15.060> of<00:45:15.240> the<00:45:15.359> inputs 00:45:16.730 --> 00:45:16.740 align:start position:0% notice here is the part of the inputs 00:45:16.740 --> 00:45:18.650 align:start position:0% notice here is the part of the inputs it<00:45:16.980> took<00:45:17.220> before<00:45:17.400> about<00:45:17.640> the<00:45:17.880> Constructor<00:45:18.240> a 00:45:18.650 --> 00:45:18.660 align:start position:0% it took before about the Constructor a 00:45:18.660 --> 00:45:21.470 align:start position:0% it took before about the Constructor a setting<00:45:19.140> for<00:45:19.500> three<00:45:19.980> different<00:45:20.099> inputs<00:45:20.819> first 00:45:21.470 --> 00:45:21.480 align:start position:0% setting for three different inputs first 00:45:21.480 --> 00:45:23.750 align:start position:0% setting for three different inputs first one<00:45:21.720> is<00:45:21.960> the<00:45:22.200> owner<00:45:22.560> the<00:45:22.980> admin<00:45:23.339> of<00:45:23.579> this 00:45:23.750 --> 00:45:23.760 align:start position:0% one is the owner the admin of this 00:45:23.760 --> 00:45:26.450 align:start position:0% one is the owner the admin of this voting<00:45:24.180> second<00:45:24.960> is<00:45:25.440> the<00:45:25.560> number<00:45:25.680> of<00:45:25.859> persons 00:45:26.450 --> 00:45:26.460 align:start position:0% voting second is the number of persons 00:45:26.460 --> 00:45:29.150 align:start position:0% voting second is the number of persons of<00:45:26.640> register<00:45:27.060> addresses<00:45:27.660> that<00:45:28.020> can<00:45:28.200> vote<00:45:28.380> and 00:45:29.150 --> 00:45:29.160 align:start position:0% of register addresses that can vote and 00:45:29.160 --> 00:45:31.730 align:start position:0% of register addresses that can vote and finally<00:45:29.460> the<00:45:29.760> actual<00:45:30.060> addresses<00:45:30.960> so<00:45:31.500> this<00:45:31.619> is 00:45:31.730 --> 00:45:31.740 align:start position:0% finally the actual addresses so this is 00:45:31.740 --> 00:45:34.309 align:start position:0% finally the actual addresses so this is how<00:45:31.920> they<00:45:32.099> look<00:45:32.339> this<00:45:33.060> one<00:45:33.300> as<00:45:33.839> you<00:45:33.960> can<00:45:34.079> see<00:45:34.140> is 00:45:34.309 --> 00:45:34.319 align:start position:0% how they look this one as you can see is 00:45:34.319 --> 00:45:36.589 align:start position:0% how they look this one as you can see is a<00:45:34.440> hexa<00:45:34.859> a<00:45:35.099> hexa<00:45:35.760> value<00:45:35.880> and<00:45:36.300> this<00:45:36.420> is<00:45:36.480> the 00:45:36.589 --> 00:45:36.599 align:start position:0% a hexa a hexa value and this is the 00:45:36.599 --> 00:45:38.030 align:start position:0% a hexa a hexa value and this is the address<00:45:36.720> that<00:45:37.140> is<00:45:37.260> the<00:45:37.380> owner<00:45:37.680> of<00:45:37.859> this 00:45:38.030 --> 00:45:38.040 align:start position:0% address that is the owner of this 00:45:38.040 --> 00:45:40.790 align:start position:0% address that is the owner of this contract<00:45:38.880> then<00:45:39.480> only<00:45:39.839> one<00:45:40.140> person<00:45:40.319> or<00:45:40.680> one 00:45:40.790 --> 00:45:40.800 align:start position:0% contract then only one person or one 00:45:40.800 --> 00:45:42.290 align:start position:0% contract then only one person or one address<00:45:40.980> can<00:45:41.339> vote 00:45:42.290 --> 00:45:42.300 align:start position:0% address can vote 00:45:42.300 --> 00:45:43.490 align:start position:0% address can vote this<00:45:42.780> one 00:45:43.490 --> 00:45:43.500 align:start position:0% this one 00:45:43.500 --> 00:45:46.370 align:start position:0% this one and<00:45:44.099> we<00:45:44.400> can<00:45:44.520> simply<00:45:44.760> deploy<00:45:45.119> it<00:45:45.300> run<00:45:46.020> it<00:45:46.200> like 00:45:46.370 --> 00:45:46.380 align:start position:0% and we can simply deploy it run it like 00:45:46.380 --> 00:45:47.569 align:start position:0% and we can simply deploy it run it like like<00:45:46.740> this 00:45:47.569 --> 00:45:47.579 align:start position:0% like this 00:45:47.579 --> 00:45:49.130 align:start position:0% like this photo<00:45:47.880> store<00:45:48.180> is<00:45:48.359> very<00:45:48.480> good<00:45:48.660> it's<00:45:48.960> very 00:45:49.130 --> 00:45:49.140 align:start position:0% photo store is very good it's very 00:45:49.140 --> 00:45:51.109 align:start position:0% photo store is very good it's very usable<00:45:49.560> it<00:45:50.220> has<00:45:50.339> amazing<00:45:50.760> testing 00:45:51.109 --> 00:45:51.119 align:start position:0% usable it has amazing testing 00:45:51.119 --> 00:45:52.849 align:start position:0% usable it has amazing testing functionalities<00:45:51.660> but<00:45:52.020> you<00:45:52.200> can<00:45:52.319> also<00:45:52.500> deploy 00:45:52.849 --> 00:45:52.859 align:start position:0% functionalities but you can also deploy 00:45:52.859 --> 00:45:54.829 align:start position:0% functionalities but you can also deploy your<00:45:53.040> contracts<00:45:53.520> and<00:45:54.119> that<00:45:54.300> is<00:45:54.420> simply<00:45:54.660> the 00:45:54.829 --> 00:45:54.839 align:start position:0% your contracts and that is simply the 00:45:54.839 --> 00:45:56.630 align:start position:0% your contracts and that is simply the content<00:45:55.140> that<00:45:55.260> we<00:45:55.380> deploy<00:45:55.680> here 00:45:56.630 --> 00:45:56.640 align:start position:0% content that we deploy here 00:45:56.640 --> 00:45:58.849 align:start position:0% content that we deploy here and<00:45:57.180> as<00:45:57.480> we<00:45:57.660> as<00:45:58.140> we<00:45:58.260> can<00:45:58.319> see<00:45:58.440> we<00:45:58.680> already 00:45:58.849 --> 00:45:58.859 align:start position:0% and as we as we can see we already 00:45:58.859 --> 00:46:02.210 align:start position:0% and as we as we can see we already bought<00:45:59.220> it<00:45:59.940> if<00:46:00.359> I<00:46:00.540> go<00:46:00.599> to<00:46:00.720> read<00:46:00.960> contracts<00:46:01.619> we 00:46:02.210 --> 00:46:02.220 align:start position:0% bought it if I go to read contracts we 00:46:02.220 --> 00:46:04.130 align:start position:0% bought it if I go to read contracts we should<00:46:02.400> get 00:46:04.130 --> 00:46:04.140 align:start position:0% should get 00:46:04.140 --> 00:46:06.410 align:start position:0% should get a<00:46:04.740> boat<00:46:04.920> in<00:46:05.099> status<00:46:05.339> where<00:46:05.760> we<00:46:06.000> had<00:46:06.119> a<00:46:06.240> boat 00:46:06.410 --> 00:46:06.420 align:start position:0% a boat in status where we had a boat 00:46:06.420 --> 00:46:08.990 align:start position:0% a boat in status where we had a boat with<00:46:06.660> yes<00:46:06.839> we're<00:46:07.319> number<00:46:07.619> one<00:46:07.740> it<00:46:07.980> updated<00:46:08.400> and 00:46:08.990 --> 00:46:09.000 align:start position:0% with yes we're number one it updated and 00:46:09.000 --> 00:46:11.809 align:start position:0% with yes we're number one it updated and zero<00:46:09.359> is<00:46:09.480> still<00:46:09.660> no<00:46:09.960> I<00:46:10.440> could<00:46:10.619> note<00:46:11.280> both<00:46:11.520> again 00:46:11.809 --> 00:46:11.819 align:start position:0% zero is still no I could note both again 00:46:11.819 --> 00:46:13.010 align:start position:0% zero is still no I could note both again because 00:46:13.010 --> 00:46:13.020 align:start position:0% because 00:46:13.020 --> 00:46:15.770 align:start position:0% because uh<00:46:13.920> directly<00:46:14.640> theoretically<00:46:15.240> I<00:46:15.480> should<00:46:15.660> not 00:46:15.770 --> 00:46:15.780 align:start position:0% uh directly theoretically I should not 00:46:15.780 --> 00:46:17.329 align:start position:0% uh directly theoretically I should not be<00:46:15.900> able<00:46:16.020> to<00:46:16.140> vote<00:46:16.440> again 00:46:17.329 --> 00:46:17.339 align:start position:0% be able to vote again 00:46:17.339 --> 00:46:23.809 align:start position:0% be able to vote again let's<00:46:17.819> see<00:46:18.000> what<00:46:18.300> happens 00:46:23.809 --> 00:46:23.819 align:start position:0% 00:46:23.819 --> 00:46:25.490 align:start position:0% oh<00:46:24.119> it<00:46:24.420> should<00:46:24.540> be<00:46:24.660> it<00:46:24.839> should<00:46:25.020> it<00:46:25.200> shouldn't 00:46:25.490 --> 00:46:25.500 align:start position:0% oh it should be it should it shouldn't 00:46:25.500 --> 00:46:27.890 align:start position:0% oh it should be it should it shouldn't pass<00:46:25.619> right<00:46:25.859> now<00:46:26.040> but<00:46:26.400> let's<00:46:26.640> wait<00:46:26.880> for<00:46:27.060> it 00:46:27.890 --> 00:46:27.900 align:start position:0% pass right now but let's wait for it 00:46:27.900 --> 00:46:30.290 align:start position:0% pass right now but let's wait for it so<00:46:28.319> that<00:46:28.500> would<00:46:28.680> be<00:46:28.800> the<00:46:28.980> the<00:46:29.339> main<00:46:30.000> part<00:46:30.240> of 00:46:30.290 --> 00:46:30.300 align:start position:0% so that would be the the main part of 00:46:30.300 --> 00:46:32.270 align:start position:0% so that would be the the main part of the<00:46:30.420> workshop<00:46:30.720> you<00:46:31.020> we<00:46:31.440> have<00:46:31.680> three<00:46:32.040> minutes 00:46:32.270 --> 00:46:32.280 align:start position:0% the workshop you we have three minutes 00:46:32.280 --> 00:46:35.150 align:start position:0% the workshop you we have three minutes two<00:46:32.819> more<00:46:33.000> questions 00:46:35.150 --> 00:46:35.160 align:start position:0% two more questions 00:46:35.160 --> 00:46:36.900 align:start position:0% two more questions yes 00:46:36.900 --> 00:46:36.910 align:start position:0% yes 00:46:36.910 --> 00:46:40.809 align:start position:0% yes [Music] 00:46:40.809 --> 00:46:40.819 align:start position:0% 00:46:40.819 --> 00:46:44.690 align:start position:0% the<00:46:41.819> implicit<00:46:42.500> right<00:46:43.500> now<00:46:43.859> here<00:46:44.099> I<00:46:44.400> don't<00:46:44.520> have 00:46:44.690 --> 00:46:44.700 align:start position:0% the implicit right now here I don't have 00:46:44.700 --> 00:46:46.550 align:start position:0% the implicit right now here I don't have any<00:46:44.819> but<00:46:45.119> they<00:46:45.480> can<00:46:45.900> change<00:46:46.020> depending<00:46:46.560> on 00:46:46.550 --> 00:46:46.560 align:start position:0% any but they can change depending on 00:46:46.560 --> 00:46:51.430 align:start position:0% any but they can change depending on what<00:46:46.800> you're<00:46:46.920> building 00:46:51.430 --> 00:46:51.440 align:start position:0% 00:46:51.440 --> 00:46:53.990 align:start position:0% can<00:46:52.440> you<00:46:52.560> think<00:46:52.680> of<00:46:52.800> a<00:46:52.980> scenario<00:46:53.280> and<00:46:53.579> when<00:46:53.880> do 00:46:53.990 --> 00:46:54.000 align:start position:0% can you think of a scenario and when do 00:46:54.000 --> 00:46:57.410 align:start position:0% can you think of a scenario and when do implicit<00:46:54.480> arguments<00:46:54.960> change 00:46:57.410 --> 00:46:57.420 align:start position:0% 00:46:57.420 --> 00:46:59.750 align:start position:0% every<00:46:58.079> time<00:46:58.260> they're<00:46:58.500> used<00:46:58.740> basically 00:46:59.750 --> 00:46:59.760 align:start position:0% every time they're used basically 00:46:59.760 --> 00:47:01.309 align:start position:0% every time they're used basically um<00:46:59.819> it's<00:47:00.180> a<00:47:00.240> it's<00:47:00.480> a<00:47:00.599> bit<00:47:00.660> of<00:47:00.780> a<00:47:00.900> deep<00:47:01.020> question 00:47:01.309 --> 00:47:01.319 align:start position:0% um it's a it's a bit of a deep question 00:47:01.319 --> 00:47:03.470 align:start position:0% um it's a it's a bit of a deep question the<00:47:02.099> workshop<00:47:02.400> is<00:47:02.579> about<00:47:02.700> to<00:47:02.940> finish<00:47:03.060> so<00:47:03.300> if 00:47:03.470 --> 00:47:03.480 align:start position:0% the workshop is about to finish so if 00:47:03.480 --> 00:47:04.790 align:start position:0% the workshop is about to finish so if you<00:47:03.599> want<00:47:03.660> let's<00:47:03.780> meet<00:47:03.960> outside<00:47:04.200> and<00:47:04.619> we'll 00:47:04.790 --> 00:47:04.800 align:start position:0% you want let's meet outside and we'll 00:47:04.800 --> 00:47:06.710 align:start position:0% you want let's meet outside and we'll we'll<00:47:04.980> give<00:47:05.220> you<00:47:05.339> a<00:47:05.579> a<00:47:05.880> more<00:47:06.300> definitive 00:47:06.710 --> 00:47:06.720 align:start position:0% we'll give you a a more definitive 00:47:06.720 --> 00:47:09.109 align:start position:0% we'll give you a a more definitive answer 00:47:09.109 --> 00:47:09.119 align:start position:0% 00:47:09.119 --> 00:47:12.290 align:start position:0% yes 00:47:12.290 --> 00:47:12.300 align:start position:0% 00:47:12.300 --> 00:47:15.890 align:start position:0% I<00:47:13.200> think<00:47:13.319> I<00:47:13.500> have<00:47:13.680> another<00:47:13.859> message<00:47:14.220> here 00:47:15.890 --> 00:47:15.900 align:start position:0% I think I have another message here 00:47:15.900 --> 00:47:18.230 align:start position:0% I think I have another message here hey<00:47:16.560> will<00:47:17.040> I<00:47:17.160> look<00:47:17.339> for<00:47:17.520> it<00:47:17.700> any<00:47:18.060> other 00:47:18.230 --> 00:47:18.240 align:start position:0% hey will I look for it any other 00:47:18.240 --> 00:47:20.270 align:start position:0% hey will I look for it any other question<00:47:18.480> in<00:47:18.900> the<00:47:18.960> meantime<00:47:19.319> I<00:47:20.040> have<00:47:20.160> a 00:47:20.270 --> 00:47:20.280 align:start position:0% question in the meantime I have a 00:47:20.280 --> 00:47:22.190 align:start position:0% question in the meantime I have a question<00:47:20.400> for<00:47:20.700> the<00:47:20.880> audience<00:47:21.180> before<00:47:21.599> we<00:47:21.900> wrap 00:47:22.190 --> 00:47:22.200 align:start position:0% question for the audience before we wrap 00:47:22.200 --> 00:47:24.589 align:start position:0% question for the audience before we wrap the<00:47:22.560> the<00:47:22.859> workshop<00:47:23.400> up<00:47:23.579> can<00:47:23.880> we<00:47:24.060> get<00:47:24.180> just<00:47:24.420> get 00:47:24.589 --> 00:47:24.599 align:start position:0% the the workshop up can we get just get 00:47:24.599 --> 00:47:26.450 align:start position:0% the the workshop up can we get just get a<00:47:24.780> quick<00:47:24.960> show<00:47:25.140> of<00:47:25.380> hand<00:47:25.619> who<00:47:26.099> learned 00:47:26.450 --> 00:47:26.460 align:start position:0% a quick show of hand who learned 00:47:26.460 --> 00:47:28.970 align:start position:0% a quick show of hand who learned something<00:47:26.579> during<00:47:26.940> the<00:47:27.180> workshop 00:47:28.970 --> 00:47:28.980 align:start position:0% something during the workshop 00:47:28.980 --> 00:47:32.750 align:start position:0% something during the workshop cool<00:47:29.460> who<00:47:30.060> thought<00:47:30.300> this<00:47:30.660> was<00:47:30.839> too<00:47:31.140> difficult 00:47:32.750 --> 00:47:32.760 align:start position:0% cool who thought this was too difficult 00:47:32.760 --> 00:47:36.950 align:start position:0% cool who thought this was too difficult who<00:47:33.300> thought<00:47:33.480> this<00:47:33.780> was<00:47:33.960> too<00:47:34.260> easy 00:47:36.950 --> 00:47:36.960 align:start position:0% 00:47:36.960 --> 00:47:39.650 align:start position:0% okay<00:47:37.380> fine<00:47:37.800> so<00:47:38.400> it's<00:47:38.819> great<00:47:39.119> this<00:47:39.300> means<00:47:39.540> this 00:47:39.650 --> 00:47:39.660 align:start position:0% okay fine so it's great this means this 00:47:39.660 --> 00:47:41.809 align:start position:0% okay fine so it's great this means this was<00:47:39.839> spot<00:47:40.020> on<00:47:40.260> those<00:47:40.680> of<00:47:40.859> you<00:47:40.980> still<00:47:41.339> are 00:47:41.809 --> 00:47:41.819 align:start position:0% was spot on those of you still are 00:47:41.819 --> 00:47:44.930 align:start position:0% was spot on those of you still are hungry<00:47:42.240> don't<00:47:42.780> estate<00:47:43.020> ask<00:47:43.500> us<00:47:43.680> question<00:47:43.980> come 00:47:44.930 --> 00:47:44.940 align:start position:0% hungry don't estate ask us question come 00:47:44.940 --> 00:47:47.750 align:start position:0% hungry don't estate ask us question come on<00:47:45.119> our<00:47:45.240> Discord<00:47:45.720> go<00:47:46.260> on<00:47:46.440> our<00:47:46.560> resources<00:47:47.040> look 00:47:47.750 --> 00:47:47.760 align:start position:0% on our Discord go on our resources look 00:47:47.760 --> 00:47:50.750 align:start position:0% on our Discord go on our resources look at<00:47:47.940> what<00:47:48.180> we<00:47:48.300> do<00:47:48.480> as<00:47:49.319> also<00:47:49.800> as<00:47:50.040> Omar<00:47:50.400> mentioned 00:47:50.750 --> 00:47:50.760 align:start position:0% at what we do as also as Omar mentioned 00:47:50.760 --> 00:47:52.790 align:start position:0% at what we do as also as Omar mentioned like<00:47:51.000> most<00:47:51.359> of<00:47:51.540> these<00:47:51.780> things<00:47:51.960> the<00:47:52.260> Paradigm 00:47:52.790 --> 00:47:52.800 align:start position:0% like most of these things the Paradigm 00:47:52.800 --> 00:47:55.370 align:start position:0% like most of these things the Paradigm you're<00:47:53.520> used<00:47:53.819> to<00:47:54.000> that<00:47:54.180> you're<00:47:54.720> used<00:47:54.960> to<00:47:55.200> how 00:47:55.370 --> 00:47:55.380 align:start position:0% you're used to that you're used to how 00:47:55.380 --> 00:47:57.109 align:start position:0% you're used to that you're used to how you<00:47:55.560> write<00:47:55.680> smart<00:47:55.980> contracts<00:47:56.520> how<00:47:56.819> you<00:47:56.940> deal 00:47:57.109 --> 00:47:57.119 align:start position:0% you write smart contracts how you deal 00:47:57.119 --> 00:47:59.390 align:start position:0% you write smart contracts how you deal with<00:47:57.359> Scholars<00:47:57.960> and<00:47:58.079> stuff<00:47:58.319> like<00:47:58.500> that<00:47:58.680> this 00:47:59.390 --> 00:47:59.400 align:start position:0% with Scholars and stuff like that this 00:47:59.400 --> 00:48:01.069 align:start position:0% with Scholars and stuff like that this syntax<00:47:59.760> is<00:47:59.940> a<00:48:00.060> bit<00:48:00.180> different<00:48:00.300> the<00:48:00.599> tooling<00:48:00.960> is 00:48:01.069 --> 00:48:01.079 align:start position:0% syntax is a bit different the tooling is 00:48:01.079 --> 00:48:03.170 align:start position:0% syntax is a bit different the tooling is a<00:48:01.200> bit<00:48:01.319> different<00:48:01.500> but<00:48:02.160> you<00:48:02.400> can<00:48:02.579> and<00:48:02.940> will 00:48:03.170 --> 00:48:03.180 align:start position:0% a bit different but you can and will 00:48:03.180 --> 00:48:05.630 align:start position:0% a bit different but you can and will Master<00:48:03.480> Cairo<00:48:04.200> it's<00:48:04.619> just<00:48:04.800> a<00:48:04.980> matter<00:48:05.099> of<00:48:05.280> just 00:48:05.630 --> 00:48:05.640 align:start position:0% Master Cairo it's just a matter of just 00:48:05.640 --> 00:48:08.930 align:start position:0% Master Cairo it's just a matter of just like<00:48:06.180> trying<00:48:06.480> and<00:48:07.440> this<00:48:07.859> will<00:48:08.099> give<00:48:08.280> this<00:48:08.640> tool 00:48:08.930 --> 00:48:08.940 align:start position:0% like trying and this will give this tool 00:48:08.940 --> 00:48:11.089 align:start position:0% like trying and this will give this tool will<00:48:09.119> give<00:48:09.359> you<00:48:09.540> extreme<00:48:10.440> power<00:48:10.680> in<00:48:10.980> your 00:48:11.089 --> 00:48:11.099 align:start position:0% will give you extreme power in your 00:48:11.099 --> 00:48:13.190 align:start position:0% will give you extreme power in your blockchain<00:48:11.460> applications<00:48:11.940> so<00:48:12.780> if<00:48:13.079> you're 00:48:13.190 --> 00:48:13.200 align:start position:0% blockchain applications so if you're 00:48:13.200 --> 00:48:15.770 align:start position:0% blockchain applications so if you're looking<00:48:13.440> to<00:48:13.800> go<00:48:13.980> more<00:48:14.339> to<00:48:15.000> do<00:48:15.240> more<00:48:15.420> and<00:48:15.660> go 00:48:15.770 --> 00:48:15.780 align:start position:0% looking to go more to do more and go 00:48:15.780 --> 00:48:17.870 align:start position:0% looking to go more to do more and go beyond<00:48:16.140> what<00:48:16.319> you<00:48:16.440> can<00:48:16.500> do<00:48:16.619> with<00:48:16.740> the<00:48:16.859> evm<00:48:17.339> I 00:48:17.870 --> 00:48:17.880 align:start position:0% beyond what you can do with the evm I 00:48:17.880 --> 00:48:20.390 align:start position:0% beyond what you can do with the evm I invite<00:48:18.180> you<00:48:18.300> like<00:48:18.660> do<00:48:19.319> take<00:48:19.619> a<00:48:19.740> look<00:48:19.859> it<00:48:20.160> really 00:48:20.390 --> 00:48:20.400 align:start position:0% invite you like do take a look it really 00:48:20.400 --> 00:48:22.490 align:start position:0% invite you like do take a look it really is<00:48:20.579> powerful<00:48:21.000> and<00:48:21.180> will<00:48:21.359> let<00:48:21.599> you<00:48:21.720> build<00:48:22.260> super 00:48:22.490 --> 00:48:22.500 align:start position:0% is powerful and will let you build super 00:48:22.500 --> 00:48:25.250 align:start position:0% is powerful and will let you build super cool<00:48:22.740> stuff<00:48:22.980> and<00:48:23.640> again<00:48:23.819> this<00:48:24.180> is<00:48:24.300> the<00:48:24.599> QR<00:48:25.020> to 00:48:25.250 --> 00:48:25.260 align:start position:0% cool stuff and again this is the QR to 00:48:25.260 --> 00:48:27.290 align:start position:0% cool stuff and again this is the QR to the<00:48:25.380> educational<00:48:25.680> resources<00:48:26.339> you<00:48:26.819> want<00:48:27.000> to<00:48:27.119> go 00:48:27.290 --> 00:48:27.300 align:start position:0% the educational resources you want to go 00:48:27.300 --> 00:48:29.870 align:start position:0% the educational resources you want to go look<00:48:27.660> at<00:48:27.839> them<00:48:28.020> we'll<00:48:28.680> have<00:48:28.920> a<00:48:29.160> boots<00:48:29.520> on 00:48:29.870 --> 00:48:29.880 align:start position:0% look at them we'll have a boots on 00:48:29.880 --> 00:48:31.670 align:start position:0% look at them we'll have a boots on Thursday<00:48:30.000> and<00:48:30.359> Friday<00:48:30.540> you<00:48:30.900> can<00:48:31.020> ask<00:48:31.500> ask<00:48:31.500> any 00:48:31.670 --> 00:48:31.680 align:start position:0% Thursday and Friday you can ask ask any 00:48:31.680 --> 00:48:33.230 align:start position:0% Thursday and Friday you can ask ask any question<00:48:31.859> come<00:48:32.220> with<00:48:32.400> us 00:48:33.230 --> 00:48:33.240 align:start position:0% question come with us 00:48:33.240 --> 00:48:35.809 align:start position:0% question come with us and<00:48:33.839> finally<00:48:34.140> regarding<00:48:34.800> the<00:48:34.920> question<00:48:35.220> the 00:48:35.809 --> 00:48:35.819 align:start position:0% and finally regarding the question the 00:48:35.819 --> 00:48:39.170 align:start position:0% and finally regarding the question the the<00:48:36.000> error<00:48:36.359> messages<00:48:36.540> this<00:48:37.079> is<00:48:37.200> how<00:48:37.319> they<00:48:37.500> look 00:48:39.170 --> 00:48:39.180 align:start position:0% the error messages this is how they look 00:48:39.180 --> 00:48:42.349 align:start position:0% the error messages this is how they look so<00:48:39.660> if<00:48:39.900> this<00:48:40.079> assertion<00:48:40.619> true<00:48:41.160> or<00:48:41.339> false 00:48:42.349 --> 00:48:42.359 align:start position:0% so if this assertion true or false 00:48:42.359 --> 00:48:45.950 align:start position:0% so if this assertion true or false fails<00:48:43.140> then<00:48:43.740> it<00:48:43.980> will<00:48:44.099> print<00:48:44.400> this<00:48:44.819> mistake 00:48:45.950 --> 00:48:45.960 align:start position:0% fails then it will print this mistake 00:48:45.960 --> 00:48:48.230 align:start position:0% fails then it will print this mistake motor<00:48:46.319> info 00:48:48.230 --> 00:48:48.240 align:start position:0% motor info 00:48:48.240 --> 00:48:55.790 align:start position:0% motor info well<00:48:48.660> thank<00:48:49.079> you<00:48:49.200> thank<00:48:49.500> you<00:48:49.619> very<00:48:49.680> much 00:48:55.790 --> 00:48:55.800 align:start position:0% 00:48:55.800 --> 00:48:59.329 align:start position:0% well<00:48:56.099> it<00:48:56.339> depends<00:48:56.700> on<00:48:56.940> the<00:48:57.240> on<00:48:57.900> the<00:48:58.079> wallet<00:48:58.440> uh 00:48:59.329 --> 00:48:59.339 align:start position:0% well it depends on the on the wallet uh 00:48:59.339 --> 00:49:01.069 align:start position:0% well it depends on the on the wallet uh let's<00:48:59.520> see<00:48:59.700> for<00:48:59.880> example<00:49:00.119> this<00:49:00.480> case<00:49:00.720> a 00:49:01.069 --> 00:49:01.079 align:start position:0% let's see for example this case a 00:49:01.079 --> 00:49:03.829 align:start position:0% let's see for example this case a certain<00:49:01.319> Lounge 00:49:03.829 --> 00:49:03.839 align:start position:0% certain Lounge 00:49:03.839 --> 00:49:05.809 align:start position:0% certain Lounge yeah<00:49:04.260> so<00:49:04.440> what<00:49:04.680> your<00:49:05.040> question<00:49:05.160> is<00:49:05.400> what<00:49:05.640> does 00:49:05.809 --> 00:49:05.819 align:start position:0% yeah so what your question is what does 00:49:05.819 --> 00:49:07.490 align:start position:0% yeah so what your question is what does a<00:49:06.000> narrower<00:49:06.300> message<00:49:06.540> look<00:49:06.960> like<00:49:07.079> from<00:49:07.380> the 00:49:07.490 --> 00:49:07.500 align:start position:0% a narrower message look like from the 00:49:07.500 --> 00:49:09.770 align:start position:0% a narrower message look like from the browser<00:49:07.859> perspective<00:49:08.540> essentially<00:49:09.540> you'll 00:49:09.770 --> 00:49:09.780 align:start position:0% browser perspective essentially you'll 00:49:09.780 --> 00:49:11.630 align:start position:0% browser perspective essentially you'll get<00:49:09.960> a<00:49:10.140> failed<00:49:10.560> transaction<00:49:10.859> like<00:49:11.160> you<00:49:11.339> do<00:49:11.460> on 00:49:11.630 --> 00:49:11.640 align:start position:0% get a failed transaction like you do on 00:49:11.640 --> 00:49:14.750 align:start position:0% get a failed transaction like you do on ethereum<00:49:12.060> and<00:49:12.960> the<00:49:13.500> trace<00:49:13.800> like<00:49:14.220> the<00:49:14.400> way<00:49:14.579> it 00:49:14.750 --> 00:49:14.760 align:start position:0% ethereum and the trace like the way it 00:49:14.760 --> 00:49:16.790 align:start position:0% ethereum and the trace like the way it shows<00:49:15.060> up<00:49:15.180> is<00:49:15.599> kind<00:49:15.839> of<00:49:16.020> ugly<00:49:16.200> to<00:49:16.440> be<00:49:16.560> honest 00:49:16.790 --> 00:49:16.800 align:start position:0% shows up is kind of ugly to be honest 00:49:16.800 --> 00:49:18.589 align:start position:0% shows up is kind of ugly to be honest it's<00:49:17.339> still<00:49:17.520> very<00:49:17.700> rough<00:49:17.940> around<00:49:18.119> the<00:49:18.359> edges 00:49:18.589 --> 00:49:18.599 align:start position:0% it's still very rough around the edges 00:49:18.599 --> 00:49:20.030 align:start position:0% it's still very rough around the edges there's<00:49:18.839> a<00:49:19.020> lot<00:49:19.140> of<00:49:19.260> info<00:49:19.560> that<00:49:19.680> is<00:49:19.859> not 00:49:20.030 --> 00:49:20.040 align:start position:0% there's a lot of info that is not 00:49:20.040 --> 00:49:21.290 align:start position:0% there's a lot of info that is not necessarily<00:49:20.400> relevant<00:49:20.700> to<00:49:20.819> you<00:49:20.940> but<00:49:21.180> the 00:49:21.290 --> 00:49:21.300 align:start position:0% necessarily relevant to you but the 00:49:21.300 --> 00:49:22.970 align:start position:0% necessarily relevant to you but the message<00:49:21.480> the<00:49:21.900> error<00:49:22.200> message<00:49:22.440> will<00:49:22.740> appear 00:49:22.970 --> 00:49:22.980 align:start position:0% message the error message will appear 00:49:22.980 --> 00:49:24.410 align:start position:0% message the error message will appear somewhere<00:49:23.339> and<00:49:23.520> you'll<00:49:23.700> be<00:49:23.819> you<00:49:23.940> know<00:49:24.000> able<00:49:24.359> to 00:49:24.410 --> 00:49:24.420 align:start position:0% somewhere and you'll be you know able to 00:49:24.420 --> 00:49:26.450 align:start position:0% somewhere and you'll be you know able to know<00:49:24.599> where<00:49:24.780> the<00:49:24.900> error<00:49:25.200> is<00:49:25.440> from 00:49:26.450 --> 00:49:26.460 align:start position:0% know where the error is from 00:49:26.460 --> 00:49:29.569 align:start position:0% know where the error is from in<00:49:27.240> general<00:49:27.480> this<00:49:28.380> thing<00:49:28.560> works<00:49:29.040> and<00:49:29.339> this 00:49:29.569 --> 00:49:29.579 align:start position:0% in general this thing works and this 00:49:29.579 --> 00:49:31.550 align:start position:0% in general this thing works and this feels<00:49:29.940> scale<00:49:30.180> this<00:49:30.599> thing<00:49:30.720> scales<00:49:31.200> ethereum 00:49:31.550 --> 00:49:31.560 align:start position:0% feels scale this thing scales ethereum 00:49:31.560 --> 00:49:33.349 align:start position:0% feels scale this thing scales ethereum right<00:49:31.859> now<00:49:31.980> it's<00:49:32.460> a<00:49:32.640> bit<00:49:32.760> rough<00:49:32.880> around<00:49:33.119> the 00:49:33.349 --> 00:49:33.359 align:start position:0% right now it's a bit rough around the 00:49:33.359 --> 00:49:35.210 align:start position:0% right now it's a bit rough around the edges<00:49:33.660> meaning<00:49:34.140> that<00:49:34.440> it's<00:49:34.619> not<00:49:34.859> all<00:49:34.980> pretty 00:49:35.210 --> 00:49:35.220 align:start position:0% edges meaning that it's not all pretty 00:49:35.220 --> 00:49:38.089 align:start position:0% edges meaning that it's not all pretty there's<00:49:35.520> a<00:49:35.700> lot<00:49:35.760> of<00:49:35.880> info<00:49:36.300> or<00:49:36.599> not<00:49:36.780> enough<00:49:37.099> but 00:49:38.089 --> 00:49:38.099 align:start position:0% there's a lot of info or not enough but 00:49:38.099 --> 00:49:40.370 align:start position:0% there's a lot of info or not enough but uh<00:49:38.520> but<00:49:38.760> it<00:49:38.880> works<00:49:39.240> and<00:49:39.599> that's<00:49:39.839> cool<00:49:40.020> that's 00:49:40.370 --> 00:49:40.380 align:start position:0% uh but it works and that's cool that's 00:49:40.380 --> 00:49:42.109 align:start position:0% uh but it works and that's cool that's cool<00:49:40.619> though 00:49:42.109 --> 00:49:42.119 align:start position:0% cool though 00:49:42.119 --> 00:49:44.870 align:start position:0% cool though this<00:49:42.359> is<00:49:42.599> how<00:49:42.660> the<00:49:42.780> error<00:49:43.020> looks<00:49:43.260> like 00:49:44.870 --> 00:49:44.880 align:start position:0% this is how the error looks like 00:49:44.880 --> 00:49:46.670 align:start position:0% this is how the error looks like as<00:49:45.180> you<00:49:45.359> can<00:49:45.480> see<00:49:45.599> that's<00:49:45.780> the<00:49:46.079> message<00:49:46.380> that 00:49:46.670 --> 00:49:46.680 align:start position:0% as you can see that's the message that 00:49:46.680 --> 00:49:49.190 align:start position:0% as you can see that's the message that we<00:49:46.859> saw<00:49:47.040> before<00:49:47.220> in<00:49:47.640> there 00:49:49.190 --> 00:49:49.200 align:start position:0% we saw before in there 00:49:49.200 --> 00:49:51.170 align:start position:0% we saw before in there yeah<00:49:49.440> explore<00:49:49.980> info<00:49:50.339> your<00:49:50.579> address<00:49:50.760> is<00:49:51.060> not 00:49:51.170 --> 00:49:51.180 align:start position:0% yeah explore info your address is not 00:49:51.180 --> 00:49:52.849 align:start position:0% yeah explore info your address is not allowed<00:49:51.480> to<00:49:51.540> boot 00:49:52.849 --> 00:49:52.859 align:start position:0% allowed to boot 00:49:52.859 --> 00:49:54.770 align:start position:0% allowed to boot then<00:49:53.339> we<00:49:53.579> will<00:49:53.700> have<00:49:53.819> a<00:49:53.880> boot<00:49:54.180> please<00:49:54.599> feel 00:49:54.770 --> 00:49:54.780 align:start position:0% then we will have a boot please feel 00:49:54.780 --> 00:49:56.390 align:start position:0% then we will have a boot please feel free<00:49:54.900> to<00:49:55.020> ask<00:49:55.200> any<00:49:55.380> questions<00:49:55.619> and<00:49:56.040> thank<00:49:56.280> you 00:49:56.390 --> 00:49:56.400 align:start position:0% free to ask any questions and thank you 00:49:56.400 --> 00:49:57.380 align:start position:0% free to ask any questions and thank you very<00:49:56.520> much<00:49:56.640> for<00:49:56.940> coming 00:49:57.380 --> 00:49:57.390 align:start position:0% very much for coming 00:49:57.390 --> 00:50:02.929 align:start position:0% very much for coming [Applause]