WEBVTT Kind: captions Language: en 00:00:13.170 --> 00:00:18.300 align:start position:0% okay<00:00:14.170> welcome<00:00:14.940> back<00:00:15.940> from<00:00:16.150> lunch<00:00:16.829> now<00:00:17.829> we<00:00:17.890> will 00:00:18.300 --> 00:00:18.310 align:start position:0% okay welcome back from lunch now we will 00:00:18.310 --> 00:00:22.050 align:start position:0% okay welcome back from lunch now we will be<00:00:18.429> speaking<00:00:18.699> about<00:00:18.939> web<00:00:19.509> 3js<00:00:20.289> 1.0<00:00:21.099> which<00:00:21.550> is<00:00:21.789> a 00:00:22.050 --> 00:00:22.060 align:start position:0% be speaking about web 3js 1.0 which is a 00:00:22.060 --> 00:00:26.069 align:start position:0% be speaking about web 3js 1.0 which is a major<00:00:22.869> refactor<00:00:23.679> from<00:00:24.099> the<00:00:24.999> early<00:00:25.569> version 00:00:26.069 --> 00:00:26.079 align:start position:0% major refactor from the early version 00:00:26.079 --> 00:00:30.439 align:start position:0% major refactor from the early version which<00:00:27.039> was<00:00:27.789> around<00:00:28.119> for<00:00:28.359> the<00:00:28.419> last<00:00:28.569> two<00:00:28.989> years 00:00:30.439 --> 00:00:30.449 align:start position:0% which was around for the last two years 00:00:30.449 --> 00:00:33.780 align:start position:0% which was around for the last two years shortly<00:00:31.449> about<00:00:31.509> myself<00:00:32.280> my<00:00:33.280> problem-focused 00:00:33.780 --> 00:00:33.790 align:start position:0% shortly about myself my problem-focused 00:00:33.790 --> 00:00:38.840 align:start position:0% shortly about myself my problem-focused Ella<00:00:34.210> I<00:00:34.620> am<00:00:35.620> bill<00:00:36.370> T<00:00:36.640> initially<00:00:37.330> film<00:00:38.110> wallet 00:00:38.840 --> 00:00:38.850 align:start position:0% Ella I am bill T initially film wallet 00:00:38.850 --> 00:00:40.410 align:start position:0% Ella I am bill T initially film wallet miss<00:00:39.850> Bowser 00:00:40.410 --> 00:00:40.420 align:start position:0% miss Bowser 00:00:40.420 --> 00:00:43.520 align:start position:0% miss Bowser and<00:00:41.040> worked<00:00:42.040> on<00:00:42.220> web<00:00:42.370> through<00:00:42.550> jazz<00:00:42.760> since 00:00:43.520 --> 00:00:43.530 align:start position:0% and worked on web through jazz since 00:00:43.530 --> 00:00:46.610 align:start position:0% and worked on web through jazz since there<00:00:44.530> are<00:00:44.650> two<00:00:44.920> and<00:00:45.010> a<00:00:45.040> half<00:00:45.160> years<00:00:45.460> roughly 00:00:46.610 --> 00:00:46.620 align:start position:0% there are two and a half years roughly 00:00:46.620 --> 00:00:50.520 align:start position:0% there are two and a half years roughly build<00:00:47.620> a<00:00:47.710> few<00:00:47.890> other<00:00:47.980> things<00:00:48.510> also<00:00:49.530> initiated 00:00:50.520 --> 00:00:50.530 align:start position:0% build a few other things also initiated 00:00:50.530 --> 00:00:53.610 align:start position:0% build a few other things also initiated the<00:00:50.710> UC<00:00:51.190> 20<00:00:51.640> tokens<00:00:52.090> standard<00:00:52.510> together<00:00:53.440> with 00:00:53.610 --> 00:00:53.620 align:start position:0% the UC 20 tokens standard together with 00:00:53.620 --> 00:00:57.180 align:start position:0% the UC 20 tokens standard together with italic<00:00:54.070> and<00:00:54.750> did<00:00:55.750> a<00:00:55.780> lot<00:00:56.410> of<00:00:56.440> other<00:00:56.620> smaller 00:00:57.180 --> 00:00:57.190 align:start position:0% italic and did a lot of other smaller 00:00:57.190 --> 00:01:02.060 align:start position:0% italic and did a lot of other smaller things<00:00:57.550> in<00:00:58.060> the<00:00:58.240> space<00:00:59.880> the<00:01:00.880> web<00:01:01.060> switches 00:01:02.060 --> 00:01:02.070 align:start position:0% things in the space the web switches 00:01:02.070 --> 00:01:04.619 align:start position:0% things in the space the web switches were<00:01:03.070> 3GS<00:01:03.489> is<00:01:03.700> basically<00:01:04.059> a<00:01:04.329> library 00:01:04.619 --> 00:01:04.629 align:start position:0% were 3GS is basically a library 00:01:04.629 --> 00:01:06.899 align:start position:0% were 3GS is basically a library JavaScript<00:01:05.619> library<00:01:05.979> which<00:01:06.340> allows<00:01:06.640> you<00:01:06.880> to 00:01:06.899 --> 00:01:06.909 align:start position:0% JavaScript library which allows you to 00:01:06.909 --> 00:01:10.020 align:start position:0% JavaScript library which allows you to interact<00:01:07.569> with<00:01:07.780> your<00:01:08.020> theme<00:01:08.319> node<00:01:09.030> normally 00:01:10.020 --> 00:01:10.030 align:start position:0% interact with your theme node normally 00:01:10.030 --> 00:01:11.730 align:start position:0% interact with your theme node normally as<00:01:10.179> a<00:01:10.210> JavaScript<00:01:10.749> developer<00:01:10.780> you<00:01:11.380> don't<00:01:11.409> want 00:01:11.730 --> 00:01:11.740 align:start position:0% as a JavaScript developer you don't want 00:01:11.740 --> 00:01:15.330 align:start position:0% as a JavaScript developer you don't want to<00:01:11.890> deal<00:01:12.579> with<00:01:12.819> low-level<00:01:13.090> api<00:01:13.899> and<00:01:14.340> decoding 00:01:15.330 --> 00:01:15.340 align:start position:0% to deal with low-level api and decoding 00:01:15.340 --> 00:01:18.629 align:start position:0% to deal with low-level api and decoding encoding<00:01:16.859> you<00:01:17.859> want<00:01:18.069> to<00:01:18.159> basically<00:01:18.429> have<00:01:18.609> a 00:01:18.629 --> 00:01:18.639 align:start position:0% encoding you want to basically have a 00:01:18.639 --> 00:01:20.760 align:start position:0% encoding you want to basically have a nice<00:01:19.060> javascript<00:01:19.719> object<00:01:20.109> which<00:01:20.319> you<00:01:20.350> can 00:01:20.760 --> 00:01:20.770 align:start position:0% nice javascript object which you can 00:01:20.770 --> 00:01:23.609 align:start position:0% nice javascript object which you can interact<00:01:21.340> with<00:01:21.579> and<00:01:22.109> easily<00:01:23.109> write<00:01:23.380> your 00:01:23.609 --> 00:01:23.619 align:start position:0% interact with and easily write your 00:01:23.619 --> 00:01:26.190 align:start position:0% interact with and easily write your applications<00:01:24.310> and<00:01:24.579> web<00:01:25.179> switches<00:01:25.569> is<00:01:25.719> exactly 00:01:26.190 --> 00:01:26.200 align:start position:0% applications and web switches is exactly 00:01:26.200 --> 00:01:30.719 align:start position:0% applications and web switches is exactly this<00:01:26.499> kind<00:01:26.770> of<00:01:26.950> middleware<00:01:28.499> it's<00:01:29.520> widely<00:01:30.520> used 00:01:30.719 --> 00:01:30.729 align:start position:0% this kind of middleware it's widely used 00:01:30.729 --> 00:01:34.849 align:start position:0% this kind of middleware it's widely used and<00:01:31.420> actually<00:01:32.100> the<00:01:33.100> core<00:01:33.399> piece<00:01:33.909> of<00:01:34.149> a<00:01:34.270> lot<00:01:34.450> of 00:01:34.849 --> 00:01:34.859 align:start position:0% and actually the core piece of a lot of 00:01:34.859 --> 00:01:38.629 align:start position:0% and actually the core piece of a lot of different<00:01:35.859> libraries<00:01:36.130> built<00:01:36.639> on<00:01:36.789> top<00:01:36.999> and 00:01:38.629 --> 00:01:38.639 align:start position:0% different libraries built on top and 00:01:38.639 --> 00:01:42.899 align:start position:0% different libraries built on top and working<00:01:39.639> for<00:01:40.240> two<00:01:40.539> years<00:01:40.569> on<00:01:40.869> it<00:01:41.109> and<00:01:41.350> it<00:01:42.280> grew 00:01:42.899 --> 00:01:42.909 align:start position:0% working for two years on it and it grew 00:01:42.909 --> 00:01:47.340 align:start position:0% working for two years on it and it grew over<00:01:42.939> time<00:01:43.539> I<00:01:43.869> found<00:01:44.829> very<00:01:45.399> necessary<00:01:45.850> to<00:01:46.359> do<00:01:47.319> a 00:01:47.340 --> 00:01:47.350 align:start position:0% over time I found very necessary to do a 00:01:47.350 --> 00:01:51.120 align:start position:0% over time I found very necessary to do a overhaul<00:01:48.219> so<00:01:48.819> to<00:01:48.880> say<00:01:49.649> it<00:01:50.649> was<00:01:50.829> initially 00:01:51.120 --> 00:01:51.130 align:start position:0% overhaul so to say it was initially 00:01:51.130 --> 00:01:55.499 align:start position:0% overhaul so to say it was initially created<00:01:51.520> by<00:01:52.029> Jeff<00:01:52.619> Jeffrey<00:01:53.619> Wilker<00:01:54.329> the<00:01:55.329> go 00:01:55.499 --> 00:01:55.509 align:start position:0% created by Jeff Jeffrey Wilker the go 00:01:55.509 --> 00:02:00.649 align:start position:0% created by Jeff Jeffrey Wilker the go aetherium<00:01:56.219> founder<00:01:57.389> core<00:01:58.389> developer<00:01:58.959> and 00:02:00.649 --> 00:02:00.659 align:start position:0% aetherium founder core developer and 00:02:00.659 --> 00:02:04.559 align:start position:0% aetherium founder core developer and mary<00:02:01.659> cutter<00:02:02.020> which<00:02:02.229> are<00:02:02.649> but<00:02:02.920> worked<00:02:03.569> later 00:02:04.559 --> 00:02:04.569 align:start position:0% mary cutter which are but worked later 00:02:04.569 --> 00:02:07.620 align:start position:0% mary cutter which are but worked later on<00:02:04.779> it<00:02:04.959> I<00:02:05.459> joined<00:02:06.459> in<00:02:06.639> 2015 00:02:07.620 --> 00:02:07.630 align:start position:0% on it I joined in 2015 00:02:07.630 --> 00:02:09.690 align:start position:0% on it I joined in 2015 working<00:02:08.470> on<00:02:08.590> it<00:02:08.740> since<00:02:08.950> then<00:02:09.220> and<00:02:09.459> we<00:02:09.550> have 00:02:09.690 --> 00:02:09.700 align:start position:0% working on it since then and we have 00:02:09.700 --> 00:02:12.180 align:start position:0% working on it since then and we have also<00:02:09.880> a<00:02:10.000> lot<00:02:10.060> of<00:02:10.180> contributors<00:02:10.840> and<00:02:11.080> there's<00:02:12.070> a 00:02:12.180 --> 00:02:12.190 align:start position:0% also a lot of contributors and there's a 00:02:12.190 --> 00:02:15.000 align:start position:0% also a lot of contributors and there's a lot<00:02:12.370> more<00:02:12.610> than<00:02:12.820> on<00:02:13.360> this<00:02:13.540> list<00:02:13.780> here 00:02:15.000 --> 00:02:15.010 align:start position:0% lot more than on this list here 00:02:15.010 --> 00:02:18.240 align:start position:0% lot more than on this list here so<00:02:15.340> it<00:02:15.610> started<00:02:16.000> out<00:02:16.180> in<00:02:16.650> 2015 00:02:18.240 --> 00:02:18.250 align:start position:0% so it started out in 2015 00:02:18.250 --> 00:02:22.440 align:start position:0% so it started out in 2015 grew<00:02:19.180> quite<00:02:19.510> a<00:02:19.540> lot<00:02:19.810> and<00:02:20.489> now<00:02:21.489> we<00:02:21.549> structured<00:02:22.360> a 00:02:22.440 --> 00:02:22.450 align:start position:0% grew quite a lot and now we structured a 00:02:22.450 --> 00:02:26.670 align:start position:0% grew quite a lot and now we structured a lot<00:02:22.659> in<00:02:22.870> there<00:02:23.080> 1.0<00:02:23.650> we<00:02:23.890> factor<00:02:24.780> so<00:02:25.780> how 00:02:26.670 --> 00:02:26.680 align:start position:0% lot in there 1.0 we factor so how 00:02:26.680 --> 00:02:29.039 align:start position:0% lot in there 1.0 we factor so how exactly<00:02:26.920> the<00:02:27.400> theorem<00:02:27.909> communication<00:02:28.870> to 00:02:29.039 --> 00:02:29.049 align:start position:0% exactly the theorem communication to 00:02:29.049 --> 00:02:30.570 align:start position:0% exactly the theorem communication to applications<00:02:29.620> work<00:02:29.950> right 00:02:30.570 --> 00:02:30.580 align:start position:0% applications work right 00:02:30.580 --> 00:02:33.570 align:start position:0% applications work right the<00:02:31.209> theorem<00:02:31.510> note<00:02:31.810> itself<00:02:32.319> and<00:02:32.620> the<00:02:33.190> EVM 00:02:33.570 --> 00:02:33.580 align:start position:0% the theorem note itself and the EVM 00:02:33.580 --> 00:02:36.199 align:start position:0% the theorem note itself and the EVM especially<00:02:34.180> only<00:02:34.480> understands<00:02:35.019> bytecode 00:02:36.199 --> 00:02:36.209 align:start position:0% especially only understands bytecode 00:02:36.209 --> 00:02:38.640 align:start position:0% especially only understands bytecode bytecode<00:02:37.209> is<00:02:37.420> not<00:02:37.569> necessarily<00:02:38.080> easy<00:02:38.230> to<00:02:38.379> work 00:02:38.640 --> 00:02:38.650 align:start position:0% bytecode is not necessarily easy to work 00:02:38.650 --> 00:02:42.020 align:start position:0% bytecode is not necessarily easy to work with<00:02:38.709> for<00:02:39.099> most<00:02:39.310> application<00:02:39.910> developers<00:02:40.390> and 00:02:42.020 --> 00:02:42.030 align:start position:0% with for most application developers and 00:02:42.030 --> 00:02:44.550 align:start position:0% with for most application developers and everything<00:02:43.030> which<00:02:43.209> goes<00:02:43.510> into<00:02:43.750> the<00:02:43.959> EVM<00:02:44.290> has 00:02:44.550 --> 00:02:44.560 align:start position:0% everything which goes into the EVM has 00:02:44.560 --> 00:02:46.319 align:start position:0% everything which goes into the EVM has to<00:02:44.739> be<00:02:44.829> first<00:02:45.099> translated<00:02:45.730> to<00:02:46.000> the<00:02:46.120> BET 00:02:46.319 --> 00:02:46.329 align:start position:0% to be first translated to the BET 00:02:46.329 --> 00:02:49.770 align:start position:0% to be first translated to the BET bytecode<00:02:46.840> to<00:02:46.989> be<00:02:47.140> able<00:02:47.590> to<00:02:47.709> be<00:02:47.829> executed<00:02:48.780> so 00:02:49.770 --> 00:02:49.780 align:start position:0% bytecode to be able to be executed so 00:02:49.780 --> 00:02:52.800 align:start position:0% bytecode to be able to be executed so for<00:02:49.959> example<00:02:50.610> this<00:02:51.610> happens<00:02:52.000> over<00:02:52.209> the<00:02:52.450> JSON 00:02:52.800 --> 00:02:52.810 align:start position:0% for example this happens over the JSON 00:02:52.810 --> 00:02:56.270 align:start position:0% for example this happens over the JSON RPC<00:02:53.310> API<00:02:54.310> which<00:02:54.790> is<00:02:54.940> a<00:02:54.970> low-level<00:02:55.329> JSON<00:02:55.959> API 00:02:56.270 --> 00:02:56.280 align:start position:0% RPC API which is a low-level JSON API 00:02:56.280 --> 00:02:58.770 align:start position:0% RPC API which is a low-level JSON API where<00:02:57.280> you<00:02:57.430> have<00:02:57.700> to<00:02:57.910> send<00:02:58.150> all<00:02:58.420> of<00:02:58.599> your 00:02:58.770 --> 00:02:58.780 align:start position:0% where you have to send all of your 00:02:58.780 --> 00:03:01.380 align:start position:0% where you have to send all of your requests<00:02:59.349> and<00:02:59.500> this<00:02:59.980> has<00:03:00.160> to<00:03:00.280> be<00:03:00.310> pre<00:03:00.700> encoded 00:03:01.380 --> 00:03:01.390 align:start position:0% requests and this has to be pre encoded 00:03:01.390 --> 00:03:04.170 align:start position:0% requests and this has to be pre encoded to<00:03:01.840> be<00:03:01.959> understood<00:03:02.379> by<00:03:02.590> the<00:03:02.650> VM<00:03:03.040> and<00:03:03.340> this<00:03:04.030> is 00:03:04.170 --> 00:03:04.180 align:start position:0% to be understood by the VM and this is 00:03:04.180 --> 00:03:08.039 align:start position:0% to be understood by the VM and this is exactly<00:03:04.690> what<00:03:05.500> were<00:03:05.650> three<00:03:05.890> J's<00:03:06.700> does<00:03:07.450> for 00:03:08.039 --> 00:03:08.049 align:start position:0% exactly what were three J's does for 00:03:08.049 --> 00:03:09.690 align:start position:0% exactly what were three J's does for example<00:03:08.379> if<00:03:08.440> you<00:03:08.560> look<00:03:08.739> at<00:03:08.829> this<00:03:08.950> example<00:03:09.280> here 00:03:09.690 --> 00:03:09.700 align:start position:0% example if you look at this example here 00:03:09.700 --> 00:03:12.150 align:start position:0% example if you look at this example here if<00:03:09.940> you<00:03:10.420> want<00:03:10.629> to<00:03:10.810> call<00:03:11.019> a<00:03:11.049> function<00:03:11.680> in<00:03:11.890> the 00:03:12.150 --> 00:03:12.160 align:start position:0% if you want to call a function in the 00:03:12.160 --> 00:03:15.150 align:start position:0% if you want to call a function in the EVM<00:03:13.109> for<00:03:14.109> somebody<00:03:14.379> we<00:03:14.440> want<00:03:14.650> to<00:03:14.739> call<00:03:14.920> the 00:03:15.150 --> 00:03:15.160 align:start position:0% EVM for somebody we want to call the 00:03:15.160 --> 00:03:18.240 align:start position:0% EVM for somebody we want to call the transfer<00:03:15.640> function<00:03:16.120> with<00:03:16.810> two<00:03:17.079> parameters<00:03:17.650> on 00:03:18.240 --> 00:03:18.250 align:start position:0% transfer function with two parameters on 00:03:18.250 --> 00:03:20.460 align:start position:0% transfer function with two parameters on a<00:03:18.310> contract<00:03:19.030> we<00:03:19.540> would<00:03:19.750> have<00:03:19.900> to<00:03:20.109> translate 00:03:20.460 --> 00:03:20.470 align:start position:0% a contract we would have to translate 00:03:20.470 --> 00:03:24.870 align:start position:0% a contract we would have to translate this<00:03:21.810> by<00:03:23.310> hashing<00:03:24.310> do<00:03:24.519> you<00:03:24.609> function 00:03:24.870 --> 00:03:24.880 align:start position:0% this by hashing do you function 00:03:24.880 --> 00:03:28.080 align:start position:0% this by hashing do you function including<00:03:25.720> its<00:03:25.870> parameter<00:03:26.319> types<00:03:26.799> and<00:03:27.250> then 00:03:28.080 --> 00:03:28.090 align:start position:0% including its parameter types and then 00:03:28.090 --> 00:03:30.599 align:start position:0% including its parameter types and then taking<00:03:28.540> the<00:03:28.959> first<00:03:29.260> four<00:03:29.590> bytes<00:03:29.769> of<00:03:30.069> that<00:03:30.340> as 00:03:30.599 --> 00:03:30.609 align:start position:0% taking the first four bytes of that as 00:03:30.609 --> 00:03:33.509 align:start position:0% taking the first four bytes of that as the<00:03:31.180> function<00:03:31.750> name<00:03:31.959> and<00:03:32.230> then<00:03:32.829> appending<00:03:33.400> the 00:03:33.509 --> 00:03:33.519 align:start position:0% the function name and then appending the 00:03:33.519 --> 00:03:38.069 align:start position:0% the function name and then appending the other<00:03:33.639> parameters<00:03:34.239> after<00:03:34.690> that<00:03:36.660> once<00:03:37.660> which<00:03:37.840> s 00:03:38.069 --> 00:03:38.079 align:start position:0% other parameters after that once which s 00:03:38.079 --> 00:03:40.470 align:start position:0% other parameters after that once which s is<00:03:38.349> exactly<00:03:39.099> like<00:03:39.340> taking<00:03:39.760> care<00:03:39.940> of<00:03:40.000> that<00:03:40.269> so 00:03:40.470 --> 00:03:40.480 align:start position:0% is exactly like taking care of that so 00:03:40.480 --> 00:03:41.909 align:start position:0% is exactly like taking care of that so you<00:03:40.569> don't<00:03:40.690> have<00:03:40.840> to<00:03:41.019> do<00:03:41.139> it<00:03:41.169> and<00:03:41.530> you<00:03:41.769> can 00:03:41.909 --> 00:03:41.919 align:start position:0% you don't have to do it and you can 00:03:41.919 --> 00:03:43.949 align:start position:0% you don't have to do it and you can easily<00:03:42.130> community<00:03:42.880> work<00:03:43.209> with<00:03:43.389> JavaScript 00:03:43.949 --> 00:03:43.959 align:start position:0% easily community work with JavaScript 00:03:43.959 --> 00:03:48.120 align:start position:0% easily community work with JavaScript objects<00:03:44.530> and<00:03:44.880> the<00:03:45.880> 1.0<00:03:46.720> refactor<00:03:47.470> is<00:03:47.739> actually 00:03:48.120 --> 00:03:48.130 align:start position:0% objects and the 1.0 refactor is actually 00:03:48.130 --> 00:03:51.690 align:start position:0% objects and the 1.0 refactor is actually a<00:03:48.190> major<00:03:48.609> overhaul<00:03:49.709> to<00:03:50.709> make<00:03:51.069> that<00:03:51.280> even<00:03:51.579> more 00:03:51.690 --> 00:03:51.700 align:start position:0% a major overhaul to make that even more 00:03:51.700 --> 00:03:53.640 align:start position:0% a major overhaul to make that even more convenient<00:03:52.030> and<00:03:52.359> even<00:03:52.630> more<00:03:52.840> intuitive<00:03:53.410> and 00:03:53.640 --> 00:03:53.650 align:start position:0% convenient and even more intuitive and 00:03:53.650 --> 00:03:56.159 align:start position:0% convenient and even more intuitive and give<00:03:54.400> you<00:03:54.519> a<00:03:54.549> lot<00:03:54.940> more<00:03:55.150> features<00:03:55.569> and<00:03:55.780> tools 00:03:56.159 --> 00:03:56.169 align:start position:0% give you a lot more features and tools 00:03:56.169 --> 00:03:58.589 align:start position:0% give you a lot more features and tools so<00:03:56.380> that<00:03:56.410> you<00:03:56.590> can<00:03:56.889> care<00:03:57.849> building<00:03:58.299> about<00:03:58.480> your 00:03:58.589 --> 00:03:58.599 align:start position:0% so that you can care building about your 00:03:58.599 --> 00:04:01.250 align:start position:0% so that you can care building about your application<00:03:58.690> rather<00:03:59.470> than<00:03:59.799> thinking<00:04:00.250> about 00:04:01.250 --> 00:04:01.260 align:start position:0% application rather than thinking about 00:04:01.260 --> 00:04:05.369 align:start position:0% application rather than thinking about how<00:04:02.260> to<00:04:02.319> encode<00:04:02.859> what<00:04:03.190> and<00:04:03.430> what<00:04:03.609> kind<00:04:03.879> of<00:04:04.379> how 00:04:05.369 --> 00:04:05.379 align:start position:0% how to encode what and what kind of how 00:04:05.379 --> 00:04:07.680 align:start position:0% how to encode what and what kind of how to<00:04:05.410> watch<00:04:05.769> for<00:04:06.129> your<00:04:06.389> transactions<00:04:07.389> and 00:04:07.680 --> 00:04:07.690 align:start position:0% to watch for your transactions and 00:04:07.690 --> 00:04:09.259 align:start position:0% to watch for your transactions and building<00:04:07.989> all<00:04:08.079> of<00:04:08.230> that<00:04:08.349> logic<00:04:08.500> for<00:04:08.829> yourself 00:04:09.259 --> 00:04:09.269 align:start position:0% building all of that logic for yourself 00:04:09.269 --> 00:04:13.710 align:start position:0% building all of that logic for yourself so<00:04:10.269> I<00:04:10.660> hope<00:04:11.079> that<00:04:11.669> 1.0<00:04:12.669> fulfills<00:04:13.120> all<00:04:13.359> of<00:04:13.419> that 00:04:13.710 --> 00:04:13.720 align:start position:0% so I hope that 1.0 fulfills all of that 00:04:13.720 --> 00:04:16.439 align:start position:0% so I hope that 1.0 fulfills all of that needs<00:04:13.989> and<00:04:14.349> is<00:04:14.500> kind<00:04:14.799> of<00:04:14.919> the<00:04:15.190> that<00:04:15.940> developers 00:04:16.439 --> 00:04:16.449 align:start position:0% needs and is kind of the that developers 00:04:16.449 --> 00:04:20.779 align:start position:0% needs and is kind of the that developers best<00:04:16.690> friend 00:04:20.779 --> 00:04:20.789 align:start position:0% 00:04:20.789 --> 00:04:24.540 align:start position:0% so<00:04:21.789> the<00:04:22.300> 1.0<00:04:22.870> refactor<00:04:23.469> is<00:04:23.590> a<00:04:23.620> major<00:04:23.919> refactor 00:04:24.540 --> 00:04:24.550 align:start position:0% so the 1.0 refactor is a major refactor 00:04:24.550 --> 00:04:26.399 align:start position:0% so the 1.0 refactor is a major refactor in<00:04:24.610> the<00:04:24.729> sense<00:04:24.940> that<00:04:25.060> i<00:04:25.330> restructured<00:04:26.110> a<00:04:26.229> lot 00:04:26.399 --> 00:04:26.409 align:start position:0% in the sense that i restructured a lot 00:04:26.409 --> 00:04:27.510 align:start position:0% in the sense that i restructured a lot of<00:04:26.620> the 00:04:27.510 --> 00:04:27.520 align:start position:0% of the 00:04:27.520 --> 00:04:30.540 align:start position:0% of the tools<00:04:28.020> everything<00:04:29.020> before<00:04:29.560> was<00:04:29.770> on<00:04:30.039> the<00:04:30.340> major 00:04:30.540 --> 00:04:30.550 align:start position:0% tools everything before was on the major 00:04:30.550 --> 00:04:33.059 align:start position:0% tools everything before was on the major object<00:04:31.180> kind<00:04:31.810> of<00:04:31.960> like<00:04:32.139> this<00:04:32.289> burst<00:04:32.620> this<00:04:32.830> way 00:04:33.059 --> 00:04:33.069 align:start position:0% object kind of like this burst this way 00:04:33.069 --> 00:04:35.640 align:start position:0% object kind of like this burst this way and<00:04:33.340> now<00:04:33.849> we<00:04:33.910> restructured<00:04:34.630> it<00:04:34.750> in<00:04:34.900> proper 00:04:35.640 --> 00:04:35.650 align:start position:0% and now we restructured it in proper 00:04:35.650 --> 00:04:38.309 align:start position:0% and now we restructured it in proper elements<00:04:36.539> utility<00:04:37.539> functions<00:04:37.990> are<00:04:38.169> for 00:04:38.309 --> 00:04:38.319 align:start position:0% elements utility functions are for 00:04:38.319 --> 00:04:40.050 align:start position:0% elements utility functions are for example<00:04:38.680> under<00:04:38.860> the<00:04:39.009> utility<00:04:39.430> objects<00:04:39.910> and 00:04:40.050 --> 00:04:40.060 align:start position:0% example under the utility objects and 00:04:40.060 --> 00:04:42.210 align:start position:0% example under the utility objects and all<00:04:40.479> of<00:04:40.660> these<00:04:40.810> packages<00:04:41.169> are<00:04:41.470> also<00:04:41.710> separate 00:04:42.210 --> 00:04:42.220 align:start position:0% all of these packages are also separate 00:04:42.220 --> 00:04:44.730 align:start position:0% all of these packages are also separate packages<00:04:42.759> so<00:04:43.180> you<00:04:43.240> can<00:04:43.509> load<00:04:44.020> either<00:04:44.319> the<00:04:44.560> ones 00:04:44.730 --> 00:04:44.740 align:start position:0% packages so you can load either the ones 00:04:44.740 --> 00:04:46.650 align:start position:0% packages so you can load either the ones you<00:04:44.889> need<00:04:45.099> or<00:04:45.400> you<00:04:45.610> can<00:04:46.000> load<00:04:46.180> it<00:04:46.330> all<00:04:46.449> together 00:04:46.650 --> 00:04:46.660 align:start position:0% you need or you can load it all together 00:04:46.660 --> 00:04:50.820 align:start position:0% you need or you can load it all together in<00:04:46.990> the<00:04:47.169> umbrella<00:04:47.470> package<00:04:49.020> so<00:04:50.020> I<00:04:50.050> will<00:04:50.410> now<00:04:50.590> go 00:04:50.820 --> 00:04:50.830 align:start position:0% in the umbrella package so I will now go 00:04:50.830 --> 00:04:53.400 align:start position:0% in the umbrella package so I will now go through<00:04:51.130> all<00:04:51.490> of<00:04:51.550> these<00:04:52.060> package<00:04:53.050> separately 00:04:53.400 --> 00:04:53.410 align:start position:0% through all of these package separately 00:04:53.410 --> 00:04:55.350 align:start position:0% through all of these package separately and<00:04:53.860> show<00:04:54.009> a<00:04:54.039> little<00:04:54.220> bit<00:04:54.430> of<00:04:54.550> what<00:04:54.729> I<00:04:54.759> have<00:04:55.060> and 00:04:55.350 --> 00:04:55.360 align:start position:0% and show a little bit of what I have and 00:04:55.360 --> 00:04:58.050 align:start position:0% and show a little bit of what I have and what<00:04:55.419> new<00:04:56.050> features<00:04:56.530> they<00:04:56.860> have<00:04:57.060> one 00:04:58.050 --> 00:04:58.060 align:start position:0% what new features they have one 00:04:58.060 --> 00:05:03.029 align:start position:0% what new features they have one obviously<00:04:58.509> very<00:04:58.810> important<00:04:59.970> piece<00:05:01.169> in<00:05:02.169> this 00:05:03.029 --> 00:05:03.039 align:start position:0% obviously very important piece in this 00:05:03.039 --> 00:05:07.020 align:start position:0% obviously very important piece in this is<00:05:03.780> that<00:05:04.780> we<00:05:04.930> now<00:05:05.080> have<00:05:05.110> promises<00:05:06.030> something 00:05:07.020 --> 00:05:07.030 align:start position:0% is that we now have promises something 00:05:07.030 --> 00:05:14.610 align:start position:0% is that we now have promises something which<00:05:07.210> was<00:05:12.840> something<00:05:13.840> which<00:05:13.960> probably<00:05:14.139> took 00:05:14.610 --> 00:05:14.620 align:start position:0% which was something which probably took 00:05:14.620 --> 00:05:18.779 align:start position:0% which was something which probably took way<00:05:14.830> too<00:05:14.860> long<00:05:16.500> this<00:05:17.500> is<00:05:17.680> all<00:05:17.860> due<00:05:18.400> to<00:05:18.550> the<00:05:18.669> way 00:05:18.779 --> 00:05:18.789 align:start position:0% way too long this is all due to the way 00:05:18.789 --> 00:05:20.760 align:start position:0% way too long this is all due to the way how<00:05:19.030> it<00:05:19.210> COO<00:05:19.479> over<00:05:19.840> time<00:05:20.110> and<00:05:20.349> we<00:05:20.440> all<00:05:20.560> had<00:05:20.740> to 00:05:20.760 --> 00:05:20.770 align:start position:0% how it COO over time and we all had to 00:05:20.770 --> 00:05:22.469 align:start position:0% how it COO over time and we all had to figure<00:05:21.190> out<00:05:21.340> what<00:05:21.580> works<00:05:21.819> and<00:05:21.970> what<00:05:22.090> doesn't 00:05:22.469 --> 00:05:22.479 align:start position:0% figure out what works and what doesn't 00:05:22.479 --> 00:05:25.710 align:start position:0% figure out what works and what doesn't work<00:05:23.280> initially<00:05:24.280> think<00:05:24.669> thinking<00:05:25.240> also<00:05:25.419> that 00:05:25.710 --> 00:05:25.720 align:start position:0% work initially think thinking also that 00:05:25.720 --> 00:05:27.839 align:start position:0% work initially think thinking also that the<00:05:25.960> connection<00:05:26.770> to<00:05:26.860> node<00:05:27.039> will<00:05:27.280> be<00:05:27.310> way<00:05:27.550> fast 00:05:27.839 --> 00:05:27.849 align:start position:0% the connection to node will be way fast 00:05:27.849 --> 00:05:29.550 align:start position:0% the connection to node will be way fast and<00:05:28.180> way<00:05:28.419> more<00:05:28.449> smoothly<00:05:28.990> than<00:05:29.169> it<00:05:29.409> actually 00:05:29.550 --> 00:05:29.560 align:start position:0% and way more smoothly than it actually 00:05:29.560 --> 00:05:30.330 align:start position:0% and way more smoothly than it actually is 00:05:30.330 --> 00:05:30.340 align:start position:0% is 00:05:30.340 --> 00:05:33.510 align:start position:0% is with<00:05:30.639> like<00:05:30.940> large<00:05:31.530> network<00:05:32.530> which<00:05:33.190> we<00:05:33.310> crew 00:05:33.510 --> 00:05:33.520 align:start position:0% with like large network which we crew 00:05:33.520 --> 00:05:37.050 align:start position:0% with like large network which we crew today<00:05:33.759> to<00:05:35.219> basically<00:05:36.219> promises<00:05:36.789> allow<00:05:37.000> you 00:05:37.050 --> 00:05:37.060 align:start position:0% today to basically promises allow you 00:05:37.060 --> 00:05:40.350 align:start position:0% today to basically promises allow you simply<00:05:37.539> to<00:05:37.949> chain<00:05:38.949> your<00:05:39.430> functions<00:05:40.000> which 00:05:40.350 --> 00:05:40.360 align:start position:0% simply to chain your functions which 00:05:40.360 --> 00:05:41.790 align:start position:0% simply to chain your functions which makes<00:05:40.599> them<00:05:40.719> more<00:05:40.840> convenient<00:05:41.169> and<00:05:41.469> more<00:05:41.530> easy 00:05:41.790 --> 00:05:41.800 align:start position:0% makes them more convenient and more easy 00:05:41.800 --> 00:05:44.670 align:start position:0% makes them more convenient and more easy to<00:05:42.039> use<00:05:42.550> and<00:05:42.820> to<00:05:42.940> see<00:05:43.120> but<00:05:43.930> we<00:05:44.050> have<00:05:44.229> a<00:05:44.259> special 00:05:44.670 --> 00:05:44.680 align:start position:0% to use and to see but we have a special 00:05:44.680 --> 00:05:46.890 align:start position:0% to use and to see but we have a special case<00:05:44.889> in<00:05:45.070> web<00:05:45.190> switches<00:05:45.669> and<00:05:46.330> especially<00:05:46.690> with 00:05:46.890 --> 00:05:46.900 align:start position:0% case in web switches and especially with 00:05:46.900 --> 00:05:50.189 align:start position:0% case in web switches and especially with block<00:05:47.110> chains<00:05:47.409> we<00:05:47.979> have<00:05:48.159> the<00:05:48.340> case<00:05:48.580> that<00:05:49.199> you 00:05:50.189 --> 00:05:50.199 align:start position:0% block chains we have the case that you 00:05:50.199 --> 00:05:51.779 align:start position:0% block chains we have the case that you have<00:05:50.440> an<00:05:50.620> event<00:05:50.919> which<00:05:51.099> is<00:05:51.250> not<00:05:51.400> necessarily 00:05:51.779 --> 00:05:51.789 align:start position:0% have an event which is not necessarily 00:05:51.789 --> 00:05:54.180 align:start position:0% have an event which is not necessarily final<00:05:52.419> so<00:05:52.750> it<00:05:52.870> cannot<00:05:53.139> really<00:05:53.349> come<00:05:53.710> with<00:05:53.979> one 00:05:54.180 --> 00:05:54.190 align:start position:0% final so it cannot really come with one 00:05:54.190 --> 00:05:56.760 align:start position:0% final so it cannot really come with one result<00:05:54.580> only<00:05:55.000> especially<00:05:55.990> when<00:05:56.349> you<00:05:56.469> send<00:05:56.680> the 00:05:56.760 --> 00:05:56.770 align:start position:0% result only especially when you send the 00:05:56.770 --> 00:05:58.230 align:start position:0% result only especially when you send the transactions<00:05:57.340> there's<00:05:57.819> the<00:05:57.969> possibility 00:05:58.230 --> 00:05:58.240 align:start position:0% transactions there's the possibility 00:05:58.240 --> 00:06:01.860 align:start position:0% transactions there's the possibility that<00:05:58.690> you<00:05:58.870> can<00:05:59.909> you<00:06:00.909> get<00:06:01.090> a<00:06:01.120> transaction<00:06:01.690> hash 00:06:01.860 --> 00:06:01.870 align:start position:0% that you can you get a transaction hash 00:06:01.870 --> 00:06:04.200 align:start position:0% that you can you get a transaction hash but<00:06:02.409> you're<00:06:02.530> also<00:06:02.740> able<00:06:03.280> to<00:06:03.580> get<00:06:03.759> the<00:06:03.880> receipt 00:06:04.200 --> 00:06:04.210 align:start position:0% but you're also able to get the receipt 00:06:04.210 --> 00:06:06.089 align:start position:0% but you're also able to get the receipt and<00:06:04.509> there's<00:06:04.900> also<00:06:05.080> a<00:06:05.259> lot<00:06:05.440> of<00:06:05.469> other<00:06:05.710> things 00:06:06.089 --> 00:06:06.099 align:start position:0% and there's also a lot of other things 00:06:06.099 --> 00:06:07.439 align:start position:0% and there's also a lot of other things you<00:06:06.190> have<00:06:06.280> to<00:06:06.370> take<00:06:06.520> care<00:06:06.729> of<00:06:06.880> for<00:06:06.969> example<00:06:07.090> to 00:06:07.439 --> 00:06:07.449 align:start position:0% you have to take care of for example to 00:06:07.449 --> 00:06:10.050 align:start position:0% you have to take care of for example to change<00:06:07.719> and<00:06:07.930> reorganize<00:06:08.520> for<00:06:09.520> certain<00:06:09.849> amount 00:06:10.050 --> 00:06:10.060 align:start position:0% change and reorganize for certain amount 00:06:10.060 --> 00:06:13.080 align:start position:0% change and reorganize for certain amount of<00:06:10.180> blocks<00:06:10.419> with<00:06:10.840> a<00:06:10.900> likelihood<00:06:11.759> so<00:06:12.759> you<00:06:12.849> have 00:06:13.080 --> 00:06:13.090 align:start position:0% of blocks with a likelihood so you have 00:06:13.090 --> 00:06:14.309 align:start position:0% of blocks with a likelihood so you have to<00:06:13.240> take<00:06:13.449> care<00:06:13.630> of<00:06:13.659> all<00:06:13.840> of<00:06:13.990> these<00:06:14.139> things 00:06:14.309 --> 00:06:14.319 align:start position:0% to take care of all of these things 00:06:14.319 --> 00:06:16.800 align:start position:0% to take care of all of these things yourself<00:06:14.789> so<00:06:15.789> when<00:06:16.180> you<00:06:16.270> just<00:06:16.509> use<00:06:16.659> the 00:06:16.800 --> 00:06:16.810 align:start position:0% yourself so when you just use the 00:06:16.810 --> 00:06:18.600 align:start position:0% yourself so when you just use the promise<00:06:17.199> for<00:06:17.409> example<00:06:17.800> you<00:06:17.919> get<00:06:18.069> the<00:06:18.219> received 00:06:18.600 --> 00:06:18.610 align:start position:0% promise for example you get the received 00:06:18.610 --> 00:06:20.909 align:start position:0% promise for example you get the received which<00:06:19.150> is<00:06:19.300> what<00:06:19.449> most<00:06:19.599> developers<00:06:20.440> want<00:06:20.710> they 00:06:20.909 --> 00:06:20.919 align:start position:0% which is what most developers want they 00:06:20.919 --> 00:06:22.709 align:start position:0% which is what most developers want they won't<00:06:21.069> simply<00:06:21.789> send<00:06:22.030> the<00:06:22.120> transaction<00:06:22.300> and 00:06:22.709 --> 00:06:22.719 align:start position:0% won't simply send the transaction and 00:06:22.719 --> 00:06:25.469 align:start position:0% won't simply send the transaction and act<00:06:22.930> once<00:06:23.229> their<00:06:23.440> mind<00:06:24.030> but<00:06:25.030> in<00:06:25.180> most<00:06:25.330> cases 00:06:25.469 --> 00:06:25.479 align:start position:0% act once their mind but in most cases 00:06:25.479 --> 00:06:27.749 align:start position:0% act once their mind but in most cases you<00:06:25.810> actually<00:06:25.930> want<00:06:26.409> to<00:06:26.500> have<00:06:26.710> more<00:06:27.219> complex 00:06:27.749 --> 00:06:27.759 align:start position:0% you actually want to have more complex 00:06:27.759 --> 00:06:29.909 align:start position:0% you actually want to have more complex and<00:06:28.000> more<00:06:28.120> detailed<00:06:28.569> response<00:06:28.810> to<00:06:29.380> you<00:06:29.469> up<00:06:29.590> to 00:06:29.909 --> 00:06:29.919 align:start position:0% and more detailed response to you up to 00:06:29.919 --> 00:06:32.339 align:start position:0% and more detailed response to you up to your<00:06:30.190> transactions<00:06:30.759> maybe<00:06:31.750> you<00:06:31.900> want<00:06:32.080> to<00:06:32.139> wait 00:06:32.339 --> 00:06:32.349 align:start position:0% your transactions maybe you want to wait 00:06:32.349 --> 00:06:34.740 align:start position:0% your transactions maybe you want to wait for<00:06:32.590> five<00:06:32.800> confirmations<00:06:33.520> or<00:06:33.759> maybe<00:06:34.389> you<00:06:34.539> want 00:06:34.740 --> 00:06:34.750 align:start position:0% for five confirmations or maybe you want 00:06:34.750 --> 00:06:36.089 align:start position:0% for five confirmations or maybe you want to<00:06:34.870> actually<00:06:35.050> do<00:06:35.529> something<00:06:35.770> with<00:06:35.889> the 00:06:36.089 --> 00:06:36.099 align:start position:0% to actually do something with the 00:06:36.099 --> 00:06:39.510 align:start position:0% to actually do something with the transaction<00:06:36.430> hash<00:06:36.789> directly<00:06:37.389> so<00:06:38.139> this<00:06:38.919> prom 00:06:39.510 --> 00:06:39.520 align:start position:0% transaction hash directly so this prom 00:06:39.520 --> 00:06:41.460 align:start position:0% transaction hash directly so this prom event<00:06:39.880> construct<00:06:40.539> basically<00:06:40.990> allows 00:06:41.460 --> 00:06:41.470 align:start position:0% event construct basically allows 00:06:41.470 --> 00:06:45.450 align:start position:0% event construct basically allows to<00:06:43.020> get<00:06:44.020> all<00:06:44.260> of<00:06:44.410> these<00:06:44.560> different<00:06:44.800> types<00:06:45.280> you 00:06:45.450 --> 00:06:45.460 align:start position:0% to get all of these different types you 00:06:45.460 --> 00:06:48.150 align:start position:0% to get all of these different types you can<00:06:45.640> get<00:06:45.880> back<00:06:46.060> from<00:06:46.270> one<00:06:46.480> transaction<00:06:46.840> and<00:06:47.350> do 00:06:48.150 --> 00:06:48.160 align:start position:0% can get back from one transaction and do 00:06:48.160 --> 00:06:49.560 align:start position:0% can get back from one transaction and do something<00:06:48.610> related<00:06:49.030> to<00:06:49.060> it 00:06:49.560 --> 00:06:49.570 align:start position:0% something related to it 00:06:49.570 --> 00:06:52.470 align:start position:0% something related to it so<00:06:49.870> it<00:06:50.050> can<00:06:50.320> be<00:06:50.440> a<00:06:50.640> promise<00:06:51.640> but<00:06:51.850> it<00:06:51.970> can<00:06:52.300> also 00:06:52.470 --> 00:06:52.480 align:start position:0% so it can be a promise but it can also 00:06:52.480 --> 00:06:55.680 align:start position:0% so it can be a promise but it can also be<00:06:52.630> an<00:06:52.750> event<00:06:53.460> where<00:06:54.460> you<00:06:54.580> can<00:06:54.610> wait<00:06:55.390> for<00:06:55.660> a 00:06:55.680 --> 00:06:55.690 align:start position:0% be an event where you can wait for a 00:06:55.690 --> 00:06:56.910 align:start position:0% be an event where you can wait for a transaction<00:06:55.960> has<00:06:56.200> to<00:06:56.260> receive<00:06:56.590> confirmation 00:06:56.910 --> 00:06:56.920 align:start position:0% transaction has to receive confirmation 00:06:56.920 --> 00:06:58.860 align:start position:0% transaction has to receive confirmation and<00:06:57.550> we<00:06:57.640> can<00:06:57.790> even<00:06:57.970> add<00:06:58.180> a<00:06:58.210> lot<00:06:58.450> more<00:06:58.690> in<00:06:58.780> the 00:06:58.860 --> 00:06:58.870 align:start position:0% and we can even add a lot more in the 00:06:58.870 --> 00:07:03.780 align:start position:0% and we can even add a lot more in the future<00:07:01.260> web<00:07:02.260> switches<00:07:02.620> 1.0<00:07:03.220> has<00:07:03.550> a 00:07:03.780 --> 00:07:03.790 align:start position:0% future web switches 1.0 has a 00:07:03.790 --> 00:07:05.280 align:start position:0% future web switches 1.0 has a subscription<00:07:04.090> and<00:07:04.540> this<00:07:04.720> is<00:07:04.840> something<00:07:05.050> I 00:07:05.280 --> 00:07:05.290 align:start position:0% subscription and this is something I 00:07:05.290 --> 00:07:07.770 align:start position:0% subscription and this is something I worked<00:07:05.560> on<00:07:05.800> quite<00:07:06.130> long<00:07:06.250> and<00:07:06.820> it<00:07:07.180> always<00:07:07.420> takes 00:07:07.770 --> 00:07:07.780 align:start position:0% worked on quite long and it always takes 00:07:07.780 --> 00:07:09.570 align:start position:0% worked on quite long and it always takes a<00:07:07.900> bit<00:07:08.050> of<00:07:08.080> time<00:07:08.440> to<00:07:08.590> convince<00:07:08.830> many<00:07:09.070> parties 00:07:09.570 --> 00:07:09.580 align:start position:0% a bit of time to convince many parties 00:07:09.580 --> 00:07:12.180 align:start position:0% a bit of time to convince many parties to<00:07:09.790> do<00:07:10.030> something<00:07:10.480> and<00:07:11.230> you<00:07:11.470> are<00:07:11.620> different<00:07:11.830> or 00:07:12.180 --> 00:07:12.190 align:start position:0% to do something and you are different or 00:07:12.190 --> 00:07:15.530 align:start position:0% to do something and you are different or a<00:07:12.220> certain<00:07:12.520> way<00:07:12.670> and<00:07:14.280> subscriptions<00:07:15.280> are 00:07:15.530 --> 00:07:15.540 align:start position:0% a certain way and subscriptions are 00:07:15.540 --> 00:07:17.910 align:start position:0% a certain way and subscriptions are important<00:07:16.540> because<00:07:16.690> we<00:07:17.380> have<00:07:17.620> a<00:07:17.650> lot<00:07:17.890> of 00:07:17.910 --> 00:07:17.920 align:start position:0% important because we have a lot of 00:07:17.920 --> 00:07:20.640 align:start position:0% important because we have a lot of events<00:07:18.220> coming<00:07:18.640> from<00:07:18.880> the<00:07:19.060> node<00:07:19.240> and<00:07:19.510> the<00:07:20.410> old 00:07:20.640 --> 00:07:20.650 align:start position:0% events coming from the node and the old 00:07:20.650 --> 00:07:22.410 align:start position:0% events coming from the node and the old way<00:07:20.950> of<00:07:21.130> doing<00:07:21.460> that<00:07:21.610> is<00:07:21.670> that<00:07:21.850> your 00:07:22.410 --> 00:07:22.420 align:start position:0% way of doing that is that your 00:07:22.420 --> 00:07:25.140 align:start position:0% way of doing that is that your application<00:07:23.020> is<00:07:23.080> polling<00:07:23.560> that<00:07:24.490> node<00:07:24.760> that 00:07:25.140 --> 00:07:25.150 align:start position:0% application is polling that node that 00:07:25.150 --> 00:07:27.510 align:start position:0% application is polling that node that works<00:07:26.050> quite<00:07:26.320> fairly<00:07:26.710> well<00:07:27.010> if<00:07:27.190> you<00:07:27.280> have<00:07:27.370> one 00:07:27.510 --> 00:07:27.520 align:start position:0% works quite fairly well if you have one 00:07:27.520 --> 00:07:29.190 align:start position:0% works quite fairly well if you have one application<00:07:28.180> and<00:07:28.330> you<00:07:28.480> bought<00:07:28.720> for<00:07:28.930> a<00:07:28.960> few 00:07:29.190 --> 00:07:29.200 align:start position:0% application and you bought for a few 00:07:29.200 --> 00:07:31.500 align:start position:0% application and you bought for a few events<00:07:29.440> but<00:07:30.400> it<00:07:30.550> doesn't<00:07:30.850> really<00:07:31.000> work<00:07:31.240> well 00:07:31.500 --> 00:07:31.510 align:start position:0% events but it doesn't really work well 00:07:31.510 --> 00:07:33.720 align:start position:0% events but it doesn't really work well if<00:07:31.750> you<00:07:31.870> have<00:07:32.080> many<00:07:32.470> applications<00:07:32.710> polling<00:07:33.610> on 00:07:33.720 --> 00:07:33.730 align:start position:0% if you have many applications polling on 00:07:33.730 --> 00:07:39.540 align:start position:0% if you have many applications polling on the<00:07:33.820> same<00:07:34.030> node<00:07:35.220> so<00:07:37.950> subscription<00:07:38.950> basically 00:07:39.540 --> 00:07:39.550 align:start position:0% the same node so subscription basically 00:07:39.550 --> 00:07:41.990 align:start position:0% the same node so subscription basically allows<00:07:39.790> you<00:07:40.000> exactly<00:07:40.420> this<00:07:40.540> pops<00:07:40.930> up<00:07:41.200> model 00:07:41.990 --> 00:07:42.000 align:start position:0% allows you exactly this pops up model 00:07:42.000 --> 00:07:47.010 align:start position:0% allows you exactly this pops up model where<00:07:43.000> you<00:07:43.180> can<00:07:44.820> wait<00:07:45.820> for<00:07:46.180> events<00:07:46.570> and<00:07:46.750> you 00:07:47.010 --> 00:07:47.020 align:start position:0% where you can wait for events and you 00:07:47.020 --> 00:07:49.080 align:start position:0% where you can wait for events and you have<00:07:47.169> to<00:07:47.290> do<00:07:47.410> nothing<00:07:47.800> best<00:07:48.370> but<00:07:48.669> waiting 00:07:49.080 --> 00:07:49.090 align:start position:0% have to do nothing best but waiting 00:07:49.090 --> 00:07:51.960 align:start position:0% have to do nothing best but waiting until<00:07:49.450> it<00:07:49.570> happens<00:07:50.040> this<00:07:51.040> which<00:07:51.400> uses<00:07:51.700> a<00:07:51.790> lot 00:07:51.960 --> 00:07:51.970 align:start position:0% until it happens this which uses a lot 00:07:51.970 --> 00:07:53.310 align:start position:0% until it happens this which uses a lot of<00:07:52.000> the<00:07:52.120> resource<00:07:52.480> load<00:07:52.750> you<00:07:52.930> have<00:07:53.110> in<00:07:53.230> the 00:07:53.310 --> 00:07:53.320 align:start position:0% of the resource load you have in the 00:07:53.320 --> 00:07:56.520 align:start position:0% of the resource load you have in the node<00:07:53.530> and<00:07:53.770> this<00:07:53.890> also<00:07:54.750> improves<00:07:55.750> the 00:07:56.520 --> 00:07:56.530 align:start position:0% node and this also improves the 00:07:56.530 --> 00:07:58.140 align:start position:0% node and this also improves the processing<00:07:57.130> you<00:07:57.250> need<00:07:57.280> to<00:07:57.520> do<00:07:57.640> on<00:07:57.820> your<00:07:57.850> node 00:07:58.140 --> 00:07:58.150 align:start position:0% processing you need to do on your node 00:07:58.150 --> 00:08:01.890 align:start position:0% processing you need to do on your node itself<00:07:58.510> on<00:07:59.500> your<00:07:59.680> application<00:08:00.220> itself<00:08:00.490> so<00:08:01.300> IPC 00:08:01.890 --> 00:08:01.900 align:start position:0% itself on your application itself so IPC 00:08:01.900 --> 00:08:04.080 align:start position:0% itself on your application itself so IPC sockets<00:08:02.350> is<00:08:02.620> basically<00:08:03.190> the<00:08:03.400> local<00:08:03.760> socket 00:08:04.080 --> 00:08:04.090 align:start position:0% sockets is basically the local socket 00:08:04.090 --> 00:08:05.850 align:start position:0% sockets is basically the local socket you<00:08:04.240> have<00:08:04.450> when<00:08:04.690> you<00:08:04.810> notice<00:08:05.020> running<00:08:05.440> locally 00:08:05.850 --> 00:08:05.860 align:start position:0% you have when you notice running locally 00:08:05.860 --> 00:08:08.280 align:start position:0% you have when you notice running locally and<00:08:06.040> web<00:08:06.820> socket<00:08:07.210> is<00:08:07.360> when<00:08:07.540> you<00:08:07.660> would<00:08:07.780> you 00:08:08.280 --> 00:08:08.290 align:start position:0% and web socket is when you would you 00:08:08.290 --> 00:08:11.580 align:start position:0% and web socket is when you would you talk<00:08:08.560> to<00:08:08.710> a<00:08:08.740> remote<00:08:09.130> node<00:08:09.660> the<00:08:10.660> HTTP<00:08:11.230> still 00:08:11.580 --> 00:08:11.590 align:start position:0% talk to a remote node the HTTP still 00:08:11.590 --> 00:08:14.520 align:start position:0% talk to a remote node the HTTP still works<00:08:11.980> as<00:08:12.310> well<00:08:12.490> but<00:08:12.850> for<00:08:13.780> subscriptions<00:08:14.410> it 00:08:14.520 --> 00:08:14.530 align:start position:0% works as well but for subscriptions it 00:08:14.530 --> 00:08:17.540 align:start position:0% works as well but for subscriptions it can't<00:08:14.770> work<00:08:15.300> there<00:08:16.300> we<00:08:16.480> are<00:08:16.600> thinking<00:08:16.900> about 00:08:17.540 --> 00:08:17.550 align:start position:0% can't work there we are thinking about 00:08:17.550 --> 00:08:20.360 align:start position:0% can't work there we are thinking about using<00:08:18.550> also<00:08:19.210> some<00:08:19.390> kind<00:08:19.570> of<00:08:19.660> polling<00:08:19.990> again 00:08:20.360 --> 00:08:20.370 align:start position:0% using also some kind of polling again 00:08:20.370 --> 00:08:22.830 align:start position:0% using also some kind of polling again but<00:08:21.370> ideally<00:08:21.730> you<00:08:21.880> make<00:08:22.180> it<00:08:22.300> work<00:08:22.480> with<00:08:22.660> web 00:08:22.830 --> 00:08:22.840 align:start position:0% but ideally you make it work with web 00:08:22.840 --> 00:08:25.530 align:start position:0% but ideally you make it work with web sockets<00:08:23.230> or<00:08:23.440> you<00:08:23.590> actually<00:08:24.040> have<00:08:24.730> a<00:08:24.940> local 00:08:25.530 --> 00:08:25.540 align:start position:0% sockets or you actually have a local 00:08:25.540 --> 00:08:28.470 align:start position:0% sockets or you actually have a local node<00:08:25.690> running<00:08:25.870> directly<00:08:26.970> so<00:08:27.970> for<00:08:28.150> example<00:08:28.450> a 00:08:28.470 --> 00:08:28.480 align:start position:0% node running directly so for example a 00:08:28.480 --> 00:08:31.470 align:start position:0% node running directly so for example a subscription<00:08:29.110> could<00:08:29.320> be<00:08:29.530> locks<00:08:30.370> or<00:08:30.669> pending 00:08:31.470 --> 00:08:31.480 align:start position:0% subscription could be locks or pending 00:08:31.480 --> 00:08:35.250 align:start position:0% subscription could be locks or pending transactions<00:08:32.080> or<00:08:33.180> if<00:08:34.180> you<00:08:34.599> know<00:08:34.750> the<00:08:34.780> syncing 00:08:35.250 --> 00:08:35.260 align:start position:0% transactions or if you know the syncing 00:08:35.260 --> 00:08:37.980 align:start position:0% transactions or if you know the syncing or<00:08:35.380> not<00:08:35.760> the<00:08:36.760> advantage<00:08:37.180> of<00:08:37.300> that<00:08:37.360> over<00:08:37.900> the 00:08:37.980 --> 00:08:37.990 align:start position:0% or not the advantage of that over the 00:08:37.990 --> 00:08:40.170 align:start position:0% or not the advantage of that over the previous<00:08:38.409> way<00:08:39.039> how<00:08:39.219> we<00:08:39.280> did<00:08:39.520> it<00:08:39.669> is<00:08:39.820> that<00:08:39.849> it's 00:08:40.170 --> 00:08:40.180 align:start position:0% previous way how we did it is that it's 00:08:40.180 --> 00:08:41.670 align:start position:0% previous way how we did it is that it's a<00:08:40.300> lot<00:08:40.570> more<00:08:40.599> intuitive<00:08:41.200> and<00:08:41.440> a<00:08:41.560> lot<00:08:41.650> more 00:08:41.670 --> 00:08:41.680 align:start position:0% a lot more intuitive and a lot more 00:08:41.680 --> 00:08:43.350 align:start position:0% a lot more intuitive and a lot more clean<00:08:42.070> right<00:08:42.610> now<00:08:42.640> you<00:08:42.849> can<00:08:43.150> basically 00:08:43.350 --> 00:08:43.360 align:start position:0% clean right now you can basically 00:08:43.360 --> 00:08:45.180 align:start position:0% clean right now you can basically subscribe<00:08:43.960> for<00:08:44.200> information<00:08:44.710> which<00:08:44.860> is<00:08:44.980> a 00:08:45.180 --> 00:08:45.190 align:start position:0% subscribe for information which is a 00:08:45.190 --> 00:08:47.520 align:start position:0% subscribe for information which is a pattern<00:08:45.550> most<00:08:45.760> people<00:08:46.060> understand<00:08:46.510> before<00:08:47.320> we 00:08:47.520 --> 00:08:47.530 align:start position:0% pattern most people understand before we 00:08:47.530 --> 00:08:50.070 align:start position:0% pattern most people understand before we had<00:08:47.800> like<00:08:47.950> filters<00:08:48.430> and<00:08:48.850> watch<00:08:49.060> and<00:08:49.480> get<00:08:49.720> watch 00:08:50.070 --> 00:08:50.080 align:start position:0% had like filters and watch and get watch 00:08:50.080 --> 00:08:52.590 align:start position:0% had like filters and watch and get watch and<00:08:50.410> which<00:08:50.710> was<00:08:50.890> very<00:08:51.190> unclear<00:08:52.089> of<00:08:52.360> what<00:08:52.510> it 00:08:52.590 --> 00:08:52.600 align:start position:0% and which was very unclear of what it 00:08:52.600 --> 00:08:54.990 align:start position:0% and which was very unclear of what it even<00:08:52.750> means<00:08:53.070> now<00:08:54.070> everything<00:08:54.550> is<00:08:54.670> under<00:08:54.880> the 00:08:54.990 --> 00:08:55.000 align:start position:0% even means now everything is under the 00:08:55.000 --> 00:08:55.199 align:start position:0% even means now everything is under the sub 00:08:55.199 --> 00:08:55.209 align:start position:0% sub 00:08:55.209 --> 00:08:57.720 align:start position:0% sub Cripe<00:08:55.540> namespace<00:08:56.230> and<00:08:56.589> it's<00:08:57.160> pretty<00:08:57.369> clear 00:08:57.720 --> 00:08:57.730 align:start position:0% Cripe namespace and it's pretty clear 00:08:57.730 --> 00:09:00.600 align:start position:0% Cripe namespace and it's pretty clear that<00:08:58.059> this<00:08:58.629> will<00:08:58.839> be<00:08:58.959> an<00:08:59.290> event<00:08:59.709> you're<00:09:00.160> you 00:09:00.600 --> 00:09:00.610 align:start position:0% that this will be an event you're you 00:09:00.610 --> 00:09:04.350 align:start position:0% that this will be an event you're you retrieve<00:09:02.129> but<00:09:03.129> also<00:09:03.459> here<00:09:03.699> we<00:09:03.850> have<00:09:03.939> special 00:09:04.350 --> 00:09:04.360 align:start position:0% retrieve but also here we have special 00:09:04.360 --> 00:09:06.869 align:start position:0% retrieve but also here we have special cases<00:09:04.779> that<00:09:04.990> ins<00:09:05.559> ank<00:09:05.769> some<00:09:06.129> cases<00:09:06.550> you<00:09:06.670> can 00:09:06.869 --> 00:09:06.879 align:start position:0% cases that ins ank some cases you can 00:09:06.879 --> 00:09:08.730 align:start position:0% cases that ins ank some cases you can have<00:09:06.910> an<00:09:07.240> event<00:09:07.389> which<00:09:07.809> actually<00:09:08.170> can<00:09:08.350> change 00:09:08.730 --> 00:09:08.740 align:start position:0% have an event which actually can change 00:09:08.740 --> 00:09:11.639 align:start position:0% have an event which actually can change for<00:09:09.610> example<00:09:09.670> you<00:09:10.029> can<00:09:10.179> have<00:09:10.329> an<00:09:10.480> event<00:09:10.929> coming 00:09:11.639 --> 00:09:11.649 align:start position:0% for example you can have an event coming 00:09:11.649 --> 00:09:13.799 align:start position:0% for example you can have an event coming from<00:09:11.860> a<00:09:11.980> smart<00:09:12.249> contract<00:09:12.429> and<00:09:12.910> it<00:09:13.480> might<00:09:13.779> be 00:09:13.799 --> 00:09:13.809 align:start position:0% from a smart contract and it might be 00:09:13.809 --> 00:09:18.319 align:start position:0% from a smart contract and it might be different<00:09:14.519> after<00:09:15.519> chain<00:09:16.119> organization<00:09:17.019> so 00:09:18.319 --> 00:09:18.329 align:start position:0% different after chain organization so 00:09:18.329 --> 00:09:20.850 align:start position:0% different after chain organization so that's<00:09:19.329> why<00:09:19.480> we<00:09:19.629> also<00:09:19.809> here<00:09:20.199> need<00:09:20.439> this<00:09:20.619> kind 00:09:20.850 --> 00:09:20.860 align:start position:0% that's why we also here need this kind 00:09:20.860 --> 00:09:23.519 align:start position:0% that's why we also here need this kind of<00:09:20.920> pattern<00:09:21.129> that<00:09:21.309> we<00:09:21.550> are<00:09:21.670> able<00:09:21.790> to<00:09:22.230> wait<00:09:23.230> for 00:09:23.519 --> 00:09:23.529 align:start position:0% of pattern that we are able to wait for 00:09:23.529 --> 00:09:25.949 align:start position:0% of pattern that we are able to wait for the<00:09:23.949> data<00:09:24.160> the<00:09:24.550> actual<00:09:24.850> event<00:09:25.149> or<00:09:25.389> we<00:09:25.749> are<00:09:25.809> also 00:09:25.949 --> 00:09:25.959 align:start position:0% the data the actual event or we are also 00:09:25.959 --> 00:09:29.069 align:start position:0% the data the actual event or we are also able<00:09:26.439> to<00:09:26.679> wait<00:09:26.949> for<00:09:27.160> the<00:09:27.249> changed<00:09:27.670> event<00:09:28.029> so<00:09:28.959> we 00:09:29.069 --> 00:09:29.079 align:start position:0% able to wait for the changed event so we 00:09:29.079 --> 00:09:31.109 align:start position:0% able to wait for the changed event so we can<00:09:29.199> reverse<00:09:29.589> it<00:09:29.889> in<00:09:30.009> our<00:09:30.160> dab<00:09:30.490> and<00:09:30.790> we<00:09:30.939> can 00:09:31.109 --> 00:09:31.119 align:start position:0% can reverse it in our dab and we can 00:09:31.119 --> 00:09:33.929 align:start position:0% can reverse it in our dab and we can apply<00:09:31.929> the<00:09:32.230> Newton<00:09:32.800> to<00:09:32.980> new<00:09:33.189> log<00:09:33.429> which<00:09:33.699> might 00:09:33.929 --> 00:09:33.939 align:start position:0% apply the Newton to new log which might 00:09:33.939 --> 00:09:35.369 align:start position:0% apply the Newton to new log which might look<00:09:34.089> different<00:09:34.269> it<00:09:34.720> might<00:09:34.869> have<00:09:35.050> different 00:09:35.369 --> 00:09:35.379 align:start position:0% look different it might have different 00:09:35.379 --> 00:09:40.559 align:start position:0% look different it might have different results<00:09:38.610> the<00:09:39.610> way<00:09:39.759> smart<00:09:40.119> contracts<00:09:40.449> are 00:09:40.559 --> 00:09:40.569 align:start position:0% results the way smart contracts are 00:09:40.569 --> 00:09:45.230 align:start position:0% results the way smart contracts are initiated<00:09:41.529> in<00:09:41.679> the<00:09:41.800> new<00:09:41.949> web<00:09:42.509> 31.0<00:09:43.509> is<00:09:44.189> more 00:09:45.230 --> 00:09:45.240 align:start position:0% initiated in the new web 31.0 is more 00:09:45.240 --> 00:09:47.489 align:start position:0% initiated in the new web 31.0 is more the<00:09:46.240> way<00:09:46.389> we<00:09:46.540> would<00:09:46.720> expect<00:09:47.110> it<00:09:47.259> when<00:09:47.350> we 00:09:47.489 --> 00:09:47.499 align:start position:0% the way we would expect it when we 00:09:47.499 --> 00:09:50.639 align:start position:0% the way we would expect it when we actually<00:09:47.649> initiate<00:09:48.420> a<00:09:49.420> class<00:09:49.689> object<00:09:49.929> so<00:09:50.619> you 00:09:50.639 --> 00:09:50.649 align:start position:0% actually initiate a class object so you 00:09:50.649 --> 00:09:52.739 align:start position:0% actually initiate a class object so you have<00:09:50.920> to<00:09:51.069> use<00:09:51.220> the<00:09:51.399> new<00:09:51.759> keyboard<00:09:52.209> a<00:09:52.329> keyword 00:09:52.739 --> 00:09:52.749 align:start position:0% have to use the new keyboard a keyword 00:09:52.749 --> 00:09:55.549 align:start position:0% have to use the new keyboard a keyword and<00:09:53.110> you<00:09:53.139> have<00:09:54.100> to<00:09:54.249> give<00:09:54.399> it<00:09:54.490> a<00:09:54.579> JSON<00:09:54.939> interface 00:09:55.549 --> 00:09:55.559 align:start position:0% and you have to give it a JSON interface 00:09:55.559 --> 00:09:58.559 align:start position:0% and you have to give it a JSON interface this<00:09:56.559> way<00:09:56.740> you<00:09:56.800> instantiate<00:09:57.279> the<00:09:57.790> object<00:09:57.819> and 00:09:58.559 --> 00:09:58.569 align:start position:0% this way you instantiate the object and 00:09:58.569 --> 00:10:02.220 align:start position:0% this way you instantiate the object and you<00:09:59.139> can<00:09:59.319> give<00:09:59.740> it<00:09:59.769> an<00:09:59.949> address<00:10:01.019> optional<00:10:02.019> or 00:10:02.220 --> 00:10:02.230 align:start position:0% you can give it an address optional or 00:10:02.230 --> 00:10:04.829 align:start position:0% you can give it an address optional or additional<00:10:02.949> options<00:10:03.480> therefore<00:10:04.480> also<00:10:04.629> the 00:10:04.829 --> 00:10:04.839 align:start position:0% additional options therefore also the 00:10:04.839 --> 00:10:07.109 align:start position:0% additional options therefore also the options<00:10:05.379> are<00:10:05.649> in<00:10:05.679> a<00:10:06.040> separate<00:10:06.490> options<00:10:06.910> object 00:10:07.109 --> 00:10:07.119 align:start position:0% options are in a separate options object 00:10:07.119 --> 00:10:09.509 align:start position:0% options are in a separate options object so<00:10:07.660> you<00:10:07.720> can<00:10:08.079> easily<00:10:08.259> see<00:10:08.439> what<00:10:09.279> are<00:10:09.429> the 00:10:09.509 --> 00:10:09.519 align:start position:0% so you can easily see what are the 00:10:09.519 --> 00:10:13.609 align:start position:0% so you can easily see what are the current<00:10:09.730> settings<00:10:10.209> of<00:10:10.389> your<00:10:10.569> contract<00:10:10.929> object 00:10:13.609 --> 00:10:13.619 align:start position:0% 00:10:13.619 --> 00:10:16.799 align:start position:0% also<00:10:14.619> to<00:10:15.279> note<00:10:15.490> here<00:10:15.819> is<00:10:15.999> that<00:10:16.029> all<00:10:16.480> the 00:10:16.799 --> 00:10:16.809 align:start position:0% also to note here is that all the 00:10:16.809 --> 00:10:19.590 align:start position:0% also to note here is that all the addresses<00:10:16.990> returned<00:10:17.920> from<00:10:18.459> web<00:10:18.670> switches<00:10:19.179> are 00:10:19.590 --> 00:10:19.600 align:start position:0% addresses returned from web switches are 00:10:19.600 --> 00:10:23.069 align:start position:0% addresses returned from web switches are now<00:10:20.470> check<00:10:20.860> some<00:10:21.129> addresses<00:10:21.660> you<00:10:22.660> cannot<00:10:22.899> see 00:10:23.069 --> 00:10:23.079 align:start position:0% now check some addresses you cannot see 00:10:23.079 --> 00:10:26.939 align:start position:0% now check some addresses you cannot see this<00:10:23.230> here<00:10:23.439> in<00:10:23.470> this<00:10:23.649> example<00:10:24.569> but<00:10:25.949> actually 00:10:26.939 --> 00:10:26.949 align:start position:0% this here in this example but actually 00:10:26.949 --> 00:10:29.129 align:start position:0% this here in this example but actually you<00:10:27.009> can<00:10:27.189> see<00:10:27.339> it<00:10:27.639> from<00:10:27.819> it<00:10:28.509> has<00:10:28.660> an<00:10:28.779> upper<00:10:28.990> case 00:10:29.129 --> 00:10:29.139 align:start position:0% you can see it from it has an upper case 00:10:29.139 --> 00:10:32.039 align:start position:0% you can see it from it has an upper case D<00:10:29.170> for<00:10:29.649> example<00:10:29.679> upper<00:10:30.129> case<00:10:30.309> F<00:10:30.519> so<00:10:31.269> when<00:10:31.899> you 00:10:32.039 --> 00:10:32.049 align:start position:0% D for example upper case F so when you 00:10:32.049 --> 00:10:34.499 align:start position:0% D for example upper case F so when you use<00:10:32.259> an<00:10:32.410> address<00:10:32.740> and<00:10:32.889> you<00:10:32.980> pass<00:10:33.189> it<00:10:33.459> in<00:10:33.579> you 00:10:34.499 --> 00:10:34.509 align:start position:0% use an address and you pass it in you 00:10:34.509 --> 00:10:36.119 align:start position:0% use an address and you pass it in you send<00:10:34.720> it<00:10:34.809> into<00:10:35.019> any<00:10:35.170> kind<00:10:35.379> of<00:10:35.410> function<00:10:35.860> in<00:10:35.980> web 00:10:36.119 --> 00:10:36.129 align:start position:0% send it into any kind of function in web 00:10:36.129 --> 00:10:37.949 align:start position:0% send it into any kind of function in web to<00:10:36.279> test<00:10:36.519> if<00:10:36.670> we<00:10:36.790> check<00:10:37.029> to<00:10:37.179> check<00:10:37.420> some<00:10:37.629> and<00:10:37.869> if 00:10:37.949 --> 00:10:37.959 align:start position:0% to test if we check to check some and if 00:10:37.959 --> 00:10:40.400 align:start position:0% to test if we check to check some and if you<00:10:38.199> check<00:10:38.379> some<00:10:38.559> is<00:10:38.679> invalid<00:10:39.069> it<00:10:39.249> will<00:10:39.429> fail 00:10:40.400 --> 00:10:40.410 align:start position:0% you check some is invalid it will fail 00:10:40.410 --> 00:10:43.470 align:start position:0% you check some is invalid it will fail if<00:10:41.410> you<00:10:41.470> pass<00:10:41.829> in<00:10:42.100> a<00:10:42.220> lower<00:10:42.429> case<00:10:42.730> address<00:10:43.209> it 00:10:43.470 --> 00:10:43.480 align:start position:0% if you pass in a lower case address it 00:10:43.480 --> 00:10:45.150 align:start position:0% if you pass in a lower case address it will<00:10:43.660> just<00:10:43.839> accept<00:10:44.230> it<00:10:44.379> as<00:10:44.529> is<00:10:44.709> because<00:10:44.860> it 00:10:45.150 --> 00:10:45.160 align:start position:0% will just accept it as is because it 00:10:45.160 --> 00:10:50.489 align:start position:0% will just accept it as is because it cannot<00:10:45.369> check<00:10:45.579> to<00:10:45.819> check<00:10:45.999> some<00:10:48.629> now<00:10:49.629> in<00:10:50.049> the 00:10:50.489 --> 00:10:50.499 align:start position:0% cannot check to check some now in the 00:10:50.499 --> 00:10:53.189 align:start position:0% cannot check to check some now in the smart<00:10:50.769> content<00:10:51.100> object<00:10:51.579> itself<00:10:52.059> all<00:10:52.929> the 00:10:53.189 --> 00:10:53.199 align:start position:0% smart content object itself all the 00:10:53.199 --> 00:10:55.379 align:start position:0% smart content object itself all the methods<00:10:53.649> and<00:10:53.799> all<00:10:53.949> the<00:10:54.069> events<00:10:54.490> are<00:10:54.639> separated 00:10:55.379 --> 00:10:55.389 align:start position:0% methods and all the events are separated 00:10:55.389 --> 00:10:58.309 align:start position:0% methods and all the events are separated in<00:10:55.540> its<00:10:55.660> own<00:10:55.809> namespace<00:10:56.249> this<00:10:57.249> helps<00:10:57.670> with 00:10:58.309 --> 00:10:58.319 align:start position:0% in its own namespace this helps with 00:10:58.319 --> 00:11:01.049 align:start position:0% in its own namespace this helps with things<00:10:59.319> like<00:10:59.649> where<00:11:00.189> you<00:11:00.279> have<00:11:00.309> an<00:11:00.519> event<00:11:00.819> may 00:11:01.049 --> 00:11:01.059 align:start position:0% things like where you have an event may 00:11:01.059 --> 00:11:02.970 align:start position:0% things like where you have an event may be<00:11:01.089> called<00:11:01.480> the<00:11:01.660> same<00:11:01.839> way<00:11:02.079> than<00:11:02.499> a<00:11:02.529> native 00:11:02.970 --> 00:11:02.980 align:start position:0% be called the same way than a native 00:11:02.980 --> 00:11:06.139 align:start position:0% be called the same way than a native event<00:11:03.339> on<00:11:03.519> this<00:11:03.669> mark<00:11:03.879> on<00:11:04.029> the<00:11:04.120> object<00:11:04.540> and 00:11:06.139 --> 00:11:06.149 align:start position:0% event on this mark on the object and 00:11:06.149 --> 00:11:08.670 align:start position:0% event on this mark on the object and when<00:11:07.149> you<00:11:07.299> call<00:11:07.600> that<00:11:07.749> event 00:11:08.670 --> 00:11:08.680 align:start position:0% when you call that event 00:11:08.680 --> 00:11:11.639 align:start position:0% when you call that event it<00:11:08.920> gives<00:11:09.339> you<00:11:09.460> back<00:11:09.610> a<00:11:09.880> object<00:11:10.570> with<00:11:11.080> moldable 00:11:11.639 --> 00:11:11.649 align:start position:0% it gives you back a object with moldable 00:11:11.649 --> 00:11:13.290 align:start position:0% it gives you back a object with moldable actions<00:11:12.100> you<00:11:12.250> can<00:11:12.430> now<00:11:12.550> do<00:11:12.610> with<00:11:13.089> that 00:11:13.290 --> 00:11:13.300 align:start position:0% actions you can now do with that 00:11:13.300 --> 00:11:16.829 align:start position:0% actions you can now do with that function<00:11:14.250> so<00:11:15.250> for<00:11:15.399> example<00:11:15.820> if<00:11:16.029> I<00:11:16.300> call<00:11:16.600> this 00:11:16.829 --> 00:11:16.839 align:start position:0% function so for example if I call this 00:11:16.839 --> 00:11:19.620 align:start position:0% function so for example if I call this do<00:11:17.080> something<00:11:17.589> I<00:11:17.800> get<00:11:18.160> an<00:11:18.279> object<00:11:18.430> back<00:11:18.850> where 00:11:19.620 --> 00:11:19.630 align:start position:0% do something I get an object back where 00:11:19.630 --> 00:11:21.540 align:start position:0% do something I get an object back where I<00:11:19.660> can<00:11:20.020> also<00:11:20.260> later<00:11:20.649> even<00:11:21.070> change<00:11:21.370> the 00:11:21.540 --> 00:11:21.550 align:start position:0% I can also later even change the 00:11:21.550 --> 00:11:24.750 align:start position:0% I can also later even change the arguments<00:11:22.149> or<00:11:22.870> I<00:11:22.930> can<00:11:23.230> decide<00:11:23.380> to<00:11:23.770> do<00:11:24.339> I<00:11:24.399> call 00:11:24.750 --> 00:11:24.760 align:start position:0% arguments or I can decide to do I call 00:11:24.760 --> 00:11:27.000 align:start position:0% arguments or I can decide to do I call that<00:11:24.970> on<00:11:25.089> my<00:11:25.240> note<00:11:25.420> do<00:11:26.350> I<00:11:26.410> send<00:11:26.830> the 00:11:27.000 --> 00:11:27.010 align:start position:0% that on my note do I send the 00:11:27.010 --> 00:11:29.310 align:start position:0% that on my note do I send the transaction<00:11:27.220> off<00:11:27.790> to<00:11:28.000> the<00:11:28.089> node<00:11:28.300> to<00:11:28.899> be<00:11:29.020> mined 00:11:29.310 --> 00:11:29.320 align:start position:0% transaction off to the node to be mined 00:11:29.320 --> 00:11:31.590 align:start position:0% transaction off to the node to be mined in<00:11:29.470> the<00:11:29.560> network<00:11:29.950> or<00:11:30.730> if<00:11:31.000> I<00:11:31.089> just<00:11:31.330> want<00:11:31.510> to 00:11:31.590 --> 00:11:31.600 align:start position:0% in the network or if I just want to 00:11:31.600 --> 00:11:33.540 align:start position:0% in the network or if I just want to estimate<00:11:32.050> the<00:11:32.170> gasp<00:11:32.350> of<00:11:32.589> this<00:11:32.770> transaction<00:11:33.160> or 00:11:33.540 --> 00:11:33.550 align:start position:0% estimate the gasp of this transaction or 00:11:33.550 --> 00:11:36.360 align:start position:0% estimate the gasp of this transaction or I<00:11:34.060> maybe<00:11:34.450> just<00:11:34.839> want<00:11:35.020> to<00:11:35.140> encode<00:11:35.589> the<00:11:35.890> API<00:11:36.190> to 00:11:36.360 --> 00:11:36.370 align:start position:0% I maybe just want to encode the API to 00:11:36.370 --> 00:11:38.610 align:start position:0% I maybe just want to encode the API to be<00:11:36.850> used<00:11:37.089> in<00:11:37.330> as<00:11:37.660> a<00:11:37.690> parameter<00:11:38.170> and<00:11:38.320> another 00:11:38.610 --> 00:11:38.620 align:start position:0% be used in as a parameter and another 00:11:38.620 --> 00:11:42.150 align:start position:0% be used in as a parameter and another function<00:11:39.130> and<00:11:40.470> also<00:11:41.470> here<00:11:41.709> we<00:11:41.890> have<00:11:42.010> the 00:11:42.150 --> 00:11:42.160 align:start position:0% function and also here we have the 00:11:42.160 --> 00:11:43.889 align:start position:0% function and also here we have the ability<00:11:42.550> to<00:11:42.580> add<00:11:42.820> even<00:11:43.029> more<00:11:43.149> if<00:11:43.540> we<00:11:43.690> need<00:11:43.720> to 00:11:43.889 --> 00:11:43.899 align:start position:0% ability to add even more if we need to 00:11:43.899 --> 00:11:47.300 align:start position:0% ability to add even more if we need to in<00:11:44.200> the<00:11:44.320> future<00:11:44.680> and<00:11:45.130> extend<00:11:45.670> whatever<00:11:46.300> the 00:11:47.300 --> 00:11:47.310 align:start position:0% in the future and extend whatever the 00:11:47.310 --> 00:11:51.050 align:start position:0% in the future and extend whatever the method<00:11:48.450> methods<00:11:49.450> of<00:11:49.660> a<00:11:49.750> smart<00:11:49.959> phone<00:11:50.110> can<00:11:50.320> do 00:11:51.050 --> 00:11:51.060 align:start position:0% method methods of a smart phone can do 00:11:51.060 --> 00:11:53.760 align:start position:0% method methods of a smart phone can do so<00:11:52.060> if<00:11:52.300> you<00:11:52.330> for<00:11:52.600> example<00:11:52.630> call<00:11:53.140> that<00:11:53.410> it<00:11:53.620> would 00:11:53.760 --> 00:11:53.770 align:start position:0% so if you for example call that it would 00:11:53.770 --> 00:11:55.800 align:start position:0% so if you for example call that it would look<00:11:53.890> like<00:11:53.950> this<00:11:54.279> you<00:11:54.850> call<00:11:55.089> the<00:11:55.300> method<00:11:55.450> on 00:11:55.800 --> 00:11:55.810 align:start position:0% look like this you call the method on 00:11:55.810 --> 00:11:57.750 align:start position:0% look like this you call the method on the<00:11:55.930> methods<00:11:56.260> namespace<00:11:56.770> you<00:11:56.800> paste<00:11:57.310> in<00:11:57.520> the 00:11:57.750 --> 00:11:57.760 align:start position:0% the methods namespace you paste in the 00:11:57.760 --> 00:12:03.510 align:start position:0% the methods namespace you paste in the parameters<00:11:58.750> and<00:11:59.020> as<00:12:00.010> we<00:12:00.220> also<00:12:00.670> now<00:12:01.860> paste<00:12:02.860> only 00:12:03.510 --> 00:12:03.520 align:start position:0% parameters and as we also now paste only 00:12:03.520 --> 00:12:06.090 align:start position:0% parameters and as we also now paste only parameters<00:12:04.149> of<00:12:04.300> the<00:12:04.450> smart<00:12:04.690> conduct<00:12:05.100> function 00:12:06.090 --> 00:12:06.100 align:start position:0% parameters of the smart conduct function 00:12:06.100 --> 00:12:08.579 align:start position:0% parameters of the smart conduct function in<00:12:06.279> the<00:12:06.459> parameter<00:12:07.029> space<00:12:07.149> we<00:12:07.990> are<00:12:08.020> also<00:12:08.350> in 00:12:08.579 --> 00:12:08.589 align:start position:0% in the parameter space we are also in 00:12:08.589 --> 00:12:11.220 align:start position:0% in the parameter space we are also in the<00:12:08.680> future<00:12:08.830> able<00:12:09.370> to<00:12:09.520> allow<00:12:09.760> structs<00:12:10.390> which 00:12:11.220 --> 00:12:11.230 align:start position:0% the future able to allow structs which 00:12:11.230 --> 00:12:14.130 align:start position:0% the future able to allow structs which we<00:12:11.350> are<00:12:11.470> working<00:12:11.589> on<00:12:11.860> right<00:12:12.010> now<00:12:12.690> before<00:12:13.690> the 00:12:14.130 --> 00:12:14.140 align:start position:0% we are working on right now before the 00:12:14.140 --> 00:12:15.780 align:start position:0% we are working on right now before the struct<00:12:14.470> was<00:12:14.650> always<00:12:15.010> meant<00:12:15.310> as<00:12:15.580> the 00:12:15.780 --> 00:12:15.790 align:start position:0% struct was always meant as the 00:12:15.790 --> 00:12:17.670 align:start position:0% struct was always meant as the transaction<00:12:16.300> object<00:12:16.420> so<00:12:17.020> there<00:12:17.200> was<00:12:17.320> a<00:12:17.350> bit<00:12:17.560> of 00:12:17.670 --> 00:12:17.680 align:start position:0% transaction object so there was a bit of 00:12:17.680 --> 00:12:20.010 align:start position:0% transaction object so there was a bit of a<00:12:17.740> confusion<00:12:18.250> and<00:12:18.850> if<00:12:19.510> you<00:12:19.600> didn't<00:12:19.810> want<00:12:19.930> to 00:12:20.010 --> 00:12:20.020 align:start position:0% a confusion and if you didn't want to 00:12:20.020 --> 00:12:22.620 align:start position:0% a confusion and if you didn't want to send<00:12:20.290> it<00:12:20.470> you<00:12:21.040> give<00:12:21.250> it<00:12:21.400> your<00:12:21.520> the<00:12:21.880> options 00:12:22.620 --> 00:12:22.630 align:start position:0% send it you give it your the options 00:12:22.630 --> 00:12:24.120 align:start position:0% send it you give it your the options object<00:12:23.020> of<00:12:23.110> the<00:12:23.230> central<00:12:23.560> section<00:12:23.770> for 00:12:24.120 --> 00:12:24.130 align:start position:0% object of the central section for 00:12:24.130 --> 00:12:27.000 align:start position:0% object of the central section for example<00:12:24.630> for<00:12:25.630> example<00:12:26.020> if<00:12:26.110> you<00:12:26.200> then<00:12:26.350> get<00:12:26.830> this 00:12:27.000 --> 00:12:27.010 align:start position:0% example for example if you then get this 00:12:27.010 --> 00:12:28.800 align:start position:0% example for example if you then get this back<00:12:27.279> and<00:12:27.490> you<00:12:27.640> wait<00:12:27.820> for<00:12:27.850> the<00:12:28.029> receipt<00:12:28.420> or<00:12:28.720> you 00:12:28.800 --> 00:12:28.810 align:start position:0% back and you wait for the receipt or you 00:12:28.810 --> 00:12:30.570 align:start position:0% back and you wait for the receipt or you just<00:12:28.990> like<00:12:29.230> we<00:12:29.410> solve<00:12:29.620> the<00:12:29.800> promise<00:12:30.190> you<00:12:30.430> would 00:12:30.570 --> 00:12:30.580 align:start position:0% just like we solve the promise you would 00:12:30.580 --> 00:12:32.540 align:start position:0% just like we solve the promise you would get<00:12:30.790> back<00:12:31.060> to<00:12:31.330> receive<00:12:31.660> and<00:12:31.990> it<00:12:32.200> would<00:12:32.350> be 00:12:32.540 --> 00:12:32.550 align:start position:0% get back to receive and it would be 00:12:32.550 --> 00:12:38.030 align:start position:0% get back to receive and it would be decoded<00:12:34.290> parameters<00:12:35.290> also<00:12:36.220> the<00:12:36.730> raw<00:12:36.850> data<00:12:37.060> and 00:12:38.030 --> 00:12:38.040 align:start position:0% decoded parameters also the raw data and 00:12:38.040 --> 00:12:40.440 align:start position:0% decoded parameters also the raw data and everything<00:12:39.040> else<00:12:39.279> you<00:12:39.459> need<00:12:39.670> so<00:12:40.300> the 00:12:40.440 --> 00:12:40.450 align:start position:0% everything else you need so the 00:12:40.450 --> 00:12:43.170 align:start position:0% everything else you need so the structure<00:12:40.930> is<00:12:40.990> a<00:12:41.080> lot<00:12:41.260> more<00:12:41.470> clean<00:12:41.740> and<00:12:42.040> a<00:12:42.180> lot 00:12:43.170 --> 00:12:43.180 align:start position:0% structure is a lot more clean and a lot 00:12:43.180 --> 00:12:45.380 align:start position:0% structure is a lot more clean and a lot more<00:12:43.209> accessible<00:12:43.900> than<00:12:43.990> it<00:12:44.110> was<00:12:44.260> before 00:12:45.380 --> 00:12:45.390 align:start position:0% more accessible than it was before 00:12:45.390 --> 00:12:48.720 align:start position:0% more accessible than it was before same<00:12:46.390> here<00:12:46.720> if<00:12:46.839> you<00:12:46.959> have<00:12:47.080> an<00:12:47.170> event<00:12:47.459> so<00:12:48.459> if<00:12:48.610> you 00:12:48.720 --> 00:12:48.730 align:start position:0% same here if you have an event so if you 00:12:48.730 --> 00:12:50.130 align:start position:0% same here if you have an event so if you have<00:12:48.910> an<00:12:49.000> event<00:12:49.240> it's<00:12:49.420> under<00:12:49.630> the<00:12:49.690> namespace 00:12:50.130 --> 00:12:50.140 align:start position:0% have an event it's under the namespace 00:12:50.140 --> 00:12:53.699 align:start position:0% have an event it's under the namespace events<00:12:51.660> you<00:12:52.660> could<00:12:52.810> have<00:12:53.350> an<00:12:53.470> additional 00:12:53.699 --> 00:12:53.709 align:start position:0% events you could have an additional 00:12:53.709 --> 00:12:55.829 align:start position:0% events you could have an additional options<00:12:54.370> that<00:12:54.700> you<00:12:55.060> want<00:12:55.240> to<00:12:55.329> fill<00:12:55.510> the<00:12:55.660> for 00:12:55.829 --> 00:12:55.839 align:start position:0% options that you want to fill the for 00:12:55.839 --> 00:12:58.019 align:start position:0% options that you want to fill the for specific<00:12:56.260> events<00:12:56.589> for<00:12:57.490> example<00:12:57.820> you<00:12:57.910> could 00:12:58.019 --> 00:12:58.029 align:start position:0% specific events for example you could 00:12:58.029 --> 00:13:00.060 align:start position:0% specific events for example you could say<00:12:58.089> I<00:12:58.270> only<00:12:58.540> want<00:12:58.690> to<00:12:58.959> have<00:12:59.170> events<00:12:59.680> which 00:13:00.060 --> 00:13:00.070 align:start position:0% say I only want to have events which 00:13:00.070 --> 00:13:03.360 align:start position:0% say I only want to have events which matches<00:13:00.430> the<00:13:00.670> my<00:13:01.420> index<00:13:01.839> parameter<00:13:02.220> 20<00:13:03.220> with 00:13:03.360 --> 00:13:03.370 align:start position:0% matches the my index parameter 20 with 00:13:03.370 --> 00:13:07.650 align:start position:0% matches the my index parameter 20 with the<00:13:03.520> value<00:13:03.790> 20<00:13:04.180> and<00:13:04.329> 30<00:13:04.570> and<00:13:05.670> my<00:13:06.670> other<00:13:06.850> index 00:13:07.650 --> 00:13:07.660 align:start position:0% the value 20 and 30 and my other index 00:13:07.660 --> 00:13:09.210 align:start position:0% the value 20 and 30 and my other index parameter<00:13:07.779> has<00:13:08.200> to<00:13:08.320> have<00:13:08.470> an<00:13:08.560> address<00:13:08.709> so<00:13:09.070> and 00:13:09.210 --> 00:13:09.220 align:start position:0% parameter has to have an address so and 00:13:09.220 --> 00:13:13.139 align:start position:0% parameter has to have an address so and so<00:13:09.370> and<00:13:10.950> it<00:13:11.950> would<00:13:12.190> then<00:13:12.339> only<00:13:12.459> which<00:13:12.760> we<00:13:12.940> view 00:13:13.139 --> 00:13:13.149 align:start position:0% so and it would then only which we view 00:13:13.149 --> 00:13:15.660 align:start position:0% so and it would then only which we view these<00:13:13.329> events<00:13:13.810> matching<00:13:14.649> that<00:13:14.829> and<00:13:15.100> you<00:13:15.490> would 00:13:15.660 --> 00:13:15.670 align:start position:0% these events matching that and you would 00:13:15.670 --> 00:13:17.699 align:start position:0% these events matching that and you would get<00:13:15.850> them<00:13:16.230> basically<00:13:17.230> once<00:13:17.440> they<00:13:17.650> are 00:13:17.699 --> 00:13:17.709 align:start position:0% get them basically once they are 00:13:17.709 --> 00:13:20.640 align:start position:0% get them basically once they are happening<00:13:18.190> and<00:13:19.020> this<00:13:20.020> is<00:13:20.079> under<00:13:20.440> the<00:13:20.529> hood 00:13:20.640 --> 00:13:20.650 align:start position:0% happening and this is under the hood 00:13:20.650 --> 00:13:22.790 align:start position:0% happening and this is under the hood using<00:13:20.980> for<00:13:21.130> example<00:13:21.190> subscriptions 00:13:22.790 --> 00:13:22.800 align:start position:0% using for example subscriptions 00:13:22.800 --> 00:13:25.530 align:start position:0% using for example subscriptions which<00:13:23.800> right<00:13:24.250> now<00:13:24.310> it<00:13:24.550> doesn't<00:13:24.700> work<00:13:24.880> for<00:13:25.060> HTTP 00:13:25.530 --> 00:13:25.540 align:start position:0% which right now it doesn't work for HTTP 00:13:25.540 --> 00:13:32.010 align:start position:0% which right now it doesn't work for HTTP so<00:13:25.990> we<00:13:26.140> have<00:13:26.320> to<00:13:26.530> at<00:13:27.250> the<00:13:27.820> polling<00:13:28.180> here<00:13:30.810> web<00:13:31.810> 3 00:13:32.010 --> 00:13:32.020 align:start position:0% so we have to at the polling here web 3 00:13:32.020 --> 00:13:33.870 align:start position:0% so we have to at the polling here web 3 use<00:13:32.230> accounts<00:13:32.800> that's<00:13:32.950> actually<00:13:33.400> a<00:13:33.460> complete 00:13:33.870 --> 00:13:33.880 align:start position:0% use accounts that's actually a complete 00:13:33.880 --> 00:13:36.000 align:start position:0% use accounts that's actually a complete new<00:13:34.060> thing<00:13:34.380> because<00:13:35.380> web<00:13:35.740> through<00:13:35.890> these 00:13:36.000 --> 00:13:36.010 align:start position:0% new thing because web through these 00:13:36.010 --> 00:13:37.850 align:start position:0% new thing because web through these accounts<00:13:36.490> allows<00:13:36.970> you<00:13:37.210> to<00:13:37.330> actually<00:13:37.630> generate 00:13:37.850 --> 00:13:37.860 align:start position:0% accounts allows you to actually generate 00:13:37.860 --> 00:13:41.280 align:start position:0% accounts allows you to actually generate accounts<00:13:38.860> and<00:13:39.010> sign<00:13:39.790> data 00:13:41.280 --> 00:13:41.290 align:start position:0% accounts and sign data 00:13:41.290 --> 00:13:44.220 align:start position:0% accounts and sign data sign<00:13:42.010> transaction<00:13:42.640> encrypt<00:13:43.510> these<00:13:43.720> accounts 00:13:44.220 --> 00:13:44.230 align:start position:0% sign transaction encrypt these accounts 00:13:44.230 --> 00:13:46.320 align:start position:0% sign transaction encrypt these accounts decrypt<00:13:44.620> these<00:13:44.740> accounts<00:13:45.220> import<00:13:45.790> key<00:13:46.000> store 00:13:46.320 --> 00:13:46.330 align:start position:0% decrypt these accounts import key store 00:13:46.330 --> 00:13:49.560 align:start position:0% decrypt these accounts import key store accounts<00:13:47.020> and<00:13:47.910> basically<00:13:48.910> gives<00:13:49.060> you<00:13:49.180> all<00:13:49.360> the 00:13:49.560 --> 00:13:49.570 align:start position:0% accounts and basically gives you all the 00:13:49.570 --> 00:13:50.880 align:start position:0% accounts and basically gives you all the tools<00:13:49.720> you<00:13:49.960> need<00:13:49.990> if<00:13:50.320> you<00:13:50.410> want<00:13:50.590> to<00:13:50.650> interact 00:13:50.880 --> 00:13:50.890 align:start position:0% tools you need if you want to interact 00:13:50.890 --> 00:13:54.570 align:start position:0% tools you need if you want to interact with<00:13:51.130> a<00:13:52.410> public<00:13:53.410> key<00:13:53.590> private<00:13:53.980> key<00:13:54.190> account 00:13:54.570 --> 00:13:54.580 align:start position:0% with a public key private key account 00:13:54.580 --> 00:13:58.100 align:start position:0% with a public key private key account and<00:13:55.800> having<00:13:56.800> these<00:13:56.950> signing<00:13:57.400> functions<00:13:57.880> in 00:13:58.100 --> 00:13:58.110 align:start position:0% and having these signing functions in 00:13:58.110 --> 00:14:01.110 align:start position:0% and having these signing functions in Webster<00:13:59.110> HS<00:13:59.410> directly<00:13:59.920> allows<00:14:00.580> us<00:14:00.820> to<00:14:00.970> do<00:14:01.090> a 00:14:01.110 --> 00:14:01.120 align:start position:0% Webster HS directly allows us to do a 00:14:01.120 --> 00:14:04.860 align:start position:0% Webster HS directly allows us to do a lot<00:14:01.360> more<00:14:02.610> what<00:14:03.610> you<00:14:03.790> before<00:14:04.270> would<00:14:04.600> have<00:14:04.720> to 00:14:04.860 --> 00:14:04.870 align:start position:0% lot more what you before would have to 00:14:04.870 --> 00:14:08.490 align:start position:0% lot more what you before would have to do<00:14:05.050> with<00:14:05.260> multiple<00:14:05.890> libraries<00:14:06.280> a<00:14:07.110> note<00:14:08.110> here 00:14:08.490 --> 00:14:08.500 align:start position:0% do with multiple libraries a note here 00:14:08.500 --> 00:14:09.900 align:start position:0% do with multiple libraries a note here this<00:14:08.770> is<00:14:08.950> still<00:14:09.190> in<00:14:09.220> better 00:14:09.900 --> 00:14:09.910 align:start position:0% this is still in better 00:14:09.910 --> 00:14:12.810 align:start position:0% this is still in better there's<00:14:10.510> no<00:14:10.720> all<00:14:10.930> and<00:14:11.140> run<00:14:11.290> on<00:14:11.440> that<00:14:11.650> so<00:14:12.130> use<00:14:12.670> it 00:14:12.810 --> 00:14:12.820 align:start position:0% there's no all and run on that so use it 00:14:12.820 --> 00:14:15.710 align:start position:0% there's no all and run on that so use it at<00:14:12.940> your<00:14:12.970> own<00:14:13.180> risk 00:14:15.710 --> 00:14:15.720 align:start position:0% 00:14:15.720 --> 00:14:18.180 align:start position:0% we<00:14:16.720> will<00:14:16.900> ideally<00:14:17.290> have<00:14:17.440> an<00:14:17.560> audit<00:14:17.860> on<00:14:17.980> that 00:14:18.180 --> 00:14:18.190 align:start position:0% we will ideally have an audit on that 00:14:18.190 --> 00:14:23.420 align:start position:0% we will ideally have an audit on that and<00:14:19.350> then<00:14:20.350> it's<00:14:20.560> probably<00:14:20.890> more<00:14:21.010> safe<00:14:21.220> to<00:14:21.250> use 00:14:23.420 --> 00:14:23.430 align:start position:0% and then it's probably more safe to use 00:14:23.430 --> 00:14:26.970 align:start position:0% and then it's probably more safe to use we<00:14:24.430> have<00:14:24.670> a<00:14:25.060> bi<00:14:25.840> directly<00:14:26.560> a<00:14:26.770> bi 00:14:26.970 --> 00:14:26.980 align:start position:0% we have a bi directly a bi 00:14:26.980 --> 00:14:28.830 align:start position:0% we have a bi directly a bi encoding/decoding<00:14:27.700> functions<00:14:28.390> I<00:14:28.510> think<00:14:28.720> this 00:14:28.830 --> 00:14:28.840 align:start position:0% encoding/decoding functions I think this 00:14:28.840 --> 00:14:31.290 align:start position:0% encoding/decoding functions I think this is<00:14:28.960> very<00:14:29.170> important<00:14:29.770> because<00:14:30.060> you<00:14:31.060> are<00:14:31.150> able 00:14:31.290 --> 00:14:31.300 align:start position:0% is very important because you are able 00:14:31.300 --> 00:14:35.310 align:start position:0% is very important because you are able now<00:14:31.570> to<00:14:31.600> like<00:14:32.260> encode<00:14:32.800> your<00:14:33.040> own<00:14:33.520> ABI<00:14:34.110> calls 00:14:35.310 --> 00:14:35.320 align:start position:0% now to like encode your own ABI calls 00:14:35.320 --> 00:14:38.190 align:start position:0% now to like encode your own ABI calls decode<00:14:36.250> them<00:14:36.520> and<00:14:36.880> you<00:14:37.630> have<00:14:37.780> all<00:14:37.960> of<00:14:37.990> this 00:14:38.190 --> 00:14:38.200 align:start position:0% decode them and you have all of this 00:14:38.200 --> 00:14:40.440 align:start position:0% decode them and you have all of this what<00:14:38.410> was<00:14:38.650> what<00:14:39.130> she<00:14:39.310> was<00:14:39.460> before<00:14:39.730> inverse 00:14:40.440 --> 00:14:40.450 align:start position:0% what was what she was before inverse 00:14:40.450 --> 00:14:43.680 align:start position:0% what was what she was before inverse which<00:14:40.660> is<00:14:40.900> internal<00:14:41.730> exposed<00:14:42.730> and<00:14:43.120> nicely 00:14:43.680 --> 00:14:43.690 align:start position:0% which is internal exposed and nicely 00:14:43.690 --> 00:14:46.920 align:start position:0% which is internal exposed and nicely named<00:14:44.110> and<00:14:44.410> so<00:14:44.560> on<00:14:44.700> it<00:14:45.700> even<00:14:46.120> can<00:14:46.300> decode<00:14:46.660> you<00:14:46.900> a 00:14:46.920 --> 00:14:46.930 align:start position:0% named and so on it even can decode you a 00:14:46.930 --> 00:14:50.730 align:start position:0% named and so on it even can decode you a whole<00:14:47.200> lock<00:14:47.790> automatically<00:14:49.350> we<00:14:50.350> have<00:14:50.500> now<00:14:50.680> the 00:14:50.730 --> 00:14:50.740 align:start position:0% whole lock automatically we have now the 00:14:50.740 --> 00:14:54.030 align:start position:0% whole lock automatically we have now the new<00:14:51.160> swarm<00:14:51.550> API<00:14:52.000> as<00:14:52.570> well<00:14:52.900> so<00:14:53.470> you're<00:14:53.680> able<00:14:53.860> to 00:14:54.030 --> 00:14:54.040 align:start position:0% new swarm API as well so you're able to 00:14:54.040 --> 00:14:56.340 align:start position:0% new swarm API as well so you're able to interact<00:14:54.280> with<00:14:54.580> swarm<00:14:55.060> swarm<00:14:55.660> works<00:14:56.140> a<00:14:56.260> little 00:14:56.340 --> 00:14:56.350 align:start position:0% interact with swarm swarm works a little 00:14:56.350 --> 00:14:59.730 align:start position:0% interact with swarm swarm works a little bit<00:14:56.560> different<00:14:57.130> than<00:14:57.460> the<00:14:58.110> film<00:14:59.110> node<00:14:59.350> so<00:14:59.620> the 00:14:59.730 --> 00:14:59.740 align:start position:0% bit different than the film node so the 00:14:59.740 --> 00:15:01.230 align:start position:0% bit different than the film node so the provider<00:15:00.100> is<00:15:00.250> different<00:15:00.700> it<00:15:00.790> doesn't<00:15:01.090> use 00:15:01.230 --> 00:15:01.240 align:start position:0% provider is different it doesn't use 00:15:01.240 --> 00:15:03.960 align:start position:0% provider is different it doesn't use this<00:15:01.420> the<00:15:01.870> IPC<00:15:02.350> connection<00:15:02.860> you<00:15:03.640> can<00:15:03.790> either 00:15:03.960 --> 00:15:03.970 align:start position:0% this the IPC connection you can either 00:15:03.970 --> 00:15:07.350 align:start position:0% this the IPC connection you can either use<00:15:04.680> directly<00:15:05.680> HTTP<00:15:06.250> or<00:15:06.580> it<00:15:06.790> connects<00:15:07.150> to<00:15:07.270> your 00:15:07.350 --> 00:15:07.360 align:start position:0% use directly HTTP or it connects to your 00:15:07.360 --> 00:15:10.680 align:start position:0% use directly HTTP or it connects to your local<00:15:07.570> swarm<00:15:08.170> node<00:15:08.380> which<00:15:08.620> opens<00:15:09.010> a<00:15:09.690> local 00:15:10.680 --> 00:15:10.690 align:start position:0% local swarm node which opens a local 00:15:10.690 --> 00:15:17.670 align:start position:0% local swarm node which opens a local host<00:15:11.400> 8<00:15:12.400> 5<00:15:12.910> something<00:15:14.640> endpoint<00:15:15.640> and<00:15:16.680> this 00:15:17.670 --> 00:15:17.680 align:start position:0% host 8 5 something endpoint and this 00:15:17.680 --> 00:15:19.140 align:start position:0% host 8 5 something endpoint and this basically<00:15:18.040> allows<00:15:18.280> you<00:15:18.430> to<00:15:18.550> upload<00:15:18.790> files 00:15:19.140 --> 00:15:19.150 align:start position:0% basically allows you to upload files 00:15:19.150 --> 00:15:23.130 align:start position:0% basically allows you to upload files download<00:15:19.960> files<00:15:20.230> and<00:15:21.180> even<00:15:22.180> opens<00:15:22.570> a<00:15:22.750> file 00:15:23.130 --> 00:15:23.140 align:start position:0% download files and even opens a file 00:15:23.140 --> 00:15:25.680 align:start position:0% download files and even opens a file picker<00:15:23.590> way<00:15:23.740> can<00:15:23.980> file<00:15:24.670> pic<00:15:24.970> so<00:15:25.300> if<00:15:25.420> you<00:15:25.510> in<00:15:25.600> the 00:15:25.680 --> 00:15:25.690 align:start position:0% picker way can file pic so if you in the 00:15:25.690 --> 00:15:27.300 align:start position:0% picker way can file pic so if you in the browser<00:15:25.930> you<00:15:26.200> can<00:15:26.350> pick<00:15:26.620> your<00:15:26.830> files<00:15:27.100> and 00:15:27.300 --> 00:15:27.310 align:start position:0% browser you can pick your files and 00:15:27.310 --> 00:15:29.070 align:start position:0% browser you can pick your files and upload<00:15:27.430> them<00:15:27.760> to<00:15:27.790> Swan<00:15:28.120> directly<00:15:28.600> and<00:15:28.780> you<00:15:28.870> get 00:15:29.070 --> 00:15:29.080 align:start position:0% upload them to Swan directly and you get 00:15:29.080 --> 00:15:32.880 align:start position:0% upload them to Swan directly and you get the<00:15:29.260> hash<00:15:29.440> back<00:15:29.770> to<00:15:30.160> interoperate<00:15:30.520> with<00:15:30.790> it 00:15:32.880 --> 00:15:32.890 align:start position:0% the hash back to interoperate with it 00:15:32.890 --> 00:15:36.360 align:start position:0% the hash back to interoperate with it whisper<00:15:33.850> is<00:15:34.170> currently<00:15:35.170> the<00:15:35.260> whisper 00:15:36.360 --> 00:15:36.370 align:start position:0% whisper is currently the whisper 00:15:36.370 --> 00:15:39.180 align:start position:0% whisper is currently the whisper version<00:15:36.640> 5<00:15:36.880> API<00:15:37.480> in<00:15:37.750> web<00:15:37.900> switch<00:15:38.110> s<00:15:38.350> there's 00:15:39.180 --> 00:15:39.190 align:start position:0% version 5 API in web switch s there's 00:15:39.190 --> 00:15:41.280 align:start position:0% version 5 API in web switch s there's right<00:15:39.490> now<00:15:39.700> a<00:15:39.970> discussion<00:15:40.420> about<00:15:40.690> refactoring 00:15:41.280 --> 00:15:41.290 align:start position:0% right now a discussion about refactoring 00:15:41.290 --> 00:15:43.950 align:start position:0% right now a discussion about refactoring into<00:15:41.710> version<00:15:42.010> 6<00:15:42.450> which<00:15:43.450> will<00:15:43.630> also<00:15:43.839> be 00:15:43.950 --> 00:15:43.960 align:start position:0% into version 6 which will also be 00:15:43.960 --> 00:15:47.100 align:start position:0% into version 6 which will also be supported<00:15:44.260> by<00:15:44.740> parity<00:15:45.300> the<00:15:46.300> current<00:15:46.660> version 00:15:47.100 --> 00:15:47.110 align:start position:0% supported by parity the current version 00:15:47.110 --> 00:15:50.130 align:start position:0% supported by parity the current version 5<00:15:47.470> is<00:15:48.010> basically<00:15:48.460> in<00:15:48.760> the<00:15:48.970> old<00:15:49.240> web<00:15:49.720> switches 00:15:50.130 --> 00:15:50.140 align:start position:0% 5 is basically in the old web switches 00:15:50.140 --> 00:15:51.960 align:start position:0% 5 is basically in the old web switches and<00:15:50.350> Oswell<00:15:50.740> and<00:15:50.980> the<00:15:51.100> new<00:15:51.250> one<00:15:51.460> and<00:15:51.670> you<00:15:51.790> can 00:15:51.960 --> 00:15:51.970 align:start position:0% and Oswell and the new one and you can 00:15:51.970 --> 00:15:56.820 align:start position:0% and Oswell and the new one and you can play<00:15:52.210> around<00:15:52.360> with<00:15:52.570> it<00:15:52.810> and<00:15:53.490> experiment<00:15:55.830> and 00:15:56.820 --> 00:15:56.830 align:start position:0% play around with it and experiment and 00:15:56.830 --> 00:15:59.370 align:start position:0% play around with it and experiment and the<00:15:57.460> details<00:15:57.760> function<00:15:58.210> obviously<00:15:58.960> there's<00:15:59.320> a 00:15:59.370 --> 00:15:59.380 align:start position:0% the details function obviously there's a 00:15:59.380 --> 00:16:04.280 align:start position:0% the details function obviously there's a lot<00:15:59.620> of<00:15:59.740> extra<00:16:00.130> utility<00:16:00.870> tools<00:16:01.870> you<00:16:02.050> can<00:16:02.200> use 00:16:04.280 --> 00:16:04.290 align:start position:0% 00:16:04.290 --> 00:16:07.019 align:start position:0% there's<00:16:05.290> a<00:16:05.410> lot<00:16:05.589> of<00:16:05.770> things<00:16:06.310> you<00:16:06.490> would<00:16:06.640> use<00:16:06.790> as 00:16:07.019 --> 00:16:07.029 align:start position:0% there's a lot of things you would use as 00:16:07.029 --> 00:16:10.620 align:start position:0% there's a lot of things you would use as a<00:16:07.740> that<00:16:08.740> app<00:16:09.070> developer<00:16:09.610> especially<00:16:10.270> here 00:16:10.620 --> 00:16:10.630 align:start position:0% a that app developer especially here 00:16:10.630 --> 00:16:12.990 align:start position:0% a that app developer especially here things<00:16:11.560> to<00:16:11.740> check<00:16:11.950> for<00:16:12.279> example<00:16:12.640> focus<00:16:12.850> champ 00:16:12.990 --> 00:16:13.000 align:start position:0% things to check for example focus champ 00:16:13.000 --> 00:16:15.660 align:start position:0% things to check for example focus champ check<00:16:13.330> some<00:16:13.510> addresses<00:16:14.490> encoding<00:16:15.490> and 00:16:15.660 --> 00:16:15.670 align:start position:0% check some addresses encoding and 00:16:15.670 --> 00:16:18.720 align:start position:0% check some addresses encoding and decoding<00:16:16.260> to<00:16:17.260> a<00:16:17.290> certain<00:16:17.740> extent<00:16:18.310> especially 00:16:18.720 --> 00:16:18.730 align:start position:0% decoding to a certain extent especially 00:16:18.730 --> 00:16:23.450 align:start position:0% decoding to a certain extent especially from<00:16:19.300> utf-8<00:16:20.040> I'm<00:16:21.040> converting<00:16:21.610> numbers<00:16:22.270> and 00:16:23.450 --> 00:16:23.460 align:start position:0% from utf-8 I'm converting numbers and 00:16:23.460 --> 00:16:26.010 align:start position:0% from utf-8 I'm converting numbers and internally<00:16:24.460> right<00:16:24.670> now<00:16:24.880> we<00:16:24.940> are<00:16:25.360> using<00:16:25.390> always 00:16:26.010 --> 00:16:26.020 align:start position:0% internally right now we are using always 00:16:26.020 --> 00:16:29.340 align:start position:0% internally right now we are using always DPN<00:16:26.950> library<00:16:27.460> but<00:16:28.390> when<00:16:28.570> it<00:16:28.720> returns<00:16:29.110> a<00:16:29.200> number 00:16:29.340 --> 00:16:29.350 align:start position:0% DPN library but when it returns a number 00:16:29.350 --> 00:16:31.579 align:start position:0% DPN library but when it returns a number it<00:16:29.650> returns<00:16:30.010> the<00:16:30.190> number<00:16:30.310> as<00:16:30.580> a<00:16:30.610> plain<00:16:30.970> string 00:16:31.579 --> 00:16:31.589 align:start position:0% it returns the number as a plain string 00:16:31.589 --> 00:16:33.840 align:start position:0% it returns the number as a plain string so<00:16:32.589> that<00:16:32.620> you<00:16:32.890> can<00:16:33.070> actually<00:16:33.250> use<00:16:33.580> whatever 00:16:33.840 --> 00:16:33.850 align:start position:0% so that you can actually use whatever 00:16:33.850 --> 00:16:35.760 align:start position:0% so that you can actually use whatever library<00:16:34.420> you<00:16:34.540> want<00:16:34.720> to<00:16:34.990> interact<00:16:35.320> with<00:16:35.470> large 00:16:35.760 --> 00:16:35.770 align:start position:0% library you want to interact with large 00:16:35.770 --> 00:16:37.740 align:start position:0% library you want to interact with large numbers<00:16:36.220> and<00:16:36.460> it's<00:16:36.910> also<00:16:37.120> for<00:16:37.420> debugging 00:16:37.740 --> 00:16:37.750 align:start position:0% numbers and it's also for debugging 00:16:37.750 --> 00:16:39.810 align:start position:0% numbers and it's also for debugging reasons<00:16:38.200> a<00:16:38.290> lot<00:16:38.320> easier<00:16:38.890> to<00:16:39.100> see<00:16:39.279> the<00:16:39.430> number 00:16:39.810 --> 00:16:39.820 align:start position:0% reasons a lot easier to see the number 00:16:39.820 --> 00:16:44.160 align:start position:0% reasons a lot easier to see the number rather<00:16:40.480> than<00:16:40.600> a<00:16:40.750> big<00:16:40.990> number<00:16:41.200> object<00:16:41.709> and<00:16:43.170> very 00:16:44.160 --> 00:16:44.170 align:start position:0% rather than a big number object and very 00:16:44.170 --> 00:16:47.329 align:start position:0% rather than a big number object and very important<00:16:44.589> probably<00:16:44.770> also<00:16:45.390> you're<00:16:46.390> able<00:16:46.750> to 00:16:47.329 --> 00:16:47.339 align:start position:0% important probably also you're able to 00:16:47.339 --> 00:16:51.440 align:start position:0% important probably also you're able to hash<00:16:48.339> exactly<00:16:49.000> the<00:16:49.120> way<00:16:49.440> solidity<00:16:50.440> hashes<00:16:50.950> so 00:16:51.440 --> 00:16:51.450 align:start position:0% hash exactly the way solidity hashes so 00:16:51.450 --> 00:16:53.790 align:start position:0% hash exactly the way solidity hashes so this<00:16:52.450> allows<00:16:52.720> you<00:16:52.930> to<00:16:53.080> basically<00:16:53.440> generate 00:16:53.790 --> 00:16:53.800 align:start position:0% this allows you to basically generate 00:16:53.800 --> 00:16:56.490 align:start position:0% this allows you to basically generate some<00:16:54.190> hash<00:16:54.400> and<00:16:54.700> then<00:16:54.850> knowing<00:16:55.750> that<00:16:56.140> the 00:16:56.490 --> 00:16:56.500 align:start position:0% some hash and then knowing that the 00:16:56.500 --> 00:16:58.170 align:start position:0% some hash and then knowing that the smartphone<00:16:56.920> itself<00:16:57.040> would<00:16:57.520> come<00:16:57.730> to<00:16:57.880> the<00:16:57.970> same 00:16:58.170 --> 00:16:58.180 align:start position:0% smartphone itself would come to the same 00:16:58.180 --> 00:17:01.050 align:start position:0% smartphone itself would come to the same hash<00:16:58.650> so<00:16:59.650> this<00:16:59.920> is<00:17:00.070> tightly<00:17:00.339> packing<00:17:00.910> the 00:17:01.050 --> 00:17:01.060 align:start position:0% hash so this is tightly packing the 00:17:01.060 --> 00:17:02.610 align:start position:0% hash so this is tightly packing the arguments<00:17:01.630> the<00:17:01.779> multiple<00:17:02.170> ways<00:17:02.200> of<00:17:02.380> how<00:17:02.589> you 00:17:02.610 --> 00:17:02.620 align:start position:0% arguments the multiple ways of how you 00:17:02.620 --> 00:17:04.439 align:start position:0% arguments the multiple ways of how you can<00:17:02.860> do<00:17:02.980> that<00:17:03.160> you<00:17:03.640> can<00:17:03.850> use<00:17:04.030> the<00:17:04.209> order 00:17:04.439 --> 00:17:04.449 align:start position:0% can do that you can use the order 00:17:04.449 --> 00:17:05.850 align:start position:0% can do that you can use the order detection<00:17:04.959> which<00:17:05.110> is<00:17:05.230> probably<00:17:05.500> not<00:17:05.559> very 00:17:05.850 --> 00:17:05.860 align:start position:0% detection which is probably not very 00:17:05.860 --> 00:17:07.919 align:start position:0% detection which is probably not very safe<00:17:06.130> for<00:17:06.429> things<00:17:06.760> like<00:17:06.939> numbers<00:17:07.360> which 00:17:07.919 --> 00:17:07.929 align:start position:0% safe for things like numbers which 00:17:07.929 --> 00:17:11.910 align:start position:0% safe for things like numbers which simply<00:17:08.290> convert<00:17:08.620> to<00:17:08.740> you<00:17:09.040> in<00:17:09.250> 256<00:17:09.819> it's<00:17:10.240> easy<00:17:10.920> a 00:17:11.910 --> 00:17:11.920 align:start position:0% simply convert to you in 256 it's easy a 00:17:11.920 --> 00:17:15.990 align:start position:0% simply convert to you in 256 it's easy a string<00:17:12.699> would<00:17:12.910> be<00:17:12.970> converted<00:17:13.660> right<00:17:14.110> from<00:17:15.000> a 00:17:15.990 --> 00:17:16.000 align:start position:0% string would be converted right from a 00:17:16.000 --> 00:17:20.449 align:start position:0% string would be converted right from a utf-8<00:17:16.929> and<00:17:17.730> obviously<00:17:18.730> bytes<00:17:19.000> would<00:17:19.270> be<00:17:19.449> bytes 00:17:20.449 --> 00:17:20.459 align:start position:0% utf-8 and obviously bytes would be bytes 00:17:20.459 --> 00:17:23.730 align:start position:0% utf-8 and obviously bytes would be bytes the<00:17:21.459> byte<00:17:21.939> 32<00:17:22.360> right<00:17:22.510> now<00:17:22.660> I<00:17:22.689> think<00:17:22.839> but<00:17:23.650> you 00:17:23.730 --> 00:17:23.740 align:start position:0% the byte 32 right now I think but you 00:17:23.740 --> 00:17:25.439 align:start position:0% the byte 32 right now I think but you can<00:17:23.890> also<00:17:24.100> give<00:17:24.370> it<00:17:24.459> an<00:17:24.550> object<00:17:24.730> and<00:17:25.150> tell<00:17:25.300> it 00:17:25.439 --> 00:17:25.449 align:start position:0% can also give it an object and tell it 00:17:25.449 --> 00:17:28.110 align:start position:0% can also give it an object and tell it the<00:17:25.689> exact<00:17:26.020> type<00:17:26.319> so<00:17:26.890> this<00:17:27.220> can<00:17:27.400> be<00:17:27.429> V<00:17:27.730> and<00:17:27.910> T 00:17:28.110 --> 00:17:28.120 align:start position:0% the exact type so this can be V and T 00:17:28.120 --> 00:17:30.180 align:start position:0% the exact type so this can be V and T but<00:17:28.300> it<00:17:28.420> can<00:17:28.540> also<00:17:28.690> be<00:17:28.809> value<00:17:29.260> and<00:17:29.410> type<00:17:29.650> and 00:17:30.180 --> 00:17:30.190 align:start position:0% but it can also be value and type and 00:17:30.190 --> 00:17:32.850 align:start position:0% but it can also be value and type and you<00:17:31.059> can<00:17:31.090> basically<00:17:31.870> tell<00:17:32.170> them<00:17:32.320> hey<00:17:32.500> this<00:17:32.530> is 00:17:32.850 --> 00:17:32.860 align:start position:0% you can basically tell them hey this is 00:17:32.860 --> 00:17:34.410 align:start position:0% you can basically tell them hey this is my<00:17:33.010> arguments<00:17:33.550> this<00:17:33.700> is<00:17:33.820> the<00:17:33.970> type<00:17:34.150> of<00:17:34.179> the 00:17:34.410 --> 00:17:34.420 align:start position:0% my arguments this is the type of the 00:17:34.420 --> 00:17:39.030 align:start position:0% my arguments this is the type of the arguments<00:17:34.960> and<00:17:35.110> then<00:17:35.290> hash<00:17:35.830> them<00:17:37.650> yeah<00:17:38.650> it<00:17:38.950> is 00:17:39.030 --> 00:17:39.040 align:start position:0% arguments and then hash them yeah it is 00:17:39.040 --> 00:17:43.020 align:start position:0% arguments and then hash them yeah it is just<00:17:39.070> a<00:17:39.280> longer<00:17:39.490> version<00:17:41.520> and<00:17:42.520> this<00:17:42.880> is 00:17:43.020 --> 00:17:43.030 align:start position:0% just a longer version and this is 00:17:43.030 --> 00:17:45.080 align:start position:0% just a longer version and this is another<00:17:43.240> worse 00:17:45.080 --> 00:17:45.090 align:start position:0% another worse 00:17:45.090 --> 00:17:49.649 align:start position:0% another worse so<00:17:46.090> yeah<00:17:46.509> actually<00:17:47.139> it<00:17:47.649> works<00:17:48.130> right<00:17:48.309> now<00:17:48.659> I 00:17:49.649 --> 00:17:49.659 align:start position:0% so yeah actually it works right now I 00:17:49.659 --> 00:17:52.769 align:start position:0% so yeah actually it works right now I think<00:17:50.620> for<00:17:50.889> the<00:17:50.980> reason<00:17:51.429> how<00:17:51.700> NPM<00:17:52.240> works<00:17:52.509> it 00:17:52.769 --> 00:17:52.779 align:start position:0% think for the reason how NPM works it 00:17:52.779 --> 00:17:54.840 align:start position:0% think for the reason how NPM works it will<00:17:52.990> right<00:17:53.289> now<00:17:53.320> by<00:17:53.860> default<00:17:54.009> install<00:17:54.730> the 00:17:54.840 --> 00:17:54.850 align:start position:0% will right now by default install the 00:17:54.850 --> 00:17:57.450 align:start position:0% will right now by default install the beta<00:17:55.059> version<00:17:55.860> which<00:17:56.860> is<00:17:56.980> probably<00:17:57.250> not<00:17:57.309> very 00:17:57.450 --> 00:17:57.460 align:start position:0% beta version which is probably not very 00:17:57.460 --> 00:18:01.889 align:start position:0% beta version which is probably not very wanted<00:17:58.210> but<00:17:58.419> this<00:17:58.570> is<00:17:59.669> the<00:18:00.669> fault<00:18:01.120> of<00:18:01.240> NPM<00:18:01.779> I 00:18:01.889 --> 00:18:01.899 align:start position:0% wanted but this is the fault of NPM I 00:18:01.899 --> 00:18:05.730 align:start position:0% wanted but this is the fault of NPM I guess<00:18:02.139> and<00:18:03.720> there's<00:18:04.720> a<00:18:04.899> extended 00:18:05.730 --> 00:18:05.740 align:start position:0% guess and there's a extended 00:18:05.740 --> 00:18:09.120 align:start position:0% guess and there's a extended documentation<00:18:06.580> now<00:18:07.649> which<00:18:08.649> is<00:18:08.799> a<00:18:08.830> major 00:18:09.120 --> 00:18:09.130 align:start position:0% documentation now which is a major 00:18:09.130 --> 00:18:10.710 align:start position:0% documentation now which is a major improvement<00:18:09.490> to<00:18:09.820> the<00:18:09.940> documentation<00:18:10.539> we<00:18:10.659> have 00:18:10.710 --> 00:18:10.720 align:start position:0% improvement to the documentation we have 00:18:10.720 --> 00:18:11.399 align:start position:0% improvement to the documentation we have before 00:18:11.399 --> 00:18:11.409 align:start position:0% before 00:18:11.409 --> 00:18:12.810 align:start position:0% before basically<00:18:11.919> all<00:18:12.159> the<00:18:12.340> functions<00:18:12.730> are 00:18:12.810 --> 00:18:12.820 align:start position:0% basically all the functions are 00:18:12.820 --> 00:18:14.820 align:start position:0% basically all the functions are documented<00:18:13.389> and<00:18:13.600> they're<00:18:13.779> all<00:18:13.990> with<00:18:14.230> examples 00:18:14.820 --> 00:18:14.830 align:start position:0% documented and they're all with examples 00:18:14.830 --> 00:18:17.970 align:start position:0% documented and they're all with examples and<00:18:15.039> everything<00:18:15.629> so<00:18:16.629> go<00:18:17.230> to<00:18:17.289> read<00:18:17.620> the<00:18:17.769> docs 00:18:17.970 --> 00:18:17.980 align:start position:0% and everything so go to read the docs 00:18:17.980 --> 00:18:21.090 align:start position:0% and everything so go to read the docs right<00:18:18.340> now<00:18:19.059> you<00:18:19.120> have<00:18:19.330> to<00:18:19.450> go<00:18:19.600> to<00:18:19.690> the<00:18:20.100> 1.0 00:18:21.090 --> 00:18:21.100 align:start position:0% right now you have to go to the 1.0 00:18:21.100 --> 00:18:23.669 align:start position:0% right now you have to go to the 1.0 branch<00:18:21.399> if<00:18:21.610> you<00:18:21.700> want<00:18:21.879> to<00:18:21.940> see<00:18:22.029> the<00:18:22.679> 1.0 00:18:23.669 --> 00:18:23.679 align:start position:0% branch if you want to see the 1.0 00:18:23.679 --> 00:18:26.249 align:start position:0% branch if you want to see the 1.0 documentation<00:18:24.340> the<00:18:24.970> old<00:18:25.149> one<00:18:25.419> the<00:18:25.750> old<00:18:26.049> branch 00:18:26.249 --> 00:18:26.259 align:start position:0% documentation the old one the old branch 00:18:26.259 --> 00:18:30.419 align:start position:0% documentation the old one the old branch doesn't<00:18:26.470> have<00:18:26.679> any<00:18:26.889> so<00:18:27.820> go<00:18:28.090> to<00:18:28.149> E<00:18:28.659> and<00:18:29.200> 1.0<00:18:30.129> and 00:18:30.419 --> 00:18:30.429 align:start position:0% doesn't have any so go to E and 1.0 and 00:18:30.429 --> 00:18:33.749 align:start position:0% doesn't have any so go to E and 1.0 and you<00:18:30.580> can<00:18:31.350> read<00:18:32.350> the<00:18:32.740> docs<00:18:32.950> and<00:18:33.220> that's<00:18:33.399> the<00:18:33.610> end 00:18:33.749 --> 00:18:33.759 align:start position:0% you can read the docs and that's the end 00:18:33.759 --> 00:18:36.360 align:start position:0% you can read the docs and that's the end yeah 00:18:36.360 --> 00:18:36.370 align:start position:0% 00:18:36.370 --> 00:18:42.990 align:start position:0% [Applause] 00:18:42.990 --> 00:18:43.000 align:start position:0% 00:18:43.000 --> 00:18:50.579 align:start position:0% [Music]