WEBVTT Kind: captions Language: en 00:00:05.070 --> 00:00:14.910 align:start position:0% [Music] 00:00:14.910 --> 00:00:14.920 align:start position:0% 00:00:14.920 --> 00:00:19.710 align:start position:0% [Music] 00:00:19.710 --> 00:00:19.720 align:start position:0% 00:00:19.720 --> 00:00:23.509 align:start position:0% uh<00:00:19.960> yeah<00:00:20.320> let's<00:00:20.600> talk<00:00:20.800> about<00:00:21.119> mix<00:00:21.519> my<00:00:21.640> name<00:00:21.840> is 00:00:23.509 --> 00:00:23.519 align:start position:0% uh yeah let's talk about mix my name is 00:00:23.519 --> 00:00:28.630 align:start position:0% uh yeah let's talk about mix my name is aradan<00:00:24.880> um<00:00:25.880> and<00:00:26.160> mix<00:00:26.720> is<00:00:26.880> an<00:00:27.199> IDE<00:00:27.920> for 00:00:28.630 --> 00:00:28.640 align:start position:0% aradan um and mix is an IDE for 00:00:28.640 --> 00:00:31.070 align:start position:0% aradan um and mix is an IDE for developing<00:00:29.439> distributed<00:00:30.080> applications<00:00:30.800> on 00:00:31.070 --> 00:00:31.080 align:start position:0% developing distributed applications on 00:00:31.080 --> 00:00:33.790 align:start position:0% developing distributed applications on ethereum<00:00:31.920> platform<00:00:32.920> it<00:00:33.040> started<00:00:33.440> about<00:00:33.640> a 00:00:33.790 --> 00:00:33.800 align:start position:0% ethereum platform it started about a 00:00:33.800 --> 00:00:37.069 align:start position:0% ethereum platform it started about a year<00:00:34.200> ago<00:00:35.200> we've<00:00:35.399> been<00:00:35.559> working<00:00:35.840> on<00:00:36.000> it<00:00:36.440> in 00:00:37.069 --> 00:00:37.079 align:start position:0% year ago we've been working on it in 00:00:37.079 --> 00:00:40.150 align:start position:0% year ago we've been working on it in ifdf<00:00:37.719> Berlin<00:00:38.719> I<00:00:38.879> did<00:00:39.040> some<00:00:39.239> work<00:00:39.440> on<00:00:39.600> it<00:00:39.879> a<00:00:39.960> few 00:00:40.150 --> 00:00:40.160 align:start position:0% ifdf Berlin I did some work on it a few 00:00:40.160 --> 00:00:43.229 align:start position:0% ifdf Berlin I did some work on it a few months<00:00:40.480> ago<00:00:40.879> but<00:00:41.079> nowadays<00:00:41.640> it's<00:00:42.640> been<00:00:42.840> mostly 00:00:43.229 --> 00:00:43.239 align:start position:0% months ago but nowadays it's been mostly 00:00:43.239 --> 00:00:45.110 align:start position:0% months ago but nowadays it's been mostly programmed<00:00:43.800> by<00:00:44.200> Young 00:00:45.110 --> 00:00:45.120 align:start position:0% programmed by Young 00:00:45.120 --> 00:00:50.350 align:start position:0% programmed by Young lro<00:00:46.120> wouldn't<00:00:46.440> be<00:00:46.640> here<00:00:47.320> today<00:00:48.320> so<00:00:48.640> still<00:00:49.440> um 00:00:50.350 --> 00:00:50.360 align:start position:0% lro wouldn't be here today so still um 00:00:50.360 --> 00:00:54.630 align:start position:0% lro wouldn't be here today so still um credit<00:00:51.360> should<00:00:51.600> go<00:00:51.800> to<00:00:52.000> Y<00:00:52.559> and<00:00:52.760> of<00:00:53.039> course<00:00:54.039> Utah 00:00:54.630 --> 00:00:54.640 align:start position:0% credit should go to Y and of course Utah 00:00:54.640 --> 00:00:57.389 align:start position:0% credit should go to Y and of course Utah and<00:00:55.199> alar<00:00:55.800> for<00:00:56.039> providing 00:00:57.389 --> 00:00:57.399 align:start position:0% and alar for providing 00:00:57.399 --> 00:01:01.509 align:start position:0% and alar for providing design<00:00:58.399> yeah 00:01:01.509 --> 00:01:01.519 align:start position:0% 00:01:01.519 --> 00:01:05.990 align:start position:0% this<00:01:01.680> will<00:01:01.879> be<00:01:02.440> a<00:01:02.640> live 00:01:05.990 --> 00:01:06.000 align:start position:0% 00:01:06.000 --> 00:01:16.390 align:start position:0% demonstration<00:01:07.000> just<00:01:07.200> a<00:01:08.040> sec<00:01:09.040> make<00:01:09.200> it 00:01:16.390 --> 00:01:16.400 align:start position:0% 00:01:16.400 --> 00:01:19.749 align:start position:0% work<00:01:17.400> okay<00:01:17.840> this<00:01:18.000> is<00:01:18.320> inconvenient<00:01:19.320> I<00:01:19.479> can't 00:01:19.749 --> 00:01:19.759 align:start position:0% work okay this is inconvenient I can't 00:01:19.759 --> 00:01:24.550 align:start position:0% work okay this is inconvenient I can't really<00:01:20.280> see<00:01:20.640> what's<00:01:20.880> going 00:01:24.550 --> 00:01:24.560 align:start position:0% 00:01:24.560 --> 00:01:31.630 align:start position:0% on<00:01:25.560> okay<00:01:26.159> hope<00:01:26.320> you<00:01:26.439> can<00:01:26.560> see<00:01:26.799> it 00:01:31.630 --> 00:01:31.640 align:start position:0% 00:01:31.640 --> 00:01:35.109 align:start position:0% so<00:01:32.320> the<00:01:32.479> idea<00:01:32.799> behind<00:01:33.079> mix<00:01:33.479> is<00:01:33.640> to<00:01:33.880> provide 00:01:35.109 --> 00:01:35.119 align:start position:0% so the idea behind mix is to provide 00:01:35.119 --> 00:01:38.350 align:start position:0% so the idea behind mix is to provide an<00:01:36.119> environment<00:01:36.920> for<00:01:37.360> developing 00:01:38.350 --> 00:01:38.360 align:start position:0% an environment for developing 00:01:38.360 --> 00:01:40.310 align:start position:0% an environment for developing distributed<00:01:38.920> applications<00:01:39.479> and<00:01:39.640> to 00:01:40.310 --> 00:01:40.320 align:start position:0% distributed applications and to 00:01:40.320 --> 00:01:43.270 align:start position:0% distributed applications and to support<00:01:41.320> a<00:01:41.720> full<00:01:42.079> life<00:01:42.399> cycle<00:01:42.720> for<00:01:43.040> the 00:01:43.270 --> 00:01:43.280 align:start position:0% support a full life cycle for the 00:01:43.280 --> 00:01:45.910 align:start position:0% support a full life cycle for the application<00:01:43.799> development<00:01:44.439> starting<00:01:44.920> from 00:01:45.910 --> 00:01:45.920 align:start position:0% application development starting from 00:01:45.920 --> 00:01:48.149 align:start position:0% application development starting from the<00:01:46.159> smart<00:01:46.560> contracts<00:01:47.119> and<00:01:47.240> then<00:01:47.399> moving<00:01:47.759> to 00:01:48.149 --> 00:01:48.159 align:start position:0% the smart contracts and then moving to 00:01:48.159 --> 00:01:50.830 align:start position:0% the smart contracts and then moving to user<00:01:48.560> interface<00:01:49.119> and<00:01:49.280> then<00:01:49.439> to<00:01:49.719> testing<00:01:50.600> to 00:01:50.830 --> 00:01:50.840 align:start position:0% user interface and then to testing to 00:01:50.840 --> 00:01:53.990 align:start position:0% user interface and then to testing to deployment<00:01:51.680> and<00:01:52.119> to 00:01:53.990 --> 00:01:54.000 align:start position:0% deployment and to 00:01:54.000 --> 00:01:57.310 align:start position:0% deployment and to updating 00:01:57.310 --> 00:01:57.320 align:start position:0% 00:01:57.320 --> 00:02:00.510 align:start position:0% okay<00:01:58.320> so<00:01:58.520> mix<00:01:58.920> is<00:01:59.000> a<00:01:59.200> desktop<00:01:59.600> appliation<00:02:00.039> a<00:02:00.360> it 00:02:00.510 --> 00:02:00.520 align:start position:0% okay so mix is a desktop appliation a it 00:02:00.520 --> 00:02:02.590 align:start position:0% okay so mix is a desktop appliation a it doesn't<00:02:00.880> require<00:02:01.439> any<00:02:01.759> network<00:02:02.200> connection 00:02:02.590 --> 00:02:02.600 align:start position:0% doesn't require any network connection 00:02:02.600 --> 00:02:03.429 align:start position:0% doesn't require any network connection to 00:02:03.429 --> 00:02:03.439 align:start position:0% to 00:02:03.439 --> 00:02:06.029 align:start position:0% to work<00:02:04.439> and<00:02:05.320> yeah 00:02:06.029 --> 00:02:06.039 align:start position:0% work and yeah 00:02:06.039 --> 00:02:08.510 align:start position:0% work and yeah let's<00:02:07.039> take<00:02:07.200> a<00:02:07.360> look<00:02:07.479> at<00:02:07.680> what<00:02:07.880> features<00:02:08.360> we 00:02:08.510 --> 00:02:08.520 align:start position:0% let's take a look at what features we 00:02:08.520 --> 00:02:11.510 align:start position:0% let's take a look at what features we have 00:02:11.510 --> 00:02:11.520 align:start position:0% 00:02:11.520 --> 00:02:15.350 align:start position:0% here<00:02:12.520> um<00:02:13.400> so<00:02:13.640> the<00:02:13.840> basic<00:02:14.160> is<00:02:14.319> this<00:02:14.640> simple 00:02:15.350 --> 00:02:15.360 align:start position:0% here um so the basic is this simple 00:02:15.360 --> 00:02:17.229 align:start position:0% here um so the basic is this simple editor<00:02:15.920> we<00:02:16.080> have<00:02:16.239> for 00:02:17.229 --> 00:02:17.239 align:start position:0% editor we have for 00:02:17.239 --> 00:02:19.229 align:start position:0% editor we have for contracts<00:02:18.239> it<00:02:18.400> has<00:02:18.519> all<00:02:18.680> the<00:02:18.800> features<00:02:19.120> you 00:02:19.229 --> 00:02:19.239 align:start position:0% contracts it has all the features you 00:02:19.239 --> 00:02:21.430 align:start position:0% contracts it has all the features you would<00:02:19.440> expect<00:02:19.760> from<00:02:20.040> code<00:02:20.319> editors<00:02:21.000> such<00:02:21.200> as 00:02:21.430 --> 00:02:21.440 align:start position:0% would expect from code editors such as 00:02:21.440 --> 00:02:24.309 align:start position:0% would expect from code editors such as syntax<00:02:22.000> highlighting<00:02:23.000> a 00:02:24.309 --> 00:02:24.319 align:start position:0% syntax highlighting a 00:02:24.319 --> 00:02:27.750 align:start position:0% syntax highlighting a completion<00:02:25.319> now<00:02:25.599> it 00:02:27.750 --> 00:02:27.760 align:start position:0% completion now it 00:02:27.760 --> 00:02:30.910 align:start position:0% completion now it also<00:02:28.760> highlights<00:02:29.440> errors<00:02:30.000> in<00:02:30.160> the<00:02:30.319> code<00:02:30.640> so 00:02:30.910 --> 00:02:30.920 align:start position:0% also highlights errors in the code so 00:02:30.920 --> 00:02:35.229 align:start position:0% also highlights errors in the code so let's<00:02:31.160> say<00:02:31.480> I<00:02:31.599> would<00:02:32.000> make<00:02:32.319> an<00:02:32.840> error 00:02:35.229 --> 00:02:35.239 align:start position:0% let's say I would make an error 00:02:35.239 --> 00:02:38.509 align:start position:0% let's say I would make an error here<00:02:36.239> yeah<00:02:36.400> it<00:02:36.720> would<00:02:37.720> would<00:02:37.879> show<00:02:38.160> the<00:02:38.239> error 00:02:38.509 --> 00:02:38.519 align:start position:0% here yeah it would would show the error 00:02:38.519 --> 00:02:40.229 align:start position:0% here yeah it would would show the error immediately<00:02:39.200> I<00:02:39.319> can<00:02:39.480> navigate<00:02:39.920> between 00:02:40.229 --> 00:02:40.239 align:start position:0% immediately I can navigate between 00:02:40.239 --> 00:02:44.509 align:start position:0% immediately I can navigate between errors<00:02:40.720> fix<00:02:41.560> errors<00:02:42.680> and<00:02:43.680> other<00:02:44.080> completion 00:02:44.509 --> 00:02:44.519 align:start position:0% errors fix errors and other completion 00:02:44.519 --> 00:02:46.910 align:start position:0% errors fix errors and other completion also<00:02:44.800> works 00:02:46.910 --> 00:02:46.920 align:start position:0% also works 00:02:46.920 --> 00:02:51.229 align:start position:0% also works here<00:02:47.920> so<00:02:48.239> let's<00:02:49.040> the<00:02:49.200> first<00:02:49.599> step<00:02:50.599> I<00:02:50.760> did<00:02:51.000> here 00:02:51.229 --> 00:02:51.239 align:start position:0% here so let's the first step I did here 00:02:51.239 --> 00:02:54.309 align:start position:0% here so let's the first step I did here is<00:02:51.400> I<00:02:51.560> enter<00:02:51.920> this<00:02:52.080> contract<00:02:52.440> now<00:02:52.599> this<00:02:53.120> is<00:02:54.120> a 00:02:54.309 --> 00:02:54.319 align:start position:0% is I enter this contract now this is a 00:02:54.319 --> 00:02:56.990 align:start position:0% is I enter this contract now this is a basic<00:02:54.640> token<00:02:55.120> contract<00:02:55.720> the<00:02:55.920> very<00:02:56.159> same<00:02:56.400> idea 00:02:56.990 --> 00:02:57.000 align:start position:0% basic token contract the very same idea 00:02:57.000 --> 00:02:59.630 align:start position:0% basic token contract the very same idea was<00:02:57.159> mentioned<00:02:57.519> in<00:02:57.640> the<00:02:57.800> previous<00:02:58.280> talk<00:02:59.280> and 00:02:59.630 --> 00:02:59.640 align:start position:0% was mentioned in the previous talk and 00:02:59.640 --> 00:03:01.430 align:start position:0% was mentioned in the previous talk and this<00:02:59.879> this<00:03:00.040> is<00:03:00.239> the<00:03:00.440> simplest<00:03:00.879> form<00:03:01.159> of<00:03:01.280> the 00:03:01.430 --> 00:03:01.440 align:start position:0% this this is the simplest form of the 00:03:01.440 --> 00:03:03.630 align:start position:0% this this is the simplest form of the token<00:03:01.840> contract<00:03:02.239> you<00:03:02.360> can<00:03:02.599> have<00:03:03.040> it<00:03:03.200> only<00:03:03.480> has 00:03:03.630 --> 00:03:03.640 align:start position:0% token contract you can have it only has 00:03:03.640 --> 00:03:05.550 align:start position:0% token contract you can have it only has the<00:03:03.840> send<00:03:04.280> function 00:03:05.550 --> 00:03:05.560 align:start position:0% the send function 00:03:05.560 --> 00:03:08.910 align:start position:0% the send function which<00:03:06.560> transfers<00:03:07.400> tokens<00:03:08.120> from<00:03:08.360> one<00:03:08.599> account 00:03:08.910 --> 00:03:08.920 align:start position:0% which transfers tokens from one account 00:03:08.920 --> 00:03:12.789 align:start position:0% which transfers tokens from one account to<00:03:09.120> another<00:03:09.840> right 00:03:12.789 --> 00:03:12.799 align:start position:0% 00:03:12.799 --> 00:03:15.190 align:start position:0% here<00:03:13.799> now 00:03:15.190 --> 00:03:15.200 align:start position:0% here now 00:03:15.200 --> 00:03:18.509 align:start position:0% here now after<00:03:16.200> I've<00:03:16.480> done<00:03:16.920> writing<00:03:17.319> my<00:03:17.519> contract<00:03:18.080> The 00:03:18.509 --> 00:03:18.519 align:start position:0% after I've done writing my contract The 00:03:18.519 --> 00:03:20.789 align:start position:0% after I've done writing my contract The Next<00:03:18.840> Step<00:03:19.080> would<00:03:19.280> be<00:03:19.560> to<00:03:19.799> test 00:03:20.789 --> 00:03:20.799 align:start position:0% Next Step would be to test 00:03:20.799 --> 00:03:23.550 align:start position:0% Next Step would be to test it 00:03:23.550 --> 00:03:23.560 align:start position:0% it 00:03:23.560 --> 00:03:26.990 align:start position:0% it and<00:03:24.560> for<00:03:24.879> that<00:03:25.200> I<00:03:25.400> have 00:03:26.990 --> 00:03:27.000 align:start position:0% and for that I have 00:03:27.000 --> 00:03:30.270 align:start position:0% and for that I have this<00:03:28.000> scenario<00:03:28.720> panel<00:03:29.159> here 00:03:30.270 --> 00:03:30.280 align:start position:0% this scenario panel here 00:03:30.280 --> 00:03:33.309 align:start position:0% this scenario panel here now<00:03:30.480> scenario<00:03:31.040> is<00:03:31.560> basically<00:03:32.560> a<00:03:32.760> sequence<00:03:33.120> of 00:03:33.309 --> 00:03:33.319 align:start position:0% now scenario is basically a sequence of 00:03:33.319 --> 00:03:35.509 align:start position:0% now scenario is basically a sequence of transactions<00:03:34.120> executed<00:03:34.720> in<00:03:34.879> the<00:03:35.040> same<00:03:35.319> way 00:03:35.509 --> 00:03:35.519 align:start position:0% transactions executed in the same way 00:03:35.519 --> 00:03:36.949 align:start position:0% transactions executed in the same way they<00:03:35.680> would<00:03:36.000> execute<00:03:36.400> on<00:03:36.519> an<00:03:36.680> actual 00:03:36.949 --> 00:03:36.959 align:start position:0% they would execute on an actual 00:03:36.959 --> 00:03:39.869 align:start position:0% they would execute on an actual blockchain<00:03:37.400> so<00:03:37.599> this<00:03:37.720> is<00:03:37.920> in<00:03:38.319> fact<00:03:39.319> and 00:03:39.869 --> 00:03:39.879 align:start position:0% blockchain so this is in fact and 00:03:39.879 --> 00:03:43.070 align:start position:0% blockchain so this is in fact and sandbox<00:03:40.560> blockchain<00:03:41.360> very<00:03:41.599> much<00:03:41.920> like<00:03:42.560> in<00:03:42.760> the 00:03:43.070 --> 00:03:43.080 align:start position:0% sandbox blockchain very much like in the 00:03:43.080 --> 00:03:45.830 align:start position:0% sandbox blockchain very much like in the eer<00:03:43.519> camp<00:03:43.799> ID<00:03:44.120> you<00:03:44.200> we've<00:03:44.400> seen<00:03:44.640> earlier<00:03:45.640> but 00:03:45.830 --> 00:03:45.840 align:start position:0% eer camp ID you we've seen earlier but 00:03:45.840 --> 00:03:48.270 align:start position:0% eer camp ID you we've seen earlier but there<00:03:45.959> are<00:03:46.120> some<00:03:46.360> key<00:03:46.599> differences 00:03:48.270 --> 00:03:48.280 align:start position:0% there are some key differences 00:03:48.280 --> 00:03:51.110 align:start position:0% there are some key differences here<00:03:49.280> so<00:03:49.519> I<00:03:49.599> can<00:03:49.760> set<00:03:49.959> up<00:03:50.519> a<00:03:50.680> number<00:03:50.920> of 00:03:51.110 --> 00:03:51.120 align:start position:0% here so I can set up a number of 00:03:51.120 --> 00:03:53.670 align:start position:0% here so I can set up a number of transactions<00:03:51.720> to<00:03:51.920> test<00:03:52.200> my<00:03:52.400> contract<00:03:53.400> I<00:03:53.519> can 00:03:53.670 --> 00:03:53.680 align:start position:0% transactions to test my contract I can 00:03:53.680 --> 00:03:57.350 align:start position:0% transactions to test my contract I can have<00:03:53.920> multiple<00:03:54.400> scenarios<00:03:55.720> and<00:03:56.720> to<00:03:57.000> test 00:03:57.350 --> 00:03:57.360 align:start position:0% have multiple scenarios and to test 00:03:57.360 --> 00:04:00.470 align:start position:0% have multiple scenarios and to test various<00:03:57.799> aspects 00:04:00.470 --> 00:04:00.480 align:start position:0% various aspects 00:04:00.480 --> 00:04:03.509 align:start position:0% various aspects now<00:04:00.720> let's<00:04:01.040> see<00:04:01.360> what<00:04:01.560> we<00:04:01.720> can<00:04:02.000> configure 00:04:03.509 --> 00:04:03.519 align:start position:0% now let's see what we can configure 00:04:03.519 --> 00:04:05.990 align:start position:0% now let's see what we can configure here<00:04:04.519> so<00:04:04.920> this 00:04:05.990 --> 00:04:06.000 align:start position:0% here so this 00:04:06.000 --> 00:04:08.750 align:start position:0% here so this particular<00:04:07.000> testing<00:04:07.519> blockchain<00:04:08.439> has<00:04:08.560> a 00:04:08.750 --> 00:04:08.760 align:start position:0% particular testing blockchain has a 00:04:08.760 --> 00:04:11.869 align:start position:0% particular testing blockchain has a Genesis<00:04:09.560> state<00:04:10.519> which<00:04:10.760> can<00:04:11.079> I<00:04:11.200> can<00:04:11.400> import 00:04:11.869 --> 00:04:11.879 align:start position:0% Genesis state which can I can import 00:04:11.879 --> 00:04:14.350 align:start position:0% Genesis state which can I can import from<00:04:12.360> adjacent<00:04:12.879> file<00:04:13.239> which<00:04:13.360> I<00:04:13.480> can<00:04:13.959> generate 00:04:14.350 --> 00:04:14.360 align:start position:0% from adjacent file which I can generate 00:04:14.360 --> 00:04:16.189 align:start position:0% from adjacent file which I can generate from<00:04:14.519> an<00:04:14.720> actual 00:04:16.189 --> 00:04:16.199 align:start position:0% from an actual 00:04:16.199 --> 00:04:18.710 align:start position:0% from an actual blockchain<00:04:17.199> or<00:04:17.359> I<00:04:17.479> can<00:04:17.680> just<00:04:17.880> list<00:04:18.280> accounts 00:04:18.710 --> 00:04:18.720 align:start position:0% blockchain or I can just list accounts 00:04:18.720 --> 00:04:19.990 align:start position:0% blockchain or I can just list accounts here<00:04:18.919> with<00:04:19.040> some 00:04:19.990 --> 00:04:20.000 align:start position:0% here with some 00:04:20.000 --> 00:04:24.070 align:start position:0% here with some balances<00:04:21.000> so<00:04:21.440> yeah<00:04:21.799> have 00:04:24.070 --> 00:04:24.080 align:start position:0% 00:04:24.080 --> 00:04:28.189 align:start position:0% four<00:04:25.080> accounts<00:04:26.040> here<00:04:27.040> and<00:04:27.199> I<00:04:27.360> also 00:04:28.189 --> 00:04:28.199 align:start position:0% four accounts here and I also 00:04:28.199 --> 00:04:30.790 align:start position:0% four accounts here and I also have<00:04:29.199> two 00:04:30.790 --> 00:04:30.800 align:start position:0% have two 00:04:30.800 --> 00:04:33.029 align:start position:0% have two transactions<00:04:31.479> here<00:04:31.800> each<00:04:32.000> of<00:04:32.360> them<00:04:32.639> goes<00:04:32.840> into 00:04:33.029 --> 00:04:33.039 align:start position:0% transactions here each of them goes into 00:04:33.039 --> 00:04:35.830 align:start position:0% transactions here each of them goes into a<00:04:33.199> separate<00:04:33.560> block<00:04:34.560> so<00:04:34.759> the<00:04:34.960> first 00:04:35.830 --> 00:04:35.840 align:start position:0% a separate block so the first 00:04:35.840 --> 00:04:39.390 align:start position:0% a separate block so the first Transaction<00:04:36.840> what<00:04:37.000> it<00:04:37.479> does<00:04:38.479> it<00:04:38.639> deploys<00:04:39.160> my 00:04:39.390 --> 00:04:39.400 align:start position:0% Transaction what it does it deploys my 00:04:39.400 --> 00:04:41.710 align:start position:0% Transaction what it does it deploys my contract<00:04:39.960> on<00:04:40.199> this 00:04:41.710 --> 00:04:41.720 align:start position:0% contract on this 00:04:41.720 --> 00:04:44.270 align:start position:0% contract on this sandbox 00:04:44.270 --> 00:04:44.280 align:start position:0% sandbox 00:04:44.280 --> 00:04:48.029 align:start position:0% sandbox blockchain<00:04:45.280> here<00:04:45.440> I<00:04:45.680> have<00:04:45.800> a<00:04:46.000> UI<00:04:46.479> to<00:04:47.400> specify 00:04:48.029 --> 00:04:48.039 align:start position:0% blockchain here I have a UI to specify 00:04:48.039 --> 00:04:49.830 align:start position:0% blockchain here I have a UI to specify transaction<00:04:48.600> parameters<00:04:49.160> and<00:04:49.280> that<00:04:49.440> includes 00:04:49.830 --> 00:04:49.840 align:start position:0% transaction parameters and that includes 00:04:49.840 --> 00:04:52.350 align:start position:0% transaction parameters and that includes to<00:04:50.120> this<00:04:50.720> as<00:04:50.840> you<00:04:50.919> can<00:04:51.080> see<00:04:51.320> here<00:04:51.600> my<00:04:51.840> contract 00:04:52.350 --> 00:04:52.360 align:start position:0% to this as you can see here my contract 00:04:52.360 --> 00:04:56.270 align:start position:0% to this as you can see here my contract has<00:04:53.199> a<00:04:53.400> Constructor<00:04:54.320> which<00:04:54.560> accepts<00:04:55.039> a<00:04:55.160> single 00:04:56.270 --> 00:04:56.280 align:start position:0% has a Constructor which accepts a single 00:04:56.280 --> 00:04:59.150 align:start position:0% has a Constructor which accepts a single argument<00:04:57.280> and<00:04:57.479> I<00:04:57.600> can<00:04:58.080> provide<00:04:58.440> a<00:04:58.639> value<00:04:58.960> for 00:04:59.150 --> 00:04:59.160 align:start position:0% argument and I can provide a value for 00:04:59.160 --> 00:05:01.710 align:start position:0% argument and I can provide a value for this<00:04:59.280> argument<00:04:59.840> right 00:05:01.710 --> 00:05:01.720 align:start position:0% this argument right 00:05:01.720 --> 00:05:04.710 align:start position:0% this argument right here<00:05:02.720> it<00:05:02.960> also<00:05:03.600> it<00:05:03.720> allows<00:05:04.039> to<00:05:04.199> set<00:05:04.440> basic 00:05:04.710 --> 00:05:04.720 align:start position:0% here it also it allows to set basic 00:05:04.720 --> 00:05:06.990 align:start position:0% here it also it allows to set basic transaction<00:05:05.240> parameters<00:05:05.840> such<00:05:06.039> as<00:05:06.479> gas<00:05:06.759> and 00:05:06.990 --> 00:05:07.000 align:start position:0% transaction parameters such as gas and 00:05:07.000 --> 00:05:10.510 align:start position:0% transaction parameters such as gas and gas 00:05:10.510 --> 00:05:10.520 align:start position:0% 00:05:10.520 --> 00:05:14.710 align:start position:0% price<00:05:11.520> okay<00:05:11.759> so<00:05:11.880> I<00:05:12.039> have<00:05:12.320> this<00:05:13.080> and<00:05:13.240> the<00:05:13.360> second 00:05:14.710 --> 00:05:14.720 align:start position:0% price okay so I have this and the second 00:05:14.720 --> 00:05:18.870 align:start position:0% price okay so I have this and the second transaction<00:05:15.720> just<00:05:15.919> sends<00:05:16.440> some<00:05:16.960> tokens<00:05:17.880> from 00:05:18.870 --> 00:05:18.880 align:start position:0% transaction just sends some tokens from 00:05:18.880 --> 00:05:22.390 align:start position:0% transaction just sends some tokens from current<00:05:19.560> account<00:05:19.960> to<00:05:20.199> another<00:05:20.560> account 00:05:22.390 --> 00:05:22.400 align:start position:0% current account to another account 00:05:22.400 --> 00:05:26.469 align:start position:0% current account to another account so<00:05:23.400> have<00:05:23.600> the<00:05:23.759> send<00:05:24.120> function<00:05:24.639> here 00:05:26.469 --> 00:05:26.479 align:start position:0% so have the send function here 00:05:26.479 --> 00:05:29.950 align:start position:0% so have the send function here and<00:05:27.479> it<00:05:27.639> also<00:05:27.919> accepts<00:05:28.280> two<00:05:28.479> parameters<00:05:29.759> the 00:05:29.950 --> 00:05:29.960 align:start position:0% and it also accepts two parameters the 00:05:29.960 --> 00:05:32.430 align:start position:0% and it also accepts two parameters the recipient<00:05:30.639> for<00:05:31.160> the<00:05:31.360> transfer<00:05:32.039> and<00:05:32.280> the 00:05:32.430 --> 00:05:32.440 align:start position:0% recipient for the transfer and the 00:05:32.440 --> 00:05:34.070 align:start position:0% recipient for the transfer and the number<00:05:32.639> of<00:05:32.800> tokens<00:05:33.160> to 00:05:34.070 --> 00:05:34.080 align:start position:0% number of tokens to 00:05:34.080 --> 00:05:38.590 align:start position:0% number of tokens to transfer<00:05:35.080> here<00:05:35.240> it 00:05:38.590 --> 00:05:38.600 align:start position:0% 00:05:38.600 --> 00:05:41.590 align:start position:0% is<00:05:39.600> now<00:05:39.759> with<00:05:39.880> a<00:05:40.000> click<00:05:40.199> of<00:05:40.479> the<00:05:40.720> button<00:05:41.080> I<00:05:41.199> can 00:05:41.590 --> 00:05:41.600 align:start position:0% is now with a click of the button I can 00:05:41.600 --> 00:05:45.870 align:start position:0% is now with a click of the button I can execute<00:05:42.199> these<00:05:42.720> transactions<00:05:43.720> and<00:05:44.639> get 00:05:45.870 --> 00:05:45.880 align:start position:0% execute these transactions and get 00:05:45.880 --> 00:05:51.430 align:start position:0% execute these transactions and get result<00:05:46.880> so<00:05:47.160> this<00:05:47.280> is<00:05:48.680> my<00:05:49.680> current<00:05:50.440> state 00:05:51.430 --> 00:05:51.440 align:start position:0% result so this is my current state 00:05:51.440 --> 00:05:57.189 align:start position:0% result so this is my current state displayed<00:05:51.960> here<00:05:52.160> it<00:05:52.680> shows<00:05:53.880> contract<00:05:54.880> storage 00:05:57.189 --> 00:05:57.199 align:start position:0% displayed here it shows contract storage 00:05:57.199 --> 00:06:03.270 align:start position:0% displayed here it shows contract storage and<00:05:58.199> configurate<00:05:58.800> accounts<00:05:59.160> as<00:05:59.280> well 00:06:03.270 --> 00:06:03.280 align:start position:0% 00:06:03.280 --> 00:06:05.590 align:start position:0% okay<00:06:03.479> so<00:06:04.280> this<00:06:04.400> is<00:06:04.520> a<00:06:04.639> simple<00:06:05.000> contract<00:06:05.479> but 00:06:05.590 --> 00:06:05.600 align:start position:0% okay so this is a simple contract but 00:06:05.600 --> 00:06:08.270 align:start position:0% okay so this is a simple contract but I've<00:06:05.720> seen<00:06:06.400> people<00:06:06.919> writing<00:06:07.440> really<00:06:07.840> complex 00:06:08.270 --> 00:06:08.280 align:start position:0% I've seen people writing really complex 00:06:08.280 --> 00:06:10.430 align:start position:0% I've seen people writing really complex contracts<00:06:08.960> in<00:06:09.160> solidity<00:06:09.960> and<00:06:10.160> what<00:06:10.280> if 00:06:10.430 --> 00:06:10.440 align:start position:0% contracts in solidity and what if 00:06:10.440 --> 00:06:13.430 align:start position:0% contracts in solidity and what if something<00:06:10.759> goes<00:06:11.599> wrong<00:06:12.599> and<00:06:12.880> we<00:06:13.039> might<00:06:13.240> want 00:06:13.430 --> 00:06:13.440 align:start position:0% something goes wrong and we might want 00:06:13.440 --> 00:06:17.950 align:start position:0% something goes wrong and we might want to<00:06:13.800> debug<00:06:14.319> things<00:06:15.319> and<00:06:15.599> what<00:06:15.919> mix<00:06:16.280> supports 00:06:17.950 --> 00:06:17.960 align:start position:0% to debug things and what mix supports 00:06:17.960 --> 00:06:21.309 align:start position:0% to debug things and what mix supports is<00:06:18.960> building<00:06:19.599> debugger<00:06:20.280> for 00:06:21.309 --> 00:06:21.319 align:start position:0% is building debugger for 00:06:21.319 --> 00:06:24.270 align:start position:0% is building debugger for solidity<00:06:22.319> let's<00:06:22.599> take<00:06:22.720> a<00:06:22.880> look<00:06:23.039> at<00:06:23.440> that<00:06:23.880> so<00:06:24.120> I 00:06:24.270 --> 00:06:24.280 align:start position:0% solidity let's take a look at that so I 00:06:24.280 --> 00:06:27.710 align:start position:0% solidity let's take a look at that so I have 00:06:27.710 --> 00:06:27.720 align:start position:0% 00:06:27.720 --> 00:06:31.309 align:start position:0% this<00:06:28.720> debu<00:06:29.199> trans 00:06:31.309 --> 00:06:31.319 align:start position:0% this debu trans 00:06:31.319 --> 00:06:33.710 align:start position:0% this debu trans ction 00:06:33.710 --> 00:06:33.720 align:start position:0% ction 00:06:33.720 --> 00:06:37.749 align:start position:0% ction yeah<00:06:34.720> and<00:06:35.039> I<00:06:35.319> can<00:06:36.319> I'm<00:06:36.479> debugging<00:06:37.080> this<00:06:37.319> sand 00:06:37.749 --> 00:06:37.759 align:start position:0% yeah and I can I'm debugging this sand 00:06:37.759 --> 00:06:40.350 align:start position:0% yeah and I can I'm debugging this sand function<00:06:38.120> now<00:06:39.120> I<00:06:39.240> can<00:06:39.400> step<00:06:39.639> through<00:06:39.840> the<00:06:40.000> code 00:06:40.350 --> 00:06:40.360 align:start position:0% function now I can step through the code 00:06:40.360 --> 00:06:42.670 align:start position:0% function now I can step through the code and<00:06:40.520> see<00:06:40.800> how<00:06:40.960> it<00:06:41.160> gets<00:06:41.479> executed<00:06:42.479> this 00:06:42.670 --> 00:06:42.680 align:start position:0% and see how it gets executed this 00:06:42.680 --> 00:06:45.270 align:start position:0% and see how it gets executed this operates<00:06:43.120> on<00:06:43.280> an<00:06:43.479> Expression<00:06:43.960> level<00:06:44.319> so<00:06:44.560> I<00:06:44.639> can 00:06:45.270 --> 00:06:45.280 align:start position:0% operates on an Expression level so I can 00:06:45.280 --> 00:06:48.629 align:start position:0% operates on an Expression level so I can step<00:06:46.280> not<00:06:46.520> over<00:06:46.840> the<00:06:47.039> lines<00:06:47.520> but<00:06:47.759> individual 00:06:48.629 --> 00:06:48.639 align:start position:0% step not over the lines but individual 00:06:48.639 --> 00:06:52.390 align:start position:0% step not over the lines but individual solidity<00:06:49.520> expressions<00:06:50.520> and<00:06:50.680> as<00:06:50.840> I<00:06:51.080> go<00:06:51.720> I<00:06:51.840> can 00:06:52.390 --> 00:06:52.400 align:start position:0% solidity expressions and as I go I can 00:06:52.400 --> 00:06:55.390 align:start position:0% solidity expressions and as I go I can see<00:06:53.400> how<00:06:53.680> much<00:06:53.960> gas<00:06:54.560> the<00:06:54.759> function<00:06:55.280> the 00:06:55.390 --> 00:06:55.400 align:start position:0% see how much gas the function the 00:06:55.400 --> 00:06:58.550 align:start position:0% see how much gas the function the transactions<00:06:56.000> consume<00:06:56.479> so<00:06:57.160> far<00:06:58.160> as<00:06:58.280> you<00:06:58.400> can 00:06:58.550 --> 00:06:58.560 align:start position:0% transactions consume so far as you can 00:06:58.560 --> 00:07:01.270 align:start position:0% transactions consume so far as you can see<00:06:58.759> it's<00:06:58.879> slowly<00:06:59.280> grown 00:07:01.270 --> 00:07:01.280 align:start position:0% see it's slowly grown 00:07:01.280 --> 00:07:03.830 align:start position:0% see it's slowly grown here<00:07:02.280> and<00:07:02.479> notice<00:07:02.919> how 00:07:03.830 --> 00:07:03.840 align:start position:0% here and notice how 00:07:03.840 --> 00:07:07.950 align:start position:0% here and notice how steep<00:07:04.840> it<00:07:05.039> went<00:07:05.360> from<00:07:06.080> 300<00:07:06.879> to<00:07:07.160> 5,000 00:07:07.950 --> 00:07:07.960 align:start position:0% steep it went from 300 to 5,000 00:07:07.960 --> 00:07:10.150 align:start position:0% steep it went from 300 to 5,000 something<00:07:08.960> that's<00:07:09.199> because 00:07:10.150 --> 00:07:10.160 align:start position:0% something that's because 00:07:10.160 --> 00:07:13.469 align:start position:0% something that's because storage<00:07:11.160> rights<00:07:11.479> are<00:07:11.759> expensive<00:07:12.319> in<00:07:12.560> theum 00:07:13.469 --> 00:07:13.479 align:start position:0% storage rights are expensive in theum 00:07:13.479 --> 00:07:17.150 align:start position:0% storage rights are expensive in theum yeah<00:07:14.280> so<00:07:14.479> I<00:07:14.599> can<00:07:14.800> step<00:07:15.160> forward<00:07:15.720> and<00:07:16.000> backwards 00:07:17.150 --> 00:07:17.160 align:start position:0% yeah so I can step forward and backwards 00:07:17.160 --> 00:07:20.070 align:start position:0% yeah so I can step forward and backwards so<00:07:18.160> basically<00:07:18.560> I<00:07:18.639> can<00:07:18.840> navigate<00:07:19.280> to<00:07:19.599> any<00:07:19.879> point 00:07:20.070 --> 00:07:20.080 align:start position:0% so basically I can navigate to any point 00:07:20.080 --> 00:07:21.950 align:start position:0% so basically I can navigate to any point in<00:07:20.360> time<00:07:20.720> here<00:07:21.039> during<00:07:21.400> transaction 00:07:21.950 --> 00:07:21.960 align:start position:0% in time here during transaction 00:07:21.960 --> 00:07:24.629 align:start position:0% in time here during transaction execution<00:07:22.560> and<00:07:22.759> examine<00:07:23.199> the<00:07:23.360> state<00:07:24.280> of<00:07:24.440> the 00:07:24.629 --> 00:07:24.639 align:start position:0% execution and examine the state of the 00:07:24.639 --> 00:07:27.830 align:start position:0% execution and examine the state of the contract<00:07:25.080> at<00:07:25.720> this<00:07:26.720> point<00:07:26.960> of<00:07:27.199> time<00:07:27.560> so<00:07:27.720> it 00:07:27.830 --> 00:07:27.840 align:start position:0% contract at this point of time so it 00:07:27.840 --> 00:07:30.029 align:start position:0% contract at this point of time so it shows<00:07:28.120> me<00:07:28.400> here<00:07:28.639> my<00:07:28.960> walk 00:07:30.029 --> 00:07:30.039 align:start position:0% shows me here my walk 00:07:30.039 --> 00:07:32.270 align:start position:0% shows me here my walk variable 00:07:32.270 --> 00:07:32.280 align:start position:0% variable 00:07:32.280 --> 00:07:36.070 align:start position:0% variable and<00:07:33.280> contract<00:07:33.919> storage<00:07:34.440> as 00:07:36.070 --> 00:07:36.080 align:start position:0% and contract storage as 00:07:36.080 --> 00:07:38.589 align:start position:0% and contract storage as well<00:07:37.080> so<00:07:37.319> yeah<00:07:37.560> this<00:07:37.720> allows<00:07:38.160> contract 00:07:38.589 --> 00:07:38.599 align:start position:0% well so yeah this allows contract 00:07:38.599 --> 00:07:41.710 align:start position:0% well so yeah this allows contract debuging<00:07:39.199> basically<00:07:39.599> you<00:07:40.120> can<00:07:41.120> figure<00:07:41.400> out 00:07:41.710 --> 00:07:41.720 align:start position:0% debuging basically you can figure out 00:07:41.720 --> 00:07:43.390 align:start position:0% debuging basically you can figure out what's<00:07:42.039> going<00:07:42.319> wrong<00:07:42.560> with<00:07:42.720> your<00:07:42.919> contract 00:07:43.390 --> 00:07:43.400 align:start position:0% what's going wrong with your contract 00:07:43.400 --> 00:07:46.149 align:start position:0% what's going wrong with your contract here<00:07:44.360> and<00:07:44.479> if<00:07:44.599> it's<00:07:44.800> not<00:07:45.000> enough<00:07:45.280> you<00:07:45.479> can<00:07:45.840> go 00:07:46.149 --> 00:07:46.159 align:start position:0% here and if it's not enough you can go 00:07:46.159 --> 00:07:51.070 align:start position:0% here and if it's not enough you can go deeper<00:07:46.599> to<00:07:47.400> this<00:07:48.400> um<00:07:48.800> evm<00:07:49.720> assembly<00:07:50.199> level 00:07:51.070 --> 00:07:51.080 align:start position:0% deeper to this um evm assembly level 00:07:51.080 --> 00:07:54.070 align:start position:0% deeper to this um evm assembly level debugging<00:07:52.080> you 00:07:54.070 --> 00:07:54.080 align:start position:0% debugging you 00:07:54.080 --> 00:07:58.430 align:start position:0% debugging you can<00:07:55.080> view<00:07:55.800> which<00:07:56.039> instructions<00:07:56.639> are<00:07:57.560> executed 00:07:58.430 --> 00:07:58.440 align:start position:0% can view which instructions are executed 00:07:58.440 --> 00:08:00.270 align:start position:0% can view which instructions are executed and<00:07:59.120> step 00:08:00.270 --> 00:08:00.280 align:start position:0% and step 00:08:00.280 --> 00:08:03.469 align:start position:0% and step in<00:08:00.440> and<00:08:00.639> out<00:08:00.919> of<00:08:01.159> functions<00:08:01.759> and<00:08:02.639> over 00:08:03.469 --> 00:08:03.479 align:start position:0% in and out of functions and over 00:08:03.479 --> 00:08:06.149 align:start position:0% in and out of functions and over instructions<00:08:04.479> and<00:08:04.680> also 00:08:06.149 --> 00:08:06.159 align:start position:0% instructions and also 00:08:06.159 --> 00:08:08.510 align:start position:0% instructions and also shows<00:08:07.159> the<00:08:07.280> place<00:08:07.560> in<00:08:07.720> the<00:08:07.879> code<00:08:08.199> which 00:08:08.510 --> 00:08:08.520 align:start position:0% shows the place in the code which 00:08:08.520 --> 00:08:11.070 align:start position:0% shows the place in the code which corresponds<00:08:09.080> to<00:08:09.240> current 00:08:11.070 --> 00:08:11.080 align:start position:0% corresponds to current 00:08:11.080 --> 00:08:14.189 align:start position:0% corresponds to current instruction<00:08:12.080> as<00:08:12.240> you<00:08:12.360> can<00:08:12.599> see<00:08:13.039> here<00:08:13.919> so 00:08:14.189 --> 00:08:14.199 align:start position:0% instruction as you can see here so 00:08:14.199 --> 00:08:17.270 align:start position:0% instruction as you can see here so that's<00:08:14.520> also<00:08:14.879> great<00:08:15.120> tool<00:08:15.400> to<00:08:16.039> study<00:08:17.039> how 00:08:17.270 --> 00:08:17.280 align:start position:0% that's also great tool to study how 00:08:17.280 --> 00:08:23.309 align:start position:0% that's also great tool to study how solidity<00:08:17.800> compiles<00:08:18.319> into<00:08:18.840> evm 00:08:23.309 --> 00:08:23.319 align:start position:0% 00:08:23.319 --> 00:08:25.029 align:start position:0% here 00:08:25.029 --> 00:08:25.039 align:start position:0% here 00:08:25.039 --> 00:08:32.430 align:start position:0% here okay<00:08:26.039> let's<00:08:26.319> get<00:08:26.599> out<00:08:26.800> of<00:08:27.000> it 00:08:32.430 --> 00:08:32.440 align:start position:0% 00:08:32.440 --> 00:08:34.670 align:start position:0% so<00:08:32.640> I<00:08:32.719> can<00:08:32.959> have<00:08:33.360> multiple<00:08:34.320> of<00:08:34.479> these 00:08:34.670 --> 00:08:34.680 align:start position:0% so I can have multiple of these 00:08:34.680 --> 00:08:37.310 align:start position:0% so I can have multiple of these so-called<00:08:35.120> scenarios<00:08:35.760> here<00:08:36.200> and<00:08:36.399> I<00:08:36.479> can<00:08:36.719> have 00:08:37.310 --> 00:08:37.320 align:start position:0% so-called scenarios here and I can have 00:08:37.320 --> 00:08:40.630 align:start position:0% so-called scenarios here and I can have one<00:08:37.680> for<00:08:37.800> example<00:08:38.159> the<00:08:38.919> tests<00:08:39.919> if<00:08:40.120> the<00:08:40.240> fonts 00:08:40.630 --> 00:08:40.640 align:start position:0% one for example the tests if the fonts 00:08:40.640 --> 00:08:42.469 align:start position:0% one for example the tests if the fonts are<00:08:40.800> stand<00:08:41.279> correctly<00:08:41.680> and<00:08:41.800> another<00:08:42.039> one 00:08:42.469 --> 00:08:42.479 align:start position:0% are stand correctly and another one 00:08:42.479 --> 00:08:44.070 align:start position:0% are stand correctly and another one which<00:08:42.719> tests 00:08:44.070 --> 00:08:44.080 align:start position:0% which tests 00:08:44.080 --> 00:08:47.990 align:start position:0% which tests if<00:08:45.080> this<00:08:46.000> condition<00:08:47.000> is<00:08:47.200> checked<00:08:47.560> correctly 00:08:47.990 --> 00:08:48.000 align:start position:0% if this condition is checked correctly 00:08:48.000 --> 00:08:48.949 align:start position:0% if this condition is checked correctly for 00:08:48.949 --> 00:08:48.959 align:start position:0% for 00:08:48.959 --> 00:08:53.790 align:start position:0% for example 00:08:53.790 --> 00:08:53.800 align:start position:0% 00:08:53.800 --> 00:08:58.670 align:start position:0% yeah<00:08:54.800> um<00:08:55.320> okay<00:08:55.640> let's<00:08:55.839> move<00:08:56.160> on<00:08:57.240> so<00:08:58.240> after<00:08:58.480> I'm 00:08:58.670 --> 00:08:58.680 align:start position:0% yeah um okay let's move on so after I'm 00:08:58.680 --> 00:09:01.910 align:start position:0% yeah um okay let's move on so after I'm done<00:08:59.600> testing<00:09:00.160> my<00:09:00.640> solidity<00:09:01.320> contract<00:09:01.800> I 00:09:01.910 --> 00:09:01.920 align:start position:0% done testing my solidity contract I 00:09:01.920 --> 00:09:04.230 align:start position:0% done testing my solidity contract I would<00:09:02.399> probably<00:09:02.720> want<00:09:02.880> to<00:09:03.079> create<00:09:03.640> a<00:09:03.920> user 00:09:04.230 --> 00:09:04.240 align:start position:0% would probably want to create a user 00:09:04.240 --> 00:09:06.230 align:start position:0% would probably want to create a user interface<00:09:04.720> for<00:09:04.920> my<00:09:05.120> dab<00:09:05.440> so<00:09:05.640> that<00:09:05.880> actual 00:09:06.230 --> 00:09:06.240 align:start position:0% interface for my dab so that actual 00:09:06.240 --> 00:09:10.269 align:start position:0% interface for my dab so that actual users<00:09:06.760> could<00:09:07.160> interact<00:09:07.800> with<00:09:08.000> this<00:09:08.800> simple 00:09:10.269 --> 00:09:10.279 align:start position:0% users could interact with this simple 00:09:10.279 --> 00:09:13.150 align:start position:0% users could interact with this simple stuff 00:09:13.150 --> 00:09:13.160 align:start position:0% stuff 00:09:13.160 --> 00:09:18.710 align:start position:0% stuff and<00:09:14.160> oh<00:09:14.440> yeah<00:09:14.959> one<00:09:15.560> one<00:09:15.720> more 00:09:18.710 --> 00:09:18.720 align:start position:0% 00:09:18.720 --> 00:09:20.710 align:start position:0% stuff<00:09:19.720> where 00:09:20.710 --> 00:09:20.720 align:start position:0% stuff where 00:09:20.720 --> 00:09:24.430 align:start position:0% stuff where it<00:09:21.720> yeah<00:09:22.279> so<00:09:22.600> as<00:09:22.720> in<00:09:22.920> regular<00:09:23.399> IDE<00:09:24.000> this<00:09:24.200> has<00:09:24.320> a 00:09:24.430 --> 00:09:24.440 align:start position:0% it yeah so as in regular IDE this has a 00:09:24.440 --> 00:09:27.910 align:start position:0% it yeah so as in regular IDE this has a notion<00:09:24.720> of<00:09:24.839> a<00:09:25.079> project<00:09:25.519> so<00:09:25.839> I<00:09:26.360> can<00:09:27.360> have<00:09:27.519> a<00:09:27.680> list 00:09:27.910 --> 00:09:27.920 align:start position:0% notion of a project so I can have a list 00:09:27.920 --> 00:09:30.430 align:start position:0% notion of a project so I can have a list of<00:09:28.120> files<00:09:28.640> here<00:09:29.120> which 00:09:30.430 --> 00:09:30.440 align:start position:0% of files here which 00:09:30.440 --> 00:09:33.470 align:start position:0% of files here which essentially<00:09:30.920> form<00:09:31.440> my<00:09:31.800> dab<00:09:32.800> and<00:09:32.920> I<00:09:33.000> also<00:09:33.279> have 00:09:33.470 --> 00:09:33.480 align:start position:0% essentially form my dab and I also have 00:09:33.480 --> 00:09:34.389 align:start position:0% essentially form my dab and I also have this 00:09:34.389 --> 00:09:34.399 align:start position:0% this 00:09:34.399 --> 00:09:38.230 align:start position:0% this little<00:09:35.399> web<00:09:35.720> page<00:09:36.200> which<00:09:36.480> acts<00:09:36.720> as<00:09:36.839> an 00:09:38.230 --> 00:09:38.240 align:start position:0% little web page which acts as an 00:09:38.240 --> 00:09:45.069 align:start position:0% little web page which acts as an interface<00:09:39.240> let's<00:09:39.440> hi 00:09:45.069 --> 00:09:45.079 align:start position:0% 00:09:45.079 --> 00:09:48.630 align:start position:0% that<00:09:46.079> so<00:09:46.480> this<00:09:46.720> works<00:09:47.720> basically<00:09:48.120> in<00:09:48.240> the<00:09:48.399> same 00:09:48.630 --> 00:09:48.640 align:start position:0% that so this works basically in the same 00:09:48.640 --> 00:09:51.710 align:start position:0% that so this works basically in the same way<00:09:48.800> it<00:09:48.920> would<00:09:49.120> work<00:09:49.320> in<00:09:49.600> mist 00:09:51.710 --> 00:09:51.720 align:start position:0% way it would work in mist 00:09:51.720 --> 00:09:55.230 align:start position:0% way it would work in mist or<00:09:52.720> regular<00:09:53.360> web<00:09:53.560> browser<00:09:54.240> it<00:09:54.440> communicates 00:09:55.230 --> 00:09:55.240 align:start position:0% or regular web browser it communicates 00:09:55.240 --> 00:09:56.150 align:start position:0% or regular web browser it communicates with 00:09:56.150 --> 00:09:56.160 align:start position:0% with 00:09:56.160 --> 00:09:59.430 align:start position:0% with the<00:09:57.160> with<00:09:57.399> etherum<00:09:57.839> network<00:09:58.320> using<00:09:58.800> web<00:09:59.040> free 00:09:59.430 --> 00:09:59.440 align:start position:0% the with etherum network using web free 00:09:59.440 --> 00:10:02.509 align:start position:0% the with etherum network using web free API<00:10:00.320> in<00:10:00.519> this<00:10:00.720> case<00:10:00.959> the<00:10:01.200> API<00:10:01.800> is<00:10:01.920> implemented 00:10:02.509 --> 00:10:02.519 align:start position:0% API in this case the API is implemented 00:10:02.519 --> 00:10:06.150 align:start position:0% API in this case the API is implemented by<00:10:02.680> mix<00:10:03.160> so<00:10:03.680> it<00:10:03.800> works<00:10:04.160> with<00:10:04.399> this<00:10:05.160> particular 00:10:06.150 --> 00:10:06.160 align:start position:0% by mix so it works with this particular 00:10:06.160 --> 00:10:10.110 align:start position:0% by mix so it works with this particular sandbox<00:10:06.760> blockchain<00:10:07.200> as 00:10:10.110 --> 00:10:10.120 align:start position:0% 00:10:10.120 --> 00:10:12.870 align:start position:0% well<00:10:11.120> oops 00:10:12.870 --> 00:10:12.880 align:start position:0% well oops 00:10:12.880 --> 00:10:16.670 align:start position:0% well oops sorry<00:10:13.880> now<00:10:14.079> here<00:10:14.360> the 00:10:16.670 --> 00:10:16.680 align:start position:0% sorry now here the 00:10:16.680 --> 00:10:20.310 align:start position:0% sorry now here the preview<00:10:17.680> of<00:10:17.959> this<00:10:18.200> little<00:10:18.560> web 00:10:20.310 --> 00:10:20.320 align:start position:0% preview of this little web 00:10:20.320 --> 00:10:27.230 align:start position:0% preview of this little web page<00:10:21.320> yeah<00:10:21.519> it<00:10:21.920> has<00:10:22.920> web<00:10:23.240> 0.0 00:10:27.230 --> 00:10:27.240 align:start position:0% 00:10:27.240 --> 00:10:32.829 align:start position:0% design<00:10:28.240> so<00:10:29.000> let's<00:10:29.440> test<00:10:30.160> how<00:10:31.160> my<00:10:31.480> dab 00:10:32.829 --> 00:10:32.839 align:start position:0% design so let's test how my dab 00:10:32.839 --> 00:10:36.269 align:start position:0% design so let's test how my dab Works<00:10:33.839> through<00:10:34.200> the<00:10:34.519> user<00:10:34.839> interface<00:10:35.639> I 00:10:36.269 --> 00:10:36.279 align:start position:0% Works through the user interface I 00:10:36.279 --> 00:10:43.110 align:start position:0% Works through the user interface I can<00:10:37.279> fck<00:10:37.440> an<00:10:37.600> account<00:10:38.200> oops<00:10:38.839> see<00:10:39.839> that's 00:10:43.110 --> 00:10:43.120 align:start position:0% 00:10:43.120 --> 00:10:46.230 align:start position:0% weird<00:10:44.120> fck<00:10:44.360> an<00:10:44.560> account<00:10:44.839> to<00:10:45.040> sent<00:10:45.399> to<00:10:46.040> and 00:10:46.230 --> 00:10:46.240 align:start position:0% weird fck an account to sent to and 00:10:46.240 --> 00:10:50.430 align:start position:0% weird fck an account to sent to and enter<00:10:46.519> the 00:10:50.430 --> 00:10:50.440 align:start position:0% 00:10:50.440 --> 00:11:00.910 align:start position:0% value<00:10:51.440> okay<00:10:51.720> that's 00:11:00.910 --> 00:11:00.920 align:start position:0% 00:11:00.920 --> 00:11:03.910 align:start position:0% okay<00:11:01.279> my<00:11:01.519> S<00:11:01.920> send<00:11:02.279> button<00:11:02.600> disappeared 00:11:03.910 --> 00:11:03.920 align:start position:0% okay my S send button disappeared 00:11:03.920 --> 00:11:21.269 align:start position:0% okay my S send button disappeared somewhere<00:11:04.920> let<00:11:05.079> me<00:11:05.320> restart 00:11:21.269 --> 00:11:21.279 align:start position:0% 00:11:21.279 --> 00:11:24.910 align:start position:0% it<00:11:22.279> anyway<00:11:22.680> whatever<00:11:23.360> I<00:11:23.480> do<00:11:24.240> in<00:11:24.399> the<00:11:24.600> user 00:11:24.910 --> 00:11:24.920 align:start position:0% it anyway whatever I do in the user 00:11:24.920 --> 00:11:26.990 align:start position:0% it anyway whatever I do in the user interface<00:11:25.560> also<00:11:25.959> ends<00:11:26.240> up<00:11:26.560> in<00:11:26.760> this 00:11:26.990 --> 00:11:27.000 align:start position:0% interface also ends up in this 00:11:27.000 --> 00:11:29.829 align:start position:0% interface also ends up in this transaction<00:11:27.519> list<00:11:27.800> so<00:11:27.959> I<00:11:28.240> can<00:11:29.279> let<00:11:29.399> me<00:11:29.560> check 00:11:29.829 --> 00:11:29.839 align:start position:0% transaction list so I can let me check 00:11:29.839 --> 00:11:38.230 align:start position:0% transaction list so I can let me check if<00:11:30.000> I<00:11:30.160> can<00:11:31.000> see<00:11:31.320> it 00:11:38.230 --> 00:11:38.240 align:start position:0% 00:11:38.240 --> 00:11:50.790 align:start position:0% here<00:11:39.240> yeah<00:11:39.360> so<00:11:39.600> here's<00:11:40.480> a<00:11:40.720> call<00:11:41.160> made<00:11:41.680> from 00:11:50.790 --> 00:11:50.800 align:start position:0% 00:11:50.800 --> 00:11:53.110 align:start position:0% JavaScript<00:11:51.800> this<00:11:51.880> is<00:11:52.000> a<00:11:52.160> call<00:11:52.399> to<00:11:52.560> request<00:11:52.880> of 00:11:53.110 --> 00:11:53.120 align:start position:0% JavaScript this is a call to request of 00:11:53.120 --> 00:11:56.110 align:start position:0% JavaScript this is a call to request of balance<00:11:53.800> for<00:11:54.120> this<00:11:54.320> account 00:11:56.110 --> 00:11:56.120 align:start position:0% balance for this account 00:11:56.120 --> 00:11:58.389 align:start position:0% balance for this account here<00:11:57.120> if<00:11:57.240> I<00:11:57.399> change<00:11:57.600> an<00:11:57.800> account<00:11:58.040> it<00:11:58.160> makes 00:11:58.389 --> 00:11:58.399 align:start position:0% here if I change an account it makes 00:11:58.399 --> 00:11:59.829 align:start position:0% here if I change an account it makes another<00:11:58.760> call 00:11:59.829 --> 00:11:59.839 align:start position:0% another call 00:11:59.839 --> 00:12:04.069 align:start position:0% another call and<00:11:59.959> I<00:12:00.079> can<00:12:00.200> see<00:12:00.360> these<00:12:00.519> cloes<00:12:01.079> here 00:12:04.069 --> 00:12:04.079 align:start position:0% and I can see these cloes here 00:12:04.079 --> 00:12:06.910 align:start position:0% and I can see these cloes here right<00:12:05.079> I<00:12:05.200> can<00:12:05.480> save<00:12:05.800> them<00:12:06.079> as<00:12:06.200> a<00:12:06.360> part<00:12:06.600> of<00:12:06.760> my 00:12:06.910 --> 00:12:06.920 align:start position:0% right I can save them as a part of my 00:12:06.920 --> 00:12:09.790 align:start position:0% right I can save them as a part of my testing<00:12:07.360> scenario<00:12:07.959> and<00:12:08.079> I 00:12:09.790 --> 00:12:09.800 align:start position:0% testing scenario and I 00:12:09.800 --> 00:12:13.269 align:start position:0% testing scenario and I can<00:12:10.800> addit<00:12:11.160> the<00:12:11.360> parameters<00:12:12.160> or<00:12:12.560> I<00:12:12.639> can<00:12:12.800> even 00:12:13.269 --> 00:12:13.279 align:start position:0% can addit the parameters or I can even 00:12:13.279 --> 00:12:15.750 align:start position:0% can addit the parameters or I can even debug<00:12:13.760> them<00:12:14.000> the<00:12:14.279> same<00:12:14.560> way<00:12:15.360> now<00:12:15.560> there's 00:12:15.750 --> 00:12:15.760 align:start position:0% debug them the same way now there's 00:12:15.760 --> 00:12:17.590 align:start position:0% debug them the same way now there's nothing<00:12:15.959> to<00:12:16.120> debug<00:12:16.560> here<00:12:16.760> since<00:12:16.959> it's<00:12:17.160> just<00:12:17.320> a 00:12:17.590 --> 00:12:17.600 align:start position:0% nothing to debug here since it's just a 00:12:17.600 --> 00:12:20.389 align:start position:0% nothing to debug here since it's just a single 00:12:20.389 --> 00:12:20.399 align:start position:0% 00:12:20.399 --> 00:12:24.949 align:start position:0% line<00:12:21.399> so 00:12:24.949 --> 00:12:24.959 align:start position:0% 00:12:24.959 --> 00:12:36.110 align:start position:0% yeah<00:12:25.959> that's<00:12:26.279> weird 00:12:36.110 --> 00:12:36.120 align:start position:0% 00:12:36.120 --> 00:12:41.189 align:start position:0% again<00:12:36.760> after<00:12:37.519> I'm<00:12:37.680> done<00:12:38.279> testing<00:12:38.800> my<00:12:39.440> web 00:12:41.189 --> 00:12:41.199 align:start position:0% again after I'm done testing my web 00:12:41.199 --> 00:12:44.949 align:start position:0% again after I'm done testing my web interface<00:12:42.199> I<00:12:42.320> can<00:12:42.720> package<00:12:43.240> and<00:12:43.440> deploy<00:12:43.839> my<00:12:44.639> ad 00:12:44.949 --> 00:12:44.959 align:start position:0% interface I can package and deploy my ad 00:12:44.959 --> 00:12:48.750 align:start position:0% interface I can package and deploy my ad to<00:12:45.279> real<00:12:46.160> Network<00:12:46.760> and<00:12:47.240> this<00:12:47.480> has<00:12:47.680> this 00:12:48.750 --> 00:12:48.760 align:start position:0% to real Network and this has this 00:12:48.760 --> 00:12:50.990 align:start position:0% to real Network and this has this deployment<00:12:49.760> wizard<00:12:50.279> I'm<00:12:50.399> not<00:12:50.560> going<00:12:50.760> to 00:12:50.990 --> 00:12:51.000 align:start position:0% deployment wizard I'm not going to 00:12:51.000 --> 00:12:53.150 align:start position:0% deployment wizard I'm not going to demonstrate<00:12:51.440> it<00:12:51.600> now<00:12:51.880> because<00:12:52.040> it<00:12:52.240> requires 00:12:53.150 --> 00:12:53.160 align:start position:0% demonstrate it now because it requires 00:12:53.160 --> 00:12:54.550 align:start position:0% demonstrate it now because it requires an<00:12:53.320> actual<00:12:53.600> network 00:12:54.550 --> 00:12:54.560 align:start position:0% an actual network 00:12:54.560 --> 00:12:57.069 align:start position:0% an actual network connection<00:12:55.560> but<00:12:55.760> the<00:12:55.880> idea<00:12:56.240> is<00:12:56.440> it<00:12:56.639> packages 00:12:57.069 --> 00:12:57.079 align:start position:0% connection but the idea is it packages 00:12:57.079 --> 00:12:59.629 align:start position:0% connection but the idea is it packages your<00:12:57.360> dab<00:12:57.880> and<00:12:58.480> pushes<00:12:58.800> it<00:12:58.920> to 00:12:59.629 --> 00:12:59.639 align:start position:0% your dab and pushes it to 00:12:59.639 --> 00:13:02.550 align:start position:0% your dab and pushes it to to<00:13:00.639> uh<00:13:00.920> swarm 00:13:02.550 --> 00:13:02.560 align:start position:0% to uh swarm 00:13:02.560 --> 00:13:06.150 align:start position:0% to uh swarm or<00:13:03.560> ipfs<00:13:04.199> or<00:13:04.399> whatever<00:13:05.079> it's<00:13:05.360> not<00:13:05.560> supported 00:13:06.150 --> 00:13:06.160 align:start position:0% or ipfs or whatever it's not supported 00:13:06.160 --> 00:13:08.550 align:start position:0% or ipfs or whatever it's not supported yet<00:13:06.480> but<00:13:06.639> for<00:13:06.839> now<00:13:07.000> it<00:13:07.160> can<00:13:07.279> only<00:13:07.800> deploy<00:13:08.279> to 00:13:08.550 --> 00:13:08.560 align:start position:0% yet but for now it can only deploy to 00:13:08.560 --> 00:13:11.389 align:start position:0% yet but for now it can only deploy to regular<00:13:09.000> HTTP<00:13:09.760> server<00:13:10.760> and<00:13:10.880> it<00:13:11.079> also 00:13:11.389 --> 00:13:11.399 align:start position:0% regular HTTP server and it also 00:13:11.399 --> 00:13:14.670 align:start position:0% regular HTTP server and it also registers<00:13:12.320> a<00:13:12.519> URL<00:13:13.000> for<00:13:13.199> the<00:13:13.399> da 00:13:14.670 --> 00:13:14.680 align:start position:0% registers a URL for the da 00:13:14.680 --> 00:13:18.710 align:start position:0% registers a URL for the da in<00:13:15.680> the<00:13:16.040> registry<00:13:16.600> contract<00:13:17.120> which<00:13:17.720> is 00:13:18.710 --> 00:13:18.720 align:start position:0% in the registry contract which is 00:13:18.720 --> 00:13:22.629 align:start position:0% in the registry contract which is already<00:13:19.399> on<00:13:20.399> Main<00:13:20.680> ethereum<00:13:21.160> Network 00:13:22.629 --> 00:13:22.639 align:start position:0% already on Main ethereum Network 00:13:22.639 --> 00:13:25.150 align:start position:0% already on Main ethereum Network there<00:13:23.639> so<00:13:23.880> this<00:13:24.040> allows<00:13:24.480> pretty<00:13:24.800> complex 00:13:25.150 --> 00:13:25.160 align:start position:0% there so this allows pretty complex 00:13:25.160 --> 00:13:25.760 align:start position:0% there so this allows pretty complex deployment 00:13:25.760 --> 00:13:25.770 align:start position:0% deployment 00:13:25.770 --> 00:13:27.550 align:start position:0% deployment [Music] 00:13:27.550 --> 00:13:27.560 align:start position:0% [Music] 00:13:27.560 --> 00:13:29.590 align:start position:0% [Music] scenarios<00:13:28.560> you<00:13:28.680> can<00:13:28.839> have<00:13:29.160> multiple 00:13:29.590 --> 00:13:29.600 align:start position:0% scenarios you can have multiple 00:13:29.600 --> 00:13:31.230 align:start position:0% scenarios you can have multiple contracts<00:13:30.160> depending<00:13:30.519> on<00:13:30.680> each<00:13:30.839> other<00:13:31.120> you 00:13:31.230 --> 00:13:31.240 align:start position:0% contracts depending on each other you 00:13:31.240 --> 00:13:33.870 align:start position:0% contracts depending on each other you can<00:13:31.440> set<00:13:31.639> up<00:13:31.800> a<00:13:31.959> sequence<00:13:32.560> on<00:13:33.519> how<00:13:33.720> these 00:13:33.870 --> 00:13:33.880 align:start position:0% can set up a sequence on how these 00:13:33.880 --> 00:13:35.590 align:start position:0% can set up a sequence on how these contracts<00:13:34.279> are<00:13:34.480> deployed<00:13:34.959> and<00:13:35.199> which 00:13:35.590 --> 00:13:35.600 align:start position:0% contracts are deployed and which 00:13:35.600 --> 00:13:38.269 align:start position:0% contracts are deployed and which transactions<00:13:36.199> are<00:13:36.440> called<00:13:37.320> for<00:13:37.519> deployment 00:13:38.269 --> 00:13:38.279 align:start position:0% transactions are called for deployment 00:13:38.279 --> 00:13:42.030 align:start position:0% transactions are called for deployment and<00:13:38.480> so 00:13:42.030 --> 00:13:42.040 align:start position:0% 00:13:42.040 --> 00:13:44.750 align:start position:0% on<00:13:43.040> another<00:13:43.480> little<00:13:43.800> cool<00:13:44.079> feature<00:13:44.440> I<00:13:44.560> can 00:13:44.750 --> 00:13:44.760 align:start position:0% on another little cool feature I can 00:13:44.760 --> 00:13:47.110 align:start position:0% on another little cool feature I can demonstrate<00:13:45.480> here 00:13:47.110 --> 00:13:47.120 align:start position:0% demonstrate here 00:13:47.120 --> 00:13:50.470 align:start position:0% demonstrate here is<00:13:48.120> gas<00:13:48.440> estimation 00:13:50.470 --> 00:13:50.480 align:start position:0% is gas estimation 00:13:50.480 --> 00:13:52.790 align:start position:0% is gas estimation yeah<00:13:51.480> for 00:13:52.790 --> 00:13:52.800 align:start position:0% yeah for 00:13:52.800 --> 00:13:57.430 align:start position:0% yeah for solidity<00:13:53.800> so<00:13:54.040> I<00:13:54.600> can<00:13:55.600> basically<00:13:56.079> see<00:13:56.680> which 00:13:57.430 --> 00:13:57.440 align:start position:0% solidity so I can basically see which 00:13:57.440 --> 00:13:59.749 align:start position:0% solidity so I can basically see which statements<00:13:57.959> and<00:13:58.199> which<00:13:58.560> expression 00:13:59.749 --> 00:13:59.759 align:start position:0% statements and which expression 00:13:59.759 --> 00:14:02.430 align:start position:0% statements and which expression consume<00:14:00.759> the<00:14:00.959> most<00:14:01.360> and<00:14:01.519> the<00:14:01.639> least<00:14:01.920> amount<00:14:02.199> of 00:14:02.430 --> 00:14:02.440 align:start position:0% consume the most and the least amount of 00:14:02.440 --> 00:14:04.550 align:start position:0% consume the most and the least amount of gas<00:14:02.759> and<00:14:02.880> it<00:14:03.079> also<00:14:03.360> shows<00:14:03.720> the<00:14:03.959> estimations 00:14:04.550 --> 00:14:04.560 align:start position:0% gas and it also shows the estimations 00:14:04.560 --> 00:14:08.030 align:start position:0% gas and it also shows the estimations for<00:14:04.880> functions<00:14:05.839> this<00:14:05.959> is<00:14:06.079> a<00:14:06.240> l<00:14:06.680> bound<00:14:07.560> estimate 00:14:08.030 --> 00:14:08.040 align:start position:0% for functions this is a l bound estimate 00:14:08.040 --> 00:14:12.590 align:start position:0% for functions this is a l bound estimate of<00:14:08.240> how<00:14:08.440> much<00:14:08.800> gas<00:14:09.120> this<00:14:09.320> function<00:14:09.759> can 00:14:12.590 --> 00:14:12.600 align:start position:0% 00:14:12.600 --> 00:14:18.910 align:start position:0% consume<00:14:13.600> which<00:14:13.800> can<00:14:13.959> be<00:14:14.199> pretty 00:14:18.910 --> 00:14:18.920 align:start position:0% 00:14:18.920 --> 00:14:22.790 align:start position:0% useful<00:14:19.920> okay<00:14:20.639> so<00:14:21.639> as<00:14:21.759> you<00:14:21.920> can<00:14:22.040> see<00:14:22.240> the<00:14:22.399> focus 00:14:22.790 --> 00:14:22.800 align:start position:0% useful okay so as you can see the focus 00:14:22.800 --> 00:14:30.790 align:start position:0% useful okay so as you can see the focus so<00:14:23.160> far<00:14:23.399> has<00:14:23.560> been<00:14:23.759> on<00:14:24.040> solidity<00:14:24.600> features<00:14:25.199> so 00:14:30.790 --> 00:14:30.800 align:start position:0% 00:14:30.800 --> 00:14:32.870 align:start position:0% we<00:14:30.920> don't<00:14:31.199> support<00:14:31.680> web<00:14:31.920> debugging<00:14:32.519> yet<00:14:32.720> and 00:14:32.870 --> 00:14:32.880 align:start position:0% we don't support web debugging yet and 00:14:32.880 --> 00:14:35.110 align:start position:0% we don't support web debugging yet and stuff<00:14:33.120> like<00:14:33.320> that<00:14:33.560> and<00:14:33.720> if<00:14:33.839> you<00:14:33.959> would<00:14:34.160> like<00:14:34.320> to 00:14:35.110 --> 00:14:35.120 align:start position:0% stuff like that and if you would like to 00:14:35.120 --> 00:14:37.790 align:start position:0% stuff like that and if you would like to use<00:14:35.639> web<00:14:35.880> framework<00:14:36.440> such<00:14:36.639> as<00:14:37.079> metor<00:14:37.600> for 00:14:37.790 --> 00:14:37.800 align:start position:0% use web framework such as metor for 00:14:37.800 --> 00:14:40.550 align:start position:0% use web framework such as metor for example<00:14:38.279> this<00:14:38.399> would<00:14:38.600> be<00:14:38.839> complicated<00:14:39.600> here 00:14:40.550 --> 00:14:40.560 align:start position:0% example this would be complicated here 00:14:40.560 --> 00:14:47.350 align:start position:0% example this would be complicated here but<00:14:40.920> the<00:14:41.160> goal<00:14:41.480> is<00:14:41.639> to<00:14:41.800> support<00:14:42.240> that<00:14:42.440> as 00:14:47.350 --> 00:14:47.360 align:start position:0% 00:14:47.360 --> 00:14:50.590 align:start position:0% well<00:14:48.360> so<00:14:48.959> yeah<00:14:49.079> you<00:14:49.160> can<00:14:49.320> use<00:14:49.560> this<00:14:49.720> tool<00:14:50.040> for 00:14:50.590 --> 00:14:50.600 align:start position:0% well so yeah you can use this tool for 00:14:50.600 --> 00:14:53.350 align:start position:0% well so yeah you can use this tool for prototyping<00:14:51.279> your<00:14:51.519> dep<00:14:51.920> really<00:14:52.279> quickly<00:14:53.279> I 00:14:53.350 --> 00:14:53.360 align:start position:0% prototyping your dep really quickly I 00:14:53.360 --> 00:15:08.030 align:start position:0% prototyping your dep really quickly I mean<00:14:53.639> it<00:14:53.920> should<00:14:54.240> just<00:14:54.560> work 00:15:08.030 --> 00:15:08.040 align:start position:0% 00:15:08.040 --> 00:15:25.150 align:start position:0% okay<00:15:09.040> what<00:15:09.199> else<00:15:09.399> do<00:15:09.560> we<00:15:09.720> have<00:15:10.360> here<00:15:11.360> let 00:15:25.150 --> 00:15:25.160 align:start position:0% 00:15:25.160 --> 00:15:36.389 align:start position:0% me<00:15:26.160> just<00:15:26.399> a<00:15:26.680> SI 00:15:36.389 --> 00:15:36.399 align:start position:0% 00:15:36.399 --> 00:15:37.829 align:start position:0% now<00:15:36.600> there<00:15:36.759> was<00:15:36.959> a<00:15:37.079> number<00:15:37.279> of<00:15:37.360> features<00:15:37.720> we 00:15:37.829 --> 00:15:37.839 align:start position:0% now there was a number of features we 00:15:37.839 --> 00:15:40.550 align:start position:0% now there was a number of features we want<00:15:37.920> to<00:15:38.079> add<00:15:38.240> to<00:15:38.399> this<00:15:38.639> program<00:15:39.560> including 00:15:40.550 --> 00:15:40.560 align:start position:0% want to add to this program including 00:15:40.560 --> 00:15:43.269 align:start position:0% want to add to this program including JavaScript<00:15:41.120> debugging<00:15:41.920> and<00:15:42.120> so<00:15:42.319> on<00:15:42.759> you<00:15:42.880> can 00:15:43.269 --> 00:15:43.279 align:start position:0% JavaScript debugging and so on you can 00:15:43.279 --> 00:15:46.470 align:start position:0% JavaScript debugging and so on you can use<00:15:44.279> your<00:15:44.519> regular<00:15:45.000> browser<00:15:45.440> for<00:15:45.680> now<00:15:46.240> to 00:15:46.470 --> 00:15:46.480 align:start position:0% use your regular browser for now to 00:15:46.480 --> 00:15:49.269 align:start position:0% use your regular browser for now to debug<00:15:47.079> JavaScript<00:15:47.680> things<00:15:48.560> and<00:15:48.720> you<00:15:48.839> can<00:15:49.000> use 00:15:49.269 --> 00:15:49.279 align:start position:0% debug JavaScript things and you can use 00:15:49.279 --> 00:15:51.189 align:start position:0% debug JavaScript things and you can use Chrome<00:15:49.639> development<00:15:50.040> tools<00:15:50.360> for 00:15:51.189 --> 00:15:51.199 align:start position:0% Chrome development tools for 00:15:51.199 --> 00:15:54.749 align:start position:0% Chrome development tools for example<00:15:52.199> um<00:15:52.920> another<00:15:53.240> thing<00:15:53.440> we<00:15:53.560> want<00:15:53.720> to 00:15:54.749 --> 00:15:54.759 align:start position:0% example um another thing we want to 00:15:54.759 --> 00:15:57.509 align:start position:0% example um another thing we want to add<00:15:55.759> is 00:15:57.509 --> 00:15:57.519 align:start position:0% add is 00:15:57.519 --> 00:16:00.629 align:start position:0% add is um<00:15:58.519> test<00:15:59.040> driven<00:15:59.360> development<00:16:00.079> so<00:16:00.240> we<00:16:00.360> want<00:16:00.480> to 00:16:00.629 --> 00:16:00.639 align:start position:0% um test driven development so we want to 00:16:00.639 --> 00:16:04.590 align:start position:0% um test driven development so we want to use<00:16:01.360> JavaScript<00:16:02.319> to<00:16:03.319> provide<00:16:03.600> a<00:16:03.720> way<00:16:03.920> to<00:16:04.160> write 00:16:04.590 --> 00:16:04.600 align:start position:0% use JavaScript to provide a way to write 00:16:04.600 --> 00:16:07.189 align:start position:0% use JavaScript to provide a way to write the<00:16:04.759> unit<00:16:05.120> test<00:16:05.440> for<00:16:05.600> your<00:16:06.240> contract<00:16:06.959> both 00:16:07.189 --> 00:16:07.199 align:start position:0% the unit test for your contract both 00:16:07.199 --> 00:16:10.710 align:start position:0% the unit test for your contract both solidity<00:16:07.680> contracts<00:16:08.279> and<00:16:09.199> a<00:16:09.440> JavaScript<00:16:10.440> web 00:16:10.710 --> 00:16:10.720 align:start position:0% solidity contracts and a JavaScript web 00:16:10.720 --> 00:16:14.309 align:start position:0% solidity contracts and a JavaScript web interface<00:16:11.279> in<00:16:11.759> in<00:16:11.959> JavaScript 00:16:14.309 --> 00:16:14.319 align:start position:0% interface in in JavaScript 00:16:14.319 --> 00:16:22.350 align:start position:0% interface in in JavaScript itself 00:16:22.350 --> 00:16:22.360 align:start position:0% 00:16:22.360 --> 00:16:24.910 align:start position:0% yeah<00:16:23.360> now<00:16:23.560> this<00:16:23.800> been<00:16:24.000> we've<00:16:24.160> been<00:16:24.319> over<00:16:24.720> this 00:16:24.910 --> 00:16:24.920 align:start position:0% yeah now this been we've been over this 00:16:24.920 --> 00:16:26.629 align:start position:0% yeah now this been we've been over this so 00:16:26.629 --> 00:16:26.639 align:start position:0% so 00:16:26.639 --> 00:16:29.829 align:start position:0% so far<00:16:27.639> uh<00:16:28.319> yeah 00:16:29.829 --> 00:16:29.839 align:start position:0% far uh yeah 00:16:29.839 --> 00:16:33.509 align:start position:0% far uh yeah so<00:16:30.480> and<00:16:30.839> that's<00:16:31.160> basically<00:16:31.560> it<00:16:31.880> so 00:16:33.509 --> 00:16:33.519 align:start position:0% so and that's basically it so 00:16:33.519 --> 00:16:37.590 align:start position:0% so and that's basically it so we<00:16:34.519> really<00:16:34.800> need<00:16:35.440> feedback<00:16:35.880> from<00:16:36.160> developer 00:16:37.590 --> 00:16:37.600 align:start position:0% we really need feedback from developer 00:16:37.600 --> 00:16:39.670 align:start position:0% we really need feedback from developer now<00:16:38.600> and<00:16:38.800> you<00:16:38.880> can 00:16:39.670 --> 00:16:39.680 align:start position:0% now and you can 00:16:39.680 --> 00:16:44.150 align:start position:0% now and you can get<00:16:40.680> binary<00:16:41.519> releases<00:16:42.240> you<00:16:42.360> can<00:16:43.160> visit<00:16:43.480> our 00:16:44.150 --> 00:16:44.160 align:start position:0% get binary releases you can visit our 00:16:44.160 --> 00:16:49.030 align:start position:0% get binary releases you can visit our EAB<00:16:44.680> page<00:16:44.959> or<00:16:45.240> viser<00:16:45.920> chat<00:16:47.000> and<00:16:48.000> let<00:16:48.199> us<00:16:48.720> know 00:16:49.030 --> 00:16:49.040 align:start position:0% EAB page or viser chat and let us know 00:16:49.040 --> 00:16:51.150 align:start position:0% EAB page or viser chat and let us know what<00:16:49.199> you<00:16:49.360> think<00:16:49.560> of 00:16:51.150 --> 00:16:51.160 align:start position:0% what you think of 00:16:51.160 --> 00:16:53.949 align:start position:0% what you think of it<00:16:52.160> yeah<00:16:52.399> that's<00:16:52.600> basically<00:16:53.160> thank<00:16:53.360> you<00:16:53.759> very 00:16:53.949 --> 00:16:53.959 align:start position:0% it yeah that's basically thank you very 00:16:53.959 --> 00:17:01.180 align:start position:0% it yeah that's basically thank you very much 00:17:01.180 --> 00:17:01.190 align:start position:0% 00:17:01.190 --> 00:17:05.079 align:start position:0% [Music]