WEBVTT Kind: captions Language: en 00:00:00.060 --> 00:00:02.960 align:start position:0% hello<00:00:00.780> I'm<00:00:01.079> a<00:00:01.110> Murie<00:00:02.010> I'm<00:00:02.129> the<00:00:02.280> lead<00:00:02.460> developer 00:00:02.960 --> 00:00:02.970 align:start position:0% hello I'm a Murie I'm the lead developer 00:00:02.970 --> 00:00:05.410 align:start position:0% hello I'm a Murie I'm the lead developer of<00:00:03.000> the<00:00:03.270> BART<00:00:03.510> framework<00:00:04.290> bye<00:00:04.470> bye<00:00:04.830> status 00:00:05.410 --> 00:00:05.420 align:start position:0% of the BART framework bye bye status 00:00:05.420 --> 00:00:07.670 align:start position:0% of the BART framework bye bye status we're<00:00:06.420> trying<00:00:06.750> to<00:00:06.870> do<00:00:06.990> a<00:00:07.020> framework<00:00:07.379> that 00:00:07.670 --> 00:00:07.680 align:start position:0% we're trying to do a framework that 00:00:07.680 --> 00:00:09.830 align:start position:0% we're trying to do a framework that makes<00:00:07.740> it<00:00:08.099> as<00:00:08.309> easy<00:00:08.700> as<00:00:08.820> possible<00:00:08.970> to<00:00:09.450> develop 00:00:09.830 --> 00:00:09.840 align:start position:0% makes it as easy as possible to develop 00:00:09.840 --> 00:00:12.980 align:start position:0% makes it as easy as possible to develop disatrous<00:00:10.559> applications<00:00:11.330> and<00:00:12.330> I<00:00:12.450> do<00:00:12.509> mean<00:00:12.780> the 00:00:12.980 --> 00:00:12.990 align:start position:0% disatrous applications and I do mean the 00:00:12.990 --> 00:00:15.020 align:start position:0% disatrous applications and I do mean the central<00:00:13.320> application<00:00:13.500> in<00:00:14.309> a<00:00:14.460> true<00:00:14.639> sense<00:00:14.910> of 00:00:15.020 --> 00:00:15.030 align:start position:0% central application in a true sense of 00:00:15.030 --> 00:00:17.720 align:start position:0% central application in a true sense of the<00:00:15.089> word<00:00:15.179> so<00:00:15.619> the<00:00:16.619> apps<00:00:16.740> that<00:00:16.890> really<00:00:17.220> use<00:00:17.520> the 00:00:17.720 --> 00:00:17.730 align:start position:0% the word so the apps that really use the 00:00:17.730 --> 00:00:20.210 align:start position:0% the word so the apps that really use the entire<00:00:18.590> decentralized<00:00:19.590> stack<00:00:19.859> that<00:00:20.039> is 00:00:20.210 --> 00:00:20.220 align:start position:0% entire decentralized stack that is 00:00:20.220 --> 00:00:25.160 align:start position:0% entire decentralized stack that is currently<00:00:20.640> available<00:00:21.270> and<00:00:23.330> I'm<00:00:24.330> we're<00:00:24.960> really 00:00:25.160 --> 00:00:25.170 align:start position:0% currently available and I'm we're really 00:00:25.170 --> 00:00:27.349 align:start position:0% currently available and I'm we're really excited<00:00:25.439> to<00:00:25.830> to<00:00:26.340> talk<00:00:26.519> today<00:00:26.670> about<00:00:26.789> in<00:00:27.150> part 00:00:27.349 --> 00:00:27.359 align:start position:0% excited to to talk today about in part 00:00:27.359 --> 00:00:29.570 align:start position:0% excited to to talk today about in part four<00:00:27.599> and<00:00:28.410> we<00:00:28.650> also<00:00:28.800> have<00:00:28.980> a<00:00:29.010> few<00:00:29.279> other 00:00:29.570 --> 00:00:29.580 align:start position:0% four and we also have a few other 00:00:29.580 --> 00:00:33.170 align:start position:0% four and we also have a few other surprises<00:00:30.470> first<00:00:31.470> though<00:00:32.219> we'll<00:00:32.550> just<00:00:33.090> do<00:00:33.149> a 00:00:33.170 --> 00:00:33.180 align:start position:0% surprises first though we'll just do a 00:00:33.180 --> 00:00:35.780 align:start position:0% surprises first though we'll just do a quick<00:00:33.390> detour<00:00:33.660> for<00:00:34.590> embark<00:00:35.070> three<00:00:35.340> and<00:00:35.610> what 00:00:35.780 --> 00:00:35.790 align:start position:0% quick detour for embark three and what 00:00:35.790 --> 00:00:38.209 align:start position:0% quick detour for embark three and what happened<00:00:36.149> this<00:00:36.540> year<00:00:36.739> for<00:00:37.739> those<00:00:37.860> of<00:00:37.980> you<00:00:38.070> that 00:00:38.209 --> 00:00:38.219 align:start position:0% happened this year for those of you that 00:00:38.219 --> 00:00:40.459 align:start position:0% happened this year for those of you that might<00:00:38.940> not<00:00:39.000> be<00:00:39.270> familiar<00:00:39.390> yet<00:00:39.750> would<00:00:40.020> win<00:00:40.440> a 00:00:40.459 --> 00:00:40.469 align:start position:0% might not be familiar yet would win a 00:00:40.469 --> 00:00:43.610 align:start position:0% might not be familiar yet would win a mark<00:00:40.770> so<00:00:41.460> this<00:00:41.969> year<00:00:42.239> back<00:00:42.450> in<00:00:42.660> May 00:00:43.610 --> 00:00:43.620 align:start position:0% mark so this year back in May 00:00:43.620 --> 00:00:46.220 align:start position:0% mark so this year back in May status<00:00:44.280> announced<00:00:44.850> that<00:00:45.120> it<00:00:45.450> was<00:00:45.600> supporting 00:00:46.220 --> 00:00:46.230 align:start position:0% status announced that it was supporting 00:00:46.230 --> 00:00:49.130 align:start position:0% status announced that it was supporting embark<00:00:46.710> and<00:00:47.579> the<00:00:47.910> team<00:00:48.090> has<00:00:48.239> grown<00:00:48.750> a<00:00:48.809> lot<00:00:48.960> to 00:00:49.130 --> 00:00:49.140 align:start position:0% embark and the team has grown a lot to 00:00:49.140 --> 00:00:52.100 align:start position:0% embark and the team has grown a lot to learn<00:00:49.230> Alex<00:00:49.590> seven<00:00:50.340> seven<00:00:51.120> members<00:00:51.539> full-time 00:00:52.100 --> 00:00:52.110 align:start position:0% learn Alex seven seven members full-time 00:00:52.110 --> 00:00:57.139 align:start position:0% learn Alex seven seven members full-time working<00:00:52.350> on<00:00:53.100> this<00:00:53.280> and<00:00:55.340> so<00:00:56.340> first<00:00:56.910> of<00:00:57.030> all 00:00:57.139 --> 00:00:57.149 align:start position:0% working on this and so first of all 00:00:57.149 --> 00:00:59.299 align:start position:0% working on this and so first of all embark<00:00:57.750> goes<00:00:57.930> far<00:00:58.199> beyond<00:00:58.469> just<00:00:58.710> the<00:00:59.039> smart 00:00:59.299 --> 00:00:59.309 align:start position:0% embark goes far beyond just the smart 00:00:59.309 --> 00:01:02.270 align:start position:0% embark goes far beyond just the smart contracts<00:00:59.789> it<00:01:00.780> does<00:01:00.989> support<00:01:01.140> sylheti<00:01:01.890> and 00:01:02.270 --> 00:01:02.280 align:start position:0% contracts it does support sylheti and 00:01:02.280 --> 00:01:04.579 align:start position:0% contracts it does support sylheti and other<00:01:02.760> language<00:01:03.120> like<00:01:03.149> VIPRE<00:01:03.870> and<00:01:04.080> bamboo<00:01:04.379> out 00:01:04.579 --> 00:01:04.589 align:start position:0% other language like VIPRE and bamboo out 00:01:04.589 --> 00:01:06.440 align:start position:0% other language like VIPRE and bamboo out of<00:01:04.739> the<00:01:04.860> box<00:01:05.070> and<00:01:05.640> you<00:01:05.729> can<00:01:05.760> even<00:01:06.030> use<00:01:06.299> them 00:01:06.440 --> 00:01:06.450 align:start position:0% of the box and you can even use them 00:01:06.450 --> 00:01:10.520 align:start position:0% of the box and you can even use them together<00:01:06.630> if<00:01:07.049> if<00:01:07.799> you<00:01:08.250> want<00:01:08.430> to<00:01:08.750> but<00:01:09.750> it<00:01:09.900> also 00:01:10.520 --> 00:01:10.530 align:start position:0% together if if you want to but it also 00:01:10.530 --> 00:01:14.120 align:start position:0% together if if you want to but it also supports<00:01:10.830> swarm<00:01:11.670> ipfs<00:01:12.299> whisper<00:01:12.900> and<00:01:13.170> and 00:01:14.120 --> 00:01:14.130 align:start position:0% supports swarm ipfs whisper and and 00:01:14.130 --> 00:01:17.719 align:start position:0% supports swarm ipfs whisper and and recently<00:01:14.580> ENS<00:01:15.240> has<00:01:16.020> more<00:01:16.320> components<00:01:16.860> in<00:01:17.100> the 00:01:17.719 --> 00:01:17.729 align:start position:0% recently ENS has more components in the 00:01:17.729 --> 00:01:20.359 align:start position:0% recently ENS has more components in the stack<00:01:18.320> and<00:01:19.320> we<00:01:19.560> can<00:01:19.710> also<00:01:19.860> add<00:01:19.979> other 00:01:20.359 --> 00:01:20.369 align:start position:0% stack and we can also add other 00:01:20.369 --> 00:01:22.310 align:start position:0% stack and we can also add other technologies<00:01:21.119> technologies<00:01:21.570> through<00:01:22.200> the 00:01:22.310 --> 00:01:22.320 align:start position:0% technologies technologies through the 00:01:22.320 --> 00:01:25.580 align:start position:0% technologies technologies through the plug-in<00:01:22.530> API<00:01:23.060> and<00:01:24.060> we<00:01:24.270> work<00:01:24.479> with<00:01:24.840> some<00:01:25.080> other 00:01:25.580 --> 00:01:25.590 align:start position:0% plug-in API and we work with some other 00:01:25.590 --> 00:01:28.070 align:start position:0% plug-in API and we work with some other projects<00:01:26.549> to<00:01:26.670> include<00:01:27.150> to<00:01:27.360> add<00:01:27.780> their 00:01:28.070 --> 00:01:28.080 align:start position:0% projects to include to add their 00:01:28.080 --> 00:01:33.830 align:start position:0% projects to include to add their projects<00:01:28.590> between<00:01:29.189> work<00:01:30.920> so<00:01:32.119> the<00:01:33.119> first<00:01:33.689> big 00:01:33.830 --> 00:01:33.840 align:start position:0% projects between work so the first big 00:01:33.840 --> 00:01:36.429 align:start position:0% projects between work so the first big difference<00:01:33.990> of<00:01:34.350> embark<00:01:34.740> would<00:01:35.100> would<00:01:35.670> with 00:01:36.429 --> 00:01:36.439 align:start position:0% difference of embark would would with 00:01:36.439 --> 00:01:39.160 align:start position:0% difference of embark would would with other<00:01:37.439> tools<00:01:37.770> is<00:01:37.950> that<00:01:37.979> the<00:01:38.280> contracts<00:01:38.790> you 00:01:39.160 --> 00:01:39.170 align:start position:0% other tools is that the contracts you 00:01:39.170 --> 00:01:41.390 align:start position:0% other tools is that the contracts you describe<00:01:40.170> the<00:01:40.409> relationship<00:01:41.009> between<00:01:41.159> the 00:01:41.390 --> 00:01:41.400 align:start position:0% describe the relationship between the 00:01:41.400 --> 00:01:44.780 align:start position:0% describe the relationship between the contracts<00:01:41.909> so<00:01:42.509> it's<00:01:42.630> a<00:01:42.750> very<00:01:43.049> complex<00:01:43.640> and<00:01:44.640> of 00:01:44.780 --> 00:01:44.790 align:start position:0% contracts so it's a very complex and of 00:01:44.790 --> 00:01:47.510 align:start position:0% contracts so it's a very complex and of the<00:01:44.939> often<00:01:45.329> spaghetti-like<00:01:46.170> migrations<00:01:46.979> all 00:01:47.510 --> 00:01:47.520 align:start position:0% the often spaghetti-like migrations all 00:01:47.520 --> 00:01:48.969 align:start position:0% the often spaghetti-like migrations all we<00:01:47.700> have<00:01:47.820> to<00:01:47.970> do<00:01:48.090> is<00:01:48.210> really<00:01:48.479> describe 00:01:48.969 --> 00:01:48.979 align:start position:0% we have to do is really describe 00:01:48.979 --> 00:01:52.480 align:start position:0% we have to do is really describe contracts<00:01:49.979> are<00:01:50.570> related<00:01:51.570> to<00:01:51.659> each<00:01:51.750> other<00:01:51.960> and 00:01:52.480 --> 00:01:52.490 align:start position:0% contracts are related to each other and 00:01:52.490 --> 00:01:55.249 align:start position:0% contracts are related to each other and what<00:01:53.490> actions<00:01:53.880> you<00:01:54.000> might<00:01:54.210> want<00:01:54.479> to<00:01:54.509> do<00:01:54.720> once 00:01:55.249 --> 00:01:55.259 align:start position:0% what actions you might want to do once 00:01:55.259 --> 00:01:57.700 align:start position:0% what actions you might want to do once the<00:01:55.409> contract<00:01:55.680> is<00:01:55.920> deployed<00:01:56.310> and<00:01:56.700> and<00:01:56.939> other 00:01:57.700 --> 00:01:57.710 align:start position:0% the contract is deployed and and other 00:01:57.710 --> 00:02:00.910 align:start position:0% the contract is deployed and and other events<00:01:58.710> and<00:01:59.009> import<00:01:59.969> will<00:02:00.090> automatically 00:02:00.910 --> 00:02:00.920 align:start position:0% events and import will automatically 00:02:00.920 --> 00:02:03.469 align:start position:0% events and import will automatically figure<00:02:01.920> out<00:02:02.130> what<00:02:02.340> is<00:02:02.460> the<00:02:02.579> best<00:02:02.610> way<00:02:03.450> to 00:02:03.469 --> 00:02:03.479 align:start position:0% figure out what is the best way to 00:02:03.479 --> 00:02:07.130 align:start position:0% figure out what is the best way to deploy<00:02:04.290> those<00:02:05.130> contracts<00:02:05.700> to<00:02:06.210> reflect<00:02:06.899> the 00:02:07.130 --> 00:02:07.140 align:start position:0% deploy those contracts to reflect the 00:02:07.140 --> 00:02:09.080 align:start position:0% deploy those contracts to reflect the state<00:02:07.409> that<00:02:07.560> you<00:02:07.710> just<00:02:07.890> described<00:02:08.310> and<00:02:08.610> that's 00:02:09.080 --> 00:02:09.090 align:start position:0% state that you just described and that's 00:02:09.090 --> 00:02:12.320 align:start position:0% state that you just described and that's also<00:02:09.390> effects<00:02:10.229> if<00:02:10.349> you<00:02:10.619> change<00:02:11.610> particular 00:02:12.320 --> 00:02:12.330 align:start position:0% also effects if you change particular 00:02:12.330 --> 00:02:13.010 align:start position:0% also effects if you change particular contract 00:02:13.010 --> 00:02:13.020 align:start position:0% contract 00:02:13.020 --> 00:02:14.720 align:start position:0% contract he<00:02:13.530> will<00:02:13.710> not<00:02:13.830> deploy<00:02:14.130> everything<00:02:14.520> will 00:02:14.720 --> 00:02:14.730 align:start position:0% he will not deploy everything will 00:02:14.730 --> 00:02:17.300 align:start position:0% he will not deploy everything will deploy<00:02:15.540> only<00:02:15.750> what's<00:02:16.020> actually<00:02:16.230> needed<00:02:16.740> to 00:02:17.300 --> 00:02:17.310 align:start position:0% deploy only what's actually needed to 00:02:17.310 --> 00:02:19.400 align:start position:0% deploy only what's actually needed to again<00:02:17.580> reflect<00:02:18.450> that<00:02:18.660> particular 00:02:19.400 --> 00:02:19.410 align:start position:0% again reflect that particular 00:02:19.410 --> 00:02:24.440 align:start position:0% again reflect that particular configuration<00:02:20.780> so<00:02:21.920> stairs<00:02:22.920> uses<00:02:23.450> embark 00:02:24.440 --> 00:02:24.450 align:start position:0% configuration so stairs uses embark 00:02:24.450 --> 00:02:27.170 align:start position:0% configuration so stairs uses embark extensively<00:02:25.050> internally<00:02:25.950> for<00:02:26.370> the<00:02:26.640> Ford<00:02:27.000> apps 00:02:27.170 --> 00:02:27.180 align:start position:0% extensively internally for the Ford apps 00:02:27.180 --> 00:02:30.560 align:start position:0% extensively internally for the Ford apps and<00:02:27.480> smart<00:02:28.470> contracts<00:02:28.890> this<00:02:29.460> is<00:02:29.610> a<00:02:29.640> more<00:02:30.540> or 00:02:30.560 --> 00:02:30.570 align:start position:0% and smart contracts this is a more or 00:02:30.570 --> 00:02:33.530 align:start position:0% and smart contracts this is a more or less<00:02:30.750> real<00:02:31.350> example<00:02:32.070> I<00:02:32.250> am<00:02:32.760> already<00:02:33.000> for<00:02:33.300> it 00:02:33.530 --> 00:02:33.540 align:start position:0% less real example I am already for it 00:02:33.540 --> 00:02:36.980 align:start position:0% less real example I am already for it modified<00:02:33.990> a<00:02:34.260> lot<00:02:34.700> for<00:02:35.700> the<00:02:35.970> purposes<00:02:36.390> of<00:02:36.450> this 00:02:36.980 --> 00:02:36.990 align:start position:0% modified a lot for the purposes of this 00:02:36.990 --> 00:02:41.150 align:start position:0% modified a lot for the purposes of this presentation<00:02:38.360> but<00:02:39.560> the<00:02:40.560> first<00:02:40.800> thing<00:02:40.950> is<00:02:41.130> that 00:02:41.150 --> 00:02:41.160 align:start position:0% presentation but the first thing is that 00:02:41.160 --> 00:02:44.270 align:start position:0% presentation but the first thing is that there<00:02:41.640> are<00:02:41.790> environments<00:02:42.150> so<00:02:42.900> you<00:02:43.280> there's 00:02:44.270 --> 00:02:44.280 align:start position:0% there are environments so you there's 00:02:44.280 --> 00:02:46.310 align:start position:0% there are environments so you there's this<00:02:44.400> special<00:02:44.940> default<00:02:45.630> environment<00:02:46.140> which 00:02:46.310 --> 00:02:46.320 align:start position:0% this special default environment which 00:02:46.320 --> 00:02:49.750 align:start position:0% this special default environment which is<00:02:46.440> a<00:02:47.090> sort<00:02:48.090> of<00:02:48.180> environment<00:02:49.080> that<00:02:49.170> applies<00:02:49.500> to 00:02:49.750 --> 00:02:49.760 align:start position:0% is a sort of environment that applies to 00:02:49.760 --> 00:02:52.430 align:start position:0% is a sort of environment that applies to every<00:02:50.760> other<00:02:50.910> environment<00:02:51.510> and<00:02:51.720> then<00:02:52.140> you<00:02:52.260> can 00:02:52.430 --> 00:02:52.440 align:start position:0% every other environment and then you can 00:02:52.440 --> 00:02:55.040 align:start position:0% every other environment and then you can override<00:02:52.830> in<00:02:53.490> a<00:02:53.670> specific<00:02:54.120> environment<00:02:54.390> and 00:02:55.040 --> 00:02:55.050 align:start position:0% override in a specific environment and 00:02:55.050 --> 00:02:58.130 align:start position:0% override in a specific environment and in<00:02:55.170> particular<00:02:56.900> configurations<00:02:57.900> that<00:02:57.960> you 00:02:58.130 --> 00:02:58.140 align:start position:0% in particular configurations that you 00:02:58.140 --> 00:03:00.050 align:start position:0% in particular configurations that you might<00:02:58.320> need<00:02:58.470> so<00:02:58.980> in<00:02:59.100> this<00:02:59.220> case<00:02:59.490> there<00:02:59.790> is<00:02:59.820> this 00:03:00.050 --> 00:03:00.060 align:start position:0% might need so in this case there is this 00:03:00.060 --> 00:03:03.530 align:start position:0% might need so in this case there is this mini-me<00:03:00.780> token<00:03:01.650> Factory<00:03:02.100> which<00:03:02.820> it's<00:03:03.390> already 00:03:03.530 --> 00:03:03.540 align:start position:0% mini-me token Factory which it's already 00:03:03.540 --> 00:03:06.470 align:start position:0% mini-me token Factory which it's already deployed<00:03:04.020> in<00:03:04.170> robson<00:03:04.620> so<00:03:05.220> we<00:03:05.670> we<00:03:06.030> define<00:03:06.360> it 00:03:06.470 --> 00:03:06.480 align:start position:0% deployed in robson so we we define it 00:03:06.480 --> 00:03:09.080 align:start position:0% deployed in robson so we we define it there<00:03:06.690> so<00:03:06.930> when<00:03:07.170> we<00:03:07.320> do<00:03:07.500> when<00:03:07.920> we<00:03:08.070> deploy<00:03:08.850> to 00:03:09.080 --> 00:03:09.090 align:start position:0% there so when we do when we deploy to 00:03:09.090 --> 00:03:10.760 align:start position:0% there so when we do when we deploy to Russian<00:03:09.510> it<00:03:09.690> will<00:03:09.810> take<00:03:09.990> the<00:03:10.200> configuration 00:03:10.760 --> 00:03:10.770 align:start position:0% Russian it will take the configuration 00:03:10.770 --> 00:03:13.910 align:start position:0% Russian it will take the configuration of<00:03:10.950> of<00:03:11.610> default<00:03:12.360> merge<00:03:12.810> it<00:03:13.020> with<00:03:13.050> Robson<00:03:13.710> and 00:03:13.910 --> 00:03:13.920 align:start position:0% of of default merge it with Robson and 00:03:13.920 --> 00:03:16.360 align:start position:0% of of default merge it with Robson and in<00:03:14.430> that<00:03:14.580> case<00:03:14.730> will<00:03:14.970> not<00:03:15.180> try<00:03:15.510> to<00:03:15.540> redeploy 00:03:16.360 --> 00:03:16.370 align:start position:0% in that case will not try to redeploy 00:03:16.370 --> 00:03:20.510 align:start position:0% in that case will not try to redeploy mini<00:03:17.370> token<00:03:17.670> factory<00:03:18.030> we'll<00:03:18.180> just<00:03:18.480> reuse<00:03:19.520> that 00:03:20.510 --> 00:03:20.520 align:start position:0% mini token factory we'll just reuse that 00:03:20.520 --> 00:03:24.620 align:start position:0% mini token factory we'll just reuse that address<00:03:21.920> then<00:03:22.920> here<00:03:23.850> you<00:03:23.970> can<00:03:24.000> see<00:03:24.300> there's<00:03:24.540> a 00:03:24.620 --> 00:03:24.630 align:start position:0% address then here you can see there's a 00:03:24.630 --> 00:03:27.350 align:start position:0% address then here you can see there's a mini-me<00:03:25.230> token<00:03:25.530> factory<00:03:25.950> is<00:03:26.190> being<00:03:26.700> passed<00:03:27.150> as 00:03:27.350 --> 00:03:27.360 align:start position:0% mini-me token factory is being passed as 00:03:27.360 --> 00:03:30.230 align:start position:0% mini-me token factory is being passed as a<00:03:27.709> string<00:03:28.709> with<00:03:28.950> a<00:03:28.980> dollar<00:03:29.459> sign<00:03:29.730> and<00:03:29.970> that's<00:03:30.120> a 00:03:30.230 --> 00:03:30.240 align:start position:0% a string with a dollar sign and that's a 00:03:30.240 --> 00:03:32.930 align:start position:0% a string with a dollar sign and that's a special<00:03:30.890> this<00:03:31.890> is<00:03:31.950> a<00:03:32.040> special<00:03:32.070> directive<00:03:32.580> that 00:03:32.930 --> 00:03:32.940 align:start position:0% special this is a special directive that 00:03:32.940 --> 00:03:35.840 align:start position:0% special this is a special directive that it<00:03:33.300> doesn't<00:03:33.660> work<00:03:33.780> that<00:03:34.190> this<00:03:35.190> contract<00:03:35.730> for 00:03:35.840 --> 00:03:35.850 align:start position:0% it doesn't work that this contract for 00:03:35.850 --> 00:03:37.670 align:start position:0% it doesn't work that this contract for this<00:03:36.120> argument<00:03:36.570> it<00:03:36.690> needs<00:03:36.870> the<00:03:37.020> address<00:03:37.380> of 00:03:37.670 --> 00:03:37.680 align:start position:0% this argument it needs the address of 00:03:37.680 --> 00:03:41.030 align:start position:0% this argument it needs the address of this<00:03:37.830> of<00:03:38.280> this<00:03:38.550> contract<00:03:39.000> so<00:03:39.690> important<00:03:40.650> with 00:03:41.030 --> 00:03:41.040 align:start position:0% this of this contract so important with 00:03:41.040 --> 00:03:42.530 align:start position:0% this of this contract so important with this<00:03:41.190> knows<00:03:41.459> that<00:03:41.670> it<00:03:41.850> first<00:03:42.090> needs<00:03:42.209> to<00:03:42.420> deploy 00:03:42.530 --> 00:03:42.540 align:start position:0% this knows that it first needs to deploy 00:03:42.540 --> 00:03:46.010 align:start position:0% this knows that it first needs to deploy mini<00:03:43.380> mini<00:03:43.820> mini<00:03:44.820> me<00:03:44.970> token<00:03:45.300> factory<00:03:45.720> or 00:03:46.010 --> 00:03:46.020 align:start position:0% mini mini mini me token factory or 00:03:46.020 --> 00:03:48.470 align:start position:0% mini mini mini me token factory or guitar<00:03:46.500> dress<00:03:46.950> and<00:03:47.250> only<00:03:47.910> internally<00:03:48.270> it 00:03:48.470 --> 00:03:48.480 align:start position:0% guitar dress and only internally it 00:03:48.480 --> 00:03:53.060 align:start position:0% guitar dress and only internally it should<00:03:48.690> deploy<00:03:48.959> this<00:03:49.230> as<00:03:49.560> TT<00:03:49.890> token<00:03:52.070> there's 00:03:53.060 --> 00:03:53.070 align:start position:0% should deploy this as TT token there's 00:03:53.070 --> 00:03:54.890 align:start position:0% should deploy this as TT token there's also<00:03:53.220> other<00:03:53.490> directives<00:03:54.120> like<00:03:54.209> deploy<00:03:54.690> AF 00:03:54.890 --> 00:03:54.900 align:start position:0% also other directives like deploy AF 00:03:54.900 --> 00:03:57.170 align:start position:0% also other directives like deploy AF which<00:03:55.230> will<00:03:55.650> only<00:03:55.740> deploy<00:03:56.070> if<00:03:56.370> a<00:03:56.580> particular 00:03:57.170 --> 00:03:57.180 align:start position:0% which will only deploy if a particular 00:03:57.180 --> 00:03:59.540 align:start position:0% which will only deploy if a particular condition<00:03:57.750> is<00:03:57.870> true<00:03:58.140> that<00:03:58.680> can<00:03:58.860> be<00:03:58.980> something 00:03:59.540 --> 00:03:59.550 align:start position:0% condition is true that can be something 00:03:59.550 --> 00:04:01.070 align:start position:0% condition is true that can be something in<00:03:59.610> JavaScript<00:04:00.060> code<00:04:00.209> or<00:04:00.360> can<00:04:00.540> be<00:04:00.720> even<00:04:00.930> as 00:04:01.070 --> 00:04:01.080 align:start position:0% in JavaScript code or can be even as 00:04:01.080 --> 00:04:04.490 align:start position:0% in JavaScript code or can be even as something<00:04:01.380> in<00:04:01.830> a<00:04:01.980> contract<00:04:02.900> and<00:04:03.900> you<00:04:04.080> can<00:04:04.260> also 00:04:04.490 --> 00:04:04.500 align:start position:0% something in a contract and you can also 00:04:04.500 --> 00:04:07.340 align:start position:0% something in a contract and you can also do<00:04:05.160> multiple<00:04:05.640> actions<00:04:06.120> want<00:04:06.900> a<00:04:06.959> contract 00:04:07.340 --> 00:04:07.350 align:start position:0% do multiple actions want a contract 00:04:07.350 --> 00:04:09.110 align:start position:0% do multiple actions want a contract deploys<00:04:07.680> and<00:04:08.130> there's<00:04:08.520> other<00:04:08.670> directives 00:04:09.110 --> 00:04:09.120 align:start position:0% deploys and there's other directives 00:04:09.120 --> 00:04:10.820 align:start position:0% deploys and there's other directives here<00:04:09.450> which<00:04:09.630> are<00:04:09.840> not<00:04:10.140> really<00:04:10.380> going<00:04:10.560> to 00:04:10.820 --> 00:04:10.830 align:start position:0% here which are not really going to 00:04:10.830 --> 00:04:12.290 align:start position:0% here which are not really going to because<00:04:11.370> there's<00:04:11.520> a<00:04:11.610> lot<00:04:11.760> of<00:04:11.790> them<00:04:12.000> there's 00:04:12.290 --> 00:04:12.300 align:start position:0% because there's a lot of them there's 00:04:12.300 --> 00:04:14.420 align:start position:0% because there's a lot of them there's things<00:04:12.930> like<00:04:13.080> after<00:04:13.410> deploy<00:04:13.770> and<00:04:14.130> other 00:04:14.420 --> 00:04:14.430 align:start position:0% things like after deploy and other 00:04:14.430 --> 00:04:16.970 align:start position:0% things like after deploy and other directives<00:04:15.140> so<00:04:16.140> you<00:04:16.290> can<00:04:16.650> do<00:04:16.770> a<00:04:16.799> lot<00:04:16.950> of 00:04:16.970 --> 00:04:16.980 align:start position:0% directives so you can do a lot of 00:04:16.980 --> 00:04:18.860 align:start position:0% directives so you can do a lot of different<00:04:17.220> configurations<00:04:17.760> with<00:04:18.570> this<00:04:18.690> type 00:04:18.860 --> 00:04:18.870 align:start position:0% different configurations with this type 00:04:18.870 --> 00:04:22.430 align:start position:0% different configurations with this type of<00:04:18.900> thing<00:04:19.169> and<00:04:20.690> here's<00:04:21.690> another<00:04:21.960> example<00:04:22.109> that 00:04:22.430 --> 00:04:22.440 align:start position:0% of thing and here's another example that 00:04:22.440 --> 00:04:25.760 align:start position:0% of thing and here's another example that you<00:04:22.830> can<00:04:23.490> also<00:04:23.700> specify<00:04:24.000> a<00:04:24.330> URI<00:04:24.960> for 00:04:25.760 --> 00:04:25.770 align:start position:0% you can also specify a URI for 00:04:25.770 --> 00:04:28.159 align:start position:0% you can also specify a URI for particular<00:04:26.160> contract<00:04:26.610> and<00:04:27.360> this<00:04:27.660> very<00:04:27.870> useful 00:04:28.159 --> 00:04:28.169 align:start position:0% particular contract and this very useful 00:04:28.169 --> 00:04:29.540 align:start position:0% particular contract and this very useful if<00:04:28.259> you<00:04:28.379> want<00:04:28.500> to<00:04:28.650> quickly<00:04:28.860> prototype 00:04:29.540 --> 00:04:29.550 align:start position:0% if you want to quickly prototype 00:04:29.550 --> 00:04:31.430 align:start position:0% if you want to quickly prototype something<00:04:30.180> that<00:04:30.539> and<00:04:30.810> here's<00:04:31.169> a<00:04:31.229> contract 00:04:31.430 --> 00:04:31.440 align:start position:0% something that and here's a contract 00:04:31.440 --> 00:04:34.430 align:start position:0% something that and here's a contract from<00:04:31.770> open<00:04:32.190> sampling<00:04:32.669> in<00:04:33.360> this<00:04:33.569> case<00:04:33.810> give<00:04:34.229> us 00:04:34.430 --> 00:04:34.440 align:start position:0% from open sampling in this case give us 00:04:34.440 --> 00:04:37.850 align:start position:0% from open sampling in this case give us you<00:04:35.009> can<00:04:35.190> specify<00:04:35.370> a<00:04:35.610> URL<00:04:36.210> or<00:04:36.750> even<00:04:37.110> even<00:04:37.770> a 00:04:37.850 --> 00:04:37.860 align:start position:0% you can specify a URL or even even a 00:04:37.860 --> 00:04:43.219 align:start position:0% you can specify a URL or even even a swarm<00:04:38.509> URL<00:04:39.509> or<00:04:39.720> ipfs<00:04:42.020> that<00:04:43.020> comes 00:04:43.219 --> 00:04:43.229 align:start position:0% swarm URL or ipfs that comes 00:04:43.229 --> 00:04:49.460 align:start position:0% swarm URL or ipfs that comes configuration<00:04:43.979> by<00:04:45.139> the<00:04:46.139> ratio<00:04:48.470> okay 00:04:49.460 --> 00:04:49.470 align:start position:0% configuration by the ratio okay 00:04:49.470 --> 00:04:51.529 align:start position:0% configuration by the ratio okay questions<00:04:50.009> we<00:04:50.190> asked<00:04:50.400> no<00:04:50.580> sir<00:04:50.849> okay<00:04:51.090> all<00:04:51.389> right 00:04:51.529 --> 00:04:51.539 align:start position:0% questions we asked no sir okay all right 00:04:51.539 --> 00:04:55.580 align:start position:0% questions we asked no sir okay all right so<00:04:53.000> that<00:04:54.000> counts<00:04:54.120> by<00:04:54.389> default<00:04:54.750> we<00:04:54.900> will<00:04:55.259> take 00:04:55.580 --> 00:04:55.590 align:start position:0% so that counts by default we will take 00:04:55.590 --> 00:04:58.330 align:start position:0% so that counts by default we will take the<00:04:55.770> accounts<00:04:56.129> on<00:04:56.940> offer<00:04:57.300> connected<00:04:57.810> note 00:04:58.330 --> 00:04:58.340 align:start position:0% the accounts on offer connected note 00:04:58.340 --> 00:05:01.700 align:start position:0% the accounts on offer connected note however<00:04:59.340> you<00:04:59.520> can<00:04:59.759> specify<00:05:00.479> there's<00:05:01.380> a<00:05:01.470> light 00:05:01.700 --> 00:05:01.710 align:start position:0% however you can specify there's a light 00:05:01.710 --> 00:05:03.920 align:start position:0% however you can specify there's a light wallet<00:05:02.190> functionality<00:05:02.909> which<00:05:03.539> you<00:05:03.659> can<00:05:03.810> use 00:05:03.920 --> 00:05:03.930 align:start position:0% wallet functionality which you can use 00:05:03.930 --> 00:05:05.839 align:start position:0% wallet functionality which you can use to<00:05:03.960> specify<00:05:04.289> accounts<00:05:04.919> and<00:05:05.069> even<00:05:05.220> set<00:05:05.669> their 00:05:05.839 --> 00:05:05.849 align:start position:0% to specify accounts and even set their 00:05:05.849 --> 00:05:09.680 align:start position:0% to specify accounts and even set their balance<00:05:06.210> so<00:05:06.870> in<00:05:07.500> this<00:05:07.710> case<00:05:08.180> we<00:05:09.180> define<00:05:09.479> here 00:05:09.680 --> 00:05:09.690 align:start position:0% balance so in this case we define here 00:05:09.690 --> 00:05:11.930 align:start position:0% balance so in this case we define here two<00:05:09.900> accounts<00:05:10.349> we<00:05:10.500> use<00:05:10.650> a<00:05:10.680> private<00:05:11.069> key<00:05:11.280> not 00:05:11.930 --> 00:05:11.940 align:start position:0% two accounts we use a private key not 00:05:11.940 --> 00:05:15.860 align:start position:0% two accounts we use a private key not wanna<00:05:12.150> use<00:05:12.240> a<00:05:12.509> mnemonic<00:05:12.750> and<00:05:14.509> there's<00:05:15.509> two 00:05:15.860 --> 00:05:15.870 align:start position:0% wanna use a mnemonic and there's two 00:05:15.870 --> 00:05:18.920 align:start position:0% wanna use a mnemonic and there's two examples<00:05:16.380> that<00:05:17.250> are<00:05:17.400> possible<00:05:17.819> it<00:05:18.389> preferably 00:05:18.920 --> 00:05:18.930 align:start position:0% examples that are possible it preferably 00:05:18.930 --> 00:05:20.540 align:start position:0% examples that are possible it preferably don't<00:05:19.169> put<00:05:19.319> your<00:05:19.469> private<00:05:19.740> key<00:05:19.919> and<00:05:20.250> source 00:05:20.540 --> 00:05:20.550 align:start position:0% don't put your private key and source 00:05:20.550 --> 00:05:24.409 align:start position:0% don't put your private key and source control<00:05:20.940> it's<00:05:21.599> a<00:05:21.690> good<00:05:21.810> idea<00:05:21.900> and<00:05:22.759> you<00:05:23.759> can<00:05:24.270> see 00:05:24.409 --> 00:05:24.419 align:start position:0% control it's a good idea and you can see 00:05:24.419 --> 00:05:26.360 align:start position:0% control it's a good idea and you can see there's<00:05:24.569> a<00:05:24.659> balance<00:05:24.990> five<00:05:25.229> eater<00:05:25.469> which<00:05:25.919> so<00:05:26.250> if 00:05:26.360 --> 00:05:26.370 align:start position:0% there's a balance five eater which so if 00:05:26.370 --> 00:05:28.070 align:start position:0% there's a balance five eater which so if you're<00:05:26.520> in<00:05:26.669> a<00:05:26.759> development<00:05:27.330> chain<00:05:27.569> or<00:05:27.840> it's<00:05:27.960> a 00:05:28.070 --> 00:05:28.080 align:start position:0% you're in a development chain or it's a 00:05:28.080 --> 00:05:29.870 align:start position:0% you're in a development chain or it's a hornet<00:05:28.440> when<00:05:28.860> a<00:05:28.889> testimony<00:05:29.460> we'll<00:05:29.639> set<00:05:29.849> that 00:05:29.870 --> 00:05:29.880 align:start position:0% hornet when a testimony we'll set that 00:05:29.880 --> 00:05:32.209 align:start position:0% hornet when a testimony we'll set that to<00:05:30.120> five<00:05:30.719> eater<00:05:30.900> of<00:05:31.169> course<00:05:31.680> this<00:05:31.800> won't<00:05:31.979> work 00:05:32.209 --> 00:05:32.219 align:start position:0% to five eater of course this won't work 00:05:32.219 --> 00:05:34.070 align:start position:0% to five eater of course this won't work and<00:05:32.400> may<00:05:32.550> not<00:05:32.759> but<00:05:33.150> it's<00:05:33.750> just<00:05:33.840> for 00:05:34.070 --> 00:05:34.080 align:start position:0% and may not but it's just for 00:05:34.080 --> 00:05:39.980 align:start position:0% and may not but it's just for development<00:05:34.819> and<00:05:36.469> ens<00:05:37.469> is<00:05:37.680> is<00:05:38.150> so<00:05:39.150> ENS<00:05:39.539> in<00:05:39.780> and 00:05:39.980 --> 00:05:39.990 align:start position:0% development and ens is is so ENS in and 00:05:39.990 --> 00:05:43.879 align:start position:0% development and ens is is so ENS in and work<00:05:40.169> is<00:05:40.289> considered<00:05:41.990> one<00:05:42.990> another<00:05:43.620> layer<00:05:43.860> in 00:05:43.879 --> 00:05:43.889 align:start position:0% work is considered one another layer in 00:05:43.889 --> 00:05:46.610 align:start position:0% work is considered one another layer in the<00:05:44.460> in<00:05:44.789> the<00:05:44.940> stack<00:05:45.210> so<00:05:45.900> which<00:05:46.169> is<00:05:46.289> the<00:05:46.409> naming 00:05:46.610 --> 00:05:46.620 align:start position:0% the in the stack so which is the naming 00:05:46.620 --> 00:05:49.219 align:start position:0% the in the stack so which is the naming layer<00:05:46.919> the<00:05:47.789> NS<00:05:48.060> right<00:05:48.509> now<00:05:48.630> seems<00:05:48.870> to<00:05:48.930> be<00:05:49.020> the 00:05:49.219 --> 00:05:49.229 align:start position:0% layer the NS right now seems to be the 00:05:49.229 --> 00:05:54.040 align:start position:0% layer the NS right now seems to be the only<00:05:50.060> working<00:05:51.060> centralized<00:05:51.569> naming<00:05:52.550> system 00:05:54.040 --> 00:05:54.050 align:start position:0% only working centralized naming system 00:05:54.050 --> 00:05:56.050 align:start position:0% only working centralized naming system so<00:05:55.050> it's<00:05:55.199> only<00:05:55.349> what<00:05:55.590> that's<00:05:55.770> actually 00:05:56.050 --> 00:05:56.060 align:start position:0% so it's only what that's actually 00:05:56.060 --> 00:06:00.409 align:start position:0% so it's only what that's actually supported<00:05:57.199> embark<00:05:58.199> will<00:05:58.969> when<00:05:59.969> you<00:06:00.240> are<00:06:00.300> in 00:06:00.409 --> 00:06:00.419 align:start position:0% supported embark will when you are in 00:06:00.419 --> 00:06:01.700 align:start position:0% supported embark will when you are in the<00:06:00.509> velopment<00:06:00.779> chain<00:06:01.110> or<00:06:01.319> in<00:06:01.440> a<00:06:01.529> private 00:06:01.700 --> 00:06:01.710 align:start position:0% the velopment chain or in a private 00:06:01.710 --> 00:06:04.040 align:start position:0% the velopment chain or in a private chain<00:06:02.130> embark<00:06:02.849> will<00:06:02.969> automatically<00:06:03.630> deploy 00:06:04.040 --> 00:06:04.050 align:start position:0% chain embark will automatically deploy 00:06:04.050 --> 00:06:06.589 align:start position:0% chain embark will automatically deploy and<00:06:04.229> set<00:06:04.409> up<00:06:04.590> the<00:06:04.800> NS<00:06:05.130> contracts<00:06:05.639> so<00:06:06.300> you<00:06:06.360> can 00:06:06.589 --> 00:06:06.599 align:start position:0% and set up the NS contracts so you can 00:06:06.599 --> 00:06:09.790 align:start position:0% and set up the NS contracts so you can use<00:06:06.810> the<00:06:06.990> use<00:06:07.319> them<00:06:07.500> in<00:06:07.650> your<00:06:07.680> application<00:06:07.830> and 00:06:09.790 --> 00:06:09.800 align:start position:0% use the use them in your application and 00:06:09.800 --> 00:06:12.050 align:start position:0% use the use them in your application and this<00:06:10.800> whole<00:06:10.979> configuration<00:06:11.279> might<00:06:11.729> look<00:06:12.000> like 00:06:12.050 --> 00:06:12.060 align:start position:0% this whole configuration might look like 00:06:12.060 --> 00:06:15.050 align:start position:0% this whole configuration might look like so<00:06:12.990> in<00:06:13.289> this<00:06:13.469> case<00:06:13.710> when<00:06:14.039> this<00:06:14.219> is<00:06:14.340> enabled<00:06:14.610> and 00:06:15.050 --> 00:06:15.060 align:start position:0% so in this case when this is enabled and 00:06:15.060 --> 00:06:18.499 align:start position:0% so in this case when this is enabled and we<00:06:15.180> are<00:06:15.330> in<00:06:15.449> the<00:06:15.919> development<00:06:16.919> chain<00:06:17.219> if<00:06:18.180> I<00:06:18.389> go 00:06:18.499 --> 00:06:18.509 align:start position:0% we are in the development chain if I go 00:06:18.509 --> 00:06:20.420 align:start position:0% we are in the development chain if I go to<00:06:18.569> my<00:06:18.690> job<00:06:18.810> and<00:06:19.199> resolve<00:06:19.650> started<00:06:20.069> at<00:06:20.219> add 00:06:20.420 --> 00:06:20.430 align:start position:0% to my job and resolve started at add 00:06:20.430 --> 00:06:24.050 align:start position:0% to my job and resolve started at add that<00:06:20.699> will<00:06:21.349> that<00:06:22.349> will<00:06:22.409> resolve<00:06:23.279> to<00:06:23.460> the<00:06:23.490> to 00:06:24.050 --> 00:06:24.060 align:start position:0% that will that will resolve to the to 00:06:24.060 --> 00:06:25.790 align:start position:0% that will that will resolve to the to that<00:06:24.090> address<00:06:24.449> that<00:06:24.569> is<00:06:24.900> defined<00:06:25.229> and<00:06:25.469> you<00:06:25.650> can 00:06:25.790 --> 00:06:25.800 align:start position:0% that address that is defined and you can 00:06:25.800 --> 00:06:27.320 align:start position:0% that address that is defined and you can put<00:06:25.979> the<00:06:26.159> contract<00:06:26.490> or<00:06:26.759> contract<00:06:27.090> that<00:06:27.210> you 00:06:27.320 --> 00:06:27.330 align:start position:0% put the contract or contract that you 00:06:27.330 --> 00:06:30.769 align:start position:0% put the contract or contract that you just<00:06:27.900> deploy<00:06:28.229> as<00:06:29.130> one<00:06:29.610> of<00:06:29.699> those<00:06:29.849> addresses<00:06:30.180> if 00:06:30.769 --> 00:06:30.779 align:start position:0% just deploy as one of those addresses if 00:06:30.779 --> 00:06:33.829 align:start position:0% just deploy as one of those addresses if your<00:06:31.259> tab<00:06:31.500> then<00:06:32.069> is<00:06:32.340> if<00:06:32.880> you<00:06:33.120> are<00:06:33.240> having<00:06:33.270> bar 00:06:33.829 --> 00:06:33.839 align:start position:0% your tab then is if you are having bar 00:06:33.839 --> 00:06:36.230 align:start position:0% your tab then is if you are having bar connected<00:06:34.139> to<00:06:34.500> an<00:06:34.889> on<00:06:35.130> chain<00:06:35.430> like<00:06:35.699> Rob<00:06:35.969> Stan 00:06:36.230 --> 00:06:36.240 align:start position:0% connected to an on chain like Rob Stan 00:06:36.240 --> 00:06:36.800 align:start position:0% connected to an on chain like Rob Stan or<00:06:36.509> main 00:06:36.800 --> 00:06:36.810 align:start position:0% or main 00:06:36.810 --> 00:06:39.230 align:start position:0% or main then<00:06:37.440> it<00:06:37.650> will<00:06:37.800> just<00:06:38.070> use<00:06:38.250> the<00:06:38.460> NS<00:06:38.760> contracts 00:06:39.230 --> 00:06:39.240 align:start position:0% then it will just use the NS contracts 00:06:39.240 --> 00:06:40.940 align:start position:0% then it will just use the NS contracts that<00:06:39.419> are<00:06:39.600> already<00:06:39.720> there<00:06:39.900> it<00:06:40.169> will<00:06:40.260> not<00:06:40.410> not 00:06:40.940 --> 00:06:40.950 align:start position:0% that are already there it will not not 00:06:40.950 --> 00:06:46.280 align:start position:0% that are already there it will not not try<00:06:41.220> to<00:06:41.419> to<00:06:42.419> redeploy<00:06:42.690> them<00:06:44.150> or<00:06:45.150> it<00:06:45.450> that<00:06:45.870> test 00:06:46.280 --> 00:06:46.290 align:start position:0% try to to redeploy them or it that test 00:06:46.290 --> 00:06:48.950 align:start position:0% try to to redeploy them or it that test so<00:06:47.220> there's<00:06:47.370> a<00:06:47.430> lot<00:06:47.550> functional<00:06:47.970> in<00:06:48.060> the<00:06:48.600> test 00:06:48.950 --> 00:06:48.960 align:start position:0% so there's a lot functional in the test 00:06:48.960 --> 00:06:51.170 align:start position:0% so there's a lot functional in the test they<00:06:49.740> are<00:06:49.860> they<00:06:50.220> are<00:06:50.280> quite<00:06:50.490> flexible<00:06:50.669> in<00:06:51.120> the 00:06:51.170 --> 00:06:51.180 align:start position:0% they are they are quite flexible in the 00:06:51.180 --> 00:06:53.510 align:start position:0% they are they are quite flexible in the sense<00:06:51.210> that<00:06:51.419> you<00:06:51.600> can<00:06:51.810> use<00:06:52.080> the<00:06:52.889> same<00:06:53.130> contract 00:06:53.510 --> 00:06:53.520 align:start position:0% sense that you can use the same contract 00:06:53.520 --> 00:06:55.600 align:start position:0% sense that you can use the same contract configuration<00:06:54.120> that<00:06:54.240> we<00:06:54.419> say<00:06:54.630> within<00:06:54.870> before 00:06:55.600 --> 00:06:55.610 align:start position:0% configuration that we say within before 00:06:55.610 --> 00:06:58.430 align:start position:0% configuration that we say within before if<00:06:56.610> if<00:06:57.090> you<00:06:57.330> don't<00:06:57.540> want<00:06:57.690> it<00:06:57.840> in<00:06:58.020> one<00:06:58.050> of<00:06:58.290> the 00:06:58.430 --> 00:06:58.440 align:start position:0% if if you don't want it in one of the 00:06:58.440 --> 00:07:00.110 align:start position:0% if if you don't want it in one of the very<00:06:58.650> very<00:06:58.710> pure<00:06:59.070> unit<00:06:59.460> tests<00:06:59.669> you<00:06:59.790> can<00:06:59.970> also 00:07:00.110 --> 00:07:00.120 align:start position:0% very very pure unit tests you can also 00:07:00.120 --> 00:07:02.390 align:start position:0% very very pure unit tests you can also do<00:07:00.810> that<00:07:00.990> just<00:07:01.230> import<00:07:01.530> the<00:07:01.620> contract<00:07:01.980> objects 00:07:02.390 --> 00:07:02.400 align:start position:0% do that just import the contract objects 00:07:02.400 --> 00:07:05.150 align:start position:0% do that just import the contract objects and<00:07:02.730> deploy<00:07:03.030> deploy<00:07:03.660> them<00:07:03.990> in<00:07:04.110> before<00:07:04.530> each<00:07:04.830> or 00:07:05.150 --> 00:07:05.160 align:start position:0% and deploy deploy them in before each or 00:07:05.160 --> 00:07:09.020 align:start position:0% and deploy deploy them in before each or before<00:07:05.940> all<00:07:06.560> they're<00:07:07.560> quite<00:07:07.770> fast<00:07:08.100> they<00:07:08.460> they 00:07:09.020 --> 00:07:09.030 align:start position:0% before all they're quite fast they they 00:07:09.030 --> 00:07:12.230 align:start position:0% before all they're quite fast they they try<00:07:09.560> there's<00:07:10.560> like<00:07:10.770> little<00:07:11.370> tricks<00:07:11.639> that<00:07:11.880> the 00:07:12.230 --> 00:07:12.240 align:start position:0% try there's like little tricks that the 00:07:12.240 --> 00:07:13.550 align:start position:0% try there's like little tricks that the framework<00:07:12.450> tries<00:07:12.780> to<00:07:13.020> do<00:07:13.139> it<00:07:13.229> like<00:07:13.380> if<00:07:13.530> you 00:07:13.550 --> 00:07:13.560 align:start position:0% framework tries to do it like if you 00:07:13.560 --> 00:07:15.650 align:start position:0% framework tries to do it like if you have<00:07:13.710> any<00:07:13.860> mark<00:07:14.190> instance<00:07:14.700> you<00:07:15.270> will<00:07:15.389> actually 00:07:15.650 --> 00:07:15.660 align:start position:0% have any mark instance you will actually 00:07:15.660 --> 00:07:17.480 align:start position:0% have any mark instance you will actually connect<00:07:15.960> it<00:07:16.110> and<00:07:16.200> instance<00:07:16.620> and<00:07:16.860> we<00:07:16.979> use<00:07:17.160> a<00:07:17.190> lot 00:07:17.480 --> 00:07:17.490 align:start position:0% connect it and instance and we use a lot 00:07:17.490 --> 00:07:20.120 align:start position:0% connect it and instance and we use a lot of<00:07:17.550> the<00:07:18.389> code<00:07:19.139> that's<00:07:19.320> already<00:07:19.410> running<00:07:19.770> like 00:07:20.120 --> 00:07:20.130 align:start position:0% of the code that's already running like 00:07:20.130 --> 00:07:22.280 align:start position:0% of the code that's already running like might<00:07:21.060> we<00:07:21.210> use<00:07:21.240> the<00:07:21.479> compiler<00:07:21.960> or<00:07:22.139> might<00:07:22.260> even 00:07:22.280 --> 00:07:22.290 align:start position:0% might we use the compiler or might even 00:07:22.290 --> 00:07:24.110 align:start position:0% might we use the compiler or might even we<00:07:22.620> use<00:07:22.770> the<00:07:22.950> node<00:07:23.130> that<00:07:23.370> you<00:07:23.520> already<00:07:23.760> have 00:07:24.110 --> 00:07:24.120 align:start position:0% we use the node that you already have 00:07:24.120 --> 00:07:27.650 align:start position:0% we use the node that you already have which<00:07:24.330> is<00:07:24.479> much<00:07:25.050> faster<00:07:25.290> than<00:07:25.530> putting<00:07:26.370> a<00:07:26.660> VM 00:07:27.650 --> 00:07:27.660 align:start position:0% which is much faster than putting a VM 00:07:27.660 --> 00:07:30.590 align:start position:0% which is much faster than putting a VM on<00:07:28.229> the<00:07:28.350> spot<00:07:28.590> it<00:07:29.400> will<00:07:29.550> display<00:07:29.850> Gaskell's 00:07:30.590 --> 00:07:30.600 align:start position:0% on the spot it will display Gaskell's 00:07:30.600 --> 00:07:32.719 align:start position:0% on the spot it will display Gaskell's and<00:07:30.810> he<00:07:30.900> also<00:07:31.050> supports<00:07:31.470> code<00:07:31.650> coverage<00:07:32.040> out 00:07:32.719 --> 00:07:32.729 align:start position:0% and he also supports code coverage out 00:07:32.729 --> 00:07:35.690 align:start position:0% and he also supports code coverage out of<00:07:32.880> the<00:07:33.030> box<00:07:33.210> and<00:07:34.490> there's<00:07:35.490> a<00:07:35.550> lot<00:07:35.669> of 00:07:35.690 --> 00:07:35.700 align:start position:0% of the box and there's a lot of 00:07:35.700 --> 00:07:38.960 align:start position:0% of the box and there's a lot of functionality<00:07:35.940> in<00:07:36.330> producing<00:07:37.080> bark<00:07:37.290> which<00:07:37.970> we 00:07:38.960 --> 00:07:38.970 align:start position:0% functionality in producing bark which we 00:07:38.970 --> 00:07:40.550 align:start position:0% functionality in producing bark which we cannot<00:07:39.180> really<00:07:39.360> cover<00:07:39.630> it<00:07:39.720> here<00:07:39.960> but<00:07:40.169> for 00:07:40.550 --> 00:07:40.560 align:start position:0% cannot really cover it here but for 00:07:40.560 --> 00:07:42.290 align:start position:0% cannot really cover it here but for instance<00:07:40.890> there's<00:07:41.039> full<00:07:41.280> support<00:07:41.640> for<00:07:41.789> for 00:07:42.290 --> 00:07:42.300 align:start position:0% instance there's full support for for 00:07:42.300 --> 00:07:46.400 align:start position:0% instance there's full support for for web<00:07:43.080> pack<00:07:43.380> so<00:07:43.680> it<00:07:43.770> makes<00:07:43.979> it<00:07:44.130> very<00:07:44.250> easy<00:07:44.370> to<00:07:45.410> do 00:07:46.400 --> 00:07:46.410 align:start position:0% web pack so it makes it very easy to do 00:07:46.410 --> 00:07:50.090 align:start position:0% web pack so it makes it very easy to do production<00:07:46.860> builds<00:07:47.460> of<00:07:48.330> your<00:07:48.570> diaper<00:07:48.780> or<00:07:49.289> so 00:07:50.090 --> 00:07:50.100 align:start position:0% production builds of your diaper or so 00:07:50.100 --> 00:07:51.980 align:start position:0% production builds of your diaper or so you<00:07:50.160> can<00:07:50.310> have<00:07:50.550> very<00:07:50.789> small<00:07:51.090> file<00:07:51.360> sizes<00:07:51.630> which 00:07:51.980 --> 00:07:51.990 align:start position:0% you can have very small file sizes which 00:07:51.990 --> 00:07:54.830 align:start position:0% you can have very small file sizes which is<00:07:52.220> really<00:07:53.220> handy<00:07:53.490> when<00:07:53.520> uploading<00:07:54.060> to<00:07:54.360> to 00:07:54.830 --> 00:07:54.840 align:start position:0% is really handy when uploading to to 00:07:54.840 --> 00:07:57.140 align:start position:0% is really handy when uploading to to switch<00:07:55.289> form<00:07:55.680> for<00:07:55.860> instance<00:07:56.150> supports 00:07:57.140 --> 00:07:57.150 align:start position:0% switch form for instance supports 00:07:57.150 --> 00:08:01.430 align:start position:0% switch form for instance supports already<00:07:57.530> IP<00:07:58.550> 1102<00:07:59.810> there's<00:08:00.810> many<00:08:01.020> templates 00:08:01.430 --> 00:08:01.440 align:start position:0% already IP 1102 there's many templates 00:08:01.440 --> 00:08:03.290 align:start position:0% already IP 1102 there's many templates ready<00:08:01.560> to<00:08:01.800> use<00:08:01.979> such<00:08:02.340> as<00:08:02.520> which<00:08:02.760> one<00:08:02.910> is<00:08:03.090> like<00:08:03.270> a 00:08:03.290 --> 00:08:03.300 align:start position:0% ready to use such as which one is like a 00:08:03.300 --> 00:08:05.540 align:start position:0% ready to use such as which one is like a react<00:08:03.600> Templar<00:08:04.020> or<00:08:04.260> or<00:08:04.979> when<00:08:05.130> you<00:08:05.220> want<00:08:05.400> to<00:08:05.430> do 00:08:05.540 --> 00:08:05.550 align:start position:0% react Templar or or when you want to do 00:08:05.550 --> 00:08:07.340 align:start position:0% react Templar or or when you want to do like<00:08:05.700> a<00:08:05.729> statue<00:08:06.090> snap<00:08:06.450> there's<00:08:06.780> also<00:08:06.900> plug-in 00:08:07.340 --> 00:08:07.350 align:start position:0% like a statue snap there's also plug-in 00:08:07.350 --> 00:08:10.790 align:start position:0% like a statue snap there's also plug-in for<00:08:07.500> that<00:08:08.030> and<00:08:09.030> it<00:08:09.930> can<00:08:10.110> very<00:08:10.350> easily<00:08:10.440> so 00:08:10.790 --> 00:08:10.800 align:start position:0% for that and it can very easily so 00:08:10.800 --> 00:08:13.730 align:start position:0% for that and it can very easily so create<00:08:11.220> private<00:08:11.610> change<00:08:11.880> so<00:08:12.870> if<00:08:13.020> I<00:08:13.440> would 00:08:13.730 --> 00:08:13.740 align:start position:0% create private change so if I would 00:08:13.740 --> 00:08:14.990 align:start position:0% create private change so if I would other<00:08:13.889> developers<00:08:14.370> you<00:08:14.460> want<00:08:14.580> to<00:08:14.639> develop<00:08:14.820> on 00:08:14.990 --> 00:08:15.000 align:start position:0% other developers you want to develop on 00:08:15.000 --> 00:08:16.820 align:start position:0% other developers you want to develop on the<00:08:15.060> same<00:08:15.180> chain<00:08:15.450> that's<00:08:15.690> also<00:08:16.050> pretty<00:08:16.650> simple 00:08:16.820 --> 00:08:16.830 align:start position:0% the same chain that's also pretty simple 00:08:16.830 --> 00:08:19.969 align:start position:0% the same chain that's also pretty simple to<00:08:17.100> do<00:08:17.220> and<00:08:17.400> there's<00:08:18.030> there's<00:08:18.570> a<00:08:18.660> plug-in<00:08:19.350> API 00:08:19.969 --> 00:08:19.979 align:start position:0% to do and there's there's a plug-in API 00:08:19.979 --> 00:08:22.520 align:start position:0% to do and there's there's a plug-in API that<00:08:20.460> allows<00:08:20.789> you<00:08:21.060> also<00:08:21.120> to<00:08:21.300> extend<00:08:21.660> and 00:08:22.520 --> 00:08:22.530 align:start position:0% that allows you also to extend and 00:08:22.530 --> 00:08:24.170 align:start position:0% that allows you also to extend and completely<00:08:23.010> change<00:08:23.250> the<00:08:23.340> functionality<00:08:23.789> if 00:08:24.170 --> 00:08:24.180 align:start position:0% completely change the functionality if 00:08:24.180 --> 00:08:24.800 align:start position:0% completely change the functionality if you<00:08:24.330> want<00:08:24.510> to 00:08:24.800 --> 00:08:24.810 align:start position:0% you want to 00:08:24.810 --> 00:08:28.090 align:start position:0% you want to in<00:08:25.169> fact<00:08:25.410> in<00:08:25.560> work<00:08:25.770> itself<00:08:26.130> is<00:08:26.720> entirely 00:08:28.090 --> 00:08:28.100 align:start position:0% in fact in work itself is entirely 00:08:28.100 --> 00:08:32.839 align:start position:0% in fact in work itself is entirely plug-in<00:08:29.960> based<00:08:30.960> so<00:08:31.320> everything<00:08:31.770> in<00:08:31.889> it<00:08:32.219> is<00:08:32.490> is 00:08:32.839 --> 00:08:32.849 align:start position:0% plug-in based so everything in it is is 00:08:32.849 --> 00:08:36.079 align:start position:0% plug-in based so everything in it is is implemented<00:08:33.659> as<00:08:33.779> a<00:08:34.080> plugin<00:08:34.529> so<00:08:35.219> if<00:08:35.760> you<00:08:35.909> wanna 00:08:36.079 --> 00:08:36.089 align:start position:0% implemented as a plugin so if you wanna 00:08:36.089 --> 00:08:37.969 align:start position:0% implemented as a plugin so if you wanna add<00:08:36.360> some<00:08:36.810> other<00:08:36.959> technology<00:08:37.560> or<00:08:37.650> completely 00:08:37.969 --> 00:08:37.979 align:start position:0% add some other technology or completely 00:08:37.979 --> 00:08:40.370 align:start position:0% add some other technology or completely change<00:08:38.219> you<00:08:38.430> you<00:08:38.849> can<00:08:39.360> actually<00:08:39.510> quite<00:08:40.169> easily 00:08:40.370 --> 00:08:40.380 align:start position:0% change you you can actually quite easily 00:08:40.380 --> 00:08:45.440 align:start position:0% change you you can actually quite easily so<00:08:41.630> now<00:08:42.630> embark<00:08:43.229> for<00:08:43.589> so<00:08:44.250> the<00:08:44.970> team<00:08:45.150> has<00:08:45.180> been 00:08:45.440 --> 00:08:45.450 align:start position:0% so now embark for so the team has been 00:08:45.450 --> 00:08:48.860 align:start position:0% so now embark for so the team has been working<00:08:45.890> hard<00:08:46.890> in<00:08:47.070> this<00:08:47.400> the<00:08:47.670> last<00:08:47.880> last<00:08:48.360> few 00:08:48.860 --> 00:08:48.870 align:start position:0% working hard in this the last last few 00:08:48.870 --> 00:08:49.140 align:start position:0% working hard in this the last last few more 00:08:49.140 --> 00:08:49.150 align:start position:0% more 00:08:49.150 --> 00:08:53.970 align:start position:0% more and<00:08:51.510> there's<00:08:52.510> this<00:08:52.660> there's<00:08:52.990> this<00:08:53.200> feature<00:08:53.800> in 00:08:53.970 --> 00:08:53.980 align:start position:0% and there's this there's this feature in 00:08:53.980 --> 00:08:55.530 align:start position:0% and there's this there's this feature in the<00:08:54.310> embark<00:08:54.580> tree<00:08:54.790> which<00:08:54.970> is<00:08:55.000> a<00:08:55.150> transaction 00:08:55.530 --> 00:08:55.540 align:start position:0% the embark tree which is a transaction 00:08:55.540 --> 00:08:58.890 align:start position:0% the embark tree which is a transaction logger<00:08:55.930> and<00:08:56.279> what<00:08:57.279> what<00:08:57.850> is<00:08:58.089> what<00:08:58.330> is<00:08:58.630> the 00:08:58.890 --> 00:08:58.900 align:start position:0% logger and what what is what is the 00:08:58.900 --> 00:09:01.680 align:start position:0% logger and what what is what is the dates<00:08:59.230> and<00:08:59.589> still<00:08:59.890> the<00:09:00.040> huts<00:09:00.220> is<00:09:00.480> when<00:09:01.480> you<00:09:01.570> do 00:09:01.680 --> 00:09:01.690 align:start position:0% dates and still the huts is when you do 00:09:01.690 --> 00:09:03.150 align:start position:0% dates and still the huts is when you do a<00:09:01.720> transaction<00:09:02.020> in<00:09:02.350> your<00:09:02.380> tab<00:09:02.710> say<00:09:02.980> of 00:09:03.150 --> 00:09:03.160 align:start position:0% a transaction in your tab say of 00:09:03.160 --> 00:09:05.100 align:start position:0% a transaction in your tab say of developing<00:09:03.640> it<00:09:04.089> will<00:09:04.240> show<00:09:04.390> in<00:09:04.510> the<00:09:04.600> logs<00:09:04.810> what 00:09:05.100 --> 00:09:05.110 align:start position:0% developing it will show in the logs what 00:09:05.110 --> 00:09:08.190 align:start position:0% developing it will show in the logs what contracts<00:09:05.890> you're<00:09:06.040> calling<00:09:06.720> what<00:09:07.720> mattered 00:09:08.190 --> 00:09:08.200 align:start position:0% contracts you're calling what mattered 00:09:08.200 --> 00:09:11.579 align:start position:0% contracts you're calling what mattered what<00:09:08.580> parameters<00:09:09.900> and<00:09:10.900> all<00:09:11.110> they<00:09:11.230> had<00:09:11.380> all 00:09:11.579 --> 00:09:11.589 align:start position:0% what parameters and all they had all 00:09:11.589 --> 00:09:14.820 align:start position:0% what parameters and all they had all that<00:09:11.710> all<00:09:12.070> that<00:09:12.250> information<00:09:13.140> in<00:09:14.140> import<00:09:14.560> for 00:09:14.820 --> 00:09:14.830 align:start position:0% that all that information in import for 00:09:14.830 --> 00:09:17.640 align:start position:0% that all that information in import for now<00:09:15.040> it<00:09:15.250> will<00:09:15.400> also<00:09:15.640> show<00:09:16.110> why<00:09:17.110> if<00:09:17.470> a 00:09:17.640 --> 00:09:17.650 align:start position:0% now it will also show why if a 00:09:17.650 --> 00:09:19.650 align:start position:0% now it will also show why if a transaction<00:09:17.920> failed<00:09:18.400> we<00:09:18.820> will<00:09:18.970> show<00:09:19.150> you<00:09:19.180> why 00:09:19.650 --> 00:09:19.660 align:start position:0% transaction failed we will show you why 00:09:19.660 --> 00:09:23.760 align:start position:0% transaction failed we will show you why and<00:09:19.990> exactly<00:09:20.860> what<00:09:21.190> line<00:09:21.520> caused<00:09:22.450> that<00:09:22.779> to 00:09:23.760 --> 00:09:23.770 align:start position:0% and exactly what line caused that to 00:09:23.770 --> 00:09:26.880 align:start position:0% and exactly what line caused that to fail<00:09:24.010> we'll<00:09:24.640> also<00:09:24.880> show<00:09:25.270> you<00:09:25.300> the<00:09:25.890> the 00:09:26.880 --> 00:09:26.890 align:start position:0% fail we'll also show you the the 00:09:26.890 --> 00:09:30.320 align:start position:0% fail we'll also show you the the variables<00:09:27.339> values<00:09:28.180> and<00:09:28.589> so<00:09:29.589> I<00:09:29.620> can<00:09:29.770> easily<00:09:29.890> see 00:09:30.320 --> 00:09:30.330 align:start position:0% variables values and so I can easily see 00:09:30.330 --> 00:09:41.750 align:start position:0% variables values and so I can easily see why<00:09:38.580> we<00:09:39.580> we<00:09:39.940> also<00:09:40.089> including<00:09:40.660> in<00:09:40.750> work<00:09:40.960> for<00:09:41.200> a 00:09:41.750 --> 00:09:41.760 align:start position:0% why we we also including in work for a 00:09:41.760 --> 00:09:45.600 align:start position:0% why we we also including in work for a debugger<00:09:42.810> so<00:09:43.810> if<00:09:43.960> you<00:09:44.110> type<00:09:44.339> you<00:09:45.339> can<00:09:45.460> either 00:09:45.600 --> 00:09:45.610 align:start position:0% debugger so if you type you can either 00:09:45.610 --> 00:09:47.430 align:start position:0% debugger so if you type you can either type<00:09:45.850> debug<00:09:46.210> in<00:09:46.420> the<00:09:46.540> transaction<00:09:47.080> or<00:09:47.170> you<00:09:47.260> can 00:09:47.430 --> 00:09:47.440 align:start position:0% type debug in the transaction or you can 00:09:47.440 --> 00:09:49.230 align:start position:0% type debug in the transaction or you can or<00:09:47.589> if<00:09:47.710> you<00:09:47.830> just<00:09:48.010> type<00:09:48.220> debug<00:09:48.640> then<00:09:48.910> it<00:09:49.089> will 00:09:49.230 --> 00:09:49.240 align:start position:0% or if you just type debug then it will 00:09:49.240 --> 00:09:51.600 align:start position:0% or if you just type debug then it will debug<00:09:50.170> the<00:09:50.350> last<00:09:50.589> filling<00:09:50.950> transaction<00:09:51.490> so 00:09:51.600 --> 00:09:51.610 align:start position:0% debug the last filling transaction so 00:09:51.610 --> 00:09:54.540 align:start position:0% debug the last filling transaction so you<00:09:51.700> can<00:09:51.880> easily<00:09:52.320> you<00:09:53.320> can<00:09:53.470> quickly<00:09:53.740> see<00:09:54.100> okay 00:09:54.540 --> 00:09:54.550 align:start position:0% you can easily you can quickly see okay 00:09:54.550 --> 00:09:57.240 align:start position:0% you can easily you can quickly see okay what<00:09:54.730> are<00:09:54.880> the<00:09:55.350> values<00:09:56.350> of<00:09:56.470> the<00:09:56.589> variables<00:09:57.070> you 00:09:57.240 --> 00:09:57.250 align:start position:0% what are the values of the variables you 00:09:57.250 --> 00:10:00.060 align:start position:0% what are the values of the variables you can<00:09:57.370> UNIX<00:09:57.820> previous<00:09:58.420> and<00:09:58.990> other<00:09:59.320> other 00:10:00.060 --> 00:10:00.070 align:start position:0% can UNIX previous and other other 00:10:00.070 --> 00:10:04.940 align:start position:0% can UNIX previous and other other commands<00:10:01.529> we<00:10:02.529> also<00:10:02.740> including<00:10:03.450> experimental 00:10:04.940 --> 00:10:04.950 align:start position:0% commands we also including experimental 00:10:04.950 --> 00:10:08.730 align:start position:0% commands we also including experimental DAP<00:10:05.950> generator<00:10:06.779> and<00:10:07.779> the<00:10:07.959> idea<00:10:08.200> of<00:10:08.260> this<00:10:08.470> is 00:10:08.730 --> 00:10:08.740 align:start position:0% DAP generator and the idea of this is 00:10:08.740 --> 00:10:10.530 align:start position:0% DAP generator and the idea of this is that<00:10:08.920> you<00:10:09.070> can<00:10:09.279> you<00:10:09.640> can<00:10:09.820> give<00:10:09.970> him<00:10:10.060> work<00:10:10.270> a 00:10:10.530 --> 00:10:10.540 align:start position:0% that you can you can give him work a 00:10:10.540 --> 00:10:13.019 align:start position:0% that you can you can give him work a contract<00:10:11.140> and<00:10:11.410> he<00:10:12.130> will<00:10:12.339> attempt<00:10:12.730> to<00:10:12.790> generate 00:10:13.019 --> 00:10:13.029 align:start position:0% contract and he will attempt to generate 00:10:13.029 --> 00:10:17.190 align:start position:0% contract and he will attempt to generate a<00:10:13.570> react<00:10:14.020> app<00:10:14.970> that<00:10:15.970> works<00:10:16.240> for<00:10:16.510> that<00:10:16.630> for<00:10:17.170> that 00:10:17.190 --> 00:10:17.200 align:start position:0% a react app that works for that for that 00:10:17.200 --> 00:10:19.260 align:start position:0% a react app that works for that for that contract<00:10:17.800> which<00:10:17.980> is<00:10:18.100> can<00:10:18.550> be<00:10:18.670> quite<00:10:18.880> handy<00:10:19.240> for 00:10:19.260 --> 00:10:19.270 align:start position:0% contract which is can be quite handy for 00:10:19.270 --> 00:10:23.370 align:start position:0% contract which is can be quite handy for for<00:10:20.110> prototyping<00:10:20.440> and<00:10:21.279> which<00:10:21.940> we<00:10:22.360> want<00:10:22.720> a 00:10:23.370 --> 00:10:23.380 align:start position:0% for prototyping and which we want a 00:10:23.380 --> 00:10:27.090 align:start position:0% for prototyping and which we want a level<00:10:23.980> deeper<00:10:24.279> and<00:10:24.820> a<00:10:25.230> for<00:10:26.230> certain<00:10:26.650> for 00:10:27.090 --> 00:10:27.100 align:start position:0% level deeper and a for certain for 00:10:27.100 --> 00:10:29.210 align:start position:0% level deeper and a for certain for particular<00:10:27.490> cases<00:10:27.670> you<00:10:28.510> can<00:10:28.690> also<00:10:28.810> just 00:10:29.210 --> 00:10:29.220 align:start position:0% particular cases you can also just 00:10:29.220 --> 00:10:31.980 align:start position:0% particular cases you can also just specify<00:10:30.220> like<00:10:30.400> a<00:10:30.459> model<00:10:31.000> and<00:10:31.330> it<00:10:31.630> will<00:10:31.750> create 00:10:31.980 --> 00:10:31.990 align:start position:0% specify like a model and it will create 00:10:31.990 --> 00:10:35.040 align:start position:0% specify like a model and it will create the<00:10:32.310> it<00:10:33.310> will<00:10:33.640> create<00:10:33.820> entire<00:10:34.180> the<00:10:34.540> contract 00:10:35.040 --> 00:10:35.050 align:start position:0% the it will create entire the contract 00:10:35.050 --> 00:10:37.260 align:start position:0% the it will create entire the contract and<00:10:35.260> the<00:10:35.440> DAP<00:10:35.680> based<00:10:36.610> on<00:10:36.820> the<00:10:36.970> own<00:10:37.120> the 00:10:37.260 --> 00:10:37.270 align:start position:0% and the DAP based on the own the 00:10:37.270 --> 00:10:38.970 align:start position:0% and the DAP based on the own the configuration<00:10:37.839> that<00:10:37.930> you<00:10:38.080> date<00:10:38.230> so<00:10:38.380> in<00:10:38.830> the 00:10:38.970 --> 00:10:38.980 align:start position:0% configuration that you date so in the 00:10:38.980 --> 00:10:41.610 align:start position:0% configuration that you date so in the case<00:10:39.160> of<00:10:39.339> this<00:10:39.520> of<00:10:39.850> this<00:10:40.060> command<00:10:40.620> for 00:10:41.610 --> 00:10:41.620 align:start position:0% case of this of this command for 00:10:41.620 --> 00:10:43.680 align:start position:0% case of this of this command for instance<00:10:41.890> because<00:10:42.010> that's<00:10:42.339> picture<00:10:42.790> ipfs<00:10:43.450> it 00:10:43.680 --> 00:10:43.690 align:start position:0% instance because that's picture ipfs it 00:10:43.690 --> 00:10:45.180 align:start position:0% instance because that's picture ipfs it knows<00:10:43.870> that<00:10:43.900> it<00:10:44.709> has<00:10:44.740> to<00:10:44.980> put<00:10:45.130> the 00:10:45.180 --> 00:10:45.190 align:start position:0% knows that it has to put the 00:10:45.190 --> 00:10:47.690 align:start position:0% knows that it has to put the functionality<00:10:46.060> to<00:10:46.240> upload<00:10:47.110> and<00:10:47.350> display 00:10:47.690 --> 00:10:47.700 align:start position:0% functionality to upload and display 00:10:47.700 --> 00:10:50.699 align:start position:0% functionality to upload and display pictures<00:10:48.700> they<00:10:49.360> should<00:10:49.540> go<00:10:49.660> to<00:10:49.720> my<00:10:49.900> PFS<00:10:50.140> and 00:10:50.699 --> 00:10:50.709 align:start position:0% pictures they should go to my PFS and 00:10:50.709 --> 00:10:52.769 align:start position:0% pictures they should go to my PFS and the<00:10:51.250> ash<00:10:51.400> that<00:10:51.430> Scott's<00:10:51.850> return<00:10:52.180> needs<00:10:52.450> to<00:10:52.600> be 00:10:52.769 --> 00:10:52.779 align:start position:0% the ash that Scott's return needs to be 00:10:52.779 --> 00:10:56.769 align:start position:0% the ash that Scott's return needs to be in<00:10:53.770> the<00:10:53.920> in<00:10:54.100> the<00:10:54.190> smart<00:10:54.459> contract 00:10:56.769 --> 00:10:56.779 align:start position:0% in the in the smart contract 00:10:56.779 --> 00:11:01.360 align:start position:0% in the in the smart contract now<00:10:58.010> embark<00:10:59.010> as<00:10:59.519> since<00:11:00.000> version<00:11:00.300> 2<00:11:00.750> I<00:11:00.779> believe 00:11:01.360 --> 00:11:01.370 align:start position:0% now embark as since version 2 I believe 00:11:01.370 --> 00:11:05.000 align:start position:0% now embark as since version 2 I believe this<00:11:02.370> dashboards<00:11:03.089> and<00:11:03.470> just<00:11:04.470> be<00:11:04.589> very<00:11:04.620> clear 00:11:05.000 --> 00:11:05.010 align:start position:0% this dashboards and just be very clear 00:11:05.010 --> 00:11:09.740 align:start position:0% this dashboards and just be very clear this<00:11:05.160> is<00:11:05.310> not<00:11:05.490> going<00:11:06.450> away<00:11:07.700> because<00:11:08.700> we<00:11:09.600> got 00:11:09.740 --> 00:11:09.750 align:start position:0% this is not going away because we got 00:11:09.750 --> 00:11:11.930 align:start position:0% this is not going away because we got very<00:11:09.930> typically<00:11:10.470> very<00:11:10.680> good<00:11:10.860> feedback<00:11:11.490> on 00:11:11.930 --> 00:11:11.940 align:start position:0% very typically very good feedback on 00:11:11.940 --> 00:11:13.670 align:start position:0% very typically very good feedback on this 00:11:13.670 --> 00:11:13.680 align:start position:0% this 00:11:13.680 --> 00:11:17.750 align:start position:0% this however<00:11:14.550> we<00:11:15.240> introducing<00:11:15.779> now<00:11:16.339> cockpits<00:11:17.339> and 00:11:17.750 --> 00:11:17.760 align:start position:0% however we introducing now cockpits and 00:11:17.760 --> 00:11:21.100 align:start position:0% however we introducing now cockpits and this<00:11:18.660> is<00:11:19.040> this<00:11:20.040> is<00:11:20.190> essentially<00:11:20.700> a 00:11:21.100 --> 00:11:21.110 align:start position:0% this is this is essentially a 00:11:21.110 --> 00:11:24.019 align:start position:0% this is this is essentially a complimentary<00:11:22.110> but<00:11:22.920> it<00:11:23.100> launches<00:11:23.610> it 00:11:24.019 --> 00:11:24.029 align:start position:0% complimentary but it launches it 00:11:24.029 --> 00:11:27.290 align:start position:0% complimentary but it launches it launches<00:11:24.390> a<00:11:24.420> UI<00:11:24.930> that<00:11:25.470> you<00:11:26.070> can<00:11:26.730> you<00:11:27.149> can 00:11:27.290 --> 00:11:27.300 align:start position:0% launches a UI that you can you can 00:11:27.300 --> 00:11:30.530 align:start position:0% launches a UI that you can you can access<00:11:27.839> to<00:11:28.140> interact<00:11:28.589> with<00:11:28.709> would<00:11:29.100> embark<00:11:29.540> so 00:11:30.530 --> 00:11:30.540 align:start position:0% access to interact with would embark so 00:11:30.540 --> 00:11:33.620 align:start position:0% access to interact with would embark so it<00:11:31.350> kind<00:11:31.560> of<00:11:31.620> takes<00:11:31.800> that<00:11:31.920> dashboard<00:11:32.640> and<00:11:33.390> puts 00:11:33.620 --> 00:11:33.630 align:start position:0% it kind of takes that dashboard and puts 00:11:33.630 --> 00:11:36.230 align:start position:0% it kind of takes that dashboard and puts it<00:11:33.779> as<00:11:33.959> a<00:11:34.350> web<00:11:34.649> UI<00:11:34.860> so<00:11:35.490> you<00:11:35.790> have<00:11:35.910> the<00:11:36.060> same 00:11:36.230 --> 00:11:36.240 align:start position:0% it as a web UI so you have the same 00:11:36.240 --> 00:11:39.139 align:start position:0% it as a web UI so you have the same things<00:11:36.480> that<00:11:36.600> you<00:11:37.320> had<00:11:37.500> in<00:11:38.370> the<00:11:38.399> console<00:11:38.940> from 00:11:39.139 --> 00:11:39.149 align:start position:0% things that you had in the console from 00:11:39.149 --> 00:11:40.550 align:start position:0% things that you had in the console from the<00:11:39.269> services<00:11:39.750> you<00:11:39.930> can<00:11:40.050> see<00:11:40.170> the<00:11:40.260> deploy 00:11:40.550 --> 00:11:40.560 align:start position:0% the services you can see the deploy 00:11:40.560 --> 00:11:43.100 align:start position:0% the services you can see the deploy contract<00:11:41.130> but<00:11:41.910> it's<00:11:42.149> obviously<00:11:42.510> much<00:11:42.750> more 00:11:43.100 --> 00:11:43.110 align:start position:0% contract but it's obviously much more 00:11:43.110 --> 00:11:45.650 align:start position:0% contract but it's obviously much more interactive<00:11:43.560> so<00:11:43.950> for<00:11:44.519> example<00:11:44.850> the<00:11:45.060> in<00:11:45.450> the 00:11:45.650 --> 00:11:45.660 align:start position:0% interactive so for example the in the 00:11:45.660 --> 00:11:48.230 align:start position:0% interactive so for example the in the console<00:11:46.110> oh<00:11:46.410> yeah<00:11:47.070> we<00:11:47.279> also<00:11:47.310> have<00:11:47.640> like<00:11:47.790> light 00:11:48.230 --> 00:11:48.240 align:start position:0% console oh yeah we also have like light 00:11:48.240 --> 00:11:50.150 align:start position:0% console oh yeah we also have like light team<00:11:48.450> dark<00:11:48.779> team<00:11:49.019> depending<00:11:49.980> on<00:11:50.070> your 00:11:50.150 --> 00:11:50.160 align:start position:0% team dark team depending on your 00:11:50.160 --> 00:11:55.610 align:start position:0% team dark team depending on your preference<00:11:50.640> I<00:11:50.940> prefer<00:11:51.930> the<00:11:52.380> dark<00:11:54.140> so<00:11:55.140> the 00:11:55.610 --> 00:11:55.620 align:start position:0% preference I prefer the dark so the 00:11:55.620 --> 00:11:56.990 align:start position:0% preference I prefer the dark so the console<00:11:55.950> for<00:11:56.130> instance<00:11:56.430> you<00:11:56.550> have<00:11:56.640> also 00:11:56.990 --> 00:11:57.000 align:start position:0% console for instance you have also 00:11:57.000 --> 00:11:59.630 align:start position:0% console for instance you have also suggest<00:11:57.390> an<00:11:57.630> 8<00:11:57.899> it<00:11:58.500> tries<00:11:58.800> to<00:11:58.829> recognize<00:11:59.430> what 00:11:59.630 --> 00:11:59.640 align:start position:0% suggest an 8 it tries to recognize what 00:11:59.640 --> 00:12:01.579 align:start position:0% suggest an 8 it tries to recognize what you're<00:11:59.790> doing<00:12:00.209> and<00:12:00.510> give<00:12:01.320> it<00:12:01.380> a<00:12:01.440> proper 00:12:01.579 --> 00:12:01.589 align:start position:0% you're doing and give it a proper 00:12:01.589 --> 00:12:03.949 align:start position:0% you're doing and give it a proper suggestion<00:12:02.310> so<00:12:02.459> if<00:12:02.519> you're<00:12:02.670> using<00:12:02.820> web<00:12:03.060> 3<00:12:03.329> it 00:12:03.949 --> 00:12:03.959 align:start position:0% suggestion so if you're using web 3 it 00:12:03.959 --> 00:12:05.420 align:start position:0% suggestion so if you're using web 3 it kind<00:12:04.170> of<00:12:04.230> gives<00:12:04.410> you<00:12:04.470> a<00:12:04.529> documentation<00:12:04.980> on<00:12:05.279> the 00:12:05.420 --> 00:12:05.430 align:start position:0% kind of gives you a documentation on the 00:12:05.430 --> 00:12:08.120 align:start position:0% kind of gives you a documentation on the spots<00:12:05.699> of<00:12:06.029> what<00:12:06.570> each<00:12:07.410> of<00:12:07.649> the<00:12:07.769> suggestions 00:12:08.120 --> 00:12:08.130 align:start position:0% spots of what each of the suggestions 00:12:08.130 --> 00:12:10.850 align:start position:0% spots of what each of the suggestions are<00:12:08.459> if<00:12:09.420> you're<00:12:09.630> typing<00:12:09.990> a<00:12:10.140> contract<00:12:10.589> address 00:12:10.850 --> 00:12:10.860 align:start position:0% are if you're typing a contract address 00:12:10.860 --> 00:12:12.920 align:start position:0% are if you're typing a contract address you<00:12:11.010> will<00:12:11.130> give<00:12:11.279> information<00:12:11.430> like<00:12:11.970> where 00:12:12.920 --> 00:12:12.930 align:start position:0% you will give information like where 00:12:12.930 --> 00:12:14.630 align:start position:0% you will give information like where that<00:12:13.079> contract<00:12:13.560> is<00:12:13.800> deployed<00:12:14.160> what<00:12:14.430> is<00:12:14.519> the 00:12:14.630 --> 00:12:14.640 align:start position:0% that contract is deployed what is the 00:12:14.640 --> 00:12:17.870 align:start position:0% that contract is deployed what is the type<00:12:14.820> of<00:12:14.850> the<00:12:15.390> object<00:12:16.459> it<00:12:17.459> also<00:12:17.640> has<00:12:17.850> a 00:12:17.870 --> 00:12:17.880 align:start position:0% type of the object it also has a 00:12:17.880 --> 00:12:21.680 align:start position:0% type of the object it also has a blockchain<00:12:18.360> Explorer<00:12:19.279> so<00:12:20.279> I<00:12:20.390> it<00:12:21.390> has<00:12:21.510> pretty 00:12:21.680 --> 00:12:21.690 align:start position:0% blockchain Explorer so I it has pretty 00:12:21.690 --> 00:12:22.910 align:start position:0% blockchain Explorer so I it has pretty much<00:12:21.779> typically<00:12:22.440> everything<00:12:22.740> you<00:12:22.829> would 00:12:22.910 --> 00:12:22.920 align:start position:0% much typically everything you would 00:12:22.920 --> 00:12:26.060 align:start position:0% much typically everything you would expect<00:12:23.430> to<00:12:23.699> have<00:12:24.600> from<00:12:25.470> accounts<00:12:25.860> block 00:12:26.060 --> 00:12:26.070 align:start position:0% expect to have from accounts block 00:12:26.070 --> 00:12:28.660 align:start position:0% expect to have from accounts block transactions<00:12:26.699> and<00:12:26.910> the<00:12:27.870> contracts<00:12:28.350> as<00:12:28.560> well 00:12:28.660 --> 00:12:28.670 align:start position:0% transactions and the contracts as well 00:12:28.670 --> 00:12:31.810 align:start position:0% transactions and the contracts as well the<00:12:29.670> contract<00:12:30.029> that<00:12:30.060> you<00:12:30.300> have<00:12:30.329> just<00:12:30.839> deployed 00:12:31.810 --> 00:12:31.820 align:start position:0% the contract that you have just deployed 00:12:31.820 --> 00:12:36.110 align:start position:0% the contract that you have just deployed it<00:12:32.820> has<00:12:33.089> a<00:12:33.140> editor<00:12:34.610> and<00:12:35.610> again<00:12:35.850> this<00:12:35.970> is 00:12:36.110 --> 00:12:36.120 align:start position:0% it has a editor and again this is 00:12:36.120 --> 00:12:38.000 align:start position:0% it has a editor and again this is complimentary<00:12:36.810> don't<00:12:37.199> you<00:12:37.350> can<00:12:37.560> still<00:12:37.829> use 00:12:38.000 --> 00:12:38.010 align:start position:0% complimentary don't you can still use 00:12:38.010 --> 00:12:41.540 align:start position:0% complimentary don't you can still use say<00:12:38.640> more<00:12:38.970> vehicles<00:12:39.810> or<00:12:40.050> or<00:12:40.290> forgot<00:12:41.220> for<00:12:41.399> ready 00:12:41.540 --> 00:12:41.550 align:start position:0% say more vehicles or or forgot for ready 00:12:41.550 --> 00:12:47.990 align:start position:0% say more vehicles or or forgot for ready max<00:12:44.990> so<00:12:46.040> and<00:12:47.040> when<00:12:47.250> you<00:12:47.370> when<00:12:47.670> you<00:12:47.760> open<00:12:47.970> a 00:12:47.990 --> 00:12:48.000 align:start position:0% max so and when you when you open a 00:12:48.000 --> 00:12:49.639 align:start position:0% max so and when you when you open a contract<00:12:48.420> file<00:12:48.600> you<00:12:48.720> can<00:12:48.839> immediately<00:12:49.079> you 00:12:49.639 --> 00:12:49.649 align:start position:0% contract file you can immediately you 00:12:49.649 --> 00:12:53.329 align:start position:0% contract file you can immediately you can<00:12:49.800> interact<00:12:50.279> with<00:12:50.490> it<00:12:50.750> and<00:12:51.750> in<00:12:52.440> the<00:12:52.680> ins<00:12:52.920> IDE 00:12:53.329 --> 00:12:53.339 align:start position:0% can interact with it and in the ins IDE 00:12:53.339 --> 00:12:56.389 align:start position:0% can interact with it and in the ins IDE you<00:12:53.519> can<00:12:53.699> see<00:12:53.850> here<00:12:54.269> in<00:12:54.390> the<00:12:54.480> sidebar<00:12:55.399> there's 00:12:56.389 --> 00:12:56.399 align:start position:0% you can see here in the sidebar there's 00:12:56.399 --> 00:12:58.790 align:start position:0% you can see here in the sidebar there's also<00:12:56.810> other<00:12:57.810> the<00:12:58.019> screenshot<00:12:58.470> might<00:12:58.620> be 00:12:58.790 --> 00:12:58.800 align:start position:0% also other the screenshot might be 00:12:58.800 --> 00:13:00.920 align:start position:0% also other the screenshot might be missing<00:12:59.190> there's<00:12:59.370> also<00:12:59.519> grass<00:12:59.880> a<00:13:00.149> gas<00:13:00.630> price 00:13:00.920 --> 00:13:00.930 align:start position:0% missing there's also grass a gas price 00:13:00.930 --> 00:13:04.069 align:start position:0% missing there's also grass a gas price estimator<00:13:01.579> which<00:13:02.579> is<00:13:02.760> useful<00:13:03.300> for<00:13:03.480> connecting 00:13:04.069 --> 00:13:04.079 align:start position:0% estimator which is useful for connecting 00:13:04.079 --> 00:13:06.590 align:start position:0% estimator which is useful for connecting to<00:13:04.140> a<00:13:04.709> more<00:13:05.310> public<00:13:05.490> network<00:13:06.029> so<00:13:06.209> I<00:13:06.300> can<00:13:06.449> see 00:13:06.590 --> 00:13:06.600 align:start position:0% to a more public network so I can see 00:13:06.600 --> 00:13:08.680 align:start position:0% to a more public network so I can see how<00:13:06.720> fast<00:13:07.050> the<00:13:07.709> transactions<00:13:08.279> can 00:13:08.680 --> 00:13:08.690 align:start position:0% how fast the transactions can 00:13:08.690 --> 00:13:11.500 align:start position:0% how fast the transactions can actually<00:13:09.050> go<00:13:09.230> and<00:13:09.530> for<00:13:09.710> what<00:13:09.830> price<00:13:10.040> I<00:13:10.510> will 00:13:11.500 --> 00:13:11.510 align:start position:0% actually go and for what price I will 00:13:11.510 --> 00:13:13.360 align:start position:0% actually go and for what price I will serve<00:13:11.660> the<00:13:11.750> details<00:13:12.230> in<00:13:12.470> case<00:13:12.590> you<00:13:12.740> need<00:13:12.890> a<00:13:13.160> bi 00:13:13.360 --> 00:13:13.370 align:start position:0% serve the details in case you need a bi 00:13:13.370 --> 00:13:16.630 align:start position:0% serve the details in case you need a bi or<00:13:13.850> the<00:13:14.180> bytecode<00:13:14.390> to<00:13:14.810> copy/paste<00:13:15.260> ads<00:13:15.640> we 00:13:16.630 --> 00:13:16.640 align:start position:0% or the bytecode to copy/paste ads we 00:13:16.640 --> 00:13:18.280 align:start position:0% or the bytecode to copy/paste ads we also<00:13:17.090> have<00:13:17.330> the<00:13:17.420> same<00:13:17.630> transaction<00:13:17.930> loader 00:13:18.280 --> 00:13:18.290 align:start position:0% also have the same transaction loader 00:13:18.290 --> 00:13:20.200 align:start position:0% also have the same transaction loader that<00:13:18.530> are<00:13:18.680> shown<00:13:18.830> on<00:13:18.950> the<00:13:19.040> console<00:13:19.400> been<00:13:20.090> in 00:13:20.200 --> 00:13:20.210 align:start position:0% that are shown on the console been in 00:13:20.210 --> 00:13:22.840 align:start position:0% that are shown on the console been in here<00:13:20.450> here<00:13:21.050> you<00:13:21.140> can<00:13:21.320> actually<00:13:21.500> see<00:13:22.430> what<00:13:22.640> were 00:13:22.840 --> 00:13:22.850 align:start position:0% here here you can actually see what were 00:13:22.850 --> 00:13:24.820 align:start position:0% here here you can actually see what were the<00:13:23.270> transactions<00:13:23.870> done<00:13:24.080> to<00:13:24.290> that<00:13:24.320> contract 00:13:24.820 --> 00:13:24.830 align:start position:0% the transactions done to that contract 00:13:24.830 --> 00:13:28.150 align:start position:0% the transactions done to that contract and<00:13:25.250> you<00:13:26.150> can<00:13:26.330> actually<00:13:26.720> filter<00:13:27.560> them<00:13:27.830> if<00:13:28.040> you 00:13:28.150 --> 00:13:28.160 align:start position:0% and you can actually filter them if you 00:13:28.160 --> 00:13:31.180 align:start position:0% and you can actually filter them if you want<00:13:28.340> to<00:13:28.460> can<00:13:28.670> filter<00:13:28.910> by<00:13:29.150> advanced<00:13:29.770> and<00:13:30.770> you 00:13:31.180 --> 00:13:31.190 align:start position:0% want to can filter by advanced and you 00:13:31.190 --> 00:13:34.720 align:start position:0% want to can filter by advanced and you can<00:13:31.340> also<00:13:31.520> debug<00:13:32.240> them<00:13:32.510> and<00:13:33.340> in<00:13:34.340> the<00:13:34.460> case<00:13:34.580> of 00:13:34.720 --> 00:13:34.730 align:start position:0% can also debug them and in the case of 00:13:34.730 --> 00:13:36.490 align:start position:0% can also debug them and in the case of debugger<00:13:35.030> so<00:13:35.360> it<00:13:35.540> will<00:13:35.750> show<00:13:35.780> you<00:13:36.050> the 00:13:36.490 --> 00:13:36.500 align:start position:0% debugger so it will show you the 00:13:36.500 --> 00:13:39.310 align:start position:0% debugger so it will show you the contract<00:13:36.980> I<00:13:37.280> will<00:13:38.120> join<00:13:38.300> the<00:13:38.420> contract<00:13:38.810> global 00:13:39.310 --> 00:13:39.320 align:start position:0% contract I will join the contract global 00:13:39.320 --> 00:13:40.690 align:start position:0% contract I will join the contract global variables<00:13:39.740> you'll<00:13:39.890> show<00:13:40.160> the<00:13:40.340> solidity 00:13:40.690 --> 00:13:40.700 align:start position:0% variables you'll show the solidity 00:13:40.700 --> 00:13:42.730 align:start position:0% variables you'll show the solidity variables<00:13:41.240> as<00:13:41.420> well<00:13:41.570> as<00:13:41.630> the<00:13:41.750> the<00:13:42.470> local 00:13:42.730 --> 00:13:42.740 align:start position:0% variables as well as the the local 00:13:42.740 --> 00:13:44.920 align:start position:0% variables as well as the the local variables<00:13:43.130> to<00:13:43.280> that<00:13:43.430> function<00:13:43.670> and<00:13:44.600> you<00:13:44.750> can 00:13:44.920 --> 00:13:44.930 align:start position:0% variables to that function and you can 00:13:44.930 --> 00:13:48.880 align:start position:0% variables to that function and you can step<00:13:45.230> through<00:13:45.470> it<00:13:45.650> step<00:13:46.100> in<00:13:46.570> breakpoints<00:13:47.890> the 00:13:48.880 --> 00:13:48.890 align:start position:0% step through it step in breakpoints the 00:13:48.890 --> 00:13:51.910 align:start position:0% step through it step in breakpoints the whole<00:13:49.040> thing<00:13:49.550> and<00:13:50.030> there's<00:13:50.750> also<00:13:50.870> a<00:13:51.020> browser 00:13:51.910 --> 00:13:51.920 align:start position:0% whole thing and there's also a browser 00:13:51.920 --> 00:13:55.150 align:start position:0% whole thing and there's also a browser preview<00:13:52.570> that<00:13:53.570> that<00:13:54.080> you<00:13:54.170> can<00:13:54.320> use<00:13:54.470> for<00:13:54.710> more 00:13:55.150 --> 00:13:55.160 align:start position:0% preview that that you can use for more 00:13:55.160 --> 00:13:58.900 align:start position:0% preview that that you can use for more quick<00:13:55.870> prototyping<00:13:56.870> so<00:13:57.200> a<00:13:57.230> good<00:13:57.710> algorithm<00:13:58.640> of 00:13:58.900 --> 00:13:58.910 align:start position:0% quick prototyping so a good algorithm of 00:13:58.910 --> 00:14:01.120 align:start position:0% quick prototyping so a good algorithm of a<00:13:59.270> good<00:13:59.570> workflow<00:14:00.230> in<00:14:00.350> this<00:14:00.500> would<00:14:00.710> be<00:14:00.860> for 00:14:01.120 --> 00:14:01.130 align:start position:0% a good workflow in this would be for 00:14:01.130 --> 00:14:03.580 align:start position:0% a good workflow in this would be for example<00:14:01.460> that<00:14:01.550> type<00:14:01.730> I<00:14:01.910> press<00:14:02.180> the<00:14:02.840> set<00:14:03.080> value 00:14:03.580 --> 00:14:03.590 align:start position:0% example that type I press the set value 00:14:03.590 --> 00:14:05.860 align:start position:0% example that type I press the set value I<00:14:03.890> seen<00:14:04.400> a<00:14:04.430> transaction<00:14:05.090> in<00:14:05.150> the<00:14:05.240> set<00:14:05.450> 1<00:14:05.630> and 00:14:05.860 --> 00:14:05.870 align:start position:0% I seen a transaction in the set 1 and 00:14:05.870 --> 00:14:09.250 align:start position:0% I seen a transaction in the set 1 and maybe<00:14:06.230> it<00:14:06.410> broke<00:14:06.680> I<00:14:07.210> press<00:14:08.210> debug<00:14:08.600> go<00:14:08.810> to<00:14:08.870> debug 00:14:09.250 --> 00:14:09.260 align:start position:0% maybe it broke I press debug go to debug 00:14:09.260 --> 00:14:12.310 align:start position:0% maybe it broke I press debug go to debug and<00:14:09.500> I<00:14:09.590> can<00:14:09.950> then<00:14:10.570> debug<00:14:11.570> the<00:14:11.840> contract<00:14:12.230> and 00:14:12.310 --> 00:14:12.320 align:start position:0% and I can then debug the contract and 00:14:12.320 --> 00:14:16.570 align:start position:0% and I can then debug the contract and see<00:14:12.500> and<00:14:12.770> see<00:14:12.920> what<00:14:13.100> went<00:14:13.310> wrong<00:14:13.900> and<00:14:15.400> we<00:14:16.400> also 00:14:16.570 --> 00:14:16.580 align:start position:0% see and see what went wrong and we also 00:14:16.580 --> 00:14:20.380 align:start position:0% see and see what went wrong and we also introducing<00:14:17.570> this<00:14:17.750> a<00:14:18.380> deployment<00:14:19.220> tool<00:14:19.490> so 00:14:20.380 --> 00:14:20.390 align:start position:0% introducing this a deployment tool so 00:14:20.390 --> 00:14:23.710 align:start position:0% introducing this a deployment tool so the<00:14:21.110> idea<00:14:21.350> here<00:14:21.440> is<00:14:21.710> that<00:14:21.950> we<00:14:22.450> from<00:14:23.450> speaking 00:14:23.710 --> 00:14:23.720 align:start position:0% the idea here is that we from speaking 00:14:23.720 --> 00:14:27.100 align:start position:0% the idea here is that we from speaking to<00:14:23.810> many<00:14:24.290> of<00:14:24.440> our<00:14:24.590> users<00:14:24.770> we<00:14:25.370> realized<00:14:25.940> that<00:14:26.110> a 00:14:27.100 --> 00:14:27.110 align:start position:0% to many of our users we realized that a 00:14:27.110 --> 00:14:30.550 align:start position:0% to many of our users we realized that a lot<00:14:27.980> of<00:14:28.100> people<00:14:28.280> actually<00:14:28.370> prefer<00:14:28.640> to<00:14:29.560> deploy 00:14:30.550 --> 00:14:30.560 align:start position:0% lot of people actually prefer to deploy 00:14:30.560 --> 00:14:33.930 align:start position:0% lot of people actually prefer to deploy directly<00:14:30.830> with<00:14:31.400> what<00:14:32.120> would<00:14:32.570> madam<00:14:32.780> ask 00:14:33.930 --> 00:14:33.940 align:start position:0% directly with what would madam ask 00:14:33.940 --> 00:14:36.070 align:start position:0% directly with what would madam ask typically<00:14:34.940> with<00:14:35.120> a<00:14:35.150> browser<00:14:35.420> idea<00:14:35.810> with<00:14:36.050> a 00:14:36.070 --> 00:14:36.080 align:start position:0% typically with a browser idea with a 00:14:36.080 --> 00:14:37.990 align:start position:0% typically with a browser idea with a browser<00:14:36.290> app<00:14:36.470> ID<00:14:36.710> and<00:14:36.740> then<00:14:37.190> deploy<00:14:37.790> to<00:14:37.910> a 00:14:37.990 --> 00:14:38.000 align:start position:0% browser app ID and then deploy to a 00:14:38.000 --> 00:14:40.060 align:start position:0% browser app ID and then deploy to a madam<00:14:38.240> ask<00:14:38.390> because<00:14:39.290> sometimes<00:14:39.920> they<00:14:39.980> don't 00:14:40.060 --> 00:14:40.070 align:start position:0% madam ask because sometimes they don't 00:14:40.070 --> 00:14:41.530 align:start position:0% madam ask because sometimes they don't feel<00:14:40.280> very<00:14:40.310> comfortable<00:14:40.670> deployment<00:14:41.450> from 00:14:41.530 --> 00:14:41.540 align:start position:0% feel very comfortable deployment from 00:14:41.540 --> 00:14:43.600 align:start position:0% feel very comfortable deployment from the<00:14:41.660> command<00:14:41.930> line<00:14:41.990> and<00:14:42.470> because<00:14:43.040> in<00:14:43.340> the<00:14:43.460> case 00:14:43.600 --> 00:14:43.610 align:start position:0% the command line and because in the case 00:14:43.610 --> 00:14:46.510 align:start position:0% the command line and because in the case of<00:14:43.670> more<00:14:44.360> advanced<00:14:45.230> tools<00:14:45.410> like<00:14:45.590> embark<00:14:45.950> it 00:14:46.510 --> 00:14:46.520 align:start position:0% of more advanced tools like embark it 00:14:46.520 --> 00:14:48.330 align:start position:0% of more advanced tools like embark it does<00:14:46.700> not<00:14:46.790> it<00:14:46.940> can<00:14:47.090> do<00:14:47.180> a<00:14:47.270> lot<00:14:47.420> of<00:14:47.450> deployments 00:14:48.330 --> 00:14:48.340 align:start position:0% does not it can do a lot of deployments 00:14:48.340 --> 00:14:51.820 align:start position:0% does not it can do a lot of deployments and<00:14:49.340> and<00:14:50.000> when<00:14:50.870> to<00:14:51.050> point<00:14:51.230> the<00:14:51.320> minute<00:14:51.650> people 00:14:51.820 --> 00:14:51.830 align:start position:0% and and when to point the minute people 00:14:51.830 --> 00:14:53.590 align:start position:0% and and when to point the minute people need<00:14:52.310> to<00:14:52.430> have<00:14:52.490> the<00:14:52.640> confidence<00:14:52.910> of<00:14:53.300> what's 00:14:53.590 --> 00:14:53.600 align:start position:0% need to have the confidence of what's 00:14:53.600 --> 00:14:56.350 align:start position:0% need to have the confidence of what's actually<00:14:53.780> happening<00:14:54.010> so<00:14:55.010> here<00:14:55.880> instead<00:14:56.120> in 00:14:56.350 --> 00:14:56.360 align:start position:0% actually happening so here instead in 00:14:56.360 --> 00:14:58.570 align:start position:0% actually happening so here instead in this<00:14:56.660> with<00:14:56.990> this<00:14:57.080> option<00:14:57.500> in<00:14:57.950> work<00:14:58.160> will<00:14:58.339> tell 00:14:58.570 --> 00:14:58.580 align:start position:0% this with this option in work will tell 00:14:58.580 --> 00:15:00.640 align:start position:0% this with this option in work will tell you<00:14:58.700> what<00:14:58.910> is<00:14:59.030> the<00:14:59.240> intended<00:14:59.780> deploy<00:15:00.260> order 00:15:00.640 --> 00:15:00.650 align:start position:0% you what is the intended deploy order 00:15:00.650 --> 00:15:03.370 align:start position:0% you what is the intended deploy order and<00:15:00.890> then<00:15:01.339> you<00:15:01.400> can<00:15:01.550> actually<00:15:01.670> deploy<00:15:02.380> semi 00:15:03.370 --> 00:15:03.380 align:start position:0% and then you can actually deploy semi 00:15:03.380 --> 00:15:06.280 align:start position:0% and then you can actually deploy semi manually<00:15:04.040> one<00:15:04.280> by<00:15:04.310> one<00:15:04.670> and<00:15:04.990> each<00:15:05.990> time<00:15:06.260> you 00:15:06.280 --> 00:15:06.290 align:start position:0% manually one by one and each time you 00:15:06.290 --> 00:15:07.510 align:start position:0% manually one by one and each time you deploy<00:15:06.560> contract<00:15:06.950> manually<00:15:07.339> you<00:15:07.490> can 00:15:07.510 --> 00:15:07.520 align:start position:0% deploy contract manually you can 00:15:07.520 --> 00:15:09.790 align:start position:0% deploy contract manually you can interact<00:15:08.150> with<00:15:08.420> that<00:15:08.570> see<00:15:09.200> where<00:15:09.410> everything 00:15:09.790 --> 00:15:09.800 align:start position:0% interact with that see where everything 00:15:09.800 --> 00:15:11.650 align:start position:0% interact with that see where everything is<00:15:09.890> okay<00:15:10.190> and<00:15:10.220> then<00:15:10.460> you<00:15:10.580> can<00:15:10.610> move<00:15:10.940> to<00:15:11.000> the<00:15:11.210> to 00:15:11.650 --> 00:15:11.660 align:start position:0% is okay and then you can move to the to 00:15:11.660 --> 00:15:16.690 align:start position:0% is okay and then you can move to the to the<00:15:11.960> next<00:15:12.230> contract<00:15:13.690> so<00:15:14.690> you<00:15:15.310> can<00:15:16.310> get<00:15:16.490> more 00:15:16.690 --> 00:15:16.700 align:start position:0% the next contract so you can get more 00:15:16.700 --> 00:15:18.400 align:start position:0% the next contract so you can get more info<00:15:16.970> in<00:15:17.150> the<00:15:17.330> in<00:15:17.510> the<00:15:17.630> barque<00:15:17.839> where<00:15:18.020> in<00:15:18.200> the 00:15:18.400 --> 00:15:18.410 align:start position:0% info in the in the barque where in the 00:15:18.410 --> 00:15:20.790 align:start position:0% info in the in the barque where in the embark<00:15:18.710> website<00:15:19.130> status<00:15:20.030> as<00:15:20.150> I<00:15:20.270> am 00:15:20.790 --> 00:15:20.800 align:start position:0% embark website status as I am 00:15:20.800 --> 00:15:24.700 align:start position:0% embark website status as I am it<00:15:21.800> will<00:15:22.100> it's<00:15:22.400> now<00:15:22.580> available<00:15:22.820> as<00:15:23.240> alpha<00:15:23.900> it's 00:15:24.700 --> 00:15:24.710 align:start position:0% it will it's now available as alpha it's 00:15:24.710 --> 00:15:29.620 align:start position:0% it will it's now available as alpha it's the<00:15:24.860> one<00:15:25.010> alpha<00:15:25.490> stage<00:15:25.760> so<00:15:26.330> be<00:15:26.870> careful<00:15:27.340> and<00:15:28.630> we 00:15:29.620 --> 00:15:29.630 align:start position:0% the one alpha stage so be careful and we 00:15:29.630 --> 00:15:31.300 align:start position:0% the one alpha stage so be careful and we all<00:15:29.750> we<00:15:30.230> also<00:15:30.380> intended<00:15:30.830> to<00:15:30.890> make<00:15:31.160> it 00:15:31.300 --> 00:15:31.310 align:start position:0% all we also intended to make it 00:15:31.310 --> 00:15:34.510 align:start position:0% all we also intended to make it available<00:15:31.580> as<00:15:31.940> a<00:15:32.390> pure<00:15:32.720> web<00:15:33.110> application<00:15:33.830> if 00:15:34.510 --> 00:15:34.520 align:start position:0% available as a pure web application if 00:15:34.520 --> 00:15:35.950 align:start position:0% available as a pure web application if you're<00:15:34.700> interested<00:15:35.090> in<00:15:35.180> that<00:15:35.300> you<00:15:35.600> can<00:15:35.720> go<00:15:35.870> to 00:15:35.950 --> 00:15:35.960 align:start position:0% you're interested in that you can go to 00:15:35.960 --> 00:15:37.600 align:start position:0% you're interested in that you can go to the<00:15:36.050> embark<00:15:36.290> website<00:15:36.650> and<00:15:36.890> sign<00:15:37.130> up<00:15:37.280> in<00:15:37.430> the 00:15:37.600 --> 00:15:37.610 align:start position:0% the embark website and sign up in the 00:15:37.610 --> 00:15:40.450 align:start position:0% the embark website and sign up in the m'ling<00:15:38.480> list<00:15:38.660> and<00:15:38.900> you<00:15:38.990> will<00:15:39.110> get<00:15:39.290> an<00:15:40.040> invite 00:15:40.450 --> 00:15:40.460 align:start position:0% m'ling list and you will get an invite 00:15:40.460 --> 00:15:43.240 align:start position:0% m'ling list and you will get an invite and<00:15:40.990> I<00:15:41.990> just<00:15:42.290> want<00:15:42.410> to<00:15:42.470> thank<00:15:42.590> them<00:15:42.830> for<00:15:43.040> the 00:15:43.240 --> 00:15:43.250 align:start position:0% and I just want to thank them for the 00:15:43.250 --> 00:15:45.280 align:start position:0% and I just want to thank them for the embark<00:15:43.520> team<00:15:43.730> and<00:15:44.060> all<00:15:44.480> our<00:15:44.690> contributors 00:15:45.280 --> 00:15:45.290 align:start position:0% embark team and all our contributors 00:15:45.290 --> 00:15:47.530 align:start position:0% embark team and all our contributors that<00:15:45.320> made<00:15:45.710> all<00:15:46.460> of<00:15:46.520> this<00:15:46.760> all<00:15:47.360> of<00:15:47.420> this 00:15:47.530 --> 00:15:47.540 align:start position:0% that made all of this all of this 00:15:47.540 --> 00:15:54.900 align:start position:0% that made all of this all of this possible<00:15:48.080> and<00:15:49.930> thank<00:15:50.930> you 00:15:54.900 --> 00:15:54.910 align:start position:0% 00:15:54.910 --> 00:15:57.340 align:start position:0% debugger<00:15:55.910> like<00:15:56.180> the<00:15:56.270> visual<00:15:56.570> debugger<00:15:57.110> are 00:15:57.340 --> 00:15:57.350 align:start position:0% debugger like the visual debugger are 00:15:57.350 --> 00:15:59.830 align:start position:0% debugger like the visual debugger are you<00:15:57.530> using<00:15:58.130> are<00:15:58.610> you<00:15:58.850> leveraging<00:15:59.000> remix<00:15:59.690> for 00:15:59.830 --> 00:15:59.840 align:start position:0% you using are you leveraging remix for 00:15:59.840 --> 00:16:03.490 align:start position:0% you using are you leveraging remix for that<00:15:59.990> yep<00:16:00.410> we're<00:16:00.830> using<00:16:00.980> remix<00:16:02.290> reusing<00:16:03.290> most 00:16:03.490 --> 00:16:03.500 align:start position:0% that yep we're using remix reusing most 00:16:03.500 --> 00:16:07.420 align:start position:0% that yep we're using remix reusing most of<00:16:03.650> that<00:16:03.850> library<00:16:04.850> from<00:16:05.180> remix<00:16:05.600> yes<00:16:06.320> so<00:16:06.620> remix 00:16:07.420 --> 00:16:07.430 align:start position:0% of that library from remix yes so remix 00:16:07.430 --> 00:16:12.850 align:start position:0% of that library from remix yes so remix it's<00:16:08.360> being<00:16:08.780> basically<00:16:10.360> refactoring<00:16:11.360> into<00:16:11.860> an 00:16:12.850 --> 00:16:12.860 align:start position:0% it's being basically refactoring into an 00:16:12.860 --> 00:16:15.370 align:start position:0% it's being basically refactoring into an API<00:16:13.190> that<00:16:13.310> you<00:16:13.610> can<00:16:13.670> use<00:16:13.870> an<00:16:14.870> embark<00:16:15.230> is 00:16:15.370 --> 00:16:15.380 align:start position:0% API that you can use an embark is 00:16:15.380 --> 00:16:18.010 align:start position:0% API that you can use an embark is leverage<00:16:15.740> and<00:16:15.890> leveraging<00:16:16.400> that<00:16:16.550> so<00:16:17.300> it<00:16:17.780> has<00:16:17.810> a 00:16:18.010 --> 00:16:18.020 align:start position:0% leverage and leveraging that so it has a 00:16:18.020 --> 00:16:20.160 align:start position:0% leverage and leveraging that so it has a pretty<00:16:18.860> much<00:16:19.070> the<00:16:19.160> same<00:16:19.280> functionality<00:16:19.700> as 00:16:20.160 --> 00:16:20.170 align:start position:0% pretty much the same functionality as 00:16:20.170 --> 00:16:25.180 align:start position:0% pretty much the same functionality as remix<00:16:21.170> I<00:16:21.460> thinks<00:16:22.460> hi<00:16:23.500> so<00:16:24.500> I<00:16:24.560> understood<00:16:25.070> that 00:16:25.180 --> 00:16:25.190 align:start position:0% remix I thinks hi so I understood that 00:16:25.190 --> 00:16:29.350 align:start position:0% remix I thinks hi so I understood that you<00:16:25.370> provide<00:16:26.440> like<00:16:27.440> a<00:16:27.470> testing<00:16:28.280> framework<00:16:28.400> for 00:16:29.350 --> 00:16:29.360 align:start position:0% you provide like a testing framework for 00:16:29.360 --> 00:16:33.700 align:start position:0% you provide like a testing framework for off<00:16:29.690> train<00:16:30.460> code<00:16:31.460> doesn't<00:16:31.820> work<00:16:31.940> for<00:16:32.680> mmm 00:16:33.700 --> 00:16:33.710 align:start position:0% off train code doesn't work for mmm 00:16:33.710 --> 00:16:36.970 align:start position:0% off train code doesn't work for mmm solidity<00:16:34.250> contracts<00:16:34.730> to<00:16:34.910> and<00:16:35.770> as<00:16:36.770> an 00:16:36.970 --> 00:16:36.980 align:start position:0% solidity contracts to and as an 00:16:36.980 --> 00:16:39.430 align:start position:0% solidity contracts to and as an alternative<00:16:37.400> do<00:16:37.610> you<00:16:37.730> integrate<00:16:38.210> truffle<00:16:39.020> or 00:16:39.430 --> 00:16:39.440 align:start position:0% alternative do you integrate truffle or 00:16:39.440 --> 00:16:40.990 align:start position:0% alternative do you integrate truffle or I<00:16:39.500> mean<00:16:39.920> the<00:16:40.040> whole<00:16:40.160> suite<00:16:40.370> you<00:16:40.520> know<00:16:40.610> truffle 00:16:40.990 --> 00:16:41.000 align:start position:0% I mean the whole suite you know truffle 00:16:41.000 --> 00:16:44.230 align:start position:0% I mean the whole suite you know truffle drizzle<00:16:41.390> and<00:16:41.540> and<00:16:42.700> what's<00:16:43.700> it<00:16:43.790> called 00:16:44.230 --> 00:16:44.240 align:start position:0% drizzle and and what's it called 00:16:44.240 --> 00:16:49.030 align:start position:0% drizzle and and what's it called ganache<00:16:44.600> thank<00:16:45.260> you<00:16:47.440> can<00:16:48.440> you<00:16:48.530> be<00:16:48.710> the<00:16:48.830> first 00:16:49.030 --> 00:16:49.040 align:start position:0% ganache thank you can you be the first 00:16:49.040 --> 00:16:52.510 align:start position:0% ganache thank you can you be the first question<00:16:50.260> yeah<00:16:51.260> you<00:16:51.560> you<00:16:51.920> in<00:16:52.190> your 00:16:52.510 --> 00:16:52.520 align:start position:0% question yeah you you in your 00:16:52.520 --> 00:16:57.160 align:start position:0% question yeah you you in your presentation<00:16:53.090> you<00:16:53.240> show<00:16:53.540> you<00:16:54.260> showed<00:16:55.720> I<00:16:56.720> mean 00:16:57.160 --> 00:16:57.170 align:start position:0% presentation you show you showed I mean 00:16:57.170 --> 00:16:58.480 align:start position:0% presentation you show you showed I mean apparently<00:16:57.380> you<00:16:57.680> can<00:16:57.830> write<00:16:57.980> tests<00:16:58.220> with 00:16:58.480 --> 00:16:58.490 align:start position:0% apparently you can write tests with 00:16:58.490 --> 00:17:01.030 align:start position:0% apparently you can write tests with embark<00:16:58.880> right<00:16:59.690> what<00:17:00.320> are<00:17:00.380> you<00:17:00.470> test<00:17:00.680> exactly 00:17:01.030 --> 00:17:01.040 align:start position:0% embark right what are you test exactly 00:17:01.040 --> 00:17:03.160 align:start position:0% embark right what are you test exactly do<00:17:01.280> you<00:17:01.370> test<00:17:01.550> the<00:17:02.030> smart<00:17:02.270> contract<00:17:02.660> code<00:17:02.840> or 00:17:03.160 --> 00:17:03.170 align:start position:0% do you test the smart contract code or 00:17:03.170 --> 00:17:05.830 align:start position:0% do you test the smart contract code or you<00:17:03.290> test<00:17:03.560> the<00:17:03.920> off<00:17:04.400> train<00:17:04.760> code<00:17:04.970> so<00:17:05.480> that's<00:17:05.630> my 00:17:05.830 --> 00:17:05.840 align:start position:0% you test the off train code so that's my 00:17:05.840 --> 00:17:08.260 align:start position:0% you test the off train code so that's my first<00:17:06.020> question<00:17:06.140> and<00:17:06.950> if<00:17:07.400> it<00:17:07.520> works<00:17:07.760> for<00:17:08.060> both 00:17:08.260 --> 00:17:08.270 align:start position:0% first question and if it works for both 00:17:08.270 --> 00:17:11.620 align:start position:0% first question and if it works for both and<00:17:08.780> if<00:17:09.620> not<00:17:09.800> do<00:17:10.160> you<00:17:10.310> for<00:17:10.850> for<00:17:11.030> testing<00:17:11.360> smart 00:17:11.620 --> 00:17:11.630 align:start position:0% and if not do you for for testing smart 00:17:11.630 --> 00:17:14.760 align:start position:0% and if not do you for for testing smart contract<00:17:11.960> code<00:17:12.140> do<00:17:12.320> you<00:17:12.470> integrate<00:17:13.160> truffle 00:17:14.760 --> 00:17:14.770 align:start position:0% contract code do you integrate truffle 00:17:14.770 --> 00:17:20.320 align:start position:0% contract code do you integrate truffle right<00:17:17.440> so<00:17:18.440> it's<00:17:18.710> a<00:17:18.920> smart<00:17:19.430> contracts<00:17:19.940> it 00:17:20.320 --> 00:17:20.330 align:start position:0% right so it's a smart contracts it 00:17:20.330 --> 00:17:22.960 align:start position:0% right so it's a smart contracts it doesn't<00:17:20.630> mean<00:17:20.720> focus<00:17:21.400> its<00:17:22.400> actual<00:17:22.700> support 00:17:22.960 --> 00:17:22.970 align:start position:0% doesn't mean focus its actual support 00:17:22.970 --> 00:17:27.130 align:start position:0% doesn't mean focus its actual support solidity<00:17:23.830> tests<00:17:25.840> truffle<00:17:26.840> is<00:17:26.960> like<00:17:27.110> a 00:17:27.130 --> 00:17:27.140 align:start position:0% solidity tests truffle is like a 00:17:27.140 --> 00:17:29.860 align:start position:0% solidity tests truffle is like a different<00:17:27.710> framework<00:17:28.460> and<00:17:28.760> it<00:17:28.970> does<00:17:29.240> what 00:17:29.860 --> 00:17:29.870 align:start position:0% different framework and it does what 00:17:29.870 --> 00:17:31.780 align:start position:0% different framework and it does what Moore's<00:17:30.080> a<00:17:30.500> sub 00:17:31.780 --> 00:17:31.790 align:start position:0% Moore's a sub 00:17:31.790 --> 00:17:33.460 align:start position:0% Moore's a sub it<00:17:32.090> does<00:17:32.270> like<00:17:32.390> it<00:17:32.510> specifically<00:17:33.080> just<00:17:33.260> for 00:17:33.460 --> 00:17:33.470 align:start position:0% it does like it specifically just for 00:17:33.470 --> 00:17:35.350 align:start position:0% it does like it specifically just for the<00:17:33.560> smart<00:17:33.800> contracts<00:17:34.220> well<00:17:34.850> this<00:17:35.030> does<00:17:35.240> the 00:17:35.350 --> 00:17:35.360 align:start position:0% the smart contracts well this does the 00:17:35.360 --> 00:17:37.930 align:start position:0% the smart contracts well this does the smart<00:17:35.630> contract<00:17:36.050> so<00:17:36.200> it<00:17:36.290> is<00:17:36.410> what<00:17:37.310> do<00:17:37.370> you<00:17:37.460> you 00:17:37.930 --> 00:17:37.940 align:start position:0% smart contract so it is what do you you 00:17:37.940 --> 00:17:40.030 align:start position:0% smart contract so it is what do you you were<00:17:38.060> describing<00:17:38.390> like<00:17:38.570> truffle<00:17:38.960> does<00:17:39.140> but<00:17:39.920> it 00:17:40.030 --> 00:17:40.040 align:start position:0% were describing like truffle does but it 00:17:40.040 --> 00:17:42.070 align:start position:0% were describing like truffle does but it also<00:17:40.190> focuses<00:17:40.700> on<00:17:41.120> the<00:17:41.510> other<00:17:41.720> other 00:17:42.070 --> 00:17:42.080 align:start position:0% also focuses on the other other 00:17:42.080 --> 00:17:45.240 align:start position:0% also focuses on the other other component<00:17:42.770> and<00:17:43.160> drizzle<00:17:44.000> I<00:17:44.150> assume<00:17:44.420> that's 00:17:45.240 --> 00:17:45.250 align:start position:0% component and drizzle I assume that's 00:17:45.250 --> 00:17:47.410 align:start position:0% component and drizzle I assume that's independent<00:17:46.250> of<00:17:46.280> truffle<00:17:46.700> so<00:17:46.910> in<00:17:47.060> that<00:17:47.180> case 00:17:47.410 --> 00:17:47.420 align:start position:0% independent of truffle so in that case 00:17:47.420 --> 00:17:50.380 align:start position:0% independent of truffle so in that case which<00:17:47.750> it<00:17:48.140> should<00:17:48.440> should<00:17:49.160> work<00:17:49.340> get<00:17:50.270> one 00:17:50.380 --> 00:17:50.390 align:start position:0% which it should should work get one 00:17:50.390 --> 00:17:53.050 align:start position:0% which it should should work get one right<00:17:50.540> here<00:17:51.910> okay 00:17:53.050 --> 00:17:53.060 align:start position:0% right here okay 00:17:53.060 --> 00:17:55.630 align:start position:0% right here okay so<00:17:53.620> when<00:17:54.620> you<00:17:54.770> are<00:17:54.950> showing<00:17:55.250> the 00:17:55.630 --> 00:17:55.640 align:start position:0% so when you are showing the 00:17:55.640 --> 00:17:58.120 align:start position:0% so when you are showing the configuration<00:17:56.390> we<00:17:56.990> are<00:17:57.020> showing<00:17:57.290> some<00:17:57.440> kind 00:17:58.120 --> 00:17:58.130 align:start position:0% configuration we are showing some kind 00:17:58.130 --> 00:18:02.020 align:start position:0% configuration we are showing some kind of<00:17:58.250> hooks<00:17:58.490> in<00:17:58.790> this<00:17:59.950> javascript<00:18:00.950> object<00:18:01.340> like 00:18:02.020 --> 00:18:02.030 align:start position:0% of hooks in this javascript object like 00:18:02.030 --> 00:18:04.330 align:start position:0% of hooks in this javascript object like on<00:18:02.300> deploy<00:18:02.750> and<00:18:03.080> the<00:18:03.260> string<00:18:03.620> representing 00:18:04.330 --> 00:18:04.340 align:start position:0% on deploy and the string representing 00:18:04.340 --> 00:18:07.030 align:start position:0% on deploy and the string representing the<00:18:04.550> code<00:18:04.940> that<00:18:05.270> it's<00:18:05.510> gonna<00:18:05.750> be<00:18:05.990> evaluated<00:18:06.590> my 00:18:07.030 --> 00:18:07.040 align:start position:0% the code that it's gonna be evaluated my 00:18:07.040 --> 00:18:09.250 align:start position:0% the code that it's gonna be evaluated my question<00:18:07.400> is<00:18:07.490> why<00:18:07.700> don't<00:18:08.540> you<00:18:08.780> just<00:18:09.050> use 00:18:09.250 --> 00:18:09.260 align:start position:0% question is why don't you just use 00:18:09.260 --> 00:18:11.380 align:start position:0% question is why don't you just use anonymous<00:18:09.800> function<00:18:10.250> with<00:18:10.790> you<00:18:11.000> know<00:18:11.120> some 00:18:11.380 --> 00:18:11.390 align:start position:0% anonymous function with you know some 00:18:11.390 --> 00:18:14.620 align:start position:0% anonymous function with you know some arguments<00:18:11.960> and<00:18:12.760> like<00:18:13.760> here<00:18:14.120> you're<00:18:14.330> doing 00:18:14.620 --> 00:18:14.630 align:start position:0% arguments and like here you're doing 00:18:14.630 --> 00:18:17.050 align:start position:0% arguments and like here you're doing like<00:18:15.080> angular<00:18:15.470> one<00:18:15.830> style<00:18:16.310> like<00:18:16.610> with<00:18:16.850> this 00:18:17.050 --> 00:18:17.060 align:start position:0% like angular one style like with this 00:18:17.060 --> 00:18:19.980 align:start position:0% like angular one style like with this funny<00:18:17.330> syntax 00:18:19.980 --> 00:18:19.990 align:start position:0% funny syntax 00:18:19.990 --> 00:18:22.450 align:start position:0% funny syntax so<00:18:20.990> I<00:18:21.020> took<00:18:21.290> I<00:18:21.590> took<00:18:21.620> like<00:18:21.920> a<00:18:21.950> real 00:18:22.450 --> 00:18:22.460 align:start position:0% so I took I took like a real 00:18:22.460 --> 00:18:24.880 align:start position:0% so I took I took like a real configuration<00:18:23.210> and<00:18:23.480> then<00:18:24.290> I<00:18:24.470> said<00:18:24.650> okay 00:18:24.880 --> 00:18:24.890 align:start position:0% configuration and then I said okay 00:18:24.890 --> 00:18:26.230 align:start position:0% configuration and then I said okay what's<00:18:25.190> missing<00:18:25.550> here<00:18:25.820> that<00:18:26.000> could<00:18:26.120> be 00:18:26.230 --> 00:18:26.240 align:start position:0% what's missing here that could be 00:18:26.240 --> 00:18:28.390 align:start position:0% what's missing here that could be educational<00:18:26.780> and<00:18:26.990> I<00:18:27.080> added<00:18:27.260> I<00:18:27.590> I<00:18:27.950> didn't 00:18:28.390 --> 00:18:28.400 align:start position:0% educational and I added I I didn't 00:18:28.400 --> 00:18:30.430 align:start position:0% educational and I added I I didn't really<00:18:28.550> talk<00:18:28.700> about<00:18:28.760> anything<00:18:29.240> about<00:18:29.690> you 00:18:30.430 --> 00:18:30.440 align:start position:0% really talk about anything about you 00:18:30.440 --> 00:18:32.470 align:start position:0% really talk about anything about you know<00:18:30.470> that<00:18:31.160> type<00:18:31.310> of<00:18:31.340> starter<00:18:31.730> gold<00:18:31.940> if 00:18:32.470 --> 00:18:32.480 align:start position:0% know that type of starter gold if 00:18:32.480 --> 00:18:34.360 align:start position:0% know that type of starter gold if anything<00:18:32.960> probably<00:18:33.350> confuse<00:18:33.830> people<00:18:33.980> more 00:18:34.360 --> 00:18:34.370 align:start position:0% anything probably confuse people more 00:18:34.370 --> 00:18:37.770 align:start position:0% anything probably confuse people more and<00:18:35.330> it<00:18:35.420> was<00:18:35.510> already<00:18:35.660> a<00:18:35.810> big<00:18:35.870> config<00:18:36.380> file<00:18:36.590> so 00:18:37.770 --> 00:18:37.780 align:start position:0% and it was already a big config file so 00:18:37.780 --> 00:18:39.970 align:start position:0% and it was already a big config file so to<00:18:38.780> answer<00:18:38.900> your<00:18:38.990> question<00:18:39.140> for<00:18:39.470> educational 00:18:39.970 --> 00:18:39.980 align:start position:0% to answer your question for educational 00:18:39.980 --> 00:18:48.460 align:start position:0% to answer your question for educational purposes<00:18:40.430> that's<00:18:41.420> the<00:18:41.630> test<00:18:41.960> answers<00:18:45.940> hi<00:18:47.320> as<00:18:48.320> a 00:18:48.460 --> 00:18:48.470 align:start position:0% purposes that's the test answers hi as a 00:18:48.470 --> 00:18:51.160 align:start position:0% purposes that's the test answers hi as a long<00:18:48.710> time<00:18:49.240> truffle<00:18:50.240> and<00:18:50.360> embark<00:18:50.840> user 00:18:51.160 --> 00:18:51.170 align:start position:0% long time truffle and embark user 00:18:51.170 --> 00:18:53.530 align:start position:0% long time truffle and embark user I've<00:18:51.470> been<00:18:51.710> waiting<00:18:52.460> anxiously<00:18:52.580> to<00:18:53.120> see<00:18:53.150> which 00:18:53.530 --> 00:18:53.540 align:start position:0% I've been waiting anxiously to see which 00:18:53.540 --> 00:18:56.140 align:start position:0% I've been waiting anxiously to see which framework<00:18:54.020> actually<00:18:54.380> which<00:18:54.830> JavaScript<00:18:55.610> kind 00:18:56.140 --> 00:18:56.150 align:start position:0% framework actually which JavaScript kind 00:18:56.150 --> 00:18:58.540 align:start position:0% framework actually which JavaScript kind of<00:18:56.270> version<00:18:57.050> of<00:18:57.170> the<00:18:57.410> blockchain<00:18:57.920> some 00:18:58.540 --> 00:18:58.550 align:start position:0% of version of the blockchain some 00:18:58.550 --> 00:19:02.380 align:start position:0% of version of the blockchain some ganache<00:18:59.000> or<00:19:00.130> whatever<00:19:01.130> embark<00:19:01.520> powers<00:19:01.910> up<00:19:02.090> is 00:19:02.380 --> 00:19:02.390 align:start position:0% ganache or whatever embark powers up is 00:19:02.390 --> 00:19:05.850 align:start position:0% ganache or whatever embark powers up is going<00:19:02.750> to<00:19:02.840> support<00:19:03.260> default<00:19:03.830> event<00:19:04.040> reading 00:19:05.850 --> 00:19:05.860 align:start position:0% going to support default event reading 00:19:05.860 --> 00:19:08.170 align:start position:0% going to support default event reading like<00:19:06.860> when<00:19:07.040> they<00:19:07.130> happen<00:19:07.490> in<00:19:07.610> contracts 00:19:08.170 --> 00:19:08.180 align:start position:0% like when they happen in contracts 00:19:08.180 --> 00:19:09.670 align:start position:0% like when they happen in contracts without<00:19:08.420> having<00:19:08.690> to<00:19:08.780> subscribe<00:19:09.170> to<00:19:09.290> them<00:19:09.440> so 00:19:09.670 --> 00:19:09.680 align:start position:0% without having to subscribe to them so 00:19:09.680 --> 00:19:12.880 align:start position:0% without having to subscribe to them so are<00:19:10.370> there<00:19:10.580> any<00:19:10.670> plans<00:19:10.880> to<00:19:11.240> have<00:19:11.390> can't<00:19:12.380> to 00:19:12.880 --> 00:19:12.890 align:start position:0% are there any plans to have can't to 00:19:12.890 --> 00:19:15.100 align:start position:0% are there any plans to have can't to have<00:19:13.010> events<00:19:13.520> tracked<00:19:13.850> by<00:19:14.120> default<00:19:14.480> from<00:19:14.840> your 00:19:15.100 --> 00:19:15.110 align:start position:0% have events tracked by default from your 00:19:15.110 --> 00:19:17.500 align:start position:0% have events tracked by default from your smart<00:19:15.560> contracts<00:19:16.070> and<00:19:16.280> shown<00:19:16.580> in<00:19:16.610> the<00:19:17.060> block 00:19:17.500 --> 00:19:17.510 align:start position:0% smart contracts and shown in the block 00:19:17.510 --> 00:19:21.700 align:start position:0% smart contracts and shown in the block Explorer<00:19:19.000> so<00:19:20.000> you<00:19:20.060> mean<00:19:20.450> actual<00:19:20.810> in<00:19:21.140> facility 00:19:21.700 --> 00:19:21.710 align:start position:0% Explorer so you mean actual in facility 00:19:21.710 --> 00:19:23.050 align:start position:0% Explorer so you mean actual in facility the<00:19:21.830> events<00:19:22.100> you<00:19:22.190> don't<00:19:22.370> mean<00:19:22.490> like<00:19:22.640> just<00:19:22.940> the 00:19:23.050 --> 00:19:23.060 align:start position:0% the events you don't mean like just the 00:19:23.060 --> 00:19:25.120 align:start position:0% the events you don't mean like just the transactions<00:19:23.600> no<00:19:23.930> not<00:19:24.110> just<00:19:24.320> actual<00:19:24.770> events 00:19:25.120 --> 00:19:25.130 align:start position:0% transactions no not just actual events 00:19:25.130 --> 00:19:26.560 align:start position:0% transactions no not just actual events from<00:19:25.310> the<00:19:25.490> code<00:19:25.640> without<00:19:26.090> having<00:19:26.480> to 00:19:26.560 --> 00:19:26.570 align:start position:0% from the code without having to 00:19:26.570 --> 00:19:30.970 align:start position:0% from the code without having to subscribe<00:19:27.020> individually<00:19:29.290> I'll<00:19:30.290> think<00:19:30.890> about 00:19:30.970 --> 00:19:30.980 align:start position:0% subscribe individually I'll think about 00:19:30.980 --> 00:19:34.690 align:start position:0% subscribe individually I'll think about it<00:19:31.160> because<00:19:31.400> I<00:19:32.140> feel<00:19:33.140> there's<00:19:33.320> some<00:19:33.700> downsides 00:19:34.690 --> 00:19:34.700 align:start position:0% it because I feel there's some downsides 00:19:34.700 --> 00:19:36.370 align:start position:0% it because I feel there's some downsides to<00:19:34.880> it<00:19:35.000> but<00:19:35.180> I<00:19:35.210> know<00:19:35.330> they're<00:19:35.600> this<00:19:35.900> is<00:19:35.960> coming 00:19:36.370 --> 00:19:36.380 align:start position:0% to it but I know they're this is coming 00:19:36.380 --> 00:19:38.470 align:start position:0% to it but I know they're this is coming in<00:19:36.440> the<00:19:36.530> next<00:19:36.560> version<00:19:36.890> of<00:19:37.100> ganache<00:19:37.610> right<00:19:38.330> and 00:19:38.470 --> 00:19:38.480 align:start position:0% in the next version of ganache right and 00:19:38.480 --> 00:19:42.370 align:start position:0% in the next version of ganache right and I<00:19:38.570> really<00:19:38.870> hope<00:19:39.050> you<00:19:39.230> guys<00:19:39.410> beat<00:19:40.070> them<00:19:40.250> to<00:19:40.400> it 00:19:42.370 --> 00:19:42.380 align:start position:0% I really hope you guys beat them to it 00:19:42.380 --> 00:19:44.930 align:start position:0% I really hope you guys beat them to it yeah<00:19:43.380> yeah<00:19:43.590> that's<00:19:43.860> exactly<00:19:44.580> what<00:19:44.700> this<00:19:44.790> thing 00:19:44.930 --> 00:19:44.940 align:start position:0% yeah yeah that's exactly what this thing 00:19:44.940 --> 00:19:47.060 align:start position:0% yeah yeah that's exactly what this thing yeah<00:19:45.330> cuz<00:19:45.660> we<00:19:45.960> do<00:19:46.080> have<00:19:46.200> the<00:19:46.350> logger<00:19:46.590> that<00:19:46.710> you 00:19:47.060 --> 00:19:47.070 align:start position:0% yeah cuz we do have the logger that you 00:19:47.070 --> 00:19:50.630 align:start position:0% yeah cuz we do have the logger that you can<00:19:47.250> see<00:19:47.460> the<00:19:48.180> state<00:19:48.450> so<00:19:49.110> doing<00:19:49.500> that<00:19:49.680> it<00:19:50.430> looks 00:19:50.630 --> 00:19:50.640 align:start position:0% can see the state so doing that it looks 00:19:50.640 --> 00:19:52.100 align:start position:0% can see the state so doing that it looks fairly<00:19:51.120> trivial<00:19:51.540> unless<00:19:51.870> some 00:19:52.100 --> 00:19:52.110 align:start position:0% fairly trivial unless some 00:19:52.110 --> 00:19:54.620 align:start position:0% fairly trivial unless some misunderstanding<00:19:52.920> song<00:19:53.100> but<00:19:53.280> yeah<00:19:53.820> we<00:19:54.030> would 00:19:54.620 --> 00:19:54.630 align:start position:0% misunderstanding song but yeah we would 00:19:54.630 --> 00:19:57.440 align:start position:0% misunderstanding song but yeah we would so<00:19:54.780> I<00:19:54.810> didn't<00:19:55.410> show<00:19:55.500> really<00:19:55.740> the<00:19:55.770> the<00:19:56.450> the 00:19:57.440 --> 00:19:57.450 align:start position:0% so I didn't show really the the the 00:19:57.450 --> 00:19:59.630 align:start position:0% so I didn't show really the the the Explorer<00:19:57.750> for<00:19:57.960> the<00:19:58.080> contracts<00:19:58.830> and<00:19:59.220> you<00:19:59.250> can 00:19:59.630 --> 00:19:59.640 align:start position:0% Explorer for the contracts and you can 00:19:59.640 --> 00:20:02.030 align:start position:0% Explorer for the contracts and you can you<00:20:00.360> can<00:20:00.540> choose<00:20:00.720> your<00:20:00.840> contract<00:20:01.320> a<00:20:01.470> candy<00:20:01.710> and 00:20:02.030 --> 00:20:02.040 align:start position:0% you can choose your contract a candy and 00:20:02.040 --> 00:20:04.280 align:start position:0% you can choose your contract a candy and yeah<00:20:02.940> you<00:20:03.030> can<00:20:03.120> interact<00:20:03.540> with<00:20:03.720> it<00:20:03.840> but<00:20:03.990> adding 00:20:04.280 --> 00:20:04.290 align:start position:0% yeah you can interact with it but adding 00:20:04.290 --> 00:20:05.960 align:start position:0% yeah you can interact with it but adding this<00:20:04.440> we<00:20:04.650> could<00:20:04.830> also<00:20:05.040> add<00:20:05.280> this<00:20:05.490> state<00:20:05.730> to<00:20:05.850> it 00:20:05.960 --> 00:20:05.970 align:start position:0% this we could also add this state to it 00:20:05.970 --> 00:20:08.390 align:start position:0% this we could also add this state to it so<00:20:06.690> I<00:20:06.720> think<00:20:07.020> it's<00:20:07.230> a<00:20:07.260> good<00:20:07.410> good<00:20:07.770> suggestion 00:20:08.390 --> 00:20:08.400 align:start position:0% so I think it's a good good suggestion 00:20:08.400 --> 00:20:12.860 align:start position:0% so I think it's a good good suggestion so<00:20:09.030> you<00:20:09.480> support<00:20:09.930> en<00:20:10.920> su<00:20:11.160> support<00:20:11.850> ipfs<00:20:12.660> are 00:20:12.860 --> 00:20:12.870 align:start position:0% so you support en su support ipfs are 00:20:12.870 --> 00:20:14.050 align:start position:0% so you support en su support ipfs are you<00:20:12.960> going<00:20:13.200> to<00:20:13.320> support 00:20:14.050 --> 00:20:14.060 align:start position:0% you going to support 00:20:14.060 --> 00:20:18.620 align:start position:0% you going to support APNs<00:20:15.470> we<00:20:16.470> actually<00:20:16.770> do<00:20:17.190> support<00:20:17.640> Alpena's<00:20:18.390> I 00:20:18.620 --> 00:20:18.630 align:start position:0% APNs we actually do support Alpena's I 00:20:18.630 --> 00:20:28.960 align:start position:0% APNs we actually do support Alpena's I didn't<00:20:19.140> mention<00:20:19.290> it<00:20:19.500> but<00:20:19.590> we<00:20:20.070> do<00:20:20.130> support 00:20:28.960 --> 00:20:28.970 align:start position:0% 00:20:28.970 --> 00:20:31.030 align:start position:0% you