WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:16.470 align:start position:0% [Applause] 00:00:16.470 --> 00:00:16.480 align:start position:0% 00:00:16.480 --> 00:00:19.750 align:start position:0% developer<00:00:17.480> conference<00:00:17.930> Apple<00:00:18.110> in<00:00:18.610> for<00:00:19.610> those 00:00:19.750 --> 00:00:19.760 align:start position:0% developer conference Apple in for those 00:00:19.760 --> 00:00:24.730 align:start position:0% developer conference Apple in for those of<00:00:20.090> you<00:00:20.270> who<00:00:20.570> don't<00:00:20.960> know<00:00:21.470> us<00:00:23.380> at<00:00:24.380> open 00:00:24.730 --> 00:00:24.740 align:start position:0% of you who don't know us at open 00:00:24.740 --> 00:00:27.840 align:start position:0% of you who don't know us at open zeppelin<00:00:25.189> we<00:00:25.460> build<00:00:25.939> developer<00:00:26.180> tools<00:00:26.750> and 00:00:27.840 --> 00:00:27.850 align:start position:0% zeppelin we build developer tools and 00:00:27.850 --> 00:00:31.109 align:start position:0% zeppelin we build developer tools and formalities<00:00:28.850> of<00:00:29.119> decentralized<00:00:29.780> systems 00:00:31.109 --> 00:00:31.119 align:start position:0% formalities of decentralized systems 00:00:31.119 --> 00:00:33.910 align:start position:0% formalities of decentralized systems which<00:00:32.119> power<00:00:32.449> multi-million<00:00:33.320> blowers 00:00:33.910 --> 00:00:33.920 align:start position:0% which power multi-million blowers 00:00:33.920 --> 00:00:38.080 align:start position:0% which power multi-million blowers economies<00:00:34.930> we<00:00:35.930> fear<00:00:36.830> on<00:00:36.980> foundation<00:00:37.699> on<00:00:37.879> the 00:00:38.080 --> 00:00:38.090 align:start position:0% economies we fear on foundation on the 00:00:38.090 --> 00:00:45.430 align:start position:0% economies we fear on foundation on the solidity<00:00:38.480> compiler<00:00:39.020> outlet<00:00:39.620> and<00:00:43.269> and<00:00:44.440> we 00:00:45.430 --> 00:00:45.440 align:start position:0% solidity compiler outlet and and we 00:00:45.440 --> 00:00:47.710 align:start position:0% solidity compiler outlet and and we created<00:00:45.920> the<00:00:46.129> most<00:00:46.580> popular<00:00:47.000> smart<00:00:47.269> contracts 00:00:47.710 --> 00:00:47.720 align:start position:0% created the most popular smart contracts 00:00:47.720 --> 00:00:49.990 align:start position:0% created the most popular smart contracts library<00:00:48.170> which<00:00:48.920> has<00:00:49.129> over<00:00:49.580> 1<00:00:49.760> million 00:00:49.990 --> 00:00:50.000 align:start position:0% library which has over 1 million 00:00:50.000 --> 00:00:54.100 align:start position:0% library which has over 1 million downloads<00:00:50.300> and<00:00:51.040> over<00:00:52.120> 180<00:00:53.120> contributors<00:00:53.900> as 00:00:54.100 --> 00:00:54.110 align:start position:0% downloads and over 180 contributors as 00:00:54.110 --> 00:00:56.890 align:start position:0% downloads and over 180 contributors as you<00:00:54.769> can<00:00:54.920> see<00:00:55.129> we<00:00:55.400> spend<00:00:55.790> some<00:00:56.030> time<00:00:56.299> writing 00:00:56.890 --> 00:00:56.900 align:start position:0% you can see we spend some time writing 00:00:56.900 --> 00:01:00.969 align:start position:0% you can see we spend some time writing and<00:00:57.470> auditing<00:00:58.420> smart<00:00:59.420> contracts<00:00:59.870> and<00:01:00.110> today 00:01:00.969 --> 00:01:00.979 align:start position:0% and auditing smart contracts and today 00:01:00.979 --> 00:01:03.969 align:start position:0% and auditing smart contracts and today i'm<00:01:01.309> excited<00:01:01.699> and<00:01:02.269> delighted<00:01:02.479> to<00:01:03.170> share<00:01:03.680> my 00:01:03.969 --> 00:01:03.979 align:start position:0% i'm excited and delighted to share my 00:01:03.979 --> 00:01:06.310 align:start position:0% i'm excited and delighted to share my findings<00:01:04.220> on<00:01:04.670> how<00:01:04.879> you<00:01:05.210> can<00:01:05.449> improve<00:01:06.049> your 00:01:06.310 --> 00:01:06.320 align:start position:0% findings on how you can improve your 00:01:06.320 --> 00:01:09.160 align:start position:0% findings on how you can improve your solidity<00:01:07.130> developer<00:01:07.820> experience<00:01:08.360> with<00:01:08.750> hot 00:01:09.160 --> 00:01:09.170 align:start position:0% solidity developer experience with hot 00:01:09.170 --> 00:01:12.250 align:start position:0% solidity developer experience with hot loader<00:01:10.330> but<00:01:11.330> Before<00:01:11.690> we<00:01:11.720> jump<00:01:11.810> to<00:01:12.080> the<00:01:12.170> next 00:01:12.250 --> 00:01:12.260 align:start position:0% loader but Before we jump to the next 00:01:12.260 --> 00:01:14.290 align:start position:0% loader but Before we jump to the next slide<00:01:12.560> please<00:01:12.979> raise<00:01:13.430> your<00:01:13.460> hand<00:01:13.909> if<00:01:14.120> you<00:01:14.270> have 00:01:14.290 --> 00:01:14.300 align:start position:0% slide please raise your hand if you have 00:01:14.300 --> 00:01:19.470 align:start position:0% slide please raise your hand if you have a<00:01:14.480> written<00:01:14.980> smart<00:01:15.980> contract<00:01:16.400> in<00:01:16.520> solidity<00:01:18.340> yes 00:01:19.470 --> 00:01:19.480 align:start position:0% a written smart contract in solidity yes 00:01:19.480 --> 00:01:25.090 align:start position:0% a written smart contract in solidity yes developers<00:01:20.480> developers<00:01:21.020> workers<00:01:22.660> yeah<00:01:24.100> with 00:01:25.090 --> 00:01:25.100 align:start position:0% developers developers workers yeah with 00:01:25.100 --> 00:01:29.800 align:start position:0% developers developers workers yeah with the<00:01:25.310> companies<00:01:27.040> by<00:01:28.040> today's<00:01:28.540> developers<00:01:29.540> used 00:01:29.800 --> 00:01:29.810 align:start position:0% the companies by today's developers used 00:01:29.810 --> 00:01:32.440 align:start position:0% the companies by today's developers used it<00:01:29.960> to<00:01:30.110> ship<00:01:30.320> software<00:01:30.500> and<00:01:31.100> it<00:01:31.940> was<00:01:32.120> literally 00:01:32.440 --> 00:01:32.450 align:start position:0% it to ship software and it was literally 00:01:32.450 --> 00:01:35.830 align:start position:0% it to ship software and it was literally immutable<00:01:33.170> code<00:01:33.550> once<00:01:34.550> you<00:01:34.730> stupid<00:01:35.120> you<00:01:35.510> can't 00:01:35.830 --> 00:01:35.840 align:start position:0% immutable code once you stupid you can't 00:01:35.840 --> 00:01:38.980 align:start position:0% immutable code once you stupid you can't change<00:01:36.170> the<00:01:36.380> single<00:01:36.770> line<00:01:36.950> on<00:01:37.160> it<00:01:37.310> it<00:01:37.990> affected 00:01:38.980 --> 00:01:38.990 align:start position:0% change the single line on it it affected 00:01:38.990 --> 00:01:40.000 align:start position:0% change the single line on it it affected their<00:01:39.200> practices 00:01:40.000 --> 00:01:40.010 align:start position:0% their practices 00:01:40.010 --> 00:01:42.610 align:start position:0% their practices Backlund<00:01:40.460> the<00:01:41.210> workers<00:01:41.570> were<00:01:41.780> really<00:01:42.200> careful 00:01:42.610 --> 00:01:42.620 align:start position:0% Backlund the workers were really careful 00:01:42.620 --> 00:01:44.530 align:start position:0% Backlund the workers were really careful about<00:01:42.650> testing<00:01:43.550> and<00:01:43.670> point<00:01:43.940> in<00:01:44.090> their<00:01:44.300> code 00:01:44.530 --> 00:01:44.540 align:start position:0% about testing and point in their code 00:01:44.540 --> 00:01:47.800 align:start position:0% about testing and point in their code because<00:01:45.350> he<00:01:45.530> knew<00:01:45.830> once<00:01:46.640> it's<00:01:46.880> out<00:01:47.060> you<00:01:47.570> can 00:01:47.800 --> 00:01:47.810 align:start position:0% because he knew once it's out you can 00:01:47.810 --> 00:01:50.170 align:start position:0% because he knew once it's out you can change<00:01:48.110> it<00:01:48.260> does<00:01:49.190> it<00:01:49.340> remind<00:01:49.640> you<00:01:49.880> something 00:01:50.170 --> 00:01:50.180 align:start position:0% change it does it remind you something 00:01:50.180 --> 00:01:57.060 align:start position:0% change it does it remind you something something<00:01:51.020> we<00:01:51.440> do<00:01:51.560> today 00:01:57.060 --> 00:01:57.070 align:start position:0% 00:01:57.070 --> 00:02:00.789 align:start position:0% this<00:01:58.070> is<00:01:58.220> Internet<00:01:58.790> Explorer<00:01:59.090> 6<00:01:59.390> is<00:01:59.720> the<00:02:00.590> first 00:02:00.789 --> 00:02:00.799 align:start position:0% this is Internet Explorer 6 is the first 00:02:00.799 --> 00:02:03.070 align:start position:0% this is Internet Explorer 6 is the first browser<00:02:01.040> ever<00:02:01.520> used<00:02:01.880> and<00:02:02.119> is<00:02:02.750> the<00:02:02.869> first 00:02:03.070 --> 00:02:03.080 align:start position:0% browser ever used and is the first 00:02:03.080 --> 00:02:06.580 align:start position:0% browser ever used and is the first browser<00:02:03.259> I've<00:02:03.770> written<00:02:04.159> called<00:02:04.729> for<00:02:05.440> back<00:02:06.440> in 00:02:06.580 --> 00:02:06.590 align:start position:0% browser I've written called for back in 00:02:06.590 --> 00:02:09.550 align:start position:0% browser I've written called for back in the<00:02:06.710> day<00:02:06.860> it<00:02:07.400> was<00:02:07.580> boiling<00:02:08.050> it<00:02:09.050> was<00:02:09.229> working<00:02:09.500> in 00:02:09.550 --> 00:02:09.560 align:start position:0% the day it was boiling it was working in 00:02:09.560 --> 00:02:12.690 align:start position:0% the day it was boiling it was working in the<00:02:09.649> common<00:02:09.979> way<00:02:10.009> you<00:02:10.880> would<00:02:11.090> edit<00:02:11.600> your 00:02:12.690 --> 00:02:12.700 align:start position:0% the common way you would edit your 00:02:12.700 --> 00:02:15.729 align:start position:0% the common way you would edit your mixture<00:02:13.700> of<00:02:13.760> JavaScript<00:02:14.750> and<00:02:14.840> HTML<00:02:15.470> in 00:02:15.729 --> 00:02:15.739 align:start position:0% mixture of JavaScript and HTML in 00:02:15.739 --> 00:02:19.470 align:start position:0% mixture of JavaScript and HTML in external<00:02:16.280> editor<00:02:16.730> then<00:02:17.480> you<00:02:17.600> save<00:02:17.930> it<00:02:18.110> and 00:02:19.470 --> 00:02:19.480 align:start position:0% external editor then you save it and 00:02:19.480 --> 00:02:22.000 align:start position:0% external editor then you save it and once<00:02:20.480> you<00:02:20.600> say<00:02:20.840> you<00:02:21.230> go<00:02:21.410> back<00:02:21.620> to<00:02:21.739> the<00:02:21.830> browser 00:02:22.000 --> 00:02:22.010 align:start position:0% once you say you go back to the browser 00:02:22.010 --> 00:02:24.970 align:start position:0% once you say you go back to the browser and<00:02:22.489> you<00:02:22.550> first<00:02:22.910> the<00:02:23.030> page<00:02:23.270> to<00:02:23.959> see<00:02:24.200> what<00:02:24.739> has 00:02:24.970 --> 00:02:24.980 align:start position:0% and you first the page to see what has 00:02:24.980 --> 00:02:27.550 align:start position:0% and you first the page to see what has changed<00:02:25.010> and<00:02:25.660> if<00:02:26.660> you<00:02:26.840> have<00:02:27.230> to<00:02:27.380> change 00:02:27.550 --> 00:02:27.560 align:start position:0% changed and if you have to change 00:02:27.560 --> 00:02:29.080 align:start position:0% changed and if you have to change something<00:02:27.650> else<00:02:28.010> you<00:02:28.250> have<00:02:28.280> to<00:02:28.459> do<00:02:28.700> the<00:02:28.880> game 00:02:29.080 --> 00:02:29.090 align:start position:0% something else you have to do the game 00:02:29.090 --> 00:02:34.509 align:start position:0% something else you have to do the game and<00:02:30.550> just<00:02:31.550> remind<00:02:31.970> you<00:02:32.120> something<00:02:33.069> and<00:02:34.069> what<00:02:34.489> I 00:02:34.509 --> 00:02:34.519 align:start position:0% and just remind you something and what I 00:02:34.519 --> 00:02:37.809 align:start position:0% and just remind you something and what I think<00:02:34.790> how<00:02:35.440> rich<00:02:36.440> do<00:02:36.680> our<00:02:36.830> schools<00:02:37.340> in<00:02:37.670> the 00:02:37.809 --> 00:02:37.819 align:start position:0% think how rich do our schools in the 00:02:37.819 --> 00:02:39.190 align:start position:0% think how rich do our schools in the exports<00:02:38.360> its<00:02:38.600> head 00:02:39.190 --> 00:02:39.200 align:start position:0% exports its head 00:02:39.200 --> 00:02:41.949 align:start position:0% exports its head the<00:02:39.800> answer<00:02:40.040> is<00:02:40.160> no<00:02:40.610> it<00:02:41.000> hasn't<00:02:41.300> been<00:02:41.630> having 00:02:41.949 --> 00:02:41.959 align:start position:0% the answer is no it hasn't been having 00:02:41.959 --> 00:02:45.550 align:start position:0% the answer is no it hasn't been having any<00:02:42.170> developers<00:02:42.920> DOS<00:02:43.220> and<00:02:43.930> I'm<00:02:44.930> here<00:02:45.290> not<00:02:45.500> to 00:02:45.550 --> 00:02:45.560 align:start position:0% any developers DOS and I'm here not to 00:02:45.560 --> 00:02:47.949 align:start position:0% any developers DOS and I'm here not to smash<00:02:45.980> Internet<00:02:46.400> Explorer<00:02:46.790> 6<00:02:47.120> instead<00:02:47.660> it<00:02:47.840> was 00:02:47.949 --> 00:02:47.959 align:start position:0% smash Internet Explorer 6 instead it was 00:02:47.959 --> 00:02:51.690 align:start position:0% smash Internet Explorer 6 instead it was a<00:02:48.019> great<00:02:48.470> piece<00:02:48.650> of<00:02:48.830> technology<00:02:48.890> at<00:02:49.430> the<00:02:49.549> time 00:02:51.690 --> 00:02:51.700 align:start position:0% 00:02:51.700 --> 00:02:54.509 align:start position:0% you<00:02:52.700> will<00:02:52.850> see<00:02:53.060> a<00:02:53.269> lot<00:02:53.390> of<00:02:53.420> similarities<00:02:54.170> about 00:02:54.509 --> 00:02:54.519 align:start position:0% you will see a lot of similarities about 00:02:54.519 --> 00:02:58.270 align:start position:0% you will see a lot of similarities about how<00:02:55.600> developer<00:02:56.600> tools<00:02:56.930> were<00:02:57.380> back<00:02:57.709> then<00:02:58.100> in 00:02:58.270 --> 00:02:58.280 align:start position:0% how developer tools were back then in 00:02:58.280 --> 00:03:00.430 align:start position:0% how developer tools were back then in the<00:02:58.370> days<00:02:58.580> and<00:02:58.910> how<00:02:59.239> developers<00:02:59.840> tools<00:03:00.140> are 00:03:00.430 --> 00:03:00.440 align:start position:0% the days and how developers tools are 00:03:00.440 --> 00:03:03.280 align:start position:0% the days and how developers tools are today<00:03:00.980> at<00:03:01.340> the<00:03:01.850> blockchain<00:03:02.180> and<00:03:02.630> go<00:03:02.900> change<00:03:03.170> in 00:03:03.280 --> 00:03:03.290 align:start position:0% today at the blockchain and go change in 00:03:03.290 --> 00:03:09.589 align:start position:0% today at the blockchain and go change in general 00:03:09.589 --> 00:03:09.599 align:start position:0% 00:03:09.599 --> 00:03:14.190 align:start position:0% we're<00:03:10.599> gonna<00:03:10.750> see<00:03:11.080> quick<00:03:11.700> video<00:03:12.959> but<00:03:13.959> before 00:03:14.190 --> 00:03:14.200 align:start position:0% we're gonna see quick video but before 00:03:14.200 --> 00:03:16.259 align:start position:0% we're gonna see quick video but before that<00:03:14.530> I'm<00:03:14.709> gonna<00:03:14.890> explain<00:03:15.370> what's<00:03:15.879> happening 00:03:16.259 --> 00:03:16.269 align:start position:0% that I'm gonna explain what's happening 00:03:16.269 --> 00:03:22.020 align:start position:0% that I'm gonna explain what's happening here<00:03:18.510> yeah<00:03:19.510> so<00:03:19.870> I<00:03:20.590> have<00:03:21.250> a<00:03:21.280> really<00:03:21.700> simple 00:03:22.020 --> 00:03:22.030 align:start position:0% here yeah so I have a really simple 00:03:22.030 --> 00:03:24.660 align:start position:0% here yeah so I have a really simple smart<00:03:22.540> contract<00:03:23.019> it's<00:03:23.140> called<00:03:23.349> counter<00:03:23.890> old 00:03:24.660 --> 00:03:24.670 align:start position:0% smart contract it's called counter old 00:03:24.670 --> 00:03:28.470 align:start position:0% smart contract it's called counter old has<00:03:25.060> is<00:03:25.420> that<00:03:25.930> simple<00:03:26.590> is<00:03:27.099> that<00:03:27.430> one<00:03:27.730> state 00:03:28.470 --> 00:03:28.480 align:start position:0% has is that simple is that one state 00:03:28.480 --> 00:03:32.160 align:start position:0% has is that simple is that one state variable<00:03:28.720> called<00:03:29.430> count<00:03:30.430> and<00:03:30.849> you<00:03:31.540> can<00:03:31.599> go<00:03:31.900> by 00:03:32.160 --> 00:03:32.170 align:start position:0% variable called count and you can go by 00:03:32.170 --> 00:03:33.960 align:start position:0% variable called count and you can go by the<00:03:32.200> up<00:03:32.530> and<00:03:32.769> down<00:03:32.950> basically<00:03:33.340> with<00:03:33.700> smart 00:03:33.960 --> 00:03:33.970 align:start position:0% the up and down basically with smart 00:03:33.970 --> 00:03:37.039 align:start position:0% the up and down basically with smart contract<00:03:34.390> just<00:03:34.540> counts<00:03:35.110> up<00:03:35.590> and<00:03:35.890> down<00:03:36.040> and<00:03:36.370> has 00:03:37.039 --> 00:03:37.049 align:start position:0% contract just counts up and down and has 00:03:37.049 --> 00:03:39.420 align:start position:0% contract just counts up and down and has appropriate<00:03:38.049> methods<00:03:38.500> increased<00:03:38.950> counter 00:03:39.420 --> 00:03:39.430 align:start position:0% appropriate methods increased counter 00:03:39.430 --> 00:03:43.020 align:start position:0% appropriate methods increased counter decreased<00:03:40.030> under<00:03:41.340> which<00:03:42.340> you<00:03:42.519> can<00:03:42.549> modify 00:03:43.020 --> 00:03:43.030 align:start position:0% decreased under which you can modify 00:03:43.030 --> 00:03:47.220 align:start position:0% decreased under which you can modify this<00:03:43.420> state<00:03:44.170> variable<00:03:44.680> and<00:03:45.450> on<00:03:46.450> the<00:03:46.569> left<00:03:46.780> is 00:03:47.220 --> 00:03:47.230 align:start position:0% this state variable and on the left is 00:03:47.230 --> 00:03:48.990 align:start position:0% this state variable and on the left is the<00:03:47.379> front<00:03:47.590> end<00:03:47.920> representation<00:03:48.700> of<00:03:48.910> the 00:03:48.990 --> 00:03:49.000 align:start position:0% the front end representation of the 00:03:49.000 --> 00:03:51.720 align:start position:0% the front end representation of the smart<00:03:49.329> contract<00:03:49.569> written<00:03:50.260> in<00:03:50.950> create<00:03:51.310> react 00:03:51.720 --> 00:03:51.730 align:start position:0% smart contract written in create react 00:03:51.730 --> 00:03:55.229 align:start position:0% smart contract written in create react app<00:03:51.970> it<00:03:52.780> displays<00:03:53.260> contract<00:03:54.220> address<00:03:54.579> as<00:03:55.090> well 00:03:55.229 --> 00:03:55.239 align:start position:0% app it displays contract address as well 00:03:55.239 --> 00:03:57.440 align:start position:0% app it displays contract address as well as<00:03:55.390> the<00:03:55.450> current<00:03:55.810> weight<00:03:56.109> which<00:03:56.349> is<00:03:56.500> 32<00:03:56.890> and 00:03:57.440 --> 00:03:57.450 align:start position:0% as the current weight which is 32 and 00:03:57.450 --> 00:04:00.089 align:start position:0% as the current weight which is 32 and brought<00:03:58.450> to<00:03:58.840> buttons<00:03:59.260> to<00:03:59.440> increase<00:03:59.470> and 00:04:00.089 --> 00:04:00.099 align:start position:0% brought to buttons to increase and 00:04:00.099 --> 00:04:02.789 align:start position:0% brought to buttons to increase and decrease<00:04:00.129> the<00:04:00.489> counter<00:04:01.030> for<00:04:01.239> one<00:04:01.450> and<00:04:01.840> let's 00:04:02.789 --> 00:04:02.799 align:start position:0% decrease the counter for one and let's 00:04:02.799 --> 00:04:06.780 align:start position:0% decrease the counter for one and let's say<00:04:03.239> realize<00:04:04.239> that<00:04:04.660> increase<00:04:05.530> in<00:04:05.709> counter<00:04:06.310> by 00:04:06.780 --> 00:04:06.790 align:start position:0% say realize that increase in counter by 00:04:06.790 --> 00:04:09.420 align:start position:0% say realize that increase in counter by amount<00:04:07.540> is<00:04:07.959> not<00:04:08.170> good<00:04:08.500> enough<00:04:08.769> low<00:04:09.069> business 00:04:09.420 --> 00:04:09.430 align:start position:0% amount is not good enough low business 00:04:09.430 --> 00:04:11.819 align:start position:0% amount is not good enough low business logic<00:04:09.640> and<00:04:10.030> then<00:04:10.569> only<00:04:10.870> gonna<00:04:11.170> increase<00:04:11.500> it<00:04:11.680> by 00:04:11.819 --> 00:04:11.829 align:start position:0% logic and then only gonna increase it by 00:04:11.829 --> 00:04:14.190 align:start position:0% logic and then only gonna increase it by the<00:04:11.890> number<00:04:12.340> of<00:04:12.370> three<00:04:12.640> in<00:04:13.239> this<00:04:13.540> video<00:04:13.900> I'm 00:04:14.190 --> 00:04:14.200 align:start position:0% the number of three in this video I'm 00:04:14.200 --> 00:04:16.949 align:start position:0% the number of three in this video I'm gonna<00:04:14.440> modify<00:04:14.889> this<00:04:15.819> math<00:04:16.180> contract<00:04:16.660> to<00:04:16.810> do 00:04:16.949 --> 00:04:16.959 align:start position:0% gonna modify this math contract to do 00:04:16.959 --> 00:04:19.680 align:start position:0% gonna modify this math contract to do that<00:04:17.139> and<00:04:17.519> he's<00:04:18.519> going<00:04:18.760> to<00:04:18.849> be<00:04:18.970> reflected<00:04:19.539> on 00:04:19.680 --> 00:04:19.690 align:start position:0% that and he's going to be reflected on 00:04:19.690 --> 00:04:24.480 align:start position:0% that and he's going to be reflected on the<00:04:20.019> front<00:04:20.289> yeah<00:04:20.620> let's<00:04:21.340> see<00:04:22.680> so<00:04:23.680> first<00:04:24.160> I'm 00:04:24.480 --> 00:04:24.490 align:start position:0% the front yeah let's see so first I'm 00:04:24.490 --> 00:04:27.810 align:start position:0% the front yeah let's see so first I'm gonna<00:04:24.669> edit<00:04:25.300> smart<00:04:26.229> conduct<00:04:26.590> itself<00:04:26.860> and<00:04:27.520> save 00:04:27.810 --> 00:04:27.820 align:start position:0% gonna edit smart conduct itself and save 00:04:27.820 --> 00:04:32.909 align:start position:0% gonna edit smart conduct itself and save it<00:04:28.950> then<00:04:30.000> ever<00:04:31.000> like<00:04:31.240> compiled<00:04:31.800> we<00:04:32.800> will 00:04:32.909 --> 00:04:32.919 align:start position:0% it then ever like compiled we will 00:04:32.919 --> 00:04:35.980 align:start position:0% it then ever like compiled we will compile<00:04:33.280> comment 00:04:35.980 --> 00:04:35.990 align:start position:0% 00:04:35.990 --> 00:04:39.900 align:start position:0% once<00:04:36.620> it<00:04:36.770> compiles<00:04:37.539> I'm<00:04:38.539> going<00:04:38.810> to<00:04:38.990> deploy<00:04:39.319> but 00:04:39.900 --> 00:04:39.910 align:start position:0% once it compiles I'm going to deploy but 00:04:39.910 --> 00:04:41.920 align:start position:0% once it compiles I'm going to deploy but because<00:04:40.910> if<00:04:41.180> you<00:04:41.330> don't<00:04:41.389> blockchain<00:04:41.900> is 00:04:41.920 --> 00:04:41.930 align:start position:0% because if you don't blockchain is 00:04:41.930 --> 00:04:44.589 align:start position:0% because if you don't blockchain is mutable<00:04:42.580> every<00:04:43.580> time<00:04:43.789> you<00:04:43.940> devote<00:04:44.240> it<00:04:44.419> you 00:04:44.589 --> 00:04:44.599 align:start position:0% mutable every time you devote it you 00:04:44.599 --> 00:04:47.080 align:start position:0% mutable every time you devote it you have<00:04:44.810> to<00:04:45.110> initialize<00:04:45.770> during<00:04:46.490> your<00:04:46.610> contract 00:04:47.080 --> 00:04:47.090 align:start position:0% have to initialize during your contract 00:04:47.090 --> 00:04:50.620 align:start position:0% have to initialize during your contract and<00:04:47.800> my<00:04:48.800> old<00:04:49.039> contract<00:04:49.340> has<00:04:49.610> a<00:04:49.849> value<00:04:50.120> of<00:04:50.300> 32 00:04:50.620 --> 00:04:50.630 align:start position:0% and my old contract has a value of 32 00:04:50.630 --> 00:04:53.830 align:start position:0% and my old contract has a value of 32 but<00:04:51.199> now<00:04:51.380> I<00:04:51.410> have<00:04:51.860> to<00:04:52.039> provide<00:04:52.370> a<00:04:52.669> new<00:04:53.449> alias 00:04:53.830 --> 00:04:53.840 align:start position:0% but now I have to provide a new alias 00:04:53.840 --> 00:04:55.689 align:start position:0% but now I have to provide a new alias for<00:04:53.960> the<00:04:54.020> counter<00:04:54.500> initial<00:04:54.979> value<00:04:55.280> I'm<00:04:55.490> gonna 00:04:55.689 --> 00:04:55.699 align:start position:0% for the counter initial value I'm gonna 00:04:55.699 --> 00:04:58.260 align:start position:0% for the counter initial value I'm gonna go<00:04:55.940> give<00:04:56.180> one<00:04:56.720> two<00:04:56.900> three 00:04:58.260 --> 00:04:58.270 align:start position:0% go give one two three 00:04:58.270 --> 00:05:01.480 align:start position:0% go give one two three and<00:04:59.270> also<00:04:59.479> because<00:04:59.990> new<00:05:00.710> contract<00:05:01.130> is<00:05:01.220> a<00:05:01.250> new 00:05:01.480 --> 00:05:01.490 align:start position:0% and also because new contract is a new 00:05:01.490 --> 00:05:02.050 align:start position:0% and also because new contract is a new address 00:05:02.050 --> 00:05:02.060 align:start position:0% address 00:05:02.060 --> 00:05:07.120 align:start position:0% address my<00:05:02.210> favorite<00:05:02.599> F<00:05:03.110> can't<00:05:03.710> pick<00:05:04.039> up<00:05:04.220> the<00:05:06.130> files 00:05:07.120 --> 00:05:07.130 align:start position:0% my favorite F can't pick up the files 00:05:07.130 --> 00:05:09.400 align:start position:0% my favorite F can't pick up the files required<00:05:07.639> for<00:05:07.970> protium<00:05:08.419> so<00:05:08.960> I<00:05:08.990> also<00:05:09.110> have<00:05:09.380> to 00:05:09.400 --> 00:05:09.410 align:start position:0% required for protium so I also have to 00:05:09.410 --> 00:05:13.600 align:start position:0% required for protium so I also have to restart<00:05:10.000> my<00:05:11.000> Granger<00:05:11.750> app<00:05:12.139> which<00:05:12.680> takes<00:05:13.400> some 00:05:13.600 --> 00:05:13.610 align:start position:0% restart my Granger app which takes some 00:05:13.610 --> 00:05:20.469 align:start position:0% restart my Granger app which takes some time<00:05:15.940> but<00:05:17.229> you<00:05:18.229> see<00:05:18.410> how<00:05:18.590> like<00:05:19.580> our<00:05:20.150> now 00:05:20.469 --> 00:05:20.479 align:start position:0% time but you see how like our now 00:05:20.479 --> 00:05:27.040 align:start position:0% time but you see how like our now keepsake<00:05:23.979> and<00:05:24.979> let's<00:05:25.820> say<00:05:26.030> does<00:05:26.599> it<00:05:26.750> even<00:05:26.990> work 00:05:27.040 --> 00:05:27.050 align:start position:0% keepsake and let's say does it even work 00:05:27.050 --> 00:05:28.420 align:start position:0% keepsake and let's say does it even work okay<00:05:27.560> so<00:05:27.620> I'm<00:05:27.800> going<00:05:28.009> to<00:05:28.039> press<00:05:28.280> the<00:05:28.400> button 00:05:28.420 --> 00:05:28.430 align:start position:0% okay so I'm going to press the button 00:05:28.430 --> 00:05:31.779 align:start position:0% okay so I'm going to press the button metal<00:05:29.360> mask<00:05:29.539> as<00:05:29.780> usual<00:05:30.199> yes<00:05:30.889> first<00:05:31.310> it<00:05:31.580> went 00:05:31.779 --> 00:05:31.789 align:start position:0% metal mask as usual yes first it went 00:05:31.789 --> 00:05:35.589 align:start position:0% metal mask as usual yes first it went from<00:05:31.940> 1<00:05:32.150> 2<00:05:32.330> 3<00:05:32.360> to<00:05:32.780> 1<00:05:33.020> to<00:05:33.050> 6<00:05:33.409> and<00:05:33.680> so<00:05:34.569> over<00:05:35.569> a 00:05:35.589 --> 00:05:35.599 align:start position:0% from 1 2 3 to 1 to 6 and so over a 00:05:35.599 --> 00:05:38.350 align:start position:0% from 1 2 3 to 1 to 6 and so over a minute<00:05:36.020> we<00:05:36.470> achieved<00:05:37.099> incredible<00:05:37.880> things<00:05:38.120> to 00:05:38.350 --> 00:05:38.360 align:start position:0% minute we achieved incredible things to 00:05:38.360 --> 00:05:41.529 align:start position:0% minute we achieved incredible things to just<00:05:38.630> change<00:05:39.130> the<00:05:40.130> counter<00:05:40.580> somehow<00:05:41.060> it's 00:05:41.529 --> 00:05:41.539 align:start position:0% just change the counter somehow it's 00:05:41.539 --> 00:05:42.820 align:start position:0% just change the counter somehow it's free<00:05:41.900> right 00:05:42.820 --> 00:05:42.830 align:start position:0% free right 00:05:42.830 --> 00:05:47.170 align:start position:0% free right and<00:05:43.340> I<00:05:44.770> read<00:05:45.770> you'll<00:05:45.919> agree<00:05:46.220> with<00:05:46.340> me<00:05:46.490> that<00:05:46.669> was 00:05:47.170 --> 00:05:47.180 align:start position:0% and I read you'll agree with me that was 00:05:47.180 --> 00:05:49.390 align:start position:0% and I read you'll agree with me that was quite<00:05:47.599> a<00:05:47.630> lot<00:05:47.930> of<00:05:47.960> steps<00:05:48.380> involved<00:05:49.190> for 00:05:49.390 --> 00:05:49.400 align:start position:0% quite a lot of steps involved for 00:05:49.400 --> 00:05:52.209 align:start position:0% quite a lot of steps involved for something<00:05:49.759> trivial<00:05:50.000> I<00:05:50.650> called<00:05:51.650> one<00:05:51.979> line 00:05:52.209 --> 00:05:52.219 align:start position:0% something trivial I called one line 00:05:52.219 --> 00:05:55.170 align:start position:0% something trivial I called one line change<00:05:52.550> problem<00:05:53.500> let's<00:05:54.500> break<00:05:54.860> it<00:05:55.039> down 00:05:55.170 --> 00:05:55.180 align:start position:0% change problem let's break it down 00:05:55.180 --> 00:05:59.709 align:start position:0% change problem let's break it down quickly<00:05:56.800> in<00:05:57.800> order<00:05:58.009> to<00:05:58.219> at<00:05:59.120> the<00:05:59.270> minimal 00:05:59.709 --> 00:05:59.719 align:start position:0% quickly in order to at the minimal 00:05:59.719 --> 00:06:02.850 align:start position:0% quickly in order to at the minimal change<00:06:00.229> one<00:06:00.650> line<00:06:00.889> is<00:06:01.159> not<00:06:01.340> very<00:06:01.669> smart 00:06:02.850 --> 00:06:02.860 align:start position:0% change one line is not very smart 00:06:02.860 --> 00:06:06.430 align:start position:0% change one line is not very smart contract<00:06:03.860> which<00:06:04.849> is<00:06:04.880> tied<00:06:05.360> to<00:06:05.690> some<00:06:05.930> front-end 00:06:06.430 --> 00:06:06.440 align:start position:0% contract which is tied to some front-end 00:06:06.440 --> 00:06:09.520 align:start position:0% contract which is tied to some front-end app<00:06:06.800> you<00:06:07.580> have<00:06:07.789> to<00:06:08.030> change<00:06:08.449> a<00:06:08.750> smart<00:06:09.020> contract 00:06:09.520 --> 00:06:09.530 align:start position:0% app you have to change a smart contract 00:06:09.530 --> 00:06:13.760 align:start position:0% app you have to change a smart contract then<00:06:09.860> compiled<00:06:10.460> the<00:06:11.210> decoy<00:06:11.680> then 00:06:13.760 --> 00:06:13.770 align:start position:0% then compiled the decoy then 00:06:13.770 --> 00:06:18.230 align:start position:0% then compiled the decoy then the<00:06:14.069> story<00:06:14.639> today<00:06:16.039> the<00:06:17.039> historic<00:06:17.280> state<00:06:17.940> and 00:06:18.230 --> 00:06:18.240 align:start position:0% the story today the historic state and 00:06:18.240 --> 00:06:21.170 align:start position:0% the story today the historic state and if<00:06:19.080> you<00:06:19.650> had<00:06:19.889> some<00:06:20.160> my<00:06:20.340> complex<00:06:20.849> state 00:06:21.170 --> 00:06:21.180 align:start position:0% if you had some my complex state 00:06:21.180 --> 00:06:23.809 align:start position:0% if you had some my complex state restoring<00:06:22.050> say<00:06:22.289> can<00:06:22.650> be<00:06:22.800> greeted<00:06:23.310> not<00:06:23.430> drivel 00:06:23.809 --> 00:06:23.819 align:start position:0% restoring say can be greeted not drivel 00:06:23.819 --> 00:06:25.520 align:start position:0% restoring say can be greeted not drivel because<00:06:24.180> one<00:06:24.509> security<00:06:25.020> put<00:06:25.169> all<00:06:25.349> the 00:06:25.520 --> 00:06:25.530 align:start position:0% because one security put all the 00:06:25.530 --> 00:06:27.920 align:start position:0% because one security put all the contracts<00:06:25.949> of<00:06:26.130> your<00:06:26.340> state<00:06:26.550> is<00:06:26.729> gone<00:06:27.000> and<00:06:27.360> if 00:06:27.920 --> 00:06:27.930 align:start position:0% contracts of your state is gone and if 00:06:27.930 --> 00:06:30.350 align:start position:0% contracts of your state is gone and if it<00:06:28.050> was<00:06:28.139> in<00:06:28.380> the<00:06:28.500> middle<00:06:28.830> of<00:06:28.949> my<00:06:29.130> dividing<00:06:30.060> some 00:06:30.350 --> 00:06:30.360 align:start position:0% it was in the middle of my dividing some 00:06:30.360 --> 00:06:33.170 align:start position:0% it was in the middle of my dividing some issue<00:06:31.169> and<00:06:31.710> suddenly<00:06:32.490> you<00:06:32.580> have<00:06:32.789> to<00:06:32.819> be<00:06:33.120> wrong 00:06:33.170 --> 00:06:33.180 align:start position:0% issue and suddenly you have to be wrong 00:06:33.180 --> 00:06:35.450 align:start position:0% issue and suddenly you have to be wrong everything<00:06:33.870> everything<00:06:34.500> is<00:06:34.620> gone<00:06:34.919> and<00:06:35.250> I 00:06:35.450 --> 00:06:35.460 align:start position:0% everything everything is gone and I 00:06:35.460 --> 00:06:36.890 align:start position:0% everything everything is gone and I experienced<00:06:35.970> it<00:06:36.090> personally 00:06:36.890 --> 00:06:36.900 align:start position:0% experienced it personally 00:06:36.900 --> 00:06:40.779 align:start position:0% experienced it personally and<00:06:37.590> then<00:06:38.220> you<00:06:38.310> have<00:06:38.430> to<00:06:38.520> refresh<00:06:38.699> the<00:06:38.910> browser 00:06:40.779 --> 00:06:40.789 align:start position:0% and then you have to refresh the browser 00:06:40.789 --> 00:06:43.670 align:start position:0% and then you have to refresh the browser but<00:06:41.789> if<00:06:42.090> you<00:06:42.180> think<00:06:42.330> about<00:06:42.449> it<00:06:42.900> how<00:06:43.199> it<00:06:43.380> really 00:06:43.670 --> 00:06:43.680 align:start position:0% but if you think about it how it really 00:06:43.680 --> 00:06:47.600 align:start position:0% but if you think about it how it really should<00:06:44.099> be<00:06:44.130> is<00:06:44.550> it<00:06:44.970> is<00:06:45.150> it<00:06:45.330> the<00:06:45.539> whe<00:06:46.470> way<00:06:46.650> if<00:06:47.460> you 00:06:47.600 --> 00:06:47.610 align:start position:0% should be is it is it the whe way if you 00:06:47.610 --> 00:06:49.370 align:start position:0% should be is it is it the whe way if you look<00:06:47.759> at<00:06:47.849> the<00:06:47.909> Internet<00:06:48.300> Explorer<00:06:48.599> 6<00:06:48.870> it's<00:06:49.229> not 00:06:49.370 --> 00:06:49.380 align:start position:0% look at the Internet Explorer 6 it's not 00:06:49.380 --> 00:06:51.710 align:start position:0% look at the Internet Explorer 6 it's not like<00:06:49.560> how<00:06:49.919> we<00:06:49.979> do<00:06:50.250> things<00:06:50.460> anymore<00:06:50.909> now<00:06:51.690> we 00:06:51.710 --> 00:06:51.720 align:start position:0% like how we do things anymore now we 00:06:51.720 --> 00:06:53.899 align:start position:0% like how we do things anymore now we have<00:06:51.960> this<00:06:52.289> our<00:06:52.500> luxury<00:06:53.069> of<00:06:53.220> development 00:06:53.899 --> 00:06:53.909 align:start position:0% have this our luxury of development 00:06:53.909 --> 00:06:56.450 align:start position:0% have this our luxury of development tools<00:06:54.210> is<00:06:54.569> like<00:06:54.900> loading<00:06:55.740> confront<00:06:56.220> me<00:06:56.400> and 00:06:56.450 --> 00:06:56.460 align:start position:0% tools is like loading confront me and 00:06:56.460 --> 00:06:59.749 align:start position:0% tools is like loading confront me and web<00:06:57.449> dev<00:06:57.800> server<00:06:58.800> switched<00:06:59.310> just<00:06:59.610> like 00:06:59.749 --> 00:06:59.759 align:start position:0% web dev server switched just like 00:06:59.759 --> 00:07:02.120 align:start position:0% web dev server switched just like refresh<00:07:00.539> everything<00:07:00.960> for<00:07:01.380> us<00:07:01.470> watch<00:07:01.919> our 00:07:02.120 --> 00:07:02.130 align:start position:0% refresh everything for us watch our 00:07:02.130 --> 00:07:05.029 align:start position:0% refresh everything for us watch our files<00:07:02.490> you<00:07:03.240> just<00:07:03.449> type<00:07:03.810> called<00:07:04.530> in<00:07:04.860> your 00:07:05.029 --> 00:07:05.039 align:start position:0% files you just type called in your 00:07:05.039 --> 00:07:07.939 align:start position:0% files you just type called in your editor<00:07:05.580> hit<00:07:06.330> save<00:07:06.630> and<00:07:06.960> everything<00:07:07.380> works<00:07:07.620> in 00:07:07.939 --> 00:07:07.949 align:start position:0% editor hit save and everything works in 00:07:07.949 --> 00:07:12.170 align:start position:0% editor hit save and everything works in web<00:07:08.909> development<00:07:09.210> and<00:07:10.370> I<00:07:11.370> believe<00:07:11.819> it<00:07:12.120> should 00:07:12.170 --> 00:07:12.180 align:start position:0% web development and I believe it should 00:07:12.180 --> 00:07:15.379 align:start position:0% web development and I believe it should be<00:07:12.539> the<00:07:12.780> same<00:07:12.990> experience<00:07:13.889> when<00:07:14.729> you<00:07:14.940> develop 00:07:15.379 --> 00:07:15.389 align:start position:0% be the same experience when you develop 00:07:15.389 --> 00:07:22.670 align:start position:0% be the same experience when you develop applications<00:07:16.169> for<00:07:16.229> film<00:07:21.380> excited<00:07:22.380> to<00:07:22.500> present 00:07:22.670 --> 00:07:22.680 align:start position:0% applications for film excited to present 00:07:22.680 --> 00:07:26.360 align:start position:0% applications for film excited to present a<00:07:23.039> significant<00:07:23.729> loader<00:07:24.710> so<00:07:25.710> you<00:07:25.830> have<00:07:26.099> other 00:07:26.360 --> 00:07:26.370 align:start position:0% a significant loader so you have other 00:07:26.370 --> 00:07:33.640 align:start position:0% a significant loader so you have other address<00:07:27.360> this<00:07:27.719> problem 00:07:33.640 --> 00:07:33.650 align:start position:0% 00:07:33.650 --> 00:07:37.010 align:start position:0% we're<00:07:34.650> going<00:07:34.800> to<00:07:34.860> see<00:07:35.010> another<00:07:35.250> video<00:07:35.690> it<00:07:36.690> has 00:07:37.010 --> 00:07:37.020 align:start position:0% we're going to see another video it has 00:07:37.020 --> 00:07:39.290 align:start position:0% we're going to see another video it has the<00:07:37.140> same<00:07:37.350> setup<00:07:37.710> where<00:07:38.100> is<00:07:38.160> the<00:07:38.430> counter 00:07:39.290 --> 00:07:39.300 align:start position:0% the same setup where is the counter 00:07:39.300 --> 00:07:40.880 align:start position:0% the same setup where is the counter contract<00:07:39.750> which<00:07:39.960> channel<00:07:40.260> familiar<00:07:40.710> at<00:07:40.860> least 00:07:40.880 --> 00:07:40.890 align:start position:0% contract which channel familiar at least 00:07:40.890 --> 00:07:45.230 align:start position:0% contract which channel familiar at least to<00:07:41.760> not<00:07:41.940> familiar<00:07:42.270> with<00:07:42.720> and<00:07:43.640> same<00:07:44.640> content<00:07:45.090> on 00:07:45.230 --> 00:07:45.240 align:start position:0% to not familiar with and same content on 00:07:45.240 --> 00:07:47.360 align:start position:0% to not familiar with and same content on the<00:07:45.390> left<00:07:45.600> but<00:07:46.200> right<00:07:46.440> now<00:07:46.620> issue<00:07:46.980> our<00:07:47.130> value 00:07:47.360 --> 00:07:47.370 align:start position:0% the left but right now issue our value 00:07:47.370 --> 00:07:49.960 align:start position:0% the left but right now issue our value is<00:07:47.460> 58<00:07:47.970> there<00:07:48.690> is<00:07:48.780> a<00:07:48.810> console<00:07:49.320> at<00:07:49.410> the<00:07:49.440> bottom 00:07:49.960 --> 00:07:49.970 align:start position:0% is 58 there is a console at the bottom 00:07:49.970 --> 00:07:53.420 align:start position:0% is 58 there is a console at the bottom and<00:07:50.970> we're<00:07:51.660> going<00:07:51.840> to<00:07:52.080> repeat<00:07:52.470> the<00:07:52.860> same<00:07:52.890> steps 00:07:53.420 --> 00:07:53.430 align:start position:0% and we're going to repeat the same steps 00:07:53.430 --> 00:07:56.270 align:start position:0% and we're going to repeat the same steps as<00:07:53.670> just<00:07:54.270> to<00:07:54.420> get<00:07:54.570> before<00:07:54.780> whether<00:07:55.740> it<00:07:55.830> is<00:07:55.980> time 00:07:56.270 --> 00:07:56.280 align:start position:0% as just to get before whether it is time 00:07:56.280 --> 00:08:03.680 align:start position:0% as just to get before whether it is time we've<00:07:57.180> solidity<00:07:57.660> upload<00:07:58.140> or<00:07:58.350> enable<00:08:02.690> you're 00:08:03.680 --> 00:08:03.690 align:start position:0% we've solidity upload or enable you're 00:08:03.690 --> 00:08:07.040 align:start position:0% we've solidity upload or enable you're going<00:08:03.840> to<00:08:03.900> change<00:08:04.080> the<00:08:04.230> file<00:08:05.330> and<00:08:06.330> save<00:08:06.690> it<00:08:06.870> as 00:08:07.040 --> 00:08:07.050 align:start position:0% going to change the file and save it as 00:08:07.050 --> 00:08:09.500 align:start position:0% going to change the file and save it as you<00:08:07.320> can<00:08:07.440> see<00:08:07.710> it<00:08:07.950> starts<00:08:08.280> to<00:08:08.310> compile<00:08:08.820> it's<00:08:09.240> in 00:08:09.500 --> 00:08:09.510 align:start position:0% you can see it starts to compile it's in 00:08:09.510 --> 00:08:13.730 align:start position:0% you can see it starts to compile it's in the<00:08:09.630> console<00:08:10.460> while<00:08:11.460> I'm<00:08:12.500> randomly<00:08:13.500> clicking 00:08:13.730 --> 00:08:13.740 align:start position:0% the console while I'm randomly clicking 00:08:13.740 --> 00:08:19.070 align:start position:0% the console while I'm randomly clicking everywhere<00:08:15.800> and<00:08:17.180> suddenly<00:08:18.180> our<00:08:18.540> front<00:08:18.870> end 00:08:19.070 --> 00:08:19.080 align:start position:0% everywhere and suddenly our front end 00:08:19.080 --> 00:08:24.100 align:start position:0% everywhere and suddenly our front end does<00:08:19.470> refresh<00:08:19.950> and<00:08:20.790> if<00:08:21.600> I<00:08:21.690> press<00:08:21.900> this<00:08:22.110> button 00:08:24.100 --> 00:08:24.110 align:start position:0% does refresh and if I press this button 00:08:24.110 --> 00:08:27.920 align:start position:0% does refresh and if I press this button it<00:08:25.110> doesn't<00:08:25.380> visit<00:08:25.770> by<00:08:25.920> free<00:08:26.420> but<00:08:27.420> as<00:08:27.690> you<00:08:27.840> can 00:08:27.920 --> 00:08:27.930 align:start position:0% it doesn't visit by free but as you can 00:08:27.930 --> 00:08:30.500 align:start position:0% it doesn't visit by free but as you can see<00:08:27.990> the<00:08:28.320> stage<00:08:29.060> Township<00:08:30.060> stayed<00:08:30.330> the<00:08:30.480> same 00:08:30.500 --> 00:08:30.510 align:start position:0% see the stage Township stayed the same 00:08:30.510 --> 00:08:36.080 align:start position:0% see the stage Township stayed the same which<00:08:31.280> is<00:08:32.280> strange<00:08:32.790> because<00:08:33.979> the<00:08:34.979> state<00:08:35.280> did 00:08:36.080 --> 00:08:36.090 align:start position:0% which is strange because the state did 00:08:36.090 --> 00:08:40.390 align:start position:0% which is strange because the state did appoint<00:08:36.360> you<00:08:36.510> can't<00:08:36.720> exchange<00:08:37.729> using<00:08:39.080> why/how 00:08:40.390 --> 00:08:40.400 align:start position:0% appoint you can't exchange using why/how 00:08:40.400 --> 00:08:45.890 align:start position:0% appoint you can't exchange using why/how as<00:08:41.400> possible<00:08:43.820> let's<00:08:44.820> quickly<00:08:45.240> break<00:08:45.630> down 00:08:45.890 --> 00:08:45.900 align:start position:0% as possible let's quickly break down 00:08:45.900 --> 00:08:49.630 align:start position:0% as possible let's quickly break down what's<00:08:46.650> it<00:08:46.860> about<00:08:47.190> your<00:08:47.580> desk<00:08:47.820> for<00:08:48.030> you 00:08:49.630 --> 00:08:49.640 align:start position:0% what's it about your desk for you 00:08:49.640 --> 00:08:53.540 align:start position:0% what's it about your desk for you compiles<00:08:50.640> just<00:08:51.540> not<00:08:51.780> contracts<00:08:52.550> essentially 00:08:53.540 --> 00:08:53.550 align:start position:0% compiles just not contracts essentially 00:08:53.550 --> 00:08:55.760 align:start position:0% compiles just not contracts essentially right<00:08:53.730> in<00:08:53.850> a<00:08:53.970> compartment<00:08:54.360> for<00:08:54.810> you<00:08:55.080> so<00:08:55.530> they 00:08:55.760 --> 00:08:55.770 align:start position:0% right in a compartment for you so they 00:08:55.770 --> 00:08:59.420 align:start position:0% right in a compartment for you so they need<00:08:55.920> to<00:08:55.950> type<00:08:56.250> in<00:08:56.900> then<00:08:57.900> it<00:08:58.740> deploys<00:08:59.070> in<00:08:59.280> your 00:08:59.420 --> 00:08:59.430 align:start position:0% need to type in then it deploys in your 00:08:59.430 --> 00:09:02.210 align:start position:0% need to type in then it deploys in your body<00:08:59.670> code<00:09:00.000> to<00:09:00.570> the<00:09:00.810> local<00:09:01.650> node<00:09:01.860> which<00:09:02.190> is 00:09:02.210 --> 00:09:02.220 align:start position:0% body code to the local node which is 00:09:02.220 --> 00:09:05.870 align:start position:0% body code to the local node which is Ganesh<00:09:02.670> with<00:09:03.630> a<00:09:03.840> tricky<00:09:04.080> step<00:09:04.410> and<00:09:04.860> then<00:09:05.640> it 00:09:05.870 --> 00:09:05.880 align:start position:0% Ganesh with a tricky step and then it 00:09:05.880 --> 00:09:09.590 align:start position:0% Ganesh with a tricky step and then it refresh<00:09:06.270> the<00:09:06.600> browser<00:09:06.720> page<00:09:07.560> frame<00:09:08.300> let's<00:09:09.300> dig 00:09:09.590 --> 00:09:09.600 align:start position:0% refresh the browser page frame let's dig 00:09:09.600 --> 00:09:12.230 align:start position:0% refresh the browser page frame let's dig into<00:09:09.990> how<00:09:10.380> exactly<00:09:10.950> it<00:09:11.250> was<00:09:11.430> a<00:09:11.490> new<00:09:11.700> code<00:09:11.940> in 00:09:12.230 --> 00:09:12.240 align:start position:0% into how exactly it was a new code in 00:09:12.240 --> 00:09:14.680 align:start position:0% into how exactly it was a new code in the<00:09:12.780> way<00:09:12.930> you<00:09:13.350> preserve<00:09:13.740> your<00:09:13.770> state<00:09:14.280> and 00:09:14.680 --> 00:09:14.690 align:start position:0% the way you preserve your state and 00:09:14.690 --> 00:09:21.800 align:start position:0% the way you preserve your state and address<00:09:18.140> Lance's<00:09:19.140> availability<00:09:20.810> behind 00:09:21.800 --> 00:09:21.810 align:start position:0% address Lance's availability behind 00:09:21.810 --> 00:09:24.850 align:start position:0% address Lance's availability behind since<00:09:22.230> the<00:09:22.500> effort<00:09:23.070> logic<00:09:23.550> relies<00:09:24.060> on 00:09:24.850 --> 00:09:24.860 align:start position:0% since the effort logic relies on 00:09:24.860 --> 00:09:28.100 align:start position:0% since the effort logic relies on availability<00:09:25.860> of<00:09:26.250> pattern<00:09:26.790> which<00:09:27.570> allows<00:09:27.870> you 00:09:28.100 --> 00:09:28.110 align:start position:0% availability of pattern which allows you 00:09:28.110 --> 00:09:30.800 align:start position:0% availability of pattern which allows you to<00:09:28.170> change<00:09:28.850> implementation<00:09:29.850> of<00:09:30.420> a<00:09:30.510> smart 00:09:30.800 --> 00:09:30.810 align:start position:0% to change implementation of a smart 00:09:30.810 --> 00:09:33.920 align:start position:0% to change implementation of a smart contract<00:09:31.020> without<00:09:31.880> losing<00:09:32.880> its<00:09:33.060> state<00:09:33.480> or 00:09:33.920 --> 00:09:33.930 align:start position:0% contract without losing its state or 00:09:33.930 --> 00:09:37.700 align:start position:0% contract without losing its state or address 00:09:37.700 --> 00:09:37.710 align:start position:0% 00:09:37.710 --> 00:09:43.890 align:start position:0% so<00:09:38.710> a<00:09:38.980> lot<00:09:39.220> there<00:09:39.430> is<00:09:39.610> imitation<00:09:40.740> by<00:09:42.900> open 00:09:43.890 --> 00:09:43.900 align:start position:0% so a lot there is imitation by open 00:09:43.900 --> 00:09:45.210 align:start position:0% so a lot there is imitation by open Zeppelin<00:09:44.290> SDK 00:09:45.210 --> 00:09:45.220 align:start position:0% Zeppelin SDK 00:09:45.220 --> 00:09:49.530 align:start position:0% Zeppelin SDK it's<00:09:45.640> called<00:09:45.910> upgrades<00:09:46.390> and<00:09:47.820> I'm<00:09:48.820> gonna<00:09:49.240> give 00:09:49.530 --> 00:09:49.540 align:start position:0% it's called upgrades and I'm gonna give 00:09:49.540 --> 00:09:53.430 align:start position:0% it's called upgrades and I'm gonna give a<00:09:49.570> quick<00:09:50.700> explanation<00:09:51.700> how<00:09:52.270> it<00:09:52.330> works<00:09:52.630> but<00:09:53.230> if 00:09:53.430 --> 00:09:53.440 align:start position:0% a quick explanation how it works but if 00:09:53.440 --> 00:09:55.650 align:start position:0% a quick explanation how it works but if you<00:09:53.560> want<00:09:53.740> more<00:09:54.010> if<00:09:54.730> you<00:09:54.880> want<00:09:55.210> to<00:09:55.300> know<00:09:55.450> more 00:09:55.650 --> 00:09:55.660 align:start position:0% you want more if you want to know more 00:09:55.660 --> 00:10:00.150 align:start position:0% you want more if you want to know more go<00:09:55.720> to<00:09:56.020> open<00:09:56.830> Zeppelin<00:09:57.310> from<00:09:57.910> /tk<00:09:58.750> and<00:09:59.160> you'll 00:10:00.150 --> 00:10:00.160 align:start position:0% go to open Zeppelin from /tk and you'll 00:10:00.160 --> 00:10:01.950 align:start position:0% go to open Zeppelin from /tk and you'll find<00:10:00.460> everything<00:10:00.940> you<00:10:01.300> want<00:10:01.480> to<00:10:01.660> know<00:10:01.780> about 00:10:01.950 --> 00:10:01.960 align:start position:0% find everything you want to know about 00:10:01.960 --> 00:10:04.770 align:start position:0% find everything you want to know about it<00:10:02.440> far<00:10:03.190> more<00:10:03.310> examples<00:10:04.000> and<00:10:04.210> where<00:10:04.630> the 00:10:04.770 --> 00:10:04.780 align:start position:0% it far more examples and where the 00:10:04.780 --> 00:10:11.580 align:start position:0% it far more examples and where the detailed<00:10:05.110> explanation<00:10:08.040> verse<00:10:09.990> 3<00:10:10.990> the<00:10:11.050> proxy 00:10:11.580 --> 00:10:11.590 align:start position:0% detailed explanation verse 3 the proxy 00:10:11.590 --> 00:10:14.190 align:start position:0% detailed explanation verse 3 the proxy contract<00:10:12.100> which<00:10:13.030> pretends<00:10:13.630> to<00:10:13.750> be<00:10:13.840> your 00:10:14.190 --> 00:10:14.200 align:start position:0% contract which pretends to be your 00:10:14.200 --> 00:10:17.310 align:start position:0% contract which pretends to be your contract<00:10:14.680> and<00:10:14.890> handles<00:10:15.610> all<00:10:15.820> the<00:10:15.850> calls<00:10:16.320> and 00:10:17.310 --> 00:10:17.320 align:start position:0% contract and handles all the calls and 00:10:17.320 --> 00:10:19.850 align:start position:0% contract and handles all the calls and it<00:10:17.980> is<00:10:18.160> delicious<00:10:18.490> constructions<00:10:19.480> to 00:10:19.850 --> 00:10:19.860 align:start position:0% it is delicious constructions to 00:10:19.860 --> 00:10:22.950 align:start position:0% it is delicious constructions to redirect<00:10:20.860> the<00:10:21.220> function<00:10:21.730> calls<00:10:21.940> to<00:10:22.300> contracts 00:10:22.950 --> 00:10:22.960 align:start position:0% redirect the function calls to contracts 00:10:22.960 --> 00:10:26.460 align:start position:0% redirect the function calls to contracts issue<00:10:23.200> to<00:10:24.240> contain<00:10:25.240> implementation<00:10:26.080> lodging 00:10:26.460 --> 00:10:26.470 align:start position:0% issue to contain implementation lodging 00:10:26.470 --> 00:10:30.540 align:start position:0% issue to contain implementation lodging while<00:10:27.160> the<00:10:28.680> contract<00:10:29.680> while<00:10:29.980> the<00:10:30.160> proxy 00:10:30.540 --> 00:10:30.550 align:start position:0% while the contract while the proxy 00:10:30.550 --> 00:10:33.840 align:start position:0% while the contract while the proxy contract<00:10:31.000> calls<00:10:31.240> all<00:10:31.510> the<00:10:31.720> state<00:10:32.050> and<00:10:32.850> address 00:10:33.840 --> 00:10:33.850 align:start position:0% contract calls all the state and address 00:10:33.850 --> 00:10:36.330 align:start position:0% contract calls all the state and address in<00:10:34.390> that<00:10:34.450> way<00:10:34.810> we<00:10:35.140> always<00:10:35.290> interact<00:10:36.070> with<00:10:36.250> a 00:10:36.330 --> 00:10:36.340 align:start position:0% in that way we always interact with a 00:10:36.340 --> 00:10:38.520 align:start position:0% in that way we always interact with a proxy<00:10:36.730> contract<00:10:37.210> where<00:10:37.540> is<00:10:37.660> why<00:10:37.840> our<00:10:38.110> state 00:10:38.520 --> 00:10:38.530 align:start position:0% proxy contract where is why our state 00:10:38.530 --> 00:10:41.840 align:start position:0% proxy contract where is why our state and<00:10:38.830> rest<00:10:39.550> is<00:10:39.820> preserved<00:10:40.390> at<00:10:40.690> all<00:10:40.840> times<00:10:41.140> and 00:10:41.840 --> 00:10:41.850 align:start position:0% and rest is preserved at all times and 00:10:41.850 --> 00:10:45.210 align:start position:0% and rest is preserved at all times and then<00:10:42.850> we<00:10:43.060> change<00:10:43.420> the<00:10:43.570> code<00:10:43.780> and<00:10:44.050> hit<00:10:44.530> safe<00:10:44.890> in 00:10:45.210 --> 00:10:45.220 align:start position:0% then we change the code and hit safe in 00:10:45.220 --> 00:10:48.570 align:start position:0% then we change the code and hit safe in our<00:10:45.370> editor<00:10:45.610> what<00:10:46.360> happens<00:10:46.750> is<00:10:47.110> the<00:10:48.100> new<00:10:48.310> byte 00:10:48.570 --> 00:10:48.580 align:start position:0% our editor what happens is the new byte 00:10:48.580 --> 00:10:52.620 align:start position:0% our editor what happens is the new byte code<00:10:48.850> gets<00:10:49.180> compiled<00:10:49.720> and<00:10:51.300> uploaded<00:10:52.300> to<00:10:52.330> the 00:10:52.620 --> 00:10:52.630 align:start position:0% code gets compiled and uploaded to the 00:10:52.630 --> 00:10:56.070 align:start position:0% code gets compiled and uploaded to the blockchain<00:10:52.870> and<00:10:54.180> proxy<00:10:55.180> address<00:10:55.510> is 00:10:56.070 --> 00:10:56.080 align:start position:0% blockchain and proxy address is 00:10:56.080 --> 00:10:59.430 align:start position:0% blockchain and proxy address is limitations<00:10:56.680> changed<00:10:57.220> to<00:10:57.370> the<00:10:57.490> new<00:10:58.440> new 00:10:59.430 --> 00:10:59.440 align:start position:0% limitations changed to the new new 00:10:59.440 --> 00:11:01.230 align:start position:0% limitations changed to the new new contract<00:10:59.950> implementation<00:11:00.640> and<00:11:00.910> all<00:11:01.090> the 00:11:01.230 --> 00:11:01.240 align:start position:0% contract implementation and all the 00:11:01.240 --> 00:11:04.470 align:start position:0% contract implementation and all the calls<00:11:01.480> after<00:11:02.170> you<00:11:02.320> upgraded<00:11:03.130> go<00:11:04.000> to<00:11:04.060> the<00:11:04.300> new 00:11:04.470 --> 00:11:04.480 align:start position:0% calls after you upgraded go to the new 00:11:04.480 --> 00:11:08.550 align:start position:0% calls after you upgraded go to the new implementation<00:11:05.550> in<00:11:06.550> that<00:11:07.180> way<00:11:07.440> you<00:11:08.440> can 00:11:08.550 --> 00:11:08.560 align:start position:0% implementation in that way you can 00:11:08.560 --> 00:11:10.950 align:start position:0% implementation in that way you can achieve<00:11:08.680> frictionless<00:11:09.520> transition<00:11:10.450> from<00:11:10.660> old 00:11:10.950 --> 00:11:10.960 align:start position:0% achieve frictionless transition from old 00:11:10.960 --> 00:11:12.930 align:start position:0% achieve frictionless transition from old called<00:11:11.500> the<00:11:11.740> human<00:11:12.100> where<00:11:12.430> you<00:11:12.550> preserve<00:11:12.910> the 00:11:12.930 --> 00:11:12.940 align:start position:0% called the human where you preserve the 00:11:12.940 --> 00:11:16.920 align:start position:0% called the human where you preserve the state<00:11:13.450> and<00:11:13.810> your<00:11:14.680> dress<00:11:15.010> which<00:11:15.430> is<00:11:15.540> place<00:11:16.540> nice 00:11:16.920 --> 00:11:16.930 align:start position:0% state and your dress which is place nice 00:11:16.930 --> 00:11:30.700 align:start position:0% state and your dress which is place nice rest<00:11:17.470> really<00:11:17.890> well<00:11:18.100> with<00:11:18.400> front-end<00:11:18.910> tools 00:11:30.700 --> 00:11:30.710 align:start position:0% 00:11:30.710 --> 00:11:35.600 align:start position:0% yet<00:11:32.000> again<00:11:33.000> ability<00:11:33.770> being<00:11:34.770> great<00:11:35.280> and 00:11:35.600 --> 00:11:35.610 align:start position:0% yet again ability being great and 00:11:35.610 --> 00:11:40.250 align:start position:0% yet again ability being great and awesome<00:11:35.790> for<00:11:36.330> many<00:11:36.510> cases<00:11:37.190> not<00:11:38.190> always<00:11:39.260> works 00:11:40.250 --> 00:11:40.260 align:start position:0% awesome for many cases not always works 00:11:40.260 --> 00:11:42.140 align:start position:0% awesome for many cases not always works for<00:11:40.560> every<00:11:41.040> project<00:11:41.280> every<00:11:41.640> environment 00:11:42.140 --> 00:11:42.150 align:start position:0% for every project every environment 00:11:42.150 --> 00:11:45.980 align:start position:0% for every project every environment every<00:11:42.840> setup<00:11:43.250> and<00:11:44.250> I<00:11:44.370> was<00:11:44.520> thinking<00:11:44.730> can<00:11:45.540> we<00:11:45.690> do 00:11:45.980 --> 00:11:45.990 align:start position:0% every setup and I was thinking can we do 00:11:45.990 --> 00:11:46.990 align:start position:0% every setup and I was thinking can we do better 00:11:46.990 --> 00:11:47.000 align:start position:0% better 00:11:47.000 --> 00:11:49.730 align:start position:0% better and<00:11:48.000> we<00:11:48.210> create<00:11:48.660> some<00:11:48.870> solution<00:11:49.380> which<00:11:49.500> will 00:11:49.730 --> 00:11:49.740 align:start position:0% and we create some solution which will 00:11:49.740 --> 00:11:55.400 align:start position:0% and we create some solution which will be<00:11:50.610> a<00:11:51.120> silver<00:11:51.510> bullet<00:11:51.870> for<00:11:53.510> four<00:11:54.510> cylinders 00:11:55.400 --> 00:11:55.410 align:start position:0% be a silver bullet for four cylinders 00:11:55.410 --> 00:11:58.130 align:start position:0% be a silver bullet for four cylinders development<00:11:55.980> and<00:11:56.100> any<00:11:56.280> environment<00:11:56.910> with<00:11:57.390> any 00:11:58.130 --> 00:11:58.140 align:start position:0% development and any environment with any 00:11:58.140 --> 00:12:06.290 align:start position:0% development and any environment with any framework<00:11:58.860> a<00:11:59.040> library<00:12:04.550> we<00:12:05.550> have<00:12:05.700> to<00:12:05.850> talk<00:12:06.060> a 00:12:06.290 --> 00:12:06.300 align:start position:0% framework a library we have to talk a 00:12:06.300 --> 00:12:11.810 align:start position:0% framework a library we have to talk a bit<00:12:06.510> about<00:12:06.540> Ganesh<00:12:08.570> before<00:12:10.190> as<00:12:11.190> you<00:12:11.490> all<00:12:11.640> know 00:12:11.810 --> 00:12:11.820 align:start position:0% bit about Ganesh before as you all know 00:12:11.820 --> 00:12:16.970 align:start position:0% bit about Ganesh before as you all know Ganesh<00:12:12.210> is<00:12:13.400> the<00:12:14.400> film<00:12:14.760> MBC<00:12:15.570> client<00:12:16.470> which<00:12:16.950> is 00:12:16.970 --> 00:12:16.980 align:start position:0% Ganesh is the film MBC client which is 00:12:16.980 --> 00:12:21.520 align:start position:0% Ganesh is the film MBC client which is really<00:12:17.490> good<00:12:17.670> for<00:12:18.000> development<00:12:18.780> testing<00:12:19.230> has 00:12:21.520 --> 00:12:21.530 align:start position:0% really good for development testing has 00:12:21.530 --> 00:12:24.560 align:start position:0% really good for development testing has slightly<00:12:22.530> used<00:12:22.740> and<00:12:23.040> has<00:12:23.730> quite<00:12:24.150> a<00:12:24.180> few<00:12:24.390> dishes 00:12:24.560 --> 00:12:24.570 align:start position:0% slightly used and has quite a few dishes 00:12:24.570 --> 00:12:27.290 align:start position:0% slightly used and has quite a few dishes to<00:12:25.080> help<00:12:25.950> you<00:12:26.130> with<00:12:26.310> testing<00:12:26.730> and<00:12:26.910> development 00:12:27.290 --> 00:12:27.300 align:start position:0% to help you with testing and development 00:12:27.300 --> 00:12:31.730 align:start position:0% to help you with testing and development and<00:12:28.140> in<00:12:28.920> particular<00:12:29.490> has<00:12:29.880> custom<00:12:30.870> methods 00:12:31.730 --> 00:12:31.740 align:start position:0% and in particular has custom methods 00:12:31.740 --> 00:12:35.600 align:start position:0% and in particular has custom methods even<00:12:32.550> snapshot<00:12:33.390> TM<00:12:33.900> revert<00:12:34.290> even<00:12:34.920> Christine 00:12:35.600 --> 00:12:35.610 align:start position:0% even snapshot TM revert even Christine 00:12:35.610 --> 00:12:39.410 align:start position:0% even snapshot TM revert even Christine and<00:12:35.970> mine<00:12:37.520> they<00:12:38.520> allow<00:12:38.790> you<00:12:38.850> to<00:12:39.030> do<00:12:39.180> things 00:12:39.410 --> 00:12:39.420 align:start position:0% and mine they allow you to do things 00:12:39.420 --> 00:12:41.540 align:start position:0% and mine they allow you to do things which<00:12:40.080> are<00:12:40.230> not<00:12:40.380> possible<00:12:40.890> on<00:12:40.950> production 00:12:41.540 --> 00:12:41.550 align:start position:0% which are not possible on production 00:12:41.550 --> 00:12:45.220 align:start position:0% which are not possible on production ready<00:12:42.210> knows<00:12:42.540> such<00:12:42.960> as<00:12:43.140> parity<00:12:43.680> in<00:12:43.770> gear<00:12:44.010> for 00:12:45.220 --> 00:12:45.230 align:start position:0% ready knows such as parity in gear for 00:12:45.230 --> 00:12:47.960 align:start position:0% ready knows such as parity in gear for example<00:12:46.230> in<00:12:46.410> action<00:12:46.740> shot<00:12:46.980> allows<00:12:47.640> you<00:12:47.850> to 00:12:47.960 --> 00:12:47.970 align:start position:0% example in action shot allows you to 00:12:47.970 --> 00:12:50.000 align:start position:0% example in action shot allows you to take<00:12:48.120> a<00:12:48.150> snapshot<00:12:48.510> of<00:12:48.750> your<00:12:48.960> blockchain<00:12:49.470> do 00:12:50.000 --> 00:12:50.010 align:start position:0% take a snapshot of your blockchain do 00:12:50.010 --> 00:12:52.250 align:start position:0% take a snapshot of your blockchain do some<00:12:50.220> stuff<00:12:50.580> and<00:12:50.910> then<00:12:51.330> go<00:12:51.540> back<00:12:51.810> through<00:12:51.840> and 00:12:52.250 --> 00:12:52.260 align:start position:0% some stuff and then go back through and 00:12:52.260 --> 00:12:56.270 align:start position:0% some stuff and then go back through and then<00:12:52.890> go<00:12:53.280> back<00:12:53.580> to<00:12:53.610> this<00:12:54.090> stage<00:12:54.420> which<00:12:55.170> is<00:12:55.320> not 00:12:56.270 --> 00:12:56.280 align:start position:0% then go back to this stage which is not 00:12:56.280 --> 00:12:57.710 align:start position:0% then go back to this stage which is not possible<00:12:56.520> a<00:12:57.000> magnet 00:12:57.710 --> 00:12:57.720 align:start position:0% possible a magnet 00:12:57.720 --> 00:13:00.170 align:start position:0% possible a magnet I<00:12:57.750> guess<00:12:58.560> honestly<00:12:58.800> doubt<00:12:59.400> but<00:12:59.820> then<00:13:00.030> it's 00:13:00.170 --> 00:13:00.180 align:start position:0% I guess honestly doubt but then it's 00:13:00.180 --> 00:13:04.220 align:start position:0% I guess honestly doubt but then it's expensive<00:13:00.480> and<00:13:02.210> with<00:13:03.210> other<00:13:03.510> commands<00:13:03.930> which 00:13:04.220 --> 00:13:04.230 align:start position:0% expensive and with other commands which 00:13:04.230 --> 00:13:06.290 align:start position:0% expensive and with other commands which is<00:13:04.380> increased<00:13:04.800> time<00:13:05.010> enough<00:13:05.460> to<00:13:05.700> jump<00:13:05.940> in<00:13:06.120> time 00:13:06.290 --> 00:13:06.300 align:start position:0% is increased time enough to jump in time 00:13:06.300 --> 00:13:09.380 align:start position:0% is increased time enough to jump in time forward<00:13:06.810> to<00:13:07.140> really<00:13:07.680> helpful<00:13:08.160> with<00:13:08.910> testing 00:13:09.380 --> 00:13:09.390 align:start position:0% forward to really helpful with testing 00:13:09.390 --> 00:13:11.690 align:start position:0% forward to really helpful with testing and<00:13:09.570> give<00:13:10.440> in<00:13:10.560> mind<00:13:10.830> allows<00:13:11.280> you<00:13:11.400> to<00:13:11.520> mighty 00:13:11.690 --> 00:13:11.700 align:start position:0% and give in mind allows you to mighty 00:13:11.700 --> 00:13:14.000 align:start position:0% and give in mind allows you to mighty block<00:13:12.030> as<00:13:12.480> you<00:13:12.540> can<00:13:12.750> see<00:13:12.900> something<00:13:13.830> similar 00:13:14.000 --> 00:13:14.010 align:start position:0% block as you can see something similar 00:13:14.010 --> 00:13:16.310 align:start position:0% block as you can see something similar between<00:13:14.400> his<00:13:14.670> commands<00:13:15.060> is<00:13:15.330> that<00:13:15.570> they<00:13:15.990> allow 00:13:16.310 --> 00:13:16.320 align:start position:0% between his commands is that they allow 00:13:16.320 --> 00:13:17.870 align:start position:0% between his commands is that they allow you<00:13:16.380> to<00:13:16.470> do<00:13:16.650> things<00:13:16.950> which<00:13:17.340> are<00:13:17.520> not<00:13:17.610> possible 00:13:17.870 --> 00:13:17.880 align:start position:0% you to do things which are not possible 00:13:17.880 --> 00:13:21.140 align:start position:0% you to do things which are not possible on<00:13:18.180> mayhem<00:13:18.920> yeah<00:13:19.980> it's<00:13:20.370> extremely<00:13:20.730> variable 00:13:21.140 --> 00:13:21.150 align:start position:0% on mayhem yeah it's extremely variable 00:13:21.150 --> 00:13:26.249 align:start position:0% on mayhem yeah it's extremely variable and<00:13:21.630> how<00:13:21.780> to<00:13:21.840> do<00:13:22.230> in<00:13:22.380> testing<00:13:22.800> in<00:13:22.950> development 00:13:26.249 --> 00:13:26.259 align:start position:0% 00:13:26.259 --> 00:13:28.919 align:start position:0% and<00:13:26.350> I<00:13:26.889> was<00:13:27.100> asking<00:13:27.369> myself<00:13:27.519> is<00:13:28.239> there<00:13:28.449> any 00:13:28.919 --> 00:13:28.929 align:start position:0% and I was asking myself is there any 00:13:28.929 --> 00:13:32.729 align:start position:0% and I was asking myself is there any missing<00:13:29.769> comments<00:13:30.339> for<00:13:30.639> our<00:13:31.739> test 00:13:32.729 --> 00:13:32.739 align:start position:0% missing comments for our test 00:13:32.739 --> 00:13:40.159 align:start position:0% missing comments for our test development<00:13:33.459> Hulme<00:13:34.149> clients<00:13:37.199> I<00:13:38.199> want<00:13:38.739> to 00:13:40.159 --> 00:13:40.169 align:start position:0% development Hulme clients I want to 00:13:40.169 --> 00:13:45.179 align:start position:0% development Hulme clients I want to suggest<00:13:41.169> the<00:13:41.999> presenter<00:13:42.999> evm<00:13:43.539> a<00:13:43.779> big<00:13:44.189> command 00:13:45.179 --> 00:13:45.189 align:start position:0% suggest the presenter evm a big command 00:13:45.189 --> 00:13:47.609 align:start position:0% suggest the presenter evm a big command this<00:13:45.669> to<00:13:45.879> be<00:13:46.059> absolutely<00:13:46.629> clear<00:13:46.839> this<00:13:47.229> is<00:13:47.410> on 00:13:47.609 --> 00:13:47.619 align:start position:0% this to be absolutely clear this is on 00:13:47.619 --> 00:13:50.819 align:start position:0% this to be absolutely clear this is on the<00:13:47.799> state<00:13:48.069> of<00:13:48.100> an<00:13:48.459> idea<00:13:49.379> proposal<00:13:50.379> research 00:13:50.819 --> 00:13:50.829 align:start position:0% the state of an idea proposal research 00:13:50.829 --> 00:13:54.869 align:start position:0% the state of an idea proposal research at<00:13:51.039> this<00:13:51.220> moment<00:13:52.499> the<00:13:53.499> idea<00:13:53.829> and<00:13:54.279> this<00:13:54.429> command 00:13:54.869 --> 00:13:54.879 align:start position:0% at this moment the idea and this command 00:13:54.879 --> 00:13:59.219 align:start position:0% at this moment the idea and this command is<00:13:55.299> it<00:13:56.079> will<00:13:56.289> allow<00:13:56.379> you<00:13:57.329> to<00:13:58.329> upgrade<00:13:58.660> smart 00:13:59.219 --> 00:13:59.229 align:start position:0% is it will allow you to upgrade smart 00:13:59.229 --> 00:14:03.629 align:start position:0% is it will allow you to upgrade smart contracts<00:14:00.720> in<00:14:01.720> the<00:14:01.749> really<00:14:02.619> hard<00:14:02.859> way<00:14:03.160> evolve 00:14:03.629 --> 00:14:03.639 align:start position:0% contracts in the really hard way evolve 00:14:03.639 --> 00:14:06.379 align:start position:0% contracts in the really hard way evolve like<00:14:03.910> my<00:14:04.149> notes<00:14:04.629> or<00:14:05.019> I<00:14:05.229> turn<00:14:05.289> anything<00:14:05.979> else 00:14:06.379 --> 00:14:06.389 align:start position:0% like my notes or I turn anything else 00:14:06.389 --> 00:14:08.789 align:start position:0% like my notes or I turn anything else essentially<00:14:07.389> just<00:14:07.569> swapping<00:14:07.929> the 00:14:08.789 --> 00:14:08.799 align:start position:0% essentially just swapping the 00:14:08.799 --> 00:14:12.359 align:start position:0% essentially just swapping the implementation<00:14:09.579> of<00:14:09.669> one<00:14:10.769> implementation<00:14:11.769> of 00:14:12.359 --> 00:14:12.369 align:start position:0% implementation of one implementation of 00:14:12.369 --> 00:14:17.449 align:start position:0% implementation of one implementation of smart<00:14:13.269> contract<00:14:13.689> with<00:14:13.809> another<00:14:14.199> limitation 00:14:17.449 --> 00:14:17.459 align:start position:0% 00:14:17.459 --> 00:14:20.159 align:start position:0% so<00:14:18.459> I'm<00:14:18.850> going<00:14:19.029> to<00:14:19.119> give<00:14:19.269> a<00:14:19.299> quick<00:14:19.569> example<00:14:19.720> of 00:14:20.159 --> 00:14:20.169 align:start position:0% so I'm going to give a quick example of 00:14:20.169 --> 00:14:21.499 align:start position:0% so I'm going to give a quick example of how<00:14:20.229> it's<00:14:20.499> gonna<00:14:20.619> work 00:14:21.499 --> 00:14:21.509 align:start position:0% how it's gonna work 00:14:21.509 --> 00:14:24.629 align:start position:0% how it's gonna work let's<00:14:22.509> say<00:14:22.720> because<00:14:23.619> the<00:14:23.919> same<00:14:24.189> smart 00:14:24.629 --> 00:14:24.639 align:start position:0% let's say because the same smart 00:14:24.639 --> 00:14:26.909 align:start position:0% let's say because the same smart contract<00:14:25.089> under<00:14:25.299> which<00:14:25.509> you<00:14:26.019> know<00:14:26.259> we<00:14:26.649> have 00:14:26.909 --> 00:14:26.919 align:start position:0% contract under which you know we have 00:14:26.919 --> 00:14:31.379 align:start position:0% contract under which you know we have expert<00:14:27.759> knowledge<00:14:27.789> fun<00:14:28.359> and<00:14:29.970> the<00:14:30.970> original 00:14:31.379 --> 00:14:31.389 align:start position:0% expert knowledge fun and the original 00:14:31.389 --> 00:14:34.169 align:start position:0% expert knowledge fun and the original limitation<00:14:32.139> just<00:14:33.039> improves<00:14:33.369> the<00:14:33.519> count<00:14:33.789> by 00:14:34.169 --> 00:14:34.179 align:start position:0% limitation just improves the count by 00:14:34.179 --> 00:14:37.379 align:start position:0% limitation just improves the count by one<00:14:34.419> but<00:14:35.289> you<00:14:35.439> want<00:14:35.649> to<00:14:35.799> allow<00:14:36.009> is<00:14:36.999> to<00:14:37.239> be 00:14:37.379 --> 00:14:37.389 align:start position:0% one but you want to allow is to be 00:14:37.389 --> 00:14:41.669 align:start position:0% one but you want to allow is to be increased<00:14:37.720> by<00:14:37.989> any<00:14:38.259> arbitrary<00:14:39.069> amount<00:14:39.720> and<00:14:40.720> on 00:14:41.669 --> 00:14:41.679 align:start position:0% increased by any arbitrary amount and on 00:14:41.679 --> 00:14:45.389 align:start position:0% increased by any arbitrary amount and on the<00:14:41.919> left 00:14:45.389 --> 00:14:45.399 align:start position:0% 00:14:45.399 --> 00:14:47.909 align:start position:0% series<00:14:46.179> of<00:14:46.359> course<00:14:46.629> from<00:14:46.989> top<00:14:47.199> to<00:14:47.230> bottom<00:14:47.410> and 00:14:47.909 --> 00:14:47.919 align:start position:0% series of course from top to bottom and 00:14:47.919 --> 00:14:50.549 align:start position:0% series of course from top to bottom and to<00:14:48.730> start<00:14:48.999> with<00:14:49.179> an<00:14:49.299> account<00:14:49.629> get<00:14:50.049> counter 00:14:50.549 --> 00:14:50.559 align:start position:0% to start with an account get counter 00:14:50.559 --> 00:14:52.889 align:start position:0% to start with an account get counter which<00:14:50.799> which<00:14:51.069> on<00:14:51.220> 32<00:14:51.759> is<00:14:51.999> the<00:14:52.029> initial<00:14:52.509> state 00:14:52.889 --> 00:14:52.899 align:start position:0% which which on 32 is the initial state 00:14:52.899 --> 00:14:56.189 align:start position:0% which which on 32 is the initial state of<00:14:53.139> our<00:14:53.499> contract<00:14:54.160> and<00:14:54.519> then<00:14:55.509> you<00:14:55.779> gotta<00:14:55.959> call 00:14:56.189 --> 00:14:56.199 align:start position:0% of our contract and then you gotta call 00:14:56.199 --> 00:15:00.179 align:start position:0% of our contract and then you gotta call EVM<00:14:56.679> update<00:14:57.039> to<00:14:57.579> update<00:14:58.289> the<00:14:59.289> smart<00:14:59.980> contract 00:15:00.179 --> 00:15:00.189 align:start position:0% EVM update to update the smart contract 00:15:00.189 --> 00:15:04.109 align:start position:0% EVM update to update the smart contract between<00:15:00.730> you<00:15:01.029> by<00:15:01.239> code<00:15:01.619> which<00:15:02.619> will<00:15:03.249> be<00:15:03.489> by 00:15:04.109 --> 00:15:04.119 align:start position:0% between you by code which will be by 00:15:04.119 --> 00:15:06.689 align:start position:0% between you by code which will be by called<00:15:04.509> allowing<00:15:05.079> to<00:15:05.289> increase<00:15:06.129> it<00:15:06.279> by<00:15:06.399> any 00:15:06.689 --> 00:15:06.699 align:start position:0% called allowing to increase it by any 00:15:06.699 --> 00:15:09.840 align:start position:0% called allowing to increase it by any month<00:15:07.350> and<00:15:08.350> after<00:15:08.499> that<00:15:08.829> we<00:15:09.369> wanna<00:15:09.549> call 00:15:09.840 --> 00:15:09.850 align:start position:0% month and after that we wanna call 00:15:09.850 --> 00:15:12.149 align:start position:0% month and after that we wanna call increased<00:15:10.480> counter<00:15:10.989> method<00:15:11.379> here<00:15:11.799> isn't 00:15:12.149 --> 00:15:12.159 align:start position:0% increased counter method here isn't 00:15:12.159 --> 00:15:15.179 align:start position:0% increased counter method here isn't quite<00:15:12.249> free<00:15:12.730> but<00:15:13.720> this<00:15:14.350> car<00:15:14.619> is<00:15:14.649> not<00:15:14.889> going<00:15:15.069> to 00:15:15.179 --> 00:15:15.189 align:start position:0% quite free but this car is not going to 00:15:15.189 --> 00:15:17.699 align:start position:0% quite free but this car is not going to fail<00:15:15.399> because<00:15:15.819> now<00:15:16.239> code<00:15:16.689> now<00:15:16.959> our<00:15:17.169> contract 00:15:17.699 --> 00:15:17.709 align:start position:0% fail because now code now our contract 00:15:17.709 --> 00:15:18.240 align:start position:0% fail because now code now our contract has 00:15:18.240 --> 00:15:18.250 align:start position:0% has 00:15:18.250 --> 00:15:22.110 align:start position:0% has you<00:15:19.860> implementation<00:15:20.860> and<00:15:21.340> after<00:15:21.730> that<00:15:21.880> we're 00:15:22.110 --> 00:15:22.120 align:start position:0% you implementation and after that we're 00:15:22.120 --> 00:15:24.240 align:start position:0% you implementation and after that we're gonna<00:15:22.240> call<00:15:22.660> a<00:15:22.900> jet<00:15:23.080> counter<00:15:23.560> method<00:15:23.920> which 00:15:24.240 --> 00:15:24.250 align:start position:0% gonna call a jet counter method which 00:15:24.250 --> 00:15:27.980 align:start position:0% gonna call a jet counter method which returns<00:15:24.460> the<00:15:25.000> magnitude<00:15:25.930> 35<00:15:26.440> in<00:15:26.800> that<00:15:27.250> way<00:15:27.460> not 00:15:27.980 --> 00:15:27.990 align:start position:0% returns the magnitude 35 in that way not 00:15:27.990 --> 00:15:31.560 align:start position:0% returns the magnitude 35 in that way not only<00:15:28.990> we<00:15:29.320> are<00:15:29.350> graded<00:15:29.860> our<00:15:30.330> contract<00:15:31.330> we<00:15:31.420> also 00:15:31.560 --> 00:15:31.570 align:start position:0% only we are graded our contract we also 00:15:31.570 --> 00:15:35.700 align:start position:0% only we are graded our contract we also preserve<00:15:31.990> this<00:15:32.410> day<00:15:33.360> and<00:15:34.360> address<00:15:34.840> which<00:15:35.530> is 00:15:35.700 --> 00:15:35.710 align:start position:0% preserve this day and address which is 00:15:35.710 --> 00:15:37.530 align:start position:0% preserve this day and address which is really<00:15:36.100> important<00:15:36.580> for<00:15:36.610> developers<00:15:37.210> schools 00:15:37.530 --> 00:15:37.540 align:start position:0% really important for developers schools 00:15:37.540 --> 00:15:40.470 align:start position:0% really important for developers schools because<00:15:38.460> you<00:15:39.460> want<00:15:39.670> to<00:15:39.700> have<00:15:40.000> you<00:15:40.240> want<00:15:40.270> to 00:15:40.470 --> 00:15:40.480 align:start position:0% because you want to have you want to 00:15:40.480 --> 00:15:44.240 align:start position:0% because you want to have you want to hide<00:15:40.690> all<00:15:41.140> the<00:15:41.320> complexity<00:15:42.010> from<00:15:42.370> the<00:15:42.550> user<00:15:42.790> a 00:15:44.240 --> 00:15:44.250 align:start position:0% hide all the complexity from the user a 00:15:44.250 --> 00:15:48.330 align:start position:0% hide all the complexity from the user a developer<00:15:45.270> and<00:15:46.270> to<00:15:47.110> hide<00:15:47.290> it<00:15:47.500> inside<00:15:47.740> the<00:15:48.130> dev 00:15:48.330 --> 00:15:48.340 align:start position:0% developer and to hide it inside the dev 00:15:48.340 --> 00:15:53.130 align:start position:0% developer and to hide it inside the dev tools<00:15:49.470> in<00:15:50.470> this<00:15:50.650> approach<00:15:51.040> as<00:15:51.930> might<00:15:52.930> be<00:15:52.960> in 00:15:53.130 --> 00:15:53.140 align:start position:0% tools in this approach as might be in 00:15:53.140 --> 00:15:55.680 align:start position:0% tools in this approach as might be in English<00:15:53.500> which<00:15:54.310> surfaced<00:15:54.850> an<00:15:55.000> opportunity 00:15:55.680 --> 00:15:55.690 align:start position:0% English which surfaced an opportunity 00:15:55.690 --> 00:15:58.860 align:start position:0% English which surfaced an opportunity for<00:15:55.990> other<00:15:56.350> developers<00:15:57.130> tools<00:15:57.340> as<00:15:57.520> well<00:15:57.870> where 00:15:58.860 --> 00:15:58.870 align:start position:0% for other developers tools as well where 00:15:58.870 --> 00:16:04.710 align:start position:0% for other developers tools as well where ability<00:15:59.830> just<00:16:00.790> modified<00:16:01.980> any<00:16:03.720> modified 00:16:04.710 --> 00:16:04.720 align:start position:0% ability just modified any modified 00:16:04.720 --> 00:16:06.360 align:start position:0% ability just modified any modified mutation<00:16:05.260> of<00:16:05.380> management<00:16:05.890> contract<00:16:06.280> of 00:16:06.360 --> 00:16:06.370 align:start position:0% mutation of management contract of 00:16:06.370 --> 00:16:08.640 align:start position:0% mutation of management contract of course<00:16:06.610> not<00:16:06.940> gonna<00:16:07.180> happen<00:16:08.020> on<00:16:08.320> the<00:16:08.410> black 00:16:08.640 --> 00:16:08.650 align:start position:0% course not gonna happen on the black 00:16:08.650 --> 00:16:12.540 align:start position:0% course not gonna happen on the black chain<00:16:08.920> in<00:16:09.190> anywhere<00:16:09.880> anytime<00:16:10.380> but<00:16:11.380> again<00:16:11.860> it's 00:16:12.540 --> 00:16:12.550 align:start position:0% chain in anywhere anytime but again it's 00:16:12.550 --> 00:16:14.430 align:start position:0% chain in anywhere anytime but again it's very<00:16:12.910> variable<00:16:13.240> for<00:16:13.600> developer<00:16:14.020> tools<00:16:14.260> and 00:16:14.430 --> 00:16:14.440 align:start position:0% very variable for developer tools and 00:16:14.440 --> 00:16:17.100 align:start position:0% very variable for developer tools and will<00:16:14.740> enable<00:16:15.010> all<00:16:15.460> sorts<00:16:15.910> of<00:16:16.030> tricks<00:16:16.750> which 00:16:17.100 --> 00:16:17.110 align:start position:0% will enable all sorts of tricks which 00:16:17.110 --> 00:16:20.370 align:start position:0% will enable all sorts of tricks which will<00:16:17.380> make<00:16:18.130> each<00:16:18.520> video<00:16:18.760> for<00:16:19.600> the<00:16:19.840> development 00:16:20.370 --> 00:16:20.380 align:start position:0% will make each video for the development 00:16:20.380 --> 00:16:29.150 align:start position:0% will make each video for the development process 00:16:29.150 --> 00:16:29.160 align:start position:0% 00:16:29.160 --> 00:16:32.990 align:start position:0% then<00:16:30.090> I<00:16:30.120> won't<00:16:30.480> talk<00:16:30.690> a<00:16:30.750> bit<00:16:31.020> of<00:16:31.400> teacher<00:16:32.400> free 00:16:32.990 --> 00:16:33.000 align:start position:0% then I won't talk a bit of teacher free 00:16:33.000 --> 00:16:36.710 align:start position:0% then I won't talk a bit of teacher free death<00:16:33.210> tolls<00:16:33.740> in<00:16:34.740> the<00:16:34.950> way<00:16:35.070> that<00:16:35.430> I<00:16:35.760> believe 00:16:36.710 --> 00:16:36.720 align:start position:0% death tolls in the way that I believe 00:16:36.720 --> 00:16:39.110 align:start position:0% death tolls in the way that I believe the<00:16:36.900> future<00:16:37.140> is<00:16:37.440> that<00:16:37.680> predefined<00:16:38.340> remain 00:16:39.110 --> 00:16:39.120 align:start position:0% the future is that predefined remain 00:16:39.120 --> 00:16:42.170 align:start position:0% the future is that predefined remain many<00:16:39.750> possible<00:16:40.410> fishes<00:16:40.830> and<00:16:41.460> if<00:16:41.610> you<00:16:41.760> all<00:16:41.970> know 00:16:42.170 --> 00:16:42.180 align:start position:0% many possible fishes and if you all know 00:16:42.180 --> 00:16:45.140 align:start position:0% many possible fishes and if you all know almost<00:16:42.570> a<00:16:42.779> century<00:16:43.020> ago<00:16:43.460> gasps<00:16:44.460> cries<00:16:44.880> were 00:16:45.140 --> 00:16:45.150 align:start position:0% almost a century ago gasps cries were 00:16:45.150 --> 00:16:48.170 align:start position:0% almost a century ago gasps cries were completed<00:16:45.630> electric<00:16:46.230> cars<00:16:46.500> but<00:16:47.370> for<00:16:48.000> some 00:16:48.170 --> 00:16:48.180 align:start position:0% completed electric cars but for some 00:16:48.180 --> 00:16:50.960 align:start position:0% completed electric cars but for some reverse<00:16:48.750> reasons<00:16:49.290> electric<00:16:49.620> cars<00:16:49.890> lost<00:16:50.700> the 00:16:50.960 --> 00:16:50.970 align:start position:0% reverse reasons electric cars lost the 00:16:50.970 --> 00:16:53.750 align:start position:0% reverse reasons electric cars lost the bet<00:16:51.150> off<00:16:51.180> to<00:16:51.570> the<00:16:51.690> gas<00:16:51.870> cars<00:16:52.230> and<00:16:52.620> only<00:16:53.460> right 00:16:53.750 --> 00:16:53.760 align:start position:0% bet off to the gas cars and only right 00:16:53.760 --> 00:16:54.410 align:start position:0% bet off to the gas cars and only right now 00:16:54.410 --> 00:16:54.420 align:start position:0% now 00:16:54.420 --> 00:16:56.690 align:start position:0% now electric<00:16:55.350> cars<00:16:55.589> starting<00:16:56.160> to<00:16:56.310> get<00:16:56.430> some 00:16:56.690 --> 00:16:56.700 align:start position:0% electric cars starting to get some 00:16:56.700 --> 00:17:03.250 align:start position:0% electric cars starting to get some traction<00:16:59.060> and<00:17:00.380> in<00:17:01.380> this<00:17:01.500> way<00:17:02.120> blockchain 00:17:03.250 --> 00:17:03.260 align:start position:0% traction and in this way blockchain 00:17:03.260 --> 00:17:06.110 align:start position:0% traction and in this way blockchain doesn't<00:17:04.260> particularly<00:17:04.770> has<00:17:05.189> to<00:17:05.400> happen<00:17:05.610> where 00:17:06.110 --> 00:17:06.120 align:start position:0% doesn't particularly has to happen where 00:17:06.120 --> 00:17:08.689 align:start position:0% doesn't particularly has to happen where like<00:17:06.329> other<00:17:06.600> futures<00:17:07.170> where<00:17:07.380> it<00:17:08.130> happens<00:17:08.550> in 00:17:08.689 --> 00:17:08.699 align:start position:0% like other futures where it happens in 00:17:08.699 --> 00:17:09.679 align:start position:0% like other futures where it happens in 100<00:17:09.209> years 00:17:09.679 --> 00:17:09.689 align:start position:0% 100 years 00:17:09.689 --> 00:17:11.420 align:start position:0% 100 years but<00:17:10.020> I<00:17:10.199> personally<00:17:10.260> don't<00:17:10.709> want<00:17:10.949> it<00:17:11.160> to<00:17:11.280> happen 00:17:11.420 --> 00:17:11.430 align:start position:0% but I personally don't want it to happen 00:17:11.430 --> 00:17:14.929 align:start position:0% but I personally don't want it to happen in<00:17:11.699> 100<00:17:12.240> years<00:17:12.860> because<00:17:13.860> I<00:17:14.130> want<00:17:14.640> to<00:17:14.699> see 00:17:14.929 --> 00:17:14.939 align:start position:0% in 100 years because I want to see 00:17:14.939 --> 00:17:18.170 align:start position:0% in 100 years because I want to see happen<00:17:15.390> and<00:17:15.530> I<00:17:16.550> believe<00:17:17.550> that<00:17:17.760> if<00:17:18.000> I 00:17:18.170 --> 00:17:18.180 align:start position:0% happen and I believe that if I 00:17:18.180 --> 00:17:21.110 align:start position:0% happen and I believe that if I developers<00:17:19.140> tools<00:17:19.560> you'll<00:17:20.010> stay<00:17:20.310> on<00:17:20.640> the 00:17:21.110 --> 00:17:21.120 align:start position:0% developers tools you'll stay on the 00:17:21.120 --> 00:17:21.439 align:start position:0% developers tools you'll stay on the level 00:17:21.439 --> 00:17:21.449 align:start position:0% level 00:17:21.449 --> 00:17:24.140 align:start position:0% level Internet<00:17:21.900> Explorer<00:17:22.230> sees<00:17:22.560> is<00:17:23.459> going<00:17:23.819> to<00:17:23.939> try 00:17:24.140 --> 00:17:24.150 align:start position:0% Internet Explorer sees is going to try 00:17:24.150 --> 00:17:26.390 align:start position:0% Internet Explorer sees is going to try to<00:17:24.209> bring<00:17:24.689> new<00:17:24.930> developers<00:17:25.740> to<00:17:25.949> the<00:17:26.040> field<00:17:26.280> in 00:17:26.390 --> 00:17:26.400 align:start position:0% to bring new developers to the field in 00:17:26.400 --> 00:17:28.550 align:start position:0% to bring new developers to the field in the<00:17:26.490> system<00:17:26.910> because<00:17:27.300> the<00:17:27.569> expectations 00:17:28.550 --> 00:17:28.560 align:start position:0% the system because the expectations 00:17:28.560 --> 00:17:31.100 align:start position:0% the system because the expectations right<00:17:28.800> now<00:17:29.010> developers<00:17:29.730> so<00:17:29.940> high<00:17:30.240> they'd<00:17:31.050> be 00:17:31.100 --> 00:17:31.110 align:start position:0% right now developers so high they'd be 00:17:31.110 --> 00:17:35.480 align:start position:0% right now developers so high they'd be like<00:17:31.410> super<00:17:31.860> spoiled<00:17:32.370> and<00:17:33.920> unless<00:17:34.920> we<00:17:35.340> make 00:17:35.480 --> 00:17:35.490 align:start position:0% like super spoiled and unless we make 00:17:35.490 --> 00:17:38.540 align:start position:0% like super spoiled and unless we make this<00:17:36.200> awesome<00:17:37.200> we're<00:17:37.679> three<00:17:37.980> developers 00:17:38.540 --> 00:17:38.550 align:start position:0% this awesome we're three developers 00:17:38.550 --> 00:17:41.900 align:start position:0% this awesome we're three developers which<00:17:38.790> happen<00:17:39.330> I<00:17:39.890> would<00:17:40.890> say<00:17:41.130> it's<00:17:41.580> going<00:17:41.700> to 00:17:41.900 --> 00:17:41.910 align:start position:0% which happen I would say it's going to 00:17:41.910 --> 00:17:44.720 align:start position:0% which happen I would say it's going to be<00:17:42.000> incredibly<00:17:42.540> hard<00:17:42.929> to<00:17:43.290> achieve<00:17:43.730> developer 00:17:44.720 --> 00:17:44.730 align:start position:0% be incredibly hard to achieve developer 00:17:44.730 --> 00:17:49.650 align:start position:0% be incredibly hard to achieve developer adoption 00:17:49.650 --> 00:17:49.660 align:start position:0% 00:17:49.660 --> 00:17:56.580 align:start position:0% I<00:17:49.800> urge<00:17:50.800> you<00:17:50.950> all<00:17:51.130> to<00:17:51.340> try<00:17:51.940> uploading<00:17:52.540> today<00:17:55.590> do 00:17:56.580 --> 00:17:56.590 align:start position:0% I urge you all to try uploading today do 00:17:56.590 --> 00:18:00.180 align:start position:0% I urge you all to try uploading today do it<00:17:56.770> just<00:17:57.070> run<00:17:57.310> ten<00:17:57.670> Peaks<00:17:58.500> seal<00:17:59.500> I<00:17:59.650> unpacked 00:18:00.180 --> 00:18:00.190 align:start position:0% it just run ten Peaks seal I unpacked 00:18:00.190 --> 00:18:03.480 align:start position:0% it just run ten Peaks seal I unpacked the<00:18:01.030> oil<00:18:01.450> commend<00:18:01.840> and<00:18:02.080> by<00:18:02.710> the<00:18:02.770> way<00:18:03.010> this<00:18:03.250> is 00:18:03.480 --> 00:18:03.490 align:start position:0% the oil commend and by the way this is 00:18:03.490 --> 00:18:10.440 align:start position:0% the oil commend and by the way this is the<00:18:03.520> slide<00:18:04.300> where<00:18:04.600> you<00:18:04.630> take<00:18:04.990> a<00:18:05.020> picture<00:18:09.450> but 00:18:10.440 --> 00:18:10.450 align:start position:0% the slide where you take a picture but 00:18:10.450 --> 00:18:13.740 align:start position:0% the slide where you take a picture but if<00:18:10.630> you<00:18:10.780> security<00:18:11.290> you<00:18:12.150> concerned<00:18:13.150> person<00:18:13.360> and 00:18:13.740 --> 00:18:13.750 align:start position:0% if you security you concerned person and 00:18:13.750 --> 00:18:15.930 align:start position:0% if you security you concerned person and don't<00:18:13.900> want<00:18:14.170> to<00:18:14.230> run<00:18:14.530> random<00:18:15.220> calls<00:18:15.490> on<00:18:15.790> your 00:18:15.930 --> 00:18:15.940 align:start position:0% don't want to run random calls on your 00:18:15.940 --> 00:18:19.220 align:start position:0% don't want to run random calls on your machine<00:18:16.270> you<00:18:16.510> can<00:18:17.080> just<00:18:17.290> go<00:18:17.440> to<00:18:17.500> open<00:18:18.460> Zeppelin 00:18:19.220 --> 00:18:19.230 align:start position:0% machine you can just go to open Zeppelin 00:18:19.230 --> 00:18:22.800 align:start position:0% machine you can just go to open Zeppelin github<00:18:20.230> account<00:18:20.620> and<00:18:21.000> clone<00:18:22.000> start<00:18:22.480> repeat 00:18:22.800 --> 00:18:22.810 align:start position:0% github account and clone start repeat 00:18:22.810 --> 00:18:26.100 align:start position:0% github account and clone start repeat tutorial<00:18:23.550> this<00:18:24.550> is<00:18:24.610> a<00:18:24.730> tutorial<00:18:25.060> which<00:18:25.450> has 00:18:26.100 --> 00:18:26.110 align:start position:0% tutorial this is a tutorial which has 00:18:26.110 --> 00:18:29.160 align:start position:0% tutorial this is a tutorial which has say<00:18:26.890> to<00:18:26.950> upload<00:18:27.490> your<00:18:27.700> there<00:18:27.970> enable<00:18:28.780> so<00:18:29.110> you 00:18:29.160 --> 00:18:29.170 align:start position:0% say to upload your there enable so you 00:18:29.170 --> 00:18:32.400 align:start position:0% say to upload your there enable so you can<00:18:29.380> wherever<00:18:29.800> it<00:18:30.100> does<00:18:30.610> has<00:18:31.000> a<00:18:31.360> great<00:18:32.290> ability 00:18:32.400 --> 00:18:32.410 align:start position:0% can wherever it does has a great ability 00:18:32.410 --> 00:18:37.110 align:start position:0% can wherever it does has a great ability insulite<00:18:33.720> so<00:18:34.720> you<00:18:34.780> get<00:18:35.230> more<00:18:35.620> than<00:18:35.860> just<00:18:36.130> a<00:18:36.790> lot 00:18:37.110 --> 00:18:37.120 align:start position:0% insulite so you get more than just a lot 00:18:37.120 --> 00:18:40.620 align:start position:0% insulite so you get more than just a lot of<00:18:37.330> the<00:18:37.450> ladies<00:18:37.870> and<00:18:38.730> it's<00:18:39.730> rather<00:18:40.030> polished 00:18:40.620 --> 00:18:40.630 align:start position:0% of the ladies and it's rather polished 00:18:40.630 --> 00:18:45.540 align:start position:0% of the ladies and it's rather polished experience<00:18:43.590> thank<00:18:44.590> you<00:18:44.680> very<00:18:44.860> much<00:18:45.070> for<00:18:45.280> time 00:18:45.540 --> 00:18:45.550 align:start position:0% experience thank you very much for time 00:18:45.550 --> 00:18:51.760 align:start position:0% experience thank you very much for time and<00:18:45.730> patience 00:18:51.760 --> 00:18:51.770 align:start position:0% 00:18:51.770 --> 00:18:56.220 align:start position:0% [Applause]