WEBVTT Kind: captions Language: en 00:00:19.269 --> 00:00:23.910 align:start position:0% so<00:00:20.269> I<00:00:20.300> have<00:00:20.510> to<00:00:20.630> be<00:00:20.720> quick<00:00:20.929> now 00:00:23.910 --> 00:00:23.920 align:start position:0% 00:00:23.920 --> 00:00:26.950 align:start position:0% okay<00:00:24.920> so<00:00:24.980> web<00:00:25.310> switches<00:00:25.759> which<00:00:26.539> is<00:00:26.689> like<00:00:26.929> a 00:00:26.950 --> 00:00:26.960 align:start position:0% okay so web switches which is like a 00:00:26.960 --> 00:00:30.310 align:start position:0% okay so web switches which is like a very<00:00:27.849> core<00:00:28.849> important<00:00:29.330> part<00:00:29.539> of<00:00:29.779> the<00:00:30.140> whole 00:00:30.310 --> 00:00:30.320 align:start position:0% very core important part of the whole 00:00:30.320 --> 00:00:33.250 align:start position:0% very core important part of the whole ecosystem<00:00:30.410> a<00:00:30.949> lot<00:00:31.160> of<00:00:31.279> people<00:00:31.519> use<00:00:31.669> it<00:00:32.260> it's 00:00:33.250 --> 00:00:33.260 align:start position:0% ecosystem a lot of people use it it's 00:00:33.260 --> 00:00:35.350 align:start position:0% ecosystem a lot of people use it it's totally<00:00:33.500> about<00:00:33.620> me<00:00:33.830> I<00:00:34.100> build<00:00:34.880> a<00:00:35.030> content 00:00:35.350 --> 00:00:35.360 align:start position:0% totally about me I build a content 00:00:35.360 --> 00:00:37.530 align:start position:0% totally about me I build a content management<00:00:35.420> system<00:00:35.780> open<00:00:36.410> source<00:00:36.620> libraries 00:00:37.530 --> 00:00:37.540 align:start position:0% management system open source libraries 00:00:37.540 --> 00:00:41.830 align:start position:0% management system open source libraries worked<00:00:38.540> as<00:00:38.720> a<00:00:38.870> web<00:00:39.020> designer<00:00:39.350> for<00:00:39.620> like<00:00:40.840> 15 00:00:41.830 --> 00:00:41.840 align:start position:0% worked as a web designer for like 15 00:00:41.840 --> 00:00:46.990 align:start position:0% worked as a web designer for like 15 years<00:00:42.110> so<00:00:42.610> I<00:00:43.610> wrote<00:00:44.150> a<00:00:44.180> book<00:00:44.450> about<00:00:44.750> meteor<00:00:46.000> and 00:00:46.990 --> 00:00:47.000 align:start position:0% years so I wrote a book about meteor and 00:00:47.000 --> 00:00:50.080 align:start position:0% years so I wrote a book about meteor and built<00:00:47.450> the<00:00:47.870> mist<00:00:48.230> web<00:00:48.980> browser<00:00:49.310> and<00:00:49.670> the<00:00:49.880> theme 00:00:50.080 --> 00:00:50.090 align:start position:0% built the mist web browser and the theme 00:00:50.090 --> 00:00:53.260 align:start position:0% built the mist web browser and the theme wallet<00:00:50.510> how<00:00:50.720> it<00:00:50.780> is<00:00:50.930> today<00:00:51.100> now<00:00:52.100> our<00:00:52.760> team<00:00:53.060> is<00:00:53.120> a 00:00:53.260 --> 00:00:53.270 align:start position:0% wallet how it is today now our team is a 00:00:53.270 --> 00:00:57.070 align:start position:0% wallet how it is today now our team is a big<00:00:53.480> bigger<00:00:53.840> than<00:00:54.110> than<00:00:54.800> just<00:00:55.070> me<00:00:55.280> and<00:00:55.550> Alex<00:00:56.080> we 00:00:57.070 --> 00:00:57.080 align:start position:0% big bigger than than just me and Alex we 00:00:57.080 --> 00:01:00.640 align:start position:0% big bigger than than just me and Alex we also<00:00:57.230> have<00:00:57.470> RAM<00:00:57.710> Everton<00:00:58.370> and<00:00:58.750> Luca<00:00:59.750> as<00:01:00.260> part 00:01:00.640 --> 00:01:00.650 align:start position:0% also have RAM Everton and Luca as part 00:01:00.650 --> 00:01:02.470 align:start position:0% also have RAM Everton and Luca as part of<00:01:00.710> the<00:01:00.860> team<00:01:01.070> if<00:01:01.730> you're<00:01:01.910> somewhere<00:01:02.240> here 00:01:02.470 --> 00:01:02.480 align:start position:0% of the team if you're somewhere here 00:01:02.480 --> 00:01:03.700 align:start position:0% of the team if you're somewhere here maybe<00:01:02.630> you<00:01:02.810> want<00:01:02.930> to<00:01:02.990> send<00:01:03.200> up<00:01:03.350> or<00:01:03.560> you're 00:01:03.700 --> 00:01:03.710 align:start position:0% maybe you want to send up or you're 00:01:03.710 --> 00:01:05.139 align:start position:0% maybe you want to send up or you're probably<00:01:03.950> sending<00:01:04.489> already<00:01:04.729> on<00:01:04.850> the<00:01:04.939> side 00:01:05.139 --> 00:01:05.149 align:start position:0% probably sending already on the side 00:01:05.149 --> 00:01:17.469 align:start position:0% probably sending already on the side there<00:01:06.140> he<00:01:06.350> is<00:01:06.380> there's<00:01:06.679> everyone<00:01:15.609> so<00:01:16.609> and<00:01:16.909> it 00:01:17.469 --> 00:01:17.479 align:start position:0% there he is there's everyone so and it 00:01:17.479 --> 00:01:21.279 align:start position:0% there he is there's everyone so and it theorem<00:01:18.729> JavaScript<00:01:19.729> API<00:01:19.939> or<00:01:20.329> web<00:01:20.659> three.js 00:01:21.279 --> 00:01:21.289 align:start position:0% theorem JavaScript API or web three.js 00:01:21.289 --> 00:01:25.450 align:start position:0% theorem JavaScript API or web three.js how<00:01:21.560> it's<00:01:21.740> called<00:01:23.170> so<00:01:24.170> I<00:01:24.499> contributed<00:01:25.219> to<00:01:25.310> this 00:01:25.450 --> 00:01:25.460 align:start position:0% how it's called so I contributed to this 00:01:25.460 --> 00:01:27.069 align:start position:0% how it's called so I contributed to this as<00:01:25.759> you<00:01:25.909> can<00:01:26.060> see<00:01:26.240> here<00:01:26.420> this<00:01:26.539> is<00:01:26.600> kind<00:01:26.810> of<00:01:26.929> like 00:01:27.069 --> 00:01:27.079 align:start position:0% as you can see here this is kind of like 00:01:27.079 --> 00:01:29.919 align:start position:0% as you can see here this is kind of like the<00:01:27.259> graph<00:01:27.530> off<00:01:27.829> of<00:01:28.100> github<00:01:29.090> contributions 00:01:29.919 --> 00:01:29.929 align:start position:0% the graph off of github contributions 00:01:29.929 --> 00:01:31.450 align:start position:0% the graph off of github contributions I'm<00:01:30.200> there<00:01:30.439> in<00:01:30.499> the<00:01:30.619> middle<00:01:30.890> the<00:01:31.399> screen 00:01:31.450 --> 00:01:31.460 align:start position:0% I'm there in the middle the screen 00:01:31.460 --> 00:01:34.899 align:start position:0% I'm there in the middle the screen figure<00:01:32.829> but<00:01:33.829> it<00:01:33.920> was<00:01:34.039> originally<00:01:34.490> started<00:01:34.850> by 00:01:34.899 --> 00:01:34.909 align:start position:0% figure but it was originally started by 00:01:34.909 --> 00:01:37.300 align:start position:0% figure but it was originally started by Jeffrey<00:01:35.450> who<00:01:36.289> wanted<00:01:36.560> to<00:01:36.619> have<00:01:36.740> a<00:01:36.829> simple<00:01:37.189> way 00:01:37.300 --> 00:01:37.310 align:start position:0% Jeffrey who wanted to have a simple way 00:01:37.310 --> 00:01:40.029 align:start position:0% Jeffrey who wanted to have a simple way to<00:01:37.840> access<00:01:38.840> or<00:01:39.049> like<00:01:39.259> view<00:01:39.469> of<00:01:39.590> the<00:01:39.710> node<00:01:39.890> and 00:01:40.029 --> 00:01:40.039 align:start position:0% to access or like view of the node and 00:01:40.039 --> 00:01:42.639 align:start position:0% to access or like view of the node and JavaScript<00:01:40.780> writing<00:01:41.780> simple<00:01:42.109> scripts<00:01:42.439> to 00:01:42.639 --> 00:01:42.649 align:start position:0% JavaScript writing simple scripts to 00:01:42.649 --> 00:01:44.830 align:start position:0% JavaScript writing simple scripts to interact<00:01:43.130> with<00:01:43.310> the<00:01:43.460> node<00:01:43.670> building<00:01:44.569> little 00:01:44.830 --> 00:01:44.840 align:start position:0% interact with the node building little 00:01:44.840 --> 00:01:48.069 align:start position:0% interact with the node building little dabs<00:01:45.100> later<00:01:46.100> then<00:01:46.399> joined<00:01:46.819> Marek<00:01:47.329> he<00:01:47.810> took 00:01:48.069 --> 00:01:48.079 align:start position:0% dabs later then joined Marek he took 00:01:48.079 --> 00:01:50.910 align:start position:0% dabs later then joined Marek he took over<00:01:48.289> the<00:01:48.499> project<00:01:48.710> and<00:01:49.280> basically<00:01:49.899> built 00:01:50.910 --> 00:01:50.920 align:start position:0% over the project and basically built 00:01:50.920 --> 00:01:53.379 align:start position:0% over the project and basically built most<00:01:51.920> part<00:01:52.249> of<00:01:52.429> it<00:01:52.549> what<00:01:52.729> is<00:01:52.850> currently<00:01:53.299> the 00:01:53.379 --> 00:01:53.389 align:start position:0% most part of it what is currently the 00:01:53.389 --> 00:01:54.399 align:start position:0% most part of it what is currently the web<00:01:53.780> three.js 00:01:54.399 --> 00:01:54.409 align:start position:0% web three.js 00:01:54.409 --> 00:01:58.590 align:start position:0% web three.js I<00:01:54.619> joined<00:01:55.159> like<00:01:55.630> almost<00:01:56.630> two<00:01:56.840> years<00:01:57.109> ago<00:01:57.170> and 00:01:58.590 --> 00:01:58.600 align:start position:0% I joined like almost two years ago and 00:01:58.600 --> 00:02:01.569 align:start position:0% I joined like almost two years ago and helped<00:01:59.600> refactoring<00:02:00.319> a<00:02:00.499> lot<00:02:00.679> of<00:02:00.829> this<00:02:01.069> under 00:02:01.569 --> 00:02:01.579 align:start position:0% helped refactoring a lot of this under 00:02:01.579 --> 00:02:03.639 align:start position:0% helped refactoring a lot of this under the<00:02:01.639> hood<00:02:01.850> code<00:02:02.149> improving<00:02:02.780> the<00:02:02.899> API<00:02:03.229> and 00:02:03.639 --> 00:02:03.649 align:start position:0% the hood code improving the API and 00:02:03.649 --> 00:02:07.629 align:start position:0% the hood code improving the API and adding<00:02:04.069> additions<00:02:04.579> I<00:02:05.709> wrote<00:02:06.709> or<00:02:06.950> restructured 00:02:07.629 --> 00:02:07.639 align:start position:0% adding additions I wrote or restructured 00:02:07.639 --> 00:02:09.790 align:start position:0% adding additions I wrote or restructured the<00:02:07.789> RPC<00:02:08.090> endpoints<00:02:08.990> to<00:02:09.110> make<00:02:09.530> them<00:02:09.680> more 00:02:09.790 --> 00:02:09.800 align:start position:0% the RPC endpoints to make them more 00:02:09.800 --> 00:02:12.670 align:start position:0% the RPC endpoints to make them more readable<00:02:10.130> understandable<00:02:10.400> and 00:02:12.670 --> 00:02:12.680 align:start position:0% readable understandable and 00:02:12.680 --> 00:02:14.770 align:start position:0% readable understandable and basically<00:02:13.459> because<00:02:13.700> mark<00:02:14.150> is<00:02:14.269> now<00:02:14.420> part<00:02:14.689> of 00:02:14.770 --> 00:02:14.780 align:start position:0% basically because mark is now part of 00:02:14.780 --> 00:02:17.009 align:start position:0% basically because mark is now part of its<00:02:15.019> core<00:02:15.290> and<00:02:15.590> working<00:02:15.920> on<00:02:16.010> parity<00:02:16.340> I'm 00:02:17.009 --> 00:02:17.019 align:start position:0% its core and working on parity I'm 00:02:17.019 --> 00:02:21.009 align:start position:0% its core and working on parity I'm maintaining<00:02:18.019> web<00:02:18.170> 3j<00:02:18.620> s<00:02:19.540> we<00:02:20.540> have<00:02:20.629> also<00:02:20.780> other 00:02:21.009 --> 00:02:21.019 align:start position:0% maintaining web 3j s we have also other 00:02:21.019 --> 00:02:25.929 align:start position:0% maintaining web 3j s we have also other contributors<00:02:21.700> Alex<00:02:22.700> there<00:02:22.939> too<00:02:24.400> and<00:02:25.400> a<00:02:25.760> lot<00:02:25.879> of 00:02:25.929 --> 00:02:25.939 align:start position:0% contributors Alex there too and a lot of 00:02:25.939 --> 00:02:30.460 align:start position:0% contributors Alex there too and a lot of others<00:02:26.269> actually<00:02:26.510> who<00:02:27.260> also<00:02:27.409> helped<00:02:27.829> out<00:02:29.470> so 00:02:30.460 --> 00:02:30.470 align:start position:0% others actually who also helped out so 00:02:30.470 --> 00:02:33.449 align:start position:0% others actually who also helped out so the<00:02:30.650> main<00:02:30.859> reason<00:02:30.890> of<00:02:31.310> web<00:02:31.519> 3<00:02:31.700> JS<00:02:31.970> is<00:02:32.239> because 00:02:33.449 --> 00:02:33.459 align:start position:0% the main reason of web 3 JS is because 00:02:33.459 --> 00:02:36.160 align:start position:0% the main reason of web 3 JS is because the<00:02:34.459> node<00:02:34.700> only<00:02:34.909> understand<00:02:35.510> understands 00:02:36.160 --> 00:02:36.170 align:start position:0% the node only understand understands 00:02:36.170 --> 00:02:39.309 align:start position:0% the node only understand understands JSON<00:02:36.620> RPC<00:02:36.769> so<00:02:37.730> basically<00:02:38.239> what<00:02:38.540> JavaScript<00:02:39.079> or 00:02:39.309 --> 00:02:39.319 align:start position:0% JSON RPC so basically what JavaScript or 00:02:39.319 --> 00:02:41.170 align:start position:0% JSON RPC so basically what JavaScript or what<00:02:39.500> web<00:02:39.650> three.js<00:02:40.040> does<00:02:40.430> is<00:02:40.730> it<00:02:40.939> translates 00:02:41.170 --> 00:02:41.180 align:start position:0% what web three.js does is it translates 00:02:41.180 --> 00:02:45.759 align:start position:0% what web three.js does is it translates this<00:02:41.810> JSON<00:02:42.260> RPC<00:02:42.700> code<00:02:43.989> calls<00:02:44.989> where<00:02:45.349> you<00:02:45.500> send 00:02:45.759 --> 00:02:45.769 align:start position:0% this JSON RPC code calls where you send 00:02:45.769 --> 00:02:47.949 align:start position:0% this JSON RPC code calls where you send a<00:02:45.889> JSON<00:02:46.250> object<00:02:46.400> into<00:02:47.329> something<00:02:47.810> you<00:02:47.930> can 00:02:47.949 --> 00:02:47.959 align:start position:0% a JSON object into something you can 00:02:47.959 --> 00:02:50.530 align:start position:0% a JSON object into something you can actually<00:02:48.440> easily<00:02:48.590> use<00:02:48.920> in<00:02:49.069> JavaScript<00:02:49.700> and<00:02:49.909> it 00:02:50.530 --> 00:02:50.540 align:start position:0% actually easily use in JavaScript and it 00:02:50.540 --> 00:02:53.500 align:start position:0% actually easily use in JavaScript and it looks<00:02:50.780> like<00:02:51.609> calling<00:02:52.609> simple<00:02:52.940> JavaScript 00:02:53.500 --> 00:02:53.510 align:start position:0% looks like calling simple JavaScript 00:02:53.510 --> 00:02:57.789 align:start position:0% looks like calling simple JavaScript objects<00:02:55.030> the<00:02:56.030> evm<00:02:56.450> itself<00:02:56.870> only<00:02:57.139> understands 00:02:57.789 --> 00:02:57.799 align:start position:0% objects the evm itself only understands 00:02:57.799 --> 00:03:02.500 align:start position:0% objects the evm itself only understands pipe<00:02:58.010> code<00:02:58.340> and<00:03:00.730> that's<00:03:01.730> not<00:03:02.000> easy<00:03:02.239> for 00:03:02.500 --> 00:03:02.510 align:start position:0% pipe code and that's not easy for 00:03:02.510 --> 00:03:04.089 align:start position:0% pipe code and that's not easy for JavaScript<00:03:03.019> developer<00:03:03.500> and<00:03:03.650> that's<00:03:03.799> probably 00:03:04.089 --> 00:03:04.099 align:start position:0% JavaScript developer and that's probably 00:03:04.099 --> 00:03:06.849 align:start position:0% JavaScript developer and that's probably not<00:03:04.250> easy<00:03:04.459> for<00:03:04.670> most<00:03:04.790> people<00:03:05.329> and<00:03:05.650> it's<00:03:06.650> not 00:03:06.849 --> 00:03:06.859 align:start position:0% not easy for most people and it's not 00:03:06.859 --> 00:03:10.449 align:start position:0% not easy for most people and it's not really<00:03:07.069> human<00:03:07.519> readable<00:03:08.739> so<00:03:09.739> basically<00:03:10.159> what 00:03:10.449 --> 00:03:10.459 align:start position:0% really human readable so basically what 00:03:10.459 --> 00:03:13.929 align:start position:0% really human readable so basically what web<00:03:10.639> dj's<00:03:11.060> helps<00:03:11.569> is<00:03:11.720> translating<00:03:12.939> these 00:03:13.929 --> 00:03:13.939 align:start position:0% web dj's helps is translating these 00:03:13.939 --> 00:03:16.390 align:start position:0% web dj's helps is translating these function<00:03:14.450> names<00:03:14.689> through<00:03:15.590> what<00:03:15.950> we<00:03:16.099> call<00:03:16.129> the 00:03:16.390 --> 00:03:16.400 align:start position:0% function names through what we call the 00:03:16.400 --> 00:03:19.710 align:start position:0% function names through what we call the ABI<00:03:16.910> to<00:03:17.120> the<00:03:17.660> application<00:03:18.199> binary<00:03:18.440> interface 00:03:19.710 --> 00:03:19.720 align:start position:0% ABI to the application binary interface 00:03:19.720 --> 00:03:22.869 align:start position:0% ABI to the application binary interface to<00:03:20.720> something<00:03:21.139> which<00:03:21.290> DVM<00:03:21.919> understands<00:03:22.669> and 00:03:22.869 --> 00:03:22.879 align:start position:0% to something which DVM understands and 00:03:22.879 --> 00:03:28.390 align:start position:0% to something which DVM understands and to<00:03:23.780> do<00:03:23.930> that<00:03:24.139> you<00:03:24.739> basically<00:03:24.919> take<00:03:25.549> the<00:03:27.400> you 00:03:28.390 --> 00:03:28.400 align:start position:0% to do that you basically take the you 00:03:28.400 --> 00:03:31.330 align:start position:0% to do that you basically take the you take<00:03:28.609> the<00:03:28.849> function<00:03:29.389> the<00:03:30.199> transfer<00:03:30.709> including 00:03:31.330 --> 00:03:31.340 align:start position:0% take the function the transfer including 00:03:31.340 --> 00:03:33.430 align:start position:0% take the function the transfer including its<00:03:31.699> parameters<00:03:32.239> you<00:03:32.510> shall<00:03:32.750> three<00:03:33.049> that<00:03:33.260> and 00:03:33.430 --> 00:03:33.440 align:start position:0% its parameters you shall three that and 00:03:33.440 --> 00:03:35.080 align:start position:0% its parameters you shall three that and you<00:03:33.500> take<00:03:33.680> the<00:03:33.799> first<00:03:33.829> four<00:03:34.220> bytes<00:03:34.430> and<00:03:34.849> this 00:03:35.080 --> 00:03:35.090 align:start position:0% you take the first four bytes and this 00:03:35.090 --> 00:03:37.839 align:start position:0% you take the first four bytes and this becomes<00:03:35.780> the<00:03:35.959> function<00:03:36.139> name<00:03:36.560> and<00:03:36.859> then<00:03:37.699> you 00:03:37.839 --> 00:03:37.849 align:start position:0% becomes the function name and then you 00:03:37.849 --> 00:03:39.640 align:start position:0% becomes the function name and then you add<00:03:38.030> the<00:03:38.209> first<00:03:38.449> parameter<00:03:38.750> and<00:03:39.169> you<00:03:39.319> add<00:03:39.440> the 00:03:39.640 --> 00:03:39.650 align:start position:0% add the first parameter and you add the 00:03:39.650 --> 00:03:41.949 align:start position:0% add the first parameter and you add the second<00:03:40.010> parameter<00:03:40.250> in<00:03:40.940> this<00:03:41.479> you<00:03:41.659> send<00:03:41.870> over 00:03:41.949 --> 00:03:41.959 align:start position:0% second parameter in this you send over 00:03:41.959 --> 00:03:45.550 align:start position:0% second parameter in this you send over JSON<00:03:42.440> RPC<00:03:42.560> to<00:03:43.159> the<00:03:43.310> to<00:03:44.030> the<00:03:44.150> node<00:03:44.359> and<00:03:44.690> this<00:03:45.319> way 00:03:45.550 --> 00:03:45.560 align:start position:0% JSON RPC to the to the node and this way 00:03:45.560 --> 00:03:47.740 align:start position:0% JSON RPC to the to the node and this way the<00:03:45.829> node<00:03:46.040> understands<00:03:46.819> what<00:03:47.030> to<00:03:47.180> do<00:03:47.329> in<00:03:47.599> the 00:03:47.740 --> 00:03:47.750 align:start position:0% the node understands what to do in the 00:03:47.750 --> 00:03:51.069 align:start position:0% the node understands what to do in the smart<00:03:48.019> contract<00:03:48.199> and<00:03:49.209> basically<00:03:50.209> web<00:03:50.870> bridge 00:03:51.069 --> 00:03:51.079 align:start position:0% smart contract and basically web bridge 00:03:51.079 --> 00:03:52.960 align:start position:0% smart contract and basically web bridge is<00:03:51.379> in<00:03:51.620> the<00:03:51.769> contract<00:03:52.099> object<00:03:52.519> does<00:03:52.729> all<00:03:52.940> of 00:03:52.960 --> 00:03:52.970 align:start position:0% is in the contract object does all of 00:03:52.970 --> 00:03:55.000 align:start position:0% is in the contract object does all of this<00:03:53.239> for<00:03:53.479> you<00:03:53.599> so<00:03:54.229> you<00:03:54.290> only<00:03:54.530> have<00:03:54.709> to<00:03:54.829> deal 00:03:55.000 --> 00:03:55.010 align:start position:0% this for you so you only have to deal 00:03:55.010 --> 00:03:57.189 align:start position:0% this for you so you only have to deal with<00:03:55.190> JavaScript<00:03:56.120> object<00:03:56.540> they<00:03:56.750> look<00:03:56.959> like 00:03:57.189 --> 00:03:57.199 align:start position:0% with JavaScript object they look like 00:03:57.199 --> 00:04:00.099 align:start position:0% with JavaScript object they look like normal<00:03:58.010> standard<00:03:58.549> functions<00:03:59.000> but<00:03:59.720> under<00:04:00.019> the 00:04:00.099 --> 00:04:00.109 align:start position:0% normal standard functions but under the 00:04:00.109 --> 00:04:03.759 align:start position:0% normal standard functions but under the hood<00:04:00.260> it<00:04:00.409> translated<00:04:00.919> to<00:04:01.510> this<00:04:02.510> ABI<00:04:02.840> in 00:04:03.759 --> 00:04:03.769 align:start position:0% hood it translated to this ABI in 00:04:03.769 --> 00:04:06.270 align:start position:0% hood it translated to this ABI in webpages<00:04:04.370> you<00:04:04.579> also<00:04:04.729> have<00:04:04.940> a<00:04:04.970> bunch<00:04:05.180> of<00:04:05.299> other 00:04:06.270 --> 00:04:06.280 align:start position:0% webpages you also have a bunch of other 00:04:06.280 --> 00:04:09.339 align:start position:0% webpages you also have a bunch of other tools<00:04:07.280> and<00:04:07.760> utility<00:04:08.329> functions<00:04:08.810> you<00:04:09.079> can<00:04:09.199> use 00:04:09.339 --> 00:04:09.349 align:start position:0% tools and utility functions you can use 00:04:09.349 --> 00:04:11.500 align:start position:0% tools and utility functions you can use in<00:04:09.470> your<00:04:09.500> application<00:04:09.879> but<00:04:10.879> because<00:04:11.209> it<00:04:11.359> crew 00:04:11.500 --> 00:04:11.510 align:start position:0% in your application but because it crew 00:04:11.510 --> 00:04:13.479 align:start position:0% in your application but because it crew over<00:04:11.659> the<00:04:11.900> time<00:04:12.169> it's<00:04:12.530> quite<00:04:12.739> messy<00:04:13.069> right<00:04:13.430> now 00:04:13.479 --> 00:04:13.489 align:start position:0% over the time it's quite messy right now 00:04:13.489 --> 00:04:16.509 align:start position:0% over the time it's quite messy right now it's<00:04:14.000> it's<00:04:14.449> it<00:04:14.870> grows<00:04:15.379> it<00:04:15.709> could<00:04:16.010> just<00:04:16.310> over 00:04:16.509 --> 00:04:16.519 align:start position:0% it's it's it grows it could just over 00:04:16.519 --> 00:04:18.009 align:start position:0% it's it's it grows it could just over time<00:04:16.729> with<00:04:16.909> a<00:04:17.000> lot<00:04:17.120> of<00:04:17.150> people<00:04:17.510> influencing 00:04:18.009 --> 00:04:18.019 align:start position:0% time with a lot of people influencing 00:04:18.019 --> 00:04:20.560 align:start position:0% time with a lot of people influencing the<00:04:18.109> decisions<00:04:18.620> and<00:04:19.090> that's<00:04:20.090> why<00:04:20.329> there's 00:04:20.560 --> 00:04:20.570 align:start position:0% the decisions and that's why there's 00:04:20.570 --> 00:04:23.370 align:start position:0% the decisions and that's why there's time<00:04:20.840> for<00:04:20.870> new<00:04:21.260> we're<00:04:21.709> three<00:04:21.919> chairs 00:04:23.370 --> 00:04:23.380 align:start position:0% time for new we're three chairs 00:04:23.380 --> 00:04:30.100 align:start position:0% time for new we're three chairs so<00:04:24.380> the<00:04:24.680> whole<00:04:24.830> idea<00:04:24.860> is<00:04:25.250> that<00:04:25.370> it's<00:04:26.560> um<00:04:29.110> like 00:04:30.100 --> 00:04:30.110 align:start position:0% so the whole idea is that it's um like 00:04:30.110 --> 00:04:32.200 align:start position:0% so the whole idea is that it's um like the<00:04:30.440> way<00:04:30.560> it<00:04:30.710> grew<00:04:30.950> it<00:04:31.310> became<00:04:31.520> to<00:04:31.880> a<00:04:31.910> point 00:04:32.200 --> 00:04:32.210 align:start position:0% the way it grew it became to a point 00:04:32.210 --> 00:04:34.360 align:start position:0% the way it grew it became to a point which<00:04:32.480> it's<00:04:32.900> influenced<00:04:33.590> by<00:04:33.710> so<00:04:33.890> many<00:04:34.070> sites 00:04:34.360 --> 00:04:34.370 align:start position:0% which it's influenced by so many sites 00:04:34.370 --> 00:04:36.460 align:start position:0% which it's influenced by so many sites that<00:04:34.610> it's<00:04:34.850> not<00:04:35.030> really<00:04:35.420> easy<00:04:35.750> to<00:04:35.930> use<00:04:36.230> for 00:04:36.460 --> 00:04:36.470 align:start position:0% that it's not really easy to use for 00:04:36.470 --> 00:04:40.000 align:start position:0% that it's not really easy to use for JavaScript<00:04:36.980> developers<00:04:37.490> and<00:04:38.920> there<00:04:39.920> are 00:04:40.000 --> 00:04:40.010 align:start position:0% JavaScript developers and there are 00:04:40.010 --> 00:04:41.170 align:start position:0% JavaScript developers and there are certain<00:04:40.310> parts<00:04:40.430> which<00:04:40.670> actually<00:04:41.000> doesn't 00:04:41.170 --> 00:04:41.180 align:start position:0% certain parts which actually doesn't 00:04:41.180 --> 00:04:43.660 align:start position:0% certain parts which actually doesn't don't<00:04:41.660> make<00:04:41.840> sense<00:04:42.140> as<00:04:42.380> a<00:04:42.410> as<00:04:43.190> a<00:04:43.250> JavaScript 00:04:43.660 --> 00:04:43.670 align:start position:0% don't make sense as a as a JavaScript 00:04:43.670 --> 00:04:48.010 align:start position:0% don't make sense as a as a JavaScript library<00:04:44.360> and<00:04:46.000> it<00:04:47.000> became<00:04:47.330> clear<00:04:47.630> to<00:04:47.660> me<00:04:47.750> that 00:04:48.010 --> 00:04:48.020 align:start position:0% library and it became clear to me that 00:04:48.020 --> 00:04:49.690 align:start position:0% library and it became clear to me that this<00:04:48.110> needs<00:04:48.350> to<00:04:48.440> have<00:04:48.860> a<00:04:48.890> refactor<00:04:49.430> at<00:04:49.520> some 00:04:49.690 --> 00:04:49.700 align:start position:0% this needs to have a refactor at some 00:04:49.700 --> 00:04:51.790 align:start position:0% this needs to have a refactor at some point<00:04:50.000> and<00:04:50.300> the<00:04:50.570> community<00:04:50.960> also<00:04:51.170> asks<00:04:51.650> for 00:04:51.790 --> 00:04:51.800 align:start position:0% point and the community also asks for 00:04:51.800 --> 00:04:53.680 align:start position:0% point and the community also asks for other<00:04:52.010> features<00:04:52.490> and<00:04:52.790> things<00:04:53.090> and<00:04:53.450> want<00:04:53.630> to 00:04:53.680 --> 00:04:53.690 align:start position:0% other features and things and want to 00:04:53.690 --> 00:04:55.780 align:start position:0% other features and things and want to have<00:04:53.840> things<00:04:54.140> changed<00:04:54.470> and<00:04:54.890> that's<00:04:55.370> basically 00:04:55.780 --> 00:04:55.790 align:start position:0% have things changed and that's basically 00:04:55.790 --> 00:04:57.730 align:start position:0% have things changed and that's basically what<00:04:56.030> I'm<00:04:56.150> right<00:04:56.390> now<00:04:56.540> working<00:04:56.810> on<00:04:57.050> is<00:04:57.380> like 00:04:57.730 --> 00:04:57.740 align:start position:0% what I'm right now working on is like 00:04:57.740 --> 00:04:59.620 align:start position:0% what I'm right now working on is like making<00:04:58.130> the<00:04:58.280> new<00:04:58.430> website<00:04:58.820> you<00:04:59.090> were<00:04:59.420> three 00:04:59.620 --> 00:04:59.630 align:start position:0% making the new website you were three 00:04:59.630 --> 00:05:02.080 align:start position:0% making the new website you were three chairs<00:04:59.870> so<00:05:00.620> it<00:05:00.740> will<00:05:00.980> be<00:05:01.160> a<00:05:01.190> refactor<00:05:01.790> it's<00:05:01.910> not 00:05:02.080 --> 00:05:02.090 align:start position:0% chairs so it will be a refactor it's not 00:05:02.090 --> 00:05:04.660 align:start position:0% chairs so it will be a refactor it's not built<00:05:02.390> from<00:05:02.540> scratch<00:05:02.870> and<00:05:03.340> it<00:05:04.340> will<00:05:04.520> not 00:05:04.660 --> 00:05:04.670 align:start position:0% built from scratch and it will not 00:05:04.670 --> 00:05:07.540 align:start position:0% built from scratch and it will not completely<00:05:05.120> change<00:05:05.570> but<00:05:06.230> it<00:05:06.680> will<00:05:06.950> have<00:05:07.190> core 00:05:07.540 --> 00:05:07.550 align:start position:0% completely change but it will have core 00:05:07.550 --> 00:05:10.750 align:start position:0% completely change but it will have core pieces<00:05:08.330> changed<00:05:09.050> and<00:05:09.370> probably<00:05:10.370> one<00:05:10.520> of<00:05:10.550> the 00:05:10.750 --> 00:05:10.760 align:start position:0% pieces changed and probably one of the 00:05:10.760 --> 00:05:12.940 align:start position:0% pieces changed and probably one of the main<00:05:11.000> one<00:05:11.270> is<00:05:11.540> that<00:05:11.570> the<00:05:12.170> communication<00:05:12.830> will 00:05:12.940 --> 00:05:12.950 align:start position:0% main one is that the communication will 00:05:12.950 --> 00:05:16.360 align:start position:0% main one is that the communication will be<00:05:12.980> socket<00:05:13.430> based<00:05:14.080> so<00:05:15.080> currently<00:05:15.890> everything 00:05:16.360 --> 00:05:16.370 align:start position:0% be socket based so currently everything 00:05:16.370 --> 00:05:18.400 align:start position:0% be socket based so currently everything is<00:05:16.490> done<00:05:16.700> in<00:05:16.850> HTTP<00:05:17.300> requests<00:05:17.840> and<00:05:17.990> this<00:05:18.170> will 00:05:18.400 --> 00:05:18.410 align:start position:0% is done in HTTP requests and this will 00:05:18.410 --> 00:05:21.040 align:start position:0% is done in HTTP requests and this will still<00:05:18.680> work<00:05:18.950> but<00:05:19.310> they<00:05:20.030> will<00:05:20.210> not<00:05:20.330> work<00:05:20.840> for 00:05:21.040 --> 00:05:21.050 align:start position:0% still work but they will not work for 00:05:21.050 --> 00:05:25.150 align:start position:0% still work but they will not work for everything<00:05:21.790> because<00:05:22.790> of<00:05:23.180> the<00:05:23.690> nature<00:05:24.050> of<00:05:24.160> what 00:05:25.150 --> 00:05:25.160 align:start position:0% everything because of the nature of what 00:05:25.160 --> 00:05:27.190 align:start position:0% everything because of the nature of what we<00:05:25.610> do<00:05:25.820> which<00:05:26.060> I<00:05:26.090> will<00:05:26.300> show<00:05:26.420> later<00:05:26.450> that<00:05:27.080> we 00:05:27.190 --> 00:05:27.200 align:start position:0% we do which I will show later that we 00:05:27.200 --> 00:05:28.840 align:start position:0% we do which I will show later that we have<00:05:27.350> subscriptions<00:05:27.770> and<00:05:28.280> subscriptions 00:05:28.840 --> 00:05:28.850 align:start position:0% have subscriptions and subscriptions 00:05:28.850 --> 00:05:31.060 align:start position:0% have subscriptions and subscriptions need<00:05:29.090> sockets<00:05:29.570> so<00:05:30.140> you<00:05:30.200> can<00:05:30.440> either<00:05:30.620> use<00:05:30.890> the 00:05:31.060 --> 00:05:31.070 align:start position:0% need sockets so you can either use the 00:05:31.070 --> 00:05:33.250 align:start position:0% need sockets so you can either use the IPC<00:05:31.460> socket<00:05:31.910> which<00:05:32.450> is<00:05:32.600> like<00:05:32.810> your<00:05:33.020> local 00:05:33.250 --> 00:05:33.260 align:start position:0% IPC socket which is like your local 00:05:33.260 --> 00:05:36.070 align:start position:0% IPC socket which is like your local socket<00:05:33.800> you<00:05:34.010> use<00:05:34.730> to<00:05:34.970> talk<00:05:35.210> to<00:05:35.360> your<00:05:35.480> note<00:05:35.930> on 00:05:36.070 --> 00:05:36.080 align:start position:0% socket you use to talk to your note on 00:05:36.080 --> 00:05:39.540 align:start position:0% socket you use to talk to your note on your<00:05:36.110> computer<00:05:36.650> or<00:05:36.860> you<00:05:37.310> can<00:05:37.460> use<00:05:37.520> WebSockets 00:05:39.540 --> 00:05:39.550 align:start position:0% your computer or you can use WebSockets 00:05:39.550 --> 00:05:42.400 align:start position:0% your computer or you can use WebSockets so<00:05:40.550> before<00:05:41.000> we<00:05:41.240> had<00:05:41.420> this<00:05:41.630> concept<00:05:42.110> of<00:05:42.290> the 00:05:42.400 --> 00:05:42.410 align:start position:0% so before we had this concept of the 00:05:42.410 --> 00:05:44.380 align:start position:0% so before we had this concept of the filter<00:05:42.800> and<00:05:43.070> this<00:05:43.640> concept<00:05:44.000> was<00:05:44.180> rather 00:05:44.380 --> 00:05:44.390 align:start position:0% filter and this concept was rather 00:05:44.390 --> 00:05:46.960 align:start position:0% filter and this concept was rather confusing<00:05:45.140> for<00:05:45.350> many<00:05:45.500> people<00:05:45.950> so<00:05:46.610> basically 00:05:46.960 --> 00:05:46.970 align:start position:0% confusing for many people so basically 00:05:46.970 --> 00:05:49.380 align:start position:0% confusing for many people so basically what<00:05:47.300> you<00:05:47.690> would<00:05:47.870> have<00:05:47.990> created<00:05:48.200> a<00:05:48.500> filter 00:05:49.380 --> 00:05:49.390 align:start position:0% what you would have created a filter 00:05:49.390 --> 00:05:51.910 align:start position:0% what you would have created a filter watching<00:05:50.390> for<00:05:50.690> lock<00:05:51.020> events<00:05:51.530> and<00:05:51.710> then<00:05:51.830> you 00:05:51.910 --> 00:05:51.920 align:start position:0% watching for lock events and then you 00:05:51.920 --> 00:05:53.680 align:start position:0% watching for lock events and then you watch<00:05:52.130> it<00:05:52.400> and<00:05:52.580> then<00:05:52.700> you<00:05:52.850> get<00:05:52.970> resolved<00:05:53.540> or 00:05:53.680 --> 00:05:53.690 align:start position:0% watch it and then you get resolved or 00:05:53.690 --> 00:05:56.230 align:start position:0% watch it and then you get resolved or the<00:05:53.780> lock<00:05:53.990> at<00:05:54.140> some<00:05:54.320> point<00:05:54.620> but<00:05:55.580> this<00:05:56.000> whole 00:05:56.230 --> 00:05:56.240 align:start position:0% the lock at some point but this whole 00:05:56.240 --> 00:05:58.750 align:start position:0% the lock at some point but this whole like<00:05:56.450> it's<00:05:57.290> not<00:05:57.440> very<00:05:57.710> descriptive<00:05:58.100> and<00:05:58.610> it's 00:05:58.750 --> 00:05:58.760 align:start position:0% like it's not very descriptive and it's 00:05:58.760 --> 00:06:01.300 align:start position:0% like it's not very descriptive and it's also<00:05:58.940> in<00:05:59.600> the<00:05:59.660> JavaScript<00:06:00.200> world<00:06:00.410> not<00:06:00.650> comment 00:06:01.300 --> 00:06:01.310 align:start position:0% also in the JavaScript world not comment 00:06:01.310 --> 00:06:04.630 align:start position:0% also in the JavaScript world not comment to<00:06:01.400> do<00:06:01.520> it<00:06:01.640> this<00:06:01.790> way<00:06:02.030> and<00:06:03.010> it<00:06:04.010> confused<00:06:04.490> people 00:06:04.630 --> 00:06:04.640 align:start position:0% to do it this way and it confused people 00:06:04.640 --> 00:06:06.370 align:start position:0% to do it this way and it confused people because<00:06:05.030> they<00:06:05.180> thought<00:06:05.360> eh<00:06:05.540> I<00:06:05.570> can<00:06:05.870> filter<00:06:06.110> for 00:06:06.370 --> 00:06:06.380 align:start position:0% because they thought eh I can filter for 00:06:06.380 --> 00:06:08.710 align:start position:0% because they thought eh I can filter for a<00:06:06.410> transaction<00:06:07.010> for<00:06:07.790> an<00:06:07.910> address<00:06:08.120> and<00:06:08.510> I<00:06:08.570> get 00:06:08.710 --> 00:06:08.720 align:start position:0% a transaction for an address and I get 00:06:08.720 --> 00:06:10.210 align:start position:0% a transaction for an address and I get all<00:06:08.840> the<00:06:08.930> transaction<00:06:09.470> of<00:06:09.620> this<00:06:09.800> address 00:06:10.210 --> 00:06:10.220 align:start position:0% all the transaction of this address 00:06:10.220 --> 00:06:12.580 align:start position:0% all the transaction of this address there<00:06:10.730> was<00:06:10.910> also<00:06:11.240> my<00:06:11.420> first<00:06:11.690> understanding<00:06:12.440> of 00:06:12.580 --> 00:06:12.590 align:start position:0% there was also my first understanding of 00:06:12.590 --> 00:06:15.610 align:start position:0% there was also my first understanding of that<00:06:12.770> function<00:06:14.020> but<00:06:15.020> that's<00:06:15.230> kind<00:06:15.500> of<00:06:15.560> like 00:06:15.610 --> 00:06:15.620 align:start position:0% that function but that's kind of like 00:06:15.620 --> 00:06:18.100 align:start position:0% that function but that's kind of like wrong<00:06:16.070> right<00:06:16.430> it's<00:06:16.760> it's<00:06:17.090> not<00:06:17.570> clear<00:06:17.900> and 00:06:18.100 --> 00:06:18.110 align:start position:0% wrong right it's it's not clear and 00:06:18.110 --> 00:06:19.930 align:start position:0% wrong right it's it's not clear and makes<00:06:18.320> no<00:06:18.470> sense<00:06:18.710> like<00:06:18.860> this<00:06:19.010> so<00:06:19.370> the<00:06:19.490> real<00:06:19.700> way 00:06:19.930 --> 00:06:19.940 align:start position:0% makes no sense like this so the real way 00:06:19.940 --> 00:06:21.700 align:start position:0% makes no sense like this so the real way of<00:06:19.970> doing<00:06:20.360> this<00:06:20.540> actually<00:06:20.780> is<00:06:21.020> subscribing<00:06:21.620> to 00:06:21.700 --> 00:06:21.710 align:start position:0% of doing this actually is subscribing to 00:06:21.710 --> 00:06:24.160 align:start position:0% of doing this actually is subscribing to something<00:06:22.130> and<00:06:22.310> with<00:06:23.090> the<00:06:23.240> new<00:06:23.420> locks<00:06:23.810> it's 00:06:24.160 --> 00:06:24.170 align:start position:0% something and with the new locks it's 00:06:24.170 --> 00:06:25.780 align:start position:0% something and with the new locks it's actually<00:06:24.590> even<00:06:24.740> technically<00:06:25.310> working<00:06:25.520> as<00:06:25.760> a 00:06:25.780 --> 00:06:25.790 align:start position:0% actually even technically working as a 00:06:25.790 --> 00:06:27.550 align:start position:0% actually even technically working as a subscription<00:06:26.210> so<00:06:27.050> you<00:06:27.110> basically<00:06:27.440> just 00:06:27.550 --> 00:06:27.560 align:start position:0% subscription so you basically just 00:06:27.560 --> 00:06:30.100 align:start position:0% subscription so you basically just subscribe<00:06:28.220> to<00:06:28.250> locks<00:06:28.640> you<00:06:28.820> pass<00:06:29.000> in<00:06:29.210> another 00:06:30.100 --> 00:06:30.110 align:start position:0% subscribe to locks you pass in another 00:06:30.110 --> 00:06:32.290 align:start position:0% subscribe to locks you pass in another options<00:06:30.590> object<00:06:30.830> which<00:06:31.400> can<00:06:31.640> be<00:06:31.729> the<00:06:31.880> topics 00:06:32.290 --> 00:06:32.300 align:start position:0% options object which can be the topics 00:06:32.300 --> 00:06:34.659 align:start position:0% options object which can be the topics in<00:06:32.540> this<00:06:32.720> case<00:06:32.960> and<00:06:33.260> then<00:06:33.800> you<00:06:33.950> just<00:06:34.190> wait<00:06:34.460> for 00:06:34.659 --> 00:06:34.669 align:start position:0% in this case and then you just wait for 00:06:34.669 --> 00:06:39.520 align:start position:0% in this case and then you just wait for the<00:06:34.850> data<00:06:35.090> changes<00:06:35.419> to 00:06:39.520 --> 00:06:39.530 align:start position:0% 00:06:39.530 --> 00:06:41.770 align:start position:0% well<00:06:40.370> three<00:06:40.550> J's<00:06:40.760> right<00:06:41.030> now<00:06:41.150> is<00:06:41.300> like<00:06:41.450> a<00:06:41.480> big 00:06:41.770 --> 00:06:41.780 align:start position:0% well three J's right now is like a big 00:06:41.780 --> 00:06:45.280 align:start position:0% well three J's right now is like a big bulky<00:06:42.850> library<00:06:43.850> you<00:06:44.180> have<00:06:44.360> to<00:06:44.600> use<00:06:44.840> if<00:06:45.170> you 00:06:45.280 --> 00:06:45.290 align:start position:0% bulky library you have to use if you 00:06:45.290 --> 00:06:48.070 align:start position:0% bulky library you have to use if you want<00:06:45.470> to<00:06:45.530> use<00:06:45.710> web<00:06:45.890> switches<00:06:46.340> in<00:06:46.610> the<00:06:47.080> future 00:06:48.070 --> 00:06:48.080 align:start position:0% want to use web switches in the future 00:06:48.080 --> 00:06:50.680 align:start position:0% want to use web switches in the future this<00:06:48.440> will<00:06:48.500> be<00:06:48.890> more<00:06:49.240> split<00:06:50.240> in<00:06:50.360> separate 00:06:50.680 --> 00:06:50.690 align:start position:0% this will be more split in separate 00:06:50.690 --> 00:06:52.900 align:start position:0% this will be more split in separate packages<00:06:51.200> where<00:06:51.590> you<00:06:51.680> also<00:06:51.860> can<00:06:52.130> require<00:06:52.550> the 00:06:52.900 --> 00:06:52.910 align:start position:0% packages where you also can require the 00:06:52.910 --> 00:06:55.630 align:start position:0% packages where you also can require the large<00:06:53.690> package<00:06:54.110> web<00:06:54.290> 3<00:06:54.530> which<00:06:54.740> we<00:06:54.920> have<00:06:55.160> which 00:06:55.630 --> 00:06:55.640 align:start position:0% large package web 3 which we have which 00:06:55.640 --> 00:06:57.100 align:start position:0% large package web 3 which we have which will<00:06:55.910> have<00:06:56.150> everything<00:06:56.480> you<00:06:56.630> need<00:06:56.870> for<00:06:57.050> your 00:06:57.100 --> 00:06:57.110 align:start position:0% will have everything you need for your 00:06:57.110 --> 00:06:58.900 align:start position:0% will have everything you need for your dab<00:06:57.350> or<00:06:57.590> you<00:06:57.740> only<00:06:57.920> need<00:06:58.250> the<00:06:58.400> utility 00:06:58.900 --> 00:06:58.910 align:start position:0% dab or you only need the utility 00:06:58.910 --> 00:07:01.920 align:start position:0% dab or you only need the utility functions<00:06:59.360> or<00:06:59.630> your<00:07:00.290> only<00:07:00.620> detail<00:07:01.070> functions 00:07:01.920 --> 00:07:01.930 align:start position:0% functions or your only detail functions 00:07:01.930 --> 00:07:08.230 align:start position:0% functions or your only detail functions only<00:07:02.930> the<00:07:03.470> swarm<00:07:03.740> functions<00:07:04.390> and<00:07:06.970> one<00:07:07.970> big 00:07:08.230 --> 00:07:08.240 align:start position:0% only the swarm functions and one big 00:07:08.240 --> 00:07:12.070 align:start position:0% only the swarm functions and one big part<00:07:08.540> of<00:07:08.930> the<00:07:09.320> refactor<00:07:09.860> is<00:07:10.040> the<00:07:10.750> way<00:07:11.750> how<00:07:12.050> we 00:07:12.070 --> 00:07:12.080 align:start position:0% part of the refactor is the way how we 00:07:12.080 --> 00:07:14.800 align:start position:0% part of the refactor is the way how we call<00:07:12.440> functions<00:07:13.010> so<00:07:13.640> we<00:07:13.850> currently<00:07:14.120> had<00:07:14.630> this 00:07:14.800 --> 00:07:14.810 align:start position:0% call functions so we currently had this 00:07:14.810 --> 00:07:17.170 align:start position:0% call functions so we currently had this way<00:07:15.020> of<00:07:15.050> calling<00:07:15.550> function<00:07:16.550> synchronous 00:07:17.170 --> 00:07:17.180 align:start position:0% way of calling function synchronous 00:07:17.180 --> 00:07:19.420 align:start position:0% way of calling function synchronous which<00:07:18.110> is<00:07:18.290> a<00:07:18.320> terrible<00:07:18.830> idea 00:07:19.420 --> 00:07:19.430 align:start position:0% which is a terrible idea 00:07:19.430 --> 00:07:21.370 align:start position:0% which is a terrible idea because<00:07:19.760> in<00:07:20.180> JavaScript<00:07:20.540> when<00:07:21.170> you<00:07:21.260> have 00:07:21.370 --> 00:07:21.380 align:start position:0% because in JavaScript when you have 00:07:21.380 --> 00:07:23.410 align:start position:0% because in JavaScript when you have synchronous<00:07:21.800> functions<00:07:22.280> your<00:07:22.910> interface 00:07:23.410 --> 00:07:23.420 align:start position:0% synchronous functions your interface 00:07:23.420 --> 00:07:25.690 align:start position:0% synchronous functions your interface freezes<00:07:23.960> the<00:07:24.590> assumption<00:07:25.040> was<00:07:25.190> that<00:07:25.250> the 00:07:25.690 --> 00:07:25.700 align:start position:0% freezes the assumption was that the 00:07:25.700 --> 00:07:27.940 align:start position:0% freezes the assumption was that the responses<00:07:26.360> from<00:07:26.480> the<00:07:26.660> node<00:07:26.810> will<00:07:27.050> be<00:07:27.170> so<00:07:27.380> so 00:07:27.940 --> 00:07:27.950 align:start position:0% responses from the node will be so so 00:07:27.950 --> 00:07:29.710 align:start position:0% responses from the node will be so so small<00:07:28.340> that<00:07:28.580> you<00:07:28.730> never<00:07:28.910> have<00:07:29.150> a<00:07:29.180> problem<00:07:29.390> with 00:07:29.710 --> 00:07:29.720 align:start position:0% small that you never have a problem with 00:07:29.720 --> 00:07:32.170 align:start position:0% small that you never have a problem with that<00:07:29.900> but<00:07:30.650> reality<00:07:31.070> teach<00:07:31.490> to<00:07:31.700> us<00:07:31.760> that<00:07:32.030> that 00:07:32.170 --> 00:07:32.180 align:start position:0% that but reality teach to us that that 00:07:32.180 --> 00:07:34.900 align:start position:0% that but reality teach to us that that is<00:07:32.360> actually<00:07:32.720> a<00:07:32.990> problem<00:07:33.290> and<00:07:33.710> it's<00:07:34.490> also<00:07:34.640> not 00:07:34.900 --> 00:07:34.910 align:start position:0% is actually a problem and it's also not 00:07:34.910 --> 00:07:37.890 align:start position:0% is actually a problem and it's also not the<00:07:35.030> way<00:07:35.150> you<00:07:35.210> can<00:07:35.480> do<00:07:35.630> that<00:07:35.720> in<00:07:35.870> JavaScript<00:07:36.100> so 00:07:37.890 --> 00:07:37.900 align:start position:0% the way you can do that in JavaScript so 00:07:37.900 --> 00:07:40.120 align:start position:0% the way you can do that in JavaScript so from<00:07:38.900> the<00:07:39.020> future<00:07:39.320> on<00:07:39.440> everything<00:07:39.860> will<00:07:40.010> be 00:07:40.120 --> 00:07:40.130 align:start position:0% from the future on everything will be 00:07:40.130 --> 00:07:43.660 align:start position:0% from the future on everything will be based<00:07:40.340> on<00:07:40.490> promises<00:07:41.320> but<00:07:42.490> there's<00:07:43.490> this 00:07:43.660 --> 00:07:43.670 align:start position:0% based on promises but there's this 00:07:43.670 --> 00:07:45.610 align:start position:0% based on promises but there's this special<00:07:43.970> case<00:07:44.360> and<00:07:44.390> etherium<00:07:45.110> that<00:07:45.440> one 00:07:45.610 --> 00:07:45.620 align:start position:0% special case and etherium that one 00:07:45.620 --> 00:07:49.590 align:start position:0% special case and etherium that one action<00:07:46.070> can<00:07:46.820> have<00:07:46.850> multiple<00:07:47.720> end<00:07:48.220> results<00:07:49.220> I 00:07:49.590 --> 00:07:49.600 align:start position:0% action can have multiple end results I 00:07:49.600 --> 00:07:52.240 align:start position:0% action can have multiple end results I combine<00:07:50.600> that<00:07:50.810> with<00:07:50.870> events<00:07:51.740> and<00:07:51.980> you 00:07:52.240 --> 00:07:52.250 align:start position:0% combine that with events and you 00:07:52.250 --> 00:07:55.570 align:start position:0% combine that with events and you basically<00:07:52.460> get<00:07:52.850> an<00:07:53.030> promise<00:07:53.600> event<00:07:53.930> back<00:07:54.580> so 00:07:55.570 --> 00:07:55.580 align:start position:0% basically get an promise event back so 00:07:55.580 --> 00:07:58.360 align:start position:0% basically get an promise event back so you<00:07:56.090> can<00:07:56.300> chain<00:07:56.660> it<00:07:56.900> and<00:07:57.110> then<00:07:57.680> will<00:07:57.980> be<00:07:58.010> called 00:07:58.360 --> 00:07:58.370 align:start position:0% you can chain it and then will be called 00:07:58.370 --> 00:08:00.550 align:start position:0% you can chain it and then will be called once<00:07:58.670> the<00:07:58.850> transactions<00:07:59.390> mind<00:07:59.660> but<00:08:00.320> you<00:08:00.440> can 00:08:00.550 --> 00:08:00.560 align:start position:0% once the transactions mind but you can 00:08:00.560 --> 00:08:03.070 align:start position:0% once the transactions mind but you can also<00:08:00.880> listen<00:08:01.880> for<00:08:02.000> specific<00:08:02.240> events<00:08:02.960> for 00:08:03.070 --> 00:08:03.080 align:start position:0% also listen for specific events for 00:08:03.080 --> 00:08:04.090 align:start position:0% also listen for specific events for example<00:08:03.110> when<00:08:03.470> you<00:08:03.590> want<00:08:03.710> to<00:08:03.830> get<00:08:04.010> the 00:08:04.090 --> 00:08:04.100 align:start position:0% example when you want to get the 00:08:04.100 --> 00:08:06.820 align:start position:0% example when you want to get the transaction<00:08:04.640> hash<00:08:04.850> or<00:08:05.150> like<00:08:06.140> the<00:08:06.290> mind<00:08:06.530> event 00:08:06.820 --> 00:08:06.830 align:start position:0% transaction hash or like the mind event 00:08:06.830 --> 00:08:08.380 align:start position:0% transaction hash or like the mind event and<00:08:07.070> in<00:08:07.250> the<00:08:07.340> future<00:08:07.700> we<00:08:07.820> could<00:08:07.970> add<00:08:08.150> more 00:08:08.380 --> 00:08:08.390 align:start position:0% and in the future we could add more 00:08:08.390 --> 00:08:09.910 align:start position:0% and in the future we could add more events<00:08:08.810> we<00:08:08.900> could<00:08:09.080> add<00:08:09.230> programmable<00:08:09.830> a 00:08:09.910 --> 00:08:09.920 align:start position:0% events we could add programmable a 00:08:09.920 --> 00:08:12.430 align:start position:0% events we could add programmable a confirmation<00:08:10.550> event<00:08:10.850> or<00:08:11.060> an<00:08:11.510> event<00:08:12.110> for<00:08:12.260> each 00:08:12.430 --> 00:08:12.440 align:start position:0% confirmation event or an event for each 00:08:12.440 --> 00:08:14.350 align:start position:0% confirmation event or an event for each single<00:08:13.010> confirmation<00:08:13.550> up<00:08:13.640> to<00:08:13.970> 12 00:08:14.350 --> 00:08:14.360 align:start position:0% single confirmation up to 12 00:08:14.360 --> 00:08:16.660 align:start position:0% single confirmation up to 12 confirmations<00:08:15.020> we<00:08:15.800> can<00:08:15.920> think<00:08:16.070> of<00:08:16.220> way<00:08:16.430> more 00:08:16.660 --> 00:08:16.670 align:start position:0% confirmations we can think of way more 00:08:16.670 --> 00:08:20.050 align:start position:0% confirmations we can think of way more things<00:08:16.910> we<00:08:17.150> can<00:08:17.330> actually<00:08:17.600> look<00:08:17.900> for<00:08:18.520> on<00:08:19.520> what 00:08:20.050 --> 00:08:20.060 align:start position:0% things we can actually look for on what 00:08:20.060 --> 00:08:21.400 align:start position:0% things we can actually look for on what happens<00:08:20.360> on<00:08:20.450> the<00:08:20.540> field<00:08:20.570> network<00:08:21.050> with<00:08:21.230> your 00:08:21.400 --> 00:08:21.410 align:start position:0% happens on the field network with your 00:08:21.410 --> 00:08:27.280 align:start position:0% happens on the field network with your action<00:08:21.890> you<00:08:22.040> did<00:08:25.390> the<00:08:26.390> same<00:08:26.600> goes<00:08:26.870> on<00:08:27.080> for 00:08:27.280 --> 00:08:27.290 align:start position:0% action you did the same goes on for 00:08:27.290 --> 00:08:29.080 align:start position:0% action you did the same goes on for other<00:08:27.380> functions<00:08:27.710> the<00:08:28.280> question<00:08:28.610> here<00:08:28.820> is<00:08:28.850> do 00:08:29.080 --> 00:08:29.090 align:start position:0% other functions the question here is do 00:08:29.090 --> 00:08:31.960 align:start position:0% other functions the question here is do we<00:08:29.210> need<00:08:29.420> like<00:08:29.780> the<00:08:30.410> events<00:08:30.770> here<00:08:30.980> to<00:08:31.190> that's 00:08:31.960 --> 00:08:31.970 align:start position:0% we need like the events here to that's 00:08:31.970 --> 00:08:33.580 align:start position:0% we need like the events here to that's to<00:08:32.270> be<00:08:32.390> seen<00:08:32.630> but<00:08:32.870> at<00:08:33.140> least<00:08:33.290> keeps 00:08:33.580 --> 00:08:33.590 align:start position:0% to be seen but at least keeps 00:08:33.590 --> 00:08:37.690 align:start position:0% to be seen but at least keeps consistency<00:08:35.080> deploying<00:08:36.080> contracts<00:08:36.680> and<00:08:36.890> the 00:08:37.690 --> 00:08:37.700 align:start position:0% consistency deploying contracts and the 00:08:37.700 --> 00:08:39.670 align:start position:0% consistency deploying contracts and the main<00:08:37.910> change<00:08:38.330> is<00:08:38.690> that<00:08:39.020> actually<00:08:39.440> you<00:08:39.530> now 00:08:39.670 --> 00:08:39.680 align:start position:0% main change is that actually you now 00:08:39.680 --> 00:08:41.530 align:start position:0% main change is that actually you now instantiate<00:08:40.430> the<00:08:40.610> new<00:08:40.760> contract<00:08:41.180> object 00:08:41.530 --> 00:08:41.540 align:start position:0% instantiate the new contract object 00:08:41.540 --> 00:08:44.920 align:start position:0% instantiate the new contract object using<00:08:41.840> the<00:08:41.870> nique<00:08:42.170> new<00:08:42.560> keyword<00:08:43.750> you<00:08:44.750> don't 00:08:44.920 --> 00:08:44.930 align:start position:0% using the nique new keyword you don't 00:08:44.930 --> 00:08:46.540 align:start position:0% using the nique new keyword you don't have<00:08:45.050> a<00:08:45.080> deploy<00:08:45.560> function<00:08:46.040> and<00:08:46.160> this<00:08:46.280> will<00:08:46.460> be 00:08:46.540 --> 00:08:46.550 align:start position:0% have a deploy function and this will be 00:08:46.550 --> 00:08:48.070 align:start position:0% have a deploy function and this will be the<00:08:46.670> same<00:08:46.880> as<00:08:47.120> the<00:08:47.420> transaction<00:08:47.990> you 00:08:48.070 --> 00:08:48.080 align:start position:0% the same as the transaction you 00:08:48.080 --> 00:08:49.890 align:start position:0% the same as the transaction you basically<00:08:48.440> just 00:08:49.890 --> 00:08:49.900 align:start position:0% basically just 00:08:49.900 --> 00:08:53.260 align:start position:0% basically just the<00:08:50.900> promise<00:08:51.860> we<00:08:52.310> solved<00:08:52.700> once<00:08:53.000> the 00:08:53.260 --> 00:08:53.270 align:start position:0% the promise we solved once the 00:08:53.270 --> 00:08:55.270 align:start position:0% the promise we solved once the transactions<00:08:54.020> mind<00:08:54.290> and<00:08:54.560> you<00:08:54.740> actually<00:08:54.950> have 00:08:55.270 --> 00:08:55.280 align:start position:0% transactions mind and you actually have 00:08:55.280 --> 00:08:58.240 align:start position:0% transactions mind and you actually have to<00:08:55.490> contract<00:08:55.820> address<00:08:56.270> object<00:08:56.750> the<00:08:57.710> contact 00:08:58.240 --> 00:08:58.250 align:start position:0% to contract address object the contact 00:08:58.250 --> 00:09:00.220 align:start position:0% to contract address object the contact address<00:08:58.580> and<00:08:58.790> the<00:08:58.910> contract<00:08:59.270> object<00:08:59.630> attached 00:09:00.220 --> 00:09:00.230 align:start position:0% address and the contract object attached 00:09:00.230 --> 00:09:02.770 align:start position:0% address and the contract object attached with<00:09:00.470> the<00:09:00.620> address<00:09:00.980> and<00:09:01.160> you'll<00:09:02.120> also<00:09:02.390> have 00:09:02.770 --> 00:09:02.780 align:start position:0% with the address and you'll also have 00:09:02.780 --> 00:09:04.810 align:start position:0% with the address and you'll also have this<00:09:03.050> event<00:09:03.560> so<00:09:03.860> basically<00:09:04.190> you<00:09:04.370> have<00:09:04.550> two 00:09:04.810 --> 00:09:04.820 align:start position:0% this event so basically you have two 00:09:04.820 --> 00:09:07.120 align:start position:0% this event so basically you have two ways<00:09:04.970> of<00:09:05.180> doing<00:09:05.240> it<00:09:05.750> and<00:09:06.020> there's<00:09:06.560> also<00:09:06.710> debate 00:09:07.120 --> 00:09:07.130 align:start position:0% ways of doing it and there's also debate 00:09:07.130 --> 00:09:09.100 align:start position:0% ways of doing it and there's also debate going<00:09:07.340> on<00:09:07.580> should<00:09:07.850> we<00:09:07.970> add<00:09:08.090> two<00:09:08.360> callbacks<00:09:08.660> or 00:09:09.100 --> 00:09:09.110 align:start position:0% going on should we add two callbacks or 00:09:09.110 --> 00:09:16.330 align:start position:0% going on should we add two callbacks or not<00:09:12.400> when<00:09:13.400> you<00:09:13.430> calling<00:09:14.000> methods<00:09:14.860> so<00:09:15.860> that's 00:09:16.330 --> 00:09:16.340 align:start position:0% not when you calling methods so that's 00:09:16.340 --> 00:09:18.010 align:start position:0% not when you calling methods so that's actually<00:09:16.520> a<00:09:16.790> better<00:09:17.150> way<00:09:17.270> than<00:09:17.660> we<00:09:17.780> did<00:09:17.930> it 00:09:18.010 --> 00:09:18.020 align:start position:0% actually a better way than we did it 00:09:18.020 --> 00:09:18.640 align:start position:0% actually a better way than we did it before 00:09:18.640 --> 00:09:18.650 align:start position:0% before 00:09:18.650 --> 00:09:20.370 align:start position:0% before so<00:09:18.830> you<00:09:18.890> basically<00:09:19.340> will<00:09:19.670> call<00:09:19.970> the<00:09:20.150> method 00:09:20.370 --> 00:09:20.380 align:start position:0% so you basically will call the method 00:09:20.380 --> 00:09:23.560 align:start position:0% so you basically will call the method you<00:09:21.380> give<00:09:21.710> it<00:09:21.830> all<00:09:21.980> the<00:09:22.100> parameters<00:09:22.700> and<00:09:22.970> be 00:09:23.560 --> 00:09:23.570 align:start position:0% you give it all the parameters and be 00:09:23.570 --> 00:09:26.550 align:start position:0% you give it all the parameters and be caught<00:09:23.780> because<00:09:24.350> before<00:09:24.980> we<00:09:25.250> basically<00:09:25.730> mixed 00:09:26.550 --> 00:09:26.560 align:start position:0% caught because before we basically mixed 00:09:26.560 --> 00:09:28.750 align:start position:0% caught because before we basically mixed parameters<00:09:27.560> with<00:09:27.800> the<00:09:27.830> transaction<00:09:28.400> object 00:09:28.750 --> 00:09:28.760 align:start position:0% parameters with the transaction object 00:09:28.760 --> 00:09:30.610 align:start position:0% parameters with the transaction object we<00:09:29.420> had<00:09:29.570> the<00:09:29.690> problem<00:09:30.050> that<00:09:30.080> you<00:09:30.320> could<00:09:30.470> never 00:09:30.610 --> 00:09:30.620 align:start position:0% we had the problem that you could never 00:09:30.620 --> 00:09:34.810 align:start position:0% we had the problem that you could never pass<00:09:31.460> a<00:09:31.490> struct<00:09:32.090> in<00:09:32.860> as<00:09:33.860> a<00:09:33.890> parameter<00:09:34.190> object 00:09:34.810 --> 00:09:34.820 align:start position:0% pass a struct in as a parameter object 00:09:34.820 --> 00:09:36.790 align:start position:0% pass a struct in as a parameter object because<00:09:35.120> we're<00:09:35.990> three<00:09:36.170> J's<00:09:36.410> would<00:09:36.650> have 00:09:36.790 --> 00:09:36.800 align:start position:0% because we're three J's would have 00:09:36.800 --> 00:09:38.590 align:start position:0% because we're three J's would have detected<00:09:37.310> this<00:09:37.460> as<00:09:37.700> being<00:09:37.940> the<00:09:38.030> options 00:09:38.590 --> 00:09:38.600 align:start position:0% detected this as being the options 00:09:38.600 --> 00:09:42.190 align:start position:0% detected this as being the options object<00:09:38.810> for<00:09:39.320> your<00:09:39.470> sin<00:09:39.740> transaction<00:09:40.480> so<00:09:41.480> doing 00:09:42.190 --> 00:09:42.200 align:start position:0% object for your sin transaction so doing 00:09:42.200 --> 00:09:43.900 align:start position:0% object for your sin transaction so doing it<00:09:42.290> this<00:09:42.500> way<00:09:42.560> it<00:09:43.130> allows<00:09:43.460> us<00:09:43.490> to<00:09:43.820> basically 00:09:43.900 --> 00:09:43.910 align:start position:0% it this way it allows us to basically 00:09:43.910 --> 00:09:46.180 align:start position:0% it this way it allows us to basically pass<00:09:44.330> any<00:09:44.540> kind<00:09:44.630> of<00:09:44.900> parameter<00:09:45.620> and<00:09:45.950> it<00:09:46.040> would 00:09:46.180 --> 00:09:46.190 align:start position:0% pass any kind of parameter and it would 00:09:46.190 --> 00:09:48.340 align:start position:0% pass any kind of parameter and it would be<00:09:46.280> clearly<00:09:46.520> only<00:09:46.880> a<00:09:46.910> parameter<00:09:47.390> then<00:09:48.110> you<00:09:48.200> get 00:09:48.340 --> 00:09:48.350 align:start position:0% be clearly only a parameter then you get 00:09:48.350 --> 00:09:50.350 align:start position:0% be clearly only a parameter then you get an<00:09:48.470> object<00:09:48.800> back<00:09:49.400> which<00:09:49.640> has<00:09:49.880> different 00:09:50.350 --> 00:09:50.360 align:start position:0% an object back which has different 00:09:50.360 --> 00:09:53.140 align:start position:0% an object back which has different functions<00:09:51.020> like<00:09:51.050> estimate<00:09:51.590> gas<00:09:51.830> which<00:09:52.820> gives 00:09:53.140 --> 00:09:53.150 align:start position:0% functions like estimate gas which gives 00:09:53.150 --> 00:09:54.910 align:start position:0% functions like estimate gas which gives you<00:09:53.360> the<00:09:53.510> gas<00:09:53.720> estimation<00:09:54.380> for<00:09:54.530> that<00:09:54.650> kind<00:09:54.860> of 00:09:54.910 --> 00:09:54.920 align:start position:0% you the gas estimation for that kind of 00:09:54.920 --> 00:09:58.660 align:start position:0% you the gas estimation for that kind of call<00:09:55.250> and<00:09:55.720> code<00:09:56.720> which<00:09:57.020> encodes<00:09:57.380> you<00:09:57.590> the<00:09:57.830> the 00:09:58.660 --> 00:09:58.670 align:start position:0% call and code which encodes you the the 00:09:58.670 --> 00:10:00.640 align:start position:0% call and code which encodes you the the ABI<00:09:59.000> for<00:09:59.510> that<00:09:59.660> kind<00:09:59.870> of<00:09:59.930> call<00:10:00.200> which<00:10:00.530> you 00:10:00.640 --> 00:10:00.650 align:start position:0% ABI for that kind of call which you 00:10:00.650 --> 00:10:02.320 align:start position:0% ABI for that kind of call which you could<00:10:00.830> then<00:10:00.860> use<00:10:01.250> and<00:10:01.520> pass<00:10:01.670> it<00:10:01.880> into<00:10:02.120> in<00:10:02.240> the 00:10:02.320 --> 00:10:02.330 align:start position:0% could then use and pass it into in the 00:10:02.330 --> 00:10:04.330 align:start position:0% could then use and pass it into in the contract<00:10:02.780> for<00:10:02.960> example<00:10:03.020> if<00:10:03.560> you<00:10:03.890> have<00:10:03.980> a<00:10:04.010> proxy 00:10:04.330 --> 00:10:04.340 align:start position:0% contract for example if you have a proxy 00:10:04.340 --> 00:10:07.720 align:start position:0% contract for example if you have a proxy contract<00:10:04.910> or<00:10:05.180> you<00:10:06.010> calling<00:10:07.010> the<00:10:07.160> function<00:10:07.550> or 00:10:07.720 --> 00:10:07.730 align:start position:0% contract or you calling the function or 00:10:07.730 --> 00:10:09.490 align:start position:0% contract or you calling the function or sending<00:10:08.180> the<00:10:08.300> transaction<00:10:08.840> for<00:10:08.990> the<00:10:09.050> function 00:10:09.490 --> 00:10:09.500 align:start position:0% sending the transaction for the function 00:10:09.500 --> 00:10:12.250 align:start position:0% sending the transaction for the function and<00:10:09.710> this<00:10:10.400> again<00:10:10.730> will<00:10:11.030> return<00:10:11.330> a<00:10:11.390> promise<00:10:12.050> or 00:10:12.250 --> 00:10:12.260 align:start position:0% and this again will return a promise or 00:10:12.260 --> 00:10:18.280 align:start position:0% and this again will return a promise or an<00:10:12.830> ester<00:10:13.340> and<00:10:13.780> events<00:10:16.840> you<00:10:17.840> also<00:10:17.990> will<00:10:18.260> have 00:10:18.280 --> 00:10:18.290 align:start position:0% an ester and events you also will have 00:10:18.290 --> 00:10:20.110 align:start position:0% an ester and events you also will have other<00:10:18.590> utility<00:10:19.370> function<00:10:19.730> which<00:10:19.850> you<00:10:19.970> right 00:10:20.110 --> 00:10:20.120 align:start position:0% other utility function which you right 00:10:20.120 --> 00:10:22.840 align:start position:0% other utility function which you right now<00:10:20.270> don't<00:10:20.540> expose<00:10:20.960> but<00:10:21.920> they're<00:10:22.130> very 00:10:22.840 --> 00:10:22.850 align:start position:0% now don't expose but they're very 00:10:22.850 --> 00:10:24.430 align:start position:0% now don't expose but they're very necessary<00:10:23.120> if<00:10:23.720> you<00:10:23.810> want<00:10:23.840> to<00:10:24.110> build<00:10:24.230> more 00:10:24.430 --> 00:10:24.440 align:start position:0% necessary if you want to build more 00:10:24.440 --> 00:10:25.960 align:start position:0% necessary if you want to build more complex<00:10:24.500> application<00:10:25.370> and<00:10:25.520> you<00:10:25.610> want<00:10:25.790> to<00:10:25.850> do 00:10:25.960 --> 00:10:25.970 align:start position:0% complex application and you want to do 00:10:25.970 --> 00:10:28.450 align:start position:0% complex application and you want to do things<00:10:26.210> yourself<00:10:26.470> means<00:10:27.470> you<00:10:27.710> can<00:10:27.860> encode 00:10:28.450 --> 00:10:28.460 align:start position:0% things yourself means you can encode 00:10:28.460 --> 00:10:30.310 align:start position:0% things yourself means you can encode like<00:10:28.730> you<00:10:28.820> get<00:10:28.970> the<00:10:29.060> chase<00:10:29.420> interface<00:10:29.780> just<00:10:30.200> of 00:10:30.310 --> 00:10:30.320 align:start position:0% like you get the chase interface just of 00:10:30.320 --> 00:10:31.750 align:start position:0% like you get the chase interface just of a<00:10:30.410> method<00:10:30.770> and<00:10:30.950> you<00:10:31.010> can<00:10:31.070> code<00:10:31.520> the<00:10:31.730> whole 00:10:31.750 --> 00:10:31.760 align:start position:0% a method and you can code the whole 00:10:31.760 --> 00:10:33.910 align:start position:0% a method and you can code the whole thing<00:10:32.750> if<00:10:32.930> you<00:10:32.990> want<00:10:33.050> to<00:10:33.260> do<00:10:33.410> this<00:10:33.530> in<00:10:33.770> the 00:10:33.910 --> 00:10:33.920 align:start position:0% thing if you want to do this in the 00:10:33.920 --> 00:10:35.680 align:start position:0% thing if you want to do this in the contract<00:10:34.580> object<00:10:34.970> you<00:10:35.090> already<00:10:35.330> have<00:10:35.540> the 00:10:35.680 --> 00:10:35.690 align:start position:0% contract object you already have the 00:10:35.690 --> 00:10:38.140 align:start position:0% contract object you already have the encode<00:10:35.960> functions<00:10:36.470> function<00:10:37.370> you<00:10:37.700> also<00:10:37.940> have 00:10:38.140 --> 00:10:38.150 align:start position:0% encode functions function you also have 00:10:38.150 --> 00:10:39.730 align:start position:0% encode functions function you also have a<00:10:38.180> constructor<00:10:38.750> function<00:10:39.140> which<00:10:39.350> you<00:10:39.470> cannot 00:10:39.730 --> 00:10:39.740 align:start position:0% a constructor function which you cannot 00:10:39.740 --> 00:10:42.100 align:start position:0% a constructor function which you cannot call<00:10:40.040> or<00:10:40.250> send<00:10:40.430> transactions<00:10:40.940> to<00:10:41.180> but<00:10:41.930> which 00:10:42.100 --> 00:10:42.110 align:start position:0% call or send transactions to but which 00:10:42.110 --> 00:10:46.090 align:start position:0% call or send transactions to but which you<00:10:42.140> can<00:10:42.380> also<00:10:42.590> encode<00:10:43.070> and<00:10:44.770> there's<00:10:45.770> more<00:10:45.950> to 00:10:46.090 --> 00:10:46.100 align:start position:0% you can also encode and there's more to 00:10:46.100 --> 00:10:47.980 align:start position:0% you can also encode and there's more to come<00:10:46.280> for<00:10:46.520> example<00:10:46.640> like<00:10:47.030> passing<00:10:47.420> in<00:10:47.540> structs 00:10:47.980 --> 00:10:47.990 align:start position:0% come for example like passing in structs 00:10:47.990 --> 00:10:49.710 align:start position:0% come for example like passing in structs returning<00:10:48.380> structural<00:10:48.770> smart<00:10:49.010> contracts<00:10:49.490> and 00:10:49.710 --> 00:10:49.720 align:start position:0% returning structural smart contracts and 00:10:49.720 --> 00:10:52.360 align:start position:0% returning structural smart contracts and I<00:10:50.720> would<00:10:50.930> like<00:10:51.110> to<00:10:51.290> get<00:10:51.470> feedback<00:10:51.800> and<00:10:52.250> ideas 00:10:52.360 --> 00:10:52.370 align:start position:0% I would like to get feedback and ideas 00:10:52.370 --> 00:10:56.620 align:start position:0% I would like to get feedback and ideas so<00:10:52.940> my<00:10:53.720> main<00:10:53.960> idea<00:10:54.320> is<00:10:55.270> doing<00:10:56.270> everything 00:10:56.620 --> 00:10:56.630 align:start position:0% so my main idea is doing everything 00:10:56.630 --> 00:10:58.630 align:start position:0% so my main idea is doing everything which<00:10:56.870> is<00:10:56.900> currently<00:10:57.350> in<00:10:57.440> the<00:10:57.530> 1.0<00:10:58.130> milestone 00:10:58.630 --> 00:10:58.640 align:start position:0% which is currently in the 1.0 milestone 00:10:58.640 --> 00:10:59.550 align:start position:0% which is currently in the 1.0 milestone and 00:10:59.550 --> 00:10:59.560 align:start position:0% and 00:10:59.560 --> 00:11:01.140 align:start position:0% and working<00:11:00.040> through<00:11:00.220> it<00:11:00.430> and<00:11:00.610> doing<00:11:00.730> it<00:11:00.910> this<00:11:01.090> way 00:11:01.140 --> 00:11:01.150 align:start position:0% working through it and doing it this way 00:11:01.150 --> 00:11:03.240 align:start position:0% working through it and doing it this way and<00:11:01.330> then<00:11:01.780> releasing<00:11:02.500> an<00:11:02.560> alpha<00:11:02.920> getting 00:11:03.240 --> 00:11:03.250 align:start position:0% and then releasing an alpha getting 00:11:03.250 --> 00:11:05.910 align:start position:0% and then releasing an alpha getting feedback<00:11:03.400> from<00:11:03.610> the<00:11:03.850> community<00:11:04.030> and<00:11:04.890> then<00:11:05.890> we 00:11:05.910 --> 00:11:05.920 align:start position:0% feedback from the community and then we 00:11:05.920 --> 00:11:07.980 align:start position:0% feedback from the community and then we can<00:11:06.190> go<00:11:06.400> on<00:11:06.550> and<00:11:06.790> released<00:11:07.240> at<00:11:07.360> some<00:11:07.390> point<00:11:07.780> a 00:11:07.980 --> 00:11:07.990 align:start position:0% can go on and released at some point a 00:11:07.990 --> 00:11:12.090 align:start position:0% can go on and released at some point a web<00:11:08.140> 3js<00:11:09.210> 1.0<00:11:10.210> which<00:11:10.770> everybody<00:11:11.770> is<00:11:11.890> happy 00:11:12.090 --> 00:11:12.100 align:start position:0% web 3js 1.0 which everybody is happy 00:11:12.100 --> 00:11:14.520 align:start position:0% web 3js 1.0 which everybody is happy with<00:11:12.370> and<00:11:12.640> which<00:11:13.150> will<00:11:13.630> be<00:11:13.780> hopefully<00:11:14.110> the 00:11:14.520 --> 00:11:14.530 align:start position:0% with and which will be hopefully the 00:11:14.530 --> 00:11:16.530 align:start position:0% with and which will be hopefully the only<00:11:14.890> breaking<00:11:15.160> changes<00:11:15.790> for<00:11:16.000> the<00:11:16.090> next<00:11:16.270> few 00:11:16.530 --> 00:11:16.540 align:start position:0% only breaking changes for the next few 00:11:16.540 --> 00:11:19.290 align:start position:0% only breaking changes for the next few years<00:11:16.890> but<00:11:17.890> there<00:11:18.040> will<00:11:18.190> be<00:11:18.220> a<00:11:18.460> few<00:11:18.970> breaking 00:11:19.290 --> 00:11:19.300 align:start position:0% years but there will be a few breaking 00:11:19.300 --> 00:11:22.020 align:start position:0% years but there will be a few breaking changes<00:11:19.720> but<00:11:19.930> necessary<00:11:20.410> ones<00:11:20.650> so<00:11:21.280> your 00:11:22.020 --> 00:11:22.030 align:start position:0% changes but necessary ones so your 00:11:22.030 --> 00:11:24.810 align:start position:0% changes but necessary ones so your feedback<00:11:22.360> is<00:11:22.480> welcome<00:11:22.950> the<00:11:23.950> keto<00:11:24.130> Channel<00:11:24.580> and 00:11:24.810 --> 00:11:24.820 align:start position:0% feedback is welcome the keto Channel and 00:11:24.820 --> 00:11:28.290 align:start position:0% feedback is welcome the keto Channel and the<00:11:25.240> issues<00:11:25.570> ideally<00:11:26.140> and<00:11:27.000> let's<00:11:28.000> talk<00:11:28.240> about 00:11:28.290 --> 00:11:28.300 align:start position:0% the issues ideally and let's talk about 00:11:28.300 --> 00:11:30.120 align:start position:0% the issues ideally and let's talk about what's<00:11:29.170> what<00:11:29.470> could<00:11:29.650> be<00:11:29.740> next 00:11:30.120 --> 00:11:30.130 align:start position:0% what's what could be next 00:11:30.130 --> 00:11:36.360 align:start position:0% what's what could be next Thanks<00:11:32.820> thank<00:11:33.820> you<00:11:33.940> for<00:11:34.090> the<00:11:34.300> end<00:11:35.280> did<00:11:36.280> you 00:11:36.360 --> 00:11:36.370 align:start position:0% Thanks thank you for the end did you 00:11:36.370 --> 00:11:40.740 align:start position:0% Thanks thank you for the end did you want<00:11:36.550> to<00:11:36.610> take<00:11:36.760> a<00:11:36.790> question<00:11:38.370> I<00:11:39.600> can<00:11:40.600> take 00:11:40.740 --> 00:11:40.750 align:start position:0% want to take a question I can take 00:11:40.750 --> 00:11:42.480 align:start position:0% want to take a question I can take questions<00:11:41.230> yeah<00:11:41.620> if<00:11:41.740> I<00:11:41.830> have<00:11:41.920> time<00:11:42.130> yes<00:11:42.310> any 00:11:42.480 --> 00:11:42.490 align:start position:0% questions yeah if I have time yes any 00:11:42.490 --> 00:11:45.360 align:start position:0% questions yeah if I have time yes any questions<00:11:42.910> for<00:11:43.000> Fabian<00:11:43.420> any<00:11:44.140> questions<00:11:44.650> come 00:11:45.360 --> 00:11:45.370 align:start position:0% questions for Fabian any questions come 00:11:45.370 --> 00:11:46.550 align:start position:0% questions for Fabian any questions come on 00:11:46.550 --> 00:11:46.560 align:start position:0% on 00:11:46.560 --> 00:11:57.960 align:start position:0% on yep<00:11:54.720> perfect<00:11:55.720> microphone<00:11:56.430> with<00:11:57.430> the<00:11:57.460> next 00:11:57.960 --> 00:11:57.970 align:start position:0% yep perfect microphone with the next 00:11:57.970 --> 00:11:59.670 align:start position:0% yep perfect microphone with the next rewrite<00:11:58.300> do<00:11:58.450> you<00:11:58.510> plan<00:11:58.750> on<00:11:58.780> utilizing<00:11:59.080> type 00:11:59.670 --> 00:11:59.680 align:start position:0% rewrite do you plan on utilizing type 00:11:59.680 --> 00:12:02.610 align:start position:0% rewrite do you plan on utilizing type scripts<00:11:59.980> to<00:12:00.190> help<00:12:00.750> make<00:12:01.750> it<00:12:01.900> cleaner<00:12:02.170> and<00:12:02.440> help 00:12:02.610 --> 00:12:02.620 align:start position:0% scripts to help make it cleaner and help 00:12:02.620 --> 00:12:04.560 align:start position:0% scripts to help make it cleaner and help to<00:12:02.800> check<00:12:03.430> for<00:12:03.610> standard<00:12:04.180> bugs<00:12:04.330> and<00:12:04.510> things 00:12:04.560 --> 00:12:04.570 align:start position:0% to check for standard bugs and things 00:12:04.570 --> 00:12:07.350 align:start position:0% to check for standard bugs and things like<00:12:04.750> that<00:12:04.810> yeah<00:12:05.380> what<00:12:05.589> makes<00:12:05.770> sense<00:12:06.010> right<00:12:06.360> I 00:12:07.350 --> 00:12:07.360 align:start position:0% like that yeah what makes sense right I 00:12:07.360 --> 00:12:09.630 align:start position:0% like that yeah what makes sense right I want<00:12:08.020> to<00:12:08.140> keep<00:12:08.260> it<00:12:08.410> as<00:12:08.530> minimal<00:12:09.520> as<00:12:09.580> possible 00:12:09.630 --> 00:12:09.640 align:start position:0% want to keep it as minimal as possible 00:12:09.640 --> 00:12:11.490 align:start position:0% want to keep it as minimal as possible if<00:12:10.120> other<00:12:10.300> people<00:12:10.630> want<00:12:10.870> to<00:12:10.930> build<00:12:11.140> on<00:12:11.320> top 00:12:11.490 --> 00:12:11.500 align:start position:0% if other people want to build on top 00:12:11.500 --> 00:12:12.840 align:start position:0% if other people want to build on top like<00:12:11.740> something<00:12:12.130> like<00:12:12.280> a<00:12:12.310> typescript 00:12:12.840 --> 00:12:12.850 align:start position:0% like something like a typescript 00:12:12.850 --> 00:12:15.540 align:start position:0% like something like a typescript compiling<00:12:13.620> version<00:12:14.620> yeah<00:12:14.770> that<00:12:14.980> makes<00:12:15.430> sense 00:12:15.540 --> 00:12:15.550 align:start position:0% compiling version yeah that makes sense 00:12:15.550 --> 00:12:17.730 align:start position:0% compiling version yeah that makes sense but<00:12:15.970> I<00:12:16.210> want<00:12:16.600> to<00:12:16.720> keep<00:12:16.870> it<00:12:17.020> as<00:12:17.170> like<00:12:17.380> a<00:12:17.410> bare 00:12:17.730 --> 00:12:17.740 align:start position:0% but I want to keep it as like a bare 00:12:17.740 --> 00:12:18.450 align:start position:0% but I want to keep it as like a bare minimum 00:12:18.450 --> 00:12:18.460 align:start position:0% minimum 00:12:18.460 --> 00:12:21.300 align:start position:0% minimum library<00:12:19.560> otherwise<00:12:20.560> it's<00:12:20.770> getting<00:12:21.040> a<00:12:21.130> point 00:12:21.300 --> 00:12:21.310 align:start position:0% library otherwise it's getting a point 00:12:21.310 --> 00:12:23.370 align:start position:0% library otherwise it's getting a point put<00:12:21.610> opinionated<00:12:22.300> again<00:12:22.570> and<00:12:22.839> then<00:12:22.960> there's<00:12:23.350> a 00:12:23.370 --> 00:12:23.380 align:start position:0% put opinionated again and then there's a 00:12:23.380 --> 00:12:25.350 align:start position:0% put opinionated again and then there's a bunch<00:12:23.560> of<00:12:23.620> discussions<00:12:23.950> its<00:12:24.850> cousins<00:12:25.180> and 00:12:25.350 --> 00:12:25.360 align:start position:0% bunch of discussions its cousins and 00:12:25.360 --> 00:12:27.150 align:start position:0% bunch of discussions its cousins and other<00:12:25.480> people<00:12:25.810> would<00:12:25.930> then<00:12:26.500> use<00:12:26.530> CoffeeScript 00:12:27.150 --> 00:12:27.160 align:start position:0% other people would then use CoffeeScript 00:12:27.160 --> 00:12:29.670 align:start position:0% other people would then use CoffeeScript and<00:12:27.580> everybody<00:12:28.570> wants<00:12:28.810> to<00:12:28.870> do<00:12:29.050> use<00:12:29.380> something 00:12:29.670 --> 00:12:29.680 align:start position:0% and everybody wants to do use something 00:12:29.680 --> 00:12:34.970 align:start position:0% and everybody wants to do use something else<00:12:29.800> so<00:12:30.370> I<00:12:30.610> stick<00:12:31.570> with<00:12:31.600> the<00:12:31.930> pure<00:12:32.260> JavaScript 00:12:34.970 --> 00:12:34.980 align:start position:0% 00:12:34.980 --> 00:12:39.900 align:start position:0% anyone<00:12:35.980> else<00:12:38.070> okay<00:12:39.070> well<00:12:39.490> thank<00:12:39.730> you<00:12:39.880> very 00:12:39.900 --> 00:12:39.910 align:start position:0% anyone else okay well thank you very 00:12:39.910 --> 00:12:42.930 align:start position:0% anyone else okay well thank you very much<00:12:40.360> Fabian