WEBVTT Kind: captions Language: en 00:00:17.710 --> 00:00:20.770 align:start position:0% all<00:00:18.710> right<00:00:18.860> so<00:00:19.220> my<00:00:19.940> name<00:00:19.970> is<00:00:20.180> Yuri<00:00:20.450> I'm<00:00:20.750> a 00:00:20.770 --> 00:00:20.780 align:start position:0% all right so my name is Yuri I'm a 00:00:20.780 --> 00:00:23.980 align:start position:0% all right so my name is Yuri I'm a developer<00:00:21.470> from<00:00:21.650> Montreal<00:00:22.490> Canada 00:00:23.980 --> 00:00:23.990 align:start position:0% developer from Montreal Canada 00:00:23.990 --> 00:00:28.150 align:start position:0% developer from Montreal Canada I'm<00:00:24.380> daughter<00:00:24.680> of<00:00:25.090> embark<00:00:26.090> as<00:00:26.869> well<00:00:27.140> as<00:00:27.350> some 00:00:28.150 --> 00:00:28.160 align:start position:0% I'm daughter of embark as well as some 00:00:28.160 --> 00:00:30.340 align:start position:0% I'm daughter of embark as well as some other<00:00:28.279> projects<00:00:28.910> more<00:00:29.090> recently<00:00:29.510> transaction 00:00:30.340 --> 00:00:30.350 align:start position:0% other projects more recently transaction 00:00:30.350 --> 00:00:33.370 align:start position:0% other projects more recently transaction dealer<00:00:30.740> a<00:00:31.040> relay<00:00:31.630> you<00:00:32.630> might<00:00:32.810> know<00:00:32.930> me<00:00:33.079> in<00:00:33.140> read 00:00:33.370 --> 00:00:33.380 align:start position:0% dealer a relay you might know me in read 00:00:33.380 --> 00:00:37.180 align:start position:0% dealer a relay you might know me in read it<00:00:33.590> as<00:00:33.829> a<00:00:34.280> liam<00:00:34.610> craft<00:00:35.200> so<00:00:36.200> today<00:00:36.890> are<00:00:36.980> going<00:00:37.070> to 00:00:37.180 --> 00:00:37.190 align:start position:0% it as a liam craft so today are going to 00:00:37.190 --> 00:00:42.190 align:start position:0% it as a liam craft so today are going to talk<00:00:37.310> about<00:00:37.430> embark<00:00:38.210> you<00:00:38.900> and<00:00:40.690> so<00:00:41.690> embark<00:00:42.050> was 00:00:42.190 --> 00:00:42.200 align:start position:0% talk about embark you and so embark was 00:00:42.200 --> 00:00:45.130 align:start position:0% talk about embark you and so embark was the<00:00:42.320> first<00:00:42.760> framework<00:00:43.760> for<00:00:44.030> Freud<00:00:44.810> cerium 00:00:45.130 --> 00:00:45.140 align:start position:0% the first framework for Freud cerium 00:00:45.140 --> 00:00:45.550 align:start position:0% the first framework for Freud cerium DAPs 00:00:45.550 --> 00:00:45.560 align:start position:0% DAPs 00:00:45.560 --> 00:00:49.030 align:start position:0% DAPs and<00:00:46.690> to<00:00:47.690> give<00:00:47.840> some<00:00:48.020> background<00:00:48.050> on<00:00:48.650> some<00:00:48.680> of 00:00:49.030 --> 00:00:49.040 align:start position:0% and to give some background on some of 00:00:49.040 --> 00:00:52.270 align:start position:0% and to give some background on some of the<00:00:49.130> features<00:00:49.690> it's<00:00:50.890> so<00:00:51.890> it's<00:00:52.040> completely 00:00:52.270 --> 00:00:52.280 align:start position:0% the features it's so it's completely 00:00:52.280 --> 00:00:55.090 align:start position:0% the features it's so it's completely compatible<00:00:52.820> with<00:00:53.210> any<00:00:53.450> build<00:00:53.810> pipeline<00:00:54.380> you 00:00:55.090 --> 00:00:55.100 align:start position:0% compatible with any build pipeline you 00:00:55.100 --> 00:00:57.400 align:start position:0% compatible with any build pipeline you can<00:00:55.130> use<00:00:55.430> it<00:00:55.580> what<00:00:55.730> grant<00:00:56.060> or<00:00:56.330> meteor<00:00:56.900> or 00:00:57.400 --> 00:00:57.410 align:start position:0% can use it what grant or meteor or 00:00:57.410 --> 00:00:59.820 align:start position:0% can use it what grant or meteor or whatever<00:00:58.100> pipeline<00:00:58.520> you're<00:00:58.790> you're<00:00:59.180> used<00:00:59.390> to 00:00:59.820 --> 00:00:59.830 align:start position:0% whatever pipeline you're you're used to 00:00:59.830 --> 00:01:03.700 align:start position:0% whatever pipeline you're you're used to embark<00:01:00.830> to<00:01:01.040> welcome<00:01:01.520> with<00:01:01.730> its<00:01:01.880> own<00:01:02.710> pipeline 00:01:03.700 --> 00:01:03.710 align:start position:0% embark to welcome with its own pipeline 00:01:03.710 --> 00:01:06.700 align:start position:0% embark to welcome with its own pipeline for<00:01:04.420> convenience<00:01:05.420> purposes<00:01:05.630> for<00:01:06.200> development 00:01:06.700 --> 00:01:06.710 align:start position:0% for convenience purposes for development 00:01:06.710 --> 00:01:08.620 align:start position:0% for convenience purposes for development but<00:01:07.280> you<00:01:07.430> will<00:01:07.610> still<00:01:07.939> be<00:01:07.970> able<00:01:08.119> to<00:01:08.299> use<00:01:08.509> it 00:01:08.620 --> 00:01:08.630 align:start position:0% but you will still be able to use it 00:01:08.630 --> 00:01:11.679 align:start position:0% but you will still be able to use it with<00:01:08.780> any<00:01:08.990> any<00:01:09.439> pipeline<00:01:10.030> it's<00:01:11.030> also<00:01:11.210> supports 00:01:11.679 --> 00:01:11.689 align:start position:0% with any any pipeline it's also supports 00:01:11.689 --> 00:01:14.319 align:start position:0% with any any pipeline it's also supports you<00:01:12.049> can't<00:01:12.229> test<00:01:13.100> your<00:01:13.400> contracts<00:01:14.180> using 00:01:14.319 --> 00:01:14.329 align:start position:0% you can't test your contracts using 00:01:14.329 --> 00:01:17.340 align:start position:0% you can't test your contracts using javascript<00:01:14.979> it<00:01:15.979> also<00:01:16.189> keeps<00:01:16.490> track<00:01:16.880> of<00:01:16.909> the 00:01:17.340 --> 00:01:17.350 align:start position:0% javascript it also keeps track of the 00:01:17.350 --> 00:01:19.810 align:start position:0% javascript it also keeps track of the the<00:01:18.350> contracts<00:01:18.800> that<00:01:18.920> have<00:01:19.280> already<00:01:19.550> been 00:01:19.810 --> 00:01:19.820 align:start position:0% the contracts that have already been 00:01:19.820 --> 00:01:23.440 align:start position:0% the contracts that have already been deployed<00:01:20.030> and<00:01:20.800> it<00:01:21.800> it's<00:01:22.370> smart<00:01:22.730> about<00:01:23.000> it<00:01:23.060> so 00:01:23.440 --> 00:01:23.450 align:start position:0% deployed and it it's smart about it so 00:01:23.450 --> 00:01:26.710 align:start position:0% deployed and it it's smart about it so you<00:01:23.510> can<00:01:23.840> even<00:01:24.080> we<00:01:24.800> factor<00:01:25.220> a<00:01:25.250> contract<00:01:25.790> and<00:01:26.330> so 00:01:26.710 --> 00:01:26.720 align:start position:0% you can even we factor a contract and so 00:01:26.720 --> 00:01:29.340 align:start position:0% you can even we factor a contract and so long<00:01:26.840> we<00:01:26.960> don't<00:01:27.080> change<00:01:27.440> something<00:01:28.000> that 00:01:29.340 --> 00:01:29.350 align:start position:0% long we don't change something that 00:01:29.350 --> 00:01:32.680 align:start position:0% long we don't change something that effect<00:01:30.350> the<00:01:30.620> decks<00:01:31.159> you<00:01:31.460> know<00:01:31.640> the<00:01:32.150> external 00:01:32.680 --> 00:01:32.690 align:start position:0% effect the decks you know the external 00:01:32.690 --> 00:01:34.810 align:start position:0% effect the decks you know the external of<00:01:32.750> the<00:01:32.900> contract<00:01:33.350> you<00:01:33.830> want<00:01:34.100> you<00:01:34.490> want<00:01:34.729> to 00:01:34.810 --> 00:01:34.820 align:start position:0% of the contract you want you want to 00:01:34.820 --> 00:01:37.060 align:start position:0% of the contract you want you want to deploy<00:01:35.180> again<00:01:35.450> so<00:01:35.630> you<00:01:35.720> can<00:01:35.840> refactor<00:01:36.140> say<00:01:36.530> an 00:01:37.060 --> 00:01:37.070 align:start position:0% deploy again so you can refactor say an 00:01:37.070 --> 00:01:39.580 align:start position:0% deploy again so you can refactor say an internal<00:01:37.670> variable<00:01:38.600> we<00:01:38.870> can<00:01:39.020> change<00:01:39.260> the<00:01:39.440> name 00:01:39.580 --> 00:01:39.590 align:start position:0% internal variable we can change the name 00:01:39.590 --> 00:01:41.830 align:start position:0% internal variable we can change the name it<00:01:40.580> will<00:01:40.729> not<00:01:40.850> redeploy<00:01:41.270> because<00:01:41.600> you<00:01:41.690> haven't 00:01:41.830 --> 00:01:41.840 align:start position:0% it will not redeploy because you haven't 00:01:41.840 --> 00:01:42.969 align:start position:0% it will not redeploy because you haven't really<00:01:42.200> change<00:01:42.440> anything 00:01:42.969 --> 00:01:42.979 align:start position:0% really change anything 00:01:42.979 --> 00:01:45.700 align:start position:0% really change anything but<00:01:43.340> if<00:01:43.460> you<00:01:43.610> change<00:01:43.909> say<00:01:44.180> a<00:01:44.780> public<00:01:45.500> variable 00:01:45.700 --> 00:01:45.710 align:start position:0% but if you change say a public variable 00:01:45.710 --> 00:01:48.460 align:start position:0% but if you change say a public variable then<00:01:46.130> it<00:01:46.159> will<00:01:46.520> redeploy<00:01:46.970> because<00:01:47.479> there's<00:01:48.380> a 00:01:48.460 --> 00:01:48.470 align:start position:0% then it will redeploy because there's a 00:01:48.470 --> 00:01:51.070 align:start position:0% then it will redeploy because there's a code<00:01:48.650> change<00:01:48.950> you<00:01:49.940> can<00:01:50.120> also<00:01:50.270> manage 00:01:51.070 --> 00:01:51.080 align:start position:0% code change you can also manage 00:01:51.080 --> 00:01:52.750 align:start position:0% code change you can also manage different<00:01:51.500> change<00:01:51.710> with<00:01:51.979> it<00:01:52.100> you<00:01:52.250> can<00:01:52.430> deploy 00:01:52.750 --> 00:01:52.760 align:start position:0% different change with it you can deploy 00:01:52.760 --> 00:01:55.420 align:start position:0% different change with it you can deploy to<00:01:52.970> the<00:01:53.200> development<00:01:54.200> change<00:01:54.500> can<00:01:54.860> go<00:01:55.070> to<00:01:55.130> the 00:01:55.420 --> 00:01:55.430 align:start position:0% to the development change can go to the 00:01:55.430 --> 00:01:58.300 align:start position:0% to the development change can go to the production<00:01:56.390> chain<00:01:56.690> and<00:01:57.440> you<00:01:57.650> can<00:01:57.799> also<00:01:57.950> use 00:01:58.300 --> 00:01:58.310 align:start position:0% production chain and you can also use 00:01:58.310 --> 00:02:01.660 align:start position:0% production chain and you can also use both<00:01:58.940> solidity<00:01:59.420> and<00:01:59.540> serpent's<00:02:00.440> you<00:02:01.310> can<00:02:01.490> use 00:02:01.660 --> 00:02:01.670 align:start position:0% both solidity and serpent's you can use 00:02:01.670 --> 00:02:03.280 align:start position:0% both solidity and serpent's you can use it<00:02:01.820> either<00:02:02.030> you<00:02:02.270> can<00:02:02.420> use<00:02:02.570> either<00:02:02.720> of<00:02:02.869> them<00:02:03.110> or 00:02:03.280 --> 00:02:03.290 align:start position:0% it either you can use either of them or 00:02:03.290 --> 00:02:04.870 align:start position:0% it either you can use either of them or you<00:02:03.350> can<00:02:03.500> even<00:02:03.650> use<00:02:03.920> both<00:02:04.340> of<00:02:04.369> them<00:02:04.640> at<00:02:04.820> the 00:02:04.870 --> 00:02:04.880 align:start position:0% you can even use both of them at the 00:02:04.880 --> 00:02:09.190 align:start position:0% you can even use both of them at the same<00:02:04.940> at<00:02:05.510> same<00:02:05.690> time<00:02:05.930> so<00:02:07.989> another<00:02:08.989> thing<00:02:09.049> that 00:02:09.190 --> 00:02:09.200 align:start position:0% same at same time so another thing that 00:02:09.200 --> 00:02:11.559 align:start position:0% same at same time so another thing that embark<00:02:09.679> is<00:02:09.769> pretty<00:02:10.039> good<00:02:10.250> ads<00:02:10.429> is<00:02:10.670> is<00:02:11.239> dealing 00:02:11.559 --> 00:02:11.569 align:start position:0% embark is pretty good ads is is dealing 00:02:11.569 --> 00:02:14.229 align:start position:0% embark is pretty good ads is is dealing with<00:02:12.010> multiple<00:02:13.010> concert<00:02:13.610> the<00:02:13.700> contracts<00:02:14.150> that 00:02:14.229 --> 00:02:14.239 align:start position:0% with multiple concert the contracts that 00:02:14.239 --> 00:02:17.710 align:start position:0% with multiple concert the contracts that are<00:02:14.480> dependent<00:02:15.230> on<00:02:15.290> each<00:02:15.349> other<00:02:15.620> so<00:02:16.569> to<00:02:17.569> give 00:02:17.710 --> 00:02:17.720 align:start position:0% are dependent on each other so to give 00:02:17.720 --> 00:02:21.520 align:start position:0% are dependent on each other so to give some<00:02:17.900> example<00:02:18.409> of<00:02:18.500> this<00:02:19.989> so<00:02:20.989> let's<00:02:21.170> say<00:02:21.319> that 00:02:21.520 --> 00:02:21.530 align:start position:0% some example of this so let's say that 00:02:21.530 --> 00:02:24.040 align:start position:0% some example of this so let's say that you<00:02:21.799> have<00:02:22.310> three<00:02:22.760> contracts<00:02:23.240> and<00:02:23.450> they<00:02:23.540> each 00:02:24.040 --> 00:02:24.050 align:start position:0% you have three contracts and they each 00:02:24.050 --> 00:02:26.500 align:start position:0% you have three contracts and they each dependent<00:02:24.620> on<00:02:24.680> each<00:02:24.770> other<00:02:24.950> so<00:02:25.760> in<00:02:26.209> this<00:02:26.300> case 00:02:26.500 --> 00:02:26.510 align:start position:0% dependent on each other so in this case 00:02:26.510 --> 00:02:28.180 align:start position:0% dependent on each other so in this case you<00:02:26.660> need<00:02:26.780> a<00:02:26.840> token<00:02:27.110> to<00:02:27.470> be<00:02:27.560> deployed<00:02:27.890> first 00:02:28.180 --> 00:02:28.190 align:start position:0% you need a token to be deployed first 00:02:28.190 --> 00:02:28.600 align:start position:0% you need a token to be deployed first and<00:02:28.430> then 00:02:28.600 --> 00:02:28.610 align:start position:0% and then 00:02:28.610 --> 00:02:31.450 align:start position:0% and then the<00:02:28.940> Dow<00:02:29.150> and<00:02:29.560> once<00:02:30.560> that's<00:02:30.800> deploy<00:02:31.190> you<00:02:31.250> need 00:02:31.450 --> 00:02:31.460 align:start position:0% the Dow and once that's deploy you need 00:02:31.460 --> 00:02:35.050 align:start position:0% the Dow and once that's deploy you need to<00:02:31.550> deploy<00:02:31.820> the<00:02:31.970> liquid<00:02:32.270> democracy<00:02:33.040> so<00:02:34.040> in<00:02:34.580> in 00:02:35.050 --> 00:02:35.060 align:start position:0% to deploy the liquid democracy so in in 00:02:35.060 --> 00:02:37.000 align:start position:0% to deploy the liquid democracy so in in that<00:02:35.240> case<00:02:35.450> you<00:02:35.600> can<00:02:35.780> see<00:02:35.900> you<00:02:36.230> can<00:02:36.380> specify<00:02:36.680> in 00:02:37.000 --> 00:02:37.010 align:start position:0% that case you can see you can specify in 00:02:37.010 --> 00:02:40.000 align:start position:0% that case you can see you can specify in a<00:02:37.100> configuration<00:02:37.340> file<00:02:37.910> that<00:02:38.320> on<00:02:39.320> the<00:02:39.470> Dow<00:02:39.650> you 00:02:40.000 --> 00:02:40.010 align:start position:0% a configuration file that on the Dow you 00:02:40.010 --> 00:02:44.910 align:start position:0% a configuration file that on the Dow you say<00:02:40.310> okay<00:02:40.960> dollar<00:02:41.960> sign<00:02:42.290> token<00:02:42.860> and<00:02:43.130> that<00:02:43.970> will 00:02:44.910 --> 00:02:44.920 align:start position:0% say okay dollar sign token and that will 00:02:44.920 --> 00:02:48.310 align:start position:0% say okay dollar sign token and that will that<00:02:45.920> will<00:02:45.980> tell<00:02:46.400> in<00:02:46.550> work<00:02:46.790> that<00:02:47.110> okay<00:02:48.110> this 00:02:48.310 --> 00:02:48.320 align:start position:0% that will tell in work that okay this 00:02:48.320 --> 00:02:51.400 align:start position:0% that will tell in work that okay this contract<00:02:48.860> is<00:02:49.010> dependent<00:02:49.610> on<00:02:49.670> the<00:02:49.880> token<00:02:50.330> and<00:02:50.480> I 00:02:51.400 --> 00:02:51.410 align:start position:0% contract is dependent on the token and I 00:02:51.410 --> 00:02:53.380 align:start position:0% contract is dependent on the token and I need<00:02:51.620> to<00:02:51.740> I<00:02:51.920> need<00:02:51.980> first<00:02:52.370> to<00:02:52.520> deploy<00:02:52.850> the<00:02:53.000> token 00:02:53.380 --> 00:02:53.390 align:start position:0% need to I need first to deploy the token 00:02:53.390 --> 00:02:56.440 align:start position:0% need to I need first to deploy the token and<00:02:53.540> then<00:02:53.750> pass<00:02:54.050> the<00:02:54.320> address<00:02:54.890> to<00:02:55.850> the<00:02:55.970> to<00:02:56.300> the 00:02:56.440 --> 00:02:56.450 align:start position:0% and then pass the address to the to the 00:02:56.450 --> 00:03:00.310 align:start position:0% and then pass the address to the to the Dow<00:02:56.600> and<00:02:56.959> you<00:02:57.590> can<00:02:57.709> have<00:02:57.830> a<00:02:57.890> galaxy<00:02:58.400> of<00:02:58.580> or<00:02:59.510> Nats 00:03:00.310 --> 00:03:00.320 align:start position:0% Dow and you can have a galaxy of or Nats 00:03:00.320 --> 00:03:03.430 align:start position:0% Dow and you can have a galaxy of or Nats if<00:03:00.560> you<00:03:00.680> want<00:03:01.010> to<00:03:01.070> call<00:03:01.220> it<00:03:01.340> of<00:03:01.690> of<00:03:02.690> contracts 00:03:03.430 --> 00:03:03.440 align:start position:0% if you want to call it of of contracts 00:03:03.440 --> 00:03:05.050 align:start position:0% if you want to call it of of contracts each<00:03:03.650> depend<00:03:04.010> on<00:03:04.130> each<00:03:04.250> other<00:03:04.459> and<00:03:04.760> embark 00:03:05.050 --> 00:03:05.060 align:start position:0% each depend on each other and embark 00:03:05.060 --> 00:03:07.210 align:start position:0% each depend on each other and embark will<00:03:05.300> determine<00:03:06.020> what<00:03:06.290> is<00:03:06.440> the<00:03:06.560> right<00:03:06.770> order 00:03:07.210 --> 00:03:07.220 align:start position:0% will determine what is the right order 00:03:07.220 --> 00:03:11.229 align:start position:0% will determine what is the right order to<00:03:07.520> deploy<00:03:08.090> the<00:03:08.270> contracts<00:03:09.640> you<00:03:10.640> can<00:03:11.090> also 00:03:11.229 --> 00:03:11.239 align:start position:0% to deploy the contracts you can also 00:03:11.239 --> 00:03:13.750 align:start position:0% to deploy the contracts you can also have<00:03:11.450> contract<00:03:11.980> instances<00:03:12.980> so<00:03:13.250> this<00:03:13.580> is<00:03:13.670> the 00:03:13.750 --> 00:03:13.760 align:start position:0% have contract instances so this is the 00:03:13.760 --> 00:03:17.110 align:start position:0% have contract instances so this is the case<00:03:13.910> that<00:03:13.940> you<00:03:14.150> have<00:03:14.540> a<00:03:14.570> sort<00:03:14.989> of<00:03:16.120> factory 00:03:17.110 --> 00:03:17.120 align:start position:0% case that you have a sort of factory 00:03:17.120 --> 00:03:19.360 align:start position:0% case that you have a sort of factory kind<00:03:17.480> of<00:03:17.600> contract<00:03:18.050> that<00:03:18.230> has<00:03:18.440> all<00:03:19.040> the<00:03:19.250> main 00:03:19.360 --> 00:03:19.370 align:start position:0% kind of contract that has all the main 00:03:19.370 --> 00:03:22.750 align:start position:0% kind of contract that has all the main functionality<00:03:19.850> but<00:03:20.630> any<00:03:20.810> of<00:03:21.520> you<00:03:22.520> have<00:03:22.640> an 00:03:22.750 --> 00:03:22.760 align:start position:0% functionality but any of you have an 00:03:22.760 --> 00:03:24.699 align:start position:0% functionality but any of you have an argument<00:03:22.970> that<00:03:23.420> specifies<00:03:24.140> a<00:03:24.170> particular 00:03:24.699 --> 00:03:24.709 align:start position:0% argument that specifies a particular 00:03:24.709 --> 00:03:26.949 align:start position:0% argument that specifies a particular change<00:03:25.010> so<00:03:25.790> in<00:03:25.910> this<00:03:26.000> example<00:03:26.209> let's<00:03:26.810> say<00:03:26.900> you 00:03:26.949 --> 00:03:26.959 align:start position:0% change so in this example let's say you 00:03:26.959 --> 00:03:29.680 align:start position:0% change so in this example let's say you have<00:03:27.050> a<00:03:27.110> back<00:03:27.440> token<00:03:28.010> contract<00:03:28.520> but<00:03:29.239> only<00:03:29.450> only 00:03:29.680 --> 00:03:29.690 align:start position:0% have a back token contract but only only 00:03:29.690 --> 00:03:31.030 align:start position:0% have a back token contract but only only you<00:03:29.959> know<00:03:30.080> you<00:03:30.170> want<00:03:30.410> to<00:03:30.440> deploy<00:03:30.680> two 00:03:31.030 --> 00:03:31.040 align:start position:0% you know you want to deploy two 00:03:31.040 --> 00:03:33.610 align:start position:0% you know you want to deploy two contracts<00:03:31.550> which<00:03:31.760> is<00:03:31.940> a<00:03:31.970> USD<00:03:32.930> token<00:03:33.350> and<00:03:33.530> a 00:03:33.610 --> 00:03:33.620 align:start position:0% contracts which is a USD token and a 00:03:33.620 --> 00:03:35.920 align:start position:0% contracts which is a USD token and a euro<00:03:33.860> token<00:03:34.340> so<00:03:34.970> in<00:03:35.299> that<00:03:35.420> case<00:03:35.660> you<00:03:35.810> can 00:03:35.920 --> 00:03:35.930 align:start position:0% euro token so in that case you can 00:03:35.930 --> 00:03:39.039 align:start position:0% euro token so in that case you can specify<00:03:36.250> instance<00:03:37.250> of<00:03:37.459> peg<00:03:37.940> token<00:03:38.450> so<00:03:38.930> he 00:03:39.039 --> 00:03:39.049 align:start position:0% specify instance of peg token so he 00:03:39.049 --> 00:03:41.229 align:start position:0% specify instance of peg token so he knows<00:03:39.200> what<00:03:39.410> is<00:03:39.530> the<00:03:39.650> parent<00:03:40.010> contract<00:03:40.760> and 00:03:41.229 --> 00:03:41.239 align:start position:0% knows what is the parent contract and 00:03:41.239 --> 00:03:42.940 align:start position:0% knows what is the parent contract and then<00:03:41.630> you<00:03:41.750> and<00:03:42.140> then<00:03:42.170> you<00:03:42.350> see<00:03:42.590> here<00:03:42.739> in<00:03:42.860> the 00:03:42.940 --> 00:03:42.950 align:start position:0% then you and then you see here in the 00:03:42.950 --> 00:03:45.460 align:start position:0% then you and then you see here in the arguments<00:03:43.519> you<00:03:43.580> have<00:03:43.700> requests<00:03:44.330> Oracle<00:03:45.170> yes 00:03:45.460 --> 00:03:45.470 align:start position:0% arguments you have requests Oracle yes 00:03:45.470 --> 00:03:48.100 align:start position:0% arguments you have requests Oracle yes the<00:03:45.680> JSON<00:03:46.640> so<00:03:46.820> I<00:03:46.880> imagine<00:03:47.060> you're<00:03:47.269> you're 00:03:48.100 --> 00:03:48.110 align:start position:0% the JSON so I imagine you're you're 00:03:48.110 --> 00:03:51.570 align:start position:0% the JSON so I imagine you're you're calling<00:03:48.500> Oracle<00:03:49.010> like<00:03:49.160> Oracle<00:03:49.640> eyes<00:03:49.910> and<00:03:50.269> so 00:03:51.570 --> 00:03:51.580 align:start position:0% calling Oracle like Oracle eyes and so 00:03:51.580 --> 00:03:54.250 align:start position:0% calling Oracle like Oracle eyes and so the<00:03:52.580> two<00:03:52.790> differences<00:03:53.330> in<00:03:53.450> arguments<00:03:53.959> is<00:03:54.049> what 00:03:54.250 --> 00:03:54.260 align:start position:0% the two differences in arguments is what 00:03:54.260 --> 00:03:58.740 align:start position:0% the two differences in arguments is what will<00:03:54.470> make<00:03:54.680> the<00:03:55.340> contracts<00:03:55.790> be<00:03:56.000> different<00:03:56.650> and 00:03:58.740 --> 00:03:58.750 align:start position:0% will make the contracts be different and 00:03:58.750 --> 00:04:01.449 align:start position:0% will make the contracts be different and also<00:03:59.750> if<00:03:59.870> you<00:04:00.019> are<00:04:00.140> using<00:04:00.380> you<00:04:01.160> can<00:04:01.190> also 00:04:01.449 --> 00:04:01.459 align:start position:0% also if you are using you can also 00:04:01.459 --> 00:04:03.250 align:start position:0% also if you are using you can also interact<00:04:01.730> with<00:04:01.910> the<00:04:02.000> existing<00:04:02.480> contracts<00:04:03.049> so 00:04:03.250 --> 00:04:03.260 align:start position:0% interact with the existing contracts so 00:04:03.260 --> 00:04:05.170 align:start position:0% interact with the existing contracts so let's<00:04:03.920> say<00:04:04.010> we<00:04:04.220> are<00:04:04.250> interacting<00:04:04.850> with<00:04:04.970> the 00:04:05.170 --> 00:04:05.180 align:start position:0% let's say we are interacting with the 00:04:05.180 --> 00:04:09.250 align:start position:0% let's say we are interacting with the dgs<00:04:06.820> contracts<00:04:07.820> they<00:04:08.299> can<00:04:08.510> specify<00:04:08.959> the 00:04:09.250 --> 00:04:09.260 align:start position:0% dgs contracts they can specify the 00:04:09.260 --> 00:04:11.560 align:start position:0% dgs contracts they can specify the address<00:04:09.470> and<00:04:10.100> import<00:04:10.549> we'll<00:04:10.670> just<00:04:11.000> use<00:04:11.269> that 00:04:11.560 --> 00:04:11.570 align:start position:0% address and import we'll just use that 00:04:11.570 --> 00:04:15.460 align:start position:0% address and import we'll just use that that's<00:04:12.350> address<00:04:12.709> and<00:04:13.480> it's<00:04:14.480> also<00:04:14.660> a<00:04:14.840> support 00:04:15.460 --> 00:04:15.470 align:start position:0% that's address and it's also a support 00:04:15.470 --> 00:04:19.030 align:start position:0% that's address and it's also a support for<00:04:16.209> deployment<00:04:17.209> commands<00:04:17.750> that<00:04:18.049> there<00:04:18.950> are 00:04:19.030 --> 00:04:19.040 align:start position:0% for deployment commands that there are 00:04:19.040 --> 00:04:22.420 align:start position:0% for deployment commands that there are executors<00:04:19.609> once<00:04:19.940> the<00:04:20.870> contract<00:04:21.229> is<00:04:21.500> deployed 00:04:22.420 --> 00:04:22.430 align:start position:0% executors once the contract is deployed 00:04:22.430 --> 00:04:25.780 align:start position:0% executors once the contract is deployed so<00:04:23.240> in<00:04:23.390> this<00:04:23.510> case<00:04:23.810> i<00:04:24.340> have<00:04:25.340> an<00:04:25.460> account 00:04:25.780 --> 00:04:25.790 align:start position:0% so in this case i have an account 00:04:25.790 --> 00:04:28.210 align:start position:0% so in this case i have an account manager<00:04:26.270> i<00:04:26.330> want<00:04:26.510> to<00:04:26.600> manage<00:04:27.260> my<00:04:27.470> gold<00:04:27.770> tokens 00:04:28.210 --> 00:04:28.220 align:start position:0% manager i want to manage my gold tokens 00:04:28.220 --> 00:04:31.420 align:start position:0% manager i want to manage my gold tokens and<00:04:28.660> on<00:04:29.660> deploy<00:04:30.290> then<00:04:30.590> i<00:04:30.710> transfer<00:04:30.950> from 00:04:31.420 --> 00:04:31.430 align:start position:0% and on deploy then i transfer from 00:04:31.430 --> 00:04:34.060 align:start position:0% and on deploy then i transfer from myself<00:04:31.669> a<00:04:32.060> thousand<00:04:32.479> tokens<00:04:32.900> to<00:04:33.470> that<00:04:33.680> to<00:04:33.890> the 00:04:34.060 --> 00:04:34.070 align:start position:0% myself a thousand tokens to that to the 00:04:34.070 --> 00:04:39.290 align:start position:0% myself a thousand tokens to that to the recently<00:04:34.520> deployed<00:04:35.080> contract<00:04:36.820> now 00:04:39.290 --> 00:04:39.300 align:start position:0% recently deployed contract now 00:04:39.300 --> 00:04:43.410 align:start position:0% recently deployed contract now nor<00:04:40.300> embark<00:04:40.750> as<00:04:41.490> so<00:04:42.490> as<00:04:42.610> a<00:04:42.670> new<00:04:42.880> set<00:04:43.090> of<00:04:43.120> goals 00:04:43.410 --> 00:04:43.420 align:start position:0% nor embark as so as a new set of goals 00:04:43.420 --> 00:04:46.460 align:start position:0% nor embark as so as a new set of goals the<00:04:43.810> the<00:04:44.470> goal<00:04:44.680> is<00:04:44.860> in<00:04:44.980> inner<00:04:45.280> bark<00:04:45.490> one<00:04:45.760> was<00:04:45.970> to 00:04:46.460 --> 00:04:46.470 align:start position:0% the the goal is in inner bark one was to 00:04:46.470 --> 00:04:50.610 align:start position:0% the the goal is in inner bark one was to was<00:04:47.470> to<00:04:47.500> provide<00:04:47.920> good<00:04:48.430> deployment<00:04:49.210> tools<00:04:49.620> for 00:04:50.610 --> 00:04:50.620 align:start position:0% was to provide good deployment tools for 00:04:50.620 --> 00:04:54.180 align:start position:0% was to provide good deployment tools for this<00:04:50.800> kind<00:04:51.040> of<00:04:51.360> complex<00:04:52.360> contracts<00:04:53.290> now 00:04:54.180 --> 00:04:54.190 align:start position:0% this kind of complex contracts now 00:04:54.190 --> 00:04:56.580 align:start position:0% this kind of complex contracts now embark<00:04:55.120> two<00:04:55.270> will<00:04:55.480> focus<00:04:55.780> a<00:04:55.930> bit<00:04:56.140> more<00:04:56.200> on<00:04:56.470> the 00:04:56.580 --> 00:04:56.590 align:start position:0% embark two will focus a bit more on the 00:04:56.590 --> 00:04:58.710 align:start position:0% embark two will focus a bit more on the client<00:04:57.040> side<00:04:57.100> and<00:04:57.490> focus<00:04:57.970> more<00:04:58.120> in 00:04:58.710 --> 00:04:58.720 align:start position:0% client side and focus more in 00:04:58.720 --> 00:05:02.040 align:start position:0% client side and focus more in integrations<00:04:59.650> with<00:04:59.950> storage<00:05:00.820> layers<00:05:01.120> such<00:05:01.870> as 00:05:02.040 --> 00:05:02.050 align:start position:0% integrations with storage layers such as 00:05:02.050 --> 00:05:05.150 align:start position:0% integrations with storage layers such as swarm<00:05:02.950> and<00:05:03.670> communication<00:05:04.330> layers<00:05:04.540> such<00:05:04.870> as 00:05:05.150 --> 00:05:05.160 align:start position:0% swarm and communication layers such as 00:05:05.160 --> 00:05:09.540 align:start position:0% swarm and communication layers such as whisper<00:05:06.630> and<00:05:07.630> as<00:05:07.930> well<00:05:08.110> as<00:05:08.230> providing<00:05:08.710> easier 00:05:09.540 --> 00:05:09.550 align:start position:0% whisper and as well as providing easier 00:05:09.550 --> 00:05:12.060 align:start position:0% whisper and as well as providing easier ways<00:05:09.760> to<00:05:09.940> distribute<00:05:10.440> applications<00:05:11.440> so 00:05:12.060 --> 00:05:12.070 align:start position:0% ways to distribute applications so 00:05:12.070 --> 00:05:15.510 align:start position:0% ways to distribute applications so embark<00:05:12.520> to<00:05:12.640> is<00:05:12.940> actually<00:05:13.060> read<00:05:13.450> done<00:05:13.960> from<00:05:14.520> was 00:05:15.510 --> 00:05:15.520 align:start position:0% embark to is actually read done from was 00:05:15.520 --> 00:05:19.230 align:start position:0% embark to is actually read done from was redone<00:05:16.090> from<00:05:16.300> scratch<00:05:17.670> by<00:05:18.670> default<00:05:19.000> it<00:05:19.120> comes 00:05:19.230 --> 00:05:19.240 align:start position:0% redone from scratch by default it comes 00:05:19.240 --> 00:05:21.180 align:start position:0% redone from scratch by default it comes with<00:05:19.540> this<00:05:19.720> dashboard<00:05:20.380> you<00:05:20.920> can<00:05:21.070> actually 00:05:21.180 --> 00:05:21.190 align:start position:0% with this dashboard you can actually 00:05:21.190 --> 00:05:23.280 align:start position:0% with this dashboard you can actually override<00:05:22.180> this<00:05:22.480> if<00:05:22.660> you<00:05:22.750> don't<00:05:22.870> want<00:05:23.050> to<00:05:23.140> if<00:05:23.230> we 00:05:23.280 --> 00:05:23.290 align:start position:0% override this if you don't want to if we 00:05:23.290 --> 00:05:26.520 align:start position:0% override this if you don't want to if we want<00:05:23.410> to<00:05:23.500> old<00:05:23.710> lock<00:05:24.010> I<00:05:24.480> just<00:05:25.480> found<00:05:25.720> that<00:05:25.870> the 00:05:26.520 --> 00:05:26.530 align:start position:0% want to old lock I just found that the 00:05:26.530 --> 00:05:29.100 align:start position:0% want to old lock I just found that the the<00:05:27.520> look<00:05:27.670> and<00:05:27.910> could<00:05:28.240> be<00:05:28.360> a<00:05:28.390> very<00:05:28.690> confusing 00:05:29.100 --> 00:05:29.110 align:start position:0% the look and could be a very confusing 00:05:29.110 --> 00:05:29.970 align:start position:0% the look and could be a very confusing if<00:05:29.290> you're<00:05:29.440> dealing<00:05:29.560> with<00:05:29.740> a<00:05:29.830> lot<00:05:29.950> of 00:05:29.970 --> 00:05:29.980 align:start position:0% if you're dealing with a lot of 00:05:29.980 --> 00:05:32.490 align:start position:0% if you're dealing with a lot of contracts<00:05:30.520> because<00:05:30.760> it<00:05:30.880> was<00:05:31.290> hard<00:05:32.290> to<00:05:32.470> know 00:05:32.490 --> 00:05:32.500 align:start position:0% contracts because it was hard to know 00:05:32.500 --> 00:05:34.590 align:start position:0% contracts because it was hard to know exactly<00:05:33.130> what<00:05:33.310> was<00:05:33.490> the<00:05:33.610> status<00:05:34.090> of<00:05:34.240> different 00:05:34.590 --> 00:05:34.600 align:start position:0% exactly what was the status of different 00:05:34.600 --> 00:05:37.800 align:start position:0% exactly what was the status of different contracts<00:05:35.100> so<00:05:36.100> I<00:05:36.550> did<00:05:36.880> this<00:05:37.000> dashboard<00:05:37.300> so 00:05:37.800 --> 00:05:37.810 align:start position:0% contracts so I did this dashboard so 00:05:37.810 --> 00:05:41.430 align:start position:0% contracts so I did this dashboard so it's<00:05:37.930> it<00:05:38.940> it's<00:05:39.940> us<00:05:40.150> for<00:05:40.780> example<00:05:40.840> does<00:05:41.260> this 00:05:41.430 --> 00:05:41.440 align:start position:0% it's it it's us for example does this 00:05:41.440 --> 00:05:44.160 align:start position:0% it's it it's us for example does this section<00:05:41.890> that<00:05:42.100> says<00:05:42.390> okay<00:05:43.390> the<00:05:43.690> particular 00:05:44.160 --> 00:05:44.170 align:start position:0% section that says okay the particular 00:05:44.170 --> 00:05:45.420 align:start position:0% section that says okay the particular contracts<00:05:44.590> you<00:05:44.710> can<00:05:44.740> see<00:05:45.040> I<00:05:45.070> have<00:05:45.280> they've 00:05:45.420 --> 00:05:45.430 align:start position:0% contracts you can see I have they've 00:05:45.430 --> 00:05:47.670 align:start position:0% contracts you can see I have they've been<00:05:45.610> deployed<00:05:46.030> where<00:05:46.420> are<00:05:46.570> they<00:05:46.810> was<00:05:47.500> there 00:05:47.670 --> 00:05:47.680 align:start position:0% been deployed where are they was there 00:05:47.680 --> 00:05:50.190 align:start position:0% been deployed where are they was there an<00:05:47.800> error<00:05:48.010> what<00:05:48.490> is<00:05:48.610> there<00:05:48.820> or<00:05:49.200> still 00:05:50.190 --> 00:05:50.200 align:start position:0% an error what is there or still 00:05:50.200 --> 00:05:52.640 align:start position:0% an error what is there or still deploying<00:05:50.700> there's<00:05:51.700> another<00:05:51.910> section<00:05:52.270> that 00:05:52.640 --> 00:05:52.650 align:start position:0% deploying there's another section that 00:05:52.650 --> 00:05:55.200 align:start position:0% deploying there's another section that you<00:05:53.650> have<00:05:53.740> the<00:05:53.860> current<00:05:54.160> chain<00:05:54.850> that<00:05:55.030> you're 00:05:55.200 --> 00:05:55.210 align:start position:0% you have the current chain that you're 00:05:55.210 --> 00:05:56.640 align:start position:0% you have the current chain that you're using<00:05:55.450> in<00:05:55.690> this<00:05:55.780> case<00:05:55.930> they<00:05:56.140> development 00:05:56.640 --> 00:05:56.650 align:start position:0% using in this case they development 00:05:56.650 --> 00:05:59.430 align:start position:0% using in this case they development chain<00:05:56.910> what<00:05:57.910> embark<00:05:58.270> is<00:05:58.390> doing<00:05:58.720> right<00:05:58.900> now<00:05:58.930> and 00:05:59.430 --> 00:05:59.440 align:start position:0% chain what embark is doing right now and 00:05:59.440 --> 00:06:01.950 align:start position:0% chain what embark is doing right now and available<00:05:59.880> services<00:06:00.880> so<00:06:01.420> let's<00:06:01.660> say<00:06:01.750> if<00:06:01.810> your 00:06:01.950 --> 00:06:01.960 align:start position:0% available services so let's say if your 00:06:01.960 --> 00:06:03.960 align:start position:0% available services so let's say if your tap<00:06:02.140> was<00:06:02.290> using<00:06:02.560> IP<00:06:02.710> FS<00:06:03.100> and<00:06:03.340> ipfs<00:06:03.790> was 00:06:03.960 --> 00:06:03.970 align:start position:0% tap was using IP FS and ipfs was 00:06:03.970 --> 00:06:06.480 align:start position:0% tap was using IP FS and ipfs was unavailable<00:06:04.330> it<00:06:05.050> would<00:06:05.200> show<00:06:05.380> up<00:06:05.560> right<00:06:06.130> here 00:06:06.480 --> 00:06:06.490 align:start position:0% unavailable it would show up right here 00:06:06.490 --> 00:06:11.090 align:start position:0% unavailable it would show up right here and<00:06:07.590> it<00:06:08.590> finally<00:06:08.920> also<00:06:09.130> comes<00:06:09.550> with<00:06:09.760> a<00:06:10.420> console 00:06:11.090 --> 00:06:11.100 align:start position:0% and it finally also comes with a console 00:06:11.100 --> 00:06:13.700 align:start position:0% and it finally also comes with a console so<00:06:12.100> you<00:06:12.130> can<00:06:12.370> use<00:06:12.520> that<00:06:12.640> console<00:06:13.030> with<00:06:13.210> to 00:06:13.700 --> 00:06:13.710 align:start position:0% so you can use that console with to 00:06:13.710 --> 00:06:15.840 align:start position:0% so you can use that console with to inter<00:06:14.710> interact<00:06:15.160> with<00:06:15.310> the<00:06:15.400> existing 00:06:15.840 --> 00:06:15.850 align:start position:0% inter interact with the existing 00:06:15.850 --> 00:06:18.330 align:start position:0% inter interact with the existing contracts<00:06:16.510> or<00:06:16.660> to<00:06:16.900> tell<00:06:17.740> embark<00:06:18.070> to<00:06:18.190> do 00:06:18.330 --> 00:06:18.340 align:start position:0% contracts or to tell embark to do 00:06:18.340 --> 00:06:21.570 align:start position:0% contracts or to tell embark to do something<00:06:18.760> like<00:06:18.940> redeploy<00:06:19.750> in<00:06:19.810> I<00:06:20.530> will<00:06:21.310> deploy 00:06:21.570 --> 00:06:21.580 align:start position:0% something like redeploy in I will deploy 00:06:21.580 --> 00:06:23.870 align:start position:0% something like redeploy in I will deploy another<00:06:21.700> contract<00:06:22.390> or<00:06:22.690> add<00:06:23.200> another<00:06:23.650> account 00:06:23.870 --> 00:06:23.880 align:start position:0% another contract or add another account 00:06:23.880 --> 00:06:28.580 align:start position:0% another contract or add another account etc<00:06:25.800> in<00:06:26.800> park<00:06:27.070> to<00:06:27.190> also<00:06:27.490> introduces<00:06:28.390> a 00:06:28.580 --> 00:06:28.590 align:start position:0% etc in park to also introduces a 00:06:28.590 --> 00:06:31.110 align:start position:0% etc in park to also introduces a client-side<00:06:29.590> library<00:06:30.130> which<00:06:30.670> is<00:06:30.880> called 00:06:31.110 --> 00:06:31.120 align:start position:0% client-side library which is called 00:06:31.120 --> 00:06:35.310 align:start position:0% client-side library which is called embark<00:06:32.050> GS<00:06:32.350> so<00:06:33.220> that<00:06:33.940> library<00:06:34.390> is<00:06:34.420> meant<00:06:35.080> to 00:06:35.310 --> 00:06:35.320 align:start position:0% embark GS so that library is meant to 00:06:35.320 --> 00:06:38.250 align:start position:0% embark GS so that library is meant to aid<00:06:35.350> the<00:06:35.860> developers<00:06:37.020> interacting<00:06:38.020> with 00:06:38.250 --> 00:06:38.260 align:start position:0% aid the developers interacting with 00:06:38.260 --> 00:06:39.870 align:start position:0% aid the developers interacting with contracts<00:06:39.190> it<00:06:39.310> makes<00:06:39.460> things<00:06:39.670> a<00:06:39.730> bit<00:06:39.760> more 00:06:39.870 --> 00:06:39.880 align:start position:0% contracts it makes things a bit more 00:06:39.880 --> 00:06:42.480 align:start position:0% contracts it makes things a bit more simpler<00:06:40.390> and<00:06:40.990> also<00:06:41.140> provides<00:06:41.620> api's<00:06:42.040> to 00:06:42.480 --> 00:06:42.490 align:start position:0% simpler and also provides api's to 00:06:42.490 --> 00:06:45.750 align:start position:0% simpler and also provides api's to abstract<00:06:43.590> interaction<00:06:44.590> with<00:06:44.830> those<00:06:45.520> layers 00:06:45.750 --> 00:06:45.760 align:start position:0% abstract interaction with those layers 00:06:45.760 --> 00:06:48.810 align:start position:0% abstract interaction with those layers such<00:06:46.210> as<00:06:46.390> storage<00:06:46.810> in'<00:06:46.990> and<00:06:47.580> communication<00:06:48.580> so 00:06:48.810 --> 00:06:48.820 align:start position:0% such as storage in' and communication so 00:06:48.820 --> 00:06:51.480 align:start position:0% such as storage in' and communication so you<00:06:48.850> can<00:06:49.150> easily<00:06:49.710> switch 00:06:51.480 --> 00:06:51.490 align:start position:0% you can easily switch 00:06:51.490 --> 00:06:54.120 align:start position:0% you can easily switch the<00:06:51.900> technology<00:06:52.900> if<00:06:53.020> you<00:06:53.440> need<00:06:53.620> to<00:06:53.740> because 00:06:54.120 --> 00:06:54.130 align:start position:0% the technology if you need to because 00:06:54.130 --> 00:06:55.890 align:start position:0% the technology if you need to because different<00:06:54.880> technologies<00:06:55.389> generally<00:06:55.569> have 00:06:55.890 --> 00:06:55.900 align:start position:0% different technologies generally have 00:06:55.900 --> 00:06:59.219 align:start position:0% different technologies generally have different<00:06:56.440> trade-offs<00:06:57.069> and<00:06:57.520> your<00:06:58.419> your<00:06:58.840> your 00:06:59.219 --> 00:06:59.229 align:start position:0% different trade-offs and your your your 00:06:59.229 --> 00:07:01.469 align:start position:0% different trade-offs and your your your tap<00:06:59.470> might<00:06:59.710> have<00:06:59.889> different<00:07:00.190> needs<00:07:00.699> depending 00:07:01.469 --> 00:07:01.479 align:start position:0% tap might have different needs depending 00:07:01.479 --> 00:07:06.210 align:start position:0% tap might have different needs depending on<00:07:01.960> on<00:07:02.110> what<00:07:02.199> you<00:07:02.560> want<00:07:02.979> to<00:07:03.069> do<00:07:03.220> so<00:07:05.099> so<00:07:06.099> the 00:07:06.210 --> 00:07:06.220 align:start position:0% on on what you want to do so so the 00:07:06.220 --> 00:07:08.850 align:start position:0% on on what you want to do so so the library<00:07:06.569> introduces<00:07:07.569> promises<00:07:08.500> which<00:07:08.710> is 00:07:08.850 --> 00:07:08.860 align:start position:0% library introduces promises which is 00:07:08.860 --> 00:07:13.890 align:start position:0% library introduces promises which is long<00:07:09.069> overdue<00:07:10.500> it's<00:07:11.500> also<00:07:12.750> it's<00:07:13.750> also 00:07:13.890 --> 00:07:13.900 align:start position:0% long overdue it's also it's also 00:07:13.900 --> 00:07:15.960 align:start position:0% long overdue it's also it's also introduces<00:07:14.500> named<00:07:14.770> parameters<00:07:15.370> so<00:07:15.580> you<00:07:15.610> can 00:07:15.960 --> 00:07:15.970 align:start position:0% introduces named parameters so you can 00:07:15.970 --> 00:07:18.450 align:start position:0% introduces named parameters so you can still<00:07:16.240> pass<00:07:16.960> a<00:07:16.990> list<00:07:17.349> of<00:07:17.590> arguments<00:07:18.039> if<00:07:18.340> you 00:07:18.450 --> 00:07:18.460 align:start position:0% still pass a list of arguments if you 00:07:18.460 --> 00:07:20.490 align:start position:0% still pass a list of arguments if you want<00:07:18.639> to<00:07:18.789> but<00:07:19.060> you<00:07:19.569> can<00:07:19.750> also<00:07:19.870> specify<00:07:20.229> the 00:07:20.490 --> 00:07:20.500 align:start position:0% want to but you can also specify the 00:07:20.500 --> 00:07:26.400 align:start position:0% want to but you can also specify the name<00:07:20.860> of<00:07:21.130> the<00:07:21.580> of<00:07:22.419> the<00:07:22.810> argument<00:07:23.259> and<00:07:25.110> I<00:07:26.110> know<00:07:26.380> I 00:07:26.400 --> 00:07:26.410 align:start position:0% name of the of the argument and I know I 00:07:26.410 --> 00:07:28.760 align:start position:0% name of the of the argument and I know I think<00:07:26.530> it<00:07:26.770> does<00:07:26.919> also<00:07:27.160> that<00:07:27.580> it's<00:07:28.030> actually 00:07:28.760 --> 00:07:28.770 align:start position:0% think it does also that it's actually 00:07:28.770 --> 00:07:31.260 align:start position:0% think it does also that it's actually automatically<00:07:29.770> calculates<00:07:30.550> the<00:07:30.669> gas<00:07:30.880> cost 00:07:31.260 --> 00:07:31.270 align:start position:0% automatically calculates the gas cost 00:07:31.270 --> 00:07:35.700 align:start position:0% automatically calculates the gas cost and<00:07:31.660> puts<00:07:32.320> that<00:07:32.410> in<00:07:32.830> the<00:07:32.979> call<00:07:33.220> so<00:07:34.560> because<00:07:35.560> it 00:07:35.700 --> 00:07:35.710 align:start position:0% and puts that in the call so because it 00:07:35.710 --> 00:07:37.020 align:start position:0% and puts that in the call so because it sometimes<00:07:36.070> happens<00:07:36.400> if<00:07:36.520> you're<00:07:36.639> working<00:07:36.820> in<00:07:36.940> a 00:07:37.020 --> 00:07:37.030 align:start position:0% sometimes happens if you're working in a 00:07:37.030 --> 00:07:38.700 align:start position:0% sometimes happens if you're working in a method<00:07:37.419> and<00:07:38.050> it<00:07:38.169> changes<00:07:38.530> it<00:07:38.620> suddenly 00:07:38.700 --> 00:07:38.710 align:start position:0% method and it changes it suddenly 00:07:38.710 --> 00:07:41.129 align:start position:0% method and it changes it suddenly becomes<00:07:39.099> very<00:07:39.340> complex<00:07:39.849> and<00:07:40.389> it<00:07:40.720> just<00:07:40.900> stops 00:07:41.129 --> 00:07:41.139 align:start position:0% becomes very complex and it just stops 00:07:41.139 --> 00:07:42.360 align:start position:0% becomes very complex and it just stops working<00:07:41.410> because<00:07:41.740> it<00:07:41.919> didn't<00:07:42.190> have<00:07:42.280> enough 00:07:42.360 --> 00:07:42.370 align:start position:0% working because it didn't have enough 00:07:42.370 --> 00:07:45.240 align:start position:0% working because it didn't have enough gas<00:07:42.909> so<00:07:43.539> important<00:07:44.259> tries<00:07:44.650> to<00:07:44.800> take<00:07:44.979> care<00:07:45.220> of 00:07:45.240 --> 00:07:45.250 align:start position:0% gas so important tries to take care of 00:07:45.250 --> 00:07:48.710 align:start position:0% gas so important tries to take care of this<00:07:45.570> so<00:07:46.570> it<00:07:46.659> doesn't<00:07:46.870> happen<00:07:47.159> it<00:07:48.159> does<00:07:48.340> some 00:07:48.710 --> 00:07:48.720 align:start position:0% this so it doesn't happen it does some 00:07:48.720 --> 00:07:51.870 align:start position:0% this so it doesn't happen it does some it's<00:07:49.720> also<00:07:49.990> times<00:07:50.289> to<00:07:50.440> do<00:07:50.560> some<00:07:50.880> automatic 00:07:51.870 --> 00:07:51.880 align:start position:0% it's also times to do some automatic 00:07:51.880 --> 00:07:55.649 align:start position:0% it's also times to do some automatic type<00:07:52.569> of<00:07:52.780> conversion<00:07:53.590> so<00:07:54.520> if<00:07:54.639> you<00:07:54.819> have<00:07:54.909> a<00:07:54.970> big 00:07:55.649 --> 00:07:55.659 align:start position:0% type of conversion so if you have a big 00:07:55.659 --> 00:07:59.070 align:start position:0% type of conversion so if you have a big ain't<00:07:55.930> it<00:07:56.470> will<00:07:56.740> just<00:07:56.949> do<00:07:57.099> a<00:07:57.130> to<00:07:57.400> number<00:07:57.900> if<00:07:58.900> you 00:07:59.070 --> 00:07:59.080 align:start position:0% ain't it will just do a to number if you 00:07:59.080 --> 00:08:01.770 align:start position:0% ain't it will just do a to number if you have<00:07:59.169> say<00:08:00.130> an<00:08:00.400> axe<00:08:00.639> that<00:08:01.000> was<00:08:01.300> supposed<00:08:01.570> to<00:08:01.599> be 00:08:01.770 --> 00:08:01.780 align:start position:0% have say an axe that was supposed to be 00:08:01.780 --> 00:08:03.870 align:start position:0% have say an axe that was supposed to be a<00:08:01.810> string<00:08:02.169> you've<00:08:02.650> also<00:08:02.800> converted<00:08:03.400> to<00:08:03.550> a 00:08:03.870 --> 00:08:03.880 align:start position:0% a string you've also converted to a 00:08:03.880 --> 00:08:05.999 align:start position:0% a string you've also converted to a string<00:08:04.180> this<00:08:04.840> is<00:08:04.960> all<00:08:05.050> also<00:08:05.320> configurable 00:08:05.999 --> 00:08:06.009 align:start position:0% string this is all also configurable 00:08:06.009 --> 00:08:08.520 align:start position:0% string this is all also configurable because<00:08:06.370> you<00:08:06.460> might<00:08:06.639> have<00:08:06.820> different<00:08:07.530> use 00:08:08.520 --> 00:08:08.530 align:start position:0% because you might have different use 00:08:08.530 --> 00:08:12.240 align:start position:0% because you might have different use cases<00:08:08.800> of<00:08:09.219> course<00:08:09.449> and<00:08:10.449> it's<00:08:11.409> also<00:08:11.560> does<00:08:12.159> the 00:08:12.240 --> 00:08:12.250 align:start position:0% cases of course and it's also does the 00:08:12.250 --> 00:08:14.370 align:start position:0% cases of course and it's also does the same<00:08:12.310> thing<00:08:12.610> what's<00:08:12.820> struct<00:08:13.180> usually<00:08:14.020> call<00:08:14.349> a 00:08:14.370 --> 00:08:14.380 align:start position:0% same thing what's struct usually call a 00:08:14.380 --> 00:08:17.040 align:start position:0% same thing what's struct usually call a struct<00:08:14.830> you<00:08:15.009> will<00:08:15.190> it<00:08:16.180> will<00:08:16.360> return<00:08:16.780> you<00:08:16.840> a 00:08:17.040 --> 00:08:17.050 align:start position:0% struct you will it will return you a 00:08:17.050 --> 00:08:20.339 align:start position:0% struct you will it will return you a list<00:08:17.349> of<00:08:17.590> the<00:08:17.860> parameters<00:08:18.490> and<00:08:19.020> and<00:08:20.020> if<00:08:20.199> you 00:08:20.339 --> 00:08:20.349 align:start position:0% list of the parameters and and if you 00:08:20.349 --> 00:08:22.050 align:start position:0% list of the parameters and and if you change<00:08:20.590> the<00:08:20.710> order<00:08:20.889> will<00:08:21.159> also<00:08:21.550> affect<00:08:21.940> that 00:08:22.050 --> 00:08:22.060 align:start position:0% change the order will also affect that 00:08:22.060 --> 00:08:24.870 align:start position:0% change the order will also affect that order<00:08:22.449> so<00:08:23.139> now<00:08:23.409> no<00:08:23.889> it's<00:08:24.099> just<00:08:24.310> a<00:08:24.490> converts 00:08:24.870 --> 00:08:24.880 align:start position:0% order so now no it's just a converts 00:08:24.880 --> 00:08:27.089 align:start position:0% order so now no it's just a converts automatically<00:08:25.539> to<00:08:25.690> an<00:08:25.840> ash<00:08:26.050> so<00:08:26.680> you<00:08:26.740> can<00:08:26.889> just 00:08:27.089 --> 00:08:27.099 align:start position:0% automatically to an ash so you can just 00:08:27.099 --> 00:08:29.999 align:start position:0% automatically to an ash so you can just convert<00:08:27.400> it<00:08:27.580> by<00:08:27.729> say<00:08:28.210> you<00:08:28.719> can<00:08:28.900> refer<00:08:29.560> to<00:08:29.590> it<00:08:29.740> as 00:08:29.999 --> 00:08:30.009 align:start position:0% convert it by say you can refer to it as 00:08:30.009 --> 00:08:33.300 align:start position:0% convert it by say you can refer to it as dot<00:08:30.310> outer<00:08:30.610> instead<00:08:31.300> of<00:08:31.589> position<00:08:32.589> zero<00:08:32.890> to 00:08:33.300 --> 00:08:33.310 align:start position:0% dot outer instead of position zero to 00:08:33.310 --> 00:08:36.899 align:start position:0% dot outer instead of position zero to get<00:08:33.789> the<00:08:33.909> outer<00:08:34.740> and<00:08:35.740> it's<00:08:36.279> also<00:08:36.579> supports 00:08:36.899 --> 00:08:36.909 align:start position:0% get the outer and it's also supports 00:08:36.909 --> 00:08:40.319 align:start position:0% get the outer and it's also supports client-side<00:08:37.860> deployment<00:08:38.860> so<00:08:38.950> you<00:08:39.039> can<00:08:39.329> devote 00:08:40.319 --> 00:08:40.329 align:start position:0% client-side deployment so you can devote 00:08:40.329 --> 00:08:42.269 align:start position:0% client-side deployment so you can devote the<00:08:40.510> contract<00:08:40.899> only<00:08:41.079> only<00:08:41.529> bark<00:08:41.860> just<00:08:42.099> like 00:08:42.269 --> 00:08:42.279 align:start position:0% the contract only only bark just like 00:08:42.279 --> 00:08:44.760 align:start position:0% the contract only only bark just like you<00:08:42.459> do<00:08:42.729> now<00:08:42.760> but<00:08:43.180> and<00:08:43.419> but<00:08:44.229> you<00:08:44.320> can<00:08:44.470> make<00:08:44.649> it 00:08:44.760 --> 00:08:44.770 align:start position:0% you do now but and but you can make it 00:08:44.770 --> 00:08:48.930 align:start position:0% you do now but and but you can make it available<00:08:45.010> on<00:08:45.899> the<00:08:46.899> client<00:08:47.290> side<00:08:47.320> so<00:08:48.040> you<00:08:48.730> can 00:08:48.930 --> 00:08:48.940 align:start position:0% available on the client side so you can 00:08:48.940 --> 00:08:51.750 align:start position:0% available on the client side so you can dynamically<00:08:49.810> deploy<00:08:50.170> contracts<00:08:50.829> there<00:08:51.700> are 00:08:51.750 --> 00:08:51.760 align:start position:0% dynamically deploy contracts there are 00:08:51.760 --> 00:08:53.510 align:start position:0% dynamically deploy contracts there are certain<00:08:52.000> type<00:08:52.149> of<00:08:52.180> applications<00:08:52.959> that 00:08:53.510 --> 00:08:53.520 align:start position:0% certain type of applications that 00:08:53.520 --> 00:08:56.550 align:start position:0% certain type of applications that require<00:08:54.520> that<00:08:55.089> sort<00:08:55.300> of<00:08:55.510> functionality<00:08:56.170> or 00:08:56.550 --> 00:08:56.560 align:start position:0% require that sort of functionality or 00:08:56.560 --> 00:09:00.480 align:start position:0% require that sort of functionality or very<00:08:56.860> dynamic<00:08:57.310> adapts<00:08:58.860> example<00:08:59.860> this<00:09:00.010> is<00:09:00.220> if 00:09:00.480 --> 00:09:00.490 align:start position:0% very dynamic adapts example this is if 00:09:00.490 --> 00:09:02.280 align:start position:0% very dynamic adapts example this is if you<00:09:00.610> wanted<00:09:00.850> to<00:09:00.970> do<00:09:01.089> like<00:09:01.240> a<00:09:01.300> font<00:09:01.690> app<00:09:01.990> like 00:09:02.280 --> 00:09:02.290 align:start position:0% you wanted to do like a font app like 00:09:02.290 --> 00:09:04.920 align:start position:0% you wanted to do like a font app like create<00:09:03.220> your<00:09:03.370> own<00:09:03.430> token<00:09:03.970> you<00:09:04.449> would<00:09:04.570> use<00:09:04.750> this 00:09:04.920 --> 00:09:04.930 align:start position:0% create your own token you would use this 00:09:04.930 --> 00:09:05.400 align:start position:0% create your own token you would use this sort<00:09:05.170> of 00:09:05.400 --> 00:09:05.410 align:start position:0% sort of 00:09:05.410 --> 00:09:08.460 align:start position:0% sort of shanell<00:09:05.790> arrival<00:09:06.790> of<00:09:06.879> a<00:09:07.029> form<00:09:07.329> the<00:09:07.990> user<00:09:08.199> would 00:09:08.460 --> 00:09:08.470 align:start position:0% shanell arrival of a form the user would 00:09:08.470 --> 00:09:10.350 align:start position:0% shanell arrival of a form the user would put<00:09:08.649> the<00:09:09.100> name<00:09:09.129> with<00:09:09.339> talking<00:09:09.970> some 00:09:10.350 --> 00:09:10.360 align:start position:0% put the name with talking some 00:09:10.360 --> 00:09:12.660 align:start position:0% put the name with talking some parameters<00:09:11.050> like<00:09:11.170> the<00:09:11.230> supply<00:09:11.709> and<00:09:12.009> then 00:09:12.660 --> 00:09:12.670 align:start position:0% parameters like the supply and then 00:09:12.670 --> 00:09:14.790 align:start position:0% parameters like the supply and then that's<00:09:13.600> what<00:09:13.750> that's<00:09:14.050> the<00:09:14.170> command<00:09:14.379> is<00:09:14.560> pretty 00:09:14.790 --> 00:09:14.800 align:start position:0% that's what that's the command is pretty 00:09:14.800 --> 00:09:18.150 align:start position:0% that's what that's the command is pretty much<00:09:14.920> would<00:09:15.160> run<00:09:15.339> on<00:09:15.519> the<00:09:15.579> client<00:09:15.850> side<00:09:17.160> now 00:09:18.150 --> 00:09:18.160 align:start position:0% much would run on the client side now 00:09:18.160 --> 00:09:21.600 align:start position:0% much would run on the client side now for<00:09:18.699> the<00:09:18.850> communication<00:09:20.610> communication 00:09:21.600 --> 00:09:21.610 align:start position:0% for the communication communication 00:09:21.610 --> 00:09:24.840 align:start position:0% for the communication communication layer<00:09:21.970> so<00:09:22.899> so<00:09:23.680> in<00:09:23.800> part<00:09:24.009> Troy's<00:09:24.250> nota<00:09:24.550> app 00:09:24.840 --> 00:09:24.850 align:start position:0% layer so so in part Troy's nota app 00:09:24.850 --> 00:09:28.559 align:start position:0% layer so so in part Troy's nota app tries<00:09:25.779> to<00:09:25.930> provide<00:09:26.259> an<00:09:26.410> abstraction<00:09:26.920> on<00:09:27.569> on 00:09:28.559 --> 00:09:28.569 align:start position:0% tries to provide an abstraction on on 00:09:28.569 --> 00:09:31.530 align:start position:0% tries to provide an abstraction on on that<00:09:29.199> layer<00:09:29.470> and<00:09:29.769> you<00:09:30.029> can<00:09:31.029> see<00:09:31.180> here<00:09:31.420> an 00:09:31.530 --> 00:09:31.540 align:start position:0% that layer and you can see here an 00:09:31.540 --> 00:09:34.710 align:start position:0% that layer and you can see here an example<00:09:31.660> that<00:09:32.290> ok<00:09:32.889> put<00:09:33.160> in<00:09:33.670> party<00:09:34.029> s<00:09:34.149> messages 00:09:34.710 --> 00:09:34.720 align:start position:0% example that ok put in party s messages 00:09:34.720 --> 00:09:36.150 align:start position:0% example that ok put in party s messages send<00:09:34.990> message<00:09:35.379> you<00:09:35.529> send<00:09:35.740> that<00:09:35.889> on<00:09:35.980> a<00:09:36.009> certain 00:09:36.150 --> 00:09:36.160 align:start position:0% send message you send that on a certain 00:09:36.160 --> 00:09:38.699 align:start position:0% send message you send that on a certain channel<00:09:36.579> with<00:09:37.449> certain<00:09:37.779> data<00:09:37.990> and<00:09:38.319> then<00:09:38.500> you 00:09:38.699 --> 00:09:38.709 align:start position:0% channel with certain data and then you 00:09:38.709 --> 00:09:42.150 align:start position:0% channel with certain data and then you listen<00:09:39.189> or<00:09:39.990> you<00:09:40.990> listen<00:09:41.319> on<00:09:41.529> that<00:09:41.709> topic<00:09:41.889> so 00:09:42.150 --> 00:09:42.160 align:start position:0% listen or you listen on that topic so 00:09:42.160 --> 00:09:43.889 align:start position:0% listen or you listen on that topic so that<00:09:42.370> that's<00:09:43.029> useful<00:09:43.209> to<00:09:43.480> make<00:09:43.600> the<00:09:43.660> apps 00:09:43.889 --> 00:09:43.899 align:start position:0% that that's useful to make the apps 00:09:43.899 --> 00:09:46.619 align:start position:0% that that's useful to make the apps communicate<00:09:44.379> with<00:09:44.529> each<00:09:44.649> other<00:09:45.389> if<00:09:46.389> you're 00:09:46.619 --> 00:09:46.629 align:start position:0% communicate with each other if you're 00:09:46.629 --> 00:09:48.269 align:start position:0% communicate with each other if you're familiar<00:09:46.810> will<00:09:47.139> whisper<00:09:47.439> you<00:09:47.800> can<00:09:47.949> see<00:09:48.129> this 00:09:48.269 --> 00:09:48.279 align:start position:0% familiar will whisper you can see this 00:09:48.279 --> 00:09:50.309 align:start position:0% familiar will whisper you can see this is<00:09:48.430> actually<00:09:48.759> pretty<00:09:49.629> similar<00:09:50.019> to<00:09:50.050> the 00:09:50.309 --> 00:09:50.319 align:start position:0% is actually pretty similar to the 00:09:50.319 --> 00:09:56.850 align:start position:0% is actually pretty similar to the whisper<00:09:51.180> to<00:09:52.180> whisper<00:09:52.600> a<00:09:52.810> P<00:09:53.170> I<00:09:53.490> and<00:09:54.870> so<00:09:55.870> that<00:09:56.079> the 00:09:56.850 --> 00:09:56.860 align:start position:0% whisper to whisper a P I and so that the 00:09:56.860 --> 00:09:58.139 align:start position:0% whisper to whisper a P I and so that the reason<00:09:57.009> that<00:09:57.160> you<00:09:57.250> would<00:09:57.550> use<00:09:57.759> this<00:09:57.910> is 00:09:58.139 --> 00:09:58.149 align:start position:0% reason that you would use this is 00:09:58.149 --> 00:10:01.290 align:start position:0% reason that you would use this is because<00:09:59.069> that's<00:10:00.069> why<00:10:00.250> you<00:10:00.310> can<00:10:00.519> focus<00:10:00.850> on 00:10:01.290 --> 00:10:01.300 align:start position:0% because that's why you can focus on 00:10:01.300 --> 00:10:02.790 align:start position:0% because that's why you can focus on behavior<00:10:02.019> and<00:10:02.050> not<00:10:02.290> in<00:10:02.439> an<00:10:02.560> implementation 00:10:02.790 --> 00:10:02.800 align:start position:0% behavior and not in an implementation 00:10:02.800 --> 00:10:05.189 align:start position:0% behavior and not in an implementation details<00:10:03.569> especially<00:10:04.569> because<00:10:04.660> if<00:10:04.839> you<00:10:04.990> want 00:10:05.189 --> 00:10:05.199 align:start position:0% details especially because if you want 00:10:05.199 --> 00:10:06.869 align:start position:0% details especially because if you want to<00:10:05.259> try<00:10:05.620> out<00:10:05.769> with<00:10:05.920> different<00:10:06.310> technologies 00:10:06.869 --> 00:10:06.879 align:start position:0% to try out with different technologies 00:10:06.879 --> 00:10:08.999 align:start position:0% to try out with different technologies the<00:10:07.660> implementation<00:10:08.230> would<00:10:08.319> be<00:10:08.500> different 00:10:08.999 --> 00:10:09.009 align:start position:0% the implementation would be different 00:10:09.009 --> 00:10:12.480 align:start position:0% the implementation would be different and<00:10:09.449> and<00:10:10.449> this<00:10:10.600> way<00:10:10.870> you<00:10:10.930> you<00:10:11.829> just<00:10:12.040> worry 00:10:12.480 --> 00:10:12.490 align:start position:0% and and this way you you just worry 00:10:12.490 --> 00:10:13.829 align:start position:0% and and this way you you just worry about<00:10:12.550> the<00:10:12.880> behavior<00:10:13.360> you<00:10:13.449> don't<00:10:13.480> need<00:10:13.720> to 00:10:13.829 --> 00:10:13.839 align:start position:0% about the behavior you don't need to 00:10:13.839 --> 00:10:16.290 align:start position:0% about the behavior you don't need to worry<00:10:14.050> about<00:10:14.199> the<00:10:14.970> actual<00:10:15.970> details 00:10:16.290 --> 00:10:16.300 align:start position:0% worry about the actual details 00:10:16.300 --> 00:10:18.150 align:start position:0% worry about the actual details underneath<00:10:16.649> so<00:10:17.649> if<00:10:17.769> you<00:10:17.860> change<00:10:18.069> your 00:10:18.150 --> 00:10:18.160 align:start position:0% underneath so if you change your 00:10:18.160 --> 00:10:20.550 align:start position:0% underneath so if you change your technology<00:10:18.490> you<00:10:18.730> don't<00:10:18.850> need<00:10:19.029> to<00:10:19.180> change<00:10:19.560> you 00:10:20.550 --> 00:10:20.560 align:start position:0% technology you don't need to change you 00:10:20.560 --> 00:10:22.079 align:start position:0% technology you don't need to change you don't<00:10:20.709> need<00:10:20.800> to<00:10:20.920> change<00:10:21.100> your<00:10:21.279> code<00:10:21.430> all<00:10:21.910> over 00:10:22.079 --> 00:10:22.089 align:start position:0% don't need to change your code all over 00:10:22.089 --> 00:10:26.069 align:start position:0% don't need to change your code all over again<00:10:22.319> so<00:10:24.029> so<00:10:25.029> it<00:10:25.120> does<00:10:25.269> have<00:10:25.449> provided 00:10:26.069 --> 00:10:26.079 align:start position:0% again so so it does have provided 00:10:26.079 --> 00:10:29.009 align:start position:0% again so so it does have provided functionality<00:10:26.829> and<00:10:26.949> you<00:10:27.069> can<00:10:27.279> just<00:10:27.959> you<00:10:28.959> can 00:10:29.009 --> 00:10:29.019 align:start position:0% functionality and you can just you can 00:10:29.019 --> 00:10:31.259 align:start position:0% functionality and you can just you can just<00:10:29.170> choose<00:10:29.649> the<00:10:29.920> provider<00:10:30.310> that<00:10:30.579> you<00:10:30.850> you 00:10:31.259 --> 00:10:31.269 align:start position:0% just choose the provider that you you 00:10:31.269 --> 00:10:31.620 align:start position:0% just choose the provider that you you want 00:10:31.620 --> 00:10:31.630 align:start position:0% want 00:10:31.630 --> 00:10:34.860 align:start position:0% want so<00:10:32.230> a<00:10:32.529> sign<00:10:33.160> party<00:10:33.490> will<00:10:33.610> support<00:10:33.939> this<00:10:34.120> three 00:10:34.860 --> 00:10:34.870 align:start position:0% so a sign party will support this three 00:10:34.870 --> 00:10:38.160 align:start position:0% so a sign party will support this three providers<00:10:35.230> which<00:10:35.620> is<00:10:35.740> whisper<00:10:36.220> a<00:10:36.939> contract<00:10:37.899> a 00:10:38.160 --> 00:10:38.170 align:start position:0% providers which is whisper a contract a 00:10:38.170 --> 00:10:40.889 align:start position:0% providers which is whisper a contract a contract<00:10:38.410> for<00:10:39.160> the<00:10:39.399> messages<00:10:39.939> kind<00:10:40.779> of 00:10:40.889 --> 00:10:40.899 align:start position:0% contract for the messages kind of 00:10:40.899 --> 00:10:43.439 align:start position:0% contract for the messages kind of replicates<00:10:41.380> the<00:10:41.709> this<00:10:42.040> kind<00:10:42.279> of<00:10:42.449> channel 00:10:43.439 --> 00:10:43.449 align:start position:0% replicates the this kind of channel 00:10:43.449 --> 00:10:46.230 align:start position:0% replicates the this kind of channel function<00:10:44.290> functionality<00:10:45.160> and<00:10:45.790> also<00:10:45.939> will 00:10:46.230 --> 00:10:46.240 align:start position:0% function functionality and also will 00:10:46.240 --> 00:10:51.120 align:start position:0% function functionality and also will support<00:10:46.540> tell<00:10:47.170> ash<00:10:49.439> now<00:10:50.439> regarding<00:10:50.920> for 00:10:51.120 --> 00:10:51.130 align:start position:0% support tell ash now regarding for 00:10:51.130 --> 00:10:53.189 align:start position:0% support tell ash now regarding for storage<00:10:51.519> it<00:10:51.699> does<00:10:51.850> a<00:10:51.880> similar<00:10:52.300> type<00:10:53.170> of 00:10:53.189 --> 00:10:53.199 align:start position:0% storage it does a similar type of 00:10:53.199 --> 00:10:56.189 align:start position:0% storage it does a similar type of abstraction<00:10:54.009> so<00:10:54.850> you<00:10:55.269> can't<00:10:55.480> just<00:10:55.720> say<00:10:55.839> okay<00:10:56.170> I 00:10:56.189 --> 00:10:56.199 align:start position:0% abstraction so you can't just say okay I 00:10:56.199 --> 00:10:59.220 align:start position:0% abstraction so you can't just say okay I want<00:10:56.350> to<00:10:56.470> save<00:10:56.709> text<00:10:57.309> and<00:10:57.490> then<00:10:57.610> I<00:10:57.699> got<00:10:58.230> a 00:10:59.220 --> 00:10:59.230 align:start position:0% want to save text and then I got a 00:10:59.230 --> 00:11:01.379 align:start position:0% want to save text and then I got a particular<00:11:00.100> in<00:11:00.189> that<00:11:00.220> fire<00:11:00.610> it's<00:11:00.939> usually<00:11:01.149> a 00:11:01.379 --> 00:11:01.389 align:start position:0% particular in that fire it's usually a 00:11:01.389 --> 00:11:05.340 align:start position:0% particular in that fire it's usually a national<00:11:02.230> a<00:11:03.069> PF<00:11:03.910> fast<00:11:04.120> for<00:11:04.300> example<00:11:04.660> and<00:11:05.019> then 00:11:05.340 --> 00:11:05.350 align:start position:0% national a PF fast for example and then 00:11:05.350 --> 00:11:08.009 align:start position:0% national a PF fast for example and then when<00:11:05.860> he<00:11:05.949> passes<00:11:06.610> that<00:11:06.730> she<00:11:07.059> will<00:11:07.209> get<00:11:07.420> back 00:11:08.009 --> 00:11:08.019 align:start position:0% when he passes that she will get back 00:11:08.019 --> 00:11:13.350 align:start position:0% when he passes that she will get back the<00:11:08.399> data<00:11:09.399> that<00:11:09.639> you<00:11:09.879> requested<00:11:10.660> and<00:11:11.759> it<00:11:12.759> also 00:11:13.350 --> 00:11:13.360 align:start position:0% the data that you requested and it also 00:11:13.360 --> 00:11:16.650 align:start position:0% the data that you requested and it also obstructs<00:11:14.199> the<00:11:14.459> functionality<00:11:15.459> to<00:11:15.759> upload 00:11:16.650 --> 00:11:16.660 align:start position:0% obstructs the functionality to upload 00:11:16.660 --> 00:11:17.980 align:start position:0% obstructs the functionality to upload files 00:11:17.980 --> 00:11:17.990 align:start position:0% files 00:11:17.990 --> 00:11:20.500 align:start position:0% files so<00:11:18.440> presented<00:11:19.190> this<00:11:19.279> in<00:11:19.580> this<00:11:19.730> example<00:11:20.060> if<00:11:20.390> you 00:11:20.500 --> 00:11:20.510 align:start position:0% so presented this in this example if you 00:11:20.510 --> 00:11:23.710 align:start position:0% so presented this in this example if you have<00:11:20.600> a<00:11:20.680> this<00:11:21.680> HTML<00:11:22.220> input<00:11:22.640> you<00:11:23.120> can<00:11:23.270> just<00:11:23.480> pass 00:11:23.710 --> 00:11:23.720 align:start position:0% have a this HTML input you can just pass 00:11:23.720 --> 00:11:26.110 align:start position:0% have a this HTML input you can just pass it<00:11:23.900> the<00:11:23.990> Dom<00:11:24.170> element<00:11:24.380> and<00:11:24.950> it<00:11:25.580> will<00:11:25.700> just<00:11:25.910> take 00:11:26.110 --> 00:11:26.120 align:start position:0% it the Dom element and it will just take 00:11:26.120 --> 00:11:28.329 align:start position:0% it the Dom element and it will just take care<00:11:26.300> of<00:11:26.450> taking<00:11:26.839> the<00:11:27.020> file<00:11:27.290> doing<00:11:28.160> whatever 00:11:28.329 --> 00:11:28.339 align:start position:0% care of taking the file doing whatever 00:11:28.339 --> 00:11:30.490 align:start position:0% care of taking the file doing whatever it<00:11:28.550> needs<00:11:28.760> and<00:11:29.240> it<00:11:29.630> will<00:11:29.810> upload<00:11:30.080> the<00:11:30.290> file 00:11:30.490 --> 00:11:30.500 align:start position:0% it needs and it will upload the file 00:11:30.500 --> 00:11:32.200 align:start position:0% it needs and it will upload the file it's<00:11:31.070> pretty<00:11:31.310> useful<00:11:31.460> because<00:11:31.820> different 00:11:32.200 --> 00:11:32.210 align:start position:0% it's pretty useful because different 00:11:32.210 --> 00:11:33.880 align:start position:0% it's pretty useful because different technologies<00:11:32.930> actually<00:11:33.110> have<00:11:33.380> slightly 00:11:33.880 --> 00:11:33.890 align:start position:0% technologies actually have slightly 00:11:33.890 --> 00:11:35.680 align:start position:0% technologies actually have slightly different<00:11:34.100> ways<00:11:34.550> they<00:11:34.940> actually<00:11:35.360> deal<00:11:35.660> with 00:11:35.680 --> 00:11:35.690 align:start position:0% different ways they actually deal with 00:11:35.690 --> 00:11:39.970 align:start position:0% different ways they actually deal with the<00:11:36.080> files<00:11:36.320> and<00:11:36.589> and<00:11:36.800> and<00:11:37.070> upload<00:11:37.850> them<00:11:38.200> so<00:11:39.200> if 00:11:39.970 --> 00:11:39.980 align:start position:0% the files and and and upload them so if 00:11:39.980 --> 00:11:41.380 align:start position:0% the files and and and upload them so if you<00:11:40.220> just<00:11:40.460> use<00:11:40.550> this<00:11:40.790> you<00:11:40.940> don't<00:11:41.060> need<00:11:41.240> to 00:11:41.380 --> 00:11:41.390 align:start position:0% you just use this you don't need to 00:11:41.390 --> 00:11:43.090 align:start position:0% you just use this you don't need to worry<00:11:41.540> about<00:11:41.600> all<00:11:41.960> those<00:11:42.110> details<00:11:42.320> and<00:11:42.950> then 00:11:43.090 --> 00:11:43.100 align:start position:0% worry about all those details and then 00:11:43.100 --> 00:11:45.490 align:start position:0% worry about all those details and then again<00:11:43.310> again<00:11:43.760> you<00:11:43.850> can<00:11:44.000> just<00:11:44.180> do<00:11:44.360> get<00:11:44.690> URL<00:11:44.960> ash 00:11:45.490 --> 00:11:45.500 align:start position:0% again again you can just do get URL ash 00:11:45.500 --> 00:11:49.690 align:start position:0% again again you can just do get URL ash and<00:11:45.890> you<00:11:46.370> got<00:11:46.520> your<00:11:47.180> your<00:11:48.110> a<00:11:48.500> lot<00:11:48.740> of<00:11:48.950> the<00:11:49.310> that 00:11:49.690 --> 00:11:49.700 align:start position:0% and you got your your a lot of the that 00:11:49.700 --> 00:11:52.019 align:start position:0% and you got your your a lot of the that will<00:11:49.880> point<00:11:50.089> to<00:11:50.300> the<00:11:50.750> content<00:11:51.110> of<00:11:51.230> that<00:11:51.260> file 00:11:52.019 --> 00:11:52.029 align:start position:0% will point to the content of that file 00:11:52.029 --> 00:11:55.660 align:start position:0% will point to the content of that file so<00:11:53.029> this<00:11:53.330> is<00:11:53.450> this<00:11:53.990> pretty<00:11:54.260> useful<00:11:54.560> for<00:11:54.740> you 00:11:55.660 --> 00:11:55.670 align:start position:0% so this is this pretty useful for you 00:11:55.670 --> 00:11:58.120 align:start position:0% so this is this pretty useful for you know<00:11:55.790> human<00:11:56.260> upload<00:11:57.260> cat<00:11:57.470> pictures<00:11:57.860> or 00:11:58.120 --> 00:11:58.130 align:start position:0% know human upload cat pictures or 00:11:58.130 --> 00:12:02.200 align:start position:0% know human upload cat pictures or profile<00:11:58.820> pics<00:11:59.060> or<00:11:59.330> so<00:11:59.540> on<00:12:00.100> and<00:12:01.100> just<00:12:02.060> like 00:12:02.200 --> 00:12:02.210 align:start position:0% profile pics or so on and just like 00:12:02.210 --> 00:12:03.700 align:start position:0% profile pics or so on and just like before<00:12:02.390> you<00:12:02.600> can<00:12:02.690> also<00:12:02.960> choose<00:12:03.350> a<00:12:03.410> provider 00:12:03.700 --> 00:12:03.710 align:start position:0% before you can also choose a provider 00:12:03.710 --> 00:12:07.269 align:start position:0% before you can also choose a provider you<00:12:04.100> can<00:12:04.279> choose<00:12:04.580> a<00:12:04.610> configuration<00:12:06.279> default 00:12:07.269 --> 00:12:07.279 align:start position:0% you can choose a configuration default 00:12:07.279 --> 00:12:10.630 align:start position:0% you can choose a configuration default for<00:12:07.970> now<00:12:08.180> will<00:12:08.480> be<00:12:08.660> ipfs<00:12:09.520> mostly<00:12:10.520> because 00:12:10.630 --> 00:12:10.640 align:start position:0% for now will be ipfs mostly because 00:12:10.640 --> 00:12:12.930 align:start position:0% for now will be ipfs mostly because that's<00:12:10.910> what<00:12:11.120> I<00:12:11.150> was<00:12:11.330> actually<00:12:11.480> working<00:12:12.350> on 00:12:12.930 --> 00:12:12.940 align:start position:0% that's what I was actually working on 00:12:12.940 --> 00:12:17.350 align:start position:0% that's what I was actually working on but<00:12:13.940> the<00:12:14.630> default<00:12:14.900> will<00:12:15.230> there<00:12:15.440> be<00:12:15.680> swarm<00:12:16.610> and 00:12:17.350 --> 00:12:17.360 align:start position:0% but the default will there be swarm and 00:12:17.360 --> 00:12:21.790 align:start position:0% but the default will there be swarm and so<00:12:18.260> there's<00:12:18.770> actually<00:12:19.010> five<00:12:20.800> providers 00:12:21.790 --> 00:12:21.800 align:start position:0% so there's actually five providers 00:12:21.800 --> 00:12:24.790 align:start position:0% so there's actually five providers supported<00:12:22.459> the<00:12:23.060> first<00:12:23.270> three<00:12:23.570> are<00:12:23.750> a<00:12:24.110> swarm<00:12:24.500> RP 00:12:24.790 --> 00:12:24.800 align:start position:0% supported the first three are a swarm RP 00:12:24.800 --> 00:12:27.850 align:start position:0% supported the first three are a swarm RP FS<00:12:25.040> and<00:12:25.250> and<00:12:25.670> a<00:12:26.029> storage<00:12:26.390> contract<00:12:26.930> and<00:12:27.350> again 00:12:27.850 --> 00:12:27.860 align:start position:0% FS and and a storage contract and again 00:12:27.860 --> 00:12:30.820 align:start position:0% FS and and a storage contract and again there's<00:12:28.040> different<00:12:28.100> trade-offs<00:12:28.790> to<00:12:29.000> this<00:12:29.830> you 00:12:30.820 --> 00:12:30.830 align:start position:0% there's different trade-offs to this you 00:12:30.830 --> 00:12:32.110 align:start position:0% there's different trade-offs to this you might<00:12:31.070> actually<00:12:31.310> want<00:12:31.670> to<00:12:31.850> store<00:12:32.089> something 00:12:32.110 --> 00:12:32.120 align:start position:0% might actually want to store something 00:12:32.120 --> 00:12:34.780 align:start position:0% might actually want to store something on<00:12:32.779> the<00:12:32.990> blockchain<00:12:33.200> which<00:12:33.709> in<00:12:34.520> this<00:12:34.610> case 00:12:34.780 --> 00:12:34.790 align:start position:0% on the blockchain which in this case 00:12:34.790 --> 00:12:37.090 align:start position:0% on the blockchain which in this case we'll<00:12:35.029> use<00:12:35.240> a<00:12:35.300> pre<00:12:35.600> deployed<00:12:35.900> contract<00:12:36.500> to<00:12:36.980> do 00:12:37.090 --> 00:12:37.100 align:start position:0% we'll use a pre deployed contract to do 00:12:37.100 --> 00:12:39.670 align:start position:0% we'll use a pre deployed contract to do that<00:12:37.279> it's<00:12:37.820> very<00:12:38.060> expensive<00:12:38.630> but<00:12:38.930> dark<00:12:39.260> use 00:12:39.670 --> 00:12:39.680 align:start position:0% that it's very expensive but dark use 00:12:39.680 --> 00:12:43.120 align:start position:0% that it's very expensive but dark use cases<00:12:39.950> that<00:12:40.220> might<00:12:40.520> actually<00:12:40.760> be<00:12:41.180> be<00:12:42.050> worth<00:12:42.260> it 00:12:43.120 --> 00:12:43.130 align:start position:0% cases that might actually be be worth it 00:12:43.130 --> 00:12:46.180 align:start position:0% cases that might actually be be worth it there<00:12:43.550> also<00:12:43.670> be<00:12:43.970> supported<00:12:44.810> for<00:12:45.470> made<00:12:45.920> safe 00:12:46.180 --> 00:12:46.190 align:start position:0% there also be supported for made safe 00:12:46.190 --> 00:12:54.760 align:start position:0% there also be supported for made safe and<00:12:46.600> store<00:12:47.600> G<00:12:52.240> so<00:12:53.240> regarding<00:12:54.080> not<00:12:54.230> that 00:12:54.760 --> 00:12:54.770 align:start position:0% and store G so regarding not that 00:12:54.770 --> 00:12:57.310 align:start position:0% and store G so regarding not that distribution<00:12:55.360> so<00:12:56.360> in<00:12:56.750> part<00:12:56.959> right<00:12:57.260> now 00:12:57.310 --> 00:12:57.320 align:start position:0% distribution so in part right now 00:12:57.320 --> 00:12:59.460 align:start position:0% distribution so in part right now there's<00:12:57.620> two<00:12:57.950> ways<00:12:57.980> you<00:12:58.339> can<00:12:58.459> distribute<00:12:59.000> your 00:12:59.460 --> 00:12:59.470 align:start position:0% there's two ways you can distribute your 00:12:59.470 --> 00:13:02.980 align:start position:0% there's two ways you can distribute your your<00:13:00.470> DAP<00:13:00.800> would<00:13:01.100> embark<00:13:01.430> one<00:13:02.240> is<00:13:02.420> that<00:13:02.600> you<00:13:02.810> do 00:13:02.980 --> 00:13:02.990 align:start position:0% your DAP would embark one is that you do 00:13:02.990 --> 00:13:06.610 align:start position:0% your DAP would embark one is that you do impart<00:13:03.440> build<00:13:03.740> and<00:13:04.150> it<00:13:05.150> will<00:13:05.450> create<00:13:05.690> a 00:13:06.610 --> 00:13:06.620 align:start position:0% impart build and it will create a 00:13:06.620 --> 00:13:09.730 align:start position:0% impart build and it will create a directory<00:13:07.430> that<00:13:07.640> as<00:13:07.820> your<00:13:08.660> old<00:13:09.170> your<00:13:09.320> DAP<00:13:09.529> all 00:13:09.730 --> 00:13:09.740 align:start position:0% directory that as your old your DAP all 00:13:09.740 --> 00:13:12.010 align:start position:0% directory that as your old your DAP all the<00:13:09.890> needed<00:13:10.310> files<00:13:10.490> and<00:13:10.790> it<00:13:10.850> can<00:13:11.000> just<00:13:11.150> copy 00:13:12.010 --> 00:13:12.020 align:start position:0% the needed files and it can just copy 00:13:12.020 --> 00:13:13.600 align:start position:0% the needed files and it can just copy paste<00:13:12.140> it<00:13:12.440> and<00:13:12.560> put<00:13:12.620> it<00:13:12.800> on<00:13:12.920> your<00:13:13.100> web<00:13:13.339> server 00:13:13.600 --> 00:13:13.610 align:start position:0% paste it and put it on your web server 00:13:13.610 --> 00:13:18.220 align:start position:0% paste it and put it on your web server for<00:13:13.880> instance<00:13:14.270> or<00:13:14.630> you<00:13:15.200> can<00:13:15.380> also<00:13:15.529> do<00:13:17.230> embark 00:13:18.220 --> 00:13:18.230 align:start position:0% for instance or you can also do embark 00:13:18.230 --> 00:13:21.790 align:start position:0% for instance or you can also do embark deploy<00:13:18.650> ipfs<00:13:19.520> and<00:13:20.050> and<00:13:21.050> this<00:13:21.200> command<00:13:21.560> what<00:13:21.709> it 00:13:21.790 --> 00:13:21.800 align:start position:0% deploy ipfs and and this command what it 00:13:21.800 --> 00:13:23.590 align:start position:0% deploy ipfs and and this command what it does<00:13:21.920> is<00:13:22.070> that<00:13:22.100> the<00:13:22.339> it<00:13:22.520> deploys<00:13:22.850> or<00:13:23.029> contracts 00:13:23.590 --> 00:13:23.600 align:start position:0% does is that the it deploys or contracts 00:13:23.600 --> 00:13:25.900 align:start position:0% does is that the it deploys or contracts if<00:13:23.720> they<00:13:23.959> are<00:13:24.020> not<00:13:24.200> already<00:13:24.380> deployed<00:13:24.910> build 00:13:25.900 --> 00:13:25.910 align:start position:0% if they are not already deployed build 00:13:25.910 --> 00:13:28.750 align:start position:0% if they are not already deployed build your<00:13:26.089> app<00:13:26.300> and<00:13:26.920> uploads<00:13:27.920> it<00:13:28.100> uploads<00:13:28.610> your 00:13:28.750 --> 00:13:28.760 align:start position:0% your app and uploads it uploads your 00:13:28.760 --> 00:13:30.790 align:start position:0% your app and uploads it uploads your your<00:13:29.270> def<00:13:29.570> for<00:13:29.870> to<00:13:30.110> IPF 00:13:30.790 --> 00:13:30.800 align:start position:0% your def for to IPF 00:13:30.800 --> 00:13:33.519 align:start position:0% your def for to IPF and<00:13:31.100> then<00:13:31.670> it<00:13:32.060> shows<00:13:32.510> you<00:13:32.570> okay<00:13:32.959> it<00:13:33.170> will<00:13:33.320> be 00:13:33.519 --> 00:13:33.529 align:start position:0% and then it shows you okay it will be 00:13:33.529 --> 00:13:37.210 align:start position:0% and then it shows you okay it will be available<00:13:34.010> and<00:13:34.279> this<00:13:34.640> URL<00:13:34.970> or<00:13:35.390> this<00:13:36.170> URL<00:13:36.470> in 00:13:37.210 --> 00:13:37.220 align:start position:0% available and this URL or this URL in 00:13:37.220 --> 00:13:41.079 align:start position:0% available and this URL or this URL in that<00:13:37.399> case<00:13:37.610> it's<00:13:38.149> a<00:13:38.240> gateway<00:13:39.310> so<00:13:40.310> that's<00:13:40.940> why<00:13:41.060> I 00:13:41.079 --> 00:13:41.089 align:start position:0% that case it's a gateway so that's why I 00:13:41.089 --> 00:13:42.850 align:start position:0% that case it's a gateway so that's why I was<00:13:41.209> supporting<00:13:41.690> a<00:13:41.750> part<00:13:41.959> one<00:13:42.200> and<00:13:42.410> in<00:13:42.620> part 00:13:42.850 --> 00:13:42.860 align:start position:0% was supporting a part one and in part 00:13:42.860 --> 00:13:46.150 align:start position:0% was supporting a part one and in part two<00:13:42.890> will<00:13:43.160> support<00:13:44.019> swarmer<00:13:45.019> PFS<00:13:45.470> made<00:13:45.860> safe 00:13:46.150 --> 00:13:46.160 align:start position:0% two will support swarmer PFS made safe 00:13:46.160 --> 00:13:47.440 align:start position:0% two will support swarmer PFS made safe and<00:13:46.490> store 00:13:47.440 --> 00:13:47.450 align:start position:0% and store 00:13:47.450 --> 00:13:51.400 align:start position:0% and store Sergi<00:13:47.870> as<00:13:48.910> the<00:13:49.910> centralized<00:13:50.300> storage<00:13:50.510> for<00:13:50.899> for 00:13:51.400 --> 00:13:51.410 align:start position:0% Sergi as the centralized storage for for 00:13:51.410 --> 00:13:56.800 align:start position:0% Sergi as the centralized storage for for distribution<00:13:52.990> so<00:13:53.990> finally<00:13:55.360> the<00:13:56.360> other<00:13:56.510> way 00:13:56.800 --> 00:13:56.810 align:start position:0% distribution so finally the other way 00:13:56.810 --> 00:13:59.199 align:start position:0% distribution so finally the other way that<00:13:57.019> I'm<00:13:57.350> park<00:13:57.560> also<00:13:57.709> true<00:13:57.980> this<00:13:58.339> was<00:13:58.880> also 00:13:59.199 --> 00:13:59.209 align:start position:0% that I'm park also true this was also 00:13:59.209 --> 00:14:01.480 align:start position:0% that I'm park also true this was also support<00:13:59.720> that<00:14:00.380> distribution<00:14:00.769> will<00:14:01.190> be<00:14:01.339> as<00:14:01.459> a 00:14:01.480 --> 00:14:01.490 align:start position:0% support that distribution will be as a 00:14:01.490 --> 00:14:04.240 align:start position:0% support that distribution will be as a desktop<00:14:02.180> app<00:14:02.480> so<00:14:03.290> it<00:14:03.529> will<00:14:03.709> have<00:14:03.829> a<00:14:03.860> command 00:14:04.240 --> 00:14:04.250 align:start position:0% desktop app so it will have a command 00:14:04.250 --> 00:14:06.759 align:start position:0% desktop app so it will have a command that<00:14:04.339> will<00:14:04.670> automatically<00:14:05.570> create<00:14:06.350> a<00:14:06.500> full 00:14:06.759 --> 00:14:06.769 align:start position:0% that will automatically create a full 00:14:06.769 --> 00:14:10.900 align:start position:0% that will automatically create a full desktop<00:14:06.980> app<00:14:07.459> with<00:14:08.329> the<00:14:08.480> DAP<00:14:08.829> for<00:14:09.910> Windows 00:14:10.900 --> 00:14:10.910 align:start position:0% desktop app with the DAP for Windows 00:14:10.910 --> 00:14:15.130 align:start position:0% desktop app with the DAP for Windows Linux<00:14:11.089> and<00:14:11.540> and<00:14:12.440> Mac<00:14:13.240> it<00:14:14.240> will<00:14:14.450> also<00:14:14.870> include 00:14:15.130 --> 00:14:15.140 align:start position:0% Linux and and Mac it will also include 00:14:15.140 --> 00:14:16.960 align:start position:0% Linux and and Mac it will also include the<00:14:15.290> binaries<00:14:16.160> that<00:14:16.339> are<00:14:16.459> necessary 00:14:16.960 --> 00:14:16.970 align:start position:0% the binaries that are necessary 00:14:16.970 --> 00:14:19.120 align:start position:0% the binaries that are necessary depending<00:14:17.209> on<00:14:17.600> the<00:14:17.779> configuration<00:14:17.959> that<00:14:18.410> you 00:14:19.120 --> 00:14:19.130 align:start position:0% depending on the configuration that you 00:14:19.130 --> 00:14:21.639 align:start position:0% depending on the configuration that you choose<00:14:19.430> so<00:14:20.209> in<00:14:20.420> this<00:14:20.570> case<00:14:20.810> if<00:14:21.050> you<00:14:21.290> distribute 00:14:21.639 --> 00:14:21.649 align:start position:0% choose so in this case if you distribute 00:14:21.649 --> 00:14:24.639 align:start position:0% choose so in this case if you distribute app<00:14:21.950> this<00:14:22.220> way<00:14:22.430> and<00:14:22.730> your<00:14:23.360> app<00:14:23.510> uses<00:14:23.870> a<00:14:24.019> ipfs 00:14:24.639 --> 00:14:24.649 align:start position:0% app this way and your app uses a ipfs 00:14:24.649 --> 00:14:27.550 align:start position:0% app this way and your app uses a ipfs you<00:14:24.920> don't<00:14:25.100> need<00:14:25.190> to<00:14:25.310> worry<00:14:25.550> if<00:14:26.149> your<00:14:26.560> customer 00:14:27.550 --> 00:14:27.560 align:start position:0% you don't need to worry if your customer 00:14:27.560 --> 00:14:29.920 align:start position:0% you don't need to worry if your customer or<00:14:27.620> user<00:14:27.769> as<00:14:28.160> a<00:14:28.190> PF<00:14:28.550> yes<00:14:28.760> because<00:14:29.000> if<00:14:29.750> it 00:14:29.920 --> 00:14:29.930 align:start position:0% or user as a PF yes because if it 00:14:29.930 --> 00:14:32.319 align:start position:0% or user as a PF yes because if it doesn't<00:14:30.110> end<00:14:30.470> then<00:14:31.459> the<00:14:31.610> app<00:14:31.760> will<00:14:32.000> use<00:14:32.209> the 00:14:32.319 --> 00:14:32.329 align:start position:0% doesn't end then the app will use the 00:14:32.329 --> 00:14:36.480 align:start position:0% doesn't end then the app will use the binary<00:14:32.540> that<00:14:32.870> it<00:14:33.079> comes<00:14:33.320> included<00:14:33.560> with<00:14:33.890> it 00:14:36.480 --> 00:14:36.490 align:start position:0% 00:14:36.490 --> 00:14:39.310 align:start position:0% all<00:14:37.490> right<00:14:37.550> then<00:14:37.850> and<00:14:38.180> that's<00:14:38.810> it<00:14:38.959> more 00:14:39.310 --> 00:14:39.320 align:start position:0% all right then and that's it more 00:14:39.320 --> 00:14:41.920 align:start position:0% all right then and that's it more information<00:14:39.740> you<00:14:39.800> can<00:14:39.950> find<00:14:40.160> it<00:14:40.370> in<00:14:40.579> in<00:14:41.180> github 00:14:41.920 --> 00:14:41.930 align:start position:0% information you can find it in in github 00:14:41.930 --> 00:14:45.630 align:start position:0% information you can find it in in github if<00:14:42.740> you<00:14:43.010> if<00:14:43.579> if<00:14:44.270> are<00:14:44.480> passionate<00:14:44.899> about<00:14:44.990> that 00:14:45.630 --> 00:14:45.640 align:start position:0% if you if if are passionate about that 00:14:45.640 --> 00:14:48.460 align:start position:0% if you if if are passionate about that development<00:14:46.640> please<00:14:47.120> join<00:14:47.329> us<00:14:47.360> at<00:14:47.630> that's<00:14:48.290> our 00:14:48.460 --> 00:14:48.470 align:start position:0% development please join us at that's our 00:14:48.470 --> 00:14:51.340 align:start position:0% development please join us at that's our gita<00:14:49.010> channel<00:14:49.430> I<00:14:49.660> thank<00:14:50.660> you<00:14:50.720> very<00:14:50.750> much<00:14:51.140> for 00:14:51.340 --> 00:14:51.350 align:start position:0% gita channel I thank you very much for 00:14:51.350 --> 00:14:56.320 align:start position:0% gita channel I thank you very much for your<00:14:51.470> time<00:14:51.620> thank<00:14:53.320> you