WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:17.650 align:start position:0% [Music] 00:00:17.650 --> 00:00:17.660 align:start position:0% 00:00:17.660 --> 00:00:19.250 align:start position:0% okay 00:00:19.250 --> 00:00:19.260 align:start position:0% okay 00:00:19.260 --> 00:00:20.929 align:start position:0% okay so<00:00:19.619> my<00:00:19.800> name<00:00:19.920> is<00:00:19.980> Richard<00:00:20.160> Moore<00:00:20.580> I<00:00:20.760> go<00:00:20.880> away 00:00:20.929 --> 00:00:20.939 align:start position:0% so my name is Richard Moore I go away 00:00:20.939 --> 00:00:23.929 align:start position:0% so my name is Richard Moore I go away Rickman<00:00:21.359> online<00:00:21.600> and<00:00:22.380> so<00:00:22.500> I<00:00:22.740> write<00:00:22.859> ethereum<00:00:23.520> a 00:00:23.929 --> 00:00:23.939 align:start position:0% Rickman online and so I write ethereum a 00:00:23.939 --> 00:00:26.630 align:start position:0% Rickman online and so I write ethereum a library<00:00:24.119> called<00:00:24.420> ethersjs 00:00:26.630 --> 00:00:26.640 align:start position:0% library called ethersjs 00:00:26.640 --> 00:00:28.550 align:start position:0% library called ethersjs um<00:00:26.720> so 00:00:28.550 --> 00:00:28.560 align:start position:0% um so 00:00:28.560 --> 00:00:31.130 align:start position:0% um so what<00:00:28.800> is<00:00:28.980> ethers<00:00:29.580> it<00:00:30.119> aims<00:00:30.420> to<00:00:30.539> be<00:00:30.660> a<00:00:30.840> complete 00:00:31.130 --> 00:00:31.140 align:start position:0% what is ethers it aims to be a complete 00:00:31.140 --> 00:00:33.350 align:start position:0% what is ethers it aims to be a complete compact<00:00:31.679> and<00:00:32.220> friendly<00:00:32.640> ethereum<00:00:33.120> library 00:00:33.350 --> 00:00:33.360 align:start position:0% compact and friendly ethereum library 00:00:33.360 --> 00:00:35.810 align:start position:0% compact and friendly ethereum library that<00:00:33.600> developers<00:00:33.960> can<00:00:34.320> use<00:00:34.500> but<00:00:34.800> also<00:00:35.100> part<00:00:35.700> of 00:00:35.810 --> 00:00:35.820 align:start position:0% that developers can use but also part of 00:00:35.820 --> 00:00:38.450 align:start position:0% that developers can use but also part of user<00:00:36.120> friendliness<00:00:36.540> is 00:00:38.450 --> 00:00:38.460 align:start position:0% user friendliness is 00:00:38.460 --> 00:00:40.610 align:start position:0% user friendliness is safety<00:00:39.180> like<00:00:39.420> you<00:00:39.600> don't<00:00:39.780> let<00:00:39.960> user<00:00:40.260> don't<00:00:40.500> let 00:00:40.610 --> 00:00:40.620 align:start position:0% safety like you don't let user don't let 00:00:40.620 --> 00:00:42.049 align:start position:0% safety like you don't let user don't let the<00:00:40.739> developer<00:00:41.100> do<00:00:41.280> things<00:00:41.460> that<00:00:41.579> like<00:00:41.760> bites 00:00:42.049 --> 00:00:42.059 align:start position:0% the developer do things that like bites 00:00:42.059 --> 00:00:43.970 align:start position:0% the developer do things that like bites in<00:00:42.180> the<00:00:42.300> ass<00:00:42.360> without<00:00:42.600> realizing<00:00:43.140> it 00:00:43.970 --> 00:00:43.980 align:start position:0% in the ass without realizing it 00:00:43.980 --> 00:00:44.569 align:start position:0% in the ass without realizing it um 00:00:44.569 --> 00:00:44.579 align:start position:0% um 00:00:44.579 --> 00:00:46.010 align:start position:0% um so<00:00:44.940> one<00:00:45.059> of<00:00:45.180> the<00:00:45.180> cool<00:00:45.360> things<00:00:45.480> is<00:00:45.660> the<00:00:45.780> default 00:00:46.010 --> 00:00:46.020 align:start position:0% so one of the cool things is the default 00:00:46.020 --> 00:00:47.750 align:start position:0% so one of the cool things is the default provider<00:00:46.500> I<00:00:46.860> don't<00:00:46.980> know<00:00:47.100> where<00:00:47.460> I<00:00:47.640> should 00:00:47.750 --> 00:00:47.760 align:start position:0% provider I don't know where I should 00:00:47.760 --> 00:00:48.590 align:start position:0% provider I don't know where I should stand 00:00:48.590 --> 00:00:48.600 align:start position:0% stand 00:00:48.600 --> 00:00:51.049 align:start position:0% stand so<00:00:49.020> with<00:00:49.140> the<00:00:49.260> default<00:00:49.559> provider 00:00:51.049 --> 00:00:51.059 align:start position:0% so with the default provider 00:00:51.059 --> 00:00:53.750 align:start position:0% so with the default provider will<00:00:51.480> haul<00:00:51.920> basically<00:00:52.920> it<00:00:53.100> lets<00:00:53.399> you<00:00:53.460> just 00:00:53.750 --> 00:00:53.760 align:start position:0% will haul basically it lets you just 00:00:53.760 --> 00:00:55.430 align:start position:0% will haul basically it lets you just connect<00:00:54.059> to<00:00:54.420> ethereum 00:00:55.430 --> 00:00:55.440 align:start position:0% connect to ethereum 00:00:55.440 --> 00:00:56.990 align:start position:0% connect to ethereum um<00:00:55.500> historically<00:00:56.219> you<00:00:56.340> had<00:00:56.460> to<00:00:56.579> either<00:00:56.699> run<00:00:56.879> a 00:00:56.990 --> 00:00:57.000 align:start position:0% um historically you had to either run a 00:00:57.000 --> 00:00:58.250 align:start position:0% um historically you had to either run a node<00:00:57.239> or<00:00:57.480> you<00:00:57.600> have<00:00:57.660> to<00:00:57.780> like<00:00:57.840> sign<00:00:58.020> up<00:00:58.140> for 00:00:58.250 --> 00:00:58.260 align:start position:0% node or you have to like sign up for 00:00:58.260 --> 00:00:59.689 align:start position:0% node or you have to like sign up for inferior<00:00:58.680> you<00:00:58.860> have<00:00:58.920> to<00:00:59.039> do<00:00:59.160> something<00:00:59.399> to 00:00:59.689 --> 00:00:59.699 align:start position:0% inferior you have to do something to 00:00:59.699 --> 00:01:03.349 align:start position:0% inferior you have to do something to start<00:00:59.879> using<00:01:00.300> ether<00:01:01.140> ethereum<00:01:01.860> right<00:01:02.100> away<00:01:02.359> so 00:01:03.349 --> 00:01:03.359 align:start position:0% start using ether ethereum right away so 00:01:03.359 --> 00:01:06.109 align:start position:0% start using ether ethereum right away so we've<00:01:04.320> got<00:01:04.440> like<00:01:04.619> a<00:01:04.799> bunch<00:01:04.979> of 00:01:06.109 --> 00:01:06.119 align:start position:0% we've got like a bunch of 00:01:06.119 --> 00:01:07.730 align:start position:0% we've got like a bunch of relationships<00:01:06.900> with<00:01:07.080> these<00:01:07.260> third<00:01:07.439> party 00:01:07.730 --> 00:01:07.740 align:start position:0% relationships with these third party 00:01:07.740 --> 00:01:09.410 align:start position:0% relationships with these third party providers<00:01:08.340> and<00:01:08.580> right<00:01:08.760> off<00:01:08.880> the<00:01:09.000> bat<00:01:09.119> you<00:01:09.299> can 00:01:09.410 --> 00:01:09.420 align:start position:0% providers and right off the bat you can 00:01:09.420 --> 00:01:10.609 align:start position:0% providers and right off the bat you can just<00:01:09.540> connect<00:01:09.659> to<00:01:09.840> ethereum<00:01:10.200> start<00:01:10.439> doing 00:01:10.609 --> 00:01:10.619 align:start position:0% just connect to ethereum start doing 00:01:10.619 --> 00:01:12.770 align:start position:0% just connect to ethereum start doing Simple<00:01:10.860> Things<00:01:11.159> it's<00:01:11.939> heavily<00:01:12.240> throttled<00:01:12.659> but 00:01:12.770 --> 00:01:12.780 align:start position:0% Simple Things it's heavily throttled but 00:01:12.780 --> 00:01:14.570 align:start position:0% Simple Things it's heavily throttled but you<00:01:12.900> can<00:01:12.960> at<00:01:13.080> least<00:01:13.080> do<00:01:13.380> something<00:01:13.680> before 00:01:14.570 --> 00:01:14.580 align:start position:0% you can at least do something before 00:01:14.580 --> 00:01:16.010 align:start position:0% you can at least do something before deciding<00:01:15.060> whether<00:01:15.240> you<00:01:15.420> want<00:01:15.540> to<00:01:15.659> like<00:01:15.780> get 00:01:16.010 --> 00:01:16.020 align:start position:0% deciding whether you want to like get 00:01:16.020 --> 00:01:18.230 align:start position:0% deciding whether you want to like get your<00:01:16.140> own<00:01:16.260> inferior<00:01:16.560> ID<00:01:16.799> and<00:01:17.100> all<00:01:17.220> that<00:01:17.340> this 00:01:18.230 --> 00:01:18.240 align:start position:0% your own inferior ID and all that this 00:01:18.240 --> 00:01:19.429 align:start position:0% your own inferior ID and all that this is<00:01:18.360> all<00:01:18.420> the<00:01:18.600> old<00:01:18.659> stuff<00:01:18.840> so<00:01:19.020> I'll<00:01:19.140> just<00:01:19.260> go 00:01:19.429 --> 00:01:19.439 align:start position:0% is all the old stuff so I'll just go 00:01:19.439 --> 00:01:21.109 align:start position:0% is all the old stuff so I'll just go over<00:01:19.500> quickly<00:01:19.920> it's<00:01:20.460> written<00:01:20.700> in<00:01:20.820> typescript 00:01:21.109 --> 00:01:21.119 align:start position:0% over quickly it's written in typescript 00:01:21.119 --> 00:01:24.830 align:start position:0% over quickly it's written in typescript now<00:01:21.540> very<00:01:22.380> few<00:01:22.560> dependencies 00:01:24.830 --> 00:01:24.840 align:start position:0% now very few dependencies 00:01:24.840 --> 00:01:28.010 align:start position:0% now very few dependencies um 26<00:01:25.500> 000<00:01:25.560> in<00:01:25.740> growing<00:01:26.040> test<00:01:26.400> cases<00:01:27.000> ens<00:01:27.720> is<00:01:27.900> a 00:01:28.010 --> 00:01:28.020 align:start position:0% um 26 000 in growing test cases ens is a 00:01:28.020 --> 00:01:30.170 align:start position:0% um 26 000 in growing test cases ens is a first-class<00:01:28.380> citizen<00:01:28.799> everything<00:01:29.640> including 00:01:30.170 --> 00:01:30.180 align:start position:0% first-class citizen everything including 00:01:30.180 --> 00:01:32.749 align:start position:0% first-class citizen everything including all<00:01:30.420> dependencies<00:01:30.900> are<00:01:31.200> MIT<00:01:31.439> licensed<00:01:32.040> and 00:01:32.749 --> 00:01:32.759 align:start position:0% all dependencies are MIT licensed and 00:01:32.759 --> 00:01:34.190 align:start position:0% all dependencies are MIT licensed and there's<00:01:33.000> extensive<00:01:33.420> documentation<00:01:33.840> and<00:01:34.080> in 00:01:34.190 --> 00:01:34.200 align:start position:0% there's extensive documentation and in 00:01:34.200 --> 00:01:35.630 align:start position:0% there's extensive documentation and in V6<00:01:34.560> the<00:01:34.740> documentation<00:01:35.100> is<00:01:35.220> getting<00:01:35.400> much 00:01:35.630 --> 00:01:35.640 align:start position:0% V6 the documentation is getting much 00:01:35.640 --> 00:01:37.010 align:start position:0% V6 the documentation is getting much better 00:01:37.010 --> 00:01:37.020 align:start position:0% better 00:01:37.020 --> 00:01:37.550 align:start position:0% better um 00:01:37.550 --> 00:01:37.560 align:start position:0% um 00:01:37.560 --> 00:01:39.289 align:start position:0% um and<00:01:37.979> an<00:01:38.159> important<00:01:38.460> thing<00:01:38.579> is<00:01:38.880> to<00:01:39.180> understand 00:01:39.289 --> 00:01:39.299 align:start position:0% and an important thing is to understand 00:01:39.299 --> 00:01:41.030 align:start position:0% and an important thing is to understand like<00:01:39.600> I<00:01:39.780> made<00:01:39.900> ethers<00:01:40.380> because<00:01:40.500> something<00:01:40.740> I 00:01:41.030 --> 00:01:41.040 align:start position:0% like I made ethers because something I 00:01:41.040 --> 00:01:42.830 align:start position:0% like I made ethers because something I needed<00:01:41.340> and<00:01:41.820> something<00:01:42.060> that<00:01:42.240> I<00:01:42.360> use<00:01:42.479> a<00:01:42.720> lot 00:01:42.830 --> 00:01:42.840 align:start position:0% needed and something that I use a lot 00:01:42.840 --> 00:01:44.510 align:start position:0% needed and something that I use a lot and<00:01:43.380> so 00:01:44.510 --> 00:01:44.520 align:start position:0% and so 00:01:44.520 --> 00:01:46.310 align:start position:0% and so I<00:01:44.880> mean<00:01:44.939> it's<00:01:45.060> in<00:01:45.299> my<00:01:45.420> best<00:01:45.600> interest<00:01:45.780> to<00:01:46.079> keep 00:01:46.310 --> 00:01:46.320 align:start position:0% I mean it's in my best interest to keep 00:01:46.320 --> 00:01:48.230 align:start position:0% I mean it's in my best interest to keep it<00:01:46.500> getting<00:01:46.979> better<00:01:47.220> over<00:01:47.520> time<00:01:47.820> and<00:01:48.060> that 00:01:48.230 --> 00:01:48.240 align:start position:0% it getting better over time and that 00:01:48.240 --> 00:01:49.429 align:start position:0% it getting better over time and that sort<00:01:48.360> of<00:01:48.420> thing<00:01:48.540> I<00:01:48.720> think<00:01:48.840> dog<00:01:49.020> fooding<00:01:49.380> is 00:01:49.429 --> 00:01:49.439 align:start position:0% sort of thing I think dog fooding is 00:01:49.439 --> 00:01:50.929 align:start position:0% sort of thing I think dog fooding is very<00:01:49.560> important<00:01:49.799> to<00:01:49.860> keeping<00:01:50.280> a<00:01:50.399> library<00:01:50.579> good 00:01:50.929 --> 00:01:50.939 align:start position:0% very important to keeping a library good 00:01:50.939 --> 00:01:53.210 align:start position:0% very important to keeping a library good otherwise<00:01:51.720> you<00:01:51.899> get<00:01:52.079> a<00:01:52.259> library<00:01:52.619> is<00:01:52.860> very<00:01:53.100> good 00:01:53.210 --> 00:01:53.220 align:start position:0% otherwise you get a library is very good 00:01:53.220 --> 00:01:55.130 align:start position:0% otherwise you get a library is very good at<00:01:53.340> hello<00:01:53.460> world<00:01:53.759> but<00:01:54.299> very<00:01:54.479> difficult<00:01:54.720> at 00:01:55.130 --> 00:01:55.140 align:start position:0% at hello world but very difficult at 00:01:55.140 --> 00:01:59.630 align:start position:0% at hello world but very difficult at anything<00:01:55.740> more<00:01:56.100> complex<00:01:56.460> so 00:01:59.630 --> 00:01:59.640 align:start position:0% 00:01:59.640 --> 00:02:01.609 align:start position:0% modern<00:02:00.240> so<00:02:00.600> getting<00:02:00.960> into<00:02:01.140> the<00:02:01.380> new<00:02:01.439> things 00:02:01.609 --> 00:02:01.619 align:start position:0% modern so getting into the new things 00:02:01.619 --> 00:02:03.289 align:start position:0% modern so getting into the new things than<00:02:02.159> V6<00:02:02.520> that's<00:02:02.759> coming<00:02:03.000> out<00:02:03.119> there's 00:02:03.289 --> 00:02:03.299 align:start position:0% than V6 that's coming out there's 00:02:03.299 --> 00:02:05.330 align:start position:0% than V6 that's coming out there's currently<00:02:03.540> a<00:02:03.659> V6<00:02:03.960> available 00:02:05.330 --> 00:02:05.340 align:start position:0% currently a V6 available 00:02:05.340 --> 00:02:07.190 align:start position:0% currently a V6 available um<00:02:05.399> both<00:02:05.640> on<00:02:05.759> npm<00:02:06.180> and<00:02:06.360> GitHub 00:02:07.190 --> 00:02:07.200 align:start position:0% um both on npm and GitHub 00:02:07.200 --> 00:02:09.770 align:start position:0% um both on npm and GitHub uh<00:02:07.799> it's<00:02:07.979> still<00:02:08.160> very<00:02:08.399> beta<00:02:08.940> but<00:02:09.360> it's<00:02:09.599> there 00:02:09.770 --> 00:02:09.780 align:start position:0% uh it's still very beta but it's there 00:02:09.780 --> 00:02:10.790 align:start position:0% uh it's still very beta but it's there to<00:02:09.899> try<00:02:10.020> out<00:02:10.200> so<00:02:10.380> one<00:02:10.560> of<00:02:10.679> the<00:02:10.679> biggest 00:02:10.790 --> 00:02:10.800 align:start position:0% to try out so one of the biggest 00:02:10.800 --> 00:02:13.430 align:start position:0% to try out so one of the biggest features<00:02:11.099> is<00:02:11.340> modern<00:02:11.580> es<00:02:11.819> features 00:02:13.430 --> 00:02:13.440 align:start position:0% features is modern es features 00:02:13.440 --> 00:02:17.330 align:start position:0% features is modern es features um<00:02:13.500> currently<00:02:13.860> V5<00:02:14.599> it<00:02:15.599> targets<00:02:16.020> ES3<00:02:16.620> so<00:02:16.980> if<00:02:17.160> you 00:02:17.330 --> 00:02:17.340 align:start position:0% um currently V5 it targets ES3 so if you 00:02:17.340 --> 00:02:21.830 align:start position:0% um currently V5 it targets ES3 so if you are<00:02:17.520> trying<00:02:17.700> to<00:02:17.819> run<00:02:18.379> ethers<00:02:19.379> in<00:02:19.980> IE<00:02:20.940> 3<00:02:21.360> from 00:02:21.830 --> 00:02:21.840 align:start position:0% are trying to run ethers in IE 3 from 00:02:21.840 --> 00:02:24.010 align:start position:0% are trying to run ethers in IE 3 from 2002<00:02:22.500> it'll<00:02:22.800> probably<00:02:22.920> still<00:02:23.099> work<00:02:23.340> mostly 00:02:24.010 --> 00:02:24.020 align:start position:0% 2002 it'll probably still work mostly 00:02:24.020 --> 00:02:26.930 align:start position:0% 2002 it'll probably still work mostly but<00:02:25.020> that's<00:02:25.319> no<00:02:25.560> longer<00:02:25.860> a<00:02:25.980> priority<00:02:26.400> and<00:02:26.700> so 00:02:26.930 --> 00:02:26.940 align:start position:0% but that's no longer a priority and so 00:02:26.940 --> 00:02:29.570 align:start position:0% but that's no longer a priority and so the<00:02:27.180> goal<00:02:27.420> is<00:02:27.480> to<00:02:27.720> start<00:02:27.959> adding 00:02:29.570 --> 00:02:29.580 align:start position:0% the goal is to start adding 00:02:29.580 --> 00:02:31.729 align:start position:0% the goal is to start adding um<00:02:29.640> kind<00:02:30.420> of<00:02:30.480> like<00:02:30.660> new<00:02:31.020> age<00:02:31.200> JavaScript 00:02:31.729 --> 00:02:31.739 align:start position:0% um kind of like new age JavaScript 00:02:31.739 --> 00:02:33.890 align:start position:0% um kind of like new age JavaScript things<00:02:32.040> heavily<00:02:32.940> reduces<00:02:33.300> the<00:02:33.480> code<00:02:33.660> size 00:02:33.890 --> 00:02:33.900 align:start position:0% things heavily reduces the code size 00:02:33.900 --> 00:02:35.210 align:start position:0% things heavily reduces the code size because<00:02:34.200> rather<00:02:34.500> than<00:02:34.620> having<00:02:34.800> this<00:02:35.040> big 00:02:35.210 --> 00:02:35.220 align:start position:0% because rather than having this big 00:02:35.220 --> 00:02:36.470 align:start position:0% because rather than having this big class<00:02:35.400> for<00:02:35.640> big<00:02:35.819> numbers<00:02:36.000> you<00:02:36.239> can<00:02:36.420> actually 00:02:36.470 --> 00:02:36.480 align:start position:0% class for big numbers you can actually 00:02:36.480 --> 00:02:38.390 align:start position:0% class for big numbers you can actually just<00:02:36.720> use<00:02:36.959> the<00:02:37.560> built-in<00:02:37.860> big<00:02:38.040> numbers<00:02:38.160> that 00:02:38.390 --> 00:02:38.400 align:start position:0% just use the built-in big numbers that 00:02:38.400 --> 00:02:40.550 align:start position:0% just use the built-in big numbers that JavaScript<00:02:38.700> now<00:02:38.879> provides<00:02:39.300> you 00:02:40.550 --> 00:02:40.560 align:start position:0% JavaScript now provides you 00:02:40.560 --> 00:02:42.290 align:start position:0% JavaScript now provides you um<00:02:40.980> so 00:02:42.290 --> 00:02:42.300 align:start position:0% um so 00:02:42.300 --> 00:02:44.150 align:start position:0% um so uh<00:02:43.140> I<00:02:43.319> mean<00:02:43.440> you<00:02:43.560> can<00:02:43.620> now<00:02:43.739> use<00:02:43.920> like<00:02:44.099> the 00:02:44.150 --> 00:02:44.160 align:start position:0% uh I mean you can now use like the 00:02:44.160 --> 00:02:45.710 align:start position:0% uh I mean you can now use like the equals<00:02:44.519> equals<00:02:44.819> equal<00:02:45.000> sign<00:02:45.239> which<00:02:45.540> is<00:02:45.599> super 00:02:45.710 --> 00:02:45.720 align:start position:0% equals equals equal sign which is super 00:02:45.720 --> 00:02:48.290 align:start position:0% equals equals equal sign which is super exciting<00:02:46.280> if<00:02:47.280> you<00:02:47.459> want<00:02:47.580> to<00:02:47.700> use<00:02:47.819> a<00:02:48.000> big<00:02:48.120> number 00:02:48.290 --> 00:02:48.300 align:start position:0% exciting if you want to use a big number 00:02:48.300 --> 00:02:50.449 align:start position:0% exciting if you want to use a big number you<00:02:49.019> just<00:02:49.080> put<00:02:49.260> an<00:02:49.379> n<00:02:49.560> on<00:02:49.800> the<00:02:49.920> end<00:02:50.040> and<00:02:50.340> that 00:02:50.449 --> 00:02:50.459 align:start position:0% you just put an n on the end and that 00:02:50.459 --> 00:02:52.009 align:start position:0% you just put an n on the end and that tells<00:02:50.700> JavaScript<00:02:51.060> this<00:02:51.480> number<00:02:51.660> should<00:02:51.900> be 00:02:52.009 --> 00:02:52.019 align:start position:0% tells JavaScript this number should be 00:02:52.019 --> 00:02:53.990 align:start position:0% tells JavaScript this number should be treated<00:02:52.260> as<00:02:52.379> a<00:02:52.440> big<00:02:52.560> literal<00:02:52.920> uh<00:02:53.760> don't<00:02:53.879> go 00:02:53.990 --> 00:02:54.000 align:start position:0% treated as a big literal uh don't go 00:02:54.000 --> 00:02:57.110 align:start position:0% treated as a big literal uh don't go doing<00:02:54.180> IEEE<00:02:54.840> or<00:02:54.959> yeah<00:02:55.260> IEEE<00:02:55.860> 754<00:02:56.400> truncation 00:02:57.110 --> 00:02:57.120 align:start position:0% doing IEEE or yeah IEEE 754 truncation 00:02:57.120 --> 00:02:59.750 align:start position:0% doing IEEE or yeah IEEE 754 truncation to<00:02:57.360> it<00:02:57.540> and<00:02:57.900> and<00:02:58.560> that<00:02:58.800> sort<00:02:58.920> of<00:02:59.099> thing 00:02:59.750 --> 00:02:59.760 align:start position:0% to it and and that sort of thing 00:02:59.760 --> 00:03:01.970 align:start position:0% to it and and that sort of thing um<00:02:59.879> I'm<00:03:00.180> trying<00:03:00.480> going<00:03:01.200> to<00:03:01.379> try<00:03:01.500> to<00:03:01.620> go<00:03:01.860> through 00:03:01.970 --> 00:03:01.980 align:start position:0% um I'm trying going to try to go through 00:03:01.980 --> 00:03:04.190 align:start position:0% um I'm trying going to try to go through this<00:03:02.220> faster<00:03:02.519> ish<00:03:03.239> if<00:03:03.660> I'm<00:03:03.780> talking<00:03:03.900> too<00:03:04.080> fast 00:03:04.190 --> 00:03:04.200 align:start position:0% this faster ish if I'm talking too fast 00:03:04.200 --> 00:03:05.750 align:start position:0% this faster ish if I'm talking too fast let<00:03:04.379> me<00:03:04.500> know<00:03:04.620> but<00:03:04.920> basically<00:03:05.340> it'd<00:03:05.580> be<00:03:05.640> nice 00:03:05.750 --> 00:03:05.760 align:start position:0% let me know but basically it'd be nice 00:03:05.760 --> 00:03:06.949 align:start position:0% let me know but basically it'd be nice to<00:03:05.879> get<00:03:05.940> to<00:03:06.060> the<00:03:06.120> end<00:03:06.239> so<00:03:06.420> people<00:03:06.660> who<00:03:06.780> have 00:03:06.949 --> 00:03:06.959 align:start position:0% to get to the end so people who have 00:03:06.959 --> 00:03:08.630 align:start position:0% to get to the end so people who have questions<00:03:07.140> can<00:03:07.379> ask<00:03:07.620> questions 00:03:08.630 --> 00:03:08.640 align:start position:0% questions can ask questions 00:03:08.640 --> 00:03:10.850 align:start position:0% questions can ask questions so<00:03:09.360> another<00:03:09.540> really<00:03:09.900> cool<00:03:10.080> feature<00:03:10.379> that<00:03:10.680> uh 00:03:10.850 --> 00:03:10.860 align:start position:0% so another really cool feature that uh 00:03:10.860 --> 00:03:13.430 align:start position:0% so another really cool feature that uh modern<00:03:11.099> JS<00:03:11.519> offers<00:03:11.819> is<00:03:12.060> proxies<00:03:12.540> for<00:03:13.319> those 00:03:13.430 --> 00:03:13.440 align:start position:0% modern JS offers is proxies for those 00:03:13.440 --> 00:03:14.869 align:start position:0% modern JS offers is proxies for those that<00:03:13.560> don't<00:03:13.680> know<00:03:13.739> proxy<00:03:14.220> is<00:03:14.340> basically<00:03:14.580> and 00:03:14.869 --> 00:03:14.879 align:start position:0% that don't know proxy is basically and 00:03:14.879 --> 00:03:17.809 align:start position:0% that don't know proxy is basically and are<00:03:15.060> are<00:03:15.480> an<00:03:15.840> object<00:03:16.200> and<00:03:17.040> if<00:03:17.220> you<00:03:17.400> call<00:03:17.640> a 00:03:17.809 --> 00:03:17.819 align:start position:0% are are an object and if you call a 00:03:17.819 --> 00:03:20.270 align:start position:0% are are an object and if you call a property<00:03:18.060> that<00:03:18.360> doesn't<00:03:18.480> exist<00:03:18.860> code<00:03:19.860> gets<00:03:20.220> to 00:03:20.270 --> 00:03:20.280 align:start position:0% property that doesn't exist code gets to 00:03:20.280 --> 00:03:21.949 align:start position:0% property that doesn't exist code gets to run<00:03:20.459> first<00:03:20.760> and<00:03:21.060> decide<00:03:21.360> whether<00:03:21.599> or<00:03:21.720> not<00:03:21.720> it 00:03:21.949 --> 00:03:21.959 align:start position:0% run first and decide whether or not it 00:03:21.959 --> 00:03:24.110 align:start position:0% run first and decide whether or not it should<00:03:22.200> let<00:03:22.800> you<00:03:22.980> think<00:03:23.280> something<00:03:23.580> exists 00:03:24.110 --> 00:03:24.120 align:start position:0% should let you think something exists 00:03:24.120 --> 00:03:26.330 align:start position:0% should let you think something exists and<00:03:24.239> continue<00:03:24.420> so<00:03:25.319> this<00:03:25.500> heavily<00:03:25.920> improves 00:03:26.330 --> 00:03:26.340 align:start position:0% and continue so this heavily improves 00:03:26.340 --> 00:03:28.070 align:start position:0% and continue so this heavily improves how 00:03:28.070 --> 00:03:28.080 align:start position:0% how 00:03:28.080 --> 00:03:29.330 align:start position:0% how um<00:03:28.140> the<00:03:28.379> contract<00:03:28.680> object<00:03:28.980> Works 00:03:29.330 --> 00:03:29.340 align:start position:0% um the contract object Works 00:03:29.340 --> 00:03:32.570 align:start position:0% um the contract object Works historically<00:03:30.239> you<00:03:30.659> had<00:03:30.840> like<00:03:31.140> a<00:03:31.800> ABI<00:03:32.280> with 00:03:32.570 --> 00:03:32.580 align:start position:0% historically you had like a ABI with 00:03:32.580 --> 00:03:34.729 align:start position:0% historically you had like a ABI with multiple<00:03:33.120> different 00:03:34.729 --> 00:03:34.739 align:start position:0% multiple different 00:03:34.739 --> 00:03:35.690 align:start position:0% multiple different um 00:03:35.690 --> 00:03:35.700 align:start position:0% um 00:03:35.700 --> 00:03:39.290 align:start position:0% um signatures<00:03:36.480> for<00:03:36.959> for<00:03:37.200> different<00:03:37.440> methods<00:03:38.400> it 00:03:39.290 --> 00:03:39.300 align:start position:0% signatures for for different methods it 00:03:39.300 --> 00:03:41.030 align:start position:0% signatures for for different methods it really<00:03:39.720> required<00:03:40.200> you<00:03:40.260> to<00:03:40.440> understand<00:03:40.560> all 00:03:41.030 --> 00:03:41.040 align:start position:0% really required you to understand all 00:03:41.040 --> 00:03:43.610 align:start position:0% really required you to understand all the<00:03:41.159> rules<00:03:41.340> for<00:03:41.519> how<00:03:41.700> formatting<00:03:42.239> Works<00:03:42.620> to 00:03:43.610 --> 00:03:43.620 align:start position:0% the rules for how formatting Works to 00:03:43.620 --> 00:03:44.750 align:start position:0% the rules for how formatting Works to normalize<00:03:43.920> the<00:03:44.040> signature<00:03:44.400> in<00:03:44.519> order<00:03:44.640> to 00:03:44.750 --> 00:03:44.760 align:start position:0% normalize the signature in order to 00:03:44.760 --> 00:03:46.250 align:start position:0% normalize the signature in order to access<00:03:44.940> it<00:03:45.180> so<00:03:45.360> now<00:03:45.540> you<00:03:45.659> can<00:03:45.780> do<00:03:45.900> whatever<00:03:46.019> you 00:03:46.250 --> 00:03:46.260 align:start position:0% access it so now you can do whatever you 00:03:46.260 --> 00:03:48.289 align:start position:0% access it so now you can do whatever you want<00:03:46.440> so<00:03:47.040> like<00:03:47.280> basically<00:03:47.640> you<00:03:47.879> can<00:03:47.940> have<00:03:48.120> all 00:03:48.289 --> 00:03:48.299 align:start position:0% want so like basically you can have all 00:03:48.299 --> 00:03:49.369 align:start position:0% want so like basically you can have all sorts<00:03:48.480> of<00:03:48.540> white<00:03:48.659> space<00:03:48.900> extra<00:03:49.140> little 00:03:49.369 --> 00:03:49.379 align:start position:0% sorts of white space extra little 00:03:49.379 --> 00:03:51.649 align:start position:0% sorts of white space extra little letters<00:03:49.739> and<00:03:49.980> and<00:03:50.280> whatnot<00:03:50.760> in<00:03:50.940> there<00:03:51.060> and 00:03:51.649 --> 00:03:51.659 align:start position:0% letters and and whatnot in there and 00:03:51.659 --> 00:03:53.690 align:start position:0% letters and and whatnot in there and this<00:03:51.780> will<00:03:51.959> all<00:03:52.140> figure<00:03:52.319> it<00:03:52.500> out<00:03:52.620> at<00:03:53.220> runtime 00:03:53.690 --> 00:03:53.700 align:start position:0% this will all figure it out at runtime 00:03:53.700 --> 00:03:55.670 align:start position:0% this will all figure it out at runtime and<00:03:54.360> map<00:03:54.540> it<00:03:54.720> back<00:03:54.840> into<00:03:55.019> that<00:03:55.260> and<00:03:55.440> get<00:03:55.560> the 00:03:55.670 --> 00:03:55.680 align:start position:0% and map it back into that and get the 00:03:55.680 --> 00:03:57.289 align:start position:0% and map it back into that and get the right<00:03:55.799> thing<00:03:55.980> for<00:03:56.099> you<00:03:56.220> basically<00:03:56.760> for<00:03:57.180> all 00:03:57.289 --> 00:03:57.299 align:start position:0% right thing for you basically for all 00:03:57.299 --> 00:03:58.550 align:start position:0% right thing for you basically for all those<00:03:57.360> people<00:03:57.480> who've<00:03:57.720> ever<00:03:57.840> had<00:03:58.019> duplicate 00:03:58.550 --> 00:03:58.560 align:start position:0% those people who've ever had duplicate 00:03:58.560 --> 00:04:01.430 align:start position:0% those people who've ever had duplicate ABI<00:03:58.980> definition<00:03:59.099> errors<00:03:59.720> and<00:04:00.720> have<00:04:01.019> filed<00:04:01.379> an 00:04:01.430 --> 00:04:01.440 align:start position:0% ABI definition errors and have filed an 00:04:01.440 --> 00:04:02.809 align:start position:0% ABI definition errors and have filed an issue<00:04:01.680> saying<00:04:01.980> how<00:04:02.040> to<00:04:02.159> get<00:04:02.220> rid<00:04:02.340> of<00:04:02.459> them<00:04:02.580> this 00:04:02.809 --> 00:04:02.819 align:start position:0% issue saying how to get rid of them this 00:04:02.819 --> 00:04:04.910 align:start position:0% issue saying how to get rid of them this is<00:04:02.940> for<00:04:03.060> you<00:04:03.239> typed<00:04:04.019> values<00:04:04.260> are<00:04:04.440> another<00:04:04.560> cool 00:04:04.910 --> 00:04:04.920 align:start position:0% is for you typed values are another cool 00:04:04.920 --> 00:04:06.229 align:start position:0% is for you typed values are another cool thing<00:04:05.099> so<00:04:05.459> going<00:04:05.700> back<00:04:05.819> to<00:04:06.000> the<00:04:06.120> same 00:04:06.229 --> 00:04:06.239 align:start position:0% thing so going back to the same 00:04:06.239 --> 00:04:09.530 align:start position:0% thing so going back to the same situation<00:04:06.659> where<00:04:07.500> you<00:04:07.799> have<00:04:08.120> uh<00:04:09.120> two 00:04:09.530 --> 00:04:09.540 align:start position:0% situation where you have uh two 00:04:09.540 --> 00:04:12.470 align:start position:0% situation where you have uh two different<00:04:09.720> methods<00:04:10.379> Foo<00:04:10.799> and<00:04:10.920> Foo<00:04:11.299> and<00:04:12.299> they 00:04:12.470 --> 00:04:12.480 align:start position:0% different methods Foo and Foo and they 00:04:12.480 --> 00:04:15.350 align:start position:0% different methods Foo and Foo and they take<00:04:12.659> in<00:04:12.900> different<00:04:13.260> things<00:04:13.920> in<00:04:14.760> V5<00:04:15.120> there's 00:04:15.350 --> 00:04:15.360 align:start position:0% take in different things in V5 there's 00:04:15.360 --> 00:04:16.729 align:start position:0% take in different things in V5 there's no<00:04:15.540> way<00:04:15.599> for<00:04:15.780> it<00:04:15.900> to<00:04:15.959> know<00:04:16.079> which<00:04:16.260> one<00:04:16.380> if<00:04:16.620> you 00:04:16.729 --> 00:04:16.739 align:start position:0% no way for it to know which one if you 00:04:16.739 --> 00:04:19.009 align:start position:0% no way for it to know which one if you pass<00:04:16.859> into<00:04:17.100> parameters<00:04:17.699> an<00:04:18.419> address<00:04:18.600> looks 00:04:19.009 --> 00:04:19.019 align:start position:0% pass into parameters an address looks 00:04:19.019 --> 00:04:21.229 align:start position:0% pass into parameters an address looks very<00:04:19.139> much<00:04:19.260> like<00:04:19.440> a<00:04:19.680> number<00:04:19.799> of<00:04:20.400> 160<00:04:21.000> bit 00:04:21.229 --> 00:04:21.239 align:start position:0% very much like a number of 160 bit 00:04:21.239 --> 00:04:22.250 align:start position:0% very much like a number of 160 bit number<00:04:21.419> but<00:04:21.600> it<00:04:21.720> looks<00:04:21.840> like<00:04:21.959> a<00:04:22.079> number 00:04:22.250 --> 00:04:22.260 align:start position:0% number but it looks like a number 00:04:22.260 --> 00:04:24.350 align:start position:0% number but it looks like a number there's<00:04:22.800> no<00:04:22.979> way<00:04:23.100> for<00:04:23.280> ethers<00:04:24.060> to<00:04:24.240> actually 00:04:24.350 --> 00:04:24.360 align:start position:0% there's no way for ethers to actually 00:04:24.360 --> 00:04:26.390 align:start position:0% there's no way for ethers to actually know<00:04:24.540> which<00:04:24.720> one<00:04:24.840> you<00:04:24.960> meant<00:04:25.199> to<00:04:25.259> call<00:04:25.500> and<00:04:26.220> so 00:04:26.390 --> 00:04:26.400 align:start position:0% know which one you meant to call and so 00:04:26.400 --> 00:04:29.689 align:start position:0% know which one you meant to call and so now<00:04:26.639> you<00:04:26.940> can<00:04:27.060> do<00:04:27.300> uh<00:04:28.259> so<00:04:28.500> you<00:04:28.800> yeah<00:04:29.340> so<00:04:29.580> this 00:04:29.689 --> 00:04:29.699 align:start position:0% now you can do uh so you yeah so this 00:04:29.699 --> 00:04:30.890 align:start position:0% now you can do uh so you yeah so this would<00:04:29.820> be<00:04:29.880> an<00:04:30.000> error<00:04:30.300> it<00:04:30.360> doesn't<00:04:30.479> know<00:04:30.660> what 00:04:30.890 --> 00:04:30.900 align:start position:0% would be an error it doesn't know what 00:04:30.900 --> 00:04:32.330 align:start position:0% would be an error it doesn't know what this<00:04:31.199> is<00:04:31.380> this<00:04:31.560> looks<00:04:31.800> like<00:04:31.860> it<00:04:31.979> could<00:04:32.100> be<00:04:32.220> a 00:04:32.330 --> 00:04:32.340 align:start position:0% this is this looks like it could be a 00:04:32.340 --> 00:04:33.890 align:start position:0% this is this looks like it could be a number<00:04:32.520> this<00:04:32.820> is<00:04:32.880> a<00:04:33.000> perfectly<00:04:33.300> valid<00:04:33.600> u<00:04:33.720> in 00:04:33.890 --> 00:04:33.900 align:start position:0% number this is a perfectly valid u in 00:04:33.900 --> 00:04:36.590 align:start position:0% number this is a perfectly valid u in 256.<00:04:34.560> so<00:04:34.979> now<00:04:35.160> you<00:04:35.400> can<00:04:35.520> force<00:04:35.880> it<00:04:36.000> and<00:04:36.180> tell<00:04:36.419> it 00:04:36.590 --> 00:04:36.600 align:start position:0% 256. so now you can force it and tell it 00:04:36.600 --> 00:04:38.629 align:start position:0% 256. so now you can force it and tell it that<00:04:36.840> it's<00:04:37.020> a<00:04:37.139> typed<00:04:37.440> object<00:04:37.740> of<00:04:37.919> an<00:04:38.040> address 00:04:38.629 --> 00:04:38.639 align:start position:0% that it's a typed object of an address 00:04:38.639 --> 00:04:40.670 align:start position:0% that it's a typed object of an address and<00:04:39.300> then<00:04:39.419> if<00:04:39.900> you<00:04:39.960> do<00:04:40.139> this<00:04:40.259> it'll 00:04:40.670 --> 00:04:40.680 align:start position:0% and then if you do this it'll 00:04:40.680 --> 00:04:42.050 align:start position:0% and then if you do this it'll automatically<00:04:41.040> know<00:04:41.280> oh<00:04:41.520> this<00:04:41.699> is<00:04:41.820> the<00:04:41.940> one 00:04:42.050 --> 00:04:42.060 align:start position:0% automatically know oh this is the one 00:04:42.060 --> 00:04:43.909 align:start position:0% automatically know oh this is the one you<00:04:42.180> wanted<00:04:42.300> so<00:04:43.020> again<00:04:43.259> really<00:04:43.620> cool<00:04:43.800> things 00:04:43.909 --> 00:04:43.919 align:start position:0% you wanted so again really cool things 00:04:43.919 --> 00:04:45.469 align:start position:0% you wanted so again really cool things we<00:04:44.100> can<00:04:44.220> do<00:04:44.340> this<00:04:44.639> is<00:04:44.820> sort<00:04:45.000> of<00:04:45.120> related<00:04:45.360> to 00:04:45.469 --> 00:04:45.479 align:start position:0% we can do this is sort of related to 00:04:45.479 --> 00:04:47.469 align:start position:0% we can do this is sort of related to proxies<00:04:45.840> but<00:04:46.259> kind<00:04:46.680> of<00:04:46.800> its<00:04:46.979> own<00:04:47.100> thing 00:04:47.469 --> 00:04:47.479 align:start position:0% proxies but kind of its own thing 00:04:47.479 --> 00:04:49.909 align:start position:0% proxies but kind of its own thing likewise<00:04:48.479> if<00:04:48.780> you<00:04:48.960> have 00:04:49.909 --> 00:04:49.919 align:start position:0% likewise if you have 00:04:49.919 --> 00:04:51.350 align:start position:0% likewise if you have um if<00:04:50.340> you're<00:04:50.460> doing<00:04:50.580> programmatic<00:04:51.180> things 00:04:51.350 --> 00:04:51.360 align:start position:0% um if you're doing programmatic things 00:04:51.360 --> 00:04:52.969 align:start position:0% um if you're doing programmatic things sometimes<00:04:52.199> you<00:04:52.380> just<00:04:52.500> have<00:04:52.620> a<00:04:52.800> bunch<00:04:52.860> of 00:04:52.969 --> 00:04:52.979 align:start position:0% sometimes you just have a bunch of 00:04:52.979 --> 00:04:54.469 align:start position:0% sometimes you just have a bunch of keyworded<00:04:53.460> objects<00:04:53.880> and<00:04:54.000> so<00:04:54.180> for<00:04:54.240> example 00:04:54.469 --> 00:04:54.479 align:start position:0% keyworded objects and so for example 00:04:54.479 --> 00:04:56.570 align:start position:0% keyworded objects and so for example you've<00:04:54.720> got<00:04:54.840> transfer<00:04:55.199> from<00:04:55.500> it's<00:04:56.220> got<00:04:56.400> an 00:04:56.570 --> 00:04:56.580 align:start position:0% you've got transfer from it's got an 00:04:56.580 --> 00:05:00.170 align:start position:0% you've got transfer from it's got an from<00:04:57.240> a<00:04:57.720> two<00:04:57.960> and<00:04:58.259> a<00:04:58.440> value<00:04:58.639> so<00:04:59.639> this<00:04:59.940> is<00:05:00.000> how 00:05:00.170 --> 00:05:00.180 align:start position:0% from a two and a value so this is how 00:05:00.180 --> 00:05:01.969 align:start position:0% from a two and a value so this is how you<00:05:00.300> would<00:05:00.419> do<00:05:00.540> it<00:05:00.660> in<00:05:00.780> V5<00:05:01.199> you<00:05:01.560> can<00:05:01.740> still<00:05:01.860> do 00:05:01.969 --> 00:05:01.979 align:start position:0% you would do it in V5 you can still do 00:05:01.979 --> 00:05:04.129 align:start position:0% you would do it in V5 you can still do this<00:05:02.100> in<00:05:02.280> V6<00:05:02.580> this<00:05:02.820> works<00:05:03.120> fine<00:05:03.240> using 00:05:04.129 --> 00:05:04.139 align:start position:0% this in V6 this works fine using 00:05:04.139 --> 00:05:05.870 align:start position:0% this in V6 this works fine using positional<00:05:04.560> parameters<00:05:04.979> for<00:05:05.400> those<00:05:05.580> that<00:05:05.759> are 00:05:05.870 --> 00:05:05.880 align:start position:0% positional parameters for those that are 00:05:05.880 --> 00:05:07.430 align:start position:0% positional parameters for those that are used<00:05:06.120> to<00:05:06.240> python<00:05:06.600> they<00:05:06.840> call<00:05:06.960> them<00:05:07.080> positional 00:05:07.430 --> 00:05:07.440 align:start position:0% used to python they call them positional 00:05:07.440 --> 00:05:09.670 align:start position:0% used to python they call them positional versus<00:05:07.560> keywords<00:05:08.160> but<00:05:09.060> now<00:05:09.180> you<00:05:09.300> can<00:05:09.419> also<00:05:09.540> do 00:05:09.670 --> 00:05:09.680 align:start position:0% versus keywords but now you can also do 00:05:09.680 --> 00:05:12.230 align:start position:0% versus keywords but now you can also do types.keywords<00:05:10.680> and<00:05:10.919> pass<00:05:11.100> in<00:05:11.280> a<00:05:11.520> from<00:05:11.759> a<00:05:12.120> two 00:05:12.230 --> 00:05:12.240 align:start position:0% types.keywords and pass in a from a two 00:05:12.240 --> 00:05:14.990 align:start position:0% types.keywords and pass in a from a two and<00:05:12.479> a<00:05:12.660> value<00:05:12.780> and<00:05:13.740> it<00:05:13.919> knows<00:05:14.340> that<00:05:14.639> those 00:05:14.990 --> 00:05:15.000 align:start position:0% and a value and it knows that those 00:05:15.000 --> 00:05:16.670 align:start position:0% and a value and it knows that those things<00:05:15.180> should<00:05:15.479> get<00:05:15.660> deconstructed<00:05:16.199> into<00:05:16.440> the 00:05:16.670 --> 00:05:16.680 align:start position:0% things should get deconstructed into the 00:05:16.680 --> 00:05:19.189 align:start position:0% things should get deconstructed into the from<00:05:16.860> to<00:05:17.220> some<00:05:17.759> value<00:05:17.940> this<00:05:18.720> order<00:05:18.900> doesn't 00:05:19.189 --> 00:05:19.199 align:start position:0% from to some value this order doesn't 00:05:19.199 --> 00:05:20.810 align:start position:0% from to some value this order doesn't matter<00:05:19.380> either<00:05:19.620> if<00:05:19.919> you<00:05:20.040> wanted<00:05:20.160> to<00:05:20.400> construct 00:05:20.810 --> 00:05:20.820 align:start position:0% matter either if you wanted to construct 00:05:20.820 --> 00:05:23.270 align:start position:0% matter either if you wanted to construct this<00:05:21.360> object<00:05:21.780> from<00:05:22.560> a<00:05:22.740> bunch<00:05:22.800> of<00:05:22.919> other<00:05:22.979> lines 00:05:23.270 --> 00:05:23.280 align:start position:0% this object from a bunch of other lines 00:05:23.280 --> 00:05:24.830 align:start position:0% this object from a bunch of other lines of<00:05:23.460> code<00:05:23.580> reading<00:05:24.060> stuff<00:05:24.240> in<00:05:24.360> you<00:05:24.600> can<00:05:24.720> just 00:05:24.830 --> 00:05:24.840 align:start position:0% of code reading stuff in you can just 00:05:24.840 --> 00:05:26.689 align:start position:0% of code reading stuff in you can just build<00:05:25.020> an<00:05:25.259> object<00:05:25.500> up<00:05:25.740> and<00:05:25.919> add<00:05:26.100> a<00:05:26.220> two<00:05:26.400> if<00:05:26.580> it's 00:05:26.689 --> 00:05:26.699 align:start position:0% build an object up and add a two if it's 00:05:26.699 --> 00:05:28.310 align:start position:0% build an object up and add a two if it's not<00:05:26.880> null<00:05:27.240> and<00:05:27.479> out<00:05:27.720> of<00:05:27.780> this<00:05:27.900> if<00:05:28.020> it's<00:05:28.139> not 00:05:28.310 --> 00:05:28.320 align:start position:0% not null and out of this if it's not 00:05:28.320 --> 00:05:29.689 align:start position:0% not null and out of this if it's not that 00:05:29.689 --> 00:05:29.699 align:start position:0% that 00:05:29.699 --> 00:05:33.490 align:start position:0% that um and<00:05:30.240> then<00:05:30.360> it's<00:05:30.479> Off<00:05:30.539> to<00:05:30.660> the<00:05:30.780> Races 00:05:33.490 --> 00:05:33.500 align:start position:0% 00:05:33.500 --> 00:05:36.710 align:start position:0% okay<00:05:34.500> another<00:05:35.160> big<00:05:35.520> thing<00:05:35.699> uh<00:05:36.240> is<00:05:36.360> things<00:05:36.600> are 00:05:36.710 --> 00:05:36.720 align:start position:0% okay another big thing uh is things are 00:05:36.720 --> 00:05:39.830 align:start position:0% okay another big thing uh is things are now<00:05:36.900> classes<00:05:37.440> okay<00:05:37.919> I'm<00:05:38.160> down<00:05:38.340> to<00:05:38.460> 19<00:05:38.699> minutes 00:05:39.830 --> 00:05:39.840 align:start position:0% now classes okay I'm down to 19 minutes 00:05:39.840 --> 00:05:43.010 align:start position:0% now classes okay I'm down to 19 minutes um<00:05:39.900> so<00:05:40.020> things<00:05:40.259> have<00:05:40.500> class<00:05:40.800> basically 00:05:43.010 --> 00:05:43.020 align:start position:0% um so things have class basically 00:05:43.020 --> 00:05:44.390 align:start position:0% um so things have class basically um<00:05:43.080> oh<00:05:43.320> yes<00:05:43.500> so<00:05:43.680> I'll<00:05:43.800> dive<00:05:43.979> into<00:05:44.100> this<00:05:44.280> a<00:05:44.340> bit 00:05:44.390 --> 00:05:44.400 align:start position:0% um oh yes so I'll dive into this a bit 00:05:44.400 --> 00:05:45.529 align:start position:0% um oh yes so I'll dive into this a bit more<00:05:44.520> because<00:05:44.699> I<00:05:44.880> think<00:05:44.940> this<00:05:45.120> is<00:05:45.240> a<00:05:45.419> really 00:05:45.529 --> 00:05:45.539 align:start position:0% more because I think this is a really 00:05:45.539 --> 00:05:48.469 align:start position:0% more because I think this is a really cool<00:05:45.840> feature<00:05:46.440> in<00:05:47.220> general<00:05:47.400> of<00:05:48.000> something<00:05:48.240> we 00:05:48.469 --> 00:05:48.479 align:start position:0% cool feature in general of something we 00:05:48.479 --> 00:05:50.689 align:start position:0% cool feature in general of something we should<00:05:48.660> be<00:05:48.720> doing<00:05:48.960> more<00:05:49.440> in<00:05:49.800> solidity<00:05:50.280> this<00:05:50.580> is 00:05:50.689 --> 00:05:50.699 align:start position:0% should be doing more in solidity this is 00:05:50.699 --> 00:05:52.010 align:start position:0% should be doing more in solidity this is kind<00:05:51.000> of<00:05:51.120> steering<00:05:51.300> away<00:05:51.419> from<00:05:51.600> ethers 00:05:52.010 --> 00:05:52.020 align:start position:0% kind of steering away from ethers 00:05:52.020 --> 00:05:53.629 align:start position:0% kind of steering away from ethers specifically<00:05:52.440> into<00:05:52.919> more<00:05:53.160> solidity 00:05:53.629 --> 00:05:53.639 align:start position:0% specifically into more solidity 00:05:53.639 --> 00:05:55.850 align:start position:0% specifically into more solidity generically<00:05:54.180> if<00:05:54.660> you're<00:05:54.780> using<00:05:55.020> V5<00:05:55.440> a 00:05:55.850 --> 00:05:55.860 align:start position:0% generically if you're using V5 a 00:05:55.860 --> 00:05:58.310 align:start position:0% generically if you're using V5 a signature<00:05:56.280> is<00:05:56.580> literally<00:05:56.880> just<00:05:57.180> some<00:05:57.900> dumb 00:05:58.310 --> 00:05:58.320 align:start position:0% signature is literally just some dumb 00:05:58.320 --> 00:05:59.990 align:start position:0% signature is literally just some dumb object<00:05:58.680> it's<00:05:58.979> not<00:05:59.160> a<00:05:59.340> class<00:05:59.520> it's<00:05:59.699> just<00:05:59.880> an 00:05:59.990 --> 00:06:00.000 align:start position:0% object it's not a class it's just an 00:06:00.000 --> 00:06:02.330 align:start position:0% object it's not a class it's just an object<00:06:00.240> with<00:06:00.419> a<00:06:00.600> values<00:06:00.840> r<00:06:01.080> s<00:06:01.259> and<00:06:01.500> V<00:06:01.680> and 00:06:02.330 --> 00:06:02.340 align:start position:0% object with a values r s and V and 00:06:02.340 --> 00:06:04.430 align:start position:0% object with a values r s and V and that's<00:06:02.460> all<00:06:02.639> you<00:06:02.759> get<00:06:02.940> by<00:06:03.720> making<00:06:03.900> it<00:06:04.139> a<00:06:04.259> class 00:06:04.430 --> 00:06:04.440 align:start position:0% that's all you get by making it a class 00:06:04.440 --> 00:06:06.950 align:start position:0% that's all you get by making it a class it<00:06:04.919> can<00:06:05.039> take<00:06:05.220> in<00:06:05.400> anything<00:06:05.820> whether<00:06:06.419> it's<00:06:06.660> a 00:06:06.950 --> 00:06:06.960 align:start position:0% it can take in anything whether it's a 00:06:06.960 --> 00:06:09.469 align:start position:0% it can take in anything whether it's a like<00:06:07.560> a<00:06:07.800> raw<00:06:08.100> signature<00:06:08.639> or<00:06:08.880> whether<00:06:09.120> it's<00:06:09.300> an 00:06:09.469 --> 00:06:09.479 align:start position:0% like a raw signature or whether it's an 00:06:09.479 --> 00:06:12.890 align:start position:0% like a raw signature or whether it's an RS<00:06:09.900> and<00:06:10.020> Y<00:06:10.199> parity<00:06:10.500> r<00:06:10.919> s<00:06:11.100> and<00:06:11.280> v<00:06:11.460> r<00:06:12.180> and<00:06:12.360> Y<00:06:12.479> parody 00:06:12.890 --> 00:06:12.900 align:start position:0% RS and Y parity r s and v r and Y parody 00:06:12.900 --> 00:06:15.529 align:start position:0% RS and Y parity r s and v r and Y parody are<00:06:13.620> are<00:06:13.979> y<00:06:14.220> period<00:06:14.580> s<00:06:14.880> whatever<00:06:15.120> random 00:06:15.529 --> 00:06:15.539 align:start position:0% are are y period s whatever random 00:06:15.539 --> 00:06:17.450 align:start position:0% are are y period s whatever random combination<00:06:15.900> of<00:06:16.139> things<00:06:16.320> you<00:06:16.620> have<00:06:16.740> feed<00:06:17.220> it 00:06:17.450 --> 00:06:17.460 align:start position:0% combination of things you have feed it 00:06:17.460 --> 00:06:19.610 align:start position:0% combination of things you have feed it in<00:06:17.639> it'll<00:06:18.300> figure<00:06:18.479> it<00:06:18.600> out<00:06:18.660> give<00:06:19.020> you<00:06:19.139> back<00:06:19.320> the 00:06:19.610 --> 00:06:19.620 align:start position:0% in it'll figure it out give you back the 00:06:19.620 --> 00:06:22.490 align:start position:0% in it'll figure it out give you back the signature<00:06:20.039> you<00:06:20.160> want<00:06:20.419> and<00:06:21.419> then<00:06:22.020> if<00:06:22.259> you<00:06:22.380> do 00:06:22.490 --> 00:06:22.500 align:start position:0% signature you want and then if you do 00:06:22.500 --> 00:06:24.409 align:start position:0% signature you want and then if you do something<00:06:22.740> like<00:06:23.160> update<00:06:23.580> a<00:06:23.819> value<00:06:23.940> if<00:06:24.300> you 00:06:24.409 --> 00:06:24.419 align:start position:0% something like update a value if you 00:06:24.419 --> 00:06:27.290 align:start position:0% something like update a value if you said<00:06:24.660> for<00:06:24.840> example<00:06:25.020> Sig<00:06:25.380> dot<00:06:25.860> y<00:06:26.520> parity<00:06:26.940> equals 00:06:27.290 --> 00:06:27.300 align:start position:0% said for example Sig dot y parity equals 00:06:27.300 --> 00:06:30.050 align:start position:0% said for example Sig dot y parity equals zero<00:06:27.840> and<00:06:28.680> it<00:06:28.860> used<00:06:29.039> to<00:06:29.100> be<00:06:29.220> one<00:06:29.340> it'll<00:06:29.819> also 00:06:30.050 --> 00:06:30.060 align:start position:0% zero and it used to be one it'll also 00:06:30.060 --> 00:06:31.850 align:start position:0% zero and it used to be one it'll also change<00:06:30.240> the<00:06:30.479> V<00:06:30.600> for<00:06:30.900> you<00:06:31.080> it'll<00:06:31.380> update<00:06:31.620> all 00:06:31.850 --> 00:06:31.860 align:start position:0% change the V for you it'll update all 00:06:31.860 --> 00:06:34.610 align:start position:0% change the V for you it'll update all the<00:06:32.280> why<00:06:32.699> parenting<00:06:33.240> s<00:06:33.360> it'll<00:06:33.720> it'll<00:06:34.080> reflect 00:06:34.610 --> 00:06:34.620 align:start position:0% the why parenting s it'll it'll reflect 00:06:34.620 --> 00:06:36.830 align:start position:0% the why parenting s it'll it'll reflect all<00:06:34.860> the<00:06:35.039> changes<00:06:35.400> so<00:06:36.180> that<00:06:36.300> the<00:06:36.419> signature 00:06:36.830 --> 00:06:36.840 align:start position:0% all the changes so that the signature 00:06:36.840 --> 00:06:40.430 align:start position:0% all the changes so that the signature stays<00:06:37.199> consistent<00:06:37.740> which<00:06:38.220> means<00:06:38.840> so<00:06:39.840> you<00:06:40.380> can 00:06:40.430 --> 00:06:40.440 align:start position:0% stays consistent which means so you can 00:06:40.440 --> 00:06:42.170 align:start position:0% stays consistent which means so you can get<00:06:40.680> all<00:06:40.800> the<00:06:40.919> stuff<00:06:41.039> out<00:06:41.220> of<00:06:41.340> it<00:06:41.460> and<00:06:42.000> that 00:06:42.170 --> 00:06:42.180 align:start position:0% get all the stuff out of it and that 00:06:42.180 --> 00:06:43.610 align:start position:0% get all the stuff out of it and that sort<00:06:42.300> of<00:06:42.419> thing<00:06:42.539> but<00:06:42.780> the<00:06:42.960> cool<00:06:43.139> thing<00:06:43.319> I<00:06:43.500> want 00:06:43.610 --> 00:06:43.620 align:start position:0% sort of thing but the cool thing I want 00:06:43.620 --> 00:06:45.529 align:start position:0% sort of thing but the cool thing I want to<00:06:43.680> show<00:06:43.800> off<00:06:43.979> is 00:06:45.529 --> 00:06:45.539 align:start position:0% to show off is 00:06:45.539 --> 00:06:46.610 align:start position:0% to show off is um<00:06:45.660> maybe<00:06:45.780> I'll<00:06:46.020> come<00:06:46.139> back<00:06:46.199> to<00:06:46.319> this<00:06:46.440> in<00:06:46.560> a 00:06:46.610 --> 00:06:46.620 align:start position:0% um maybe I'll come back to this in a 00:06:46.620 --> 00:06:49.189 align:start position:0% um maybe I'll come back to this in a second<00:06:46.680> that's<00:06:47.039> how<00:06:47.280> things<00:06:47.460> are<00:06:47.639> done<00:06:47.819> today 00:06:49.189 --> 00:06:49.199 align:start position:0% second that's how things are done today 00:06:49.199 --> 00:06:49.790 align:start position:0% second that's how things are done today um 00:06:49.790 --> 00:06:49.800 align:start position:0% um 00:06:49.800 --> 00:06:51.950 align:start position:0% um maybe<00:06:50.520> I<00:06:50.699> will<00:06:50.819> explain<00:06:51.060> this<00:06:51.300> quickly<00:06:51.600> so 00:06:51.950 --> 00:06:51.960 align:start position:0% maybe I will explain this quickly so 00:06:51.960 --> 00:06:52.909 align:start position:0% maybe I will explain this quickly so those<00:06:52.080> are<00:06:52.259> the<00:06:52.440> things<00:06:52.500> are<00:06:52.620> basically<00:06:52.800> done 00:06:52.909 --> 00:06:52.919 align:start position:0% those are the things are basically done 00:06:52.919 --> 00:06:54.830 align:start position:0% those are the things are basically done today<00:06:53.039> so<00:06:53.400> this<00:06:53.580> is<00:06:53.819> basically<00:06:54.360> people<00:06:54.600> that 00:06:54.830 --> 00:06:54.840 align:start position:0% today so this is basically people that 00:06:54.840 --> 00:06:57.290 align:start position:0% today so this is basically people that pass<00:06:55.020> a<00:06:55.199> new<00:06:55.259> signature<00:06:55.740> for 00:06:57.290 --> 00:06:57.300 align:start position:0% pass a new signature for 00:06:57.300 --> 00:06:58.189 align:start position:0% pass a new signature for um 00:06:58.189 --> 00:06:58.199 align:start position:0% um 00:06:58.199 --> 00:07:00.290 align:start position:0% um first<00:06:58.620> solidity<00:06:59.100> for<00:06:59.340> doing<00:06:59.460> easy<00:06:59.639> recover<00:07:00.060> on 00:07:00.290 --> 00:07:00.300 align:start position:0% first solidity for doing easy recover on 00:07:00.300 --> 00:07:02.510 align:start position:0% first solidity for doing easy recover on they<00:07:00.780> pass<00:07:00.960> into<00:07:01.139> bytes<00:07:01.560> or<00:07:01.860> they<00:07:02.039> deconstruct 00:07:02.510 --> 00:07:02.520 align:start position:0% they pass into bytes or they deconstruct 00:07:02.520 --> 00:07:04.730 align:start position:0% they pass into bytes or they deconstruct themselves<00:07:03.000> so<00:07:03.240> that'll<00:07:03.539> be<00:07:03.720> the<00:07:03.960> third<00:07:04.380> slide 00:07:04.730 --> 00:07:04.740 align:start position:0% themselves so that'll be the third slide 00:07:04.740 --> 00:07:06.770 align:start position:0% themselves so that'll be the third slide for<00:07:04.919> now<00:07:05.100> but<00:07:06.000> they'll<00:07:06.180> pass<00:07:06.360> this<00:07:06.479> bytes 00:07:06.770 --> 00:07:06.780 align:start position:0% for now but they'll pass this bytes 00:07:06.780 --> 00:07:08.330 align:start position:0% for now but they'll pass this bytes object<00:07:07.020> in<00:07:07.259> and<00:07:07.740> then<00:07:07.860> you've<00:07:08.039> got<00:07:08.160> this 00:07:08.330 --> 00:07:08.340 align:start position:0% object in and then you've got this 00:07:08.340 --> 00:07:10.010 align:start position:0% object in and then you've got this expensive<00:07:08.819> weird<00:07:09.120> byte<00:07:09.539> manipulation 00:07:10.010 --> 00:07:10.020 align:start position:0% expensive weird byte manipulation 00:07:10.020 --> 00:07:11.930 align:start position:0% expensive weird byte manipulation Library<00:07:10.259> I<00:07:10.680> mean<00:07:10.800> it's<00:07:10.979> well<00:07:11.280> written<00:07:11.580> it's<00:07:11.759> by 00:07:11.930 --> 00:07:11.940 align:start position:0% Library I mean it's well written it's by 00:07:11.940 --> 00:07:13.730 align:start position:0% Library I mean it's well written it's by open<00:07:12.060> Zeppelin<00:07:12.539> I<00:07:12.720> think<00:07:12.840> but<00:07:13.380> you're<00:07:13.500> doing<00:07:13.620> a 00:07:13.730 --> 00:07:13.740 align:start position:0% open Zeppelin I think but you're doing a 00:07:13.740 --> 00:07:15.710 align:start position:0% open Zeppelin I think but you're doing a bunch<00:07:13.860> of<00:07:13.979> string<00:07:14.280> manipulation<00:07:14.759> on<00:07:15.240> byte 00:07:15.710 --> 00:07:15.720 align:start position:0% bunch of string manipulation on byte 00:07:15.720 --> 00:07:18.830 align:start position:0% bunch of string manipulation on byte arrays<00:07:16.139> to<00:07:16.500> figure<00:07:16.800> out<00:07:17.039> where<00:07:17.819> the<00:07:18.000> RS<00:07:18.360> and<00:07:18.600> V 00:07:18.830 --> 00:07:18.840 align:start position:0% arrays to figure out where the RS and V 00:07:18.840 --> 00:07:21.589 align:start position:0% arrays to figure out where the RS and V sit<00:07:19.139> it's<00:07:19.620> also<00:07:19.919> a<00:07:20.039> huge<00:07:20.280> amount<00:07:20.460> of<00:07:20.639> data 00:07:21.589 --> 00:07:21.599 align:start position:0% sit it's also a huge amount of data 00:07:21.599 --> 00:07:24.409 align:start position:0% sit it's also a huge amount of data otherwise<00:07:21.979> and<00:07:22.979> then<00:07:23.220> this<00:07:24.000> is<00:07:24.060> what<00:07:24.300> your 00:07:24.409 --> 00:07:24.419 align:start position:0% otherwise and then this is what your 00:07:24.419 --> 00:07:26.029 align:start position:0% otherwise and then this is what your code<00:07:24.599> looks<00:07:24.960> like<00:07:25.020> the<00:07:25.440> cool<00:07:25.620> thing<00:07:25.800> with 00:07:26.029 --> 00:07:26.039 align:start position:0% code looks like the cool thing with 00:07:26.039 --> 00:07:27.650 align:start position:0% code looks like the cool thing with these<00:07:26.340> new 00:07:27.650 --> 00:07:27.660 align:start position:0% these new 00:07:27.660 --> 00:07:30.589 align:start position:0% these new things<00:07:28.199> are<00:07:28.440> classed<00:07:29.340> you<00:07:30.060> could<00:07:30.180> for<00:07:30.419> example 00:07:30.589 --> 00:07:30.599 align:start position:0% things are classed you could for example 00:07:30.599 --> 00:07:32.930 align:start position:0% things are classed you could for example in<00:07:30.900> your<00:07:31.020> code<00:07:31.259> have<00:07:32.039> a<00:07:32.220> signature<00:07:32.580> that<00:07:32.819> has 00:07:32.930 --> 00:07:32.940 align:start position:0% in your code have a signature that has 00:07:32.940 --> 00:07:35.029 align:start position:0% in your code have a signature that has an<00:07:33.120> R<00:07:33.300> an<00:07:33.599> S<00:07:33.780> and<00:07:34.020> a<00:07:34.199> v 00:07:35.029 --> 00:07:35.039 align:start position:0% an R an S and a v 00:07:35.039 --> 00:07:36.890 align:start position:0% an R an S and a v and<00:07:35.460> then<00:07:35.520> you<00:07:35.699> can<00:07:35.759> just<00:07:35.940> use<00:07:36.120> the<00:07:36.360> Sig<00:07:36.479> type 00:07:36.890 --> 00:07:36.900 align:start position:0% and then you can just use the Sig type 00:07:36.900 --> 00:07:38.510 align:start position:0% and then you can just use the Sig type from<00:07:37.319> the<00:07:37.500> struct 00:07:38.510 --> 00:07:38.520 align:start position:0% from the struct 00:07:38.520 --> 00:07:40.430 align:start position:0% from the struct and<00:07:38.880> this<00:07:39.000> is<00:07:39.120> your<00:07:39.240> EC<00:07:39.479> recovery<00:07:39.960> so 00:07:40.430 --> 00:07:40.440 align:start position:0% and this is your EC recovery so 00:07:40.440 --> 00:07:42.650 align:start position:0% and this is your EC recovery so historically<00:07:40.860> you<00:07:41.099> might<00:07:41.340> have<00:07:41.460> also<00:07:41.639> seen<00:07:41.940> a 00:07:42.650 --> 00:07:42.660 align:start position:0% historically you might have also seen a 00:07:42.660 --> 00:07:46.070 align:start position:0% historically you might have also seen a verify<00:07:43.139> that<00:07:43.319> takes<00:07:43.440> in<00:07:43.560> a<00:07:43.680> byte32<00:07:44.160> digest<00:07:44.580> a 00:07:46.070 --> 00:07:46.080 align:start position:0% verify that takes in a byte32 digest a 00:07:46.080 --> 00:07:50.089 align:start position:0% verify that takes in a byte32 digest a bytes<00:07:46.740> 32<00:07:47.160> V<00:07:47.639> bytes<00:07:48.240> or<00:07:48.360> sorry<00:07:48.479> bytes<00:07:48.840> you<00:07:49.620> went 00:07:50.089 --> 00:07:50.099 align:start position:0% bytes 32 V bytes or sorry bytes you went 00:07:50.099 --> 00:07:50.990 align:start position:0% bytes 32 V bytes or sorry bytes you went eight 00:07:50.990 --> 00:07:51.000 align:start position:0% eight 00:07:51.000 --> 00:07:54.170 align:start position:0% eight V<00:07:51.419> byte<00:07:52.020> series<00:07:52.080> who<00:07:52.380> are<00:07:52.440> by<00:07:52.680> Sergio<00:07:53.160> s<00:07:53.340> and<00:07:54.000> go 00:07:54.170 --> 00:07:54.180 align:start position:0% V byte series who are by Sergio s and go 00:07:54.180 --> 00:07:55.969 align:start position:0% V byte series who are by Sergio s and go off<00:07:54.300> the<00:07:54.419> races<00:07:54.780> but<00:07:55.139> with<00:07:55.319> this<00:07:55.500> you<00:07:55.740> can<00:07:55.800> kind 00:07:55.969 --> 00:07:55.979 align:start position:0% off the races but with this you can kind 00:07:55.979 --> 00:07:57.350 align:start position:0% off the races but with this you can kind of<00:07:56.099> pack<00:07:56.280> them<00:07:56.520> all<00:07:56.639> together<00:07:56.819> this<00:07:57.060> is<00:07:57.180> the 00:07:57.350 --> 00:07:57.360 align:start position:0% of pack them all together this is the 00:07:57.360 --> 00:07:59.629 align:start position:0% of pack them all together this is the same<00:07:57.479> size<00:07:57.720> for<00:07:58.080> the<00:07:58.139> ABI<00:07:58.560> point<00:07:58.860> of<00:07:59.039> view<00:07:59.099> and 00:07:59.629 --> 00:07:59.639 align:start position:0% same size for the ABI point of view and 00:07:59.639 --> 00:08:02.270 align:start position:0% same size for the ABI point of view and then<00:07:59.759> you<00:07:59.880> just<00:08:00.060> pass<00:08:00.360> in<00:08:00.599> the<00:08:00.960> signature<00:08:01.380> and 00:08:02.270 --> 00:08:02.280 align:start position:0% then you just pass in the signature and 00:08:02.280 --> 00:08:04.490 align:start position:0% then you just pass in the signature and because<00:08:02.639> it's<00:08:03.000> a<00:08:03.180> class<00:08:03.660> when<00:08:04.139> it's<00:08:04.319> starting 00:08:04.490 --> 00:08:04.500 align:start position:0% because it's a class when it's starting 00:08:04.500 --> 00:08:06.290 align:start position:0% because it's a class when it's starting to<00:08:04.680> build<00:08:04.979> out<00:08:05.220> that<00:08:05.520> encoded<00:08:06.000> piece<00:08:06.240> of 00:08:06.290 --> 00:08:06.300 align:start position:0% to build out that encoded piece of 00:08:06.300 --> 00:08:08.570 align:start position:0% to build out that encoded piece of information<00:08:06.479> it<00:08:07.440> knows<00:08:07.740> to<00:08:07.860> take<00:08:07.979> the<00:08:08.220> r<00:08:08.340> and 00:08:08.570 --> 00:08:08.580 align:start position:0% information it knows to take the r and 00:08:08.580 --> 00:08:10.070 align:start position:0% information it knows to take the r and pack<00:08:08.699> it<00:08:08.880> together<00:08:09.000> with<00:08:09.240> the<00:08:09.300> S<00:08:09.419> impacted<00:08:09.960> out 00:08:10.070 --> 00:08:10.080 align:start position:0% pack it together with the S impacted out 00:08:10.080 --> 00:08:12.409 align:start position:0% pack it together with the S impacted out the<00:08:10.199> v<00:08:10.380> in<00:08:10.919> a<00:08:11.039> nice<00:08:11.160> compact<00:08:11.520> format<00:08:11.940> and<00:08:12.300> then 00:08:12.409 --> 00:08:12.419 align:start position:0% the v in a nice compact format and then 00:08:12.419 --> 00:08:14.570 align:start position:0% the v in a nice compact format and then you're<00:08:12.599> off<00:08:12.720> to<00:08:12.900> the<00:08:13.020> races<00:08:13.319> so<00:08:14.160> one<00:08:14.340> important 00:08:14.570 --> 00:08:14.580 align:start position:0% you're off to the races so one important 00:08:14.580 --> 00:08:15.830 align:start position:0% you're off to the races so one important thing<00:08:14.699> to<00:08:14.819> note<00:08:14.880> with<00:08:15.060> this<00:08:15.180> the<00:08:15.419> next<00:08:15.539> slide 00:08:15.830 --> 00:08:15.840 align:start position:0% thing to note with this the next slide 00:08:15.840 --> 00:08:17.870 align:start position:0% thing to note with this the next slide is<00:08:16.199> this<00:08:16.440> line<00:08:16.680> here 00:08:17.870 --> 00:08:17.880 align:start position:0% is this line here 00:08:17.880 --> 00:08:21.830 align:start position:0% is this line here bloop<00:08:18.720> does<00:08:19.199> not<00:08:19.379> change<00:08:19.759> and<00:08:20.759> so<00:08:21.060> you<00:08:21.599> see 00:08:21.830 --> 00:08:21.840 align:start position:0% bloop does not change and so you see 00:08:21.840 --> 00:08:23.330 align:start position:0% bloop does not change and so you see you're<00:08:22.139> still<00:08:22.319> creating<00:08:22.560> a<00:08:22.680> signature<00:08:23.099> you're 00:08:23.330 --> 00:08:23.340 align:start position:0% you're still creating a signature you're 00:08:23.340 --> 00:08:24.770 align:start position:0% you're still creating a signature you're just<00:08:23.520> passing<00:08:23.759> the<00:08:23.819> signature<00:08:24.180> in<00:08:24.240> verbatim 00:08:24.770 --> 00:08:24.780 align:start position:0% just passing the signature in verbatim 00:08:24.780 --> 00:08:27.050 align:start position:0% just passing the signature in verbatim and 00:08:27.050 --> 00:08:27.060 align:start position:0% and 00:08:27.060 --> 00:08:27.890 align:start position:0% and um 00:08:27.890 --> 00:08:27.900 align:start position:0% um 00:08:27.900 --> 00:08:30.050 align:start position:0% um yeah<00:08:28.440> basically<00:08:28.919> it's<00:08:29.280> because<00:08:29.460> the<00:08:29.639> ABI<00:08:30.000> is 00:08:30.050 --> 00:08:30.060 align:start position:0% yeah basically it's because the ABI is 00:08:30.060 --> 00:08:31.309 align:start position:0% yeah basically it's because the ABI is encoding<00:08:30.419> it<00:08:30.479> it<00:08:30.599> can<00:08:30.720> look<00:08:30.840> at<00:08:30.960> this<00:08:31.080> object 00:08:31.309 --> 00:08:31.319 align:start position:0% encoding it it can look at this object 00:08:31.319 --> 00:08:33.889 align:start position:0% encoding it it can look at this object and<00:08:31.500> figure<00:08:31.680> out<00:08:31.860> okay<00:08:32.099> I<00:08:32.820> need<00:08:32.940> to<00:08:33.060> take<00:08:33.360> the 00:08:33.889 --> 00:08:33.899 align:start position:0% and figure out okay I need to take the 00:08:33.899 --> 00:08:35.510 align:start position:0% and figure out okay I need to take the difference<00:08:34.080> in<00:08:34.320> this<00:08:34.500> case<00:08:34.560> is<00:08:34.740> the<00:08:34.919> r<00:08:35.099> and<00:08:35.399> the 00:08:35.510 --> 00:08:35.520 align:start position:0% difference in this case is the r and the 00:08:35.520 --> 00:08:37.130 align:start position:0% difference in this case is the r and the Y<00:08:35.640> parity<00:08:36.060> and<00:08:36.300> S 00:08:37.130 --> 00:08:37.140 align:start position:0% Y parity and S 00:08:37.140 --> 00:08:38.990 align:start position:0% Y parity and S for<00:08:37.500> those<00:08:37.620> that<00:08:37.740> aren't<00:08:37.860> familiar<00:08:38.159> with 00:08:38.990 --> 00:08:39.000 align:start position:0% for those that aren't familiar with 00:08:39.000 --> 00:08:40.430 align:start position:0% for those that aren't familiar with um 00:08:40.430 --> 00:08:40.440 align:start position:0% um 00:08:40.440 --> 00:08:45.590 align:start position:0% um uh<00:08:41.159> EIP<00:08:41.779> 2098<00:08:42.800> basically<00:08:43.800> this<00:08:44.039> allows<00:08:44.459> you 00:08:45.590 --> 00:08:45.600 align:start position:0% uh EIP 2098 basically this allows you 00:08:45.600 --> 00:08:47.269 align:start position:0% uh EIP 2098 basically this allows you signatures<00:08:46.320> are<00:08:46.500> much<00:08:46.680> bigger<00:08:46.860> than<00:08:46.920> need<00:08:47.160> to 00:08:47.269 --> 00:08:47.279 align:start position:0% signatures are much bigger than need to 00:08:47.279 --> 00:08:49.370 align:start position:0% signatures are much bigger than need to be<00:08:47.399> so<00:08:47.820> basically<00:08:48.180> you're<00:08:48.420> used<00:08:48.600> to<00:08:48.779> RS<00:08:49.019> and<00:08:49.200> V 00:08:49.370 --> 00:08:49.380 align:start position:0% be so basically you're used to RS and V 00:08:49.380 --> 00:08:52.490 align:start position:0% be so basically you're used to RS and V that<00:08:50.040> V<00:08:50.220> is<00:08:50.459> actually<00:08:50.640> just<00:08:50.880> one<00:08:51.180> bit<00:08:51.500> and 00:08:52.490 --> 00:08:52.500 align:start position:0% that V is actually just one bit and 00:08:52.500 --> 00:08:56.930 align:start position:0% that V is actually just one bit and thanks<00:08:52.740> to<00:08:52.920> Homestead<00:08:53.660> uh<00:08:54.660> every<00:08:55.080> s<00:08:55.680> value<00:08:56.339> in 00:08:56.930 --> 00:08:56.940 align:start position:0% thanks to Homestead uh every s value in 00:08:56.940 --> 00:08:59.090 align:start position:0% thanks to Homestead uh every s value in ethereum<00:08:57.540> is<00:08:58.080> actually<00:08:58.260> always<00:08:58.500> got<00:08:58.740> the<00:08:58.980> top 00:08:59.090 --> 00:08:59.100 align:start position:0% ethereum is actually always got the top 00:08:59.100 --> 00:09:01.430 align:start position:0% ethereum is actually always got the top bit<00:08:59.339> set<00:08:59.580> to<00:08:59.820> zero<00:09:00.180> so<00:09:00.720> we<00:09:00.959> kind<00:09:01.080> of<00:09:01.200> just<00:09:01.260> like 00:09:01.430 --> 00:09:01.440 align:start position:0% bit set to zero so we kind of just like 00:09:01.440 --> 00:09:04.610 align:start position:0% bit set to zero so we kind of just like slot<00:09:01.920> that<00:09:02.100> in<00:09:02.339> and<00:09:03.060> now<00:09:03.240> your<00:09:03.480> signatures<00:09:03.959> are 00:09:04.610 --> 00:09:04.620 align:start position:0% slot that in and now your signatures are 00:09:04.620 --> 00:09:08.990 align:start position:0% slot that in and now your signatures are 60<00:09:05.040> 30<00:09:05.700> smaller<00:09:06.560> and<00:09:07.560> uh 00:09:08.990 --> 00:09:09.000 align:start position:0% 60 30 smaller and uh 00:09:09.000 --> 00:09:10.790 align:start position:0% 60 30 smaller and uh yeah<00:09:09.600> again<00:09:09.899> feel<00:09:10.200> free<00:09:10.380> to<00:09:10.440> ask<00:09:10.560> questions 00:09:10.790 --> 00:09:10.800 align:start position:0% yeah again feel free to ask questions 00:09:10.800 --> 00:09:12.590 align:start position:0% yeah again feel free to ask questions because<00:09:11.279> these<00:09:11.640> are<00:09:11.760> going<00:09:11.880> to<00:09:11.880> be<00:09:12.120> a<00:09:12.540> little 00:09:12.590 --> 00:09:12.600 align:start position:0% because these are going to be a little 00:09:12.600 --> 00:09:15.050 align:start position:0% because these are going to be a little complicated<00:09:13.080> but<00:09:13.440> you<00:09:14.279> need<00:09:14.640> a<00:09:14.760> little<00:09:14.820> bit<00:09:14.940> of 00:09:15.050 --> 00:09:15.060 align:start position:0% complicated but you need a little bit of 00:09:15.060 --> 00:09:17.750 align:start position:0% complicated but you need a little bit of more<00:09:15.420> math<00:09:15.600> to<00:09:15.959> help<00:09:16.140> decouple<00:09:16.800> that<00:09:16.980> I'm 00:09:17.750 --> 00:09:17.760 align:start position:0% more math to help decouple that I'm 00:09:17.760 --> 00:09:20.870 align:start position:0% more math to help decouple that I'm going<00:09:17.940> to<00:09:18.060> bug<00:09:18.300> the<00:09:18.600> the<00:09:19.500> um<00:09:19.500> facility<00:09:20.339> guys<00:09:20.700> to 00:09:20.870 --> 00:09:20.880 align:start position:0% going to bug the the um facility guys to 00:09:20.880 --> 00:09:22.790 align:start position:0% going to bug the the um facility guys to see<00:09:20.940> if<00:09:21.060> we<00:09:21.180> can<00:09:21.240> kind<00:09:21.360> of<00:09:21.480> get<00:09:21.600> this<00:09:22.019> built 00:09:22.790 --> 00:09:22.800 align:start position:0% see if we can kind of get this built 00:09:22.800 --> 00:09:24.530 align:start position:0% see if we can kind of get this built more<00:09:22.980> into<00:09:23.160> solidity<00:09:23.640> so<00:09:23.880> you<00:09:24.000> just<00:09:24.180> pass<00:09:24.360> in 00:09:24.530 --> 00:09:24.540 align:start position:0% more into solidity so you just pass in 00:09:24.540 --> 00:09:26.570 align:start position:0% more into solidity so you just pass in the<00:09:24.660> signature<00:09:25.019> directly<00:09:25.399> but<00:09:26.399> in<00:09:26.519> the 00:09:26.570 --> 00:09:26.580 align:start position:0% the signature directly but in the 00:09:26.580 --> 00:09:28.910 align:start position:0% the signature directly but in the meantime<00:09:26.880> this<00:09:27.300> is<00:09:27.420> still<00:09:27.720> much<00:09:28.260> simpler<00:09:28.620> than 00:09:28.910 --> 00:09:28.920 align:start position:0% meantime this is still much simpler than 00:09:28.920 --> 00:09:31.130 align:start position:0% meantime this is still much simpler than the<00:09:29.220> like<00:09:29.459> couple<00:09:29.760> dozen<00:09:30.120> of<00:09:30.240> lines<00:09:30.540> of<00:09:30.839> bite 00:09:31.130 --> 00:09:31.140 align:start position:0% the like couple dozen of lines of bite 00:09:31.140 --> 00:09:33.110 align:start position:0% the like couple dozen of lines of bite manipulation<00:09:31.740> byte<00:09:32.220> manipulation<00:09:32.700> libraries 00:09:33.110 --> 00:09:33.120 align:start position:0% manipulation byte manipulation libraries 00:09:33.120 --> 00:09:34.670 align:start position:0% manipulation byte manipulation libraries that's<00:09:33.420> going<00:09:33.779> on 00:09:34.670 --> 00:09:34.680 align:start position:0% that's going on 00:09:34.680 --> 00:09:38.210 align:start position:0% that's going on um<00:09:34.740> if<00:09:34.920> you<00:09:35.040> pass<00:09:35.100> into<00:09:35.220> bytes 00:09:38.210 --> 00:09:38.220 align:start position:0% 00:09:38.220 --> 00:09:40.070 align:start position:0% um<00:09:38.339> so<00:09:38.640> quick<00:09:38.880> comparison<00:09:39.300> so<00:09:39.660> if<00:09:39.779> you<00:09:39.899> use<00:09:39.959> the 00:09:40.070 --> 00:09:40.080 align:start position:0% um so quick comparison so if you use the 00:09:40.080 --> 00:09:41.509 align:start position:0% um so quick comparison so if you use the raw<00:09:40.260> bytes<00:09:40.500> like<00:09:40.620> most<00:09:40.800> people<00:09:40.920> do<00:09:41.100> today<00:09:41.279> it's 00:09:41.509 --> 00:09:41.519 align:start position:0% raw bytes like most people do today it's 00:09:41.519 --> 00:09:44.030 align:start position:0% raw bytes like most people do today it's 160<00:09:41.940> bytes<00:09:42.360> which<00:09:42.660> is<00:09:42.839> by<00:09:43.260> itself<00:09:43.560> just<00:09:43.860> for 00:09:44.030 --> 00:09:44.040 align:start position:0% 160 bytes which is by itself just for 00:09:44.040 --> 00:09:49.490 align:start position:0% 160 bytes which is by itself just for the<00:09:44.160> call<00:09:44.279> data<00:09:44.640> is<00:09:44.880> 144<00:09:45.839> gas<00:09:46.940> expensive<00:09:48.440> so<00:09:49.440> if 00:09:49.490 --> 00:09:49.500 align:start position:0% the call data is 144 gas expensive so if 00:09:49.500 --> 00:09:51.350 align:start position:0% the call data is 144 gas expensive so if you<00:09:49.620> use<00:09:49.740> decompose<00:09:50.160> that's<00:09:50.399> 96<00:09:50.820> bytes<00:09:51.120> but<00:09:51.240> if 00:09:51.350 --> 00:09:51.360 align:start position:0% you use decompose that's 96 bytes but if 00:09:51.360 --> 00:09:52.610 align:start position:0% you use decompose that's 96 bytes but if you<00:09:51.420> use<00:09:51.540> the<00:09:51.720> compact<00:09:51.959> representation<00:09:52.440> it's 00:09:52.610 --> 00:09:52.620 align:start position:0% you use the compact representation it's 00:09:52.620 --> 00:09:54.590 align:start position:0% you use the compact representation it's 64<00:09:53.100> bytes 00:09:54.590 --> 00:09:54.600 align:start position:0% 64 bytes 00:09:54.600 --> 00:09:55.250 align:start position:0% 64 bytes um 00:09:55.250 --> 00:09:55.260 align:start position:0% um 00:09:55.260 --> 00:09:56.810 align:start position:0% um yeah<00:09:55.740> I'm<00:09:55.920> not<00:09:56.040> gonna<00:09:56.160> go<00:09:56.279> to<00:09:56.399> more<00:09:56.519> than<00:09:56.640> that 00:09:56.810 --> 00:09:56.820 align:start position:0% yeah I'm not gonna go to more than that 00:09:56.820 --> 00:09:58.790 align:start position:0% yeah I'm not gonna go to more than that uh<00:09:57.600> that<00:09:57.839> was<00:09:57.959> just<00:09:58.140> a<00:09:58.260> quick<00:09:58.380> thing<00:09:58.560> for 00:09:58.790 --> 00:09:58.800 align:start position:0% uh that was just a quick thing for 00:09:58.800 --> 00:09:59.870 align:start position:0% uh that was just a quick thing for people<00:09:58.920> who<00:09:59.100> are<00:09:59.220> looking<00:09:59.339> at<00:09:59.459> the<00:09:59.519> slides 00:09:59.870 --> 00:09:59.880 align:start position:0% people who are looking at the slides 00:09:59.880 --> 00:10:02.509 align:start position:0% people who are looking at the slides afterwards<00:10:00.899> transactions<00:10:01.740> are<00:10:01.920> also<00:10:02.160> now<00:10:02.279> an 00:10:02.509 --> 00:10:02.519 align:start position:0% afterwards transactions are also now an 00:10:02.519 --> 00:10:06.290 align:start position:0% afterwards transactions are also now an object<00:10:02.820> so<00:10:03.380> if<00:10:04.380> you<00:10:04.700> decouple<00:10:05.700> a<00:10:05.940> transaction 00:10:06.290 --> 00:10:06.300 align:start position:0% object so if you decouple a transaction 00:10:06.300 --> 00:10:07.910 align:start position:0% object so if you decouple a transaction if<00:10:06.660> you<00:10:06.839> just<00:10:06.899> feed<00:10:07.019> in<00:10:07.200> a<00:10:07.320> bunch<00:10:07.440> of<00:10:07.560> raw<00:10:07.740> like 00:10:07.910 --> 00:10:07.920 align:start position:0% if you just feed in a bunch of raw like 00:10:07.920 --> 00:10:09.650 align:start position:0% if you just feed in a bunch of raw like a<00:10:08.040> raw<00:10:08.220> transaction<00:10:08.519> object<00:10:08.940> or<00:10:09.180> a<00:10:09.300> bunch<00:10:09.480> of 00:10:09.650 --> 00:10:09.660 align:start position:0% a raw transaction object or a bunch of 00:10:09.660 --> 00:10:12.590 align:start position:0% a raw transaction object or a bunch of stuff<00:10:10.080> if<00:10:10.980> you<00:10:11.100> start<00:10:11.220> updating<00:10:11.700> the<00:10:11.940> stuff<00:10:12.180> it 00:10:12.590 --> 00:10:12.600 align:start position:0% stuff if you start updating the stuff it 00:10:12.600 --> 00:10:14.930 align:start position:0% stuff if you start updating the stuff it updates<00:10:12.839> the<00:10:13.140> other<00:10:13.320> parts<00:10:13.680> of<00:10:13.860> it<00:10:13.980> as<00:10:14.160> well 00:10:14.930 --> 00:10:14.940 align:start position:0% updates the other parts of it as well 00:10:14.940 --> 00:10:15.889 align:start position:0% updates the other parts of it as well um 00:10:15.889 --> 00:10:15.899 align:start position:0% um 00:10:15.899 --> 00:10:17.990 align:start position:0% um yes<00:10:16.560> basically 00:10:17.990 --> 00:10:18.000 align:start position:0% yes basically 00:10:18.000 --> 00:10:19.970 align:start position:0% yes basically when<00:10:18.720> you<00:10:18.899> have<00:10:18.959> just<00:10:19.080> an<00:10:19.200> object<00:10:19.440> and<00:10:19.680> you<00:10:19.800> set 00:10:19.970 --> 00:10:19.980 align:start position:0% when you have just an object and you set 00:10:19.980 --> 00:10:21.410 align:start position:0% when you have just an object and you set some<00:10:20.160> property<00:10:20.459> on<00:10:20.580> it<00:10:20.700> you're<00:10:20.940> only<00:10:21.120> opening 00:10:21.410 --> 00:10:21.420 align:start position:0% some property on it you're only opening 00:10:21.420 --> 00:10:23.509 align:start position:0% some property on it you're only opening that<00:10:21.540> property<00:10:21.839> but<00:10:22.019> with<00:10:22.380> this<00:10:22.560> when<00:10:23.160> you<00:10:23.279> set 00:10:23.509 --> 00:10:23.519 align:start position:0% that property but with this when you set 00:10:23.519 --> 00:10:25.190 align:start position:0% that property but with this when you set a<00:10:23.700> property<00:10:24.000> it<00:10:24.420> sets<00:10:24.660> that<00:10:24.779> property<00:10:25.019> but 00:10:25.190 --> 00:10:25.200 align:start position:0% a property it sets that property but 00:10:25.200 --> 00:10:27.650 align:start position:0% a property it sets that property but also<00:10:25.440> updates<00:10:25.800> all<00:10:26.160> the<00:10:26.399> all<00:10:27.000> the<00:10:27.180> entangled 00:10:27.650 --> 00:10:27.660 align:start position:0% also updates all the all the entangled 00:10:27.660 --> 00:10:30.530 align:start position:0% also updates all the all the entangled properties<00:10:28.080> for<00:10:28.500> example<00:10:28.940> if<00:10:29.940> you<00:10:30.060> set<00:10:30.300> the 00:10:30.530 --> 00:10:30.540 align:start position:0% properties for example if you set the 00:10:30.540 --> 00:10:33.530 align:start position:0% properties for example if you set the gas<00:10:30.779> price<00:10:31.080> then<00:10:31.920> the<00:10:32.279> serialized<00:10:33.000> version<00:10:33.240> of 00:10:33.530 --> 00:10:33.540 align:start position:0% gas price then the serialized version of 00:10:33.540 --> 00:10:36.110 align:start position:0% gas price then the serialized version of that<00:10:33.660> transaction<00:10:34.019> should<00:10:34.260> update 00:10:36.110 --> 00:10:36.120 align:start position:0% that transaction should update 00:10:36.120 --> 00:10:36.650 align:start position:0% that transaction should update um 00:10:36.650 --> 00:10:36.660 align:start position:0% um 00:10:36.660 --> 00:10:38.509 align:start position:0% um and<00:10:37.260> you<00:10:37.380> can<00:10:37.500> just<00:10:37.620> set<00:10:37.800> things<00:10:38.040> you<00:10:38.220> can<00:10:38.339> set 00:10:38.509 --> 00:10:38.519 align:start position:0% and you can just set things you can set 00:10:38.519 --> 00:10:39.829 align:start position:0% and you can just set things you can set them<00:10:38.640> to<00:10:38.820> anything<00:10:39.000> that's<00:10:39.240> valid<00:10:39.600> you<00:10:39.720> could 00:10:39.829 --> 00:10:39.839 align:start position:0% them to anything that's valid you could 00:10:39.839 --> 00:10:41.750 align:start position:0% them to anything that's valid you could so<00:10:40.019> in<00:10:40.140> this<00:10:40.260> case<00:10:40.380> I'm<00:10:40.560> using<00:10:40.800> a<00:10:40.860> bigint<00:10:41.160> but 00:10:41.750 --> 00:10:41.760 align:start position:0% so in this case I'm using a bigint but 00:10:41.760 --> 00:10:43.130 align:start position:0% so in this case I'm using a bigint but you<00:10:41.880> could<00:10:42.000> pass<00:10:42.180> it<00:10:42.360> a<00:10:42.540> string<00:10:42.779> you<00:10:42.959> could 00:10:43.130 --> 00:10:43.140 align:start position:0% you could pass it a string you could 00:10:43.140 --> 00:10:46.430 align:start position:0% you could pass it a string you could pass<00:10:43.320> in<00:10:43.560> a<00:10:44.279> hex<00:10:44.640> string<00:10:44.940> pass<00:10:45.360> in<00:10:45.660> pretty<00:10:46.320> much 00:10:46.430 --> 00:10:46.440 align:start position:0% pass in a hex string pass in pretty much 00:10:46.440 --> 00:10:48.410 align:start position:0% pass in a hex string pass in pretty much anything<00:10:46.620> you<00:10:46.920> want<00:10:47.100> that<00:10:47.459> makes<00:10:47.640> sense<00:10:47.880> for<00:10:48.180> a 00:10:48.410 --> 00:10:48.420 align:start position:0% anything you want that makes sense for a 00:10:48.420 --> 00:10:52.790 align:start position:0% anything you want that makes sense for a Max<00:10:48.540> fee<00:10:48.959> per<00:10:49.140> gas<00:10:49.380> and<00:10:50.339> it'll<00:10:50.640> be<00:10:50.760> reflected 00:10:52.790 --> 00:10:52.800 align:start position:0% Max fee per gas and it'll be reflected 00:10:52.800 --> 00:10:55.430 align:start position:0% Max fee per gas and it'll be reflected uh<00:10:53.579> 13<00:10:53.880> minutes<00:10:54.240> bits<00:10:54.839> so<00:10:55.019> this<00:10:55.140> is<00:10:55.260> just<00:10:55.380> a 00:10:55.430 --> 00:10:55.440 align:start position:0% uh 13 minutes bits so this is just a 00:10:55.440 --> 00:10:57.110 align:start position:0% uh 13 minutes bits so this is just a little<00:10:55.560> odds<00:10:55.860> and<00:10:55.920> ends<00:10:56.220> of<00:10:56.399> like<00:10:56.579> random 00:10:57.110 --> 00:10:57.120 align:start position:0% little odds and ends of like random 00:10:57.120 --> 00:11:01.190 align:start position:0% little odds and ends of like random things<00:10:57.440> so<00:10:58.440> pausing<00:10:58.920> providers<00:11:00.019> so<00:11:01.019> for 00:11:01.190 --> 00:11:01.200 align:start position:0% things so pausing providers so for 00:11:01.200 --> 00:11:03.050 align:start position:0% things so pausing providers so for example<00:11:01.440> a<00:11:01.620> lot<00:11:01.740> of<00:11:01.800> people<00:11:01.860> find<00:11:02.160> that<00:11:02.519> people 00:11:03.050 --> 00:11:03.060 align:start position:0% example a lot of people find that people 00:11:03.060 --> 00:11:06.470 align:start position:0% example a lot of people find that people keep<00:11:03.660> their<00:11:04.320> their<00:11:04.940> customers<00:11:05.940> keep<00:11:06.240> their 00:11:06.470 --> 00:11:06.480 align:start position:0% keep their their customers keep their 00:11:06.480 --> 00:11:08.569 align:start position:0% keep their their customers keep their their<00:11:06.720> app<00:11:06.959> open<00:11:07.140> in<00:11:07.440> a<00:11:07.620> tab<00:11:07.800> that<00:11:08.399> they're<00:11:08.459> not 00:11:08.569 --> 00:11:08.579 align:start position:0% their app open in a tab that they're not 00:11:08.579 --> 00:11:10.430 align:start position:0% their app open in a tab that they're not even<00:11:08.760> looking<00:11:08.940> at<00:11:09.060> anymore<00:11:09.240> which<00:11:09.899> means<00:11:10.200> that 00:11:10.430 --> 00:11:10.440 align:start position:0% even looking at anymore which means that 00:11:10.440 --> 00:11:12.350 align:start position:0% even looking at anymore which means that their<00:11:10.740> events<00:11:11.160> are<00:11:11.279> still<00:11:11.399> firing<00:11:11.760> it's<00:11:12.060> still 00:11:12.350 --> 00:11:12.360 align:start position:0% their events are still firing it's still 00:11:12.360 --> 00:11:14.569 align:start position:0% their events are still firing it's still hitting<00:11:12.839> the<00:11:13.079> inferior<00:11:13.680> gobbling<00:11:14.220> up<00:11:14.339> all 00:11:14.569 --> 00:11:14.579 align:start position:0% hitting the inferior gobbling up all 00:11:14.579 --> 00:11:16.730 align:start position:0% hitting the inferior gobbling up all their<00:11:14.760> all<00:11:15.060> their<00:11:15.240> requests 00:11:16.730 --> 00:11:16.740 align:start position:0% their all their requests 00:11:16.740 --> 00:11:18.470 align:start position:0% their all their requests um well<00:11:17.040> because<00:11:17.640> there's<00:11:18.120> now<00:11:18.240> these 00:11:18.470 --> 00:11:18.480 align:start position:0% um well because there's now these 00:11:18.480 --> 00:11:20.210 align:start position:0% um well because there's now these visibility<00:11:18.779> apis<00:11:19.260> available<00:11:19.560> in<00:11:19.800> browsers 00:11:20.210 --> 00:11:20.220 align:start position:0% visibility apis available in browsers 00:11:20.220 --> 00:11:23.750 align:start position:0% visibility apis available in browsers you<00:11:21.000> can<00:11:21.060> tell<00:11:21.300> ethers<00:11:21.959> by<00:11:22.140> the<00:11:22.320> way<00:11:22.440> when<00:11:23.339> when 00:11:23.750 --> 00:11:23.760 align:start position:0% you can tell ethers by the way when when 00:11:23.760 --> 00:11:25.790 align:start position:0% you can tell ethers by the way when when I'm<00:11:24.120> not<00:11:24.300> visible<00:11:24.600> anymore<00:11:24.779> pause<00:11:25.500> the 00:11:25.790 --> 00:11:25.800 align:start position:0% I'm not visible anymore pause the 00:11:25.800 --> 00:11:27.170 align:start position:0% I'm not visible anymore pause the provider 00:11:27.170 --> 00:11:27.180 align:start position:0% provider 00:11:27.180 --> 00:11:28.910 align:start position:0% provider um that<00:11:27.480> way<00:11:27.600> if<00:11:27.899> they<00:11:28.019> go<00:11:28.320> to<00:11:28.440> another<00:11:28.560> page 00:11:28.910 --> 00:11:28.920 align:start position:0% um that way if they go to another page 00:11:28.920 --> 00:11:30.350 align:start position:0% um that way if they go to another page for<00:11:29.100> a<00:11:29.220> week<00:11:29.339> and<00:11:29.519> then<00:11:29.640> they<00:11:29.760> find<00:11:29.940> that<00:11:30.060> tab 00:11:30.350 --> 00:11:30.360 align:start position:0% for a week and then they find that tab 00:11:30.360 --> 00:11:32.389 align:start position:0% for a week and then they find that tab that's<00:11:30.540> left<00:11:30.839> around<00:11:31.079> from<00:11:31.440> like<00:11:31.620> a<00:11:31.860> week<00:11:32.100> ago 00:11:32.389 --> 00:11:32.399 align:start position:0% that's left around from like a week ago 00:11:32.399 --> 00:11:34.250 align:start position:0% that's left around from like a week ago or<00:11:32.519> a<00:11:32.640> month<00:11:32.760> ago<00:11:33.000> or<00:11:33.180> we<00:11:33.720> all<00:11:33.839> have<00:11:33.959> really<00:11:34.079> old 00:11:34.250 --> 00:11:34.260 align:start position:0% or a month ago or we all have really old 00:11:34.260 --> 00:11:35.690 align:start position:0% or a month ago or we all have really old tabs 00:11:35.690 --> 00:11:35.700 align:start position:0% tabs 00:11:35.700 --> 00:11:37.610 align:start position:0% tabs um<00:11:35.820> this<00:11:36.360> way<00:11:36.540> they<00:11:36.779> haven't<00:11:36.899> been<00:11:37.140> consuming 00:11:37.610 --> 00:11:37.620 align:start position:0% um this way they haven't been consuming 00:11:37.620 --> 00:11:39.290 align:start position:0% um this way they haven't been consuming your<00:11:38.040> your<00:11:38.220> bandwidth<00:11:38.700> every<00:11:38.820> time<00:11:39.000> that 00:11:39.290 --> 00:11:39.300 align:start position:0% your your bandwidth every time that 00:11:39.300 --> 00:11:41.090 align:start position:0% your your bandwidth every time that you've<00:11:39.600> been<00:11:39.839> they've<00:11:40.680> been<00:11:40.800> doing<00:11:40.920> nothing 00:11:41.090 --> 00:11:41.100 align:start position:0% you've been they've been doing nothing 00:11:41.100 --> 00:11:44.210 align:start position:0% you've been they've been doing nothing with<00:11:41.339> your<00:11:41.519> site<00:11:41.700> so<00:11:42.420> you<00:11:43.200> can<00:11:43.320> pause<00:11:43.860> your 00:11:44.210 --> 00:11:44.220 align:start position:0% with your site so you can pause your 00:11:44.220 --> 00:11:46.370 align:start position:0% with your site so you can pause your provider<00:11:44.700> and<00:11:45.240> then<00:11:45.360> when<00:11:45.540> it<00:11:45.660> comes<00:11:45.839> when<00:11:46.019> the 00:11:46.370 --> 00:11:46.380 align:start position:0% provider and then when it comes when the 00:11:46.380 --> 00:11:48.410 align:start position:0% provider and then when it comes when the tab<00:11:46.680> becomes<00:11:46.920> visibly<00:11:47.279> visible<00:11:47.880> again<00:11:48.060> you 00:11:48.410 --> 00:11:48.420 align:start position:0% tab becomes visibly visible again you 00:11:48.420 --> 00:11:50.210 align:start position:0% tab becomes visibly visible again you can<00:11:48.480> resume<00:11:48.660> and<00:11:49.440> you<00:11:49.560> get<00:11:49.680> the<00:11:49.800> choice<00:11:49.980> of 00:11:50.210 --> 00:11:50.220 align:start position:0% can resume and you get the choice of 00:11:50.220 --> 00:11:51.530 align:start position:0% can resume and you get the choice of whether<00:11:50.399> you<00:11:50.579> want<00:11:50.700> to<00:11:50.820> replay<00:11:51.000> all<00:11:51.480> the 00:11:51.530 --> 00:11:51.540 align:start position:0% whether you want to replay all the 00:11:51.540 --> 00:11:53.630 align:start position:0% whether you want to replay all the events<00:11:51.899> that<00:11:52.140> would<00:11:52.320> have<00:11:52.500> happened<00:11:52.740> during 00:11:53.630 --> 00:11:53.640 align:start position:0% events that would have happened during 00:11:53.640 --> 00:11:56.269 align:start position:0% events that would have happened during the<00:11:53.940> time<00:11:54.060> that<00:11:54.240> was<00:11:54.420> paused<00:11:54.959> or<00:11:55.620> whether<00:11:56.100> you 00:11:56.269 --> 00:11:56.279 align:start position:0% the time that was paused or whether you 00:11:56.279 --> 00:11:57.710 align:start position:0% the time that was paused or whether you kind<00:11:56.459> of<00:11:56.519> watched<00:11:56.880> you<00:11:57.000> just<00:11:57.180> drop<00:11:57.300> them<00:11:57.540> and 00:11:57.710 --> 00:11:57.720 align:start position:0% kind of watched you just drop them and 00:11:57.720 --> 00:12:00.050 align:start position:0% kind of watched you just drop them and keep<00:11:57.839> keep<00:11:58.320> on<00:11:58.500> going<00:11:58.680> both<00:11:59.160> situations<00:11:59.640> have 00:12:00.050 --> 00:12:00.060 align:start position:0% keep keep on going both situations have 00:12:00.060 --> 00:12:03.710 align:start position:0% keep keep on going both situations have like<00:12:00.360> valid<00:12:00.720> use<00:12:00.839> cases<00:12:01.200> so<00:12:01.860> up<00:12:02.700> to<00:12:02.880> your<00:12:03.180> own 00:12:03.710 --> 00:12:03.720 align:start position:0% like valid use cases so up to your own 00:12:03.720 --> 00:12:05.389 align:start position:0% like valid use cases so up to your own personal<00:12:04.079> use<00:12:04.500> case 00:12:05.389 --> 00:12:05.399 align:start position:0% personal use case 00:12:05.399 --> 00:12:07.550 align:start position:0% personal use case um<00:12:05.880> uh<00:12:06.360> the<00:12:06.600> cool<00:12:06.779> thing<00:12:06.899> with<00:12:07.079> this<00:12:07.260> feature 00:12:07.550 --> 00:12:07.560 align:start position:0% um uh the cool thing with this feature 00:12:07.560 --> 00:12:09.370 align:start position:0% um uh the cool thing with this feature is<00:12:07.680> because<00:12:07.860> we<00:12:08.160> can<00:12:08.279> now<00:12:08.399> pause<00:12:08.640> and<00:12:08.880> unpause 00:12:09.370 --> 00:12:09.380 align:start position:0% is because we can now pause and unpause 00:12:09.380 --> 00:12:13.370 align:start position:0% is because we can now pause and unpause uh<00:12:10.380> providers<00:12:10.920> all<00:12:11.700> the<00:12:11.880> underlying<00:12:12.420> API<00:12:13.140> and 00:12:13.370 --> 00:12:13.380 align:start position:0% uh providers all the underlying API and 00:12:13.380 --> 00:12:15.350 align:start position:0% uh providers all the underlying API and framework<00:12:13.740> changes<00:12:14.160> that<00:12:14.399> went<00:12:14.880> into<00:12:15.120> making 00:12:15.350 --> 00:12:15.360 align:start position:0% framework changes that went into making 00:12:15.360 --> 00:12:17.090 align:start position:0% framework changes that went into making this<00:12:15.720> happen<00:12:15.899> it<00:12:16.500> means<00:12:16.680> that<00:12:16.740> if<00:12:16.860> you<00:12:16.980> have 00:12:17.090 --> 00:12:17.100 align:start position:0% this happen it means that if you have 00:12:17.100 --> 00:12:18.170 align:start position:0% this happen it means that if you have for<00:12:17.160> example<00:12:17.339> a<00:12:17.519> websocket<00:12:18.000> and<00:12:18.060> the 00:12:18.170 --> 00:12:18.180 align:start position:0% for example a websocket and the 00:12:18.180 --> 00:12:20.030 align:start position:0% for example a websocket and the websocket<00:12:18.600> disconnects<00:12:19.200> it<00:12:19.800> can<00:12:19.920> now 00:12:20.030 --> 00:12:20.040 align:start position:0% websocket disconnects it can now 00:12:20.040 --> 00:12:22.670 align:start position:0% websocket disconnects it can now reconnect<00:12:20.399> and<00:12:21.300> re-subscribe<00:12:21.959> to<00:12:22.140> all<00:12:22.440> your 00:12:22.670 --> 00:12:22.680 align:start position:0% reconnect and re-subscribe to all your 00:12:22.680 --> 00:12:25.310 align:start position:0% reconnect and re-subscribe to all your events<00:12:23.339> before<00:12:24.120> it<00:12:24.420> starts<00:12:24.720> feeding<00:12:25.079> you<00:12:25.140> the 00:12:25.310 --> 00:12:25.320 align:start position:0% events before it starts feeding you the 00:12:25.320 --> 00:12:26.930 align:start position:0% events before it starts feeding you the new<00:12:25.440> events<00:12:25.800> that<00:12:25.860> start<00:12:26.040> coming<00:12:26.279> in<00:12:26.519> it<00:12:26.820> can 00:12:26.930 --> 00:12:26.940 align:start position:0% new events that start coming in it can 00:12:26.940 --> 00:12:28.310 align:start position:0% new events that start coming in it can actually<00:12:27.120> get<00:12:27.420> the<00:12:27.540> events<00:12:27.839> that<00:12:27.959> happen<00:12:28.140> from 00:12:28.310 --> 00:12:28.320 align:start position:0% actually get the events that happen from 00:12:28.320 --> 00:12:29.569 align:start position:0% actually get the events that happen from the<00:12:28.440> time<00:12:28.560> it<00:12:28.740> disconnected<00:12:29.160> from<00:12:29.339> the<00:12:29.519> time 00:12:29.569 --> 00:12:29.579 align:start position:0% the time it disconnected from the time 00:12:29.579 --> 00:12:31.610 align:start position:0% the time it disconnected from the time that<00:12:29.760> is<00:12:30.000> now<00:12:30.240> and<00:12:30.899> so<00:12:31.019> all<00:12:31.140> your<00:12:31.260> events<00:12:31.500> come 00:12:31.610 --> 00:12:31.620 align:start position:0% that is now and so all your events come 00:12:31.620 --> 00:12:33.470 align:start position:0% that is now and so all your events come back<00:12:31.740> in<00:12:31.920> order<00:12:32.100> and<00:12:32.760> you<00:12:32.880> don't<00:12:33.060> miss<00:12:33.180> a<00:12:33.360> beat 00:12:33.470 --> 00:12:33.480 align:start position:0% back in order and you don't miss a beat 00:12:33.480 --> 00:12:34.490 align:start position:0% back in order and you don't miss a beat and<00:12:33.839> you<00:12:33.899> don't<00:12:34.019> even<00:12:34.140> know<00:12:34.260> that<00:12:34.380> your 00:12:34.490 --> 00:12:34.500 align:start position:0% and you don't even know that your 00:12:34.500 --> 00:12:37.250 align:start position:0% and you don't even know that your websocket<00:12:34.920> crashed 00:12:37.250 --> 00:12:37.260 align:start position:0% websocket crashed 00:12:37.260 --> 00:12:38.210 align:start position:0% websocket crashed um 00:12:38.210 --> 00:12:38.220 align:start position:0% um 00:12:38.220 --> 00:12:40.009 align:start position:0% um and<00:12:38.880> ordinance 00:12:40.009 --> 00:12:40.019 align:start position:0% and ordinance 00:12:40.019 --> 00:12:41.090 align:start position:0% and ordinance um<00:12:40.079> I'll<00:12:40.320> just<00:12:40.440> go<00:12:40.560> to<00:12:40.680> these<00:12:40.800> quickly 00:12:41.090 --> 00:12:41.100 align:start position:0% um I'll just go to these quickly 00:12:41.100 --> 00:12:43.190 align:start position:0% um I'll just go to these quickly basically<00:12:41.700> networks<00:12:42.180> are<00:12:42.600> now<00:12:42.720> a<00:12:42.899> plug-in 00:12:43.190 --> 00:12:43.200 align:start position:0% basically networks are now a plug-in 00:12:43.200 --> 00:12:45.590 align:start position:0% basically networks are now a plug-in they<00:12:43.500> have<00:12:43.620> a<00:12:43.740> plug-in<00:12:44.040> system<00:12:44.360> there's<00:12:45.360> a<00:12:45.540> lot 00:12:45.590 --> 00:12:45.600 align:start position:0% they have a plug-in system there's a lot 00:12:45.600 --> 00:12:47.150 align:start position:0% they have a plug-in system there's a lot of<00:12:45.720> really<00:12:45.959> strange<00:12:46.320> networks<00:12:46.800> out<00:12:46.860> there<00:12:46.980> and 00:12:47.150 --> 00:12:47.160 align:start position:0% of really strange networks out there and 00:12:47.160 --> 00:12:48.710 align:start position:0% of really strange networks out there and I<00:12:47.279> always<00:12:47.339> get<00:12:47.579> like<00:12:47.700> requests<00:12:48.180> saying<00:12:48.480> like 00:12:48.710 --> 00:12:48.720 align:start position:0% I always get like requests saying like 00:12:48.720 --> 00:12:51.110 align:start position:0% I always get like requests saying like oh<00:12:49.139> my<00:12:49.620> network<00:12:49.860> computes<00:12:50.399> hashes<00:12:50.760> in<00:12:50.940> this 00:12:51.110 --> 00:12:51.120 align:start position:0% oh my network computes hashes in this 00:12:51.120 --> 00:12:52.730 align:start position:0% oh my network computes hashes in this strange<00:12:51.420> way<00:12:51.600> or<00:12:51.959> my<00:12:52.139> network<00:12:52.320> doesn't 00:12:52.730 --> 00:12:52.740 align:start position:0% strange way or my network doesn't 00:12:52.740 --> 00:12:54.949 align:start position:0% strange way or my network doesn't doesn't<00:12:53.279> have<00:12:53.579> an<00:12:53.760> author<00:12:54.120> in<00:12:54.240> the<00:12:54.360> block<00:12:54.540> or 00:12:54.949 --> 00:12:54.959 align:start position:0% doesn't have an author in the block or 00:12:54.959 --> 00:12:57.050 align:start position:0% doesn't have an author in the block or this<00:12:55.139> sort<00:12:55.320> of<00:12:55.380> thing<00:12:55.500> in<00:12:55.680> the<00:12:55.860> other<00:12:55.980> so<00:12:56.880> this 00:12:57.050 --> 00:12:57.060 align:start position:0% this sort of thing in the other so this 00:12:57.060 --> 00:12:59.509 align:start position:0% this sort of thing in the other so this makes<00:12:57.240> it<00:12:57.420> possible<00:12:57.660> that<00:12:57.959> ethers<00:12:58.500> can<00:12:58.620> stop 00:12:59.509 --> 00:12:59.519 align:start position:0% makes it possible that ethers can stop 00:12:59.519 --> 00:13:01.250 align:start position:0% makes it possible that ethers can stop capitulating<00:13:00.300> to<00:13:00.480> each<00:13:00.600> of<00:13:00.720> these<00:13:00.839> individual 00:13:01.250 --> 00:13:01.260 align:start position:0% capitulating to each of these individual 00:13:01.260 --> 00:13:03.530 align:start position:0% capitulating to each of these individual things<00:13:01.440> and<00:13:01.860> all<00:13:02.100> those<00:13:02.399> all<00:13:02.880> those<00:13:03.060> Oddities 00:13:03.530 --> 00:13:03.540 align:start position:0% things and all those all those Oddities 00:13:03.540 --> 00:13:05.449 align:start position:0% things and all those all those Oddities which<00:13:04.079> are<00:13:04.320> fine<00:13:04.500> I<00:13:04.740> mean<00:13:04.920> you<00:13:05.399> know 00:13:05.449 --> 00:13:05.459 align:start position:0% which are fine I mean you know 00:13:05.459 --> 00:13:07.250 align:start position:0% which are fine I mean you know competition<00:13:05.760> ecosystem<00:13:06.240> is<00:13:06.480> good<00:13:06.600> but<00:13:07.019> then 00:13:07.250 --> 00:13:07.260 align:start position:0% competition ecosystem is good but then 00:13:07.260 --> 00:13:09.650 align:start position:0% competition ecosystem is good but then we<00:13:07.380> can<00:13:07.500> like<00:13:07.800> push<00:13:08.639> all<00:13:09.000> those<00:13:09.180> differences 00:13:09.650 --> 00:13:09.660 align:start position:0% we can like push all those differences 00:13:09.660 --> 00:13:12.170 align:start position:0% we can like push all those differences into<00:13:10.200> the<00:13:10.680> uh<00:13:10.860> the<00:13:11.220> network<00:13:11.399> object<00:13:11.820> and<00:13:12.060> let 00:13:12.170 --> 00:13:12.180 align:start position:0% into the uh the network object and let 00:13:12.180 --> 00:13:14.170 align:start position:0% into the uh the network object and let it<00:13:12.300> handle<00:13:12.600> it 00:13:14.170 --> 00:13:14.180 align:start position:0% it handle it 00:13:14.180 --> 00:13:15.949 align:start position:0% it handle it foreign 00:13:15.949 --> 00:13:15.959 align:start position:0% foreign 00:13:15.959 --> 00:13:18.170 align:start position:0% foreign package<00:13:16.620> exports<00:13:17.100> I'm<00:13:17.339> moving<00:13:17.639> away<00:13:17.760> from<00:13:18.060> a 00:13:18.170 --> 00:13:18.180 align:start position:0% package exports I'm moving away from a 00:13:18.180 --> 00:13:20.870 align:start position:0% package exports I'm moving away from a mono<00:13:18.420> repo<00:13:18.779> which<00:13:18.959> uses<00:13:19.320> a<00:13:19.980> bajillion<00:13:20.519> sub 00:13:20.870 --> 00:13:20.880 align:start position:0% mono repo which uses a bajillion sub 00:13:20.880 --> 00:13:23.030 align:start position:0% mono repo which uses a bajillion sub packages<00:13:21.300> all<00:13:21.720> by<00:13:21.959> ethers<00:13:22.560> because<00:13:22.740> it<00:13:22.920> used 00:13:23.030 --> 00:13:23.040 align:start position:0% packages all by ethers because it used 00:13:23.040 --> 00:13:24.829 align:start position:0% packages all by ethers because it used to<00:13:23.160> be<00:13:23.160> like<00:13:23.279> at<00:13:23.339> ether's<00:13:23.820> project<00:13:23.880> ABI 00:13:24.829 --> 00:13:24.839 align:start position:0% to be like at ether's project ABI 00:13:24.839 --> 00:13:26.509 align:start position:0% to be like at ether's project ABI Addie's<00:13:25.320> project<00:13:25.440> providers<00:13:26.100> and<00:13:26.220> that<00:13:26.339> sort 00:13:26.509 --> 00:13:26.519 align:start position:0% Addie's project providers and that sort 00:13:26.519 --> 00:13:28.910 align:start position:0% Addie's project providers and that sort of<00:13:26.639> thing<00:13:27.200> package<00:13:28.200> exports<00:13:28.620> are<00:13:28.800> awesome 00:13:28.910 --> 00:13:28.920 align:start position:0% of thing package exports are awesome 00:13:28.920 --> 00:13:30.650 align:start position:0% of thing package exports are awesome they're<00:13:29.339> supported<00:13:29.700> by<00:13:29.820> all<00:13:30.000> major<00:13:30.180> bundlers 00:13:30.650 --> 00:13:30.660 align:start position:0% they're supported by all major bundlers 00:13:30.660 --> 00:13:32.690 align:start position:0% they're supported by all major bundlers now<00:13:30.959> and<00:13:31.920> it<00:13:32.040> means<00:13:32.279> that<00:13:32.339> there's<00:13:32.519> no 00:13:32.690 --> 00:13:32.700 align:start position:0% now and it means that there's no 00:13:32.700 --> 00:13:34.550 align:start position:0% now and it means that there's no complicated<00:13:33.180> weird<00:13:33.480> process<00:13:33.899> going<00:13:34.200> on<00:13:34.320> for 00:13:34.550 --> 00:13:34.560 align:start position:0% complicated weird process going on for 00:13:34.560 --> 00:13:36.710 align:start position:0% complicated weird process going on for ether's<00:13:35.040> build<00:13:35.160> for<00:13:36.000> those<00:13:36.180> who've<00:13:36.540> used 00:13:36.710 --> 00:13:36.720 align:start position:0% ether's build for those who've used 00:13:36.720 --> 00:13:39.470 align:start position:0% ether's build for those who've used ether's<00:13:37.800> or<00:13:38.279> tried<00:13:38.519> modifying<00:13:38.940> ethers<00:13:39.300> at<00:13:39.420> all 00:13:39.470 --> 00:13:39.480 align:start position:0% ether's or tried modifying ethers at all 00:13:39.480 --> 00:13:40.970 align:start position:0% ether's or tried modifying ethers at all the<00:13:39.600> build<00:13:39.779> process<00:13:40.139> is<00:13:40.320> absolutely<00:13:40.620> insane 00:13:40.970 --> 00:13:40.980 align:start position:0% the build process is absolutely insane 00:13:40.980 --> 00:13:44.090 align:start position:0% the build process is absolutely insane because<00:13:41.700> I<00:13:41.940> try<00:13:42.060> to<00:13:42.180> Target<00:13:42.300> again<00:13:42.779> ES3<00:13:43.500> and 00:13:44.090 --> 00:13:44.100 align:start position:0% because I try to Target again ES3 and 00:13:44.100 --> 00:13:46.430 align:start position:0% because I try to Target again ES3 and react<00:13:44.519> and<00:13:45.060> I<00:13:45.660> try<00:13:45.779> to<00:13:45.899> build<00:13:46.019> for<00:13:46.260> everything 00:13:46.430 --> 00:13:46.440 align:start position:0% react and I try to build for everything 00:13:46.440 --> 00:13:48.889 align:start position:0% react and I try to build for everything and<00:13:46.860> as<00:13:47.040> a<00:13:47.220> result<00:13:47.339> people<00:13:48.240> who<00:13:48.480> are<00:13:48.540> using 00:13:48.889 --> 00:13:48.899 align:start position:0% and as a result people who are using 00:13:48.899 --> 00:13:51.889 align:start position:0% and as a result people who are using more<00:13:49.320> modern<00:13:49.639> utilities<00:13:50.639> like<00:13:51.240> uh<00:13:51.720> people 00:13:51.889 --> 00:13:51.899 align:start position:0% more modern utilities like uh people 00:13:51.899 --> 00:13:53.930 align:start position:0% more modern utilities like uh people complain<00:13:52.380> about<00:13:52.500> Vite<00:13:52.860> a<00:13:53.100> lot<00:13:53.220> or<00:13:53.700> if<00:13:53.880> you're 00:13:53.930 --> 00:13:53.940 align:start position:0% complain about Vite a lot or if you're 00:13:53.940 --> 00:13:56.210 align:start position:0% complain about Vite a lot or if you're trying<00:13:54.180> to<00:13:54.480> build<00:13:55.200> a<00:13:55.320> bundle<00:13:55.620> for<00:13:55.740> node<00:13:56.040> it 00:13:56.210 --> 00:13:56.220 align:start position:0% trying to build a bundle for node it 00:13:56.220 --> 00:13:58.250 align:start position:0% trying to build a bundle for node it just<00:13:56.399> fails<00:13:56.760> so<00:13:57.240> the<00:13:57.360> nice<00:13:57.480> thing<00:13:57.600> is<00:13:57.660> by<00:13:57.839> using 00:13:58.250 --> 00:13:58.260 align:start position:0% just fails so the nice thing is by using 00:13:58.260 --> 00:13:59.750 align:start position:0% just fails so the nice thing is by using package<00:13:58.560> exports<00:13:59.100> instead<00:13:59.459> of<00:13:59.519> all<00:13:59.639> this 00:13:59.750 --> 00:13:59.760 align:start position:0% package exports instead of all this 00:13:59.760 --> 00:14:02.750 align:start position:0% package exports instead of all this crazy<00:13:59.940> custom<00:14:00.240> scripts<00:14:00.980> it<00:14:01.980> just<00:14:02.160> kind<00:14:02.639> of 00:14:02.750 --> 00:14:02.760 align:start position:0% crazy custom scripts it just kind of 00:14:02.760 --> 00:14:04.370 align:start position:0% crazy custom scripts it just kind of works<00:14:03.120> with<00:14:03.360> all<00:14:03.540> these<00:14:03.720> tools<00:14:04.079> and 00:14:04.370 --> 00:14:04.380 align:start position:0% works with all these tools and 00:14:04.380 --> 00:14:06.230 align:start position:0% works with all these tools and everyone's<00:14:04.740> happier 00:14:06.230 --> 00:14:06.240 align:start position:0% everyone's happier 00:14:06.240 --> 00:14:08.269 align:start position:0% everyone's happier um I<00:14:06.420> hope<00:14:06.600> we'll<00:14:06.959> see<00:14:07.260> that<00:14:07.440> after<00:14:07.800> I<00:14:08.040> launch 00:14:08.269 --> 00:14:08.279 align:start position:0% um I hope we'll see that after I launch 00:14:08.279 --> 00:14:12.470 align:start position:0% um I hope we'll see that after I launch the<00:14:08.880> non-beta 00:14:12.470 --> 00:14:12.480 align:start position:0% 00:14:12.480 --> 00:14:14.090 align:start position:0% um 00:14:14.090 --> 00:14:14.100 align:start position:0% um 00:14:14.100 --> 00:14:15.470 align:start position:0% um there's<00:14:14.519> better<00:14:14.700> and<00:14:14.880> fewer<00:14:15.120> dependencies 00:14:15.470 --> 00:14:15.480 align:start position:0% there's better and fewer dependencies 00:14:15.480 --> 00:14:16.970 align:start position:0% there's better and fewer dependencies I'm<00:14:15.720> actually<00:14:15.839> going<00:14:16.019> to<00:14:16.019> grab<00:14:16.200> a<00:14:16.380> bit<00:14:16.740> of 00:14:16.970 --> 00:14:16.980 align:start position:0% I'm actually going to grab a bit of 00:14:16.980 --> 00:14:18.769 align:start position:0% I'm actually going to grab a bit of water 00:14:18.769 --> 00:14:18.779 align:start position:0% water 00:14:18.779 --> 00:14:21.769 align:start position:0% water um<00:14:19.380> so<00:14:19.920> yes<00:14:20.160> there's<00:14:20.639> basically<00:14:21.180> I<00:14:21.480> think<00:14:21.600> I'm 00:14:21.769 --> 00:14:21.779 align:start position:0% um so yes there's basically I think I'm 00:14:21.779 --> 00:14:23.870 align:start position:0% um so yes there's basically I think I'm at<00:14:21.959> five<00:14:22.320> dependencies<00:14:22.860> ish<00:14:23.279> right<00:14:23.399> now<00:14:23.579> but 00:14:23.870 --> 00:14:23.880 align:start position:0% at five dependencies ish right now but 00:14:23.880 --> 00:14:26.329 align:start position:0% at five dependencies ish right now but down<00:14:24.120> to<00:14:24.300> four<00:14:24.540> authors 00:14:26.329 --> 00:14:26.339 align:start position:0% down to four authors 00:14:26.339 --> 00:14:28.250 align:start position:0% down to four authors um 00:14:28.250 --> 00:14:28.260 align:start position:0% um 00:14:28.260 --> 00:14:29.509 align:start position:0% um which<00:14:28.620> is<00:14:28.740> an<00:14:28.800> important<00:14:29.040> thing<00:14:29.160> I<00:14:29.279> feel<00:14:29.399> like 00:14:29.509 --> 00:14:29.519 align:start position:0% which is an important thing I feel like 00:14:29.519 --> 00:14:31.250 align:start position:0% which is an important thing I feel like we've<00:14:29.700> all<00:14:29.820> seen<00:14:30.000> we've<00:14:30.300> all<00:14:30.420> like<00:14:30.720> recently 00:14:31.250 --> 00:14:31.260 align:start position:0% we've all seen we've all like recently 00:14:31.260 --> 00:14:33.949 align:start position:0% we've all seen we've all like recently been<00:14:31.440> pretty<00:14:31.620> worried<00:14:31.980> about<00:14:32.160> like<00:14:32.519> uh 00:14:33.949 --> 00:14:33.959 align:start position:0% been pretty worried about like uh 00:14:33.959 --> 00:14:36.590 align:start position:0% been pretty worried about like uh supply<00:14:34.320> chain<00:14:34.680> attacks<00:14:35.279> going<00:14:35.760> on<00:14:35.880> from<00:14:36.120> mpm 00:14:36.590 --> 00:14:36.600 align:start position:0% supply chain attacks going on from mpm 00:14:36.600 --> 00:14:38.870 align:start position:0% supply chain attacks going on from mpm installing<00:14:36.959> a<00:14:37.019> bajillion<00:14:37.560> things<00:14:37.800> and<00:14:38.639> so 00:14:38.870 --> 00:14:38.880 align:start position:0% installing a bajillion things and so 00:14:38.880 --> 00:14:41.090 align:start position:0% installing a bajillion things and so right<00:14:39.600> now<00:14:39.779> there's<00:14:40.019> four<00:14:40.260> well-established 00:14:41.090 --> 00:14:41.100 align:start position:0% right now there's four well-established 00:14:41.100 --> 00:14:42.470 align:start position:0% right now there's four well-established authors<00:14:41.519> that<00:14:41.820> are<00:14:41.880> responsible<00:14:42.180> for<00:14:42.240> all<00:14:42.420> the 00:14:42.470 --> 00:14:42.480 align:start position:0% authors that are responsible for all the 00:14:42.480 --> 00:14:43.730 align:start position:0% authors that are responsible for all the library<00:14:42.600> so<00:14:42.779> there's<00:14:42.959> me 00:14:43.730 --> 00:14:43.740 align:start position:0% library so there's me 00:14:43.740 --> 00:14:46.090 align:start position:0% library so there's me I<00:14:44.160> actually<00:14:44.339> myself<00:14:44.639> well<00:14:44.880> established 00:14:46.090 --> 00:14:46.100 align:start position:0% I actually myself well established 00:14:46.100 --> 00:14:48.470 align:start position:0% I actually myself well established there's<00:14:47.100> uh<00:14:47.519> Paul<00:14:47.699> Miller<00:14:47.880> who<00:14:48.180> does<00:14:48.360> an 00:14:48.470 --> 00:14:48.480 align:start position:0% there's uh Paul Miller who does an 00:14:48.480 --> 00:14:50.810 align:start position:0% there's uh Paul Miller who does an awesome<00:14:48.800> library<00:14:49.800> for<00:14:50.100> hashing<00:14:50.519> and<00:14:50.699> for 00:14:50.810 --> 00:14:50.820 align:start position:0% awesome library for hashing and for 00:14:50.820 --> 00:14:53.090 align:start position:0% awesome library for hashing and for signing<00:14:51.240> and 00:14:53.090 --> 00:14:53.100 align:start position:0% signing and 00:14:53.100 --> 00:14:55.730 align:start position:0% signing and Microsoft<00:14:53.880> writes<00:14:54.480> TS<00:14:54.779> lib<00:14:55.079> it's<00:14:55.320> a<00:14:55.500> tiny 00:14:55.730 --> 00:14:55.740 align:start position:0% Microsoft writes TS lib it's a tiny 00:14:55.740 --> 00:14:56.990 align:start position:0% Microsoft writes TS lib it's a tiny little<00:14:55.860> thing<00:14:56.040> it<00:14:56.220> just<00:14:56.399> helps<00:14:56.639> save<00:14:56.760> some 00:14:56.990 --> 00:14:57.000 align:start position:0% little thing it just helps save some 00:14:57.000 --> 00:14:59.090 align:start position:0% little thing it just helps save some space<00:14:57.240> and<00:14:58.019> websocket<00:14:58.620> there's<00:14:58.800> a<00:14:58.920> popular 00:14:59.090 --> 00:14:59.100 align:start position:0% space and websocket there's a popular 00:14:59.100 --> 00:15:02.030 align:start position:0% space and websocket there's a popular websocket<00:14:59.699> library<00:14:59.940> that<00:15:00.360> works<00:15:00.720> in<00:15:01.139> node<00:15:01.740> if 00:15:02.030 --> 00:15:02.040 align:start position:0% websocket library that works in node if 00:15:02.040 --> 00:15:03.290 align:start position:0% websocket library that works in node if you're<00:15:02.160> using<00:15:02.339> a<00:15:02.459> browser<00:15:02.760> you<00:15:02.880> don't<00:15:03.000> have<00:15:03.240> to 00:15:03.290 --> 00:15:03.300 align:start position:0% you're using a browser you don't have to 00:15:03.300 --> 00:15:04.550 align:start position:0% you're using a browser you don't have to use<00:15:03.420> that<00:15:03.540> one<00:15:03.660> so<00:15:03.779> now<00:15:03.959> you're<00:15:04.079> down<00:15:04.260> to<00:15:04.380> like 00:15:04.550 --> 00:15:04.560 align:start position:0% use that one so now you're down to like 00:15:04.560 --> 00:15:07.790 align:start position:0% use that one so now you're down to like three<00:15:04.740> authors<00:15:05.160> and<00:15:05.459> and<00:15:05.639> four<00:15:05.820> dependencies 00:15:07.790 --> 00:15:07.800 align:start position:0% three authors and and four dependencies 00:15:07.800 --> 00:15:08.689 align:start position:0% three authors and and four dependencies um 00:15:08.689 --> 00:15:08.699 align:start position:0% um 00:15:08.699 --> 00:15:10.129 align:start position:0% um and<00:15:09.060> it<00:15:09.120> saves<00:15:09.420> me<00:15:09.480> a<00:15:09.540> lot<00:15:09.600> of<00:15:09.720> work<00:15:09.839> as<00:15:09.959> well 00:15:10.129 --> 00:15:10.139 align:start position:0% and it saves me a lot of work as well 00:15:10.139 --> 00:15:11.329 align:start position:0% and it saves me a lot of work as well because 00:15:11.329 --> 00:15:11.339 align:start position:0% because 00:15:11.339 --> 00:15:12.769 align:start position:0% because there's<00:15:11.820> so<00:15:12.000> many<00:15:12.120> times<00:15:12.300> where<00:15:12.540> like 00:15:12.769 --> 00:15:12.779 align:start position:0% there's so many times where like 00:15:12.779 --> 00:15:15.470 align:start position:0% there's so many times where like elliptic<00:15:13.740> has<00:15:13.980> some<00:15:14.279> bug<00:15:14.459> in<00:15:14.699> it<00:15:14.880> and<00:15:15.360> I'm 00:15:15.470 --> 00:15:15.480 align:start position:0% elliptic has some bug in it and I'm 00:15:15.480 --> 00:15:17.090 align:start position:0% elliptic has some bug in it and I'm trying<00:15:15.660> to<00:15:15.779> track<00:15:15.959> down<00:15:16.139> on<00:15:16.320> him<00:15:16.560> to<00:15:16.860> get<00:15:16.980> him 00:15:17.090 --> 00:15:17.100 align:start position:0% trying to track down on him to get him 00:15:17.100 --> 00:15:19.970 align:start position:0% trying to track down on him to get him to<00:15:17.339> update<00:15:17.699> things<00:15:18.060> and<00:15:18.600> once<00:15:19.260> that's<00:15:19.440> fixed<00:15:19.800> I 00:15:19.970 --> 00:15:19.980 align:start position:0% to update things and once that's fixed I 00:15:19.980 --> 00:15:21.590 align:start position:0% to update things and once that's fixed I now<00:15:20.160> have<00:15:20.279> to<00:15:20.399> update<00:15:20.639> everything<00:15:20.880> and<00:15:21.300> put<00:15:21.480> a 00:15:21.590 --> 00:15:21.600 align:start position:0% now have to update everything and put a 00:15:21.600 --> 00:15:23.509 align:start position:0% now have to update everything and put a new<00:15:21.720> build<00:15:21.899> out<00:15:22.079> so<00:15:22.380> the<00:15:22.620> fewer<00:15:22.920> dependencies 00:15:23.509 --> 00:15:23.519 align:start position:0% new build out so the fewer dependencies 00:15:23.519 --> 00:15:27.110 align:start position:0% new build out so the fewer dependencies the<00:15:24.060> the<00:15:24.300> happier<00:15:24.720> my<00:15:24.899> life<00:15:25.019> is<00:15:25.139> as<00:15:25.320> well 00:15:27.110 --> 00:15:27.120 align:start position:0% the the happier my life is as well 00:15:27.120 --> 00:15:30.350 align:start position:0% the the happier my life is as well and<00:15:27.959> that's<00:15:28.320> all<00:15:28.500> I've<00:15:28.680> got<00:15:28.800> I've<00:15:29.399> got<00:15:29.760> nine 00:15:30.350 --> 00:15:30.360 align:start position:0% and that's all I've got I've got nine 00:15:30.360 --> 00:15:31.790 align:start position:0% and that's all I've got I've got nine minutes<00:15:30.600> for<00:15:30.899> questions<00:15:31.079> if<00:15:31.380> anybody's 00:15:31.790 --> 00:15:31.800 align:start position:0% minutes for questions if anybody's 00:15:31.800 --> 00:15:33.829 align:start position:0% minutes for questions if anybody's questions<00:15:31.980> oh<00:15:32.339> and 00:15:33.829 --> 00:15:33.839 align:start position:0% questions oh and 00:15:33.839 --> 00:15:35.629 align:start position:0% questions oh and come<00:15:34.260> find<00:15:34.500> me<00:15:34.680> afterwards<00:15:35.040> I've<00:15:35.279> got<00:15:35.399> these 00:15:35.629 --> 00:15:35.639 align:start position:0% come find me afterwards I've got these 00:15:35.639 --> 00:15:38.449 align:start position:0% come find me afterwards I've got these little<00:15:35.760> like<00:15:36.000> ahiva<00:15:36.720> I<00:15:37.199> brought<00:15:37.320> one<00:15:37.500> up<00:15:38.040> for 00:15:38.449 --> 00:15:38.459 align:start position:0% little like ahiva I brought one up for 00:15:38.459 --> 00:15:41.810 align:start position:0% little like ahiva I brought one up for anyone<00:15:38.699> who's<00:15:38.880> like<00:15:39.320> curious<00:15:40.320> about<00:15:40.980> V6<00:15:41.519> I've 00:15:41.810 --> 00:15:41.820 align:start position:0% anyone who's like curious about V6 I've 00:15:41.820 --> 00:15:43.430 align:start position:0% anyone who's like curious about V6 I've actually<00:15:42.000> started<00:15:42.480> to<00:15:42.600> write<00:15:42.839> oh<00:15:43.079> I<00:15:43.260> should 00:15:43.430 --> 00:15:43.440 align:start position:0% actually started to write oh I should 00:15:43.440 --> 00:15:45.710 align:start position:0% actually started to write oh I should explain<00:15:43.500> that<00:15:43.740> so<00:15:43.920> yes<00:15:44.100> basically<00:15:44.639> I'm<00:15:45.540> trying 00:15:45.710 --> 00:15:45.720 align:start position:0% explain that so yes basically I'm trying 00:15:45.720 --> 00:15:47.389 align:start position:0% explain that so yes basically I'm trying to<00:15:45.839> write<00:15:45.959> a<00:15:46.139> bunch<00:15:46.260> of<00:15:46.380> little<00:15:46.500> apps<00:15:46.920> right 00:15:47.389 --> 00:15:47.399 align:start position:0% to write a bunch of little apps right 00:15:47.399 --> 00:15:50.569 align:start position:0% to write a bunch of little apps right now<00:15:47.639> against<00:15:48.540> V6<00:15:49.139> to<00:15:49.380> help<00:15:49.500> test<00:15:49.680> it<00:15:50.399> um<00:15:50.459> so 00:15:50.569 --> 00:15:50.579 align:start position:0% now against V6 to help test it um so 00:15:50.579 --> 00:15:51.829 align:start position:0% now against V6 to help test it um so this<00:15:50.760> one's<00:15:51.060> actually<00:15:51.180> found<00:15:51.420> quite<00:15:51.660> a<00:15:51.779> few 00:15:51.829 --> 00:15:51.839 align:start position:0% this one's actually found quite a few 00:15:51.839 --> 00:15:53.150 align:start position:0% this one's actually found quite a few bugs<00:15:52.199> already 00:15:53.150 --> 00:15:53.160 align:start position:0% bugs already 00:15:53.160 --> 00:15:54.650 align:start position:0% bugs already um it's<00:15:53.279> an<00:15:53.399> nft<00:15:53.639> it's<00:15:54.060> got<00:15:54.180> a<00:15:54.300> little<00:15:54.360> scratch 00:15:54.650 --> 00:15:54.660 align:start position:0% um it's an nft it's got a little scratch 00:15:54.660 --> 00:15:57.350 align:start position:0% um it's an nft it's got a little scratch off<00:15:54.839> hologram<00:15:55.320> when<00:15:55.620> you<00:15:55.740> scratch<00:15:55.980> it<00:15:56.100> off<00:15:56.360> you 00:15:57.350 --> 00:15:57.360 align:start position:0% off hologram when you scratch it off you 00:15:57.360 --> 00:16:00.170 align:start position:0% off hologram when you scratch it off you can<00:15:57.480> scan<00:15:57.779> it<00:15:57.899> and<00:15:58.019> claim<00:15:58.380> it<00:15:58.500> and<00:15:59.100> you<00:15:59.339> can<00:15:59.459> you 00:16:00.170 --> 00:16:00.180 align:start position:0% can scan it and claim it and you can you 00:16:00.180 --> 00:16:01.910 align:start position:0% can scan it and claim it and you can you know<00:16:00.240> fold<00:16:00.540> your<00:16:00.720> little<00:16:00.899> papercraft<00:16:01.320> robot 00:16:01.910 --> 00:16:01.920 align:start position:0% know fold your little papercraft robot 00:16:01.920 --> 00:16:04.310 align:start position:0% know fold your little papercraft robot up<00:16:02.100> and<00:16:02.459> like<00:16:02.699> do<00:16:03.000> this<00:16:03.180> and<00:16:03.959> then<00:16:04.079> take 00:16:04.310 --> 00:16:04.320 align:start position:0% up and like do this and then take 00:16:04.320 --> 00:16:05.990 align:start position:0% up and like do this and then take pictures<00:16:04.560> of<00:16:04.800> him<00:16:04.980> and<00:16:05.399> post<00:16:05.519> it<00:16:05.699> into<00:16:05.760> the 00:16:05.990 --> 00:16:06.000 align:start position:0% pictures of him and post it into the 00:16:06.000 --> 00:16:09.710 align:start position:0% pictures of him and post it into the contract<00:16:06.500> and<00:16:07.500> you<00:16:08.220> can<00:16:08.339> like<00:16:08.880> I'm<00:16:09.420> thinking 00:16:09.710 --> 00:16:09.720 align:start position:0% contract and you can like I'm thinking 00:16:09.720 --> 00:16:11.090 align:start position:0% contract and you can like I'm thinking more<00:16:10.019> of<00:16:10.079> like<00:16:10.199> that<00:16:10.320> little<00:16:10.500> gnome<00:16:10.860> from 00:16:11.090 --> 00:16:11.100 align:start position:0% more of like that little gnome from 00:16:11.100 --> 00:16:12.650 align:start position:0% more of like that little gnome from Amelie<00:16:11.639> you<00:16:12.000> know<00:16:12.060> you<00:16:12.240> can<00:16:12.300> take<00:16:12.420> it<00:16:12.540> around 00:16:12.650 --> 00:16:12.660 align:start position:0% Amelie you know you can take it around 00:16:12.660 --> 00:16:13.970 align:start position:0% Amelie you know you can take it around and<00:16:12.899> show<00:16:13.079> you<00:16:13.139> those<00:16:13.380> things<00:16:13.560> visited 00:16:13.970 --> 00:16:13.980 align:start position:0% and show you those things visited 00:16:13.980 --> 00:16:15.590 align:start position:0% and show you those things visited different<00:16:14.160> places 00:16:15.590 --> 00:16:15.600 align:start position:0% different places 00:16:15.600 --> 00:16:17.090 align:start position:0% different places um right<00:16:16.320> now<00:16:16.440> it's<00:16:16.500> only<00:16:16.680> deployed<00:16:17.040> to 00:16:17.090 --> 00:16:17.100 align:start position:0% um right now it's only deployed to 00:16:17.100 --> 00:16:18.170 align:start position:0% um right now it's only deployed to Gourley 00:16:18.170 --> 00:16:18.180 align:start position:0% Gourley 00:16:18.180 --> 00:16:19.730 align:start position:0% Gourley for<00:16:18.660> anyone<00:16:18.899> who<00:16:19.019> actually<00:16:19.199> like<00:16:19.440> goes 00:16:19.730 --> 00:16:19.740 align:start position:0% for anyone who actually like goes 00:16:19.740 --> 00:16:20.810 align:start position:0% for anyone who actually like goes through<00:16:19.800> the<00:16:19.920> effort<00:16:20.100> of<00:16:20.220> like<00:16:20.399> submitting 00:16:20.810 --> 00:16:20.820 align:start position:0% through the effort of like submitting 00:16:20.820 --> 00:16:22.310 align:start position:0% through the effort of like submitting this<00:16:20.940> I<00:16:21.120> will<00:16:21.240> be<00:16:21.360> migrating<00:16:21.660> your<00:16:21.839> tokens<00:16:22.079> to 00:16:22.310 --> 00:16:22.320 align:start position:0% this I will be migrating your tokens to 00:16:22.320 --> 00:16:24.230 align:start position:0% this I will be migrating your tokens to mainnet<00:16:23.160> um<00:16:23.220> if<00:16:23.339> you<00:16:23.459> want<00:16:23.579> to<00:16:23.639> wait<00:16:23.760> till<00:16:23.880> the 00:16:24.230 --> 00:16:24.240 align:start position:0% mainnet um if you want to wait till the 00:16:24.240 --> 00:16:26.449 align:start position:0% mainnet um if you want to wait till the main<00:16:24.360> version<00:16:24.660> launches<00:16:25.139> the<00:16:25.620> same<00:16:25.800> QR<00:16:26.279> codes 00:16:26.449 --> 00:16:26.459 align:start position:0% main version launches the same QR codes 00:16:26.459 --> 00:16:27.769 align:start position:0% main version launches the same QR codes will<00:16:26.639> work<00:16:26.760> on<00:16:26.880> mainnet<00:16:27.180> and<00:16:27.300> you<00:16:27.480> can<00:16:27.600> claim 00:16:27.769 --> 00:16:27.779 align:start position:0% will work on mainnet and you can claim 00:16:27.779 --> 00:16:29.090 align:start position:0% will work on mainnet and you can claim it<00:16:27.839> there 00:16:29.090 --> 00:16:29.100 align:start position:0% it there 00:16:29.100 --> 00:16:30.949 align:start position:0% it there um<00:16:29.160> so<00:16:29.399> that's<00:16:29.519> just<00:16:29.699> like<00:16:29.820> a<00:16:30.060> little<00:16:30.300> demo<00:16:30.779> I'm 00:16:30.949 --> 00:16:30.959 align:start position:0% um so that's just like a little demo I'm 00:16:30.959 --> 00:16:32.689 align:start position:0% um so that's just like a little demo I'm flirting<00:16:31.320> together<00:16:31.440> to 00:16:32.689 --> 00:16:32.699 align:start position:0% flirting together to 00:16:32.699 --> 00:16:36.170 align:start position:0% flirting together to to<00:16:32.880> test<00:16:33.240> and<00:16:33.480> make<00:16:33.600> sure<00:16:33.779> V6<00:16:34.199> works<00:16:34.740> and<00:16:35.279> it's 00:16:36.170 --> 00:16:36.180 align:start position:0% to test and make sure V6 works and it's 00:16:36.180 --> 00:16:37.430 align:start position:0% to test and make sure V6 works and it's definitely<00:16:36.420> not<00:16:36.540> ready<00:16:36.720> for<00:16:36.899> production<00:16:37.199> as 00:16:37.430 --> 00:16:37.440 align:start position:0% definitely not ready for production as 00:16:37.440 --> 00:16:39.590 align:start position:0% definitely not ready for production as it<00:16:37.560> stands<00:16:37.860> right<00:16:37.980> now<00:16:38.160> but<00:16:38.940> it's<00:16:39.420> getting 00:16:39.590 --> 00:16:39.600 align:start position:0% it stands right now but it's getting 00:16:39.600 --> 00:16:40.910 align:start position:0% it stands right now but it's getting closer<00:16:39.959> and<00:16:40.139> I'll<00:16:40.320> probably<00:16:40.440> be<00:16:40.560> doing<00:16:40.680> a<00:16:40.860> few 00:16:40.910 --> 00:16:40.920 align:start position:0% closer and I'll probably be doing a few 00:16:40.920 --> 00:16:42.170 align:start position:0% closer and I'll probably be doing a few more<00:16:41.040> little<00:16:41.220> weird<00:16:41.519> projects<00:16:41.940> like<00:16:42.060> this 00:16:42.170 --> 00:16:42.180 align:start position:0% more little weird projects like this 00:16:42.180 --> 00:16:44.389 align:start position:0% more little weird projects like this just<00:16:42.480> to<00:16:42.660> kind<00:16:42.839> of<00:16:42.959> like 00:16:44.389 --> 00:16:44.399 align:start position:0% just to kind of like 00:16:44.399 --> 00:16:47.269 align:start position:0% just to kind of like find<00:16:45.060> those<00:16:45.300> little<00:16:45.420> foibles<00:16:45.959> and<00:16:46.259> and<00:16:46.980> things 00:16:47.269 --> 00:16:47.279 align:start position:0% find those little foibles and and things 00:16:47.279 --> 00:16:49.370 align:start position:0% find those little foibles and and things that<00:16:47.579> happened<00:16:47.699> during<00:16:48.120> the<00:16:48.360> last<00:16:48.600> two<00:16:49.139> years 00:16:49.370 --> 00:16:49.380 align:start position:0% that happened during the last two years 00:16:49.380 --> 00:16:51.170 align:start position:0% that happened during the last two years worth<00:16:49.680> of<00:16:49.920> rewriting<00:16:50.399> and<00:16:50.579> rewriting<00:16:51.060> and 00:16:51.170 --> 00:16:51.180 align:start position:0% worth of rewriting and rewriting and 00:16:51.180 --> 00:16:54.170 align:start position:0% worth of rewriting and rewriting and rewriting<00:16:52.139> so<00:16:52.620> I've<00:16:52.800> got<00:16:52.980> 7<00:16:53.339> Minutes<00:16:53.639> 49 00:16:54.170 --> 00:16:54.180 align:start position:0% rewriting so I've got 7 Minutes 49 00:16:54.180 --> 00:16:55.670 align:start position:0% rewriting so I've got 7 Minutes 49 seconds<00:16:54.480> left<00:16:54.839> for<00:16:55.139> if<00:16:55.259> there's<00:16:55.440> any 00:16:55.670 --> 00:16:55.680 align:start position:0% seconds left for if there's any 00:16:55.680 --> 00:16:58.129 align:start position:0% seconds left for if there's any questions<00:16:55.920> out<00:16:56.399> there<00:16:57.180> I<00:16:57.779> don't<00:16:57.839> know<00:16:57.959> where 00:16:58.129 --> 00:16:58.139 align:start position:0% questions out there I don't know where 00:16:58.139 --> 00:17:00.769 align:start position:0% questions out there I don't know where we'd<00:16:58.380> be<00:16:58.500> without<00:16:58.680> you<00:16:59.040> like 00:17:00.769 --> 00:17:00.779 align:start position:0% we'd be without you like 00:17:00.779 --> 00:17:04.010 align:start position:0% we'd be without you like open<00:17:01.680> source<00:17:02.160> hero 00:17:04.010 --> 00:17:04.020 align:start position:0% open source hero 00:17:04.020 --> 00:17:05.569 align:start position:0% open source hero thank<00:17:04.500> you 00:17:05.569 --> 00:17:05.579 align:start position:0% thank you 00:17:05.579 --> 00:17:08.510 align:start position:0% thank you at<00:17:06.240> this<00:17:06.360> point<00:17:06.660> in<00:17:07.319> the<00:17:07.679> state<00:17:07.980> of<00:17:08.100> ethereum 00:17:08.510 --> 00:17:08.520 align:start position:0% at this point in the state of ethereum 00:17:08.520 --> 00:17:10.549 align:start position:0% at this point in the state of ethereum at<00:17:08.939> this<00:17:09.059> point<00:17:09.240> in<00:17:09.419> the<00:17:09.600> state<00:17:09.720> of<00:17:09.959> ethers 00:17:10.549 --> 00:17:10.559 align:start position:0% at this point in the state of ethers 00:17:10.559 --> 00:17:13.069 align:start position:0% at this point in the state of ethers what<00:17:10.980> kind<00:17:11.220> of<00:17:11.339> support<00:17:11.520> are<00:17:12.059> you<00:17:12.240> getting<00:17:12.540> in 00:17:13.069 --> 00:17:13.079 align:start position:0% what kind of support are you getting in 00:17:13.079 --> 00:17:16.130 align:start position:0% what kind of support are you getting in terms<00:17:13.319> of<00:17:13.500> like<00:17:14.059> uh<00:17:15.059> audit<00:17:15.540> help<00:17:15.720> especially 00:17:16.130 --> 00:17:16.140 align:start position:0% terms of like uh audit help especially 00:17:16.140 --> 00:17:17.689 align:start position:0% terms of like uh audit help especially as<00:17:16.260> we<00:17:16.380> see<00:17:16.500> more<00:17:16.679> like<00:17:16.860> front<00:17:17.100> end<00:17:17.220> attacks 00:17:17.689 --> 00:17:17.699 align:start position:0% as we see more like front end attacks 00:17:17.699 --> 00:17:18.770 align:start position:0% as we see more like front end attacks and<00:17:17.819> things<00:17:17.939> like<00:17:18.059> that<00:17:18.179> right<00:17:18.419> where<00:17:18.600> it's 00:17:18.770 --> 00:17:18.780 align:start position:0% and things like that right where it's 00:17:18.780 --> 00:17:20.689 align:start position:0% and things like that right where it's like<00:17:19.020> you<00:17:19.439> know<00:17:19.500> smart<00:17:19.799> contract<00:17:20.100> auditing<00:17:20.520> is 00:17:20.689 --> 00:17:20.699 align:start position:0% like you know smart contract auditing is 00:17:20.699 --> 00:17:22.370 align:start position:0% like you know smart contract auditing is important<00:17:21.000> but<00:17:21.299> the<00:17:21.600> interaction<00:17:21.900> layer<00:17:22.260> is 00:17:22.370 --> 00:17:22.380 align:start position:0% important but the interaction layer is 00:17:22.380 --> 00:17:24.710 align:start position:0% important but the interaction layer is equally<00:17:22.620> as<00:17:22.860> important<00:17:23.480> especially<00:17:24.480> now<00:17:24.540> as 00:17:24.710 --> 00:17:24.720 align:start position:0% equally as important especially now as 00:17:24.720 --> 00:17:26.329 align:start position:0% equally as important especially now as people<00:17:24.839> are<00:17:25.020> getting<00:17:25.079> more<00:17:25.260> clever<00:17:25.500> like<00:17:25.860> like 00:17:26.329 --> 00:17:26.339 align:start position:0% people are getting more clever like like 00:17:26.339 --> 00:17:29.510 align:start position:0% people are getting more clever like like you<00:17:26.939> know<00:17:27.059> not<00:17:27.900> to<00:17:28.260> not<00:17:28.740> to<00:17:28.860> throw<00:17:29.040> shade<00:17:29.400> but 00:17:29.510 --> 00:17:29.520 align:start position:0% you know not to not to throw shade but 00:17:29.520 --> 00:17:31.930 align:start position:0% you know not to not to throw shade but you<00:17:29.700> know<00:17:29.760> like<00:17:29.940> when<00:17:30.120> I<00:17:30.360> saw<00:17:30.660> uh<00:17:31.320> you<00:17:31.500> know 00:17:31.930 --> 00:17:31.940 align:start position:0% you know like when I saw uh you know 00:17:31.940 --> 00:17:35.810 align:start position:0% you know like when I saw uh you know string<00:17:32.940> normalization<00:17:33.540> for<00:17:34.020> for<00:17:34.340> ABI<00:17:35.340> it 00:17:35.810 --> 00:17:35.820 align:start position:0% string normalization for for ABI it 00:17:35.820 --> 00:17:37.549 align:start position:0% string normalization for for ABI it calls<00:17:36.179> you<00:17:36.480> know<00:17:36.600> I<00:17:36.720> instantly<00:17:37.200> thought<00:17:37.380> like 00:17:37.549 --> 00:17:37.559 align:start position:0% calls you know I instantly thought like 00:17:37.559 --> 00:17:39.350 align:start position:0% calls you know I instantly thought like just<00:17:37.799> made<00:17:37.980> me<00:17:38.160> like<00:17:38.400> uncomfortable<00:17:38.940> in<00:17:39.240> my 00:17:39.350 --> 00:17:39.360 align:start position:0% just made me like uncomfortable in my 00:17:39.360 --> 00:17:40.730 align:start position:0% just made me like uncomfortable in my gut<00:17:39.600> of<00:17:39.840> like<00:17:40.020> different<00:17:40.200> things<00:17:40.440> that<00:17:40.559> could 00:17:40.730 --> 00:17:40.740 align:start position:0% gut of like different things that could 00:17:40.740 --> 00:17:43.490 align:start position:0% gut of like different things that could happen<00:17:40.919> so<00:17:41.220> just<00:17:41.520> curious<00:17:42.419> like<00:17:43.020> um<00:17:43.140> like 00:17:43.490 --> 00:17:43.500 align:start position:0% happen so just curious like um like 00:17:43.500 --> 00:17:44.930 align:start position:0% happen so just curious like um like who's<00:17:43.679> helping<00:17:43.980> you<00:17:44.100> audit<00:17:44.460> who's<00:17:44.640> helping 00:17:44.930 --> 00:17:44.940 align:start position:0% who's helping you audit who's helping 00:17:44.940 --> 00:17:46.669 align:start position:0% who's helping you audit who's helping you<00:17:45.059> kind<00:17:45.240> of<00:17:45.360> like<00:17:45.600> comb<00:17:46.260> through<00:17:46.320> this<00:17:46.440> code 00:17:46.669 --> 00:17:46.679 align:start position:0% you kind of like comb through this code 00:17:46.679 --> 00:17:48.590 align:start position:0% you kind of like comb through this code and<00:17:46.860> go<00:17:47.039> through<00:17:47.280> uh<00:17:47.700> different<00:17:47.940> edge<00:17:48.240> cases 00:17:48.590 --> 00:17:48.600 align:start position:0% and go through uh different edge cases 00:17:48.600 --> 00:17:51.169 align:start position:0% and go through uh different edge cases and<00:17:48.780> things<00:17:48.960> like<00:17:49.140> that<00:17:49.260> right<00:17:49.980> so<00:17:50.700> basically 00:17:51.169 --> 00:17:51.179 align:start position:0% and things like that right so basically 00:17:51.179 --> 00:17:53.570 align:start position:0% and things like that right so basically the<00:17:51.600> auditing<00:17:52.080> is<00:17:52.200> all<00:17:52.380> done<00:17:52.620> by<00:17:52.919> me<00:17:53.160> which<00:17:53.460> is 00:17:53.570 --> 00:17:53.580 align:start position:0% the auditing is all done by me which is 00:17:53.580 --> 00:17:54.890 align:start position:0% the auditing is all done by me which is terrible<00:17:53.940> right<00:17:54.179> now<00:17:54.299> one<00:17:54.600> of<00:17:54.780> the<00:17:54.840> cool 00:17:54.890 --> 00:17:54.900 align:start position:0% terrible right now one of the cool 00:17:54.900 --> 00:17:57.049 align:start position:0% terrible right now one of the cool things<00:17:55.080> though<00:17:55.380> is<00:17:55.679> between<00:17:56.160> I've<00:17:56.520> got<00:17:56.700> like 00:17:57.049 --> 00:17:57.059 align:start position:0% things though is between I've got like 00:17:57.059 --> 00:18:00.470 align:start position:0% things though is between I've got like oh<00:17:57.539> sorry<00:17:57.840> the<00:17:58.080> EF<00:17:58.500> helps<00:17:58.919> sponsor<00:17:59.520> me 00:18:00.470 --> 00:18:00.480 align:start position:0% oh sorry the EF helps sponsor me 00:18:00.480 --> 00:18:03.409 align:start position:0% oh sorry the EF helps sponsor me um<00:18:00.539> I<00:18:00.720> get<00:18:00.840> GitHub<00:18:01.260> grants<00:18:01.679> get<00:18:02.640> coin<00:18:02.940> get<00:18:03.120> coin 00:18:03.409 --> 00:18:03.419 align:start position:0% um I get GitHub grants get coin get coin 00:18:03.419 --> 00:18:05.330 align:start position:0% um I get GitHub grants get coin get coin grants<00:18:03.720> a<00:18:04.559> few<00:18:04.620> sponsors<00:18:04.919> and<00:18:05.100> so<00:18:05.160> now<00:18:05.280> I'm 00:18:05.330 --> 00:18:05.340 align:start position:0% grants a few sponsors and so now I'm 00:18:05.340 --> 00:18:07.370 align:start position:0% grants a few sponsors and so now I'm starting<00:18:05.520> developed<00:18:06.240> an<00:18:06.360> endowment<00:18:06.780> so<00:18:07.020> I<00:18:07.200> am 00:18:07.370 --> 00:18:07.380 align:start position:0% starting developed an endowment so I am 00:18:07.380 --> 00:18:08.810 align:start position:0% starting developed an endowment so I am hoping<00:18:07.620> to<00:18:07.679> be<00:18:07.799> able<00:18:07.860> to<00:18:07.980> get<00:18:08.039> like<00:18:08.220> a<00:18:08.460> proper 00:18:08.810 --> 00:18:08.820 align:start position:0% hoping to be able to get like a proper 00:18:08.820 --> 00:18:12.230 align:start position:0% hoping to be able to get like a proper audit<00:18:09.660> at<00:18:09.840> some<00:18:09.960> point<00:18:10.340> there<00:18:11.340> was<00:18:11.520> one<00:18:12.059> team 00:18:12.230 --> 00:18:12.240 align:start position:0% audit at some point there was one team 00:18:12.240 --> 00:18:13.789 align:start position:0% audit at some point there was one team at<00:18:12.539> one<00:18:12.780> point<00:18:12.840> that<00:18:13.020> was<00:18:13.140> going<00:18:13.320> to<00:18:13.500> formally 00:18:13.789 --> 00:18:13.799 align:start position:0% at one point that was going to formally 00:18:13.799 --> 00:18:16.070 align:start position:0% at one point that was going to formally verify<00:18:14.220> a<00:18:14.400> bunch<00:18:14.580> of<00:18:14.700> things 00:18:16.070 --> 00:18:16.080 align:start position:0% verify a bunch of things 00:18:16.080 --> 00:18:18.409 align:start position:0% verify a bunch of things um<00:18:16.140> I<00:18:16.980> I've<00:18:17.340> heard<00:18:17.580> from<00:18:17.700> them<00:18:17.820> in<00:18:18.000> a<00:18:18.120> while<00:18:18.179> so 00:18:18.409 --> 00:18:18.419 align:start position:0% um I I've heard from them in a while so 00:18:18.419 --> 00:18:19.850 align:start position:0% um I I've heard from them in a while so I<00:18:18.480> don't<00:18:18.600> know<00:18:18.720> if<00:18:18.780> that's<00:18:18.900> still<00:18:19.140> a<00:18:19.260> thing<00:18:19.440> but 00:18:19.850 --> 00:18:19.860 align:start position:0% I don't know if that's still a thing but 00:18:19.860 --> 00:18:24.310 align:start position:0% I don't know if that's still a thing but uh<00:18:20.700> I<00:18:21.000> think<00:18:21.299> foreign 00:18:24.310 --> 00:18:24.320 align:start position:0% 00:18:24.320 --> 00:18:26.210 align:start position:0% verification<00:18:25.320> like<00:18:25.559> it<00:18:25.679> helps<00:18:25.919> in<00:18:26.039> some 00:18:26.210 --> 00:18:26.220 align:start position:0% verification like it helps in some 00:18:26.220 --> 00:18:28.490 align:start position:0% verification like it helps in some regards<00:18:26.640> but<00:18:26.820> it's<00:18:26.880> not<00:18:27.000> a<00:18:27.179> Magic<00:18:27.240> Bullet<00:18:27.720> I 00:18:28.490 --> 00:18:28.500 align:start position:0% regards but it's not a Magic Bullet I 00:18:28.500 --> 00:18:30.650 align:start position:0% regards but it's not a Magic Bullet I think<00:18:28.559> absolutely<00:18:28.980> like<00:18:29.280> proper<00:18:29.820> auditing 00:18:30.650 --> 00:18:30.660 align:start position:0% think absolutely like proper auditing 00:18:30.660 --> 00:18:32.330 align:start position:0% think absolutely like proper auditing would<00:18:30.840> work<00:18:31.020> and<00:18:31.380> I'm<00:18:31.500> also<00:18:31.740> a<00:18:31.860> big<00:18:31.919> that's<00:18:32.160> why 00:18:32.330 --> 00:18:32.340 align:start position:0% would work and I'm also a big that's why 00:18:32.340 --> 00:18:34.310 align:start position:0% would work and I'm also a big that's why I'm<00:18:32.520> a<00:18:32.640> big<00:18:32.760> fan<00:18:32.880> of<00:18:33.000> tests<00:18:33.360> I<00:18:33.720> don't<00:18:33.900> want 00:18:34.310 --> 00:18:34.320 align:start position:0% I'm a big fan of tests I don't want 00:18:34.320 --> 00:18:36.710 align:start position:0% I'm a big fan of tests I don't want issues<00:18:35.160> to<00:18:35.400> happen 00:18:36.710 --> 00:18:36.720 align:start position:0% issues to happen 00:18:36.720 --> 00:18:38.750 align:start position:0% issues to happen um<00:18:36.780> so<00:18:37.260> I<00:18:37.440> feel<00:18:37.559> like<00:18:37.679> test<00:18:37.980> I<00:18:38.280> mean<00:18:38.400> tests<00:18:38.700> can 00:18:38.750 --> 00:18:38.760 align:start position:0% um so I feel like test I mean tests can 00:18:38.760 --> 00:18:40.190 align:start position:0% um so I feel like test I mean tests can only<00:18:38.880> find<00:18:39.059> the<00:18:39.299> presence<00:18:39.539> of<00:18:39.660> bugs<00:18:39.960> not<00:18:40.080> the 00:18:40.190 --> 00:18:40.200 align:start position:0% only find the presence of bugs not the 00:18:40.200 --> 00:18:41.630 align:start position:0% only find the presence of bugs not the absence<00:18:40.440> of<00:18:40.559> bugs 00:18:41.630 --> 00:18:41.640 align:start position:0% absence of bugs 00:18:41.640 --> 00:18:42.409 align:start position:0% absence of bugs um 00:18:42.409 --> 00:18:42.419 align:start position:0% um 00:18:42.419 --> 00:18:45.409 align:start position:0% um so<00:18:43.620> I<00:18:44.160> mean<00:18:44.280> it's<00:18:44.460> a<00:18:44.640> great<00:18:44.760> question<00:18:44.940> talk<00:18:45.240> to 00:18:45.409 --> 00:18:45.419 align:start position:0% so I mean it's a great question talk to 00:18:45.419 --> 00:18:46.430 align:start position:0% so I mean it's a great question talk to me<00:18:45.480> afterwards<00:18:45.720> if<00:18:45.840> you've<00:18:46.020> got<00:18:46.080> some<00:18:46.260> ideas 00:18:46.430 --> 00:18:46.440 align:start position:0% me afterwards if you've got some ideas 00:18:46.440 --> 00:18:49.190 align:start position:0% me afterwards if you've got some ideas uh<00:18:47.280> I'm<00:18:47.520> starting<00:18:47.760> to<00:18:48.000> get<00:18:48.179> some<00:18:48.480> money<00:18:48.780> off<00:18:49.080> to 00:18:49.190 --> 00:18:49.200 align:start position:0% uh I'm starting to get some money off to 00:18:49.200 --> 00:18:50.270 align:start position:0% uh I'm starting to get some money off to the<00:18:49.320> side<00:18:49.380> now<00:18:49.620> that<00:18:49.799> I<00:18:49.919> can<00:18:49.980> actually<00:18:50.100> start 00:18:50.270 --> 00:18:50.280 align:start position:0% the side now that I can actually start 00:18:50.280 --> 00:18:51.890 align:start position:0% the side now that I can actually start throwing<00:18:50.640> if<00:18:50.820> you<00:18:51.000> know<00:18:51.120> any<00:18:51.240> like<00:18:51.480> auditing 00:18:51.890 --> 00:18:51.900 align:start position:0% throwing if you know any like auditing 00:18:51.900 --> 00:18:54.289 align:start position:0% throwing if you know any like auditing firms<00:18:52.260> that<00:18:52.380> do<00:18:52.559> typescript 00:18:54.289 --> 00:18:54.299 align:start position:0% firms that do typescript 00:18:54.299 --> 00:18:55.789 align:start position:0% firms that do typescript um 00:18:55.789 --> 00:18:55.799 align:start position:0% um 00:18:55.799 --> 00:18:58.130 align:start position:0% um what<00:18:56.280> you<00:18:56.400> mean<00:18:56.640> should<00:18:57.539> definitely<00:18:57.840> pay<00:18:57.960> for 00:18:58.130 --> 00:18:58.140 align:start position:0% what you mean should definitely pay for 00:18:58.140 --> 00:19:00.289 align:start position:0% what you mean should definitely pay for auditing<00:18:58.559> those<00:18:58.980> people<00:18:59.460> are<00:18:59.640> so<00:18:59.820> skilled<00:19:00.179> and 00:19:00.289 --> 00:19:00.299 align:start position:0% auditing those people are so skilled and 00:19:00.299 --> 00:19:01.490 align:start position:0% auditing those people are so skilled and valuable 00:19:01.490 --> 00:19:01.500 align:start position:0% valuable 00:19:01.500 --> 00:19:03.350 align:start position:0% valuable oh<00:19:01.919> okay<00:19:02.039> sure<00:19:02.340> well<00:19:02.520> I<00:19:02.640> mean<00:19:02.760> you<00:19:03.000> kind<00:19:03.179> of<00:19:03.240> are 00:19:03.350 --> 00:19:03.360 align:start position:0% oh okay sure well I mean you kind of are 00:19:03.360 --> 00:19:05.210 align:start position:0% oh okay sure well I mean you kind of are I<00:19:03.600> mean<00:19:03.720> you<00:19:03.780> think<00:19:03.960> you<00:19:04.080> get<00:19:04.200> coin<00:19:04.500> uh 00:19:05.210 --> 00:19:05.220 align:start position:0% I mean you think you get coin uh 00:19:05.220 --> 00:19:07.070 align:start position:0% I mean you think you get coin uh bitcoin's<00:19:05.760> been<00:19:05.880> awesome 00:19:07.070 --> 00:19:07.080 align:start position:0% bitcoin's been awesome 00:19:07.080 --> 00:19:08.270 align:start position:0% bitcoin's been awesome so 00:19:08.270 --> 00:19:08.280 align:start position:0% so 00:19:08.280 --> 00:19:13.250 align:start position:0% so I<00:19:08.760> was<00:19:08.880> wondering<00:19:09.419> if<00:19:09.840> you<00:19:10.260> are<00:19:10.500> gonna<00:19:10.799> add 00:19:13.250 --> 00:19:13.260 align:start position:0% I was wondering if you are gonna add 00:19:13.260 --> 00:19:14.830 align:start position:0% I was wondering if you are gonna add um 00:19:14.830 --> 00:19:14.840 align:start position:0% um 00:19:14.840 --> 00:19:17.150 align:start position:0% um this<00:19:15.840> version 00:19:17.150 --> 00:19:17.160 align:start position:0% this version 00:19:17.160 --> 00:19:19.549 align:start position:0% this version uh<00:19:17.760> do<00:19:18.179> you<00:19:18.360> sorry<00:19:18.539> it's<00:19:19.020> a<00:19:19.140> little<00:19:19.320> bit<00:19:19.440> hard 00:19:19.549 --> 00:19:19.559 align:start position:0% uh do you sorry it's a little bit hard 00:19:19.559 --> 00:19:20.630 align:start position:0% uh do you sorry it's a little bit hard to<00:19:19.679> hear<00:19:19.799> with<00:19:19.919> the<00:19:19.980> echo<00:19:20.160> are<00:19:20.340> you<00:19:20.460> guys<00:19:20.520> know 00:19:20.630 --> 00:19:20.640 align:start position:0% to hear with the echo are you guys know 00:19:20.640 --> 00:19:23.830 align:start position:0% to hear with the echo are you guys know about<00:19:20.880> batch<00:19:21.240> Json<00:19:21.600> RPC<00:19:22.080> but 00:19:23.830 --> 00:19:23.840 align:start position:0% about batch Json RPC but 00:19:23.840 --> 00:19:27.350 align:start position:0% about batch Json RPC but transactions<00:19:24.840> sorry<00:19:25.440> oh<00:19:25.919> bash<00:19:26.100> transactions 00:19:27.350 --> 00:19:27.360 align:start position:0% transactions sorry oh bash transactions 00:19:27.360 --> 00:19:28.669 align:start position:0% transactions sorry oh bash transactions um<00:19:27.480> what<00:19:27.600> which<00:19:27.780> means<00:19:28.020> by<00:19:28.260> bachelor's 00:19:28.669 --> 00:19:28.679 align:start position:0% um what which means by bachelor's 00:19:28.679 --> 00:19:30.710 align:start position:0% um what which means by bachelor's actions<00:19:28.980> like<00:19:29.280> via<00:19:29.700> Smart<00:19:30.000> contract<00:19:30.360> wallets 00:19:30.710 --> 00:19:30.720 align:start position:0% actions like via Smart contract wallets 00:19:30.720 --> 00:19:34.010 align:start position:0% actions like via Smart contract wallets like<00:19:31.500> by<00:19:31.799> you<00:19:32.100> mean<00:19:32.340> through<00:19:32.820> smart<00:19:33.480> contracts 00:19:34.010 --> 00:19:34.020 align:start position:0% like by you mean through smart contracts 00:19:34.020 --> 00:19:35.270 align:start position:0% like by you mean through smart contracts or 00:19:35.270 --> 00:19:35.280 align:start position:0% or 00:19:35.280 --> 00:19:37.730 align:start position:0% or yes<00:19:35.880> yeah<00:19:36.179> yeah<00:19:36.299> I<00:19:36.660> mean<00:19:36.840> that<00:19:37.020> all<00:19:37.200> already 00:19:37.730 --> 00:19:37.740 align:start position:0% yes yeah yeah I mean that all already 00:19:37.740 --> 00:19:40.549 align:start position:0% yes yeah yeah I mean that all already Works<00:19:38.100> uh<00:19:38.460> you<00:19:38.640> just<00:19:38.820> need<00:19:38.940> the<00:19:39.059> ABI<00:19:39.480> for<00:19:39.720> it 00:19:40.549 --> 00:19:40.559 align:start position:0% Works uh you just need the ABI for it 00:19:40.559 --> 00:19:42.950 align:start position:0% Works uh you just need the ABI for it um<00:19:40.679> there's<00:19:41.100> not<00:19:41.340> currently<00:19:41.760> in<00:19:42.059> ethereum<00:19:42.600> an 00:19:42.950 --> 00:19:42.960 align:start position:0% um there's not currently in ethereum an 00:19:42.960 --> 00:19:45.590 align:start position:0% um there's not currently in ethereum an official<00:19:43.380> like<00:19:43.559> batch<00:19:43.919> standard 00:19:45.590 --> 00:19:45.600 align:start position:0% official like batch standard 00:19:45.600 --> 00:19:48.169 align:start position:0% official like batch standard um<00:19:45.720> but<00:19:46.320> you<00:19:46.440> can<00:19:46.559> do<00:19:46.679> with<00:19:46.860> smart<00:19:47.039> contracts 00:19:48.169 --> 00:19:48.179 align:start position:0% um but you can do with smart contracts 00:19:48.179 --> 00:19:49.730 align:start position:0% um but you can do with smart contracts like<00:19:48.660> smart<00:19:48.960> contract<00:19:49.200> well<00:19:49.380> it's<00:19:49.500> like<00:19:49.620> a 00:19:49.730 --> 00:19:49.740 align:start position:0% like smart contract well it's like a 00:19:49.740 --> 00:19:51.409 align:start position:0% like smart contract well it's like a gnosis<00:19:50.220> safe<00:19:50.400> for<00:19:50.580> example<00:19:50.760> allows<00:19:51.179> you<00:19:51.240> to 00:19:51.409 --> 00:19:51.419 align:start position:0% gnosis safe for example allows you to 00:19:51.419 --> 00:19:52.970 align:start position:0% gnosis safe for example allows you to send<00:19:51.600> mobile<00:19:51.840> is<00:19:52.260> that<00:19:52.440> I'm<00:19:52.559> sorry<00:19:52.679> is<00:19:52.860> that 00:19:52.970 --> 00:19:52.980 align:start position:0% send mobile is that I'm sorry is that 00:19:52.980 --> 00:19:53.810 align:start position:0% send mobile is that I'm sorry is that what<00:19:53.100> you<00:19:53.160> mean<00:19:53.280> like<00:19:53.400> being<00:19:53.520> able<00:19:53.640> to<00:19:53.700> send 00:19:53.810 --> 00:19:53.820 align:start position:0% what you mean like being able to send 00:19:53.820 --> 00:19:55.490 align:start position:0% what you mean like being able to send multiple<00:19:54.120> transactions<00:19:54.539> at<00:19:54.660> once<00:19:54.840> an<00:19:55.080> atomic 00:19:55.490 --> 00:19:55.500 align:start position:0% multiple transactions at once an atomic 00:19:55.500 --> 00:19:58.610 align:start position:0% multiple transactions at once an atomic atomically<00:19:56.160> I<00:19:56.820> have<00:19:57.179> an<00:19:57.419> application<00:19:57.960> and<00:19:58.320> I 00:19:58.610 --> 00:19:58.620 align:start position:0% atomically I have an application and I 00:19:58.620 --> 00:20:02.750 align:start position:0% atomically I have an application and I was<00:19:58.860> I<00:19:59.280> I<00:19:59.520> want<00:19:59.820> to<00:20:00.020> to<00:20:01.100> send<00:20:02.100> a<00:20:02.460> bachelor 00:20:02.750 --> 00:20:02.760 align:start position:0% was I I want to to send a bachelor 00:20:02.760 --> 00:20:06.710 align:start position:0% was I I want to to send a bachelor structures<00:20:03.360> in<00:20:04.320> my<00:20:04.559> node<00:20:04.919> application<00:20:05.720> not 00:20:06.710 --> 00:20:06.720 align:start position:0% structures in my node application not 00:20:06.720 --> 00:20:09.830 align:start position:0% structures in my node application not through<00:20:07.500> contracts<00:20:08.340> okay<00:20:08.820> after<00:20:09.120> contracts 00:20:09.830 --> 00:20:09.840 align:start position:0% through contracts okay after contracts 00:20:09.840 --> 00:20:11.150 align:start position:0% through contracts okay after contracts um<00:20:09.900> so<00:20:10.140> that<00:20:10.320> you<00:20:10.559> can't<00:20:10.679> currently<00:20:10.980> in 00:20:11.150 --> 00:20:11.160 align:start position:0% um so that you can't currently in 00:20:11.160 --> 00:20:13.310 align:start position:0% um so that you can't currently in ethereum<00:20:11.580> in<00:20:11.760> general<00:20:11.940> send<00:20:12.900> multiple 00:20:13.310 --> 00:20:13.320 align:start position:0% ethereum in general send multiple 00:20:13.320 --> 00:20:16.610 align:start position:0% ethereum in general send multiple transactions<00:20:14.120> atomically<00:20:15.120> or<00:20:15.360> at<00:20:15.539> once 00:20:16.610 --> 00:20:16.620 align:start position:0% transactions atomically or at once 00:20:16.620 --> 00:20:18.529 align:start position:0% transactions atomically or at once um<00:20:16.679> you<00:20:16.919> basically<00:20:17.220> if<00:20:17.940> you<00:20:18.120> will<00:20:18.240> have<00:20:18.419> a 00:20:18.529 --> 00:20:18.539 align:start position:0% um you basically if you will have a 00:20:18.539 --> 00:20:19.789 align:start position:0% um you basically if you will have a bunch<00:20:18.660> of<00:20:18.780> transactions<00:20:19.320> you're<00:20:19.500> trying<00:20:19.679> to 00:20:19.789 --> 00:20:19.799 align:start position:0% bunch of transactions you're trying to 00:20:19.799 --> 00:20:21.230 align:start position:0% bunch of transactions you're trying to send<00:20:19.919> serially 00:20:21.230 --> 00:20:21.240 align:start position:0% send serially 00:20:21.240 --> 00:20:22.970 align:start position:0% send serially um so<00:20:21.419> the<00:20:21.600> Nots<00:20:22.020> manager<00:20:22.380> already<00:20:22.500> does<00:20:22.799> that 00:20:22.970 --> 00:20:22.980 align:start position:0% um so the Nots manager already does that 00:20:22.980 --> 00:20:24.710 align:start position:0% um so the Nots manager already does that uh<00:20:23.400> basically<00:20:23.640> it's<00:20:23.820> a<00:20:24.000> wrapper<00:20:24.360> that<00:20:24.480> goes 00:20:24.710 --> 00:20:24.720 align:start position:0% uh basically it's a wrapper that goes 00:20:24.720 --> 00:20:27.049 align:start position:0% uh basically it's a wrapper that goes around<00:20:24.780> assigner<00:20:25.440> and<00:20:26.039> you<00:20:26.220> can<00:20:26.340> just<00:20:26.580> quickly 00:20:27.049 --> 00:20:27.059 align:start position:0% around assigner and you can just quickly 00:20:27.059 --> 00:20:28.490 align:start position:0% around assigner and you can just quickly fire<00:20:27.299> off<00:20:27.539> transactions<00:20:28.140> and<00:20:28.320> it<00:20:28.440> will 00:20:28.490 --> 00:20:28.500 align:start position:0% fire off transactions and it will 00:20:28.500 --> 00:20:29.990 align:start position:0% fire off transactions and it will automatically<00:20:28.860> bump<00:20:29.039> up<00:20:29.220> the<00:20:29.340> nonce<00:20:29.760> from<00:20:29.880> the 00:20:29.990 --> 00:20:30.000 align:start position:0% automatically bump up the nonce from the 00:20:30.000 --> 00:20:32.210 align:start position:0% automatically bump up the nonce from the initial<00:20:30.179> amounts<00:20:30.600> of<00:20:30.720> fetched 00:20:32.210 --> 00:20:32.220 align:start position:0% initial amounts of fetched 00:20:32.220 --> 00:20:34.970 align:start position:0% initial amounts of fetched um<00:20:32.240> there<00:20:33.240> are<00:20:33.360> some<00:20:34.080> issues<00:20:34.500> with<00:20:34.679> that<00:20:34.799> as 00:20:34.970 --> 00:20:34.980 align:start position:0% um there are some issues with that as 00:20:34.980 --> 00:20:37.070 align:start position:0% um there are some issues with that as well<00:20:35.100> if<00:20:35.340> you<00:20:35.520> just<00:20:35.820> you<00:20:36.360> know<00:20:36.419> flood<00:20:36.900> the 00:20:37.070 --> 00:20:37.080 align:start position:0% well if you just you know flood the 00:20:37.080 --> 00:20:38.810 align:start position:0% well if you just you know flood the mempool<00:20:37.500> with<00:20:37.919> a<00:20:38.039> bunch<00:20:38.160> of<00:20:38.280> transactions 00:20:38.810 --> 00:20:38.820 align:start position:0% mempool with a bunch of transactions 00:20:38.820 --> 00:20:40.250 align:start position:0% mempool with a bunch of transactions from<00:20:39.120> the<00:20:39.299> same<00:20:39.419> address<00:20:39.660> that<00:20:40.020> are<00:20:40.140> all 00:20:40.250 --> 00:20:40.260 align:start position:0% from the same address that are all 00:20:40.260 --> 00:20:42.950 align:start position:0% from the same address that are all serialized<00:20:40.860> uh<00:20:41.700> it<00:20:41.940> could<00:20:42.059> be<00:20:42.240> seen<00:20:42.600> from<00:20:42.840> the 00:20:42.950 --> 00:20:42.960 align:start position:0% serialized uh it could be seen from the 00:20:42.960 --> 00:20:44.390 align:start position:0% serialized uh it could be seen from the Network's<00:20:43.260> point<00:20:43.440> of<00:20:43.500> view<00:20:43.620> as<00:20:43.799> a<00:20:43.919> Dos<00:20:44.280> attack 00:20:44.390 --> 00:20:44.400 align:start position:0% Network's point of view as a Dos attack 00:20:44.400 --> 00:20:46.490 align:start position:0% Network's point of view as a Dos attack and<00:20:44.700> so<00:20:44.820> it<00:20:45.000> might<00:20:45.120> drop<00:20:45.299> them<00:20:45.539> so<00:20:46.140> that's<00:20:46.260> a 00:20:46.490 --> 00:20:46.500 align:start position:0% and so it might drop them so that's a 00:20:46.500 --> 00:20:47.810 align:start position:0% and so it might drop them so that's a feature<00:20:46.740> I<00:20:46.860> want<00:20:46.980> to<00:20:47.100> add<00:20:47.160> to<00:20:47.400> the<00:20:47.580> nonce 00:20:47.810 --> 00:20:47.820 align:start position:0% feature I want to add to the nonce 00:20:47.820 --> 00:20:50.150 align:start position:0% feature I want to add to the nonce manager<00:20:48.000> in<00:20:48.120> V6<00:20:48.720> as<00:20:48.960> well<00:20:49.140> is<00:20:49.799> kind<00:20:49.980> of<00:20:50.039> the 00:20:50.150 --> 00:20:50.160 align:start position:0% manager in V6 as well is kind of the 00:20:50.160 --> 00:20:52.370 align:start position:0% manager in V6 as well is kind of the ability<00:20:50.460> to<00:20:50.760> rebroadcast<00:20:51.419> or<00:20:51.900> whenever 00:20:52.370 --> 00:20:52.380 align:start position:0% ability to rebroadcast or whenever 00:20:52.380 --> 00:20:55.610 align:start position:0% ability to rebroadcast or whenever something<00:20:52.679> succeeds<00:20:53.340> kind<00:20:54.179> of<00:20:54.299> like<00:20:54.539> have<00:20:55.440> a 00:20:55.610 --> 00:20:55.620 align:start position:0% something succeeds kind of like have a 00:20:55.620 --> 00:20:57.110 align:start position:0% something succeeds kind of like have a callback<00:20:55.919> that<00:20:56.220> lets<00:20:56.520> you<00:20:56.580> know<00:20:56.760> something 00:20:57.110 --> 00:20:57.120 align:start position:0% callback that lets you know something 00:20:57.120 --> 00:20:59.930 align:start position:0% callback that lets you know something succeeds<00:20:57.860> succeeded<00:20:58.860> and<00:20:59.400> so<00:20:59.520> you<00:20:59.700> can<00:20:59.820> kind 00:20:59.930 --> 00:20:59.940 align:start position:0% succeeds succeeded and so you can kind 00:20:59.940 --> 00:21:01.850 align:start position:0% succeeds succeeded and so you can kind of<00:21:00.059> nudge<00:21:00.539> or<00:21:00.780> tell<00:21:00.900> it<00:21:01.020> to<00:21:01.140> rebroadcast<00:21:01.620> the 00:21:01.850 --> 00:21:01.860 align:start position:0% of nudge or tell it to rebroadcast the 00:21:01.860 --> 00:21:03.770 align:start position:0% of nudge or tell it to rebroadcast the transactions<00:21:02.400> that<00:21:02.520> are<00:21:02.700> still<00:21:02.820> around<00:21:03.000> hey 00:21:03.770 --> 00:21:03.780 align:start position:0% transactions that are still around hey 00:21:03.780 --> 00:21:06.169 align:start position:0% transactions that are still around hey Richard<00:21:03.960> uh<00:21:04.500> can't<00:21:04.740> understate<00:21:05.340> how<00:21:05.880> useful 00:21:06.169 --> 00:21:06.179 align:start position:0% Richard uh can't understate how useful 00:21:06.179 --> 00:21:07.909 align:start position:0% Richard uh can't understate how useful what<00:21:06.660> you<00:21:06.780> did<00:21:06.960> for<00:21:07.200> the<00:21:07.380> whole<00:21:07.500> ethereum 00:21:07.909 --> 00:21:07.919 align:start position:0% what you did for the whole ethereum 00:21:07.919 --> 00:21:09.650 align:start position:0% what you did for the whole ethereum Community<00:21:08.160> we<00:21:08.640> use<00:21:08.820> what<00:21:09.120> you<00:21:09.240> do<00:21:09.360> every 00:21:09.650 --> 00:21:09.660 align:start position:0% Community we use what you do every 00:21:09.660 --> 00:21:11.270 align:start position:0% Community we use what you do every single<00:21:10.020> day<00:21:10.200> back<00:21:10.620> in<00:21:10.860> front<00:21:11.039> of<00:21:11.220> them 00:21:11.270 --> 00:21:11.280 align:start position:0% single day back in front of them 00:21:11.280 --> 00:21:13.850 align:start position:0% single day back in front of them everywhere<00:21:11.820> so<00:21:12.179> uh<00:21:12.840> thanks<00:21:13.080> for<00:21:13.260> that<00:21:13.380> thank 00:21:13.850 --> 00:21:13.860 align:start position:0% everywhere so uh thanks for that thank 00:21:13.860 --> 00:21:15.529 align:start position:0% everywhere so uh thanks for that thank you 00:21:15.529 --> 00:21:15.539 align:start position:0% you 00:21:15.539 --> 00:21:22.630 align:start position:0% you thanks 00:21:22.630 --> 00:21:22.640 align:start position:0% 00:21:22.640 --> 00:21:25.909 align:start position:0% so<00:21:23.640> yeah<00:21:23.820> more<00:21:24.480> than<00:21:24.600> deserved<00:21:25.620> um<00:21:25.679> one 00:21:25.909 --> 00:21:25.919 align:start position:0% so yeah more than deserved um one 00:21:25.919 --> 00:21:27.289 align:start position:0% so yeah more than deserved um one question<00:21:26.160> about<00:21:26.340> philosophy<00:21:26.940> and<00:21:27.059> this<00:21:27.179> is 00:21:27.289 --> 00:21:27.299 align:start position:0% question about philosophy and this is 00:21:27.299 --> 00:21:28.909 align:start position:0% question about philosophy and this is this<00:21:27.419> is<00:21:27.539> going<00:21:27.660> very<00:21:27.960> specific<00:21:28.260> on<00:21:28.559> being 00:21:28.909 --> 00:21:28.919 align:start position:0% this is going very specific on being 00:21:28.919 --> 00:21:29.990 align:start position:0% this is going very specific on being that<00:21:29.159> guy 00:21:29.990 --> 00:21:30.000 align:start position:0% that guy 00:21:30.000 --> 00:21:31.850 align:start position:0% that guy um<00:21:30.059> but<00:21:30.240> one<00:21:30.659> thing<00:21:30.840> that<00:21:31.080> ethers<00:21:31.559> has<00:21:31.679> a 00:21:31.850 --> 00:21:31.860 align:start position:0% um but one thing that ethers has a 00:21:31.860 --> 00:21:34.070 align:start position:0% um but one thing that ethers has a philosophy<00:21:32.220> is<00:21:32.520> really<00:21:32.640> the<00:21:33.059> how<00:21:33.480> it<00:21:33.659> returns 00:21:34.070 --> 00:21:34.080 align:start position:0% philosophy is really the how it returns 00:21:34.080 --> 00:21:35.690 align:start position:0% philosophy is really the how it returns undefined<00:21:34.740> and<00:21:34.919> actually<00:21:35.159> it<00:21:35.280> doesn't<00:21:35.460> return 00:21:35.690 --> 00:21:35.700 align:start position:0% undefined and actually it doesn't return 00:21:35.700 --> 00:21:37.610 align:start position:0% undefined and actually it doesn't return undefined<00:21:36.419> for<00:21:36.539> waiting<00:21:36.840> for<00:21:36.960> transactions 00:21:37.610 --> 00:21:37.620 align:start position:0% undefined for waiting for transactions 00:21:37.620 --> 00:21:39.890 align:start position:0% undefined for waiting for transactions and<00:21:38.039> we<00:21:38.220> actually<00:21:38.340> talked<00:21:38.880> once<00:21:39.240> in<00:21:39.539> one<00:21:39.720> of 00:21:39.890 --> 00:21:39.900 align:start position:0% and we actually talked once in one of 00:21:39.900 --> 00:21:42.409 align:start position:0% and we actually talked once in one of the PRS<00:21:40.500> of<00:21:40.860> typescript<00:21:41.700> really<00:21:42.059> giving<00:21:42.240> the 00:21:42.409 --> 00:21:42.419 align:start position:0% the PRS of typescript really giving the 00:21:42.419 --> 00:21:45.049 align:start position:0% the PRS of typescript really giving the option<00:21:42.659> of<00:21:42.900> of<00:21:43.260> returning<00:21:44.220> undefined<00:21:44.880> money 00:21:45.049 --> 00:21:45.059 align:start position:0% option of of returning undefined money 00:21:45.059 --> 00:21:47.149 align:start position:0% option of of returning undefined money transaction<00:21:45.600> you<00:21:46.080> wait<00:21:46.320> on<00:21:46.500> it<00:21:46.679> and<00:21:46.860> it 00:21:47.149 --> 00:21:47.159 align:start position:0% transaction you wait on it and it 00:21:47.159 --> 00:21:49.190 align:start position:0% transaction you wait on it and it doesn't<00:21:47.340> return<00:21:47.580> anything<00:21:47.940> for<00:21:48.240> example 00:21:49.190 --> 00:21:49.200 align:start position:0% doesn't return anything for example 00:21:49.200 --> 00:21:50.330 align:start position:0% doesn't return anything for example um<00:21:49.260> and<00:21:49.380> you<00:21:49.500> mentioned<00:21:49.740> that<00:21:49.860> that's<00:21:50.100> not 00:21:50.330 --> 00:21:50.340 align:start position:0% um and you mentioned that that's not 00:21:50.340 --> 00:21:51.649 align:start position:0% um and you mentioned that that's not really<00:21:50.460> part<00:21:50.700> of<00:21:50.820> the<00:21:50.880> philosophy<00:21:51.240> of<00:21:51.480> how 00:21:51.649 --> 00:21:51.659 align:start position:0% really part of the philosophy of how 00:21:51.659 --> 00:21:53.750 align:start position:0% really part of the philosophy of how you're<00:21:51.780> building<00:21:51.960> the<00:21:52.140> types<00:21:52.440> for<00:21:52.620> for<00:21:52.919> ethers 00:21:53.750 --> 00:21:53.760 align:start position:0% you're building the types for for ethers 00:21:53.760 --> 00:21:56.270 align:start position:0% you're building the types for for ethers so<00:21:54.120> I<00:21:54.600> missed<00:21:55.080> that<00:21:55.140> last<00:21:55.260> part<00:21:55.440> so<00:21:55.679> we<00:21:55.919> mainly 00:21:56.270 --> 00:21:56.280 align:start position:0% so I missed that last part so we mainly 00:21:56.280 --> 00:21:57.590 align:start position:0% so I missed that last part so we mainly set<00:21:56.460> a<00:21:56.580> transaction<00:21:56.880> and<00:21:57.059> you<00:21:57.240> get<00:21:57.299> back<00:21:57.419> to 00:21:57.590 --> 00:21:57.600 align:start position:0% set a transaction and you get back to 00:21:57.600 --> 00:21:59.029 align:start position:0% set a transaction and you get back to null<00:21:57.840> or 00:21:59.029 --> 00:21:59.039 align:start position:0% null or 00:21:59.039 --> 00:22:01.730 align:start position:0% null or um<00:21:59.100> let's<00:21:59.760> say<00:21:59.940> let's<00:22:00.480> say<00:22:00.659> it's<00:22:00.780> a<00:22:01.020> hash<00:22:01.200> that 00:22:01.730 --> 00:22:01.740 align:start position:0% um let's say let's say it's a hash that 00:22:01.740 --> 00:22:03.950 align:start position:0% um let's say let's say it's a hash that doesn't<00:22:02.039> exist<00:22:02.520> okay 00:22:03.950 --> 00:22:03.960 align:start position:0% doesn't exist okay 00:22:03.960 --> 00:22:05.270 align:start position:0% doesn't exist okay um<00:22:04.080> what<00:22:04.500> what<00:22:04.620> is<00:22:04.799> the<00:22:04.919> philosophy<00:22:05.220> of 00:22:05.270 --> 00:22:05.280 align:start position:0% um what what is the philosophy of 00:22:05.280 --> 00:22:06.470 align:start position:0% um what what is the philosophy of ether's<00:22:05.700> returning<00:22:06.000> that<00:22:06.120> would<00:22:06.240> it<00:22:06.360> be 00:22:06.470 --> 00:22:06.480 align:start position:0% ether's returning that would it be 00:22:06.480 --> 00:22:08.029 align:start position:0% ether's returning that would it be undefined<00:22:06.900> because<00:22:07.020> in<00:22:07.200> their<00:22:07.380> case<00:22:07.500> the<00:22:07.860> type 00:22:08.029 --> 00:22:08.039 align:start position:0% undefined because in their case the type 00:22:08.039 --> 00:22:10.130 align:start position:0% undefined because in their case the type script<00:22:08.460> for<00:22:08.820> that<00:22:09.000> doesn't<00:22:09.659> contain 00:22:10.130 --> 00:22:10.140 align:start position:0% script for that doesn't contain 00:22:10.140 --> 00:22:12.110 align:start position:0% script for that doesn't contain undefined<00:22:10.799> it<00:22:11.220> always<00:22:11.340> says<00:22:11.640> oh<00:22:11.760> I<00:22:12.000> know 00:22:12.110 --> 00:22:12.120 align:start position:0% undefined it always says oh I know 00:22:12.120 --> 00:22:13.250 align:start position:0% undefined it always says oh I know you're<00:22:12.240> talking<00:22:12.299> about<00:22:12.419> now<00:22:12.600> okay<00:22:12.900> so<00:22:13.140> that's 00:22:13.250 --> 00:22:13.260 align:start position:0% you're talking about now okay so that's 00:22:13.260 --> 00:22:15.350 align:start position:0% you're talking about now okay so that's okay<00:22:13.440> that's<00:22:13.799> a<00:22:13.980> big<00:22:14.220> thing<00:22:14.460> in<00:22:14.640> V6<00:22:14.940> as<00:22:15.120> well<00:22:15.240> I 00:22:15.350 --> 00:22:15.360 align:start position:0% okay that's a big thing in V6 as well I 00:22:15.360 --> 00:22:17.090 align:start position:0% okay that's a big thing in V6 as well I should<00:22:15.419> probably<00:22:15.659> put<00:22:15.840> on<00:22:15.960> the<00:22:16.080> odds<00:22:16.620> and<00:22:16.740> ends 00:22:17.090 --> 00:22:17.100 align:start position:0% should probably put on the odds and ends 00:22:17.100 --> 00:22:19.850 align:start position:0% should probably put on the odds and ends okay<00:22:17.640> uh<00:22:18.000> so<00:22:18.299> we<00:22:18.840> four<00:22:19.140> came<00:22:19.320> for<00:22:19.500> exactly 00:22:19.850 --> 00:22:19.860 align:start position:0% okay uh so we four came for exactly 00:22:19.860 --> 00:22:22.549 align:start position:0% okay uh so we four came for exactly right<00:22:20.220> so<00:22:20.640> right<00:22:21.299> okay<00:22:21.480> so<00:22:21.600> for<00:22:21.780> background 00:22:22.549 --> 00:22:22.559 align:start position:0% right so right okay so for background 00:22:22.559 --> 00:22:25.909 align:start position:0% right so right okay so for background basically<00:22:23.460> ether's<00:22:24.240> V5<00:22:24.600> was<00:22:25.260> started<00:22:25.740> two 00:22:25.909 --> 00:22:25.919 align:start position:0% basically ether's V5 was started two 00:22:25.919 --> 00:22:27.230 align:start position:0% basically ether's V5 was started two years<00:22:26.100> ago<00:22:26.340> I<00:22:26.520> was<00:22:26.640> still<00:22:26.820> kind<00:22:26.940> of<00:22:27.000> learning 00:22:27.230 --> 00:22:27.240 align:start position:0% years ago I was still kind of learning 00:22:27.240 --> 00:22:29.810 align:start position:0% years ago I was still kind of learning typescript<00:22:27.600> it<00:22:28.200> did<00:22:28.320> not<00:22:28.500> have<00:22:28.799> strict<00:22:29.520> null 00:22:29.810 --> 00:22:29.820 align:start position:0% typescript it did not have strict null 00:22:29.820 --> 00:22:32.330 align:start position:0% typescript it did not have strict null checks<00:22:30.299> enabled<00:22:30.900> which<00:22:31.740> basically<00:22:32.039> means 00:22:32.330 --> 00:22:32.340 align:start position:0% checks enabled which basically means 00:22:32.340 --> 00:22:34.610 align:start position:0% checks enabled which basically means anything<00:22:32.760> that<00:22:33.179> returns<00:22:33.659> anything 00:22:34.610 --> 00:22:34.620 align:start position:0% anything that returns anything 00:22:34.620 --> 00:22:37.010 align:start position:0% anything that returns anything I'll<00:22:35.159> turn<00:22:35.580> that<00:22:35.880> anything 00:22:37.010 --> 00:22:37.020 align:start position:0% I'll turn that anything 00:22:37.020 --> 00:22:38.510 align:start position:0% I'll turn that anything or<00:22:37.620> no 00:22:38.510 --> 00:22:38.520 align:start position:0% or no 00:22:38.520 --> 00:22:41.210 align:start position:0% or no and<00:22:38.880> so<00:22:39.000> in<00:22:39.179> V6<00:22:39.539> I've<00:22:39.840> got<00:22:39.960> strict<00:22:40.260> null<00:22:40.620> typing 00:22:41.210 --> 00:22:41.220 align:start position:0% and so in V6 I've got strict null typing 00:22:41.220 --> 00:22:43.490 align:start position:0% and so in V6 I've got strict null typing in<00:22:41.460> some<00:22:41.760> strict<00:22:42.120> null<00:22:42.840> checked<00:22:43.200> type 00:22:43.490 --> 00:22:43.500 align:start position:0% in some strict null checked type 00:22:43.500 --> 00:22:45.590 align:start position:0% in some strict null checked type whatever<00:22:44.100> you<00:22:44.400> know<00:22:44.580> that<00:22:44.820> what<00:22:45.120> the<00:22:45.240> plague 00:22:45.590 --> 00:22:45.600 align:start position:0% whatever you know that what the plague 00:22:45.600 --> 00:22:49.370 align:start position:0% whatever you know that what the plague is<00:22:45.720> it's<00:22:46.320> disabled<00:22:46.860> and<00:22:47.340> so<00:22:47.580> for<00:22:48.240> example<00:22:48.539> the 00:22:49.370 --> 00:22:49.380 align:start position:0% is it's disabled and so for example the 00:22:49.380 --> 00:22:52.130 align:start position:0% is it's disabled and so for example the provider's<00:22:49.980> method<00:22:50.340> for<00:22:50.520> get<00:22:50.700> transaction<00:22:51.240> it 00:22:52.130 --> 00:22:52.140 align:start position:0% provider's method for get transaction it 00:22:52.140 --> 00:22:54.470 align:start position:0% provider's method for get transaction it will<00:22:52.260> be<00:22:52.440> the<00:22:52.919> return<00:22:53.100> type<00:22:53.460> is<00:22:53.760> null<00:22:54.179> or 00:22:54.470 --> 00:22:54.480 align:start position:0% will be the return type is null or 00:22:54.480 --> 00:22:56.750 align:start position:0% will be the return type is null or transaction<00:22:54.960> response<00:22:55.500> whereas<00:22:56.039> in<00:22:56.159> V5<00:22:56.520> it 00:22:56.750 --> 00:22:56.760 align:start position:0% transaction response whereas in V5 it 00:22:56.760 --> 00:22:58.850 align:start position:0% transaction response whereas in V5 it was<00:22:56.880> just<00:22:57.000> transaction<00:22:57.360> response<00:22:58.020> and<00:22:58.500> I<00:22:58.679> just 00:22:58.850 --> 00:22:58.860 align:start position:0% was just transaction response and I just 00:22:58.860 --> 00:23:01.370 align:start position:0% was just transaction response and I just trusted<00:22:59.280> people<00:22:59.460> knew<00:22:59.940> that<00:23:00.600> uh<00:23:00.900> it<00:23:01.140> could<00:23:01.260> be 00:23:01.370 --> 00:23:01.380 align:start position:0% trusted people knew that uh it could be 00:23:01.380 --> 00:23:04.850 align:start position:0% trusted people knew that uh it could be null<00:23:01.679> but<00:23:02.240> don't<00:23:03.240> worry<00:23:03.419> about<00:23:03.480> it<00:23:03.720> so<00:23:04.140> yes<00:23:04.380> uh 00:23:04.850 --> 00:23:04.860 align:start position:0% null but don't worry about it so yes uh 00:23:04.860 --> 00:23:07.850 align:start position:0% null but don't worry about it so yes uh yes<00:23:05.100> V6<00:23:05.460> has<00:23:05.700> been<00:23:05.880> fixed<00:23:06.659> um<00:23:06.659> it<00:23:06.960> helps<00:23:07.500> fix<00:23:07.620> a 00:23:07.850 --> 00:23:07.860 align:start position:0% yes V6 has been fixed um it helps fix a 00:23:07.860 --> 00:23:08.930 align:start position:0% yes V6 has been fixed um it helps fix a lot<00:23:07.919> of<00:23:07.980> other<00:23:08.039> people's<00:23:08.340> libraries<00:23:08.640> as<00:23:08.820> well 00:23:08.930 --> 00:23:08.940 align:start position:0% lot of other people's libraries as well 00:23:08.940 --> 00:23:10.789 align:start position:0% lot of other people's libraries as well that<00:23:09.179> are<00:23:09.360> like<00:23:09.480> dependent<00:23:10.080> on<00:23:10.200> it<00:23:10.320> and<00:23:10.620> are 00:23:10.789 --> 00:23:10.799 align:start position:0% that are like dependent on it and are 00:23:10.799 --> 00:23:12.590 align:start position:0% that are like dependent on it and are kind<00:23:11.039> of<00:23:11.100> crawling<00:23:11.460> into<00:23:11.640> the<00:23:11.760> ethers<00:23:12.179> tree<00:23:12.299> to 00:23:12.590 --> 00:23:12.600 align:start position:0% kind of crawling into the ethers tree to 00:23:12.600 --> 00:23:14.630 align:start position:0% kind of crawling into the ethers tree to like<00:23:12.840> run<00:23:13.260> their<00:23:13.440> linting<00:23:13.799> rules<00:23:14.039> so<00:23:14.340> yes 00:23:14.630 --> 00:23:14.640 align:start position:0% like run their linting rules so yes 00:23:14.640 --> 00:23:16.730 align:start position:0% like run their linting rules so yes that's<00:23:14.880> absolutely<00:23:15.240> changed<00:23:15.600> and<00:23:16.320> will<00:23:16.500> there 00:23:16.730 --> 00:23:16.740 align:start position:0% that's absolutely changed and will there 00:23:16.740 --> 00:23:18.710 align:start position:0% that's absolutely changed and will there be<00:23:16.860> backwards<00:23:17.280> compatibility<00:23:17.760> between<00:23:18.240> those 00:23:18.710 --> 00:23:18.720 align:start position:0% be backwards compatibility between those 00:23:18.720 --> 00:23:21.350 align:start position:0% be backwards compatibility between those new<00:23:19.320> big<00:23:19.919> in<00:23:20.100> type<00:23:20.400> and<00:23:20.580> the<00:23:20.760> old<00:23:20.940> big<00:23:21.120> number 00:23:21.350 --> 00:23:21.360 align:start position:0% new big in type and the old big number 00:23:21.360 --> 00:23:25.370 align:start position:0% new big in type and the old big number type<00:23:21.720> like<00:23:22.559> will<00:23:22.799> big<00:23:23.039> in<00:23:23.400> be<00:23:23.700> big<00:23:24.059> number-ish 00:23:25.370 --> 00:23:25.380 align:start position:0% type like will big in be big number-ish 00:23:25.380 --> 00:23:27.169 align:start position:0% type like will big in be big number-ish sorry<00:23:26.039> will<00:23:26.280> it<00:23:26.400> will<00:23:26.580> what<00:23:26.700> be<00:23:26.880> big<00:23:27.000> numbers 00:23:27.169 --> 00:23:27.179 align:start position:0% sorry will it will what be big numbers 00:23:27.179 --> 00:23:29.870 align:start position:0% sorry will it will what be big numbers at<00:23:27.900> the<00:23:28.080> new<00:23:28.200> Big<00:23:28.440> in<00:23:28.620> time<00:23:28.799> oh<00:23:29.100> yes<00:23:29.220> too<00:23:29.460> big<00:23:29.640> I 00:23:29.870 --> 00:23:29.880 align:start position:0% at the new Big in time oh yes too big I 00:23:29.880 --> 00:23:31.730 align:start position:0% at the new Big in time oh yes too big I mean<00:23:29.940> for<00:23:30.240> input<00:23:30.480> types<00:23:30.780> you<00:23:30.900> mean<00:23:31.080> yeah<00:23:31.500> yes 00:23:31.730 --> 00:23:31.740 align:start position:0% mean for input types you mean yeah yes 00:23:31.740 --> 00:23:32.750 align:start position:0% mean for input types you mean yeah yes there's<00:23:31.980> no<00:23:32.220> there's<00:23:32.400> still<00:23:32.520> a<00:23:32.640> big 00:23:32.750 --> 00:23:32.760 align:start position:0% there's no there's still a big 00:23:32.760 --> 00:23:35.510 align:start position:0% there's no there's still a big number-ish<00:23:33.120> type<00:23:33.419> because<00:23:34.140> uh<00:23:34.980> like<00:23:35.159> so<00:23:35.340> for 00:23:35.510 --> 00:23:35.520 align:start position:0% number-ish type because uh like so for 00:23:35.520 --> 00:23:37.010 align:start position:0% number-ish type because uh like so for example<00:23:35.760> the<00:23:36.120> the<00:23:36.299> slide<00:23:36.600> up<00:23:36.780> there<00:23:36.900> that 00:23:37.010 --> 00:23:37.020 align:start position:0% example the the slide up there that 00:23:37.020 --> 00:23:39.590 align:start position:0% example the the slide up there that demonstrated<00:23:37.500> I<00:23:37.860> lost<00:23:38.100> the<00:23:38.400> clicker 00:23:39.590 --> 00:23:39.600 align:start position:0% demonstrated I lost the clicker 00:23:39.600 --> 00:23:41.870 align:start position:0% demonstrated I lost the clicker um<00:23:39.720> the<00:23:40.020> slide<00:23:40.320> that<00:23:40.500> shows<00:23:40.919> you 00:23:41.870 --> 00:23:41.880 align:start position:0% um the slide that shows you 00:23:41.880 --> 00:23:42.890 align:start position:0% um the slide that shows you um 00:23:42.890 --> 00:23:42.900 align:start position:0% um 00:23:42.900 --> 00:23:45.049 align:start position:0% um uh<00:23:43.320> like<00:23:43.440> the<00:23:43.679> transaction<00:23:44.100> dot<00:23:44.580> Max<00:23:44.700> gas 00:23:45.049 --> 00:23:45.059 align:start position:0% uh like the transaction dot Max gas 00:23:45.059 --> 00:23:47.090 align:start position:0% uh like the transaction dot Max gas equals<00:23:45.720> uh<00:23:46.320> so<00:23:46.500> that<00:23:46.620> takes<00:23:46.740> in<00:23:46.860> a<00:23:47.039> big 00:23:47.090 --> 00:23:47.100 align:start position:0% equals uh so that takes in a big 00:23:47.100 --> 00:23:48.470 align:start position:0% equals uh so that takes in a big number-ish<00:23:47.400> so<00:23:47.640> you<00:23:47.700> can<00:23:47.760> pass<00:23:47.880> in<00:23:48.059> a<00:23:48.179> bigint 00:23:48.470 --> 00:23:48.480 align:start position:0% number-ish so you can pass in a bigint 00:23:48.480 --> 00:23:50.630 align:start position:0% number-ish so you can pass in a bigint you<00:23:49.020> can<00:23:49.200> pass<00:23:49.380> in<00:23:49.620> a<00:23:49.860> string<00:23:50.159> that<00:23:50.340> happens<00:23:50.520> to 00:23:50.630 --> 00:23:50.640 align:start position:0% you can pass in a string that happens to 00:23:50.640 --> 00:23:51.830 align:start position:0% you can pass in a string that happens to be<00:23:50.700> decimal<00:23:51.059> number<00:23:51.179> you<00:23:51.360> can<00:23:51.480> pass<00:23:51.539> in<00:23:51.720> a 00:23:51.830 --> 00:23:51.840 align:start position:0% be decimal number you can pass in a 00:23:51.840 --> 00:23:53.270 align:start position:0% be decimal number you can pass in a string<00:23:52.020> that's<00:23:52.140> a<00:23:52.260> hex<00:23:52.440> number 00:23:53.270 --> 00:23:53.280 align:start position:0% string that's a hex number 00:23:53.280 --> 00:23:55.909 align:start position:0% string that's a hex number um<00:23:53.340> that'll<00:23:53.640> all<00:23:53.760> be<00:23:53.880> munged<00:23:54.419> into<00:23:54.900> a<00:23:55.380> big<00:23:55.440> int 00:23:55.909 --> 00:23:55.919 align:start position:0% um that'll all be munged into a big int 00:23:55.919 --> 00:23:57.830 align:start position:0% um that'll all be munged into a big int type<00:23:56.100> but<00:23:56.640> you<00:23:56.760> can<00:23:56.880> still<00:23:57.059> pass<00:23:57.299> anything 00:23:57.830 --> 00:23:57.840 align:start position:0% type but you can still pass anything 00:23:57.840 --> 00:24:00.890 align:start position:0% type but you can still pass anything anything<00:23:58.799> that's<00:23:59.159> not<00:23:59.460> ambiguous<00:24:00.059> ethers 00:24:00.890 --> 00:24:00.900 align:start position:0% anything that's not ambiguous ethers 00:24:00.900 --> 00:24:02.690 align:start position:0% anything that's not ambiguous ethers will<00:24:01.020> accept<00:24:01.080> it<00:24:01.559> will<00:24:01.679> not<00:24:01.799> accept<00:24:01.980> things 00:24:02.690 --> 00:24:02.700 align:start position:0% will accept it will not accept things 00:24:02.700 --> 00:24:06.529 align:start position:0% will accept it will not accept things that<00:24:03.000> it<00:24:03.179> can't<00:24:03.659> possibly<00:24:04.400> interpret<00:24:05.400> like<00:24:05.760> uh 00:24:06.529 --> 00:24:06.539 align:start position:0% that it can't possibly interpret like uh 00:24:06.539 --> 00:24:09.110 align:start position:0% that it can't possibly interpret like uh for<00:24:06.840> example<00:24:07.020> non-zero<00:24:07.799> X<00:24:07.919> prefixed<00:24:08.640> things 00:24:09.110 --> 00:24:09.120 align:start position:0% for example non-zero X prefixed things 00:24:09.120 --> 00:24:11.029 align:start position:0% for example non-zero X prefixed things because<00:24:09.780> if<00:24:10.020> it<00:24:10.200> did<00:24:10.380> that<00:24:10.500> it<00:24:10.740> wouldn't<00:24:10.860> know 00:24:11.029 --> 00:24:11.039 align:start position:0% because if it did that it wouldn't know 00:24:11.039 --> 00:24:15.110 align:start position:0% because if it did that it wouldn't know whether<00:24:11.159> one<00:24:11.520> one<00:24:11.820> was<00:24:13.159> hexadecimal<00:24:14.159> 17<00:24:14.580> or 00:24:15.110 --> 00:24:15.120 align:start position:0% whether one one was hexadecimal 17 or 00:24:15.120 --> 00:24:17.810 align:start position:0% whether one one was hexadecimal 17 or binary<00:24:15.600> 11<00:24:15.780> and<00:24:16.559> so<00:24:16.740> it<00:24:16.919> requires<00:24:17.400> you<00:24:17.520> to<00:24:17.700> be 00:24:17.810 --> 00:24:17.820 align:start position:0% binary 11 and so it requires you to be 00:24:17.820 --> 00:24:19.610 align:start position:0% binary 11 and so it requires you to be completely<00:24:18.120> non-ambiguous 00:24:19.610 --> 00:24:19.620 align:start position:0% completely non-ambiguous 00:24:19.620 --> 00:24:21.230 align:start position:0% completely non-ambiguous um<00:24:19.679> so<00:24:20.100> if<00:24:20.159> you<00:24:20.340> pass<00:24:20.460> in<00:24:20.640> a<00:24:20.760> string<00:24:20.940> that's<00:24:21.059> one 00:24:21.230 --> 00:24:21.240 align:start position:0% um so if you pass in a string that's one 00:24:21.240 --> 00:24:23.330 align:start position:0% um so if you pass in a string that's one one<00:24:21.419> it's<00:24:21.600> going<00:24:21.780> to<00:24:21.840> assume<00:24:22.140> as<00:24:22.200> decimal<00:24:22.620> but 00:24:23.330 --> 00:24:23.340 align:start position:0% one it's going to assume as decimal but 00:24:23.340 --> 00:24:25.610 align:start position:0% one it's going to assume as decimal but yes<00:24:23.520> it's<00:24:24.059> uh<00:24:24.419> it's<00:24:24.960> still<00:24:25.080> a<00:24:25.140> big<00:24:25.200> number<00:24:25.380> it's 00:24:25.610 --> 00:24:25.620 align:start position:0% yes it's uh it's still a big number it's 00:24:25.620 --> 00:24:28.430 align:start position:0% yes it's uh it's still a big number it's still<00:24:25.860> a<00:24:26.039> big<00:24:26.280> number-ish 00:24:28.430 --> 00:24:28.440 align:start position:0% still a big number-ish 00:24:28.440 --> 00:24:29.810 align:start position:0% still a big number-ish um<00:24:28.500> and<00:24:28.740> there's<00:24:28.860> functions<00:24:29.340> as<00:24:29.460> well<00:24:29.640> for 00:24:29.810 --> 00:24:29.820 align:start position:0% um and there's functions as well for 00:24:29.820 --> 00:24:32.990 align:start position:0% um and there's functions as well for your<00:24:30.000> own<00:24:30.120> purposes<00:24:30.480> that<00:24:31.260> will<00:24:31.820> convert<00:24:32.820> any 00:24:32.990 --> 00:24:33.000 align:start position:0% your own purposes that will convert any 00:24:33.000 --> 00:24:35.930 align:start position:0% your own purposes that will convert any big<00:24:33.179> number-ish<00:24:33.659> into<00:24:34.140> a<00:24:34.320> big<00:24:34.440> number<00:24:34.760> or<00:24:35.760> any 00:24:35.930 --> 00:24:35.940 align:start position:0% big number-ish into a big number or any 00:24:35.940 --> 00:24:37.669 align:start position:0% big number-ish into a big number or any numeric<00:24:36.480> which<00:24:36.780> is<00:24:36.840> another<00:24:36.960> type<00:24:37.260> that<00:24:37.500> it 00:24:37.669 --> 00:24:37.679 align:start position:0% numeric which is another type that it 00:24:37.679 --> 00:24:41.870 align:start position:0% numeric which is another type that it now<00:24:37.799> has<00:24:38.100> into<00:24:38.640> a<00:24:39.480> number 00:24:41.870 --> 00:24:41.880 align:start position:0% now has into a number 00:24:41.880 --> 00:24:44.659 align:start position:0% now has into a number thank<00:24:42.179> you<00:24:42.299> thank<00:24:42.480> you