WEBVTT Kind: captions Language: en 00:00:20.700 --> 00:00:24.620 align:start position:0% so<00:00:21.700> uh<00:00:22.169> Martin<00:00:23.169> sanda<00:00:23.470> going<00:00:23.890> to<00:00:24.099> talk<00:00:24.279> about 00:00:24.620 --> 00:00:24.630 align:start position:0% so uh Martin sanda going to talk about 00:00:24.630 --> 00:00:32.460 align:start position:0% so uh Martin sanda going to talk about ethereum<00:00:25.630> security<00:00:27.539> so<00:00:30.660> cool<00:00:31.660> can<00:00:32.199> we<00:00:32.230> turn 00:00:32.460 --> 00:00:32.470 align:start position:0% ethereum security so cool can we turn 00:00:32.470 --> 00:00:37.320 align:start position:0% ethereum security so cool can we turn this<00:00:32.650> a<00:00:32.710> volume<00:00:33.250> up<00:00:33.370> a<00:00:33.489> little<00:00:33.670> bit<00:00:33.879> please<00:00:36.330> to 00:00:37.320 --> 00:00:37.330 align:start position:0% this a volume up a little bit please to 00:00:37.330 --> 00:00:39.660 align:start position:0% this a volume up a little bit please to start<00:00:37.660> off<00:00:37.809> with<00:00:38.080> security<00:00:39.010> it's<00:00:39.340> like<00:00:39.489> this 00:00:39.660 --> 00:00:39.670 align:start position:0% start off with security it's like this 00:00:39.670 --> 00:00:44.880 align:start position:0% start off with security it's like this big<00:00:40.150> pretty<00:00:41.050> vague<00:00:41.379> term<00:00:43.350> so<00:00:44.350> what<00:00:44.500> is<00:00:44.650> it<00:00:44.800> so 00:00:44.880 --> 00:00:44.890 align:start position:0% big pretty vague term so what is it so 00:00:44.890 --> 00:00:46.920 align:start position:0% big pretty vague term so what is it so when<00:00:45.040> we<00:00:45.129> talk<00:00:45.280> about<00:00:45.370> security<00:00:45.820> is<00:00:46.510> easier 00:00:46.920 --> 00:00:46.930 align:start position:0% when we talk about security is easier 00:00:46.930 --> 00:00:49.500 align:start position:0% when we talk about security is easier sometimes<00:00:47.170> to<00:00:47.440> think<00:00:47.920> about<00:00:48.129> risk<00:00:48.460> and<00:00:48.850> the 00:00:49.500 --> 00:00:49.510 align:start position:0% sometimes to think about risk and the 00:00:49.510 --> 00:00:52.859 align:start position:0% sometimes to think about risk and the risk<00:00:49.690> is<00:00:50.820> something<00:00:51.820> which<00:00:52.360> could 00:00:52.859 --> 00:00:52.869 align:start position:0% risk is something which could 00:00:52.869 --> 00:00:54.719 align:start position:0% risk is something which could potentially<00:00:53.229> cause<00:00:53.799> a<00:00:53.830> loss<00:00:54.129> a<00:00:54.430> risk 00:00:54.719 --> 00:00:54.729 align:start position:0% potentially cause a loss a risk 00:00:54.729 --> 00:00:56.640 align:start position:0% potentially cause a loss a risk something<00:00:55.210> a<00:00:55.540> possible<00:00:55.989> event<00:00:56.199> which<00:00:56.440> would 00:00:56.640 --> 00:00:56.650 align:start position:0% something a possible event which would 00:00:56.650 --> 00:01:00.869 align:start position:0% something a possible event which would be<00:00:56.799> bad<00:00:57.040> and<00:00:58.140> typically<00:00:59.140> the<00:00:59.830> risk<00:01:00.040> level 00:01:00.869 --> 00:01:00.879 align:start position:0% be bad and typically the risk level 00:01:00.879 --> 00:01:02.820 align:start position:0% be bad and typically the risk level depends<00:01:01.390> on<00:01:01.570> the<00:01:01.720> likelihood<00:01:02.290> of<00:01:02.320> that<00:01:02.500> bad 00:01:02.820 --> 00:01:02.830 align:start position:0% depends on the likelihood of that bad 00:01:02.830 --> 00:01:06.359 align:start position:0% depends on the likelihood of that bad thing<00:01:03.159> occurring<00:01:03.519> and<00:01:04.199> the<00:01:05.199> impacts<00:01:05.860> if<00:01:06.040> that 00:01:06.359 --> 00:01:06.369 align:start position:0% thing occurring and the impacts if that 00:01:06.369 --> 00:01:10.770 align:start position:0% thing occurring and the impacts if that bad<00:01:06.580> thing<00:01:06.909> did<00:01:07.240> occur<00:01:08.430> so<00:01:09.430> if<00:01:10.390> we<00:01:10.540> want<00:01:10.720> to 00:01:10.770 --> 00:01:10.780 align:start position:0% bad thing did occur so if we want to 00:01:10.780 --> 00:01:12.870 align:start position:0% bad thing did occur so if we want to reduce<00:01:11.140> risk<00:01:11.500> we<00:01:11.860> can<00:01:12.070> reduce<00:01:12.400> the<00:01:12.700> likelihood 00:01:12.870 --> 00:01:12.880 align:start position:0% reduce risk we can reduce the likelihood 00:01:12.880 --> 00:01:15.539 align:start position:0% reduce risk we can reduce the likelihood that<00:01:13.540> the<00:01:13.990> bad<00:01:14.140> thing<00:01:14.380> happens<00:01:14.770> or<00:01:15.250> we<00:01:15.400> can 00:01:15.539 --> 00:01:15.549 align:start position:0% that the bad thing happens or we can 00:01:15.549 --> 00:01:19.230 align:start position:0% that the bad thing happens or we can reduce<00:01:15.880> the<00:01:16.330> impact<00:01:16.479> if<00:01:16.960> it<00:01:17.080> occurs<00:01:18.000> so<00:01:19.000> we 00:01:19.230 --> 00:01:19.240 align:start position:0% reduce the impact if it occurs so we 00:01:19.240 --> 00:01:20.910 align:start position:0% reduce the impact if it occurs so we reduce<00:01:19.390> risk<00:01:19.780> that<00:01:19.960> way<00:01:20.170> we<00:01:20.649> increase 00:01:20.910 --> 00:01:20.920 align:start position:0% reduce risk that way we increase 00:01:20.920 --> 00:01:24.440 align:start position:0% reduce risk that way we increase security<00:01:21.869> common<00:01:22.869> ways<00:01:23.020> to<00:01:23.049> do<00:01:23.409> that<00:01:23.619> is<00:01:23.950> to 00:01:24.440 --> 00:01:24.450 align:start position:0% security common ways to do that is to 00:01:24.450 --> 00:01:29.609 align:start position:0% security common ways to do that is to separate<00:01:25.450> things<00:01:26.369> isolate<00:01:27.369> them<00:01:27.640> and<00:01:28.619> apply 00:01:29.609 --> 00:01:29.619 align:start position:0% separate things isolate them and apply 00:01:29.619 --> 00:01:37.109 align:start position:0% separate things isolate them and apply several<00:01:30.009> layers<00:01:30.249> of<00:01:30.640> Defense<00:01:33.659> and<00:01:36.119> some 00:01:37.109 --> 00:01:37.119 align:start position:0% several layers of Defense and some 00:01:37.119 --> 00:01:39.480 align:start position:0% several layers of Defense and some typical<00:01:37.570> security<00:01:37.840> concerns<00:01:38.530> in<00:01:38.829> the<00:01:38.950> overall 00:01:39.480 --> 00:01:39.490 align:start position:0% typical security concerns in the overall 00:01:39.490 --> 00:01:42.810 align:start position:0% typical security concerns in the overall etherium<00:01:40.240> ecosystem<00:01:40.899> it's<00:01:41.530> like<00:01:41.859> and<00:01:42.280> uses 00:01:42.810 --> 00:01:42.820 align:start position:0% etherium ecosystem it's like and uses 00:01:42.820 --> 00:01:44.940 align:start position:0% etherium ecosystem it's like and uses security<00:01:43.390> when<00:01:43.659> you<00:01:43.780> have<00:01:43.960> the<00:01:44.109> wallets<00:01:44.590> and 00:01:44.940 --> 00:01:44.950 align:start position:0% security when you have the wallets and 00:01:44.950 --> 00:01:47.929 align:start position:0% security when you have the wallets and interact<00:01:45.490> with<00:01:45.719> contracts<00:01:46.719> and<00:01:46.840> daps 00:01:47.929 --> 00:01:47.939 align:start position:0% interact with contracts and daps 00:01:47.939 --> 00:01:50.789 align:start position:0% interact with contracts and daps and<00:01:48.939> also<00:01:49.210> put<00:01:49.359> developers<00:01:49.899> how<00:01:50.380> do<00:01:50.439> I<00:01:50.590> develop 00:01:50.789 --> 00:01:50.799 align:start position:0% and also put developers how do I develop 00:01:50.799 --> 00:01:54.389 align:start position:0% and also put developers how do I develop secure<00:01:51.399> contracts<00:01:52.299> and<00:01:52.630> apps<00:01:52.899> and<00:01:53.799> on<00:01:54.039> a<00:01:54.069> macro 00:01:54.389 --> 00:01:54.399 align:start position:0% secure contracts and apps and on a macro 00:01:54.399 --> 00:02:00.139 align:start position:0% secure contracts and apps and on a macro scale<00:01:55.560> the<00:01:56.560> network<00:01:56.979> security<00:01:58.170> overall<00:01:59.170> and 00:02:00.139 --> 00:02:00.149 align:start position:0% scale the network security overall and 00:02:00.149 --> 00:02:02.370 align:start position:0% scale the network security overall and these<00:02:01.149> are<00:02:01.359> all<00:02:01.450> different<00:02:01.659> security 00:02:02.370 --> 00:02:02.380 align:start position:0% these are all different security 00:02:02.380 --> 00:02:08.490 align:start position:0% these are all different security concerns<00:02:04.139> and<00:02:05.139> the<00:02:05.889> threats<00:02:06.280> they<00:02:06.929> vary<00:02:07.929> some 00:02:08.490 --> 00:02:08.500 align:start position:0% concerns and the threats they vary some 00:02:08.500 --> 00:02:11.630 align:start position:0% concerns and the threats they vary some of<00:02:08.530> them<00:02:08.740> are<00:02:08.920> like<00:02:09.280> game<00:02:09.520> theoretical 00:02:11.630 --> 00:02:11.640 align:start position:0% of them are like game theoretical 00:02:11.640 --> 00:02:16.860 align:start position:0% of them are like game theoretical incentivization<00:02:12.640> of<00:02:12.790> miners<00:02:13.330> or<00:02:15.870> third 00:02:16.860 --> 00:02:16.870 align:start position:0% incentivization of miners or third 00:02:16.870 --> 00:02:21.970 align:start position:0% incentivization of miners or third exploits<00:02:18.090> or<00:02:19.090> protocol 00:02:21.970 --> 00:02:21.980 align:start position:0% exploits or protocol 00:02:21.980 --> 00:02:24.369 align:start position:0% exploits or protocol yeah<00:02:22.580> stuff<00:02:23.300> in<00:02:23.450> the<00:02:23.540> protocol<00:02:23.989> which<00:02:24.110> makes 00:02:24.369 --> 00:02:24.379 align:start position:0% yeah stuff in the protocol which makes 00:02:24.379 --> 00:02:27.699 align:start position:0% yeah stuff in the protocol which makes the<00:02:25.090> communication<00:02:26.090> between<00:02:26.569> nodes<00:02:26.989> lag 00:02:27.699 --> 00:02:27.709 align:start position:0% the communication between nodes lag 00:02:27.709 --> 00:02:31.089 align:start position:0% the communication between nodes lag stuff<00:02:28.099> like<00:02:28.250> that<00:02:28.459> is<00:02:28.870> very<00:02:29.870> wide<00:02:30.319> variety<00:02:30.590> of 00:02:31.089 --> 00:02:31.099 align:start position:0% stuff like that is very wide variety of 00:02:31.099 --> 00:02:35.320 align:start position:0% stuff like that is very wide variety of threats<00:02:33.489> and<00:02:34.489> I'm<00:02:34.580> gonna<00:02:34.700> start<00:02:35.000> with<00:02:35.150> end 00:02:35.320 --> 00:02:35.330 align:start position:0% threats and I'm gonna start with end 00:02:35.330 --> 00:02:39.550 align:start position:0% threats and I'm gonna start with end users<00:02:35.950> dealing<00:02:36.950> with<00:02:37.069> wallets<00:02:38.230> so<00:02:39.230> will<00:02:39.500> you 00:02:39.550 --> 00:02:39.560 align:start position:0% users dealing with wallets so will you 00:02:39.560 --> 00:02:42.610 align:start position:0% users dealing with wallets so will you deal<00:02:39.739> with<00:02:39.769> wallets<00:02:40.280> a<00:02:41.239> good<00:02:42.019> model<00:02:42.440> for 00:02:42.610 --> 00:02:42.620 align:start position:0% deal with wallets a good model for 00:02:42.620 --> 00:02:44.800 align:start position:0% deal with wallets a good model for security<00:02:43.220> is<00:02:43.280> to<00:02:43.430> isolate<00:02:43.880> them<00:02:44.090> have<00:02:44.480> hot 00:02:44.800 --> 00:02:44.810 align:start position:0% security is to isolate them have hot 00:02:44.810 --> 00:02:47.830 align:start position:0% security is to isolate them have hot cold<00:02:45.170> and<00:02:45.440> frozen<00:02:46.120> where<00:02:47.120> hope<00:02:47.360> wallet<00:02:47.720> is 00:02:47.830 --> 00:02:47.840 align:start position:0% cold and frozen where hope wallet is 00:02:47.840 --> 00:02:51.880 align:start position:0% cold and frozen where hope wallet is what<00:02:47.989> we'd<00:02:48.170> use<00:02:48.470> for<00:02:48.860> everyday<00:02:49.220> cash<00:02:50.349> on<00:02:51.349> your 00:02:51.880 --> 00:02:51.890 align:start position:0% what we'd use for everyday cash on your 00:02:51.890 --> 00:02:53.890 align:start position:0% what we'd use for everyday cash on your everyday<00:02:52.190> computer<00:02:52.760> interacting<00:02:53.480> with<00:02:53.660> that 00:02:53.890 --> 00:02:53.900 align:start position:0% everyday computer interacting with that 00:02:53.900 --> 00:02:57.400 align:start position:0% everyday computer interacting with that or<00:02:54.349> whatever<00:02:54.890> you<00:02:55.099> do<00:02:55.190> with<00:02:55.220> your<00:02:55.370> ether<00:02:56.410> and 00:02:57.400 --> 00:02:57.410 align:start position:0% or whatever you do with your ether and 00:02:57.410 --> 00:02:59.620 align:start position:0% or whatever you do with your ether and then<00:02:57.560> have<00:02:57.709> a<00:02:57.739> cold<00:02:58.670> wallet<00:02:59.060> which<00:02:59.330> you<00:02:59.480> would 00:02:59.620 --> 00:02:59.630 align:start position:0% then have a cold wallet which you would 00:02:59.630 --> 00:03:01.750 align:start position:0% then have a cold wallet which you would more<00:02:59.840> consider<00:03:00.380> your<00:03:00.530> bank<00:03:00.799> if<00:03:01.220> you<00:03:01.280> need<00:03:01.579> more 00:03:01.750 --> 00:03:01.760 align:start position:0% more consider your bank if you need more 00:03:01.760 --> 00:03:03.910 align:start position:0% more consider your bank if you need more money<00:03:02.000> in<00:03:02.329> your<00:03:02.360> wallet<00:03:02.569> you<00:03:03.049> take<00:03:03.590> some<00:03:03.769> money 00:03:03.910 --> 00:03:03.920 align:start position:0% money in your wallet you take some money 00:03:03.920 --> 00:03:06.809 align:start position:0% money in your wallet you take some money from<00:03:04.040> the<00:03:04.280> bank<00:03:04.310> and<00:03:04.700> put<00:03:04.760> it<00:03:04.970> in<00:03:05.120> the<00:03:05.239> hold<00:03:05.599> and 00:03:06.809 --> 00:03:06.819 align:start position:0% from the bank and put it in the hold and 00:03:06.819 --> 00:03:09.370 align:start position:0% from the bank and put it in the hold and you<00:03:07.819> would<00:03:08.000> naturally<00:03:08.269> need<00:03:08.660> to<00:03:08.810> backup<00:03:09.049> of 00:03:09.370 --> 00:03:09.380 align:start position:0% you would naturally need to backup of 00:03:09.380 --> 00:03:10.839 align:start position:0% you would naturally need to backup of the<00:03:09.470> cold<00:03:09.709> wallets<00:03:10.099> and<00:03:10.310> that's<00:03:10.459> what<00:03:10.610> I<00:03:10.640> call 00:03:10.839 --> 00:03:10.849 align:start position:0% the cold wallets and that's what I call 00:03:10.849 --> 00:03:13.839 align:start position:0% the cold wallets and that's what I call the<00:03:10.970> frozen<00:03:11.510> so<00:03:12.500> then<00:03:13.010> you<00:03:13.190> have<00:03:13.370> done<00:03:13.730> the 00:03:13.839 --> 00:03:13.849 align:start position:0% the frozen so then you have done the 00:03:13.849 --> 00:03:15.729 align:start position:0% the frozen so then you have done the reduction<00:03:14.299> you're<00:03:14.450> done<00:03:14.630> reduce<00:03:15.170> the<00:03:15.349> impact 00:03:15.729 --> 00:03:15.739 align:start position:0% reduction you're done reduce the impact 00:03:15.739 --> 00:03:17.380 align:start position:0% reduction you're done reduce the impact of<00:03:15.860> the<00:03:15.920> hot<00:03:16.099> would<00:03:16.340> compromise<00:03:16.790> you<00:03:17.120> reduce 00:03:17.380 --> 00:03:17.390 align:start position:0% of the hot would compromise you reduce 00:03:17.390 --> 00:03:18.789 align:start position:0% of the hot would compromise you reduce the<00:03:17.540> likelihood<00:03:17.720> of<00:03:18.079> a<00:03:18.170> cold<00:03:18.440> wallet 00:03:18.789 --> 00:03:18.799 align:start position:0% the likelihood of a cold wallet 00:03:18.799 --> 00:03:21.580 align:start position:0% the likelihood of a cold wallet compromise<00:03:19.280> and<00:03:19.790> you<00:03:19.819> do<00:03:20.180> the<00:03:20.660> impact<00:03:21.079> in<00:03:21.380> case 00:03:21.580 --> 00:03:21.590 align:start position:0% compromise and you do the impact in case 00:03:21.590 --> 00:03:27.670 align:start position:0% compromise and you do the impact in case you're<00:03:21.860> cold<00:03:22.190> wallets<00:03:22.579> burns<00:03:23.540> up<00:03:26.290> and<00:03:27.290> if<00:03:27.590> you 00:03:27.670 --> 00:03:27.680 align:start position:0% you're cold wallets burns up and if you 00:03:27.680 --> 00:03:29.229 align:start position:0% you're cold wallets burns up and if you don't<00:03:27.889> deal<00:03:28.160> with<00:03:28.370> wallets<00:03:28.790> maybe<00:03:29.060> you're 00:03:29.229 --> 00:03:29.239 align:start position:0% don't deal with wallets maybe you're 00:03:29.239 --> 00:03:30.910 align:start position:0% don't deal with wallets maybe you're having<00:03:29.389> the<00:03:29.600> money<00:03:29.750> on<00:03:29.959> an<00:03:30.049> exchange<00:03:30.470> which<00:03:30.799> is 00:03:30.910 --> 00:03:30.920 align:start position:0% having the money on an exchange which is 00:03:30.920 --> 00:03:32.800 align:start position:0% having the money on an exchange which is perfectly<00:03:31.340> fine<00:03:31.430> if<00:03:31.910> your<00:03:32.090> money<00:03:32.389> that<00:03:32.630> you 00:03:32.800 --> 00:03:32.810 align:start position:0% perfectly fine if your money that you 00:03:32.810 --> 00:03:35.199 align:start position:0% perfectly fine if your money that you have<00:03:33.109> accepted<00:03:33.680> that<00:03:33.709> you<00:03:33.920> may<00:03:34.130> lose<00:03:34.430> you 00:03:35.199 --> 00:03:35.209 align:start position:0% have accepted that you may lose you 00:03:35.209 --> 00:03:39.340 align:start position:0% have accepted that you may lose you should<00:03:35.450> not<00:03:35.630> store<00:03:35.989> more<00:03:36.319> than<00:03:36.620> you<00:03:37.780> have<00:03:38.780> then 00:03:39.340 --> 00:03:39.350 align:start position:0% should not store more than you have then 00:03:39.350 --> 00:03:44.460 align:start position:0% should not store more than you have then you<00:03:39.440> can<00:03:39.590> accept<00:03:39.920> the<00:03:40.010> risk<00:03:40.040> of<00:03:40.370> losing 00:03:44.460 --> 00:03:44.470 align:start position:0% 00:03:44.470 --> 00:03:47.319 align:start position:0% electronic<00:03:45.470> wallets<00:03:45.880> if<00:03:46.880> you<00:03:46.970> put<00:03:47.239> together 00:03:47.319 --> 00:03:47.329 align:start position:0% electronic wallets if you put together 00:03:47.329 --> 00:03:49.599 align:start position:0% electronic wallets if you put together kind<00:03:47.780> of<00:03:47.900> a<00:03:48.019> feature<00:03:48.290> list<00:03:48.620> of<00:03:48.980> things<00:03:49.220> that<00:03:49.489> we 00:03:49.599 --> 00:03:49.609 align:start position:0% kind of a feature list of things that we 00:03:49.609 --> 00:03:52.120 align:start position:0% kind of a feature list of things that we want<00:03:49.850> from<00:03:50.030> a<00:03:50.150> cold<00:03:50.420> electronic<00:03:50.989> wallet<00:03:51.290> is 00:03:52.120 --> 00:03:52.130 align:start position:0% want from a cold electronic wallet is 00:03:52.130 --> 00:03:53.559 align:start position:0% want from a cold electronic wallet is that<00:03:52.370> it<00:03:52.489> should<00:03:52.730> be<00:03:52.880> safe<00:03:53.120> to<00:03:53.359> use<00:03:53.389> with 00:03:53.559 --> 00:03:53.569 align:start position:0% that it should be safe to use with 00:03:53.569 --> 00:03:56.770 align:start position:0% that it should be safe to use with untrusted<00:03:54.380> devices<00:03:54.889> so<00:03:55.459> if<00:03:55.639> you're<00:03:55.880> using<00:03:56.540> an 00:03:56.770 --> 00:03:56.780 align:start position:0% untrusted devices so if you're using an 00:03:56.780 --> 00:03:59.620 align:start position:0% untrusted devices so if you're using an internet<00:03:57.170> kiosk<00:03:57.650> or<00:03:58.069> your<00:03:58.280> normal<00:03:59.150> laptop<00:03:59.299> has 00:03:59.620 --> 00:03:59.630 align:start position:0% internet kiosk or your normal laptop has 00:03:59.630 --> 00:04:02.319 align:start position:0% internet kiosk or your normal laptop has been<00:03:59.900> compromised<00:04:00.650> we<00:04:01.310> don't<00:04:01.489> want<00:04:01.670> that<00:04:01.910> to 00:04:02.319 --> 00:04:02.329 align:start position:0% been compromised we don't want that to 00:04:02.329 --> 00:04:04.479 align:start position:0% been compromised we don't want that to be<00:04:02.359> able<00:04:02.540> to<00:04:02.840> compromise<00:04:03.410> your<00:04:03.769> cold<00:04:03.980> wallets 00:04:04.479 --> 00:04:04.489 align:start position:0% be able to compromise your cold wallets 00:04:04.489 --> 00:04:08.050 align:start position:0% be able to compromise your cold wallets you<00:04:04.790> should<00:04:05.000> still<00:04:05.569> be<00:04:05.660> safe<00:04:05.840> to<00:04:05.989> use<00:04:06.019> and<00:04:07.060> if 00:04:08.050 --> 00:04:08.060 align:start position:0% you should still be safe to use and if 00:04:08.060 --> 00:04:09.490 align:start position:0% you should still be safe to use and if someone<00:04:08.480> should<00:04:08.630> steal<00:04:08.989> it 00:04:09.490 --> 00:04:09.500 align:start position:0% someone should steal it 00:04:09.500 --> 00:04:11.729 align:start position:0% someone should steal it we<00:04:09.680> wanted<00:04:09.950> to<00:04:10.099> resist<00:04:10.430> key<00:04:10.700> extraction 00:04:11.729 --> 00:04:11.739 align:start position:0% we wanted to resist key extraction 00:04:11.739 --> 00:04:18.420 align:start position:0% we wanted to resist key extraction typically<00:04:13.420> by<00:04:14.420> a<00:04:14.569> race<00:04:14.780> on<00:04:14.989> tamper<00:04:15.789> also<00:04:16.789> HSM<00:04:17.599> a 00:04:18.420 --> 00:04:18.430 align:start position:0% typically by a race on tamper also HSM a 00:04:18.430 --> 00:04:24.400 align:start position:0% typically by a race on tamper also HSM a secure<00:04:19.430> element<00:04:22.240> for<00:04:23.240> all<00:04:23.300> you<00:04:23.479> techno<00:04:24.139> maps 00:04:24.400 --> 00:04:24.410 align:start position:0% secure element for all you techno maps 00:04:24.410 --> 00:04:26.409 align:start position:0% secure element for all you techno maps traveling<00:04:24.950> in<00:04:25.010> the<00:04:25.070> world<00:04:25.220> is<00:04:25.700> good<00:04:26.090> if<00:04:26.240> it's 00:04:26.409 --> 00:04:26.419 align:start position:0% traveling in the world is good if it's 00:04:26.419 --> 00:04:28.180 align:start position:0% traveling in the world is good if it's small<00:04:27.020> enough<00:04:27.200> to<00:04:27.349> carry<00:04:27.560> in<00:04:27.620> your<00:04:27.740> pockets 00:04:28.180 --> 00:04:28.190 align:start position:0% small enough to carry in your pockets 00:04:28.190 --> 00:04:29.589 align:start position:0% small enough to carry in your pockets you<00:04:28.370> don't<00:04:28.550> have<00:04:28.669> to<00:04:28.789> leave<00:04:28.910> it<00:04:29.090> in<00:04:29.150> the<00:04:29.270> hotel 00:04:29.589 --> 00:04:29.599 align:start position:0% you don't have to leave it in the hotel 00:04:29.599 --> 00:04:34.480 align:start position:0% you don't have to leave it in the hotel room<00:04:32.080> there<00:04:33.080> are<00:04:33.229> some<00:04:33.590> of<00:04:33.800> these<00:04:33.919> products 00:04:34.480 --> 00:04:34.490 align:start position:0% room there are some of these products 00:04:34.490 --> 00:04:35.530 align:start position:0% room there are some of these products coming<00:04:34.729> up<00:04:34.820> the<00:04:34.970> legend<00:04:35.270> on 00:04:35.530 --> 00:04:35.540 align:start position:0% coming up the legend on 00:04:35.540 --> 00:04:38.950 align:start position:0% coming up the legend on has<00:04:35.870> been<00:04:35.990> released<00:04:37.510> truster<00:04:38.510> is<00:04:38.540> a<00:04:38.690> Bitcoin 00:04:38.950 --> 00:04:38.960 align:start position:0% has been released truster is a Bitcoin 00:04:38.960 --> 00:04:41.320 align:start position:0% has been released truster is a Bitcoin wallet<00:04:39.500> it's<00:04:40.280> going<00:04:40.550> they<00:04:41.000> have<00:04:41.030> announced 00:04:41.320 --> 00:04:41.330 align:start position:0% wallet it's going they have announced 00:04:41.330 --> 00:04:47.260 align:start position:0% wallet it's going they have announced the<00:04:41.720> terraeum<00:04:43.510> integration<00:04:45.340> USB<00:04:46.340> armory<00:04:46.790> this 00:04:47.260 --> 00:04:47.270 align:start position:0% the terraeum integration USB armory this 00:04:47.270 --> 00:04:50.950 align:start position:0% the terraeum integration USB armory this is<00:04:47.420> the<00:04:47.660> generic<00:04:48.050> computer<00:04:49.570> the<00:04:50.570> interesting 00:04:50.950 --> 00:04:50.960 align:start position:0% is the generic computer the interesting 00:04:50.960 --> 00:04:52.420 align:start position:0% is the generic computer the interesting part<00:04:51.200> of<00:04:51.290> it<00:04:51.410> is<00:04:51.530> that<00:04:51.560> when<00:04:51.830> you<00:04:51.920> plug<00:04:52.160> it<00:04:52.310> in 00:04:52.420 --> 00:04:52.430 align:start position:0% part of it is that when you plug it in 00:04:52.430 --> 00:04:55.570 align:start position:0% part of it is that when you plug it in it<00:04:52.960> spins<00:04:53.960> up<00:04:54.140> in<00:04:54.320> your<00:04:54.470> network<00:04:54.830> interface<00:04:55.010> so 00:04:55.570 --> 00:04:55.580 align:start position:0% it spins up in your network interface so 00:04:55.580 --> 00:04:57.700 align:start position:0% it spins up in your network interface so you<00:04:55.670> can<00:04:55.880> plug<00:04:56.480> it<00:04:56.600> in<00:04:56.720> in<00:04:56.870> USB<00:04:57.350> and<00:04:57.530> then<00:04:57.590> you 00:04:57.700 --> 00:04:57.710 align:start position:0% you can plug it in in USB and then you 00:04:57.710 --> 00:05:01.450 align:start position:0% you can plug it in in USB and then you can<00:04:57.860> SSH<00:04:58.310> into<00:04:58.640> it<00:04:59.980> or<00:05:00.980> will<00:05:01.190> is<00:05:01.340> an 00:05:01.450 --> 00:05:01.460 align:start position:0% can SSH into it or will is an 00:05:01.460 --> 00:05:04.360 align:start position:0% can SSH into it or will is an open-source<00:05:02.470> secure<00:05:03.470> computer<00:05:03.950> and<00:05:04.040> attempt 00:05:04.360 --> 00:05:04.370 align:start position:0% open-source secure computer and attempt 00:05:04.370 --> 00:05:06.340 align:start position:0% open-source secure computer and attempt at<00:05:04.490> a<00:05:04.730> secure<00:05:05.090> computer<00:05:05.300> it<00:05:05.600> completely<00:05:06.050> open 00:05:06.340 --> 00:05:06.350 align:start position:0% at a secure computer it completely open 00:05:06.350 --> 00:05:12.430 align:start position:0% at a secure computer it completely open and<00:05:08.920> moving<00:05:09.920> on<00:05:10.100> frozen<00:05:10.520> so<00:05:11.150> the<00:05:11.810> backup<00:05:12.020> if 00:05:12.430 --> 00:05:12.440 align:start position:0% and moving on frozen so the backup if 00:05:12.440 --> 00:05:14.110 align:start position:0% and moving on frozen so the backup if you<00:05:12.560> want<00:05:12.740> to<00:05:12.830> backup<00:05:13.010> your<00:05:13.220> cold<00:05:13.580> wallet<00:05:13.910> you 00:05:14.110 --> 00:05:14.120 align:start position:0% you want to backup your cold wallet you 00:05:14.120 --> 00:05:16.030 align:start position:0% you want to backup your cold wallet you want<00:05:14.270> to<00:05:14.330> do<00:05:14.390> it<00:05:14.510> securely<00:05:14.870> you<00:05:15.710> don't<00:05:15.890> want 00:05:16.030 --> 00:05:16.040 align:start position:0% want to do it securely you don't want 00:05:16.040 --> 00:05:18.730 align:start position:0% want to do it securely you don't want the<00:05:16.220> the<00:05:16.700> seeds<00:05:17.210> or<00:05:17.600> the<00:05:17.660> private<00:05:18.260> key<00:05:18.440> to<00:05:18.470> be 00:05:18.730 --> 00:05:18.740 align:start position:0% the the seeds or the private key to be 00:05:18.740 --> 00:05:24.400 align:start position:0% the the seeds or the private key to be able<00:05:18.830> to<00:05:18.980> burn<00:05:19.880> or<00:05:21.100> get<00:05:22.100> broken<00:05:22.780> you<00:05:23.780> could<00:05:24.080> put 00:05:24.400 --> 00:05:24.410 align:start position:0% able to burn or get broken you could put 00:05:24.410 --> 00:05:25.740 align:start position:0% able to burn or get broken you could put it<00:05:24.530> in<00:05:24.650> the<00:05:24.710> cloud 00:05:25.740 --> 00:05:25.750 align:start position:0% it in the cloud 00:05:25.750 --> 00:05:30.340 align:start position:0% it in the cloud cryptographic<00:05:27.490> encrypted<00:05:28.490> and<00:05:29.020> I<00:05:30.020> only<00:05:30.140> have 00:05:30.340 --> 00:05:30.350 align:start position:0% cryptographic encrypted and I only have 00:05:30.350 --> 00:05:35.170 align:start position:0% cryptographic encrypted and I only have a<00:05:30.380> very<00:05:31.250> hard<00:05:31.910> password<00:05:33.550> which<00:05:34.550> may<00:05:34.880> not<00:05:35.000> be<00:05:35.150> a 00:05:35.170 --> 00:05:35.180 align:start position:0% a very hard password which may not be a 00:05:35.180 --> 00:05:36.670 align:start position:0% a very hard password which may not be a good<00:05:35.360> idea<00:05:35.660> because<00:05:35.840> you<00:05:36.110> can<00:05:36.140> lose<00:05:36.470> your 00:05:36.670 --> 00:05:36.680 align:start position:0% good idea because you can lose your 00:05:36.680 --> 00:05:39.060 align:start position:0% good idea because you can lose your memory<00:05:37.010> or<00:05:37.100> got<00:05:37.250> hit<00:05:37.400> by<00:05:37.580> a<00:05:37.610> car<00:05:37.850> or<00:05:37.880> something 00:05:39.060 --> 00:05:39.070 align:start position:0% memory or got hit by a car or something 00:05:39.070 --> 00:05:41.440 align:start position:0% memory or got hit by a car or something so<00:05:40.070> one<00:05:40.250> solution<00:05:40.430> is<00:05:40.820> to<00:05:40.850> use<00:05:40.970> something<00:05:41.300> like 00:05:41.440 --> 00:05:41.450 align:start position:0% so one solution is to use something like 00:05:41.450 --> 00:05:44.140 align:start position:0% so one solution is to use something like the<00:05:41.660> crypto<00:05:41.990> steal<00:05:42.290> and<00:05:42.670> put<00:05:43.670> it<00:05:43.760> in<00:05:43.880> a<00:05:43.970> bank 00:05:44.140 --> 00:05:44.150 align:start position:0% the crypto steal and put it in a bank 00:05:44.150 --> 00:05:47.500 align:start position:0% the crypto steal and put it in a bank vault<00:05:44.270> or<00:05:45.190> take<00:05:46.190> it<00:05:46.310> down<00:05:46.340> in<00:05:46.670> the<00:05:46.760> backyard<00:05:46.940> in 00:05:47.500 --> 00:05:47.510 align:start position:0% vault or take it down in the backyard in 00:05:47.510 --> 00:05:52.000 align:start position:0% vault or take it down in the backyard in the<00:05:47.750> outback<00:05:49.690> or<00:05:50.690> you<00:05:50.930> can<00:05:51.140> just<00:05:51.320> maybe<00:05:51.650> buy<00:05:51.950> an 00:05:52.000 --> 00:05:52.010 align:start position:0% the outback or you can just maybe buy an 00:05:52.010 --> 00:05:54.810 align:start position:0% the outback or you can just maybe buy an old<00:05:52.220> laptop<00:05:52.660> this<00:05:53.660> is<00:05:53.810> a<00:05:53.840> cheaper<00:05:54.230> solution 00:05:54.810 --> 00:05:54.820 align:start position:0% old laptop this is a cheaper solution 00:05:54.820 --> 00:05:57.880 align:start position:0% old laptop this is a cheaper solution never<00:05:55.820> let<00:05:56.060> it<00:05:56.180> touch<00:05:56.330> the<00:05:56.360> internet<00:05:57.020> and<00:05:57.290> then 00:05:57.880 --> 00:05:57.890 align:start position:0% never let it touch the internet and then 00:05:57.890 --> 00:06:00.820 align:start position:0% never let it touch the internet and then just<00:05:58.130> print<00:05:58.550> out<00:05:58.730> the<00:05:58.790> seeds<00:05:59.690> and<00:06:00.080> put<00:06:00.560> it<00:06:00.680> in 00:06:00.820 --> 00:06:00.830 align:start position:0% just print out the seeds and put it in 00:06:00.830 --> 00:06:05.410 align:start position:0% just print out the seeds and put it in the<00:06:00.950> bank<00:06:01.460> vault<00:06:03.760> you<00:06:04.760> can<00:06:04.880> also<00:06:05.030> use<00:06:05.240> the 00:06:05.410 --> 00:06:05.420 align:start position:0% the bank vault you can also use the 00:06:05.420 --> 00:06:06.010 align:start position:0% the bank vault you can also use the Force 00:06:06.010 --> 00:06:06.020 align:start position:0% Force 00:06:06.020 --> 00:06:09.280 align:start position:0% Force we<00:06:06.170> have<00:06:06.380> ethereum<00:06:07.570> so<00:06:08.570> there<00:06:08.840> are<00:06:08.900> native 00:06:09.280 --> 00:06:09.290 align:start position:0% we have ethereum so there are native 00:06:09.290 --> 00:06:12.040 align:start position:0% we have ethereum so there are native tools<00:06:09.760> Nick<00:06:10.760> Johnson<00:06:11.270> and<00:06:11.510> who's<00:06:11.630> going<00:06:11.810> to 00:06:12.040 --> 00:06:12.050 align:start position:0% tools Nick Johnson and who's going to 00:06:12.050 --> 00:06:14.560 align:start position:0% tools Nick Johnson and who's going to present<00:06:12.440> after<00:06:12.920> me<00:06:13.010> he's<00:06:13.640> done<00:06:14.300> an 00:06:14.560 --> 00:06:14.570 align:start position:0% present after me he's done an 00:06:14.570 --> 00:06:16.180 align:start position:0% present after me he's done an implementation<00:06:15.140> I<00:06:15.200> mean<00:06:15.320> it's<00:06:15.470> very<00:06:15.680> involved 00:06:16.180 --> 00:06:16.190 align:start position:0% implementation I mean it's very involved 00:06:16.190 --> 00:06:20.220 align:start position:0% implementation I mean it's very involved which<00:06:16.400> is<00:06:16.430> a<00:06:16.610> time<00:06:17.030> lock<00:06:17.500> so<00:06:18.500> you<00:06:18.530> can<00:06:18.620> only<00:06:19.150> use 00:06:20.220 --> 00:06:20.230 align:start position:0% which is a time lock so you can only use 00:06:20.230 --> 00:06:24.250 align:start position:0% which is a time lock so you can only use a<00:06:21.230> certain<00:06:21.890> amount<00:06:22.100> at<00:06:23.000> every<00:06:23.750> predefined 00:06:24.250 --> 00:06:24.260 align:start position:0% a certain amount at every predefined 00:06:24.260 --> 00:06:28.540 align:start position:0% a certain amount at every predefined time<00:06:24.590> period<00:06:26.050> and<00:06:27.050> that's<00:06:27.200> you<00:06:27.860> do<00:06:28.010> that<00:06:28.190> using 00:06:28.540 --> 00:06:28.550 align:start position:0% time period and that's you do that using 00:06:28.550 --> 00:06:30.970 align:start position:0% time period and that's you do that using your<00:06:28.580> hotkey<00:06:29.090> and<00:06:29.300> then<00:06:30.110> you<00:06:30.230> also<00:06:30.380> have<00:06:30.770> the 00:06:30.970 --> 00:06:30.980 align:start position:0% your hotkey and then you also have the 00:06:30.980 --> 00:06:32.740 align:start position:0% your hotkey and then you also have the recovery<00:06:31.430> key<00:06:31.670> and<00:06:32.120> you<00:06:32.210> can<00:06:32.360> only<00:06:32.510> use<00:06:32.720> that 00:06:32.740 --> 00:06:32.750 align:start position:0% recovery key and you can only use that 00:06:32.750 --> 00:06:35.260 align:start position:0% recovery key and you can only use that once<00:06:33.260> and<00:06:33.830> when<00:06:34.130> you<00:06:34.250> do<00:06:34.400> use<00:06:34.610> that<00:06:34.640> it 00:06:35.260 --> 00:06:35.270 align:start position:0% once and when you do use that it 00:06:35.270 --> 00:06:36.940 align:start position:0% once and when you do use that it destroys<00:06:35.660> the<00:06:35.900> vault<00:06:36.140> and<00:06:36.380> sends<00:06:36.770> all<00:06:36.920> the 00:06:36.940 --> 00:06:36.950 align:start position:0% destroys the vault and sends all the 00:06:36.950 --> 00:06:40.030 align:start position:0% destroys the vault and sends all the ether<00:06:37.400> to<00:06:37.580> the<00:06:37.700> recovery<00:06:38.120> address<00:06:38.450> so<00:06:39.290> if<00:06:39.650> the 00:06:40.030 --> 00:06:40.040 align:start position:0% ether to the recovery address so if the 00:06:40.040 --> 00:06:43.360 align:start position:0% ether to the recovery address so if the bad<00:06:40.400> guy<00:06:40.700> has<00:06:40.940> got<00:06:41.570> hold<00:06:41.840> of<00:06:41.990> your<00:06:42.140> hotkey<00:06:42.710> then 00:06:43.360 --> 00:06:43.370 align:start position:0% bad guy has got hold of your hotkey then 00:06:43.370 --> 00:06:44.980 align:start position:0% bad guy has got hold of your hotkey then you<00:06:43.490> just<00:06:43.730> nuke<00:06:44.090> the<00:06:44.120> vault<00:06:44.480> and<00:06:44.750> get<00:06:44.840> the 00:06:44.980 --> 00:06:44.990 align:start position:0% you just nuke the vault and get the 00:06:44.990 --> 00:06:48.250 align:start position:0% you just nuke the vault and get the money<00:06:45.140> back<00:06:45.790> so<00:06:46.790> you<00:06:47.480> should<00:06:47.750> store<00:06:48.020> that 00:06:48.250 --> 00:06:48.260 align:start position:0% money back so you should store that 00:06:48.260 --> 00:06:49.340 align:start position:0% money back so you should store that recovery<00:06:48.800> key 00:06:49.340 --> 00:06:49.350 align:start position:0% recovery key 00:06:49.350 --> 00:06:54.910 align:start position:0% recovery key in<00:06:49.440> some<00:06:50.340> kind<00:06:50.520> of<00:06:50.640> safe<00:06:50.880> probe<00:06:51.390> some<00:06:51.600> backup 00:06:54.910 --> 00:06:54.920 align:start position:0% 00:06:54.920 --> 00:06:58.880 align:start position:0% there's<00:06:55.920> also<00:06:56.160> the<00:06:56.490> multi-sig<00:06:57.440> contract<00:06:58.440> and 00:06:58.880 --> 00:06:58.890 align:start position:0% there's also the multi-sig contract and 00:06:58.890 --> 00:07:00.800 align:start position:0% there's also the multi-sig contract and you<00:06:59.040> spread<00:06:59.340> the<00:06:59.490> trust<00:06:59.790> across<00:07:00.450> several 00:07:00.800 --> 00:07:00.810 align:start position:0% you spread the trust across several 00:07:00.810 --> 00:07:03.080 align:start position:0% you spread the trust across several people<00:07:01.290> so<00:07:02.040> in<00:07:02.370> in<00:07:02.580> the<00:07:02.670> one<00:07:02.790> of<00:07:02.850> them<00:07:03.000> you 00:07:03.080 --> 00:07:03.090 align:start position:0% people so in in the one of them you 00:07:03.090 --> 00:07:05.180 align:start position:0% people so in in the one of them you reduce<00:07:03.360> the<00:07:03.540> impact<00:07:03.930> and<00:07:04.470> the<00:07:04.620> other<00:07:04.740> you 00:07:05.180 --> 00:07:05.190 align:start position:0% reduce the impact and the other you 00:07:05.190 --> 00:07:07.520 align:start position:0% reduce the impact and the other you reduce<00:07:05.520> likelihood<00:07:06.180> if<00:07:06.300> the<00:07:07.020> likelihood<00:07:07.500> of 00:07:07.520 --> 00:07:07.530 align:start position:0% reduce likelihood if the likelihood of 00:07:07.530 --> 00:07:09.740 align:start position:0% reduce likelihood if the likelihood of all<00:07:07.740> them<00:07:08.180> trusted<00:07:09.180> people<00:07:09.480> getting 00:07:09.740 --> 00:07:09.750 align:start position:0% all them trusted people getting 00:07:09.750 --> 00:07:15.950 align:start position:0% all them trusted people getting compromised<00:07:12.620> and<00:07:13.620> don't<00:07:14.040> get<00:07:14.250> hacked<00:07:14.750> try<00:07:15.750> not 00:07:15.950 --> 00:07:15.960 align:start position:0% compromised and don't get hacked try not 00:07:15.960 --> 00:07:17.390 align:start position:0% compromised and don't get hacked try not to<00:07:16.080> get<00:07:16.170> hacked<00:07:16.410> you<00:07:16.590> know<00:07:16.860> ordinary<00:07:17.280> laptop 00:07:17.390 --> 00:07:17.400 align:start position:0% to get hacked you know ordinary laptop 00:07:17.400 --> 00:07:19.760 align:start position:0% to get hacked you know ordinary laptop if<00:07:17.850> you're<00:07:18.180> running<00:07:18.300> a<00:07:18.450> minor<00:07:18.690> remember<00:07:19.620> that 00:07:19.760 --> 00:07:19.770 align:start position:0% if you're running a minor remember that 00:07:19.770 --> 00:07:25.010 align:start position:0% if you're running a minor remember that a<00:07:19.920> minor<00:07:20.160> is<00:07:21.440> it's<00:07:22.670> 24/7<00:07:23.670> connected<00:07:24.510> to<00:07:24.900> this 00:07:25.010 --> 00:07:25.020 align:start position:0% a minor is it's 24/7 connected to this 00:07:25.020 --> 00:07:27.920 align:start position:0% a minor is it's 24/7 connected to this network<00:07:25.080> of<00:07:25.740> potentially<00:07:26.310> hostile<00:07:26.640> peers 00:07:27.920 --> 00:07:27.930 align:start position:0% network of potentially hostile peers 00:07:27.930 --> 00:07:29.840 align:start position:0% network of potentially hostile peers I'm<00:07:28.620> guessing<00:07:29.250> it's<00:07:29.370> most<00:07:29.640> often 00:07:29.840 --> 00:07:29.850 align:start position:0% I'm guessing it's most often 00:07:29.850 --> 00:07:32.000 align:start position:0% I'm guessing it's most often unsupervised<00:07:30.540> so<00:07:31.050> don't<00:07:31.290> put<00:07:31.500> anything<00:07:31.740> on 00:07:32.000 --> 00:07:32.010 align:start position:0% unsupervised so don't put anything on 00:07:32.010 --> 00:07:34.790 align:start position:0% unsupervised so don't put anything on value<00:07:32.400> on<00:07:32.520> it<00:07:32.700> including<00:07:33.540> your<00:07:33.990> coin<00:07:34.320> base<00:07:34.590> it 00:07:34.790 --> 00:07:34.800 align:start position:0% value on it including your coin base it 00:07:34.800 --> 00:07:36.620 align:start position:0% value on it including your coin base it shouldn't<00:07:35.100> be<00:07:35.220> on<00:07:35.400> the<00:07:35.550> on<00:07:35.790> the<00:07:35.880> minor<00:07:36.120> it 00:07:36.620 --> 00:07:36.630 align:start position:0% shouldn't be on the on the minor it 00:07:36.630 --> 00:07:38.570 align:start position:0% shouldn't be on the on the minor it should<00:07:36.840> mind<00:07:37.080> to<00:07:37.290> the<00:07:37.530> coin<00:07:37.740> base<00:07:37.950> somewhere 00:07:38.570 --> 00:07:38.580 align:start position:0% should mind to the coin base somewhere 00:07:38.580 --> 00:07:42.320 align:start position:0% should mind to the coin base somewhere else<00:07:39.530> use<00:07:40.530> virtual<00:07:41.010> machines<00:07:41.400> and<00:07:41.760> firewalls 00:07:42.320 --> 00:07:42.330 align:start position:0% else use virtual machines and firewalls 00:07:42.330 --> 00:07:45.560 align:start position:0% else use virtual machines and firewalls and<00:07:43.010> drop<00:07:44.010> everything<00:07:44.520> coming<00:07:45.090> to<00:07:45.270> your<00:07:45.390> host 00:07:45.560 --> 00:07:45.570 align:start position:0% and drop everything coming to your host 00:07:45.570 --> 00:07:49.400 align:start position:0% and drop everything coming to your host which<00:07:45.810> you're<00:07:46.200> not<00:07:46.350> originating<00:07:48.170> just<00:07:49.170> do 00:07:49.400 --> 00:07:49.410 align:start position:0% which you're not originating just do 00:07:49.410 --> 00:07:51.770 align:start position:0% which you're not originating just do sanity<00:07:49.920> check<00:07:50.160> or<00:07:50.430> what<00:07:50.580> you<00:07:50.700> expose<00:07:51.090> if 00:07:51.770 --> 00:07:51.780 align:start position:0% sanity check or what you expose if 00:07:51.780 --> 00:07:53.000 align:start position:0% sanity check or what you expose if you're<00:07:52.020> developer<00:07:52.620> you're<00:07:52.770> probably 00:07:53.000 --> 00:07:53.010 align:start position:0% you're developer you're probably 00:07:53.010 --> 00:07:56.600 align:start position:0% you're developer you're probably exposing<00:07:53.760> like<00:07:53.910> your<00:07:54.150> MySQL<00:07:54.780> or<00:07:55.200> a<00:07:55.590> patchy<00:07:56.310> or 00:07:56.600 --> 00:07:56.610 align:start position:0% exposing like your MySQL or a patchy or 00:07:56.610 --> 00:08:03.790 align:start position:0% exposing like your MySQL or a patchy or Tomcat<00:07:57.420> or<00:07:57.630> whatever<00:07:58.640> limit<00:07:59.640> that<00:08:02.360> right 00:08:03.790 --> 00:08:03.800 align:start position:0% Tomcat or whatever limit that right 00:08:03.800 --> 00:08:08.120 align:start position:0% Tomcat or whatever limit that right interacting<00:08:04.800> with<00:08:04.950> contracts<00:08:06.320> so<00:08:07.320> a<00:08:07.350> verified 00:08:08.120 --> 00:08:08.130 align:start position:0% interacting with contracts so a verified 00:08:08.130 --> 00:08:10.940 align:start position:0% interacting with contracts so a verified contract<00:08:09.380> what<00:08:10.380> does<00:08:10.470> that<00:08:10.500> mean<00:08:10.800> it<00:08:10.920> means 00:08:10.940 --> 00:08:10.950 align:start position:0% contract what does that mean it means 00:08:10.950 --> 00:08:16.120 align:start position:0% contract what does that mean it means that<00:08:11.330> what<00:08:12.330> is<00:08:12.360> deployed<00:08:12.960> on<00:08:13.380> the<00:08:14.220> blockchain 00:08:16.120 --> 00:08:16.130 align:start position:0% that what is deployed on the blockchain 00:08:16.130 --> 00:08:18.740 align:start position:0% that what is deployed on the blockchain there<00:08:17.130> is<00:08:17.220> a<00:08:17.250> source<00:08:17.640> code<00:08:17.880> and<00:08:18.150> it<00:08:18.450> can<00:08:18.630> be 00:08:18.740 --> 00:08:18.750 align:start position:0% there is a source code and it can be 00:08:18.750 --> 00:08:20.180 align:start position:0% there is a source code and it can be verify<00:08:19.140> that<00:08:19.320> the<00:08:19.440> source<00:08:19.680> code<00:08:19.980> when 00:08:20.180 --> 00:08:20.190 align:start position:0% verify that the source code when 00:08:20.190 --> 00:08:23.030 align:start position:0% verify that the source code when compiled<00:08:20.700> and<00:08:20.910> deployed<00:08:21.410> will<00:08:22.410> correspond<00:08:22.950> to 00:08:23.030 --> 00:08:23.040 align:start position:0% compiled and deployed will correspond to 00:08:23.040 --> 00:08:24.710 align:start position:0% compiled and deployed will correspond to that<00:08:23.250> it<00:08:23.550> doesn't<00:08:23.730> mean<00:08:23.940> anything<00:08:24.210> more<00:08:24.540> than 00:08:24.710 --> 00:08:24.720 align:start position:0% that it doesn't mean anything more than 00:08:24.720 --> 00:08:26.720 align:start position:0% that it doesn't mean anything more than that<00:08:24.870> it<00:08:25.020> doesn't<00:08:25.050> mean<00:08:25.380> that<00:08:25.410> there's<00:08:25.920> it<00:08:26.580> has 00:08:26.720 --> 00:08:26.730 align:start position:0% that it doesn't mean that there's it has 00:08:26.730 --> 00:08:28.190 align:start position:0% that it doesn't mean that there's it has been<00:08:26.910> audited<00:08:27.270> by<00:08:27.300> a<00:08:27.510> third<00:08:27.750> party<00:08:27.930> or 00:08:28.190 --> 00:08:28.200 align:start position:0% been audited by a third party or 00:08:28.200 --> 00:08:29.350 align:start position:0% been audited by a third party or anything<00:08:28.440> like<00:08:28.650> that 00:08:29.350 --> 00:08:29.360 align:start position:0% anything like that 00:08:29.360 --> 00:08:32.320 align:start position:0% anything like that only<00:08:30.360> that<00:08:30.510> the<00:08:30.630> source<00:08:30.870> code<00:08:30.900> is<00:08:31.080> available 00:08:32.320 --> 00:08:32.330 align:start position:0% only that the source code is available 00:08:32.330 --> 00:08:35.300 align:start position:0% only that the source code is available some<00:08:33.330> things<00:08:33.570> to<00:08:33.780> watch<00:08:33.960> out<00:08:34.140> for<00:08:34.200> if<00:08:34.740> you're 00:08:35.300 --> 00:08:35.310 align:start position:0% some things to watch out for if you're 00:08:35.310 --> 00:08:36.500 align:start position:0% some things to watch out for if you're interacting<00:08:35.669> with<00:08:35.849> the<00:08:35.910> contract<00:08:36.300> and<00:08:36.360> have 00:08:36.500 --> 00:08:36.510 align:start position:0% interacting with the contract and have 00:08:36.510 --> 00:08:38.600 align:start position:0% interacting with the contract and have the<00:08:36.630> source<00:08:36.840> code<00:08:37.050> is<00:08:37.289> does<00:08:38.099> it<00:08:38.250> use 00:08:38.600 --> 00:08:38.610 align:start position:0% the source code is does it use 00:08:38.610 --> 00:08:41.300 align:start position:0% the source code is does it use randomness<00:08:39.360> in<00:08:39.780> any<00:08:40.110> way<00:08:40.229> shape<00:08:40.469> or<00:08:40.650> form<00:08:40.710> and 00:08:41.300 --> 00:08:41.310 align:start position:0% randomness in any way shape or form and 00:08:41.310 --> 00:08:44.120 align:start position:0% randomness in any way shape or form and if<00:08:42.180> it<00:08:42.270> does<00:08:42.539> where<00:08:43.229> does<00:08:43.410> that<00:08:43.440> random<00:08:43.950> come 00:08:44.120 --> 00:08:44.130 align:start position:0% if it does where does that random come 00:08:44.130 --> 00:08:47.240 align:start position:0% if it does where does that random come from<00:08:44.400> and<00:08:45.290> can<00:08:46.290> the<00:08:46.410> source<00:08:46.710> of<00:08:46.890> that<00:08:47.040> random 00:08:47.240 --> 00:08:47.250 align:start position:0% from and can the source of that random 00:08:47.250 --> 00:08:50.330 align:start position:0% from and can the source of that random be<00:08:47.550> gained<00:08:47.850> and<00:08:48.560> can<00:08:49.560> anyone<00:08:49.860> access<00:08:50.190> it 00:08:50.330 --> 00:08:50.340 align:start position:0% be gained and can anyone access it 00:08:50.340 --> 00:08:53.480 align:start position:0% be gained and can anyone access it before<00:08:50.700> you<00:08:50.880> and<00:08:51.120> in<00:08:52.050> many<00:08:52.230> cases<00:08:52.470> they<00:08:52.740> can<00:08:53.010> so 00:08:53.480 --> 00:08:53.490 align:start position:0% before you and in many cases they can so 00:08:53.490 --> 00:08:55.730 align:start position:0% before you and in many cases they can so some<00:08:53.760> sources<00:08:54.120> of<00:08:54.360> random<00:08:54.780> that<00:08:55.200> can<00:08:55.440> be<00:08:55.530> used 00:08:55.730 --> 00:08:55.740 align:start position:0% some sources of random that can be used 00:08:55.740 --> 00:09:01.100 align:start position:0% some sources of random that can be used are<00:08:56.690> low<00:08:57.690> caches<00:08:58.200> it<00:08:58.770> can<00:08:59.040> be<00:08:59.220> also<00:09:00.110> important 00:09:01.100 --> 00:09:01.110 align:start position:0% are low caches it can be also important 00:09:01.110 --> 00:09:02.750 align:start position:0% are low caches it can be also important hashes<00:09:01.980> from<00:09:02.220> the<00:09:02.520> bit 00:09:02.750 --> 00:09:02.760 align:start position:0% hashes from the bit 00:09:02.760 --> 00:09:06.710 align:start position:0% hashes from the bit boxing<00:09:03.300> Maya<00:09:03.510> BTC<00:09:03.960> relay<00:09:05.150> in<00:09:06.150> which<00:09:06.420> case 00:09:06.710 --> 00:09:06.720 align:start position:0% boxing Maya BTC relay in which case 00:09:06.720 --> 00:09:09.050 align:start position:0% boxing Maya BTC relay in which case there<00:09:07.230> are<00:09:07.320> a<00:09:07.380> number<00:09:07.440> of<00:09:07.830> other<00:09:08.550> people<00:09:08.910> which 00:09:09.050 --> 00:09:09.060 align:start position:0% there are a number of other people which 00:09:09.060 --> 00:09:11.180 align:start position:0% there are a number of other people which can<00:09:09.540> see<00:09:09.780> the<00:09:09.930> headers<00:09:10.230> before<00:09:10.590> before<00:09:11.070> they 00:09:11.180 --> 00:09:11.190 align:start position:0% can see the headers before before they 00:09:11.190 --> 00:09:12.950 align:start position:0% can see the headers before before they actually<00:09:11.340> get<00:09:11.610> deployed<00:09:11.910> on<00:09:12.120> the<00:09:12.150> East<00:09:12.480> ether 00:09:12.950 --> 00:09:12.960 align:start position:0% actually get deployed on the East ether 00:09:12.960 --> 00:09:15.980 align:start position:0% actually get deployed on the East ether chain<00:09:13.260> and<00:09:13.610> even<00:09:14.610> if<00:09:14.730> the<00:09:15.030> source<00:09:15.570> of<00:09:15.870> the 00:09:15.980 --> 00:09:15.990 align:start position:0% chain and even if the source of the 00:09:15.990 --> 00:09:20.870 align:start position:0% chain and even if the source of the random<00:09:16.440> is<00:09:17.480> some<00:09:18.480> user<00:09:18.750> on<00:09:19.140> ethereum<00:09:20.010> some 00:09:20.870 --> 00:09:20.880 align:start position:0% random is some user on ethereum some 00:09:20.880 --> 00:09:23.510 align:start position:0% random is some user on ethereum some game<00:09:21.450> operator<00:09:22.250> remember<00:09:23.250> that<00:09:23.430> the 00:09:23.510 --> 00:09:23.520 align:start position:0% game operator remember that the 00:09:23.520 --> 00:09:26.650 align:start position:0% game operator remember that the transaction<00:09:24.470> goes<00:09:25.470> out<00:09:25.740> and<00:09:26.160> then<00:09:26.340> it<00:09:26.460> takes 00:09:26.650 --> 00:09:26.660 align:start position:0% transaction goes out and then it takes 00:09:26.660 --> 00:09:29.300 align:start position:0% transaction goes out and then it takes 14<00:09:27.660> seconds<00:09:28.140> before<00:09:28.500> it's<00:09:28.590> getting<00:09:28.860> cluded<00:09:29.190> in 00:09:29.300 --> 00:09:29.310 align:start position:0% 14 seconds before it's getting cluded in 00:09:29.310 --> 00:09:31.820 align:start position:0% 14 seconds before it's getting cluded in block<00:09:29.640> so<00:09:30.210> anyone<00:09:30.540> can<00:09:30.750> just<00:09:30.960> use<00:09:31.590> that 00:09:31.820 --> 00:09:31.830 align:start position:0% block so anyone can just use that 00:09:31.830 --> 00:09:37.520 align:start position:0% block so anyone can just use that information<00:09:32.070> and<00:09:32.640> from<00:09:33.600> from<00:09:33.900> that<00:09:34.200> source<00:09:36.530> so 00:09:37.520 --> 00:09:37.530 align:start position:0% information and from from that source so 00:09:37.530 --> 00:09:39.980 align:start position:0% information and from from that source so unless<00:09:37.770> they<00:09:37.980> are<00:09:38.040> actually<00:09:38.850> defined<00:09:39.540> time 00:09:39.980 --> 00:09:39.990 align:start position:0% unless they are actually defined time 00:09:39.990 --> 00:09:43.580 align:start position:0% unless they are actually defined time slots<00:09:40.350> for<00:09:40.650> random<00:09:41.610> and<00:09:41.820> then<00:09:42.570> acting<00:09:43.380> on<00:09:43.470> that 00:09:43.580 --> 00:09:43.590 align:start position:0% slots for random and then acting on that 00:09:43.590 --> 00:09:49.520 align:start position:0% slots for random and then acting on that random<00:09:44.100> and<00:09:44.280> it<00:09:45.000> can<00:09:45.240> probably<00:09:45.870> be<00:09:46.530> gamed<00:09:48.530> you 00:09:49.520 --> 00:09:49.530 align:start position:0% random and it can probably be gamed you 00:09:49.530 --> 00:09:50.930 align:start position:0% random and it can probably be gamed you should<00:09:49.680> also<00:09:49.800> watch<00:09:49.980> out<00:09:50.190> for<00:09:50.340> Sybil<00:09:50.670> attacks 00:09:50.930 --> 00:09:50.940 align:start position:0% should also watch out for Sybil attacks 00:09:50.940 --> 00:09:53.270 align:start position:0% should also watch out for Sybil attacks so<00:09:51.540> a<00:09:51.570> civil<00:09:51.900> attack<00:09:52.170> is<00:09:52.380> when<00:09:52.740> an<00:09:52.860> attacker<00:09:53.160> is 00:09:53.270 --> 00:09:53.280 align:start position:0% so a civil attack is when an attacker is 00:09:53.280 --> 00:09:55.640 align:start position:0% so a civil attack is when an attacker is using<00:09:53.340> several<00:09:53.850> identities<00:09:54.500> imagine<00:09:55.500> that 00:09:55.640 --> 00:09:55.650 align:start position:0% using several identities imagine that 00:09:55.650 --> 00:09:57.350 align:start position:0% using several identities imagine that you're<00:09:55.770> sitting<00:09:55.920> at<00:09:56.100> a<00:09:56.190> poker<00:09:56.520> table<00:09:56.790> playing 00:09:57.350 --> 00:09:57.360 align:start position:0% you're sitting at a poker table playing 00:09:57.360 --> 00:10:00.050 align:start position:0% you're sitting at a poker table playing against<00:09:57.840> five<00:09:58.620> other<00:09:58.800> people<00:09:59.070> and<00:09:59.610> what<00:09:59.970> you 00:10:00.050 --> 00:10:00.060 align:start position:0% against five other people and what you 00:10:00.060 --> 00:10:01.640 align:start position:0% against five other people and what you don't<00:10:00.210> know<00:10:00.450> is<00:10:00.660> that<00:10:00.690> they're<00:10:01.020> all<00:10:01.140> colluding 00:10:01.640 --> 00:10:01.650 align:start position:0% don't know is that they're all colluding 00:10:01.650 --> 00:10:05.560 align:start position:0% don't know is that they're all colluding against<00:10:02.010> you<00:10:02.190> they're<00:10:02.610> all<00:10:02.730> the<00:10:02.850> same<00:10:02.880> person 00:10:05.560 --> 00:10:05.570 align:start position:0% 00:10:05.570 --> 00:10:08.180 align:start position:0% you<00:10:06.570> should<00:10:06.750> watch<00:10:06.900> out<00:10:07.050> for<00:10:07.080> ragequitting<00:10:07.800> so 00:10:08.180 --> 00:10:08.190 align:start position:0% you should watch out for ragequitting so 00:10:08.190 --> 00:10:11.450 align:start position:0% you should watch out for ragequitting so if<00:10:08.610> you're<00:10:09.530> using<00:10:10.530> some<00:10:10.890> kind<00:10:11.040> of<00:10:11.190> service 00:10:11.450 --> 00:10:11.460 align:start position:0% if you're using some kind of service 00:10:11.460 --> 00:10:14.570 align:start position:0% if you're using some kind of service which<00:10:12.450> has<00:10:12.630> several<00:10:12.930> states<00:10:13.530> which<00:10:14.220> it<00:10:14.370> moves 00:10:14.570 --> 00:10:14.580 align:start position:0% which has several states which it moves 00:10:14.580 --> 00:10:17.780 align:start position:0% which has several states which it moves between<00:10:14.850> if<00:10:15.750> the<00:10:16.230> state<00:10:16.500> transition<00:10:17.160> depends 00:10:17.780 --> 00:10:17.790 align:start position:0% between if the state transition depends 00:10:17.790 --> 00:10:19.640 align:start position:0% between if the state transition depends on<00:10:17.970> someone<00:10:18.510> doing<00:10:18.990> their<00:10:19.200> part 00:10:19.640 --> 00:10:19.650 align:start position:0% on someone doing their part 00:10:19.650 --> 00:10:22.340 align:start position:0% on someone doing their part for<00:10:20.490> example<00:10:20.850> the<00:10:20.970> operator<00:10:21.420> providing<00:10:22.110> the 00:10:22.340 --> 00:10:22.350 align:start position:0% for example the operator providing the 00:10:22.350 --> 00:10:24.670 align:start position:0% for example the operator providing the seeds<00:10:22.590> for<00:10:22.920> the<00:10:23.010> next<00:10:23.040> round<00:10:23.520> or<00:10:23.850> the<00:10:23.880> operator 00:10:24.670 --> 00:10:24.680 align:start position:0% seeds for the next round or the operator 00:10:24.680 --> 00:10:27.290 align:start position:0% seeds for the next round or the operator cashing<00:10:25.680> out<00:10:25.800> what<00:10:26.520> happens<00:10:26.880> if<00:10:27.000> he<00:10:27.090> doesn't 00:10:27.290 --> 00:10:27.300 align:start position:0% cashing out what happens if he doesn't 00:10:27.300 --> 00:10:30.110 align:start position:0% cashing out what happens if he doesn't if<00:10:27.720> it<00:10:27.840> just<00:10:27.990> stops<00:10:28.350> or<00:10:29.280> you<00:10:29.430> see<00:10:29.640> it<00:10:29.790> can<00:10:30.030> he 00:10:30.110 --> 00:10:30.120 align:start position:0% if it just stops or you see it can he 00:10:30.120 --> 00:10:32.030 align:start position:0% if it just stops or you see it can he suicide<00:10:30.750> the<00:10:30.870> contract<00:10:31.380> and<00:10:31.560> just<00:10:31.590> collect 00:10:32.030 --> 00:10:32.040 align:start position:0% suicide the contract and just collect 00:10:32.040 --> 00:10:41.150 align:start position:0% suicide the contract and just collect the<00:10:32.190> bank<00:10:36.830> I'm<00:10:37.830> going<00:10:38.220> to<00:10:38.430> taps<00:10:39.140> so<00:10:40.140> adapts<00:10:40.500> I'm 00:10:41.150 --> 00:10:41.160 align:start position:0% the bank I'm going to taps so adapts I'm 00:10:41.160 --> 00:10:43.310 align:start position:0% the bank I'm going to taps so adapts I'm sure<00:10:41.310> most<00:10:41.520> of<00:10:41.670> you<00:10:41.790> know<00:10:42.000> probably<00:10:42.840> all<00:10:43.050> of 00:10:43.310 --> 00:10:43.320 align:start position:0% sure most of you know probably all of 00:10:43.320 --> 00:10:46.550 align:start position:0% sure most of you know probably all of you<00:10:43.850> HTML<00:10:44.850> Javascript<00:10:45.270> pages<00:10:45.690> which<00:10:46.170> have 00:10:46.550 --> 00:10:46.560 align:start position:0% you HTML Javascript pages which have 00:10:46.560 --> 00:10:49.250 align:start position:0% you HTML Javascript pages which have access<00:10:47.070> to<00:10:47.280> this<00:10:47.430> web<00:10:47.850> 3<00:10:48.120> API<00:10:48.480> and<00:10:48.810> they<00:10:49.080> can 00:10:49.250 --> 00:10:49.260 align:start position:0% access to this web 3 API and they can 00:10:49.260 --> 00:10:52.130 align:start position:0% access to this web 3 API and they can interact<00:10:49.410> interact<00:10:50.280> with<00:10:50.490> ethereum<00:10:51.140> so 00:10:52.130 --> 00:10:52.140 align:start position:0% interact interact with ethereum so 00:10:52.140 --> 00:10:53.750 align:start position:0% interact interact with ethereum so that's<00:10:52.380> reciting<00:10:53.160> the<00:10:53.250> browser 00:10:53.750 --> 00:10:53.760 align:start position:0% that's reciting the browser 00:10:53.760 --> 00:10:57.710 align:start position:0% that's reciting the browser it<00:10:54.180> could<00:10:54.810> be<00:10:54.900> missed<00:10:55.170> or<00:10:56.150> parity<00:10:57.150> based<00:10:57.330> and 00:10:57.710 --> 00:10:57.720 align:start position:0% it could be missed or parity based and 00:10:57.720 --> 00:11:00.170 align:start position:0% it could be missed or parity based and the<00:10:58.230> browser<00:10:58.470> has<00:10:59.100> an<00:10:59.310> extensive<00:10:59.700> attack 00:11:00.170 --> 00:11:00.180 align:start position:0% the browser has an extensive attack 00:11:00.180 --> 00:11:02.860 align:start position:0% the browser has an extensive attack service<00:11:00.660> because<00:11:01.440> the<00:11:01.590> web<00:11:01.740> is<00:11:01.770> broken 00:11:02.860 --> 00:11:02.870 align:start position:0% service because the web is broken 00:11:02.870 --> 00:11:05.690 align:start position:0% service because the web is broken it's<00:11:03.870> a<00:11:04.020> centralized<00:11:04.620> trust<00:11:04.950> model<00:11:05.310> based<00:11:05.550> on 00:11:05.690 --> 00:11:05.700 align:start position:0% it's a centralized trust model based on 00:11:05.700 --> 00:11:09.530 align:start position:0% it's a centralized trust model based on the<00:11:05.760> ca<00:11:06.060> authority<00:11:06.810> and<00:11:08.120> mainly<00:11:09.120> the<00:11:09.270> browser 00:11:09.530 --> 00:11:09.540 align:start position:0% the ca authority and mainly the browser 00:11:09.540 --> 00:11:12.470 align:start position:0% the ca authority and mainly the browser tries<00:11:10.170> to<00:11:10.560> render<00:11:11.010> things<00:11:11.400> not<00:11:12.060> based<00:11:12.330> on 00:11:12.470 --> 00:11:12.480 align:start position:0% tries to render things not based on 00:11:12.480 --> 00:11:15.470 align:start position:0% tries to render things not based on specification<00:11:13.790> is<00:11:14.790> more<00:11:15.120> like<00:11:15.300> the 00:11:15.470 --> 00:11:15.480 align:start position:0% specification is more like the 00:11:15.480 --> 00:11:16.879 align:start position:0% specification is more like the specification 00:11:16.879 --> 00:11:16.889 align:start position:0% specification 00:11:16.889 --> 00:11:21.169 align:start position:0% specification to<00:11:17.399> document<00:11:18.170> what<00:11:19.170> what<00:11:19.470> we<00:11:19.619> have<00:11:20.149> there 00:11:21.169 --> 00:11:21.179 align:start position:0% to document what what we have there 00:11:21.179 --> 00:11:23.869 align:start position:0% to document what what we have there they've<00:11:22.079> been<00:11:22.199> specified<00:11:22.769> post<00:11:23.100> factum<00:11:23.639> and 00:11:23.869 --> 00:11:23.879 align:start position:0% they've been specified post factum and 00:11:23.879 --> 00:11:26.059 align:start position:0% they've been specified post factum and there's<00:11:24.299> no<00:11:24.449> real<00:11:24.660> governing<00:11:25.109> security<00:11:25.709> model 00:11:26.059 --> 00:11:26.069 align:start position:0% there's no real governing security model 00:11:26.069 --> 00:11:29.960 align:start position:0% there's no real governing security model for<00:11:26.819> how<00:11:27.029> anything<00:11:27.420> is<00:11:27.660> handled<00:11:28.369> on<00:11:29.369> the<00:11:29.429> web 00:11:29.960 --> 00:11:29.970 align:start position:0% for how anything is handled on the web 00:11:29.970 --> 00:11:31.639 align:start position:0% for how anything is handled on the web so<00:11:30.660> there<00:11:30.809> are<00:11:30.869> a<00:11:30.899> lot<00:11:30.989> of<00:11:31.019> vulnerabilities 00:11:31.639 --> 00:11:31.649 align:start position:0% so there are a lot of vulnerabilities 00:11:31.649 --> 00:11:34.629 align:start position:0% so there are a lot of vulnerabilities and<00:11:31.949> a<00:11:32.009> lot<00:11:32.549> of<00:11:32.699> possible<00:11:33.419> exploits 00:11:34.629 --> 00:11:34.639 align:start position:0% and a lot of possible exploits 00:11:34.639 --> 00:11:37.369 align:start position:0% and a lot of possible exploits so<00:11:35.639> with<00:11:35.790> that<00:11:35.970> browser<00:11:36.269> connects<00:11:37.169> this 00:11:37.369 --> 00:11:37.379 align:start position:0% so with that browser connects this 00:11:37.379 --> 00:11:40.909 align:start position:0% so with that browser connects this broken<00:11:37.769> web<00:11:37.919> with<00:11:38.399> your<00:11:38.669> wallet<00:11:39.619> so<00:11:40.619> I<00:11:40.649> would 00:11:40.909 --> 00:11:40.919 align:start position:0% broken web with your wallet so I would 00:11:40.919 --> 00:11:42.889 align:start position:0% broken web with your wallet so I would recommend<00:11:41.069> don't<00:11:41.549> couch<00:11:41.879> surf<00:11:42.149> the<00:11:42.419> internet 00:11:42.889 --> 00:11:42.899 align:start position:0% recommend don't couch surf the internet 00:11:42.899 --> 00:11:45.769 align:start position:0% recommend don't couch surf the internet with<00:11:43.079> your<00:11:43.109> deaf<00:11:43.439> browser<00:11:43.739> and<00:11:44.480> verify<00:11:45.480> that 00:11:45.769 --> 00:11:45.779 align:start position:0% with your deaf browser and verify that 00:11:45.779 --> 00:11:51.439 align:start position:0% with your deaf browser and verify that resources<00:11:46.619> are<00:11:46.769> fit<00:11:47.040> securely<00:11:48.290> over<00:11:50.449> HTTPS 00:11:51.439 --> 00:11:51.449 align:start position:0% resources are fit securely over HTTPS 00:11:51.449 --> 00:11:55.309 align:start position:0% resources are fit securely over HTTPS and<00:11:52.459> when<00:11:53.459> you're<00:11:53.579> signing<00:11:53.910> something<00:11:54.689> in<00:11:54.869> a 00:11:55.309 --> 00:11:55.319 align:start position:0% and when you're signing something in a 00:11:55.319 --> 00:11:57.379 align:start position:0% and when you're signing something in a DAP<00:11:55.559> you<00:11:55.859> should<00:11:56.040> verify<00:11:56.220> that<00:11:56.549> the<00:11:56.790> recipient 00:11:57.379 --> 00:11:57.389 align:start position:0% DAP you should verify that the recipient 00:11:57.389 --> 00:11:59.389 align:start position:0% DAP you should verify that the recipient address<00:11:57.540> just<00:11:58.350> actually<00:11:58.559> correspond<00:11:59.220> to<00:11:59.279> the 00:11:59.389 --> 00:11:59.399 align:start position:0% address just actually correspond to the 00:11:59.399 --> 00:12:01.669 align:start position:0% address just actually correspond to the contract<00:11:59.879> that<00:12:00.029> you<00:12:00.179> intend<00:12:00.600> to<00:12:00.839> interact 00:12:01.669 --> 00:12:01.679 align:start position:0% contract that you intend to interact 00:12:01.679 --> 00:12:06.710 align:start position:0% contract that you intend to interact with<00:12:03.859> for<00:12:04.859> building<00:12:05.220> the<00:12:05.399> apps<00:12:05.519> the<00:12:06.449> same 00:12:06.710 --> 00:12:06.720 align:start position:0% with for building the apps the same 00:12:06.720 --> 00:12:10.159 align:start position:0% with for building the apps the same applies<00:12:07.079> use<00:12:07.769> HTTPS<00:12:08.549> that<00:12:08.929> certificates<00:12:09.929> as 00:12:10.159 --> 00:12:10.169 align:start position:0% applies use HTTPS that certificates as 00:12:10.169 --> 00:12:13.269 align:start position:0% applies use HTTPS that certificates as their<00:12:10.739> strict<00:12:11.279> Transport<00:12:11.519> Security<00:12:12.230> and 00:12:13.269 --> 00:12:13.279 align:start position:0% their strict Transport Security and 00:12:13.279 --> 00:12:17.059 align:start position:0% their strict Transport Security and tried<00:12:14.279> not<00:12:14.519> to<00:12:14.549> use<00:12:14.730> CDN<00:12:15.559> content<00:12:16.559> delivery 00:12:17.059 --> 00:12:17.069 align:start position:0% tried not to use CDN content delivery 00:12:17.069 --> 00:12:18.949 align:start position:0% tried not to use CDN content delivery network<00:12:17.399> because<00:12:18.089> that<00:12:18.239> means<00:12:18.449> that<00:12:18.660> someone 00:12:18.949 --> 00:12:18.959 align:start position:0% network because that means that someone 00:12:18.959 --> 00:12:22.129 align:start position:0% network because that means that someone else<00:12:19.169> is<00:12:19.319> delivering<00:12:19.919> code<00:12:20.819> and<00:12:21.209> if<00:12:21.779> someone 00:12:22.129 --> 00:12:22.139 align:start position:0% else is delivering code and if someone 00:12:22.139 --> 00:12:23.989 align:start position:0% else is delivering code and if someone else<00:12:22.290> can<00:12:22.470> execute<00:12:22.709> JavaScript<00:12:23.459> on<00:12:23.639> your<00:12:23.669> DAP 00:12:23.989 --> 00:12:23.999 align:start position:0% else can execute JavaScript on your DAP 00:12:23.999 --> 00:12:26.210 align:start position:0% else can execute JavaScript on your DAP didn't<00:12:24.329> it<00:12:24.419> either<00:12:24.989> because<00:12:25.499> they<00:12:25.679> can<00:12:25.860> inject 00:12:26.210 --> 00:12:26.220 align:start position:0% didn't it either because they can inject 00:12:26.220 --> 00:12:28.939 align:start position:0% didn't it either because they can inject the<00:12:26.399> traffic<00:12:26.939> at<00:12:27.379> where<00:12:28.379> the<00:12:28.499> client<00:12:28.889> is 00:12:28.939 --> 00:12:28.949 align:start position:0% the traffic at where the client is 00:12:28.949 --> 00:12:30.799 align:start position:0% the traffic at where the client is sitting<00:12:29.160> because<00:12:29.519> you're<00:12:29.759> not<00:12:29.879> using<00:12:30.119> HTTPS 00:12:30.799 --> 00:12:30.809 align:start position:0% sitting because you're not using HTTPS 00:12:30.809 --> 00:12:35.919 align:start position:0% sitting because you're not using HTTPS or<00:12:31.019> because<00:12:31.739> they're<00:12:31.980> serving<00:12:32.459> the<00:12:32.579> content 00:12:35.919 --> 00:12:35.929 align:start position:0% 00:12:35.929 --> 00:12:38.269 align:start position:0% or<00:12:36.929> because<00:12:37.199> it's<00:12:37.379> the<00:12:37.439> cross-site<00:12:37.799> scripting 00:12:38.269 --> 00:12:38.279 align:start position:0% or because it's the cross-site scripting 00:12:38.279 --> 00:12:40.159 align:start position:0% or because it's the cross-site scripting vulnerability<00:12:38.910> it's<00:12:39.600> like<00:12:39.720> an<00:12:39.839> execute 00:12:40.159 --> 00:12:40.169 align:start position:0% vulnerability it's like an execute 00:12:40.169 --> 00:12:41.720 align:start position:0% vulnerability it's like an execute JavaScript<00:12:40.649> they<00:12:41.069> can<00:12:41.249> do<00:12:41.369> whatever<00:12:41.549> they 00:12:41.720 --> 00:12:41.730 align:start position:0% JavaScript they can do whatever they 00:12:41.730 --> 00:12:43.069 align:start position:0% JavaScript they can do whatever they want<00:12:41.970> with<00:12:42.029> the<00:12:42.209> DAP<00:12:42.389> and<00:12:42.419> they<00:12:42.689> can<00:12:42.809> send<00:12:42.989> the 00:12:43.069 --> 00:12:43.079 align:start position:0% want with the DAP and they can send the 00:12:43.079 --> 00:12:45.229 align:start position:0% want with the DAP and they can send the payments<00:12:43.470> to<00:12:43.589> another<00:12:43.799> address<00:12:44.179> and<00:12:45.179> you 00:12:45.229 --> 00:12:45.239 align:start position:0% payments to another address and you 00:12:45.239 --> 00:12:47.299 align:start position:0% payments to another address and you should<00:12:45.389> learn<00:12:45.509> about<00:12:45.809> web<00:12:46.079> security<00:12:46.309> if 00:12:47.299 --> 00:12:47.309 align:start position:0% should learn about web security if 00:12:47.309 --> 00:12:50.359 align:start position:0% should learn about web security if you're<00:12:47.519> starting<00:12:47.730> with<00:12:47.879> our<00:12:48.089> top<00:12:48.480> ten<00:12:49.369> and 00:12:50.359 --> 00:12:50.369 align:start position:0% you're starting with our top ten and 00:12:50.369 --> 00:12:52.309 align:start position:0% you're starting with our top ten and there<00:12:51.149> are<00:12:51.239> a<00:12:51.269> lot<00:12:51.419> more<00:12:51.449> than<00:12:51.660> I<00:12:51.899> was<00:12:52.049> a<00:12:52.079> top 00:12:52.309 --> 00:12:52.319 align:start position:0% there are a lot more than I was a top 00:12:52.319 --> 00:12:56.869 align:start position:0% there are a lot more than I was a top ten<00:12:52.499> but<00:12:52.679> that's<00:12:52.829> a<00:12:52.919> good<00:12:53.069> start<00:12:53.399> so<00:12:55.879> building 00:12:56.869 --> 00:12:56.879 align:start position:0% ten but that's a good start so building 00:12:56.879 --> 00:13:00.259 align:start position:0% ten but that's a good start so building contracts<00:12:58.160> just<00:12:59.160> as<00:12:59.279> Java<00:12:59.699> has<00:12:59.789> mentioned<00:13:00.089> a 00:13:00.259 --> 00:13:00.269 align:start position:0% contracts just as Java has mentioned a 00:13:00.269 --> 00:13:01.759 align:start position:0% contracts just as Java has mentioned a lot<00:13:00.419> about<00:13:00.600> this<00:13:00.869> but<00:13:01.110> all<00:13:01.410> the<00:13:01.529> thing<00:13:01.679> in 00:13:01.759 --> 00:13:01.769 align:start position:0% lot about this but all the thing in 00:13:01.769 --> 00:13:04.909 align:start position:0% lot about this but all the thing in testing<00:13:02.189> is<00:13:02.279> very<00:13:02.489> important<00:13:03.619> you<00:13:04.619> need<00:13:04.799> to 00:13:04.909 --> 00:13:04.919 align:start position:0% testing is very important you need to 00:13:04.919 --> 00:13:07.269 align:start position:0% testing is very important you need to learn<00:13:05.069> the<00:13:05.309> inner<00:13:05.489> workings<00:13:05.819> of<00:13:05.970> the<00:13:06.779> VM 00:13:07.269 --> 00:13:07.279 align:start position:0% learn the inner workings of the VM 00:13:07.279 --> 00:13:12.109 align:start position:0% learn the inner workings of the VM unfortunately<00:13:08.279> but<00:13:08.939> also<00:13:09.389> it's<00:13:09.869> pretty<00:13:11.119> easy 00:13:12.109 --> 00:13:12.119 align:start position:0% unfortunately but also it's pretty easy 00:13:12.119 --> 00:13:14.419 align:start position:0% unfortunately but also it's pretty easy to<00:13:12.449> do<00:13:12.569> so<00:13:12.809> you<00:13:13.379> can<00:13:13.559> I'd<00:13:13.799> recommend<00:13:14.220> you<00:13:14.309> to 00:13:14.419 --> 00:13:14.429 align:start position:0% to do so you can I'd recommend you to 00:13:14.429 --> 00:13:16.429 align:start position:0% to do so you can I'd recommend you to start<00:13:14.669> with<00:13:14.850> the<00:13:14.939> VM<00:13:15.239> source<00:13:15.509> code<00:13:15.809> of<00:13:15.959> Python 00:13:16.429 --> 00:13:16.439 align:start position:0% start with the VM source code of Python 00:13:16.439 --> 00:13:20.229 align:start position:0% start with the VM source code of Python it's<00:13:16.829> very<00:13:17.129> small<00:13:17.660> 600<00:13:18.660> lines<00:13:18.749> of<00:13:18.929> code<00:13:19.109> and 00:13:20.229 --> 00:13:20.239 align:start position:0% it's very small 600 lines of code and 00:13:20.239 --> 00:13:22.759 align:start position:0% it's very small 600 lines of code and try<00:13:21.239> to<00:13:21.299> have<00:13:21.480> an<00:13:21.539> upgrade<00:13:21.899> path<00:13:22.109> and<00:13:22.439> not<00:13:22.559> only 00:13:22.759 --> 00:13:22.769 align:start position:0% try to have an upgrade path and not only 00:13:22.769 --> 00:13:24.739 align:start position:0% try to have an upgrade path and not only for<00:13:23.160> the<00:13:23.220> code<00:13:23.970> in<00:13:24.179> your<00:13:24.329> contracts 00:13:24.739 --> 00:13:24.749 align:start position:0% for the code in your contracts 00:13:24.749 --> 00:13:26.689 align:start position:0% for the code in your contracts potentially<00:13:25.350> also<00:13:25.499> for<00:13:25.860> all<00:13:25.949> your<00:13:26.100> data<00:13:26.309> how 00:13:26.689 --> 00:13:26.699 align:start position:0% potentially also for all your data how 00:13:26.699 --> 00:13:29.230 align:start position:0% potentially also for all your data how do<00:13:26.759> you<00:13:26.910> move<00:13:27.089> that<00:13:27.299> into<00:13:27.600> the<00:13:27.809> next 00:13:29.230 --> 00:13:29.240 align:start position:0% do you move that into the next 00:13:29.240 --> 00:13:32.590 align:start position:0% do you move that into the next version<00:13:29.540> of<00:13:29.660> your<00:13:29.839> contract<00:13:31.209> as<00:13:32.209> Joseph 00:13:32.590 --> 00:13:32.600 align:start position:0% version of your contract as Joseph 00:13:32.600 --> 00:13:34.750 align:start position:0% version of your contract as Joseph mentioned<00:13:32.630> check<00:13:33.589> the<00:13:33.770> invariance<00:13:34.250> escape 00:13:34.750 --> 00:13:34.760 align:start position:0% mentioned check the invariance escape 00:13:34.760 --> 00:13:37.600 align:start position:0% mentioned check the invariance escape hatches<00:13:35.029> emergency<00:13:35.750> brakes<00:13:35.990> and<00:13:36.470> try<00:13:37.220> to<00:13:37.279> make 00:13:37.600 --> 00:13:37.610 align:start position:0% hatches emergency brakes and try to make 00:13:37.610 --> 00:13:41.620 align:start position:0% hatches emergency brakes and try to make things<00:13:37.850> foolproof<00:13:38.680> so<00:13:39.680> so<00:13:40.430> even<00:13:40.760> fools<00:13:41.029> can 00:13:41.620 --> 00:13:41.630 align:start position:0% things foolproof so so even fools can 00:13:41.630 --> 00:13:45.060 align:start position:0% things foolproof so so even fools can use<00:13:41.810> them<00:13:42.110> and<00:13:42.320> allow<00:13:43.279> users<00:13:43.820> to<00:13:43.850> make<00:13:44.180> errors 00:13:45.060 --> 00:13:45.070 align:start position:0% use them and allow users to make errors 00:13:45.070 --> 00:13:49.199 align:start position:0% use them and allow users to make errors so<00:13:46.070> this<00:13:46.339> is<00:13:46.520> from<00:13:46.880> one<00:13:47.870> of<00:13:48.440> the<00:13:48.649> splinters 00:13:49.199 --> 00:13:49.209 align:start position:0% so this is from one of the splinters 00:13:49.209 --> 00:13:51.880 align:start position:0% so this is from one of the splinters after<00:13:50.209> the<00:13:50.330> hard<00:13:50.540> work<00:13:50.839> and<00:13:51.200> what's 00:13:51.880 --> 00:13:51.890 align:start position:0% after the hard work and what's 00:13:51.890 --> 00:13:56.949 align:start position:0% after the hard work and what's highlighted<00:13:52.100> here<00:13:52.640> is<00:13:54.550> 1,493<00:13:55.550> ether<00:13:56.120> which 00:13:56.949 --> 00:13:56.959 align:start position:0% highlighted here is 1,493 ether which 00:13:56.959 --> 00:13:59.530 align:start position:0% highlighted here is 1,493 ether which has<00:13:57.260> been<00:13:57.500> successfully<00:13:58.490> split<00:13:58.790> into<00:13:59.180> the 00:13:59.530 --> 00:13:59.540 align:start position:0% has been successfully split into the 00:13:59.540 --> 00:14:02.410 align:start position:0% has been successfully split into the zero<00:13:59.870> address<00:14:00.580> so<00:14:01.580> someone<00:14:02.060> who<00:14:02.180> probably 00:14:02.410 --> 00:14:02.420 align:start position:0% zero address so someone who probably 00:14:02.420 --> 00:14:06.699 align:start position:0% zero address so someone who probably wanted<00:14:03.020> to<00:14:03.520> split<00:14:04.520> away<00:14:04.850> his<00:14:05.089> etc'<00:14:05.720> but<00:14:06.380> keep 00:14:06.699 --> 00:14:06.709 align:start position:0% wanted to split away his etc' but keep 00:14:06.709 --> 00:14:10.810 align:start position:0% wanted to split away his etc' but keep his<00:14:07.010> eth<00:14:07.850> ether<00:14:08.540> and<00:14:09.110> didn't<00:14:09.980> put<00:14:10.220> anything<00:14:10.520> in 00:14:10.810 --> 00:14:10.820 align:start position:0% his eth ether and didn't put anything in 00:14:10.820 --> 00:14:13.780 align:start position:0% his eth ether and didn't put anything in in<00:14:11.779> that<00:14:11.930> field<00:14:11.990> so<00:14:12.980> basically<00:14:13.310> it<00:14:13.490> became 00:14:13.780 --> 00:14:13.790 align:start position:0% in that field so basically it became 00:14:13.790 --> 00:14:17.949 align:start position:0% in that field so basically it became zero<00:14:14.149> and<00:14:14.480> all<00:14:15.380> his<00:14:15.680> ether<00:14:16.660> went<00:14:17.660> up<00:14:17.779> in<00:14:17.930> smoke 00:14:17.949 --> 00:14:17.959 align:start position:0% zero and all his ether went up in smoke 00:14:17.959 --> 00:14:21.130 align:start position:0% zero and all his ether went up in smoke and<00:14:18.350> in<00:14:18.500> total<00:14:18.890> there's<00:14:19.070> been<00:14:19.310> about<00:14:20.140> 1800 00:14:21.130 --> 00:14:21.140 align:start position:0% and in total there's been about 1800 00:14:21.140 --> 00:14:23.560 align:start position:0% and in total there's been about 1800 ether<00:14:21.470> sent<00:14:21.740> to<00:14:21.920> the<00:14:22.070> syrian<00:14:22.940> rest<00:14:23.120> by<00:14:23.360> allah 00:14:23.560 --> 00:14:23.570 align:start position:0% ether sent to the syrian rest by allah 00:14:23.570 --> 00:14:27.670 align:start position:0% ether sent to the syrian rest by allah splitter<00:14:23.870> right<00:14:26.410> there<00:14:27.410> are<00:14:27.500> several 00:14:27.670 --> 00:14:27.680 align:start position:0% splitter right there are several 00:14:27.680 --> 00:14:28.800 align:start position:0% splitter right there are several vulnerabilities 00:14:28.800 --> 00:14:28.810 align:start position:0% vulnerabilities 00:14:28.810 --> 00:14:31.240 align:start position:0% vulnerabilities Josef's<00:14:29.810> talks<00:14:30.050> about<00:14:30.320> most<00:14:30.589> of<00:14:30.830> them<00:14:30.980> and<00:14:31.160> i 00:14:31.240 --> 00:14:31.250 align:start position:0% Josef's talks about most of them and i 00:14:31.250 --> 00:14:33.550 align:start position:0% Josef's talks about most of them and i don't<00:14:31.670> have<00:14:31.760> time<00:14:31.970> to<00:14:32.149> go<00:14:32.240> into<00:14:32.360> them<00:14:32.600> i'll 00:14:33.550 --> 00:14:33.560 align:start position:0% don't have time to go into them i'll 00:14:33.560 --> 00:14:34.690 align:start position:0% don't have time to go into them i'll mentioned<00:14:34.040> some<00:14:34.279> of<00:14:34.310> them 00:14:34.690 --> 00:14:34.700 align:start position:0% mentioned some of them 00:14:34.700 --> 00:14:38.280 align:start position:0% mentioned some of them so<00:14:35.000> not<00:14:35.839> robust<00:14:36.200> against<00:14:36.620> Shane<00:14:36.829> reordering 00:14:38.280 --> 00:14:38.290 align:start position:0% so not robust against Shane reordering 00:14:38.290 --> 00:14:41.920 align:start position:0% so not robust against Shane reordering that<00:14:39.290> for<00:14:40.220> example<00:14:40.520> if<00:14:40.820> you<00:14:40.970> have<00:14:41.180> a<00:14:41.390> committee 00:14:41.920 --> 00:14:41.930 align:start position:0% that for example if you have a committee 00:14:41.930 --> 00:14:44.470 align:start position:0% that for example if you have a committee reveal<00:14:42.410> scheme<00:14:42.860> what<00:14:43.760> could<00:14:44.029> happen<00:14:44.360> is<00:14:44.450> that 00:14:44.470 --> 00:14:44.480 align:start position:0% reveal scheme what could happen is that 00:14:44.480 --> 00:14:46.930 align:start position:0% reveal scheme what could happen is that you<00:14:44.690> commit<00:14:45.350> and<00:14:45.680> then<00:14:46.100> comes<00:14:46.459> the<00:14:46.640> reveal 00:14:46.930 --> 00:14:46.940 align:start position:0% you commit and then comes the reveal 00:14:46.940 --> 00:14:49.990 align:start position:0% you commit and then comes the reveal phase<00:14:47.300> and<00:14:47.630> then<00:14:48.410> the<00:14:48.440> malicious<00:14:48.920> minor<00:14:49.190> rolls 00:14:49.990 --> 00:14:50.000 align:start position:0% phase and then the malicious minor rolls 00:14:50.000 --> 00:14:52.780 align:start position:0% phase and then the malicious minor rolls back<00:14:50.390> and<00:14:50.810> starts<00:14:51.410> mining<00:14:51.800> a<00:14:51.860> step<00:14:52.130> back<00:14:52.399> and 00:14:52.780 --> 00:14:52.790 align:start position:0% back and starts mining a step back and 00:14:52.790 --> 00:14:54.930 align:start position:0% back and starts mining a step back and uses<00:14:53.209> the<00:14:53.329> information<00:14:53.470> that<00:14:54.470> has<00:14:54.560> been 00:14:54.930 --> 00:14:54.940 align:start position:0% uses the information that has been 00:14:54.940 --> 00:15:02.769 align:start position:0% uses the information that has been revealed<00:14:55.940> it<00:14:56.839> starts<00:14:57.170> a<00:14:57.260> new<00:14:57.790> version<00:15:01.779> right 00:15:02.769 --> 00:15:02.779 align:start position:0% revealed it starts a new version right 00:15:02.779 --> 00:15:06.460 align:start position:0% revealed it starts a new version right there's<00:15:03.140> a<00:15:03.230> simple<00:15:04.779> double<00:15:05.779> function<00:15:06.320> which 00:15:06.460 --> 00:15:06.470 align:start position:0% there's a simple double function which 00:15:06.470 --> 00:15:09.449 align:start position:0% there's a simple double function which tries<00:15:06.709> to<00:15:06.920> double<00:15:07.279> the<00:15:07.790> input<00:15:07.970> you<00:15:08.630> into<00:15:08.870> eight 00:15:09.449 --> 00:15:09.459 align:start position:0% tries to double the input you into eight 00:15:09.459 --> 00:15:12.940 align:start position:0% tries to double the input you into eight and<00:15:10.459> it<00:15:10.640> puts<00:15:11.570> it<00:15:11.690> into<00:15:11.839> you<00:15:12.020> at<00:15:12.140> 64<00:15:12.709> so<00:15:12.860> it 00:15:12.940 --> 00:15:12.950 align:start position:0% and it puts it into you at 64 so it 00:15:12.950 --> 00:15:14.860 align:start position:0% and it puts it into you at 64 so it should<00:15:13.160> be<00:15:13.279> fine<00:15:13.520> right<00:15:13.550> but<00:15:14.270> when<00:15:14.420> we<00:15:14.540> run<00:15:14.690> the 00:15:14.860 --> 00:15:14.870 align:start position:0% should be fine right but when we run the 00:15:14.870 --> 00:15:20.910 align:start position:0% should be fine right but when we run the test<00:15:15.140> and<00:15:15.440> Sun<00:15:15.770> in<00:15:15.920> our<00:15:16.160> X<00:15:16.339> 80<00:15:16.959> it<00:15:17.959> returns<00:15:18.320> zero 00:15:20.910 --> 00:15:20.920 align:start position:0% 00:15:20.920 --> 00:15:23.410 align:start position:0% so<00:15:21.920> you<00:15:22.010> should<00:15:22.160> learn<00:15:22.339> the<00:15:22.579> details<00:15:22.790> of<00:15:23.300> how 00:15:23.410 --> 00:15:23.420 align:start position:0% so you should learn the details of how 00:15:23.420 --> 00:15:25.660 align:start position:0% so you should learn the details of how solidity<00:15:23.930> works<00:15:24.230> if<00:15:25.130> you<00:15:25.279> want<00:15:25.459> to<00:15:25.520> make 00:15:25.660 --> 00:15:25.670 align:start position:0% solidity works if you want to make 00:15:25.670 --> 00:15:29.500 align:start position:0% solidity works if you want to make secure<00:15:26.120> smart<00:15:26.450> contracts<00:15:28.240> there<00:15:29.240> are<00:15:29.300> several 00:15:29.500 --> 00:15:29.510 align:start position:0% secure smart contracts there are several 00:15:29.510 --> 00:15:35.560 align:start position:0% secure smart contracts there are several patterns<00:15:30.190> also<00:15:31.190> mentioned<00:15:31.610> earlier<00:15:34.360> and<00:15:35.360> you 00:15:35.560 --> 00:15:35.570 align:start position:0% patterns also mentioned earlier and you 00:15:35.570 --> 00:15:37.360 align:start position:0% patterns also mentioned earlier and you should<00:15:35.779> also<00:15:36.110> think<00:15:36.260> about<00:15:36.560> that<00:15:36.920> private 00:15:37.360 --> 00:15:37.370 align:start position:0% should also think about that private 00:15:37.370 --> 00:15:40.240 align:start position:0% should also think about that private networks<00:15:37.760> are<00:15:37.940> not<00:15:38.089> really<00:15:38.540> private<00:15:39.250> okay 00:15:40.240 --> 00:15:40.250 align:start position:0% networks are not really private okay 00:15:40.250 --> 00:15:42.280 align:start position:0% networks are not really private okay they<00:15:40.430> call<00:15:40.760> private<00:15:41.120> networks<00:15:41.690> but<00:15:41.959> that 00:15:42.280 --> 00:15:42.290 align:start position:0% they call private networks but that 00:15:42.290 --> 00:15:42.760 align:start position:0% they call private networks but that doesn't 00:15:42.760 --> 00:15:42.770 align:start position:0% doesn't 00:15:42.770 --> 00:15:48.220 align:start position:0% doesn't mean<00:15:42.950> that<00:15:45.430> that<00:15:46.430> someone<00:15:46.730> cannot<00:15:47.180> come<00:15:48.080> into 00:15:48.220 --> 00:15:48.230 align:start position:0% mean that that someone cannot come into 00:15:48.230 --> 00:15:48.670 align:start position:0% mean that that someone cannot come into them 00:15:48.670 --> 00:15:48.680 align:start position:0% them 00:15:48.680 --> 00:15:50.260 align:start position:0% them everything<00:15:49.130> is<00:15:49.250> center<00:15:49.610> of<00:15:49.640> them<00:15:49.850> can<00:15:50.149> be<00:15:50.240> seen 00:15:50.260 --> 00:15:50.270 align:start position:0% everything is center of them can be seen 00:15:50.270 --> 00:15:54.420 align:start position:0% everything is center of them can be seen and<00:15:50.770> studied<00:15:51.770> and<00:15:52.730> if<00:15:52.910> you're<00:15:53.089> using<00:15:53.330> the 00:15:54.420 --> 00:15:54.430 align:start position:0% and studied and if you're using the 00:15:54.430 --> 00:15:57.400 align:start position:0% and studied and if you're using the original<00:15:55.430> Genesis<00:15:56.300> they<00:15:56.870> might<00:15:57.050> even<00:15:57.260> be 00:15:57.400 --> 00:15:57.410 align:start position:0% original Genesis they might even be 00:15:57.410 --> 00:16:00.699 align:start position:0% original Genesis they might even be people<00:15:57.860> who<00:15:58.040> have<00:15:58.220> access<00:15:58.490> and<00:15:58.940> can<00:15:59.709> interact 00:16:00.699 --> 00:16:00.709 align:start position:0% people who have access and can interact 00:16:00.709 --> 00:16:05.910 align:start position:0% people who have access and can interact and<00:16:01.160> have<00:16:01.370> ether<00:16:01.790> on<00:16:01.820> that<00:16:02.089> Private<00:16:02.450> Network 00:16:05.910 --> 00:16:05.920 align:start position:0% 00:16:05.920 --> 00:16:08.350 align:start position:0% some<00:16:06.920> final<00:16:07.279> notes<00:16:07.310> you<00:16:07.820> should<00:16:08.000> think<00:16:08.180> about 00:16:08.350 --> 00:16:08.360 align:start position:0% some final notes you should think about 00:16:08.360 --> 00:16:11.050 align:start position:0% some final notes you should think about your<00:16:08.660> risks<00:16:09.050> and<00:16:09.260> your<00:16:09.470> exposures<00:16:10.070> okay<00:16:10.880> and 00:16:11.050 --> 00:16:11.060 align:start position:0% your risks and your exposures okay and 00:16:11.060 --> 00:16:14.740 align:start position:0% your risks and your exposures okay and your<00:16:11.510> threats<00:16:13.270> according<00:16:14.270> to<00:16:14.360> what<00:16:14.510> you<00:16:14.630> are 00:16:14.740 --> 00:16:14.750 align:start position:0% your threats according to what you are 00:16:14.750 --> 00:16:16.810 align:start position:0% your threats according to what you are doing<00:16:15.050> and<00:16:15.320> what<00:16:15.410> your<00:16:15.560> what<00:16:16.220> your<00:16:16.339> assets<00:16:16.520> are 00:16:16.810 --> 00:16:16.820 align:start position:0% doing and what your what your assets are 00:16:16.820 --> 00:16:20.230 align:start position:0% doing and what your what your assets are and<00:16:17.290> the<00:16:18.290> way<00:16:18.410> to<00:16:18.470> increase<00:16:18.980> security<00:16:19.190> is<00:16:19.940> to 00:16:20.230 --> 00:16:20.240 align:start position:0% and the way to increase security is to 00:16:20.240 --> 00:16:22.930 align:start position:0% and the way to increase security is to minimize<00:16:20.839> the<00:16:21.110> likelihood<00:16:21.290> and<00:16:21.950> the<00:16:22.040> impacts 00:16:22.930 --> 00:16:22.940 align:start position:0% minimize the likelihood and the impacts 00:16:22.940 --> 00:16:26.500 align:start position:0% minimize the likelihood and the impacts and<00:16:23.690> those<00:16:23.839> minimize<00:16:24.290> the<00:16:24.440> risk<00:16:24.970> and<00:16:25.970> to<00:16:26.360> do 00:16:26.500 --> 00:16:26.510 align:start position:0% and those minimize the risk and to do 00:16:26.510 --> 00:16:28.720 align:start position:0% and those minimize the risk and to do that<00:16:26.690> you<00:16:26.959> typically<00:16:27.320> separate<00:16:27.860> isolate<00:16:28.430> and 00:16:28.720 --> 00:16:28.730 align:start position:0% that you typically separate isolate and 00:16:28.730 --> 00:16:32.350 align:start position:0% that you typically separate isolate and defend<00:16:29.300> everywhere<00:16:29.720> possible<00:16:30.160> and<00:16:31.360> harden 00:16:32.350 --> 00:16:32.360 align:start position:0% defend everywhere possible and harden 00:16:32.360 --> 00:16:34.870 align:start position:0% defend everywhere possible and harden your<00:16:32.420> environment<00:16:32.930> so<00:16:33.380> I<00:16:33.649> study<00:16:34.010> the<00:16:34.190> VM<00:16:34.610> and 00:16:34.870 --> 00:16:34.880 align:start position:0% your environment so I study the VM and 00:16:34.880 --> 00:16:37.350 align:start position:0% your environment so I study the VM and learn<00:16:35.089> solidity<00:16:35.630> used<00:16:35.990> best<00:16:36.260> practices<00:16:36.920> and 00:16:37.350 --> 00:16:37.360 align:start position:0% learn solidity used best practices and 00:16:37.360 --> 00:16:41.410 align:start position:0% learn solidity used best practices and if<00:16:38.360> you<00:16:38.480> worried<00:16:38.690> about<00:16:38.810> consensus<00:16:39.560> issues<00:16:40.420> on 00:16:41.410 --> 00:16:41.420 align:start position:0% if you worried about consensus issues on 00:16:41.420 --> 00:16:44.019 align:start position:0% if you worried about consensus issues on network<00:16:41.810> attack<00:16:42.140> just<00:16:43.100> run<00:16:43.339> several<00:16:43.730> clients 00:16:44.019 --> 00:16:44.029 align:start position:0% network attack just run several clients 00:16:44.029 --> 00:16:45.820 align:start position:0% network attack just run several clients in<00:16:44.300> parallel<00:16:44.660> that's<00:16:44.870> a<00:16:44.990> big<00:16:45.170> strength<00:16:45.560> that 00:16:45.820 --> 00:16:45.830 align:start position:0% in parallel that's a big strength that 00:16:45.830 --> 00:16:47.260 align:start position:0% in parallel that's a big strength that we<00:16:46.010> have<00:16:46.160> in<00:16:46.279> aetherium<00:16:46.610> that<00:16:46.880> there<00:16:47.000> are<00:16:47.089> so 00:16:47.260 --> 00:16:47.270 align:start position:0% we have in aetherium that there are so 00:16:47.270 --> 00:16:49.510 align:start position:0% we have in aetherium that there are so many<00:16:47.480> different<00:16:47.990> client<00:16:48.350> versions<00:16:48.770> so<00:16:49.490> that 00:16:49.510 --> 00:16:49.520 align:start position:0% many different client versions so that 00:16:49.520 --> 00:16:54.780 align:start position:0% many different client versions so that one<00:16:50.300> network<00:16:50.720> attack<00:16:53.410> touching<00:16:54.410> would 00:16:54.780 --> 00:16:54.790 align:start position:0% one network attack touching would 00:16:54.790 --> 00:16:57.880 align:start position:0% one network attack touching would doesn't<00:16:55.810> affect<00:16:56.810> the<00:16:56.959> whole<00:16:57.140> network<00:16:57.380> at<00:16:57.680> once 00:16:57.880 --> 00:16:57.890 align:start position:0% doesn't affect the whole network at once 00:16:57.890 --> 00:17:01.060 align:start position:0% doesn't affect the whole network at once but<00:16:58.220> only<00:16:58.339> parts<00:16:58.790> of<00:16:58.940> the<00:16:59.029> network<00:17:00.010> try<00:17:01.010> to 00:17:01.060 --> 00:17:01.070 align:start position:0% but only parts of the network try to 00:17:01.070 --> 00:17:02.620 align:start position:0% but only parts of the network try to build<00:17:01.310> things<00:17:01.550> that<00:17:01.670> anyone<00:17:02.029> can<00:17:02.300> use 00:17:02.620 --> 00:17:02.630 align:start position:0% build things that anyone can use 00:17:02.630 --> 00:17:08.740 align:start position:0% build things that anyone can use not<00:17:03.140> just<00:17:03.410> us<00:17:04.209> techniques<00:17:07.360> there's<00:17:08.360> lots<00:17:08.600> of 00:17:08.740 --> 00:17:08.750 align:start position:0% not just us techniques there's lots of 00:17:08.750 --> 00:17:12.220 align:start position:0% not just us techniques there's lots of work<00:17:09.339> going<00:17:10.339> on<00:17:10.640> which<00:17:11.300> I<00:17:11.630> would<00:17:11.780> hope<00:17:11.929> that 00:17:12.220 --> 00:17:12.230 align:start position:0% work going on which I would hope that 00:17:12.230 --> 00:17:14.169 align:start position:0% work going on which I would hope that more<00:17:12.589> people<00:17:12.650> get<00:17:13.040> involved<00:17:13.280> in<00:17:13.520> here<00:17:14.000> are<00:17:14.120> a 00:17:14.169 --> 00:17:14.179 align:start position:0% more people get involved in here are a 00:17:14.179 --> 00:17:15.939 align:start position:0% more people get involved in here are a couple<00:17:14.240> of<00:17:14.540> discussions<00:17:15.140> that<00:17:15.439> are<00:17:15.709> happening 00:17:15.939 --> 00:17:15.949 align:start position:0% couple of discussions that are happening 00:17:15.949 --> 00:17:18.579 align:start position:0% couple of discussions that are happening in<00:17:16.339> the<00:17:16.760> form<00:17:16.970> of<00:17:17.089> ethereum<00:17:17.870> improvement 00:17:18.579 --> 00:17:18.589 align:start position:0% in the form of ethereum improvement 00:17:18.589 --> 00:17:19.919 align:start position:0% in the form of ethereum improvement protocol 00:17:19.919 --> 00:17:19.929 align:start position:0% protocol 00:17:19.929 --> 00:17:24.010 align:start position:0% protocol there's<00:17:21.670> 134<00:17:22.670> and<00:17:23.150> discussion<00:17:23.630> about<00:17:23.720> how<00:17:23.990> we 00:17:24.010 --> 00:17:24.020 align:start position:0% there's 134 and discussion about how we 00:17:24.020 --> 00:17:26.049 align:start position:0% there's 134 and discussion about how we can<00:17:24.230> prevent<00:17:24.500> cross-chain<00:17:25.189> replay<00:17:25.670> attacks 00:17:26.049 --> 00:17:26.059 align:start position:0% can prevent cross-chain replay attacks 00:17:26.059 --> 00:17:31.780 align:start position:0% can prevent cross-chain replay attacks using<00:17:27.580> by<00:17:28.780> changing<00:17:29.780> how<00:17:29.960> transactions<00:17:30.800> the 00:17:31.780 --> 00:17:31.790 align:start position:0% using by changing how transactions the 00:17:31.790 --> 00:17:33.850 align:start position:0% using by changing how transactions the fields<00:17:32.210> in<00:17:32.390> them<00:17:32.570> that<00:17:33.110> they're<00:17:33.290> only<00:17:33.440> valid 00:17:33.850 --> 00:17:33.860 align:start position:0% fields in them that they're only valid 00:17:33.860 --> 00:17:38.410 align:start position:0% fields in them that they're only valid after<00:17:34.010> a<00:17:34.220> particular<00:17:34.670> hash<00:17:36.790> 138<00:17:37.790> concerning 00:17:38.410 --> 00:17:38.420 align:start position:0% after a particular hash 138 concerning 00:17:38.420 --> 00:17:42.940 align:start position:0% after a particular hash 138 concerning the<00:17:38.540> bomb<00:17:40.000> 140<00:17:41.000> how<00:17:41.540> can<00:17:41.809> implement<00:17:42.080> throw<00:17:42.620> in 00:17:42.940 --> 00:17:42.950 align:start position:0% the bomb 140 how can implement throw in 00:17:42.950 --> 00:17:48.640 align:start position:0% the bomb 140 how can implement throw in a<00:17:43.100> cheaper<00:17:43.610> way<00:17:45.880> 116<00:17:46.880> we<00:17:47.809> can<00:17:48.020> add<00:17:48.110> a<00:17:48.170> static 00:17:48.640 --> 00:17:48.650 align:start position:0% a cheaper way 116 we can add a static 00:17:48.650 --> 00:17:51.310 align:start position:0% a cheaper way 116 we can add a static call<00:17:48.890> up<00:17:49.130> code<00:17:49.370> which<00:17:49.820> would<00:17:50.000> make<00:17:50.390> it<00:17:50.540> you 00:17:51.310 --> 00:17:51.320 align:start position:0% call up code which would make it you 00:17:51.320 --> 00:17:53.380 align:start position:0% call up code which would make it you could<00:17:51.470> call<00:17:51.800> a<00:17:51.830> contract<00:17:52.610> from<00:17:52.760> a<00:17:52.880> contract 00:17:53.380 --> 00:17:53.390 align:start position:0% could call a contract from a contract 00:17:53.390 --> 00:17:56.200 align:start position:0% could call a contract from a contract but<00:17:53.750> that<00:17:53.809> contract<00:17:54.800> cannot<00:17:55.040> modify<00:17:55.429> it 00:17:56.200 --> 00:17:56.210 align:start position:0% but that contract cannot modify it 00:17:56.210 --> 00:18:01.690 align:start position:0% but that contract cannot modify it States<00:17:57.280> so<00:17:58.280> it<00:17:58.430> would<00:17:58.640> make<00:18:00.700> reentrant 00:18:01.690 --> 00:18:01.700 align:start position:0% States so it would make reentrant 00:18:01.700 --> 00:18:02.650 align:start position:0% States so it would make reentrant attacks 00:18:02.650 --> 00:18:02.660 align:start position:0% attacks 00:18:02.660 --> 00:18:05.170 align:start position:0% attacks impossible<00:18:03.410> well<00:18:03.800> they<00:18:04.340> can<00:18:04.550> reenter<00:18:04.730> but 00:18:05.170 --> 00:18:05.180 align:start position:0% impossible well they can reenter but 00:18:05.180 --> 00:18:06.520 align:start position:0% impossible well they can reenter but they<00:18:05.270> can't<00:18:05.480> modify<00:18:05.720> the<00:18:05.840> state<00:18:06.080> while<00:18:06.410> you're 00:18:06.520 --> 00:18:06.530 align:start position:0% they can't modify the state while you're 00:18:06.530 --> 00:18:11.230 align:start position:0% they can't modify the state while you're entering<00:18:07.420> one<00:18:08.420> or<00:18:08.570> two<00:18:09.670> make<00:18:10.670> it<00:18:10.700> possible<00:18:10.970> to 00:18:11.230 --> 00:18:11.240 align:start position:0% entering one or two make it possible to 00:18:11.240 --> 00:18:13.300 align:start position:0% entering one or two make it possible to do<00:18:11.450> ring<00:18:11.690> signatures<00:18:12.230> elliptic<00:18:12.950> curve 00:18:13.300 --> 00:18:13.310 align:start position:0% do ring signatures elliptic curve 00:18:13.310 --> 00:18:16.750 align:start position:0% do ring signatures elliptic curve cryptography<00:18:13.610> on<00:18:14.570> chain<00:18:14.930> and<00:18:15.230> one<00:18:16.010> one<00:18:16.250> is<00:18:16.490> one 00:18:16.750 --> 00:18:16.760 align:start position:0% cryptography on chain and one one is one 00:18:16.760 --> 00:18:18.970 align:start position:0% cryptography on chain and one one is one that<00:18:16.790> I<00:18:17.030> really<00:18:17.240> like<00:18:17.480> big<00:18:18.110> into<00:18:18.350> Earth<00:18:18.470> Mattox 00:18:18.970 --> 00:18:18.980 align:start position:0% that I really like big into Earth Mattox 00:18:18.980 --> 00:18:21.600 align:start position:0% that I really like big into Earth Mattox would<00:18:19.610> enable<00:18:19.970> make<00:18:20.330> it<00:18:20.450> possible<00:18:20.630> to<00:18:20.870> the<00:18:21.050> RSA 00:18:21.600 --> 00:18:21.610 align:start position:0% would enable make it possible to the RSA 00:18:21.610 --> 00:18:24.880 align:start position:0% would enable make it possible to the RSA cryptography<00:18:22.610> and<00:18:22.820> those<00:18:23.510> PGP<00:18:24.110> verification 00:18:24.880 --> 00:18:24.890 align:start position:0% cryptography and those PGP verification 00:18:24.890 --> 00:18:29.080 align:start position:0% cryptography and those PGP verification on<00:18:25.160> chain<00:18:25.630> so<00:18:26.630> I<00:18:27.350> urge<00:18:27.920> you<00:18:28.310> all<00:18:28.340> to<00:18:28.400> get 00:18:29.080 --> 00:18:29.090 align:start position:0% on chain so I urge you all to get 00:18:29.090 --> 00:18:32.370 align:start position:0% on chain so I urge you all to get involved<00:18:29.600> in<00:18:29.780> the<00:18:30.290> ongoing<00:18:30.710> discussion 00:18:32.370 --> 00:18:32.380 align:start position:0% involved in the ongoing discussion 00:18:32.380 --> 00:18:36.640 align:start position:0% involved in the ongoing discussion that's<00:18:33.380> all<00:18:33.560> for<00:18:33.740> me<00:18:33.830> thank<00:18:34.580> you