WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:11.600 align:start position:0% [Applause] 00:00:11.600 --> 00:00:11.610 align:start position:0% 00:00:11.610 --> 00:00:15.060 align:start position:0% there's<00:00:12.610> I<00:00:12.820> feel<00:00:13.179> a<00:00:13.480> really<00:00:14.110> bounty<00:00:14.650> of<00:00:14.679> bold 00:00:15.060 --> 00:00:15.070 align:start position:0% there's I feel a really bounty of bold 00:00:15.070 --> 00:00:18.120 align:start position:0% there's I feel a really bounty of bold but<00:00:15.820> absolutely<00:00:16.380> sweet<00:00:17.380> requests<00:00:17.740> for<00:00:17.919> thing 00:00:18.120 --> 00:00:18.130 align:start position:0% but absolutely sweet requests for thing 00:00:18.130 --> 00:00:20.339 align:start position:0% but absolutely sweet requests for thing that<00:00:18.279> I<00:00:18.550> don't<00:00:19.180> want<00:00:19.300> to<00:00:19.360> deal<00:00:19.509> with<00:00:19.539> or<00:00:19.990> is 00:00:20.339 --> 00:00:20.349 align:start position:0% that I don't want to deal with or is 00:00:20.349 --> 00:00:21.479 align:start position:0% that I don't want to deal with or is this<00:00:20.439> type<00:00:20.680> I<00:00:20.800> will<00:00:20.949> have<00:00:21.160> a<00:00:21.189> side<00:00:21.400> with 00:00:21.479 --> 00:00:21.489 align:start position:0% this type I will have a side with 00:00:21.489 --> 00:00:23.519 align:start position:0% this type I will have a side with absolutely<00:00:21.880> you<00:00:22.060> got<00:00:22.270> balcony<00:00:22.840> they're 00:00:23.519 --> 00:00:23.529 align:start position:0% absolutely you got balcony they're 00:00:23.529 --> 00:00:27.870 align:start position:0% absolutely you got balcony they're pretty<00:00:23.710> good<00:00:24.240> so<00:00:25.240> well<00:00:25.900> oh<00:00:26.230> nine<00:00:26.800> ever<00:00:27.580> take 00:00:27.870 --> 00:00:27.880 align:start position:0% pretty good so well oh nine ever take 00:00:27.880 --> 00:00:32.369 align:start position:0% pretty good so well oh nine ever take some<00:00:28.150> seconds<00:00:28.509> so<00:00:28.810> should<00:00:29.529> I<00:00:29.560> start<00:00:29.619> out<00:00:29.980> or<00:00:31.379> so 00:00:32.369 --> 00:00:32.379 align:start position:0% some seconds so should I start out or so 00:00:32.379 --> 00:00:32.910 align:start position:0% some seconds so should I start out or so mellow 00:00:32.910 --> 00:00:32.920 align:start position:0% mellow 00:00:32.920 --> 00:00:35.790 align:start position:0% mellow I'm<00:00:33.280> Richard<00:00:33.550> Moore<00:00:33.790> IRA<00:00:34.600> operator<00:00:35.290> ethers<00:00:35.589> je 00:00:35.790 --> 00:00:35.800 align:start position:0% I'm Richard Moore IRA operator ethers je 00:00:35.800 --> 00:00:38.790 align:start position:0% I'm Richard Moore IRA operator ethers je s<00:00:35.920> it's<00:00:36.339> a<00:00:36.550> hearing<00:00:37.030> library<00:00:37.480> as<00:00:38.320> goals<00:00:38.589> are 00:00:38.790 --> 00:00:38.800 align:start position:0% s it's a hearing library as goals are 00:00:38.800 --> 00:00:42.959 align:start position:0% s it's a hearing library as goals are being<00:00:38.920> completely<00:00:39.280> simple<00:00:39.820> and<00:00:40.000> tiny<00:00:40.210> I<00:00:41.969> also 00:00:42.959 --> 00:00:42.969 align:start position:0% being completely simple and tiny I also 00:00:42.969 --> 00:00:44.910 align:start position:0% being completely simple and tiny I also attend<00:00:43.390> overseeing<00:00:43.780> my<00:00:44.020> slides<00:00:44.379> so<00:00:44.620> I<00:00:44.739> might 00:00:44.910 --> 00:00:44.920 align:start position:0% attend overseeing my slides so I might 00:00:44.920 --> 00:00:48.110 align:start position:0% attend overseeing my slides so I might say<00:00:45.160> things<00:00:45.219> with<00:00:45.610> the<00:00:45.820> slide<00:00:46.030> comes<00:00:46.270> to<00:00:46.870> see 00:00:48.110 --> 00:00:48.120 align:start position:0% say things with the slide comes to see 00:00:48.120 --> 00:00:51.150 align:start position:0% say things with the slide comes to see so<00:00:49.120> there's<00:00:49.809> a<00:00:49.840> few<00:00:49.960> things<00:00:50.020> that<00:00:50.230> I<00:00:50.260> don't 00:00:51.150 --> 00:00:51.160 align:start position:0% so there's a few things that I don't 00:00:51.160 --> 00:00:52.650 align:start position:0% so there's a few things that I don't think<00:00:51.489> a<00:00:51.550> whole<00:00:51.760> bunch<00:00:51.910> of<00:00:52.000> random<00:00:52.149> stuff<00:00:52.449> so 00:00:52.650 --> 00:00:52.660 align:start position:0% think a whole bunch of random stuff so 00:00:52.660 --> 00:00:54.029 align:start position:0% think a whole bunch of random stuff so the<00:00:52.809> things<00:00:52.989> that<00:00:53.109> are<00:00:53.199> like<00:00:53.350> kind<00:00:53.469> of<00:00:53.559> folder 00:00:54.029 --> 00:00:54.039 align:start position:0% the things that are like kind of folder 00:00:54.039 --> 00:00:56.849 align:start position:0% the things that are like kind of folder I'll<00:00:54.280> be<00:00:54.399> wanting<00:00:54.640> to<00:00:54.760> more<00:00:54.910> detail<00:00:55.590> so<00:00:56.590> I'll 00:00:56.849 --> 00:00:56.859 align:start position:0% I'll be wanting to more detail so I'll 00:00:56.859 --> 00:00:58.920 align:start position:0% I'll be wanting to more detail so I'll just<00:00:56.980> go<00:00:57.100> quickly<00:00:57.370> over<00:00:57.519> kind<00:00:57.969> of<00:00:58.059> bigger 00:00:58.920 --> 00:00:58.930 align:start position:0% just go quickly over kind of bigger 00:00:58.930 --> 00:01:02.400 align:start position:0% just go quickly over kind of bigger things<00:01:00.030> so<00:01:01.030> for<00:01:01.420> example<00:01:01.750> so<00:01:01.870> it's<00:01:02.050> complete 00:01:02.400 --> 00:01:02.410 align:start position:0% things so for example so it's complete 00:01:02.410 --> 00:01:04.410 align:start position:0% things so for example so it's complete you<00:01:02.679> can<00:01:02.859> create<00:01:03.070> equality<00:01:03.370> of<00:01:03.730> utilities 00:01:04.410 --> 00:01:04.420 align:start position:0% you can create equality of utilities 00:01:04.420 --> 00:01:08.400 align:start position:0% you can create equality of utilities frameworks<00:01:05.379> and<00:01:05.590> apps<00:01:05.740> used<00:01:06.420> lying<00:01:07.420> ether 00:01:08.400 --> 00:01:08.410 align:start position:0% frameworks and apps used lying ether 00:01:08.410 --> 00:01:10.499 align:start position:0% frameworks and apps used lying ether lying<00:01:08.619> it's<00:01:09.340> built<00:01:09.580> on<00:01:09.700> public<00:01:10.000> leaders<00:01:10.300> that 00:01:10.499 --> 00:01:10.509 align:start position:0% lying it's built on public leaders that 00:01:10.509 --> 00:01:12.660 align:start position:0% lying it's built on public leaders that their<00:01:10.630> loves<00:01:10.869> about<00:01:11.200> things<00:01:11.440> I<00:01:11.740> try<00:01:12.280> to<00:01:12.310> expose 00:01:12.660 --> 00:01:12.670 align:start position:0% their loves about things I try to expose 00:01:12.670 --> 00:01:14.760 align:start position:0% their loves about things I try to expose all<00:01:12.940> the<00:01:12.970> internals<00:01:13.690> that<00:01:13.899> I<00:01:14.020> use<00:01:14.229> is<00:01:14.440> because 00:01:14.760 --> 00:01:14.770 align:start position:0% all the internals that I use is because 00:01:14.770 --> 00:01:17.100 align:start position:0% all the internals that I use is because those<00:01:15.069> are<00:01:15.190> often<00:01:15.429> useful<00:01:15.550> for<00:01:16.090> tools<00:01:16.270> we're 00:01:17.100 --> 00:01:17.110 align:start position:0% those are often useful for tools we're 00:01:17.110 --> 00:01:18.419 align:start position:0% those are often useful for tools we're trying<00:01:17.289> to<00:01:17.410> kind<00:01:17.590> of<00:01:17.619> do<00:01:17.709> like<00:01:17.740> lower<00:01:18.099> level 00:01:18.419 --> 00:01:18.429 align:start position:0% trying to kind of do like lower level 00:01:18.429 --> 00:01:20.550 align:start position:0% trying to kind of do like lower level things<00:01:18.630> it's<00:01:19.630> ready<00:01:19.810> so<00:01:20.050> it's<00:01:20.170> available<00:01:20.259> for 00:01:20.550 --> 00:01:20.560 align:start position:0% things it's ready so it's available for 00:01:20.560 --> 00:01:25.050 align:start position:0% things it's ready so it's available for nodejs<00:01:20.920> type<00:01:21.310> scripts<00:01:21.899> b5<00:01:22.899> has<00:01:23.759> yes<00:01:24.759> six 00:01:25.050 --> 00:01:25.060 align:start position:0% nodejs type scripts b5 has yes six 00:01:25.060 --> 00:01:27.899 align:start position:0% nodejs type scripts b5 has yes six modules<00:01:25.239> available<00:01:25.599> and<00:01:26.289> the 00:01:27.899 --> 00:01:27.909 align:start position:0% modules available and the 00:01:27.909 --> 00:01:31.250 align:start position:0% modules available and the even<00:01:28.330> before<00:01:28.479> is<00:01:28.960> complete<00:01:29.440> rating<00:01:30.030> browser 00:01:31.250 --> 00:01:31.260 align:start position:0% even before is complete rating browser 00:01:31.260 --> 00:01:34.050 align:start position:0% even before is complete rating browser tested<00:01:32.260> they're<00:01:32.409> showing<00:01:32.650> over<00:01:33.159> 20,000<00:01:33.909> test 00:01:34.050 --> 00:01:34.060 align:start position:0% tested they're showing over 20,000 test 00:01:34.060 --> 00:01:37.200 align:start position:0% tested they're showing over 20,000 test pieces<00:01:34.440> I<00:01:35.440> pretty<00:01:36.250> testing<00:01:36.790> the<00:01:36.880> fit<00:01:37.030> big 00:01:37.200 --> 00:01:37.210 align:start position:0% pieces I pretty testing the fit big 00:01:37.210 --> 00:01:40.590 align:start position:0% pieces I pretty testing the fit big thing<00:01:37.420> I<00:01:38.430> know<00:01:39.430> I<00:01:39.670> use<00:01:39.940> ethers<00:01:40.270> for<00:01:40.450> my<00:01:40.540> own 00:01:40.590 --> 00:01:40.600 align:start position:0% thing I know I use ethers for my own 00:01:40.600 --> 00:01:42.420 align:start position:0% thing I know I use ethers for my own stuff<00:01:40.720> I<00:01:40.960> don't<00:01:41.080> want<00:01:41.290> a<00:01:41.619> mistake<00:01:41.950> I<00:01:42.070> need<00:01:42.280> to 00:01:42.420 --> 00:01:42.430 align:start position:0% stuff I don't want a mistake I need to 00:01:42.430 --> 00:01:44.490 align:start position:0% stuff I don't want a mistake I need to destroy<00:01:42.700> my<00:01:42.820> own<00:01:42.970> anger<00:01:43.150> and<00:01:43.780> so<00:01:43.930> it<00:01:44.050> was<00:01:44.170> more 00:01:44.490 --> 00:01:44.500 align:start position:0% destroy my own anger and so it was more 00:01:44.500 --> 00:01:46.080 align:start position:0% destroy my own anger and so it was more correct<00:01:45.009> okay<00:01:45.280> teasing<00:01:45.640> or<00:01:45.759> enemies 00:01:46.080 --> 00:01:46.090 align:start position:0% correct okay teasing or enemies 00:01:46.090 --> 00:01:48.889 align:start position:0% correct okay teasing or enemies important<00:01:46.540> things<00:01:46.690> so<00:01:47.399> although<00:01:48.399> it's<00:01:48.580> tiny 00:01:48.889 --> 00:01:48.899 align:start position:0% important things so although it's tiny 00:01:48.899 --> 00:01:52.230 align:start position:0% important things so although it's tiny it's<00:01:49.899> creeping<00:01:50.740> up<00:01:50.860> slowly<00:01:51.369> over<00:01:51.700> time<00:01:51.880> last 00:01:52.230 --> 00:01:52.240 align:start position:0% it's creeping up slowly over time last 00:01:52.240 --> 00:01:53.760 align:start position:0% it's creeping up slowly over time last year's<00:01:52.540> with<00:01:52.750> 78<00:01:53.229> kilobytes 00:01:53.760 --> 00:01:53.770 align:start position:0% year's with 78 kilobytes 00:01:53.770 --> 00:01:55.109 align:start position:0% year's with 78 kilobytes there's<00:01:54.310> been<00:01:54.399> a<00:01:54.430> lot<00:01:54.490> more<00:01:54.640> supply<00:01:54.850> that<00:01:55.000> so 00:01:55.109 --> 00:01:55.119 align:start position:0% there's been a lot more supply that so 00:01:55.119 --> 00:01:57.899 align:start position:0% there's been a lot more supply that so now<00:01:55.270> over<00:01:55.720> the<00:01:55.810> wire<00:01:55.960> is<00:01:56.229> about<00:01:56.340> 98<00:01:57.340> kilobytes 00:01:57.899 --> 00:01:57.909 align:start position:0% now over the wire is about 98 kilobytes 00:01:57.909 --> 00:01:59.580 align:start position:0% now over the wire is about 98 kilobytes once<00:01:58.240> again<00:01:58.360> sup<00:01:58.570> 100<00:01:58.899> or<00:01:58.990> I<00:01:59.110> start<00:01:59.440> panicking 00:01:59.580 --> 00:01:59.590 align:start position:0% once again sup 100 or I start panicking 00:01:59.590 --> 00:02:02.130 align:start position:0% once again sup 100 or I start panicking and<00:02:00.039> maybe<00:02:00.820> start<00:02:01.090> rolling<00:02:01.360> back<00:02:01.390> employee<00:02:02.050> of 00:02:02.130 --> 00:02:02.140 align:start position:0% and maybe start rolling back employee of 00:02:02.140 --> 00:02:04.169 align:start position:0% and maybe start rolling back employee of some<00:02:02.289> of<00:02:02.350> the<00:02:02.410> features<00:02:02.500> but<00:02:03.340> part<00:02:03.640> of<00:02:03.789> the 00:02:04.169 --> 00:02:04.179 align:start position:0% some of the features but part of the 00:02:04.179 --> 00:02:06.870 align:start position:0% some of the features but part of the move<00:02:04.570> for<00:02:04.840> v5<00:02:05.200> is<00:02:05.229> moving<00:02:05.860> for<00:02:06.009> modular<00:02:06.399> system 00:02:06.870 --> 00:02:06.880 align:start position:0% move for v5 is moving for modular system 00:02:06.880 --> 00:02:10.020 align:start position:0% move for v5 is moving for modular system using<00:02:07.390> sort<00:02:08.170> of<00:02:08.320> lerna<00:02:08.560> is<00:02:09.310> usually<00:02:09.820> a<00:02:09.850> lot<00:02:09.970> of 00:02:10.020 --> 00:02:10.030 align:start position:0% using sort of lerna is usually a lot of 00:02:10.030 --> 00:02:11.729 align:start position:0% using sort of lerna is usually a lot of parts<00:02:10.300> of<00:02:10.390> learn<00:02:10.539> and<00:02:10.570> has<00:02:11.080> a<00:02:11.110> bunch<00:02:11.320> of<00:02:11.410> stuff 00:02:11.729 --> 00:02:11.739 align:start position:0% parts of learn and has a bunch of stuff 00:02:11.739 --> 00:02:14.670 align:start position:0% parts of learn and has a bunch of stuff to<00:02:12.160> learn<00:02:12.430> on<00:02:12.970> top<00:02:13.150> of<00:02:13.300> it<00:02:13.420> but<00:02:14.350> that<00:02:14.410> way<00:02:14.620> if 00:02:14.670 --> 00:02:14.680 align:start position:0% to learn on top of it but that way if 00:02:14.680 --> 00:02:16.920 align:start position:0% to learn on top of it but that way if you<00:02:14.800> just<00:02:15.010> eat<00:02:15.280> API<00:02:15.760> coding<00:02:16.209> about<00:02:16.630> the<00:02:16.750> month 00:02:16.920 --> 00:02:16.930 align:start position:0% you just eat API coding about the month 00:02:16.930 --> 00:02:18.630 align:start position:0% you just eat API coding about the month of<00:02:17.050> the<00:02:17.110> librarian<00:02:17.590> and<00:02:17.860> not<00:02:18.340> worry<00:02:18.610> about 00:02:18.630 --> 00:02:18.640 align:start position:0% of the librarian and not worry about 00:02:18.640 --> 00:02:20.910 align:start position:0% of the librarian and not worry about having<00:02:18.850> an<00:02:19.120> entire<00:02:19.390> clip<00:02:19.660> to<00:02:19.810> turn<00:02:20.080> our<00:02:20.709> key 00:02:20.910 --> 00:02:20.920 align:start position:0% having an entire clip to turn our key 00:02:20.920 --> 00:02:24.900 align:start position:0% having an entire clip to turn our key light<00:02:21.069> ratings<00:02:23.370> lots<00:02:24.370> of<00:02:24.459> documentation 00:02:24.900 --> 00:02:24.910 align:start position:0% light ratings lots of documentation 00:02:24.910 --> 00:02:27.090 align:start position:0% light ratings lots of documentation again<00:02:25.870> this<00:02:26.290> is<00:02:26.440> something<00:02:26.560> that<00:02:26.650> canoes<00:02:26.950> were 00:02:27.090 --> 00:02:27.100 align:start position:0% again this is something that canoes were 00:02:27.100 --> 00:02:29.520 align:start position:0% again this is something that canoes were at<00:02:27.190> work<00:02:27.280> talking<00:02:27.940> about<00:02:28.300> bounties<00:02:28.630> anyone 00:02:29.520 --> 00:02:29.530 align:start position:0% at work talking about bounties anyone 00:02:29.530 --> 00:02:31.350 align:start position:0% at work talking about bounties anyone who<00:02:29.680> wants<00:02:29.890> to<00:02:29.980> help<00:02:30.100> there's<00:02:30.940> lots<00:02:31.090> of<00:02:31.180> little 00:02:31.350 --> 00:02:31.360 align:start position:0% who wants to help there's lots of little 00:02:31.360 --> 00:02:33.750 align:start position:0% who wants to help there's lots of little things<00:02:31.630> in<00:02:31.750> the<00:02:31.810> universe<00:02:31.959> that<00:02:32.140> people<00:02:32.760> that 00:02:33.750 --> 00:02:33.760 align:start position:0% things in the universe that people that 00:02:33.760 --> 00:02:35.370 align:start position:0% things in the universe that people that aren't<00:02:33.910> obvious<00:02:34.090> feel<00:02:34.450> about<00:02:34.690> ethereal<00:02:35.230> like 00:02:35.370 --> 00:02:35.380 align:start position:0% aren't obvious feel about ethereal like 00:02:35.380 --> 00:02:37.199 align:start position:0% aren't obvious feel about ethereal like they're<00:02:35.500> these<00:02:35.829> new<00:02:36.010> concepts<00:02:36.640> included<00:02:37.090> in 00:02:37.199 --> 00:02:37.209 align:start position:0% they're these new concepts included in 00:02:37.209 --> 00:02:40.470 align:start position:0% they're these new concepts included in the<00:02:37.269> documentation<00:02:38.370> also<00:02:39.370> as<00:02:39.820> much<00:02:40.060> earlier 00:02:40.470 --> 00:02:40.480 align:start position:0% the documentation also as much earlier 00:02:40.480 --> 00:02:42.800 align:start position:0% the documentation also as much earlier the<00:02:40.660> important<00:02:40.989> thing<00:02:41.140> is<00:02:41.530> I<00:02:41.829> see<00:02:42.070> licensing 00:02:42.800 --> 00:02:42.810 align:start position:0% the important thing is I see licensing 00:02:42.810 --> 00:02:44.789 align:start position:0% the important thing is I see licensing everything<00:02:43.810> including<00:02:44.230> all<00:02:44.350> dependencies 00:02:44.789 --> 00:02:44.799 align:start position:0% everything including all dependencies 00:02:44.799 --> 00:02:47.940 align:start position:0% everything including all dependencies 100%<00:02:45.549> RMIT<00:02:45.970> license<00:02:46.450> this<00:02:47.230> means<00:02:47.470> that<00:02:47.620> if<00:02:47.799> you 00:02:47.940 --> 00:02:47.950 align:start position:0% 100% RMIT license this means that if you 00:02:47.950 --> 00:02:49.470 align:start position:0% 100% RMIT license this means that if you are<00:02:48.010> some<00:02:48.310> private<00:02:48.730> corporation<00:02:49.209> you<00:02:49.329> can 00:02:49.470 --> 00:02:49.480 align:start position:0% are some private corporation you can 00:02:49.480 --> 00:02:50.900 align:start position:0% are some private corporation you can take<00:02:49.600> this<00:02:49.690> code<00:02:49.959> and<00:02:49.989> not<00:02:50.290> worry<00:02:50.560> about 00:02:50.900 --> 00:02:50.910 align:start position:0% take this code and not worry about 00:02:50.910 --> 00:02:53.130 align:start position:0% take this code and not worry about something<00:02:51.910> propping<00:02:52.269> up<00:02:52.329> in<00:02:52.420> the<00:02:52.480> future<00:02:52.810> and 00:02:53.130 --> 00:02:53.140 align:start position:0% something propping up in the future and 00:02:53.140 --> 00:02:54.569 align:start position:0% something propping up in the future and you<00:02:53.320> having<00:02:53.620> to<00:02:53.650> open<00:02:53.769> source<00:02:54.040> some 00:02:54.569 --> 00:02:54.579 align:start position:0% you having to open source some 00:02:54.579 --> 00:02:59.260 align:start position:0% you having to open source some fundamental<00:02:55.209> part<00:02:55.390> of<00:02:55.450> your<00:02:55.600> bills 00:02:59.260 --> 00:02:59.270 align:start position:0% 00:02:59.270 --> 00:03:06.700 align:start position:0% so<00:03:00.270> I<00:03:00.990> played<00:03:02.390> two<00:03:03.390> minutes<00:03:05.060> so<00:03:06.060> a<00:03:06.090> big 00:03:06.700 --> 00:03:06.710 align:start position:0% so I played two minutes so a big 00:03:06.710 --> 00:03:10.070 align:start position:0% so I played two minutes so a big distinction<00:03:07.710> between<00:03:07.950> ethers<00:03:08.640> and<00:03:09.080> most 00:03:10.070 --> 00:03:10.080 align:start position:0% distinction between ethers and most 00:03:10.080 --> 00:03:12.620 align:start position:0% distinction between ethers and most other<00:03:10.290> libraries<00:03:10.650> of<00:03:10.770> their<00:03:11.280> today<00:03:11.630> and 00:03:12.620 --> 00:03:12.630 align:start position:0% other libraries of their today and 00:03:12.630 --> 00:03:13.790 align:start position:0% other libraries of their today and there's<00:03:12.780> a<00:03:12.870> people<00:03:13.140> working<00:03:13.410> with<00:03:13.530> this<00:03:13.650> ball 00:03:13.790 --> 00:03:13.800 align:start position:0% there's a people working with this ball 00:03:13.800 --> 00:03:15.620 align:start position:0% there's a people working with this ball trying<00:03:14.040> to<00:03:14.160> help<00:03:14.250> promote<00:03:14.670> this<00:03:14.760> idea<00:03:14.880> that 00:03:15.620 --> 00:03:15.630 align:start position:0% trying to help promote this idea that 00:03:15.630 --> 00:03:17.180 align:start position:0% trying to help promote this idea that signers<00:03:16.170> and<00:03:16.410> providers<00:03:16.800> should<00:03:16.830> be 00:03:17.180 --> 00:03:17.190 align:start position:0% signers and providers should be 00:03:17.190 --> 00:03:20.090 align:start position:0% signers and providers should be fundamentally<00:03:18.030> different<00:03:18.240> creatures<00:03:19.100> your 00:03:20.090 --> 00:03:20.100 align:start position:0% fundamentally different creatures your 00:03:20.100 --> 00:03:21.710 align:start position:0% fundamentally different creatures your signer<00:03:20.370> has<00:03:20.700> a<00:03:20.730> private<00:03:21.120> key<00:03:21.270> in<00:03:21.390> it<00:03:21.480> it 00:03:21.710 --> 00:03:21.720 align:start position:0% signer has a private key in it it 00:03:21.720 --> 00:03:23.690 align:start position:0% signer has a private key in it it actually<00:03:22.020> science<00:03:22.650> messages<00:03:23.130> for<00:03:23.280> you<00:03:23.400> it 00:03:23.690 --> 00:03:23.700 align:start position:0% actually science messages for you it 00:03:23.700 --> 00:03:26.930 align:start position:0% actually science messages for you it does<00:03:23.910> things<00:03:24.350> providers<00:03:25.350> are<00:03:25.850> so<00:03:26.850> they 00:03:26.930 --> 00:03:26.940 align:start position:0% does things providers are so they 00:03:26.940 --> 00:03:28.700 align:start position:0% does things providers are so they provide<00:03:27.210> a<00:03:27.360> countless<00:03:27.780> information<00:03:28.560> they 00:03:28.700 --> 00:03:28.710 align:start position:0% provide a countless information they 00:03:28.710 --> 00:03:30.200 align:start position:0% provide a countless information they actually<00:03:29.130> let<00:03:29.280> you<00:03:29.340> ask<00:03:29.550> for<00:03:29.850> things<00:03:29.970> like 00:03:30.200 --> 00:03:30.210 align:start position:0% actually let you ask for things like 00:03:30.210 --> 00:03:32.060 align:start position:0% actually let you ask for things like what<00:03:30.900> is<00:03:31.020> the<00:03:31.110> current<00:03:31.380> block<00:03:31.470> number 00:03:32.060 --> 00:03:32.070 align:start position:0% what is the current block number 00:03:32.070 --> 00:03:34.430 align:start position:0% what is the current block number what<00:03:32.190> does<00:03:32.310> block<00:03:32.580> sent<00:03:32.940> me<00:03:33.000> by<00:03:33.180> a<00:03:33.210> book<00:03:33.510> like<00:03:33.750> a 00:03:34.430 --> 00:03:34.440 align:start position:0% what does block sent me by a book like a 00:03:34.440 --> 00:03:36.860 align:start position:0% what does block sent me by a book like a gas<00:03:34.890> price<00:03:35.250> they<00:03:36.000> let<00:03:36.180> you<00:03:36.240> sign<00:03:36.480> the<00:03:36.600> abroad 00:03:36.860 --> 00:03:36.870 align:start position:0% gas price they let you sign the abroad 00:03:36.870 --> 00:03:38.660 align:start position:0% gas price they let you sign the abroad transaction<00:03:37.500> but<00:03:37.590> a<00:03:37.650> Roth<00:03:37.800> transaction<00:03:38.430> of<00:03:38.550> it 00:03:38.660 --> 00:03:38.670 align:start position:0% transaction but a Roth transaction of it 00:03:38.670 --> 00:03:41.960 align:start position:0% transaction but a Roth transaction of it of<00:03:39.000> itself<00:03:39.300> is<00:03:39.630> kind<00:03:39.660> of<00:03:40.080> a<00:03:40.140> countless<00:03:40.970> you 00:03:41.960 --> 00:03:41.970 align:start position:0% of itself is kind of a countless you 00:03:41.970 --> 00:03:44.120 align:start position:0% of itself is kind of a countless you needed<00:03:42.390> something<00:03:42.690> else<00:03:43.050> with<00:03:43.590> the<00:03:43.800> account 00:03:44.120 --> 00:03:44.130 align:start position:0% needed something else with the account 00:03:44.130 --> 00:03:46.730 align:start position:0% needed something else with the account to<00:03:44.430> do<00:03:44.520> that<00:03:44.670> part<00:03:45.320> so<00:03:46.320> there's<00:03:46.560> a<00:03:46.590> big 00:03:46.730 --> 00:03:46.740 align:start position:0% to do that part so there's a big 00:03:46.740 --> 00:03:47.750 align:start position:0% to do that part so there's a big distinction<00:03:47.040> between<00:03:47.220> providers<00:03:47.730> and 00:03:47.750 --> 00:03:47.760 align:start position:0% distinction between providers and 00:03:47.760 --> 00:03:48.980 align:start position:0% distinction between providers and signers<00:03:48.209> and<00:03:48.240> so<00:03:48.480> if<00:03:48.570> you're<00:03:48.660> coming<00:03:48.810> from 00:03:48.980 --> 00:03:48.990 align:start position:0% signers and so if you're coming from 00:03:48.990 --> 00:03:50.900 align:start position:0% signers and so if you're coming from about<00:03:49.200> three<00:03:49.440> worlds<00:03:49.860> this<00:03:50.430> will<00:03:50.610> be<00:03:50.700> one<00:03:50.820> to 00:03:50.900 --> 00:03:50.910 align:start position:0% about three worlds this will be one to 00:03:50.910 --> 00:03:51.890 align:start position:0% about three worlds this will be one to take<00:03:51.090> paying<00:03:51.360> points 00:03:51.890 --> 00:03:51.900 align:start position:0% take paying points 00:03:51.900 --> 00:03:53.840 align:start position:0% take paying points feel<00:03:52.260> free<00:03:52.350> to<00:03:52.440> bug<00:03:52.590> me<00:03:52.709> afterwards<00:03:53.070> or<00:03:53.340> online 00:03:53.840 --> 00:03:53.850 align:start position:0% feel free to bug me afterwards or online 00:03:53.850 --> 00:03:55.760 align:start position:0% feel free to bug me afterwards or online or<00:03:53.910> anywhere<00:03:54.240> to<00:03:54.720> learn<00:03:55.050> more<00:03:55.230> about<00:03:55.290> this<00:03:55.530> and 00:03:55.760 --> 00:03:55.770 align:start position:0% or anywhere to learn more about this and 00:03:55.770 --> 00:03:58.130 align:start position:0% or anywhere to learn more about this and my<00:03:56.340> legs<00:03:56.550> strive<00:03:57.150> to<00:03:57.570> make<00:03:57.750> every<00:03:57.900> one 00:03:58.130 --> 00:03:58.140 align:start position:0% my legs strive to make every one 00:03:58.140 --> 00:04:02.540 align:start position:0% my legs strive to make every one separate<00:03:58.530> these<00:03:58.650> things<00:04:00.050> so<00:04:01.130> basic<00:04:02.130> providers 00:04:02.540 --> 00:04:02.550 align:start position:0% separate these things so basic providers 00:04:02.550 --> 00:04:04.150 align:start position:0% separate these things so basic providers your<00:04:02.730> pricing<00:04:03.000> there<00:04:03.090> with<00:04:03.209> Lisa<00:04:03.390> JSON<00:04:03.660> RPC 00:04:04.150 --> 00:04:04.160 align:start position:0% your pricing there with Lisa JSON RPC 00:04:04.160 --> 00:04:08.210 align:start position:0% your pricing there with Lisa JSON RPC IPC<00:04:05.160> provider<00:04:05.519> which<00:04:06.060> is<00:04:07.010> actually<00:04:08.010> just<00:04:08.040> a 00:04:08.210 --> 00:04:08.220 align:start position:0% IPC provider which is actually just a 00:04:08.220 --> 00:04:11.150 align:start position:0% IPC provider which is actually just a starting<00:04:08.489> to<00:04:08.550> see<00:04:08.670> over<00:04:08.970> IPC<00:04:09.769> final<00:04:10.769> community 00:04:11.150 --> 00:04:11.160 align:start position:0% starting to see over IPC final community 00:04:11.160 --> 00:04:13.310 align:start position:0% starting to see over IPC final community or<00:04:11.340> the<00:04:11.459> vendors<00:04:11.940> the<00:04:12.150> web<00:04:12.330> view<00:04:12.540> web<00:04:13.050> three 00:04:13.310 --> 00:04:13.320 align:start position:0% or the vendors the web view web three 00:04:13.320 --> 00:04:15.590 align:start position:0% or the vendors the web view web three providers<00:04:13.620> purpose<00:04:14.130> is<00:04:14.370> that<00:04:14.550> you<00:04:14.670> can<00:04:14.880> if<00:04:15.420> you 00:04:15.590 --> 00:04:15.600 align:start position:0% providers purpose is that you can if you 00:04:15.600 --> 00:04:17.330 align:start position:0% providers purpose is that you can if you currently<00:04:15.870> have<00:04:16.080> a<00:04:16.290> web<00:04:16.590> free<00:04:16.799> application 00:04:17.330 --> 00:04:17.340 align:start position:0% currently have a web free application 00:04:17.340 --> 00:04:18.800 align:start position:0% currently have a web free application you<00:04:17.519> can<00:04:17.760> take<00:04:17.970> your<00:04:18.120> wealth<00:04:18.330> your<00:04:18.450> provider 00:04:18.800 --> 00:04:18.810 align:start position:0% you can take your wealth your provider 00:04:18.810 --> 00:04:21.170 align:start position:0% you can take your wealth your provider and<00:04:19.140> jam<00:04:19.769> it<00:04:19.799> into<00:04:20.100> that<00:04:20.310> provider<00:04:20.669> and<00:04:20.970> it 00:04:21.170 --> 00:04:21.180 align:start position:0% and jam it into that provider and it 00:04:21.180 --> 00:04:23.390 align:start position:0% and jam it into that provider and it builds<00:04:21.660> a<00:04:21.840> features<00:04:22.320> provider<00:04:22.770> out<00:04:22.980> of<00:04:23.100> it<00:04:23.190> so 00:04:23.390 --> 00:04:23.400 align:start position:0% builds a features provider out of it so 00:04:23.400 --> 00:04:26.600 align:start position:0% builds a features provider out of it so it<00:04:23.460> becomes<00:04:23.520> features<00:04:24.090> compatible<00:04:25.610> there's 00:04:26.600 --> 00:04:26.610 align:start position:0% it becomes features compatible there's 00:04:26.610 --> 00:04:27.530 align:start position:0% it becomes features compatible there's also<00:04:26.730> one<00:04:26.940> I'm<00:04:27.030> going<00:04:27.120> to<00:04:27.180> explain<00:04:27.390> the 00:04:27.530 --> 00:04:27.540 align:start position:0% also one I'm going to explain the 00:04:27.540 --> 00:04:29.270 align:start position:0% also one I'm going to explain the fallback<00:04:27.720> writer<00:04:28.140> a<00:04:28.200> second<00:04:28.620> the<00:04:28.890> third-party 00:04:29.270 --> 00:04:29.280 align:start position:0% fallback writer a second the third-party 00:04:29.280 --> 00:04:31.040 align:start position:0% fallback writer a second the third-party providers<00:04:30.240> so<00:04:30.360> there's<00:04:30.480> like<00:04:30.540> currently 00:04:31.040 --> 00:04:31.050 align:start position:0% providers so there's like currently 00:04:31.050 --> 00:04:32.780 align:start position:0% providers so there's like currently either<00:04:31.260> skin<00:04:31.530> here<00:04:31.919> announcement<00:04:32.430> Alfie 00:04:32.780 --> 00:04:32.790 align:start position:0% either skin here announcement Alfie 00:04:32.790 --> 00:04:34.820 align:start position:0% either skin here announcement Alfie CloudFlare<00:04:33.780> there's<00:04:34.080> the<00:04:34.169> two<00:04:34.380> other<00:04:34.530> sort<00:04:34.800> of 00:04:34.820 --> 00:04:34.830 align:start position:0% CloudFlare there's the two other sort of 00:04:34.830 --> 00:04:36.640 align:start position:0% CloudFlare there's the two other sort of most<00:04:35.220> recent<00:04:35.340> stuff<00:04:35.700> that<00:04:35.820> wants<00:04:36.000> to<00:04:36.030> be<00:04:36.330> added 00:04:36.640 --> 00:04:36.650 align:start position:0% most recent stuff that wants to be added 00:04:36.650 --> 00:04:39.170 align:start position:0% most recent stuff that wants to be added so<00:04:37.650> many<00:04:37.770> would<00:04:37.980> like<00:04:38.100> the<00:04:38.250> default<00:04:38.640> providers 00:04:39.170 --> 00:04:39.180 align:start position:0% so many would like the default providers 00:04:39.180 --> 00:04:41.060 align:start position:0% so many would like the default providers so<00:04:39.390> the<00:04:39.570> default<00:04:39.720> provider<00:04:40.200> is<00:04:40.470> a<00:04:40.500> system<00:04:40.950> that 00:04:41.060 --> 00:04:41.070 align:start position:0% so the default provider is a system that 00:04:41.070 --> 00:04:43.550 align:start position:0% so the default provider is a system that might<00:04:41.190> consider<00:04:41.520> also<00:04:41.790> makes<00:04:42.090> a<00:04:42.300> lot<00:04:42.570> of<00:04:42.840> my 00:04:43.550 --> 00:04:43.560 align:start position:0% might consider also makes a lot of my 00:04:43.560 --> 00:04:45.390 align:start position:0% might consider also makes a lot of my leg<00:04:43.740> I'm<00:04:43.860> talking<00:04:44.160> too<00:04:44.250> fast<00:04:44.280> please<00:04:44.790> I'm<00:04:45.000> just 00:04:45.390 --> 00:04:45.400 align:start position:0% leg I'm talking too fast please I'm just 00:04:45.400 --> 00:04:49.920 align:start position:0% leg I'm talking too fast please I'm just I<00:04:45.510> get<00:04:46.510> carried<00:04:46.630> away<00:04:46.800> oh<00:04:48.510> yes 00:04:49.920 --> 00:04:49.930 align:start position:0% I get carried away oh yes 00:04:49.930 --> 00:04:52.260 align:start position:0% I get carried away oh yes the<00:04:50.230> default<00:04:50.500> provider<00:04:50.740> basically<00:04:51.490> this<00:04:52.090> is 00:04:52.260 --> 00:04:52.270 align:start position:0% the default provider basically this is 00:04:52.270 --> 00:04:54.450 align:start position:0% the default provider basically this is the<00:04:52.480> type<00:04:52.690> of<00:04:52.720> providers<00:04:53.260> like<00:04:53.440> to<00:04:53.560> see<00:04:53.740> more 00:04:54.450 --> 00:04:54.460 align:start position:0% the type of providers like to see more 00:04:54.460 --> 00:04:58.950 align:start position:0% the type of providers like to see more important<00:04:55.000> as<00:04:55.090> well<00:04:55.590> the<00:04:56.590> way<00:04:57.780> there's<00:04:58.780> no<00:04:58.840> key 00:04:58.950 --> 00:04:58.960 align:start position:0% important as well the way there's no key 00:04:58.960 --> 00:05:02.909 align:start position:0% important as well the way there's no key no<00:04:59.669> see<00:05:00.699> maybe<00:05:01.240> so<00:05:01.900> basically<00:05:02.229> the<00:05:02.380> AF<00:05:02.590> default 00:05:02.909 --> 00:05:02.919 align:start position:0% no see maybe so basically the AF default 00:05:02.919 --> 00:05:07.379 align:start position:0% no see maybe so basically the AF default provider<00:05:03.190> is<00:05:03.460> so<00:05:04.060> it's<00:05:04.720> a<00:05:05.970> instance<00:05:06.970> of<00:05:07.150> a 00:05:07.379 --> 00:05:07.389 align:start position:0% provider is so it's a instance of a 00:05:07.389 --> 00:05:09.000 align:start position:0% provider is so it's a instance of a fallback<00:05:07.660> provider<00:05:08.229> so<00:05:08.590> if<00:05:08.680> you<00:05:08.770> for<00:05:08.979> example 00:05:09.000 --> 00:05:09.010 align:start position:0% fallback provider so if you for example 00:05:09.010 --> 00:05:10.379 align:start position:0% fallback provider so if you for example create<00:05:09.490> the<00:05:09.580> default<00:05:09.910> provider<00:05:10.180> for 00:05:10.379 --> 00:05:10.389 align:start position:0% create the default provider for 00:05:10.389 --> 00:05:13.200 align:start position:0% create the default provider for homestead<00:05:10.900> it'll<00:05:11.800> be<00:05:12.220> backed<00:05:12.460> by<00:05:12.610> either<00:05:12.910> scan 00:05:13.200 --> 00:05:13.210 align:start position:0% homestead it'll be backed by either scan 00:05:13.210 --> 00:05:15.120 align:start position:0% homestead it'll be backed by either scan in<00:05:13.360> here<00:05:13.600> at<00:05:13.750> cloud<00:05:13.960> Smith<00:05:14.320> or<00:05:14.560> clouds<00:05:14.860> layer 00:05:15.120 --> 00:05:15.130 align:start position:0% in here at cloud Smith or clouds layer 00:05:15.130 --> 00:05:17.400 align:start position:0% in here at cloud Smith or clouds layer don't<00:05:15.460> submit<00:05:15.729> alchemy<00:05:16.360> and<00:05:16.630> it<00:05:17.260> will 00:05:17.400 --> 00:05:17.410 align:start position:0% don't submit alchemy and it will 00:05:17.410 --> 00:05:19.080 align:start position:0% don't submit alchemy and it will actually<00:05:17.620> keep<00:05:18.040> a<00:05:18.100> connection<00:05:18.340> to<00:05:18.610> all<00:05:18.790> five 00:05:19.080 --> 00:05:19.090 align:start position:0% actually keep a connection to all five 00:05:19.090 --> 00:05:25.230 align:start position:0% actually keep a connection to all five of<00:05:19.120> these<00:05:22.440> and<00:05:23.440> when<00:05:24.130> you<00:05:24.250> make<00:05:24.430> a<00:05:24.460> request<00:05:24.760> for 00:05:25.230 --> 00:05:25.240 align:start position:0% of these and when you make a request for 00:05:25.240 --> 00:05:27.510 align:start position:0% of these and when you make a request for a<00:05:25.750> state<00:05:26.169> of<00:05:26.229> the<00:05:26.320> current<00:05:26.410> block<00:05:26.680> number<00:05:27.010> it 00:05:27.510 --> 00:05:27.520 align:start position:0% a state of the current block number it 00:05:27.520 --> 00:05:28.800 align:start position:0% a state of the current block number it will<00:05:27.760> worry 00:05:28.800 --> 00:05:28.810 align:start position:0% will worry 00:05:28.810 --> 00:05:30.960 align:start position:0% will worry two<00:05:29.080> of<00:05:29.229> them<00:05:29.320> are<00:05:29.380> random<00:05:29.710> and<00:05:30.130> when<00:05:30.790> it<00:05:30.910> gets 00:05:30.960 --> 00:05:30.970 align:start position:0% two of them are random and when it gets 00:05:30.970 --> 00:05:32.700 align:start position:0% two of them are random and when it gets the<00:05:31.120> response<00:05:31.510> it<00:05:31.810> will<00:05:31.870> decide<00:05:32.169> are<00:05:32.530> these 00:05:32.700 --> 00:05:32.710 align:start position:0% the response it will decide are these 00:05:32.710 --> 00:05:34.620 align:start position:0% the response it will decide are these that<00:05:32.919> if<00:05:33.040> they<00:05:33.340> both<00:05:33.520> say<00:05:33.790> block<00:05:34.030> 1<00:05:34.300> million 00:05:34.620 --> 00:05:34.630 align:start position:0% that if they both say block 1 million 00:05:34.630 --> 00:05:36.150 align:start position:0% that if they both say block 1 million you're<00:05:34.810> good<00:05:34.930> to<00:05:34.990> go<00:05:35.050> returns<00:05:35.560> 1<00:05:35.740> million<00:05:36.010> to 00:05:36.150 --> 00:05:36.160 align:start position:0% you're good to go returns 1 million to 00:05:36.160 --> 00:05:38.760 align:start position:0% you're good to go returns 1 million to you<00:05:36.340> the<00:05:36.610> user<00:05:36.789> and<00:05:37.570> you're<00:05:37.690> done<00:05:37.840> if<00:05:38.470> there's 00:05:38.760 --> 00:05:38.770 align:start position:0% you the user and you're done if there's 00:05:38.770 --> 00:05:40.290 align:start position:0% you the user and you're done if there's a<00:05:38.830> discrepancy<00:05:39.070> between<00:05:39.460> them<00:05:39.789> it'll<00:05:39.970> pour 00:05:40.290 --> 00:05:40.300 align:start position:0% a discrepancy between them it'll pour 00:05:40.300 --> 00:05:41.909 align:start position:0% a discrepancy between them it'll pour you<00:05:40.389> the<00:05:40.510> third<00:05:40.750> and<00:05:41.020> then<00:05:41.110> a<00:05:41.200> fourth<00:05:41.229> until 00:05:41.909 --> 00:05:41.919 align:start position:0% you the third and then a fourth until 00:05:41.919 --> 00:05:43.800 align:start position:0% you the third and then a fourth until there's<00:05:42.070> a<00:05:42.130> consensus<00:05:42.729> across<00:05:42.910> the<00:05:43.270> backends 00:05:43.800 --> 00:05:43.810 align:start position:0% there's a consensus across the backends 00:05:43.810 --> 00:05:47.909 align:start position:0% there's a consensus across the backends so<00:05:44.380> this<00:05:44.740> being<00:05:44.919> said<00:05:46.050> the<00:05:47.050> classic<00:05:47.410> example<00:05:47.830> I 00:05:47.909 --> 00:05:47.919 align:start position:0% so this being said the classic example I 00:05:47.919 --> 00:05:49.379 align:start position:0% so this being said the classic example I worry<00:05:48.190> about<00:05:48.280> in<00:05:48.520> terms<00:05:48.699> of<00:05:48.820> the<00:05:48.880> developers 00:05:49.379 --> 00:05:49.389 align:start position:0% worry about in terms of the developers 00:05:49.389 --> 00:05:52.620 align:start position:0% worry about in terms of the developers Republic<00:05:50.080> rushman<00:05:50.320> a<00:05:51.120> classic<00:05:52.120> example<00:05:52.210> I 00:05:52.620 --> 00:05:52.630 align:start position:0% Republic rushman a classic example I 00:05:52.630 --> 00:05:53.640 align:start position:0% Republic rushman a classic example I worry<00:05:52.840> about<00:05:52.990> in<00:05:53.110> terms<00:05:53.139> of<00:05:53.320> an<00:05:53.440> attack 00:05:53.640 --> 00:05:53.650 align:start position:0% worry about in terms of an attack 00:05:53.650 --> 00:05:56.670 align:start position:0% worry about in terms of an attack vectors<00:05:54.070> so<00:05:54.910> people<00:05:55.270> who<00:05:55.419> are<00:05:55.450> protein<00:05:55.900> s<00:05:56.110> you 00:05:56.670 --> 00:05:56.680 align:start position:0% vectors so people who are protein s you 00:05:56.680 --> 00:05:59.490 align:start position:0% vectors so people who are protein s you can<00:05:56.919> ask<00:05:57.130> you<00:05:57.850> know<00:05:57.880> what<00:05:58.389> address<00:05:58.660> should<00:05:59.410> I 00:05:59.490 --> 00:05:59.500 align:start position:0% can ask you know what address should I 00:05:59.500 --> 00:06:02.250 align:start position:0% can ask you know what address should I send<00:05:59.770> this<00:05:59.919> ether<00:06:00.220> to<00:06:00.370> for<00:06:00.700> Rick<00:06:00.849> Moonen 00:06:02.250 --> 00:06:02.260 align:start position:0% send this ether to for Rick Moonen 00:06:02.260 --> 00:06:04.710 align:start position:0% send this ether to for Rick Moonen if<00:06:02.560> I<00:06:02.740> was<00:06:02.889> an<00:06:02.950> attacker<00:06:03.220> I<00:06:03.400> would<00:06:03.729> just<00:06:03.849> hijack 00:06:04.710 --> 00:06:04.720 align:start position:0% if I was an attacker I would just hijack 00:06:04.720 --> 00:06:06.960 align:start position:0% if I was an attacker I would just hijack athira<00:06:05.139> and<00:06:05.440> make<00:06:05.560> it<00:06:05.680> always<00:06:05.950> return<00:06:06.310> the 00:06:06.960 --> 00:06:06.970 align:start position:0% athira and make it always return the 00:06:06.970 --> 00:06:08.850 align:start position:0% athira and make it always return the attackers<00:06:07.419> address<00:06:07.780> every<00:06:08.139> time<00:06:08.380> you<00:06:08.530> sent<00:06:08.770> me 00:06:08.850 --> 00:06:08.860 align:start position:0% attackers address every time you sent me 00:06:08.860 --> 00:06:11.400 align:start position:0% attackers address every time you sent me through<00:06:08.979> anyone<00:06:09.430> it<00:06:09.700> goes<00:06:09.849> to<00:06:10.000> that<00:06:10.120> person<00:06:10.510> so 00:06:11.400 --> 00:06:11.410 align:start position:0% through anyone it goes to that person so 00:06:11.410 --> 00:06:12.990 align:start position:0% through anyone it goes to that person so this<00:06:11.560> means<00:06:11.830> you<00:06:11.979> have<00:06:12.190> to<00:06:12.280> compromise 00:06:12.990 --> 00:06:13.000 align:start position:0% this means you have to compromise 00:06:13.000 --> 00:06:17.029 align:start position:0% this means you have to compromise two<00:06:13.300> of<00:06:13.630> these<00:06:13.750> randoms<00:06:14.229> sources<00:06:15.160> to<00:06:15.910> kind<00:06:16.150> of 00:06:17.029 --> 00:06:17.039 align:start position:0% two of these randoms sources to kind of 00:06:17.039 --> 00:06:19.110 align:start position:0% two of these randoms sources to kind of compromise<00:06:18.039> that<00:06:18.070> system<00:06:18.460> as<00:06:18.520> a<00:06:18.550> whole<00:06:18.639> if 00:06:19.110 --> 00:06:19.120 align:start position:0% compromise that system as a whole if 00:06:19.120 --> 00:06:21.810 align:start position:0% compromise that system as a whole if that<00:06:19.479> makes<00:06:19.690> sense 00:06:21.810 --> 00:06:21.820 align:start position:0% 00:06:21.820 --> 00:06:23.310 align:start position:0% long<00:06:22.300> story<00:06:22.450> short<00:06:22.539> one<00:06:22.810> finds<00:06:22.990> days<00:06:23.139> they 00:06:23.310 --> 00:06:23.320 align:start position:0% long story short one finds days they 00:06:23.320 --> 00:06:24.390 align:start position:0% long story short one finds days they send<00:06:23.530> these<00:06:23.650> a<00:06:23.680> lot<00:06:23.860> safer<00:06:24.099> to<00:06:24.280> health 00:06:24.390 --> 00:06:24.400 align:start position:0% send these a lot safer to health 00:06:24.400 --> 00:06:26.159 align:start position:0% send these a lot safer to health providers<00:06:24.849> in<00:06:25.000> this<00:06:25.090> way<00:06:25.300> to<00:06:25.690> basically<00:06:25.990> back 00:06:26.159 --> 00:06:26.169 align:start position:0% providers in this way to basically back 00:06:26.169 --> 00:06:28.409 align:start position:0% providers in this way to basically back up<00:06:26.320> by<00:06:26.410> local<00:06:26.680> sources<00:06:27.039> if<00:06:27.669> you<00:06:27.910> run<00:06:28.150> your<00:06:28.270> own 00:06:28.409 --> 00:06:28.419 align:start position:0% up by local sources if you run your own 00:06:28.419 --> 00:06:30.659 align:start position:0% up by local sources if you run your own infrastructure<00:06:28.919> also<00:06:29.919> if<00:06:30.130> I<00:06:30.220> want<00:06:30.460> to<00:06:30.520> do<00:06:30.580> this 00:06:30.659 --> 00:06:30.669 align:start position:0% infrastructure also if I want to do this 00:06:30.669 --> 00:06:34.950 align:start position:0% infrastructure also if I want to do this you<00:06:30.910> can<00:06:31.090> have<00:06:31.270> your<00:06:32.020> own<00:06:32.260> note<00:06:33.070> your<00:06:33.370> own<00:06:33.960> if 00:06:34.950 --> 00:06:34.960 align:start position:0% you can have your own note your own if 00:06:34.960 --> 00:06:39.240 align:start position:0% you can have your own note your own if your<00:06:35.289> knows<00:06:35.440> a<00:06:35.740> higher<00:06:36.550> priority<00:06:36.910> so<00:06:38.099> you<00:06:39.099> can 00:06:39.240 --> 00:06:39.250 align:start position:0% your knows a higher priority so you can 00:06:39.250 --> 00:06:40.710 align:start position:0% your knows a higher priority so you can get<00:06:39.340> like<00:06:39.460> this<00:06:39.610> a<00:06:39.729> link<00:06:40.000> of<00:06:40.150> three<00:06:40.450> now<00:06:40.660> that 00:06:40.710 --> 00:06:40.720 align:start position:0% get like this a link of three now that 00:06:40.720 --> 00:06:42.480 align:start position:0% get like this a link of three now that means<00:06:40.900> that<00:06:40.960> yours<00:06:41.260> is<00:06:41.380> far<00:06:41.830> more<00:06:42.099> likely<00:06:42.250> to 00:06:42.480 --> 00:06:42.490 align:start position:0% means that yours is far more likely to 00:06:42.490 --> 00:06:46.710 align:start position:0% means that yours is far more likely to matter<00:06:43.270> when<00:06:43.720> it<00:06:43.810> comes<00:06:43.840> to<00:06:44.200> deciding<00:06:45.720> given 00:06:46.710 --> 00:06:46.720 align:start position:0% matter when it comes to deciding given 00:06:46.720 --> 00:06:49.210 align:start position:0% matter when it comes to deciding given this<00:06:47.110> call<00:06:47.560> against<00:06:48.099> the<00:06:48.160> blockchain<00:06:48.700> here's 00:06:49.210 --> 00:06:49.220 align:start position:0% this call against the blockchain here's 00:06:49.220 --> 00:06:51.430 align:start position:0% this call against the blockchain here's response<00:06:49.550> it's<00:06:50.360> going<00:06:50.570> to<00:06:50.690> pour<00:06:50.900> in<00:06:51.050> multiple 00:06:51.430 --> 00:06:51.440 align:start position:0% response it's going to pour in multiple 00:06:51.440 --> 00:06:53.140 align:start position:0% response it's going to pour in multiple sources<00:06:51.770> it's<00:06:52.070> going<00:06:52.190> to<00:06:52.250> get<00:06:52.340> more<00:06:52.520> close<00:06:52.910> to 00:06:53.140 --> 00:06:53.150 align:start position:0% sources it's going to get more close to 00:06:53.150 --> 00:06:57.520 align:start position:0% sources it's going to get more close to your<00:06:53.450> ears<00:06:53.800> and<00:06:54.820> Cory<00:06:55.820> first<00:06:56.200> if<00:06:57.200> there's<00:06:57.470> a 00:06:57.520 --> 00:06:57.530 align:start position:0% your ears and Cory first if there's a 00:06:57.530 --> 00:06:58.990 align:start position:0% your ears and Cory first if there's a discrepancy<00:06:57.800> which<00:06:58.250> might<00:06:58.490> happen<00:06:58.700> to<00:06:58.880> your 00:06:58.990 --> 00:06:59.000 align:start position:0% discrepancy which might happen to your 00:06:59.000 --> 00:07:00.160 align:start position:0% discrepancy which might happen to your own<00:06:59.120> infrastructure<00:06:59.480> you<00:06:59.780> might<00:06:59.990> have<00:07:00.080> been 00:07:00.160 --> 00:07:00.170 align:start position:0% own infrastructure you might have been 00:07:00.170 --> 00:07:02.980 align:start position:0% own infrastructure you might have been hacked<00:07:00.410> or<00:07:00.680> I<00:07:01.400> like<00:07:01.880> to<00:07:02.030> hear<00:07:02.360> who's<00:07:02.660> used<00:07:02.900> to 00:07:02.980 --> 00:07:02.990 align:start position:0% hacked or I like to hear who's used to 00:07:02.990 --> 00:07:04.990 align:start position:0% hacked or I like to hear who's used to running<00:07:03.230> their<00:07:03.470> own<00:07:03.500> nodes<00:07:03.890> will<00:07:04.640> know<00:07:04.790> that 00:07:04.990 --> 00:07:05.000 align:start position:0% running their own nodes will know that 00:07:05.000 --> 00:07:07.660 align:start position:0% running their own nodes will know that sometimes<00:07:05.180> they<00:07:05.450> get<00:07:05.900> out<00:07:06.050> of<00:07:06.170> sync<00:07:06.380> and<00:07:07.250> when 00:07:07.660 --> 00:07:07.670 align:start position:0% sometimes they get out of sync and when 00:07:07.670 --> 00:07:09.340 align:start position:0% sometimes they get out of sync and when they<00:07:07.760> do<00:07:07.820> that<00:07:08.030> it's<00:07:08.360> nice<00:07:08.540> that<00:07:08.570> at<00:07:08.960> least<00:07:09.110> in 00:07:09.340 --> 00:07:09.350 align:start position:0% they do that it's nice that at least in 00:07:09.350 --> 00:07:11.710 align:start position:0% they do that it's nice that at least in fear<00:07:09.710> will<00:07:09.890> pick<00:07:10.070> up<00:07:10.190> the<00:07:10.370> slack<00:07:10.670> for<00:07:10.970> you<00:07:11.120> or 00:07:11.710 --> 00:07:11.720 align:start position:0% fear will pick up the slack for you or 00:07:11.720 --> 00:07:13.690 align:start position:0% fear will pick up the slack for you or the<00:07:11.900> fears<00:07:12.200> of<00:07:12.320> the<00:07:12.440> sync<00:07:12.680> your<00:07:13.190> node<00:07:13.490> might 00:07:13.690 --> 00:07:13.700 align:start position:0% the fears of the sync your node might 00:07:13.700 --> 00:07:14.920 align:start position:0% the fears of the sync your node might work<00:07:13.850> together<00:07:14.000> who<00:07:14.240> eat<00:07:14.390> their<00:07:14.540> skin<00:07:14.750> to 00:07:14.920 --> 00:07:14.930 align:start position:0% work together who eat their skin to 00:07:14.930 --> 00:07:17.440 align:start position:0% work together who eat their skin to provide<00:07:15.140> a<00:07:15.200> more<00:07:15.380> reliable<00:07:15.410> answer<00:07:16.090> so<00:07:17.090> long 00:07:17.440 --> 00:07:17.450 align:start position:0% provide a more reliable answer so long 00:07:17.450 --> 00:07:18.640 align:start position:0% provide a more reliable answer so long story<00:07:17.660> short<00:07:17.870> it's<00:07:17.990> very<00:07:18.140> easy<00:07:18.320> to<00:07:18.440> connect 00:07:18.640 --> 00:07:18.650 align:start position:0% story short it's very easy to connect 00:07:18.650 --> 00:07:19.780 align:start position:0% story short it's very easy to connect you<00:07:18.770> basically<00:07:19.010> just<00:07:19.100> a<00:07:19.250> comms<00:07:19.490> provider 00:07:19.780 --> 00:07:19.790 align:start position:0% you basically just a comms provider 00:07:19.790 --> 00:07:21.670 align:start position:0% you basically just a comms provider equals<00:07:20.150> easier<00:07:20.540> setup<00:07:21.050> default<00:07:21.260> provider 00:07:21.670 --> 00:07:21.680 align:start position:0% equals easier setup default provider 00:07:21.680 --> 00:07:23.500 align:start position:0% equals easier setup default provider you're<00:07:22.340> not<00:07:22.460> connected<00:07:22.790> to<00:07:22.820> homestead<00:07:23.180> and 00:07:23.500 --> 00:07:23.510 align:start position:0% you're not connected to homestead and 00:07:23.510 --> 00:07:24.970 align:start position:0% you're not connected to homestead and you're<00:07:23.840> going<00:07:23.960> to<00:07:23.990> for<00:07:24.560> whatever<00:07:24.710> you<00:07:24.860> need<00:07:24.890> to 00:07:24.970 --> 00:07:24.980 align:start position:0% you're going to for whatever you need to 00:07:24.980 --> 00:07:27.070 align:start position:0% you're going to for whatever you need to do<00:07:25.190> it<00:07:25.970> obviously<00:07:26.060> supports<00:07:26.660> all<00:07:26.810> the<00:07:26.900> major 00:07:27.070 --> 00:07:27.080 align:start position:0% do it obviously supports all the major 00:07:27.080 --> 00:07:30.000 align:start position:0% do it obviously supports all the major networks<00:07:27.260> they<00:07:27.680> can<00:07:27.800> be<00:07:27.890> Ralston<00:07:28.370> before<00:07:29.150> we 00:07:30.000 --> 00:07:30.010 align:start position:0% networks they can be Ralston before we 00:07:30.010 --> 00:07:38.950 align:start position:0% networks they can be Ralston before we go<00:07:31.010> in<00:07:31.780> okay<00:07:35.860> so<00:07:36.860> signers<00:07:37.600> not<00:07:38.600> really<00:07:38.780> love 00:07:38.950 --> 00:07:38.960 align:start position:0% go in okay so signers not really love 00:07:38.960 --> 00:07:42.220 align:start position:0% go in okay so signers not really love the<00:07:39.080> same<00:07:39.290> so<00:07:39.680> this<00:07:40.040> is<00:07:40.190> the<00:07:40.340> other<00:07:40.720> dual<00:07:41.720> to 00:07:42.220 --> 00:07:42.230 align:start position:0% the same so this is the other dual to 00:07:42.230 --> 00:07:43.930 align:start position:0% the same so this is the other dual to the<00:07:42.350> provider<00:07:42.680> this<00:07:43.010> action<00:07:43.460> is<00:07:43.550> a<00:07:43.610> private 00:07:43.930 --> 00:07:43.940 align:start position:0% the provider this action is a private 00:07:43.940 --> 00:07:47.620 align:start position:0% the provider this action is a private key<00:07:44.060> in<00:07:44.150> it<00:07:44.270> it's<00:07:44.960> it's<00:07:45.940> apparently<00:07:46.940> isolated 00:07:47.620 --> 00:07:47.630 align:start position:0% key in it it's it's apparently isolated 00:07:47.630 --> 00:07:48.400 align:start position:0% key in it it's it's apparently isolated theory 00:07:48.400 --> 00:07:48.410 align:start position:0% theory 00:07:48.410 --> 00:07:49.870 align:start position:0% theory unfortunately<00:07:49.070> a<00:07:49.100> lot<00:07:49.130> people<00:07:49.340> today<00:07:49.580> miss 00:07:49.870 --> 00:07:49.880 align:start position:0% unfortunately a lot people today miss 00:07:49.880 --> 00:07:51.820 align:start position:0% unfortunately a lot people today miss things<00:07:50.090> like<00:07:50.210> death<00:07:50.450> which<00:07:51.080> conflate<00:07:51.620> your 00:07:51.820 --> 00:07:51.830 align:start position:0% things like death which conflate your 00:07:51.830 --> 00:07:53.740 align:start position:0% things like death which conflate your science<00:07:52.160> fire<00:07:52.400> but<00:07:53.120> in<00:07:53.240> the<00:07:53.300> future<00:07:53.480> I'd<00:07:53.630> like 00:07:53.740 --> 00:07:53.750 align:start position:0% science fire but in the future I'd like 00:07:53.750 --> 00:07:55.330 align:start position:0% science fire but in the future I'd like to<00:07:53.810> see<00:07:53.960> more<00:07:54.140> people<00:07:54.320> move<00:07:54.740> towards<00:07:55.100> the 00:07:55.330 --> 00:07:55.340 align:start position:0% to see more people move towards the 00:07:55.340 --> 00:07:57.010 align:start position:0% to see more people move towards the cider<00:07:55.610> this<00:07:55.910> could<00:07:56.090> be<00:07:56.180> a<00:07:56.210> lighter<00:07:56.510> nano<00:07:56.750> cider 00:07:57.010 --> 00:07:57.020 align:start position:0% cider this could be a lighter nano cider 00:07:57.020 --> 00:07:59.260 align:start position:0% cider this could be a lighter nano cider which<00:07:57.770> is<00:07:57.890> in<00:07:58.040> no<00:07:58.190> way<00:07:58.370> whatsoever<00:07:58.550> connected 00:07:59.260 --> 00:07:59.270 align:start position:0% which is in no way whatsoever connected 00:07:59.270 --> 00:08:01.750 align:start position:0% which is in no way whatsoever connected to<00:07:59.390> your<00:07:59.630> provider<00:08:00.370> providers<00:08:01.370> consider<00:08:01.700> a 00:08:01.750 --> 00:08:01.760 align:start position:0% to your provider providers consider a 00:08:01.760 --> 00:08:03.820 align:start position:0% to your provider providers consider a place<00:08:02.060> where<00:08:02.300> as<00:08:02.390> well<00:08:02.570> so<00:08:03.140> maybe<00:08:03.560> we<00:08:03.650> need<00:08:03.680> to 00:08:03.820 --> 00:08:03.830 align:start position:0% place where as well so maybe we need to 00:08:03.830 --> 00:08:07.510 align:start position:0% place where as well so maybe we need to find<00:08:03.950> a<00:08:04.220> better<00:08:04.400> worthy<00:08:04.790> providers<00:08:06.520> but 00:08:07.510 --> 00:08:07.520 align:start position:0% find a better worthy providers but 00:08:07.520 --> 00:08:09.130 align:start position:0% find a better worthy providers but basically<00:08:07.910> we<00:08:08.120> support<00:08:08.480> all<00:08:08.630> the<00:08:08.780> common 00:08:09.130 --> 00:08:09.140 align:start position:0% basically we support all the common 00:08:09.140 --> 00:08:14.170 align:start position:0% basically we support all the common languages<00:08:10.690> 45039<00:08:12.340> way<00:08:13.340> to<00:08:13.400> known<00:08:13.610> that<00:08:13.910> all 00:08:14.170 --> 00:08:14.180 align:start position:0% languages 45039 way to known that all 00:08:14.180 --> 00:08:17.020 align:start position:0% languages 45039 way to known that all the<00:08:14.510> encoding<00:08:15.050> czar<00:08:15.290> custom<00:08:15.710> encodings<00:08:16.030> this 00:08:17.020 --> 00:08:17.030 align:start position:0% the encoding czar custom encodings this 00:08:17.030 --> 00:08:18.190 align:start position:0% the encoding czar custom encodings this is<00:08:17.150> going<00:08:17.300> to<00:08:17.360> sound<00:08:17.450> weird<00:08:17.540> and<00:08:17.930> not<00:08:18.020> make 00:08:18.190 --> 00:08:18.200 align:start position:0% is going to sound weird and not make 00:08:18.200 --> 00:08:19.570 align:start position:0% is going to sound weird and not make lessons<00:08:18.560> but<00:08:18.740> for<00:08:18.919> people<00:08:19.010> who<00:08:19.130> care<00:08:19.370> maybe 00:08:19.570 --> 00:08:19.580 align:start position:0% lessons but for people who care maybe 00:08:19.580 --> 00:08:22.480 align:start position:0% lessons but for people who care maybe indeed<00:08:19.850> care<00:08:20.560> basically<00:08:21.560> they're<00:08:21.770> all<00:08:21.800> a<00:08:21.950> c7 00:08:22.480 --> 00:08:22.490 align:start position:0% indeed care basically they're all a c7 00:08:22.490 --> 00:08:24.130 align:start position:0% indeed care basically they're all a c7 so<00:08:22.669> there's<00:08:22.850> no<00:08:22.970> transmission<00:08:23.300> errors<00:08:23.810> for 00:08:24.130 --> 00:08:24.140 align:start position:0% so there's no transmission errors for 00:08:24.140 --> 00:08:28.000 align:start position:0% so there's no transmission errors for these<00:08:24.290> libraries<00:08:25.510> if<00:08:26.510> you<00:08:26.720> transmit<00:08:27.260> normal 00:08:28.000 --> 00:08:28.010 align:start position:0% these libraries if you transmit normal 00:08:28.010 --> 00:08:30.940 align:start position:0% these libraries if you transmit normal things<00:08:28.280> or<00:08:28.520> if<00:08:29.360> you<00:08:29.480> transfer<00:08:30.200> you<00:08:30.560> have<00:08:30.830> a 00:08:30.940 --> 00:08:30.950 align:start position:0% things or if you transfer you have a 00:08:30.950 --> 00:08:33.219 align:start position:0% things or if you transfer you have a probe<00:08:31.310> over<00:08:31.820> and<00:08:31.970> on<00:08:32.120> YouTube<00:08:32.450> a<00:08:32.570> channel<00:08:32.990> you 00:08:33.219 --> 00:08:33.229 align:start position:0% probe over and on YouTube a channel you 00:08:33.229 --> 00:08:35.560 align:start position:0% probe over and on YouTube a channel you will<00:08:33.650> crop<00:08:33.950> the<00:08:34.099> data<00:08:34.280> and<00:08:34.610> so<00:08:34.910> there's<00:08:35.450> a<00:08:35.510> lot 00:08:35.560 --> 00:08:35.570 align:start position:0% will crop the data and so there's a lot 00:08:35.570 --> 00:08:36.430 align:start position:0% will crop the data and so there's a lot of<00:08:35.690> work 00:08:36.430 --> 00:08:36.440 align:start position:0% of work 00:08:36.440 --> 00:08:40.779 align:start position:0% of work happen<00:08:38.919> one<00:08:39.919> of<00:08:39.979> their<00:08:40.099> keynote<00:08:40.430> I<00:08:40.550> want<00:08:40.729> to 00:08:40.779 --> 00:08:40.789 align:start position:0% happen one of their keynote I want to 00:08:40.789 --> 00:08:42.730 align:start position:0% happen one of their keynote I want to point<00:08:40.909> out<00:08:41.060> this<00:08:41.510> is<00:08:41.570> like<00:08:41.810> a<00:08:41.870> PSA<00:08:42.289> that<00:08:42.320> I<00:08:42.530> want 00:08:42.730 --> 00:08:42.740 align:start position:0% point out this is like a PSA that I want 00:08:42.740 --> 00:08:44.980 align:start position:0% point out this is like a PSA that I want more<00:08:42.830> people<00:08:43.010> to<00:08:43.220> do<00:08:43.370> a<00:08:43.580> lot<00:08:44.330> of<00:08:44.360> people<00:08:44.480> in 00:08:44.980 --> 00:08:44.990 align:start position:0% more people to do a lot of people in 00:08:44.990 --> 00:08:46.750 align:start position:0% more people to do a lot of people in their<00:08:45.170> wallets<00:08:45.530> they<00:08:45.740> kind<00:08:46.250> of<00:08:46.310> skip<00:08:46.580> the 00:08:46.750 --> 00:08:46.760 align:start position:0% their wallets they kind of skip the 00:08:46.760 --> 00:08:51.160 align:start position:0% their wallets they kind of skip the security<00:08:47.740> so<00:08:48.740> memory<00:08:49.490> based<00:08:49.960> cryptography<00:08:50.960> in 00:08:51.160 --> 00:08:51.170 align:start position:0% security so memory based cryptography in 00:08:51.170 --> 00:08:52.450 align:start position:0% security so memory based cryptography in order<00:08:51.350> to<00:08:51.410> improve<00:08:51.680> something<00:08:51.920> and<00:08:52.220> for<00:08:52.370> it<00:08:52.430> to 00:08:52.450 --> 00:08:52.460 align:start position:0% order to improve something and for it to 00:08:52.460 --> 00:08:55.360 align:start position:0% order to improve something and for it to be<00:08:52.520> safe<00:08:52.820> it<00:08:53.090> has<00:08:53.300> to<00:08:53.450> take<00:08:53.690> a<00:08:53.900> while<00:08:54.190> making<00:08:55.190> it 00:08:55.360 --> 00:08:55.370 align:start position:0% be safe it has to take a while making it 00:08:55.370 --> 00:08:57.790 align:start position:0% be safe it has to take a while making it faster<00:08:55.850> makes<00:08:56.210> it<00:08:56.390> less<00:08:56.540> secure<00:08:56.930> so<00:08:57.590> if<00:08:57.710> you 00:08:57.790 --> 00:08:57.800 align:start position:0% faster makes it less secure so if you 00:08:57.800 --> 00:08:59.590 align:start position:0% faster makes it less secure so if you want<00:08:58.010> ten<00:08:58.280> seconds<00:08:58.790> of<00:08:58.940> work 00:08:59.590 --> 00:08:59.600 align:start position:0% want ten seconds of work 00:08:59.600 --> 00:09:01.480 align:start position:0% want ten seconds of work people<00:09:00.350> usually<00:09:00.470> forego<00:09:00.890> that<00:09:00.920> and<00:09:01.220> just<00:09:01.340> put 00:09:01.480 --> 00:09:01.490 align:start position:0% people usually forego that and just put 00:09:01.490 --> 00:09:04.090 align:start position:0% people usually forego that and just put no<00:09:01.580> pressure<00:09:01.610> on<00:09:01.970> it<00:09:02.090> because<00:09:02.450> it's<00:09:02.920> no<00:09:03.920> one 00:09:04.090 --> 00:09:04.100 align:start position:0% no pressure on it because it's no one 00:09:04.100 --> 00:09:05.680 align:start position:0% no pressure on it because it's no one everyone<00:09:04.580> hates<00:09:04.880> it<00:09:04.940> that<00:09:05.090> they<00:09:05.150> can<00:09:05.300> log<00:09:05.480> into 00:09:05.680 --> 00:09:05.690 align:start position:0% everyone hates it that they can log into 00:09:05.690 --> 00:09:07.300 align:start position:0% everyone hates it that they can log into their<00:09:05.900> their<00:09:06.290> wallet<00:09:06.560> and<00:09:06.710> the<00:09:07.010> you<00:09:07.130> white 00:09:07.300 --> 00:09:07.310 align:start position:0% their their wallet and the you white 00:09:07.310 --> 00:09:09.970 align:start position:0% their their wallet and the you white freezes<00:09:07.880> for<00:09:08.090> ten<00:09:08.270> seconds<00:09:08.690> while<00:09:09.560> it's<00:09:09.860> like 00:09:09.970 --> 00:09:09.980 align:start position:0% freezes for ten seconds while it's like 00:09:09.980 --> 00:09:13.210 align:start position:0% freezes for ten seconds while it's like unlocking<00:09:10.730> your<00:09:10.790> wallet<00:09:11.180> so<00:09:12.110> PSA<00:09:13.010> our 00:09:13.210 --> 00:09:13.220 align:start position:0% unlocking your wallet so PSA our 00:09:13.220 --> 00:09:16.330 align:start position:0% unlocking your wallet so PSA our suggestion<00:09:14.180> is<00:09:14.270> better<00:09:14.570> than<00:09:14.660> usage<00:09:15.280> for<00:09:16.280> a 00:09:16.330 --> 00:09:16.340 align:start position:0% suggestion is better than usage for a 00:09:16.340 --> 00:09:18.220 align:start position:0% suggestion is better than usage for a progress<00:09:16.550> bar<00:09:16.700> like<00:09:17.240> people<00:09:17.750> see<00:09:17.960> a<00:09:17.990> progress 00:09:18.220 --> 00:09:18.230 align:start position:0% progress bar like people see a progress 00:09:18.230 --> 00:09:19.960 align:start position:0% progress bar like people see a progress bar<00:09:18.380> quantitative<00:09:19.220> it<00:09:19.550> makes<00:09:19.790> them<00:09:19.940> feel 00:09:19.960 --> 00:09:19.970 align:start position:0% bar quantitative it makes them feel 00:09:19.970 --> 00:09:22.480 align:start position:0% bar quantitative it makes them feel better<00:09:20.450> what<00:09:21.140> it<00:09:21.230> says<00:09:21.320> we're<00:09:21.560> decrypting<00:09:22.280> and 00:09:22.480 --> 00:09:22.490 align:start position:0% better what it says we're decrypting and 00:09:22.490 --> 00:09:24.220 align:start position:0% better what it says we're decrypting and underneath<00:09:22.820> it<00:09:23.030> or<00:09:23.210> securing<00:09:23.810> your<00:09:23.930> funds 00:09:24.220 --> 00:09:24.230 align:start position:0% underneath it or securing your funds 00:09:24.230 --> 00:09:25.810 align:start position:0% underneath it or securing your funds underneath<00:09:24.710> it<00:09:24.830> people<00:09:25.490> are<00:09:25.550> far<00:09:25.790> more 00:09:25.810 --> 00:09:25.820 align:start position:0% underneath it people are far more 00:09:25.820 --> 00:09:28.030 align:start position:0% underneath it people are far more willing<00:09:26.270> to<00:09:26.300> wait<00:09:26.570> those<00:09:26.780> ten<00:09:26.990> seconds<00:09:27.380> and<00:09:27.800> so 00:09:28.030 --> 00:09:28.040 align:start position:0% willing to wait those ten seconds and so 00:09:28.040 --> 00:09:29.170 align:start position:0% willing to wait those ten seconds and so you<00:09:28.160> just<00:09:28.250> need<00:09:28.340> to<00:09:28.400> trick<00:09:28.700> the<00:09:28.820> user<00:09:28.880> into 00:09:29.170 --> 00:09:29.180 align:start position:0% you just need to trick the user into 00:09:29.180 --> 00:09:30.790 align:start position:0% you just need to trick the user into accepting<00:09:29.930> the<00:09:30.020> fact<00:09:30.140> that<00:09:30.320> you're<00:09:30.470> trying<00:09:30.710> to 00:09:30.790 --> 00:09:30.800 align:start position:0% accepting the fact that you're trying to 00:09:30.800 --> 00:09:43.660 align:start position:0% accepting the fact that you're trying to make<00:09:30.920> more<00:09:31.160> secure<00:09:40.960> okay<00:09:41.960> two<00:09:42.020> months<00:09:42.320> so<00:09:42.980> E&S 00:09:43.660 --> 00:09:43.670 align:start position:0% make more secure okay two months so E&S 00:09:43.670 --> 00:09:45.850 align:start position:0% make more secure okay two months so E&S is<00:09:43.820> a<00:09:43.910> first-class<00:09:44.210> system<00:09:44.600> yes<00:09:44.960> I<00:09:45.230> always 00:09:45.850 --> 00:09:45.860 align:start position:0% is a first-class system yes I always 00:09:45.860 --> 00:09:47.890 align:start position:0% is a first-class system yes I always explain<00:09:46.370> I<00:09:46.670> think<00:09:46.700> eNOS<00:09:47.120> it's<00:09:47.270> like<00:09:47.360> the<00:09:47.630> most 00:09:47.890 --> 00:09:47.900 align:start position:0% explain I think eNOS it's like the most 00:09:47.900 --> 00:09:49.690 align:start position:0% explain I think eNOS it's like the most important<00:09:48.560> thing<00:09:48.770> the<00:09:49.100> entire<00:09:49.220> watching 00:09:49.690 --> 00:09:49.700 align:start position:0% important thing the entire watching 00:09:49.700 --> 00:09:52.570 align:start position:0% important thing the entire watching space<00:09:49.970> not<00:09:50.630> just<00:09:50.840> a<00:09:50.930> theory<00:09:51.110> like<00:09:51.350> there's<00:09:52.340> so 00:09:52.570 --> 00:09:52.580 align:start position:0% space not just a theory like there's so 00:09:52.580 --> 00:09:53.740 align:start position:0% space not just a theory like there's so many<00:09:52.640> problems<00:09:53.090> than<00:09:53.270> how<00:09:53.360> the<00:09:53.420> internet 00:09:53.740 --> 00:09:53.750 align:start position:0% many problems than how the internet 00:09:53.750 --> 00:09:56.080 align:start position:0% many problems than how the internet works<00:09:53.870> today<00:09:54.140> you<00:09:54.770> have<00:09:54.950> to<00:09:55.040> trust<00:09:55.280> every<00:09:55.760> CA 00:09:56.080 --> 00:09:56.090 align:start position:0% works today you have to trust every CA 00:09:56.090 --> 00:09:58.480 align:start position:0% works today you have to trust every CA otherwise<00:09:56.690> you're<00:09:57.020> compromised<00:09:57.470> so<00:09:58.340> heinous 00:09:58.480 --> 00:09:58.490 align:start position:0% otherwise you're compromised so heinous 00:09:58.490 --> 00:10:00.550 align:start position:0% otherwise you're compromised so heinous it<00:09:58.760> solve<00:09:58.970> all<00:09:59.090> these<00:09:59.180> problems<00:09:59.240> so<00:09:59.720> es<00:10:00.080> is<00:10:00.320> a 00:10:00.550 --> 00:10:00.560 align:start position:0% it solve all these problems so es is a 00:10:00.560 --> 00:10:02.230 align:start position:0% it solve all these problems so es is a first<00:10:00.800> busted<00:10:01.160> ass<00:10:01.250> and<00:10:01.400> Anita's<00:10:01.790> it<00:10:02.060> always 00:10:02.230 --> 00:10:02.240 align:start position:0% first busted ass and Anita's it always 00:10:02.240 --> 00:10:05.410 align:start position:0% first busted ass and Anita's it always has<00:10:02.510> been<00:10:02.750> since<00:10:02.990> like<00:10:03.770> version<00:10:04.160> 2<00:10:04.460> and<00:10:04.850> it<00:10:05.330> was 00:10:05.410 --> 00:10:05.420 align:start position:0% has been since like version 2 and it was 00:10:05.420 --> 00:10:07.090 align:start position:0% has been since like version 2 and it was really<00:10:05.630> dial-up<00:10:05.960> version<00:10:06.380> 3<00:10:06.590> and<00:10:06.620> since<00:10:06.950> then 00:10:07.090 --> 00:10:07.100 align:start position:0% really dial-up version 3 and since then 00:10:07.100 --> 00:10:09.850 align:start position:0% really dial-up version 3 and since then it's<00:10:07.250> carried<00:10:07.490> on<00:10:07.580> so<00:10:08.270> for<00:10:08.990> example<00:10:09.350> you<00:10:09.710> can 00:10:09.850 --> 00:10:09.860 align:start position:0% it's carried on so for example you can 00:10:09.860 --> 00:10:11.260 align:start position:0% it's carried on so for example you can use<00:10:09.890> tap<00:10:10.340> you<00:10:10.430> guys<00:10:10.520> you<00:10:10.610> got<00:10:10.730> Eve<00:10:10.880> which<00:10:11.150> is 00:10:11.260 --> 00:10:11.270 align:start position:0% use tap you guys you got Eve which is 00:10:11.270 --> 00:10:13.780 align:start position:0% use tap you guys you got Eve which is one<00:10:11.390> of<00:10:11.420> our<00:10:11.540> contracts<00:10:12.020> the<00:10:12.950> address<00:10:13.310> for<00:10:13.610> the 00:10:13.780 --> 00:10:13.790 align:start position:0% one of our contracts the address for the 00:10:13.790 --> 00:10:15.970 align:start position:0% one of our contracts the address for the contract<00:10:14.300> when<00:10:14.570> you<00:10:14.660> instantiate<00:10:14.900> this<00:10:15.260> it'll 00:10:15.970 --> 00:10:15.980 align:start position:0% contract when you instantiate this it'll 00:10:15.980 --> 00:10:17.440 align:start position:0% contract when you instantiate this it'll wind<00:10:16.220> it<00:10:16.310> up<00:10:16.370> the<00:10:16.670> cool<00:10:16.880> thing<00:10:17.060> is<00:10:17.090> when<00:10:17.360> we 00:10:17.440 --> 00:10:17.450 align:start position:0% wind it up the cool thing is when we 00:10:17.450 --> 00:10:20.230 align:start position:0% wind it up the cool thing is when we upgrade<00:10:17.660> over<00:10:18.530> our<00:10:19.070> contract<00:10:19.520> we<00:10:20.089> just 00:10:20.230 --> 00:10:20.240 align:start position:0% upgrade over our contract we just 00:10:20.240 --> 00:10:22.840 align:start position:0% upgrade over our contract we just upgrade<00:10:20.570> ES<00:10:20.930> and<00:10:21.230> all<00:10:22.160> of<00:10:22.400> our<00:10:22.490> software<00:10:22.760> can 00:10:22.840 --> 00:10:22.850 align:start position:0% upgrade ES and all of our software can 00:10:22.850 --> 00:10:23.530 align:start position:0% upgrade ES and all of our software can use<00:10:23.089> to<00:10:23.210> work 00:10:23.530 --> 00:10:23.540 align:start position:0% use to work 00:10:23.540 --> 00:10:24.670 align:start position:0% use to work you<00:10:23.570> don't<00:10:23.690> have<00:10:23.810> to<00:10:23.870> change<00:10:24.050> anything 00:10:24.670 --> 00:10:24.680 align:start position:0% you don't have to change anything 00:10:24.680 --> 00:10:26.949 align:start position:0% you don't have to change anything there's<00:10:25.100> no<00:10:25.190> redeploying<00:10:25.699> stuff<00:10:26.000> other<00:10:26.779> than 00:10:26.949 --> 00:10:26.959 align:start position:0% there's no redeploying stuff other than 00:10:26.959 --> 00:10:29.530 align:start position:0% there's no redeploying stuff other than contracting<00:10:27.620> displeased<00:10:28.540> obviously 00:10:29.530 --> 00:10:29.540 align:start position:0% contracting displeased obviously 00:10:29.540 --> 00:10:31.749 align:start position:0% contracting displeased obviously anywhere<00:10:29.990> it<00:10:30.139> once<00:10:31.070> we're<00:10:31.190> short<00:10:31.370> anywhere 00:10:31.749 --> 00:10:31.759 align:start position:0% anywhere it once we're short anywhere 00:10:31.759 --> 00:10:41.639 align:start position:0% anywhere it once we're short anywhere teachers<00:10:32.089> you<00:10:32.209> can<00:10:32.300> use<00:10:32.420> an<00:10:32.540> address<00:10:33.279> use<00:10:34.279> a 00:10:41.639 --> 00:10:41.649 align:start position:0% 00:10:41.649 --> 00:10:45.100 align:start position:0% deployment<00:10:42.649> contract<00:10:43.810> plan<00:10:44.810> what's<00:10:45.019> gonna 00:10:45.100 --> 00:10:45.110 align:start position:0% deployment contract plan what's gonna 00:10:45.110 --> 00:10:47.740 align:start position:0% deployment contract plan what's gonna stay<00:10:45.259> with<00:10:45.410> this<00:10:45.500> but<00:10:46.130> basically<00:10:46.420> in<00:10:47.420> created 00:10:47.740 --> 00:10:47.750 align:start position:0% stay with this but basically in created 00:10:47.750 --> 00:10:49.180 align:start position:0% stay with this but basically in created contract<00:10:48.110> factories<00:10:48.470> which<00:10:48.769> allows<00:10:49.009> you<00:10:49.130> to 00:10:49.180 --> 00:10:49.190 align:start position:0% contract factories which allows you to 00:10:49.190 --> 00:10:51.100 align:start position:0% contract factories which allows you to create<00:10:49.339> a<00:10:49.490> contract<00:10:49.910> the<00:10:50.630> important<00:10:50.959> thing 00:10:51.100 --> 00:10:51.110 align:start position:0% create a contract the important thing 00:10:51.110 --> 00:10:54.999 align:start position:0% create a contract the important thing either's<00:10:51.500> is<00:10:51.829> how<00:10:52.069> a<00:10:52.810> so<00:10:53.810> a<00:10:53.839> signers<00:10:54.500> send 00:10:54.999 --> 00:10:55.009 align:start position:0% either's is how a so a signers send 00:10:55.009 --> 00:10:56.559 align:start position:0% either's is how a so a signers send transaction<00:10:55.670> does<00:10:55.910> not<00:10:56.029> return<00:10:56.300> to<00:10:56.449> you<00:10:56.540> a 00:10:56.559 --> 00:10:56.569 align:start position:0% transaction does not return to you a 00:10:56.569 --> 00:10:58.809 align:start position:0% transaction does not return to you a transaction<00:10:57.199> cash<00:10:57.410> it<00:10:58.220> returns<00:10:58.519> to<00:10:58.639> you<00:10:58.670> the 00:10:58.809 --> 00:10:58.819 align:start position:0% transaction cash it returns to you the 00:10:58.819 --> 00:11:01.930 align:start position:0% transaction cash it returns to you the full<00:10:59.000> transaction<00:10:59.660> which<00:11:00.319> means<00:11:00.589> that<00:11:01.339> once 00:11:01.930 --> 00:11:01.940 align:start position:0% full transaction which means that once 00:11:01.940 --> 00:11:03.910 align:start position:0% full transaction which means that once you've<00:11:02.329> done<00:11:02.540> this<00:11:02.779> step<00:11:03.079> so<00:11:03.319> you<00:11:03.560> wanted<00:11:03.800> that 00:11:03.910 --> 00:11:03.920 align:start position:0% you've done this step so you wanted that 00:11:03.920 --> 00:11:05.530 align:start position:0% you've done this step so you wanted that at<00:11:04.009> this<00:11:04.160> point<00:11:04.430> the<00:11:04.639> contract<00:11:05.089> is<00:11:05.209> not<00:11:05.360> been 00:11:05.530 --> 00:11:05.540 align:start position:0% at this point the contract is not been 00:11:05.540 --> 00:11:07.780 align:start position:0% at this point the contract is not been mine<00:11:05.750> but<00:11:06.740> you<00:11:07.040> have<00:11:07.220> available<00:11:07.430> to<00:11:07.639> you<00:11:07.730> a 00:11:07.780 --> 00:11:07.790 align:start position:0% mine but you have available to you a 00:11:07.790 --> 00:11:10.420 align:start position:0% mine but you have available to you a full<00:11:08.149> contract<00:11:08.569> object<00:11:08.990> with<00:11:09.680> the<00:11:09.980> contract 00:11:10.420 --> 00:11:10.430 align:start position:0% full contract object with the contract 00:11:10.430 --> 00:11:13.920 align:start position:0% full contract object with the contract address<00:11:10.790> so<00:11:11.120> if<00:11:11.389> you<00:11:11.480> had<00:11:11.690> some<00:11:11.930> sort<00:11:12.050> of 00:11:13.920 --> 00:11:13.930 align:start position:0% address so if you had some sort of 00:11:13.930 --> 00:11:16.269 align:start position:0% address so if you had some sort of database<00:11:14.930> you<00:11:15.230> wanted<00:11:15.500> to<00:11:15.589> track<00:11:15.889> this<00:11:16.069> in 00:11:16.269 --> 00:11:16.279 align:start position:0% database you wanted to track this in 00:11:16.279 --> 00:11:19.269 align:start position:0% database you wanted to track this in maybe<00:11:16.550> the<00:11:17.480> gas<00:11:18.079> prices<00:11:18.500> gonna<00:11:18.680> like<00:11:18.920> surge 00:11:19.269 --> 00:11:19.279 align:start position:0% maybe the gas prices gonna like surge 00:11:19.279 --> 00:11:21.280 align:start position:0% maybe the gas prices gonna like surge you<00:11:19.730> want<00:11:20.060> to<00:11:20.300> keep<00:11:20.480> track<00:11:20.690> of<00:11:20.810> what 00:11:21.280 --> 00:11:21.290 align:start position:0% you want to keep track of what 00:11:21.290 --> 00:11:22.660 align:start position:0% you want to keep track of what transactions<00:11:21.860> you've<00:11:22.009> sent<00:11:22.250> to<00:11:22.310> the<00:11:22.370> network 00:11:22.660 --> 00:11:22.670 align:start position:0% transactions you've sent to the network 00:11:22.670 --> 00:11:24.639 align:start position:0% transactions you've sent to the network whether<00:11:23.209> transaction<00:11:23.779> IDs<00:11:23.959> works<00:11:24.230> maybe<00:11:24.500> you 00:11:24.639 --> 00:11:24.649 align:start position:0% whether transaction IDs works maybe you 00:11:24.649 --> 00:11:26.949 align:start position:0% whether transaction IDs works maybe you need<00:11:24.829> to<00:11:24.860> like<00:11:25.220> bump<00:11:25.970> up<00:11:26.149> the<00:11:26.240> gas<00:11:26.389> price<00:11:26.690> later 00:11:26.949 --> 00:11:26.959 align:start position:0% need to like bump up the gas price later 00:11:26.959 --> 00:11:29.650 align:start position:0% need to like bump up the gas price later in<00:11:27.199> the<00:11:27.319> event<00:11:27.529> it<00:11:27.649> does<00:11:27.769> not<00:11:27.889> actually<00:11:28.540> so<00:11:29.540> you 00:11:29.650 --> 00:11:29.660 align:start position:0% in the event it does not actually so you 00:11:29.660 --> 00:11:30.660 align:start position:0% in the event it does not actually so you gotta<00:11:29.870> have<00:11:29.959> access<00:11:30.350> to<00:11:30.440> all<00:11:30.500> information 00:11:30.660 --> 00:11:30.670 align:start position:0% gotta have access to all information 00:11:30.670 --> 00:11:33.579 align:start position:0% gotta have access to all information before<00:11:31.670> the<00:11:32.600> contract<00:11:32.990> is<00:11:33.079> even<00:11:33.350> on<00:11:33.470> the 00:11:33.579 --> 00:11:33.589 align:start position:0% before the contract is even on the 00:11:33.589 --> 00:11:35.680 align:start position:0% before the contract is even on the network<00:11:33.829> and<00:11:34.069> then<00:11:34.370> you<00:11:34.519> can<00:11:34.880> cancel<00:11:35.209> a<00:11:35.420> step 00:11:35.680 --> 00:11:35.690 align:start position:0% network and then you can cancel a step 00:11:35.690 --> 00:11:36.910 align:start position:0% network and then you can cancel a step to<00:11:35.839> actually<00:11:35.959> wait<00:11:36.290> for<00:11:36.560> to<00:11:36.620> be<00:11:36.740> there 00:11:36.910 --> 00:11:36.920 align:start position:0% to actually wait for to be there 00:11:36.920 --> 00:11:39.129 align:start position:0% to actually wait for to be there obviously<00:11:37.910> if<00:11:37.970> you<00:11:38.029> send<00:11:38.209> a<00:11:38.240> message<00:11:38.269> to<00:11:38.750> your 00:11:39.129 --> 00:11:39.139 align:start position:0% obviously if you send a message to your 00:11:39.139 --> 00:11:41.860 align:start position:0% obviously if you send a message to your contract<00:11:39.589> before<00:11:39.740> it's<00:11:39.980> deployed<00:11:40.870> other 00:11:41.860 --> 00:11:41.870 align:start position:0% contract before it's deployed other 00:11:41.870 --> 00:11:43.569 align:start position:0% contract before it's deployed other things<00:11:42.139> they're<00:11:42.260> gonna<00:11:42.380> work<00:11:42.529> you<00:11:43.339> won't<00:11:43.430> be 00:11:43.569 --> 00:11:43.579 align:start position:0% things they're gonna work you won't be 00:11:43.579 --> 00:11:45.160 align:start position:0% things they're gonna work you won't be having<00:11:43.699> anchor<00:11:44.089> so<00:11:44.420> you<00:11:44.480> still<00:11:44.839> have<00:11:44.990> to<00:11:45.079> wait 00:11:45.160 --> 00:11:45.170 align:start position:0% having anchor so you still have to wait 00:11:45.170 --> 00:11:48.430 align:start position:0% having anchor so you still have to wait before<00:11:45.440> the<00:11:45.970> employee<00:11:46.970> also<00:11:47.510> but<00:11:48.230> it<00:11:48.319> does 00:11:48.430 --> 00:11:48.440 align:start position:0% before the employee also but it does 00:11:48.440 --> 00:11:56.410 align:start position:0% before the employee also but it does mean<00:11:48.560> you<00:11:48.620> can<00:11:48.829> use<00:11:48.949> stuff<00:11:49.100> anytime<00:11:55.300> so<00:11:56.300> this 00:11:56.410 --> 00:11:56.420 align:start position:0% mean you can use stuff anytime so this 00:11:56.420 --> 00:12:00.460 align:start position:0% mean you can use stuff anytime so this is<00:11:56.540> more<00:11:56.779> like<00:11:57.290> low<00:11:58.130> level<00:11:58.610> things<00:11:59.120> watch<00:11:59.870> you 00:12:00.460 --> 00:12:00.470 align:start position:0% is more like low level things watch you 00:12:00.470 --> 00:12:03.280 align:start position:0% is more like low level things watch you can<00:12:00.589> do<00:12:00.769> for<00:12:01.220> contracts<00:12:02.180> so<00:12:02.630> normally<00:12:02.990> new 00:12:03.280 --> 00:12:03.290 align:start position:0% can do for contracts so normally new 00:12:03.290 --> 00:12:05.530 align:start position:0% can do for contracts so normally new contract<00:12:03.800> dot<00:12:04.120> transferred<00:12:05.120> whatever<00:12:05.420> your 00:12:05.530 --> 00:12:05.540 align:start position:0% contract dot transferred whatever your 00:12:05.540 --> 00:12:07.170 align:start position:0% contract dot transferred whatever your function<00:12:05.959> name<00:12:06.139> is<00:12:06.319> you<00:12:06.500> just<00:12:06.649> call<00:12:06.860> it 00:12:07.170 --> 00:12:07.180 align:start position:0% function name is you just call it 00:12:07.180 --> 00:12:09.129 align:start position:0% function name is you just call it sometimes<00:12:08.180> you<00:12:08.420> want<00:12:08.630> deferred<00:12:08.930> sign 00:12:09.129 --> 00:12:09.139 align:start position:0% sometimes you want deferred sign 00:12:09.139 --> 00:12:10.900 align:start position:0% sometimes you want deferred sign anything<00:12:09.380> wants<00:12:09.829> to<00:12:10.010> for<00:12:10.339> example<00:12:10.639> one<00:12:10.760> of<00:12:10.819> the 00:12:10.900 --> 00:12:10.910 align:start position:0% anything wants to for example one of the 00:12:10.910 --> 00:12:13.120 align:start position:0% anything wants to for example one of the signers<00:12:11.120> I<00:12:11.360> provide<00:12:11.660> is<00:12:12.199> an<00:12:12.380> offline<00:12:12.709> signer 00:12:13.120 --> 00:12:13.130 align:start position:0% signers I provide is an offline signer 00:12:13.130 --> 00:12:15.699 align:start position:0% signers I provide is an offline signer what<00:12:13.699> this<00:12:14.329> does<00:12:14.540> is<00:12:14.899> when<00:12:14.959> your<00:12:15.470> science 00:12:15.699 --> 00:12:15.709 align:start position:0% what this does is when your science 00:12:15.709 --> 00:12:17.679 align:start position:0% what this does is when your science transaction<00:12:16.189> it<00:12:16.760> just<00:12:17.000> shows<00:12:17.329> up<00:12:17.510> on<00:12:17.630> the 00:12:17.679 --> 00:12:17.689 align:start position:0% transaction it just shows up on the 00:12:17.689 --> 00:12:20.050 align:start position:0% transaction it just shows up on the screen<00:12:17.990> as<00:12:18.439> a<00:12:18.500> QR<00:12:18.860> code<00:12:19.040> so<00:12:19.670> this<00:12:19.790> is<00:12:19.910> what<00:12:20.029> I 00:12:20.050 --> 00:12:20.060 align:start position:0% screen as a QR code so this is what I 00:12:20.060 --> 00:12:23.100 align:start position:0% screen as a QR code so this is what I run<00:12:20.329> on<00:12:20.630> my<00:12:20.769> my<00:12:21.769> level 00:12:23.100 --> 00:12:23.110 align:start position:0% run on my my level 00:12:23.110 --> 00:12:28.010 align:start position:0% run on my my level you<00:12:23.380> know<00:12:23.470> $100<00:12:24.040> laptop<00:12:24.450> it's<00:12:25.450> I<00:12:25.810> had<00:12:26.680> the 00:12:28.010 --> 00:12:28.020 align:start position:0% you know $100 laptop it's I had the 00:12:28.020 --> 00:12:30.830 align:start position:0% you know $100 laptop it's I had the network<00:12:29.020> card<00:12:29.260> and<00:12:29.470> Bluetooth<00:12:29.950> it's<00:12:30.070> all<00:12:30.190> been 00:12:30.830 --> 00:12:30.840 align:start position:0% network card and Bluetooth it's all been 00:12:30.840 --> 00:12:34.020 align:start position:0% network card and Bluetooth it's all been very<00:12:32.370> progressively<00:12:33.370> removed 00:12:34.020 --> 00:12:34.030 align:start position:0% very progressively removed 00:12:34.030 --> 00:12:35.700 align:start position:0% very progressively removed there's<00:12:34.360> no<00:12:34.510> antennas<00:12:35.050> left<00:12:35.230> in<00:12:35.350> the<00:12:35.410> machine 00:12:35.700 --> 00:12:35.710 align:start position:0% there's no antennas left in the machine 00:12:35.710 --> 00:12:37.770 align:start position:0% there's no antennas left in the machine so<00:12:36.340> I<00:12:36.370> can<00:12:36.580> now<00:12:36.760> assign<00:12:37.060> license<00:12:37.450> actually<00:12:37.690> for 00:12:37.770 --> 00:12:37.780 align:start position:0% so I can now assign license actually for 00:12:37.780 --> 00:12:39.630 align:start position:0% so I can now assign license actually for that<00:12:37.870> machine<00:12:37.990> it<00:12:38.320> pops<00:12:38.560> up<00:12:38.680> with<00:12:38.740> the<00:12:38.890> work<00:12:39.130> my 00:12:39.630 --> 00:12:39.640 align:start position:0% that machine it pops up with the work my 00:12:39.640 --> 00:12:42.360 align:start position:0% that machine it pops up with the work my scan<00:12:40.000> takes<00:12:40.990> me<00:12:41.170> on<00:12:41.350> my<00:12:41.560> phone<00:12:41.770> it<00:12:42.070> takes<00:12:42.250> them 00:12:42.360 --> 00:12:42.370 align:start position:0% scan takes me on my phone it takes them 00:12:42.370 --> 00:12:43.260 align:start position:0% scan takes me on my phone it takes them to<00:12:42.460> a<00:12:42.490> website<00:12:42.820> which<00:12:42.970> sum<00:12:43.150> is<00:12:43.240> the 00:12:43.260 --> 00:12:43.270 align:start position:0% to a website which sum is the 00:12:43.270 --> 00:12:45.390 align:start position:0% to a website which sum is the transaction<00:12:43.660> to<00:12:43.900> the<00:12:43.930> network<00:12:44.230> and<00:12:44.530> so<00:12:45.190> I<00:12:45.220> have 00:12:45.390 --> 00:12:45.400 align:start position:0% transaction to the network and so I have 00:12:45.400 --> 00:12:48.710 align:start position:0% transaction to the network and so I have a<00:12:45.430> nice<00:12:45.790> air<00:12:46.030> gap<00:12:46.240> solution<00:12:47.130> inside<00:12:48.130> the<00:12:48.370> coals 00:12:48.710 --> 00:12:48.720 align:start position:0% a nice air gap solution inside the coals 00:12:48.720 --> 00:12:50.850 align:start position:0% a nice air gap solution inside the coals again<00:12:49.720> most<00:12:50.320> these<00:12:50.440> things<00:12:50.620> are<00:12:50.770> probably 00:12:50.850 --> 00:12:50.860 align:start position:0% again most these things are probably 00:12:50.860 --> 00:12:52.470 align:start position:0% again most these things are probably familiar<00:12:51.220> people<00:12:51.490> who<00:12:51.760> use<00:12:51.970> them<00:12:52.210> if<00:12:52.360> you're 00:12:52.470 --> 00:12:52.480 align:start position:0% familiar people who use them if you're 00:12:52.480 --> 00:12:53.220 align:start position:0% familiar people who use them if you're not<00:12:52.570> going<00:12:52.720> to<00:12:52.780> go<00:12:52.840> through<00:12:52.930> that<00:12:53.020> you<00:12:53.110> cry 00:12:53.220 --> 00:12:53.230 align:start position:0% not going to go through that you cry 00:12:53.230 --> 00:12:54.690 align:start position:0% not going to go through that you cry don't<00:12:53.290> care<00:12:53.500> too<00:12:53.590> much<00:12:53.620> with<00:12:53.830> them<00:12:54.040> but<00:12:54.580> this 00:12:54.690 --> 00:12:54.700 align:start position:0% don't care too much with them but this 00:12:54.700 --> 00:12:56.430 align:start position:0% don't care too much with them but this allows<00:12:54.970> you<00:12:55.240> this<00:12:55.360> is<00:12:55.510> equal<00:12:55.780> to<00:12:55.840> the<00:12:55.960> doc<00:12:56.140> call 00:12:56.430 --> 00:12:56.440 align:start position:0% allows you this is equal to the doc call 00:12:56.440 --> 00:12:59.070 align:start position:0% allows you this is equal to the doc call on<00:12:56.800> a<00:12:56.860> transaction<00:12:57.250> and<00:12:57.700> in-depth<00:12:58.270> reading<00:12:58.480> it 00:12:59.070 --> 00:12:59.080 align:start position:0% on a transaction and in-depth reading it 00:12:59.080 --> 00:13:01.410 align:start position:0% on a transaction and in-depth reading it lets<00:12:59.290> you<00:12:59.470> use<00:13:00.250> an<00:13:00.490> e<00:13:00.640> underscore<00:13:01.150> call 00:13:01.410 --> 00:13:01.420 align:start position:0% lets you use an e underscore call 00:13:01.420 --> 00:13:03.900 align:start position:0% lets you use an e underscore call instead<00:13:01.990> of<00:13:02.080> a<00:13:02.140> cent<00:13:02.320> transaction<00:13:02.830> just<00:13:03.370> to 00:13:03.900 --> 00:13:03.910 align:start position:0% instead of a cent transaction just to 00:13:03.910 --> 00:13:05.700 align:start position:0% instead of a cent transaction just to simulate<00:13:04.210> what<00:13:04.450> might<00:13:04.630> happen<00:13:05.140> it's 00:13:05.700 --> 00:13:05.710 align:start position:0% simulate what might happen it's 00:13:05.710 --> 00:13:06.690 align:start position:0% simulate what might happen it's important<00:13:06.040> to<00:13:06.100> realize<00:13:06.310> there's<00:13:06.490> a<00:13:06.520> lot<00:13:06.550> of 00:13:06.690 --> 00:13:06.700 align:start position:0% important to realize there's a lot of 00:13:06.700 --> 00:13:08.670 align:start position:0% important to realize there's a lot of consistency<00:13:07.150> things<00:13:07.480> in<00:13:07.750> watching<00:13:08.290> general 00:13:08.670 --> 00:13:08.680 align:start position:0% consistency things in watching general 00:13:08.680 --> 00:13:11.460 align:start position:0% consistency things in watching general you<00:13:09.550> can't<00:13:09.820> rely<00:13:10.000> on<00:13:10.180> this<00:13:10.420> to<00:13:10.960> be<00:13:11.080> what's 00:13:11.460 --> 00:13:11.470 align:start position:0% you can't rely on this to be what's 00:13:11.470 --> 00:13:13.020 align:start position:0% you can't rely on this to be what's going<00:13:11.530> to<00:13:11.740> actually<00:13:11.920> happen<00:13:12.220> but<00:13:12.640> it<00:13:12.790> can<00:13:12.850> help 00:13:13.020 --> 00:13:13.030 align:start position:0% going to actually happen but it can help 00:13:13.030 --> 00:13:14.640 align:start position:0% going to actually happen but it can help give<00:13:13.180> you<00:13:13.270> clues<00:13:13.600> if<00:13:13.930> maybe<00:13:14.380> something 00:13:14.640 --> 00:13:14.650 align:start position:0% give you clues if maybe something 00:13:14.650 --> 00:13:16.830 align:start position:0% give you clues if maybe something through<00:13:15.070> you<00:13:15.820> can<00:13:15.970> kind<00:13:16.180> of<00:13:16.210> it<00:13:16.360> may<00:13:16.540> be<00:13:16.600> error 00:13:16.830 --> 00:13:16.840 align:start position:0% through you can kind of it may be error 00:13:16.840 --> 00:13:19.320 align:start position:0% through you can kind of it may be error messages<00:13:17.200> from<00:13:17.350> us<00:13:17.500> or<00:13:17.680> thing<00:13:18.180> estimated<00:13:19.180> skew 00:13:19.320 --> 00:13:19.330 align:start position:0% messages from us or thing estimated skew 00:13:19.330 --> 00:13:20.910 align:start position:0% messages from us or thing estimated skew the<00:13:19.510> gas<00:13:19.660> price<00:13:19.990> that's<00:13:20.230> expected<00:13:20.800> by<00:13:20.890> the 00:13:20.910 --> 00:13:20.920 align:start position:0% the gas price that's expected by the 00:13:20.920 --> 00:13:24.770 align:start position:0% the gas price that's expected by the network<00:13:21.220> for<00:13:21.310> something<00:13:21.550> it<00:13:21.610> cost 00:13:24.770 --> 00:13:24.780 align:start position:0% 00:13:24.780 --> 00:13:32.360 align:start position:0% [Music] 00:13:32.360 --> 00:13:32.370 align:start position:0% 00:13:32.370 --> 00:13:35.730 align:start position:0% okay<00:13:33.370> so<00:13:33.700> a<00:13:33.970> bi<00:13:34.660> is<00:13:34.780> so<00:13:35.260> one<00:13:35.410> of<00:13:35.440> the<00:13:35.530> things<00:13:35.650> I 00:13:35.730 --> 00:13:35.740 align:start position:0% okay so a bi is so one of the things I 00:13:35.740 --> 00:13:37.580 align:start position:0% okay so a bi is so one of the things I just<00:13:35.770> appears<00:13:36.310> no<00:13:36.460> is<00:13:36.610> a<00:13:36.640> human<00:13:36.910> readable<00:13:37.120> ABI 00:13:37.580 --> 00:13:37.590 align:start position:0% just appears no is a human readable ABI 00:13:37.590 --> 00:13:39.780 align:start position:0% just appears no is a human readable ABI it<00:13:38.590> pilots<00:13:38.980> familiar<00:13:39.310> it<00:13:39.460> looks<00:13:39.610> like<00:13:39.760> a 00:13:39.780 --> 00:13:39.790 align:start position:0% it pilots familiar it looks like a 00:13:39.790 --> 00:13:43.140 align:start position:0% it pilots familiar it looks like a signature<00:13:40.990> because<00:13:41.950> it<00:13:42.070> is<00:13:42.190> that 00:13:43.140 --> 00:13:43.150 align:start position:0% signature because it is that 00:13:43.150 --> 00:13:45.300 align:start position:0% signature because it is that literally<00:13:43.750> all<00:13:43.990> is<00:13:44.170> the<00:13:44.710> important<00:13:45.160> thing<00:13:45.250> to 00:13:45.300 --> 00:13:45.310 align:start position:0% literally all is the important thing to 00:13:45.310 --> 00:13:47.670 align:start position:0% literally all is the important thing to realize<00:13:45.610> is<00:13:45.820> that<00:13:45.910> solidity<00:13:46.570> happens<00:13:47.440> to<00:13:47.590> be 00:13:47.670 --> 00:13:47.680 align:start position:0% realize is that solidity happens to be 00:13:47.680 --> 00:13:49.920 align:start position:0% realize is that solidity happens to be machine<00:13:47.920> readable<00:13:48.240> but<00:13:49.240> it's<00:13:49.360> also<00:13:49.480> fairly 00:13:49.920 --> 00:13:49.930 align:start position:0% machine readable but it's also fairly 00:13:49.930 --> 00:13:51.930 align:start position:0% machine readable but it's also fairly human<00:13:50.320> readable<00:13:50.590> and<00:13:50.800> so<00:13:51.340> we<00:13:51.550> might<00:13:51.730> as<00:13:51.820> well 00:13:51.930 --> 00:13:51.940 align:start position:0% human readable and so we might as well 00:13:51.940 --> 00:13:53.430 align:start position:0% human readable and so we might as well to<00:13:52.090> just<00:13:52.240> use<00:13:52.480> the<00:13:52.690> solidia<00:13:52.960> signature 00:13:53.430 --> 00:13:53.440 align:start position:0% to just use the solidia signature 00:13:53.440 --> 00:13:55.170 align:start position:0% to just use the solidia signature instead<00:13:54.190> of<00:13:54.340> this<00:13:54.640> craziness 00:13:55.170 --> 00:13:55.180 align:start position:0% instead of this craziness 00:13:55.180 --> 00:13:57.090 align:start position:0% instead of this craziness I've<00:13:55.360> also<00:13:55.600> emitted<00:13:56.110> a<00:13:56.170> lot<00:13:56.320> of<00:13:56.410> things<00:13:56.560> so<00:13:56.920> it 00:13:57.090 --> 00:13:57.100 align:start position:0% I've also emitted a lot of things so it 00:13:57.100 --> 00:14:02.190 align:start position:0% I've also emitted a lot of things so it in<00:13:57.550> a<00:13:57.610> slide<00:13:59.190> so<00:14:00.750> basically<00:14:01.750> I'm<00:14:01.930> trying<00:14:02.020> to 00:14:02.190 --> 00:14:02.200 align:start position:0% in a slide so basically I'm trying to 00:14:02.200 --> 00:14:04.530 align:start position:0% in a slide so basically I'm trying to push<00:14:02.560> this<00:14:02.890> type<00:14:03.130> of<00:14:03.160> format<00:14:03.520> it<00:14:04.120> also<00:14:04.240> means 00:14:04.530 --> 00:14:04.540 align:start position:0% push this type of format it also means 00:14:04.540 --> 00:14:05.520 align:start position:0% push this type of format it also means you<00:14:04.660> look<00:14:04.840> at<00:14:04.930> your<00:14:05.020> source<00:14:05.170> code<00:14:05.470> and 00:14:05.520 --> 00:14:05.530 align:start position:0% you look at your source code and 00:14:05.530 --> 00:14:07.230 align:start position:0% you look at your source code and Keitel's<00:14:06.040> going<00:14:06.280> on<00:14:06.400> because<00:14:06.700> just<00:14:06.940> you're<00:14:07.150> a 00:14:07.230 --> 00:14:07.240 align:start position:0% Keitel's going on because just you're a 00:14:07.240 --> 00:14:09.480 align:start position:0% Keitel's going on because just you're a guy<00:14:07.540> you<00:14:08.440> know<00:14:08.620> that<00:14:08.860> it<00:14:08.950> has<00:14:09.070> a<00:14:09.100> transfer 00:14:09.480 --> 00:14:09.490 align:start position:0% guy you know that it has a transfer 00:14:09.490 --> 00:14:10.590 align:start position:0% guy you know that it has a transfer function<00:14:09.610> and<00:14:09.880> a<00:14:09.940> balance<00:14:10.210> of<00:14:10.270> function<00:14:10.570> of 00:14:10.590 --> 00:14:10.600 align:start position:0% function and a balance of function of 00:14:10.600 --> 00:14:12.510 align:start position:0% function and a balance of function of this<00:14:10.690> sort<00:14:10.900> of<00:14:10.930> thing<00:14:11.110> this<00:14:11.800> is<00:14:11.980> very<00:14:12.160> hard<00:14:12.400> and 00:14:12.510 --> 00:14:12.520 align:start position:0% this sort of thing this is very hard and 00:14:12.520 --> 00:14:13.950 align:start position:0% this sort of thing this is very hard and this<00:14:12.670> is<00:14:12.760> you<00:14:12.850> know<00:14:12.970> sort<00:14:13.120> of<00:14:13.240> December<00:14:13.570> JSON 00:14:13.950 --> 00:14:13.960 align:start position:0% this is you know sort of December JSON 00:14:13.960 --> 00:14:17.850 align:start position:0% this is you know sort of December JSON file<00:14:14.170> you<00:14:14.440> can<00:14:14.530> get<00:14:14.770> lost<00:14:14.920> on<00:14:16.560> so<00:14:17.560> the 00:14:17.850 --> 00:14:17.860 align:start position:0% file you can get lost on so the 00:14:17.860 --> 00:14:19.710 align:start position:0% file you can get lost on so the important<00:14:18.220> thing<00:14:18.250> is<00:14:18.370> all<00:14:18.730> these<00:14:19.180> tools<00:14:19.480> for 00:14:19.710 --> 00:14:19.720 align:start position:0% important thing is all these tools for 00:14:19.720 --> 00:14:22.080 align:start position:0% important thing is all these tools for conversion<00:14:20.200> between<00:14:20.320> readable<00:14:20.980> JSON<00:14:21.850> and 00:14:22.080 --> 00:14:22.090 align:start position:0% conversion between readable JSON and 00:14:22.090 --> 00:14:22.590 align:start position:0% conversion between readable JSON and sync 00:14:22.590 --> 00:14:22.600 align:start position:0% sync 00:14:22.600 --> 00:14:25.350 align:start position:0% sync this<00:14:22.990> is<00:14:23.110> how<00:14:23.290> you<00:14:23.350> compute<00:14:23.800> topics<00:14:24.759> and<00:14:25.000> the 00:14:25.350 --> 00:14:25.360 align:start position:0% this is how you compute topics and the 00:14:25.360 --> 00:14:27.720 align:start position:0% this is how you compute topics and the first<00:14:25.750> four<00:14:26.050> bytes<00:14:26.430> when<00:14:27.430> you're<00:14:27.519> computing 00:14:27.720 --> 00:14:27.730 align:start position:0% first four bytes when you're computing 00:14:27.730 --> 00:14:31.019 align:start position:0% first four bytes when you're computing the<00:14:28.300> signature<00:14:28.720> for<00:14:28.959> function<00:14:29.319> call<00:14:29.940> so<00:14:30.940> you 00:14:31.019 --> 00:14:31.029 align:start position:0% the signature for function call so you 00:14:31.029 --> 00:14:32.610 align:start position:0% the signature for function call so you can<00:14:31.149> convert<00:14:31.300> in<00:14:31.630> between<00:14:31.930> all<00:14:32.079> these<00:14:32.199> formats 00:14:32.610 --> 00:14:32.620 align:start position:0% can convert in between all these formats 00:14:32.620 --> 00:14:36.269 align:start position:0% can convert in between all these formats by<00:14:32.860> using<00:14:33.069> the<00:14:33.430> fragment<00:14:33.819> you<00:14:34.000> pull<00:14:34.420> in<00:14:35.279> JSON 00:14:36.269 --> 00:14:36.279 align:start position:0% by using the fragment you pull in JSON 00:14:36.279 --> 00:14:38.759 align:start position:0% by using the fragment you pull in JSON and<00:14:36.519> a<00:14:36.699> spit<00:14:37.120> out<00:14:37.149> of<00:14:37.269> you<00:14:38.170> know<00:14:38.290> the<00:14:38.410> full<00:14:38.620> or 00:14:38.759 --> 00:14:38.769 align:start position:0% and a spit out of you know the full or 00:14:38.769 --> 00:14:41.189 align:start position:0% and a spit out of you know the full or whatever<00:14:39.040> these<00:14:39.850> are<00:14:40.060> useful<00:14:40.209> tools<00:14:40.509> if<00:14:41.019> you 00:14:41.189 --> 00:14:41.199 align:start position:0% whatever these are useful tools if you 00:14:41.199 --> 00:14:43.499 align:start position:0% whatever these are useful tools if you just<00:14:41.410> need<00:14:41.560> to<00:14:41.680> look<00:14:41.740> I<00:14:41.920> transform<00:14:42.579> or<00:14:43.240> even 00:14:43.499 --> 00:14:43.509 align:start position:0% just need to look I transform or even 00:14:43.509 --> 00:14:49.920 align:start position:0% just need to look I transform or even parts<00:14:43.779> eliminating<00:14:44.529> signatures<00:14:47.940> I<00:14:48.940> think 00:14:49.920 --> 00:14:49.930 align:start position:0% parts eliminating signatures I think 00:14:49.930 --> 00:14:52.499 align:start position:0% parts eliminating signatures I think we're<00:14:50.050> getting<00:14:50.199> close<00:14:50.380> a<00:14:50.589> div<00:14:50.800> to<00:14:51.509> seven 00:14:52.499 --> 00:14:52.509 align:start position:0% we're getting close a div to seven 00:14:52.509 --> 00:14:55.590 align:start position:0% we're getting close a div to seven minutes<00:14:52.690> left<00:14:53.250> so<00:14:54.250> a<00:14:54.279> maybe<00:14:54.790> two<00:14:55.060> for<00:14:55.389> people 00:14:55.590 --> 00:14:55.600 align:start position:0% minutes left so a maybe two for people 00:14:55.600 --> 00:14:57.389 align:start position:0% minutes left so a maybe two for people who<00:14:55.690> aren't<00:14:55.810> familiar<00:14:55.899> I<00:14:56.380> introduced<00:14:57.250> us<00:14:57.370> to 00:14:57.389 --> 00:14:57.399 align:start position:0% who aren't familiar I introduced us to 00:14:57.399 --> 00:14:59.550 align:start position:0% who aren't familiar I introduced us to year<00:14:57.699> introduced<00:14:58.449> this<00:14:58.630> two<00:14:58.839> years<00:14:59.050> ago<00:14:59.110> in 00:14:59.550 --> 00:14:59.560 align:start position:0% year introduced this two years ago in 00:14:59.560 --> 00:15:04.590 align:start position:0% year introduced this two years ago in because<00:14:59.889> Jas<00:15:00.750> basically<00:15:02.550> the<00:15:03.550> by<00:15:04.149> default 00:15:04.590 --> 00:15:04.600 align:start position:0% because Jas basically the by default 00:15:04.600 --> 00:15:06.540 align:start position:0% because Jas basically the by default slowly<00:15:04.990> does<00:15:05.199> not<00:15:05.380> enable<00:15:05.620> you<00:15:05.949> to<00:15:05.980> have<00:15:06.250> a 00:15:06.540 --> 00:15:06.550 align:start position:0% slowly does not enable you to have a 00:15:06.550 --> 00:15:08.790 align:start position:0% slowly does not enable you to have a raise<00:15:06.910> of<00:15:07.329> dynamic<00:15:07.899> objects<00:15:08.290> and<00:15:08.529> that's<00:15:08.740> not 00:15:08.790 --> 00:15:08.800 align:start position:0% raise of dynamic objects and that's not 00:15:08.800 --> 00:15:11.579 align:start position:0% raise of dynamic objects and that's not allow<00:15:08.980> you<00:15:09.040> to<00:15:09.190> expose<00:15:09.670> structs<00:15:10.440> outside<00:15:11.440> of<00:15:11.529> a 00:15:11.579 --> 00:15:11.589 align:start position:0% allow you to expose structs outside of a 00:15:11.589 --> 00:15:13.769 align:start position:0% allow you to expose structs outside of a contract<00:15:12.040> there<00:15:12.459> I'll<00:15:12.699> actually<00:15:12.940> support<00:15:13.660> it 00:15:13.769 --> 00:15:13.779 align:start position:0% contract there I'll actually support it 00:15:13.779 --> 00:15:16.439 align:start position:0% contract there I'll actually support it you<00:15:13.870> get<00:15:14.110> a<00:15:14.139> special<00:15:14.380> flag<00:15:14.740> to<00:15:15.190> tell<00:15:16.149> asleep 00:15:16.439 --> 00:15:16.449 align:start position:0% you get a special flag to tell asleep 00:15:16.449 --> 00:15:18.809 align:start position:0% you get a special flag to tell asleep either<00:15:16.690> not<00:15:16.930> throw<00:15:17.170> warnings<00:15:17.639> there<00:15:18.639> very 00:15:18.809 --> 00:15:18.819 align:start position:0% either not throw warnings there very 00:15:18.819 --> 00:15:21.480 align:start position:0% either not throw warnings there very easily<00:15:18.940> have<00:15:19.240> complex<00:15:19.660> objects<00:15:20.110> to<00:15:20.889> pass<00:15:21.100> in 00:15:21.480 --> 00:15:21.490 align:start position:0% easily have complex objects to pass in 00:15:21.490 --> 00:15:27.769 align:start position:0% easily have complex objects to pass in and<00:15:21.699> out<00:15:21.819> of<00:15:22.560> functions<00:15:23.560> basically<00:15:26.670> maybe 00:15:27.769 --> 00:15:27.779 align:start position:0% and out of functions basically maybe 00:15:27.779 --> 00:15:30.780 align:start position:0% and out of functions basically maybe self-explanatory<00:15:29.220> again<00:15:30.220> maybe<00:15:30.370> but<00:15:30.579> we<00:15:30.670> have 00:15:30.780 --> 00:15:30.790 align:start position:0% self-explanatory again maybe but we have 00:15:30.790 --> 00:15:31.550 align:start position:0% self-explanatory again maybe but we have to<00:15:30.880> reverse<00:15:31.000> if<00:15:31.149> you<00:15:31.240> have<00:15:31.329> more<00:15:31.420> questions 00:15:31.550 --> 00:15:31.560 align:start position:0% to reverse if you have more questions 00:15:31.560 --> 00:15:33.689 align:start position:0% to reverse if you have more questions this<00:15:32.560> is<00:15:32.620> going<00:15:32.889> to<00:15:32.949> be<00:15:33.009> changing<00:15:33.339> soon<00:15:33.550> as 00:15:33.689 --> 00:15:33.699 align:start position:0% this is going to be changing soon as 00:15:33.699 --> 00:15:35.129 align:start position:0% this is going to be changing soon as well<00:15:33.880> so<00:15:34.089> right<00:15:34.240> now<00:15:34.329> you<00:15:34.389> obviously<00:15:34.990> you'll 00:15:35.129 --> 00:15:35.139 align:start position:0% well so right now you obviously you'll 00:15:35.139 --> 00:15:36.509 align:start position:0% well so right now you obviously you'll always<00:15:35.410> be<00:15:35.649> able<00:15:35.709> to<00:15:35.829> specify<00:15:35.949> Tuffle 00:15:36.509 --> 00:15:36.519 align:start position:0% always be able to specify Tuffle 00:15:36.519 --> 00:15:39.569 align:start position:0% always be able to specify Tuffle straightening<00:15:37.060> I'm<00:15:37.300> gonna<00:15:37.920> that<00:15:38.920> Amy<00:15:39.100> is<00:15:39.220> sue 00:15:39.569 --> 00:15:39.579 align:start position:0% straightening I'm gonna that Amy is sue 00:15:39.579 --> 00:15:42.360 align:start position:0% straightening I'm gonna that Amy is sue mean<00:15:39.810> extended<00:15:40.810> to<00:15:40.990> support<00:15:41.110> struct<00:15:41.769> we 00:15:42.360 --> 00:15:42.370 align:start position:0% mean extended to support struct we 00:15:42.370 --> 00:15:44.069 align:start position:0% mean extended to support struct we actually<00:15:42.610> specify<00:15:42.880> struct<00:15:43.389> definitions<00:15:43.899> in 00:15:44.069 --> 00:15:44.079 align:start position:0% actually specify struct definitions in 00:15:44.079 --> 00:15:46.139 align:start position:0% actually specify struct definitions in your<00:15:44.199> API<00:15:44.470> and<00:15:44.889> then<00:15:45.519> you<00:15:45.790> be<00:15:45.939> able<00:15:46.089> to 00:15:46.139 --> 00:15:46.149 align:start position:0% your API and then you be able to 00:15:46.149 --> 00:15:48.240 align:start position:0% your API and then you be able to sprinkles<00:15:46.660> just<00:15:46.720> say<00:15:47.019> add<00:15:47.380> user<00:15:47.680> takes<00:15:48.069> him 00:15:48.240 --> 00:15:48.250 align:start position:0% sprinkles just say add user takes him 00:15:48.250 --> 00:15:53.809 align:start position:0% sprinkles just say add user takes him Mike<00:15:48.459> user<00:15:48.790> and<00:15:49.540> it<00:15:49.660> would<00:15:49.779> do<00:15:50.170> all<00:15:50.290> press<00:15:50.500> the 00:15:53.809 --> 00:15:53.819 align:start position:0% 00:15:53.819 --> 00:15:57.300 align:start position:0% utilities<00:15:54.819> so<00:15:55.529> this<00:15:56.529> is<00:15:56.680> just<00:15:56.949> not<00:15:57.040> quick 00:15:57.300 --> 00:15:57.310 align:start position:0% utilities so this is just not quick 00:15:57.310 --> 00:15:59.009 align:start position:0% utilities so this is just not quick slide<00:15:57.790> potential<00:15:58.089> from<00:15:58.329> the<00:15:58.449> other<00:15:58.569> utilities 00:15:59.009 --> 00:15:59.019 align:start position:0% slide potential from the other utilities 00:15:59.019 --> 00:16:03.329 align:start position:0% slide potential from the other utilities are<00:15:59.110> available<00:15:59.470> in<00:16:00.160> either's<00:16:02.040> it's<00:16:03.040> obviously 00:16:03.329 --> 00:16:03.339 align:start position:0% are available in either's it's obviously 00:16:03.339 --> 00:16:04.600 align:start position:0% are available in either's it's obviously the<00:16:03.459> a<00:16:03.490> guy<00:16:03.790> quarter 00:16:04.600 --> 00:16:04.610 align:start position:0% the a guy quarter 00:16:04.610 --> 00:16:06.069 align:start position:0% the a guy quarter so<00:16:04.759> these<00:16:04.850> things<00:16:04.999> are<00:16:05.149> all<00:16:05.269> exposed<00:16:05.600> because 00:16:06.069 --> 00:16:06.079 align:start position:0% so these things are all exposed because 00:16:06.079 --> 00:16:07.929 align:start position:0% so these things are all exposed because a<00:16:06.259> lot<00:16:06.529> of<00:16:06.619> tools<00:16:06.920> that<00:16:07.249> aren't<00:16:07.459> necessarily 00:16:07.929 --> 00:16:07.939 align:start position:0% a lot of tools that aren't necessarily 00:16:07.939 --> 00:16:10.869 align:start position:0% a lot of tools that aren't necessarily even<00:16:08.269> etherium<00:16:08.779> or<00:16:08.989> aren't<00:16:09.259> aren't<00:16:10.009> apps<00:16:10.369> and 00:16:10.869 --> 00:16:10.879 align:start position:0% even etherium or aren't aren't apps and 00:16:10.879 --> 00:16:13.139 align:start position:0% even etherium or aren't aren't apps and use<00:16:11.089> these<00:16:11.299> to<00:16:11.540> build<00:16:11.660> their<00:16:11.839> own<00:16:11.869> tools 00:16:13.139 --> 00:16:13.149 align:start position:0% use these to build their own tools 00:16:13.149 --> 00:16:15.519 align:start position:0% use these to build their own tools there's<00:16:14.149> a<00:16:14.209> there's<00:16:14.689> a<00:16:14.749> language<00:16:15.079> I'm<00:16:15.199> working 00:16:15.519 --> 00:16:15.529 align:start position:0% there's a there's a language I'm working 00:16:15.529 --> 00:16:17.470 align:start position:0% there's a there's a language I'm working on<00:16:15.589> and<00:16:15.980> it<00:16:16.069> uses<00:16:16.220> a<00:16:16.399> lot<00:16:16.610> of<00:16:16.639> these<00:16:16.790> just<00:16:17.149> kind 00:16:17.470 --> 00:16:17.480 align:start position:0% on and it uses a lot of these just kind 00:16:17.480 --> 00:16:22.629 align:start position:0% on and it uses a lot of these just kind of<00:16:17.629> the<00:16:18.410> Morse<00:16:18.860> eliminate<00:16:19.639> friendly<00:16:21.489> which<00:16:22.489> is 00:16:22.629 --> 00:16:22.639 align:start position:0% of the Morse eliminate friendly which is 00:16:22.639 --> 00:16:24.669 align:start position:0% of the Morse eliminate friendly which is pretty<00:16:23.389> much<00:16:23.449> unrelated<00:16:23.929> to<00:16:24.019> makin<00:16:24.319> it<00:16:24.379> exists 00:16:24.669 --> 00:16:24.679 align:start position:0% pretty much unrelated to makin it exists 00:16:24.679 --> 00:16:27.069 align:start position:0% pretty much unrelated to makin it exists today<00:16:24.769> so<00:16:25.249> there's<00:16:26.179> lots<00:16:26.329> of<00:16:26.420> cool<00:16:26.569> to<00:16:26.689> do<00:16:26.869> that 00:16:27.069 --> 00:16:27.079 align:start position:0% today so there's lots of cool to do that 00:16:27.079 --> 00:16:30.129 align:start position:0% today so there's lots of cool to do that are<00:16:27.529> LP<00:16:27.889> E<00:16:27.920> minor<00:16:28.369> is<00:16:28.610> begun<00:16:28.939> everything's<00:16:29.389> yes 00:16:30.129 --> 00:16:30.139 align:start position:0% are LP E minor is begun everything's yes 00:16:30.139 --> 00:16:32.499 align:start position:0% are LP E minor is begun everything's yes won't<00:16:30.379> the<00:16:30.470> fable<00:16:30.709> legends<00:16:31.009> strings<00:16:31.850> if 00:16:32.499 --> 00:16:32.509 align:start position:0% won't the fable legends strings if 00:16:32.509 --> 00:16:33.879 align:start position:0% won't the fable legends strings if you're<00:16:32.660> dealing<00:16:32.809> with<00:16:32.929> strings<00:16:33.319> at<00:16:33.499> all<00:16:33.619> in 00:16:33.879 --> 00:16:33.889 align:start position:0% you're dealing with strings at all in 00:16:33.889 --> 00:16:36.100 align:start position:0% you're dealing with strings at all in etherium<00:16:34.279> I<00:16:34.519> recommend<00:16:35.329> you<00:16:35.389> use<00:16:35.449> you<00:16:35.779> have<00:16:35.989> a 00:16:36.100 --> 00:16:36.110 align:start position:0% etherium I recommend you use you have a 00:16:36.110 --> 00:16:38.289 align:start position:0% etherium I recommend you use you have a library<00:16:36.319> in<00:16:37.160> JavaScript<00:16:37.790> if<00:16:37.970> you<00:16:38.059> have<00:16:38.209> an 00:16:38.289 --> 00:16:38.299 align:start position:0% library in JavaScript if you have an 00:16:38.299 --> 00:16:41.619 align:start position:0% library in JavaScript if you have an invalid<00:16:38.689> string<00:16:38.989> it'll<00:16:39.739> just<00:16:40.249> fix<00:16:41.059> it<00:16:41.269> for<00:16:41.480> you 00:16:41.619 --> 00:16:41.629 align:start position:0% invalid string it'll just fix it for you 00:16:41.629 --> 00:16:44.679 align:start position:0% invalid string it'll just fix it for you it'll<00:16:41.839> either<00:16:42.829> replace<00:16:43.610> bytes<00:16:44.299> that<00:16:44.449> don't 00:16:44.679 --> 00:16:44.689 align:start position:0% it'll either replace bytes that don't 00:16:44.689 --> 00:16:46.749 align:start position:0% it'll either replace bytes that don't make<00:16:44.749> sense<00:16:44.809> with<00:16:45.319> a<00:16:45.350> placeholder<00:16:45.739> byte<00:16:46.160> or 00:16:46.749 --> 00:16:46.759 align:start position:0% make sense with a placeholder byte or 00:16:46.759 --> 00:16:48.819 align:start position:0% make sense with a placeholder byte or district<00:16:47.149> from<00:16:47.299> entirely<00:16:47.569> when<00:16:48.439> you're<00:16:48.559> doing 00:16:48.819 --> 00:16:48.829 align:start position:0% district from entirely when you're doing 00:16:48.829 --> 00:16:51.069 align:start position:0% district from entirely when you're doing fashion<00:16:49.279> the<00:16:49.369> things<00:16:49.610> is<00:16:50.029> this<00:16:50.239> is<00:16:50.420> not<00:16:50.600> ideal 00:16:51.069 --> 00:16:51.079 align:start position:0% fashion the things is this is not ideal 00:16:51.079 --> 00:16:52.989 align:start position:0% fashion the things is this is not ideal because<00:16:51.739> the<00:16:52.129> actually<00:16:52.519> these<00:16:52.579> two<00:16:52.759> things 00:16:52.989 --> 00:16:52.999 align:start position:0% because the actually these two things 00:16:52.999 --> 00:16:54.160 align:start position:0% because the actually these two things that's<00:16:53.179> not<00:16:53.239> people<00:16:53.540> anymore 00:16:54.160 --> 00:16:54.170 align:start position:0% that's not people anymore 00:16:54.170 --> 00:16:56.590 align:start position:0% that's not people anymore so<00:16:54.799> this<00:16:54.980> strings<00:16:55.220> library<00:16:55.579> is<00:16:55.850> designed<00:16:56.299> to 00:16:56.590 --> 00:16:56.600 align:start position:0% so this strings library is designed to 00:16:56.600 --> 00:16:59.619 align:start position:0% so this strings library is designed to just<00:16:57.529> throw<00:16:57.980> an<00:16:58.069> exception<00:16:58.160> in<00:16:58.999> the<00:16:59.179> inventors 00:16:59.619 --> 00:16:59.629 align:start position:0% just throw an exception in the inventors 00:16:59.629 --> 00:17:00.429 align:start position:0% just throw an exception in the inventors envelopment 00:17:00.429 --> 00:17:00.439 align:start position:0% envelopment 00:17:00.439 --> 00:17:03.009 align:start position:0% envelopment stuff<00:17:01.029> it's<00:17:02.029> usually<00:17:02.149> indication<00:17:02.689> so<00:17:02.809> it's 00:17:03.009 --> 00:17:03.019 align:start position:0% stuff it's usually indication so it's 00:17:03.019 --> 00:17:05.649 align:start position:0% stuff it's usually indication so it's trying<00:17:03.230> to<00:17:03.410> break<00:17:03.529> the<00:17:03.679> system<00:17:03.860> or<00:17:04.639> I<00:17:05.269> mean 00:17:05.649 --> 00:17:05.659 align:start position:0% trying to break the system or I mean 00:17:05.659 --> 00:17:06.179 align:start position:0% trying to break the system or I mean we're<00:17:05.809> in<00:17:05.870> Japan 00:17:06.179 --> 00:17:06.189 align:start position:0% we're in Japan 00:17:06.189 --> 00:17:09.069 align:start position:0% we're in Japan people<00:17:07.189> might<00:17:07.789> still<00:17:08.029> be<00:17:08.089> writing<00:17:08.299> ships<00:17:08.600> j/s 00:17:09.069 --> 00:17:09.079 align:start position:0% people might still be writing ships j/s 00:17:09.079 --> 00:17:10.779 align:start position:0% people might still be writing ships j/s as<00:17:09.439> their<00:17:10.010> default<00:17:10.159> encoding 00:17:10.779 --> 00:17:10.789 align:start position:0% as their default encoding 00:17:10.789 --> 00:17:13.509 align:start position:0% as their default encoding it's<00:17:11.419> nice<00:17:11.659> when<00:17:12.110> things<00:17:12.409> fail<00:17:12.769> before<00:17:13.429> you 00:17:13.509 --> 00:17:13.519 align:start position:0% it's nice when things fail before you 00:17:13.519 --> 00:17:16.509 align:start position:0% it's nice when things fail before you submit<00:17:13.760> a<00:17:14.089> ship<00:17:14.689> j/s<00:17:15.169> or<00:17:15.559> kind<00:17:16.010> of<00:17:16.069> big<00:17:16.309> five 00:17:16.509 --> 00:17:16.519 align:start position:0% submit a ship j/s or kind of big five 00:17:16.519 --> 00:17:20.769 align:start position:0% submit a ship j/s or kind of big five imported<00:17:17.179> or<00:17:17.329> whatever<00:17:18.730> set<00:17:19.730> of<00:17:19.819> bytes<00:17:19.970> into 00:17:20.769 --> 00:17:20.779 align:start position:0% imported or whatever set of bytes into 00:17:20.779 --> 00:17:23.230 align:start position:0% imported or whatever set of bytes into es<00:17:21.230> which<00:17:21.589> you've<00:17:22.399> now<00:17:22.549> registered<00:17:22.970> a<00:17:23.029> name 00:17:23.230 --> 00:17:23.240 align:start position:0% es which you've now registered a name 00:17:23.240 --> 00:17:26.140 align:start position:0% es which you've now registered a name that<00:17:23.720> you 00:17:26.140 --> 00:17:26.150 align:start position:0% 00:17:26.150 --> 00:17:30.280 align:start position:0% I<00:17:26.180> think<00:17:27.220> that's<00:17:28.600> mostly<00:17:29.600> what<00:17:29.870> I<00:17:29.960> want<00:17:30.110> to<00:17:30.200> say 00:17:30.280 --> 00:17:30.290 align:start position:0% I think that's mostly what I want to say 00:17:30.290 --> 00:17:34.020 align:start position:0% I think that's mostly what I want to say about<00:17:30.350> that<00:17:30.590> it<00:17:30.770> might<00:17:31.070> be<00:17:31.309> done<00:17:31.490> oh<00:17:32.530> ok 00:17:34.020 --> 00:17:34.030 align:start position:0% about that it might be done oh ok 00:17:34.030 --> 00:17:37.600 align:start position:0% about that it might be done oh ok performance<00:17:35.030> prey<00:17:35.420> line<00:17:35.600> interface<00:17:35.960> yes 00:17:37.600 --> 00:17:37.610 align:start position:0% performance prey line interface yes 00:17:37.610 --> 00:17:40.180 align:start position:0% performance prey line interface yes so<00:17:38.450> there's<00:17:38.600> also<00:17:38.720> a<00:17:38.780> line<00:17:39.080> interface<00:17:39.410> erasing 00:17:40.180 --> 00:17:40.190 align:start position:0% so there's also a line interface erasing 00:17:40.190 --> 00:17:41.680 align:start position:0% so there's also a line interface erasing the<00:17:40.250> library<00:17:40.580> experience<00:17:41.270> to<00:17:41.360> write<00:17:41.510> your<00:17:41.660> own 00:17:41.680 --> 00:17:41.690 align:start position:0% the library experience to write your own 00:17:41.690 --> 00:17:45.040 align:start position:0% the library experience to write your own utilities<00:17:42.440> as<00:17:42.680> command<00:17:43.010> line<00:17:43.600> so<00:17:44.600> for<00:17:44.750> example 00:17:45.040 --> 00:17:45.050 align:start position:0% utilities as command line so for example 00:17:45.050 --> 00:17:47.920 align:start position:0% utilities as command line so for example if<00:17:45.110> you're<00:17:45.230> doing<00:17:45.290> your<00:17:45.770> own<00:17:46.210> ear<00:17:47.210> see<00:17:47.420> 2012<00:17:47.809> if 00:17:47.920 --> 00:17:47.930 align:start position:0% if you're doing your own ear see 2012 if 00:17:47.930 --> 00:17:49.750 align:start position:0% if you're doing your own ear see 2012 if you<00:17:48.020> might<00:17:48.200> have<00:17:48.680> a<00:17:49.130> function<00:17:49.370> that<00:17:49.640> allows 00:17:49.750 --> 00:17:49.760 align:start position:0% you might have a function that allows 00:17:49.760 --> 00:17:53.500 align:start position:0% you might have a function that allows you<00:17:50.090> to<00:17:50.150> withdraw<00:17:50.690> your<00:17:50.930> funds<00:17:52.360> that<00:17:53.360> you've 00:17:53.500 --> 00:17:53.510 align:start position:0% you to withdraw your funds that you've 00:17:53.510 --> 00:17:55.330 align:start position:0% you to withdraw your funds that you've collected<00:17:54.050> from<00:17:54.320> from<00:17:54.590> users<00:17:54.950> this<00:17:55.130> allows 00:17:55.330 --> 00:17:55.340 align:start position:0% collected from from users this allows 00:17:55.340 --> 00:17:57.850 align:start position:0% collected from from users this allows you<00:17:55.520> to<00:17:55.550> easily<00:17:55.760> make<00:17:56.120> a<00:17:56.150> tool<00:17:56.360> which<00:17:57.200> lets<00:17:57.680> you 00:17:57.850 --> 00:17:57.860 align:start position:0% you to easily make a tool which lets you 00:17:57.860 --> 00:18:00.820 align:start position:0% you to easily make a tool which lets you collect<00:17:58.220> those<00:17:58.460> funds<00:17:59.050> by<00:18:00.050> default<00:18:00.410> include 00:18:00.820 --> 00:18:00.830 align:start position:0% collect those funds by default include 00:18:00.830 --> 00:18:02.620 align:start position:0% collect those funds by default include sending<00:18:01.670> you<00:18:01.820> here<00:18:01.940> citing<00:18:02.270> messages 00:18:02.620 --> 00:18:02.630 align:start position:0% sending you here citing messages 00:18:02.630 --> 00:18:03.940 align:start position:0% sending you here citing messages graphing<00:18:02.990> from<00:18:03.200> on<00:18:03.320> our<00:18:03.440> pager 00:18:03.940 --> 00:18:03.950 align:start position:0% graphing from on our pager 00:18:03.950 --> 00:18:06.850 align:start position:0% graphing from on our pager sweeping<00:18:04.700> is<00:18:04.820> very<00:18:05.030> useful<00:18:05.360> I'm<00:18:06.260> sure<00:18:06.320> once<00:18:06.770> in 00:18:06.850 --> 00:18:06.860 align:start position:0% sweeping is very useful I'm sure once in 00:18:06.860 --> 00:18:09.430 align:start position:0% sweeping is very useful I'm sure once in a<00:18:06.890> while<00:18:07.040> you've<00:18:07.990> accidentally<00:18:08.990> published<00:18:09.200> a 00:18:09.430 --> 00:18:09.440 align:start position:0% a while you've accidentally published a 00:18:09.440 --> 00:18:11.500 align:start position:0% a while you've accidentally published a public<00:18:09.770> and<00:18:09.920> private<00:18:09.950> key<00:18:10.250> or<00:18:10.510> information 00:18:11.500 --> 00:18:11.510 align:start position:0% public and private key or information 00:18:11.510 --> 00:18:13.330 align:start position:0% public and private key or information the<00:18:11.600> keys<00:18:11.780> to<00:18:11.929> derive<00:18:12.260> a<00:18:12.290> public<00:18:12.770> private<00:18:13.010> key 00:18:13.330 --> 00:18:13.340 align:start position:0% the keys to derive a public private key 00:18:13.340 --> 00:18:15.990 align:start position:0% the keys to derive a public private key or<00:18:13.520> something<00:18:13.670> to<00:18:14.390> github<00:18:14.780> this<00:18:15.380> gives<00:18:15.650> you<00:18:15.770> a 00:18:15.990 --> 00:18:16.000 align:start position:0% or something to github this gives you a 00:18:16.000 --> 00:18:18.190 align:start position:0% or something to github this gives you a 10-second<00:18:17.000> like<00:18:17.150> quick<00:18:17.510> steal<00:18:17.840> my<00:18:17.960> thumbs 00:18:18.190 --> 00:18:18.200 align:start position:0% 10-second like quick steal my thumbs 00:18:18.200 --> 00:18:19.750 align:start position:0% 10-second like quick steal my thumbs back<00:18:18.380> and<00:18:18.740> so<00:18:18.890> you<00:18:18.980> can<00:18:19.100> move<00:18:19.190> your<00:18:19.250> funds<00:18:19.550> back 00:18:19.750 --> 00:18:19.760 align:start position:0% back and so you can move your funds back 00:18:19.760 --> 00:18:22.090 align:start position:0% back and so you can move your funds back to<00:18:19.880> the<00:18:20.000> wall<00:18:20.150> you<00:18:20.270> control<00:18:20.650> before<00:18:21.650> anything 00:18:22.090 --> 00:18:22.100 align:start position:0% to the wall you control before anything 00:18:22.100 --> 00:18:26.350 align:start position:0% to the wall you control before anything takes<00:18:22.280> off<00:18:22.400> with<00:18:22.580> it<00:18:24.220> it<00:18:25.220> can<00:18:25.340> also<00:18:25.429> run<00:18:25.850> like 00:18:26.350 --> 00:18:26.360 align:start position:0% takes off with it it can also run like 00:18:26.360 --> 00:18:27.970 align:start position:0% takes off with it it can also run like so<00:18:26.900> this<00:18:27.080> allows<00:18:27.260> you<00:18:27.380> to<00:18:27.410> do<00:18:27.559> like<00:18:27.740> bash 00:18:27.970 --> 00:18:27.980 align:start position:0% so this allows you to do like bash 00:18:27.980 --> 00:18:30.280 align:start position:0% so this allows you to do like bash scripting<00:18:28.520> to<00:18:28.730> do<00:18:28.900> so<00:18:29.900> you<00:18:30.020> can<00:18:30.140> for<00:18:30.260> example 00:18:30.280 --> 00:18:30.290 align:start position:0% scripting to do so you can for example 00:18:30.290 --> 00:18:36.070 align:start position:0% scripting to do so you can for example resolve<00:18:31.070> DNS<00:18:31.340> names<00:18:31.730> and<00:18:31.940> match<00:18:32.120> the<00:18:35.080> same 00:18:36.070 --> 00:18:36.080 align:start position:0% resolve DNS names and match the same 00:18:36.080 --> 00:18:37.360 align:start position:0% resolve DNS names and match the same sort<00:18:36.230> of<00:18:36.260> thing<00:18:36.380> is<00:18:36.470> this<00:18:36.530> green<00:18:36.830> s<00:18:37.010> there's<00:18:37.309> a 00:18:37.360 --> 00:18:37.370 align:start position:0% sort of thing is this green s there's a 00:18:37.370 --> 00:18:41.560 align:start position:0% sort of thing is this green s there's a massive<00:18:37.610> ENS<00:18:39.520> CLI<00:18:40.520> that<00:18:41.000> lets<00:18:41.150> you<00:18:41.240> register 00:18:41.560 --> 00:18:41.570 align:start position:0% massive ENS CLI that lets you register 00:18:41.570 --> 00:18:43.320 align:start position:0% massive ENS CLI that lets you register names<00:18:41.720> manage<00:18:42.170> your<00:18:42.290> name<00:18:42.410> send<00:18:42.740> resolvers 00:18:43.320 --> 00:18:43.330 align:start position:0% names manage your name send resolvers 00:18:43.330 --> 00:18:46.870 align:start position:0% names manage your name send resolvers everything<00:18:44.330> you<00:18:44.420> can<00:18:44.540> do<00:18:44.660> in<00:18:45.280> NS<00:18:46.280> you<00:18:46.580> can<00:18:46.730> do 00:18:46.870 --> 00:18:46.880 align:start position:0% everything you can do in NS you can do 00:18:46.880 --> 00:18:48.430 align:start position:0% everything you can do in NS you can do through<00:18:47.150> the<00:18:47.270> command<00:18:47.450> line<00:18:47.510> especially 00:18:48.430 --> 00:18:48.440 align:start position:0% through the command line especially 00:18:48.440 --> 00:18:50.200 align:start position:0% through the command line especially useful<00:18:48.770> if<00:18:49.220> you're<00:18:49.429> like<00:18:49.550> me<00:18:49.700> and<00:18:49.790> keep<00:18:49.970> most 00:18:50.200 --> 00:18:50.210 align:start position:0% useful if you're like me and keep most 00:18:50.210 --> 00:18:52.510 align:start position:0% useful if you're like me and keep most of<00:18:50.330> your<00:18:50.450> DNS<00:18:50.780> names<00:18:50.990> on<00:18:51.710> a<00:18:51.740> separate<00:18:52.190> computer 00:18:52.510 --> 00:18:52.520 align:start position:0% of your DNS names on a separate computer 00:18:52.520 --> 00:18:54.310 align:start position:0% of your DNS names on a separate computer that's<00:18:52.790> air-gapped<00:18:53.240> going<00:18:53.990> back<00:18:54.140> to<00:18:54.230> the 00:18:54.310 --> 00:18:54.320 align:start position:0% that's air-gapped going back to the 00:18:54.320 --> 00:18:56.650 align:start position:0% that's air-gapped going back to the previous<00:18:54.500> offline<00:18:55.460> signing<00:18:55.790> thing<00:18:55.940> it's<00:18:56.600> a 00:18:56.650 --> 00:18:56.660 align:start position:0% previous offline signing thing it's a 00:18:56.660 --> 00:18:58.030 align:start position:0% previous offline signing thing it's a little<00:18:56.840> more<00:18:56.960> work<00:18:56.990> but<00:18:57.350> it<00:18:57.500> means<00:18:57.559> that<00:18:57.740> my 00:18:58.030 --> 00:18:58.040 align:start position:0% little more work but it means that my 00:18:58.040 --> 00:19:04.060 align:start position:0% little more work but it means that my eNOS<00:18:58.400> games<00:18:58.610> are<00:18:58.880> less<00:18:59.780> in<00:19:00.710> the<00:19:00.920> wind<00:19:01.540> and<00:19:03.070> I'm 00:19:04.060 --> 00:19:04.070 align:start position:0% eNOS games are less in the wind and I'm 00:19:04.070 --> 00:19:05.470 align:start position:0% eNOS games are less in the wind and I'm done<00:19:04.250> and<00:19:04.429> this<00:19:04.730> is<00:19:04.910> some<00:19:05.090> sort<00:19:05.270> of<00:19:05.330> I<00:19:05.420> know 00:19:05.470 --> 00:19:05.480 align:start position:0% done and this is some sort of I know 00:19:05.480 --> 00:19:06.910 align:start position:0% done and this is some sort of I know this<00:19:05.660> QR<00:19:05.900> codes<00:19:06.080> border<00:19:06.380> I<00:19:06.470> guess<00:19:06.679> you<00:19:06.770> some 00:19:06.910 --> 00:19:06.920 align:start position:0% this QR codes border I guess you some 00:19:06.920 --> 00:19:09.610 align:start position:0% this QR codes border I guess you some sort<00:19:07.100> of<00:19:07.160> contest<00:19:07.610> or<00:19:07.820> something<00:19:07.850> so<00:19:08.660> make 00:19:09.610 --> 00:19:09.620 align:start position:0% sort of contest or something so make 00:19:09.620 --> 00:19:11.430 align:start position:0% sort of contest or something so make sure<00:19:09.650> you<00:19:09.860> scan<00:19:10.190> it<00:19:10.340> so<00:19:10.460> I<00:19:10.520> think<00:19:10.580> you<00:19:10.760> need 00:19:11.430 --> 00:19:11.440 align:start position:0% sure you scan it so I think you need 00:19:11.440 --> 00:19:16.259 align:start position:0% sure you scan it so I think you need oh<00:19:13.320> that's<00:19:14.320> my<00:19:14.649> viola<00:19:15.129> I<00:19:15.309> think<00:19:15.519> I<00:19:15.580> have<00:19:15.789> two 00:19:16.259 --> 00:19:16.269 align:start position:0% oh that's my viola I think I have two 00:19:16.269 --> 00:19:25.649 align:start position:0% oh that's my viola I think I have two minutes<00:19:16.450> for<00:19:16.539> questions<00:19:23.850> plus<00:19:24.850> regular<00:19:25.210> are 00:19:25.649 --> 00:19:25.659 align:start position:0% minutes for questions plus regular are 00:19:25.659 --> 00:19:27.840 align:start position:0% minutes for questions plus regular are you<00:19:25.779> using<00:19:26.350> web<00:19:26.620> or<00:19:26.799> crime<00:19:27.340> fiction<00:19:27.549> when 00:19:27.840 --> 00:19:27.850 align:start position:0% you using web or crime fiction when 00:19:27.850 --> 00:19:29.340 align:start position:0% you using web or crime fiction when you're<00:19:28.000> on<00:19:28.059> no<00:19:28.419> because<00:19:28.720> what<00:19:28.870> workers<00:19:29.049> are 00:19:29.340 --> 00:19:29.350 align:start position:0% you're on no because what workers are 00:19:29.350 --> 00:19:31.019 align:start position:0% you're on no because what workers are only<00:19:29.740> for<00:19:29.950> the<00:19:30.009> browser<00:19:30.220> they<00:19:30.700> don't<00:19:30.909> that<00:19:30.970> you 00:19:31.019 --> 00:19:31.029 align:start position:0% only for the browser they don't that you 00:19:31.029 --> 00:19:34.619 align:start position:0% only for the browser they don't that you can<00:19:31.269> just<00:19:33.059> ensuring<00:19:34.059> the<00:19:34.120> Braille<00:19:34.299> office 00:19:34.619 --> 00:19:34.629 align:start position:0% can just ensuring the Braille office 00:19:34.629 --> 00:19:36.299 align:start position:0% can just ensuring the Braille office there's<00:19:35.139> not<00:19:35.259> really<00:19:35.379> a<00:19:35.470> lot<00:19:35.649> of<00:19:35.679> value<00:19:35.830> to<00:19:36.190> it 00:19:36.299 --> 00:19:36.309 align:start position:0% there's not really a lot of value to it 00:19:36.309 --> 00:19:37.980 align:start position:0% there's not really a lot of value to it because<00:19:36.549> the<00:19:36.669> person<00:19:37.120> is<00:19:37.360> not<00:19:37.389> thus<00:19:37.600> what<00:19:37.840> do 00:19:37.980 --> 00:19:37.990 align:start position:0% because the person is not thus what do 00:19:37.990 --> 00:19:40.649 align:start position:0% because the person is not thus what do you<00:19:38.080> mean<00:19:38.200> like<00:19:38.379> like<00:19:38.860> a<00:19:39.009> script<00:19:39.250> yeah<00:19:40.120> s 00:19:40.649 --> 00:19:40.659 align:start position:0% you mean like like a script yeah s 00:19:40.659 --> 00:19:42.539 align:start position:0% you mean like like a script yeah s script<00:19:40.960> is<00:19:41.080> written<00:19:41.200> entirely<00:19:41.590> custom<00:19:42.220> so<00:19:42.429> it 00:19:42.539 --> 00:19:42.549 align:start position:0% script is written entirely custom so it 00:19:42.549 --> 00:19:44.519 align:start position:0% script is written entirely custom so it actually<00:19:42.669> uses<00:19:42.970> co-routines<00:19:43.480> so<00:19:44.080> it<00:19:44.259> doesn't 00:19:44.519 --> 00:19:44.529 align:start position:0% actually uses co-routines so it doesn't 00:19:44.529 --> 00:19:45.869 align:start position:0% actually uses co-routines so it doesn't feel<00:19:44.590> any<00:19:44.769> better<00:19:44.919> workers<00:19:45.279> to<00:19:45.490> be<00:19:45.580> async 00:19:45.869 --> 00:19:45.879 align:start position:0% feel any better workers to be async 00:19:45.879 --> 00:19:48.450 align:start position:0% feel any better workers to be async recipe<00:19:46.590> because<00:19:47.590> it's<00:19:47.830> not<00:19:47.950> it's<00:19:48.279> not<00:19:48.399> a 00:19:48.450 --> 00:19:48.460 align:start position:0% recipe because it's not it's not a 00:19:48.460 --> 00:19:50.519 align:start position:0% recipe because it's not it's not a portable<00:19:49.149> way<00:19:49.240> to<00:19:49.299> be<00:19:49.509> is<00:19:49.600> experience<00:19:50.110> but<00:19:50.259> we 00:19:50.519 --> 00:19:50.529 align:start position:0% portable way to be is experience but we 00:19:50.529 --> 00:19:55.019 align:start position:0% portable way to be is experience but we should<00:19:50.679> have<00:19:50.830> to<00:19:50.980> talk<00:19:51.159> backwards<00:19:53.789> you<00:19:54.789> need 00:19:55.019 --> 00:19:55.029 align:start position:0% should have to talk backwards you need 00:19:55.029 --> 00:19:57.419 align:start position:0% should have to talk backwards you need plans<00:19:55.450> about<00:19:56.200> a<00:19:56.259> cover<00:19:56.500> deal<00:19:56.740> with<00:19:57.100> like 00:19:57.419 --> 00:19:57.429 align:start position:0% plans about a cover deal with like 00:19:57.429 --> 00:20:01.590 align:start position:0% plans about a cover deal with like networks<00:19:58.090> changes<00:19:58.799> with<00:19:59.799> a<00:20:00.090> provider<00:20:01.090> right 00:20:01.590 --> 00:20:01.600 align:start position:0% networks changes with a provider right 00:20:01.600 --> 00:20:02.909 align:start position:0% networks changes with a provider right because<00:20:01.960> then<00:20:02.289> amounts<00:20:02.559> can<00:20:02.649> no<00:20:02.740> longer 00:20:02.909 --> 00:20:02.919 align:start position:0% because then amounts can no longer 00:20:02.919 --> 00:20:03.539 align:start position:0% because then amounts can no longer refresh<00:20:03.279> it 00:20:03.539 --> 00:20:03.549 align:start position:0% refresh it 00:20:03.549 --> 00:20:06.240 align:start position:0% refresh it absolutely<00:20:04.000> so<00:20:04.240> way<00:20:05.139> I<00:20:05.169> held<00:20:05.620> that<00:20:05.740> my<00:20:06.159> own 00:20:06.240 --> 00:20:06.250 align:start position:0% absolutely so way I held that my own 00:20:06.250 --> 00:20:08.639 align:start position:0% absolutely so way I held that my own custom<00:20:06.549> function<00:20:06.909> which<00:20:07.149> refreshes<00:20:08.019> if<00:20:08.470> they 00:20:08.639 --> 00:20:08.649 align:start position:0% custom function which refreshes if they 00:20:08.649 --> 00:20:10.529 align:start position:0% custom function which refreshes if they need<00:20:08.799> if<00:20:08.889> that<00:20:09.190> sub<00:20:09.429> changes<00:20:09.759> how<00:20:10.240> about<00:20:10.389> yes 00:20:10.529 --> 00:20:10.539 align:start position:0% need if that sub changes how about yes 00:20:10.539 --> 00:20:13.200 align:start position:0% need if that sub changes how about yes in<00:20:10.690> the<00:20:10.750> meantime<00:20:11.279> basically<00:20:12.279> the<00:20:12.909> idea<00:20:13.149> is 00:20:13.200 --> 00:20:13.210 align:start position:0% in the meantime basically the idea is 00:20:13.210 --> 00:20:14.639 align:start position:0% in the meantime basically the idea is we're<00:20:13.360> in<00:20:13.450> one<00:20:13.720> step<00:20:13.899> up<00:20:14.049> there<00:20:14.259> will<00:20:14.350> be<00:20:14.379> a 00:20:14.639 --> 00:20:14.649 align:start position:0% we're in one step up there will be a 00:20:14.649 --> 00:20:17.730 align:start position:0% we're in one step up there will be a provider<00:20:15.490> manager<00:20:16.450> which<00:20:16.870> will<00:20:17.169> give<00:20:17.559> you<00:20:17.649> the 00:20:17.730 --> 00:20:17.740 align:start position:0% provider manager which will give you the 00:20:17.740 --> 00:20:19.409 align:start position:0% provider manager which will give you the notifications<00:20:18.220> that<00:20:18.429> a<00:20:18.460> new<00:20:18.669> provider<00:20:18.940> is<00:20:19.269> now 00:20:19.409 --> 00:20:19.419 align:start position:0% notifications that a new provider is now 00:20:19.419 --> 00:20:22.350 align:start position:0% notifications that a new provider is now being<00:20:19.929> used<00:20:20.279> because<00:20:21.279> providers<00:20:21.820> have<00:20:22.210> to 00:20:22.350 --> 00:20:22.360 align:start position:0% being used because providers have to 00:20:22.360 --> 00:20:23.669 align:start position:0% being used because providers have to remain<00:20:22.570> a<00:20:22.600> beautiful<00:20:23.019> otherwise<00:20:23.350> weird 00:20:23.669 --> 00:20:23.679 align:start position:0% remain a beautiful otherwise weird 00:20:23.679 --> 00:20:25.320 align:start position:0% remain a beautiful otherwise weird things<00:20:23.830> happen<00:20:24.129> it'll<00:20:24.879> become<00:20:25.000> more 00:20:25.320 --> 00:20:25.330 align:start position:0% things happen it'll become more 00:20:25.330 --> 00:20:27.029 align:start position:0% things happen it'll become more important<00:20:25.750> to<00:20:25.899> I<00:20:26.200> know<00:20:26.409> once<00:20:26.860> you<00:20:27.009> start 00:20:27.029 --> 00:20:27.039 align:start position:0% important to I know once you start 00:20:27.039 --> 00:20:29.369 align:start position:0% important to I know once you start having<00:20:27.460> multiple<00:20:27.940> availability<00:20:28.509> chains<00:20:28.750> you 00:20:29.369 --> 00:20:29.379 align:start position:0% having multiple availability chains you 00:20:29.379 --> 00:20:30.840 align:start position:0% having multiple availability chains you will<00:20:29.529> actually<00:20:29.740> have<00:20:30.009> to<00:20:30.159> talk<00:20:30.399> to<00:20:30.549> multiple 00:20:30.840 --> 00:20:30.850 align:start position:0% will actually have to talk to multiple 00:20:30.850 --> 00:20:33.840 align:start position:0% will actually have to talk to multiple chain<00:20:31.509> IDs<00:20:31.840> at<00:20:32.110> the<00:20:32.259> same<00:20:32.440> time<00:20:32.620> so<00:20:33.399> it<00:20:33.549> becomes 00:20:33.840 --> 00:20:33.850 align:start position:0% chain IDs at the same time so it becomes 00:20:33.850 --> 00:20:37.019 align:start position:0% chain IDs at the same time so it becomes more<00:20:34.649> common<00:20:35.649> to<00:20:35.950> see<00:20:35.980> multiple<00:20:36.669> fighters 00:20:37.019 --> 00:20:37.029 align:start position:0% more common to see multiple fighters 00:20:37.029 --> 00:20:45.180 align:start position:0% more common to see multiple fighters assembly<00:20:41.850> why<00:20:42.850> why<00:20:43.330> would<00:20:43.539> I<00:20:43.570> use<00:20:43.870> web<00:20:44.289> 3j<00:20:45.009> s 00:20:45.180 --> 00:20:45.190 align:start position:0% assembly why why would I use web 3j s 00:20:45.190 --> 00:20:49.450 align:start position:0% assembly why why would I use web 3j s instead<00:20:45.820> of<00:20:45.909> ethers<00:20:46.240> I<00:20:46.570> mean<00:20:47.519> um 00:20:49.450 --> 00:20:49.460 align:start position:0% instead of ethers I mean um 00:20:49.460 --> 00:20:52.150 align:start position:0% instead of ethers I mean um politically<00:20:50.180> searched<00:20:50.480> I<00:20:51.380> had<00:20:51.980> to<00:20:52.070> let 00:20:52.150 --> 00:20:52.160 align:start position:0% politically searched I had to let 00:20:52.160 --> 00:20:53.610 align:start position:0% politically searched I had to let standing 00:20:53.610 --> 00:20:53.620 align:start position:0% standing 00:20:53.620 --> 00:20:56.530 align:start position:0% standing I<00:20:54.620> mean<00:20:55.340> I<00:20:55.580> like<00:20:55.790> ethers<00:20:56.090> I've<00:20:56.330> built<00:20:56.510> it 00:20:56.530 --> 00:20:56.540 align:start position:0% I mean I like ethers I've built it 00:20:56.540 --> 00:21:00.250 align:start position:0% I mean I like ethers I've built it because<00:20:56.630> I<00:20:56.990> needed<00:20:57.200> it<00:20:57.410> I<00:20:57.590> use<00:20:57.800> it<00:20:58.010> I<00:20:59.260> don't 00:21:00.250 --> 00:21:00.260 align:start position:0% because I needed it I use it I don't 00:21:00.260 --> 00:21:04.290 align:start position:0% because I needed it I use it I don't want<00:21:00.980> to<00:21:01.130> bad-mouth<00:21:01.520> web<00:21:02.300> three<00:21:02.600> per<00:21:02.840> se<00:21:02.990> so 00:21:04.290 --> 00:21:04.300 align:start position:0% want to bad-mouth web three per se so 00:21:04.300 --> 00:21:12.210 align:start position:0% want to bad-mouth web three per se so afterwards<00:21:09.640> on<00:21:10.640> record<00:21:11.030> saying<00:21:11.240> anything 00:21:12.210 --> 00:21:12.220 align:start position:0% afterwards on record saying anything 00:21:12.220 --> 00:21:14.380 align:start position:0% afterwards on record saying anything yeah<00:21:13.220> you<00:21:13.280> mentioned<00:21:13.430> that<00:21:13.670> pullback<00:21:14.090> provide 00:21:14.380 --> 00:21:14.390 align:start position:0% yeah you mentioned that pullback provide 00:21:14.390 --> 00:21:16.630 align:start position:0% yeah you mentioned that pullback provide us<00:21:14.570> with<00:21:14.860> when<00:21:15.860> you<00:21:15.920> have<00:21:15.950> when<00:21:16.400> you<00:21:16.490> try<00:21:16.610> to 00:21:16.630 --> 00:21:16.640 align:start position:0% us with when you have when you try to 00:21:16.640 --> 00:21:17.620 align:start position:0% us with when you have when you try to read<00:21:16.850> but<00:21:17.000> what<00:21:17.060> about<00:21:17.240> were<00:21:17.300> you<00:21:17.420> trying<00:21:17.540> to 00:21:17.620 --> 00:21:17.630 align:start position:0% read but what about were you trying to 00:21:17.630 --> 00:21:19.150 align:start position:0% read but what about were you trying to run<00:21:17.780> for<00:21:17.990> Senate<00:21:18.140> transaction<00:21:18.710> also<00:21:18.950> writing 00:21:19.150 --> 00:21:19.160 align:start position:0% run for Senate transaction also writing 00:21:19.160 --> 00:21:21.130 align:start position:0% run for Senate transaction also writing broadcast<00:21:19.760> across<00:21:19.970> all<00:21:20.300> would<00:21:20.480> sound<00:21:20.660> asleep 00:21:21.130 --> 00:21:21.140 align:start position:0% broadcast across all would sound asleep 00:21:21.140 --> 00:21:24.070 align:start position:0% broadcast across all would sound asleep writing<00:21:21.920> costs<00:21:22.460> ether<00:21:22.820> so<00:21:23.420> it's<00:21:23.750> not<00:21:23.840> really<00:21:24.050> a 00:21:24.070 --> 00:21:24.080 align:start position:0% writing costs ether so it's not really a 00:21:24.080 --> 00:21:26.440 align:start position:0% writing costs ether so it's not really a real<00:21:24.890> attack<00:21:25.130> vector<00:21:25.460> if<00:21:25.970> someone's<00:21:26.300> paying 00:21:26.440 --> 00:21:26.450 align:start position:0% real attack vector if someone's paying 00:21:26.450 --> 00:21:32.110 align:start position:0% real attack vector if someone's paying oh<00:21:26.890> that<00:21:27.890> times<00:21:28.160> up<00:21:28.840> lemons<00:21:29.840> or<00:21:29.930> calcium<00:21:31.120> yeah 00:21:32.110 --> 00:21:32.120 align:start position:0% oh that times up lemons or calcium yeah 00:21:32.120 --> 00:21:34.510 align:start position:0% oh that times up lemons or calcium yeah so<00:21:32.300> basically<00:21:32.630> it's<00:21:33.350> 20<00:21:33.860> safe<00:21:34.010> broadcast 00:21:34.510 --> 00:21:34.520 align:start position:0% so basically it's 20 safe broadcast 00:21:34.520 --> 00:21:38.080 align:start position:0% so basically it's 20 safe broadcast across<00:21:34.700> all<00:21:34.940> them<00:21:35.170> in<00:21:36.170> that<00:21:36.320> case<00:21:36.910> now<00:21:37.910> if<00:21:37.970> you 00:21:38.080 --> 00:21:38.090 align:start position:0% across all them in that case now if you 00:21:38.090 --> 00:21:40.120 align:start position:0% across all them in that case now if you mind<00:21:38.330> that<00:21:38.570> if<00:21:39.050> you've<00:21:39.350> brought<00:21:39.560> us<00:21:39.770> to<00:21:39.950> fight 00:21:40.120 --> 00:21:40.130 align:start position:0% mind that if you've brought us to fight 00:21:40.130 --> 00:21:42.370 align:start position:0% mind that if you've brought us to fight back<00:21:40.160> Evans<00:21:40.790> the<00:21:40.910> same<00:21:41.090> transaction<00:21:41.630> two<00:21:42.290> of 00:21:42.370 --> 00:21:42.380 align:start position:0% back Evans the same transaction two of 00:21:42.380 --> 00:21:43.690 align:start position:0% back Evans the same transaction two of them<00:21:42.500> will<00:21:42.650> cry<00:21:42.800> say<00:21:43.010> okay<00:21:43.340> got<00:21:43.520> it 00:21:43.690 --> 00:21:43.700 align:start position:0% them will cry say okay got it 00:21:43.700 --> 00:21:45.640 align:start position:0% them will cry say okay got it but<00:21:44.030> the<00:21:44.180> other<00:21:44.390> three<00:21:44.780> that<00:21:45.110> took<00:21:45.200> a<00:21:45.290> little 00:21:45.640 --> 00:21:45.650 align:start position:0% but the other three that took a little 00:21:45.650 --> 00:21:47.830 align:start position:0% but the other three that took a little bit<00:21:45.830> longer<00:21:45.890> can<00:21:46.370> say<00:21:46.550> transaction<00:21:47.540> already 00:21:47.830 --> 00:21:47.840 align:start position:0% bit longer can say transaction already 00:21:47.840 --> 00:21:49.810 align:start position:0% bit longer can say transaction already seen<00:21:48.050> on<00:21:48.140> network<00:21:48.410> okay<00:21:48.710> but<00:21:49.130> that's<00:21:49.250> in<00:21:49.640> this 00:21:49.810 --> 00:21:49.820 align:start position:0% seen on network okay but that's in this 00:21:49.820 --> 00:21:52.330 align:start position:0% seen on network okay but that's in this case<00:21:50.030> a<00:21:50.270> fine<00:21:50.630> error<00:21:51.020> and<00:21:51.290> so<00:21:51.620> it<00:21:51.770> returns<00:21:52.130> to 00:21:52.330 --> 00:21:52.340 align:start position:0% case a fine error and so it returns to 00:21:52.340 --> 00:21:58.510 align:start position:0% case a fine error and so it returns to you<00:21:52.400> the<00:21:52.550> fact<00:21:52.760> that<00:21:52.910> you<00:21:53.690> know<00:21:53.810> it<00:21:54.080> was<00:21:57.520> so 00:21:58.510 --> 00:21:58.520 align:start position:0% you the fact that you know it was so 00:21:58.520 --> 00:21:59.770 align:start position:0% you the fact that you know it was so earlier<00:21:58.820> you<00:21:58.910> mentioned<00:21:59.060> JavaScript<00:21:59.660> no 00:21:59.770 --> 00:21:59.780 align:start position:0% earlier you mentioned JavaScript no 00:21:59.780 --> 00:22:01.960 align:start position:0% earlier you mentioned JavaScript no toolchain<00:22:00.590> yes<00:22:01.010> routines<00:22:01.520> are<00:22:01.640> there<00:22:01.820> any 00:22:01.960 --> 00:22:01.970 align:start position:0% toolchain yes routines are there any 00:22:01.970 --> 00:22:04.180 align:start position:0% toolchain yes routines are there any other<00:22:02.120> like<00:22:02.270> pressing<00:22:03.050> matters<00:22:03.560> that<00:22:03.800> you<00:22:04.010> can 00:22:04.180 --> 00:22:04.190 align:start position:0% other like pressing matters that you can 00:22:04.190 --> 00:22:05.910 align:start position:0% other like pressing matters that you can use<00:22:04.280> up<00:22:04.430> with 00:22:05.910 --> 00:22:05.920 align:start position:0% use up with 00:22:05.920 --> 00:22:07.890 align:start position:0% use up with I<00:22:05.950> mean<00:22:06.910> I<00:22:07.060> think<00:22:07.210> the<00:22:07.420> biggest<00:22:07.570> things<00:22:07.780> right 00:22:07.890 --> 00:22:07.900 align:start position:0% I mean I think the biggest things right 00:22:07.900 --> 00:22:11.520 align:start position:0% I mean I think the biggest things right now<00:22:07.930> our<00:22:08.200> documentation<00:22:08.680> and<00:22:08.980> building<00:22:10.170> but<00:22:11.170> I 00:22:11.520 --> 00:22:11.530 align:start position:0% now our documentation and building but I 00:22:11.530 --> 00:22:13.320 align:start position:0% now our documentation and building but I would<00:22:12.370> like<00:22:12.610> to<00:22:12.670> talk<00:22:12.880> to<00:22:12.940> somebody 00:22:13.320 --> 00:22:13.330 align:start position:0% would like to talk to somebody 00:22:13.330 --> 00:22:15.660 align:start position:0% would like to talk to somebody people<00:22:14.140> don't<00:22:14.290> realize<00:22:14.410> how<00:22:14.530> open<00:22:15.190> ball<00:22:15.340> a 00:22:15.660 --> 00:22:15.670 align:start position:0% people don't realize how open ball a 00:22:15.670 --> 00:22:26.240 align:start position:0% people don't realize how open ball a WebSocket<00:22:16.270> provider<00:22:16.690> is<00:22:16.930> in<00:22:17.230> a<00:22:17.830> reliable<00:22:18.430> and 00:22:26.240 --> 00:22:26.250 align:start position:0% 00:22:26.250 --> 00:22:43.350 align:start position:0% yes<00:22:41.250> right<00:22:42.250> absolutely<00:22:42.550> and<00:22:42.880> so<00:22:43.150> that<00:22:43.270> it's 00:22:43.350 --> 00:22:43.360 align:start position:0% yes right absolutely and so that it's 00:22:43.360 --> 00:22:44.310 align:start position:0% yes right absolutely and so that it's important<00:22:43.660> realize<00:22:43.840> that<00:22:43.990> your<00:22:44.080> attack 00:22:44.310 --> 00:22:44.320 align:start position:0% important realize that your attack 00:22:44.320 --> 00:22:47.490 align:start position:0% important realize that your attack vector<00:22:44.620> is<00:22:44.860> is<00:22:45.220> based<00:22:45.730> if<00:22:46.570> it<00:22:47.170> takes<00:22:47.350> 10 00:22:47.490 --> 00:22:47.500 align:start position:0% vector is is based if it takes 10 00:22:47.500 --> 00:22:48.840 align:start position:0% vector is is based if it takes 10 seconds<00:22:47.800> to<00:22:47.860> decrypt<00:22:48.190> your<00:22:48.310> password<00:22:48.670> today 00:22:48.840 --> 00:22:48.850 align:start position:0% seconds to decrypt your password today 00:22:48.850 --> 00:22:50.430 align:start position:0% seconds to decrypt your password today the<00:22:49.030> reason<00:22:49.210> why<00:22:49.270> is<00:22:49.330> is<00:22:49.450> valuable<00:22:49.810> is<00:22:50.050> because 00:22:50.430 --> 00:22:50.440 align:start position:0% the reason why is is valuable is because 00:22:50.440 --> 00:22:52.080 align:start position:0% the reason why is is valuable is because that<00:22:50.950> means<00:22:51.100> if<00:22:51.220> an<00:22:51.340> attacker<00:22:51.640> is<00:22:51.850> trying<00:22:52.030> to 00:22:52.080 --> 00:22:52.090 align:start position:0% that means if an attacker is trying to 00:22:52.090 --> 00:22:54.090 align:start position:0% that means if an attacker is trying to guess<00:22:52.330> your<00:22:52.540> password<00:22:52.600> they<00:22:53.260> take<00:22:53.410> 10<00:22:53.650> seconds 00:22:54.090 --> 00:22:54.100 align:start position:0% guess your password they take 10 seconds 00:22:54.100 --> 00:22:56.580 align:start position:0% guess your password they take 10 seconds of<00:22:54.310> their<00:22:54.670> computer<00:22:55.060> working<00:22:55.420> at<00:22:55.510> 100%<00:22:55.840> per 00:22:56.580 --> 00:22:56.590 align:start position:0% of their computer working at 100% per 00:22:56.590 --> 00:22:58.230 align:start position:0% of their computer working at 100% per guess<00:22:56.830> yeah<00:22:57.220> they<00:22:57.520> want<00:22:57.700> to<00:22:57.760> guess<00:22:57.850> a<00:22:57.880> million 00:22:58.230 --> 00:22:58.240 align:start position:0% guess yeah they want to guess a million 00:22:58.240 --> 00:23:00.780 align:start position:0% guess yeah they want to guess a million things<00:22:58.390> say<00:22:58.660> that<00:22:58.840> but<00:22:59.290> absolutely<00:22:59.890> next<00:23:00.550> year 00:23:00.780 --> 00:23:00.790 align:start position:0% things say that but absolutely next year 00:23:00.790 --> 00:23:03.570 align:start position:0% things say that but absolutely next year when<00:23:00.940> computers<00:23:01.240> are<00:23:01.330> twice<00:23:01.600> as<00:23:01.630> fast<00:23:02.580> that 00:23:03.570 --> 00:23:03.580 align:start position:0% when computers are twice as fast that 00:23:03.580 --> 00:23:05.490 align:start position:0% when computers are twice as fast that five<00:23:03.820> seconds<00:23:04.210> is<00:23:04.300> now<00:23:04.450> five<00:23:04.750> seconds<00:23:05.140> at<00:23:05.290> some 00:23:05.490 --> 00:23:05.500 align:start position:0% five seconds is now five seconds at some 00:23:05.500 --> 00:23:06.870 align:start position:0% five seconds is now five seconds at some point<00:23:05.740> the<00:23:05.890> attack<00:23:06.100> vector<00:23:06.130> will<00:23:06.610> become 00:23:06.870 --> 00:23:06.880 align:start position:0% point the attack vector will become 00:23:06.880 --> 00:23:08.940 align:start position:0% point the attack vector will become affordable<00:23:07.360> and<00:23:07.510> so<00:23:07.930> it's<00:23:08.080> also<00:23:08.260> important<00:23:08.800> to 00:23:08.940 --> 00:23:08.950 align:start position:0% affordable and so it's also important to 00:23:08.950 --> 00:23:10.620 align:start position:0% affordable and so it's also important to realize<00:23:09.070> you<00:23:09.370> should<00:23:09.640> be<00:23:09.790> building<00:23:10.420> new 00:23:10.620 --> 00:23:10.630 align:start position:0% realize you should be building new 00:23:10.630 --> 00:23:12.900 align:start position:0% realize you should be building new accounts<00:23:11.110> regularly<00:23:11.290> and<00:23:11.830> every<00:23:12.610> so<00:23:12.760> often 00:23:12.900 --> 00:23:12.910 align:start position:0% accounts regularly and every so often 00:23:12.910 --> 00:23:15.150 align:start position:0% accounts regularly and every so often moving<00:23:13.570> if<00:23:14.140> you're<00:23:14.290> using<00:23:14.410> memory<00:23:14.620> card<00:23:14.860> up<00:23:15.010> if 00:23:15.150 --> 00:23:15.160 align:start position:0% moving if you're using memory card up if 00:23:15.160 --> 00:23:16.320 align:start position:0% moving if you're using memory card up if you're<00:23:15.370> not<00:23:15.520> if<00:23:15.730> you<00:23:15.790> just<00:23:15.880> using<00:23:16.120> a<00:23:16.150> mnemonic 00:23:16.320 --> 00:23:16.330 align:start position:0% you're not if you just using a mnemonic 00:23:16.330 --> 00:23:17.700 align:start position:0% you're not if you just using a mnemonic it<00:23:16.630> doesn't<00:23:16.870> matter<00:23:16.990> it's<00:23:17.170> already<00:23:17.470> as 00:23:17.700 --> 00:23:17.710 align:start position:0% it doesn't matter it's already as 00:23:17.710 --> 00:23:20.550 align:start position:0% it doesn't matter it's already as insecure<00:23:18.070> some<00:23:18.400> of<00:23:18.490> you<00:23:18.810> but<00:23:19.810> if<00:23:20.050> you<00:23:20.380> already 00:23:20.550 --> 00:23:20.560 align:start position:0% insecure some of you but if you already 00:23:20.560 --> 00:23:22.950 align:start position:0% insecure some of you but if you already have<00:23:20.860> ever<00:23:20.980> heard<00:23:21.570> things<00:23:22.570> like<00:23:22.750> this<00:23:22.810> for 00:23:22.950 --> 00:23:22.960 align:start position:0% have ever heard things like this for 00:23:22.960 --> 00:23:24.270 align:start position:0% have ever heard things like this for this<00:23:23.080> purpose<00:23:23.380> you<00:23:23.860> should<00:23:23.980> absolutely<00:23:24.070> be 00:23:24.270 --> 00:23:24.280 align:start position:0% this purpose you should absolutely be 00:23:24.280 --> 00:23:27.750 align:start position:0% this purpose you should absolutely be bravely<00:23:24.580> removing<00:23:25.090> your<00:23:25.210> funds<00:23:25.420> just<00:23:26.020> to<00:23:26.760> kind 00:23:27.750 --> 00:23:27.760 align:start position:0% bravely removing your funds just to kind 00:23:27.760 --> 00:23:30.600 align:start position:0% bravely removing your funds just to kind of<00:23:27.820> stay<00:23:28.330> up<00:23:28.750> to<00:23:28.900> date<00:23:29.040> the<00:23:30.040> other<00:23:30.160> thing<00:23:30.550> I 00:23:30.600 --> 00:23:30.610 align:start position:0% of stay up to date the other thing I 00:23:30.610 --> 00:23:32.010 align:start position:0% of stay up to date the other thing I recommend<00:23:30.760> is<00:23:31.060> going<00:23:31.480> into<00:23:31.720> the<00:23:31.780> contract 00:23:32.010 --> 00:23:32.020 align:start position:0% recommend is going into the contract 00:23:32.020 --> 00:23:37.270 align:start position:0% recommend is going into the contract wall<00:23:32.320> you<00:23:32.500> really<00:23:32.710> care<00:23:32.920> about<00:23:33.480> yes<00:23:34.480> I<00:23:34.800> think 00:23:37.270 --> 00:23:37.280 align:start position:0% wall you really care about yes I think 00:23:37.280 --> 00:23:40.640 align:start position:0% wall you really care about yes I think awesome<00:23:38.280> I<00:23:38.430> think<00:23:38.460> I'm<00:23:38.730> also<00:23:39.090> from<00:23:39.480> time<00:23:39.750> but 00:23:40.640 --> 00:23:40.650 align:start position:0% awesome I think I'm also from time but 00:23:40.650 --> 00:23:44.930 align:start position:0% awesome I think I'm also from time but there's<00:23:41.070> one<00:23:41.430> more<00:23:41.640> question<00:23:43.040> okay<00:23:44.040> come<00:23:44.850> on 00:23:44.930 --> 00:23:44.940 align:start position:0% there's one more question okay come on 00:23:44.940 --> 00:23:53.600 align:start position:0% there's one more question okay come on Martin<00:23:45.300> yes<00:23:50.960> what<00:23:51.960> no<00:23:52.920> it<00:23:53.070> does<00:23:53.220> not<00:23:53.370> it<00:23:53.430> will 00:23:53.600 --> 00:23:53.610 align:start position:0% Martin yes what no it does not it will 00:23:53.610 --> 00:23:57.260 align:start position:0% Martin yes what no it does not it will soon<00:23:54.050> but<00:23:55.050> on<00:23:55.620> the<00:23:55.710> program<00:23:56.090> Chanti<00:23:57.090> was<00:23:57.210> the 00:23:57.260 --> 00:23:57.270 align:start position:0% soon but on the program Chanti was the 00:23:57.270 --> 00:24:00.590 align:start position:0% soon but on the program Chanti was the one<00:23:57.390> thing<00:23:57.510> that<00:23:57.570> value<00:23:57.990> to<00:23:58.280> them<00:23:59.390> okay 00:24:00.590 --> 00:24:00.600 align:start position:0% one thing that value to them okay 00:24:00.600 --> 00:24:03.380 align:start position:0% one thing that value to them okay how<00:24:00.780> does<00:24:00.930> it<00:24:00.960> work<00:24:01.080> funded<00:24:01.610> so<00:24:02.610> that's<00:24:03.090> right 00:24:03.380 --> 00:24:03.390 align:start position:0% how does it work funded so that's right 00:24:03.390 --> 00:24:06.350 align:start position:0% how does it work funded so that's right now<00:24:03.540> I'm<00:24:03.810> actually<00:24:04.320> officially<00:24:04.800> back<00:24:05.460> now<00:24:05.670> so 00:24:06.350 --> 00:24:06.360 align:start position:0% now I'm actually officially back now so 00:24:06.360 --> 00:24:08.120 align:start position:0% now I'm actually officially back now so the<00:24:06.600> EF<00:24:06.870> is<00:24:07.020> like<00:24:07.170> helping<00:24:07.470> keep<00:24:07.800> this<00:24:07.950> thing 00:24:08.120 --> 00:24:08.130 align:start position:0% the EF is like helping keep this thing 00:24:08.130 --> 00:24:10.670 align:start position:0% the EF is like helping keep this thing going<00:24:08.370> up<00:24:09.150> until<00:24:09.480> then<00:24:09.600> the<00:24:09.720> EF<00:24:09.930> rented<00:24:10.440> a<00:24:10.530> few 00:24:10.670 --> 00:24:10.680 align:start position:0% going up until then the EF rented a few 00:24:10.680 --> 00:24:12.640 align:start position:0% going up until then the EF rented a few grants<00:24:10.920> I<00:24:11.220> received<00:24:11.640> grants<00:24:11.970> from<00:24:12.030> a<00:24:12.390> on 00:24:12.640 --> 00:24:12.650 align:start position:0% grants I received grants from a on 00:24:12.650 --> 00:24:15.140 align:start position:0% grants I received grants from a on there's<00:24:13.650> an<00:24:13.740> a<00:24:13.830> on<00:24:14.010> port<00:24:14.310> this<00:24:14.520> as<00:24:14.820> well<00:24:15.030> which 00:24:15.140 --> 00:24:15.150 align:start position:0% there's an a on port this as well which 00:24:15.150 --> 00:24:16.520 align:start position:0% there's an a on port this as well which I<00:24:15.240> wrote<00:24:15.390> so<00:24:15.630> that<00:24:15.780> helped<00:24:15.990> fund<00:24:16.230> a<00:24:16.290> lot<00:24:16.410> of 00:24:16.520 --> 00:24:16.530 align:start position:0% I wrote so that helped fund a lot of 00:24:16.530 --> 00:24:19.310 align:start position:0% I wrote so that helped fund a lot of this<00:24:16.650> especially<00:24:17.520> the<00:24:17.880> v5<00:24:18.210> stuff<00:24:18.570> and<00:24:18.780> good 00:24:19.310 --> 00:24:19.320 align:start position:0% this especially the v5 stuff and good 00:24:19.320 --> 00:24:21.110 align:start position:0% this especially the v5 stuff and good point<00:24:19.560> it<00:24:19.800> coin<00:24:20.070> is<00:24:20.280> phenomenal<00:24:20.850> you're<00:24:21.000> not 00:24:21.110 --> 00:24:21.120 align:start position:0% point it coin is phenomenal you're not 00:24:21.120 --> 00:24:23.000 align:start position:0% point it coin is phenomenal you're not meant<00:24:21.270> to<00:24:21.330> learn<00:24:21.510> to<00:24:21.660> become<00:24:22.410> familiar<00:24:22.680> with 00:24:23.000 --> 00:24:23.010 align:start position:0% meant to learn to become familiar with 00:24:23.010 --> 00:24:26.090 align:start position:0% meant to learn to become familiar with it<00:24:23.130> it's<00:24:23.280> freaking<00:24:23.760> awesome<00:24:24.920> also<00:24:25.920> I'm<00:24:26.040> sure 00:24:26.090 --> 00:24:26.100 align:start position:0% it it's freaking awesome also I'm sure 00:24:26.100 --> 00:24:27.470 align:start position:0% it it's freaking awesome also I'm sure everyone<00:24:26.520> here<00:24:26.670> is<00:24:26.790> familiar<00:24:26.910> with<00:24:27.150> it<00:24:27.300> so 00:24:27.470 --> 00:24:27.480 align:start position:0% everyone here is familiar with it so 00:24:27.480 --> 00:24:36.220 align:start position:0% everyone here is familiar with it so that's<00:24:27.930> a<00:24:31.310> thank<00:24:32.310> you 00:24:36.220 --> 00:24:36.230 align:start position:0% 00:24:36.230 --> 00:24:42.380 align:start position:0% [Applause]