WEBVTT Kind: captions Language: en 00:00:00.810 --> 00:00:03.679 align:start position:0% so<00:00:01.290> I<00:00:01.319> wrote<00:00:01.800> ethers<00:00:02.100> j/s<00:00:02.399> the<00:00:03.300> ideas<00:00:03.540> is<00:00:03.659> a 00:00:03.679 --> 00:00:03.689 align:start position:0% so I wrote ethers j/s the ideas is a 00:00:03.689 --> 00:00:05.329 align:start position:0% so I wrote ethers j/s the ideas is a complete<00:00:04.020> simple<00:00:04.410> tiny<00:00:04.650> library<00:00:05.190> its 00:00:05.329 --> 00:00:05.339 align:start position:0% complete simple tiny library its 00:00:05.339 --> 00:00:08.560 align:start position:0% complete simple tiny library its replacement<00:00:05.730> for<00:00:06.120> web<00:00:06.930> 3<00:00:07.230> and<00:00:07.500> aetherium<00:00:07.980> je<00:00:08.220> s 00:00:08.560 --> 00:00:08.570 align:start position:0% replacement for web 3 and aetherium je s 00:00:08.570 --> 00:00:11.030 align:start position:0% replacement for web 3 and aetherium je s if<00:00:09.570> you<00:00:09.690> use<00:00:09.870> either<00:00:10.080> of<00:00:10.290> those<00:00:10.410> you<00:00:10.469> can<00:00:10.920> use 00:00:11.030 --> 00:00:11.040 align:start position:0% if you use either of those you can use 00:00:11.040 --> 00:00:13.640 align:start position:0% if you use either of those you can use this<00:00:11.160> instead<00:00:11.480> so<00:00:12.480> some<00:00:12.719> quick<00:00:12.870> history<00:00:13.290> I<00:00:13.320> was 00:00:13.640 --> 00:00:13.650 align:start position:0% this instead so some quick history I was 00:00:13.650 --> 00:00:15.740 align:start position:0% this instead so some quick history I was writing<00:00:13.889> an<00:00:14.070> in-browser<00:00:14.580> equivalent<00:00:15.450> of<00:00:15.540> meta 00:00:15.740 --> 00:00:15.750 align:start position:0% writing an in-browser equivalent of meta 00:00:15.750 --> 00:00:17.150 align:start position:0% writing an in-browser equivalent of meta mask<00:00:15.990> but<00:00:16.350> this<00:00:16.379> was<00:00:16.590> before<00:00:16.740> madam<00:00:17.039> asked 00:00:17.150 --> 00:00:17.160 align:start position:0% mask but this was before madam asked 00:00:17.160 --> 00:00:19.010 align:start position:0% mask but this was before madam asked existed<00:00:17.609> I<00:00:17.760> want<00:00:18.300> some<00:00:18.449> like<00:00:18.570> in<00:00:18.720> browser 00:00:19.010 --> 00:00:19.020 align:start position:0% existed I want some like in browser 00:00:19.020 --> 00:00:21.769 align:start position:0% existed I want some like in browser adapt<00:00:19.410> browser<00:00:19.939> so<00:00:20.939> by<00:00:21.150> the<00:00:21.210> time<00:00:21.420> I<00:00:21.449> included 00:00:21.769 --> 00:00:21.779 align:start position:0% adapt browser so by the time I included 00:00:21.779 --> 00:00:24.259 align:start position:0% adapt browser so by the time I included all<00:00:21.960> the<00:00:22.050> libraries<00:00:22.470> that<00:00:22.769> I<00:00:23.279> needed<00:00:23.490> the<00:00:23.850> this 00:00:24.259 --> 00:00:24.269 align:start position:0% all the libraries that I needed the this 00:00:24.269 --> 00:00:27.189 align:start position:0% all the libraries that I needed the this page<00:00:24.630> was<00:00:25.260> 7.4<00:00:26.099> megabytes<00:00:26.609> to<00:00:26.670> download 00:00:27.189 --> 00:00:27.199 align:start position:0% page was 7.4 megabytes to download 00:00:27.199 --> 00:00:29.509 align:start position:0% page was 7.4 megabytes to download there's<00:00:28.199> a<00:00:28.260> lot<00:00:28.349> of<00:00:28.470> bugs<00:00:28.650> back<00:00:28.890> then<00:00:29.130> I<00:00:29.160> think 00:00:29.509 --> 00:00:29.519 align:start position:0% there's a lot of bugs back then I think 00:00:29.519 --> 00:00:30.620 align:start position:0% there's a lot of bugs back then I think somebody<00:00:29.760> was<00:00:29.820> mentioning<00:00:30.300> and<00:00:30.449> the<00:00:30.510> other 00:00:30.620 --> 00:00:30.630 align:start position:0% somebody was mentioning and the other 00:00:30.630 --> 00:00:33.110 align:start position:0% somebody was mentioning and the other talk<00:00:30.990> earlier<00:00:31.380> that<00:00:32.070> one<00:00:32.250> out<00:00:32.460> of<00:00:32.489> 128 00:00:33.110 --> 00:00:33.120 align:start position:0% talk earlier that one out of 128 00:00:33.120 --> 00:00:34.880 align:start position:0% talk earlier that one out of 128 addresses<00:00:33.660> were<00:00:33.870> computed<00:00:34.260> wrong<00:00:34.530> from<00:00:34.860> the 00:00:34.880 --> 00:00:34.890 align:start position:0% addresses were computed wrong from the 00:00:34.890 --> 00:00:36.830 align:start position:0% addresses were computed wrong from the private<00:00:35.250> key<00:00:35.430> so<00:00:35.640> I<00:00:35.760> just<00:00:35.880> produced<00:00:36.149> unspent 00:00:36.830 --> 00:00:36.840 align:start position:0% private key so I just produced unspent 00:00:36.840 --> 00:00:40.819 align:start position:0% private key so I just produced unspent able<00:00:37.820> monies<00:00:39.230> the<00:00:40.230> other<00:00:40.379> big<00:00:40.620> thing 00:00:40.819 --> 00:00:40.829 align:start position:0% able monies the other big thing 00:00:40.829 --> 00:00:41.990 align:start position:0% able monies the other big thing especially<00:00:40.980> back<00:00:41.309> in<00:00:41.340> the<00:00:41.460> day<00:00:41.550> if<00:00:41.670> you<00:00:41.760> wanted 00:00:41.990 --> 00:00:42.000 align:start position:0% especially back in the day if you wanted 00:00:42.000 --> 00:00:43.970 align:start position:0% especially back in the day if you wanted to<00:00:42.120> build<00:00:42.270> a<00:00:42.360> DAP<00:00:42.540> I<00:00:43.140> mean<00:00:43.620> it<00:00:43.680> was<00:00:43.800> really 00:00:43.970 --> 00:00:43.980 align:start position:0% to build a DAP I mean it was really 00:00:43.980 --> 00:00:45.410 align:start position:0% to build a DAP I mean it was really simple<00:00:44.160> so<00:00:44.399> all<00:00:44.520> you<00:00:44.610> had<00:00:44.700> to<00:00:44.730> do<00:00:44.850> is<00:00:44.940> download 00:00:45.410 --> 00:00:45.420 align:start position:0% simple so all you had to do is download 00:00:45.420 --> 00:00:48.110 align:start position:0% simple so all you had to do is download death<00:00:45.809> wait<00:00:46.559> three<00:00:46.950> days<00:00:46.980> for<00:00:47.399> it<00:00:47.430> to<00:00:47.489> sync<00:00:47.820> and 00:00:48.110 --> 00:00:48.120 align:start position:0% death wait three days for it to sync and 00:00:48.120 --> 00:00:50.360 align:start position:0% death wait three days for it to sync and once<00:00:48.660> that<00:00:48.840> was<00:00:48.960> done<00:00:49.140> connect<00:00:49.890> to<00:00:50.039> it<00:00:50.160> and<00:00:50.309> do 00:00:50.360 --> 00:00:50.370 align:start position:0% once that was done connect to it and do 00:00:50.370 --> 00:00:51.799 align:start position:0% once that was done connect to it and do all<00:00:50.399> other<00:00:50.670> stuff<00:00:50.969> and<00:00:51.239> now<00:00:51.360> it'll<00:00:51.600> probably 00:00:51.799 --> 00:00:51.809 align:start position:0% all other stuff and now it'll probably 00:00:51.809 --> 00:00:53.660 align:start position:0% all other stuff and now it'll probably work<00:00:52.170> you<00:00:52.800> might<00:00:53.010> have<00:00:53.100> to<00:00:53.160> blow<00:00:53.280> the<00:00:53.370> database 00:00:53.660 --> 00:00:53.670 align:start position:0% work you might have to blow the database 00:00:53.670 --> 00:00:55.100 align:start position:0% work you might have to blow the database away<00:00:53.820> a<00:00:53.850> few<00:00:54.030> times<00:00:54.090> and<00:00:54.480> like<00:00:54.600> resync<00:00:54.989> from 00:00:55.100 --> 00:00:55.110 align:start position:0% away a few times and like resync from 00:00:55.110 --> 00:00:57.830 align:start position:0% away a few times and like resync from scratch<00:00:55.320> but<00:00:55.559> it's<00:00:56.489> easy<00:00:56.640> no<00:00:56.969> worries<00:00:57.059> so<00:00:57.809> I 00:00:57.830 --> 00:00:57.840 align:start position:0% scratch but it's easy no worries so I 00:00:57.840 --> 00:00:59.389 align:start position:0% scratch but it's easy no worries so I was<00:00:57.960> really<00:00:58.199> trying<00:00:58.739> to<00:00:58.829> get<00:00:58.890> around<00:00:59.039> that<00:00:59.190> the 00:00:59.389 --> 00:00:59.399 align:start position:0% was really trying to get around that the 00:00:59.399 --> 00:01:01.189 align:start position:0% was really trying to get around that the other<00:00:59.579> big<00:00:59.789> issue<00:00:59.940> is<00:01:00.120> all<00:01:00.359> the<00:01:00.510> libraries<00:01:00.960> web 00:01:01.189 --> 00:01:01.199 align:start position:0% other big issue is all the libraries web 00:01:01.199 --> 00:01:05.240 align:start position:0% other big issue is all the libraries web 3<00:01:01.440> etc<00:01:01.829> were<00:01:01.949> LGPL<00:01:02.699> GPL<00:01:03.300> like<00:01:04.140> random<00:01:05.070> weird 00:01:05.240 --> 00:01:05.250 align:start position:0% 3 etc were LGPL GPL like random weird 00:01:05.250 --> 00:01:06.950 align:start position:0% 3 etc were LGPL GPL like random weird licenses<00:01:05.790> that<00:01:06.090> were<00:01:06.450> really<00:01:06.630> not<00:01:06.689> conducive 00:01:06.950 --> 00:01:06.960 align:start position:0% licenses that were really not conducive 00:01:06.960 --> 00:01:09.770 align:start position:0% licenses that were really not conducive to<00:01:07.820> proprietary<00:01:08.820> software<00:01:08.970> which<00:01:09.390> means<00:01:09.420> that 00:01:09.770 --> 00:01:09.780 align:start position:0% to proprietary software which means that 00:01:09.780 --> 00:01:11.480 align:start position:0% to proprietary software which means that if<00:01:10.080> we<00:01:10.229> have<00:01:10.260> things<00:01:10.830> that<00:01:11.250> eventually 00:01:11.480 --> 00:01:11.490 align:start position:0% if we have things that eventually 00:01:11.490 --> 00:01:13.070 align:start position:0% if we have things that eventually occurred<00:01:11.939> like<00:01:12.090> hyper<00:01:12.330> ledger<00:01:12.600> that<00:01:12.750> start 00:01:13.070 --> 00:01:13.080 align:start position:0% occurred like hyper ledger that start 00:01:13.080 --> 00:01:14.539 align:start position:0% occurred like hyper ledger that start making<00:01:13.350> their<00:01:13.470> own<00:01:13.500> sort<00:01:13.860> of<00:01:13.920> versions<00:01:14.310> of<00:01:14.400> it 00:01:14.539 --> 00:01:14.549 align:start position:0% making their own sort of versions of it 00:01:14.549 --> 00:01:16.550 align:start position:0% making their own sort of versions of it which<00:01:14.640> would<00:01:14.760> be<00:01:14.850> weirdly<00:01:15.240> incompatible<00:01:15.810> just 00:01:16.550 --> 00:01:16.560 align:start position:0% which would be weirdly incompatible just 00:01:16.560 --> 00:01:18.560 align:start position:0% which would be weirdly incompatible just because<00:01:16.860> we<00:01:17.130> didn't<00:01:17.430> let<00:01:17.759> them<00:01:18.030> join<00:01:18.360> in<00:01:18.509> the 00:01:18.560 --> 00:01:18.570 align:start position:0% because we didn't let them join in the 00:01:18.570 --> 00:01:20.420 align:start position:0% because we didn't let them join in the first<00:01:18.750> place<00:01:18.930> so<00:01:19.890> that<00:01:20.040> was<00:01:20.130> the<00:01:20.189> idea<00:01:20.220> is 00:01:20.420 --> 00:01:20.430 align:start position:0% first place so that was the idea is 00:01:20.430 --> 00:01:22.280 align:start position:0% first place so that was the idea is basically<00:01:20.580> that<00:01:20.880> sort<00:01:21.150> of<00:01:21.180> idea<00:01:21.420> also 00:01:22.280 --> 00:01:22.290 align:start position:0% basically that sort of idea also 00:01:22.290 --> 00:01:25.429 align:start position:0% basically that sort of idea also documentation<00:01:22.799> was<00:01:23.040> like<00:01:23.159> nil<00:01:24.320> so<00:01:25.320> the 00:01:25.429 --> 00:01:25.439 align:start position:0% documentation was like nil so the 00:01:25.439 --> 00:01:27.859 align:start position:0% documentation was like nil so the highlights<00:01:25.590> of<00:01:25.830> ethers<00:01:26.100> j/s<00:01:26.400> so<00:01:27.360> it's<00:01:27.509> tiny 00:01:27.859 --> 00:01:27.869 align:start position:0% highlights of ethers j/s so it's tiny 00:01:27.869 --> 00:01:29.539 align:start position:0% highlights of ethers j/s so it's tiny over<00:01:28.470> the<00:01:28.560> wire<00:01:28.680> it's<00:01:28.979> about<00:01:29.130> it's<00:01:29.369> actually 00:01:29.539 --> 00:01:29.549 align:start position:0% over the wire it's about it's actually 00:01:29.549 --> 00:01:32.899 align:start position:0% over the wire it's about it's actually about<00:01:29.850> 89<00:01:30.329> kilobytes<00:01:30.869> right<00:01:31.020> now<00:01:31.140> not<00:01:31.350> 88<00:01:31.909> but 00:01:32.899 --> 00:01:32.909 align:start position:0% about 89 kilobytes right now not 88 but 00:01:32.909 --> 00:01:35.050 align:start position:0% about 89 kilobytes right now not 88 but it<00:01:33.030> handles<00:01:33.180> pneumonic<00:01:33.750> pneumonic<00:01:34.560> he's 00:01:35.050 --> 00:01:35.060 align:start position:0% it handles pneumonic pneumonic he's 00:01:35.060 --> 00:01:37.940 align:start position:0% it handles pneumonic pneumonic he's private<00:01:36.060> keys<00:01:36.210> JSON<00:01:36.630> wallets<00:01:36.960> it<00:01:37.740> tries<00:01:37.920> to 00:01:37.940 --> 00:01:37.950 align:start position:0% private keys JSON wallets it tries to 00:01:37.950 --> 00:01:39.410 align:start position:0% private keys JSON wallets it tries to really<00:01:38.220> do<00:01:38.310> anything<00:01:38.700> you<00:01:38.970> could<00:01:39.150> do<00:01:39.240> if<00:01:39.390> you 00:01:39.410 --> 00:01:39.420 align:start position:0% really do anything you could do if you 00:01:39.420 --> 00:01:40.580 align:start position:0% really do anything you could do if you were<00:01:39.540> trying<00:01:39.750> to<00:01:39.810> build<00:01:39.900> a<00:01:40.110> wallet<00:01:40.439> or 00:01:40.580 --> 00:01:40.590 align:start position:0% were trying to build a wallet or 00:01:40.590 --> 00:01:45.139 align:start position:0% were trying to build a wallet or framework<00:01:41.250> or<00:01:43.579> basically<00:01:44.579> anything<00:01:44.850> you<00:01:45.000> want 00:01:45.139 --> 00:01:45.149 align:start position:0% framework or basically anything you want 00:01:45.149 --> 00:01:47.719 align:start position:0% framework or basically anything you want to<00:01:45.210> in<00:01:45.299> aetherium<00:01:45.720> it<00:01:45.810> supports<00:01:46.490> it's<00:01:47.490> ready 00:01:47.719 --> 00:01:47.729 align:start position:0% to in aetherium it supports it's ready 00:01:47.729 --> 00:01:49.999 align:start position:0% to in aetherium it supports it's ready to<00:01:47.850> use<00:01:48.030> one<00:01:48.810> thing<00:01:49.020> that<00:01:49.200> the<00:01:49.320> other<00:01:49.500> options 00:01:49.999 --> 00:01:50.009 align:start position:0% to use one thing that the other options 00:01:50.009 --> 00:01:51.530 align:start position:0% to use one thing that the other options didn't<00:01:50.220> offer<00:01:50.340> especially<00:01:50.759> at<00:01:50.820> the<00:01:50.880> time<00:01:51.060> was 00:01:51.530 --> 00:01:51.540 align:start position:0% didn't offer especially at the time was 00:01:51.540 --> 00:01:52.940 align:start position:0% didn't offer especially at the time was like<00:01:51.659> a<00:01:51.720> dist<00:01:52.110> package<00:01:52.530> that<00:01:52.680> you<00:01:52.740> could<00:01:52.860> just 00:01:52.940 --> 00:01:52.950 align:start position:0% like a dist package that you could just 00:01:52.950 --> 00:01:54.410 align:start position:0% like a dist package that you could just like<00:01:53.100> jam<00:01:53.399> in<00:01:53.520> a<00:01:53.579> browser<00:01:53.790> and<00:01:54.030> be<00:01:54.119> off<00:01:54.210> to<00:01:54.329> the 00:01:54.410 --> 00:01:54.420 align:start position:0% like jam in a browser and be off to the 00:01:54.420 --> 00:01:54.859 align:start position:0% like jam in a browser and be off to the races 00:01:54.859 --> 00:01:54.869 align:start position:0% races 00:01:54.869 --> 00:01:56.539 align:start position:0% races you<00:01:55.320> had<00:01:55.500> to<00:01:55.619> browserify<00:01:56.070> all<00:01:56.430> these 00:01:56.539 --> 00:01:56.549 align:start position:0% you had to browserify all these 00:01:56.549 --> 00:01:58.959 align:start position:0% you had to browserify all these libraries<00:01:56.729> to<00:01:57.030> make<00:01:57.119> things<00:01:57.360> work<00:01:57.570> test<00:01:58.560> cases 00:01:58.959 --> 00:01:58.969 align:start position:0% libraries to make things work test cases 00:01:58.969 --> 00:02:01.399 align:start position:0% libraries to make things work test cases most<00:01:59.969> libraries<00:02:00.450> around<00:02:00.540> the<00:02:00.689> time<00:02:00.840> again 00:02:01.399 --> 00:02:01.409 align:start position:0% most libraries around the time again 00:02:01.409 --> 00:02:03.679 align:start position:0% most libraries around the time again even<00:02:01.799> today<00:02:02.130> have<00:02:02.490> between<00:02:02.820> like<00:02:02.939> 83<00:02:03.420> and<00:02:03.630> a 00:02:03.679 --> 00:02:03.689 align:start position:0% even today have between like 83 and a 00:02:03.689 --> 00:02:04.700 align:start position:0% even today have between like 83 and a couple<00:02:03.869> hundred<00:02:04.020> test<00:02:04.350> cases 00:02:04.700 --> 00:02:04.710 align:start position:0% couple hundred test cases 00:02:04.710 --> 00:02:07.429 align:start position:0% couple hundred test cases I'm<00:02:05.460> currently<00:02:05.640> clocked<00:02:05.939> in<00:02:06.030> at<00:02:06.119> 20,000<00:02:06.869> give 00:02:07.429 --> 00:02:07.439 align:start position:0% I'm currently clocked in at 20,000 give 00:02:07.439 --> 00:02:10.940 align:start position:0% I'm currently clocked in at 20,000 give or<00:02:07.619> take<00:02:07.920> maybe<00:02:08.819> 50<00:02:09.179> or<00:02:09.239> 60<00:02:09.509> test<00:02:09.690> cases<00:02:09.840> all<00:02:10.830> of 00:02:10.940 --> 00:02:10.950 align:start position:0% or take maybe 50 or 60 test cases all of 00:02:10.950 --> 00:02:12.290 align:start position:0% or take maybe 50 or 60 test cases all of them<00:02:11.069> are<00:02:11.160> procedurally<00:02:11.640> procedurally 00:02:12.290 --> 00:02:12.300 align:start position:0% them are procedurally procedurally 00:02:12.300 --> 00:02:13.820 align:start position:0% them are procedurally procedurally generated<00:02:12.660> love<00:02:12.959> to<00:02:13.050> talk<00:02:13.200> with<00:02:13.379> that<00:02:13.410> for 00:02:13.820 --> 00:02:13.830 align:start position:0% generated love to talk with that for 00:02:13.830 --> 00:02:15.200 align:start position:0% generated love to talk with that for anybody<00:02:14.040> afterwards<00:02:14.460> who<00:02:14.730> wants<00:02:14.940> to<00:02:15.030> find<00:02:15.150> out 00:02:15.200 --> 00:02:15.210 align:start position:0% anybody afterwards who wants to find out 00:02:15.210 --> 00:02:16.880 align:start position:0% anybody afterwards who wants to find out more<00:02:15.300> about<00:02:15.390> how<00:02:15.540> to<00:02:15.570> like<00:02:15.840> procedures<00:02:16.710> gender 00:02:16.880 --> 00:02:16.890 align:start position:0% more about how to like procedures gender 00:02:16.890 --> 00:02:19.460 align:start position:0% more about how to like procedures gender test<00:02:17.010> cases<00:02:17.540> providers<00:02:18.540> going<00:02:19.080> back<00:02:19.200> to<00:02:19.380> the 00:02:19.460 --> 00:02:19.470 align:start position:0% test cases providers going back to the 00:02:19.470 --> 00:02:21.830 align:start position:0% test cases providers going back to the sinking<00:02:20.010> of<00:02:20.100> full<00:02:20.280> node<00:02:20.460> providers<00:02:21.150> you 00:02:21.830 --> 00:02:21.840 align:start position:0% sinking of full node providers you 00:02:21.840 --> 00:02:22.970 align:start position:0% sinking of full node providers you should<00:02:21.990> be<00:02:22.050> able<00:02:22.170> to<00:02:22.230> use<00:02:22.320> anything<00:02:22.530> you<00:02:22.680> want 00:02:22.970 --> 00:02:22.980 align:start position:0% should be able to use anything you want 00:02:22.980 --> 00:02:25.430 align:start position:0% should be able to use anything you want so<00:02:23.250> you<00:02:23.280> can<00:02:23.490> use<00:02:23.580> JSON<00:02:23.820> RPC<00:02:24.140> but<00:02:25.140> there's 00:02:25.430 --> 00:02:25.440 align:start position:0% so you can use JSON RPC but there's 00:02:25.440 --> 00:02:28.040 align:start position:0% so you can use JSON RPC but there's things<00:02:25.650> like<00:02:25.710> ether<00:02:26.130> scan<00:02:26.490> and<00:02:27.050> technically 00:02:28.040 --> 00:02:28.050 align:start position:0% things like ether scan and technically 00:02:28.050 --> 00:02:29.660 align:start position:0% things like ether scan and technically my<00:02:28.350> crypto<00:02:28.770> you<00:02:28.950> could<00:02:29.100> just<00:02:29.280> like<00:02:29.370> kind<00:02:29.610> of 00:02:29.660 --> 00:02:29.670 align:start position:0% my crypto you could just like kind of 00:02:29.670 --> 00:02:31.370 align:start position:0% my crypto you could just like kind of tie<00:02:29.940> into<00:02:30.270> their<00:02:30.420> their<00:02:30.810> back-end<00:02:30.990> there's<00:02:31.290> no 00:02:31.370 --> 00:02:31.380 align:start position:0% tie into their their back-end there's no 00:02:31.380 --> 00:02:32.960 align:start position:0% tie into their their back-end there's no reason<00:02:31.620> why<00:02:31.710> you<00:02:31.770> can't<00:02:32.040> just<00:02:32.190> use<00:02:32.820> these 00:02:32.960 --> 00:02:32.970 align:start position:0% reason why you can't just use these 00:02:32.970 --> 00:02:36.620 align:start position:0% reason why you can't just use these other<00:02:33.150> sources<00:02:33.420> of<00:02:33.600> truth<00:02:34.880> so<00:02:35.880> another<00:02:36.360> big 00:02:36.620 --> 00:02:36.630 align:start position:0% other sources of truth so another big 00:02:36.630 --> 00:02:38.690 align:start position:0% other sources of truth so another big difference<00:02:36.750> for<00:02:37.410> people<00:02:37.650> coming<00:02:38.160> from<00:02:38.250> web<00:02:38.430> 3 00:02:38.690 --> 00:02:38.700 align:start position:0% difference for people coming from web 3 00:02:38.700 --> 00:02:40.220 align:start position:0% difference for people coming from web 3 is<00:02:38.880> that<00:02:39.000> signers<00:02:39.540> and<00:02:39.720> providers<00:02:40.050> actually 00:02:40.220 --> 00:02:40.230 align:start position:0% is that signers and providers actually 00:02:40.230 --> 00:02:42.260 align:start position:0% is that signers and providers actually go<00:02:40.440> more<00:02:40.710> to<00:02:40.800> this<00:02:40.860> in<00:02:41.010> next<00:02:41.130> slides<00:02:41.400> but<00:02:41.700> as<00:02:42.210> a 00:02:42.260 --> 00:02:42.270 align:start position:0% go more to this in next slides but as a 00:02:42.270 --> 00:02:43.460 align:start position:0% go more to this in next slides but as a quick<00:02:42.390> we'll<00:02:42.600> review<00:02:42.810> signers<00:02:43.170> and<00:02:43.200> fighter 00:02:43.460 --> 00:02:43.470 align:start position:0% quick we'll review signers and fighter 00:02:43.470 --> 00:02:45.380 align:start position:0% quick we'll review signers and fighter providers<00:02:44.010> are<00:02:44.130> very<00:02:44.160> different<00:02:44.400> but<00:02:45.240> there's 00:02:45.380 --> 00:02:45.390 align:start position:0% providers are very different but there's 00:02:45.390 --> 00:02:48.020 align:start position:0% providers are very different but there's different<00:02:45.630> types<00:02:45.840> of<00:02:45.990> signers<00:02:46.640> ENS<00:02:47.640> support 00:02:48.020 --> 00:02:48.030 align:start position:0% different types of signers ENS support 00:02:48.030 --> 00:02:49.880 align:start position:0% different types of signers ENS support is<00:02:48.210> a<00:02:48.240> first-class<00:02:48.810> system<00:02:49.500> go<00:02:49.590> more<00:02:49.740> to<00:02:49.830> that 00:02:49.880 --> 00:02:49.890 align:start position:0% is a first-class system go more to that 00:02:49.890 --> 00:02:51.550 align:start position:0% is a first-class system go more to that in<00:02:50.130> a<00:02:50.190> few<00:02:50.340> slides 00:02:51.550 --> 00:02:51.560 align:start position:0% in a few slides 00:02:51.560 --> 00:02:54.980 align:start position:0% in a few slides ABI<00:02:52.560> v2<00:02:53.010> this<00:02:53.310> ABI<00:02:54.120> v2<00:02:54.390> has<00:02:54.450> been<00:02:54.600> available<00:02:54.750> in 00:02:54.980 --> 00:02:54.990 align:start position:0% ABI v2 this ABI v2 has been available in 00:02:54.990 --> 00:02:57.680 align:start position:0% ABI v2 this ABI v2 has been available in ethers<00:02:55.290> j/s<00:02:55.590> for<00:02:55.740> over<00:02:55.980> a<00:02:56.010> year<00:02:56.160> now<00:02:56.190> I<00:02:57.000> was 00:02:57.680 --> 00:02:57.690 align:start position:0% ethers j/s for over a year now I was 00:02:57.690 --> 00:02:58.910 align:start position:0% ethers j/s for over a year now I was kind<00:02:57.900> of<00:02:57.930> talking<00:02:58.110> up<00:02:58.290> last<00:02:58.500> year<00:02:58.740> at<00:02:58.830> the 00:02:58.910 --> 00:02:58.920 align:start position:0% kind of talking up last year at the 00:02:58.920 --> 00:03:00.680 align:start position:0% kind of talking up last year at the previous<00:02:59.340> Def<00:02:59.520> Con<00:02:59.760> again<00:03:00.450> lost 00:03:00.680 --> 00:03:00.690 align:start position:0% previous Def Con again lost 00:03:00.690 --> 00:03:02.660 align:start position:0% previous Def Con again lost documentation<00:03:01.260> and<00:03:01.470> everything<00:03:02.430> all 00:03:02.660 --> 00:03:02.670 align:start position:0% documentation and everything all 00:03:02.670 --> 00:03:04.790 align:start position:0% documentation and everything all dependencies<00:03:03.209> are<00:03:03.450> MIT<00:03:03.750> licensed<00:03:04.260> which 00:03:04.790 --> 00:03:04.800 align:start position:0% dependencies are MIT licensed which 00:03:04.800 --> 00:03:06.080 align:start position:0% dependencies are MIT licensed which meant<00:03:05.040> a<00:03:05.280> few<00:03:05.580> of<00:03:05.640> the<00:03:05.730> libraries<00:03:06.060> that 00:03:06.080 --> 00:03:06.090 align:start position:0% meant a few of the libraries that 00:03:06.090 --> 00:03:07.970 align:start position:0% meant a few of the libraries that existed<00:03:06.540> like<00:03:06.600> our<00:03:06.780> LP<00:03:07.020> encoding<00:03:07.500> at<00:03:07.680> the<00:03:07.800> time 00:03:07.970 --> 00:03:07.980 align:start position:0% existed like our LP encoding at the time 00:03:07.980 --> 00:03:09.380 align:start position:0% existed like our LP encoding at the time again<00:03:08.310> we're<00:03:08.459> only<00:03:08.580> available<00:03:08.700> as<00:03:08.970> GPL<00:03:09.360> or 00:03:09.380 --> 00:03:09.390 align:start position:0% again we're only available as GPL or 00:03:09.390 --> 00:03:12.080 align:start position:0% again we're only available as GPL or LGPL<00:03:10.110> so<00:03:10.740> like<00:03:11.280> those<00:03:11.490> things<00:03:11.700> were<00:03:11.850> rewritten 00:03:12.080 --> 00:03:12.090 align:start position:0% LGPL so like those things were rewritten 00:03:12.090 --> 00:03:16.250 align:start position:0% LGPL so like those things were rewritten so<00:03:12.510> that<00:03:12.630> they<00:03:12.690> could<00:03:12.810> be<00:03:12.870> MIT<00:03:13.170> licensed<00:03:15.260> ok 00:03:16.250 --> 00:03:16.260 align:start position:0% so that they could be MIT licensed ok 00:03:16.260 --> 00:03:19.640 align:start position:0% so that they could be MIT licensed ok can't<00:03:17.130> read<00:03:17.220> the<00:03:17.310> clock<00:03:17.450> anyways<00:03:18.530> so<00:03:19.530> yeah 00:03:19.640 --> 00:03:19.650 align:start position:0% can't read the clock anyways so yeah 00:03:19.650 --> 00:03:20.660 align:start position:0% can't read the clock anyways so yeah going<00:03:19.769> back<00:03:19.860> providers<00:03:20.310> there's<00:03:20.519> lots<00:03:20.640> of 00:03:20.660 --> 00:03:20.670 align:start position:0% going back providers there's lots of 00:03:20.670 --> 00:03:22.460 align:start position:0% going back providers there's lots of different<00:03:20.910> types<00:03:20.940> of<00:03:21.209> providers<00:03:21.420> ether<00:03:22.260> scan 00:03:22.460 --> 00:03:22.470 align:start position:0% different types of providers ether scan 00:03:22.470 --> 00:03:23.930 align:start position:0% different types of providers ether scan and<00:03:22.680> Fira<00:03:22.920> json-rpc 00:03:23.930 --> 00:03:23.940 align:start position:0% and Fira json-rpc 00:03:23.940 --> 00:03:26.750 align:start position:0% and Fira json-rpc IPC<00:03:24.480> web<00:03:25.200> is<00:03:25.380> coming<00:03:25.650> soon<00:03:25.860> there's<00:03:26.250> a<00:03:26.310> web<00:03:26.489> 3 00:03:26.750 --> 00:03:26.760 align:start position:0% IPC web is coming soon there's a web 3 00:03:26.760 --> 00:03:28.610 align:start position:0% IPC web is coming soon there's a web 3 provider<00:03:27.120> which<00:03:27.870> you<00:03:27.989> can<00:03:28.140> if<00:03:28.320> you<00:03:28.410> have<00:03:28.440> a 00:03:28.610 --> 00:03:28.620 align:start position:0% provider which you can if you have a 00:03:28.620 --> 00:03:30.740 align:start position:0% provider which you can if you have a currently<00:03:28.980> current<00:03:29.580> existing<00:03:29.970> web<00:03:30.150> 3<00:03:30.390> app<00:03:30.540> you 00:03:30.740 --> 00:03:30.750 align:start position:0% currently current existing web 3 app you 00:03:30.750 --> 00:03:32.870 align:start position:0% currently current existing web 3 app you just<00:03:30.780> jam<00:03:31.170> that<00:03:31.350> provider<00:03:31.680> wrap<00:03:32.459> it<00:03:32.610> in<00:03:32.700> a<00:03:32.760> web 00:03:32.870 --> 00:03:32.880 align:start position:0% just jam that provider wrap it in a web 00:03:32.880 --> 00:03:34.160 align:start position:0% just jam that provider wrap it in a web 3<00:03:33.060> provider<00:03:33.330> and<00:03:33.570> now<00:03:33.630> you<00:03:33.690> have<00:03:33.780> an<00:03:33.840> ether<00:03:34.110> is 00:03:34.160 --> 00:03:34.170 align:start position:0% 3 provider and now you have an ether is 00:03:34.170 --> 00:03:36.770 align:start position:0% 3 provider and now you have an ether is compatible<00:03:34.560> provider<00:03:34.830> you<00:03:35.220> can<00:03:35.250> use<00:03:35.489> for<00:03:35.790> any 00:03:36.770 --> 00:03:36.780 align:start position:0% compatible provider you can use for any 00:03:36.780 --> 00:03:37.850 align:start position:0% compatible provider you can use for any of<00:03:36.959> these<00:03:37.019> sorts<00:03:37.230> of<00:03:37.260> things<00:03:37.350> fallback 00:03:37.850 --> 00:03:37.860 align:start position:0% of these sorts of things fallback 00:03:37.860 --> 00:03:39.920 align:start position:0% of these sorts of things fallback provider<00:03:38.220> we're<00:03:39.060> coming<00:03:39.300> with<00:03:39.360> a<00:03:39.450> smart 00:03:39.920 --> 00:03:39.930 align:start position:0% provider we're coming with a smart 00:03:39.930 --> 00:03:42.830 align:start position:0% provider we're coming with a smart provider<00:03:40.830> soon<00:03:41.190> which<00:03:41.459> will<00:03:41.700> for<00:03:41.970> example<00:03:42.000> get 00:03:42.830 --> 00:03:42.840 align:start position:0% provider soon which will for example get 00:03:42.840 --> 00:03:44.870 align:start position:0% provider soon which will for example get quorum<00:03:43.440> against<00:03:43.800> multiple<00:03:44.160> backends 00:03:44.870 --> 00:03:44.880 align:start position:0% quorum against multiple backends 00:03:44.880 --> 00:03:46.490 align:start position:0% quorum against multiple backends because<00:03:45.510> right<00:03:45.630> now<00:03:45.660> you're<00:03:45.870> trusting<00:03:46.170> API<00:03:46.410> is 00:03:46.490 --> 00:03:46.500 align:start position:0% because right now you're trusting API is 00:03:46.500 --> 00:03:47.990 align:start position:0% because right now you're trusting API is you're<00:03:46.680> trusting<00:03:47.070> ether<00:03:47.340> scan<00:03:47.550> tells<00:03:47.760> you<00:03:47.880> the 00:03:47.990 --> 00:03:48.000 align:start position:0% you're trusting ether scan tells you the 00:03:48.000 --> 00:03:50.540 align:start position:0% you're trusting ether scan tells you the truth<00:03:48.120> what<00:03:48.780> if<00:03:48.930> they're<00:03:49.230> hacked<00:03:49.530> or<00:03:49.830> you 00:03:50.540 --> 00:03:50.550 align:start position:0% truth what if they're hacked or you 00:03:50.550 --> 00:03:52.009 align:start position:0% truth what if they're hacked or you click<00:03:50.820> that<00:03:51.000> I<00:03:51.180> accept 00:03:52.009 --> 00:03:52.019 align:start position:0% click that I accept 00:03:52.019 --> 00:03:53.570 align:start position:0% click that I accept turning<00:03:52.350> off<00:03:52.440> SSL<00:03:52.920> protection<00:03:53.370> basically 00:03:53.570 --> 00:03:53.580 align:start position:0% turning off SSL protection basically 00:03:53.580 --> 00:03:56.840 align:start position:0% turning off SSL protection basically when<00:03:54.150> you're<00:03:54.300> at<00:03:54.360> Starbucks<00:03:55.250> so<00:03:56.250> that's<00:03:56.760> the 00:03:56.840 --> 00:03:56.850 align:start position:0% when you're at Starbucks so that's the 00:03:56.850 --> 00:03:58.310 align:start position:0% when you're at Starbucks so that's the age<00:03:56.910> of<00:03:57.000> providers<00:03:57.330> providers<00:03:57.600> are<00:03:57.780> very<00:03:58.110> high 00:03:58.310 --> 00:03:58.320 align:start position:0% age of providers providers are very high 00:03:58.320 --> 00:04:00.710 align:start position:0% age of providers providers are very high level<00:03:58.620> very<00:03:58.890> only<00:03:59.610> talking<00:04:00.330> to<00:04:00.360> what<00:04:00.600> you'd 00:04:00.710 --> 00:04:00.720 align:start position:0% level very only talking to what you'd 00:04:00.720 --> 00:04:02.210 align:start position:0% level very only talking to what you'd expect<00:04:01.050> a<00:04:01.200> blockchain<00:04:01.500> to<00:04:01.800> be<00:04:01.860> able<00:04:01.920> to<00:04:02.010> tell 00:04:02.210 --> 00:04:02.220 align:start position:0% expect a blockchain to be able to tell 00:04:02.220 --> 00:04:04.340 align:start position:0% expect a blockchain to be able to tell you<00:04:02.370> which<00:04:03.150> is<00:04:03.180> very<00:04:03.420> separate<00:04:03.720> from<00:04:03.750> signers 00:04:04.340 --> 00:04:04.350 align:start position:0% you which is very separate from signers 00:04:04.350 --> 00:04:06.080 align:start position:0% you which is very separate from signers signers<00:04:05.010> are<00:04:05.160> where<00:04:05.310> your<00:04:05.430> private<00:04:05.730> key<00:04:05.880> lives 00:04:06.080 --> 00:04:06.090 align:start position:0% signers are where your private key lives 00:04:06.090 --> 00:04:07.580 align:start position:0% signers are where your private key lives the<00:04:06.239> idea<00:04:06.600> that<00:04:06.690> your<00:04:06.810> private<00:04:07.140> key<00:04:07.290> should 00:04:07.580 --> 00:04:07.590 align:start position:0% the idea that your private key should 00:04:07.590 --> 00:04:11.690 align:start position:0% the idea that your private key should live<00:04:07.830> in<00:04:08.400> the<00:04:08.730> same<00:04:09.000> memory<00:04:09.750> space<00:04:10.230> as<00:04:10.700> the 00:04:11.690 --> 00:04:11.700 align:start position:0% live in the same memory space as the 00:04:11.700 --> 00:04:12.830 align:start position:0% live in the same memory space as the thing<00:04:11.910> that's<00:04:12.090> just<00:04:12.209> talking<00:04:12.450> to<00:04:12.660> the<00:04:12.720> network 00:04:12.830 --> 00:04:12.840 align:start position:0% thing that's just talking to the network 00:04:12.840 --> 00:04:14.630 align:start position:0% thing that's just talking to the network and<00:04:13.049> doing<00:04:13.230> crazy<00:04:13.380> things<00:04:13.799> just<00:04:14.100> seems 00:04:14.630 --> 00:04:14.640 align:start position:0% and doing crazy things just seems 00:04:14.640 --> 00:04:17.509 align:start position:0% and doing crazy things just seems inherently<00:04:15.030> unsafe<00:04:15.440> so<00:04:16.440> we<00:04:16.680> let<00:04:16.859> waltz<00:04:17.280> be<00:04:17.489> a 00:04:17.509 --> 00:04:17.519 align:start position:0% inherently unsafe so we let waltz be a 00:04:17.519 --> 00:04:20.360 align:start position:0% inherently unsafe so we let waltz be a private<00:04:18.030> key<00:04:18.180> a<00:04:18.209> mnemonic<00:04:18.590> for<00:04:19.590> example<00:04:19.950> the 00:04:20.360 --> 00:04:20.370 align:start position:0% private key a mnemonic for example the 00:04:20.370 --> 00:04:22.550 align:start position:0% private key a mnemonic for example the Firefly<00:04:20.820> the<00:04:21.419> hardware<00:04:21.690> wallet<00:04:21.870> we<00:04:21.959> design<00:04:22.229> or 00:04:22.550 --> 00:04:22.560 align:start position:0% Firefly the hardware wallet we design or 00:04:22.560 --> 00:04:24.590 align:start position:0% Firefly the hardware wallet we design or Leger<00:04:22.950> nano<00:04:23.190> wallet<00:04:23.520> these<00:04:24.120> are<00:04:24.240> just<00:04:24.390> other 00:04:24.590 --> 00:04:24.600 align:start position:0% Leger nano wallet these are just other 00:04:24.600 --> 00:04:26.210 align:start position:0% Leger nano wallet these are just other types<00:04:24.930> of<00:04:25.140> signers<00:04:25.530> you<00:04:25.710> want<00:04:25.890> to<00:04:25.950> be<00:04:26.039> able<00:04:26.100> to 00:04:26.210 --> 00:04:26.220 align:start position:0% types of signers you want to be able to 00:04:26.220 --> 00:04:27.530 align:start position:0% types of signers you want to be able to use<00:04:26.490> to<00:04:26.880> to<00:04:27.210> carry 00:04:27.530 --> 00:04:27.540 align:start position:0% use to to carry 00:04:27.540 --> 00:04:30.890 align:start position:0% use to to carry and<00:04:27.840> do<00:04:28.290> your<00:04:29.120> work 00:04:30.890 --> 00:04:30.900 align:start position:0% and do your work 00:04:30.900 --> 00:04:33.710 align:start position:0% and do your work this<00:04:31.860> was<00:04:32.010> a<00:04:32.040> weird<00:04:32.640> decision<00:04:32.850> I'm<00:04:33.210> actually 00:04:33.710 --> 00:04:33.720 align:start position:0% this was a weird decision I'm actually 00:04:33.720 --> 00:04:35.270 align:start position:0% this was a weird decision I'm actually curious<00:04:33.990> why<00:04:34.290> this<00:04:34.350> was<00:04:34.650> originally<00:04:35.160> designed 00:04:35.270 --> 00:04:35.280 align:start position:0% curious why this was originally designed 00:04:35.280 --> 00:04:37.580 align:start position:0% curious why this was originally designed basically<00:04:36.210> when<00:04:36.450> you<00:04:36.510> send<00:04:36.720> a<00:04:36.780> transaction<00:04:37.140> in 00:04:37.580 --> 00:04:37.590 align:start position:0% basically when you send a transaction in 00:04:37.590 --> 00:04:41.180 align:start position:0% basically when you send a transaction in web<00:04:37.770> 3<00:04:38.010> you<00:04:38.640> get<00:04:38.790> back<00:04:38.940> a<00:04:38.970> transaction<00:04:39.540> hash<00:04:40.190> so 00:04:41.180 --> 00:04:41.190 align:start position:0% web 3 you get back a transaction hash so 00:04:41.190 --> 00:04:43.340 align:start position:0% web 3 you get back a transaction hash so for<00:04:41.490> example<00:04:41.820> if<00:04:42.360> you<00:04:42.540> send<00:04:42.750> a<00:04:42.840> transaction<00:04:43.170> to 00:04:43.340 --> 00:04:43.350 align:start position:0% for example if you send a transaction to 00:04:43.350 --> 00:04:46.940 align:start position:0% for example if you send a transaction to the<00:04:43.530> goth<00:04:43.740> node<00:04:44.300> and<00:04:45.300> you<00:04:45.660> say<00:04:46.110> value<00:04:46.710> this 00:04:46.940 --> 00:04:46.950 align:start position:0% the goth node and you say value this 00:04:46.950 --> 00:04:49.460 align:start position:0% the goth node and you say value this data<00:04:47.370> that<00:04:47.610> the<00:04:48.210> Geth<00:04:48.390> node<00:04:48.690> is<00:04:48.930> figuring<00:04:49.380> out 00:04:49.460 --> 00:04:49.470 align:start position:0% data that the Geth node is figuring out 00:04:49.470 --> 00:04:51.440 align:start position:0% data that the Geth node is figuring out the<00:04:49.620> gas<00:04:49.770> price<00:04:50.100> for<00:04:50.370> you<00:04:50.520> the<00:04:50.760> nonce<00:04:50.940> all<00:04:51.330> that 00:04:51.440 --> 00:04:51.450 align:start position:0% the gas price for you the nonce all that 00:04:51.450 --> 00:04:53.180 align:start position:0% the gas price for you the nonce all that extra<00:04:51.660> stuff<00:04:51.780> but<00:04:52.710> all<00:04:52.830> you<00:04:52.920> get<00:04:53.040> back<00:04:53.070> is 00:04:53.180 --> 00:04:53.190 align:start position:0% extra stuff but all you get back is 00:04:53.190 --> 00:04:54.680 align:start position:0% extra stuff but all you get back is opaque<00:04:53.610> hash<00:04:53.880> so<00:04:54.120> you<00:04:54.210> actually<00:04:54.480> don't<00:04:54.630> know 00:04:54.680 --> 00:04:54.690 align:start position:0% opaque hash so you actually don't know 00:04:54.690 --> 00:04:56.990 align:start position:0% opaque hash so you actually don't know what<00:04:54.930> it<00:04:55.080> chose<00:04:55.350> for<00:04:55.650> you<00:04:55.830> especially<00:04:56.730> in<00:04:56.940> the 00:04:56.990 --> 00:04:57.000 align:start position:0% what it chose for you especially in the 00:04:57.000 --> 00:04:59.870 align:start position:0% what it chose for you especially in the case<00:04:57.120> of<00:04:57.150> like<00:04:57.420> gas<00:04:57.720> congestion<00:04:58.350> you<00:04:59.280> actually 00:04:59.870 --> 00:04:59.880 align:start position:0% case of like gas congestion you actually 00:04:59.880 --> 00:05:01.700 align:start position:0% case of like gas congestion you actually don't<00:05:00.120> know<00:05:00.210> what<00:05:00.300> was<00:05:00.450> used<00:05:00.660> so<00:05:01.320> you<00:05:01.380> can't 00:05:01.700 --> 00:05:01.710 align:start position:0% don't know what was used so you can't 00:05:01.710 --> 00:05:02.780 align:start position:0% don't know what was used so you can't even<00:05:01.860> know<00:05:02.040> if<00:05:02.100> you<00:05:02.160> need<00:05:02.280> to<00:05:02.310> replay<00:05:02.670> the 00:05:02.780 --> 00:05:02.790 align:start position:0% even know if you need to replay the 00:05:02.790 --> 00:05:04.750 align:start position:0% even know if you need to replay the transaction<00:05:03.240> a<00:05:03.300> higher<00:05:03.450> gasp<00:05:03.690> cast 00:05:04.750 --> 00:05:04.760 align:start position:0% transaction a higher gasp cast 00:05:04.760 --> 00:05:06.980 align:start position:0% transaction a higher gasp cast importantly<00:05:05.760> all<00:05:06.030> that<00:05:06.270> information<00:05:06.690> was 00:05:06.980 --> 00:05:06.990 align:start position:0% importantly all that information was 00:05:06.990 --> 00:05:09.380 align:start position:0% importantly all that information was signed<00:05:07.320> by<00:05:07.650> the<00:05:07.710> Geth<00:05:08.040> node<00:05:08.310> so<00:05:08.610> it<00:05:08.640> knew<00:05:09.090> all 00:05:09.380 --> 00:05:09.390 align:start position:0% signed by the Geth node so it knew all 00:05:09.390 --> 00:05:11.540 align:start position:0% signed by the Geth node so it knew all that<00:05:09.540> information<00:05:09.990> it<00:05:10.170> simply<00:05:10.890> just<00:05:10.920> hashed 00:05:11.540 --> 00:05:11.550 align:start position:0% that information it simply just hashed 00:05:11.550 --> 00:05:12.770 align:start position:0% that information it simply just hashed it<00:05:11.820> and<00:05:11.970> threw<00:05:12.180> all<00:05:12.300> that<00:05:12.330> stuff<00:05:12.570> away<00:05:12.660> and 00:05:12.770 --> 00:05:12.780 align:start position:0% it and threw all that stuff away and 00:05:12.780 --> 00:05:14.780 align:start position:0% it and threw all that stuff away and gave<00:05:13.050> you<00:05:13.110> back<00:05:13.260> the<00:05:13.380> hash<00:05:13.560> so<00:05:14.430> I<00:05:14.460> think<00:05:14.640> makes 00:05:14.780 --> 00:05:14.790 align:start position:0% gave you back the hash so I think makes 00:05:14.790 --> 00:05:16.250 align:start position:0% gave you back the hash so I think makes a<00:05:14.820> lot<00:05:14.850> more<00:05:14.970> sense<00:05:15.060> to<00:05:15.300> return<00:05:15.570> the<00:05:15.810> hash<00:05:15.990> this 00:05:16.250 --> 00:05:16.260 align:start position:0% a lot more sense to return the hash this 00:05:16.260 --> 00:05:18.560 align:start position:0% a lot more sense to return the hash this gives<00:05:16.440> you<00:05:16.500> a<00:05:16.530> lot<00:05:16.650> of<00:05:16.680> advantages<00:05:17.570> the 00:05:18.560 --> 00:05:18.570 align:start position:0% gives you a lot of advantages the 00:05:18.570 --> 00:05:20.240 align:start position:0% gives you a lot of advantages the biggest<00:05:19.080> one<00:05:19.230> being<00:05:19.410> that<00:05:19.650> if<00:05:19.860> you<00:05:19.920> deploy<00:05:20.220> a 00:05:20.240 --> 00:05:20.250 align:start position:0% biggest one being that if you deploy a 00:05:20.250 --> 00:05:22.850 align:start position:0% biggest one being that if you deploy a contract<00:05:20.730> you<00:05:20.910> can<00:05:21.030> instantly<00:05:21.480> know<00:05:21.750> what<00:05:22.590> the 00:05:22.850 --> 00:05:22.860 align:start position:0% contract you can instantly know what the 00:05:22.860 --> 00:05:24.650 align:start position:0% contract you can instantly know what the thank<00:05:23.340> you<00:05:23.430> you<00:05:23.970> can<00:05:24.000> instantly<00:05:24.270> know<00:05:24.450> what 00:05:24.650 --> 00:05:24.660 align:start position:0% thank you you can instantly know what 00:05:24.660 --> 00:05:27.590 align:start position:0% thank you you can instantly know what the<00:05:24.840> the<00:05:25.310> contract<00:05:26.310> address<00:05:26.670> is<00:05:26.910> going<00:05:27.360> to<00:05:27.480> be 00:05:27.590 --> 00:05:27.600 align:start position:0% the the contract address is going to be 00:05:27.600 --> 00:05:30.830 align:start position:0% the the contract address is going to be once<00:05:27.960> it's<00:05:28.110> mined<00:05:28.850> right<00:05:29.850> that's<00:05:30.630> kind<00:05:30.810> of 00:05:30.830 --> 00:05:30.840 align:start position:0% once it's mined right that's kind of 00:05:30.840 --> 00:05:33.140 align:start position:0% once it's mined right that's kind of what<00:05:31.050> this<00:05:31.230> slide<00:05:31.560> explains<00:05:31.940> I'm<00:05:32.940> getting 00:05:33.140 --> 00:05:33.150 align:start position:0% what this slide explains I'm getting 00:05:33.150 --> 00:05:35.360 align:start position:0% what this slide explains I'm getting ahead<00:05:33.210> myself<00:05:33.570> but<00:05:33.810> yes<00:05:34.230> the<00:05:35.040> last<00:05:35.130> thing<00:05:35.280> I 00:05:35.360 --> 00:05:35.370 align:start position:0% ahead myself but yes the last thing I 00:05:35.370 --> 00:05:39.440 align:start position:0% ahead myself but yes the last thing I said<00:05:35.430> apply<00:05:35.790> to<00:05:35.850> the<00:05:35.970> slide<00:05:36.620> 2d<00:05:37.730> this<00:05:38.730> for<00:05:39.000> me<00:05:39.120> I 00:05:39.440 --> 00:05:39.450 align:start position:0% said apply to the slide 2d this for me I 00:05:39.450 --> 00:05:41.480 align:start position:0% said apply to the slide 2d this for me I often<00:05:40.020> go<00:05:40.110> on<00:05:40.200> record<00:05:40.350> saying<00:05:40.620> like<00:05:40.800> if<00:05:40.920> ENS<00:05:41.340> is 00:05:41.480 --> 00:05:41.490 align:start position:0% often go on record saying like if ENS is 00:05:41.490 --> 00:05:42.860 align:start position:0% often go on record saying like if ENS is the<00:05:41.580> only<00:05:41.790> thing<00:05:42.240> that<00:05:42.420> comes<00:05:42.630> out<00:05:42.810> of 00:05:42.860 --> 00:05:42.870 align:start position:0% the only thing that comes out of 00:05:42.870 --> 00:05:45.530 align:start position:0% the only thing that comes out of aetherium<00:05:43.380> that<00:05:44.010> aetherium<00:05:44.520> has<00:05:44.640> been<00:05:44.790> a<00:05:44.940> wild 00:05:45.530 --> 00:05:45.540 align:start position:0% aetherium that aetherium has been a wild 00:05:45.540 --> 00:05:48.350 align:start position:0% aetherium that aetherium has been a wild success<00:05:45.660> like<00:05:46.080> E&S<00:05:46.530> people<00:05:47.190> again<00:05:47.970> talk<00:05:48.180> to<00:05:48.270> me 00:05:48.350 --> 00:05:48.360 align:start position:0% success like E&S people again talk to me 00:05:48.360 --> 00:05:50.810 align:start position:0% success like E&S people again talk to me afterwards<00:05:48.750> like<00:05:48.900> I<00:05:49.080> I<00:05:49.980> will<00:05:50.250> talk<00:05:50.460> for<00:05:50.640> hours 00:05:50.810 --> 00:05:50.820 align:start position:0% afterwards like I I will talk for hours 00:05:50.820 --> 00:05:53.510 align:start position:0% afterwards like I I will talk for hours about<00:05:51.270> how<00:05:51.630> ENS<00:05:52.230> is<00:05:52.440> like<00:05:52.620> the<00:05:52.980> biggest<00:05:53.220> game 00:05:53.510 --> 00:05:53.520 align:start position:0% about how ENS is like the biggest game 00:05:53.520 --> 00:05:55.640 align:start position:0% about how ENS is like the biggest game changer<00:05:53.940> in<00:05:54.300> the<00:05:54.690> crypto<00:05:55.020> space<00:05:55.260> like<00:05:55.470> I<00:05:55.590> don't 00:05:55.640 --> 00:05:55.650 align:start position:0% changer in the crypto space like I don't 00:05:55.650 --> 00:05:58.180 align:start position:0% changer in the crypto space like I don't even<00:05:55.890> care<00:05:56.190> about<00:05:56.250> yeah<00:05:56.820> exactly<00:05:57.000> yeah 00:05:58.180 --> 00:05:58.190 align:start position:0% even care about yeah exactly yeah 00:05:58.190 --> 00:06:00.640 align:start position:0% even care about yeah exactly yeah UNESCO<00:05:59.190> get<00:05:59.490> your<00:05:59.610> stickers<00:05:59.910> later<00:06:00.090> everyone 00:06:00.640 --> 00:06:00.650 align:start position:0% UNESCO get your stickers later everyone 00:06:00.650 --> 00:06:04.910 align:start position:0% UNESCO get your stickers later everyone the<00:06:02.810> so<00:06:03.810> es<00:06:04.110> is<00:06:04.260> really<00:06:04.440> cool<00:06:04.560> because<00:06:04.710> you<00:06:04.800> get 00:06:04.910 --> 00:06:04.920 align:start position:0% the so es is really cool because you get 00:06:04.920 --> 00:06:06.050 align:start position:0% the so es is really cool because you get these<00:06:05.070> named<00:06:05.340> things<00:06:05.640> it's<00:06:05.790> kind<00:06:05.910> of<00:06:05.940> like 00:06:06.050 --> 00:06:06.060 align:start position:0% these named things it's kind of like 00:06:06.060 --> 00:06:07.460 align:start position:0% these named things it's kind of like dynamic<00:06:06.480> linking<00:06:06.780> it<00:06:06.930> means<00:06:07.080> that<00:06:07.230> if<00:06:07.320> your 00:06:07.460 --> 00:06:07.470 align:start position:0% dynamic linking it means that if your 00:06:07.470 --> 00:06:09.440 align:start position:0% dynamic linking it means that if your app<00:06:07.620> depends<00:06:08.100> on<00:06:08.160> a<00:06:08.190> contract<00:06:08.670> you<00:06:09.240> can 00:06:09.440 --> 00:06:09.450 align:start position:0% app depends on a contract you can 00:06:09.450 --> 00:06:11.270 align:start position:0% app depends on a contract you can actually<00:06:09.660> and<00:06:10.110> you<00:06:10.380> can<00:06:10.530> choose<00:06:10.740> static<00:06:11.160> if 00:06:11.270 --> 00:06:11.280 align:start position:0% actually and you can choose static if 00:06:11.280 --> 00:06:12.200 align:start position:0% actually and you can choose static if you<00:06:11.310> want<00:06:11.460> put<00:06:11.550> an<00:06:11.670> address<00:06:11.820> in<00:06:12.000> there<00:06:12.090> or 00:06:12.200 --> 00:06:12.210 align:start position:0% you want put an address in there or 00:06:12.210 --> 00:06:14.540 align:start position:0% you want put an address in there or dynamic<00:06:12.630> people<00:06:12.750> use<00:06:12.960> an<00:06:13.230> ENS<00:06:13.650> name<00:06:13.860> but<00:06:14.460> it 00:06:14.540 --> 00:06:14.550 align:start position:0% dynamic people use an ENS name but it 00:06:14.550 --> 00:06:16.370 align:start position:0% dynamic people use an ENS name but it means<00:06:14.610> if<00:06:14.790> you<00:06:14.880> update<00:06:15.210> your<00:06:15.300> contract<00:06:15.810> all 00:06:16.370 --> 00:06:16.380 align:start position:0% means if you update your contract all 00:06:16.380 --> 00:06:17.990 align:start position:0% means if you update your contract all those<00:06:16.830> places<00:06:17.100> you've<00:06:17.370> deployed<00:06:17.640> code 00:06:17.990 --> 00:06:18.000 align:start position:0% those places you've deployed code 00:06:18.000 --> 00:06:20.060 align:start position:0% those places you've deployed code including<00:06:18.750> maybe<00:06:18.870> e<00:06:18.990> and<00:06:19.230> s<00:06:19.350> where<00:06:19.830> there's<00:06:20.010> a 00:06:20.060 --> 00:06:20.070 align:start position:0% including maybe e and s where there's a 00:06:20.070 --> 00:06:21.950 align:start position:0% including maybe e and s where there's a hash<00:06:20.280> and<00:06:20.310> you<00:06:20.610> can't<00:06:20.940> ever<00:06:21.180> actually<00:06:21.510> change 00:06:21.950 --> 00:06:21.960 align:start position:0% hash and you can't ever actually change 00:06:21.960 --> 00:06:24.910 align:start position:0% hash and you can't ever actually change it<00:06:22.110> just<00:06:22.890> continue<00:06:23.820> to<00:06:23.910> work<00:06:24.030> your<00:06:24.060> upgraded 00:06:24.910 --> 00:06:24.920 align:start position:0% it just continue to work your upgraded 00:06:24.920 --> 00:06:26.840 align:start position:0% it just continue to work your upgraded contract<00:06:25.920> goes<00:06:26.070> off<00:06:26.190> to<00:06:26.280> the<00:06:26.310> races<00:06:26.490> it's 00:06:26.840 --> 00:06:26.850 align:start position:0% contract goes off to the races it's 00:06:26.850 --> 00:06:29.240 align:start position:0% contract goes off to the races it's happy<00:06:27.120> and<00:06:27.300> functioning<00:06:28.260> so<00:06:28.860> you<00:06:28.950> can<00:06:29.040> use<00:06:29.160> it 00:06:29.240 --> 00:06:29.250 align:start position:0% happy and functioning so you can use it 00:06:29.250 --> 00:06:31.010 align:start position:0% happy and functioning so you can use it anywhere<00:06:29.490> if<00:06:29.970> you're<00:06:30.120> sending<00:06:30.330> a<00:06:30.480> transaction 00:06:31.010 --> 00:06:31.020 align:start position:0% anywhere if you're sending a transaction 00:06:31.020 --> 00:06:34.160 align:start position:0% anywhere if you're sending a transaction if<00:06:31.260> you<00:06:31.680> have<00:06:31.770> a<00:06:31.800> ERC<00:06:32.430> 20<00:06:32.730> token<00:06:33.360> contract<00:06:33.930> and 00:06:34.160 --> 00:06:34.170 align:start position:0% if you have a ERC 20 token contract and 00:06:34.170 --> 00:06:36.680 align:start position:0% if you have a ERC 20 token contract and you've<00:06:34.410> got<00:06:34.590> a<00:06:34.860> to<00:06:35.580> address<00:06:35.970> in<00:06:36.150> amount<00:06:36.390> that 00:06:36.680 --> 00:06:36.690 align:start position:0% you've got a to address in amount that 00:06:36.690 --> 00:06:39.200 align:start position:0% you've got a to address in amount that to<00:06:36.870> address<00:06:37.080> can<00:06:37.410> just<00:06:37.650> be<00:06:37.860> Rick<00:06:38.550> muta<00:06:38.850> Firefly 00:06:39.200 --> 00:06:39.210 align:start position:0% to address can just be Rick muta Firefly 00:06:39.210 --> 00:06:41.340 align:start position:0% to address can just be Rick muta Firefly eath<00:06:39.570> and<00:06:39.840> it<00:06:40.380> will<00:06:40.470> be<00:06:40.560> parsed 00:06:41.340 --> 00:06:41.350 align:start position:0% eath and it will be parsed 00:06:41.350 --> 00:06:43.080 align:start position:0% eath and it will be parsed for<00:06:41.440> you<00:06:41.560> and<00:06:41.740> figured<00:06:41.980> out<00:06:42.130> at<00:06:42.310> deploy<00:06:42.790> time 00:06:43.080 --> 00:06:43.090 align:start position:0% for you and figured out at deploy time 00:06:43.090 --> 00:06:45.090 align:start position:0% for you and figured out at deploy time calling<00:06:43.960> a<00:06:44.110> contract<00:06:44.590> is<00:06:44.680> already<00:06:44.860> a 00:06:45.090 --> 00:06:45.100 align:start position:0% calling a contract is already a 00:06:45.100 --> 00:06:48.240 align:start position:0% calling a contract is already a synchronous<00:06:45.520> there's<00:06:45.790> no<00:06:46.030> additional<00:06:46.360> cost 00:06:48.240 --> 00:06:48.250 align:start position:0% synchronous there's no additional cost 00:06:48.250 --> 00:06:51.750 align:start position:0% synchronous there's no additional cost oh<00:06:48.570> yes<00:06:49.570> Hugh<00:06:49.810> and<00:06:49.870> real<00:06:50.020> api's<00:06:50.580> okay<00:06:51.580> I'm<00:06:51.700> at 00:06:51.750 --> 00:06:51.760 align:start position:0% oh yes Hugh and real api's okay I'm at 00:06:51.760 --> 00:06:56.220 align:start position:0% oh yes Hugh and real api's okay I'm at three<00:06:52.090> I<00:06:52.120> guess<00:06:53.400> so<00:06:54.400> I<00:06:54.850> was<00:06:55.720> also<00:06:55.930> a<00:06:55.960> strange 00:06:56.220 --> 00:06:56.230 align:start position:0% three I guess so I was also a strange 00:06:56.230 --> 00:06:58.320 align:start position:0% three I guess so I was also a strange idea<00:06:56.500> we<00:06:56.650> have<00:06:56.860> this<00:06:57.070> machine<00:06:57.700> readable<00:06:58.060> code 00:06:58.320 --> 00:06:58.330 align:start position:0% idea we have this machine readable code 00:06:58.330 --> 00:07:00.420 align:start position:0% idea we have this machine readable code in<00:06:58.660> the<00:06:58.780> form<00:06:58.900> of<00:06:59.050> solidity<00:06:59.470> so<00:07:00.250> we've<00:07:00.370> all 00:07:00.420 --> 00:07:00.430 align:start position:0% in the form of solidity so we've all 00:07:00.430 --> 00:07:01.530 align:start position:0% in the form of solidity so we've all these<00:07:00.550> signatures<00:07:01.060> that<00:07:01.180> are<00:07:01.270> machine 00:07:01.530 --> 00:07:01.540 align:start position:0% these signatures that are machine 00:07:01.540 --> 00:07:03.090 align:start position:0% these signatures that are machine readable<00:07:01.840> and<00:07:02.110> actually<00:07:02.470> sort<00:07:02.710> of<00:07:02.830> human 00:07:03.090 --> 00:07:03.100 align:start position:0% readable and actually sort of human 00:07:03.100 --> 00:07:05.220 align:start position:0% readable and actually sort of human readable<00:07:03.370> and<00:07:03.580> so<00:07:04.120> we<00:07:04.240> take<00:07:04.450> that<00:07:04.480> that 00:07:05.220 --> 00:07:05.230 align:start position:0% readable and so we take that that 00:07:05.230 --> 00:07:07.080 align:start position:0% readable and so we take that that machine<00:07:05.830> and<00:07:06.040> human<00:07:06.250> readable<00:07:06.460> code<00:07:06.760> and<00:07:07.000> we 00:07:07.080 --> 00:07:07.090 align:start position:0% machine and human readable code and we 00:07:07.090 --> 00:07:08.940 align:start position:0% machine and human readable code and we turn<00:07:07.240> it<00:07:07.360> into<00:07:07.420> this<00:07:07.630> like<00:07:08.110> machine<00:07:08.620> readable 00:07:08.940 --> 00:07:08.950 align:start position:0% turn it into this like machine readable 00:07:08.950 --> 00:07:11.520 align:start position:0% turn it into this like machine readable code<00:07:09.270> it's<00:07:10.270> complicated<00:07:10.900> so<00:07:11.050> this<00:07:11.350> is<00:07:11.500> a 00:07:11.520 --> 00:07:11.530 align:start position:0% code it's complicated so this is a 00:07:11.530 --> 00:07:13.680 align:start position:0% code it's complicated so this is a simple<00:07:12.130> API<00:07:12.190> it's<00:07:12.640> six<00:07:12.970> kilobytes<00:07:13.420> worth<00:07:13.540> of 00:07:13.680 --> 00:07:13.690 align:start position:0% simple API it's six kilobytes worth of 00:07:13.690 --> 00:07:15.960 align:start position:0% simple API it's six kilobytes worth of JSON<00:07:13.930> which<00:07:14.620> is<00:07:14.770> kind<00:07:15.370> of<00:07:15.400> ludicrous<00:07:15.520> as 00:07:15.960 --> 00:07:15.970 align:start position:0% JSON which is kind of ludicrous as 00:07:15.970 --> 00:07:19.530 align:start position:0% JSON which is kind of ludicrous as opposed<00:07:16.660> to<00:07:17.520> like<00:07:18.520> it's<00:07:18.820> human<00:07:19.060> readable<00:07:19.390> and 00:07:19.530 --> 00:07:19.540 align:start position:0% opposed to like it's human readable and 00:07:19.540 --> 00:07:21.180 align:start position:0% opposed to like it's human readable and machine<00:07:19.810> readable<00:07:19.840> just<00:07:20.440> use<00:07:20.680> the<00:07:20.890> solidity 00:07:21.180 --> 00:07:21.190 align:start position:0% machine readable just use the solidity 00:07:21.190 --> 00:07:23.160 align:start position:0% machine readable just use the solidity contract<00:07:21.640> so<00:07:21.730> if<00:07:21.820> you<00:07:21.850> look<00:07:22.090> I<00:07:22.330> can't<00:07:22.870> point 00:07:23.160 --> 00:07:23.170 align:start position:0% contract so if you look I can't point 00:07:23.170 --> 00:07:26.130 align:start position:0% contract so if you look I can't point the<00:07:23.530> thingy<00:07:23.740> but<00:07:24.700> this<00:07:24.940> is<00:07:25.150> like<00:07:25.510> all<00:07:25.720> you<00:07:25.960> need 00:07:26.130 --> 00:07:26.140 align:start position:0% the thingy but this is like all you need 00:07:26.140 --> 00:07:28.380 align:start position:0% the thingy but this is like all you need you<00:07:26.170> just<00:07:26.500> need<00:07:26.560> the<00:07:26.710> signatures<00:07:27.280> we<00:07:28.210> can 00:07:28.380 --> 00:07:28.390 align:start position:0% you just need the signatures we can 00:07:28.390 --> 00:07:30.000 align:start position:0% you just need the signatures we can parse<00:07:28.660> that<00:07:28.930> for<00:07:29.140> you<00:07:29.290> and<00:07:29.530> figure<00:07:29.800> out<00:07:29.830> what 00:07:30.000 --> 00:07:30.010 align:start position:0% parse that for you and figure out what 00:07:30.010 --> 00:07:32.580 align:start position:0% parse that for you and figure out what the<00:07:30.100> ABI<00:07:30.370> should<00:07:30.940> be<00:07:31.090> and<00:07:31.360> the<00:07:32.200> nice<00:07:32.350> thing<00:07:32.560> is 00:07:32.580 --> 00:07:32.590 align:start position:0% the ABI should be and the nice thing is 00:07:32.590 --> 00:07:33.990 align:start position:0% the ABI should be and the nice thing is if<00:07:32.770> you<00:07:32.830> look<00:07:32.890> at<00:07:33.070> the<00:07:33.130> source<00:07:33.340> code<00:07:33.430> like<00:07:33.970> you 00:07:33.990 --> 00:07:34.000 align:start position:0% if you look at the source code like you 00:07:34.000 --> 00:07:37.800 align:start position:0% if you look at the source code like you think<00:07:34.240> you<00:07:34.300> you<00:07:35.080> understand<00:07:36.570> what<00:07:37.570> this 00:07:37.800 --> 00:07:37.810 align:start position:0% think you you understand what this 00:07:37.810 --> 00:07:39.330 align:start position:0% think you you understand what this contract<00:07:38.200> is<00:07:38.290> doing<00:07:38.560> most<00:07:38.830> the<00:07:38.890> time<00:07:39.070> you<00:07:39.160> pull 00:07:39.330 --> 00:07:39.340 align:start position:0% contract is doing most the time you pull 00:07:39.340 --> 00:07:42.360 align:start position:0% contract is doing most the time you pull this<00:07:39.400> big<00:07:39.760> opaque<00:07:40.090> piece<00:07:40.300> of<00:07:40.450> JSON<00:07:40.840> in<00:07:41.020> and<00:07:41.370> now 00:07:42.360 --> 00:07:42.370 align:start position:0% this big opaque piece of JSON in and now 00:07:42.370 --> 00:07:44.220 align:start position:0% this big opaque piece of JSON in and now the<00:07:42.430> rest<00:07:42.640> of<00:07:42.700> the<00:07:42.790> code<00:07:42.970> you<00:07:43.300> totally<00:07:43.960> don't 00:07:44.220 --> 00:07:44.230 align:start position:0% the rest of the code you totally don't 00:07:44.230 --> 00:07:45.870 align:start position:0% the rest of the code you totally don't really<00:07:44.620> know<00:07:44.710> what's<00:07:44.830> going<00:07:45.010> on<00:07:45.160> whereas<00:07:45.790> this 00:07:45.870 --> 00:07:45.880 align:start position:0% really know what's going on whereas this 00:07:45.880 --> 00:07:47.550 align:start position:0% really know what's going on whereas this is<00:07:46.000> very<00:07:46.150> obvious<00:07:46.510> what<00:07:46.840> the<00:07:46.960> api's<00:07:47.350> are 00:07:47.550 --> 00:07:47.560 align:start position:0% is very obvious what the api's are 00:07:47.560 --> 00:07:49.820 align:start position:0% is very obvious what the api's are available<00:07:48.010> to<00:07:48.100> you<00:07:48.250> if<00:07:48.970> you<00:07:49.060> just<00:07:49.180> use<00:07:49.330> them 00:07:49.820 --> 00:07:49.830 align:start position:0% available to you if you just use them 00:07:49.830 --> 00:07:52.470 align:start position:0% available to you if you just use them makes<00:07:50.830> code<00:07:51.010> readable<00:07:51.580> I<00:07:51.700> think<00:07:52.210> readability 00:07:52.470 --> 00:07:52.480 align:start position:0% makes code readable I think readability 00:07:52.480 --> 00:07:53.850 align:start position:0% makes code readable I think readability is<00:07:52.720> very<00:07:52.900> important<00:07:53.230> especially<00:07:53.320> in<00:07:53.560> terms<00:07:53.710> of 00:07:53.850 --> 00:07:53.860 align:start position:0% is very important especially in terms of 00:07:53.860 --> 00:07:58.290 align:start position:0% is very important especially in terms of audits<00:07:54.730> and<00:07:55.120> like<00:07:55.390> just<00:07:56.110> trusts<00:07:56.620> oh<00:07:56.830> oh<00:07:57.300> sorry 00:07:58.290 --> 00:07:58.300 align:start position:0% audits and like just trusts oh oh sorry 00:07:58.300 --> 00:08:00.570 align:start position:0% audits and like just trusts oh oh sorry I<00:07:58.600> think<00:07:59.500> I'm<00:07:59.710> almost<00:07:59.800> through<00:08:00.220> my<00:08:00.340> slides 00:08:00.570 --> 00:08:00.580 align:start position:0% I think I'm almost through my slides 00:08:00.580 --> 00:08:04.320 align:start position:0% I think I'm almost through my slides sort<00:08:01.570> of<00:08:01.690> but<00:08:02.140> ABI<00:08:02.980> v2<00:08:03.370> so<00:08:03.670> like<00:08:03.940> I<00:08:04.030> said<00:08:04.090> we've 00:08:04.320 --> 00:08:04.330 align:start position:0% sort of but ABI v2 so like I said we've 00:08:04.330 --> 00:08:06.690 align:start position:0% sort of but ABI v2 so like I said we've supported<00:08:04.570> ABI<00:08:05.380> v2<00:08:05.890> for<00:08:06.220> over<00:08:06.490> a<00:08:06.520> year<00:08:06.580> now 00:08:06.690 --> 00:08:06.700 align:start position:0% supported ABI v2 for over a year now 00:08:06.700 --> 00:08:09.410 align:start position:0% supported ABI v2 for over a year now that's<00:08:07.510> basically<00:08:08.050> you<00:08:08.200> can<00:08:08.320> pass<00:08:08.470> trucks<00:08:08.770> in 00:08:09.410 --> 00:08:09.420 align:start position:0% that's basically you can pass trucks in 00:08:09.420 --> 00:08:12.210 align:start position:0% that's basically you can pass trucks in arrays<00:08:10.420> of<00:08:10.630> strings<00:08:10.750> it's<00:08:11.680> actually<00:08:12.010> kind<00:08:12.190> of 00:08:12.210 --> 00:08:12.220 align:start position:0% arrays of strings it's actually kind of 00:08:12.220 --> 00:08:13.800 align:start position:0% arrays of strings it's actually kind of cool<00:08:12.370> web<00:08:12.580> 3<00:08:12.790> now<00:08:12.910> supports<00:08:13.330> it<00:08:13.420> if<00:08:13.540> you<00:08:13.630> take<00:08:13.750> a 00:08:13.800 --> 00:08:13.810 align:start position:0% cool web 3 now supports it if you take a 00:08:13.810 --> 00:08:15.690 align:start position:0% cool web 3 now supports it if you take a look<00:08:13.900> at<00:08:14.020> web<00:08:14.140> 3s<00:08:14.350> implementation<00:08:14.890> it's 00:08:15.690 --> 00:08:15.700 align:start position:0% look at web 3s implementation it's 00:08:15.700 --> 00:08:18.330 align:start position:0% look at web 3s implementation it's require<00:08:16.150> ethers<00:08:16.810> slash<00:08:17.260> utils<00:08:17.710> slash<00:08:17.980> ABI 00:08:18.330 --> 00:08:18.340 align:start position:0% require ethers slash utils slash ABI 00:08:18.340 --> 00:08:21.120 align:start position:0% require ethers slash utils slash ABI coder<00:08:18.640> it's<00:08:19.600> an<00:08:19.720> awesome<00:08:19.930> solution<00:08:20.290> and<00:08:20.710> it 00:08:21.120 --> 00:08:21.130 align:start position:0% coder it's an awesome solution and it 00:08:21.130 --> 00:08:22.740 align:start position:0% coder it's an awesome solution and it means<00:08:21.280> we<00:08:21.400> have<00:08:21.490> like<00:08:21.610> one<00:08:21.880> good<00:08:22.360> working 00:08:22.740 --> 00:08:22.750 align:start position:0% means we have like one good working 00:08:22.750 --> 00:08:25.050 align:start position:0% means we have like one good working solution<00:08:23.170> that<00:08:23.260> everyone<00:08:23.440> can<00:08:23.620> use<00:08:23.650> and<00:08:24.100> we're 00:08:25.050 --> 00:08:25.060 align:start position:0% solution that everyone can use and we're 00:08:25.060 --> 00:08:27.320 align:start position:0% solution that everyone can use and we're off<00:08:25.150> to<00:08:25.180> the<00:08:25.330> races 00:08:27.320 --> 00:08:27.330 align:start position:0% off to the races 00:08:27.330 --> 00:08:29.520 align:start position:0% off to the races extras<00:08:28.330> promise<00:08:28.780> friendly<00:08:29.140> you<00:08:29.500> can 00:08:29.520 --> 00:08:29.530 align:start position:0% extras promise friendly you can 00:08:29.530 --> 00:08:31.440 align:start position:0% extras promise friendly you can basically<00:08:30.040> pass<00:08:30.250> promises<00:08:30.790> in<00:08:30.910> anywhere<00:08:31.360> you 00:08:31.440 --> 00:08:31.450 align:start position:0% basically pass promises in anywhere you 00:08:31.450 --> 00:08:33.659 align:start position:0% basically pass promises in anywhere you could<00:08:31.570> pass<00:08:31.690> a<00:08:31.720> thing<00:08:32.110> in<00:08:32.349> a<00:08:32.590> lot<00:08:33.460> of 00:08:33.659 --> 00:08:33.669 align:start position:0% could pass a thing in a lot of 00:08:33.669 --> 00:08:35.400 align:start position:0% could pass a thing in a lot of blockchain<00:08:34.060> things<00:08:34.330> are<00:08:34.690> asynchronous<00:08:35.080> and 00:08:35.400 --> 00:08:35.410 align:start position:0% blockchain things are asynchronous and 00:08:35.410 --> 00:08:37.010 align:start position:0% blockchain things are asynchronous and so<00:08:35.500> for<00:08:35.620> example<00:08:35.890> if<00:08:35.950> you<00:08:36.010> have<00:08:36.099> a<00:08:36.160> transaction 00:08:37.010 --> 00:08:37.020 align:start position:0% so for example if you have a transaction 00:08:37.020 --> 00:08:39.060 align:start position:0% so for example if you have a transaction one<00:08:38.020> of<00:08:38.080> the<00:08:38.140> things<00:08:38.260> you<00:08:38.349> pass<00:08:38.530> in<00:08:38.710> is<00:08:38.830> a<00:08:38.860> nonce 00:08:39.060 --> 00:08:39.070 align:start position:0% one of the things you pass in is a nonce 00:08:39.070 --> 00:08:42.330 align:start position:0% one of the things you pass in is a nonce well<00:08:39.820> you<00:08:40.479> can<00:08:40.599> just<00:08:40.750> pass<00:08:40.900> in<00:08:41.200> a<00:08:41.229> promise<00:08:42.219> that 00:08:42.330 --> 00:08:42.340 align:start position:0% well you can just pass in a promise that 00:08:42.340 --> 00:08:44.730 align:start position:0% well you can just pass in a promise that resolves<00:08:42.760> to<00:08:42.820> the<00:08:42.940> nonce<00:08:43.120> as<00:08:43.419> your<00:08:43.750> nonce<00:08:44.380> and 00:08:44.730 --> 00:08:44.740 align:start position:0% resolves to the nonce as your nonce and 00:08:44.740 --> 00:08:46.740 align:start position:0% resolves to the nonce as your nonce and again<00:08:45.730> everything<00:08:46.030> is<00:08:46.060> asynchronous<00:08:46.300> it<00:08:46.630> can 00:08:46.740 --> 00:08:46.750 align:start position:0% again everything is asynchronous it can 00:08:46.750 --> 00:08:48.990 align:start position:0% again everything is asynchronous it can be<00:08:46.840> resolved<00:08:47.200> a<00:08:47.380> bit<00:08:47.950> 39m<00:08:48.370> onyx<00:08:48.640> we<00:08:48.760> support 00:08:48.990 --> 00:08:49.000 align:start position:0% be resolved a bit 39m onyx we support 00:08:49.000 --> 00:08:51.329 align:start position:0% be resolved a bit 39m onyx we support English<00:08:49.270> Spanish<00:08:49.750> French<00:08:49.990> Italian<00:08:50.530> Japanese 00:08:51.329 --> 00:08:51.339 align:start position:0% English Spanish French Italian Japanese 00:08:51.339 --> 00:08:54.269 align:start position:0% English Spanish French Italian Japanese Korean<00:08:51.610> and<00:08:52.510> both<00:08:53.320> simplified<00:08:53.740> in 00:08:54.269 --> 00:08:54.279 align:start position:0% Korean and both simplified in 00:08:54.279 --> 00:08:57.720 align:start position:0% Korean and both simplified in traditional<00:08:54.610> Chinese<00:08:56.370> yes 00:08:57.720 --> 00:08:57.730 align:start position:0% traditional Chinese yes 00:08:57.730 --> 00:08:59.670 align:start position:0% traditional Chinese yes utilities<00:08:58.569> we've<00:08:58.839> got<00:08:58.930> lots<00:08:59.079> of<00:08:59.170> utilities 00:08:59.670 --> 00:08:59.680 align:start position:0% utilities we've got lots of utilities 00:08:59.680 --> 00:09:02.629 align:start position:0% utilities we've got lots of utilities for<00:08:59.949> dealing<00:09:00.100> with<00:09:00.339> one<00:09:00.730> minute<00:09:00.879> okay 00:09:02.629 --> 00:09:02.639 align:start position:0% for dealing with one minute okay 00:09:02.639 --> 00:09:05.939 align:start position:0% for dealing with one minute okay avi<00:09:03.639> yeah<00:09:04.089> so<00:09:04.300> basically<00:09:04.569> stuff<00:09:05.499> these<00:09:05.680> slides 00:09:05.939 --> 00:09:05.949 align:start position:0% avi yeah so basically stuff these slides 00:09:05.949 --> 00:09:08.369 align:start position:0% avi yeah so basically stuff these slides will<00:09:06.100> be<00:09:06.129> available<00:09:06.220> online<00:09:06.689> I<00:09:07.689> try<00:09:08.170> to<00:09:08.230> make 00:09:08.369 --> 00:09:08.379 align:start position:0% will be available online I try to make 00:09:08.379 --> 00:09:10.949 align:start position:0% will be available online I try to make everything<00:09:08.769> as<00:09:09.160> possibly<00:09:09.850> available<00:09:10.240> as<00:09:10.720> I 00:09:10.949 --> 00:09:10.959 align:start position:0% everything as possibly available as I 00:09:10.959 --> 00:09:13.470 align:start position:0% everything as possibly available as I can<00:09:11.290> and<00:09:11.620> the<00:09:12.129> rest<00:09:12.339> are<00:09:12.519> just<00:09:12.550> examples<00:09:12.970> I<00:09:13.329> was 00:09:13.470 --> 00:09:13.480 align:start position:0% can and the rest are just examples I was 00:09:13.480 --> 00:09:14.759 align:start position:0% can and the rest are just examples I was not<00:09:13.689> really<00:09:13.809> planning<00:09:14.170> to<00:09:14.259> show<00:09:14.470> these<00:09:14.620> off 00:09:14.759 --> 00:09:14.769 align:start position:0% not really planning to show these off 00:09:14.769 --> 00:09:16.499 align:start position:0% not really planning to show these off these<00:09:15.040> are<00:09:15.069> just<00:09:15.279> in<00:09:15.459> the<00:09:15.699> slide<00:09:15.970> deck<00:09:16.149> so<00:09:16.360> when 00:09:16.499 --> 00:09:16.509 align:start position:0% these are just in the slide deck so when 00:09:16.509 --> 00:09:17.939 align:start position:0% these are just in the slide deck so when you<00:09:16.569> look<00:09:16.689> at<00:09:16.749> the<00:09:16.809> slides<00:09:16.990> afterwards<00:09:17.379> you 00:09:17.939 --> 00:09:17.949 align:start position:0% you look at the slides afterwards you 00:09:17.949 --> 00:09:20.160 align:start position:0% you look at the slides afterwards you can<00:09:18.040> kind<00:09:18.249> of<00:09:18.279> get<00:09:18.399> an<00:09:18.490> example<00:09:18.790> of<00:09:19.209> it's<00:09:19.899> easy 00:09:20.160 --> 00:09:20.170 align:start position:0% can kind of get an example of it's easy 00:09:20.170 --> 00:09:21.960 align:start position:0% can kind of get an example of it's easy to<00:09:20.350> use<00:09:20.499> you<00:09:20.769> just<00:09:20.800> pick<00:09:21.279> it<00:09:21.309> up<00:09:21.459> and<00:09:21.639> start 00:09:21.960 --> 00:09:21.970 align:start position:0% to use you just pick it up and start 00:09:21.970 --> 00:09:23.460 align:start position:0% to use you just pick it up and start using<00:09:22.089> it<00:09:22.360> there's<00:09:22.629> no<00:09:22.870> sinking<00:09:23.259> nodes 00:09:23.460 --> 00:09:23.470 align:start position:0% using it there's no sinking nodes 00:09:23.470 --> 00:09:26.369 align:start position:0% using it there's no sinking nodes there's<00:09:23.740> none<00:09:23.889> of<00:09:24.009> you<00:09:24.879> don't<00:09:25.029> need<00:09:25.379> meta 00:09:26.369 --> 00:09:26.379 align:start position:0% there's none of you don't need meta 00:09:26.379 --> 00:09:27.600 align:start position:0% there's none of you don't need meta masks<00:09:26.620> or<00:09:26.740> anything<00:09:26.860> it<00:09:27.100> just<00:09:27.129> works<00:09:27.399> out<00:09:27.519> of 00:09:27.600 --> 00:09:27.610 align:start position:0% masks or anything it just works out of 00:09:27.610 --> 00:09:31.799 align:start position:0% masks or anything it just works out of the<00:09:27.639> box<00:09:27.699> and<00:09:28.949> done<00:09:29.949> so<00:09:30.519> questions<00:09:31.269> I<00:09:31.569> think<00:09:31.629> I 00:09:31.799 --> 00:09:31.809 align:start position:0% the box and done so questions I think I 00:09:31.809 --> 00:09:41.280 align:start position:0% the box and done so questions I think I have<00:09:31.959> a<00:09:32.230> minute<00:09:32.740> maybe<00:09:32.949> half<00:09:33.550> a<00:09:33.639> minute 00:09:41.280 --> 00:09:41.290 align:start position:0% 00:09:41.290 --> 00:09:43.350 align:start position:0% you