WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:12.869 align:start position:0% [Applause] 00:00:12.869 --> 00:00:12.879 align:start position:0% 00:00:12.879 --> 00:00:16.660 align:start position:0% opening<00:00:14.469> probably<00:00:15.469> you<00:00:15.740> have<00:00:16.099> heard<00:00:16.129> about<00:00:16.520> it 00:00:16.660 --> 00:00:16.670 align:start position:0% opening probably you have heard about it 00:00:16.670 --> 00:00:18.460 align:start position:0% opening probably you have heard about it and<00:00:16.970> simply<00:00:17.270> because<00:00:17.570> of<00:00:17.599> the<00:00:17.960> security 00:00:18.460 --> 00:00:18.470 align:start position:0% and simply because of the security 00:00:18.470 --> 00:00:21.670 align:start position:0% and simply because of the security audits<00:00:19.039> we<00:00:19.220> perform<00:00:19.640> last<00:00:20.509> year<00:00:20.779> we<00:00:21.079> audited 00:00:21.670 --> 00:00:21.680 align:start position:0% audits we perform last year we audited 00:00:21.680 --> 00:00:24.550 align:start position:0% audits we perform last year we audited this<00:00:21.860> community<00:00:22.310> compiler<00:00:22.759> we<00:00:23.329> all<00:00:23.720> saw<00:00:24.140> what 00:00:24.550 --> 00:00:24.560 align:start position:0% this community compiler we all saw what 00:00:24.560 --> 00:00:27.460 align:start position:0% this community compiler we all saw what I<00:00:24.980> did<00:00:25.070> a<00:00:25.430> lot<00:00:25.699> of<00:00:25.730> profits<00:00:26.300> for<00:00:26.359> coinbase<00:00:26.810> we 00:00:27.460 --> 00:00:27.470 align:start position:0% I did a lot of profits for coinbase we 00:00:27.470 --> 00:00:31.060 align:start position:0% I did a lot of profits for coinbase we audited<00:00:28.269> but<00:00:29.269> in<00:00:29.390> the<00:00:29.480> days<00:00:29.660> the<00:00:30.199> serpent 00:00:31.060 --> 00:00:31.070 align:start position:0% audited but in the days the serpent 00:00:31.070 --> 00:00:33.189 align:start position:0% audited but in the days the serpent language<00:00:31.519> and<00:00:31.880> we<00:00:32.000> broke<00:00:32.269> it<00:00:32.330> by<00:00:32.599> the<00:00:32.660> way<00:00:32.870> and 00:00:33.189 --> 00:00:33.199 align:start position:0% language and we broke it by the way and 00:00:33.199 --> 00:00:35.439 align:start position:0% language and we broke it by the way and most<00:00:33.980> recently<00:00:34.460> we<00:00:34.790> are<00:00:34.820> today<00:00:35.150> the 00:00:35.439 --> 00:00:35.449 align:start position:0% most recently we are today the 00:00:35.449 --> 00:00:40.210 align:start position:0% most recently we are today the well-known<00:00:36.110> compound<00:00:37.070> and<00:00:37.629> instead<00:00:38.629> of<00:00:39.220> you 00:00:40.210 --> 00:00:40.220 align:start position:0% well-known compound and instead of you 00:00:40.220 --> 00:00:43.119 align:start position:0% well-known compound and instead of you probably<00:00:40.670> also<00:00:40.970> known<00:00:41.480> know<00:00:42.050> us<00:00:42.260> because<00:00:42.980> of 00:00:43.119 --> 00:00:43.129 align:start position:0% probably also known know us because of 00:00:43.129 --> 00:00:44.709 align:start position:0% probably also known know us because of the<00:00:43.250> open<00:00:43.579> sampling<00:00:43.910> contractor<00:00:44.420> was<00:00:44.600> it 00:00:44.709 --> 00:00:44.719 align:start position:0% the open sampling contractor was it 00:00:44.719 --> 00:00:46.990 align:start position:0% the open sampling contractor was it really<00:00:44.989> one<00:00:45.199> of<00:00:45.230> the<00:00:45.500> most<00:00:45.680> used<00:00:46.160> libraries<00:00:46.699> in 00:00:46.990 --> 00:00:47.000 align:start position:0% really one of the most used libraries in 00:00:47.000 --> 00:00:49.930 align:start position:0% really one of the most used libraries in the<00:00:47.660> civil<00:00:47.989> system<00:00:48.140> that<00:00:48.649> has<00:00:48.859> more<00:00:49.460> than<00:00:49.609> 20 00:00:49.930 --> 00:00:49.940 align:start position:0% the civil system that has more than 20 00:00:49.940 --> 00:00:52.720 align:start position:0% the civil system that has more than 20 to<00:00:50.059> gain<00:00:50.239> of<00:00:50.870> 10<00:00:51.469> days<00:00:51.710> per<00:00:52.010> week<00:00:52.039> and<00:00:52.520> that 00:00:52.720 --> 00:00:52.730 align:start position:0% to gain of 10 days per week and that 00:00:52.730 --> 00:00:55.389 align:start position:0% to gain of 10 days per week and that probably<00:00:53.539> everyone<00:00:53.989> that<00:00:54.230> has<00:00:54.500> developed 00:00:55.389 --> 00:00:55.399 align:start position:0% probably everyone that has developed 00:00:55.399 --> 00:00:59.520 align:start position:0% probably everyone that has developed under<00:00:55.789> ERC<00:00:56.120> 20<00:00:56.449> or<00:00:56.649> ERC<00:00:57.649> 721<00:00:58.340> probably<00:00:58.820> used 00:00:59.520 --> 00:00:59.530 align:start position:0% under ERC 20 or ERC 721 probably used 00:00:59.530 --> 00:01:05.049 align:start position:0% under ERC 20 or ERC 721 probably used discovery<00:01:01.570> so<00:01:02.920> gender<00:01:03.920> for<00:01:04.190> today<00:01:04.429> we're 00:01:05.049 --> 00:01:05.059 align:start position:0% discovery so gender for today we're 00:01:05.059 --> 00:01:08.350 align:start position:0% discovery so gender for today we're gonna<00:01:05.300> go<00:01:05.929> through<00:01:06.369> how<00:01:07.369> we<00:01:07.820> can<00:01:08.030> develop 00:01:08.350 --> 00:01:08.360 align:start position:0% gonna go through how we can develop 00:01:08.360 --> 00:01:11.400 align:start position:0% gonna go through how we can develop smart<00:01:08.840> contracts<00:01:09.380> using<00:01:09.770> the<00:01:09.890> open<00:01:10.160> 17<00:01:10.490> SDK 00:01:11.400 --> 00:01:11.410 align:start position:0% smart contracts using the open 17 SDK 00:01:11.410 --> 00:01:13.990 align:start position:0% smart contracts using the open 17 SDK afterwards<00:01:12.410> we<00:01:12.679> are<00:01:12.740> gonna<00:01:12.979> see<00:01:13.160> how<00:01:13.369> we<00:01:13.429> can 00:01:13.990 --> 00:01:14.000 align:start position:0% afterwards we are gonna see how we can 00:01:14.000 --> 00:01:17.139 align:start position:0% afterwards we are gonna see how we can build<00:01:14.270> jobs<00:01:14.869> super<00:01:15.770> super<00:01:16.099> easy<00:01:16.130> using<00:01:17.000> the 00:01:17.139 --> 00:01:17.149 align:start position:0% build jobs super super easy using the 00:01:17.149 --> 00:01:19.270 align:start position:0% build jobs super super easy using the opens<00:01:17.539> of<00:01:17.660> these<00:01:17.810> charter<00:01:18.200> kids<00:01:18.410> and 00:01:19.270 --> 00:01:19.280 align:start position:0% opens of these charter kids and 00:01:19.280 --> 00:01:21.820 align:start position:0% opens of these charter kids and afterwards<00:01:19.849> we're<00:01:20.060> gonna<00:01:20.209> talk<00:01:20.990> about<00:01:21.020> sound 00:01:21.820 --> 00:01:21.830 align:start position:0% afterwards we're gonna talk about sound 00:01:21.830 --> 00:01:22.650 align:start position:0% afterwards we're gonna talk about sound DX 00:01:22.650 --> 00:01:22.660 align:start position:0% DX 00:01:22.660 --> 00:01:26.919 align:start position:0% DX uxn<00:01:23.660> main<00:01:23.840> problems<00:01:24.380> we<00:01:24.679> faced<00:01:25.459> while<00:01:26.330> you 00:01:26.919 --> 00:01:26.929 align:start position:0% uxn main problems we faced while you 00:01:26.929 --> 00:01:30.969 align:start position:0% uxn main problems we faced while you know<00:01:27.050> developing<00:01:28.009> doubts<00:01:28.789> for<00:01:29.179> for<00:01:30.050> users<00:01:30.440> and 00:01:30.969 --> 00:01:30.979 align:start position:0% know developing doubts for for users and 00:01:30.979 --> 00:01:32.529 align:start position:0% know developing doubts for for users and we're<00:01:31.220> gonna<00:01:31.369> talk<00:01:31.670> about<00:01:31.759> the<00:01:32.090> open<00:01:32.330> ceiling 00:01:32.529 --> 00:01:32.539 align:start position:0% we're gonna talk about the open ceiling 00:01:32.539 --> 00:01:35.529 align:start position:0% we're gonna talk about the open ceiling GSM<00:01:33.259> groups<00:01:33.700> so<00:01:34.700> the<00:01:34.819> first<00:01:35.090> part<00:01:35.270> of<00:01:35.390> this 00:01:35.529 --> 00:01:35.539 align:start position:0% GSM groups so the first part of this 00:01:35.539 --> 00:01:38.589 align:start position:0% GSM groups so the first part of this talk<00:01:35.780> is<00:01:35.959> gonna<00:01:36.170> be<00:01:36.319> about<00:01:36.789> DX<00:01:37.789> and<00:01:38.149> the<00:01:38.300> second 00:01:38.589 --> 00:01:38.599 align:start position:0% talk is gonna be about DX and the second 00:01:38.599 --> 00:01:42.130 align:start position:0% talk is gonna be about DX and the second one<00:01:38.750> about<00:01:39.229> us<00:01:40.209> developer<00:01:41.209> experience<00:01:41.720> their 00:01:42.130 --> 00:01:42.140 align:start position:0% one about us developer experience their 00:01:42.140 --> 00:01:46.499 align:start position:0% one about us developer experience their user<00:01:42.530> experience<00:01:42.729> so<00:01:43.729> let's<00:01:43.759> start<00:01:44.330> with<00:01:44.810> DX 00:01:46.499 --> 00:01:46.509 align:start position:0% user experience so let's start with DX 00:01:46.509 --> 00:01:50.620 align:start position:0% user experience so let's start with DX it's<00:01:47.509> super<00:01:47.840> important<00:01:48.289> for<00:01:48.349> us<00:01:48.649> to<00:01:48.950> know<00:01:49.849> what 00:01:50.620 --> 00:01:50.630 align:start position:0% it's super important for us to know what 00:01:50.630 --> 00:01:52.140 align:start position:0% it's super important for us to know what problem<00:01:51.170> we<00:01:51.289> have<00:01:51.500> here 00:01:52.140 --> 00:01:52.150 align:start position:0% problem we have here 00:01:52.150 --> 00:01:54.060 align:start position:0% problem we have here I<00:01:52.180> think<00:01:52.510> that<00:01:52.690> if<00:01:52.960> used<00:01:53.380> a<00:01:53.650> software 00:01:54.060 --> 00:01:54.070 align:start position:0% I think that if used a software 00:01:54.070 --> 00:01:56.820 align:start position:0% I think that if used a software developers<00:01:54.610> for<00:01:54.910> developers<00:01:55.120> and<00:01:55.930> have 00:01:56.820 --> 00:01:56.830 align:start position:0% developers for developers and have 00:01:56.830 --> 00:01:59.340 align:start position:0% developers for developers and have worked<00:01:57.100> in<00:01:57.460> other<00:01:58.030> ecosystems<00:01:58.210> proud<00:01:58.990> of<00:01:59.140> you 00:01:59.340 --> 00:01:59.350 align:start position:0% worked in other ecosystems proud of you 00:01:59.350 --> 00:02:03.210 align:start position:0% worked in other ecosystems proud of you no<00:01:59.980> doubt<00:02:00.310> our<00:02:01.210> tools<00:02:02.200> are<00:02:02.500> still<00:02:02.980> super 00:02:03.210 --> 00:02:03.220 align:start position:0% no doubt our tools are still super 00:02:03.220 --> 00:02:03.870 align:start position:0% no doubt our tools are still super super-great 00:02:03.870 --> 00:02:03.880 align:start position:0% super-great 00:02:03.880 --> 00:02:06.620 align:start position:0% super-great compared<00:02:04.660> to<00:02:04.840> those<00:02:04.960> other<00:02:05.020> resistance<00:02:05.920> and 00:02:06.620 --> 00:02:06.630 align:start position:0% compared to those other resistance and 00:02:06.630 --> 00:02:11.160 align:start position:0% compared to those other resistance and us<00:02:07.630> in<00:02:08.110> opens<00:02:08.560> up<00:02:08.710> then<00:02:08.860> basically<00:02:09.670> love<00:02:10.600> to 00:02:11.160 --> 00:02:11.170 align:start position:0% us in opens up then basically love to 00:02:11.170 --> 00:02:14.790 align:start position:0% us in opens up then basically love to really<00:02:11.860> stop<00:02:12.400> for<00:02:13.150> you<00:02:13.390> to<00:02:13.870> make<00:02:14.050> your<00:02:14.230> life 00:02:14.790 --> 00:02:14.800 align:start position:0% really stop for you to make your life 00:02:14.800 --> 00:02:19.200 align:start position:0% really stop for you to make your life easier<00:02:15.220> and<00:02:15.460> that's<00:02:16.270> why<00:02:16.540> we<00:02:17.170> built<00:02:17.880> two<00:02:18.880> super 00:02:19.200 --> 00:02:19.210 align:start position:0% easier and that's why we built two super 00:02:19.210 --> 00:02:22.380 align:start position:0% easier and that's why we built two super ace<00:02:19.330> the<00:02:19.540> tools<00:02:19.810> of<00:02:19.990> our<00:02:20.110> Java<00:02:20.530> SDK<00:02:21.070> NGO<00:02:21.850> in<00:02:22.120> 7 00:02:22.380 --> 00:02:22.390 align:start position:0% ace the tools of our Java SDK NGO in 7 00:02:22.390 --> 00:02:25.560 align:start position:0% ace the tools of our Java SDK NGO in 7 easy<00:02:22.480> targets<00:02:23.459> let's<00:02:24.459> begin<00:02:24.910> with<00:02:25.180> the<00:02:25.300> opens 00:02:25.560 --> 00:02:25.570 align:start position:0% easy targets let's begin with the opens 00:02:25.570 --> 00:02:28.110 align:start position:0% easy targets let's begin with the opens up<00:02:25.720> in<00:02:25.900> SDK<00:02:26.530> G<00:02:27.130> opens<00:02:27.370> up<00:02:27.490> the<00:02:27.610> SDK<00:02:27.940> is<00:02:27.970> a 00:02:28.110 --> 00:02:28.120 align:start position:0% up in SDK G opens up the SDK is a 00:02:28.120 --> 00:02:30.330 align:start position:0% up in SDK G opens up the SDK is a software<00:02:28.690> developer<00:02:29.110> gears<00:02:29.350> or<00:02:29.620> a<00:02:29.650> software 00:02:30.330 --> 00:02:30.340 align:start position:0% software developer gears or a software 00:02:30.340 --> 00:02:32.910 align:start position:0% software developer gears or a software development<00:02:30.760> tool<00:02:31.030> basically<00:02:31.660> a<00:02:32.050> CLI<00:02:32.530> that 00:02:32.910 --> 00:02:32.920 align:start position:0% development tool basically a CLI that 00:02:32.920 --> 00:02:35.580 align:start position:0% development tool basically a CLI that will<00:02:33.160> let<00:02:33.520> you<00:02:33.790> develop<00:02:34.690> your<00:02:34.810> own<00:02:35.110> contracts 00:02:35.580 --> 00:02:35.590 align:start position:0% will let you develop your own contracts 00:02:35.590 --> 00:02:37.680 align:start position:0% will let you develop your own contracts compile<00:02:36.310> them<00:02:36.520> with<00:02:36.730> any<00:02:37.030> version<00:02:37.480> of 00:02:37.680 --> 00:02:37.690 align:start position:0% compile them with any version of 00:02:37.690 --> 00:02:40.650 align:start position:0% compile them with any version of solidity<00:02:38.170> want<00:02:38.560> deploy<00:02:39.550> them<00:02:39.760> with<00:02:40.180> this<00:02:40.300> only 00:02:40.650 --> 00:02:40.660 align:start position:0% solidity want deploy them with this only 00:02:40.660 --> 00:02:43.980 align:start position:0% solidity want deploy them with this only with<00:02:40.930> one<00:02:41.110> command<00:02:41.820> upgrade<00:02:42.820> them<00:02:43.209> and<00:02:43.600> we<00:02:43.780> can 00:02:43.980 --> 00:02:43.990 align:start position:0% with one command upgrade them and we can 00:02:43.990 --> 00:02:46.980 align:start position:0% with one command upgrade them and we can talk<00:02:44.500> later<00:02:44.650> about<00:02:44.800> that<00:02:45.660> interact<00:02:46.660> with<00:02:46.750> them 00:02:46.980 --> 00:02:46.990 align:start position:0% talk later about that interact with them 00:02:46.990 --> 00:02:50.370 align:start position:0% talk later about that interact with them in<00:02:47.170> a<00:02:47.620> super<00:02:48.010> easy<00:02:48.130> way<00:02:48.430> and<00:02:49.209> also<00:02:49.390> start<00:02:50.230> your 00:02:50.370 --> 00:02:50.380 align:start position:0% in a super easy way and also start your 00:02:50.380 --> 00:02:55.020 align:start position:0% in a super easy way and also start your jobs<00:02:50.650> like<00:02:51.490> in<00:02:52.000> five<00:02:52.390> minutes<00:02:53.610> how<00:02:54.610> you<00:02:54.850> can 00:02:55.020 --> 00:02:55.030 align:start position:0% jobs like in five minutes how you can 00:02:55.030 --> 00:02:58.830 align:start position:0% jobs like in five minutes how you can use<00:02:55.180> well<00:02:55.750> its<00:02:56.350> name<00:02:57.340> package<00:02:57.970> open<00:02:58.420> Zebulon 00:02:58.830 --> 00:02:58.840 align:start position:0% use well its name package open Zebulon 00:02:58.840 --> 00:03:02.970 align:start position:0% use well its name package open Zebulon CLI<00:02:59.650> so<00:03:00.100> just<00:03:00.550> running<00:03:01.150> MVA<00:03:01.660> and<00:03:01.959> PM<00:03:02.590> install 00:03:02.970 --> 00:03:02.980 align:start position:0% CLI so just running MVA and PM install 00:03:02.980 --> 00:03:04.540 align:start position:0% CLI so just running MVA and PM install add-ons<00:03:03.760> eminence 00:03:04.540 --> 00:03:04.550 align:start position:0% add-ons eminence 00:03:04.550 --> 00:03:07.870 align:start position:0% add-ons eminence like<00:03:04.790> whether<00:03:05.540> the<00:03:05.780> tree<00:03:06.340> you<00:03:07.340> will<00:03:07.550> probably 00:03:07.870 --> 00:03:07.880 align:start position:0% like whether the tree you will probably 00:03:07.880 --> 00:03:11.440 align:start position:0% like whether the tree you will probably first<00:03:08.480> want<00:03:08.930> to<00:03:09.730> initialize<00:03:10.730> from<00:03:10.970> project 00:03:11.440 --> 00:03:11.450 align:start position:0% first want to initialize from project 00:03:11.450 --> 00:03:13.960 align:start position:0% first want to initialize from project you<00:03:11.930> can<00:03:12.140> do<00:03:12.290> is<00:03:12.410> that<00:03:12.650> you<00:03:12.980> can<00:03:13.280> do<00:03:13.430> that<00:03:13.550> using 00:03:13.960 --> 00:03:13.970 align:start position:0% you can do is that you can do that using 00:03:13.970 --> 00:03:15.790 align:start position:0% you can do is that you can do that using the<00:03:14.300> open<00:03:14.630> Zeppelin<00:03:14.930> in<00:03:15.170> the<00:03:15.230> Koran<00:03:15.560> it 00:03:15.790 --> 00:03:15.800 align:start position:0% the open Zeppelin in the Koran it 00:03:15.800 --> 00:03:18.220 align:start position:0% the open Zeppelin in the Koran it basically<00:03:16.280> will<00:03:16.550> run<00:03:17.240> a<00:03:17.270> lot<00:03:17.510> of<00:03:17.600> stuff<00:03:17.960> that 00:03:18.220 --> 00:03:18.230 align:start position:0% basically will run a lot of stuff that 00:03:18.230 --> 00:03:20.620 align:start position:0% basically will run a lot of stuff that will<00:03:18.500> trade<00:03:19.130> your<00:03:19.250> contracts<00:03:19.760> folder<00:03:19.940> it<00:03:20.600> will 00:03:20.620 --> 00:03:20.630 align:start position:0% will trade your contracts folder it will 00:03:20.630 --> 00:03:22.690 align:start position:0% will trade your contracts folder it will set<00:03:21.050> up<00:03:21.170> your<00:03:21.200> network<00:03:21.650> configuration<00:03:22.010> file 00:03:22.690 --> 00:03:22.700 align:start position:0% set up your network configuration file 00:03:22.700 --> 00:03:25.210 align:start position:0% set up your network configuration file and<00:03:23.060> a<00:03:23.390> couple<00:03:23.540> of<00:03:23.720> other<00:03:23.990> things<00:03:24.260> for<00:03:24.800> you<00:03:24.830> to 00:03:25.210 --> 00:03:25.220 align:start position:0% and a couple of other things for you to 00:03:25.220 --> 00:03:27.130 align:start position:0% and a couple of other things for you to track<00:03:25.520> your<00:03:26.060> different<00:03:26.480> contracts<00:03:26.900> within 00:03:27.130 --> 00:03:27.140 align:start position:0% track your different contracts within 00:03:27.140 --> 00:03:32.440 align:start position:0% track your different contracts within your<00:03:29.050> so<00:03:30.250> basically<00:03:31.250> we<00:03:32.090> want<00:03:32.300> to 00:03:32.440 --> 00:03:32.450 align:start position:0% your so basically we want to 00:03:32.450 --> 00:03:34.300 align:start position:0% your so basically we want to develop<00:03:32.930> our<00:03:33.260> conference<00:03:33.680> we<00:03:33.830> have<00:03:33.980> a<00:03:34.010> my 00:03:34.300 --> 00:03:34.310 align:start position:0% develop our conference we have a my 00:03:34.310 --> 00:03:38.110 align:start position:0% develop our conference we have a my contract<00:03:34.960> contract<00:03:35.960> which<00:03:36.890> has<00:03:36.920> do<00:03:37.700> something 00:03:38.110 --> 00:03:38.120 align:start position:0% contract contract which has do something 00:03:38.120 --> 00:03:40.810 align:start position:0% contract contract which has do something function<00:03:38.750> that<00:03:38.960> receives<00:03:39.320> something<00:03:40.010> brother 00:03:40.810 --> 00:03:40.820 align:start position:0% function that receives something brother 00:03:40.820 --> 00:03:45.850 align:start position:0% function that receives something brother Sonny<00:03:41.590> super<00:03:42.590> easy<00:03:43.340> to<00:03:43.550> understand<00:03:44.650> we<00:03:45.650> only 00:03:45.850 --> 00:03:45.860 align:start position:0% Sonny super easy to understand we only 00:03:45.860 --> 00:03:47.760 align:start position:0% Sonny super easy to understand we only have<00:03:46.130> to<00:03:46.280> run<00:03:46.460> open<00:03:46.970> setting<00:03:47.360> create 00:03:47.760 --> 00:03:47.770 align:start position:0% have to run open setting create 00:03:47.770 --> 00:03:50.290 align:start position:0% have to run open setting create specifying<00:03:48.770> the<00:03:48.980> contract<00:03:49.400> name<00:03:49.550> on<00:03:49.790> the 00:03:50.290 --> 00:03:50.300 align:start position:0% specifying the contract name on the 00:03:50.300 --> 00:03:52.630 align:start position:0% specifying the contract name on the network<00:03:50.960> name<00:03:51.140> and<00:03:51.680> that's<00:03:51.890> all<00:03:52.070> you<00:03:52.520> will 00:03:52.630 --> 00:03:52.640 align:start position:0% network name and that's all you will 00:03:52.640 --> 00:03:55.120 align:start position:0% network name and that's all you will have<00:03:52.910> your<00:03:53.330> contractor<00:03:54.080> your<00:03:54.710> contract 00:03:55.120 --> 00:03:55.130 align:start position:0% have your contractor your contract 00:03:55.130 --> 00:03:57.940 align:start position:0% have your contractor your contract deploys<00:03:55.460> for<00:03:55.730> block<00:03:56.630> you<00:03:56.840> to<00:03:57.230> the<00:03:57.350> maintenance 00:03:57.940 --> 00:03:57.950 align:start position:0% deploys for block you to the maintenance 00:03:57.950 --> 00:04:00.790 align:start position:0% deploys for block you to the maintenance Network<00:03:58.790> in<00:03:58.940> this<00:03:59.090> case<00:03:59.300> but<00:03:59.990> if<00:04:00.290> you<00:04:00.470> forgot 00:04:00.790 --> 00:04:00.800 align:start position:0% Network in this case but if you forgot 00:04:00.800 --> 00:04:04.990 align:start position:0% Network in this case but if you forgot all<00:04:01.160> the<00:04:01.460> pointer<00:04:02.420> name<00:04:02.630> or<00:04:03.170> the<00:04:03.700> network<00:04:04.700> name 00:04:04.990 --> 00:04:05.000 align:start position:0% all the pointer name or the network name 00:04:05.000 --> 00:04:07.930 align:start position:0% all the pointer name or the network name it's<00:04:05.450> fine<00:04:05.720> all<00:04:06.350> the<00:04:06.560> open<00:04:06.860> sibling<00:04:07.250> contracts 00:04:07.930 --> 00:04:07.940 align:start position:0% it's fine all the open sibling contracts 00:04:07.940 --> 00:04:10.210 align:start position:0% it's fine all the open sibling contracts are<00:04:08.150> interactive<00:04:08.840> all<00:04:09.620> the<00:04:09.800> organs<00:04:10.040> of<00:04:10.130> the 00:04:10.210 --> 00:04:10.220 align:start position:0% are interactive all the organs of the 00:04:10.220 --> 00:04:12.520 align:start position:0% are interactive all the organs of the commands<00:04:10.730> carry<00:04:11.060> the<00:04:11.239> map<00:04:11.390> -<00:04:11.570> and<00:04:12.080> you<00:04:12.260> will<00:04:12.380> be 00:04:12.520 --> 00:04:12.530 align:start position:0% commands carry the map - and you will be 00:04:12.530 --> 00:04:14.860 align:start position:0% commands carry the map - and you will be able<00:04:12.650> to<00:04:12.800> just<00:04:13.130> run<00:04:13.340> open<00:04:13.730> setting<00:04:14.000> create<00:04:14.330> and 00:04:14.860 --> 00:04:14.870 align:start position:0% able to just run open setting create and 00:04:14.870 --> 00:04:17.260 align:start position:0% able to just run open setting create and the<00:04:15.020> CLI<00:04:15.380> will<00:04:15.680> guide<00:04:15.980> you<00:04:16.280> in<00:04:16.549> the<00:04:16.730> process<00:04:16.760> of 00:04:17.260 --> 00:04:17.270 align:start position:0% the CLI will guide you in the process of 00:04:17.270 --> 00:04:20.170 align:start position:0% the CLI will guide you in the process of deploying<00:04:17.930> your<00:04:18.350> contract<00:04:18.890> so<00:04:19.640> for<00:04:19.820> example 00:04:20.170 --> 00:04:20.180 align:start position:0% deploying your contract so for example 00:04:20.180 --> 00:04:22.750 align:start position:0% deploying your contract so for example here<00:04:20.450> we<00:04:20.480> have<00:04:20.630> a<00:04:20.810> contract<00:04:21.470> my<00:04:21.950> contract<00:04:22.520> in 00:04:22.750 --> 00:04:22.760 align:start position:0% here we have a contract my contract in 00:04:22.760 --> 00:04:25.450 align:start position:0% here we have a contract my contract in maintenance<00:04:23.180> at<00:04:23.870> the<00:04:23.930> address<00:04:24.410> one<00:04:24.680> area<00:04:25.130> the 00:04:25.450 --> 00:04:25.460 align:start position:0% maintenance at the address one area the 00:04:25.460 --> 00:04:28.120 align:start position:0% maintenance at the address one area the one<00:04:25.580> the<00:04:25.760> strands<00:04:26.060> with<00:04:26.480> one<00:04:26.690> Ian<00:04:26.900> and<00:04:27.830> we 00:04:28.120 --> 00:04:28.130 align:start position:0% one the strands with one Ian and we 00:04:28.130 --> 00:04:31.600 align:start position:0% one the strands with one Ian and we probably<00:04:28.750> want<00:04:29.750> to<00:04:29.930> talk<00:04:30.680> with<00:04:30.980> our<00:04:31.100> contracts 00:04:31.600 --> 00:04:31.610 align:start position:0% probably want to talk with our contracts 00:04:31.610 --> 00:04:33.670 align:start position:0% probably want to talk with our contracts right<00:04:31.760> because<00:04:32.000> we<00:04:32.360> have<00:04:32.600> already<00:04:32.840> deployed 00:04:33.670 --> 00:04:33.680 align:start position:0% right because we have already deployed 00:04:33.680 --> 00:04:34.770 align:start position:0% right because we have already deployed them<00:04:33.950> and<00:04:34.130> we<00:04:34.310> want 00:04:34.770 --> 00:04:34.780 align:start position:0% them and we want 00:04:34.780 --> 00:04:38.190 align:start position:0% them and we want for<00:04:34.870> example<00:04:35.380> functions<00:04:36.000> see<00:04:37.000> the<00:04:37.540> value<00:04:38.080> of 00:04:38.190 --> 00:04:38.200 align:start position:0% for example functions see the value of 00:04:38.200 --> 00:04:40.610 align:start position:0% for example functions see the value of variables<00:04:38.920> or<00:04:39.130> maybe<00:04:39.340> just<00:04:39.610> two<00:04:39.910> transactions 00:04:40.610 --> 00:04:40.620 align:start position:0% variables or maybe just two transactions 00:04:40.620 --> 00:04:43.800 align:start position:0% variables or maybe just two transactions G<00:04:41.620> opens<00:04:41.860> investigate<00:04:42.430> has<00:04:42.670> two<00:04:43.000> super<00:04:43.450> handy 00:04:43.800 --> 00:04:43.810 align:start position:0% G opens investigate has two super handy 00:04:43.810 --> 00:04:45.540 align:start position:0% G opens investigate has two super handy commands<00:04:44.139> which<00:04:44.410> are<00:04:44.620> called<00:04:44.950> and<00:04:45.220> central 00:04:45.540 --> 00:04:45.550 align:start position:0% commands which are called and central 00:04:45.550 --> 00:04:48.180 align:start position:0% commands which are called and central section<00:04:45.940> call<00:04:46.270> for<00:04:46.600> calling<00:04:46.990> pure<00:04:47.770> view 00:04:48.180 --> 00:04:48.190 align:start position:0% section call for calling pure view 00:04:48.190 --> 00:04:49.920 align:start position:0% section call for calling pure view functions<00:04:48.669> and<00:04:48.850> central<00:04:49.150> sections<00:04:49.540> to<00:04:49.690> any 00:04:49.920 --> 00:04:49.930 align:start position:0% functions and central sections to any 00:04:49.930 --> 00:04:52.530 align:start position:0% functions and central sections to any other<00:04:50.169> public<00:04:50.740> function<00:04:51.220> of<00:04:51.669> our<00:04:51.940> contract 00:04:52.530 --> 00:04:52.540 align:start position:0% other public function of our contract 00:04:52.540 --> 00:04:54.470 align:start position:0% other public function of our contract that<00:04:52.630> will<00:04:52.960> actually<00:04:53.080> create<00:04:53.350> a<00:04:53.650> transaction 00:04:54.470 --> 00:04:54.480 align:start position:0% that will actually create a transaction 00:04:54.480 --> 00:04:58.040 align:start position:0% that will actually create a transaction they<00:04:55.480> use<00:04:55.770> usage<00:04:56.770> is<00:04:57.010> super<00:04:57.550> super<00:04:57.910> easy 00:04:58.040 --> 00:04:58.050 align:start position:0% they use usage is super super easy 00:04:58.050 --> 00:05:00.810 align:start position:0% they use usage is super super easy interactive<00:04:59.050> comments<00:04:59.500> if<00:05:00.160> you<00:05:00.370> just<00:05:00.639> run 00:05:00.810 --> 00:05:00.820 align:start position:0% interactive comments if you just run 00:05:00.820 --> 00:05:03.090 align:start position:0% interactive comments if you just run open<00:05:01.150> second<00:05:01.450> column<00:05:01.840> or<00:05:02.050> central<00:05:02.620> section<00:05:02.980> it 00:05:03.090 --> 00:05:03.100 align:start position:0% open second column or central section it 00:05:03.100 --> 00:05:04.920 align:start position:0% open second column or central section it will<00:05:03.280> ask<00:05:03.550> you<00:05:03.730> to<00:05:03.790> pick<00:05:04.000> a<00:05:04.120> network<00:05:04.450> of<00:05:04.630> your 00:05:04.920 --> 00:05:04.930 align:start position:0% will ask you to pick a network of your 00:05:04.930 --> 00:05:07.440 align:start position:0% will ask you to pick a network of your network<00:05:05.260> configuration<00:05:05.440> file<00:05:06.100> it<00:05:06.760> then<00:05:07.060> will 00:05:07.440 --> 00:05:07.450 align:start position:0% network configuration file it then will 00:05:07.450 --> 00:05:10.940 align:start position:0% network configuration file it then will list<00:05:07.870> all<00:05:08.140> the<00:05:08.590> instances<00:05:09.190> you<00:05:09.970> can<00:05:10.210> create 00:05:10.940 --> 00:05:10.950 align:start position:0% list all the instances you can create 00:05:10.950 --> 00:05:13.650 align:start position:0% list all the instances you can create afterwards<00:05:11.950> in<00:05:12.250> will<00:05:12.610> I<00:05:12.880> mean<00:05:13.210> not<00:05:13.390> create<00:05:13.630> but 00:05:13.650 --> 00:05:13.660 align:start position:0% afterwards in will I mean not create but 00:05:13.660 --> 00:05:16.950 align:start position:0% afterwards in will I mean not create but to<00:05:14.050> call<00:05:14.370> afterwards<00:05:15.370> it<00:05:15.940> will<00:05:16.360> list<00:05:16.600> all<00:05:16.810> the 00:05:16.950 --> 00:05:16.960 align:start position:0% to call afterwards it will list all the 00:05:16.960 --> 00:05:20.490 align:start position:0% to call afterwards it will list all the functions<00:05:17.380> that<00:05:17.410> that<00:05:18.900> contract<00:05:19.900> has<00:05:20.169> for 00:05:20.490 --> 00:05:20.500 align:start position:0% functions that that contract has for 00:05:20.500 --> 00:05:21.720 align:start position:0% functions that that contract has for example<00:05:20.560> here<00:05:21.010> that<00:05:21.040> there's<00:05:21.310> something<00:05:21.490> and 00:05:21.720 --> 00:05:21.730 align:start position:0% example here that there's something and 00:05:21.730 --> 00:05:24.210 align:start position:0% example here that there's something and I<00:05:21.790> already<00:05:21.940> show<00:05:22.450> on<00:05:22.750> a<00:05:22.810> community<00:05:23.800> function 00:05:24.210 --> 00:05:24.220 align:start position:0% I already show on a community function 00:05:24.220 --> 00:05:27.000 align:start position:0% I already show on a community function and<00:05:24.669> just<00:05:25.180> by<00:05:25.570> selecting<00:05:26.560> the<00:05:26.680> seventh-inning 00:05:27.000 --> 00:05:27.010 align:start position:0% and just by selecting the seventh-inning 00:05:27.010 --> 00:05:29.219 align:start position:0% and just by selecting the seventh-inning will<00:05:27.340> ask<00:05:27.520> you<00:05:27.700> for<00:05:27.760> each<00:05:28.240> parameter<00:05:28.810> the 00:05:29.219 --> 00:05:29.229 align:start position:0% will ask you for each parameter the 00:05:29.229 --> 00:05:31.710 align:start position:0% will ask you for each parameter the function<00:05:29.530> s<00:05:29.770> and<00:05:30.580> that's<00:05:30.729> it<00:05:30.880> that's<00:05:31.240> it<00:05:31.390> you 00:05:31.710 --> 00:05:31.720 align:start position:0% function s and that's it that's it you 00:05:31.720 --> 00:05:33.420 align:start position:0% function s and that's it that's it you will<00:05:31.840> see<00:05:32.080> the<00:05:32.200> transaction<00:05:32.590> cache<00:05:32.979> which<00:05:33.250> you 00:05:33.420 --> 00:05:33.430 align:start position:0% will see the transaction cache which you 00:05:33.430 --> 00:05:35.909 align:start position:0% will see the transaction cache which you will<00:05:33.639> be<00:05:34.120> probably<00:05:34.360> able<00:05:34.840> to<00:05:35.050> copy<00:05:35.320> and<00:05:35.740> paste 00:05:35.909 --> 00:05:35.919 align:start position:0% will be probably able to copy and paste 00:05:35.919 --> 00:05:42.230 align:start position:0% will be probably able to copy and paste in<00:05:36.310> ether<00:05:36.970> scan<00:05:37.300> and<00:05:37.570> see<00:05:38.229> how<00:05:38.650> it<00:05:39.490> did<00:05:40.710> well<00:05:41.710> we 00:05:42.230 --> 00:05:42.240 align:start position:0% in ether scan and see how it did well we 00:05:42.240 --> 00:05:46.260 align:start position:0% in ether scan and see how it did well we know<00:05:43.240> that<00:05:43.680> software<00:05:44.680> development<00:05:45.270> contract 00:05:46.260 --> 00:05:46.270 align:start position:0% know that software development contract 00:05:46.270 --> 00:05:50.340 align:start position:0% know that software development contract development<00:05:46.780> r<00:05:47.200> is<00:05:48.010> done<00:05:48.310> by<00:05:49.080> developers<00:05:50.080> and 00:05:50.340 --> 00:05:50.350 align:start position:0% development r is done by developers and 00:05:50.350 --> 00:05:53.940 align:start position:0% development r is done by developers and universe<00:05:51.190> are<00:05:51.550> persons<00:05:52.060> people<00:05:52.930> people<00:05:53.770> make 00:05:53.940 --> 00:05:53.950 align:start position:0% universe are persons people people make 00:05:53.950 --> 00:05:56.219 align:start position:0% universe are persons people people make mistakes<00:05:54.370> every<00:05:54.610> timings<00:05:55.240> we<00:05:55.660> know<00:05:55.780> this<00:05:55.960> we 00:05:56.219 --> 00:05:56.229 align:start position:0% mistakes every timings we know this we 00:05:56.229 --> 00:05:58.050 align:start position:0% mistakes every timings we know this we know<00:05:56.260> what's<00:05:56.770> happening<00:05:57.280> right<00:05:57.490> now<00:05:57.550> in<00:05:57.940> this 00:05:58.050 --> 00:05:58.060 align:start position:0% know what's happening right now in this 00:05:58.060 --> 00:06:01.680 align:start position:0% know what's happening right now in this modular<00:05:58.630> system<00:05:59.200> we<00:05:59.890> can<00:06:00.130> just<00:06:00.610> push<00:06:01.030> our 00:06:01.680 --> 00:06:01.690 align:start position:0% modular system we can just push our 00:06:01.690 --> 00:06:03.719 align:start position:0% modular system we can just push our broken<00:06:02.229> code<00:06:02.500> and<00:06:02.740> a<00:06:02.800> lot<00:06:03.039> of<00:06:03.070> jars 00:06:03.719 --> 00:06:03.729 align:start position:0% broken code and a lot of jars 00:06:03.729 --> 00:06:05.540 align:start position:0% broken code and a lot of jars millions<00:06:04.210> of<00:06:04.330> tourists<00:06:04.720> can<00:06:04.900> be<00:06:04.990> lost<00:06:05.200> and 00:06:05.540 --> 00:06:05.550 align:start position:0% millions of tourists can be lost and 00:06:05.550 --> 00:06:09.480 align:start position:0% millions of tourists can be lost and it's<00:06:06.550> important<00:06:07.180> to<00:06:07.360> have<00:06:07.510> like<00:06:08.100> tools<00:06:09.100> for 00:06:09.480 --> 00:06:09.490 align:start position:0% it's important to have like tools for 00:06:09.490 --> 00:06:12.290 align:start position:0% it's important to have like tools for getting<00:06:10.300> rid<00:06:10.479> of<00:06:10.510> these<00:06:10.780> problems<00:06:11.320> so 00:06:12.290 --> 00:06:12.300 align:start position:0% getting rid of these problems so 00:06:12.300 --> 00:06:15.719 align:start position:0% getting rid of these problems so probably<00:06:13.830> upgrading<00:06:14.830> our<00:06:15.010> contract<00:06:15.580> is<00:06:15.700> a 00:06:15.719 --> 00:06:15.729 align:start position:0% probably upgrading our contract is a 00:06:15.729 --> 00:06:17.640 align:start position:0% probably upgrading our contract is a solution<00:06:16.210> if<00:06:16.600> we<00:06:16.750> have<00:06:16.930> a<00:06:16.960> my<00:06:17.229> contract 00:06:17.640 --> 00:06:17.650 align:start position:0% solution if we have a my contract 00:06:17.650 --> 00:06:20.730 align:start position:0% solution if we have a my contract solution<00:06:18.039> my<00:06:18.250> contract<00:06:18.729> contract<00:06:19.530> with<00:06:20.530> our 00:06:20.730 --> 00:06:20.740 align:start position:0% solution my contract contract with our 00:06:20.740 --> 00:06:23.430 align:start position:0% solution my contract contract with our do<00:06:21.070> something<00:06:21.550> function<00:06:22.090> which<00:06:22.270> might<00:06:23.140> be 00:06:23.430 --> 00:06:23.440 align:start position:0% do something function which might be 00:06:23.440 --> 00:06:25.270 align:start position:0% do something function which might be broken<00:06:23.919> with<00:06:24.640> her 00:06:25.270 --> 00:06:25.280 align:start position:0% broken with her 00:06:25.280 --> 00:06:27.790 align:start position:0% broken with her witties<00:06:25.880> just<00:06:26.389> modify<00:06:26.840> the<00:06:26.870> code<00:06:27.110> we<00:06:27.530> can<00:06:27.680> also 00:06:27.790 --> 00:06:27.800 align:start position:0% witties just modify the code we can also 00:06:27.800 --> 00:06:30.640 align:start position:0% witties just modify the code we can also add<00:06:28.010> new<00:06:28.280> functionality<00:06:29.080> and<00:06:30.080> just<00:06:30.410> run<00:06:30.620> the 00:06:30.640 --> 00:06:30.650 align:start position:0% add new functionality and just run the 00:06:30.650 --> 00:06:34.950 align:start position:0% add new functionality and just run the open<00:06:31.040> setting<00:06:31.550> up<00:06:31.790> great<00:06:32.590> command<00:06:33.590> which<00:06:34.070> will 00:06:34.950 --> 00:06:34.960 align:start position:0% open setting up great command which will 00:06:34.960 --> 00:06:39.400 align:start position:0% open setting up great command which will reload<00:06:35.960> the<00:06:36.620> new<00:06:36.800> code<00:06:37.510> in<00:06:38.510> the<00:06:38.810> exactly<00:06:39.290> same 00:06:39.400 --> 00:06:39.410 align:start position:0% reload the new code in the exactly same 00:06:39.410 --> 00:06:43.450 align:start position:0% reload the new code in the exactly same address<00:06:40.330> I'm<00:06:41.330> not<00:06:41.600> gonna<00:06:41.840> go<00:06:42.310> super<00:06:43.310> super 00:06:43.450 --> 00:06:43.460 align:start position:0% address I'm not gonna go super super 00:06:43.460 --> 00:06:46.330 align:start position:0% address I'm not gonna go super super deep<00:06:43.760> in<00:06:43.880> this<00:06:44.000> topic<00:06:44.270> you<00:06:45.139> can<00:06:45.350> afterwards 00:06:46.330 --> 00:06:46.340 align:start position:0% deep in this topic you can afterwards 00:06:46.340 --> 00:06:48.879 align:start position:0% deep in this topic you can afterwards after<00:06:46.760> the<00:06:46.790> talk<00:06:47.360> asking<00:06:48.020> questions<00:06:48.410> but<00:06:48.590> if 00:06:48.879 --> 00:06:48.889 align:start position:0% after the talk asking questions but if 00:06:48.889 --> 00:06:51.370 align:start position:0% after the talk asking questions but if you<00:06:49.040> want<00:06:49.220> to<00:06:49.370> just<00:06:49.610> see<00:06:50.240> how<00:06:50.419> it<00:06:50.600> works<00:06:50.870> you 00:06:51.370 --> 00:06:51.380 align:start position:0% you want to just see how it works you 00:06:51.380 --> 00:06:53.230 align:start position:0% you want to just see how it works you can<00:06:51.410> look<00:06:51.710> to<00:06:51.830> assembly<00:06:52.220> in<00:06:52.280> such<00:06:52.580> a<00:06:52.610> great<00:06:53.000> son 00:06:53.230 --> 00:06:53.240 align:start position:0% can look to assembly in such a great son 00:06:53.240 --> 00:06:56.190 align:start position:0% can look to assembly in such a great son that<00:06:53.840> dresser<00:06:54.230> is<00:06:54.260> a<00:06:54.380> mutation<00:06:54.770> per<00:06:55.100> unit 00:06:56.190 --> 00:06:56.200 align:start position:0% that dresser is a mutation per unit 00:06:56.200 --> 00:07:00.640 align:start position:0% that dresser is a mutation per unit anything<00:06:57.200> else<00:06:57.350> well<00:06:58.340> yeah<00:06:59.050> we<00:07:00.050> have<00:07:00.080> seen<00:07:00.500> all 00:07:00.640 --> 00:07:00.650 align:start position:0% anything else well yeah we have seen all 00:07:00.650 --> 00:07:03.580 align:start position:0% anything else well yeah we have seen all the<00:07:00.680> left<00:07:01.220> commands<00:07:01.580> yeah<00:07:02.000> at<00:07:02.840> least<00:07:03.020> this<00:07:03.410> one 00:07:03.580 --> 00:07:03.590 align:start position:0% the left commands yeah at least this one 00:07:03.590 --> 00:07:04.810 align:start position:0% the left commands yeah at least this one that<00:07:03.740> they<00:07:03.830> actually<00:07:03.950> did<00:07:04.250> create<00:07:04.520> a<00:07:04.550> great 00:07:04.810 --> 00:07:04.820 align:start position:0% that they actually did create a great 00:07:04.820 --> 00:07:06.370 align:start position:0% that they actually did create a great fall<00:07:05.060> in<00:07:05.210> central<00:07:05.510> section<00:07:05.810> but<00:07:05.990> we<00:07:06.020> also 00:07:06.370 --> 00:07:06.380 align:start position:0% fall in central section but we also 00:07:06.380 --> 00:07:08.470 align:start position:0% fall in central section but we also developed<00:07:06.950> a<00:07:07.040> lot<00:07:07.220> of<00:07:07.370> superintending<00:07:08.180> events 00:07:08.470 --> 00:07:08.480 align:start position:0% developed a lot of superintending events 00:07:08.480 --> 00:07:09.940 align:start position:0% developed a lot of superintending events for<00:07:08.660> example<00:07:08.690> moment<00:07:09.350> something<00:07:09.530> compiled 00:07:09.940 --> 00:07:09.950 align:start position:0% for example moment something compiled 00:07:09.950 --> 00:07:12.400 align:start position:0% for example moment something compiled for<00:07:10.130> competitor<00:07:10.640> contracts<00:07:11.540> with<00:07:12.050> pennies 00:07:12.400 --> 00:07:12.410 align:start position:0% for competitor contracts with pennies 00:07:12.410 --> 00:07:14.680 align:start position:0% for competitor contracts with pennies for<00:07:12.530> the<00:07:12.590> diversion<00:07:12.890> horns<00:07:13.400> open<00:07:14.000> 17<00:07:14.330> verified 00:07:14.680 --> 00:07:14.690 align:start position:0% for the diversion horns open 17 verified 00:07:14.690 --> 00:07:17.409 align:start position:0% for the diversion horns open 17 verified for<00:07:14.870> verifying<00:07:15.350> them<00:07:15.620> in<00:07:16.370> ether<00:07:16.700> scan<00:07:16.940> or<00:07:17.180> a 00:07:17.409 --> 00:07:17.419 align:start position:0% for verifying them in ether scan or a 00:07:17.419 --> 00:07:19.360 align:start position:0% for verifying them in ether scan or a third<00:07:17.630> chain<00:07:17.870> of<00:07:18.350> insomnia<00:07:18.830> comes<00:07:19.070> for 00:07:19.360 --> 00:07:19.370 align:start position:0% third chain of insomnia comes for 00:07:19.370 --> 00:07:21.730 align:start position:0% third chain of insomnia comes for listing<00:07:19.850> all<00:07:20.600> your<00:07:20.930> accounts<00:07:21.200> within<00:07:21.560> the 00:07:21.730 --> 00:07:21.740 align:start position:0% listing all your accounts within the 00:07:21.740 --> 00:07:23.650 align:start position:0% listing all your accounts within the network<00:07:22.310> open<00:07:22.640> sudden<00:07:23.090> transfer<00:07:23.450> for 00:07:23.650 --> 00:07:23.660 align:start position:0% network open sudden transfer for 00:07:23.660 --> 00:07:27.040 align:start position:0% network open sudden transfer for transparent<00:07:24.229> not<00:07:24.830> only<00:07:25.100> Navarro<00:07:25.580> also<00:07:25.850> ERC<00:07:26.780> 20 00:07:27.040 --> 00:07:27.050 align:start position:0% transparent not only Navarro also ERC 20 00:07:27.050 --> 00:07:29.550 align:start position:0% transparent not only Navarro also ERC 20 tokens<00:07:27.530> open<00:07:28.490> separately<00:07:28.790> matters<00:07:29.120> for 00:07:29.550 --> 00:07:29.560 align:start position:0% tokens open separately matters for 00:07:29.560 --> 00:07:32.050 align:start position:0% tokens open separately matters for wearing<00:07:30.560> a<00:07:30.650> valence<00:07:30.979> of<00:07:31.160> an<00:07:31.310> account<00:07:31.610> again 00:07:32.050 --> 00:07:32.060 align:start position:0% wearing a valence of an account again 00:07:32.060 --> 00:07:35.159 align:start position:0% wearing a valence of an account again teen<00:07:32.360> ether<00:07:32.720> and<00:07:32.960> in<00:07:33.500> the<00:07:33.650> RC<00:07:33.950> 20<00:07:34.220> tokens<00:07:34.640> and 00:07:35.159 --> 00:07:35.169 align:start position:0% teen ether and in the RC 20 tokens and 00:07:35.169 --> 00:07:37.900 align:start position:0% teen ether and in the RC 20 tokens and opens<00:07:36.169> at<00:07:36.320> the<00:07:36.350> impact<00:07:36.800> that<00:07:36.950> is<00:07:37.070> volatile 00:07:37.900 --> 00:07:37.910 align:start position:0% opens at the impact that is volatile 00:07:37.910 --> 00:07:44.710 align:start position:0% opens at the impact that is volatile I<00:07:37.940> don't<00:07:38.419> know<00:07:38.570> when<00:07:43.120> okay<00:07:44.120> okay 00:07:44.710 --> 00:07:44.720 align:start position:0% I don't know when okay okay 00:07:44.720 --> 00:07:47.710 align:start position:0% I don't know when okay okay so<00:07:45.110> really<00:07:45.380> pilot<00:07:46.130> who<00:07:46.460> made<00:07:46.940> this 00:07:47.710 --> 00:07:47.720 align:start position:0% so really pilot who made this 00:07:47.720 --> 00:07:49.300 align:start position:0% so really pilot who made this presentation<00:07:47.930> for<00:07:48.590> me<00:07:48.680> because<00:07:48.919> I'm<00:07:49.039> super 00:07:49.300 --> 00:07:49.310 align:start position:0% presentation for me because I'm super 00:07:49.310 --> 00:07:50.890 align:start position:0% presentation for me because I'm super lazy<00:07:49.430> for<00:07:49.669> making<00:07:49.970> my<00:07:50.120> own<00:07:50.150> presentations 00:07:50.890 --> 00:07:50.900 align:start position:0% lazy for making my own presentations 00:07:50.900 --> 00:07:53.860 align:start position:0% lazy for making my own presentations wanted<00:07:51.650> to<00:07:51.770> save<00:07:51.950> me<00:07:52.070> something<00:07:52.280> right<00:07:52.870> well 00:07:53.860 --> 00:07:53.870 align:start position:0% wanted to save me something right well 00:07:53.870 --> 00:07:58.050 align:start position:0% wanted to save me something right well basically<00:07:54.350> the<00:07:55.010> open<00:07:55.400> setting<00:07:55.760> unpack<00:07:56.240> is<00:07:56.680> the 00:07:58.050 --> 00:07:58.060 align:start position:0% basically the open setting unpack is the 00:07:58.060 --> 00:08:01.630 align:start position:0% basically the open setting unpack is the command<00:07:59.060> that<00:07:59.210> will<00:07:59.510> they<00:07:59.750> test<00:08:00.080> let<00:08:00.440> us<00:08:00.650> link 00:08:01.630 --> 00:08:01.640 align:start position:0% command that will they test let us link 00:08:01.640 --> 00:08:04.270 align:start position:0% command that will they test let us link the<00:08:02.120> open<00:08:02.390> something<00:08:02.600> SDK<00:08:03.110> with<00:08:03.500> the<00:08:03.650> open<00:08:03.890> 17 00:08:04.270 --> 00:08:04.280 align:start position:0% the open something SDK with the open 17 00:08:04.280 --> 00:08:05.080 align:start position:0% the open something SDK with the open 17 stories 00:08:05.080 --> 00:08:05.090 align:start position:0% stories 00:08:05.090 --> 00:08:08.590 align:start position:0% stories open<00:08:05.630> semanas<00:08:05.960> targets<00:08:06.380> are<00:08:06.650> basically 00:08:08.590 --> 00:08:08.600 align:start position:0% open semanas targets are basically 00:08:08.600 --> 00:08:11.890 align:start position:0% open semanas targets are basically tab<00:08:09.050> scaffoldings<00:08:09.680> that<00:08:10.640> will<00:08:10.880> let<00:08:11.090> us<00:08:11.360> charge 00:08:11.890 --> 00:08:11.900 align:start position:0% tab scaffoldings that will let us charge 00:08:11.900 --> 00:08:15.040 align:start position:0% tab scaffoldings that will let us charge our<00:08:12.140> jobs<00:08:12.470> super<00:08:13.280> super<00:08:13.550> easy<00:08:13.580> take<00:08:14.539> blue<00:08:14.780> team 00:08:15.040 --> 00:08:15.050 align:start position:0% our jobs super super easy take blue team 00:08:15.050 --> 00:08:17.110 align:start position:0% our jobs super super easy take blue team well-known<00:08:15.560> open<00:08:15.860> something<00:08:16.070> contracts<00:08:16.820> the 00:08:17.110 --> 00:08:17.120 align:start position:0% well-known open something contracts the 00:08:17.120 --> 00:08:18.709 align:start position:0% well-known open something contracts the opens<00:08:17.600> of<00:08:17.720> the<00:08:17.810> SDK 00:08:18.709 --> 00:08:18.719 align:start position:0% opens of the SDK 00:08:18.719 --> 00:08:20.869 align:start position:0% opens of the SDK and<00:08:19.049> talking<00:08:19.439> about<00:08:19.549> inferior<00:08:20.549> for 00:08:20.869 --> 00:08:20.879 align:start position:0% and talking about inferior for 00:08:20.879 --> 00:08:23.029 align:start position:0% and talking about inferior for connecting<00:08:21.239> to<00:08:21.449> any<00:08:21.569> blockchain<00:08:22.110> very<00:08:22.860> low 00:08:23.029 --> 00:08:23.039 align:start position:0% connecting to any blockchain very low 00:08:23.039 --> 00:08:27.649 align:start position:0% connecting to any blockchain very low chain<00:08:23.279> a<00:08:24.319> one-liner<00:08:25.319> that<00:08:25.739> will<00:08:26.149> allow<00:08:27.149> us<00:08:27.389> to 00:08:27.649 --> 00:08:27.659 align:start position:0% chain a one-liner that will allow us to 00:08:27.659 --> 00:08:31.009 align:start position:0% chain a one-liner that will allow us to configure<00:08:27.899> super<00:08:28.889> super<00:08:29.189> easy<00:08:29.519> for<00:08:29.729> three<00:08:30.239> we 00:08:31.009 --> 00:08:31.019 align:start position:0% configure super super easy for three we 00:08:31.019 --> 00:08:33.670 align:start position:0% configure super super easy for three we have<00:08:31.139> to<00:08:31.289> remove<00:08:31.559> for<00:08:31.769> our<00:08:31.889> front-end 00:08:33.670 --> 00:08:33.680 align:start position:0% have to remove for our front-end 00:08:33.680 --> 00:08:36.379 align:start position:0% have to remove for our front-end components<00:08:34.680> and<00:08:35.129> also<00:08:35.310> G<00:08:35.699> opens<00:08:36.089> up<00:08:36.269> the 00:08:36.379 --> 00:08:36.389 align:start position:0% components and also G opens up the 00:08:36.389 --> 00:08:38.839 align:start position:0% components and also G opens up the loader<00:08:36.899> which<00:08:37.169> is<00:08:37.349> basically<00:08:37.800> a<00:08:38.159> tool<00:08:38.669> we 00:08:38.839 --> 00:08:38.849 align:start position:0% loader which is basically a tool we 00:08:38.849 --> 00:08:41.719 align:start position:0% loader which is basically a tool we developed<00:08:39.300> for<00:08:39.930> you<00:08:40.169> to<00:08:40.610> modify<00:08:41.610> your 00:08:41.719 --> 00:08:41.729 align:start position:0% developed for you to modify your 00:08:41.729 --> 00:08:44.600 align:start position:0% developed for you to modify your contract<00:08:42.329> and<00:08:42.569> see<00:08:43.289> the<00:08:43.349> changes<00:08:43.800> of<00:08:44.069> that 00:08:44.600 --> 00:08:44.610 align:start position:0% contract and see the changes of that 00:08:44.610 --> 00:08:47.090 align:start position:0% contract and see the changes of that contract<00:08:45.060> in<00:08:45.389> your<00:08:45.449> web<00:08:45.810> app<00:08:45.959> just<00:08:46.649> saving 00:08:47.090 --> 00:08:47.100 align:start position:0% contract in your web app just saving 00:08:47.100 --> 00:08:49.340 align:start position:0% contract in your web app just saving fire<00:08:47.490> so<00:08:47.970> you<00:08:48.000> had<00:08:48.569> a<00:08:48.600> new<00:08:48.870> function<00:08:49.319> for 00:08:49.340 --> 00:08:49.350 align:start position:0% fire so you had a new function for 00:08:49.350 --> 00:08:51.019 align:start position:0% fire so you had a new function for example<00:08:49.470> that<00:08:49.829> you<00:08:49.980> are<00:08:50.009> reading<00:08:50.310> the<00:08:50.490> API<00:08:50.730> of 00:08:51.019 --> 00:08:51.029 align:start position:0% example that you are reading the API of 00:08:51.029 --> 00:08:53.559 align:start position:0% example that you are reading the API of top<00:08:51.540> contract<00:08:52.019> you<00:08:52.410> will<00:08:52.560> be<00:08:52.709> able<00:08:52.800> to<00:08:52.949> find 00:08:53.559 --> 00:08:53.569 align:start position:0% top contract you will be able to find 00:08:53.569 --> 00:08:56.150 align:start position:0% top contract you will be able to find 75c<00:08:54.569> value<00:08:54.990> function<00:08:55.350> ID<00:08:55.470> within<00:08:55.980> your 00:08:56.150 --> 00:08:56.160 align:start position:0% 75c value function ID within your 00:08:56.160 --> 00:09:00.050 align:start position:0% 75c value function ID within your website<00:08:57.589> so<00:08:58.589> super<00:08:59.069> e<00:08:59.100> seconds<00:08:59.550> you<00:08:59.610> use<00:08:59.759> with 00:09:00.050 --> 00:09:00.060 align:start position:0% website so super e seconds you use with 00:09:00.060 --> 00:09:01.730 align:start position:0% website so super e seconds you use with the<00:09:00.149> SDK<00:09:00.420> we<00:09:00.839> just<00:09:01.079> have<00:09:01.290> to<00:09:01.410> run<00:09:01.589> over 00:09:01.730 --> 00:09:01.740 align:start position:0% the SDK we just have to run over 00:09:01.740 --> 00:09:03.470 align:start position:0% the SDK we just have to run over something<00:09:02.100> on<00:09:02.430> that<00:09:02.579> starter<00:09:03.060> which<00:09:03.269> is 00:09:03.470 --> 00:09:03.480 align:start position:0% something on that starter which is 00:09:03.480 --> 00:09:06.350 align:start position:0% something on that starter which is basically<00:09:04.139> at<00:09:04.500> an<00:09:04.769> empty<00:09:05.009> version<00:09:05.730> of<00:09:06.029> the 00:09:06.350 --> 00:09:06.360 align:start position:0% basically at an empty version of the 00:09:06.360 --> 00:09:08.480 align:start position:0% basically at an empty version of the starter<00:09:06.750> kit<00:09:07.050> so<00:09:07.560> you<00:09:07.589> can<00:09:07.769> start<00:09:08.310> your 00:09:08.480 --> 00:09:08.490 align:start position:0% starter kit so you can start your 00:09:08.490 --> 00:09:11.179 align:start position:0% starter kit so you can start your project<00:09:08.730> from<00:09:09.029> from<00:09:09.449> scratch<00:09:09.720> or<00:09:10.470> open<00:09:11.040> simply 00:09:11.179 --> 00:09:11.189 align:start position:0% project from from scratch or open simply 00:09:11.189 --> 00:09:14.090 align:start position:0% project from from scratch or open simply unpack<00:09:11.579> tutorial<00:09:12.180> just<00:09:12.540> a<00:09:12.810> super<00:09:13.500> fancy<00:09:13.709> very 00:09:14.090 --> 00:09:14.100 align:start position:0% unpack tutorial just a super fancy very 00:09:14.100 --> 00:09:17.900 align:start position:0% unpack tutorial just a super fancy very we're<00:09:14.279> gonna<00:09:14.579> see<00:09:15.149> later<00:09:15.300> or<00:09:16.730> open<00:09:17.730> something 00:09:17.900 --> 00:09:17.910 align:start position:0% we're gonna see later or open something 00:09:17.910 --> 00:09:20.300 align:start position:0% we're gonna see later or open something about<00:09:18.240> GSM<00:09:18.689> and<00:09:18.959> I<00:09:19.019> am<00:09:19.139> going<00:09:19.319> to<00:09:19.379> hear<00:09:19.620> a<00:09:19.649> split 00:09:20.300 --> 00:09:20.310 align:start position:0% about GSM and I am going to hear a split 00:09:20.310 --> 00:09:22.910 align:start position:0% about GSM and I am going to hear a split earlier<00:09:20.610> because<00:09:20.939> we're<00:09:21.120> going<00:09:21.300> to<00:09:21.360> go<00:09:21.920> deeper 00:09:22.910 --> 00:09:22.920 align:start position:0% earlier because we're going to go deeper 00:09:22.920 --> 00:09:25.999 align:start position:0% earlier because we're going to go deeper every<00:09:23.189> GSM<00:09:24.029> in<00:09:24.930> a<00:09:24.990> couple<00:09:25.230> of<00:09:25.290> minutes<00:09:25.680> but 00:09:25.999 --> 00:09:26.009 align:start position:0% every GSM in a couple of minutes but 00:09:26.009 --> 00:09:28.160 align:start position:0% every GSM in a couple of minutes but just<00:09:26.309> running<00:09:26.639> MV<00:09:26.939> around<00:09:27.329> start<00:09:27.660> with<00:09:27.930> the 00:09:28.160 --> 00:09:28.170 align:start position:0% just running MV around start with the 00:09:28.170 --> 00:09:31.480 align:start position:0% just running MV around start with the trick<00:09:28.410> you<00:09:28.620> will<00:09:28.800> be<00:09:28.920> able<00:09:29.069> to<00:09:29.279> see<00:09:29.459> the<00:09:30.029> demo 00:09:31.480 --> 00:09:31.490 align:start position:0% trick you will be able to see the demo 00:09:31.490 --> 00:09:34.639 align:start position:0% trick you will be able to see the demo there<00:09:32.490> are<00:09:32.639> two<00:09:32.879> samples<00:09:33.449> for<00:09:33.870> you<00:09:34.170> to<00:09:34.410> learn 00:09:34.639 --> 00:09:34.649 align:start position:0% there are two samples for you to learn 00:09:34.649 --> 00:09:36.499 align:start position:0% there are two samples for you to learn how<00:09:34.889> to<00:09:34.980> use<00:09:35.279> the<00:09:35.399> open<00:09:35.519> second<00:09:35.939> instigator 00:09:36.499 --> 00:09:36.509 align:start position:0% how to use the open second instigator 00:09:36.509 --> 00:09:38.840 align:start position:0% how to use the open second instigator Pantera<00:09:36.990> and<00:09:37.139> even<00:09:37.439> budgies<00:09:37.949> super<00:09:38.550> easy<00:09:38.790> to 00:09:38.840 --> 00:09:38.850 align:start position:0% Pantera and even budgies super easy to 00:09:38.850 --> 00:09:42.379 align:start position:0% Pantera and even budgies super easy to understand<00:09:39.420> if<00:09:40.079> you<00:09:40.139> want<00:09:40.470> to<00:09:40.559> go<00:09:40.860> and<00:09:41.389> see 00:09:42.379 --> 00:09:42.389 align:start position:0% understand if you want to go and see 00:09:42.389 --> 00:09:44.660 align:start position:0% understand if you want to go and see what<00:09:42.720> is<00:09:42.839> this<00:09:43.079> police<00:09:43.800> go<00:09:44.040> to<00:09:44.069> assembling 00:09:44.660 --> 00:09:44.670 align:start position:0% what is this police go to assembling 00:09:44.670 --> 00:09:47.809 align:start position:0% what is this police go to assembling slash<00:09:45.029> targets<00:09:45.750> or<00:09:45.990> settling<00:09:46.649> slash<00:09:47.069> SDK<00:09:47.579> to 00:09:47.809 --> 00:09:47.819 align:start position:0% slash targets or settling slash SDK to 00:09:47.819 --> 00:09:52.460 align:start position:0% slash targets or settling slash SDK to see<00:09:48.000> was<00:09:48.360> a<00:09:48.569> 20d<00:09:49.079> SDKs<00:09:50.329> and<00:09:51.329> I<00:09:51.449> think<00:09:51.689> that<00:09:51.870> we 00:09:52.460 --> 00:09:52.470 align:start position:0% see was a 20d SDKs and I think that we 00:09:52.470 --> 00:09:55.309 align:start position:0% see was a 20d SDKs and I think that we may<00:09:52.980> have<00:09:53.339> solved<00:09:54.000> the<00:09:54.120> GX<00:09:54.480> problems<00:09:55.079> here 00:09:55.309 --> 00:09:55.319 align:start position:0% may have solved the GX problems here 00:09:55.319 --> 00:09:57.170 align:start position:0% may have solved the GX problems here mean<00:09:55.559> we<00:09:56.189> have<00:09:56.370> a<00:09:56.399> lot<00:09:56.610> of<00:09:56.639> these<00:09:56.850> problems 00:09:57.170 --> 00:09:57.180 align:start position:0% mean we have a lot of these problems 00:09:57.180 --> 00:10:00.259 align:start position:0% mean we have a lot of these problems that<00:09:57.509> maybe<00:09:57.720> you<00:09:58.589> know<00:09:58.709> now<00:09:59.129> you<00:09:59.189> can<00:09:59.519> start<00:10:00.209> a 00:10:00.259 --> 00:10:00.269 align:start position:0% that maybe you know now you can start a 00:10:00.269 --> 00:10:02.869 align:start position:0% that maybe you know now you can start a project<00:10:00.509> to<00:10:00.990> play<00:10:01.170> them<00:10:01.379> with<00:10:01.680> only<00:10:01.980> one 00:10:02.869 --> 00:10:02.879 align:start position:0% project to play them with only one 00:10:02.879 --> 00:10:03.850 align:start position:0% project to play them with only one command 00:10:03.850 --> 00:10:03.860 align:start position:0% command 00:10:03.860 --> 00:10:05.470 align:start position:0% command interact<00:10:04.190> with<00:10:04.280> things<00:10:04.760> your<00:10:04.970> equity<00:10:05.180> your 00:10:05.470 --> 00:10:05.480 align:start position:0% interact with things your equity your 00:10:05.480 --> 00:10:07.150 align:start position:0% interact with things your equity your fault<00:10:05.720> I<00:10:05.900> don't<00:10:06.170> know<00:10:06.230> man<00:10:06.410> upgrade<00:10:06.860> with 00:10:07.150 --> 00:10:07.160 align:start position:0% fault I don't know man upgrade with 00:10:07.160 --> 00:10:09.280 align:start position:0% fault I don't know man upgrade with other<00:10:07.430> command<00:10:07.880> verify<00:10:08.630> them<00:10:08.870> with<00:10:09.050> other 00:10:09.280 --> 00:10:09.290 align:start position:0% other command verify them with other 00:10:09.290 --> 00:10:12.370 align:start position:0% other command verify them with other command<00:10:09.790> but<00:10:10.790> this<00:10:11.210> doesn't<00:10:11.450> solve<00:10:11.780> I<00:10:12.080> mean 00:10:12.370 --> 00:10:12.380 align:start position:0% command but this doesn't solve I mean 00:10:12.380 --> 00:10:13.960 align:start position:0% command but this doesn't solve I mean this<00:10:12.620> is<00:10:12.740> solving<00:10:13.040> our<00:10:13.250> problems<00:10:13.850> as 00:10:13.960 --> 00:10:13.970 align:start position:0% this is solving our problems as 00:10:13.970 --> 00:10:16.090 align:start position:0% this is solving our problems as developers<00:10:14.570> but<00:10:15.200> what<00:10:15.350> about<00:10:15.560> the<00:10:15.710> product 00:10:16.090 --> 00:10:16.100 align:start position:0% developers but what about the product 00:10:16.100 --> 00:10:18.700 align:start position:0% developers but what about the product usage<00:10:17.000> like<00:10:17.210> real<00:10:17.540> people<00:10:17.750> tasks<00:10:18.140> by<00:10:18.650> the 00:10:18.700 --> 00:10:18.710 align:start position:0% usage like real people tasks by the 00:10:18.710 --> 00:10:22.030 align:start position:0% usage like real people tasks by the people<00:10:19.100> that<00:10:19.130> everyday<00:10:19.910> exceeds<00:10:20.390> in<00:10:21.040> their 00:10:22.030 --> 00:10:22.040 align:start position:0% people that everyday exceeds in their 00:10:22.040 --> 00:10:25.120 align:start position:0% people that everyday exceeds in their desktops<00:10:22.700> or<00:10:22.910> laptops<00:10:23.740> for<00:10:24.740> example<00:10:25.040> my 00:10:25.120 --> 00:10:25.130 align:start position:0% desktops or laptops for example my 00:10:25.130 --> 00:10:28.900 align:start position:0% desktops or laptops for example my father<00:10:25.690> which<00:10:26.690> by<00:10:27.680> the<00:10:27.740> way<00:10:27.800> loves<00:10:28.250> to<00:10:28.460> buy 00:10:28.900 --> 00:10:28.910 align:start position:0% father which by the way loves to buy 00:10:28.910 --> 00:10:31.840 align:start position:0% father which by the way loves to buy stuff<00:10:29.330> in<00:10:29.390> the<00:10:29.630> internet<00:10:30.020> I'm<00:10:30.980> from<00:10:31.670> when 00:10:31.840 --> 00:10:31.850 align:start position:0% stuff in the internet I'm from when 00:10:31.850 --> 00:10:34.300 align:start position:0% stuff in the internet I'm from when Cyrus<00:10:32.240> Argentina<00:10:32.930> we<00:10:33.440> don't<00:10:33.620> have<00:10:33.740> Amazon 00:10:34.300 --> 00:10:34.310 align:start position:0% Cyrus Argentina we don't have Amazon 00:10:34.310 --> 00:10:37.090 align:start position:0% Cyrus Argentina we don't have Amazon there<00:10:35.000> but<00:10:35.270> we<00:10:35.390> have<00:10:35.540> a<00:10:35.570> person<00:10:36.470> our<00:10:36.650> website 00:10:37.090 --> 00:10:37.100 align:start position:0% there but we have a person our website 00:10:37.100 --> 00:10:38.980 align:start position:0% there but we have a person our website that<00:10:37.250> is<00:10:37.280> calm<00:10:37.670> and<00:10:37.880> probably<00:10:38.210> wouldn't<00:10:38.450> that 00:10:38.980 --> 00:10:38.990 align:start position:0% that is calm and probably wouldn't that 00:10:38.990 --> 00:10:40.900 align:start position:0% that is calm and probably wouldn't that basically<00:10:39.350> is<00:10:39.710> acceptance<00:10:40.220> and<00:10:40.400> you<00:10:40.550> can<00:10:40.760> buy 00:10:40.900 --> 00:10:40.910 align:start position:0% basically is acceptance and you can buy 00:10:40.910 --> 00:10:43.180 align:start position:0% basically is acceptance and you can buy whatever<00:10:41.120> you<00:10:41.330> want<00:10:41.390> or<00:10:42.140> I<00:10:42.170> don't<00:10:42.440> know<00:10:42.590> food 00:10:43.180 --> 00:10:43.190 align:start position:0% whatever you want or I don't know food 00:10:43.190 --> 00:10:46.720 align:start position:0% whatever you want or I don't know food stuff<00:10:44.150> and<00:10:44.450> just<00:10:45.410> by<00:10:45.770> adding<00:10:46.040> your<00:10:46.280> credit 00:10:46.720 --> 00:10:46.730 align:start position:0% stuff and just by adding your credit 00:10:46.730 --> 00:10:47.980 align:start position:0% stuff and just by adding your credit card<00:10:46.940> using<00:10:47.240> your<00:10:47.360> credit<00:10:47.600> card<00:10:47.780> you<00:10:47.960> can 00:10:47.980 --> 00:10:47.990 align:start position:0% card using your credit card you can 00:10:47.990 --> 00:10:50.920 align:start position:0% card using your credit card you can picture<00:10:48.650> stuff<00:10:49.010> in<00:10:49.640> your<00:10:49.760> home<00:10:50.000> life<00:10:50.240> two<00:10:50.780> days 00:10:50.920 --> 00:10:50.930 align:start position:0% picture stuff in your home life two days 00:10:50.930 --> 00:10:55.690 align:start position:0% picture stuff in your home life two days later<00:10:51.230> but<00:10:52.480> what<00:10:53.480> about<00:10:54.220> by<00:10:55.220> the<00:10:55.280> way<00:10:55.400> my<00:10:55.550> that 00:10:55.690 --> 00:10:55.700 align:start position:0% later but what about by the way my that 00:10:55.700 --> 00:10:58.990 align:start position:0% later but what about by the way my that is<00:10:55.790> 73<00:10:56.480> years<00:10:56.510> old<00:10:56.930> so<00:10:57.170> what<00:10:57.680> would<00:10:58.190> happen<00:10:58.610> to 00:10:58.990 --> 00:10:59.000 align:start position:0% is 73 years old so what would happen to 00:10:59.000 --> 00:11:02.160 align:start position:0% is 73 years old so what would happen to him<00:10:59.210> if<00:10:59.240> he's<00:11:00.110> in<00:11:00.260> his<00:11:00.380> computer<00:11:00.830> and<00:11:01.040> he<00:11:01.220> sees 00:11:02.160 --> 00:11:02.170 align:start position:0% him if he's in his computer and he sees 00:11:02.170 --> 00:11:06.670 align:start position:0% him if he's in his computer and he sees Jesus<00:11:03.170> pops<00:11:03.560> like<00:11:04.360> what<00:11:05.360> the<00:11:05.650> what<00:11:06.650> the 00:11:06.670 --> 00:11:06.680 align:start position:0% Jesus pops like what the what the 00:11:06.680 --> 00:11:08.350 align:start position:0% Jesus pops like what the what the is<00:11:06.950> minimized<00:11:07.400> what<00:11:07.640> the<00:11:07.880> are<00:11:08.060> my 00:11:08.350 --> 00:11:08.360 align:start position:0% is minimized what the are my 00:11:08.360 --> 00:11:11.260 align:start position:0% is minimized what the are my monies<00:11:08.780> Woody's<00:11:09.770> private<00:11:10.670> keys<00:11:10.880> with<00:11:11.120> our 00:11:11.260 --> 00:11:11.270 align:start position:0% monies Woody's private keys with our 00:11:11.270 --> 00:11:13.870 align:start position:0% monies Woody's private keys with our private<00:11:11.510> keys<00:11:11.780> spur<00:11:12.560> counters<00:11:13.100> have<00:11:13.280> for<00:11:13.730> him 00:11:13.870 --> 00:11:13.880 align:start position:0% private keys spur counters have for him 00:11:13.880 --> 00:11:15.700 align:start position:0% private keys spur counters have for him not<00:11:14.360> for<00:11:14.420> us<00:11:14.660> because<00:11:14.930> we're<00:11:15.110> developers<00:11:15.470> but 00:11:15.700 --> 00:11:15.710 align:start position:0% not for us because we're developers but 00:11:15.710 --> 00:11:17.380 align:start position:0% not for us because we're developers but for<00:11:15.890> a<00:11:15.950> real<00:11:16.100> user<00:11:16.370> it<00:11:16.700> will<00:11:16.880> be<00:11:17.030> super 00:11:17.380 --> 00:11:17.390 align:start position:0% for a real user it will be super 00:11:17.390 --> 00:11:19.510 align:start position:0% for a real user it will be super Congress<00:11:17.720> on<00:11:17.870> so<00:11:18.620> my<00:11:18.800> dad<00:11:19.010> will<00:11:19.220> be<00:11:19.250> sad 00:11:19.510 --> 00:11:19.520 align:start position:0% Congress on so my dad will be sad 00:11:19.520 --> 00:11:21.460 align:start position:0% Congress on so my dad will be sad because<00:11:19.760> he<00:11:20.120> won't<00:11:20.360> be<00:11:20.510> able<00:11:20.630> to<00:11:20.900> like<00:11:21.050> his<00:11:21.230> tab 00:11:21.460 --> 00:11:21.470 align:start position:0% because he won't be able to like his tab 00:11:21.470 --> 00:11:23.710 align:start position:0% because he won't be able to like his tab and<00:11:21.710> the<00:11:22.130> post<00:11:22.340> will<00:11:22.610> troll<00:11:22.880> him<00:11:23.090> and<00:11:23.540> that's 00:11:23.710 --> 00:11:23.720 align:start position:0% and the post will troll him and that's 00:11:23.720 --> 00:11:27.850 align:start position:0% and the post will troll him and that's not<00:11:23.870> good<00:11:24.140> so<00:11:24.760> it's<00:11:25.760> a<00:11:25.880> pact<00:11:26.120> and<00:11:26.470> it's<00:11:27.470> well 00:11:27.850 --> 00:11:27.860 align:start position:0% not good so it's a pact and it's well 00:11:27.860 --> 00:11:29.980 align:start position:0% not good so it's a pact and it's well known<00:11:28.130> fact<00:11:28.490> by<00:11:28.700> the<00:11:28.760> way<00:11:28.880> that<00:11:29.180> we<00:11:29.420> lose<00:11:29.600> the 00:11:29.980 --> 00:11:29.990 align:start position:0% known fact by the way that we lose the 00:11:29.990 --> 00:11:31.690 align:start position:0% known fact by the way that we lose the ninety<00:11:30.290> percent<00:11:30.440> of<00:11:30.710> our<00:11:30.830> users<00:11:31.070> in<00:11:31.610> the 00:11:31.690 --> 00:11:31.700 align:start position:0% ninety percent of our users in the 00:11:31.700 --> 00:11:37.180 align:start position:0% ninety percent of our users in the install<00:11:32.150> America's<00:11:32.630> image<00:11:35.590> clearly<00:11:36.590> what<00:11:37.010> we 00:11:37.180 --> 00:11:37.190 align:start position:0% install America's image clearly what we 00:11:37.190 --> 00:11:39.640 align:start position:0% install America's image clearly what we are<00:11:37.280> missing<00:11:37.460> is<00:11:37.760> user<00:11:38.090> experience<00:11:38.650> that's 00:11:39.640 --> 00:11:39.650 align:start position:0% are missing is user experience that's 00:11:39.650 --> 00:11:42.580 align:start position:0% are missing is user experience that's why<00:11:39.890> I'm<00:11:40.760> super<00:11:41.420> happy<00:11:41.540> to<00:11:41.810> introduce<00:11:42.050> you<00:11:42.440> to 00:11:42.580 --> 00:11:42.590 align:start position:0% why I'm super happy to introduce you to 00:11:42.590 --> 00:11:44.560 align:start position:0% why I'm super happy to introduce you to the<00:11:42.710> gas<00:11:42.920> station<00:11:43.460> Network<00:11:43.820> which<00:11:44.210> is<00:11:44.390> the 00:11:44.560 --> 00:11:44.570 align:start position:0% the gas station Network which is the 00:11:44.570 --> 00:11:46.300 align:start position:0% the gas station Network which is the ultimate<00:11:45.050> on<00:11:45.290> word<00:11:45.470> resolution<00:11:45.980> 43 00:11:46.300 --> 00:11:46.310 align:start position:0% ultimate on word resolution 43 00:11:46.310 --> 00:11:51.400 align:start position:0% ultimate on word resolution 43 obligations<00:11:47.410> basically<00:11:48.410> the<00:11:48.560> GSM<00:11:49.010> is<00:11:49.790> a<00:11:50.410> great 00:11:51.400 --> 00:11:51.410 align:start position:0% obligations basically the GSM is a great 00:11:51.410 --> 00:11:53.050 align:start position:0% obligations basically the GSM is a great contract<00:11:51.980> architecture<00:11:52.580> in<00:11:52.760> the<00:11:52.850> blockchain 00:11:53.050 --> 00:11:53.060 align:start position:0% contract architecture in the blockchain 00:11:53.060 --> 00:11:56.240 align:start position:0% contract architecture in the blockchain that<00:11:53.450> was<00:11:53.660> first<00:11:54.590> developed<00:11:54.920> right 00:11:56.240 --> 00:11:56.250 align:start position:0% that was first developed right 00:11:56.250 --> 00:12:00.650 align:start position:0% that was first developed right developer<00:11:56.760> by<00:11:57.150> an<00:11:57.450> alliance<00:11:57.720> of<00:11:59.120> companies<00:12:00.120> to 00:12:00.650 --> 00:12:00.660 align:start position:0% developer by an alliance of companies to 00:12:00.660 --> 00:12:03.740 align:start position:0% developer by an alliance of companies to compensate<00:12:01.260> the<00:12:01.380> employees<00:12:01.850> Peter<00:12:02.850> for 00:12:03.740 --> 00:12:03.750 align:start position:0% compensate the employees Peter for 00:12:03.750 --> 00:12:07.640 align:start position:0% compensate the employees Peter for solving<00:12:04.200> the<00:12:04.560> user<00:12:05.220> awarding<00:12:05.790> problem<00:12:06.650> I'm 00:12:07.640 --> 00:12:07.650 align:start position:0% solving the user awarding problem I'm 00:12:07.650 --> 00:12:09.650 align:start position:0% solving the user awarding problem I'm gonna<00:12:07.890> give<00:12:08.310> you<00:12:08.460> a<00:12:08.490> brief<00:12:08.880> everything 00:12:09.650 --> 00:12:09.660 align:start position:0% gonna give you a brief everything 00:12:09.660 --> 00:12:12.350 align:start position:0% gonna give you a brief everything protection<00:12:10.080> about<00:12:10.260> this<00:12:10.610> basically<00:12:11.610> the<00:12:11.820> GSM 00:12:12.350 --> 00:12:12.360 align:start position:0% protection about this basically the GSM 00:12:12.360 --> 00:12:15.680 align:start position:0% protection about this basically the GSM is<00:12:13.340> composed<00:12:14.340> by<00:12:14.520> a<00:12:14.640> centralized<00:12:15.330> group<00:12:15.540> of 00:12:15.680 --> 00:12:15.690 align:start position:0% is composed by a centralized group of 00:12:15.690 --> 00:12:18.410 align:start position:0% is composed by a centralized group of three<00:12:15.960> layers<00:12:16.140> who<00:12:17.070> are<00:12:17.520> paid<00:12:17.880> for<00:12:18.060> millions 00:12:18.410 --> 00:12:18.420 align:start position:0% three layers who are paid for millions 00:12:18.420 --> 00:12:20.900 align:start position:0% three layers who are paid for millions on<00:12:18.540> sections<00:12:18.900> we're<00:12:19.050> gonna<00:12:19.230> go<00:12:19.380> deeper<00:12:19.910> into 00:12:20.900 --> 00:12:20.910 align:start position:0% on sections we're gonna go deeper into 00:12:20.910 --> 00:12:23.300 align:start position:0% on sections we're gonna go deeper into this<00:12:21.150> later<00:12:21.480> but<00:12:22.200> believe<00:12:22.740> me<00:12:22.770> they<00:12:23.010> are<00:12:23.040> like 00:12:23.300 --> 00:12:23.310 align:start position:0% this later but believe me they are like 00:12:23.310 --> 00:12:27.170 align:start position:0% this later but believe me they are like you<00:12:24.120> know<00:12:24.210> frilliness<00:12:24.890> a<00:12:25.890> single<00:12:26.730> unaudited 00:12:27.170 --> 00:12:27.180 align:start position:0% you know frilliness a single unaudited 00:12:27.180 --> 00:12:29.930 align:start position:0% you know frilliness a single unaudited by<00:12:27.420> open<00:12:28.410> 17<00:12:28.770> contract<00:12:29.250> or<00:12:29.400> coordinated 00:12:29.930 --> 00:12:29.940 align:start position:0% by open 17 contract or coordinated 00:12:29.940 --> 00:12:32.470 align:start position:0% by open 17 contract or coordinated everything<00:12:30.330> that<00:12:30.450> is<00:12:30.540> called<00:12:30.780> the<00:12:30.870> relay<00:12:31.260> hub 00:12:32.470 --> 00:12:32.480 align:start position:0% everything that is called the relay hub 00:12:32.480 --> 00:12:35.840 align:start position:0% everything that is called the relay hub your<00:12:33.480> jobs<00:12:34.010> will<00:12:35.010> pay<00:12:35.280> for<00:12:35.670> their<00:12:35.820> own 00:12:35.840 --> 00:12:35.850 align:start position:0% your jobs will pay for their own 00:12:35.850 --> 00:12:37.730 align:start position:0% your jobs will pay for their own transactions<00:12:36.480> I<00:12:36.600> mean<00:12:36.720> if<00:12:36.930> I<00:12:37.080> made<00:12:37.320> an<00:12:37.410> app<00:12:37.560> I 00:12:37.730 --> 00:12:37.740 align:start position:0% transactions I mean if I made an app I 00:12:37.740 --> 00:12:39.920 align:start position:0% transactions I mean if I made an app I attack<00:12:38.400> I<00:12:38.610> will<00:12:38.850> pay<00:12:39.030> for<00:12:39.090> the<00:12:39.330> transactions 00:12:39.920 --> 00:12:39.930 align:start position:0% attack I will pay for the transactions 00:12:39.930 --> 00:12:41.570 align:start position:0% attack I will pay for the transactions not<00:12:40.770> to<00:12:40.920> you<00:12:41.040> sir 00:12:41.570 --> 00:12:41.580 align:start position:0% not to you sir 00:12:41.580 --> 00:12:44.660 align:start position:0% not to you sir so<00:12:42.480> my<00:12:42.690> dad<00:12:42.870> doesn't<00:12:43.140> have<00:12:43.470> to<00:12:43.680> or<00:12:44.040> any<00:12:44.340> user 00:12:44.660 --> 00:12:44.670 align:start position:0% so my dad doesn't have to or any user 00:12:44.670 --> 00:12:46.010 align:start position:0% so my dad doesn't have to or any user doesn't<00:12:44.880> happy<00:12:45.210> that<00:12:45.390> doesn't<00:12:45.720> have<00:12:45.840> to 00:12:46.010 --> 00:12:46.020 align:start position:0% doesn't happy that doesn't have to 00:12:46.020 --> 00:12:47.750 align:start position:0% doesn't happy that doesn't have to struggle<00:12:46.620> with<00:12:46.770> the<00:12:46.920> pulse<00:12:47.130> which<00:12:47.400> is<00:12:47.430> crazy 00:12:47.750 --> 00:12:47.760 align:start position:0% struggle with the pulse which is crazy 00:12:47.760 --> 00:12:52.150 align:start position:0% struggle with the pulse which is crazy so<00:12:48.750> let's<00:12:49.230> go<00:12:49.410> and<00:12:49.820> see<00:12:50.820> how<00:12:51.420> does<00:12:51.690> it<00:12:51.720> work 00:12:52.150 --> 00:12:52.160 align:start position:0% so let's go and see how does it work 00:12:52.160 --> 00:12:55.190 align:start position:0% so let's go and see how does it work these<00:12:53.160> however<00:12:53.340> players<00:12:53.820> are<00:12:54.420> used<00:12:54.750> to<00:12:54.870> my<00:12:55.050> dad 00:12:55.190 --> 00:12:55.200 align:start position:0% these however players are used to my dad 00:12:55.200 --> 00:12:57.350 align:start position:0% these however players are used to my dad every<00:12:55.860> day<00:12:55.890> urge<00:12:56.220> every<00:12:56.550> day<00:12:56.700> hat<00:12:56.940> and<00:12:57.240> they're 00:12:57.350 --> 00:12:57.360 align:start position:0% every day urge every day hat and they're 00:12:57.360 --> 00:12:58.640 align:start position:0% every day urge every day hat and they're receiving<00:12:57.570> a<00:12:57.750> contract<00:12:58.110> which<00:12:58.230> is<00:12:58.260> our 00:12:58.640 --> 00:12:58.650 align:start position:0% receiving a contract which is our 00:12:58.650 --> 00:13:00.170 align:start position:0% receiving a contract which is our smartphone<00:12:59.220> direct<00:12:59.430> at<00:12:59.550> least<00:12:59.700> linked<00:13:00.030> it<00:13:00.150> to 00:13:00.170 --> 00:13:00.180 align:start position:0% smartphone direct at least linked it to 00:13:00.180 --> 00:13:03.290 align:start position:0% smartphone direct at least linked it to a<00:13:00.330> hotel<00:13:01.250> we<00:13:02.250> don't<00:13:02.460> know<00:13:02.640> how<00:13:02.880> a<00:13:02.910> regular 00:13:03.290 --> 00:13:03.300 align:start position:0% a hotel we don't know how a regular 00:13:03.300 --> 00:13:06.410 align:start position:0% a hotel we don't know how a regular transection<00:13:04.050> works<00:13:04.430> and<00:13:05.430> that<00:13:05.640> choice<00:13:06.030> to 00:13:06.410 --> 00:13:06.420 align:start position:0% transection works and that choice to 00:13:06.420 --> 00:13:10.220 align:start position:0% transection works and that choice to minimize<00:13:07.220> mana<00:13:08.220> must<00:13:08.370> help<00:13:08.910> him<00:13:09.270> help<00:13:09.930> scheme 00:13:10.220 --> 00:13:10.230 align:start position:0% minimize mana must help him help scheme 00:13:10.230 --> 00:13:12.050 align:start position:0% minimize mana must help him help scheme to<00:13:10.470> talk<00:13:11.100> with<00:13:11.310> the<00:13:11.370> contracting<00:13:11.820> with<00:13:11.910> your 00:13:12.050 --> 00:13:12.060 align:start position:0% to talk with the contracting with your 00:13:12.060 --> 00:13:14.570 align:start position:0% to talk with the contracting with your look<00:13:12.300> change<00:13:12.330> we<00:13:13.170> also<00:13:13.290> know<00:13:13.500> how<00:13:13.710> manage<00:13:14.520> from 00:13:14.570 --> 00:13:14.580 align:start position:0% look change we also know how manage from 00:13:14.580 --> 00:13:16.280 align:start position:0% look change we also know how manage from sanctions<00:13:14.880> pretty<00:13:15.210> dramatic<00:13:15.780> from<00:13:15.930> sections 00:13:16.280 --> 00:13:16.290 align:start position:0% sanctions pretty dramatic from sections 00:13:16.290 --> 00:13:16.670 align:start position:0% sanctions pretty dramatic from sections work 00:13:16.670 --> 00:13:16.680 align:start position:0% work 00:13:16.680 --> 00:13:18.620 align:start position:0% work I<00:13:16.710> got<00:13:17.070> will<00:13:17.250> talked<00:13:17.580> with<00:13:17.790> re<00:13:18.030> layer<00:13:18.180> under<00:13:18.600> a 00:13:18.620 --> 00:13:18.630 align:start position:0% I got will talked with re layer under a 00:13:18.630 --> 00:13:20.000 align:start position:0% I got will talked with re layer under a layer<00:13:18.839> we<00:13:19.080> talked<00:13:19.589> with<00:13:19.740> the<00:13:19.830> blockchain 00:13:20.000 --> 00:13:20.010 align:start position:0% layer we talked with the blockchain 00:13:20.010 --> 00:13:22.850 align:start position:0% layer we talked with the blockchain maybe<00:13:20.370> or<00:13:21.120> probably<00:13:21.570> using<00:13:21.900> an<00:13:22.050> identity 00:13:22.850 --> 00:13:22.860 align:start position:0% maybe or probably using an identity 00:13:22.860 --> 00:13:26.900 align:start position:0% maybe or probably using an identity contract<00:13:23.600> assigned<00:13:24.600> for<00:13:24.780> my<00:13:24.900> dad<00:13:25.880> did<00:13:26.880> you 00:13:26.900 --> 00:13:26.910 align:start position:0% contract assigned for my dad did you 00:13:26.910 --> 00:13:29.870 align:start position:0% contract assigned for my dad did you send<00:13:27.240> militant<00:13:27.660> section<00:13:28.550> solution<00:13:29.550> works 00:13:29.870 --> 00:13:29.880 align:start position:0% send militant section solution works 00:13:29.880 --> 00:13:33.350 align:start position:0% send militant section solution works slightly<00:13:30.420> different<00:13:31.050> basically<00:13:31.740> my<00:13:32.160> dad<00:13:32.370> will 00:13:33.350 --> 00:13:33.360 align:start position:0% slightly different basically my dad will 00:13:33.360 --> 00:13:35.600 align:start position:0% slightly different basically my dad will talk<00:13:33.780> to<00:13:33.930> her<00:13:34.020> later<00:13:34.440> this<00:13:34.920> relator<00:13:35.310> will 00:13:35.600 --> 00:13:35.610 align:start position:0% talk to her later this relator will 00:13:35.610 --> 00:13:38.060 align:start position:0% talk to her later this relator will check<00:13:35.970> whether<00:13:36.630> or<00:13:36.870> not<00:13:36.900> the<00:13:37.140> recipient 00:13:38.060 --> 00:13:38.070 align:start position:0% check whether or not the recipient 00:13:38.070 --> 00:13:41.480 align:start position:0% check whether or not the recipient contract<00:13:38.820> has<00:13:39.089> funds<00:13:39.839> for<00:13:40.490> payment 00:13:41.480 --> 00:13:41.490 align:start position:0% contract has funds for payment 00:13:41.490 --> 00:13:44.570 align:start position:0% contract has funds for payment transaction<00:13:41.670> fees<00:13:42.120> and<00:13:42.560> to<00:13:43.560> pay<00:13:43.740> Gerry<00:13:44.280> later 00:13:44.570 --> 00:13:44.580 align:start position:0% transaction fees and to pay Gerry later 00:13:44.580 --> 00:13:46.970 align:start position:0% transaction fees and to pay Gerry later fee<00:13:44.940> because<00:13:45.150> here<00:13:45.570> we<00:13:45.690> have<00:13:45.870> very<00:13:46.140> little<00:13:46.440> if 00:13:46.970 --> 00:13:46.980 align:start position:0% fee because here we have very little if 00:13:46.980 --> 00:13:49.190 align:start position:0% fee because here we have very little if you're<00:13:47.280> later<00:13:47.700> if<00:13:47.940> you<00:13:48.030> want<00:13:48.240> to<00:13:48.390> start<00:13:49.020> up 00:13:49.190 --> 00:13:49.200 align:start position:0% you're later if you want to start up 00:13:49.200 --> 00:13:51.050 align:start position:0% you're later if you want to start up every<00:13:49.589> day<00:13:49.710> or<00:13:49.860> just<00:13:49.890> to<00:13:50.550> go<00:13:50.670> easy<00:13:50.790> treatment 00:13:51.050 --> 00:13:51.060 align:start position:0% every day or just to go easy treatment 00:13:51.060 --> 00:13:57.560 align:start position:0% every day or just to go easy treatment to<00:13:51.360> me<00:13:51.510> like<00:13:52.290> I<00:13:52.650> never<00:13:52.980> five-minute<00:13:53.610> thing<00:13:56.570> you 00:13:57.560 --> 00:13:57.570 align:start position:0% to me like I never five-minute thing you 00:13:57.570 --> 00:14:00.920 align:start position:0% to me like I never five-minute thing you will<00:13:57.780> be<00:13:57.870> able<00:13:58.020> to<00:13:58.370> actually<00:13:59.600> get<00:14:00.600> paid<00:14:00.870> for 00:14:00.920 --> 00:14:00.930 align:start position:0% will be able to actually get paid for 00:14:00.930 --> 00:14:01.769 align:start position:0% will be able to actually get paid for those 00:14:01.769 --> 00:14:01.779 align:start position:0% those 00:14:01.779 --> 00:14:04.470 align:start position:0% those you<00:14:02.199> relate<00:14:02.470> so<00:14:02.649> if<00:14:02.829> you<00:14:02.949> have<00:14:03.160> 100<00:14:03.670> real<00:14:04.209> acres 00:14:04.470 --> 00:14:04.480 align:start position:0% you relate so if you have 100 real acres 00:14:04.480 --> 00:14:05.999 align:start position:0% you relate so if you have 100 real acres and<00:14:04.779> there<00:14:04.959> are<00:14:05.019> a<00:14:05.050> lot<00:14:05.259> of<00:14:05.290> transactions<00:14:05.889> on 00:14:05.999 --> 00:14:06.009 align:start position:0% and there are a lot of transactions on 00:14:06.009 --> 00:14:08.910 align:start position:0% and there are a lot of transactions on pure<00:14:06.339> relating<00:14:06.910> you<00:14:07.360> will<00:14:07.569> be<00:14:08.290> winning 00:14:08.910 --> 00:14:08.920 align:start position:0% pure relating you will be winning 00:14:08.920 --> 00:14:13.290 align:start position:0% pure relating you will be winning earning<00:14:09.579> money<00:14:10.170> so<00:14:11.610> as<00:14:12.610> I<00:14:12.759> was<00:14:12.850> saying<00:14:12.910> earlier 00:14:13.290 --> 00:14:13.300 align:start position:0% earning money so as I was saying earlier 00:14:13.300 --> 00:14:15.660 align:start position:0% earning money so as I was saying earlier will<00:14:14.079> check<00:14:14.649> whether<00:14:14.920> or<00:14:15.160> not<00:14:15.189> the<00:14:15.459> recipient 00:14:15.660 --> 00:14:15.670 align:start position:0% will check whether or not the recipient 00:14:15.670 --> 00:14:19.650 align:start position:0% will check whether or not the recipient contract<00:14:16.269> has<00:14:17.259> funds<00:14:17.980> to<00:14:18.339> pay<00:14:18.519> for<00:14:19.209> these 00:14:19.650 --> 00:14:19.660 align:start position:0% contract has funds to pay for these 00:14:19.660 --> 00:14:23.189 align:start position:0% contract has funds to pay for these transaction<00:14:20.350> fee<00:14:20.740> and<00:14:21.009> earlier<00:14:21.459> fee<00:14:21.699> and<00:14:22.199> it 00:14:23.189 --> 00:14:23.199 align:start position:0% transaction fee and earlier fee and it 00:14:23.199 --> 00:14:26.129 align:start position:0% transaction fee and earlier fee and it does<00:14:23.910> generally<00:14:24.910> not<00:14:25.209> every<00:14:25.540> day<00:14:25.660> have<00:14:25.930> this 00:14:26.129 --> 00:14:26.139 align:start position:0% does generally not every day have this 00:14:26.139 --> 00:14:27.569 align:start position:0% does generally not every day have this contract<00:14:26.649> release 00:14:27.569 --> 00:14:27.579 align:start position:0% contract release 00:14:27.579 --> 00:14:30.329 align:start position:0% contract release by<00:14:27.850> the<00:14:27.910> way<00:14:28.230> deployed<00:14:29.230> by<00:14:29.410> us<00:14:29.620> in<00:14:29.949> every 00:14:30.329 --> 00:14:30.339 align:start position:0% by the way deployed by us in every 00:14:30.339 --> 00:14:32.280 align:start position:0% by the way deployed by us in every single<00:14:30.370> motion<00:14:30.790> and<00:14:31.360> its<00:14:31.480> unique<00:14:31.870> there's 00:14:32.280 --> 00:14:32.290 align:start position:0% single motion and its unique there's 00:14:32.290 --> 00:14:35.220 align:start position:0% single motion and its unique there's only<00:14:32.589> one<00:14:32.800> for<00:14:33.069> each<00:14:33.249> ball<00:14:33.519> chain<00:14:33.759> will<00:14:34.600> do<00:14:34.809> the 00:14:35.220 --> 00:14:35.230 align:start position:0% only one for each ball chain will do the 00:14:35.230 --> 00:14:37.530 align:start position:0% only one for each ball chain will do the several<00:14:35.589> checks<00:14:35.860> for<00:14:36.009> example<00:14:36.430> if<00:14:36.999> the<00:14:37.240> relay 00:14:37.530 --> 00:14:37.540 align:start position:0% several checks for example if the relay 00:14:37.540 --> 00:14:41.069 align:start position:0% several checks for example if the relay called<00:14:37.870> is<00:14:38.800> legitimate<00:14:39.459> and<00:14:40.120> afterwards<00:14:40.629> it 00:14:41.069 --> 00:14:41.079 align:start position:0% called is legitimate and afterwards it 00:14:41.079 --> 00:14:43.230 align:start position:0% called is legitimate and afterwards it will<00:14:41.290> ask<00:14:41.800> the<00:14:42.160> recipient<00:14:42.610> contract<00:14:43.089> whether 00:14:43.230 --> 00:14:43.240 align:start position:0% will ask the recipient contract whether 00:14:43.240 --> 00:14:46.069 align:start position:0% will ask the recipient contract whether or<00:14:43.449> not<00:14:43.569> it<00:14:44.079> wants<00:14:44.350> to<00:14:44.800> accept<00:14:45.189> a<00:14:45.309> relay<00:14:45.550> call 00:14:46.069 --> 00:14:46.079 align:start position:0% or not it wants to accept a relay call 00:14:46.079 --> 00:14:50.639 align:start position:0% or not it wants to accept a relay call if<00:14:47.079> it<00:14:47.290> does<00:14:47.819> well<00:14:48.819> it<00:14:49.600> will<00:14:49.839> actually<00:14:50.139> send 00:14:50.639 --> 00:14:50.649 align:start position:0% if it does well it will actually send 00:14:50.649 --> 00:14:52.590 align:start position:0% if it does well it will actually send the<00:14:50.800> relay<00:14:51.009> call<00:14:51.220> to<00:14:51.339> the<00:14:51.430> contract<00:14:51.910> to<00:14:52.509> the 00:14:52.590 --> 00:14:52.600 align:start position:0% the relay call to the contract to the 00:14:52.600 --> 00:14:56.220 align:start position:0% the relay call to the contract to the recipient<00:14:53.079> contract<00:14:53.529> and<00:14:54.120> the<00:14:55.120> receive<00:14:55.779> under 00:14:56.220 --> 00:14:56.230 align:start position:0% recipient contract and the receive under 00:14:56.230 --> 00:14:59.249 align:start position:0% recipient contract and the receive under a<00:14:56.259> hub<00:14:56.829> will<00:14:57.129> be<00:14:57.339> able<00:14:57.730> to<00:14:58.029> pay<00:14:58.209> earlier<00:14:58.689> for 00:14:59.249 --> 00:14:59.259 align:start position:0% a hub will be able to pay earlier for 00:14:59.259 --> 00:15:02.970 align:start position:0% a hub will be able to pay earlier for that<00:14:59.490> transaction<00:15:01.110> so<00:15:02.110> basically<00:15:02.559> it's<00:15:02.800> the 00:15:02.970 --> 00:15:02.980 align:start position:0% that transaction so basically it's the 00:15:02.980 --> 00:15:05.129 align:start position:0% that transaction so basically it's the meta<00:15:03.249> transactions<00:15:03.910> on<00:15:04.059> roids<00:15:04.269> because<00:15:04.720> you 00:15:05.129 --> 00:15:05.139 align:start position:0% meta transactions on roids because you 00:15:05.139 --> 00:15:07.980 align:start position:0% meta transactions on roids because you don't<00:15:05.319> have<00:15:05.499> you<00:15:06.269> and<00:15:07.269> when<00:15:07.420> I<00:15:07.449> say<00:15:07.660> you<00:15:07.720> is 00:15:07.980 --> 00:15:07.990 align:start position:0% don't have you and when I say you is 00:15:07.990 --> 00:15:10.290 align:start position:0% don't have you and when I say you is basically<00:15:08.860> the<00:15:09.220> smart<00:15:09.519> contract<00:15:09.699> developer 00:15:10.290 --> 00:15:10.300 align:start position:0% basically the smart contract developer 00:15:10.300 --> 00:15:12.660 align:start position:0% basically the smart contract developer deduct<00:15:10.720> developer<00:15:11.170> you<00:15:11.290> don't<00:15:11.319> have<00:15:11.709> to<00:15:11.949> like 00:15:12.660 --> 00:15:12.670 align:start position:0% deduct developer you don't have to like 00:15:12.670 --> 00:15:17.490 align:start position:0% deduct developer you don't have to like think<00:15:13.420> about<00:15:14.009> you<00:15:15.009> know<00:15:15.160> assigning<00:15:16.500> identity 00:15:17.490 --> 00:15:17.500 align:start position:0% think about you know assigning identity 00:15:17.500 --> 00:15:20.670 align:start position:0% think about you know assigning identity pond'rous<00:15:17.860> to<00:15:18.250> users<00:15:18.939> and<00:15:19.269> maybe<00:15:19.930> afterwards 00:15:20.670 --> 00:15:20.680 align:start position:0% pond'rous to users and maybe afterwards 00:15:20.680 --> 00:15:23.280 align:start position:0% pond'rous to users and maybe afterwards ask<00:15:20.980> the<00:15:21.189> user<00:15:21.399> to<00:15:21.579> please<00:15:22.000> his<00:15:22.629> credit<00:15:23.019> card 00:15:23.280 --> 00:15:23.290 align:start position:0% ask the user to please his credit card 00:15:23.290 --> 00:15:25.949 align:start position:0% ask the user to please his credit card or<00:15:23.980> you<00:15:24.459> know<00:15:24.610> doing<00:15:25.180> a<00:15:25.300> simple<00:15:25.600> transaction 00:15:25.949 --> 00:15:25.959 align:start position:0% or you know doing a simple transaction 00:15:25.959 --> 00:15:29.809 align:start position:0% or you know doing a simple transaction by<00:15:26.920> pressing<00:15:27.339> the<00:15:27.399> botany<00:15:27.790> in<00:15:28.240> your<00:15:28.660> website 00:15:29.809 --> 00:15:29.819 align:start position:0% by pressing the botany in your website 00:15:29.819 --> 00:15:33.150 align:start position:0% by pressing the botany in your website that's<00:15:30.819> why<00:15:31.059> I<00:15:31.089> told<00:15:31.269> you<00:15:31.540> hear<00:15:31.899> that<00:15:32.170> jobs 00:15:33.150 --> 00:15:33.160 align:start position:0% that's why I told you hear that jobs 00:15:33.160 --> 00:15:35.220 align:start position:0% that's why I told you hear that jobs paid<00:15:33.490> for<00:15:33.759> their<00:15:33.939> own<00:15:34.059> transactions<00:15:34.839> which<00:15:35.079> is 00:15:35.220 --> 00:15:35.230 align:start position:0% paid for their own transactions which is 00:15:35.230 --> 00:15:36.990 align:start position:0% paid for their own transactions which is great<00:15:35.470> at<00:15:36.069> least<00:15:36.339> for<00:15:36.490> the<00:15:36.579> onboarding 00:15:36.990 --> 00:15:37.000 align:start position:0% great at least for the onboarding 00:15:37.000 --> 00:15:40.439 align:start position:0% great at least for the onboarding program<00:15:37.949> and<00:15:38.949> how<00:15:39.550> can<00:15:39.759> we<00:15:39.939> use<00:15:40.089> this<00:15:40.240> stuff 00:15:40.439 --> 00:15:40.449 align:start position:0% program and how can we use this stuff 00:15:40.449 --> 00:15:42.090 align:start position:0% program and how can we use this stuff because<00:15:40.899> I'm<00:15:41.110> talking<00:15:41.379> a<00:15:41.529> lot<00:15:41.589> of<00:15:41.709> technical 00:15:42.090 --> 00:15:42.100 align:start position:0% because I'm talking a lot of technical 00:15:42.100 --> 00:15:45.030 align:start position:0% because I'm talking a lot of technical stuff<00:15:42.370> and<00:15:42.610> maybe<00:15:43.089> you<00:15:44.019> just<00:15:44.050> want<00:15:44.559> to<00:15:44.589> use<00:15:44.860> it 00:15:45.030 --> 00:15:45.040 align:start position:0% stuff and maybe you just want to use it 00:15:45.040 --> 00:15:49.410 align:start position:0% stuff and maybe you just want to use it well<00:15:46.029> we<00:15:46.389> developed<00:15:47.069> as<00:15:48.069> a<00:15:48.129> team<00:15:48.429> the<00:15:48.970> GSM 00:15:49.410 --> 00:15:49.420 align:start position:0% well we developed as a team the GSM 00:15:49.420 --> 00:15:52.850 align:start position:0% well we developed as a team the GSM provider<00:15:49.980> you<00:15:50.980> can<00:15:51.009> install<00:15:51.459> it<00:15:51.610> using 00:15:52.850 --> 00:15:52.860 align:start position:0% provider you can install it using 00:15:52.860 --> 00:15:55.369 align:start position:0% provider you can install it using the<00:15:53.310> gsm<00:15:53.730> provider<00:15:54.029> is<00:15:54.180> basically<00:15:54.600> yet 00:15:55.369 --> 00:15:55.379 align:start position:0% the gsm provider is basically yet 00:15:55.379 --> 00:15:57.499 align:start position:0% the gsm provider is basically yet another<00:15:55.620> web<00:15:56.069> through<00:15:56.310> provider<00:15:56.670> that<00:15:57.449> you 00:15:57.499 --> 00:15:57.509 align:start position:0% another web through provider that you 00:15:57.509 --> 00:16:00.199 align:start position:0% another web through provider that you will<00:15:57.810> be<00:15:57.990> able<00:15:58.110> to<00:15:58.319> use<00:15:58.620> to<00:15:59.310> transform<00:15:59.819> your 00:16:00.199 --> 00:16:00.209 align:start position:0% will be able to use to transform your 00:16:00.209 --> 00:16:03.259 align:start position:0% will be able to use to transform your regular<00:16:01.079> transactions<00:16:01.680> into<00:16:02.310> management 00:16:03.259 --> 00:16:03.269 align:start position:0% regular transactions into management 00:16:03.269 --> 00:16:06.980 align:start position:0% regular transactions into management sections<00:16:03.839> into<00:16:04.199> relay<00:16:04.769> have<00:16:05.100> read<00:16:05.790> a<00:16:05.990> GSM 00:16:06.980 --> 00:16:06.990 align:start position:0% sections into relay have read a GSM 00:16:06.990 --> 00:16:09.350 align:start position:0% sections into relay have read a GSM transaction<00:16:07.620> so<00:16:07.920> just<00:16:08.519> by<00:16:08.670> changing<00:16:08.699> your 00:16:09.350 --> 00:16:09.360 align:start position:0% transaction so just by changing your 00:16:09.360 --> 00:16:13.040 align:start position:0% transaction so just by changing your typical<00:16:10.069> HTTP<00:16:11.069> provider<00:16:11.579> to<00:16:12.269> the<00:16:12.509> gsm 00:16:13.040 --> 00:16:13.050 align:start position:0% typical HTTP provider to the gsm 00:16:13.050 --> 00:16:15.530 align:start position:0% typical HTTP provider to the gsm provider<00:16:13.410> you<00:16:14.100> will<00:16:14.279> be<00:16:14.399> able<00:16:14.490> to<00:16:14.730> do<00:16:14.879> a<00:16:15.120> call 00:16:15.530 --> 00:16:15.540 align:start position:0% provider you will be able to do a call 00:16:15.540 --> 00:16:18.530 align:start position:0% provider you will be able to do a call as<00:16:16.019> in<00:16:16.290> the<00:16:16.439> third<00:16:17.009> line<00:16:17.310> my<00:16:17.910> contracted 00:16:18.530 --> 00:16:18.540 align:start position:0% as in the third line my contracted 00:16:18.540 --> 00:16:20.689 align:start position:0% as in the third line my contracted methods<00:16:18.930> that<00:16:19.379> do<00:16:19.709> something<00:16:20.160> the<00:16:20.310> condor<00:16:20.550> we 00:16:20.689 --> 00:16:20.699 align:start position:0% methods that do something the condor we 00:16:20.699 --> 00:16:23.600 align:start position:0% methods that do something the condor we were<00:16:20.970> seeing<00:16:21.720> before<00:16:21.860> dots<00:16:22.860> em<00:16:23.100> and<00:16:23.370> that's 00:16:23.600 --> 00:16:23.610 align:start position:0% were seeing before dots em and that's 00:16:23.610 --> 00:16:26.059 align:start position:0% were seeing before dots em and that's all<00:16:23.730> instead<00:16:24.300> of<00:16:24.389> you<00:16:24.589> instead<00:16:25.589> of<00:16:25.680> doing<00:16:25.920> a 00:16:26.059 --> 00:16:26.069 align:start position:0% all instead of you instead of doing a 00:16:26.069 --> 00:16:27.410 align:start position:0% all instead of you instead of doing a regular<00:16:26.100> transaction<00:16:27.000> it<00:16:27.089> will<00:16:27.269> do<00:16:27.389> a 00:16:27.410 --> 00:16:27.420 align:start position:0% regular transaction it will do a 00:16:27.420 --> 00:16:29.869 align:start position:0% regular transaction it will do a management<00:16:27.990> session<00:16:28.350> which<00:16:29.339> is<00:16:29.490> great<00:16:29.699> right 00:16:29.869 --> 00:16:29.879 align:start position:0% management session which is great right 00:16:29.879 --> 00:16:31.939 align:start position:0% management session which is great right so<00:16:30.360> you<00:16:30.569> only<00:16:30.720> have<00:16:30.959> two<00:16:31.110> connections<00:16:31.259> we 00:16:31.939 --> 00:16:31.949 align:start position:0% so you only have two connections we 00:16:31.949 --> 00:16:36.019 align:start position:0% so you only have two connections we change<00:16:32.189> one<00:16:32.430> online<00:16:33.500> also<00:16:34.500> you<00:16:35.310> have<00:16:35.699> to<00:16:35.730> make 00:16:36.019 --> 00:16:36.029 align:start position:0% change one online also you have to make 00:16:36.029 --> 00:16:40.189 align:start position:0% change one online also you have to make your<00:16:36.600> contract<00:16:37.490> gsm<00:16:38.490> cable<00:16:38.910> and<00:16:39.240> for<00:16:39.480> that<00:16:39.600> G 00:16:40.189 --> 00:16:40.199 align:start position:0% your contract gsm cable and for that G 00:16:40.199 --> 00:16:42.259 align:start position:0% your contract gsm cable and for that G open<00:16:40.319> Zeppelin<00:16:40.860> contracts<00:16:41.399> or<00:16:41.579> open<00:16:41.910> settings 00:16:42.259 --> 00:16:42.269 align:start position:0% open Zeppelin contracts or open settings 00:16:42.269 --> 00:16:45.230 align:start position:0% open Zeppelin contracts or open settings solidity<00:16:42.689> team<00:16:43.490> created<00:16:44.490> a<00:16:44.790> couple<00:16:45.180> of 00:16:45.230 --> 00:16:45.240 align:start position:0% solidity team created a couple of 00:16:45.240 --> 00:16:48.499 align:start position:0% solidity team created a couple of contracts<00:16:46.100> for<00:16:47.100> example<00:16:47.160> the<00:16:47.550> GSM<00:16:48.000> recipient 00:16:48.499 --> 00:16:48.509 align:start position:0% contracts for example the GSM recipient 00:16:48.509 --> 00:16:50.179 align:start position:0% contracts for example the GSM recipient that<00:16:48.600> you<00:16:48.959> will<00:16:49.170> find<00:16:49.439> you<00:16:49.529> the<00:16:49.620> best<00:16:49.649> miss 00:16:50.179 --> 00:16:50.189 align:start position:0% that you will find you the best miss 00:16:50.189 --> 00:16:51.439 align:start position:0% that you will find you the best miss Pauline<00:16:50.519> obviously<00:16:50.879> open<00:16:51.240> something 00:16:51.439 --> 00:16:51.449 align:start position:0% Pauline obviously open something 00:16:51.449 --> 00:16:57.319 align:start position:0% Pauline obviously open something contracts<00:16:52.399> which<00:16:53.399> just<00:16:54.120> inheriting<00:16:56.029> yes<00:16:57.029> if 00:16:57.319 --> 00:16:57.329 align:start position:0% contracts which just inheriting yes if 00:16:57.329 --> 00:16:58.879 align:start position:0% contracts which just inheriting yes if you<00:16:57.509> have<00:16:57.689> your<00:16:57.839> country<00:16:58.139> are<00:16:58.290> you<00:16:58.410> enter<00:16:58.740> it 00:16:58.879 --> 00:16:58.889 align:start position:0% you have your country are you enter it 00:16:58.889 --> 00:17:00.800 align:start position:0% you have your country are you enter it and<00:16:59.279> it<00:16:59.370> from<00:16:59.579> it<00:16:59.699> you<00:17:00.240> will<00:17:00.269> be<00:17:00.569> able<00:17:00.660> to 00:17:00.800 --> 00:17:00.810 align:start position:0% and it from it you will be able to 00:17:00.810 --> 00:17:02.960 align:start position:0% and it from it you will be able to access<00:17:01.019> to<00:17:01.199> the<00:17:01.529> accept<00:17:01.980> relay<00:17:02.220> call<00:17:02.519> this 00:17:02.960 --> 00:17:02.970 align:start position:0% access to the accept relay call this 00:17:02.970 --> 00:17:05.409 align:start position:0% access to the accept relay call this function<00:17:03.420> I<00:17:03.540> told<00:17:04.020> you<00:17:04.169> that<00:17:04.380> I<00:17:04.679> checks 00:17:05.409 --> 00:17:05.419 align:start position:0% function I told you that I checks 00:17:05.419 --> 00:17:08.299 align:start position:0% function I told you that I checks whether<00:17:06.419> or<00:17:06.659> not<00:17:06.809> the<00:17:07.199> recipient<00:17:07.500> contract 00:17:08.299 --> 00:17:08.309 align:start position:0% whether or not the recipient contract 00:17:08.309 --> 00:17:11.210 align:start position:0% whether or not the recipient contract wants<00:17:09.030> to<00:17:09.319> receive<00:17:10.319> their<00:17:10.530> the<00:17:10.890> transaction 00:17:11.210 --> 00:17:11.220 align:start position:0% wants to receive their the transaction 00:17:11.220 --> 00:17:13.490 align:start position:0% wants to receive their the transaction or<00:17:11.459> not<00:17:11.640> well<00:17:12.030> you<00:17:12.299> can<00:17:12.539> code<00:17:12.900> that<00:17:13.110> in<00:17:13.350> that 00:17:13.490 --> 00:17:13.500 align:start position:0% or not well you can code that in that 00:17:13.500 --> 00:17:16.059 align:start position:0% or not well you can code that in that separate<00:17:13.949> home 00:17:16.059 --> 00:17:16.069 align:start position:0% separate home 00:17:16.069 --> 00:17:20.329 align:start position:0% separate home and<00:17:17.150> what<00:17:18.150> else<00:17:18.329> do<00:17:18.990> you<00:17:19.110> open<00:17:19.260> Zeppelin<00:17:19.890> GSN 00:17:20.329 --> 00:17:20.339 align:start position:0% and what else do you open Zeppelin GSN 00:17:20.339 --> 00:17:24.289 align:start position:0% and what else do you open Zeppelin GSN helper<00:17:20.789> so<00:17:21.030> maybe<00:17:21.720> could<00:17:22.559> be<00:17:22.740> for<00:17:22.980> you<00:17:23.100> to<00:17:23.610> you 00:17:24.289 --> 00:17:24.299 align:start position:0% helper so maybe could be for you to you 00:17:24.299 --> 00:17:26.390 align:start position:0% helper so maybe could be for you to you know<00:17:24.419> set<00:17:24.750> up<00:17:24.839> everything<00:17:25.230> to<00:17:25.949> develop<00:17:26.309> your 00:17:26.390 --> 00:17:26.400 align:start position:0% know set up everything to develop your 00:17:26.400 --> 00:17:31.190 align:start position:0% know set up everything to develop your own<00:17:27.140> gsm<00:17:28.140> cable<00:17:28.500> capable<00:17:29.190> of<00:17:29.340> ups<00:17:29.700> and<00:17:30.200> we 00:17:31.190 --> 00:17:31.200 align:start position:0% own gsm cable capable of ups and we 00:17:31.200 --> 00:17:34.610 align:start position:0% own gsm cable capable of ups and we basically<00:17:31.530> developed<00:17:32.460> this<00:17:32.520> GSN<00:17:33.120> helpers<00:17:33.630> for 00:17:34.610 --> 00:17:34.620 align:start position:0% basically developed this GSN helpers for 00:17:34.620 --> 00:17:36.830 align:start position:0% basically developed this GSN helpers for you<00:17:34.770> to<00:17:35.130> make<00:17:35.280> it<00:17:35.490> like<00:17:35.700> in<00:17:36.120> only<00:17:36.450> one<00:17:36.690> two 00:17:36.830 --> 00:17:36.840 align:start position:0% you to make it like in only one two 00:17:36.840 --> 00:17:39.830 align:start position:0% you to make it like in only one two minutes<00:17:37.200> just<00:17:37.500> by<00:17:37.740> after<00:17:38.700> installing<00:17:39.270> the<00:17:39.450> GSM 00:17:39.830 --> 00:17:39.840 align:start position:0% minutes just by after installing the GSM 00:17:39.840 --> 00:17:43.039 align:start position:0% minutes just by after installing the GSM helpers<00:17:40.200> running<00:17:40.620> if<00:17:40.980> you<00:17:41.159> run<00:17:41.309> us<00:17:42.049> GSN 00:17:43.039 --> 00:17:43.049 align:start position:0% helpers running if you run us GSN 00:17:43.049 --> 00:17:45.830 align:start position:0% helpers running if you run us GSN regulator<00:17:43.679> this<00:17:44.429> will<00:17:44.640> basically<00:17:44.789> create<00:17:45.659> a 00:17:45.830 --> 00:17:45.840 align:start position:0% regulator this will basically create a 00:17:45.840 --> 00:17:47.650 align:start position:0% regulator this will basically create a relay<00:17:46.320> have<00:17:46.590> in<00:17:46.860> your<00:17:47.039> look 00:17:47.650 --> 00:17:47.660 align:start position:0% relay have in your look 00:17:47.660 --> 00:17:50.980 align:start position:0% relay have in your look if<00:17:48.110> it's<00:17:48.590> not<00:17:48.830> created<00:17:49.280> it<00:17:49.820> will<00:17:50.060> download<00:17:50.690> the 00:17:50.980 --> 00:17:50.990 align:start position:0% if it's not created it will download the 00:17:50.990 --> 00:17:52.240 align:start position:0% if it's not created it will download the binary<00:17:51.170> of<00:17:51.590> the<00:17:51.770> relator 00:17:52.240 --> 00:17:52.250 align:start position:0% binary of the relator 00:17:52.250 --> 00:17:55.390 align:start position:0% binary of the relator it<00:17:52.910> will<00:17:53.150> then<00:17:54.080> start<00:17:54.470> the<00:17:54.560> relator<00:17:54.950> it<00:17:55.220> will 00:17:55.390 --> 00:17:55.400 align:start position:0% it will then start the relator it will 00:17:55.400 --> 00:17:58.750 align:start position:0% it will then start the relator it will associate<00:17:56.060> that<00:17:56.300> we<00:17:56.450> later<00:17:56.630> to<00:17:57.760> terminate 00:17:58.750 --> 00:17:58.760 align:start position:0% associate that we later to terminate 00:17:58.760 --> 00:18:03.040 align:start position:0% associate that we later to terminate have<00:17:59.030> and<00:17:59.330> will<00:18:00.080> fund<00:18:00.440> it<00:18:00.590> so<00:18:00.620> it's<00:18:01.480> capable<00:18:02.480> of 00:18:03.040 --> 00:18:03.050 align:start position:0% have and will fund it so it's capable of 00:18:03.050 --> 00:18:04.930 align:start position:0% have and will fund it so it's capable of receiving<00:18:03.380> from<00:18:03.650> assumptions<00:18:04.100> really<00:18:04.340> really 00:18:04.930 --> 00:18:04.940 align:start position:0% receiving from assumptions really really 00:18:04.940 --> 00:18:08.350 align:start position:0% receiving from assumptions really really close<00:18:06.040> and<00:18:07.040> if<00:18:07.340> you<00:18:07.460> don't<00:18:07.670> like<00:18:07.880> she<00:18:08.090> likes 00:18:08.350 --> 00:18:08.360 align:start position:0% close and if you don't like she likes 00:18:08.360 --> 00:18:10.630 align:start position:0% close and if you don't like she likes you<00:18:08.630> also<00:18:08.720> can<00:18:09.110> use<00:18:09.140> a<00:18:09.320> chromatic<00:18:09.650> way<00:18:10.100> which 00:18:10.630 --> 00:18:10.640 align:start position:0% you also can use a chromatic way which 00:18:10.640 --> 00:18:13.090 align:start position:0% you also can use a chromatic way which will<00:18:10.940> be<00:18:11.090> basically<00:18:11.470> important<00:18:12.470> ever<00:18:12.680> issues 00:18:13.090 --> 00:18:13.100 align:start position:0% will be basically important ever issues 00:18:13.100 --> 00:18:15.100 align:start position:0% will be basically important ever issues to<00:18:13.310> really<00:18:13.460> function<00:18:13.910> and<00:18:14.360> upon<00:18:14.660> recipient 00:18:15.100 --> 00:18:15.110 align:start position:0% to really function and upon recipient 00:18:15.110 --> 00:18:17.350 align:start position:0% to really function and upon recipient function<00:18:15.710> from<00:18:16.250> the<00:18:16.430> same<00:18:16.640> library<00:18:16.850> and<00:18:17.330> just 00:18:17.350 --> 00:18:17.360 align:start position:0% function from the same library and just 00:18:17.360 --> 00:18:19.300 align:start position:0% function from the same library and just with<00:18:18.170> a<00:18:18.200> one-liner 00:18:19.300 --> 00:18:19.310 align:start position:0% with a one-liner 00:18:19.310 --> 00:18:21.790 align:start position:0% with a one-liner you<00:18:19.640> will<00:18:19.850> be<00:18:20.000> able<00:18:20.150> to<00:18:20.540> order<00:18:21.080> a<00:18:21.200> layer<00:18:21.470> of 00:18:21.790 --> 00:18:21.800 align:start position:0% you will be able to order a layer of 00:18:21.800 --> 00:18:23.710 align:start position:0% you will be able to order a layer of other<00:18:22.040> recipients<00:18:22.580> or<00:18:22.940> whatever<00:18:23.300> you<00:18:23.450> want 00:18:23.710 --> 00:18:23.720 align:start position:0% other recipients or whatever you want 00:18:23.720 --> 00:18:27.810 align:start position:0% other recipients or whatever you want and<00:18:25.510> we<00:18:26.510> have<00:18:26.720> been<00:18:26.870> talking<00:18:27.080> only<00:18:27.320> about 00:18:27.810 --> 00:18:27.820 align:start position:0% and we have been talking only about 00:18:27.820 --> 00:18:31.840 align:start position:0% and we have been talking only about Eli's<00:18:28.820> code<00:18:29.630> we<00:18:30.410> also<00:18:30.590> develop<00:18:31.130> some<00:18:31.160> web 00:18:31.840 --> 00:18:31.850 align:start position:0% Eli's code we also develop some web 00:18:31.850 --> 00:18:36.370 align:start position:0% Eli's code we also develop some web tools<00:18:32.210> you<00:18:32.960> can<00:18:33.230> go<00:18:33.650> to<00:18:33.710> sibling<00:18:34.670> /<00:18:35.140> GSN<00:18:36.140> tool 00:18:36.370 --> 00:18:36.380 align:start position:0% tools you can go to sibling / GSN tool 00:18:36.380 --> 00:18:39.310 align:start position:0% tools you can go to sibling / GSN tool which<00:18:36.980> will<00:18:37.220> let<00:18:37.460> you<00:18:37.760> see<00:18:38.060> I<00:18:38.330> mean<00:18:38.900> if<00:18:39.140> you 00:18:39.310 --> 00:18:39.320 align:start position:0% which will let you see I mean if you 00:18:39.320 --> 00:18:41.530 align:start position:0% which will let you see I mean if you develop<00:18:39.710> your<00:18:39.950> own<00:18:39.980> contracts<00:18:40.670> and<00:18:41.330> you 00:18:41.530 --> 00:18:41.540 align:start position:0% develop your own contracts and you 00:18:41.540 --> 00:18:43.720 align:start position:0% develop your own contracts and you upload<00:18:41.810> them<00:18:42.200> and<00:18:42.530> you<00:18:42.710> link<00:18:43.010> them<00:18:43.220> to<00:18:43.430> the<00:18:43.460> gas 00:18:43.720 --> 00:18:43.730 align:start position:0% upload them and you link them to the gas 00:18:43.730 --> 00:18:46.360 align:start position:0% upload them and you link them to the gas station<00:18:44.210> network<00:18:44.570> there<00:18:44.960> are<00:18:44.990> GSN<00:18:45.950> capable 00:18:46.360 --> 00:18:46.370 align:start position:0% station network there are GSN capable 00:18:46.370 --> 00:18:48.430 align:start position:0% station network there are GSN capable you<00:18:46.520> will<00:18:46.700> be<00:18:46.850> able<00:18:47.030> to<00:18:47.330> see<00:18:48.050> all<00:18:48.350> the 00:18:48.430 --> 00:18:48.440 align:start position:0% you will be able to see all the 00:18:48.440 --> 00:18:51.550 align:start position:0% you will be able to see all the information<00:18:48.680> at<00:18:49.160> the<00:18:49.190> top<00:18:49.460> -<00:18:50.110> with<00:18:51.110> the<00:18:51.200> doctor 00:18:51.550 --> 00:18:51.560 align:start position:0% information at the top - with the doctor 00:18:51.560 --> 00:18:54.010 align:start position:0% information at the top - with the doctor and<00:18:51.860> also<00:18:52.120> see<00:18:53.120> information<00:18:53.330> about<00:18:53.750> their 00:18:54.010 --> 00:18:54.020 align:start position:0% and also see information about their 00:18:54.020 --> 00:18:58.840 align:start position:0% and also see information about their relatives<00:18:56.110> okay<00:18:57.110> I<00:18:57.320> know<00:18:57.470> I<00:18:57.620> got<00:18:58.010> like<00:18:58.250> talked 00:18:58.840 --> 00:18:58.850 align:start position:0% relatives okay I know I got like talked 00:18:58.850 --> 00:19:02.020 align:start position:0% relatives okay I know I got like talked a<00:18:59.030> lot<00:18:59.150> about<00:18:59.390> a<00:18:59.840> lot<00:18:59.900> of<00:19:00.200> life<00:19:00.500> you<00:19:01.280> know<00:19:01.310> to 00:19:02.020 --> 00:19:02.030 align:start position:0% a lot about a lot of life you know to 00:19:02.030 --> 00:19:06.430 align:start position:0% a lot about a lot of life you know to sue<00:19:02.360> sue<00:19:02.660> sue<00:19:02.690> so<00:19:03.700> spoiler<00:19:04.700> alert<00:19:05.000> ended<00:19:05.480> you 00:19:06.430 --> 00:19:06.440 align:start position:0% sue sue sue so spoiler alert ended you 00:19:06.440 --> 00:19:09.970 align:start position:0% sue sue sue so spoiler alert ended you can<00:19:06.470> use<00:19:06.920> the<00:19:07.780> starter<00:19:08.780> kit<00:19:08.990> the<00:19:09.140> GSN<00:19:09.620> starter 00:19:09.970 --> 00:19:09.980 align:start position:0% can use the starter kit the GSN starter 00:19:09.980 --> 00:19:12.460 align:start position:0% can use the starter kit the GSN starter kit<00:19:10.160> just<00:19:10.400> by<00:19:10.610> running<00:19:10.850> with<00:19:11.240> the<00:19:11.330> CLI<00:19:11.720> open 00:19:12.460 --> 00:19:12.470 align:start position:0% kit just by running with the CLI open 00:19:12.470 --> 00:19:15.430 align:start position:0% kit just by running with the CLI open something<00:19:12.860> aambat<00:19:13.280> GSM<00:19:13.820> and<00:19:14.570> you<00:19:14.840> will<00:19:15.110> Gerry 00:19:15.430 --> 00:19:15.440 align:start position:0% something aambat GSM and you will Gerry 00:19:15.440 --> 00:19:17.290 align:start position:0% something aambat GSM and you will Gerry have<00:19:15.650> the<00:19:15.800> open<00:19:16.040> something<00:19:16.220> contracts<00:19:16.730> on<00:19:16.880> CLI 00:19:17.290 --> 00:19:17.300 align:start position:0% have the open something contracts on CLI 00:19:17.300 --> 00:19:19.690 align:start position:0% have the open something contracts on CLI as<00:19:17.480> you<00:19:17.720> having<00:19:18.110> to<00:19:18.410> previous<00:19:18.830> starter<00:19:19.490> kits 00:19:19.690 --> 00:19:19.700 align:start position:0% as you having to previous starter kits 00:19:19.700 --> 00:19:22.000 align:start position:0% as you having to previous starter kits inferior<00:19:20.600> gonna<00:19:20.930> react<00:19:21.350> Greenville<00:19:21.770> again 00:19:22.000 --> 00:19:22.010 align:start position:0% inferior gonna react Greenville again 00:19:22.010 --> 00:19:24.340 align:start position:0% inferior gonna react Greenville again and<00:19:22.400> you<00:19:22.790> will<00:19:22.970> also<00:19:23.180> have<00:19:23.540> it<00:19:23.750> within<00:19:24.020> this 00:19:24.340 --> 00:19:24.350 align:start position:0% and you will also have it within this 00:19:24.350 --> 00:19:27.370 align:start position:0% and you will also have it within this target<00:19:24.830> the<00:19:25.730> open<00:19:26.240> something<00:19:26.450> GSN<00:19:27.050> provider 00:19:27.370 --> 00:19:27.380 align:start position:0% target the open something GSN provider 00:19:27.380 --> 00:19:29.440 align:start position:0% target the open something GSN provider and<00:19:27.680> the<00:19:27.860> GSM<00:19:28.250> helper<00:19:28.610> so<00:19:28.790> basically<00:19:29.090> by 00:19:29.440 --> 00:19:29.450 align:start position:0% and the GSM helper so basically by 00:19:29.450 --> 00:19:33.160 align:start position:0% and the GSM helper so basically by running<00:19:29.810> of<00:19:30.280> mdx<00:19:31.540> if<00:19:32.540> this<00:19:32.750> point 00:19:33.160 --> 00:19:33.170 align:start position:0% running of mdx if this point 00:19:33.170 --> 00:19:35.290 align:start position:0% running of mdx if this point opens<00:19:33.770> up<00:19:33.860> like<00:19:34.010> advantages<00:19:34.670> and<00:19:34.850> you<00:19:34.970> will<00:19:35.180> be 00:19:35.290 --> 00:19:35.300 align:start position:0% opens up like advantages and you will be 00:19:35.300 --> 00:19:37.950 align:start position:0% opens up like advantages and you will be able<00:19:35.390> to<00:19:35.720> just<00:19:36.200> start<00:19:36.740> your<00:19:37.070> gsm 00:19:37.950 --> 00:19:37.960 align:start position:0% able to just start your gsm 00:19:37.960 --> 00:19:44.100 align:start position:0% able to just start your gsm capable<00:19:38.759> job<00:19:40.350> and<00:19:41.639> well<00:19:42.639> that's<00:19:43.539> all<00:19:43.749> this<00:19:43.929> is 00:19:44.100 --> 00:19:44.110 align:start position:0% capable job and well that's all this is 00:19:44.110 --> 00:19:47.460 align:start position:0% capable job and well that's all this is all<00:19:44.679> this<00:19:45.669> are<00:19:45.909> all<00:19:46.240> the<00:19:46.450> researchers<00:19:47.080> we<00:19:47.289> have 00:19:47.460 --> 00:19:47.470 align:start position:0% all this are all the researchers we have 00:19:47.470 --> 00:19:49.320 align:start position:0% all this are all the researchers we have been<00:19:47.649> working<00:19:48.190> on<00:19:48.340> for<00:19:48.369> the<00:19:48.639> last<00:19:48.730> year<00:19:49.179> the 00:19:49.320 --> 00:19:49.330 align:start position:0% been working on for the last year the 00:19:49.330 --> 00:19:52.739 align:start position:0% been working on for the last year the contracts<00:19:50.230> the<00:19:50.440> CLI<00:19:50.830> the<00:19:50.889> GSM<00:19:51.669> provider<00:19:51.999> the 00:19:52.739 --> 00:19:52.749 align:start position:0% contracts the CLI the GSM provider the 00:19:52.749 --> 00:19:55.859 align:start position:0% contracts the CLI the GSM provider the GSM<00:19:53.200> helpers<00:19:53.710> the<00:19:54.519> open<00:19:55.149> something<00:19:55.360> network 00:19:55.859 --> 00:19:55.869 align:start position:0% GSM helpers the open something network 00:19:55.869 --> 00:19:57.690 align:start position:0% GSM helpers the open something network and<00:19:56.080> opens<00:19:56.409> up<00:19:56.529> into<00:19:56.710> scalper<00:19:57.190> for<00:19:57.429> you<00:19:57.519> to 00:19:57.690 --> 00:19:57.700 align:start position:0% and opens up into scalper for you to 00:19:57.700 --> 00:20:00.210 align:start position:0% and opens up into scalper for you to test<00:19:57.909> your<00:19:58.149> contracts<00:19:58.960> you<00:19:59.470> can<00:19:59.529> at<00:19:59.830> least<00:19:59.980> go 00:20:00.210 --> 00:20:00.220 align:start position:0% test your contracts you can at least go 00:20:00.220 --> 00:20:04.049 align:start position:0% test your contracts you can at least go to<00:20:01.139> 17/8<00:20:02.139> part<00:20:02.379> to<00:20:02.470> see<00:20:02.649> all<00:20:03.220> of<00:20:03.279> this<00:20:03.580> and<00:20:03.879> also 00:20:04.049 --> 00:20:04.059 align:start position:0% to 17/8 part to see all of this and also 00:20:04.059 --> 00:20:06.029 align:start position:0% to 17/8 part to see all of this and also to<00:20:04.240> simply<00:20:04.659> in<00:20:04.720> /<00:20:05.019> dose<00:20:05.289> to<00:20:05.799> see<00:20:05.919> the 00:20:06.029 --> 00:20:06.039 align:start position:0% to simply in / dose to see the 00:20:06.039 --> 00:20:13.000 align:start position:0% to simply in / dose to see the documentation<00:20:06.850> and<00:20:07.360> thank<00:20:08.350> you 00:20:13.000 --> 00:20:13.010 align:start position:0% 00:20:13.010 --> 00:20:19.450 align:start position:0% [Applause]